I would wager that this use case is much more prevalent than ones where the LLM changed the comment significantly enough to change one's voice.
I never copy/paste from an LLM into HN. Everything is typed by myself (and I never "manually" copy LLM content). I don't have any automatic tools for inserting LLM content here.[1]
Always, always, always keep in mind that you don't notice these positive use cases, because they are not noticeable by design. So the problematic "clearly LLM" comments you see may well be a small minority of LLM-assisted comments. Don't punish the (majority) "good" folks to limit the few "bad" ones.
Lastly, I often wish we had a rule for not calling out others' comments as "AI slop" or the like.[2] It just leads to pointless debates on whether an LLM was used and distracts far more than the comment under question. I'm sure plenty of 100% human written comments have been labeled as LLM generated.
[1] The dictation one is a slight exception, and I use it only occasionally when health issues arise.
[2] Probably OK for submissions, but not comments.
I was thinking of calling this service "Dang It."
You say you want hear posts in other people's voices but I'm pretty sure that if I did this that the people who used it would find greater acceptance of their comments than if they just posted them as they originally wrote them.
But that name is hilarious!
It's a bit different when specific cases come up because then there's a chance to talk about it, add clarifying comments, etc.
For me that link says:
> Error: Forbidden
> Your client does not have permission to get URL / from this server.
https://hn.algolia.com/?dateRange=all&page=0&prefix=false&qu...
How the hell does does this place exist right now with all that is going on. I dont know much about YC, but they don't seem that humane..
The short version is that we included it to protect users who don't realize how much damage they're doing to their reception here when they think "I'll just run this through ChatGPT to fix my grammar and spelling". I've seen many cases of people getting flamed for this and I don't want more vulnerable users—e.g. people worried about their English—to get punished for trying to improve their contributions. Certainly that would apply to disabled users as well.
Here are some past cases of these interactions: https://hn.algolia.com/?dateRange=all&page=0&prefix=false&qu....
Most rules in https://news.ycombinator.com/newsguidelines.html have a lot of grey area, and how we apply them always involves interpretation and judgment calls. Mostly the ones we explicitly list there are so we have a basis for explaining to people the intended use of the site. HN has always been a spirit-of-the-law place, and—contrary to the "technically correct is the best correct" mentality that many of us share—we consciously resist the temptation to make them too precise.
In other words yes, that bit needs to be applied cautiously and with care, and in this way it's similar to most of the other rules. Trying to get that caution and care right is something we work at every day.