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 the /follow methods)... > > In the case of the /follow methods (as opposed to the unfiltered > /(fire|garden)hose methods), there is specific intent to get the > updates of a particular user. Even if Twitter considers a user > unworthy of indexing in Search (for whatever reason), I purposefully > want to receive their updates and am stating as much by putting their > userid in the "follow" parameter. In other words, I am opting-in to > get those updates whether Twitter considers them spammy or not. > > If a user account is not in an officially suspended state, I think > they should be fair game for /follow methods. > > Any other opinions out there? > -Chad > > On Fri, Jun 5, 2009 at 1:44 PM, John Kalucki <jkalu...@gmail.com> wrote: > > > 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 that everything is working by the rules, if > > not also by design. These two concepts are not always in alignment! > > > -John Kalucki > > Services, Twitter, Inc. > > > On Jun 5, 10:09 am, Chad Etzel <jazzyc...@gmail.com> wrote: > >> Hi John, et al. > > >> I have been playing with the /follow streams and noticed that some > >> users' updates don't appear at all. This was really confounding for > >> quite a while. Then I noticed that using the search API to search for > >> "from:user" returned no recent results. > > >> An example is @KimSherrell. I have been trying to get her updates in > >> the /follow stream (she posts *a lot*) as a way to verify that it is > >> working. Lo and behold her most recent entry in the Search API is > >> from 5 days ago:http://search.twitter.com/search?q=from:kimsherrell > > >> I know there is some administrative bit on the accounts that > >> determines whether a user will be indexed by Search; is this same bit > >> used to determine whether their updates will go out on the Hosebird > >> streams? If so, may I ask why? > > >> Thanks! > >> -Chad
