For example - make a script which tracks a specific #hashtag you are required to include to be in the chain, then each time it is mentioned harvest the "in reply to" from that tag and keep it in a database which can then be used to access that tweet later...
A rather roundabout way but will work i guess. On Aug 6, 8:48 am, gloopymoop <nerdf...@gmail.com> wrote: > Thankyou for your reply. I'm a little unsure as to how the streaming > API method would work.. can you give me an example ? I would still > have to create a local database of the chain, right? > > On Aug 6, 3:58 am, David <dtran...@gmail.com> wrote: > > > > > Hey gloopymoop, > > > Like the original thread said, you can use the search API to search > > for tweets to that particular user and check the in_reply_to_status_id > > field. If you want to track the chain (ie all the replies to > > @dtran320's reply to @gloopymoop's original tweet), then you have to > > periodically search each user in the chain. > > > A more efficient way of achieving this would be to use the Track or > > Follow streaming API methods and add one users as they join the reply > > chain:http://dev.twitter.com/pages/streaming_api_methods#follow > > > On Aug 3, 6:49 pm, gloopymoop <nerdf...@gmail.com> wrote:> I believe this > > has been discussed before here, so forgive me if this > > > is redundant. > > > >http://groups.google.com/group/twitter-development-talk/browse_thread... > > > > I would like to build a chain of replies originating from a single > > > tweet. > > > > The user will look at the first tweet, then be presented with the > > > replies to this tweet and be able to move along the chain from the > > > head down the branches. > > > > What would be the best way of implementing this? Requiring users to > > > include a hashtag then periodically searching and keeping a local > > > database of which tweets are in_reply_to which?
