New RealPlayer to rip YouTube video streams
And more importantly (for adbeast possibly) it will support
QuickTime. Depending upon how they implement the interface and
the uptake on browser plugins this could have a major impact on
the internet video space.
Real Networks announced today that it will be launching
a new version of its dying video player this June. Unlike previous
versions of the player, the new version will support file types
other than just Real files, including Windows Media, Flash, and
QuickTime. The new version of the player will also allow users to
download video streams onto their computers. This means that users
will be able to save their own copies of videos from sites like
YouTube, MySpace, Soapbox, Revver, and more with a single click
instead of relying on more convoluted methods.
New RealPlayer to rip YouTube video streams
Frameworkers
Frameworkers
Originally uploaded by
adactio. This came
from the recent Web 2.0 conference. Unfortunately the prototype
library is missing from list of panelists. However, if it was there
it would probably sit somewhere between YUI and Dojo and between
websites and applications (in my opinion).
Risk Analysis: The Longevity of Mashup APIs
Everyone knows that
saying "you get what you pay for". So when we start using any one
of the hundreds of web based APIs for free what sort of assumptions
can we make about it? For instance:
- How long will it be around?
- If it changes how will I be notified so I can change and test
the code in my application?
- What if my application receives so many hits that it overwhelms
the server I am mashing up to?
- Can I realistically use this API (which will solve all my
problems and cost me nothing) in my application?
While I have played with a few of the available APIs I find it very
difficult to consider using them in any of my applications. And
this includes applications I am architecting for my employer as
well as some of my smaller, non-profit community applications I am
building in my spare time. My concern is that someone offering web
services, data and an API at no cost has no real obligation to me
as the consumer of that information. While it is in the best
interest of some of the larger players to maintain their API (think
Amazon, eBay, etc) the smaller organizations could decide to take
down their provision at any time if they feel they are not getting
anything back from it or perhaps their limited bandwidth is being
exceeded. At the minimum this could result in a severe disruption
in service for my users. For that matter, how can I make any
statement of service or availability to my users if I am depending
upon external services themselves not providing this statement.
Perhaps we need to see an emergence of a standard SLA that gets
published much the same way a privacy statement is. If the provider
of the API communicates their intended service level then consumers
of that API can make a more informed decision. Unfortunately, I
think the type of information that would need to be disclosed would
often be considered confidential and proprietary.
Web 3.0: When Web Sites Become Web Services
This article talks about
the continued growth of web APIs and how they are critical to the
next evolution of the www.
Link to Web 3.0: When Web Sites Become Web Services
O'Reilly -- What Is Web 2.0
Tim O'Reilly (of O'Reilly
books) presents a comprehensive definition of Web 2.0. This would
be a great companion article to the What Is Web 2.0 video that has
been floating around on YouTube recently.
O'Reilly -- What Is Web 2.0