Can I get something clarified here, because I'm a bit confused about one aspect of this. So these DRM extensions are platform-specific binary globs that will b

Can I get something clarified here, because I'm a bit confused about one aspect of this. So these DRM extensions are platform-specific binary globs that will be simple to talk to via JS. The idea being that you write an HTML5 page that has a <video> tag in it, which takes content from a URI, passes it to this binary blog, which then returns you something to render. (basically, don't worry if I got the API wrong). These binary extensions: who writes them? Is there going to be a generic "Windows" DRM binary blog that gets called if you're on Windows for YouTube, Netflix, HBO, etc? That's written by (e.g) Microsoft? Or are you going to have to install DRM binaries from each website, like drivers, into your system? If it's the latter, how the BALLS^ does anyone expect that to work on linux, or more importantly (in terms of tasty tasty money) iOS? Do they actually expect it to work on iOS, or will they just deliver content through apps? If it's apps, what problem is this solution solving exactly? Is it just a way of getting rid of the downsides of flash? Because in terms of cross platform compatibility it's obviously creating its own issues. ^I wouldn't usually talk like this on HN, but I think it's warranted here