Hi Linvi. That is neat. Thank you so much for your time.
One other possible problem is that if the search filter does not generate frequent tweets, it is not possible to restore the missed ones until a new one arrives. Is there a way to get the latest Tweet ID anywhere on twitter so that collection can start as soon as the program is restarted in order that we dont have to wait around for a filterstream match ?
The advantage of the way you have done it of course is that new event tweets dont have to care about whether those events have been collected by the catch up code.
I guess the server could always post or DM itself?
Thanks
One other possible problem is that if the search filter does not generate frequent tweets, it is not possible to restore the missed ones until a new one arrives. Is there a way to get the latest Tweet ID anywhere on twitter so that collection can start as soon as the program is restarted in order that we dont have to wait around for a filterstream match ?
The advantage of the way you have done it of course is that new event tweets dont have to care about whether those events have been collected by the catch up code.
I guess the server could always post or DM itself?
Thanks