[twitter-dev] Re: oAUTH - can it be done without interaction with a core browser?

2009-05-14 Thread Doug Williams
t; > > > Jeff > > > > > ----- Original Message - > > > *From:* Doug Williams > > > *To:* twitter-development-talk@googlegroups.com > > > *Sent:* Sunday, April 19, 2009 9:22 PM > > > *Subject:* [twitter-dev] Re: oAUTH - can it be don

[twitter-dev] Re: oAUTH - can it be done without interaction with a core browser?

2009-05-14 Thread David Troyer
d" button on that page so that the user could paste it in. > > Is this something planned or does it already exist? > > > Jeff > > > - Original Message - > > *From:* Doug Williams > > *To:* twitter-development-talk@googlegroups.com > > *Sent:* Sunda

[twitter-dev] Re: oAUTH - can it be done without interaction with a core browser?

2009-04-19 Thread Doug Williams
that page so that the user could paste it in. > Is this something planned or does it already exist? > > Jeff > > > - Original Message - > *From:* Doug Williams > *To:* twitter-development-talk@googlegroups.com > *Sent:* Sunday, April 19, 2009 9:22 PM > *Subject

[twitter-dev] Re: oAUTH - can it be done without interaction with a core browser?

2009-04-19 Thread Jeff Bishop
aste it in. Is this something planned or does it already exist? Jeff - Original Message - From: Doug Williams To: twitter-development-talk@googlegroups.com Sent: Sunday, April 19, 2009 9:22 PM Subject: [twitter-dev] Re: oAUTH - can it be done without interaction with a co

[twitter-dev] Re: oAUTH - can it be done without interaction with a core browser?

2009-04-19 Thread Doug Williams
The call to http://twitter.com/oauth/authorize (or the Sign in with Twitter equivalent http://twitter.com/oauth/authenticate) requires a browser to render the HTML necessary for the user prompt. This is a limitation we recognize with the current beta release of the OAuth implementation. Doug Willi

[twitter-dev] Re: oAUTH - can it be done without interaction with a core browser?

2009-04-19 Thread Guan Yang
On Sun, Apr 19, 2009 at 14:37, Jeff Bishop wrote: > 1.  Get all of the required items from the user outside of Twitter's > interface? > 2.  Authenticate (like with basic auth of some type using XML posts)? > 3.  Be able to post back to get the token information. I'm not completely sure what you