Skip to main content

Search

Items tagged with: did


lmao taking a look at #ATProtocol / #Bluesky's implementation of #DID, and I think they missed the "decentralized" part in their "placeholder" DID method.

Your domain's DNS entries just contain a (truncated) hash that then has to be resolved at plc.directory

recall that the DID method (plc) is part of the DID, so a different method (eg. web) is a different DID. to switch, you'd need to set an alsoKnownAs entry. plc only supports AT handles for alsoKnownAs.

https://github.com/bluesky-social/did-method-plc#did-resolution
DID Resolution

PLC DIDs are resolved to a DID document (JSON) by making simple HTTP GET request to the PLC server. The resolution endpoint is: https://plc.directory/:did

The PLC-specific state data (based on the most recent operation) can be fetched as a JSON object at: https://plc.directory/:did/data