I do most of my work in a cafe environment, so having any twitter traffic transmitted in the clear is really unacceptable. I'll continue to explore Tweetie for the Mac at home, where I control the network but for the bulk of my time Tweetie won't be usable because of this.
Eek. Didn't know about this! Definitely don't like my twitter password's transmitted over non/ssl. I only work not-at-home 1ce a week, but I'm still concerned :)
If the password is being passed over plain text this is a major and shocking problem. If OAuth is being used that is a different story. Please make sure our communication is secure.
Awesome feedback response atebits. Thanks for keeping us updated! I also noticed there's an auto-update added to 1.0.1. Good job on quickly squashing this issue!
Great, thanks! I can confirm that it does connect to twitter.com on port 443, according to my logs. Is it only using this for initial login purposes, or are all communications with the site via https? I'd prefer the latter -- as much encryption as possible, even for something basic like Twitter.