- From: Alex M (Coyo) <coyo@darkdna.net>
- Date: Tue, 16 Apr 2013 12:29:14 -0500
- To: public-html-media@w3.org
- Message-ID: <516D8A6A.9030609@darkdna.net>
On 04/16/2013 11:55 AM, Glenn Adams wrote: > > On Tue, Apr 16, 2013 at 10:38 AM, Florian Bösch <pyalot@gmail.com > <mailto:pyalot@gmail.com>> wrote: > > On Tue, Apr 16, 2013 at 6:25 PM, Mark Watson <watsonm@netflix.com > <mailto:watsonm@netflix.com>> wrote: > > We are defining an extension point that is in some way like > <object> but with greatly restricted functionality and with > the expectation that browsers control and curate the > extensions they support. These extensions may implement DRM, > but we are not proposing to standardize a complete DRM solution. > > You are defining an extension point, that nobody can extend > because the extension activation is selective (by UA vendor), and > the only example of an extension in the wild is not independently > implementable (Widevine) which incidentially belongs to Google, > who is also promoting the standardization effort, to what amounts > in practise to a licensing scheme for their own pockets. It should > be self evident that this is isn't going to foster compatibility > going forward once other players start doing the same. > > > You seem overly fond of sweeping generalizations like: > > * nobody can extend > * cannot be independently implemented > * no path to an implementation > > Why do I get the strong sense that you haven't tried doing any of > these things? Also, why do you keep using the term "HTML-DRM" when you > know very well that there is no such a thing? > No such thing as HTML-DRM? Ah, I understand now. This must be an elaborate hoax. This is all propaganda from pirates, terrorists, hackers and revolutionaries. I see now. http://www.w3.org/2010/11/web-and-tv/papers/webtv2_submission_62.pdf http://www.w3.org/2010/11/web-and-tv/papers/webtv2_submission_65.pdf https://dvcs.w3.org/hg/html-media/raw-file/tip/encrypted-media/encrypted-media.html#goals https://dvcs.w3.org/hg/html-media/raw-file/tip/encrypted-media/encrypted-media-fpwd.html https://dvcs.w3.org/hg/html-media/raw-file/tip/media-source/media-source.html http://gizmodo.com/5461711/giz-explains-why-html5-isnt-going-to-save-the-internet https://www.techdirt.com/articles/20130129/09264821815/truly-stupid-ideas-adding-drm-to-html5.shtml http://www.techdirt.com/articles/20130313/03554322310/disappointing-tim-berners-lee-defends-drm-html-5.shtml http://arstechnica.com/information-technology/2013/04/netflix-coming-to-html5-just-as-soon-as-the-drm-ducks-are-in-a-row/ http://www.theregister.co.uk/2013/04/16/netflix_planning_html5_switch/ https://www.eff.org/deeplinks/2013/03/defend-open-web-keep-drm-out-w3c-standards http://www.engadget.com/2012/02/23/google-microsoft-and-netflix-want-drm-like-encryption-in-html5/ http://www.theverge.com/2013/4/15/4228248/netflix-plans-its-move-from-microsoft-silverlight-to-html5-video http://www.geek.com/microsoft/google-netflix-and-microsoft-propose-drm-for-html5-1537974/ http://manu.sporny.org/2013/drm-in-html5/ http://techblog.netflix.com/2013/04/html5-video-at-netflix.html http://www.streamingmedia.com/Articles/Editorial/Featured-Articles/Google-Outlines-Crucial-HTML5-Video-Development-During-Keynote-82632.aspx https://www.techdirt.com/articles/20130129/09264821815/truly-stupid-ideas-adding-drm-to-html5.shtml http://manu.sporny.org/2013/drm-in-html5/ http://www.defectivebydesign.org/no-drm-in-html5 http://boingboing.net/2013/03/10/tim-berners-lee-the-web-needs.html http://www.guardian.co.uk/technology/blog/2013/mar/12/tim-berners-lee-drm-cory-doctorow?CMP=twt_fd https://identi.ca/tag/netflix It's clearly a hoax and propaganda piece propagated pirates, hackers, cyber-terrorists and anti-capitalists. Clearly.
Received on Tuesday, 16 April 2013 17:29:42 UTC