@double-beep That pattern looks like it's already caught by Bad phone number in answer and Bad phone number in body; append -force if you really want to do that.
### IndexError on teward/Hypergate at 2019-08-21T12:12:03Z: list index out of range File "/home/smokey/SmokeDetector/chatcommunicate.py", line 452, in __call__ result = self.__func__(*processed_args, alias_used=alias_used) File "/home/smokey/SmokeDetector/chatcommands.py", line 354, in watch msg, force=alias_used.split("-")[-1] == "force") File "/home/smokey/SmokeDetector/chatcommands.py", line 251, in do_blacklist pattern = rebuild_str(msg.content_source.split(" ", 1)[1])
### ErrorReturnCode_1 on teward/Hypergate at 2019-08-21T10:55:41Z:
@Olivia I don't know about "supposed to", but the reviewer role isn't auto-granted with the current code. From what I've seen, moderators aren't programmatically given roles on MS. When I've seen a moderator sign up on MS, I've manually given them the Flagger and Reviewer roles, because, as we say wrt. SD privileges, "we assume that moderators are, on the whole, pretty good at moderation." So, I've added the Reviewer role for Martijn.
@Olivia SD privileges gives you the ability to give feedback and commands through SmokeDetector, and is granted automatically to moderators. The Reviewer role gives permission to give feedback and flag through the MS API and on metasmoke itself (such actions are significantly less visible). I haven't looked at exactly which things are gated by the Reviewer role, but my experience is that if the user wants to do write operations via the MS API, then that role is needed.
@Makyen 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.
@Makyen That pattern looks like it's already caught by Mostly punctuation marks in answer, Potentially bad keyword in answer, Potentially bad keyword in body, and Mostly punctuation marks in body; append -force if you really want to do that.
@double-beep 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.
@Stormblessed That appears to have been applied to a few/several SE sites. It's not wrong, but the "notspam" tag, which it also has, would be more appropriate.
"Smokie seems to work great, could he (she?) be integrated into the site (maybe as a review queue)?" -- "Half of the messages in our chat room are 'sdfpu' etc., which turns away newcomers. Should the bot move to a different room?" -- "A moderator suspended Smokie for two years, why?" — balphaJan 7 '16 at 6:01
