Nostr Web Client

The most stupid thing about the entire concept of a "DID" is that it was supposed be this one interoperable thing, right? You use "DIDs" in your project and now people using all sorts of DIDs can interoperate.

But what actually happens in practice (obviously) is that projects have to pick one specific DID and support just that.

So Web5 only works with "did-dht" and Bluesky with "did-plc" (aka their server) and one is not compatible with the other.

But somehow Nostr is less compatible and morally wrong because Nostr keys don't have a "did:" prefix in them.

nostr:nevent1qyd8wumn8ghj7urewfsk66ty9enxjct5dfskvtnrdakj7qgmwaehxw309aex2mrp0yh8wetnw3jhymnzw33jucm0d5hsz9mhwden5te0wfjkccte9ehx7um5wghxyctwvshsz9thwden5te0wfjkccte9ejxzmt4wvhxjme0qy88wumn8ghj7mn0wvhxcmmv9uq36amnwvaz7tmwdaehgu3wvf5hgcm0d9hx2u3wwdhkx6tpdshszxrhwden5te0wfjkccte9e3h2unjv4h8gtnx095j7qpqzxjq7cesh9dehesk60k99xlgkqf4st98l8ax2kz6wzd4zt08nkeqz3ts7a

frphank 1y ago

That linked document specifies a "did:key" btw -- that's like nostr.

Reply to this note

Please Login to reply.

Discussion

fiatjaf 1y ago

Except no, because keys are different in different curves, and Nostr is not interoperable with anything because Nostr keys specifically sign Nostr events and all the tooling and apps expect that. It's not possible to just plug a new DID method, which was the idea, but I don't expect you understand my point anymore.

_ 1y ago

did:key has secp256k1 variants, and if you used did:dht, you can just put your npub in your key set, along with any other keys you want to add of any types. Additionally, you can add relay endpoints to your DID's service endpoint routing section.

frphank 1y ago

😃😃

I'm glad we've got smart cookies running the show here.