Archive.today links going forward

2 hours ago (reddit.com)

Archive.today = archive.is - which is added via comment on a huge percentage of posts on HN.

Link to comment explaining the discovery:

https://old.reddit.com/r/Seattle/comments/1xhf6qp/archivetod...

edit: Maybe I should have titled this "claim to have discovered" as there is no external verification, and no write up. I thought I should post this in any case.

Not sure what to believe here. Wouldn't it be possible to create a site that has some js embedded that is able to be aware of archive's process so that the archived page renders a different page than the original? Could that secondary page be what is trying to deliver the malware, using archive as an unwitting laundry? That matches the MO of malware delivery via other services, no? I'm baffled as to why the mods don't provide any details whatsoever. There are more links to the controversy between the blogger who sought archive's webmasters identity than details of this incident. The mods in this subreddit are doubling down on not sharing details under the guise of "not our job to be infosec". Perhaps a write up is in due time but at the moment this feels like a sketchy of the aforementioned drama

  • It looks like the some reddit mods on a power trip. Zero actual evidence presented.

    • Is it a power trip stemming from a technical misunderstanding (archive.today exploited to deliver malware =/= archive.today attempting to deliver malware) or is it something else? In any case, reading the comments on reddit, seems like the mods are going out of their way to appeal to hysterics.

      Unbelievable that the comment asking for evidence sits at -24 upvotes in that thread as of now. https://www.reddit.com/r/Seattle/comments/1xhf6qp/archivetod...

I think it's a shame that copyright laws don't allow us to host a non shady alternative to this. The only reason people use such dubious sites is that there's no other way to share a link to a news site without risking that the text will be altered later or hidden behind a paywall.

They really need to show some evidence for this! Just this suggestion means I won't ever use it again

The writing had been on the wall for a while. Hopefully this'll finally drive the usage of the site down.

  • Surprised that using visitors for DDoS attacks wasn't enough already.

    • Residential proxies DDoSing half the internet is standard operating procedure this decade and yet everyone still buys connected garbage and monetizes their apps this way.

    • not sure why this is downvoted. they modified their captcha so that visitors contributed to a ddos against a blog, on top of a handful of other threats, tampering of archived data, etc.

      they are not great people.

      2 replies →

    • There's been quite a lot of people still defending the site. Basically "who cares about DDoS attacks and altering archived sites' content when it allows bypassing paywalls?"

      2 replies →

Disappointing but not that surprising; it's been banned from Wikipedia for months because it was enlisting viewers' computers in a DDoS against an investigative journalist for trying to figure out who was behind it. But it's the only way I've found to access a lot of information that is otherwise lost. So, what do we do?

Until somebody invents a solution for bypassing paywalls at scale, they are not going away. It's like people asking "why don't AI companies release their training data".