echovar: Simulating VRM at the beginning of the Searlsian Decade
Adriana
· 1 year ago
"What I’d like to do is construct an RSS feed of the kind of things I’m interested in for my kitchen remodel. Vendors could read that feed and respond with feeds of their own that I could wrap into a consolidated feed where I could rank, tag, filter, sort, and search the RSS items. The user contract with the vendor is: don’t offer me feeds that aren’t relevant to my interest/gesture feed or you will be labeled a spammer."
That's exactly what I concluded some time ago and what I want for myself. Given that there isn't much out there (checked evernote and live mash and they don't really cut it), I decided to try to design such a tool myself. here is more, if interested. http://www.mediainfluencer.net/2008/05/i-haz-a-...
cgerrish
· 1 year ago
Interesting approach, I tried to express something similar with my posts "Who owns the pen with which you write?" and some discussions about Data Liquidity.
Lately I've been thinking that the foundation for this approach already exists in Dave Winer's OPML Editor. Because Dave fundamentally believes that you should have a local copy of everything you write or create, you keep your data at the point of origin. Then there's a simple upstreaming process that could be pointed to various clouds, or the blogging API. A comment API would be a welcome addition.
There's a question about how new infrastructure and standards propagate -- it requires a tremendous use of force to implement change systematically. Spreading virally node by node seems to be the more effective model.
Doc Searls
· 1 year ago
Cliff,
Thanks for understanding VRM so well — and for adding to that understanding.
A couple thoughts.
First, you are right that VRM is an Archimedean challenge. I prefer that metaphor to ocean-boiling. If we borrow the ocean metaphor, it's to look at the sea (half million and counting) of open source code bases out there for the right combination of small wheels we don't need to re-invent. I believe this is exactly what Adriana, Alec and friends are doing with the work she points to in her comments. It's also what we're doing with the relbutton. The nice thing there is that we have a handy symbol behind which all kinds of code can be placed.
Second, the "Searlsian" adjective makes me cringe. I'd prefer something descriptive. "The relationship decade" or "The live Web decade" perhaps? I like 'live" because I think the most important and meaningful interactions will happen in close to real time. Too much of demand works that way already in any case, and the site-based static web can't cut it. Not alone, anyway.
I also think it needs to be mobile. A whole 'nuther topic I don't have time to go into, but let's stick a reminder there.
And thanks again.
cgerrish
· 1 year ago
Thanks for the comment Doc. The 'ocean boiling' metaphor is really a question of approach, as you note. But it does give a sense of the size of the task at hand.
The live real-time aspect of this is very interesting. While XML-HTTP-Request has created a back door into a more interactive web page, it seems clear that an XMPP infrastructure will need to be deployed along side the established HTTP servers to provide that capability.
If we assume success, the scale and bursty-ness of traffic will be tough to engineer for. Witness the difficulties of Twitter. I'm starting to explore the idea that a primary market will be required for VRM gestures. It'll be too difficult for Vendors to scan all possible nodes looking for possible connections. This is where the utility of Twitter and Track could be a piece of the puzzle.
Regarding the mobility issue. The un-networked desktop computer is dead, long live the teleputer.
As far as my use of the "Searlsian" adjective, ultimately it's not for you or me to say. If VRM and IIW have achieved their goals in ten years, I'd like to make sure that it's remembered that a person had this vision and worked with others to make it happen. The technical achievement will be substantial, but the human achievement will be world changing.
Graham Sadd
· 1 year ago
A key point about VRM is to have the ability to post 'invitations' to pull relevant information whilst retaining your anonymity. You may be interested to read the article 'VRM - Threat or opportunity?' on my blog or at http://www.mycustomer.com/cgi-bin/item.cgi?id=1...
cgerrish
· 1 year ago
My understanding of the ongoing development of identity models through the IIW process is that 'anonymity' may either be a default state, or a managed persona within an identity management system.
The key is to enable a two-way market and conversation. One might ask the question: who would perceive VRM as a threat?
All Comments
That's exactly what I concluded some time ago and what I want for myself. Given that there isn't much out there (checked evernote and live mash and they don't really cut it), I decided to try to design such a tool myself. here is more, if interested. http://www.mediainfluencer.net/2008/05/i-haz-a-...
Lately I've been thinking that the foundation for this approach already exists in Dave Winer's OPML Editor. Because Dave fundamentally believes that you should have a local copy of everything you write or create, you keep your data at the point of origin. Then there's a simple upstreaming process that could be pointed to various clouds, or the blogging API. A comment API would be a welcome addition.
There's a question about how new infrastructure and standards propagate -- it requires a tremendous use of force to implement change systematically. Spreading virally node by node seems to be the more effective model.
Thanks for understanding VRM so well — and for adding to that understanding.
A couple thoughts.
First, you are right that VRM is an Archimedean challenge. I prefer that metaphor to ocean-boiling. If we borrow the ocean metaphor, it's to look at the sea (half million and counting) of open source code bases out there for the right combination of small wheels we don't need to re-invent. I believe this is exactly what Adriana, Alec and friends are doing with the work she points to in her comments. It's also what we're doing with the relbutton. The nice thing there is that we have a handy symbol behind which all kinds of code can be placed.
Second, the "Searlsian" adjective makes me cringe. I'd prefer something descriptive. "The relationship decade" or "The live Web decade" perhaps? I like 'live" because I think the most important and meaningful interactions will happen in close to real time. Too much of demand works that way already in any case, and the site-based static web can't cut it. Not alone, anyway.
I also think it needs to be mobile. A whole 'nuther topic I don't have time to go into, but let's stick a reminder there.
And thanks again.
The live real-time aspect of this is very interesting. While XML-HTTP-Request has created a back door into a more interactive web page, it seems clear that an XMPP infrastructure will need to be deployed along side the established HTTP servers to provide that capability.
If we assume success, the scale and bursty-ness of traffic will be tough to engineer for. Witness the difficulties of Twitter. I'm starting to explore the idea that a primary market will be required for VRM gestures. It'll be too difficult for Vendors to scan all possible nodes looking for possible connections. This is where the utility of Twitter and Track could be a piece of the puzzle.
Regarding the mobility issue. The un-networked desktop computer is dead, long live the teleputer.
As far as my use of the "Searlsian" adjective, ultimately it's not for you or me to say. If VRM and IIW have achieved their goals in ten years, I'd like to make sure that it's remembered that a person had this vision and worked with others to make it happen. The technical achievement will be substantial, but the human achievement will be world changing.
You may be interested to read the article 'VRM - Threat or opportunity?' on my blog or at
http://www.mycustomer.com/cgi-bin/item.cgi?id=1...
The key is to enable a two-way market and conversation. One might ask the question: who would perceive VRM as a threat?