On interoperability—this is what made the web so big. It didn’t just invent HTML; it embraced email, PDFs, FTP, IRC—systems it didn’t control. Anything useful it could connect to was added to its growth path. Today, you can link to a PDF and it just works—even though the web didn’t create PDF viewers. When I spoke with Tim Berners-Lee, inventor of the web, and mentioned Nostr, his first question was, “What’s Nostr?” After I explained, his response was: “Let’s make my web OS interoperable with it.” That’s already been merged. In contrast, when I once suggested to fiatjaf that the wider web might want to use Nostr, he replied: “I hope they never use it.” Interoperability isn’t just about protocols talking to themselves—it’s about acknowledging that other systems exist, and figuring out how to work with them. That’s how the web won. View quoted note →

A github star is a more effective intervention than a vote in a national election. And it is quicker to do. If people were taught this, and the principle of why that is, we would be living in a different world, where internecine institutions are made irrelevant. View quoted note →

“You never change things by fighting the existing reality. To change something, build a new model that makes the existing model obsolete.”

The reason that consistent profiles in nostr is important, is that zaps dont work without them. Say you have your profile overwritten, or you are rugged, and have to move your lnprovider (both have happened to me multiple times) then setting up a new provider is not an easy process, if you use multiple apps. I am more technical than most but my zaps have not been working well for over a year, and i rarely even click the zap any more, and zaps that I kindly get I dont always get to see who from. While some devs think that inconsistent profiles are a feature of decentralizaion, not a bug, I say we can and should fix it. One advantage did-nostr could offer would be to have a consistent profile that is up-to-date and discoverable by clients. We'd have to get clients to buy in to it, but clients that offer more consistent profiles could out compete those that dont.

Honestly, I was never a fan of Bluesky’s approach to identity with DIDs. I always felt that, with a clean slate, we could’ve built something much better on Nostr—but that opportunity never really materialized. Given that, the next best path was to bring Nostr’s identity system up to parity with Bluesky’s, which is what we’ve aimed to do with did-nostr. In fact, there are a few aspects I believe will end up being better than Bluesky’s did:plc. Of course, it’s going to take significant investment and a solid growth strategy to compete with Bluesky. But at least when it comes to identity, Nostr is now in a position where it has feature parity.

Nostr DID Method Specification

View quoted note →

This is a great list. Hopefully, did-nostr will be a step toward greater interoperability with the rest of the web:

Nostr DID Method Specification

View quoted note →

If we were to add the latest timestamp to nostr-did, and ensure it is not overwritten by an older timestamp, it would be possible to solve the consistent profile, and buggy following UX in nostr. NIP-05 providers could simply point to a DID and update it on the server, or allow the user to update it via NIP-98. Some providers would offer it as a paid service, others offer it for free.

Nostr DID Method Specification

What if nostr accounts were tradable?

Red Dragon

Sketch: Selling Digital Art with DID-Nostr, Bitcoin, and Nostr This is only a sketch, but I think it is 90% there already.

DEV Community

Sketch: Selling Digital Art with DID-Nostr, Bitcoin, and Nostr

Sketch: Selling Digital Art with DID-Nostr, Bitcoin, and Nostr The fusion of digital...

Two levels of censorship-resistance are emerging via open protocols. One is the dns-censorship-resistance model (nostr et al 2020) which is the same model as the current web w/ replication, and subject to take downs. The second model is the bittorrent-censorship reistance model of the web (pkarr, pubky et al c. 2025) which seems to be holding its own, even against take down requests. It's trivial to upgrade users to offer both level of censorshp-resistance for nostr devs. And it will be interesting to see which clients are the first upgrade their censorship resistance, and which are the last. I think we're moving from a first gen nostr which was a proof of concept. To a second gen which actually is verifiably censorship resistant and is scale free. Exciting!