5 ms·
Sigh. Look, I'm okay with DRM, as long as it works on all my devices. EME won't, under linux, I guarantee the DRM Vendors won't bother releasing Linux binaries.
by girvo 13y ago
Sigh. Look, I'm okay with DRM, as long as it works on all my devices. EME won't, under linux, I guarantee the DRM Vendors won't bother releasing Linux binaries. That annoys me.
- Touche 13y agoIt will work under Google Chrome (not Chromium) on Linux most likely, as Google is a DRM vendor.
- cpeterso 13y agoAnd Google will presumably have a Linux CDM for Chrome OS, so they could release it for Linux desktop, too.
- duncan_bayne 13y agoBut it doesn't matter. Google could release their CDM for any operating system they choose; it doesn't alter the fact that EME and CDM are inimical to the Open Web and should be rejected by the W3C.
- wmf 13y agoAFAIK ChromeOS supports Widevine EME and Chrome does not. Why is it enabled on one platform and not the other? Make of that what you will.
- bzbarsky 13y agoBecause they haven't got it locked down enough yet, presumably. Chrome on Android doesn't support it either, yet, but http://code.google.com/p/chromium/issues/detail?id=275989 http://code.google.com/p/chromium/issues/detail?id=275989 is targeted for Chrome 32...
- code_duck 13y agoThey're going to have to create ways to play their media on Linux, with the growing popularity of the OS for appliances such as living room video players and products like the Steam Machine.
- duncan_bayne 13y agoPlaying on Linux is not the issue. The issue is that EME + CDM introduces an 'Open Web' standard that cannot in fact be implemented by anyone who chooses. Say the W3C decided to add a new tag to HTML, called '<happy>', that displays a smiling face. Anyone who wishes (Firefox, Mozilla, you, me) could implement that feature and start properly displaying content that contains <happy> tags. This is not true of encrypted content that requires a proprietary, closed-source CDM and / or a secret key to operate. That is why EME should be rejected by the W3C. Lack of Linux support is a consequence of the problem, not the problem itself.
- gbhn 13y agoHow about the embed tag? What big differences do you see between implementing EME vs the embed tag?
- Rizz 13y agoOne difference is that with embed you can still support most existing platforms by implementing NSAPI.
- gbhn 13y agoMy reading is that ESE is intended to work in much the same way -- the main work is done by the Content Decryption Module, which is more plugin-like. And indeed, the way existing DRM-using systems work in the browser is with the embed tag. The spec says "The Content Decryption Module (CDM) is a generic term for a part of or add-on to the user agent that provides functionality for one or more Key Systems."
- wmf 13y ago
- baddox 13y agoIt's pretty much baked into the definition of DRM that it may not work on all of your devices.
- duncan_bayne 13y agoThere is no technical reason that DRM technology can't be FOSS and use non-secret keys; this is a result of licensing agreements with content owners. I'm hoping to have those agreements made public so technical discussions surrounding EME can take place with a degree of transparency.
- nly 13y agoEh? If your DRM code is FOSS I'm just going to patch it, recompile it, dump out the keys, decrypt my media, and ignore all your constraints. Technical DRM only 'works' when the code is an obfuscated steaming pile and the implementation/platform/hardware tries to make it an incredibly difficult process to mess subvert. Theres never been a consumer-facing DRM technology thats made a lick of sense, and frankly I'm glad most of the FOSS success stories are in defeating it rather than proliferating a broken trust model that serves to prop up slow-moving industry monopolists who bump up costs (of many kinds) to consumers and are going to lose in the long-run anyway.
- duncan_bayne 13y agoSure - and the fact that you can do that is why 'big content' don't want a bar of FOSS DRM. Personally, I like the idea of copyright bits that travel with content. Some way of telling the user how the creator wishes the content to be used, or not used. Not enforced, mind you (because as you say, that's impossible) but just notified. Making it easier to do the right thing. That would go well with watermarking to identify paid content, and a good system for processing micropayments. But of course it's easier just to lobby the W3C and break the Open Web :(
- nly 13y agoI agree. I think if we promoted Creative Commons and generally made people more aware of how copyright law can be used to promote creativity, fair use and empower indy content creators that we'd become more sympathetic to the case made by Hollywood and the music industry, and maybe eventually get out of this rut of seeing it as a weapon for big media. I wouldn't oppose any standard that made it mandatory for copyright and license information to be encoded in to image, video and audio content. Nor would I oppose a requirement for browser vendors to expose that information accessibly (on demand) to users. I'd also like to see online registries that worked like TinEye or Midomi and let me quickly identify content with an emphasis on copyright and license discovery.
- duncan_bayne 13y agoEME will work on Linux. The thing is, the CDMs with which it is designed to interface won't. It is technically possible to produce a purely FOSS CDM that will compile on pretty much any platform. However that idea has been rejected by content licensees on the grounds that it won't meet requirements, as defined by licence agreements that (so far) no-one is authorised to post on the W3C discussion list. Other ideas that have been rejected are server-side watermarking (too expensive, doesn't meet requirements) and client side watermarking (doesn't meet requirements). So, myself and (most) others are rejecting EME on the grounds that it is inseparable from "non-user-modifiable client components" (a wonderful phrase I picked up on the list), a.k.a. closed-source, proprietary CDMs that are tied to particular OSs.
- zanny 13y agoI find it somewhat awesome that this whole html drm debacle is effectively what Richard Stallman has been saying for decades versus outdated entrenched old media interests. Except in this case, the web standards consortium is giving away your freedom for you. That is what pisses me off most, really - if big media was left to squalor in broken plugins and horrible drm, which should be horrible because its entirely anti-user, they would have to eventually adapt to the Internet and change their ways or die. But with the power of money and apathy on the part of vast swathes of the tech community that think they don't have ground to stand on (hint: you are the consumers they want buying stuff, you hold all the cards) they are ending the open inter-operable web. It sucks.
- duncan_bayne 13y agoYes it sucks, but it's not too late. The issue of patents in W3C standards came up a decade ago; it looked like the W3C had caved then, but a 'firestorm of public criticism' (to quote an article at the time) caused them to back down. So, agitate. Tell people about it. Bring it up at user groups. Post to Hacker News :) If you know anyone in tech. journalism, tell them. Support the EFF.
- gsnedders 13y ago
- krasin 13y agoyou should not be okay with DRM. It's as simple as it's: DRM is the form of slavery.
- markdown 13y ago> DRM is the form of slavery. I dislike DRM as much as the next guy, but really? Slavery?
- cycrutchfield 13y agoCaptain Hyperbole to the rescue!
- hbags 13y ago> you should not be okay with DRM. It's as simple as it's: DRM is the form of slavery. Sorry Ivan, but voluntarily agreeing to access encrypted content is not comparable to slavery.
- krasin 13y agofirst of all, I agree that my message was too short and didn't have any arguments to positively contribute to the thread. Sorry about that. Now, let me explain how did I come to this comparison (even if it seems rogue). To make it more specific, let's consider Raspberry Pi, which is one of the most open ARM boards and, at the same time, practices DRM. For example, its hardware video decoding capabilities might be unlocked, if a separate digital license is acquired in the store [1]. I am perfectly fine when people voluntarily agree to access encrypted content or "premium" functionality. The problem is that the need to put this DRM to the chip, has led to the decision of the manufacturer to make its GPU core a supervisor. GPU starts to work ahead of CPU, initializes its firmware and starts CPU at some point later ([2]). Additional GPU firmware (provided by a binary blob) may be loaded to support OpenGL and other related stuff [3]. Effectively, even if the user does not want to access an encrypted content or use the "premium" functionality, he is being kept in a jail to make sure this premium stuff is not used. Moreover, the supervisor capability of the GPU chip combined with a binary blob updates, makes it possible for the manufacturer to reduce the amount of allowed to the user. The user of the device is treated as a customer, and it's the manufacturer who is the owner of the device, not the user. Given these capabilities of the manufacturer over this aspect of the user life, we may start looking at the definition of slavery [4]: """Slavery is a system under which people are treated as property to be bought and sold, and are forced to work. Slaves can be held against their will from the time of their capture, purchase or birth, and deprived of the right to leave, to refuse to work, or to demand compensation.""" At least half of the definition applies: 1. The customers are treated as property to be sold or rented. There're video dongles/boxes on the market which stream content to the TV. They would often allow only a subset of the video services to be used, even if these services are freely available on the internet. The manufacturers of this devices may actually sell the access to the users of this device to the content providers. 2. The customers may be shown ads against their will and their user experience may be altered by the manufacturer w/o their consent or right to refuse. Again, that does not happen to the people, it happens to the customers, which appear as a virtual entity applied to the devices, but I really see some similarities. [1] http://www.raspberrypi.com/mpeg-2-license-key/ http://www.raspberrypi.com/mpeg-2-license-key/ [2] http://stackoverflow.com/questions/16317623/how-does-raspberry-pis-boot-loader-work http://stackoverflow.com/questions/16317623/how-does-raspber... [3] https://github.com/raspberrypi/firmware/tree/master/boot https://github.com/raspberrypi/firmware/tree/master/boot [4] http://en.wikipedia.org/wiki/Slavery http://en.wikipedia.org/wiki/Slavery
- zanny 13y ago> I'm okay with DRM It seems really defeatist to say this. You are a consumer. You have the ultimate vote on everything, with your wallet, with the only exceptions really being what you need to survive and whatever your government takes. And I don't think netflix is on par with eating. My problem is I have no idea what to do about the w3c. I'd really like to know what alternative network protocols for document rendering there are, because they are destroying the platform they are supposed to advance, community backlash be damned, they got bought off. I'm definitely looking into ways to get qml into browsers, though. I think qtquick apps as remote resources would be amazing, because they would be actual apps, not documents with scripts running on them.
- duncan_bayne 13y agoI've been hacking around with 'websites as Racket' ... the idea that you could use Racket's documentation format for, well, documents, and the Racket GUI for everything else. Much the same idea, just Scheme instead of QT. But I don't think it's too late for the W3C. I don't think they've been bought out in the strictest sense; rather, I think they've been subject to some very effective lobbying that has proved most persuasive ( a.k.a. 'crisis of representation; see http://boingboing.net/2013/06/06/w3c-insider-explains-whats-w.html http://boingboing.net/2013/06/06/w3c-insider-explains-whats-... ).
- girvo 13y agoI'll be honest, I can say that I don't mind it as I rarely consume media that we're discussing. If I do, it's one show rented on my Apple TV, and that's it, maybe once every six months.
- duncan_bayne 13y agoIf you don't frequently consume those media, then you should be doubly angry that the W3C might harm the Open Web to support it.
- zobzu 13y agoWell, this very push for DRM on the web is to change exactly that. It's to force you to use DRM-only content. So - yeah.
- shmerl 13y agoNo one should be OK with DRM if we want this garbage to be gone. If we are OK with it, how can we expect brain dead publishers to understand that it's not needed ever?
- zobzu 13y agoI'm not okay with DRM. It will never work on all devices. It will never work with all software. That's the nature of DRM. It's made to block playback on non-approved devices/software (and generally is a PITA even with approved stuff). There is an alternative which works on all devices and with any software. its called "not using DRMs".
- ppergame 13y agoTurns out, Chrome on Linux shipped with a Widevine CDM before any other browser (including Chrome on Windows).
- hsivonen 13y agoChrome for Linux indeed comes with libwidevinecdm.so, but still, Netflix is not letting the Chrome on desktop Linux play content even though Netflix allows Chrome OS to play content. So that libwidevinecdm.so isn't particularly useful to Linux users.
- pbhjpbhj 13y agoDRM destroys the possibility that the contract of copyright can be upheld. The contract is that we, the people, give - through our respective states - content producers a limited monopoly on reproduction [and modification, etc.] of artistic works in exchange for them being release in to the public domain at the end of that limited term. With DRM a content producer (or at least the rights holder) destroys the ability of the work to pass in to the public domain [effectively]. In other words applying DRM breaks the contract. This means that we, the people, should be under no obligation to provide the state enforcement to their monopolistic rights gained via that contract. There are ways the contract could be maintained under DRM [deposit an unblemished copy that can be released to all copy holders on expiry of the term] but I've never seen anything to suggest rights holders are acting to avoid breaching the central contract. This is pertinent because it's not just linux that will be cut out of being able to present this data [DRM protected works] but also the OS of those in the future who're supposed to get access to copyright works which are currently being locked for good by DRM techniques.