Stop DRM in HTML5

Community announcements - software releases, LUG meetings etc.

Moderators: ChrisThornett, LXF moderators

Stop DRM in HTML5

Postby roseway » Thu May 30, 2013 1:59 pm

Don't allow the media companies to control access to the web. Sign the petition.

http://www.defectivebydesign.org/no-drm-in-html5
Eric
roseway
LXF regular
 
Posts: 448
Joined: Thu Jan 18, 2007 2:27 pm

Postby johnhudson » Thu May 30, 2013 9:07 pm

Done it already.

However, there is nothing to stop people from adding DRM to HTML5 - the question will be which browsers will implement the necessary code.

Not all browsers implement all the existing features.
johnhudson
LXF regular
 
Posts: 876
Joined: Wed Aug 03, 2005 1:37 pm

Postby guy » Fri May 31, 2013 9:07 am

johnhudson wrote:Done it already.

However, there is nothing to stop people from adding DRM to HTML5 - the question will be which browsers will implement the necessary code.

Not all browsers implement all the existing features.


"This proposal stands apart from all other aspects of HTML standardization: it defines a new 'black box' for the entertainment industry, fenced off from control by the browser and end-user,"

At least, according to Danny O'Brien of the EFF - see EFF Makes Formal Objection to DRM in HTML5.

[Thanks to Groklaw and BoingBoing for the breadcrumb trail]

Reminds me a bit of the non-standard data islands in Microsoft's OOXML "standard".
Cheers,
Guy
The eternal help vampire
User avatar
guy
LXF regular
 
Posts: 1077
Joined: Thu Apr 07, 2005 12:07 pm
Location: Worcestershire

Postby johnhudson » Fri May 31, 2013 9:59 pm

But the browser will still have to include it in the DOM and the browser may not do so just as not all browsers include all the input types in HTML5.
johnhudson
LXF regular
 
Posts: 876
Joined: Wed Aug 03, 2005 1:37 pm

Postby guy » Sat Jun 01, 2013 8:06 am

So, if browser developers are going to choose for themselves whether to implement DRM, why does the EFF care a fig about HTML5 standardisation of it?
Cheers,
Guy
The eternal help vampire
User avatar
guy
LXF regular
 
Posts: 1077
Joined: Thu Apr 07, 2005 12:07 pm
Location: Worcestershire

Postby johnhudson » Sat Jun 01, 2013 9:02 pm

1. Thin end of the wedge.
2. Fragmentation.
3. (but really 1.) Principle.

As Gabriella Coleman's book Coding freedom points out, the content providers have been at this since the 1980s and the FOSS advocates have fought back in a variety of ways, usually successfully - but we can't rely on that. So all options for fighting back from supporting the EFF to persuading major browser provides to ignore the ‘black box’ have to be on the table.

The best approach would be to persuade content providers that they would lose customers if they went down with line; with them money always talks.
johnhudson
LXF regular
 
Posts: 876
Joined: Wed Aug 03, 2005 1:37 pm

Postby guy » Sun Jun 02, 2013 12:57 pm

So you don't agree with the EFF that "it defines [in HTML5] a new 'black box' for the entertainment industry, fenced off from control by the browser and end-user"?

Or do you think that is just another little brick in a very big wall?
Cheers,
Guy
The eternal help vampire
User avatar
guy
LXF regular
 
Posts: 1077
Joined: Thu Apr 07, 2005 12:07 pm
Location: Worcestershire

Postby johnhudson » Sun Jun 02, 2013 8:53 pm

I agree with EFF because that's exactly what it's intended to do.

The questions are:
will browsers agree to implement it?
will hackers find a way round it?
what are the best strategies to frustrate it?

I happen to believe that, in the long run, it will be frustrated. But I don't know how much pain it is going to cause in the short term and which of the many strategies one might use against it is likely to be the most effective.
johnhudson
LXF regular
 
Posts: 876
Joined: Wed Aug 03, 2005 1:37 pm


Return to Announcements

Who is online

Users browsing this forum: No registered users and 1 guest