If it reaches a protected status, it obviously cannot proceed fetching
more of the conversation. You may want to provide some sort of
indicator of that if your UI allows it.
And no, the search api sadly doesn't contain the in_reply_to_status_id
field. My UI only shows the "Show Conversation" menu item if that
field is available, so it's just not an option when showing search
results. I really hope they add it to the search API soon -- it would
allow me to do a search for anything @SomeoneWhoAskedAQuestion and
pick out other people's answers, which would be very useful.
On Dec 24, 12:19 am, "Shahid Faiz" <
shahid.f...@gmail.com> wrote:
> Nice approach to get conversations. What you do if that status is from
> protected profile and that person is not friend? What about results returned
> from search, I think these results don't have in_reply_to_status_id?
>
> Thanks,
> Shahid
>
> On Wed, Dec 24, 2008 at 9:46 AM, JakeS <
jakesteven...@gmail.com> wrote:
>
> > My application currently does it by looking at the
> > in_reply_to_status_id on the current status, then calling
> >
http://twitter.com//statuses/show/WHATEVERTHATIDWAS.xmlto get that