> On 22 Oct 2026, at 12:17, Tim Parenti via tz <[email protected]> wrote:
> 
> I will add that, if there is any useful semi-recurring task here that one 
> could automate, it would be quite a light one and not really part of this 
> project, though supportive: Whenever there is a new tz release, it would be 
> nice to ensure that the handful of new links throughout end up being 
> submitted to Wayback for archival if they haven't been already.  This would 
> help those future researchers when they do inevitably come across a dead 
> link, helping stem the effects of future linkrot.
> 

I looked into this a few years ago (well before the current days of AI bots) 
and got a decent project going with some fairly simple Python scripts. But it 
hit some hurdles that stopped me from running it regularly.

One interesting catch I found is that just checking Wayback for a broken link 
isn't enough; you need to also check around the date that the link was first 
added to the tzdb files. There were some links that I think had detailed 
information when they were first added to the Wayback archive, but years later 
became generic landing pages, which also got archived. So just using the latest 
archived version can sometimes give the wrong page.

There were also some links for news websites that have had revamps and just 
redirect all old links to their home page. Trickier to auto-detect because 
they're still valid redirects, just with no useful information at the end (it's 
more of a judgement call about whether the links need updating).

I can probably look into reviving that old project, if for no other reason than 
my own inherent curiosity.

Cheers,
Gil

Reply via email to