And he’s an example of the same spammers getting caught here: https://meta.discourse.org/t/full-list-of-quickbooks-desktop-support-contact-numbers-a-complete-call-center-in-the-usa/380776 (it’s already hidden).
These guys are definitely working hard.
Great work on this feature. 
This is exactly how I like to see AI used.
Quick question: when a new TL0 user submits a reply or topic, is there a time delay while the content is scanned?
I see a short delay in the built-in tester (screenshot below), but when I post from a test account, there’s no similar pause. Is the live scan asynchronous after publishing, with the post hidden only if it trips a rule? (context: I’m using the OpenAI ChatGPT 5 API.)
For what it’s worth, AI > Spam & Stats increment as expected with the test account, so the post IS being scanned; it just isn’t introducing the same delay as the Test button does.
Thanks.
Ok so this works pretty well but what happens when it flags dozens of topics/users. I’m not seeing a way to bulk ban/delete these users/posts.
Thanks for the detailed thread. We have Discourse AI spam detection enabled on our instance, and one of the things that we’re seeing is the auto-silencing default when the first post made by an account is flagged.
I understand this is for silencing one-shot spammers; however, this is causing issues where approving/accepting a flag means that the user will remain silenced in cases where we want to approve the flag but not silence the user. It would be good to have:
This is a tricky one, we don’t want to paralyze people with choice here, but I totally get that at scale this can be a problem.
Let me check with the enterprise xp team maybe there is a small customization we can make for your forum.