@Vickel 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 875-721-7751 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 875-721-7751. Append -force to the command word(s) if you really want to add the pattern you provided.
@VLAZ that's the best I have; Makyen would point out that there's even limitations when searching via MS, too. The only shortcut I sometimes see/use is that the domain pages on MS will summarize the tp/fp where that domain is seen.
@JeffSchaller Yep, I also use the domain pages, since it's faster and convenient. But other regex watches can't really be examined like that... Well, alright, I was just checking if I wasn't missing anything there.
lol, I couldn't figure out what the first two feedbacks were. Candle and droplet? What does it mean? Turns out, it was just emoji in the title. Doesn't really make it any clearer what those mean, but at least I didn't just feedback types I never knew exited:
2
Oh, the first one is apparently penguin. Not sure how it relates to inequality (it's some maths question). Maybe penguin society embraces inequality or something.
> Potentially bad ns for domain in body, potentially bad ns for domain in title, potentially bad keyword in body, potentially bad keyword in title, potentially bad keyword in username ---------- Potentially bad keyword in body - Position 0-12: testleaf.com Potentially bad keyword in title - Position 0-12: testleaf.com Potentially bad keyword in username - Position 0-12: testleaf.com Potentially bad ns for domain in body - testleaf.com NS suspicious ns58.domaincontrol.com.,ns57.domaincontrol.com.
Apparently I forgot to post these this morning. Switched back to the other computer and noticed I had them in a text document. Also, apparently the domain was already watched anyway.
Right, that generated the report. But this report has an ignore feedback from 8 months ago. It was bumped by Community now and Smokey reported it. I thought it shouldn't.
@VLAZ Matched by (?:support|service)(?!/)(?!(?:[^<]++|<(?!\/?code>))*+<\/code>)(?:\W++(?:\w(?<!\d))++)?[\W_]*+(?!\d\d(?:\d\d)?[:-]\d\d[:-]\d\d(?:\d\d)?(?:\b|\D))(?:2[\W_]*+4(?:[\W_]*+7)?|(?:\d[\W_]*+){6,12}) on line 66054 of watched_keywords.txt
@ThomasWard Hello! I'm hoping to do another watchlist/blacklist scrub offline with an MS dump; the last one was in Feb, and I see your note where it required more work for you to migrate. Is that something that's still on your radar?
@ThomasWard perfect! It's just something I like to do to help out with the quality standards around here, so I'll keep an eye out for a future announcement. Thanks!
i need to finish up my code for adjusting the watch-number command. maybe ill get to it this weekend. though I am starting a new job that has me working graveyard shift thursday through monday. so maybe on my off day ill get to it
@music2myear ╳ You are not a privileged user. Please see the privileges wiki page for information on what privileges are and what is expected of privileged users.
