03:40:43DogsRNice quits [Read error: Connection reset by peer]
07:36:37pabs quits [Ping timeout: 272 seconds]
07:50:40pabs (pabs) joins
09:17:10<tzt>https://www.niemanlab.org/2025/10/the-wayback-machines-snapshots-of-news-homepages-plummet-after-a-breakdown-in-archiving-projects/
09:25:06<tzt>>“Some material we had archived post-May 16th of this year is not yet available via the Wayback Machine as their corresponding indexes have not yet been built,” he said. Under normal circumstances, building these indexes can cause a delay of a few hours or a few days before the snapshots appear in the Wayback Machine. The delay we documented is more than five months
09:25:09<tzt>long. Graham said there are “various operational reasons” for this delay, namely “resource allocation,” but otherwise declined to specify.
10:41:40HP_Archivist quits [Ping timeout: 256 seconds]
11:06:41c3manu quits [Read error: Connection reset by peer]
11:45:21night quits [Remote host closed the connection]
11:46:28night joins
12:19:20c3manu (c3manu) joins
12:27:13DigitalDragons eyes urls-sources commit on may 16th
12:45:45DigitalDragons (likely unrelated)
15:22:45eggdrop quits [Ping timeout: 272 seconds]
15:27:19eggdrop (eggdrop) joins
16:09:46eggdrop quits [Ping timeout: 256 seconds]
16:20:58eggdrop (eggdrop) joins
16:54:14SootBector quits [Remote host closed the connection]
18:29:25HP_Archivist (HP_Archivist) joins
19:58:30DogsRNice joins
20:10:06HP_Archivist quits [Read error: Connection reset by peer]
21:56:54HP_Archivist (HP_Archivist) joins
23:01:54<nicolas17>my DigitalOcean VPS (159.203.64.167) can't connect to archive.org (207.241.224.2), connection timeout on port 443
23:02:02<nicolas17>port 80 works
23:02:16<nicolas17>and connecting to 443 from home works
23:02:46<nicolas17>bizarre
23:04:46<nicolas17>I suppose I could change my script to use http: but ugh
23:06:29<nicolas17>ok done that for this one time