@RocketNikita cigien is correct; this group is "focused on detecting and eliminating spam and rude/abusive posts", and so while some of the automatically-reported posts here end up being NAA (seen as false positives by this project), NAA's are not something this group is looking for.
[ SmokeDetector | MS ] Bad ip for hostname in body, bad ns for domain in body, bad keyword in body, bad keyword in link text in body, blacklisted website in body, +1 more (458): corrupted circuitPython files? by Rahul1995seven on askubuntu.com
!!/reject 7826 "while the post might have been spam (I cannot see it), there is at least one other Oleg.S user, making for immediate FP; a 'watch' would be much more appropriate, particularly if the user repeats spammy behavior"
@user16217248 Please be quite hesitant to watch, and particularly blacklist, usernames which might be someone's real name. While that can be done when the volume is high or the name is quite unique, particular care should be used to avoid targeting potentially innocent users (i.e. ones with a similar name that aren't the person you're wanting to catch), just because of their name.
@user16217248 right; the most appropriate feedback (when MS is up) would be a "tpu" on that report, to add a watch the user. To blacklist a username, I think it's usually done with case sensitivity and anchoring -- but I still wouldn't recommend blacklisting a username based on one report.
Please star this message if you support Charcoal participating in the network-wide strike, which would mean shutting down SmokeDetector (but leaving MS up) Monday (2023-06-05), until this AI policy is dropped.
I don't know anything about "Magento" but I joined the community because it seems to be a common target of spam and troll posts and my flags will help get them deleted faster
@user16217248 NAQ would be "Needs details or clarity" (as to what the question is)
There is a VLQ flag for questions but mods hate it
If they're horribly off-topic, use the community-specific close reasons to flag as off-topic
The reason mods hate the VLQ flag for questions is that it's basically "I think this question should be closed or edited but I'm not going to tell you why it should be closed or make the edit myself"
so we have a stricter interpretation on SO, but the system still marks them helpful if someone edits the question or it gets closed
I guess that makes sense, after all, it's the question VLQ flags that get so many people confused, whereas the answer VLQ/NAA flags are more straightforward for both flaggers and flag reviewers. The same would apply to feedbackers on smoke detector.
@user16217248 From MS' point of view, which is primarily about autoflagging, NAA == FP. The NAA feedback exists because we pesky humans like to make that differentiation and people feel better giving NAA feedback, rather than FP.
We could implement something similar for questions, but it would really be to make the humans feel better, as it's not information we're using to determine if to autoflag or not. Implementing it would be considerable work. So far, nobody's been motivated enough to do it. There are always plenty of other things to do, most of which would be considered a higher priority.
