-
Notifications
You must be signed in to change notification settings - Fork 374
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.
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
[WIP] MSC1762: Support user-owned identifiers as new 3PID type #1762
base: old_master
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Overall, this proposal start on a good idea but its execution is off, mostly because it mixes/misses several independent problems which could each deserve their own MSC potentially:
- Defining a new 3PID type
- Defining how such 3PID can be validated by an Identity server within an association session
- Defining how such 3PID can be added to the Homeserver user's administrative contacts
- Defining if and how this new 3PID can be used with Homeserver authentication
@maxidor Thank you for your input! I have removed the parts relevant to the authentication flow and just mentioned a potential authentication flow as a motivation for adding DIDs as a new 3PID type. I hope to address your comments about authentication in the new MSC for authentication. |
@friedger Looking good! And definitely something that I could turn into concrete implementation. Good work! Looking forward to your other MSC. |
Signed-off-by: Friedger Müffke mail@friedger.de |
@turt2live @maxidor I have resolved the open conversations with comments. |
These require new MSCs. |
rendered