I gave this reportfpu, but this report was still made by SD, where the only caught content is the potentially bad keyword in username. I'm not sure what I did wrong, or what I'm misunderstanding.
The feedback was given via FIRE. All I've done is add .append(createFeedbackButton(d, ['7', 'f', numpad('7')], 'fpu-', 'fpu-', '', 'False Positive. Whitelist username')) to ButtonContainer on line 1159, and that appears to work (i.e. MS records the feedback as fpu), but I don't really know what I'm doing, so that may be what's wrong.
@metasmoke @cigien I'm not sure removing the contact information from NAAs like this is productive: it doesn't address the problem with the post in any way, and it would dismiss any VLQ flags that might have been raised.
@SmokeDetector I have questions about the usefulness of autoflagging a nearly eight-year-old post. It does appear likely to be undisclosed self-promotion, but it seemingly answers the question. The autoflags were based solely on three experimental reasons relating to DNS and the link at end.
Which, I suppose, is fine if you've also flagged NAA, because that won't be dismissed...but might confuse someone seeing the flag marked helpful but the post left up.
@RyanM Hmm, I see what you mean. I would have liked to just delete it, but since I can't I wanted at least the contact info gone asap. Maybe a half solution isn't a good idea here.
[ SmokeDetector | MS ] Bad ip for hostname in body, blacklisted website in body, potentially bad ns for domain in body, potentially bad keyword in body, potentially bad keyword in title (202): Hire WordPress Developer by Ankit Verma on android.SE (@AndrewT.)
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in username, blacklisted website in body, potentially bad keyword in body, potentially bad keyword in title, +1 more (355): Where to buy cheap used 128gb iphone? by PAD Store on serverfault.com
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in link text in body, bad keyword in title, potentially bad keyword in body, potentially bad keyword in title (264): Web Design Company in Pune by jayshinde on stackoverflow.com
@SmokeDetector Spam/undisclosed affiliation: username is the same as the username in the GitHub URL, and this answer doesn't really address the question in any meaningful way.
@RyanM To avoid SmokeDetector reporting posts too slowly, you can report at most 5 posts at a time. This is to avoid SmokeDetector's chat messages getting rate-limited too much, which would slow down reports.
!!/scan stackoverflow.com/a/68816199 "Possible spam, low-quality answer: Given other spam posts for this domain and the fact that this answer is otherwise extremely vague without the link (making it very nearly link-only), it is probably better off gone. Custom-flagged for deletion."
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, potentially bad asn for hostname in body, potentially bad ns for domain in body, potentially bad keyword in body, +1 more (197): Digital marketing Services in Noida by Shrawan Singh on apple.SE
[ SmokeDetector | MS ] Blacklisted website in body, potentially bad ip for hostname in body, potentially bad keyword in body (101): Leolist Nanaimo by Twinkle Khatri on drupal.SE
[ SmokeDetector | MS ] Blacklisted website in answer, link at end of answer, potentially bad ip for hostname in answer, potentially bad keyword in answer (157): Leolist Nanaimo by rahul argalon on drupal.SE
@tripleee That pattern looks like it's already caught by Mostly non-latin body and Mostly non-latin answer Append -force to the command if you really want to add this pattern.
