» tagged pages
» logout

(Feed found, click Add Page to syndicate.) Error finding feed, please try again » Find feed title

A Blog Page allows you to add entries, for news or other time sensitive postings

(Login required to save to your tagged pages.)
(or Cancel)

Make further edits, (or Cancel)

(Login required to save to your tagged pages.)
(or Cancel)

(Editing anonymously: to be credited for your changes, login or register a new account)

Change Page Permissions? Changing these permissions will adjust who can modify this page.

dland (change)
Swik Users (change)
(or Cancel)
Upload an image from your computer:
or Copy an image from a URL:
or Erase the current icon:
Icon Preview:

or Cancel

Erase User:dolander? The contents of User:dolander page and all pages directly attached to User:dolander will be erased.

or Cancel

(Editing anonymously: to be credited for your changes, login or register a new account)

other page actions:
User:dolander

User:dolander

sorted by: recent | see : popular
Content Tagged User:dolander

Freedom of Speech Doesn’t Mean Freedom from Consequences

A year ago Loren Feldman produced a controversial video called "TechNigga" which seems to still be causing him problems today. Matthew Ingram captures the latest fallout from that controversy in his post Protests over Verizon deal with 1938media where he writes

Several civil-rights groups and media watchdogs are protesting a decision by telecom giant Verizon to add 1938media’s video clips to its mobile Vcast service, saying Loren’s "TechNigga" clip is demeaning to black people. Project Islamic Hope , for example, has issued a statement demanding that Verizon drop its distribution arrangement with 1938media, which was just announced about a week ago , and other groups including the National Action Network and LA Humanity Foundation are also apparently calling for people to email Verizon and protest.

The video that has Islamic Hope and other groups so upset is one called "TechNigga," which Loren put together last August. After wondering aloud why there are no black tech bloggers, Loren reappears with a skullcap and some gawdy jewelry, and claims to be the host of a show called TechNigga. He then swigs from a bottle of booze, does a lot of tongue-kissing and face-licking with his girlfriend Michelle Oshen , and then introduces a new Web app called "Ho-Trackr," which is a mashup with Google Maps that allows prospective johns to locate prostitutes. In a statement, Islamic Hope says that the video "sends a horrible message that Verizon seeks to partner with racists."

I remember encountering the video last year and thinking it was incredibly unfunny. It wasn’t a clever juxtaposition of hip hop culture and tech geekery. It wasn’t satire since that involves lampooning someone or something you disapprove off in a humorous way (see The Colbert Report).  Of course, I thought the responses to the video were even dumber; like Robert Scoble responding to the video with the comment “Dare Obasanjo is black”.

Since posting the video Loren Feldman has lost a bunch of video distribution deals with the current Verizon deal being the latest. I’ve been amused to read all of the comments on TechCrunch about how this violates Loren’s freedom of speech.

People often confuse the fact that it is not a crime to speak your mind in America with the belief that you should be able to speak your mind without consequence. The two things are not the same. If I call you an idiot, I may not go to jail but I shouldn’t expect you to be nice to me afterwards. The things you say can come back and bite you on butt is something everyone should have learned growing up. So it is always surprising for me to see people petulantly complain that “this violates my freedom of speech” when they have to deal with the consequences of their actions.

BONUS VIDEO: A juxtaposition of hip hop culture and Web geekery by a black tech blogger.

Now Playing: NWAN*ggaz 4 Life

User:dolander: Dare Obasanjo

A List of Companies Working Hard to Screw Up My Web Experience

Every once in a while I encounter an online service or Web site that is so irritating that it seems like the people behind the service are just in it to frustrate Web users. And I don’t mean the obvious candidates like email spammers and purveyors of popup ads since they’ve been around for so long I’ve either learned how to ignore and avoid them.

There is a new generation of irritants and many of them are part of the new lunacy we call “Web 2.0”

  1. Flash Widgets with Embedded PDF Documents: Somewhere along the line a bunch of startups decided that they needed to put a “Web 2.0” spin on the simple concept of hosting people’s office documents online. You see, lots of people would like to share documents in PDF or Microsoft Office® formats that aren’t particularly Web friendly. So how have sites like Scribd and Docstoc fixed this problem? By creating a Flash widgets containing the embedded PDF/Office documents like the one shown here. So not only are the documents still in a Web unfriendly format but now I can’t even download them and use the tools on my desktop to read them. It’s like let’s combine the FAIL of putting non-Web documents on the Web with the fail of a Web-unfriendly format like Flash. FAIL++. By the way, it’s pretty ironic that a Microsoft enterprise product gets this right where so many “Web 2.0” startups get it wrong.

  2. Hovering Over Links Produces Flash Widgets as Pop Over Windows: The company that takes the cake for spreading this major irritant across the blogosphere is Snap Technologies and their Snap Shots™ product. There’s nothing quite as irritating as hovering over a link on your way to click another link and leaving a wake of pop over windows with previews of the Web pages at the end of said links. I seriously wonder if anyone finds this useful?

  3. Facebook Advertisers: One of the promises of Facebook is that its users will see more relevant advertising because there is all this rich demographic data about the site’s users in their profiles. Somewhere along the line this information is either getting lost or being ignored by Facebook’s advertisers. Even though my profile says I’m married and out of my twenties I keep getting borderline sleazy ads whenever I login to play Scrabulous asking if I want to meet college girls. Then there are the ads which aren’t for dating sites but still use sleazy imagery anyway. It’s mad embarrassing whenever my wife looks over to see what I’m doing on my laptop to have dating site ads blaring in her face. Obviously she knows I’m not on a dating site but still…

  4. Forums that Require Registration Showing Up in Search Results : Every once in a while I do a Web search for a programming problem and a couple of links to Experts Exchange end up in the results. What is truly annoying about this site is that the excerpt on the search result page makes  it seem as though the answer to your question is one click away but when you click through you are greeted with “All comments and solutions are available to Premium Service Members only”. I thought search engines had rules about banning sites with that sort of obnoxious behavior?

  5. Newspaper Websites with Interstitial Ads and Registration Requirements: Newspapers such as the New York Times often act as if they don’t really want me reading the content on their Web site. If I click on a link to a story on the New York Times site such as this one, one of two things will happen; I’m either taken to a full page animated advertisement with an option to skip the ad in relatively small font or I get a one sentence summary of the story with a notice that I need to register on their Web site before I can read the story. Either way it’s a bunch of bull crap that prevents me from getting to the news.

There are two things that strike me about this list as notable. The first is that there are an increasing number of “Web 2.0” startups out there who are actively using Flash to cause more problems than they claim to be solving. The second is that requiring registration to view content is an amazingly stupid trend that is beyond dumb. It’s not like people need to register on your site to see ads so why reduce the size of your potential audience by including this road block? That’s just stupid.

Now Playing: Pleasure P - Rock Bottom (feat. Lil Wayne)

User:dolander: Dare Obasanjo

Gnip: FeedBurner + Ping Server for Web APIs

Gnip is a newly launched startup that pitches itself as a service that aims to “make data portability suck less”. Mike Arrington describes the service in his post Gnip Launches To Ease The Strain On Web Services which is excerpted below

A close analogy is a blog ping server ( see our overview here ). Ping servers tell blog search engines like Technorati and Google Blog Search when a blog has been updated, so the search engines don’t have to constantly re-index sites just to see if new content has been posted. Instead, the blog tells the ping server when it updates, which tells the search engines to drop by and re-index. The creation of the first ping server, Weblogs.com, by Dave Winer resulted in orders of magnitude better efficiency for blog search engines.

The same thinking basically applies to Gnip. The idea is to gather simple information from social networks - just a username and the fact that they created new content (like writing a Twitter message, for example). Gnip then distributes that data to whoever wants it, and those downstream services can then access the core service’s API, with proper user authentication, and access the actual data (in our example, the actual Twitter message).

From a user’s perspective, the result is faster data updates across services and less downtime for services since their APIs won’t be hit as hard.

From my perspective, Gnip also shares some similarity to services like FeedBurner as well as blog ping servers. The original purpose of blog ping servers was to make it cheaper for services like Technorati and Feedster to index the blogosphere without having to invest in a Google-sized server farm and crawl the entire Web every couple of minutes. In addition, since blogs often have tiny readerships and are thus infrequently linked to, crawling alone was not enough to ensure that they find their way into the search index. It wasn’t about taking load off of the sites that were doing the pinging.

On the other hand, FeedBurner hosts a site’s RSS feed as a way to take load off of their servers and then provides analytics data so the site doesn’t miss out from losing the direct connection to its subscribers. This is more in line with the expectation that Gnip will take load off of a service’s API servers. However unlike FeedBurner, Gnip doesn’t actually store the user data from the social networking site. It simply stores a record that indicates that “user X on site Y made an update of type Z at time T”.  The thinking is that web sites will publish a notification to Gnip whenever their users perform an update. Below is a sample interaction between Digg and Gnip where Digg notifies Gnip that the users amy and john.doe have dugg two stories.

            ===> POST /publishers/digg/activity.xml Accept: application/xml
Content-Type: application/xml <activities> <activity at="2008-06-08T10:12:42Z"
uid="amy" type="dugg" guid="http://digg.com/odd_stuff/a_story"/> <activity at="2008-06-09T09:14:07Z"
uid="john.doe" type="dugg" guid="http://digg.com/odd_stuff/really_weird"/> </activities>
<--- 200 OK Content-Type: application/xml <result>Success</result> 

          

There are two modes in which "subscribers" can choose to interact with the data published to Gnip. The first is in a mode similar to how blog search engines interact with the changes.xml file on Weblogs.com and other blog ping servers. For example, services like Summize or TweetScan can ask Gnip for the last hour of changes on Twitter instead of whatever mechanism they are using today to crawl the site. Below is what a sample interaction to retrieve the most recent updates on Twitter from Gnip would look like

            ===>
GET /publishers/twitter/activity/current.xml
Accept: application/xml

<---
200 OK
Content-Type: application/xml

<activities>
<activity at="2008-06-08T10:12:07Z" uid="john.doe" type="tweet" guid="http://twitter.com/john.doe/statuses/42"/>
<activity at="2008-06-08T10:12:42Z" uid="amy" type="tweet" guid="http://twitter.com/amy/statuses/52"/>
</activities>

The main problem with this approach is the same one that affects blog ping servers. If the rate of updates is more than the ping server can handle then it may begin to fall behind or lose updates completely. Services that don’t want to risk their content not being crawled are best off providing their own update stream that applications can poll periodically. That’s why the folks at Six Apart came up with the Six Apart Update Stream for LiveJournal, TypePad and Vox weblogs.

The second mode is one that has gotten Twitter fans like Dave Winer raving about Gnip being the solution to Twitter’s scaling problems. In this mode, an application creates a collection of one or more usernames they are interested in. Below is what a collection document created by the Twadget application to indicate that it is interested in my Twitter updates might look like.

<collection name="twadget-carnage4life">
     <uid name="carnage4life" publisher.name="twitter"/>
</collection>

Then instead of polling Twitter every 5 minutes for updates it polls Gnip every 5 minutes for updates and only talks to Twitter’s servers when Gnip indicates that I’ve made an update since the last time the application polled Gnip. The interaction between Twadget and Gnip would then be as follows

            ===>
GET /collections/twadget-carnage4life/activity/current.xml
Accept: application/xml
<---
200 OK
Content-Type: application/xml

<activities>
<activity at="2008-06-08T10:12:07Z" uid="carnage4life" type="tweet" guid="http://twitter.com/Carnage4Life/statuses/850726804"/>

</activities>

Of course, this makes me wonder why one would think that it is feasible for Gnip to build a system that can handle the API polling traffic of every microblogging and social networking site out there but it is infeasible for Twitter to figure out how to handle the polling traffic for their own service. Talk about lowered expectations. Wink

So what do I think of Gnip? I think the ping server mode may be of some interest for services that think it is cheaper to have code that pings Gnip after every user update instead building out an update stream service. However since a lot of sites already have some equivalent of the public timeline it isn’t clear that there is a huge need for a ping service. Crawlers can just hit the public timeline which I assume is what services like Summize and TweetScan do to keep their indexes of tweets up to date.

As for using Gnip as a mechanism for reducing the load API clients put on a microblogging or similar service? Gnip is totally useless for that in it’s current incarnation. API clients aren’t interested in updates made by single user. They are interested in all the updates made by all the people the user is following. So for Twadget to use Gnip to lighten the load it causes on Twitter’s servers on my behalf, it has to build a collection of all the people I am following in Gnip and then keep that list of users in sync with whatever that list is on Twitter. But if it has to constantly poll Twitter for my friend list, isn’t it still putting the same amount of load on Twitter? I guess this could be fixed by having Twitter publish follower/following lists to Gnip but that introduces all sorts of interesting technical and privacy issues. But that doesn’t matter since the folks at Gnip brag about only keeping 60 minutes of worth of updates as the “secret sauce” to their scalability. This means if I shut my Twitter client hasn’t polled Gnip in a 60 minute window (maybe my laptop is closed) then it doesn’t matter anyway and it has to poll Twitter.  I suspect someone didn’t finish doing their homework before rushing to “launch” Gnip.

PS: One thing that is confusing to me is why all communication between applications and Gnip needs to be over SSL. The only thing I can see it adding is making it more expensive for Gnip run their service. I can’t think of any reason why the interactions described above need to be over a secure channel.

Now Playing: Lil Wayne - Hustler Musik

User:dolander: Dare Obasanjo

Some Thoughts on Google Adopting OAuth for GData APIs

Late last week, the folks on the Google Data APIs blog announced that Google will now be supporting OAuth as the delegated authentication mechanism for all Google Data APIs. This move is meant to encourage the various online services that provide APIs that access a user’s data in the “cloud” to stop reinventing the wheel when it comes to delegated authentication and standardize on a single approach.

Every well-designed Web API that provides access to a customer’s data in the cloud utilizes a delegated authentication mechanism which allows users to grant 3rd party applications access to their data without having to give the application their username and password. There is a good analogy for this practice in the OAuth: Introduction page which is excerpted below

What is it For?

Many luxury cars today come with a valet key. It is a special key you give the parking attendant and unlike your regular key, will not allow the car to drive more than a mile or two. Some valet keys will not open the trunk, while others will block access to your onboard cell phone address book. Regardless of what restrictions the valet key imposes, the idea is very clever. You give someone limited access to your car with a special key, while using your regular key to unlock everything.

Everyday new website offer services which tie together functionality from other sites. A photo lab printing your online photos, a social network using your address book to look for friends, and APIs to build your own desktop application version of a popular site. These are all great services – what is not so great about some of the implementations available today is their request for your username and password to the other site. When you agree to share your secret credentials, not only you expose your password to someone else (yes, that same password you also use for online banking), you also give them full access to do as they wish. They can do anything they wanted – even change your password and lock you out.

This is what OAuth does, it allows the you the User to grant access to your private resources on one site (which is called the Service Provider), to another site (called Consumer, not to be confused with you, the User). While OpenID is all about using a single identity to sign into many sites, OAuth is about giving access to your stuff without sharing your identity at all (or its secret parts).

So every service provider invented their own protocol to do this, all of which are different but have the same basic components. Today we have Google AuthSub, Yahoo! BBAuth, Windows Live DelAuth, AOL OpenAuth, the Flickr Authentication API, the Facebook Authentication API and others. All different, proprietary solutions to the same problem.

This ends up being problematic for developers because if you want to build an application that talks to multiple services you not only have to deal with the different APIs provided by these services but also the different authorization/authentication models they utilize as well. In a world where “social aggregation” is becoming more commonplace with services like Plaxo Pulse & FriendFeed and more applications are trying to bridge the desktop/cloud divide like OutSync and RSS Bandit, it sucks that these applications have to rewrite the same type of code over and over again to deal with the basic task of getting permission to access a user’s data. Standardizing on OAuth is meant to fix that. A number of startups like Digg & Twitter as well as major players like Yahoo and Google have promised to support it, so this should make the lives of developers easier.

Of course, we still have work to do as an industry when it comes to the constant wheel reinvention in the area of Web APIs. Chris Messina points to another place where every major service provider has invented a different proprietary protocol for doing the same task in his post Inventing contact schemas for fun and profit! (Ugh) where he writes

And then there were three
...
Today, Yahoo!
announced the public availability of their own Address Book API .

However, I have to lament yet more needless reinvention of contact schema. Why is this a problem? Well, as I pointed out about Facebook’s approach to developing their own platform methods and formats, having to write and debug against yet another contact schema makes the “tax” of adding support for contact syncing and export increasingly onerous for sites and web services that want to better serve their customers by letting them host and maintain their address book elsewhere.

This isn’t just a problem that I have with Yahoo!. It’s something that I encountered last November with the SREG and proposed Attribute Exchange profile definition . And yet again when Google announced their Contacts API . And then again when Microsoft released theirs ! Over and over again we’re seeing better ways of fighting the password anti-pattern flow of inviting friends to new social services, but having to implement support for countless contact schemas. What we need is one common contacts interchange format and I strongly suggest that it inherit from vcard with allowances or extension points for contemporary trends in social networking profile data.

I’ve gone ahead and whipped up a comparison matrix between the primary contact schemas to demonstrate the mess we’re in.

Kudos to the folks at Google for trying to force the issue when it comes to standardizing on a delegated authentication protocol for use on the Web. However there are still lots of places across the industry where we speak different protocols and thus incur a needless burden on developers when a single language might do. It would be nice to see some of this unnecessary redundancy eliminated in the future.

Now Playing: G-Unit - I Like The Way She Do It

User:dolander: Dare Obasanjo

In Defense of XML

Jeff Atwood recently published two anti-XML rants in his blog entitled XML: The Angle Bracket Tax and Revisiting the XML Angle Bracket Tax. The source of his beef with XML and his recommendations to developers are excerpted below

Everywhere I look, programmers and programming tools seem to have standardized on XML . Configuration files, build scripts, local data storage, code comments, project files, you name it -- if it's stored in a text file and needs to be retrieved and parsed, it's probably XML. I realize that we have to use something to represent reasonably human readable data stored in a text file, but XML sometimes feels an awful lot like using an enormous sledgehammer to drive common household nails.

I'm deeply ambivalent about XML. I'm reminded of this Winston Churchill quote:

It has been said that democracy is the worst form of government except all the others that have been tried.

XML is like democracy. Sometimes it even works. On the other hand, it also means we end up with stuff like this:

<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" 
  SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
  <SOAP-ENV:Body>
    <m:GetLastTradePrice xmlns:m="Some-URI">
      <symbol>DIS</symbol>
    </m:GetLastTradePrice>
  </SOAP-ENV:Body>
</SOAP-ENV:Envelope>

You could do worse than XML. It's a reasonable choice, and if you're going to use XML, then at least learn to use it correctly. But consider:
  1. Should XML be the default choice?
  2. Is XML the simplest possible thing that can work for your intended use?
  3. Do you know what the XML alternatives are?
  4. Wouldn't it be nice to have easily readable, understandable data and configuration files, without all those sharp, pointy angle brackets jabbing you directly in your ever-lovin' eyeballs?

I don't necessarily think XML sucks, but the mindless, blanket application of XML as a dessert topping and a floor wax certainly does. Like all tools, it's a question of how you use it. Please think twice before subjecting yourself, your fellow programmers, and your users to the XML angle bracket tax. <CleverEndQuote>Again.</CleverEndQuote>

The question of if and when to use XML is one I am intimately familiar with given that I spent the first 2.5 years of my professional career at Microsoft working on the XML team as the “face of XML” on MSDN.

My problem with Jeff’s articles is that they take a very narrow view of how to evaluate a technology. No one should argue that XML is the simplest or most efficient technology to satisfy the uses it has been put to today. It isn’t. The value of XML isn’t in its simplicity or its efficiency. It is in the fact that there is a massive ecosystem of knowledge and tools around working with XML.

If I decide to use XML for my data format, I can be sure that my data will be consumable using a variety off-the-shelf tools on practically every platform in use today. In addition, there are a variety of tools for authoring XML, transforming it to HTML or text, parsing it, converting it to objects, mapping it to database schemas, validating it against a schema, and so on. Want to convert my XML config file into a pretty HTML page? I can use XSLT or CSS. Want to validate my XML against a schema? I have my choice of Schematron, Relax NG and XSD. Want to find stuff in my XML document? XPath and XQuery to the rescue. And so on.

No other data format hits a similar sweet spot when it comes to ease of use, popularity and breadth of tool ecosystem.

So the question you really want to ask yourself before taking on the “Angle Bracket Tax” as Jeff Atwood puts it, is whether the benefits of avoiding XML outweigh the costs of giving up the tool ecosystem of XML and the familiarity that practically every developer out there has with the technology? In some cases this might be true such as when deciding whether to go with JSON over XML in AJAX applications (I’ve given tworeasons in the past why JSON is a better choice).  On the other hand, I can’t imagine a good reason to want to roll your own data format for office documents or application configuration files as opposed to using XML.

FURTHER READING
  • The XML Litmus Test - Dare Obasanjo provides some simple guidelines for determining when XML is the appropriate technology to use in a software application or architecture design. (6 printed pages)
  • Understanding XML - Learn how the Extensible Markup Language (XML) facilitates universal data access. XML is a plain-text, Unicode-based meta-language: a language for defining markup languages. It is not tied to any programming language, operating system, or software vendor. XML provides access to a plethora of technologies for manipulating, structuring, transforming and querying data. (14 printed pages)

Now Playing:Metallica - The God That Failed

User:dolander: Dare Obasanjo

Splunk: A Software Enabled Platform for Data Search

When I first met with the team at Splunk, they were working away on building a system that could accurately track a transaction as it traversed the entire enterprise stack. If the transaction broke somewhere along the way, their software could help IT discover the cause of that failure. While it was clearly a pain point for some businesses, there was no clear customer and the value proposition was a relatively hard one to articulate. But the technology they were building created a whole lot of intelligence built on the fumes of the data center (namely the log files). I was interested in what they were doing, but not interested enough to fund them. One day I got a call from Michael Baum, CEO of Splunk. He told me that they had "figured it out" and that we should meet up. I was certainly game to hear what they had figured out and we got together again a short time later.

So what had Splunk figured out? They had figured out that if they could track, manage and correlate log files across the entire data center in near real time, that they could create the killer IT Search Engine that would allow an end user to see into their enterprise stack in a way never before possible. The Splunk guys showed me a very simple example using Voip data and how one could track all systems that touched a particular extension by simply searching for that extension in the Splunk engine. I was an instant believer -- it was clearly a better way to manage the massive amounts of IT data that exist in enterprises today. I invested in the Series A and the Splunk team got to building the software that they had envisioned.

A short time after investing in Splunk, I was meeting with a group of managers from one of August Capital's biggest Limited Partners (the folks who invest in our fund). I was describing for them what Splunk was planning to build and they asked me "so what's the market size for that?" I quickly answered as best I could -- "I have no idea." Needless to say, this was not the most satisfying answer they had ever received and they stared back at me with a look that suggested perhaps I should come up with a better answer. But the reality was that I didn't have a better answer. Not because it was unclear if there was any market for what Splunk was building. But, more importantly, because once Splunk had built their search engine, it was unclear what market they would go after. I explained to my investors that Splunk had a number of multi-billion dollar markets in which they might play (management, compliance, BI, security, capacity planning, development, etc.) and the only question was which ones they would choose to go after first.

That conversation with my Limited Partners was over two and a half years ago. And since that time, the Splunk team has built precisely what they promised -- a large-scale, high-speed search technology for your data center. But despite the fact that Splunk's software has been downloaded by over 100,000 users and despite the fact that there are now more than 350 paying enterprise customers (including 21st Century Insurance, BEA, British Telecom, Catholic Healthcare West, Chicago Mercantile Exchange, Comcast, Dow Jones, FedEx, Fiserv, GE Consumer Finance, LinkedIn, Mantech, Mozilla.org, NASA, Shopzilla, Telstra, U.S. Department of Energy, U.S. Department of Justice, U.S. Department of State, Vodafone and Yahoo!), I would still have a tough time answering the question posed by my Limited Partner.

Splunk has not built an application. Nor is Splunk merely selling software. Splunk has created a software enabled platform that continues to be extremely broadly applicable. Is Splunk mission critical when it comes to maintaining availability of large scale enterprise systems? Yes. Is Splunk invaluable in the fight to maintain the security of your data center? Yes. Does Splunk uniquely simplify the process of data compliance? Yes. Can Splunk help you dig into your data and analyze it like no other solution? Yes. But, frankly, that's just the tip of the iceberg -- once you are able to query individual pieces of data across your entire data center in real time, the applicability of the platform is limited only by the creativity of its end users. And those end users are driving value back into the platform, creating applications we hadn't thought of before.

So what is the market for Splunk? i still couldn't say for certain. But I can tell you one thing -- it is awfully big. And in the venture business, that's big enough.

User:dolander: Venture Blog

The Ramblings of an Itinerant VentureBlogger

Hello VentureBlog readers. Are there still any of you out there? My hat is off to folks like Fred Wilson who blog religiously on a daily basis. While I post a thing or two daily to my personal Vox blog, that's usually a picture, a quote, a video. Fully formed sentences are a bonus on my Vox blog. But what it lacks in structure and depth, it makes up in cute pictures and video of my kids. Sure, my mom is willing to read VentureBlog and pretend she gives a crap about liquidation preference because I'm her son, but when it comes to cute pictures of her grandchildren, she'll check that blog with OCD consistency. My mom's desire for more info on her grandchildren, however, is no excuse for neglecting VentureBlog. And so I return to the hallowed pages of VentureBlog (I hope it is more hallowed than hollow).

Do you ever read a newspaper column and get annoyed when it is just a bunch of little snippets without any overriding theme or structure. Lazy, lazy, lazy. Well, for the sake of easing back into VentureBlog, this post is going to smack of those lazy columns. Sorry about that. I'll try to do better next time.

First things first, welcome to the New and Improved VentureBlog. Do not be confused by its near identical appearance to the old and not yet improved VentureBlog (particularly if you are reading this via my RSS feed :)). VentureBlog is now running on MT4. There's been a ton said out there about MT4 -- lots and lots of praise for its depth, simplicity and beautiful new UI. I second all of that (and not just because I'm an investor). It is a pleasure to use and the MT team deserves a pile of credit for continuing to raise the bar for blogging software.

Not surprising to most of you, I'm sure, I spent the beginning part of this week at the TechCrunch40 conference. While folks like Walt Mossberg, Kara Swisher, Chris Anderson, John Battelle, make it look easy, the conference business is anything but. It takes a pile of planning, a huge amount of leg work, some real personality and a fair bit of luck to make a new conference work. But Mike, Jason and Heather pulled it off in a big way. The TechCrunch40 had the necessary mix of startup energy, investors trolling the halls, journalists chasing down stories, and ice cream bars. So congratulations to them for a great conference. If you couldn't make it to the TechCrunch40 and want to get a feel for the energy in the halls, Craig and I recorded a VentureCast show there that I am sure Craig will be posting shortly.

While I was at the TC40 event, I bumped into Michael Copeland. Michael is a great guy and an equally great journalist. It saddened me to see "Fortune" on his name tag. I don't have any problem with Fortune. I like the magazine and I'm thrilled that Michael is writing for them now. But it was just a reminder of the terrible decision by Time Inc. to shut down Business 2.0. The crew at Business 2.0 worked hard to understand and articulate the underlying trends that continue to power this round of Internet innovation. They weren't content to simply write about the fads after they had been outed by the blogosphere. They dug in. I was lucky enough to attend a couple of the Business 2.0 gatherings of their "Next Net" companies. They were lively debates orchestrated by Erick Schonfeld and the rest of the Business 2.0 editorial team. It is a shame that there won't be any more of those gatherings. Maybe Michael can carry the tradition over to Fortune. [I wrote this post on a plane this morning and then read this evening that Erick Schonfeld has joined TechCrunch as Co-Editor with Arrington. That is fantastic news for TechCrunch -- Congratulations to Erick, Mike and Heather.]

As is par for the course, I didn't actually spend much time in the conference hall during the TechCrunch40. But during one interesting session in which Marc Andreessen and Dave Filo were explaining to Chad Hurley how they invented the Internet, I peaked in and saw Eric Savitz in the front row blogging away madly. Have I ever mentioned on VentureBlog how incredibly great Eric Savitz is? He really is. Unfortunately, because he writes for Barrons he blogs mostly about the public markets. Somehow he managed to even make posts about earnings calls entertaining. And when he is blogging at things like TechCrunch40, his stuff is just awesome. If you haven't read Eric's blog, go check it out now. It has been really impressive how quickly his blog has become one of the standard bearing tech blogs.

As a bookend to Shameless Self Promotion Month, I should mention that over the summer I funded a great company called Jaxtr. Jaxtr is what I like to think of as "social telephony." You can put a Jaxtr widget on your blog, social network, eBay listing, etc. and enable click to call. Jaxtr then establishes a virtual phone number for you that is local for the person calling -- if someone is calling you from India, they get a local India number, same in Europe or China or Iowa. And because the number is virtual and lives on top of a voip platform, you can then control the destination of those incoming calls. It can come to your cell phone, your home phone, Jaxtr voicemail, whatever you prefer. Better yet, you can determine the path of the call by individual. These features are just the beginning for Jaxtr, which will increasingly take advantage of voip and the social graph (oh crap, I swore I wouldn't use that term) to create more control, leverage, cost efficiency and fun for users. I'm thrilled to be involved with the company (along side many of the earliest Skype investors). Incidentally, I did get a fair number of comments and emails telling me that Shameless Self Promotion Month sucked and that I should cut it out. Fair enough. We now return to our ordinarily scheduled program of pontification and sarcasm.

I guess that's enough for now. Sorry for the rambling. It is good to be back.

User:dolander: Venture Blog

Sick Blogging: Graphing Social Patterns and DonorsChoose Blogger Challenge

One of the good things about being home sick is that you have time to blog. So let me catch up on a couple of quick things.

Graphing Social Patterns Conference
: The first one is that my friend Dave McClure has organized an interesting conference that is coming up called "Graphing Social Patterns: The Business and Technology of Facebook" The event is all about Facebook as a platform for other businesses and will have some great speakers like Tim O'Reilly and Reid Hoffman. The Facebook phenomenon is sweeping Silicon Valley and this is the first event to try to put it in some perspective. The conference is in San Jose from October 7th through 9th and you can REGISTER HERE to get a 25% discount on the conference (because VentureBlog isn't just about information, it is also all about value). Also, don't miss the VideoEgg conference called App Camp on how to build a real business on Facebook. VideoEgg have become The experts on rich media advertising and monetization of social media. Given that, App Camp will be a very interesting discussion of how to actually make money on Facebook. I have been saying for a long time that I believed social networking (or, the "social graph" in today's parlance) would become a core piece of infrastructure in all sorts of applications and the Facebook platform is the perfect extension of that observation -- now application providers can outsource the entire social networking infrastructure to Facebook and focus on the overlying application. It will be interesting to see how these applications and monetization continue to evolve.

DonorsChoose Blogger Challenge: The second random snippet of this fine sick day is Kara Swisher's quest for lunch with Jerry Yang. According to Kara, the Yahoo PR machine won't give her direct access to Jerry, so she is working on an end run to the problem. In support of the DonorsChoose blogger challenge, Yahoo has offered a lunch with Jerry for the blogger who gets the most donors to give money to schools through DonorChoose.org. Kara is hoping to earn that honor so that she can dine with Jerry and, no doubt, put it on video tape. The DonorsChoose blogger challenge is a fantastic way to help out worthy school projects. But since I'm late to the challenge, I may as well lend my support to Kara, who has chosen some great projects to fund. So if you are interested in contributing to some worthy causes, click HERE to get to Kara's DonorChoose page.

Hope you all are healthy. I strongly recommend getting flu shots. Trust me. Get the shots.

User:dolander: Venture Blog

The Lobby Conference

I spent this week in Hawaii at a conference I hosted called The Lobby. The idea behind The Lobby was to gather together a fantastic group of people with a shared interest in the future of media and facilitate a conversation among the participants. There were no speakers on stages, no panels addressing broad themes, no big name mucky-mucks invited to draw crowds, just a fantastically engaged and engaging group of subject-matter experts eager to connect and talk. Everyone who attended would have been those speakers, those panelists, those mucky-mucks at other conferences, but this conference wasn't about being the center of attention -- it was about participating. And man did everyone participate. From dawn to well-past dusk, the folks at The Lobby devoured the conversations. The energy was frenetic, a veritable Type A Power Plant. By the time I got on a plane to head home this morning I was literally spent. I suspect it will be weeks before I'm fully recharged. And I will take the next 12 months to follow up on everything I've learned, connect with everyone I've met, and prepare for next year's Lobby conference.

The Lobby would never have happened had it not been for the encouragement, expertise and friendship of the incredible Lia Lorenzano-Kennett. Lia is the high priestess of conference production. She was one of the first Producers of the Apple Developers Conference, ran Demo and Agenda, was the President of IDG Executive Forums, and worked with Walt and Kara to create the phenomenal All This Digital conference, of which she still is the Producer. When I first met with Lia to talk about my idea for The Lobby, she told me that she had always wondered what made a great conference -- was it the speakers or the audience? And she had always wondered what was the answer to the age old conference chicken and egg problem. Was a conference made great by the people who attended? Or did great people only attend great conferences? As The Lobby wound to a close this week, Lia turned to me and said "so now we know -- it's the chicken." And man were there some great chickens in attendance at The Lobby.

I would love to tell you more about The Lobby, but that's about all that I can say without breaching my own terms of the conference. The Lobby was from the very outset touted as an off the record conversation about the future of media. When attendees registered for the conference, they confirmed that they would not report on anything said by the other attendees. My theory was that if everyone felt comfortable that their discussions and conversations would not be reported beyond the confines of the event, people would speak more freely and we would all get a lot more out of it. I still believe that is true, although I am not certain how realistic it is to assume that in this day and age there is such a thing as off the record. It is too easy for information to be disseminated, either with attribution or anonymously. And what constitutes "off the record"? Is it still off the record if you report what was said at the event but don't attribute it to anyone in particular? Is it still off the record when you Twitter "having great conversations at The Lobby" or "Will sell bead clue for $100"? Is it still off the record when you post a public photo of the event to Flickr or Photobucket? What if that photo paints another attendee in a less than flattering light? Is it off the record if you simply report that you are attending The Lobby, even if you never mention more than the meals you had at the event? For what it is worth, my goal was to keep the content of the conversations off the record (attributed or otherwise, during sessions or at the bar, to a few or to thousands). My slogan for The Lobby was "the content is the conversation" -- off the record was about promoting open discussion, not creating a secret society. But it is a tough line to draw and I will continue to ponder these questions in anticipation of The Lobby 2. Until that time, I look forward to continuing to participate in the rapid evolution of digital media and hope that The Lobby has played some small role in that evolution.

User:dolander: Venture Blog

Venture Capital in China

For the last several years there has been a lot of talk on Sand Hill Road about investing in China. To a certain degree there has been a lot of talk about all the BRIC countries -- Brazil, Russia, India and China. But the most excitement is clearly around China. (Interestingly, while India is a relatively close second, I have yet to hear of a single Bay Area VC exploring investment in either Brazil or Russia). Drawn by huge markets and a rapidly expanding economy, American VC's are heading to China to stake their claims. Go East young VC's. Go East.

Venture Capital investment in China has not, however, been a headlong dive. Bay Area VC's seem to be sending over exploratory parties. By way of example, David Chao from Doll Capital has been in and out of China for some time. Now a number of his partners are getting in on the act as well. Paul Koontz from Foundation Capital spent a year in China exploring the market. And perhaps the best indicator that the Chinese market is hot is Dick Kramlich's pilgrimage to China this year. Kramlich is one of the founding fathers of Sand Hill Road -- a 25 year veteran of the venture capital business. Not one to miss out on a big opportunity, Kramlich has headed over to China for 2008 to catch the wave of entrepreneurship and, perhaps, some of the Beijing olympics. Chow, Koontz and Kramlich are not the only US VC's headed to China by any stretch of the imagination. But these high profile forays into the Chinese market are excellent indicators of the level of interest in the market.

It is hard not to be intrigued by the Chinese market. With 1.3 Billion people, you don't need a huge amount of penetration to hit big numbers. One percent of the Chinese market is 13 million people. As they say, if you are "one in a million" in China, there are thirteen-hundred people just like you. What's more, the Chinese government anticipates that approximately 300 Million people will move from the countryside to urban centers in the next decade -- that's the same number as the entire population of the United States. The combination of massive aggregate numbers, rapid urban migration (and the commensurate increase in wages) and relatively low concentrations of modernized business processes, suggest a market ripe for investment. And that is precisely the conclusion many of my brethren on Sand Hill Road have drawn.

Given all that, I was anxious to check out China for myself. And right before the new year, I had the good fortune to do just that -- I accompanied a group of Stanford Business School students on a ten day study trip to China. We met with senior executives from companies like China Telecom, Alibaba, GM China and Bao Steel, as well as senior government officials and party leaders (yes, it is still a Communist country). But the most interesting discussions, to my mind, were with the leading private investors in China. (Because my meetings with these private investors took place as part of a study trip, there was no expectation that I would blog about the content of our conversations -- thus, I have decided to exclude the names of the specific investors so as not to violate any confidences they may have reasonable expected.) These investors gave a surprisingly candid view of venture capital throughout the country -- the good, the bad and the ugly.

To the mind of the Chinese investing community, the market dynamics described above well outweigh the risks of investing in the current environment. Huge markets with lots of business white space provides for numerous opportunities for economic gain. While American investors are busy debating the degree to which the US startup market is saturated, Chinese investors are having trouble keeping up with the inflow of opportunities. The opportunities in China seem unbounded, making foreign investors starry-eyed. But despite the glories of the Chinese market -- and there is no denying that the demographic trends in China are glorious -- I heard more than enough from Chinese investors to scare me away from the market.

As an initial matter, the biggest challenge that investors find in building Chinese startups is identifying great entrepreneurs. Because there has been all but no startup culture prior to a handful of years ago, there are essentially no seasoned entrepreneurs. A few native Chinese business expats are returning from abroad to take advantage of China's increasingly open economy. But those numbers are de minimis and do nothing to staff the rest of the enterprise. Meanwhile, Chinese executives have been trained to function in a business culture of bureaucracy and Party connections -- not the fast-paced, fluid environment of the startup world. The investors with whom I met lamented the lack of qualified executives and warned about the significant challenges of doing diligence on Chinese entrepreneurs.

The second challenge with entrepreneurship in China is grounded in the laws of China. The legal structures needed to support a vibrant startup economy are, at best, embryonic. Neither entrepreneurs nor investors are particularly well protected by the Chinese legal system. One investor with who I met on my trip described a recent situation in which he funded an entrepreneur, only to have that entrepreneur turn around and leave for business school months later. The entrepreneur assured the investor that he would be better situated to make the business a success after the two years of school. The investor had no recourse as his money left the country with the entrepreneur. In another instance, an investor backed an entrepreneur in a business that thereafter appeared to be failing. However, a couple years later when the same company started thriving, the entrepreneur informed the investor that it was not the company he had backed. The investor was incredulous. He told the entrepreneur that it was the very same company with the same team and even the same name. The entrepreneur assured the investor that it was, in fact, a different company and that he had not invested in this successful company, his investment was in the previous failed venture. Despite the obvious deception, the investor told me that he again had no legal recourse.

In many ways, venture capital in China is like the wild west. There are big opportunities, but they are not well defined and capturing their full value may well require manipulating the law to your own devices. One investor with whom I met described entrepreneurship in the United States like a zoo and entrepreneurship in China like a jungle. In the United States, he said, while there is always a lion next to you with sharp claws, driven by self-interest, there is a cage between you and the lion to keep you safe. You can count on the cage to protect you from unreasonable or illegal behavior. In China, on the other hand, there is no cage between you and the Lion -- if you don't take great pains to protect yourself from the self-interested behavior of the lion, you are going to get bitten. Case in point, one Chinese executive with whom I met on my trip described how he was able to leverage his dominant market position to force his competitors to sell at a discount. What's more, the entrepreneur described with pride that once he had bought up all of his competition, he was able to raise his prices three-fold.

Yet another significant challenge for United States VC's seeking to invest in China is the government itself. While China appears to be making huge market-driven strides in its economy, there remains a significant wild-card in all business transactions -- the Communist government. On my trip it was repeatedly pointed out to us that government officials don't make laws, Party leaders do. The government officials are tasked with managing the bureaucracies of their localities, but the party leaders are tasked with making the decisions. The Communist Party single-handedly makes all of the rules in China. For example, by mandate of the Party, no Chinese financial institution may be majority-owned by foreign investors. Thus, the fasted growing segment of the Chinese market is off-limits to foreign investment. What is to stop the Chinese government from making similar mandates in other market segments? This lack of predictability of the fundament legal underpinnings of business in China is sufficient in and of itself to make me take pause.

I thoroughly enjoyed my visit to China. The shear scale of Beijing and Shanghai was absolutely stunning, as was the velocity of the growth in both cities. And the extraordinarily candid conversations we had with Chinese business leaders and Party officials was both surprising and invaluable. But rather than leaving China emboldened to invest in their great economy, I returned to the United States surprised that my fellow VC's could accept the risks inherent in investing in China. I could not. And I don't anticipate that changing any time soon.

User:dolander: Venture Blog

Entrepreneurship for Lawyers

I was recently reading some old posts on Venture Blog and couldn't believe how short they were. One might call them pithy. Or one might also call them lazy. Either way, they were short. I should really try that again.

I have been teaching a class at Harvard Law School this winter semester called Venture Capital and the Technology Start-up with John Palfrey, the Executive Director of the Berkman Center. It is really fun to be back at the law school and working with John. I have been blown away by the energy that the law students are bringing to the topic of Entrepreneurship and Venture Capital. Sadly, I never had a VC or Entrepreneurship class in law school. Lets see, I had torts, contracts, criminal law, federal courts, administrative law, property, intellectual property, corporations, securities regulation, constitutional law . . . but no entrepreneurship. Then again, I don't know that I would have had the sense to actually take a VC or Entrepreneurship class back then. So its presence would have been wasted on me.

Today my students had to actually pitch business ideas to real live VCs from the Boston area. And they did a great job. As I was discussing with them how to think about company building and pitching, it struck me that much like the law, building great companies is all about applying precedent. Only, instead of the applicable precedent being case law in this instance, the applicable precedent is a business case. Pitching your business is all about finding the right business analogs and describing how they apply to the company you're building (e.g., "we're the Amazon.com of funeral supplies."). That isn't so different from finding the right case analogs and describing how they apply to the lawsuit you're defending. So there may be hope that we lawyers are able to figure out this entrepreneurship stuff yet.

User:dolander: Venture Blog

Pitching a VC -- The Basics Revisited

When I first started writing VentureBlog, I used to talk a lot about entrepreneurship. At the time, not a lot had been written about pitching VCs or the Venture Capital process, so there was lots of virgin territory. Since that time, dozens of VCs have started blogging and much has been said about what it takes to get a VC down the isle. Bits and pieces here and there -- a good Google archeologist can pull it all together. But having spent the week pontificating about PowerPoint and the likes, I've decided to take one more swing through the basics of pitching a VC.

As I thought about the process of pitching a business, it struck me that no matter what the stage, the information was essentially the same. A good elevator pitch contains the same content as a good executive summary contains the same content as a good PowerPoint contains the same content as a good business plan. The distinction among these business descriptions is not the substance, it is the degree to which the essential elements are fleshed out. Each document contains slightly more detail than the preceding.

Elevator Pitch --> Executive Summary --> PowerPoint --> Business Plan

This makes good intuitive sense. There is no reason that the things that are most compelling about your business would change based upon the nature of the business description. Nor would an investor be interested in different things by virtue of the form that description takes.

What, then, are the essential elements that make up a good PowerPoint, a persuasive elevator pitch, a compelling executive summary? I have no doubt that VCs will differ somewhat on the precise list, as well as the order and the emphasis. But at its core, I believe that a successful business description should include the following elements:<