Should the client reconnect when the auth token is updated?

[pajlada]

No description provided.

[iProdigy]

answer: only if the account switched or new scopes were added (that allow for creating a missing subscription type)

even if token expires, the websocket is not killed & refreshing the token doesn't kill the websocket either - token only has to be valid at the time the helix calls are made that establish the eventsub subscriptions

if we're concerned about the edge case where user revokes the auth connection & reauths, we would already know the subscriptions were dead via https://dev.twitch.tv/docs/eventsub/handling-websocket-events/#revocation-message

[pajlada]

Given the lifetime of a client, I don't think we need to handle this then.

Do you think there's a scenario where we should try to handle the revocation message?
I see 3 revocations in the docs:

• One of the users that's part of the subscription no longer exists (e.g. if channel we were joined to is banned)
  I don't think we want the messages anymore anyway then
• Subscription no longer supported
  Nothing we can do to recover in this case
• The user authorization is revoked
  If the user changes their password or disconnects from the Chatterino client ID, do we need to do anything?

[iProdigy]

i haven't closely looked at the c2 impl, but on revocation, we should free any internal state/memory associated with the sub, but no need to make any helix requests to clean up the sub

if post cleanup there's zero topics subscribed, theoretically we could disconnect the socket - but ppl may later add other channels so no need

on version_removed, we could try to resub with an incremented version number since the updated payload is prolly similar enough to still work, but not necessary

in short: yeah we're fine to just ignore them for now

tho we could use auth revoked on whispers topic to tell the user to reauth