this post was submitted on 17 Nov 2023
64 points (100.0% liked)
Technology
37711 readers
338 users here now
A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.
Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.
Subcommunities on Beehaw:
This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
That's what I wanted to ask. Last time I heard about their federation, their team were claiming the tests are underway in a sandbox or something. I wonder how that's going.
@loki @dawnerd Well, since the accounts are now moved to their specific hosts, you can use these hostnames instead of the generic one when using their protocol. The only action where you currently still need the generic bluesky host name (bsky.app) is during some account related activities.
The different hosts already talk to each other using the same protocol that is already in use for third parties who interact with bluesky (like alternate clients or custom feeds). The only thing that currently prevents "real" decentralization is the user registry.
From the outside it appears as if it all was some monolithic block. But this is only the case since the default usernames are using the
bsky.socialhostname. But in fact you can already use your own hostnames for your account, since the account is not locked to any hostname but to some unique hash. (Which is one of the advantages of their protocol and which we really should implement in the Fediverse as well to perform real account portability)