Live data from Hacker News

Archive.today is directing a DDoS attack against my blog

gyrovague.com

31–40 of 187 posts

Re: Archive.today is directing a DDoS attack against my blog

#31
post #27
post #25

Earlier quoted context omitted.

I looked at the flags and they seem to be legit flags from legit users. My guess is that they thought this was below-the-radar drama that wasn't on topic for HN. (I could make a "people who flagged X also flagged" list a la https://news.ycombinator.com/item?id=46771900 to support the point, but it's a time-consuming pain so I'd rather not!) Edit: after looking at this more closely, I have a counterintuitive (to me at…

This is definitely interesting and HN-worthy. If nothing else, archive.today links are posted on tons of HN submissions, so it's topical.

I agree - it's clear that archive.is / archive.ph / archive.today / who-knows-what-else has been a lubricant in many HN threads, letting people read things they otherwise couldn't, and that increases the interest of the topic.

I suppose I should add that we prefer archive.org links when they're available, but often they aren't.

Edit: I suppose I should also re-add that we have no knowledge of or opinion about what's going on in the dispute at hand.

Re: Archive.today is directing a DDoS attack against my blog

#32

[flagged]

Please, let's not re-fight WWII on HN.

We know that the impact from that time is far from worked through, but to the extent it shows up here, commenters should make the effort not to fall back into war mode.

You're welcome on HN, and so are the users you disagree with—but you all (i.e. we all) need to stay within the site guidelines when discussing tough stuff. These include: "Comments should get more thoughtful and substantive, not less, as a topic gets more divisive." - https://news.ycombinator.com/newsguidelines.html

p.s. This comment is not just for the user I'm replying to but everyone else who's expressing strong feelings below. It's amazing, and totally human, how alive these feelings are after 80+ years, but at the same time, 80+ years of distance should give us the ability to relate to each other a little bit better than our grandfathers and great-grandfathers were able to.

Re: Archive.today is directing a DDoS attack against my blog

#33

previously https://news.ycombinator.com/item?id=46624740

See also https://archive-is.tumblr.com/post/806832066465497088/ladies...

also Archive.today: on the trail of mysterious guerrilla archivists of the Internet - https://news.ycombinator.com/item?id=37009598 August 2023

Re: Archive.today is directing a DDoS attack against my blog

#34

Why is this flagged? Given the content, I find this suspicious.

I didnt flag the article, but anecdotally, I was initially unable to load the article at all. It mentions how it ended up in an adblock list. The article makes it sound like this is a good thing, as it stops the DDOS, but it isn't preventing people from loading the page directly. That may be true for people using an adblocking extension, but my adblocking DNS seems to be blocking it based on that same list. I had to manually tweak my dns-based adblocker to allow the domain in order to read the article.

Re: Archive.today is directing a DDoS attack against my blog

#36

Earlier quoted context omitted.

Finland did send hundreds of people to be murdered in Nazi concentration camps.

No, it did not. Unless you count the Soviet POWs who were murdered in Stalin's gulags. https://en.wikipedia.org/wiki/History_of_the_Jews_in_Finland...

Finland starved thousands to death in it's own camps. https://en.wikipedia.org/wiki/East_Karelian_concentration_ca...

Re: Archive.today is directing a DDoS attack against my blog

#37
post #28

It is academically very interesting to think about this in light of their long-standing dispute with Cloudflare ( https://community.cloudflare.com/t/archive-is-error-1001/182... ) over EDNS, which could have privacy implications attached. I think no matter how you slice it though, it's unethical and reprehensible to coordinate (even a shoddy) DDoS leveraging your visitors as middlemen. This is effectively coordinatin…

It's definitely interesting to see this roll around since the only individuals that see the CAPCHA page mentioned, are users of Cloudflare's DNS services (knowingly or not).

P.S. Shout-out to dang for dropping the flags. I have a small suspicion that their may be some foul play, given the contents...

Re: Archive.today is directing a DDoS attack against my blog

#38
post #17

Earlier quoted context omitted.

"Gyrovague", the author of the post we're commenting under has for reasons unknown engaged in targeted harassment of the owner of "archive.today". Now the owner of archive.today is attempting a rather lazy DoS attack against gyrovague.com. A rather mild response to gyrovague attempting to bring the archive.today owner physical harm by spreading potentially identifying information about them. There's really very littl…

Like I said, I can't tell who is attacking who. Archive.is has more money, resources and ASN's than Akamai so surely they can mitigate anything anyone can throw at them. A little forum trying to respond in kind can't really be much of a threat. Archive could just tell their controlling nodes to ignore any requests to mirror the forum which means there is a lot more to this than any of us are seeing. That is why I wou…

> Archive.is has more money, resources and ASN's than Akamai so surely they can mitigate anything anyone can throw at them.

This statement makes me think you're misunderstanding the person above you.

They're saying this blog author, gyrovague, is doxing¹ Archive.is. I am wondering if you are misreading that as DoSing. To "dox" is to reveal the identity of, typically for purposes of harassment. To "DoS" is to spam with requests. Archive.is is not being spammed with requests, nor do I see anyone here suggesting they are except here: "resources and ASN's … mitigate anything anyone can throw at them" … that seems to indicate you're (mis)reading it as "DoS"?

(I.e., gyrovague is doxing the Archive.today owner¹. Archive.today is, in return, DoSing gyrovague.)

(¹I'm not trying to comment on whether that term is being appropriately applied here, or not.)

Re: Archive.today is directing a DDoS attack against my blog

#40

previously https://news.ycombinator.com/item?id=46624740

Interestingly, theres an account in that thread claiming to be from Gyrovague, but its not the same one thats in this thread, which has been confirmed to be legit as it is mentioned by name in this latest Gyrovague article.

I wonder, is the newer gyrovague-com account because they lost the login for the old one? or was the old one a different person? Hopefully they can clarify, because if there's an account pretending to be them that makes this story even more confusingly weird.

Post reply on HN