-
Notifications
You must be signed in to change notification settings - Fork 151
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
localparts for virtual Matrix users contain capital letters #1780
Comments
https://spec.matrix.org/v1.8/appendices/#historical-user-ids says
so that looks rather like a Conduit shortcoming. |
(I'm not affiliated with conduit just to be clear) Neither my room, nor the userIDs are "historical", they were created yesterday. If anything, the next section even explains what bridges such as this one are supposed to do |
The same issue with the Dendrit server. The problem is that during registration, the server returns a user_id that needs to be used subsequently. Moreover, according to https://spec.matrix.org/v1.8/appendices/#user-identifiers, a user_id can only contain lowercase letters (from v1.8). This means that the bridge is in direct violation of the standard v1.8. |
see matrix-org/matrix-appservice-irc#1780 Signed-off-by: strawberry <strawberry@puppygock.gay>
Matrix User Identifiers are supposed to only contain lower-case letters
https://spec.matrix.org/v1.8/appendices/#user-identifiers
However, the bridge creates Localparts with capital letters, if the IRC nick contains capital letters
https://github.com/matrix-org/matrix-appservice-irc/blob/develop/src/irc/IrcServer.ts#L535
Synapse seems to not care and just accept these User IDs.
Conduit, however only expects lower-case IDs and then bridging for IRC users with capital letters in their names fails.
see also https://gitlab.com/famedly/conduit/-/issues/388
Lowercasing all Localparts seems to work for me but I don't know about the consequences for other homeservers or existing deployments. Maybe this should be a config option
The text was updated successfully, but these errors were encountered: