@forest 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 word(s) if you really want to add the pattern you provided.
@cocomac The regex contains an unescaped ".", which should be "\." in most cases. Append -force to the command word(s) if you really want to add the pattern you provided.
!!/report stackoverflow.com/questions/73424257/… "Possible spam seed, not sure. I have to go so I can't keep an eye on the post, but this will mean they get blacklisted so it will show up if they post spam as an answer. That said, it could be a legit (albeit, off-topic) request, so feel free to unblacklist them if they're fine"
[ SmokeDetector | MS ] Bad ip for hostname in body, bad ns for domain in body, blacklisted website in body, blacklisted user (364): What is selenium? by ganesh reddy on superuser.com (@Ollie)
@JeffSchaller That pattern looks like it's already caught by Potentially bad keyword in answer and Potentially bad keyword in body Append -force to the command word(s) if you really want to add the pattern you provided.
[ SmokeDetector | MS ] Bad ns for domain in body, blacklisted website in body, potentially bad ip for hostname in body, potentially bad keyword in body, potentially problematic ns configuration in body (197): How to prepare for MPPSC Exam? by SHARMA ACADEMY on superuser.com (@Ollie)
[ SmokeDetector | MS ] Link at beginning of body, pattern-matching website in body, potentially bad asn for hostname in body, potentially bad ns for domain in body, potentially bad keyword in body (138): Writing sociological papers by Ronald Tolkien on graphicdesign.SE
@ThomasWard Yeah, I'm not sure how that happened. Rather than attempt to figure out how that happened, I'd be more tempted to pull out all of SD adding MS comments for chat messages which aren't direct replies.
@Makyen tbh I think that should be done to begin with. That's the way it should have been, IMO
i went and did some cleanup on that MS post to remove the messages, and it took ditgging around all the channels to find the discussion that led to the posts.
I know it's probably NOT what we would intend, but we need to stop the random unrelated irrelevant posts esp. if it comes from a random unrelated channel
@ThomasWard Yeah, I'm really not sure why that's in there. I suspect that, at the time, there were a variety of conversations which weren't direct replies and appeared relevant. At this point, people are fairly used to leaving comments through direct replies. IIRC, I wasn't all that thrilled with it picking up "close" chat messages which aren't direct replies when the code was added.
We also need to have proper attribution of the comments in order to comply with CC BY-SA. There are some which end up on MS without any indication of the author. That could be fairly reasonably solved by including at least the username of the author and a link back to the chat message. That would at least be a significant step in the right direction.
@cigien The regex contains an unescaped ".", which should be "\." in most cases. Append -force to the command word(s) if you really want to add the pattern you provided.
@SmokeDetector While this might be a spam seed, it might alternately be a real off-topic question. The user's account on SO has been around > 8 years and does have other (deleted) valid contributions over that time.
The quota_remaining property was not in the API response. Error: no method found with this name at 18:19:58 UTC. Backing off on requests for the next 12 seconds. Previous URL: https://api.stackexchange.com/2.2/questions
