6 ms·
We use DIDs to avoid NIHing everything (we already NIHed enough) but weren't pleased with any of the DID methods available, and are currently using did:web for
by pfraze 4y ago
We use DIDs to avoid NIHing everything (we already NIHed enough) but weren't pleased with any of the DID methods available, and are currently using did:web for self-hosters and then a registry for non-self-hosters that we're running (did:plc) which we hope to spin out to a non-profit consortium. If something else with the right properties comes along then we'll adopt it, but you're right about how much variance can exist between the did methods due to the light spec and we don't expect to support a lot of them.
- woodruffw 4y agoThanks for the explanation!
- dane-pgp 4y ago> If something else with the right properties comes along then we'll adopt it Have you looked at DID-SIOP?[0] It's based on the "Self-Issued OpenID Provider" extension[1] to OpenID Connect, to make it easier for existing OIDC relying parties to support those identities. [0] https://www.didsiop.org/ https://www.didsiop.org/ [1] https://openid.net/specs/openid-connect-self-issued-v2-1_0.html https://openid.net/specs/openid-connect-self-issued-v2-1_0.h...
- pfraze 4y agoThat must be relatively new - I read every registered spec last summer. I’ll give it a look, thanks for the pointer