Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
Twitter Development Talk
Home
About this group
Join this group
Message from discussion Coming soon: a solution for Open Source applications using OAuth with the Twitter API
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Josh Roesslein  
View profile  
 More options Jun 12 2010, 11:54 am
From: Josh Roesslein <jroessl...@gmail.com>
Date: Sat, 12 Jun 2010 10:54:18 -0500
Local: Sat, Jun 12 2010 11:54 am
Subject: Re: [twitter-dev] Re: Coming soon: a solution for Open Source applications using OAuth with the Twitter API
Print | View thread | Show original | Report this message | Find messages by this author

Sorry over looked the access token being included. I still do not think this
fits well with open source
desktop apps. I think for now just not distributing a key with the app's
source, but provide it when the app
is built (hidden in the binary or such).

On Sat, Jun 12, 2010 at 10:09 AM, Cameron Kaiser <spec...@floodgap.com>wrote:

> > Not sure I totally like this idea. Seems almost like double
> authentication
> > to me.
> > The user has to still sign in via the web to replicate the app and then
> we
> > have to fetch an access token
> > again by asking for their credentials?? So its like doing a 3-legged
> dance +
> > the xAuth.

> No. The process generates a user access token along with a new "child" app
> key in one step. There is no additional xAuth step, and I suspect Twitter
> won't want xAuth-enabled app keys to be "childed" in any case. Like any
> user
> token, it does not expire until the user revokes it, which I assume in this
> case will probably never occur since it can only ever be used by the app
> key
> "child" instance they themselves generated.

> --
> ------------------------------------ personal:
> http://www.cameronkaiser.com/ --
>  Cameron Kaiser * Floodgap Systems * www.floodgap.com *
> ckai...@floodgap.com
> -- Put down your guns, it's Weasel Stomping Day!
> ------------------------------


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
©2013 Google