Differences in the v3/v5 data outputs so developers need to be aware of that when updating old code.
So a forced upgrade from v3 to v5 calls wasn’t forced
v3 tended to call and return using usernames
v5 is call and return by user ID
v3 code calling the API would then fail as the call wouldn’t work as the data returned (if any) doesn’t match the expected output. So safer to HTTP error rather than return the v5 response to a v3 call
Use helix where possible, that doesn’t “abuse” the accept header.
Not sure how Google’s API limits relate to Twitch suxx-ing