3 ms·

this push requires converting the web into a closed platform How so? It requires the ability to have "locked" content and a mechanism to "unlock" it, but how d

this push requires converting the web into a closed platform How so? It requires the ability to have "locked" content and a mechanism to "unlock" it, but how does this affect anything else? Honest question.

Udo 14y ago
Because the browser is an open stack. There are many layers interacting from the network protocols up to the rendering and scripting engines, and they are all open. The implementations are generally open, but more importantly it's possible to look into the data itself. You can see why this is a problem for DRM. To "properly" lock it down, you'd have to close the entire stack, and then you'd have to outlaw open source implementations. The whole thing is just not designed to disobey the user. Keep in mind that this would have to cover the entire chain, from the network connection all the way up to the screen you are allowed to play the content on. For that kind of DRM to work, your browser would have to be turned into a black box that is difficult to inspect, designed to be controlled entirely from remote, and illegal to alter. If this series of events were to unfold, closing the browser would not be done to benefit the content industry directly. They don't need that to deliver content, because they can always just put out an app and pump out their stuff that way. They can also just make a plugin if they want to deliver video content through the browser - which would possible with current technology today. That's not why they are proposing this. Instead this move would serve solely to restrict user freedom to use anything but approved apps for approved content. So to make it clear why this outrage exists: there is absolutely no technical need to include this natively in HTML5. The proposal does not aim to give something to the content industry, it is instead designed to take something away from everybody else. That's not a subtle difference. But, as I said earlier, it's doubtful it will/could play out this way. The only way to achieve this "dream" is by making the web as it exists today illegal to use, and then enforce that ban through extensive ISP surveillance. In which case a DRM solution for HTML5 wouldn't matter anyway.
- PavlovsCat 14y ago
  To "properly" lock it down, you'd have to close the entire stack, and then you'd have to outlaw open source implementations. ORLY? How does encryption work then? One could say "in order to properly encrypt your stuff, you actually need to make sure nobody is outside your window with binoculars", but that's not the job of encryption is it. I guess it would ultimately boil down to possession of private and public keys, and making it illegal to transmit those. So? As you said, they can deliver their stuff in proprietary apps already, what is lost when they use proprietary keys instead?
  - Udo 14y ago
    Yes, really. Encryption in the browser today works exactly the other way around. It's sole purpose is to ensure data integrity on my behalf as things are transmitted between me and my chosen endpoint. The endpoint is not protected from me, and I can do whatever I want with this data once it arrives in my browser. DRM would be the antithesis of that. The problem is not they keys, it's what they keys can control or not.
    - PavlovsCat 14y ago
      That you'd need a closed source browser or plugin to access the draconian DRM content that insists on protecting the render path wouldn't mean anyone would have to consume said DRM content, or use such a browser for anything else. As you said, they could as well "put out an app", they already do; and adding a "content protection provider", a black box ultimately, to a browser just turns that browser into that app. But, and that's kind of my point, it doesn't affect my browser in any way I can discern, at worst it would mean somtimes seeing "sorry, your browser (or lack of plugins/dongle/whatever) does not support playback of this content", as opposed to that page not being there in the first place.
    - jshen 14y ago
      They aren't trying to "properly" lock it down. They are trying to bring html5 up to the same level as current flash based solutions.
      - 14y ago
ferongr 14y ago
The current DRM proposal [1] requires specific platform-specific CDMs (content decryption modules) that are not prart of the the browser. Those can be anything, from an open source module with cross-platform support to (most likely) a closed-source binary distributed by the OS and not available for use by specific browsers. [1] https://dvcs.w3.org/hg/html-media/raw-file/tip/encrypted-media/encrypted-media.html https://dvcs.w3.org/hg/html-media/raw-file/tip/encrypted-med... More reading https://www.w3.org/Bugs/Public/show_bug.cgi?id=20944 https://www.w3.org/Bugs/Public/show_bug.cgi?id=20944 http://arstechnica.com/business/2012/02/unethical-html-video-copy-protection-proposal-criticized-by-standards-stakeholders/ http://arstechnica.com/business/2012/02/unethical-html-video...
onemorepassword 14y ago
Today, you can build a browser that can render all content on the web that adheres to the open standards. With DRM built in, you can adhere to the standards all you want, you still can't render all the content unless have access to the secret keys, which can only be granted to you by the powers-that-be. The only viable client-software will be that controlled by a few major companies in cahoots with the content-industry, and they will dictate terms on the rest of us, tearing down whatever "open" is left. Average users are not going to install an open, non-DRM client if that doesn't allow them to use Hulu, Netflix, YouTube, BBC etcetera. Thanks to "open", the total monopoly if Microsoft's IE6 was broken and the web moved forward. With DRM, that will no longer be a viable option. Google, Microsoft and Apple together will decide how we experience the web. If you think "open" will still play a role in that, you must haven been living under a rock for the past 10 years. Even Google's love for "open" and "neutral" has been reduced to mostly marketing.
- rimantas 14y ago
  > Today, you can build a browser that can render all content on the web that > adheres to the open standards. Actually, if your browser would only show that kind of content you wouldn't see much. Very little content on the web follows any standard at all. > Google, Microsoft and Apple together will decide how > we experience the web You forgot Mozilla. And anyone making web browsers. That how it always was, that how it always be: browsers vendors will decide that. > and they will dictate terms on the rest of us, tearing down whatever "open" is left. > Average users are not going to install an open, non-DRM client if that doesn't allow > them to use Hulu, Netflix, YouTube, BBC etcetera. And there you have it: the amount of "whatever "open" left" is immensely bigger than all hulus and netflixes. I cannot see hulu and netflix anyway, does that mean I have no access to the open web already? What does it mean "non DRM" client anyway? The one that only shows DRM'ed content? Does this exist? Back in the days of ITMS selling DRMed audio content iTunes still could play any mp3 you threw at it, and it still can do the same today. Just because some client will allow you to play DRMed content it in no way means that it won't be able to play open content. And because of that all this outrage is quite moronic. > If you think "open" will still play a role in that, you must haven been living under a rock > for the past 10 years. Even Google's love for "open" and "neutral" has been reduced to mostly marketing. Yes, I do. Your argument is just stupid.

Udo 14y ago

Because the browser is an open stack. There are many layers interacting from the network protocols up to the rendering and scripting engines, and they are all open. The implementations are generally open, but more importantly it's possible to look into the data itself. You can see why this is a problem for DRM. To "properly" lock it down, you'd have to close the entire stack, and then you'd have to outlaw open source implementations. The whole thing is just not designed to disobey the user. Keep in mind that this would have to cover the entire chain, from the network connection all the way up to the screen you are allowed to play the content on. For that kind of DRM to work, your browser would have to be turned into a black box that is difficult to inspect, designed to be controlled entirely from remote, and illegal to alter. If this series of events were to unfold, closing the browser would not be done to benefit the content industry directly. They don't need that to deliver content, because they can always just put out an app and pump out their stuff that way. They can also just make a plugin if they want to deliver video content through the browser - which would possible with current technology today. That's not why they are proposing this. Instead this move would serve solely to restrict user freedom to use anything but approved apps for approved content. So to make it clear why this outrage exists: there is absolutely no technical need to include this natively in HTML5. The proposal does not aim to give something to the content industry, it is instead designed to take something away from everybody else. That's not a subtle difference. But, as I said earlier, it's doubtful it will/could play out this way. The only way to achieve this "dream" is by making the web as it exists today illegal to use, and then enforce that ban through extensive ISP surveillance. In which case a DRM solution for HTML5 wouldn't matter anyway.

PavlovsCat 14y ago
To "properly" lock it down, you'd have to close the entire stack, and then you'd have to outlaw open source implementations. ORLY? How does encryption work then? One could say "in order to properly encrypt your stuff, you actually need to make sure nobody is outside your window with binoculars", but that's not the job of encryption is it. I guess it would ultimately boil down to possession of private and public keys, and making it illegal to transmit those. So? As you said, they can deliver their stuff in proprietary apps already, what is lost when they use proprietary keys instead?
- Udo 14y ago
  Yes, really. Encryption in the browser today works exactly the other way around. It's sole purpose is to ensure data integrity on my behalf as things are transmitted between me and my chosen endpoint. The endpoint is not protected from me, and I can do whatever I want with this data once it arrives in my browser. DRM would be the antithesis of that. The problem is not they keys, it's what they keys can control or not.
  - PavlovsCat 14y ago
    That you'd need a closed source browser or plugin to access the draconian DRM content that insists on protecting the render path wouldn't mean anyone would have to consume said DRM content, or use such a browser for anything else. As you said, they could as well "put out an app", they already do; and adding a "content protection provider", a black box ultimately, to a browser just turns that browser into that app. But, and that's kind of my point, it doesn't affect my browser in any way I can discern, at worst it would mean somtimes seeing "sorry, your browser (or lack of plugins/dongle/whatever) does not support playback of this content", as opposed to that page not being there in the first place.
  - jshen 14y ago
    They aren't trying to "properly" lock it down. They are trying to bring html5 up to the same level as current flash based solutions.
    - 14y ago

ferongr 14y ago

The current DRM proposal [1] requires specific platform-specific CDMs (content decryption modules) that are not prart of the the browser. Those can be anything, from an open source module with cross-platform support to (most likely) a closed-source binary distributed by the OS and not available for use by specific browsers. [1] https://dvcs.w3.org/hg/html-media/raw-file/tip/encrypted-media/encrypted-media.html https://dvcs.w3.org/hg/html-media/raw-file/tip/encrypted-med... More reading https://www.w3.org/Bugs/Public/show_bug.cgi?id=20944 https://www.w3.org/Bugs/Public/show_bug.cgi?id=20944 http://arstechnica.com/business/2012/02/unethical-html-video-copy-protection-proposal-criticized-by-standards-stakeholders/ http://arstechnica.com/business/2012/02/unethical-html-video...

onemorepassword 14y ago

Today, you can build a browser that can render all content on the web that adheres to the open standards. With DRM built in, you can adhere to the standards all you want, you still can't render all the content unless have access to the secret keys, which can only be granted to you by the powers-that-be. The only viable client-software will be that controlled by a few major companies in cahoots with the content-industry, and they will dictate terms on the rest of us, tearing down whatever "open" is left. Average users are not going to install an open, non-DRM client if that doesn't allow them to use Hulu, Netflix, YouTube, BBC etcetera. Thanks to "open", the total monopoly if Microsoft's IE6 was broken and the web moved forward. With DRM, that will no longer be a viable option. Google, Microsoft and Apple together will decide how we experience the web. If you think "open" will still play a role in that, you must haven been living under a rock for the past 10 years. Even Google's love for "open" and "neutral" has been reduced to mostly marketing.

rimantas 14y ago
> Today, you can build a browser that can render all content on the web that > adheres to the open standards. Actually, if your browser would only show that kind of content you wouldn't see much. Very little content on the web follows any standard at all. > Google, Microsoft and Apple together will decide how > we experience the web You forgot Mozilla. And anyone making web browsers. That how it always was, that how it always be: browsers vendors will decide that. > and they will dictate terms on the rest of us, tearing down whatever "open" is left. > Average users are not going to install an open, non-DRM client if that doesn't allow > them to use Hulu, Netflix, YouTube, BBC etcetera. And there you have it: the amount of "whatever "open" left" is immensely bigger than all hulus and netflixes. I cannot see hulu and netflix anyway, does that mean I have no access to the open web already? What does it mean "non DRM" client anyway? The one that only shows DRM'ed content? Does this exist? Back in the days of ITMS selling DRMed audio content iTunes still could play any mp3 you threw at it, and it still can do the same today. Just because some client will allow you to play DRMed content it in no way means that it won't be able to play open content. And because of that all this outrage is quite moronic. > If you think "open" will still play a role in that, you must haven been living under a rock > for the past 10 years. Even Google's love for "open" and "neutral" has been reduced to mostly marketing. Yes, I do. Your argument is just stupid.