01:20:44nulldata quits [Ping timeout: 255 seconds]
01:30:50nulldata (nulldata) joins
01:31:03qwertyasdfuiopghjkl quits [Remote host closed the connection]
01:31:40qwertyasdfuiopghjkl (qwertyasdfuiopghjkl) joins
03:10:55qwertyasdfuiopghjkl quits [Remote host closed the connection]
03:11:56qwertyasdfuiopghjkl (qwertyasdfuiopghjkl) joins
03:16:25DogsRNice joins
03:32:23DogsRNice_ joins
03:35:44DogsRNice quits [Ping timeout: 255 seconds]
05:15:12SF joins
05:26:26SF quits [Ping timeout: 255 seconds]
05:39:34SF joins
05:40:50DogsRNice_ quits [Ping timeout: 255 seconds]
05:58:39qwertyasdfuiopghjkl quits [Ping timeout: 265 seconds]
06:05:05BearFortress joins
07:39:19Arcorann (Arcorann) joins
09:12:47f_ quits [Ping timeout: 255 seconds]
09:28:33qwertyasdfuiopghjkl (qwertyasdfuiopghjkl) joins
09:58:54qwertyasdfuiopghjkl quits [Remote host closed the connection]
09:59:21qwertyasdfuiopghjkl (qwertyasdfuiopghjkl) joins
10:17:01<qwertyasdfuiopghjkl>For some reason, each use of SPN2 seems to be counted against the rate limit twice if "Save screen shot" is checked. Is this intentional? (after saving a page without screenshot enabled, on https://web.archive.org/save/status/user "available" decreases and "processing" increases by 1, but after saving with screenshot enabled they change by 2)
10:22:31BearFortress_ joins
10:26:35BearFortress quits [Ping timeout: 255 seconds]
10:53:47f_ (funderscore) joins
11:05:42BearFortress_ quits [Client Quit]
12:51:57Arcorann quits [Ping timeout: 272 seconds]
14:04:46BearFortress joins
14:36:00<@arkiver>qwertyasdfuiopghjkl: checking
16:15:45Sanqui joins
16:15:47Sanqui quits [Changing host]
16:15:47Sanqui (Sanqui) joins
16:16:29Sanqui quits [Remote host closed the connection]
16:19:44Sanqui joins
16:19:46Sanqui quits [Changing host]
16:19:46Sanqui (Sanqui) joins
17:33:09SF quits [Ping timeout: 272 seconds]
17:35:04SF joins
18:42:38qwertyasdfuiopghjkl quits [Client Quit]