[ SmokeDetector | MS ] Offensive title detected, potentially bad keyword in body, potentially bad keyword in title, toxic body detected (114): Susan Collins Is An Asshole by Stink on politics.SE
@Spevacus Yeah. SQL has no concept of timezones and the spam DB has (UTC) timestamps in the period between 2am and 3am that doesn't exist in my local time.
(for daylight saving time shifts)
simple one-line config fix of course but it took a while to figure it out. Now I'm off my work computer (windows) trying to replicate it on my mac.
@NobodyNada Just wait until they try my new esoteric programming language in which all the keywords are profanity and every program is required to start with keto keto keto keto keto keto.
@SmokeDetector The question explicitly asks for free alternatives. This answer provides links to four alternatives, only one of which is free. The free one which it does include is already mentioned/linked in two other answers from up to 7 years ago.
Speaking of which, there's another one in there that's a watched domain, and the only other tp is this one: metasmoke.erwaysoftware.com/post/62357 which looks more like an NAA without additional context, especially given this user's habit of posting NAAs: metasmoke.erwaysoftware.com/post/62358 (which is also marked TP for unclear reasons).
The user has been deleted, which suggests that there may in fact be missing context, but I'm not sure what it is.
@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 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 ] Url in title, blacklisted website in body, potentially bad ip for hostname in body, potentially bad ns for domain in body, potentially bad keyword in body (197): jabazaar.com/ by Jabazaar on workplace.SE
@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.
[ SmokeDetector | MS ] Blacklisted website in body, potentially bad ip for hostname in body, potentially bad ns for domain in body, potentially bad keyword in body, blacklisted user (173): Look at your total portfolio by nobile on bitcoin.SE
@Mast While I generally agree, I can't actually seem to reproduce those fps, either via the link in the MS GitHub comment or via entering the search query myself
Anyway, based on MS, there is 0 justification for this watch.
With a potential to do more harm than good.
And I've warned for this in 4897 ("Just because the code is malicious, doesn't mean it's spam or a troll. Insufficient justification.") and 4891 ("Way too many FP. Current score in MS is 1 true positive, 25 false positives, and 2 NAAs. And who knows how many false hits in already existing, uncaught legitimate questions.") without response.
[ SmokeDetector | MS ] Url in title, bad ip for hostname in body, bad ip for hostname in title, bad keyword in body, bad keyword in title, +6 more (887): slimfitpills.com/ciagenix/ by nahmneih on graphicdesign.SE
@VictorVosMottor given the feedback on your previous similar watches, please refrain from pursuing this further, or follow up on those PRs and work with us to clarify what you are hoping to accomplish
[ SmokeDetector | MS ] Few unique characters in body, no whitespace in body, no whitespace in title, potentially bad keyword in body, repeating characters in body, +1 more (396): aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa ✏️ by Yevon Ting on stackoverflow.com
