Share Your Slides!

Congratulations to Rashmi Sinha and her partner-in-crime, Jonathan Boutelle, for the beta release of SlideShare. SlideShare allows you to publish your slides in You Tube-like fashion. It can read PowerPoint and OpenOffice (sorry Mac users, no Keynote yet).    (LA5)

Here are my long-promised-but-never-published slides from WikiSym 2006 this past August and the Internet Identity Workshop last May:    (LA6)

I’ve got a love-hate relationship with slides, and I try to avoid them when possible, but as Ross Mayfield noted, sometimes they’re useful. And when they are, SlideShare is a fantastic way to share them. I will most certainly be using this service.    (LA9)

This is a beta, and I suspect we’ll see Flickr-like Social Networking capabilities eventually. My only gripe: There should be Permalinks for each slide, not just for the entire deck.    (LAA)

I’ve got a few more invitations left, so if you’d like to play, drop me a line.    (LAB)

Socialtext 2.0 Released

Congratulations to Ross Mayfield, Peter Kaminski, Adina Levin, and all the excellent folks at Socialtext for the release of Socialtext 2.0. Even bigger props for slipping in “Purple Consulting” in the screencast. I’ve been cranking so hard over the past six months, I didn’t have a chance to congratulate them on their Open Source release last July, so now I get to combine my commentary here. (In fact, I’m sitting on a bunch of Wiki-related posts right now that I need to push out; a lot of really cool stuff has been happening.) That’s good, because I have plenty to say.    (L72)

Socialtext 2.0 is an important release for three reasons. First, it doesn’t just look good, it’s highly usable. Adina and Pete deserve big-time credit for this. They’ve spent months painstakingly experimenting and testing the design. More importantly, they haven’t just focused on making it easy to use, but they’ve also agonized over how to accomodate expert usage as well.    (L73)

Have they succeeded? I think the personal home base concept is great. I love the fact that Backlinks are visible on the page and get lots of love. I love their new Recent Changes interface (and I hope to see a Tag Cloud view of the all pages index in the next release). I hate the fact that a Recent Changes link is not on every Wiki page. Both Pete and Adina are well aware of this beef, and I’m also well aware of their reason for not including it. Testing and user observation will tell what’s better.    (L74)

Second, Socialtext 2.0 has a really cool REST interface. Chris Dent has been boasting about it for months, but I didn’t look at it myself until Kirsten Jones walked me through it last week. (Her WikiWednesday presentation from earlier this month is online.) It really is cool, and it’s also useful. Congrats to Chris, Kirsten, Matthew O’Connor, and Matt Liggett for their excellent work!    (L75)

What’s great about this API is that it could very well serve as a standard URI scheme for all Wikis. This would obviate the need for a separate SOAP or Atom API. You just have a regular Web app, and you get the API behavior for free.    (L76)

For example, Alex Schroeder‘s currently going through the same process that Chris went through a year ago with Atom and OddMuse. An easier way around this problem would be to implement these REST APIs.    (L77)

(This is also a great opportunity for me to mention WikiOhana again, which gained great traction at WikiSym last month and which now has a lively Wiki of its own. PBWiki recently announced its own Wiki API, which is a good thing. We are all part of the same Wiki family. Socialtext and PBWiki need to talk about how their two efforts can work together. That’s the WikiOhana Way.)    (L78)

The third important thing about Socialtext 2.0 is that it’s Open Source. (Big props to Jonas Luster and Andy Lester for finally making this happen.) Here’s the thing. I think the announcement a few months back was overblown by a lot of blogosphere hype. The reality of all corporate Open Source releases is that — in and of themselves — they’re mostly meaningless. Mostly, but not completely. The fact that Socialtext 2.0 is Open Source means that other Wiki implementations can benefit from the great work that the Socialtext developers have done, from the APIs to the user interface. That makes for a healthier ecosystem, which is good for everybody.    (L79)

That said, the reason the actual open sourcing of Socialtext 2.0 (and any proprietary software project) is mostly meaningless is that the license is a critical, but tiny part of what makes Open Source software interesting and important. The big part is the community and collaborative process, and a lot of other things besides an open license are required to make that successful.    (L7A)

Before Socialtext went Open Source, I spent many hours talking to a bunch of people there about the impending release. I wanted to know how committed they were to making this a truly open and collaborative software project, because I felt the potential impact on the Wiki community was enormous. The answer I got was complex. The fact that everyone was willing to talk to me with no strings attached, in and of itself, demonstrated a commitment to openness, and I’m still grateful for that. The code itself will be a short-term bottleneck, as it needs a lot of work before outside developers will find it compelling. I also think the licensing terms are weaker than they need to be, although I also understand the outside pressures that make it so.    (L7B)

In short, I think the spirit is strong within Socialtext to fully realize the potential of this Open Source project, but there are also roadblocks. Hopefully, external pressures won’t squash that spirit. If Socialtext ever fulfills its potential as an Open Source company, it will not only help the ecosystem, but it will also tremendously benefit Socialtext as a business.    (L7C)

WikiMania 2006: Quick Hits and Final Thoughts

I really enjoyed Wikimania, but it felt distinctly different than last year. A big part of it was personal. The conference was held in Cambridge, my home for four years, so the location itself was familiar and uninteresting. I was only there for three days, whereas last year I came early for Hacking Days, where I had a chance to get to know people better at my leisure. I also had much more on my mind, whereas last year, I was fully present the whole time — morning, noon, and night.    (L0E)

Part of it was the conference itself. It wasn’t as international as last year, but it was still quite good — one out of four attendees were from outside of the States. There were also more visitors, folks new to Wikis who came to see what this stuff was all about. Several of these people were fairly high-level, described by Jason Calacanis as “folks who ride on the back of builders.”    (L0F)

The same held true for RecentChangesCamp earlier this year, except the spirit was quite different. There, the visitors were eager to learn and to participate, and the community embraced them. Here, many visitors stayed at arm’s length, choosing to observe from afar rather than immerse themselves in this wonderful community. At Wikimania last year, a different group of us would go out every night, laughing, sharing stories, mixing with other groups. This year, there were more clusters, more silos. I saw people — especially the visitors — sticking with the folks they knew, rather than mixing with others.    (L0G)

That is not our community’s way, and I found it mildly distressful. To some extent, it’s the price of success — especially true in the case of Wikipedia — and the result of the culture that those not acclimated to Wikis bring to the table. To a large extent, process is at fault. I find it fascinating that a community schooled in self-organization and the value of emergence continues to organize top-down gatherings. If it’s not careful, Wikimania may eventually go the way of Linux World, Comdex, and many other conferences that began as a wonderful, generative community gathering and eventually became a meeting place for fast-talking salespeople.    (L0H)

Despite my standing in the Wiki community, I’m an outsider to Wikipedia, and I only have three ways of encouraging a shift in how Wikimania operates. The first and best way is to become active in the community and in the planning of the next conference. In an alternative world, this would have already happened, but the reality is that it’s not likely. The second and worst way is to preach to the folks in the community, which I’ve been doing. I find this distasteful. It’s my personality to effect change, not to talk about it.    (L0I)

The third way is to create a space where people can learn for themselves and to catalyze that learning as much as possible. This, in a nutshell, is the purpose of Blue Oxen Associates. I’ve had some success in this area. The FLOSS Usability Sprints exposed some folks to effective collaborative processes, including one of the original Bar Camp organizers. I was then able to point to Bar Camp as a model for the RecentChangesCamp organizers, who wanted to bring Open Space to the Wiki community. Both the usability sprints and Bar Camp helped spawn DCamp, the Bar Camp for the usability community. Our “Tools for Catalyzing Collaboration” workshops have inspired a number of people to pursue similar event models.    (L0J)

In addition to helping the tech community learn about face-to-face collaborative processes, I’ve also helped other communities — from Planetwork to the World Economic Forum — learn how online collaborative spaces can complement physical ones.    (L0K)

All of this is just the start. I have bigger and better things in the works. More importantly, the meme is starting to spread. I’ve helped initiate some of this, but there are many other sparks, and others are starting to fan the flames. We will learn how to collaborate more effectively. But it will take time.    (L0L)

I’m sounding a bit ominous, and it’s an exaggeration of how I actually feel. As I said before, all in all, Wikimania was wonderful. When you bring great people together and get out of the way, great things happen. Even if there are minor obstacles, great people will find a way around them. This has held true not just for the participants at Wikimania, but for the organizers. I am amazed at the efforts, commitment, and passion of Samuel Klein, Phoebe Ayers, Delphine Menard, and the many, many others who worked ridiculously hard to make this conference happen. The whole community deserves tremendous praise. I hope it continues to do what it does well, while unabashedly exploring ways to improve.    (L0M)

One goal that the Wikimania organizers should have for next year is improving conference Wiki usage among the participants. Effective self-documentation via Wiki is a staple of Blue Oxen‘s processes, and we’ve managed to influence many others about it, including Bar Camp and the Aspiration events. But the best Wiki usage at an event I’ve ever seen was at RecentChangesCamp. The community was already steeped in Wiki culture, and the process encouraged self-documentation. The fact that neither Wikimania nor WikiSym has seen effective conference-wide usage of Wikis is an indicator that something is blocking the community’s natural instincts. It’s also a lost opportunity, as those who attend the conference seeking to learn about Wikis miss out on the chance to experience them first-hand.    (L0N)

Quick Hits    (L0O)

  • I was amazed at the number of speakers who exclaimed how honored they were to be there. Some of them were merely experiencing the euphoria of speaking at a gathering of their peers for the first time. Others were hardened veterans of the speaking circuit, including Yochai Benkler and David Weinberger. Yochai even interrupted his traditional two months beach getaway to speak at the conference.    (L0P)
  • Speaking of David Weinberger, I saw him talk for the first time, and now I know what the fuss is about. He’s a wonderful speaker — self-deprecating, sharp wit, great sense of humor, and very thoughtful. He did a Monty Python-like parody of Lawrence Lessig‘s presentation-style that had the entire audience rolling with laughter, and he managed to slip in references to Hegel and Heidegger without sounding pretentious. But I had two beefs with his talk. (Boy, I’m just Mr. Negativity today.) First, he disputed the notion that knowledge is just in people’s head, citing all the knowledge associated with the artifacts that surround us. I understand the point he was trying to make, but I didn’t like how he made it. Artifacts are not knowledge. I generally find myself taking the exact opposite stance as Weinberger — emphasizing that knowledge is in our heads, because it stresses the human element we so often forget when we think about our relationship to knowledge. Second, he made a hypothesis about Wikipedia editing behavior that practically everybody in the room knew was wrong. He admitted that he was speculating, and gracefully acknowledged his error when informed of it, but he never should have made that mistake in the first place. There were many people he could have simply asked before making such a claim.    (L0Q)
  • The best talk from someone I had never heard of was by Seth Anthony, who spoke about Wikipedia editing patterns. See Ross Mayfield‘s notes for a summary.    (L0R)
  • Fernanda Viegas and Martin Wattenberg, the IBM researchers who created History Flow, gave an outstanding talk where they demonstrated some new visualizations of Wiki usage. Some of those visualizations are available in my Flickr collection. I particularly found their visualizations of user behavior interesting, because of past suggestions that such visualizations could be a powerful way to help casual readers determine reputations. The biggest obstacle (besides the computing power required to generate these visualizations)? Privacy. Even though these visualizations were based on public data, that does not automatically make it okay to make those visualizations available. Witness AOL’s recent fiasco (and read Tom Maddox‘s commentary).    (L0S)
  • I caught up with Denny Vrandecic towards the end of the conference, and I’m glad I did. He gave me an in-depth demo of Semantic MediaWiki, which he had first proposed (but had not coded) at last year’s Wikimania. The notion of encoding link types in Wikis is not new, but up until I saw the Semantic Mediawiki, the best implementation I had seen was Evan Prodromou‘s WikiTravel. I think the Semantic Mediawiki is a better approach. It’s less expressive than WikiTravel, but more likely to be widely adopted. I plan on experimenting with it and incorporating some of its capabilities into my own Wikis.    (L0T)

Web 1.0 VC Pitch Champions

The highlight of my Wikimania experience came at the party on Saturday night, when Ross Mayfield and I won the Web 1.0 VC Pitch competition, judged by Mitch Kapor, Brewster Kahle, and Jack Herrick. The pitch? Ross’s first startup, which at one point had a market cap of $1 billion and a fat $60,000 in total revenue. Gotta love the bubble, baby! As Jack said when announcing the results, truth is sometimes stranger than fiction.    (L02)

I did my part by doing my best Steve Ballmer impression, only ignorant and more obnoxious. We may have been the only pitch that the judges actually heard, thanks to our shouting and gesticulations. Here we are proudly showing off our spoils — Wikimania staff T-shirts and Wikipedia lanyards:    (L03)

https://i0.wp.com/static.flickr.com/84/207953953_4c447c8f34_m.jpg?w=700    (L04)

Ah, sweet, sweet victory. If only it really were 1998 again….    (L05)

Purple Numbers and WIKIWYG

For a while, it was looking like I was going to break another personal blogging record last month, then things got so busy I had zero time to blog whatsoever. That means I’m in catch up mode again, so as usual, I’ll post in reverse chronological order (which in the blogosphere is really reverse reverse chronological order).    (JYN)

Yesterday, I spent the afternoon at Socialtext, where they were having an all-hands meeting. They graciously invited me to participate in the Open Space segment of their gathering, which meant quality time with Chris Dent and a rare opportunity to evangelize the Church Of Purple together. Of course, Chris has been spreading the Purple religion at Socialtext for a while now, so it wasn’t as much about evangelism as it was about next steps.    (JYO)

As I’ve mentioned many times before, browser-based WYSIWYG editors are an exciting development because they allow us to make Purple Numbers transparent in the authoring process. Right now, when you edit a PurpleWiki page, you see the node ID tags (e.g. {nid 123}). This is impossible to get around with the default browser text-editing widget. However, with a WYSIWYG editor, you can hide the Purple Numbers while still maintaining their associations with a node behind the scenes.    (JYP)

That’s the theory, anyway. In particular, I’ve been excited about WIKIWYG ever since Ross Mayfield showed me an early prototype last August. I had a personal bias, since Chris Dent and Matt Liggett helped write it, as did Casey West and the inimitable Brian Ingerson, whom I finally met last weekend at Tag Camp.    (JYQ)

Yesterday afternoon, we discussed Purple Numbers and WIKIWYG, and it was good. Then in the evening, Ingy and I spent a few hours trying to get WIKIWYG integrated into PurpleWiki.    (JYR)

We didn’t quite make it. Our biggest roadblock was a bug we discovered in Mozilla’s design mode that we can’t do much about. (My days of statically typed languages are well behind me.) But, we got something somewhat working, and I learned a heckuvalot. You can play with our semi-working demo.    (JYS)

WIKIWYG seems well-architected and is easy to customize. For folks with relatively standard Wiki editing requirements, I highly encourage you to play with it. PurpleWiki has some special formatting funkiness (mainly due to the Purple Numbers), but we were able to get around this fairly easily. (This was also true thanks to PurpleWiki‘s model of parsing to an intermediate data structure, then using view drivers to serialize. I wish more Wiki engines did this. I know Magnus Manske is thinking about doing this for Mediawiki, and I think Janne Jalkanen is already doing it with JSPWiki.)    (JYT)

The Mozilla bug annoyed me, because it’s a show-stopper in some ways, and there’s not much I can do about it. I didn’t realize it, but all of the JavaScript WYSIWYG widgets actually switch to the browser’s “design mode” in order to handle WYSIWYG editing. As with many HTML editors, design mode does not handle structure cleanly, and you end up getting weird artifacts such as spurious break tags. Our problem was that we serialize node ID information as id attributes in the HTML tags. However, Firefox does not maintain those attributes correctly when you move content around.    (JYU)

I’ll report the bug (if folks have suggestions as to the best way to bring this to the right people’s attention, let me know), but it also puts the kibosh on my hopes for WIKIWYG and Purple Numbers. Even if the bug is fixed in the next version of Firefox, we’re still prey to all the folks using older versions as well as Internet Explorer or Safari, which have their own problems with design mode.    (JYV)

Chris and I discussed one workaround that I’m still pondering: render the Purple Number and have users be responsible for maintaining the association with the nodes. That’s the status quo, except users are doing it in WikiText rather than in WYSIWYG. Doing it in WYSIWYG certainly lowers the bar, and it’s probably the next best thing for us to do.    (JYW)