@JeffSchaller 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 905-649-9117 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 905-649-9117. Append -force to the command word(s) if you really want to add the pattern you provided.(?#No NorAm)
@Dragonrage A normalized version, {{'9059648233'}}, of that pattern is already on the number watchlist and the pattern you provided is not an exact match to an existing entry on the number watchlist. You can use !!/bisect-number +9059648233 to determine which entries on the number lists match that pattern, which would tell you: Matched by 9059648233(?#no NorAm) on line 4637 of watched_numbers.txt: 9059648233 found normalized
@Dragonrage A normalized version, {{'905964823300', '9059648233'}}, of that pattern is already on the number watchlist and the pattern you provided is not an exact match to an existing entry on the number watchlist. You can use !!/bisect-number 9059648233(?#no NorAm to determine which entries on the number lists match that pattern, which would tell you: Matched by 9059648233(?#no NorAm) on line 4637 of watched_numbers.txt: 9059648233 found verbatim
@Dragonrage That pattern appears to be homoglyph obfuscated. It's better to use the non-obfuscated number. Perhaps try: !!/blacklist-number 9120509022(#N0 N0rAm). In order for a "number" to make an exact match, the pattern must end with a digit. Append -force to the command word(s) if you really want to add the pattern you provided.
[ SmokeDetector | MS ] Blacklisted website in answer, potentially bad ip for hostname in answer, potentially bad keyword in answer, potentially bad keyword in username, blacklisted user (169): What is a real-world application for HORN? by spammer on stackoverflow.com
[ SmokeDetector | MS ] Messaging number in body, potentially bad ip for hostname in body, potentially bad keyword in body, potentially bad keyword in title (85): Buy Verified Bitget account by ARKYC ACCOUNT on stackoverflow.com
[ SmokeDetector | MS ] Bad keyword in answer, bad keyword in link text in answer, potentially bad asn for hostname in answer, potentially bad keyword in answer, username similar to website in answer (245): How to track method calling in MVC? by SAP Masters on stackoverflow.com
@JeffSchaller That pattern looks like it's already caught by Blacklisted website in body and Blacklisted website in answer Append -force to the command word(s) if you really want to add the pattern you provided.
@JeffSchaller A normalized version, {{'4915751490206'}}, of that pattern is already on the number watchlist and the pattern you provided is not an exact match to an existing entry on the number watchlist. You can use !!/bisect-number 4915751490206 to determine which entries on the number lists match that pattern, which would tell you: Matched by +4915751490206 on line 4075 of watched_numbers.txt: 4915751490206 found normalized
@JeffSchaller 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 891-882-3414 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 891-882-3414. Append -force to the command word(s) if you really want to add the pattern you provided.
