Trying to figure this out as in the recent threads a few people said that Bluesky was federated, but it didn't seem to actually be the case.
https://bsky.social/about/blog/02-22-2024-open-social-web in February announced that Bluesky would allow federated servers
The Bluesky documentation on the topic isn't very clear. They mention Bluesky.social a lot, as if it's supposed to be the one central server other PDS need to federate with:
Bluesky runs many PDSs. Each PDS runs as a completely separate service in the network with its own identity. They federate with the rest of the network in the exact same manner that a non-Bluesky PDS would. These PDSs have hostnames such as morel.us-east.host.bsky.network.
However, the user-facing concept for Bluesky's "PDS Service" is simply bsky.social. This is reflected in the provided subdomain that users on a Bluesky PDS have access to (i.e. their default handle suffix), as well as the hostname that they may provide at login in order to route their login request to the correct service. A user should not be expected to understand or remember the specific host that their account is on.
To enable this, we introduced a PDS Entryway service. This service is used to orchestrate account management across Bluesky PDSs and to provide an interface for interacting with bsky.social accounts.
https://docs.bsky.app/docs/advanced-guides/entryway#account-management
Self-hosting a Bluesky PDS means running your own Personal Data Server that is capable of federating with the wider Bluesky social network.
https://github.com/bluesky-social/pds?tab=readme-ov-file#what-is-the-current-status-of-federation
The custom domain name is still something else, and does not seem to require a PDS: https://bsky.social/about/blog/4-28-2023-domain-handle-tutorial
So, to come back to the title question, do people know of an example of PDS that can be used to access Bluesky without being on the main server?
@Blaze
Long winded, nuanced answer, ready your eyeballs:
It's a bit complicated, but since we're on Fediverse and at least somewhat familiar with how things work here, I'll try to explain with that comparison in mind.
On Fediverse, instances are in control of the user data directly. To "migrate" your account, you'd be switching instances and admins entirely.
BlueSky splits things up quite a bit more.
There, you can host your own "PDS" or Personal Data Server. That hosts your account and post info only.
Then, there's the "AppView". In comparison to Fediverse, these are like Lemmy, Mastodon, Mbin, etc. Right now, there's VERY few Appviews to choose from.
Then, there's the "relay". Which to Fediverse, the only thing similar is also relays, but they work differently. On BlueSky, they relay every post and interactions of all the PDS data that connect to AppViews. I do not think there's a choice on *what* is relayed, just a huge firehose. That being said, they're not optional like Fediverse. To complete the network, relays are required on ATProto and apparently could be expensive to host, so right now, it appears the only relay is hosted by BlueSky the company. Which makes things slightly centralized.
Now, that we have those definitions out of the way, this is where things get a bit muddy and a bit of purposeful corporate created confusion for purpose of selfishness is quite apparent.
Right now, there's very few AppViews. The ones I'm aware of are, BlueSky itself, Whitewind, and Frontpage.xyz.
The confusion happens because BlueSky, the company, doesn't separate the fact that accounts hosted on self-hosted PDS, aren't technically Bluesky accounts, they're ATproto accounts. Everywhere you look to login, it says "login using your BlueSky account". I can only assume they're doing this on purpose so that anyone who tries to make an Appview, host a PDS, AND a relay, can't have their own "identity" like different instances and platforms have here on Fedi.
That will confuse people and make them think *everything* is just hosted by BlueSky the company. However, as we've now established, there's definitely a separation of "Bluesky" the company, "BlueSky" the AppView that you can login to using your "BlueSky" account, which doesnt technically have to be hosted by anything related to BlueSky.
I hope this all makes sense and you can tell that *technically* things are decentralized for the most part. It's just that BlueSky is purposefully muddying their own definitions of things so that anyone that tries to build on ATproto, has a hard time making themselves known as *not* bluesky due to the way they conflate all these definitions.
Sorry for the huge post and hope it makes sense in some way.
Thanks for reading.😁👍
@fediverse
Damn. This needs to be a blog article and saved somewhere! No need to apologize. You've done a great job explaining a very technical topic in a simple and relatable way.
@mark thank you for the compliment and assurance friend.
I am always self conscious about my long winded replies because sometimes even I wouldn't wanna read a post that long.
Though, with topics like this that I'm very passionate about, I feel it's very important to lay out all the information and knowledge I have so that others can make informed decisions themselves based on the most important details.
I discuss Fediverse and networks like it, literally constantly and there's LOTS of nuances with these systems that need lots of explanations.
@fediverse
No need to be self-conscious - that's a concise account of a complicated issue, which is going to go long. Long posts become an issue when they are rambling and unfocused.
Thank you for the detailed explanation!
@Blaze no problem, friend.
I always worry if my long winded answers make sense to neurotypical people as I'm ADHD and slightly autistic.😅
So I hope it does make sense, at least even partially.
Overall, they're mostly centralized because there's *very* few relays and they're required infrastructure, but decentralized in other ways, which may or may not matter in the bigger picture because of this previous information.
@fediverse
Your answer was concise and succinct, for such a complicated topic. Thank you!
@Drunemeton you're welcome, and thank you for the reassurance, friend.🫡
@fediverse
Thanks for the explanation. Didn't realize Bluesky/AT is more like a fedi-washed version of ActivityPub rather than a real alternative ...
I'm not sure; on the one hand, I think the fact that federation has become a unique selling point in micro-blogging is indicating a positive trend; so even if people join Bluesky its good for the Fediverse. On the other hand, if federated just becomes another buzz word that means nothing at all, while places where the real innovation is happening are drowned out, the window of opportunity could just close.
@blue_berry TBH I think our biggest strength here is decentralization, but every day we're inching closer and closer to centralization here in many ways and most don't care.
Mastodon controls how 73% of users interact with Fediverse. Threads, if it fully federates will completely take that over, but then we have 2 corporate entities in charge here and there's nothing any of us are doing about it.
They will be able to enact change in AP that most other softwares can't and effectively completely change Fedi as we know it.
@fediverse
A number I've seen quoted multiple times now is ~$150 per month to host a relay (Source). Which explains why Whitewind, Smokesignal and Frontpage don't host one, they are mostly still small projects by individual talented devs, but imo if that number is true, it really doesn't seem too outlandish that someone might go for it.
Wow, that's very high, thanks!
Lemmy.world used to cost that much, but I think they downscaled a bit recently, or are at least planning to as the current growth of the userbase has slowed down.
I was actually surprised by that 150 figure when I first read it, as it is much cheaper than what the BlueSky documentation makes it sound.
It is certainly possible to collect that much in monthly donations, but then again... how do you build a loyal base of supporters for running a mostly hidden piece of infrastructure? People always complain about the instance focussed nature of the fediverse, but the ability to build communities around them and get people actually emotionally invested in their home instance is IMHO rather a strength of it. That is also why I am slightly sceptic of easy account migration tools, as it devalues the instance as yourhome base to a certain extend.
Yeah, the instance-focus aspect of the Fediverse is a good thing. You are a good example with slrpnk.net, but dbzer0, all the language/country-based instances (feddit.org, jlai.lu, aussie.zone, lemmy.ca, feddit.uk) also have their own culture and feeling. That's cool to see.
That's definitely a thing for generalist instances. I don't really think there is much of a lemm.ee culture for instance. Which is also okay, some people just want access to Lemmy without a strong instance identity.
Frontpage.xyz doesnt seem to exist do you know the correct domain?
@xnx yes! I mistyped.🫣
It's frontpage.fyi
Sorry!😅
@fediverse
@BeAware @Blaze @fediverse Yeah, so it's not a bad explanation, maybe a bit biased ;)
The key is that the architecture is very different, and there isn't a direct equivalent of instances. There are PDSes, but they do much less than Fedi instances, and they also don't directly talk to (federate with) each other. The data flows from PDSes to relay(s) to AppView(s) and to clients.
@BeAware @Blaze @fediverse There's a small number of self-hosted personal PDSes (https://blue.mackuba.eu/directory/pdses), but the system isn't really open yet to running larger ones with open signup. The Bluesky Relay doesn't currently accept more than 10 users on one PDS (with exceptions like Bridgy).
Technically anyone can run a parallel Relay and/or AppView, and hopefully that will happen, but nobody has done it yet so far (Whitewind/Frontpage are kind of different services on the same protocol).
@mackuba @Blaze @fediverse that's what I said, no? just in more words.🤷♂️
And yeah, my opinion is mixed in, but I figured that should be obvious. Maybe I should put *opinion* somewhere in there?🤔
Most of it is true, with my opinion in 2 or 3 sentences.
So its activitypub, but worse because its designed from the ground up to be difficult to federate? Bro just use twitter at this point.
That's like choosing gangrene on your foot because you can't decide which shoe to wear and tying the laces seems like a pain in the ass.
That's a wild interpretation of what they said.
Dude described a branding problem, not a technical problem.
Man this is a Bruh moment comment from me, My bad guys
@tengkuizdihar well, it's not difficult to federate, it's difficult to seperate your identity from BlueSky itself, if you're trying to create something on ATproto.
I doubt you'll see big news about a service using ATproto, the way Fedi platforms do, besides BlueSky because they really don't want you to differentiate that way.🤦♂️
@fediverse
Or maybe they do it because it would be very confusing for 99% of users to read “sign in with your atproto account” when no one knows what that is. Its a good thing theyre keeping things simple for now instead of getting the mastodon “its too complicated” issue and having non tech users not use it.
Mastodon and the activitypub culture is very much either “its too complicated” or “how do you not understand its so simple maybe you’re just dumb and shouldnt be here” energy and its why 99% of topics here are just tech and politics. Almost no artists use it and the few that use it are on mastodon.art which defederates from so many instances.
@xnx well, it doesn't really matter their reasoning when the end result is the same.
It won't become truly decentralized with these things in the way.
@fediverse
It does matter their reasoning and they can change the word when atproto is more understood. No fedi software uses “sign in with your activitypub account” either because confusing users is a bad thing.
I personally like that theyre doing things to appeal to non tech users because i dont want to use a service no one uses. Its why i dont use any activitypub service for my art because theres no artists using activitypub but bluesky has a huge art community even though they still dont have video
@xnx to each their own.
The anarchist in me doesn't feel right having a corporate overlord who can :yeet: me from existence whenever they choose.🤷♂️
That's not important to everyone and that's fine. We are all different.
@fediverse
@BeAware @xnx @fediverse I'm with you on this one, I think it's important to eventually have non-Bluesky-owned infrastructure alternatives even if a lot of people don't care about it… I hope we'll get there
You can be yeeted here too? And as time goes on people can run their own relays making it impossible for the bluesky team to ban you
@xnx I certainly cannot. I'm on my own instance and there's like 20,000 instances. Someone can *attempt* to yeet me. They'll have a hell of a time getting admin privileges to all instances though.
@fediverse
@xnx @BeAware
I believe they're planning to change that into something like "Sign in with your ATmosphere account." (hopefully)
I could be wrong, but the term "ATmosphere" has been used widely by non-technical users.
Where do you see atmosphere?
@xnx @ccoremapd @fediverse It was an unofficial term until recently, but they seem to be adopting it a bit more officially right now, see e.g. here https://atproto.com and in the "Glossary" section. But I think this will stay a developer-targeted term, I don't think they'll use it in such context as "Sign in with your ATmosphere account" (but they don't really dictate to third parties right now how they should phrase this on their side).