Last week Facebook announced Open Graph, a way for external sites to connect Facebook’s users and services. Open graph takes what was previously called Facebook Connect a bit further. First, it’s based on using OAuth rather then Facebook’s proprietary system. Secondly, it allows tighter integration with Facebook’s data as well as allowing 3rd parties to locally retain user data for more then 24 hours. This is a huge perk to 3rd party developers; on the flip side this is a huge privacy concern for members. Other additions include the ability for any site to embed some Facebook functionality without requiring OAuth or compromising user privacy, this is done through iFrames.
The OAuth connection allows for more access to user data then ever before. OAuth now has access to profile data and the ability to locally store Facebook user data for periods longer then 24 hours. This empowers developers with the ability to parse through all the user data and make analytical connections that were previously impossible. For example if User X allows access and a week later User Y allows access, if User X is friends with User Y the data is now available to make this connection and any others that come along with the increased dataset. Additionally as an admin for pages that were “liked” you can push page updates to those users.
Overall, Facebook’s Open Graph looks like it’s worth using even if it’s only for the simple marketing benefits by adding a “like” button. Granted the real power lies in the OAuth integration. The biggest winner in all this is Facebook, as all these services places Facebook at the center of it all. As Facebook’s gravity increases they can always switch to a pay system so I don’t suggest relying solely on Facebook for the future of your site/service, but until then no reason not to take advantage of all that Open Graph has to offer.
Facebook: Open Graph
Facebook’s Developer’s guide