Upgraded to 1.3.2 on my Samsung SGH-E250 yesterday, and found some issues. Previously (up to 1.1.28) I had the timeline length (stored in the phone) set to 1000, so I didn't have to look at the screen all the time, and could scroll back a bit. The individual update size limit (20) did work for me since I follow about 300 people and the interval is set to 150 seconds. With the new version (based on new API features), at the beginning up to 200 tweets are loaded (~100kBytes), at least in theory, in practice it would never finish. I have to set tl size to 20 manually, then fetch, then set tl size to a large value. Each time I start jibjib. - A new setting "request size" (or the like, default 20 as before) would fix this. Sometimes, when I notice that a request (send or receive) gets stuck, I press Cancel with the result that the connection gets lost. From within jibjib then there's no way to re-establish the connection, I have to exit and restart. (Add an item "reconnect"to the error menu?) Sometimes, kind of remainders keep alive in the background, and an error pops up in the middle when all has already been fixed by a refresh/re-send. Apparently not everything gets cancelled on Cancel... A similar thing happens if I by mistake choose "d Messages" then cancel and select "Friends" - I end up with the DM timeline. Switching back and forth between friends and mentions timeline reloads the whole stuff instead of keeping it in memory and only retrieving the newest entries (this issue has been there all the time, and perhaps will never be fixed - it's effectively keeping me from following my non-friends mentions and DMs while travelling).

Despite of these rather nitpicky issues, jibjib is still the Twitter client of my choice when I'm travelling - thanks for your work on constantly extending and improving it!