About Bluesky and federation:
Edit: There might be some mistakes, and my information could be outdated, but the point still stands - Bluesky wasn't built on 100% federation from the start.
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: docs.bsky.app/blog/self-host-f….). 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
Early Access Federation for Self-Hosters | Bluesky
For a high-level introduction to data federation, as well as a comparison to other federated social protocols, check out the Bluesky blog.docs.bsky.app
Cynda hat dies geteilt.
John Ahlroos
Als Antwort auf Roni Rolle Laukkarinen • • •Nicely put.
This is the reason I went with Mastodon in 2022 and still not regretting it.
Ralph Brandi
Als Antwort auf Roni Rolle Laukkarinen • • •Emil Jacobs - Collectifission
Als Antwort auf Roni Rolle Laukkarinen • • •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?
DoktorZjivago
Als Antwort auf Roni Rolle Laukkarinen • • •Kalle Kniivilä
Als Antwort auf DoktorZjivago • • •@doktorzjivago Let's hope they do run out of money...
🙄
zotheca (Moved)
Als Antwort auf Roni Rolle Laukkarinen • • •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.
bsky.app/profile/rude1.blacksk…
bsky.app/profile/rude1.blacksk…
bsky.app/profile/rude1.blacksk…
I can also connect to At Proto via Blacksky
blacksky.community/profile/did…
Rudy wants revolution. (@rude1.blacksky.team)
Rudy wants revolution. (@rude1.blacksky.team) (Blacksky Community)Roni Rolle Laukkarinen
Als Antwort auf zotheca (Moved) • • •@zotheca So I've heard. But there are challenges.
mementomori.social/@thereisnoc…
Memento mori
mementomori.socialRalph Brandi
2026-01-16 19:09:50
zotheca (Moved)
Als Antwort auf Roni Rolle Laukkarinen • • •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.
Roni Rolle Laukkarinen
Als Antwort auf zotheca (Moved) • • •@zotheca It's not just populism when it comes to self-hosting and independence. The amount of data in the Fediverse is huge, yet you can still host everything from a USB stick if you want to (need S3 or NAS for storage, but anyway, it's simple).
I see Bluesky as false marketing in many ways. Decentralization, by definition, should mean as much as possible. We all know what happens when Cloudflare or AWS goes down - that's not decentralization if only a handful of large services exist. So I completely disagree with the idea that "a few is enough".
zotheca (Moved)
Als Antwort auf Roni Rolle Laukkarinen • • •Grow Your Own Services 🌱
Als Antwort auf zotheca (Moved) • • •@zotheca
Bluesky was able to ban Blacksky's users directly on Blacksky, it seems there's still a centralised kill switch in Bluesky's control:
plus.flux.community/p/banning-…
Banning controversy reveals Bluesky’s federation isn’t there yet
Matthew Sheffield (Flux)zotheca (Moved)
Als Antwort auf Grow Your Own Services 🌱 • • •@homegrown You can't argue with outdated information. The event you are referring to dates back to a time when Blacksky did not yet have an own Application(AppView). It was not a secret switch. You can check the date of the developments.
@rolle
irelephant
Als Antwort auf Grow Your Own Services 🌱 • • •Bluesky banned the user from their appview, the user still exists on alternative ones. reddwarf.app/profile/spacelaws…
staging.blacksky.community/pro…
Łink. (@spacelawshitpost.me)
Blacksky CommunityStefan Bohacek
Als Antwort auf Roni Rolle Laukkarinen • • •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.
Jens Ljungkvist
Als Antwort auf Roni Rolle Laukkarinen • • •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?
Mathew Storm
Als Antwort auf Roni Rolle Laukkarinen • • •That's crazy. I wonder why they are trying so hard to look decentralized, when under the hood they really aren't.
If they truly cared about decentralization, they would have implemented the already existing ActivityPub it became a W3C recommended standard in 2018...
Something fishy about bluesky. Thanks for sharing, I didn't know about this!
Roni Rolle Laukkarinen
Als Antwort auf Mathew Storm • • •@smattymatty Their problem is they wanted their own from the begin with, to control. They claim that Fediverse and ActivityPub community have been "suspicious" towards them, but also "it’d have been a difficult collaboration if we chose to use AP, especially since we weren’t willing to compromise on some of the decisions". I see it they never even wanted to try.
github.com/bluesky-social/atpr…
Already a decentralized federated protocol · Issue #255 · bluesky-social/atproto
dmbr0 (GitHub)gabboman the wafrn dev
Als Antwort auf Roni Rolle Laukkarinen • • •I have too many corrections on this one.
Pds a year ago when i got to 100 accounts I had to get in contact with someone on the team, now is higher
The relay and app view: have you seen appviewlite? Its quite light
Regarding production ready alternatives: blacksky. Seriously. Blacksky
The idea is different. Fedi is trains and bsky are trucks. Knowing about one doesn’t means you know the other. The architecture is too different.
And a lot of the times the question is “wait you dont get railed i mean use rails?”
If bsky llc vanished tomorrow it would be fine. Seriously
Its a bit late here but if you want we can keep this conversation later in a better medium than this one, this one will make both of us look like confrontational pricks
Else, Someone
Als Antwort auf gabboman the wafrn dev • • •gabboman the wafrn dev
Als Antwort auf Else, Someone • • •The idea for self hosting is the pds that does data stuff. The architecture is very different to the fedi one.
Making a simple “amnesic” relay is super cheap and simple. There are a lot of simple pieces and you can make all of them without bsky.
In this moment the only centralised stuff is the did:plc and they are working ok giving that to another open entity like w3c
(Did plc: hello yes account did something here is hosted in this domain (wich can chage))
The idea isn’t scaling down to a raspberry pi but a 30€ dedicated server from ovh at minimum if you want to host THE WHOLE STACK.
The pds? Yeah a potato pc is fine and less resource intensive than any fedi server
Caio C. G. Oliveira
Als Antwort auf Roni Rolle Laukkarinen • • •Bluesky is not to be trusted. It is just Twitter, but delayed.
#Decentralization #SelfHosting #SelfHosted #Mastodon #Fediverse #Bluesky #Servers
irelephant
Als Antwort auf Roni Rolle Laukkarinen • • •Red Dwarf
reddwarf.appTommi 🤯
Als Antwort auf Roni Rolle Laukkarinen • • •hallunke23 🇺🇦
Als Antwort auf Roni Rolle Laukkarinen • • •Well, I recently discovered that Bluesky got one step closer to decentralization:
It is now possible to set up DIDs without depending on Bluesky's services. If you look into the AT spec, you will find that there are now two types of DIDs that can be used for Bluesky: did:plc (which can only be issued by Bluesky) and did:web which essentially consist of a domain name. So an AT user of johndoe.example.com could have a DID of did:web:johndoe.example.com.
But now there are at
(1/3) @rolle #Bluesky
hallunke23 🇺🇦
Als Antwort auf hallunke23 🇺🇦 • • •least 3 parts that remain to be done:
• Alternative instances need own Relay and AppView -> should be feasable
• Alternative instances need their own servers for private messages -> This is still a problem. How are you supposed to chat with someone if another instance can't find your chat server?
• Bluesky still needs to adopt IPv6 -> This is also a problem. IPv4 is slowly heading for its end, and I wouldn't want to rely on IPv4 for Bluesky federation.
Another issue that
(2/3) @rolle #Bluesky
hallunke23 🇺🇦
Als Antwort auf hallunke23 🇺🇦 • • •popped up recently is that Bluesky allowed ICE (Terrorist Organization) to open an account on their platform which might be a good reason for deferating them.
With those 3 issues (ICE, IPv4 and centralized Chat), I think I wouldn't want to federate with Bluesky anymore.
Oh, and btw, my Mastodon account which is bridged to Bluesky, recently was banned by Bluesky. I have no clue why this happened because Bluesky won't tell me.
(3/3) @rolle #Bluesky
zivi
Als Antwort auf Roni Rolle Laukkarinen • • •Devil Doll, Esq.
Als Antwort auf Roni Rolle Laukkarinen • • •Please let your words get to @mmasnick ’s ears. A person that I admire, and have probably been banned by, for harping this point. As a non-sycophant, I just see him addicted to the numbers game, just like I saw others fall, when Twitter fell. It’s an addiction, and it demands an intervention. Individual, intelligent human minds can break the dopamine abuse cycle, with our help.
Follower count is not the dragon you need to be chasing, friends. Bluesky is owned, and it will take you down, as low as its billionaires and advertisers can gaslight you.
Only you can make the choice to stop.
Follower count is a drug. The algorithm that makes you think your influence is measured in a number, is the dopamine rush. It is designed so that you will defend it, argue for it, and never want to let it go.
It is gross, and it is making your teeth rot, when those of us who like you, see you.
Sorry to be so dramatic, but this is the current state of things, in analogy. 🤷🏼♂️
LarsNygard
Als Antwort auf Roni Rolle Laukkarinen • • •The problem with self hosting and mastodon is that only a handful of tech people actually care to host their own. Hosting an instance starts to cost serious money if you have a lot of users.
I think the best solution would be a torrent based solution that can run entirely in a browser. I've started working on such a client, but development is stale right now for resources, time and knowledge.
I've successfully synced profiles from LAN to a mobile on cellular network, so the concept should work.
If anyone wants to take a look, fork or join, let me know:
github.com/larsnygard/SnartNet
GitHub - larsnygard/SnartNet: Verified, signed, and decentralized social media and messaging.
GitHubRoni Rolle Laukkarinen
Als Antwort auf LarsNygard • • •LarsNygard
Als Antwort auf Roni Rolle Laukkarinen • • •Not everyone can host their own. Most of my friends and family can't. If you host an instance and get two thousand users, it won't be free to host. Ten thousands instances is a handful in this matter. And if you host your own instance and have a million followers?
Torrents can scale for all of this. It will also be impossible to block. No central servers to attack. No central storage of data.
Roni Rolle Laukkarinen
Als Antwort auf LarsNygard • • •gabboman the wafrn dev
Unbekannter Ursprungsbeitrag • • •Blacksky has been runing a relay for months and are preparing an appview (test on this moment)
Appview lite is a simple small app view easy to run locally too
And yes the problem theoretically is big O with the number of appviews.
But here is the thing, not every user needs a full appview with all stuff
gabboman the wafrn dev
Unbekannter Ursprungsbeitrag • • •In that case mastodon is not decentralised because you don’t have a copy of all messages, too expensive.
Untagging everyone, this has hell thread potential
gabboman the wafrn dev
Unbekannter Ursprungsbeitrag • • •I did on release week i know that for sure. Didn’t redo a fuil read appoogies.
But the thing is, the problems of big O only apply for needing the whole network. Wich not everyone needs
Else, Someone
Unbekannter Ursprungsbeitrag • • •@tokyo_0 @gabboman @cwebber
:+1: I think this is a promising line of thinking: how does atproto handle partitions and split brain situations? It's actually a feature when there's a (hierarchy of) local subnetwork(s) that can stay functional even when the network at large is partitioned. It's better yet if the synchronezation can be restored after the fact. Better still when the older or remote messages can be pruned or fetched lazily. Otherwise it's the usenet failure?
Kristian 🌒
Als Antwort auf Roni Rolle Laukkarinen • •megan mag das.
tesaguri 🦀🦝
Als Antwort auf Roni Rolle Laukkarinen • • •Rate Limits | Bluesky
docs.bsky.app