This comment betrays your ignorance about the whole situation. Like almost every other game developer out there, Steam does the updating for us. And even for our non-Steam applications, we rely on filestores (Amazon S3, etc.) for updates, which can’t proxy HTTP get requests.
Of course I can fire up an EC2 node or whatever just to gather and stream the twitch data, but that’s a stupid amount of overkill for what we want to do (just displaying publicly available information from Twitch).
The suggestion that offended me deeply was when you said to “move off Air”. If your first suggestion to the lead engineer behind a successful application is that they change their entire client-side technology stack (including the game engine itself), of an app that’s been running just fine for years, then it’s hard for me to think much of your “experience and knowledge”.
People use all kinds of different technology to make games. Twitch should be aiming to create APIs that make access to them as easy as possible for as many game creators as possible. Instead, they’re needlessly imposing burdens that make it more difficult for some developers. I assume this is something they would want to hear about (and rectify).