Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Requirements for DRM in HTML are confidential

lists.w3.org

Post reply on HN
Print view View original

151–160 of 424 posts

Re: Requirements for DRM in HTML are confidential

#151

Post by Daiz »

This should really be at the top of every HTML DRM discussion:

HTML DRM will not give you plugin-free or standardized playback. It will simply replace Flash/Silverlight with multiple custom and proprietary DRM black boxes that will likely have even worse cross-platform compatibility than the existing solutions. In other words, giving in to HTML DRM will only make the situation worse.

Some vendors will keep pushing for it, but at the very least we should not officially sanction what they are doing.

Re: Requirements for DRM in HTML are confidential

#152

Post by gcb0 »

ekianjo wrote: post #147
darklajid wrote: post #143

Earlier quoted context omitted.

Can you explain the "no backups" part? I'm sure you know about the backups you can create in Steam itself, bundling the application. What is the missing detail? Being unable to extract the data again, without Steam? Is Steam unable to restore these bundles in offline mode?

Steam will require you to be connected to their servers once in a while at least. There's no pure offline mode.

steam is just like any other drm system for your games. it phone home and prevents you from playing without a connection to the mothership.

they just have saner fallback times than other ill talked solutions from EA. but besides its pretty eyes, its the same virus.

good luck running online games as root.

Re: Requirements for DRM in HTML are confidential

#155

Post by gcb0 »

gfosco wrote: post #139
MichaelGG wrote: post #126

Earlier quoted context omitted.

Which seems more rooted in the overall ease-of-use and lock-in Steam creates as well as goodwill towards Valve from their games. Steam's terrible - fight them on a transaction, and you could lose your entire library.

Maybe if you're a total jerk about it?... I purchased the full iD collection once for like $90+, and the next day I requested a refund because several of the old titles didn't want to run. Despite the no-refund policy, they reversed the transaction. I've heard more positive stories than negative ones.

it still only takes it happening once to you to lose your titles.

Re: Requirements for DRM in HTML are confidential

#156

Post by xyjztr »

Daiz wrote: post #151

This should really be at the top of every HTML DRM discussion: HTML DRM will not give you plugin-free or standardized playback. It will simply replace Flash/Silverlight with multiple custom and proprietary DRM black boxes that will likely have even worse cross-platform compatibility than the existing solutions. In other words, giving in to HTML DRM will only make the situation worse . Some vendors will keep pushing f…

Hey Guys, can somebody create a simple guide, FAQ or something similar for non-tech people to understand what is going on with HTML and DRM? It will help to spread the word.

Re: Requirements for DRM in HTML are confidential

#157

Post by lazyjones »

mcot2 wrote: post #142

If our end result is to see Netflix using HTML5 video on Desktop browsers, how do we get there from a technology and business point of view? Keep in mind that Netflix has content created and owned by the major studios. If any form of DRM is not the way, than what? How do we get to this end goal? Do we make streams 'free' to copy and rely more on the legal system for protection? We are all keen to slam DRM, but what i…

> If our end result is to see Netflix using HTML5 video on Desktop browsers, how do we get there from a technology and business point of view

Where's the specific value in that? Netflix can use their own application to display the DRM-ridden content. I don't see why everyone else should have to deal with DRM in the browser because of that.

Re: Requirements for DRM in HTML are confidential

#158

Post by jasonwatkinspdx »

simonsarris wrote: post #107

I suppose that the title assertion is to be expected. DRM only works if you don't know how it works. ~~~ I'm not sure I see anything wrong with DRM per se (this could be my fever talking), there are probably good uses I'm too dim to think about, but I do think it's unnecessary as part of the HTML specification. There's no industry or company that has switched to DRM-free content, that I know of, that has failed or su…

> DRM only works if you don't know how it works.

http://en.wikipedia.org/wiki/Kerckhoffs's_principle

Re: Requirements for DRM in HTML are confidential

#159

Post by gcb0 »

nemothekid wrote: post #145
byuu wrote: post #94

Earlier quoted context omitted.

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 fill…

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.…

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

#160

Post by fpgeek »

mcot2 wrote: post #135
w-ll wrote: post #73

Earlier quoted context omitted.

> Yes, every DRM will eventually be broken, but at least it satisfies the executives enough, so what's the problem? Executives are never satisfied, and the world doesn't revolve around them. Should we allow tapping of our communications because it satisfies our leaders. > Security, battery life, and script-able/touch friendly controls. And what do any of these have to do with DRM? In fact, I can guarantee DRM will of…

They will be satisfied enough to offer HTML5 video. The point is killing off Flash. It is a lot easier to secure a smallish DRM module in a browser than a gigantic environment like Flash.

Not really.

"Securing" a DRM plugin means "securing" the browser it runs in (otherwise it will be cracked by the browser lying to it about whether DRMed media is being played "securely"), which means "securing" the OS the browser runs on and so on...

Post reply on HN