I would like to give an update on "federation" on Bluesky.
-
Why does the "relay" matter? Well, because although Bluesky's claim is that moderation is "composable" in their system— that you can choose which moderators to follow— moderation decisions made by Bluesky are hard binding on systems they control. Someone blocked by Bluesky is blocked from the Bluesky appview, their content will get removed from the Bluesky PDS if they were using that. The Bluesky relay censors content that violates the data "schema"; I suspect (?) it enforces moderation also.
And this is a problem because the Bluesky moderators are *having a time*. This leads us to impetus #2 for Bluesky decentralization: A huge faction on Bluesky is leftist shitposters and trans folks who fled Twitter early under looming threat of censorship by Elon Musk. Bluesky *does not* seem to want this group in their userbase and repeated "odd" moderation decisions have reduced trust in Bluesky among this user community to zero. The death of Charlie Kirk has brought this to a breaking point.
-
And this is a problem because the Bluesky moderators are *having a time*. This leads us to impetus #2 for Bluesky decentralization: A huge faction on Bluesky is leftist shitposters and trans folks who fled Twitter early under looming threat of censorship by Elon Musk. Bluesky *does not* seem to want this group in their userbase and repeated "odd" moderation decisions have reduced trust in Bluesky among this user community to zero. The death of Charlie Kirk has brought this to a breaking point.
I don't want to talk about Charlie Kirk, so I won't. Skipping forward:
We're now seeing a "Northsky" copy of the ATP stack coming together which seeks to be a Blacksky equivalent for the 2SLGBTQIA+ community. This will probably be viable within the next couple weeks, unless it collapses in toxic queer-community infighting (which may already be beginning).
So. Three fullstack ATP instances soon. Is Bluesky "decentralized" now? Well, no, not really. Let me run through a Hypothetical Scenario.
-
I don't want to talk about Charlie Kirk, so I won't. Skipping forward:
We're now seeing a "Northsky" copy of the ATP stack coming together which seeks to be a Blacksky equivalent for the 2SLGBTQIA+ community. This will probably be viable within the next couple weeks, unless it collapses in toxic queer-community infighting (which may already be beginning).
So. Three fullstack ATP instances soon. Is Bluesky "decentralized" now? Well, no, not really. Let me run through a Hypothetical Scenario.
Imagine a hypothetical comic artist, "Gertrude". One day a hypothetical podcaster named "Louis CK" dies, and "Gertrude" posts something rude about this. Bluesky bans her. She's now deleted from the Bluesky PDS, blocked from the Bluesky relay and appview. Say, hypothetically, that virtually everyone agrees this was a bad moderation decision.
But Bluesky is decentralized, so we don't have to use the Bluesky PDS, relay, moderation service, or appview! We can Credibly Exit! Right? Right? (1/3)
-
Imagine a hypothetical comic artist, "Gertrude". One day a hypothetical podcaster named "Louis CK" dies, and "Gertrude" posts something rude about this. Bluesky bans her. She's now deleted from the Bluesky PDS, blocked from the Bluesky relay and appview. Say, hypothetically, that virtually everyone agrees this was a bad moderation decision.
But Bluesky is decentralized, so we don't have to use the Bluesky PDS, relay, moderation service, or appview! We can Credibly Exit! Right? Right? (1/3)
I (me, mcc) never trusted Bluesky, so I've been self-hosting my own PDS from the start. I've been happily using blacksky.community for the last month (since Bluesky started gating access to their appview/web frontend on clicking to agree to a new TOS that seemed to me sketchy). Hypothetically, "Gertrude" could do the same. She can join Northsky PDS, make posts through Zeppelin, and Bluesky blocks her but Blacksky just fetches the posts from her PDS for me, and I get to read them.
Right? (2/3)
-
I (me, mcc) never trusted Bluesky, so I've been self-hosting my own PDS from the start. I've been happily using blacksky.community for the last month (since Bluesky started gating access to their appview/web frontend on clicking to agree to a new TOS that seemed to me sketchy). Hypothetically, "Gertrude" could do the same. She can join Northsky PDS, make posts through Zeppelin, and Bluesky blocks her but Blacksky just fetches the posts from her PDS for me, and I get to read them.
Right? (2/3)
No. Because "Gertrude", in our hypothetical, *won't bother making those posts*. Because the vast, incredible, overwhelming majority of Bluesky users are still on the Bluesky network, and she is excommunicated. She *could* cultivate a group of followers who all use the Northsky infrastructure just so they can see her posts. But she could also cultivate a following on her Patreon. So Hypothetical Gertrude ignores Bluesky, posts to Patreon, and her Patreon posts get *shared* to Bluesky. (3/3)
-
No. Because "Gertrude", in our hypothetical, *won't bother making those posts*. Because the vast, incredible, overwhelming majority of Bluesky users are still on the Bluesky network, and she is excommunicated. She *could* cultivate a group of followers who all use the Northsky infrastructure just so they can see her posts. But she could also cultivate a following on her Patreon. So Hypothetical Gertrude ignores Bluesky, posts to Patreon, and her Patreon posts get *shared* to Bluesky. (3/3)
And that's why I say, TLDR:
- I am legitimately excited about the work being done by Blacksky Algorithms! I am using their frontend and happy with it.
- Northsky is an interesting development to watch
- If you're on a Bluesky PDS, I recommend migrating off with one of these tools https://bsky.app/profile/did:plc:ii5jchdzlmcojjw4dqczcgkh/post/3lyt6t6qfa22u
- Everything Sucks. A LOT of things would have to change at a social level for *any* entity other than Bluesky to have power or independence in the ATP ecosystem. I still don't trust Bluesky.
-
And that's why I say, TLDR:
- I am legitimately excited about the work being done by Blacksky Algorithms! I am using their frontend and happy with it.
- Northsky is an interesting development to watch
- If you're on a Bluesky PDS, I recommend migrating off with one of these tools https://bsky.app/profile/did:plc:ii5jchdzlmcojjw4dqczcgkh/post/3lyt6t6qfa22u
- Everything Sucks. A LOT of things would have to change at a social level for *any* entity other than Bluesky to have power or independence in the ATP ecosystem. I still don't trust Bluesky.
May be a stupid question but I don't know enough about ATProto, ActivityPub or Bluesky infrastructure to be sure
Would it be possible for one of those systems that is forking Bluesky to make it so they use both ATProto and ActivityPub streams so they can be on here without a bridge?
-
May be a stupid question but I don't know enough about ATProto, ActivityPub or Bluesky infrastructure to be sure
Would it be possible for one of those systems that is forking Bluesky to make it so they use both ATProto and ActivityPub streams so they can be on here without a bridge?
@gbargoud Sure. You could do that. I'm aware of a patch to the PDS (backend) software that allows it to flat out publish via ActivityPub. I haven't seen a *frontend* that merges the streams yet though.
There's also the problem that you can't reeeallly monitor *just part* of the Bluesky network. To follow part of it you're supposed to drink the entire firehose and filter out the parts you care about.
-
And that's why I say, TLDR:
- I am legitimately excited about the work being done by Blacksky Algorithms! I am using their frontend and happy with it.
- Northsky is an interesting development to watch
- If you're on a Bluesky PDS, I recommend migrating off with one of these tools https://bsky.app/profile/did:plc:ii5jchdzlmcojjw4dqczcgkh/post/3lyt6t6qfa22u
- Everything Sucks. A LOT of things would have to change at a social level for *any* entity other than Bluesky to have power or independence in the ATP ecosystem. I still don't trust Bluesky.
@mcc I'm curious, but I haven't had any time to look into this, so if you know off the top of your head, cost aside, how much work/knowledge does it take to stand up the whole stack at this point? Does Blacksky, for example, or Northsky, have their software available and documented? I think that it would be fun to try to try, but I have limited time and this isn't really my specialization.
-
@gbargoud Sure. You could do that. I'm aware of a patch to the PDS (backend) software that allows it to flat out publish via ActivityPub. I haven't seen a *frontend* that merges the streams yet though.
There's also the problem that you can't reeeallly monitor *just part* of the Bluesky network. To follow part of it you're supposed to drink the entire firehose and filter out the parts you care about.
So what I understand from this is that it would be relatively possible for BlackSky or NorthSky to add ActivityPub as a secondary protocol in ways that would likely be unfeasible to do the other way (ActivityPub instance using ATProto as a secondary protocol)
-
No. Because "Gertrude", in our hypothetical, *won't bother making those posts*. Because the vast, incredible, overwhelming majority of Bluesky users are still on the Bluesky network, and she is excommunicated. She *could* cultivate a group of followers who all use the Northsky infrastructure just so they can see her posts. But she could also cultivate a following on her Patreon. So Hypothetical Gertrude ignores Bluesky, posts to Patreon, and her Patreon posts get *shared* to Bluesky. (3/3)
@mcc For my own understanding: while the server architecture is different, the same thing could happen on the Fediverse, right? (Except portability is worse.) The only thing saving it is that mastodon.social is only the plurality of users, maybe a majority, but not the overwhelming majority?
-
@gbargoud Sure. You could do that. I'm aware of a patch to the PDS (backend) software that allows it to flat out publish via ActivityPub. I haven't seen a *frontend* that merges the streams yet though.
There's also the problem that you can't reeeallly monitor *just part* of the Bluesky network. To follow part of it you're supposed to drink the entire firehose and filter out the parts you care about.
@mcc @gbargoud It would seem like maybe this could be mitigated a bit by a (hosted) service that operates a filtered relay feed -- which drinks from the full network firehose, but lets downstream users small instances/servers subscribe to a subset view of that (based on accounts/hashtags/filters to observe).
-
@mcc I'm curious, but I haven't had any time to look into this, so if you know off the top of your head, cost aside, how much work/knowledge does it take to stand up the whole stack at this point? Does Blacksky, for example, or Northsky, have their software available and documented? I think that it would be fun to try to try, but I have limited time and this isn't really my specialization.
@alter_kaker @mcc hmm, apparently not that much knowledge is required, and the cost dropped significantly, I still don't trust any of it though
A Full-Network Relay for $34 a Month | bryan newbold (🇪🇺Europa again)
This is an update to a Summer 2024 blog post. At the time, atproto relays required a cache of the full network on local disk to validate data structures. With the Sync v1.1 updates, relays don't need all that disk I/O. What impact does that have on hosting setup and operating costs? Turns out the d...
(whtwnd.com)
-
@mcc @gbargoud It would seem like maybe this could be mitigated a bit by a (hosted) service that operates a filtered relay feed -- which drinks from the full network firehose, but lets downstream users small instances/servers subscribe to a subset view of that (based on accounts/hashtags/filters to observe).
@swetland that is pretty much the intention of the ATmosphere's design. The vision of this "composable moderation" is to allow independent "labeller" or filter services be able to process the firehose of relay traffic.
I do find the atmosphere approach interesting but its "service oriented" design seems to fight against the nature (or original intentions at least) of the host-centric internet we all try to navigate.
I think that, if reasonableness prevails, ATproto and ActivityPub will end up cross pollinating ideas and resembling each other more. Oddly enough they are both hobbled by the same problem to some degree...the dominance of a single entity hampering the true potential each has (Bluesky and Mastodon or at least Gargron's Big Instances).
One thing is pretty certain at least... The dominant platform within the fediverse driving certain communities away was a more significant factor in why Bluesky gained traction than any technical design decisions either network made.
-
The biggest movement on this front has come from the community formerly known as Black Twitter, which now has complete, viable alternative dupes of the whole stack:
Rudy wants revolution. (@rude1.blacksky.team)
blacksky.app → pds atproto.africa → relay blacksky.community → app @blackskyweb.xyz → moderation @tektite.cc → migration assembly.blacksky.community → governance blackskyweb.xyz → marketing website rsky.satnav.dev → exported data explorer https://blacksky.community
Blacksky Community (blacksky.community)
This makes intuitive sense to me! My first question, looking at ATP, is "why do free dev for this protocol, controlled by one corporation, when Fediverse is right there and is more complete?". But the black dev community, from everything I saw, tried to adopt Fediverse *first* and basically got harassed off.
@mcc "tried to adopt Fediverse first and basically got harassed off."
what does this mean, exactly? you don't have to interact with any other instance on the whole stack if you don't want to. what I'm guessing is this actually means people tried to signup for mastodon.social which is a shithole and then that got conflated with the whole fediverse -
@swetland that is pretty much the intention of the ATmosphere's design. The vision of this "composable moderation" is to allow independent "labeller" or filter services be able to process the firehose of relay traffic.
I do find the atmosphere approach interesting but its "service oriented" design seems to fight against the nature (or original intentions at least) of the host-centric internet we all try to navigate.
I think that, if reasonableness prevails, ATproto and ActivityPub will end up cross pollinating ideas and resembling each other more. Oddly enough they are both hobbled by the same problem to some degree...the dominance of a single entity hampering the true potential each has (Bluesky and Mastodon or at least Gargron's Big Instances).
One thing is pretty certain at least... The dominant platform within the fediverse driving certain communities away was a more significant factor in why Bluesky gained traction than any technical design decisions either network made.
@msh @swetland @mcc @gbargoud I think it is good to keep looking at fediverse's decentralisation too but of course there's a huge difference between the degrees to which these two are controlled by a single entity.
Why do you say this was a significant factor in driving communities away from the fediverse? It sounds surprising to me.
-
@alter_kaker @mcc hmm, apparently not that much knowledge is required, and the cost dropped significantly, I still don't trust any of it though
A Full-Network Relay for $34 a Month | bryan newbold (🇪🇺Europa again)
This is an update to a Summer 2024 blog post. At the time, atproto relays required a cache of the full network on local disk to validate data structures. With the Sync v1.1 updates, relays don't need all that disk I/O. What impact does that have on hosting setup and operating costs? Turns out the d...
(whtwnd.com)
@esoteric_programmer @alter_kaker @mcc as I understand it the cost of a relay has gone down because you can run it without keeping full account of the message history for all time and instead restrict what you have to a time-window.
Raises the question of whether that's good enough if we want real alternatives to the official company infra though.
-
And that's why I say, TLDR:
- I am legitimately excited about the work being done by Blacksky Algorithms! I am using their frontend and happy with it.
- Northsky is an interesting development to watch
- If you're on a Bluesky PDS, I recommend migrating off with one of these tools https://bsky.app/profile/did:plc:ii5jchdzlmcojjw4dqczcgkh/post/3lyt6t6qfa22u
- Everything Sucks. A LOT of things would have to change at a social level for *any* entity other than Bluesky to have power or independence in the ATP ecosystem. I still don't trust Bluesky.
@mcc what exactly is the benefit of migrating to a non bluesky PDS? I understand being on an entirely different vertical stack like Blacksky or Northsky but what does being on a PDS give you? Aren't you still (almost) entirely at bluesky's mercy?
-
@mcc For my own understanding: while the server architecture is different, the same thing could happen on the Fediverse, right? (Except portability is worse.) The only thing saving it is that mastodon.social is only the plurality of users, maybe a majority, but not the overwhelming majority?
@jrose @mcc Even the portability being better is somewhat theoretical right now because if your identity is using did:plc then you are unable to move away from did:plc and Bluesky PBC has custody of your keys... And also like people have noticed hosting your own data in a PDS does not really make you independent from their actions so the point of doing it is somewhat unclear.
-
@mcc "tried to adopt Fediverse first and basically got harassed off."
what does this mean, exactly? you don't have to interact with any other instance on the whole stack if you don't want to. what I'm guessing is this actually means people tried to signup for mastodon.social which is a shithole and then that got conflated with the whole fediverse@nullpotential @mcc people on Bluesky who have soured on fedi often complain about having been lectured about using alt text and CWs for what it's worth.
&handle=@bnewbold.net&avatar=https://cdn.bsky.app/img/avatar/plain/did:plc:44ybard66vv44zksje25o7dz/bafkreiglnysron3h2je7nf6cmvtimuaxi7xe2c7rkxitmks3mzmajnc2ou@jpeg)
