News for hackers. Stuff that matters.
Re:DRM/EME in HTML5 - an American thing by chimeracoder on Sunday October 13, 2013 @12:18PM (#6543073)
> If Ubuntu, FirefoxOS, and CyanogenMod are locked out of watching Netflix but iOS and Windows work fine

The status quo is that Linux users are already locked out of Netflix.

The only reason that Cyanogenmod users aren't is because they can run the standard Android apk, which, incidentally, is a separate proprietary blob that Netflix had to write and produce on their own dime.

I'd rather vendors be forced to ship proprietary binaries that they have to produce themselves than for them to offload the work onto open-source browsers (or, worse, be able to pressure open-source browsers to cripple their own functionality in order to preserve DRM).

> If widespread restrictions are going to exist anyway, then it's strictly better for the interface to be standardized.

If widespread restrictions are going to exist, it's better for them to be less convenient for everyone involved (both consumers and distributors), not more.

Re:DRM/EME in HTML5 - an American thing by makomk on Sunday October 13, 2013 @05:00PM (#6544151)
Actually, the status quo is that Linux users are more locked out of Netflix with HTML5 EME than they are with the existing solutions. Silverlight is a small enough plugin that people have figured out how to run it under Linux using Wine, likewise with the Android .apk and CyanogenMod; but I don't think anyone's even managed to get the EME-based Netflix for Chromebooks to run with developer mode enabled let alone on different hardware, and IE11's EME implementation requires the whole of IE11.