Comment 3 for bug 682779

I tried to reproduce this today but with no luck. So either:

1. The issue is fixed. I think this is the case, because I haven't
   observed this issue for a long time and I've been using a lot of
   different/laggy networks for the last six months.

2. My testing method wasn't good. I tried two things: I disconnected
   the network and watched Gwibber in htop for awhile. I also used
   'tc' to make my interface randomly drop packets. In both cases,
   Gwibber performed well.

So I think this should probably be marked 'Invalid'. I'll do that now
and if I'm wrong about it this bug can be reopened.