I'm still thinking about how this might be happening and how we might debug
this situation. It isn't trivially reproducible. In the mean time, I've
started some reproduction cases that I'm going to let age for a few hours
and see what happens there.
-John
On Tue, Mar 23, 2010 at 9:16 PM,
John -
We isolated a bug on our side today that was causing some of the
issue. I'm being told (waiting on proof) that there are still some
replies that never come in via the stream. I'll update this post when
I know more.
Thanks,
Brian
On Mar 24, 6:29 am, John Kalucki j...@twitter.com wrote:
Mark -
Two separate threads (one user is restricted track, the other is
shadow).
Track user/thread is running track=briantroy (along with 230 something
other terms). The Follow thread/user is follow=4246611 - which is my
userid (along with 60 something other user id's).
Both threads have
I couldn't trivially reproduce this. But, I'll say that I suspect that there
may indeed be some sort of bug around tracking on screen names and not
always getting all tweets. There might be some combination of text reply vs.
explicit reply vs. protected vs. private vs. something that causes
John -
We rarely get limit messages - and no, none have coincided with
missing replies. Our last limit message was yesterday at: NOTICE:
TRACK - NOTICE: Mon, 22 Mar 2010 22:52:28 -0400 Stream is limited
The track user is justsignal - the follow user is justsignalshad
I'll have to dig through
John -
Here is a good example:
These two tweets came in 2 minutes apart from 2 different 3rd party
clients. We got one and not the other:
http://bit.ly/cG9emM (Got this one)
http://bit.ly/aFvimS (Not this one)
No limit messages, re-connects or anything at all unusual about the
stream activity
