Ditto here. Note to self, never trust since_id in the Twitter API. This has burned me before. It really burned me this time.
-- Barry http://iridesco.com http://bjhess.com On Mar 30, 2:06 pm, Doug Williams <d...@twitter.com> wrote: > Ben, > I can see the same problem. There is now an open issue for this problem [1]. > > 1.http://code.google.com/p/twitter-api/issues/detail?id=399 > > Thanks, > Doug Williams > Twitter API Supporthttp://twitter.com/dougw > > On Mon, Mar 30, 2009 at 11:56 AM, Ben Burleson <ben.burle...@gmail.com>wrote: > > > > > > > I use this URL: > >http://twitter.com/direct_messages.xml?since_id=82528092 > > > The result includes the message with that ID (when it should only > > include > > messages AFTER that ID) AND previous messages. This is very broken. > > > Should I abandon it and just use the since parameter (as date)? > > > If so, fix the API doc!!!!!!!11111 > > > Cheers, > > Ben
