Facebook Pulling an Open Social?

From “JavaScript Client Library for Facebook API“:

This JavaScript client library allows you to make Facebook API calls from any web site and makes it easy to create Ajax Facebook applications. Since the library does not require any server-side code on your server, you can now create a Facebook application that can be hosted on any web site that serves static HTML.

Now let’s compare this to the Open Social API description:

OpenSocial provides a common set of APIs for social applications across multiple websites. With standard JavaScript and HTML, developers can create apps that access a social network’s friends and update feeds.

Is it just me or are others also thinking this is a missed opportunity for FB to take part in Open Social?

On the other hand, it could also lead to just that with what could be a simple wrapper to interconnect both ecosystems. That’s if FB decides not to go that way on their own and doesn’t expressly block such development through technical or legal means.

WP Plugin Challenge: Who Wants to be a Five-Thousander?

From Jeff Chandler’s “Calais Offers WordPress Plugin Bounty“:

Calais which is a metadata generation web service that is powered by Reuters is offering up a $5,000.00 bounty to anyone who can develop a plugin that meets the following criteria: tag auto suggestion, semantic cloud, GUID incorporation.

I can’t go for this one, having other immediate priorities and commitments, but it sounds like a neat and challenging project to tackle.

PDO 2: Request for Comments

From “php.pdo: PDO 2: Request for Comments“:

It became apparent over the past year or so that PDO has been a good and valuable addition to PHP. Like JDBC in the Java world, PDO offers similar advantages, such as consistent data access APIs and better consistency across the various drivers. It has also become clear that there is still room for improvement around the functionality, consistency and broader vendor support for PDO.

I love PDO. My only real pet peeve with it is that it wasn’t right in PHP 1.0.

I’m looking forward to see some of the proposed improvements come to life.

XMPP as the Future of Cloud Services?

From Matt Tucker’s “XMPP (a.k.a. Jabber) is the future for cloud services“:

There’s a new firestorm brewing in web services architectures. Cloud services are being talked up as a fundamental shift in web architecture that promises to move us from interconnected silos to a collaborative network of services whose sum is greater than its parts. The problem is that the protocols powering current cloud services; SOAP and a few other assorted HTTP-based protocols are all one way information exchanges. Therefore cloud services aren’t real-time, won’t scale, and often can’t clear the firewall. So, it’s time we blow up those barriers and come to Jesus about the protocol that will fuel the SaaS models of tomorrow–that solution is XMPP (also called Jabber) . Never heard of it? In just a couple of years Google, Apple, AOL, IBM, Livejournal and Jive have all jumped on board.

An interesting read on an increasingly attractive architecture.