Thanks John,
that's the fall back tactic I was considering!
Thanks for your help
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
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