Archive.today is directing a DDoS attack against my blog
51–60 of 187 posts
Re: Archive.today is directing a DDoS attack against my blog
#52Why does this say it's been posted 8 hours ago but on hn.algolia.com is archived 2 days ago, also I'm sure I already saw it yesterday.
Re: Archive.today is directing a DDoS attack against my blog
#53Also, as someone interested in OPSEC and OSINT as a hobby, I find the measures taken by the .is webmaster, especially the dedication to setting up countless fake accounts for each persona, to be very intriguing. I spent about an hour looking into the Nora Puchreiner persona and all the accounts registered to it that I could find. It appears that "Tomas Poder" is another alter-ego used by the .is administrator. Nora also seems to have a sister: "Sara Puchreiner". Again, all very interesting and I can't seem to make a clear picture of the situation.
Re: Archive.today is directing a DDoS attack against my blog
#54Archive.today does not seem to have worked for people connecting from Finland since mid-January, it just gives an endless captcha loop. Is this related to whatever this drama is?
Re: Archive.today is directing a DDoS attack against my blog
#55- 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 somewhere where it has real power; realistically speaking, who wouldn't be losing it?
- The blog post is preserving information that could aid further investigations even if purged from the original sources, and reveals non-OSINT information in the follow ups
- At the same time, it's, to say the least, hypocritical of the archive.today owner to attempt forcefully taking the original post down, when archive.today itself is an OSINT tool
I don't think there's a way to fairly untangle this mess anymore.
Hence, I'd focus on the possible outcomes: do we want archive.today taken down over this? Who would lose and who would benefit the most from this takedown?
Re: Archive.today is directing a DDoS attack against my blog
#56Archive.today does not seem to have worked for people connecting from Finland since mid-January, it just gives an endless captcha loop. Is this related to whatever this drama is?
Re: Archive.today is directing a DDoS attack against my blog
#57previously 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 pretendi…
Re: Archive.today is directing a DDoS attack against my blog
#58… seems like we the HN community should find a new site to mirror with.
There isn't one. As far as I know, no one really knows for sure how they bypass all these paywalls. (Most credible theory I heard: They actually just pay for the subscriptions.)
Re: Archive.today is directing a DDoS attack against my blog
#59Re: Archive.today is directing a DDoS attack against my blog
#60It 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...
I don't think this is true. I run my own recursive DNS resolver, and get a CAPTCHA when visiting archive.today.