Hi Elliott, This scenario worked well with basic authentication; you could just delegate the login to Twitter. Now I don't see a way to do it without requiring the user to create another account so that the token can be associated with it. I haven't got that far myself, but I think you're missing the bit where you store the token and reuse it the next time the user logs in to your app.
In my case, I'm working on a web service to compliment Twitter and want desktop Twitter clients to be able to access it to store/retrieve supplementary information about a Twitter account. But if I can't prove that the user running the client owns the Twitter account then I can't see a way to avoid making them go through yet another registration process with my web service. I suppose an alternative would be to ask the desktop clients for their tokens and use that to call verify credentials? Feels very wrong, but I really want to avoid the complication of a duplicate set of accounts for Twitter users. Cheers, G. P.S. Sorry about my accidental post - my palm slipped onto my laptop trackpad while I was typing and it clicked send! On Mar 21, 4:16 pm, Elliott Kember <[email protected]> wrote: > Hi Graeme, > > I think I'm doing a similar thing - I want to use Twitter as the > registration and login process for my app. Right now, Twitter asks for > approval every time the user logs into the account. Is there a way to > say "remember this application" and then always accept auth requests > from that application in future, like OpenID does? > > Long story short, I'm using OAuth like OpenID. Sorry to hijack your > thread, but I think we're after the same thing.
