cross-posted from: https://lemmy.zip/post/70749935
An interesting blog post about how the AT protocol has it’s own cool little ecosystem next to the fediverse.
It’s really interesting how the way ATproto is both more and less as every service must follow a strict format to interact with others using the same format.
Like, ATproto has more variety than the fediverse, but the way they interact is a bit more strict, which means that a post from a lemmy analogue wouldn’t show up on bluesky, but it also means that each platform often seems more polished.
I think the lexicon requirement certainly leads to a more polished look as you don’t have to worry about custom interactions across multiple platforms, interoperability is basically baked in (given it’s built to begin with).
It’s quite nice I’ve been working in it quite a lot. A lot of people here tend to get into the “my protocol is better” arguments but honestly both sides have the same ultimate goal, each has its quirks.
Note on the variety, a lot of these like Mu is re-using the bluesky lexicon so it’s effectively like a Mastadon Client. Same goes for Offprint, Leaflet, Pckt they all use the same Standard Site lexicon so they’re effectively clients with some frontend niceties built in and maybe their own features, but the core is the same.
Also my account here is actually atproto 👋
But whatever gateway you’re using to federate with the fediverse must be speaking ActivityPub, otherwise we wouldn’t be seeing your comment, right?