Bluesky Social still clearly dominates the ecosystem, but there is no single component of the system that does not have a open/alternative option for exit.
Do you disagree? Is there a specific centralized component you take issue with?
Bluesky Social still clearly dominates the ecosystem, but there is no single component of the system that does not have a open/alternative option for exit.
Do you disagree? Is there a specific centralized component you take issue with?
Users can move their follows, followers and posts to zeppelin.social fron BlueSky transparently?
Now you can of course debate on what "decenttalized" means, but in a social network easy migration between servers is the crucial feature that would allow the decentralized network to emerge.
Edit. Does the network actually work over at zeppelin.social alone if Bluesky servers go down?
I totally agree. However, a lot of people in the fediverse/ActivityPub world apparently (?) disagree, seeing as your domain is tightly coupled to your server, i.e. no name portability. Seems like a wild oversight to me, and getting massive instances like matrix.org and mastadon.social seems like an inevitable consequence.
Lack of name portability implies greater risk when choosing a server. Greater risk when choosing a server means choosing comparatively less risky servers. Choosing comparatively less risky servers means choosing more well-known servers. Thus you have the GMail-ification of the fediverse.
Yes, even if Bluesky was down (as long as they have a backup) which is not the case for ActivityPub.
Migration between servers is so seamless that is causes confusion and doubt that the protocol even supports migration, because there is basically zero in-app visibility of which users are on which server.
Yes, the network continues to work on zeppelin.social if Bluesky servers are down.
Making it hard to setup or run, complex to understand or change are also forms of discouraging independent use.