Is there a command normal privileged users can run if it breaks (like restarting the normal SD instance), or was this something only an admin could fix?
@RyanM I believe it was recoverable from chat, but I'm not certain of that. However, the steps which would have been needed, in this specific case, are probably not peoples go-to solution.
@RyanM Anyone with the "Smoke Detector Runner" role on MS should be privileged to issue commands in this room, which is where that instance is listening for commands. However, there are only a limited number of commands which should be run.
The commands which do a pull and hard sync would rely on the state of the master and deploy branches in my GitHub fork of the SD repo being that they are set to the head of the MS branch, which may not be the case (and was not when this problem happened). However, a !!/master command may have worked (I'd have to check the code). I have reset the master and deploy branches in my repo to the correct location for the MS instance.
Unfortunately the Check Flag Conditions requires you to enable whatever you have set (even if it won't pass) for the checker to produce any result, otherwise it's all zeros. --- The 'timeout' seems rather short, certainly less than it was previously, resulting in four messages; whereas previously I've only seen one (and had sufficient time to tweak / check) without triggering another warning.
[ SmokeDetector | MS ] Url in title, bad keyword in body, body starts with title and ends in url, potentially bad asn for hostname in body, potentially bad asn for hostname in title (290): rapiketoburn.com/testoryl/ by CharleRodri on apple.SE
@RyanM 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.
Recently a moderator deleted my answer with 37 upvotes and it says:
This answer was marked as spam or rude or abusive and is therefore not shown - you can see the revision history for details.
Also, I should mention that recently I added a new section to the answer containing a link to my repos...
[ SmokeDetector | MS ] Bad ip for hostname in body, blacklisted username, blacklisted website in body, potentially bad keyword in body, potentially bad keyword in title, +1 more (362): Exchange EDB to PST Using EdbMails by Linden Goorge on serverfault.com
[ SmokeDetector | MS ] Bad keyword in body, potentially bad asn for hostname in body, potentially bad ip for hostname in body, potentially bad ns for domain in body, potentially bad keyword in body, +1 more (100): Malaysia Visa - IVC Services by gil singh on crafts.SE
[ SmokeDetector | MS ] Bad ip for hostname in body, bad keyword in body, bad keyword in title, bad keyword in username, pattern-matching product name in body, +2 more (577): What is Divine Ease CBD Oil? by DivineEaseCBDOil on mathoverflow.net
we generally tolerate but don't particularly look for rude/abusive
i.e. if Smokey flags something which isn't spam but which is red-flaggable that's not a bug, but we don't particularly want to stretch our efforts to cover more of that ground
@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.
[ SmokeDetector | MS ] Bad keyword in answer, blacklisted website in answer, link at beginning of answer, potentially bad ns for domain in answer, potentially bad keyword in answer (215): Forest characterization by mianlaanti on cs.SE
Just come across this answer stackoverflow.com/a/64282476. It's the only post by this user on SO, but they have a couple of dodgy posts on Magento that look like they're obviously spam
Recently a moderator deleted my answer with 37 upvotes and it says:
This answer was marked as spam or rude or abusive and is therefore not shown - you can see the revision history for details.
Also, I should mention that recently I added a new section to the answer containing a link to my repos...
