This makes it 3 relays synced up now?

Pretty neat progress for the p2p relay set up. Changes on one relay instantly replicate to the other relay super fast.

This post is being written on Damus (Desktop) to a relay on local host and will be broadcast out on my other Damus client on my iPhone.

Much more code clean up and error checking to do here but the GitHub for this will be set up soon.

Looks like writing to this online relay replicates nicely

Test

123345

Testing

Testing post on pocket relay

Nostr has lost the battle for censorship resistance.

While WE all know that Nostr is superior because it’s a protocol, people do NOT care enough. They are more interested in what’s written ON the box, not what’s necessarily inside the box.

The people who did care about “free speech” are now placated enough with Rumble for Video, X for short form, Substack for long form. With Meta now throwing their weight behind the movement, it’s game over for this narrative - at least for the foreseeable future.

There is no way Nostr as a brand can claim that space in people’s minds, especially against multiple established brands.

That ‘censorship resistance’ and ‘free speeech’ ships have sailed (even though they were fake), and the people who cared enough boarded.

The normies who never cared, still don’t care, or they found their way to the anti-platforms, like Threads, BlueSky or Pornhub.

The small minority of us still here on Nostr…are well…still here. We’re building, which is great - that MUST happen before anything else.

But if the goal is to grow the network effect here and bring in more people, then we need to find a new angle. Something more compelling that is a “running towards” value, not a “running away from” value.

I’m not 100% sure what that is. My instinct is that a “network of incredible applications”, that don’t necessarliy or explicitly brand themselves as Nostr, but have it under the hood is the right direction, but it needs more experimentation. Also needs more really well-build apps for non-sovereignty minded people (especially content creators) and people who don’t necessarly care about the reasons Nostr was first built.

We’ve been working away at this Satlantis thing for almost a year now and it’s coming along - albeit WAY slower than I would’ve liked. We’ve made a whole bunch of mistakes and at times I feel like a LARP considering the state of non-delivery.

BUT…we made some big changes in the last 2mths since missing a couple key deadlines, and I’m pretty confident we’ll have something cool to show in a month or two.

Let’s see if this approach starts to bring new interest andn activity here. Or if I’m full of shit. Either way, I’m going to keep looking for a better ngle than “free speech” because I no longer think that’s a battle we can win (we can come back and fight that battle when the time is more right, and when the winds have shifted in our favor once more).

What app should I use to write long-from content on Nostr?

DUDE! I may have a direct use of a tool that lets you easily play games over the pear stack! Let’s chat

Lol yeah, ideas wizzing around here. Also the issue of maintaining all those npubs with a sign-in extension or whatnot.

Nice. Earlier I was thinking along these lines for DMs to deal with the metadata issue without requiring gift-wrapping.

-Bob creates a secondary npub, this npub has no profile

-Bob messages Alice from the secondary npub with a special event called an 'It's me message' (IMM) or some such thing. This templated message contains Bob's actual npub

-Alice's client receives the IMM and sends back an IMM return (also an event type, contains a code valid for a period of time)

-Bob's client adds this code to Bob's profile, similar to adding a TXT record for DNS verification

-Bob's client sends a "go check" message to Alice

-Alice's client sees the code on Bob's profile and marks the DM chat as as being with Bob. Code is no longer needed.

The idea being this would all run over a few seconds, and Alice would not have to know anything about it if the verification failed.

Thought about this for a second but haven’t worked out the UX.

- You have a main key 1234 and a secondary one generated 5678 separately (non derived from main key)

- your main npub has a kind 0 profile that has information that says that your “subkey” is 5678

- your subkey has a kind 0 profile event that just says “parent” 1234

- you use key 5678 and post a message

- clients that understand this will look up key 5678 kind 0 eventand see that it points to a parent key 1234.

- clients will check kind 0 event for 1234 and also see that it confirms the subkey.

If parent npub is compromised the subkey can disassociate.

If the sub key is compromised the parent key can disassociate.

Not sure of the UX because of having to manage multiple distinct keys to manage.

I might think more about this. Thoughts?

Nostr's main goal for 2025:

Figure out if we prefer single pubkey in all of our apps and thus a single main follow list, single notification feed for everything, single key to send DMs OR if we prefer owning multiple pubkeys, one for each app, so that follows, notifications, profile info can all be separate per app.

There are pros and cons in each. And any solution between those two gets really complicated.

For instance,

- If we use multiple keys, one per app, our DMs will also be on a "per-app" basis and senders for the DM wouldn't know which app you are still using to send you a DM. We would need to declare which key everybody should use for DMs with us.

- If we use just one key, we need to move away from our main follow list event so that each app can have their own follows and all sub-root event kinds (zaps, boosts, reactions, replies, reports, edits, etc) MUST also include the event kind of the root event so that each app can have their own notifications. Since it's impossible to require full compliance from ALL clients, it's likely that some notifications won't show up where they should.

- If we use multiple keys, friends of one app might not be readily available when @-tagging on a separate app. We can try to link all the keys so that Clients can always check information in the other keys to bring up to you, maybe as a fall back mode. But wouldn't that in the long term just create the same one-key for everything system?

Who knows...

Most people subscribe to: "if I'm not doing anything illegal I have nothing to hide" and therefore don't care about anonymity or anything like that. It's just a hassle to them. People love to go to extremes so like Daniel implies, that gets morphed into "If you're trying to hide something you're certainly doing something illegal."

Most people can only think one step ahead. They don't consider that their data can be turned against them to look like they're guilty of something they didn't do.

Nevermind all the security breaches and identity theft and all that mess happening all around us. Yes it's mindboggling that people can be so negatively affected by something yet actively reject the solution to their problems.

Look, people are stupid, to their own detriment.