Live data from Hacker News

Archive.today is directing a DDoS attack against my blog

gyrovague.com

161–170 of 187 posts

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

#161

Earlier quoted context omitted.

Me for one. Adding an auto-updating IP address blocker to my personal blog site would probably cost more than setting up the whole site did in the first place.

We're talking about sites that make their living via subscriptions. They should have a great interest at blocking archive.is, which is, by the way, the only service that can reliably bypass many paywalls. Clearly whatever they're doing is not easily replicated.

> We're talking about sites that make their living via subscriptions.

Sorry, but I wasn't. I thought that was clear from "can't afford the cost of keeping up-to-date with the Google IP list".

> They should have a great interest at blocking archive.is

Agreed, and many should have a budget to suit. So I conclude archive.is has put a lot of effort and cost into its defence. And all for free to us, the users.

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

#162

Earlier quoted context omitted.

How is it misrepresentative of the situation?

Because none of the names are real and they were all already posted publicly previously. This is covered in the article.

We don't know that none of the names are real. And even if they aren't, the article is still showcasing his failed attempt at doxing the owner of archive.today and providing a starting point for anyone else wanting to try.

> they were all already posted publicly previously

Doxing very often consists of nothing more than collecting data from a bunch of public sources

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

#163

Earlier quoted context omitted.

Because none of the names are real and they were all already posted publicly previously. This is covered in the article.

We don't know that none of the names are real. And even if they aren't, the article is still showcasing his failed attempt at doxing the owner of archive.today and providing a starting point for anyone else wanting to try. > they were all already posted publicly previously Doxing very often consists of nothing more than collecting data from a bunch of public sources

> Doxing very often consists of nothing more than collecting data from a bunch of public sources

I simply don't agree that this looks like doxing. No addresses or even any private information were reported. It's just a Google using WhoIs data and, in one case, the person said, in a public forum, that archive.is is "my website." Why would they have said that if they were worried about people finding out who it belongs to?

If they'd have stumbled upon an address to a private residence and reported that, sure, that would look like doxing. I just don't see it here.

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

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

There is a perception that the use of the archive by the HN community has some positive value for the archive.

But in fact:

1. HN uses a free service that someone else pays for.

2. HN abuses its paywall bypass function, which is not its main function, is not advertised (unlike 12ft).

3. HN creates legal problems for the archive by highlighting and framing the archive as a paywall-circumvention tool first.

4. HN promotes doxing.

Who would be more motivated in reducing traffic here?

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

#166

Earlier quoted context omitted.

[flagged]

[flagged]

If you don't understand how a democracy with actual police reports work, maybe just shut up? Maybe just check the police reports? Maybe build a platform where no morons auto delete everything that's against their extremist belief? And maybe also don't believe everything that kids type online in their devtools?

Just some hints, kid.

@dang are you effing serious? Why are you tolerating users like this guy but then strike me for pointing out that there's a doxxing campaign going on against the author, which the author literally mentions in the linked article?

I'm really disappointed by the moderation double standards here.

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

#167

Earlier quoted context omitted.

Most paywalls just allow search engines to read their content just fine. Because they do want discoverability, they want their cake and eat it. There's a few publications that don't even do that though and archive.is is very good at bypassing them so I do imagine they use logins for those, but for the masses of sites it's not currently necessary.

Then why hasn't anyone built a client-side browser addon that impersonates a suitable search engine?

They have. It's called bypass-paywalls-clean . It works pretty ok.

It just keeps getting banned from the addon catalogs because of complaints from media. The Firefox one was taken down by a french newspaper. So you have to sideload it, which is hard to do on Android.

Edit: it looks like even the github was taken down now: https://github.com/iamadamdev/bypass-paywalls-firefox

But yes it exists. And it works for most sites. It's just hard to get it now.

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

#168

Earlier quoted context omitted.

What serious operator of a service isn't budgeting time to implement and operate critical maintenance functions?

Me for one. Adding an auto-updating IP address blocker to my personal blog site would probably cost more than setting up the whole site did in the first place.

Have you actually priced it, or are you just guessing?

Are you doing regular patching? Automated restarts? Watching for security breaches? Or just praying it stays up forever?

Otherwise, respectfully, I would not classify you as a "serious operator." Your site could live or die, and it would be all the same to you. Or, you've handed it to a third party for management and they don't offer much in the way of resilience or stability.

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

#169
post #96

Earlier quoted context omitted.

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

I don't think these two are exactly equivalent. Internet Archive is a registered non-profit organization. It is more trustworthy and accountable, but it cannot realistically stand against government-imposed censorship. We've seen this unfold before with Twitter and Meta, partly with Telegram. Archive.today may be similar on the surface, but if you take a closer look, it's actually an underground "evil twin" that has…

If you don't like Archive.org use something else, there's plenty of ways to archive something. I think the idea that the world's most powerful organizations are trying and failing to pursue this makes "Should we shut it down?" all the more ludicrous a question.

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

#170

Earlier quoted context omitted.

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

There is a perception that the use of the archive by the HN community has some positive value for the archive. But in fact: 1. HN uses a free service that someone else pays for. 2. HN abuses its paywall bypass function, which is not its main function, is not advertised (unlike 12ft). 3. HN creates legal problems for the archive by highlighting and framing the archive as a paywall-circumvention tool first. 4. HN promo…

> 4. HN promotes doxing.

Source:

Post reply on HN