The W3C's plan for DRM in HTML5 is a betrayal for all web users
1–10 of 158 posts
Re: The W3C's plan for DRM in HTML5 is a betrayal for all web users
#2[deleted]
Re: The W3C's plan for DRM in HTML5 is a betrayal for all web users
#3TL;DR:
# Myths
1. that DRM doesn’t work; that it exists to protect creators, but since it is easily cracked and can be worked around, it is largely ineffective and irrelevant
2. that DRM in HTML5 is a necessary compromise to finally bring an end to the proliferation of proprietary browser plugins such as Adobe Flash Player and Micrisoft Silverlight
3. that the web needs DRM in HTML5 in order for Hollywood and other media giants to finally start giving the Web priority over delivering media over traditional means
# Reality
1. DRM is not about protecting copyright. That is a straw man. DRM is about limiting the functionality of devices and selling features back in the form of services. (https://plus.google.com/107429617152575897589/posts/iPmatxBY...)
2. DRM in HTML5 doesn’t obviate proprietary browser plug-ins, it encourages them. (https://www.eff.org/deeplinks/2013/03/defend-open-web-keep-d...)
3. The Web doesn’t need big media; big media needs the Web. (http://blogs.computerworlduk.com/open-enterprise/2013/02/bbc...)
# So sign the petition
Re: The W3C's plan for DRM in HTML5 is a betrayal for all web users
#4TL;DR: # Myths 1. that DRM doesn’t work; that it exists to protect creators, but since it is easily cracked and can be worked around, it is largely ineffective and irrelevant 2. that DRM in HTML5 is a necessary compromise to finally bring an end to the proliferation of proprietary browser plugins such as Adobe Flash Player and Micrisoft Silverlight 3. that the web needs DRM in HTML5 in order for Hollywood and other m…
Honest question - why is having a framework that allows for others to provide some form of DRM different from any other plugin system that exists currently?
Re: The W3C's plan for DRM in HTML5 is a betrayal for all web users
#5What's the solution? Forking html?
Re: The W3C's plan for DRM in HTML5 is a betrayal for all web users
#6DRM is based on obfuscation at the core. How would this ever work with open source browsers?
Re: The W3C's plan for DRM in HTML5 is a betrayal for all web users
#7What's the solution? Forking html?
The solution is waiting it out. They caved on music; they will cave here too. All that is required is patience: something that is admittedly rare in the tech world, but it works.
Re: The W3C's plan for DRM in HTML5 is a betrayal for all web users
#8DRM is based on obfuscation at the core. How would this ever work with open source browsers?
It wouldn't. The explicitly stated plan from the people who originated this proposal involves proprietary browser plugins.
Re: The W3C's plan for DRM in HTML5 is a betrayal for all web users
#9It appears that the spec for EME doesn't provide a mechanism to reliably detect decryption failure, this will be inconvenient to end users. This could be alleviated by adding a mandatory tag that includes a hash of the decrypted video for verification purposes, to be tested by the client while streaming the content. If the hash is missing or incorrect the media must not play.
The Tiger Tree Hash system is already being deployed for this purpose in other systems.
Re: The W3C's plan for DRM in HTML5 is a betrayal for all web users
#10TL;DR: # Myths 1. that DRM doesn’t work; that it exists to protect creators, but since it is easily cracked and can be worked around, it is largely ineffective and irrelevant 2. that DRM in HTML5 is a necessary compromise to finally bring an end to the proliferation of proprietary browser plugins such as Adobe Flash Player and Micrisoft Silverlight 3. that the web needs DRM in HTML5 in order for Hollywood and other m…
Honest question - why is having a framework that allows for others to provide some form of DRM different from any other plugin system that exists currently?
It isn't, that's why plugins are being killed off too.