Matched by the following regexes: wixsite\.com on line 195 of watched_keywords.txt duro[\W_]*+xl(?:[\W_]*+(?:male|review|enhancement|\d++|[\da-f]{5,}+)s?)* on line 26498 of watched_keywords.txt
@CodyGray That pattern looks like it's already caught by Potentially bad keyword in body and Potentially bad keyword in answer; append -force if you really want to do that.
Yeah. Texas and California are both big places, then there are other states in between.
From Austin, I can drive straight for 10 hours on highways (so, approximately 70 miles per hour) without leaving the state. And Austin is pretty much in the center of the state.
@Yatin The exact differences are multiple and would take considerable time/space/effort to detail (and someone has probably already made something of a stab at it, so I'd just search, if I was answering in full). However, we don't use the stock Python regular expression engine. SmokeDetector uses the regex regular expression engine, which is much closer to PCRE (or PCRE2) than it is to the Python re engine.
Why they used Python 2.7 for new functionality, given that Python 2 is EOL, I have no idea.
I'm also not familiar enough with the PHP implementations of PCRE and PCRE2 to be able to tell you which is closer to what we use. Interestingly, given that JavaScript now supports variable length look-behinds, it may be more effective to use the JavaScript engine, under some circumstances. It doesn't support possessive quantifiers (e.g. \W*+), but that will, usually, be less of a functional difference than not supporting variable length look-behinds.
@CodyGray You can't do that here :) The buy order thing's not what's causing the issue I'm pretty sure. It's the cbd gummies and I can't change the order of that. Unless I add cbd and gummies to the alternation, but I definitely don't want to just be catching poor Rachael Ray
room topic changed to Charcoal HQ: Where diamonds are made, smoke is detected, and we break things by developing on production. 180k true positives and counting. This room is for Charcoal, which focuses on detecting and eliminating spam and rude/abusive posts on all SE sites. For more information, see charcoal-se.org/about. Handy links: metasmoke.erwaysoftware.com, github.com/Charcoal-SE [dev-on-prod] [flag-based-fraternity] [programmatic-crowbars]
@CodyGray I already spent so much time learning everything, including subtle nuances, about how one Q&A engine works. Having to learn all about a new engine from the ground up would be too much work :)
@cigien That pattern looks like it's already caught by Bad keyword in answer, Bad keyword in body, and Pattern-matching product name in body; append -force if you really want to do that.
Matched by the following regexes: consultant\.com on line 2425 of watched_keywords.txt consultant(?:\.|\W*dot\W*)com on line 16726 of watched_keywords.txt
@Yatin That pattern looks like it's already caught by Potentially bad keyword in body and Potentially bad keyword in answer; append -force if you really want to do that.
@Yatin That pattern looks like it's already caught by Potentially bad keyword in body and Potentially bad keyword in answer; append -force if you really want to do that.
