In a support discussion titled ‘Show reason for approval being triggered on approval queue,’ merefield asks why approval queue entries don’t display the reason for triggering, noting in logs that a user was silenced for ‘typing too fast.’ cpradio initially states this is the only reason posts appear in the approval queue, but nawthor clarifies that site settings like ‘approve unless trust level’ can also route posts to the queue based on user trust level or post count. cpradio concedes this point, noting such settings would make the reason obvious to moderators. Mittineague adds that currently, screened URLs don’t route to the approval queue — they default to ‘do nothing’ — and expresses hope for future functionality to change this. The discussion highlights a gap in transparency for moderators reviewing approval queues and explores configuration options that influence queue behavior.
Not entirely true. It’s possible to make it so that every post or topic by users below a certain trust level goes through the approval queue with the site settings “approve unless trust level” and “approve new topics unless trust level”. (Maybe also “approve post count”, but I don’t have experience with that one).
Okay, that’s fair, but if you enabled that, the new assumption is you know why the post is there. As that would become the ONLY reason for it to be there. As the “Fast Typing” rule, IIRC, only applies to TL0 users (maybe TL1?)
Yes, I’ve been hoping that eventually the Screened URLs list would send posts into the approval queue instead of “do nothing” but it hasn’t happened yet. eg.
SELECT COUNT(*)
FROM `screened-url-180328`
WHERE `action` NOT LIKE 'do nothing';
.....
[COUNT(*)] => 0