|
1,110
results for
since_id.
|
Gather replies with since_id
TIA, ~Barry Hess On Thu, Apr 17, 2008 at 2:01 AM, Alex Payne <a...@twitter.com> wrote: It's my plan to support since_id for replies and all methods on which it's appropriate and not currently supported. Thanks for the suggestion! On Wed, Apr 16, 2008 at 9:45 PM, Barry Hess <ba...@bjhess.com> wrote: Hi, ...
Apr 25 2008 by Barry Hess
- 6 messages - 3 authors
|
since_id basic usage confusion
matt sanford m...@twitter.com twitter-development-talk hi there, just as a general software comment if you're sending since_id it's probably a good idea to also double check your results. that said: since_id should work like you expect. one case where it does not work is if you follow the next_page url for ...
May 7 by Matt Sanford
- 5 messages - 4 authors
|
404 with Twitter Search API and since_id
jan gnue...@gmail.com twitter-development-talk Hi folks, could someone help me by telling me why http://search.twitter.com/search.json?q=from% 3Amitchfanning&since_id=1066081654 yields a 404 while http://search.twitter.com/ search.json?q=from%3Alayzdaisy&since_id=1097277226 works like a charm? ...
Jan 6 by jan
- 3 messages - 2 authors
|
survey: usage of since/if-modified-since vs since_id
alex payne a...@twitter.com twitter-development-talk we've recently discovered some performance problems in the use of the since/if-modified-since parameter and http header, respectively. what was originally implemented as a way for developers to help us keep our servers happy by requesting only the tweets they ...
Mar 6 by Alex Payne
- 1 message - 1 author
|
search api not working with 'refresh' and since_id does not return ...
burton burtona...@gmail.com twitter-development-talk running this request: http: //search.twitter.com/search.atom?q=linux and then fetching the 'refresh' link doesn't work. http://search.twitter.com/search.atom?q=linux&since_id=2011153563 is this broken? the documentation seems to hint that i can use this to fetch ...
Jun 2 by burton
- 1 message - 1 author
|
since_id returning older messages
gmail.com> wrote: i am trying to retrieve direct messages using the since_id to fetch only the new ones. the documentations says "returns only direct messages with an id greater than (that is, more recent than) the specified id." however, the api is giving me messages with an id lower than the since_id that i pass. ...
Apr 6 by Beier
- 3 messages - 3 authors
|
since_id for direct_messages not in the spec
Fred Brunel fbru...@gmail.com twitter-development-talk Hi, I've learned from previous posts that the direct_message API support a since_id parameters. I've tested it and it works but it is not described in the spec as it is for the public_timeline API. Is it deprecated or unsupported (I'm currently using it) ?
Jul 10 2007 by Fred Brunel
- 4 messages - 3 authors
|
from and since_id 404 issues
hayes davis ha...@appozite.com twitter-development-talk sounds related to my earlier post[1] about issues using from and since (as opposed to since_id). hayes http://groups.google.com/group/twitter-development-talk/browse_thread/ thread/2960bcdf84fef6d6 on mon, jun 29, 2009 at 8:36 pm, ...
Jun 29 by Hayes Davis
- 2 messages - 2 authors
|
search api ignoring since_id?
gmail.com> wrote: same thing here, since_id is totally ignored and i'm getting duplicated results on jul 14, 12:50 pm, chad etzel <jazzyc...@gmail.com> wrote: i'm noticing something strange in my search logs at the moment... i'm getting back a full set of results (number of results = rpp) when using since_id when i ...
Jul 14 by TweetByMail
- 5 messages - 3 authors
|
search api error {"error":"since_id too recent ...
chad etzel jazzyc...@gmail.com twitter-development-talk that usually happens when the search servers get out of sync and the since_id tweet hasn't been indexed on the other server(s) yet, so it thinks it's a tweet from the future. - chad on tue, jul 21, 2009 at 12:38 pm, matthew<jesc...@gmail.com> wrote: i am ...
Jul 21 by Chad Etzel
- 5 messages - 3 authors
|
|
|