[twitter-dev] Re: Percent of total tweets in GardenHose Stream Access

[Don Park]

Based on my recent #s, Gardenhose is streaming ~3% of Firehose at ~22
tweets-per-second.

Re: [twitter-dev] Re: Percent of total tweets in GardenHose Stream Access

[Don Park]

You are right. I got the names mixed up. My numbers are for spritzer. Doh. - 
Don

On Mar 11, 2010, at 1:45 PM, M. Edward (Ed) Borasky wrote:

 That sounds low - I'm seeing about 3.4% of all *status IDs* coming out of 
 sample formerly known as spritzer. I would expect gardenhose to be 
 delivering about 3 times that, or about 10% of all status IDs.
 -- 
 M. Edward (Ed) Borasky
 borasky-research.net/m-edward-ed-borasky/
 
 A mathematician is a device for turning coffee into theorems. ~ Paul Erd?s
 
 
 Quoting Don Park super...@gmail.com:
 
 Based on my recent #s, Gardenhose is streaming ~3% of Firehose at ~22
 tweets-per-second.
 
 

[twitter-dev] Non-finite values in Geo Location bounding_box.coordinates

[Don Park]

Hi,

Some of the tweets are causing my JSON parser (Json-Lib) to throw
JSON does not allow non-finite numbers exception. Looking at the
tweet, only likely suspect is the new Geo Location field
'bounding_box'.

bounding_box: {
type: Polygon,
coordinates: [
[
[
1.79769313486232e+308,
1.79769313486232e+308
],
[
-1.79769313486232e+308,
1.79769313486232e+308
],
[
-1.79769313486232e+308,
-1.79769313486232e+308
],
[
1.79769313486232e+308,
-1.79769313486232e+308
]
]
]
},

JSON verifiers say they are valid so it's kinda confusing.
Nevertheless, I thought Twitter API team should be aware that some of
the JSON parsers are barfing on tweets like above.

Best,

Don Park

[twitter-dev] Re: Non-finite values in Geo Location bounding_box.coordinates

[Don Park]

Boy, that was fast Raffi. Thx! :-)

[twitter-dev] Re: More Streaming API data, please

[Don Park]

+1 to more event types but in its own stream if not in addition to the
firehose. Applications interested only in these events should not have
to drink from the firehose to get those events.

[twitter-dev] Re: friends_timeline and following

[Don Park]

I don't think this is fixed, at least based on responses I am seeing.
If it was fixed then cache/cluster issues are delaying the results I
am expecting. As to the value type, I am seeing following value of 0
instead of true/false.