[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 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
Re: [twitter-dev] Re: Net::Twitter::Lite cannot authenticate me
Sol, They do come from Twitter, but your program must retrieve the token and extract the access token and secret. If your program doesn't save them to variables or cookies, subsequent requests will fail, for example. You probably haven't probably retrieved them. That said, I am having problems making new Twitter programs work during the last 48 hours for newly registered programs. There may be some kind of problem with the API. I wasn't having any problem day before yesterday. ~Patrick On Fri, Jan 28, 2011 at 3:02 PM, Sol wrote: > Marc, > > Where do the access token and access token secret come from? > I thought they cam from some computation that twitter does with > the consumer key and consumer_secret. If they don't come from > there then what do I do to generate/get them? > > Thanks very much. > > Sol > > On Jan 19, 9:20 am, Marc Mims wrote: >> * Sol [110115 11:02]: >> >> > Hello. I'm trying to tweet programmatically using the >> > Net::Twitter::Lite perl module. I use their example verbatim, with my >> > consumer_key and consumer_secret which I got by registering an app on >> > twitter. >> >> Did you also copy/paste your access token and access token secret? >> Those are also required. >> >> -Marc > > -- > 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: Net::Twitter::Lite cannot authenticate me
Marc, Where do the access token and access token secret come from? I thought they cam from some computation that twitter does with the consumer key and consumer_secret. If they don't come from there then what do I do to generate/get them? Thanks very much. Sol On Jan 19, 9:20 am, Marc Mims wrote: > * Sol [110115 11:02]: > > > Hello. I'm trying to tweet programmatically using the > > Net::Twitter::Lite perl module. I use their example verbatim, with my > > consumer_key and consumer_secret which I got by registering an app on > > twitter. > > Did you also copy/paste your access token and access token secret? > Those are also required. > > -Marc -- 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] Some Russian letters become garbage!
This should work fine -- how are you %-encoding the UTF-8 characters in your POST body? For example, in your POST body it should look something like: > status=%d0%bf%d1%80%d0%be%d0%b2%d0%b5%d1%80%d0%ba%d0%b0 And in your signature base string: > POST&https%3A%2F%2Fapi.twitter.com > %2F1%2Fstatuses%2Fupdate.json&oauth_consumer_key%3Dri8JxYK2ddwSV5xIUfNNvQ%26oauth_nonce%3DZwmxIz73x3qI8bvNA9LF71IzfAXF0ZdGNw37iyo1B2g%26oauth_signature_method%3DHMAC-SHA1%26oauth_timestamp%3D1296248907%26oauth_token%3D119476949-gF0B5O1Wwa2UqqIwopAhQtQVTzmfSIOSiHQS7Vf8%26oauth_version%3D1.0%26status%3D%25D0%25BF%25D1%2580%25D0%25BE%25D0%25B2%25D0%25B5%25D1%2580%25D0%25BA%25D0%25B0 Which results in this (segment of) JSON response: > "text":"\u043f\u0440\u043e\u0432\u0435\u0440\u043a\u0430" Which looks like this when rendered: http://twitter.com/#!/oauth_dancer/status/31096289030578176 проверка Taylor On Fri, Jan 28, 2011 at 12:18 PM, zendocon wrote: > Most Russian letters are correct in my tweets, but for certain letters > I get garbage... > > If I tweet this through my Twitter application: "испытания" > I get this: "испÑ39Ñ1Aания" > > And if I tweet this: "проверка" > I get this: "пÑACовеÑACка" > Which is sent as UTF8: d0 bf d1 80 d0 be d0 b2 d0 b5 d1 80 d0 ba d0 b0 > > Where's the error? I have verified the UTF8 string with multiple > converters. It is indeed correct! > > Please help! > > -- > 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] Some Russian letters become garbage!
Most Russian letters are correct in my tweets, but for certain letters I get garbage... If I tweet this through my Twitter application: "испытания" I get this: "испÑ39Ñ1Aания" And if I tweet this: "проверка" I get this: "пÑACовеÑACка" Which is sent as UTF8: d0 bf d1 80 d0 be d0 b2 d0 b5 d1 80 d0 ba d0 b0 Where's the error? I have verified the UTF8 string with multiple converters. It is indeed correct! Please help! -- 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] Updating status with a picture
Hi, currently i am able to update my status through my twitter app. when updating with a link to an image i must click the link in twitter to view the image. what i wanted was to have the image popup in the right sidebar just like pictures from twitpic come up. just wondering if a domain must be whitelisted so that when updating your status with an image it becomes viewable in the sidebar, or if there is a special api call for pictures. thanks, Nelson -- 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] SSL support for search API
Great - Thanks Matt! -- 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] Tweet button fails to parse URL - query strings beginning with & rather than ?
On Fri, Jan 28, 2011 at 3:02 AM, JonM wrote: > The following URLs won't parse using the "tweet" button: > > "'url' parameter does not contain a valid URL." > > > http://www.pitchero.com/clubs/stockport/j/team-news-1249.html&news_id=247910 Well, that's not a valid URL. See the RFC. http://www.ietf.org/rfc/rfc1738.txt If you need a "&" right there, you'll have to encode it. > I expect this is because the string has an ampersand "&" rather than a > question mark "?" before the first GET variable. Yes. > Facebooks "share" and "like" functions both accept this formatting, as > do Google and Yahoo. My guess is that they are encoding the URL for you, and Twitter does not at this time. > Is there a reason Twitter's API does not? Is there any work around I > can use? Mainly security. We've seen people abusing the tweetbutton URLs in cross-site-scripting attempts and other forms of abuse. -j > Thanks > > -- > 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] SSL support for search API
Hey, SSL is supported by Search. You can find the other API URLs and whether they support SSL or not in this thread: http://groups.google.com/group/twitter-development-talk/browse_thread/thread/46ca6fcb9ea7eb49/f0f818daee475666 Best, @themattharris Developer Advocate, Twitter http://twitter.com/themattharris On Fri, Jan 28, 2011 at 7:45 AM, fredp wrote: > Most of the posts I've read here indicate that the search API isn't > available over SSL (apologies if I misread anything), but currently it > seems like it is available to hit. Does anyone know if the search API > over SSL is supported for general use? > > Example: https://search.twitter.com/search.json?q=ipad > > -- > 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] SSL support for search API
Most of the posts I've read here indicate that the search API isn't available over SSL (apologies if I misread anything), but currently it seems like it is available to hit. Does anyone know if the search API over SSL is supported for general use? Example: https://search.twitter.com/search.json?q=ipad -- 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] in_reply_to_status_id
Hi all, I am trying to achieve the reply functionality of the twitter to a particular tweet(status) using the http://api.twitter.com/version/statuses/update.format url. 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] Tweet button fails to parse URL - query strings beginning with & rather than ?
The following URLs won't parse using the "tweet" button: "'url' parameter does not contain a valid URL." http://www.pitchero.com/clubs/stockport/j/team-news-1249.html&news_id=247910 I expect this is because the string has an ampersand "&" rather than a question mark "?" before the first GET variable. Facebooks "share" and "like" functions both accept this formatting, as do Google and Yahoo. Is there a reason Twitter's API does not? Is there any work around I can use? Thanks -- 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
