>I'll see if there's anything we can do about offering a "give me /my/ access yes, please let us know. That is why I wrote this qyuestion. I think this option should be somewhere within 'my account' settings on Twitter
On Apr 26, 6:17 pm, Taylor Singletary <taylorsinglet...@twitter.com> wrote: > Obtaining a single access token for your application without necessarily > implementing the entire OAuth dance shouldn't be too difficult -- there are > many OAuth libraries that include command-line tools to acquire access > tokens in this way. You could also use Twurl > (http://github.com/marcel/twurl). My OAuth Dancer > (http://bit.ly/oauth-dancer) tool also lets you do this through a server > interface your run on your own machine. I don't recommend sharing your > consumer key or secret to any third-party website to acquire this > information, but using a tool locally on your own machine is likely the best > method. > > I'll see if there's anything we can do about offering a "give me /my/ access > token & access token secret for my application" feature on > dev.twitter.comto help with this. It'd then be as simple as porting > those two pieces of > information into whatever database, configuration file, or otherwise you > would use to store the access token and access token secret. As with any of > these kind of keys though, it wouldn't be appropriate to distribute access > tokens of any kind with your software -- whether on github, in a desktop > application, or in plaintext in a Javascript file. > > Taylor Singletary > Developer Advocate, Twitterhttp://twitter.com/episod > > On Mon, Apr 26, 2010 at 5:29 AM, Ken <k...@cimas.ch> wrote: > > With OAuthcalypse looming, there is an urgent need for your service. I > > doubt that every API user with a "Twitter-spitter" even knows about > > the deadline. If you can convince them of your benign intent, great. > > If you have thought of a way to make it pay, even better! > > > On Apr 26, 10:26 am, Harshad RJ <harshad...@gmail.com> wrote: > > > On Mon, Apr 26, 2010 at 1:50 PM, Ken <k...@cimas.ch> wrote: > > > > For security reasons this service should be left to Twitter, but a > > > > third party could deliver the same tokens if provided with the app's > > > > Consumer key and secret. A bit messy though - need to change the > > > > requesting app's callback URL - but it's doable. > > > > > Is someone already doing this? Would that violate ToS? > > > > Just FYI, I am working on a similar concept. Waiting for clarifications > > from > > > Twitter before releasing it publicly. > > > > -- > > > Harshad RJhttp://hrj.wikidot.com > > > > -- > > > Subscription settings: > >http://groups.google.com/group/twitter-development-talk/subscribe?hl=en
