Hey @geardrops! Thanks for responding. Hope things are going well on your end since we chatted at TwitchCon.
The challenge there is a developer doubles their API calls if they need to update a user’s follower count to display it or perform some logic based on the follower count. At scale (and/or potentially if you need to do this multiple times a day), this becomes an issue in a variety of scenarios (especially now that measured rate limits are being put into place).
I’d love to know if you see this changing in the future at all, or if we should plan on this way for the longterm. @BarryCarlyon brings up the key point: is this an internal refactor away from appearing again, or is this low on the priority list?
I want to say that on our team, we all appreciate all your hard work @geardrops. We are all working hard to get moved over to Helix but several things like this really make this shift arduous, time-consuming, and ultimately expensive for our businesses (as the shift competes with our time spent on new features, fixing other bugs, etc.)
Really appreciate your information and/or help to understand more here if you can.
Thanks,
Michael