[twitter-dev] Re: Streaming API Terms Of Service change - multiple simultaneous logins discouraged
Not to be picky, but can we get these announcements on the twitter-announce list in the future? Who is this John and is he a real Twitter employee? On Sat, May 9, 2009 at 10:04 PM, John Kalucki wrote: > > Note: The Streaming API is currently under a limited alpha test, > details below. > > Multiple concurrent connections from the same account are discouraged > on the Streaming API. Starting on or after the afternoon of Monday, > May 11th (22:00:00 11-May-2009 UTC) the service will gently enforce > this policy. A later release will fully enforce this policy. > Subsequent connections from the same account will cause previously > established connections to be disconnected. > > In some cases, this might cause operational difficulties for > developers who are using the restricted resources. For example, a > developer's staging test might knock that developer's production / > gardenhose feed offline. Non-production uses should connect to the / > spritzer resource with a secondary account to avoid these conflicts. > We may, on a case-by-case basis, grant exceptions to this policy as we > work through the alpha test. We will attempt to balance ease-of-use, > resource consumption and abuse prevention. > > -John Kalucki - Services, Twitter Inc. > http://twitter.com/jkalucki > > > > Important Alpha Test Note: > The Streaming API (aka Hosebird) is currently under an alpha test. All > developers using the Streaming API must tolerate possible unannounced > and extended periods of unavailability, especially during off-hours, > Pacific Time. New features, resources and policies are being deployed > on very little, if any, notice. Any developer may experiment with the > unrestricted resources and provide feedback via this list. Access to > restricted resources is extremely limited and is only granted on a > case-by-case basis after acceptance of an additional terms of service > document. Documentation is available: > http://apiwiki.twitter.com/Streaming-API-Documentation. >
[twitter-dev] Re: Streaming API Terms Of Service change - multiple simultaneous logins discouraged
Jesse, We will announce this to the announce list when we feel it is ready for a larger audience. John is a Twitter employee and is developing the streaming service. Be sure to give him a thanks if you use his stuff. Doug -- Doug Williams Twitter Platform Support http://twitter.com/dougw On Sat, May 9, 2009 at 9:51 PM, Jesse Stay wrote: > Not to be picky, but can we get these announcements on the twitter-announce > list in the future? Who is this John and is he a real Twitter employee? > > On Sat, May 9, 2009 at 10:04 PM, John Kalucki wrote: > >> >> Note: The Streaming API is currently under a limited alpha test, >> details below. >> >> Multiple concurrent connections from the same account are discouraged >> on the Streaming API. Starting on or after the afternoon of Monday, >> May 11th (22:00:00 11-May-2009 UTC) the service will gently enforce >> this policy. A later release will fully enforce this policy. >> Subsequent connections from the same account will cause previously >> established connections to be disconnected. >> >> In some cases, this might cause operational difficulties for >> developers who are using the restricted resources. For example, a >> developer's staging test might knock that developer's production / >> gardenhose feed offline. Non-production uses should connect to the / >> spritzer resource with a secondary account to avoid these conflicts. >> We may, on a case-by-case basis, grant exceptions to this policy as we >> work through the alpha test. We will attempt to balance ease-of-use, >> resource consumption and abuse prevention. >> >> -John Kalucki - Services, Twitter Inc. >> http://twitter.com/jkalucki >> >> >> >> Important Alpha Test Note: >> The Streaming API (aka Hosebird) is currently under an alpha test. All >> developers using the Streaming API must tolerate possible unannounced >> and extended periods of unavailability, especially during off-hours, >> Pacific Time. New features, resources and policies are being deployed >> on very little, if any, notice. Any developer may experiment with the >> unrestricted resources and provide feedback via this list. Access to >> restricted resources is extremely limited and is only granted on a >> case-by-case basis after acceptance of an additional terms of service >> document. Documentation is available: >> http://apiwiki.twitter.com/Streaming-API-Documentation. >> > >
[twitter-dev] Re: Streaming API Terms Of Service change - multiple simultaneous logins discouraged
Just to clarify, are we limited to one resource per account? If i connect to /spritzer on a test server, will that knock off my connection to /gardenhose on my production server if I use the same account? -Ben On May 9, 11:04 pm, John Kalucki wrote: > Note: The Streaming API is currently under a limited alpha test, > details below. > > Multiple concurrent connections from the same account are discouraged > on the Streaming API. Starting on or after the afternoon of Monday, > May 11th (22:00:00 11-May-2009 UTC) the service will gently enforce > this policy. A later release will fully enforce this policy. > Subsequent connections from the same account will cause previously > established connections to be disconnected. > > In some cases, this might cause operational difficulties for > developers who are using the restricted resources. For example, a > developer's staging test might knock that developer's production / > gardenhose feed offline. Non-production uses should connect to the / > spritzer resource with a secondary account to avoid these conflicts. > We may, on a case-by-case basis, grant exceptions to this policy as we > work through the alpha test. We will attempt to balance ease-of-use, > resource consumption and abuse prevention. > > -John Kalucki - Services, Twitter Inc.http://twitter.com/jkalucki > > Important Alpha Test Note: > The Streaming API (aka Hosebird) is currently under an alpha test. All > developers using the Streaming API must tolerate possible unannounced > and extended periods of unavailability, especially during off-hours, > Pacific Time. New features, resources and policies are being deployed > on very little, if any, notice. Any developer may experiment with the > unrestricted resources and provide feedback via this list. Access to > restricted resources is extremely limited and is only granted on a > case-by-case basis after acceptance of an additional terms of service > document. Documentation is > available:http://apiwiki.twitter.com/Streaming-API-Documentation.
[twitter-dev] Re: Streaming API Terms Of Service change - multiple simultaneous logins discouraged
Once the service fully enforces the intended policy, then yes, a / spritzer login will knock off a /gardenhose login, or visa versa. The current intention is for developers to create a /gardenhose production account and a testing /spritzer account. At first glance, this requirement does not appear too onerous. Unfortunately such clients will require the login credentials to be predicated on production status. If we're missing a use case, let's discuss. We have options at this early stage. -John Kalucki - Services, Twitter Inc. http://twitter.com/jkalucki On May 10, 12:55 pm, benburkert wrote: > Just to clarify, are we limited to one resource per account? If i > connect to /spritzer on a test server, will that knock off my > connection to /gardenhose on my production server if I use the same > account? > > -Ben > > On May 9, 11:04 pm, John Kalucki wrote: > > > Note: The Streaming API is currently under a limited alpha test, > > details below. > > > Multiple concurrent connections from the same account are discouraged > > on the Streaming API. Starting on or after the afternoon of Monday, > > May 11th (22:00:00 11-May-2009 UTC) the service will gently enforce > > this policy. A later release will fully enforce this policy. > > Subsequent connections from the same account will cause previously > > established connections to be disconnected. > > > In some cases, this might cause operational difficulties for > > developers who are using the restricted resources. For example, a > > developer's staging test might knock that developer's production / > > gardenhose feed offline. Non-production uses should connect to the / > > spritzer resource with a secondary account to avoid these conflicts. > > We may, on a case-by-case basis, grant exceptions to this policy as we > > work through the alpha test. We will attempt to balance ease-of-use, > > resource consumption and abuse prevention. > > > -John Kalucki - Services, Twitter Inc.http://twitter.com/jkalucki > > > Important Alpha Test Note: > > The Streaming API (aka Hosebird) is currently under an alpha test. All > > developers using the Streaming API must tolerate possible unannounced > > and extended periods of unavailability, especially during off-hours, > > Pacific Time. New features, resources and policies are being deployed > > on very little, if any, notice. Any developer may experiment with the > > unrestricted resources and provide feedback via this list. Access to > > restricted resources is extremely limited and is only granted on a > > case-by-case basis after acceptance of an additional terms of service > > document. Documentation is > > available:http://apiwiki.twitter.com/Streaming-API-Documentation.
[twitter-dev] Re: Streaming API Terms Of Service change - multiple simultaneous logins discouraged
Thanks Doug - I just wanted to be sure we weren't venturing away from this practice. I'll often miss it if it's not on the announce list, and it's a great way to know for sure it's coming from Twitter. Thanks for your work John! I don't use your service now but if I ever do I think the streaming API is very important to the future of Twitter. Jesse On Sun, May 10, 2009 at 1:20 PM, Doug Williams wrote: > Jesse, > We will announce this to the announce list when we feel it is ready for a > larger audience. > > John is a Twitter employee and is developing the streaming service. Be sure > to give him a thanks if you use his stuff. > > Doug > -- > > Doug Williams > Twitter Platform Support > http://twitter.com/dougw > > > > > > On Sat, May 9, 2009 at 9:51 PM, Jesse Stay wrote: > >> Not to be picky, but can we get these announcements on the >> twitter-announce list in the future? Who is this John and is he a real >> Twitter employee? >> >> On Sat, May 9, 2009 at 10:04 PM, John Kalucki wrote: >> >>> >>> Note: The Streaming API is currently under a limited alpha test, >>> details below. >>> >>> Multiple concurrent connections from the same account are discouraged >>> on the Streaming API. Starting on or after the afternoon of Monday, >>> May 11th (22:00:00 11-May-2009 UTC) the service will gently enforce >>> this policy. A later release will fully enforce this policy. >>> Subsequent connections from the same account will cause previously >>> established connections to be disconnected. >>> >>> In some cases, this might cause operational difficulties for >>> developers who are using the restricted resources. For example, a >>> developer's staging test might knock that developer's production / >>> gardenhose feed offline. Non-production uses should connect to the / >>> spritzer resource with a secondary account to avoid these conflicts. >>> We may, on a case-by-case basis, grant exceptions to this policy as we >>> work through the alpha test. We will attempt to balance ease-of-use, >>> resource consumption and abuse prevention. >>> >>> -John Kalucki - Services, Twitter Inc. >>> http://twitter.com/jkalucki >>> >>> >>> >>> Important Alpha Test Note: >>> The Streaming API (aka Hosebird) is currently under an alpha test. All >>> developers using the Streaming API must tolerate possible unannounced >>> and extended periods of unavailability, especially during off-hours, >>> Pacific Time. New features, resources and policies are being deployed >>> on very little, if any, notice. Any developer may experiment with the >>> unrestricted resources and provide feedback via this list. Access to >>> restricted resources is extremely limited and is only granted on a >>> case-by-case basis after acceptance of an additional terms of service >>> document. Documentation is available: >>> http://apiwiki.twitter.com/Streaming-API-Documentation. >>> >> >> >
[twitter-dev] Re: Streaming API Terms Of Service change - multiple simultaneous logins discouraged
Oh god. Please share where is this twitter-announce list? -- Hwee-Boon On May 10, 12:51 pm, Jesse Stay wrote: > Not to be picky, but can we get these announcements on the twitter-announce > list in the future? Who is this John and is he a real Twitter employee? > > > > On Sat, May 9, 2009 at 10:04 PM, John Kalucki wrote: > > > Note: The Streaming API is currently under a limited alpha test, > > details below. > > > Multiple concurrent connections from the same account are discouraged > > on the Streaming API. Starting on or after the afternoon of Monday, > > May 11th (22:00:00 11-May-2009 UTC) the service will gently enforce > > this policy. A later release will fully enforce this policy. > > Subsequent connections from the same account will cause previously > > established connections to be disconnected. > > > In some cases, this might cause operational difficulties for > > developers who are using the restricted resources. For example, a > > developer's staging test might knock that developer's production / > > gardenhose feed offline. Non-production uses should connect to the / > > spritzer resource with a secondary account to avoid these conflicts. > > We may, on a case-by-case basis, grant exceptions to this policy as we > > work through the alpha test. We will attempt to balance ease-of-use, > > resource consumption and abuse prevention. > > > -John Kalucki - Services, Twitter Inc. > >http://twitter.com/jkalucki > > > Important Alpha Test Note: > > The Streaming API (aka Hosebird) is currently under an alpha test. All > > developers using the Streaming API must tolerate possible unannounced > > and extended periods of unavailability, especially during off-hours, > > Pacific Time. New features, resources and policies are being deployed > > on very little, if any, notice. Any developer may experiment with the > > unrestricted resources and provide feedback via this list. Access to > > restricted resources is extremely limited and is only granted on a > > case-by-case basis after acceptance of an additional terms of service > > document. Documentation is available: > >http://apiwiki.twitter.com/Streaming-API-Documentation.
[twitter-dev] Re: Streaming API Terms Of Service change - multiple simultaneous logins discouraged
Nice work guys, talk about the firehose has been floating around for ages, great to see it finally appear and with numerous variants available (thats a bonus). I personally don't have any use for it (yet) but I'm sure it'll please quite a few. On May 10, 2:04 pm, John Kalucki wrote: > Note: The Streaming API is currently under a limited alpha test, > details below. > > Multiple concurrent connections from the same account are discouraged > on the Streaming API. Starting on or after the afternoon of Monday, > May 11th (22:00:00 11-May-2009 UTC) the service will gently enforce > this policy. A later release will fully enforce this policy. > Subsequent connections from the same account will cause previously > established connections to be disconnected. > > In some cases, this might cause operational difficulties for > developers who are using the restricted resources. For example, a > developer's staging test might knock that developer's production / > gardenhose feed offline. Non-production uses should connect to the / > spritzer resource with a secondary account to avoid these conflicts. > We may, on a case-by-case basis, grant exceptions to this policy as we > work through the alpha test. We will attempt to balance ease-of-use, > resource consumption and abuse prevention. > > -John Kalucki - Services, Twitter Inc.http://twitter.com/jkalucki > > Important Alpha Test Note: > The Streaming API (aka Hosebird) is currently under an alpha test. All > developers using the Streaming API must tolerate possible unannounced > and extended periods of unavailability, especially during off-hours, > Pacific Time. New features, resources and policies are being deployed > on very little, if any, notice. Any developer may experiment with the > unrestricted resources and provide feedback via this list. Access to > restricted resources is extremely limited and is only granted on a > case-by-case basis after acceptance of an additional terms of service > document. Documentation is > available:http://apiwiki.twitter.com/Streaming-API-Documentation.
[twitter-dev] Re: Streaming API Terms Of Service change - multiple simultaneous logins discouraged
John, Do the concurrent connections apply to the birddog/shadow/follow feeds as well? I can see a use case where I might want to set up multiple connections to these services, i.e. I want to set up a stream for x,y and z users and another stream for p,q and r users. Is that a valid use of those streams? Thanks, dpc On May 9, 9:04 pm, John Kalucki wrote: > Note: The Streaming API is currently under a limited alpha test, > details below. > > Multiple concurrent connections from the same account are discouraged > on the Streaming API. Starting on or after the afternoon of Monday, > May 11th (22:00:00 11-May-2009 UTC) the service will gently enforce > this policy. A later release will fully enforce this policy. > Subsequent connections from the same account will cause previously > established connections to be disconnected. > > In some cases, this might cause operational difficulties for > developers who are using the restricted resources. For example, a > developer's staging test might knock that developer's production / > gardenhose feed offline. Non-production uses should connect to the / > spritzer resource with a secondary account to avoid these conflicts. > We may, on a case-by-case basis, grant exceptions to this policy as we > work through the alpha test. We will attempt to balance ease-of-use, > resource consumption and abuse prevention. > > -John Kalucki - Services, Twitter Inc.http://twitter.com/jkalucki > > Important Alpha Test Note: > The Streaming API (akaHosebird) is currently under an alpha test. All > developers using the Streaming API must tolerate possible unannounced > and extended periods of unavailability, especially during off-hours, > Pacific Time. New features, resources and policies are being deployed > on very little, if any, notice. Any developer may experiment with the > unrestricted resources and provide feedback via this list. Access to > restricted resources is extremely limited and is only granted on a > case-by-case basis after acceptance of an additional terms of service > document. Documentation is > available:http://apiwiki.twitter.com/Streaming-API-Documentation.
[twitter-dev] Re: Streaming API Terms Of Service change - multiple simultaneous logins discouraged
Damon, Interesting use cases are starting to pop up! For now, yes, the concurrent connection limit applies to all resources. If you want streams for various sets of users, we'd ask that you just set up one stream and multiplex all your requests over the same connection. You'll have to do the demux on your end, but that should be easy enough. -John On May 13, 11:40 pm, "Damon P. Cortesi" wrote: > John, > > Do the concurrent connections apply to the birddog/shadow/follow feeds > as well? > > I can see a use case where I might want to set up multiple connections > to these services, i.e. I want to set up a stream for x,y and z users > and another stream for p,q and r users. > > Is that a valid use of those streams? > > Thanks, > > dpc > > On May 9, 9:04 pm, John Kalucki wrote: > > > Note: The Streaming API is currently under a limited alpha test, > > details below. > > > Multiple concurrent connections from the same account are discouraged > > on the Streaming API. Starting on or after the afternoon of Monday, > > May 11th (22:00:00 11-May-2009 UTC) the service will gently enforce > > this policy. A later release will fully enforce this policy. > > Subsequent connections from the same account will cause previously > > established connections to be disconnected. > > > In some cases, this might cause operational difficulties for > > developers who are using the restricted resources. For example, a > > developer's staging test might knock that developer's production / > > gardenhose feed offline. Non-production uses should connect to the / > > spritzer resource with a secondary account to avoid these conflicts. > > We may, on a case-by-case basis, grant exceptions to this policy as we > > work through the alpha test. We will attempt to balance ease-of-use, > > resource consumption and abuse prevention. > > > -John Kalucki - Services, Twitter Inc.http://twitter.com/jkalucki > > > Important Alpha Test Note: > > The Streaming API (akaHosebird) is currently under an alpha test. All > > developers using the Streaming API must tolerate possible unannounced > > and extended periods of unavailability, especially during off-hours, > > Pacific Time. New features, resources and policies are being deployed > > on very little, if any, notice. Any developer may experiment with the > > unrestricted resources and provide feedback via this list. Access to > > restricted resources is extremely limited and is only granted on a > > case-by-case basis after acceptance of an additional terms of service > > document. Documentation is > > available:http://apiwiki.twitter.com/Streaming-API-Documentation.
[twitter-dev] Re: Streaming API Terms Of Service change - multiple simultaneous logins discouraged
Hello John (or other appropriate Twitter Services person) We are a new start up called FanTwits.com. We are seeking the agreement for use of the Twitter API (for "Garden Hose"). We would ideally like to be considered for "Firehose". However, in reading through the documentation, we recognize that this seems to be invite- only. FanTwits is being designed to be a user community focused on sports. We have angel funding and consider our endeavor to be quite serious. Can you please direct me to the Twitter API agreement for "Garden Hose" or identify how we could go about getting consideration for "Firehose"? Thank you, Scott Sherman CEO & Founder FanTwits 917-282-7980 On May 10, 12:04 am, John Kalucki wrote: > Note: The Streaming API is currently under a limited alpha test, > details below. > > Multiple concurrent connections from the same account are discouraged > on the Streaming API. Starting on or after the afternoon of Monday, > May 11th (22:00:00 11-May-2009 UTC) the service will gently enforce > this policy. A later release will fully enforce this policy. > Subsequent connections from the same account will cause previously > established connections to be disconnected. > > In some cases, this might cause operational difficulties for > developers who are using the restricted resources. For example, a > developer's staging test might knock that developer's production / > gardenhose feed offline. Non-production uses should connect to the / > spritzer resource with a secondary account to avoid these conflicts. > We may, on a case-by-case basis, grant exceptions to this policy as we > work through the alpha test. We will attempt to balance ease-of-use, > resource consumption and abuse prevention. > > -John Kalucki - Services, Twitter Inc.http://twitter.com/jkalucki > > Important Alpha Test Note: > The Streaming API (aka Hosebird) is currently under an alpha test. All > developers using the Streaming API must tolerate possible unannounced > and extended periods of unavailability, especially during off-hours, > Pacific Time. New features, resources and policies are being deployed > on very little, if any, notice. Any developer may experiment with the > unrestricted resources and provide feedback via this list. Access to > restricted resources is extremely limited and is only granted on a > case-by-case basis after acceptance of an additional terms of service > document. Documentation is > available:http://apiwiki.twitter.com/Streaming-API-Documentation.
[twitter-dev] Re: Streaming API Terms Of Service change - multiple simultaneous logins discouraged
John, Can we have two concurrent connections, one each to the methods gardenhose and shadow from a single Twitter account? Thanks, Karthik On May 10, 9:04 am, John Kalucki wrote: > Note: TheStreamingAPI is currently under a limited alpha test, > details below. > > Multiple concurrent connections from the same account are discouraged > on theStreamingAPI. Starting on or after the afternoon of Monday, > May 11th (22:00:00 11-May-2009 UTC) the service will gently enforce > this policy. A later release will fully enforce this policy. > Subsequent connections from the same account will cause previously > established connections to be disconnected. > > In some cases, this might cause operational difficulties for > developers who are using the restricted resources. For example, a > developer's staging test might knock that developer's production / > gardenhose feed offline. Non-production uses should connect to the / > spritzer resource with a secondary account to avoid these conflicts. > We may, on a case-by-case basis, grant exceptions to this policy as we > work through the alpha test. We will attempt to balance ease-of-use, > resource consumption and abuse prevention. > > -John Kalucki - Services, Twitter Inc.http://twitter.com/jkalucki > > Important Alpha Test Note: > TheStreamingAPI (aka Hosebird) is currently under an alpha test. All > developers using theStreamingAPI must tolerate possible unannounced > and extended periods of unavailability, especially during off-hours, > Pacific Time. New features, resources and policies are being deployed > on very little, if any, notice. Any developer may experiment with the > unrestricted resources and provide feedback via this list. Access to > restricted resources is extremely limited and is only granted on a > case-by-case basis after acceptance of an additional terms of service > document. Documentation is > available:http://apiwiki.twitter.com/Streaming-API-Documentation.
[twitter-dev] Re: Streaming API Terms Of Service change - multiple simultaneous logins discouraged
You can't have multiple logins per account at the moment. In general, contact the API group for help with this. In this case, I'll set things up for you. -John Kalucki Services, Twitter Inc. On Jun 23, 7:26 am, கார்த்திக்.மு wrote: > John, > > Can we have two concurrent connections, one each to the methods > gardenhose and shadow from a single Twitter account? > > Thanks, > Karthik > > On May 10, 9:04 am, John Kalucki wrote: > > > Note: TheStreamingAPI is currently under a limited alpha test, > > details below. > > > Multiple concurrent connections from the same account are discouraged > > on theStreamingAPI. Starting on or after the afternoon of Monday, > > May 11th (22:00:00 11-May-2009 UTC) the service will gently enforce > > this policy. A later release will fully enforce this policy. > > Subsequent connections from the same account will cause previously > > established connections to be disconnected. > > > In some cases, this might cause operational difficulties for > > developers who are using the restricted resources. For example, a > > developer's staging test might knock that developer's production / > > gardenhose feed offline. Non-production uses should connect to the / > > spritzer resource with a secondary account to avoid these conflicts. > > We may, on a case-by-case basis, grant exceptions to this policy as we > > work through the alpha test. We will attempt to balance ease-of-use, > > resource consumption and abuse prevention. > > > -John Kalucki - Services, Twitter Inc.http://twitter.com/jkalucki > > > Important Alpha Test Note: > > TheStreamingAPI (aka Hosebird) is currently under an alpha test. All > > developers using theStreamingAPI must tolerate possible unannounced > > and extended periods of unavailability, especially during off-hours, > > Pacific Time. New features, resources and policies are being deployed > > on very little, if any, notice. Any developer may experiment with the > > unrestricted resources and provide feedback via this list. Access to > > restricted resources is extremely limited and is only granted on a > > case-by-case basis after acceptance of an additional terms of service > > document. Documentation is > > available:http://apiwiki.twitter.com/Streaming-API-Documentation.
