With the World IPv6 Launch coming on June 6th 2012, Facebook has committed to enabling IPv6 access for our users on most of our HTTP and HTTPS endpoints. Based on the results of last years IPv6 test on June 8th 2011, we are confident that enabling IPv6 on our platform will be a success. On May 18th, we will be enabling IPv6 on beta.facebook.com ahead of World IPv6 Launch to give our developer community time to discover issues and report bugs back to us.
IPv6 is vital because the Internet's original addressing system (IPv4) has run out of free space. Since every device on the Internet relies on a unique address to communicate, we must transition to IPv6 which provides over 4 billion times more addresses than IPv4. IPv6 will ensure everyone (users, ISPs, governments, and companies) have direct and open access to the Internet.
We are in the process of updating the JS SDK to be more modular and strict. This means we will be enforcing the inclusion of the fb-root element and correctly initializing the SDK with FB.init.
appId : 'YOUR_APP_ID',
channelUrl : '//WWW.YOUR_DOMAIN.COM/channel.html',
status : true,
cookie : true,
xfbml : true
The SDK inserts elements into fb-root, which expects to be positioned relative to the body or relative to an element close to the top of the page. Read more about fb-root here. Make sure you call FB.init if you plan to use any of FB.api, FB.ui or FB.Canvas.
As announced on the Roadmap and Developer Blog, the following changes are going into effect on May 2, 2012:
offline_access Permission Removal
offline_accesspermission is deprecated and will be removed May 1, 2012. Until then, you can turn this change on or off using the "Deprecate offline access" migration. Please see the Removal of offline_access Permission doc for more details.
Removal of group_type and group_subtype columns from group FQL table
We remove the
group_subtypecolumns of the
groupFQL table. Please ensure that your apps are not utilizing these columns.
Removing support to claim Domains using Page ID - Originally scheduled for April 1st, 2012
We will remove the ability to claim domains with a Page ID. The recommended option for claiming domains is with an App ID or User ID and existing domains that have been claimed will continue to work fine. After claiming domains, owners are able to view insights or run Domain Sponsored Stories. See the Insights documentation for more on the updated domain claiming flow.
Please check out the Developer Roadmap for more upcoming changes.