The Stack Exchange API has a couple of calls that return a list of flag_option objects.
These objects contain a couple of properties that can be used to identify the flag you need.
For example, when I want to cast a spam flag from an app, I used to look for a flag option with an title equal to "...
It's... hard... to argue in favor of writing an algorithm and making a bot spend time calculating which of the two flag types to use when they are, in actuality, the exact same flag. It's not even Coke vs. Pepsi, it's Pepsi vs. a second bottle of Pepsi that's using a different but still valid Pepsi logo.
[ SmokeDetector | MS ] URL-only title, bad NS for domain in body, bad NS for domain in title, bad keyword in body, bad keyword in title, +5 more: getsupplementhelp.com/tryvexan/ by amuu on askubuntu.com
[ SmokeDetector | MS ] Bad NS for domain in body, bad keyword in body, blacklisted website in body, link at end of body, pattern-matching website in body, +1 more: The service to notice transcenf by Kno th on drupal.SE
I vote the following:
Red flags on gibberish are okay (handle as Helpful). Do we really want "sdfiushrf;usrgbsrilbslfibsl.eifub!" sticking around the site for longer than necessary? Red flags put the ability to remove these posts in the hands of a much wider scope of the community than communit...
[ SmokeDetector | MS ] Bad keyword in link text in body, bad keyword in title, pattern-matching website in body: Writing Service by igordavidson94 on stackoverflow.com (@iBug @TetsuyaYamamoto)
I recently came across a question that was deleted for rude/abuse. I was the last person to flag it before it was deleted, so I think smokey didn't read the question because it was deleted at the time my userscript reported the post. Should I manually report the (now deleted) post, so that smokey can keep track of it?
Unfortunately, that doesn't work - Smokey can only read not-deleted posts.
And in general, while catching rude/abusive posts is nice and I have no problem !!/report-ing them, automated detection of them and keeping records is less of a priority than it is for straight spam.
Glorfindel: I posted a question to meta.se about the deleted:1 tag. One of the things I mentioned was our conversation and a bit about the deleted post issue (As I think they're somewhat related).
We've done it ladies and gentlemen (and flowers of course). We've eliminated all the spam from the Stack Exchange network. It's taken a long time, but I think they've realized it's futile to try to surpass the advanced detection abilities of our SmokeDetector.
@Catija looks suspiciously like it... can't verify for certain cuz I don't have porkchat, but it's calling something called replace_emoji - which sounds like it would mess with the FIRE emoji