Account portability is the major reason why we chose to build a separate protocol. We consider portability to be crucial because it protects users from sudden bans, server shutdowns, and policy disagreements. Our solution for portability requires both signed data repositories and DIDs, neither of which are easy to retrofit into ActivityPub. The migration tools for ActivityPub are comparatively limited; they require the original server to provide a redirect and cannot migrate the user’s previous data.
Other smaller differences include: a different viewpoint about how schemas should be handled, a preference for domain usernames over AP’s double-@ email usernames, and the goal of having large scale search and discovery (rather than the hashtag style of discovery that ActivityPub favors).
rn not much. In the future there’ll be properly portable accounts using cryptographic keys and once federation kicks in lighter servers making it probably more distributed.
I am from Mastodon / ActivityPub bubble. Can someone explain me the benefits of Bluesky / AT protocol?
From their website:
https://atproto.com/guides/faq#why-not-use-activitypub
Sounds fair to me, although I am also not using either Mastodon or Bluesky.
rn not much. In the future there’ll be properly portable accounts using cryptographic keys and once federation kicks in lighter servers making it probably more distributed.
So nothing to keep an eye on considering an overwhelming amount of cons of Bluesky.
Exactly