[twitter-dev] Server-2-Server & User Streams

2010-04-22 Thread Darren Bounds (Cliqset)
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

[twitter-dev] Streaming API : Shadow white listing

2009-12-03 Thread Darren Bounds (Cliqset)
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 sha

[twitter-dev] Streaming API statuses/filter access increase request

2009-11-05 Thread Darren Bounds (Cliqset)
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 current

[twitter-dev] Re: heavy throttling by search.twitter.com API from GAE application

2009-08-22 Thread Darren Bounds (Cliqset)
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 wrote: > Hello, > > I have replied to Jud off-list, but for everyone's benefit we'd like > to reiterate that AWS and GAE are