[ SmokeDetector | MS ] URL in title, bad keyword in body, bad keyword in title, link at end of body, pattern-matching website in body, pattern-matching website in title, repeated URL at end of long post: supplementlab.org/hl-slim-pro/ by seend topi on drupal.stackexchange.com
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, pattern-matching website in body, repeated URL at end of long post: HL Slim Pro Taking creatine by gaki on stackoverflow.com (@dorukayhan)
tpu- by 4castle
[ SmokeDetector | MS ] URL in title, bad keyword in body, bad keyword in title, pattern-matching website in body, pattern-matching website in title: supplementlab.org/hl-slim-pro/ by seend topi on apple.stackexchange.com
On branch master Your branch is ahead of 'origin/master' by 1 commit. (use "git push" to publish your local commits) nothing to commit, working directory clean
[ SmokeDetector | MS ] URL-only title, bad keyword in body, bad keyword in title, link at end of body, pattern-matching website in body, pattern-matching website in title, repeated URL at end of long post: supplementlab.org/hl-slim-pro/ by xatozi on askubuntu.com (@ThomasWard)
@Seth I was originally planning to manually write an entry into the MS DB, but I've never done it before and looking at the code it was going to be a lot harder than I thought. Don't worry about
[ SmokeDetector | MS ] URL in title, bad keyword in body, bad keyword in title, pattern-matching website in body, pattern-matching website in title, repeated URL at end of long post: supplementlab.org/hl-slim-pro/ by needhampearce448 on apple.stackexchange.com
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, link at end of body, pattern-matching website in body, repeated URL at end of long post: HL Slim Pro time of summer by seend topi on superuser.com
[ SmokeDetector | MS ] URL-only title, bad keyword in body, bad keyword in title, link at end of body, pattern-matching website in body, pattern-matching website in title, repeated URL at end of long post: gomusclebuilding.com/reaction-male-enhancement/ by jeffreurry on askubuntu.com (@ThomasWard)
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, link at end of body, pattern-matching website in body: Testosterone Supplement by revimad on workplace.stackexchange.com
[ SmokeDetector | MS ] URL in title, bad keyword in body, bad keyword in title, link at end of body, pattern-matching website in body, pattern-matching website in title, repeated URL at end of long post: supplementlab.org/hl-slim-pro/ by EdithPatrick on workplace.stackexchange.com
Given the massive score of that post, it should've cast an autoflag.
!!/errorlogs 50
@ArtOfCode it's not urgent, but you might want to have a look why this post ^ didn't get autoflagged. It doesn't appear as a failure in the flagging logs.
@M.A.R. You can select them all, even if you don't have accounts on all. If it tries to flag on a site you have no account on, it'll simply errror out and move to the next eligible flagger.
I share your concerns, but there are measures in place to prevent those human errors before they happen.
user61230
8:29 AM
Especially when it comes to spam flags, which are designed to work by human agreement and consensus, not automated processes, and carry heavy penalties. I guess it depends on how they're implemented.
I'm pretty confident that undo and art and thomas have a pretty strong grip on that stuff
user61230
No matter how strong someone's grip on the subject matter, human errors happen. Every major website or service has had a big screwup at one point or another.
@Emrakul The worst that could happen (the system running haywire and auto-destroying a bunch of mundane stuff) would still be completly logged (so it's undoable), and any privileged smokey member can stop all autoflagging via command
@Emrakul It's all still logged, and SE has measures to undo the damage quickly, i'm sure they could even do it in bulk (since we're using the same API key for all cast flags and doing it from the same IP)
All this is in the hypothethical case that the flagging decides to go completly haywire (very unlikely) in a time frame where nobody is here (so pretty much only weekend nights / early mornings and even then 1 guy is usually here)
Still, I think that in the long run, this saves the community so much time that even if it would fail at a point and require some major intervention from Stack Overflow itself, it's still worth it.
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, link at end of body, pattern-matching website in body, repeated URL at end of long post: glimpse HL Slim Pro usually by whe ng1942 on drupal.stackexchange.com
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, pattern-matching website in body, repeated URL at end of long post: HL Slim Pro usually by whe ng1942 on apple.stackexchange.com
@AshishAhuja Title - Key phrase: technical support
[ SmokeDetector | MS ] URL in title, bad keyword in body, bad keyword in title, link at end of body, pattern-matching website in body, pattern-matching website in title: maleenhancementshop.info/profollix/ by sallyiduran on drupal.stackexchange.com
@ArtOfCode getting Uncaught TypeError: $(...).selectpicker is not a function in console when loading the autoflagging new condition page, tried force reload as suggested in #73, but still gives the error
Ok, the screen seems to work, even if it keeps giving the error
We could try inserting the library JS itself into application.js
Since it appears to be the only thing not loading
Also @art, do you think that it would be a good idea to add a form on MS for admins only which allows them to add a post to the MS DB? Sorta like !!/report for deleted posts, so that when network mods come around with a screenshot of deleted spam we can manually add it to our records
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, blacklisted website in body, pattern-matching website in body, repeated URL at end of long post: Skin Opulent Serum rich in section by nuju on stackoverflow.com (@dorukayhan)
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, blacklisted website in body, link at end of body, pattern-matching website in body, repeated URL at end of long post: Skin Opulent Inside directly by brild sonia on drupal.stackexchange.com
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, blacklisted website in body, link at end of body, pattern-matching website in body, repeated URL at end of long post: Skin Opulent y are prone by jusi on askubuntu.com (@ThomasWard)
@ArtOfCode a CDN, though you can download the source files in minefield form. Search for bootstrap-select if you want to try it now, otherwise I can give it a go in the morning
@ArtOfCode you probably don't have tools to deploy metasmoke, but if absolutely necessary that public key is on the ssh list. ssh -i ~/path/to/privkey.pem -p 65522 ubuntu@34.197.90.29 should work, maybe test it before I disappear
@Glorfindel So the flagging routine did run on that, but failed with some obscure error - and the resulting failed flag log was never committed to the database, because its transaction got rolled back.
