supybot and SSL with freenode
Freenode now has SSL on all the nodes, so I figured I’d switch our supybot to use SSL via the Twisted driver. Trouble looked like this:
INFO 2010-01-30T18:49:30 Connecting to chat.freenode.net:7000. WARNING 2010-01-30T18:49:31 Error connecting to chat.freenode.net:7000: An error occurred while connecting: -9: Unknown error 18446744073709551607.
Which was confusing, to say the least. Thanks to themill in the #supybot channel, I found this bug report, which suggested that if I connect to a hostname that does not have any AAAA records, I should be fine for now. Simply changing our config from pointing to chat.freenode to chat.us.freenode did the trick. I could have also put a bare IP address in. Both are fragile, since apparently chat.us should have AAAA records, and of course a bare IP could be pulled from rotation. I’ll cross that bridge when I get there.





