It will take time, but eventually everyone will know about it.
It will take time, but eventually everyone will know about it.
Note that the guidelines do explicitly say not to post about guidelines violations in comments, and to email them instead. I know this isn’t a well-loved guideline in this modern era, but duly noted: those well-intended comments are themselves breaking the guidelines.
> Please don't post insinuations about astroturfing, shilling, brigading, foreign agents, and the like. It degrades discussion and is usually mistaken. If you're worried about abuse, email hn@ycombinator.com and we'll look at the data.
If so, that seems different. If not, can you clarify?
- I insinuate that you are a bot (often shortened to “Is this a bot?”)
- I claim that you are a bot. (often shortened to “This is a bot.”)
- I accuse you of being a bot l. (often shortened to “Are you a bot?”)
The part where I’m interpreting to include accusations of bottery and slop is “and the like. It”; the first clause, ‘the like’ refers to the generic category of accusations against posted comments, which historically were the listed examples, but is also defined to include others not listed, such as today’s popular accusations of bot or AI; the second clause, ‘It’, refers to all insinuations-class content. Without the list of examples, this reads:
’Please don’t post insinuations. It degrades discussion
Yep, this is true. Accusations, Insinuations, Claims, of bot or AI or astroturf; they all wreck discussions and I end up having to email the mods to deal with them. A lot of people use the rhetorical device of Discredit The Opposition by invoking this sort of thing, and while that’s less prevalent in ‘reads like AI’ insinuations, they still degrade the site.
With AI-assisted writing is a violation of site guidelines, and even before it was, posting of AI-assisted writing was a clear ‘abuse’ of the community’s expectations of unassisted-human discussions. Aside from expectations, I can also classically understand in Internet history that ‘violating the guidelines’ is the phrase formerly known as ‘abuse of service’, by which I interpret the above reference to abuse to refer to breaking the guideline about posting accusations.
The guidelines are not a legal contract as program code, and perhaps this one is clunky enough that it needs to be reworded slightly; thus my intent, once the flames die down here, to let the mods know about the confusion. As I’m not a mod, this is my interpretation alone; you might have to email the mods and ask them to reply here if you want a formal statement on the matter, given how many comments this thread got in a couple hours.
ps. On ’and is usually mistaken’: I’m not a mod, so I can’t judge how often accusations of AI/bot are mistaken, but I’m also an old human who learned em-dashes in composition class, so I tend to view the modern pitchfork mobs out to get anyone who can compose English as being less accurate in their judgments than they believe they are.
Unless you're arguing that the rule violations are something the author intends to be part of the meaning of what one wrote?
That's fair.
>Unless you're arguing that the rule violations are something the author intends to be part of the meaning of what one wrote?
I think what I wanted to get at is more like this:
1. I think that they may be part of the meaning
2. I think that people would be primed to accept changes even if they change the meaning
3. I suspected that it would always correct something and wouldn't just say LGTM even if the input was fine
To check, and at the risk of this being hypocritical, I asked for a grammar correction on part of your post that I thought had no mistakes, and both in context and isolation, it corrected "spat out" to "produced." Now, this isn't a huge deal, but it is a loss of the connotation of "spat out," which is the phrasing you chose.
I think grammatical errors are low-cost, and changes in meaning and intent are high-cost, so with 2. above, running it through an LLM risks more loss than it gains.
(On that tangential note, though, I do appreciate that Kagi Translate provides multiple translations and attempts to explain their differences in connotation such that I can pick whichever one most closely matches my intent; if other LLM-assisted writing tools did that then that'd render a lot of this problem moot.)
In all seriousness, if you use some tool to make sure you're using the right "there", noone will mind. Just don't generate another boring predictable comment and everything will be ok
And no, I don't have to reply to a post, but when I think it's a bad policy, should I just accept it without discussion? And who determines the "experts/insiders" and which voices should be allowed?
As Isaac Asimov pointed out[0]:
“Anti-intellectualism has been a constant thread winding its way through our political and cultural life, nurtured by the false notion that democracy means that 'my ignorance is just as good as your knowledge.'”
This thread runs through many cultures and isn't just a problem on the Internet, although the Internet certainly has accelerated/worsened the problem. And it has created a distrust of experts which (as has been obvious for a long time) has made us, as a whole, dumber and less informed.
I recommend The Death of Expertise[1] by Tom Nichols for a sane and reasonable treatment of this issue. If books aren't your thing, Nichols did a book talk[2] which lays out the main points he makes in the book. During that talk, he also gives the best definition of disinformation I've heard yet.
[0] https://www.goodreads.com/quotes/84250-anti-intellectualism-...
[1] https://en.wikipedia.org/wiki/The_Death_of_Expertise
[2] https://www.c-span.org/program/book-tv/the-death-of-expertis...
If someone posts a link on a a new laptop, who should respond? I am not an expert on the current laptop market, but I have options about it. Maybe my English is not the best so I run through an AI to clean it up of ambiguities or wrong wording. Maybe I say “I like to take my laptop from behind” when I meant “I lift my laptop from the back”. An AI could point out this type of error.