>>Would any developers out there that proxy credentials like this, please speak
>>up and share your use case?
I realize I hadn't shared the use case for Tipjoy.
We opened an API for payments that requires a twitter username and
password:
http://tipjoy.com/api
Here is a tutorial
http://tipjoy.c
The workflow you describe has actually always bothered me, and I think
is the kind of thing OAuth is trying to combat.
Twitpic is not an official service of Twitter, but it seems to be
treated as such by many clients, which silently share their users'
Twitter authentication information. Any clien
Ivan,
Iain of @tweetdeck brought this use case to my attention during devnest so
it is certainty something we want to address with OAuth. We still consider
OAuth's current implementation as a beta, and thus incomplete. The pattern
for proxied approval hasn't been decided but as I said, is on our mi
