Verwarrend verzoek voor review wachtrij

AI-generated summary

Théo_Zimmermann reported an issue in the review queue where a new user’s posts—actually private messages to @discobot—were flagged for review due to being typed too fast (copy-pasted from another source). These posts appeared nonsensical out of context but were legitimate. Théo suggests private messages, especially to @discobot, should not be auto-flagged or included in bulk user reviews unless flagged by the recipient. simon asked for the flagging reason, which Théo clarified was “typing too fast” [3], a known source of false positives. Simon acknowledged the scenario—likely occurring during the new user tutorial—and committed to investigating whether this behavior can be reproduced and improved [4]. The core concern is that legitimate automated interactions (like with @discobot) should not trigger unnecessary moderator review.

Hello,

Usually, I don’t have any problem with the review queue: it works very well to flag spam, and sometimes I need to approve manually a first poster, but this is fine.

However, today a user was flagged and the review queue asked me to review all of their posts. The first two posts were nonsensical to me: a link to a Wikipedia article and a picture of a unicorn. It was only after messaging the user that I finally realized that these nonsensical posts were private messages to @discobot, and were thus perfectly legitimate posts.

I think that private messages should never be automatically flagged and they should be shown to moderator only if they were flagged by the recipient. But at the very least, when Discourse decides that all posts by a user should be reviewed, it should not include private messages, especially those to @discobot!

Thanks!

Do you know what the reason for the posts being flagged was (off-topic, inappropriate, spam)?

Sorry, I missed that reply. The reason was that it was typed too fast (copy-paste announcement from another source). This is a relatively frequent source of flagging which generally gives false positives, but I haven’t disabled this check yet.

If I’m understanding this correctly, a user was flagged for typing too fast (copying and pasting into the composer) when going through the new user tutorial. I’m not sure what we expect to happen for that case, but I’ll have a look at it and see if I can reproduce the issue.