Ross Mayfield's Weblog

The Rose Bowl Wiki Wednesday

January's Wiki Wednesday coincides with the Rose Bowl (USC vs. Texas).  For Palo Alto we are projecting the game and have a keg from Gordon Beirsche.  Come on by for a weird mix of tech and sports.

The Business Blogging 500, Wiki Powered

Chris Anderson (Wired/Long Tail Blog) kicks off an open research project:

Short Form: In collaboration with Socialtext, we've created a wiki that tracks which of the Fortune 500 is blogging. Check it out here. 

Jason Calacanis already did by contributing Time Warner Inc (he should know), increasing the count to 14 of the Fortune 500, or 3%:

Blogging F500 Company	Sample Blog
Amazon.com Inc.	Amazon Web Services Blog
Avaya Inc.	2006 FIFA World Cup Blog
Avon Products, Inc.	Beauty Dish
Cisco Systems, Inc.	Cisco High Tech Policy Blog
Dell, Inc	Linux Engineering
Electronic Data Systems	EDS' Next Big Thing Blog
Ford Motor Company	2005 Mustang Blog
General Motors Corporation	FastLane Blog
Hewlett-Packard Company	HP Blogs
Microsoft Corporation	MSDN's Microsoft Blogs
Motorola Inc	Motoblog: 4 bloggers & a phone
Oracle Corporation	OraBlogs
Sprint	Things That Make You Go Wireless
Sun Microsystems Inc	Jonathan Schwartz
Texas Instruments	Video 360 Blog
Time Warner Inc	AOL Blogs
The Boeing Company	Randy's Journal

Chris (and Doc) may be on to something about observing the correlation between F500 blogging and stock performance.  But at the least, this can serve as a renewable resource for informing social software adoption.

My Wikipedia Policy

I'm not sure that Scoble has the right idea about pledging not to edit their own Wikpedia page.  Wired News' latest celebrity flap points out:

In fact, Wikipedia's own guidelines caution against editing your own bio as it "can open the door to rather immature behavior and loss of dignity."

It's actually a proposed policy or guideline, and one I would vote against.  I do think it is good advice, what you could call media training, to consider that:

• When you participate on your own page, you open yourself up to debate
• What edits you make could come back to haunt you
• Don't be an idiot, or it could go on your semi-permanent record

However, several reasons come to mind for why people should edit their own pages:

• You probably have a lot of expertise about yourself and a copy of your resume
• If enough attention is given to your page, your bias will be countered
• The policy would be near impossible to enforce
• It would be easy to obey the policy, but skirt the intent, by getting your friends to edit for you

At the very least, make the practice of watching your page and use your best judgement.  For the record, I added some facts a while ago to my Wikipedia page, we will see if they remain.

See Also: Tim Bray

Crazy Ass Projections

I wouldn't call them facts, but here they are:

Blogs:

Number of blogs worldwide in 2005:
• 22 million

Number of blogs worldwide in 2010:
• Approaching 1 billion

RFID

Price-per-unit that RFID chips need to reach in order to ignite massive deployment of RFID chips:
• $.05 (the “magic nickel” according to Sclavos)

TV

U.S. household use of Tivo and Tivo-like devices in 2005:
• 3%

Projected U.S. household use of Tivo and Tivo-like devices in 2010:
• 70%

Percent of TV ads skipped by users of Tivo and Tivo-like devices:
• 79%

What may be reasonable is 1B people projecting an identity online in 2005 and blogs will have an entirely different buzzword encapsulating them.

Capitalized Punishment

Unfortunately a journalist from the Times Online in the UK took a comment off of Mark Pincus' blog that was full of hate speech on the Tookie Termination and attributed it to him.  I really feel for Mark.  It's not just bad journalism or understanding the difference between a blog post and a comment.  They should know that Mark is against capital punishment -- and rarely capitalizes his posts.

The Nature of Wikipedia and Britannica

Recent events may provide cause for setting the differences, or lack thereof, between Wikipedia and Brittanica as well as Wikipedia and Open Source. A peer review of 42 articles in Wikipedia and Brittannica shows equal serious errors and a minor difference in minor errors:

Yet Nature's investigation suggests that Britannica's advantage may not be great, at least when it comes to science entries. In the study, entries were chosen from the websites of Wikipedia and Encyclopaedia Britannica on a broad range of scientific disciplines and sent to a relevant expert for peer review. Each reviewer examined the entry on a single subject from the two encyclopaedias; they were not told which article came from which encyclopaedia. A total of 42 usable reviews were returned out of 50 sent out, and were then examined by Nature's news team.

Only eight serious errors, such as misinterpretations of important concepts, were detected in the pairs of articles reviewed, four from each encyclopaedia. But reviewers also found many factual errors, omissions or misleading statements: 162 and 123 in Wikipedia and Britannica, respectively.

A key difference is the speed of update for Wikipedia not only helps for correction, but means it is some thinig different -- something that doesn't presently claim authoritativeness:

But Michael Twidale, an information scientist at the University of Illinois at Urbana-Champaign, says that Wikipedia's strongest suit is the speed at which it can updated, a factor not considered by Nature's reviewers.

"People will find it shocking to see how many errors there are in Britannica," Twidale adds. "Print encyclopaedias are often set up as the gold standards of information quality against which the failings of faster or cheaper resources can be compared. These findings remind us that we have an 18-carat standard, not a 24-carat one."

The dynamic nature of Wikipedia does present challenges for participants and results in a different product.  There are plans to create a stable branch (basically tagging a revision as reviewed, although review processes are still experimental, while letting users continue to edit new revisions), which would result in a truely comparable product and support print versions.

My hope is the Nature article provides a proof point to at least simplify the neverending debate of quality in Wikipedia.  But before taking a break (the interesting stuff isn't metaphysical debates, but understanding the social practices that make Wikipedia work) from the disconnected-meta excersize of blogging about Wikipedia (albeit a hair above the disconnect of criticizing an Article without submitting changes), let me take on one last issue. 

The model of a stable branch is an approach borrowed from open source software development.  Recently, Cnet posted a News Analysis in search of a problem that came across as an opinion piece by the author.  The premise was that Wikipedia is often labeled as open source and the label was factually innacurate.  Open source practices have project managers as gatekeepers for quality, while Wikipedia offloads this responsibility to an open group.  A bunch of open source experts were rounded up to explain that, some speculated in agreement with the author that this may be the cause of quality issues in Wikipedia.  While the piece is an interesting read, as the CEO of a commercial open source wiki company (more critically, I am a student of the topic), I can point out some significant flaws:

• Wikis do not require centralized project management because the work product is different.  Coding software is an act of vertical information assembly, marked by the dependencies of contributions.  By contrast, Wikipedia is horizontal information assembly without dependencies.  It should be celebrated that the lack of central project management is a cause for the growth and success of the project.
• Having a central project manager for Wikipedia would also be complicated because of the lack of objective measures.  From the article: "With software, you get the benefit of there being some objective measure of a change," said Brian Behlendorf, co-founder of the Apache Software Project. "It's not a question of aesthetics. Does this fix the bug people have noticed? Does it speed up performance?"
• Wikis and Open Source share the critical attribute of The Right to Fork
• Wikis and Open Source enable anyone to contribute, but with implicit reputation giving greater weight to different contributions.  Even in Wikipedia, there is authority of participants.
• Wikis and Open Source share a common model of Commons-based Peer Production.

The definition of what is Open Source is often debated and is more likely to be settled on a wiki page than here or in the News Analysis.  Here is an unpublished chapter in wiki format on Open Source Dynamics of Wiki Practices if you would like to learn, and possibly contribute, more.

Akimbo Abimbo and Video Blogs

Akimbo is an IPTV service for video and subscription on demand that is as simple to use as Tivo.  To get content to your couch, you use your existing broadband connection (I plugged in a WiFi USB keychain and was downloading in minutes) and take advantage of 150 hours of storage. You can manage downloads with a Tivo-like interface as well as a web-browser (can't watch your content over the web, yet).

VoD has been a dream of the cable TV industry for years, and it just happened without them, almost.  Akimbo is a relatively new network that has to contend with IP regimes that have vertically integrated.  Content is relatively sparse with about 400 channels (RSS feed for what's new) -- with two notable exceptions.

Porn.  Like all great new communications technologies, porn portends future.  In this case, there are gobs of it, perhaps more than any content type -- but it does come with parental controls.  My wife and I jokingly call it the Abimbo.

Video Blogs.  Okay, this is where it gets interesting.  Today there are only four video blogs on Akimbo, but Rocketboom and Clint Sharp are pretty cool.  Subscribing to them are dead simple -- and video is still best watched on the couch. When I started seeing my friends on some of Clint's episodes I think I saw the future.  With great independent content today, the launch of the video iPod with iTunes and new Flickr-for-video startups -- there will be a wealth of video blog content next year (more on that later).  Akimbo is about to open the network -- Video bloggers will be able to submit a registered RSS feed with enclosures to get their clips on the network -- which will blow the doors wide open.

Until this happens, the utility is limited and you could end up with a big bill for premium downloads (not just porn). It does provide a good entertainment alternative, but they are stuck playing MPAA wargames.  But the enticement today is a holiday special for $69 for the player (normally $199).  The subscription service runs on the player or the Windows Media Center for $9.99 monthly or $199 lifetime.

Full disclosure: I got a player and one year subscription for free as part of the Silicon Valley 100.

live evil

While Yahoo! may be the new evil, Microsoft is the live evil.

While researching the nature of evil, I came across this:

68.23.45.217: "Are you evil?"
Jimbo Wales: "Indeed."
68.23.45.217: "Is Wikipedia evil?"
Jimbo Wales: "It should go without saying."
68.23.45.217: "Is Wikimedia Foundation evil?"
Jimbo Wales: "Worse than that, actually."
68.23.45.217: "Are you a Todo?"
Jimbo Wales: "Only on Tuesdays."

There you have it. 

However, the one thing I do know about being evil is that you can't simply be evil, people need to believe you are evil.  And odds are, beliefs about what is evil will change.  Therefore, Larry and Sergey's credo of "don't be evil" may be less about being bad and more about being static.  It's not a self-fulfilling prophecy, unless you believe that religion is marketing.

Happy Wednesday.

Structured Blogging

Structured Blogging is described by Marc Canter as a way to gain structure without people having to look at XML.  Today at Syndicate they released an open source component to structure as microformats in microcontent within social software apps. It currently works with Wordpress and Moveable Type.

Socialtext is supporting this ad hoc standards effort alongside 40 or so great companies. These collaborative initiatives, harkening back to the social software alliance, are perhaps the greatest reason for innovation in social software.

My personal take is this bottom-up approach won't degrade into Semantic Fuzz.  But only a subset of users will fill in forms to contribute metadata (readers are better at it than writers, and they are better at writing in an unstructured way and freeform tagging than the constraints of a form).  The real test is if new innovations provide a strong enough incentive for user contributions at the cost of a form.

Syndicate San Francisco

I'm playing booth babe today at the Syndicate conference in San Francisco.  Here's the wiki, naturally.  Doc blogged his keynote here.  Quote of the day so far was from Liz Lawley: "I'm headed upstairs to help my kids level up."