No joke, this PR adds preliminary ActivityPub (i.e. Mastodon) support to the PDS. 🤯
IMPORTANT: You shouldn't expect full interoperability with this alone! At most, you should expect that your p...
Hmm, let’s see if I remember the terminology correctly:
Client apps have nothing to do with it, obviously.
Alternate appviews have nothing to do with it, except in that they’d presumably need to work with whatever form of atproto federation exists, if any did.
Alternate relays aren’t federated unless there’s some protocol for routing messages between them — such as ActivityPub.
A PDS stores your posts/comments/likes/blocks/articles/whatever. These all get crawled and saved to a relay.
An appview connects to a relay and sorts through all the posts, and indexes them.
They handle all the interactions, rather than passing messages between servers.
Hmm, let’s see if I remember the terminology correctly:
Client apps have nothing to do with it, obviously.
Alternate appviews have nothing to do with it, except in that they’d presumably need to work with whatever form of atproto federation exists, if any did.
Alternate relays aren’t federated unless there’s some protocol for routing messages between them — such as ActivityPub.
So, bluesky works differently to fedi.
A PDS stores your posts/comments/likes/blocks/articles/whatever. These all get crawled and saved to a relay.
An appview connects to a relay and sorts through all the posts, and indexes them.
They handle all the interactions, rather than passing messages between servers.
Let me just ask the less technical and more important questions: