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
Message from discussion countdown to OAuth / basic auth removal / OAuthcalypse
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
 
John Meyer  
View profile  
 More options Apr 27 2010, 9:13 am
From: John Meyer <john.l.me...@gmail.com>
Date: Tue, 27 Apr 2010 07:13:24 -0600
Local: Tues, Apr 27 2010 9:13 am
Subject: Re: [twitter-dev] Re: countdown to OAuth / basic auth removal / OAuthcalypse
On 4/27/2010 5:52 AM, Eoin wrote:

> Hi,

> This is probably a basic question - but what is the best option if you
> have written an integration for a web-based application that is
> installed on multiple sites?

> The URL is going to change per installation (and won't be publicly
> accessible), and I would really like to minimise the impact to the
> application's administrators and users.

> thanks,

> Eoin

If the app stores twitter usernames/passwords in combo, one solution may
be to use xAuth and run a batch job to convert.  Once you've converted
over to tokens, ditch the passwords and you're done.

--
Subscription settings: http://groups.google.com/group/twitter-development-talk/subscribe?hl=en


 
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.