@Makyen That pattern looks like it's already caught by Potentially bad keyword in answer and Potentially bad keyword in body; append -force if you really want to do that.
@Shree That pattern looks like it's already caught by Blacklisted website in body and Blacklisted website in answer; append -force if you really want to do that.
Restart: API quota is 16201.
[ SmokeDetector | MS ] Blacklisted website in body, body starts with title and ends in url, link at end of body, pattern-matching website in body, repeated url at end of long post: Joint Advance Music genres that have by Holdxold on drupal.SE
@TetsuyaYamamoto That pattern looks like it's already caught by Potentially bad keyword in answer and Potentially bad keyword in body; append -force if you really want to do that.
[ SmokeDetector | MS ] Bad keyword in body, body starts with title and ends in url, link at end of body, link following arrow in body, pattern-matching product name in body, +3 more: Green Coffee Grano by maryihaasi on drupal.SE
> Potentially bad keyword in body, potentially bad keyword in title, potentially bad keyword in username ---------- Title - Position 1-9: baneh.com Body - Position 1-9: baneh.com Username - Position 1-9: baneh.com
@iBug That pattern looks like it's already caught by Potentially bad keyword in answer, Mostly non-latin answer, Potentially bad keyword in body, and Mostly non-latin body; append -force if you really want to do that.
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, blacklisted website in body, body starts with title and ends in url, pattern-matching product name in body, +4 more: Keto Slim Diet Be that as it ma by banlordar on graphicdesign.SE
@iBug Thanks. I was reading up on how Python and the regex module handle it. Do you know if we enable the word flag? It looks like the definition of \b is not very compatible with Unicode without using that flag.
> Mostly dots in body, mostly dots in title, pattern-matching website in body, pattern-matching website in title, pattern-matching website in username, potentially bad ns for domain in body, potentially bad ns for domain in title ---------- Title - Position 2-16: bodyprodiets.co Title - bodyprodiets.com NS suspicious dns1.namecheaphosting.com.,dns2.namecheaphosting.com. Title - Position 9-17: diets.com Title - Post contains 1 dots out of 1 characters Body - Position 2-16: bodyprodiets.co Body - bodyprodiets.com NS suspicious dns1.namecheaphosting.com.,dns2.namecheaphosting.com.
[ SmokeDetector | MS ] Blacklisted website in body, body starts with title and ends in url, link at end of body, pattern-matching website in body, repeated url at end of long post: Joint Advance You might be informed by Holdxold on askubuntu.com
@iBug Yes, and no. The documentation for regex indicates that if the word flag is not set, then \b matches \w\W, \W\w, ^\w, and \w$ (not ^\W or \W$) where \w and \W are defined as [A-Za-z0-9_] and [^A-Za-z0-9_]. With the word flag set, then \w and \W use Unicode definitions.
I've seen some behavior where watches/blacklist-keywords haven't matched where I would have expected them to match. This could be a result of using non-Unicode definitions of \w and \W for \b while doing searches on Unicode strings, with definitions of \w and \W being Unicode for everything other than \b and line separators (rarely noticed, due to SE not using Unicode line endings and our use of the DOTALL flag.
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, blacklisted website in body, link at end of body, pattern-matching product name in body, +4 more: Where to buy purefit keto? by tinamejias on meta.SE
@iBug That pattern looks like it's already caught by Bad keyword in answer, Mostly non-latin body, Mostly non-latin answer, and Bad keyword in body; append -force if you really want to do that.
@iBug This is the text I was talking about. It says "The WORD flag changes the definition of a ‘word boundary’ to that of a default Unicode word boundary. This applies to \b and \B." There are multiple ways that sentence could be interpreted. I'd have to find more explicit documentation, read the source, and/or test to determine exactly what they mean. However, it's probably this.
@iBug if this is the one you are grappling with, I remember changing \W around it to \w on the notion that the original \W was probably a mistake there
commit 570fbb1d6ae458c3927e39a22a005435b49470b9 Aug 24
File "/home/ubuntu/charcoal/SmokeDetector/deletionwatcher.py", line 47, in _start msg = self.socket.recv()
File "/home/ubuntu/charcoal/SmokeDetector/env/lib/python3.6/site-packages/websocket/_core.py", line 293, in recv opcode, data = self.recv_data()
File "/home/ubuntu/charcoal/SmokeDetector/env/lib/python3.6/site-packages/websocket/_core.py", line 310, in recv_data opcode, frame = self.recv_data_frame(control_frame)
File "/home/ubuntu/charcoal/SmokeDetector/env/lib/python3.6/site-packages/websocket/_core.py", line 323, in recv_data_frame
@tripleee I added the \W* to those. I added them because it wasn't matching in spots where it was intended to match. You're correct that doing so was a mistake, although a couple that hadn't worked did match correctly after the change (i.e. minimal testing passed). The choice assumed we weren't dealing with Unicode versions of \w and \W. Given Unicode \w and \W, the \w* is correct, unless we are dealing with some screwy definition of \b, which is what we've been talking about.
For what we're doing we want a \b that is defined as \w\W (and the other combinations, see above) where the \w and \W used for \b are also defined as Unicode. I was under the impression we were still having problems with matching those Unicode regexes, even with the \w*, which is what lead me towards the possibility of our having a not identically compatible definition for \b. But, if we're not having a problem matching those, then there's no need to spend time on it.
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, bad pattern in url body, blacklisted website in body, pattern-matching website in body, +1 more: Erogen X Reviews by kfbzgsad on apple.SE
[ SmokeDetector | MS ] Url in title, bad keyword in body, blacklisted website in body, pattern-matching product name in body, pattern-matching website in body, +1 more: youtu.be/WMxfhrPNIHI by BrandonCarlson on gaming.SE
