Running mostr
https://soapbox.pub/blog/mostr-fediverse-nostr-bridge/
- relay: wss://relay.mostr.pub
- user: https://mostr.pub/users/de7ecd1e2976a6adb2ffa5f4db81a7d812c8bb6698aa00dcf1e76adb55efd645
- followers: https://mostr.pub/users/de7ecd1e2976a6adb2ffa5f4db81a7d812c8bb6698aa00dcf1e76adb55efd645/followers
- following: https://mostr.pub/users/de7ecd1e2976a6adb2ffa5f4db81a7d812c8bb6698aa00dcf1e76adb55efd645/following
And what is mostr?
It's a bridge to the fediverse
Nice bridge, logically this kind of bridge should be capable to connect Bluesky and Nostr, right?
In theory yes
In practice, bluesky is going to struggle to interoperate with itself, imho. So, I'll believe it when I see it
I hope they do manage to build a bridge, tho. Everyone wins!
For example looking at this bridge
They have publicKey ... #main-key
This is good
But they dont do the same for the profile
It should be person ... #me
This is a general breakage across the fediverse, which is a relatively mature eco system. You can just about get away with these interop bugs
Bluesky is a whole other world, new clients, new servers, new identity schemes, new URI schems, lots of stuff that isnt finished.For example their DID identity method is called "placeholder". It's going to be really hard.
What they should do is align their keys with nostr, and create an overlap, and simple way to communicate with nostr. Then each of their other ideas they should see if they can fit in to the eco system piece by piece. Some will work, others not. Hopefully they will make a good looking app, that can also become a nostr client though.
Agree. Seems a lot of works for their Devs with those big burden and challenges. I think they will probably only make some interoperability bridge to Nostr after they can solve all the issues above. 😅
