#qi-hardware IRC log for Saturday, 2016-03-05

eintopfhttp://www.ibtimes.co.uk/meet-tomatan-wearable-robot-that-feeds-you-tomatoes-you-run-148870607:34
eintopfnice wearable07:34
whitequarkDocScrutinizer51: dunno08:10
whitequarkfreenode weirdness probably. it sometimes lands on a flaky server via the usual rotation08:10
DocScrutinizer05hmm, possible08:10
DocScrutinizer05freenode suffers from some (D)Dos at least last weekend, maybe it's still ongoing08:12
DocScrutinizer05I got quit msgs on ignore, what's the quit msg of _whitelogger?08:12
DocScrutinizer05ping timeout? that would be the usual DDoS related effect08:14
whitequarkalso on ignore08:19
whitequarkI'd look in logs but there are like fifty channels08:19
DocScrutinizer05dang, infobot's logs have only join events logged08:26
DocScrutinizer05mine as well, since my logs only log what's also displayed (lame)08:27
DocScrutinizer05even more lame: I can't set 'hide join/nick/part' per channel, only globally08:28
DocScrutinizer05let's see what xchat has08:29
DocScrutinizer51210239 * _whitelogger has quit (Excess Flood)08:33
DocScrutinizer05which is a tad strange, I dunno what it would post to flood08:34
DocScrutinizer05_whitelogger: help08:34
DocScrutinizer05_whitelogger: ?08:34
DocScrutinizer05whitequark: does whitelogger post *anything* except login and /join and services-related posts?08:51
whitequarkoh Excess Flood08:54
whitequarksigh08:54
whitequarkno, it doesn't08:54
whitequarkit only joins08:54
whitequarkand responds to pings, and requests channel lists08:55
DocScrutinizer05forget #freenode, it turned into ##defocus09:18
DocScrutinizer05I just conferred the title "poorest moderation on freenode"09:21
DocScrutinizer05staffers instead of answering a plain question like "why gets a client disconnected with `excess flood`?" they suggest /stats p and /query09:23
DocScrutinizer05while the channel explodes from trolling and noise09:24
DocScrutinizer05~+chaninfo09:43
MSG541[09:44:14] <infobot> 98/124 channels, 3882 users, 3089 unique: #debian/1536, #kde/447, #gsoc/321, #asterisk/190, #maemo/171, #wowuidev/122, #wowace/83, #cubieboard/74, #harmattan/58, #meego/54, #qi-hardware/47, #openmoko/46, #bzflag/46, #openmoko-cdevel/42, #arm-netbook/42, #maemo-ssu/40, #curseforge/38, #asterisk-dev/33, #elinux/32, #slug/26, #brlcad/25, #sc2mapster/21, #gllug/19, #debianppc/17, #n9/16, ##kierra/15, #esouidev/14, #htc-linux/13, ##leaguesunited/13, ...09:44
DocScrutinizer05~+chaninfo09:44
infobot118/125 channels, 4266 users, 3311 unique: #debian/1536, #kde/447, #gsoc/321, #asterisk/190, #maemo/171, #oe/122, #wowuidev/122, #neo900/87, #wowace/83, #utah/79, #cubieboard/74, #harmattan/58, #meego/54, #qi-hardware/47, #bzflag/46, #openmoko/46, #arm-netbook/42, #openmoko-cdevel/42, #maemo-ssu/40, #curseforge/38, #asterisk-dev/33, #elinux/32, #slug/26, #brlcad/25, #uphpu/24, #sc2mapster/21, #gllug/19, #debianppc/17, #n9/16, #nslu2-linux/15, ...09:44
DocScrutinizer05whitequark: infobot throttles chan /joins to not get kicked for excess flood. I however don't see how _whitelogger could suffer from this when it already joined all channels09:45
whitequarkDocScrutinizer05: whitelogger throttles joins too09:52
DocScrutinizer05that's what I thought09:53
whitequarkunfortunately freenode staff refused to tell me what the actual limit is09:53
whitequark"increase it if you get kicked" my ass09:53
DocScrutinizer05hehe yes09:53
whitequarkit's currently at 1 msg every 0.5s09:53
DocScrutinizer05seems they adjusted that a few times, but not during last 2 years iirc. infobot seems to do 1 join per second, see above09:54
whitequarkI used to do 1 join per second as is the default with my IRC framework09:54
whitequarkhowever, that started breaking once I got over ~30 channels (I think), with 2 commands per channel09:54
whitequarkthey have something like per-minute buckets and you have a limit of how many messages per bucket you can send09:54
whitequarkit's very obnoxious to debug09:55
whitequarkI bumped it down to 0.4 messages per second09:55
DocScrutinizer05well, I seem to recall having seen excess flood kicks when servers got DDoSed or otherwise overloaded and the client slowly sent a few posts which piled up in server's receive queue and got processed as bulk09:57
DocScrutinizer05hardly anything you can do about that, except waiting for response from one command before sending next09:58
whitequarkhmmm could be09:59
wpwrakwaiting for a response may not be enough, e.g., if the response is quick but the bucket still enforces a lower rate12:18
wpwrakbut i guess it could be good practice to avoid overrunning the server12:19
--- Sun Mar 6 201600:00

Generated by irclog2html.py 2.9.2 by Marius Gedminas - find it at mg.pov.lt!