News for hackers. Stuff that matters.
Re:Update on HTML5 Video for Netflix by jasonkostempski on Wednesday March 22, 2017 @03:25PM (#13933938)
It would be better if the platforms that wanted DRM just made their own damn desktop apps, just like they make their own iOS apps, Android apps, Roku apps, smart tv apps, etc. There's no reason for them to be embedded in a browser.
Re:Update on HTML5 Video for Netflix by hsivonen on Wednesday March 22, 2017 @04:26PM (#13934539)
Why would you prefer letting streaming companies have full code execution on you desktop instead of having browsers mediate?
Re:Update on HTML5 Video for Netflix by zanny on Wednesday March 22, 2017 @04:31PM (#13934605)
I wouldn't, and they knew that.

They knew the adoption rates for out-of-browser proprietary content viewers were awful. That is why they dedicated resources to usurp the open web.

If Mozilla had fought back, we might have progressed towards the death of the obsolete content model big media wants to keep in place and prevent change in the market. It would have at least been a step in the right direction - instead, the promise of the open Internet was sabotaged, and big media gets to be more "convenient" at its sacrifice.

Re:Update on HTML5 Video for Netflix by kibwen on Wednesday March 22, 2017 @05:05PM (#13934952)
Mozilla did fight back, but nobody in the OSS community at large bothered to care about EME until the writing was already on the wall. I remember being at the Mozilla Summit 2013 discussing Mozilla's alternative proposals, but even by then the prevailing mood was that of imminent despair at the inevitable.
Re:Update on HTML5 Video for Netflix by rtpg on Thursday March 23, 2017 @03:11AM (#13937893)
out of curiosity, what alternative proposals were offered?
Re:Update on HTML5 Video for Netflix by kibwen on Thursday March 23, 2017 @12:59PM (#13941610)
AFAIR the alternative with the most promise involved implementing a new video codec in JS (heavily leveraging the GPU and the then-nascent asm.js) with first-class support for digital watermarking, then convincing studios that per-user watermarking was more effective than DRM. You can see the difficulty of Mozilla's position: it wasn't enough to come up with an alternative to EME, they had to come up with an alternative to DRM altogether. A tough sell, to say the least, and basically DOA because Chrome and IE were shipping EME for use with Netflix in 2012.
Re:Update on HTML5 Video for Netflix by wildmusings on Wednesday March 22, 2017 @04:38PM (#13934680)
Or more realistically, if Mozilla had fought back, more people would simply have stopped using Firefox.
Re:Update on HTML5 Video for Netflix by problems on Wednesday March 22, 2017 @04:48PM (#13934775)
Yeah, the problem started when people decided installing a browser from an ad agency seemed like a good idea.
Re:Update on HTML5 Video for Netflix by wildmusings on Wednesday March 22, 2017 @06:20PM (#13935554)
Why is reasonable DRM a problem in the first place? I'm paying Netflix $8 a month to watch thousands of movies whenever I want. Being constrained to a large number of devices that take some steps to prevent someone from ripping the movies is a fair tradeoff. It works flawlessly on my computer, on my phone, and on my xbox. The DRM hasn't bothered me once.
Re:Update on HTML5 Video for Netflix by zanny on Wednesday March 22, 2017 @06:54PM (#13935810)
Because I'm going to immediately argue with you that there is no reasonable DRM.

It comes from two ideological positions. One believes that content creators need complete systemic control of what they make - at all costs (that the creator maintains full control no matter how the content is interacted with) - and the other is that content shouldn't be controlled (or that I, as a buyer of content, should control the content I bought), and all real world implementations fall between those extremes.

But when it comes to DRM, it should be understandable that plenty of people (myself included) are not willing to allow third party companies to run proprietary code (the drm) on my hardware for the exclusive purpose of preventing me from interacting with data on my own computer (the streamed movie / music). When web browsers start baking in this proprietary functionality, it forces me to look for alternatives to the established open source browsers.

If you are content with that relationship with content (heh) providers, then this is not your fight. But at least accept that a lot of us want to own our computers, and proprietary software takes away that right, and DRM is just one of the more visceral forms proprietary software takes where its entire purpose is to impede the users ability to control their computers.

Re:Update on HTML5 Video for Netflix by merb on Wednesday March 22, 2017 @07:37PM (#13936128)
> or that I, as a buyer of content, should control the content I bought

your never bought content. you only rented it. this is especially true on netflix & co

Re:Update on HTML5 Video for Netflix by usrusr on Wednesday March 22, 2017 @07:46PM (#13936193)
So, install a DRM-free browser on your universal computer and get a dedicated box for the subscription service? Except for perfectly avoidable waste, what did I miss?
Re:Update on HTML5 Video for Netflix by jasonkostempski on Wednesday March 22, 2017 @09:15PM (#13936683)
The problem is, eventually, no one is going to make an DRM-free browser because "no one" will use it if they can't watch movies or access whatever other content will be locked down with EME. Firefox let's you easily disable DRM, for now, I have no faith it will remain that way forever. If content providers were really never going to give up on DRM requirements, I think a standardized "Media Browser" specification should have been created with the only goal being audio/video delivery, completely separate from web standards. I don't even understand why Netflix wants to be under the thumb of the major browsers, they should be the one's looking for a dedicated solution so they can declare independence.
Re:Update on HTML5 Video for Netflix by problems on Wednesday March 22, 2017 @10:27PM (#13936979)
Yes, the bundling is ridiculous, but as long as the browser is open source, it'll still be possible to disable it - it's a tiny amount of code to allow that to happen, not a high maintenance effort item at all.
Re:Update on HTML5 Video for Netflix by Razengan on Wednesday March 22, 2017 @09:27PM (#13936744)
> content shouldn't be controlled (or that I, as a buyer of content, should control the content I bought)

How should content creators protect against people who access their content without buying it?

Re:Update on HTML5 Video for Netflix by problems on Thursday March 23, 2017 @01:37AM (#13937601)
They quite frankly can't technically, only legally - they're selling a 0 margin good, anyone who has it can basically give away infinite copies at zero cost per additional copy. Anyone who wants it for free will have it for free. They need no more than drop a few words into Google or type the name of something into a fully automatic tool like Sonarr.

It's pointless for them to bother trying to stop piracy, especially of analog content using technical means.

Re:Update on HTML5 Video for Netflix by wildmusings on Thursday March 23, 2017 @11:23AM (#13940516)
"but it's not perfect, someone could just xyz and abc and get around the system."

DRM is not about being perfect against a dedicated pirate. Just like locks on doors, it's about putting up a few barriers that serve to keep the vast majority of people honest. No one is under any illusions that DRM will stop movies and games from showing up on torrent trackers.

Re:Update on HTML5 Video for Netflix by problems on Thursday March 23, 2017 @01:02PM (#13941638)
There's a big different between breaking a door down to bypass a lock and pirating a movie via bittorrent though.

It doesn't "keep honest people honest" when piracy is so damn easy regardless of what they do with DRM. The point of that phrase is to increase the effort and motivation necessary to commit a crime - in this case, DRM doesn't do that. With or without DRM any idiot can download the latest Popcorn Time fork and stream movies with 1 click. DRM doesn't hinder the most casual of pirates at all, it only hinders honest customers.

Re:Update on HTML5 Video for Netflix by wildmusings on Thursday March 23, 2017 @02:20PM (#13942534)
People are pretty wary of using torrents because they're scared of being sued. What DRM on Netflix prevents is you ripping all of the seasons of your favorite shows, with almost no risk of getting caught, and then cancelling your Netflix subscription/sharing the rips with your friend, who is probably not inclined to use torrent sites.
Re:Update on HTML5 Video for Netflix by problems on Friday March 24, 2017 @01:01AM (#13946724)
Most people I know who casually pirate things don't even use torrents, they use streaming websites, file lockers, Kodi plugins, etc. Which offer similarly no risk of getting caught. I was simply using Popcorn Time as the extreme example of the level of ease it can be at.

None of these are exactly out-of-the-way high-effort options. There's no increased effort - you just don't bother trying to do so via Netflix. Any of these can be Googled in a few minutes. DRM does nothing to prevent them.

The legal risk you're talking about is just that though - nothing to do with DRM, everything to do with a legal threat. Note that it's more effective than DRM.

Even those who do go out of their way somewhat to improve the piracy experience don't go that far. I wouldn't compare configuring a typical Usenet+Sonarr+CouchPotato+Plex rig to breaking down a door, and that's pretty much the most advanced sort of setup you can get. It may require slightly specialized knowledge, but it doesn't require specialized intent usually. The intent is still the same as that of the casual pirate, it's just a tradeoff of upfront effort for later ease.

Re:Update on HTML5 Video for Netflix by Razengan on Thursday March 23, 2017 @02:00AM (#13937668)
So how do we ensure people keep making quality content and software? Should they give it away for free by default and just count on charity?

Seems to me the only ultimate solution is to have some kind of guaranteed basic income, at least for all people that aren't involved in the creation of tangible goods (that can't be copied at zero cost).

Re:Update on HTML5 Video for Netflix by problems on Thursday March 23, 2017 @01:06PM (#13941691)
Or - without doing any of that - just ship it on the honor system - no DRM. GOG does it and they still get more than 1 sale per game.
Re:Update on HTML5 Video for Netflix by Razengan on Thursday March 23, 2017 @03:12PM (#13943137)
> How should content creators protect against people who access their content without buying it?

This question got downvoted. What did you read into it, or which insinuation do you think it makes that you find offensive?

Re:Update on HTML5 Video for Netflix by Razengan on Wednesday March 22, 2017 @09:25PM (#13936735)
Does anyone remember what the prevailing mood was like when/before Chrome started becoming popular? Were people simply happy to see more companies putting a dent in that avatar of Lovecraftian horrors that was Internet Explorer?

Why didn't Mozilla work harder to catch up with Chrome and counter Google? Was it a case of "My enemy's enemy is my friend?"

And why did Opera slip away into the mists of obscurity? I remember it being pretty good and it was actually my main browser for a year or so.

Re:Update on HTML5 Video for Netflix by problems on Wednesday March 22, 2017 @10:18PM (#13936951)
> Why didn't Mozilla work harder to catch up with Chrome and counter Google? Was it a case of "My enemy's enemy is my friend?"

I'd argue that this "catching up to Google" was more their problem than their solution.

In making Firefox more and more Chrome-like they took away many unique and important Firefox features and they keep moving further and further in that direction. They now want to trash XUL and move to an extension framework that exactly matches Chrome's, removing the deep flexibility and customization that Firefox users have enjoyed. Several of my favorite extension authors have already announced they're giving up when that change happens.

If your browser just plays catch up without differentiating itself in any significant way, why would anyone use it?

Mozilla came up with some cool UI ideas, but never implemented them, or quickly did so, got them to a tiny percentage of their full potential and then abandoned them. That's the kind of thing they should be focusing on - that's the kind of thing that made Firefox gain market share in the first place. Instead they keep playing catch up. And playing catch up with a massive codebase against a giant company is incredibly hard.

Right now Brave is doing a better job differentiating itself and it's built on top of Electron - on Chrome's core codebase. If it were a little more active I think it'd have a shot at something.

Re:Update on HTML5 Video for Netflix by jasonkostempski on Wednesday March 22, 2017 @06:32PM (#13935643)
That's a good reason. Ideally sand-boxing desktop applications will be an easy thing to do in the future. Maybe the big companies involved in making this Netflix thing happen could have spent their time coming up with a cross platform standard for that. No matter what, the open internet's more important than me or you or even Morpheus. I make the trust call with desktop applications every day, I'd be ok with making the call for 1 or 2 more. I have DRM turned off in Firefox and I won't change it for Netflix or Hulu (the only 2 sites for me that don't work with it off), I limit Netflix and Hulu use to Roku.
Re:Update on HTML5 Video for Netflix by nikcub on Wednesday March 22, 2017 @05:08PM (#13934980)
Because the browser provides a privacy and security sandbox where you can't be fingerprinted and where it is more difficult to turn decoding bugs into remote code execution exploits.

Users should have a lot more faith in the protections of a browser over the free-for-all security and privacy nightmare that is desktop computing.

Re:Update on HTML5 Video for Netflix by greenhouse_gas on Wednesday March 22, 2017 @06:14PM (#13935503)
Who told you it's going to be sandboxed? It's probably going to be a obfuscated binary blob (it has to of it wants to try ensure that nothing is intercepting it) which will try verifying that OS isn't intercepting data.
Re:Update on HTML5 Video for Netflix by nikcub on Wednesday March 22, 2017 @06:51PM (#13935786)
Firefox:

https://bugzilla.mozilla.org/show_bug.cgi?id=1021232

https://bugzilla.mozilla.org/show_bug.cgi?id=1021235

The spec talks about both securing the CDM with Sandboxing and preventing fingerprinting, amongst other security + privacy issues that should be addressed:

https://w3c.github.io/encrypted-media/#cdm-security

https://w3c.github.io/encrypted-media/#privacy-fingerprintin...

the spec also says if the CDN isn't sandboxed then the user needs to be warned and prompted to allow exec:

> if a user agent chooses to support a Key System implementation that cannot be sufficiently sandboxed or otherwise secured, the user agent should ensure that users are fully informed and/or give explicit consent before loading or invoking it.

Re:Update on HTML5 Video for Netflix by mtgx on Wednesday March 22, 2017 @03:32PM (#13934011)
The irony is that Netflix does have a desktop application as well.
Re:Update on HTML5 Video for Netflix by jasonkostempski on Wednesday March 22, 2017 @03:36PM (#13934047)
Not for Linux and I know first had that the Windows Store one is complete garbage because I really wanted it to work. The Hulu one is just as bad.
Re:Update on HTML5 Video for Netflix by flukus on Wednesday March 22, 2017 @07:39PM (#13936146)
I've used the windows one a fair bit and would take it over the browser one any day. The desktop one wins for resource usage alone.
Re:Update on HTML5 Video for Netflix by jasonkostempski on Wednesday March 22, 2017 @09:20PM (#13936714)
For me, it usually wouldn't start up (some oddball Windows Store error, probably because I don't sign into my machine with a Microsoft ID) and streaming quality was horrible, especially at the beginning, and there was no way to tell it to wait longer for buffering.
Re:Update on HTML5 Video for Netflix by futurix on Wednesday March 22, 2017 @03:38PM (#13934061)
This is mostly a side effect of their development efforts for Xbox and Windows 10 Mobile.