@Makyen 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 if you really want to add the pattern you entered.
:61129809 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 if you really want to add the pattern you entered.
@SmokeDetector Based on a Google translate: While this does offer to pay, doing so appears incidental to the question which is asked. I'd even agree that it's something that would be reasonable for SE to block in its current state. However, if it was in English, then it would almost certainly merely be closed and/or people would work with the OP to edit it into something that could be asked (maybe). Overall, it doesn't seem like something which we should be red-flag nuking.
@JonasCz An autoflag from you was used on this post [MS] which appears to be a false positive, IMO. You may want to evaluate the post yourself and retract the flag, if appropriate. I'd note that the post is not in English and that my evaluation of it is based on a Google translate. It is a question which should be closed, but I don't feel red-flag nuking it is the right thing to do.
@SmokeDetector @tripleee @Makyen do either of you know why SD re-reported a question days later? I get why it would be nice if it has no feedback, but seeing as it has four FPs I’m confused…
@cocomac yes, it should. These things happen sometimes when the primary gets stuck on something for a long enough time to seem to have lost its connection
@tripleee Thanks! I'm not very familiar with the 'admin'/instance control commands (I know the basic commands, but I don't mess with the instances) which is why I pinged you and Makyen. But thanks!
@tripleee 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 if you really want to add the pattern you entered.
@tripleee 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 if you really want to add the pattern you entered.
[ SmokeDetector | MS ] Potentially bad ns for domain in body, potentially bad keyword in body, potentially problematic ns configuration in body, blacklisted user (74): Select the appropriate capacitor ✏️ by fcbuy on webapps.SE
[ SmokeDetector | MS ] Link at end of answer, potentially bad asn for hostname in answer, potentially bad ns for domain in answer, potentially bad keyword in answer (64): Buy weed in Europe online by Nnoko339 on meta.SE (@Ollie)
@tripleee The regex contains an unescaped ".", which should be "\." in most cases. Append -force to the command if you really want to add the pattern you entered.
@tripleee A normalized version, {'8664070171', '18664070171'}, of that pattern is already on the number blacklist. You can use !!/bisect-number +1 866 407 0171 to determine which entries on the number lists match that pattern.
That pattern may be a North American number. If it is, please use a format which starts with an optional `1` followed by possible separator text and has the main number in the format `906-442-3466` where `-` could be a single alpha character or any `[\W_]*+`. Alternately, you can add the comment `(?#IS NorAm)` to the end of the pattern to force also using the alternate normalized form, or `(?#NO NorAm)` if it's not a North American phone number and it's incorrectly recognized as one. Perhaps try
@SmokeDetector fp- Possibly just a low quality question, but the timing of the spam answer is suspect. Keeping an eye on the user in case it's spam seed.
