@tripleee 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 if you really want to add this pattern.
@SmokeDetector Google translation: "Don’t have a job and want to borrow money? The LBK Quanhaodai loan platform provides 24-hour matching private lending fund owners, simple and fast operation through mobile phones, as long as ID cards, automobiles and motorcycles, you can quickly obtain small capital turnover!"
I have refrained from putting recent routine IP and NS watches on autopull as they will be pulled anyway whenever something is actually being autopulled
cc @tripleee (the above discussion about bumping the SD Python version)
@ThomasWard I don't have a problem with that, but I'd probably say bump to 3.7 and deprecate 3.6. At least so far, it looks like everything I'm seeing, or adding, works on 3.6.
@ThomasWard This is where we should be, unless we have things that need 3.7. The only thing I'm really aware of is some code that, at least in a minor way, relies upon dicts using insertion order for iteration. That's functional as an implementation detail in 3.6, but fully spec'ed in 3.7.
[ SmokeDetector | MS ] Blacklisted username, offensive answer detected, potentially bad keyword in answer, potentially bad keyword in username, toxic answer detected (249): Red border/frame around screen by fuck on gaming.SE
