[twitter-dev] Issues with parameters in API console
Hi, When using the Twitter API console at http://dev.twitter.com/console it seems support for query parameters is broken: 1. select GET /1/statuses/home_timeline.json 2. under Parameters and values put page and 4 3. press + Add a query parameter 4. press Send The result is always page 1 of the home timeline. Looking at the request I don't see any signs of a page query parameter. Is this a known issue? I tested with Firefox 3.6.6 and Google Chrome on Ubuntu Linux. Also, the documentation for home_timeline at http://dev.twitter.com/doc/get/statuses/home_timeline states there are pagination limits (see page parameter doc). I wasn't able to find any specific info in the FAQ; could someone point me to the details? Thanks, Mike
[twitter-dev] Updating profile image via API results in broken image on Twitter.com
Whenever we update someones profile image using the API (from Twibbon.com) it is resulting in a broken image on Twitter.com even though the API is returning a HTTP 200 OK. The request and response looks like: --REQUEST: http://api.twitter.com POST /1/account/update_profile_image.json HTTP/1.1 Authorization: OAuth oauth_consumer_key=cmrjngkKmoHNaSG1OfWFA,oauth_token=57184902- BgSM4dVrnqDsPyFXmU2lYwsAzb406dVWMQMU6YwWE,oauth_nonce=tvx5owtqfawild73,oauth_timestamp=1279107191,oauth_signature_method=HMAC- SHA1,oauth_signature=5GP911M9Ej %2FZV4O8VGRAU272aT8%3D,oauth_version=1.0 Content-Type: multipart/form-data; boundary=e750bd87-3bee-4a19-98e6-55fb254283ef --e750bd87-3bee-4a19-98e6-55fb254283ef Content-Disposition: file; name=image; filename=jpfette.png Content-Type: image/png [FILE DATA][System.Text.Latin1Encoding] --e750bd87-3bee-4a19-98e6-55fb254283ef-- --RESPONSE: http://api.twitter.com/1/account/update_profile_image.json HTTP/1.1 200 OK Date: Wed, 14 Jul 2010 11:33:12 GMT Server: hi Status: 200 OK X-Transaction: 1279107192-63482-30103 ETag: 23eefa77c91e270e9d96507216e06334 Last-Modified: Wed, 14 Jul 2010 11:33:12 GMT X-Runtime: 0.05593 Content-Type: application/json; charset=utf-8 Content-Length: 1332 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=84.19.234.238.1279107192043086; path=/; expires=Wed, 21- Jul-10 11:33:12 GMT; domain=.twitter.com,guest_id=127910719241063792; path=/; expires=Fri, 13 Aug 2010 11:33:12 GMT,lang=en; path=/,_twitter_sess=BAh7CToPY3JlYXRlZF9hdGwrCGPWutApAToRdHJhbnNfcHJvbXB0MDoHaWQi %250AJTFhNDgxMDkzYjk4NDhhZDkxOTNlNTM0YTE4YTM3OWM4IgpmbGFzaElDOidB %250AY3Rpb25Db250cm9sbGVyOjpGbGFzaDo6Rmxhc2hIYXNoewAGOgpAdXNlZHsA--1622471acd43e84d39724f9f168f573c7fc8de4a; domain=.twitter.com; path=/ Vary: Accept-Encoding Connection: close You can see the broken image on: http://twitter.com/jpfette As you can imagine this is causing us a serious problem at present, any help would be greatly appreciated. Thanks, Bob Founder Twibbon.com
[twitter-dev] Request token out from twitter
Hi,
I tried to do the request token out from basic, not using any
framework, like MGTwitter, or anything like that. I used objective C
for iPhone for development.
Things that still confused me is, I always get an error
{
NSErrorFailingURLKey = https://api.twitter.com/oauth/
request_token;
NSErrorFailingURLStringKey = https://api.twitter.com/oauth/
request_token;
NSUnderlyingError = Error Domain=kCFErrorDomainCFNetwork
Code=-1012 \The operation couldn\U2019t be completed.
(kCFErrorDomainCFNetwork error -1012.)\ UserInfo=0x783b940 {};
}
I assumed that it is because that the request has not reached your
server yet? cause I was expecting that i got the nice result, saying
that I have a problem with the authentication, or some sort? like
http://oauth.net/core/1.0/#auth_step1
If the request fails verification or is rejected for other reasons,
the Service Provider SHOULD respond with the appropriate response code
as defined in HTTP Response Codes (HTTP Response Codes). The Service
Provider MAY include some further details about why the request was
rejected in the HTTP response body as defined in Service Provider
Response Parameters (Service Provider Response Parameters).
That was from the OAuth documentation, and because I received an
error, not a error response, can I assume that the problem is in my
code?
NSMutableString *strings = [[NSMutableString alloc] init];
[strings appendString:@OAUTH ];
[strings appendString:@oauth_nonce=\];
[strings appendString:[signatures objectForKey:@oauth_nonce]];
[strings appendString:@\, oauth_callback=\];
[strings appendString:[signatures objectForKey:@oauth_callback]];
[strings appendString:@\, oauth_signature_method=\];
[strings appendString:[signatures
objectForKey:@oauth_signature_method]];
[strings appendString:@\, oauth_timestamp=\];
[strings appendString:[signatures objectForKey:@oauth_timestamp]];
[strings appendString:@\, oauth_consumer_key=\];
[strings appendString:[signatures
objectForKey:@oauth_consumer_key]];
[strings appendString:@\, oauth_signature=\];
[strings appendString:[string stringForURLEncoding]];
[strings appendString:@\, oauth_version=\];
[strings appendString:[signatures objectForKey:@oauth_version]];
[strings appendString:@\];
NSMutableURLRequest *req = [NSMutableURLRequest requestWithURL:url];
[req setHTTPMethod:@GET];
[req setValue:strings forHTTPHeaderField:@Authorization];
NSHTTPURLResponse *response = nil;
NSError *error = nil;
NSData *responseData = [NSURLConnection sendSynchronousRequest:req
returningResponse:response
error:error];
if (response ==nil)
NSLog(@%@, [error userInfo]);
else
{
NSLog(@REPONSE STATUS CODE %d, [response statusCode]);
NSLog(@CONTENT TYPE : %@, [[response allHeaderFields]
objectForKey:@Content-Type]);
NSString *payloadAsString = [[NSString alloc]
initWithData:responseData
encoding:NSUTF8StringEncoding];
NSLog(@CONTENT : %@, payloadAsString);
[payloadAsString release];
}
--
Regards,
Rendy Pranata
Re: [twitter-dev] Name search
Hey, We had some problems where users wouldn't show up in the index but this was fixed yesterday. There is more information on our help site: http://help.twitter.com/entries/60660-i-m-missing-from-find-people-search-fixed-known-issue Best, Matt On Tue, Jul 13, 2010 at 10:23 PM, M. Edward (Ed) Borasky zn...@borasky-research.net wrote: I've been experimenting with Name Search on twitter.com. I'm logged in, and when I enter some Twitter screen names in the search bar, for example, marshallk, I get a Name Results bar at the top of the results that says, Name results for marshallk. But when I enter some Twitter names, for example, znmeb, I don't get the Name Results. How does Search decide who gets a Name Results bar and who doesn't? -- M. Edward (Ed) Borasky http://borasky-research.net http://twitter.com/znmeb A mathematician is a device for turning coffee into theorems. - Paul Erdos -- Matt Harris Developer Advocate, Twitter http://twitter.com/themattharris
Re: [twitter-dev] Issues with parameters in API console
Hi Mike, Thanks for letting us know about this. It is a known bug and is being tracked on our issue tracker [1]. We don't have an eta for a fix so in the meantime we recommend you try using the twurl command line tool [2] or a service like Apigiee [3]. Best, Matt 1. http://code.google.com/p/twitter-api/issues/detail?id=1661 2. http://github.com/marcel/twurl 3. http://apigee.com/ On Wed, Jul 14, 2010 at 12:05 AM, Mike Mazur mma...@gmail.com wrote: Hi, When using the Twitter API console at http://dev.twitter.com/console it seems support for query parameters is broken: 1. select GET /1/statuses/home_timeline.json 2. under Parameters and values put page and 4 3. press + Add a query parameter 4. press Send The result is always page 1 of the home timeline. Looking at the request I don't see any signs of a page query parameter. Is this a known issue? I tested with Firefox 3.6.6 and Google Chrome on Ubuntu Linux. Also, the documentation for home_timeline at http://dev.twitter.com/doc/get/statuses/home_timeline states there are pagination limits (see page parameter doc). I wasn't able to find any specific info in the FAQ; could someone point me to the details? Thanks, Mike -- Matt Harris Developer Advocate, Twitter http://twitter.com/themattharris
[twitter-dev] API Service Disruptions
Please give us something credible to tell our users. users/show has been effectively down for the past 18 hours. I've beaten the Soccer World Cup excuse to a bloody pulp, but now it doesn't fly with my users any more. The SSL certificate thing is also wearing thin guys, especially since this the second time in quick succession. We all need something to tell our users. Telling them Twitter is falling apart is not an option.
Re: [twitter-dev] Request token out from twitter
Hi Randy,
We recommend you use an already created library to get OAuth working first.
That way you can see the calls being made, the sort of responses you should
be getting and giving you something to compare your code to. We have a list
of OAuth libraries in different languages (including objective C) on our
developer resources site: http://dev.twitter.com/pages/oauth_libraries
Best,
Matt
On Wed, Jul 14, 2010 at 6:52 AM, Rendy Pranata rendy.pran...@gmail.comwrote:
Hi,
I tried to do the request token out from basic, not using any
framework, like MGTwitter, or anything like that. I used objective C
for iPhone for development.
Things that still confused me is, I always get an error
{
NSErrorFailingURLKey = https://api.twitter.com/oauth/
request_token;
NSErrorFailingURLStringKey = https://api.twitter.com/oauth/
request_token;
NSUnderlyingError = Error Domain=kCFErrorDomainCFNetwork
Code=-1012 \The operation couldn\U2019t be completed.
(kCFErrorDomainCFNetwork error -1012.)\ UserInfo=0x783b940 {};
}
I assumed that it is because that the request has not reached your
server yet? cause I was expecting that i got the nice result, saying
that I have a problem with the authentication, or some sort? like
http://oauth.net/core/1.0/#auth_step1
If the request fails verification or is rejected for other reasons,
the Service Provider SHOULD respond with the appropriate response code
as defined in HTTP Response Codes (HTTP Response Codes). The Service
Provider MAY include some further details about why the request was
rejected in the HTTP response body as defined in Service Provider
Response Parameters (Service Provider Response Parameters).
That was from the OAuth documentation, and because I received an
error, not a error response, can I assume that the problem is in my
code?
NSMutableString *strings = [[NSMutableString alloc] init];
[strings appendString:@OAUTH ];
[strings appendString:@oauth_nonce=\];
[strings appendString:[signatures objectForKey:@oauth_nonce]];
[strings appendString:@\, oauth_callback=\];
[strings appendString:[signatures objectForKey:@oauth_callback]];
[strings appendString:@\, oauth_signature_method=\];
[strings appendString:[signatures
objectForKey:@oauth_signature_method]];
[strings appendString:@\, oauth_timestamp=\];
[strings appendString:[signatures objectForKey:@
oauth_timestamp]];
[strings appendString:@\, oauth_consumer_key=\];
[strings appendString:[signatures
objectForKey:@oauth_consumer_key]];
[strings appendString:@\, oauth_signature=\];
[strings appendString:[string stringForURLEncoding]];
[strings appendString:@\, oauth_version=\];
[strings appendString:[signatures objectForKey:@oauth_version]];
[strings appendString:@\];
NSMutableURLRequest *req = [NSMutableURLRequest requestWithURL:url];
[req setHTTPMethod:@GET];
[req setValue:strings forHTTPHeaderField:@Authorization];
NSHTTPURLResponse *response = nil;
NSError *error = nil;
NSData *responseData = [NSURLConnection sendSynchronousRequest:req
returningResponse:response
error:error];
if (response ==nil)
NSLog(@%@, [error userInfo]);
else
{
NSLog(@REPONSE STATUS CODE %d, [response statusCode]);
NSLog(@CONTENT TYPE : %@, [[response allHeaderFields]
objectForKey:@Content-Type]);
NSString *payloadAsString = [[NSString alloc]
initWithData:responseData
encoding:NSUTF8StringEncoding];
NSLog(@CONTENT : %@, payloadAsString);
[payloadAsString release];
}
--
Regards,
Rendy Pranata
--
Matt Harris
Developer Advocate, Twitter
http://twitter.com/themattharris
Re: [twitter-dev] API Service Disruptions
Hi Dewald, There were some lingering issues with the SSL certificates due to what appears to be a number of machines not receiving the re-deployed SSL certificates. This should work itself out in the early part of the day today. We are investigating issues with users/show -- could you please be more specific as to what issues you are seeing with users/show -- by down do you mean that it is throwing 500s, 401s, 400s, incomplete results, invalid results, delayed results? Meanwhile, we have dedicated teams focused on resolving numerous issues that have been plaguing the system lately and the fruits of their labor should be visible and realized steadily on an ongoing basis. We are continuing to monitor the progress of many deployed fixes, including the rate limiting issues that a great number were experiencing earlier this week and last -- on that front, things are looking much better. Taylor On Wed, Jul 14, 2010 at 8:42 AM, Dewald Pretorius dpr...@gmail.com wrote: Please give us something credible to tell our users. users/show has been effectively down for the past 18 hours. I've beaten the Soccer World Cup excuse to a bloody pulp, but now it doesn't fly with my users any more. The SSL certificate thing is also wearing thin guys, especially since this the second time in quick succession. We all need something to tell our users. Telling them Twitter is falling apart is not an option.
[twitter-dev] Re: Updating profile image via API results in broken image on Twitter.com
I see the same thing - a good response from the API, but the actual image is missing on the web pages. The file name is correctly processed and saved - but no image. If I upload the same image via the Settings, Profile page, everything works fine. These results are very consistent. I first observed the failure at 8 am MDT on 7/14/2010. By the way, I have never been able to upload a PNG via the API, only JPG or GIF. Ray Franklin Avionics Specialists LLC On Jul 14, 5:45 am, Bob movingforwa...@gmail.com wrote: Whenever we update someones profile image using the API (from Twibbon.com) it is resulting in a broken image on Twitter.com even though the API is returning a HTTP 200 OK. The request and response looks like: --REQUEST:http://api.twitter.com POST /1/account/update_profile_image.json HTTP/1.1 Authorization: OAuth oauth_consumer_key=cmrjngkKmoHNaSG1OfWFA,oauth_token=57184902- BgSM4dVrnqDsPyFXmU2lYwsAzb406dVWMQMU6YwWE,oauth_nonce=tvx5owtqfawild73,oauth_timestamp=1279107191,oauth_signature_method=HMAC- SHA1,oauth_signature=5GP911M9Ej %2FZV4O8VGRAU272aT8%3D,oauth_version=1.0 Content-Type: multipart/form-data; boundary=e750bd87-3bee-4a19-98e6-55fb254283ef --e750bd87-3bee-4a19-98e6-55fb254283ef Content-Disposition: file; name=image; filename=jpfette.png Content-Type: image/png [FILE DATA][System.Text.Latin1Encoding] --e750bd87-3bee-4a19-98e6-55fb254283ef-- --RESPONSE:http://api.twitter.com/1/account/update_profile_image.json HTTP/1.1 200 OK Date: Wed, 14 Jul 2010 11:33:12 GMT Server: hi Status: 200 OK X-Transaction: 1279107192-63482-30103 ETag: 23eefa77c91e270e9d96507216e06334 Last-Modified: Wed, 14 Jul 2010 11:33:12 GMT X-Runtime: 0.05593 Content-Type: application/json; charset=utf-8 Content-Length: 1332 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=84.19.234.238.1279107192043086; path=/; expires=Wed, 21- Jul-10 11:33:12 GMT; domain=.twitter.com,guest_id=127910719241063792; path=/; expires=Fri, 13 Aug 2010 11:33:12 GMT,lang=en; path=/,_twitter_sess=BAh7CToPY3JlYXRlZF9hdGwrCGPWutApAToRdHJhbnNfcHJvbXB0MDoHaWQi %250AJTFhNDgxMDkzYjk4NDhhZDkxOTNlNTM0YTE4YTM3OWM4IgpmbGFzaElDOidB %250AY3Rpb25Db250cm9sbGVyOjpGbGFzaDo6Rmxhc2hIYXNoewAGOgpAdXNlZHsA--1622471acd43e84d39724f9f168f573c7fc8de4a; domain=.twitter.com; path=/ Vary: Accept-Encoding Connection: close You can see the broken image on: http://twitter.com/jpfette As you can imagine this is causing us a serious problem at present, any help would be greatly appreciated. Thanks, Bob Founder Twibbon.com
[twitter-dev] Re: Updating profile image via API results in broken image on Twitter.com
Thanks @RayF glad to know we're not alone in the wilderness here. Our entire service is based around this function so as you can imagine our users are screaming loudly at present. What you describe is almost exactly the same as we are seeing other than the fact we are usually able to upload PNG images. To reiterate: Calls to update_profile_image return a 200 OK Images uploaded to Amazon S3 by Twitter When the new image is shown on profiles it is broken When trying to view one of these images in a browser e.g: http://a0.twimg.com/profile_images/1078075804/8e9ccddf-ccd0-4ca2-9b66-8eea6dab27e5_bigger.png Firefox reports The image cannot be displayed becuase it contains errors IE reports a 403 (access denied) Looking at the HTTP request for the image using Fiddler shows that S3 is returning: ?xml version=1.0 encoding=UTF-8? ErrorCodeAccessDenied/CodeMessageAccess Denied/ MessageRequestId44DCE9951E7DD003/ RequestIdHostIdNhYnE6GUTSxSl8Ku3/ gCZvUNeMEhcbB8rbAg7qhbqqjaYDZCsnWnUryg8w16qvNh/HostId/Error Which can sometimes happen if the ACL permissions are set incorrectly (or at least not to public) on S3. I've not heard anything from Twitter yet on the issue, looks like they have their hands somewhat full at the moment. Thanks, Bob On Jul 14, 5:47 pm, RayF rfrank...@airportview.net wrote: I see the same thing - a good response from the API, but the actual image is missing on the web pages. The file name is correctly processed and saved - but no image. If I upload the same image via the Settings, Profile page, everything works fine. These results are very consistent. I first observed the failure at 8 am MDT on 7/14/2010. By the way, I have never been able to upload a PNG via the API, only JPG or GIF. Ray Franklin Avionics Specialists LLC On Jul 14, 5:45 am, Bob movingforwa...@gmail.com wrote: Whenever we update someones profile image using the API (from Twibbon.com) it is resulting in a broken image on Twitter.com even though the API is returning a HTTP 200 OK. The request and response looks like: --REQUEST:http://api.twitter.com POST /1/account/update_profile_image.json HTTP/1.1 Authorization: OAuth oauth_consumer_key=cmrjngkKmoHNaSG1OfWFA,oauth_token=57184902- BgSM4dVrnqDsPyFXmU2lYwsAzb406dVWMQMU6YwWE,oauth_nonce=tvx5owtqfawild73,oauth_timestamp=1279107191,oauth_signature_method=HMAC- SHA1,oauth_signature=5GP911M9Ej %2FZV4O8VGRAU272aT8%3D,oauth_version=1.0 Content-Type: multipart/form-data; boundary=e750bd87-3bee-4a19-98e6-55fb254283ef --e750bd87-3bee-4a19-98e6-55fb254283ef Content-Disposition: file; name=image; filename=jpfette.png Content-Type: image/png [FILE DATA][System.Text.Latin1Encoding] --e750bd87-3bee-4a19-98e6-55fb254283ef-- --RESPONSE:http://api.twitter.com/1/account/update_profile_image.json HTTP/1.1 200 OK Date: Wed, 14 Jul 2010 11:33:12 GMT Server: hi Status: 200 OK X-Transaction: 1279107192-63482-30103 ETag: 23eefa77c91e270e9d96507216e06334 Last-Modified: Wed, 14 Jul 2010 11:33:12 GMT X-Runtime: 0.05593 Content-Type: application/json; charset=utf-8 Content-Length: 1332 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=84.19.234.238.1279107192043086; path=/; expires=Wed, 21- Jul-10 11:33:12 GMT; domain=.twitter.com,guest_id=127910719241063792; path=/; expires=Fri, 13 Aug 2010 11:33:12 GMT,lang=en; path=/,_twitter_sess=BAh7CToPY3JlYXRlZF9hdGwrCGPWutApAToRdHJhbnNfcHJvbXB0MDoHaWQi %250AJTFhNDgxMDkzYjk4NDhhZDkxOTNlNTM0YTE4YTM3OWM4IgpmbGFzaElDOidB %250AY3Rpb25Db250cm9sbGVyOjpGbGFzaDo6Rmxhc2hIYXNoewAGOgpAdXNlZHsA--1622471acd43e84d39724f9f168f573c7fc8de4a; domain=.twitter.com; path=/ Vary: Accept-Encoding Connection: close You can see the broken image on: http://twitter.com/jpfette As you can imagine this is causing us a serious problem at present, any help would be greatly appreciated. Thanks, Bob Founder Twibbon.com
Re: [twitter-dev] Re: Updating profile image via API results in broken image on Twitter.com
Thanks for bringing this to our attention. It's definately not the correct behavior so we'll get somebody looking into this today. I've noticed uploading avatars through the website seems to be working fine so the issue seems isolated to the REST API. I have filed a ticket on our issue tracker [1] which we'll update with any news and recommend you go there and star the issue so you get the email notifications. Best, Matt 1. http://code.google.com/p/twitter-api/issues/list?thanks=1745 On Wed, Jul 14, 2010 at 10:02 AM, Bob movingforwa...@gmail.com wrote: Thanks @RayF glad to know we're not alone in the wilderness here. Our entire service is based around this function so as you can imagine our users are screaming loudly at present. What you describe is almost exactly the same as we are seeing other than the fact we are usually able to upload PNG images. To reiterate: Calls to update_profile_image return a 200 OK Images uploaded to Amazon S3 by Twitter When the new image is shown on profiles it is broken When trying to view one of these images in a browser e.g: http://a0.twimg.com/profile_images/1078075804/8e9ccddf-ccd0-4ca2-9b66-8eea6dab27e5_bigger.png Firefox reports The image cannot be displayed becuase it contains errors IE reports a 403 (access denied) Looking at the HTTP request for the image using Fiddler shows that S3 is returning: ?xml version=1.0 encoding=UTF-8? ErrorCodeAccessDenied/CodeMessageAccess Denied/ MessageRequestId44DCE9951E7DD003/ RequestIdHostIdNhYnE6GUTSxSl8Ku3/ gCZvUNeMEhcbB8rbAg7qhbqqjaYDZCsnWnUryg8w16qvNh/HostId/Error Which can sometimes happen if the ACL permissions are set incorrectly (or at least not to public) on S3. I've not heard anything from Twitter yet on the issue, looks like they have their hands somewhat full at the moment. Thanks, Bob On Jul 14, 5:47 pm, RayF rfrank...@airportview.net wrote: I see the same thing - a good response from the API, but the actual image is missing on the web pages. The file name is correctly processed and saved - but no image. If I upload the same image via the Settings, Profile page, everything works fine. These results are very consistent. I first observed the failure at 8 am MDT on 7/14/2010. By the way, I have never been able to upload a PNG via the API, only JPG or GIF. Ray Franklin Avionics Specialists LLC On Jul 14, 5:45 am, Bob movingforwa...@gmail.com wrote: Whenever we update someones profile image using the API (from Twibbon.com) it is resulting in a broken image on Twitter.com even though the API is returning a HTTP 200 OK. The request and response looks like: --REQUEST:http://api.twitter.com POST /1/account/update_profile_image.json HTTP/1.1 Authorization: OAuth oauth_consumer_key=cmrjngkKmoHNaSG1OfWFA,oauth_token=57184902- BgSM4dVrnqDsPyFXmU2lYwsAzb406dVWMQMU6YwWE,oauth_nonce=tvx5owtqfawild73,oauth_timestamp=1279107191,oauth_signature_method=HMAC- SHA1,oauth_signature=5GP911M9Ej %2FZV4O8VGRAU272aT8%3D,oauth_version=1.0 Content-Type: multipart/form-data; boundary=e750bd87-3bee-4a19-98e6-55fb254283ef --e750bd87-3bee-4a19-98e6-55fb254283ef Content-Disposition: file; name=image; filename=jpfette.png Content-Type: image/png [FILE DATA][System.Text.Latin1Encoding] --e750bd87-3bee-4a19-98e6-55fb254283ef-- --RESPONSE:http://api.twitter.com/1/account/update_profile_image.json HTTP/1.1 200 OK Date: Wed, 14 Jul 2010 11:33:12 GMT Server: hi Status: 200 OK X-Transaction: 1279107192-63482-30103 ETag: 23eefa77c91e270e9d96507216e06334 Last-Modified: Wed, 14 Jul 2010 11:33:12 GMT X-Runtime: 0.05593 Content-Type: application/json; charset=utf-8 Content-Length: 1332 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=84.19.234.238.1279107192043086; path=/; expires=Wed, 21- Jul-10 11:33:12 GMT; domain=.twitter.com,guest_id=127910719241063792; path=/; expires=Fri, 13 Aug 2010 11:33:12 GMT,lang=en; path=/,_twitter_sess=BAh7CToPY3JlYXRlZF9hdGwrCGPWutApAToRdHJhbnNfcHJvbXB0MDoHaWQi %250AJTFhNDgxMDkzYjk4NDhhZDkxOTNlNTM0YTE4YTM3OWM4IgpmbGFzaElDOidB %250AY3Rpb25Db250cm9sbGVyOjpGbGFzaDo6Rmxhc2hIYXNoewAGOgpAdXNlZHsA--1622471acd43e84d39724f9f168f573c7fc8de4a; domain=.twitter.com; path=/ Vary: Accept-Encoding Connection: close You can see the broken image on: http://twitter.com/jpfette As you can imagine this is causing us a serious problem at present, any help would be greatly appreciated. Thanks, Bob Founder Twibbon.com -- Matt Harris Developer Advocate, Twitter http://twitter.com/themattharris
[twitter-dev] Re: Updating profile image via API results in broken image on Twitter.com
Thanks Matt, I have added what we know to the ticket. Will update if we find anything else. On Jul 14, 6:25 pm, Matt Harris thematthar...@twitter.com wrote: Thanks for bringing this to our attention. It's definately not the correct behavior so we'll get somebody looking into this today. I've noticed uploading avatars through the website seems to be working fine so the issue seems isolated to the REST API. I have filed a ticket on our issue tracker [1] which we'll update with any news and recommend you go there and star the issue so you get the email notifications. Best, Matt 1.http://code.google.com/p/twitter-api/issues/list?thanks=1745 On Wed, Jul 14, 2010 at 10:02 AM, Bob movingforwa...@gmail.com wrote: Thanks @RayF glad to know we're not alone in the wilderness here. Our entire service is based around this function so as you can imagine our users are screaming loudly at present. What you describe is almost exactly the same as we are seeing other than the fact we are usually able to upload PNG images. To reiterate: Calls to update_profile_image return a 200 OK Images uploaded to Amazon S3 by Twitter When the new image is shown on profiles it is broken When trying to view one of these images in a browser e.g: http://a0.twimg.com/profile_images/1078075804/8e9ccddf-ccd0-4ca2-9b66... Firefox reports The image cannot be displayed becuase it contains errors IE reports a 403 (access denied) Looking at the HTTP request for the image using Fiddler shows that S3 is returning: ?xml version=1.0 encoding=UTF-8? ErrorCodeAccessDenied/CodeMessageAccess Denied/ MessageRequestId44DCE9951E7DD003/ RequestIdHostIdNhYnE6GUTSxSl8Ku3/ gCZvUNeMEhcbB8rbAg7qhbqqjaYDZCsnWnUryg8w16qvNh/HostId/Error Which can sometimes happen if the ACL permissions are set incorrectly (or at least not to public) on S3. I've not heard anything from Twitter yet on the issue, looks like they have their hands somewhat full at the moment. Thanks, Bob On Jul 14, 5:47 pm, RayF rfrank...@airportview.net wrote: I see the same thing - a good response from the API, but the actual image is missing on the web pages. The file name is correctly processed and saved - but no image. If I upload the same image via the Settings, Profile page, everything works fine. These results are very consistent. I first observed the failure at 8 am MDT on 7/14/2010. By the way, I have never been able to upload a PNG via the API, only JPG or GIF. Ray Franklin Avionics Specialists LLC On Jul 14, 5:45 am, Bob movingforwa...@gmail.com wrote: Whenever we update someones profile image using the API (from Twibbon.com) it is resulting in a broken image on Twitter.com even though the API is returning a HTTP 200 OK. The request and response looks like: --REQUEST:http://api.twitter.com POST /1/account/update_profile_image.json HTTP/1.1 Authorization: OAuth oauth_consumer_key=cmrjngkKmoHNaSG1OfWFA,oauth_token=57184902- BgSM4dVrnqDsPyFXmU2lYwsAzb406dVWMQMU6YwWE,oauth_nonce=tvx5owtqfawild73,oauth_timestamp=1279107191,oauth_signature_method=HMAC- SHA1,oauth_signature=5GP911M9Ej %2FZV4O8VGRAU272aT8%3D,oauth_version=1.0 Content-Type: multipart/form-data; boundary=e750bd87-3bee-4a19-98e6-55fb254283ef --e750bd87-3bee-4a19-98e6-55fb254283ef Content-Disposition: file; name=image; filename=jpfette.png Content-Type: image/png [FILE DATA][System.Text.Latin1Encoding] --e750bd87-3bee-4a19-98e6-55fb254283ef-- --RESPONSE:http://api.twitter.com/1/account/update_profile_image.json HTTP/1.1 200 OK Date: Wed, 14 Jul 2010 11:33:12 GMT Server: hi Status: 200 OK X-Transaction: 1279107192-63482-30103 ETag: 23eefa77c91e270e9d96507216e06334 Last-Modified: Wed, 14 Jul 2010 11:33:12 GMT X-Runtime: 0.05593 Content-Type: application/json; charset=utf-8 Content-Length: 1332 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=84.19.234.238.1279107192043086; path=/; expires=Wed, 21- Jul-10 11:33:12 GMT; domain=.twitter.com,guest_id=127910719241063792; path=/; expires=Fri, 13 Aug 2010 11:33:12 GMT,lang=en; path=/,_twitter_sess=BAh7CToPY3JlYXRlZF9hdGwrCGPWutApAToRdHJhbnNfcHJvbXB0MDoHaWQi %250AJTFhNDgxMDkzYjk4NDhhZDkxOTNlNTM0YTE4YTM3OWM4IgpmbGFzaElDOidB %250AY3Rpb25Db250cm9sbGVyOjpGbGFzaDo6Rmxhc2hIYXNoewAGOgpAdXNlZHsA--1622471acd43e84d39724f9f168f573c7fc8de4a; domain=.twitter.com; path=/ Vary: Accept-Encoding Connection: close You can see the broken image on: http://twitter.com/jpfette As you can imagine this is causing us a serious problem at present, any help would be greatly appreciated. Thanks, Bob Founder Twibbon.com -- Matt Harris Developer Advocate,
Re: [twitter-dev] API Service Disruptions
LOL On Wed, Jul 14, 2010 at 8:42 AM, Dewald Pretorius dpr...@gmail.com wrote: Please give us something credible to tell our users. users/show has been effectively down for the past 18 hours. I've beaten the Soccer World Cup excuse to a bloody pulp, but now it doesn't fly with my users any more. The SSL certificate thing is also wearing thin guys, especially since this the second time in quick succession. We all need something to tell our users. Telling them Twitter is falling apart is not an option. -- Dale
[twitter-dev] Re: API Service Disruptions
Why not? I tell my users that all the time, if it's the truth. What benefit is there in lying to your users? On Jul 14, 11:42 am, Dewald Pretorius dpr...@gmail.com wrote: We all need something to tell our users. Telling them Twitter is falling apart is not an option.
[twitter-dev] Re: Search Users Per Location
I built TweepSearch.com to do this. Example: http://tweepsearch.com/search?query=name:joe+location:montrealcommit=Do+Your+Thing! Your milage may vary - the site is definitely slow at the moment and somewhat out-of-date. Damon On Jul 13, 2:28 pm, PhilGo20 gauvin.phili...@gmail.com wrote: anyone ? On 29 juin, 16:20, PhilGo20 gauvin.phili...@gmail.com wrote: Is there a way to run a query returning Users around a particular location based on the location specified in their profile (returns all user with name=joe in montreal ? Or is the only way is to use the user/search method and filter out the results set ?
[twitter-dev] SPAM tweets from API, need help!
I think there is some problem. I have an account FriendCaller on twitter (twitter.com/friendcaller), and some tweets were being sent through API (clicking the API brings me here. These tweets are related to some shopping stuff. Tweets go like this: I put in my email and got a free $1000 best buy gift card! When I search on google for this exact string with quotes, I saw http://buzztter.com/en/k/email which shows the same tweet tweeted by many users, some profiles even with a very few followers, so I think its not the job of the 'free following' websites. There seem to be some very severe problem, for which I need a solution asap, because I cannot delete the tweets. It comes again and again itself. Help please!
[twitter-dev] statuses/update usage Replying a tweet
i trying to use statuses/update API function replying a tweet and
isnt works
//--
$_SESSION['tmptxt'] = Test Text;
$_SESSION['Reply'] = 18518815514;
$twittuser = ($connection-post('statuses/update', array('status' =
$_SESSION['tmptxt'], 'in_reply_to_status_id' = $_SESSION['Reply'])));
//---
is this the correct usage?
Re: [twitter-dev] Can't retrieve requestToken because of a Redirection
Hi Mounir, Can you detail step-by-step the full URLs and OAuth headers/query string parameters you are using throughout these steps? This should all be consistently achievable if you're using all the right end points. Taylor On Tue, Jul 13, 2010 at 1:46 AM, Mounir Regragui reg.mou...@gmail.comwrote: Hello everybody! So I'm developping an application on Android that will include some Twitter features. But I have some trouble retrieving the requestToken on OAuth. Everything works just fine on the emulator, but on actual devices I can't retrieve the requestToken for a simple reason. From the emulator, I get my response containing the requestToken and the secret, so I can fetch these informations. But on actual devices, I do not receive the string containing the secret and token, but i get a HTML page, redirecting me to m.twitter.com : htmlbodyYou are being a href=http:// mobile.twitter.comredirected/a./body/html I really need not to be redirected to get my informations, as I'm not running the request token process from a browser, but from and android application. Plus, the redirection to mobile.twitter.com is really NOT what I'm trying to achieve ^^ Any thoughts. I'd be grateful if someone could help me. If you need additional informations, please feel free to ask.
[twitter-dev] Get Twitter replies since
Perhaps Im not understanding this correctly but I am using the Twitter API to grab the replies from my twitter account. The problem is I dont want to grab the same ones so Im trying to use the since variable but no matter what value I use for the since variable in the url it always comes back with the same replies. For example: http://twitter.com/statuses/replies.xml?since=Tue%2C+27+Mar+2011+22%3A55%3A48+GMT I did this as a test, I was assuming the since variable meant show all replies that have been added since Tues March 11 2011. If that is correct then it should come back with 0 results correct? Well right now it is coming back with the same results as if I am not using the since variable. Anyone point me in the right direction?
[twitter-dev] Re: User protected account privacy - API terms
Hi Furkan, Public information is public. If someone without a Twitter account can view that information on a user's Twitter profile, or if the same information can be returned from an unauthenticated API call, it's considered public information and you may display it. Twitter does not require certain display conventions to indicate that the information comes from a protected account, but as you may notice, we use a lock icon on protected accounts. Brian Sutorius Twitter API Policy On Jul 11, 3:02 pm, Furkan Kuru furkank...@gmail.com wrote: I have read the terms of service (https://twitter.com/tos) and api rules. But it is not clear whether we can publish a protected account's profile information as shown in their profile page. (only screen_name, name, website, bio, follower, friends count) with a proper way as twitter specifies (i.e twitter icon, screen name) We will add a filter for protected accounts if we do not have right to display basic user information for protected users. -- Furkan Kuru
Re: [twitter-dev] statuses/update usage Replying a tweet
You have to include the@ sceen_name of the user you are replying to in the
text of the status.
On Jul 14, 2010 12:45 PM, lu5ceh ignacio.santo...@gmail.com wrote:
i trying to use statuses/update API function replying a tweet and
isnt works
//--
$_SESSION['tmptxt'] = Test Text;
$_SESSION['Reply'] = 18518815514;
$twittuser = ($connection-post('statuses/update', array('status' =
$_SESSION['tmptxt'], 'in_reply_to_status_id' = $_SESSION['Reply'])));
//---
is this the correct usage?
Re: [twitter-dev] Re: User protected account privacy - API terms
Thank you for clarification Brian. On Thu, Jul 15, 2010 at 12:02 AM, Brian Sutorius bsutor...@twitter.comwrote: Hi Furkan, Public information is public. If someone without a Twitter account can view that information on a user's Twitter profile, or if the same information can be returned from an unauthenticated API call, it's considered public information and you may display it. Twitter does not require certain display conventions to indicate that the information comes from a protected account, but as you may notice, we use a lock icon on protected accounts. Brian Sutorius Twitter API Policy On Jul 11, 3:02 pm, Furkan Kuru furkank...@gmail.com wrote: I have read the terms of service (https://twitter.com/tos) and api rules. But it is not clear whether we can publish a protected account's profile information as shown in their profile page. (only screen_name, name, website, bio, follower, friends count) with a proper way as twitter specifies (i.e twitter icon, screen name) We will add a filter for protected accounts if we do not have right to display basic user information for protected users. -- Furkan Kuru -- Furkan Kuru
[twitter-dev] Re: API Service Disruptions
Because things may not be really falling apart internally, even though it may appear that way from the outside. On Jul 14, 2:59 pm, Dossy Shiobara do...@panoptic.com wrote: Why not? I tell my users that all the time, if it's the truth. What benefit is there in lying to your users? On Jul 14, 11:42 am, Dewald Pretorius dpr...@gmail.com wrote: We all need something to tell our users. Telling them Twitter is falling apart is not an option.
[twitter-dev] Oauth rate status?
In using the account rate status call, I only seem to get the basic auth status back of 150 left. Where can I get the oauth status (the 350)? John
Re: [twitter-dev] Oauth rate status?
Hi, On Thu, Jul 15, 2010 at 05:52, johnw john.we...@gmail.com wrote: In using the account rate status call, I only seem to get the basic auth status back of 150 left. Where can I get the oauth status (the 350)? You need to authenticate with Twitter using OAuth. See the Authentication section of the documentation at http://dev.twitter.com/doc for details. HTH, Mike
Re: [twitter-dev] Issues with parameters in API console
Hi Matt, Thanks for the reply, I got twurl set up. Any thoughts on the second question in my email? Also, the documentation for home_timeline at http://dev.twitter.com/doc/get/statuses/home_timeline states there are pagination limits (see page parameter doc). I wasn't able to find any specific info in the FAQ; could someone point me to the details? I notice that only the first 40 pages contain tweets, any request with page 40 returns an empty array of statuses. Is this a documented limitation? Does it change over time? Thanks, Mike On Wed, Jul 14, 2010 at 23:38, Matt Harris thematthar...@twitter.com wrote: Hi Mike, Thanks for letting us know about this. It is a known bug and is being tracked on our issue tracker [1]. We don't have an eta for a fix so in the meantime we recommend you try using the twurl command line tool [2] or a service like Apigiee [3]. Best, Matt 1. http://code.google.com/p/twitter-api/issues/detail?id=1661 2. http://github.com/marcel/twurl 3. http://apigee.com/ On Wed, Jul 14, 2010 at 12:05 AM, Mike Mazur mma...@gmail.com wrote: Hi, When using the Twitter API console at http://dev.twitter.com/console it seems support for query parameters is broken: 1. select GET /1/statuses/home_timeline.json 2. under Parameters and values put page and 4 3. press + Add a query parameter 4. press Send The result is always page 1 of the home timeline. Looking at the request I don't see any signs of a page query parameter. Is this a known issue? I tested with Firefox 3.6.6 and Google Chrome on Ubuntu Linux. Also, the documentation for home_timeline at http://dev.twitter.com/doc/get/statuses/home_timeline states there are pagination limits (see page parameter doc). I wasn't able to find any specific info in the FAQ; could someone point me to the details? Thanks, Mike -- Matt Harris Developer Advocate, Twitter http://twitter.com/themattharris
[twitter-dev] Re: wating for whitelist confirmation for over a week
Dear David and Tim - Thank much for your clarifying that. I appreciate that! I guess I need to wait a bit longer. On Jul 13, 5:49 am, David dtran...@gmail.com wrote: Hey hkimscll, I think you just need to be patient - you'll get an email when they approve your request. From the API Announce List: Ryan Sarver rsar...@twitter.com Jul 07 07:18AM -0700 ^ I wanted to email everyone and give notice that we are going to be holding off on approving any additional whitelist requests until after the World Cup is over. We actually paused this last week, so if you haven't gotten a response, this is why. It will take us a while to get through the backlog after the World Cup, so please be patient and don't reapply as it just makes it more difficult to suss through the requests. Please let me know if you have any questions. Best, Ryan On Jul 11, 8:47 am, hkimscil hkims...@gmail.com wrote: I have been waiting for being whitelisted over a week period. Should I write Twitter about the confirmation? Is there anyway to check the status of my request? Thanks!
[twitter-dev] Re: Profile image uploads not working (using twitter-async)
I have a similar problem. I am trying to upload a profile image with
the API with OAuth authentication. I get a 200 response and a valid
response body, indicating a path like
http://a1.twimg.com/profile_images/1078800125/myProfileImage_normal.jpg
in the response for the uploaded image. However, when I try to access
this URL, I get HTTP 403 Forbidden. Is this expected in the current
state of things, or is the problem on my client side?
J
On Jun 15, 8:12 am, Taylor Singletary taylorsinglet...@twitter.com
wrote:
The image upload facilities at Twitter are in need of some love (and are
being worked on!) -- they'll often throw a 500 error and actually update the
image, or show a 500 error and not update the image.. it should, in general,
function better and more reliably in the near future. The current site
issues make it sometimes difficult to have clarity on how something failed,
and at what stage.
Taylor Singletary
Developer Advocate, Twitterhttp://twitter.com/episod
On Tue, Jun 15, 2010 at 7:00 AM, Roy Tanck roy.ta...@gmail.com wrote:
I'm trying to upload profile images using oAuth. This basically works
(I get the right return data, no errors), except that the image is not
updated. Sending tweets through the same library does work, so this
probably isn't an authentication issue.
As per the twitter-async documentation, I'm using:
$twitterObj-post('/account/update_profile_image.json', array('@image'
= '@'.$img_path));
$img_path is the correct path (+filename) for the file, I've checked
the folder name using phpinfo, used a test image, etc.
Since I'm not getting errors, this issue is very hard to troubleshoot
from my end. Suggestions on how to tackle this very welcome.
(More info on twitter-async is here:
http://github.com/jmathai/twitter-async
, on sending images here
http://wiki.github.com/jmathai/twitter-async/#multipart)
