| 00:33:17 | | OrIdow6 (OrIdow6) joins |
| 03:57:19 | | qw3rty__ joins |
| 04:00:50 | | qw3rty_ quits [Ping timeout: 250 seconds] |
| 06:06:03 | | Stiletto quits [Remote host closed the connection] |
| 06:09:14 | <Ryz> | Random thought: I wonder if there's a way to curate existing content on WBM/IA... |
| 06:09:21 | <Ryz> | Within the website to note~ |
| 06:11:26 | | Stiletto joins |
| 06:22:25 | | Stilett0 joins |
| 06:24:00 | | Stiletto quits [Ping timeout: 244 seconds] |
| 13:37:29 | | britmob256 quits [Ping timeout: 244 seconds] |
| 13:48:21 | | britmob256 joins |
| 15:26:53 | | HCross quits [Read error: Connection reset by peer] |
| 15:26:53 | | aarchi quits [Read error: Connection reset by peer] |
| 15:26:54 | | themadpro quits [Write error: Connection reset by peer] |
| 15:31:07 | | themadpro (themadpro) joins |
| 15:31:12 | | aarchi (aarchi) joins |
| 15:31:23 | | HCross (HCross) joins |
| 23:43:33 | | pabs (pabs) joins |
| 23:45:35 | <pabs> | some users of the wayback-machine-downloader program are sometimes getting 400 Bad Request responses from IA id_ URLs and sometimes those responses go away https://github.com/hartator/wayback-machine-downloader/issues/182#issuecomment-902682451 |
| 23:46:33 | <pabs> | I'm wondering what circumstances this 400 error happens in, and how to reproduce it so that I can test the tool under those conditions |
| 23:46:57 | <pabs> | (and also if the error is a bug in the tool or in IA) |
| 23:47:18 | <pabs> | hmm, I guess I should just mail info@ :) |
| 23:49:56 | <@JAA> | Include an example URL that returns 400 if you can. |
| 23:52:53 | <pabs> | unfortunately none of the users included one, and I can't reproduce the error with the sites the users mentioned |
| 23:53:36 | <@JAA> | Well, unless it's a known bug, I doubt they'll be able to help without an example. |
| 23:54:25 | <pabs> | they might be able to look at their code and find out what conditions the 400 is emitted in |