it's probably does to an older fetch arriving after the updated one.
http fetches are not done in order: some can take a while.
one second is way too little: the old ones can stack up, and twitter is going to turn you off after a few hours of war-hammering like your doing.
plus, i would be pissed if i realized your page sucks 500mb per day from my data plan; that's ridiculousness!
(2013/5) HTML5:90.2% MOB:14% IE7:0.5% IE8:8.6% IE9:9.8% IE10:10%
Last edited by rnd me; 01-17-2013 at 12:39 AM..