Yeah at first I was thinking discovery of endpoints for identity, for which it's pretty hard to disagree that PKDNS is a step up over free-floating metadata events. For nostr at this point I wonder how painful processing a list of carefully selected breaking changes (encryption type included) would be? Even just changing encryption and maybe transport, and leaving most everything else the same. My gut says nostr would bounce back pretty quick, given that so much of nostr a this point is nostr enthusiasts. Of course if it didn't bounce back that'd be a big "D'oh!" moment.
The other discovery seems like a problem that if you *genuinely* have it that's a good sign!
Login to reply
Replies (1)
Have a look at nostr next
-- tons of good stuff in there
Discovery is sovled in nostr with did-nostr, which is far better than spray and pray. It's simply a case of which clients want discovery and which want to struggle on without.
If you want censorship-resistance then #pubky is your choice. And it slots nicely into with did-nostr and discovery. Gen-1 clients will continue trending sideways, bluesky will continue growing, and clients that upgrade will gain market share.
The web is working as expected.
GitHub
GitHub - mikedilger/nostr-next: Issues with nostr that would require breaking changes to fix
Issues with nostr that would require breaking changes to fix - mikedilger/nostr-next