[ 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: nuvieskincareserum.com/luxia-no-7/ by sdfdser on drupal.stackexchange.com
[ SmokeDetector | MS ] Bad keyword in body, blacklisted website in body, pattern-matching website in body, repeated URL at end of long post: it onTrue to its word Size by ristinajuri on stackoverflow.com (@dorukayhan)
[ 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: maleenhancementshop.info/virilax/ by tonyaidowd on askubuntu.com (@ThomasWard)
[ 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: muscle groups via additional rigid? by sinyshelly on drupal.stackexchange.com
We are receiving documentation requests from new Stack Overflow members with a reputation of 1 that look like this:
I ran this through Google Translate, and it's clearly SPAM.
Please, can someone raise the minimum required reputation for posting user requests? Otherwise we'll keep on getting ...
[ SmokeDetector | MS ] 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: www.ifirmationantiagingcream.com/bioslim-fr/ by user630366 on askubuntu.com (@ThomasWard)
[ SmokeDetector | MS ] URL in title, blacklisted website in body, blacklisted website in title, pattern-matching website in body, pattern-matching website in title, repeated URL at end of long post: healthflyup.com/astoria-vr/ by hukema on apple.stackexchange.com
tpu- by Glorfindel
[ SmokeDetector | MS ] URL in title, blacklisted website in body, blacklisted website in title, pattern-matching website in body, pattern-matching website in title, repeated URL at end of long post: healthflyup.com/astoria-vr/ by Forcesel73 on graphicdesign.stackexchange.com
[ SmokeDetector | MS ] Bad keyword in title, bad keyword with email in body, blacklisted website in body, repeated URL at end of long post: Online OBIEE Training by muneer12 on stackoverflow.com (@dorukayhan)
@hichris123 OK, but they're also used sometimes in gibberish. And even if that is considered a side effect, this might change in the future. To me, more data = better.
I know already and understand why we don't want to !!/report NAA's, as there are too many of them and it's harder to detect them with regexes. But gibberish/vandalism should be doable.
@ArtOfCode Depends on how it's built, but if one could get hold of a metasmoke key (not hard), or just deploy some rogue code (easier), then sit in chat and tp stuff...
Not really sure what the motivation for that would be, but people are weird.
At a maximum security level, have a separate Smokey instance that doesn't post to chat and doesn't allow automatic pulling, on a trusted person's server.
@ArtOfCode this is why I had the backup of the code on my hypervisors - just in case i need to do a very quick switch to fix a tiny thing, but don't want to rely on everyone being around XD (Also, a test bed for deploying Smokey changes, and such... gonna actually test the 'bad credentials' thing in a short while... since I'm a little bored and have nothing else to do)
also in case anyone cares, @AquariusOne is my sockpuppet - one of the reasons it's explicit-write here - with the privileged access I have as diamondmod, to test with an unpriv'd account :)
@ArtOfCode well the one problem is if the account is hijacked or a rogue Smokey rolling around with creds. If we limit it to autoflag using someone specific's account that we can always shut that account on the offending site (CMs can shut it globally) and then we address the problem there (change all the credentials!)
that's the biggest thing on my radar in terms of "abuse risk"
We are receiving documentation requests from new Stack Overflow members with a reputation of 1 that look like this:
I ran this through Google Translate, and it's clearly SPAM.
Please, can someone raise the minimum required reputation for posting user requests? Otherwise we'll keep on getting ...
