You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug The way we encode usernames, makes it impossible to losslessly decode them later: it's impossible to tell if a =201d was originally a 1d or a ”. This could result in duplicate mxids for otherwise distinct remote users, but also prevents us from turning MXids into remote IDs reliably (see matrix-org/matrix-bifrost#268).
The text was updated successfully, but these errors were encountered:
tadzik
added a commit
to matrix-org/matrix-bifrost
that referenced
this issue
Jul 30, 2021
Remote usernames with multibyte characters in them currently get encoded
into mxids in a way that may result in information loss
(see matrix-org/matrix-appservice-bridge#346).
This makes it impossible to reach some users by MXID alone, so this
makes it lookup the MXID in the user store, which contains the original,
unmangled username.
Remote usernames with multibyte characters in them currently get encoded
into mxids in a way that may result in information loss
(see matrix-org/matrix-appservice-bridge#346).
This makes it impossible to reach some users by MXID alone, so this
makes it lookup the MXID in the user store, which contains the original,
unmangled username.
tadzik
added a commit
to matrix-org/matrix-bifrost
that referenced
this issue
Jul 30, 2021
Remote usernames with multibyte characters in them currently get encoded
into mxids in a way that may result in information loss
(see matrix-org/matrix-appservice-bridge#346).
This makes it impossible to reach some users by MXID alone, so this
makes it lookup the MXID in the user store, which contains the original,
unmangled username.
FixesGH-268.
tadzik
added a commit
to matrix-org/matrix-bifrost
that referenced
this issue
Aug 2, 2021
Remote usernames with multibyte characters in them currently get encoded
into mxids in a way that may result in information loss
(see matrix-org/matrix-appservice-bridge#346).
This makes it impossible to reach some users by MXID alone, so this
makes it lookup the MXID in the user store, which contains the original,
unmangled username.
FixesGH-268.
Describe the bug
The way we encode usernames, makes it impossible to losslessly decode them later: it's impossible to tell if a
=201d
was originally a1d
or a”
. This could result in duplicate mxids for otherwise distinct remote users, but also prevents us from turning MXids into remote IDs reliably (see matrix-org/matrix-bifrost#268).The text was updated successfully, but these errors were encountered: