it seems oauth requires the use of a web browser at the very least that would be the case with twitter. I can possibly see a callback system being implemented to allow the user to hook in their redirect to twitter.com, and a user induced callback with the oath token once redirected back from twitter.com. But a full stack oath implementation as part of the api might not be possible without asking the user for their username and password (i.e. it will not be possible while adhering to what oauth is about (security)).

ok i used the word user in two different contexts. The first user is the programmer using the api, the second user (who will give the username and password) is the enduser using what the programmer has made.

We could just return the url to go to to the developer? the dev could then use web_browser standard module or whatever he wants to do with it and return the ticket key to the object itself through another method or property or what have you?

I've just stumbled upon this package here on github, it could serve as inspiration: http://github.com/henriklied/django-twitter-oauth/tree/master

I could be convinced to help create a django app using Six's wicked twitter app. I'm still new to oauth, but pretty good with django. Any takers?

Further to this - it may just be a case of using django-oauth-consumer and adding in twitter. May not need a seperate app just for twitter oauth.

I believe this functionality would be accomplished using a search