From what I understand, he is using the 'statuses/filter' call of the stream api, filtering with users that have installed his app. This allows him to get the t

From what I understand, he is using the 'statuses/filter' call of the stream api, filtering with users that have installed his app. This allows him to get the tweets of all his users in a single connection to twitter. 'statuses/filter' and 'statuses/sample' are the only two methods provided to all accounts and they are very limited. I mean, 100K users is a big number for sure, but not a surprising number given it's a twitter app on facebook. We are far from the firehose level! As a work around, he might be able to go back to the REST api, use statuses/friends_timeline, and stay within the 300 per hour/per user limit. Good luck Michael.