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

nickname i18n using a variation of punycode #2

Closed
sdaugherty opened this issue Jul 28, 2016 · 2 comments
Closed

nickname i18n using a variation of punycode #2

sdaugherty opened this issue Jul 28, 2016 · 2 comments

Comments

@sdaugherty
Copy link

Was thinking about internationalization and nicknames, and thought about a possible scheme to implement nickname internationalization in a way that does not break clients or servers, nor does it
invite abuse.

Internationalized nicknames could be represented in ASCII using a variation on Punycode (which is used for internationalization of domain names).

The ASCII representation would be used for all IRC commands, and it would be recommended for clients to show and accept both the "proper" UTF-8 representation and the ASCII representation.

Thoughts?

@sdaugherty
Copy link
Author

sdaugherty commented Jul 28, 2016

Zarthus points out that RFC7700 covers exactly this,, however, some implementation details specific to IRC probably need to be spelled out so as not to enable abuse.

Specifically, it must always be possible for a user who can only input characters in an ASCII character set to quickly and unambiguously issue commands that require the user's full nickname. (/kick. /whois, etc)

@jwheare
Copy link
Member

jwheare commented Jul 28, 2016

Dupe of ircv3/ircv3-specifications#259

@jwheare jwheare closed this as completed Jul 28, 2016
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