I guess @clA_ment is Clément.
Apparently non-ASCII characters are (unfortunately) not handle correctly by Disclose and/or MusicBrainz.
Maybe the MusicBrainz user creation should forbid non-ASCII characters where we are choosing our user name?
I guess @clA_ment is Clément.
2 Likes
Quite relatedly:
3 Likes
I see 3 options to improve this.
Because it quite sucks that you don’t know when you create your MB username that you will get a lame Discourse username out of it, like this one, for example: Ù_Ø_Ù_Ø_Ø_Ù_Ø_غØ_Ù_Ù_ص
A. Make MB username normalisation for Discourse SSO more intelligent
- Turn
éintoeinstead ofÃ_ - Related to Normalise usernames for Discourse SSO?
B. Restrict MB usernames to plain /[A-Za-z0-9_-]*[A-Za-z0-9]/
- must only include numbers, letters, dashes, dots, and underscores
- must end with a letter or a number
- Related to Disallow “special” characters for new accounts
C. Allow Unicode usernames in Discourse
- now possible since 2019-05-14
unicode_usernames= true?- same
allowed_unicode_username_charactersas in MusicBrainz - No tickets yet
I would prefer option C, then A.
Because I would prefer that we don’t need to change existing MB usernames.
Related topics: discourse + sso + username
1 Like
I agree with @jesus2099. Option C would be the best solution. My username on MusicBrainz is לוכסן, but here on Discourse it was for some reason set to “user2”, which I am unable to fix.
1 Like