Facebook开发者博客最新更新内容：Facebook为应用开发商推出平台政策备忘录；Facebook用户可以通过点击请求通知直接访问应用；iframe应用开发商需填写HTTPS URL实现应用访问；Facebook在欧洲举办开发商活动；FQL（Facebook查询语言）变更和Facebook添加新功能。

平台政策备忘录

开发商如果不清楚自己的应用是否违背Facebook的服务条款或者平台政策，如今可以参考Facebook公布的平台政策备忘录。该备忘录以PDF格式出现，文字通俗易懂，并有多种语言版本，内容涉及隐私、数据、内容、社交渠道、品牌化及功能指南几大方面，开发商在发布应用前可对照查看产品是否违规。要注意的是，以奖励手段让用户邀请朋友或同朋友分享内容，支持用户每天发布数条动态消息，或者在广告中盗用用户相关数据等行为，都是违规频率较高的做法，Facebook政策明令禁止这种行为。

这个备忘录有助于减少Facebook开发者论坛一些常见问题的咨询量，与此同时，开发商再也无法辩称不知应用违反了Facebook政策，侵害了用户权利，更有助于政策落到实处。

branding and functionality

早前在界定上比较模糊的，比如禁止出现损害Facebook产品的概念或功能（其中包括：“阻止用户标注除真人以外的事物”、“不提示用户好友已被移除”。）据称Facebook有可能凭这条规定，取缔某些未违反其他明文规定的应用。现在厘清这些概念后，开发商应该对此感到高兴，因为这可以节省他们的大量时间和金钱，避免在某些有违Facebook政策的应用上做无用功。

请求通告导入应用页面

上月Facebook引进了请求功能的2.0版本，该系统支持用户及应用自动生成请求，并将通告发送给接收者。在此之前，这些通告会导入游戏仪表板（Games Dashboard）或者应用仪表板（Applications Dashboard），用户可以在那里管理自己的请求设置，但该请求不利于用户重访原来的页面。为了提高请求的回访率，用户如今点击通告后，会直接进入一个canvas应用界面。

notifications

这个变化让请求功能成了开发者更为可行的病毒式传播渠道，而用户在应用内而非仪表板中管理请求设置，则更有助于提升应用的MAU数值。

HTTPS  URLs安全访问设置

今年1月份，Facebook宣布用户可以通过HTTPS浏览网站，增加访问安全性。Facebook还新增了需开发商填写的Secure Canvas URL域名，这样他们的应用才可以通过HTTPS被用户浏览，否则Facebook会弹出确认页面，提醒用户他们使用的是标准的HTTP浏览网页。

2月份，Facebook开始支持Pages展示iframe应用，但如果用户采用了HTTPS功能，iframe Page tab apps加载的时候会呈现空白状态，无法在Page导航菜单中显示。Facebook在3月16日开始推出了一份漏洞报告，这一举措获得了许多开发商的支持。

3月17日，Facebook为开发者应用引入了新的命名Secure Tab URL，开发商必须填写这项内容，否则用户无法以Page标签格式访问他们的应用。

Page Tabs

消除自动生产图片信息

Facebook开发商现今可以消除用户通过应用上传图片时，自动出现于用户界面的信息。这样一来，如果开发商想发布图片的相关信息，就得通过用户来编辑，用户墙上不会出现两个重叠的信息。这使得更多用户会点击应用版本的图片，而不是分化成两个阵营，这样就会有更多用户回访同一个应用。开发商只需把“no_story=1”参数添加到“POST”，就可以消除这种信息，避免出现累赘感。

Facebook在欧洲举办开发商活动

Facebook将于本月在欧洲举办系列活动，促使本土独立开发商及初创公司能够不断推陈出新，与同行、风险投资家碰面交流，共同探讨平台发展，同时通过Facebook团队了解最新技术更新情况。

3月25日的HACK Berlin包括座谈会和黑客马拉松两部分。3月29日的Facebook Developer Garage Paris将是一个混合主题的会议，同时还会介绍Facebook在法国和比荷卢地区的平台合作关系新主管Julien Codorniou。此外，3月31日的Startup Day London将是Facebook团队、风险投资者以及社交游戏初创公司的交流盛会。（本文为游戏邦/gamerboom.com编译，转载请注明来源：游戏邦）

Platform Updates: Platform Policy Checklist, App Request Notifications Lead to Apps, HTTPS for Page Tabs, Hack EuropeMarch 21st, 2011

Facebook’s latest updates to the Developers Blog announced a new policy checklist for app developers, that users are now directed straight to an app when they click through notifications from app requests, the need for developers to fill in their HTTPS URL for their iframe apps, several Facebook-hosted events for developers in Europe, and a few other FQL changes and functionality additions.

Platform Policies Checklis

Developers curious as to whether their apps violate any of Facebook’s terms of service or Platform policies can now refer to the Platform Policy Checklist. Available as a .PDF in several languages for review before an app’s launch, the list includes privacy, data, content, social channel, branding, and functionality guidelines in easy-to-understand terms. Some of the policies that are more frequently violated, such as rewarding users for inviting or sharing with friends, allowing users to publish more than one news feed story per day, or using data about users in ads are all clearly prohibited.

The Checklist will help reduce support and developers forum inquiries by answering some frequently asked questions. The document also will make it difficult for developers to claim that they didn’t know that their app violated Facebook’s terms or exploited users, and will therefore make policy enforcement more straightforward.

One policy that has been hazy before –the prohibition of “concepts or features that undermine the Facebook product” — includes examples such as “don’t encourage users to tag anything other than real people” and  ”don’t notify users of friend remove”. This could be referenced in the future as a reason for Facebook banning certain apps that don’t necessarily violate another specific policy. Developers should by happy to have this resource, as reviewing it during conceptual planning for an app could save them a lot of time and money that might be wasted creating an app that gets disabled soon after launch.

App Request Notifications Lead to Apps

Last month, Facebook introduced Requests 2.0, a system that allowed for user-generated and app-generated requests to be sent that trigger notifications for the recipient. Previously, these notifications led to the Games Dashboard or Applications Dashboard where users could manage their requests, but they weren’t leading to reengagement as they were designed. To increase the reengagement spurred by these requests, users are now brought directly to a canvas app when they click the notification generated by an app’s request.

The change makes requests a much more valuable viral channel to developers, and should boost MAU numbers since it pushes users to manage requests from within apps, not the dashboards.

HTTPS URLs for Page Tab Apps

In January, Facebook launched the option for users to browse the site over HTTPS for increased security. It also added a Secure Canvas URL field that developers needed to fill out to allow their apps to be browsed through HTTPS, otherwise Facebook would show users a confirmation screen to inform them they’d have to browse over standard HTTP.

In February, Facebook began allowing Pages to display iframe apps, but if users had HTTPS enabled, iframe Page tab apps would be blank when loaded and would not appear in a Page’s navigation menu. A bug report was filed on March 16th and it received a number of up-votes from developers.

On March 17th, Facebook introduced a new field in the developer app called “Secure Tab URL” to the Facebook Integration section of the Developer app. Developers must fill in this field, or users won’t be able to see or access their app in Page tab form.

Supressing Auto-Generated Photo Stories

Facebook app developers can now suppress the auto-generated stories that appear on a user’s profile when they upload a photo through the app. This wayif a developer wants to publish a story about the photo, perhaps after a user has edited it through the app, there won’t be two similar stories stacked on a user’s wall. This will lead more users to click through the app’s version of the photo instead of being split between the two, exposing more users to a link back to the app. Developers simply add the no_story=1 parameter to the POST to suppress the story and prevent redundancy.

Facebook Developers Events in Europe

Several Facebook-hosted events will occur in Europe this month, allowing independent developers and startups in the region to build apps, meet peers and venture capitalists, discuss the Platform, and learn about technical updates from Facebook’s team.

HACK Berlin on March 25th will include panels and a judged hackathon. Facebook Developer Garage Paris on March 29th will include a mixer and an introduction to Julien Codorniou, Facebook’s new Head of Platform Partnerships for France and Benelux. Startup Day London on March 31st will allow Facebook team members, VCs, and employees of socially-focused startups to get to know each other.（source:insidefacebook）