You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
From what I understand, it's basically kind of like Bittorrent but for the whole web: resources stay where they are but are identified from different (decentralized) origins.
Identifiers will be stored on registries which will provide methods: https://w3c.github.io/did-spec-registries/#did-methods
I think CouchDB would be a perfect use case for implementing these decentralized identifiers. At least, it would be nice to follow the principles they suggest for the authentication (publicKey,...) and the authorization (profiles, rules,...).
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
The W3C is finalizing its proposal for decentralized identifiers: https://www.w3.org/blog/news/archives/8966
From what I understand, it's basically kind of like Bittorrent but for the whole web: resources stay where they are but are identified from different (decentralized) origins.
Identifiers will be stored on registries which will provide methods: https://w3c.github.io/did-spec-registries/#did-methods
One which drew my attention was the
peer
one by Daniel Hardman: https://identity.foundation/peer-did-method-spec/index.htmlThis method will provide authentication and authorizations.
I think CouchDB would be a perfect use case for implementing these decentralized identifiers. At least, it would be nice to follow the principles they suggest for the authentication (publicKey,...) and the authorization (profiles, rules,...).
Thoughts?
Beta Was this translation helpful? Give feedback.
All reactions