Hacker News Reader

Maybe an enhancement would be to have it look at the edit history and use the most recent URL that has remained on the page for at least X hours/days

One challenge with this approach can be seen by considering a scihub takedown followed immediately by a correction to a new TLD. The new(and suddenly correct) address would be changed to an incorrect old address.

pop up a warning instead to say there's been churn and let the user pick?

That would take way too long.

This is possible with the DNS already which is why there have been various efforts to try to harden the protocol, to varying effect so far.

Sure but that requires knowledge of DNS, and a bad edit on wikipedia is much more accessible.

Are you saying it's not a good idea to rely on domain lookup from a public wiki?

I think you might be onto something...