Policy Roadmap: Facebook’s New Popup Feed Form Rule Now in Effect
Last week, several new policy changes went into effect on the Facebook Platform. This week, another important new policy regarding the way developers can use Facebook’s News Feed “feed forms” has gone live: now, feed forms cannot be popped up without “explicit user intent.”
This means that developers can no longer show popup boxes prompting users to publish content to their profile (and thus their friends’ News Feeds) without users explicitly choosing to do so. Until now, many of the largest apps have grown by frequently and aggressively prompting users to publish content into the stream.
As a result, apps that heavily relied on the News Feed for distribution and reengagement could see significant traffic decreases over the coming weeks- some have already been pulling back on this lately. Already, many social games are off their December traffic highs, but it’s too early to tell if this is due to policy changes or the seasonality of the holidays. We’ll be keeping close watch on AppData.
For now, here’s the current state of the Developer Roadmap – however, at this point, it’s looking like either the next week is going to be a very busy one, or perhaps more likely that some of the items slated for “December 2009″ are going to slip into 2010.
Already Launched
1. Simplified policies posted, verification program ended, and “extending verification standards to all applications”
2. Platform Live Status tool launching, which will show “updates on platform stability and load”
3. Stream story formatting changes (1 image shown by default, few lines of text, 1 action link)
4. New “add bookmark” button
5. All stream publishing APIs beside Stream.publish, Facebook.streamPublish, and FB.Connect.streamPublish will no longer be supported (going into effect December 20)
6. Feed forms cannot be popped open without “explicit user intent” (note: this is a new Facebook policy) (going into effect December 20)
Coming December 2009
7. New email permission API (developers can ask users to share their email address)
8. Access point to invites will be moved “to either a filter in Inbox or surfaced in the Application and Games Dashboards”
9. User-to-user Inbox APIs will be launched
10. Application bookmarks moving from the bottom menu bar to the left side of the home page
11. Counter API launching (counts can appear on home page application bookmarks)
12. Applications and Games dashboards launching
13. New application branding on canvas pages launching
14. Revamped developer site launching
Late December 2009 / Early January 2010
15. Notifications API (both app-to-user and user-to-user) will be removed (note: Facebook says this will happen “30 days after email permission is available”) (this was originally scheduled for “December 2009″)
Late 2009 / Early 2010
16. Requests API will be removed (note: Facebook says this will happen “30 days after launching new Inbox sharing”)
17. Profile boxes will be removed (application tabs will be the only way to integrate into the profile page at that point)
18. Improved analytics and APIs launching
Early 2010
19. Open Graph API launching













December 22nd, 2009 at 7:33 pm
Remember vista popups? When there is a skip option then why, after all, thousand clicks? publish, publish and then publish.
December 22nd, 2009 at 7:59 pm
I didn’t see a mention of the smaller application tab space (from 760 down to 520), though I may just have missed it. That was slated for Dec 2009, but I spoke to FB this week and they say it won’t happen until Feb 1, 2010 at the earliest. So, there’s that.
December 22nd, 2009 at 8:01 pm
Also, I didn’t opt to use Facebook Connect to post that previous comment (although I have used it in the past) and entered my name, email and url as a normal wordpress comment, and it apparently logged me in and posted as my FB user instead. Before my comment, I saw the “connect using Facebook” button. After I posted it, I am now logged in using Facebook. That’s a bit of a security issue, no? If I were on a shared computer, it could easily have posted as someone other than me through no ill-intent on my part.
December 22nd, 2009 at 8:27 pm
Thanks Alison – we’ll look into that.
December 23rd, 2009 at 8:56 am
Dangit. And now this post was just tagged in a google alert hit on my name. While I don’t care that my name can be linked back to this particular site, I protect my privacy for exactly these reasons, and am always extremely choosy about where I use FB Connect. :(
This is as much Facebook’s fault for screwing up the privacy settings though. Previously, I would just be tagged as ‘Facebook User’. I’m still *fuming* over that, and am tempt to close down my personal FB account for that reason.