id,summary,reporter,owner,description,type,status,priority,milestone,component,version,resolution,keywords,cc,irc_client,os,os_version 990,Twitter fails to update when Jabber reconnecting,SynrG,,"During the recent jabber.org DDoS, my Jabber account was repeatedly reconnecting with messages like: {{{ 09:35 <@root> jabber - Logging in: Connecting 09:37 <@root> jabber - Login error: Connection timeout 09:37 <@root> jabber - Logging in: Signing off.. 09:37 <@root> jabber - Login error: Short write() to server 09:37 <@root> jabber - Logging in: Reconnecting in 900 seconds.. }}} Also during that time, my Twitter account stopped receiving updates. After the DDoS was over, and I had logged out of Twitter and back in again, then logged into Jabber again, Twitter updates were restored. To reproduce this problem after the DDoS was over, I had to DROP traffic to jabber.org with iptables at my firewall to simulate the failure in a way that would cause a soft failure (i.e. reconnection attempts are made). After that rule was in place, I logged into both Jabber and Twitter. The Jabber login attempt failed, and immediately started reconnection attempts. Now, some time elapsed before a tweet arrived on the web, so I don't know exactly when Twitter updates failed in bitlbee, but I confirmed that no further tweets arrived after this point, even though I knew they had arrived on the web. It appears, therefore, that Jabber reconnecting causes Twitter to fail to update. It was insufficient to simply cancel the Jabber account reconnection retries to make my Twitter account work again. I had to log out of Twitter and back in again before new tweets arrived in bitlbee again. Thanks to everyone on irc who helped me to identify this problem and patiently answered my questions and helped me set up a reproducible failing case, particularly wilmer and TigerP.",defect,closed,normal,,BitlBee,3.0.5,worksforme,,,irssi 0.8.15,Linux,Debian squeeze