". 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." ~ P
Based on my recent #s, Gardenhose is streaming ~3% of Firehose at ~22
tweets-per-second.
+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.
Boy, that was fast Raffi. Thx! :-)
3486232e+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
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.
