Live data from Hacker News

Our investigation into the suspicious pressure on Archive.today

adguard-dns.io

11–20 of 473 posts

Re: Our investigation into the suspicious pressure on Archive.today

#11

Its interesting that being unable to find a legal route to dig up dirt on archive.is, they're going the route of CSAM allegations. I first heard of this technique on a discussion on Lowendtalk from a hoster discussing how pressure campaigns were orchestrated. The host used to host VMs for a customer that was not well liked but otherwise within the bounds of free speech in the US (I guess something on the order of KF/…

[flagged]

Re: Our investigation into the suspicious pressure on Archive.today

#12

Its interesting that being unable to find a legal route to dig up dirt on archive.is, they're going the route of CSAM allegations. I first heard of this technique on a discussion on Lowendtalk from a hoster discussing how pressure campaigns were orchestrated. The host used to host VMs for a customer that was not well liked but otherwise within the bounds of free speech in the US (I guess something on the order of KF/…

I doubt they’d have to. If the site truly doesn’t remove CSAM automatically I’ve no doubt plenty of it would end up there organically. You wouldn’t have to upload any anywhere, you’d only need to know some URLs to look for which presumably any major law enforcement agency would.

Re: Our investigation into the suspicious pressure on Archive.today

#13

I speculate, and the conspiracy theorist in me believes, something of a compromising nature has been archived and they want that data inaccessible, but at the same time, pointing out what they want hidden would shine a light on it. It is even more interesting the US government is coming after archive.today at the same time, or maybe that is just a coincidence, and this is just a tech-savvy philanderer trying to hide…

If we're speculating, there is another reason to censor archiving site - if you recently committed well documented genocide and want the evidence erased. Given the systematic removal of such content from social media, it would not be surprising if this was related.

Re: Our investigation into the suspicious pressure on Archive.today

#14
post #4

archive.is is frequently used to bypass paywalls, I wonder if this is motivated by that somehow

100%. It's like Lenin said, you look for the person who will benefit… and, uh, uh, you know… You know, you'll uh, uh—well, you know what I'm trying to say…

Re: Our investigation into the suspicious pressure on Archive.today

#15
post #4

archive.is is frequently used to bypass paywalls, I wonder if this is motivated by that somehow

That's most likely the reason pressure is being put on them. Big media companies successfully shutdown 12ft.io, which was used to bypass paywalls, and forced the BPC (Bypass Paywalls Chrome) browser extension off the Mozilla Extension store, then Gitlab, then Github. Now the dev is hosting it on a Russian Github clone, presumably making it untouchable.

Since archive[.]today is using some very obscure hosting methods with multiple international mirrors, it makes it incredibly difficult for law enforcement to go after.

Re: Our investigation into the suspicious pressure on Archive.today

#16

Its interesting that being unable to find a legal route to dig up dirt on archive.is, they're going the route of CSAM allegations. I first heard of this technique on a discussion on Lowendtalk from a hoster discussing how pressure campaigns were orchestrated. The host used to host VMs for a customer that was not well liked but otherwise within the bounds of free speech in the US (I guess something on the order of KF/…

It's unlikely law enforcement would take the risk to handle CSAM just to make a case against a Russian pirate, jeopardizing their careers and freedom, when the copyright case is pretty strong already.

These are the doings of one of the myriad freelance "intelectual rights enforcement agents", which are paid on success and employed by some large media organization. Another possibility is that a single aggrieved individual who found themselves doxed or their criminal conviction archived etc. took action after failing to enforce their so called "right to be forgotten".

Unfortunately, archive.is operating model is uniquely vulnerable to such false flag attacks.

Re: Our investigation into the suspicious pressure on Archive.today

#17

Its interesting that being unable to find a legal route to dig up dirt on archive.is, they're going the route of CSAM allegations. I first heard of this technique on a discussion on Lowendtalk from a hoster discussing how pressure campaigns were orchestrated. The host used to host VMs for a customer that was not well liked but otherwise within the bounds of free speech in the US (I guess something on the order of KF/…

[flagged]

Cocaine is a hell of a drug

Re: Our investigation into the suspicious pressure on Archive.today

#19
The FBI investigation might be a coincidence. Unsurprisingly, archive.today is attacked with CSAM uploads+reports all the time, you can find occasional mentions of this in their blog from 3 and 9 years ago, and I bet there was a ton of this in between.

Re: Our investigation into the suspicious pressure on Archive.today

#20

Its interesting that being unable to find a legal route to dig up dirt on archive.is, they're going the route of CSAM allegations. I first heard of this technique on a discussion on Lowendtalk from a hoster discussing how pressure campaigns were orchestrated. The host used to host VMs for a customer that was not well liked but otherwise within the bounds of free speech in the US (I guess something on the order of KF/…

I've spent enough time on telegram to see this happening more times to ban groups. Csam shit storm, content gets flagged, the group gets banned (or at least, unavailable for some time)
Post reply on HN