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

Move from PubSub to EventSub #634

Open
neeo opened this issue Dec 20, 2024 · 4 comments
Open

Move from PubSub to EventSub #634

neeo opened this issue Dec 20, 2024 · 4 comments

Comments

@neeo
Copy link

neeo commented Dec 20, 2024

Twitch has announced that PubSub WS API will be shut down on April 14, 2025.

I would like to see the app move to the EventSub API to avoid downtime after PubSub termination.

Proposed solution

Rewrite WebSocketsPool to use EventSub API

Alternatives you've considered

No response

Additional context

No response

@mpforce1
Copy link

mpforce1 commented Jan 6, 2025

Hi, it's interesting that they say PubSub is being shutdown (and soon) since the current version of the Twitch web client still uses it. Given that EventSub has apparently had feature parity for about a year, I would have thought the web client would have already moved to the new system by now.

It should be noted that the publicly listed EventSub subscriptions do not cover all of the miner's currently used PubSub topics. In particular, only video-playback-by-id, raid, and predictions-channel-v1 have documented subscriptions. It's likely, as with PubSub, that there are undocumented subscriptions we could use but we'd need more info to be able to use them. I might have missed something here so any corrections would be appreciated.

Also, the EventSub API is intended for 3rd party app integrations. The web client is not a 3rd party app, it is one of Twitch's 1st party apps. I suspect that what's actually going to happen is that 3rd party app auth tokens will have their PubSub permissions revoked. However, this is just speculation, so it's worth checking out how the both the web client and the miner function during the scheduled PubSub phased shutdown, the first window is February 10th.

@mpforce1
Copy link

Following up on this, I had a look at the miner during the shutdown window and didn't notice anything out of the ordinary. I also tried restarting the miner during the window and had no issue connecting to PubSub. I'll check again during the next shutdown window on the 24th.

If anyone noticed anything strange related to PubSub during the window please post here with, if appropriate, the section of logs during the shutdown window and a description of the issue.

@mpforce1
Copy link

Another follow up, no issues on the 24th. I'll check the next window on the 10th and report back.

I have created a discussion (#652) for something that may be relevant to PubSub deprecation. It's not directly related to EventSub so I didn't want to include it here directly. Any further information on this would be greatly appreciated.

@mpforce1
Copy link

Once again I have no issues to report on the 10th. The next window duration is 24h on the 24th/25th, I'll report back on that too.

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

No branches or pull requests

2 participants