News for hackers. Stuff that matters.
Re:You Can't Destroy the Village to Save It: W3C vs. DRM, Ro... by JoshTriplett on Friday January 15, 2016 @01:45PM (#10911218)
Standardization provides endorsement. If DRM requires a non-standard plugin, and plugins themselves become increasingly verboten, at least some folks who might have used DRM may decide that they want to reach a wider audience instead.

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.)

Re:You Can't Destroy the Village to Save It: W3C vs. DRM, Ro... by amlgsmsn on Friday January 15, 2016 @09:04PM (#10913836)
>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.

Re:You Can't Destroy the Village to Save It: W3C vs. DRM, Ro... by Silhouette on Friday January 15, 2016 @02:21PM (#10911447)
So what would happen if Chrome and Firefox had stood together in solidarity and said "no"?

Given that Google has been one of the biggest voices in favour of EME, that seems rather unlikely.

Re:You Can't Destroy the Village to Save It: W3C vs. DRM, Ro... by icebraining on Friday January 15, 2016 @03:06PM (#10911734)
Yeah, the thing is that Chrome interests are inseparable from Youtube's, and unless they can force the media companies to let go of DRM, like Apple did to music labels, they need some kind of solution. And frankly, what's in it for them?
Re:You Can't Destroy the Village to Save It: W3C vs. DRM, Ro... by toast0 on Friday January 15, 2016 @03:22PM (#10911840)
Apple uses DRM for subscription music, but not music you've paid for a perpetual license; why wouldn't Youtube use DRM (at the copyright owner's request) for music and video when you haven't paid them for a license?
Re:You Can't Destroy the Village to Save It: W3C vs. DRM, Ro... by magicalist on Friday January 15, 2016 @03:41PM (#10911973)
Does youtube use DRM? All the youtube download extensions suggest not.
Re:You Can't Destroy the Village to Save It: W3C vs. DRM, Ro... by JoshTriplett on Friday January 15, 2016 @03:48PM (#10912027)
YouTube rentals and purchases use DRM (and the downloaders don't handle those); normal videos just use obfuscation.
Re:You Can't Destroy the Village to Save It: W3C vs. DRM, Ro... by icebraining on Friday January 15, 2016 @06:36PM (#10913141)
DRM is obfuscation.
Re:You Can't Destroy the Village to Save It: W3C vs. DRM, Ro... by spyder on Saturday January 16, 2016 @05:20PM (#10917137)
No DRM yet, but Google doesn't allow YouTube downloader extensions in their Chrome Web Store (but allows downloaders for other video sites, how strange :-/).
Re:You Can't Destroy the Village to Save It: W3C vs. DRM, Ro... by bct on Friday January 15, 2016 @02:50PM (#10911635)
> If DRM requires a non-standard plugin, and plugins themselves become increasingly verboten

The unstated assumption here is that DRM that isn't a standard won't be built into a browser.

Re:You Can't Destroy the Village to Save It: W3C vs. DRM, Ro... by chimeracoder on Friday January 15, 2016 @03:05PM (#10911722)
> 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.

Re:You Can't Destroy the Village to Save It: W3C vs. DRM, Ro... by cpeterso on Friday January 15, 2016 @03:30PM (#10911894)
EME commoditizes DRM, for better or worse. Like you said, a EME lowers the pain to adopt DRM. With a standard EME API and CENC (Common Encryption), services can easily support multiple DRM backends or switch DRM backends. I worry that increased competition between DRM providers will lead to an arms race of stronger DRM tech.
Re:You Can't Destroy the Village to Save It: W3C vs. DRM, Ro... by the_ancient on Friday January 15, 2016 @10:09PM (#10914040)
Umm no

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.

Re:You Can't Destroy the Village to Save It: W3C vs. DRM, Ro... by derf_ on Friday January 15, 2016 @04:52PM (#10912431)
It's worse than that. Competition drives price to zero. That means DRM providers need to get their revenue from some other way. The obvious way is to exploit (track, or worse) the user.
Re:You Can't Destroy the Village to Save It: W3C vs. DRM, Ro... by icebraining on Friday January 15, 2016 @06:30PM (#10913098)
So if these businesses did earn money from DRM, you think they'd go "some extra profit by adding user tracking? Oh, no, thanks, we're good" and leave it on the table? Why?
Re:You Can't Destroy the Village to Save It: W3C vs. DRM, Ro... by shmerl on Friday January 15, 2016 @04:18PM (#10912215)
> Standardization provides endorsement.

Indeed. Standardizing an unethical practice sounds like a very bad idea.