Over the last few weeks we have noticed several developers misleading our users into clicking on links, adding applications and taking actions. While the majority of developers are doing the right thing and playing by the rules, a few aren’t – and are creating spam as a result. Going forward, if you are deceptively notifying users or tricking them into taking actions that they wouldn’t have otherwise taken, we will start blocking these notifications. The bottom line is that if the notifications you send are the result of a genuine action by a Facebook user and that action is truthfully reported to the recipient so they can make an informed decision, you should have no problems. If you do find some notifications blocked, it was probably because this wasn’t the case and we will be happy to inform you of some best practices by other developers that have prevented this issue.
If you've been blocked by us for deceptive notifications, the error message you will see is - 200 Permissions Error.
If you've been blocked by us for deceptive notifications, the error message you will see is - 200 Permissions Error.
Recent News
Updates to the Facebook Home Page
February 4, 2010
New Terms for Advertising Providers on Facebook Platform
February 3, 2010
HipHop for PHP: Move Fast
February 2, 2010
Communicating Directly with Your Users via Email
January 20, 2010
Building on our Commitment to Open Source Software
January 12, 2010
Postcards from December Developer Events
January 6, 2010
December 2009 Platform News
December 31, 2009
A Look Back on the App Economy of Facebook in 2009
December 22, 2009
