Issues with ASCII characters in server nicknames

General Discussion
1

Okay! This issue keeps happening again and again, no matter which service I use, but for Myteamspeak checks someone need to update the verification domain code to actually accept domains not using normal ASCII such as xn--q9jyb4c or みんな. (The xn--q9jyb4c is actually the punycode for みんな)

If you take a look, the domain exists, but it’s just not as common, even using IP:Port for now, this still needs to be considered and get updated as soon as possible.

The other bug I want to report is related to editing Server Nicknames, when it was already made and set as something… If you try to edit it again and save it shows an error message saying you can’t modify password, like what password having anything to do with Server Nicknames, seriously… :laughing:

2

I can both set and edit punycode nicknames just fine. As you already noted, all punycode domains are actually pure ascii with an optional unicode representation. I think for the purpose of nichnames supporting unicode input is valid, but in general I am really not a friend of punycode since it facilitates homograph attacks, which are otherwise easily preventable.

2 Likes
3

Working fine here on my end as well.

Can you check the console logs?

1 Like