@Nick 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.
@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 word(s) if you really want to add the pattern you provided.
[ SmokeDetector | MS ] Bad pattern in url body, potentially bad asn for hostname in body, potentially bad ns for domain in body, potentially bad keyword in title (88): Aussie Play Casino Review by martin gary on meta.SE (@Ollie)
@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 word(s) if you really want to add the pattern you provided.
I'm not 100% sure this won't generate a lot of FPs, but I'm pretty sure it shouldn't, but I'm open to it being a bad idea. Unfortunately, SEDE timed out and SE doesn't support case-sensitive search, so checking for FPs on SE isn't trivial here. Regardless, by looking at the case insensitive search results, I'm guessing requiring it in all caps should work out fine
I suggest watching (?-i:HELPLINE) (i.e., "helpline" in all caps). I don't think this should have (any?) FPs, but I don't know of any way to do a case sensitive SE search so I could be wrong here. Thoughts on watching it?
Yeah, I agree with tripleee. A quick search on SE doesn't show any hits, and on MS it's 117/0 tp/fp which is quite good, even though a lot of the posts look like they'd be caught for other reasons.
[ SmokeDetector | MS ] Link at beginning of answer, potentially bad ip for hostname in answer, potentially bad ns for domain in answer (37): Work from home in hotel room by vik123 on superuser.com (@Ollie)
@tripleee 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 keyword with a link in answer, pattern-matching website in answer, potentially bad ns for domain in answer, username similar to website in answer (229): Generate a Tiefling's Traits by barbari-arya on codegolf.SE (@cairdcoinheringaahing @lyxal)
teward/Osiris: In getting MS post information, recovered from `requests.exceptions.ConnectionError: HTTPSConnectionPool(host='metasmoke.erwaysoftware.com', port=443): Max retries exceeded with url: /api/v2.0/posts/urls?key=[METASMOKE KEY REDACTED]&filter=GHOOIJGNLKHIIOIKGILKIJGHFMNKKGFJ&urls=%2F%2Fserverfault.com%2Fquestions%2F54547%2Fdo-routers-have-ip-addresses%2F747285%23747285 (Caused by NewConnectionError('<urllib3.connection.VerifiedHTTPSConnection object at 0x7f46a4effe20>: Fail ed to establish a new connection: [Errno -3] Temporary failure in name resolution'))`
[ SmokeDetector | MS ] Link at beginning of body, potentially bad ip for hostname in body, potentially bad ns for domain in body, potentially bad keyword in body, potentially bad keyword in username (44): What is a Monkey type? by Avajos on superuser.com (@Ollie)
@tripleee 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.
@tripleee I don't think "reviewdifference" was spam. The user just plagiarised content from there to make the content seem legitimate. The spam links about songs were added almost two months later.
Hmm, you're right. Although the link is dead. Seems like the spammer swapped to an alive link with the same content as their answer and then also decided to edit in the spam links. And re-post the same answer. Weird.
Oh, wait, the original site shows the article was written by somebody who shares one name with the user: archive link. There seems to be affiliation with that as well.
The edited article doesn't show the shared name but mostly shares the name with the author of the old article: Chukwuebuka Martins (original article) vs Martinez (new article).
Hmm, if anything, seems like the original domain nccmed.com was "abandoned". I can't find any useful content there. The new reviewdifference has very similar layout. And apparently re-hosts the same article as the original. Very likely the nccmed domain might be sufficiently blacklisted, hence the new domain.
@VLAZ Yes, it was indeed manually reported, though there was no reason provided so I guess it was reported because of the promotional nature. I would hard delete it, but there isn't enough evidence to spam flag it as far as I can see.
[ SmokeDetector | MS ] Link at end of answer, pattern-matching website in answer, potentially bad asn for hostname in answer, potentially bad ns for domain in answer, potentially bad keyword in answer, +1 more (213): Celerra: zoning done to data mover by jackkythermistgetr on serverfault.com
