[ SmokeDetector | MS ] Bad keyword in body, link at end of body, pattern-matching website in body, potentially bad keyword in body, potentially bad keyword in title, +1 more: Tryvix Cream In Spain by tryvix on askubuntu.com
As per the FAQ, we know that there are two small differences between spam flags and R/A flags.
If a deleted post has at least 1 valid spam flag, it can be used as review audits. The same doesn't apply to R/A flags.
If a question has a second answer deleted with at least 1 valid spam flag, it's ...
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 ] Bad keyword in body, bad keyword in title, blacklisted website in body, link at end of body, pattern-matching website in body, +1 more: CBD Pure Hemp Oil offer by dgewzqtyr on drupal.SE
[ SmokeDetector | MS ] Bad keyword in title, blacklisted website in body, link at end of body, pattern-matching website in body, title starts and ends with a forward slash: /nouveau-beauty-cream/ by GailWren on drupal.SE
My problem with that question, @iBug, is that it makes it seem like charcoal just decided to only use spam flags, while there has actually been quite a bit of discussion about whether or not it's okay. The question doesn't mention any thought that went into the decision.
@HyperNeutrino I use FIRE, but the mouse/desk here are crappy. Mouse keeps going all over the place. Gotta love it when a customer provides a good working environment.
I find the blur helpful for when a dialog shows up because it helps me focus on the dialog but I find it doubly unhelpful when the blur doesn't go away afterwards :P (not a problem for opening spam reports, only for token request which is a one-time thing so I'm ok with it)
Unless the cache caches all known MS posts, according to the error it tries to do Rails.cache.fetch('last-posts', expires_in: 30.seconds) do, what could be good if we want to see the error quickly before other things fail
@ArtOfCode Yep. tp- is expected to not flag. I'm still kicking around how the UI will look in order for it to be clear to the user exactly what their action will cause the script/system to do. Obviously, people will have had to go through the SE OAuth2 process in order to do the other types of flags, but that's already available in FIRE.