| 00:48:50 | | jasons (jasons) joins |
| 01:15:50 | | TheTechRobo quits [Ping timeout: 240 seconds] |
| 01:20:12 | | TheTechRobo (TheTechRobo) joins |
| 01:54:18 | | pseudorizer quits [Client Quit] |
| 01:56:37 | | pseudorizer (pseudorizer) joins |
| 02:03:42 | | qwertyasdfuiopghjkl (qwertyasdfuiopghjkl) joins |
| 02:29:43 | | qwertyasdfuiopghjkl quits [Remote host closed the connection] |
| 02:49:02 | | qwertyasdfuiopghjkl (qwertyasdfuiopghjkl) joins |
| 02:51:07 | | jasons quits [Client Quit] |
| 06:31:22 | | qwertyasdfuiopghjkl quits [Remote host closed the connection] |
| 06:56:33 | | qwertyasdfuiopghjkl (qwertyasdfuiopghjkl) joins |
| 09:37:12 | | qwertyasdfuiopghjkl quits [Remote host closed the connection] |
| 09:39:45 | | parfait (kdqep) joins |
| 09:41:35 | | parfait_ quits [Ping timeout: 272 seconds] |
| 10:08:11 | | @rewby quits [Ping timeout: 272 seconds] |
| 11:33:13 | | rewby (rewby) joins |
| 11:33:13 | | @ChanServ sets mode: +o rewby |
| 11:38:27 | | nulldata5 (nulldata) joins |
| 11:40:01 | | nulldata quits [Ping timeout: 272 seconds] |
| 11:40:01 | | nulldata5 is now known as nulldata |
| 13:49:07 | | qwertyasdfuiopghjkl (qwertyasdfuiopghjkl) joins |
| 16:26:56 | | maxfan8_ quits [Quit: WeeChat 3.3] |
| 16:27:20 | | andrew quits [Ping timeout: 240 seconds] |
| 16:31:31 | | andrew (andrew) joins |
| 16:33:09 | | maxfan8 (maxfan8) joins |
| 19:16:58 | | nothere quits [Quit: Leaving] |
| 20:06:32 | | nothere joins |
| 21:37:58 | | jasons (jasons) joins |
| 22:29:45 | | duszek joins |
| 22:30:21 | <duszek> | i want to run a warrior, however, i tend to put my laptop on sleep a lot |
| 22:31:27 | <duszek> | does it have any impact on your archiving efforts? |
| 22:38:41 | | jasons quits [Ping timeout: 272 seconds] |
| 23:41:48 | | jasons (jasons) joins |
| 23:41:52 | | Sluggs_ is now known as Sluggs |
| 23:52:05 | <myself> | My understanding is that that's not really suitable, the VM will pause when the machine is suspended. At the very least, this breaks network connections that're open at the time, and nothing's really designed for that. |
| 23:52:34 | <myself> | Also, jobs that're claimed by your warrior might be sent back out to others since yours hasn't been heard from in a while, then when yours finishes them, they get uploaded anyway and counted as duplicate. |
| 23:53:11 | <@JAA> | I think there might be problems with timestamps, but I'm not sure we've properly verified that. |
| 23:53:41 | <@JAA> | As in, wrong timestamps written to the WARC because the clock gets suspended and doesn't catch up immediately. |
| 23:53:55 | <@JAA> | We have some countermeasures for that, but not sure it's in all projects. |
| 23:54:04 | <@JAA> | (And it can't catch all cases.) |
| 23:57:23 | <myself> | Laptops do make splendid warrior platforms, but think more along the lines of "my previous laptop with the busted keyboard and crappy battery, tucked on a shelf somewhere running 24/7 acting as a low-power server", rather than your daily-driver. |