KWPro.net

Don't read this unless you're a nerd or are involved in a Facebook project.  But I found this little line out:

"You cannot convert user data you receive from us into Independent Data (e.g., by pre-filling user information with data obtained from the API and then asking the user to save the data)."

I have a huge problem with this line because of the fact that Facebook's API makes available a fair number of user information fields.  In fact, those fields are easily controlled by the user's privacy settings.  However, with the Facebook Connect platform, you're attempting to encourage better user experience through sharing user connectivity information by essentially porting the user from Facebook to your application.  I think Facebook is heavily contradicting themselves in what they expose through their API and their data policies.

I can agree that storing or even caching the data beyond a 24 hour period might be a stretch.  But the prefilling part I think allows for a better experience because you can help fill out legitimate profiles in doing this.  Otherwise, it's practically a waste not to be able to utilize these capabilities.  Certainly, from a developer's point of view, you don't want to continuously make calls to Facebook over the network to retrieve profile information.  That simply is inefficient and uneconomical, especially for high traffic sites.

In short, what's the point?