indigo

Thanks for the response Nora. Because of your blog post I went through the process of setting up a did:web account myself this afternoon, and it was painful. Eg, I found a bug in our Go SDK causing that "deactivated" error (https://github.com/bluesky-social/indigo/pull/1281). I kept notes and will try to get out a blog post and update to 'goat' soon. We've also been making progress on the architecture and governance of the PLC system. I don't know if those will assuage all concerns with that system immediately, but I do think they are meaningful steps in reducing operational dependency on Bluesky PBC.

the backend (the AppView) can be found here: https://github.com/bluesky-social/atproto/tree/main/packages... there are various supporting services written in Go as well https://github.com/bluesky-social/indigo

> The relay isn’t open-source either and I’m not aware of any independent ones running; at minimum it would be very expensive to do so. https://github.com/bluesky-social/indigo/tree/main/cmd/bigsk... > These are some informal notes on setting up a full-network atproto Relay, using the bigsky relay software developed by Bluesky. This is the same software we run ourselves at https://bsky.network. https://whtwnd.com/bnewbold.net/3kwzl7tye6u2y The post goes a bit into costs as well.

Why would you think it's not open source? The reference implementation: https://github.com/bluesky-social/atproto Complete React Native Android/iOS/Web app: https://github.com/bluesky-social/social-app Go libraries: https://github.com/bluesky-social/indigo PDS distribution: https://github.com/bluesky-social/pds All dual MIT / Apache 2.0 licensed.

It's still a notable bit of centralization present in the protocol - from the documentation presented, it's obvious that moreso than any other "node" in the software, if the relay breaks, that entire chunk of the network stops working. A PDS, a labeler or a feed generator vanishing means very little for the network on the whole, while the relay vanishing causes everything to fall apart. Similarly, the fact Bluesky is offering a PDS implementation for self-hosting[0] but not a relay[1] tells me that hosting a relay is more than a non-trivial matter, although I'd love to be proven wrong there. [0]: https://github.com/bluesky-social/pds [1]: Well, outside of literally deploying Blueskys own implementation - https://github.com/bluesky-social/indigo/tree/main/cmd/bigsk... .

Yup, you could. Although connecting your own PDS hosts to the Bluesky production network won't be possible for a little while longer. Creating custom algorithms (feeds) is already possible, as it participating in the developer sandbox network, including PDS hosting. The architecture is explained briefly here: https://blueskyweb.xyz/blog/5-5-2023-federation-architecture Code/docs are here: 1. AT Protocol (atproto) is documented here: https://atproto.com 2. App Web/Android/iOS app: https://github.com/bluesky-social/social-app 3. API (AppView) and PDS (Personal Data Server): https://github.com/bluesky-social/atproto 4. The Relay (formerly BGS) https://github.com/bluesky-social/indigo 5. Custom algorithm (Feed Generator): https://github.com/bluesky-social/feed-generator 6. Sandbox PDS distribution: https://github.com/bluesky-social/pds/blob/m

If I host my own identity server can I bypass the need for an invite? Maybe it's this? https://github.com/bluesky-social/indigo