Out of curiosity. What are the use cases for automated application creation?
On Tue, Apr 14, 2009 at 18:53, Dr Nic <[email protected]> wrote: > > Currently the only way (I think) to register an application to use the > OAuth API is via the web form at http://twitter.com/oauth_clients/new > which requires the user to use login/password on the main site. To > automate this (e.g. move it into a command-line application like the > twitter rubygem) means that the login/password must be stored locally. > Which is fine, until its not. > > The maintainer of the twitter rubygem is/has migrated his code base to > be whole OAuth compatible and removed all notions of storing login/ > password locally to use for Basic Auth on the APIs. This means the > twitter rubygem cannot be extended to support registering OAuth > applications. Which is a pity. > > Can registration of OAuth applications be added to the API, please? > That would be wonderful. > > Cheers > Nic > -- Abraham Williams | http://the.hackerconundrum.com Hacker | http://abrah.am | http://twitter.com/abraham Web608 | Community Evangelist | http://web608.org This email is: [ ] blogable [x] ask first [ ] private.
