[ SmokeDetector | MS ] Blacklisted website in answer, pattern-matching website in answer, potentially bad ip for hostname in answer, potentially bad ns for domain in answer, blacklisted user (246): Celsius to Fahrenheit conversion- JavaScript by d kumar on stackoverflow.com
Makyen/EC2-linux received failover signal. <-- This probably shouldn't have happened. Check if there are any operational notifications from Thomas Ward, which are usually pinned in the sidebar. If Cerberus is operational (i.e. use the !!/location command to see if it responds), then consider executing !!/standby Makyen/EC2-linux to put this instance back in standby. @Makyen
[ SmokeDetector | MS ] Bad ns for domain in body, link at beginning of body, potentially bad asn for hostname in body, potentially problematic ns configuration in body, repeated url at end of long post (243): XCode Editing Process? by mac travels on stackoverflow.com
@VLAZ 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.
@Cow try to use non-capturing groups when capturing is not needed. When using (some sub-pattern here) the regex engine will keep a note of the match inside the brackets which means more memory usage. Instead use (?:some sub-pattern here) which acts the same (e.g., allowing alteration inside with | or repetition of the group) but the regex engine does not need to keep the result of the sub-match.
@Cow np. It's a small thing but can help when you need to run a regex over very large bodies of text. Or just match things repeatedly. FWIW, it's a very common issue that shows up all the time. It's just something you need to be aware with regex.
@Cow to match zero or one "s", to match "consultant" or "consultants", which, as I write that out, if you've matched "consultant" you've also matched "consultants", so I wouldn't bother with the s?
@VLAZ I do usually make the computer do the hard thing and make it easier for a future human to read, but I think there's some sensitivity to speed for this massive pile of regex we have going :)
@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.
@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.
@Cow A normalized version, {{'00201067580194'}}, of that pattern is already on the number watchlist and the pattern you provided is not an exact match to an existing entry on the number watchlist. You can use !!/bisect-number 00201067580194 to determine which entries on the number lists match that pattern, which would tell you: Matched by 002-01067580194 on line 4734 of watched_numbers.txt: 00201067580194 found normalized
