Photo: Flickr user lifeontheedge

Saturday, September 23, 2006

Erik Möller won the board election. (He's supremely qualified and seems like a good guy.)

Friday, September 22, 2006

Lawrence Lessig's wikimania keynote was about making sure free culture wasn't divided into isolated islands. To that end, FlickrLickr grabs free-licenced Flickr photos for use on wikimedia projects.

Thursday, September 21, 2006

The Tree of Ténéré was a solitary acacia that was once considered the most isolated tree on Earth — the only one within more than 400 km. It was knocked down by an allegedly drunk Libyan truck driver in 1973. On November 8, 1973 the dead tree was relocated to the Niger National Museum in the capital Niamey. It has been replaced by a simple metal sculpture representing a tree.

List of famous trees

Pedia bills itself as a wikipedia client for mac, but it's really just a stripped-down web browser, not even as full-featured as Gollum. (It's free-licenced, so it'll improve. Maybe I'll finish learning Cocoa and do it myself.)

Clay Shirky on why Citizendium won't work. I'm inclined to think these problems might be solvable (not least because Citizendium content can be recycled to wikipedia -- Citizendium just needs to be a tide pool, a set of nooks and crannies where an alternate rulebook elides problems that crop up in some corners of wikipedia), but the snippiness of Sanger's response is a bit concerning.

Monday, September 18, 2006

Wikipedia blog endorses Aaron Swartz. Check out his essays, and go vote for him in the Wikimedia board elections (which end in a couple days).

From Code, and Other Laws of Wikipedia:

The page design the site uses encourages specific actions by making some links clear and prominent. Software functions like categories make certain kinds of features possible. The formatting codes used for things like infoboxes and links determine how easy it is for newcomers to edit those pieces of the site.

All of these things are political choices, not technical ones. It's not like there's a right answer that's obvious to any intelligent programmer. And these choices can have huge effects on the community. That's why it's essential the community be involved in making these decisions.

The current team of Wikipedia programmers is a volunteer group (although a couple of them were recently hired by the Wikimedia Foundation so they could live a little more comfortably) working much like a standard free software community, discussing things on mailing lists and IRC channels. They got together in person in the days before Wikimania to discuss some of the current hot topics in the software.

One presentation was by a usability expert who told us about a study done on how hard people found it to add a photo to a Wikipedia page. The discussion after the presentation turned into a debate over whether Wikipedia should be easy to to use. Some suggested that confused users should just add their contributions in the wrong way and a more experienced users would come along to clean their contributions up. Others questioned whether confused users should be allowed to edit the site at all -- were their contributions even valuable?

As a programmer, I have a great deal of respect for the members of my trade. But with all due respect, are these really decisions that the programmers should be making?

Meanwhile, Jimbo Wales also has a for-profit company, Wikia, which recently received $4 million in venture capital funding. Wales has said, including in his keynote speech at Wikimania, that one of the things he hopes to spend it on is hiring programmers to improve the Wikipedia software.

This is the kind of thing that seems like a thoughtful gesture if you think of the software as neutral -- after all, improvements are improvements -- but becomes rather more problematic if technical choices have political effects. Should executives and venture capitalists be calling the shots on some of these issues?

The Wikipedia community is enormously vibrant and I have no doubt that the site will manage to survive many software changes. But if we're concerned about more than mere survival, about how to make Wikipedia the best that it can be, we need to start thinking about software design as much as we think about the rest of our policy choices.


From Making more Wikipedias:

Wikipedia's real innovation was much more than simply starting a community to build an encyclopedia or using wiki software to do it. Wikipedia's real innovation was the idea of radical collaboration. Instead of having a small group of people work together, it invited the entire world to take part. Instead of assigning tasks, it let anyone work on whatever they wanted, whenever they felt like it. Instead of having someone be in charge, it let people sort things out for themselves. And yet it did all this towards creating a very specific product.

Even now, it's hard to think of anything else quite like it. Books have been co-authored, but usually only by two people. Large groups have written encyclopedias, but usually only by being assigned tasks. Software has been written by communities, but typically someone is in charge.

But if we take this definition, rather than wiki software, as the core of Wikipedia, then we see that other types of software are also forms of radical collaboration. Reddit, for example, is radical collaboration to build a news site: anyone can add or edit, nobody is in charge, and yet an interesting news site results. Freed from the notion that Wikipedia is simply about wiki software, one can even imagine new kinds of sites. What about a "debate wiki", where people argue about a question, but the outcome is a carefully-constructed discussion for others to read later, rather than a morass of bickering messages.

If we take radical collaboration as our core, then it becomes clear that extending Wikipedia's success doesn't simply mean installing more copies of wiki software for different tasks. It means figuring out the key principles that make radical collaboration work. What kinds of projects is it good for? How do you get them started? How do you keep them growing? What rules do you put in place? What software do you use?

These questions can't be answered from the armchair, of course. They require experimentation and study. And that, in turn, requires building a community around strong collaboration itself. It doesn't help us much if each person goes off and tries to start a wiki on their own. To learn what works and what doesn't, we need to share our experiences and be willing to test new things -- new goals, new social structures, new software.

Buffalo buffalo Buffalo buffalo buffalo buffalo Buffalo buffalo. (See also)

Saturday, September 16, 2006

Omnipelagos is like 6 degrees of wikipedia but much better. (You can actaully play 6 degrees of Kevin Bacon with it.)

"...if you want to have authority on the Web, you have to show up on the Web. And those who ought to enjoy more authority than Wikipedia aren’t. Let me make the point by example

...

Cast your eyes back across those web addresses. What are your chances of guessing them? Of remembering them? Of writing them down accurately? If you bookmark them, how confident are you that they’ll be there after the next site re-org?

So if the public-sector community decided to standardize their URIs, or adopt a principle that every front page should have a FAQ link, or make some sort of concerted intelligent attempt to show up on the Web, they might grab some authority back. But they’re not. And I don’t see any signs of interest.

So Wikipedia is going to win. Do you see any other plausible outcome?"

Thursday, September 14, 2006

Monday, September 11, 2006

Wikipedia is Written by the Public has a correllary: Process is Dangerous.

In physics, Planck units are physical units of measurement defined exclusively in terms of five universal physical constants, in such a manner that all of these physical constants take on the numerical value of one when expressed in terms of these units. Planck units elegantly simplify particular algebraic expressions appearing in physical law.

Jimmy: 'One of the points that I'm trying to push is that if there's a small town in China that has a wonderful local tradition, that won't make its way into Wikipedia because the people of China are not allowed to share their knowledge with the world. I think that's an ironic side-effect and something the people in the censorship department need to have a much bigger awareness of: you're not just preventing information about Falun Gong or whatever you're upset about getting into China, you're preventing the Chinese people speaking to the world.'

Sunday, September 10, 2006

Interesting blog post.

Then there's a distinct second group of people who argue fiercely against what they perceive as 'mob rule'; people who can't fathom the thought of open, participatory systems that actually work. Typically these are people from Academia or political institutions, both of which are groups that are deeply characterized by their thresholds of entry. (I'm not joking here. That's anecdotal evidence, true, but happened too often to be a coincidence.)

And these are the people we need to have discussions with. Because they're the gateways to making changes on a large scale, to changing the system from within. If we can't persuade them we at least must [reduce] their fear of these systems. We must demonstrate that what we're proposing is not Anarchy.

Tuesday, September 05, 2006

Wikipedia really is written by the public -- if this tremendously important bit of research is independently confirmed, it upsets conventional thinking.

Wales seems to think that the vast majority of users are just doing the first two (vandalizing or contributing small fixes) while the core group of Wikipedians writes the actual bulk of the article. But that's not at all what I found. Almost every time I saw a substantive edit, I found the user who had contributed it was not an active user of the site. They generally had made less than 50 edits (typically around 10), usually on related pages. Most never even bothered to create an account.

To investigate more formally, I purchased some time on a computer cluster and downloaded a copy of the Wikipedia archives. I wrote a little program to go through each edit and count how much of it remained in the latest version. Instead of counting edits, as Wales did, I counted the number of letters a user actually contributed to the present article.

If you just count edits, it appears the biggest contributors to the Alan Alda article (7 of the top 10) are registered users who (all but 2) have made thousands of edits to the site. Indeed, #4 has made over 7,000 edits while #7 has over 25,000. In other words, if you use Wales's methods, you get Wales's results: most of the content seems to be written by heavy editors.

But when you count letters, the picture dramatically changes: few of the contributors (2 out of the top 10) are even registered and most (6 out of the top 10) have made less than 25 edits to the entire site. In fact, #9 has made exactly one edit -- this one! With the more reasonable metric -- indeed, the one Wales himself said he planned to use in the next revision of his study -- the result completely reverses.

I don't have the resources to run this calculation across all of Wikipedia (there are over 60 billion edits!), but I ran it on several more randomly-selected articles and the results were much the same. For example, the largest portion of the Anaconda article was written by a user who only made 2 edits to it (and only 100 on the entire site). By contrast, the largest number of edits were made by a user who appears to have contributed no text to the final article (the edits were all deleting things and moving things around).

When you put it all together, the story become clear: an outsider makes one edit to add a chunk of information, then insiders make several edits tweaking and reformatting it. In addition, insiders rack up thousands of edits doing things like changing the name of a category across the entire site -- the kind of thing only insiders deeply care about. As a result, insiders account for the vast majority of the edits. But it's the outsiders who provide nearly all of the content.

And when you think about it, this makes perfect sense. Writing an encyclopedia is hard. To do anywhere near a decent job, you have to know a great deal of information about an incredibly wide variety of subjects. Writing so much text is difficult, but doing all the background research seems impossible.

On the other hand, everyone has a bunch of obscure things that, for one reason or another, they've come to know well. So they share them, clicking the edit link and adding a paragraph or two to Wikipedia. At the same time, a small number of people have become particularly involved in Wikipedia itself, learning its policies and special syntax, and spending their time tweaking the contributions of everybody else.

Other encyclopedias work similarly, just on a much smaller scale: a large group of people write articles on topics they know well, while a small staff formats them into a single work. This second group is clearly very important -- it's thanks to them encyclopedias have a consistent look and tone -- but it's a severe exaggeration to say that they wrote the encyclopedia. One imagines the people running Britannica worry more about their contributors than their formatters.

And Wikipedia should too. Even if all the formatters quit the project tomorrow, Wikipedia would still be immensely valuable. For the most part, people read Wikipedia because it has the information they need, not because it has a consistent look. It certainly wouldn't be as nice without one, but the people who (like me) care about such things would probably step up to take the place of those who had left. The formatters aid the contributors, not the other way around.

Sunday, September 03, 2006

Flickr's added geotagging and there are already millions of photos on the map. 2 thoughts spring immediately to mind:

1. Someone needs to mash this up with Wikimapia. (It can be done; there's an API.)

2. The hill ahead of Digital Universe keeps getting steeper.