Announcing APIs and EventSub for Polls and Predictions

[Louis6321]

@Dist

Some channels have dozens of moderators, especially larger channels with more organised moderation policies/teams (although these channels are likely to already have dedicated moderator tools/dashboards like those which Barry has described).

I am aware. I’m a mod/senior mod/head mod for a number of them. Chatty is the most-used dedicated moderator tool that is used by human mods for channels of that size. Moderating using native chat or the official mod view page is too slow/inefficient for channels of that size. This means to run predictions/polls we have to have a page open specifically for that, which is not efficient at all. It should be possible for mods to control them over the API and Twitch should have a proper permissions structure within the broadcaster’s roles dashboard to allow mods to do that if there is a genuine concern about abuse… which I understand, I get it… some idiots out there will abuse it or get their accounts compromised… but that’s not a reason to limit the access for everyone. Improve the logging to show which mod performed the action and setup a proper permissions structure. (I know it’s off-topic but a head mod role is long overdue!)

@Dist

If you’re insistent on using Chatty and refusing to use any other service then you’re obviously going to be limited by what Chatty offer.

It’s not a question of what Chatty offers, it’s a question of what Twitch offers in their API.

@Dist

Chatty is primarily a chat client, and is not designed to be a feature rich moderation tool.

I don’t agree with this statement.

@Dist

If you are willing use other 3rd party tools but still wish your mods to interact through Chatty itself then you could create a bot that the broadcaster grants permission to, and then the mods interact with that bot through Chatty which will perform the API requests. Or simply use a dashboard style approach that many channels/apps already do, like Barry has suggested.

Why? That’s just not efficient. Why not open the API up and address the concerns of abuse by implementing (among other possible things) a proper permissions structure?