Currently, in order to get the full list of Followers for things like special features for our users (our channel, RobAndDan, uses a custom chat widget that displays a logo if the user follows us), we need to pull down multiple pages via the Followers Endpoint using the Cursor value.
Having 8400+ followers at this point, this is around 84 pages of full, public information for each follower. There are a few ways this can be optimized on our side of things, for example, we currently only pull down a new list every 6-12 hours, and never when we are live with the channel.
I would like to suggest a more optimized method be added to the Follower Endpoint where we can request an altered version of the follower list.
Rather than receive all public user information for 100 users at a time, could we have a method for receiving JUST the UserIDs, in a simple JSON array, in the order of Most Recent Follower to Oldest Follower. This Endpoint method could still be paginated via a cursor, but since it would only contain ID numbers, far more IDs could be packed into a single response.
As a quick example of the size of the response data, gathering the first page of our followers via the Endpoint, the total number of characters (including all JSON data structure characters) in the response was 29670 total characters. With an ID number being 8 total character (minus 100 characters for any other required data and structural character), around 3600 +/- User IDs could be passed on their own per page. If we had access to an Endpoint method like this, it could reduce our own usage of the Endpoint from 84 requests per full refresh (again, every 6-12 hours) to just around 3 requests per full refresh.
Obviously a counter argument to this could be that just getting any information for each follower is resource intensive, regardless of the amount of actual information gathered, so my idea could be just impractical. And since I dont know the specifics of the Twitch API back end systems, i dont know one way or another. Just an idea though