Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[WIP] MSC1781: Proposal for associations for DIDs and DID names #1781

Draft
wants to merge 1 commit into
base: old_master
Choose a base branch
from
Draft

[WIP] MSC1781: Proposal for associations for DIDs and DID names #1781

wants to merge 1 commit into from

Conversation

friedger
Copy link

@friedger friedger commented Jan 7, 2019 •
edited
Loading

@friedger friedger changed the title Proposal for associations for DIDs and DID names MSC1781: Proposal for associations for DIDs and DID names Jan 7, 2019
@friedger friedger changed the title MSC1781: Proposal for associations for DIDs and DID names [WIP] MSC1781: Proposal for associations for DIDs and DID names Jan 7, 2019
@turt2live turt2live added the proposal A matrix spec change proposal label Jan 29, 2019
@bmiller59 bmiller59 mentioned this pull request Mar 8, 2020
Draft
@turt2live turt2live added the kind:feature MSC for not-core and not-maintenance stuff label Apr 20, 2020
@turt2live turt2live marked this pull request as draft April 8, 2021 23:36
@turt2live turt2live added the needs-implementation This MSC does not have a qualifying implementation for the SCT to review. The MSC cannot enter FCP. label Jun 8, 2021
@izN8nu6RyeneG5XnBoBgyRMVGH6H43WF
Copy link

W3C recently approved a recommendation for Decentralized Identifiers. Human-Friendly Identifiers are explicitly out of scope of these recommendations. The DID spec notes DNS-DID, but that draft has expired. Solutions to this are forthcoming.

In light of #2787, I have two thoughts:

  1. DIDs proper should be used as the "canonical" identifier that is "portable" in the sense of MSC2787: Portable Identities #2787. Meanwhile, human-readable aliases should either be handled by the client, which can configure its own DID mapping solution, or this should be integrated into the Matrix Identity Service API.
  2. Maybe this MSC should be put on hold until W3C recommends a solution for mapping human-readable identifiers to DIDs. In the meantime, clients can simply use the DID proper for identification.

This was referenced Dec 13, 2022
Draft
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
kind:feature MSC for not-core and not-maintenance stuff needs-implementation This MSC does not have a qualifying implementation for the SCT to review. The MSC cannot enter FCP. proposal A matrix spec change proposal
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
3 participants
@friedger @izN8nu6RyeneG5XnBoBgyRMVGH6H43WF @turt2live