4 ms·
I have really mixed feelings about this. On one hand, I enjoy renting new material from Google Plus Movies and TV, enjoy Hulu and Netflix. I understand the nee
by mark_l_watson 11y ago
I have really mixed feelings about this.
On one hand, I enjoy renting new material from Google Plus Movies and TV, enjoy Hulu and Netflix. I understand the need for some form of DRM.
On the other hand, I support the FSF and like to see open source options.
For me, the best middle road is to isolate all of the DRM in one closed source web browsers, and have the rest of my system as close to liver software as is practical.
- julie1 11y agohuhu Whatever the DRM technique you have can always put in a low noise chamber a cam/microphone to make a close to the original reproduction by analogic means you can re-publish. People used to enjoy watching videos in 1024x768x16bpp and hearing is satisfied with 46KHz More than what can be achieved in AAD, or ADD chains. DRM is a chimera. It costs money and IP laws are flawed at the contractual level. Since Louis XIV when _lettre de Patentes_ where invented the deal was exclusivity granted to invest in new content versus free public domain when exclusivity disappears. Disney/Sony music are recycling public domain in so called original works (Grimm tales, 1900 pop songs converted in Rap melodies ...) hence breaking the deal. And exclusivity is getting WAY overboard. As if chosen authors where the new nobility of culture, while street art is being stolen by galleries and real artists lives in misery. Plus, except Gutenberg close to none public domain contents are cheaper than new one, while paying the artists are said to be the greatest expense. Try to find the integral of Shakespeare, Molière, The 1001 night tales for a decent price.
- fixermark 11y agoEssentially, the choices are not "Standardize DRM descriptions in the w3c process or don't have browsers supporting DRM at the HTML-model level." The choices are "Standardize DRM descriptions in the w3c process or have an ad-hoc collection of binary blobs, de-facto standards implemented by the dominant browser vendors, and external mobile players." If the w3c doesn't standardize the DRM descriptions, it just pushes the standards a little bit towards irrelevance as the industry interprets silence as damage and routes around it (especially given the current ecosystem where ever-more "web content" is actually vended through mobile apps). This may very well be the principled stand that the w3c should take---it may be correct to curtail themselves to only standardizing things that can be openly implemented. But we should observe that their lack of a hat in this ring isn't going to kill DRM-protected video streams---the owners of the content want that and are willing to pay a LOT of money to be lied to.
- nitrogen 11y agoLast time I checked, EME still results in an ad hoc collection of binary blobs. There's Google, Adobe, Microsoft, and Apple all with competing blobs.
- fixermark 11y agoIt results in a standard for describing them so that browsers can properly select the right one, or ignore all of them. That's less ad-hoc than the alternatives.
- nitrogen 11y agoBut it does very little, if anything, for the open web, and either needs total top to bottom specification for open implementation, or doesn't belong in a web standard.
- fixermark 11y agoThat may be true, but it is irrelevant. I don't know why you believe that the technologies under the W3C web standards need be open. The standards themselves need be open (they're published, after all), but the technologies underpinning them? Checking W3C's website, their guidelines for implementations appear to be "W3C issues a call for implementations as part of standardization and welcomes public participation" [https://www.w3.org/participate/implementation https://www.w3.org/participate/implementation]. Nothing in the formal standards process [https://www.w3.org/2005/10/Process-20051014/tr.html https://www.w3.org/2005/10/Process-20051014/tr.html] appears to require all implementations be "open," and that assumption flies in the face of previous legacy standards (<img> when .gif was an accepted file format but still encumbered by patent, the <object> and <embed> standards that specify closed-binary plugins to side-load). While it'd be nice if it worked the way you described, it seems that the standard as currently codified (including one specified "dummy" open reference implementation) is all that is needed.
- nitrogen 11y ago