I get that the Mastodon folks are out of date and don't realize how much development has happened on ATproto in the last year, but it makes them all sound silly when they repeat things as if it were still 2023.

@[email protected]

That's a deflection again. Nobody doubts that technically both #activitypub and #atproto support decentralization.

But the point is that *in practice* basically all #bluesky users are concentrated on infrastructure of a single company under US jurisdiction, while #mastodon users are distributed over many servers in many jurisdictions all over the world.

The consequences can be seen with Mississippi.

https://mastodon.social/@ikuturso/115124768664434731

https://mastodon.social/@mastodonmigra[email protected]/115125132980066617

@folkerschamel @mmasnick.bsky.social

The technique Mike Masnick employs is to ignore the substance of the critique. #Bluesky may technically be capable of decentralization, but in practice it is still highly centralized. Instead, he repeats the mantra there are some examples of decentralization.

Stipulated Mike.

Now move on to addressing the reality that for all intents and purposes, which is what matters for these censorship issues, it is centralized.

https://arewedecentralizedyet.online/

@mastodonmigration @folkerschamel @[email protected] I just saw this thanks to folker posting it (misleadingly) on Bluesky. As I've said repeatedly, that chart is not only meaningless, but it's misleading. If it included Threads on the AP side, then Mastodon would look way way worse. But that's silly. If it counted Threads would that suddenly make Mastodon less decentralized? Of course not. That's why that chart is completely meaningless.

@mmasnick @folkerschamel @mmasnick.bsky.social

This is a specious argument, and does not deserve a serious response. Please stop misrepresenting the current degree of centralized concentration of Bluesky PBC on AT Protocol. You are in a perfect position to advocate for actual meaningful decentralization, but instead continue to misrepresent the current overwhelming dominance of Bluesky PBC.

1/

@mmasnick @folkerschamel @mmasnick.bsky.social

Rather than making false and misleading arguments you could instead stipulate that the overwhelming dominance Bluesky PBC does currently make AT Protocol a defacto centralized network, but the company recognizes this and are taking specific steps to address it. AT Protocol is designed to facilitate decentralization and list what steps are being taken, against what metrics to achieve real decentralization.

2/

@mmasnick @folkerschamel @mmasnick.bsky.social

Specifically, what is the company doing to enable independent instances and provide the type of choice your marketing ballyhoos? What are your goals for achieving a meaningful percentage of the AT Protocol network users NOT being Bluesky PBC users? What programs are you sponsoring to achieve these ends? Are you serious about these goals?

3/

@mastodonmigration @folkerschamel @[email protected] the only one misrepresenting stuff is you, unfortunately. Bluesky has done a ton of stuff to enable actual decentralization, all of which we're starting to see come into effect as we speak and all you guys do is lie about it.

But you still ignore my point. If we (properly) counted Threads as part of the fediverse, would that make the fediverse less decentralized?

Answer please.

@mmasnick @folkerschamel @mmasnick.bsky.social

@mmasnick

@ricci did answer your question very specifically here:

https://discuss.systems/@ricci/115171236116610436

There was also more in depth discussion of the issue. It may be that you are not seeing the entire thread across the bridge.

Rob Ricci (@[email protected])

Hi, creator of the chart here. I'm disappointed to see people using it as a way to try to dunk on or bully various protocols. @[email protected] and @[email protected] if you're going to share the screenshot I'd appreciate if you'd update it to the latest version, which is slightly clearer that the gauge is showing the HHI, a measure from economics that captures market concentration - not just users on the biggest servers, as are in the table. It also now has git forges as well to show that the point is to compare many forms of decentralized networks (I'm working on getting data for more); it's not just there to dunk on atproto. The heading that you cut off also (tries) to make it clear that it's showing user data, eg. it's not attempting to show things like moderation or feeds, where Bluesky likely has more diversity. @[email protected] I'm working on getting Threads data in here; Meta doesn't make that data available via the standard APIs so it's not in my data sources. The most recent estimate I can find for the number of Threads users who have opted in to the fediverse is around 25k-50k as of Dec 2024: https://fediversereport.com/why-is-meta-adding-fediverse-interoperability-to-threads/ . So while I do want to get it in here for completeness, Threads doesn't really move the needle. I do want criticism of this data, the way that it's presented, and other ways I can show the decentralization that does exist in the deployment of the AT Protocol ecosystem. I've made several changes in response to feedback, some of it from Bluesky team members - in fact creating this dashboard in the first place and the way I'm getting ATProto data was the idea of a Bluesky team member. (He didn't suggest the specific use of HHI, however) But that said, this specific criticism is off-base: if we add the number of Threads users who are actually fediverse users, nothing changes. If we were to add in the 400M MAU that Threads claims to have, but who are not fediverse users, that would be kind of like asking why we didn't put Facebook on the AT Protocol side: not a meaningful thing to do. And, if, hypothetically, all those 400M Threads users *were* fediverse users, that would, in fact, centralize a *lot* of power in Meta's hands - not all of it, but a ton. We all know how networks work. This is one reason (the other being the, you know, everything, about Meta) that fediverse folks were quite worried about Thread's entrance. My goal in building this thing is so that we can watch the deployments, nothing more nothing less. Hopefully, blacksky grows and we see that reflected in the Atmosphere side. I've seen your recent post about a bunch of AT Protocol development that is not from Bluesky. Great. The point of this chart is to watch that grow. There are plenty of anecdotes, those are good and necessary. Data is part of the story too, and that's what I'm trying to provide here. Speaking of which, I would very much like to get data from Bluesky regarding the use of third-party feeds and moderation tools. As far as I can tell, I can only get this from the Appview, and I can't find any indication it's exposed yet. I hope that you understand that I'm trying to provide a valuable data source here, and if you do, I'd appreciate if you could put me in touch with the right person to ask about this. And finally, thanks for One Billion Users, I had a great game with my spouse last night :)

discuss.systems

@mastodonmigration @folkerschamel @[email protected] @ricci No @ricci is making a different (totally valid!) point. I am saying IF he included Threads, would you then say that Mastodon is less decentralized?

That's the only question I am asking. If your answer is yes, I would be confused. If your answer is no, you are admitting that this is not a measure of decentralization.

Which is it?

@mmasnick @mastodonmigration @folkerschamel @mmasnick.bsky.social I think a better question here, Mike is *if* Threads had 400M users who were active on the fediverse, would the fediverse be more centralized?

I would say yes.

@mmasnick @mastodonmigration @folkerschamel @mmasnick.bsky.social Of course, it does not. It has like 50k.

@ricci @mmasnick @mastodonmigration @[email protected]

But even if all of #threads would be part of the #fediverse and make the fediverse practically centralized, it wouldn't change the the factual situation that
a) #mastodon is #decentralized,
b) #bluesky as being controlled by a single company is completely centralized, and
c) #atmosphere as being dominated by #bluesky is practically centralized.

@folkerschamel @ricci @mastodonmigration @[email protected] the thing is, multiple people have explained to you, repeatedly, that your point "b" is incorrect. ATproto/Atmosphere is NOT controlled by a single company. Why you keep repeating that lie is the part that bugs me.

@mmasnick @folkerschamel @mastodonmigration @mmasnick.bsky.social

I am not a fan of this guy's style of engagement but I do feel the need to point out that his point b literally does not say what your reply says it does.

@ricci @mmasnick @folkerschamel @mmasnick.bsky.social

Concur. His point b specifically references Bluesky not AT Protocol.

@mastodonmigration @mmasnick @folkerschamel @mmasnick.bsky.social

Okay to play devil's advocate for my own point :) there are things you could plausibly say are part of bluesky but not the atmosphere that are not controlled by the company, namely third party labelers and feed generators.

@ricci @mmasnick @folkerschamel @mmasnick.bsky.social

Not endorsing point b, just pointing out it references Bluesky and not AT Protocol. In general the conflation of the two leads to a lot of confusion and ambiguous statements. Think that it is much more useful to look at the overall networks and the relative percentage ownership of the various distributed components, as the Rob Ricci analysis does.

1/

@ricci @mmasnick @folkerschamel @mmasnick.bsky.social

Mike Masnick seems to suggest that it is not the current state of distributed ownership, but some measure of the ease of people moving to other independent nodes on the network. It is hard to see how any metrics could capture this, since it would necessarily involve the creation and rapid expansion of very significant server resources that do not currently exist. This just doesn't seem feasible.

2/

@ricci @mmasnick @folkerschamel @mmasnick.bsky.social

So, returning to Rob Ricci's point that the current measure, while not dispositive on the subject of potential decentralizability is a useful thing to know. And further, that it can give insight into the ability of the independent network resources to respond to a 'mass migration' event.

3/

@mastodonmigration @mmasnick @folkerschamel @mmasnick.bsky.social

I'm not too worried about *potential* for *infrastructure* to scale: at a technical level we've been putting a lot of engineering resources into that sort of thing for a long time now, and what I've seen of the various atproto implementations suggests to me that it's reasonable to believe they can be operated at scale by groups other than bluesky-the-company.

Money I'm not super worried about either. Sure anyone wanting to absorb a mass migration would need to get a bunch of money quickly, but we have existence proof that the "please donate to your server" model, while it has its flaws, is remarkably stable.

But the human capital, that's the hard part. If all of the knowledge and hard-won experience about how to actually run a social network is locked up in one organization, or a few, that takes a long time to build up. The distribution across *some* measure of independent services is a proxy for how centralized or distributed that human capital is. This is why I really wish I could get data re: labelers and feed generators, as that's one place where I do think Bluesky is probably building up some distributed expertise.

@ricci @mmasnick @folkerschamel @mmasnick.bsky.social

Agree with all this. We don't really need to isolate the different components of what basically comes down to inertia.

Edit: Which is also why getting things spun up from rest is very different from accelerating them once they are up and spinning.