Comment 13 for bug 613420

The problem isn't so much gwibber, as it is twitter. Twitter often has periods of time where we get unexpected results and gwibber doesn't necessarily handle that well. They are usually transient errors, meaning it will start working again without changing anything, just service dependant. I suspect the problem was rate limiting, it is pretty easy to hit that 45 requests per hour limit. The next update we push for gwibber to Lucid will include these logging fixes so it is easier to at least find out what is going wrong, by looking at the log. In the future, we will provide a better way in the client to see the errors and decide if they need to be acted on.

I would also suggest increasing your refresh interval, I recommend at least 15 minutes. I think each refresh is 5 requests to twitter, plus any manual refreshes and posts.