[twitter-dev] Re: oauth status update returning error 401 invalid / used nonce
Thanks for the response. I am using the consumer key and secret found here: http://dev.twitter.com/apps/ And the access token and secret found here: http://dev.twitter.com/apps//my_token No joy. On Jun 30, 9:47 pm, "Andrew W. Donoho" wrote: > On Jun 30, 2010, at 14:32 , James Ford wrote: > > > One thing I'm perhaps not clear on, do I need xAuth for this to work? > > You do need to get the access token somehow. That is what xAuth provides you. > That said, you sound like you are a server app. Twitter doesn't support xAuth > for server apps. You probably need to use the standardOAuthtoken request > protocol. > > Anon, > Andrew > > Andrew W. Donoho > Donoho Design Group, L.L.C. > a...@ddg.com, +1 (512) 750-7596 > > "To take no detours from the high road of reason and social responsibility." > -- Marcus Aurelius
[twitter-dev] Re: Help! Failed to validate oauth signature and token
Thanks for your quick answer. I have check the time stamp again and got it solved. I should not use the local time. After I change it to universal time, it works. To my surprise, there is no time zone specification in the http://dev.twitter.com/auth#signing-requests . I suggest someone should add the time zone info to the document. On Jun 30, 9:56 pm, Taylor Singletary wrote: > Hi Slavik, > > Happy to help. Are you able to share the signature base string that goes > with this request? Do you know if the server/system you're executing this > from has a clock in sync with Twitter's? (We offer the current date / time > in the HTTP response to failed and successful requests). I take it your > Authorization header doesn't actually contain the line break seen there? > > Thanks, > Taylor > > > > On Wed, Jun 30, 2010 at 3:01 AM, slavik wrote: > > I am writting a client on Symbian. > > > There is no lib for the platform, so I write one. However, I have not > > been successful yet. > > > When I post tohttp://api.twitter.com/oauth/request_token, I always > > get "Failed to validate oauth signature and token". > > > I have check the time and the signature value according to the > > >https://hueniverse.com/2008/10/beginners-guide-to-oauth-part-iv-signi... > > They are all right. But it just don't work. > > > Could anybody help me? > > > The following is what I posted > > > POST /oauth/request_token HTTP/1.1 > > Host: api.twitter.com > > Authorization: OAuth > > > oauth_nonce="QP70eNmVz8jvdPevU3oJD2AfF7R7odC2XJcn4XlZJqk",oauth_signature_m > > ethod="HMAC- > > > SHA1",oauth_timestamp="1277790519",oauth_consumer_key="5E1f**QB > > g",oauth_version="1.0",oauth_signature="neYefd > > %2FM2fNwj%2BVyDW1P7v0M2xk%3D" > > Content-Length: 0 > > > HTTP/1.1 401 Unauthorized > > Date: Wed, 30 Jun 2010 09:49:29 GMT > > Server: hi > > Status: 401 Unauthorized > > X-Transaction: 1277891369-55674-5200 > > Last-Modified: Wed, 30 Jun 2010 09:49:29 GMT > > X-Runtime: 0.00588 > > Content-Type: text/html; charset=utf-8 > > Content-Length: 44 > > Pragma: no-cache > > X-Revision: DEV > > Expires: Tue, 31 Mar 1981 05:00:00 GMT > > Cache-Control: no-cache, no-store, must-revalidate, pre-check=0, post- > > check=0 > > Set-Cookie: k=72.13.82.125.1277891369172474; path=/; expires=Wed, 07- > > Jul-10 09:49:29 GMT; domain=.twitter.com > > Set-Cookie: guest_id=127789136917890129; path=/; expires=Fri, 30 Jul > > 2010 09:49:29 GMT > > Set-Cookie: > > _twitter_sess=BAh7CToRdHJhbnNfcHJvbXB0MDoPY3JlYXRlZF9hdGwrCNvYQogpAToHaWQi > > %250AJTlkZWMwNzNmY2NlYjE4Y2U1MWE5ZTgyMTJlYWM5M2UyIgpmbGFzaElDOidB > > > %250AY3Rpb25Db250cm9sbGVyOjpGbGFzaDo6Rmxhc2hIYXNoewAGOgpAdXNlZHsA--0233aacf > > da88d179166546d965bad353ad8dda38; > > domain=.twitter.com; path=/ > > Vary: Accept-Encoding > > Connection: close > > > Failed to validate oauth signature and token
Re: [twitter-dev] oAuth and callback function
check the config.php file if you defined the callback url there. On Wed, Jun 30, 2010 at 6:23 PM, EastSideDev wrote: > I changed the url for my callback function, and updated that > information in my application settings on the twitter API site. The > problem I am running into, is that I am still getting the old callback > URL. Is there a lag time, before changes take effect?
[twitter-dev] Re: Authentication for retweeted_by_me
Matt, It doesn't seem to make a difference. I also checked it against the base string and headers for the user_timeline query that is working ok, and the order of the elements is the same in both queries. Thanks, Carl On Jun 30, 4:42 pm, Matt Harris wrote: > Hi Carl, > > My immediate response is that the order of arguments in your basestring are > different to the order in your authorization header. This would cause the > signatures to be different as you signed them in one order but delivered in > another. > > See if keeping them in the same order fixes it. > > Matt > > > > On Wed, Jun 30, 2010 at 2:29 PM, cthress wrote: > > Matt, > > > Here's the base string: > > GET&http%3A%2F%2Fapi.twitter.com%2F1%2Fstatuses > > %2Fretweeted_by_me.json&oauth_consumer_key%3D > > %26oauth_signature_method%3DHMAC-SHA1%26oauth_timestamp > > %3D1277932576%26oauth_token%3D%26oauth_version%3D1.0 > > > And here are the headers: > > Authorization: OAuth realm="http%3A%2F%2Fapi.twitter.com > > > %2F",oauth_version="1.0",oauth_nonce="e32167a3bfc33f59e1d18e3907df5ee6",oauth_timestamp="1277932576",oauth_consumer_key="*",oauth_token="*",oauth_signature_method="HMAC- > > SHA1",oauth_signature="ZQZvWpefFlWr1ro%2FxMF%2FNvCX624%3D" > > > Let me know if you need any of the values I replaced with asterisks. > > > Thanks, > > > Carl > > > On Jun 30, 3:35 pm, Matt Harris wrote: > > > Hi Carl, > > > > Could you share your base string and the post headers you are sending? > > (with > > > the oauth token and secret obscured) and we'll see what we can find. > > > > Thanks, > > > Matt > > > > On Wed, Jun 30, 2010 at 1:10 PM, cthress wrote: > > > > Matt, > > > > > I'm running into a different issue now. I'm using the same method for > > > > authentication as I would for user_timeline, but I'm getting an > > > > "incorrect signature" error returned to me when I try authenticating. > > > > When I run the same function with user_timeline as the endpoint, it > > > > works great. Any ideas? > > > > > Thanks, > > > > > Carl > > > > -- > > > > Matt Harris > > > Developer Advocate, Twitterhttp://twitter.com/themattharris > > -- > > Matt Harris > Developer Advocate, Twitterhttp://twitter.com/themattharris
[twitter-dev] Limit search to poi place types
Is there search modifier for place type? So that if I run a search like this: http://search.twitter.com/search.atom?q=place:ac88a4f17a51c7fc Can I can limit the results to just those with place type = "poi"
[twitter-dev] Finding place id of a city
I was working with the place search method: http://api.twitter.com/1/geo/search.json?query=Portland,%20OR&granularity=city But, I'm only getting place results with type = poi What's the preferred way to get the place id of a city? I was able to get it with a lat/long: http://api.twitter.com/1/geo/reverse_geocode.json?lat=45.5234515&long=-122.6762071&granularity=city http://api.twitter.com/1/geo/search.json?lat=45.5234515&long=-122.6762071&granularity=city But, I was trying to see if I could get it with a string search. Thanks!
[twitter-dev] Re: oAuth and callback function
False alarm. I was calling an outdated include file. On Jun 30, 7:33 pm, Malayil George wrote: > I've only done PIN based authentication, but, my understanding of the > protocol was that you supply the callback url in your oauth request token > call? Are you seeing that you are getting the old callback after updating > the code in the request token step? > > George > > > > On Wed, Jun 30, 2010 at 9:23 PM, EastSideDev wrote: > > I changed the url for my callback function, and updated that > > information in my application settings on the twitter API site. The > > problem I am running into, is that I am still getting the old callback > > URL. Is there a lag time, before changes take effect?- Hide quoted text - > > - Show quoted text -
Re: [twitter-dev] oAuth and callback function
I've only done PIN based authentication, but, my understanding of the protocol was that you supply the callback url in your oauth request token call? Are you seeing that you are getting the old callback after updating the code in the request token step? George On Wed, Jun 30, 2010 at 9:23 PM, EastSideDev wrote: > I changed the url for my callback function, and updated that > information in my application settings on the twitter API site. The > problem I am running into, is that I am still getting the old callback > URL. Is there a lag time, before changes take effect?
[twitter-dev] oAuth and callback function
I changed the url for my callback function, and updated that information in my application settings on the twitter API site. The problem I am running into, is that I am still getting the old callback URL. Is there a lag time, before changes take effect?
Re: [twitter-dev] Re: Authentication for retweeted_by_me
Hi Carl, My immediate response is that the order of arguments in your basestring are different to the order in your authorization header. This would cause the signatures to be different as you signed them in one order but delivered in another. See if keeping them in the same order fixes it. Matt On Wed, Jun 30, 2010 at 2:29 PM, cthress wrote: > Matt, > > Here's the base string: > GET&http%3A%2F%2Fapi.twitter.com%2F1%2Fstatuses > %2Fretweeted_by_me.json&oauth_consumer_key%3D > %26oauth_signature_method%3DHMAC-SHA1%26oauth_timestamp > %3D1277932576%26oauth_token%3D%26oauth_version%3D1.0 > > > And here are the headers: > Authorization: OAuth realm="http%3A%2F%2Fapi.twitter.com > > %2F",oauth_version="1.0",oauth_nonce="e32167a3bfc33f59e1d18e3907df5ee6",oauth_timestamp="1277932576",oauth_consumer_key="*",oauth_token="*",oauth_signature_method="HMAC- > SHA1",oauth_signature="ZQZvWpefFlWr1ro%2FxMF%2FNvCX624%3D" > > > Let me know if you need any of the values I replaced with asterisks. > > > Thanks, > > Carl > > > On Jun 30, 3:35 pm, Matt Harris wrote: > > Hi Carl, > > > > Could you share your base string and the post headers you are sending? > (with > > the oauth token and secret obscured) and we'll see what we can find. > > > > Thanks, > > Matt > > > > On Wed, Jun 30, 2010 at 1:10 PM, cthress wrote: > > > Matt, > > > > > I'm running into a different issue now. I'm using the same method for > > > authentication as I would for user_timeline, but I'm getting an > > > "incorrect signature" error returned to me when I try authenticating. > > > When I run the same function with user_timeline as the endpoint, it > > > works great. Any ideas? > > > > > Thanks, > > > > > Carl > > > > -- > > > > Matt Harris > > Developer Advocate, Twitterhttp://twitter.com/themattharris > -- Matt Harris Developer Advocate, Twitter http://twitter.com/themattharris
Re: [twitter-dev] Re: Twitter Goodies
does it smthing related to twitter rate limit per hour? On Wed, Jun 30, 2010 at 5:15 PM, themattharris wrote: > Hi Nick, > > The widgets offer vary basic interaction with Twitter. If they do not > receive results it is likely Twitter is over capacity and results will > become available once service is resumed. > > As such, they don't any customizing over the options available on the > widget configuration screen. > > If you are interested in building a more reliable widget you can find > resources and information on our Developer Resources site > http://dev.twitter.com > > Hope that helps. > Matt > > On Jun 30, 1:34 pm, Nick wrote: > > can anybody, Please assist? > > > > On Jun 29, 11:39 am, Nick wrote: > > > > > > > > > Hi Support > > > > > I am using twitter goodies to show the recent tweets on my website. > > > But sometimes I dint get any response from twitter and hence was not > > > able to display anything on the website. > > > > > Is there any way I can handle such exceptions in twitter goodies? > > > > > Regards > > > Nikhlesh >
[twitter-dev] Re: Authentication for retweeted_by_me
Matt, Here's the base string: GET&http%3A%2F%2Fapi.twitter.com%2F1%2Fstatuses %2Fretweeted_by_me.json&oauth_consumer_key%3D %26oauth_signature_method%3DHMAC-SHA1%26oauth_timestamp %3D1277932576%26oauth_token%3D%26oauth_version%3D1.0 And here are the headers: Authorization: OAuth realm="http%3A%2F%2Fapi.twitter.com %2F",oauth_version="1.0",oauth_nonce="e32167a3bfc33f59e1d18e3907df5ee6",oauth_timestamp="1277932576",oauth_consumer_key="*",oauth_token="*",oauth_signature_method="HMAC- SHA1",oauth_signature="ZQZvWpefFlWr1ro%2FxMF%2FNvCX624%3D" Let me know if you need any of the values I replaced with asterisks. Thanks, Carl On Jun 30, 3:35 pm, Matt Harris wrote: > Hi Carl, > > Could you share your base string and the post headers you are sending? (with > the oauth token and secret obscured) and we'll see what we can find. > > Thanks, > Matt > > On Wed, Jun 30, 2010 at 1:10 PM, cthress wrote: > > Matt, > > > I'm running into a different issue now. I'm using the same method for > > authentication as I would for user_timeline, but I'm getting an > > "incorrect signature" error returned to me when I try authenticating. > > When I run the same function with user_timeline as the endpoint, it > > works great. Any ideas? > > > Thanks, > > > Carl > > -- > > Matt Harris > Developer Advocate, Twitterhttp://twitter.com/themattharris
[twitter-dev] Re: Twitter Goodies
Hi Nick, The widgets offer vary basic interaction with Twitter. If they do not receive results it is likely Twitter is over capacity and results will become available once service is resumed. As such, they don't any customizing over the options available on the widget configuration screen. If you are interested in building a more reliable widget you can find resources and information on our Developer Resources site http://dev.twitter.com Hope that helps. Matt On Jun 30, 1:34 pm, Nick wrote: > can anybody, Please assist? > > On Jun 29, 11:39 am, Nick wrote: > > > > > Hi Support > > > I am using twitter goodies to show the recent tweets on my website. > > But sometimes I dint get any response from twitter and hence was not > > able to display anything on the website. > > > Is there any way I can handle such exceptions in twitter goodies? > > > Regards > > Nikhlesh
[twitter-dev] Launch of the Golden Tweet Ratio
Hi Folks I'd like to let you know about an exciting new development, The Golden Tweet Ratio, “Originally what we wanted to create was a way of “on going” delivery of news and information to the users screen, while there’re still engaged in other social media conversations and activities. “To always be in the conversation”. With this in mind we called in the data analysts, the mathematicians and the “social media number crunchers”, we gave them a holy grail, “Is there a constant that exists in social media, amongst all the variables is there something that always remains the same?” Using the combination of a 2400 year old mathematical concepts and the astronomical amount of statistical data generated by the billion users of Social media networks, we set to work, analyzing the data, looking for repetition of events, looking for patterns. After a while, after many wild goose chases, we found that in fact a constant did exist, we called it the “chatter constant” Tc . On it’s own the “Tc”, made no sense, it had to be placed in relation to the variables. So the Tc was the first component of an equation, and time after time, however we did the math this number remained the same. The other components were; the number of contacts, connections, friends or followers and the user interface i.e. (the screen itself). The equation took shape over several weeks and we called it “The Golden Tweet Ratio” (G) A period of extensive beta testing in the later half of 2009 led to the redesign and fine tuning of “The Golden Tweet Ratio”, to accommodate for a wide variety of variables, across all existing and potential social media platforms. At this point we chose to concentrate on one social media portal, to test the equation, we decided to use Twitter. Let me say though that even though the equation was tested on the Twitter model, it’s not exclusively a twitter app, it can be applied across the board to any social media and networking niche, with any site, that utilises the micro-blogging or journal style layout. What we found was that “The Golden Tweet Ratio” has the ability to calculate the exact number of posts required per hour, to allow internet marketers to carve an almost permanent niche in the screen real estate of their digital associates, friends and followers. The Golden Tweet Ratio and it’s principles can be applied to any social media network, and it will work. Using it to achieve perfect leverage is a matter of delivering, relevant, up to date and interesting information to the end user. Social media users want a mix of news, entertainment, useful products that relate to their own interests and passions. Our results and The Golden Tweet Ratio, itself, are contained in a e- book which is now available for download from http://www.downloadablewealth.com/goldentweetratio.html We hope that a wide range of internet professionals will be able to use “the Ratio” as a pivotal part of their online activities.
Re: [twitter-dev] Re: Authentication for retweeted_by_me
Hi Carl, Could you share your base string and the post headers you are sending? (with the oauth token and secret obscured) and we'll see what we can find. Thanks, Matt On Wed, Jun 30, 2010 at 1:10 PM, cthress wrote: > Matt, > > I'm running into a different issue now. I'm using the same method for > authentication as I would for user_timeline, but I'm getting an > "incorrect signature" error returned to me when I try authenticating. > When I run the same function with user_timeline as the endpoint, it > works great. Any ideas? > > > Thanks, > > Carl > > -- Matt Harris Developer Advocate, Twitter http://twitter.com/themattharris
[twitter-dev] Re: Twitter Goodies
can anybody, Please assist? On Jun 29, 11:39 am, Nick wrote: > Hi Support > > I am using twitter goodies to show the recent tweets on my website. > But sometimes I dint get any response from twitter and hence was not > able to display anything on the website. > > Is there any way I can handle such exceptions in twitter goodies? > > Regards > Nikhlesh
[twitter-dev] Re: Authentication for retweeted_by_me
Matt, I'm running into a different issue now. I'm using the same method for authentication as I would for user_timeline, but I'm getting an "incorrect signature" error returned to me when I try authenticating. When I run the same function with user_timeline as the endpoint, it works great. Any ideas? Thanks, Carl
[twitter-dev] Re: Anywhere : fetch user's favorites
I am not sure about @Anywhere as I haven't looked into it. However they are also available as an RSS feed and as a widget: http://twitter.com/goodies/widget_faves Cheers Georgios http://favorious.com - Only the best of Twitter, based on favorites. On Jun 30, 8:56 am, Palleas wrote: > Thanks! So I guess it's not possible to do so directly using Anywhere? I > have to fetch them using PHP etc. ? > > Cheers ! > > Romain > > > > > > On Wed, Jun 30, 2010 at 9:08 AM, Georgios wrote: > > Hi Palleas > > > If you are after the tweets that a user has favorited then this > > explains how to do it:http://dev.twitter.com/doc/get/favorites > > > If you are after the tweets of the user that have been favorited, then > > that is not available from the Twitter API. It is available from other > > sites (not through an API though) such us a website I have build: > >http://favorious.com > > > For examplehttp://favorious.com/people/bpglobalprshows the tweets > > from BPGlobalPR that have been favorited. > > > Cheers > > Georgios > >http://favorious.com- Only the best of Twitter, based on favorites. > > > On Jun 29, 8:04 am, Palleas wrote: > > > Hi, > > > > I have a simple web project, but I need access to user"s favorites > > tweets. > > > Is this something we can do using Anywhere? All I can see is " > > > favourites_count", but that's not enough for me... > > > > Thanks! > > > > -- > > > Romain Pouclethttp://www.palleas.com > > -- > Romain Pouclethttp://www.palleas.com
Re: [twitter-dev] Re: oauth status update returning error 401 invalid / used nonce
On Jun 30, 2010, at 14:32 , James Ford wrote: > One thing I'm perhaps not clear on, do I need xAuth for this to work? You do need to get the access token somehow. That is what xAuth provides you. That said, you sound like you are a server app. Twitter doesn't support xAuth for server apps. You probably need to use the standard OAuth token request protocol. Anon, Andrew Andrew W. Donoho Donoho Design Group, L.L.C. a...@ddg.com, +1 (512) 750-7596 "To take no detours from the high road of reason and social responsibility." -- Marcus Aurelius
[twitter-dev] Re: How to get the latest retweets?
Anyone have any ideas about this? On Jun 26, 9:12 pm, empika wrote: > Hallo > > I am having an issue with fetching and caching retweets of a user and > was wondering if anyone has any advice of how to handle this properly. > > I am currently calling statuses/retweets_of_me with since_id as the id > of the last cached retweet I have. > My problem is that statuses/retweets_of_me returns results in the > order that the original tweets were published, not in the order that > the retweets were published. > For example, tweet A was published yesterday and tweet B was published > today. If i retweet B, retweets_of_me would return an array with B as > the first element. If i then retweet A, and call statuses/ > retweets_of_me with a since_id of B's id, I get nothing back. > If I call statuses/retweets_of_me without setting a since id it would > return an array with B still as the first element, even though A has > had the most recent activity. > > So, any tips on how to get the latest retweets, perhaps without having > to call statuses/retweets_of_me without a since_id and without having > to call statuses/retweets on each returned tweet. > > Thanks
[twitter-dev] Re: oauth status update returning error 401 invalid / used nonce
Hi Craig, Taylor, did you guys ever figure out what the problem was? I am having a very similar issue to Craig. I am trying to post a status update to Twitter from a server-side PHP app. More specifically, it is to automatically tweet updates from a news site I help develop. I'm using all the same types of HTTP authorization headers, and base strings, and tokens and such as Craig, but I can't get any variation to work. I've used OAuth programmatically with Vimeo quite successfully. With Twitter, however, I've no luck. One thing I'm perhaps not clear on, do I need xAuth for this to work? Regards, James. On Jun 17, 12:28 am, Taylor Singletary wrote: > Can you follow up with me off the list and I'll help you out tomorrow? We'll > need to compare signatures and work with me knowing your application > secrets. There's something subtle going on. > > Taylor > > > > On Wed, Jun 16, 2010 at 3:22 PM, Craig wrote: > > Just tried it. Same error. So at least that rules something out... > > > -Craig > > > On Jun 16, 5:19 pm, Taylor Singletary > > wrote: > > > I agree that it's the wrong error. We have a new, better implementation > > of > > > OAuth waiting in the wings that's going to be much more helpful in this > > > regard. > > > > I'm still trying to rule out some possibilities. Can you try and create a > > > new application, then grab the access token from the my access token > > > feature, and try to post? It'll just help rule something out. > > > > Taylor Singletary > > > Developer Advocate, Twitterhttp://twitter.com/episod > > > > On Wed, Jun 16, 2010 at 1:55 PM, Craig wrote: > > > > I am in "read/write" mode. > > > > > I tried posting to two different twitter accounts without luck...my > > > > dev account, where I know what the access secret and token is supposed > > > > to be and another one I just created. I know my access token and > > > > secret are being stored correctly and I believe they are being used > > > > correctly in the auth header and the signature base string. > > > > > Other thoughts? It would be nice to get an error returned that was a > > > > little more indicative of what the problem might be. Invalid/used > > > > nonce isn't really cutting it right now. > > > > > Thanks, > > > > Craig > > > > > On Jun 16, 3:52 pm, Taylor Singletary > > > > wrote: > > > > > Our setup is such that I can't easily trace a single request. > > > > > > Connecting some dots: if you have time, can you try to use a > > different > > > > > access token with your keys and see if it has the ability to tweet? > > > > > > Can you go to your application settings and verify that your > > application > > > > is > > > > > in "read/write mode" on dev.twitter.com? > > > > > > Finally, this might be a case of something funky with your client > > > > > application -- which might be resolved by creating a new one. But > > let's > > > > rule > > > > > out some other possibilities first. > > > > > > Taylor Singletary > > > > > Developer Advocate, Twitterhttp://twitter.com/episod > > > > > > On Wed, Jun 16, 2010 at 12:39 PM, Craig > > wrote: > > > > > > By the way, even when I try to tweet with just one word like: > > "tweet", > > > > > > it doesn't work. Just simple ascii characters. Is there any way > > you > > > > > > can just intercept one of my test tweets and look at what, if > > anything > > > > > > might be going wrong on the server side? > > > > > > > -Craig > > > > > > > On Jun 16, 3:05 pm, Craig wrote: > > > > > > > My signature base string status pair looks like: > > > > > > > status%3Dmy%2520tweet > > > > > > > > When I tried xAuth authentication with a * character in the > > password, > > > > > > > it didn't work at first. But once I double url encoded it, I was > > > > able > > > > > > > to authenticate no problem. So that definitely helps. I am now > > > > > > > double url encoding the username and password values. > > > > > > > > However, the tweet still didn't work. I am double url encoding > > the > > > > > > > status message in the signature base string and single url > > encoding > > > > it > > > > > > > in the post body. > > > > > > > > Thanks, > > > > > > > Craig > > > > > > > > On Jun 16, 11:30 am, Taylor Singletary < > > taylorsinglet...@twitter.com > > > > > > > > wrote: > > > > > > > > > Hi Craig, > > > > > > > > > Do you know if the status update, status=my%20tweet is being > > > > encoded > > > > > > > > correctly in your signature base string (which is the string > > used > > > > to > > > > > > create > > > > > > > > your signature). > > > > > > > > > For the signature base string, the key/value pair would look > > like: > > > > > > > > > status%3Dmy%2520tweet > > > > > > > > > Have you tried your xAuth authentication with spaces and other > > > > possible > > > > > > odd > > > > > > > > characters yet in fields like the password? > > > > > > > > > Taylor > > > > > > > > > On Wed, Jun 16, 2010 at 8:21 AM, Craig > > > > wrote: > > > > > > > > > Hi Matt, > > > > > > > > > > Thank
[twitter-dev] @raffi & @themattharris @hackerdojo tomorrow thursday july 1 - 6:30pm
http://www.meetup.com/TwitterMeetup/calendar/13830016 @raffi & @themattharris will be sharing their knowledge of the Twitter APIs and tips and tricks for getting the most out of it. They'll talk about things like what xAuth and OAuth Echo is, how to use @anywhere, what you can do with new Geo API and the new features available on timelines. Hacker Dojo 140A S Whisman Road Mountain View, CA 94041 6:30 pm - 8:30 pm pizza, networking, awesome presenters, a third party demo or two
Re: [twitter-dev] Authentication for retweeted_by_me
Hi Carl, There is an error on the docs page. The retweeted_by_me method requires authentication to work as it uses the authentication users as the 'me'. Have a go by authenticating as you would with user_timeline and let us know how it goes. Best, Matt On Wed, Jun 30, 2010 at 10:35 AM, cthress wrote: > I'm trying to grab api.twitter.com/1/statuses/retweeted_by_me.json > using CURL and PHP, with OAuth authentication. I'm able to get the > user_timeline.json without any problems, but for some reason, I keep > getting an error "Could not authenticate with OAuth" when I try to > retrieve the retweeted_by_me data using the same method. > > In the documentation (http://dev.twitter.com/doc/get/statuses/ > retweeted_by_me), it says that authentication is not required for > retweeted_by_me, but when I try to access the page without > authenticating first, it tells me it cannot authenticate me. So I'm > guessing that authentication really is required. > > If anyone knows any tricks or special instructions needed for > retrieving the retweeted_by_me data, please let me know. > > > Thanks! > > Carl > -- Matt Harris Developer Advocate, Twitter http://twitter.com/themattharris
[twitter-dev] Authentication for retweeted_by_me
I'm trying to grab api.twitter.com/1/statuses/retweeted_by_me.json using CURL and PHP, with OAuth authentication. I'm able to get the user_timeline.json without any problems, but for some reason, I keep getting an error "Could not authenticate with OAuth" when I try to retrieve the retweeted_by_me data using the same method. In the documentation (http://dev.twitter.com/doc/get/statuses/ retweeted_by_me), it says that authentication is not required for retweeted_by_me, but when I try to access the page without authenticating first, it tells me it cannot authenticate me. So I'm guessing that authentication really is required. If anyone knows any tricks or special instructions needed for retrieving the retweeted_by_me data, please let me know. Thanks! Carl
Re: [twitter-dev] Re: Rate limit reduction to 75?
Hi John, I appreciate the offer, and I'm excited about user steams. I attended your talk about it at chirp. But I'm afraid I don't have the resources to invest in experimental development. When everything's settled and user-streams are a reality I'll join the crowd. isaiah http://twitter.com/isaiah On Jun 29, 2010, at 7:24 PM, John Kalucki wrote: > Isaiah, > > I'm assuming your client is Kiwi, a desktop client. Are you interested in > participating in the User Streams beta test for desktop clients? User Streams > are not subject to the same rate limits that the rest of the API must adhere > to. > > We're currently lining up clients to start the beta test in the next few > weeks. Basically, you'll need to implement oAuth and follow the guidelines > (http://apiwiki.twitter.com/User-Stream-Implementation-Suggestions) to get > ready for a limited private test for a few hundred users. For capacity > planning purposes, we'll also need to understand how many users to expect > during a public beta and how many installed copies you have. > > Let me know if you'd like to participate. > > -John Kalucki > http://twitter.com/jkalucki > Infrastructure, Twitter Inc. > > > > > > > > > > On Tue, Jun 29, 2010 at 12:30 PM, isaiah wrote: > > Given that Raffi told us that that Rate Limits would be going to 10X > by chirp -- it almost sounds like a joke now, but he definitely seemed > serious -- we designed features that were already constrained at 350 > calls/hr. > > Now at these dramatically lower limits, even with dynamic adjustments, > many features are failing regularly and our customers are screaming. > > Clearly cutting features from our app is pretty much the only way > forward. However we were already having trouble trying to maintain > some semblance of feature parity with Twitter.com -- which is what our > users are demanding. > > With the failures and changes combined our users are going to be > marching with pitchforks very and torches looking for heads to chop > very soon. > > I'm not asking for any specific action here. Merely passing along the > anger that we see just in case you weren't aware of it. > > Isaiah > >
Re: [twitter-dev] Help! Failed to validate oauth signature and token
Hi Slavik, Happy to help. Are you able to share the signature base string that goes with this request? Do you know if the server/system you're executing this from has a clock in sync with Twitter's? (We offer the current date / time in the HTTP response to failed and successful requests). I take it your Authorization header doesn't actually contain the line break seen there? Thanks, Taylor On Wed, Jun 30, 2010 at 3:01 AM, slavik wrote: > I am writting a client on Symbian. > > There is no lib for the platform, so I write one. However, I have not > been successful yet. > > When I post to http://api.twitter.com/oauth/request_token, I always > get "Failed to validate oauth signature and token". > > I have check the time and the signature value according to the > > https://hueniverse.com/2008/10/beginners-guide-to-oauth-part-iv-signing-requests/ > They are all right. But it just don't work. > > Could anybody help me? > > The following is what I posted > > POST /oauth/request_token HTTP/1.1 > Host: api.twitter.com > Authorization: OAuth > > oauth_nonce="QP70eNmVz8jvdPevU3oJD2AfF7R7odC2XJcn4XlZJqk",oauth_signature_method="HMAC- > > SHA1",oauth_timestamp="1277790519",oauth_consumer_key="5E1f**QBg",oauth_version="1.0",oauth_signature="neYefd > %2FM2fNwj%2BVyDW1P7v0M2xk%3D" > Content-Length: 0 > > HTTP/1.1 401 Unauthorized > Date: Wed, 30 Jun 2010 09:49:29 GMT > Server: hi > Status: 401 Unauthorized > X-Transaction: 1277891369-55674-5200 > Last-Modified: Wed, 30 Jun 2010 09:49:29 GMT > X-Runtime: 0.00588 > Content-Type: text/html; charset=utf-8 > Content-Length: 44 > Pragma: no-cache > X-Revision: DEV > Expires: Tue, 31 Mar 1981 05:00:00 GMT > Cache-Control: no-cache, no-store, must-revalidate, pre-check=0, post- > check=0 > Set-Cookie: k=72.13.82.125.1277891369172474; path=/; expires=Wed, 07- > Jul-10 09:49:29 GMT; domain=.twitter.com > Set-Cookie: guest_id=127789136917890129; path=/; expires=Fri, 30 Jul > 2010 09:49:29 GMT > Set-Cookie: > _twitter_sess=BAh7CToRdHJhbnNfcHJvbXB0MDoPY3JlYXRlZF9hdGwrCNvYQogpAToHaWQi > %250AJTlkZWMwNzNmY2NlYjE4Y2U1MWE5ZTgyMTJlYWM5M2UyIgpmbGFzaElDOidB > > %250AY3Rpb25Db250cm9sbGVyOjpGbGFzaDo6Rmxhc2hIYXNoewAGOgpAdXNlZHsA--0233aacfda88d179166546d965bad353ad8dda38; > domain=.twitter.com; path=/ > Vary: Accept-Encoding > Connection: close > > Failed to validate oauth signature and token >
Re: [twitter-dev] Search tweets of a particular user not working.. Can some one give a light ?
Hi Nissar, Some users or tweets don't end up within search results -- you can read more about this here: http://help.twitter.com/entries/66018-my-tweets-or-hashtags-are-missing-from-search-known-issue-- there are also times when the search index is a few steps behind on indexing. Taylor On Wed, Jun 30, 2010 at 12:01 AM, Nissar Pulikkil wrote: > Hi mates, > > When I try to search for all tweets of a particular user, it is not > working for some users.. but working for some other users... > > ie, if you try http://twitter.com/search?q=from%3Apknissar not working > (not returning any tweets.. but there are tweets) > again, http://twitter.com/search?q=from%3Asachin_rt not returning any > tweets.. > > but .. http://twitter.com/search?q=from%3Akarikalan78 working > fine..!!! > > Can any one give an idea on.. what could be the reason and how to get > this ? > > Thanks in advance.. > > regards, > Nissar >
Re: [twitter-dev] Streaming API: Why not Curl?
It's not libcurl, per se, that's the problem, but just using curl(1) from a shell script doesn't necessarily give you the control that you might desire to build a stable client. You may want to set a connect timeout, socket timeout, perform parsing before persisting to disk, use overlapping connections to update predicates without data loss, provide an estimate for the count parameter, deal with events from downstream processes, rotate journal files, or any number of other things that are non-obvious or difficult to do with a single threaded shell script wrapping a curl(1) process. You require periodic reconnections to deal with predicate change on your end, or operational bumps (server restarts after code deploys) on our end. Most of the blogged Streaming API examples I've seen contain no error handling and would cause you to get locked out and your IP address eventually banned. -John Kalucki http://twitter.com/jkalucki Infrastructure, Twitter Inc. On Wed, Jun 30, 2010 at 2:47 AM, Mark Linsey wrote: > I am just getting started with the streaming API, and I was a bit > puzzled by this line in the documentation: > > "While a client can be built around cycling connections, perhaps using > curl for transport, the overall reliability will tend to be poor due > to operational gotchas. Save curl for debugging and build upon a > persistent process that does not require periodic reconnections." > > I am not at all familiar with the internals of how libcurl works, so > maybe I'm missing something quite obvious, but can't curl/libcurl keep > a persistent connection? Why does using it require periodic > reconnections? In fact, many examples around the web of how to consume > the streaming API seem to use libcurl. (I'm using Python so have been > looking at this example in particular: > > http://arstechnica.com/open-source/guides/2010/04/tutorial-use-twitters-new-real-time-stream-api-in-python.ars > ) >
[twitter-dev] Search tweets of a particular user not working.. Can some one give a light ?
Hi mates, When I try to search for all tweets of a particular user, it is not working for some users.. but working for some other users... ie, if you try http://twitter.com/search?q=from%3Apknissar not working (not returning any tweets.. but there are tweets) again, http://twitter.com/search?q=from%3Asachin_rt not returning any tweets.. but .. http://twitter.com/search?q=from%3Akarikalan78 working fine..!!! Can any one give an idea on.. what could be the reason and how to get this ? Thanks in advance.. regards, Nissar
Re: [twitter-dev] Re: Anywhere : fetch user's favorites
Thanks! So I guess it's not possible to do so directly using Anywhere? I have to fetch them using PHP etc. ? Cheers ! Romain On Wed, Jun 30, 2010 at 9:08 AM, Georgios wrote: > Hi Palleas > > If you are after the tweets that a user has favorited then this > explains how to do it: http://dev.twitter.com/doc/get/favorites > > If you are after the tweets of the user that have been favorited, then > that is not available from the Twitter API. It is available from other > sites (not through an API though) such us a website I have build: > http://favorious.com > > For example http://favorious.com/people/bpglobalpr shows the tweets > from BPGlobalPR that have been favorited. > > Cheers > Georgios > http://favorious.com - Only the best of Twitter, based on favorites. > > On Jun 29, 8:04 am, Palleas wrote: > > Hi, > > > > I have a simple web project, but I need access to user"s favorites > tweets. > > Is this something we can do using Anywhere? All I can see is " > > favourites_count", but that's not enough for me... > > > > Thanks! > > > > -- > > Romain Pouclethttp://www.palleas.com > -- Romain Pouclet http://www.palleas.com
[twitter-dev] Streaming API: Why not Curl?
I am just getting started with the streaming API, and I was a bit puzzled by this line in the documentation: "While a client can be built around cycling connections, perhaps using curl for transport, the overall reliability will tend to be poor due to operational gotchas. Save curl for debugging and build upon a persistent process that does not require periodic reconnections." I am not at all familiar with the internals of how libcurl works, so maybe I'm missing something quite obvious, but can't curl/libcurl keep a persistent connection? Why does using it require periodic reconnections? In fact, many examples around the web of how to consume the streaming API seem to use libcurl. (I'm using Python so have been looking at this example in particular: http://arstechnica.com/open-source/guides/2010/04/tutorial-use-twitters-new-real-time-stream-api-in-python.ars)
[twitter-dev] Help! Failed to validate oauth signature and token
I am writting a client on Symbian. There is no lib for the platform, so I write one. However, I have not been successful yet. When I post to http://api.twitter.com/oauth/request_token, I always get "Failed to validate oauth signature and token". I have check the time and the signature value according to the https://hueniverse.com/2008/10/beginners-guide-to-oauth-part-iv-signing-requests/ They are all right. But it just don't work. Could anybody help me? The following is what I posted POST /oauth/request_token HTTP/1.1 Host: api.twitter.com Authorization: OAuth oauth_nonce="QP70eNmVz8jvdPevU3oJD2AfF7R7odC2XJcn4XlZJqk",oauth_signature_method="HMAC- SHA1",oauth_timestamp="1277790519",oauth_consumer_key="5E1f**QBg",oauth_version="1.0",oauth_signature="neYefd %2FM2fNwj%2BVyDW1P7v0M2xk%3D" Content-Length: 0 HTTP/1.1 401 Unauthorized Date: Wed, 30 Jun 2010 09:49:29 GMT Server: hi Status: 401 Unauthorized X-Transaction: 1277891369-55674-5200 Last-Modified: Wed, 30 Jun 2010 09:49:29 GMT X-Runtime: 0.00588 Content-Type: text/html; charset=utf-8 Content-Length: 44 Pragma: no-cache X-Revision: DEV Expires: Tue, 31 Mar 1981 05:00:00 GMT Cache-Control: no-cache, no-store, must-revalidate, pre-check=0, post- check=0 Set-Cookie: k=72.13.82.125.1277891369172474; path=/; expires=Wed, 07- Jul-10 09:49:29 GMT; domain=.twitter.com Set-Cookie: guest_id=127789136917890129; path=/; expires=Fri, 30 Jul 2010 09:49:29 GMT Set-Cookie: _twitter_sess=BAh7CToRdHJhbnNfcHJvbXB0MDoPY3JlYXRlZF9hdGwrCNvYQogpAToHaWQi %250AJTlkZWMwNzNmY2NlYjE4Y2U1MWE5ZTgyMTJlYWM5M2UyIgpmbGFzaElDOidB %250AY3Rpb25Db250cm9sbGVyOjpGbGFzaDo6Rmxhc2hIYXNoewAGOgpAdXNlZHsA--0233aacfda88d179166546d965bad353ad8dda38; domain=.twitter.com; path=/ Vary: Accept-Encoding Connection: close Failed to validate oauth signature and token
[twitter-dev] [ANN] Semiocast releases micromessage analysis API
Hello Everyone, Semiocast has been developing technologies for analyzing micro-messages (such as Twitter and Facebook messages) and today Semiocast is making two of these technologies available to the public as a web service through its API: - language identification from short text: 61 languages recognized (including non-latin languages such as Arabic, Chinese, Farsi, Japanese, Korean, Pashto, Russian, Ukrainian…); - location extraction from short text: city and country recognized from free form text or GPS coordinates. Although these technologies were specifically developed for short free form texts, Semiocast API is tailored for analyzing Twitter messages (and other networks such as Facebook, StatusNet…). With Semiocast API, you can: - analyze status updates and timelines to extract language and user location; - filter timelines according to languages and locations; - prepare annotations based on semantic analysis for a message to be posted on Twitter using the forthcoming annotation feature. We are very excited by what you will be able to build using this API. For example, you can use Semiocast API to compute statistics about messages or to filter out messages in languages end-users do not understand. Semiocast has used the very same technology for the February and March 2010 studies that revealed that less than 50% of tweets were not in English and gave a break down of tweets by languages and countries. Future releases will give access to more of our technologies such as tokenization, sentiment analysis and topic extraction. For more information, please visit Semiocast API website: http://developer.semiocast.com/ Let us know what you think! Jean-Charles
[twitter-dev] Re: Anywhere : fetch user's favorites
Hi Palleas If you are after the tweets that a user has favorited then this explains how to do it: http://dev.twitter.com/doc/get/favorites If you are after the tweets of the user that have been favorited, then that is not available from the Twitter API. It is available from other sites (not through an API though) such us a website I have build: http://favorious.com For example http://favorious.com/people/bpglobalpr shows the tweets from BPGlobalPR that have been favorited. Cheers Georgios http://favorious.com - Only the best of Twitter, based on favorites. On Jun 29, 8:04 am, Palleas wrote: > Hi, > > I have a simple web project, but I need access to user"s favorites tweets. > Is this something we can do using Anywhere? All I can see is " > favourites_count", but that's not enough for me... > > Thanks! > > -- > Romain Pouclethttp://www.palleas.com
