I don't want it "live". In fact, my application scenario explicitly does not want it live.
What I have is a Windows service that periodically polls Twitter for messages about particular topics of interest (like specific hashtags). Now after a tweet has been posted, its statistics may get updated. The only stats I am interested in is the number of
Retweets and number of "favorite" flags for that tweet.
While I can do a GET statuses/show/:id. However, as per this page (
), I get back the whole original tweet object. This is perfectly okay, but I imagine over a period of time, I would need to file this GET request for each tweet I have (filtering for a reasonable
time window, leaving out quite older ones and ones that are fairly the latest). This would quickly use up all of my rate limits :-(
An alternate I can think of is to re-fire my original request, get all of the objects all over again and then look through them for new tweets and updates to old tweets and update my data containers appropriately :-(
Anything you know in your Tweetinvi code base that can significantly reduce all those rate limit usages and multiple calls would be greatly helpful :-) :-)