FIRE: When a post has autoflags, don't automatically submit a manual flag

[ferrybig]

See the following for context: https://chat.stackexchange.com/transcript/message/43236093#43236093

Quick summary:
"
At the moment, "FIRE makes it easy to forget how powerful a spam flag can be." (quoting Henders) This is a problem if we want to increase our autoflags to 5, because that would mean that any small mistake, or because you are a roboreviewer means that we have to reach out to a sites moderator, and explain our "voting ring" mistake, leading to reputation damage.
"

I'm suggesting that if FIRE detect that a post has autoflags, it shouldn't add its own spamflag, only MS feedback, and then give a notification that the user has to go to the post and manually flag the post.

I think this works great against the robo reviewers because most people aren't going to pay attention to the popup (as it normally also appears), as they expect it, while the people who carefully review the post are going to spam flag it (and eventually delete it).

[ArtOfCode-]

Addendum: I'm happy for FIRE to continue casting flags on 3-autoflagged posts, but on 5-autoflagged posts this would be good.

[SulphurDioxide]

To me, this sounds like a great solution. If you really wanted to go to the post and flag as spam you can, but most people probably won't do that.

[Cerbrus]

Users that aren't paying attention when using FIRE, shouldn't be using FIRE in the first place.

If this is a real issue, I'd rather see those users' FIRE MS keys revoked.

You're talking about robo reviewers as if the whole SmokeDetector / FIRE workflow is "yet another review queue". It's not. If there are indeed robo reviewers, these should be easy to identify with MetaSmoke's existing feedback / review system. I'd argue for a (close to) zero tolerance policy on such abuse of the provided tools.

I don't want to disrupt FIRE users because of a (theoretical) minority abusing all the tools provided to them.