I appreciate your response. That works if your trying to develop your on 
separate client/dusplay e.g. TweetDeck. 

But that doesn't help with updating the list displayed in Twitter. This more of 
a Twitter.com issue than a Twitter API issue. But I posted here anyway in hopes 
development would pickup on it. 

As it stands right now, the Twitter.com lists display is cluttered. We're just 
moving the clutter from timeline to the multiple "lists". And when Twitter API 
developers go to query these lists from Twitter API, the results don't tell you 
much about the tweets in the list. Like you said, we'll have to use hashtags 
and scan the list results. 


From: JDG <ghil...@gmail.com>
To: twitter-development-talk@googlegroups.com
Sent: Thu, October 29, 2009 6:02:28 PM
Subject: [twitter-dev] Re: Twitter Lists Need Optional Hashtag binding  with 
list subscription

pull the whole list and do the filtering in-memory yourself. It's not a perfect 
solution, in terms of bandwidth or processing, but there it is.

On Thu, Oct 29, 2009 at 17:22, Leon Spencer <spencer_l...@yahoo.com> wrote:

I don't think a 3rd party app would work - with Oauth or like a TweetDeck. The 
searches and updates would do well beyond Twitter limits and impact user's 
ability to perform other functions.
>Plus having the hashtags would reduce load on bandwidth anyway, right? Each 
>time you pull this lists that are duplicating tweet results?
>But I'm listening. How would you see a 3rd party app solving this problem when 
>the lists are filters?

Reply via email to