4 ms·
That's why the W3C proposal is a proposal for an API which proprietary plug-ins would use. The plug-in will do the decoding and rendering. Therefore the EFF i
by fafner 13y ago
That's why the W3C proposal is a proposal for an API which proprietary plug-ins would use. The plug-in will do the decoding and rendering. Therefore the EFF is absolutely not over-reacting.
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...
- walid 13y agoI'm sorry but you're overlooking that this is already the case with Flash. Our other alternative to Flash is to use a native app. Both ways are not web friendly in that they both completely rely on closed standards. This is one of my gripes with Flash. It is a lock-in tool that is controlled by one company, namely Adobe, who isn't interested in my security and gives me a player for free to collect money from publishers. Native platforms, aka apps, on the other hand create a lock-in that completely ignores the browser. This draft however helps create a common standard, albeit closed, but standardized in operation which means there will be competition on other many fronts: better encryption extensions, secure, respecting privacy, all of which don't describe Flash or even QuickTime or whatever pops to mind. To point out the irony of labeling DRM as the ultimate evil: Do you use iOS/Android/Windows Phone/BlackBerry 10/Kindle?