Facebook has announced that they are about to release vanity URLs.

What most people don’t realize is that this move, while interesting, is not really about vanity URLs at all – it’s actually about addressable identity.

One of Twitter’s key advantages in the race for dominance over internet identity is their growing namespace of what I call Addressable Identities.

What are they I hear you ask? An example of an Addressable Identity is being able to write ‘@chrissaad‘ and have the system and users understand that it is a direct and concrete reference to me. This form of addressing is particularly interesting because it is easy to write in a sentence or micro-blog.

With Vanity URLs, Facebook will encourage users to specify a tidy/tiny/compact identity identifier by which friends/followers/others can reference/point to each other. This is a big step towards keeping up with Twitter as one of the web’s only providers of modern addressable identities (email is an old, less compact version of this).

It will be interesting to see how this unfolds and how we consolidate these namespaces when using 3rd party services.

It might ultimately have to end up like good old email:

chrissaad@twitter.com, chrissaad@facebook.com etc.

Ideally though, we should be able to use our own/personal email address and have it resolve to an OpenID for true, federated and open addressable identity.

That, however, is still some way away.

google_wave_logo-760260

I was just debating with a friend about the value and usefulness of Google’s Wave in the enterprise.

His argument is that Wave has 10 years of adoption curve ahead of it and would not quickly replace email or wikis for enterprise staff.

I tweeted my response:

20% of enterprise users will be using wave in the first 12 months for more than 50% of their comms (replacing email and wiki)

Edit: To be clear, my 12 month time frame begins when Wave is publicly available.

That’s a big call to make on enterprises adopting a radically new technology. Enterprises move very, very slowly. So why am I so bullish on the adoption of Google Wave in the enterprise?

Here’s why…

Email is king

Everyone uses email right? Why would people swap? Because with Wave, they don’t have to.

First, with Wave’s API there will quickly and instantly (I mean in weeks, long before public launch) be integration between Wave and Email. Wave messages and events will  be funneled to email and back again as if the two were built from the same protocol.

Second, Wave will be viral. Users will quickly realize that their email inbox is only giving them a pale imitation of the Wave collaboration experience. It will be like working with shadow puppets while your friends are over having an acid trip of light, sound, fun and productivity.

If someone had told me that they were setting out to kill/replace email, I would have laughed in their face. Now that I see the Wave product and roll out strategy – I think it might actually happen.

Enterprise IT Departments

IT departments are slow to adopt and roll out new technologies right?

People forget that enterprises are just a collection of human beings. Social beings. Like IM, Facebook, LinkedIn, Gmail, Wikis and countless other applications, Wave will soak into an enterprise long before the IT department knows what the hell is going on.

The enterprise adoption curve of Wave, however, will make those other technologies look glacial. Everyone who ever picked up a Wiki, IM client, Facebook or Twitter (I think that covers 99.9% of the developed, working world) will latch onto Wave for dear life.

Everyone else will be forced to open a Wave client to find out what the hell is going on.

Too many tools

Enterprises indeed have many, many tools that already ‘own’ a large part of a given knowledge worker’s/enterprise user’s day.

None of them matter anymore. Again, with Wave’s amazing API and extensibility model, each of these apps, custom or not, will have a Wave bridge.

Official Wiki Pages, Sales Reports, Bug Tickets, New Blog Posts, Emails, Customer Records will all be available and accessibly from the Wave interface.

Who’s going to write all those bridges? Hacker employees, smart IT department engineers, new start-ups and the companies that own those other products hoping desperately to remain relevant and competitive.

Half Lives

Geocities, MySpace, Facebook, Twitter. What do these things show us? That technology adoption has a half-life. Geocities lasted as king of the heap twice as long as MySpace, MySpace twice as long as Facebook and so on. We are approaching a kind of singularity – although just like with the mathematical function, one can never achieve 0 of course.

Sure, enterprises move much more slowly, but when was the last time a really new enterprise productivity application hit the market? Do we even know what the current half-life is? My bet is that it’s pretty damn short – and Wave has the potential to be ahead of the curve.

Related link: Business Opportunities around Google Wave

media-20-best-practices-logo

Today the Media 2.0 Best Practices went live. I’m very happy to see this come to light.

I’ve been working on something like it for a number of years now, and with JS-Kit’s backing and the participation of my friends it has taken shape.

I’d like to thank all involved. I look forward to having conversations with the participants and creating something that vendors can use to make and keep user-centric promises to their participants.

I’m also very happy that the Media 2.0 Workgroup was able to take on this process and see it through. There is a lot of potential in that group that is yet to be realized.

Check it out…

Visit the site and view the strawman at www.mediabestpractices.com


Follow along


Source materials
donated to the community by

Supported and
shepherded by

I’m a little weary of the Twitter Vs. Facebook debate.

I posted this comment on Fred Wilson’s blog. I thought I would share here:

Twitter is the status service of the web-wide social network. Facebook status updates are the status update feature of Facebook. The web will always be bigger than Facebook therefore Twitter’s potential as a messaging bus will always be greater.

While Twitter continues to create loosely coupled links across the open web (a lightweight process), Facebook continues to try to expand the perimeter of its walled garden (a heavy weight process that is creating a backlash from major brands and savvy users).

Twitter is public and asymmetrical. It allows for bots and other innovations.

Facebook is private and symmetrical, forcing users to use their real names and deciding which updates get through to follower news feed.

The two services couldn’t be more different and the influence and effectiveness of their scale can not be measured 1:1.

Proposal: OpenID Connect

December 8, 2008

OpenID needs to be as simple as Facebook Connect if it has any chance of competing. The problem is User Experience. It’s a nightmare.

My proposal:

  1. All Email providers and OpenID Consumers (particularly Gmail, Hotmail and Yahoo Mail) implement: http://eaut.org/
  2. Until we have critical mass with step 1, a 3rd party, community controled “Email to OpenID mapping service” should be provided. Vidoop runs a related service at http://emailtoid.net/. It’s quite good but it should be donated to the OpenID foundation for independent control.
  3. OpenID Connect login prompts ask for your email address on 3rd party sites.
  4. When you hit ‘connect’ it generates a popup much like the FB Connect popup.
  5. The contents of the popup is either:
    • The password screen of the OpenID provider as resolved via EAUT OR
    • The password screen of the OpenID provider as resolved via the community EmailtoID service OR
    • A prompt from the EmailToID service that walks you through creating a new OpenID or mapping an exiting OpenID to this email address.Here’s the important part: In all cases, the screens MUST conform to a strict UX Design Guideline set forth by the OpenID Foundation to ensure the process is as simple as Facebook Connect.Only providers that confirm to this OpenID Connect UX standard (as certified by the OpenID Foundation?) may have their OpenIDs validated in this popup. This is a harsh rule but it ensures a smooth UX for all involved.
  6. This initial Email to OpenID mapping through a 3rd party service is painful since most email providers and OpenID consumers do not use EAUT yet.
  7. This can be overcome if we get a series of OpenID Consumers and OpenID Providers involved as launch partners. A major email provider (Gmail, Hotmail and/or Yahoo) would also be be helpful but not a blocker.

Potential Concerns:

  1. How do we deter phishing? Does this work-flow make phishing worse because of the predictable UX? Does it matter? Is there a way to ensure a distributed karma system is included in the work flow?
  2. This only solves the login problem and does not go into the issue of connecting to, accessing and manipulating data as the full data portability vision describes. This is a conversation for another thread.

Bonus:

  • If you provide OpenID but do not consume it you need to be named and shamed. There should be a 2 month grace period, then The OpenID Foundation, the DataPortability Project and everyone else who is interested should participate.
  • “OpenID Connect” should be a new brand with a fresh batch of announcements with strict implementation guidelines (not just around UX but also around things like consumption).

To summarize, my proposal world:

  1. Allow users to use their email address for OpenID
  2. Standardize the User Experience for OpenID
  3. Provide a stop gap while Email providers catch up with Email to OpenID mapping.

Get involved:

I’d love to do mockups for this – but I’m busy. Anyone interested in learning from the Facebook Connect UX and drafting OpenID Connect Mockups from which we can draw the strict UX guidelines I mentioned?

Could this work?

According to CNet, Facebook is going to start charging app developers a fee to achieve ‘Verified Application’ status. The fee is optional, but that doesn’t matter. Apps that are not ‘verified’ will quickly get buried by those that are.

I think in hindsight people will recognize this move as one of the final death knels of the Facebook platform as we know it today.

First, they de-emphasized applications all together by relegating them to a ‘boxes’ page and making the stream their primary interaction metaphor (Read: FriendFeed clone). Now they are trying to lock down the platform further, raising the bar for participation and charging what amounts to a protection fee for app developers to get any real attention at all.

The fact of the matter is, an increasing number of people are finally realizing that Facebook looks very similar to Pre Internet networks, AOL, Passport/Hailstorm, and any other proprietary implementation of a platform that can and must be open.

The only platform that matters on the web is the web itself, and Facebook through its actions and inactions is helping us all learn this lesson faster than ever.

Forget Facebook

May 16, 2008

Debating Facebook’s data portability move (Facebook Connect) is like debating AOLs web strategy back in the day. Their strategy is clearly to create a rarefied ecosystem where users (read: facebook) are in complete control of the ‘approved’ content and interactions. With this in mind, it is clear that Facebook is not the first, best platform in which to design, implement or debate Data Portability.

Debating Google’s data portability move (Friend Connect) is like debating the Netvibes universal widget platform. It is not data portability in the sense that the DataPortability project has defined it. It is a platform that translates existing proprietary implementations into it’s own unified proprietary implementation to enable social widgets to run in more places.

MySpace’s data portability move (Data Availability) is actually the closest play to data portability as defined by the DataPortability project. It proposes to allow 3rd party sites to access the users personal data using open standards extracted from the page (using microformats and a collection of full XML standards). The terms and conditions about caching, however, also bring it in conflict with the philosophies of the DataPortability project.

So as stated before, none of these plays are true ‘DataPortability’ implementations. But they are important first steps. They are the first shots across the bow to the industry that a data portability battle is coming. In fact it has started. Are we going to let it shake out like the IM wars? Or are startups, second tier players, standards groups, bloggers and users going to rally around and standardize to a totally open, grass-roots alternative?

Are the big players going to evolve their offerings to come in line with the rest of the world, or are they going to try to dominate (read: lose).

Further, data portability, and DataPortability is not just about social networking data or social networking scenarios. Certainly not social networking as defined by the social contract of Facebook. It might even be true that Facebook is a culturally bad fit for the DataPortability ecosystem. DataPortability is about a different social contract – a contract more closely resembling the one found in the email address book.

My address book is my own. When you email me, or when you communicate with me, you are revealing something about yourself. You define a social contract with me that means that I can use your information to contact you whenever and however I like – I could even re-purpose my address book for all manor of other things.

If, however, you violate that trust, either directly or indirectly, you break the social contract and I will tend to not deal with you again. We can not perfectly engineer these sorts of contracts into systems – we can try, but in the end social behavior will be the last mile in enforcing user rights.

Also, the dichotomy between who ‘owns’ the data is false. In my mind there is shared ownership. While you use a service, it has a shared custodianship of the data. By giving the service your data you’re getting something else in return – utility. In many cases free utility.

You personally, however, have shared (and overriding) ownership over your data. This has been declared as universally true by all the vendors I’ve spoken to.

The question is not one of ownership though, it’s one of control. If you own your data but can’t control it as you choose then ownership is a moot point. Further, the question is not one of if you own it, but rather how much of it you own.

For example, do you own your friends profile data since you have access to it via the social tool you are using? Or have they only granted you access within that social context and under that social contract. These considerations blur the analogy of the purely personal address book.

In this case, there is no correct, default answer. The answer must come from an old saying – “Your rights end where my rights begin”. That is, your friends need an additional options when ‘friending’ you. A checkbox will probably be required that states ‘Allow this contact to use my data elsewhere’.

The act of ‘friending’ will also need to take on more meaning and ‘grouping’ friends will become important. It will evolve, for most of us, and in most applications, from a popularity contest to a carefully curated address book of people we actually care about.