79
Bluesky Continues Rapid Growth, Reaches Federation Milestone
(wedistribute.org)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 13 Oct 2023
79 points (100.0% liked)
Technology
37573 readers
228 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
According to their blog post a few days ago, they're looking at federation in H1 '24, and beginning the move to put governance of the AT Protocol that powers BlueSky to an established standards body like IEFT, though they predict that'll be a multi-year process.^[https://atproto.com/blog/2023-protocol-roadmap]
I hope they continue to move towards federation; the developers at least appear very interested in it even if the community doesn't, but I'm gonna be apprehensive about getting too excited until it actually happens.
They have a number of big promises with AT Protocol, including fully portable accounts that let you keep your content, even if your home-instance (what they call provider) goes down,^[https://github.com/bluesky-social/atproto-website/blob/516ce223e58b3a25bfa5150e00bb28533720885a/content/specs/atp.md] but it's hard to see if this is even preferable while they're still centralized.
Standards bodies is where social protocols traditionally go to die (see Jabber/XMPP).
Fully portable accounts, even fully portable communities, is something possible with Lemmy (not implemented), along with several other interesting possibilities.
How would fully portable accounts and communities be implemented do you think? My vague understanding is that users, communities and content lives at a particular URL and can’t simply change its domain.
Bluesky already allows you to use your own domain for your handle. Currently they just use a TXT record in DNS to verify it is your domain - but adding another record to specify on which instance this is hosted shouldn't be too hard.