newVideoPlayer( {"type":"video","player":"http://www.youtube.com/v/mWunH5-ut5U&hl=en&fs=1&fmt=22","customParams":[] ,"width":570,"height":375,"ratio":0.824,"flashData":"","embedName":null,"objectId":null,"noEmbed":false,"source":"youtube","wrap":true,"agegate":false} );
Whoa! My head is spinning after watching this video demo of a TweetDeck beta release which uses Twitters new user stream API. It lets you watch people replying, retweeting or favouriting tweets in real time. Amazing.
There are two ways for a device to access YouTube: either through the regular web interface (i.e. Flash) or for cleaner integration, through its back-end APIs. As of December, Google is shutting off the tap. Update.
Sounds sinister, right? That’s probably because I replaced the word “computers” with “robots”! For effect! But no, still, this is at least interesting: Developers are now reporting that apps are getting rejected, and not by humans.
Netflix will introduce their API to the public tomorrow at the Experience AJAX conference, and according to ReadWriteWeb, it will allow free access to movie data and stats stored on their servers. This doesn’t mean that anyone will be able to write a streaming video app for any random piece of open hardware. However, it does mean that people will be able to will be able to integrate movie info (ratings, related films, etc…) into widgets, like the ones you’d see on Typepad or Facebook. Or more importantly, create apps that allow for queue management (yes, this API is read and write capable).
