Bulk-clean spam from the pending comment queue

CommentsIntermediate~10 min

Before you start

A connected site whose bound user holds the moderate-comments capability, with the pending-comments read and the moderate-comment write enabled.

There is a difference between a comment queue you want to read and one you just want gone. When a month of link spam has piled up behind a genuine trickle, reviewing each entry is not moderation, it is punishment. This is the decisive version: you set the rule, the agent clears the queue in bulk, and because it only marks or trashes, nothing it does is final.

The prompt
My pending comment queue is buried in spam and I want to clear it in bulk, not
review it one by one. Still, action nothing until I approve the rule.
First, read the pending queue and tell me what I'm dealing with: how many are
waiting, and a quick sample of the obvious junk so I can see the pattern, the
link-stuffed bodies and gibberish authors. Don't mark anything yet.
I'll give you a rule, something like "mark everything with three or more links
as spam and trash the rest of the junk." Apply it in batches, marking as spam
or sending to trash, and show me each batch as you go. Both spam and trash are
recoverable, so a wrong call is something I can pull back. When you're done,
tell me how many you marked as spam, how many you trashed, and what you left
in the queue for me.

Why this is safe to run

Reading the queue and moderating a comment are two separate abilities with two separate switches, so the opening read genuinely writes nothing: you see the size of the problem and a sample of the pattern before setting a rule. You approve the rule before a single comment is touched, and the agent works in batches you watch rather than clearing everything in one silent pass. Every action is a spam mark or a move to trash, both recoverable, so a rule that catches one good comment is a quick undo, not a loss. And comment reads never hand back an email address or an IP, so the sample stays privacy safe.

Already connected? Ask your agent for the “bulk-clean the comment queue” recipe, give it a rule, and it runs the same read-first sweep on your own backlog.

How it works

  1. Read the pending queue and report how many comments are waiting.
  2. Show you a sample of the obvious junk so you can see the pattern.
  3. Wait for you to give a rule for what counts as spam.
  4. Apply the rule in batches, marking as spam or sending to trash, showing each batch.
  5. Report how many were marked spam, how many trashed, and what was left.

Questions

How is this different from triaging the queue one by one?
Triage reviews each comment and asks you per item. This one is a decisive sweep: you hand over a rule like 'anything with three or more links is spam' and the agent applies it across the queue in batches. Use triage when the queue is small, this when it is buried.
Can it delete a comment for good?
No. This recipe only marks comments as spam or sends them to trash, both of which are recoverable. Permanently deleting a comment is a different ability entirely, and it is not part of this flow, so a wrong sweep is always something you can pull back.