I wonder if anyone can help me, I'm getting a little confused as to which API to use. If anyone can offer some guidance I would really appreciate it.
I'm trying to create an website where users can monitor Twitter for certain hashtags. The site will continually search twitter for any new updates and store any tweet related to that particular hashtag continuously. This process will run for up to 60 days. As far as I can gather, my two options are: Using the Search API The problem with this API is that if I have a 1000 users all monitoring different hashtags, I am quickly going to reach my API limit since I will be making a fair few requests, potentially once every 2-3 minutes. Is there a way to use oauth in conjunction with the search API so that the limits are user based and not application based? That way, the limit will be user specific and I won't have to worry. Using the Stream API I thought this might be a better solution, but it seems you are limited to how many connections you can have open. The documentation seems unclear as to how this works... is the connection limit per user or ip? For example, if my site had 1000 users each of those users was monitoring a hashtag, would those 1000 stream api connections be against my servers ip or would they against the user? I'm not sure either of those solutions will work in this instance, what should I do? -- 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
