Followup from T276299 where logmsgbot had troubles reconnecting to freenode:
- pontoon was connecting without password as logmsgbot, and given the nick has no enforce on, it will just lie around, causing tcpircbot to be unable to connect - this also caused problems with freenode's spam protection so even after ghosting the user, we had issues coming from that - any attempt to !log while the bot is reconnecting (it can take up to 2 minutes) will crash the bot.