00:04:04angenieux quits [Ping timeout: 250 seconds]
00:06:49angenieux (angenieux) joins
02:31:18thenes quits [Remote host closed the connection]
02:31:37thenes (thenes) joins
03:06:04utulien quits [Ping timeout: 250 seconds]
04:09:58@rewby quits [Ping timeout: 260 seconds]
05:11:01Webuser037850 joins
05:44:35rewby (rewby) joins
05:44:35@ChanServ sets mode: +o rewby
09:15:42@rewby quits [Ping timeout: 250 seconds]
09:38:16rewby (rewby) joins
09:38:16@ChanServ sets mode: +o rewby
10:41:29T31M quits [Quit: ZNC - https://znc.in]
10:43:19T31M joins
12:56:53qw3rty_ joins
12:59:03qw3rty__ quits [Ping timeout: 260 seconds]
14:00:40thenes quits [Remote host closed the connection]
14:02:55thenes (thenes) joins
15:35:11Webuser037850 quits [Quit: Ooops, wrong browser tab.]
16:15:37<h2ibot>[AT] URLTeam tracker https://tracker.archiveteam.org:1338/api/health is down (507,HTTP status returned: 507)
17:06:44angenieux quits [Ping timeout: 250 seconds]
19:28:22tech234a quits []
19:53:24utulien joins
21:32:50<h2ibot>[AT] URLTeam tracker https://tracker.archiveteam.org:1338/api/health is up (200,Success)
21:33:18<@Flashfire42>terroroftinytown.client.errors.UnhandledStatusCode: Unknown status code 200 for 'https://tiny.cc/about'
21:33:29<@Flashfire42>is the issue and I am not certain how to skip it
21:39:47<AK>🤔200 doesn't seem like a very unknown status code 😂
21:40:54<@Flashfire42>I dont wanna put 200 through as a good status code as I have seen it used as a rate limit before. I may be able to flush the claim manually and not have it readded
21:42:06<AK>Oh, unless somehow /about got put through as a shortcode which it clearly isn't
21:55:18itachi1706 quits [Quit: Bye :P]
22:01:03itachi1706 (itachi1706) joins
22:15:30<TheTechRobo>AK: URLteam brute-forces the shortcodes, so yeah, eventually /about would be done.