An archive site that alters content in the archive is worse than worthless.
The DDoS is just confirmation that the site is actively harmful.
Submitted 3 weeks ago by onehundredsixtynine@sh.itjust.works to technology@lemmy.world
An archive site that alters content in the archive is worse than worthless.
The DDoS is just confirmation that the site is actively harmful.
has it been proven that they alter archived content? haven’t heard that before
From the article:
There is consensus to immediately deprecate archive.today, and, as soon as practicable, add it to the spam blacklist (or create an edit filter that blocks adding new links) and remove all links to it. There is a strong consensus that Wikipedia should not direct its readers towards a website that hijacks users’ computers to run a DDoS attack (see [WP:ELNO#3]). Additionally, evidence has been presented that archive.today’s operators have altered the content of archived pages, rendering it unreliable.
Evidence was presented here: en.wikipedia.org/wiki/…/Archive.is_RFC_5#Evidence…
Deeply saddening. Archive.today was a great resource, and stored a vast repository of human knowledge. As the internet turns to slop, we need sites that preserve the history of the web more than ever, and it’s very disappointing that the team at archive.today has failed us so profoundly in our hour of greatest need.
It is not clear to me why archive.today is so important given the continuing existence of archive.org.
Because having one thing is never good. IA goes down then what? Also archive.today captures websites differently which can work in a pinch when IA fails to archive a site.
It does more to handle client-side rendering than archive.org, so there are pages that could be rendered by today that were not archivable by org. Also, because of differing usage patterns, it has archives of pages that org didn’t, and even for pages that org does have, at times org doesn’t.
Automation won’t do it right. And that’s the goal.
Besides, Wikipedia has always been human written for humans. Or at least, that too is the goal.
Quacksalber@sh.itjust.works 3 weeks ago
Archive.today apparently hijacks visitor’s browsers to DDoS a blog that tried to uncover the identity of the archive’s admin. UBlock helps to stop that script.
helpImTrappedOnline@lemmy.world 3 weeks ago
Another example why Unlock Origin should be considered essential security software, not just an “ad-block”.
Damage@feddit.it 3 weeks ago
If a tool is demonstrably indispensable to disable some browsers’ functionality, is it wise for browsers to have that functionality?
otter@lemmy.ca 3 weeks ago
Would that be by default, or do I need to enable something specific
kip@piefed.zip 3 weeks ago
from the blog in question
- https://gyrovague.com/2026/02/01/archive-today-is-directing-a-ddos-attack-against-my-blog/
can’t find anything from a quick look that confirms this list is used by default in ublock though
pkjqpg1h@lemmy.zip 3 weeks ago
It’s by default easylist-privacy list is default
SkaveRat@discuss.tchncs.de 3 weeks ago
from what I heard, the default one is enough. Although I haven’t checked it
Quacksalber@sh.itjust.works 3 weeks ago
I don’t know more than what the wiki article linked to. It says UBlock blocks it. It doesn’t say any more than that.
hector@lemmy.today 2 weeks ago
I would be happy to contribute some browser action to ddos some fucking mercenary blog post working for tech parasites.
sakuraba@lemmy.ml 3 weeks ago
makes sense, I didn’t get it when people started saying it but I don’t browse without ublock