Tip of the day: Did you know that users are put in the security-group known-users based on their reputation score or if they are identified to Services?Users in this group receive a number of benefits, such as being able to send more messages per minute. |
Translations:Set block/531/en
Important: if you enable this, it is good to know UnrealIRCd implements the specification in a strict way. UnrealIRCd will reject any command that contains non-UTF8, usually from very old clients that don't know UTF8 (or UTF8ONLY) or clients that are deliberately configured to send non-UTF8 data. UnrealIRCd will do no attempt to convert from non-UTF8 codepages to UTF8 (and this is not planned either) and we also do no attempt to replace non-UTF8 characters to make it valid UTF8. This is a design decision, because doing so easily leads to garbled text and it is more clear to the sender if the line is rejected in full. We also apply the restriction to all commands, not just PRIVMSG, NOTICE, TOPIC, etc. The only place we do some replacement instead of outright reject is in the registration phase. This is so a non-confirming user/client at least gets the chance to get on IRC even if e.g. their realname contains invalid UTF8 (otherwise the USER command would be rejected and they would never get online).