4 ms·

DIDs are a W3C standard, not invented by Bluesky. The PLC method specifically is currently hosted by them, but they’re working on moving it, as Dan says. The m

by rmccue 1y ago

DIDs are a W3C standard, not invented by Bluesky. The PLC method specifically is currently hosted by them, but they’re working on moving it, as Dan says. The method specific ID for PLC is a hash of the genesis operation, so it’s not just an arbitrary ID that the PLC server creates.

supermatt 1y ago
The PLC DID method is absolutely created by bluesky. I never said the id they use is arbitrary, I said why not use something deterministic, so it can be handled by alternate resolvers - something that is absolutely possible while still maintaining plc integrity.
- Retr0id 1y ago
  It can be handled by alternative resolvers, like https://plc.wtf https://plc.wtf
  - supermatt 1y ago
    Non-plc resolvers. This resolver you referenced is still using plc.directory upstream.
    - Retr0id 1y ago
      I'm not sure I understand what a non-plc plc resolver would entail.
- rmccue 1y ago
  I never said it wasn’t created by Bluesky, so I’m really not sure why you’re trying to argue that I am. The point is that PLC is usable as a DID method for things that aren’t atproto. The ID is deterministic, you can reconstruct it by hashing the genesis entry in the audit log.
  - deleted 1y ago
    [deleted]