HomeSearchPrevious dayNext day

00:04:30sralracer quits [Client Quit]
00:04:55PredatorIWD24 joins
00:06:50PredatorIWD2 quits [Ping timeout: 260 seconds]
00:06:50PredatorIWD24 is now known as PredatorIWD2
00:09:39collat joins
00:15:00collat quits [Ping timeout: 260 seconds]
00:26:53collat joins
00:31:55collat quits [Ping timeout: 260 seconds]
00:34:53collat joins
00:42:25collat quits [Ping timeout: 260 seconds]
00:53:32collat joins
00:58:18collat quits [Ping timeout: 240 seconds]
01:10:18collat joins
01:15:40collat quits [Ping timeout: 260 seconds]
01:26:46collat joins
01:33:38collat quits [Ping timeout: 240 seconds]
01:45:31collat joins
01:50:18collat quits [Ping timeout: 240 seconds]
02:15:13Kenshin quits [Ping timeout: 255 seconds]
02:15:27Kenshin joins
02:22:13etnguyen03 quits [Quit: Konversation terminated!]
02:34:43etnguyen03 (etnguyen03) joins
02:36:18Commander001 quits [Ping timeout: 240 seconds]
02:40:45Commander001 joins
02:43:37etnguyen03 quits [Remote host closed the connection]
02:50:17Hackerpcs quits [Quit: Hackerpcs]
02:51:23lennier2 joins
02:54:15lennier2_ quits [Ping timeout: 260 seconds]
03:06:06apache2 quits [Remote host closed the connection]
03:06:15apache2 joins
03:06:41Meroje quits [Quit: bye!]
03:06:55Meroje (Meroje) joins
03:14:41Wohlstand quits [Quit: Wohlstand]
03:17:44<pabs>-feed/#hn-firehose- The question of whether to still allow HTTP/1.0 requests or block them https://utcc.utoronto.ca/~cks/space/blog/web/HTTP10BlockQuestion https://news.ycombinator.com/item?id=41980387
03:18:03Gadelhas5627 joins
03:21:05Gadelhas562 quits [Ping timeout: 260 seconds]
03:21:05Gadelhas5627 is now known as Gadelhas562
03:27:45Gadelhas5625 joins
03:28:17<@JAA>I'd be interested in what clients still use HTTP/1.0.
03:31:35Gadelhas562 quits [Ping timeout: 260 seconds]
03:31:35Gadelhas5625 is now known as Gadelhas562
03:33:04wickedplayer494 quits [Remote host closed the connection]
03:42:25<pabs>ah, AT stuff does 1.1 I guess?
03:43:19<@JAA>Yes. By a very strict reading, WARC doesn't even support 1.0.
03:44:45Commander001 quits [Read error: Connection reset by peer]
03:45:02Commander001 joins
03:45:40Gadelhas5624 joins
03:49:05Gadelhas562 quits [Ping timeout: 260 seconds]
03:49:05Gadelhas5624 is now known as Gadelhas562
03:49:46wickedplayer494 joins
03:54:52Gadelhas5622 joins
03:59:00Gadelhas562 quits [Ping timeout: 260 seconds]
03:59:00Gadelhas5622 is now known as Gadelhas562
04:00:27<steering>1.1 is basically just "include a Host header"
04:00:53wickedplayer494 quits [Remote host closed the connection]
04:03:10<nicolas17>steering: and "you have keepalive so you better send a content-length instead of relying on closing the connection"
04:03:47<@JAA>Yep. WARC requires headers that are compatible with HTTP/1.1 (RFC 2616 for WARC/1.0, 723x for WARC/1.1), and since HTTP/1.0 headers might not be compatible due to the above, you technically can't write them to WARC.
04:04:30wickedplayer494 joins
04:06:48<steering>nicolas17: welllll, the client doesn't really need to worry about that
04:07:24<steering>it's more complex for the server of course but the client can just go pfft someone gave me a one line patch to include a Host header 25 years ago and now I support HTTP/1.1!
04:08:08<steering>oh crap it really was 25 years, good guess me
04:09:41<nicolas17>it can't be 25 years
04:10:02<steering>rfc2616 june 1999 \o/
04:10:21<nicolas17>I refuse to believe that was 25 years ago /o\
04:20:07wickedplayer494 quits [Remote host closed the connection]
04:24:08<steering>i was 6 \o/ i don't remember it
04:24:11<steering>lol
04:27:48tool joins
04:28:46tool quits [Client Quit]
04:46:12wickedplayer494 joins
05:13:26sec^nd quits [Remote host closed the connection]
05:13:46sec^nd (second) joins
05:21:13Island quits [Read error: Connection reset by peer]
05:23:18BlueMaxima quits [Ping timeout: 240 seconds]
05:42:45Island joins
05:55:02Guest54 quits [Quit: My MacBook has gone to sleep. ZZZzzz…]
06:18:25anarcat quits [Ping timeout: 260 seconds]
06:29:46anarcat (anarcat) joins
06:56:01Wohlstand (Wohlstand) joins
07:02:26Radzig2 joins
07:04:38Wohlstand quits [Client Quit]
07:04:58Radzig quits [Ping timeout: 240 seconds]
07:04:58Radzig2 is now known as Radzig
07:05:50Unholy2361924645377131 (Unholy2361) joins
07:53:54Hackerpcs (Hackerpcs) joins
08:05:39<h2ibot>OrIdow6 uploaded File:Cohost logo.png (Logo of Cohost): https://wiki.archiveteam.org/?title=File%3ACohost%20logo.png
08:08:49BornOn420 quits [Remote host closed the connection]
08:09:22BornOn420 (BornOn420) joins
08:36:54<@arkiver>temporary targets may go through a few hours of instability
09:18:38useretail joins
09:46:40pabs quits [Ping timeout: 260 seconds]
09:52:31pabs (pabs) joins
10:13:30lennier2 quits [Ping timeout: 260 seconds]
10:15:03lennier2 joins
10:15:19sralracer joins
10:16:36lennier2_ joins
10:19:58lennier2 quits [Ping timeout: 240 seconds]
10:33:20BornOn420 quits [Remote host closed the connection]
10:33:56BornOn420 (BornOn420) joins
11:00:01Bleo18260072271962 quits [Quit: The Lounge - https://thelounge.chat]
11:02:06vix5110_ joins
11:02:47Bleo18260072271962 joins
11:06:57vix5110_ quits [Client Quit]
11:07:17vix5110_5 joins
11:14:35vix5110_5 quits [Client Quit]
11:18:22nulldata quits [Ping timeout: 255 seconds]
11:26:19nulldata (nulldata) joins
11:38:50SkilledAlpaca418 quits [Quit: SkilledAlpaca418]
11:40:32SkilledAlpaca418 joins
11:42:10lennier2_ quits [Ping timeout: 260 seconds]
11:43:56lennier2_ joins
11:46:36lennier2 joins
11:50:20lennier2_ quits [Ping timeout: 260 seconds]
12:23:49MrMcNuggets (MrMcNuggets) joins
12:31:13beastbg8_ joins
12:34:40beastbg8 quits [Ping timeout: 260 seconds]
12:40:34<h2ibot>Exorcism uploaded File:Screenshot-veoh.png: https://wiki.archiveteam.org/?title=File%3AScreenshot-veoh.png
12:41:35<h2ibot>Exorcism edited Veoh (+29): https://wiki.archiveteam.org/?diff=53683&oldid=53651
13:10:15<anarcat>JAA: fantastic, thank you so much for your help
13:10:56<anarcat>JAA: is there any dashboard that allows one to follow a single task? the current viewer overloads my poor 16-core 4GHz 12th gen intel CPU with 32GB of ram
13:11:03<anarcat>i should probably upgrade, i know ;)
13:39:04<that_lurker>http://archivebot.com/3
13:39:29<that_lurker>though im not sure if the tasks are still in the background
13:43:59<anarcat>oh yeah, taht thing
13:44:00<anarcat>i'll test
14:25:05<pabs>anarcat: overloads? my ancient 2013 desktop is fine :)
14:33:45Guest54 joins
15:12:53<anarcat>pabs: i don't understand there, my browser uses up a lot of CPU and the fan spins up when i use the old UI
15:12:57<anarcat>the new UI is fine, surprisingly
15:14:53Radzig2 joins
15:15:05Radzig quits [Ping timeout: 260 seconds]
15:15:29Radzig2 is now known as Radzig
15:58:08VerifiedJ9 quits [Remote host closed the connection]
15:59:10VerifiedJ9 (VerifiedJ) joins
17:00:12<@JAA>anarcat: Hmm, weird. Both dashboards have to process all data, there's no filtering at that level. And the old dashboard recently got a big update that makes it a lot less CPU-intensive. My 2015 laptop doesn't even turn up the fan.
17:11:24cow_2001 quits [Quit: ✡]
17:13:23cow_2001 joins
17:26:25Juesto (Juest) joins
17:26:55Juest quits [Ping timeout: 260 seconds]
17:26:55Juesto is now known as Juest
17:29:12Juesto (Juest) joins
17:32:45Juest quits [Ping timeout: 260 seconds]
17:32:45Juesto is now known as Juest
17:33:42<TheTechRobo>yeah I've never had issues with the viewer overloading my PC since the updates to the dashboard
17:36:25<@JAA>Maybe it's interference from a browser extension?
17:37:53<anarcat>maybe!
17:38:47<anarcat>about:performance tells me it's "firefox" taking 50% of a CPU
17:38:53<anarcat>isn't it great?
17:39:09<TheTechRobo>if you have an adblocker enabled, try disabling that
17:40:25<@JAA>I'd probably test in a separate temporary browser profile first just to narrow it down.
17:49:05FireFly quits [Ping timeout: 260 seconds]
17:49:24FireFly joins
17:50:31MrMcNuggets quits [Quit: WeeChat 4.3.2]
18:04:20Radzig2 joins
18:06:38Radzig quits [Ping timeout: 240 seconds]
18:06:38Radzig2 is now known as Radzig
19:12:40qwertyasdfuiopghjkl quits [Ping timeout: 255 seconds]
19:17:32qwertyasdfuiopghjkl (qwertyasdfuiopghjkl) joins
19:25:20Guest54 quits [Ping timeout: 260 seconds]
19:34:22Commander001 quits [Remote host closed the connection]
19:45:05Commander001 joins
20:23:40Juest quits [Ping timeout: 260 seconds]
20:32:18bilboed quits [Quit: Ping timeout (120 seconds)]
20:32:30bilboed joins
20:36:26Island quits [Read error: Connection reset by peer]
20:38:38Island joins
20:53:25Irenes quits [Ping timeout: 260 seconds]
20:53:41Island quits [Read error: Connection reset by peer]
20:55:14Island joins
21:06:06Irenes (ireneista) joins
21:13:09etnguyen03 (etnguyen03) joins
21:50:28Juest (Juest) joins
21:59:20M60_ quits [Ping timeout: 260 seconds]
21:59:25M60_ joins
22:05:10M60_ quits [Ping timeout: 260 seconds]
22:06:00etnguyen03 quits [Client Quit]
22:06:14M60_ joins
22:06:45etnguyen03 (etnguyen03) joins
22:32:19monika quits [Quit: Zzz]
22:32:32monika (boom) joins
23:30:57etnguyen03 quits [Client Quit]
23:44:21sec^nd quits [Ping timeout: 240 seconds]
23:48:39sec^nd (second) joins
23:53:31Wohlstand (Wohlstand) joins

HomeSearchPrevious dayNext day