Re:W3C green-lights adding DRM to the Web's standards
by toyg on Thursday October 03, 2013 @07:38PM
(#6492879)
Much smaller, I don't think. It will still have to grab the screen and render directly onto it. It's basically the same thing a regular plugin would do except a little bit of identity validation, from what I understand.
Technically speaking it's almost the same as the status quo, but a little bit of DRM principles have now been enshrined in the foundations of our web. Depending on what your view of DRM is, of course, this is good news or bad news; but from a technical point of view, it changes very, very little.
Re:W3C green-lights adding DRM to the Web's standards
by jeltz on Friday October 04, 2013 @07:12AM
(#6494689)
Indeed, this changes nothing technically. But what it does is harm the idea that standards should promote the the open web. You may or may not agree to this idea of course.
Re:W3C green-lights adding DRM to the Web's standards
by Drakim on Friday October 04, 2013 @04:09AM
(#6494283)
> Isn't this the same with all software?
That's exactly the point, the case is NOT so with HTML and JavaScript. A webapp I write in HTML and JavaScript is OS agnostic!
Re:W3C green-lights adding DRM to the Web's standards
by makomk on Thursday October 03, 2013 @08:22PM
(#6493028)
It's not the same because HTML5 EME is designed to ensure anyone who manages to get media working on unauthorized platforms can be arrested under the anti-circumvention provisions of the DMCA and other similar laws. As in, this was actually one of the stated requirements.
If I want to watch netflix or play GTA5 on my haiku box I'm SOL as it is unless there is a business case to be made for doing the port.
This actually makes things easier. For example netflix currently uses silverlight for their streaming, this means that in order to watch netflix you need something that supports the entire silverlight stack.
With this proposal all you need is modern browser and a compatible CDM which is a much smaller chunk of code.