You're right. The simplest (only?) way would be to create an account specifically for managing your app. I believe there was a recent post on this list talking about that being the norm, but I couldn't find it. I'd love for the app to have it's own credentials, and allow for assigning multiple twitter users to administer/manage the app.
James On Mon, May 23, 2011 at 4:14 PM, Craig Walls <[email protected]> wrote: > Correct me if I'm mistaken, but I believe that access token/secret > pair are still *my* access token and secret for that application. That > is, they can be used to access my personal Twitter data. I'm > uncomfortable using my personal credentials (or those of any > individual user) for this purpose. > > What I'm looking for is a token/secret that belongs to the app and can > only be used to do things that required authentication, but not access > an individual's data (accessing the streaming API, for instance). > Perhaps I create a bogus user that represents the application and use > their credentials? > > -- > Twitter developer documentation and resources: https://dev.twitter.com/doc > API updates via Twitter: https://twitter.com/twitterapi > Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list > Change your membership to this group: > https://groups.google.com/forum/#!forum/twitter-development-talk > -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
