@Blaze AT (Bluesky’s protocol) is a little bit different then activity pub. There’s two types of servers, a PDS and a relay. A PDS is basically a git repository of all your posts/interactions, it’s super lightweight and doesn’t do anything but host them and provide it to any server that asks for it. The PDS basically does the profile hosting portion of a Mastodon server, and is very similar to a Nostr relay if you’re familiar with that.
A relay accesses data across a bunch of PDSs and provides it as one big network to the relay’s users. It’s basically the equivalent of the federated portion of what a Mastodon server does. It’s also doing what a Nostr client does (although Nostr does that on the user’s device) if you’re familiar with that.
Any relay can pull data from any PDS, so theoretically it’s very decentralized since anybody could host either a PDS and/or Relay. Bluesky was opened up very recently though, so there’s not many non-Bluesky-hosted PDSs on the network yet and most are small and experimental. There’s also no relays other than Bluesky that I’m aware of, although it’s only been open for ~6 months so I expect that’d change soon.
@erlend_sh Cool to see things being built with AT. For what my thoughts are worth, I think that having Frontpage posts showing up on Bluesky would be benificial. It’d probably make it feel like it has a lower barrier to entry and increase interactions/discussions across the different communities.
P.S. replying here with Friendica which is taking advantage of similar cross compatibility.
Also, just a curiosity, how good is AT’s cross compatibility without workarounds? Obviously if you guys are considering I assume it works, but I’ve been curious how well things play together. Nostr has NIPs to solve the issue, and ActivityPub is a little tempermental, but with AT’s repo style accounts I’ve wondered how well everything interacts across different implementations.