Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Check on behavior if PubSub is shut down (Do we get errors? Do reward messages come through? etc.) #5928

Open
Tracked by #5908
pajlada opened this issue Feb 7, 2025 · 3 comments

Comments

@pajlada
Copy link
Member

pajlada commented Feb 7, 2025

(felanbird): see https://discuss.dev.twitch.com/t/legacy-pubsub-deprecation-and-shutdown-timeline/58043#p-119521-pubsub-shutdown-timeline-3 for the brownout periods.

@Felanbird
Copy link
Collaborator

Felanbird commented Feb 10, 2025

assuming they didn't forget to brownout:

images

image
image

@Wissididom
Copy link
Contributor

Wissididom commented Feb 10, 2025

assuming they didn't forget to brownout:

Maybe related to the snippet Existing connections may not disconnect during the shorter windows, but will be closed during the 24-hour and 48-hour periods. Connections will also be closed on the final shutdown date. from the linked brownout times article in twitch's forums.

@Felanbird
Copy link
Collaborator

Maybe related to the snippet Existing connections may not disconnect during the shorter windows, but will be closed during the 24-hour and 48-hour periods. Connections will also be closed on the final shutdown date. from the linked brownout times article in twitch's forums.

Yeah does seem to be the case, a second client has neither feature, mod channels do fall back to the non-pubsub message w/o moderator name.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants