Consider what happened when Apple refused to allow Flash on their platform; that certainly accelerated the decline of Flash, or at least forced the development of Apple-specific approaches for that platform.
So what would happen if Chrome and Firefox had stood together in solidarity and said "no"? I don't think the answer would have been a mass exodus to IE; for that matter, what if IE had gone along with it? (Edge already bans plugins.)
Google has been a prime supporter of DRM on the web. They bought Widevine a few years ago which is a DRM provider and pushed for inclusion of DRM in the W3C.
It's basically Mozilla vs. the rest, just like it happened with patent encumbered H.264 and Mozilla was left holding the bag.
Given that Google has been one of the biggest voices in favour of EME, that seems rather unlikely.
The unstated assumption here is that DRM that isn't a standard won't be built into a browser.
That's not the assumption (because DRM already existed in the browser before it became a web standard - remember Silverlight?).
But it's much less work for the entities providing the DRM when EME provides a common standard for them to work with. This lowers the pain (for them) of using DRM, which makes it harder to provide enough pressure on them to stop DRM.
EME Standardized the Plugin err "extension" API. It in no way standardizes DRM. The Stardardization is around the way Javascript will be used to call inside HTML5 the browsers CDM (content decryption module" which is a plugin by another name.
There are currently 3 competing technologies, with more to come, that are incompatible with FOSS, incompatible with open systems
For Chrome Browsers there is Google Widevine CDM
For MS Browsers there is MS PlayReady
For Firefox there is Adobe Video CDM (which is basiclly the video playback part of Flash)
This is the problem with EME, Netflix, Google, and Microsoft have been masterful at their marketing of this to people that should be able to see past the bullshit
EME/CDM is still a binary browser plugin, Sure we "eliminate" flash and the need for a "3rd party" plugin, but in many ways that it worse, Before we had a standard Plugin API that allowed non-supported browser to make use of Flash, so there where many many many browser that could call the 3rd party flash application to make use of that content. Now those browsers are completely locked out. You will only be able to Access content on the Big 2, Chrome and IE, and maybe Firefox is they finalize their agreement with Adobe to bring in a Binary Blob into the Firefox Browser
I do not call that a "WIN" for interoperablity.
Indeed. Standardizing an unethical practice sounds like a very bad idea.
This is patently false. From 2003 to 2009 music sold on the most popular online store, iTunes, contained DRM. Due to competitive pressure from Amazon's DRM-free store, Apple also dropped their DRM. It once seemed impossible that the major labels' digital music would be sold without DRM, but now that is the norm. Content industries can and have changed their minds on DRM when consumers force them to.
http://macdailynews.com/2007/02/06/apple_ceo_steve_jobs_post...
The relevant part is: "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. If the big four music companies would license Apple their music without the requirement that it be protected with a DRM, we would switch to selling only DRM-free music on our iTunes store. Every iPod ever made will play this DRM-free music."
However, it's also worth noting that the music industry is the only major content industry where this has been achieved.
If anything, things are going the other way with video content. There have been stories this week about Netflix cracking down on those who are circumventing region locking using VPNs. It seems big name shows are increasingly being offered via proprietary pay-per-view systems run by their production organisations, and centralised libraries like Netflix are either not carrying the material or dropping content they used to offer. We still have different release dates for movies in theatres in different countries, and for films and TV shows on DVD/Blu-ray. A recent trend seems to be for US TV shows not to release new seasons on Blu-ray at all here in the UK, so you can buy the lower quality version on DVD or you have to sign up for yet another online service to watch in HD, assuming you even have access to such a service from where you live. All of these measures are overtly consumer-hostile, but there is little the consumer who enjoys TV and movies can do if the entire industry moves that way (short of resorting to illegal channels and risking the consequences, which obviously is what a lot of people do in practice).
The software industry is similarly screwed up. We've gone from buying a copy of something and being able to use it, to buying a copy but needing remote activation, to buying a copy but needing varying degrees of ongoing online access to continue using it, to not even being able to buy a copy and merely renting. Personally I draw the line before I get that far, and refuse to pay for any important software unless I can reasonably expect it to continue working indefinitely. Even then, my businesses have been screwed repeatedly by varying degrees of ongoing online access or cutting off support, and slightly surprisingly, the most expensive professional software is by far the worst for this and for fixing the mess is something goes wrong.
I really hope that before too long the law starts to reflect the real relationships with modern technologies, where the original vendor who would traditionally be the main second party in a purchase contract is effectively just providing an introduction to the real other party, which is the organisation that makes the software/service and is (or isn't) going to provide ongoing support and/or retain ongoing control over it. I also hope that smaller, disruptive software businesses who are starting to take on industry heavyweights can demonstrate that money talks and enough customers are willing to vote with their wallets for less one-sided arrangements. But for now, the possibility that industry heavyweights like Microsoft, Adobe and Autodesk are going to give up their vice-like grips built on DRM and related technologies seems more remote than ever, and all of them are pushing hard in the opposite direction.
At least in public, Netflix has claimed that they don't want DRM themselves, and would remove it if they could, but that their content providers require it.
The dance doesn't match the music.
Video games are a major industry where there was significant pushback from DRM thanks to sellers like GOG. There are still many games with DRM, but the portion that don't use DRM has increased significantly.
However, the anti-censorship instinct of the internet will eventually drive all of these forms media to an open distribution model.
EDIT: Which, to the larger point -- DRM is two things, a content play and a platform play. Standardizing DRM is one way to limit the power of platform holders over content providers. Eliminating DRM is another. Deciding whether standardizing DRM is a lesser evil than leaving DRM up to platform holders is a question of who do you fear more, the content owners or the platform owners.
Half the problem is EME doesn't even attempt to standardise DRM in any real way: it just provides a JS API to deal with DRM'd content, decrypted by some "module" which interfaces with the browser in an undefined way (and in every case except Firefox, does so by bundled with no possibility of any other modules being installed).
They merely accepted a JS API for launching non-standard proprietary DRM Content Decryption Modules. API of these modules is deliberately undefined and left to be browser-specific.
It's just as standard and interoperable as using W3C's <object> to launch Flash.
It's just not true. Lots of people are pushed only weakly towards one side or the other. Making it easier to go one way and harder to go the other way will influence where people in the middle end up.
However, does EME allow encryption of javascript? I thought it was just for playback elements in <video> and <audio>? Searching a bit, I can't find evidence that executable javascript could be encrypted.
Flash is only disappearing because of Web DRM. The situation gets worse for Linux users. Instead of installing the Flash plugin and seeing DRM content through it, now DRM only works if you are using Google Chrome because it's the only browser with Hollywood-approved DRM scheme.
As for users of FreeBSD and other less popular OSes, well Google Chrome doesn't have a build for you, so you lose this content completely.
Netflix and such need Chrome to play videos because of DRM. Well, let me see: Netflix doesn't cache any videos, so if I want to watch something more than once, it's smarter to download it unencumbered.
And then it gets to the point that pirating most of your content makes sense again. If you're going to be a scofflaw, might as well go all the way, and get the good experience from it.
That is simply not true. Flash was on the way out with or with out EME, Chrome and IE was already doing it. With out EME they still would have moved forward with their implementations of Widevine and PlayReady respectively.
Netflix would have still switch to it, and Chrome on Linux would have still played Netflix.
EME did not result in "Content coming to Linux" and there is no guarantee it will continue.
It will be up to the individual CDM makers, in this case google, if they want to continue to include the binary blob on Linux. No different than Flash. If google chooses tomorrow to remove widevine from Chrome on Linux, there goes your Netflix and any future "HTML5 EME" enabled websites
Further many other "HTML5" Browsers can not play this content because the binary blob required is not there... making it non-interoperable with any true FOSS gnu/linux operating system. Firefox has to pay Adobe for a CDM Plugin under pressure from their less than idealist users...
"HTML5" as a standard should mean anyone implementing the spec is able to see all content built on the spec. Sadly with the inclusion of EME sites like Netflix can claim to be "HTML5" compliant while still preventing every FOSS HTML5 browser from viewing any content.
That is not a WIN for Standardization, or a WIN for interoperablity
The way to deal with them is by not accepting them in return, and only using alternatives. Losing money bites, and they can quickly straighten their crooked ways out of fear for competition. That's the only method that works for curing DRM disease.
I think standards bodies operate most efficiently when they provide a bit of choice. If some browser writers want to implement DRM in their browsers I would rather it be standardized than not. Simply because the W3C doesn't standardize it does not mean it will not be implemented in browsers. It's not like W3C standards are binding legal documents.
From TFA: Much of the "Web" is disappearing into apps and into the big companies' walled gardens. If it is to be relevant in the decades to come, it must do everything it can to keep the Web open as an alternative to those walled gardens.
Then remove a reason for the web to disappear into walled gardens and allow the W3C to standardize DRM. Not providing ways for everyone to serve up their content via the web will only accelerate movement to other mediums.
I like the idea of the non-agression covenant. But the obvious problem with it is that implementers of EME don't have to sign it. It looks like it only covers those who participate at the W3C. It's a rather strange legal concept, and possibly unenforceable, but I'll leave it at that.
Of course they will. The big media companies like to posture and pretend they're going to take their ball and go home, but the customers hold all the power in this relationship. It's not like they are going to leave money on the table by sticking to dying platforms out of a religious devotion to DRM, they just think they can have their cake and eat it too by bluffing.
The goal seems to be to reduce the spread of DRM. I'm cool with that. However, I'm not sure that these actions will do anything at all to reduce the usage of DRM. My reasoning there is that those who want to use DRM are not going to accept any alternative that is not DRMd. So in order to stop spread of DRM, keeping DRM non-standardized would have to prevent others from adopting DRM.
So the ultimate question for me is: who's going to start using DRM that's not already? I think this set is zero. Adding standardization of DRM won't close up any more content that wasn't closed before, IMHO.
However, by not standardizing, we lock out all sorts of non-mainstream clients form accessing content. Now that Flash is going to disappear entirely, that means no access to all sorts of content on Linux, unless it's standardized.
So I see something to gain, and nothing to lose by standardizing DRM. I'm making assumptions to arrive at that conclusion, but I believe that they're no worse than the ones that Cory Doctorow is making here. It's just weird to see myself diverging from the EFF on this, and on T-mobile, and other things.