Twitch: "Please send us API feedback!" Me: "You need an IsStreamerLive endpoint that sites can embed without a client ID." Twitch: "Thanks for the feedback. We've gone ahead and done the opposite of that. You now need both the client ID _and_ an OAuth token!" Me: "I give up."
-
Show this thread
-
Replying to @cmuratori
The primary reason web APIs require auth even for public info is to allow them to time out/blacklist bad actors who don’t respect request limits and just hammer the servers with a billion requests/sec (whether malicious or a bug). Having a clientId means they know who to notify.
2 replies 0 retweets 0 likes -
Replying to @dbechrd @cmuratori
And you think Casey doesn’t know that? Endpoints that are so simple like checking the live status should have no privileges because of how basic they are. 10/100 Queries per second by IP is pretty common as a lockout to avoid abuse even if you have an auth token.
1 reply 0 retweets 1 like -
Replying to @downthecrop @dbechrd
Yes, of course Casey doesn't know that. He's stupid! It's not like he would have checked first to make sure this information is provided _unmasked and easy to crawl_ right on the publicly available Twitch page for each streamer anyway, as a single tag with the word "LIVE" in it.
1 reply 0 retweets 3 likes -
So it can't be that Casey looked at it carefully, determined that they provide this information without any credentialing in an easy-to-crawl-by-bots format, and thus determined that providing it via the API would actually just save them bandwidth. That couldn't be.
2 replies 0 retweets 3 likes -
What's much more likely is Casey is just one of those game programmers who doesn't understand "the web", despite of course making all the websites for his company, and running a server which properly masks the client ID through a proxy, unlike most sites which just leak it.
1 reply 0 retweets 3 likes
Because that would mean Casey knows a lot about web architecture, security, encryption, APIs, efficiency, reliability, and up time, which of course would mean we'd have to take him seriously when he pointed out that our web architecture was a gigantic pile of shit.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.