I read somewhere on the API documentation that caching tweets is recommended(I’d do it anyways). I am currently in the following situation:
(1) The user is at this home timeline
(2) There are currently only the newest 20 tweets displayed
(3) He scrolls down, when he reaches the end of the timeline, new tweets are fetched from the Twitter server
At (3) I’d like to know whether I actually have to download anything at all - since I’m caching tweets anyway, they could already be on the hard disk so I’d just have to load them from there and display them.
Since I have 64bit integers I’m already using the most “efficient” version from , but I’d like to give the user a seamless expierence by just displaying already cached data.
Is that possible? If yes, how? If not, is anything in that direction planned?(E.g. a “next_status_id”/“prev_status_id” parameter for home_timeline that would give developers the possibility to check wheter the next/previous tweets is cached by their application).
I hope my qustion was clear enough, thanks in advance.