@Makyen That pattern looks like it's already caught by Potentially bad keyword in body and Potentially bad keyword in answer Append -force to the command if you really want to add this pattern.
@RyanM That pattern looks like it's already caught by Potentially bad keyword in body and Potentially bad keyword in answer Append -force to the command if you really want to add this pattern.
@tripleee I don't see anything obviously wrong with the site, so I don't see how those links could conceivably be adding anything to even a follow-up question. It sort of seems like a generic phrase intended to make it look like it might not be spam, followed by spam.
[ SmokeDetector | MS ] Link at end of answer, potentially bad ip for hostname in answer, potentially bad keyword in answer, blacklisted user (134): PHP 8 Comments bug by dlamini bekilila on stackoverflow.com
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, blacklisted website in body, link at beginning of body, potentially bad ip for hostname in body, +1 more (334): do yo want play the sattaking game? by lallu lal on android.SE (@AndrewT.)
@tripleee That pattern looks like it's already caught by Potentially bad keyword in body and Potentially bad keyword in answer Append -force to the command if you really want to add this pattern.
[ SmokeDetector | MS ] Blacklisted website in body, link at beginning of body, potentially bad ns for domain in body, potentially bad keyword in body, potentially bad keyword in title (142): iWRITE | Students Factory by ishant sharma on superuser.com
@tripleee That pattern looks like it's already caught by Bad keyword in body, Blacklisted website in body, Bad keyword in answer, and Blacklisted website in answer Append -force to the command if you really want to add this pattern.
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in link text in body, pattern-matching website in body, potentially bad ns for domain in body, potentially bad keyword in body (262): How to do good essay? by Edward C. Long on writing.SE
@tripleee That pattern looks like it's already caught by Potentially bad keyword in body and Potentially bad keyword in answer Append -force to the command if you really want to add this pattern.
[ SmokeDetector | MS ] Bad keyword in answer, pattern-matching website in answer, potentially problematic ns configuration in answer (165): Stuck in a toll booth by John Hoffer on gaming.SE
[ SmokeDetector | MS ] Bad ip for hostname in body, bad keyword in body, blacklisted website in body, body starts with title and ends in url, pattern-matching website in body (487): Eat Before You Go Out by Carlos Benz on stackoverflow.com
There's no question that spam should be flagged as spam. That's what the flag is for. But sometimes people also vote to close with various custom close reasons. Is there any harm in that provided they also flag as spam? (I don't see any point to the close vote, seems like a waste of time, but tha...