An Association Game

Here’s an association or riddle game that Mika and I created last night that I found interesting.

  • Give a player a list of three random, dissimilar objects (e.g., pancakes, manhole covers, and condominiums). Tell them that you are thinking of some quality or feature shared by all three and ask them to tell you what it might be.
  • After letting them think for some time, or even after supplying answers, tell the player that you lied and that you didn’t have an answer in mind. In fact, the goal of the game is to come up with any and all associations.

Most people I’ve talked feel that the problem becomes easier after one realizes that there isn’t a correct answer. Of course, the strategy that the second stage invites (thinking of anything without the idea that the answer might be right or wrong) is exactly what the player should have been doing from the beginning. Why don’t we? In what situations might we be more creative problem solvers if we pretended that there isn’t a correct answer?

Bring the Bling?

I’m been perplexed by the recent fracas around the possibility of Ubuntu shipping non-free drivers by default as part of the feisty release goal to bring the bling. The issue has been discussed by many people, most recently and eloquently in a blog post by Scott James Remnant.

I have never been 100% comfortable with our (Ubuntu’s) decision to ship proprietary drivers. The Ubuntu philosophy document — which Mark Shuttleworth and I drafted originally — says quite unambiguously:

Every computer user should have the freedom to run, copy, distribute, study, share, change and improve their software for any purpose, without paying licensing fees.

I believe this deeply. Consequently, I feel that binary drivers in Ubuntu are, and always have been, a failure to live up to our principles. If our philosophy document is still representative, most people in our community should be a little uncomfortable with them — even if they think, as most of us do, that shipping them is the correct thing to do.

Early on Ubuntu decided that binary firmware and hardware drivers would be distributed and quasi-supported in restricted. While not completely comfortable with the move, I could understand and defend it for three reasons:

  1. The drivers were easily removable and not enabled by default unless necessary to achieve functioning hardware.
  2. As part of this process, we promised to work with vendors to accelerate the freeing/open-sourcing of their drivers.
  3. Perhaps most importantly, I couldn’t imagine not using them if it were the choice between non-free drivers or inoperable hardware.

The proposal to include proprietary nVidia driver in place of the existing free nVidia driver is important because it changes, or eliminates, the first and third justifications. Since the first issue has been discussed in depth, it seem appropriate to focus on the third and final point. The point is perhaps best introduced with an observation:

While I have met many people who research and buy hardware to avoid the need for non-free drivers, something I do myself, I have never met anyone who voluntarily chooses inoperable hardware on a computer they use over working hardware through a non-free driver.

While not airtight, this observation is precisely why the old policy of using non-free drivers only when no free drivers exist works so well. By effectively synonymizing use of the non-free driver with use of the hardware, the crisis created by non-free drivers is rendered paradoxical: anybody using a piece of hardware that only works with non-free drivers is, by definition, either using non-free drivers or not using the hardware. The only way to not use non-free drivers in situations where no free drivers exist is to not use hardware that requires them. If you use different hardware, you will not need to use non-free drivers. This important justification is completely inapplicable to the proposal to include non-free drivers in place of free (but not perfect) alternatives.

Second, while shipping non-free drivers is wrong because we lose our freedom and violate our philosophy, the desire for basic hardware support is universal and important enough that it’s defensible. One reason that the "binary by default for bling" situation alarms me is that I don’t believe that the desire for desktop bling is as universal, or as strong, as the desire for working hardware.

An analogy might be stealing food to feed your family and stealing a CD from the record store. Both are wrong because stealing is wrong, but I have a lot more sympathy for the hungry thief in the first example because CDs are not as necessary as food and because many people would rather go without a new CD than steal. We can ask: "Which is worse: selling your soul for a decent job or selling your soul for a PS3?" In an absolute sense, neither is worse; but it’s easier to support the former than the latter. I’m very impressed with Beryl — but I have trouble empathizing strongly with the need for a spinning desktop cube.

New users may be impressed and attracted to an Ubuntu desktop powered by proprietary drivers. They might also be impressed by proprietary applications. However, it is self-defeating to attract new users to our free platform and principles by compromising our core values. Many users already make the decision to use non-free video drivers and Ubuntu makes it very easy to do so once they have made that choice. Installing binary drivers by default is choosing for the large number of users who will stick with any default. It may be a conservative stance but as long as we believe that a non-insignificant number of users would choose to live without bling before compromising Ubuntu’s philosophy and goals, we should make the difficult decision to side with freedom by default.

When discussing this issue, many people say, it’s not my decision or it isn’t my call. Regardless of whether anyone agrees with me and regardless of who the final decision is up to — and it’s not clear to me now — I believe that the Ubuntu community has the power to inform and shape the development of their distribution. As the Ubuntu community, we can make our position heard. The best place to do that right now seems to be the Accelerated X specification comments page. One can also email the the Technical Board (for technical comments) and the Community Council (for principle or philosophy related issues).

Support Parallel Distribution Now!

My friend James Grimmelmann, currently a Resident Fellow of the Information Society Project at Yale Law School and an Adjunct Professor at New York Law School, contacted me recently because he was concerned that it doesn’t seem likely that parallel distribution language is going to make it in latest draft of the Creative Commons 3.0 licenses. The issues and arguments around parallel distribution are complex but James and I both think that the status quo represents a mistake and a lost opportunity by CC. As a result, we have written a position statement that tries to explain the issues simply, make a case for parallel distribution, and answer some of the criticism that has been leveled against the idea.

Prompted by conversations with hackers from Debian (myself included), CC lawyers recommend new "parallel distribution" language at the beginning of the CC 3.0 license revision process as a way to fix unanticipated effects of the current CC anti-DRM clause. Immediate negative reactions by a number of people demoted the language to an issue for debate. While the resulting debate has been both lengthy and heated, it has not involved more than a small handful of voices or led to any firm decisions. Time is running out for the drafts of CC’s 3.0 licenses and unless something changes, the status quo — no parallel distribution — will remain. As a result, it’s extremely important that users of CC licenses try to familiarize themselves with the issue and to make their voice heard.

James and I feel the lack of a parallel distribution language in the CC licenses represents a failure by CC to live up to its own ideals and to do what is in the best interest of the users of CC licenses. Please read our position statement, pass the link and article around to others, and make yourself heard either on the cc-licenses list by emailing cc-licenses@lists.ibiblio.org or by posting a response on the comments page in my wiki.

Finally, as a Debian developer, it’s important for me to say that I do not think that the lack of parallel distribution makes the CC licenses non-free under the DFSG — especially in light of the recent general resolution on the GFDL which deemed the GFDL, which contains language that is extremely similar to the current CC text, DFSG free. CC should use parallel distribution language because it is the right thing to do for the free culture movement and for the users of CC works and not because it will have any effect on the inclusion of CC BY and BY-SA works in Debian.

You can find the position statement at: http://wiki.mako.cc/ParallelDistribution

Poor Santa

I think it wold be a good idea if companies did not typeset their bicycles in ways that remind people of falling.

/copyrighteous/images/santa_fell.jpg

With that said, the red and white theme is a particularly nice touch in this case.

Writing and Writing Code

Over the years, I’ve published some of the articles I am most proud of on Advogato. As you can imagine, I was sad to see demise of Advogato announced early September and thrilled to see that by the end of the month, Steve Rainwater had stepped up to save the site.

For a belated welcome of Advogato back from the edge of the grave, I’ve published a short essay about the effectiveness of an analogy of software and writing on the site. In it, I introduce the analogy and argue that it is useful in advocating free software and programming education and in justifying the disproportionately large amount of programming related projects in the free software world. Here’s the intro:

Advocates of free and open source software, myself included, like to talk about the "democratizing" effect of free software. Others, especially non-programmers, are quick to point out that the only technical people can take advantage of half of the enumerated freedoms in FOSS. The freedoms to modify and collaborate mean little if you don’t know to program. Over time, I have come to the conclusion that the only good solution to this problem — and one that I was initially quite opposed to — is to teach everyone to program. In considering this position, the processes of reading and writing provide a useful analogy when considering the processes of using and creating computer software. Additionally, the analogy provides an powerful justification for the fact that FOSS programmers produce a disproportionately large amount of software that is primarily of interest to FOSS programmers.

Please check it out on Advogato and feel free to leave a comment on my blog if you don’t have an Advogato account.

Hard Work

Our ice cream was out of the freezer a bit too long and got soft. When I went to extract it from its container, the ease with which I could scoop it led me to spoon out two or three times what I might normally have served myself.

It’s interesting to consider that perhaps my thinness is due at least in part to my laziness and frugality in obtaining food.

Once Again…

Overheard on my flight back from San Francisco last week… over the PA system:

Once again, we are keeping our PAs to an absolute minimum on this flight.

Perhaps not an absolute minimum.

Small Subgroup of a Small Subgroup

With the new Charlie Card coming out, it seemed like it was about time to obtain an RFID blocking wallet. I liked the idea of buying a nice off-the-shelf wallet but the only pre-made RFID-proof wallet I’ve found is made of leather. I’d like to buy a vegan wallet.

Here is the Venn diagram describing my problem:

/copyrighteous/images/vegan-wallets.png

If you know a wallet for those of us in the purple zone, leave a comment or let me know. Otherwise, I suppose I’m going to have to make my own.

Dare to DReaM?

I went to a talk today by Sun scientist Susan Landau on Sun’s DReaM/Open Media Commons DRM system that I’ve mentioned in the past. Landau used a variant of these slides to do a rough overview of the Sun system and the problems that it is trying to solve.

Halfway through her talk, Landau showed a slide titled, "Users Matter: Creative Commons." Elaborating, Landau mentioned that she had been talking to a number of people — both at CC and outside — about the possibility of using DReaM to enforce the terms of CC licenses.

I interrupted Landau to point out that CC licenses had an anti-DRM clause that, as far I knew, would make her system unusable on CC content. The CC anti-DRM clause, plus the resistance of the CC and iCommons community to accept parallel distribution language, are why it’s impossible to play CC-licensed works on an unmodified PlayStation or XBox (these systems only play signed disks) — even if you include an unencumbered copy alongside! Landau reassured me that I must be mistaken and that she had talked about DReaM in depth with CC leadership, lawyers, and technical advisory board members and she was sure her system was at least possible. Puzzled, I shut up.

For most of the rest of her talk, Landau talked about fair use and how a DRM system might go about respecting it. In his qualified endorsement of the DRM system, Lessig mentioned that DReaM, "would be implemented to allow individuals to assert ‘fair use,’ and unlock DRM’d content, with a tag to trace misuse." At the time, I had a hard time imagining how fair use could be built into such a system — separating fair from unfair use is remarkably resistant to technical solutions. Even bright light cases like verbatim copies every page of the Encyclopedia Britannica might be fair use if I were to make them into a paper mâché bust of Johann Gutenburg or use them to wallpaper a gallery wall.

Landau’s acknowledged the trickiness around fair use and suggested a compromise:

By default, works might be encumbered in the ways and to the degrees that the copyright holder wish. However, users could petition for an unencumbered "fair use copy" by identifying themselves and then checking some boxes and explaining (briefly) why they think their use for the work qualifies as fair. Once they’ve done this, the system would present the user with an unencumbered, watermarked, and fully traceable piece of media.

Conceivably, requests would be subject to some sort of review (at the very least to prevent automated requests) and non-fair uses of watermarked goods would be strictly tracked. If a "fair use" copy is found in the wild, the watermark would be traced and the originator would be held liable. Of course, anonymous fair use becomes impossible but, as Simson Garfinkel pointed out at Landau’s talk, users may have a right to anonymous speech and to fair use but not to anonymous fair use. "Fair" enough.

It is perhaps important to point out that DReaM does not currently implement this "fair use" system and that, one can only assume, the vast majority of DReaM users (e.g., Hollywood movie studios and their ilk) would have no little interest in giving their users a blanket ability to make "fair use copies" and would in most cases choose not to enable such an option.

But let’s return to the issue of DRM enforcement of CC license terms. While I was initially quite confused by the idea of DRM enforcement of CC license terms, it made much more sense when I looked at the CC anti-DRM clause itself:

You may not distribute, publicly display, publicly perform, or publicly digitally perform the Work with any technological measures that control access or use of the Work in a manner inconsistent with the terms of this License Agreement.

The emphasis (mine) points to the crux of the issue. The CC anti-DRM clause only blocks technological measures that overstep the boundaries set in the rest of the licensee. For the free licenses, that’s a wide boundary that leaves little room for DRM. But as I’ve pointed out before, CC is a lot more than just free licenses.

Landau mentioned that her group was primarily interested in using the DReaM system to enforce attribution and non-derivative work clauses in CC licenses — a wise choice as non-commercial use is hard enough for humans to discern. As a result, the DReaM system might be used to make it impossible to remove attribution from CC works or might block modification to works marked as "ND." The catch that led me to believe that CC license blocked all DRM was the fact that I didn’t think it would be possible for a DRM system to respect fair use. After all, each CC license includes an explicit affirmation that, "nothing in this license is intended to reduce, limit, or restrict any rights arising from fair use."

The question that the possibility of a CC DRM scheme like DReaM hangs on is: to what degree does Landau’s suggestion live up to the fair use legal bargain?

Landau pointed out that a number of lawyers including Pam Samuelson and CC’s technical advisory board and legal staff have been generally positive about her fair use permission-asking compromise. Honestly and on CC’s own terms, it’s hard to see why they wouldn’t be. The loss of anonymous fair use was only ever a right we enjoyed by a fortunate accident. Watermarks are only there to "keep honest people honest." If you are not doing anything wrong, what do you have to hide?

But DReaM enforcement of CC licenses is a bad thing and the bad taste that it inevitably leaves in many commoners mouths is not hard to explain:

  • Many commoners are not comfortable with the idea of DRM because it shifts power over users’ computing devices away from the users and makes computers obey the will of a copyright holder. That’s true of DReaM just as much as as it is of Apple iTunes or Microsoft DRM.
  • Many commoners are not completely comfortable with all CC licenses, so the idea of technical protection measures enforcing these terms, even those allowing for fair use lines and in line with the will of the author, is seen as dangerous.

To solve the first issue, CC needs a more strongly worded anti-DRM clause — ideally one tied to a parallel distribution clause. To solve the second, we will ultimately need a new banner under which only truly free cultural works will reside.

Susan Landau doesn’t have it easy but she does seem to have the genuine best interest of consumers and users at heart. That’s more than I can say about the vast majority of people in the DRM business. She’s trying to walk a fine line and she’s almost certainly being abused and heckled by folks in the industry who call her "communist" and by folks like me who feel that she’s sacrificing essential principles in an attempt to compromise. The one thing we all agree on is that the ground she’s treading is mine field.

Yet while I sympathize with her, I must speak out against both her and DReaM. A DRM compromise at this stage would be insanity. This is a fight we have to win.

Ignorance is Bliss

A banker at my hippy bank had never heard of Google. I had to spell the name out and explain it to her!

I’ve never imagined one could feel so happy about their choice of financial institution.

iRony RockBox Installer

In my blog post yesterday I described iRony, an install party I helped organize for iPods. In the post, I pointed folks to some resources for holding similar parties.

To help with mass installs at our party, I wrote a simple installer for RockBox in Python that would run on GNU/Linux. With a few modifications, the script could be relatively easily converted to also run on Mac OS X.

While an unofficial installer exists for Windows, my installer, simply called the iRony RockBox Installer, seems to be the first installer for GNU/Linux.

Of course, the installer is still largely rough and untested and is definitely unsupported by the RockBox team. If you get around to trying it, please send me feedback, advice, or and patches. You can grab it (and future version) here: http://mako.cc/projects/irony/

iPod Liberation!

About a month ago, I announced an iPod liberation party (i.e., an install-fest for free/open source software onto iPods). The summary, now several weeks after the fact, was that the party was a total success. More than fifty people attended and several dozens iPods were liberated. Pictures and information on the event are now online.

Over the past few weeks, I’ve been polishing a RockBox installer that I wrote for the event, writing up an article published on NewsForge today, and documenting the process for those that want to hold their own similar events.

If you are unconvinced on the subject of iPod liberation, read the NewsForge article written with others from my research group and Harvard Free Culture. Most of the rest of the information on our party and information on throwing your own party exists in sub-pages from the iPod Liberation page in the Free Culture wiki.

I’m looking forward to seeing a whole string of similar parties run by LUGs and other interested groups. It’s a great way to get out a message about software freedom, DRM and about freedom on devices other than computers.