Comment by LeoPanthera
7 hours ago
Um. You mean the same site that uses its captcha page to DDOS sites the owner doesn't agree with, and was banned from use on Wikipedia because the owner was modifying the archived pages?
https://en.wikipedia.org/wiki/Archive.today#2026_attack_on_G...
I don't think we should be supporting this random guy, no.
> to DDOS sites the owner doesn't agree with
to DDOS one website, which is doxxing the owner. Not that it makes it good idea, but it's a little more understandable.
DDoSing a website, modifying their archives surreptitiously to serve their own wants (which was what tipped Wikipedia towards banning their use), running weird sockpuppet campaigns to build dependence on them, and fucking with Cloudflare's DNS resolution to prevent anti-tracking measures from working.
Oh and even if I wanted to ignore all of this, I couldn't use them anyways because they blackholed the majority of Finnish IP ranges after the DDoS incident to I guess punish the entire country for the targeted blogger being born here.
archive.today has been targeted by Western institutions, like the FBI, for over a year now. Which signals to me they are the good guys.
4 replies →
I'm not well-informed about this situation, but DDOSing does strike me as an action which is fundamentally counter to information freedom and archival, so that seems like a reasonable suspicion to me.
I would add it was also completely ineffective since the site in question was hosted on wordpress.com, which is about as likely to work as ddosing Google.
If it works, it works. Also the Internet Archive also excludes many sites for ideological reasons which is the opposite of preservation
Not sure how well it’s “working” considering any of the archived pages might be altered by the site’s administrator to further their causes. There’s a reason why Wikipedia stopped trusting them.
I agree, it makes sense for large source-reliant projects like Wikipedia to stop using them. However, for the end-user, it's often the service that works best.
Please provide example of such cases?
1 reply →
What offends me the most is how they used visitor's compute and badnwidth for ther own purpose unrelated to the reason the visitor accessed the site, without consent or disclosure. It's MY computer, MY internet, not yours to do with it what you please
And archive.org removes perfectly legal content from their accessible archives. Nobody's perfect. The guy running archive.today has done a shit ton of good.
My beef with IA is that none of the books as listed for borrowing are borrowable anymore. Why list it then!
[flagged]
Well then another guy should provide a technically equivalent and morally superior service ;)
I mean, lots of other archive.* sites exist and do the same thing minus problematic behavior, such as archive.is, archive.oh (though maybe some are operated by the same individual...)
Are any of those not run by the archive.today guy? That site has like a dozen aliases.
Haha all of those are .today aliases. Not sure the hate over him ddosing the guy doxxing him. .today’s paywall circumvention is also why miscellaneous groups have tried to report him to the FBI over planted CSAM material, among other horrible harassment. I think we should all give him a second chance for the huge amount of time, both before and after the stupid and short lived ddos incident, that he has dedicated to archiving.
His identity must be secretive, as he has already drawn the ire of many powers that be, so… I personally think the ddos incident was justified… and I’m glad my bandwidth helped in any way, frankly. Some people seem to really want to portray him as some shady evil bad guy, and after all the hit jobs against him in the past year or two, I really wonder who these anti-archive.today people actually are and what they’re motivations are (besides money).
2 replies →
Wikipedia links these as the mirrors.
archive.today
archive.fo
archive.is
archive.li
archive.md
archive.ph
archive.vn
archiveiya74codqgiixo33q62qlrqtkgmcitqx5u2oeqnmn5bpcbiyd.onion