Earlier quoted context omitted.
It's just dumb. DRM is just dumb. It doesn't work for anything but the most naive case. It won't prevent distribution of "pirated" content, ever. Steam's DRM is why I've bought more games than I've pirated. iTunes DRM was why I've bought more songs than I would've pirated. They were both more convenient than pirating the content. Is a distribution channel a form of DRM?
Steam is still DRMed, in regards to the installers and for major part of the games even requiring Steam client to run them. GOG in contrast isn't, that's why I use GOG and other DRM free distributors, but not Steam.
The W3C's plan for DRM in HTML5 is a betrayal for all web users
111–120 of 158 posts
Re: The W3C's plan for DRM in HTML5 is a betrayal for all web users
#112Earlier quoted context omitted.
See below: https://news.ycombinator.com/item?id=5599601 DRM by definition implies security and privacy risk. Focusing on minor issue (native plugin) while ignoring the major one (DRM) sounds strange. And in reality this whole EME thing won't even remove native DRM code. It just will hook it into JavaScript. The risk caused by DRM won't get any less than it is already.
> DRM by definition implies security and privacy risk Source please
Re: The W3C's plan for DRM in HTML5 is a betrayal for all web users
#113Consumers don't care about implementation, they only care about the content, and until they do, suppliers of content hold all the cards. There is nothing to be won by resisting hooks for DRM in the browser however appealing it seems to take a principled stand. The content suppliers will gleefully go with native apps, flash, silverlight, even Emscripten-cross-compiled codecs. With content consumption going mobile, the…
Re: The W3C's plan for DRM in HTML5 is a betrayal for all web users
#114Once it's implemented, you can just patch Firefox or Chromium to dump the unencrypted video stream before sending it to the H.264/WebM codec, and you get an universal method to trivially liberate all "DRM"-encumbered web content.
Re: The W3C's plan for DRM in HTML5 is a betrayal for all web users
#115Earlier quoted context omitted.
You're assuming that blockbuster movies are a business model that will continue to work in the future. That's highly questionable - in the game industry developers and publishers are being forced to accept the possibility that the blockbuster model is no longer going to be a reliable source of revenue or the right way to develop things. I won't claim to know enough to say whether this is true for film or television,…
Possible, I'll buy that. Maybe YouTube will one day kill off the major networks and studios, and production will get cheap, just like startups have gotten a lot cheaper to run with EC2. But I'm still going to go see Iron Man 3 and Star Trek Into Darkness and I'm not holding my breath that a non-DRM version will be cooked up outside the blockbuster system anytime soon. :)
It looked very much like fans of Firefly would have been able to raise enough to continue making the series but they were given not very subtle hints than getting involved in a crowdfunded production would have been bad for the showbiz careers of those involved.
Re: The W3C's plan for DRM in HTML5 is a betrayal for all web users
#116Re: The W3C's plan for DRM in HTML5 is a betrayal for all web users
#117Re: The W3C's plan for DRM in HTML5 is a betrayal for all web users
#118Earlier quoted context omitted.
> Steam's DRM is why I've bought more games than I've pirated. Steam's DRM has nothing to do with why individuals buy games on Steam. Steam offsets the net negative of DRM by bundling in a number of very attractive value-adds, like the ability to reinstall your games on any system without media, keeping all your games up to date for you, syncs settings and such (for Steamworks games) and provides an attractive platfo…
There is at least one game I would have pirated, but could not find a functional pirated copy of, so I bought it on steam. If steam had no DRM I am confident it would have been much easier for me to pirate it (I would have copied it from the friend who suggested it to me).
I went to pirate a film last year. Mind you, it was a film I had purchased but I didn't have it on holiday with me so I thought about just downloading it on a torrent site. But then I noticed YouTube offered the same movie for £2.50 rental, streamed on a fast connection in HD 1080p. That is what stopped me pirating it. Not because I couldn't find it, but because I found an option that was more convenient than waiting 8 hours for a download.
That's what Steam does really well. Why would I bother pirating that game, when I can pay a pretty small fee and have it ready to play within half an hour tops?
Re: The W3C's plan for DRM in HTML5 is a betrayal for all web users
#119Earlier quoted context omitted.
Emscripten cross-compiled codecs are better than black-box, closed source DRM codecs built into partially or fully proprietary browsers like Chrome and Internet Explorer. Do you really think a DRM plugin would ever work in Firefox or Chromium? If they really want to ship DRM, they can do it using the same tools everyone else uses, without special monopoly-preserving treatment or 'protected media paths' or kernel hook…
The problem is that they know as well as we do that DRM doesn't work Unfortunately, as much as some of us would like that to be true, it seems very unlikely. DRM isn't some binary thing where either it prevents copying 100% or it doesn't; it's a deterrent. It works as long as it stops/delays anyone from copying the product illegally so they get it through a legitimate channel instead. It works and is cost-effective i…
The fact that such people consume big media content now does not mean they wouldn't rather dispense with such content in exchange for the elimination of such laws.
In fact, an argument could be made that the production of such content smothers other, less capital intensive content made with lower expectations of large returns (for example, theater was much more successful around here before the big Hollywood blockbusters came to the scene).
However, the same conditions are toxic to smaller, independent content producers who might have done something innovative or catered to a niche market.
I don't doubt that the current conditions are toxic, but I don't think "those people" argue that the status quo is OK. Whether the conditions they argue for are toxic or not remains to be seen.
Re: The W3C's plan for DRM in HTML5 is a betrayal for all web users
#120Honestly, rants like this sound a lot like "allowing same-sex marriages will destroy the sanctity of marriage" and alike. How exactly?
Will the ability to have DRM'ed content in HTML suddenly shut down "the open web"? No.