[twitter-dev] Re: New app for every Twitter account?
As Taylor says, you don't need a different app for each account, but actually that's the easy solution, with the added benefit that you never need to do the Oauth dance to capture any tokens. PLUS... each app gets the glory of it's own via tag. Creating an app is no more work than creating a Twitter account. The actual app is of course your same code each time. Just fill in the blanks and grab the tokens using the 'My Access Token link. Then in your publication code just substitute in the keys for that site/account. On Aug 11, 9: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.
[twitter-dev] Re: New app for every Twitter account?
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.
Re: [twitter-dev] Re: New app for every Twitter account?
Hi Marc, You can do this using the OAuth authentication flow which you can find at http://dev.twitter.com/pages/auth#intro This may seem very much complicated for a simple application with only a few users (and static keys), and I agree. However, unless there is some service on the internet which simply allows you to get some keys in exchange for your username/password (and I do not know any), you will have to use this. Tom On 8/11/10 10:58 PM, Skygazer 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.
[twitter-dev] Re: New app for every Twitter account?
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.
[twitter-dev] Re: New app for every Twitter account?
Sorry for the typos, here its again: 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 having aliases a better solution for this? In other words, one user having several aliases, each alias being permitted to get separate access tokens for the same app? Regards, Shob On Aug 11, 2:04 pm, Jacky jaga...@gmail.com wrote: 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.
[twitter-dev] Re: New app for every Twitter account?
That makes sense to me but that's not supported at this time from my understanding. On Aug 11, 5:04 pm, Jacky jaga...@gmail.com wrote: 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.
[twitter-dev] Re: New app for every Twitter account?
Ok, I'll give it a try. Thanks. On Aug 11, 5:02 pm, Tom van der Woerdt i...@tvdw.eu wrote: Hi Marc, You can do this using the OAuth authentication flow which you can find athttp://dev.twitter.com/pages/auth#intro This may seem very much complicated for a simple application with only a few users (and static keys), and I agree. However, unless there is some service on the internet which simply allows you to get some keys in exchange for your username/password (and I do not know any), you will have to use this. Tom On 8/11/10 10:58 PM, Skygazer 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.
[twitter-dev] Re: New app for every Twitter account?
No its not, and I wish it was allowed/supported... On Aug 11, 2:09 pm, Skygazer marc.bouc...@gmail.com wrote: That makes sense to me but that's not supported at this time from my understanding. On Aug 11, 5:04 pm, Jacky jaga...@gmail.com wrote: 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.
