[ SmokeDetector | MS ] Bad keyword in body, blacklisted website in body, link at end of body, link following arrow in body, pattern-matching website in body, +1 more (490): What Is BioVirexagen? by rickerson cater on askubuntu.com
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, blacklisted website in body, link at end of body, potentially bad ns for domain in body, +1 more (394): The Velofel New Zealand Mystery by user1015037 on askubuntu.com
[ SmokeDetector | MS ] Blacklisted website in answer, link at end of answer, potentially bad asn for hostname in answer (154): Spin statistics by white spider on physics.SE
@tripleee That pattern looks like it's already caught by Blacklisted website in body and Blacklisted website in answer; append -force if you really want to do that.
@treyBake To avoid SmokeDetector reporting posts too slowly, you can report at most 5 posts at a time. This is to avoid SmokeDetector's chat messages getting rate-limited too much, which would slow down reports.
Oh wow, didn't see that. Only checked their GitHub. I had mod flagged because of the quick question-answer posting, all 1-2 minutes from each other and posted as if answering from another account
@Das_Geek FYI on that Kedro question, we had another user from that company come in and spam a bunch of links and LQP before. I don't think the docs are spam themselves
^ yee tbf, that other guy didn't post it in such a spam-y way and I reckon an edit would have made it viable, but think he panicked and deleted every question and answer relating to it
@treyBake FYI: the comment/report reason at the end of a !!/report command must be enclosed in double-quotes. As written, SD parsed every word of this as something you wanted to report, which is why it said you couldn't report more than five posts at a time.
@treyBake You can do so, but it's significantly discouraged. We generally want the feedback to be from other people. It's not as critical now that we require two feedbacks per report, but it's still not something we want to see.
@Machavity 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.
