Earlier quoted context omitted.
Blame Google and Microsoft. They were the people who created the specification, and pushed for it, when Netflix came begging for a solution to their DRM conundrum. Even if the W3C hadn't approved it, that's two of the big four browser vendors who are committing to implementing it anyways, which is enough to guarantee a de facto standard anyways.
No, blame the movie studios, record labels etc. They're the one which require asinine DRM support for web browsers. Google/Microsoft/Apple/Adobe want to support media content, but to do so requires towing the line with the media companies otherwise they refuse to license the content (at least in HD+). Having worked with various DRM teams I know that they have to treat their code as if its the most secret code in the…
I tried creating a web browser, and Google blocked me
101–110 of 632 posts
Re: I tried creating a web browser, and Google blocked me
#102The blame for this sits squarely on the w3c for their efforts in trying to replace flash by letting the content companies dictate standards for encrypted playback. If they had held fast, we could have forced the companies to do their key management in something like WebAssembly and avoided this gatekeeping mess.
It was never gonna happen; as soon as Intel introduced SGX, any DRM-producing company that wasn’t taking advantage of it would be seen as failing their shareholders. Even if Flash had died on schedule without browsers offering a native browser-DOM DRMed-content API, DRMed-content producers would just have jumped to another tech the DRM vendors sold them. My guess is that, if browser vendors wouldn’t have played ball,…
And if the browser vendors really didn't like it for unknown reasons then they could have just stopped supporting Java in the browser, as has largely already happened for various other reasons.
This is one of those "we all must hang together or we shall all hang separately" situations, and they apparently decided they'd prefer to hang separately.
Re: I tried creating a web browser, and Google blocked me
#103Re: I tried creating a web browser, and Google blocked me
#104How (re)usable is Adobe's Primetime DRM for something like this? Primetime was removed from Firefox in version 52 (pre-Quantum) in early 2017 [1]. Are there any others?
[1]: https://www.ghacks.net/2017/01/10/firefox-52-adobe-primetime...
Re: I tried creating a web browser, and Google blocked me
#105Thats an assumption i would say is not given. If you build something like this and you expect to support DRM, do your homework on DRM before you start building stuff around it.
Re: I tried creating a web browser, and Google blocked me
#106Re: I tried creating a web browser, and Google blocked me
#107The blame for this sits squarely on the w3c for their efforts in trying to replace flash by letting the content companies dictate standards for encrypted playback. If they had held fast, we could have forced the companies to do their key management in something like WebAssembly and avoided this gatekeeping mess.
Without W3C DRM they would have kept those plugins alive instead of deprecating them. I see no reason why they'd have migrated to webasm, webasm wouldn't provide the know-thy-customer aspect the DRM people want.
Re: I tried creating a web browser, and Google blocked me
#108If only we'd been warned about the risks of handing over so much influence to Google by basing everything around their browser... >-<
Re: I tried creating a web browser, and Google blocked me
#109This is why I break DRM when I can, treating its presence as advisory at best. From a balancing test standpoint, if you want a technological solution to people copying your work then I think you should not be allowed to claim copyright protection of your work. Pick a legal or technical solution to unauthorized copying, not both.