I've been wondering this about Twitter apps lately.
I don't love OAuth, but it is at least a decent answer to the concern you're raising.
See http://twitpic.com/api.do, http://img.ly/pages/API, http://code.google.com/p/imageshackapi/wiki/YFROGuploadAndPo..., http://twitrpix.com/api, http://twic.li/api. All of them require and/or allow the client app to pass the user's Twitter username and password.
http://code.google.com/p/twitter-api/issues/detail?id=395
Also fun: if I have an iPhone client app interacting with Twitter and also with a web service that in turn interacts with Twitter, how does OAuth fit into that scheme? Do I make the user do the OAuth dance for the iPhone app? My web site? Both?