19 ms·
Mozilla bug 923590: Pledge never to implement HTML5 DRM
- chris_wot 13y agoI'm not sure I put this into the right category. It's really more than a Firefox issue, it's something for Mozilla as an organisation.
- frozenport 13y agoI wonder if this will finally kill Firefox? Imagine a world where FF can't play YouTube or watch Netflix? What if DRM content becomes so prevalent it FF will render most websites like Lynx?
- guelo 13y agoThat world would really suck. We must do everything we can now to prevent it. Berners-Lee and the W3C don't dictate the web, they have been ignored and overridden before.
- fafner 13y agoI guess in that case they'd add DRM support. Similar to them adding h.264 support now.
- coldpie 13y agoAs far as I'm aware, Firefox doesn't support h.264. They support codecs provided by your operating system. Firefox can't include h.264 decode because they would be violating patent law.
- josteink 13y agoWhat if DRM content becomes so prevalent it FF will render most websites like Lynx? That is the future we can very well face unless we oppose this DRM evil now, at its root, before it enters our HTML standard. Don't attempt to be "pragmatic" about this one; be principled. Stop using any browser supporting the EME initiative.
- spongle 13y agoWell I'll have a lot more time on my hands so perhaps it isn't a bad thing. Perhaps the fragmentation it will cause will destroy closed media on the internet as a whole. Nothing bad can come of it.
- duckduckblert 13y ago> Perhaps the fragmentation it will cause will destroy closed media on the internet as a whole. It almost certainly won't. The majority of consumers won't care (or even notice) so long as good products are being made with the technology.
- ProNoob13 13y agoFirst of all, making a bug-ticket for something that doesn't exists yet isn't going to solve anything. Second of all, why do you oppose DRM? It's been around for years. Games, DVDs... Nobody really had troubles with it until the bad (not so user-friendly) implementations came around. But, with W3 standardizing the spec for it, we get a win-win: We can watch all our (streaming) video without Flash (which was previously used for DRM), and content providers can be sure that the content we're watching is payed for.
- pgeorgi 13y agoWe can only watch the streaming video if the DRM provider wants to provide a plugin (following the EME spec) for your platform. That will make Firefox on Haiku less functional than Firefox on Windows. (and if the plugin were able to run everywhere, it would be trivial to work around: Just run on a system without a protected AV path)
- lucid00 13y agoBut if content providers refuse to not use DRM anyways, won't Haiku users still lose out regardless? If you can't use HTML5 DRM with Netflix your other options are either Silver light or a native app and Haiku has neither. I'd say HTML5 DRM is the far lesser evil in this case.
- pgeorgi 13y agoThey're all equally evil, since they're all equally useless on non-Win/OSX platforms (which are the only ones providing a reliable protected AV path), and since they're all very similar in that they need a plugin. IMHO If anything EME is more evil than the other options in that it standardizes (and this way implicitely mandates) a special plugin interface for DRM purposes only. Users still have to install plugins, and now browser vendors get the blame if things fail (since the user will be hard pressed to identify plugin issues in "that website doesn't work"). I fail to see where it's the W3C's, browser vendors' or web users' responsibility to make the DRM vendors' lifes easier. And that's all EME does.
- ddebernardy 13y agoI think you're barking up the wrong tree... And that it has the potential to blow up in Firefox's face. Remember what happened to html5 video. Everyone but Firefox was pragmatic, and implemented h.264 -- primarily, but not only for hardware acceleration reasons. Years later, Webkit-based browsers are ubiquitous, and Mozilla is developing a phone OS nobody will care about, in a desperate effort to become relevant again. Imo, Mozilla ought to spare itself another embarrassment by being the only guys in the room with the contrarian opinion. Take the issue to the W3C directly -- or for that matter vote for your local pirate party. HN and other tech news venues might be the correct places to recruit support, but you ultimately want to lobby your case directly.
- Udo 13y agoWhat drove me to Chrome at the time was the resource hunger and the inferior UI of Firefox, not the video thing. If DRM is the consensus, Mozilla should (and probably for technical reasons must) have the contrarian opinion. It would be enough to make me switch back, actually.
- PhasmaFelis 13y agoI like Chrome. I think it's a better browser than Firefox. Having to switch back, after several years settling into Chrome's extensions and configurations, would really piss me off. But I'll do it if Chrome implements this bullshit and Firefox doesn't. Wonder if I've still got tabs saved from the last time I seriously used Firefox, years ago. Probably not...
- jotm 13y agoDoes it finally have good flash and JS blockers? Regardless, i hate the tab system and address bar search in Chrome, wish it was like Firefox's, then I'd switch because it's faster...
- nine_k 13y agoBookmark all tabs, exit one browser, open another, import the bookmarks. Mozilla and Chrome can import each other's bookmarks. BTW I switched to Firefox on my laptop since it seems to be much less resource-hungry than Chrome. Not painful.
- skrebbel 13y agoCan some of the more involved please explain the consequence of a choice like this? If Mozilla chooses to not implement this spec, will the effect be that: * Firefox is the only browser that can't play certain content * Firefox is the only browser that plays all content ? I would assume the first, because it should be easy for a content provider to just block a certain browser entirely (and that block could be circumvented, but the majority of people won't do that). People will blame Firefox, not the content provider.
- pgeorgi 13y agoFirefox couldn't display those files/streams, but it would notice and could cope, eg. by displaying some informative message instead that lays the blame where it belongs to: the website. Since FF is still popular enough in certain regions, that it (plus legacy IE versions) could kill EME before it gets popular, except for certain special use cases like Netflix on Chromebooks (where, honestly, a fully custom plugin solution would work just as well).
- ben0x539 13y ago> by displaying some informative message instead that lays the blame where it belongs to: the website. Surely the website will detect FF and instead of serving an encrypted stream, display some informative message laying the blame with Mozilla and link to a DRM-enabled browser download.
- pgeorgi 13y agoOf course they're free to do that, like they are now. So instead of installing a plugin, the user is now expected to install a new browser (with different UI and everything) _and_ a plugin for the DRM implementation. That surely helped the DRM vendors' cause.
- madeofpalk 13y agoOr, the user would see their browser not supporting Netflix, think it's a poor product and which to a 'superior' one.
- Qantourisc 13y agoI'd like to make a comment, but does anyone know how this DRM works ? I mean either you trust the client, by binary-blobs/hardware or other form of protection, or you are delivering the content into the lap of the consumer. So I wonder if FireFox CAN even implement it ?
- fafner 13y agoThe current proposal for Digital Restrictions Management is to have an API which would load proprietary closed source binary blobs to handle the videos. Or in other words: They force "Yet Another Flash" into HTML5. Perverting the whole idea of an open web...
- chris_wot 13y agoNot to mention tie content to a particular browser, not to mention a particular OS.
- ksec 13y agoRealistically, how are content provider suppose to copy protect their properties without the use of DRM?
- pgeorgi 13y agoBy storing them in a large vault with armed security at the entrance, never letting them see the light of day. Oh, they can't monetize it then? That's the price for security.
- curiousdannii 13y agoSo the Disney Vault is an actual physical vault with human security guards? Wow! I thought it was just a scheme for introducing artificial scarcity.
- icebraining 13y agoRealistically, DRM does fuck all to protect content; The Pirate Bay is proof of that (most content there comes from DRM'd sources). All it does is control paying users.
- res0nat0r 13y agoRealistically, DRM keeps the majority of users from pirating content(otherwise I'll venture to guess that BigBadCo would have found via their research it was a losing proposition). The internet dorks who frequent HN and Reddit who know how to easily circumvent said DRM are the minority.
- gizzlon 13y agoReally? At least half of my "normal" friends know how to torrent stuff. That any normal people would torrent anything says a lot. Normally convenience wins. Maybe torrenting actually is the easiest way to get some content? For me, it's a no-brainer[1], but it's more surprising if this is the case for normal people as well. That should open the eyes of some content providers, but of course it won't. [1] - Meaning that for me as a technical user, torrenting is really easy. Some things have just started to compete, like spotify, netflix and hbo online, but they are often crippled in other ways.
- deleted 13y ago[deleted]
- deleted 13y ago[deleted]
- jamespo 13y agoYou can always fork your own clean Firefox and promote it
- devx 13y agoIt's bad enough that governments are starting to restrict the Internet all over the world [1], almost in unison, why should the last bastions of freedom on the Internet fall so easily, too? I see the corruption of W3C (because that's what it is) by corporations almost as bad as the corruption of NIST and the security standards by the NSA. And for what exactly? The apparent "convenience" of not having a 3rd party plugin, but instead a "native" plugin in the operating system, that will only work on certain operating systems and browsers? HTML and DRM are incompatible in principle, and will be incompatible in practice, too. It won't give you any convenience, and will potentially make things worse in many other ways. And all of this because we're starting to buy into the idea that the content companies are right and piracy is hurting their sales? I guess repeating a lie long enough, does make it true in the end - even though it probably isn't [2]. So once again, why are you letting our Internet freedom slip away without even a fight? [1] - http://www.freedomhouse.org/report/freedom-net/freedom-net-2013 http://www.freedomhouse.org/report/freedom-net/freedom-net-2... [2] - http://torrentfreak.com/piracy-isnt-hurting-the-entertainment-industry-121003/ http://torrentfreak.com/piracy-isnt-hurting-the-entertainmen...
- gsnedders 13y agoThe W3C is an industrial consortium — its direction and what it produces is down to its membership, so obviously it will follow what corporations want, because that's what industrial consortia do.
- guelo 13y agoWhat's ridiculous about everybody bending over backwards for the Netflix usecase is that Hollywood isn't letting Netflix have the content anyway because they want to control and destroy yet another medium. Hollywood is a corrupting evil in our technical, legal and political systems and should be shunned, not accommodated, as much as possible.
- deleted 13y ago[deleted]
- belorn 13y agoBoycotting is a tool used by advocates to bring up media attentions and raise public awareness. Its surely a useful tool, but not the only one. We can still say no to Hollywood when they try to attain ownership of our private owned hardware, our software, our networks.
- antocv 13y agoIt is quite ridiculous that in a very capitalist oriented society the consumers end up owning nothing. Not even the movies they payed to watch, or the smart-phones in their pockets are really their property. Well, "the intellectual property" which prevents me from selling a copy of movie or book I bought, seems to supersede private property. I miss the old days when my money could actually buy things and I could trade with the goods and services that I bought. Now they want to take ownership of my user agent, my browser, they want to impose their intellectual rights on it, instead of mine.
- sudomal 13y agoMovies are probably the most easily justifiable for DRM. They aren't the sorts of 'products' that people watch over and over again (unless they get a cult following). A single viewing of a movie reduces the value to a point where it may not be purchased. That's why distributors release them in as many stunted, protected, phases as possible - they want a return on their investment before it becomes relatively worthless.
- captainmuon 13y agoImplement it, but don't implement it properly. Always tell the server (or whatever does the checks) that DRM is available, and that the user is authorized to play the content. Or add a button or setting to unlock any content. And even if they implement DRM, I could probably just grab the source and comment out a few ifs, and would be fine (assuming its not just a wrapper for Windows' DRM).
- mercurial 13y agoI don't think it's supposed to work like this. It's not about implementing DRM itself, it's about having a standard API which would allow an opaque binary blob to implement the actual DRM. And then, as the issue points out, possibly extend the reasoning to other elements, like Javascript code.
- chris_wot 13y agoP.S. in case anyone asks, I submitted the bug on my iPad... Hope it's not too disconcerting to see the WebKit user agent on this bug! :-)
- lmm 13y agoSo you choose convenience over freedom for yourself, but want Mozilla to not cater to people like you?
- chris_wot 13y agoWere you thinking of the children who hate your freedom before or after you wrote that false dichotomy?
- aaronem 13y agoIt's about as coherent as most of what's coming out of the "all DRM is evil period" camp right now, or at pretty much any other time. Besides, I'm sure his iPad is jailbroken.
- chris_wot 13y agoIt's not.
- lucb1e 13y agoinb4 "I play open software advocate on a closed platform"
- chris_wot 13y agoI can use a closed platform (because webkit is super closed...) and advocate for open source.
- this_user 13y agoI think he was talking about the whole Apple/iOS/iTunes thing which is worse by an order of magnitude than any DRM that has ever existed or will ever exist. So, yes, of course you can advocate for open source from the convenient position of your walled garden, it just makes you a hypocrite.
- smegel 13y agoWell its either that or flash...think I would rather HTML5.
- pgeorgi 13y agoI'd rather have problems like DRM well-contained. Flash sounds like a good isolating barrier for that purpose.
- idlewan 13y agoJust because we hate flash doesn't mean we should accept something worse to get rid of it. You think the DRM blob would be less slow, less buggy, less closed and less resource-hungry than flash is and has been? Think again.
- takluyver 13y agoWhy? The DRM blob has to do far less than Flash - it's not a whole runtime environment, it just decrypts a data stream and sends it to be rendered. There are very good reasons to think that that would be less slow, buggy and resource hungry. Though I agree that it would be no less closed.
- alkonaut 13y agoWhile I agree that it does seem like "less work" to just do the DRM bit, is it really likely that this plugin will really decrypt data, leaving a normal unprotected video stream for the browser to render? In that case, a browser implementation could just write the unencrypted video to disk or re-stream it over http to other clients, without even having to do a new transcoding/compression (which costs cpu power and reduces quality). The whole point of effective software video DRM is that the plugin must render the video to screen itself, and ideally in a way that doesn't let the attacker find the unencrypted stream in memory. Silverlight does this via PlayReady for example.
- Fice 13y agoDRM can't be properly implemented in free (as in freedom) software. Either you will not be able to run any modified version not signed by the vendor on your device, or any version you build yourself will lack DRM support. DRM is all about restricting the user control over their devices. DRM-enabled Firefox would be effectively non-free software: you could not modify it and rebuild it from source while retaining the DRM functionality.
- jomohke 13y agoYou're right about DRM implementations in general, but note that the W3C standard isn't actually a DRM implementation, it's (afaict) a common API that allows web pages to supply their own DRM implementations. An open source browser can conform to the W3C DRM standard ("Encrypted Media Extensions") and remain open source.
- chris_wot 13y agoExcept they need to implement Content Decryption Modules, which are not standardised and which may use features (or DRM systems) that are only implemented on particular systems. Ultimately, this extension could tie particular content to a particular system. Say, for instance, you could only watch some content on a Windows 8 system because it requires a Microsoft specific DRM system implemented only on Windows 8. A system that could ultimately be badly documented (or not documented at all) that makes it hard for competing browsers to use the CDM. Frankly, this system would only work if you standardise in a DRM system. The W3C may claim "only the simple clear key system is required to be implemented as a common baseline" [1], but that's highly misleading IMO. 1. https://dvcs.w3.org/hg/html-media/raw-file/tip/encrypted-media/encrypted-media-fpwd.html https://dvcs.w3.org/hg/html-media/raw-file/tip/encrypted-med...
- acdha 13y agoThe idea is that currently most video on the web plays in either Flash or Silverlight, which are poorly supported plugins which offer a huge amount of extra functionality and – more importantly – attack surface. This is really only about replacing a huge proprietary blob with a much smaller one.
- aaronem 13y agoI'm still trying to figure out how we go from "UA streams encrypted content to EME plugin -- oops, sorry, 'extension' -- and EME extension streams decrypted content back to browser" to 'View Source' being prohibited, copy-paste of text demanding micropayments to complete, dogs and cats marrying each other, and Satan going to and fro on the earth.
- chris_wot 13y agoI'll deal with what I wrote only, not the rest of your silliness :-) The basic argument is that those who want restrictions to content have been attempting to chip away at what is essentially an open platform. While the W3C's argument is that it is an "extension" to the HTMLMediaElement, and while the draft goes to great pains to state that it is not a DRM system, in actual fact it goes a great way towards allowing for a DRM system. If you review the diagram in the draft [1], you will see that it covers playback of certain content. Currently, it is restricted to media files. But you can see that once this is adopted, it would then lower the barriers for media companies and other interested actors to push for encryption mechanisms for individual elements. Even worse, note that the Content Decryption Module (CDM) is a "part of or add-on to the user agent that provides functionality for one or more Key Systems". In other words, these will probably need to be implemented as binary blobs which are add-ons for browsers. They may need to use specific technologies that are part of particular operating systems. What does this leave us all with? Well, it leaves us with the promogulation of a bad idea (restrictive DRM) implemented using a variety of browser specific extensions that may need to utilise the specific technologies of a particular operating system. As an example, you could be forced to use an add-on for Internet Explorer that can only be used on Windows 8. So in other words, the plan is a bad one for technical reasons, and for political reasons it lowers the barriers to campaigning for more restrictive measures leaking nto the rest of the standard. 1. https://dvcs.w3.org/hg/html-media/raw-file/tip/encrypted-media/stack_overview.png https://dvcs.w3.org/hg/html-media/raw-file/tip/encrypted-med...
- acdha 13y agoHow is this different from the status quo? All you appear to be arguing is that we should stick with the status quo where you are required to use something supported by Flash or Silverlight. The option I'd like, where video is watermarked or otherwise not encumbered, isn't on the table and much as I'd like that to change, the security realist in me would like a web without Flash even more.
- lucb1e 13y agoI dislike this. Now sites will just say "View this site in Internet Explorer" and I'll have to boot a virtual machine to legally view the content. Well, if I ever get sued for it I guess I can always say Hollywood should provide me with a Windows license.
- chris_wot 13y agoYou can choose not to view that content.
- mordae 13y agoNah, just watch whatever you want and donate to those who deserve it.
- chris_wot 13y agoWhich, ironically, is what happens when you implement DRM systems. Often, no one gets paid.
- ricardobeat 13y agoWhat if all content was under DRM? What if I owned all the land on earth, charged huge taxes, then told you 'you can choose not to live here'?
- chris_wot 13y agoDo you own all the land on earth, and are you ever likely to?
- fafner 13y agoDislike the DRM in HTML5 attempt instead. What chance does Mozilla have to implement DRM? None. DRM can't be implemented in free software. They could add support for closed source proprietary blobs. But the W3C proposal does not specify how to do that. Meaning Google will do it through PPAPI and just ship Chrome with the modules included. IE will simply include PlayReady and Safari will include the Apple DRM. Leaving Firefox stranded. If Firefox bends over and adds support for PlayReady and the other crap then this will effectively mean that Firefox will depend on proprietary binary blobs to do the video rendering. In other words it will be exactly like Flash but unlike Flash it won't work on Linux at all. We have to oppose DRM in HTML5 and we shouldn't give up on the open web. It is sad that Tim Berners-Lee has given up on it and is destroying this own legacy. But we should fight it!
- ialex 13y agoWhat a scary stuff is this? Imagine the new world that would be open to the malware/spyware if DRM is enabled they will easily use this to hide their shitty stuff and not allowing anybody to see whats going on, how does w3c is going to let that happen :S Hopefully Firefox wont be open to implemment this shit on their browser.
- jheriko 13y agowell done. :) as we all know drm is folly. if the data can be decrypted to use then it can be stolen /always/.
- dingdingdang 13y agoYeah, good luck the the DRM crap - it worked over so well with music (not) and I'm sure it'll fly super fine with video too. Tim Berners-Lee has sold his soul somewhere along the line. Following bit from Florian Bösch comment on article sums it up brilliantly: "The W3Cs (and Tim Baner Lees) support of EME shows clearly that once again, the W3C has gone down a blind alley (like with XHTML) and is not interested to serve the real needs of the web. The WhatWG was the result of W3Cs stagnation on addressing real world needs. And once again the W3C is more interested in stagnation than real world needs with EME. It has to be expected that the relevancy of any W3C standard will substantially diminish in the future."
- deleted 13y ago[deleted]
- tpainton 13y agountil you see some slime profit from your hard work by simply copying it... it's easy to talk about how evil drm, and copyrights are. I know photographers, great photographers, that were stunned when they googled their images and found them front and center on some scumbags webpage, claimed as theirs. musicians go thru the same ordeal. This isn't just about Hollywood, it affects creators who are far from rich.
- rkda 13y agoWouldn't watermarking solve this problem? Then people would know the original owners. Other people can't get away with claiming them as their own.
- alkonaut 13y agoEither make way for content protection for video in some kind of standard, or we are stuck with Silverlight and Flash video forever. Why wouldn't I want some kind of standard platform for delivering protected video in my browser, rather than getting and updating 2-3 different insecure plugins all the time for doing the same thing? Is this just a crusade agains DRM as a whole (good luck with that) from the free software movement, or do they have problems with this exact proposal from the w3c?
- jimktrains2 13y ago> or we are stuck with Silverlight and Flash video forever This proposal simply trades one insecure, binary blob for another. It doesn't really solve the problem. > rather than getting and updating 2-3 different insecure plugins all the time for doing the same thing? IIRC each site can provide its own module, so it'll be many more than 2-3 plugins > Is this just a crusade agains DRM as a whole (good luck with that) from the free software movement, or do they have problems with this exact proposal from the w3c? Why good luck with that? DRM simply makes honest users jump through hoops and allow themselves to be controlled. Also, the proposal itself doesn't really solve any of the problems that flash and silverlight do. And those binary blobs will still probably not run in linux...
- alkonaut 13y agoYes, the problem: the only way the content owners will stream tonights game to my computer is if it is protected somehow. If there is a way to make a transparent & open platform that allows content to my computer in a way that makes the content providers happy, then I'm all for doing that instead of having the system of insecure binary blobs. But is that possible? If it is possible, wht isn't the W3C pushing for that instead of the "plug your own binary"-platform? Is security through obscurity inherent in DRM?
- jimktrains2 13y agoIt's not possible. DRM is impossible when a user has access to the full system. That is why there is a push for locked boot loaders and security modules and such. The more access the user has the easier it is to defeat DRM. Conversely, the less access they have the harder it is to break.
- zamalek 13y ago"To view this website please download our plugin that enables DRM-protected content in your browser."
- ChikkaChiChi 13y agoPlease implement this. The faster we lull these stupid media companies into a false sense of security, the faster we can get rid of Silverlight.
- surrealize 13y agoSilverlight is going away regardless--it's already deprecated by Microsoft. Just as Flash has been deprecated by Adobe. We don't need to do anything to ensure that they go away.
- shmerl 13y agoI still wonder what was Tim Berners-Lee thinking, when supporting DRM? He should have known better.
- mmcclure 13y agoMozilla wouldn't implement EME in the browser. It would come in the form of a plugin. It's absolutely incredible what a few uninformed blog posts will do to an otherwise very smart group of people. I wrote pretty much the same thing in the comments on the blog post yesterday when people were freaking out about this then. EME is a plugin spec for implementing DRM, not something that would get baked into browsers. Everyone put their logic pants on and stop freaking out for a second. This is might be a silly spec for implementing a stupid premise (DRM), but it's not the end of the open web.
- crazychrome 13y agoam i the only one to against the pledge? here is the reason: if there was such kind of mechanism in browser, we probably already had snapchat years ago on browser instead of Apple's safe guarded garden. there is no evil technology. it just depends on how to use it. i'm surprised so many are blindly naive.
- Zigurd 13y agoTens of billions of dollars worth of JavaScript source code are squirted out to every person, good and nefarious, rich and poor, all over the planet without boundaries, every day as they use Web applications. Why is nobody promulgating a standard for hiding it? The answer is that such proposals get laughed out of the room. They would break the Web, which is far more valuable than anyone's JavaScript source code. Has innovation in JavaScript suffered for lack of source code protection in Web standards? That's also a laughable idea. So, why not the same answer for passive content?
- thenerdfiles 13y agoThe Grand Chancellor of English, or Webster's Dictionary, has confirmed that utterance of protected terms is in scope of the latest edition.
- AYBABTME 13y agoMaybe I have no idea of what I'm talking about, but my understanding over how this "Media and Piracy" plot has gone is: - Media purchase was inconvenient and overly expensive. - People pirated because it was convenient and cheap. - Streaming services offered convenient, low cost solutions. - People 'stopped' pirating because streaming is a decent, convenient legal alternative. At least that's how I've (and everybody I've asked about) gone through it. So in that perspective, it seems to be a useless attempt at defending from a fading threat.
- alkonaut 13y agoI have the same feeling. But like I have tried to explain elsewhere: live streamed events (expensive sports broadcasts) are really sensitive to piracy. At least if you judge by the precautions they use. Today they typically use PlayReady DRM in a Silverlight video player (flash based solutions also exist). They usually also randomly insert subscriber id:s as text at regular intervals and random locations in the video stream thereby watermarking it and making it a risk for whoever decides to re-stream their screen. So the current situation is this: the broadcasters already have several methods of protection (Watermarking, Encryption), which means any technology we wish they would adapt better support at least what they have today.
- code_duck 13y agoThey say, "A Web where you cannot cut and paste text; where your browser can't "Save As..." an image; where the "allowed" uses of saved files are monitored beyond the browser; where JavaScript is sealed away in opaque tombs; and maybe even where we can no longer effectively "View Source" on some sites, is a very different Web from the one we have today. It's a Web where user agents—browsers—must navigate a nest of enforced duties every time they visit a page. It's a place where the next Tim Berners-Lee or Mozilla, if they were building a new browser from scratch, couldn't just look up the details of all the "Web" technologies. They'd have to negotiate and sign compliance agreements with a raft of DRM providers just to be fully standards-compliant and interoperable." Well, so essentially like the situation with native apps then. My guess is most consumers wouldn't notice at this point.