Slashdot Mirror
No HTML5 Hulu Anytime Soon
99BottlesOfBeerInMyF writes "The Hulu website briefly commented the other day about why they would not be implementing HTML5 video for their service: 'We continue to monitor developments on HTML5, but as of now it doesn't yet meet all of our customers' needs. Our player doesn't just simply stream video, it must also secure the content, handle reporting for our advertisers, render the video using a high performance codec to ensure premium visual quality, communicate back with the server to determine how long to buffer and what bitrate to stream, and dozens of other things that aren't necessarily visible to the end user.' They plan to release a dedicated application for the iPad and iPhone instead, likely a paid subscription service. Perhaps this is a good sign for Web-based television, as it will move more users away from the single, locked down channel from the networks and to more diverse options less interested in extracting subscription fees (like YouTube)."
HTML5 advocates should really give an option for content security aka DRM, that is how real World works for now...
Even if they wanted to, how would you propose that they do that? It would be trivial enough to add a "donotallowworthlesspirateusertocopyonpainofdeath" option to the video tag; but that would only be as useful as the various browser's enforcement of it. You might get some vendors on board(though that would hardly be a given. The FOSS guys hate DRM on principle, and the corporates already have their own DRM systems, and it isn't clear that they want the competition); but you would have absolutely no way to go after the ones that refused, or the fly-by-night redistribution of copies of firefox compiled with the -ignore_DRM_flags option set.
If you observe real world DRM systems, they are all either single-party(WMDRM, Fairplay, etc.) or multi-vendor standards controlled by IP cartels bristling with patents that you must license in order to implement whatever the attached spec is(CSS, HDCP, AACS). HTML5 is in neither position. There would be absolutely no way to stop the proliferation of implementations compliant enough to receive the video; but noncompliant with respect to denying it to the user(good luck, for instance, having your site distinguish between a good-faith/best-effort DRM implementing webkit build, and a slightly tweaked build that reports exactly the same ID strings but "accidentally" lets the precious premium content sit in a snoopable memory location...
On closed platforms, where undesired binaries can simply be excluded, it'd be trivial enough; but there would be Just No Way on PCs generally.