[schoen]

Unfortunately (though it's considerably more compartmentalized and constrained than prior iterations), Google is trying to replace Flash with a DRM mechanism that also requires proprietary software. So while you might think that the advent of HTML5 video means you no longer need proprietary software to interoperate with the services that use it, Google and its partners are working to ensure that that's not true.

[pippy]

If you're referring to Encrypted Media Extensions it's not a DRM mechanism that requires proprietary software. It's a specification for a communication channel between a browser and Digital Rights Management agent software on the local machine. While it's not ideal, it's just some javascript functions that interact with the DRM on the computer. The DRM software itself is completely optional.

It's much better than having plugins that do the same thing (if you use firefox you're used to Flash asking for trial Norton to be installed every time a security exploit is found in Flash). In the perfect world we wouldn't need it, but it leaves no excuse for media companies not to use HTML5.

[bzbarsky]

Sorry, but there's an important distinction between what you said and what EME is.

EME is a spec for a communication channel between script in a web page and a browser, with the idea that the browser then talks to a DRM module. It's not a spec for a communication channel between the browser and a DRM module.

This is important, because it means that you end up with DRM modules that are tied to a particular browser.

The NPAPI plugin situation is unfortunate in all sorts of ways, but the one good thing it had going for it was that there _was_ an API that multiple browsers all implemented, such that a single plugin binary woudl work in all of them (modulo the usual bugs and incompatibilities you have when there are multiple implementors of an API).

Unfortunately, 3 of the 4 main browser vendors also happen to be DRM vendors, and were rather united in their opposition to the W3C creating a specification for the communication channel between the browser and the DRM module.

[walterbell]

Is there any current or proposed implementation that can support W3C SMIL in the browser? A decade ago, RealPlayer was able to seamlessly edit video excerpts (defined by start::stop intervals) into a single video stream. The excerpts could have originated from different servers.

Will the new DRM formats support this use case? E.g. if I'm a paying Netflix subscriber, could I view a dynamically defined (XML or JSON) mashup of Buffy and Twilight, using only a list of start/stop edit points? The HTML5 viewer would need to pre-buffer each video clip, to make the viewed stream seamless.

[bzbarsky]

You could build something like that in Javascript on top of HTML <video> and MSE, probably. The EME (DRM) spec is not really related to this.

[walterbell]

Wouldn't the DRM spec have to explicitly permit MSE buffering? If Javascript could buffer the stream and send it to any destination other than a DRM-approved output device, that would defeat the DRM.

[bzbarsky]

The way EME is designed, the browser is responsible for fetching the data from the network and passing it to the DRM module. This is no different with MSE, as far as I can tell; what you buffer up is the encrypted data, then pass it on to the DRM stuff.

[abdias]

True, it was approved by W3C and Tim Berners-Lee a while back (http://www.infoworld.com/article/2612478/html5/berners-lee-a...), and was criticized - understandably so.

For instance: If someone do research for educational or critical purposes, they have the right to use copyrighted material under "Fair Use" (US, UK and other countries have similar rules).

With DRM this would essentially block this right (if used on the material in question), which of course is not a good thing.

But it's great to see that HTML5 is now the preferred choice on YT.

[ucaetano]

"Right to use" != "right to have it provided to you in an easy-to-copy way".

[deathanatos]

> "Right to use" != "right to have it provided to you in an easy-to-copy way".

One of the big problems with DRM is that this ends up being not "right to use" but "right to use in several very narrow ways that someone else deems fit". If your use is innovative or just different — such as using a more capable media player with more features than the one provided to play the media with —, you end up being not able to do it.

[ucaetano]

So if I write a poem in a rock in the middle of the desert I'm offending your right to have access to it? You can always film the screen and use that as fair use.

I'm against DRM, but "You're offending my rights to copy with minimum effort" is not an argument against it. Nobody has to provide anything in an easy-to-copy way, which doesn't mean that you don't have the right to copy it.

[schoen]

I agree that HTML5 is much better than Flash in every way, so in this sense I'd just like to encourage our community to continue applying pressure at all levels and in all channels to ensure that Encrypted Media Extensions doesn't continue to be a part of HTML5 standards, UAs, or websites.

[yohui]

> I'd just like to encourage our community to continue applying pressure at all levels and in all channels to ensure that Encrypted Media Extensions doesn't continue to be a part of HTML5 standards

Which just means content owners will continue to use proprietary plugins or push unstandardized extensions.

Pressure should be applied to the root of the issue (copyright holders' desire for DRM), not the symptom.

[patzerhacker]

Pressure should be applied in both places.

[JoshTriplett]

> Which just means content owners will continue to use proprietary plugins or push unstandardized extensions.

Which will provide a worse experience, making it easier for competing content owners to provide a better experience.

[cabalamat]

> The DRM software itself is completely optional.

Unless you want the web page to work. One could just as well describe having a web browser as "completely optional".

[derekp7]

Is the DRM module itself an open specification? Or will it be a separate proprietary program that content sites will still require you to install? I can see for example Real or Flash making such modules, and still bundling with random tool bars and popups.

Or will it most likely be a specification that allows multiple (but NDA'd) implementations, such as the DRM component of dvd and bluray players? If that is the case, then it is still better than what we had before, as multiple vendors will need to compete (increasing the likelihood of a non-crappy implementation).

[lbenes]

> Is the DRM module itself an open specification? Or will it be a separate proprietary program

It's a closed source proprietary blob. You can read about it here.

https://blog.mozilla.org/blog/2014/05/14/drm-and-the-challen...

[hsivonen]

There is no single "the DRM module". Microsoft has its own in IE. Google has its own in Chrome. Apple has its own in Safari. Adobe has its own (that Firefox will be able to use).

None of these have open specs.

[Buge]

A company could make it necessary to install their DRM to view their videos and bundle Norton with it. This would actually be worse than the current situation because the user would have to install a different DRM thing for each different site.

Although I can see sites being reluctant to do that because it would be inconvenient for the users to have to install something specifically to watch the web videos on that site. One thing I can see happening would be one major DRM software that emerges and all websites that want DRM work together to use that.

[anigbrowl]

I don't care about DRM as long as it's lightweight and seamless. Streaming is one use case where its use is entirely justifiable if it operates transparently.

[girvo]

As long as streaming is available on all the devices I wish to use it on (that used to include Linux, but nowadays it's not my "daily driver"), then I'm okay with transparent DRM for streaming or rentals, too.

[josteink]

If a platform has to be explicitly supported in a supposedly cross-platform standard, then the details on how to implement that must be published or the standard is no longer cross platform.

With this move, Linux is no longer "supported" on a web wholly built on it. That's completely fucked up.

DRM is fundamentally incompatible with the web. Let's not give it any reason to think it belongs here.

[Buge]

The problem is most companies wouldn't create modules that are compatible with all operating systems. Open web is supposed to be open, not platform dependent.

[mholt]

This all assumes you have a solid Internet connection. Some of us have to watch movies offline most of the time.

[jsprogrammer]

Why would users switch to this as yet non-existent proprietary DRM mechanism when free and open source solutions already exist and are widely used?

[vertex-four]

Because I want to watch Netflix or whatever else requires it, and that's a value calculation I've made?

[click170]

Still seems like a false dichotomy to me. Subscribe to Netflix and pirate your content if you have a firm believe in being DRM free while rewarding the creators of content you consume.

[derekp7]

Last I checked, the most effective way to pirate content is via a protocol such as Bit Torrent which requires you to also distribute pirated content. And that has legal ramifications, which then requires non-trivial methods to obscure your activities (paid proxy servers, etc). Most of us use Netflix not for ideological reasons, but for the pure convenience of it. Compared to Bit-Torrent,with Netflix you can easily browse titles, watch a bit, switch to another one, or watch whole seasons without waiting for multi-hour or multi-day downloads.

[zaroth]

If you are not adverse to piracy, or you believe you have a valid fair use right to access the content, but you don't want to be guilty of distribution (a much higher penalty) then Usenet is probably the best bet.

[jambox888]

> valid fair use right

They seem to be making it tricky to rip DVDs/Blu Rays these days (dirty tricks to screw with Handbrake/VLC) so the only way to get a movie onto my media server is to dl from somewhere after I bought the disc. Ironic, no?

[jsprogrammer]

BitTorrent traffic can be encrypted. There is no legal attack vector when used.

[sjy]

Encryption just makes it difficult for your ISP to automatically throttle your torrents. Anyone can still download the torrent themselves and see that you're an uploader.

[macns]

> Anyone can still download the torrent themselves and see that you're an uploader.

Not exactly an uploader, but a peer.

All a downloader knows about his peers, is that they have pieces of that torrent.

[robotresearcher]

Paying for a DRM-encumbered service is not really consistent with a "firm belief in being DRM free".

[mccr8]

What do you mean by "as yet non-existent"? I believe Chrome, IE and Safari are all shipping it. It sounds like you can even use Netflix with it, as of last year: https://news.ycombinator.com/item?id=8159110

[mark-r]

Because there will come a day when something they want to watch desperately will require it.

[jsprogrammer]

That day will never come[1].

[1] http://en.wikipedia.org/wiki/Analog_hole

[TaylorAlexander]

I remember the days where they talked about making video cameras that would actually stop recording if they were pointed at a piece of media with special markers in it.

Nowadays people would use some kind of HDCP-breaking digital capture device, and regulating all video cameras is basically impossible with their ubiquity, but it's crazy to think about video cameras being modified against our will to suit the needs of one industry.

Those in power will always try to take control away from us. Don't let them.

[gatehouse]

It isn't all that crazy, it has already been done to printers:

http://www.pcworld.com/article/229647/counterfeit_money_on_c...

https://www.eff.org/issues/printers

[derekp7]

And VCRs too. The original Macrovision technique relied on the low tolerance to noise in the old record-mode AGC circuits on first generation VCRs. But when VCRs improved to the point that Macrovision was ineffective, legislation was passed so that VCR manufactures had to include a special circuit to recognize the Macrovision noise bursts, and emulate the old behavior. (Source: my memory of an old article in an electronics magazine, so the above may be somewhat inaccurate -- the article may have been only referring to proposed legislation, or possibly industry self-regulation).

[anigbrowl]

That's not practical for video in most cases - dedicated pirates will find a way around it, but casual consumers won't bother. Duplicating HD or better video by analog means without significant quality sacrifices is much easier said than done.

[newaccountfool]

Surely you only need the pirates to find a way around it as they will be the ones who distribute the free copies.

[Retra]

Yeah, until the video recorder on your cell phone gets a little nicer.

[anigbrowl]

It would have to get a lot nicer. I work in film and shooting an image of a TV or computer monitor is often a pain, even with high-end cameras, due to interference between the frame rates of the camera and display devices, as well as light intensity. For high quality results the typical workaround is to just throw up a grid pattern on the screen in question and composite in the desired image afterwards.

Is it possible to get results this way, yes of course. Are the results any good, not really. Commercial pirates work with people in the exhibition sector, amateurs rely on known weaknesses in popular disc formats. You'd have to be pretty desperate to rely on streamed media as your 'original.'

[schoen]

I think you might be confusing whether the DRM will be effective at stopping copying with whether many users will adopt DRM-restricted tools and platforms.

[coldtea]

Nope, it will come aliright. You're just taking a black/white dichotomy. But they don't have to make it impossible - just inconvenient.

[baddox]

They can make it inconvenient to access the analog hole, but they can't make it very inconvenient to play the DRM-free copy once someone has captured it.

[realusername]

It will be the same problem as with current DRM techniques. It works now because it's still not fragmented yet. You will have your content available with your computer with particular updates and browser versions and for some reasons, it will never work with some combination of hardware + OS + driver + browser + country (especially with phones) and the result is people are going to pirate it anyway because it just works all the time, as always.

[dijit]

users wont, content producers, publishers and companies will publish want DRM.