@Spevacus 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.
I've already experienced enough table-flipping for the week. Winter storm came through here, icing up all the trees and causing branches to fall all over the place. I was without power for 8 hours one day, and just under 36 hours another day. Only just came back on this afternoon.
@CodyGray Oh, geez. I'm sorry to hear that. I'm in a warmer area where we're only now experiencing our lowest temps at around 30 degrees. We also had a light dusting of snow yesterday morning. I'm quite thankful to not be experiencing all that snow and ice.
[ SmokeDetector | MS ] Potentially bad asn for hostname in answer, potentially bad ns for domain in answer, potentially bad keyword in answer, potentially bad keyword in username, blacklisted user (74): box-shadow doesn't work in Chrome by vuvietduc.com on stackoverflow.com
@cocomac 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 asn for hostname in answer, potentially bad ns for domain in answer, potentially bad keyword in answer, username similar to website in answer, blacklisted user (143): Spark functions vs UDF performance? by NixonData on stackoverflow.com
@CodyGray That pattern appears to be homoglyph obfuscated. It's better to use the non-obfuscated number. Perhaps try: !!/watch-number 0567563337. In order for a "number" to make an exact match, the pattern must begin with a digit or up to two of +,(,[, or { immediately followed by a digit. Append -force to the command word(s) if you really want to add the pattern you provided.
@CodyGray 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.
What's the policy for prefixes on watched numbers? I don't think that it can ignore prefixes if they are in the watched string, whereas watching the number without the prefix works fine. Do we force-watch both of them? Or only watch the version without the prefix? Something else? cc @Makyen
@CodyGray A normalized version, {{'0528604116'}}, of that pattern is already on the number blacklist. You can use !!/bisect-number 0528604116 to determine which entries on the number lists match that pattern, which would tell you: Matched by 0528604116 on line 751 of blacklisted_numbers.txt: 0528604116 found verbatim
Not sure what to make if this answer, it's totally off-track for the question (although that could be an honest mistake) but the I looked at the Q/A platform they're recommending and it's new with a total of 1 question which seems suspicious for a genuine recommendation: stackoverflow.com/a/75343725/1599751
@CodyGray 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.
@CodyGray That pattern looks like it's already caught by Bad keyword in body and Bad keyword in answer Append -force to the command word(s) if you really want to add the pattern you provided.
@CodyGray I'd go ahead and -force that. Alternately, if you add the longer one first, the shorter one won't require -force. Another alternative would be to add the longer one without a non-digit separator character after the country code, which will prevent it from being detected as the shorter number and won't need -force. Any way you add them, we want them both.
The only country code which the code automatically understands is the "1" for those in the North American Numbering Plan (NANP), which it effectively handles by adding both versions (with and without a "1") when it thinks the number is in the NANP. That already causes enough confusion such that I'm hesitant to add additional automatic handling for other country codes.
OTOH, given the overlap between NANP and India (both are 10 digits without country code), it might be reasonable to just assume the appropriate 10 digit numbers could be in either, unless it's explicit in the number or explicitly directed. Doing so probably wouldn't cause all that many FP.
