@tripleee That pattern looks like it's already caught by Potentially bad keyword in answer and Potentially bad keyword in body; append -force if you really want to do that.
@VictorVosMottor An invalid pattern was provided, please check your command.
@VictorVosMottor That pattern looks like it's already caught by Potentially bad keyword in answer and Potentially bad keyword in body; append -force if you really want to do that.
@RobertColumbia That pattern looks like it's already caught by Potentially bad keyword in answer and Potentially bad keyword in body; append -force if you really want to do that.
@tripleee That pattern looks like it's already caught by Bad phone number in body and Bad phone number in answer; append -force if you really want to do that.
@VictorVosMottor That pattern looks like it's already caught by Potentially bad keyword in answer and Potentially bad keyword in body; append -force if you really want to do that.
@VictorVosMottor That pattern looks like it's already caught by Potentially bad keyword in answer and Potentially bad keyword in body; append -force if you really want to do that.
@VictorVosMottor 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.
@VictorVosMottor You don't have blacklist manager privileges, but I've created PR#5064 for you.
There are quite a few FP's with that. Plus, most keto spam is already caught by an unholy amount of regex watches/blacklists. I'm not sure we need another that isn't specifically targeted at keto spam that has low weight.
!!/reject 5064 "Most of the keto spam is already handled by an unholy number of regex watches and blacklists. New watches/blacklists for such content should be focused and hopefully FP-free."
Yeah you have to cut that part out of a full word to get close to something that could be potentially offensive.
I dunno. And, again, even if we grant that, it's still one singular instance of a user trolling, which we've humbly asked you not to report on a one-time offense basis.
I dunno. And, again, even if we grant that, it's still one singular instance of a user trolling, which we've humbly asked you not to report on a one-time offense basis.
> it's still one singular instance of a user trolling, which we've humbly asked you not to report on a one-time offense basis
I'm trying to tread carefully here because I don't understand Russian very well, but it doesn't look reportable. In the future, could you please attach a reason to why you !!/report a given post? You can do so like this: !!/report <link> "(Reason here)". The quotes are required for this command to work.
Well... technically that's something we tp, but that particular user is testing stuff in the Formatting Sandbox, which is totally fair game.
@Machavity For what it's worth, that user's interacting with a mod over there to play with automated flags made by the Community user. The comments are indicative of that, at least.
@JeffSchaller As already mentioned, the question was bumped by the Community user, which caused both the question and answer to be rescanned. SD had identical detections on a post which was unchanged from the last record in MS. MS no longer creates a new record if the report from a new SD report when it exactly matches the most recent prior report (exact match for all of: title, body, username, why text).
@Makyen got it; thank you! Skipping the report to the CHQ chat room (in the case of posts that had 'complete' feedback) would be more code, so: not worth chasing?
@Spevacus interesting; I held off on doing that because I saw it was subsumed by "Pattern-matching website in answer - Position 300-320: digitalmarketing.com"
I've seen some stuff posted there that I know Smokey would pick up not be reported, so I thought there was some form of protection on that post already.
