| 01:28:04 | | Arcorann quits [Ping timeout: 265 seconds] |
| 02:25:51 | | HP_Archivist (HP_Archivist) joins |
| 02:33:04 | | HP_Archivist quits [Client Quit] |
| 02:43:01 | | qwertyasdfuiopghjkl quits [Remote host closed the connection] |
| 02:48:21 | | qwertyasdfuiopghjkl joins |
| 03:29:48 | | knecht420 quits [Read error: Connection reset by peer] |
| 03:30:11 | | knecht420 (knecht420) joins |
| 04:05:53 | | tzt quits [Quit: WeeChat 2.3] |
| 04:06:32 | | tzt (tzt) joins |
| 05:03:41 | | themadpro quits [Quit: Connection closed for inactivity] |
| 05:11:35 | | tech234a quits [Quit: Connection closed for inactivity] |
| 05:57:57 | | tech234a (tech234a) joins |
| 06:26:04 | | Arcorann (Arcorann) joins |
| 06:51:58 | | Specular joins |
| 06:53:07 | <Specular> | I've noticed in the past 2-3 months that saving a web page manually via the Wayback Machine returns an olden version of the page upon completion, rather than the new version at the time of submission. |
| 06:53:14 | <Specular> | Anyone know what changed? |
| 06:54:37 | <Specular> | Like, sometimes the date in the returned URL will be older by even days. Other times it may only be hours. |
| 08:49:56 | | qw3rty_ quits [Read error: Connection reset by peer] |
| 08:50:07 | | qw3rty_ joins |
| 10:13:10 | | johtso joins |
| 11:29:50 | <IDK> | Any idea what crawl this is: https://archive.org/details/TikTok |
| 11:30:38 | <IDK> | And how is the links being discovered |
| 12:43:21 | | qwertyasdfuiopghjkl quits [Remote host closed the connection] |
| 13:15:15 | | qwertyasdfuiopghjkl joins |
| 14:07:26 | | Arcorann quits [Ping timeout: 240 seconds] |
| 15:17:03 | | Specular quits [Client Quit] |
| 15:48:55 | <@JAA> | If Specular returns: that's been happening for years, and last time I asked, I was told it's an issue with the index and/or caching. The new snapshot usually starts working a few minutes later, sometimes it takes a few hours. |
| 16:36:59 | | HP_Archivist (HP_Archivist) joins |
| 16:42:33 | | HP_Archivist quits [Client Quit] |
| 17:10:15 | | datechnoman quits [Quit: Ping timeout (120 seconds)] |
| 17:11:38 | | datechnoman (datechnoman) joins |
| 19:11:06 | | systwi quits [Quit: Give me your HAND, and I'll help you across.] |
| 19:22:55 | | systwi (systwi) joins |
| 19:44:34 | <IDK> | server for index can't keep up with the demand |
| 19:45:05 | <IDK> | thats why sometimes SPN shows as still working on capture, but the capture may have already completed |
| 19:45:52 | <IDK> | because the capture cant be found by the server, but the SPN returned success |
| 20:25:38 | <@JAA> | It's not a matter of demand/throughput but one of a poor implementation. It shouldn't be hard to make SPN block until the records are in the index, for example. |
| 20:25:46 | <@JAA> | There are caching bugs as well. |
| 22:07:22 | | AK quits [Quit: Ping timeout (120 seconds)] |
| 22:08:25 | | AK (AK) joins |