Comment by direwolf20
5 hours ago
AT is not yours - it belongs to Blue Sky pbc. You can link your own domain to it, but the user interface belongs to Blue Sky and they will block you if they want.
5 hours ago
AT is not yours - it belongs to Blue Sky pbc. You can link your own domain to it, but the user interface belongs to Blue Sky and they will block you if they want.
This is, like, the entire problem ATProto is designed to solve.
Sure, Bluesky can block you from showing up in Bluesky the application. But if they do, you can still host your own content (as is being done here) or access it via alternative apps (like Blacksky).
This is like saying that "RSS isn't yours because Google Reader can block you."
This article has nothing to do with the Bluesky lexicon or with the bsky.app AppView.
What does “they will block you” even mean: this article is talking about hosting your data on your PDS and presenting it on your domain.
Everyone* using AT is using it through BlueSky. If you're not trying to reach those people there isn't any reason to use AT, it's just RSS with an identity centrally tied to BlueSky PBC.
The majority still use bluesky PBC's infra but that's increasingly less true.
- Blacksky has their own full appview for bluesky nowadays + relays and PDS w/ something like 60-70k users. It's small compared to the total bluesky count but it's still very sizable.
- There are countless atproto relays running independent of "big bluesky" and they only cost like 20usd/month max nowadays to run.
- Likewise it's trivial to host your data on any thirdparty PDS and scaling up a PDS community isn't terribly hard (PDS scale linearly up to like 500k users and then it scales linearly past that by just periodically launching a new PDS part of your "cluster")
- And most importantly the UX on migration is getting a lot better so it's reasonably approachable for average users.
--------
Side note but I noticed your name. Are you "the direwolf20"?
2 replies →