Then in March, Yahoo! announced their service sign-on, called Yahoo! Updates.

Now, this week, Twitter have announced their connection service, called ‘Sign in with Twitter‘. It too gives you a secure authenticated access to your information and contacts, in exactly the same way the others do – except this time, it’s Twitter.

You might ask if we have three, do we need a fourth? Have you ever used any of the other three?

But don’t dismiss it, or think it Twitter are jumping on to any kind of bandwagon, Twitter’s implementation is fundamentally different to the others – and it could cause quite a stir.

The problem with the other services (ultimately the problem with the platforms) is, more than often not, they are completely closed and non-portable. Although you can sign-in to a third-party site and access your data, there’s a lot of limitation to what you can retrieve and publish. These popular social networks have grown and amassed huge amounts of members and data which they horde and keep to themselves. I’m not talking about privacy, I’m referring to data portability.

The infrastructures are like locked-in silos of information and each built differently, because, either, they never considered that you’d want to make your data portable or they didn’t then want (or see value) in you moving your data anywhere else. The services they’ve created to ‘connect’ to your data are also proprietary methods – custom built to channel in and out of those silos. Each of those services too, are singularities, they won’t work with each other.

Twitter though, have come up with a solution that adheres to agreed upon standards, specifically, by using OAuth to facilitate it’s connection. Technically, it’s significantly different, but in practice, you can expect it to do everything the others can do.

The community’s thoughts

Yahoo’s Eran Hammer-Lahav (a frequent contributor to OAuth) has written a good post discussing his thoughts, he says it’s ‘Open done right’ – no proprietary ’special sauce’ clouds interoperability as happens with Facebook Connect. I think he’s right.

He looks at what happened when Facebook Connect was introduced, that they essentially offered third-party sites two key features: the ability to use existing Facebook accounts for their own needs, and access Facebook social data to enhance the site. The value of Facebook Connect is to save sites the need to build their own social layer. Twitter though, is not about yet another layer, but doing more with that you’ve already got.

Marshall Kirkpatrick also wrote about the announcement, his metaphor for the other ‘connection’ services best describes how they function – ‘it’s letting sites borrow the data – not setting data free’.

But then he talks about Twitter ‘as a platform’, and I think this is where things get interesting. He says:

Twitter is a fundamentally different beast.

All social networking services these days want to be “a platform” – but it’s really true for Twitter. From desktop apps to social connection analysis programs, to services that will Twitter through your account when a baby monitoring garment feels a kick in utero – there’s countless technologies being built on top of Twitter.”

He’s right. Twitter apps do pretty much anything and everything you can think of on top of Twitter, not just the primary use of sending and receiving tweets. I love all the OAuth and open standards adoption – but that’s because I’m a developer, but thinking about Twitter as a platform makes me wonder what kind of effect this will have on the users, how it could effect the climate, even landcape, of social media if, already being great, Twitter is given some real power. 

People have long questioned Twitter’s future – it’s business model, how it can be monetised, those things are important – but where can it otherwise go and how can it expand? Does it need to ‘expand’? It’s service is great it doesn’t need to start spouting needless extras and I don’t think it will. But in widening it’s connectivity, it’s adaptability, I think could change our perception of Twitter – it’s longevity and road map, the way we use it and think of ourselves using it.

My Thoughts

Irrelevant of Richard Madeley or Oprah Winfrey’s evangelism, Twitter is an undeniable success.

When Facebook reworked and redesigned their feed and messaging model, I almost couldn’t believe it. What was the ’status’ updates, basically IS Twitter now, and that’s it’s backbone. It’s Twitter’s messaging model, it asks ‘What’s on your mind?’.

I’m probably not the only one who thought this, I’d guess any complaints about this being a bit of a blatant rip-off were bogged down by all the negativity about the interface redesign.

I think Facebook realised that Twitter has become a real rival. I think (and I guess Facebook also think) that as people become more web-savvy and literate to these sociable websites, they want to cleanse.

The great appeal of Twitter for me was, ingeniously, they took a tiny part of Facebook (this is how I saw it two years ago anyway) and made it their complete function – simple, short updates. Snippets of personal insight or creative wisdom, it didn’t matter really, what was important was it ignored the fuss and noise of whatever else Facebook had flying around it’s own ecology (and this was before Facebook applications came around) and took a bold single straight route through the middle of it.

Looking back, a lot of Facebook’s early adoption could be attributed to people growing restless with the noise and fuss of MySpace at the time – Facebook then was a clean and more structured an option.

I remember Twitter was almost ridiculed for basing it’s whole premise on such a minute part of Facebook’s huge machine. Now look at the turnaround.

Now people are growing up out of Web 2.0 craze. A lot went on, there was a lot of ‘buzz’, but a lot of progress was made in connecting things. People now are far more connected, but perhaps they’re over-connected, struggling from what Joseph Smarr calls ’social media fatigue’. People they have multiple accounts in a ton of dispersed and unconnected sites around the web – true, each unique and successful for it’s own achievements – but it can’t go on.

Twitter for me is streamlined, cleansed, publishing. Whether talking about what I’m doing or finding out information from people or about topics that I follow, the 140 character limit constrains these utterances to be concise and straight-to-the-point pieces of information. The ‘@’ replies and hashtags are brilliant mechanisms conceived to create connections between people and objects where there is almost no space to do so.

I use my blog to write longer discourse, I use my Twitter to link to it. Likewise with the music I listen to, I can tweet Spotify URIs. I link to Last.fm events and anything particularly good I’ve found (and probably bookmarked with Delicious) I’ll tweet that out too.

Twitter for me is like a central nervous system for my online activities. I won’t say ‘backbone’ – because it’s not that heavy. Specifically a nervous system in the way it intricately connects my online life, spindling and extending out links, almost to itself be like a lifestream in micro.

Recently, I saw Dave Winer’s ‘Continuous Bootstrap‘ which although is admittedly a bit of fun, describes the succession of platforms deemed social media ‘leaders’ (see the full post here).

What I initially noticed is that he aligns successful platforms – blogging, podcasting – with a single application: Twitter. It doesn’t matter whether he is actually suggesting that Twitter alone is as successful as any single publishing form, but it did make me wonder if Twitter, rather than being the current ‘holder of the baton’, will actually be the spawn for whatever kind of Web-wide platform does become popular next.

If the real Data Portability revolution is going to kick in, if it’s on the cusp of starting right now and everything will truly become networked and connected – would you rather it was your Twitter connections and voice that formed that basis for you or your Facebook profile?

I know I’d much rather read explore the connections I’ve made through Twitter. The kind of information I’d get back from the type of people who’d connect in this way would be far more relevant from my pool of Twitter connections rather than the old school friends and family members (notoriously) who’ve added me on Facebook, the kind that just add you for the sake of it.

If Web 3.0 (or whatever you want to call it) is coming soon, I’d rather detox. Twitter is slimmer and still feels fresh to start it out with. For me, Facebook feels far too heavy now, out of date and messy. Maybe I’m being unfair and I feel that way because I’ve fallen out of touch with it and now I visit less frequently, but all the negativity hasn’t done it any favours – and those complaints aren’t unfounded.

This week though, Adobe and Facebook announced a partnership they’d managed to keep neatly under wraps and have now released a new official open source client library for Actionscript 3.

This joint effort is intended to be a complete resource supporting all Facebook APIs, including Facebook Connect, for all Flash and Flex applications for Facebook.

Over on the Adobe’s Facebook Developer Connection, Adrian Ludwig (Adobe) and Josh Elman (Facebook) talk about the library and the partnership. There’s also documentation, example applications, quick starts, inspiration and code.

In his post, Serge Jespers points to a nice quick start by Danny Dura that uses the library to set up a simple connection to Facebook in about ten minutes.

You can tell both Adobe and Facebook are excited about this, adding social elements to games, user experiences or interactions makes them endlessly more engaging, it almost goes without saying. But now that these experiences can be as easily enabled – and in my opinion, enhanced - by Flash, I hope will prove to facilitate some great applications.

It’s equally beneficial for Facebook and Adobe. It means even more applications for the Flash platform and an easily entry point for yet another set of developers to integrate with the Facebook API.

And to help kick that off, Rich Tretola at InsideRIA has announced a new series of articles covering development with the new AS3 library, authored by Mirza Hatipovic – an ambitious 20 articles, from a simple Hello World to advanced PHP and database-supported applications.

I’m particularly looking forward to seeing and playing with the Facebook Connect API – not sure if InsideRIA will cover these – but hopefully whatever I do get up to, I’ll get round to writing about.

I’ve spoken about Friend Connect and Facebook Connect a of couple times already as they vie for the mantle of the primary single sign-on for social web applications, but I hadn’t heard anything about Yahoo! offering an implementation on their part – but it turns out to be a pretty good challenge.

They announced on their Developer Network Blog yesterday, that it’s a collaboration with JS-Kit, a leading distributed social network that currently connects over 600,000 sites through powering comments and ratings services. JS-Kit have already got some huge implementations, including sites for AOL, Evite, and Sun Microsystems.

As the JS-Kit blog explains, in this scenario these third-party sites can share user-generated content (e.g. blog comments) directly to a user’s social connections on Yahoo! via the “Updates from My Connections” feed.

This new capability offers a potentially massive new distribution channel for content and a great engine for driving referral traffic from Yahoo!’s global audience. The integration with the Yahoo! Social Directory API enables these sites to allow users to leverage their Yahoo! identity and display their Yahoo! profile photo with their comments. By enabling commenters to use their Yahoo! profile commenting, publishers can build a stronger sense of community at their sites.

Yahoo! have implemented the OAuth open standard to achieve this, a trusted connection to third party sites, not only making users more willing to add content, but by leveraging the social profile data already stored by Yahoo!, makes the commenting and rating an easier process.

This in turn not only means no need for re-registration (cue repetitive form filling), but also a singular, portable syndication of activity can be aggregated on Yahoo! for those users, which, as Marshall Kilpatrick suggests, could then be used by site owners to access verified information about their readers’ profiles and interests.

If this were possible, this could be used to serve more relevant content to those users as well as offer those site owners assurance as to who is contributing to their sites.

Yahoo! talked about their Open Strategy back in October, so it’s good (and about time!) to see some of this come to fruition. They’ve hit the ground running, but the JS-Kit support won’t win this alone – those sites also support Facebook Connect.

I’m more impressed with Yahoo! for consistently championing open standards, as they do with SearchMonkey also, so hope this will expand to other networks in the future. But as much as I enjoy a third contender to the table heating things up, I hope this doesn’t result in three (or more) incompatible platforms heading in their own directions and we’re back to square one.

Josh Elman, Facebook Platform Project Manager, joins him – offering a little technical history and strategy behind the application platform and Facebook Connect also.

It’s a good introduction to building Flash applications using the Facebook API. It’s clear that building on the Facebook platform grants developers an equal opportunity to create powerful and successful social experiences.

As Ted and Josh describe, by utilising Facebook users’ social contexts and by the ease of which you can distribute through the social graph, applications can generate a huge amount of traffic – and as Josh puts it, developers can profit wildy.

Ted gives a simple overview of the architecture of a Facebook application, the various application states and talks about FBML, Facebook’s XML mark-up – and shows how to build a simple single-component Flex application that really demonstrates how easy Facebook have made the information retrieval possible via the API.

The Q&A is worth listening to (it starts around 37 minutes), Ted and Josh discuss important development aspects outside of the actual coding – how hosting is managed, handling session keys and such.

But Ted also points to a promising looking Actionscript library designed for Facebook application developers, simply called The Facebook Actionscript API - which definitely sounds worth checking out (no pun intended).

As yet, Facebook only ‘officially’ support their PHP library, but continue to work with developers in the community to support the other languages. Josh claims this will only improve over the next couple of months and through the year – hopefully (it sounded) to develop similar ‘official’ library counterparts.

Ted’s also posted his Facebook on The Flash Platform sample files.

But if these platforms are successful, what will that actually be like? The demo sites Google provides are good for functional demonstrations but little else. There’s a complete list of sites that use Facebook Connect up on their dev wiki – there’s Joost, Netvibes and TechCrunch, but no-one with such a diverse and active user base like Twitter.

Then on Monday came on the news that Twitter chose to Connect with Google’s service. It’s strange that there wasn’t more made of the announcement, considering what could come of it.

Twitter hardly said much about it at all on their blog, Google covered it in more depth but also provided the first real recognisable use case for an integrated site. Now whenever you join a ‘Friend Connected’ site, you can use your Twitter profile to join their service. From there, you can see of a combination of your followers and those who you follow that are already on the site and connect with them there too. You can tweet about your find from the connected website’s portal.

Getting a big site like Twitter on board will really kick Friend Connect up a gear, undoubtedly it’ll receive a massive increase in attention. But it’s not like Facebook Connect is by any means down or out – it’s so early. If anything, the introduction of these services to such widely used web apps as an almost unblinkingly ’standard’ feature (this will eventually boil down to a simple ‘Connect’ button) could positively change users’ perceptions of them to being just commonplace. I’m sure that’s the ultimate intention, but right now it’ll work in favour for any such service, be it Facebook Connect or any other.

It’ll be a while before we see any real difference in the reception or growth of implementation for either service, whether by then we have a preferred leader or not.

I’m interested to see how Facebook will respond in aiming to get as big a site as Twitter integrated with Connect. Prior to the Twitter inclusion, I felt that Google’s Friend Connect came across almost like a developer’s toolkit – like a set of ready-made widgets to enhance onto your site, boosted by the capability to network centrally. But now I’ve seen it in action, Facebook have a undeniable rival product.

It should be said of course that Twitter hasn’t really chosen Google over Facebook. Biz Stone wrote that there was hardly any effort required on Twitter’s part - Google maybe just got in there first.

It’s in the same post he goes on to say that Facebook Connect integration is already in development. Twitter officially announced integration with MySpace and the Data Availability initiative seven months ago – they’re embracing everything they can, good on ‘em.

Both services are very similar. Essentially, each functions to simplify the connection between social and non-social websites by offering connectivity (and some functionality) of each’s proprietary central platform on 3rd party websites.

The idea is that a user can ‘Connect’ with whichever service the site has employed and find users with whom they’ve already connected with on the other services – rather than creating a new account, profile, repeat the steps of entering information to then find the friends you’ve already added over and over again with every other social-enabled web app you’ve used previously.

I first saw Facebook Connect in August with their demonstration service  The Run Around. There, you could ‘Connect with Facebook’ to initially join the site and immediately see who else (of your Facebook friends) has joined too. This is all outside of the Facebook chrome, not on the Facebook domain. What’s more, as well as interacting with the linked data pulled from Facebook, the website could push data back in. The actual site intended to track your running routes and times, so when you submitted a new ‘run’, it would publish to your live newsfeed on your Facebook profile.

The idea is simple, the effect could be game-changing. It’s been met with both cautious optimism and healthy skepticism.

If this becomes as massive as it could be, we could see a single sign-in that abolishes the need to register and re-register for every newly launched social app. We’re already experiencing social fatigue within that process as consumers and as developers, we’re having to build whole registration and authentication systems from scratch every time. Plugging into a platform like this – that we assume to be secure and trusted – could offer a means to develop and deploy services much easier and faster.

But can we trust – or do we want to trust – a propriety platform to do this for us? The idea of a single social graph isn’t new, but I don’t know if I want Facebook to offer it. I’d much prefer FOAF – but how many people outside of the development world have heard of it?

I feel I need to write another post entirely about OpenID, OpenSocial and OAuth entirely – services that can’t go unmentioned here – but Marshall Kirkpatrick at ReadWriteWeb wrote a direct comparison of Facebook Connect and OpenID that asks some interesting questions as well as offering a good introduction to the open source services anyway. Although he started by discussing as to which of the two should website owners use to authenticate and learn about their users, the community expanded his initial mindmap to cover pretty much every angle in the comparison – and it’s very detailed, see it here.

He also asks, even if it doesn’t become the dominant identifier online, will Facebook’s challenge breathe new life into the movement for open source, standards based, federated user identity?

Then there’s Google Friend Connect – launched in public beta the same day as Facebook Connect went public for 3rd party sites. This does use a blend of the open source services, but although integrating the open standards might suggest a weightier development process, the first thing to notice is a far less developer-oriented implementation than Facebook Connect.

Using Facebook Connect is down to the site creator to construct and integrate an interface to facilitate the connection – Google Friend Connect is widgety, with pretty much zero coding other than cutting and pasting directed portions. Similarly with the functionality, Google offer widgets for simple commenting on pages, media sharing, or rating content. With Facebook Connect you have to write that yourself – although admittedly, you then have full reign on design and interaction.

There’s a demonstration video on the Google blog’s announcement of the beta launch.

It’s not like this is just a two-horse race though, or that someone won’t work out a way two use both anyway. Google and Facebook are in direct competition, but attempting to open the Web in this way extends far beyond them.

What I find interesting is the interoperability. These technologies aren’t semantic, but do push the exposure and interoperation on a user’s social graph with ideas akin to the Semantic Web – utilising data to extend single-site online identities and networking social connections.

They’re not Semantic Web efforts but they have similar aims. Friend Connect’s goal is an open social web, the Semantic Web is – quite simply – a fully understood, completely open web, not only it’s social domain.