#[0]​ what is your private key?

Dependency will fuck your day up.

#nostr is where the data is equal, identity is guaranteed, and aggregation is personal preference.

I keep seeing people write software where they pass state everywhere so everything can compute a value from it.

When delegation or passing expressions is suggest it is seen as “too complicated.” But we end up with objects/structs that have lots of state and methods because that is the only thing that gets passed around.

Anyone else been in this #software spot?

I’ll have to call that out in the post.

There is a trend that bech32 ids are generally *only used by humans* and the protocol itself uses hex encoding for most everything.

My understanding as well.

Joy is the only true measure of #success.

I have a #nostr library written to handle creating/reading events. I started a relay framework to test out building ideas on how to use the protocol to engage with different communities.

I love it.

A collection of people/computers who agree to generate ids from a subset of seeds to improve the odds of finding vanity keys for a portion of they fee collected to generate them.

You need vanity pools.

#nostr is a disjunction which equally contains all perspectives A || B || C and people build the intersections that are interesting or rewarding.

Vibe control suggests that communication be a conjunction where only the intersection A&B&C can exist. That world is small.

Things are starting to bloom.

I’ve been writing my own implementation.

I was thrilled to see my first message written from my own library!

Too late. Already observed.

Keep it fruity #beerstr !

Congrats!

How easy is it to white label the Damus client and just roll variations out. People can use the client that fits the view they desire.

Last night I was considering what it would be like to have #nostr delegates that run a small process on data and the result as events.

Sound like you could have a service that receives email and identifies creates a key pair for a sender. The worker publishes contact and content events to a private relay.

I wonder how that factors into the long term story of #nostr events. For example, what if my relay goes out of service and I want to migrate to another relay?

Maybe that is a path that is not available via the web socket and instead migration occurs out of band with different validation rules.