@eilah_tan @mastodonmigration @pluralistic It does federate I believe. But it's weird.
@rolle @eilah_tan @mastodonmigration @pluralistic
Bluesky is most likely federated, but I'm saying 'most likely' because nobody really knows what federation even means in the context of ATProto's architecture
This is not even getting into the parts that I think you should most likely take feed generators as a meaningful component of the system as well, making the question 'is it federated' even more confusing and devoid of meaning
https://fediversereport.com/a-conceptual-model-of-atproto-and-activitypub/
@laurenshof @rolle @mastodonmigration @pluralistic
oh wauw Laurens, this piece was already on my reading list but you really NAILED it on this explanation. As i understood it, the individualization/atomization of nodes in the network that runs on ATproto means there is not 'federation' between collectives as there is on the Fedi, but there is 'decentralization' of people's PDS' (and people can already 'join' the network from their own PDS, which they can share with others right?)
aww thank you!
and yes, thats correct! But there is more, because there is also decentralisation of AppViews. And also what I was getting at in the other discussion on bluesky we had: what if people move their interaction more and more towards the custom feeds on bluesky? Those are decentralised as well, and in a way tiny appviews. So thats what makes the whole question of 'is bluesky decentralised and federated' so confusing, its unclear what system part were even talking about
@laurenshof hmmm interesting, I have to sit on this for a bit.
A feed is more of 'a network', where your post might be moderated away from that network, but stays alive/visible elsewhere on bluesky.
Feed owners also get moderation power in the sense of 'deamplification' (if they manage to do ranking) and removing 'members' (and potentially removing specific post from a feed).
The parallel to de-federation on Bluesky impacts visibility rather than connection on fediverse.