The problem isn’t really OAuth, its the complexity that comes with managing multiple user tokens, parititoning your data per server rather than globally (which for polling a single user token, or using eventsub, is desirable in order to de-dup streamers) and monitoring such a system that has a new host of problems (how do we handle the user revoking access, how do we handle the user being banned, how do we handle multiple bots using that same token and hitting ratelimits (is this a case? not sure)) while still being able to cache streamers across multiple user tokens. This is much more complex than an EventSub setup, or even a single-token polling system would be
That does nothing to reduce the overall requests needed and we would still be wasting time on offline streamers.
Fair point, taken. Let’s switch gears a little bit then, would it be possible for Twitch to provide a feed of users that recently came online through the API? In this way, you guys could keep the heavy caching and we would benefit from not having to visit offline streamers. There are a host of solutions here that could benefit both sides.