Interesting post about BlueSky’s underlying federated protocol (AT Protocol)
You must log in or # to comment.
“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.
They’re kind of right, though. Basic interaction with ActivityPub even on a small server causes a storm of HTTP requests. It’s not very efficient, but efficiency has been sacrificed to allow for easier decentralisation.
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.
I’m not clear who the intended audience is here. A self-moderated micro-blogging platform is what most people needed all along, which is why the Fediverse exists. The real question remains how a corporate Fedi-protocol is going to interact with advertisers and marketers.
