And I'm not happy to see web-sites and services "available" for a specific OS nor browser. That's like going back to the 90s. Not cool.
Update on HTML5 Video for Netflix
41–50 of 524 posts
Re: Update on HTML5 Video for Netflix
#42Earlier quoted context omitted.
What Netflix is doing that hurts the web is opposing net neutrality now that they're big enough they can bargain for special treatment. This—on the other hand—provides a replacement for use cases which used poorly-supported, insecure, and battery-hungry proprietary plugins. I run Safari with no extensions and having this for Netflix and Amazon is fantastic. I trust Apple to patch security vulnerabilities and the brow…
You're not getting EME extensions from Apple, you're getting them from the third-party that developed the extensions. You can count on terrible security vulnerabilities being found in these. Movies aren't important. Netflix isn't important. The open web, the ideology (or as you put it pejoratively, "purity") behind it, is important.
The amount of heat this change has generated is disproportionate to its actual role as a threat to the open web
Re: Update on HTML5 Video for Netflix
#43Does anyone else find it extremely off putting that companies that are supposed tech leaders are pushing "web" features to a subset of browsers? I really have trouble accepting the fragmentation in the web world. This includes less extreme cases like mobile/desktop versions of browsers without user ability to toggle between the two. Stuff on the web should just work on all browsers. How did we get to this point, seri…
This isn't any different from the compatibility issues across desktop operating systems. You wouldn't expect a mac desktop app binary to "just work" when double-clicked on a Windows OS.
I know, the web supposedly has a standard that should make this argument null, but the fact is browsers are basically being used as though they're little mini-operating systems by both consumers and developers. This kind of fragmentation has historically been just something that happens as each "operating environment"'s maintainers implement their own flavor of whatever, standards be damned.
And even with a completely coherent, well-formed standard, browsers will have (sometimes subtly) different behaviors between operating system implementations that will make 100% standards compliance forever be relegated to "nice to have" status.
Re: Update on HTML5 Video for Netflix
#44Translation: Netflix successfully lobied DRM into what is supposed to be the OPEN web standard, to the point where even Firefox couldn't afford not to support it. Dark days for the free exchange of information enabled by the web.
When the choice is between proprietary apps or DRM for multimedia content inside open web environment, I'd rather have the latter. Yes, in ideal world there will be DRM-free streaming - but unfortunately that's unrealistic.
Why? That puts the cost of DRM on everyone except the ones who want to freeload on our open tech to take our freedom away.
And that's ass backwards.
You want non-free and closed? Cool deal. Go build it yourself.
Re: Update on HTML5 Video for Netflix
#45Earlier quoted context omitted.
Netflix wouldn't be a viable business if not for DRM. Why is everyone so upset? Having the option to use DRM in native web APIs is not a bad thing.
>Netflix wouldn't be a viable business if not for DRM. Uh, why not? All Netflix series are already getting pirated even with DRM.
Re: Update on HTML5 Video for Netflix
#46Earlier quoted context omitted.
Netflix wouldn't be a viable business if not for DRM. Why is everyone so upset? Having the option to use DRM in native web APIs is not a bad thing.
>Netflix wouldn't be a viable business if not for DRM. Uh, why not? All Netflix series are already getting pirated even with DRM.
And even if you take netflix original content out of the picture, that applies. their "viable business" is "stream other people's content" and "other people" have to agree to that, and won't without DRM.
Re: Update on HTML5 Video for Netflix
#47Does this use Firefox's super-sandboxed Adobe CDM module [0]? [0] https://blog.mozilla.org/blog/2015/05/12/update-on-digital-r...
It may use Google's Widevine, since Firefox recently started supporting it.
Re: Update on HTML5 Video for Netflix
#48Translation: Netflix successfully lobied DRM into what is supposed to be the OPEN web standard, to the point where even Firefox couldn't afford not to support it. Dark days for the free exchange of information enabled by the web.
Am I missing something? Is this a case where an open standard is a bad thing?
Re: Update on HTML5 Video for Netflix
#49Earlier quoted context omitted.
When the choice is between proprietary apps or DRM for multimedia content inside open web environment, I'd rather have the latter. Yes, in ideal world there will be DRM-free streaming - but unfortunately that's unrealistic.
> When the choice is between proprietary apps or DRM for multimedia content inside open web environment Why? That puts the cost of DRM on everyone except the ones who want to freeload on our open tech to take our freedom away. And that's ass backwards. You want non-free and closed? Cool deal. Go build it yourself.
Re: Update on HTML5 Video for Netflix
#50They really needed DRM to survive. It's great that they can run a sandbox in my computer so I can watch videos, something which wasn't possible with the open web standards. By the way, here's the list of titles which weren't pirated thanks to DRM: .