Replying to Avatar SondreB

nostr:nprofile1qqsdulkdrc5hdf4dktl6taxmsxnasykghdnf32sqmnc7w6km2hhav3g2kyjn9 has been working on DID support for Nostr, which would make any Nostr key pair pluggable into the DID/VC ecosystem.

I just read a blog post regarding the cost of moving social networks, and how Facebook integrated a "backdoor" into MySpace allowing users to migrate more easily back in the day. Mastodon did something similar when people started exit from Twitter, until they stopped it by closing down their APIs.

The bridge with Mastodon that nostr:nprofile1qqsqgc0uhmxycvm5gwvn944c7yfxnnxm0nyh8tt62zhrvtd3xkj8fhggpt7fy built works fairly well, it does increase the amount of content on Nostr.

You're pointing out a major issue though and there is no good solution to the situation.
Avatar
tree 木 21h ago 💬 1

> @Melvin Carvalho has been working on DID support for Nostr, which would make any Nostr key pair pluggable into the DID/VC ecosystem.

Do you have any details about that? The fact that Nostr identity will have a DID variant is useless in itself if other protocol (such as the AT Protocol) does not implement it.

Moreover, the idea that you can create a DID variant of Nostr identity and it will be "pluggable" is very naive, ignoring all dependencies, identity is just the tip of the iceberg. Identity (actually the public key) is tied to human-readable identifiers, to profile information, content... and each protocol works completely differently in this.

Reply to this note

Please Login to reply.

Discussion

Avatar
Élodie Carter 9h ago

It's how the internetw works and is interoperable, via uniform resource identifiers. Needs a bit of adoption but is making slow but steady progress.

https://nostrcg.github.io/did-nostr/