Notices where this attachment appears
-
@silverpill
I was looking at FEPs and had some thoughts:
Would it be beneficial to specify Decentralized Identifiers fields as a normally resolvable URL like https://example.com/.well-known/did:example:1234 so that software that doesn't support DIDs silently uses the URL for lookup, but software that does support DIDs treats the values as DIDs and applies special processing for them? You do something similar in FEP-ef61 with did:apkey and /.well-known/apkey except for still using the did: scheme in the field values.
The webfinger lookup in FEP-4adb made me think it would be possible to use a DHT to determine servers that have DID data. I think any such DHT needs to have support for multiple addresses on different networks (clearnet, tor, i2p, etc.).
Are there any Content Addressible DIDs? I saw a mention of urn:sha256: in FEP-cb76 but couldn't find anything on that elsewhere or a did: that used a hash function for verification. If you know of any, i would like to know.