October 2013 Platform Changes Facebook

The link to the full story is here

A year ago we started bundling Platform changes into quarterly migrations. Today, we are announcing the set of changes included in the October 2013 migration, available in the app dashboard today.

The following changes can be enabled/disabled using the "October 2013 Breaking Changes" migration in the app dashboard until October 2nd when they will go into effect permanently for everyone:

Game Achievement API update
Game Achievement action custom properties will appear in the 'data' field, and consistent with other Open Graph Actions.

/USER_ID/likes default update
Currently the API returns all likes by default. After the migration, fetching a user's likes via the Graph API will return 25 results at a time. We've added pagination to the results so you can page through to all of a user's likes.

/POST_ID/likes update
Apps will be able to retrieve all likes on a post (rather than the first 4 as it is today) through paging. As a result of the functionality update, the like count will be moved to the summary field.

Removing 'network' based privacy
As we have deprecated 'network' based privacy settings on Facebook, we are removing the network privacy field from Graph API and FQL. Currently if an app attempts to create a post with a network privacy, it will default to 'only me'. After the migration period, posting with a network privacy will result in an error.

Removing the ability to post to friends' timelines via API
We have found that posting content via API (stream.publish) on a friend's wall lead to a high incidence of user dissatisfaction (hiding content, blocking the app). After the migration period, posting content to friends' timelines via stream.publish will no longer be allowed. Please use the Feed Dialog for posting.

FQL and Graph API limit=0 change
Currently, we have a bug where limit=0 returns all results. After the migration period, specifying a limit of 0 in FQL or the Graph API will return zero results.

The following changes will go into effect on October 2, 2013:

Native iOS and Android apps must use SDKs for login
Native apps on iOS and Android must use our iOS and Android SDKs to initiate Facebook Login. This will provide the best user experience and result in higher conversion. Please see our SDK documentation for details.

Please note: if you are using Apple's Social framework, you may continue to do so, but ensure that if the user is not using the iOS integration, that your app falls back to the Facebook SDK for iOS. This can create more work than necessary, though, so we highly recommend using our SDK instead.

Some developers will receive Dev Alerts in the app dashboard when we detect usage of the changing features. However, we encourage all developers to validate apps with the migration enabled before the effective date to ensure functionality. Please see the Developer Roadmap for more info.