Open irssibot opened 12 years ago
irssibot
commented
12 years ago This happens because the nick you want is already in use or otherwise unusable. At that point, irssi has not received information about the maximum nick length from the server yet so it ensures there is a difference in the first 9 characters (servers will truncate nicks if they are too long).
You can /set alternate_nick but that will obviously not work if that nick is not usable either.
irssibot
commented
12 years ago If this expected behavior, then it needs to be documented and listed as a feature; as right now it looks more like a bug than a feature. Furthermore Irssi should allow for a tertiary nick to be specified or possibly a method to control the permutation of the nick to avoid conflict. I spent an hour or so Googling this issue and I never stumbled upon something saying Irssi would mangle the nick in case of collision, But it also doesn't just happen on nick collision which is what I was more worried about. As I've had multiple clients up and watched this behavior. The one nick(lets say panda_pie) would not be in use and Irssi would connect as panda_pi1 despite Panda_pie not being currently used. I have solved the nick collision issue myself by adding some ghost autocommands but it would be nice if this had its own field in the config.
Thank you
9th Character in my default nick is randomly replaced with a "1" upon initial connect to servers, generally one specific server, however its happened on all the servers I frequent. Is this a "Feature" and I should just brute force the proper nick with some edits to my config file?