I've been wondering about Bluesky's decentralization again.
Fediverso
11
Posts
9
Posters
1
Views
-
I've been wondering about Bluesky's decentralization again. I can't think of any reason why I'd want to self-host Bluesky in its current form. I cannot 100% self host "my own Bluesky".
Their main selling points for building their own protocol were easier migration and better discoverability, but right now there's no simple way to migrate my Bluesky account to my own instance. And hosting the centralized parts yourself isn't really possible, or if it were, not affordable, they haven't made that feasible, by design, it seems.
Even if you self-host a PDS, Bluesky's Relay only indexes up to 10 accounts from it. You can run more, but they won't federate, the central infrastructure decides what gets seen. They control this (source: https://docs.bsky.app/blog/self-host-federation#:~:text=For%20a%20smooth%20transition%20into,for%20everyone%20in%20the%20ecosystem.). You can self-host a PDS (Personal Data Server), but you still depend on Bluesky's centralized Relay and AppView. There's no production-ready alternative infrastructure from what I gather.
It feels like I'd be renting a room in a hotel that someone else is running anyway, when I want my own hotel.
If Mastodon gGmbH vanishes tomorrow, my instance keeps running and federating with everyone else. If Bluesky PBC vanishes, the ecosystem would need to scramble to stand up replacement infrastructure that doesn't really exist yet.
ATProto keeps getting evaluated on its promises while other systems get evaluated on their merits. The "portability" selling point depends on infrastructure that isn't mature enough to actually catch you if Bluesky falls.
I trust W3C, the builders and fathers of the World Wide Web, ActivityPub and the Fediverse.
#Decentralization #SelfHosting #SelfHosted #Mastodon #Fediverse #Bluesky #Servers
-
I've been wondering about Bluesky's decentralization again. I can't think of any reason why I'd want to self-host Bluesky in its current form. I cannot 100% self host "my own Bluesky".
Their main selling points for building their own protocol were easier migration and better discoverability, but right now there's no simple way to migrate my Bluesky account to my own instance. And hosting the centralized parts yourself isn't really possible, or if it were, not affordable, they haven't made that feasible, by design, it seems.
Even if you self-host a PDS, Bluesky's Relay only indexes up to 10 accounts from it. You can run more, but they won't federate, the central infrastructure decides what gets seen. They control this (source: https://docs.bsky.app/blog/self-host-federation#:~:text=For%20a%20smooth%20transition%20into,for%20everyone%20in%20the%20ecosystem.). You can self-host a PDS (Personal Data Server), but you still depend on Bluesky's centralized Relay and AppView. There's no production-ready alternative infrastructure from what I gather.
It feels like I'd be renting a room in a hotel that someone else is running anyway, when I want my own hotel.
If Mastodon gGmbH vanishes tomorrow, my instance keeps running and federating with everyone else. If Bluesky PBC vanishes, the ecosystem would need to scramble to stand up replacement infrastructure that doesn't really exist yet.
ATProto keeps getting evaluated on its promises while other systems get evaluated on their merits. The "portability" selling point depends on infrastructure that isn't mature enough to actually catch you if Bluesky falls.
I trust W3C, the builders and fathers of the World Wide Web, ActivityPub and the Fediverse.
#Decentralization #SelfHosting #SelfHosted #Mastodon #Fediverse #Bluesky #Servers
@rolle Nicely put.
This is the reason I went with Mastodon in 2022 and still not regretting it.
-
I've been wondering about Bluesky's decentralization again. I can't think of any reason why I'd want to self-host Bluesky in its current form. I cannot 100% self host "my own Bluesky".
Their main selling points for building their own protocol were easier migration and better discoverability, but right now there's no simple way to migrate my Bluesky account to my own instance. And hosting the centralized parts yourself isn't really possible, or if it were, not affordable, they haven't made that feasible, by design, it seems.
Even if you self-host a PDS, Bluesky's Relay only indexes up to 10 accounts from it. You can run more, but they won't federate, the central infrastructure decides what gets seen. They control this (source: https://docs.bsky.app/blog/self-host-federation#:~:text=For%20a%20smooth%20transition%20into,for%20everyone%20in%20the%20ecosystem.). You can self-host a PDS (Personal Data Server), but you still depend on Bluesky's centralized Relay and AppView. There's no production-ready alternative infrastructure from what I gather.
It feels like I'd be renting a room in a hotel that someone else is running anyway, when I want my own hotel.
If Mastodon gGmbH vanishes tomorrow, my instance keeps running and federating with everyone else. If Bluesky PBC vanishes, the ecosystem would need to scramble to stand up replacement infrastructure that doesn't really exist yet.
ATProto keeps getting evaluated on its promises while other systems get evaluated on their merits. The "portability" selling point depends on infrastructure that isn't mature enough to actually catch you if Bluesky falls.
I trust W3C, the builders and fathers of the World Wide Web, ActivityPub and the Fediverse.
#Decentralization #SelfHosting #SelfHosted #Mastodon #Fediverse #Bluesky #Servers
@rolle I self host my own PDS, but yeah, too much depends on their centralized services. I think Blacksky is trying to set up a completely separate but federated instance, but if even they struggle to, I don’t see any way for a lone person like me to.
-
I've been wondering about Bluesky's decentralization again. I can't think of any reason why I'd want to self-host Bluesky in its current form. I cannot 100% self host "my own Bluesky".
Their main selling points for building their own protocol were easier migration and better discoverability, but right now there's no simple way to migrate my Bluesky account to my own instance. And hosting the centralized parts yourself isn't really possible, or if it were, not affordable, they haven't made that feasible, by design, it seems.
Even if you self-host a PDS, Bluesky's Relay only indexes up to 10 accounts from it. You can run more, but they won't federate, the central infrastructure decides what gets seen. They control this (source: https://docs.bsky.app/blog/self-host-federation#:~:text=For%20a%20smooth%20transition%20into,for%20everyone%20in%20the%20ecosystem.). You can self-host a PDS (Personal Data Server), but you still depend on Bluesky's centralized Relay and AppView. There's no production-ready alternative infrastructure from what I gather.
It feels like I'd be renting a room in a hotel that someone else is running anyway, when I want my own hotel.
If Mastodon gGmbH vanishes tomorrow, my instance keeps running and federating with everyone else. If Bluesky PBC vanishes, the ecosystem would need to scramble to stand up replacement infrastructure that doesn't really exist yet.
ATProto keeps getting evaluated on its promises while other systems get evaluated on their merits. The "portability" selling point depends on infrastructure that isn't mature enough to actually catch you if Bluesky falls.
I trust W3C, the builders and fathers of the World Wide Web, ActivityPub and the Fediverse.
#Decentralization #SelfHosting #SelfHosted #Mastodon #Fediverse #Bluesky #Servers
@rolle Very well put. And in addition, the service itself, I think, has a serious risk of being endangered if the current American administration sees it as a threat. Also, they seem to soon run out of money. Lots of 🚩🚩🚩
-
I've been wondering about Bluesky's decentralization again. I can't think of any reason why I'd want to self-host Bluesky in its current form. I cannot 100% self host "my own Bluesky".
Their main selling points for building their own protocol were easier migration and better discoverability, but right now there's no simple way to migrate my Bluesky account to my own instance. And hosting the centralized parts yourself isn't really possible, or if it were, not affordable, they haven't made that feasible, by design, it seems.
Even if you self-host a PDS, Bluesky's Relay only indexes up to 10 accounts from it. You can run more, but they won't federate, the central infrastructure decides what gets seen. They control this (source: https://docs.bsky.app/blog/self-host-federation#:~:text=For%20a%20smooth%20transition%20into,for%20everyone%20in%20the%20ecosystem.). You can self-host a PDS (Personal Data Server), but you still depend on Bluesky's centralized Relay and AppView. There's no production-ready alternative infrastructure from what I gather.
It feels like I'd be renting a room in a hotel that someone else is running anyway, when I want my own hotel.
If Mastodon gGmbH vanishes tomorrow, my instance keeps running and federating with everyone else. If Bluesky PBC vanishes, the ecosystem would need to scramble to stand up replacement infrastructure that doesn't really exist yet.
ATProto keeps getting evaluated on its promises while other systems get evaluated on their merits. The "portability" selling point depends on infrastructure that isn't mature enough to actually catch you if Bluesky falls.
I trust W3C, the builders and fathers of the World Wide Web, ActivityPub and the Fediverse.
#Decentralization #SelfHosting #SelfHosted #Mastodon #Fediverse #Bluesky #Servers
@rolle This neatly sums up why, every time a BS fan was talking about federation, I just didn't get it. Now I understand they were only pretending to talk about federation, or perhaps worse, talk about some twisted definition of 'federation'. That's why I simply didn't understand them. They were talking about something else entirely, while claiming "federation" at the same time.
Gaslighting by design?
-
I've been wondering about Bluesky's decentralization again. I can't think of any reason why I'd want to self-host Bluesky in its current form. I cannot 100% self host "my own Bluesky".
Their main selling points for building their own protocol were easier migration and better discoverability, but right now there's no simple way to migrate my Bluesky account to my own instance. And hosting the centralized parts yourself isn't really possible, or if it were, not affordable, they haven't made that feasible, by design, it seems.
Even if you self-host a PDS, Bluesky's Relay only indexes up to 10 accounts from it. You can run more, but they won't federate, the central infrastructure decides what gets seen. They control this (source: https://docs.bsky.app/blog/self-host-federation#:~:text=For%20a%20smooth%20transition%20into,for%20everyone%20in%20the%20ecosystem.). You can self-host a PDS (Personal Data Server), but you still depend on Bluesky's centralized Relay and AppView. There's no production-ready alternative infrastructure from what I gather.
It feels like I'd be renting a room in a hotel that someone else is running anyway, when I want my own hotel.
If Mastodon gGmbH vanishes tomorrow, my instance keeps running and federating with everyone else. If Bluesky PBC vanishes, the ecosystem would need to scramble to stand up replacement infrastructure that doesn't really exist yet.
ATProto keeps getting evaluated on its promises while other systems get evaluated on their merits. The "portability" selling point depends on infrastructure that isn't mature enough to actually catch you if Bluesky falls.
I trust W3C, the builders and fathers of the World Wide Web, ActivityPub and the Fediverse.
#Decentralization #SelfHosting #SelfHosted #Mastodon #Fediverse #Bluesky #Servers
@rolle Blacksky has its own AppView and a Bluesky-independent way of unlocking users who have been blocked by Bluesky, for example.
A person can host a PDS on a server of their choice, including their own, and connect to the service they prefer.https://bsky.app/profile/rude1.blacksky.team/post/3m4ra7cs75s2z
https://bsky.app/profile/rude1.blacksky.team/post/3mccvziodyc2v
https://bsky.app/profile/rude1.blacksky.team/post/3mcg5h5ef2k2z
I can also connect to At Proto via Blacksky
https://blacksky.community/profile/did:plc:w4xbfzo7kqfes5zb7r6qv3rw/post/3m4ra7cs75s2z
-
@rolle Blacksky has its own AppView and a Bluesky-independent way of unlocking users who have been blocked by Bluesky, for example.
A person can host a PDS on a server of their choice, including their own, and connect to the service they prefer.https://bsky.app/profile/rude1.blacksky.team/post/3m4ra7cs75s2z
https://bsky.app/profile/rude1.blacksky.team/post/3mccvziodyc2v
https://bsky.app/profile/rude1.blacksky.team/post/3mcg5h5ef2k2z
I can also connect to At Proto via Blacksky
https://blacksky.community/profile/did:plc:w4xbfzo7kqfes5zb7r6qv3rw/post/3m4ra7cs75s2z
RE: https://toot.cafe/@thereisnocat/115906352914274869
@zotheca So I've heard. But there are challenges.
https://mementomori.social/@thereisnocat@toot.cafe/115906353041503398
-
RE: https://toot.cafe/@thereisnocat/115906352914274869
@zotheca So I've heard. But there are challenges.
https://mementomori.social/@thereisnocat@toot.cafe/115906353041503398
@rolle Yes, I would say the biggest challenge is the amount of data that is transferred there, which makes it hardly suitable for a home server. A Hubzilla installation can be set up as PHP on the side. The system does not require every user to have their own relay at home.
The question is, at what number of offerings is decentralization achieved? Are Bluesky and Blacksky sufficient, or do we also need Eurosky and Northernsky, and so on? And is it necessary for decentralization that everyone can host at home...
Basically, the statement often made in the Fediverse that there is only one AppView and that Bluesky can therefore simply pull the plug is, in my view, incorrect and, for many people, more a matter of populism.
Currently, if I am not satisfied with Bluesky's moderation of applications, I can easily switch to Blacksky.
-
@rolle Very well put. And in addition, the service itself, I think, has a serious risk of being endangered if the current American administration sees it as a threat. Also, they seem to soon run out of money. Lots of 🚩🚩🚩
@doktorzjivago @rolle Let's hope they do run out of money...
🙄
-
I've been wondering about Bluesky's decentralization again. I can't think of any reason why I'd want to self-host Bluesky in its current form. I cannot 100% self host "my own Bluesky".
Their main selling points for building their own protocol were easier migration and better discoverability, but right now there's no simple way to migrate my Bluesky account to my own instance. And hosting the centralized parts yourself isn't really possible, or if it were, not affordable, they haven't made that feasible, by design, it seems.
Even if you self-host a PDS, Bluesky's Relay only indexes up to 10 accounts from it. You can run more, but they won't federate, the central infrastructure decides what gets seen. They control this (source: https://docs.bsky.app/blog/self-host-federation#:~:text=For%20a%20smooth%20transition%20into,for%20everyone%20in%20the%20ecosystem.). You can self-host a PDS (Personal Data Server), but you still depend on Bluesky's centralized Relay and AppView. There's no production-ready alternative infrastructure from what I gather.
It feels like I'd be renting a room in a hotel that someone else is running anyway, when I want my own hotel.
If Mastodon gGmbH vanishes tomorrow, my instance keeps running and federating with everyone else. If Bluesky PBC vanishes, the ecosystem would need to scramble to stand up replacement infrastructure that doesn't really exist yet.
ATProto keeps getting evaluated on its promises while other systems get evaluated on their merits. The "portability" selling point depends on infrastructure that isn't mature enough to actually catch you if Bluesky falls.
I trust W3C, the builders and fathers of the World Wide Web, ActivityPub and the Fediverse.
#Decentralization #SelfHosting #SelfHosted #Mastodon #Fediverse #Bluesky #Servers
@rolle Well, the problem is that vast majority of people don't care about this.
*But*, one lesson from the forkiverse should be, this is still a great selling point for community organizers. And they can bring over their people.
-
I've been wondering about Bluesky's decentralization again. I can't think of any reason why I'd want to self-host Bluesky in its current form. I cannot 100% self host "my own Bluesky".
Their main selling points for building their own protocol were easier migration and better discoverability, but right now there's no simple way to migrate my Bluesky account to my own instance. And hosting the centralized parts yourself isn't really possible, or if it were, not affordable, they haven't made that feasible, by design, it seems.
Even if you self-host a PDS, Bluesky's Relay only indexes up to 10 accounts from it. You can run more, but they won't federate, the central infrastructure decides what gets seen. They control this (source: https://docs.bsky.app/blog/self-host-federation#:~:text=For%20a%20smooth%20transition%20into,for%20everyone%20in%20the%20ecosystem.). You can self-host a PDS (Personal Data Server), but you still depend on Bluesky's centralized Relay and AppView. There's no production-ready alternative infrastructure from what I gather.
It feels like I'd be renting a room in a hotel that someone else is running anyway, when I want my own hotel.
If Mastodon gGmbH vanishes tomorrow, my instance keeps running and federating with everyone else. If Bluesky PBC vanishes, the ecosystem would need to scramble to stand up replacement infrastructure that doesn't really exist yet.
ATProto keeps getting evaluated on its promises while other systems get evaluated on their merits. The "portability" selling point depends on infrastructure that isn't mature enough to actually catch you if Bluesky falls.
I trust W3C, the builders and fathers of the World Wide Web, ActivityPub and the Fediverse.
#Decentralization #SelfHosting #SelfHosted #Mastodon #Fediverse #Bluesky #Servers
This is why I’m on the Fediverse, bridging with BlueSky. Because I’d be happy to federate with them, if they’d open up as standard.
But they don’t. They want to keep to themselves unless someone explicitly says they want to bridge to Fediverse.
That’s the reason I don’t really trust BlueSky.
Did you see the European PDS, EuroSky?
-
undefined davew@mastodon.social shared this topic
Gli ultimi otto messaggi ricevuti dalla Federazione
-
Not sure about you 😉
But I will follow just for the cats.
-
@rufustheduck
Lovely cat! Here's some more moss
#mosstodon
-
@silverpill@mitra.social Thanks for sharing these links. I sometimes miss the articles... the one by @mapache@hachyderm.io is interesting, and deserves a response 🤔
-
Week in Fediverse 2026-01-16
Servers
- Mobilizon v5.2.2
- Owncast v0.2.4
- Epicyon v1.7.0
- Wafrn v2026.01.03
- PieFed v1.5.0
- snac v2.88
- ActivityPub for WordPress v7.8.3
- Sharkey v2025.4.5
- NodeBB v4.8.0
- NeoDB v0.12.8
- Trunk & Tidbits, December 2025 (Mastodon)
- WordPress Federation: Recap of 2025Clients
- PleromaFE v2.10.1
- Mastodon for iOS v2026.1
- TangerineUI for Mastodon v2.5.3
- Aria v1.4.0
- Voyager v2.43.2Tools and Plugins
- Fediway: Recommendation engine for Mastodon
Protocol
- FEP-f15d: Context Relocation and Removal
- FEP-ee3a: Exif metadata supportArticles
- The Forkiverse Experiment and Why Instance Choice Matters
- List of RSS feeds distributed by each software on Fediverse
- Fediverse Report – #149 – On Protocol Governance
- Mastodon for ActivityPub development-----
#WeekInFediverse #Fediverse #ActivityPub
Previous edition: https://mitra.social/objects/019ba420-e45f-3802-6e4f-5f0767dcc2d4
-
@shye maybe if you'd put some sugar in it...?
-
@rufustheduck@mastodon.social I spent some time in the USA, a long time ago now, and once took over British food that I thought would be interesting for them to try. But, I just could not get anyone to try mushy peas. For some reason the whole concept completely freaked them out. I even took mint source to go with it. But no.... weirdos...
-
@rufustheduck @jeridansky "Get that camera out of my face!" 😂
-
Or that weird red dot that zips around the wall and floor. What could it be?
