Bluesky has just released their server code!

https://github.com/bluesky-social/social-app

expect it to be a frickin' mess, but they're putting it out there live

EDIT: d'oh, this is the client code! (and even says so.) server code is at: https://github.com/bluesky-social

Comparing main...1.120.0-ota-2 · bluesky-social/social-app

The Bluesky Social application for Web, iOS, and Android - Comparing main...1.120.0-ota-2 · bluesky-social/social-app

GitHub

@davidgerard Hm OK

My questions:

- How long until the first server-to-server link / federation K-clique with Bluesky itself not involved

- The (very vague, executive-level) summary they posted of their model seemed to imply a single server-like entity called the BGS had to spider the *entire* network for anyone to read follows in a coherent way at all. Is this actually true, or could an independent k-clique work with just point-to-point connections?

@mcc @davidgerard there doesn't need to be *one* BGS. there can be as many as people want. the problem is running a BGS is much more onerous than running a homeserver, so they expect there to be fewer of them
@jesopo @davidgerard but you need a BGS? Like, you either need to use bluesky's BGS or you need to set up your own? What happens without the BGS? Can you even access a post without a BGS retaining it? What's the downside of having a smaller BGS than Bluesky's?
@mcc @davidgerard without a BGS you have how mastodon currently functions. like counts, follow counts, etc are unreliable numbers
@mcc @davidgerard you can easily retrieve a specific post or all of a given user's posts without a BGS. you can resolve a handle to which PDS is responsible for their repository
@mcc @davidgerard BGSes are for aggregating data that isnt typically federated widely due to sheer volume. if you liked my post, you'd need to send the fact that you liked my post to every homeserver on the fediverse for every homeserver to be able to accurately display like counts on my post