The /shadow resource, (along with /firehose, /birddog, /follow, and all the /*track urls) have been deprecated. The rewrite rules that allow them to function may be removed at any time. All developers should be using only the documented resources. When you connect, you'll get the appropriate level of access. Behind the scenes, you are already using the /1/statuses/filter method...
Your level of access is not determined by IP address or by the URL you connect to. Rather access is determined by roles assigned to usernames. -John Kalucki http://twitter.com/jkalucki Services, Twitter Inc. On Oct 1, 7:36 am, Sameer <sameer.kha...@gmail.com> wrote: > Can you explain what you mean by 'filtered for quality'. Does your > engine believe theses users submit spam? > > Also on another issue, i have access to the shadow stream by using > shadow.json, but I see a new URL and filtered.json in the docs. If I > use filtered.json will the stream engine allow me to follow 50,000 > users based on my ip/username? Or do I have to explicitly use > shadow.json? > > Thanks. > > On Sep 30, 5:22 pm, Sameer <sameer.kha...@gmail.com> wrote: > > > Sorry to clarify I am using the shadow stream with a set of follow > > ID's. > > > On Sep 30, 4:52 pm, JDG <ghil...@gmail.com> wrote: > > > > the streaming API, if i recall correctly, is simply a random sampling of > > > users. it could be that those users are simply not collected in said > > > sample. > > > I may be wrong though. > > > > On Wed, Sep 30, 2009 at 14:21, Sameer <sameer.kha...@gmail.com> wrote: > > > > > Hello, I have been using the stream API for quite some time and I > > > > have come across a select few of my users that don't show in the > > > > stream. There does not seem to be anything unusual with these users > > > > but for some odd reason no stream data comes for their ID's. I get no > > > > data for them through my application or using command line CURL. Here > > > > are some of the users: > > > > > 56623 - thedomesticdiva > > > > 14099695 - ObamaNews > > > > 13553822 - dealtaker > > > > > What causes these users not to be included in the stream? Is this a > > > > bug in the stream API or something that legitimately prevents them > > > > from being included? > > > > > Thanks. > > > > -- > > > Internets. Serious business.
