Live data from Hacker News

Archive.today is directing a DDoS attack against my blog

gyrovague.com

71–80 of 187 posts

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

#71
post #55

It's a puzzling situation: - The DDoS was certainly unethical and unneeded - Although the blog post only shows an extremely one-sided version of the story by skipping straight to the threats, there are reasons to think that diplomacy has also failed terribly - The website owner has all eyes of the "thought police" on them, and given the current political situation in Russia, it's more than likely they reside somewher…

> Do we want archive.today taken down over this?

I don't think that's on the table. I would say use this as your incentive to support archive.org, who has proven much more accountable. Archive.Today is weaponizing their traffic, and reducing traffic is the best way to deal with it. Vote with your feet.

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

#72
post #37

Earlier quoted context omitted.

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...

> the only individuals that see the CAPCHA page mentioned, are users of Cloudflare's DNS services I don't think this is true. I run my own recursive DNS resolver, and get a CAPTCHA when visiting archive.today.

I use my ISP's default DNS servers and have consistently gotten the CAPTCHA page for weeks now. The CAPTCHA seems to be broken too, rendering archive.today entirely inaccessible.

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

#76
post #72

Earlier quoted context omitted.

> the only individuals that see the CAPCHA page mentioned, are users of Cloudflare's DNS services I don't think this is true. I run my own recursive DNS resolver, and get a CAPTCHA when visiting archive.today.

I use my ISP's default DNS servers and have consistently gotten the CAPTCHA page for weeks now. The CAPTCHA seems to be broken too, rendering archive.today entirely inaccessible.

Someone has suggested that CAPTCHA is broken for everyone in Finland.

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

#77
post #61

Earlier quoted context omitted.

This is a regular HN feature where admins resurrect old posts that did not get the attention they maybe deserved.

... and the resurrection falsly associates the timestamp of the admin's action with the originator's posting. Needs attention.

I'm pretty sure that's intentional because the timestamp used to calculate where the article shows up on the front page.

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

#79
post #65
post #31

Earlier quoted context omitted.

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…

> we prefer archive.org links when they're available Interesting. May we know why?

Perhaps because the admins of archive.org don't go around DDoSing random blogs I'd reckon.

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

#80

… seems like we the HN community should find a new site to mirror with.

I think there are multiple hurdles that make a new competitor very unlikely.

The first one is money. You need lots of it to run such an operation (servers, IPs, paying to bypass all these paywalls, etc.).

The second one is the legality, as no one wants to be hunted by the FBI, especially not for running a website that is also losing money.

Post reply on HN