BTW, I see that applications that authenticate with oAuth are going to
get a 10X increase in the number of API calls they can make per hour.
When does that go into effect?
On Dec 20, 3:55 pm, M. Edward (Ed) Borasky zzn...@gmail.com wrote:
On Dec 18, 9:23 am, Raffi Krikorian ra...@twitter.com
On Dec 18, 9:23 am, Raffi Krikorian ra...@twitter.com wrote:
Will the geo-hose streaming API return only those tweets which are geo-
tagged, or will it also return tweets for users whose location (in
profile) falls within the lat, lon specified
the geo-hose will only return tweets that
Hi Raffi,
Will the geo-hose streaming API return only those tweets which are geo-
tagged, or will it also return tweets for users whose location (in
profile) falls within the lat, lon specified.
If it returns only tweets that are geo-tagged, I guess the volume of
returned tweets will be pretty
Will the geo-hose streaming API return only those tweets which are geo-
tagged, or will it also return tweets for users whose location (in
profile) falls within the lat, lon specified
the geo-hose will only return tweets that are geotagged.
while the volume may be low (comparably) now, its
On Dec 15, 9:58 am, John Kalucki j...@twitter.com wrote:
Bandwidth is likely to only be a small fraction of your total cost when
consuming the firehose. If you want to focus on this small part and ignore
all the other dominating costs, the prudent systems engineer would provision
2x to 3x
For one thing, I do a lot of location-based processing. I'm quite
interested in what's happening in Portland, Oregon, and not so much
about the rest of the world. As far as I can tell, there's no geocode
parameter for filter. In addition, I can do a search back in time
with Twitter search -
Excellent! That's exactly what I need! If something gets past the
filter, I can always backsearch for it.
On Dec 17, 9:19 pm, Raffi Krikorian ra...@twitter.com wrote:
For one thing, I do a lot of location-based processing. I'm quite
interested in what's happening in Portland, Oregon, and not
The other levels of Streaming access are not only considerably more cost
effective for all parties, they are also (nearly) sufficient for the vast
majority of applications.
-John Kalucki
http://twitter.com/jkalucki
Services, Twitter Inc.
On Mon, Dec 14, 2009 at 10:16 PM, M. Edward (Ed) Borasky
Just so we all can guestimate if we're equiped for and financially
able to consider consumption of the firehose, in average, what's the
daily data throughput on a firehose stream?
Thanks,
Michael.
On Dec 15, 2009, at 9:38 AM, John Kalucki j...@twitter.com wrote:
The other levels of
Bandwidth is likely to only be a small fraction of your total cost when
consuming the firehose. If you want to focus on this small part and ignore
all the other dominating costs, the prudent systems engineer would provision
2x to 3x daily peak to account for traffic spikes, growth, backlog
Thanks!! At this point, I'm not sure I'll be using the firehose even
if it is available -I don't think I can afford the pipe width to
consume it. ;-)
On Dec 14, 9:59 pm, John Kalucki j...@twitter.com wrote:
There will be further announcements about Streaming API access early next
year.
-John
11 matches
Mail list logo
