@Normal Perhaps test versions, like @hichris123's, could have a DEBUG flag, that causes them to respond to different commands. EG: tsd k ... or t!!/report ..., etc.
I see: two bots are not at sync in terms of API queue, so hichris-bot read the post earlier, and then hichris-human edited it, leaving Smokey with nothing.
Whipped up a *Monkey user script that adds a volume slider to our @StackOverflow and @StackExchange chat rooms: https://greasyfork.org/en/scripts/16359-stack-chat-volume-control
What do y'all think about creating another room for smokey on C.MSE, so it can still run in Tavern but be muted by users who don't want to hear the stream of crap, and replies can be in the new room?
@bjb568 Weren't JasonC, Infinite Recursion and balpha working on this? In all honesty, it sounds like something that the Tavern needs to discuss as a room, especially since the room owners seem to be split on the next course of action
If you get the room to have the discussion, it probably needs to stay active for a bit so that all sides can have a say instead of calling a vote (or whatever the proposed method of determining the outcome) and being done with it in a few hours
@Andy No consensus. Jason proposed what I said, Inf says smokey could be evicted, can't find alpha's response. But it seems like Jason's proposal is the best of both worlds, since it won't disrupt existing users.
But it can still do that without replies, letting the annoyed users mute it. It'd still accomplish its goal of interjecting to get flags, but it won't annoy everybody.
Smokey posts reports to other rooms. Do any, other than here, get all reports or are they limited to only the posts associated with the room's parent site?
Possible idea to reduce command spam: have each report generate two links - correct/incorrect. Users click them to report tp or fp. I'd also make the links valid for only X minutes so that someone going through the transcript can't spam click.
Downside...Users can click the link more than once
Mitigation: only accept X reports for a post
Just throwing out an idea. I'm not sure it's a great one yet though
Another confirmation action could be star-unstar (two clicks). But less convenient (especially on mobile), and not easy to think of "false" version of it.
@Andy Downside: any user can click, not only privileged ones.
I've tossed that idea around too. We could do it, but we'd have to wait for the metasmoke report to finish (and give us an id) before sending the message
It'd probably add a negligible amount of time, but we'd also have to deal with what happens when metasmoke is down (instead of just letting it silently fail like we do now)
