Around January 11, 2026, archive.today (aka archive.is, archive.md, etc) started using its users as proxies to conduct a distributed denial of service (DDOS) attack against Gyrovague, my personal blog. All users encountering archive.today’s CAPTCHA page currently load and execute the following Javascript:
Posting this here since the dispute was started over a PII concern.
Link to a post a while back about archive.is (and other archive.* sites) sending data to Russia. Post discusses this article
The linked article is nothing more than incompetent, bad-faith fearmongering. It has already been debunked in this comment. Long story short: literally every request mentioned in this article is blocked by any ad blocker with default settings, which you should be using anyway.
Thanks very much for the link. Appreciate your research and explanation. Always grateful to learn from others. Have a PiHole and use uBlock. Thanks again.
Victim blaming may not be the answer you think it is.
literally
I’m a bit of a troglodyte, I had to look up what PII referred to.
Whoever is doing the responding and the petty bullshit with the captcha stuff isn’t doing themselves any favors by being a gland end unnecessarily. I’m not really curious as to who is behind the archive website so the blog authors need to unmask them is lost on me admittedly. I do use the paywall bypass site, but given the person’s responses I’ll try not to use it at all going forward, for however much that actually makes a difference.
There have been a bunch of posts and articles about this. I don’t know why it keeps getting reposted on lemmy tbh. Both sides are complete dicks. From what I understand, the “poor victim” was the initial asshole and both sides have kept escalating it.
