[twitter-dev] Re: Twitter Error codes/statements?
Only info I have found so far is http://apiwiki.twitter.com/HTTP-Response-Codes-and-Errors On May 28, 1:02 am, Michael Cameron darx...@gmail.com wrote: So i am writing my catch expressions for twitter when parsing the response from twitter is there any error codes or definite strings for certain reasons. example not following user, or other errors? Thank you!
[twitter-dev] Re: OAuth UTF-8 issue
I can also vouch for OAuth UTF-8 issues as I retrieve some funky chars on my side. I went as far as checking the encodings and converting any non utf-8 strings myself to no avail. A very quick example of something that does not work is pulling the name field from the account: http://www.twitter.com/snipeyhead On May 27, 6:43 pm, Alvaro Montoro alvaromont...@gmail.com wrote: Also, if I try to post something like: 私のさえずりを設定する, it works. In fact, if I try to post anything with a japanese character in it, the tweet will go through correctly.
[twitter-dev] Re: Twitter Error codes/statements?
Yeah i have only seen a response error, I would hope that we could get a tabularized list of those error responses. it would make debuging so much easier. On May 28, 1:53 am, wibblefish docherty.ja...@gmail.com wrote: Only info I have found so far ishttp://apiwiki.twitter.com/HTTP-Response-Codes-and-Errors On May 28, 1:02 am, Michael Cameron darx...@gmail.com wrote: So i am writing my catch expressions for twitter when parsing the response from twitter is there any error codes or definite strings for certain reasons. example not following user, or other errors? Thank you!
[twitter-dev] Re: Entities not working?
Strangely, it's working along with the parameter since_id under some conditions. My web app initially loads home_timeline?count=100 (the app is in its infancy and only I use it, otherwise I'd be using since_id and a cache). Every three minutes thereafter, an ajax call gets new tweets using home_timeline?since_id=[id]include_entities=true. That works -- it retrieves the entities. However, if I manually refresh (i.e., call the exact same ajax function explicitly rather than wait for the setTimeout to do it), I get the error 500 page as the response, as described below. On May 27, 9:40 pm, Ellsass cpa...@gmail.com wrote: For most of the day I was getting the new entities just fine, but for the last hour or two my home_timeline XML request is met with the Something is technically wrong. page as the response. I am using PHP EpiTwitter. This works fine: $twitterInfo = $twitterObj-get_statusesHome_timeline(array(count = $numTweets)); This was working for most of the day, but not recently: $twitterInfo = $twitterObj-get_statusesHome_timeline(array(count = $numTweets , include_entities = true));
[twitter-dev] Re: oAuth Echo problems
Rich, thanks so much.. my issue ended up being that I was signing my OAuth Echo header as a POST request (because my request is a POST to twitpic), not GET. On May 22, 2:14 am, Rich rhyl...@gmail.com wrote: The request to verify_credentials should be a GET and shouldn't contain any of the parameters you intend to send to TwitPic either On May 22, 4:51 am, Miguel de Icaza miguel.de.ic...@gmail.com wrote: Hello, 1) You do not oAuth sign the actual request toTwitPic 2) You make a fake request to Twitter's verify credentials api over SSL and grab the Authorization header that would be sent, however when you create the header make sure you include a 'Realm' ofhttps://api.twitter.com 3) Create a new post request toTwitPicand put the oAuth header that you grabbed from Authorization in the HTTP header X-Verify-Credentials- Authorization 4) Add a X-Auth-Service-Provider header with the URL to verify credentials. 5) You should be good to go after that I tried this, but I am getting the following message from TwitPic: could not authenticate you (header rejected by twitter) I created the OAuth headers as if I was trying to send an OAuth request tohttps://api.twitter.com/1/account/verify_credentials.json and added those headers to X-Verify-Credential-Authorization The headers contain realm http://api.twitter.com; (tried also with https) Any ideas what Header rejected by twitter means? If you get the signature right, it will work as I and a few others have got it working when we were liasing with their engineers on Sunday On May 19, 3:41 am, uprise78 des...@gmail.com wrote: I'm in the same boat. My call to Twitter works fine but I get 401's fromTwitPicevery time.
Re: [twitter-dev] Encrypted data over Twitter
Yes, the laws covered encryption technology and not ciphertext. You are also correct about regulations concerning amateur radio broadcasts but that is a different topic. The airwaves are highly regulated and broadcasters must have a license. I see no legal difference between inserting ciphertext into this email which is viewable by many and inserting the same into a tweet. It is indeed antisocial and Twitter may deem it violates TOS but I think it would be legal. Remember, even simple things like ROT13 are considered encryption. ROT13 was used heavily in usenet (you remember that). EBG13 vf rapelcgvba! BTW, the amateur radio regulation has hampered one of my activities in Disaster Response. If communication systems fail, amateur radio is considered the great fall-back. So we discussed how to transfer files which may contain health or financial information. We basically had to go caveman style and write that our backup plan was to use a courier even though we were sitting next to a fully functioning ham radio. On Thu, May 27, 2010 at 1:58 AM, Dave Sherohman d...@fishtwits.com wrote: On Wed, May 26, 2010 at 10:16:40AM -0700, John Adams wrote: I think you're referring to ITAR, most of which was repealed in 1997. Until 1996?1997, ITAR classified strong cryptography as arms and prohibited their export from the U.S. Times have changed quite a bit since then. Also, as I understood the matter at the time, ITAR only restricted international distribution of encryption technology (i.e., crypto algorithms and implementations of those algorithms) and didn't care at all about what might be done with the resulting ciphertext or where it might be sent. However... Amateur radio regulations in the US do include (or at least did include last I heard) an absolute ban on transmitting encrypted information. It used to be fairly common for ham radio operators to use packet radio technologies to transmit TCP/IP data over the amateur bands in order to get free roaming internet access; I expect this practice is less common today (thanks to widespread cellular data access), but not extinct. When using packet radio on amateur bands, ssh/ssl/etc. are not legal due to the crypto ban on those bands. I would expect encrypted tweets to be illgal under the same regulations, although that may be dependent on whether the receiver has the means to decrypt them. -- Dave Sherohman
[twitter-dev] Re: New opt-in API features available today, May 26th: entities, retweets in timelines, custom oauth_callback schemes
It appears that skip_user=true is ignored by the retweets returned in a timeline method using include_rts=true Is this a bug or as-designed? And may I +1 uprise78's point about the utility of adding entities to all returned tweets, especially search. Finally, it would be super-helpful to have a changelog on dev.twitter.com—especially if it came with an rss feed!
[twitter-dev] Open Call for Twitter Marketing and Advertising Blog Submissions
Twitter developers have a lot of insight into what works and what doesn't in a Twitter application, but there is no road map yet to building one that is commercially successful. Yesterday I launched a blog at http://blog.pay4tweet.com and I'd like to showcase articles, blog posts, charts, data, analysis, infographics, and insights about the commercial use of Twitter. - If you have a startup or are building an application that uses Twitter, and you'd like to have a place to discuss your insights consider this an open call for article submissions. - If you already have a blog, please send us a link and we'll add it to our blogroll. Also, feel free to send us a link to your new articles, or @reply @pay4tweet with the post title and link. Hopefully, with your contributions, we can create a blog that developers and startups can reference to figure out the best way to promote and monetize their applications. -Mo http://www.pay4tweet.com
[twitter-dev] Re: Post from C#
Al, Be sure to get the 2.1 beta that was just recently posted. Andrew, I'm not sure what you mean saying that the .NET OAuth stuff is out of date/incomplete on the Twitter side. On May 26, 3:15 pm, Andrew Badera and...@badera.us wrote: Cool. Just keep in mind a lot of the .NET OAuth stuff, especially on the Twitter side, is somewhat out of date or incomplete. --ab On Wed, May 26, 2010 at 2:51 PM, Al aa1...@gmail.com wrote: Thanks for the link. I also found this page: http://apiwiki.twitter.com/OAuth-Examples AL. On May 26, 9:29 am, Al aa1...@gmail.com wrote: I am a new to programming, what I want to do is post a comment to my twitter page using C#. Something simple amd direct, I have started my C# app with the Twitterizer api. Is this api a good place to start? I just want to contact my Twitter page and post a message. Thanks AL.
Re: [twitter-dev] Open Call for Twitter Marketing and Advertising Blog Submissions
Quoting Mo maur...@moluv.com: Twitter developers have a lot of insight into what works and what doesn't in a Twitter application, but there is no road map yet to building one that is commercially successful. Yesterday I launched a blog at http://blog.pay4tweet.com and I'd like to showcase articles, blog posts, charts, data, analysis, infographics, and insights about the commercial use of Twitter. - If you have a startup or are building an application that uses Twitter, and you'd like to have a place to discuss your insights consider this an open call for article submissions. - If you already have a blog, please send us a link and we'll add it to our blogroll. Also, feel free to send us a link to your new articles, or @reply @pay4tweet with the post title and link. Hopefully, with your contributions, we can create a blog that developers and startups can reference to figure out the best way to promote and monetize their applications. -Mo http://www.pay4tweet.com What's your business model? How do *you* make money?
Re: [twitter-dev] Re: New opt-in API features available today, May 26th: entities, retweets in timelines, custom oauth_callback schemes
On Fri, May 28, 2010 at 8:08 AM, earth2marsh ma...@earth2marsh.com wrote: Finally, it would be super-helpful to have a changelog on dev.twitter.com—especially if it came with an rss feed! +1
[twitter-dev] Bug with source parameter in Twitter search ?
Over the past several weeks, I've seen an intermittent issue with Twitter search. A search of http://search.twitter.com/search?q=%23ceconomy shows all recent tweets with this hashtag. Multiple people have used this hashtag. However, a source-based search of http://search.twitter.com/search?q=%23cEconomy+source%3AiPhoneEconomyApp returns zero results (even though almost all the tweet-results from the previous search are from this source) The same source-based search works fine on some days (and it returns all tweets made over the past 5-6 days with this source and hashtag). On days like today, it returns zero results. On other days, it returns partial results. I'm assuming that adding a source parameter should not suppress any results for tweets (made from the specified source) that show up in searches made without the source parameter. Can someone from Twitter confirm that this is a bug (or does anyone else have any thoughts on this issue) ?
[twitter-dev] Re: Open Call for Twitter Marketing and Advertising Blog Submissions
Good question. The answer is rev share on text ads, and text ad networks. Pay4Tweet.com enables transactions for tweets. Those tweets will serve as the datasource for ads similar to Adsense. The trick is that these types of ads and networks have to grow organically first. http://www.pay4tweet.com provides a very simplified interface to help that happen. You can see an example of what a final text ad unit can look like at http://www.moluv.com . There are also a lot of other creative possibilities for text ads. Twistori and Digg Labs Big Spy are some pretty good examples. Hope that sheds a little light. Maybe I should put this in a blog post. :-) Twistori: http://www.twistori.com Digg Labs Big Spy: http://labs.digg.com/bigspy/ On May 28, 10:29 am, M. Edward (Ed) Borasky zn...@borasky- research.net wrote: Quoting Mo maur...@moluv.com: Twitter developers have a lot of insight into what works and what doesn't in a Twitter application, but there is no road map yet to building one that is commercially successful. Yesterday I launched a blog athttp://blog.pay4tweet.comand I'd like to showcase articles, blog posts, charts, data, analysis, infographics, and insights about the commercial use of Twitter. - If you have a startup or are building an application that uses Twitter, and you'd like to have a place to discuss your insights consider this an open call for article submissions. - If you already have a blog, please send us a link and we'll add it to our blogroll. Also, feel free to send us a link to your new articles, or @reply @pay4tweet with the post title and link. Hopefully, with your contributions, we can create a blog that developers and startups can reference to figure out the best way to promote and monetize their applications. -Mo http://www.pay4tweet.com What's your business model? How do *you* make money?
[twitter-dev] Re: Getting 401 when using one access token with OAuth
Thanks for this response, Taylor. Turns out I was making a noob mistake and it's all squared away. Your trouble shooting tips helped me find that mistake. ~Barry On May 17, 9:58 am, Taylor Singletary taylorsinglet...@twitter.com wrote: Hi Barry, Unfortunately can't go to the logs to figure out what's going wrong -- but happy to help. You don't need xAuth access to get this to work, you are correct. There may be other reasons it is failing for you. One thing to check is that your system clock is synced with a NTP server or reasonably correct -- if the timestamp generated by the OAuth flow doesn't match ours within about 5 minutes, you'll get an invalid request. As for the example: just dotting i's: you've placed your consumer key and secret on line 3 of the example and your oauth_token and oauth_token_secret (access token) on the method call for prepare_access_token? Assuming all is correct, this part should function. After you've checked your clock and if you're still having issues I'll help you debug this further. Thanks, Taylor Singletary Developer Advocate, Twitterhttp://twitter.com/episod On Mon, May 17, 2010 at 7:35 AM, bjhess ba...@bjhess.com wrote: I'm not 100% sure that applies. I've been told by Twitter support that I should not be using xAuth. Twitter - any help here? ~Barry On May 15, 8:23 am, @sebagomez sebastiangomezcor...@gmail.com wrote: Take a look in this post at the suggestion Taylor sent me. http://groups.google.com/group/twitter-development-talk/browse_thread... regards On May 14, 5:48 pm, bjhess ba...@bjhess.com wrote: I'm trying to implement the following in Ruby: http://dev.twitter.com/pages/oauth_single_token Unfortunately I'm receiving 401's from to Twitter usernames, harvest and harvest_test. Both have been set up with an OAuth key and secret. I'm essentially using the identical code to your sample. I contacted Twitter support seeking xAuth access, thinking that was what was leading me to the 401. They've sent me here. Anything you'd like me to share from how I'm calling Twitter would be beneficial. Hopefully you can see my failures in your logs from yesterday, though. Thanks! ~Barry Hesshttp://www.getharvest.com
Re: [twitter-dev] Re: Important Notice on Incorrect API Endpoints for Search, REST, OAuth (+ some general tips!)
Taylor: Can we get clarification on the since_id issue? You have warned us that not using since_id will get us blacklisted, and at the same time since_id appears to still be broken according to others on this list. Please advise. What I do is request 100 responses per page, and then manually check each tweet against the most recent tweet_id I've received for this query. I stop asking for more pages when I reach a tweet that I already have. Is this acceptable, or is since_id working now? On Fri, May 28, 2010 at 1:41 AM, janole s...@mobileways.de wrote: Hi Taylor, I've filed a bug report about using since_id with search 6 months ago after my client users complained about empty / no search results: http://bit.ly/since_id Is this bug fixed already? If not, how can we use since_id with the Search API so that it is giving us some results and not just an empty set? Also, I'm using a proxy for my users from China and have therefore used the user auth'ed version of the Search api (http:// api.twitter.com/1/search...) If I'm switching to search.twitter.com, will I run into API limits for my proxy then? Thanks for any help Ole @ mobileways.de / #Gravity Twitter Client for S60 Symbian -- http://twitter.com/janole On 28 Mai, 00:12, Taylor Singletary taylorsinglet...@twitter.com wrote: Hi Developers, A few quick points before I go into more detail: * For the Search API, you should *only* be usinghttp://search.twitter.comtoexecute search requests. *Not*http://api.twitter.com/1/searchor any other variation. * *Next week*, we plan to remove the erroneous, unsupported endpoint athttp://api.twitter.com/1/search * All REST requests to the API should use the fully qualified hostname and API version in URLs:http://api.twitter.com/1/*-- no other version is valid at this time. * All OAuth negotiation steps should be over SSL and also athttp://api.twitter.com-- but without a version. * Don't execute the same search query more often than every 20s and always use since_id on subsequent requests * Consider the streaming API if you're relying on search heavily to power your application *The Long-winded Approach* * * The only endpoint you should be using for search operations in the Twitter API today ishttp://search.twitter.com-- it doesn't require user authentication or OAuth -- simply identify yourself with a user-agent that is unique to your application. For those usinghttp://twitter.com/search,http://api.twitter.com/search, orhttp://api.twitter.com/1/search-- you've been doing it wrong :) Though we should have rejected traffic to that end point long ago to avoid confusion, it was never intended as a valid resource for search queries. Next week, we'll be properly closing off this end point to avoid further confusion. If you have code today that uses thehttp://api.twitter.comor http:/twitter.com domains to execute search requests, be sure and update your code for the proper end point. You can find the Search API documentation athttp://bit.ly/twitter-search-api Many users of the Search API are better served by using the Streaming API. If you use the search API to track the tweets of specific users, hashtags, or simple keyword queries, it is highly recommended that you use the Streaming API instead. You shouldn't issue the same request to the search API more frequently than once every 20 seconds -- if you issue the same query more frequently than that, you're in danger of getting blacklisted. In addition, if you find yourself repeating the same query frequently, be sure and make use of the since_id parameter on subsequent requests -- without it, you put undue stress on the search infrastructure and will also be in danger of blacklisting. While we're on the topic of using the proper endpoints, a general reminder about endpoints with the Twitter API: All REST resource requests, with the exception of Search, should be pointed athttp://api.twitter.com/1/*-- always use the api subdomain and specify the version number (1). No other version number will be accepted for the API at this time and your requests will fail if you provide a different string or integer. All OAuth negotiation steps should be over SSL athttps://api.twitter.com/oauth/*(https://api.twitter.com/oauth/request_token;, https://api.twitter.com/oauth/authorize;, https://api.twitter.com/oauth/access_token;, https://api.twitter.com/oauth/authenticate;) Let us know if you have any concerns about the removal of the unofficial/unsupported search end point. We don't want to break people, but we also don't want you using unofficial API calls with substandard and unpredictable responses. Thanks! Taylor Singletary Developer Advocate, Twitterhttp://twitter.com/episod
[twitter-dev] Re: Important Notice on Incorrect API Endpoints for Search, REST, OAuth (+ some general tips!)
Twitter, your since_id feature has been broken since October 2009, and it is STILL broken. And yet you warn us that not using it will result in blacklisting? Your search API is unreliable when since_id is used. Someone at Twitter mistakenly closed the bug in December but oh yes, it still exists, it still gets plenty of comments. Fix that before requiring it to be used. Unacceptable. http://code.google.com/p/twitter-api/issues/detail?id=1154 On May 27, 3:12 pm, Taylor Singletary taylorsinglet...@twitter.com wrote: Hi Developers, A few quick points before I go into more detail: * For the Search API, you should *only* be usinghttp://search.twitter.comtoexecute search requests. *Not*http://api.twitter.com/1/searchor any other variation. * *Next week*, we plan to remove the erroneous, unsupported endpoint athttp://api.twitter.com/1/search * All REST requests to the API should use the fully qualified hostname and API version in URLs:http://api.twitter.com/1/*-- no other version is valid at this time. * All OAuth negotiation steps should be over SSL and also athttp://api.twitter.com-- but without a version. * Don't execute the same search query more often than every 20s and always use since_id on subsequent requests * Consider the streaming API if you're relying on search heavily to power your application *The Long-winded Approach* * * The only endpoint you should be using for search operations in the Twitter API today ishttp://search.twitter.com-- it doesn't require user authentication or OAuth -- simply identify yourself with a user-agent that is unique to your application. For those usinghttp://twitter.com/search,http://api.twitter.com/search, orhttp://api.twitter.com/1/search-- you've been doing it wrong :) Though we should have rejected traffic to that end point long ago to avoid confusion, it was never intended as a valid resource for search queries. Next week, we'll be properly closing off this end point to avoid further confusion. If you have code today that uses thehttp://api.twitter.comor http:/twitter.com domains to execute search requests, be sure and update your code for the proper end point. You can find the Search API documentation athttp://bit.ly/twitter-search-api Many users of the Search API are better served by using the Streaming API. If you use the search API to track the tweets of specific users, hashtags, or simple keyword queries, it is highly recommended that you use the Streaming API instead. You shouldn't issue the same request to the search API more frequently than once every 20 seconds -- if you issue the same query more frequently than that, you're in danger of getting blacklisted. In addition, if you find yourself repeating the same query frequently, be sure and make use of the since_id parameter on subsequent requests -- without it, you put undue stress on the search infrastructure and will also be in danger of blacklisting. While we're on the topic of using the proper endpoints, a general reminder about endpoints with the Twitter API: All REST resource requests, with the exception of Search, should be pointed athttp://api.twitter.com/1/*-- always use the api subdomain and specify the version number (1). No other version number will be accepted for the API at this time and your requests will fail if you provide a different string or integer. All OAuth negotiation steps should be over SSL athttps://api.twitter.com/oauth/*(https://api.twitter.com/oauth/request_token;, https://api.twitter.com/oauth/authorize;, https://api.twitter.com/oauth/access_token;, https://api.twitter.com/oauth/authenticate;) Let us know if you have any concerns about the removal of the unofficial/unsupported search end point. We don't want to break people, but we also don't want you using unofficial API calls with substandard and unpredictable responses. Thanks! Taylor Singletary Developer Advocate, Twitterhttp://twitter.com/episod
[twitter-dev] Issue with posting to twitter: http://twitter.com/home?status=doesnotworkifyouarenotloggedin
Hi, It appears that if you are not logged in, and hit the following URL: http://twitter.com/home?status=doesnotworkifyouarenotloggedin, you lose the status you were trying to post. I'm very certain this used to work until a few days ago. Has something changed? Thanks for your help! Priyanka
[twitter-dev] Another Failed to validate oauth signature and token
I'm new to OAuth and the Twitter API and I'm trying to learn the nitty
gritty of the OAuth flow and therefore I am writing my own classes (in
PHP.) I'm on step one and I haven't been able to get a request_token
properly and I'm failing with the common error Failed to validate
oauth signature and token.
I'm hoping someone can point out the obvious of what I may be doing
wrong. Thanks in advance for any feedback / ideas. My application
works fine with the PHP library I downloaded and tried out, and I've
even replaced much of the code I wrote with snippets from the library
to see if I was simply doing something incorrectly.
My system time is up to date. I've tried generating timestamps based
on the UTC timezone and my local timezone.
Here's an example of my base signature string:
POSThttp%3A%2F%2Fapi.twitter.com%2Foauth
%2Frequest_tokenoauth_callback%3Dhttp%3A%2F%2Fmy.domain.net%2F~patrick
%2Foauth%2Ftwitter%2Fsuccess.php%26oauth_consumer_key
%3DMYCONSOMUERKEYHERE%26oauth_nonce
%3D1275027099%26oauth_signature_method%3DHMAC-SHA1%26oauth_timestamp
%3D1275027099%26oauth_version%3D1.0
I've tried using the md5 of unuiqe id for the nonce, and also the md5
of a timestamp (the example above is simply using a nonce that equals
the timestamp...all have still failed.
I'm signing it with:
private function get_signature(){
return base64_encode(hash_hmac('sha1', $this-
build_signature_base_string(), $this-consumer_secret . '', true));
}
My authorization header looks like this:
Authorization: OAuth oauth_consumer_key=MYCONSUMERKEYHERE,
oauth_nonce=1275025890, oauth_signature_method=HMAC-SHA1,
oauth_timestamp=1275025890, oauth_version=1.0,
oauth_signature=W1KcHPpYMdu3cPPz%2FyfSPcyhj7c%3D
I'm then using curl with the following options to request the page:
$ch = curl_init();
curl_setopt($ch, CURLOPT_URL,
'https://api.twitter.com/oauth/
request_token');
curl_setopt($ch, CURLOPT_HTTPHEADER,
$this-build_auth_header());
curl_setopt($ch, CURLOPT_HEADER, true);
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_POST, true);
return curl_exec($ch);
If it helps, the full response I'm getting back is:
HTTP/1.1 401 Unauthorized
Date: Fri, 28 May 2010 05:51:30 GMT
Server: hi
Status: 401 Unauthorized
X-Transaction: 1275025890-51043-4802
Last-Modified: Fri, 28 May 2010 05:51:30 GMT
X-Runtime: 0.00185
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=1.2.3.4.1275025890583471; path=/; expires=Fri, 04-Jun-10
05:51:30 GMT; domain=.twitter.com
Set-Cookie: guest_id=127502589058847976; path=/; expires=Sun, 27 Jun
2010 05:51:30 GMT
Set-Cookie:
_twitter_sess=BAh7CToRdHJhbnNfcHJvbXB0MDoPY3JlYXRlZF9hdGwrCBwdd90oAToHaWQi
%250AJWM2M2UwNTBlNmJlNjE1MDljYmI0YmVkOWU1M2VlZjUwIgpmbGFzaElDOidB
%250AY3Rpb25Db250cm9sbGVyOjpGbGFzaDo6Rmxhc2hIYXNoewAGOgpAdXNlZHsA--74c2e797b692435f46c95d28138b58d7a8467acb;
domain=.twitter.com; path=/
Vary: Accept-Encoding
Connection: close
Failed to validate oauth signature and token
Once again, I'm sorry for bothering you all with a relatively trivial
issue, but I greatly appreciate any help you can throw at me.
[twitter-dev] Re: What tools do you use?
Native API maybe. On 5月23日, 上午9时29分, roteva bernd.str...@gmail.com wrote: There is qoauth for example on githubhttp://github.com/ayoy/qoauth Bernd On Mar 31, 12:18 pm, Nigel Legg nigel.l...@gmail.com wrote: Working with QTwitLib in Qt on Windows. Developing desktop apps. Any one know whether there is a Qt lib for OAuth? Nigel. On 31 March 2010 16:59, Guille gui...@nianoniano.com wrote: Howdy! I script calls with PHP's Curl library and also user command-line (linux shell) curl command. I've seen some proxies mentioned. The one of my choice is: BurpProxy (@portswigger http://twitter.com/portswigger - http://portswigger.net/proxy/ ) I host my TwiPHPr library project at GitHub (@github http:// twitter.com/github -https://github.com/) I code using NetBeans (@netbeans http://twitter.com/netbeans - http://netbeans.org/) Whenever I do web applications I develop them using Symfony Framework (@symfony http://twitter.com/symfony -http://www.symfony-project.org/ ) On 30 ene, 21:55, Abraham Williams 4bra...@gmail.com wrote: Lets collect an awesome list of tools and applications we use to help develop with the Twitter API. I'll start the list with a couple that I use: Charles Proxy - @charlesproxy http://twitter.com/charlesproxy - http://www.charlesproxy.com/ Charles is an HTTP proxy / HTTP monitor / Reverse Proxy that enables a developer to view all of the HTTP and SSL / HTTPS traffic between their machine and the Internet. This includes requests, responses and the HTTP headers (which contain the cookies and caching information) Hurl - @hurlit http://twitter.com/hurlit -http://hurl.it/ Hurl makes HTTP requests. Enter a URL, set some headers, view the response, then share it with others. Perfect for demoing and debugging APIs. Hurl is also open source -http://defunkt.github.com/hurl/ TwitterOAuth PHP Library - @oauthlib http://twitter.com/oauthlib - http://github.com/abraham/twitteroauth The first PHP Library to support OAuth for Twitter's REST API. MIT licensed. GitHub - @github http://twitter.com/github -https://github.com/ GitHub is the easiest (and prettiest) way to participate in that collaboration: fork projects, send pull requests, monitor development, all with ease. What tools do you use while developing with the Twitter API? -- Abraham Williams | Community Advocate |http://abrah.am Project | Out Loud |http://outloud.labs.poseurtech.com This email is: [ ] shareable [x] ask first [ ] private. Sent from Seattle, WA, United States
[twitter-dev] 401 unauthorized error
Hi~ I'm developing the twitter application with Android. For posting twitpic data, I use Oauth echo, but I'v got 401 error. Could not authentication you. (header rejected by twitter) Oauth header POST /2/upload.xml HTTP 1.1 x-auth-service-provider: https://api.twitter.com/1/account/verify_credentials.xml x-verify-credentials-authorization: Oauth realm=http:// api.twitter.com, oauth_consumer_key=a, oauth_signature_method=HMAC-SHA1, oauth_timestamp=1212, oauth_nonce=123123, oauth_version=1.0, oauth_token=user_oauth_token . What is the problem? I have spent for a week. --;
[twitter-dev] Uploading videos to Twitter using OAuth
Hi, I am developing an iPhone app that uses Twitvid library for uploading videos to TwitVid. This library first authenticates the app using the user-name and password input parameters. Then it uploads the video. But, recently I switched to OAuth mechanism of authentication which leads to a web-page where user can enter the user-name and password. So, I cannot provide the input fields for user-name and password in my app for uploading video. Can someone help me out to solve this problem. Thanks and Regards, Deepa
[twitter-dev] Re: Deleted status still in JSON, not in XML
Hi Twitter API Team,
This looks like long standing issue in the actual API, Can any one
confirm this from your team and fix it.
I have seen this issue in 2009 Feb also.
On Apr 22, 1:50 pm, Ricky ri...@digitally-born.com wrote:
Has anyone seen this behavior before? Is this a once in a lifetime
event? I (still) haven't found any mention of this anywhere.
Ricky
On Apr 20, 2:47 pm, Ricky ri...@digitally-born.com wrote:
I've had a bug submitted by a user of the Twitterizer .NET library,
and it appears to be a possible bug with the Twitter API.
After destroying a status, the /users/show/screen_name.json result
still contained the destroyed status, while the /users/show/
screen_name.xml results (correctly, I think) contains the previous
status.
Below is the example, both from the user ronneylovely. The status
wow has been deleted.
Thanks in advance for any insight or attention you give,
Ricky
JSON (api.twitter.com/1/users/show/ronneylovely.json):
{favourites_count:1,created_at:Thu Apr 15 15:23:35 +
2010,profile_sidebar_fill_color:e0ff92,description:null,contributor
s_enabled:false,time_zone:null,status:
{in_reply_to_status_id:null,created_at:Mon Apr 19 22:05:12 +
2010,in_reply_to_user_id:null,truncated:false,source:web,favorite
d:false,id:
12478411850,in_reply_to_screen_name:null,text:wow},following:false,
geo_enabled:false,profile_sidebar_border_color:87bc44,url:null,ver
ified:false,profile_background_color:9ae4e8,location:null,profile_b
ackground_image_url:http://
s.twimg.com/a/1271213136/images/themes/theme1/
bg.png,profile_text_color:00,followers_count:
0,protected:false,profile_image_url:http://s.twimg.com/a/
1271213136/images/
default_profile_3_normal.png,notifications:false,profile_background_til
e:false,name:ronneylovely,friends_count:
4,profile_link_color:ff,screen_name:ronneylovely,id:
133348295,lang:en,statuses_count:2,utc_offset:null}
XML (api.twitter.com/1/users/show/ronneylovely.xml):
user
id133348295/id
nameronneylovely/name
screen_nameronneylovely/screen_name
location/location
description/description
profile_image_urlhttp://s.twimg.com/a/1271725794/images/
default_profile_3_normal.png/profile_image_url
url/url
protectedfalse/protected
followers_count0/followers_count
profile_background_color9ae4e8/profile_background_color
profile_text_color00/profile_text_color
profile_link_colorff/profile_link_color
profile_sidebar_fill_colore0ff92/profile_sidebar_fill_color
profile_sidebar_border_color87bc44/profile_sidebar_border_color
friends_count4/friends_count
created_atThu Apr 15 15:23:35 + 2010/created_at
favourites_count1/favourites_count
utc_offset/utc_offset
time_zone/time_zone
profile_background_image_urlhttp://s.twimg.com/a/1271725794/images/
themes/theme1/bg.png/profile_background_image_url
profile_background_tilefalse/profile_background_tile
notifications/notifications
geo_enabledfalse/geo_enabled
verifiedfalse/verified
following/following
statuses_count1/statuses_count
langen/lang
contributors_enabledfalse/contributors_enabled
status
created_atThu Apr 15 15:25:38 + 2010/created_at
id12228846134/id
texttesting this thing/text
sourceweb/source
truncatedfalse/truncated
in_reply_to_status_id/in_reply_to_status_id
in_reply_to_user_id/in_reply_to_user_id
favoritedfalse/favorited
in_reply_to_screen_name/in_reply_to_screen_name
geo/
coordinates/
place/
contributors/
/status
/user
--
Subscription
settings:http://groups.google.com/group/twitter-development-talk/subscribe?hl=en
[twitter-dev] Deleted status remains in JSON, not in XML
Hi Twitter API Team, I am able to reproduce this issue. Can you guys please confirm it and fix it. http://groups.google.com/group/twitter-development-talk/browse_thread/thread/dcc1486532858e04
[twitter-dev] Force mobile OAUTH ui?
Anyone know a way to get the mobile OAUTH ui from the desktop browser? Looks like they detect the browser and then swap the style sheets as oppose to redirecting to mobile.twitter.com/oauth/authorize (which dosnt exist) Maybe there is an undocumented parameter we can use? Something like: http://twitter.com/oauth/authorize?mobile=1oauth_token=123abc
[twitter-dev] Re: Issue with posting to twitter: http://twitter.com/home?status=doesnotworkifyouarenotloggedin
Hi Priyanka, Thanks. We're aware of the problem and it is being tracked as ticket 1650 [1] on the twitter-api issues log. 1. http://code.google.com/p/twitter-api/issues/detail?id=1650 Matt On May 27, 8:24 pm, newtothisworld priyankalut...@gmail.com wrote: Hi, It appears that if you are not logged in, and hit the following URL:http://twitter.com/home?status=doesnotworkifyouarenotloggedin, you lose the status you were trying to post. I'm very certain this used to work until a few days ago. Has something changed? Thanks for your help! Priyanka
[twitter-dev] Re: users.lookup() pulls by friendship date
Hey cballou, What is the actual API call you are making? I ask because the users/lookup.json method requires you pass it user ids for it to work. If you don't pass it any user ids or screen names you will told that no user matches the specified terms. The data is then returned in an undefined order. As nischalshetty said, this method can be used to request information about any user so the sort order is arbitrary. Are you getting results when you pass no IDs? Matt On May 27, 7:43 pm, nischalshetty nischalshett...@gmail.com wrote: So it's the same one that I was talking about. They haven't specified any sorting rules in the doc, are you sure about it? Before all that, I hope you know that the lookup API can be used to retrieve info about ANY twitter user. So it does not matter if that user is your friend. How will the sorting be applied then? -Nischal On May 27, 5:18 am, cballou ball...@gmail.com wrote: The link is: http://dev.twitter.com/doc/get/users/lookup It actually returns the full dataset for up to 100 users. The returned data is sorted by your newest friendship in descending order. This functionality is quite minimal and could definitely be expanded upon like I suggested above. I was just wondering if there were any possibly hidden parameters I could pass in to change the count, cursor position, etc. On May 26, 1:22 am, nischalshetty nischalshett...@gmail.com wrote: Are you talking about this -http://api.twitter.com/version/users/lookup.format The above API returns whatever ids you have passed. Am I missing something? -Nischal On May 26, 4:38 am, cballou ball...@gmail.com wrote: Nobody? On May 25, 12:14 pm, cballou ball...@gmail.com wrote: I really don't like the fact that calling users.lookup() returns the last 100 users I have friended. Is there a way to retrieve users in a more random fashion or with some kind of ordering (ascending/descending)? I'm looking for more optional parameters. Suppose, for instance, that I have 500 friends. I would not want to pull my last 100 friends when making this API call. I might want to, however, pull a random sampling of 100 of those friends. I may also want to pull a particular number of friends (i.e. imposing a limit on the request). I would propose that there be additional filtering parameters for this request: sort: asc/desc/random (default desc) limit: 1-100 (default 100) Can anybody clarify and expand upon this for me?
[twitter-dev] Re: Search spam??
I'm wondering whether the search is getting popular tweets mixed in (the default behavior) and that those are what you are seeing. Can you give an example of one or two of the searches that are doing this? Thanks, Matt On May 27, 2:19 pm, M. Edward (Ed) Borasky zn...@borasky- research.net wrote: I just noticed this today - may have been going on for a while, though. I'm logged in on twitter.com. I have a few saved searches for some friends - about four of them with different groups of friends. What's in the search term is, for example, screen name 1 OR screen name 2. The screen names appear without @ signs. One of these searches is returning tweets that don't match either of the two screen names! They are returning tweets from the two screen names *plus* some tweets that appear to be from people trying to get me to click on links. These tweets do *not* have the characteristics of a Promoted Tweet. They aren't showing up at the top of the search - they're showing up in time sequence order. Has someone figured out how to game the search? Is Twitter testing something and not telling us? When I search for sn1 OR sn2 I do *not* want to receive tweets like this! http://twitter.com/rx8mall/status/14859299274
[twitter-dev] Re: Social Graph Methods Page Size change?
Hi Miles, Which API method are you using. The preferred method for retrieving friends and followers is friends/ids [1] and followers/ids [2]. In both cases it is recommended that you add cursor=-1 to the end. Matt 1. http://dev.twitter.com/doc/get/friends/ids 2. http://dev.twitter.com/doc/get/followers/ids On May 27, 1:37 pm, Miles Parker milespar...@gmail.com wrote: I'm noticing now that page for friends and followers (for arbitrary user ids) are returning 100 users, not 5,000 as I'm seeing in the API docs. Is it my imagination that this has changed just in the last couple of days?
[twitter-dev] Re: Widget Search problem
Hi cfalar, This is a known bug and is being tracked as ticket 1404 [1]. Matt 1. http://code.google.com/p/twitter-api/issues/detail?id=1401 On May 27, 12:55 pm, cfalar carolfalard...@hotmail.com wrote: Hi, I have a problem with the Search widget. If i go on this pagehttp://twitter.com/goodies/widget_searchand type #habs OR attaquea5 on the search input, i got no result. If i take a look at the get parameter the q value is #habs+OR attaquea5. Look like something add the + sign. It always do that and its return no result.
Re: [twitter-dev] Re: Deleted status still in JSON, not in XML
I can reproduce this, and am taking a look now.
---Mark
http://twitter.com/mccv
On Fri, May 28, 2010 at 9:57 AM, Ronak ronakppa...@gmail.com wrote:
Hi Twitter API Team,
This looks like long standing issue in the actual API, Can any one
confirm this from your team and fix it.
I have seen this issue in 2009 Feb also.
On Apr 22, 1:50 pm, Ricky ri...@digitally-born.com wrote:
Has anyone seen this behavior before? Is this a once in a lifetime
event? I (still) haven't found any mention of this anywhere.
Ricky
On Apr 20, 2:47 pm, Ricky ri...@digitally-born.com wrote:
I've had a bug submitted by a user of the Twitterizer .NET library,
and it appears to be a possible bug with the Twitter API.
After destroying a status, the /users/show/screen_name.json result
still contained the destroyed status, while the /users/show/
screen_name.xml results (correctly, I think) contains the previous
status.
Below is the example, both from the user ronneylovely. The status
wow has been deleted.
Thanks in advance for any insight or attention you give,
Ricky
JSON (api.twitter.com/1/users/show/ronneylovely.json):
{favourites_count:1,created_at:Thu Apr 15 15:23:35 +
2010,profile_sidebar_fill_color:e0ff92,description:null,contributor
s_enabled:false,time_zone:null,status:
{in_reply_to_status_id:null,created_at:Mon Apr 19 22:05:12 +
2010,in_reply_to_user_id:null,truncated:false,source:web,favorite
d:false,id:
12478411850,in_reply_to_screen_name:null,text:wow},following:false,
geo_enabled:false,profile_sidebar_border_color:87bc44,url:null,ver
ified:false,profile_background_color:9ae4e8,location:null,profile_b
ackground_image_url:http://
s.twimg.com/a/1271213136/images/themes/theme1/
bg.png,profile_text_color:00,followers_count:
0,protected:false,profile_image_url:http://s.twimg.com/a/
1271213136/images/
default_profile_3_normal.png,notifications:false,profile_background_til
e:false,name:ronneylovely,friends_count:
4,profile_link_color:ff,screen_name:ronneylovely,id:
133348295,lang:en,statuses_count:2,utc_offset:null}
XML (api.twitter.com/1/users/show/ronneylovely.xml):
user
id133348295/id
nameronneylovely/name
screen_nameronneylovely/screen_name
location/location
description/description
profile_image_urlhttp://s.twimg.com/a/1271725794/images/
default_profile_3_normal.png/profile_image_url
url/url
protectedfalse/protected
followers_count0/followers_count
profile_background_color9ae4e8/profile_background_color
profile_text_color00/profile_text_color
profile_link_colorff/profile_link_color
profile_sidebar_fill_colore0ff92/profile_sidebar_fill_color
profile_sidebar_border_color87bc44/profile_sidebar_border_color
friends_count4/friends_count
created_atThu Apr 15 15:23:35 + 2010/created_at
favourites_count1/favourites_count
utc_offset/utc_offset
time_zone/time_zone
profile_background_image_urlhttp://s.twimg.com/a/1271725794/images/
themes/theme1/bg.png/profile_background_image_url
profile_background_tilefalse/profile_background_tile
notifications/notifications
geo_enabledfalse/geo_enabled
verifiedfalse/verified
following/following
statuses_count1/statuses_count
langen/lang
contributors_enabledfalse/contributors_enabled
status
created_atThu Apr 15 15:25:38 + 2010/created_at
id12228846134/id
texttesting this thing/text
sourceweb/source
truncatedfalse/truncated
in_reply_to_status_id/in_reply_to_status_id
in_reply_to_user_id/in_reply_to_user_id
favoritedfalse/favorited
in_reply_to_screen_name/in_reply_to_screen_name
geo/
coordinates/
place/
contributors/
/status
/user
--
Subscription
settings:http://groups.google.com/group/twitter-development-talk/subscribe?hl=en
Re: [twitter-dev] Re: Current TwitterOAuth API won't display authorization page
Try switching
$to-OAuthRequest( https://twitter.com/statuses/update.xml;, array('status'
= $expanded_txt, 'POST') );
to:
$to-format = 'xml';
$to-post( statuses/update, array('status' = $expanded_txt));
Abraham
On Tue, May 11, 2010 at 15:43, Jonathan jhsa...@jhsachs.com wrote:
I'm afraid I spoke to soon. Things are not quite working.
I am able to authorize tweeting through the new API, but I am not able
to tweet yet.
When I first tried, I got back a message from this tweet operation:
$to-OAuthRequest( https://twitter.com/statuses/update.xml;,
array('status' = $expanded_txt, 'POST') );
which said,
Warning: Missing argument 3 for TwitterOAuth::oAuthRequest(),
called in ... and defined in .../twitterOAuth.php on line 178
I looked at the code and concluded that the third parameter should be
NULL. I added that and got this from PHP:
Notice: Array to string conversion in .../OAuth.php/b on
line 373
and from the tweet call:
errorCould not authenticate you./error
Oauth.php lines 373 says
return strtoupper($this-http_method);
I traced the value in http_method back to the second parameter of
twitterOAuth::oAuthRequest. I saw that instead of returning an array
which contained, among other things, the scalar 'POST', the second
parameter should just be 'POST'.
Accordingly, I changed the call to:
$to-OAuthRequest( https://twitter.com/statuses/update.xml;,
'POST', NULL );
and got a return value that contained this:
errorClient must provide a 'status' parameter with a value./
error
...which makes perfect sense, since the status element of the array
contains the text of the tweet!
I'm not sure what's happening here. It appears that one part of the
code requires OAuthRequest's second parameter to be an array, and
another part requires it to be a scalar! I know that can't be so, but
I don't see what it wants. Again, I'm stymied by the lack of API
documentation.
--
Abraham Williams | Developer for hire | http://abrah.am
@abraham | http://projects.abrah.am | http://blog.abrah.am
This email is: [ ] shareable [x] ask first [ ] private.
[twitter-dev] Re: Important Notice on Incorrect API Endpoints for Search, REST, OAuth (+ some general tips!)
I just wanted to make everyone aware that this issue is open and being tracked [1]. Any progress or developments will be posted on that thread. If you are experiencing a problem with since_id I encourage you to read my comment [2]. Thank you, Matt 1. http://code.google.com/p/twitter-api/issues/detail?id=1154 2. http://code.google.com/p/twitter-api/issues/detail?id=1154#c19 On May 27, 5:24 pm, schammy scha...@gmail.com wrote: Twitter, your since_id feature has been broken since October 2009, and it is STILL broken. And yet you warn us that not using it will result in blacklisting? Your search API is unreliable when since_id is used. Someone at Twitter mistakenly closed the bug in December but oh yes, it still exists, it still gets plenty of comments. Fix that before requiring it to be used. Unacceptable. http://code.google.com/p/twitter-api/issues/detail?id=1154 On May 27, 3:12 pm, Taylor Singletary taylorsinglet...@twitter.com wrote: Hi Developers, A few quick points before I go into more detail: * For the Search API, you should *only* be usinghttp://search.twitter.comtoexecutesearch requests. *Not*http://api.twitter.com/1/searchorany other variation. * *Next week*, we plan to remove the erroneous, unsupported endpoint athttp://api.twitter.com/1/search * All REST requests to the API should use the fully qualified hostname and API version in URLs:http://api.twitter.com/1/*--no other version is valid at this time. * All OAuth negotiation steps should be over SSL and also athttp://api.twitter.com--but without a version. * Don't execute the same search query more often than every 20s and always use since_id on subsequent requests * Consider the streaming API if you're relying on search heavily to power your application *The Long-winded Approach* * * The only endpoint you should be using for search operations in the Twitter API today ishttp://search.twitter.com--it doesn't require user authentication or OAuth -- simply identify yourself with a user-agent that is unique to your application. For those usinghttp://twitter.com/search,http://api.twitter.com/search, orhttp://api.twitter.com/1/search--you've been doing it wrong :) Though we should have rejected traffic to that end point long ago to avoid confusion, it was never intended as a valid resource for search queries. Next week, we'll be properly closing off this end point to avoid further confusion. If you have code today that uses thehttp://api.twitter.comor http:/twitter.com domains to execute search requests, be sure and update your code for the proper end point. You can find the Search API documentation athttp://bit.ly/twitter-search-api Many users of the Search API are better served by using the Streaming API. If you use the search API to track the tweets of specific users, hashtags, or simple keyword queries, it is highly recommended that you use the Streaming API instead. You shouldn't issue the same request to the search API more frequently than once every 20 seconds -- if you issue the same query more frequently than that, you're in danger of getting blacklisted. In addition, if you find yourself repeating the same query frequently, be sure and make use of the since_id parameter on subsequent requests -- without it, you put undue stress on the search infrastructure and will also be in danger of blacklisting. While we're on the topic of using the proper endpoints, a general reminder about endpoints with the Twitter API: All REST resource requests, with the exception of Search, should be pointed athttp://api.twitter.com/1/*--always use the api subdomain and specify the version number (1). No other version number will be accepted for the API at this time and your requests will fail if you provide a different string or integer. All OAuth negotiation steps should be over SSL athttps://api.twitter.com/oauth/*(https://api.twitter.com/oauth/request_token;, https://api.twitter.com/oauth/authorize;, https://api.twitter.com/oauth/access_token;, https://api.twitter.com/oauth/authenticate;) Let us know if you have any concerns about the removal of the unofficial/unsupported search end point. We don't want to break people, but we also don't want you using unofficial API calls with substandard and unpredictable responses. Thanks! Taylor Singletary Developer Advocate, Twitterhttp://twitter.com/episod
[twitter-dev] Re: Entities not working?
I've retooled my app a bit to avoid using count=X in my REST requests, and I've been getting the entities very consistently. Is no one else having issues using 'count' along with 'include_entities'? On May 28, 12:23 pm, Ellsass cpa...@gmail.com wrote: Strangely, it's working along with the parameter since_id under some conditions. My web app initially loads home_timeline?count=100 (the app is in its infancy and only I use it, otherwise I'd be using since_id and a cache). Every three minutes thereafter, an ajax call gets new tweets using home_timeline?since_id=[id]include_entities=true. That works -- it retrieves the entities. However, if I manually refresh (i.e., call the exact same ajax function explicitly rather than wait for the setTimeout to do it), I get the error 500 page as the response, as described below. On May 27, 9:40 pm, Ellsass cpa...@gmail.com wrote: For most of the day I was getting the new entities just fine, but for the last hour or two my home_timeline XML request is met with the Something is technically wrong. page as the response. I am using PHP EpiTwitter. This works fine: $twitterInfo = $twitterObj-get_statusesHome_timeline(array(count = $numTweets)); This was working for most of the day, but not recently: $twitterInfo = $twitterObj-get_statusesHome_timeline(array(count = $numTweets , include_entities = true));
Re: [twitter-dev] What tools do you use?
php.net/oauth On Sat, Jan 30, 2010 at 12:55 PM, Abraham Williams 4bra...@gmail.com wrote: Lets collect an awesome list of tools and applications we use to help develop with the Twitter API. I'll start the list with a couple that I use: Charles Proxy - @charlesproxy - http://www.charlesproxy.com/ Charles is an HTTP proxy / HTTP monitor / Reverse Proxy that enables a developer to view all of the HTTP and SSL / HTTPS traffic between their machine and the Internet. This includes requests, responses and the HTTP headers (which contain the cookies and caching information) Hurl - @hurlit - http://hurl.it/ Hurl makes HTTP requests. Enter a URL, set some headers, view the response, then share it with others. Perfect for demoing and debugging APIs. Hurl is also open source - http://defunkt.github.com/hurl/ TwitterOAuth PHP Library - @oauthlib - http://github.com/abraham/twitteroauth The first PHP Library to support OAuth for Twitter's REST API. MIT licensed. GitHub - @github - https://github.com/ GitHub is the easiest (and prettiest) way to participate in that collaboration: fork projects, send pull requests, monitor development, all with ease. What tools do you use while developing with the Twitter API? -- Abraham Williams | Community Advocate | http://abrah.am Project | Out Loud | http://outloud.labs.poseurtech.com This email is: [ ] shareable [x] ask first [ ] private. Sent from Seattle, WA, United States
[twitter-dev] If your IP gets blacklisted
Hey guys, Wanted to share a few details about last nights experience in case anyone else gets hit with it. Hopefully it can save you a few hours troubleshooting if it happens to you. Favstar's IP address was blacklisted by twitter yesterday. When this occurs, they don't inform you of it. Instead, you start seeing percentage of your requests blocked. Not all of them, just some of them. For me it varied between the 50% and 80% range. In the way I do my logging, these appeared as timeouts, so at first I thought the API was suffering overload, and when @mccv told me there was no overload, I fell in to trap of trying to diagnose either what was wrong with my server, or what was wrong with the network in between. What I should have done, is ran a curl in verbose mode (-v). This tells you that your connections are being refused: ~/current: curl -i -u my_account:fuuu! http://api.twitter.com/1/account/rate_limit_status.json -v * About to connect() to api.twitter.com port 80 (#0) * Trying 128.242.240.157... Connection refused * Trying 168.143.161.29... Connection refused * Trying 168.143.162.45... Connection refused * Trying 128.121.146.109... connected snip correct/incorrect response When I tried this from another server, my connections were never refused. When I tried this from the blacklisted server, I would see something like the above. Sometimes I'd get a successful response, sometimes I'd get curl: (52) Empty reply from server which googling for is useless, and sometimes I'd get curl: (7) couldn't connect to host. If you'd like to see Twitter make a reasonable attempt to notify 3rd parties when they are blacklisted, please vote on this issue: http://code.google.com/p/twitter-api/issues/detail?id=1658 Cheers, Tim.
[twitter-dev] Re: users.lookup() pulls by friendship date
Matt, I'm passing individual screen names and/or ids. I understand the full functionality of this API method. My question is more of a feature request because the return data is not particularly useful for what I'm trying to do. Ideally I would want to pass a cursor parameter like many of the other API calls so I can sort over datasets of 100 results. Scenario: I would like to retrieve all specific user's followers screen names (not just 100 of the latest) in the fewest possible API calls. Ideally this would involve checking a next_cursor return variable from the json data. On May 28, 6:27 pm, themattharris thematthar...@twitter.com wrote: Hey cballou, What is the actual API call you are making? I ask because the users/lookup.json method requires you pass it user ids for it to work. If you don't pass it any user ids or screen names you will told that no user matches the specified terms. The data is then returned in an undefined order. As nischalshetty said, this method can be used to request information about any user so the sort order is arbitrary. Are you getting results when you pass no IDs? Matt On May 27, 7:43 pm, nischalshetty nischalshett...@gmail.com wrote: So it's the same one that I was talking about. They haven't specified any sorting rules in the doc, are you sure about it? Before all that, I hope you know that the lookup API can be used to retrieve info about ANY twitter user. So it does not matter if that user is your friend. How will the sorting be applied then? -Nischal On May 27, 5:18 am, cballou ball...@gmail.com wrote: The link is: http://dev.twitter.com/doc/get/users/lookup It actually returns the full dataset for up to 100 users. The returned data is sorted by your newest friendship in descending order. This functionality is quite minimal and could definitely be expanded upon like I suggested above. I was just wondering if there were any possibly hidden parameters I could pass in to change the count, cursor position, etc. On May 26, 1:22 am, nischalshetty nischalshett...@gmail.com wrote: Are you talking about this -http://api.twitter.com/version/users/lookup.format The above API returns whatever ids you have passed. Am I missing something? -Nischal On May 26, 4:38 am, cballou ball...@gmail.com wrote: Nobody? On May 25, 12:14 pm, cballou ball...@gmail.com wrote: I really don't like the fact that calling users.lookup() returns the last 100 users I have friended. Is there a way to retrieve users in a more random fashion or with some kind of ordering (ascending/descending)? I'm looking for more optional parameters. Suppose, for instance, that I have 500 friends. I would not want to pull my last 100 friends when making this API call. I might want to, however, pull a random sampling of 100 of those friends. I may also want to pull a particular number of friends (i.e. imposing a limit on the request). I would propose that there be additional filtering parameters for this request: sort: asc/desc/random (default desc) limit: 1-100 (default 100) Can anybody clarify and expand upon this for me?
Re: [twitter-dev] If your IP gets blacklisted
We're working on a project internally that will greatly reduce the number of false positives on blacklisting. Right now it's really tough to match up IPs and applications, and therefore difficult to figure out who we would contact about blacklisting. Once our internal project is complete we should have a pretty easy way to match IPs with apps, which should in turn allow us to be better about warning/notification when we do blacklist IPs. The troubleshooting steps you listed here are good ones in the meantime. ---Mark http://twitter.com/mccv On Fri, May 28, 2010 at 6:22 PM, Tim Haines tmhai...@gmail.com wrote: Hey guys, Wanted to share a few details about last nights experience in case anyone else gets hit with it. Hopefully it can save you a few hours troubleshooting if it happens to you. Favstar's IP address was blacklisted by twitter yesterday. When this occurs, they don't inform you of it. Instead, you start seeing percentage of your requests blocked. Not all of them, just some of them. For me it varied between the 50% and 80% range. In the way I do my logging, these appeared as timeouts, so at first I thought the API was suffering overload, and when @mccv told me there was no overload, I fell in to trap of trying to diagnose either what was wrong with my server, or what was wrong with the network in between. What I should have done, is ran a curl in verbose mode (-v). This tells you that your connections are being refused: ~/current: curl -i -u my_account:fuuu! http://api.twitter.com/1/account/rate_limit_status.json -v * About to connect() to api.twitter.com port 80 (#0) * Trying 128.242.240.157... Connection refused * Trying 168.143.161.29... Connection refused * Trying 168.143.162.45... Connection refused * Trying 128.121.146.109... connected snip correct/incorrect response When I tried this from another server, my connections were never refused. When I tried this from the blacklisted server, I would see something like the above. Sometimes I'd get a successful response, sometimes I'd get curl: (52) Empty reply from server which googling for is useless, and sometimes I'd get curl: (7) couldn't connect to host. If you'd like to see Twitter make a reasonable attempt to notify 3rd parties when they are blacklisted, please vote on this issue: http://code.google.com/p/twitter-api/issues/detail?id=1658 Cheers, Tim.
