Best examples of using Twitter apps?

Question

Imagine an application that is not just another way to publish tweets, but something like an aggregator and you need to store / have access to tweets published through.

Since twitter added a restriction on API calls, the application should / can use some cache, then it should periodically check if the tweet was deleted, etc.

How do you manage limits? Do you think good traffic apps live, not white?

Answer 1

To name a few.

• Aggressive caching. Do not access the API unless you need to.
  • As a rule, I dump as much data as I can, and I store them somewhere. Then I run the local store until it runs out and needs to be updated.
• Avoid doing things in real time. Request queues and do them by timer.
  • If you work on Linux, cronjob is the easiest way to do this.
• Combine queries as much as possible.

Answer 2

You have 100 requests per hour, so the question is how do you balance it between the different types of requests. I think the best option is the TweetDeck method, which allows you to set the percentage and save the rest of% for publication (because this is important too):

Around caching, the database would be nice, and I would ignore the deleted ones - after you downloaded the tweet, it doesn’t matter if it was deleted. If you wanted, you could theoretically just try to open the page using a tweet, and if you get 404, it will be deleted. This means no API costs.