News for hackers. Stuff that matters.
Re:Update on HTML5 Video for Netflix by cyborgx7 on Wednesday March 22, 2017 @03:13PM (#13933804)
Translation: 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.
Re:Update on HTML5 Video for Netflix by dasil003 on Wednesday March 22, 2017 @06:16PM (#13935520)
Sorry, but as someone who spent nearly a decade founding and building a premium content VOD service, and 6 of those years fighting fiercely against DRM and making great content available without DRM, I have both the knowledge and moral authority to say that you're living in a fantasy world. You might as well say that anyone who is not living an RMS-sanctioned ascetic technology lifestyle is hurting the cause of free software everywhere. Technically that might be true, but a few true believers martyring themselves is not going to change the social and political forces that drive software over time.

Here's the bottom line: browser makers have absolutely zero leverage over DRM. Firefox refusing to implement DRM would have been 1000 times more likely to lead to Firefox's irrelevance and death than it would lead to rightsholders caving on DRM requirements. Even if all browsers banded together and refused, all that would mean is that premium content would not be available in browsers, and that would lead to a significant devaluation of the web in favor of proprietary apps. It is a techno-centric fantasy to think that browser makers have even a modicum of leverage here. The fact is content producers would restrict themselves to licensed devices in a heartbeat, and they would get away with it to, because at the end of the day, people want to watch what they want to watch.

EME is a ideological compromise, sure, but it's a net benefit to the open web since its scope is small and it maintains the overall schema of web standards. It shouldn't be considered worse than proprietary plugins with arbitrary scope.

Re:Update on HTML5 Video for Netflix by amelius on Wednesday March 22, 2017 @07:27PM (#13936040)
People have been recording the things they watch since the invention of the VCR.

DRM will not have any impact on that. Someone will come along, and make a video-grabbing utility that bypasses the DRM. Also, many of the content is already available via bittorrent.

DRM is pointless. But perhaps you are right about "browser vendors refusing to cooperate" not being the best possible approach. However, do you know what is?

Re:Update on HTML5 Video for Netflix by derekp7 on Wednesday March 22, 2017 @08:47PM (#13936558)
We somehow got away from DRM on audio. I was wondering how to do this for video too. What worked for audio, was that you had one vendor (Apple) that had a large enough market share. In order to sell DRMd media that worked on Ipods, the media companies had to sell through Apple. Or they could sell non-DRMd files that would still work on Ipods. They did the calculation, and figured they would make more money going non-DRM so they can pick other distributors such as Amazon.

For video, people don't download it and take it with them (typically), they either play from their computer or from a set top box or smart TV. So there is no market forces that would give the movie studios any incentive to do non-DRM.

Re:Update on HTML5 Video for Netflix by eugeniub on Wednesday March 22, 2017 @09:53PM (#13936853)
> We somehow got away from DRM on audio.

Did we? Look at Apple Music, Spotify, and other subscription music services. They all have DRM.

Re:Update on HTML5 Video for Netflix by drdrey on Thursday March 23, 2017 @12:28AM (#13937375)
But music you buy on iTunes is DRM-free. That's a significant step away from DRM.
Re:Update on HTML5 Video for Netflix by josteink on Thursday March 23, 2017 @02:35AM (#13937783)
> But music you buy on iTunes is DRM-free. That's a significant step away from DRM.

And Amazon. And Google Play music. And band-camp. Etc etc.

In fact, I don't know a single place on the entire internet which still sells DRMed music. Such a thing simply ceased to exist.

Imagine if we could make the same happen for video. That would be real nice.

Re:Update on HTML5 Video for Netflix by Twisell on Thursday March 23, 2017 @04:01AM (#13938043)
Yes but in Netflix case and html5 we are precisely talking about streaming service.

Download should be DRM free for free for vidéo that's true but don't blame Netflix for using DRM on a streaming service as every music streaming service does that too.

Indeed I think studios could reduce pirating to baseline (people who can't afford anyway) in a split second should they understand that people are willing to pay for a fair priced streaming service like Netflix. They just need to open up their catalogs like music majors finally did as an average wallet can hardly sustain a dozen different subscriptions in order to have a decent movie catalog.

Re:Update on HTML5 Video for Netflix by sneak on Thursday March 23, 2017 @04:58AM (#13938239)
Nobody normal buys music and shuffles files around anymore.

They all just switched to DRMed streaming services.

Re:Update on HTML5 Video for Netflix by josteink on Thursday March 23, 2017 @06:23AM (#13938580)
I think the entire Plex userbase would disagree. There's also a reason Google Play Music lets you upload your own music: Not all music can be found in "regular" streaming catalogs.

Technicalities aside: Also I like to think that buying albums (even if I stream them later on) makes the artist more money. And I want to support the artists I appreciate as much as I can.

Re:Update on HTML5 Video for Netflix by sneak on Thursday March 23, 2017 @06:37AM (#13938632)
I meant "normal" as in mass-market, not "normal for HN". I, probably like you, of course have a unix fileserver in my residence (as well as a metric ass-ton of vinyl, because it seems we are similar types of nerd).
Re:Update on HTML5 Video for Netflix by thirdsun on Thursday March 23, 2017 @03:32AM (#13937941)
How else would a subscription service work? If you bought your music instead of renting it you'd truly own it without DRM or any other strings attached.

As a very frequent music buyer, I'd say the situation is very comfortable and user-friendly and I'd wish to see the same for video content.

Re:Update on HTML5 Video for Netflix by xg15 on Wednesday March 22, 2017 @08:59PM (#13936601)
> What worked for audio, was that you had one vendor (Apple) that had a large enough market share. In order to sell DRMd media that worked on Ipods, the media companies had to sell through Apple. Or they could sell non-DRMd files that would still work on Ipods.

Ironically, this scenario just got more unlikely, thanks to EME now being a standard and thus available for everyone... Hooray for web standards!

Re:Update on HTML5 Video for Netflix by Silhouette on Wednesday March 22, 2017 @09:03PM (#13936617)
We somehow got away from DRM on audio.

We got away from it with audio in part because a typical audio product such as a music single or short audiobook can viably be produced and sold DRM-free at a price so low that it's hardly worth anyone looking for it elsewhere even if they could find it literally for free. Unfortunately, the same economics don't work in most other markets.

Re:Update on HTML5 Video for Netflix by MBCook on Wednesday March 22, 2017 @10:34PM (#13937009)
> We somehow got away from DRM on audio.

Guess which industry watched how that happened REALLY REALLY closely?

The music industry was falling apart by the time they gave up on DRM, the video industry is still very strong and had time to learn where all the mistakes were made that lead to DRM free content.

Re:Update on HTML5 Video for Netflix by ubernostrum on Thursday March 23, 2017 @02:50AM (#13937826)
The end of DRM for purchased music downloads was primarily driven by the need to break what the record industry perceived as a monopoly.

They got in bed with Apple, and at first they were happy with that -- Apple showed that offering a legal way to download music would succeed, so long as it was A) convenient, B) had a suitably large catalog and C) was priced in a way customers saw as fair.

And the result was Apple became a major player in the market, to the point that the record labels started getting scared of what Apple could now force them to do. So they needed to give Apple a competitor. Except... Apple wasn't about to license its Apple-specific DRM scheme to that competitor, and wasn't going to install the competitor's DRM scheme on Apple devices. Which left them with no way to introduce a serious competitor other than to go DRM-free so purchased music would be playable on all the popular devices, including Apple's. Thus, Amazon got to start selling DRM-free music (and eventually Apple got to sell it too).

I suspect sooner or later the book industry will have to go DRM-free to break Amazon's ebook stranglehold, in much the same way.

But video... is different. There isn't a monopolish player in the online video market. There are multiple competing services, some doing purchase and some doing temporary rental and some doing streaming and some doing combinations of multiple options, and there's nobody emerging with power to dictate to movie/TV studios the way Apple emerged in music or Amazon did in ebooks. Which suggests DRM on video is going to be with us for a while no matter what.

And video is one area where I have some sympathy for attempts to control access: the video market is quite young compared to music or books, and has had the short-term rental as a key segment of its market for roughly as long as it's existed. And this makes some sense, as video content tends to have less long-term re-use value: listening to a song multiple times, and re-reading a book multiple times, both seem to be much more common than watching a movie multiple times. So providing a reduced-price option which limits the number of times or amount of time of watching makes business sense. I'm unsure how to reconcile that with hardcore anti-DRM positions, since some type of access control is necessary to enable a rental market.

Re:Update on HTML5 Video for Netflix by MBCook on Thursday March 23, 2017 @03:52PM (#13943572)
> I suspect sooner or later the book industry will have to go DRM-free to break Amazon's ebook stranglehold, in much the same way.

I wonder about this, because the fact is that I really LIKE Amazon's system. It doesn't matter where music comes from, I listen to it over and over and usually listen to each song totally.

But with books, it takes more than 3 minutes to read. The fact that all my stuff (Kindle App, Kindle, website) know my place and sync all that stuff is very handy. It's the main reason I use Kindle over physical books.

If you load non-DRMed eBooks onto Kindle my understanding is you don't get that functionality for them and I'm guessing no one would have the power to force Amazon to implement that feature. The end result is that Amazon's DRMed books may be more appealing to me than DRM free options from other places.

As for breaking their monopoly.... Apple tried and the government smacked them down for it.

Re:Update on HTML5 Video for Netflix by jMyles on Wednesday March 22, 2017 @10:57PM (#13937107)
> For video, people don't download it and take it with them (typically)

...which is crazy, especially for HD video. Why use the bandwidth every time you want to watch something when storage is so much cheaper?

Re:Update on HTML5 Video for Netflix by cstrahan on Thursday March 23, 2017 @12:55AM (#13937475)
That's assuming people are going watch things multiple times. Most people, including myself, are one and done.

I've always rented the movies I've watched because I know I won't watch them again, so the savings is win on the whole.

I guess there's something to be said for TV shows, as people often watch those over. I generally don't watch TV series, the exception being a couple Netflix series that friends have begged me to watch, so I don't have too much of an opinion there.

Re:Update on HTML5 Video for Netflix by jon-wood on Thursday March 23, 2017 @05:28AM (#13938350)
I think this could be rephrased as people don't consciously download things to keep forever. Whatever device you're watching on will cache anything you've viewed for a while so it doesn't need downloading again, and I at least make quite heavy use of the ability to save things for offline viewing on train journeys.

What I don't do anymore is to download video or music and then just keep it around on a hard disk just in case I want to watch it again. At least in my case storage is actually far more expensive than bandwidth, both in monetary value and time spent maintaining things.

Re:Update on HTML5 Video for Netflix by Sharlin on Thursday March 23, 2017 @06:41AM (#13938651)
Bandwidth is practically free at least where I'm living in. Storage is something I need to think about and go buy separately.
Re:Update on HTML5 Video for Netflix by kriro on Thursday March 23, 2017 @03:39AM (#13937970)
I'd say this is false. I'd love to watch more videos when I commute. My Pay TV provider even offers a download option for their streaming sub service(DRMed and self destructing after X days I think, never tried it) which would indicate that there's certainly market demand for it.
Re:Update on HTML5 Video for Netflix by hsivonen on Thursday March 23, 2017 @06:24AM (#13938591)
Download as in "cache this title within this app for viewing in an environment where Internet connectivity doesn't work well yet" is very different from download as in "here's an .mp4/.webm file for you to hold onto for ever--have fun taking backups and figuring out which third party player can handle the subtitles.

Fun story: Not very long ago, I bought a copy of a documentary using the latter model.

Another person with whom I was going to watch the documentary had visited their site and seen what movie services it was on. I trusted that info at first without checking the documentary's own site. I got very annoyed about the movie services having the title geoblocked in my country (even when a movie service had presence here and in a neighboring country and the rights for both countries are typically sold as a bundle and the neighboring country had it available!).

Then I looked at the site of the documentary myself. And indeed, for the price of the Blu-Ray version, I could buy a full-HD .mp4 without DRM to download.

So I paid and downloaded the .mp4 plus .mp4s for all the Blu-Ray extras. And I downloaded a .srt file for the subtitles.

The Linux box I had connected to my TV couldn't do full HD well in software but could via VAAPI. However, the player that supported VAAPI was supposed to support .srt but didn't actually support at least this .srt file.

In the end, we watched it by pluggin in a more performant Windows laptop doing the whole thing in software.

Conclusion: This is what we always said we wanted. However, when it was there, I didn't expect it to be there and assumed I had to find the title on one of the big-name services instead of navigating to the documentary's own site. The UX of getting stuff to work was less smooth than with the locked-down streaming services.

Re:Update on HTML5 Video for Netflix by Arnt on Thursday March 23, 2017 @05:07AM (#13938263)
Some people want to download, they're a smallish minority. You can think about some reasons if you want, but but do the reasons really matter?
Re:Update on HTML5 Video for Netflix by nsomaru on Thursday March 23, 2017 @12:51AM (#13937464)
Guessing that it's probably more rare to watch something again than it is to watch something new.
Re:Update on HTML5 Video for Netflix by toomanybeersies on Thursday March 23, 2017 @09:15PM (#13945777)
People usually watch video once, but listen to songs multiple times.
Re:Update on HTML5 Video for Netflix by canibal on Thursday March 23, 2017 @08:04AM (#13939012)
>For video, people don't download it and take it with them

If this is so, why would Netflix have JUST added the download feature last quarter? Obviously there's some demand for storage-based playback.

Re:Update on HTML5 Video for Netflix by cletus on Thursday March 23, 2017 @04:45AM (#13938198)
You can thank Steve Jobs for that.

When digital music downloads started record companies demanded DRM. They agreed to a model with iTunes of $0.99 per song. They chafed against this model and wanted pricing tiers. Jobs was willing to give them this but the price was to go DRM free.

Jobs could get away with this for two reasons. First, he was Steve Jobs. Second, the record industry had unwittingly created a virtual music download monopoly in iTunes.

I personally use Spotify because streaming is incredibly convenient and there isn't much you can buy but can't stream. I use Netflix and Ahbo Now for the same reason.

I'd never "buy" DRMed content so music would be fine. Video not so much. I personally don't have as much of an issue with DRM on streaming content.

Re:Update on HTML5 Video for Netflix by dchest on Thursday March 23, 2017 @05:27AM (#13938344)
Contrary opinion from a former Apple employee:

"The music industry didn't go DRM free because they hated DRM; they went DRM free because they were fearful of the leverage Apple was gaining with their iTunes + FairPlay + iPod combination. Apple’s DRM created this lock, and it became so successful that the music industry went with the lesser of two evils (songs locked to Apple’s iPod monopoly vs. the distribution of DRM-free music) and chose to distribute DRM-free music...

http://fortune.com/2014/12/14/re-thinking-steve-jobs-thought...

You say "Jobs was willing to give them this but the price was to go DRM free", but why would he do that if DRM was good for Apple, it's what locked this market to iPods? Doesn't make sense to me. The music industry had to go DRM free (with Amazon, for example) because that was the only alternative way to sell music that would play on iPods.

Re:Update on HTML5 Video for Netflix by lloeki on Thursday March 23, 2017 @06:27AM (#13938604)
> You say "Jobs was willing to give them this but the price was to go DRM free", but why would he do that if DRM was good for Apple, it's what locked this market to iPods?

Here goes a ~10yo tidbit from SJ [0]. Whether you take it at face value, see it as a PR trick, or anything in between is up to you.

> Apple was able to negotiate landmark usage rights at the time, which include allowing users to play their DRM protected music on up to 5 computers and on an unlimited number of iPods. Obtaining such rights from the music companies was unprecedented at the time, and even today is unmatched by most other digital music services. However, a key provision of our agreements with the music companies is that if our DRM system is compromised and their music becomes playable on unauthorized devices, we have only a small number of weeks to fix the problem or they can withdraw their entire music catalog from our iTunes store.

> [...] only 22 out of 1000 songs, or under 3% of the music on the average iPod, is purchased from the iTunes store and protected with a DRM. The remaining 97% of the music is unprotected and playable on any player that can play the open formats. It’s hard to believe that just 3% of the music on the average iPod is enough to lock users into buying only iPods in the future. And since 97% of the music on the average iPod was not purchased from the iTunes store, iPod users are clearly not locked into the iTunes store to acquire their music.

> The third alternative is to abolish DRMs entirely. Imagine a world where every online store sells DRM-free music encoded in open licensable formats. In such a world, any player can play music purchased from any store, and any store can sell music which is playable on all players. This is clearly the best alternative for consumers, and Apple would embrace it in a heartbeat.

> Why would the big four music companies agree to let Apple and others distribute their music without using DRM systems to protect it? The simplest answer is because DRMs haven’t worked, and may never work, to halt music piracy. Though the big four music companies require that all their music sold online be protected with DRMs, these same music companies continue to sell billions of CDs a year which contain completely unprotected music.

[0]: https://web.archive.org/web/20080107121341/http://www.apple....

Re:Update on HTML5 Video for Netflix by amelius on Thursday March 23, 2017 @06:29AM (#13938609)
> ... the record industry had unwittingly created a virtual music download monopoly in iTunes.

I really wonder how they could have been so stupid.

Re:Update on HTML5 Video for Netflix by flukus on Wednesday March 22, 2017 @09:51PM (#13936847)
Aren't music publishers a lot less consolidated than there movie/TV counterparts?
Re:Update on HTML5 Video for Netflix by yeukhon on Wednesday March 22, 2017 @10:12PM (#13936925)
Kinda of, but most labels find the big three for both production and distribution. There is independent distribution company within each of the big three to attract independent labels. Most labels come to the big three simply because they have the infrastructure in place for global distriubtion from marketing to production to music distriubtion to all the major DSP (digital service providers) such as Apple and Spotify, as well as ringtone. One interesting thing about music deal is that while the big three have the infrastructure and capability, for example WMG can sign a deal with Sony in terrority Y (a country or multiple countries) for the release of X there and they split the royality, and vice versa.

I said kinda of because not all sign with big three and further more there are so many independent artists out there releasing to YouTube or Apple iTune or Soundcloud on their own).

(Disclaimer: work in a music company)

Re:Update on HTML5 Video for Netflix by dasil003 on Wednesday March 22, 2017 @08:53PM (#13936576)
A lot of geeks are under the misapprehension that the studios don't know this. But actually they are not idiots, they are fully aware of the sisyphean nature and ultimate futility of DRM.

The point of enforcing DRM is not to prevent piracy, but rather to flex their market clout and demonstrate control. As long as they put up moderate barriers to ripping, and as long as they have legal sanction to suppress productized piracy, the steady stream of new must-have content allows them to throw their weight around. Licensing streaming without DRM is a slippery slope that decreases the perceived value of their content. Small distributors will do it because they need to make whatever money they can, big distributors will never do it because it damages their brand.

Re:Update on HTML5 Video for Netflix by matt_kantor on Friday March 24, 2017 @04:54PM (#13952141)
Spot on. Ian Hickson explained this very well a few years ago[0].

[0]: https://plus.google.com/+IanHickson/posts/iPmatxBYuj2

Re:Update on HTML5 Video for Netflix by grinich on Wednesday March 22, 2017 @07:37PM (#13936125)
This is like saying door locks are pointless because you can break a window and climb through.

Protecting media copyright isn't a black or white thing like crypto. It's about compromises to drive behavior and consumer spending with convenience.

Re:Update on HTML5 Video for Netflix by amelius on Wednesday March 22, 2017 @08:09PM (#13936348)
What exactly do you think this DRM will stop?

1. People who have access to the content can usually see it over and over again (when they have a subscription to a service like Netflix). DRM will do nothing here.

2. People who don't have access to the content can't even see the DRM'ed version of the file, so DRM will do nothing here either.

3. People who want to pirate (illegally distribute) the content have advanced tools and knowledge to circumvent DRM, so DRM is of no use here again.

Re:Update on HTML5 Video for Netflix by recursive on Wednesday March 22, 2017 @08:25PM (#13936438)
Whether you have access to content isn't an immutable fact of your genetics. People can freely move between groups 1 and 2. That's the whole point.

For instance, I didn't have access to netflix content, and then I signed up for a netflix account and paid them money, and now I do have access.

Re:Update on HTML5 Video for Netflix by unicornporn on Thursday March 23, 2017 @03:53AM (#13938011)
> Whether you have access to content isn't an immutable fact of your genetics. People can freely move between groups 1 and 2. That's the whole point.

So you're saying people could move to another jurisdiction to be able to watch their favorite show on Netflix? Yeah, that truly sounds like freedom to me. Or am I misinterpretating you?

Re:Update on HTML5 Video for Netflix by recursive on Thursday March 23, 2017 @05:33PM (#13944553)
You're misinterpretating me. Some people already live in jurisdictions to which Netflix permits distribution of their favorite show. Those people can decide to pay for access or not.

It's also true that some people don't live in such places. But that doesn't matter. You said that DRM serves no purpose. For some it may not. But for some people it does.

Re:Update on HTML5 Video for Netflix by pferde on Thursday March 23, 2017 @05:08AM (#13938267)
Yes, you are misrepresentating(sic!) him. The "move between groups 1 and 2" was meant as decision to start paying for a service, or to stop paying for a service, not a physical move. In other words, voting with your wallet.
Re:Update on HTML5 Video for Netflix by Silhouette on Wednesday March 22, 2017 @08:51PM (#13936571)
1. People who have access to the content can usually see it over and over again (when they have a subscription to a service like Netflix). DRM will do nothing here.

Sure it will. It will stop people writing a script to download as much as they can get away with in a single month and then cancelling since they have enough content to keep them going for several more months without paying for them.

3. People who want to pirate (illegally distribute) the content have advanced tools and knowledge to circumvent DRM, so DRM is of no use here again.

That is a big assumption, and in many cases not a correct one. The major online DRM systems today are fairly robust, and if anyone has a crack for some of them, they're keeping their cards very close to their chests. The leaks of major movies that you find on torrent sites and the like are usually from other sources.

Re:Update on HTML5 Video for Netflix by amelius on Wednesday March 22, 2017 @09:20PM (#13936713)
> Sure it will. It will stop people writing a script to download as much as they can

But the people who go through the trouble of that are exactly the people who wouldn't mind downloading pirated copies in the first place.

Re:Update on HTML5 Video for Netflix by Silhouette on Wednesday March 22, 2017 @09:30PM (#13936755)
If you're supplying digital content as a business, then usually that isn't your real problem. They weren't going to give you any more money anyway, and with the legal framework being as it is in most places today, it's frustrating to see your content ripped off but not actually worth doing much about it. Meanwhile, your real problem is probably people who will casually copy and share your content, because even if the multiplication is relatively small, those are potentially still reaching people who would otherwise pay for a legitimate copy.
Re:Update on HTML5 Video for Netflix by schrodinger on Wednesday March 22, 2017 @09:04PM (#13936621)
There's always the analog loophole. If you can watch it on your screen, you can record it.
Re:Update on HTML5 Video for Netflix by Silhouette on Wednesday March 22, 2017 @09:19PM (#13936702)
Of course, but typically quality suffers significantly, so what you get isn't as good as the original and that in itself is a deterrent for a lot of people.

Also, some modern watermarking techniques can survive conversions like this, so if anyone is making a habit of recording content from a service using watermarking and redistributing it on a scale that justifies taking serious action, it'll be pretty easy to prove who it was when the lawsuit comes up.

Re:Update on HTML5 Video for Netflix by amelius on Wednesday March 22, 2017 @10:51PM (#13937085)
> it'll be pretty easy to prove who it was when the lawsuit comes up

Perhaps. But this person can always claim that it was done by an external hacker. In fact, it can be done by an "external" hacker, and it will be if these guys are smart.

Re:Update on HTML5 Video for Netflix by Silhouette on Wednesday March 22, 2017 @11:43PM (#13937257)
I'm sure that's an appealing argument if you don't like DRM, but the reality is that someone who ripped content marked to their personal account, which server logs show did access the content in question from their usual IP address etc., is going to have a tough time convincing any court on the balance of probabilities that some unidentified bogeyman actually did it.
Re:Update on HTML5 Video for Netflix by flukus on Wednesday March 22, 2017 @09:58PM (#13936872)
> Also, some modern watermarking techniques can survive conversions like this, so if anyone is making a habit of recording content from a service using watermarking and redistributing it on a scale that justifies taking serious action, it'll be pretty easy to prove who it was when the lawsuit comes up.

How many compromised netflix accounts do you think are floating around? At some point the bits have to actually go to a display device as well, which can always be tapped.

Re:Update on HTML5 Video for Netflix by Silhouette on Wednesday March 22, 2017 @11:45PM (#13937261)
If a compromised account was used, presumably the server logs will show an unusual access pattern on that account, in particular involving the content that has leaked being accessed from an unusual location. And then presumably the person whose account was used will have to make a convincing case that they shouldn't be held responsible for access using their credentials anyway.
Re:Update on HTML5 Video for Netflix by flukus on Thursday March 23, 2017 @01:24AM (#13937568)
Ok, what if a machine is compromised (there are millions of zombie boxes out there)? Someone can gain access, do their stuff and then upload the result. Are they going to start suing grandmas with weak wifi passwords? That worked so well for the RIAA last time.
Re:Update on HTML5 Video for Netflix by Silhouette on Thursday March 23, 2017 @01:45AM (#13937626)
Then it'll be up to the person whose account was accessed to provide some evidence that something like this happened and that it wasn't their fault. That's how these things work. You go to court, you make your case and the other side makes theirs, and the court draws its conclusions and acts accordingly.

However, you don't just get to conveniently avoid taking any responsibility when there are videos being distributed that are specifically linked to an account you signed up for that clearly said you couldn't redistribute the content you got through it, just because there's some vaguely possible alternative that might have once happened somewhere maybe.

Re:Update on HTML5 Video for Netflix by boomboomsubban on Thursday March 23, 2017 @02:57AM (#13937845)
A compromised account is a vague possibility? I'm not amazing at these things, but I could probably access a WiFi network unconnected to me, mask my IP to a different location, and acquire a random Netflix account in a couple of hours. These things are likely, and wrongful lawsuits greatly damage the company while successful ones provide a minimal benefit.
Re:Update on HTML5 Video for Netflix by Silhouette on Thursday March 23, 2017 @03:11AM (#13937891)
I'm not amazing at these things, but I could probably access a WiFi network unconnected to me, mask my IP to a different location, and acquire a random Netflix account in a couple of hours.

Really? How would you do that, exactly?

If you're looking online and find camcorder copies of videos that were served to a specific customer at a specific time, as confirmed by the watermarking, and your server logs show that that stream was sent to the customer's usual IP address at the time in question, what are the odds that they were the victim of a carefully crafted hack of the kind you're implying, and not just someone who set up a camcorder to record from their own account?

Re:Update on HTML5 Video for Netflix by flukus on Thursday March 23, 2017 @03:38AM (#13937963)
> Really? How would you do that, exactly?

Wireless isn't very secure, you're mileage may vary on the encryption mechanism but here is a guide to hacking WPA networks (with WEP it takes seconds):

http://www.hackingtutorials.org/wifi-hacking-tutorials/how-t...

From there you can try a range of known exploits and gain admin access to a PC, after that it's game over, they can run what they want, when the want. There is no careful crafting necessary, the process can be largely automated.

We aren't talking camcorder copies, but exact digital replicas from the netflix stream.

Re:Update on HTML5 Video for Netflix by Silhouette on Thursday March 23, 2017 @12:50PM (#13941503)
WPA2 is reasonably secure and has been the standard for home and business WiFi for years.

In any case, merely compromising WiFi won't get you someone's Netflix account. The Netflix data itself, including the credentials, are all encrypted.

As for taking over someone's PC, that's far beyond the average pirate, and you're talking about serious criminal offences on top of mere copyright infringement at that point.

And even then, we're not necessarily talking about being able to make exact copies of the stream. The whole point of hardware-backed DRM schemes is that just because you can run software on the PC, that doesn't mean you can access the unencrypted data stream.

So again, how exactly were you planning to do this? What you're talking about is far beyond the average script kiddie or casual pirate.

Remember, we were talking about convincing a court that it was more likely that someone did all of this and that was how a watermarked copy of protected content got out than that the person whose account was used to download that content then somehow shared it. A slight possibility that professional pirates who are also expert crackers chose that particular customer to pick on and left no evidence having done so isn't likely to be very convincing.

Re:Update on HTML5 Video for Netflix by boomboomsubban on Friday March 24, 2017 @01:14AM (#13946789)
I can't figure out why you've added this ridiculous "need to use their computer" part, that would be necessary for a successful lawsuit but suing random Netflix users will look terrible even if the court clears them in the end. But OK...

WPA2 is reasonably secure, but most home instances aren't set up well. They often have WPS enabled or a guessable password. Plus weaker set ups are still easy to find. Once you're on, redirect Netflix to a site to grab their info, record the stream from a computer outside their house. This is needlessly complex for what is needed, find a compromised Netflix(+email?), record.

Re:Update on HTML5 Video for Netflix by Silhouette on Friday March 24, 2017 @09:07AM (#13948630)
Netflix serves over HTTPS and uses HSTS. Under most circumstances, you aren't going to be able to MITM them and "grab their info" even if you've compromised their WiFi.

You keep coming up with these claims about how easy this is, yet you also keep missing basic technical points about the system actually works. As I've said before, if there is actual evidence that someone's account was compromised then they can produce that as part of their defence in court. However, if content that is watermarked to a specific account turns up all over the Internet, that is evidence suggesting that the person in question has infringed copyright, and that does need a real defence if the rightsholder chooses to take legal action accordingly.

Re:Update on HTML5 Video for Netflix by boomboomsubban on Friday March 24, 2017 @12:16PM (#13949933)
Yes, and people are so great at making sure they access https addresses and never ignore a "this may not be secure" warning.

And you're still ignoring the major parts. What someone actually needs to do is much easier than all this, and Netflix has already lost if they end up in court with an innocent person.

If you want me to prove accounts have been compromised, look at all the account breaches over the past few years, think of how many reuse passwords.

Re:Update on HTML5 Video for Netflix by flukus on Thursday March 23, 2017 @03:15AM (#13937904)
> That's how these things work. You go to court, you make your case and the other side makes theirs, and the court draws its conclusions and acts accordingly.

Currently the burden of evidence is far too low. Something being done with my account, or even my machine is not evidence that I've done anything wrong.

> However, you don't just get to conveniently avoid taking any responsibility when there are videos being distributed that are specifically linked to an account you signed up for that clearly said you couldn't redistribute the content you got through it

How are we supposed to take responsibility for the actions of others? Should we be liable for crimes committed due to the insecurity of home networks? If so the computer industry has much bigger problems than DRM.

Re:Update on HTML5 Video for Netflix by Silhouette on Thursday March 23, 2017 @02:33PM (#13942684)
Something being done with my account, or even my machine is not evidence that I've done anything wrong.

Yes, it is. It may not be absolute proof, but it most certainly is strong evidence.

How are we supposed to take responsibility for the actions of others?

Hopefully, you don't have to. But you also don't get to just invent some hypothetical bogeyman and use that as an excuse to ignore real evidence.

Re:Update on HTML5 Video for Netflix by infinite8s on Wednesday March 22, 2017 @09:15PM (#13936689)
If you discount the cost of your time to zero. Otherwise it's not even worth a minimum wage job.
Re:Update on HTML5 Video for Netflix by flukus on Wednesday March 22, 2017 @09:55PM (#13936865)
It only needs to be done by one person, not every viewer.

And yes, the value of much of my time is effectively zero. The same is true for most people.

Re:Update on HTML5 Video for Netflix by MBCook on Wednesday March 22, 2017 @10:36PM (#13937017)
That's why we have laws to apply negative externalities like very large jail sentences if you're caught distributing a file that you created by taping a movie off-screen.
Re:Update on HTML5 Video for Netflix by flukus on Wednesday March 22, 2017 @10:53PM (#13937092)
Local solutions to global problems that don't even work locally. Those large jail sentences also place a lot of externalities on the rest of society.
Re:Update on HTML5 Video for Netflix by MBCook on Thursday March 23, 2017 @03:49PM (#13943531)
I agree. My comment was not meant as an endorsement, simply a statement I think that's how they've 'solved' that issue.
Re:Update on HTML5 Video for Netflix by taneq on Wednesday March 22, 2017 @10:56PM (#13937101)
You missed:

2b. People who don't have access to the content, but want to watch it for free.

Re:Update on HTML5 Video for Netflix by jimktrains2 on Wednesday March 22, 2017 @08:10PM (#13936355)
> It's about compromises to drive behavior and consumer spending with convenience.

You mean grabbing a DRM-free (i.e. pirated) copy so that I can watch it at my leasure and on devices of my choosing, even if I have access to it via other legit means?

Re:Update on HTML5 Video for Netflix by notjoemama on Thursday March 23, 2017 @04:25PM (#13943907)
Any free or low cost run-of-the-mill capture software renders DRM useless. If it's made out of bits, you can't ensure ownership after redistribution. In an environment like this people pay because it is quality content and access is easy. The publishers business model needs to get with the times, not strong arm browser vendors into adhering to their archaic requirements. I'm personally sick of hearing about this DRM war. There are so many more things to be concerned with. ◔̯◔
Re:Update on HTML5 Video for Netflix by accountface on Thursday March 23, 2017 @12:00AM (#13937296)
Do you lock the front door to your house when you leave?
Re:Update on HTML5 Video for Netflix by matt4077 on Wednesday March 22, 2017 @06:44PM (#13935727)
Browser makers have plenty leverage. A Firefox user watching Netflix will, and this is a tautology, be worse off if they cannot continue doing so. That may lead to people switching to other browsers more often than dropping Netflix subscriptions, but the costs for Netflix wouldn't be 0, and may even be substantial considering the population of people using Firefox is self-selected to those placing a high value on openness.

If Chrome were to ship without DRM, Netflix would cave faster than you can say "thepiratebay". See what happened to flash when it wasn't supported on the iPhone. There are millions of archived predictions of Apple's demised in forums such as this, but even though they had 20% of the market at peak, they easily killed flash.

Unfortunately, Google has an interest in DRM for its own sake. This may serve as a welcome reminder that the awesome job they have done with Chrome is a result of an alignment of interest between them and the web community: they need the open web to compete against iOS and the closed Facebook ecosystem. That situation may not last forever.

I'm quite happy to have had RMS and other true-believing ascetic martyrs shaping the techno-centric fantasy world we're living in. If your defeatist attitude had prevailed in the early years, we'd all be writing VBScript to animate the spinning gif on homepage.doc – yes, Microsoft once tried to push .doc to replace .html.

I also think the music industry has proven quite clearly that you'll have a lot more success with carrots than sticks. I honestly don't know what benefit they think they're getting from DRM, considering all their material somehow ends in a .torrent anyway.

Re:Update on HTML5 Video for Netflix by tptacek on Wednesday March 22, 2017 @06:58PM (#13935839)
Not only is it not true that Netflix would cave if they didn't have native browser support, but we know it's not true, because Netflix for years relied on plugins to deliver over browsers. Meanwhile, every year that passes, browsers have less leverage as more Netflix subscribers get their content either on set-top boxes or mobile devices (where Netflix has total end-to-end control), and fewer are stuck with browsers.
Re:Update on HTML5 Video for Netflix by danso on Wednesday March 22, 2017 @07:20PM (#13935996)
Have to say that this mirrors my experience. Netflix as an app is ubiquitous -- it's on virtually every electronic device I have, from smart TV to Chromecast to phone to tablet to Wii U and PS4. I believe I have Flash specifically updated and enabled for Netflix (or one of the video services, HBO maybe?). If Netflix required a specialized Mac OS X, I probably would install it. I imagine browsers have less leverage when it comes to the average non-technically inclined user.
Re:Update on HTML5 Video for Netflix by vacri on Thursday March 23, 2017 @12:17AM (#13937339)
So the response becomes "so what?". Oh no, proprietary videos will move to proprietary apps, and free videos would remain in the browser. People aren't going to stop using browsers for everything else just because they watch youtube vids on the youtube app. Browsers just aren't going to suffer if proprietary videos move elsewhere - it doesn't matter whether Netflix caves or not. It's not like the rest of the world-wide-web that doesn't rely on DRM'd electronic files is going to follow suit and leave the browser.
Re:Update on HTML5 Video for Netflix by syshum on Wednesday March 22, 2017 @09:07PM (#13936636)
>> because Netflix for years relied on plugins to deliver over browsers.

They still do, you have to have the Widevine PLUGIN and the Open H264 PLUGIN to play content on netflix

It is a pure myth that eme does not have plugins

>browsers have less leverage as more Netflix subscribers get their content either on set-top boxes or mobile devices (where Netflix has total end-to-end control), and fewer are stuck with browsers.

I am fine with that, I would rather have that than an HTML5 standard that requires binary plugins to work. I would rather have that then the risk EME brings to extent beyond video content to start having entire pages plugin bases, fonts DRM encumbered, and 100's of other consequences to this move that are coming

Re:Update on HTML5 Video for Netflix by tptacek on Wednesday March 22, 2017 @09:12PM (#13936662)
I agree that it's a myth that EME doesn't have plugins. What EME does is reduce the scope of those plugins.

HTML5 does not require binary plugins in order to work.

Re:Update on HTML5 Video for Netflix by syshum on Wednesday March 22, 2017 @09:26PM (#13936737)
>>HTML5 does not require binary plugins in order to work.

Yet... EME opens the door, and only the Naive believe EME will start and stop at Video Content.

There are already requests for ebooks,and fonts. Images and and even web content itself is not far behind

>I agree that it's a myth that EME doesn't have plugins. What EME does is reduce the scope of those plugins.

Yes and no, if you buy in to the "perfect sandbox" myth then sure, but to believe CDM's are secure is laughable. There are too many hooks into the hardware, there as to be in order to bypass the user, for it to actually be secure.

No the security is more protecting the CDM from the user, not protecting the user from the CDM

Re:Update on HTML5 Video for Netflix by onli on Wednesday March 22, 2017 @07:30PM (#13936064)
Netflix would not have the option anymore to use plugins now. They are gone, and browser would not bring them back just for Netflix.
Re:Update on HTML5 Video for Netflix by tptacek on Wednesday March 22, 2017 @07:33PM (#13936088)
In which case Netflix would simply make available a "native" application for Windows and OS X, like Slack does, and everybody loses (except Netflix).

Proof: this is exactly what Amazon does with Kindle content.

Re:Update on HTML5 Video for Netflix by Nexxxeh on Wednesday March 22, 2017 @07:36PM (#13936122)
Netflix already have a Native Windows app. I don't know if it's still the case, but it was the only way to get 5.1 audio on PC.

The app and Edge are the only two PC 4k viewing options. And both require a Kaby Lake CPU.

Re:Update on HTML5 Video for Netflix by scarface74 on Wednesday March 22, 2017 @08:37PM (#13936505)
Well. Look what happened when Apple refused to support Flash. Did Netflix all the sudden support HTML 5 H.264 video in the browser in a cross platform way? No. They wrote a proprietary app for iOS. Would more people have been served if Netflix could have had a standard that worked across all browsers that would have allowed Android users to use Netflix 9 months sooner?

Firefox users were already viewing Netflix with a Silverlight plug in. Would you rather be stuck with an MS solution or one with input from various companies.

As far as the music industry getting rid of DRM it had nothing to do with "carrot vs. sticks." The real history:

2003: itunes was introduced with DRMd music that only worked with the iPod.

late 2006: other companies tried to sell drmd music but since it didn't work with the iPod, none of them could gain traction.

Early 2007: the music industry asked Apple to license FairPlay. Apple refused. As an alternative, Jobs said that if the music industry would license their music without DRM, any music sold anywhere would be compatible with any player. His "Thoughts on Music" essay giving this alternative was widely publicized in 2007 (https://www.google.com/amp/readwrite.com/2007/02/06/steve_jo...) and was on the front page of Apple.com

The music industry wanted variable priced music, the ability to bundle songs, a cut of every iPod sold, and a deposit to insure against losses due to privacy. Apple refused all of those conditions.

To both decrease Apple's dominance in the market and to increase the competition, the music industry allowed all of Apple's competitors who would bow to their demands to offer DRM free music. Apple was only able to sell DRM free music by EMI and independent labels and they weren't allowed to sell music at all over cellular for the then new iPhone.

2008: Apple and the music industry came to terms and Apple started selling DRM free music.

The only reason the music industry allowed DRM free music was to decrease Apple's dominance.

Re:Update on HTML5 Video for Netflix by Silhouette on Wednesday March 22, 2017 @09:10PM (#13936650)
That may lead to people switching to other browsers more often than dropping Netflix subscriptions, but the costs for Netflix wouldn't be 0

Maybe not, but since they already provide their content via various apps anyway, it's hardly a leap to them providing a dedicated, proprietary player on other platforms as well.

If Chrome were to ship without DRM, Netflix would cave faster than you can say "thepiratebay". See what happened to flash when it wasn't supported on the iPhone.

Flash continued to be the dominant platform for online video for several more years, major sites didn't work on Apple devices, and competitors literally ran campaigns with lines like "See the whole Internet"? I'm not sure you're making the point you intended to here.

If your defeatist attitude had prevailed in the early years, we'd all be writing VBScript to animate the spinning gif on homepage.doc – yes, Microsoft once tried to push .doc to replace .html.

This is just silly. At no point in the history of the Web, from its earliest days growing out into public awareness, was there any serious prospect of anything like that happening. Whether we're really better off with JS having become the dominant front-end language is a different question, but I digress.

I also think the music industry has proven quite clearly that you'll have a lot more success with carrots than sticks.

The music industry can sell its primary content at sub-dollar prices and still make a reasonable profit. Almost no-one else can.

Re:Update on HTML5 Video for Netflix by josteink on Thursday March 23, 2017 @02:39AM (#13937799)
> If Chrome were to ship without DRM, Netflix would cave faster than you can say "thepiratebay".

True or not true, this is just not going to happen.

Google was the single browser pushing DRM into the web-standards to begin with. They were the first to ship with this enabled.

And Google already has a vested interest in DRM. They have their own media-services now, remember...

Re:Update on HTML5 Video for Netflix by franciscop on Wednesday March 22, 2017 @06:30PM (#13935631)
I don't agree with "people want to watch what they want to watch."

IMO the 2005-2015 wave of pirated content was due to the exact opposite; users (people in the living room) not going the extra literal mile to buy/rent a DVD.

With the coming of Spotify & Co the music pirate scene has pretty much died off and it's because the physical CDs are replaces by something orders of magnitude easier.

Same thing is happening with video content now that most houses have the capability of streaming it.

What people want to do after work is to sit in the sofa and press "play". They don't want to start installing software.

Re:Update on HTML5 Video for Netflix by e40 on Wednesday March 22, 2017 @06:51PM (#13935788)
I don't agree with "people want to watch what they want to watch."

I have quite a few data points that say you are flat wrong about that. I would add to this: people watch what they want to watch and how they want to watch it.

I've literally downloaded HBO shows even though I'm an HBO Now subscriber. The Roku HBO Now app is so horrible, I just hate using it.

Re:Update on HTML5 Video for Netflix by jameskegel on Wednesday March 22, 2017 @07:05PM (#13935900)
I agree with this. My frustration is not only HBO, but also UFC. I pay for Fight Pass because I love the sport, and I want to support it, but my Roku experience is so bad that I found myself looking for other means of consuming it.
Re:Update on HTML5 Video for Netflix by e40 on Wednesday March 22, 2017 @07:09PM (#13935928)
Me, too (on the UFC)! I never use it. I just pay them because I download the content elsewhere.
Re:Update on HTML5 Video for Netflix by mastazi on Wednesday March 22, 2017 @07:21PM (#13936006)
> I have quite a few data points

Show us the data points or it didn't happen.

I am highly sceptical about your statement and am convinced that most people are willing to pay in exchange for ease of use and convenience.

Re:Update on HTML5 Video for Netflix by Silhouette on Wednesday March 22, 2017 @08:45PM (#13936547)
Show us the data points or it didn't happen.

Sorry, that's not how it works. The situation is what it is, and the people with hard data are going to act on it, and your scepticism does not change any of that.

As another person with business interests that produce custom video content for niche markets, I have shifted significantly in my attitude towards DRM since discovering how real people behave. We tried to be nice and considerate and not limit access to the video files with DRM. We did this while producing new, original content unlike anything else out there for our subscribers. We held out for several years.

But we got to the point where we were spending so much time dealing with that that it was directly affecting our ability to deliver for the vast majority of our customers who respected the rules. We were losing out on revenues, our genuine customers were losing out on new content, and the only people winning were the freeloaders and the people enjoying our content on other people's sites/channels/whatever.

My concern about DRM affecting legitimate customers if something goes wrong is as strong as ever, so we still take a cautious approach and err on the side of being nice. However, I have no qualms at all about DRMing every single asset we have, and I have no qualms whatsoever about deploying the lawyers against people who knowingly, maliciously and without remorse rip off the results of several years of hard work and share them with others.

As a final point, none of this negates your point that making access convenient and prices reasonable improves conversion rates. But I see little evidence that this helps if part of your potential market is finding your content totally free from someone else first.

Re:Update on HTML5 Video for Netflix by bearcobra on Wednesday March 22, 2017 @06:41PM (#13935713)
> What people want to do after work is to sit in the sofa and press "play". They don't want to start installing software.

Maybe, but Roku, Fire Sticks, Apple TV & Chromecast all seem to indicate that people are willing to put in some effort to set up a platform for video consumption. That combined with pre-installed solutions like iTunes and Microsoft Movies & TV give users some pretty easy options to compete with their browser.

Re:Update on HTML5 Video for Netflix by pdeuchler on Wednesday March 22, 2017 @06:52PM (#13935791)
I think we lost the ability to make fun of RMS once the Snowden revelations come out. Regardless...

>> It is a techno-centric fantasy to think that browser makers have even a modicum of leverage here

You realize the world's largest browser vendors are Google, Apple, and Microsoft... right?

>> EME is a ideological compromise, sure, but it's a net benefit to the open web since its scope is small and it maintains the overall schema of web standards.

Ahhh yes, the classic "compromise some of my morals to save the rest of them". Works every time.

Re:Update on HTML5 Video for Netflix by tptacek on Wednesday March 22, 2017 @06:57PM (#13935835)
Google and Apple have very little leverage. If even one major studio withdrew all their content from Apple and only made it available on Netflix, Apple could potentially lose millions of subscribers. People want to watch what they want to watch.
Re:Update on HTML5 Video for Netflix by pdeuchler on Wednesday March 22, 2017 @07:04PM (#13935894)
I do not buy this for several reasons:

1) Content production is rapidly moving to an "in house" model, where subscribers are more heavily influenced by original and exclusive content

2) I doubt there would be large transfers of subscribers, more a slight depression across the board and large increases in piracy, as we saw rather distinctly with the early days of music providers (like before itunes early days)

3) Google and Apple each by themselves are worth the entirety of Hollywood many times over. I think it's less them having little leverage, and more them playing a longer game and not caring about DRM battles in the short term.

Re:Update on HTML5 Video for Netflix by tptacek on Wednesday March 22, 2017 @07:21PM (#13936010)
Content is indeed moving in house, and all the companies that are doing in-house production in any meaningful way DRM their content. So what does this matter?
Re:Update on HTML5 Video for Netflix by CaptSpify on Wednesday March 22, 2017 @07:45PM (#13936184)
> People want to watch what they want to watch.

You keep using this phrase. Doesn't that also suggest that, if given enough trouble, they will just pirate that content instead? DRM has shown to do very little to stop that, so why continue pretending that it does.

Re:Update on HTML5 Video for Netflix by kelnos on Wednesday March 22, 2017 @08:43PM (#13936529)
> You keep using this phrase. Doesn't that also suggest that, if given enough trouble, they will just pirate that content instead? DRM has shown to do very little to stop that, so why continue pretending that it does.

Yes, but, in general, trouble has been decreasing, and so has the need to pirate. I would argue that there are only three kinds of people who pirate anymore:

1. People who want a local copy of the content that can't be taken away (e.g. Netflix pulling a title, or just canceling one's Netflix account).

2. Content that is so long-tail that it's not available for streaming from one of the major players that have decent device/playback support.

3. People who are so far in the "openness"/ownership camp that they would refuse to buy into a service like Netflix unless they provided #1 (DRM-free, of course).

The fourth kind of person is mostly gone: the person who doesn't need 1-3, but finds the options for playing content legally to be too cumbersome, or who can't find a legal player for their chosen viewing device. (Essentially, they've been "given enough trouble".)

If Netflix were to drop all browser support, and release native apps for Windows and macOS, there would be an increase of that fourth kind of person (Linux users, mainly, though I wouldn't put it past Netflix to release a Linux client too), but that wouldn't change the situation for the 1-3 type people, who are the bulk of pirating community.

I really think, for the vast majority of viewers, having a native Windows/MacOS app, plus native apps for Android/iOS, is plenty. Taking away browser support isn't going to increase piracy by any measurable amount.

Re:Update on HTML5 Video for Netflix by cstejerean on Wednesday March 22, 2017 @10:35PM (#13937014)
You missed be largest category for pirating: people who want to watch new releases before they are available on Netflix, but cannot afford $20 to see it in theaters, or $15-20 to buy it digitally before it becomes available on Netflix. The window before a movie is in theaters until it becomes available on Netflix can be huge, and many people don't want to wait that long. I usually prefer watching movies in theaters (I like the experience) and if I miss it in theaters I will gladly buy it through iTunes, and even then I usually have to wait 3+ months before a movie I missed in theaters is available for purchase. I don't pirate because I wouldn't even know where to start but I can say I've been tempted to look into it just so I can watch a movie today rather than 3 months from now (and I would gladly buy it even after pirating it).
Re:Update on HTML5 Video for Netflix by Kliment on Thursday March 23, 2017 @02:33AM (#13937779)
4 is still a thing because of exclusives and regional restrictions meaning that you need a growing number of subscriptions to access a chosen subset of content, and it might not be available at all in your region
Re:Update on HTML5 Video for Netflix by Karlozkiller on Wednesday March 22, 2017 @07:52PM (#13936235)
> > People want to watch what they want to watch.

> You keep using this phrase. Doesn't that also suggest that, if given enough trouble, they will just pirate that content instead?

Not to point any fingers, but I can confirm that this happens, a lot.

But regardless of my personal views of DRM and its efficiency, kudos to Netflix for targeting Linux as a platform, even if they do it for their own pockets' sake.

Re:Update on HTML5 Video for Netflix by pdog on Thursday March 23, 2017 @09:04AM (#13939362)
> You might as well say that anyone who is not living an RMS-sanctioned ascetic technology lifestyle is hurting the cause of free software everywhere.

"The reasonable man adapts himself to the world; the unreasonable one persists in trying to adapt the world to himself. Therefore all progress depends on the unreasonable man."

―George Bernard Shaw, Man and Superman (1903) "Maxims for Revolutionists"

Re:Update on HTML5 Video for Netflix by khedoros1 on Wednesday March 22, 2017 @06:27PM (#13935602)
This is all true. What has happened is probably the best out of a set of crappy options. It's only a net benefit compared to the other non-fantasy possibilities, though. EME is more something to be resigned to than happy about.

> It shouldn't be considered worse than proprietary plugins with arbitrary scope.

True. Proprietary plugins with limited scope are better than proprietary plugins with arbitrary scope, all other things being equal.

Re:Update on HTML5 Video for Netflix by josteink on Thursday March 23, 2017 @02:33AM (#13937778)
> Sorry, but as someone who spent nearly a decade founding and building a premium content VOD service, and 6 of those years fighting fiercely against DRM and making great content available without DRM, I have both the knowledge and moral authority to say that you're living in a fantasy world. .... EME is a ideological compromise, sure, but it's a net benefit to the open web

If you need DRM, nobody is forcing you to create a solution based on a open-platform. Go make a OS and platform-specific app instead.

I mean... That's what EME makes browsers and web-sites into anyway. You now have so called "web-sites" where your OS and platform has to be "supported".

And then you might as well make a native app. Like Netflix does. Like Spotify does. Like everyone does.

We don't need DRM in our open standard.

Re:Update on HTML5 Video for Netflix by flukus on Wednesday March 22, 2017 @07:34PM (#13936093)
I think you're living in fantasy world where DRM actually works. Not once has DRM prevented me from watching a netflix show, it's only prevented me from watching it on netflix.
Re:Update on HTML5 Video for Netflix by bunderbunder on Wednesday March 22, 2017 @07:55PM (#13936253)
DRM works to do the only thing it was ever really meant to do, which is give copyright holders warm fuzzies so that they're more willing to put their content up for sale on legal channels that don't require much in the way of technical savvy to use. Which means that it also works for the vast majority of consumers, since that's all they really ever wanted in the first place.

The whole bit about preventing people from copying content is just a feel good story that's told to TV executives in order to further DRM's primary purpose.

Re:Update on HTML5 Video for Netflix by Karlozkiller on Wednesday March 22, 2017 @07:59PM (#13936289)
> I think you're living in fantasy world where DRM actually works. Not once has DRM prevented me from watching a netflix show, it's only prevented me from watching it on netflix.

Yes, yes, and yes. DRM has blocked me from Netflix as a Linux user (not anymore obviously), blocked me from games due to bugs in the DRM in windows and or rootkits, and blocked me because the DRM does not work in Linux while the actual game does. And often you can find DRM free piracy versions.

DRM is a pestilence that blocks legitimate use.

Re:Update on HTML5 Video for Netflix by azinman2 on Wednesday March 22, 2017 @09:35PM (#13936772)
There's a difference between deterring (upping the bar) and making it impossible. See CIA guidelines on writing malware in the recent leak.
Re:Update on HTML5 Video for Netflix by flukus on Wednesday March 22, 2017 @11:05PM (#13937134)
It only deters people that were already detered by their own technological inability, the ones that don't know what files are. Everyone else can circumvent it by grabbing a pirate bay version.
Re:Update on HTML5 Video for Netflix by dasil003 on Wednesday March 22, 2017 @09:00PM (#13936603)
Wrong, neither I nor anyone in industry believes DRM "works" in that sense. You're misunderstanding the purpose of DRM, see my other comment: https://news.ycombinator.com/item?id=13936576
Re:Update on HTML5 Video for Netflix by flukus on Wednesday March 22, 2017 @09:08PM (#13936640)
I don't understand your clarification either:

> The point of enforcing DRM is not to prevent piracy, but rather to flex their market clout and demonstrate control.

I don't see how DRM does this. The amount they've spent compared to the results they've got seems to demonstrate a complete lack of control to me.

>As long as they put up moderate barriers to ripping, and as long as they have legal sanction to suppress productized piracy, the steady stream of new must-have content allows them to throw their weight around.

What does DRM do to prevent productized piracy?

>Licensing streaming without DRM is a slippery slope that decreases the perceived value of their content.

So the choose to increase the real value of it instead?

Re:Update on HTML5 Video for Netflix by greggman on Wednesday March 22, 2017 @10:31PM (#13937002)
All evidence points to the opposite. Browser usage has expanded every single day since they were introduced ~26 something years ago. All that time there was no DRM in the browser.

Proprietary plugins have been the source of the majority of exploits. EME will be no different

Re:Update on HTML5 Video for Netflix by shmerl on Thursday March 23, 2017 @12:31AM (#13937386)
> all that would mean is that premium content would not be available in browsers

I doubt that. All browsers boycotting DRM freaks would cause more rational heads in the media industry to push against those who insist on DRM, and it could become the tipping point in ridding video of this disease.

They themselves admit, they don't mind it, but don't want to be first to disrupt the status quo. So cowardice of browser makers only advanced the problem. But I agree that Firefox alone couldn't change things. This had to be a combined effort. But others simply either have no guts to stand against DRM, or are themselves dirty with it.

Re:Update on HTML5 Video for Netflix by Eric_WVGG on Thursday March 23, 2017 @12:31AM (#13937389)
More people already watch movies on internet-connected set top boxes like Apple TVs and PS4s, or i-devices, than computers.

At worst Netflix could have resorted to desktop apps for their movies. DRM doesn't need to be on the web.

Re:Update on HTML5 Video for Netflix by beefsack on Thursday March 23, 2017 @12:43AM (#13937430)
> Even if all browsers banded together and refused, all that would mean is that premium content would not be available in browsers, and that would lead to a significant devaluation of the web in favor of proprietary apps

Not everyone sees this as a bad thing. Horses for courses; the web doesn't have to be the platform for everything.

Re:Update on HTML5 Video for Netflix by zzalpha on Wednesday March 22, 2017 @07:20PM (#13935994)
tl;dr Content is king.

And you're absolutely right.

Re:Update on HTML5 Video for Netflix by throwaway91111 on Wednesday March 22, 2017 @11:31PM (#13937214)
Any evidence?
Re:Update on HTML5 Video for Netflix by frik on Thursday March 23, 2017 @01:53AM (#13937647)
EME is a binary blob from Adobe. Welcome again the Flash days - not.
Re:Update on HTML5 Video for Netflix by miclill_kit on Thursday March 23, 2017 @03:11AM (#13937889)
>...I have both the knowledge and moral authority...

So, you are god then?

Re:Update on HTML5 Video for Netflix by ReverseCold on Wednesday March 22, 2017 @06:39PM (#13935696)
Someone can fork FF though and make it so that the DRM looks like it's there to the websites it visits, but it isn't really there. There's no way DRM can't be removed if I own the device that can play it.
Re:Update on HTML5 Video for Netflix by bubblethink on Wednesday March 22, 2017 @06:56PM (#13935827)
You don't understand how this works. Firefox just provides some APIs that the DRM blob can use. All the decryption is done by the blob, not Firefox. You can reverse engineer the blob itself to an extent, but that will also become impossible with SGX (hence 4k on kabylake + edge only).
Re:Update on HTML5 Video for Netflix by Rusky on Wednesday March 22, 2017 @08:53PM (#13936574)
What's to stop someone reverse engineering the blob before it's loaded into an SGX enclave? I don't understand it very well so I could be missing something, but wouldn't that at least let someone document how the DRM works even if not running their own implementation?
Re:Update on HTML5 Video for Netflix by bubblethink on Wednesday March 22, 2017 @11:54PM (#13937279)
It would be of no use (and the code can also be encrypted for additional obfuscation). There is no private data in the blob. The blob communicates to mothership once it's safe inside the enclave, and that's when sensitive data is transmitted over an encrypted channel which only the blob can decrypt inside the enclave.
Re:Update on HTML5 Video for Netflix by MBCook on Wednesday March 22, 2017 @10:41PM (#13937035)
We still have the good old DMCA to make sure that anyone who does do that kind of thing could be punished to a ridiculous extent.
Re:Update on HTML5 Video for Netflix by ndesaulniers on Wednesday March 22, 2017 @09:42PM (#13936799)
Digital signatures. Not that I actually know how it's implemented, but I would expect someone like Netflix to pay Intel for the build infrastructure to be able to build signed blobs that the SGX will load.

The "someone" in your hypothetical can modify the blob, but then they won't be able to resign the blob, so SGX will fail to load it.

Re:Update on HTML5 Video for Netflix by flukus on Wednesday March 22, 2017 @08:48PM (#13936563)
Can't you just run in an emulator to get the blob? It looks like qemu was the first to support SGX: https://en.wikipedia.org/wiki/Software_Guard_Extensions
Re:Update on HTML5 Video for Netflix by bubblethink on Wednesday March 22, 2017 @11:56PM (#13937284)
No, that's all fine for mucking around and developing apps, but actual SGX needs attestation which the emulator can't fake. That's the whole point of SGX.
Re:Update on HTML5 Video for Netflix by flukus on Thursday March 23, 2017 @06:16AM (#13938550)
But how does that remain a secret when the browser can MitM everything between the CPU and the web?
Re:Update on HTML5 Video for Netflix by bubblethink on Thursday March 23, 2017 @05:36PM (#13944592)
There is a hardware-based secret which emulators cannot obtain or fake. That breaks the attestation chain. At the heart of it, there is some stuff that only your processor can do and not you the user even though you may have full control over the operating system. The OS is in SGX's threat model.
Re:Update on HTML5 Video for Netflix by ReverseCold on Thursday March 23, 2017 @10:07PM (#13946000)
Oh, apparently I don't. Still though, it should be 100% possible to circumvent it given that it's playing on the device.
Re:Update on HTML5 Video for Netflix by coldtea on Wednesday March 22, 2017 @07:19PM (#13935993)
>Someone can fork FF though and make it so that the DRM looks like it's there to the websites it visits, but it isn't really there.

No, they can't. The DRM will have to be there, or the content (as is from the website) wont play.

>There's no way DRM can't be removed if I own the device that can play it.

There are several ways (including recording the analog signal if it comes down to that). But not any way of "make it so that the DRM looks like it's there to the websites it visits, but it isn't really there"

Re:Update on HTML5 Video for Netflix by jasonmp85 on Wednesday March 22, 2017 @03:16PM (#13933833)
Yes, the world was better when Flash and Silverlight were the media of choice for delivering video.
Re:Update on HTML5 Video for Netflix by JoshTriplett on Wednesday March 22, 2017 @03:24PM (#13933919)
It was indeed, since people had started recognizing the problems with Flash and Silverlight, and they'd have been much easier to kill off.

DRM should have stayed second-class, leaving the way open for competitors to offer a first-class web experience as long as they left DRM behind.

Re:Update on HTML5 Video for Netflix by cmsimike on Wednesday March 22, 2017 @04:22PM (#13934495)
> leaving the way open for competitors to offer a first-class web experience as long as they left DRM behind.

Competitors already exist in this area. Here is GoG's listening of DRM-free movies: https://www.gog.com/movies?sort=bestselling&page=1

It is very rare that I find something I want to watch here, where as the content I generally want to watch, sadly, exists behind a DRM-wall.

Services/competitors are a dime a dozen, but the issue is driving users to your service, and I don't believe users will run to watch content they don't want to watch just because it is DRM free. I also don't feel like we will force content creators to go DRM free since, as we're seeing, everyone is releasing their own streaming service, which would include DRM.

Re:Update on HTML5 Video for Netflix by mozumder on Wednesday March 22, 2017 @04:46PM (#13934760)
Sorry, but Hollywood has the upper hand here.

Hollywood has no desire to enter an open platform. They're completely happy if none of their movies are online, ever. Really. They already have a massively profitable distribution system in the theaters.

The problem is that people want to watch Hollywood movies on their computer, including people that use Linux. So what do you tell those people to do? Tell them run Windows? Have them go watch it in the theater? And they have copyright controls that can force offline sites that host copyrighted content in various countries.

So DRM is the tech industry's way to kiss these people ass. It may be flawed or may not work, but it's still ass-kissing. They're the artists, they get to decide what they do with their art. The consumer has no right to an artists creation. Their only choice is to pay up or ignore it.

And you'll find that this happens to other art mediums as well. There are many, many art galleries that won't sell certain works of art if they deem your ownership as insufficient. Literally - the customer is wrong.

Re:Update on HTML5 Video for Netflix by technofiend on Wednesday March 22, 2017 @05:01PM (#13934914)
That's true but Hollywood has been dead wrong so many times it's laughable. They've been dragged kicking and screaming from one giant pile of money to the next. Don't forget the former head of the MPAA Jack Valenti's testimony to Congress in 1982:

>We are facing a very new and a very troubling assault on our fiscal security, on our very economic life and we are facing it from a thing called the video cassette recorder and its necessary companion called the blank tape. And it is like a great tidal wave just off the shore. This video cassette recorder and the blank tape threaten profoundly the life-sustaining protection, I guess you would call it, on which copyright owners depend, on which film people depend, on which television people depend and it is called copyright.

But hey if Hollywood wants to refund every purchase I made adjusting for inflation and with interest of VCRs, LaserDisc Players, DVD Players, BluRay players and all the titles I bought on them over and over then fine let's go back to you can only ever see a movie in a theatre.

Yes I realize DVD and BluRay have DRM but there was just as much wailing and gnashing of teeth over those media when introduced and each one was more profitable than the last and remain so even though their DRM is now broken. Contrast that with the failed DIVX platform and you can see what consumers want versus what Hollywood does are very much out of sync.

Re:Update on HTML5 Video for Netflix by abecedarius on Wednesday March 22, 2017 @05:09PM (#13934994)
People used to say the same about music before iTunes went DRM-free. In the long run, universal computers have far more value than audiovisual media. And you can explain what Hollywood wants without taking their side.
Re:Update on HTML5 Video for Netflix by vinceguidry on Wednesday March 22, 2017 @06:56PM (#13935826)
Music is a different animal. I can listen to a piece of music hundreds of times. I'll only watch a movie once, even the most diehard will only watch a movie at most dozens of times. I'm going to notice restrictions on my music way way sooner than I'll notice them on my movies. My only real objection to DRM on movies is philosophical, while my objection to DRM in music is practical, as in, I'll pirate my music if I can't move it around.
Re:Update on HTML5 Video for Netflix by WizzleKake on Wednesday March 22, 2017 @04:57PM (#13934872)
Their only choice is to pay up or ignore it.

They can pirate it too, which is often a superior user experience in that the user can keep the file, move it to a different device, watch without arcane restrictions, etc.

Re:Update on HTML5 Video for Netflix by JoshTriplett on Wednesday March 22, 2017 @06:01PM (#13935408)
> Sorry, but Hollywood has the upper hand here.

Look at Netflix and others who are starting to build alternatives to that ecosystem (in addition to working with it for existing content). If DRM remained second-class, maybe the next such alternative would loosen its stranglehold a bit to gain a broader audience and reduce friction.

Re:Update on HTML5 Video for Netflix by chc on Wednesday March 22, 2017 @08:07PM (#13936338)
The dominance of a distribution platform is largely determined by the content it offers. If you aren't willing to play ball but the competition is, guess who gets the content?
Re:Update on HTML5 Video for Netflix by yuhong on Wednesday March 22, 2017 @04:49PM (#13934796)
I wonder why Hollywood was taken over by lawyers in the first place. Yes, I am going back to before Sony vs Universal.
Re:Update on HTML5 Video for Netflix by pjc50 on Wednesday March 22, 2017 @05:16PM (#13935053)
Hollywood got its start in escaping Edison's patent lawyers (and hired goons); that's part of why it's on the west cost in the first place.
Re:Update on HTML5 Video for Netflix by ethbro on Wednesday March 22, 2017 @05:02PM (#13934920)
For the same reason that most fields eventually attract lawyers - Hollywood was making lots and lots of money.
Re:Update on HTML5 Video for Netflix by yuhong on Wednesday March 22, 2017 @05:43PM (#13935287)
Which makes me more interested in more details on why.
Re:Update on HTML5 Video for Netflix by blitmap on Wednesday March 22, 2017 @05:08PM (#13934977)
The problem is DRM has been used for more than digital rights management. We've seen it used to surveill the user and collect information - and restrict actions on the users' computer when it thinks you're doing something illicit (not allowing you to burn things to disc, restricting the ability to screenshot videos, uninstalling/deleting programs, adding rootkits, etc).

Far outside the scope of providing authorized access to protected content.

What's terrible is Netflix could have used it's considerable influence to tell _that_ _Industry_ that we won't walk this walk anymore. EME - as I understand it - allows them to create a closed-source program that runs in a sandbox to authorize and reproduce content we've paid to view. It should have very limited ability to do this - but breaking out of sandboxes is what some software engineers are employed to figure out. We're trusting those companies with the ability to run their programs on our computer so we can watch Paul Blart: Mall Cop. We hope it works as it's defined, but it's not a guarantee.

It's not worth it and pirates don't rip from Netflix anyway. They usually work for the industry as some part of the distribution/theater network.

This hurts the customer. Our computers are not our own.

Re:Update on HTML5 Video for Netflix by daenney on Wednesday March 22, 2017 @05:19PM (#13935080)
> What's terrible is Netflix could have used it's considerable influence to tell _that_ _Industry_ that we won't walk this walk anymore.

Why do you assume they didn't? And if they did and the industry said no, what should they have done? Walk away, lose access to all its content, see a large part of their subscriber base move to different services that do support DRM and therefor get the content and eventually have to start firing employees as their income drops?

Just about any streaming service has this exact same problem. They don't love DRM nor want to support it, it's annoying and cumbersome. But it's how you get access to the content. And unless you can survive purely on your own content you don't really have the option to walk away over your ideals.

If you want DRM out of the system, convince the content/rights holders that DRM isn't in their best interests, i.e they can make more money without it or at the very least won't lose money over not having it. If you're hoping that somehow a significant enough size of the population will boycott it for the industry to change, based on the ideals of the open web and open access, you'll be waiting a long time.

Re:Update on HTML5 Video for Netflix by derefr on Wednesday March 22, 2017 @05:57PM (#13935379)
It's interesting that DRM is basically a "free market problem." In cases where there is a government-supported media production/distribution service, as with the BBC in Britain, no DRM is needed, because the success of the service is not dependent on income from licensing the content. Instead, the content itself is often put up for free on a government-hosted online archive, in as many formats as possible, to ensure it can reach all the citizens who paid for it.
Re:Update on HTML5 Video for Netflix by tssva on Wednesday March 22, 2017 @06:43PM (#13935721)
About a 1 billion of BBC revenues of about 5 billion GBP come from licensing content worldwide. They utilize both geolocation access restrictions and DRM in an attempt to protect this revenue.
Re:Update on HTML5 Video for Netflix by syshum on Wednesday March 22, 2017 @09:13PM (#13936669)
Aside from the fact that your wrong about the BBC

the issue itself is not a "free market problem" because copyright only exists because of government interference. Government created the "right" DRM is protecting against.

In a pure free market, there is no copyright, thus no need for DRM to protect a right that does not exist

Re:Update on HTML5 Video for Netflix by 0xcde4c3db on Wednesday March 22, 2017 @09:43PM (#13936804)
DRM schemes effectively allow the implementer to invent their own rules well beyond what copyright law specifically reserves (e.g. restrictions on resale and lending, ability to create their own licensing regime to publish on a given platform), so I don't see how DRM depends on government intervention. DRM is already defined more by business and technical considerations than by the law. If anything, it seems to me that draconian DRM schemes would be more desirable to vendors if they didn't also have copyright lawsuits in their arsenal.
Re:Update on HTML5 Video for Netflix by syshum on Wednesday March 22, 2017 @10:03PM (#13936893)
What keeps DRM in play though is it is illegal to distrbute tools to circumvent DRM

So company like Slysoft, Replay, the devs of DeCSS, etc get sued out of existence when they create software that circumvents DRM

the cat and mouse game of DRM only works if you have government legal backing hamstringing the anti-drm crowd.

With out Anti-Circumvention laws there would be software on the open market to bypass every known DRM about 48 hours after it is release if not sooner

Re:Update on HTML5 Video for Netflix by 0xcde4c3db on Wednesday March 22, 2017 @11:15PM (#13937165)
I see how that's supposed to work, but I don't think that's how it happens in practice, and hence doesn't explain much about the motivation behind actually bothering to deploy DRM. Proto-DRM (copy protection, lockout chips, dongles) was in play decades before anticircumvention laws, and as far as I've seen those laws have little practical value in stopping circumvention anyway. They seem to be primarily used for extra charges against vendors of "fully loaded" hardware (e.g. consoles and media players preloaded with illegally copied content). When governments are leveraged to go after pure circumvention tools, the Streisand effect usually kicks in and ensures that the necessary code and keys are spread far and wide. The main place where DRM actually has teeth is in applications where connectivity and an account are required, such as streaming media services (i.e. the primary application of EME) and online gaming. In that case, the vendor can frequently update anticircumvention measures in the client and deactivate accounts (or, in the case of vendor-managed platforms like game consoles, ban the actual device) that fail enough checks.
Re:Update on HTML5 Video for Netflix by pfooti on Wednesday March 22, 2017 @06:44PM (#13935732)
And yet, I cannot just simply stream BBC content in the US.
Re:Update on HTML5 Video for Netflix by mavrc on Wednesday March 22, 2017 @06:15PM (#13935516)
> And if they did and the industry said no, what should they have done?

Distribute industry content with DRM, distribute their own content without, and see what the results are.

Somebody's going to have to perform the experiment to see what the outcome will be. Since Netflix produces tons of content now, they are in an excellent position to try this.

Re:Update on HTML5 Video for Netflix by Ironchefpython on Wednesday March 22, 2017 @06:33PM (#13935651)
> Distribute industry content with DRM, distribute their own content without, and see what the results are.

The industry content will show up on the Pirate Bay, and Netflix original content will show up on the Pirate Bay.

Were you expecting another outcome?

Re:Update on HTML5 Video for Netflix by caf on Wednesday March 22, 2017 @07:05PM (#13935902)
..which would indicate that the marginal value delivered by the DRM is zero?
Re:Update on HTML5 Video for Netflix by usrusr on Wednesday March 22, 2017 @07:38PM (#13936132)
Unfortunately, the cost for DRM is also zero for the content providers, as long as they are not distributors themselves.
Re:Update on HTML5 Video for Netflix by matt_kantor on Friday March 24, 2017 @09:52PM (#13953643)
Netflix creates tons of original content so it is both a producer and distributor. If Netflix really believed that the marginal value of DRM was zero they wouldn't use it on their own content since it has a nonzero cost on the distribution side.

The only other possibility that I can come up with is if Netflix's original content has multi-party rightsholder situations with contacts that legally require them to apply DRM even to "their own" content (IANAL and don't know much about how these things work, but it wouldn't surprise me).

Re:Update on HTML5 Video for Netflix by voltagex_ on Wednesday March 22, 2017 @06:47PM (#13935748)
Netflix content is already on Pirate Bay.
Re:Update on HTML5 Video for Netflix by usrusr on Wednesday March 22, 2017 @07:35PM (#13936111)
From a purely consumerist standpoint, by far the biggest problem with DRM used to be how it was falsely advertised as selling copies, when it was in fact just temporary access that could end any day, even tomorrow (company/server shutdown, hardware token malfunction/loss, general incompatibility with new stuff). Now that "buying" has mostly been replaced by streaming subscriptions, this problem has disappeared: it is perfectly obvious to even the most naive user that access to the content will be gone if they cancel Netflix (or if Netflix disappears) and as a bonus, it has become just as obvious that the streaming provider knows what you stream, open, "natural" surveillance instead of hidden, deliberate. Now it is more like the cashier knows what you buy at the supermarket (how else could they do their job?), whereas before it was a bit like the loyalty card backend knows (ignoring the massive difference in centralisation between cashier and loyalty card).
Re:Update on HTML5 Video for Netflix by acdha on Wednesday March 22, 2017 @09:00PM (#13936604)
I think you've perfectly summed up the problem the average anti-DRM advocate has: it's pretty easy to get people riled up when they paid a noticeable amount of money to “buy” something which goes away. In contrast, the Netflix/Spotify model where you pay a modest amount of money for all-you-can-eat accesss is hard to get much traction with since nobody thought they owned a particular work and the total price is so much lower that few people care.

I can't decide whether this is bad or a sign of progress towards training people that DRMed content is not worth much.

Re:Update on HTML5 Video for Netflix by guyzero on Wednesday March 22, 2017 @05:21PM (#13935101)
The major EME providers are PlayReady, which is Microsoft, and Widevine, which is Google.

You've already given those two companies pretty broad permission to run binaries on your computer (unless you use Firefox on Linux) so I'm not sure what the incremental security issue really is.

Re:Update on HTML5 Video for Netflix by CaptSpify on Wednesday March 22, 2017 @07:53PM (#13936242)
That's quite the invalid assumption. Additionally, if I let Google run binaries on my system in one spot, it does not mean I have given them full access to run binaries elsewhere.
Re:Update on HTML5 Video for Netflix by guyzero on Wednesday March 22, 2017 @11:42PM (#13937252)
I suppose but when you're already using Chrome using the Widevine CDM isn't a huge difference. When you're using Edge using the PlayReady CDM isn't a huge difference.

I see the general theory of the argument for Opera and especially Firefox but even so, why trust a CDM blob less than any other commercial binary?

Re:Update on HTML5 Video for Netflix by threeseed on Wednesday March 22, 2017 @05:17PM (#13935066)
The idea that Netflix could tell the movie and TV industries what to do is laughable and woefully ignorant of how those industries work.

Why do you think Netflix et al invests so much in original content ? Because they have zero leverage and are beholden to the whims of Hollywood.

Re:Update on HTML5 Video for Netflix by jungletek on Thursday March 23, 2017 @01:55AM (#13937650)
>[...]pirates don't rip from Netflix anyway.

Tell that to the 4k webrips on the private torrent trackers; I'm sure they'll be surprised both by the fact that they exist, and have apparently gained sentience.

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.
Re:Update on HTML5 Video for Netflix by noir_lord on Wednesday March 22, 2017 @03:24PM (#13933932)
That wasn't his central point I don't think, also Flash and Silverlight where largely beaten by the Open Web because they never got the adoption sufficient to rival it.

So instead they lobbied for it to be built in, the day will come when view source won't work anymore because everything fed down will protected by DRM and we moved another step closer to turning the web into a gigantic walled garden for whoever the incumbents are at that point in time.

Re:Update on HTML5 Video for Netflix by gsnedders on Wednesday March 22, 2017 @04:14PM (#13934431)
Flash's peak marketshare was over 99%. They had the adoption.
Re:Update on HTML5 Video for Netflix by Razengan on Wednesday March 22, 2017 @09:28PM (#13936750)
Until Steve Jobs slew it, or so I'm told.
Re:Update on HTML5 Video for Netflix by camus2 on Wednesday March 22, 2017 @05:13PM (#13935019)
> That wasn't his central point I don't think, also Flash and Silverlight where largely beaten by the Open Web because they never got the adoption sufficient to rival it.

this is a false statement, Flash was ubiquitous. Still today every chrome user on desktop has a flash player. Obviously, this isn't true for mobile, but before the mobile era flash was basically on every Windows and Mac computer with a browser.

Re:Update on HTML5 Video for Netflix by noir_lord on Wednesday March 22, 2017 @05:30PM (#13935179)
Merely been installed isn't adoption, if 99% of my web time is using HTML/JS to render content and 1% of that time Flash then do the web browser and flash have the same adoption?.

By that metric notepad would be the most adopted programmer text editor in the world..

Re:Update on HTML5 Video for Netflix by frik on Thursday March 23, 2017 @02:00AM (#13937665)
> the day will come when view source won't work

Yes, with WebAssembly. (With ASM.js, the predecessor it was still JS, but hard to read as human.) that's why WebAssembly is bad for the open web. In near future we will see binary blob SaaS like full Office running in browser. So the 1990s vision of vendor lock-in come to a full circle.

Re:Update on HTML5 Video for Netflix by nikcub on Wednesday March 22, 2017 @04:53PM (#13934835)
One of the only positives to come out of these new standards was that NPAPI could be deprecated.

We've arguably replaced an insecure and general purpose open interface to proprietary blobs with more narrow and single purpose open interfaces to proprietary blobs.

Re:Update on HTML5 Video for Netflix by greenhouse_gas on Wednesday March 22, 2017 @04:46PM (#13934762)
The thing is that there is (for all intents and purposes) no difference between ECE and plugins.

Actually, ECE is a plugin. The only difference is that it helps web-designers switch plugin providers.

That's it. No more security. No more standardization.

As a user, you still depend on the goodwill of the ECE provider throw you a bone. If you use a slightly niche OS (say, OpenBSD on ARM), you're out of luck.

If Adobe decides that it's not worth their time to develop a plugin for PaleMoon, they won't and you're out of luck (or will MS let their ECE plugin run on Linux, or Google's run on FF?). You (as a user) won't be able to switch to another provider. It all depends on the provider.

Re:Update on HTML5 Video for Netflix by djrogers on Wednesday March 22, 2017 @05:23PM (#13935120)
I completely understand and sympathize with your point, however this:

"If you use a slightly niche OS (say, OpenBSD on ARM)"

Is rather hilarious - calling OpenBSD on ARM a 'slightly niche' OS in the context of 'operating systems people use to watch video on the web' is rather ambitious, don't you think? OpenBSD on ARM would have to increase it's user base in this arena by a couple orders of magnitude to elevate itself to 'slightly niche'....

Re:Update on HTML5 Video for Netflix by greenhouse_gas on Wednesday March 22, 2017 @06:09PM (#13935468)
I picked two relativity popular platforms, though niche together to focus on the danger. All the more so would something like the rust os have problems.

The bigger issue will be when these providers will start holding OS's hostage (well, you want to view half the web? You've got to have a locked bootloader and only I have the key. You want to index our sites? Google has permission (the unlocking key) but not you).

Re:Update on HTML5 Video for Netflix by merb on Wednesday March 22, 2017 @07:42PM (#13936157)
isn't the Nintendo Switch based on either OpenBSD or FreeBSD and uses ARM? woudn't that be a good reason to have a plugin for that?

> https://en.wikipedia.org/wiki/Nintendo_Switch_system_softwar...

Re:Update on HTML5 Video for Netflix by Dagwoodie on Wednesday March 22, 2017 @10:11PM (#13936918)
Linux running FreeBSD Kernel, last I heard.
Re:Update on HTML5 Video for Netflix by cyphar on Thursday March 23, 2017 @03:39AM (#13937972)
> Linux running FreeBSD Kernel, last I heard.

Do you mean GNU running the FreeBSD kernel? Linux is only a kernel.

Re:Update on HTML5 Video for Netflix by caf on Wednesday March 22, 2017 @07:16PM (#13935973)
Google's CDM ("Widevine") does run on Firefox, apparently.

I wonder whether it would be feasible to run the CDM within QEMU on a platform like OpenBSD/ARM? At the end of the day it's just ordinary code that runs in the Gecko Media Plugin sandbox.

Re:Update on HTML5 Video for Netflix by frik on Thursday March 23, 2017 @02:02AM (#13937675)
ECE provider is Adobe (can we assume it shares some code from Flash DRM ?).
Re:Update on HTML5 Video for Netflix by Yver on Wednesday March 22, 2017 @04:21PM (#13934486)
How is that even an argument? That's a false dilemma. The choice isn't limited to binary blob Flash/Silverlight vs binary blob DRM plugin.
Re:Update on HTML5 Video for Netflix by acdha on Wednesday March 22, 2017 @09:05PM (#13936625)
What other option was seriously on offer? I buy DRM-free music but the video options are extremely limited to a few committed proponents — I love them for that but it's like saying nobody should buy conventional agribusiness food because you can buy organic free-trade kombucha.
Re:Update on HTML5 Video for Netflix by mmagin on Wednesday March 22, 2017 @03:21PM (#13933891)
Nevermind that the binary blobs come from pretty much the same place: https://wiki.mozilla.org/Media/EME#Platform_Support

(Ok, I guess on Linux it's a blob from a Google-owned company.)

Re:Update on HTML5 Video for Netflix by hsivonen on Wednesday March 22, 2017 @04:29PM (#13934578)
The previous DRM plug-in (Silverlight) was made by Microsoft. The new one (Widevine CDM) is made by Google.
Re:Update on HTML5 Video for Netflix by OhSoHumble on Wednesday March 22, 2017 @04:45PM (#13934751)
I was hopeful that the announcement from Mozilla applied to BSD. If Widevine is used, then this will be Linux only. Still good news, however.
Re:Update on HTML5 Video for Netflix by camus2 on Wednesday March 22, 2017 @05:14PM (#13935027)
How about the DRM stays out of the free web entirely? You want DRM? develop your own desktop app.
Re:Update on HTML5 Video for Netflix by throwanem on Wednesday March 22, 2017 @05:36PM (#13935229)
All frontiers close. The response suggested by history, if you prefer life on the frontier, is to find a new one.
Re:Update on HTML5 Video for Netflix by dkonofalski on Wednesday March 22, 2017 @05:15PM (#13935038)
I don't know if I'm just looking too far into your comment, but I don't see why you're blaming Netflix (or it seems you are) or how you got to them being the bad guys for this? They're not the ones that make the content. If it was up to Netflix, they would just release their shows DRM-free on Netflix for any platform. Unfortunately, that's not how things work and they have to bow to the demands of the content distributors (not creators, like some people have stated in other comments).
Re:Update on HTML5 Video for Netflix by criley2 on Wednesday March 22, 2017 @05:23PM (#13935118)
"I don't know if I'm just looking too far into your comment, but I don't see why you're blaming Netflix (or it seems you are) or how you got to them being the bad guys for this? They're not the ones that make the content. If it was up to Netflix, they would just release their shows DRM-free on Netflix for any platform. Unfortunately, that's not how things work and they have to bow to the demands of the content distributors (not creators, like some people have stated in other comments)."

We did a book study on a book called Clean Code where I work, and I reminded of a similar situation that the book explains when describing why we all write dirty and bad code.

Why do we write bad code? Because our stakeholders and our product owners require it. Well, they push deadlines and expectations on us that mean we have to cut corners to make their promises become reality within the unrealistic time provided.

But if you ask the stakeholder why they pust that on you, the stakeholder will say "well, it's the client". Or they'll say "marketing made a promise to the client".

It's always upstream. There's always an upstream concern.

In the book they talk about making a stand, as a developer. That you have a responsibility to explain to your stakeholders and the people above you that doing something the RIGHT way is worth it. That you are the subject matter expert, that it is your responsibility to raise these concerns and thus your responsibility to write good code.

Netflix can pass the buck. "We do what we have to".

But they have a responsibility as one of the premiere web companies to do more than pass the buck.

A Good Internet doesn't happen accidentally, and it doesn't happen when stakeholders pass the buck. It happens when people make a stand for what's right and operate according to their values.

So yes, it is Netflix's responsibility not to bend Mozilla into accepting a Studio's IP demands, but to bend the Studio into accepting humanity's internet demands.

Why do we assume that Netflix can persuade Mozilla, but not a rightsholder?

Re:Update on HTML5 Video for Netflix by mentat on Wednesday March 22, 2017 @06:03PM (#13935418)
The balance of the power is with the rightsholder. They own the content that Netflix wants to sell and that people want to watch.
Re:Update on HTML5 Video for Netflix by criley2 on Thursday March 23, 2017 @09:19AM (#13939453)
And the balance of power when coding is with the client and management, we are but poor pawns, doomed to dirty code.
Re:Update on HTML5 Video for Netflix by gech on Wednesday March 22, 2017 @11:02PM (#13937125)
Elvis is dead. His music should be free.
Re:Update on HTML5 Video for Netflix by dkonofalski on Wednesday March 22, 2017 @07:58PM (#13936282)
While I agree that there's always an upstream to hot potato too, Netflix really isn't in a position to make those kinds of demands. That's part of the reason why they're starting to produce their own content. The majority of the revenue in their business model comes from the content they show and the majority of that content is owned by someone else. If there wasn't historical precedent of companies giving Netflix the finger and pulling all of their content from their service, I would say that Netflix could push the boundaries and take a stand to try and make a change in the right direction. Unfortunately, until losing Netflix as a platform hurts the movie studios and publishers, that's not going to happen.
Re:Update on HTML5 Video for Netflix by EpicEng on Wednesday March 22, 2017 @08:48PM (#13936561)
Netflix absolutely does not have a responsibility to go out of business for the sake of pushing an issue few people care about. They have no real leverage here.
Re:Update on HTML5 Video for Netflix by komali2 on Wednesday March 22, 2017 @06:27PM (#13935600)
Is it Netflix's sole responsibility though? Their only real legal responsibility (other than, well, to not break the law) is to add value for their shareholders. "Taking a stand against DRM" doesn't sound like that.

It sounds more like the job of the citizens to elect representatives that support a Good Internet, and if the politicians they elect turn around and screw their supporters (which isn't illegal), to elect new politicians. A pretty disgusting and slow system, sure, but the only other solution I can think of (I am not a smart man) is outright revolution, and hoping the revolutionary government is all about a Good Internet.

EDIT: I'm fine with being downvoted if I'm wrong or stupid, but I'd appreciate if someone could tell me why they believe I'm wrong or stupid.

Re:Update on HTML5 Video for Netflix by ndesaulniers on Wednesday March 22, 2017 @05:18PM (#13935071)
> If it was up to Netflix, they would just release their shows DRM-free on Netflix for any platform.

That is SO UNTRUE. Netflix would never want their content to be distributed by anyone other than them, which is the point of DRM; absolute control over distribution, not copy protection.

If Netflix was against DRM, then why release their first party content DRM ensnared?

Re:Update on HTML5 Video for Netflix by dkonofalski on Wednesday March 22, 2017 @08:00PM (#13936294)
That's not necessarily true. It may just be a matter of efficiency. Because all the other content requires DRM, they may have a processing workflow or other technology that just DRMs any and all content in a single, unified manner. Changing that workflow to bypass DRM may actually make it more complicated. You also have to consider that their first party content is rather new so this could absolutely be something that they're working on doing but never implemented because it wasn't an option when they weren't producing their own content.
Re:Update on HTML5 Video for Netflix by ndesaulniers on Wednesday March 22, 2017 @08:08PM (#13936347)
That's a pretty big "what if" I'm not willing to grant. Given how complicated the MSE+EME stacks are, I have no doubt they would test just MSE without EME, since they can't guarantee EME compliance on any given browser. You're reaching.
Re:Update on HTML5 Video for Netflix by dkonofalski on Wednesday March 22, 2017 @08:22PM (#13936420)
Ok, fine... then replace it with any other one of the innumerable reasons they could have. Maybe it's not a technical issue. Maybe it's a political issue. The fact is that no one here knows why they haven't taken a position, especially based on their historic behavior related to it, and the issue is likely more complicated than anyone is giving it credit for.
Re:Update on HTML5 Video for Netflix by bubblethink on Wednesday March 22, 2017 @05:27PM (#13935157)
> If it was up to Netflix, they would just release their shows DRM-free on Netflix for any platform.

What evidence do you have to back this ? It's not like Netflix's own content is available DRM free. Corollary: If you are a content owner and want your content to be available DRM-free on Netflix, will Netflix make a provision for you ? I hate these generalizations that people make. Just because a company (like Netflix) is more tech-savvy than the average media house and makes a few blogs and OSS projects that run on BSD or Linux, it doesn't make them any better for the end user.

Re:Update on HTML5 Video for Netflix by paulddraper on Wednesday March 22, 2017 @05:22PM (#13935112)
Wait, who is forcing Netflix to use DRM for Netflix-produced content?
Re:Update on HTML5 Video for Netflix by AsyncAwait on Wednesday March 22, 2017 @06:31PM (#13935636)
I actually agree with you and am against DRM, but I think I've read that Netflix doesn't actually own all the rights to their content, which doesn't mean that they don't have a great amount of influence if they wanted to do it - obviously, they don't.
Re:Update on HTML5 Video for Netflix by paulddraper on Wednesday March 22, 2017 @09:36PM (#13936778)
Who else is competing with Netflix for Netflix-produced content?
Re:Update on HTML5 Video for Netflix by pathsjs on Thursday March 23, 2017 @08:26AM (#13939147)
Depends on the country. In Italy, Netflix cannot distribute house of cards because it sold the rights to do so to sky
Re:Update on HTML5 Video for Netflix by dkonofalski on Wednesday March 22, 2017 @08:06PM (#13936329)
I can't say for sure but rights are really complicated. I mean... if you look at a show like House of Cards, Netflix doesn't even own all the rights for that. It's not just a decision that they can make unilaterally.
Re:Update on HTML5 Video for Netflix by teej on Wednesday March 22, 2017 @05:16PM (#13935057)
I get your argument but a larger portion than ever of Netflix's catalog is first party content.
Re:Update on HTML5 Video for Netflix by dkonofalski on Wednesday March 22, 2017 @08:05PM (#13936324)
That doesn't mean that the majority of their catalog is. Everything they do will be optimized for what they have the most of.
Re:Update on HTML5 Video for Netflix by gcb0 on Wednesday March 22, 2017 @05:34PM (#13935216)
1. they make content too. but regardless...

2. they are the middle man for content. they are exactly the group that benefit most from drm.

Re:Update on HTML5 Video for Netflix by criddell on Wednesday March 22, 2017 @03:56PM (#13934248)
I thought that the only change was that the DRM mechanism was turned into an open standard. How is this worse than before? As someone that occasionally uses Linux, I think it's great that Netflix works there now. Previously, the audience on Linux wasn't worth the development effort for Netflix.

Am I missing something? Is this a case where an open standard is a bad thing?

Re:Update on HTML5 Video for Netflix by azakai on Wednesday March 22, 2017 @04:20PM (#13934477)
First, the DRM is still not standard. Only the interface to it is. Every browser must still deal directly with the DRM provider and hope to reach an agreement with them, both technically and financially. As a result, only certain platforms are supported. New browsers face a new barrier to entry, in particular - the exact opposite of how the Web is support to work.

Second, this is worse in the sense that Netflix, Google, and Microsoft - creators of EME - have gotten the W3C to support DRM. That's not just a symbolic blow.

Re:Update on HTML5 Video for Netflix by Hydraulix989 on Wednesday March 22, 2017 @04:38PM (#13934692)
<Redacted>
Re:Update on HTML5 Video for Netflix by snissn on Wednesday March 22, 2017 @04:48PM (#13934774)
From another comment, don't necessarily think of the dilemma of a netflix user, or internet browser, instead think of the of the blow to the openness of the next person that wants to make a brand new web browser. For the new browser to fully compete, they now /NEED/ to set up a closed relationship with netflix, the drm provider, the other browsers. If it was an open standard, they could simply code the crypto algorithms that the standard needs and not need to get permission for the closed drm formats.
Re:Update on HTML5 Video for Netflix by openasocket on Wednesday March 22, 2017 @07:05PM (#13935897)
So what's the alternative, exactly? Before EME, you needed Flash or Silverlight to view DRM-ed content like netflix. Someone making a brand new web browser would similarly need to support a Flash plugin or Silverlight plugin to compete. Such a developer could choose not to bother with a Flash or Silverlight plugin, but couldn't they also choose not to bother to implement EME? What's changed?
Re:Update on HTML5 Video for Netflix by __jal on Wednesday March 22, 2017 @04:55PM (#13934848)
> it's a good compromise in a capitalist society where artists need to make money for what they produce in order to feed themselves

Funny, I haven't heard many artists clamoring for DRM, and the ones who do tend to be well beyond the feeding-themselves step on Maslow's Hierarchy.

No, it is, as always, the distributors. That's because DRM hurts artists but entrenches distributors.

It is a shitty compromise because it is the start of a closed web. Enjoy your view-source while your corporate overlords deign to give you permission.

Re:Update on HTML5 Video for Netflix by criddell on Wednesday March 22, 2017 @04:34PM (#13934635)
> First, the DRM is still not standard. Only the interface to it is.

Is a programming language a good analogy? The C++ spec says what a switch-statement should do, but nothing about how it must be implemented, right?

> New browsers face a new barrier to entry

It's not really a new barrier to entry though, is it? If I wrote a browser last year, were my chances of getting Netflix to support it better then than they are now?

What about if I wrote a new DRM scheme? With a standard interface, are the barriers to entry for me now lower?

Re:Update on HTML5 Video for Netflix by izacus on Wednesday March 22, 2017 @05:00PM (#13934907)
> Is a programming language a good analogy? The C++ spec says what a switch-statement should do, but nothing about how it must be implemented, right?

No it isn't. Example: Netflix will ask for Widevine DRM provider (and exactly that provider!). It's a proprietary closed licensed platform and your system needs to have their binary blob licensed and compiled for it. If you don't have it and didn't pay for it, you won't be able to decrypt the DRM. Of course to get your DRM blob to run, you'll also have to prove and promise to the DRM provider that you have locked out the user from their own device so they won't be able to accidentally record the video they watch.

It's impossible to make your own open implementation or compete with existing players because they built the fact that you need to negotiate with them for licensing into the standard.

Re:Update on HTML5 Video for Netflix by criddell on Thursday March 23, 2017 @08:20AM (#13939110)
> It's impossible to make your own open implementation

I don't think that's true. It's still just a plugin so as long as implement something like the Gecko Media Plugin / CDM, you should be good, or at least no worse off than before where you had to support the Flash or Silverlight plugin.

Re:Update on HTML5 Video for Netflix by merb on Wednesday March 22, 2017 @07:49PM (#13936218)
well at least as it looks Widevine has no license fees for Device Manufacturers i.e. browsers. You only need to contact them. Not sure how this company makes any money tough. (maybe through training courses)
Re:Update on HTML5 Video for Netflix by criddell on Wednesday March 22, 2017 @05:06PM (#13934961)
I'm still not getting how this is a step backwards. Last year there was no Netflix on Linux. This year there is.

Is there a better way to make strong DRM?

Re:Update on HTML5 Video for Netflix by azakai on Wednesday March 22, 2017 @06:43PM (#13935724)
It's true that in the short term this can seem like a step forward - we went from bad to slightly less bad. But it's also harmful and dangerous in the long term for all the reasons being discussed.
Re:Update on HTML5 Video for Netflix by BuuQu9hu on Wednesday March 22, 2017 @06:05PM (#13935430)
The 'Open Web' means "My browser can access ANY AND ALL CONTENT on the Web given that it supports the necessary standards."

This DRM implementation would add this suffix: "and any number of third parties have chosen to allow my browser to use their proprietary decryption modules." This is the opposite of the Open Web and therefore a threat to user freedom and the integrity of the Web as a whole.

Re:Update on HTML5 Video for Netflix by criddell on Thursday March 23, 2017 @10:42AM (#13940116)
The internet is used for a heck of a lot more than content destined for a browser.
Re:Update on HTML5 Video for Netflix by asdfgadsfgasfdg on Wednesday March 22, 2017 @05:15PM (#13935042)
EME is a much bigger barrier than the old system of plugins. With plugins you implemented the right API for the silverlight plugin and netflix would work. In the future you need to not just implement the API but persuade someone to build the plugin for your browser and then persuade each individual DRM using site to work with your browser.
Re:Update on HTML5 Video for Netflix by caf on Wednesday March 22, 2017 @09:02PM (#13936613)
The CDM is just a plugin - on Firefox it's a Gecko Media Plugin, and it seems easier to implement the GMP API than the NPAPI for Silverlight, since it's a lot more restricted.
Re:Update on HTML5 Video for Netflix by asdfgadsfgasfdg on Thursday March 23, 2017 @03:32PM (#13943353)
Please re-read my post.

These steps are not technical but they are very significant.

Consider how you would provide this plugin to your users as the author of a new browser? You have to ask the plugin authors for permission to use it.

Then consider that you have to persuade Netflix to allow the users of your browser to use their site (without changing user agents).

Neither of these steps were required with NPAPI

Re:Update on HTML5 Video for Netflix by caf on Thursday March 23, 2017 @07:16PM (#13945224)
Your browser can just download the plugin from Google the same way Firefox does. No permission required since you're not distributing it yourself. This is no different than the case of the Silverlight plugin.

There is no reason why Netflix would need to do user-agent sniffing - the EME API is built around request access to specific "Key Systems" (eg. Widevine) by well-known-name. If they do user-agent sniffing that's an entirely separate issue, and is just as much as problem in the Silverlight case.

Re:Update on HTML5 Video for Netflix by criddell on Thursday March 23, 2017 @09:40PM (#13945876)
> You have to ask the plugin authors for permission to use it.

I don't believe that's true. The plugin is freely available. You just have to write the host.

I don't think Netflix or the rights owners would care since the stream is protected equally in any browser.

Re:Update on HTML5 Video for Netflix by amluto on Wednesday March 22, 2017 @04:41PM (#13934716)
> Is a programming language a good analogy? The C++ spec says what a switch-statement should do, but nothing about how it must be implemented, right?

That's not what's going on, though. It's an API that a DRM provider can implement. A website that gets a DRM provider it doesn't recognize will refuse to work with it.

Re:Update on HTML5 Video for Netflix by josteink on Wednesday March 22, 2017 @04:08PM (#13934366)
> Am I missing something? Is this a case where an open standard

Yes. The bit where this is an "open standard" to implement completely closed, non-standard plugins, which cannot be implemented by reading the spec.

With this "open standard" any browser or OS not blessed by Hollywood can't have a full web experience.

And I take great issues with that.

Re:Update on HTML5 Video for Netflix by cwyers on Wednesday March 22, 2017 @05:06PM (#13934957)
I don't get it. You argue that not being able to visit Netflix "isn't the full experience," and so people won't choose a browser where they can't visit Netflix. So, because of this... all standards-compliant browsers should be unable to visit Netflix? So then why would anyone choose a standards-compliant browser?
Re:Update on HTML5 Video for Netflix by k_ on Thursday March 23, 2017 @03:27AM (#13937932)
It is not "not being able to visit Netflix" which isn't the full web experience. Web-based DRM will spread to other services, maybe even to other things than video.

I couldn't care less about Netflix, I never intended to use their services and never will, but this really is bad news for the web.

Netflix on the web with a plugin was fine for me: people wanting to watch Netflix on their standards-compliant browser would need to install a proprietary plugin to do so, and would have done it (at least a great number would have, I guess). It was their choice to do so (the other one being not to watch Netflix in a browser, and yes it _is_ a choice).

The difference (and it's big to me) was that it had _no_ impact on people not wanting to watch Netflix in their browser. These people did not have this proprietary code running in their browser and all the potential security issues coming with it.

IMO the browsers should (and I don't actually know if they do or not atm, this is a thing I need to check soon) at the very least let people opt in or out of this. Of course if they opt out they wouldn't be able to use services like Netflix.

And here comes the browser plugins world again... So much for killing flash (which was and still is a _great_ platform for small to medium web games).

Re:Update on HTML5 Video for Netflix by cwyers on Thursday March 23, 2017 @10:23AM (#13939973)
This again seems odd. Browsers shipped with Flash preinstalled, and EME in Firefox is a plugin.

People are just tying themselves in knots to act like the status quo is a disaster.

Re:Update on HTML5 Video for Netflix by maxerickson on Wednesday March 22, 2017 @04:14PM (#13934428)
Another way to look at it is that Netflix isn't part of the web.

I suppose that viewpoint admits that obstinance on the part of Firefox was not going to get Netflix to offer their service without DRM.

Re:Update on HTML5 Video for Netflix by cgearhart on Wednesday March 22, 2017 @05:40PM (#13935265)
Only insofar as Netflix was opting not to put their content on the web. Netflix was _not_ prevented from being on the web pre-DRM -- it's just that responsibility for meeting their requirements for access to content rested with them rather than browser developers.

edit: not really sure how I messed up the original comment, which was an incoherent mess.

Re:Update on HTML5 Video for Netflix by maxerickson on Wednesday March 22, 2017 @06:00PM (#13935391)
Huh? If a browser developer doesn't bother to implement an EME interface and get access to DRM components for their users, all that happens is that some sites don't work. It doesn't force any burden on the developer.

I understand the argument about this making it harder to develop new browsers and so on, but eschewing EME probably wasn't going to prevent that from happening, it would just happen in flash or other closed code.

Re:Update on HTML5 Video for Netflix by sandov on Wednesday March 22, 2017 @04:28PM (#13934567)
Could we "fork the web" or something?. Someone could create a parallel stack of web standards that is fully free/open. For the most part it would be the same as the conventional web standard, but open source browser developers would have something to base their developments on, something like the "OpenWeb Stack". Sorry for my bad english.
Re:Update on HTML5 Video for Netflix by hsivonen on Wednesday March 22, 2017 @04:59PM (#13934898)
Uncheck the “Play DRM content” checkbox in Firefox, and you have your parallel stack right there. Does it still play Netflix that way? No.
Re:Update on HTML5 Video for Netflix by simplyluke on Wednesday March 22, 2017 @04:40PM (#13934709)
Could you? Absolutely. Would it be used widely? Unlikely.
Re:Update on HTML5 Video for Netflix by ce4 on Wednesday March 22, 2017 @04:45PM (#13934754)
It will open DRM to every other websites as well as the barrier to DRM is now low enough for everyone.
Re:Update on HTML5 Video for Netflix by davexunit on Wednesday March 22, 2017 @03:24PM (#13933931)
Dark days, indeed. Sacrificing the open web so some can watch movies.
Re:Update on HTML5 Video for Netflix by kefka on Wednesday March 22, 2017 @04:38PM (#13934687)
I wonder how long it will be for newsprint media companies to use this to "secure" their websites so that Adblockers cannot process the 'encrypted but you can't see' data?
Re:Update on HTML5 Video for Netflix by MBCook on Wednesday March 22, 2017 @04:11PM (#13934402)
To a huge chunk of users video IS the web. If Netflix, Hulu, and YouTube didn't work (assume YT adopts DRM) the browser would basically be DOA for a HUGE chunk of people.
Re:Update on HTML5 Video for Netflix by cgearhart on Wednesday March 22, 2017 @05:45PM (#13935303)
So...the _entire_ web should be saddled with DRM because people who don't care about the web wouldn't use it otherwise? Is the web better now because all those people now have _another_ way to passively consume video content?
Re:Update on HTML5 Video for Netflix by MBCook on Wednesday March 22, 2017 @06:12PM (#13935488)
That argument works both ways. _NO ONE_ should have the option to view copyrighted videos because you don't want it?

Yes, I think this improves the web. You no longer need the unmaintained disaster that was silverlight or the resource vampire and exploit factory that was flash. Users can choose to view this content in a safeER way than before.

The only good argument against this is the 'we don't need DRM ' argument, but that hinges on the ability to get content you want in a non-DRM format and it seems clear that isn't happening anytime soon thanks to Hollywood et. al and I don't blame them.

Re:Update on HTML5 Video for Netflix by rimliu on Thursday March 23, 2017 @02:30AM (#13937765)
How does it sacrifice the open web again? Is there a law being passed that entire web should be DRMed?
Re:Update on HTML5 Video for Netflix by appleflaxen on Wednesday March 22, 2017 @04:09PM (#13934378)
This is so true that the title should be changed. I propose:

Online video services get DRM added to browser in order to "protect content".

Re:Update on HTML5 Video for Netflix by scythe on Wednesday March 22, 2017 @04:23PM (#13934502)
It's true but it doesn't make sense IMO for the buck to stop at Netflix. If Netflix could have talked content providers into allowing them to use an open-source "DRM" that worked for ordinary users but which could probably be circumvented by someone with programming skills, this wouldn't happen. The problem is that legally Netflix could be on the hook for any copyright infringement that may have been facilitated by their service. Crucially, the definition of "facilitated" can include not taking enough precautions to prevent it, and apparently using an open-source script that imperfectly prevents copying is still enough to expose Netflix to liability.

The laws must be ordered in a way that allows streaming video to be sold to users of open-source software. It's not like the current scheme is entirely resistant to pirates anyway. It's very much like the Drug War in that externalities affecting individuals who have done nothing wrong begin to exceed the damage caused by the "crime".

Re:Update on HTML5 Video for Netflix by nikcub on Wednesday March 22, 2017 @04:44PM (#13934745)
This argument was more true in the early days of the web DRM debate, but the Netflix of today is largely publishing its own content rather than distributing the content of others, so it is setting the terms of how its content will be protected.

I don't think it is a coincidence that Netflix's more aggressive anti-piracy actions and rollout of more DRM-enabled platform choices has come at a time that they're distributing more of their own content.

Re:Update on HTML5 Video for Netflix by algesten on Wednesday March 22, 2017 @04:52PM (#13934819)
Even if I don't like DRM, I don't believe a closed source DRM is any more perfect than an open source one. There's a strong link to cryptography here, and in that area an open source encryption is no less perfect than a closed one.

Whatever DRM was required to please the suffering media conglomerates, it could at least have been open source.

Re:Update on HTML5 Video for Netflix by futurix on Wednesday March 22, 2017 @03:36PM (#13934043)
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.

Re:Update on HTML5 Video for Netflix by josteink on Wednesday March 22, 2017 @03:50PM (#13934186)
> 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 by astrodust on Wednesday March 22, 2017 @03:56PM (#13934249)
Free as in freedom means companies are free to add things like DRM if the want and consumers are free to choose services that don't go down that path.
Re:Update on HTML5 Video for Netflix by aurelianito on Wednesday March 22, 2017 @06:06PM (#13935440)
Mmmmmmm, only if I can edit the source of the DRM program and make my own modified version.
Re:Update on HTML5 Video for Netflix by CJefferson on Wednesday March 22, 2017 @04:22PM (#13934501)
You want free and open? Go build that yourself. People do build Firefox and chrome without this, go download them and enjoy yourself.
Re:Update on HTML5 Video for Netflix by hsivonen on Wednesday March 22, 2017 @05:04PM (#13934934)
If you don't want Widevine, you can simply uncheck the “Play DRM content” checkbox in Mozilla-distributed Firefox, and the CDM doesn’t get downloaded and gets deleted if it was already downloaded. No need for a different build. Be sure to uninstall Flash and Silverlight, too.
Re:Update on HTML5 Video for Netflix by scythe on Wednesday March 22, 2017 @04:26PM (#13934542)
>That puts the cost of DRM on everyone except the ones who want to freeload on our open tech to take our freedom away.

This argument implicitly assumes that the big cost of DRM is actually implementing the DRM. Everyone knows that isn't true. The social cost of DRM is the effect on the users' freedom, and if the users are using entirely proprietary applets they're probably less free than if they depend on a single proprietary library.

Re:Update on HTML5 Video for Netflix by kmicklas on Wednesday March 22, 2017 @04:24PM (#13934513)
> but unfortunately that's unrealistic.

Why is it unrealistic? Hollywood just needs to be pushed harder. It worked for music no?

Re:Update on HTML5 Video for Netflix by TeMPOraL on Wednesday March 22, 2017 @04:59PM (#13934902)
Did it? I have a feeling we're about to see more DRM with music. All the pieces are falling into place. Files get replaced with streaming (which is to files what a service is to a product), and I wonder how long it will take before more companies will follow Apple's suit by ditching the audio jack. Going full digital there will enable companies to set up fully DRMed path from memory to speakers/headphones, like they did with video.
Re:Update on HTML5 Video for Netflix by mschuster91 on Wednesday March 22, 2017 @05:37PM (#13935240)
> to set up fully DRMed path from memory to speakers/headphones

Unlike with video, where the signal ends up unencrypted only on the very last chip in the chain, namely the one that drives the (I'm taking a guess here!) thousands of pixel lines, this is not practical with audio signals - you can always intercept and easily record the signal in analog form, either right before the PA stage or if this does not work (because the D/A converter and PA are implemented on one chip) after the PA output. The signal will of course be affected by the PA frequency characteristics, but that can be compensated for - and you still get a perfect audio signal.

Also, I highly doubt that professional/semi-professional home theater setups will ever ship with "smart" (i.e. more wires than just the +/- heavy-gauge, direct speaker power signal wires) speakers, so you get the analog hole right there, on the output matrix of the amp.

Re:Update on HTML5 Video for Netflix by bubblethink on Wednesday March 22, 2017 @07:06PM (#13935908)
The battle isn't about recording the decoded stream. Even with video, all forms of HDCP have been broken. It's about getting it before it's decoded.
Re:Update on HTML5 Video for Netflix by zabuni on Wednesday March 22, 2017 @04:48PM (#13934777)
It worked for music because they were stupid enough to put all their eggs in one basket, iTunes and iPods, and then got screwed when Apple wanted to sell electronics more than music and wouldn't raise their prices. Movies aren't in the same situation.

Movies are a great deal more fractured, and they will remain fractured. The movie studios will not let Netflix turn into the iTunes for movies.

Re:Update on HTML5 Video for Netflix by JustSomeNobody on Wednesday March 22, 2017 @05:52PM (#13935347)
If it becomes a problem the internet will find a way to evolve around it.
Re:Update on HTML5 Video for Netflix by snakeanus on Wednesday March 22, 2017 @03:48PM (#13934159)
>to the point where even Firefox couldn't afford not to support it

Mozilla did not seem to care that much actually. And as long as torrents exist I do not think that there is any reason to support it.

Re:Update on HTML5 Video for Netflix by riquito on Wednesday March 22, 2017 @04:01PM (#13934301)
It was either support EME or become the browser where you can't see any video.

https://hacks.mozilla.org/2014/05/reconciling-mozillas-missi...

Re:Update on HTML5 Video for Netflix by snakeanus on Thursday March 23, 2017 @12:33AM (#13937393)
More like "It was either support EME or become the browser where you can't use any useless service like Netflix." As long as torrents exist Netflix is useless.