Hi Ryan,
You can certainly use search that way with no problems. The
replies API call would usually be faster than search since that is
it's only function. I'm working with someone to find the cause of the
missing replies. If you need something sooner search is probably your
best choice.
Thanks;
— Matt
On Jan 13, 2009, at 11:34 AM, Ryan Fogle wrote:
Matt, thanks for pointing out the search API. I hadn't looked at that,
after seeing the ability to pull replies from the normal API. Search
looks like a better fit because of the larger count per page.
We are not a search engine. We are using replies to our user as input
for our application. We intend to poll for new replies to our user
once a minute, using a large count per page, and since_id to limit
results. If the page is full, we will fetch the next page until we are
out of replies to pull. Is this acceptable usage?
Thanks,
Ryan
On Jan 13, 12:14 pm, Matt Sanford <[email protected]> wrote:
Hi Ryan,
I can see the statuses in question in search [1] but not in the
replies timeline. There definitely seems to be some issue with
pagination not working correctly. I'll take a look but please open a
ticket athttp://code.google.com/p/twitter-api/issuesso I don't
forget about this and so I can keep you updated.
Thanks;
— Matt Sanford
[1] -http://search.twitter.com/search?q=to%3Auladoo+from%3Aryanfogle
On Jan 13, 2009, at 08:50 AM, Ryan Fogle wrote:
Sorry about the double post.
I saw replies on my account. I then sent 21 more replies. I went
back
to the replies page, and all the previous ones had been bumped off
by
the new replies, but I could not go to page 2.
The account in question is uladoo.
On Jan 13, 11:15 am, Matt Sanford <[email protected]> wrote:
Hi Ryan,
This is the same message as your previous one with the subject
"Reply Pagination Issue", please don't double post to the list.
Time
spent handling duplicates is time I could spend fixing bugs,
working
on OAuth or answering questions. Be Kind, Rewind.
Now, on to your question. Since the API and Web UI match I'm
guessing that one of your reply posts was rejected for some reason.
The most likely cause of that is a duplicate. If you post the same
status text twice in a row the second one will be ignored. If
that's
not the cause perhaps there was some sort of error when you were
replying between accounts. If you can provide the account in
question
I'll be happy to take a look.
Thanks;
— Matt Sanford / @mzsanford
On Jan 12, 2009, at 12:55 PM, Ryan Fogle wrote:
I am running into an issue in my application where I cannot fetch
the
second page of replies to my account.
I had one account send 21 replies to another account. The second
account can only see the first page of 20 replies. The extra one
vanishes. This is true both in the API (which returns an empty
list
for page 2) and in the web interface (which disables the next page
button).
Is there a workaround for this? I am intending on using the
since_id
parameter, but in the rare case that I get more than 20 replies
between checks, I will lose some.
