What all of this means is that Google is working to make Buzz content something that can be used in as many services as possible, while letting as many services as possible come into Buzz.

“The idea is that someday, any host on the web should be able to implement these open protocols and send messages back and forth in real time with users from any network, without any one company in the middle,” says Google software engineer DeWitt Clinton. “The web contains the social graph, the protocols are standard web protocols, the messages can contain whatever crazy stuff people think to put in them. Google Buzz will be just another node (a very good node, I hope) among many peers. Users of any two systems should be able to send updates back and forth, federate comments, share photos, send @replies, etc., without needing Google in the middle and without using a Google-specific protocol or format.”

Google has most recently turned on WebFinger in Gmail (via RRW). WebFinger is described as being about making email addresses more valuable, by letting people attach metadata to them. According to the WebFinger page at Google Code, that can include things like:

- 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.

WebFinger is enabled for all Gmail/Google Profiles with public profiles. Google’s Brad Fitzpatrick discusses more technical details about it here.

Google has released version 1.2.5 of the App Engine software developer kit (SDK) for Python and Java. This happens to be the company’s first simultaneous release for both. The API includes XMPP (also referred to as Jabber) support, which is an open standard for instant messaging. This comes in the form of the XMPP API for both SDKs.

“Like the other APIs that App Engine provides for developers, XMPP is built on the same powerful infrastructure that serves other Google products,” says Google on the App Engine Blog. “In this case, we take advantage of the servers that run Google Talk. This new API allows your app to exchange messages with users on any XMPP-based network, including (but not limited to!) Google Talk.”

Developers involved with the preview of Google Wave can also use the API to build bots that interact with waves. Wave will be available to schools and businesses this fall, by the way.

“We’re very proud of our first XMPP release, but there’s still more work to do,” says Google. “In the future we hope to provide even more functionality to apps, such as user status (presence) and info on new subscriptions.”

More information about the API and SDKs can be found in this post. There are links to documentation and release notes available there.