What are you talking about? Yes, it is closed - their PDS implementation and clients are open, but the actual service that runs on bsky.app is, at present, not open source.
Without the backend that handles all of the XRPC endpoints [1] being available, BlueSky still effectively maintains centralized control over their part of the 'atmosphere'. Somebody could, of course, make an open source implementation of the app.bsky lexicon and users would only need to update their DID to point at their preferred instance, but AFAIK none exists right now.
What are you talking about? Yes, it is closed - their PDS implementation and clients are open, but the actual service that runs on bsky.app is, at present, not open source.
Without the backend that handles all of the XRPC endpoints [1] being available, BlueSky still effectively maintains centralized control over their part of the 'atmosphere'. Somebody could, of course, make an open source implementation of the app.bsky lexicon and users would only need to update their DID to point at their preferred instance, but AFAIK none exists right now.
[1]: https://docs.bsky.app/docs/api/at-protocol-xrpc-api
The endpoint mentioned in those docs you linked ( https://public.api.bsky.app/ ) points to this repo: https://github.com/bluesky-social/atproto
What is missing?