Google launched its version of integrated real-time search, one of a number of impressive product demos given, at a press event this morning. It's much better than what Bing and Yahoo! have done, but it's still just the beginning of a full-scale engagement with the real-time web. To provide further context to this discussion, we're rerunning a post we wrote in seven months ago, titled "3 Models of Value in the Real-Time Web." We hope you find it useful and interesting.
Hey web DJ. Reach into your magic bag of search tools and pull out a big result - dripping with related ephemera born just moments ago. Those could hold the grain of information you're really looking for, or they could sparkle with data that changes your course of action in unexpected ways.
Alert! Another factor has emerged, elsewhere on another site. You said you wanted to be told, right away, about any online artifacts that crossed a threshold of popularity within a certain group of people in your field. That has just occurred, so it's time to watch the replay of how it got so hot, evaluate its usefulness and decide whether to bring this emergent phenomenon into the work you were doing before you were interrupted, drop the former for the latter or return to your original focus. How would you like this to be your job description? It could well be - if the red hot Real Time Web keeps showing up on sites all around the internet.
The Real Time Web is coming so fast we've hardly had any time to think about it yet. So let's do that, shall we? The two hottest technologies online, Twitter and Facebook, are fast integrating real-time delivery of activity streams to their users. Paul Buchheit, the man who built the first versions of both Gmail and Adsense, says the real time web is going to be the next big thing. Buchheit's FriendFeed is a key point of innovation in real time. Social media ping server Gnip promised to turn everything online into Instant Messaging-style XMPP feeds, and though that's been put on hold in favor of more immediately clear value - we've still got our fingers crossed. Our investigation of companies like Bit.ly and OneRiot this morning turned up even more big news that's right around the corner for the Real Time Web.
But what's the point? What's in it for us, as users? We offer below three models of value that we suspect will be found in the Real Time Web. They are the concepts that underly the vision described above at the top of this post. Those concepts are Ambiance, Automation and Emergence. This is just an initial exploration of ideas, reality will undoubtedly be more complicated shortly. We welcome your participation in thinking about this part of the fast-approaching future of the web.
The web is made up of web pages linked together, but hovering around many of those pages are now social media signals like blog posts, bookmarks, tweets and other URLs that refer to a page but aren't visible when you're looking at it. The same is true for concepts. Most of us use Google to find pages about things we're looking for, but Google prioritizes historical inbound links and the text on pages.

In the above image you can see a custom search engine we use here at ReadWriteWeb, with Mark Carey's Twitter on Google greasemonkey script running on top of it. If you want to know about streaming video, Forrester's, Jeremiah Owyang, has a running list of vendors in the space (1) and that's where you want to start - but wouldn't you like to know about the very freshest (2) live streaming vendors on the market as well? That's what people are talking about, in real time, on Twitter.
In our experience these Twitter augmented search results are valuable because they are up to the minute - but sometimes they are also just better.
Someday you'll be able to discover Owyang's list and be prompted to view the most recent, the most authoritative and the most "socially relevant to you" conversations about the same concept going on all around the web. People are working on all of that and as research-lovers we hope they succeed.
The point is that no matter what you're doing on the web, there are valuable related activities going on elsewhere - probably simultaneously. Exposing those is exciting.
We probably should have started out with this, but what's the most obviously valuable example of clear value in real-time information delivery in recent internet history? Blackberry and the push email!
We tend to assume that the real time web is something we'll be looking at constantly, because it's constantly bringing up new information. That doesn't have to be the case, though. The real time web could very well just do its thing and notify us, in real time, of important events. Thresholds crossed. Simple changes made.
For example, when the already controversial Google Chrome Terms of Service were changed again last December, I got an SMS sent to my phone notifying me that it had been changed. I was able to jump online, grab a screenshot of the changes from the application that was monitoring the document and report on the change before anyone else.

I certainly wasn't watching for the change. A robot was doing that for me and let me know about the change in near real time. It was pretty awesome, but it wasn't real time and the services I patched together to do it are all marginal enough that they often don't work or are very late. Put real time at the center of the web and we'll be able to automate all kinds of information monitoring. At first it will be a competitive advantage for those who use it strategically; then it will just change the game, become standard practice and require competitive knowledge workers to come up with something else that's new.
Read the last section of this post and the comments readers left here: 3 Models of Value in the Real-Time Web
Comments
Subscribe to comments for this post OR Subscribe to comments for all ReadWriteWeb posts
Thanks for the article. I love this little gem here, "According to PostRank, fully 97 percent of all content published online doesn't have any audience engagement at all.". Do you see services using PostRank's API to help dice up and deliver fresh, relevant content under their own application anytime soon?
I have been looking at blog engagement and there are several factors driving the loss of engagement least of which is content. The ways and means used to share and find content have changed. Postrank did an excellent post here:
http://blog.postrank.com/2009/11/measuring-engagement-of-the-social-web-2007-2009/
Great post Marshall. Good to see constructive thinking about what and how the "real-time" web is actually going to affect us in the long term. Aka, getting past the technical aspects of the discussion.
Migrating towards the real-time use cases changes the game from a number of angles: when the story is just a few seconds (or minutes) old, analytics on that specific story are not very useful. Now you're into a different game: you have to employ predictive instead of reactive models to trigger events, or, as you pointed out, specify thresholds.
Both of these models is something we've been giving a lot of thought to at PostRank. As someone has already pointed out, 97% of all the content we see on a daily basis falls on deaf ears, which is also why in our streaming / real-time content API's were innovating on the meta-data not just on speed of delivery. At the end of the day, everyone is going to get content in a matter of seconds, and that's not the interesting part. The interesting aspect is: what are you going to do with that data when it's just a few seconds old?
Trends and outlier detection, historical performance models, keyword and threshold models - this is where the real innovation needs to happen in the context of the real-time web.
(Definitely something we've been working on at PostRank: http://data.postrank.com)
Migrating towards the real-time use cases changes the game from a number of angles: when the story is just a few seconds (or minutes) old, analytics on that specific story are not very useful. Now you're into a different game: you have to employ predictive instead of reactive models to trigger events, or, as you pointed out, specify thresholds.
I'm playing around with real time streams. For this I created a prototype application (http://labs.netnode.ch/live/).
The basic idea is to have a dashboard view where you can create multiple "spaces". Per space you can define keywords and get real time updates according the keywords, you get a public url around the space to share, you can comment on spaces e.g. commenting the stream, you can chat inside a space with others watching the same space.
I'm happy to get a feedback.
Demo public spaces are: http://labs.netnode.ch/live/spacepublic.php?space=15
http://labs.netnode.ch/live/spacepublic.php?space=11
Thanks
Lukas