@mcc i mean to be fair, fedi has the same issue where a huge amount of users is in mastodon.social
also, blacksky is a thing
@nelson 1. but u r not on mastodon.social. so if mastodon.social went down you could keep posting
2. i use blacksky and it appears to have gone down at the same time as bluesky this morning! i was able to get on by using staging.bluesky which is rudy's long-promised "alternate stack"
I mean, Red Dwarf exists, nothing about ATProto specifies that you require an AppView or centralized relay, the main issue really is that everyone's on the same PDS
Wafrn actually doesn't even touch the AppView and it federates pretty well with everything else, most people say there isn't much of a difference other than the architectural difference of not having a centralized stream of information which is useful on its own right, for stuff like algo feeds
I do agree with your point though, Bluesky (as a product) is still largely centralized, it's just not a problem of the network itself but the implementation of the "defacto way" to interact with it
@mcc Really valid, I like to have conversations like these with people who clearly know what they’re talking about.
I didn’t really see the glaring flaw with the way ATProto is built not just as technology and infrastructure but the actual organizational flaws and overall centralized governance of the protocol designers, I will consider this in the future.
I still have lots of hope on it, I guess it mostly comes from my total lack of hope in ActivityPub as a decentralized social network protocol, but I do think there are a couple of interesting ideas in how it solves a lot of the usual problems with decentralized social networks. I unironically like the concept of an AppView, it’s just not very easy to distribute.
I wonder what you think about Versia /genq /lh