[twitter-dev] Re: Odd behavior with the search API when using since_id
Same issue here. Mobile app does local caching and was counting on the since_id not being included in the result set. Unfortunately, I haven't been capturing request and response logs. On Sep 23, 9:40 am, James Teters wrote: > Hello, > > This has just appeared in the last few days. When I perform a search > with the search API I keep track of the newest status id so I can pass > that back when doing the next query (as since_id) so that only tweets > with a status id greater than since_id are returned. Oddly, beginning > yesterday the search API started returning the status specified in > since_id but only when I specify a from: parameter to limit the search > to a specific user. It's like it is returning statuses >= since_id > instead of > since_id when I add the from: parameter. > > Anyone else seen odd behavior when using from:?
[twitter-dev] Re: error messages
I would second the request. Not necessarily for every possible error message, but at least for the structure of error messages. Currently, the documentation shows one example of an XML error response and seems a bit non-committal that this is the canonical structure of an error response (using the language "an error from an XML method might look like this"). I'm particularly interested in JSON responses. There are no examples. Thanks, -Mark On Jun 6, 3:59 pm, developerinlondon wrote: > is there a list of all possible error messages that twitter sends > currently I can see? > I foundhttp://apiwiki.twitter.com/HTTP-Response-Codes-and-Errors > but this only lists the http response codes, not the actual error > message twitter puts in the body of the message. > > would be good to know the messages so that it can be programmed into > the applications. > > thanks, > > nayeem
[twitter-dev] Re: WWDC Twitter developer meetup at Twitter HQ: RSVP!
I'm in. -Mark On May 21, 2:18 pm, Alex Payne wrote: > Hi all, > > There's great crossover between Twitter API developers and Mac/iPhone > developers. Andrew Stone, developer of Twittelator Pro, suggested that > we all get together during WWDC and coordinate around the Apple Push > Notification Service and other issues of mutual interest. Twitter's > offices are just a few blocks from Moscone, so it should be easy for > any interested coders to make it over here. > > Please RSVP with a reply to this thread and let us know what dates and > times work for you. Andrew was thinking early one morning, but not > being much of a morning person, I'd prefer something later in the day. > We'll let group consensus decide. > > Thanks, and hope to see you in early June. > > -- > Alex Payne - API Lead, Twitter, Inc.http://twitter.com/al3x
