News for hackers. Stuff that matters.
Re:X blames users for Grok-generated CSAM; no fixes announced by femiagbabiaka on Monday January 05, 2026 @03:12PM (#46504173)
I agree with that. But one, it is on the site, and two, how can the moderation team reasonably stop bad actors from downvoting it? They can (and probably do) unflag things that have merit or put it in the 2nd chance queue.
Re:X blames users for Grok-generated CSAM; no fixes announced by michaelt on Monday January 05, 2026 @04:18PM (#46505115)
> But one, it is on the site, and two, how can the moderation team reasonably stop bad actors from downvoting it?

In 2020, Dang said [1]

> Voting ring detection has been one of HN's priorities for over 12 years: [...]

> I've personally spent hundreds of hours working on this, as well as tracking down voting rings of every imaginable sort. I'd never claim that our software catches everything, but I can tell you that it catches so much that I often go through the lists to find examples of good projects that people were trying ineptly to promote, and invite them to do it again in a way that is more likely to gain community interest.

Of course this sort of thing is inherently heuristic; presumably bots throw up a smokescreen of benign activity, and sophisticated bots could present a very realistic, human-like smokescreen.

[1] https://news.ycombinator.com/item?id=22761897

Re:X blames users for Grok-generated CSAM; no fixes announced by slg on Monday January 05, 2026 @03:16PM (#46504254)
> how can the moderation team reasonably stop bad actors from downvoting it

There are all sorts of approaches that a moderation team could take if they actually believed this was a problem. For example, identify the users who regularly downvote/flag stories like this that end up being cleared by the moderation team for unflagging or the 2nd chance queue and devalue their downvotes/flags in the future.

Re:X blames users for Grok-generated CSAM; no fixes announced by ryandrake on Monday January 05, 2026 @03:51PM (#46504773)
Accounts are free to make, so bad actors will just create and "season/age" accounts until they have the ability to flag, then rinse and repeat.

I think the biggest thing HN could do to stop this problem is to not make flagging affect an article's ranking until after a human mod reviews the flags and determines them to be appropriate. Right now, all bad actors apparently have to do is be quick on the draw, and get their flagging ring in action ASAP. I'm sure any company's PR team (or motivated Elon worshiper) can buy "100 HN flags on an article" on the dark web right now if they wanted to.

Re:X blames users for Grok-generated CSAM; no fixes announced by dylan604 on Monday January 05, 2026 @04:42PM (#46505402)
Why would a company like any one of Musk's need to buy these flags? Why wouldn't they just push a button and have their own bots get to work? Plausible deniability?
Re:X blames users for Grok-generated CSAM; no fixes announced by ryandrake on Monday January 05, 2026 @05:38PM (#46506112)
Who knows whether or not both happen? Ultimately, only the HN admins, and they don't disclose data, so we can only speculate and look for publicly visible patterns.
Re:X blames users for Grok-generated CSAM; no fixes announced by wahnfrieden on Monday January 05, 2026 @05:45PM (#46506183)
You can judge their trustworthiness by evaluating their employer's president/CEO, who dictates behavioral requirements regardless of the personal character of each employee
Re:X blames users for Grok-generated CSAM; no fixes announced by philipkglass on Monday January 05, 2026 @03:35PM (#46504541)
That already happens. I got my flagging powers removed after over-using flag in the past. (I eventually wrote an email to the mods pledging to behave more judiciously and asked for the power back). As a user you won't see any change in the UI when this happens; the flags just stop having any effect on the back end.
Re:X blames users for Grok-generated CSAM; no fixes announced by immibis on Monday January 05, 2026 @05:15PM (#46505805)
There is one subtle clue. If your account has flagging enabled, then whenever you flag something there is a chance that your flag pushes it over the threshold to flagged state. If your account has flagging disabled, this never happens. This is what hinted me to ask dang if I'd been shadowbanned from flagging.
Re:X blames users for Grok-generated CSAM; no fixes announced by femiagbabiaka on Monday January 05, 2026 @03:24PM (#46504374)
I would be money that already happens, for flagging in particular, since it's right in the line of the moderation queue. For downvotes, it sounds like significant infra would be needed for a product that generates no revenue. Agree that I would like the problem to be solved as well however!
Re:X blames users for Grok-generated CSAM; no fixes announced by slg on Monday January 05, 2026 @03:31PM (#46504486)
>it sounds like significant infra would be needed for a product that generates no revenue

This just describes HN as a whole, so if this is the concern, might as well shut the site down.

Re:X blames users for Grok-generated CSAM; no fixes announced by immibis on Monday January 05, 2026 @05:14PM (#46505790)
My account is locked so that flags don't count - an email conversation with dang confirmed this. This was because I flagged too many comments that said things YCombinator needs to be true: that Elon Musk is good, Palestinians are terrorists, capitalism solved all problems, etc.