05:35 <green-big-frog> good morning

05:38 <JaniceKitten> gm

13:05 <green-big-frog> good day

13:09 <leftylink> dominikh: ah, earlier today I ran into a thing using cinch on this network. bot did a whois but the reply came back saying whois got rate limited. I think the whoised user then got stuck in limbo. a whois reply is not going to be coming from the server, but cinch is not making another req. I'll see if I can repro, may have to wait on it though

13:13 <leftylink> eh... is this server even rate-limiting whois

13:14 <leftylink> ok, maybe I'll try another. that, and I should have written down which server it was

13:18 <leftylink> uh, can't repro ._. doing lots of whoises, haven't gotten rate-limited. I'll file it away for later thinking if I can, but otherwise... meh.

17:48 <dominikh> leftylink: a) yes, whois is rate limited, on a number of networks, including freenode b) on freenode we can detect the rate limit reply, and try again. c) on other networks, we can't (cause they suck), but I believe we have a timeout on how long we'll wait, anyway. in that case, however, we won't retry, we'll throw an exception