Skip to main content

Mozilla, DRM, and Fighting Smart

News came out of Mozilla that was of zero surprise to me, and many others, but did upset and surprise a great number of people. Mozilla, long time champion of a free and open web, is backing down on their stance to never incorporate the new DRM mechanisms in HTML5 into Firefox. Firefox will officially support blackbox DRM’ed content played back exclusively through closed source components.
The new DRM support in HTML5 has been inevitable for some time. It is not inevitable because DRM is a good thing (it is not) or because the media companies are too powerful to fight (they are not). The inevitability of this beachhead was all due to two names on the draft authorship list: a developer from Google (the company that brings you the Chrome browser) and a developer from Microsoft (of Internet Explorer). When this DRM spec was first proposed it was obviously inevitable because it did not come from outside, but from within, and with a foothold in two of the most popular browsers in the world. It was obvious that from Day One both would support these new capabilities, that Netflix (also a co-author) and many other media sites would utilize it, and that users would be left with either a severely limited web experience or the option to leave Firefox behind.
Mozilla tried to make a stand and it was entirely admirable.
It was not, however, practical even for a second.
DRM can be beaten. DRM can be made irrelevant. DRM can even be made detrimental to the very media corporation profits that drove it into existence in the first place! This is not the day when these statements can be made in the present tense. The fight we have before us is a long-haul fight.
Had Firefox been kept out of this game entirely, it could not participate in that fight at all. We could all see the writing on the wall when Mozilla so valiantly tried to make their stand. Had they continued, we would have seen them launch (I’m sure of this) some campaign to push DRM free video portals as alternatives, to showcase that now all video content requires these measures. They would have been laughably limited and done little more than to showcase the (current) need to give users access to the content they actually do care about.
That is why, for the time being, this was the right move.
Firefox will continue to allow users to access Netflix and Hulu and Youtube content that requires silly measures to make content owners comfortable. Staying in the fight today will allow Mozilla to contribute to the fight for a long time coming, and I do think this will be a long time fight.

I just don’t know what that fight will entail.

Comments

Post a Comment

Popular posts from this blog

CARDIAC: The Cardboard Computer

I am just so excited about this. CARDIAC. The Cardboard Computer. How cool is that? This piece of history is amazing and better than that: it is extremely accessible. This fantastic design was built in 1969 by David Hagelbarger at Bell Labs to explain what computers were to those who would otherwise have no exposure to them. Miraculously, the CARDIAC (CARDboard Interactive Aid to Computation) was able to actually function as a slow and rudimentary computer.  One of the most fascinating aspects of this gem is that at the time of its publication the scope it was able to demonstrate was actually useful in explaining what a computer was. Could you imagine trying to explain computers today with anything close to the CARDIAC? It had 100 memory locations and only ten instructions. The memory held signed 3-digit numbers (-999 through 999) and instructions could be encoded such that the first digit was the instruction and the second two digits were the address of memory to operat...
1 comment
Read more

Statement Functions

At a small suggestion in #python, I wrote up a simple module that allows the use of many python statements in places requiring statements. This post serves as the announcement and documentation. You can find the release here . The pattern is the statement's keyword appended with a single underscore, so the first, of course, is print_. The example writes 'some+text' to an IOString for a URL query string. This mostly follows what it seems the print function will be in py3k. print_("some", "text", outfile=query_iostring, sep="+", end="") An obvious second choice was to wrap if statements. They take a condition value, and expect a truth value or callback an an optional else value or callback. Values and callbacks are named if_true, cb_true, if_false, and cb_false. if_(raw_input("Continue?")=="Y", cb_true=play_game, cb_false=quit) Of course, often your else might be an error case, so raising an exception could be useful...
1 comment
Read more

Announcing Feet, a Python Runner

I've been working on a problem that's bugged me for about as long as I've used Python and I want to announce my stab at a solution, finally! I've been working on the problem of "How do i get this little thing I made to my friend so they can try it out?" Python is great. Python is especially a great language to get started in, when you don't know a lot about software development, and probably don't even know a lot about computers in general. Yes, Python has a lot of options for tackling some of these distribution problems for games and apps. Py2EXE was an early option, PyInstaller is very popular now, and PyOxide is an interesting recent entry. These can be great options, but they didn't fit the kind of use case and experience that made sense to me. I'd never really been about to put my finger on it, until earlier this year: Python needs LÖVE . LÖVE, also known as "Love 2D", is a game engine that makes it super easy to build ...
Post a Comment
Read more