Re: [twitter-dev] OAuth confusion

2010-03-31 Thread Taylor Singletary
Also worth mentioning that you can use a number of tools or libraries to acquire those access tokens on your employee's behalf -- it doesn't have to be your desktop application. My OAuth Dancer tool ( http://bit.ly/oauth-dancer ) is a very easy way to negotiate access tokens which you can then lit

Re: [twitter-dev] OAuth confusion

2010-03-31 Thread BJ Weschke
Use oauth to get an access token. Once you've gotten the access token by the user approving the app to act on their behalf, that user need not be authenticated again. You only need the access token that you got through the original oAuth handshake. On 3/31/2010 3:59 PM, Edward Caine wrote: H

Re: [twitter-dev] OAuth confusion

2010-03-31 Thread Taylor Singletary
In order for those members of your staff to tweet and have the "source of LateMusic.org" to surface on the site, you'll have to use OAuth or a variation on OAuth we support called xAuth. By sending an email to a...@twitter.com, you can apply for xAuth access -- it allows you to exchange logins and

[twitter-dev] OAuth confusion

2010-03-31 Thread Edward Caine
Hello all, I'm writing a desktop client for very specific people i.e. only the staff of my website - I'd like to be able to access the API using my app, which is registered, and for it to say "via LateMusic.org" under the tweet. What I don't want to do is have the user authenticate before typing