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.

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

Usernames cannot be changed #3212

Closed
erkinalp opened this issue May 23, 2021 · 1 comment
Closed

Usernames cannot be changed #3212

erkinalp opened this issue May 23, 2021 · 1 comment

Comments

@erkinalp
Copy link

Suggestion
As usernames are currently used in the MXIDs of @localpart:serverpart format, usernames cannot be changed. This poses a serious problem, and prevents from having multiple visible identities per user.

Spin off from #3204:

> User identifiers are user-visible
> #1228 is probably the best way to take care of room IDs

Yes, and this will be solved by not using usernames as user identifiers in the protocol as we currently do. My solution is more like 
combination of #1228 and #1769. In that model, you would have a fixed-length user PKI key in a room-version-defined schema, 
which is specific to that room, public half thereof is known to everyone in that room, and private half thereof is only known to
the clients of that specific user. Membership events, using those user keys as identifiers, would point to a particular room ID for
the profile room and exactly two event IDs from that room (one for avatar, one for user alias). With such a design, you will be able
to keep otherwise completely separate identities (but still the same user for the user's home server) for a user, without others
in the room knowing.
@erkinalp erkinalp added the improvement A suggestion for a relatively simple improvement to the protocol label May 23, 2021
@KitsuneRal KitsuneRal removed the improvement A suggestion for a relatively simple improvement to the protocol label May 23, 2021
@KitsuneRal
Copy link
Member

A subset of #1228, as you well know. Please do not open issues if you know they already are indicated elsewhere.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants