Hey Ginny,
Thanks for letting us know it was the ruby gem at fault - and for correcting it.
Best
Matt
On Sun, Sep 26, 2010 at 12:17 PM, Ginny Hendry ginnyhen...@gmail.com wrote:
FYI, we found the bug! Twitter API was fine, but yajl-ruby gem has an
error that causes it to skip tweets of some
For anyone else who is having this problem, the fix has been
identified but has not yet been published as a new gem version. What
happens is that it skips some tweets. The ones it skips are the ones
that happen to have a message length in hex that includes a zero
character so it will seem
Thanks for following up with this Ginny. Brian has just pushed version
0.7.8 of the gem, which fixes this.
Tim.
On Tue, Sep 28, 2010 at 5:16 AM, Ginny Hendry ginnyhen...@gmail.com wrote:
For anyone else who is having this problem, the fix has been
identified but has not yet been published
FYI, we found the bug! Twitter API was fine, but yajl-ruby gem has an
error that causes it to skip tweets of some lengths, which accounts
for the weird way it let some through and not others.
We're heading off to correct the Ruby gem now.
-Ginny
--
Twitter developer documentation and
John-
Thanks for confirming the way this should work. We'll work on the
client side code to see what it's doing with the stream data and how
it compares to the raw stream from curl.
-Ginny
On Sep 24, 12:01 pm, John Kalucki j...@twitter.com wrote:
Accounts should work all of the time,
