Hrrm :-(

didnt the archive owner only start doing this after Patokallio revealed his identity for no good reason. Given the legal liability involved in maintaining that service, there is a threat to what Patokallio is doing so it doesn't seem entirely unsympathetic to do something in retaliation..

Seems like a mistake to rely on an archiving site that runs malware and changes the text of archived pages.

However, there’s also not really anything better out there. The owner being some wily/sketchy Russian is even an advantage in some respects, since they can’t be pressured by copyright law or foreign politics.

Well, for one, it wants me to scan a QR code as a captcha.

That is an issue you can pin on Google:

<https://reclaimthenet.org/google-broke-recaptcha-for-de-goog...> (8 May 2026).

HN discussion: <https://news.ycombinator.com/item?id=48067119>

Though yes, Archive.is have continued using reCaptcha despite this recent change.

I chose the audio option to get around this.

Me too, and ain't no way I'm doing that. That's blocklist behavior.

I've never once had that happen. It's always straight to the unrolled article.

See: <https://cybernews.com/privacy/google-qr-code-recaptcha-requi...>

Or my earlier reply to this subthread.