00:24:02bradp (bradp) joins
00:24:23bradp quits [Client Quit]
00:28:04flashmeow quits [Ping timeout: 250 seconds]
00:36:40flashmeow (flashmeow) joins
00:37:29madcarbs is now known as bradp
00:38:40bradp is now known as madcarbs
01:02:01flashmeow quits [Client Quit]
03:28:01qw3rty__ joins
03:31:36qw3rty_ quits [Ping timeout: 258 seconds]
04:14:32@OrIdow6 quits [Ping timeout: 258 seconds]
04:19:42OrIdow6 (OrIdow6) joins
04:19:42@ChanServ sets mode: +o OrIdow6
04:27:26@OrIdow6 quits [Excess Flood]
04:28:33OrIdow6 (OrIdow6) joins
04:28:33@ChanServ sets mode: +o OrIdow6
04:37:55@OrIdow6 quits [Ping timeout: 258 seconds]
04:38:08OrIdow6^2 (OrIdow6) joins
04:38:08@ChanServ sets mode: +o OrIdow6^2
04:46:23HackMii_ quits [Remote host closed the connection]
04:46:56HackMii_ (hacktheplanet) joins
04:53:27yano quits [Read error: Connection reset by peer]
04:53:27h3ndr1k quits [Read error: Connection reset by peer]
04:53:27@Kaz quits [Read error: Connection reset by peer]
04:53:28@Fusl quits [Read error: Connection reset by peer]
04:53:28@chfoo quits [Read error: Connection reset by peer]
04:53:28kpcyrd quits [Read error: Connection reset by peer]
04:53:28kiskaWeebChat quits [Read error: Connection reset by peer]
04:53:43h3ndr1k (h3ndr1k) joins
04:53:47chfoo (chfoo) joins
04:53:51@ChanServ sets mode: +o chfoo
04:54:08yano (yano) joins
04:54:35Fusl (Fusl) joins
04:54:35@ChanServ sets mode: +o Fusl
04:54:39kpcyrd (kpcyrd) joins
04:54:57Kaz (Kaz) joins
04:54:57@ChanServ sets mode: +o Kaz
04:55:11kiskaWeebChat (kiska) joins
11:29:49mrhedgehog0 joins
11:41:02mrhedgehog0 quits [Ping timeout: 250 seconds]
11:49:53mrhedgehog0 joins
17:02:46flashmeow (flashmeow) joins
17:23:36mrhedgehog0 quits [Client Quit]
21:06:28Krownest (Krownest) joins
23:25:49<flashmeow>stupid question: why is the wait time so long when there's no items available? can't the tracker just generate more urls to scan?
23:27:13<Krownest>Probably to prevent hitting all of them with the full brunt of participants.
23:28:20<@JAA>Correct. There's a limit on how many items can be processed globally per shortener at once to avoid overloading them.
23:28:52<flashmeow>And the long wait reduces load on the tracker...
23:29:13<@JAA>Yes, that as well.
23:31:20<flashmeow>but no load balancing between users, so running more in parallel increases the chances of getting a task