> Potentially bad keyword in body, potentially bad keyword in title, potentially bad keyword in username ---------- Title - Position 1-13: Upayogee.com Body - Position 1-13: Upayogee.com Username - Position 1-13: Upayogee.com
> Potentially bad keyword in body, potentially bad keyword in title, potentially bad keyword in username ---------- Title - Position 1-17: guidancepoint.in Body - Position 1-17: guidancepoint.in Username - Position 1-17: guidancepoint.in
> Bad keyword in title, pattern-matching website in body, pattern-matching website in title ---------- Title - Position 1-23: testosteroneboosterweb Title - Position 1-26: testosteroneboosterweb.co Body - Position 1-26: testosteroneboosterweb.co
[ SmokeDetector | MS ] Bad keyword in body, blacklisted website in body, link at end of body, repeated URL at end of long post: Thrustuline Boost by janicichard on askubuntu.com
> Would not be caught as a post, title or username.
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, bad pattern in URL body, blacklisted website in body, link at end of body, +1 more: Erx pro reviews by freninerei on meta.SE (@iBug)
> Bad keyword in body, bad keyword in title, bad keyword in username ---------- Title - Position 1-10: testo-rev Body - Position 1-10: testo-rev Username - Position 1-10: testo-rev
[ 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, +1 more: strongmuscleshop.com/erx-pro/ by marjorielewis on askubuntu.com
One of you guys will know better than I what to do with this: It looks like a stackoverflow hijack, or at the very least spam: https://stackoverflow.com/cv/things-make-fourth-dimension-mathematicians-pdf-374535639-audiobook
@JarkoDubbeldam np. I seem to also recall some mention of moderators and destroying accounts, or not being able to destroy accounts because the user has a Developer Story (which could convert to a CV).
Moderators can now destroy users with dev stories.
For some users, the Community Team will need to verify - this is now (Jan 16, 2017) automated, so just delete/destroy as normal.
@AJ 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.
@Makyen @JarkoDubbeldam @micsthepick There probably should be a meta, so people can find directions as to what they should do. But, the result of the meta will likely be: pick a post of your own and raise a custom flag with as much detail as you can. I've gone ahead an raised a flag.
@CalvT븃 Phantom 3 standard is good. Battery is variable. If you fly it hard, the battery lasts only about 20 minutes. If it sat in the air or flying slowly it does seem to last all right.
The video it produces is next level. Mine starts beeping to land at 30% but won't force the landing until 10% (at which point you're starting to get concerned anyway).
I don't really fly it at range either because there arent' that many places to do it here..
@micsthepick cc @Undo As for setting up Smokey, I don't think we're in need of any more "official" instances for now, but it's good to know that you're available if we need more at some point.
[ SmokeDetector | MS ] Bad NS for domain in body, bad keyword in body, blacklisted website in body, link at end of body, link following arrow in body, +3 more: how Bellavel work on skin? by user781849 on askubuntu.com
Conflicting feedback across revisions: current, #1
Is the review queue for my query implemented yet? If so where can I find it and do I need permissions to even see it? I only see "Placeholder"(no permission) and "MS Users" in the datasources
Moderators can now destroy users with dev stories.
For some users, the Community Team will need to verify - this is now (Jan 16, 2017) automated, so just delete/destroy as normal.
