Trainfeed spotting

With the 10th anniversary edition of  Cluetrain coming out, I thought I’d try to keep up with postings that mention “Cluetrain” — through four five Live Web* search engines: BlogPulse, Google BlogSearch, Technorati, FreindFeed Search and Twitter Search. I’ve got all four feeding into an aggregator.

As of 3:33pm EDST, BlogPulse finds 20 posts so far in the month of June. Google Blogsearch finds 22. Technorati is currently down.  Twitter Search finds 28 in the last day (I didn’t go back any farther there.) Not sure I want to make this a more formal research effort. I just thought it was worth vetting a bit about how I’m following stuff.

[Later…] Thanks to Chris Heath for suggesting I add FriendFeed Search. There I just gave up counting at 50 postings.

* I much prefer “live” to “real time”, mostly because my son Allen came up with the “Live Web” line way back in 2003, and correctly observed that the Web of sites was essentially a static one, and that the World Live Web would branch off of it. The language alone is a give-away. The Static Web is full of real estate language: sites, domains and locations that you architect, design and build. While the Live Web is one with feeds where you write, post, update, syndicate and now also tweet and re-tweet. To me the differences between static and live are much clearer than those between ______ (find a word) and real time.



5 responses to “Trainfeed spotting”

  1. Doc, you should add a friendfeed search to that list – http://friendfeed.com/search?q=cluetrain

  2. […] See more here: Trainfeed spotting […]

  3. Amen, Doc. The whole “real-time” thing has been over-played – “Now” has a radius, and few of the feed/stream efforts today are truly “real-time” in the sense of chat or financial markets.

  4. […] Thanks to Chris Heath for suggesting I add FriendFeed Search. There I just gave up counting at 50 […]

  5. […] Thanks to Chris Heath for suggesting I add FriendFeed Search. There I just gave up counting at 50 […]

Leave a Reply

Your email address will not be published. Required fields are marked *