@Cow 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.
@JeffSchaller Programmatically defining what text is a domain when it's not in an actual href is ... difficult and significantly prone to misidentification. Currently, for automagically adding a domain to a post MS only uses domains within actual HTML links. IMO, a better solution might be to programmatically possible domains within the title, body, and username and present adding them to the post as options to users with the appropriate Roles. An addition to that could be to have MS identify domains that are in the why text which SD has used as part of the reported detections.
In addition, adding new domains could be made easier, such that it's not a manual two-stage process where the user has to navigate to a different page to first create the domain, then add the domain from the post page.
I think it'd be useful to capture some of your wisdom in an easily findable place, for whoever wants to tackle it. Can I quote your response on the GH FR?
@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 851-999-1679 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 851-999-1679. Append -force to the command word(s) if you really want to add the pattern you provided.
@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 933-407-5598 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 933-407-5598. Append -force to the command word(s) if you really want to add the pattern you provided.
@Makyen great news; this already exists as Issue #802 from tripleee circa 4 years ago. Now I have /another/ reason to get a local MS instance going so I can learn ruby and scratch the itch...