Involuntarily when I say decentralized I'm thinking about more peer-to-peer distribution of content (a la torrents), instead of federated. Mastodon instances are these islands of content, at the whims of the owner, as to what content you can see and what policies they think there should be. Your identity is also attached to the instance, migration isn't seamless and you can't just move around your account like a domain name.
My understanding of Bluesky, actually the AT protocol, is that there are features in there to allow you to own your identity (via domain names) which would make migration between instances seamless. At the same time, there is a different deployable services for redistributing (filtered/moderated) content.
Based on posts I've seen on HN, these were still partial of planned things (?). On the other hand, not even sure if there are self-hosted Bluesky instances yet.
> which would make migration between instances seamless.
Which instances? :)
If you're referring to "Personal Data Stores", sure. However, it's the "Relay" (i.e. the aggregator that generates timelines) that everyone relies on is centralized. In contrast, with Mastodon for example, both "Personal Data Store" and "Relay" functionalities are decentralised, offering a complete solution with no centralised choke-points. At least that's my non-authoritative understanding.
There is this lengthy blog post, _How decentralized is Bluesky really?_ [0], if you want to read more about the differences between Bluesky and ActivityPub (e.g. Mastodon).
Thanks for the clarification. That makes more sense now.
I host my own GoToSocial instance, with only me as it's single user. Doesn't get much more decentralized than that.
I guess it's easier to move your identity to a different PDS on Bluesky, but for me Bluesky doesn't count as decentralized as long as there's only one single relay. You may own your identity, but currently Bluesky (the company) owns the network.
Involuntarily when I say decentralized I'm thinking about more peer-to-peer distribution of content (a la torrents), instead of federated. Mastodon instances are these islands of content, at the whims of the owner, as to what content you can see and what policies they think there should be. Your identity is also attached to the instance, migration isn't seamless and you can't just move around your account like a domain name.
My understanding of Bluesky, actually the AT protocol, is that there are features in there to allow you to own your identity (via domain names) which would make migration between instances seamless. At the same time, there is a different deployable services for redistributing (filtered/moderated) content.
Based on posts I've seen on HN, these were still partial of planned things (?). On the other hand, not even sure if there are self-hosted Bluesky instances yet.