04:20:45Exorcism|phone (exorcism) joins
04:20:48Exorcism|phone quits [Client Quit]
05:38:30qwertyasdfuiopghjkl quits [Ping timeout: 265 seconds]
05:40:09Exorcism is now known as Exorcism|phone
06:03:08qwertyasdfuiopghjkl (qwertyasdfuiopghjkl) joins
06:37:18Exorcism|phone is now known as Exorcism
07:23:19Exorcism is now known as Exorcism|t
08:38:38treora quits [Ping timeout: 252 seconds]
08:41:10treora joins
09:07:56Exorcism (exorcism) joins
11:32:32treora quits [Remote host closed the connection]
11:32:34treora joins
12:35:04AmAnd0A quits [Read error: Connection reset by peer]
12:35:35AmAnd0A joins
12:40:27AmAnd0A quits [Ping timeout: 265 seconds]
12:41:00AmAnd0A joins
13:18:05<h2ibot>[AT] URLTeam tracker https://tracker.archiveteam.org:1338/api/health is down (507,HTTP status returned: 507)
13:18:36BearFortress_ quits [Quit: https://quassel-irc.org - Chat comfortably. Anywhere.]
13:25:07treora quits [Remote host closed the connection]
13:25:08treora joins
13:54:34BearFortress joins
14:01:17AmAnd0A quits [Ping timeout: 258 seconds]
15:42:04Icyelut|2 quits [Quit: bye]
15:44:00project10 joins
16:09:35T31M quits [Quit: ZNC - https://znc.in]
16:09:54T31M joins
16:23:07@JAA pokes flashfire42.
16:39:04Artem4ikBaik (Artem4ikBaik) joins
16:54:17<fireonlive>deadman_safety_tripped, interesting
17:36:51project10 quits [Changing host]
17:36:51project10 joins
17:37:54W7RFa6AbNFz quits [Read error: Connection reset by peer]
17:45:49W7RFa6AbNFz joins
17:53:14treora quits [Remote host closed the connection]
17:53:17treora joins
18:07:03Artem4ikBaik quits [Client Quit]
20:35:15<h2ibot>[AT] URLTeam tracker https://tracker.archiveteam.org:1338/api/health is up (200,Success)
21:05:58AmAnd0A joins
21:13:16<@flashfire42>Sorry I was asleep I kicked it
21:34:46<@rewby>Was this a classic case of "turn it off and on again"
21:42:33<@flashfire42>Yeah there are 2 urls specifically for go-microsoft-com that are always 403 but I dont feel confident adding it to the ignore list because It might end up being a status code used for being banned or something. So I just clear the error reports when they pile up
21:42:57<@flashfire42>The tracker is designed so that at 4000 error reports it stops operations so that someone can investigate wtf may have happened
21:57:47AmAnd0A quits [Ping timeout: 252 seconds]
21:58:24AmAnd0A joins
22:23:10AmAnd0A quits [Read error: Connection reset by peer]
22:23:26AmAnd0A joins
22:36:26<nstrom|m>deadman switch indeed
22:42:45AmAnd0A quits [Read error: Connection reset by peer]
22:43:27AmAnd0A joins
23:53:35<fireonlive>ahh