@tripleee That pattern looks like it's already caught by Mostly non-latin body and Mostly non-latin answerThe regex contains an unescaped ".", which should be "\." in most cases. Append -force to the command word(s) if you really want to add the pattern you provided.
@tripleee An invalid pattern was provided, please check your command.
@tripleee 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.
@tripleee 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 995-916-5635 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 995-916-5635. Append -force to the command word(s) if you really want to add the pattern you provided.
[ SmokeDetector | MS ] Pattern-matching website in answer, 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 (149): Java Fitness Function Not Working by A2ZFITNESSHUB on stackoverflow.com
@cigien 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.
@cigien A normalized version, {{'9959165635'}}, of that pattern is already on the number blacklist. You can use !!/bisect-number 9959165635 to determine which entries on the number lists match that pattern, which would tell you: Matched by 9959165635(?#NO NorAm) on line 778 of blacklisted_numbers.txt: 9959165635 found verbatim
(for what it's worth, the argument to !!/pull doesn't do anything, it's just something I do locally to remind myself when to pull, and this time I forgot to delete it before hitting Enter)
@cigien This should also exclude "applogz.medium.com", so applogz(?!\.com)(?!\.medium\.com).
@Pilot6 !!/bisect operates on the exact text which you have in the chat message, so !!/bisect complete-thesis\.com probably didn't do what you were intending. You probably wanted !!/bisect complete-thesis.com.
@tripleee Thanks for doing that. It's good, of course. I merged it. I hadn't actually made any changes. I had looked at the issue, identified the file where the change needed to happen, but then searched for all the other places where we have "http:" in the repo, which is quite a few with some others that should probably be updated and many that shouldn't (e.g. in licenses, etc.), so hadn't actually done anything yet. I really appreciate trying to coordinate effort, but for something that's such a small amount of text being changed, particularly to just a single file, please feel free to go ahead and do it.
Even if I do have something in process, handling a single line of a merge conflict is really not a problem. I don't want you or anyone else to feel they can't/shouldn't work on things because of me, but I do appreciate coordination when reasonably possible, as I'd prefer there not be a lot of duplication of effort.
However, as I type this, I know (realize once again) that's really largely on me, as I'm really not doing a good job of sharing where I am with things I'm working on (e.g. by having draft PRs, branches pushed publicly, etc.). So, I should really improve here.
@Makyen 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.
teward/Thoth: In getting MS post information, recovered from requests.exceptions.ReadTimeout: HTTPSConnectionPool(host='metasmoke.erwaysoftware.com', port=443): Read timed out. (read timeout=10.0)
[ SmokeDetector | MS ] Potentially bad asn for hostname in body, potentially bad ns for domain in body, potentially bad keyword in body (3): UGC APPROVED JOURNAL by grljournals on serverfault.com
@JeffSchaller I'm getting into it... I've the Mayken userscript installed, but i think it is limited. I don't want to use it, if I'm not 100% sure how the output would look like, since there is no "preview/confirm". Sometimes I would not know what the output into the chat would look like
Oh, chat is a whole different problem! :) If you're not sure what it would match, one decent option would be to search MS (metasmoke.erwaysoftware.com/search) and put the regex in the Body search (be sure to tick the "regex" box). It's not 100% the same as an MS scan, since it would "or" that regex with the same search in the itle and username fields, but for something you know is in the body, it's a decent start
I admit, the first shortcut I used was the github auto-generated report from MS, which I like to check before approving PR's
The regex part that caused this mixup is just the ? at the end of your initial watch, which causes all of the (...) stuff to become optional in the match, meaning the only part that is/was required to match was the 3 letters sri. I think that style of watch is seen in other emaili /watches, but maybe those usernames were longer or more specific than "sri"
