How to get your apps ready for Facebook’s OAuth 2.0 upgrade
September 16th, 2011 By nFriedly
I just finished a writeup on the necessary JS changes to support Facebook’s OAuth 2.0 upgrade, and then Hilary did a followup post on the server-side.
The upgrade enabled right now, but it gets forced out on October 1st. These two posts should give you all you need to know to get your site ready for Facebook’s upgrade:
Part 1: JavaScript - JavaScript changes for Facebook’s OAuth 2.0 upgrade
Part 2: PHP / Backend – Server Side changes for Facebook’s OAuth 2.0 upgrade
Also worth noting, there’s a lot of good information on Facebook’s Developer Blog.


I’ve seen a lot of confusion about this lately, so I thought I’d make a quick writeup to explain how facebook does it. (I’ll also give a quick tip on how you can do it yourself.)
Most anti-spam methods used by websites today are annoying at best. They use impossible-to-read captcha images, or they make users jump through some kind of hoop to get the email address instead of just clicking on it. This can mean lost sales and opportunities for you, because each hurdle turns away more users. 

The twitter callback feature is nice – it makes it extremely easy to to add a twitter feed to a page. But to get the most benefit out of it, you really need to understand what it’s doing.
SEO and SEM is all the rage these days. You can do all kinds of modifications to your website, but the age-old adage still holds true: