For what it's worth, and in the spirit of open communication, Matt
just showed me a prototype of an OAuth-enabled Twitter this afternoon.
 I'd done a similar project a few months back, and found that while it
was easy to get up and running as an OAuth provider, the quality of
the libraries at the time was quite poor.  It seems they've improved
in the interim, as Matt is is pretty happy with what he's got so far.

It's been my intention to lump OAuth in with the next major release of
the API.  Because we're changing stacks, I didn't want to duplicate
the work of adding OAuth in our current stack only to have to redo it
mere weeks later in our new stack.

If we can deliver it sooner with minimal effort, though, we will.
Doing so requires resources beyond the API team here at Twitter,
though, as there's a strong User Experience component to any OAuth
implementation.  We'll be talking with our UX team about prioritizing
some of their time to get beta OAuth support out the door sooner than
later.

Hope that helps.  Long story short, we've been punting on OAuth to try
to minimize duplication of labor as we transition to some new
technologies, but we're willing to be pragmatic if the libraries have
improved.

On Thu, Nov 13, 2008 at 6:30 PM, Ed Finkler <[EMAIL PROTECTED]> wrote:
>
> I think we know this already, and allowing a flavor of the day story
> to influence things unduly would be overreaction.
>
> I trust Alex, Matt and co. to make the proper decisions in regards to
> what takes precedence.
>
> --
> Ed Finkler
> http://funkatron.com
> AIM: funka7ron
> ICQ: 3922133
> Skype: funka7ron
>
>
> On Thu, Nov 13, 2008 at 4:52 PM, Jesse Stay <[EMAIL PROTECTED]> wrote:
>>
>> I'm sure you're aware of this, but the lack of OAuth or secure login support
>> just got really public as it made Techmeme.  IMO, for my App at least, this
>> would be first priority if I were to ask for anything.  Anyone else agree?
>>  Here's the Meme:
>>
>> http://www.techmeme.com/081113/p38#a081113p38
>>
>> Jesse
>>
>



-- 
Alex Payne - API Lead, Twitter, Inc.
http://twitter.com/al3x

Reply via email to