tekArtist

From “Platform Internationalization“:

… we have a quick way for applications to integrate with users in new locales. We are now sending a param “fb_sig_locale” to all canvas pages that signals the locale set for the visiting user. Feel free to use this to begin localizing.

Good thing to know, since Facebook is now available in Spanish, with French and German to come shortly.

From “OpenSocial or OpenGadget? - ReadWriteWeb“:

Steve O’Hear (who edits our digital lifestyle blog last100) has an interesting post on his ZDNet blog that questions whether Google’s OpenSocial initiative is at all about data portability, or if in fact it really just about widget standardization. O’Hear quotes heavily from a recent article by Marc Canter, who is a strong advocate for open standards and data portability, that ran on CNet.

I see the same issue with Facebook’s JS Client Library.

I love client-side technologies, but I’m increasingly thinking that the propagation of such libraries is calculated by the providers more in terms of securing data and activity custodianship, as an alternative to truly opening one’s data APIs, rather than with scalability and processing decentralization in mind, like some argue.

It’s not a bad thing by any stretch, but I’m not sure associating them with true openness and data portability is entirely appropriate.

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.

From “FBJS/Animation - Facebook Developers Wiki“:

FBJS exposes a powerful animation library which gives developers an easy way to improve their user interface with a line of two or code. All animations are CSS based, so a working knowledge of CSS will really help you out here. An open-source version of FBJS Animation that will work on pages outside of Facebook is available at: http://developers.facebook.com/animation/.

Via ReadWriteWeb and the Facebook Developer blog.

To the left, Facebook’s status edit field in the standard web interface. To the right, the equivalent status edit field, but in their iPhone interface instead.

Spot the difference. ;-)