2016-03-05 01:15 wolfspraul has joined #qi-hardware
2016-03-05 01:16 wolfspraul has quit [Client Quit]
2016-03-05 01:37 wolfspraul has joined #qi-hardware
2016-03-05 01:39 wolfspraul has quit [Client Quit]
2016-03-05 01:44 sandeepkr has quit [Ping timeout: 244 seconds]
2016-03-05 01:52 sandeepkr has joined #qi-hardware
2016-03-05 02:19 xiangfu has joined #qi-hardware
2016-03-05 02:42 xiangfu has quit [Ping timeout: 244 seconds]
2016-03-05 02:48 xiangfu has joined #qi-hardware
2016-03-05 03:43 xiangfu has quit [Remote host closed the connection]
2016-03-05 03:51 wildlander has quit [Quit: Saliendo]
2016-03-05 04:49 DocScrutinizer05 has quit [Disconnected by services]
2016-03-05 04:49 DocScrutinizer05 has joined #qi-hardware
2016-03-05 07:34 <eintopf> http://www.ibtimes.co.uk/meet-tomatan-wearable-robot-that-feeds-you-tomatoes-you-run-1488706
2016-03-05 07:34 <eintopf> nice wearable
2016-03-05 08:10 <whitequark> DocScrutinizer51: dunno
2016-03-05 08:10 <whitequark> freenode weirdness probably. it sometimes lands on a flaky server via the usual rotation
2016-03-05 08:10 <DocScrutinizer05> hmm, possible
2016-03-05 08:12 <DocScrutinizer05> freenode suffers from some (D)Dos at least last weekend, maybe it's still ongoing
2016-03-05 08:12 <DocScrutinizer05> I got quit msgs on ignore, what's the quit msg of _whitelogger?
2016-03-05 08:14 <DocScrutinizer05> ping timeout? that would be the usual DDoS related effect
2016-03-05 08:19 <whitequark> also on ignore
2016-03-05 08:19 <whitequark> I'd look in logs but there are like fifty channels
2016-03-05 08:26 <DocScrutinizer05> dang, infobot's logs have only join events logged
2016-03-05 08:27 <DocScrutinizer05> mine as well, since my logs only log what's also displayed (lame)
2016-03-05 08:28 <DocScrutinizer05> even more lame: I can't set 'hide join/nick/part' per channel, only globally
2016-03-05 08:29 <DocScrutinizer05> let's see what xchat has
2016-03-05 08:33 <DocScrutinizer51> 210239 * _whitelogger has quit (Excess Flood)
2016-03-05 08:34 <DocScrutinizer05> which is a tad strange, I dunno what it would post to flood
2016-03-05 08:34 <DocScrutinizer05> _whitelogger: help
2016-03-05 08:34 <DocScrutinizer05> _whitelogger: ?
2016-03-05 08:38 sandeepkr has quit [Ping timeout: 244 seconds]
2016-03-05 08:51 <DocScrutinizer05> whitequark: does whitelogger post *anything* except login and /join and services-related posts?
2016-03-05 08:54 <whitequark> oh Excess Flood
2016-03-05 08:54 <whitequark> sigh
2016-03-05 08:54 <whitequark> no, it doesn't
2016-03-05 08:54 <whitequark> it only joins
2016-03-05 08:55 <whitequark> and responds to pings, and requests channel lists
2016-03-05 08:57 sandeepkr has joined #qi-hardware
2016-03-05 08:58 sandeepkr has quit [Max SendQ exceeded]
2016-03-05 09:11 mazzoo has quit [Ping timeout: 260 seconds]
2016-03-05 09:11 mazzoo has joined #qi-hardware
2016-03-05 09:18 <DocScrutinizer05> forget #freenode, it turned into ##defocus
2016-03-05 09:21 <DocScrutinizer05> I just conferred the title "poorest moderation on freenode"
2016-03-05 09:23 <DocScrutinizer05> staffers instead of answering a plain question like "why gets a client disconnected with `excess flood`?" they suggest /stats p and /query
2016-03-05 09:24 <DocScrutinizer05> while the channel explodes from trolling and noise
2016-03-05 09:24 mazzoo has quit [Ping timeout: 264 seconds]
2016-03-05 09:39 infobot has quit [Ping timeout: 246 seconds]
2016-03-05 09:43 <DocScrutinizer05> ~+chaninfo
2016-03-05 09:44 infobot has joined #qi-hardware
2016-03-05 09:44 <DocScrutinizer05> ~+chaninfo
2016-03-05 09:44 <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, ...
2016-03-05 09:44 <DocScrutinizer05> ~+chaninfo
2016-03-05 09:44 <infobot> 118/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, ...
2016-03-05 09:45 <DocScrutinizer05> whitequark: 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 channels
2016-03-05 09:48 mazzoo has joined #qi-hardware
2016-03-05 09:52 <whitequark> DocScrutinizer05: whitelogger throttles joins too
2016-03-05 09:53 <DocScrutinizer05> that's what I thought
2016-03-05 09:53 <whitequark> unfortunately freenode staff refused to tell me what the actual limit is
2016-03-05 09:53 <whitequark> "increase it if you get kicked" my ass
2016-03-05 09:53 <DocScrutinizer05> hehe yes
2016-03-05 09:53 <whitequark> it's currently at 1 msg every 0.5s
2016-03-05 09:54 <DocScrutinizer05> seems they adjusted that a few times, but not during last 2 years iirc. infobot seems to do 1 join per second, see above
2016-03-05 09:54 <whitequark> I used to do 1 join per second as is the default with my IRC framework
2016-03-05 09:54 <whitequark> however, that started breaking once I got over ~30 channels (I think), with 2 commands per channel
2016-03-05 09:54 <whitequark> they have something like per-minute buckets and you have a limit of how many messages per bucket you can send
2016-03-05 09:55 <whitequark> it's very obnoxious to debug
2016-03-05 09:55 <whitequark> I bumped it down to 0.4 messages per second
2016-03-05 09:57 <DocScrutinizer05> well, 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 bulk
2016-03-05 09:58 <DocScrutinizer05> hardly anything you can do about that, except waiting for response from one command before sending next
2016-03-05 09:59 <whitequark> hmmm could be
2016-03-05 10:42 xiangfu has joined #qi-hardware
2016-03-05 11:13 xiangfu has quit [Ping timeout: 260 seconds]
2016-03-05 11:19 sandeepkr has joined #qi-hardware
2016-03-05 12:11 FDCX has quit [Ping timeout: 250 seconds]
2016-03-05 12:18 <wpwrak> waiting for a response may not be enough, e.g., if the response is quick but the bucket still enforces a lower rate
2016-03-05 12:19 <wpwrak> but i guess it could be good practice to avoid overrunning the server
2016-03-05 12:24 FDCX has joined #qi-hardware
2016-03-05 12:31 FDCX has quit [Ping timeout: 264 seconds]
2016-03-05 12:43 FDCX has joined #qi-hardware
2016-03-05 12:43 aimg has joined #qi-hardware
2016-03-05 13:33 rjeffries has quit [Ping timeout: 248 seconds]
2016-03-05 14:30 xiangfu has joined #qi-hardware
2016-03-05 14:59 xiangfu has quit [Ping timeout: 268 seconds]
2016-03-05 15:00 xiangfu has joined #qi-hardware
2016-03-05 15:12 pcercuei has joined #qi-hardware
2016-03-05 15:36 xiangfu has quit [Quit: leaving]
2016-03-05 16:30 dandon has joined #qi-hardware
2016-03-05 17:21 anandas has joined #qi-hardware
2016-03-05 17:24 anandas has left #qi-hardware [#qi-hardware]
2016-03-05 18:19 pcercuei has quit [Ping timeout: 276 seconds]
2016-03-05 18:19 pcercuei has joined #qi-hardware
2016-03-05 18:26 pcercuei has quit [Ping timeout: 248 seconds]
2016-03-05 18:28 pcercuei has joined #qi-hardware
2016-03-05 18:33 pcercuei has quit [Ping timeout: 246 seconds]
2016-03-05 18:42 aimg has quit [Ping timeout: 260 seconds]
2016-03-05 18:45 pcercuei has joined #qi-hardware
2016-03-05 18:50 pcercuei has quit [Ping timeout: 252 seconds]
2016-03-05 18:50 pcercuei has joined #qi-hardware
2016-03-05 18:55 pcercuei has quit [Ping timeout: 244 seconds]
2016-03-05 19:52 wildlander has joined #qi-hardware
2016-03-05 19:52 wildlander has quit [Max SendQ exceeded]
2016-03-05 19:53 wildlander has joined #qi-hardware
2016-03-05 19:53 wildlander has quit [Max SendQ exceeded]
2016-03-05 19:53 wildlander has joined #qi-hardware
2016-03-05 20:34 mazzoo has quit [Remote host closed the connection]
2016-03-05 20:48 arossdotme has joined #qi-hardware
2016-03-05 21:03 pcercuei has joined #qi-hardware
2016-03-05 21:06 wej has quit [Ping timeout: 268 seconds]
2016-03-05 21:07 sandeepkr has quit [Ping timeout: 276 seconds]
2016-03-05 21:15 wej has joined #qi-hardware
2016-03-05 21:21 sandeepkr has joined #qi-hardware
2016-03-05 21:39 wolfspraul has joined #qi-hardware
2016-03-05 22:35 rozzin has quit [Ping timeout: 250 seconds]
2016-03-05 22:35 panda| has quit [Ping timeout: 276 seconds]
2016-03-05 22:40 panda|z has joined #qi-hardware
2016-03-05 22:48 wolfspraul has quit [Quit: leaving]
2016-03-05 22:56 rozzin has joined #qi-hardware
2016-03-05 23:59 pcercuei has quit [Quit: dodo]