| 01:15.36 | *** join/#qi-hardware wolfspraul (~wolfsprau@p5DD44D6D.dip0.t-ipconnect.de) |
| 01:37.21 | *** join/#qi-hardware wolfspraul (~wolfsprau@p5DD44D6D.dip0.t-ipconnect.de) |
| 01:52.41 | *** join/#qi-hardware sandeepkr (~sandeep@111.235.64.4) |
| 02:19.20 | *** join/#qi-hardware xiangfu (~xiangfu@111.202.109.14) |
| 02:48.42 | *** join/#qi-hardware xiangfu (~xiangfu@111.202.109.14) |
| 04:49.12 | *** join/#qi-hardware DocScrutinizer05 (~saturn@openmoko/engineers/joerg) |
| 07:34.08 | eintopf | http://www.ibtimes.co.uk/meet-tomatan-wearable-robot-that-feeds-you-tomatoes-you-run-1488706 |
| 07:34.12 | eintopf | nice wearable |
| 08:10.11 | whitequark | DocScrutinizer51: dunno |
| 08:10.35 | whitequark | freenode weirdness probably. it sometimes lands on a flaky server via the usual rotation |
| 08:10.51 | DocScrutinizer05 | hmm, possible |
| 08:12.26 | DocScrutinizer05 | freenode suffers from some (D)Dos at least last weekend, maybe it's still ongoing |
| 08:12.54 | DocScrutinizer05 | I got quit msgs on ignore, what's the quit msg of _whitelogger? |
| 08:14.26 | DocScrutinizer05 | ping timeout? that would be the usual DDoS related effect |
| 08:19.39 | whitequark | also on ignore |
| 08:19.52 | whitequark | I'd look in logs but there are like fifty channels |
| 08:26.50 | DocScrutinizer05 | dang, infobot's logs have only join events logged |
| 08:27.55 | DocScrutinizer05 | mine as well, since my logs only log what's also displayed (lame) |
| 08:28.49 | DocScrutinizer05 | even more lame: I can't set 'hide join/nick/part' per channel, only globally |
| 08:29.12 | DocScrutinizer05 | let's see what xchat has |
| 08:33.32 | DocScrutinizer51 | 210239 * _whitelogger has quit (Excess Flood) |
| 08:34.26 | DocScrutinizer05 | which is a tad strange, I dunno what it would post to flood |
| 08:34.32 | DocScrutinizer05 | _whitelogger: help |
| 08:34.41 | DocScrutinizer05 | _whitelogger: ? |
| 08:51.20 | DocScrutinizer05 | whitequark: does whitelogger post *anything* except login and /join and services-related posts? |
| 08:54.49 | whitequark | oh Excess Flood |
| 08:54.50 | whitequark | sigh |
| 08:54.54 | whitequark | no, it doesn't |
| 08:54.58 | whitequark | it only joins |
| 08:55.10 | whitequark | and responds to pings, and requests channel lists |
| 08:57.39 | *** join/#qi-hardware sandeepkr (~sandeep@111.235.64.4) |
| 09:11.56 | *** join/#qi-hardware mazzoo (mazzoo@brezn.club.muc.ccc.de) |
| 09:18.58 | DocScrutinizer05 | forget #freenode, it turned into ##defocus |
| 09:21.58 | DocScrutinizer05 | I just conferred the title "poorest moderation on freenode" |
| 09:23.10 | DocScrutinizer05 | staffers instead of answering a plain question like "why gets a client disconnected with `excess flood`?" they suggest /stats p and /query |
| 09:24.06 | DocScrutinizer05 | while the channel explodes from trolling and noise |
| 09:44.06 | *** join/#qi-hardware infobot (ibot@rikers.org) |
| 09:44.06 | *** topic/#qi-hardware is Copyleft hardware - http://qi-hardware.com | hardware hackers join here to discuss Ben NanoNote, atben/atusb 802.15.4 wireless, anelok and other community driven hw projects | public logging at http://en.qi-hardware.com/irclogs and http://irclog.whitequark.org/qi-hardware |
| 09:44.06 | *** mode/#qi-hardware [+v infobot] by ChanServ |
| 09:44.09 | *** mode/#qi-hardware [-o DocScrutinizer05] by ChanServ |
| 09:44.12 | DocScrutinizer05 | ~+chaninfo |
| 09:44.12 | 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.32 | DocScrutinizer05 | ~+chaninfo |
| 09:44.32 | 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, ... |
| 09:45.37 | 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 |
| 09:48.17 | *** join/#qi-hardware mazzoo (mazzoo@brezn.club.muc.ccc.de) |
| 09:52.55 | whitequark | DocScrutinizer05: whitelogger throttles joins too |
| 09:53.06 | DocScrutinizer05 | that's what I thought |
| 09:53.07 | whitequark | unfortunately freenode staff refused to tell me what the actual limit is |
| 09:53.15 | whitequark | "increase it if you get kicked" my ass |
| 09:53.21 | DocScrutinizer05 | hehe yes |
| 09:53.58 | whitequark | it's currently at 1 msg every 0.5s |
| 09:54.06 | 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 |
| 09:54.24 | whitequark | I used to do 1 join per second as is the default with my IRC framework |
| 09:54.43 | whitequark | however, that started breaking once I got over ~30 channels (I think), with 2 commands per channel |
| 09:54.59 | whitequark | they have something like per-minute buckets and you have a limit of how many messages per bucket you can send |
| 09:55.12 | whitequark | it's very obnoxious to debug |
| 09:55.30 | whitequark | I bumped it down to 0.4 messages per second |
| 09:57.34 | 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 |
| 09:58.35 | DocScrutinizer05 | hardly anything you can do about that, except waiting for response from one command before sending next |
| 09:59.08 | whitequark | hmmm could be |
| 10:42.05 | *** join/#qi-hardware xiangfu (~xiangfu@111.202.109.14) |
| 11:19.35 | *** join/#qi-hardware sandeepkr (~sandeep@111.235.64.4) |
| 12:18.38 | wpwrak | waiting for a response may not be enough, e.g., if the response is quick but the bucket still enforces a lower rate |
| 12:19.16 | wpwrak | but i guess it could be good practice to avoid overrunning the server |
| 12:24.17 | *** join/#qi-hardware fdcx (357@ceata/consiliu/FDCX) |
| 12:43.09 | *** join/#qi-hardware fdcx (357@ceata/consiliu/FDCX) |
| 12:43.49 | *** join/#qi-hardware aimg (~aim@125.16.18.198) |
| 14:30.11 | *** join/#qi-hardware xiangfu (~xiangfu@111.202.109.14) |
| 15:00.56 | *** join/#qi-hardware xiangfu (~xiangfu@111.202.109.14) |
| 15:12.49 | *** join/#qi-hardware pcercuei (~pcercuei@185.13.202.211) |
| 16:30.50 | *** join/#qi-hardware dandon (~dandon@185.16.53.65) |
| 17:21.45 | *** join/#qi-hardware anandas (ananda@gateway/shell/bnc4free/x-nsneuimntppjhnwv) |
| 17:24.51 | *** part/#qi-hardware anandas (ananda@gateway/shell/bnc4free/x-nsneuimntppjhnwv) |
| 18:19.26 | *** join/#qi-hardware pcercuei (~pcercuei@185.13.202.211) |
| 18:28.05 | *** join/#qi-hardware pcercuei (~pcercuei@185.13.202.211) |
| 18:45.28 | *** join/#qi-hardware pcercuei (~pcercuei@185.13.202.211) |
| 18:50.39 | *** join/#qi-hardware pcercuei (~pcercuei@185.13.202.211) |
| 19:52.27 | *** join/#qi-hardware wildlander (~wild@unaffiliated/wildlander) |
| 19:53.11 | *** join/#qi-hardware wildlander (~wild@unaffiliated/wildlander) |
| 19:53.48 | *** join/#qi-hardware wildlander (~wild@unaffiliated/wildlander) |
| 20:48.25 | *** join/#qi-hardware arossdotme (~zxy@host-92-26-242-129.as13285.net) |
| 21:03.15 | *** join/#qi-hardware pcercuei (~pcercuei@185.13.202.211) |
| 21:15.56 | *** join/#qi-hardware wej (~j@2001:1af8:4010:a052:21::5e) |
| 21:21.27 | *** join/#qi-hardware sandeepkr (~sandeep@111.235.64.4) |
| 21:39.18 | *** join/#qi-hardware wolfspraul (~wolfsprau@x4d0c988b.dyn.telefonica.de) |
| 22:40.19 | *** join/#qi-hardware panda|z (~panda|z@li914-99.members.linode.com) |
| 22:56.51 | *** join/#qi-hardware rozzin (rozzin@2600:3c00::f03c:91ff:fe56:7619) |