News for hackers. Stuff that matters.
Re:Update on HTML5 Video for Netflix by criddell on Wednesday March 22, 2017 @03:56PM (#13934248)
I thought that the only change was that the DRM mechanism was turned into an open standard. How is this worse than before? As someone that occasionally uses Linux, I think it's great that Netflix works there now. Previously, the audience on Linux wasn't worth the development effort for Netflix.

Am I missing something? Is this a case where an open standard is a bad thing?

Re:Update on HTML5 Video for Netflix by azakai on Wednesday March 22, 2017 @04:20PM (#13934477)
First, the DRM is still not standard. Only the interface to it is. Every browser must still deal directly with the DRM provider and hope to reach an agreement with them, both technically and financially. As a result, only certain platforms are supported. New browsers face a new barrier to entry, in particular - the exact opposite of how the Web is support to work.

Second, this is worse in the sense that Netflix, Google, and Microsoft - creators of EME - have gotten the W3C to support DRM. That's not just a symbolic blow.

Re:Update on HTML5 Video for Netflix by Hydraulix989 on Wednesday March 22, 2017 @04:38PM (#13934692)
<Redacted>
Re:Update on HTML5 Video for Netflix by snissn on Wednesday March 22, 2017 @04:48PM (#13934774)
From another comment, don't necessarily think of the dilemma of a netflix user, or internet browser, instead think of the of the blow to the openness of the next person that wants to make a brand new web browser. For the new browser to fully compete, they now /NEED/ to set up a closed relationship with netflix, the drm provider, the other browsers. If it was an open standard, they could simply code the crypto algorithms that the standard needs and not need to get permission for the closed drm formats.
Re:Update on HTML5 Video for Netflix by openasocket on Wednesday March 22, 2017 @07:05PM (#13935897)
So what's the alternative, exactly? Before EME, you needed Flash or Silverlight to view DRM-ed content like netflix. Someone making a brand new web browser would similarly need to support a Flash plugin or Silverlight plugin to compete. Such a developer could choose not to bother with a Flash or Silverlight plugin, but couldn't they also choose not to bother to implement EME? What's changed?
Re:Update on HTML5 Video for Netflix by __jal on Wednesday March 22, 2017 @04:55PM (#13934848)
> it's a good compromise in a capitalist society where artists need to make money for what they produce in order to feed themselves

Funny, I haven't heard many artists clamoring for DRM, and the ones who do tend to be well beyond the feeding-themselves step on Maslow's Hierarchy.

No, it is, as always, the distributors. That's because DRM hurts artists but entrenches distributors.

It is a shitty compromise because it is the start of a closed web. Enjoy your view-source while your corporate overlords deign to give you permission.

Re:Update on HTML5 Video for Netflix by criddell on Wednesday March 22, 2017 @04:34PM (#13934635)
> First, the DRM is still not standard. Only the interface to it is.

Is a programming language a good analogy? The C++ spec says what a switch-statement should do, but nothing about how it must be implemented, right?

> New browsers face a new barrier to entry

It's not really a new barrier to entry though, is it? If I wrote a browser last year, were my chances of getting Netflix to support it better then than they are now?

What about if I wrote a new DRM scheme? With a standard interface, are the barriers to entry for me now lower?

Re:Update on HTML5 Video for Netflix by izacus on Wednesday March 22, 2017 @05:00PM (#13934907)
> Is a programming language a good analogy? The C++ spec says what a switch-statement should do, but nothing about how it must be implemented, right?

No it isn't. Example: Netflix will ask for Widevine DRM provider (and exactly that provider!). It's a proprietary closed licensed platform and your system needs to have their binary blob licensed and compiled for it. If you don't have it and didn't pay for it, you won't be able to decrypt the DRM. Of course to get your DRM blob to run, you'll also have to prove and promise to the DRM provider that you have locked out the user from their own device so they won't be able to accidentally record the video they watch.

It's impossible to make your own open implementation or compete with existing players because they built the fact that you need to negotiate with them for licensing into the standard.

Re:Update on HTML5 Video for Netflix by criddell on Thursday March 23, 2017 @08:20AM (#13939110)
> It's impossible to make your own open implementation

I don't think that's true. It's still just a plugin so as long as implement something like the Gecko Media Plugin / CDM, you should be good, or at least no worse off than before where you had to support the Flash or Silverlight plugin.

Re:Update on HTML5 Video for Netflix by merb on Wednesday March 22, 2017 @07:49PM (#13936218)
well at least as it looks Widevine has no license fees for Device Manufacturers i.e. browsers. You only need to contact them. Not sure how this company makes any money tough. (maybe through training courses)
Re:Update on HTML5 Video for Netflix by criddell on Wednesday March 22, 2017 @05:06PM (#13934961)
I'm still not getting how this is a step backwards. Last year there was no Netflix on Linux. This year there is.

Is there a better way to make strong DRM?

Re:Update on HTML5 Video for Netflix by azakai on Wednesday March 22, 2017 @06:43PM (#13935724)
It's true that in the short term this can seem like a step forward - we went from bad to slightly less bad. But it's also harmful and dangerous in the long term for all the reasons being discussed.
Re:Update on HTML5 Video for Netflix by BuuQu9hu on Wednesday March 22, 2017 @06:05PM (#13935430)
The 'Open Web' means "My browser can access ANY AND ALL CONTENT on the Web given that it supports the necessary standards."

This DRM implementation would add this suffix: "and any number of third parties have chosen to allow my browser to use their proprietary decryption modules." This is the opposite of the Open Web and therefore a threat to user freedom and the integrity of the Web as a whole.

Re:Update on HTML5 Video for Netflix by criddell on Thursday March 23, 2017 @10:42AM (#13940116)
The internet is used for a heck of a lot more than content destined for a browser.
Re:Update on HTML5 Video for Netflix by asdfgadsfgasfdg on Wednesday March 22, 2017 @05:15PM (#13935042)
EME is a much bigger barrier than the old system of plugins. With plugins you implemented the right API for the silverlight plugin and netflix would work. In the future you need to not just implement the API but persuade someone to build the plugin for your browser and then persuade each individual DRM using site to work with your browser.
Re:Update on HTML5 Video for Netflix by caf on Wednesday March 22, 2017 @09:02PM (#13936613)
The CDM is just a plugin - on Firefox it's a Gecko Media Plugin, and it seems easier to implement the GMP API than the NPAPI for Silverlight, since it's a lot more restricted.
Re:Update on HTML5 Video for Netflix by asdfgadsfgasfdg on Thursday March 23, 2017 @03:32PM (#13943353)
Please re-read my post.

These steps are not technical but they are very significant.

Consider how you would provide this plugin to your users as the author of a new browser? You have to ask the plugin authors for permission to use it.

Then consider that you have to persuade Netflix to allow the users of your browser to use their site (without changing user agents).

Neither of these steps were required with NPAPI

Re:Update on HTML5 Video for Netflix by caf on Thursday March 23, 2017 @07:16PM (#13945224)
Your browser can just download the plugin from Google the same way Firefox does. No permission required since you're not distributing it yourself. This is no different than the case of the Silverlight plugin.

There is no reason why Netflix would need to do user-agent sniffing - the EME API is built around request access to specific "Key Systems" (eg. Widevine) by well-known-name. If they do user-agent sniffing that's an entirely separate issue, and is just as much as problem in the Silverlight case.

Re:Update on HTML5 Video for Netflix by criddell on Thursday March 23, 2017 @09:40PM (#13945876)
> You have to ask the plugin authors for permission to use it.

I don't believe that's true. The plugin is freely available. You just have to write the host.

I don't think Netflix or the rights owners would care since the stream is protected equally in any browser.

Re:Update on HTML5 Video for Netflix by amluto on Wednesday March 22, 2017 @04:41PM (#13934716)
> Is a programming language a good analogy? The C++ spec says what a switch-statement should do, but nothing about how it must be implemented, right?

That's not what's going on, though. It's an API that a DRM provider can implement. A website that gets a DRM provider it doesn't recognize will refuse to work with it.

Re:Update on HTML5 Video for Netflix by josteink on Wednesday March 22, 2017 @04:08PM (#13934366)
> Am I missing something? Is this a case where an open standard

Yes. The bit where this is an "open standard" to implement completely closed, non-standard plugins, which cannot be implemented by reading the spec.

With this "open standard" any browser or OS not blessed by Hollywood can't have a full web experience.

And I take great issues with that.

Re:Update on HTML5 Video for Netflix by cwyers on Wednesday March 22, 2017 @05:06PM (#13934957)
I don't get it. You argue that not being able to visit Netflix "isn't the full experience," and so people won't choose a browser where they can't visit Netflix. So, because of this... all standards-compliant browsers should be unable to visit Netflix? So then why would anyone choose a standards-compliant browser?
Re:Update on HTML5 Video for Netflix by k_ on Thursday March 23, 2017 @03:27AM (#13937932)
It is not "not being able to visit Netflix" which isn't the full web experience. Web-based DRM will spread to other services, maybe even to other things than video.

I couldn't care less about Netflix, I never intended to use their services and never will, but this really is bad news for the web.

Netflix on the web with a plugin was fine for me: people wanting to watch Netflix on their standards-compliant browser would need to install a proprietary plugin to do so, and would have done it (at least a great number would have, I guess). It was their choice to do so (the other one being not to watch Netflix in a browser, and yes it _is_ a choice).

The difference (and it's big to me) was that it had _no_ impact on people not wanting to watch Netflix in their browser. These people did not have this proprietary code running in their browser and all the potential security issues coming with it.

IMO the browsers should (and I don't actually know if they do or not atm, this is a thing I need to check soon) at the very least let people opt in or out of this. Of course if they opt out they wouldn't be able to use services like Netflix.

And here comes the browser plugins world again... So much for killing flash (which was and still is a _great_ platform for small to medium web games).

Re:Update on HTML5 Video for Netflix by cwyers on Thursday March 23, 2017 @10:23AM (#13939973)
This again seems odd. Browsers shipped with Flash preinstalled, and EME in Firefox is a plugin.

People are just tying themselves in knots to act like the status quo is a disaster.

Re:Update on HTML5 Video for Netflix by maxerickson on Wednesday March 22, 2017 @04:14PM (#13934428)
Another way to look at it is that Netflix isn't part of the web.

I suppose that viewpoint admits that obstinance on the part of Firefox was not going to get Netflix to offer their service without DRM.

Re:Update on HTML5 Video for Netflix by cgearhart on Wednesday March 22, 2017 @05:40PM (#13935265)
Only insofar as Netflix was opting not to put their content on the web. Netflix was _not_ prevented from being on the web pre-DRM -- it's just that responsibility for meeting their requirements for access to content rested with them rather than browser developers.

edit: not really sure how I messed up the original comment, which was an incoherent mess.

Re:Update on HTML5 Video for Netflix by maxerickson on Wednesday March 22, 2017 @06:00PM (#13935391)
Huh? If a browser developer doesn't bother to implement an EME interface and get access to DRM components for their users, all that happens is that some sites don't work. It doesn't force any burden on the developer.

I understand the argument about this making it harder to develop new browsers and so on, but eschewing EME probably wasn't going to prevent that from happening, it would just happen in flash or other closed code.

Re:Update on HTML5 Video for Netflix by sandov on Wednesday March 22, 2017 @04:28PM (#13934567)
Could we "fork the web" or something?. Someone could create a parallel stack of web standards that is fully free/open. For the most part it would be the same as the conventional web standard, but open source browser developers would have something to base their developments on, something like the "OpenWeb Stack". Sorry for my bad english.
Re:Update on HTML5 Video for Netflix by hsivonen on Wednesday March 22, 2017 @04:59PM (#13934898)
Uncheck the “Play DRM content” checkbox in Firefox, and you have your parallel stack right there. Does it still play Netflix that way? No.
Re:Update on HTML5 Video for Netflix by simplyluke on Wednesday March 22, 2017 @04:40PM (#13934709)
Could you? Absolutely. Would it be used widely? Unlikely.
Re:Update on HTML5 Video for Netflix by ce4 on Wednesday March 22, 2017 @04:45PM (#13934754)
It will open DRM to every other websites as well as the barrier to DRM is now low enough for everyone.