02:51:18datechnoman quits [Ping timeout: 256 seconds]
03:17:11Webuser749681 joins
03:20:46Webuser749681 quits [Client Quit]
04:11:38datechnoman (datechnoman) joins
04:29:02DogsRNice quits [Read error: Connection reset by peer]
05:05:02n9nes quits [Ping timeout: 256 seconds]
05:06:36n9nes joins
05:37:54pabs quits [Ping timeout: 256 seconds]
06:39:48pabs (pabs) joins
07:26:08BearFortress_ quits []
07:54:56BearFortress joins
07:55:29BearFortress quits [Client Quit]
08:02:17BearFortress joins
08:39:38pabs quits [Read error: Connection reset by peer]
08:40:13pabs (pabs) joins
11:22:10Jens leaves
13:19:40cyanbox joins
13:22:00cyanbox_ quits [Ping timeout: 256 seconds]
13:27:40fuzzy80211 quits [Ping timeout: 256 seconds]
14:58:51<h2ibot>[AT] URLTeam tracker https://tracker.archiveteam.org:1338/api/health is down (507,HTTP status returned: 507)
15:46:05@imer hands Flashfire42 the pokey stick
15:47:32driib97 quits [Quit: The Lounge - https://thelounge.chat]
15:51:32driib97 (driib) joins
15:56:15driib97 quits [Client Quit]
15:57:00driib97 (driib) joins
16:03:28driib97 quits [Client Quit]
16:07:06driib97 (driib) joins
20:03:39DogsRNice joins
22:22:59<h2ibot>[AT] URLTeam tracker https://tracker.archiveteam.org:1338/api/health is up (200,Success)
22:23:11<klea>yay!
22:27:26<@Flashfire42>Just had to delete a few 403s from the queue
23:27:49chrismeller3 quits [Quit: chrismeller3]
23:28:25<klea>JAA: I suppose because of the auto-queueing of random strings or are there any other differences?
23:29:50<@JAA>(from -bs)
23:30:12<@JAA>klea: Yeah, the autoqueueing, the settings per shortener, the progress tracking per shortener, etc.
23:30:20<klea>Ack.
23:30:32<@JAA>The data flow is also entirely different with the results going through the tracker.
23:30:43<klea>oh
23:31:06klea was thinking of asking to have #Y get some data back in the tracker, for monitoring tools to be able to be like AB.
23:31:42<@JAA>#Y builds on various capabilities that were only added to the tracker quite recently.
23:33:26chrismeller3 (chrismeller) joins