Re: [twitter-dev] Re: [twitter-api-announce] Streaming API access limits increased
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
[twitter-dev] Re: Multiple language support for your Twitter application
If anyone is interested, I have a small contribution I wrote a while back (http://softprops.github.com/bird-speak/). It's a bookmarklet that reads the lang attribute of the html tag on twitter.com and asks googles translate api to translate all of the tweets on the current page into that language. Its probably not that helpful for all those not actually using the web ui, but for those interested, its up on the githubs (http://github.com/softprops/bird-speak/blob/master/). -Doug Tangren http://lessis.me @softprops On Thu, Oct 8, 2009 at 6:08 PM, Marcel Molina mar...@twitter.com wrote: Over on the main Twitter blog we've just announced that we'll be translating the site into French, Italian, Spanish and German soon, with more languages to come later (http://bit.ly/LIa4C). We figured a lot of folks building apps on the Twitter Platform might be interested in providing their applications in various languages too but haven't had the time or resources to take on building up full translations. So we are planning to provide our translation files to the developer community. We hope they're useful as at least a starting point for your own. We're just getting started. We'll follow up with more details about where you'll be able to get these translations soon. -- Marcel Molina Twitter Platform Team http://twitter.com/noradio
[twitter-dev] Re: Can we make this a private list?
On Mon, Mar 30, 2009 at 1:02 PM, Andrew Badera and...@badera.us wrote: Chad: what you state IS quite desirable, but is, unfortunately, equally not feasible. You can moderate join requests, you can moderate members' posts, but the distinction you seem to be looking for in your original email is near-impossible to establish. Perhaps membership to the list should be predicated on assignment of a source parameter, and detection of that parameter being in-use? (This would cut off a lot of casual or tangential looky-loos ... not unlike myself, who either haven't had need to apply, or have applied and simply haven't used. It could be a decent yardstick ... but then you have people doing widgets and other integrations, who may never need a source param ...) In my case, I just started developing using twitters api. I came here to ask you guys questions for help. I have no app in production so I can't refer anyone to a particular project. I came here so seek info. I'd feel put off if I couldn't learn anything just because I haven't built anything with twitters api before. Thats kind of a catch22. On Mon, Mar 30, 2009 at 11:42 AM, Chad Etzel jazzyc...@gmail.com wrote: On Mon, Mar 30, 2009 at 8:58 AM, Clint Shryock cts...@gmail.com wrote: How then would you propose acceptance to this group is determined? I don't know, that's why I'm asking. I've never admin'd a google group before. I think it's in Twitter's best interest to allow information on their API for new developers as accessible as possible to build their platform. This list is a great resource in accomplishing that. In my opinion you should have contacted people from this list you've had interactions with privately and shown them in that manner. Otherwise, I would have solicited people interested in screening an app. That, of course, is an option, but getting responses to anything posted here is a total crapshoot, and sending a message to a subset of those people makes chances for a response even worse. I'd rather send a message to the group since that's what it is for, without fear of having it be spread all over the place. Maybe that's not possible, and I can deal with that. Anyway, it was just a suggestion/question. Maybe it's not feasible. If not, then nevermind :) -chad
