Copyrighteous

At OSCON this year, I'm going to be giving a talk about "antifeatures." Antifeatures are a way to describe a particular practice made possible by locked down technologies. Antifeatures, as I describe them, are functionality (i.e., "features) that a technology developer will charge users not to include. You can read my short article on the topic published in the FSF bulletin in 2007 for a series of examples and a more in-depth description.

One thing I want to do is put together as large a collection of these antifeatures as possible before the talk. Please read the article if you haven't already and send me examples of other antifeatures either as a comment or in email to mako@atdot.cc. Credit and my deep gratitude will be given to anybody who sends me something. A prize in the form of a real Dutch flessenlikker will given to the best example I get.

Dafydd Harries pointed me to this announcement of a "Firewall Install" version of GitHub. Basically, it's a locally installed version of GitHub designed to serve those that, “wish to enjoy the benefits of GitHub, but are unable to do so because of corporate restrictions or laws that prevent you from hosting your code with a third-party service.”

Daf and I put a little time in writing up a short reflection which I've posed over on autonomo.us. Our key points are that this represents an important compromise in the rough direction of autonomy by an important cloud player and that, unexpectedly perhaps, it has been motivated by organizations under strong institutional pressures — groups like large firms and governments. Although it certainly makes sense that these players would be reluctant to “outsource” to centralized systems, we argue that these groups might provide an unlikely ally in at least part of the fight for autonomy.

After a week at the International Open and User Innovation Workshop 2009 in Hamburg, I'm in Berlin again this week. I've got nothing concrete planned other than spending most of my days hacking on a few projects. Let me know if you're around and would like to meet up.

I'll post more about my travel and talks schedule this summer as things firm up in the next couple weeks.

When he was my adviser at the MIT Media Lab, I used to feel bad that I had trouble spelling Chris Csikszentmihályi's name. As this screenshot from Chris' Dopplr page shows, I am apparently in good company.

I finally got around to pushing out a new version of AttachCheck --- a trivial little program I wrote several years ago that tries to prevent people from having to send followup emails with subjects that include phrases like, "REALLY attached this time," by asking you for confirmation when you send an email that says you've attached something when it looks like you haven't.

The release fixes a single bug that affected a few users --- thanks to Iain Murray who sent the patch in and apologies to him and others for taking a while to push it out.

There's very little to AttachCheck and, if I remember correctly, it was the very first program I wrote in Python. I'm only mentioning this revision because it's been quite a few years since I last mentioned the program and, while the script doesn't do much, it continues to save me a little embarrassment and effort every other week or so.

About a year ago, I read American Gothic by Steven Biel and the book has left a surprising lasting impression on me. The book describes the background, history, and life of "American Gothic: America's most famous painting" by Grant Wood. Even if you don't recognize the name "American Gothic", you are likely to recognize the picture or the scene. The book is a serious and -- as far as I can tell -- reasonably comprehensive treatment of the subject that is interesting, insightful at points, and a breeze to read.

Of course, the book is not actually about the painting that hangs in the Art Institute of Chicago -- although it will certainly teach you more than you probably ever wanted to know about that painting, its subjects, its settings, etc. The book is really the story of how that paining has been received, understood, and used. Nearly half of the book focuses on examples of people who have remixed, reworked, reimagined, and reproduced the painting in myriad forms, formats, settings, and ways. The book contains scores of photographs of celebrities posing in American Gothic style settings, dozens of political cartoons based on the paintings, images of talk shows, magazine covers, Broadway plays, product advertisements, toys, gifts, kitch, and more, done up in recognizeable representations of the basic American Gothic form. There is a very incomplete of references to American Gothic in popular culture at Wikipedia that can give a tiny taste of what is out there.

The last chapter of the book is devoted to these "parodies" and there's some brief talk of issues around copyright and control of the image. Wood's sister Nan was the owner of the copyright for much of the second half of the twentieth century and is also the woman in the painting. She famously charged several makers of more lurid take-offs with defamation and successfully blocked a number of remixes. In 1988, Nan transferred ownership to the Visual Artists and Galleries Association (VAGA) which will hold the copyright until 2025. VAGA also claims "rights of publicity" in Nan's image which will last until 2060. VAGA takes a very expansive view of its copyright claims and argues that it has both veto power and royalty rights to any recognizably similar work. For example, VAGA does not want the American Gothic image used in alcohol advertisements and has successfully had such ads pulled. Biel's book contains no reference to the amount of money made from licensing the work but one can only conclude that it must be massive. VAGA blocked a plan by Iowa to use the picture on the back of the Iowa state quarter due to licensing disagreements; instead Iowa used a different Wood painting that was clearly in the public domain.

What struck me most about Biel's book is related to just how deeply ingrained in American culture the American Gothic image has become. The book cites simple surveys that show that almost every American recognizes the painting (although only a small fraction know the painting's name or who painted it). The thousands of parodies that the book documents are testament to the fact that the painting has become a way of representing something essential about American culture and its values. But in a strange way, the painting's popularity and incessant reuse has also made it part of the culture that it so effectively captured.

We can think of culture as a set of shared values and references that help us related to each other and to communicate. Just like idioms in language, culture helps us communicate more effectively, certainly, but also lets us communicate messages that would not be communicable otherwise. When Out Magazine, Coors, or any of several dozen others replace the figures in American Gothic with a gay or lesbian couple, they are succinctly sending a message about homosexual relationships and American traditional values that could not be made any other way. In this way, American Gothic -- both the painting and Biel's book -- represent a strong argument for free culture.

If American Society has infused American Gothic with so much value, how can it be fair to let one person or organization own it? Are they not owning an essential mode through which a society can relate, experience, and communicate? I can't help but conclude that it shouldn't matter if VAGA does not like alcohol, advertisements, homosexuality, or wants to make a some money every time someone makes a cartoon parody. These are trivial concerns next to the importance of our society's need to communicate about these issues. If doing so requires the use of a shared cultural reference in VAGA's painting, I find it hard to justify VAGA's position of control.

We need to be able to reproduce and reimagine American Gothic because it has become part of us. It's a striking example of the way that art becomes culture and the reason that truly free culture is the only appropriate response. We can't afford to let our experience of the world and each other -- to let ourselves at a very fundamental level -- be owned and controlled.

I had an existential experience in my local drug store last night while pondering this sign.

What does it mean for pain to be truly external to the person feeling it? Have I ever felt external pain? Is external pain merely another term for empathy? What might products to help with empathy entail? Would my local drug store stock them?

If you're interested in free software --- and free network services in particular --- and should try to join me in Boston for the weekend of March 21st and 22nd.

The FSF is organizing its annual members meeting again. This year the model is very different. For a start, the audience isn't limited to FSF members and the conference is not just about FSF projects and work.

Instead, the meeting has been rebranded LibrePlanet and has been broken up into a two-day event that is going to talk about and then try to tackle some of the biggest problems facing the world of free and open source software. Saturday March 21st will feature a series of talks about major issues facing free software. Sunday March 22nd will be focused on an unconference attempt to tackle and explore several of the key themes or tracks: network services, high priority projects, and the nascent LibrePlanet activism network.

I'll be focused on the track around free network services which I'm helping organize in part through Autonomo.us. For more information on that angle, please take a look at my blog post over at Autonomo.us. We're going to have a great group of people at the track and I'm excited by the idea that that we'll be able to make some real progress on the issues.

I encourage anyone who thinks they might be able to make it to consider doing so. There are details including travel, location, hotel information and much more on the event web page and wiki (login is required to RSVP). Please spread the word!

I recently ate a bag of potato chips made by FoodShouldTasteGood, Inc.. Their motto (as printed on that bag under their name) was, "It's our name. It's our brand. It's our motto." Now, either the antecedents for those three it's are different -- which seems implausible -- or their motto is lying in its final sentence. It's all very complicated.

Seth Schoen reminded me of a somewhat similar issue with the United States' national anthem, The Star Spangled Banner. The final stanza includes the line, "And this be our motto—'In God is our trust.'" This is not and has never been the U.S. motto. In fact, the U.S. had no motto at all until 1956 when "In God We Trust" -- which is very similar, but not quite the same -- became official.

It seems that nobody is quite sure where "In God We Trust" came from but there is some speculation that it originated in the anthem itself. Presumably, it became the motto because lawmakers thought it sounded good in the song and not because the U.S. government failed while trying to "correct" the embarrassing incorrect line in its anthem.

When I explain the importance of free software, I often use some variation of the following example:

Suppose I see a beautiful sunset and I want to describe it to a loved one on the other side of the world. Today's communication technology makes this possible. In the process, however, the technology in question puts constraints on message communicated. For example, if I pick up my cellphone, my description of the sunset will be limited to words and sounds that can be transmitted by phone. If I happen to have a camera phone and the ability to send a picture message, I will be able to communicate a very different type of description. If I'm limited to 150 characters in an SMS message, my message will be constrained differently again.

The point of the example is this: the technology I use to communicate puts limits and constraints on my communication. Technology defines what I can say, how I can say it, when I can say it, and even who I can say it to.

This is neither good nor bad. It is simply the nature of technology. But it means that those who control our technology control us, to some degree. As information technology becomes increasingly central to our lives, the way we experience, understand, and act in the world is increasingly controlled by technology and, by extension, by those who control technology.

I believe that the single most important struggle for freedom in the twenty first century is over the question of who will set these terms. Who will control the technology that controls our lives?

Free software can be understood as an answer to this question: An answer in the form of an unambiguous statement that technology must be under the control of its users. When free software triumphs, we will live in a world where users control their technological destiny. We simply cannot afford to fail.

The Free Software Foundation is the most important organization fighting for the rights of users in this struggle. Here are some of the ways that I plan to direct the FSF to support software freedom in the coming year:

Network Services

Last year, the FSF organized a meeting on software freedom and network services that lead to the creation of the Autonomo.us group and the release of the Franklin Street Statement on Freedom and Network Services. As network services --- like those built by Facebook, Google, and others --- continue rise in popularity, progress in this conversation is of increasing importance.

This year, I will direct the FSF to build on the work of Autonomo.us to launch the first of what I hope will be several FSF position statements on software freedom and network services. More importantly, the FSF will begin to provide support and planning for solutions --- technologies, social campaigns, and legal steps --- that will protect computer users whose freedom is currently threatened by network services.

Enforcing free software licenses

Early on, people who decided to work on free software did so because they agreed with --- or, at the very least, were willing to abide by --- the principles and rules laid out in our licenses. In our push for software freedom, we have created software of immense value and attracted companies and individuals to our community who are less willing, or simply less interested, in protecting users' freedom.

In December 2008, the FSF went to court for the first time in the organization's history to force Cisco to uphold the freedom of the users of FSF copyrighted software. This lawsuit asks Cisco to live up to its obligations under the GPL and to ensure that it does so in the future. The FSF needs the support of its community in this and in future enforcement actions.

The FSF has operated a compliance lab for several years and has ensured software freedom for countless users. As free software becomes more successful in the next year, the FSF will be playing an increased role in protecting software freedom from those who do not share its principles.

Continuing the fight against software patents

As I said last year, one cannot write non-trivial software today without running a serious risk of infringing patents. The software patent minefield we've found ourselves in is a very fundamental threat to the success of free software and we've already begun to see the first casualties and costs. We must eliminate software patents. Now. The FSF will continue its work toward this end.

The FSF's End Software Patents project's major contribution this year was a brief submitted in the In Re Bilski case at the U.S. Court of Appeals for the Federal Circuit. Recently, an opinion was issued which seems to mark an important shift away from broad protection for software patents. With this victory, now is the time to keep up this momentum. The FSF is drawing up a strategy to do just this and will be announcing the relaunch of its campaign on February 9,2009 led by Ciaran O'Riordan.

Every recent fundraising appeal seems to mention the difficult economic climate and it seems to cliche to do so here. That said, the effect of a bad economy is, in fact, felt most strongly in non-profits dependent on donations. The FSF is not immune.

The FSF's work is essential for success on the issues I've described here and on all of its other campaigns and projects. Although the cost of a membership or donation may be less easy to afford this year for many of you, the free software movement cannot afford a weakened FSF at this important moment.

If you are not an FSF associate member, now is the time to become one. If you are already a member, please join me in giving generously through a tax-deductible donation. The FSF is a very lean, very humble organization of passionate and dedicated individuals working tirelessly for software freedom. Every single gift makes a difference.

Over two years ago, the FSF started its BadVista campaign with the goal of educating the public on problems related to software freedom, DRM, and more, with Microsoft's latest operating system. Today, the FSF is declaring victory; the name "Vista" is synonymous in the public eye with failure.

The real credit, I suppose, should go to Microsoft. Vista's design put the desires of big media companies, software companies, and Microsoft itself ahead of the desires of users. Vista defeated itself.

But the FSF's campaign drew a huge amount attention to the problems with Vista --- especially early on --- and provided a central location aggregating and amplifying criticism of Vista. In doing so, the FSF played an important role in helping the whole process along and in balancing this criticism with a more positive message about free software alternatives.

Gratitude is due to the FSF staff, members, and supports who made BadVista a success. Please read the announcement, Digg the article, support the FSF, and follow its other work in its other campaigns so that all the FSF's work can be as successful as BadVista.

One change and one addition to my current European tour.

First, it looks like we'll be skipping Amsterdam this time and heading straight to London from Zagreb on the evening of January 10th. We'll still plan to arrive in Cambridge before the 13th.

Second, I'll be giving a redux of my Revealing Errors talk at Mama in Zagreb on January 10th at 14:00 as part of the normal skill sharing meeting. It's the longer version of my OSCON keynote with many more examples. Folks who have seen earlier versions of the talk seem to think it's a lot of fun.

If you are in or near Zagreb, you should come!

I was thrilled to be part of a successful Debian bug squashing party organized by MIT's Student Information Processing Board on December 13th. Greg Price, who helped organize the event, did a wonderful write up which he sent to the debian-devel email list.

I though it was worth mentioning the BSP now because I think it's a wonderful model that I'd love to see replicated in Debian and beyond. The event was initiated, organized, run, and executed by people with little or no direct experience with the project. While the organizers went out of their way to recruit several Debian developers and other experts to the party, these experts' role was more in answering questions and helping others. The the majority of the participants -- around 30 of them in total -- had no previous experience doing Debian development.

While the 11 bugs closed or dealt with are the most visible outcome, I'm not sure that it is the most important. The event acted as an important learning experience for everyone involved and, perhaps most centrally, an important first step for most participants from using free software to giving back and participating in the community.

You don't need experience, connections, or a @project.org email address to organize a party like this for Debian or your own free software project. All you really need is a few people, some technical knowledge, an Internet connection, and the desire to make it happen.

Other things can help, of course. In particular, the SIPB folks have packaged up some scripts they used to select bugs to work on and put them online.

Is Richard Stallman leading a secret life as Serbian Nationalist "Chetnik" Zoran Radovanovic?

Mika and I are going to be in Europe for the next few weeks. The tentative plan seems to include these stops:

• Berlin (December 24-31) - Attending the CCC
• Stuttgart (December 31-January 3) - At/around Akademie Schloss Solitude
• Undetermined location in Slovenia (January 3)
• Belgrade (January 3-8)
• Zagreb (January 9-11)
• Amsterdam (January 11-13)
• Cambridge (and|or) London (13-15)

I've got very little planned in the ways of talks or meetings with free software folks and would, as always, be open to arranging these. If you are in or near any of these places and want to plan a dinner, drinks, keysigning, talk, etc., don't hesitate to get in contact with me.

I'll try to keep this wiki page updated with details on the latest plans.

This bottle was found in Mika's biosafety level 2 laboratory.

To address any confusion, isoamyl alcohol is not drinking alcohol and this bottle was bought for use in a scientific lab from a scientific lab supply company. Explanations are welcome.

At Kinokuyina in New York, I noticed that Playboy was sorted into the "Men's Fashion" section of the magazine rack.

Funny. I wasn't under the impression that Playboy's primary selling points included either either men or clothing.

I spent more time than I would like to admit massaging the process that ultimately led to the release of the the GNU Free Documentation License 1.3 (GFDL) by the Free Software Foundation (FSF). Hours counted, it was probably one of my biggest personal projects this year.

The effect is to allow wikis under the GFDL to migrate to the Creative Commons BY-SA license or, as Wikimedia's Erik Möller has proposed, to some sort of dual-license arrangement.

There are many reasons for this change but the most important is that the move reduces very real barriers to collaboration between wikis and free culture projects due to license compatibility. BY-SA has become the GPL of the free culture world and Wikimedia wikis were basically locked out from sharing with a larger community, and vice-versa; projects will no longer have to choose between sharing with Wikipedia and sharing with essentially everyone else. The GFDL has done a wonderful job of helping get Wikimedia projects to where they are today and Möller's proposed switch seems, in my opinion, the best option to continue that work going forward.

The FSF gets a lot of credit (and a lot of flack) for what it does. Offering to "let go" of Wikipedia -- without question the crown jewel of the free culture world -- represents a real relinquishing of a type of political control and power for the FSF. Doing so was not done lightly. But giving communities the choice to increase compatibility and collaboration by switching to a fundamentally similar license was and is, in my opinion, the right thing to do.

Everyone who has worked hard to make this happen deserves the free culture movement's thanks. This list includes Richard Stallman, Brett Smith and Peter Brown of the FSF; James Vasile and Eben Moglen of the SFLC; Erik Möller, Mike Godwin and Shunling Chen of the Wikimedia Foundation.

The FSF in general, and RMS in particular, deserves a huge amount of credit for what it has decided to not do in this case and for giving up control in a way that was responsible and accountable to its principles and to GFDL authors and in the interest of free culture movement more generally. It has not been easy or quick. If you support or appreciate work like this, please support the FSF and express this while doing so. Doing so is an important way to support these essential and almost inherently underappreciated efforts.

The following list is merely a small selection of scholarly articles listed in the ISI Web of Knowledge with "invisible hand" in their title:

• Beyond the Reach of the Invisible Hand
• The Real Invisible Hand: Presidential Appointees in the Administration of George W. Bush
• The Invisible Hand of God, Visible in the History of Chemotherapy
• Does the Latex Glove Fit the Invisible Hand? Application of Market Ideology to the Doctor/Patient Relationship.
• One-Armed Economists and the Invisible Hand.
• Subjective Image of Invisible Hand Coded By Monkey Intraparietal Neurons
• Exploitation - The Invisible Hand Guided By a Blind Eye: Confronting a Flaw in Economic Theory
• The Invisible Hand: Supernatural Agency in Political Economy and the Gothic Novel
• The 'Invisible Man' and the Invisible Hand - H.G. Wells's Critique of Capitalism
• The Dilemmas of Laissez-Faire Population Policy in Capitalist Society: When the Invisible Hand Controls Reproduction.
• Hong Kong Government Policy and Information Technology Innovation: The Invisible Hand, the Helping Hand, and the Hand-Over to China
• Helping Russian Students See the Invisible Hand.
• Hailing with an Invisible Hand: A 'Cosy' Political Dispute Amid the Rise of Neoliberal Politics in Modern Ireland
• Adam Smith's Invisible Hand Is Unstable: Physics and Dynamics Reasoning Applied to Economic Theorizing
• Offering an Invisible Hand: the Rise of the Personal Choice Model for Rationing Public Benefits
• From the Invisible Handshake to the Invisible Hand? How Import Competition Changes the Employment Relationship
• Invisible Hand Effect in an Evolutionary Minority Game Model
• Did the Invisible Hand Rock the Cradle?
• Internet: The Invisible Hand of Deliberation
• The Invisible Hand Has Already Wreaked Much Havoc - About Adam Smith
• Gaussen's Invisible Hand: The University Mechanics and Machine Inspector Moritz Meyerstein: An Instrument Maker in the 19th Century.
• "The Invisible Hand" of the Market or "The Ever-Present Hand" of Management (On New Discussions and Methods in the Field of Economic History)
• Statin Utilisation - Recognising the Role of the Invisible Hand
• The Universe's Invisible Hand.
• How Did the Invisible Hand Handle Industrial Waste? By-Product Development Before the Modern Environmental Era
• When Iron Fist, Visible Hand, and Invisible Hand Meet: Firm-Level Effects of Varying Institutional Environments in China
• Behavioural Genetics: Evolutionary Fingerprint of the 'Invisible Hand'
• The Hunting of Forbidden Books. Censored Books, Persecuted Books, the Story Written By the Invisible Hand
• Identification of Pareto-Improving Policies: Information as the Real Invisible Hand
• The Conspiracy of the Invisible Hand: Anonymous Market Mechanisms and Dark Powers
• The Other Invisible Hand, Delivering Public Services Through Choice
• Reviving the Invisible Hand: the Case for Classical Liberalism in the Twenty-First Century
• Plant Science - The "Invisible Hand" of Floral Chemistry
• Suppressive Effect of Multimodal Surface Representation on Ocular Smooth Pursuit of Invisible Hand
• The Visible Versus the Invisible Hand - A Tension Inherent in Modern Economies
• The Invisible Hand and the Grabbing Hand
• A Close Eye on the Invisible Hand
• The Contracts of Credit in a Long Term Relationship From the Invisible Hand to the Handshake
• Chile's New Entrepreneurs and the "Economic Miracle": The Invisible Hand or a Hand From the State?
• The Invisible Hand or Hands Across the Water, American Consultants and Irish Economic-Policy
• How Would the Invisible Hand Handle Money
• A Helping Hand for the Invisible Hand
• Measuring the Speed of the Invisible Hand - The Macroeconomic Costs of Price Rigidity
• The Invisible Hand Turns Green - Using Economic Instruments to Conserve the Environment
• The Invisible Hand Made Visible, the 'Birth-Mark'
• Trembling Invisible Hand Equilibrium
• Guiding the Invisible Hand - Economic Liberalism and the State in Latin-American History
• The 'Invisible Hand Meets the Dead Hand High Above Washington D.C.'
• From the Invisible Hand to the Gladhand - Understanding a Careerist Orientation to Work
• Public-Sector Reform - Not So Invisible Hand
• Darwin and Paley Meet the Invisible Hand
• Economics as Ideology - On Making the Invisible Hand Invisible
• The Invisible Hand - Poetics and Narration of Verga, the Novelist
• Invisible Hand, Invisible Death
• The Invisible Hand Strikes Back - Motor Insurance and the Erosion of Organized Competition in General Insurance, 1920-38
• The Creeping Invisible Hand - Entrepreneurial Librarianship
• The Speed of the Invisible Hand
• From the Invisible Hand to Visible Feet - Anthropological Studies of Migration and Development
• Invisible Hand, the Marijuana Business
• The Invisible Hand in San Francisco.
• The Invisible Hand That Feeds the Cults - Messianic Capitalism
• Can an Invisible Hand Palpate the Carotid Pulse
• Invisible Hand or Fatherly Hand - Problems of Paternalism in the New Perspective on Health
• Palm-Reading the Invisible Hand - A Critical-Examination of Pro-Competitive Reform Proposals
• The Market as Messiah: The Invisible Hand Strikes Again.
• Federal Legislation and Investment Policy - Far-From-Invisible Hand of Congress and Treasury
• Shaking Hands with Invisible Hand - Transitional Strategies for Global Social-Change - Questions and Issues
• Invisible Hand and Clenched Fist - Is There a Safe Way to Picket Under First Amendment
• Institutional Change and Quasi-Invisible Hand

And, finally:

• What's Wrong with Invisible-Hand Explanations?

For those that are curious as to I've been up to recently, you might be interested to read this portrait of Eric von Hippel on Linux.com. The article mentions that I'm currently studying with von Hippel in my own effort to try to help build a more evidence-based understanding of how free software works and explore some of the ways I might help it work better.

I've been a bit remiss about keeping this space up to date with my upcoming talks over the last month or so. Here's me playing catchup.

On Monday October 20th, I gave a talk on Selectricity for the IEEE Boston Section's Society on Social Implications of Technology. It covered more or less the same ground I coverd in my OSCON talk on the same subject. Then next day, Tuesday October 21st, I gave a short talk on Revealing Errors as part of the MIT-Harvard-Yale Cyberscholars meeting.

There was nothing new or ground-breaking in either but it was good to spread the word on the projects -- work continues on both.

I also have one more coming up: another Revealing Errors talk in Amherst, Massachusetts at my alma mater on October 31st (Halloween). If you are in Western Massachusetts and would like to meet up or attend the talk, let me know.

On the morning after the final US presidential debate that happened a week ago, I was invited onto the excellent new WNYC morning show The Takeaway -- syndicated by Public Radio International. One of the hosts, John Hockenberry, was in Boston to tape that edition of the show.

I was on to talk about Selectricity and some of other ways that we might use election technologies. I was on and off (mostly off) air for the whole second hour (7:00-8:00 AM) of taping and had a bit of a segment just into the second half of the hour. You can check out the website or download the podcast.

Although it's definitely not as fun to listen to as my a last gig on public radio, it's certainly more consequential. The role of the techno-pundit was also -- unfortunately? --- easier for me to fill.

It's late notice but Boston area folks should drop by the local Software Freedom Day events today. It goes from 10:00-16:00 and is located in a great space in Chinatown. More information in on the wiki.

I'm teaming up with John Sullivan of the FSF to talk about free software on in your pocket on unexecpted platforms. We'll show off CHDK (for cameras), the FreeRunner (a phone), and probably also talk about RockBox, iPodLinux, and more. It should be laid back and fun!

The whole point of SFD (and this SFD event in particular) is create a space that's appropriate to folks that don't already know about free and open source software and that aren't necessary technical. If you are a hacker or an advocate, show up and meet some like minded folks and introduce new people to the ideas that inspire you. If you are just curious about this stuff this event is designed for you.

If you're not in Boston, check the SFD webpage. There are hundreds of events around the world and may even be one near you!

It's been a year or so since I last reported what I was up to in my "day job." The last year has been a productive, if sometimes schizophrenic, period.

I've had a good time working with Eric von Hippel (innovation and free and open source software research guru) and have decided I'd like to do a bit more of that.

So I'm taking classes again -- mostly sociological methods courses -- to try to learn a bit about becoming a social scientist. To do so, I've enrolled in the Technology, Innovation and Entrepreneurship PhD program at the MIT Sloan School of Management and am working on putting together an interdisciplinary -- probably even interdepartmental -- research program. My basic research questions remain the ones that have motivated all my work: How can I get a better understanding of communities producing free stuff? How can I help those communities do so more effectively?

MIT has a large number of people who share these goals and interests. Who knows, if I can put together enough of them and an academically rigorous research proposal that will provide a real benefit to the free software and free culture communities I care about, I might even manage to get a degree out of it!

I'll also be staying on as a fellow at the MIT Center for Future Civic Media where I'll continue to maintain and expand Selectricity, work on Revealing Errors, and more.

Nearly a week after its release, I suspect most of my audience has seen the FSF's Freedom Fry video of Stephen Fry wishing the GNU project and the free software movement a happy birthday. While I'm not usually one for birthdays, I thought I'd at least reflect on it briefly. Certainly, it's a wonderful video -- for which Matt Lee at others at the FSF should be proud. But it's fact that the GNU project is now twenty-five years old that is truly noteworthy.

Wikipedia says that a generation (i.e., the average interval between the birth of parents and of their offspring) is somewhere between 25-30 years in most of the Western world. Twenty-five years isn't just a big number divisible by five, it marks a generational shift.

Certainly, GNU has matured and accomplished wonderful things in last quarter-century. More importantly perhaps, it's produced wonderful progeny. It has spawned hundreds of thousands of free software projects, thousands of free or nearly-free operating systems, and an unbelievably vibrant global free and open source software community. Beyond the software realm, the free culture movement, most free licensing projects, and much of the access to knowledge movement can trace a connection back to GNU. We are living, and building, a new generation of the free software movement.

It's not been an entirely smooth ride, feelings have been hurt, and it's hard for GNU's proponents -- myself included -- to not wince at some of what has been done in GNU's name and because of its example. But even cynics must admit: the world is an undeniably better place because of GNU and the efforts and ideas that it has motivated.

I turn 28 in December and have spent my entire computing life in world where free software was a viable option and an active form of resistance. Here's to another generation! May we be half as productive and positive as the last!

When my friends Karen and Annina were confronted with an offensive sticker on the laptop of someone working at our lab, they organized a very constructive and effective intervention.

I was so impressed that I made a short illustrated write-up of the story on my wiki.

I took a little time today to make a new release of the Free Software Project Management HOWTO. Nearly eight years after I wrote it, much of the document is out of date or has been replaced with better, more comprehensive write-ups. In particular, I think Karl Fogel's book, Producing Open Source Software says everything insightful I say in the HOWTO, a whole lot clearly -- plus adds a lot I missed.

That said, my HOWTO is short and is apparently still useful to folks. I updated it to include links to a new German translation courtesy to Robert F. Schmitt, to fix a bunch of links that time broke, and to address a few obvious mistakes that readers have pointed out.

Thinking about the documents' future, I'm happy to release it under Creative Commons BY-SA in addition to GFDL and would love to help out on a wiki book project to merge a few of related efforts into a comprehensive wiki reference work.

After a late-night IRC conversation about egg corns, shaggy dog stories and feghoots the idea for a short story came to me in the bathtub this morning.

I give you, The Story of Josephville. Apologies in advance.

I watched Citizen Kane several weeks ago and was shocked to learn that the major villian in the film is a political boss named Jim Gettys. Of course, a real Jim Gettys is a well known X Window System contributor who is currently working at an OLPC manager.

Last night someone reminded me that OLPC's new President and COO -- who I'd always just thought of as Chuck -- is named Charles Kane!

Here's a short clip from a video of the fictional Charles Kane giving a rather long speech decrying the fictional Jim Gettys! (Also in Ogg.)

I haven't been this amused since I learned that the head villian in the cartoon Jem was named Eric Raymond!

Nothing is more embarrassing than a website announcing that something will happen on a particular date -- e.g., a product will be released, a feature will be turned on -- after the date has come and gone! Even worse, putting things off repeatedly can be a lot of work!

To help such people, I just did a very quick 10 minute hack I'm calling The Vaporizer. It looks like just a date on a webpage. However, if the date originally listed has come and gone, a little bit of Javascript will change the site so that it shows tomorrow's date instead. Vaporware providers of all types can use it to safely (and effortlessly) put things off without worrying about looking overdue!

I have seen the future, and the future is tomorrow.

One thing that has always annoyed me about most wiki is the way they handle images. MediaWiki, like most wikis, allows users to upload images and embed pictures. However, if you want to change an image, you need to download the file, open it up in GIMP, Inkscape, or Photoshop, edit it, save it, and re-upload it. Somewhere in this long process, the ease of editing that makes wikis so wonderful gets lost. Basically, I'm annoyed because images in wikis aren't very "wiki."

I had a talk with Brianna Laugher at Wikimania about ways to make it easier to folks to edit pictures from within the browser -- even if it is only simple stuff. Yesterday I took the afternoon to write a new MediaWiki extension which gives a working example of in-browser image editing. It provides the ability to crop images using David Spurr's wonderful Javascript cropping user interface and uses ImageMagick to do the actual image manipulation.

It is in the form of an extension to Mediawiki I've called EditImage. It's an afternoon hack from an under-qualified PHP hacker so it's nothing special. You can read it about on its page in the Mediawiki wiki and you can try it out on my personal wiki where I have it installed.

I'm certainly not the first person to think about doing this. In fact, some old pages in the MediaWiki wiki imply that I'm not even the first person to play around with the idea of using Spurr's code to do image cropping for MediaWiki. Hopefully though, my code can act as a nice first step and a framework for folks wanting to add additional image manipulation features. For example, I think it would be quick to add the ability to do in-browser brightness and contrast manipulation and I would love to see this in a future version of the extension.

When I gave a Revealing Errors talk at Lug Radio Live USA, I had the misfortune of being up against Robert Love's talk on Android which many people at the conference wanted to see -- myself included! One person who showed up to my talk anyway was Allison Randall. She was apparently entertained enough to invite me to give a short version of the talk as one of the keynote presentations at OSCON 2008!

In the talk, I covered the ideas behind my Revealing Errors project and quickly walked through a few examples that showcase what I'm trying to do. I'm happy with the result: a couple thousand people showed up for the talk despite the fact that it was at 8:45 AM after the biggest "party night" of the conference!

For those that missed it for whatever reason, you can watch a video recording that O'Reilly made and that I've embedded below.

A larger version of the Flash video as well as a QuickTime version is over on blip.tv and I've created an OGG Theora version for all my freedom loving readers.

I'm in Portland, Oregon for the week where I'll be at OSCON. I'll be giving two talks on the final day of the conference (July 25): the first will be a 15 minute keynote on Revealing Errors at 8:45 in the Portland Ballroom; the second is a full-length normal talk on Selectricity at 11:35AM in Portland 255. It will be my first long-form talk about Selectricity and I'm looking forward to it.

Because myself, a few Free Software Foundation staff members including Campaign Manager Joshua Gay, and quite a few FSF associate members will be in town, we're going to hold a small FSF Associate Members event in Portland (the first outside Boston!). It's going to be in the form of a pizza party with a few small talks from FSF folk including myself. Here are the details:

FSF Associate Members (& friends!) Event

July 22nd 6:30-9:00PM

Old Town Pizza

226 NW Davis St

Portland, OR 97209

It's free and open to all but is designed to provide a forum for members and friends. If you are an FSF member, please consider coming. If you're not a member yet, please don't let it keep you away; staff will be able to sign up new members there. RSVPs to Deborah Nicholson aren't necessary to attend but would be welcome.

I'll be heading to Seattle right after the conference for a few days. If you would like to meet up in Seattle or Portland this week, please don't hesitate to get in contact.

Once again, Wikimania was wonderful. I gave my scheduled talk on Autonomo.us and network freedom and network services. I also filled in for a few speakers to give a "Zotero for Wikipedians" demo and to say a few words about the BY-SA/FDL work as part of a Creative Commons panel.

Perhaps the most memorable part of the conference was the writing and performance of I Will Revise. A couple days before the conference, a small group of Wikipedians -- The Difftones -- wrote the song at a karaoke bar in Alexandria. We had a wonderful time leading a room full of lightning talk attendees in song and a final rendition by a massive, fully-packed, stage at the party on the final night!

It's online on meta.wikimedia.org. You should feel free to revise it, add verses, and improve it!

At the hotel I'm staying at in Alexandria for Wikimania, there is wifi from a closed network that requires login and that has no user-accessible way to gain increased access.

However, they have defined a set of "exceptions" to their closed network policy. The exceptions are described on the page users are redirected to upon connecting. Essentially, the exceptions boil down to any website that ends in google.com.

You can use Google search (but not click on the links), use GMail, Google Talk, Google Reader (but not see any images on the blogs you are reading), Google Calendar, Google Maps, Google Checkout, Google Docs, and so on.

A few people at the conference seem only barely inconvenienced by the arrangement and most seem to be able to get work done! I can't help feel like I'm experiencing some dystopian version of the Internet from 10 years in the future.

Recently, I've been doing a lot of thinking -- and a bit of talking -- about what software freedom means in the context of network services. I gave a talk on this subject at the most recent FSF members meeting and at Sun's Community One. In a few days, I'll be giving another at Wikimania in Alexandria, Egypt.

A few months ago, I worked with the FSF to organize a meeting of free software hackers and scholars to talk about the issues. Today, that group is announcing the first two concrete results of that project.

The first is a blog and a wiki called autonomo.us. The project aims to provide a space to continue, expand, and open up the work that was done at the FSF in March. Our aim is to explore the implications and responses to network services in relation to software. We're going to do that by continuing to take notes in the wiki and by publishing articles, essays, and documents that help inform the discussion about software freedom and network policies. We will be working independently from, but closely with, the Free Software Foundation, and with others in the free and open source software communities. Our goal is not to set policy, but to explore the space and inform the discussion about autonomy and user freedom in cloud computing and software as a service.

The second announcement is the first concrete product of autonomo.us's work: a statement we're calling the Franklin Street Statement on Freedom and Network Services. It lays out our initial consensus on positive steps that developers, service providers, and users can take.

If you want to follow our work, please subscribe to the autonomo.us blog and check out some of our work so far. If you've got thoughts and things to contribute, you can mail or get to work in our wiki. You can read our about page for more information about us and our goals.

In a coordinated move, the Open Knowledge Foundation (which I help advise) is launching the 1.0 version of their Open Software Service Definition.

There is a whole lot we need to learn, think through, and do before we have reasonable answers to the problems to freedom posed by network services. Today marks the beginning of several wonderful steps toward some of these answers.

My friend Aaron is moving back to Boston and in the process getting stuff for his apartment from Ikea. A lot of Ikea stuff is secured with hard plastic strapping. Luckily, Ikea also sells scissors to help you cut your way through it! The scissors are secured with hard plastic strapping.

I've always been bothered by those "Property Of Blank University" t-shirts that used to actually be the loaned (or stolen) property of college athletic departments but have now become popular enough that you can find them, for sale, in nearly any university store or gift shop in the US. Few people would assume that somebody with a "Property of" shirt had stolen their clothing. In fact, it's often impossible to find the shirts except on sale anymore -- and rarely from universities themselves.

Here's my response.

For those that don't know (and that's certainly many), Pierre-Joseph Proudhon is the nineteenth century French anarchist and mutualist most famous for saying, "La propriété, c'est le vol!" In English: "Property is theft!"

You can buy my t-shifts (red on black, where possible), in my Printfection store. Source SVG is here. Please share variations in a comment.

Another year has past and another edition of the Official Ubuntu Book has been finished and will be released soon. Over the last two years, the two previous editions of the book have grown along-side Ubuntu. The book has continued to sell very well, received almost universally favorable reviews, and been translated into more than half a dozen languages

While Jono Bacon has mostly been pulled into other projects, Corey Burger stepped up to help play the major supporting role in this version of the book's production. The whole text was updated to reflect changes in Ubuntu over the last year including a major rewrite of the chapter on Kubuntu and important work on the Edubuntu chapter. If you use either, you'll understand that there's plenty of churn to report.

In a sort of experiment, Barnes and Noble will also be selling a custom edition with an extra chapter by Matthew Helmke on the Ubuntu Forums which I hope to include in the next edition of the book. It's an excellent introduction to the best support resource Ubuntu has to offer that I hope many beginners -- the group that always been the book's audience -- will find useful.

You can pre-order the custom edition from B&N or get the book from Amazon or many other sources.

Like all previous editions, the book is licensed under the Creative Commons Attribution ShareAlike license and soft-copies should be up on the publisher's website once the book is released. Please support commercial free culture publishing by buying a copy if you find the book useful.

As I mentioned a couple weeks ago, I'm giving a talk about my Revealing Errors project tonight at the Boston Linux Unix meeting. It will be at MIT in E51-351. More information is on the BLU website.

Revealings Errors is a very different kind of project from what I've done. Please show up if you can. I'd love support, feedback, suggestions, and the like.