You must log in or register to comment.
Bluesky doesn’t really have federation. It doesn’t matter what server you’re on, it’s really just distributed hosting. Which is cool - but not as cool as federation.
Nah, I’m good.
Nostr vs Mastodon on Privacy & Autonomy:
- Relay/instance admins can choose which content goes through their relay on either platform
- On nostr, your DMs are encrypted. In Mastodon, the admin of the sender and receiver can read them, as can anybody else who breaks into their server
- On nostr, a relay admin can control what goes through their relay, but they can’t stop you from following/DMing/being followed by whoever you want since you are typically connected to multiple relays at once. As long as one relay allows it, signal flows. Nostr provides the best of both worlds: moderated “public squares” according to your moderation preferences, autonomy to follow/dm/be followed by anybody you want (assuming that individual user hasn’t blocked you).
- On mastodon, your identity is tied to your instance. If your instance goes down, you lose your follow/followee list, DMs, etc. On Nostr, it’s not, so this doesn’t happen. Mastodon provides some functionality to migrate identity between instances but it’s clunky and generally requires to have some form of advanced notice.
- Both have all the same functions as twitter: tweet, reply, re-tweet, DM, like, etc.
Why I think nostr will win https://lemmy.ml/post/11570081
This thread is about bluesky…
And you can transfer your account to another instance and it retains your followers so that user i wrong too. But i still like that your account isn’t tied to an instance feature of nostr.
All that needs to happen now is for it to work with activpub
After the drama that erupted from that ActivityPub-to-Bluesky bridge, I don’t think Bluesky will risk that kind of thing.
ActivityPub projects are free to implement AT Proto, of course, and bridges can still exist perfectly fine.
There was drama?
Lots of it. People beind mad that their Mastodon posts ended up on Bluesky, mostly. There’s a Github thread that includes a recap of most of the drama.
A section of the Fediverse sees the Fediverse as a separate thing from the big companies and other social media and wants to stay isolated rather than federate as widely as possible.
It’s possible to simply not federate outside of a specified whitelist, of course, but that doesn’t seem to be what the people complaining about the bridge want either
@leraje @muntedcrocodile The architecture of their protocol is highly incompatible with the way ActivityPub works.
With their protocol you have got the PDS (Personal Data Storage) that stores your data. Your handle is a hostname, but normally it will not be the hostname of your PDS. In fact you can use any hostname that you have control of. Your account itself is described via the DID that will never change - and that doesn’t contain a hostname. This means that you can move between different PDS without people noticing it at all.
In ActivityPub the data storage is on the same host like your handle and your account’s URL will always point to the host where your data is located. Moving your account is by far not as smooth and highly depends on the system that you are on.
