For context, all of the Bluesky app feed renderer is run off a centralized index at the moment. This article is about building your own backlink index off of Bluesky's "Jetstream" translation layer via their ATProtocol firehose.
The downsides are that the Jetstream strips all cryptography from Bluesky data, but Bluesky allows no one to hold their own keypairs so it's arguable whether that matters much at all.
Your identity must be registered at plc.directory, the central service they control, which allows them to stop clients from being able to verify your identity. I think they intend on decentralizing this, eventually.
However, you are allowed to create an identity which only uses keys you control. You are also allowed to update an existing identity and transition it to only use keys you control: https://web.plc.directory/spec/v0.1/did-plc
I've read this document before. Is there an example of someone who is doing this? Or a tutorial on how to do this? Most of my experience is my exposure to the Bluesky app which does not appear to support anything more than adding a dns handle.
3 comments
[ 3.1 ms ] story [ 18.5 ms ] threadThe downsides are that the Jetstream strips all cryptography from Bluesky data, but Bluesky allows no one to hold their own keypairs so it's arguable whether that matters much at all.
Your identity must be registered at plc.directory, the central service they control, which allows them to stop clients from being able to verify your identity. I think they intend on decentralizing this, eventually.
However, you are allowed to create an identity which only uses keys you control. You are also allowed to update an existing identity and transition it to only use keys you control: https://web.plc.directory/spec/v0.1/did-plc