• 0 Posts
  • 11 Comments
Joined 2 months ago
cake
Cake day: November 5th, 2024

help-circle
  • The entire point is that your pds can interact with multiple “instances” of bluesky or whatever other apps people build on the protocol.

    For example there is a reddit/hn clone that people can post on (keeping their same identity) when the official bluesky service goes down. The reddit clone is fully independent from the twitter clone, but they use the same protocol and (unlike AP) the same hosting and authentication infrastructure.

    Whereas on Lemmy and mastodon, my accounts are totally separate. And unlike AP, your data lives on your own pds and is never hostage to the owner of the instance that actually runs the load bearing interactivity. If they become compromised or shut down you can switch to another. No cooperation from the old owner required (unlike activitypub).



  • I asked the devs about this and they said that bluesky is designed to be a) modular b) trustless as much as possible. federation is supposed to happen on the trustless hosting and relay layers - you can ask your posts to be crawled by any indexer/appview.

    But once you get to the indexing/querying layer, there are no more merkle proofs to keep everyone honest, so there is no point in federating because any indexer can modify/censor the content they send to another indexer instance. So you could still build an api to interact laterally between servers, but it wouldn’t be atproto anymore.