Marc Canter
|
1
|
 |
|
06-22-2008 10:51 AM ET (US)
|
|
Edited by author 06-22-2008 10:57 AM
This is when I'd import my social graph from Twitter, FriendFeed, Facebook and a few other places - to form a mesh of people interested in 'fluid conversations'. I'd like them all to a new 'meme' conversations and their responses and feedback would pile up on this 'thread' - but ultimately be locked up inside the service that was hosting the conversation.
So why can't we free our fluid conversations from ownership of just ONE service? Why can't the conversation bridge the gap between services - and be owed by us all?
With each new meme - a thread would be created that was persistently stored on a DNS-like network of 'conversation servers - which was owned by nobody. NEA. These conversations would be re-entrant, have media attached to any node of the conversation and mesh smoothly into any and all participating 'services' which themselves would be part of the 'LiveWeb'.
Conversations could morph and move between browsers and desktops, Macs and PCs, mobile devices, kiosks, your car and your living room.
Years ago we started a standard called ThreadsML. We were just 4-5 years too early. Perhaps now it's time has come?
Message board/mail lists hybrids such as QuickTopic have come and gone but the notion of threaded conversations has morphed with comments, twiterring, friend feeds, video seesmicing, etc.
Technically it's possible to connect all of these services together with ThreadsML.
|