Will you be adding support for Twitter's OAuth API?

Now that Twitter is in public beta testing for their OAuth endpoint, seems like you guys should move over to this solution, no?

I’m eager

Inappropriate?

Reply to this question

6 people have this question

I have this question, too! Tell me when someone answers.
The more people who ask this question, the more it gets noticed.

Create a customer community for your own organization

Plans starting at $19/month

Remove Inappropriate?
Delete or Edit for 15 minutes

Thomas replied on April 15, 2009 19:40

Their response was thus:

we will do this when Twitter provides us with a way to migrate existing users to OAuth.

I’m sad

this answers the question

Add a comment This answers the question
EMPLOYEE

Remove Inappropriate?
Delete or Edit for 15 minutes

Brady, Official Rep, replied on April 16, 2009 00:32

Yes we will be moving to O-auth. We are looking for a way to port over the existing users that have Twitter enabled. Any suggestions?

this answers the question

2 Comments Add a comment This answers the question Mark as a company answer
Remove
Thomas commented on April 16, 2009 00:59

That's actually a pretty good idea, an API way to generate an OAuth key for your app and then switch over. You should request that on the twitter api google code tracker.
Remove
Chris Messina commented on April 21, 2009 01:10

I think it depends on what Twitter's timeline looks like, but I think you just need to pop a notice for users who activated their Twitter accounts with their username and passwords that "Twitter has changed how we access their service. In order to continue using Brighkite with Twitter, you will need to _reauthorize_ your account."

Like this:
Remove Inappropriate?
Delete or Edit for 15 minutes

Thomas replied on April 21, 2009 01:21

Please keep the other option available, because OAuth for Twitter is down now and will be down for a few days. This may happen repeatedly during the public beta for OAuth, so it's not as dependable as I'd like. Perhaps one could do both, so that when the OAuth is down (or the HTTP Auth option is removed), it'll continue working fine?

I’m sad

this answers the question

3 Comments Add a comment This answers the question
Remove
Chris Messina commented on April 21, 2009 01:25

At some point, Twitter will disable or devalue using username and password auth, so moving to OAuth will be necessary.

That said, Brightkite should wait before forcing people to use OAuth until Twitter has moved out the new API of beta. This will likely happen in the next several months; I wouldn't advocate for making this change right away.
Remove
Thomas commented on April 21, 2009 01:48

I would like to see them making it possible to use OAuth for those who don't like sharing their passwords, with the caveat that it might not always work.
Remove
Chris Messina commented on April 21, 2009 01:50

Of course it's up to them to decide how to roll this out, but I highly doubt that Brightkite wants to offer a feature that only works part of the time, even if it's Twitter's fault. Just sayin'.