Comment 2 for bug 199453

I don't believe I had any other instances of gwibber or any other twitter clients running simultaneously. I had closed and reopened gwibber a few times when it wasn't displaying any posts, but I'm pretty sure all the processes got killed when I closed it. I have my refresh set at 5 minutes.

Another issue is that the twitter error seems to have prevented jaiku updates, so if one service fails the others should not, obviously.

I was wondering if the problem might have been twitter to begin with and not gwibber at all. I don't know how to test that, though, the extent of my knowledge is to go to http://www.istwitterdown.com/ ;)

Thanks for the help!