[twitter-dev] Radomly , 401 in my twitter api request when i use x-auth
Dear all, I am getting radomly 401 (invalid signature ) error from server . I ma using the nonce as timestamp+random() ; (ramdom number) What could be the reason.. -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
[twitter-dev] Radomly , 401 in my twitter api request when i use x-auth
Dear all, I am getting radomly 401 (invalid signature ) error from server . I ma using the nonce as timestamp+random() ; (ramdom number) What could be the reason..? Most of the time my requests are served fine by the twitter server. but then and there am getting 401 ...please help me out -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
[twitter-dev] Re: Error 401 only in Target (working fine in simulator)
Dear Taylor, I am getting one new issue. In my application , randomly some api's returns 401 - invalid signature error... I am not sure whether twitter server only returns 401 randomly or some problem in my request..? Most of the time my requests are working fine... Please help me out Regards, Karthik On Sep 2, 2:07 am, Taylor Singletary taylorsinglet...@twitter.com wrote: Our generous time range is actually +- ~ 15 minutes -- I just tell everyone within 5 minutes to keep things proper and sane. :) Understand that our correction here is a bit sudden; we may make a compromise tweak that will restrict future timestamps, but now with a more relaxed resolution than 15 minutes -- with the intention to rectify this more gradually in the future. In the meantime, we strongly suggest clients perform a timestamp sanity check. I'll work on formalizing and abstracting the few options developers have to make this smooth. Some day we'll finally release our improved OAuth 1.0A implementation that will also be very specific with you about the drift detected in your timestamp. Thanks, Taylor On Wed, Sep 1, 2010 at 1:55 PM, M. Edward (Ed) Borasky zn...@borasky-research.net wrote: That's a surprise - I'd expect Apple to be on top of stuff like that! Even so, 18 seconds is well within Twitter's outrageously generous tolerance of five minutes. Then again, I used to work at Goddard Space Flight Center - I was spoiled by having clocks accurate to a microsecond available as wall plugs. ;-) -- M. Edward (Ed) Borasky http://borasky-research.nethttp://twitter.com/znmeb A mathematician is a device for turning coffee into theorems. - Paul Erdos Quoting Tom van der Woerdt i...@tvdw.eu: Not iOS (iPhone, iPod Touch, etc) - my iPod Touch seems to be 18 seconds out of sync. Tom On 9/1/10 10:39 PM, M. Edward (Ed) Borasky wrote: I'd think mobiles - at least the common ones (iPhone, Android, Symbian, Blackberry, Palm, etc.) would be synchronized to world time automatically. At least my old LG ENV and current Verizon Droid Incredible tell me what time it is. ;-) -- Twitter developer documentation and resources:http://dev.twitter.com/doc API updates via Twitter:http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en -- Twitter developer documentation and resources:http://dev.twitter.com/doc API updates via Twitter:http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
[twitter-dev] Re: Error 401 only in Target (working fine in simulator)
Dear Taylor, I am getting one new issue. In my application , randomly some api's returns 401 - invalid signature error... I am not sure whether twitter server only returns 401 randomly or some problem in my request..? Most of the time my requests are working fine... Please help me out Regards, On Sep 1, 9:34 pm, Taylor Singletary taylorsinglet...@twitter.com wrote: Hi Karthik, Make sure that the time on your device is in sync with Twitter's clocks. We return our current time in the Date HTTP header of every response. One easy way to fixate an application's clock with our servers is to issue a HTTP HEAD request tohttp://api.twitter.com/1/help/test.xml-- it's a non-rate-limited request and will allow you to adjust your clock in relation to ours. The oauth_timestamp in your example here is for Dec 31st, 2009. Taylor On Wed, Sep 1, 2010 at 9:10 AM, Karthik karthikduraisw...@gmail.com wrote: Hi , I am developing a Twitter application in MTK (Media tek ) platform. I am using Oauth and and My application has the X-auth permission I am first using POST with required params and the am using below URL https://api.twitter.com/oauth/access_token to get the access token in exchange with the username, password. I am able to get the access token and My application is working fine in the simulator (I ma using the proxy server in simulator) But in the Mobile (I amm not using proxy) , when I post https://api.twitter.com/oauth/access_token I am always getting 401 - Unauthorized (Failed to validate oauth signature and token) The below is my sample input string to get the signature (hmac-sha1) POSThttp%3A%2F%2Fapi.twitter.com%2Foauth %2Faccess_tokenoauth_consumer_key%3D4dsadsadsasdsd%26oauth_nonce %3D1262304301%26oauth_signature_method%3DHMAC-SHA1%26oauth_timestamp %3D1262304300%26oauth_version%3D1.0%26x_auth_mode%3Dclient_auth %26x_auth_password%3Dtest1234%26x_auth_username%3Dnareshs %2540google.com Please someone help me to resolve this issue.. -- Twitter developer documentation and resources:http://dev.twitter.com/doc API updates via Twitter:http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
[twitter-dev] About OAuth
I found out twitter does not support Basic Auth any, and I wonder how
can I change my code from Basic Auth to OAuth.
and my code like following:
$username=username;
$password=password;
$message=message;
$host = http://twitter.com/statuses/update.xml;;
$ch = curl_init();
curl_setopt($ch, CURLOPT_URL, $host);
//curl_setopt($ch, CURLOPT_VERBOSE, 1);
//curl_setopt($ch, CURLOPT_HTTPHEADER, array('Expect:'));
curl_setopt($ch, CURLOPT_RETURNTRANSFER, 1);
curl_setopt($ch, CURLOPT_TIMEOUT, $config-timeout );
curl_setopt($ch, CURLOPT_USERPWD, $username:$password);
curl_setopt($ch, CURLOPT_POSTFIELDS,status=$message);
//curl_setopt($ch, CURLOPT_HTTP_VERSION, CURL_HTTP_VERSION_1_1);
curl_setopt($ch, CURLOPT_POST, 1);
$result = curl_exec($ch);
// Look at the returned header
$resultArray = curl_getinfo($ch);
curl_close($ch);
--
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
http://groups.google.com/group/twitter-development-talk?hl=en
Re: [twitter-dev] Need Developer
Hi, Which help u need. Regards, George On Fri, Sep 3, 2010 at 3:20 AM, Mike Morang m...@iplusmarketing.com wrote: I need a Twitter developer to add functionality to my approved Twitter app. Best Regards, * Michael Morang Principal Consultant iPlus Marketing Corp. 714-594-7374 Website: iPlusMarketing.com http://iplusmarketing.com/ Email: m...@iplusmarketing.com Follow me on Twitter: Twitter.com/iPlusMarketinghttp://twitter.com/iPlusMarketing Linkedin:http://www.linkedin.com/in/mikemorang Skype: GrowMe * -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
[twitter-dev] retweeted always returing as false in /1/statuses/user_timeline.json
Hi there, I have a Twitter module I'm improving upon which pulls tweets from /1/statuses/user_timeline.json. An issue that I've noticed is that over the last couple of days, tweets I've retweeted using the retweet link on twitter.com have continued to display as retweeted: false in the JSON. Can someone tell me if this is normal behavior or if it's an issue with the API? Thanks! -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
[twitter-dev] Twitter MOSS Webpart
Hi, I am MOSS 2007 developer, I want to create a new Twitter webpart to display Tweets on my WebPart. Can you please help, how i can interact with Twitter services to pick tweets. Regards, Sanjeet -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
[twitter-dev] Twurl Multiple Account Usage Help
I think i'm one of many who are looking for different ways of moving from Curl to Twurl with Twitter's closing the Basic Authentication protocol. I have different scripts that run on my server, based on certain criteria on the return of that script an automated tweet goes out to 1 of 2 accounts. With basic authentication it was easy to define the account using '-u' and '-p'. I'm trying to figure out how to do it with Twurl. I've authorized the two accounts in Twurl, but I can only get the default to tweet. I see I can change the default account, but depending on how fast the script is running it may want to tweet both accounts about the same time, and I don't want it to get caught switching defaults and the wrong data being sent to the incorrect account. I tried adding '-u' and the username at the start of the Twurl call, but it errors saying You need to authorize first, even though the account was authorized. Has anyone had success in this? Thank you. -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
Re: [twitter-dev] Need Developer
Specifically, what platform(s) are you targeting and what functionality do you look to add? On Thu, Sep 2, 2010 at 23:30, Georgooty varghese georgo...@gmail.com wrote: Hi, Which help u need. Regards, George On Fri, Sep 3, 2010 at 3:20 AM, Mike Morang m...@iplusmarketing.com wrote: I need a Twitter developer to add functionality to my approved Twitter app. Best Regards, Michael Morang Principal Consultant iPlus Marketing Corp. 714-594-7374 Website: iPlusMarketing.com Email: m...@iplusmarketing.com Follow me on Twitter: Twitter.com/iPlusMarketing Linkedin:http://www.linkedin.com/in/mikemorang Skype: GrowMe -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
[twitter-dev] Re: Connevct to another users application
Hi John, Thanks for answering my question. Do I understand that for every twitter account which I want to use to for automatically twitter I have to register an application. This is what i did right now but I would like to have a more simple construction. I was in the opinion that I could use just one script with the keys in it of the registered application (so it is registered just once) and also the keys of the user in in so it uses the twitter account of that user and the application of another user. Thanks, Frank On 2 sep, 16:02, John Meyer john.l.me...@gmail.com wrote: On 9/2/2010 2:48 AM, Frank P wrote: Hi There, I am a website builder and used a Twitter API to update a Twitter status when a webaster wrote a new newsitem on his site. Now I have to rewrite the api to use oAUTH. I got it working but is it possible to register the application once and let other users make use of that application. I think I need the access token and the ouath token secret of that user to connect. But I can't find those keys in the users profile. When you initially get the user to authorize your website/application, you receive back the token combo. You then need to store those somewhere (database, cookie, etc) for subsequent authorizations. -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
Re: [twitter-dev] Re: Single Token: Using oauth with Perl: 401 Unauthorized
On 9/3/10 12:28 AM, Lars wrote: Why aren't my answers to Tom being displayed? No idea. I based my program on the exmaples I found under http://apiwiki.twitter.com/OAuth-Examples especially on the example of Scott Carter http://www.social.com/main/twitter-oauth-using-perl/. I followed his comment: # Add padding character to make a multiple of 4 per the # requirement of OAuth. $signature .= =; As long as the amount of characters is a multiple of 4, it's fine. :) I also noticed that you don't URL encode the values in $content. If I recall correctly, you have to URL encode those as well. I think I do encode them with my $signature_base_str = POST . uri_escape_RFC3986($api_url) . . uri_escape_RFC3986($content); correct? No, you need to urlencode the key/value as well, and later urlencode the complete body. If that was not the issue, then please show your Base String and the HTTP request. This is the base string: POSThttp%3A%2F2Fapi.twitter.com%2F1%2Fstatuses %2Fupdate.jsonoauth_consumer_key%3DXXX%26oauth_nonce %3D101%26oauth_signature_method%3DHMAC-SHA1%26oauth_timestamp %3D1272325550%26oauth_token%3DXXX%26oauth_version%3D1.0%26status %3DHello%20world Quoting my validator (http://quonos.nl/oauthTester/) : # Bad URL encoding! # Both key and value in the POST body need to be URL encoded. What do you mean with show us the HTTP request. I think I am doing the HTTP request with my $ua = LWP::UserAgent-new; my $req = POST($api_url = [ oauth_nonce = $oauth_nonce, oauth_signature_method = $oauth_signature_method, oauth_timestamp = $oauth_timestamp, oauth_consumer_key = $oauth_consumer_key, oauth_token = $oauth_token, oauth_signature = $signature, oauth_version = $oauth_version, status = $status ]); # Make the request my $res = $ua-request($req); Actually I meant a dump of the request you make, like the POST /endpoint HTTP/1.1 part, including headers. Tom On 3 Sep., 00:23, Lars lars_sa...@hotmail.com wrote: Sorry, I don't habe shell access... On 3 Sep., 00:20, Marc Mims marc.m...@gmail.com wrote: I am not a Perl expert but I have developed a small web page with Perl which is somewhat popular in Germany (according to Alexa trafic rank 1000). And this web site is tweeting important events using its own twitter account. I tried for days but I am not able to get it working (tweeting) again. I registered my web page/application and want to use my access tokens oauth_token and oauth_token_secret which I find under my application settings because I am using only this twitter account to tweet (seehttp://dev.twitter.com/pages/oauth_single_token) But the response is always 401 Unauthorized! Any ideas? My Perl program looks like this (my provider does not offer the module NET::Twitter) If you have shell access, you can probably install local::lib using the bootstrap method, then install Net::Twitter or Net::Twitter::Lite in your own directory. -Marc -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
[twitter-dev] Re: Twitter logout - hate to open this can of worms again
I thought I had found a solution, albeit a horrendously ugly one: redirect them to http://twitter.com/logout, but even that doesn't work. If you are looking for reliable, don't log them in with OAuth - except once, the first time, when you store their token. On Sep 3, 7:23 am, Abraham Williams 4bra...@gmail.com wrote: There is no pragmatic way to sign a user out of twitter.com through the API. When a user logs out of your site send them to to twitter.com so they can sign out there or to a page explaining they should sign out of twitter.com Abraham - Abraham Williams | Hacker Advocate |http://abrah.am @abraham |http://projects.abrah.am|http://blog.abrah.am This email is: [ ] shareable [x] ask first [ ] private. On Thu, Sep 2, 2010 at 10:43, Matei mad.doroba...@gmail.com wrote: bump? On Sep 1, 10:45 am, Matei mad.doroba...@gmail.com wrote: Hi everyone, I am compelled to ask because the search turned out a few post that were somewhat vague and didn't answer all my questions. I have a website widget that interacts heavily with Twitter. We use OAuth to authenticate our requests. To logout the users from our side we destroy the OAuth token. However during the initial OAuth workflow Twitter places a cookie on the browser, so if the user logs out from our site but navigates to the Twitter site they are still logged in. Closing the browser solves this, as it appears the cookie is a session cookie. Calling the account/end_session.json end point does nothing for use because the call is server side so the cookie doesn't get replaced. I am a little concerned about this behavior since the widget will be on a public site users can access from public computers. It is possible the users will log out of our widget but not close the browser window. At that point someone could navigate to twitter and still be logged in with their account. So finally my questions are: 1. Is how do I reliably log users out of Twitter? 2. Is it really necessary for Twitter to send this cookie during the OAuth workflow? The API is stateless so the cookie is really un- necessary as far as using the apis is concerned. Sorry for the lengthy post, responses are greatly appreciated! Cheers, Matei -- Twitter developer documentation and resources:http://dev.twitter.com/doc API updates via Twitter:http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
[twitter-dev] Re: Single Token: Using oauth with Perl: 401 Unauthorized
I usually use Wireshark for that, but it won't work with https:// connections. If you use cURL in PHP, there's an option for verbose output. I'm not sure about Perl, but Wireshark should help :) Tom On 9/3/10 10:42 AM, Lars wrote: I Tom, thanks for the validator! This is really a helpful tool. Can you explain me how to generat a dump of my http request? I have no idea how to do this in Perl. Thanks Best regards, Lars On Sep 3, 9:41 am, Tom van der Woerdt i...@tvdw.eu wrote: On 9/3/10 12:28 AM, Lars wrote: Why aren't my answers to Tom being displayed? No idea. I based my program on the exmaples I found underhttp://apiwiki.twitter.com/OAuth-Examples especially on the example of Scott Carterhttp://www.social.com/main/twitter-oauth-using-perl/. I followed his comment: # Add padding character to make a multiple of 4 per the # requirement of OAuth. $signature .= =; As long as the amount of characters is a multiple of 4, it's fine. :) I also noticed that you don't URL encode the values in $content. If I recall correctly, you have to URL encode those as well. I think I do encode them with my $signature_base_str = POST . uri_escape_RFC3986($api_url) . . uri_escape_RFC3986($content); correct? No, you need to urlencode the key/value as well, and later urlencode the complete body. If that was not the issue, then please show your Base String and the HTTP request. This is the base string: POSThttp%3A%2F2Fapi.twitter.com%2F1%2Fstatuses %2Fupdate.jsonoauth_consumer_key%3DXXX%26oauth_nonce %3D101%26oauth_signature_method%3DHMAC-SHA1%26oauth_timestamp %3D1272325550%26oauth_token%3DXXX%26oauth_version%3D1.0%26status %3DHello%20world Quoting my validator (http://quonos.nl/oauthTester/) : # Bad URL encoding! # Both key and value in the POST body need to be URL encoded. What do you mean with show us the HTTP request. I think I am doing the HTTP request with my $ua = LWP::UserAgent-new; my $req = POST($api_url = [ oauth_nonce = $oauth_nonce, oauth_signature_method = $oauth_signature_method, oauth_timestamp = $oauth_timestamp, oauth_consumer_key = $oauth_consumer_key, oauth_token = $oauth_token, oauth_signature = $signature, oauth_version = $oauth_version, status = $status ]); # Make the request my $res = $ua-request($req); Actually I meant a dump of the request you make, like the POST /endpoint HTTP/1.1 part, including headers. Tom On 3 Sep., 00:23, Lars lars_sa...@hotmail.com wrote: Sorry, I don't habe shell access... On 3 Sep., 00:20, Marc Mims marc.m...@gmail.com wrote: I am not a Perl expert but I have developed a small web page with Perl which is somewhat popular in Germany (according to Alexa trafic rank 1000). And this web site is tweeting important events using its own twitter account. I tried for days but I am not able to get it working (tweeting) again. I registered my web page/application and want to use my access tokens oauth_token and oauth_token_secret which I find under my application settings because I am using only this twitter account to tweet (seehttp://dev.twitter.com/pages/oauth_single_token) But the response is always 401 Unauthorized! Any ideas? My Perl program looks like this (my provider does not offer the module NET::Twitter) If you have shell access, you can probably install local::lib using the bootstrap method, then install Net::Twitter or Net::Twitter::Lite in your own directory. -Marc -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
[twitter-dev] Re: Where Am I going wrong? Can't get past step 1 of Oauth Integration in PHP...
Thanks Matt, Got a couple of hours spare dev time now, time to get into it! -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
[twitter-dev] garbage in json api response?
Hi everyone, I am noticing that my home timeline and that of a few other people is returning some messed up stuff, basically intemingling something that looks like a random sequence of bytes to normal messages. You can in theory verify this by accessing my home timeline (@riffraff) and requesting 200 messages, or using the public_timeline for the user @puredanger such as curl 'api.twitter.com/1/statuses/user_timeline.json?screen_name=puredangercount=48since_id=22815626427max_id=22857673035' Sorry I could not reduce this to a simpler sample. This appears to happen only with the json apis, the xml ones seem to report reasonable code. Can someone else confirm this? -- blog en: http://www.riffraff.info blog it: http://riffraff.blogsome.com -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
[twitter-dev] Re: garbage in json api response?
Confirmed here too. On Sep 3, 8:57 pm, gabriele renzi rff@gmail.com wrote: Hi everyone, I am noticing that my home timeline and that of a few other people is returning some messed up stuff, basically intemingling something that looks like a random sequence of bytes to normal messages. You can in theory verify this by accessing my home timeline (@riffraff) and requesting 200 messages, or using the public_timeline for the user @puredanger such as curl 'api.twitter.com/1/statuses/user_timeline.json?screen_name=puredangercount=48since_id=22815626427max_id=22857673035' Sorry I could not reduce this to a simpler sample. This appears to happen only with the json apis, the xml ones seem to report reasonable code. Can someone else confirm this? -- blog en:http://www.riffraff.info blog it:http://riffraff.blogsome.com -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
[twitter-dev] Re: garbage in json api response?
Here too! Lots of binary garbage coming for a: /statuses/user_timeline.json? count=40include_rts=truescreen_name=chockenberryoauth_consumer_key=...oauth_nonce=...oauth_signature_method=HMAC- SHA1oauth_timestamp=...oauth_token=...oauth_version=1.0oauth_signature=... Twitter for iPhone also reports an PCDATA Invalid Char value 1 ... for one of my private lists @janole/TwitterClientDevelopers. Could you please look into this and fix it? Thanks Ole / Gravity Twitter Client for Symbian / @janole / o...@mobileways.de On 3 Sep., 13:07, David Novakovic davidnovako...@gmail.com wrote: Confirmed here too. On Sep 3, 8:57 pm, gabriele renzi rff@gmail.com wrote: Hi everyone, I am noticing that my home timeline and that of a few other people is returning some messed up stuff, basically intemingling something that looks like a random sequence of bytes to normal messages. You can in theory verify this by accessing my home timeline (@riffraff) and requesting 200 messages, or using the public_timeline for the user @puredanger such as curl 'api.twitter.com/1/statuses/user_timeline.json?screen_name=puredangercount=48since_id=22815626427max_id=22857673035' Sorry I could not reduce this to a simpler sample. This appears to happen only with the json apis, the xml ones seem to report reasonable code. Can someone else confirm this? -- blog en:http://www.riffraff.info blog it:http://riffraff.blogsome.com -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
[twitter-dev] Re: Delivery Status Notification (Failure)
Hi, I have implemented twitter appllication in C#.net. I have used X-Auth authentication. Ie, we have directly entered int twitter account, not displayed twitter autherization pages. In that application I have displayed home tweets, to displayed friends,followers, search, etc.. Could you please explain mw, how to help u? Regards, George On Fri, Sep 3, 2010 at 12:18 PM, John SJ Anderson geneh...@gmail.com wrote: Specifically, what platform(s) are you targeting and what functionality do you look to add? On Thu, Sep 2, 2010 at 23:30, Georgooty varghese georgo...@gmail.com wrote: Hi, Which help u need. Regards, George On Fri, Sep 3, 2010 at 3:20 AM, Mike Morang m...@iplusmarketing.com wrote: I need a Twitter developer to add functionality to my approved Twitter app. Best Regards, Michael Morang Principal Consultant iPlus Marketing Corp. 714-594-7374 Website: iPlusMarketing.com Email: m...@iplusmarketing.com Follow me on Twitter: Twitter.com/iPlusMarketing Linkedin:http://www.linkedin.com/in/mikemorang Skype: GrowMe -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
Re: [twitter-dev] Need Developer
Hi, I have implemented twitter appllication in C#.net. I have used X-Auth authentication. Ie, we have directly entered int twitter account, not displayed twitter autherization pages. In that application I have displayed home tweets, to displayed friends,followers, search, etc.. Could you please explain mw, how to help u? Regards, George On Fri, Sep 3, 2010 at 12:18 PM, John SJ Anderson geneh...@gmail.comwrote: Specifically, what platform(s) are you targeting and what functionality do you look to add? On Thu, Sep 2, 2010 at 23:30, Georgooty varghese georgo...@gmail.com wrote: Hi, Which help u need. Regards, George On Fri, Sep 3, 2010 at 3:20 AM, Mike Morang m...@iplusmarketing.com wrote: I need a Twitter developer to add functionality to my approved Twitter app. Best Regards, Michael Morang Principal Consultant iPlus Marketing Corp. 714-594-7374 Website: iPlusMarketing.com Email: m...@iplusmarketing.com Follow me on Twitter: Twitter.com/iPlusMarketing Linkedin:http://www.linkedin.com/in/mikemorang Skype: GrowMe -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
[twitter-dev] Vbscript Function for OAuth authentication
I had a simple vbscript on my pc that post to my twitter account. I was hoping there is already a function for this new OAuth authentication system. -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
[twitter-dev] Re: Single Token: Using oauth with Perl: 401 Unauthorized
Sorry, how to I generate a dump of my request with Perl? On Sep 3, 9:41 am, Tom van der Woerdt i...@tvdw.eu wrote: On 9/3/10 12:28 AM, Lars wrote: Why aren't my answers to Tom being displayed? No idea. I based my program on the exmaples I found underhttp://apiwiki.twitter.com/OAuth-Examples especially on the example of Scott Carterhttp://www.social.com/main/twitter-oauth-using-perl/. I followed his comment: # Add padding character to make a multiple of 4 per the # requirement of OAuth. $signature .= =; As long as the amount of characters is a multiple of 4, it's fine. :) I also noticed that you don't URL encode the values in $content. If I recall correctly, you have to URL encode those as well. I think I do encode them with my $signature_base_str = POST . uri_escape_RFC3986($api_url) . . uri_escape_RFC3986($content); correct? No, you need to urlencode the key/value as well, and later urlencode the complete body. If that was not the issue, then please show your Base String and the HTTP request. This is the base string: POSThttp%3A%2F2Fapi.twitter.com%2F1%2Fstatuses %2Fupdate.jsonoauth_consumer_key%3DXXX%26oauth_nonce %3D101%26oauth_signature_method%3DHMAC-SHA1%26oauth_timestamp %3D1272325550%26oauth_token%3DXXX%26oauth_version%3D1.0%26status %3DHello%20world Quoting my validator (http://quonos.nl/oauthTester/) : # Bad URL encoding! # Both key and value in the POST body need to be URL encoded. What do you mean with show us the HTTP request. I think I am doing the HTTP request with my $ua = LWP::UserAgent-new; my $req = POST($api_url = [ oauth_nonce = $oauth_nonce, oauth_signature_method = $oauth_signature_method, oauth_timestamp = $oauth_timestamp, oauth_consumer_key = $oauth_consumer_key, oauth_token = $oauth_token, oauth_signature = $signature, oauth_version = $oauth_version, status = $status ]); # Make the request my $res = $ua-request($req); Actually I meant a dump of the request you make, like the POST /endpoint HTTP/1.1 part, including headers. Tom On 3 Sep., 00:23, Lars lars_sa...@hotmail.com wrote: Sorry, I don't habe shell access... On 3 Sep., 00:20, Marc Mims marc.m...@gmail.com wrote: I am not a Perl expert but I have developed a small web page with Perl which is somewhat popular in Germany (according to Alexa trafic rank 1000). And this web site is tweeting important events using its own twitter account. I tried for days but I am not able to get it working (tweeting) again. I registered my web page/application and want to use my access tokens oauth_token and oauth_token_secret which I find under my application settings because I am using only this twitter account to tweet (seehttp://dev.twitter.com/pages/oauth_single_token) But the response is always 401 Unauthorized! Any ideas? My Perl program looks like this (my provider does not offer the module NET::Twitter) If you have shell access, you can probably install local::lib using the bootstrap method, then install Net::Twitter or Net::Twitter::Lite in your own directory. -Marc -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
[twitter-dev] Re: New SSL certificate issue with WTK 2.5.2
Hey Matt, Yes, I will keep that in mind. Thanks for your time. Amit. On Aug 31, 6:06 am, Matt Harris thematthar...@twitter.com wrote: Hey Netroboost, If the device doesn't support wildcard SSL these isn't much that can be done except to use HTTP. This isn't recommended but if you have no choice it's all you can do. The only caveats to know about are: * xAuth requires SSL so won't be available to any devices that do not support our certificate * transmitting OAuth secrets without SSL increases their risk of being compromised Hope that helps, Matt On Fri, Aug 27, 2010 at 3:18 AM, Netroboost netrobo...@gmail.com wrote: Hi Matt, Thank you for your response. Yes, I was finally able to get rid of the exception with the method you suggested. However as far as I know the issue extends beyond the Sun Java WTK. Various handset manufacturers have different implementations of this JSR and while some do accept wildcard SSL certificates, some do not. In such a case wouldn't it be sensible for mobile app developers to use the HTTP method as a fail-safe method for authentication? Is there any catch to this? Regards, Amit. On Aug 26, 6:22 am, Matt Harris thematthar...@twitter.com wrote: Hi Amit, This is an issue with the Sun WTK 2.5.2 not accepting wildcard SSL certificates and not with the Twitter API. In the future we would like to move to a single domain certificate but there is no date as to when that will be. Whilst it isn't something we like you to do, the OAuth process isn't forbidden over SSL, just strongly discouraged. This means HTTP could be used - but again, this is discouraged. Instead, as wildcard SSL certificates are perfectly valid I recommend asking on the developer forums for the Sun WTK to see if support will be added to the toolkit itself. Best, Matt On Mon, Aug 23, 2010 at 12:35 AM, Netroboost netrobo...@gmail.com wrote: Hi, Has this issue been resolved yet? I am using Sun WTK 2.5.2 and facing the same issue. The error message reads: Subject alternative name did not match site name Please help if anyone knows how to deal with this. Thanks, Amit. On Jul 23, 10:18 pm, Matt Harris thematthar...@twitter.com wrote: Hi, I've seen similar reports for other service providers about this issue as well. My concern is wildcard certificates are perfectly valid and are described in RFC2818 [1]. I'm not sure why Sun WTK doesn't support them or of any workarounds but I would suggest asking on their support channels. If there are any changes on our systems we will be communicate them through this developer mailing list. Best, Matt 1.http://www.ietf.org/rfc/rfc2818.txt On Fri, Jul 23, 2010 at 4:56 AM, bjcoredev jme...@gmail.com wrote: How will we be warned when api.twitter.com fixed SSL certificate will be effective ? On 22 juil, 21:17, John Adams j...@twitter.com wrote: Unfortunately, the current situation is that api.twitter.com is on a wildcard certificate. We have plans to move it a fixed SSL certificate in the near future, but no definite date yet. -j On Thu, Jul 22, 2010 at 11:50 AM, bjcoredev jme...@gmail.com wrote: My app doesn't use the mobile site. My twitter client is written in J2ME (Java Micro Edition) and is not using the mobile site but the Twitter API. I m coding my client with WTK 2.5.2 Sun Wireless Toolkit (like many other Java mobile developers) and since the 21/07/2001 1AM GMT my app running under WTK can't access the url https://api.twitter.com/oauth/access_token because the WTK CAN'T HANDLE WILDCARD SSL certificates. returning the error:Subject alternative name did not match site name. I'have read that real (real devices opposite to the emulator) mobile JAVA platforms (Sony ericsson,WM 5.0,..) don't accept wildcard SSL certificates so twitter clients using twitter API written in J2ME running under these platform can't access the url https://api.twitter.com/oauth/access_token anymore so can't process xAuth authentication wich will be mandatory on 15 august So . On 22 juil, 20:20, John Adams j...@twitter.com wrote: The mobile site has used a wildcard certificate for the last two years; Did you recently begin experiencing this issue or was your code working in the past? -j On Thu, Jul 22, 2010 at 6:43 AM, bjcoredev jme...@gmail.com wrote: It seems that SUN WTK 2.5.2 doesn't accept wildcard certificates I hope that mobile platforms accept wildcard SSL certificates. If this not the case, it will make twitter xAuth/oAuth unusable Regards On 22 juil, 14:57, bjcoredev
Re: [twitter-dev] Re: New SSL certificate issue with WTK 2.5.2
Hi Matt, Pls tel me how can I get the Single Access token auth in j2me thanks Pradeep On Fri, Sep 3, 2010 at 1:08 AM, Ernandes Jr. ernan...@gmail.com wrote: If you use Twitter API ME Single Access token auth you will get access to Twitter API, even on emulator. When you use this type of auth, HTTPS is bypassed. But is just a workaround, since Single Access token has its constraints. On Wed, Sep 1, 2010 at 11:40 PM, Pradeep Senanayake pradeepd.senanay...@gmail.com wrote: HI Matt. tel me how can I get rid of that exception using HTTP. Thanks in advance. On Aug 31, 9:06 am, Matt Harris thematthar...@twitter.com wrote: Hey Netroboost, If the device doesn't support wildcard SSL these isn't much that can be done except to use HTTP. This isn't recommended but if you have no choice it's all you can do. The only caveats to know about are: * xAuth requires SSL so won't be available to any devices that do not support our certificate * transmitting OAuth secrets without SSL increases their risk of being compromised Hope that helps, Matt On Fri, Aug 27, 2010 at 3:18 AM, Netroboost netrobo...@gmail.com wrote: Hi Matt, Thank you for your response. Yes, I was finally able to get rid of the exception with the method you suggested. However as far as I know the issue extends beyond the Sun Java WTK. Various handset manufacturers have different implementations of this JSR and while some do accept wildcard SSL certificates, some do not. In such a case wouldn't it be sensible for mobile app developers to use the HTTP method as a fail-safe method for authentication? Is there any catch to this? Regards, Amit. On Aug 26, 6:22 am, Matt Harris thematthar...@twitter.com wrote: Hi Amit, This is an issue with the Sun WTK 2.5.2 not accepting wildcard SSL certificates and not with the Twitter API. In the future we would like to move to a single domain certificate but there is no date as to when that will be. Whilst it isn't something we like you to do, the OAuth process isn't forbidden over SSL, just strongly discouraged. This means HTTP could be used - but again, this is discouraged. Instead, as wildcard SSL certificates are perfectly valid I recommend asking on the developer forums for the Sun WTK to see if support will be added to the toolkit itself. Best, Matt On Mon, Aug 23, 2010 at 12:35 AM, Netroboost netrobo...@gmail.com wrote: Hi, Has this issue been resolved yet? I am using Sun WTK 2.5.2 and facing the same issue. The error message reads: Subject alternative name did not match site name Please help if anyone knows how to deal with this. Thanks, Amit. On Jul 23, 10:18 pm, Matt Harris thematthar...@twitter.com wrote: Hi, I've seen similar reports for other service providers about this issue as well. My concern is wildcard certificates are perfectly valid and are described in RFC2818 [1]. I'm not sure why Sun WTK doesn't support them or of any workarounds but I would suggest asking on their support channels. If there are any changes on our systems we will be communicate them through this developer mailing list. Best, Matt 1.http://www.ietf.org/rfc/rfc2818.txt On Fri, Jul 23, 2010 at 4:56 AM, bjcoredev jme...@gmail.com wrote: How will we be warned when api.twitter.com fixed SSL certificate will be effective ? On 22 juil, 21:17, John Adams j...@twitter.com wrote: Unfortunately, the current situation is that api.twitter.comis on a wildcard certificate. We have plans to move it a fixed SSL certificate in the near future, but no definite date yet. -j On Thu, Jul 22, 2010 at 11:50 AM, bjcoredev jme...@gmail.com wrote: My app doesn't use the mobile site. My twitter client is written in J2ME (Java Micro Edition) and is not using the mobile site but the Twitter API. I m coding my client with WTK 2.5.2 Sun Wireless Toolkit (like many other Java mobile developers) and since the 21/07/2001 1AM GMT my app running under WTK can't access the url https://api.twitter.com/oauth/access_token because the WTK CAN'T HANDLE WILDCARD SSL certificates. returning the error:Subject alternative name did not match site name. I'have read that real (real devices opposite to the emulator) mobile JAVA platforms (Sony ericsson,WM 5.0,..) don't accept wildcard SSL certificates so twitter clients using twitter API written in J2ME running under these platform can't access the url https://api.twitter.com/oauth/access_token anymore so can't process xAuth authentication wich will be mandatory on 15 august So . On 22 juil, 20:20, John Adams j...@twitter.com wrote:
[twitter-dev] home_timeline.json returning garbage between tweets
Hello.
Starting today (maybe yesterday, wasn't around to check) home_timeline
started sending garbage between the expected tweet objects. Since I
didn't modify my code in any way, I assume it's a bug (or a feature?) on
Twitter's side...
{normal
tweet},x mTێ�6 � � � �ں�kYH�M �(�٢/ �4��P�BRqv��{ uq�m
0o3s.3_�,/M��5��u�22��l9²
2��� {O Kr��e��ɞ��cY��+# u�A +|刌
0��9Xp��b8^6R{� Mp�� �.) �3��V#?[��;��B\�\�=?�Е�u8� �5D��=g�4��m���|�_.�_˗���2F YX��=9�P�x Cق�� ���Fi ^�t�N`�Ee��SN 5� )k A� � l� 1+sd�D��Q� ���+S HN� {Ů^ǣ�
� �^1���8� � �a� Z�K2TU�UL�Bv-�1Vc��ؠ ]p ef Y}:ۛZ ��%D�pQ�j� �7pG 5���m X��/��fi���5�1'� �
��3� � 2� V� j}��Zy$�;�H� d1Z`=� ��u��yZl
^+W c]+� /ױ'�'�h ��S�g�S =�5�A��� � ���W ,�07�~_� 0 } 6�7� ��� ̀��d�w{(3S�
�E�Z ��Ķ�[V� � {�� _� id-�!刖 �E�4���a���'�%�� ^� ��
P���v_쾗���x���n��m {/�%E��� �d�Bu
-�J^T�A �� �O���_d�ݬc3I�m_�Շ.ڣ ��M�
�=+� 7N��/���f��KONcg�� KZ�o�|�v�\� �,+6�}� -g�h�b...@�ww���t� gȗ�_ �S ) �g�ȱ�:�jK���Aky�XǠ�g [?�� +��?�� �,{normal
tweet}
Am I the only one to see this behavior? Some of the requests return
correct data, but more often there's this garbage in the data throwing
my JSON parser off...
Regards,
Fabian Schlenz
--
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
http://groups.google.com/group/twitter-development-talk?hl=en
[twitter-dev] Are IDs globally unique? Or just unique for each object type?
Are IDs globally unique? Or just unique for each object type? In other words, is it possible to have a user with the ID 7 and also a DM with the ID 7? -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
[twitter-dev] strange sudden death
Hi guys... Been working on a fun twitter app on and off for the last couple of months now. Almost done.. But today all of a sudden everything stopped working? Seems like I am not getting any cookies from twitter anymore. I know things have changed concerning oauth but all worked yesterday...anythin I need to know? Cheers Simon -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
[twitter-dev] Re: Single Token: Using oauth with Perl: 401 Unauthorized
I think, I have the base string now, the signature and all the other data. I validated it with http://quonos.nl/oauthTester/ and everything is fine. However, I am still gettin 401 or 501 error. This is my base string: POSThttp%3A%2F%2Fapi.twitter.com%2F1%2Fstatuses %2Fupdate.xmloauth_consumer_key%3D0E1xSiyE03RTEms3WfQ%26oauth_nonce %3D11%26oauth_signature_method%3DHMAC-SHA1%26oauth_timestamp %3Doauth_timestamp%26oauth_token%3D88893619- JS87TMQDkUjM7Ufq119njayEJBuihVQmMEuTu3Ugi%26oauth_version %3D1.0%26status%3DHallo%252C%2520hier%2520ist%2520Lars I think I still don't know exactly how to send all the data to twitter using HTTP::Request (I don't have Net::OAuth). My code: my $request = HTTP::Request-new(POST = $api_url); $request-header( authorization = 'OAuth realm=https://api.twitter.com/oauth/', oauth_nonce = $oauth_nonce, oauth_signature_method = $oauth_signature_method, oauth_timestamp = $oauth_timestamp, oauth_consumer_key = $oauth_consumer_key, oauth_token = $oauth_token, oauth_signature = $signature, oauth_version = $oauth_version status = $status ); $request-content_type(text/xml; charset=utf-8); my $res = $ua-request($request); Can someone help me? On Sep 3, 10:46 am, Tom van der Woerdt i...@tvdw.eu wrote: I usually use Wireshark for that, but it won't work with https:// connections. If you use cURL in PHP, there's an option for verbose output. I'm not sure about Perl, but Wireshark should help :) Tom On 9/3/10 10:42 AM, Lars wrote: I Tom, thanks for the validator! This is really a helpful tool. Can you explain me how to generat a dump of my http request? I have no idea how to do this in Perl. Thanks Best regards, Lars On Sep 3, 9:41 am, Tom van der Woerdt i...@tvdw.eu wrote: On 9/3/10 12:28 AM, Lars wrote: Why aren't my answers to Tom being displayed? No idea. I based my program on the exmaples I found underhttp://apiwiki.twitter.com/OAuth-Examples especially on the example of Scott Carterhttp://www.social.com/main/twitter-oauth-using-perl/. I followed his comment: # Add padding character to make a multiple of 4 per the # requirement of OAuth. $signature .= =; As long as the amount of characters is a multiple of 4, it's fine. :) I also noticed that you don't URL encode the values in $content. If I recall correctly, you have to URL encode those as well. I think I do encode them with my $signature_base_str = POST . uri_escape_RFC3986($api_url) . . uri_escape_RFC3986($content); correct? No, you need to urlencode the key/value as well, and later urlencode the complete body. If that was not the issue, then please show your Base String and the HTTP request. This is the base string: POSThttp%3A%2F2Fapi.twitter.com%2F1%2Fstatuses %2Fupdate.jsonoauth_consumer_key%3DXXX%26oauth_nonce %3D101%26oauth_signature_method%3DHMAC-SHA1%26oauth_timestamp %3D1272325550%26oauth_token%3DXXX%26oauth_version%3D1.0%26status %3DHello%20world Quoting my validator (http://quonos.nl/oauthTester/) : # Bad URL encoding! # Both key and value in the POST body need to be URL encoded. What do you mean with show us the HTTP request. I think I am doing the HTTP request with my $ua = LWP::UserAgent-new; my $req = POST($api_url = [ oauth_nonce = $oauth_nonce, oauth_signature_method = $oauth_signature_method, oauth_timestamp = $oauth_timestamp, oauth_consumer_key = $oauth_consumer_key, oauth_token = $oauth_token, oauth_signature = $signature, oauth_version = $oauth_version, status = $status ]); # Make the request my $res = $ua-request($req); Actually I meant a dump of the request you make, like the POST /endpoint HTTP/1.1 part, including headers. Tom On 3 Sep., 00:23, Lars lars_sa...@hotmail.com wrote: Sorry, I don't habe shell access... On 3 Sep., 00:20, Marc Mims marc.m...@gmail.com wrote: I am not a Perl expert but I have developed a small web page with Perl which is somewhat popular in Germany (according to Alexa trafic rank 1000). And this web site is tweeting important events using its own twitter account. I tried for days but I am not able to get it working (tweeting) again. I registered my web page/application and want to use my access tokens oauth_token and oauth_token_secret which I find under my application settings because I am using only this twitter account to tweet (seehttp://dev.twitter.com/pages/oauth_single_token) But the response is always 401 Unauthorized! Any ideas? My Perl program looks like this (my provider does not offer the module NET::Twitter) If you have shell access, you can probably install local::lib using the bootstrap method, then install Net::Twitter or Net::Twitter::Lite in your own directory. -Marc- Hide quoted text -
[twitter-dev] Re: home_timeline.json returning garbage between tweets
Seeing it here too. There's another thread about it as well.
On Sep 3, 8:14 pm, Fabian Schlenz m...@fabianonline.de wrote:
Hello.
Starting today (maybe yesterday, wasn't around to check) home_timeline
started sending garbage between the expected tweet objects. Since I
didn't modify my code in any way, I assume it's a bug (or a feature?) on
Twitter's side...
{normal
tweet},x mTێ 6 ں kYH M ( ٢/ 4 P BRqv { uq m
0o3s.3_ ,/M 5 u 22 l9²
2 {O Kr e ɞ cY +# u A +|刌
0 9Xp b8^6R{ Mp .) 3 V#?[ ; B\ \ =? Е u8 5D =g 4 m | _. _˗ 2F YX =9 P x Cق
Fi ^ t N` Ee SN 5 )k A l 1+sd D Q +S HN {Ů^ǣ
^1 8 a Z K2TU UL Bv- 1Vc ؠ ]p ef Y}:ۛZ %D pQ j 7pG 5 m X / fi 5 1'
3 2 V j} Zy$ ; H d 1Z`= u yZl
^+W c]+ /ױ' ' h S g S = 5 A W , 07 ~_ 0 } 6 7 ̀ d w{(3S
E Z Ķ [V { _ id- !刖 E 4 a ' % ^
P v_쾗 x n m {/ %E d B u
- J^T A O _d ݬc3I m_ Շ.ڣ M
=+ 7N / f KONcg KZ o | v \ ,+6 } -g H b*Ec@ ww t gȗ _ S ) g ȱ : jK Aky
XǠ g [? + ? ,{normal
tweet}
Am I the only one to see this behavior? Some of the requests return
correct data, but more often there's this garbage in the data throwing
my JSON parser off...
Regards,
Fabian Schlenz
--
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
http://groups.google.com/group/twitter-development-talk?hl=en
[twitter-dev] Re: Single Token: Using oauth with Perl: 401 Unauthorized
I think, I have the base string now, the signature and all the other data. I validated it with http://quonos.nl/oauthTester/ and everything is fine. However, I am still gettin 401 or 501 error. This is my base string: POSThttp%3A%2F%2Fapi.twitter.com%2F1%2Fstatuses %2Fupdate.xmloauth_consumer_key%3D0E1xSiyE03RTEms3WfQ%26oauth_nonce %3D11%26oauth_signature_method%3DHMAC-SHA1%26oauth_timestamp %3Doauth_timestamp%26oauth_token%3D88893619- JS87TMQDkUjM7Ufq119njayEJBuihVQmMEuTu3Ugi%26oauth_version %3D1.0%26status%3DHallo%252C%2520hier%2520ist%2520Lars I think I still don't know exactly how to send all the data to twitter using HTTP::Request (I don't have Net::OAuth). My code: my $request = HTTP::Request-new(POST = $api_url); $request-header( authorization = 'OAuth realm=https://api.twitter.com/oauth/', oauth_nonce = $oauth_nonce, oauth_signature_method = $oauth_signature_method, oauth_timestamp = $oauth_timestamp, oauth_consumer_key = $oauth_consumer_key, oauth_token = $oauth_token, oauth_signature = $signature, oauth_version = $oauth_version status = $status ); $request-content_type(text/xml; charset=utf-8); my $res = $ua-request($request); Can someone help me? On Sep 3, 10:46 am, Tom van der Woerdt i...@tvdw.eu wrote: I usually use Wireshark for that, but it won't work with https:// connections. If you use cURL in PHP, there's an option for verbose output. I'm not sure about Perl, but Wireshark should help :) Tom On 9/3/10 10:42 AM, Lars wrote: I Tom, thanks for the validator! This is really a helpful tool. Can you explain me how to generat a dump of my http request? I have no idea how to do this in Perl. Thanks Best regards, Lars On Sep 3, 9:41 am, Tom van der Woerdt i...@tvdw.eu wrote: On 9/3/10 12:28 AM, Lars wrote: Why aren't my answers to Tom being displayed? No idea. I based my program on the exmaples I found underhttp://apiwiki.twitter.com/OAuth-Examples especially on the example of Scott Carterhttp://www.social.com/main/twitter-oauth-using-perl/. I followed his comment: # Add padding character to make a multiple of 4 per the # requirement of OAuth. $signature .= =; As long as the amount of characters is a multiple of 4, it's fine. :) I also noticed that you don't URL encode the values in $content. If I recall correctly, you have to URL encode those as well. I think I do encode them with my $signature_base_str = POST . uri_escape_RFC3986($api_url) . . uri_escape_RFC3986($content); correct? No, you need to urlencode the key/value as well, and later urlencode the complete body. If that was not the issue, then please show your Base String and the HTTP request. This is the base string: POSThttp%3A%2F2Fapi.twitter.com%2F1%2Fstatuses %2Fupdate.jsonoauth_consumer_key%3DXXX%26oauth_nonce %3D101%26oauth_signature_method%3DHMAC-SHA1%26oauth_timestamp %3D1272325550%26oauth_token%3DXXX%26oauth_version%3D1.0%26status %3DHello%20world Quoting my validator (http://quonos.nl/oauthTester/) : # Bad URL encoding! # Both key and value in the POST body need to be URL encoded. What do you mean with show us the HTTP request. I think I am doing the HTTP request with my $ua = LWP::UserAgent-new; my $req = POST($api_url = [ oauth_nonce = $oauth_nonce, oauth_signature_method = $oauth_signature_method, oauth_timestamp = $oauth_timestamp, oauth_consumer_key = $oauth_consumer_key, oauth_token = $oauth_token, oauth_signature = $signature, oauth_version = $oauth_version, status = $status ]); # Make the request my $res = $ua-request($req); Actually I meant a dump of the request you make, like the POST /endpoint HTTP/1.1 part, including headers. Tom On 3 Sep., 00:23, Lars lars_sa...@hotmail.com wrote: Sorry, I don't habe shell access... On 3 Sep., 00:20, Marc Mims marc.m...@gmail.com wrote: I am not a Perl expert but I have developed a small web page with Perl which is somewhat popular in Germany (according to Alexa trafic rank 1000). And this web site is tweeting important events using its own twitter account. I tried for days but I am not able to get it working (tweeting) again. I registered my web page/application and want to use my access tokens oauth_token and oauth_token_secret which I find under my application settings because I am using only this twitter account to tweet (seehttp://dev.twitter.com/pages/oauth_single_token) But the response is always 401 Unauthorized! Any ideas? My Perl program looks like this (my provider does not offer the module NET::Twitter) If you have shell access, you can probably install local::lib using the bootstrap method, then install Net::Twitter or Net::Twitter::Lite in your own directory. -Marc -- Twitter developer
[twitter-dev] Re: garbage in json api response?
Same phenomenon occured in xml. URL is below http://api.twitter.com/1/statuses/user_timeline.xml?user_id=93771355 -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
Re: [twitter-dev] Radomly , 401 in my twitter api request when i use x-auth
which language is used? On Fri, Sep 3, 2010 at 11:44 AM, Karthik karthikduraisw...@gmail.comwrote: Dear all, I am getting radomly 401 (invalid signature ) error from server . I ma using the nonce as timestamp+random() ; (ramdom number) What could be the reason.. -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
Re: [twitter-dev] Are IDs globally unique? Or just unique for each object type?
Unique for each object type. On Fri, Sep 3, 2010 at 11:09 AM, Colin Howe colintheh...@googlemail.comwrote: Are IDs globally unique? Or just unique for each object type? In other words, is it possible to have a user with the ID 7 and also a DM with the ID 7? -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
[twitter-dev] Re: garbage in json api response?
+1, unable to parse timeline due to garbage in the XML feed. Many of our users are reporting the same problem. On Sep 3, 7:35 am, koujitaro kohura12345...@gmail.com wrote: Same phenomenon occured in xml. URL is belowhttp://api.twitter.com/1/statuses/user_timeline.xml?user_id=93771355 -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
[twitter-dev] Re: OAuth rate limit of 150
So just in case case someone else experience the same problem, I solved it by switching from version 0.9.8 to 0.9.7 of the Ruby Twitter Gem. Still not sure what the problem was, but I'm pretty sure I was properly authenticated since I could do things like updating lists. Regards Roger On Aug 31, 10:09 pm, Roger Ertesvåg webfo...@webfokus.no wrote: Hi Matt, thanks for your thorough response. So I assume this rate limit would be IP based then? I did some tests and got different rate limits on the server and on my development machine, which seems to support your theory that I'm not authenticated properly. After some more testing it seems that the problem is in the library, after switching to a previous version I get a rate limit of 350. I will do some more testing tomorrow to confirm this. Again, thanks for your help. Regards Roger On Aug 31, 8:34 pm, Matt Harris thematthar...@twitter.com wrote: Hey Roger, Thanks for sharing your code. A few things about the rate limits you are seeing: The 150 rate limit is for non-authenticated requests to the Twitter API. These requests happen when no user identifying details are sent. The 350 rate limit is for OAuth authenticated requests to the Twitter API. These requests happen when you send a user token and secret. As you are not authenticating with Basic Auth in any of your requests you would only see the unauthenticated rate limit (150) or your OAuth rate limit (350). The reason you could be seeing 150 is that the token and secret you have are no longer valid - although in that situation I would expect us to return an error saying Could not authenticate with OAuth. I'll be looking into other reasons why that might be happening later today. Hope that explains what you are seeing, Matt On Tue, Aug 31, 2010 at 12:39 AM, Roger Ertesvåg webfo...@webfokus.no wrote: Hi, I'm using the ruby twitter gem: http://github.com/jnunemaker/twitter So to set it up I do: oauth = Twitter::OAuth.new(CONFIG['twitter_key'], CONFIG['twitter_secret']) oauth.authorize_from_access(CONFIG['twitter_atoken'], CONFIG['twitter_asecret']) base = Twitter::Base.new(oauth) Then when I do: base.rate_limit_status I get: #Hashie::Mash hourly_limit=150 remaining_hits=150 reset_time=Tue Aug 31 08:26:37 + 2010 reset_time_in_seconds=1283243197 If I use the exact same code for other accounts I have I get: #Hashie::Mash hourly_limit=350 remaining_hits=350 reset_time=Tue Aug 31 08:22:40 + 2010 reset_time_in_seconds=1283242960 Also, if I was not authorized by OAuth shouldn't the limit be even lower? Regards Roger On Aug 31, 1:03 am, Matt Harris thematthar...@twitter.com wrote: Hi Roger, It sounds like the OAuth part of your request isn't being seen by our servers. A rate limit of 150 will be reported whenever you make a request without authorisation. Can you share the code you are using to make the requests so we can see what might be going wrong? Thanks, Matt On Mon, Aug 30, 2010 at 11:30 AM, Roger Ertesvåg webfo...@webfokus.no wrote: The OAuth rate limit for one of my accounts is stuck at 150. From what I'm reading, and seeing from other accounts I have, it is my understanding that it should be 350. What can I do to fix this? Regards Roger Ertesvag -- Twitter developer documentation and resources:http://dev.twitter.com/doc API updates via Twitter:http://twitter.com/twitterapi Issues/Enhancements Tracker:http://code.google.com/p/twitter-api/issues/list Change your membership to this group:http://groups.google.com/group/twitter-development-talk?hl=en -- Matt Harris Developer Advocate, Twitterhttp://twitter.com/themattharris -- Twitter developer documentation and resources:http://dev.twitter.com/doc API updates via Twitter:http://twitter.com/twitterapi Issues/Enhancements Tracker:http://code.google.com/p/twitter-api/issues/list Change your membership to this group:http://groups.google.com/group/twitter-development-talk?hl=en -- Matt Harris Developer Advocate, Twitterhttp://twitter.com/themattharris -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
Re: [twitter-dev] Re: garbage in json api response?
Twitterrific users have been seeing this for at least 2 hours, now. On Sep 3, 2010, at 8:47 AM, TheGuru wrote: +1, unable to parse timeline due to garbage in the XML feed. Many of our users are reporting the same problem. On Sep 3, 7:35 am, koujitaro kohura12345...@gmail.com wrote: Same phenomenon occured in xml. URL is belowhttp://api.twitter.com/1/statuses/user_timeline.xml?user_id=93771355 -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
[twitter-dev] Re: Are IDs globally unique? Or just unique for each object type?
Cool. Thanks for the help :) On Sep 3, 2:16 pm, John Kalucki j...@twitter.com wrote: Unique for each object type. On Fri, Sep 3, 2010 at 11:09 AM, Colin Howe colintheh...@googlemail.comwrote: Are IDs globally unique? Or just unique for each object type? In other words, is it possible to have a user with the ID 7 and also a DM with the ID 7? -- Twitter developer documentation and resources:http://dev.twitter.com/doc API updates via Twitter:http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
[twitter-dev] Tweet Button an understanding
At the moment I have placed the new tweet button onto one of our site, and also on several other pages within this site, now when I press the tweet button it all seems to work well and posts to my personal twitter account etc, but nothing show up on the tweet count section of the button, I was not a following the account I am using it on , but then I decided to follow and then it showed a number (1) so does this just display the number of followers to that account? What I want to happen is that it shows the amount of tweets have been shared via that button? Also on each page I have used the exact URL to that page so each one is different, but if I share any of those pages they do not show up as being shared, all I get is the same 1 total as in followers? How would I get it to display the different amounts fo reach page shared not followers to the account? The code I use ia as follows: in the head is: script src=http://platform.twitter.com/widgets.js; type=text/ javascript/script At the bottom of each page is: div a href=http://twitter.com/share; class=twitter-share-button data-url=http://www.HOMEPAGE.com; data-via=THETWITTERACCOUNT data-text=Text Here WHICH IS DIFFERENT A S WELL data-related= data-count=Tweet/a /div On each page I change the following: inner page1: data-url=http://www.HOMEPAGE.com/pageone.php; data-text=Text Here page one text inner page2: data-url=http://www.HOMEPAGE.com/pagetwo.php; data-text=Text Here page twotext Many thanks for the assistance Si -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
Re: [twitter-dev] Re: Single Token: Using oauth with Perl: 401 Unauthorized
I just looked up the Perl documentation for HTTP::Request and while I'm not really a Perl programmer, I *think* that this page can help you turn on verbose logging for requests : http://search.cpan.org/~gaas/libwww-perl-5.836/lib/HTTP/Config.pm Also, I noticed that you typed authorization instead of Authorization. It could make a difference. Also, you seem to send a content-type of text/xml. Are you sending XML data? Another thing I noticed is that you seem to send status as a header. It's a POST value. The same goes for the oauth_* parameters, which are supposed to be part of the Authorization: header. Tom On 9/3/10 2:25 PM, Lars wrote: I think, I have the base string now, the signature and all the other data. I validated it with http://quonos.nl/oauthTester/ and everything is fine. However, I am still gettin 401 or 501 error. This is my base string: POSThttp%3A%2F%2Fapi.twitter.com%2F1%2Fstatuses %2Fupdate.xmloauth_consumer_key%3D0E1xSiyE03RTEms3WfQ%26oauth_nonce %3D11%26oauth_signature_method%3DHMAC-SHA1%26oauth_timestamp %3Doauth_timestamp%26oauth_token%3D88893619- JS87TMQDkUjM7Ufq119njayEJBuihVQmMEuTu3Ugi%26oauth_version %3D1.0%26status%3DHallo%252C%2520hier%2520ist%2520Lars I think I still don't know exactly how to send all the data to twitter using HTTP::Request (I don't have Net::OAuth). My code: my $request = HTTP::Request-new(POST = $api_url); $request-header( authorization = 'OAuth realm=https://api.twitter.com/oauth/', oauth_nonce = $oauth_nonce, oauth_signature_method = $oauth_signature_method, oauth_timestamp = $oauth_timestamp, oauth_consumer_key = $oauth_consumer_key, oauth_token = $oauth_token, oauth_signature = $signature, oauth_version = $oauth_version status = $status ); $request-content_type(text/xml; charset=utf-8); my $res = $ua-request($request); Can someone help me? On Sep 3, 10:46 am, Tom van der Woerdt i...@tvdw.eu wrote: I usually use Wireshark for that, but it won't work with https:// connections. If you use cURL in PHP, there's an option for verbose output. I'm not sure about Perl, but Wireshark should help :) Tom On 9/3/10 10:42 AM, Lars wrote: I Tom, thanks for the validator! This is really a helpful tool. Can you explain me how to generat a dump of my http request? I have no idea how to do this in Perl. Thanks Best regards, Lars On Sep 3, 9:41 am, Tom van der Woerdt i...@tvdw.eu wrote: On 9/3/10 12:28 AM, Lars wrote: Why aren't my answers to Tom being displayed? No idea. I based my program on the exmaples I found underhttp://apiwiki.twitter.com/OAuth-Examples especially on the example of Scott Carterhttp://www.social.com/main/twitter-oauth-using-perl/. I followed his comment: # Add padding character to make a multiple of 4 per the # requirement of OAuth. $signature .= =; As long as the amount of characters is a multiple of 4, it's fine. :) I also noticed that you don't URL encode the values in $content. If I recall correctly, you have to URL encode those as well. I think I do encode them with my $signature_base_str = POST . uri_escape_RFC3986($api_url) . . uri_escape_RFC3986($content); correct? No, you need to urlencode the key/value as well, and later urlencode the complete body. If that was not the issue, then please show your Base String and the HTTP request. This is the base string: POSThttp%3A%2F2Fapi.twitter.com%2F1%2Fstatuses %2Fupdate.jsonoauth_consumer_key%3DXXX%26oauth_nonce %3D101%26oauth_signature_method%3DHMAC-SHA1%26oauth_timestamp %3D1272325550%26oauth_token%3DXXX%26oauth_version%3D1.0%26status %3DHello%20world Quoting my validator (http://quonos.nl/oauthTester/) : # Bad URL encoding! # Both key and value in the POST body need to be URL encoded. What do you mean with show us the HTTP request. I think I am doing the HTTP request with my $ua = LWP::UserAgent-new; my $req = POST($api_url = [ oauth_nonce = $oauth_nonce, oauth_signature_method = $oauth_signature_method, oauth_timestamp = $oauth_timestamp, oauth_consumer_key = $oauth_consumer_key, oauth_token = $oauth_token, oauth_signature = $signature, oauth_version = $oauth_version, status = $status ]); # Make the request my $res = $ua-request($req); Actually I meant a dump of the request you make, like the POST /endpoint HTTP/1.1 part, including headers. Tom On 3 Sep., 00:23, Lars lars_sa...@hotmail.com wrote: Sorry, I don't habe shell access... On 3 Sep., 00:20, Marc Mims marc.m...@gmail.com wrote: I am not a Perl expert but I have developed a small web page with Perl which is somewhat popular in Germany (according to Alexa trafic rank 1000). And this web site is tweeting important events using its own twitter account. I tried for days but I am not able to get it working (tweeting) again. I
[twitter-dev] Retweet results in 401: Unauthorized
Whilst the docs state no authorization is required. I think I'm doing something wrong with the OAuth fields I send. But I have yet to find out exactly what and how to fix it. I've tried the 'text/xml; charset=utf-8' content-type, but this results in the same message. Sniffed: POST /1/statuses/retweet/22684354355.xml HTTP/1.1 Content-Type: application/x-www-form-urlencoded User-Agent: RTL Netherlands OAuth Consumer Authorization: OAuth oauth_callback=http%3A%2F%2Fwww.rtl.nl %2Fexperience%2Frtlnl%2F, oauth_consumer_key=I1yQDPyI7WUn2fN9JfFWww, oauth_signature_method=HMAC-SHA1, oauth_timestamp=1283523528, oauth_nonce=uupiA1mAr22CmX3D3Lou73hDV7yIYP9G9YjsyuhGN%2FQ%3D, oauth_version=1.0, oauth_signature=9HWVDDiftaW%2BZaOxNB692zBop1k %3D Host: api.twitter.com HTTP/1.1 401 Unauthorized Date: Fri, 03 Sep 2010 14:18:49 GMT Server: hi Status: 401 Unauthorized WWW-Authenticate: Basic realm=Twitter API X-Runtime: 0.00591 Content-Type: application/xml; charset=utf-8 Content-Length: 163 Cache-Control: no-cache, max-age=1800 Set-Cookie: k=217.118.160.30.1283523529311927; path=/; expires=Fri, 10- Sep-10 14:18:49 GMT; domain=.twitter.com Set-Cookie: guest_id=128352352931668878; path=/; expires=Sun, 03 Oct 2010 14:18:49 GMT Set-Cookie: _twitter_sess=BAh7CDoPY3JlYXRlZF9hdGwrCGjK9tcqAToHaWQiJTFiYTNiMDlmMzZmNzdi %250AODJjMWRiMmY2OTMyODQ4ZTU0IgpmbGFzaElDOidBY3Rpb25Db250cm9sbGVy %250AOjpGbGFzaDo6Rmxhc2hIYXNoewAGOgpAdXNlZHsA--53471a68a90cd817bfe9063a156fd56d031dbd4f; domain=.twitter.com; path=/ Expires: Fri, 03 Sep 2010 14:48:49 GMT Vary: Accept-Encoding Connection: close ?xml version=1.0 encoding=UTF-8? hash request/1/statuses/retweet/22684354355.xml/request errorCould not authenticate with OAuth./error /hash -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
Re: [twitter-dev] Retweet results in 401: Unauthorized
I'm pretty sure that /1/statuses/retweet requires authorization ;-) There's one thing I see: * You are sending a oauth_callback where it's not needed. There's something I like to see: * Your Base String to verify that you are sending the right stuff. Tom On 9/3/10 4:39 PM, Papa.Coen wrote: Whilst the docs state no authorization is required. I think I'm doing something wrong with the OAuth fields I send. But I have yet to find out exactly what and how to fix it. I've tried the 'text/xml; charset=utf-8' content-type, but this results in the same message. Sniffed: POST /1/statuses/retweet/22684354355.xml HTTP/1.1 Content-Type: application/x-www-form-urlencoded User-Agent: RTL Netherlands OAuth Consumer Authorization: OAuth oauth_callback=http%3A%2F%2Fwww.rtl.nl %2Fexperience%2Frtlnl%2F, oauth_consumer_key=I1yQDPyI7WUn2fN9JfFWww, oauth_signature_method=HMAC-SHA1, oauth_timestamp=1283523528, oauth_nonce=uupiA1mAr22CmX3D3Lou73hDV7yIYP9G9YjsyuhGN%2FQ%3D, oauth_version=1.0, oauth_signature=9HWVDDiftaW%2BZaOxNB692zBop1k %3D Host: api.twitter.com HTTP/1.1 401 Unauthorized Date: Fri, 03 Sep 2010 14:18:49 GMT Server: hi Status: 401 Unauthorized WWW-Authenticate: Basic realm=Twitter API X-Runtime: 0.00591 Content-Type: application/xml; charset=utf-8 Content-Length: 163 Cache-Control: no-cache, max-age=1800 Set-Cookie: k=217.118.160.30.1283523529311927; path=/; expires=Fri, 10- Sep-10 14:18:49 GMT; domain=.twitter.com Set-Cookie: guest_id=128352352931668878; path=/; expires=Sun, 03 Oct 2010 14:18:49 GMT Set-Cookie: _twitter_sess=BAh7CDoPY3JlYXRlZF9hdGwrCGjK9tcqAToHaWQiJTFiYTNiMDlmMzZmNzdi %250AODJjMWRiMmY2OTMyODQ4ZTU0IgpmbGFzaElDOidBY3Rpb25Db250cm9sbGVy %250AOjpGbGFzaDo6Rmxhc2hIYXNoewAGOgpAdXNlZHsA--53471a68a90cd817bfe9063a156fd56d031dbd4f; domain=.twitter.com; path=/ Expires: Fri, 03 Sep 2010 14:48:49 GMT Vary: Accept-Encoding Connection: close ?xml version=1.0 encoding=UTF-8? hash request/1/statuses/retweet/22684354355.xml/request errorCould not authenticate with OAuth./error /hash -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
[twitter-dev] Re: Retweet results in 401: Unauthorized
Says here: http://dev.twitter.com/doc/post/statuses/retweet/:id It's on the internets, so it's true :) I was toying around with oauth_... header parameters. I get the same message when leaving the callback out. I thought maybe that was the problem (not having a callback at first) Base string: POSThttp%3A%2F%2Fapi.twitter.com%2F1%2Fstatuses%2Fretweet %2F2404341.xmloauth_callback%3Dhttp%253A%252F%252Fwww.rtl.nl %252Fexperience%252Frtlnl%252F%26oauth_consumer_key %3DI1yQDPyI7WUn2fN9JfFWww%26oauth_nonce %3DYmzNuZ4t6L1uYhzxFzvLjKWTyFoEVE9pyAz569zsX4g%253D %26oauth_signature_method%3DHMAC-SHA1%26oauth_timestamp %3D1283524907%26oauth_version%3D1.0 Again, you can leave out the callback part. On Sep 3, 4:46 pm, Tom van der Woerdt i...@tvdw.eu wrote: I'm pretty sure that /1/statuses/retweet requires authorization ;-) There's one thing I see: * You are sending a oauth_callback where it's not needed. There's something I like to see: * Your Base String to verify that you are sending the right stuff. Tom On 9/3/10 4:39 PM, Papa.Coen wrote: Whilst the docs state no authorization is required. I think I'm doing something wrong with the OAuth fields I send. But I have yet to find out exactly what and how to fix it. I've tried the 'text/xml; charset=utf-8' content-type, but this results in the same message. Sniffed: POST /1/statuses/retweet/22684354355.xml HTTP/1.1 Content-Type: application/x-www-form-urlencoded User-Agent: RTL Netherlands OAuth Consumer Authorization: OAuth oauth_callback=http%3A%2F%2Fwww.rtl.nl %2Fexperience%2Frtlnl%2F, oauth_consumer_key=I1yQDPyI7WUn2fN9JfFWww, oauth_signature_method=HMAC-SHA1, oauth_timestamp=1283523528, oauth_nonce=uupiA1mAr22CmX3D3Lou73hDV7yIYP9G9YjsyuhGN%2FQ%3D, oauth_version=1.0, oauth_signature=9HWVDDiftaW%2BZaOxNB692zBop1k %3D Host: api.twitter.com HTTP/1.1 401 Unauthorized Date: Fri, 03 Sep 2010 14:18:49 GMT Server: hi Status: 401 Unauthorized WWW-Authenticate: Basic realm=Twitter API X-Runtime: 0.00591 Content-Type: application/xml; charset=utf-8 Content-Length: 163 Cache-Control: no-cache, max-age=1800 Set-Cookie: k=217.118.160.30.1283523529311927; path=/; expires=Fri, 10- Sep-10 14:18:49 GMT; domain=.twitter.com Set-Cookie: guest_id=128352352931668878; path=/; expires=Sun, 03 Oct 2010 14:18:49 GMT Set-Cookie: _twitter_sess=BAh7CDoPY3JlYXRlZF9hdGwrCGjK9tcqAToHaWQiJTFiYTNiMDlmMzZmNzdi %250AODJjMWRiMmY2OTMyODQ4ZTU0IgpmbGFzaElDOidBY3Rpb25Db250cm9sbGVy %250AOjpGbGFzaDo6Rmxhc2hIYXNoewAGOgpAdXNlZHsA--53471a68a90cd817bfe9063a156fd56d031dbd4f; domain=.twitter.com; path=/ Expires: Fri, 03 Sep 2010 14:48:49 GMT Vary: Accept-Encoding Connection: close ?xml version=1.0 encoding=UTF-8? hash request/1/statuses/retweet/22684354355.xml/request errorCould not authenticate with OAuth./error /hash -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
Re: [twitter-dev] Re: Retweet results in 401: Unauthorized
I just noticed that you are not sending an oauth_token. You really need it for this request ;-) Tom On 9/3/10 4:52 PM, Papa.Coen wrote: Says here: http://dev.twitter.com/doc/post/statuses/retweet/:id It's on the internets, so it's true :) I was toying around with oauth_... header parameters. I get the same message when leaving the callback out. I thought maybe that was the problem (not having a callback at first) Base string: POSThttp%3A%2F%2Fapi.twitter.com%2F1%2Fstatuses%2Fretweet %2F2404341.xmloauth_callback%3Dhttp%253A%252F%252Fwww.rtl.nl %252Fexperience%252Frtlnl%252F%26oauth_consumer_key %3DI1yQDPyI7WUn2fN9JfFWww%26oauth_nonce %3DYmzNuZ4t6L1uYhzxFzvLjKWTyFoEVE9pyAz569zsX4g%253D %26oauth_signature_method%3DHMAC-SHA1%26oauth_timestamp %3D1283524907%26oauth_version%3D1.0 Again, you can leave out the callback part. On Sep 3, 4:46 pm, Tom van der Woerdt i...@tvdw.eu wrote: I'm pretty sure that /1/statuses/retweet requires authorization ;-) There's one thing I see: * You are sending a oauth_callback where it's not needed. There's something I like to see: * Your Base String to verify that you are sending the right stuff. Tom On 9/3/10 4:39 PM, Papa.Coen wrote: Whilst the docs state no authorization is required. I think I'm doing something wrong with the OAuth fields I send. But I have yet to find out exactly what and how to fix it. I've tried the 'text/xml; charset=utf-8' content-type, but this results in the same message. Sniffed: POST /1/statuses/retweet/22684354355.xml HTTP/1.1 Content-Type: application/x-www-form-urlencoded User-Agent: RTL Netherlands OAuth Consumer Authorization: OAuth oauth_callback=http%3A%2F%2Fwww.rtl.nl %2Fexperience%2Frtlnl%2F, oauth_consumer_key=I1yQDPyI7WUn2fN9JfFWww, oauth_signature_method=HMAC-SHA1, oauth_timestamp=1283523528, oauth_nonce=uupiA1mAr22CmX3D3Lou73hDV7yIYP9G9YjsyuhGN%2FQ%3D, oauth_version=1.0, oauth_signature=9HWVDDiftaW%2BZaOxNB692zBop1k %3D Host: api.twitter.com HTTP/1.1 401 Unauthorized Date: Fri, 03 Sep 2010 14:18:49 GMT Server: hi Status: 401 Unauthorized WWW-Authenticate: Basic realm=Twitter API X-Runtime: 0.00591 Content-Type: application/xml; charset=utf-8 Content-Length: 163 Cache-Control: no-cache, max-age=1800 Set-Cookie: k=217.118.160.30.1283523529311927; path=/; expires=Fri, 10- Sep-10 14:18:49 GMT; domain=.twitter.com Set-Cookie: guest_id=128352352931668878; path=/; expires=Sun, 03 Oct 2010 14:18:49 GMT Set-Cookie: _twitter_sess=BAh7CDoPY3JlYXRlZF9hdGwrCGjK9tcqAToHaWQiJTFiYTNiMDlmMzZmNzdi %250AODJjMWRiMmY2OTMyODQ4ZTU0IgpmbGFzaElDOidBY3Rpb25Db250cm9sbGVy %250AOjpGbGFzaDo6Rmxhc2hIYXNoewAGOgpAdXNlZHsA--53471a68a90cd817bfe9063a156fd56d031dbd4f; domain=.twitter.com; path=/ Expires: Fri, 03 Sep 2010 14:48:49 GMT Vary: Accept-Encoding Connection: close ?xml version=1.0 encoding=UTF-8? hash request/1/statuses/retweet/22684354355.xml/request errorCould not authenticate with OAuth./error /hash -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
[twitter-dev] Bad characters in statuses/home_timeline JSON
In some tweets, I'm seeing non-UTF8 characters being returned which breaks the JSON. I notice it after contributors_enabled in the user object. -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
[twitter-dev] Re: garbage in json api response?
I see it too. Here's a cached version of the response: http://app.apigee.com/console/apigee-console-snapshots-128331720_b7a1fe22-6ec8-4996-ba1a-2720227c896c/rendersnapshotview The same request with xml seems to be working fine: http://app.apigee.com/console/apigee-console-snapshots-128331720_66477219-251e-401e-8c74-f16e2a504483/rendersnapshotview -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
[twitter-dev] Re: garbage in json api response?
Thanks for the information collected on this. We're investigating this issue at the moment and updates will be posted to our status blog: http://status.twitter.com/post/1058895068/investigating-invalid-responses-from-the-api Matt On Sep 3, 8:44 am, Marsh Gardiner ma...@apigee.com wrote: I see it too. Here's a cached version of the response:http://app.apigee.com/console/apigee-console-snapshots-128331720_... The same request with xml seems to be working fine:http://app.apigee.com/console/apigee-console-snapshots-128331720_... -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
[twitter-dev] Re: garbage in json api response?
For what it's worth, I confirm the issue for paper.li - invalid json response on home_timeline and list statuses - unparseable json format. On Sep 3, 12:57 pm, gabriele renzi rff@gmail.com wrote: Hi everyone, I am noticing that my home timeline and that of a few other people is returning some messed up stuff, basically intemingling something that looks like a random sequence of bytes to normal messages. You can in theory verify this by accessing my home timeline (@riffraff) and requesting 200 messages, or using the public_timeline for the user @puredanger such as curl 'api.twitter.com/1/statuses/user_timeline.json?screen_name=puredangercount =48since_id=22815626427max_id=22857673035' Sorry I could not reduce this to a simpler sample. This appears to happen only with the json apis, the xml ones seem to report reasonable code. Can someone else confirm this? -- blog en:http://www.riffraff.info blog it:http://riffraff.blogsome.com -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
[twitter-dev] Garbage characters in home_timeline json response
Hi, I found that for some of the accounts the home tweets api (home_timeline.json) is returning garbage characters. I also found that these garbage characters are coming in between the first and the last tweet. Does some one else also facing this problem? I'm expecting this to be the twitter bug. Please fix it. - Praneeth -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
[twitter-dev] ERROR The requested URL could not be retrieved
While looping follow / unfollow, returning this error: ERROR The requested URL could not be retrieved whats that? thanks -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
[twitter-dev] Curl question
I have a really small app that uses curl in a perl script.. automated stuff like updates, when emails were sent out, stuff like that. It stopped sending tweets to my account about a day ago and won't work from the command line. Does twitter now consider this stuff an app I have to register for?? I can;t find any documentation on any of this, just full-blown public apps. Anyone know if I can use a system call from a perl script using curl anymore or is this all gone? What if I use http://api.twitter.com/statuses/update.xml instead? Seems overcomplicated to something that was dead simple... -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
Re: [twitter-dev] Garbage characters in home_timeline json response
http://status.twitter.com/post/1058895068/investigating-invalid-responses-from-the-api The issue is known. Just wait until it's fixed. Tom On 9/3/10 4:14 PM, Praneeth Kanchana wrote: Hi, I found that for some of the accounts the home tweets api (home_timeline.json) is returning garbage characters. I also found that these garbage characters are coming in between the first and the last tweet. Does some one else also facing this problem? I'm expecting this to be the twitter bug. Please fix it. - Praneeth -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
Re: [twitter-dev] Bad characters in statuses/home_timeline JSON
We're investigating this issue at the moment and updates will be posted to our status blog: http://status.twitter.com/post/1058895068/investigating-invalid-respo... Matt On Fri, Sep 3, 2010 at 8:00 AM, Aaron Rankin aran...@sproutsocial.com wrote: In some tweets, I'm seeing non-UTF8 characters being returned which breaks the JSON. I notice it after contributors_enabled in the user object. -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en -- Matt Harris Developer Advocate, Twitter http://twitter.com/themattharris -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
Re: [twitter-dev] Re: OAuth rate limit of 150
Hey Roger, Thanks for posting the solution which worked for you and glad it was sorted out. For completeness the answer to your question about getting a different rate limit on a different IP is expected if authentication isn't happening. This is because each IP has it's own 150 requests. Best, Matt On Fri, Sep 3, 2010 at 7:09 AM, Roger Ertesvåg webfo...@webfokus.no wrote: So just in case case someone else experience the same problem, I solved it by switching from version 0.9.8 to 0.9.7 of the Ruby Twitter Gem. Still not sure what the problem was, but I'm pretty sure I was properly authenticated since I could do things like updating lists. Regards Roger On Aug 31, 10:09 pm, Roger Ertesvåg webfo...@webfokus.no wrote: Hi Matt, thanks for your thorough response. So I assume this rate limit would be IP based then? I did some tests and got different rate limits on the server and on my development machine, which seems to support your theory that I'm not authenticated properly. After some more testing it seems that the problem is in the library, after switching to a previous version I get a rate limit of 350. I will do some more testing tomorrow to confirm this. Again, thanks for your help. Regards Roger On Aug 31, 8:34 pm, Matt Harris thematthar...@twitter.com wrote: Hey Roger, Thanks for sharing your code. A few things about the rate limits you are seeing: The 150 rate limit is for non-authenticated requests to the Twitter API. These requests happen when no user identifying details are sent. The 350 rate limit is for OAuth authenticated requests to the Twitter API. These requests happen when you send a user token and secret. As you are not authenticating with Basic Auth in any of your requests you would only see the unauthenticated rate limit (150) or your OAuth rate limit (350). The reason you could be seeing 150 is that the token and secret you have are no longer valid - although in that situation I would expect us to return an error saying Could not authenticate with OAuth. I'll be looking into other reasons why that might be happening later today. Hope that explains what you are seeing, Matt On Tue, Aug 31, 2010 at 12:39 AM, Roger Ertesvåg webfo...@webfokus.no wrote: Hi, I'm using the ruby twitter gem: http://github.com/jnunemaker/twitter So to set it up I do: oauth = Twitter::OAuth.new(CONFIG['twitter_key'], CONFIG['twitter_secret']) oauth.authorize_from_access(CONFIG['twitter_atoken'], CONFIG['twitter_asecret']) base = Twitter::Base.new(oauth) Then when I do: base.rate_limit_status I get: #Hashie::Mash hourly_limit=150 remaining_hits=150 reset_time=Tue Aug 31 08:26:37 + 2010 reset_time_in_seconds=1283243197 If I use the exact same code for other accounts I have I get: #Hashie::Mash hourly_limit=350 remaining_hits=350 reset_time=Tue Aug 31 08:22:40 + 2010 reset_time_in_seconds=1283242960 Also, if I was not authorized by OAuth shouldn't the limit be even lower? Regards Roger On Aug 31, 1:03 am, Matt Harris thematthar...@twitter.com wrote: Hi Roger, It sounds like the OAuth part of your request isn't being seen by our servers. A rate limit of 150 will be reported whenever you make a request without authorisation. Can you share the code you are using to make the requests so we can see what might be going wrong? Thanks, Matt On Mon, Aug 30, 2010 at 11:30 AM, Roger Ertesvåg webfo...@webfokus.no wrote: The OAuth rate limit for one of my accounts is stuck at 150. From what I'm reading, and seeing from other accounts I have, it is my understanding that it should be 350. What can I do to fix this? Regards Roger Ertesvag -- Twitter developer documentation and resources:http://dev.twitter.com/doc API updates via Twitter:http://twitter.com/twitterapi Issues/Enhancements Tracker:http://code.google.com/p/twitter-api/issues/list Change your membership to this group:http://groups.google.com/group/twitter-development-talk?hl=en -- Matt Harris Developer Advocate, Twitterhttp://twitter.com/themattharris -- Twitter developer documentation and resources:http://dev.twitter.com/doc API updates via Twitter:http://twitter.com/twitterapi Issues/Enhancements Tracker:http://code.google.com/p/twitter-api/issues/list Change your membership to this group:http://groups.google.com/group/twitter-development-talk?hl=en -- Matt Harris Developer Advocate, Twitterhttp://twitter.com/themattharris -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en -- Matt Harris Developer
Re: [twitter-dev] Simple status update
Hey Tomáš, There are a number of libraries on our developer resources site which handle OAuth in PHP: http://dev.twitter.com/pages/oauth_libraries#php Remember OAuth uses a consumer key and secret to identify an application, and a user token and secret for the user. This means you will need to have an application registered on http://dev.twitter.com/apps/new before you can Tweet using OAuth. When you have created your application there will be a button on the right of the screen labelled My Access Token. In there you will find the user token and secret that will identify you using OAuth. Some examples of using the single token can be found here: http://dev.twitter.com/pages/oauth_single_token Hope that helps, Matt On Thu, Sep 2, 2010 at 5:26 PM, Tomáš Pospíšil pospis...@gmail.com wrote: Hi, I'm trying to update my twitter status every time, when new post appears on my website. I found several classes (in PHP), but none of them works, because they don't implement OAuth. Classes which implement OAuth let anybody update their status through my page. But that is not the functionality I need. Maybe I'm blind, but there wasn't any field or variable, where i could set my username, password and new status message and let the class do the rest of the work... Please, if you know about some class, that can do what I need, or at least some tutorial let me know, it would be very helpful. Thank you! -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en -- Matt Harris Developer Advocate, Twitter http://twitter.com/themattharris -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
[twitter-dev] t.co and fail whales
Twitter folks, how are you going to ensure that t.co links are not affected by over-capacity situations on your infrastructure? If you're routing t.co links through your existing infrastructure, absolutely *everyone's* links are going to be broken when you start throwing fail whales, even when the link is clicked in third-party applications. Are you running t.co on its own separate and dedicated infrastructure? -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
Re: [twitter-dev] Re: Automated OAuth
Hey Cradash, Where do the username and password come from that you use? If they are entered by a user you can handle the OAuth flow at that time. Once you have an OAuth user token and secret it does not expire and will continue to work until either the user revokes access to the application, or the applications keys are changed. This means that when you have the user token and secret you store that instead of the username and password, and use those details to make requests to the API. There is more information about converting Basic to OAuth on our developer resources site: http://dev.twitter.com/pages/basic_to_oauth Hope that helps, Matt On Thu, Sep 2, 2010 at 4:57 PM, Cradash rand...@gmail.com wrote: Yes, but I have not found a way to have the server go out with the consumer Key/secret then get the id # programmaticly, that's what I was looking for. On Sep 3, 9:44 am, Taylor Singletary taylorsinglet...@twitter.com wrote: Each Twitter feed in this case is a user. On Thursday, September 2, 2010, Cradash rand...@gmail.com wrote: Unfortunately that is not an option for us as we have no 'users'. We have a server that gleans information then posts it into twitter feeds, all automated. -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en -- Matt Harris Developer Advocate, Twitter http://twitter.com/themattharris -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
Re: [twitter-dev] Re: Error 401 only in Target (working fine in simulator)
Hey Karthik, If some methods are returning 401 and others are succeeding it sounds like your encoding could be going wrong. Can you share the calls which 401 and a couple that are successful so we can see what maybe happening. It would be helpful to see the Auth header and signature base string for each request. Best, Matt On Thu, Sep 2, 2010 at 11:26 PM, Karthik karthikduraisw...@gmail.com wrote: Dear Taylor, I am getting one new issue. In my application , randomly some api's returns 401 - invalid signature error... I am not sure whether twitter server only returns 401 randomly or some problem in my request..? Most of the time my requests are working fine... Please help me out Regards, On Sep 1, 9:34 pm, Taylor Singletary taylorsinglet...@twitter.com wrote: Hi Karthik, Make sure that the time on your device is in sync with Twitter's clocks. We return our current time in the Date HTTP header of every response. One easy way to fixate an application's clock with our servers is to issue a HTTP HEAD request tohttp://api.twitter.com/1/help/test.xml-- it's a non-rate-limited request and will allow you to adjust your clock in relation to ours. The oauth_timestamp in your example here is for Dec 31st, 2009. Taylor On Wed, Sep 1, 2010 at 9:10 AM, Karthik karthikduraisw...@gmail.com wrote: Hi , I am developing a Twitter application in MTK (Media tek ) platform. I am using Oauth and and My application has the X-auth permission I am first using POST with required params and the am using below URL https://api.twitter.com/oauth/access_token to get the access token in exchange with the username, password. I am able to get the access token and My application is working fine in the simulator (I ma using the proxy server in simulator) But in the Mobile (I amm not using proxy) , when I post https://api.twitter.com/oauth/access_token I am always getting 401 - Unauthorized (Failed to validate oauth signature and token) The below is my sample input string to get the signature (hmac-sha1) POSThttp%3A%2F%2Fapi.twitter.com%2Foauth %2Faccess_tokenoauth_consumer_key%3D4dsadsadsasdsd%26oauth_nonce %3D1262304301%26oauth_signature_method%3DHMAC-SHA1%26oauth_timestamp %3D1262304300%26oauth_version%3D1.0%26x_auth_mode%3Dclient_auth %26x_auth_password%3Dtest1234%26x_auth_username%3Dnareshs %2540google.com Please someone help me to resolve this issue.. -- Twitter developer documentation and resources:http://dev.twitter.com/doc API updates via Twitter:http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en -- Matt Harris Developer Advocate, Twitter http://twitter.com/themattharris -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
Re: [twitter-dev] retweeted always returing as false in /1/statuses/user_timeline.json
Hi Michael, Soon after launching those fields we identified some problems with them so had to disable them. That means the behavior you are seeing is expected right now. When the fields are enabled again we'll announce it to this mailing list. Best, Matt On Thu, Sep 2, 2010 at 9:04 PM, Michael Babker mbab...@flbab.com wrote: Hi there, I have a Twitter module I'm improving upon which pulls tweets from /1/statuses/user_timeline.json. An issue that I've noticed is that over the last couple of days, tweets I've retweeted using the retweet link on twitter.com have continued to display as retweeted: false in the JSON. Can someone tell me if this is normal behavior or if it's an issue with the API? Thanks! -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en -- Matt Harris Developer Advocate, Twitter http://twitter.com/themattharris -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
Re: [twitter-dev] Twitter MOSS Webpart
Hi Sanjeet, All of our API and important information is described on our developer resources website: http://dev.twitter.com/doc There are also community provided libraries to assist you with creating an application or learning how to interact with the API in your preferred language. You can find these here: http://dev.twitter.com/pages/oauth_libraries If you have any questions when developing your application you can always ask them in this mailing list. Hope that helps, Matt On Thu, Sep 2, 2010 at 11:23 PM, Sanjeet sinha.sanj...@gmail.com wrote: Hi, I am MOSS 2007 developer, I want to create a new Twitter webpart to display Tweets on my WebPart. Can you please help, how i can interact with Twitter services to pick tweets. Regards, Sanjeet -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en -- Matt Harris Developer Advocate, Twitter http://twitter.com/themattharris -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
[twitter-dev] Re: Change in error response objects
Raffi,
I have been using the API to tweet twice daily for months, but my
script suddenly stopped working yesterday morning. I am posting to
this page using a curl connection
http://twitter.com/statuses/update.xml
and it keeps returning a 401 error. I have verified that my username
password have not changed. Does the error have something to do with
the changes you made? How can I fix this?
Thanks!
Steve
SEJohnsen at gmail.com
$mypost=$data['post'];
$twitter_user = user;
$twitter_password = pwd;
$twitter_api_url = http://twitter.com/statuses/update.xml;;
$twitter_data = status=.$mypost;
$ch = curl_init($twitter_api_url);
curl_setopt($ch, CURLOPT_POST, 1);
curl_setopt($ch, CURLOPT_POSTFIELDS, $twitter_data);
curl_setopt($ch, CURLOPT_FOLLOWLOCATION, 1);
curl_setopt($ch, CURLOPT_HEADER, 0);
curl_setopt($ch, CURLOPT_RETURNTRANSFER, 1);
curl_setopt($ch, CURLOPT_USERPWD, {$twitter_user}:
{$twitter_password});
$twitter_data = curl_exec($ch);
$httpcode = curl_getinfo($ch, CURLINFO_HTTP_CODE);
curl_close($ch);
On Aug 27, 7:03 am, Raffi Krikorian ra...@twitter.com wrote:
hi all.
this is most certainly a mistake on our part - we'll be reverting this
change.
On Fri, Aug 27, 2010 at 4:45 AM, Cameron Kaiser spec...@floodgap.comwrote:
It looks like error responses have changed, at least for users/show.
I used to get:
{error:User has been suspended}
Now, I get:
{errors:[{code:63,message:User has been suspended}]}
I'm seeing that too. When did this change?
--
personal:
http://www.cameronkaiser.com/--
Cameron Kaiser * Floodgap Systems *www.floodgap.com*
ckai...@floodgap.com
-- They told me I was gullible ... and I believed them.
---
--
Twitter developer documentation and resources:http://dev.twitter.com/doc
API updates via Twitter:http://twitter.com/twitterapi
Issues/Enhancements Tracker:
http://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
http://groups.google.com/group/twitter-development-talk?hl=en
--
Raffi Krikorian
Twitter Platform Teamhttp://twitter.com/raffi
--
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
http://groups.google.com/group/twitter-development-talk?hl=en
Re: [twitter-dev] Re: Change in error response objects
http://dev.twitter.com/announcements
Tom
On 9/3/10 6:35 PM, MrMoxy wrote:
Raffi,
I have been using the API to tweet twice daily for months, but my
script suddenly stopped working yesterday morning. I am posting to
this page using a curl connection
http://twitter.com/statuses/update.xml
and it keeps returning a 401 error. I have verified that my username
password have not changed. Does the error have something to do with
the changes you made? How can I fix this?
Thanks!
Steve
SEJohnsen at gmail.com
$mypost=$data['post'];
$twitter_user = user;
$twitter_password = pwd;
$twitter_api_url = http://twitter.com/statuses/update.xml;;
$twitter_data = status=.$mypost;
$ch = curl_init($twitter_api_url);
curl_setopt($ch, CURLOPT_POST, 1);
curl_setopt($ch, CURLOPT_POSTFIELDS, $twitter_data);
curl_setopt($ch, CURLOPT_FOLLOWLOCATION, 1);
curl_setopt($ch, CURLOPT_HEADER, 0);
curl_setopt($ch, CURLOPT_RETURNTRANSFER, 1);
curl_setopt($ch, CURLOPT_USERPWD, {$twitter_user}:
{$twitter_password});
$twitter_data = curl_exec($ch);
$httpcode = curl_getinfo($ch, CURLINFO_HTTP_CODE);
curl_close($ch);
On Aug 27, 7:03 am, Raffi Krikorian ra...@twitter.com wrote:
hi all.
this is most certainly a mistake on our part - we'll be reverting this
change.
On Fri, Aug 27, 2010 at 4:45 AM, Cameron Kaiser spec...@floodgap.comwrote:
It looks like error responses have changed, at least for users/show.
I used to get:
{error:User has been suspended}
Now, I get:
{errors:[{code:63,message:User has been suspended}]}
I'm seeing that too. When did this change?
--
personal:
http://www.cameronkaiser.com/--
Cameron Kaiser * Floodgap Systems *www.floodgap.com*
ckai...@floodgap.com
-- They told me I was gullible ... and I believed them.
---
--
Twitter developer documentation and resources:http://dev.twitter.com/doc
API updates via Twitter:http://twitter.com/twitterapi
Issues/Enhancements Tracker:
http://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
http://groups.google.com/group/twitter-development-talk?hl=en
--
Raffi Krikorian
Twitter Platform Teamhttp://twitter.com/raffi
--
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
http://groups.google.com/group/twitter-development-talk?hl=en
Re: [twitter-dev] Re: Twitter logout - hate to open this can of worms again
On Fri, 3 Sep 2010 01:27:34 -0700 (PDT) Ken k...@cimas.ch wrote: I thought I had found a solution, albeit a horrendously ugly one: redirect them to http://twitter.com/logout, but even that doesn't work. If you are looking for reliable, don't log them in with OAuth - except once, the first time, when you store their token. Indeed. If you already have the token, why would you make them log in? If you get a new token every time they visit your 3rd party (consumer) site, you generate a lot of authorized tokens, ALL of which are valid for the rest of eternity, or until twitter decides that it should be possible to invalidate tokens. Bernd -- Bernd Stramm bernd.str...@gmail.com -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
Re: [twitter-dev] Twurl Multiple Account Usage Help
Hi William, twurl is designed for inspection, one off queries and debugging of API issues. It isn't really suitable as part of an application and rapid switching of the default account may, as you have suggested, not work well. Instead have a look at the single token examples on the developer resources site - they may be better suited to your needs. http://dev.twitter.com/pages/oauth_single_token Hope that helps, Matt On Thu, Sep 2, 2010 at 9:45 PM, William K. lordbl...@gmail.com wrote: I think i'm one of many who are looking for different ways of moving from Curl to Twurl with Twitter's closing the Basic Authentication protocol. I have different scripts that run on my server, based on certain criteria on the return of that script an automated tweet goes out to 1 of 2 accounts. With basic authentication it was easy to define the account using '-u' and '-p'. I'm trying to figure out how to do it with Twurl. I've authorized the two accounts in Twurl, but I can only get the default to tweet. I see I can change the default account, but depending on how fast the script is running it may want to tweet both accounts about the same time, and I don't want it to get caught switching defaults and the wrong data being sent to the incorrect account. I tried adding '-u' and the username at the start of the Twurl call, but it errors saying You need to authorize first, even though the account was authorized. Has anyone had success in this? Thank you. -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en -- Matt Harris Developer Advocate, Twitter http://twitter.com/themattharris -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
Re: [twitter-dev] t.co and fail whales
On Fri, 3 Sep 2010 09:12:32 -0700 (PDT) Dewald Pretorius dpr...@gmail.com wrote: Twitter folks, how are you going to ensure that t.co links are not affected by over-capacity situations on your infrastructure? If you're routing t.co links through your existing infrastructure, absolutely *everyone's* links are going to be broken when you start throwing fail whales, even when the link is clicked in third-party applications. Are you running t.co on its own separate and dedicated infrastructure? Ah, that brings up the next idea of how to enhance my application :) It wouldn't be all that hard to keep a cache/database of all the t.co links seen in a user's incoming timeline, and their resolution. The user would then have a private link resolution database, to protect against such service outages. Seems pretty straightforward, perhaps people should do that sort of thing. Bernd -- Bernd Stramm bernd.str...@gmail.com -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
Re: [twitter-dev] Re: Twitter logout - hate to open this can of worms again
You may not have noticed, but with Twitter, if you request a token while you already have one, you'll simply get back the one you already have. Tom On 9/3/10 6:47 PM, Bernd Stramm wrote: On Fri, 3 Sep 2010 01:27:34 -0700 (PDT) Ken k...@cimas.ch wrote: I thought I had found a solution, albeit a horrendously ugly one: redirect them to http://twitter.com/logout, but even that doesn't work. If you are looking for reliable, don't log them in with OAuth - except once, the first time, when you store their token. Indeed. If you already have the token, why would you make them log in? If you get a new token every time they visit your 3rd party (consumer) site, you generate a lot of authorized tokens, ALL of which are valid for the rest of eternity, or until twitter decides that it should be possible to invalidate tokens. Bernd -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
Re: [twitter-dev] Re: Twitter logout - hate to open this can of worms again
If i don't want to manage an authentication system, risk storing passwords, make users go through the paint of yet another registration flow then I might consider just using Sign in with Twitter every time someone sign into my site. Abraham - Abraham Williams | Hacker Advocate | http://abrah.am @abraham | http://projects.abrah.am | http://blog.abrah.am This email is: [ ] shareable [x] ask first [ ] private. On Fri, Sep 3, 2010 at 09:47, Bernd Stramm bernd.str...@gmail.com wrote: On Fri, 3 Sep 2010 01:27:34 -0700 (PDT) Ken k...@cimas.ch wrote: I thought I had found a solution, albeit a horrendously ugly one: redirect them to http://twitter.com/logout, but even that doesn't work. If you are looking for reliable, don't log them in with OAuth - except once, the first time, when you store their token. Indeed. If you already have the token, why would you make them log in? If you get a new token every time they visit your 3rd party (consumer) site, you generate a lot of authorized tokens, ALL of which are valid for the rest of eternity, or until twitter decides that it should be possible to invalidate tokens. Bernd -- Bernd Stramm bernd.str...@gmail.com -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
Re: [twitter-dev] Re: Change in error response objects
Hey Steve,
To expand on Tom's message, Basic Auth is no longer supported on the
Twitter API and you need to update your script to use OAuth. In
addition you want to make sure the URL you are calling is pointing to
http://api.twitter.com/1/statuses/update.xml - all API requests should
go through http://api.twitter.com now.
Information about transitioning from basic to OAuth is here:
http://dev.twitter.com/pages/basic_to_oauth
There are community libraries available which may be of help:
http://dev.twitter.com/pages/oauth_libraries
Hope that explains why your script stopped working and what you can do
to get it working again.
Matt
On Fri, Sep 3, 2010 at 9:42 AM, Tom van der Woerdt i...@tvdw.eu wrote:
http://dev.twitter.com/announcements
Tom
On 9/3/10 6:35 PM, MrMoxy wrote:
Raffi,
I have been using the API to tweet twice daily for months, but my
script suddenly stopped working yesterday morning. I am posting to
this page using a curl connection
http://twitter.com/statuses/update.xml
and it keeps returning a 401 error. I have verified that my username
password have not changed. Does the error have something to do with
the changes you made? How can I fix this?
Thanks!
Steve
SEJohnsen at gmail.com
$mypost=$data['post'];
$twitter_user = user;
$twitter_password = pwd;
$twitter_api_url = http://twitter.com/statuses/update.xml;;
$twitter_data = status=.$mypost;
$ch = curl_init($twitter_api_url);
curl_setopt($ch, CURLOPT_POST, 1);
curl_setopt($ch, CURLOPT_POSTFIELDS, $twitter_data);
curl_setopt($ch, CURLOPT_FOLLOWLOCATION, 1);
curl_setopt($ch, CURLOPT_HEADER, 0);
curl_setopt($ch, CURLOPT_RETURNTRANSFER, 1);
curl_setopt($ch, CURLOPT_USERPWD, {$twitter_user}:
{$twitter_password});
$twitter_data = curl_exec($ch);
$httpcode = curl_getinfo($ch, CURLINFO_HTTP_CODE);
curl_close($ch);
On Aug 27, 7:03 am, Raffi Krikorian ra...@twitter.com wrote:
hi all.
this is most certainly a mistake on our part - we'll be reverting this
change.
On Fri, Aug 27, 2010 at 4:45 AM, Cameron Kaiser spec...@floodgap.comwrote:
It looks like error responses have changed, at least for users/show.
I used to get:
{error:User has been suspended}
Now, I get:
{errors:[{code:63,message:User has been suspended}]}
I'm seeing that too. When did this change?
--
personal:
http://www.cameronkaiser.com/--
Cameron Kaiser * Floodgap Systems *www.floodgap.com*
ckai...@floodgap.com
-- They told me I was gullible ... and I believed them.
---
--
Twitter developer documentation and resources:http://dev.twitter.com/doc
API updates via Twitter:http://twitter.com/twitterapi
Issues/Enhancements Tracker:
http://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
http://groups.google.com/group/twitter-development-talk?hl=en
--
Raffi Krikorian
Twitter Platform Teamhttp://twitter.com/raffi
--
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
http://groups.google.com/group/twitter-development-talk?hl=en
--
Matt Harris
Developer Advocate, Twitter
http://twitter.com/themattharris
--
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
http://groups.google.com/group/twitter-development-talk?hl=en
Re: [twitter-dev] ERROR The requested URL could not be retrieved
Hi Rodrigo, When you say you are looping follow and unfollow can you give an example of your code and the URL you are using. The pagination is not linear for many of our methods and requires you to use the value of the next cursor we return instead of a numerical sequence 1,2,3. The error you are getting implies you are requesting a resource that doesn't exist. Best, Matt On Fri, Sep 3, 2010 at 7:14 AM, Rodrigo Berlinck rodrigode...@gmail.com wrote: While looping follow / unfollow, returning this error: ERROR The requested URL could not be retrieved whats that? thanks -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en -- Matt Harris Developer Advocate, Twitter http://twitter.com/themattharris -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
Re: [twitter-dev] Re: Twitter logout - hate to open this can of worms again
On Fri, 03 Sep 2010 18:55:30 +0200 Tom van der Woerdt i...@tvdw.eu wrote: You may not have noticed, but with Twitter, if you request a token while you already have one, you'll simply get back the one you already have. I don't know if that is correct. The ones I looked at were all different, but that was some weeks ago. Tom On 9/3/10 6:47 PM, Bernd Stramm wrote: On Fri, 3 Sep 2010 01:27:34 -0700 (PDT) Ken k...@cimas.ch wrote: I thought I had found a solution, albeit a horrendously ugly one: redirect them to http://twitter.com/logout, but even that doesn't work. If you are looking for reliable, don't log them in with OAuth - except once, the first time, when you store their token. Indeed. If you already have the token, why would you make them log in? If you get a new token every time they visit your 3rd party (consumer) site, you generate a lot of authorized tokens, ALL of which are valid for the rest of eternity, or until twitter decides that it should be possible to invalidate tokens. Bernd -- Bernd Stramm bernd.str...@gmail.com -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
[twitter-dev] Policy for xAuth grant to background process
Hi, I have read the xAuth page on apiwiki.twitter.com (http:// dev.twitter.com/pages/xauth) so I understand that xAuth is for desktop/ mobile application which the standard web OAuth flow or PIN-code out- of-band flow is not right for. I respect Twitter's policy but I am wondering if Twitter can help since we bumped into a very special case which can't be resolved without xAuth grant for background processor which is not desktop/mobile application. (I don't really feel comfortable to describe all our services in detail here in public forum but let me try. Please let me know if this is too vague and you can't really understand what I am saying. I can send an email with more detailed info.) We are developing a service which helps twitter users to communicate within their group. Members use their own Twitter account to sign in our service and they can create groups, which are related to another Twitter account. So all of our authorization is done using Twitter accounts. When members want to create a group they should sign in using their own Twitter account first and create a group and authorize our service to access group Twitter account for background processing on our server. Our background processor will monitor activities of group account and report them to the master, someone who created the group. Also masters should be able to change screen name, bio, and profile image of group Twitter account. All the processing for group twitter account will be done by background processor on our server. - Web client (web oAuth): members sign in using their own Twitter account to read timeline, send/receive dm and tweet. (So we need access token/key for member Twitter account) - mobile/desktop client (xAuth): members sign in using their own Twitter account to read timeline, send/receive dm and tweet. (So we need access token/key for member Twitter account) - Background processor (): works on the behalf of group Twitter account. (So we need access token/key for group Twitter account) My team was wondering how members authorize our background processor to access their other Twitter account which is a group account. After long discussion and test, we reached the conclusion that it can't be done without xAuth for background processor. 1) We need to get authorization for our background processor from members to access group Twitter account. So we need to register our background processor as Twitter application, which should use oAuth as default. 2) We already have xAuth granted by Twitter for our desktop/mobile application but this is for our clients only, not for our background processor. So members can't authorize our background processor to access group Twitter account in desktop/mobile application. That's a violation against Twitter policy. 3) With xAuth for our background processor, members can authorize it to access group Twitter account in desktop/mobile application. Without it? I'm lost. Can you please help? Thanks, -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
[twitter-dev] More than five weeks of waiting for wihitelisting?
Hi guys, Our company is running a service called twittercrawl in Germany and got an IP whitelisted for that a while ago. We now are planning to expand that service to other countrys and need another IP whitelisted for that. Unfortunately that takes a bit longer than expected and than previously experienced. We posted two request for now, using the accounts @ralphsonntag and @JeyPie. What could be the reasons for taking that long? Are you still trying to catch up since the soccer World Championship? Would you mind looking into that issue? Thanks for your help! -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
RE: [twitter-dev] Re: Change in error response objects
Tom,
Thanks! That helps a lot.
Now I just have to figure out how to use it!
Steve
-Original Message-
From: twitter-development-talk@googlegroups.com
[mailto:twitter-development-t...@googlegroups.com] On Behalf Of Tom van der
Woerdt
Sent: Friday, September 03, 2010 10:42 AM
To: twitter-development-talk@googlegroups.com
Subject: Re: [twitter-dev] Re: Change in error response objects
http://dev.twitter.com/announcements
Tom
On 9/3/10 6:35 PM, MrMoxy wrote:
Raffi,
I have been using the API to tweet twice daily for months, but my
script suddenly stopped working yesterday morning. I am posting to
this page using a curl connection
http://twitter.com/statuses/update.xml
and it keeps returning a 401 error. I have verified that my username
password have not changed. Does the error have something to do with
the changes you made? How can I fix this?
Thanks!
Steve
SEJohnsen at gmail.com
$mypost=$data['post'];
$twitter_user = user;
$twitter_password = pwd;
$twitter_api_url = http://twitter.com/statuses/update.xml;;
$twitter_data = status=.$mypost;
$ch = curl_init($twitter_api_url);
curl_setopt($ch, CURLOPT_POST, 1);
curl_setopt($ch, CURLOPT_POSTFIELDS, $twitter_data);
curl_setopt($ch, CURLOPT_FOLLOWLOCATION, 1);
curl_setopt($ch, CURLOPT_HEADER, 0);
curl_setopt($ch, CURLOPT_RETURNTRANSFER, 1);
curl_setopt($ch, CURLOPT_USERPWD, {$twitter_user}:
{$twitter_password});
$twitter_data = curl_exec($ch);
$httpcode = curl_getinfo($ch, CURLINFO_HTTP_CODE);
curl_close($ch);
On Aug 27, 7:03 am, Raffi Krikorian ra...@twitter.com wrote:
hi all.
this is most certainly a mistake on our part - we'll be reverting
this change.
On Fri, Aug 27, 2010 at 4:45 AM, Cameron Kaiser
spec...@floodgap.comwrote:
It looks like error responses have changed, at least for users/show.
I used to get:
{error:User has been suspended}
Now, I get:
{errors:[{code:63,message:User has been suspended}]}
I'm seeing that too. When did this change?
--
personal:
http://www.cameronkaiser.com/--
Cameron Kaiser * Floodgap Systems *www.floodgap.com*
ckai...@floodgap.com
-- They told me I was gullible ... and I believed them.
---
--
Twitter developer documentation and
resources:http://dev.twitter.com/doc
API updates via Twitter:http://twitter.com/twitterapi
Issues/Enhancements Tracker:
http://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
http://groups.google.com/group/twitter-development-talk?hl=en
--
Raffi Krikorian
Twitter Platform Teamhttp://twitter.com/raffi
--
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements
Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
http://groups.google.com/group/twitter-development-talk?hl=en
--
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
http://groups.google.com/group/twitter-development-talk?hl=en
[twitter-dev] Re: retweeted always returing as false in /1/statuses/user_timeline.json
Thanks for the info Matt, and I look forward to when they are enabled again. On Sep 3, 6:25 pm, Matt Harris thematthar...@twitter.com wrote: Hi Michael, Soon after launching those fields we identified some problems with them so had to disable them. That means the behavior you are seeing is expected right now. When the fields are enabled again we'll announce it to this mailing list. Best, Matt On Thu, Sep 2, 2010 at 9:04 PM, Michael Babker mbab...@flbab.com wrote: Hi there, I have a Twitter module I'm improving upon which pulls tweets from /1/statuses/user_timeline.json. An issue that I've noticed is that over the last couple of days, tweets I've retweeted using the retweet link on twitter.com have continued to display as retweeted: false in the JSON. Can someone tell me if this is normal behavior or if it's an issue with the API? Thanks! -- Twitter developer documentation and resources:http://dev.twitter.com/doc API updates via Twitter:http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en -- Matt Harris Developer Advocate, Twitterhttp://twitter.com/themattharris- Hide quoted text - - Show quoted text - -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
[twitter-dev] Re: Twitter logout - hate to open this can of worms again
What is the risk of storing a token? It can't be used outside your app. This is for sites that manage users. There's no need for a registration flow, at least one that is apparent to the user. For new users, send them to Twitter for a one-time Oauth roundtrip. Upon receipt of the token, create a user in your system, assign them a password and use it to log them in. Provide them this password, and/or let them change it. That's pretty pain-free account creation. If you need to associate an existing logged-in user with their Twitter account, send them to twitter for Oauth once. When they return they'll still be logged in and you'll have the credentials for future use. On Sep 3, 6:57 pm, Abraham Williams 4bra...@gmail.com wrote: If i don't want to manage an authentication system, risk storing passwords, make users go through the paint of yet another registration flow then I might consider just using Sign in with Twitter every time someone sign into my site. Abraham - Abraham Williams | Hacker Advocate |http://abrah.am @abraham |http://projects.abrah.am|http://blog.abrah.am This email is: [ ] shareable [x] ask first [ ] private. On Fri, Sep 3, 2010 at 09:47, Bernd Stramm bernd.str...@gmail.com wrote: On Fri, 3 Sep 2010 01:27:34 -0700 (PDT) Ken k...@cimas.ch wrote: I thought I had found a solution, albeit a horrendously ugly one: redirect them tohttp://twitter.com/logout, but even that doesn't work. If you are looking for reliable, don't log them in with OAuth - except once, the first time, when you store their token. Indeed. If you already have the token, why would you make them log in? If you get a new token every time they visit your 3rd party (consumer) site, you generate a lot of authorized tokens, ALL of which are valid for the rest of eternity, or until twitter decides that it should be possible to invalidate tokens. Bernd -- Bernd Stramm bernd.str...@gmail.com -- Twitter developer documentation and resources:http://dev.twitter.com/doc API updates via Twitter:http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
Re: [twitter-dev] Re: Twitter logout - hate to open this can of worms again
On Fri, 3 Sep 2010 11:29:22 -0700 (PDT) Ken k...@cimas.ch wrote: What is the risk of storing a token? It can't be used outside your app. The token being confined to use within an app is very insecure when the app runs on an end-user device. There soon will be a billion smart phones, and many of those will run twitter apps. Then suppose user Alice finds out user Bob's token (perhaps by borrowing or stealing a phone), and publishes it. User Bob now has no way to retire the token, short of disabling the app that runs on millions of phones. Or Bob can get a new twitter user name. That's not what is normally called security. OAuth as currently done with twitter only works when the app runs on a small number of secure servers. -- Bernd Stramm bernd.str...@gmail.com -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
[twitter-dev] Re: Twitter logout - hate to open this can of worms again
Bernd, totally. In answer to the OP, I was referring to the traditional server-based app. These may one day constitute a numeric minority of apps, but will probably remain an important use case for some time to come. Really, all bets are off when you talk about stealing of the device. When there is a risk of theft, a device (phone, car etc) needs to be disabled, turned off etc. Publishing Bob's token, credit card details or other compromising information by that criminal Alice would be bad for Bob, I'll grant you that. On Sep 3, 8:43 pm, Bernd Stramm bernd.str...@gmail.com wrote: On Fri, 3 Sep 2010 11:29:22 -0700 (PDT) Ken k...@cimas.ch wrote: What is the risk of storing a token? It can't be used outside your app. The token being confined to use within an app is very insecure when the app runs on an end-user device. There soon will be a billion smart phones, and many of those will run twitter apps. Then suppose user Alice finds out user Bob's token (perhaps by borrowing or stealing a phone), and publishes it. User Bob now has no way to retire the token, short of disabling the app that runs on millions of phones. Or Bob can get a new twitter user name. That's not what is normally called security. OAuth as currently done with twitter only works when the app runs on a small number of secure servers. -- Bernd Stramm bernd.str...@gmail.com -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
[twitter-dev] Home timeline without authentication
Is it feasible to construct home timeline of any user without using the API statuses/home_timeline, which requires user's authentication? We could iterate through user's friends graph, gather each friend's statuses and sort them by time. But it's an overkill for an user with more following. Any other options? -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
RE: [twitter-dev] Re: Change in error response objects
Matt,
Thank you very much!
Steve
-Original Message-
From: twitter-development-talk@googlegroups.com
[mailto:twitter-development-t...@googlegroups.com] On Behalf Of Matt Harris
Sent: Friday, September 03, 2010 11:04 AM
To: twitter-development-talk@googlegroups.com
Subject: Re: [twitter-dev] Re: Change in error response objects
Hey Steve,
To expand on Tom's message, Basic Auth is no longer supported on the Twitter
API and you need to update your script to use OAuth. In addition you want to
make sure the URL you are calling is pointing to
http://api.twitter.com/1/statuses/update.xml - all API requests should go
through http://api.twitter.com now.
Information about transitioning from basic to OAuth is here:
http://dev.twitter.com/pages/basic_to_oauth
There are community libraries available which may be of help:
http://dev.twitter.com/pages/oauth_libraries
Hope that explains why your script stopped working and what you can do to
get it working again.
Matt
On Fri, Sep 3, 2010 at 9:42 AM, Tom van der Woerdt i...@tvdw.eu wrote:
http://dev.twitter.com/announcements
Tom
On 9/3/10 6:35 PM, MrMoxy wrote:
Raffi,
I have been using the API to tweet twice daily for months, but my
script suddenly stopped working yesterday morning. I am posting to
this page using a curl connection
http://twitter.com/statuses/update.xml
and it keeps returning a 401 error. I have verified that my username
password have not changed. Does the error have something to do with
the changes you made? How can I fix this?
Thanks!
Steve
SEJohnsen at gmail.com
$mypost=$data['post'];
$twitter_user = user;
$twitter_password = pwd;
$twitter_api_url = http://twitter.com/statuses/update.xml;;
$twitter_data = status=.$mypost;
$ch = curl_init($twitter_api_url);
curl_setopt($ch, CURLOPT_POST, 1);
curl_setopt($ch, CURLOPT_POSTFIELDS, $twitter_data);
curl_setopt($ch, CURLOPT_FOLLOWLOCATION, 1);
curl_setopt($ch, CURLOPT_HEADER, 0);
curl_setopt($ch, CURLOPT_RETURNTRANSFER, 1);
curl_setopt($ch, CURLOPT_USERPWD, {$twitter_user}:
{$twitter_password});
$twitter_data = curl_exec($ch);
$httpcode = curl_getinfo($ch, CURLINFO_HTTP_CODE);
curl_close($ch);
On Aug 27, 7:03 am, Raffi Krikorian ra...@twitter.com wrote:
hi all.
this is most certainly a mistake on our part - we'll be reverting
this change.
On Fri, Aug 27, 2010 at 4:45 AM, Cameron Kaiser
spec...@floodgap.comwrote:
It looks like error responses have changed, at least for users/show.
I used to get:
{error:User has been suspended}
Now, I get:
{errors:[{code:63,message:User has been suspended}]}
I'm seeing that too. When did this change?
--
personal:
http://www.cameronkaiser.com/--
Cameron Kaiser * Floodgap Systems *www.floodgap.com*
ckai...@floodgap.com
-- They told me I was gullible ... and I believed them.
---
--
Twitter developer documentation and
resources:http://dev.twitter.com/doc
API updates via Twitter:http://twitter.com/twitterapi
Issues/Enhancements Tracker:
http://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
http://groups.google.com/group/twitter-development-talk?hl=en
--
Raffi Krikorian
Twitter Platform Teamhttp://twitter.com/raffi
--
Twitter developer documentation and resources:
http://dev.twitter.com/doc API updates via Twitter:
http://twitter.com/twitterapi Issues/Enhancements Tracker:
http://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
http://groups.google.com/group/twitter-development-talk?hl=en
--
Matt Harris
Developer Advocate, Twitter
http://twitter.com/themattharris
--
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements
Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
http://groups.google.com/group/twitter-development-talk?hl=en
--
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
http://groups.google.com/group/twitter-development-talk?hl=en
[twitter-dev] Re: ERROR The requested URL could not be retrieved
Hi Matt, I use Code Igniter (PHP Framework). Looping: Select the followers of the user and return array follow matrix matrix unfollow insert into db (mysql) but he makes filters, and has a limit own, for example it takes only 200 followers and then make 200 unfollowers. On Sep 3, 2:15 pm, Matt Harris thematthar...@twitter.com wrote: Hi Rodrigo, When you say you are looping follow and unfollow can you give an example of your code and the URL you are using. The pagination is not linear for many of our methods and requires you to use the value of the next cursor we return instead of a numerical sequence 1,2,3. The error you are getting implies you are requesting a resource that doesn't exist. Best, Matt On Fri, Sep 3, 2010 at 7:14 AM, Rodrigo Berlinck rodrigode...@gmail.com wrote: While looping follow / unfollow, returning this error: ERROR The requested URL could not be retrieved whats that? thanks -- Twitter developer documentation and resources:http://dev.twitter.com/doc API updates via Twitter:http://twitter.com/twitterapi Issues/Enhancements Tracker:http://code.google.com/p/twitter-api/issues/list Change your membership to this group:http://groups.google.com/group/twitter-development-talk?hl=en -- Matt Harris Developer Advocate, Twitterhttp://twitter.com/themattharris -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
[twitter-dev] Re: garbage in json api response?
For what it's worth, all of the garbage data seems to be /between/ the status updates. We (Flipboard) have deployed a temporary hack to split the raw JSON at status boundaries and verify the integrity of each one before trying to parse the JSON. -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
[twitter-dev] Re: Simple status update
I posted a question similar except using perl.. All the subroutine does is update a twitter account using curl. All this OAuth stuff seems like it is shoveling a small driveway with a bulldozer! Updates are done on about 100 domains, so does that mean we have to register 100 apps and every time we put the updating on a new site, register that as well... Is there any Perl sample code or do you all just consider Perl old fart software? G. On Sep 3, 12:10 pm, Matt Harris thematthar...@twitter.com wrote: Hey Tomáš, There are a number of libraries on our developer resources site which handle OAuth in PHP: http://dev.twitter.com/pages/oauth_libraries#php Remember OAuth uses a consumer key and secret to identify an application, and a user token and secret for the user. This means you will need to have an application registered onhttp://dev.twitter.com/apps/newbefore you can Tweet using OAuth. When you have created your application there will be a button on the right of the screen labelled My Access Token. In there you will find the user token and secret that will identify you using OAuth. Some examples of using the single token can be found here: http://dev.twitter.com/pages/oauth_single_token Hope that helps, Matt On Thu, Sep 2, 2010 at 5:26 PM, Tomáš Pospíšil pospis...@gmail.com wrote: Hi, I'm trying to update my twitter status every time, when new post appears on my website. I found several classes (in PHP), but none of them works, because they don't implement OAuth. Classes which implement OAuth let anybody update their status through my page. But that is not the functionality I need. Maybe I'm blind, but there wasn't any field or variable, where i could set my username, password and new status message and let the class do the rest of the work... Please, if you know about some class, that can do what I need, or at least some tutorial let me know, it would be very helpful. Thank you! -- Twitter developer documentation and resources:http://dev.twitter.com/doc API updates via Twitter:http://twitter.com/twitterapi Issues/Enhancements Tracker:http://code.google.com/p/twitter-api/issues/list Change your membership to this group:http://groups.google.com/group/twitter-development-talk?hl=en -- Matt Harris Developer Advocate, Twitterhttp://twitter.com/themattharris -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
[twitter-dev] Re: Get all the statuses for an specific hashtag
John, I tested that and it worked fine for new tweets. ¿It's there any way I can get the old ones to? On 28 ago, 11:54, John Kalucki j...@twitter.com wrote: You want filter.json with the track parameter. -John Kaluckihttp://twitter.com/jkalucki Twitter, Inc. On Fri, Aug 27, 2010 at 7:51 PM, gabitoju gabit...@gmail.com wrote: Hi everyone. I've been reading the API documentation and the streaming API docs but I haven't been able to find a way to get all the statuses for an specific hashtag. I've tried with the search API using the page and the rpp parameters but couldn't get what I want. Is there a way to do this? Thanks! -- Twitter developer documentation and resources:http://dev.twitter.com/doc API updates via Twitter:http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
[twitter-dev] t.co link wrapping and the new 140 characters...
I just want this to be confirmed by @raffi If I understand correctly http://groups.google.com/group/twitter-api-announce/browse_thread/thread/14d5474c13ed84aa This means that I can securely send a 120 (or less) character message + a link, no matter how long the link is, it will be translated into 20 characters, and so the total being 140 character I'm fine. Right? My Rails app will send hey this is a message with always a http://link.com/path/to/resource; and all I need to check is that hey this is a message with always a is 120 chars, right? Thanks for confirming this, that would be amazingly cool because it would mean I don't need (and nobody would need) to call some t.co API to shrink a URL. Then I would only need to count on the updated clients (and twitter.com) to display my http://link.com; as a text and http://t.co/jhdafkjh; as a link! Wouldn't be a big deal if some (most) clients display the t.co as a text :) Cheers. -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
[twitter-dev] mentions.json / include_rts
Does anyone know when native retweets will be working with mentions when the include_rts query param is set to true? It seems to be an acknowledged bug, but I can't find too much information about it. The call: http://api.twitter.com/1/statuses/mentions.json?include_rts=true -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
Re: [twitter-dev] Re: Simple status update
I posted a question similar except using perl.. All the subroutine does is update a twitter account using curl. All this OAuth stuff seems like it is shoveling a small driveway with a bulldozer! Updates are done on about 100 domains, so does that mean we have to register 100 apps and every time we put the updating on a new site, register that as well... Is there any Perl sample code or do you all just consider Perl old fart software? You're welcome to look at TTYtter: http://www.floodgap.com/software/ttytter/ This is pure-Perl and uses its own built-in HMAC and SHA-1 algorithms; it has no dependencies other than cURL. FTR, I am generally considered an old fart (ask Ed Finkler). -- personal: http://www.cameronkaiser.com/ -- Cameron Kaiser * Floodgap Systems * www.floodgap.com * ckai...@floodgap.com -- UBAX vs lbh ybir EBG-13 -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
Re: [twitter-dev] Home timeline without authentication
It isn't possible to do this without having access to the users account. One of the main reasons being that protected users statuses are not available to accounts who do not follow them. If the user you want to construct the home timeline for follows a protected user you won't be able to get their statuses without authentication. In addition various social graph features such as retweets and mentions would need to be found, merged, de-duplicated and ordered. The simplest method is to be granted permission by the user to call their home_timeline. Best, Matt On Fri, Sep 3, 2010 at 1:03 PM, Bernd Stramm bernd.str...@gmail.com wrote: On Fri, 3 Sep 2010 12:12:19 -0700 (PDT) Karthik fermis...@gmail.com wrote: Is it feasible to construct home timeline of any user without using the API statuses/home_timeline, which requires user's authentication? We could iterate through user's friends graph, gather each friend's statuses and sort them by time. But it's an overkill for an user with more following. Any other options? - Create a fake user that has follows the same accounts, Or, - Pay Twitter for the data, I'm sure they will be happy to accommodate you ;) -- Bernd Stramm bernd.str...@gmail.com -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en -- Matt Harris Developer Advocate, Twitter http://twitter.com/themattharris -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
Re: [twitter-dev] Re: ERROR The requested URL could not be retrieved
I'm still not sure what you are doing or the URLs you are calling to the API. We also don't provide information about unfollows so i'm confused about that aspect of your code. On Fri, Sep 3, 2010 at 10:47 AM, Rodrigo Berlinck rodrigode...@gmail.com wrote: Hi Matt, I use Code Igniter (PHP Framework). Looping: Select the followers of the user and return array follow matrix matrix unfollow insert into db (mysql) but he makes filters, and has a limit own, for example it takes only 200 followers and then make 200 unfollowers. On Sep 3, 2:15 pm, Matt Harris thematthar...@twitter.com wrote: Hi Rodrigo, When you say you are looping follow and unfollow can you give an example of your code and the URL you are using. The pagination is not linear for many of our methods and requires you to use the value of the next cursor we return instead of a numerical sequence 1,2,3. The error you are getting implies you are requesting a resource that doesn't exist. Best, Matt On Fri, Sep 3, 2010 at 7:14 AM, Rodrigo Berlinck rodrigode...@gmail.com wrote: While looping follow / unfollow, returning this error: ERROR The requested URL could not be retrieved whats that? thanks -- Twitter developer documentation and resources:http://dev.twitter.com/doc API updates via Twitter:http://twitter.com/twitterapi Issues/Enhancements Tracker:http://code.google.com/p/twitter-api/issues/list Change your membership to this group:http://groups.google.com/group/twitter-development-talk?hl=en -- Matt Harris Developer Advocate, Twitterhttp://twitter.com/themattharris -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en -- Matt Harris Developer Advocate, Twitter http://twitter.com/themattharris -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
Re: [twitter-dev] Re: Get all the statuses for an specific hashtag
The Streaming API will provide information from the time you connect forward. To access historical data is a little harder. The Search API will allow you to access the last 5 days of Tweets. If you want any more than that you will need to use a 3rd party service that has been tracking Tweets for longer. Hope that answers your question, Matt On Fri, Sep 3, 2010 at 12:56 PM, gabitoju gabit...@gmail.com wrote: John, I tested that and it worked fine for new tweets. ¿It's there any way I can get the old ones to? On 28 ago, 11:54, John Kalucki j...@twitter.com wrote: You want filter.json with the track parameter. -John Kaluckihttp://twitter.com/jkalucki Twitter, Inc. On Fri, Aug 27, 2010 at 7:51 PM, gabitoju gabit...@gmail.com wrote: Hi everyone. I've been reading the API documentation and the streaming API docs but I haven't been able to find a way to get all the statuses for an specific hashtag. I've tried with the search API using the page and the rpp parameters but couldn't get what I want. Is there a way to do this? Thanks! -- Twitter developer documentation and resources:http://dev.twitter.com/doc API updates via Twitter:http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en -- Matt Harris Developer Advocate, Twitter http://twitter.com/themattharris -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
Re: [twitter-dev] Re: Simple status update
I suppose I should write a Twitter client in gforth just to be an older fart than the rest of you, eh? ;-) -- M. Edward (Ed) Borasky http://borasky-research.net http://twitter.com/znmeb A mathematician is a device for turning coffee into theorems. - Paul Erdos Quoting Cameron Kaiser spec...@floodgap.com: I posted a question similar except using perl.. All the subroutine does is update a twitter account using curl. All this OAuth stuff seems like it is shoveling a small driveway with a bulldozer! Updates are done on about 100 domains, so does that mean we have to register 100 apps and every time we put the updating on a new site, register that as well... Is there any Perl sample code or do you all just consider Perl old fart software? You're welcome to look at TTYtter: http://www.floodgap.com/software/ttytter/ This is pure-Perl and uses its own built-in HMAC and SHA-1 algorithms; it has no dependencies other than cURL. FTR, I am generally considered an old fart (ask Ed Finkler). -- personal: http://www.cameronkaiser.com/ -- Cameron Kaiser * Floodgap Systems * www.floodgap.com * ckai...@floodgap.com -- UBAX vs lbh ybir EBG-13 -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
[twitter-dev] All Linux applications for Twitter broken...
You find not one Twitter application for Linux that is working. Means Twitter is just useless if you use Linux. Not to talk from the thousands of Websites which send status messages to Twitter (e.g. a new posting/thread is entered). Looks like OAuth really works out for Twitter. Thx a lot guys, but it's time to look for something else than Twitter. Having enough people using the service and just doing that what you guys have done is absolutely not amusing. -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
Re: [twitter-dev] All Linux applications for Twitter broken...
Hmm, that would be down to the developers of said applications not moving them to OAuth, nothing to do with Twitter. They've had plenty of time and warnings to do so. Don't take it out on Twitter when its down to the developers of the applications to maintain them. On 3 Sep 2010, at 22:43, Herb wrote: You find not one Twitter application for Linux that is working. Means Twitter is just useless if you use Linux. Not to talk from the thousands of Websites which send status messages to Twitter (e.g. a new posting/thread is entered). Looks like OAuth really works out for Twitter. Thx a lot guys, but it's time to look for something else than Twitter. Having enough people using the service and just doing that what you guys have done is absolutely not amusing. smime.p7s Description: S/MIME cryptographic signature
Re: [twitter-dev] All Linux applications for Twitter broken...
On Fri, 3 Sep 2010 14:43:58 -0700 (PDT) Herb taa.t...@gmail.com wrote: You find not one Twitter application for Linux that is working. Mine works. Means Twitter is just useless if you use Linux. Not to talk from the thousands of Websites which send status messages to Twitter (e.g. a new posting/thread is entered). Looks like OAuth really works out for Twitter. Thx a lot guys, but it's time to look for something else than Twitter. Having enough people using the service and just doing that what you guys have done is absolutely not amusing. -- Bernd Stramm bernd.str...@gmail.com -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
[twitter-dev] Re: All Linux applications for Twitter broken...
Has all to do with Twitter. Changing to OAuth was really not needed and the problems for this change really obvious in first place, but since Twitter has that much users they probably feel that they can do whatever they like. Didn't find any way to use successfully OAuth for some Linux application in two weeks, Terminal updates for sure never will work again and and and. the list is endless. This raise the question why there is a Twitter API at all available if the usage is not user friendly at all. Well, point is if this situation continuous for some time it may provides a way for something else that is better usable than Twitter. On Sep 4, 5:01 am, Scott Wilcox sc...@dor.ky wrote: Hmm, that would be down to the developers of said applications not moving them to OAuth, nothing to do with Twitter. They've had plenty of time and warnings to do so. Don't take it out on Twitter when its down to the developers of the applications to maintain them. On 3 Sep 2010, at 22:43, Herb wrote: You find not one Twitter application for Linux that is working. Means Twitter is just useless if you use Linux. Not to talk from the thousands of Websites which send status messages to Twitter (e.g. a new posting/thread is entered). Looks like OAuth really works out for Twitter. Thx a lot guys, but it's time to look for something else than Twitter. Having enough people using the service and just doing that what you guys have done is absolutely not amusing. smime.p7s 5KViewDownload -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
Re: [twitter-dev] Re: All Linux applications for Twitter broken...
On Fri, 3 Sep 2010 15:20:15 -0700 (PDT) Herb taa.t...@gmail.com wrote: Has all to do with Twitter. Changing to OAuth was really not needed and the problems for this change really obvious in first place, but since Twitter has that much users they probably feel that they can do whatever they like. Didn't find any way to use successfully OAuth for some Linux application in two weeks, As I said, my application works, on Fedora, Ubuntu Lucid, OpenSUSE and MeeGo. Look at http://chronicon.sourceforge.net. It is also in my launchpad ppa, and in my yum/zypper repos at build.opensuse.org. There are other twitter clients that also use qoauth. As far as I know, those are working as well. Terminal updates for sure never will work again and and and. the list is endless. This raise the question why there is a Twitter API at all available if the usage is not user friendly at all. Well, point is if this situation continuous for some time it may provides a way for something else that is better usable than Twitter. There already is StatusNet. You can run your own service, or subscribe to identi.ca. Of course the value of twitter is the large number of users. Most people use twitter to publish their content, so the number of readers is what they go after. On Sep 4, 5:01 am, Scott Wilcox sc...@dor.ky wrote: Hmm, that would be down to the developers of said applications not moving them to OAuth, nothing to do with Twitter. They've had plenty of time and warnings to do so. Don't take it out on Twitter when its down to the developers of the applications to maintain them. On 3 Sep 2010, at 22:43, Herb wrote: You find not one Twitter application for Linux that is working. Means Twitter is just useless if you use Linux. Not to talk from the thousands of Websites which send status messages to Twitter (e.g. a new posting/thread is entered). Looks like OAuth really works out for Twitter. Thx a lot guys, but it's time to look for something else than Twitter. Having enough people using the service and just doing that what you guys have done is absolutely not amusing. smime.p7s 5KViewDownload -- Bernd Stramm bernd.str...@gmail.com -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
Re: [twitter-dev] Re: All Linux applications for Twitter broken...
Has all to do with Twitter. Changing to OAuth was really not needed Yes it was. Do you even know what OAuth is? and the problems for this change really obvious in first place, but since Twitter has that much users they probably feel that they can do whatever they like. Are you saying that a company can't change its own applications? That would be rather... strange, don't you think? They simply have to live with the consequences like any other company. I'm sure they know what they were doing when they decided to kill basic auth. Didn't find any way to use successfully OAuth for some Linux application in two weeks, You aren't very good in searching then :-) I've seen a lot of Linux Twitter clients that use OAuth. Terminal updates for sure never will work again and and and. the list is endless. I completely disagree. There are plenty of CLI OAuth clients if you really want one. This raise the question why there is a Twitter API at all available if the usage is not user friendly at all. OAuth is mainly a developer thing. Well, point is if this situation continuous for some time it may provides a way for something else that is better usable than Twitter. Name a popular social site that doesn't use OAuth. :-) Tom On Sep 4, 5:01 am, Scott Wilcox sc...@dor.ky wrote: Hmm, that would be down to the developers of said applications not moving them to OAuth, nothing to do with Twitter. They've had plenty of time and warnings to do so. Don't take it out on Twitter when its down to the developers of the applications to maintain them. On 3 Sep 2010, at 22:43, Herb wrote: You find not one Twitter application for Linux that is working. Means Twitter is just useless if you use Linux. Not to talk from the thousands of Websites which send status messages to Twitter (e.g. a new posting/thread is entered). Looks like OAuth really works out for Twitter. Thx a lot guys, but it's time to look for something else than Twitter. Having enough people using the service and just doing that what you guys have done is absolutely not amusing. smime.p7s 5KViewDownload -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
RE: [twitter-dev] Re: Change in error response objects
Thanks to all for the pointers. I got everything rewritten and working now thanks to the examples from Joe Chung. http://nullinfo.wordpress.com/oauth-twitter/ Steve -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
[twitter-dev] counting tweets sent from client app
Is there any way to count such tweets? maybe during paricular period of time? -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
[twitter-dev] Re: update_profile_image is returning 200OK but not updating Profile Image
Hi,
I was wondering if this issue was corrected. I'm having a problem
updating the background profile image. The API is returning 200 and
the user's profile data, but the image isn't updated.
On Jul 19, 6:54 am, Taylor Singletary taylorsinglet...@twitter.com
wrote:
Thank you for the details, Bob. We're looking into it.
Taylor
On Mon, Jul 19, 2010 at 6:19 AM, Bob movingforwa...@gmail.com wrote:
We are again seeing behaviour where update_profile_image is returning
a 200OK but the image is not updated on Twitter. This happened last
week and was fixed under Issue 1745:
http://code.google.com/p/twitter-api/issues/detail?id=1745
But it has just reappeared. Behaviour is very slightly different in
that the previous profile image remains in place rather than becoming
a broken image.
Request and response shown below.
Thanks,
Bob
Founder
Twibbon.com
--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=81r7llydmekc186w,o
auth_timestamp=1279545055,oauth_signature_method=HMAC-
SHA1,oauth_signature=9MkFOvvVxEmQZcyJUvSEOSF0na4%3D,oauth_version=1.0
Content-Type: multipart/form-data; boundary=ab0fd378-4c1f-445f-
aa8e-45488c90256d
--ab0fd378-4c1f-445f-aa8e-45488c90256d
Content-Disposition: file; name=image; filename=5e55681f-878e-46bd-
a584-57fcfaf4b52b.png
Content-Type: image/png
[FILE DATA][System.Text.Latin1Encoding]
--ab0fd378-4c1f-445f-aa8e-45488c90256d--
--RESPONSE:http://api.twitter.com/1/account/update_profile_image.json
HTTP/1.1 200 OK
Date: Mon, 19 Jul 2010 13:10:55 GMT
Server: hi
Status: 200 OK
X-Transaction: 1279545055-84509-57740
ETag: b089d0f3bb2c84ad1283361318917271
Last-Modified: Mon, 19 Jul 2010 13:10:55 GMT
X-Runtime: 0.10970
Content-Type: application/json; charset=utf-8
Content-Length: 1340
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.1279545055076066; path=/; expires=Mon, 26-
Jul-10 13:10:55 GMT; domain=.twitter.com,guest_id=127954505542692657;
path=/; expires=Wed, 18 Aug 2010 13:10:55 GMT,lang=en;
path=/,_twitter_sess=BAh7CDoPY3JlYXRlZF9hdGwrCNQY1OopAToHaWQiJTMyOWI4OGU1Mj
FmNTg3%250AZTllNzNhOTQxYjVlOGVkNjQ3IgpmbGFzaElDOidBY3Rpb25Db250cm9sbGVy
%250AOjpGbGFzaDo6Rmxhc2hIYXNoewAGOgpAdXNlZHsA--
da8b247094aedfa91e96f6b9fc02dbc701228e41; domain=.twitter.com; path=/
Vary: Accept-Encoding
Connection: close
{statuses_count:
327,profile_sidebar_border_color:87bc44,description:,location:,
profile_use_background_image:true,followers_count:
31,status:
{contributors:null,coordinates:null,truncated:false,source:a
href=\http://twibbon.com\; rel=\nofollow\Twibbon/
a,created_at:Mon Jul 19 13:04:30 +
2010,geo:null,in_reply_to_screen_name:null,favorited:false,in_reply
_to_status_id:null,place:null,id:
18914185988,in_reply_to_user_id:null,text:Support
#natsuniji_blue, add a #twibbon to your avatar now! -
http://twb.ly/9rgeFs
},contributors_enabled:false,friends_count:30,geo_enabled:false,pro
file_background_color:9ae4e8,lang:en,favourites_count:0,created_a
t:Thu
Jul 16 00:18:19 +
2009,verified:false,profile_text_color:00,follow_request_sent:
false,notifications:false,time_zone:null,following:false,profile_lin
k_color:ff,protected:false,profile_background_image_url:http://
a1.twimg.com/profile_background_images/123041250/
df10e21c-5216-4fcb-80f5-e2962b764d6f.jpg,profile_image_url:http://
a2.twimg.com/profile_images/1079636046/30f17041-0f8c-4031-b0fd-
d1bdcf043ad1_normal.png,name:Bob
Thomson,profile_sidebar_fill_color:e0ff92,url:null,id:
57184902,profile_background_tile:false,utc_offset:null,screen_name:j
pfette}
--
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
http://groups.google.com/group/twitter-development-talk?hl=en
[twitter-dev] Re: Uploading a Profile Image help
This call was working fine for me using basic auth. I've been converting my code to oAuth on my test machine. I now receive a 200 reply and the user's profile data, but the image is not updated. On Aug 9, 8:33 am, MeltingIce meltingice8...@gmail.com wrote: I too am waiting for the profileimageAPI call to be fixed. I have checked the request and even dove into HTTP_Request2's internal code just to verify that the request is correct. The only error I get back is 500 Internal Server Error. No other hints or suggestions are present in the response header. The images I am using are small and well within the limits. Any update on when this may be working again? Thanks, Ryan On Aug 9, 11:07 am, Taylor Singletary taylorsinglet...@twitter.com wrote: Also a reminder: the Twitter API is at thehttp://api.twitter.comsubdomain. Twitter API has version numbers in the URL as well. The original poster in this thread is usinghttp://twitter.com/account/update_profile_image.xmlwhenthey should be usinghttp://api.twitter.com/1/account/update_profile_image.xml And I'll echo what Tom has said: you should switch to using OAuth very soon or you'll find your script doesn't work at all in about 2 weeks. Taylor On Sun, Aug 8, 2010 at 10:28 PM, Raghu Prasad prasad.ragh...@gmail.comwrote: On Sun, Aug 8, 2010 at 5:58 AM, marketingmaniac execut...@gmail.com wrote: i use to have this app that suddenly doesn't work anymore,, it use to work perfectly and now ,, hmm,, any help would be appreciated,, Though I don't know a bit about VB, I can safely say that profileimagefunctionality of Twitter has been broken for many weeks. Updating profileimagehas not been working via API. If you check the past threads, you'd find that one of the Twitter developer is assigned the task of streamlining theimageupload functionality. I am also waiting for that to happen. Raghu here is the code that update my users profile written in vb 2008/10 that worked flawlessly 'THE BUTTON I MADE TO INITIATE THE SUB CALLED UPLOADPROFILEIMAGE Private Sub Button37_Click_1(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles Button37.Click -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
[twitter-dev] coldfusion / twitter status update/
I used to use the basic authentication process with a cfhttp tag but since that doesn't work anymore, has anyone developed a way to post a status update without having to redirect the user to the twitter site using a username and password? -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
