The site js is also exposing it through the clearchat event. Please note that CLEARCHAT is seen by all clients, so the timeout reasons are not private, and any client can technically see them. There hasn’t been any front-end work by us to support this yet.
Low risk for change:
While I don’t see any reason we would change the sending portion, if we alter the /timeout formatn, we’ll post here with any updates you’d need to make to your application.
We’re looking for your feedback, and interested in how you would use this feature.
Are you going to switch from ban_reason to ban-reason 2 months down the line again like you did with display_name and display-name (and all others with an underscore in them)?
Conversely, I’m not really interested in potentially sparking discussions about rules. I prefer to timeout/ban, and try to move on instead of talking about it. If the person that was banned wants to talk about it privately, that’s fine.
Ideally, this feature could be configured to be public/private on a per-something basis. (Channel? User? Not sure). I’m not going to hold my breath though
Will be migrating to “ban-reason” and “ban-duration” shortly. Sorry, blanked on that
For our v1, we are attaching it to CLEARCHAT, which is publicly accessible, but not exposed in our vanilla UI anywhere (extensions can use it however they feel best).
It’s unclear if exposing it to all users that want it is the best course of action, but we will start with that.
Whispers were not meant for bots to use for private notices from chat, which is why they are a separate UI. Nobody here is saying that ban reasons are being shown to anyone but the target user in the chat UI. The warning from Aaron merely stated that the reason is not private over the IRC chat connection, which in my opinion is fine. This is the lowest-hanging fruit for (in my opinion) a much needed feature.
I said nothing about bots, I was talking about myself for once.
Let’s not pretend the messages will be kept out of the chat UI. I have a feeling that one of those 3rd party browser extensions (cough) will be adding the ban reasons to the chat UI before too long. Doesn’t matter if Twitch does it officially, that information is exposed to the chat client; it’s not private over any connection.
General chat users would want to see any tid bit when it comes to timeouts/bans, but I believe broadcasters specifically would appreciate the information of who performs timeouts real time. My main broadcaster asks that frequently.
I’m not sure what sort of info should be available to normal chat users, but I think allowing mods/broadcasters to see the reason (and ideally the mod who issued the command too) would be very helpful to me as then it would be simple to log all bans/timeouts along with mod who issued it and reason which would make unban requests a lot simpler and allow broadcasters to monitor what mods have been doing.
