I'm not sure if this should be filed as a bug report, but I feel it should be here in case people want to open a new issue / suggest a solution.

Twitter released a new search function yesterday (http://engineering.twitter.com/2011/05/engineering-behind-twitters-new-s...). This basically means that the raw results for a tweet search through Twitter.com will now also be edited for 'relevance' - Twitter says they will "filter out the Tweets that do not resonate with other users". So if no-one is re-tweeting or following you, then a search on Twitter.com will not show any of your tweets.

But, you have just set up a Twitter Pull feed driven by search command that is meant to show a list of all tweets from a particular Twitter account plus all tweets with a particular hashtag, such as 'from:CookieMonster OR #cookies'. Will all of CookieMonster's tweets still be shown? Answer: only if they're relevant. This is because this part of the Twitter Pull module works through the Twitter search API which also applies the relevance filtering.

There is a workaround: make multiple requests to Twitter.com: one of '@CookieMonster' through api.twitter.com (CookieMonster's timeline) and one of '#cookies' through search.twitter.com (the #cookies hashtag). Combine the results and we're done. But the twitter_pull_render function doesn't combine and rank these results for us.