Some of you are in the OAuth closed beta and some are not. I know that's frustrating but we need to start small so we aren't buried in feature requests and bugs all at once. Our intention is to discuss the OAuth progress on this main API Google group (http://groups.google.com/group/twitter-development-talk ). If the discussion gets in the way of the normal group operation please speak up and we can always move it off to a new Google group of its own.
With all of that in mind we just launched the closed beta switch. If you're one of the 150 or so people included in the closed beta your settings page (http://twitter.com/account/settings) now contains a "Connections" tab. In the sidebar is a little information and a link to register your very own application. When you register a new application it will begin as suspended. You'll have the technical details (the key and secret) you need to get started but one of the Twitter admins will have to approve the application. It is not our intention to leave this in place forever but during these early application registrations we need to monitor things. Please use real descriptions and meaningful names, since that' what we'll have to go on. Especially meaningful names.
During the closed beta we're looking for feedback. The Google group is good for discussing general issues and experiences but the Google code issues are the best place for bugs and enhancements (http://code.google.com/p/twitter-api/issues/list if you don't already know). I added a new milestone of "OAuth", so please mark any bugs with the correct milestone. When you report issues try to be specific about the problem, especially in how to reproduce it. It would also save us some time reviewing if you mark enhancements with "Type-Enhancement"in the appropriate box.
During this closed beta we recommend very strongly that you not do general software releases using the feature. If we find any security or performance problems we will need to turn off OAuth and I don't want to break your apps. Your app can sign up users who are not in the closed beta but since this is really a focus on getting feedback please try and limit the audience to people who you feel can provide some feedback.
> Some of you are in the OAuth closed beta and some are not. I know > that's frustrating but we need to start small so we aren't buried in > feature requests and bugs all at once. Our intention is to discuss > the OAuth progress on this main API Google group (http://groups.google.com/group/twitter-development-talk > ). If the discussion gets in the way of the normal group operation > please speak up and we can always move it off to a new Google group > of its own.
> With all of that in mind we just launched the closed beta switch. > If you're one of the 150 or so people included in the closed beta > your settings page (http://twitter.com/account/settings) now > contains a "Connections" tab. In the sidebar is a little information > and a link to register your very own application. When you register > a new application it will begin as suspended. You'll have the > technical details (the key and secret) you need to get started but > one of the Twitter admins will have to approve the application. It > is not our intention to leave this in place forever but during these > early application registrations we need to monitor things. Please > use real descriptions and meaningful names, since that' what we'll > have to go on. Especially meaningful names.
> During the closed beta we're looking for feedback. The Google > group is good for discussing general issues and experiences but the > Google code issues are the best place for bugs and enhancements (http://code.google.com/p/twitter-api/issues/list > if you don't already know). I added a new milestone of "OAuth", so > please mark any bugs with the correct milestone. When you report > issues try to be specific about the problem, especially in how to > reproduce it. It would also save us some time reviewing if you mark > enhancements with "Type-Enhancement"in the appropriate box.
Do you have a guess as to how long the closed beta will last? I did not apply to be a tester, but just in the last 24h, a project has cropped up that would benefit from OAuth. I'm guessing 2 weeks barring crazy talk?
On 2/11/09, Matt Sanford <m...@twitter.com> wrote:
> During this closed beta we recommend very strongly that you not > do general software releases using the feature. If we find any > security or performance problems we will need to turn off OAuth and I > don't want to break your apps. Your app can sign up users who are not > in the closed beta but since this is really a focus on getting > feedback please try and limit the audience to people who you feel can > provide some feedback.
> Thanks; > — Matt Sanford
> On Feb 11, 2009, at 02:04 PM, Matt Sanford wrote:
>> Hello Everyone,
>> Some of you are in the OAuth closed beta and some are not. I know >> that's frustrating but we need to start small so we aren't buried in >> feature requests and bugs all at once. Our intention is to discuss >> the OAuth progress on this main API Google group >> (http://groups.google.com/group/twitter-development-talk >> ). If the discussion gets in the way of the normal group operation >> please speak up and we can always move it off to a new Google group >> of its own.
>> With all of that in mind we just launched the closed beta switch. >> If you're one of the 150 or so people included in the closed beta >> your settings page (http://twitter.com/account/settings) now >> contains a "Connections" tab. In the sidebar is a little information >> and a link to register your very own application. When you register >> a new application it will begin as suspended. You'll have the >> technical details (the key and secret) you need to get started but >> one of the Twitter admins will have to approve the application. It >> is not our intention to leave this in place forever but during these >> early application registrations we need to monitor things. Please >> use real descriptions and meaningful names, since that' what we'll >> have to go on. Especially meaningful names.
>> During the closed beta we're looking for feedback. The Google >> group is good for discussing general issues and experiences but the >> Google code issues are the best place for bugs and enhancements >> (http://code.google.com/p/twitter-api/issues/list >> if you don't already know). I added a new milestone of "OAuth", so >> please mark any bugs with the correct milestone. When you report >> issues try to be specific about the problem, especially in how to >> reproduce it. It would also save us some time reviewing if you mark >> enhancements with "Type-Enhancement"in the appropriate box.
That some of you are not seeing the new "Connections" tab. It looks like a minor bug in the code that does the beta access check (which was new, never done a closed beta before). We're working on a fix now and will send it out with tomorrows morning deploy. I'll update the list once it's out.
> During this closed beta we recommend very strongly that you not > do general software releases using the feature. If we find any > security or performance problems we will need to turn off OAuth and > I don't want to break your apps. Your app can sign up users who are > not in the closed beta but since this is really a focus on getting > feedback please try and limit the audience to people who you feel > can provide some feedback.
> Thanks; > — Matt Sanford
> On Feb 11, 2009, at 02:04 PM, Matt Sanford wrote:
>> Hello Everyone,
>> Some of you are in the OAuth closed beta and some are not. I know >> that's frustrating but we need to start small so we aren't buried >> in feature requests and bugs all at once. Our intention is to >> discuss the OAuth progress on this main API Google group (http://groups.google.com/group/twitter-development-talk >> ). If the discussion gets in the way of the normal group operation >> please speak up and we can always move it off to a new Google group >> of its own.
>> With all of that in mind we just launched the closed beta switch. >> If you're one of the 150 or so people included in the closed beta >> your settings page (http://twitter.com/account/settings) now >> contains a "Connections" tab. In the sidebar is a little >> information and a link to register your very own application. When >> you register a new application it will begin as suspended. You'll >> have the technical details (the key and secret) you need to get >> started but one of the Twitter admins will have to approve the >> application. It is not our intention to leave this in place forever >> but during these early application registrations we need to monitor >> things. Please use real descriptions and meaningful names, since >> that' what we'll have to go on. Especially meaningful names.
>> During the closed beta we're looking for feedback. The Google >> group is good for discussing general issues and experiences but the >> Google code issues are the best place for bugs and enhancements (http://code.google.com/p/twitter-api/issues/list >> if you don't already know). I added a new milestone of "OAuth", so >> please mark any bugs with the correct milestone. When you report >> issues try to be specific about the problem, especially in how to >> reproduce it. It would also save us some time reviewing if you mark >> enhancements with "Type-Enhancement"in the appropriate box.
> And the first bugs is … > That some of you are not seeing the new "Connections" tab. It looks like > a minor bug in the code that does the beta access check (which was new, > never done a closed beta before). We're working on a fix now and will send > it out with tomorrows morning deploy. I'll update the list once it's out. > Sorry about that; > — Matt Sanford > On Feb 11, 2009, at 02:16 PM, Matt Sanford wrote:
> And now for what I forgot, > During this closed beta we recommend very strongly that you not do > general software releases using the feature. If we find any security or > performance problems we will need to turn off OAuth and I don't want to > break your apps. Your app can sign up users who are not in the closed beta > but since this is really a focus on getting feedback please try and limit > the audience to people who you feel can provide some feedback. > Thanks; > — Matt Sanford > On Feb 11, 2009, at 02:04 PM, Matt Sanford wrote:
> Hello Everyone,
> Some of you are in the OAuth closed beta and some are not. I know that's > frustrating but we need to start small so we aren't buried in feature > requests and bugs all at once. Our intention is to discuss the OAuth > progress on this main API Google group > (http://groups.google.com/group/twitter-development-talk). If the discussion > gets in the way of the normal group operation please speak up and we can > always move it off to a new Google group of its own.
> With all of that in mind we just launched the closed beta switch. If > you're one of the 150 or so people included in the closed beta your settings > page (http://twitter.com/account/settings) now contains a "Connections" tab. > In the sidebar is a little information and a link to register your very own > application. When you register a new application it will begin as suspended. > You'll have the technical details (the key and secret) you need to get > started but one of the Twitter admins will have to approve the application. > It is not our intention to leave this in place forever but during these > early application registrations we need to monitor things. Please use real > descriptions and meaningful names, since that' what we'll have to go on. > Especially meaningful names.
> During the closed beta we're looking for feedback. The Google group is > good for discussing general issues and experiences but the Google code > issues are the best place for bugs and enhancements > (http://code.google.com/p/twitter-api/issues/list if you don't already > know). I added a new milestone of "OAuth", so please mark any bugs with the > correct milestone. When you report issues try to be specific about the > problem, especially in how to reproduce it. It would also save us some time > reviewing if you mark enhancements with "Type-Enhancement"in the appropriate > box.
> That some of you are not seeing the new "Connections" tab. It
> looks like a minor bug in the code that does the beta access check
> (which was new, never done a closed beta before). We're working on a
> fix now and will send it out with tomorrows morning deploy. I'll
> update the list once it's out.
> Sorry about that;
> — Matt Sanford
> On Feb 11, 2009, at 02:16 PM, Matt Sanford wrote:
> > And now for what I forgot,
> > During this closed beta we recommend very strongly that you not
> > do general software releases using the feature. If we find any
> > security or performance problems we will need to turn off OAuth and
> > I don't want to break your apps. Your app can sign up users who are
> > not in the closed beta but since this is really a focus on getting
> > feedback please try and limit the audience to people who you feel
> > can provide some feedback.
> > Thanks;
> > — Matt Sanford
> > On Feb 11, 2009, at 02:04 PM, Matt Sanford wrote:
> >> Hello Everyone,
> >> Some of you are in the OAuth closed beta and some are not. I know
> >> that's frustrating but we need to start small so we aren't buried
> >> in feature requests and bugs all at once. Our intention is to
> >> discuss the OAuth progress on this main API Google group (http://groups.google.com/group/twitter-development-talk > >> ). If the discussion gets in the way of the normal group operation
> >> please speak up and we can always move it off to a new Google group
> >> of its own.
> >> With all of that in mind we just launched the closed beta switch.
> >> If you're one of the 150 or so people included in the closed beta
> >> your settings page (http://twitter.com/account/settings) now
> >> contains a "Connections" tab. In the sidebar is a little
> >> information and a link to register your very own application. When
> >> you register a new application it will begin as suspended. You'll
> >> have the technical details (the key and secret) you need to get
> >> started but one of the Twitter admins will have to approve the
> >> application. It is not our intention to leave this in place forever
> >> but during these early application registrations we need to monitor
> >> things. Please use real descriptions and meaningful names, since
> >> that' what we'll have to go on. Especially meaningful names.
> >> During the closed beta we're looking for feedback. The Google
> >> group is good for discussing general issues and experiences but the
> >> Google code issues are the best place for bugs and enhancements (http://code.google.com/p/twitter-api/issues/list > >> if you don't already know). I added a new milestone of "OAuth", so
> >> please mark any bugs with the correct milestone. When you report
> >> issues try to be specific about the problem, especially in how to
> >> reproduce it. It would also save us some time reviewing if you mark
> >> enhancements with "Type-Enhancement"in the appropriate box.
Is there a limit to the number of applications we can register for the
closed beta? I'm looking at potentially having only 2-3, but wanted to
confirm if we are allowed multiple before submitting the first
application.
Thanks!
-Jeremy
On Feb 11, 4:40 pm, Stuart <stut...@gmail.com> wrote:
> > And the first bugs is …
> > That some of you are not seeing the new "Connections" tab. It looks like
> > a minor bug in the code that does the beta access check (which was new,
> > never done a closed beta before). We're working on a fix now and will send
> > it out with tomorrows morning deploy. I'll update the list once it's out.
> > Sorry about that;
> > — Matt Sanford
> > On Feb 11, 2009, at 02:16 PM, Matt Sanford wrote:
> > And now for what I forgot,
> > During this closed beta we recommend very strongly that you not do
> > general software releases using the feature. If we find any security or
> > performance problems we will need to turn off OAuth and I don't want to
> > break your apps. Your app can sign up users who are not in the closed beta
> > but since this is really a focus on getting feedback please try and limit
> > the audience to people who you feel can provide some feedback.
> > Thanks;
> > — Matt Sanford
> > On Feb 11, 2009, at 02:04 PM, Matt Sanford wrote:
> > Hello Everyone,
> > Some of you are in the OAuth closed beta and some are not. I know that's
> > frustrating but we need to start small so we aren't buried in feature
> > requests and bugs all at once. Our intention is to discuss the OAuth
> > progress on this main API Google group
> > (http://groups.google.com/group/twitter-development-talk). If the discussion
> > gets in the way of the normal group operation please speak up and we can
> > always move it off to a new Google group of its own.
> > With all of that in mind we just launched the closed beta switch. If
> > you're one of the 150 or so people included in the closed beta your settings
> > page (http://twitter.com/account/settings) now contains a "Connections" tab.
> > In the sidebar is a little information and a link to register your very own
> > application. When you register a new application it will begin as suspended.
> > You'll have the technical details (the key and secret) you need to get
> > started but one of the Twitter admins will have to approve the application.
> > It is not our intention to leave this in place forever but during these
> > early application registrations we need to monitor things. Please use real
> > descriptions and meaningful names, since that' what we'll have to go on.
> > Especially meaningful names.
> > During the closed beta we're looking for feedback. The Google group is
> > good for discussing general issues and experiences but the Google code
> > issues are the best place for bugs and enhancements
> > (http://code.google.com/p/twitter-api/issues/listif you don't already
> > know). I added a new milestone of "OAuth", so please mark any bugs with the
> > correct milestone. When you report issues try to be specific about the
> > problem, especially in how to reproduce it. It would also save us some time
> > reviewing if you mark enhancements with "Type-Enhancement"in the appropriate
> > box.
> 2009/2/11 Matt Sanford <m...@twitter.com>: >> And the first bugs is … >> That some of you are not seeing the new "Connections" tab. It looks like >> a minor bug in the code that does the beta access check (which was new, >> never done a closed beta before). We're working on a fix now and will send >> it out with tomorrows morning deploy. I'll update the list once it's out. >> Sorry about that; >> — Matt Sanford >> On Feb 11, 2009, at 02:16 PM, Matt Sanford wrote:
>> And now for what I forgot, >> During this closed beta we recommend very strongly that you not do >> general software releases using the feature. If we find any security or >> performance problems we will need to turn off OAuth and I don't want to >> break your apps. Your app can sign up users who are not in the closed beta >> but since this is really a focus on getting feedback please try and limit >> the audience to people who you feel can provide some feedback. >> Thanks; >> — Matt Sanford >> On Feb 11, 2009, at 02:04 PM, Matt Sanford wrote:
>> Hello Everyone,
>> Some of you are in the OAuth closed beta and some are not. I know that's >> frustrating but we need to start small so we aren't buried in feature >> requests and bugs all at once. Our intention is to discuss the OAuth >> progress on this main API Google group >> (http://groups.google.com/group/twitter-development-talk). If the discussion >> gets in the way of the normal group operation please speak up and we can >> always move it off to a new Google group of its own.
>> With all of that in mind we just launched the closed beta switch. If >> you're one of the 150 or so people included in the closed beta your settings >> page (http://twitter.com/account/settings) now contains a "Connections" tab. >> In the sidebar is a little information and a link to register your very own >> application. When you register a new application it will begin as suspended. >> You'll have the technical details (the key and secret) you need to get >> started but one of the Twitter admins will have to approve the application. >> It is not our intention to leave this in place forever but during these >> early application registrations we need to monitor things. Please use real >> descriptions and meaningful names, since that' what we'll have to go on. >> Especially meaningful names.
>> During the closed beta we're looking for feedback. The Google group is >> good for discussing general issues and experiences but the Google code >> issues are the best place for bugs and enhancements >> (http://code.google.com/p/twitter-api/issues/list if you don't already >> know). I added a new milestone of "OAuth", so please mark any bugs with the >> correct milestone. When you report issues try to be specific about the >> problem, especially in how to reproduce it. It would also save us some time >> reviewing if you mark enhancements with "Type-Enhancement"in the appropriate >> box.
This bug with approved accounts not seeing the "Connections" tab should now be fixed. It may take a little time to roll out across the cluster so please give it an hour or so. I mentioned in the original email and wanted to reiterate for those just now getting access to the "Connections" tab: applications all start out suspended and have to be activated by someone from the Twitter side. That function is currently performed by me so if you register and application in the middle of the night (US pacific time) it won't get reviewed until the next day. Over the weekend it really depends on how much I am working so it will likely be Monday before I get to it.
> That some of you are not seeing the new "Connections" tab. It > looks like a minor bug in the code that does the beta access check > (which was new, never done a closed beta before). We're working on a > fix now and will send it out with tomorrows morning deploy. I'll > update the list once it's out.
> Sorry about that; > — Matt Sanford
> On Feb 11, 2009, at 02:16 PM, Matt Sanford wrote:
>> And now for what I forgot,
>> During this closed beta we recommend very strongly that you not >> do general software releases using the feature. If we find any >> security or performance problems we will need to turn off OAuth and >> I don't want to break your apps. Your app can sign up users who are >> not in the closed beta but since this is really a focus on getting >> feedback please try and limit the audience to people who you feel >> can provide some feedback.
>> Thanks; >> — Matt Sanford
>> On Feb 11, 2009, at 02:04 PM, Matt Sanford wrote:
>>> Hello Everyone,
>>> Some of you are in the OAuth closed beta and some are not. I >>> know that's frustrating but we need to start small so we aren't >>> buried in feature requests and bugs all at once. Our intention is >>> to discuss the OAuth progress on this main API Google group (http://groups.google.com/group/twitter-development-talk >>> ). If the discussion gets in the way of the normal group operation >>> please speak up and we can always move it off to a new Google >>> group of its own.
>>> With all of that in mind we just launched the closed beta >>> switch. If you're one of the 150 or so people included in the >>> closed beta your settings page (http://twitter.com/account/ >>> settings) now contains a "Connections" tab. In the sidebar is a >>> little information and a link to register your very own >>> application. When you register a new application it will begin as >>> suspended. You'll have the technical details (the key and secret) >>> you need to get started but one of the Twitter admins will have to >>> approve the application. It is not our intention to leave this in >>> place forever but during these early application registrations we >>> need to monitor things. Please use real descriptions and >>> meaningful names, since that' what we'll have to go on. Especially >>> meaningful names.
>>> During the closed beta we're looking for feedback. The Google >>> group is good for discussing general issues and experiences but >>> the Google code issues are the best place for bugs and >>> enhancements (http://code.google.com/p/twitter-api/issues/list if >>> you don't already know). I added a new milestone of "OAuth", so >>> please mark any bugs with the correct milestone. When you report >>> issues try to be specific about the problem, especially in how to >>> reproduce it. It would also save us some time reviewing if you >>> mark enhancements with "Type-Enhancement"in the appropriate box.
Quick suggestion: I'm not sure if this is a "bug" per se, but it would be handy if you got an email or some other notification upon having your submitted app approved.
> Quick suggestion: I'm not sure if this is a "bug" per se, but it would > be handy if you got an email or some other notification upon having > your submitted app approved.
I just did a successful test for Twittermail.com.
Implementin oAuth in our application was very easy, I didn't find any
bugs so-far.
I have a few questions:
- When is oAuth going to be live? At the moment it's still closed
beta, what's the timeline and when can we use it in production?
- I guess the authorize page will be updated when it's live? At the
moment it's just a Allow/Deny button, but people want to know sure
it's really Twitter (For those's who're too lazy to check the url).
I mean adding a header / footer for this page, stuff like that..
No more questions, I didn't any bugs, implementing was very easy, so
good work Twitter people! =)
On Sun, Feb 15, 2009 at 10:14 AM, Montoja <Lenn...@gmail.com> wrote:
> Hi all,
> I just did a successful test for Twittermail.com. > Implementin oAuth in our application was very easy, I didn't find any > bugs so-far.
> I have a few questions:
> - When is oAuth going to be live? At the moment it's still closed > beta, what's the timeline and when can we use it in production?
> - I guess the authorize page will be updated when it's live? At the > moment it's just a Allow/Deny button, but people want to know sure > it's really Twitter (For those's who're too lazy to check the url). > I mean adding a header / footer for this page, stuff like that..
> No more questions, I didn't any bugs, implementing was very easy, so > good work Twitter people! =)
> We're not sure if we're going to keep that review process in
> place or not. If we keep it we'll add and email notification. Thanks
> for the suggestion.
> Cheers;
> — Matt
> On Feb 13, 2009, at 12:32 PM, Chad Etzel wrote:
> > Quick suggestion: I'm not sure if this is a "bug" per se, but it would
> > be handy if you got an email or some other notification upon having
> > your submitted app approved.
> You looking for any more beta testers? I wouldn't mind testing it out > with some of my WordPress plugins that use the Twitter API. Please > let me know.
> Thanks, > Duane
> On Feb 13, 12:38 pm, Matt Sanford <m...@twitter.com> wrote: >> Hi Chad,
>> We're not sure if we're going to keep that review process in >> place or not. If we keep it we'll add and email notification. Thanks >> for the suggestion.
>> Cheers; >> — Matt
>> On Feb 13, 2009, at 12:32 PM, Chad Etzel wrote:
>>> Quick suggestion: I'm not sure if this is a "bug" per se, but it >>> would >>> be handy if you got an email or some other notification upon having >>> your submitted app approved.
> What language did you use for oAuth programming?
> On Sun, Feb 15, 2009 at 10:14 AM, Montoja <Lenn...@gmail.com> wrote:
> > Hi all,
> > I just did a successful test for Twittermail.com.
> > Implementin oAuth in our application was very easy, I didn't find any
> > bugs so-far.
> > I have a few questions:
> > - When is oAuth going to be live? At the moment it's still closed
> > beta, what's the timeline and when can we use it in production?
> > - I guess the authorize page will be updated when it's live? At the
> > moment it's just a Allow/Deny button, but people want to know sure
> > it's really Twitter (For those's who're too lazy to check the url).
> > I mean adding a header / footer for this page, stuff like that..
> > No more questions, I didn't any bugs, implementing was very easy, so
> > good work Twitter people! =)
