@hesgen One of the huge issues I have with #Fediverse / #Mastodon / #ActivityPub is that it is engineered to be completely centered around instances, unlike other platforms.
And so this is one downside of that decision. When the instance goes down, it really messes with users.
It's why I emphasize that this platform is not decentralized but rather it is centralized around instances. Federated, not decentralized.
#BlueSky did not make the same design choice.
https://honk.tedunangst.com/u/tedu/h/6WRkFQqf2f25m9w2Xg
Also, they say on the blog and in the paper that they expect relays to only be hosted by large organizations.
@Hyolobrika @hesgen @volkris idk what you're reading that says otherwise. I'm sure if you do something "wrong" in the eyes of BlueSky, you wont be federating with their main "server"....that's a given, no? Maybe it's sort of like .social in the sense that it won't matter if enough users are on their own PDS, but I'd assume the mass majority will be on bsky.app or similar...is this wrong? Because their proprietary jargon doesn't make any of it clear at all.
PDS, DID, NSID etc are all new acronyms to me and I have to make up comparisons in my head because they're just terms they made up as far as I'm aware. It's not like I've been seeing those terms regularly or anything....
@volkris @hesgen well, decentralized in this case means not centralized on one instance. My instance can exist without any other instance existing.
On the other hand, I'd say BlueSky is centralized because BlueSky chooses who can "federate" with the main server. But each instance is on its own server that federated with the main. So it's centralized around the main server while being a federation with many instances.
I hope this makes sense.🤷♂️this is my take. Hope this doesn't come off as rude, just wanted to try to explain my thoughts.👍