There’s a lot of fury on the web right now about ‘Real Names’. FB is trying to use it as a unique feature of their comments system claiming it reduces trolling and low value comments.

Of course that isn’t really true. For one, any commenting system could force FB login. Two, users will troll with or without their name attached and, worse yet, many legitimate users won’t participate for any number of reasons if they can’t use a pseudonym. There are plenty of better ways to increase quality in your comments including participation from the content creators, game mechanics, community moderation and more.

The real debate, however, is about G+ trying to copy FB’s stance on Real Names. They are insisting all user accounts use them and are actively shutting down accounts that violate the policy. They are being so heavy handed about that even people who ARE using their real name are getting notices of violation – most notable Violet Blue.

I’m not really an expert on pseudonyms, shared contexts and anonymity so I’m going to stay out of this debate.

The real question for me, however, is what is Google’s strategic business reason for this policy. There must be a long term plan/reason for it otherwise they wouldn’t be insisting so hard.

My assumption is that it’s related to their intention to become a canonical people directory and identity provider on the internet to compete with FB in this space.

FB, after all, does not just get it’s power from news feeds and photo apps – it gets it from the deep roots it has laid down into the DNA of the internet as the provider of 1st class identity infrastructure and identity information.

In this sense, FB’s social contract has served them very well, and Google’s attempt to copy it is a hint that they understand FB is not just a .com feature set, but a powerful identity utility. They must (and in some cases seem to be) understand that strategy and it’s aggressiveness if they are to properly compete with the monopoly. My only hope, however, is that they are coming up with their own inspired counter strategy rather than just copying the moves they see on the surface – because that’s doomed to fail.

First, to define ‘Real-time’

Real-time is no CDN or Cache latency. When there is new data in the database, it’s available to the end-user.

Real-time is not needing to hit the refresh button to see new information. It’s when information folds into the page while you’re reading it.

Real-time is a new volume and velocity of data. A lot of web data used to consist of ‘Blog Posts’ or ‘News Articles’. Documents. Real-time web data is about activities. Granular, human readable micro-stories about the activities that users make.

“I read this”, “I rated this”, “I commented on this”, “I shared this”, “I edited this” and so on. Why? Because capturing, surfacing and socializing real-time activity data is part of the core essence of the social web. The ability to see not just the result of actions by users, but the play-by-play stream of those actions along side faces, names and time/date stamps takes an experience from a static ‘snapshot’ into a living, breathing stream. Further, by enabling users to like, reply, flag, share and otherwise interact with these activities, sites are creating new opportunities for engagement, conversation and conversion.

Real-time is a presentation metaphor. It often (but not always) takes the form of a reverse chronological stream with nested comments and likes. It helps users understand the order of things and mixes content with conversation in a way that drives engagement and return visits.

Real-time means filters instead of facts. Let the user decide what they want to see – to craft an experience that makes sense for them, and their friends.

Now, what is ‘Real-time as a Service’?

If all the things above are true, then it changes everything we used to know about web infrastructure, databases, user interfaces and tools for moderation or curation.

APIs can no longer be request-response. Databases must now store far more data at far faster rates. User interfaces need to factor in names, faces and actions. Moderation and curation tools must leverage algorithms, crowd sourcing and real-time flows.

Real-time as a service, then, is cloud infrastructure that helps make this transition easier.

It is a database that can handle new magnitudes of scale – handling hundreds or thousands of write events per section. Not just to a flat table, but to a hierarchical tree of arbitrary activities.

Site -> Section -> Article -> Rating -> Comment -> Reply -> Like.

It’s a database that can store all items permanently so that users can visit old streams at any time. Permanent storage that can also handle localized annotations. Localized annotations are the ability to modify the metadata of an activity – say a Tweet (Promote it, tag it, retarget it in the tree etc) – in such a way that that your view of a tweet is different from another customer’s view.

It’s a database that enables not just the ability to perform an SQL-like search query, but also continuously updates you when the data changes – so that you can modify the UI on the fly.

It’s a database that returns not just flat query results, but a hierarchical tree – allowing you to present the activity in context.

It’s a database that handles not just a few hundred users requesting (reading) data, but a few million users swarming to see the latest action in a sports game or a concert.

It’s a database that organically makes connections between items by understanding the relationships of URLs and #tags to make implicit links in the graph where and when they’re needed. For example a tweet mentioning acme.com should be attached to Acme.com in the tree.

And most importantly, it’s a database company that understands that the opportunity of the Real-time, Social Web is far too big and moves far too quickly to possibly be built by a single vendor. A company that, as a result of this understanding, chooses open standards over proprietary formats; Partnership with best-of-breed partners over trying to build mediocre versions of everything by itself.

Polls, Ratings, Comments, Live Blogging, Forums, Data Bridging, Data Enriching, Visualization, Moderation, Curation, Analytics Game Mechanics, Authentication… the list is endless. They are all transformed by the Real-time web. They must all be part of Real-time as a Service.

And finally, Real-time as a Service is about service. Enterprise grade support. Best in class uptime. White label.

That’s Real-time as a Service.

Further Reading

• Another way to describe it here.
• Here are some Case Studies for what you can build with such a service.

Part 1

Part 2

This year, like many years before it, has been one of immense personal growth for me. I have continued 2009′s transition from one who is best known and suited for talking about ideas to one who focuses much more on turning ideas into product and business process at scale. I still have a lot to learn!

For that, I continue to thank my friends and colleagues at Echo for their patience, collaboration and wisdom.

In keeping with this transition, this year I have mainly been head down at Echo working on our product, marketing and business roadmap with the team. Much of our work has not yet seen the light of day and I can’t be more excited for it’s eventual release.

The result is I’ve missed a lot of parties or conferences I love to attend, but it has also given me a great opportunity to stay at home and get to know an amazing woman, Nichole. Meeting her has been surprising. And I am rarely surprised.

That being said, though, I feel like I’ve become closer to a core set of amazing people – friends – who continue to inspire, irritate and elevate me. Like all good friends should!

The industry too has gone through some amazing transitions.

Apple’s iOS, once thought invincible, has gone through the inevitable re-balancing against a more open alternative, Android. Facebook, once thought a fad by some, has solidified it’s place as the winner of the destination social networking space through a series of very smart decisions, a total lack of competition and free pass from all the tech media.

Twitter, on the other hand, seems to have continued to struggle to find its place. From simple SMS service, messaging bus of the web or media power house; this year they seemed to drop the ball on all fronts.

Wikileaks has forced us all to think about ultimate transparency and has shone a brilliant light on the media’s inability to understand its own role (particularly the 24 hour broadcast news networks). Transitional media thinking has truly failed us in this new century and will continue to fail as long as they cling to out-dated business models and false drama.

I’m glad that Jon Stewart has taken a more active (even serious) role in this message – however slightly.

I am, however, optimistic for the mainstream media. Many of the executives I have spoken to there (which is many) understand the transition and are fighting each day to lead it.

Overall though, for me personally, 2010 was primarily a year of contentment. A rare feeling for me. For that, I am grateful for all of those who contributed. Past and present.

I can’t wait to see what 2011 brings. I only hope my luck holds out!

Steve Gillmor often writes fantastic (and fantastically long) editorials on the landscape of the real-time web, but they are often very dense and sometimes fail to cover some key points. I thought I would take the liberty of translating and correcting his latest post with my own contributions.

Ever since FriendFeed was sold to Facebook, we’ve been told over and over again that the company and its community were toast. And as if to underline the fact, FriendFeed’s access to the Twitter firehose was terminated and vaguely replaced with a slow version that is currently delivering Twitter posts between 20 minutes and two hours after their appearance on Twitter. At the Realtime CrunchUp, Bret Taylor confirmed this was not a technical but rather a legal issue. Put simply, Twitter is choking FriendFeed to death.

Translation: The FriendFeed team were absorbed by way of acquisition. Twitter has terminated their priority access to Twitter data because FriendFeed is now owned by Twitter’s primary competitor.

Correction: Of course Twitter turned them off. Facebook is Twitter’s self-declared number one competitor. When you own the platform and the protocol you have every right to protect your own arse. In fact they have an obligation to their shareholders and investors.

What’s odd about this is that most observers consider FriendFeed a failure, too complicated and user-unfriendly to compete with Twitter or Facebook. If Twitter believed that to be the case, why would they endeavor to kill it? And if it were not a failure? Then Twitter is trying to kill it for a good reason. That reason: FriendFeed exposes the impossible task of owning all access to its user’s data. Does Microsoft or Google or IBM own your email? Does Gmail apply rate limiting to POP3 and IMAP?

Translation: Most commentators think that FriendFeed is dead because the founders have been bought by and buried inside Facebook. If FriendFeed is so dead why is Twitter trying to choke it.

Correction: FriendFeed is clearly dead. If you have ever worked for a startup and tried to ship a running product you know that focus is the only thing that will keep you alive. Facebook is a massive platform serving a scale of social interaction that has only been previously seen by distributed systems like email. The last thing Facebook wants is for its newly aquiried superstar team to waste time working on a platform that no longer matters to their commercial success or the bulk of their users (i.e. Friendfeed).

Twitter is choking FriendFeed for another reason – because it’s systems are now essentially just a proxy to Facebook. As stated above, Twitter can not give it’s number one competitor priority access to one of its major assets (i.e. timley access to the data).

The data that Microsoft and Google does not exercise hoarding tactics over (the examples Steve gave were IMAP and POP3) are open standards using open protocols.

I am never sure about Steve’s position on open standards, he often vacillates from championing the open cause through projects like the Attention Trust only then to claim things like APML and DataPortability are bullshit – maybe he just doesn’t like me (That can’t be right can it Steve?).

The fact is, however, that open standards and protocols are the basis for open systems which is why companies like Microsoft and Google do not control your email. Twitter and Facebook are not open systems.

So the reason Twitter is killing FriendFeed is because they think they can get away with it. And they will, as far as it goes, as long as the third party vendors orbiting Twitter validate the idea that Twitter owns the data. That, of course, means Facebook has to go along with it. Playing ball with Twitter command and control doesn’t make sense unless Facebook likes the idea of doing the same thing with “their” own stream. Well, maybe so. That leaves two obvious alternatives.

The first is Google Wave, which offers much of the realtime conversational technology FriendFeed rebooted around, minus a way of deploying this stream publicly. The Wave team seems to be somewhat adrift in the conversion of private Waves to public streams, running into scaling issues with Wave bots that don’t seem to effectively handle a publishing process (if I understood the recent briefing correctly.) But if Waves can gain traction around events and become integrated with Gmail as Paul Buchheit recently predicted, then an enterprising Wave developer might write a bot that captures Tweets as they are entered or received by Twitter and siphons them into the Wave repository in near realtime.

Translation: Twitter is killing FriendFeed because they think no one will notice or care enough to stop them – Twitter has more than enough momentum and support to continue along it’s current path. Facebook wont cry foul because they are doing the same hoarding technique with their own data.

Maybe Google Wave might save the day, but they seem to have lost their way.

Correction: Actually the only people who can call bullshit on Twitter and Facebook is us, the media. We are all media after all. Steve Gillmor in fact is one of the loudest voices – he should call bullshit on closed systems in general. Instead we all seem to be betting on one closed system to do better than another closed system.

We are like abused wives going back for more, each time pretending that our husbands love us. Guess what, they don’t love us. They love their IPO.

I was the first to support Google Wave very loudly and proudly. I met with the team and was among the first to get in and play with the preview. It is a revolution in collaboration and how to launch a new open system. It is not, however, a Twitter or Facebook competitor. Especially not in its current state. It is not even a replacement to email. It is simply the best damned wiki product ever created.

Waves are the 180′ opposite of FriendFeed and Facebook or even Twitter. They are open, flexible and lacking any structure whatsoever. Their current container, the Google Wave client, however, is totally sub-optimal for a messaging metaphor much less a many-to-many passive social platform. It is a document development platform. Nothing more.

The same could be true of Microsoft’s deal for the firehose, but here, as with Google, Twitter may not want to risk flaunting ownership of a stream that can so easily be cloned for its enterprise value. And as easily as you can say RSS is dead, Salesforce Chatter enters the picture. Here’s one player Twitter can’t just laugh off. First of all, it’s not Twitter but Facebook Benioff is cloning, and a future Facebook at that, one where the Everyone status will be built out as a (pardon the expression) public option. This free cross-Web Chatter stream will challenge Facebook’s transitional issues from private to public, given that Salesforce’s cloud can immediately scale up to the allegedly onerous task of providing personalized Track on demand.

Translation: Maybe the enterprise players – specifically Salesforces’ Chatter – will save the day.

Correction: Doubtful. This is just another closed system for a specific vertical. It’s long overdue. It is awesome. But it is not a Facebook or Twitter competitor much less an open alternative to the proprietary messaging systems we keep flocking to. It is simply a long overdue expansion of the simple changelog tracking feature on ERP assets. It’s a simple feature that was sponsored by a simple question. “Why doesn’t the asset changelog include more data – including social data?”. Duh. I was doing this in my own web based CRM at the start of the decade.

It’s likely this pressure can be turned to good use by Facebook, unencumbered as they are by any licensing deal with Twitter. Instead, a Chatter alliance with the Facebook Everyone cloud puts Salesforce in the interesting position of managing a public stream with Google Apps support, which eventually could mean Wave integration. Where this might break first is in media publishing, as Benioff noted at the CrunchUp. Twitter’s leverage over its third party developers could be diluted significantly once Salesforce offers monetization paths for its Force.com developers. So much so that this may call Twitter’s bluff with FriendFeed.

Translation: No idea

But FriendFeed has always been more of a tactical takedown of Twitter than an actual competitor, a stalking horse for just the kind of attack Twitter seems most afraid of. No wonder the speed with which Twitter is introducing metadata traps to lock down the IP before a significant cloud emerges to challenge its inevitability. Lists, retweets, location — they’re all based on raising the rate limiting hammer to discourage heading for the exits. It’s not that retweets reduce the functionality of the trail of overlapping social circles, it’s that they lock them behind the Wall.

Translation: Twitter is introducing more metadata into tweets to maintain its lock in through API limits etc.

Correction: On this point Steve is partially correct. This isn’t about rate limiting though – it’s about turning Twitter’s proprietary protocol into a real-time transport for all the data the web has to offer. It is not about API limits but rather cramming so much value into the pipe that the pipe becomes like water – you gotta drink from it or you’re going to die.

I don’t expect anyone from Twitter to answer the simple question of when will Twitter give FriendFeed the same access they provide other third party client vendors. For now, it’s frustrating to not see the flow of Twitter messages in realtime, but over time we’ll build tools on top of FriendFeed to take such embargoed messages private. Once inside FriendFeed, the realtime conversations that result are just the kind of high value threads Chatter will support, Wave will accelerate, and Silverlight will transport. Keep up the good work, Twitter.

Translation: I doubt Twitter will play nice with FriendFeed and give them equal access again because once items are inside FriendFeed they turn into rich conversations. Conversations that Chatter will support, Wave will accelerate and silverlight will transport.

Correction: Actually Twitter does not and has never given fair and equal access to its data. FriendFeed had a moment in the sun with first class access the likes of which almost no one else has seen before or since.

I have no idea how Chatter fits into the B2C picture – it is clearly an Enterprise play for Salesforce. Wave indeed will act as a great interface through which to participate in real-time threads. The threads themselves, however, will need to be generated or framed by much more rigid systems designed for public discussion.

Silverlight is great for rich web apps. It is Microsoft’s way of bringing the richness of the client into the browser. Just like .NET is to Java, Silverlight is to Flash. A way for Microsoft to leverage a key technology component without handing the crown to someone/something it doesn’t control. But I’m not sure if fits into this discussion.

In the end, the only real solution for all of this, of course, is a return to the way the web has always worked (well). Open systems. The transport should not be Twitter, Facebook, FriendFeed, Wave or any other nonsense. It should be RSS and Atom (ActivityStrea.ms specifically) transported over PubSubHubBub and read by open standards aggregators. The namespaces should be OpenID based and adoptable by all.

The sooner the early adopter community realizes this, the commentators push for this and the developers code for this, the better off we will all be.

Disclosure: I work for JS-Kit, creators of Echo – one of the largest providers of Real-time streams. I also Tweet – trying to find an alternative though!

Lately a number of my friends seem to be having great wins and making their mark on the industry in awesome ways.

When I first moved out to Silicon Valley (starting with a short trip in 2006) I already knew (by reputation) many of the names and personalities that made up the ecosystem. I read them on blogs, listened to them on podcasts and generally admired their work and learned from their ideas.

Once coming out here, I got to know many of them personally. Some let me down, others surprised me with their generosity and still others became wonderful friends.

I’d like to highlight just a couple of those today because they’ve been on my mind.

Jeremiah Owyang (and his new partners Deb Schultz & Charlene Li) has/have always struck me as one of the hardest working and smartest people in the valley.

Most recently I’ve had the pleasure to get to know Jeremiah on a personal level but had never actually worked with him 1:1 on anything serious before.

That changed last week when we sat down for a real ‘business meeting’. He blew my mind. That doesn’t happen often. His blog posts only show a fraction of the mans thinking. Not only does he think 5 steps ahead, he manages to find a way to package it on his blog in a way that even laymen can understand.

I am so happy for his collaboration at Altimeter. Jeremiah, Debs and Charlene are the nicest people and are all wicked smart.

Those that have been around me in the last 12 months have probably heard me talk about the need for an Altimeter group style firm and I’m glad that they are the ones to pull it off. They’ve done it with grace, style and stunning execution.

Can’t wait to see what they do next.

Stephanie Agresta is another of the people that I got to know as a friend once moving out here. For some reason and on some level we connected as kindred spirits who love to smile.

I’ve always felt like she had an undeserved level of faith and affection for me – but I accepted it gladly because it meant she wanted to hang out!

She too has recently made a move that not only befits her stature as a connector and thinker, but also rewards her kind spirit and positive attitude.

She gave me her new card at her birthday the other day – it says EVP of Social Media, Global – Porter Novelli (or something like that hah). EVP, Global, Porter Novelli. Are you serious!?

This is such wonderful news for our community because it means that someone who not only gets it, but loves it and is one of us, is in a position to help the brands we all know and love.

These are just two of my friends who have gotten what they deserve lately – in the best meaning of the phrase possible.

Congratulations peeps.

If I can help any of you reading this to achieve your goals, please let me know. This whole ecosystem, worldwide, is built on pay-it-forward. And I have a lot to pay forward.

On October 14, 2008 I wrote a blog titled ‘Who is JS-Kit‘. In it, I explained why I was joining the JS-Kit team and how their philosophy and execution resonated so much with me.

On Friday the 10th of July, 2009, the JS-Kit team launched Echo. Here’s the video. It is the clearest example yet of the potential of the JS-Kit team that I spoke about back in my Who is JS-Kit post.

I wanted to take this opportunity to explain what Echo means to me personally. But first, I’d like to make something very clear. Although much of this will be about my personal opinions, feelings and philosophies on Echo and the trends and tribulations that bore it,  Echo is the result of the hard work and collaboration of a stellar team of first grade entrepreneurs that I have the pleasure of working with every day (and night).

From Khris Loux our fearless and philosophical CEO who lead the charge, to Lev Walkin our CTO who seems to know no boundaries when it comes to writing software, to Philippe Cailloux, the man who turns our raving ADD rants into actionable mingle tickets, to our developers who worked tirelessly to turn napkin sketches into reality. We all scrubbed every pixel and will continue to be at the front lines with our customers. This is the team that made it happen.

For me, Echo is the next major milestone on a journey that only properly got underway in November 2006 when I visited Silicon Valley for the first time.

I was at the Web 2.2 meetup. It was set up by one of my now friends Chris Heuer. There was a group discussion about social networking and how we, as individuals, might communicate in ways that were independent of the tools that facilitated such communication.

I was sitting in the back of the room in awe of the intellect and scope of the conversation. Could you imagine it, for the first time in a long time I (a kid from Brisbane Australia) was in a room full of people who were just as passionate about this technology thing as me – and they were actually at the center of the ecosystem that could make a real impact on the outcome of these technologies.

I shyly put my hand up at the back of the room and squeaked out (I’m paraphrasing and cleaning up for eloquence here – I’m sure I sounded far less intelligent at the time).

“Aah… excuse me… aren’t blogs the ultimate tool agnostic social networking platforms?”

What I meant was that blogs use the web as the platform. They produce RSS. They have audiences. They illicit reactions. They create social conversations over large distances. They essentially create one giant implicit social network.

I got some “oh yeah he might be right” reactions and the conversation moved swiftly along to other things.

For me, a light turned on. One I’ve been chasing ever since in various forms and to varying degrees of success (or failure as the case may be). For me, Faraday Media, APML, DataPortability and now JS-Kit have all been an exploration on how to create a tool-agnostic, internet scale social network that has notification, filtering, interoperability and community at its heart.

As I said at the start of this post, Echo is the next step along that journey. For me, Echo represents an opportunity to making Blogging not only ‘cool’ again, but to make it a first class citizen on the web-wide social network. To make all sites part of that network.

Much has been made of its real-time nature. Even more about its ability to aggregate the fragmented internet conversation back to the source. These are both critical aspects of the product. They are the most obvious and impactful changes we made. But there is much more to Echo than meets the eye. Much more in the product today and much more we hope to still add.

Our choice of comment form layout. The use of the words ‘From’ and ‘To’. The language of ‘I am… my Facebook profile’. The choice to treat the comment form as just another app (as shown by the use of the ‘Via Comments’ tag) and more. The choice to merge the various channels into a unified stream (comments+off-site gestures). These were all deliberate and painstaking choices that the team made together.

Echo is based on a theory we call the ‘Synaptic Web‘. This is the frame of reference from which all our product decisions will be made. It is an open straw man that I hope will eventually be just as exciting as any given product launch. It states in explicit terms the trends and opportunities that many of us are seeing and is designed to help foster a conversation around those observations.

In the coming hours and weeks I’m also going to record video screen casts of the specific product decisions that have already made it into Echo – hopefully these will further illustrate how each pixel brings about a subtle but important change to the space.

In the mean time, I’d like to reiterate how humbled I am by the reaction to the product and how excited I am to be working with the JS-Kit team in this space at this time in the Internet’s history.

I look forward to hearing from each of you about your thoughts and feelings on our direction, and shaping our road map directly from your feedback.

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

I just posted a summary of the current data portability landscape to the Official DataPortability Blog.

From the post:

Closed platforms are like ice cubes in a glass of water. They will float for a while. They will change the temperature of the liquid
beneath. Ultimately, however, the ice cube must eventually melt into the wider web.

Facebook’s success with Facebook Connect can and will further drive innovation in the community to develop an open alternative.

Facebook’s success will (like Google, Microsoft and Yahoo, AOL, Myspace, countless major media properties and countless small startups) to create alternatives. At least some of those participants will recognize (if they have not already) that the most open among them will earn both the respect and the market share of the next phase. Moving from Facebook Connect’s ‘data portability’ to Interoperable DataPortability.

A web of Data.

That’s a landscape where we can continue to innovate on a level playing field.

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?