Thanks for the reply.
That was a typo, sorry about that, the values are still correct in the calculations though.
This adds friction for the user, no bot asks for this, why would the user do it? I also want to remind you that most bots are 1-person endeavours and they can barely keep up with Discord changes, let alone invest the time in a complex system like this. Also, why would it be fine to have more polling capacity but not more eventsub capacity?
I don’t understand how polling massive amounts of data is the intended solution for a simple use case like being notified when a streamer is online. EventSub is the perfect solution for this, neither us nor Twitch waste resources, notifications get sent fast, it’s scalable on both sides and very light on bandwidth.
I understand the need to limit API usage due to abuse and privacy concerns, and I do not want all the EventSub limits to be lifted. But let me illustrate how different interacting with Twitch is from a developers standpoint:
For Twitch, we have to rotate and visit every single streamer, multiple times an hour, wasting resources on streams that are offline, just to get a handful of streamers that came online per rotation. 80k stream fetchs per min, 800 requests per min, we have to keep this constantly throught the day.
On Reddit, We can query their API once every ~3 seconds (20req/m) and keep up with all new posts. We don’t waste time or resources on duplicate posts, we can query their feed with only new posts and their API even allows us to resume from where we left off in case of a problem.
On YouTube, their PubSubHubBub implementation is very similar to EventSub, and has no limits.
On Twitter, we can tail a feed with the usernames we care about and get new tweets from this feed.
These are all services at the scale of Twitch, and they all allow us to tap into their data easily. Why can’t Twitch make this easier for developers?