they both redirect to the same image, some sort of matrix with a bit of advertising ... including an image which confirms that the other account is a sock puppet of theirs
[ SmokeDetector | MS ] Url-only title, bad keyword in body, bad keyword in title, blacklisted website in body, blacklisted website in title, +7 more (793): mumybuzz.com/revive-keto/ by Ahan Golima on askubuntu.com
[ SmokeDetector | MS ] Url-only title, blacklisted website in body, blacklisted website in title, body starts with title and ends in url, link at end of body, +7 more (796): evaherbalist.com/keto-kinetics/ by Gnwzamwp on askubuntu.com
[ SmokeDetector | MS ] Bad keyword in body, blacklisted website in body, body starts with title and ends in url, pattern-matching website in body, potentially bad keyword in body, +1 more (492): Regular use of 4T Plus items along by Tristanchery on stackoverflow.com
tpu- by Tetsuya Yamamoto
[ SmokeDetector | MS ] Bad keyword in body, bad pattern in url body, blacklisted website in body, pattern-matching product name in body, pattern-matching website in body, +1 more (489): If you hate the by Fiwrmail on codereview.SE
[ SmokeDetector | MS ] Url-only title, bad keyword in body, blacklisted website in body, blacklisted website in title, body starts with title and ends in url, +6 more (890): ultrasupplement.com/sugar-balance/ by user890580 on askubuntu.com
@Henders np. Just wanted to make sure you were aware of the issue. SD instances are supposed to "just run" for extended periods. Thus, it's likely the owner isn't checking their instance all that often.
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, bad keyword in username, bad pattern in url body, body starts with title and ends in url, +2 more (676): Propserx reviews by Pro Test 180 on meta.SE
@tripleee 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.
Yeah, SD has been a bit more unstable than normal over the past few/several weeks. On the plus side, there's a command now, !!/pull-sync that will fix-up the master branch.
if we are spending effort on something like that, how about a proxy between MS and Smokey so that we are more resilient against MS outages? then we could store the pickle data in the proxy too
room topic changed to Charcoal HQ: Where diamonds are made, smoke is detected, and we break things by developing on production. 111k true positives and counting. For more information, see charcoal-se.org/about. Handy links: metasmoke.erwaysoftware.com, github.com/Charcoal-SE [dev-on-prod] [panic-driven-development] [plastic-knives] [programmatic-crowbars]
@EriktheOutgolfer 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.
@EriktheOutgolfer 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.
I do QA, so I touch and break all the things. It's just more fun to break them when it's intentional. This one was me not paying attention and letting my test run away from me.
I've also had success using Charcoal Test. It's worked on a couple of occasions when the SD instance was not responding in CHQ and SOCVR. Thus, my impression is that the loss of communication tends to be per room, rather than per Chat server. OTOH, when the Chat servers start going down...
