Posts tagged: nostr

Thoughts To Nostr

2025-07-08T08:30:35Z

I am trying to use temporal at home for running automated pipelines. It’s definitely overkill for my use case but this is America…

So my first project is a system that takes my Thoughts and posts them to Nostr as I briefly discussed in Testing a Postiz Change Locally (IT WORKS!).

I have temporal infrastructure setup in homelab-compose and then homelab-temporal should probably be homelab-temporal-pipelines or something, but it’s the app code. I also have a repo homelab-social-media-pipelines - which has been consolidated down into homelab-temporal. once that all works I can destroy the homelab-social-media-pipelines repo

NOTE: everything is moving to homelab-mono

Issue 01 #

I am currently hitting a stupid python issue:

nic in homelab-temporal   main    ×2  ×4  ×7 via   v3.12.8(homelab-temporal)   (dev) 󰒄
⬢ [devbox] ❯ python -c "from homelab_temporal.postiz.postiz_client import PostizClient"
(homelab-temporal)
nic in homelab-temporal   main    ×2  ×4  ×7 via   v3.12.8(homelab-temporal)   (dev) 󰒄
⬢ [devbox] ❯ python scripts/postiz/simple_post.py
Traceback (most recent call last):
  File "/home/nic/projects/personal/homelab-temporal/scripts/postiz/simple_post.py", line 3, in <module>
    from homelab_temporal.postiz.postiz_client import PostizClient, process_for_nostr, process_for_x
ModuleNotFoundError: No module named 'homelab_temporal'

very dumb venv problem…

Resolution #

need to use python -m because the script is outside the project root? see 2025-07-08 Notes and the chatgpt notes for more on this but it works now

Thoughts Order #

as of 2025-07-11 Notes I have the thoughts ordering correct - we post the oldest thoughts up to the newest ones. Now I want more intros for the notes so they don’t get too repetitive

TODOs #

[x] - destroy the homelab-social-media-pipelines repo

[] - think about how to structure things more… monorepo in homelab-temporal might be hard to manage with AI tools due to context management… unsure though

[] - create workflow and activities for thoughts to nostr… revisit diagram to see what you need to build out in the temporal repo

[] - do something like this for github stars and then blog posts

I need to update my templates for nostr og images using this as fodder

<!-- HTML Meta Tags -->
<title>Nostr Design</title>
<meta
  name="description"
  content="A comprehensive resource for designers and developers to build successful nostr products"
/>

<!-- Facebook Meta Tags -->
<meta property="og:url" content="https://nostrdesign.org" />
<meta property="og:type" content="website" />
<meta property="og:title" content="Nostr Design" />
<meta
  property="og:description"
  content="A comprehensive resource for designers and developers to build successful nostr products"
/>
<meta
  property="og:image"
  content="https://nostrdesign.org/img/nostr-cover.jpg"
/>

<!-- Twitter Meta Tags -->
<meta name="twitter:card" content="summary_large_image" />
<meta property="twitter:domain" content="nostrdesign.org" />
<meta property="twitter:url" content="https://nostrdesign.org" />
<meta name="twitter:title" content="Nostr Design" />
<meta
  name="twitter:description"
  content="A comprehensive resource for designers and developers to build successful nostr products"
/>
<meta
  name="twitter:image"
  content="https://nostrdesign.org/img/nostr-cover.jpg"
/>

Dockerizing #

I think I wnt to dockerize my workers and workflows… build them out of the homelab-temporal repo but then run them in compose stacks… that can get stitched together better but for now that’ll probably be a good target. I have things to think about though… for example the blog builder needs my ssh keys, or an ssh key for a user… also git is a little mess up anyways

temporal link

Temporal #

I haev temporal workflows and stuff that all seem to work

on 2025-08-08 Notes I had issues with my nostr relay being too public, so I shut it down, reconfigured postiz and stuff and got it workign again, more restricted and in-memory database

Nostr

2025-07-02T21:22:03Z

How to start...

This isn’t a getting started with nostr - see [[getting-started-with-nostr]] for that

The nostr docs

Nostr is a very intriguing protocol for communication that lends itself to a decentrlized social media experience through the use of relays. I would love to understand it more fully someday, but I am inclined to be in line with almost anything decentrlized, and although the primary content in the nostr-verse right now is bitcoin, I am sure that as time goes on, the need for a truly free way to communicate will be necessary - and nostr won’t solve every problem, but I think it’ll be a tool in the set of solutions we come up with. It’s secure, decentralized, actively worked on, and very flexible.

NOSTR

Notes and Other Stuff Transmited over Relays

Decentralization #

Why does decentralization matter? Put simply - censorship. A founding principal of America is free speech and in recent years our right to speak freely has been put under severe fire.

I’ve crossed paths with people who very regularly talked about freedom of speech but it wasn’t until the last several years, mostly with covid that I started to pay a little closer attention. I’m not turning this post into any long rant about anything specific, but I do know that many voices were silenced on Facebook, Twitter/X, Insta, etc. Big Tech really threw the hammer down on people - a simple example was the Ivermectin stuff… which in the last 2 years has turned out to be a pretty effective treatment for many thousands of people!

But why does that matter? It’s because the platforms that existed which made it possible for anyone to “have an audience” made harsh judgements about what could and couldn’t be on their platforms… There’s pros and cons to this, but a primary con I see is that the power to limit the spread of information was pretty solely concentrated in the departments of these Big Tech firms that allowed or disallowed certain things to be said and expressed on their platforms.

Nostr is different here in that there’s no central command, no single data center or hub…. Nostr is a protocol, like HTTP is a protocol… anyone can send “Notes and Other Stuff over Relays” so developers can build any kind of UI for it, and you as the user can subscribe to relays that tend to have information you care about… in a sense it’s kind of like subreddits but not quite as organized (yet)…. but unlike reddit, there’s no central authority. The closest it gets is that a relay may go down or someone may choose to close one - no big, you just subscribe to other relays, or don’t subscribe to relays you don’t want to see

Another friend of mine likened this to RSS - and it’s also not UNlike that, but there’s more to it - the notes are on the relays, there’s encryption throughout the protocol, and several other standards called NIPS that make nostr unique, and I think bulletproof as we go into a future clouded by big government and big tech collaboration.

Brief Usage #

As for a usage pattern with nostr I think you have to combine the ideas of reddit, rss, and twitter…

Some apps like coracle.social have nice support for building “feeds” and “lists”… lists are combinations of tags (hashtags) and feeds are combinations of lists - at least in the coracle world. This means you can use lists of tags to discover content and users, create feeds of things you want to see regularly (like your RSS feed subscriptions), follow other users (using their pub keys see [## Follow Me]), and curate your social media experience in whatever way you want.

There’s nostr apps specific to mobile (primal, snort) and desktop (coracle.social). They help you set yourself up in different ways and to learn more about how I got started then checkout [[getting-started-with-nostr]]. There’s also content-driven nostr apps, for example fountain is great for music and podcasts that are distributed on the nostrverse, which feels like a totally different world than when I use coracle to browse my tech or bible related feeds.

End #

Nostr is a pretty cool thing taking shape… here’s some related info

Thank God for nostr podcast

nostr website

Note these posts aren’t available yet but they will show up on my RSS feed when they’re published

My post on [[getting-started-with-nostr]]

My project on Thoughts To Nostr

…

Follow Me #

my public key

npub1q3fsec2vcv99v80ga72dlv90qwkqmuxqcr6mdyumcmpkgudlhrespyurfj

Nostr hex key

2025-07-02T08:43:32Z

you can hexify your Nostr key when you need to sometimes which I needed to for Posts tagged: postiz (link with a thought I’m sure I have on postiz)


# /// script
# requires-python = ">=3.8"
# dependencies = [
#     "bech32",
# ]
# ///
#
import os

import bech32

# Set your nsec... key to NOSTR_PRIVATE_KEY or bake it in...
nsec_key = os.environ.get("NOSTR_PRIVATE_KEY")


def decode_nsec(nsec_key):
    hrp, data = bech32.bech32_decode(nsec_key)
    if hrp != "nsec":
        raise ValueError("Not a valid nsec key")
    decoded = bech32.convertbits(data, 5, 8, False)
    return bytes(decoded).hex()


# Example usage
raw_hex = decode_nsec(nsec_key)
print(f"Raw hex private key: {raw_hex}")

The Importance of Nostr According to ChatGPT

2025-01-24T06:38:03Z

Disclaimer #

This was written by ChatGPT with zero oversight from me. There are a few things that are not 100% accurate, but the main idea is there… I am hoping to actually write about my experience with nostr as I get more involved on the platform.

Social media has become a cornerstone of modern communication, allowing individuals to connect across borders and share ideas instantly. However, traditional platforms have raised concerns about censorship, data privacy, and the monopolistic control of user-generated content. Nostr (Notes and Other Stuff Transmitted by Relays), a decentralized social media protocol, offers a revolutionary alternative by emphasizing freedom, privacy, and user autonomy. This essay explores the transformative power of Nostr, why it matters, and provides a practical guide for beginners to get started.

The Power of Decentralization: Why Nostr Matters #

At its core, Nostr is a decentralized protocol designed to enable social media functionality without reliance on centralized servers. Unlike traditional platforms such as Twitter or Facebook, which depend on centralized infrastructure owned by corporations, Nostr operates on a peer-to-peer network facilitated by relays. This structural shift offers several key advantages:

Freedom of Expression
Centralized platforms often act as gatekeepers of content, enforcing moderation policies that can result in censorship. Nostr, on the other hand, allows users to communicate directly without interference from centralized authorities. This makes it particularly valuable for individuals in regions with restrictive speech laws.
Data Ownership
On traditional platforms, users sacrifice ownership of their data, which is often monetized by corporations. Nostr empowers users to retain control over their content and personal information by using cryptographic keys to manage identity.
Resilience Against Shutdowns
Centralized platforms are vulnerable to outages, government intervention, or corporate decisions to deplatform users. Nostr’s decentralized nature ensures that no single entity can shut it down, providing a more resilient communication medium.
Open and Transparent Ecosystem
As an open protocol, Nostr allows developers to create interoperable applications and services. This fosters innovation, enabling users to choose from a variety of client applications while maintaining access to the same network.

How Nostr Works: The Technical Backbone #

Nostr uses a simple yet effective system to transmit messages:

Public and Private Keys: Each user generates a pair of cryptographic keys. The private key acts as their identity, while the public key serves as their address on the network.
Relays: These are lightweight servers that broadcast messages. Users send notes (messages) to relays, which distribute them to other users.
Clients: Users access Nostr through client applications, which function as user interfaces. Examples include Damus (for mobile) and Amethyst.

This decentralized architecture eliminates single points of failure and gives users the flexibility to connect via multiple clients.

A Beginner’s Guide to Getting Started with Nostr #

For those new to Nostr, the decentralized structure might seem intimidating at first. However, with the following step-by-step guide, you’ll be able to join the network and start interacting with others seamlessly.

Step 1: Generate Your Keys #

The first step is to create a pair of cryptographic keys:

Private Key: This is your unique identifier and must be kept secret. Treat it like a password.
Public Key: This is your “address” on Nostr and can be shared with others.

Most Nostr client applications automatically generate these keys for you upon sign-up. Ensure you securely back up your private key, as losing it means losing access to your account permanently.

Step 2: Choose a Nostr Client #

Clients are the gateways through which you interact with the Nostr protocol. Popular options include:

Damus (iOS/Android): User-friendly and feature-rich.
Amethyst (Android): Tailored for Android users with a sleek interface.
Web Clients: Platforms like Nostr.guru or Iris allow you to access Nostr via a browser.

Install your chosen client and log in using your keys.

Step 3: Connect to Relays #

Relays are the backbone of the Nostr network, enabling message distribution. Most clients come pre-configured with default relays, but you can add more for better connectivity and reliability. Simply search for “Nostr relay services” and paste the relay URLs into your client settings.

Step 4: Explore and Interact #

Once set up, you can start exploring the network:

Follow Users: Add public keys of other users to your feed.
Post Notes: Share your thoughts or updates by creating a note, similar to a tweet.
Engage: Interact with others by replying to or liking their notes.

Step 5: Customize Your Experience #

Choose Relays Carefully: Some relays may specialize in certain topics or enforce content moderation policies. Tailor your relay list based on your interests and values.
Backup Your Keys: Use secure storage solutions like hardware wallets or encrypted cloud storage to protect your private key.
Experiment with Clients: Try multiple clients to find the one that suits your preferences.

The Broader Implications of Nostr #

The emergence of platforms like Nostr signals a broader shift toward decentralization in the digital era. By prioritizing user autonomy and privacy, Nostr challenges the centralized paradigms that have dominated the social media landscape for years. Its open architecture invites developers, activists, and everyday users to co-create a more inclusive and censorship-resistant digital space.

Moreover, Nostr’s impact extends beyond social media. Its decentralized protocol can be adapted for various purposes, such as secure communication, decentralized marketplaces, or even collaborative work environments. This versatility makes it a foundational building block for the next generation of internet technologies.

Conclusion #

Nostr represents a profound evolution in social media, offering a decentralized, user-centric alternative to traditional platforms. By empowering individuals with control over their identity, data, and content, it paves the way for a freer and more resilient online ecosystem. While its decentralized nature may pose a learning curve for beginners, the benefits far outweigh the challenges. By embracing Nostr, we can collectively take a step toward a more open and equitable digital future.

For those ready to explore this transformative platform, the journey begins with a simple act: generating your keys and connecting to the network. From there, the power of decentralized communication lies in your hands.

Using my own domain on nostr

2025-01-24T06:28:19Z

After generating a keypair on a nostr app (I started with primal) I copied my public key to /.well-known/nostr.json and put that at the root of my site at https://pype.dev.

The file looks like this:


{
  “names”: {
    “nic”: “npub1q3fsec2vcv99v80ga72dlv90qwkqmuxqcr6mdyumcmpkgudlhrespyurfj”
  }
}

So now I can use nic@pype.dev as on nostr because the client will verify the pubkey associated with my profile with my domain!

big upgrade from @primal.net