Comment

Comment on Great ATProto blog post on the reasoning behind their design architecture

But what about the DIDs, the things used to actually identify accounts within the ATproto ecosystem:

But Bluesky has developed its own DID method, did:plc. Today, did:plc stands for “Public Ledger of Credentials”, however it originally stood for “Placeholder DIDs”, with the hope of replacing them with something else later. The way that did:plc works is that Bluesky hosts a web service from which one can register, retrieve, and rotate keys (and other associated DID document information). However, this ledger is centrally controlled by Bluesky.

source

Sort:hotnew top

aeshna_cyanea@lemm.ee ⁨19⁩ ⁨hours⁩ ago
This is false, they support did:web which ties your identity to ownership of a DNS name (which is its own can of worms, but not PLC).

The other part is that you still have to register it to get indexed by the relay, so people can read your posts without querying your server directly (which is possible but discouraged).

source
- flamingos@feddit.uk ⁨11⁩ ⁨hours⁩ ago
  I spent a couple hours trying to create an account on pds.flamingos-cant.xyz that uses a did:web following the instructions here and the account at the end ended up with a did:plc, so IDK how you create a PDS with a did:web but it’s clearly not something they put a lot of effort into supporting.
  
  source
Little8Lost@lemmy.world ⁨1⁩ ⁨day⁩ ago
i forgot the DIDs
Oh no

source
- aeshna_cyanea@lemm.ee ⁨19⁩ ⁨hours⁩ ago
  They support did:web too if you don’t like did:plc
  
  source