[twitter-dev] Re: in_reply_to_status_id
I was working with this api method today as well. What I found was that if your update's text does not contain an @reply to the user who created the status you are sending a reply to, Twitter seems to ignore the in_reply_to_status_id. I hope that helps. -Adam On Jan 28, 10:11 am, Rocker shadab.empo...@gmail.com wrote: Hi all, I am trying to achieve the reply functionality of the twitter to a particular tweet(status) using thehttp://api.twitter.com/version/statuses/update.formaturl. In this i am passing in_reply_to_status_id parameter and include_entities=true to replay to a tweet. The status got updated but the response xml doesn't contain any data in the in_reply_to_status_id node. Even though the status got posted, it isn't displayed as a reply. Am i on the wrong track? What could be the possible reason. I am using OAuth for the whole scenario. Thanks Rocker -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] Re: in_reply_to_status_id different from in_reply_to_status_id_str
I am seeing this well w/ JSON. In fact, it's not just the in_reply_to_status_id_str, but also id id_str don't agree! Example tweet: 28480100643110912 Would love to talk to the twitter team to help solve this as it's a doozy for my particular app - Aaron @aaronwhite On Dec 1 2010, 3:36 am, Matt Harris thematthar...@twitter.com wrote: This is unexpected. Can you provide us with some sample Tweet IDs where those fields are different so we can investigate further. Best, @themattharris Developer Advocate, Twitterhttp://twitter.com/themattharris On Wed, Dec 1, 2010 at 12:18 AM, shunjie shin...@gmail.com wrote: Hi guys, I saw that sometimes in_reply_to_status_id is different from in_reply_to_status_id_str in JSON returned. This only happens recently (should be after the 53bit roll out). Do anyone else encounter the issue ? -- Twitter developer documentation and resources:http://dev.twitter.com/doc API updates via Twitter:http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] Re: in_reply_to_status_id different from in_reply_to_status_id_str
Hey Aaaron,
When I call this Tweet the values are correct. Can you paste the entire
Tweet object as you receive it, and confirm your code isn't processing the
integer before displaying it to you.
twurl
/1/statuses/show.json?id=28480100643110912\include_entities=1\trim_user=1
{
coordinates: null,
created_at: Fri Jan 21 15:52:39 + 2011,
favorited: false,
truncated: false,
id_str: 28480100643110912,
in_reply_to_user_id_str: 774675,
entities: {
urls: [
],
hashtags: [
{
text: hilowf,
indices: [
100,
107
]
}
],
user_mentions: [
{
name: Steve Garfield,
id_str: 774675,
id: 774675,
indices: [
0,
14
],
screen_name: stevegarfield
}
]
},
text: @stevegarfield sure. Def answr the questions now but go dir 2 the
community same time - tell show #hilowf,
annotations: null,
contributors: null,
id: 28480100643110912,
retweet_count: 0,
in_reply_to_status_id_str: 28478713205096449,
geo: null,
retweeted: false,
in_reply_to_user_id: 774675,
user: {
id_str: 15010685,
id: 15010685
},
in_reply_to_screen_name: stevegarfield,
source: a href=\http://www.tweetdeck.com\;
rel=\nofollow\TweetDeck/a,
place: null,
in_reply_to_status_id: 28478713205096449
}
Best,
@themattharris
Developer Advocate, Twitter
http://twitter.com/themattharris
On Fri, Jan 21, 2011 at 9:08 AM, Aaron wyrmw...@gmail.com wrote:
I am seeing this well w/ JSON. In fact, it's not just the
in_reply_to_status_id_str, but also id id_str don't agree!
Example tweet: 28480100643110912
Would love to talk to the twitter team to help solve this as it's a
doozy for my particular app
- Aaron
@aaronwhite
On Dec 1 2010, 3:36 am, Matt Harris thematthar...@twitter.com wrote:
This is unexpected. Can you provide us with some sample Tweet IDs where
those fields are different so we can investigate further.
Best,
@themattharris
Developer Advocate, Twitterhttp://twitter.com/themattharris
On Wed, Dec 1, 2010 at 12:18 AM, shunjie shin...@gmail.com wrote:
Hi guys,
I saw that sometimes in_reply_to_status_id is different from
in_reply_to_status_id_str in JSON returned. This only happens recently
(should be after the 53bit roll out).
Do anyone else encounter the issue ?
--
Twitter developer documentation and resources:
http://dev.twitter.com/doc
API updates via Twitter:http://twitter.com/twitterapi
Issues/Enhancements Tracker:
http://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
http://groups.google.com/group/twitter-development-talk
--
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker:
http://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
http://groups.google.com/group/twitter-development-talk
--
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
http://groups.google.com/group/twitter-development-talk
[twitter-dev] Re: in_reply_to_status_id on statuses/update
i have fixed it. please can you make a more complete documentation? all time we must guest about what must we do. $base_string = POST.urlencode(utf8_encode($url)).in_reply_to_status_id %3D14246241747.urlencode(utf8_encode(. $access_token.status=)).myUrlEncode(@aaa ok) and also curl_setopt($curl, CURLOPT_POSTFIELDS, status=.urlencode(@aaa ok).in_reply_to_status_id=14246241747); On Jul 21, 10:55 pm, ntortarolo ntortar...@gmail.com wrote: Hi statuses/update returns Incorrect signature when using in_reply_to_status_id parameter, when the in_reply_to_status_id parameter is omitted the request works fine. Where i must put that param and how? Im doing this call with curl on php. I have added it on my body post and also on my base string, but i cant get it works. Thanks
[twitter-dev] Re: in_reply_to_status_id validation has changed
I have updated the documentation to reflect this change. Thanks for pointing out the error. Thanks, Doug On Sun, Jun 28, 2009 at 9:01 AM, Nick npd...@gmail.com wrote: This is excellent news! (Sorry, I'm a little behind.) However, documentation still asserts that the @mention must be at the beginning of the tweet (maybe someone just needs to update this wiki page: http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-statuses%C2%A0update ) and the Twitter web interface still appears to follow this rule. That is, if I click reply from the web, it starts the tweet with the @mention at the very beginning. And if I move the @mention to somewhere else in the tweet (to avoid the #fixreplies bug and let my other followers see it), in_reply_to is silently dropped. From the web interface, this makes it impossible to send a reply that your followers can both see and follow to the conversation thread. Is the web interface just behind the times? Or are we encouraged not to use this newly-relaxed feature? Thanks, Nick On Apr 30, 6:02 pm, Doug Williams d...@twitter.com wrote: Before today, the value of the in_reply_to_status_id field was validated by two requirements,: 1) It was set to a valid status_id 2) The valid status_id's author from #1 was @replied in the update (@reply here is the old definition where @user was at the beginning of the tweet). If the value of in_reply_to_status_id did not meet these criteria, it was silently dropped. We have relaxed requirement #2 to permit mentions, meaning that the user of the referenced tweet needs to be included somewhere in the update. Enjoy the new data! Thanks, Doug -- Doug Williams Twitter Platform Supporthttp://twitter.com/dougw
[twitter-dev] Re: in_reply_to_status_id validation has changed
This is excellent news! (Sorry, I'm a little behind.) However, documentation still asserts that the @mention must be at the beginning of the tweet (maybe someone just needs to update this wiki page: http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-statuses%C2%A0update) and the Twitter web interface still appears to follow this rule. That is, if I click reply from the web, it starts the tweet with the @mention at the very beginning. And if I move the @mention to somewhere else in the tweet (to avoid the #fixreplies bug and let my other followers see it), in_reply_to is silently dropped. From the web interface, this makes it impossible to send a reply that your followers can both see and follow to the conversation thread. Is the web interface just behind the times? Or are we encouraged not to use this newly-relaxed feature? Thanks, Nick On Apr 30, 6:02 pm, Doug Williams d...@twitter.com wrote: Before today, the value of the in_reply_to_status_id field was validated by two requirements,: 1) It was set to a valid status_id 2) The valid status_id's author from #1 was @replied in the update (@reply here is the old definition where @user was at the beginning of the tweet). If the value of in_reply_to_status_id did not meet these criteria, it was silently dropped. We have relaxed requirement #2 to permit mentions, meaning that the user of the referenced tweet needs to be included somewhere in the update. Enjoy the new data! Thanks, Doug -- Doug Williams Twitter Platform Supporthttp://twitter.com/dougw
[twitter-dev] Re: in_reply_to_status_id validation has changed
The statuses/show method is perfect [1]. 1. http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-statuses%C2%A0show Thanks, Doug Doug Williams | Platform Support | Twitter, Inc. 539 Bryant St. Suite 402, San Francisco, CA 94107 http://twitter.com/dougw On Thu, Apr 30, 2009 at 3:40 PM, P Burrows pburr...@gmail.com wrote: Is there an easy way to get the screen name of an in_reply_to_status_id for purposes of linking to the original tweet? On Thu, Apr 30, 2009 at 6:02 PM, Doug Williams d...@twitter.com wrote: Before today, the value of the in_reply_to_status_id field was validated by two requirements,: 1) It was set to a valid status_id 2) The valid status_id's author from #1 was @replied in the update (@reply here is the old definition where @user was at the beginning of the tweet). If the value of in_reply_to_status_id did not meet these criteria, it was silently dropped. We have relaxed requirement #2 to permit mentions, meaning that the user of the referenced tweet needs to be included somewhere in the update. Enjoy the new data! Thanks, Doug -- Doug Williams Twitter Platform Support http://twitter.com/dougw
[twitter-dev] Re: in_reply_to_status_id validation has changed
Well, sure. But, I was thinking more of building a url ala: http://twitter.com/demosthe/status/1659019581 -- Patrick Burrows http://www.CleverHumans.com On Thu, Apr 30, 2009 at 7:13 PM, Doug Williams d...@twitter.com wrote: The statuses/show method is perfect [1]. 1. http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-statuses%C2%A0show Thanks, Doug Doug Williams | Platform Support | Twitter, Inc. 539 Bryant St. Suite 402, San Francisco, CA 94107 http://twitter.com/dougw On Thu, Apr 30, 2009 at 3:40 PM, P Burrows pburr...@gmail.com wrote: Is there an easy way to get the screen name of an in_reply_to_status_id for purposes of linking to the original tweet? On Thu, Apr 30, 2009 at 6:02 PM, Doug Williams d...@twitter.com wrote: Before today, the value of the in_reply_to_status_id field was validated by two requirements,: 1) It was set to a valid status_id 2) The valid status_id's author from #1 was @replied in the update (@reply here is the old definition where @user was at the beginning of the tweet). If the value of in_reply_to_status_id did not meet these criteria, it was silently dropped. We have relaxed requirement #2 to permit mentions, meaning that the user of the referenced tweet needs to be included somewhere in the update. Enjoy the new data! Thanks, Doug -- Doug Williams Twitter Platform Support http://twitter.com/dougw
[twitter-dev] Re: in_reply_to_status_id validation has changed
I was suggesting using the call to statuses/show to build this URL programmatically, like with this psuedo-code: $status = new Status( http://twitter.com/statuses/show/; + $in_reply_to_status_id+ .xml) $screen_name = $status-get_screen_name(); echo http://twitter.com/; + $screen_name + /status/ + $in_reply_to_status_id; Thanks, Doug -- Doug Williams Twitter Platform Support http://twitter.com/dougw On Thu, Apr 30, 2009 at 4:26 PM, P Burrows pburr...@gmail.com wrote: Well, sure. But, I was thinking more of building a url ala: http://twitter.com/demosthe/status/1659019581 -- Patrick Burrows http://www.CleverHumans.com On Thu, Apr 30, 2009 at 7:13 PM, Doug Williams d...@twitter.com wrote: The statuses/show method is perfect [1]. 1. http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-statuses%C2%A0show Thanks, Doug Doug Williams | Platform Support | Twitter, Inc. 539 Bryant St. Suite 402, San Francisco, CA 94107 http://twitter.com/dougw On Thu, Apr 30, 2009 at 3:40 PM, P Burrows pburr...@gmail.com wrote: Is there an easy way to get the screen name of an in_reply_to_status_id for purposes of linking to the original tweet? On Thu, Apr 30, 2009 at 6:02 PM, Doug Williams d...@twitter.com wrote: Before today, the value of the in_reply_to_status_id field was validated by two requirements,: 1) It was set to a valid status_id 2) The valid status_id's author from #1 was @replied in the update (@reply here is the old definition where @user was at the beginning of the tweet). If the value of in_reply_to_status_id did not meet these criteria, it was silently dropped. We have relaxed requirement #2 to permit mentions, meaning that the user of the referenced tweet needs to be included somewhere in the update. Enjoy the new data! Thanks, Doug -- Doug Williams Twitter Platform Support http://twitter.com/dougw
