Archive | Facebook Platform RSS feed for this section
Dashboard Roadmap. API Available

Dashboard Roadmap. API Available

Facebook has just announced that the new Dashboard API is now available for testing. According to the dashboard roadmap the Facebook Dashboard API lets you integrate your application into the Application Dashboard or the Games Dashboard (depending upon the type of application you have). These dashboards help users discover and engage with your applications on Facebook. They display which application’s users and their friends recently used as well as any news your applications wish to communicate to users.
The Dashboard API integrates with the Games and Application Dashboard in two ways: It gives you the ability to post news items to a user’s dashboard, providing information to the user and giving the user the opportunity to take action. It lets you set a counter as a lightweight way for you to inform your users to take action within your application.

There will also be two types of news that the applications can post on to the dashboards – Global and Personal News Items. Global News Items will be visible to all of the users of the app, while the Personal News Items will be a way to communicate with only 1 user of the app.

Games Dashboard

Games Dashboard

The Dashboard API lets you set the counters that appear next to your application bookmark under the profile picture (if the user bookmarked the application) and in news items on the dashboard. The counter informs the user in a lightweight way to take an action in your application.
After you set the counter for a user, Facebook clears the counter when the user clicks your application’s bookmark. However, when the user visits your application’s canvas page, you must call dashboard.clearCount to reset the counter.

Also, in this week’s code push Facebook updated some API calls (events.invite, group FQL table), so that they can now work without session keys.

Facebook’s New Privacy Settings

Facebook’s New Privacy Settings

Facebook announced about their new Privacy Settings earlier today. Facebook says that the changes are made to simplify the Facebook privacy settings and give users more control,  but according to the Electronic Frontier Foundation these changes are made to push users to publicly share even more information than before.

For app developers these changes will be very useful. Users won’t be able to hide information such as gender and friend lists (and other Publicly Available Information – PAI) from apps, they can’t opt out of the Facebook API (by the “Do not share any information about me” setting) anymore and even if a user hasn’t granted permission to any apps the PAI of the user will still be available through the friends of the user who use the application.

According to Chris Cox (VP, Product Management) “everyone” will be the new default for status updates, which will make Facebook more like Twitter and give greater access to information for developers. This means if Facebook allowed Google to pull user status updates for its new real-time search,  Facebook could have replaced and even eliminated Twitter.

Below is a video demonstrating these new changes.

Google’s Realtime Search Will Include Facebook Pages

Google’s Realtime Search Will Include Facebook Pages

Google announced today, at their Search event,  that its new real-time search will also include status updates from Public Profile Pages, aka Facebook Pages.

No word yet if it will include Application Profiles or not, but for now it certainly won’t include user Profile updates.

This can really increase the significance of Facebook Pages and events like the streaming of Alicia Keys’ new album on her Facebook fan page can be accessible (and searchable) for a broader audience.

Google Realtime Search

Google Realtime Search

Facebook Announces Safety Advisory Board

Facebook Announces Safety Advisory Board

Facebook has just announced the formation of a Facebook Safety Advisory Board.

According to Facebook the Safety Advisory Board is “the latest step in its commitment to improve safety on Facebook and across the Web”. The Facebook Safety Advisory Board consists of a group of five leading Internet safety organizations from North America and Europe that will serve in a consultative capacity to the company on issues related to online safety. The five organizations on the board are Common Sense Media, ConnectSafely, WiredSafety, Childnet International and The Family Online Safety Institute (FOSI).

The board will come up with ways to better educate teachers, parents and teens about online safety and will address more issues regarding safety on Facebook.

Get Your App Reviewed

Get Your App Reviewed

Are you a developer on Facebook? Have you created the most amazing Facebook Application or game but nobody knows about it yet?
Ask us to review your app today!

In the submission page, make sure you describe your application and tell us why do you think it has the potential to become the next killer app on Facebook. Describe all of its features in detail and most importantly include the link!

Good luck!

Migrate to streamPublish before December 20

Migrate to streamPublish before December 20

Yes. Facebook will deprecate all previous feed publishing functions after December 20, 2009 and your applications need to move to the OpenStream API by then. The new API implements the Streams feature, which is based on the Activity Streams standard. That’s not news. And nothing after this point is news anymore, but a short tutorial on how to get ready before Facebook deprecates a few functions which your application might be using, eventually destabilisng it. One short tip at the end of it all for your application.
So as per the new Streams functionality rolled out a few days ago across all Facebook profiles, as an application, you will need a special permission, publish_stream, to automatically publish stories to a user’s wall which is visible to the user’s friends. You need to ask for that permission by prompting the user. Until you don’t have that permission, you can use the FBJS call Facebook.streamPublish to render a feed form and have the user approve or cancel the publishing of the story right there.

As I reckon, employing the FBJS call might be a better thing to do as users may not readily give your application permission to print stories to their walls whenever you want. In fact, let me present the case of why you should ONLY use the FBJS call for all the feed story publishing needs in your application.

What Facebook.streamPublish does is show a feed form to the user which has two choices, either to publish the story contained in the form to the user’s profile or skip it. And before I proceed on feed forms, a legal advice here. You cannot show feed forms to the user whenever your application feel likes, but you have to present the user a choice as he/she takes any action on your application, if they would like to have a feed story printed on their profile page and then only. The clause that mandates this behavior is DPP.VI.1 which says “You must not display a Feed form unless a user has explicitly indicated an intention to share that content, by clicking a button or checking a box that clearly explains their content will be shared.”. Moving on, a typical feed form looks like this:

How a feed form looks like

You can supply the title(Fappside.com – Facebook News), the link of the title, the description text, thumbnail paths which will be resized to 90×90 pixels, other custom properties(Founded and Category), and action links(Become a Fan). The arguments have to be passed in a JSON array alongwith some other parameters. The function is of the form:

Facebook.streamPublish: FBJS call method and parameters
Facebook.streamPublish(user_message, attachment, action_links, target_id, user_message_prompt, callback, auto_publish, target_id);

I will detail two parameters only, the rest you can find explained here.
auto_publish: If this is set to true, and the currently logged in user has already given your application stream_publish permission, the user won’t see the feed form and instead the story will get published automatically. If you set AUTO_PUBLISH false, the feed form will show up no matter what.
target_id: This argument tells on whose behalf to submit the story. If this is set to null, it defaults to on behalf of the user currently logged in. If it is the ID of a Facebook Page and the currently logged in user is the admin of that page, the story is published to the wall of the Page, on behalf of the page.

Here is some example code to print a story using Facebook.streamPublish in PHP, FBML & FBJS. I am assuming you have a application already set up and you have a FBML canvas page.

PHP: Setting up the Feed Story parameters
$feedStory = array(
‘name’ => ‘Fappside.com – Facebook News’,
‘href’ => ‘http://fappside.com’,
‘description’ => “Fappside is all about what’s in and out of Facebook, real time”,
‘properties’ => array(‘Category’ => ‘Facebook News & Reviews’, ‘Founded’ => ‘November 2009′)
);$feedStory['media'] = array(
array(
‘type’ => ‘image’,
‘src’ => ‘http://profile.ak.fbcdn.net/object2/1487/68/n187160399906_2453.jpg’,
‘href’ => ‘http://fappside.com’
),
array(
‘type’ => ‘image’,
‘src’ => ‘http://fappside.com/wp-content/themes/headlines/thumb.php?src=http://fappside.com/wp-content/uploads/2009/12/pen.jpg&h=90&w=90&zc=9&q=95′,
‘href’ => ‘http://fappside.com’
)
);
FBML + FBJS: Setting up the Javascript variables and a link to invoke the feed form
<script>
var js_feedStory = <?php echo json_encode($feedStory); ?>;
var js_actionLinks = <?php echo json_encode(array( array(‘text’ => ‘Become A Fan’, ‘href’ => ‘http://www.facebook.com/fappside’))); ?>;
var js_targetId = null; //Keep this null if you want the feed story to appear on the user’s profile
var js_userMsg = ”; //The string which appears in the text input field. Note that the user can change this before publishing
var js_headlineMsg = “What’s on your mind?”; //A text label above the text input field prompting the user to write something in the text input field
var js_callback = null; //A Javascript callback function to handle any desired flow after the story has been published or cancelled(skipped)
var AUTO_PUBLISH = false;
var js_actorId = null;
</script>

<a href=’#’ onclick=”Facebook.streamPublish(js_userMsg, js_feedStory, js_actionLinks, js_targetId, js_headlineMsg, js_callback, AUTO_PUBLISH, js_actorId);”>Publish</a>

The above setup will print a feed story that looks like this by default:
Feed story default view

and like this when the See More link in the feed story is clicked:
Feed story after clicking on See More

That’s it with the Facebook.streamPublish method. Do let me know in the comments section if you find anything while doing this yourself, interesting or annoying. Now onto the tip I promised.

This is actually handy and we have been looking for it since sometime. The Add Bookmark feature on the application canvas pages, instead of relying on the humility of the sole link in Facebook’s bottom navigation bar with the application icons to work its magic. All you have to do now is embed the FBML <fb:bookmark /> on your canvas pages and a pretty button will be rendered. It even works on profile tabs. If the user has already bookmarked your application, Facebook will know that beforehand and won’t show the button. There may also be situations where you want to know in your code if a specified user has bookmarked your application or not, and for that use the following FQL query, where $uid is the ID of the user you want to learn about.

PHP: FQL Query to retrieve information from bookmarked column of Permissions table
$facebook->api_client->fql_query(“select bookmarked from permissions where uid=’$uid’;”); //will return Array ( [0] => Array ( [bookmarked] => 0/1 ) )

I think I have talked enough uptil now. I am looking for topics to write on that may interest you, so if you already know what you like to see, holler here and I will take note, and might do something. Looking forward to a conversation now with you in the comments section.

Become a Writer for The Facebook Journal

Become a Writer for The Facebook Journal

The Facebook Journal is looking for talented writers who would like to get published and reach our ever-growing tech-oriented audience. If you have a blog, have written for blogs before or even if you are new to blogging but you know a lot about Facebook, you can become a published author on The Facebook Journal and even earn some cash.

Here are the categories in which you can contribute:

Platform News
Application/Game Reviews
Application/Game News

Benefits:

Reach to our ever-growing tech-oriented audience

Your own Google Adsense Ad on your posts that will let you generate income from your content

The Facebook Jounral is new, but it is being heavily promoted among people interested in Facebook Platform Development. Writing for The Facebook Jounal will let you make a name for yourself and also generate income on your posts. We expect our writers to write a minimum of 1 post a week. All content will be subject to moderation but you are free to write just about anything concerning the above mentioned categories.

To become a writer, please fill in the Writer Application Form.

[Photo: Flickr - Athena]

Delays, Again…

Delays, Again…

As Don wrote in a post yesterday, Facebook is having a hard time sticking to the dates they’ve set in the Developer Roadmap. Although, we’ve heard that Facebook is planning to end the Verified Apps program today, still there are no news yet about the new Email feature that was promised to go live in November.

Pete Bratach, who is a technical writer at Facebook and according to his tag-line ”…likes keeping you up to date” didn’t mention the email feature at all in his November 2009 Platform News post today.

It’s a good thing they’ve released that Platform Live Status page where developers get notified about the condition of the Platform. Ever since it was released some major problems have been reported including a severely degraded performance of the Platform, which affected mainly FBML based applications, and problems with the Quick Transitions feature (which is still not fixed, opposite of what the Platform Live Status is saying). Let’s just hope it is all connected with with the upcoming redesign or the roll-outs of the new features and that we will have somewhat of a stable platform for the beginning of the new year.

Developer Roadmap Delays

Developer Roadmap Delays

Facebook introduced the  Facebook Developer Roadmap on October 28, 2009. This is what the description of the roadmap reads:

For the first time in this level of detail, we will provide a roadmap to help you anticipate future changes and opportunities. Like all roadmaps, it may shift slightly, but we will share insight into what is happening as these details are available. We’ll keep you posted about the progress of these changes and what they mean for you over the next two quarters.

For the month of November Facebook had 4 new features to be launched, and while most of them are now live, one of the most anticipated ones is nowhere to be seen. I’m talking about the new email sharing feature, which allows developers to gain access to the application’s users’ primary email address. This means that app developers can store real email addresses and contact their users directly. Currently applications can request permission to email users, but the emails get sent via the Facebook API and are not visible and cannot be stored.

Facebook Redesign

Facebook Redesign

Also, once this feature is live, the new notification methods will become active (after 30 days) and most likely this is when the new redesign will be activated.

Facebook Bans Ad Networks

Facebook Bans Ad Networks

Facebook just banned several ad networks from their Platform. Nick Gianos, a member of the Facebook Platform team explained the move by saying that those providers violated Facebook Policies and Principles. According to Nick Gianos, applications that continue to use the services provided by the above mentioned providers will risk enforcement action.

Here is the complete list of banned ad networks:

Gambit
Social Hour
SocialReach
Tatto Media

Something tells me this list will continue to grow. Just yesterday Facebook announced that they will give time to all the developers to comply their applications with the Platform’s new Policies, but why aren’t they doing the same for ad networks?

SocialReachSocialReach