We're getting ready to start the closed beta period for our OAuth support. If you'd like to participate in this beta, please email a...@twitter.com with the Twitter username that you'd like to be associated with your applications.
In the closed beta period, participants will be able to create and manage an unlimited number of OAuth applications. Any user will able to access these applications, but only participants will be able to create them. More documentation forthcoming.
We've had an overwhelming response, and I'm now considering the application for private beta participation closed unless you have a released, widely-used Twitter application (in which case I may have already put you on the list).
If you made the private beta, I emailed you back. If you didn't, hang tight: we'll try to keep the private beta period as short as possible. Once it's over, we'll have a public beta during which anyone can create and manage OAuth applications.
During the entire beta period, public and private, please only encourage your most technical users to try OAuth out. The beta period is, as if it needed to be said, NOT a final release, and should be treated with caution.
Thanks for your enthusiasm! We'll email out next steps soon.
On Fri, Jan 23, 2009 at 13:35, Alex Payne <a...@twitter.com> wrote: > We're getting ready to start the closed beta period for our OAuth > support. If you'd like to participate in this beta, please email > a...@twitter.com with the Twitter username that you'd like to be > associated with your applications.
> In the closed beta period, participants will be able to create and > manage an unlimited number of OAuth applications. Any user will able > to access these applications, but only participants will be able to > create them. More documentation forthcoming.
I will be integrating twitter with our search results. User can submit any media (e.g website, images, video etc.). Then user can add comments to any result and these comment will be posted to twitter automatically. Therefore I want user to provide their password and I will use these password to post to twitters. I would really appreciate, if you add us in your test for OAuth integration.
On Fri, Jan 23, 2009 at 7:03 PM, Alex Payne <a...@twitter.com> wrote:
> We've had an overwhelming response, and I'm now considering the > application for private beta participation closed unless you have a > released, widely-used Twitter application (in which case I may have > already put you on the list).
> If you made the private beta, I emailed you back. If you didn't, hang > tight: we'll try to keep the private beta period as short as possible. > Once it's over, we'll have a public beta during which anyone can > create and manage OAuth applications.
> During the entire beta period, public and private, please only > encourage your most technical users to try OAuth out. The beta period > is, as if it needed to be said, NOT a final release, and should be > treated with caution.
> Thanks for your enthusiasm! We'll email out next steps soon.
> On Fri, Jan 23, 2009 at 13:35, Alex Payne <a...@twitter.com> wrote: > > We're getting ready to start the closed beta period for our OAuth > > support. If you'd like to participate in this beta, please email > > a...@twitter.com with the Twitter username that you'd like to be > > associated with your applications.
> > In the closed beta period, participants will be able to create and > > manage an unlimited number of OAuth applications. Any user will able > > to access these applications, but only participants will be able to > > create them. More documentation forthcoming.
@Alex
I would recomend emailing him at a...@twitter.com. However your idea
sounds pretty awesome though.
I'm working on site that is a social profile, and connects all of the
social sites in one easy place. It's pretty intriguing! I can't wait
to start using OAuth.
|
