This week we launched several new features and how-tos:
In an effort to further simplify building on Platform – and in response to developer feedback – we are announcing that we have deleted the following two Platform policies this week:
FPP IV.4: You must provide users with an easily identifiable "skip" option whenever you present users with an option to use a Facebook social channel.
FPP IV.5: You must not provide users with the option to publish more than one Stream story at a time.
We removed section IV.4 because it is no longer necessary in light of our existing policy which requires that apps obtain user consent whenever publishing on a user’s behalf.
We deleted section IV.5 to open up opportunities for apps to enable a user to share a story on more than one friend’s Wall at a time. Publishing multiple Stream stories via a single share option can be an effective tool in enabling communication among friends and creating a more natural sharing flow for the user. Examples of positive use cases are enabling users to share gift cards, events, and concert tickets that they have purchased for more than one friend, without requiring the user to click on multiple share options.
Please note the importance of using discretion when providing users with the option to publish more than one story at a time, as this functionality may result in negative user feedback which could exceed our spam thresholds. We highly encourage limited use of this functionality and continued review of your App Insights to ensure that users are responding positively to all Stream stories generated by your app. Additionally, it remains a best practice to utilize Requests as a means for users to invite friends to your app.
While apps must continue to adhere to our policies, we are excited about these changes and think this will create new opportunities for developers on Facebook Platform.
You can now use any app which you’re a developer of to generate access_tokens to run the APIs on the Graph API Explorer.
We are adding a
max_age field to the activity and recommendations plugin, which imposes a limit on activity and creation time of articles that are surfaced in the plugins. This allows you to ensure that old and outdated articles don’t show up in these plugins.
HTTP GETrequest to:
Previously, when apps sent notifications to users (available by posting a request to the
apprequests connection of the
User Graph object, as documented in Social Channels), the bookmark counters were incremented, but the message included with the notification was not shown. As of this week, if you send an app to user notification, we will also display the notification message in the apps or games dashboards. This provides app developers a more effective way to communicate application-level updates to users. Note that the ticker count is now shown in bookmarks, hovercards and, for games, in the games ticker. As a result of this change, your users may see an increased number of notification messages from your application.
As always, we recommend that notifications be limited to only those that have directly useful or actionable content.
We updated the FQL documentation for the following tables:
88 docs under review
Bugzilla activity for the past 7 days:
Developer Forum activity for the past 7 days: