3,693 karma · joined October 30, 2007
---
Please send HN questions to hn@ycombinator.com.
Please don't fulminate. Please don't sneer, including at the rest of the community. https://news.ycombinator.com/newsguidelines.html
Many people from all sections of HN, the tech industry and broader society have been surprised and wrong in all directions about how the emergence of AI is playing out. I certainly have. I can't think of a single person whose predictions have been precisely accurate. So, please don't use terms like “wall of shame” and “cope”. It doesn't help anyone make better predictions and only makes you, and HN generally, seem mean.
This is obviously not true. We care about thread persistence and coherence as a default, because some of HN's most historically significant threads are from the earliest years. We will take reasonable steps to protect people's identity and safety once we know the specifics of the situation. We routinely redact URLs, company names, project names and other identifying details from historical comments to prevent people's identity from being inferred.
On a case-by-case basis we can move a selection of comments to a separate username. We of course don't want anyone to be in danger.
We can't necessarily do the exact things you've asked, because it makes all the discussion threads you participated in incoherent. We can take reasonable steps to disassociate personally-identifying comments from others.
> Please help. Death threats are not fun, especially when you have a 2 year old daughter. There is a 100+ page forum thread of people betting on when I (real name, real person) am going to die. Just saying that somewhat Doxxes me.
This sounds terrible, and of course we don't want anything like that for you. It's just not clear (and I still haven't received an email from you so I can't look into the details of the case) how the actions you're specifying that we need to take on HN will fix this issue on some other website. I don't know any details other than the limited information you're sharing here. I can't find any emails about this matter linked to the username you're commenting from here.
He (nor I) would never write that or anything like it. What we always say is that we aim to find a compromise between a user's wish for their entire history to be erased and the rest of the community's expectation that when they participate in discussion threads, those threads will persist unadulterated into the future.
We are always willing to redact PII and do other things to prevent people's real identities from being recognized from their HN activity. We help people with requests like this all the time.
Edit:
Now I can see the email in question, I can confirm that dang did not write “tough luck”. We were, and still are, happy to work with this user to redact material that reveals their identity or location from their old comments.
Idealizing killing of people is never okay on HN and we've been consistent about that for as long as I can remember.
Even if your ad hom attack was relevant: where my LinkedIn says I am based says nothing about how many people my “tax dollars have killed” or what I personally support. Digging up limited available public information about someone then making these kinds of assumptions, extrapolations and value-judgments about their level of wealth, career/life decisions and options, and political views is utterly vile. Don't ever do this again on HN; if you did this kind of thing to anyone who wasn't a moderator, the account would be immediately banned.
The facts available in the linked story indicate that there were failures at every level in the system: two teams of investigators, the prosecutors, the defense and the judge. If you have a substantive argument about how to address this kind of failure, you can make it in accordance with the guidelines.
The guidelines exist entirely so that substantive arguments can have the very best chance of being expressed and heard. Trawling through someone's limited online footprint to handwave up a whole lot of irrelevant material only indicates you don't have a strong point to make. Everyone knows that ad hominem is what you do when you don't have a strong argument to rely on, and this is about as bad as ad hom ever gets.
If your style of discourse is to declare that another human “deserves a bullet in the head”, this is not the place for you. My goodness.
In the meantime, please feel free to flag items that are badly written/unpleasant to read, and email us if something is on the front page that shouldn't be there.
It's a big additional leap to for our software to try to reach into others' sites, get through any anti-bot defenses they may be running, try to scrape their content and evaluate on whether it's sufficiently human-authored to be on HN.
There's generally a wider range of LLM involvement with a long-form post than the typical, relatively brief HN comment, which then opens the way for more debate on HN about "how much" LLM influence the post has and how much should be allowed on HN. Part of what we're trying to optimize for on HN is minimizing offtopic/meta discussion, so we don't want to encourage this kind of debate.
Our heuristic about article quality is largely unchanged from before LLMs were an issue: if an article is badly written, it shouldn't be on HN, and should be flagged.
How to think about software quality (2022) - https://news.ycombinator.com/item?id=39490543 - Feb 2024 (66 comments)
The guidelines require us to converse curiously, to be kind, and to avoid ideological battle and flamebait. To write “A judge making a “mistake” like this deserves a bullet in the head, nothing less” is obviously in breach of all those expectations.
If you want to mount a case for ways judges and other actors in the legal system should be held accountable for errors that lead to illegitimate convictions, sure, you can do so thoughtfully. This isn’t difficult.
Teach Yourself Programming in Ten Years (1998) - https://news.ycombinator.com/item?id=44697007 - July 2025 (102 comments)
Teach Yourself Programming in Ten Years (1998) - https://news.ycombinator.com/item?id=39001755 - Jan 2024 (302 comments)
Teach Yourself Programming in Ten Years (1998) - https://news.ycombinator.com/item?id=33287618 - Oct 2022 (112 comments)
Teach Yourself Programming in Ten Years (1998) - https://news.ycombinator.com/item?id=27411276 - June 2021 (115 comments)
Teach Yourself Programming in Ten Years (1998) - https://news.ycombinator.com/item?id=20543495 - July 2019 (87 comments)
Teach Yourself Programming in Ten Years (1998) - https://news.ycombinator.com/item?id=16574248 - March 2018 (51 comments)
Teach Yourself Programming in Ten Years (1998) - https://news.ycombinator.com/item?id=9395284 - April 2015 (61 comments)
Teach Yourself Programming in Ten Years (1998) - https://news.ycombinator.com/item?id=5519158 - April 2013 (86 comments)
Teach Yourself Programming in Ten Years by Peter Norvig (2001) - https://news.ycombinator.com/item?id=3439772 - Jan 2012 (29 comments)
Teach Yourself Programming in Ten Years - https://news.ycombinator.com/item?id=191235 - May 2008 (19 comments)
Norvig: Teach Yourself Programming in Ten Years - https://news.ycombinator.com/item?id=43243 - Aug 2007 (7 comments)
It's not okay to assert that anyone “deserves a bullet in the head” here, for any reason. In the case in question, clearly the system, and multiple people within it, failed to notice the issue. On HN we expect people to be thoughtful and curious, and ”bullet in the head” is a barbaric, medieval reaction to a modern scenario.
If you wouldn't mind reviewing https://news.ycombinator.com/newsguidelines.html and taking the intended spirit of the site more to heart, we'd be grateful.
So it’s an important differentiator from Garmin, which uses a proprietary connector for its charging cable, that is easy to lose/break and expensive to replace (from personal experience with a 2022 Epix).