In a new
blog post, Facebook has announced that it will proceed with further changes to its
Developer Principles and Policies effective December 16th. These changes,
again, concern how 3rd party applications interact and engage with Facebook users.
A large part of these changes is an increasing focus on enforcement. Paul Jeffries, Facebook's Head of Platform Policy Team, says, "we're investing in personnel and technology to help us better uncover and rapidly respond to policy violations. You'll continue to be able to launch an application without prior approval... but you should expect it to be proactively reviewed at any time... Those who try to circumvent the spirit of the policies or principles, or exploit a "loophole," will be subject to enforcement."
Enforcement means, temporary suspension of some or all application functionality, or your application being permanently disabled.
List of changes highlighted in the
developer wiki:
- Provide a link to your privacy policy in the Info section of your Application Profile page and on every page of your application. (DPP I.1)
- You can evolve and develop your application, but don't repurpose it. (DPP II.6)
- Be sure users can easily report inappropriate content, and be responsive to their reports. (DPP IV.B.2)
- Don't undermine the integrity of the social graph by encouraging the creation of fake accounts or inauthentic friend connections. For example, don't gate content or provide rewards based on the number of a user's friends who also use your application. (DPP V.2)
- Don't prompt users to send invitations, requests, generate notifications, or use other Facebook communication channels immediately after a user allows access or returns to your application. (DPP V.4)
- Your "skip" button must be adjacent to and the same height and design as your "send" button. (DPP V.5.)
- Don't send multiple communications in response to a user's single action. (DPP V.7)
- Certain data fields you can submit to us through the API (e.g., the user_message parameter) must be reserved for content generated solely by the user. (DPP V.8)
- Don't prompt users to bookmark your application (e.g., by using a modal window or pop-up dialog), and instead provide users with a button for users to explicitly invoke any bookmark option you provide. (DPP V.10)
Not happy about these changes? Tell Facebook
here, but I doubt it'll do much good.
Comments [0]