This technique is now deprecated.
This used to tell Google how to index the page.
https://developers.google.com/webmasters/ajax-crawling/
This technique has mostly been supplanted by the ability to use the JavaScript History API that was introduced alongside HTML5. For a URL like www.example.com/ajax.html#!key=value, Google will check the URL www.example.com/ajax.html?_escaped_fragment_=key=value to fetch a non-AJAX version of the contents.
I just dealt with this myself, and here's the part that bit me:
In your step 5... It's possible for a user to register for an account with you entirely separate from their Facebook ID, right? Then some other time they log in with Facebook.... And you just created them a second account and lost their first one.
There needs to be a way to be logged in to your web service, then log in to facebook, and capture the association between the facebook ID and the local account.
Apart from that, your plan sounds solid.
Update: Facebook has added a doc outlining such a scenario HERE
Best Answer
So /me/albums returns an array of Album objects, each of which has an
id.If an album had an id of 99394368305, you can go to
https://graph.facebook.com/99394368305/photos
to get an array of photo objects.
Each of these will have the
pictureandsourceproperties to get the image data from facebook.They will all have an
imagesarray as well if you want pre-scaled images instead of just the originals.All the facebook queries give JSON back - I'm assuming that you know how to parse this?