I don't see the point in doxing anyone, especially those providing a useful service for the average internet user. Just because you can put some info together, it doesn't mean you should.

With this said, I also disagree with turning everyone that uses archive[.]today into a botnet that DDoS sites. Changing the content of archived pages also raises questions about the authenticity of what we're reading.

The site behaves as if it was infected by some malware and the archived pages can't be trusted. I can see why Wikipedia made this decision.

▲

jsheard 3 hours ago | parent | next [-]

It's also kind of ironic that a site whose whole premise is to preserve pages forever, whether the people involved like it or not, is seeking to take down another site because they are involved and don't like it. Live by the sword, etc.

▲

cardanome 26 minutes ago | parent | prev | next [-]

As far as I understand the person behind archive.today might face jail time if they are found out. You shouldn't be surprised that people lash out when you threaten their life.

I don't think the DDOSing is a very good method for fighting back but I can't blame anyone for trying to survive. They are definitely the victim here.

If that blog really doxxed them out of idle curiosity they are an absolute piece of shit. Though I think this is more of a targeted campaign.

▲

ddtaylor 3 hours ago | parent | prev | next [-]

Did they actually run the DDoS via a script or was this a case of inserting a link and many users clicked it? They are substantially different IMO

▲

dunder_cat 3 hours ago | parent | next [-]

https://news.ycombinator.com/item?id=46624740 has the earliest writeup that I know of. It was running it via a script and intentionally using cache busting techniques to try to increase load on the hosted wordpress infrastructure.

▲

jsheard 3 hours ago | parent | next [-]

> It was running

It still is, uBlocks default lists are killing the script now but if it's allowed to load then it still tries to hammer the other blog.

	▲	dunder_cat 3 hours ago \| parent [-]
		Ah good to know. My pi-hole actually was blocking the blog itself since the ublock site list made its way into one of the blocklists I use. But I've been just avoiding links as much as possible because I didn't want to contribute.

▲

RobotToaster 2 hours ago | parent | prev | next [-]

Given the site is hosted on wordpress.com, who don't charge for bandwidth, it seems to have been completely ineffective.

▲

Hamuko an hour ago | parent [-]

The speculation that I saw was that they'd try to get Wordpress.com to boot him off for being a burden on the overall infrastructure.

	▲	chrisjj an hour ago \| parent \| next [-]
		As if Wordpress.com was that dumb...
	▲	ouhamouch an hour ago \| parent \| prev [-]
		[dead]

▲

ddtaylor 3 hours ago | parent | prev [-]

Thank you this is exactly the information I was looking for.

"You found the smoking gun!"

▲

hexagonwin 3 hours ago | parent | prev [-]

they silently ran the DDoS script on their captcha page (which is frequently shown to visitors, even when simply viewing and not archiving a new page)

▲

jMyles 3 hours ago | parent | prev [-]

> Changing the content of archived pages also raises questions about the authenticity of what we're reading.

This is absolutely the buried lede of this whole saga, and needs to be the focus of conversation in the coming age.