@Dragonrage If they posted it of their own volition I don't see a reason to make it go away. If they asked for it to be redacted it might be a diff story.
@Anerdw sometimes the watch/blacklist command will deobfuscate it by itself. othertimes it doesnt like it and it can be better to use the command to deobfuscate it first
!!/reject- 13300 "normalized version is now blacklisted. unneeded (unspecified blacklister also may have not seen this PR when said normalized version was blacklisted)"
@DavidW huh, im a bit surprised at that. I know some of the mods there like to send mod messages for first offence of (possible) self promotion/non attribution. if the question is spam flag nuked without a mod flag, it is much harder to find and send a message for
@VLAZ 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 word(s) if you really want to add the pattern you provided.
@VLAZ That pattern looks like it's already caught by Blacklisted website in answer and Blacklisted website in body Append -force to the command word(s) if you really want to add the pattern you provided.
@VLAZ 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 word(s) if you really want to add the pattern you provided.
@VLAZ A normalized version, {{'919677555651'}}, of that pattern is already on the number watchlist. You can use !!/bisect-number +91 9677555651 to determine which entries on the number lists match that pattern, which would tell you: Matched by +91 9677555651 on line 3910 of watched_numbers.txt: +91 9677555651 found verbatim
@Dragonrage I'm probably reading too much into it - the majority of custom-flags in the past have been accepted, so maybe I just caught someone on a bad day
@Dragonrage 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 word(s) if you really want to add the pattern you provided.
@VLAZ 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 865-390-9612 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 !!/blacklist-number 865-390-9612. Append -force to the command word(s) if you really want to add the pattern you provided.
@VLAZ 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 word(s) if you really want to add the pattern you provided.
[ SmokeDetector | MS ] Potentially bad ip for hostname in body, potentially bad ns for domain in body, potentially bad keyword in body (3): ai develo[pment by ai development on wordpress.SE
