You should open just one connection from your site and multiplex all your track-compatable keyword search requests over that single connection. The docs describe how to change the predicates based on user demand without data loss or tripping up the connection rate limit.
Users are slowly being trained not to enter their credentials into other websites, and once basic auth is turned off on the Streaming API, this option will be precluded. -John Kalucki http://twitter.com/jkalucki Twitter Inc On Sat, Nov 20, 2010 at 9:57 AM, Jason Newell <newell.jas...@gmail.com>wrote: > The docs recommended I contact Twitter about something like this, so > here goes. > > I'm working on a personal project the goal of which is to provide a > variety of different views of results for user input search terms, > using the Twitter streaming API, specifically filter.json. From what > I've seen it looks like connections are limited to one per user. > > It seems like I've got to force a user visiting my site to either > input their Twitter username and password, or log in to Twitter > through my site and get an OAuth token. The total impact on Twitter's > servers would be the same if I could just make the connections using a > single unchanging piece of authorization information. (well, nearly > the same, some users who would have left might stay instead) I would > like to do this. > > Am I mistaken? Or is it easy to get limited special permissions like > this? If I can't get them now, would I have better luck when I've got > a functional, useful version of the site? > > Thanks. > > -- > Twitter developer documentation and resources: http://dev.twitter.com/doc > API updates via Twitter: http://twitter.com/twitterapi > Issues/Enhancements Tracker: > http://code.google.com/p/twitter-api/issues/list > Change your membership to this group: > http://groups.google.com/group/twitter-development-talk > -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
