This bleeds into the topics i was passionate about last summer. I recall wanting to get Brian to use his rp.ly domain to spearhead this stuff….. http://in.rp.ly/to/
I was also refreshing on commentAPI and other older protocols/ideas from a decade ago.
http://www.salmon-protocol.org/salmon-protocol-summary
Signed up for an invite. Sounds like something I should be trying out!
Reading this:
http://www.readwriteweb.com/archives/the_real-time_web_a_primer_part_2.php
In particular, this paragraph:
For those prone to theorize, there are many fascinating questions to ponder. For example, the uncertainty principles states that the position and velocity of an atomic particle becomes less certain as that of another becomes more certain. If the analogy holds true, then does the veracity or truthfulness of news become less certain as the velocity of interest becomes more measurable. Likewise, what effects will the integration of the real-time stream have on the outcome of events, and how can conditions be influenced to ensure specific outcomes.
I recalled a few somewhat related comments I had made on friendfeed some time ago. So i’m collecting those and posting them here (again). This is helpful to me at least. And hopefully interesting to a few out there for good measure 
Tom Foremski
The Problem With The Real-Time Web – No Google Juice
http://www.siliconvalleywatcher.com/mt/archives/2009/07/the_problem_wit.php
My comments:
tom’s post points out the obvious. “You’ve got to do both. If you abandon your static web presence for your real-time activities you will find it harder to build your overall social media capital”. of course a single micro-message is not *typically* going to have any weight as it’s often just a pointer to the real content value. the largest percentage of the so-called real-time messaging going on today are links with a bit of context and/or opinion. it’s a medium to connect more people with more content. this broadcast medium itself is secondary as it pertains to actual content. so yeah, their is a lack of google juice but it’s not nec a problem. unless we are talking about aesthetically pleasing tweets of the poetic variety
i also think real-time is a feature of the larger evolving digital infosphere. in a way, realtime is like rapid failure…. meaning… the speed and volume of the data flow to analyze and grade and filter and stock… the greater the value realtime offers to intelligent systems (ie. google). slower data flow translates to a slower realization of what content is not only generally good but also what is accurate, what is Legitimately trending and what is Actually being requested by millions of user search queries. Realtime Find is more important than Realtime Search.
The other day, @bitlynow gave me a link about someone who died. my first thought was… hey it’s bitly, they are good at what they are doing so i gave the tweet artificial value by reposting it only to realize moments later that the link and story were part of a hoax and possibly part of a worm. perfect example of why faster realtime data flow and analysis are critical to avoiding bad data from propagating.
A comment I had posted on:
Echo won’t kill comments — they’re already dead.
echo does not present a problem that cannot be logcially and easily handled.
echo should work in tandem with traditional comment option. the UI could handle this in different ways such as a few tabs beneath the post, using a sidebar or even a popup.
echo should not replace your own comment system.
every blogger should want to have control over comments. this is not very different than the topic of owning control of your short tracker urls and using your own domain etc. comments are important enough to control in the same way.
in addition to trackbacks/pingbacks, echo can co-exist. just dont disable your own comment system, even if moderated.
yep, this is yet another wordpress blog. not a fan of wordpress but at least i own it. will migrate away, eventually.