Facebook Updating Open Graph Publishing Guidelines
It’s pretty much a given now that Facebook wants every app developer to push Open Graph. As more app developers take to Open Graph and more people become concerned with privacy, Facebook will have to amend their policies to address those concerns. This week’s Operation Developer Love sets some guidelines to address any concerns that users may have with Open Graph publishing their data.
Facebook has updated their Open Graph publishing guidelines to give developers more time to implement the changes that are required of them to create a more secure and user-friendly app ecosystem. That’s why Facebook is introducing a Breaking Change policy into Open Graph guidelines that will give developers 90 days to update an existing app to comply with the new guidelines.
To that end, developers have 90 days to amend apps with built-in watch and read actions. Unfortunately, that means that you can no longer use a custom action for reading an article or watching a video. Even if Facebook previously cleared an app that had a custom action, it must be updated to use built-in actions. After the change has been made, you must resubmit your app to be approved.
If you happen to use built-in watch and read actions with your content, you can only publish on a person’s wall after they have engaged with the content for 10 or more seconds. If the video is less than 10 seconds, a user must watch the entire video to have it published. While Facebook doesn’t explain its reasoning, it’s pretty easy to see that they’re hoping to cut down on spam. There are probably some app developers who immediately publish actions even if the user in question only visits the site for a few seconds.
Another pillar of the Open Graph platform is the tagging of people and locations. New guidelines have been put in place to discourage warrantless tagging of everybody on somebody’s friends list. Apps must now only encourage users to tag friends if they have actually done something together. It’s also encouraged to only tag a place if the user is currently there.
Aside from changes to its Open Graph publishing guidelines, Facebook has also added an FQL query tab to the Graph API Explorer. It’s pointed out that you can still run FQL queries the old fashioned way through issuing an HTTP GET request. The tab just makes it easier and faster to experiment with various queries.
The bug report this week saw 150 bugs reported with 18 of them being fixed. Check out the post on Facebook to see the full list of bugs that were fixed. Be sure to also check back next week for the new list of breaking changes coming in July.