Bluesky users can interact with Blacksky users and vice versa unless Bluesky has applied moderation to the Blacksky user, because they are decentralized via ATproto. ~Twitter~ X users cannot interact with users on any other application, because X is not decentralized.
Yes and I find it rather egregious that you can pay (a lot) to self-host a full stack then still be locked out of the majority of the audience of an entire "decentralized" platform by a single centralized entity.
For all of the problems with ActivityPub defederation, at least with ActivityPub you have:
- Many options of places to go in the Fediverse, with a wide spread of different ideologies and approaches to moderation.
- The option to feasibly self-host your own instance that is completely independent. You can be blocked by the major instances still, so they still have the ability to moderate just the same. However, as far as I know no AP server has more than half the active users of the whole network, which is a much more robust split.
It's true that Bluesky architecture enables something like Blacksky to exist. But if there were just two independent ActivityPub hosts and one of them was many multiples the size of the other the protocol would've been declared a massive failure for good reason.
And as far as I know the Fediverse mobile apps and clients are agnostic to your instance, so the apps don't have any influence over what you're able to see. Isn't this what is expected from something that is decentralized?
I wrote this other comment that I think does well to address this misconception: https://news.ycombinator.com/item?id=48601998
> Many options of places to go in the Fediverse, with a wide spread of different ideologies and approaches to moderation.
And an account tied to exactly one of them, that is a pain to migrate if it's even possible with the ActivityPub application you use. This causes decision paralysis and dissuades most people from even considering joining.
> The option to feasibly self-host your own instance that is completely independent. You can be blocked by the major instances still, so they still have the ability to moderate just the same. However, as far as I know no AP server has more than half the active users of the whole network, which is a much more robust split.
Within what is effectively a rounding error, everyone that uses ActivityPub uses Threads. Blacksky is definitely a larger percentage of the ATProto network than mastodon.social is of the ActivityPub network.
> But if there were just two independent ActivityPub hosts and one of them was many multiples the size of the other the protocol would've been declared a massive failure for good reason.
True! Just like if there were hypothetically only two ATProto applications, that would not be very interesting. I think I've used four or five ATProto applications with my identity? Pretty cool stuff!
> And as far as I know the Fediverse mobile apps and clients are agnostic to your instance, so the apps don't have any influence over what you're able to see. Isn't this what is expected from something that is decentralized?
There is nothing in the protocol enforcing this and this expectation has been broken in the past.
https://github.com/tuskyapp/Tusky/issues/2224
This is in addition to the fact that "clients" in ActivityPub extend to the monolithic instance itself, and therefore is also broken by the very "defederation" you already mentioned!
---
I am very familiar with ActivityPub. I don't hate it. I ran multiple instances for years (one for my friends, and one for my family). ATProto is simply more flexible (allows applications to scale up to provide an experience that one would expect coming from centralized applications) and easier for non-technical people to use. And it's decentralized, which is awesome.
OK, but that raises a question. Can I do that right now? If so, I don't understand why more people are doing this. When I looked into this I definitely didn't see anything like this.
> And an account tied to exactly one of them, that is a pain to migrate if it's even possible with the ActivityPub application you use. This causes decision paralysis and dissuades most people from even considering joining.
I like the concept of W3C DIDs, but it's a little soured for me that there was no real solution to the PLC DID problem. It is, quite literally, the exact opposite of being decentralized. (IIRC they do support one of the other DID methods, but it's not default, and I couldn't figure out how.)
Which seems like a common theme. You can absolutely fix the downsides of the Fediverse, it just requires you to reduce how decentralized the network is :)
> Within what is effectively a rounding error, everyone that uses ActivityPub uses Threads. Blacksky is definitely a larger percentage of the ATProto network than mastodon.social is of the ActivityPub network.
While this is technically correct, Threads is not widely considered an instance in the Fediverse and is missing in "instance lists". Threads is less like a part of the Fediverse and more like a centralized social media service service that supports interoperability with ActivityPub.
> True! Just like if there were hypothetically only two ATProto applications, that would not be very interesting. I think I've used four or five ATProto applications with my identity? Pretty cool stuff!
This is cool but not relevant. I'm more specifically talking about Bluesky vs the Fediverse here, when referring to the protocols. Obviously there are also uses of ActivityPub that are not Mastodon/Misskey as well.
I haven't seen another ATProto application that I found interesting enough to try yet.
> There is nothing in the protocol enforcing this and this expectation has been broken in the past.
> https://github.com/tuskyapp/Tusky/issues/2224
I never suggested it was literally impossible for someone to do it... but the concept of a "Mastodon" app is inherently agnostic to the instance in a way that Bluesky's apps are not.
> This is in addition to the fact that "clients" in ActivityPub extend to the monolithic instance itself, and therefore is also broken by the very "defederation" you already mentioned!
Sure. I'm suggesting you can't actually have decentralization without the possibility of all of ActivityPub's downsides. You can't use technical means to fix the social problems with decentralization; you can only defacto centralize things.
> I am very familiar with ActivityPub. I don't hate it. I ran multiple instances for years (one for my friends, and one for my family). ATProto is simply more flexible (allows applications to scale up to provide an experience that one would expect coming from centralized applications) and easier for non-technical people to use. And it's decentralized, which is awesome.
ATProto is decentralized, at least to some extent.
Bluesky isn't really, though.
How is comparing Mastodon/the Fediverse and Bluesky unfair? Are you kind of admitting that Bluesky isn't actually practically decentralized by suggesting the AP analog of Bluesky is the largest Mastodon instance rather than the federation of them? This seems to contradict what you and much of the marketing around Bluesky says.
Where do I login to ATProto. It's not an application. It's a network of applications.
Where do I login to Bluesky? https://bsky.app
Where do I login to Mastodon.social? https://mastodon.social
People use apps, not networks of apps. Saying you don't care about the broader ATmosphere is exactly the same as saying you don't care about the broader Fediverse. That's fine, but then let's compare apps to apps instead of an app to a network. How does bsky.app compare against mastodon.social? (Actually let's not do that, because comparing a single app in a decentralized network to a single app in another decentralized network is pretty boring).
> Are you kind of admitting that Bluesky isn't actually practically decentralized
The data is meaningfully decentralized (more so than any AP app). The user identity is meaningfully decentralized (more so than any AP app). Moderation is meaningfully decentralized (similarly to AP apps). Independently developed applications are meaningfully interoperable (more so than most AP apps, especially leveraging DIDs). People can and do run their own AT infrastructure all the time. Ask questions instead of trying to pin people with gotchas based on incorrect assumptions.
I'm comparing two supposedly decentralized microblogging platforms, Bluesky and Mastodon (and compatible microblogging software.)
The things in your post don't hold up. For example, people log into apps. OK. So when I log into my email account using Thunderbird, that's decentralized. Right? Literally I am using a client to connect to some IMAP+SMTP server. Couldn't be more decentralized.
So now let's say I log into gmail.com. That's still email. Is email still decentralized with the existence of gmail? Well, it is less so than it maybe should be, but absolutely! Because I actually use Fastmail. That's what a federated network looks like.
When I log into Matrix, I still use Element regardless of homeserver. I can use any instance of Element, or install it to my machine. But still, it's Element. That's what a federated network looks like.
Not all decentralized things are federated. Some of them are, for example, peer to peer, and many other architectures.
I am ignoring the broader ATmosphere because it is not part of Bluesky the microblogging network. There are also plenty of ActivityPub applications that are not Mastodon-compatible microblogging networks, and I'm not talking about those either. I'm not talking about, for example, the network of Peertube instances that are also using ActivityPub.
I fully admit that I am not an ATProto expert, but if you're not running a Bluesky compatible AppView that speaks the Bluesky schemas, you are not participating in Bluesky, which is what I am talking about specifically.
I have used the terms "ATproto" and "ActivityPub" only in the context of Bluesky/compatible and Mastodon/compatible. That is it. If you wanted to argue about something else, it is not me pulling a gotcha on you to refuse. I just simply don't care, and you are not taking the hint. It's my damn comment thread, I know what my intended scope was. I know, too, you must know that Bluesky itself is supposed to be meaningfully decentralized, such that you can indeed run your own entire appview stack and still be a part of Bluesky, so you must understand that what I am doing is inherently an apples to apples comparison.
Yet when I log into Bluesky using a Bluesky app, what I get is the Bluesky appview and Bluesky moderation service. This is because Bluesky is substantially more centralized than the Fediverse. You can kick. You can scream. It doesn't matter. Bluesky. Is. Centralized.
> The data is meaningfully decentralized (more so than any AP app). The user identity is meaningfully decentralized (more so than any AP app). Moderation is meaningfully decentralized (similarly to AP apps). Independently developed applications are meaningfully interoperable (more so than most AP apps, especially leveraging DIDs). People can and do run their own AT infrastructure all the time. Ask questions instead of trying to pin people with gotchas based on incorrect assumptions.
With all due respect, to the extent that there is any, no thank you.
That doesn't mean other places aren't doing so. As an example - here's a list of all the relays that mirror the ATProto network: https://atproto.at/relays
There's 16 relays by my account, of varying sizes. Of course, you don't have to query a relay - you can look at the Personal Data Servers (PDSes) directly.
Speaking of - there are just over 3000 PDSes: https://blue.mackuba.eu/directory/pdses
Each of these PDSes hosts one or more accounts, and you can self-host your PDS to truly own your data up and down the stack.
There's also oodles of different applications, of which Bluesky is just one. There's:
* Germ (encrypted DMs, Signal competitor)
* Leaflet (blogs, Substack/Medium competitor)
* Semble (link collection/sharing)
* BeaconBits (location-based social media, like FourSquare)
* SkyReader (Google Reader)
* Keytrace (cryptographic identity proofs)
* Smoke Signal (social events)
* Teal.fm (Last.fm)
* Goals.garden (goal/habit tracking/accountability)
* Tangled (GitHub)
* Sifa (LinkedIn)
* BookHive (Goodreads)
* Streamplace (Twitch)
* Spark (Instagram)
* Grain (also Instagram)
* Popfeed (Trakt)
* And more, like the TikTok clone I can't remember the name of, some more blogging platforms, a (fairly dead) Hackernews clone, some games, etc.
That isn't even mentioning all the Bluesky clones like Blacksky, Eurosky, Northsky, and W.
Each of these shares the same account - the account on your PDS, which you can self-host on any computer with an internet connection. I run mine alongside my smarthome server. Because they share an account, they interop - I can subscribe to a blog on Leaflet and have it show up in my Bluesky feed.
These services can fetch data from your PDS directly, or they can look at the Relay and get the full view of the network - but frequently, they don't need to.
Bluesky went down a couple months ago and many of these services were all perfectly usable, because they used the protocol but not any infra provided by Bluesky itself. The people who couldn't access the network were the ones who relied on Bluesky to host their accounts - which is a majority of the network, sure, but in the same way that Mastodon.social is a good chunk of Mastodon's network. I was able to use Blacksky to post onto Bluesky while Bluesky was down, because I was self-hosted.
Now both Eurosky and W have launched; Eurosky is aiming to be fully independent this summer and I _think_ that W already is? W's a bit more closed-off than most of the other projects I named, going directly after Twitter-as-it-is-now and not Twitter-as-it-was (hence why they chose W to compete with X).