Support for Encrypted Media Extensions (DRM content in HTML5)

asked 2015-03-10 12:56:25 +0300

wanderer

2356 ●50 ●76 ●72

updated 2016-08-17 11:28:58 +0300

jiit

2678 ●32 ●58 ●59

admin

Encrypted Media Extensions (EME) is a draft specification of the W3C to embed DRM protected content (e.g. Videos) in HTML5. With this system DRM content can be processed in a browser without the need of a plugin like Flash Player or Silverlight. Netflix, amongst others, is using this technology for their streaming solution. Most browsers support EME already. Firefox doesn't support it yet, but Mozilla works on a solution to support it via a third party content decryption module provided in a sandbox.

Has Jolla any plans to support EME natively in the Jolla Browser? Will you follow the solution of Mozilla? I want to point out that EME support would be a good alternative to android apps for Netflix and similar services (see also this request).

I know that EME is a quite controversial topic. Many people don't like it because it goes against the principles of an open web. I personally see it pragmatically: The demand of the industries for DRM will not disappear soon, so it is better to provide it in an open specification than with closed plugins. Feel free to share your thoughts and discuss about it here :-).

Edit 25.05.2015: You can vote for or against it by voting for one of the answers below.

edit retag flag offensive close delete

Comments

3

@c.la, @heubergen: I suggest that you transform your comments into answers, so we can make a voting for or against this feature.

wanderer ( 2015-05-18 12:11:21 +0300 )edit

@wanderer done :)

c.la ( 2015-05-25 19:40:19 +0300 )edit

1

I also prefer the pragmatic view on DRM: I never want to BUY any content that is DRM encrypted (e.g. I always buy music as CD's and rip them myself, and strictly did not buy any CD that had "copy-protection" on it when that was a growing model a few years ago), but it's a different thing with streaming services like Spotify for music or Netflix for video. When I buy a monthly flatrate that allows me to listen to as much music / watch as many movies as I want, I have to accept that the only way any content provider will grant me access to its services will be by shipping it with some kind of copy-protection.

It's either that or not use any streaming service. Period.

I think the Mozilla approach on this topic is quite sensible. Don't include it in your own code, but make it an external plugin (and if possible provide an API so e.g. a native Netflix app could be possible).

casanunda ( 2015-05-26 17:59:06 +0300 )edit

6

answered 2015-09-14 13:08:54 +0300

tworaz
1423 ●13 ●21 ●18

Well, as much as I don't like EME, I would like to support at least MSE. The problem is none of those features are currently fully supported in gecko. Last time I've checked gecko only partially supported MSE for youtube on mac and windows. It might change in one of the 4x releases, but our current plan is to migrate from ESR31 to ESR38. This means the feature won't be supported at least until we move to gecko 45, or 52 (certainly won't happen this year).

The QuickSilver chromium port I work on a side does support both extensions, but on a down side it currently does not do any HW video decoding. Netflix should work there, but it'll eat your battery super fast.

edit flag offensive delete publish link

Comments

I was extremely curious on that QuickSilver chromium port before the update to 1.1.9 as the browser before was giving me a real headache. Now it's not that bad anymore but where can I easily track your progress, do you post somewhere about it yet?

MoritzJT ( 2015-09-14 13:28:34 +0300 )edit

1

Well I don't blog about my work or anything like that. Once I upload the content to github you should be able to track that.

tworaz ( 2015-09-15 21:24:40 +0300 )edit

14

answered 2015-03-10 14:05:56 +0300