Hi all,
many apologies if I'm asking a basic question here but I'm looking at
this new Snowflake ID on the horizon...
My usual logic for processing tweets is something like this:
- find all tweets I'm interested in with status id {stored max
status id}
- process those tweets
- store the highest
This is good enough, as it's very unlikely that a tweet will be delivered
with an id less than your saved maximum id. If you want to be paranoid, you
can subtract a few seconds from the millisecond part of the id, but this is,
in practice, unlikely to ever happen.
-John Kalucki
