Ross Mayfield's Weblog

Pownce: Collaboration from and at the hip

At first glance, Kevin Rose of Digg's new startup Pownce is Yet Another Status Message Service (YASMS) like Twitter, Jaiku or Plazes.  But really, its a collaboration app made for the most modern web.  It's bound for adoption because the founders can drive word of mouth and its inherent virality.  And perhaps what it does is less important than the three trends it represents.

Like others, the primary activity is messaging to your social network.  You message to all your friends or public like others, or directly like typing "D Username" in Twitter at the beginning of a message, but also lets you select a subset of friends.  Beyond messages, you can share links, files and events.  Beyond doing this on the web, there is a Windows or Mac rich client.

The digerati and diggerati will probably rant away about how it doesn't have SMS or IM integration like Twitter, how the content is mundane (same thing with blogging five years ago), how it needs APIs and microformats (which it does, and hooks into Twitter, del.icio.us, Flickr, Upcoming and Facebook are inevitable), or just complain about adding friends again (Adding friends is the new zen).  The design is slick on both the web and client and they will polish up key details like last names, comment threading like Jaiku, permalinks and need a more public space to explore. 

What does it matter how one comes by the truth so long as one pounces upon it and lives by it? -- Henry Miller

But here's the three trends:

YASMS Gets and Ad Format -- I admire startups that launch with an actual business model.  They have introduced a new Ad Format, a message broadcast into the stream with the Pownce icon (the green P in the above screenshot is an ad from PBwiki, I love wikis) that doesn't seem to persist.  I didn't mind the ad from LaughingSquid (first I saw) in my peripheral attention.  And if I did, I could pay to make it go away, but subscribing to the Pro version for $20/year and also be able to send files over 100MB.

AIR Gets a Viral App -- The client is built on the Adobe Integrated Runtime (AIR), formerly Apollo and still in Beta.  Pownce's virality will give AIR the airtime it needs for base of users to install it, making it easier for the next AIR client to come along.  This should be AIR's showcase.  That said, Pownce's model is what I call contained virality, where limits are part of the draw and when you are in you feel in (at least to share music, a hidden driver).

Consumer Collaboration Get Hip -- Anyone who follows the enterprise collaboration space will immediately see parallels with P2P collaboration apps like Groove or Shinkuro.  Or IM, Skype and more directly enterprise IM like MindAlign.  The key difference is group forming by social network and default modes of sharing more publicly.  Pownce will appeal to a very different demographic, that's already collaborating on blogs, wikis and IM, and potentially full a space in between.

There are several vectors in which Pownce could go, or others could go towards including presence, location, public IM, security, indexing and integration.  Pownce will have to open up invites soon (I'm out, please don't ask) to build its network effect before others encroach.  It isn't unique enough to gain the continuous or at least partial attention of users for yet another client.  Infrastructure costs will be greater than P2P.  At the risk of breaking the design and making it too complex, Pownce should give serious thought to the role of standards and how they could be a client for Facebook.

Please, I don't have any invites.

Jaiku Tips the Tuna?

Did Jaiku tip the tuna yesterday?  Leo Laporte  jumped ship from Twitter to Jaiku, his 4,000 followers followed.  The Twitter herd debated platforms, has herds do when chosing to migrate.  Suddenly the story was Twitter vs. Jaiku and Jaiku team dealt with digesting a big chocolate Easter Bunny.

Let me provide some context first.  I was exposed to Jaiku at Aula in Helsinki last June.  From my notes:

Jyri Engeström and Mika Raento on social peripheral vision.  Phones are designed with the assumption that you know who you want to call before you do.  You need to process social signals before using the device.  Jaiku, their startup is looking to augment basic functions of a phone by pasting onto it what is happening on the internet.  If you can't find anyone in your contact book, you can search a directory made of everyone's contacts. Calendars let you share future events to let you plan together.  The demo shows very rich profiles based on phone usage (automatic data) and more social signals (more manual) -- which provides a different form of Presence.  In usage, people still call regardless of presence, but when someone doesn't answer, you leverage the presence to understand why. Integrated IM is more convenient than SMS, and includes group messaging.

Since then, Twittr came on the scene and Jakiu's web interface got a major upgrade.  It's important to understand the significant differences between the two services, their design thinking and strengths.  Joi Ito:

Looks like a bunch of people are trying out Jaiku after "tasting" co-presence with Twitter. To me, Jaiku, which existed before Twitter, is a bunch of Helsinki mobile jocks getting into the Web 2.0 of it all whereas Twitter is the Web 2.0 crowd "getting" co-presence...

Jaiku comes from a "presence" background allowing bluetooth proximity, phone idle time, ringer mode and other things to trigger state changes - the messaging came later. Twitter, on the other hand, is primarily messaging, which as we all know, is just a flexible and manual vector for presence information.

To understand where Jaiku is coming from, I encourage you to read this interview with co-founder Jyri Engeström and his post on social peripheral vision (the ability to have your finger on the pulse of your friends, family, and colleagues).

  Twitter on paper 
  Originally uploaded by jack dorsey.

In digging around for some of the thinking behind Twitter, I found Jack Dorsey's napkin design for Twitter:

from a note circa Jan 2006.

casual awareness.
"what are you up to?"

multiple entry point to set status
- web
- email
- phone
- sms
- im

multiple ways to "subscribe" to status
- web
- email
- phone
- sms
- im

3 aspects
- set status
- timeline (collaborative)
- configuration

The interesting thing is that I found it on Jack's Jaiku page where he had included his Flickr stream as part of his presence.  For a long time I've wanted the Xfire for social software, and today Jaiku provides this kind of persistent presence.

Jaiku lets you incorporate feeds from your blog, bookmarks, photos, location -- and Twitter if that is where you prefer to post status.  Every post of any kind becomes an object for conversation, through comments.  This works easily in the web UI, but it also works in the Nokia mobile client because presence isn't overwhelming. Presence is something you can glance at, not an SMS interruption. 

Unfortunately today this requires a Nokia phone, but they are working on a Java version that also specifically supports commenting (kind of like Radar.net, more on that later).  People coming from Twitter won't expect the ability to add their attention breadcrumbs to their attention stream (developers will) and will probably expect something they can adopt on their mobile easily.  In the US, this is a significant barrier (Sidenote: fuck you Cingular.  Making me change calling plans to switch SIM cards from my Blackberry and claiming the handset wont work because you don't sell it even though it runs the same software is an easy way to lose me as a customer, as if I had alternatives.).  Jaiku isn't ready to Tip the Tuna until their next mobile client comes out. 

But until then I'd expect a lot of people to use the web version as an attention pool.  Posting to Jaiku via Twitter is a no-brainer and I'd hope you can do the opposite without loops and dupes soon.  Rafe asked the right question:           Is it possible Twitter and Jaiku will end up sharing users, instead of hoarding them like the IM services did early on? I responded: systems of record are being replaced by systems of discovery. 

In other words, in the first web I would worry about which service I would commit my social network, presence and persistence to.  But services are increasingly making data discoverable and discovering data from other services.  We used to worry about transporting our FOAF relationships, but then I think we realized that each tool is different and being able compose a different social network was a virtue (not just because of faceted identity, but that different tools need different filters and the social network is the filter).

UPDATE: This post was written in haste before going out for Easter.  Jaiku released their API and developer site.  I forgot to highlight Marko Ahtisaari's why I use Jaiku:

1. Silent sociality - checking up on what my friends are up to when convenient, and posting my own state knowing that I won't be disturbing others (unless they have explicitly asked to be alerted).

2. Small-group sociality - Jaiku is not about celebrity. I'm interested in sharing state with a small group I'm nearly always in contact with, what Mimi Ito has called full-time intimate community.

3. Mobile sociality - Jaiku was designed with the mobile "living phonebook" interface in mind. SMS alerts crowding the inbox of one of the few working personal and functional communication channels is not my idea of improving communication. I use the SMS-in posting to Jaiku when I'm using my Nokia 8800 and with my N70 I use the Jaiku phonebook.

4. Background sociality - Jaiku allows me to integrate other online identities and feeds (including delicious, flickr and any RSS) into my single jaiku presence feed. This is done in a way that doesn't confuse these background posts with my explicit state messages.

Rafe posts about adding your Twitter to Jaiku.  And I wanted to add one last thing.  If you aren't trying it with a mobile client, you can't get the real experience.

The Wikinomics Playbook

UPDATE: An interesting related project by Penguin Books is A Million Penguins, letting anyone edit a book to be published.  The wiki is down at the moment, but PaidContent notes it began with “It had snowed, and was now raining. Gritty slush covered the pavement. Sharp crystals of snow decorated grass.”  Reuters notes the challenge is finding “believable fictional voice” within the mass collaboration.  This was a big challenge for group editing of the Wired Wiki story.

The last chapter of Don Tapscott's new book, Wikinomics, invites readers to write it: “Join us in peer producing the definitive guide to the twenty-first-century corporation on www.wikinomics.com.”  Today we launched a Socialtext wiki for the Wikinomics Playbook, where people can not only learn about the power of mass collaboration, but participate in it.  The book is already one of the fastest selling business titles and is an excellent primer on how models of collaboration are unfolding from open source to blogging to wikis in the enterprise to enable people to participate in the economy like never before.

The second to last chapter is about enterprise wikis.  Half of it discusses how Best Buy is using a wiki knowledge-base for the Geek Squad.  The other half is an interview with yours truly and shares some of Socialtext's success stories. The first chapter is available online as a pdf.

 

This is a great example of how a book can be augmented with a wiki, as most books are out of date by the time they are published, never quite finished and have the potential for participation. Last month we helped Larry Lessig share the entire Code 2.0 book in a wiki.  I expect that soon such commons-peer production, a wiki for every book, will be common.

SuiteTwo Launched: Enterprise 2.0 in a Box

A small dream of mine came true today.  We've been preaching an ecosystem of tools for some time now.  We've helped customers stitch them together in interesting ways.  In fact, Andrew McAfee's original article on Enterprise 2.0 was borne from observing what was happening in one of our customers and projecting into the future.  Well, future happens fast.

Looking back, look what I blogged just before the first Web 2.0 conference:

I'm providing a workshop on Enterprise Social Software with Socialtext Customer Mike Pusateri from Disney.  You might recall his great presentation at the at the O'Reilly Emerging Technology Confererence in February. Mike and his team are leading the way with how they are using lightweight web-native tools as a platform for productivity. Not just how they use Socialtext for project communication, but how they stitch it together Moveable Type and Newsgator for an ecosystem of tools with RSS.

That was then, this is now. This morning I provided a workship on Enterprise 2.0.

Today we announced SuiteTwo, The Enterprise 2.0 Suite powered by Intel.  Intel is distributing the Best of Breed wiki (Socialtext), blog (Six Apart), Feed Aggregation (Newsgator) and Feed Publishing (SimpleFeed), supported by Spikesource, through its channels including Dell, NEC, Ingram, Novell and Red Hat.

This fulfills Andrew McAfee's vision of Enterprise 2.0.  In a box.  Made simple for Small-to-Mid-sized Enterprises.  Extensible because we've all supported open APIs.  Enterprise 2.0 is freeform social software adapted for organizations.  SuiteTwo is the first offering to realize the SLATES paradigm:

SLATES = Search | Links | Authorship | Tags | Extensions | Signals

In the latest issue of the Harvard Business Review, McAfee went further to distinguish this Network IT (NIT) from Functional IT and Enterprise IT:

As the DrKW example illustrates, NIT’s principal capabilities include the following:

• Facilitating collaboration. Network technologies allow employees to work together but don’t define who should work with whom or what projects employees should work on. At DrKW, ad hoc teams have formed because employees read one another’s blogs. These teams have used the wiki to accomplish tasks, and they have disbanded without orders from senior executives.

• Allowing expressions of judgment. NITs are egalitarian technologies that let people express opinions. DrKW employees use blogs to voice their views about everything from open-source software to interest rate movements.

• Fostering emergence. “Emergence” is the appearance of high-level patterns or information because of low-level interactions. These patterns are useful because they allow managers to compare how work is done with how it’s supposed to be done. Emergence is also valuable for users. For instance, employees can easily search and navigate DrKW’s blogs and wiki for trends and data even though nobody is in charge of making them easy to use.

...Employees exploit older NITs such as e-mail and instant messaging on their own, but business leaders have a role to play in exploiting newer technologies like blogs and wikis. They can help sustain and increase the use of complements to make the technology continually more effective, primarily by guiding users. Darren Leonard, a managing director in the global equity derivatives business at Dresdner Kleinwort, recalls how he got his colleagues to use the company’s wiki: “First, if a wiki has no structure, it’s perceived not as an opportunity but as anarchy, and our people have no time for anarchy. I went back to my initial pages and rewrote them to be a lot more directive. For example, I made a page with the agenda for an upcoming meeting and asked people to add to it. Second, wikis have to be clearly better than other ways of collaborating. There have to be uses [for them] that demonstrate their power. One of these uses came prior to a special senior management meeting where we could bring questions from our groups and get them answered. I put up a page…asking my [team members] what questions they wanted me to ask on their behalf. People used the page to post questions, edit them, and discuss which ones were the most important and why. That really accelerated wiki use. Finally, old habits are hard to break. The tendency is for people to keep using e-mail because that’s what they know....I have to [tell them], ‘I’m not reading e-mails on this topic. Use the wiki’ or ‘Everyone’s assignments are on this page—use the same page to report on progress.’”

Lead users and enterprises already work this way today.  Only they do so without usable efficiency.  Integrated single sign-on, search and tag cloud are just the beginning.  One click subscription to a page, blog post, search query, report, weblog and wiki make feeds usable (unlike today's user experience, when they click on an orange icon and think their browser is broken).  Rapidly form groups, draft together on a wiki page, publish to a blog and track results. 

Beyond making such tasks efficient, the benefits to productivity, discovering emergent intelligence and high-engagement marketing are significant.  Very soon a user will wake up in the morning, log in to SuiteTwo, immediately recognize something emerging.  With the top blog posts telling her what the company is talking about, the top wiki pages showing her what people are working on, top posts from the outside that her company is subscribed to and the feedback from what they are publishing
-- something will emerge.  She recognizes the opportunity, pulls on the social fabric and easily forms a diverse group of experts.  They follow new feeds and generates others while working with a little productive friction.  They develop a plan and draft a new offering in the wiki.  They publish to a public blog and track where it goes. The feedback loops continue, she goes home for the day and the organization is bound to adapt again.

This isn't your Dad's enterprise, but one you will be working with soon.

Human Powered Serendipity

Nat Torkington has a great post on homophily and social software design.

The Washington Post has a brief article called "Why Everyone You Know Thinks The Same As You".  In short, you hang out with people who are like you, a phenomenon known as homophily. This happens online, and indeed the Internet can lower the costs of finding people like you. But homophily raises the question for social software designers of how much they should encourage homophily and how much they want to mix it up.

He goes on to explore the tradeoff of fulfilling our desire to group with the similar and expose people to the different.  I'd suggest considering that the most productive social networks have a dense core and a dynamic periphery, and strong ties don't come cheap, there is a role for both.

Nat suggests recommendations (if you liked X, try Y) are quick wins, but still within narrow interests, while Mavens-as-algorithms (people who liked X also liked Y) can serve as connectors.  Personally I prefer designing in popularity indexes because it inspires productive gaming for participation.  I also fear my Gmail thinks I am gay.  But while you can automate some aspects of social discovery, they lead to weak ties at best.  The answer may be more pivotal..

Another way to build in serendipity is to have pivotal navigation: tags, top ten lists, and Flickr's interestingness measure are all ways to break people out of whatever group they're in and take them to something new. Links are at the heart of this: we've all been lost in clicking our way through a drunkard's walk of the Internet at one point or another. Inspire that in people: build those links and the metadata behind them into your site from the get-go.

Links remove barriers to our abundant desire to share.  Not only do we have a desire to be with people we like, we suffer from the problem of believing what we write and create is more valuable than it really is (cough).  Some facet of our identity is just waiting to show off to strangers, not just in hopes of finding more people we like, but affirmation from even people we may dislike (deep down George W wants Kim Jong Il to like him, really really like him).  We may want to be with people we like, but we have multiple facets of our identity, so we are like different people when we can get away with it. We also affiliate ourselves with people we would like to be, or objects that help express given facets of our identity.

More practically, people and the social incentives that drive them are incredibly diverse, and value accrues to people who bridge social network clusters.  So give users tools to bridge divides and create new groups.  Support ridiculously easy group forming.  While many things drove Myspace into popularity, easy group forming around independent bands drove not only growth overall, but rich serendipity.

I believe people self-correct for homophiliy.  Just yesterday in an internal blog, Kirsten Jones noted she realized has been so heads down at work that she was going to subscribe to some new feeds on the outside.

But I have one point for this post, it is that people are better connectors than algorithms and if you give them tools for it, their practices will exhibit emergent properties you couldn't predict as a solution for serendipity.

I'll end this post with an underscore, from IWB at IBM:

Through experience, we have learned the limitations in our ability to leverage IT to automate quintessentially human tasks, even many seemingly simple ones, no matter how fast our computers have become.  I think that the key breakthrough that we have needed here is a cultural one - it is perfectly OK to integrate people in the design of our systems.  A good, elegant design is one that lets machines do what they do best, and lets people do what they do best.

SlideShare: the YouTube of Powerpoint

SlideShare launches today -- the YouTube of Powerpoint.  While Powerpoint destroys thought, so does TV.  And misgivings aside, slides can be an art form in and of itself.  They are objects you spin stories around.  Like this:

It is easy to embed a presentation and player within a site, blog or wiki. This one is of my Keynote at Networld/Interop, a good companion to the video.  I've been playing with the Alpha and really have to applaud Rashmi (you may know her from Dcamp), Jonathan and the gang at Uzanto.

You upload your Powerpoint (PPT and PPS formats) or OpenOffice (ODP format) slides into My Slidespace with a familiar title, description and tags. The flash player is fast and intuitive.

Slides are findable by search (the content of the presentation is indexed), Latest, Popular, Featured, Profiles and Tags (Latest, Popular this week and Popular all time).  Here is an RSS feed of the latest.

What's also fascinating is their servers are backed by Amazon S3 (Simple Storage Service).  The other week when Socialtext 2.0 launched with a large-file webcast, we got Techcrunched and were worried about the load on our servers.  After a little scrambling in IRC, Pete Kaminski leveraged S3, and problem solved.  In this case, SlideShare has web serviced their scalability.  An interesting model to watch, and good thing if this thing is a sudden hit.

Between Popular and Personal there is Social

Every time I see Gabe Rivera of TechMeme, I ask for the same thing -- MeMeme.  Give me TechMeme where the core index is based on who I read, about 150 people at any given time, to show me what my friends are interested in.  I used to ask this from people who make Newsreaders.  Because simply somedays you are too busy to read everything, but you want to make sure you haven't missed something big.  That's the real value I derive from TechMeme today.  But what I really want find something that is big with my friends, which in the larger blogosphere is actually something small.

Today we have two new and seriously great kinds of attention tools.  Newsreaders give us the ability to personally personalize.  Combined with persistent query feeds, you can follow the people and things you know you want to read.  Similarly, social networking services with a purpose let you aggregate the objects of your friends, be it pictures with Flickr, or posts with Vox.  Tagging then lets you pivot for social discovery, but that is digging deeper than you often have time or interest for.

TechMeme and others show us mass popularization.  Different communities help things bubble up.  In Social Software, you first saw this with Blogdex and DayPop.  What in the blogosophere has the most attention within a given time period.  Now we have Digg, del.icio.us/popular, Reedit, Netscape, Technorati, YouTube, Dabble, Last.fm, Flickr Interestingness and a gazillion other increasingly rich examples.  This is a Wisdom of Crowds we couldn't gain before for discoverable knowledge.

As an aside, I wonder how original Slashdotters feel about Diggers' favor for a popular  answer rather than a leading question.

So more concisely, what I hope develops:
* Tools that let me personally personalize should give me just one more degree of interestingness and popularization. 
* Tools of mass popularization should give me social popularization

Since Flickr has both kinds of attention tools, let me give specific suggestions for extension.  For within My Contacts's Photos, show me the most viewed, favorited and commented by my contacts.  Then show me the most viewed, favorited and commented pictures by my contacts in Everyone's Photos.

Now, this is just one user's greedy suggestion, and there serious usability and algorithmic challenges to overcome.  But what I'm getting at is part of the future of media.

The other night I watched the evening local news broadcast for the first time in a while.  Its funny how local news attempts to localize national news.  The idea is that if they show you a Mom in the Bay Area of a Soldier in Iraq, you can relate to that and it brings the story home.  But unless the story originates from that Mom or Soldier, it is just an overlay with too much of a contextual shift.  Similarly, when an item of local news is made national -- it is too shallow for our local tastes and we are attracted to it simply because or fair city is made popular. 

I empathize with the expert editors behind these mass media and their attempts to connect the interesting for me, when me is lost in a demographic.  But I've had a taste of going direct.  When I carry the burden of discovery, and float around YouTube's popular and related clips, I can compose a broadcast for myself.  The outstanding political commentary, funny stuff and best soccer highlights from around the world.

But after a long day of work, I'm tired, and want the network to work for me.  Cue up not what is popular, or what the people I subscribed to produced.  Cue up what my social network has found interesting.  At any given time it may be local, national, international, topical or mundane.  Of course, in the process of actively consuming it, I'll leave behind breadcrumbs of attention to make it better for my friends.

UPDATE: I've been ranting about this for years.  Sam Ruby hacked together a nifty MeMeme and the result shows a clear and simple foci of attention (a post by Spoksky at last glance), FeedDemon has something in the works and Tailrank has something close.

Plazes Goes Mobile

Took a break in Mexico this weekend, literally locking my cell phone in a safe and not bringing my laptop with me.  Still catching up, but I had lunch with Felix from Plazes today (disclosure: advisor) who told me I could have tagged the location while being safe with the new Mobile client.  The world is getting granular.

Also on the MoSoSo front, I added Twttr to the top right of my blog for those interested in the messaging of the mundane.

Dandelife

I'm advising a new startup called Dandelife, which is a Social Biography Network.  TechCrunch has the scoop, but let me tell you why I think they will be successful.

Ever get that feeling why you are blogging and flickring your life away that you have lost something?  That you are telling your life's story, but it is lost in the archives and in the minds of people who are really paying attention?

There is a gap in social software for binding stories in a chronology.  For building biographies of people, places and things.  I think Dandelife serves as different object to tell stories around.  Time.

The horizontal and vertical visualizations are what makes this work: Dandelife is definately beta and Edward and Kelly are working hard on it. But when you can upload your blog and photos to start your story, its pretty powerful. Go play. And let them know how it can get better.

Socialtext Partners with Dan Bricklin on wikiCalc

Today Socialtext announced a partnership with Dan Bricklin (inventor of VisiCalc) to exclusively distribute, redistribute and co-develop wikiCalc -- the social spreadsheet. Dan brings a rich understanding not just of spreadsheets, but also open source and social software. You can thank VisiCalc, the original killer app, for the Personal Computing revolution and bringing PCs into enterprises from the bottom up. It may take some time, but Socialtext, wikiCalc and the community will develop an important contribution to Social Computing. I'd like to share how this came together, what it means and where we are going.

David Weinberger re-introduced me to Dan, whom I met at a couple of conferences. The deal was a calculated decision that took almost six months. We needed to build a shared understanding for how we can work together and work with a community. We share common principles in open source and designing social software. We see an opportunity to change the way people work together, that is different from an office on the web.

Andy McAfee defined Enterprise 2.0 as the use of freeform social software within companies: freeform in that the application does not impose structure prior to use. Since the inception of Socialtext, we have avoided the temptations of structure, not just because one man's structure is another's barrier, but because it immediately divides the world into those who can structure it, and those who cannot.

Wikis begin as a blank page, just like spreadsheets. Some think this is a weakness, but it is actually a strength -- because it asks all the right questions. How should we use this tool? What should we apply this to? What kind of buckets should we put information in? What's my role? To make a wiki work, and all IT for that matter, agreement on how to use the tool makes it work.

When Ward Cunningham invented the wiki ten years ago, one of his core design principles was a collaboration environment for experts and novices alike. This equality of usability matters, especially in the context of an enterprise. Some approaches assume that users will learn a new proprietary scripting language to create or modify structure, but programming will never be a novice activity. Writing and linking can be done by novices, and so too using a spreadsheet. Spreadsheets are the most widely adopted interface for creating and modifying structure, databases and applications.

One way that a wiki, and wikiCalc, enables social use of a tool without imposing structure is the properties of transparency and memory. In a wiki, a copy of every edit is saved with attribution. This supports trust and accountability. Given the nature of spreadsheets, wikiCalc takes this one step further, creating a revision history of every single edit to any cell -- not just when you save and the undos before. This not only holds the promise of tracking down errors, but provides an audit trail.

But spreadsheets, like other killer PC apps, were not designed for a networked world, but for a single users. Today the problem isn't just people playing email volleyball all day digging for who did what to each revision. Work is social, information can be linked and data comes in feeds. Today it isn't the problems of productivity kept personal, but the opportunity to build computing that is social.

Dan just released wikiCalc Beta as an Open Source GPL distribution. Right now you can use and modify a web-based spreadsheet of your own. We hope you will join this community. In the coming days we will release wikiCalc under a more liberal and commercial-friendly distribution. I'll let you determine the differentiating features, but the primary one isn't in the code -- it's that it is Open Source. We see great promise for an enterprise-friendly wikiCalc.

You may know Socialtext's commitment to Open Source has been a foundation of our company values. Today I can share that the Socialtext Open Source Edition, functionally equivalent to our commercial wikis for users, will be released next month at OSCON. Yes, I know it's a little odd for startups to communicate such news in advance, but there is nothing to fear, and it's part of being open with a community. Wikiwyg, wikiCalc and the Socialtext Open Source Edition will all be released under the same OSI complaint Open Source license, based upon the Mozilla Public License. For more information on Open Source licensing, see Dan's great video.

It's a delight to work with Dan. We have a lot of work ahead of us and hope you will join us.

UPDATE: The Associated Press has an in-depth profile of Dan.