You can place parameters in the URL, but there's a practical limit to the number of parameters that you can specify in this manner. At some point the service will reject your request or you'll get tired of looking at your trace logs. If you use a POST parameter instead (placing the track= in the request body), the number of terms is only limited by the administrative limits documented on the wiki.
-John Kalucki http://twitter.com/jkalucki Services, Twitter Inc. On Sep 19, 7:33 am, Greg Avola <[email protected]> wrote: > Do you have any documentation on how to use filter.xml in PHP? The API > doc don't really spell it out. > > Can you just pass a parameter in the URL like filter.xml?track=term? > > On Sep 19, 9:15 am, Joseph Cheek <[email protected]> wrote: > > > I ran into this problem too. I adjusted my search to > > usehttp://stream.twitter.com/1/statuses/filter.xmlinstead- it seems to > > work much better. Search isn't consistent and it isn't real-time. > > > Joseph Cheek > > [email protected],www.cheek.com > > twitter:http://twitter.com/cheekdotcom > > > retsoced wrote: > > > I've been working on a small web app to be able to post to an account > > > using the API, while also displaying those tweets in the same page > > > page where they are being posted from. The problem I am having is that > > > the tweets are being indexed by tthe search, so all of the tools I > > > have found to display a thread of tweets don't work because they don't > > > return any data. > > > > The site I am working on ishttp://twanonymosuly.comwiththe account > > > twitter/twanonymously. > > > > What am I missing? Is there a way to authenticate that page to an > > > account so that the posts will show up in a search? Any ideas/help is > > > greatly appreciated.
