News for hackers. Stuff that matters.
Re:DRM/EME in HTML5 - an American thing by jmillikin on Sunday October 13, 2013 @12:10PM (#6543042)
"off-spec and on their own dime" could also be written "for only the top 2-3 most popular operating systems". If Ubuntu, FirefoxOS, and CyanogenMod are locked out of watching Netflix but iOS and Windows work fine, then that's a significant reason for users to buy the completely proprietary systems.

  > That would be far less of a setback for the open web
  > than the current state, which bakes the notion of
  > restricted access into the open standards.
If widespread restrictions are going to exist anyway, then it's strictly better for the interface to be standardized.
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.
Re:DRM/EME in HTML5 - an American thing by pyalot2 on Sunday October 13, 2013 @01:49PM (#6543420)
> If widespread restrictions are going to exist anyway, then it's strictly better for the interface to be standardized.

Those widespread restrictions imply that only proprietary browsers and operating systems can use EME.

However "standardizing" the interface gives those proprietary companies the opportunity to claim that their solution is "standards compliant", while in reality the standard is a farce and their solutions are nothing of the kind.

Re:DRM/EME in HTML5 - an American thing by icebraining on Sunday October 13, 2013 @12:19PM (#6543076)
And if the standard is implemented, there's no reason to believe the media companies will implement Content Decryption Modules for Ubuntu, FirefoxOS, etc, so what exactly would we gain?