Since last Wednesday's update, we spotlighted Bingo Bash and launched the ability for people to play games in News Feed.
Today we added an "FQL Query" tab to the Graph API Explorer to make it easier to test and play with FQL. As before, you can run FQL queries through the Graph API by issuing an HTTP GET
request to https://graph.facebook.com/fql?q=QUERY
where QUERY
can be a single FQL query or a JSON-encoded dictionary of queries. This tab in the Graph API Explorer just gives you a quick way to experiment with queries.
To give people on Facebook the best experience, we’re introducing several new Open Graph publishing guidelines. In instances where these changes require you to modify an existing app, you’ll have 90 days to complete your update per our Breaking Change policy. These guidelines address feedback we’ve received and codify best practices that encourage everyone working with our platform to put user experience first.
Additional publishing guideline
For stories about watching a video or reading an article, you must use the built-in watch and read actions. We’ll no longer approve custom actions for these stories.
90-day update window
Tagging people and places:
Only encourage people to tag friends when they have actually performed an action together. Only encourage people to tag a location if they are currently at that place.
Best practice: user controls for sharing
You should allow people to turn sharing on or off for the content in your app, and the setting a user selects should persist. Learn more about our policies and guidelines:
On June 6th, the following changes will go into effect. For more information, check out the Developer Roadmap.
Removal of FBML
FBML apps will no longer work on Platform. The "FBML Removal" migration will appear and will be enabled for all apps. It will be possible to disable the migration, thereby re-enabling FBML, until July 5, 2012 when the migration and all FBML endpoints will be removed completely.
XMPP Connections must be done over TLS
Apps connecting to Facebook's XMPP service will be required to use STARTTLS for all connections. We will start rejecting unencrypted connections.
Sign up for monthly updates from Meta for Developers.