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
@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?
i have no actual idea, but i think this is literally the codebase for the one instance that exists, dunno if it includes the phone apps
i expect even setting up a second one would involve a journey of discovery into just how many bits they hastily hardcoded.
(i haven't even looked, but you know what this manner of code dump is like.)
their plan does indeed involve solving the problem of a decentralised network with a centralised entity, yes. also, bluesky is presently the only issuer of AT protocol DIDs.
@davidgerard @mcc Unless the phone app is either a wrapped web app or React Native, it’s not in there, as the code is 99% (Java|Type)script.
If the phone app is wrapped Javascript, the user experience will be far below what one expects of a mass-market mobile app.
David Gerard
mcc
acb