Monday, July 21, 2008
Very Important New Facebook App Procedure
As Facebook moves to the launch of the revised interface, the application adding/authorizing procedure is becoming more refined. New code is due to roll out today (Monday, 7/21).
As we knew, users will no longer add applications. Now, they will authorize applications to access their user data. The former post-add URL on the app setup page is now the post-authorization URL and behaves in the same way so you can use the callback at that URL to store allowable information.
Users can opt out of sharing their data either globally in their profile (for all apps) or by not authorizing an individual application.
The change is a simplification for the user; for apps it's pretty much the same except that the once ubiquitous require_add calls need to be removed. (This is discussed in the book because it's been known for a long time--require_login is the preferred code.)
The require_add call will remain because in the case of Facebook Pages (not users), the Page (via its administrators) will be able to add apps.
As we knew, users will no longer add applications. Now, they will authorize applications to access their user data. The former post-add URL on the app setup page is now the post-authorization URL and behaves in the same way so you can use the callback at that URL to store allowable information.
Users can opt out of sharing their data either globally in their profile (for all apps) or by not authorizing an individual application.
The change is a simplification for the user; for apps it's pretty much the same except that the once ubiquitous require_add calls need to be removed. (This is discussed in the book because it's been known for a long time--require_login is the preferred code.)
The require_add call will remain because in the case of Facebook Pages (not users), the Page (via its administrators) will be able to add apps.
Subscribe to Posts [Atom]
