@Ethan If you mean just the morse code for the one word and not the whole thing, then yes, I don't think that would be unreasonable, although consider adding a regex comment to the end, something like (?#F-word in morse code). Also remember to escape the period character if you do
I don't see any other hits except that one just now, but I think it would be fine
@Ethan That pattern looks like it's already caught by Mostly punctuation marks in answer and Mostly punctuation marks in body Append -force to the command word(s) if you really want to add the pattern you provided.
@SmokeDetector I mean...that last paragraph is...pretty promotional? But it's an answer to the question, not just like, straight-up spam. At most, the promotional bits should be removed.
@Ethan This won't match as a watch, due to the bookending which watching uses. There really isn't a good way to watch that without using a separate Rule in findspam.py. cc @cocomac
Yes, there are definitely some ways to do it, but doing so as a watch with bookending has substantial performance issues, although those could be limited.
@Ethan There's a paragraph on it in Non -number blacklists and watchlist. It's, mostly, that the entries for the watchlist and keyword-blacklist have \b added to the start and end. It's actually a bit more complex than that, but that's close.
@cigien 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.
> Url in title, bad ns for domain in body, bad ns for domain in title, blacklisted website in body, blacklisted website in title ---------- Bad ns for domain in body - pg-slot.game NS suspicious daphne.ns.cloudflare.com.,garret.ns.cloudflare.com. Bad ns for domain in title - pg-slot.game NS suspicious daphne.ns.cloudflare.com.,garret.ns.cloudflare.com. Blacklisted website in body - Position 8-20: pg-slot.game Blacklisted website in title - Position 8-20: pg-slot.game Url in title - Position 0-20: https://pg-slot.game
[ SmokeDetector | MS ] Bad ns for domain in body, link at beginning of body, mostly non-latin body, potentially bad keyword in body, blacklisted user (288): NUMBER 1 Lucky Fan by Nongnong Kraf on drupal.SE
[ SmokeDetector | MS ] Bad ns for domain in answer, bad keyword in answer, bad keyword in link text in answer, blacklisted website in answer, potentially bad keyword in answer (344): Titlepage dissertation help by Taylor Wrixon on tex.SE
@SmokeDetector They made one borderline spam post on that site, and have positive contributions on other sites (2.2k rep on SO), so I don't think that's spam.
@Mast "Linked punctuation in body" actually only has 77/328 tp/fp, so that seems reasonable (though it certainly is good at catching spam that wouldn't be caught otherwise. "Linked punctuation in answer" has a much higher success rate actually, at 393/126 tp/fp.
sdc report stackoverflow.com/a/74665744/4657412 "App reports 5 downloads, which suggests that the poster is probably the author. Not really convinced it answers the question anyway"
@DavidW 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.
The quota_remaining property was not in the API response. Error: Violation of backoff parameter at 13:49:13 UTC. Backing off on requests for the next 12 seconds. Previous URL: https://api.stackexchange.com/2.2/questions?site=stackoverflow.com
The quota_remaining property was not in the API response. Error: Violation of backoff parameter at 13:49:27 UTC. Backing off on requests for the next 12 seconds. Previous URL: https://api.stackexchange.com/2.2/questions?site=stackoverflow.com
The quota_remaining property was not in the API response. Error: Violation of backoff parameter at 13:49:42 UTC. Backing off on requests for the next 12 seconds. Previous URL: https://api.stackexchange.com/2.2/questions?site=stackoverflow.com
The quota_remaining property was not in the API response. Error: Violation of backoff parameter at 13:49:57 UTC. Backing off on requests for the next 12 seconds. Previous URL: https://api.stackexchange.com/2.2/questions?site=stackoverflow.com
The quota_remaining property was not in the API response. Error: Violation of backoff parameter at 13:50:11 UTC. Backing off on requests for the next 12 seconds. Previous URL: https://api.stackexchange.com/2.2/questions?site=stackoverflow.com
The quota_remaining property was not in the API response. Error: Violation of backoff parameter at 13:50:25 UTC. Backing off on requests for the next 12 seconds. Previous URL: https://api.stackexchange.com/2.2/questions?site=stackoverflow.com
The quota_remaining property was not in the API response. Error: Violation of backoff parameter at 14:54:07 UTC. Backing off on requests for the next 12 seconds. Previous URL: https://api.stackexchange.com/2.2/questions?site=stackoverflow.com
The quota_remaining property was not in the API response. Error: Violation of backoff parameter at 14:54:26 UTC. Backing off on requests for the next 12 seconds. Previous URL: https://api.stackexchange.com/2.2/questions?site=stackoverflow.com
The quota_remaining property was not in the API response. Error: Violation of backoff parameter at 14:54:41 UTC. Backing off on requests for the next 12 seconds. Previous URL: https://api.stackexchange.com/2.2/questions?site=stackoverflow.com
The quota_remaining property was not in the API response. Error: Violation of backoff parameter at 14:54:55 UTC. Backing off on requests for the next 12 seconds. Previous URL: https://api.stackexchange.com/2.2/questions?site=stackoverflow.com
The quota_remaining property was not in the API response. Error: Violation of backoff parameter at 14:55:09 UTC. Backing off on requests for the next 12 seconds. Previous URL: https://api.stackexchange.com/2.2/questions?site=stackoverflow.com
@Makyen ^ Checks have been failing for a couple of hours. This passed, this did not.
[11:14:12.516] Entry which failed to validate twice:
askbeen.com. in watched_nses.yml for dns.resolver.NXDOMAIN
=========================== short test summary info ============================
FAILED test/test_blacklists.py::test_yaml_nses@long_runner_1 - Exception: 1 entry failed to validate in watched_nses.yml
askbeen.com. in watched_nses.yml for dns.resolver.NXDOMAIN
================== 1 failed, 355 passed in 120.95s (0:02:00) ===================
@Ollie Regarding your comment: Only users with the Reviewer role on MS can use regex searches, so it's not very effective to link to such. If you are going to link to MS, it's usually much more effective to link to something else. Non-regex searches can be done without an account. For a domain, it's probably better to just link to the domain's page.
However, in general, we usually don't link to MS in comments under spam or trolling, because it points the spammer/troll to MS. While that usually doesn't really matter, there have been some times when that's lead the spammer or troll to actively take SD/MS into account in their activities, which can make our task a bit harder.
@Makyen I did think (albeit briefly) about not linking to MS; I know certain people use(d) their awareness of Charcoal and MS to their advantage, but this one appears to be new. I didn't know about the Reviewer role requirement; I'll remember that
np. Thanks. Yeah, the Reviewer role requirement is because regex searches can be quite computationally expensive, depending on the regex, so could be used as a vector for a DOS attack on MS.
