@Stormblessed Regular Expressions can be written to not match if there is specific text. This is normally done with negative lookarounds (i.e. negative lookbehinds and negative lookaheads ). You would need to identify exactly which regex is matching and then work on adjusting it.
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, pattern-matching product name in body, pattern-matching product name in title, potentially bad keyword in body (394): Velofel Male Enhancement Reviews? by velofeldiet on superuser.com
I suppose there are many posts where academia.edu is used legitimately (if that's the correct word to use here): you can try networkwide search or some specific site such as Academia.SE.
Does adding it to blacklist mean that every post with this domain will be reported?
@MartinSleziak we'll certainly need to keep our eyes open for FPs for this one; I'm not totally comfortable but with the evidence we have now, it seems viable
@tripleee That pattern looks like it's already caught by Potentially bad keyword in body and Potentially bad keyword in answer; append -force if you really want to do that.
@tripleee @double-beep I just read the transcript. academia\.edu was not watchlisted, as far as I saw in a brief check. Thus, we have no real information as to the number of FP it will produce as a blacklist. Getting that information is why we should be watchlisting first, whenever reasonable. A search for it on MS indicates of the 13 hits 7 are TP, 5 are FP, and 2 are NAA. That doesn't doesn't meet the blacklist criteria and doesn't come close to the target TP rate we have for the blacklist.
In addition, there are 1,393 hits on SE, which is way too many for a blacklist. It's even enough such that we should be seriously considering if it's appropriate to even have on the watchlist, but it definitely shouldn't be on the blacklist, IMO.
[ SmokeDetector | MS ] Bad ip for hostname in body, bad keyword in body, bad keyword in title, blacklisted website in body, body starts with title and ends in url, +4 more (790): male enhancement supplement by BritinyScott on askubuntu.com
@double-beep That pattern looks like it's already caught by Bad keyword in answer and Bad keyword in body; append -force if you really want to do that.
[ SmokeDetector | MS ] Url in title, bad keyword in body, bad keyword in title, blacklisted website in body, blacklisted website in title, +4 more (688): welnesscare.com/control-x-keto/ by yubngr on puzzling.SE
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, blacklisted website in body, body starts with title and ends in url, link at end of body, +2 more (588): DXN Code Strike by JulieSala on askubuntu.com
@WaiHaLee That pattern looks like it's already caught by Potentially bad keyword in body and Potentially bad keyword in answer; append -force if you really want to do that.
@tripleee I suspect that one is that there is a null domain linked. That will likely take a database edit, or editing the code to prevent the error. Fixing the code is something I can do.
@Makyen That pattern looks like it's already caught by Pattern-matching website in body and Pattern-matching website in answer; append -force if you really want to do that.
[ SmokeDetector | MS ] Offensive body detected, potentially bad keyword in body, potentially bad keyword in title, toxic body detected (106): Why does Ubuntu suck ass? by Elwyn on askubuntu.com
@Makyen That pattern looks like it's already caught by Potentially bad keyword in body, Potentially bad keyword in answer, Pattern-matching website in answer, and Pattern-matching website in body; append -force if you really want to do that.
@Makyen That pattern looks like it's already caught by Potentially bad keyword in body and Potentially bad keyword in answer; append -force if you really want to do that.
[ SmokeDetector | MS ] Blacklisted website in body, pattern-matching website in body, potentially bad asn for hostname in body, potentially bad ip for hostname in body, potentially bad keyword in body, +2 more (270): 7z Password Recovery tool by izabela anna on security.SE
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, bad keyword in username, pattern-matching product name in body, potentially bad keyword in body, +2 more (387): Ultra Fast Keto Boost by Ultra Fast Keto Boost on askubuntu.com
@SmokeDetector not quite sure on this one, there appears to be another spam post including that domain, but this one is a bit different, so there isn't exactly enough evidence to judge between NAA/TP
@angussidney I didn't mean that we should remove the phrase from being watched; it shouldn't be in very many valid Unix/Linux posts, for example. I'm just not sure if Smokey can do per-site keywords.
@JeffSchaller in other words, we can, but that involves removing it from the list which is applied to all sites, and introducing a more detailed rule which can be targeted more specifically
There are some cases where the adjustments aren't worth the added complexity, but given that the poker.SE site has a dedicated 'online' tag with quite a few questions, I thought it was worth adding. In short, if you can write a Python function which takes the standard inputs (post body, username, rep, title, question, etc etc) and spits out a True/False value and reason, then we can add it as a custom spam check
