points by shagie 1 day ago | 0 comments
From historical posts on HN:
Archive.today is directing a DDoS attack against my blog https://news.ycombinator.com/item?id=46843805 (8 months ago, 366 points, 178 comments)
Ask HN: Weird archive.today behavior? https://news.ycombinator.com/item?id=46624740 (9 months ago, 140 points, 71 comments)
[–] consumer451 1 day ago
For everyone's information: r/Seattle's mod team has stickied this technical debrief in response to this HN post. We are the "external site" that is kinda brigading them.
https://www.reddit.com/r/Seattle/comments/1xhf6qp/archivetod...
[–] Vaushite 1 day ago
Wasn't the "victim" trying to get the "attacker" life in prison for the crime of archiving public information?
[–] neuronexmachina 1 day ago
What is this referring to? I tried to find when Jani Patokallio tried to get the people behind archive.today imprisoned, but can't find anything.
[–] oytis 1 day ago
Yeah, everyone is freaking out about the (not very efficient as I can see) DDoS attempt, but it was a response to a totally unprovoked attempt to deanon the maintainer which could cost them freedom at least - and us all the only more or less reliable paywall remover.
[–] dspillett 1 day ago
I tend to think that being an arsehole when provoke is still being an arsehole. There are other ways to defend against such an attack than sending the boys¹ round to play bully², that was no better than throwing bricks through all their windows and I assume that we are civilised enough here that wouldn't condone that.
I particularly dislike the fact that I was, unbeknownst to me at the time, was coopted as part of that brigade of brick throwers.
--------
[1] a significant chuck of the internet
[2] beat up his online resources
I presumed DDoS was used colloquially, but no, they literally added JS so every visitor made a request every 0.3 seconds to that blog server, in response to a blog article. Wholly malicious based on the reporting.