Punditry

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.

What I’m Up To

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.

Free Software Project Management HOWTO

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.

Vaporizer

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.

Making Wiki Images More Wiki

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.

Revealing Errors OSCON Keynote

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.

Autonomo.us and the Franklin Street Statement

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.

Ubuntu Book Third Edition

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.

Unhappy Birthday Interview

Unhappy Birthday — a website that tries to educate the public and encourage folks to snitch on their friends for singing the (copyrighted!) Happy Birthday song in public places — is perhaps the most widely read thing I’ve ever written. It’s been seen by millions and I continue to get hate mail several times a week.

Last Sunday, the nationally broadcast CBC show WireTap aired an pseudonymous in-character interview with me about the site where I pretended to be a copyright high-protectionist. I think it turned out pretty well.

You can listen to it on the unofficial WireTap podcast. My interview starts at a bit more than 10 minutes into the show.

Still Seeing Yellow

Recently, the EFF reported that the European commission had responded to a request by European Parliament member Satu Hassi about tracking dots in printers. European Commissioner Franco Frattini replied that tracking dots may constitute a human rights violation saying that:

"..to the extent that individuals may be identified through material printed or copied using certain equipment, such processing may give rise to the violation of fundamental human rights, namely the right to privacy and private life. It also might violate the right to protection of personal data."

Intriguingly, the request text includes a mention to and link to the Seeing Yellow project I started last year as an example of the fact that consumers have complained to printer manufacturers and that these complaints have fallen upon deaf ears.

Everyone who called their printer manufacturer in response to Seeing Yellow deserves come credit for the raised visibility to the issue that we’ve created and the set of actions that have brought the issue this far. Please, keep it up! If you’ve not complained to your printer manufacturer, visit Seeing Yellow and call today.

Creative Commons and the Freedom Definition

Creative Common Seal for Free Cultural Works

Yesterday witnessed the most important step forward for the Definition of Free Cultural Works (DFCW) since its adoption and endorsement by the Wikimedia Foundation a year ago.

Although I might have wished things otherwise, Creative Commons is not a social movement fighting for essential freedom or the essential freedoms at the core of the DFCW in particular. From the movement’s perspective, CC is more like a law and advocacy firm that works for us — a very sympathetic one. CC writes, hosts, and supports a variety of licenses. Some are free. Some are not. Last year they took steps to explicitly limit the extent of restrictions they are willing to tolerate in their licenses.

Yet, while CC has resisted taking a stand in favor of the Definition of Free Cultural Works, they continue to produce some of the best free licenses, tools, and metadata available and they seem honestly interested in helping users interested in social movements based around these definitions organize more effectively.

In perhaps its most important move to date in this area, Creative Commons announced yesterday that it was placing a seal on each of its licenses that provide the essential freedoms laid out in the Definition of Free Cultural Works. The seal links to the definition over at freedomdefined.org. In Creative Commons’ words:

This seal and approval signals an important delineation between less and more restrictive licenses, one that creators and users of content should be aware of.

A very practical reason users should be aware of these distinctions is that some important projects accept only freely (as defined) licensed or public domain content, in particular Wikipedia and Wikimedia sites, which use the Definition of Free Cultural Works in their licensing guidelines.

The seal is currently on two CC licenses that provide for essential freedom (Attribution and Attribution-ShareAlike) and their public domain dedication. Thanks go to Erik Moeller at the Wikimedia Foundation and everyone at Creative Commons to helped make this happen.

Free Culture Elections

Recently, Students for Free Culture — a non-profit organization dear to my heart — elected its new board. Several months ago, the group voted to hold its elections using the same preferential election method system that Debian uses. To help make their election easier I agreed to support them with a new set of features in Selectricity aimed at more structured organizational decision-making. Currently Selectricity is more geared toward more informal QuickVotes.

From a democratic and voting technology perspective, the election was a huge success. With 16 voters and 13 candidates, a traditional plurality or "first past the post" election would have been a poor match for their group — the 16 first-place votes were very split among the candidates. The results also show one very polarizing candidate who won the plurality but was in the bottom third of most preferential rankings! The use of Selectricity helped SFC select a board who better represented the preference of their group than they would have otherwise. Exciting stuff! You can read more on the Free Culture website or on the Selectricity blog.

Thanks are due both to the previous SFC board who took the risk on the technology and to all of the candidates and voters! I’m currently integrating feedback and improvements based on the SFC election and will open the feature up the public in the next couple weeks. If you want hear about this when it happens, you should subscribe to the Selectricity Blog or drop an email to team@selectricity.org.

Revealing Errors

Groups that campaign for free technology, like the Free Software Foundation and the Electronic Frontier Foundation, tend to be supported primarily by technologists. Both groups have struggled to communicate their messages to non-geeks. I have written an article and helped create a new weblog, both called Revealing Errors, that attempt to address a root cause of this issue in what I hope is both an insightful and entertainingly manner.

Geeks support groups like the FSF and EFF because, as people who understand technology, they understand just how powerful technology is. Geeks know that control of our communication technologies is control over what we can say, who we can say it to, and how and when we can say it. In an increasingly technologically mediated age, control over technology is not only the power to control our actions; it is the power to limit our possible actions. Our freedom to our technology is our freedom, full stop.

This message fails to resonate with non-geeks but it does not fail because non-geeks are happy to hand over their freedom. It fails to resonate simply because the vast majority of people do not understand that technology, and control over it, is powerful enough to impact their freedom. Most people fail to see the power because, quite simply, most people fail to see technology. While we all see the effects of technologies, the technologies themselves are frequently hidden. We see emails but not mail transport agents. We see text messages but not the mobile phone network. Before one can argue that such systems must be free, one must reveal their existence. Technologists are keenly aware of the existence of these systems. To everyone else, they are completely invisible.

Marc Weisner of Xerox PARC cited eyeglasses as an ideal technology because, with spectacles, "you look at the world, not the eyeglasses." When technology works smoothly, its nature and effects are invisible. But technologies do not always work smoothly. A tiny fracture or a smudge on a lens renders glasses quite visible to the wearer indeed. Similarly, people see their MTAs when messages bounce. They see Windows on their ATM or phone when the system crashes. Technological errors are moments when usually invisible technology becomes visible. They are, in this sense, also an educational opportunity.

/copyrighteous/images/blue_screen.jpg

I have recently published an article in Media/Culture Journal from the University of Melbourne within a special issue called Error. If you are interested in learning more about what I’m trying to do or looking at some examples, please read the article.

With support and ontributions from Aaron Swartz, I have also created a new weblog, Revealing Errors, that reveals errors that reveal technology by posting descriptions of errors with commentary on what the error reveals. I’ve posted a few examples there already and I will be updating it regularly. The goal is to help explain the power and influence of technology in the service of broadening the base of people who can get excited about freedom to technology.

Eventually, I hope to be able to communicate this message to a less technical audience. With that said, I hope that even seasoned technologists will learn things about their technological environment through the analysis and interaction. I hope readers of this blog will subscribe to it and, if possible, comment on and contribute to the project as it moves forward.