[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, link at end of body, link following arrow in body, pattern-matching website in body: Allure Skin Care by Ethel Jhon on drupal.stackexchange.com
@hichris123 More or less 5 clicks + typing the search + waiting. As for the dev time, no idea. Since it's something that I and others do quite often, I believe it can be worth it as long as the dev time isn't too high. Art noted that we could reuse parts of the API for that so hopefully it would be somewhat simple.
@hichris123 Ideally it could just fetch the results of the already existant metasmoke search page by searching for the word you give to the command in "body" and then return aggregated feedback/post from that
should be easy but then again I'm not a python guy
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, link at end of body, link following arrow in body, pattern-matching website in body: Saunas - Skin Care Guidelines? by euereuf on askubuntu.com (@ThomasWard)
[ SmokeDetector | MS ] Bad keyword in title, bad keyword with email in body, blacklisted website in body, repeated URL at end of long post: OBIEE Online Training by deekishith12 on stackoverflow.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: ingredients in their Eye Serum by eosiartha on askubuntu.com (@ThomasWard)
hmmm, FDSC seems to have trouble connecting to the Metasmoke back-end for feedback? Could be my network though (slightly shaky 3G, and Chrome seems to be overloaded with too many open tabs)
"We are not concerned with spam users unless they start posting things on our site. The profiles simply existing does no harm as the links in them do not get rendered without having 10 reputation, and we simply do not have the time to go through mass deleting spam profiles that achieve nothing on our site."
@ArtOfCode Do we have a precise guideline for when to BL websites? I've been going by min. 2 TPU reports and currently uncaught by bad keyword / pattern matching website / blacklisted website filters. Is that OK? cc @Undo
so if you find a spammer domain which has the same IP and same whois as a blacklisted one, that should be a slam dunk with no further evidence required
we don't currently have the tooling to easily diagnose that, though
[ SmokeDetector | MS ] Blacklisted website in body, pattern-matching website in body, repeated URL at end of long post: the decreasing degree? by mislashelly on graphicdesign.stackexchange.com
@hichris123 that's basically every program, every feature, ever. Make things because we're lazy, because the time they'll save us in the future is greater than the dev time.
@hichris123 might be a little low, considering we've never had 100 people in this room :P I get the point, but I also figure that if it's going to help at least some (as in more than 1 or 2) of the people here, then it's worth it.
@ArtOfCode But when it legitimately takes 10 seconds to search? I have little sympathy for that. Nor do I want the extra complexity just because of laziness.
(also, blacklisting should be something that you don't just rely on metasmoke for so...)
[ SmokeDetector | MS ] URL-only title, bad keyword in body, blacklisted website in body, blacklisted website in title, link at end of body, pattern-matching website in body, pattern-matching website in title, repeated URL at end of long post: iqdermaessentials.com/alpha-extreme-plus/ by charlessmith on askubuntu.com (@ThomasWard)
@ArtOfCode Isn't the bug as simple to solve by moving the "\n" to the other side in this line? github.com/Charcoal-SE/SmokeDetector/blob/master/… It makes more sense to solve it this way as the git blame will be more meaningfull, and we can use text editors to edit that file (like github online, or Atom)
Most editors come with the option to automatically add a newline to the end of the file by default, like POSIX says
@tripleee The only usefulness is in those messages not appearing in the transcript, but the transcript of Charcoal already looks funny with all the penis enlargement spam.
As much as it pains me to say this, thats a question. Closable, yes. Downvotable, absolutely. Despicable in its oozing entitlement yes. But neither abusive nor spam.
