@Rich
i didn't get this. When you set browser auth, there is no pin to retrieve
(if i am not wrong) and i am assuming you are retrieving access
tokens/secrets directly.So after redirecting to your own server how exactly
are you going to retrieve the values for that Particular client? Can you
elaborate?

On Fri, Nov 6, 2009 at 1:01 PM, Rich <rhyl...@gmail.com> wrote:

>
> You can do exactly that already.  Set it to browser auth, redirect it
> to your own webserver and get your webserver to redirect to your own
> url scheme, forwarding on the callback token.
>
> Trust me, it will work just fine!
>
> On Nov 6, 5:20 am, Ji Lee <mr.ji.hoon....@gmail.com> wrote:
> > Hi,
> >
> > It seems that the current OAuth for desktop apps require that the user
> > copy the 7-digit number, and paste into the client. This is fine for
> > the desktop, but it doesn't work too well for the mobile device, as
> > copy/paste is a rather cumbersome to do... Flickr OAuth seems to
> > provide a mechanism which allows the desktop client to retrieve the
> > token using a separate URL.
> >
> > Is there a URL for retrieving the token after user return to the
> > client application?  Would commerial key help?
> >
> > Another possibility is to allow for a callback URL scheme, such as
> > "myclient://" as the callback URL, which my app could register itself
> > to handle. Curretly, the twitter website does not seem to accept such
> > URLs.
> >
> > Thanks,
> >
> > -Ji
>

Reply via email to