When any of my bots start, the first thing it does is ID to username lookups via helix to check if the user changed their name (or the bot did) or not and ensure I connect to the right channel. Do you not do the same? Or even do a token validate/refresh call? (Sure thats not quite helix but still curl/http)
You don’t need a full “helix client” just a curl client for the calls you need.
A “curl client” that does a token maintaince check? And Hopefully does what I do (id to name checks) to check for the destination/target channel names in cases of renames?
First party also calls an API and doesn’t use the TMI socket. This change will bring the “3rd party experience in line with the 1st party expereience” potentitally reduce such a surface. So the exact opposite in my opinion.
It’s still the bots own token for moderation tasks, so if you are maintaining a token for your bot to login wot chat with., you don’t need any more configuration?! Beyond seeding the token with additional scopes when generating brand new token sets.
That I feel was half in jest and even then, wouldn’t replace whatever is used to deliver chat “normally” in my opinion, so would be an option.
Imagine if it supported filtering and you could ask twitch to only send chat messages you are interested in for example.