Hi,
I had posted that script:
http://groups.google.com/group/twitter-development-talk/browse_thread/thread/2985c36158742455/6a179766f32f4d50
I think it ran at around 1000 conversions/hour, but you can easily
parallelize to get more throughput.
- Jon
On Jun 17, 4:20 pm, Abraham Williams
On Jun 16, 2:58 pm, Paul Kinlan paul.kin...@gmail.com wrote:
Hi,
Since you have all the passwords, could you not just log into the users
account and authorise access to your oauth based application?
No, it's way too many users. I don't have that time. But see that's
exactly my point. I HAVE
What you're proposing kind of defeats the purpose and intent of OAuth ...
even if, implicitly, users have sort of given permission.
On Wed, Jun 17, 2009 at 6:22 AM, Simon tro...@gmail.com wrote:
On Jun 16, 2:58 pm, Paul Kinlan paul.kin...@gmail.com wrote:
Hi,
Since you have all the
Hi,
I was joking about taking their password and getting then logging in to the
accounts to auth the oauth tokens. oAuth is designed to stop people like us
having and controlling peoples passwords and thus having control of peoples
accounts.
You can stop taking peoples accounts, use sign in with
As Abraham said, even though we don't know your code it is simple to
maintain both basic auth and oauth at the same time.
Twollo's flow is basically:
if user.UseOauth:
request using oAuth
else:
request using basic Auth.
Obviously at some point path 2 will be redundant, however there has been
True... I think the way I did was kinda stupid (made 2 databases).
Going to recode everything in a new way. An easier way.
I'm still interested in knowing what measures Twitter will take to
switch basic auth users to OAuth... Will all of the users have to
switch manually and those that don't
I would have thought the plan is to give everyone enough time to direct
their users down the oauth route. I would still expect people to complain
when they turn off basic auth in the future.
Paul
2009/6/17 Simon tro...@gmail.com
True... I think the way I did was kinda stupid (made 2
