[twitter-dev] Re: Tweet threading
You don't happen to be using php do you? Any chance you would be able to share this function, even if only in psuedo code form? Maybe I am not understanding a limitation. If I find some other users timeline, and they say: hey, reply to me please", and 100 people do so, there is no way for me to get the replies of those 100 people is there? The only threading that can be done is that of a reply, where you find the parent that started the reply? On Jul 2, 2009, at 6:44 AM, @Jalada wrote: We do the same at Twitterfall - recursive calls from parent to parent until there is no more. Check out http://twitterfall.com (find something that is a proper reply first). An icon appears between the two user names when it thinks there is a conversation. Sometimes it fails because it is doing a check for tweets starting with '@someone' too (because IIRC search results do not return the tweet ID the tweet is replying to) for popular trends, as our backend sends out limited tweet data. -- Scott * If you contact me off list replace talklists@ with scott@ *
[twitter-dev] Re: Tweet threading
What is the getMentions method? I did not see that in the twitter API. I suspect this is a framework you are referring to? Or are you talking about this: http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-statuses-mentions?SearchFor=mentions&sp=1 That seems inaccurate though, would it not be better to start with the in_reply_to_status_id fields? Thanks for any help. On Jul 1, 2009, at 8:35 PM, Arnaud wrote: 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 show/statuses method. -- Scott * If you contact me off list replace talklists@ with scott@ *
[twitter-dev] Re: Tweet threading
We do the same at Twitterfall - recursive calls from parent to parent until there is no more. Check out http://twitterfall.com (find something that is a proper reply first). An icon appears between the two user names when it thinks there is a conversation. Sometimes it fails because it is doing a check for tweets starting with '@someone' too (because IIRC search results do not return the tweet ID the tweet is replying to) for popular trends, as our backend sends out limited tweet data. David Lead Developer Twitterfall.com On Jul 2, 12:11 am, Scott Haneda wrote: > Hope this is not out of line, but this list has been pretty busy > lately in traffic, and I am looking for a little hand holding on tweet > threading... so bump :) > > On Jun 30, 2009, at 3:53 PM, Scott Haneda 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. > > > tweet: > > 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 here: > >http://twitter.com/Ahem/status/2382725245 > > > However, if I search.twitter.com for @ahem, I can get this > > conversation: > >http://dl.getdropbox.com/u/340087/Drops/06.30.09/twitter-b06e01bd-154... > > But it is missing the parent, the start of the thread. > > > I can see the master parent here: > >http://search.twitter.com/search?max_id=2410761989&page=2&q=+from%3Aa... > > 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@ *
[twitter-dev] Re: Tweet threading
Whitelisting helps a lot: http://apiwiki.twitter.com/FAQ#IkeephittingtheratelimitHowdoIgetmorerequestsperhour On Thu, Jul 2, 2009 at 01:11, Coderanger wrote: > > I was wondering how you get over the API limit doing this, I would > imagine you would hit it almost straight away (10 statuses with 10 > replies would do it) as every reply will require a recursive status > request for every parent status? > -- Abraham Williams | Community Evangelist | http://web608.org Hacker | http://abrah.am | http://twitter.com/abraham Project | http://fireeagle.labs.poseurtech.com This email is: [ ] blogable [x] ask first [ ] private.
[twitter-dev] Re: Tweet threading
I was wondering how you get over the API limit doing this, I would imagine you would hit it almost straight away (10 statuses with 10 replies would do it) as every reply will require a recursive status request for every parent status?
[twitter-dev] Re: Tweet threading
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 show/statuses method. All the best, Arnaud. On Jul 1, 12:53 am, Scott Haneda 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. > > tweet: > 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 > here:http://twitter.com/Ahem/status/2382725245 > > However, if I search.twitter.com for @ahem, I can get this > conversation:http://dl.getdropbox.com/u/340087/Drops/06.30.09/twitter-b06e01bd-154... > But it is missing the parent, the start of the thread. > > I can see the master parent > here:http://search.twitter.com/search?max_id=2410761989&page=2&q=+from%3Aa... > 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@ *
[twitter-dev] Re: Tweet threading
Hope this is not out of line, but this list has been pretty busy lately in traffic, and I am looking for a little hand holding on tweet threading... so bump :) On Jun 30, 2009, at 3:53 PM, Scott Haneda 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. tweet: 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 here: http://twitter.com/Ahem/status/2382725245 However, if I search.twitter.com for @ahem, I can get this conversation: http://dl.getdropbox.com/u/340087/Drops/06.30.09/twitter-b06e01bd-154810.png But it is missing the parent, the start of the thread. I can see the master parent here: http://search.twitter.com/search?max_id=2410761989&page=2&q=+from%3Aahem&rpp=10 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@ *
