5 ms·
When he was ranting about crypto, I had assumed that Bluesky had done another silly Coin or something. Nope, this is just apparently a dislike of public keys an
by archgoon 3y ago
When he was ranting about crypto, I had assumed that Bluesky had done another silly Coin or something. Nope, this is just apparently a dislike of public keys and signing messages, which seems like a great idea for a federated protocol.
- jeroenhd 3y agoParts of the BlueSky protocol do use stuff designed for "web3" cryptocurrency stuff (https://www.w3.org/TR/did-core/ https://www.w3.org/TR/did-core/), but there's no cryptocurrency in use for the AT protocol. I'm not sure why they're even using this because the docs state that the current DID stuff is all placeholders until they can find something better.
- steveklabnik 3y ago> I'm not sure why they're even using this because the docs state that the current DID stuff is all placeholders until they can find something better. DID is there to stay, it's that the DID spec has a concept called "verification methods" https://www.w3.org/TR/did-core/#verification-methods https://www.w3.org/TR/did-core/#verification-methods. They are providing a verification method called "DID Placeholder (did:plc)", because none of the existing methods suited their goals. The idea is that if and when a better verification method appears, they can move to that, but that doesn't mean abandoning DIDs altogether.