Those Fuckers at Facebook

So last week i attended BarCamp and wrote the BT Mojo application, which lets people have a box on their facebook profile page from which people can send them text messages.

Facebook Screen shot
It does a very simple job, but there was plenty of potential to expand. So yesterday I was asked to present about the work I have been doing over the last few weeks. Clearly I wanted to show my MojoMob application. When I attempted to send myself a text (sad i know) i got the following error message. I knew for a fact that none of the code had been changed since I had last tested and also confirmed the remote file it was calling was present.


The Page at says:

An error occured during a request to a remote server .This failure may be temporary, try repeating the request


The app uses the mock ajax facebook calls which allow you to do ajax type stuff within Facebook. A look around the developer forum shows that I am clearly the not the only person experiencing this issue:

The plot actually thickens when you read some of the posts. The beta facebook site does not appear to have the issue:

Which adds to the confusion? Surely facebook is not changing their code on the production server? Quite worrying if they are.

More worrying is the  fact that the api was changed with apparently no notice and we are yet to see any comments from facebook 12 hours in.   Those fuckers, lets hope its sorted soon.

I talk more about some of the issues with using the Facebook platform in this post


6 thoughts on “Those Fuckers at Facebook

  1. It’s damn frustrating that they don’t provide us with information about errors like this and when we can expect it to work again. This mock AJAX error has forced me to push my work till tomorrow and that sucks.

  2. This is really difficult to take.

    It seems that things change at all hours of the day with no notice to what is changing or how to manage it!

  3. This Mock AJAX error was also happening at around 1am CST on Sept 12th, (about 24 hours earlier than this current reported incident) it lasted for only a few minutes and then went away.

  4. interesting. I wonder whats going on, maybe their production server cant handle its load, that would explain why the beta platform is still working fine, any other suggestions?

Comments are closed.