It's interesting how the creators of the *multi-platform* social client @npub1plst...kx8j disappeared from Nostr. The last activity I see from the team is in August..
I am more and more convinced that bridging and connecting different protocols in the social sphere doesn't work very well.
Why?
Maintenance becomes exponential - Every protocol has its own update cycles and breaking changes. You're not building one client - you're building several. When one protocol changes, everything breaks.
Lowest common denominator - To work everywhere, bridges strip out what makes each protocol unique. Nostr's zaps, Mastodon's content warnings, Bluesky's feeds - all lost in translation. Users get a watered-down experience.
Identity doesn't translate - Nostr keypairs, ActivityPub domains, and AT Protocol DIDs are fundamentally incompatible. Bridges create confusing mapping layers instead of real unification.
Culture clash - Each protocol has its own norms and expectations. Bridges create an awkward middle ground where nobody feels at home.
Thread
Login to reply
Replies (2)
@melvincarvalho 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 @Alex Gleason 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.
Hello yes, working alot of did:nostr of late
Nostr DID Method Specification