@Ollie That pattern looks like it's already caught by Bad keyword in body and Bad keyword in answer Append -force to the command word(s) if you really want to add the pattern you provided.
@SmokeDetector tpu- User is affiliated (see profile with alitech.io and linked domain hostingbyalitech.com. Also, linked article was written a week ago, and domain has been spammed before metasmoke.erwaysoftware.com/domains/78484. Custom flagged.
> Url in title, potentially bad keyword in body, potentially bad keyword in title, potentially bad keyword in username ---------- Potentially bad keyword in body - Position 8-34: newjerseyloteryresults.com Potentially bad keyword in title - Position 8-34: newjerseyloteryresults.com Potentially bad keyword in username - Position 8-34: newjerseyloteryresults.com Url in title - Position 0-34: https://newjerseyloteryresults.com
@RobertColumbia "By the way, I know this sounds a lot like money laundering or something like that, but it’s not :)" We don't make a habit of saying we have nothing to hide unless we've something to hide.
@Ollie It definitely shouldn't automatically remove the subdomain for all domains. While there are a good number which are more appropriately watched without the lowest level subdomain, there are others where that's not appropriate and the full subdomain should be watched.
@JeffSchaller That pattern looks like it's already caught by Blacklisted website in body and Blacklisted website in answer Append -force to the command word(s) if you really want to add the pattern you provided.
@JeffSchaller There's a low probability that no WebSocket notification is made to SD regarding a question being "active". We're heading in the direction of making that less likely, but there are some gating items/issues which need to happen first/be resolved first. There are some other rare edge cases which also could cause a post to be missed. At least the ones we know about should be resolved by similar changes, or at least greatly reduced.
@JeffSchaller Thanks. I appreciate that. Unfortunately, investigating what, exactly, happened to cause a post to be missed is difficult and unlikely to provide resolution. To a large extent, we'd want the console logs from the SD instance, but those are not easily available. Overall, it's quite likely to be one of the things we already know about and/or resolved by planned changes (which will tend to patch over various other possible issues).
@SmokeDetector fp TIL if there are multiple potentially bad keywords, they don't add up to increase the reporting score - the reason is only counted once
@Makyen I've got that in mind - e.g., the wixsite watches - so I'm not sure how that would be implemented. Might be better to just do it manually for now.
