layout: post title: Google Friend Connect paves over your site and plonks down a social network created: 1229412591 categories:

• Web 2.0 tags:
• distributed social networking
• Farmstead Wines
• Google
• Google Friend Connect
• Jim Pick
• OpenSocial
• Redanyway
• Twitter
• Social Media

Since my post on Redanyway, I've gone a few steps further into experimenting with Google Friend Connect.

Basically, it allows you to drop in a members system / social network onto any site. It doesn't need to be a CMS or a dynamic system at all, since it consists of just some Javascript that gets inserted wherever you like. You create a new network / site at the Friend Connect home, and then go on to upload a couple of files to your server. Select some widget options, copy and paste code, and you've got a place where visitors to your site can join your site's network.

Now, as opposed to creating yet-another-profile, visitors use their (presumably existing) Google Account to login. Google Accounts have Profiles attached to them (since about December 2007, although it's only recently that they are being talked about more). Here's my Google Profile.

There aren't really any built in "friends" in your everyday Google Account / Profile (in fact, in Google Reader it's really hard -- I enjoy Brendon Wilson's rant on this), so you can also activate several other networks to automatically connect with "friends" from those systems. Twitter and Plaxo are two that I experimented with. Orkut is also supported ... but when was the last time you signed into Orkut?

Twitter does that oh-so-lovable enter your username and password trick that leaves me feeling more than a bit queasy, but since I have a good size network, it seems pretty useful. You can then post to Twitter from within the widget to invite other people to join the network you've just entered. Plaxo does the better looking remote authentication and works just fine ... except I don't really use Plaxo all that much anymore.

OK, so now you're a "member" of a local "network"! What next? Well, on to the world of "Social Gadgets". There are ratings and a comment wall, and also support for OpenSocial apps. The OpenSocial apps are, I guess, the interesting part of this in the future, sort of allowing bridging of different data with mashups unique to the members on your own site. Except there's not much there today. Comments and ratings are fairly uninteresting when dynamic sites powered by Drupal or WordPress either do these things out of the box or can add them easily with a couple of plugins.

But....I'm not completely down on this system. In fact, I've been talking to Anthony of Farmstead Wines, who is a heavy Twitter user, about adding Friend Connect to his website. He can use his large Twitter network to build a social network around his website. It doesn't do a lot of interesting things *today* ... but you can already see how member profiles on Google Maps and other mashups will be trivial to implement in the future. Adding full network functionality to his website would cost a lot of money and time if needing to be "built in" directly, whereas the Friend Connect route lets Anthony build his network today, centered around the permalink of his own website (as opposed to some other system like ye old Ning).

I've included a Google Friend Connect network widget and wall widget after the jump. Jim Pick has also created one for the Vancouver Freebase.

Will you be adding Google Friend Connect to your site? Do you find it useful? Where is this heading?

Below is the Google "Wall Gadget" -- it lets you post comments and post YouTube links. The scope of this wall is the "entire site" -- you can make one of these that apply to a particular page or a unique id.

So far, I continue to be underwhelmed. Come on Google, ride on top of OpenID, and plug this directly into a site's existing user account system...

Update: Jim Pick left a comment that went so far as including a screencast showing OpenID support in Google Friend Connect. So, my bad, Google Friend Connect does support OpenID directly. More correctly what I meant with my closing commentary was that, rather than logging into Google's infrastructure, that this should be tied into my sites existing account system. Which already supports OpenID.