3 ms·
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 Lin
by criddell 10y ago
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?
- josteink 10y ago> 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.
- maxerickson 10y agoAnother 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.
- cgearhart 10y agoOnly 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.
- maxerickson 10y agoHuh? 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.
- sandov 10y agoCould 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.
- simplyluke 10y agoCould you? Absolutely. Would it be used widely? Unlikely.
- hsivonen 10y agoUncheck the “Play DRM content” checkbox in Firefox, and you have your parallel stack right there. Does it still play Netflix that way? No.
- cwyers 10y agoI 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?
- k_ 10y agoIt 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).
- cwyers 10y agoThis 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.
- azakai 10y agoFirst, 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.
- criddell 10y ago> 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?
- amluto 10y ago> 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.
- izacus 10y ago> 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.
- ce4 10y agoIt will open DRM to every other websites as well as the barrier to DRM is now low enough for everyone.