DDoS hit blog that tried to uncover Archive.today founder’s identity in 2023. […] A Tumblr blog post apparently written by the Archive.today founder seems to generally confirm the emails’ veracity, but says the original version threatened to create “a patokallio.gay dating app,” not “a gyrovague.gay dating app.”
https://www.heise.de/en/news/Archive-today-Operator-uses-users-for-DDoS-attack-11171455.html:
By having Archive.today unknowingly let users access the Finnish blogger’s URL, their IP addresses are transmitted to him. This could be a point of attack for prosecuting copyright infringements.
As a longtime editor who makes heavy use of archive.today (it’s often much more effective than the Wayback Machine), I’m deeply conflicted about this, and this is disgusting behavior on the part of archive.today; regardless of what a piece of shit the blog owner is, I hope they see prison time for abusing their trust to perpetrate this DDoS.
Right now, the Wikipedia RfC seems pretty split. This is a complicated issue, so I’m going to need to read and think more before I chime in. Just wild.
I don’t really see it as a complicated issue. Archive[.]today is now an unreliable source that uses its user traffic to engage in malicious activities. By using it, Wikipedia will become unreliable by proxy.
The best course of action is to distance yourself from it as quickly as possible.
Is it really an “unreliable source”, though? The owner of the site is acting maliciously with regards to this DDOS, of course, but that doesn’t necessarily mean he’s going to act maliciously about the contents of archive.today itself.
One could make the case that the owner of archive.today was already flagrantly flouting copyright law, and therefore a criminal, and therefore “unreliable” right from the get-go. Let’s not leap to conclusions here.
Using visiting clients for attacking makes the site malicious, and it’s because the owner decided it should be, not because it was hacked or got served “spicy” ads or something.
Since this jarhead has no qualm in weaponizing his site, dragging every visitor into this, and threatening the owner of a small blog with creating a whole category of AI porn just for a blog post from 2 years ago: what if he decides he could use visiting clients for other uses, like crypto mining? If my wiki had 700k links pointing there, i’d think hard about my choices, and would want to reduce my dependency on such a source.