@Ethan That pattern looks like it's already caught by Mostly non-latin body and Mostly non-latin answer Append -force to the command word(s) if you really want to add the pattern you provided.
@Spevacus Are you sure this watch will catch anything the "mostly latin" body reason wouldn't? I didn't approve it because MS doesn't like that search, whether regex or like matches.
Besides that, watching the domain only would catch more spam if that website is used again, as there are other subdomains
@Ollie I figured it'd, at least, catch the existing pattern if it shows up again. A more proper watch would also handle other homoglyph obfuscation, but... That's a lot to ask of a PR.
@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.
[ SmokeDetector | MS ] Blacklisted website in body, potentially bad ns for domain in body, potentially bad keyword in body, potentially bad keyword in title, blacklisted user (172): 5 website to make money online? by Fz _Madra on gaming.SE
@tripleee I definitely don't remember. It's possible that I wanted them to be explicitly not case-sensitive, and I didn't remember that that was the default... I would check to see what the detections are (TPs and FPs) with and without case sensitivity if I were you, rather than just assuming they're meant to be case-sensitive.
@tripleee 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 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 871-218-6898 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 !!/watch-number 871-218-6898. Append -force to the command word(s) if you really want to add the pattern you provided.
@CodyGray A normalized version, {{'918712186898'}}, of that pattern is already on the number watchlist. You can use !!/bisect-number +91-8712186898 to determine which entries on the number lists match that pattern, which would tell you: Matched by +91-8712186898 on line 3029 of watched_numbers.txt: +91-8712186898 found verbatim
@CodyGray A normalized version, {{'918179496603'}}, of that pattern is already on the number watchlist. You can use !!/bisect-number +91-8179496603 to determine which entries on the number lists match that pattern, which would tell you: Matched by the following: +91 8179496603 on line 3190 of watched_numbers.txt: 918179496603 found normalized 8179496603(?#NO NorAm) on line 3213 of watched_numbers.txt: 8179496603 found verbatim
@CodyGray A normalized version, {{'916309565721'}}, of that pattern is already on the number watchlist. You can use !!/bisect-number +91-6309565721 to determine which entries on the number lists match that pattern, which would tell you: Matched by the following: +91 6309565721 on line 3191 of watched_numbers.txt: 916309565721 found normalized 6309565721(?#NO NorAm) on line 3212 of watched_numbers.txt: 6309565721 found verbatim
[ SmokeDetector | MS ] Bad ip for hostname in body, bad keyword in body, bad keyword in link text in body, blacklisted website in body, potentially bad keyword in body (362): How can I learn medical data science? by Amit A on stackoverflow.com
[ SmokeDetector | MS ] Blacklisted website in body, link at beginning of body, potentially bad asn for hostname in body, potentially bad ip for hostname in body, potentially bad ns for domain in body, +1 more (213): Home appliance repair services? by Appliance Repair on askubuntu.com
[ SmokeDetector | MS ] Blacklisted website in answer, potentially bad ip for hostname in answer, potentially bad ns for domain in answer, potentially bad keyword in answer (97): Microsoft Office Packages by Aleks Gjoni on superuser.com
[ SmokeDetector | MS ] Blacklisted website in answer, potentially bad ip for hostname in answer, potentially bad ns for domain in answer, potentially bad keyword in answer, potentially bad keyword in username, +1 more (168): Install Office 365 E1 on office 2019 by Microprokey on stackoverflow.com
@CodyGray A normalized version, {{'84947671524'}}, of that pattern is already on the number watchlist. You can use !!/bisect-number +84 94 767 1524 to determine which entries on the number lists match that pattern, which would tell you: Matched by +84 94 767 1524 on line 3374 of watched_numbers.txt: +84 94 767 1524 found verbatim
@CodyGray 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.
