Linked by Beta on Sat 8th Jun 2013 20:06 UTC
Internet & Networking "Bruce Lawson started a very interesting discussion about the Encrypted Media Extensions to HTML a few months ago, with learned and interesting commentary from John Foliot and others. After devoting some thought to this, I believe that the amount of argument around this subject is at least partially caused by its separation of the web from the spirit of the web."
Thread beginning with comment 564326
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE: It was needed.
by ssokolow on Mon 10th Jun 2013 21:30 UTC in reply to "It was needed."
ssokolow
Member since:
2010-01-21

It was either we have DRM option in HTML video or we had flash vs h264 forever.

There have been concessions made for this sort of thing before it was called the object tag and was for 3rd party plugins.

You have every right not to use it and not to pay for it, like before.

Fundamentalism is bad for everyone and doesn't make a whole lot of sense. Let people have a specification that is open (which is in the spirit of the web) and they are free to implement it ... and their potential customers are free to decide if they wish to use it.

I don't see how this is a bad thing?


True, I suppose. It's mainly a "devil you know" situation.

With Flash, we already know how to make sure a new browser implements NPAPI well enough to get the plugin working. We understand the implications of Adobe's approach to sandboxing untrusted code. We trust Adobe to not risk the PR nightmare of trying anything funny like the Sony Rootkit fiasco.

Given the current climate regarding DRM and Secure Boot and all the other nonsense, we have neither of those guarantees with whatever replaces it. It could wind up being the new ActiveX.

Reply Parent Score: 3

RE[2]: It was needed.
by anda_skoa on Tue 11th Jun 2013 10:38 in reply to "RE: It was needed."
anda_skoa Member since:
2005-07-07

With Flash, we already know how to make sure a new browser implements NPAPI well enough to get the plugin working.


Not to mention that it is a plugin, it can be plugged into any browser implementing the respective host infrastructure.

It allows a third party like Adobe to provide something that works regardless of the browser being used by the user, leaving it up to the user to choose which browser to use based on the user's preferences.

The EME spec on the other hand only specifies a JavaScript API that the browser must provide for the content application. All browser will have to implement it again and again.
Tird parties like Adobe will have to reach out to all browser vendors or all operating system vendors or all device vendors (depending on which level the "protection" is implemented in a certain scenario) and ask them to be included.

Reply Parent Score: 2