| 01:16:32 | | britmob25 joins |
| 03:59:35 | | DogsRNice_ quits [Read error: Connection reset by peer] |
| 05:15:36 | <jtagcat> | Thought idea. Could warrior or warrior-like things be packaged in to a similar thing like Snowflake? |
| 05:15:49 | <jtagcat> | https://snowflake.torproject.org/ |
| 05:16:05 | <jtagcat> | Essentially 'warrior as a browser add-on'. |
| 05:19:58 | <OrIdow6> | I've thought about (and sometimes discussed) that sort of thing before, are two main problems: |
| 05:21:39 | <OrIdow6> | - Warrior projects use a large set of underlying software (Python, wget, numerous libraries, often several types of IPC) that would require either a complete rewrite of the entire thing or expensive emulation |
| 05:23:27 | <OrIdow6> | - It's difficult to guarantee that the browser will allow for reliable capture of raw HTTP traffic, or something that can be guaranteedly converted back into the raw format; often they like to alter and rearrange headers, inject things, etc., and even if there was a reliable browser, someone would have to keep track of changes to it in case something broke this |
| 05:27:25 | <OrIdow6> | I do recall that a year or so ago someone wrote some JS app that you could just navigate to in a site, and it would save API response bodies from some target site (strawpoll.me?) and send them back to whoever was running it - but obviously this cannot create reliable warcs, which puts it below the quality threshold for most contemporary ArchiveTeam projects |
| 05:28:17 | <jtagcat> | wasm could seem of interest |
| 05:28:45 | <@JAA> | No raw network access with wasm either. It's impossible from within any browser as far as I know. |
| 05:28:51 | <OrIdow6> | And in addition to the header thing, I don't think browsers let you send data to arbitrairy ports; mess with security headers; override DNS; etc. |
| 05:29:02 | <jtagcat> | The first point, I thought about too. For large scale, indefinitely long-running (meta) projects, like urlteam. |
| 05:29:03 | <OrIdow6> | Which have all been necessary at some point or another |
| 05:29:22 | <jtagcat> | ok |
| 05:30:05 | <@JAA> | The current implementation of URLTeam could be done with an extension since it doesn't write WARCs at all. But the long-term plan is (has been for at least several years) to change that to WARCs so all our work can go into the Wayback Machine. |
| 06:14:33 | | kiska quits [Ping timeout: 258 seconds] |
| 06:14:40 | | s-crypt quits [Ping timeout: 250 seconds] |
| 06:25:45 | | s-crypt (s-crypt) joins |
| 06:26:45 | | kiska (kiska) joins |
| 11:12:25 | | janpaul123_ (janpaul123) joins |
| 11:12:43 | | janpaul123 quits [Read error: Connection reset by peer] |
| 11:12:43 | | janpaul123_ is now known as janpaul123 |
| 11:51:46 | | Hyenadae quits [Remote host closed the connection] |
| 17:43:16 | | Zerote_ quits [Read error: Connection reset by peer] |
| 17:50:20 | | nertzy__ quits [Client Quit] |
| 17:53:10 | | nertzy (nertzy) joins |
| 17:53:16 | | nertzy quits [Client Quit] |
| 17:53:35 | | nertzy (nertzy) joins |
| 18:30:51 | | Kelsair joins |
| 21:42:26 | | RBecker quits [Remote host closed the connection] |
| 21:46:47 | | RBecker joins |
| 21:46:48 | | RBecker is now authenticated as RBecker |
| 21:46:48 | | RBecker quits [Changing host] |
| 21:46:48 | | RBecker (RBecker) joins |