[twitter-dev] Re: Streaming API: missing updates non-indexed user correlation?

2009-06-06 Thread @Jalada
I'd like to also voice my agreement with Chad here, if you're specifically wanting to follow someone/thing you should get it. I agree with filtering in search, but in this case you are purposefully stating you wish to follow someones updates, and the result should reflect that, regardless of how

[twitter-dev] Re: Streaming API: missing updates non-indexed user correlation?

2009-06-05 Thread John Kalucki
There are multiple bits set for accounts that control various levels of access and all kinds of folderol. It's complicated and for mostly understandable reasons, purposefully opaque. Search and Hosebird currently have identical access rules, but that's subject to change. In this case, it appears

[twitter-dev] Re: Streaming API: missing updates non-indexed user correlation?

2009-06-05 Thread Chad Etzel
Ok, at least that confirms my suspicions about why those updates were not being delivered. If I may make an argument to separate the policy between Search and Hosebird (at least for the /follow methods)... In the case of the /follow methods (as opposed to the unfiltered /(fire|garden)hose

[twitter-dev] Re: Streaming API: missing updates non-indexed user correlation?

2009-06-05 Thread John Kalucki
A very good point. I'll take this up with product. On Jun 5, 10:58 am, Chad Etzel jazzyc...@gmail.com wrote: Ok, at least that confirms my suspicions about why those updates were not being delivered. If I may make an argument to separate the policy between Search and Hosebird (at least for