Thanks for the link Abraham, I had look at them, most of the time their API <from my experience> timed out and never responded (e.x. http://api.twitoaster.com/conversation/show.json?id=7968304579).
Plus from looking at the eery similarities (rate limits, user agent requirement, returned JSON structs, etc) it looks like a wrapper around the twitter API (even if I am off base on that assumption they [twitoaster] must be pulling some of their data from the API.... [Unless they are riding the firehose and storing a arseload of data]) That being said, I really don't want to code to two API's for my application and if they [twitoaster] can get/thread the replies then dang-it my inner nerd says "So can I" :) Thanks, Rob On Wed, Jan 20, 2010 at 6:46 PM, Abraham Williams <4bra...@gmail.com> wrote: > You might also check out http://twitoaster.com/api/conversation-show/ > > I don't know how large their database is though. > > Abraham > > > On Wed, Jan 20, 2010 at 07:37, Orian Marx (@orian) <or...@orianmarx.com>wrote: > >> You should add your thoughts to >> http://code.google.com/p/twitter-api/issues/detail?id=142 >> >> This would be a hugely beneficial addition to the API but of course >> it's being completely ignored. >> >> On Jan 20, 4:41 am, rob <robert.bag...@gmail.com> wrote: >> > Hello, >> > >> > Questions regarding how to get replies to a tweet >> > >> > What is the recommended way to do this properly? >> > >> > A few things I have tried >> > >> > {I am aware that there is no current way to use the search API and >> > grab all responses to a tweet (i.e by reply_to_status_id) [bummer].} >> > >> > 1. The search API using a "to:someUser&since_id= >> > [theIdOfTweetIAmWatching]": this does not work since I have no >> > reply_to_status_id in the results to match up with. >> > >> > 2. API --> home_timeline: Requires the credentials for the user who >> > created the tweet [Which I may or may not have] >> > >> > 3. API --> user_timeline with the user_id from the tweet I am >> > watching: this does not include the tweets to the user >> > >> > 4. Cheat and have twitter to the work.... >> http://search.twitter.com/search/thread/[theIdOfTweetIAmWatching]<http://search.twitter.com/search/thread/%5BtheIdOfTweetIAmWatching%5D>: >> > does not seem to support JSON or anything other than HTML or ATOM >> > >> > 5. Searched the list :) >> > >> > I am just trying to get a handle on how to take a tweet that I get in >> > via a stream and go look [poll] for replies. >> > >> > It seems I would need to follow the user using the streaming API and >> > match based on the in_reply_to_status_id but that would get quite out >> > of hand due to incoming tweet volume [i.e would need to follow a large >> > amount of users that may or may not ever produce a valid reply]. >> > >> > Thanks in advance, >> > >> > Rob >> > > > > -- > Abraham Williams | Moved to Seattle | May cause email delays > Project | Intersect | http://intersect.labs.poseurtech.com > Hacker | http://abrah.am | http://twitter.com/abraham > This email is: [ ] shareable [x] ask first [ ] private. > Sent from Seattle, WA, United States >
