Global Feed Post Login
Replying to Avatar fiatjaf

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

Avatar
Vitor Pamplona 1y ago

Yep, DID Resolvers have always been a huge issue.

Funny thing: the universal DID resolver https://dev.uniresolver.io/ instantiates a docker machine for each DID method because it's impossible to develop a single library that resolves them all.

Reply to this note

Please Login to reply.

Discussion

No replies yet.