WikiWednesday in San Francisco: State of the Wiki Ecosystem

Stephen LaPorte and I are hosting an informal discussion in San Francisco on Wednesday, October 2, 2013 on the state of the wiki universe. We’re hoping to get a group of people actively working in the wiki world as well as “old timers” in the community (you know who you are, and we want to see you there) and people who simply love wikis to come together to discuss the following questions:

  • What’s happening right now?
  • What’s changed?
  • What’s the future that we’d like to see?

It will be held at the Wikimedia Foundation (149 New Montgomery Street, 3rd Floor, San Francisco) from 6:30-9pm.

In the spirit of wikis, it will be an open and participatory gathering, and we’re expecting interesting people to attend. We’ll pull together funds to order pizza and drinks.

Please feel free to spread the word and bring guests. Just be sure to RSVP in the comments below so that we know how many to expect.

Wiki Developer Meeting Today; WikiWednesday Tomorrow

Two important events are happening in Wiki-land today and tomorrow. First, this afternoon at 2pm PDT (21:00 GMT), there will be a worldwide IRC meeting for Wiki developers on #wikiohana at irc.freenode.net. The main agenda item: WikiCreole. This was one of the outcomes from RecentChangesCamp last month. The cool thing is that folks have been hanging out regularly on the channel, and that Andreas Gohr whipped up an IRC logger for us. If you do any Wiki development, please join us!    (MBM)

Tomorrow night, WikiWednesday will be moving to Citizen Space in San Francisco, and I’ll be the inaugural speaker at the first non-Palo Alto event. I’ll be talking about my recent work on Wiki Interoperability:    (MBN)

Market growth is healthy for everyone in the Wiki world. More Wiki companies and technology means greater market awareness and innovation. But Wikis are also about community and collaboration. Are we as a community collaborating as much as we could? Are there opportunities we’re missing by not collaborating more? Eugene Eric Kim will preview his upcoming paper on Wiki interoperability, where he describes real-world end-user pain, concrete opportunities (especially ways Wiki developers can help the entire space by improving their own tools), and a practical strategy (WikiOhana) for achieving interoperability.    (MBO)

Hope to see many of you there!    (MBP)

pageoftext.com

Gordon McCreight showed off his latest silly creation, pageoftext.com, at the last WikiWednesday. It’s a silly concept, and it’s got a silly lack of features. What’s really silly is how useful this silly little concept is. It’s considerably simpler than Writeboard, slightly more featureful than the various Pastebins, and better than both.    (M4D)

pageoftext.com is a collaborative text editor on laxatives. All features you might think you need have been flushed away to oblivion. There’s no formatting, no registration, and no security. Editing happens in plain text. The URLs are human-friendly, which is good, because you’ll need to remember them if you ever want to find them again. Gordon does have a remind feature, in which you describe what’s on the page, and then he tries to find it for you.    (M4E)

It’s great for when a bunch of people — especially normal people — need to edit a file together quickly and easily. You don’t have to go through the normal hullabaloo of logging in, because you don’t have to login. You don’t have to describe the markup, because there is no markup. It’s totally task-focused.    (M4F)

This, in theory, is what Writeboard was supposed to be, except I think it’s a whole lot better. When I use Writeboard, I’m constantly reminded of what it’s not, as opposed to being excited over what it is. Writeboards are no easier than a Wiki to use, but they’re much less useful.    (M4G)

I love pastebin (known as nopaste in some circles) for a lot of reasons. Pastebin emerged because developers collaborating on IRC needed a Shared Display. It’s brain-dead simple, and it does exactly what it’s supposed to do. pageoftext.com addresses a different goal than pastebin, but it has similar affordances, and could be used the same way.    (M4H)

Gordon has been militant about feature creep, which is a good thing. That said, I started a page suggesting new features. Feel free to add those there. Or, if you prefer not to think about such esoteric things, you can add some Philadelphia-area restaurants and reviews to my Philly restaurants page. (I’m visiting Philly for the first time next weekend, and I need some good cheesesteak recommendations.)    (M4I)

March Conferences

This weekend, we’re having our fourth FLOSS Usability Sprint, once again sponsored by the good folks at Google. Participating projects will include Mozilla, WiserEarth, Social Source Commons, and Drupal! It should be a fantastic event, and we still have some slots for usability folks, so if you’d like to participate, please apply by the end of the day today.    (LYO)

Tonight is another installment of WikiWednesday at Socialtext‘s offices in Palo Alto. Bryan Pendleton of Xerox PARC will be discussing his research on conflict resolution and coordination on Wikipedia. I had a chance to talk briefly with him about his work last month, and his talk should be absolutely fascinating.    (LYP)

Finally, there’s going to be an unprecedented gathering of folks in the facilitation, Organizational Design, and collaboration community on March 21-23 called Nexus for Change. It will be held at Bowling Green State University in Bowling Green, Ohio (near Detroit). If you’re interested in catalyzing transformation in your organization and in society via collaboration, this is the place to be. I am tremendously bummed that I’m going to have to miss it. I did everything I could to rearrange my schedule, and it just wasn’t to be. Many of my colleagues and friends will be there, as well as some of the deepest thinkers and practitioners in the business. I highly recommend it to everyone, but I’d like to make a special pitch to those of you in the Collaborative Tools business to attend. Should be a tremendous event.    (LYQ)

Folksonomy Taxonomy Philosophy

I love playing The Book of Questions types of games with friends and colleagues, but when it comes to answering those types of questions myself, I’m a terrible waffler. When I play these games with my friend, Steph, she often complains scornfully, “You’re such a ‘P’.” “P” refers to the “Perceiving” Myers-Briggs personality type, which refers to folks who are highly context-sensitive (also known as “wafflers”).    (LNM)

Suffice it to say, I hate truisms (except for that one). You could even call me a “philosophical relativist,” which according to Elaine Peterson, would make me a fan of folksonomies. Also true. And in a metaphysical twist that will drive the less philosophically-inclined (and Steph) crazy, if you were to ask me if folksonomies were better than taxonomies, I would respond, “That’s not a valid question.” Folksonomies and taxonomies are not quite apples and oranges, but they’re not apples and apples either. Debating the two is intellectually interesting, but it obscures the real opportunity, which is understanding how the two could potentially augment each other.    (LNN)

The impetus for this little outburst is Gavin Clabaugh‘s recent piece on folksonomies. Gavin (who cites Peterson’s essay) argues that taxonomies are better for finding information than folksonomies. Do I agree with that? It depends. Clay Shirky outlined some situations when taxonomies are better for search and vice-versa in his excellent essay, “Ontology is Overrated: Categories, Links, and Tags”.    (LNO)

What troubles me about the claim at all is that it highlights a distinction that I find to be misleading. In Elaine Peterson‘s essay, “Beneath the Metadata: Some Philosophical Problems with Folksonomy,” the main problem she cites has to do with philosophical relativism. Folksonomies allow it; traditional classification does not.    (LNP)

What is philosophical relativism? If I show you a picture of a mono-colored object, is it possible for that object to be both black and white? If you answered yes, you’re a philosophical relativist.    (LNQ)

On the surface, “philosophical relativist” might sound like another term for “dumb as hell.” But, what if the picture was of a person? And what if that person had an African-American father and a Caucasian mother? Now is it possible to classify this photo as both “black” and “white”?    (LNR)

Language is highly context-sensitive. Philosophical relativists acknowledge this. Believe it or not, so do librarians and traditional taxonomists. A taxonomy attempts to make classification more useful by restricting the scope to a single context. If you happen to be operating within that context, then this works great. There are plenty of situations when this is the case (Gavin cites the medical community, which is a great example), but there are also plenty of situations when it’s not.    (LNS)

Folksonomies allow for multiple contexts, but that does not make them inherently less useful than taxonomies. As Clay points out in his essay, in practice, there’s a long tail of tags applied to different concepts. If something is tagged “black” by 98 people and “white” by two, you can be pretty sure that the object in question is “black.” Scale essentially transforms a folksonomy into a taxonomy with a little bit of noise that can easily be filtered out (if desired).    (LNT)

Frankly, I think the concern is less about whether taxonomies are inherently better than folksonomies and more about whether so-called experts should have a role in constructing taxonomies. Gavin also alludes to this, when he describes a conversation with two friends in a San Francisco coffee shop. (I don’t want to out those friends, but I will say that one of them runs a company named after the faithful companion of a certain oversized lumberjack from American folklore. I will also say that Gavin is an outstanding tea companion, and that we’re working on a project that has very little to do with folksonomies, but that will make the world a much better place regardless.)    (LNU)

Gavin’s friends suggested that folksonomies were a great way of collaboratively developing a taxonomy. Gavin partially agreed, but expressed some doubt, stating:    (LNV)

Rather than the wisdom of a crowd, I’d recommend the wisdom of a few experts within that crowd. In the end you’d end up with a more accurate and useful taxonomy, with half of the wasted bandwidth, and in probably a tenth of the time.    (LNW)

I can actually think of many situations where I would agree with this. One is Pandora, the music recommendation service built on top of the Music Genome Project. The Music Genome Project is a formal ontology for classifying music developed by 50 musician-analysts over seven years. By all accounts, the service is extraordinarily good. Chris Allen sang its praises to me at the last WikiWednesday, and it was all the rage at the original Bar Camp.    (LNX)

But having experts involved doesn’t preclude using a folksonomy to develop a taxonomy. Is a folksonomy developed by a small group of experts any less of a folksonomy?    (LNY)

In 2002, Kay-Yut Chen, Leslie Fine, and Bernardo Huberman developed a prediction market using Wisdom of Crowds techniques for financial forecasting of a division of HP. The market was 40 percent more accurate than the company’s official forecast. The catch? The people playing the market were the same people doing the official forecast. The difference was not in who was doing the predicting; the difference was in the process.    (LNZ)

I’m a historian by background. I have a great appreciation for the lessons of the past, which is reflected in my patterns-based approach towards improving collaboration. Five years ago, I reviewed Elaine Svenonius‘s wonderful book, The Intellectual Foundation of Information Organization, where I wrote:    (LO0)

Fortunately, a small segment of our population, librarians, has been dealing with the problem of information organization since 2000 B.C. Who better to turn to in our time of need than people with thousands of years of accumulated expertise and experience?    (LO1)

There is a tremendous amount of past knowledge that I’m afraid is being passed off as trite and irrelevant, when in fact it is even more relevant today. How many people building tagging systems know about Faceted Classification? How many of these developers know of Doug Lenat‘s brilliant research on Cyc, or that a huge subset of the Cyc ontology is open source? On the flip side, how many librarians and ontologists are needlessly dismissing folksonomies as not as good, and hence irrelevant?    (LO2)

Philosophical debates over taxonomy and folksonomy are exactly that: philosophy. I love philosophy. I enjoyed Peterson’s essay, and I’d recommend it to others. Curiously enough, David Weinberger, one of folksonomy’s foremost evangelists, is also a philosopher by background. (Read his response to Peterson’s essay.)    (LO3)

However, philosophy sometimes obscures reality, or worse yet, opportunity. We should be focusing our efforts on understanding how taxonomies and folksonomies can augment each other, not on picking sides.    (LO4)