[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, pattern-matching product name in body, pattern-matching product name in title, pattern-matching website in body, +2 more (494): Where To Buy Keto Fit Premium by user10767662 on stackoverflow.com
Recovered from BrokenPipeError: [Errno 32] Broken pipe
@SmokeDetector This has been deleted and the user deleted or destroyed. The tone of this implies that it's a troll, but without context it's hard to actually declare it TP or FP.
@SmokeDetector The actual site that is detected is vbtechsupport.com, not techsupport.com. This is another case of the lack of any delimiter on the blacklisted websites list causing spurious detections.
@SmokeDetector There, a Biology moderator left this comment: "This is the anti-vaccine troll of the biology community. He shows up frequently, the only thing we do is to delete his crap. He always uses a set of the same email adresses so the mods should be able to see the pattern. If there are any further questions, ping me over at TL." – Chris
@SmokeDetector A Biology moderator left this comment: "This is the anti-vaccine troll of the biology community. He shows up frequently, the only thing we do is to delete his crap. He always uses a set of the same email adresses so the mods should be able to see the pattern. If there are any further questions, ping me over at TL." – Chris
@Zoe Where was it plagiarized from? I'm not finding a source. I'm assuming you're talking about this report. Was there another, now deleted, answer on the question? While the currently existing answer begins with the same line, the rest doesn't match any revision of that other answer.
@Rob It's a question with the same title/content that was cross-posted on two different sites.
@Makyen That pattern looks like it's already caught by Pattern-matching website in answer and Pattern-matching website in body; append -force if you really want to do that.
It would be great if two instances were running and the failover was silent - then when one kicks it could SocketScience it's time of death and the failover could pick it up seemlessly.
@Makyen - I noticed that SD only catches old stuff if it's bumped somehow. Would it be an idea if someone ran their own SD against the Stack Exchange Data Dump and if finding something actionable attempt to double-check that the post still exists and then process it as though it came from the feed. -- There was that 8 year old question several hours ago and it only came to everyone's attention because it received a new answer (which resulted in the
deletion of the answer and the question being put on hold as OT.
@Rob It's certainly possible. IIRC, it's been kicked around a bit. More effective would be to download an SE database backup and run directly off of that, which wouldn't have the limits of max API requests. Given that we really don't have the person-power to handle classifying all of the non-autoflagable posts, if done, it might be a good idea to limit the reports to only those that would be autoflagged. Side consequence: That would, of course significantly skew our statistics.
Re the stats. Could a new user be made to submit the reports and then the results of their efforts subtracted from the stats, leaving their actions invisible ?
