Subject: Editorial, General Tech | May 14, 2014 - 09:56 PM | Scott Michaud
Tagged: ultraviolet, mozilla, DRM, Adobe Access, Adobe
Needless to say, DRM is a controversial topic and I am clearly against it. I do not blame Mozilla. The non-profit organization responsible for Firefox knew that they could not oppose Chrome, IE, and Safari while being a consumer software provider. I do not even blame Apple, Google, and Microsoft for their decisions, either. This problem is much bigger and it comes down to a total misunderstanding of basic mathematics (albeit at a ridiculously abstract and applied level).
Simply put, piracy figures are meaningless. They are a measure of how many people use content without paying (assuming they are even accurate). You know what is more useful? Sales figures. Piracy figures are measurements, dependent variables, and so is revenue. Measurements cannot influence other measurements. Specifically, measurements cannot influence anything because they are, themselves, the result of influences. That is what "a measure" is.
Implementing DRM is not a measurement, however. It is a controllable action whose influence can be recorded. If you implement DRM and your sales go down, it hurt you. You may notice piracy figures decline. However, you should be too busy to care because you should be spending your time trying to undo the damage you did to your sales! Why are you looking at piracy figures when you're bleeding money?
I have yet to see a DRM implementation that correlated with an increase in sales. I have, however, seen some which correlate to a massive decrease.
The thing is, Netflix might know that and I am pretty sure that some of the web browser companies know that. They do not necessarily want to implement DRM. What they want is content and, surprise, the people who are in charge of the content are definitely not enlightened to that logic. I am not even sure if they realize that the reason why content is pirated before their release dates is because they are not leaked by end users.
But whatever. Technical companies, who want that content available on their products, are stuck finding a way to appease those content companies in a way that damages their users and shrinks their potential market the least. For Mozilla, this means keeping as much open as possible.
Since they do not have existing relationships with Hollywood, Adobe Access will be the actual method of displaying the video. They are clear to note that this only applies to video. They believe their existing relationships in text, images, and games will prevent the disease from spreading. This is basically a plug-in architecture with a sandbox that is open source and as strict as possible.
This sandbox is intended to prevent a security vulnerability from having access to the host system, give a method of controlling the DRM's performance if it hitches, and not allow the DRM to query the machine for authentication. The last part is something they wanted to highlight, because it shows their effort to protect the privacy of their users. They also imply a method for users to opt-out but did not go into specifics.
As an aside, Adobe will support their Access DRM software on Windows, Mac, and Linux. Mozilla is pushing hard for Android and Firefox OS, too. According to Adobe, Access DRM is certified for use with Ultraviolet content.
I accept Mozilla's decision to join everyone else but I am sad that it came to this. I can think of only two reasons for including DRM: for legal (felony) "protection" under the DMCA or to make content companies feel better while they slowly sink their own ships chasing after numbers which have nothing to do with profits or revenue.
Ultimately, though, they made a compromise. That is always how we stumble and fall down slippery slopes. I am disappointed but I cannot suggest a better option.
Subject: Editorial, General Tech | May 5, 2014 - 08:08 PM | Scott Michaud
Tagged: mozilla, net neutrality
Recently, the FCC has been moving to give up Net Neutrality. Mozilla, being dedicated to the free (as in speech) and open internet, has offered a simple compromise. Their proposal is that the FCC classifies internet service providers (ISPs) as common carriers on the server side, forcing restrictions on them to prevent discrimination of traffic to customers, while allowing them to be "information services" to consumers.
In other words, force ISPs to allow services to have unrestricted access to consumers, without flipping unnecessary tables with content distribution (TV, etc.) services. Like all possibilities so far, it could have some consequences, however.
"Net Neutrality" is a hot issue lately. Simply put, the internet gives society an affordable method of sharing information. How much is "just information" is catching numerous industries off guard, including ones which Internet Service Providers (ISPs) participate in (such as TV and Movie distribution), and that leads to serious tensions.
On the one hand, these companies want to protect their existing business models. They want consumers to continue to select their cable and satellite TV packages, on-demand videos, and other services at controlled profit margins and without the stress and uncertainty of competing.
On the other hand, if the world changes, they want to be the winner in that new reality. Yikes.
A... bad... photograph of Mozilla's "UP" anti-datamining proposal.
Mozilla's proposal is very typical of them. They tend to propose compromises which divides an issue such that both sides get the majority of their needs. Another good example is "UP", or User Personalization, which tries to cut down on data mining by giving a method for the browser to tell websites what they actually want to know (and let the user tell the browser how much to tell them). The user would compromise, giving the amount of information they find acceptable, so the website would compromise and take only what they need (rather than developing methods to grab anything and everything they can). It feels like a similar thing is happening here. This proposal gives users what they want, freedom to choose services without restriction, without tossing ISPs into "Title II" common carrier altogether.
Of course, this probably comes with a few caveats...
The first issue that pops in my mind is, "What is a service?". I see this causing problems for peer-to-peer applications (including BitTorrent Sync and Crashplan, excluding Crashplan Central). Neither endpoint would necessarily be classified as "a server", or at least convince a non-technical lawmaker that is the case, and thus ISPs would not need to apply common carrier restrictions to them. This could be a serious issue for WebRTC. Even worse, companies like Google and Netflix would have no incentive to help fight those battles -- they're legally protected. It would have to be defined, very clearly, what makes "a server".
Every method will get messy for someone. Still, the discussion is being made.
Subject: General Tech | April 30, 2014 - 03:52 AM | Scott Michaud
Tagged: mozilla, gamepad, firefox
After three years' reign, the orange Firefox button has been retired by Mozilla. Firefox 29 introduces the new Australis interface, with its curved tabs and a simple menu button comprised of three horizontal lines (the "Hamburger Icon"). The interface missed its targets a few times but is finally here.
Obviously, Australis makes the browser look more like Google Chrome (and less like Opera). Users of Mozilla's Thunderbird will also find it more familiar as that program skipped Firefox 4's direction and immediately adopted parts of Australis as they developed. Thunderbird still lacks a few bits and pieces, its development having slowed since its transition to Extended Support. But this is not about Thunderbird -- it is about Firefox.
In terms of actual features, Australis brings a new Bookmarks button, which is basically two buttons, and is pretty slick to both add and access links to favorite web addresses. The little star-dropping animation is a subtle hint to the user that a bookmark has been added to the list, accessed by the right-most button. Many users will be upset by the removal of the Add-on Bar, a place where extensions can leave a button or two without clogging the rest of the interface. Mozilla seems to expect that extensions, if they absolutely must leave a button, will cram it next to the gigantic location bar (or less-gigantic search bar); that, or affected users will just install an Add-on Bar extension.
Also in Firefox 29 is the finalized, and enabled by default, Gamepad API. With it, web games can be controlled with devices such as the Xbox 360 controller. If you want to see a geeky example, one is available at html5gamepad.com. This website lists every compatible game input device and their current state. In my testing, Firefox 29 was able to detect both my Xbox 360 controller and my Thrustmaster T-16000M joystick -- and register their inputs independently.
There's not really anything, from the technical side of things at least, to prevent split-screen gaming in the browser. Detecting the input devices did not even require restarting the browser, although that is a good troubleshooting step, as Firefox detected it immediately after I plugged it in and pressed a button. The flight stick, probably because it has never been attached to this instance of Windows before, required the good old unplug and replug of its USB cord after Windows "Add New Hardware" finished in order to register input. It is not perfect, but still pretty good.
Firefox 29 launched in the middle of the night on Tuesday, April 29th. It is free and, if Firefox is set to automatically update, you probably already have it. If not? Get it.
Subject: Editorial, General Tech | March 16, 2014 - 03:27 AM | Scott Michaud
Tagged: windows, mozilla, microsoft, Metro
If you use the Firefox browser on a PC, you are probably using its "Desktop" application. They also had a version for "Modern" Windows 8.x that could be used from the Start Screen. You probably did not use it because fewer than 1000 people per day did. This is more than four orders of magnitude smaller than the number of users for Desktop's pre-release builds.
Yup, less than one-thousandth.
Jonathan Nightingale, VP of Firefox, stated that Mozilla would not be willing to release the product without committing to its future development and support. There was not enough interest to take on that burden and it was not forecast to have a big uptake in adoption, either.
From what we can see, it's pretty flat.
Paul Thurrott of WinSupersite does not blame Mozilla for killing "Metro" Firefox. He acknowledges that they gave it a shot and did not see enough pre-release interest to warrant a product. He places some of the blame on Microsoft for the limitations it places on browsers (especially on Windows RT). In my opinion, this is just a symptom of the larger problem of Windows post-7. Hopefully, Microsoft can correct these problems and do so in a way that benefits their users (and society as a whole).
Subject: General Tech, Shows and Expos | March 12, 2014 - 09:17 PM | Scott Michaud
Tagged: GDC, gdc 14, mozilla, epic games, unreal engine 4
Today, Mozilla teases Unreal Engine 4 running in Firefox, ahead of GDC.
Both Mozilla and Epic will have demos in their booths on the conference floor.
Subject: General Tech, Shows and Expos | January 8, 2014 - 04:18 AM | Scott Michaud
Tagged: Panasonic, mozilla, Firefox OS, CES 2014, CES
Panasonic and Mozilla have entered into a partnership, announced at CES, for future smart TVs to be powered by Firefox OS. This can be very useful for Panasonic. Provided they keep up with certifying new releases, performance should be about the only other barrier preventing their product from running the popular apps as they arise. It also lifts the burden away for developer support.
On the other hand, this could also be good for Firefox OS and the web itself. Mozilla is not a stupid organization and, while they certainly like their products adopted, I would not be surprised if they hope this effort brings content out to play. Netflix and other content providers who want to be on Panasonic's platform would need to support their flavor of Firefox OS. Netflix, in particular, has already made inroads with HTML5 albeit with certain encryption extensions.
Atwood's Law applies to televisions, too!
Follow all of our coverage of the show at http://pcper.com/ces!
Subject: General Tech | December 5, 2013 - 01:57 PM | Scott Michaud
Tagged: mozilla, webgl
Tools for web developers are pretty astonishing these days. You are able to investigate the driving elements and objects as they are being executed within the browser -- and even modify them. This typically means that you can play around with the various functions and parameters while the app is loaded. You receive immediate feedback about your changes.
Web Standards continue to encompass 3D and other game-related tasks. As a result, developer tools are beginning to take advantage of their browser's managed architecture making it easier to tweak and debug content. In other words: you can poke your 3D scene as it is being rendered.
Now this is quite interesting. Basically all of the GPU's involvement in drawing a 3D scene comes down to two scripts (at least for WebGL 1.0): a vertex shader and a fragment shader. These are operations that run once for every vertex in a scene and once for every pixel an object in a scene occupies, respectively. Together they form a "program" which gives an object's geometry something tangible for users to see.
Here is an example of Unreal Engine 3 being modified at runtime.
The developer tools within Firefox 27 will allow you to modify these scripts at runtime and even turn specific draw calls on or off. This should vastly speed up the rate at which developers modify their effects especially when it comes to fine tuning specific variables such as the rate that waves flow in a water material.
Firefox 27 is expected to be the release version in early February; it is currently in the Aurora channel.
Subject: General Tech | December 5, 2013 - 03:59 AM | Scott Michaud
Tagged: GCC, Rust, mozilla
Rust is an interesting language in that it aims to be safe and concurrent. It was discussed frequently at Mozilla Summit back in early October both on its own and in terms of the experimental HTML5 rendering engine, Servo. From how it was describe to me from other attendees, it prides itself on its task-based architecture. Basically, your application is (or, at least, is often) set up like a bunch of tasks that get scheduled concurrently and pass messages to one another if they want to communicate. This concept allow for efficient multithreading because each task is inherently independent.
This may remind you of the experiments John Carmack did with Wolfenstein and Haskell.
Apparently at least one developer from the GNU Compiler Collection (GCC) is also paying attention. Philip Herron has been working on the "gccrs" branch to create a GCC front-end for Mozilla's language.
We will need languages like Rust in the near future as processors continue to ramp up in thread count. Just look at the Xeon Phi story from last week: a bootable 288-thread standalone processor based on the Silvermont architecture. If you want this processor to be used efficiently then you better be light on the main thread otherwise your 6 TFLOPs (3 TFLOPs double-precision) will only be quick to behave like an Atom.
Subject: General Tech, Mobile, Shows and Expos | October 7, 2013 - 11:55 PM | Scott Michaud
Tagged: Mozilla Summit 2013, mozilla
Summit 2013 came to an end on Sunday after a few closing keynotes, breakout sessions, a tour of the Mozilla Toronto campus, and interpretive dancing of what the fox says. Do not worry, Mozillians in our audience, I will only interpretively illustrate the interpretive dance with a totally unironic Shockwave Flash screenshot.
Real smooth moves, indeed.
On the topic of Flash demos, the first session I attended included an extended preview of Shumway. As discussed in Day 2, the project intends to keep Flash content alive after the platform fades. A few demos were shown to attendees including a signification portion of the HomestarRunner email, "Your Friends", where Strong Bad harms the entire cast except himself and The Poopsmith (and other off-cast or yet-to-be-introduced characters, of course). The video played just about perfectly.
BananaBread OF DOOM!
"Bananabread" was also modified into a special demo showing live textures from video elements. The game even projected a separate game of Doom against the wall of the level. This can, of course, be used for non-gaming projects as well; projects have been developed to use shader effects on web camera video for GPU-accelerated post-processing tasks.
The closing ceremonies followed the breakout sessions and mostly thanked their community. A few "Mozillians" were voted by their peers for their popular influence and were recognized with signed posters and, in one case, a paid trip to any Mozilla campus in the world. Plus, people were hugged by a fox; a picture is worth a thousand words.
The last event of the day, at least the last one relevant to a computer hardware website, was a tour of the Mozilla Toronto campus. The office is structured in departments around a central kitchen, restroom, and discussion area. They attempt to have a sort-of Canadian cottage feel with a couple of Adirondack chairs and a wood-beam ceiling. There is also a group of desks called "Benoits St." because, well, it just so happens everyone who works in that section is named Benoit.
Community Room with its reconfigurable tables and musical corner.
Thus ends the coverage of Mozilla Summit 2013, Toronto.
Subject: General Tech, Mobile, Shows and Expos | October 6, 2013 - 01:14 PM | Scott Michaud
Tagged: mozilla, Mozilla Summit 2013
The second day of Mozilla Summit 2013 kicked off with three more keynote speeches, a technology fair, and two blocks of panels. After two days and about two dozen demos, several extremely experimental, I am surprised to only see one legitimate demo fail attempting to connect two 3D browser games in multiplayer over WebRTC… and that seemed to be the fault of a stray automatic Windows Update on the host PC.
Okay technically another demo “failed” because an audience member asked, from the crowd, to browse a Mozilla Labs browser prototype, Servo, to an arbitrary website which required HTTPS and causing the engine to nope. I do not count that one.
Lastly, we saw a demo of the APC Paper which is expected to lead Firefox OS into the desktop market. It is actually a little smaller than I expected from the pictures.
One more day before everyone heads home. So far not much has happened but I will keep you updated as things occur.
Get notified when we go live!