[twitter-dev] Re: [twitter-api-announce] Streaming API access limits increased

2010-08-30 Thread John Kalucki
Spritzer remains at 1%. We can't increase this one at the moment due to
technical reasons unrelated to capacity or policy. We'll probably leave this
at 1% for a while.

Ha. Totally unrelated to Snowflake. Related changes coming soon though.

-John



On Tue, Aug 31, 2010 at 4:30 AM, M. Edward (Ed) Borasky 
zn...@borasky-research.net wrote:

 Spritzer is still approximately 1%, right? And this is algorithmically
 intertwined with Snowflake, right? ;-)

 Pushing Follow up from 400 to 5000 is a huge win for one of my apps - I'll
 have to see if I can accept that much data, though ;-)

 --
 M. Edward (Ed) Borasky
 http://borasky-research.net http://twitter.com/znmeb

 A mathematician is a device for turning coffee into theorems. - Paul
 Erdos



 Quoting John Kalucki j...@twitter.com:

  Recently we dropped the Gardenhose sample rate down from roughly 15% to
 roughly 5% of all public statuses in response to a capacity limitation.
 We've added considerable bandwidth headroom to the
 stream.twitter.comcluster, and we've provisionally increased the

 sample to roughly 10%. As
 documented since the release of the sampled endpoint, this rate is subject
 to continuous and unannounced change. Note that roughly X percent
 remains
 a somewhat complicated proportion that varies in response to certain other
 proportions in the Twitter system and is not an precise description of the
 sampling algorithm.


 We've also increased a number of limits on other endpoints to better
 reflect
 current usage:

 Shadow: 80,000 accounts to 100,000 accounts

 Follow: 400 accounts to 5,000 accounts

 LocationRestricted and LocationDefault bounding boxes can now be up to
 360-degrees per side. This allows total coverage at the potential risk
 of inducing filter rate limits.

 LocationDefault: 10 boxes to 25 boxes



 Please pardon what is a late-night production change for many developers.
 Caution dictates an off-peak deploy of these rate limit changes.

 -John Kalucki
 http://twitter.com/jkalucki
 Twitter, Inc.

 --
 Twitter API documentation and resources: http://dev.twitter.com/doc
 API updates via Twitter: http://twitter.com/twitterapi
 Change your membership to this group:
 http://groups.google.com/group/twitter-api-announce?hl=en






-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk?hl=en


Re: [twitter-dev] Re: [twitter-api-announce] Streaming API access limits increased

2010-08-30 Thread Doug Tangren
I am loving the terminology.

-Doug Tangren
http://lessis.me


On Mon, Aug 30, 2010 at 9:33 PM, John Kalucki j...@twitter.com wrote:

 Spritzer remains at 1%. We can't increase this one at the moment due to
 technical reasons unrelated to capacity or policy. We'll probably leave this
 at 1% for a while.

 Ha. Totally unrelated to Snowflake. Related changes coming soon though.

 -John



 On Tue, Aug 31, 2010 at 4:30 AM, M. Edward (Ed) Borasky 
 zn...@borasky-research.net wrote:

 Spritzer is still approximately 1%, right? And this is algorithmically
 intertwined with Snowflake, right? ;-)

 Pushing Follow up from 400 to 5000 is a huge win for one of my apps - I'll
 have to see if I can accept that much data, though ;-)

 --
 M. Edward (Ed) Borasky
 http://borasky-research.net http://twitter.com/znmeb

 A mathematician is a device for turning coffee into theorems. - Paul
 Erdos



 Quoting John Kalucki j...@twitter.com:

  Recently we dropped the Gardenhose sample rate down from roughly 15% to
 roughly 5% of all public statuses in response to a capacity limitation.
 We've added considerable bandwidth headroom to the
 stream.twitter.comcluster, and we've provisionally increased the

 sample to roughly 10%. As
 documented since the release of the sampled endpoint, this rate is
 subject
 to continuous and unannounced change. Note that roughly X percent
 remains
 a somewhat complicated proportion that varies in response to certain
 other
 proportions in the Twitter system and is not an precise description of
 the
 sampling algorithm.


 We've also increased a number of limits on other endpoints to better
 reflect
 current usage:

 Shadow: 80,000 accounts to 100,000 accounts

 Follow: 400 accounts to 5,000 accounts

 LocationRestricted and LocationDefault bounding boxes can now be up to
 360-degrees per side. This allows total coverage at the potential risk
 of inducing filter rate limits.

 LocationDefault: 10 boxes to 25 boxes



 Please pardon what is a late-night production change for many developers.
 Caution dictates an off-peak deploy of these rate limit changes.

 -John Kalucki
 http://twitter.com/jkalucki
 Twitter, Inc.

 --
 Twitter API documentation and resources: http://dev.twitter.com/doc
 API updates via Twitter: http://twitter.com/twitterapi
 Change your membership to this group:
 http://groups.google.com/group/twitter-api-announce?hl=en





  --
 Twitter developer documentation and resources: http://dev.twitter.com/doc

 API updates via Twitter: http://twitter.com/twitterapi
 Issues/Enhancements Tracker:
 http://code.google.com/p/twitter-api/issues/list
 Change your membership to this group:
 http://groups.google.com/group/twitter-development-talk?hl=en


-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk?hl=en