You may have read the previous post about Twitch App Access Tokens doing more, and my sadness about Send Chat Announcement not being supported, well yesterday that was rolled out!
But Wait, theres MORE
Yes, there is more to the MORE!
Send Chat Announcement includes the same control/ability that Send Chat Message has, the ability to control if that Announcement goes to all Channels if the channel is in shared chat mode, with the default being true/send only to home channel.
So broadly this means you can run a Twitch chat bot off JUST the App Access token, as most functions a chat bot will do day to day in the primary function thread can use the Token.
Which has the added benefit of not having to juggle tokens, user refresh tokens, saving those, as to get a new App Access Token, it’s just load ClientID and Secret from env and go get a new token! And of course App Access Tokens has a longer life time of around 60 days or so, which means less refresh operations overall!
To also note there are no additional permission/scope changes here! You should be all good to go if already using conduits and were user token-ing to send announcements.
So What Else?
The Change Log offered the following:
channel.chat.notificationnow emits Watch Streak events! No longer will a bot need to listen to IRC for this single event (oooooh waitfirst-msgmaybe that soon…), also payloads for announcements updated in line with the Send Chat Announcement change, notably as it’s not a breaking change it’s added to V1,channel.bits.usehas been updated to support “Custom Power-ups” whatever those are…- AND FINALLY: Theres a RSS Feed for the change log now!
Help?
If you need further help please join as over on the Twitch Dev Discord or Support Forums! And for anything Feature Request – Uservoice!