I might be missing something, but all of these seem like solvable problems. They are mostly data transformation problems, AFAICS. For example, it seems fairly trivial (especially relative to the payoff of doing so) to map a Bluesky feed to a key pair in Nostr to make it easy to consume that way. Indeed, this could be a monetisation vector for relays able to offer more advanced interoperability features. It’s not like the problems of integrating with, say, Twitter, Reddit, or Facebook. There are far more obstacles to that than merely transforming data from one shape into another: violating terms of service, lack of APIs, KYCing, etc.

Actually, Mostr is pretty broken, as I've described: 📝 d0c360d0… Agree that this is a pathway to what @4b461234…7953bde6 has described as "adversiarial interoperability." Personally I think this is a great way to jumpstart Nostr's growth, but I don't think it's a long-term solution for the reasons @tree 木 describes.

My comment was specifically about bridges and multi-platform clients. That's what I think doesn't work and is a waste of time. One-time migration tools make sense, but that's a little different story for me. For example, Matrix protocol has a lot of bridges, but that hasn't helped with adoption much. Similarly, on Bluesky, there is Bridgy Fed to connect to Activity Pub, but I don't think that has had any major impact on growth either. I feel like bridges like this are helping more the larger network become even more dominant, instead of helping smaller networks grow... so maybe it's counterproductive in some way.

> @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.

Hello yes, working alot of did:nostr of late https://nostrcg.github.io/did-nostr/