Comment by ksbd-pls-finish
1 day ago
I clicked that link and I don't see anything wrong with that. It's not like I donate money by doing that. And they still are very useful resource, even if they're not good enough for Wikipedia (if they indeed tampered with some old archives, it's pretty obvious why)
Thank you for the heads up! DDOS attacks are pretty concerning, but even more concerning is the potential alteration of content. Diabolical. That said, journalism needs funding more than ever, please if you can, try your best to pay for it.
I think that archive links should be made to include a cryptographic hash of the file; this can prevent alteration of content (including of the original file that it is copied from) but also can allow alternative sources of the file to be found (or verified to be correct) according to the hash. (If someone is concerned they want their username removed, they could perhaps edit their copy of the file first and then archive it, although they should have someone to trust if it matches the original one or not, if it has been modified in this way (or any other way, e.g. removing some scripts and CSS etc).)
Why is it obvious why they tampered with old archives? Why did they tamper with old archives?
> Why is it obvious why they tampered with old archives? Why did they tamper with old archives?
See section "Blog capture tampered with":
* https://arstechnica.com/tech-policy/2026/02/wikipedia-bans-a...
Also:
> On 20 February 2026, the English Wikipedia banned all links to archive.today, citing the DDoS attack and evidence that archived content was tampered with: Discussion had discovered that instances of Nora's name were replaced with Patokallio's and that "Nora" was likely an appropriated identity—the name belonged to a real person, whose only connection to archive.today had been a prior content takedown request.[18][17][19] The community's decision was made despite concerns over maintaining content verifiability—partly undermined by the discovery of the alterations— while removing and replacing the second-largest archiving service used across the Wikimedia Foundation's projects. The Wikimedia Foundation had stated its readiness to take action regardless of the community verdict.[18][20] Patokallio expressed his satisfaction with the outcome.[3]
* https://en.wikipedia.org/wiki/Archive.today#Attack_on_Gyrova...
> Specifically, AT's maintainers reportedly tweaked snapshots of a third-party blog post that Patokallio referred to in his February 2026 article about the DDoS attack. AT changed the name of a "Nora" person in said post to Jani Patokallio, making it look as if he had written some comments there. Eagle-eyed Wikipedia editors spotted the alterations, which have since then been reverted, but the action made it easy for them reach a final decision.
* https://www.tomshardware.com/software/search-engines/wikiped...
"it's pretty obvious why" here refers to why Wikipedia would reject them as a source.
Looking for the answer to this myself as well. Seems like a bit of conjecture
Maybe not, but it could be using your browser as a part of a DDoS network. The admins have also been tampering with archived articles.
A DDoS against a blog that iirc was attempting to dox the archive.today maintainer.
The bit about tampering with archived pages is news to me though. Wish the wiki discussion included receipts. Is "two users report they were redirected to tehrantimes.com" what is being referred to when they say archived pages are being tampered with?
It looks like the "tampering" was mostly just removing the username of the person submitting the links, so they wouldn't get banned by paywall sites, and archive.today has always done this: https://en.wikipedia.org/wiki/Wikipedia:Requests_for_comment...
And it looks like in some instances they changed their own alias to the name of the blogger they're in dispute with, in a fit of pique.
You have to scroll down to get hints because the conversation has been redacted, and the evidence is not provided with side-by-side comparisons.
I understand the ethical concerns about linking to the site but the blanket accusations of "tampering" seem a bit disingenuous, since no article content was ever changed afaik.
3 replies →
Not mine, UBlock has blocked that since day one, thankfully
DDoSing who? Doesn't CORS help here?
cors stops the browser from reading the response but the request still gets processed by the server
1 reply →
If you would open the second link provided you would get an answer.
>This decision was agreed on after a request for comment with more than 200 participants concluded in February 2026, and is due to multiple concerns, including the site using editors' and readers' computers to run a denial-of-service attack and evidence that the website has tampered with some archived pages