The Boy Who Could Change the World (6 page)

Making More Wikipedians

http://www.aaronsw.com/weblog/morewikipedians

September 11, 2006

Age 19

Wikipedia, the vice president of the
World Book
told us, is now recognized by ten percent of Americans. He presented this in a tone of congratulation: with no marketing budget or formal organization, a free online-only encyclopedia written by volunteers had achieved a vast amount of attention. But I took it a different way. “Only ten percent?” I thought. “That means we have ninety percent to go!”

Wikipedia is one of the few things that pretty much everyone finds useful. So how do we get all of them to use it? The first task, it appears, is telling them it exists. An ad campaign or PR blitz doesn't quite seem appropriate for the job, though. Instead, our promotion should work the same way the rest of Wikipedia works: let the community do it.

Wikipedia's users come from all over society: different cultures, different countries, different places, different fields of study. The physics grad students who contribute heavily to physics articles are in a much better position to promote it to physicists than a promotional flack from the head office. The Pokemon fan maintaining the Pokemon articles probably knows how to reach other Pokemaniacs [better] than any marketing expert.

Sure, you might say, but isn't the whole question of marketing Wikipedia somewhat silly? After all, you obviously know about Wikipedia, and your friends probably all seem to as well. But things are a lot thinner than you might expect: as noted above, only one in ten Americans even knows what Wikipedia is, and most of those don't truly understand it.

It's shocking to discover how even smart, technically minded people can't figure out how to actually edit Wikipedia. Dave Winer wrote some of the first software to have an “Edit This Page” button (indeed, he operated
EditThisPage.com
for many years) and yet he at first complained that he couldn't figure out how to edit a page on Wikipedia. Michael Arrington reviews advanced Web 2.0 websites daily, yet
he noted
that “many people don't realize how easy it is for anyone to add content to Wikipedia (I've done it several times).” If prominent technologists have trouble, imagine the rest of the world.

Obviously, this has implications for the software side: we need to work hard on making Wikipedia's interface clearer and more usable. But there's also a task here for the community: giving talks and tutorials to groups that you know about, explaining the core ideas behind Wikipedia, and giving demonstrations of how to get involved in it. The best interface in the world is no substitute for real instruction, and even the clearest document explaining our principles will be ignored in a way that a personal presentation won't.

But beyond simply giving people the ability to contribute, we need to work to make contributing more rewarding.
As I previously noted
, many people decide to dive into writing for Wikipedia, only to watch their contributions be summarily reverted. Many people create a new article, only to see it get deleted after an AfD discussion where random Wikipedians try to think up negative things to say about it. For someone who thought they were donating their time to help the project, neither response is particularly encouraging.

I'm not saying that we should change our policies or automatically keep everything a newcomer decides to add so we don't hurt their feelings. But we do need to think more about how to enforce policies without turning valuable newcomers away, how we can educate them instead of alienating them.

At Wikimania, no less an authority than Richard Stallman (who himself long ago
suggested the idea
of a free online encyclopedia) wandered around the conference complaining about a problem he'd discovered with a particular Wikipedia article. He could try to fix it himself, he noted, but it would take an enormous amount of his time and the word would probably just get reverted. He's not the only one—I constantly hear tales from experts about problems they en
counter on Wikipedia, but [which] are too complicated for them to fix alone. What if we could collect these complaints on the site, instead of having these people make them at parties?

One way to do that would be to have some sort of complaint-tracking system for articles, like the discussion system of talk pages. Instead of simply complaining about an article in public, Stallman could follow a link from it to file a complaint. The complaint would be tracked and stored with the article. More dedicated Wikipedians would go through the list of complaints, trying to address them and letting the submitter know when they were done. Things like POV allegations could be handled in a similar way: a notice saying neutrality was disputed could appear on the top of the page until the complaint was properly closed.

This is just one idea, of course, but it's an example of the kinds of things we need to think about. Wikipedia is visited by millions each day; how do get them to contribute back their thoughts on the article instead of muttering them under their breath or airing them to their friends?

Making More Wikipedias

http://www.aaronsw.com/weblog/morewikipedias

September 14, 2006

Age 19

Maybe it's just me, but it seems like everywhere you look people are trying to get a piece of Wikipedia. Wiki sites have been started in every field from
the Muppets
to
the law
. The domain
Wiki.com
recently was
sold for 3 million dollars
. Professor Cass Sunstein,
previously seen
arguing the Internet could tear apart the republic, just published
a new book
arguing tools like wikis will lead us to “Infotopia.” So is it possible to replicate Wikipedia's success? What's the key that made it work?

Unfortunately, this question hasn't gotten the attention it deserves. For the most part, people have simply assumed that Wikipedia is as simple as the name suggests: install some wiki software, say that it's for writing an encyclopedia, and
voila!
—problem solved. But as pretty much everyone who has tried has discovered, it isn't as simple as that.

Technology industry people tend to reduce websites down to their technology:
Wikipedia
is simply an instance of wiki software,
DailyKos
just blog software, and
Reddit
just voting software. But these sites aren't just installations of software, they're also communities of people.

Building a community is pretty tough; it requires just the right combination of technology and rules and people. And while it's been clear that communities are at the core of many of the most interesting things on the Internet, we're still at the very early stages of understanding what it is that makes them work.

But Wikipedia isn't even a typical community. Usually Internet
communities are groups of people who come together to discuss something, like cryptography or the writing of a technical specification. Perhaps they meet in an IRC channel, a web forum, a newsgroup, or on a mailing list, but the focus is always something “out there,” something outside the discussion itself.

But with Wikipedia, the goal is building Wikipedia. It's not a community set up to make some other thing, it's a community set up to make itself. And since Wikipedia was one of the first sites to do it, we know hardly anything about building communities like that.

Indeed, we know hardly anything about building software for that. Wiki software has been around for years—the first wiki was launched in 1995; Wikipedia wasn't started until 2001—but it was always used like any other community, for discussing something else. It wasn't generally used for building wikis in themselves; indeed, it wasn't very good at doing that.

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.

Code, and Other Laws of Wikipedia

http://www.aaronsw.com/weblog/wikicodeislaw

September 18, 2006

Age 19

Code is law, Lawrence Lessig famously said years ago, and time has not robbed the idea of any of its force. The point, so eloquently defended in his book
Code, and Other Laws of Cyberspace
, is that in the worlds created by software, the design of the software regulates behavior just as strongly as any formal law does; more effectively, in fact.

The point is obvious in some contexts. In the online 3-D universe of Second Life, if the software prevents you from typing a certain word, that's a far more effective restraint on speech in that world than any U.S. law could ever be in ours. But the point is far more subtle than that; it applies with equal force to the world of Wikipedia, the thriving community and culture that our wiki software creates.

For one thing, the software decides who gets to be part of the community. If using it is clear and simple, then lots of people can use it. But if it's complicated, then only those who take the time to learn it are able to take part. And, as we've seen, lots of intelligent people don't even understand how to edit Wikipedia, let alone do any of the other things on the site.

For another, the software decides how the community operates. Features like administrative controls privilege some users over others. Support for things like stable revisions decides what sorts of things get published. The structure of talk pages helps decide what and how things get discussed.

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 info boxes 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 use. Some suggested that confused users should just add their contributions in the wrong way and 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.