@tripleee That pattern looks like it's already caught by Potentially bad keyword in body, Pattern-matching website in answer, Potentially bad keyword in answer, and Pattern-matching website in body; append -force if you really want to do that.
@Das_Geek 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.
@Das_Geek Once SD stops listening for commands in here, you have to go to a different room to issue the !!/reboot. I usually go to either Charcoal Test SO or Charcoal Test, but any other room that accepts commands will usually work.
@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.
@SmokeDetector This site explicitly lists Olivia Williams as the contact person for the linked site. Thus, this is spam and contains undisclosed affiliation.
I flagged the first spam comment but I can't flag the second one, the GitHub interface says it won't accept another report from my IP address in a while
@SmokeDetector @Das_Geek @double-beep Is there some undisclosed affiliation, or indication the question OP and answerer are associated? Basically, the answer appears to be exactly what the question is asking for, which would make the answer not spam, unless there's undisclosed affiliation, or some other shenanigans going on.
I was just going through the Low Quality Posts queue and failed a test with the following answer:
Spam/Offensive Answer
Reading the answer and following the link within the answer, it didn't strike me that this was spam or offensive, so, although it was not in any way a brilliant answer, I clic...
@Makyen Nope, that was just me not doing due diligence. I had seen that it was tpu'd, and at first glance it kinda looked spammy, so I cast my vote in the same way. After following the links, I switched over my response to fp
@Das_Geek 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.
Can someone with the "Core" role on MS check their ability to access the "Abuse Reports" page? I'm getting a NoMethodError that's being thrown in the "Reported To" section of the page.
@double-beep If you mean the most recent CI failure on MS' GitHub repository, then that failure is a known intermittent issue with the CI tests where the database disappears. There's been some work at fixing it, but no resolution.
@double-beep It's not, necessarily, as trivial as just setting it back. The place where the version is specified is an automatically generated file, which includes any dependencies. I don't have a development environment, so can't, currently, use the appropriate tool to automatically re-generate the file. Thus, if I change it, I'd just have to hope that there aren't any dependencies which also need to change. I'm thinking about just trying it, but I'm not really a fan of doing that in production.
[ SmokeDetector | MS ] Few unique characters in body, no whitespace in body, potentially bad keyword in body, repeating characters in body (265): Matlab gives no result ✏️ by user3311415 on stackoverflow.com
@EliahKagan If you want to watch just the text that's also the subdomain (and used elsewhere), that's fine. Doing so will catch any new uses of that text. However, usually, we should also watch the entire domain. The reason is that the domain will normally be moved to the blacklisted websites list (when/if it qualifies), whereas just the text for the subdomain is more likely to end up on the bad keywords list.
Having both means that the one which is just the subdomain/identifier text needs be written to exclude matching the domain, so there isn't an eventual double-detection.
@EliahKagan Git operations failed for unspecified reasons.
@EliahKagan 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.
@EliahKagan 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 Thanks. I've replaced the watch with one for the full domain (since I don't think doodlekit.com itself should be watched) and one for the keyword outside that specific domain. This seems better than what I had before, though I'm not sure if I've done it in the best way or not.
### ValueError on iBug/Sandy Shores at 2020-01-02T22:57:28Z: not enough values to unpack (expected 2, got 1) File "/home/smokey/SmokeDetector/chatcommunicate.py", line 453, in __call__ result = self.__func__(*processed_args, alias_used=alias_used) File "/home/smokey/SmokeDetector/chatcommands.py", line 427, in watch msg, force=alias_used.split("-")[-1] == "force") File "/home/smokey/SmokeDetector/chatcommands.py", line 370, in do_blacklist metasmoke_down=metasmoke_down File "/home/smokey/SmokeDetector/gitmanager.py", line 212, in add_to_blacklist
