News for hackers. Stuff that matters.
Re:Tell W3C: We don't want the Hollyweb by Daiz on Friday March 22, 2013 @11:44AM (#5423627)
I'm actually a bit conflicted about support for DRM schemes in HTML5.

I absolute loathe DRM and I wish every damn publisher of every damn type would come to their senses and actually sell DRM-free digital products.

However, there is one case where some form of "DRM" does make sense, and that's actual renting - or more specifically, the popular case of "catalog subscription" (ala Spotify, Netflix and so on). You're clearly renting access to a catalog of goods in this kind of model, and therefore it makes sense that you'd want to stop people from permanently acquiring copies in such a scenario, especially if you're selling actual DRM-free downloads at the same time (in my ideal digital store where it makes sense they would offer both of these side-by-side). The catalog subscription model has some clear value to it, and I'd hate for it to disappear due to "technical unfeasibility".

As such, I would at least prefer for most of the tech / architecture to be based on HTML5 stuff instead of closed plugins like Flash, Silverlight, Widevine and so on. I can't really think of a good solution to this, unless you got the big wigs at various publishing outlets to accept that to do HTML5 streaming, you can only make downloading the rentable versions inconvenient for regular versions (instead of being able to use a heavy-weight closed DRM plugin), but I'm afraid that could be quite challenging. It has worked for Adobe and webfonts, though[1], so maybe there's hope. Forcing HTML5 to be DRM-free could eventually lead to this direction.

[1] http://blog.typekit.com/2009/07/21/serving-and-protecting-fo...

Re:Tell W3C: We don't want the Hollyweb by MatthewPhillips on Friday March 22, 2013 @11:58AM (#5423737)
> As such, I would at least prefer for most of the tech / architecture to be based on HTML5 stuff instead of closed plugins like Flash, Silverlight, Widevine and so on.

It's not really based on open stuff. EME isn't DRM, it provides a way to talk to a DRM service (probably a hardware DRM in most cases). They are creating a false-sense of "open standards" when this thing still won't work in Linux and most not-locked-down platforms.

Re:Tell W3C: We don't want the Hollyweb by Daiz on Friday March 22, 2013 @12:07PM (#5423807)
Yeah, that's the impression I've got as well, which is why I don't ultimately like EME. It would be a slight improvement compared to the current situation (since you could at least move stuff like video playback to HTML5), but would probably just make the situation of "closed binary blob DRM" more persistent and thus worse in the long run.
Re:Tell W3C: We don't want the Hollyweb by eridius on Friday March 22, 2013 @11:53PM (#5427179)
Unfortunately, this sort of problem is basically unsolvable for Linux (and other such "open" platforms). Either you get a proprietary blob that implements a protection scheme, or you simply don't get the functionality being promised.

Objecting to efforts to make the situation better for HTML5 experiences on other platforms because it won't work on Linux is, honestly, pretty selfish. It can't work on Linux, so you're basically saying since it can't work for you, it shouldn't work for anyone else too. And that's just dragging down the state of the web to the lowest common denominator.

Re:Tell W3C: We don't want the Hollyweb by summerdown2 on Saturday March 23, 2013 @06:21AM (#5427717)
> And that's just dragging down the state of the web to the lowest common denominator.

Or up to the state of most openness?

Re:Tell W3C: We don't want the Hollyweb by eridius on Saturday March 23, 2013 @03:56PM (#5429508)
Leaving out functionality because Linux can't support it isn't dragging anything up.
Re:Tell W3C: We don't want the Hollyweb by bzbarsky on Friday March 22, 2013 @10:22PM (#5426995)
It provides a way for script to talk to a DRM service. Assuming the browser has a way to talk to one already. It doesn't do anything towards providing a way for _browsers_ to talk to DRM services; that's up to the browser manufacturers to license or whatnot.
Re:Tell W3C: We don't want the Hollyweb by yarrel on Friday March 22, 2013 @11:48AM (#5423659)
Renting infinitely copyable goods doesn't make sense.

Subscriptions to channels containing them does.

DRM doesn't increase the convenience of those channels. It reduces them.

Re:Tell W3C: We don't want the Hollyweb by Daiz on Friday March 22, 2013 @12:02PM (#5423777)
The problem I have is that I can't really imagine the catalog subscription model to be feasible if any and all catalog entries were available to download without DRM. Someone with a fat pipe could just spend a month downloading absolutely everything, cutting the subscription and enjoying the goods for a long time to come, whereas the idea is that the user remains as a subscriber because of the limited time they have for consuming all the content.

And while DRM is generally very inconvenient, there are also places where it's mostly "invisible" - Spotify and Netflix are pretty damn convenient on the whole, with pretty much the only major downside being the inability to watch stuff without an internet connection (though Spotify offers limited offline downloads for this reason too). The DRM in Steam is also generally quite invisible to the end-users, which is why people generally do not mind it - and also because Steam offers a lot more convenience with its service than what it takes away with its DRM.

As I said, ideally I'd like to see digital stores that combine the catalog subscription model as well as individual DRM-free purchases. Think Netflix, except you could also buy the really good stuff that you like. This would allow you to download DRM-free copies in many formats whenever you want, they could also bundle purchases with stuff like extras, and best of all: since they have a streaming infrastructure in place already they could also offer unlimited streaming for bought titles, even if you don't have a subscription. I imagine it would make for quite the killer service. But if everything could be downloaded DRM-free with just the catalog subscription, the individual sales would not work, and subscriptions would probably have a terrible retention rate.

Again, I just can't see the catalog subscription model working without at least some sort of "download prevention". I guess the biggest question is: Can we achieve that without the need for heavyweight black-box DRM schemes? I mean, you'd really just need to stop "casual" downloading - pirates will always find a way around protections, so they can't be stopped, but you'd just have to make sure a regular customer sees value in both the catalog subscription (which would be essentially renting) and individual title purchasing (actual buying).

Re:Tell W3C: We don't want the Hollyweb by incongruity on Friday March 22, 2013 @01:26PM (#5424285)
Are you looking for a 100% solution? If so, you'll never find it.

Instead, you need to think about how you make offerings cheap enough and compelling enough that a sufficient number of users will choose them over pirating.

There will always be pirated content. However, thankfully, most people are also more or less honest and well-inentioned. The two balance out to a great degree. So what tips the balance is how you treat your customers – does it become painful to deal with your product because of all of the DRM? Do you treat consumers like criminals? Is it significantly less hassle to pirate than it is to buy/rent/view legally (and likely pay for)? If any of those are true, you will tip the balance away from a completely successful business model.

Every business model has inefficiencies in the supply chain. Much of it falls under what's called "shrinkage". Sometimes it's from theft, other times it's from spoilage, weather, etc. The truth is, just like in heating, cooling, power production, engine design or anything else, you can never achieve 100% efficiency and in the case of consumer-facing products and services, I suggest you re-evaluate such pursuits before they ruin what otherwise would have been a profitable business model because you've alienated your customers.

Re:Tell W3C: We don't want the Hollyweb by takluyver on Friday March 22, 2013 @02:25PM (#5424665)
There's nothing about DRM that intrinsically must be obnoxious to the user - setting aside the issue of control over your devices, because so far that's not something that much of the population cares about.

Yes, lots of companies have implemented DRM in really terrible ways. But there are also examples of DRM that users are perfectly happy with. BBC iPlayer uses some very trivial DRM so that their programmes are available for a limited time, usually a week. It's easy enough to bypass, but people mostly don't bother: it doesn't get in the way, and I think people understand why it's time limited.

Re:Tell W3C: We don't want the Hollyweb by rayiner on Saturday March 23, 2013 @01:04PM (#5428834)
Netflix has reached the convenience level for me. I didn't even know it had DRM nor do I have any reason to care. Netflix, Spotify, etc, are the future of content online: unobtrusive DRM with subscription oriented payment.
Re:Tell W3C: We don't want the Hollyweb by incongruity on Saturday March 23, 2013 @10:01PM (#5430746)
I'd even argue that just in time streaming with minimal buffering is its own form of copy protection - it just gets to be too slow to make it worth the while to copy en masse.
Re:Tell W3C: We don't want the Hollyweb by incongruity on Friday March 22, 2013 @04:04PM (#5425303)
Exactly – as I said, if you're looking for anything approaching a 100% "protection", then it's my contention that it will long since crossed that line into obnoxiousness.

Your point about trivial DRM working well exemplifies just makes my point –- "does it become painful to deal with your product because of all of the DRM? Do you treat consumers like criminals? Is it significantly less hassle to pirate than it is to buy/rent/view legally (and likely pay for)? If any of those are true, you will tip the balance away from a completely successful business model."

If the DRM is minimal and unobtrusive, then it doesn't meet my stipulations, above, and it's probably found some sort of happy-medium. (FWIW, I think most of Apple's DRM approaches in the iTunes store have gotten close, except for the device lock-in)

Re:Tell W3C: We don't want the Hollyweb by chacham15 on Friday March 22, 2013 @10:20PM (#5426985)
I think that you are missing something very critical: technology given us new tools the past twenty years which make previous ones more obsolete. Its the idea of creative destruction. When the car was invented, the horse-buggy industry died. In our case, the horse-buggy is the music cd industry. Instead of the industry trying to find a new business model with the emerging technology, they are trying to force us to stay with the old model. Fortunately, other companies have innovated in place of the RIAA (and MPAA) and we have services like Spotify, Pandora, and Netflix.

Do not confuse these companies with the industry itself. Especially with the music companies (Spotify and Pandora) the companies are paying ridiculous royalties on the music they play (especially when compared with an actual radio station). I can tell you that Pandora does not use DRM for the music that they play for you (about a year or two ago I sniffed the traffic and found raw mp3s being transferred, they might have changed that but I hope not). Still, I did not see people simply downloading all of Pandoras music. If people wanted to do that, there are much better ways (a la bittorrent).

Therefore, the real issue here is control. The industry wants to control what you can and cannot do; even more so than they used to be able to. For example, adding music to a home video which you post on youtube is something they dont want you to be able to do. You have the legal right to do so, but they still dont want you to. (You have the legal right to do so, so long as it is a creative use not meant for monitization, etc.) As long as the DRM provider allows you to do what you want to do, it can be seamless. But as soon as you want to step outside those bounds (whether within your legal right or not) theres going to be friction. I bet that people who like making videos with popular songs playing in the background have more of a problem with spotify than people who simply like listening to radio.

Re:Tell W3C: We don't want the Hollyweb by zanny on Friday March 22, 2013 @01:43PM (#5424376)
> Are you looking for a 100% solution? If so, you'll never find it.

I dunno, getting paid to make information-based content (which includes anything you can stick on a hard drive) by the people that want the content, rather than by people who want to try to profit off its artificial scarcity, could probably be a 100% solution.

Because then the information you have you can treat like anything else you own - you can share it, spread it, etc, without fear, and the content creator got paid by people that wanted it made.

I mean, it would be a culture shift, but it is a 100% solution. Piracy doesn't matter if the point of profit isn't in per-goods sales but in goods creation, where the actual costs lie.

Re:Tell W3C: We don't want the Hollyweb by tjcelaya on Friday March 22, 2013 @02:31PM (#5424694)
I'm having trouble understanding what you mean by people paying for the creation of goods by the people that want the content. The division between paying for DRM-free content and the creation of that content seems contrived unless you're saying that consumers would pay the content creators directly so that more content can be produced, but that would make it problematic for up and coming artists to break into the market.

Don't take this as an argument, I'm just asking for clarification.

Re:Tell W3C: We don't want the Hollyweb by Silhouette on Friday March 22, 2013 @10:45PM (#5427059)
I dunno, getting paid to make information-based content (which includes anything you can stick on a hard drive) by the people that want the content, rather than by people who want to try to profit off its artificial scarcity, could probably be a 100% solution.

Unfortunately, by simple economics, that works only if you can find a sufficient number of people to entirely fund the sunk costs and an acceptable level of profitability up-front, allowing the low marginal costs to be written off. This is the classical patronage model, or in more modern terms, something like Kickstarter.

On Kickstarter, a project that has experienced, well-known, credible people behind it might reach seven figures of funding, though that is a significant success and relatively rare. I'm all for cutting out the middle man and for curtailing the exorbitant fees commanded by a handful of A-lister actors/singers/producers/whatever, but raising a few million a handful of times each year still isn't going to fund the big media industries, not by a long shot.

That culture shift you're talking about would be necessary and dramatic for this idea to work, and that's not going to happen any time in the immediate future, so what's your proposed solution to keep people getting paid to make good content tomorrow?

Re:Tell W3C: We don't want the Hollyweb by anigbrowl on Friday March 22, 2013 @06:44PM (#5426251)
Netflix streaming is only $8/month, how much cheaper does it need to get before it's better than pirating?

There will always be pirated content. However, thankfully, most people are also more or less honest and well-inentioned.

I think this is likely true, but it's not something you can just take to the bank. Making a movie is a very expensive business venture because people have pretty high expectations for what constitutes a minimum viable product.

Re:Tell W3C: We don't want the Hollyweb by incongruity on Friday March 22, 2013 @07:20PM (#5426423)
I think Netflix does a great job of proving my point. Streaming big content at a rate equal to viewing speed makes a weak target for pirating and helps keep people honest, IMHO.

Tell me again why we need DRM in HTML5? How many people are actively going out of their way to pirate the movies and shows from Netflix?

At the end of the day, pirating from Netflix: A) takes a lot of time (a bit of analog DRM, if you will as the rate is a huge limiting factor) and B)Takes a decent amount of disk space. Sure, storage is cheap, but what advantage does it give me over just keeping a netflix subscription? Not much, IMHO.

So, the upshot is that, pragmatically, I just don't see why Netflix needs DRM in the HTML Spec.

Re:Tell W3C: We don't want the Hollyweb by mtrimpe on Friday March 22, 2013 @01:12PM (#5424192)
The problem is that you'd need a fully locked-down chain, all the way from server to monitor, to be able to pull that off.

Every single one of the devices in that chain has to be reduced to a black box which we're not allowed to tamper with.

Hollywoord is trying hard to actually achieve that, and that is the scary part.

Re:Tell W3C: We don't want the Hollyweb by recoiledsnake on Friday March 22, 2013 @01:30PM (#5424305)
Not really true, Hollywood just needs to make it inconvenient for casual users to make copies and give to their friends etc.
Re:Tell W3C: We don't want the Hollyweb by pdonis on Friday March 22, 2013 @04:12PM (#5425364)
Tell that to Hollywood. This may be all they actually need, but it's not all they're asking for, not by a long way.
Re:Tell W3C: We don't want the Hollyweb by fzzzy on Friday March 22, 2013 @01:06PM (#5424162)
"Download prevention" is impossible. The analog hole cannot be closed. If it can be delivered to our senses, then it can be copied.
Re:Tell W3C: We don't want the Hollyweb by TheCoelacanth on Friday March 22, 2013 @12:53PM (#5424080)
Even with DRM, I wouldn't be subscribed to a service for long if it wasn't continually adding new content.
Re:Tell W3C: We don't want the Hollyweb by dreamdu5t on Friday March 22, 2013 @03:24PM (#5425040)
I buy music on bandcamp all the time, yet I could pirate it. It's often more convenient.

Can't explain that!

Re:Tell W3C: We don't want the Hollyweb by wnight on Friday March 22, 2013 @11:31PM (#5427132)
> [But what if ...]

Yeah, and it already happens. More-over, I go out of my way to give people SD cards full of textbooks, HDs full of books, etc, and even the odd hollywood movie here and there, to make it happen.

So why not pull our heads of out the sand. After thousands of years of grubbing in the mud we've finally got the technology to give everyone a copy of everything worth knowing. So let's do it now, and reap the societal benefits, while thinking of how to reward the creators, instead of sitting and lamenting while it inevitably happens.

The US constitution gave congress the ability to grant monopolies to encourage the public good; it didn't declare that this was the best method, or require it actually be used. The constitution should read "Congress is given the ability to encourage creation of knowledge, including the power to grant limited monopolies where necessary", instead of suggesting them as the go-to strategy.

Re:Tell W3C: We don't want the Hollyweb by webreac on Friday March 22, 2013 @12:01PM (#5423764)
Watermarking makes a lot more sense than DRM. If your name is on the film you just bought, you will not want to publish it on p2p.
Re:Tell W3C: We don't want the Hollyweb by Daiz on Friday March 22, 2013 @12:12PM (#5423842)
It wouldn't really be a feasible solution for video, though. You'd have to re-encode the whole thing for every individual user, which would be incredibly inefficient. Even if you're showing the watermark in just a few places, it'd still require a damn lot of resources. There's also quite a few things out there for removing video watermarks[1], so unless the watermarks were incredibly obtrusive, they'd probably be quite easy to get rid of. And of course you couldn't really put the watermark outside the actual video stream either, since then the user could just strip it out.

[1] Like various Avisynth plugins for example: http://avisynth.org/mediawiki/External_filters#Logo_Removal

Re:Tell W3C: We don't want the Hollyweb by im3w1l on Friday March 22, 2013 @01:50PM (#5424433)
You could split the stream into N chunks. Every time you watch the movie, M of them are selected and fudged just a little bit. Since M << N, this can be done in real time. The next user sees the same chunks you saw, except that some new chunks have been fudged also. Thus the movie slowly drifts away from the original. To counteract this, fudges are more likely to carry the chunk towards the original then away from it. This is what I came up with in 5 min, so there might be problems with the approach.
Re:Tell W3C: We don't want the Hollyweb by derefr on Friday March 22, 2013 @08:05PM (#5426610)
Sounds like the steganographic equivalent of Y-chromosome genotyping.
Re:Tell W3C: We don't want the Hollyweb by Silhouette on Friday March 22, 2013 @10:37PM (#5427041)
You'd have to re-encode the whole thing for every individual user, which would be incredibly inefficient.

It would be inefficient, but not necessarily prohibitively so if you're talking about the kind of business where piracy is a serious problem so there is real money to spend.

There's also quite a few things out there for removing video watermarks

If you're operating on the kind of level we're talking about, you don't just put in a visible watermark, you convert the entire file/stream to embed a unique forensic footprint tied to the account of whoever downloaded it. Such a footprint will stand up to just about any manipulation you can think of that doesn't reduce the quality of the data so much that the value is destroyed anyway, and you're probably not removing it unless you have a PhD or two in the field and you know someone's secret key.

The limitation with any watermarking approach is that fundamentally it's still based on the honour system and obviously does nothing to prevent private copying between people who don't care about ripping someone off. It's not a technical limitation.

Re:Tell W3C: We don't want the Hollyweb by benologist on Friday March 22, 2013 @12:23PM (#5423910)
Is it really true that they can't do it on the fly? Live streaming is creating the video on the fly completely isn't it?
Re:Tell W3C: We don't want the Hollyweb by trotsky on Friday March 22, 2013 @01:13PM (#5424201)
no, they can do it. There is overlay support in current generation iptv support that can target scrolls and texture replacements at a resolution of less than a zipcode. Take that gear and apply a few static watermarks with timecodes and then swap the different streams at unique times for each viewer and you can end up with a stream thats uniquely identifiable.

Motorola's (Google) new gear can do this, though the purpose is targeted advertising not watermarks. The truth is streaming DRM is about preventing your mother from giving a copy to the neighbors, almost all the content is already on P2P by the time it streams.

Re:Tell W3C: We don't want the Hollyweb by Daiz on Friday March 22, 2013 @12:36PM (#5423982)
In case of live streaming, the video is only encoded once and then distributed to a whole bunch of users. If you were doing unique watermarks, you'd have to encode an individual stream for every single user. Encoding is much more taxing than decoding. The end result would be that you'd need a metric crapton of additional processing power, and the quality would be worse since you'd have to use sufficiently fast encoding settings to be able to do it in realtime (as opposed to being able to use a lot more expensive options when the encoding is done just once and separately from the actual streaming process).
Re:Tell W3C: We don't want the Hollyweb by benologist on Friday March 22, 2013 @02:36PM (#5424724)
What about onlive, they stream(ed) cpu/gpu intensive games in real time on a one-to-one basis?
Re:Tell W3C: We don't want the Hollyweb by coldtea on Friday March 22, 2013 @06:05PM (#5426081)
No, they don't. You have the game assets downloaded already on your PC. They just stream control messages (move the camera there, that player hits the other player, etc).

Real time gaming is not streaming video...

Re:Tell W3C: We don't want the Hollyweb by jbri on Saturday March 23, 2013 @12:06AM (#5427197)
OnLive[1], which is what was being talked about, is literally streaming video to you of a game that's running in a datacenter somewhere.

[1]: http://en.wikipedia.org/wiki/OnLive

Re:Tell W3C: We don't want the Hollyweb by wmf on Friday March 22, 2013 @04:36PM (#5425533)
There's been some interesting research on compressed-domain forensic watermarking; check it out.
Re:Tell W3C: We don't want the Hollyweb by mseebach on Friday March 22, 2013 @01:18PM (#5424228)
A film I just bought to play on my fairly high-end setup damn well better not have my name anywhere in the picture.
Re:Tell W3C: We don't want the Hollyweb by bsimpson on Friday March 22, 2013 @12:01PM (#5423765)
Is anyone here familiar with the proposed spec? Would the DRM be a private binary included with the OS, or an open part of the browser? Unless they're just specifying an API, and all the actual work is done in a private binary, I don't understand how you can have effective DRM in a publicly specified project.
Re:Tell W3C: We don't want the Hollyweb by MatthewPhillips on Friday March 22, 2013 @12:03PM (#5423781)
Could be a private binary, could be a hardware component, but yeah, the actual DRM part is not in this spec.