[twitter-dev] Server-2-Server User Streams
Hello! While it has been documented that the Twitter User Streams API is designed predominantly for server-2-client interactions, I'm wondering how Twitter feels about a service provider (like Cliqset) attempting to behave within the bounds of a typical User Streams usage pattern. At a high level what I mean by 'behave' is that the Cliqset website would exhibit the behavior of a desktop application, establishing connectivity to the User Stream only when Twitter user was active within the application. The only caveat would be the need for multiple authenticated connections from 1 or more hosts. Is this something that would be frowned upon by Twitter or can we explore this further? Thanks, Darren -- Subscription settings: http://groups.google.com/group/twitter-development-talk/subscribe?hl=en
[twitter-dev] Streaming API : Shadow white listing
Hello, Several weeks ago (approximately 5) we (Cliqset) submitted a request to increase our 'shadow' user limit to 10,000 from the default of 400. We haven't heard back. In our desperation to migrate to streaming without violating Twitter ToS or trigger rate limiting, we recently attempted to shard across multiple Twitter user accounts and subsequently streaming connections. This resulted in TCP level resets to the streaming API. Not fun. That said; we currently have several thousand users which we'd like to transition to streaming from polling but feel like we've run out of options. Can anyone assist us or provide any sort of guidance in getting things moving? Thank you. Darren Cliqset, Inc.
[twitter-dev] Streaming API statuses/filter access increase request
Hello, Several days ago we (Cliqset) made a request via the API whiltelisting form for an increase to our default 'statuses/filter' follow user limit (400). The request came back today as rejected with no content in the 'reason why' section. Is there some way we can resubmit directly? We currently have several thousand users whom we'd like to roll out to use the streaming API which we've tested thoroughly but are currently limited to 400. Any assistance would be greatly appreciated. Thanks! Darren Cliqset.com
[twitter-dev] Re: heavy throttling by search.twitter.com API from GAE application
Hello Chad, Can you confirm that this is not the case for AWS elastic IPs which had been previously whitelisted by Twitter? Thanks, Darren On Aug 21, 4:35 pm, Chad Etzel jazzyc...@gmail.com wrote: Hello, I have replied to Jud off-list, but for everyone's benefit we'd like to reiterate that AWS and GAE are shared resources and therefore share the rate limit across applications. A dedicated IP and unique UA will guarantee the maximum API limits. There are several cheap and reliable VPS hosting services available which can provide a dedicated IP address and full control over the server. Thanks, -Chad On Fri, Aug 21, 2009 at 12:48 PM, Judjvale...@gmail.com wrote: I've got a python app running on Google App Engine (appspot hosted) that querieshttp://search.twitter.com/search.atom?q=for simple queries (e.g. foo OR bar), and it's being severely throttled (e.g. can't get a successful request through (response 200 w/ data) more than a couple of times per _hour_). - I'm setting the UA string to something unique/identifiable (e.g. my company name) - I'm respecting the retry-after header coming back when I see a 503 (average retry-after duration is ~750) - GAE turns the IP address behind the app over ~ every 6 hours - app hits tries to hit search.twitter.com every 5 minutes. I've successfully polled the endpoint at much higher rates (in completely different IP address ranges) in the past, without issue. Unclear what's going on. Any suggestions would be greatly appreciated.
