WikiMania 2006, Day One

Posted on Published by Eugene Eric Kim

Day one is over. Brain is overloaded. Very tired. Attending conference during day/evening, then working late into night — bad. Law school dorms with no air conditioning in Cambridge in August — also bad.    (KWO)

Still, much to share. And amazingly enough, I will — at least a bit. There’s something about this conference that actually gets me to blog, rather than simply promising I will. Besides, I’m going to set a new record for responsiveness to Tom Maddox, even if it is via blog.    (KWP)

It is incredibly surreal to be back at my alma mater surrounded by post-college friends and colleagues. What makes it even more surreal is that folks from all facets of my professional life seem to be here, not just Wiki folks. I mentioned having my fingers in a lot of pies, right? Well, all those pies are unexpectedly well represented this weekend. It started yesterday when I discovered that Chris Messina and Tara Hunt were on the same flight to Boston, and culminated at dinner with Greg Elin (whom I first met at the FLOSS Usability Sprint, and who invited me to join him for dinner), Daniel Perry (a lawyer who’s been an important contributor to recent Identity Commons discussions), Tom Munnecke (first introduced to me by Jack Park when I was just starting Blue Oxen Associates), and Doc Searls (who needs no introduction). Also at the dinner: Ellen Miller, Micah Sifry, David Isenberg, Britt Blaser, and Yochai Benkler. Quite a contrast from last year, when I was hanging with grassroots Wiki peeps every night. I’m not complaining, though. The conversation was fascinating, even if we didn’t talk much about Wikis.    (KWQ)

Keeping with this theme, I didn’t hear much about Wikis today, other than my interview with Ward Cunningham. I kept my questions pretty basic, as a lot of folks there had never heard him speak, but I managed to slip in a few probing questions for myself. I asked Ward about the evolution of Wiki culture, and I specifically mentioned the culture of anonymity that he strongly encouraged in the early days, but that seems mostly absent in today’s Wikis. Ward seemed resignedly ambivalent. I asked him about what makes a Wiki a Wiki, and he was decidedly agnostic in his response: anything that facilitates a permissive spirit and mode of collaboration. I’m not sure whether he was being political or whether he truly feels this way. My guess is a bit of both, but I’ll press him on this if I get a chance later this weekend.    (KWR)

I showed up late to Larry Lessig‘s keynote, but I was unconcerned, as I had heard him give his Free Culture speech before. It’s excellent, but he recycles it often. Sure enough, he was doing the same speech, and I started tuning out. Fortunately, my brain was paying partial attention, or I would have missed what may end up being the most intriguing development of the conference.    (KWS)

Larry started talking about the interoperability of licenses, and how it was silly that the FDL and Creative Commons BY-SA licenses could not be relicensed interchangeably, even though the two licenses were equivalent in spirit and intent. He then proposed an interoperability clause as well as a neutral organization whose purpose would be to classify equivalent licenses. His talk was followed by a really good panel discussion between him and Eben Moglen. This stuff is really complicated and important, but it looks like Larry and Eben are serious about working together towards a common solution. Apparently, Jimbo Wales deserves a lot of credit for getting these two to cooperate. Did I mention that I love this community?    (KWT)

Quick hits:    (KWU)

  • I shared a flight and T ride here with Chris Messina aned Tara Hunt. (Chris was presenting on Bar Camp.) Chris extolled the virtues of Voodoo Pad, which apparently has autolinking features a la my Markup Free Auto Linking Wiki idea.    (KWV)
  • Was excited to see two of my roommates from last year: Kurt Jansson, a German doctoral student and president of the German chapter of Wikimedia Foundation, and Juan David Ruiz, a Chilean lawyer.    (KWW)
  • Saw Erik Zachte in the morning, who does awesome Wikipedia work. Erik immediately told me about two cool projects I had never heard of: FON and Wikimapia.    (KWX)
  • Caught up with Rory O’Connor after my session with Ward. Rory’s a filmmaker who came to last year’s Wikimania to make a documentary on Wikipedia. What I didn’t know was that he was so inspired by the proceedings, he decided to release all 13 hours of his footage under a Creative Commons license to encourage folks to mix their own documentaries from the event. Check it out, and mix away! There’s some interview footage of me somewhere in there, and I make a cameo in Rory’s 11-minute rough cut, in the background of Jimbo’s interviews yukking it up with John Breslin.    (KWY)
  • Somehow, I got recruited by multiple Wikipedians to help with the lightning talks due to my process expertise. My expert advice: “Move those chairs into a circle, and be firm with the time limit.” Yes folks, this is why I get paid the big bucks.    (KWZ)
  • Briefly got a chance to chat with Tim Starling about the OpenID integration in Mediawiki. Tim explained that they’re going to unify the user databases across all the different Wikimedia properties. This was further validation that Yoke‘s identity proxy approach is useful. Of course, one of these days, I’m going to have to actually write down what that approach is, so that I can convince people of its utility.    (KX0)

OpenID 2.0 Developer Day, August 10

Posted on Published by Eugene Eric Kim

Two important OpenID developments to announce. First, there are a bunch of $5K bounties available for folks who integrate OpenID into Open Source projects. You heard me right — you can get some cash for doing something you probably want to do anyway. Second, Kaliya Hamlin announced an OpenID developer day in Berkeley next Thursday, August 10, from 6-9pm. The lineup includes David Recordon, Andy Dale, Mary Hodder, and Scott Kveton. I’m going to try to show, and I hope many of you do the same.    (KWN)

Angry Rant on Wikis

Posted on Published by Eugene Eric Kim

Earlier this month, Jonas Luster invited me to speak at WikiWednesday. I didn’t have anything prepared, and I didn’t feel particularly motivated to prepare anything, so, I told Jonas that I was just going to rant. Jonas, being Jonas, loved the idea. So after IIW wrapped on May 3, I headed up to Palo Alto. I promised folks at IIW that I was going to give an angry rant on Wikis, and so several people decided to come watch, including Phil Windley, who blogged it. Feedback was great, except for a few complaints that I wasn’t all that angry. I promise to get more worked up next time, folks.    (KK2)

I’ve made all the points I made in my rant before in some form or another, often on this blog. Nevertheless, it was the first time I shared these ideas as one semi-cohesive thought, and so it’s worth rehashing the points here.    (KK3)

Overview    (KK4)

There are two things that make Wikis cool:    (KK5)

Lots of folks have latched onto the open access part, and there’s been some interesting exploration in this area. Very few folks know about or understand the Shared Language aspect. I think this is a huge loss, because it’s what makes Wikis truly transformational.    (KK8)

Open Access    (KK9)

Since I had just come from IIW, I started with digital identity. First, I said that all Wikis should support some form of distributed Single Sign-On, be it OpenID or something else. Implementing Single Sign-On does not imply loss of anonymity. Most Wikis give you the choice of logging in or not; implementing Single Sign-On would give you the additional choice of using a single identity across multiple sites.    (KKA)

Why would this be useful? Consider Wikipedia. As my friend, Scott Foehner, commented in a previous post on this topic (to be visible again when I turn comments back on), Wikipedia actually consists of a number of different Wikis, one for each language plus a number of special Wikis, such as its community site. Each of those Wikis require a separate user account. Not only is this a huge inconvenience, it effectively prevents you from having a single digital identity (along with your associated reputation) across each of these sites.    (KKB)

Simply having Single Sign-On across all of the Wikipedia Wikis would be valuable. More importantly, the identity community has converged to the point where it doesn’t make sense to roll your own protocols. There are several good existing protocols to choose from, and many of those are in the process of converging.    (KKC)

Reputation is closely associated with identity, and it’s also been one of the most popular topics in the Wiki community over the past year. However, most people have a misguided notion of what reputation is and what we should do about it. Reputation is what others think about you. Reputations exist in every system, whether or not they are explicitly represented. Reputation cannot be quantified. However, you can identify the factors that determine reputation and make those factors more explicit.    (KKD)

In Wikis, this could manifest itself in a number of ways. For example, one way to determine the quality of a page is to view the number of people who have edited it. You could make that number explicit by subtly changing the background color of that page — slightly yellowed for a page with few contributors and bright white for a page with many contributors.    (KKE)

The important point here is that you are not making a value judgement on reputation. You are not saying that a page that has many authors is better than a page that does not. All you are doing is making it easy to see that a page has many authors. Readers can determine for themselves how much weight (if any) to place on this factor for the reputation algorithm in their heads.    (KKF)

The most important button on a Wiki page is the Edit button. That button implies Permission To Participate. It should be one of the most visible buttons on any Wiki. If a Wiki looks too good, that discourages participation. Who wants to edit something that looks like a finished product? Ward Cunningham used to suggest sprinkling typos across a Wiki page to encourage others to participate.    (KKG)

At this point in the rant, I plugged both Ward and MeatballWiki. The Wikis success is no accident. A lot of the fundamental design features that make Wikis powerful were completely intentional, a testament to Ward’s brilliance. Additionally, most of what I ranted about is not new to the Wiki community. A lot of it — and more — has been discussed on the venerable MeatballWiki. If you really want to get a deeper understanding of how to improve Wikis, you should be on Meatball.    (KKH)

Shared Language    (KKI)

Last September, I wrote:    (KKJ)

What really makes the Wiki’s LinkAsYouThink feature special is that it facilitates the creation of SharedLanguage among the community that uses it. As I’ve said so often here, SharedLanguage is an absolute prerequisite for collaboration. The lack of SharedLanguage is the most common roadblock to effective collaboration, be it a small work team or a community of thousands.  T    (KKK)

It bears repeating over and over and over again. Wikis are transformational because they facilitate Shared Language. This is a feature that should be propagated far and wide, both in Wikis and other Collaborative Tools.    (KKL)

I noted two possible convergences. The first is Wikis and tagging. They both share a similar principle, namely namespace clash, and we should look at ways of combining these two concepts. For example, where’s the tag cloud view of a Wiki’s page index? Another idea: Clicking on a tag should also return Wiki pages of the same name. Technorati should be indexing Wiki pages and treating their titles as tags.    (KKM)

The second is implementing Link As You Think in all tools. Blogs that are built on top of Wikis (such as TWiki and JotSpot) have these features, but you don’t have to build a tool on top of a Wiki for this to work. This blog runs on blosxom, but it has Link As You Think. Chris Dent‘s blog runs on MovableType, and it has the same feature. It shouldn’t just apply to blogs, either. It should work in web-based forums and other Collaborative Tools.    (KKN)

DataTao

Posted on Published by Eugene Eric Kim

Andy Dale and the good folks at ooTao have been quietly driving the development of data sharing technologies based on XDI. This is one of the candidate Identity Commons technologies for permission-based sharing and synchronization of identity-related information.    (JSF)

What does this mean? Most of us have personal information stored all over the Internet, with no control over who can access it and what they are allowed to do with it. The privacy implications are obvious, but issues of control go beyond privacy. I may want 15 different organizations to have access to my email address, but I don’t want to have to contact each of those organizations separately every time my email address changes.    (JSG)

The knee-jerk reaction to the latter problem has been to create centralized repositories of identity data, and to persuade people to store all their data there. That approach has no long-term future.    (JSH)

We need a distributed system that gives individuals granular control over their digital identities. That’s the long-term vision of Identity Commons, and the technologies that will make this all possible are slowly coming into fruition.    (JSI)

Andy recently announced plans for DataTao, an “interoperable data hub for user controlled data.” As a service, I think DataTao will be tremendously compelling. A natural first application will be a distributed Plaxo-killer. You’ll be able to keep your contact information wherever it already is — even across multiple sites — and to grant permission to people to synchronize with that data. In other words, Andy or anyone else will be able to get my latest contact information without having to subscribe to some centralized repository, assuming I’ve given them permission. More importantly, I can take that permission away.    (JSJ)

On a technical level, what’s interesting about ooTao’s announcement is that the service is not wed to i-names. It will work with a variety of identity protocols, from OpenID to LID. On the other hand, the system will use XDI. I’ve expressed concerns, both privately and publically, over whether XDI is the best architecture for the kind of data sharing we need. The proof will be in the pudding; it will be great to see a real service built on top of XDI in action.    (JSK)