I would like to give an update on "federation" on Bluesky.
-
@feld @aeva @mcc I think mastodon.social's chunk of the fedi network isn't anywhere near as large as the bsky operated service is relative to its network. And there's plenty of (mostly?) healthy skepticism about and pushback against "too-big" servers.
That does need to be tempered with the reality that tiny personal or community servers have issues too (time/money to operate, migration not being truly seamless -- can't take your identity or posts with you, what server is right for me?, etc)
-
@msh @swetland @gbargoud From what I see, some communities were driven away by community issues, others (im thinking indie gamedev Twitter and comics artists) just couldn't navigate the additional friction of Mastodon's model. It wasn't all one thing. And I doubt you can chalk up the community issues to just one server, or at least, if there were one server I don't think it would be mastodon dot social (I have an instance in mind but don't feel like naming names)
In general, the bottleneck of social media is moderation. Big servers get that problem, a lot of small community servers don't. At the same time, that's when the resilience of decentralization really kicks in. By default the dominant idea of the internet and VC for the last 25 years is and was "big is beautiful" and the more followers I have the more important and valuable I am.
The fedi should and actually wants to be something different.
-
@mcc yeah have a look at Rudy's thread there, he makes that very clear. And similarly Northsky is saying well, our original plan was do PDS as Phase 1, Relay as Phase 2, and AppView as Phase 3, but now we're acceslerating Relay and AppView up and treating it all as Phase 1. My take is that everybody always took the approach of treating Bluesky PBC as a potential adversary but didn't expect them to be this adversarialy this quickly.
(If this is all an N-dimensional chess play to blow up the company to speed up the decentralization ... well as shitposting goes, that's pretty darned epic. But it's probably just horrbile comms accelerating and magnifying the tensions that were always inherent. Time will tell I guess.)
@by_caballero it's true that's a huge hole in the composable moderation model (and Rudy and others had been looking at it even before this -- https://discourse.atprotocol.community/t/how-should-we-fairly-split-the-costs-of-commons-moderation-across-producer-and-consumer-apps/122 is interesting thinking from the Eurosky perspective although doesn't yet point to any conclusions). But for this particular case they just need an appeal method for community members that allows themm to override the Bluesky mod service's app-level takedowns in their own AppView. On the deeper issue though I feel pretty vindicated because I've always said that composable moderation is interesting and valuable in some important use cases but doesn't actually solve the moderation scalability issue.
@jdp23 @mcc not adversary (directly), just forced to be less cooperative by being a US entity under meddling FCC and congress! I would also note that how bsky.app shows content to bsky users NOT applying their own blocklist/mod service is uncharted and unspecified territory. they never promised they even would and reserve the right to just not. its a hard problem! I refer to it as "federated moderation" and its totally fair they never even promised to try doing it
-
@jdp23 @mcc not adversary (directly), just forced to be less cooperative by being a US entity under meddling FCC and congress! I would also note that how bsky.app shows content to bsky users NOT applying their own blocklist/mod service is uncharted and unspecified territory. they never promised they even would and reserve the right to just not. its a hard problem! I refer to it as "federated moderation" and its totally fair they never even promised to try doing it
@jdp23 @mcc also note: there is a weird migration corner-case where the "blob store" of high-activity/high-attachment-volume accounts seems to glitch out when people move between PDS implementations. fascinating from the POV of someone who's been studying migration corner-cases in both protocols for years 🤯
https://bsky.app/profile/matthewcort.land/post/3m2nvkpx5tc2d -
So. The thread above. An update.
We finally got a live test of the "Gertrude scenario", when a popular Blacksky user got permbanned by Bluesky. I, using my own PDS and blacksky's website, can't see him or his posts ( https://blacksky.community/profile/did:plc:2aebn3xk5t63net43eeepire/post/3m2iokicegs2b ). What gives?
A lot of people claim this is because Blacksky really is using Bluesky's appview, and gave me a way to verify this looking at headers. This seems to contradict Rudy's previous claims. I've asked Rudy for clarification: https://bsky.app/profile/did:plc:2aebn3xk5t63net43eeepire/post/3m2jve23cf22m
Follow up, 2025-12-27: Rudy here confirms the Blacksky appview is still being worked on (eg: blacksky uses bluesky's appview still)
The sticking point, as he describes it, is "backfill". This alludes to the issue that makes me compare ATProto to blockchain: to get the features users expect, every node on the network must mirror the network's entire history. This is impractical, which is why bluesky is as of this moment a federated network with effectively only one node.
-
Follow up, 2025-12-27: Rudy here confirms the Blacksky appview is still being worked on (eg: blacksky uses bluesky's appview still)
The sticking point, as he describes it, is "backfill". This alludes to the issue that makes me compare ATProto to blockchain: to get the features users expect, every node on the network must mirror the network's entire history. This is impractical, which is why bluesky is as of this moment a federated network with effectively only one node.
@mcc its really weird for it to be controversial to compare ATProto to blockchain when it was an explicit selling point of the protocol before blockchains became embarrassing to develop for!!
-
Follow up, 2025-12-27: Rudy here confirms the Blacksky appview is still being worked on (eg: blacksky uses bluesky's appview still)
The sticking point, as he describes it, is "backfill". This alludes to the issue that makes me compare ATProto to blockchain: to get the features users expect, every node on the network must mirror the network's entire history. This is impractical, which is why bluesky is as of this moment a federated network with effectively only one node.
@mcc it's such a confusing aspect of the protocol. why does everything need the firehose? how do they expect it to scale??
-
@mcc it's such a confusing aspect of the protocol. why does everything need the firehose? how do they expect it to scale??
@whitequark If hypothetically, just hypothetically, we imagine that a core design requirement of the protocol was "regardless of what happens in future, it must continue to be necessary that the company Bluesky LLC exists"… the decision becomes a lot less confusing.
-
@whitequark If hypothetically, just hypothetically, we imagine that a core design requirement of the protocol was "regardless of what happens in future, it must continue to be necessary that the company Bluesky LLC exists"… the decision becomes a lot less confusing.
@whitequark (More charitably: If one considered fast, full-text search to be a highest priority feature, and it was merely *unimportant* to the designer whether a second full-service node could ever function… then one might make the decisions bluesky made here.
As for scaling, I assume when the day comes they need it to actually scale they'll either discontinue or break the externally-published linear event stream?)
-
@whitequark (More charitably: If one considered fast, full-text search to be a highest priority feature, and it was merely *unimportant* to the designer whether a second full-service node could ever function… then one might make the decisions bluesky made here.
As for scaling, I assume when the day comes they need it to actually scale they'll either discontinue or break the externally-published linear event stream?)
@mcc @whitequark reminds me of the good(*) old days when the Twitter firehose was open... Surely history would never repeat...
(*) in hindsight probably not actually.
-
@mcc it's such a confusing aspect of the protocol. why does everything need the firehose? how do they expect it to scale??
@whitequark @mcc given the history of the whole thing, I find it exceedingly likely that this is a feature rather than a bug, i.e. the entire premise of it was to capture an emerging market and user-base by riding the decentralisation buzz and tying it into blockchain/web3 (and NFTs to a lesser extent). it's also on brand - solutions that purport to empower users while really just maintaining plausible deniability for control and financial gain are the lifeblood of that class of technologist.
-
Follow up, 2025-12-27: Rudy here confirms the Blacksky appview is still being worked on (eg: blacksky uses bluesky's appview still)
The sticking point, as he describes it, is "backfill". This alludes to the issue that makes me compare ATProto to blockchain: to get the features users expect, every node on the network must mirror the network's entire history. This is impractical, which is why bluesky is as of this moment a federated network with effectively only one node.
:frogsiren: BLUESKY HAS OFFICIALLY NETSPLIT :frogsiren:
There has always been more than one Fediverse. Different instances make different moderation decisions so some instances can't see posts by some users.
There has only ever been one Bluesky because every ATProto frontend uses the same Appview.
It is January 2026 and that's no longer true; Blacksky's Appview is available for beta use and there is at least 1 user banned on Bluesky but not Blacksky. And vice versa.
Rudy wants revolution. (@rude1.blacksky.team)
Bluesky runs an appview. Blacksky runs an appview. A complete appview is a several terabytes sized database of the >18 billion follows, likes and posts of all bsky users, ever and forever. To run a different appview is to make a fork in bsky’s timeline. One has new posts from Łink. One doesn’t.
Bluesky Social (bsky.app)
-
:frogsiren: BLUESKY HAS OFFICIALLY NETSPLIT :frogsiren:
There has always been more than one Fediverse. Different instances make different moderation decisions so some instances can't see posts by some users.
There has only ever been one Bluesky because every ATProto frontend uses the same Appview.
It is January 2026 and that's no longer true; Blacksky's Appview is available for beta use and there is at least 1 user banned on Bluesky but not Blacksky. And vice versa.
Rudy wants revolution. (@rude1.blacksky.team)
Bluesky runs an appview. Blacksky runs an appview. A complete appview is a several terabytes sized database of the >18 billion follows, likes and posts of all bsky users, ever and forever. To run a different appview is to make a fork in bsky’s timeline. One has new posts from Łink. One doesn’t.
Bluesky Social (bsky.app)
@mcc I haven't thought about the term 'netsplit' in AGES.
Also: Huh. Makes one wonder what Blewski's response will be.
-
:frogsiren: BLUESKY HAS OFFICIALLY NETSPLIT :frogsiren:
There has always been more than one Fediverse. Different instances make different moderation decisions so some instances can't see posts by some users.
There has only ever been one Bluesky because every ATProto frontend uses the same Appview.
It is January 2026 and that's no longer true; Blacksky's Appview is available for beta use and there is at least 1 user banned on Bluesky but not Blacksky. And vice versa.
Rudy wants revolution. (@rude1.blacksky.team)
Bluesky runs an appview. Blacksky runs an appview. A complete appview is a several terabytes sized database of the >18 billion follows, likes and posts of all bsky users, ever and forever. To run a different appview is to make a fork in bsky’s timeline. One has new posts from Łink. One doesn’t.
Bluesky Social (bsky.app)
@mcc Would this mean that there'd be a new bridgy specifically to Blacksky?
-
@mcc Would this mean that there'd be a new bridgy specifically to Blacksky?
@mayintoronto No - Bridgy Fed supports any ATProto PDS, including the ones run by Blacksky
-
:frogsiren: BLUESKY HAS OFFICIALLY NETSPLIT :frogsiren:
There has always been more than one Fediverse. Different instances make different moderation decisions so some instances can't see posts by some users.
There has only ever been one Bluesky because every ATProto frontend uses the same Appview.
It is January 2026 and that's no longer true; Blacksky's Appview is available for beta use and there is at least 1 user banned on Bluesky but not Blacksky. And vice versa.
Rudy wants revolution. (@rude1.blacksky.team)
Bluesky runs an appview. Blacksky runs an appview. A complete appview is a several terabytes sized database of the >18 billion follows, likes and posts of all bsky users, ever and forever. To run a different appview is to make a fork in bsky’s timeline. One has new posts from Łink. One doesn’t.
Bluesky Social (bsky.app)
@mcc for us tech noobies in the audience, could you explain what does this mean?
-
:frogsiren: BLUESKY HAS OFFICIALLY NETSPLIT :frogsiren:
There has always been more than one Fediverse. Different instances make different moderation decisions so some instances can't see posts by some users.
There has only ever been one Bluesky because every ATProto frontend uses the same Appview.
It is January 2026 and that's no longer true; Blacksky's Appview is available for beta use and there is at least 1 user banned on Bluesky but not Blacksky. And vice versa.
Rudy wants revolution. (@rude1.blacksky.team)
Bluesky runs an appview. Blacksky runs an appview. A complete appview is a several terabytes sized database of the >18 billion follows, likes and posts of all bsky users, ever and forever. To run a different appview is to make a fork in bsky’s timeline. One has new posts from Łink. One doesn’t.
Bluesky Social (bsky.app)
The "portable identity" elements of Bluesky/ATProto make the netsplit just a tad odd. My account is hosted on a PDS server I run, so I'm beholden to no frontend. If I log in through the main Blacksky frontend (Bluesky appview) one user I'm following shows only an error message. Via the Staging Blacksky frontend (atproto.africa), I can see I'm following him and see his posts. I'm SO curious about the edge cases. I assume if I boost him it's hidden from the Bluesky appview. What if I reply to him?
-
The "portable identity" elements of Bluesky/ATProto make the netsplit just a tad odd. My account is hosted on a PDS server I run, so I'm beholden to no frontend. If I log in through the main Blacksky frontend (Bluesky appview) one user I'm following shows only an error message. Via the Staging Blacksky frontend (atproto.africa), I can see I'm following him and see his posts. I'm SO curious about the edge cases. I assume if I boost him it's hidden from the Bluesky appview. What if I reply to him?
@mcc When you are suspended by bluesky corp, is the ban at the app view or PDS level?
-
@mayintoronto No - Bridgy Fed supports any ATProto PDS, including the ones run by Blacksky
@quillmatiq @mayintoronto @mcc But what if I want to cancel the bridge, but only to the Nazi one? Can I do that, and advise my correspondents to migrate to BlackSky? How hard would that be?
-
@quillmatiq @mayintoronto @mcc But what if I want to cancel the bridge, but only to the Nazi one? Can I do that, and advise my correspondents to migrate to BlackSky? How hard would that be?
@martinvermeer Not today, but stay tuned for next week
