2 ms·
I've tried to read through the AT Protocol specs but they're very vague and clearly unfinished. Their view on federation isn't exactly what I'm looking for ("a
by jeroenhd 4y ago
I've tried to read through the AT Protocol specs but they're very vague and clearly unfinished. Their view on federation isn't exactly what I'm looking for ("a bunch of Twitters that can theoretically interoperate" rather than a decentralized platform) but I suppose only having one or two main servers does solve the "I don't know whether to pick outlook.com or gmail.com" problem that many new Mastodon users seem to face.
ActivityPub is no walk in the park either. It's a protocol closer to "the HTTP of social media" than a way to interoperate with other servers. Basic functionality is easy, all you need is a few static JSON files, but if you want to write an application around it you're going to have to dive deep into the docs.
What I don't really see is why BlueSky decided to make its own protocol. Like Mastodon is an API that works on top of ActivityPub, BlueSky could've just been a better ActivityPub server as far as I can tell. Most of the big problems ("my toots disappeared after the server shut down") can be resolved without an entirely new protocol.
Going back to the drawing board seems like an excellent way to find all the hurdles every other protocol already encountered. The recent "official" s3 account is just one example of that, and I'm sure there will be more.
Maybe the value add of the AT protocol will become clearer once it's finished. I'm sure there will be ATProto <-> ActivityPub bridges to make both networks integrate for the people who wish to do so. As far as I can tell, BlueSky is just a new, exclusive Twitter with an API at this moment.
- philipwhiuk 4y ago> As far as I can tell, BlueSky is just a new, exclusive Twitter with an API at this moment Honestly I assumed that was the USP - Twitter sans Musk.