Post

Eric Vicenti
@eric.vicenti.net

This feels like disinformation to me. Bluesky uses did:plc which is highly centralized I’d love to be proven wrong, because the world desperately needs a decentralized identity system I’m really hoping that Bluesky sees the light and allows users to actually own their keys

chrisb@boscolo.co

When a platform for social engagement grows large enough, the identity used on that platform becomes a standard for global communication. Telephone network gave us phone numbers. Internet v1 gave us email addresses. Bluesky (AT Protocol) gives Decentralized Identities (DID) 🧵

Boris
@bmann.ca

They do own their keys (you can rotate them and add backups) - PLC holds the identifier and log of actions - did:plc is not a key and isn’t used for signing. The intent is for the (currently centrally hosted) plc directory to be spun out into a separate entity & collaboratively governed.

Eric Vicenti
@eric.vicenti.net

But.. who owns the identity? Bluesky does, because they can re-key people. It's definitely an admirable intent to decentralize one day. But clearly people are thinking Bluesky already offers sovereign identities. Hence the "disinformation"

Boris
@bmann.ca

No they can’t rekey people. But @boscolo.co who you thought was doing misinformation can fight his own battles.

0 reposts0 likes

Eric Vicenti
@eric.vicenti.net

Sorry for bothering you with this, Boris 😅 I was pretty sure that the bluesky PDS holds a rotation key, as discussed here: github.com/bluesky-soci... Also I'm not sure how the "lost password" workflow (email validation) would possibly work if the bsky service can't rekey my identity

github.comHow to edit `did:plc` rotation keys · bluesky-social atproto · Discussion #3366I have migrated my Bluesky handle rekmarks.com to my own PDS. I am trying to replace one of its rotation keys. Here's what I observe: I check the rotation keys returned by com.atproto.identity.getR...