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
MSC4050: MXID verification #4050
base: main
Are you sure you want to change the base?
Conversation
proposals/4050-muid-verification.md
Outdated
@@ -0,0 +1,75 @@ | |||
# MSC4050: Matrix user id verification for third parties | |||
|
|||
If you want to sign up for a service that requires a guaranteed contact method, the current standard process is to send a verification code or link to the user. A similar method is used for so-called magic links. But this method is heavily flawed since it requires you to change the app, and for verification codes to copy the code. Finally, you need to delete the message. This proposal should simplify this process with minimal effort for the websites and services, from now on called third parties, using this method. |
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.
Please limit lines to ~100 characters.
@jucktnich please sign off on your changes to have this MSC be eligible for FCP later on in the process. |
- shorter lines - corrected spelling - changed muid to mxid
Private sign off has been recieved. |
|
||
## Proposal | ||
### Requesting verification | ||
The back-end of the requesring server sends a matrix event to the user. The content object has the following keys: |
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.
The backend cannot send events directly to the user, it must be done in a room. You should probably specify how the room is created and managed.
Also, you should specify what event type is used here.
rendered