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 http://twitter.com/jkalucki Twitter, Inc. On Thu, Nov 4, 2010 at 2:41 PM, @Joel_Hughes <j...@jojet.com> wrote: > 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 status id of processed tweets for next time round > - (etc) > > ...this way I've got a a kinda sliding window for the processing > tweets - I don't pull in tweets I know I've already processed (e.g. on > my tweko.con app) > > From what I've seen of Snowflake the ids ARE sequential so the above > logic should work? > > thanks for any thoughts guys - I've TRIED to get my head around k- > sorted but, quite frankly, I'm not bright enough :) > > Joel > > -- > Twitter developer documentation and resources: http://dev.twitter.com/doc > API updates via Twitter: http://twitter.com/twitterapi > Issues/Enhancements Tracker: > http://code.google.com/p/twitter-api/issues/list > Change your membership to this group: > http://groups.google.com/group/twitter-development-talk > -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
