Currently we store SHA256 hashes of user IDs, and then compare those to the User IDs from the EndPoint and perform the following…
- if the user in our database is following us, but the Twitch API says they are not, we toggle their follow status in our database to false
- if the user in our database is not following us, but the API says they are, we toggle it to true
- if the user is not yet in our database, we create a reference to that user
I currently throttle the requests as to not go over any potential limits, but that also makes the overall time for the request process just about 2 minutes at this point (the throttle is set to a random time from 1.5 to 3.5 seconds between each request, since the bot may also be doing other API requests at the time and this helps to make sure that pulling the follower list has very little chance of hitting the limits)
It IS a very specific use case, and I fully understand that its something that a massive number of people may not get use out of. Its also one of those things where there could be larger use cases for it that are not yet evident due to the fact that it doesnt exist currently.
To me, it just seems like I am pulling a ton of redundant or useless information when all I really care about and/or need is a simple “who is following, true or false” results rather than, “who is following and what is their user icon, username, display name, full bio, etc”. There ARE times when I need that information, but the majority of the time, when it comes to follower status, a simple yes or no is all that is needed