4 ms·

> Currently all DID resolution goes through https://plc.directory https://plc.directory almost all. You can use did:web if you want to be more independent (but

> Currently all DID resolution goes through https://plc.directory https://plc.directory almost all. You can use did:web if you want to be more independent (but since 99.99% of people don't it's almost completely irrelevant in the big picture). > The question is if Bluesky turned completely evil today, what recourse would users and app developers have? With sufficient developer consensus, we could all agree to switch to "plc2.directory". It'd be a shitshow, but hopefully not completely fatal. > One really nice thing about it is that DIDs are opaque values, so squatting should essentially go away Zooko's triangle strikes again! https://en.wikipedia.org/wiki/Zooko%27s_triangle https://en.wikipedia.org/wiki/Zooko%27s_triangle (often expressed as a problem, but in this context it's mostly an advantage)

xeonmc 2y ago
do you know how did:web works? Documentation only describes that .well-known/atproto-did should be the DID value, but no instruction at all on where the DID document should be.
- evbogue 2y ago
  you put an identifier on a dns txt record and then Bluesky's directory checks to make sure the identifier is there. I'm not sure there is documentation on how to do this yourself though, if that was what you are asking.
  - xeonmc 2y ago
    no, that's just the identifier, I'm talking about the json document itself.
    - evbogue 2y ago
      Oh! I misunderstood the question. Navigating to my profile here: https://pdsls.dev/at/did:plc:i3gjwozl32eq3j3ejyw44hh4 https://pdsls.dev/at/did:plc:i3gjwozl32eq3j3ejyw44hh4 I clicked a link and my DID document is stored here: https://plc.directory/did:plc:i3gjwozl32eq3j3ejyw44hh4 https://plc.directory/did:plc:i3gjwozl32eq3j3ejyw44hh4 Not sure how you'd store it in other places, though that'd be pretty decentralized if you could.
      - deleted 2y ago
        [deleted]
      - deleted 2y ago
        [deleted]
- Retr0id 2y ago
  It's documented here: https://w3c-ccg.github.io/did-method-web/ https://w3c-ccg.github.io/did-method-web/ For example, here's `did:web:retr0.id` : https://retr0.id/.well-known/did.json https://retr0.id/.well-known/did.json (.well-known/atproto-did is for handle resolution, not did:web)
  - evbogue 2y ago
    So when I visit my did:plc at https://plc.directory/did:plc:i3gjwozl32eq3j3ejyw44hh4 https://plc.directory/did:plc:i3gjwozl32eq3j3ejyw44hh4 It has a reference to alsoKnownAs: ["at://evbogue.com"]. And that is _not_ my did:web. That is a reference to the dns txt record that I used to verify my account and lose the subdomain evbogue.bsky.app that I had before. If I was to upload a document like yours at https://retr0.id/.well-known/did.json https://retr0.id/.well-known/did.json How do I configure Bluesky's social application to reference my did document at https://evbogue.com/.well-known/did.json https://evbogue.com/.well-known/did.json (which doesn't exist yet) and have that be how people find my posts on Bluesky? Even if my selfhosted did document points to "https://shimeji.us-east.host.bsky.network https://shimeji.us-east.host.bsky.network" as my PDS? Could I use this to host my stuff at many PDSes? Sorry if I seemed confused. I listened the whole podcast and didn't realize alsoKnownAs is different than did:web.
    - Retr0id 2y ago
      at://evbogue.com is your handle, you don't have a did:web because you have a did:plc instead. Your DID string is the immutable root of your account's identity, it cannot be changed (the DID document it references can be updated, though) - but you can create a new account that uses a did:web instead. There aren't really any instructions on doing so (afaik) but you can do it pretty easily when you self-host a PDS. (It's no longer possible to create new accounts with a did:web on Bluesky PBC's hosted PDSes, mine is old and "grandfathered" in)
      - evbogue 2y ago
        This helps, I am less confused now. What happens if I set my handle on my selfhosted PDS as "alsoKnownAs: [evbogue.com]" and leave my handle at Bluesky PBC's PDS as "alsoKnownAs: [evbogue.com]".

xeonmc 2y ago

do you know how did:web works? Documentation only describes that .well-known/atproto-did should be the DID value, but no instruction at all on where the DID document should be.

evbogue 2y ago
you put an identifier on a dns txt record and then Bluesky's directory checks to make sure the identifier is there. I'm not sure there is documentation on how to do this yourself though, if that was what you are asking.
- xeonmc 2y ago
  no, that's just the identifier, I'm talking about the json document itself.
  - evbogue 2y ago
    Oh! I misunderstood the question. Navigating to my profile here: https://pdsls.dev/at/did:plc:i3gjwozl32eq3j3ejyw44hh4 https://pdsls.dev/at/did:plc:i3gjwozl32eq3j3ejyw44hh4 I clicked a link and my DID document is stored here: https://plc.directory/did:plc:i3gjwozl32eq3j3ejyw44hh4 https://plc.directory/did:plc:i3gjwozl32eq3j3ejyw44hh4 Not sure how you'd store it in other places, though that'd be pretty decentralized if you could.
    - deleted 2y ago
      [deleted]
    - deleted 2y ago
      [deleted]
Retr0id 2y ago
It's documented here: https://w3c-ccg.github.io/did-method-web/ https://w3c-ccg.github.io/did-method-web/ For example, here's `did:web:retr0.id` : https://retr0.id/.well-known/did.json https://retr0.id/.well-known/did.json (.well-known/atproto-did is for handle resolution, not did:web)
- evbogue 2y ago
  So when I visit my did:plc at https://plc.directory/did:plc:i3gjwozl32eq3j3ejyw44hh4 https://plc.directory/did:plc:i3gjwozl32eq3j3ejyw44hh4 It has a reference to alsoKnownAs: ["at://evbogue.com"]. And that is _not_ my did:web. That is a reference to the dns txt record that I used to verify my account and lose the subdomain evbogue.bsky.app that I had before. If I was to upload a document like yours at https://retr0.id/.well-known/did.json https://retr0.id/.well-known/did.json How do I configure Bluesky's social application to reference my did document at https://evbogue.com/.well-known/did.json https://evbogue.com/.well-known/did.json (which doesn't exist yet) and have that be how people find my posts on Bluesky? Even if my selfhosted did document points to "https://shimeji.us-east.host.bsky.network https://shimeji.us-east.host.bsky.network" as my PDS? Could I use this to host my stuff at many PDSes? Sorry if I seemed confused. I listened the whole podcast and didn't realize alsoKnownAs is different than did:web.
  - Retr0id 2y ago
    at://evbogue.com is your handle, you don't have a did:web because you have a did:plc instead. Your DID string is the immutable root of your account's identity, it cannot be changed (the DID document it references can be updated, though) - but you can create a new account that uses a did:web instead. There aren't really any instructions on doing so (afaik) but you can do it pretty easily when you self-host a PDS. (It's no longer possible to create new accounts with a did:web on Bluesky PBC's hosted PDSes, mine is old and "grandfathered" in)
    - evbogue 2y ago
      This helps, I am less confused now. What happens if I set my handle on my selfhosted PDS as "alsoKnownAs: [evbogue.com]" and leave my handle at Bluesky PBC's PDS as "alsoKnownAs: [evbogue.com]".