W3C green-lights adding DRM to the Web's standards

Re:W3C green-lights adding DRM to the Web's standards by cbhl on Thursday October 03, 2013 @06:30PM (#6492593)

I'm writing this comment from a Samsung Chromebook. When I use Chrome OS; I'm already giving up my freedom. Chromium itself is open-source, but there are tons of binary blobs on this device: the accelerated graphics driver for the Mali GPU, the ARM build of Adobe Flash, and the EME implementation that makes Netflix work on my device.

EME is not new. There are already devices shipping with implementations, like mine. If EME is standardized, what it means for me is that there's a chance that my device will work with all DRMed content I want to access, and not on a per-service basis.

We're not talking about giving "big bad media companies" full control of the Ring 0 Hypervisor; I am still perfectly capable of flipping the virtual developer switch on my device and booting a pure version of Linux at any time. If I buy a device ships like that, I hope that future me will have the good sense to return it to the store.

[ Parent | on HN ]

Re:W3C green-lights adding DRM to the Web's standards by makomk on Thursday October 03, 2013 @08:25PM (#6493033)

You're giving up a lot more than that. Last I heard, the existing Chrome OS implementation of HTML5 EME refuses to run unless the device is a Chromebook that's locked down to ensure no unauthorized or modified code is running anywhere on the device: enable developer mode and the CDM disables itself.

[ Parent | on HN ]

Re:W3C green-lights adding DRM to the Web's standards by pdonis on Thursday October 03, 2013 @07:16PM (#6492787)

When I use Chrome OS; I'm already giving up my freedom.

Yes. Why? (I don't have a Chromebook, and don't use Chrome OS, for this very reason.)

[ Parent | on HN ]