Comment 101 for bug 595265

As I predicted, the bug is still there, and is causing incredible confusion due to its randomness.

To everyone posting "fixes": they aren't really fixes. What's happening is that Facebook is randomly denying requests from Gwibber, because it is generating too many of them (according to Facebook). When you add a new Facebook account, the Add button only appears after Gwibber has received the authentication token from Facebook, but if that request happens to fail, it never appears. It will start working again at some random point in the future, and if that happens to be right after you have tried something to fix it, it will seem as though the fix worked...

One reason that this is so confusing is that Gwibber fails silently. There is no indication whatsoever that a request has failed, which is especially annoying in this case, or when the request was a new post, which will then fail to appear on your Facebook page without any indication from Gwibber that something went wrong. This is something that badly needs to be fixed. If something went wrong, Gwibber should tell you about it (like it used to do in the previous version).

The story that was put out was that once enough people were using the new version the problems would go away, and that therefore the bug was fixed. It is now quite obvious that the problems have *not* gone away, and that the bug is therefore *not* fixed. It would be quite nice if the developers of Gwibber would acknowledge this.