News for hackers. Stuff that matters.
Re:Requirements for DRM in HTML are confidential by Nursie on Monday January 13, 2014 @11:24PM (#7055365)
Great. DRM. The best example of shooting yourself in the foot ever.

Give customers encrypted content and the keys, try to prevent them from freely using the two together, undermine copyright fair use and first sale doctrines as you go along.

Intended effect - No Piracy

Actual effect - Paying customers get crippled products, pirates carry on regardless

It's crazy. And the more they try to lock it down the worse their products become and the better piracy looks in comparison. Pirates don't only beat the legit industry on price, they beat them on quality and availability. How can the industry allow this to stand? Let alone continue down the same path with their fingers in their ears shouting LALALALALALA I CAN'T HEAR YOU!?!

Re:Requirements for DRM in HTML are confidential by bitwize on Tuesday January 14, 2014 @03:51AM (#7056043)
Let me tell you how things work in the real world.

When the people with money say "we want this", you don't argue. It doesn't matter if it's technically infeasible. It doesn't matter if it won't have the intended effect. When the people with money want something, YOU GIVE IT TO THEM. And let them deal with the consequences. Otherwise, you won't get the business, and life can otherwise be made very, very difficult for you.

The people who run Hollywood have lots of money to play with. The people who run the Web companies want a piece of that action. Hollywood says "no can do unless we have reasonable assurance that due diligence has been done to prevent piracy -- that means DRM." DRM isn't really about being effective -- it's about providing a nominal barrier to piracy that will dissuade casual pirates outright, and in the case of serious pirates, provides something that can be "broken" so the studios can go after the person who broke it with civil and criminal copyright infringement claims. Now you know why the DMCA anticircumvention provisions exist: so the copyright industry can do with the law what DRM alone couldn't do.

So the Web either gets DRM, or Hollywood makes content available on proprietary platforms that provide it.

Money shapes reality in this world.

Re:Requirements for DRM in HTML are confidential by onli on Tuesday January 14, 2014 @04:27AM (#7056135)
Let me tell you something about the state of the real world: The content Hollywood produces is already fully available on the Web. They try to fight that, but they lose. So the w3c is in no position where it is necessary to accommodate them to get their content. Besides, for the w3c, where is the business incentive, where is the money involved?
Re:Requirements for DRM in HTML are confidential by flavor8 on Tuesday January 14, 2014 @07:04AM (#7056544)
> The content Hollywood produces is already fully available on the Web.

For people willing to pirate, it, yes. However, it's far less convenient to pirate movies and get them to your big screen TV than it was to use napster and listen to songs on your mp3 player. On the flip side, Netflix (i.e. content with DRM) accounts for roughly 1/3 of nightly internet traffic in the US. DRM facilitates consumer access to restricted content.

> Besides, for the w3c, where is the business incentive, where is the money involved?

The w3c is primarily an industry group. The players pushing DRM in HTML5 are Google, Netflix and Microsoft, all of whom have a business interest in being able to stream content via browsers.

Re:Requirements for DRM in HTML are confidential by marcosdumay on Tuesday January 14, 2014 @09:16AM (#7057131)
> For people willing to pirate, it, yes.

What good is protection against piracy from people not willing to pirate?

And no, pirated content is far more convenient than DRMed content. DRM can only reduce the conveninence, not increase.

Re:Requirements for DRM in HTML are confidential by flavor8 on Tuesday January 14, 2014 @09:30AM (#7057209)
> What good is protection against piracy from people not willing to pirate?

It's about business. Protection that works for 99.5% of the population is good enough for the old content industries. Netflix couldn't exist in its current form without DRM -- Netflix does not succeed because of novel technologies, but rather because of successful content licensing.

To be clear I'm not a fan of DRM, especially not when it's baked into the HTML standard.

> And no, pirated content is far more convenient than DRMed content.

I didn't say that - you're arguing against a position I didn't state.

Re:Requirements for DRM in HTML are confidential by esteb_li on Tuesday January 14, 2014 @08:22AM (#7056823)
I don't think it's the DRM that facilitate anything. DRM is a tradeoff between pirated stuff and going to the theater. Netflix is a legal Napster while Hollywood are content with DRM as good enough protection.
Re:Requirements for DRM in HTML are confidential by flavor8 on Tuesday January 14, 2014 @09:26AM (#7057183)
It does, in that it allows business agreements to be signed. Without DRM, old content industries aren't interested in playing.
Re:Requirements for DRM in HTML are confidential by andyzweb on Tuesday January 14, 2014 @09:28AM (#7057189)
and we aren't interested in the old content industries. they are "considered harmful" at best
Re:Requirements for DRM in HTML are confidential by talmand on Tuesday January 14, 2014 @11:19AM (#7057803)
If you're interested in their content, then you are interested in the old content industries. If you aren't interested in their content, then what they do will have little effect on you personally.

I require a definition of how they are "considered harmful" because I seriously doubt that.

Re:Requirements for DRM in HTML are confidential by duncan_bayne on Tuesday January 14, 2014 @03:59PM (#7059688)
EME is a good example of harm.
Re:Requirements for DRM in HTML are confidential by talmand on Tuesday January 14, 2014 @06:47PM (#7060636)
But how is it harmful to you personally exactly? How is it harmful to anyone?
Re:Requirements for DRM in HTML are confidential by duncan_bayne on Tuesday January 14, 2014 @06:53PM (#7060670)
It corrupts the Open Web, meaning that one cannot simply decide to write a web client that will be able to display any standards-compliant content. It corrupts the W3C, in that it weakens their position in maintaining the Open Web, and lessens their value in the eyes of everyone except for the MPAA and its ilk. It harms culture, in that valuable cultural artifacts will be locked up in a way that will render them inaccessible to future generations, or people on non-blessed hardware.
Re:Requirements for DRM in HTML are confidential by talmand on Tuesday January 14, 2014 @07:08PM (#7060744)
I'm still waiting for the explanation of how it actually causes harm. Most of what you describe is not exactly harmful and is easily dealt with.

What's to stop someone from creating their own web client that doesn't implement that part of the standard? Where's it written that we have to follow every bit of the standard as it is written? Who gave this select group of people that much power over the open web?

Personally, I think the W3C was approaching being corrupted long before this issue. Maybe not in the terms you are describing right now but I've had issues with the behavior of various standard bodies and browser providers that happen to be a part of these bodies for a while now.

As for artifacts of culture being locked away from future generations, that is a potential problem. But we all know a silly DRM scheme isn't going to stop that. But that kind of thing has been in practice for a long time, way before we had electronics and the human race seems to be moving along in despite.

To me, a better solution is to show that people are willing to move on from these aspects of culture that everyone is so hung up on. If enough people show that these schemes don't work in the long run the content providers are more apt to change their ways. Look at the music industry, it's vastly different than it was just a few years ago and continues to change. Let these people attempt their schemes, in the long run it will matter little.

Re:Requirements for DRM in HTML are confidential by duncan_bayne on Tuesday January 14, 2014 @07:37PM (#7060873)
So, to paraphrase, you think there will be no harm because the W3C isn't doing anything useful as things stand?
Re:Requirements for DRM in HTML are confidential by talmand on Wednesday January 15, 2014 @11:04AM (#7064080)
Doing nothing useful doesn't necessarily result in harm.

I keep pointing out that people are claiming that this is harmful in some personal way. I keep asking how. The best I've seen is that it creates harm to the standards, which is more about causing harm to the people who control the standards. This decision directly harms the standards body itself, it does not harm the open web. Corrupting the standards with bad decisions hurts the reputation of the standards body, which will eventually importance in the scheme of things. The open web will just move on to something else. The reason I say that is because if the web is truly open, it is free to ignore the "standards" it doesn't like. Meaning, the people who use it can choose to not participate. It's a standard because everyone agrees to use it together. If the people using the open web decide they don't like a browser that implements DRM they don't agree with, then they have the option to choose a browser that doesn't implement the DRM. If there isn't such a browser, the open web allows someone to create and share it with the masses.

If this decision actually causes harm to the open web, then it's not truly open because that implies no one can get around the decisions made by this select group of people. If that's the case, then the web doesn't sound very open as it stands today.

Re:Requirements for DRM in HTML are confidential by flavor8 on Wednesday January 15, 2014 @06:56AM (#7062842)
This entire thread was about hollywood. To say that we aren't interested in what hollywood produces is a strange assertion, or a rather narrow definition of "we".
Re:Requirements for DRM in HTML are confidential by smsm42 on Tuesday January 14, 2014 @04:39AM (#7056166)
The problem here it does not dissuade anybody. All TV content is available on torrents within hours of the release. All movies appear on torrents sometimes before, sometimes within days of theatrical release. Technical knowledge that is needed to obtain this content is pretty much downloading one piece of software and clicking one link.

>>> or Hollywood makes content available on proprietary platforms that provide it.

Let them. They will spend tons of money on it and all those money will go down the drain once somebody wakes up and understands that treating customers as customers is better than treating them as enemies.

Re:Requirements for DRM in HTML are confidential by Nursie on Tuesday January 14, 2014 @05:32AM (#7056304)
>> When the people with money say "we want this", you don't argue. It doesn't matter if it's technically infeasible. It doesn't matter if it won't have the intended effect. When the people with money want something, YOU GIVE IT TO THEM.

Strange how the general public don't get DRM-free movies from hollywood...

Either way, my point was exactly about 'Hollywood', if you want to call them that, it's them that are delusional about their ability to protect content with DRM.

>> Money shapes reality in this world.

In this case it sems to propagate delusions.

Re:Requirements for DRM in HTML are confidential by talmand on Tuesday January 14, 2014 @11:27AM (#7057857)
The general public doesn't have an issue with DRM, they happily purchase the content as-is today. They may grumble when they have to purchase a movie for the second or third time but they continue to do so. Therefore the public, being people with money, have stated overwhelmingly that they want content without stipulating anything about DRM, free or otherwise. You are attempting to apply your viewpoint on the general public, which clearly does not agree with you.

As for your statement that Hollywood is being delusional about DRM being able to prevent piracy. They are not delusional about it at all. They know exactly what's going on. They want DRM that prevents casual copying so that Uncle Bob doesn't give a copy of the latest movie to his entire family which is not an attempt at monetary gain. That way they only have to spend money going after serious piracy efforts that exist for the purpose of making money. Your statement assumes that Hollywood is being run by stupid people and that's a serious mistake to make in this type of debate.

Re:Requirements for DRM in HTML are confidential by Nursie on Tuesday January 14, 2014 @01:03PM (#7058572)
>> The general public doesn't have an issue with DRM, they happily purchase the content as-is today.

Do they?

>> They may grumble when they have to purchase a movie for the second or third time.

So not happily then. And not what they actually want.

>> but they continue to do so

Because the choice is that or piracy, and many choose piracy. 'Not participating in popular culture' is a choice, but it's never going to be a big one.

>> You are attempting to apply your viewpoint on the general public, which clearly does not agree with you.

The general public are dolts, but even you have admitted they grumble and don't get what they want.

>> They want DRM that prevents casual copying so that Uncle Bob doesn't give a copy of the latest movie to his entire family which is not an attempt at monetary gain.

Then they have failed, because cousin bill, Bob's kid, has that figured out on them innernets.

>> That way they only have to spend money going after serious piracy efforts that exist for the purpose of making money.

Serious piracy efforts like usenet, torrents, IRC etc? Nobody makes much money there. There are for profit piracy-streaming services that advertise I guess. Never seem to have much legal trouble.

>> Your statement assumes that Hollywood is being run by stupid people and that's a serious mistake to make in this type of debate.

It is. Powerful, litigious stupid people with a lot of vested, anti-consumer interests.

Re:Requirements for DRM in HTML are confidential by talmand on Tuesday January 14, 2014 @06:40PM (#7060605)
>> Do they?

Yes, yes they do. Take a look at the proceeds from those industries and tell me people are not handing over money for said content.

>> So not happily then...

Ah, I see the problem. When I said happily I meant this definition: "felicitously; aptly; appropriately". Meaning they pay because that's what they are supposed to do. My bad. What they want and what they do are two different things. You see, they don't want to pay for multiple copies but they do, not because of DRM. They do so because that's what they are "supposed" to do. This is more of a philosophical, economical, and/or legal issue they complain about, not technological. DRM is technology that most people are probably not even that much aware of in their day-to-day lives.

>> ... many choose piracy...

I didn't claim otherwise. But, as you say, they have the choice to not participate. That's my current answer to what I feel is outlandish cable subscription fees as compared to my perceived value of what they offer. It doesn't work for me, therefore I don't pay for cable. I use other means to access the media that I wish to consume.

>> The general public are dolts...

I think it's rude of you to apply your viewpoint on a large group of people that aren't even aware of your problem. Then when they don't go along with what you think they should be doing or what you think they should know, your method to convince them otherwise is to insult them? You're not going to win anyone over with your argument.

>> Then they have failed...

Due to record profits, I think the situation has worked out quite nicely for them. I think you are exaggerating in your own mind the number of kids who are sharing movies with their families and the impact this actually has.

>> Serious piracy efforts...

If you think trading torrents is serious piracy, then you need to read up on what true media piracy is. I'm not talking streaming or torrenting content. There are areas of the world where you can buy a perfect copy of a DVD or Blu-Ray for very little and the original content owners get nothing. It's a huge industry and I'm not talking just movies/music here. Plus in these areas this is practically endorsed by the local governments as legal. And I believe there's been a few cases of big-time streamers having legal troubles, Megaupload comes to mind. Before you say anything, that fell apart because of government incompetence, not because of the lack of anyone actually breaking the law.

>> It is...

Then you are naive. Stupid people don't make that kind of money and do the things they do. Just because you think they're stupid and you can cast opinions on things they do as stupid doesn't make it true. Their anti-customer interests, which is only a recent thing mind you, are possible due to carefully crafted legal systems that took years of planning and execution that you claim they are too stupid to have accomplished. If you're going to fight this battle then you need to understand what you're up against.

Re:Requirements for DRM in HTML are confidential by Nursie on Tuesday January 14, 2014 @10:11PM (#7061429)
>> Stupid people don't make that kind of money and do the things they do.

Very few people are intelligent in all areas, these people are clearly shortsighted and stupid in many.

I'm not going to address the rest of your comment, needless to say I disagree with pretty much everything you have to say on the topic, and I think that you set up and knock down a variety of convenient straw men on your response there.

Re:Requirements for DRM in HTML are confidential by talmand on Wednesday January 15, 2014 @10:57AM (#7064024)
I didn't claim they are smart in all things. I claimed they are smart in their own industry that they control.

But if you want to skip the rest of the response by claiming straw men without defending your claim then that's fine. Especially since you did it yourself with your "very few people are intelligent in all areas" comment. I was directly responding to your statements so I fail to see how the straw man fallacy applies. I did not present a distorted version of your position, I directly responded to it. But, who cares, it's only a discussion between strangers on the Internet. We're not creating world peace here.

Re:Requirements for DRM in HTML are confidential by yarou on Tuesday January 14, 2014 @01:33PM (#7058777)
Hollywood is delusional, though. They are missing out on a huge potential revenue stream by having DRM-free distribution platforms. Why was Megaupload so popular if people really liked DRM?
Re:Requirements for DRM in HTML are confidential by extrafox on Wednesday January 15, 2014 @03:31PM (#7065930)
So, you are saying that people went to Megaupload, not because it was free, but because it was DRM free?
Re:Requirements for DRM in HTML are confidential by talmand on Tuesday January 14, 2014 @06:16PM (#7060482)
What are the numbers for comparing the amount of people who used Megaupload versus people who just paid?
Re:Requirements for DRM in HTML are confidential by al2o3cr on Tuesday January 14, 2014 @09:04AM (#7057048)
"When the people with money want something, YOU GIVE IT TO THEM."

Apparently this applies to everybody except consumers.

Re:Requirements for DRM in HTML are confidential by makomk on Tuesday January 14, 2014 @08:59AM (#7057030)
Except that the Web's getting DRM exactly so that Hollywood can restrict content to proprietary platforms that allow DRM. Right now, the main use for HTML5's DRM support is DRM on Chromebooks - hardware that's only available from a handful of approved suppliers and is locked down from the hardware up to stop the user running any non-manufacturer-approved code on it. If you enable the ability to run your own code, the DRM module refuses to decrypt anything, and so far as I know no-one has found a way to bypass this.
Re:Requirements for DRM in HTML are confidential by vidarh on Tuesday January 14, 2014 @07:15AM (#7056584)
In reality, most of the pirate activity in this house is my 4 year old son watching full length pirated movies on YouTube.

There is no real barrier to piracy. There's a minimal barrier for the hottest Hollywood properties - meaning you have to go through the hassle of a torrent instead of just going to YouTube - but if you want the content for free bad enough, you'll get it. Usually before it is available through legal channels.

Re:Requirements for DRM in HTML are confidential by talmand on Tuesday January 14, 2014 @11:33AM (#7057909)
Actually, that wouldn't necessarily be considered piracy. Unless the laws have changed the last time I read up on it, this is legal on your part but illegal for the source of the stream.

Where your kid might be the factor in the piracy bit is in file-sharing, which makes you an uploader and not just a downloader.

Re:Requirements for DRM in HTML are confidential by duncan_bayne on Tuesday January 14, 2014 @04:23AM (#7056121)
> or Hollywood makes content available on proprietary platforms that provide it.

What's wrong with that scenario, exactly?

Re:Requirements for DRM in HTML are confidential by espadrine on Tuesday January 14, 2014 @05:29AM (#7056294)
>> or Hollywood makes content available on proprietary platforms that provide it.

> What's wrong with that scenario, exactly?

Nothing. It's the current scenario. It can bother users, but overall it bothers big media, because piracy is active and well on those proprietary platforms. That's the complaint we hear from them.

There's a large part of W3C that want change so that people with disabilities (such as poor vision) can enjoy big media products. Of course, that assumes that big media cares about implementing the ARIA stuff. I personally believe that their not caring in the past, on proprietary platforms, is an indication of what they'll do in the future, on the Web.

Re:Requirements for DRM in HTML are confidential by fafner on Tuesday January 14, 2014 @01:02PM (#7058570)
> So the Web either gets DRM, or Hollywood makes content available on proprietary platforms that provide it.

DRM in the Web will be a proprietary platform! The EME proposal is a proposal to make the former open Web depend on proprietary platforms. The actual DRM is not specified (how could it be?) and it only proposes an API the browser should provide for the proprietary binary blob DRM.

This is a really horrible step and an attack on the open Web! I'd much rather have Netflix and Hollywood use a completely proprietary DRM platform for their streaming services than them ruining the Web.

Re:Requirements for DRM in HTML are confidential by bgruber on Tuesday January 14, 2014 @09:05AM (#7057056)
> So the Web either gets DRM, or Hollywood makes content available on proprietary platforms that provide it.

so, let's turn the web into another proprietary platform?

Re:Requirements for DRM in HTML are confidential by talmand on Tuesday January 14, 2014 @11:35AM (#7057928)
Or maybe make a small part of the web, which already has proprietary elements to it, have a new proprietary element that you can freely decide to not participate in.
Re:Requirements for DRM in HTML are confidential by byuu on Tuesday January 14, 2014 @12:00AM (#7055484)
The DRM is becoming increasingly complex and elaborate, and taking longer and longer to fully crack. Compare PS2 to PS3 crack times, for instance.

The media executives are of the firm belief that unbreakable DRM is just around the corner, and that when they reach it, piracy will end and they can go back to charging whatever they want again. A return to the good old days of $25 CDs for one song you like and eight filler tracks.

But as far as music and movies go, the genie's already out of the bottle: even with unbreakable DRM, we can always fall back on old camcorders / capture cards and microphones to make lossy copies. I think most pirates will tolerate a bit of quality loss if it saves them heaps of cash.

I think they will ultimately succeed in game DRM that remains unbreakable for the entire duration of a game's market viability, though. Especially with required online connectivity components. But only time will tell.

Re:Requirements for DRM in HTML are confidential by nemothekid on Tuesday January 14, 2014 @03:02AM (#7055944)
The PS3 only went uncracked for so long because Sony offered the option to install Linux on the PS3. Once Sony removed that option the people with the smarts to crack the PS3 did so. Once a magnifying glass was put under the PS3 it turned out that the "DRM" was actually horribly implemented (like Rand() functions that were essentially returning constants).

http://www.youtube.com/watch?feature=player_detailpage&v=4lo...

Re:Requirements for DRM in HTML are confidential by x123 on Tuesday January 14, 2014 @04:19AM (#7056111)
> The PS3 only went uncracked for so long because Sony offered the option to install Linux on the PS3. Once Sony removed that option the people with the smarts to crack the PS3 did so.

It's funny how the facts change over time. Just to correct the facts here: the reveal of the PS3 hack occured on January 26, 2010 and then OtherOS support was removed on April 1, 2010 citing security concerns as the rationale. And to top it off: if you look at the hacker's reasons for hacking, Linux was nowhere in his motivations.

Off topic: This is why I hate history. If we can't even remember what happened 3 years ago even if we have all records available at our fingerprints then how can we be sure what happened like 100 years ago?

Re:Requirements for DRM in HTML are confidential by ZenoArrow on Tuesday January 14, 2014 @05:13AM (#7056256)
You've misunderstood the facts. The PS3 security was not fully compromised with the first hack, and locking down the console was a motivation to those who ended up cracking the security properly (news released December 2010). Watch this... http://www.youtube.com/watch?v=HEFMAP0mTvY#t=0
Re:Requirements for DRM in HTML are confidential by deelowe on Tuesday January 14, 2014 @07:30AM (#7056631)
Doesn't change the fact that Hotz was working on the crack before otheros was removed. So, the removal of otheros was not the seminal moment that the op described. That is, the ps3 did not take so long to crack due to insufficient motivation. It took as long as it did, because it was a more difficult platform. There are similar trends in other areas as well like rooting/jailbreaking phones and installing Linux on UEFI machines.
Re:Requirements for DRM in HTML are confidential by ZenoArrow on Tuesday January 14, 2014 @09:24AM (#7057168)
Hotz's hacking may have been a contributing factor for getting OtherOS removed, but it's removal does appear to be a motivation to those behind the more complete hacks that followed (I believe it's mentioned in the video series I linked to). So with a timeline of April 2010 to December 2010, fully exploiting the PS3 security took less than 12 months.
Re:Requirements for DRM in HTML are confidential by deelowe on Tuesday January 14, 2014 @12:04PM (#7058141)
Sure, but I think that's orthogonal. My comment is addressing the OPs original premise. I seriously doubt there were hackers sitting around saying "we'll leave the PS3 alone as long as OtherOS stays supported." While removing OtherOS certainly brought more attention to the platform and accelerated the hacking, I think the reason it took so long for the PS3 to be finally cracked mostly had to do with the complexity of the architecture or other things. I don't think OtherOS was a factor.

As a counterpoint, I offer the xbox 360, which to my knowledge has not been cracked except for DVD firmware hacks and physically altering the device (mod chips).

The conclusion of this is that hackers will not continue to win the DRM battle. Eventually, enough holes will be plugged, where cracking these products becomes so time or cost prohibitive that the product stays closed for it's lifetime.

Re:Requirements for DRM in HTML are confidential by gcb0 on Tuesday January 14, 2014 @03:36AM (#7056015)
i don't follow sony because i don't consume from companies with lock in tactics (betamax, laserdisc, md, memory stick, etc, etc) but thank you for that. it was awesomely entertaining.
Re:Requirements for DRM in HTML are confidential by talmand on Tuesday January 14, 2014 @11:39AM (#7057968)
So, your current living quarters has hardly any modern entertainment to speak of? Good thing libraries still exist.
Re:Requirements for DRM in HTML are confidential by gcb0 on Wednesday January 15, 2014 @12:48AM (#7061871)
I can garantee you i don't miss blueray as i did not miss laser disc.

Also it's much more convenient that my camera and phones use sd cards instead of memory sick..

You're point?

Re:Requirements for DRM in HTML are confidential by talmand on Wednesday January 15, 2014 @10:50AM (#7063980)
Oh, don't get me wrong, I have no point per se. I'm just amazed that someone has gone that route in this age of apathy. But I am assuming this extends beyond Sony products as many electronics are along the same lines in terms of locked environments.
Re:Requirements for DRM in HTML are confidential by byuu on Tuesday January 14, 2014 @08:38AM (#7056911)
Yes, they certainly made mistakes with the PS3 crypto. And those mistakes are now certainly fixed in the PS4.

Although it sounds poetic, I don't believe for a second that the PS3 was protected by offering a limited Linux install option with crippled software graphics. The timing of the break just coincided well with that. Of course this is all my opinion on the matter.

The PS4 lacks Linux install support completely, so if Linux was the protecting factor, then people should already be tearing it apart, right? I could certainly be wrong, and there could be a gaping flaw, but my hunch is that it's going to take longer than the PS3 to crack.

Re:Requirements for DRM in HTML are confidential by marcus_holmes on Tuesday January 14, 2014 @03:07AM (#7055954)
<quote>I think most pirates will tolerate a bit of quality loss if it saves them heaps of cash.</quote>

From the studies done, piracy is not about cash, it's about convenience, freedom, etc. If the studios released the content for free (as in beer) but DRM-encumbered then pirates would still be removing the DRM.

Re:Requirements for DRM in HTML are confidential by shmerl on Tuesday January 14, 2014 @12:24AM (#7055538)
DRM was and always will be pointless and insulting, no matter how elaborate it will become. Because it's not the right way to treat customers.
Re:Requirements for DRM in HTML are confidential by MichaelGG on Tuesday January 14, 2014 @01:37AM (#7055726)
DRM on a sealed hardware platform is entirely different than DRM on a consumer controlled device, which is what the HTML5 DRM plugin interface hopes to achieve.
Re:Requirements for DRM in HTML are confidential by mitosis on Tuesday January 14, 2014 @10:58AM (#7057673)
Do consumers really control their devices anymore? Maybe they still can, but in the industry, there's no doubt that this is viewed as a problem that needs solving.
Re:Requirements for DRM in HTML are confidential by pmr_ on Tuesday January 14, 2014 @04:03AM (#7056072)
How much quality loss people are willing to accept if they are not really keen on the content is astonishing. If you go to the pirate bay and look at some of the comments on the tele-synced copies, R6 with hardcoded Chinese subs and all the other sub-par quality rips there still is a large amount of positive feedback. Sure, there is always someone who doesn't know what any of the cryptic abbreviations in the title mean and is upset about the quality, but those seem a minority to me.

I would really like to see more scientific results on how low the quality can be if the viewer doesn't exactly desire the content but uses it to just pass the time and how that compares to the price of going to the cinema.

Re:Requirements for DRM in HTML are confidential by byuu on Tuesday January 14, 2014 @08:54AM (#7057005)
For music, I can go as low as 128kbps MP3 without noticing much of a difference, and 192kbps without noticing any difference.

For movies, I've always been perfectly happy with DVD recodes into 700MB XviD. Could probably go much lower if they were recoding from a lossless master and using H.265. For most things, the Bluray/1080p quality jump reveals details I don't want to see, like how caked on actor makeup is, and all of their skin complexion issues. Great for nature shows, though.

The cutoff points for me are 64kbps Shoutcasts and telesyncs. At that point, the quality is so bad that it makes me dislike the music or movie I am watching.

Re:Requirements for DRM in HTML are confidential by Perseids on Tuesday January 14, 2014 @06:23AM (#7056434)
Also, availability is a huge issue. For me in Germany it is nigh impossible to legally watch a recent episode of Game of Thrones. And Breaking Bad or Doctor Who has only recently become available via the new service watchever.de. And even there they are published far too late if you want to participate in the online discussion of an episode.
Re:Requirements for DRM in HTML are confidential by marcosdumay on Tuesday January 14, 2014 @09:14AM (#7057111)
There is another party that you are ignoring. DRM is pushed by plataform sellers, and from the point ofview of the plataform sellers:

Intended effect - Lock people into your plataform, and externalize the cost into content distributors

Actual effect - Exactly as intended