Fedora Account System
Red Hat Associate
Red Hat Customer
gwibber seems to be able to show facebook updates, but when I attempt to post to both twitter and facebook, it fails. With no error message saying that it's failed -- I just notice that my status update didn't get posted. It's almost as if I've clicked the icon to disable facebook... which I haven't. The twitter post succeeded. gwibber-2.31.93-1.847bzr.fc13.noarch
Yeah, this is a bit of a perfect storm of fail. If you close out gwibber, then run (in a terminal): gwibber-service --debug -o You'll almost certainly see errors coming from the Facebook API about how the client is being blocked on their end. Basically, here's what's happening. Older versions of gwibber used to be rather... aggressive with their polling of Facebook. Facebook doesn't block per user via the client API, but rather, per client type, via a key. So, even though gwibber has been fixed, there are still people running old versions of Gwibber (mostly on Ubuntu LTS) which flood the server and trigger an automatic block for all gwibber clients. The Gwibber upstream is aware of this, and is trying to work out a way that Facebook will accept to get clients working reliably again.
Ah, that makes a certain amount of sense. The debug output includes this: Gwibber Dispatcher: DEBUG <STATS> facebook:receive account:40093902bb3411df9dce002564e8e9df since:2010-10-11 12:52:04.00 size:568 Gwibber Dispatcher: INFO Facebook error 4 - Application request limit reached So it is occasionally managing to receive from Facebook, when the client isn't blocked. But it isn't queuing status updates and posting them during the times that it can -- it's just losing them, without telling the user that anything went wrong. Even the debug output doesn't make it clear that anything went wrong: Gwibber Dispatcher: DEBUG *** Sending Message *** Gwibber Dispatcher: DEBUG <facebook:send> Performing operation Gwibber Dispatcher: DEBUG <facebook:send> Finished operation Gwibber Dispatcher: INFO Loading complete: 3 - [] Regardless of the underlying server-side issue, the lack of error handling is an application bug.
Can we get our own FB app key for gwibber on Fedora?
Yeah, the error handling isn't ideal. Accepting patches. ;) As to getting our own FB app key, the answer is maybe, I haven't done enough research there yet. I was hopeful that there would be a cleaner solution from upstream.
Technically the answer is 'yes'. I got my own 'gwibber-dwmw2' app key, and it works fine with that. Whether you *want* to do that is of course another question... but don't we already have our own 'gwibber-fedora' key for Twitter?
Is it actually working for you? I spent sometime today trying to get it to work for me, without any meaningful success.
*** This bug has been marked as a duplicate of bug 637580 ***