Have Geek Brain

"Gotchas" on Facebook Application Development

I dashed to Facebook dev for a couple of weeks now and it was ... difficult. Not from "how does it work?" point of view, but from "why doesn't it work!" one.

I'm curious about what "gotchas" are, unexpected behavior, or just mistakes people have seen with Facebook and what they've done to compensate.

My current albatross is a (beta) DataStore API; its quite unreliable. GetObject calls can complete with partial return values, so an object with fields {foo, bar, val} created with values ​​{1, 2 3} could presumably return {1, 0, 3}, {0, 0 , 3}, etc. I have yet to find a suitable job.

Running up is the inability to use <fb:if-*>

on the user's profile page. I got compensated for some true twisted English and <fb:visible-to-owner>

.

0


a source to share


2 answers


I run several when creating Desktop Application, I created a dedicated desktop page on Facebook wiki to make it easier for others. The two biggest "gotchas" I found caused the app to appear as a "desktop app" on the Facebook users settings page, and the desktop app would log the user out of the browser session in addition to the desktop app. Answers on this wiki page.



+1


a source


I'm having trouble with Facebook not following the current OpenAuth 2.0 standards. They are close, but not close enough.



But this is partly because I want to use the DotNetOpenAuth library, which Facebook doesn't like that much or vice versa, not sure here: P

0


a source






More articles:


All Articles