Tag Archives: Facebook

Friday Links: Facebook filing for IPO?

Filed under Links

Friday Links: So long 2011 edition

Filed under Links

Facebook removing App Profile Pages

Another week, another Facebook change. This time around they’ll be removing the application profile page on Feb 1, 2012. These pages have been confusing over the years. The application profile page looks like a FanPage, but is limited only to the application. These pages allow users to interact with the page like posting to the wall, or adding the application to a FanPage if they are an administrator. Facebook will also migrate the “likes” of the app to an existing page when you, as an administrator, select the page for the app. However, they won’t migrate any of the other page content.

You can get more information on the Facebook Developer Blog.

Filed under Technology

Friday Links: AT-ATs, nerdy vacations, and deadly sins

Filed under Links

Surprise! Facebook is breaking more stuff on January 1st

Facebook is updating their JavaScript SDK by deprecating three functions. The first function,
FB.Canvas.setAutoResize
is going to be replaced with a new function FB.Canvas.setAutoGrow. These functions are used to dynamically change the size of your Facebook canvas and remove the scroll bars from view. If the function is not replaced your canvas will not be displayed as you expect. This change does not effect the FB.Canvas.setSize() function.

The other two functions are part of the FB.Data package of functionality (FB.Data.query & FB.Data.waitOn), and are used to query the graph using FQL. These functions will not be available to new applications and appear to be available for the near future. An alternative to these functions is to use FB.api() to make your FQL call to the graph.

For the full list and dates for Facebook changes look to the Developers Roadmap.

Filed under Technology

Wednesday Links: Because it’s a holiday week

Filed under Links

Nerdery webinar: Facebook breaking change; sky falling?

Many companies who’ve invested in Facebook apps have no idea their code may fail next year, and while this isn’t quite Mayan-prophesy-2012 scary, affected businesses should know that Facebook apps written in FBML will no longer be supported starting in January – and these same apps will no longer exist in June. 

Facebook doesn’t, as policy, tell everyone about such breaking code changes. As nerds who watch their dev blog, we get such scoops – and we’ll share the news if you RSVP for our next webinars, Tuesday, November 29 at 10:15 a.m (Central) and Thursday, December 1 at 3:15 p.m.

We’ll cover how nerds can help businesses protect their social media investments by converting FBML to HTML, and how to tell if your Facebook app is written in code that limits its shelf life. Can’t wait for the webinar to find out how to spot an endangered Facebook app? Check this out:
http://blog.nerdery.com/2011/11/dont-go-breaking-my-app/

Plenty of companies don’t know they have expiring FBML apps – and since Facebook won’t tap them on the shoulder, we’re spreading word to those who wouldn’t otherwise see this breaking-code change coming.  It almost feels like we’re doing a PSA – but yeah, public awareness means business for nerds. The more you know…
Filed under Events, Technology

Don’t go breaking my app

Facebook forewarns that FBML, or Facebook mark-up language, is a dying language. This will force companies with existing Facebook apps to move it or lose it. On January 1, 2012, Facebook will no longer support apps coded in FBML – so, no bug fixes, ever again. More ominously, on June 1 all existing FBML apps – whether bug-riddled or still fully-functional – will vanish, along with user data that, until then, lived in them. Facebook giveth and taketh. But, if you proactively convert your FBML to HTML on an iFrame, all’s well. Not sure if your Facebook app’s days are numbered? Dan will tell you how to tell:

Endangered Facebook Apps in 2012 from The Nerdery on Vimeo.

Call it spring cleaning, as Facebook is purging old tech in favor of something newer and, for them, much more nimble: HTML and iFrames. Whereas FBML hogs HD space on Facebook’s content delivery network, iFrames are hosted on each user’s server.

Sure, FBML apps won’t necessarily break right then on New Years Day, but if they do, there’ll be no easy fix. To be clear, FBML apps will soon no longer exist – let alone work – on Facebook Platform; all FBML endpoints are history, come June.

Now, the good news: There’s time to be proactive, and I’m surrounded by nerds who assure me they can make everything alright. At The Nerdery we’re collectively versed in virtually all programming languages (and can practically write Haiku in them), so converting FBML to HTML is right up our alley – whether we were the original developer of your Facebook app or not. Let me hook you up.

Learn more on Facebook changes in our  previous posts and our upcoming webinars.

Forewarning: Significant Facebook changes are coming

There are a number of significant changes coming to Facebook in the next few months. Many of these effect the code of your Facebook applications.

The biggest change is that on June 1, 2012, your existing FBML applications will no longer work and may ultimately be removed from fan pages by Facebook. From Facebook, “FBML apps will no longer work on Platform. All FBML endpoints are removed as of June 1, 2012.”

If you have an FBML application and you want to keep your application, it’s time to convert from FBML to a new IFrame application.

For December, there are a number of changes that will be implemented.

1. OAuth spec migration
This code change will effect the way your developers access a specific variable. Facebook has changed the variable name and now your developers need to reference this new variable name.

2. Deprecating Dashboard APIs
This code change only applies to you if your application is leveraging the Dashboard API in your application. This is typically not part of the garden variety Facebook applications that have been built. See a list of the API calls that are effected.

3. Apps on Facebook: FB.Canvas.getPageInfo must be called with callback
This code change only effects you if your application is using this method in the Facebook SDK/API. This is typically not part of the garden variety Facebook applications that have been built.

4. Removing Bookmark URL
This is an application configuration and code change. Facebook is removing the “Bookmark URL” from the application’s configuration. The “Bookmark URL” was a way to assign a unique URL to the link to the application icon in the left column. Facebook didn’t like the way developers were using the field by redirecting users. Now, if your application will use a bookmark there is another method, via code, to track the referral from the bookmark.

For more information go to Facebook’s Developer Road Map.

Filed under Technology

New Authorization login screen for Facebook permissons

Facebook is rolling out a new Permissions dialog flow, that includes a set of new screens your users will need to interact with when installing your application. The new dialog boxes include an area when you can provide a description for your users to read before they install the application and an easy-to-read list of the permissions your application will be requesting.

As the new Open Graph is rolled out to the public the permissions dialog box will also include a flow of recent posts from the application.

Like the old permissions dialog box, this only appears the first time the user interacts with the application.

The new flow includes multiple screens, the process is described below:

1. The user is presented with the “Introduction” dialog box.

  • The user will see the application logo
  • The user will see the permissions that are requested
  • The user will read a description of the application
  • The user will see a list of their friends that have accepted the application

2. The user will click the “login” button.

  • If the user is already logged into the Facebook platform the user will be navigated to the next screen.
  • This same dialog will appear if the user is authenticating to an application that is in the Facebook tab/canvas or if the user is on your own website that is using the Facebook APIs.

3. Once the user has logged in the user will then accepted the extended permissions. This dialog box has a text area where you can explain to the user why you need these permissions for your application.

So, this is pretty cool. Yes it’s an extra step, but now as an application owner you have more tool to inform your users about your application.

Read more about this on Facebook’s developer’s blog.

Filed under Technology