Closed tommyrot closed 10 months ago
I disagree. This forbids servers and bridges from using some characters which don't cause any issues in clients.
iirc when I was putting these restrictions together originally I was wary of bridges that allow lots of weird characters and some server impls like plexus that are less restrictive and may also allow weird chars.
A big inspiration for the denied chars here was the... rfc7700? doc submitted to IRCv3, I think it was. That doc that was focused on unicode nicknames and using PRECIS.
Align the text with RFC2812 which has a slightly more relaxed nickname syntax as RFC1459 and is the most commonly used one. I'm unsure why the modern documentation tries to be so loose and unspecific about this syntax considering it already clearly states "Servers MAY have additional implementation-specific nickname restrictions.".List channel membership prefixes in the nickname as prohibited, and advise server implementations to avoid possible detrimental ambiguity.
Should solve #203