[ SmokeDetector | MS ] Offensive body detected, offensive title detected, toxic body detected (162): your full of shit by ffred on christianity.SE (@Nathaniel)
[ SmokeDetector | MS ] Bad keyword in body, blacklisted website in body, body starts with title and ends in url, link at end of body, pattern-matching product name in body, +3 more (594): Theres no magic system to losing weight by user934978 on askubuntu.com
It's mostly post bodies, which are currently not used anywhere except search_fast, so I need to finish search_fast to make it worth using over normal search.
@iBug Pretty sure we're on MySQL, and that lives on a different box, although I'm not sure cc @Undo
wasn't the issues caused by a MySQL -> Maria migration (instead of a clean Maria setup)?
Developed and hosted two Flask apps for school events a few days earlier, both of which runs on Maria, and I got my first experiences with managing web apps with DB.
The school-provided server runs CentOS and Maria 5.5, as well as terrible CJK character support. Sorta forced a yum update before it became merely usable.
Not to count the question marks all around, pressing backspace deletes half a character, and that's when readline begins to mess up.
[ SmokeDetector | MS ] Url in title, bad keyword in body, bad keyword in title, blacklisted website in body, blacklisted website in title, +5 more (790): amazontrial.com/vexgen-keto/ by jenniease on graphicdesign.SE
@thesecretmaster I was strongly under the impression MS is still on MariaDB. If we were back on MySQL, then some searches we do on MS wouldn't be functioning.
@Undo / @ArtOfCode Reasonably large MS change that I just made: Now there is a redis_log method defined in ApplicationController and that method takes a string as an argument and will stick it into redis logs. This should ideally let us migrate fully off the old prod-log system.
If anyone is interested in helping me do the /search -> /search_fast migration, bug finding would be super useful. Just generally, any query that returns different results in /search and /search_fast.
@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.
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, blacklisted website in body, pattern-matching product name in body, pattern-matching product name in title, +4 more (692): NutraKick Male Enhancement Pills by defuanavilad on boardgames.SE
[ 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, +3 more (590): Keto X Factor Weight by titufadud on apple.SE
[ SmokeDetector | MS ] Url in title, bad keyword in body, bad keyword in title, blacklisted website in body, blacklisted website in title, +8 more (990): 360nutra.org/tevida/ by xiliqibo on gamedev.SE
@quartata I didn't want to share accounts with Thunder as a matter of principle, and then when I had to create a separate account to work around a problem with room permissions, I decided I might as well make it permanent
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, blacklisted website in body, link at end of body, potentially bad ip for hostname in body, +2 more (495): where to buy VexGen Keto by AnnetteSpencek on superuser.com
[ SmokeDetector | MS ] Bad keyword in body, blacklisted website in body, body starts with title and ends in url, link at end of body, pattern-matching website in body, +3 more (592): you should join another program by user1008348 on superuser.com
[ SmokeDetector | MS ] Url in title, bad keyword in body, bad keyword in title, blacklisted website in body, blacklisted website in title, +7 more (891): 360nutra.org/tevida/ by umessakenu on expressionengine.SE
[ SmokeDetector | MS ] Url in title, bad keyword in body, bad keyword in title, blacklisted website in body, blacklisted website in title, +9 more (1186): walgreensdiet.com/nutrakick/ by nimjoy on boardgames.SE
[ SmokeDetector | MS ] Url in title, bad keyword in body, bad keyword in title, blacklisted website in body, blacklisted website in title, +5 more (787): wheretobuyy.com/breast-actives/ by anniere on 3dprinting.SE
tpu- feedback received
[ SmokeDetector | MS ] Bad keyword in body, blacklisted website in body, body starts with title and ends in url, pattern-matching website in body, potentially bad ns for domain in body, +1 more (393): thing, it is made of unadulterated normal by sdfgdfhdq on graphicdesign.SE
@double-beep 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.
@double-beep 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.
@double-beep That pattern looks like it's already caught by Pattern-matching website in answer and Pattern-matching website in body; append -force if you really want to do that.
@double-beep 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.
@double-beep 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.
@double-beep 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.
> Url in title, potentially bad keyword in body, potentially bad keyword in title, potentially bad keyword in username ---------- Potentially bad keyword in body - Position 20-31: heppylosrow Potentially bad keyword in title - Position 20-31: heppylosrow Potentially bad keyword in username - Position 20-31: heppylosrow Url in title - Position 0-18: https://medium.com
@angussidney Invalid input type given for an argument
RAN: /usr/bin/git push origin master
STDOUT:
STDERR: To github.com:Charcoal-SE/SmokeDetector.git ! [rejected] master -> master (non-fast-forward) error: failed to push some refs to 'git@github.com:Charcoal-SE/SmokeDetector.git' hint: Updates were rejected because the tip of your current branch is behind hint: its remote counterpart. Integrate the remote changes (e.g. hint: 'git pull ...') before pushing again. hint: See the 'Note about fast-forwards' in 'git push --help' for details.
STDERR: To github.com:Charcoal-SE/SmokeDetector.git ! [rejected] master -> master (non-fast-forward) error: failed to push some refs to 'git@github.com:Charcoal-SE/SmokeDetector.git' hint: Updates were rejected because the tip of your current branch is behind hint: its remote counterpart. Integrate the remote changes (e.g. hint: 'git pull ...') before pushing again. hint: See the 'Note about fast-forwards' in 'git push --help' for details.
