If every tweet were to be issued by the same account, Claudia, you would need to acquire your access token through OAuth once -- then persist the access token in your application and use it for every authenticated API action -- your users wouldn't have to ever see anything having to do with OAuth.
There's also a short cut for acquiring the access token for the account that "owns" the application -- you'll find a "my token" feature on your application details page on dev.twitter.com Taylor On Fri, Aug 20, 2010 at 10:20 AM, Claudia <cbern...@gmail.com> wrote: > I have a similar need but it is for a web app that I'm building. I > need to allow multiple users to update a single (my) twitter account > via the experience. Redirecting to the twitter authentication page > wouldn't make any sense to the user, and disrupts the whole > experience. Am I stuck here? Is there no way to use Oauth to update a > single account without redirecting to the twitter authentication page? > > Thank you! > claudia > > On Aug 19, 7:42 pm, Taylor Singletary <taylorsinglet...@twitter.com> > wrote: > > xAuth is a privilege granted on a case-by-case basis. Send a detailed > email > > to a...@twitter.com explaining your application, its userbase, and why > other > > forms of OAuth won't work for your application. > > > > xAuth is limited to native desktop & native mobile applications. > > > > Taylor > > > > 2010/8/19 João Paulo Sabino de Moraes <jona...@gmail.com> > > > > > > > > > I'm using tweetr api (adobe air api), it uses OAuth. > > > Is it possible to integrate OAuth apis with xAuth ? > > > > > thanks >