3 ms·
The simplicity also comes with problems, such as nickname registration in practice being implemented with bots that have administrative rights, which can lead t
by Blikkentrekker 5y ago
The simplicity also comes with problems, such as nickname registration in practice being implemented with bots that have administrative rights, which can lead to social engineering exploits and poor standardization of their interfaces, or the fact that the protocol does not seem to support sending an encoding so it relies on the gentleman's agreement that everyone use UTF-8, which works until that one user using latin-1 enters and starts sending characters that appear strange to everyone else.
It could be a little bit more complex in my opinion. Perhaps it is time for servers to start supporting an i.r.c. 2.0 protocol but otherwise allow 1.0 and 2.0 users to still communicate with each other to facilitate the migration.
- janc_ 5y agoYou mean IRCv3? It’s not all ready/implemented yet, but some of it is already in daily use. https://ircv3.net/ https://ircv3.net/ For example a server can tell the client that it only accepts UTF-8: https://ircv3.net/specs/extensions/utf8-only https://ircv3.net/specs/extensions/utf8-only
- Blikkentrekker 5y agoWell I am still sometimes seeing this user that is sending latin-1, confusing everyone else. I also wish that nicknames would not be handled via the hack of bots, as this sysem allows one to take a nickname one does not own, at least for a short while, but simply no identify it and ignore that message, and thus impersonate another user.