Take a look on the app I'm workig on, Twitoaster: http://twitoaster.com
The threading part is not that hard. Recursive function jumping from
parents to parents.
You should use the getMentions method, instead of hiting the search
API. You'll get the full object that way, so you won't have to use the
All the best,
On Jul 1, 12:53 am, Scott Haneda <talkli...@newgeo.com> wrote:
> I am finding near all apps I use with twitter in some way or another
> fail at threading a conversation. Anyone have pointers for how to do
> this, based on the current twitter API, and whatever bugs have been
> uncovered, perhaps with workarounds?
> Each tweet has a 'in_reply_to_status_id', if I understand, the
> existence of in_reply_to_status_id, means that the current tweet is a
> child of some parent.
> id = 1234
> in_reply_to_status_id = 5678
> In the above example, tweet #5678 would be the start of the
> conversation, and tweet #1234 would be the reply?
> What has me stumped:http://twitter.com/criticalmassey/status/2383870573
> Clearly a reply to something @ahem said, which started
> However, if I search.twitter.com for @ahem, I can get this
> But it is missing the parent, the start of the thread.
> I can see the master parent
> But threading is not an option.
> Having a hard time wrapping my head around what the limitations of
> threading are. Any suggestions on how to better understand this would
> be most appreciated.
> Ideally, what I am looking for, is to take any tweet, determine what
> other replies there are to it, and get back to the parent, displaying
> all children. I would like to avoid any ambiguous tweet searches that
> are not based on a message-id, and could pollute the results with
> inaccurate threading.
> Scott * If you contact me off list replace talklists@ with scott@ *