2 ms·
The point of my post is also this: Something changed in the behavior of New Twitter. None of this happened when I was first given access to NT months ago. The
by mikecane 16y ago
The point of my post is also this: Something changed in the behavior of New Twitter. None of this happened when I was first given access to NT months ago. The problems seemed to crop up simulataneously -- coincidentally -- with my moving to Opera 11 beta. The problems have since spread to all 3 of the browsers I wound up cycling through. So I think Twitter changed something on their end and are unaware of the ripple effect on some users. Someone, on Twitter, suggested they were once polling every 90 seconds in the beginning and now that the switch is complete, we are getting "live streaming." That might be too much for some systems to handle. Perhaps a user option to throttle back polling? [typo edit]
- russ 16y agoCurrently, we're not live streaming. We poll every 30 seconds when focused and fall back to 90 seconds unfocused. When we do push, we'll be using User Streams (http://dev.twitter.com/pages/user_streams http://dev.twitter.com/pages/user_streams) with either Websockets or Flash. Performance should improve when that happens. There are also some other neat tricks we'll be able to do to make the site even faster.
- mikecane 16y agoBut something changed somewhere. Scrolling used to be a smooth experience. The entire use of NT was exciting and not cloggy. Now it is hell scrolling and very cloggy and even autocomplete of IDs is a torment. What did you guys do over there to the code?