I spent the day hanging out at WhereCamp09, enjoying the geekdom and learning about great new projects. These folks are really doing amazing stuff.
But it surprised me how little the geo-geeks have done to embrace the social web.
The folks hanging at WhereCamp definitely need to be plugging in to the ID/Privacy/InfoCard/VRM effort. Too much of the cool stuff they are talking about is just creepy without robust controls on private data.
It’s also clear that the Identity folks need to somehow do better at getting the word out about their solutions to some of these problems.
I don’t know if this missing connection is a bigger problem for the WhereCamp folks or for the IIW folks. Is it a symptom of myopia for the mappping crowd, or lack of visibility for the identity nerds? Which effort is hurt worse when they are slow to cross-pollinate their ideas?
Last week I attended the VRM West Coast Workshop and one of the many impressive folks I met there was Joe Andrieu of Switchbook. In a recent blog post, Joe describes the The Identity Quartet – the key services that allow user to express their identity in online services. It’s one of the most clear descriptions of the identifier issues I’ve read. Joe even makes the point:
The Identity Quartet pattern isn’t rocket science. In fact, it makes things simpler when it comes to security, maintenance, and user control. The Quartet makes systems more flexible and more secure while giving users more freedom to manage how they interact and present themselves online. It is one way to turn user-centric Identity services of OpenID and Information Cards into truly user-driven Identity.
[From The Identity Quartet]
His post is recommended for anyone wanting to start understanding the issues of identity and security in internet applications and services. Check it out!
Congratulations to my friends at Seesmic for being at the front of the Facebook Open Stream…
To get things started we’ve worked alongside a few beta partners to test the Facebook Open Stream API. For example, Seesmic Desktop is now a full-featured client for the stream and Adobe has created a simple stream Notifier using the AIR development framework.
[From Facebook Developers | Facebook Developers News]
I’ve been using Seesmic Desktop since it’s launch, and loving it. It doesn’t support all the services I’d like, and maybe could have a few other features, but what they have implemented has been done well. Keep it up!
I’m not sure I like “4th party” as a description. We spent way too much time at the VRM West Coast Workshop wrangling over the naming of firs, second and third. But when you get past all that, this key idea is really something big:
VRM is about enabling the first party. It is also about building fourth-party user-driven (and within that, customer-driven) services, which make use of first-party enablement.
Fourth parties will provide many services for first parties. In fact, VRM should grow large new fourth party businesses, and give new work to large old businesses in the same categories. (Banks, brokers and insurance companies come to mind.) Native enablements, however, need to live with first parties alone, even if fourth parties provide hosting services for those enablements.
Fourth parties also need to be substitutable. They need service portability, just as the customer needs data portability between fourth (and other) party services. That way whatever they can provide can be swapped out by the user, if need be.
[From ProjectVRM Blog » VRM and the Four Party System]
The combination of service portability and data portability doesn’t just put the user in charge, it also makes the data better. Companies should be very interested in that.