Twitter strategy: Streaming API vs. REST API -

Twitter strategy: Streaming API vs. REST API -

i'm working on kind of twitter wall. users can login twitter , create own wall, display tweets terms/hashtags.

i'm still looking best strategy info out of twitter apis. next of thoughts:

strategy 1: streaming api

open single stream (post statuses/filter) walls each hashtag added track parameter when new tweets arrive, processed , sent corresponding wall ("one account, 1 application, 1 open connection" cf. https://dev.twitter.com/discussions/14935)

problems streaming api

streaming api limited 400 keywords track what if there more 400 keywords track? streaming api limited 1% of tweets of firehose it's hard above 1% of firehose, if you're tracking term "apple" it'd pretty easy exceed 1%. (cf. https://dev.twitter.com/discussions/6349) how can handle such popular terms? blacklist them?

strategy 2: rest search api

store user access tokens poll search api (get search/tweets) on behalf of user, respecting rate limits of 180 queries per 15 minute (cf. https://dev.twitter.com/discussions/11141)

problems rest search api

polling could expensive poll api lot of users.

do have suggestions/recommendations strategy fit best? there solutions these problems?

best regards

twitter streaming