There are a lot of players vying to become your gateway to rest of the web: Facebook Connect, OpenID, Sign In With Twitter, MySpace ID, and Google Friend Connect just to name a few. It’s Facebook Connect however that seems to be leaving all of the other connect methods in the dust. This includes Google Friend Connect, which without a major social network to back it has floundered in terms of adoption.

Google’s not about to hand over this potentially vital market over to Facebook, however. A few weeks ago, the company simplified the Friend Connect implementation process. Today, the search engine giant has introduced an array of new features that allow users to get to know each other by adding interests, adding the ability to send private messages, and more.

The first part of the new features revolves around what boils down to social networking. For example, site owners can use Friend Connect to ask their visitors about their favorite activities and use that data to help connect people with similar tastes. It also gives the site owner a lot of valuable data.

The other part of the announcement really focuses on getting website owners to adopt Friend Connect. Google touts new options such as building custom newsletters, creating gadgets and links that target the interests of every user, and improving the relevancy of Google ads. The company can launch all the user-based features it wants, but without site owners adopting, it won’t matter.

The push by Google is smart, but Facebook’s built-in social advantage is something the search giant just cannot beat. Leveraging the data and log-ins of 300+ million users is Facebook’s huge advantage, and unless Google can find a way to parry that, these new features, while welcomed, may not help spur a new wave of adoption.

If you want to learn more, Google has created a new overview video of Google Friend Connect which explains both the basics and the new features:

Join the Mashable Google Friend Connect Community

You can join our Frend Connect community using the widget below!

Tags: friend connect, Google, google friend connect

Facebook Connect launched to the public less than a year ago, and already it’s seen an incredible amount of traction. Unfortunately, for those people with little to no coding experience, implementing Facebook Connect has seemed like more trouble that it was worth. Today, Facebook has an answer: Facebook Connect Wizard and Playground.

Facebook writes that “you can now incorporate Facebook Connect into your site in 3 easy steps.” The process is simple. First, you enter the name of your site and its URL. Then Facebook asks you to download and then upload a special file to your site’s main directory. And.. that’s about it. Once you’ve done that, Facebook will present you with its Playground — a list of code snippets you can embed on your site to round out the functionality, including Login buttons, profile photos, publishing items to News Feeds, and rendering photos of a user’s friends.

Deciding to put their little wizard to the test, I tried to implement Connect on one of my personal sites (note that I’ve never tried to implement Connect before so I really didn’t know what I was doing). And to my surprise, it worked: I managed to have a very basic form of Connect up and running on my site within all of two minutes. It will obviously take longer to make sure the new icons and buttons play nicely with your site’s design, but it’s really surprisingly easy.

Crunch Network: CrunchBoard because it’s time for you to find a new Job2.0

There’s some excitement around the web today among a certain group of high profile techies. What are they so excited about? Something called WebFinger, and the fact that Google is apparently getting serious about supporting it. So what is it?

It’s an extension of something called the “finger protocol” that was used in the earlier days of the web to identify people by their email addresses. As the web expanded, the finger protocol faded out, but the idea of needing a unified way to identify yourself has not. That’s why you keep hearing about OpenID and the like all the time.

But those standards, while open, have failed to latch on in a meaningful way with the public at large. One of the holdups is that you have to set up a website or service you use to be your OpenID. It’s relatively easy to do, and you may already have one ready to go, but just not realize it. But it’s still kind of tricky to explain to a regular web user — wait, you login with your website?

But something everyone on the web knows is their email address. And they’re conditioned by services like Google and Facebook to use it as their identifier. The problem with it has been that it’s just a string of text, nothing more. You cannot attach information to it to let others know a bit more about you — something vital for true identification. Then idea behind WebFinger is that you should be able to attach any information you choose to your email address.

The excitement today is that a group of Googlers have apparently finally not only gotten Google’s support to pursue the project, but that they have started working the technical details. As Googler Brad Fitpatrick writes today:

In other words, we’ve eliminated both technical & political hurdles. We can now work on this spec, implement, push, try, rinse, repeat…. until we’re all reasonable happy.

Googler Brett Slatkin (incidentally, Fitzpatrick’s partner in making PubSubHubbub) explains to us that while it hasn’t been turned on yet, and that there’s still a lot of work to do on the spec, the idea is to go into testing mode soon. Fitzpatrick notes that there will be a small experiment going on internally with some Googlers’ Gmail accounts.

Without knowing much about the technical details behind it, the core idea behind WebFinger immediately strikes me as a good one. It’s taking something everyone knows on the web (your email address) and making it immensely more valuable as a way to identify yourself and information about you. Exactly what kind of information? Here are some of the ideas from the WebFinger Google Code page:

• public profile data
• pointer to identity provider (e.g. OpenID server)
• a public key
• other services used by that email address (e.g. Flickr, Picasa, Smugmug, Twitter, Facebook, and usernames for each)
• a URL to an avatar
• profile data (nickname, full name, etc)
• whether the email address is also a JID, or explicitly declare that it’s NOT an email, and ONLY a JID, or any combination to disambiguate all the addresses that look like something@somewhere.com
• or even a public declaration that the email address doesn’t have public metadata, but has a pointer to an endpoint that, provided authentication, will tell you some protected metadata, depending on who you authenticate as.

This is definitely something to watch for in the coming months.

[photo: flickr/chris owens]

Crunch Network: CrunchGear drool over the sexiest new gadgets and hardware.

Apparently it’s embrace the developer community day at Facebook. In addition to the news that they are making activity stream data available to third party developers, they’ll also be making an announcement around OpenID, we’ve heard. And importantly, the announcement is that they’ll become what’s called a relying party, meaning anyone with an OpenID (Yahoo, Google, AOL, MySpace are all issuers, and Microsoft is in beta) can create and log into a Facebook account using those credentials.

Let me take a step back. OpenID is a distributed single sign on solution that allows people to sign into different services with the same login credentials. There are two ways companies/websites can participate in the OpenID framework – as “issuing parties” or as “relying parties.” Issuing parties make their user accounts OpenID compatible. Relying parties are websites that allow users to sign into their sites with credentials from Issuing parties. Of course, sites can also be both. In fact, if they aren’t both it can be confusing and isn’t a good user experience.

All the big guys are now Issuing Parties, which allow their users logging in all over the Internet with those credentials. But none of them accept IDs from anywhere else, so anyone that uses their services has to create new credentials with them. It’s all gain, no pain. There are two exceptions – AOL Mapquest and Google’s Blogger – but for the most part the big guys are issuers, not relying parties. And that has led us in the past to accuse them of exploiting OpenID for their own benefit without giving back to the community. See our post Is OpenID Being Exploited By The Big Internet Companies?

Facebook has been a wild card with OpenID. They’ve talked about adopting it eventually, but their Facebook Connect product has actually muddled the situation – Facebook actually competes directly with OpenID when allowing users to sign in to third party sites via Facebook Connect.

Now that’s going to change, and we’ll soon see users have the ability to sign in to Facebook using, say, their MySpace credentials if they choose to. I like the thought of that.

But it still may be a while before we see the other major players take similar steps. Facebook has never really had notion of a user ID – you’ve always logged in with your Email address, which could have come from any number of other services, so Facebook isn’t really sacrificing much here. Instead of a user name, Facebook members are assigned a meaningless user ID number (though they’re experimenting with vanity pages).

Contrast that with Yahoo and Google, both of which have built up their own login systems, which can be used across multiple services using a single persistent account name. Users benefit because they can seamlessly jump between services, and Yahoo and Google get their users to stay within their own suite of products. There’s a good chance they’re not going to give that up so readily.

Crunch Network: CrunchBoard because it’s time for you to find a new Job2.0

As expected since yesterday, Facebook has launched the Open Stream API, which lets third-party developers use Facebook’s activity stream inside their own applications and services.

Developers will be able to filter and remix the stream – consisting of status updates, photos, videos, notes, as well as likes and comments on all the above – as they see fit. They will also be able to create content directly in the streams; for example, an application will be able to change the user’s status update.

Such an open approach did wonders for Twitter, and it means that we can soon expect hundreds of new applications developed for Facebook. We’ll see advanced applications like Tweetdeck applied to Facebook. For many advanced, tech-savvy users, Facebook’s homepage will become obsolete as they move on to applications that offer even more options. It also means that Facebook will get even more free PR as all these new applications start hitting the mailboxes of technology oriented blogs.

All of this will, however, work only for users who give the individual application access to their stream. From the official documentation (emphasis mine):

“Instead of prompting your users for the status_update, photo_upload, video_upload, create_note, and share_item extended permissions, you can simply prompt them for the publish_stream extended permission, and that single permission lets your users update their statuses, upload photos and videos, write notes, and share links all from your application or site.”

Twitter does not have this restriction, and although it probably won’t stop developers from creating applications on the Open Stream API, ultimately it will always mean that all these applications aren’t perfect; i.e., they don’t necessarily deliver all the data you see on Facebook itself.

Beta partners include Adobe, which has created a stream Notifier, and Seesmic Desktop, an advanced Twitter and Seesmic AIR desktop client (and the successor of Twhirl), which now also includes Facebook support, but this latest version is not yet publicly available (some details can be found here however).

More Facebook Resources from Mashable:

- 5 Elements of a Successful Facebook Fan Page

- 5 Tips for Optimizing Your Brand’s Facebook Presence

- New Facebook Pages: A Guide for Social Media Marketers

- HOW TO: Survive the New, New Facebook

- 30+ Apps for Doing Business on Facebook

Tags: facebook, Open Stream API, twitter

Google Friend Connect Is trying to catch up with Facebook Connect, and just now released its first set of APIs, which will let developers integrate Google Friend Connect more deeply into their sites and applications. Google Friend Connect offers a single sign-on service as well as several data portability features.

The new APIs will allow site owners to use both JavaScript and REST APIs to embed Google Friend Connect directly into the markup language of each site and make it easier for to combine it with their existing login systems. Google has also created APIs for developers who want to create plugins for content management systems such as Wordpress and Drupal. Gadget developers now have better authentication options as well. According to the API page:

Friend Connect API’s enable developers to

• Integrate social flows and data directly within a page’s markup, via the OpenSocial standard specification
• integrate existing login systems, registered users, and existing data with new social data and activities.
• Create social gadgets & services that are embeddable within millions of Friend Connect enabled sites.

Of course, Facebook Connect already has its own set of competing APIs (which are the same ones used by its 670,000 application developers). The Google Social Blog has more info.

Crunch Network: CrunchGear drool over the sexiest new gadgets and hardware.

Google is now making it easier for Websites to surface Friend Connect features with what it is calling the Social Bar. This is a toolbar that Websites can add to their homepage or any other page they wish, and then they can add links for drop-down gadgets that lets site visitors do things such as sign in via Friend Connect, see who else has signed in recently, check out comments, or site members, all from Social Bar. Here is an example.

Basically, the social bar is a small strip that webmasters can layer on top of any web page, either at the top or at the bottom. That way, website visitors are provided with a bit of information, and the bar also lets them interact with any social feature the site incorporates through drop-down gadgets. As Software Engineer Christopher Wren explains in the announcement blog post, this is a good way to save on pixel space and keep putting the actual content of the site forward first.

Here are some of the gadgets Websites can include in the Social Bar, from Google’s brand new Social Web blog:

• On the far left, visitors can join your site, see their identity, and edit their profiles and settings.
• Your visitors can also delve into your site’s activity stream to see what’s happening throughout your site. It includes links to recent posts made anywhere on your site, helping other visitors quickly find where the hottest conversations are taking place.
• The wall gadget can host a discussion for the whole site, a section of pages, or each individual page, letting your visitors easily read and leave comments.
• Lastly, visitors can see the other members of your site, check out their profiles to see how like-minded they really are, and even become friends.

The toolbar approach is both an attempt at ubiquity and invisibility at the same time. Google wants Friend Connect to be everywhere, but at the same time it doesn’t want to seem too pushy about being everywhere. Hence, the seemingly innocuous toolbar. But that toolbar expands with pop-down gadgets, which takes advantage of Google’s strengths with creating gadgets in iGoogle and elsewhere. Can a Facebook Connect toolbar be far behind?

Crunch Network: MobileCrunch Mobile Gadgets and Applications, Delivered Daily.

There are way too many comment login systems out there. Each blogging platform (Wordpress, Typepad, Blogger) has its own login system, then there are the cross-platform commenting systems like Disqus and JS-KIT. But many of these will soon give way to Facebook Connect and Google’s Friend Connect.

I am talking about just the ID people use to login, not the commenting systems themselves. We adopted Facebook Connect as a login option for anyone who wants to leave a comment on TechCrunch, and it already accounts for more than 20 percent of our comments. FB Connect is also now available to any of the 500,000 blogs and sites that use the JS-Kit commenting widget, and Disqus is planning on implementing Facebook Connect before the end of the year.

Other blogs are adopting Google’s Friend Connect (which lets people login with various email credentials, or even Twitter). JS-Kit is also working on adding Friend Connect, as well as MySpace ID as login options.

All of this choice is great, except that already there are six different login options in The JS-Kit widget (Guest, Existing JS-Kit, New JS-Kit, Haloscan, OpenID, FB Connect). Pretty soon we’ll need the equivalent of a “Share This” button, perhaps a “Universal ID” button, that will then open up to all the options. But I think that’s too much. Engineers may feel it is egalitarian, but consumers run away when they are presented with more than 3 or 4 options.

That is why I think Facebook Connect and Google Friend Connect will win in the end (Sorry, MySpace). People may have IDs for the various blogging platforms or commenting systems, but most don’t identify with them. It is a necessary inconvenience. They identify with Facebook or their email because that is where they manage their personal and professional lives.

In addition to replicating the comments on your Facebook News feed, the JS-Kit implementation also supports embedding Facebook photos and YouTube videos directly into the comments. It makes commenting much more personal when you know your friends will see it in Facebook. It also has the potential to reduce the amount of comment trolling and general incivility that has taken over many blog comments (we hope).

Update: No sooner did I post this than I learned that not only is Disqus working on a Facebook Connect plugin, but so is Six Apart (for Movable Type), Wordpress, and MediaWiki. Here is an entire Facebook Connect plugin directory. Grou.ps is also adding FB Connect.

Crunch Network: MobileCrunch Mobile Gadgets and Applications, Delivered Daily.

Google’s universal sign-in system, Friend Connect, which just opened to all Websites two weeks ago, now accepts Twitter IDs as a sign-in option. That means when you visit a participating Website that accepts Friend Connect as a log-in option, you can sign in using your Twitter account. If any of the people you follow on Twitter are also members of the third-party site, they will automatically be added as your friends.

Friend Connect also supports IDs from Google, Yahoo, AIM, and OpenID. For instance, I tried this on the Go2Web2.0 blog, which has implemented Friend Connect, and it gave me the option to use my Gmail or Twitter accounts (I could also use Orkut or Plaxo). I used my Twitter sign-in without a hitch. (Update: Actually, this is a little confusing, but it signs you in first using one of the four credentials above and then asks you if you want to add Twitter).

The race is on between Friend Connect, Facebook Connect, and MySpaceID to sign up the most third party sites. Adding Twitter as an issuing party is a big win for Friend Connect because sites are going to choose the sign-in system that gives their visitors the most options and broadest reach.

There is nothing stopping sites from implementing more than one sign-in system, but at some point presenting visitors with too many options becomes confusing. For instance, we use Facebook Connect, in addition to our own sign-in system. Should we add Friend Connect? Probably. MySpaceID?

It’s only been a couple weeks since these have become widely available, and already universal sign-in is anything but. Here is a list of sites that are live with Facebook Connect, and some example Friend Connect sites can be found here (if anyone has a more comprehensive list of sites live with Friend Connect, please add to comments).

Crunch Network: MobileCrunch Mobile Gadgets and Applications, Delivered Daily.

MySpace, in an all out war with Facebook over this year’s prize (socializing the web), is relaunching their Data Availability product today under a new name and announcing some snazzy new partners.

Goodbye, Data Availability. Hello MySpaceID.

Along with the renaming ceremony, MySpace is also announcing two new partners: Netvibes and Vodafone (the latter is an interesting mobile play for MySpace).

MySpaceID is roughly analogous to Facebook Connect, which had their own coming out party last week. Sites can add various elements of MySpace ID to allow their users to log in via their MySpace credentials, display their profile information, and find MySpace friends who are using those sites. Starting early next year, MySpace says, they will add the other features that Facebook Connect has now, such as publishing activities from partner sites to MySpace, and syndicating MySpace activities to partner sites. MySpace will also allow partner sites to take new user registrations beginning with their MySpace credentials and basic profile information.

The crucial difference between MySpaceID and Facebook Connect is the software stack. Facebook uses proprietary software and methods, although they say they will open up over time. MySpace has embraced open standards across the board, including OpenID, OAuth and Open Social. The benefit, they say, is that sites will be able to implement other competing services that are also on the open stack with few implementation changes. Yahoo, for one, is rumored to be taking a similar approach.

MySpace also plays nicely with Google Friend Connect, allowing users to log in to sites that have implemented Friend Connect with their MySpace ID. Facebook stubbornly refuses to play ball with Google – they seem to want that direct software connection with partner sites.

It’s clear that small sites are eating this stuff up (hey, we launched Facebook Connect the first chance we could). But the larger guys are taking their time. MySpace’s original launch partners – Twitter, eBay and Yahoo – are yet to implement it. And few of Facebook’s original launch partners have shipped the service, either (Digg is rumored to be waiting until at least the middle of next year).

But one key feature of both products – the ability to tell MySpace or Facebook a user’s email address and get back all of their friends on those services – is likely to quicken the adoption rate by large partners. They want to fill out their social graph as quickly as possible and link up all those users as friends. Both of these services make that happen.

Screen shots of the details of MySpaceID are below. I’ll be interviewing MySpace COO Amit Kapur on Tuesday morning in Paris at the Le Web conference as well, and MySpaceID will be one important area of the discussion.

Crunch Network: CrunchBoard because it’s time for you to find a new Job2.0