No he means each source is a user and has its own account, and authorizes the single app for separate access tokens..
However, my question is, is not having aliases a btter solution for this? In other words, on user having several aliases, each alias being permitted to get separate access tokens for the same app? Regards, Shob On Aug 11, 1:58 pm, Skygazer <marc.bouc...@gmail.com> wrote: > Hi Taylor, > > Ok, but how do you get an access token/access token secret for the > other account without creating a new app? > > On Aug 11, 3:49 pm, Taylor Singletary <taylorsinglet...@twitter.com> > wrote: > > > Hi Marc, > > > In this case, instead of using the username/password of a different account > > while making a request, you would use an access token/access token secret > > belonging to a different account. You don't need to create separate > > applications for each account, but you need to authorize the application to > > act on behalf of each account. > > > If you don't want to implement the OAuth flow to acquire access tokens in > > your application, you can use another application or library (such as my > > OAuth Dancer athttp://github.com/episod/oauth-dancer) to secure the access > > tokens, then port them over to your "proper" application. > > > Taylor > > > On Wed, Aug 11, 2010 at 12:37 PM, Skygazer <marc.bouc...@gmail.com> wrote: > > > My company has several news sites and each has one or more Twitter > > > accounts depending on the topic. I've created a new app using OAuth > > > and PHP to post our news stories automatically as they are published. > > > Previously with basic authentication I would just pass the username > > > and password etc. to get the story posted. But now I'm wondering, do I > > > need to create a new app for every Twitter account we have? Or can I > > > post to our accounts with the one app I created with its keys and > > > tokens? And if I can use just the one app, how do I post to the other > > > accounts? The app was created on our primary Twitter account. > > > > Thanks > > > Marc > > > > PS I already have the OAuth and PHP code working for our primary > > > Twiter account.
