Hacker Newsnew | past | comments | ask | show | jobs | submit | DoctorOW's commentslogin

> 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 all the right tools to publish information the governments and the largest of companies want silenced.

Ideally, there would be no such information in the first place. However, the reality is that this classification has only been broadened to cover more content since the invention of the Internet, regardless of which political parties are in power. The fact that the owner of Archive.today is chased by the FBI even though the website already blocks archival of the kinds of content all of us would unanimously find disturbing speaks for itself.


Internet Archive's trustworthiness took a hit when they waded into fact checking - https://blog.archive.org/2020/10/30/fact-checks-and-context-... and wiping content they disapproved of - https://news.ycombinator.com/item?id=32743325


> content they disapproved of

> Looks inside

> Literal scum of the earth engaging in coordinated harassment campaigns to get people they hate kill themselves, and celebrating their "success"

Sure, the problem with Kiwi Farms is that people "disprove of them", not what they disprove of. KF were even blocked by CloudFlare, who have a very strong neutrality policy, that's how toxic, hateful and illegal they were.


All your comments are right wing shilling

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.

archive.org supports DMCA. If you don't like some information in the Wayback Machine, you just have to send a form email and it will be removed from the Waybaeck machine.

archive.today/is/ph is adversarial. It archives things that don't want to be archived. That's why Trump's FBI is trying to unmask it.


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?


> 4. HN promotes doxing.

Source:


taking this very post from flagged trash can and posting again - is definitively a such act

I'm going to be honest, I always felt like the verbosity was the point of Go. Iirc the whole reason it was invented was to let codebases be as readable as they are writable even for less experienced developers. Why are there Error types when exceptions exist? To force you to acknowledge the possibility for errors. You can easily let your frameworks and libraries handle recovering from panics, but err is unavoidable. You have to, at the very least, put the _.


Which is great until you have to troubleshoot an error code surfaced by a nasty web of code with no idea where it came from because the simplest way to handle err is to re-return it, optionally (and more or less uselessly) wrapping it in a new err. I'll take a panic with a stack trace over that any day.


The trouble with Go is that, because the language is so simple, the obvious way to do a thing always has a bunch of drawbacks. Taking care of gotchas at a language level means complicating the language, but refusing to do so means complicating code written in your language.

There's a balance to be struck here, but Go is stingy, so you don't get things like error traces and automatic destructors and const semantics even when they would make Go a much simpler language to use.


> Perhaps the poster's curiosity is "Why is the Dallas Morning News hiring a faith reporter?"

Indeed, thank you.


Happy to help.


The root of the issue is "ChatGPT people" are using artificial intelligence to replace... intelligence. Nobody, not even ChatGPT people, wants to actually read that drivel.


If it helps you in talking yourself down from domestic terrorism, IRS is just law enforcement. Killing IRS agents won't lower your taxes, in the same way killing police officers won't legalize anything.


I agree. Which is why I have not yet performed a domestic terrorism. Usually I express my disgust by writing things like "domestic terrorist" in the job title box on my tax return.

But I do give it serious thought, with the quandary normally being: do I have the capacity (and the willingness) to inflict such an impression that I can terrify people from choosing to work for the IRS?


> consider Hey, Basecamp, Shopify

Basecamp is slow as hell, Shopify depends on some insanely specific tuning, and I don't use Hey but it's the same team as Basecamp IIRC.


Why do I need to help? Is this an experiment to see if it can do it on its own, or just another "project" where they give AI credit for human's work for marketing purposes?


I knew it.


I read somewhere (404 media? ) that they spent more on AWS than they got in revenue for 2025.


After getting $8bn in investment from Amazon... (as of nov 2024)


Never in my life have I heard of this security issue.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: