Cory Doctorow is fear-mongering. At this point I believe cheat engine 6.2 he is mis-representing the

Web developer, writer, speaker. Co-founder cheat engine 6.2 of his company Algonquin Studios as well as evolt.org. Has co-written “Usability: The Site Speaks for Itself,” “Web Graphics for Non-Designers,” and “Web Professional's Handbook.”
Note: I am a participant in the W3C HTML Working Group (as an invited expert ). Encrypted Media Extensions (EME) are part of the scope of the HTML Working Group. You can decide if my opinion is tainted, but I owe nothing to the W3C to warrant arguing either way. I also don't speak for the W3C.
In Doctorow's cheat engine 6.2 latest post on Boing Boing, Requirements for DRM in HTML5 are a secret , he cherry-picks an email from the W3C's Restricted Media Community cheat engine 6.2 Group where someone wants to dive into DRM requirements but is rebuffed simply because the W3C isn't making cheat engine 6.2 DRM, just the APIs to access content protected by DRM (via the EME spec): […] what we are trying to do with EME is provide a clean API to integrate cheat engine 6.2 these solutions with the HTML Media Element.
The more W3C-savvy among you may recognize that W3C community groups don't publish specifications, they provide a way for the general public to weigh in on topics and generate wider discussion. cheat engine 6.2 As stated on the Restricted Media Community Group page, [T]his group will not publish specifications. In fact, if you are reading this and care about it, you should join. You may note that the people attacking the W3C haven't.
This is why Tim Berners-Lee declared it as in scope for the W3C. DRM exists cheat engine 6.2 and has existed for a long time. DRM requires plug-ins or third-party applications right now. By creating an API that all DRM systems use, playback in the browser will be possible (via Content cheat engine 6.2 Decryption Modules), thus helping to support an open web (just use your browser) instead of continued silos (Hulu app, Netflix app, Silverlight plug-in, etc).
Tim Berners-Lee provided further context in response to community outcry. Those who are bashing the W3C for DRM should read it, or perhaps just these salient points: [I]f content protection of some kind has to be used for videos, it is better for it to be discussed in the open at W3C, better for everyone to use an interoperable open standard as much as possible, and better for it to be framed in a browser which can be open source, and available on a general purpose computer rather than a special purpose box. Those are key arguments for the decision that this topic is in scope.
It also doesn't suggest the kind of future that Doctorow outlines in his personal post, We are Huxleying ourselves into the full Orwell , where he says I’m not kidding about any of this. I can’t sleep anymore. I think it may be game over. Of all the things to lose sleep over, this really shouldn't rank. I'm not kidding.
Cory Doctorow is fear-mongering. At this point I believe cheat engine 6.2 he is mis-representing the facts to further his agenda of stopping all forms of DRM, as there is more than enough evidence to suggest the opposite of what he claims (though he never links it, so perhaps he's terrible at Google?). This may be because cheat engine 6.2 he genuinely doesn't understand what EME is intended cheat engine 6.2 to address, or it may be to drive ad revenue on Boing Boing by hitting a volatile topic, but I'd like to think it's the former.
People far smarter than I, and closer to the issues, have written about this. If you find my arguments lacking then you should read these before cheat engine 6.2 deciding the W3C is evil. DRM in HTML5 is a victory for the open Web, not a defeat , at Ars Technica, May 10, 2013. Dear EFF: please don't pick the wrong fight , by Chris Adams, October cheat engine 6.2 4, 2013. The Bridge of Khazad-DRM , by Brendan Eich (Mozilla CTO), October 22, 2013. (Austening cheat engine 6.2 ourselves to the full Brontë) Please Bring Me More Of That Yummy DRM Discussion , by Robin Berjon, January 10, 2014.
If you want to comment, I do not moderate but I don't allow anonymous posts (strictly spam issues). If you want to post without linking to a social media account, contact me on Twitter and I'll temporarily remove the restriction.
W3C is speccing cheat engine 6.2 an API to be used to access DRM content so browsers can use it. Once again, Doctorow misunderstands: http://t.co/hN04AtB5O4 — Adrian Roselli (@aardrian) January 14, 2014 Update: January 15, 2014
work on W3C EME? take heart, you'll be "raped for millenia by Satan" for that http://t.co/XaZNsVEcps — patrick h. lauke (@patrick_h_lauke) January 15, 2014 Update: January 21, 2014
accessibility Adobe analytics Apple apps ARIA Bing Blink Brightkite browser Buzz Chrome clients css design DRM Facebook cheat engine 6.2 Firefox Flash fonts food Foursquare g11n geolocation globalization Google Gowalla html i18n ICANN infographic Instagram internationalization internet Internet Explorer JavaScript JAWS Klout L10n law localization Lynx Mapquest Microsoft mobile Netscape NetSol ning Opera patents picplz cheat engine 6.2 Plus print privacy project management QR rant RSS Safari SCVNG