Hi, I'm implementing user streams in my client and looking for some advice on best practices. My client supports viewing multiple timelines at the same time, so it's quite possible to, for example: view a saved search, the user's own home timeline, and another user's recent tweets.
Of course, I'd love to implement these in user streams. My concern is that if each of these timelines were to open a separate stream simultaneously, then the user could easily cross over their limit of active streams. Another potential solution seems to be adding the search and the second user as tracking parameters to a single user stream. That works fine and the track parameter limitations seem to be similar to the limitations of the UI/UX of my app, so it seemed like a good fit. The challenge is that once track parameters are added to the stream I get a whole bunch of new statuses returned but i can't tell which are associated with each parameter. Or, well, I couldn't figure out how to tell short of building a regex for each of my track parameters and trying to sort the items by hand (yuck!). So my question: 1. Is there some way to disambiguate statuses returned as a specific track parameter from those returned for other reasons? 2. Is there some other way to skin this cat that I'm missing? Thanks, Isaiah -- 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
