dwould, ta for the strides forwards with this app in the last few weeks. With portrait support and fixed bugs its starting to be quite usable.

Indeed, a timer would be the best way to make the textbox disappear when not in use and the accepted way for other things (am thinking particularly of javascript timers, though that might be lots easier to setup than python+system libraries). Is there an easy interrupt handler kinda thing equivalent (am a c++/linux/python dev but not used to event-driven models yet in native app UIs)?

Obviously getting the text box back again is easy in one way (any keypress event on the main screen opens it up with the key you pressed pre-inserted), but when you're using the virtual keyboard it might be harder (I mean is there another way, apart from clicking a "reply" button from another opened post's window). You could overlay a small button bottom-left (you might not care that you'd cover up an avatar from the bottom post on the screen) that only appears when the hardware keyboard is shut, or steal one of the other hardware buttons (camera button? Probably lots of effort but there might be other apps that provide libs/ways to do it).

I used to get just a busy-wait indicator when I went to "mentions" tab (even before PR1.2), and it never got the tweets/updated; now it shows stuff, and it doesn't lose it when you switch tabs back to it either now. The other windows still seem to be empty though, or take forever. But keep going, its getting better and better!

If I felt I had a good amount of time to spare I'd offer you some coding help (I've slowly been getting to know the pygtk libs the last couple of months by writing my own basic tube station/line info app) and have a little experience with internationalisation from previous paid contracts in python/php.

PS... from your blog, v3.3.7(I think?), I quote:
"Initial support for starting a connection if none exists, currently it starts, but not before witter fails the connection is was trying. not sure yet how to make witter wait for active connection"

Did you fix this? I'm wondering if there's a dbus message you can subscribe to to know when its connected, either that or just retry the socket open for a period of time (or set the socket timeout larger?). There's gotta be a standard way to do it like the builtin Nokia-selected/built apps do.

John, London, UK