yes that's right - I'm aware that the same approval method applies. My
users are using both the desktop app and the web app, so I wanted a way of
being able to allow access the desktop app using the desktop authorisation
tool with the same twitter app. In other words, have my twitter app supply
the pin as well as generate the url when authenticating via the web app. I
think my best method here is instead getting my client app to access a
browser, either through my desktop webkit or simply through a browser.
Having the one source of authenticating seems the most attractive
alternative to me now though.
Please feel free to make some suggestions
On Wed, Aug 26, 2009 at 3:00 PM, Andrew Badera <and...@badera.us> wrote:
> Desktop has a different approval flow, but once you have credentials,
> it's all the same thing. You're using the same HTTP/REST libraries to
> access the API in either case, right? How does the API know who or
> what the final consumer is?
> ∞ Andy Badera
> ∞ This email is: [ ] bloggable [x] ask first [ ] private
> ∞ Google me:
> On Wed, Aug 26, 2009 at 8:12 AM, Nore
> Gabbidon<noregabbi...@googlemail.com> wrote:
> > Hi,
> > I'm fairly new to Twitter, particularly Twitter development. I have a
> > question:
> > I have a desktop client application and a web application. I have
> > created a twitter application for API access. Ideally, I would like
> > to be able to give users access to Twitter from my desktop app and web
> > app using just the one twitter application. Is this possible? Or do
> > I have to create two seperate twitter applications; one for desktop,
> > the other for the web?