Re:7 Major Sites that Send Passwords Unprotected, & China's ...
by briansmith on Wednesday January 13, 2010 @09:19PM
(#1051757)
See issue #395 below. That stops most mobile applications--except those on the iPhone--from using OAuth.
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.
Re:7 Major Sites that Send Passwords Unprotected, & China's ...
by wooster on Wednesday January 13, 2010 @06:32PM
(#1051491)
Let me present issue 395, the most starred issue on the Twitter API bug tracker:
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?
Re:7 Major Sites that Send Passwords Unprotected, & China's ...
by tptacek on Wednesday January 13, 2010 @06:42PM
(#1051517)
I'm a lot less concerned about the threat model where one side is your iPhone's persistant store and the other is Twitter. So, no, I think OAuth is probably unnecessary for actual iPhone apps.
I don't love OAuth, but it is at least a decent answer to the concern you're raising.