Slashdot Mirror
Microsoft Edge, HTML5, and DRM
An anonymous reader writes: Microsoft is building its new browser, Edge, with the intention of avoiding many of the flaws that plagued Internet Explorer over its long and tumultuous life. Part of this involves moving away from plug-ins, and Edge will not support ActiveX. Instead, they're focusing on interoperable media, and that means non-plug-in video players that meet HTML5 specs. Of course, not all video players want to disseminate their content for free, which means: DRM. Microsoft's Edge team has published a new post explaining how they'll be handling support for DRM and "premium media" in the new browser.
They say, "Windows 10 and Microsoft Edge support DASH, MSE, EME and CENC natively, and other major browsers ship implementations of MSE and CENC compliant EME. This support allows developers to build plug-in free web video apps that runs across a huge range of platforms and devices, with each MSE/EME implementation built on top of a different media pipeline and DRM provider. In the days when DRM systems used proprietary file formats and encryption methods, this variation in DRM providers by browser would have presented a significant issue. With the development and use of Common Encryption (CENC), the problem is substantially reduced because the files are compressed in standard formats and encrypted using global industry standards. The service provider issues the keys and licenses necessary to consume the content in a given browser, but the website code, content and encryption keys are common across all of them, regardless of which DRM is in use."
They say, "Windows 10 and Microsoft Edge support DASH, MSE, EME and CENC natively, and other major browsers ship implementations of MSE and CENC compliant EME. This support allows developers to build plug-in free web video apps that runs across a huge range of platforms and devices, with each MSE/EME implementation built on top of a different media pipeline and DRM provider. In the days when DRM systems used proprietary file formats and encryption methods, this variation in DRM providers by browser would have presented a significant issue. With the development and use of Common Encryption (CENC), the problem is substantially reduced because the files are compressed in standard formats and encrypted using global industry standards. The service provider issues the keys and licenses necessary to consume the content in a given browser, but the website code, content and encryption keys are common across all of them, regardless of which DRM is in use."
DRM and all that.
What they're glossing over with their review is that adblocker extensions, password managers, extensions that prevent video from autoplaying and etc. will not be available. And I won't use Edge because if I can't control the behavior of my web browser I won't use that web browser.
July 31, 2012
Microsoft (MS) began encrypting web-based chat with the introduction of the new outlook.com service. This new Secure Socket Layer (SSL) encryption effectively cut off collection of the new service for FAA 702 and likely 12333 (to some degree) for the Intelligence Community (IC). MS, working with the FBI, developed a surveillance capability to deal with the new SSL. These solutions were successfully tested and went live 12 Dec 2012. The SSL solution was applied to all current FISA and 702/PRISM requirements - no changes to UTT tasking procedures were required. The SSL solution does not collect server-based voice/video or file transfers. The MS legacy collection system will remain in place to collect voice/video and file transfers. As a result there will be some duplicate collection of text-based chat from the new and legacy systems which will be addressed at a later date. An increase in collection volume as a result of this solution has already been noted by CES.
March 15, 2013
SSO's PRISM program began tasking all Microsoft PRISM selectors to Skype because Skype allows users to log in using account identifiers in addition to Skype usernames. Until now, PRISM would not collect any Skype data when a user logged in using anything other than the Skype username which resulted in missing collection; this action will mitigate that. In fact, a user can create a Skype account using any e-mail address with any domain in the world. UTT does not currently allow analysts to task these non-Microsoft e-mail addresses to PRISM, however, SSO intends to fix that this summer. In the meantime, NSA, FBI and Dept of Justice coordinated over the last six months to gain approval for PRINTAURA to send all current and future Microsoft PRISM selectors to Skype. This resulted in about 9800 selectors being sent to Skype and successful collection has been received which otherwise would have been missed.
March 7, 2014
PRISM now collects Microsoft Skydrive data as part of PRISM'S standard Stored Communications collection package for a tasked FISA Amendments Act Section 702 (FAA702) selector. This means that analysts will no longer have to make a special request to SSO for this - a process step that many analysts may not have known about. This new capability will result in a much more complete and timely collection response from SSO for our Enterprise customers. This success is the result of the FBI working for many months with Microsoft to get this tasking and collection solution established.
The XBox One has been out, nothing approaching a break, and the XBox 360 will get killed off XBL the second someone sticks a modded ROM on there.
As for Windows, seen an activation crack for W2012 R2 or W2012, or even W8? Even fake KMS servers don't last long (a few hours at most).
MS in the DRM department is doing quite well.
Copied and pasted from a comment yesterday.
Please think before you moderate this FUD up. An article on Microsoft is no license to Mozilla-bash.
Who comes up with these idiotic names? Why not "Microsoft Nail" or "Microsoft Lance" or "Microsoft Thing That Penetrates"?
"Microsoft Edge" is a very '90s name to my ears, but maybe it's just the fact that I've been sitting on the porch drinking, eating barbecue and watching fireworks for the past several hours. But Microsoft was never really good at names, although I did once have a three-legged dog named "Clippy" (that's actually true).
You are welcome on my lawn.
Google's stewardship of web video has been the primary reason for these delays and frustrations. Not only have they been dicking around with HTML5 video, changing how it works every 6 months and screwing with YouTube in ways that make other browsers often look bad "just 'cause", they also paid Adobe to make a Chromium-specific version of Flash on their new plugin API, despite knowing full well that plugins were on the way out, and nobody in their right mind would adopt their plugin interface. So now most browsers have either a shit Flash version that Adobe doesn't care about anymore, or flaky HTML5 video support that requires implementing several immense new APIs like MSE, EME, and others. Google basically has a serious "not invented here" problem with web technology that leaves everyone that doesn't have a huge Google banner over their heads cold, and for every person believing they're making the web better, the actual developers in the trenches are increasingly frustrated with their efforts to rush features out in Chrome that no one else could sanely adopt for months or years - and trust me, others like the Webkit and Firefox team have been working closely to try to make heads or tails out of their specs and adopt them all along.
.net is inferior to javascript
In what way?
One advantage of the .NET Framework is static typing. In a fully dynamic language such as PHP, Python, or JavaScript, you need to put unit tests into your program to make sure the correct types are getting passed in and out of functions. A language with static typing, such as C#, already ensures type safety. So it's like the compiler writes a lot of your unit tests for you.
The .NET Framework used to have the disadvantage of being a non-free platform, which put .NET programs in what FSF calls a "Java trap". But nowadays, a lot of the interesting parts of the .NET Framework are released under a free software license.
Who comes up with these idiotic names?
I don't know who, but I do know when. IE 8 introduced the X-ua-compatible header. "Use the following value to display the webpage in edge mode, which is the highest standards mode supported by Internet Explorer."
As distasteful as I find DRM, at least we see Microsoft trying to improve their web browser. With Edge they're actually succeeding in creating something that average users do want to use!
Not exactly. Microsoft's Edge browser is still in fourth place in terms of being standards compliant, which is what I think average users want because it makes the browser actually compatible with modern content. Yes, it's a tad ahead of IE, but it's still quite behind Chrome, Firefox, and Opera.
http://html5test.com/results/d...
In fact most web browsers for mobile devices are doing better than Edge: It's behind Android WebView, BlackBerry's web browser, Chrome for Android, Firefox for Android, Safari for iOS, Opera Mobile, Tizen's web browser, Amazon Silk, Jolla Sailfish, and the now discontinued Nokia X browser.
http://html5test.com/results/m...
... flaky HTML5 video support ...
huh?
The above has worked for several years now.
The default video tag supports full screen view.
Youtube's thingy does not. Why not? What's the problem?
Not a real big fan of html5test.com. The weight they assign things are very chrome favored. Just as an example, they list stupid things like :read-only, :read-write twice, and 2d blend modes (7 points) which favor Chrome, but useful things like video track and audio track selection are weighted very little (4 points).
It's all of about 25 days from release. I doubt they are going to be adding features at this point, more likely they're just bug fixing.
You need to learn that a lot is two words.
As distasteful as I find DRM, at least we see Microsoft trying to improve their web browser. With Edge they're actually succeeding in creating something that average users do want to use!
Not exactly. Microsoft's Edge browser is still in fourth place in terms of being standards compliant,
Err.... standards? Look, HTML5Test leans heavily on W3C working drafts which are nowhere near finished. Edge doesn't implement Web Components, streams, service workers, web notifications, speech recognition and speech synthesis. These account for about 10% of the total HTML5Test score, but they're all drafts or proposals!
The fact that some browsers are implementing these drafts without a prefix is a PROBLEM, not a good thing. Library & web site developers end up taking dependencies on things that may very well change over time.
Meanwhile, if you want to stick to stable, published specifications, Edge is currently the leading browser for ES6 support in terms of percentage of features implemented. As for CSS, have a look at the list of CSS features Edge doesn't support and note that for most of them, at least one of Firefox and Chrome hasn't implemented them either..... and/or they're a working draft.... or other browsers have just implemented them in the last few months.
This is /.
At least he didn't say: "I follow the link in Lynx, but it no worky-worky,"
Get thee glass eyes, and, like a scurvy politician, seem to see things thou dost not.--King Lear