Comment aggregation
Fred Wilson groks that ‘comments’ are the new lock-in - this is a new battleground of the platforms.
IMHO content aggregation is the solution.
When a comment is posted - why only put it on ONE comment database?
Then check to see if additional comments are added and add THOSE to the other sites. use logos and colors (in the background) to connote where these comments originated and we’ll have ourselves persistent, aggregated conversations.
IMHO
Marc - I have long thought that the way comments (and email, for that matter) should be processed is that when a comment is made - no matter where it’s made - it is posted and stored on the commenter’s (or emailer’s) OWN server.
This would be enabled by something like OpenID, which would tell a remote site where the comment should be posed (I log on as downes.openid.ca which tells the blog website to sent my comment to a form at downes.openid.ca/comments.cgi).
The recipient (or a comment or an email) would recieve only a short notification - a ping - which they can accept or reject according to local rules (eg., is there a social net connection, is it from a trusted whitelist, whatever).
I think that so long as we leave content on other people’s sites (or in their in-boxes) we will have the dual problems of spam and host lock-in.
The primary use of OpenID should not simply be identification, but also, to tell remote sites where to direct our actions. So - in a sense - I carry all my own home website tools with me when I travel around the web.
Marc - I have long thought that the way comments (and email, for that matter) should be processed is that when a comment is made - no matter where it’s made - it is posted and stored on the commenter’s (or emailer’s) OWN server.
This would be enabled by something like OpenID, which would tell a remote site where the comment should be posed (I log on as downes.openid.ca which tells the blog website to sent my comment to a form at downes.openid.ca/comments.cgi).
The recipient (or a comment or an email) would recieve only a short notification - a ping - which they can accept or reject according to local rules (eg., is there a social net connection, is it from a trusted whitelist, whatever).
I think that so long as we leave content on other people’s sites (or in their in-boxes) we will have the dual problems of spam and host lock-in.
The primary use of OpenID should not simply be identification, but also, to tell remote sites where to direct our actions. So - in a sense - I carry all my own home website tools with me when I travel around the web.
Yes sure
Yes sure