Interesting post about BlueSky’s underlying federated protocol (AT Protocol)
AT seems like pretend decentralization. theyve just hidden the important centralized layers in services controlled by ‘the big guys’ because ‘traffic volume’…
so its still going to be a bunch of endpoints(instances) required to talk to these giant relays if you want any users to see any content whatsoever.
no thanks. the more i read, the more this is an over-engineered nightmare not reallly offering any benefit for those nightmares.
barrier to instance entry is still deep, and reliant on a giant ex-twitter corporation to exist.
“For example, if every time I post a new update on BlueSky, if I had to send my post to every single one of my followers’ repositories, that would be extremely inefficent”
Somewhat ironic to have this posted on and activitypub driven fediverse.
isn’t it the opposite of ironic? they’re using a federated blogging platform to talk about a federated microblogging platform. they wouldn’t make a full length blog post like this on blue sky.