Youtube Crossdomain

Months back the youtube widget player I created stopped working. It was quite obvious what happened but I still did some digging just to make sure. Sure enough, youtube implemented a crossdomain policy which basically shut all flash development of widgets and services that used their apis. It was depressing. I put a lot of time into the flv player that played solely youtube content. Sure sure, I was basically ripping their flv content without the “youtube” watermark but that’s another issue for another argument for another day.

But for basic api access I had to build a proxy service to get info from youtube then sends it to my youtube widget. What a pain in the ass, the latency I mean. What’s confusing is that youtube people aren’t stupid. They know about proxies so completely shutting off flash developers, especially when the platform they choose was flash, was IMO rather disturbing outright frustrating. Yeah yeah, I’m not talking about business or the loss of money or whatever. I’m talking just in the developer’s perspective. You want to have developers pushing youtube content and the youtube brand then open your apis like you had intended to everyone.

Leave a Reply