So you're writting a twitterbot and you need to authorize your application to post to the account. You need an access token and secret for the account you're posting to. If the posting account is the same account that owns the application, no problem, you just push the button on your application's settings page to make the keys. But if you want to post to a different twitter account, there's no UI on apps.twitter.com to authorize it. So I made this bare-minimum node server to run through the authorization process. There's probably a much better way to do this, so please let me know what that way is!
- You'll need a server with node.js!
- Make sure your application has a callback URL specified in its settings page, even if it's just a placeholder. If there's nothing in the callback URL slot, this method of authorization won't work.
- In authorize.js, fill in your application's consumer key and secret, and the domain on which you'll be running this mini-server (I think it'll work with 'localhost' if you're running it on your laptop, but I haven't tested it that way).
- Install the application (npm install)
- Run the server (node authorize.js)
- In a browser, make sure you're logged in to the account that you want to authorize, and then visit this server in the browser (e.g. http://localhost:3456)
- Click "authenticate" and you should be sent to the Twitter app authorization page
- When you authorize the app, you should see a page displaying your new access token and secret. Keep those safe!
If it doesn't work for you, I probably can't help you, but someone who understands this system better than I do will probably make a version of this process that works better.
Thanks for this solution. I was looking for a way without creating sessions and so on.