Real-Time Web: It’s about the publishing, not the consumption

So much of our attention on the real-time web focuses on consumption — the notion that we want more information, faster. This was indeed the focus of our discussions at GigaOm’s “What Comes Next” session earlier this week (see my notes).

But then we all complain about information overload and continuous partial attention. At the very same Bunker session, alpha geeks complained of the Facebook and Twitter overload problem.

I’ve become convinced the real reason people love the real-time web isn’t for the glut of information it produces, but instead because it makes publishing more fun and enjoyable.

It’s all about the near-instant gratification from an “@” reply, or retweet, or a “like” on Facebook. Publishers (and by publishers I mean people who blog, Tweet, foursquare, etc) love this.

Blogging provided some of this in much earlier days, when it was a means of expression for a much smaller, insular, alpha-geek community  — but with a much higher degree of latency. You might write a blog post and  get a comment, or trackback, several hours (or days) later. But this kind of gratification fades over time — in part because so much of what we publish is so perishable — so services like Facebook and Twitter which provide more immediate feedback loops have come to dominate.

The response rate doesn’t have to be high, or targeted, with real-time. It has to be timely. Three or four immediate replies or retweets are ample reward — one can feel heard, listened to, a part of something bigger.

The fact that it’s all about the publishing, and not the consumption, is readily apparent to anyone who digs deeper into Twitter stats. Look at the average click-through rate of a link passed through Twitter by an A-list Twitterer, and you’ll be shocked how low it is. Folks with a million followers are lucky to get a couple of hundred, maybe a couple thousand, people clicking on a link.

All of which is to say: if I were an investor, I’d stay away from companies focused on creating the best possible way to consume “real-time” information. The truth is, other than stockbrokers and traders and people in the news business, most of us don’t really have a need for that. But, there is probably lots of money to be made still from services that use real-time feedback loops to get people to participate, publish, and contribute to a service or platform.

Making Sense of the Data Explosion

This morning I was at my pal Om‘s What Comes Next for the Web — Om pulled together 40-50 people in San Francisco to talk about the combination of persistent, ever-present broadband networks and more powerful mobile devices that connect to those networks, and how we all make sense of the data explosion those two things have unleashed.

I sat in the back of the class and kept mum — I instinctively reprise my lame college and grad school behavior in those settings. … That said, I had a number of thoughts and reactions during the session, and thought I’d jot two of them down here to keep the conversation and thinking going:

Emotional and Qualitative Metadata

Marc Davis led a discussion about context — creating more standardized ways to put “who, what, where, when” metadata around media objects and other data that we create. There was much discussion of the use of geo-data in particular.

Thinking about this in the context of Vodpod (yes, I’m narrow-minded that way), I realized that this kind of “factual” metadata is often less important to us than “emotional” or “qualitative” metadata (some folks brought up emotional metadata in subsequent discussions, but the discussion on this was all too brief).

With video, the single most important piece of metadata is: is it any good? By “Good” I mean is it funny, or informational, or relevant, or beautiful.  And of course the answer to that for any given video is highly contextual (who is asking? who is answering?). We’re thinking about this a lot at Vodpod — and of course the fact we’re a community of video curators helps us — but creating interoperable ways to share this kind of qualitative metadata is a good subject for a follow-on discussion.

Serendipity Engines: Radio as a Guide?

Kevin Marks led a discussion about serendipity, and if there are ways for us to engineer and design for serendipity using all this new data. I kept turning my thoughts to the obvious and trite — but very best — example of serendipity by design on the web that I’ve seen so far — the radio offerings from Last.fm and Pandora. As I’ve written before, I’ve long been a big last.fm fan, and the appeal for me of that service is the radio feature — I invariably discover great new music through it every time I use it.

There have got to be some lessons learned from both of those services (one is top-down, one is bottom-up in how it determines which music to “recommend) that we can use.

And it also occurred to me that radio in general is an excellent format for serendipitous discovery, and that perhaps part of Twitter’s appeal for many of us is that it is a bit like radio for short-messages. Indeed, it was explicitly designed that way.

Maybe the radio analogy — in an extremely loose way, more psychological and state-of-mind than literal  — is a good one for those who seek to architect a bit of serendipity. It seems to me that when we’re explicitly receiving things — via the radio, or a Twitter stream — we’re more open to those moments of serendipity.

New URL, New Look & Feel, and One Blog Home

I’ve combined my WordPress and Typepad blogs, and am hosting both on WordPress.com now (thanks to the nifty export-import capabilities of both platform) at the mhallville.com address.

Historically, I’ve maintained two distinct blogs. The first was on Typepad, and eventually became an outlet for mostly political posts. I started my WordPress blog in late 2005, and have written mostly about technology and bikes there. Because the election is over, and I’m writing less about politics, it was becoming a pain to maintain two blogs. And given politics is no less important to me than technology, why keep the two separate.

I’ve also changed the look and feel, and am using WordPress’s relatively new P2 theme. The goals are to make the blog a little more conversational and to put up shorter posts,  more frequently, and I think the P2 format and layout encourages and rewards both of those things.

On Immigration and Silicon Valley

TechCrunch offers a guest post today by Vivek Wadhwa titled Beware The Reverse Brain Drain To India And China.

It caught my eye.

Wadhwa suggests that many younger Chinese and Indians who have come to the United States to work in the technology business are returning to their native countries, and provocatively concludes:

It is very possible that some of the smart Indians who sat in the room with me holding their hand up on Columbus Day will start the next Google or Apple. Many of them will build companies which employ thousands. But the jobs will be in Hyderbad or Pune, not Silicon Valley. (emphasis mine)

Really?

Wadhwa essentially implies: if smart Indians and Chinese leave, well, there won’t be many smart people left here in the Bay Area. “The jobs will be in Hyderbad or Pune, not Silicon Valley.

I don’t pretend to possess a definitive history or deep understanding of Silicon Valley. But it seems to me that the genius of the place is that it attracts interesting, smart, able people from all over the world and all over America, and from many diverse ethnic and racial backgrounds. Not just from one or two countries.

To the folks going home to Shanghai and Pune and Bangalore, best of luck. Yes, our economy is a mess, but I suspect some smart kid from Romania, London, Mexico, Brazil, Cleveland, Alabama, or Vietnam will arrive to take your place. And Silicon Valley will go on.

Follow

Get every new post delivered to your Inbox.