# Chat auth token annoying, constant refreshing **URL:** \ **Category:** Chat and IRC\ **Created:** [September 8, 2018, 7:35am UTC](https://staging-discuss.dev.twitch.com/t/chat-auth-token-annoying-constant-refreshing/17592 "2018-09-08T07:35:48Z")\ **Posts on this page:** 1\ **Showing post:** 24
**Author:** ![Dist](https://d1d6mrmdu7ztse.cloudfront.net/user_avatar/staging-discuss.dev.twitch.com/dist/32/7192_2.png) [@Dist](https://staging-discuss.dev.twitch.com/u/Dist)\ **Post date:** [September 15, 2018, 10:20pm UTC](https://staging-discuss.dev.twitch.com/t/chat-auth-token-annoying-constant-refreshing/17592/24 "2018-09-15T22:20:08Z")
> [@BarryCarlyon](#): > > And sadly, you need to email twitch if you want to use chat\_login on new apps. So… True, but then I saw this this post in another thread that indicates there may be new scopes coming for chat that don’t have the same requirements to email Twitch to allow their use: > [@The scope you are requesting is currently unavailable](https://staging-discuss.dev.twitch.com/t/the-scope-you-are-requesting-is-currently-unavailable/17038/12): > > You could try the new chat:read, chat:edit, and channel:moderate scopes since it looks like those don’t need to be whitelisted. They were recently introduced after chat\_login started being abused but have not been added to the documentation yet. But yeah, there are pros/cons to different implementations. Some will require the dev to change the way they do things. It sort of reminds me of when Twitch started making ID’s as important as they were. Most devs saw it as an indication of the (then not announced) username changes and made changes they needed, where as others who didn’t like changing from using usernames as reliable key kicked up a fuss. --- _[View the full topic](https://staging-discuss.dev.twitch.com/t/chat-auth-token-annoying-constant-refreshing/17592)._