PDSes only store user data. These are full instances that can be used to browse the network. The idea is to make your account really yours. Bluesky is hosting most of them. But there are some people who do it on their own.
But bluesky controls much more important components in the network, namely the Relay and AppView.
If Bluesky decides to cut off your PDS you are pretty much alone.
Bluesky is pretty much a centralized platform like Twittler.
Wait, there are 1600 BlueSky instances to join? Are they counting people using a custom domain name as an entire instance?
I suppose PDS instances are included: https://github.com/bluesky-social/pds
OK so it sounds like there is still just the single BlueSky that is “federated” with a handful of single-user BlueSkies?
PDSes only store user data. These are full instances that can be used to browse the network. The idea is to make your account really yours. Bluesky is hosting most of them. But there are some people who do it on their own.
But bluesky controls much more important components in the network, namely the Relay and AppView.
If Bluesky decides to cut off your PDS you are pretty much alone.
Bluesky is pretty much a centralized platform like Twittler.
Zeppelin.social is 3rd party appview and you can host your own
https://whtwnd.com/bnewbold.net/3lo7a2a4qxg2l
Add using DID:Web and you’re now fully self hosted