Don't report posts from Answer Bot

[Andrew5057]

Is your feature request related to a problem? Please describe.

Currently, SmokeDetector reports posts from Answer Bot if they trip a watchlist or other spam check. That's not optimal; we already know that answers from Answer Bot aren't spam, so we should probably just ignore them.

Describe the solution you'd like

Answer Bot accounts seem to be guaranteed to have an ID of -2, so adding a check for that somewhere is probably the easiest way to go about this. I'm not particularly familiar with the codebase, but maybe at the top of FindSpam.test_post?

Describe alternatives you've considered

• We definitely shouldn't whitelist based on the username.
• The user-whitelist doesn't help; Answer Bot is cross-site, and the posts themselves are tripping Smokey's spam checks (not the username).

[makyen]

I am resistant to doing this, because the premise upon which it rests is false. We do not "know that answers from Answer Bot aren't spam". We believe that SE doesn't intend them as spam, but there's nothing that actually prevents those answers from, effectively, being spam. An LLM could produce anything. There's nothing that restricts the answer from, effectively, promoting something inappropriately.

[CoconutMacaroon]

@makyen If we're not going to exclude them from SmokeDetector scanning, consensus should be established on whether or not these posts are tp (for not meeting the referencing requirements) or fp as it's SE-approved. A metasmoke search for posts with a username matching ^Answer Bot$ indicates a lack of consensus (disclaimer: I am responsible for some, but not all, of those TPs).

After re-reading the Feedback Guidance page, I think it should be considered tp for failing to meet the referencing requirements (I don't consider the profile sufficient disclosure). It does have an AI badges, but it still isn't in a blockquote. That said, I wouldn't be opposed to changing policy to state that Answer Bot's posts should be considered FP if they're only genAI and not spam, with rationale that it's SE-approved.