Defend the Open Web: Keep DRM Out of W3C Standards
jrepin writes "There's a new front in the battle against digital restrictions management (DRM)technologies. These technologies, which supposedly exist to enforce copyright, have never done anything to get creative people paid. Instead, by design or by accident, their real effect is to interfere with innovation, fair use, competition, interoperability, and our right to own things. That's why we were appalled to learn that there is a proposal currently before the World Wide Web Consortium's HTML5 Working Group to build DRM into the next generation of core Web standards. The proposal is called Encrypted Media Extensions, or EME. Its adoption would be a calamitous development, and must be stopped."
It's not going to knock DRM off the web.
So why not put in a way for it to be done in a standard fashion?
Putting the ability to serve DRM content into HTML is not going to close the web.
http://lkml.org/lkml/2005/8/20/95
It will just be another technology that ends up falling on it's face while sucking money out of the corporations while they try to get it adopted as the mainstream or most adopted technology. If they are good for all, they will get used. If they aren't, why on earth would a developer use them? Every W3C set of standards has a bunch of tags that no-one in their right mind uses - or they come up with great new ways to get what they want out of them. I mean as an example (though it never made it into W3C) but look at Silverlight, Microsoft tried to take the market away from Flash, invested heavily into Silverlight, no doubt paid a LOT of developers to use their stuff, I found for a while a bunch of free downloads that "asked" to install Silverlight along with their code.
Look at these stats:
According to statowl.com, Microsoft Silverlight has a penetration of 64.16% on May 2011. Usage on July 2010 was 53.54%, whereas Adobe Flash is installed on 95.26% of browsers, and Java support is available on 76.51% of browsers (May 2011); these statistics makes Adobe Flash the market leader in terms of penetration.[20] As of 26 August 2011, 0.3% sites are using Silverlight,[21] whereas site usage of Adobe Flash is around 27%.
Taken from http://en.wikipedia.org/wiki/Microsoft_Silverlight#Adoption
Moved to http://soylentnews.org/. You are invited to join us too!
Stuff like this wouldn't be so bad if we didn't know how much an asshole these companies have always shown themselves to be in the past. Media stored on the cloud or a computer became fantastic for me because I didn't have to worry about a DVD working in the USA but then not working in another country. That means if you ever move to another country that you will have to re-buy every DVD in your collection. Fuck that. Now, I bet they'll add the same type of control here. You must buy a DRM for your specific country or even more ridiculous restrictions than this (like fast forwarding as mentioned in the article, etc.).
The rich get richer, and the poor get poorer. The free get freer, and the shackled get deader.
The G
The reality is that some apps (like Netflix) require DRM. Why not offer a standard way to do it?
1 standard is better than 1000 crappy implementations - if you don't like it just disable it like you do any other browser option and you'll never be burdened with DRM'd content.
Look, I don't care if YOU don't want to use DRM'd services like Netflix, but some of us DO, and we'd like to be able to use these sorts of services without proprietary plugins like Silverlight dictating what operating systems we can use it on.
I'm a realist. DRM is idiotic and useless, but the people holding the cards are too dumb to realize that. If that means that I have to accept unobtrusive and transparent DRM to view content because of that, so be it. DRM done right doesn't get in the user's way, and a standardized form of DRM will help keep it from getting in the way. This needs to happen.
....has been drawn my fellow geeks.
When I see comments on the inclusion of Digital Restriction Management in Web standards couched in approving tones, I know that I must be getting old. To me the only valid use of DRM in the long term is as an answer to a trivia question on screwy 'net practices of the late 20th and early 21st centuries.
If in the interim DRM is deemed necessary for some things by some people then incorporate it in a desktop or browser widget as is currently done, say, for Netflix.
And no, I haven't any wonderful answers to all kinds 'good' questions on this, or any deep thoughts on this and the related larger issues; it's just my old fart reaction.
When I bought a book, it was mine. When I used a camera it wasn't locked in to one film manufacturer. Anything with an engine would happily use any brand of gasoline of the correct octane range. When I found that a DVD player/burner I had bought was region-locked, I half flipped. Ditto, when terms of 'sale' for a program I bought on CD forbade making an archive copy.
But then, when I went to see a movie at the theater the thought to bring a movie camera never crossed my mind.
Oh, yeah, just for grins: take Netflix for an example - it uses some kind of DRM, right? (Yeah, I know it does, 'cuz I had to fire up an vm of XP to install Silverlight - until an enterprising duo came up with a wonderful change to Wine that lets me use Netflix from my Ubuntu desktop.) So then, just how many of the protected movies on Netflix don't have torrent or magnet links somewhere? If the answer is few to none, then WTF is the use of having the DRM?
All the DRM shills are out in force tonight.
You'll still need a plugin. Something has to decrypt the video stream, and that thing HAS to be closed source. Aiding and abetting DRM will simply give those who wish to use it even more power. So you will hasten the demise of Flash and Sliverlight, so what. You will introduce a browser-level means for encryption, which could readily (and if this goes in will be) used to force encryption on entire websites.
This solves ZERO problems. None. I suspect, rather, it will introduce even more closed binary modules on systems with even weaker cross platform support and even more security holes.
EME is proposed as an API, allowing "binary blobs" to execute. That's ***EXACTLY*** what Active-X does in Internet Explorer. Just like Active-X, the binary blobs won't be a complete stand-alone OS. Instead, they'll hook into your operating system, with high privileges. That means that the binary blobs will be OS-specific.
I can see compromised websites popping up with requests to load codec-XXX to "See Sexy Suzy Stripping". And there'll be a lot of idiots who'll fall for it.
I'm not repeating myself
I'm an X window user; I'm an ex-Windows user
Next thing they'll add will be DRM for web pages, so you won't be able to view the HTML code.
I mean, WTF? Millions of $$$ were invested in the web page, and now some greasy nerd can view it freely? Protect! Protect! Intellectual property!
+1 to the open source part. The code may be opn source, but the builds need trusted clients you cannot put in the public domain.
That is my main objection. Only trusted (big) players will get the decryption keys. And DRM has the feature is starts to spread. It starts with dycrypting the stream, then the renderer needs to be trusted. Next the HDCP link to the screeen, and if there was an option to encrypt the screen to eyes link, someone will build it.
Open sourcing, and freely building, any of the components in the path will result in a leak of the content. the end result is that the entire environment gets getting more closed.