@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.
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
All that needs to happen now is for it to work with activpub
@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.
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