Requirements for DRM in HTML are confidential
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 suffered because of it:* Music is largely available DRM-free now, thanks to Amazon's MP3 store (at the least, I'm sure there are others)* For games, Steam makes it easy to avoid SecuROM Hell* Despite DRM, all of Netflix's original series House of Cards was available on The Pirate Bay within hours of release. This doesn't seem to hurt Netflix's wish to create more content, or police it more heavy-handedly. (Maybe they would if they could)For that matter, I think in the modern case every single time a business went DRM free it turned out OK. Isn't that right? In all modern cases, maybe after 2006-ish, DRM-free businesses were accompanied with an easy way to get the content online, and sales did not seem to suffer because at the end of the day piracy can appear (or be) shady and people (rightfully) don't trust shady websites, even The Pirate Bay with all of its popups.I wish we had better numbers. I would like to see a real analysis on all the reasons people don't pirate and instead buy on Steam. I wish there was a good way to convince media businesses at large.But I guess this is all water under the bridge, and I'm preaching to the choir.