[twitter-dev] Re: Changes for April 9, 2009
ok, I found out my bug, I added all parameters to the request url, but the OAuth spec(http://oauth.net/core/1.0/#request_urls) said 'The request URL query MUST NOT contain any OAuth Protocol Parameters', so I remove oauth parameters, and it works now. But, I am curious why my app work before? On Apr 10, 11:52 am, Abraham Williams 4bra...@gmail.com wrote: Try a GET instead of a POST. On Thu, Apr 9, 2009 at 19:41, Chen Jie chenyue...@gmail.com wrote: I can't get RequestToken now, but my app is work yesterday :( On Apr 10, 8:35 am, Matt Sanford m...@twitter.com wrote: Hi all, Hot on the heels of yesterday's mega-deploy we've put out two small bug fixes for today, 2009-04-09: * Fixed (OAuth): Accented characters in statuses were causing signature error for OAuth clients. This has been corrected. » See:http://code.google.com/p/twitter-api/issues/detail?id=433 * Fixed (REST): Attempting to direct message yourself failed and returned a direct message from cache. You can now direct message yourself again. » See: http://groups.google.com/group/twitter-development-talk/browse_frm/th... Thanks; — Matt Sanford / @mzsanford -- Abraham Williams |http://the.hackerconundrum.com Hacker |http://abrah.am|http://twitter.com/abraham Web608 | Community Evangelist |http://web608.org This email is: [ ] blogable [x] ask first [ ] private. Sent from Madison, WI, United States
[twitter-dev] Recommended oAuth application setup for development/staging/production environments with different sub-domain names
If I have dev/staging/prod environments defined as follows, do I need to create three separate oAuth apps on Twitter with the corresponding Application Website and Callback URLs defined in each one? 1. http://dev.example.com (pointing to my laptop external IP address) 2. http://staging.example.com (on my webhost server) 3. example.com (on my webhost server) Thanks, Doug
[twitter-dev] Re: Recommended oAuth application setup for development/staging/production environments with different sub-domain names
In your authorize reuqest URL you can manually set an oauth_callback parameter which will override the URL set in your application setup page. So, you can use one app for all of your different test/dev/staging/live (sub)domains. -Chad On Fri, Apr 10, 2009 at 1:57 AM, Doug dougire...@gmail.com wrote: If I have dev/staging/prod environments defined as follows, do I need to create three separate oAuth apps on Twitter with the corresponding Application Website and Callback URLs defined in each one? 1. http://dev.example.com (pointing to my laptop external IP address) 2. http://staging.example.com (on my webhost server) 3. example.com (on my webhost server) Thanks, Doug
[twitter-dev] 401 Unauthorized on OAuth calls?
Hi everyone, since about half an hour ago I seem to be getting 401 Unauthorized responses to my OAuth-ed API calls. Is that a known problem? Regards, Dominik
[twitter-dev] Re: Settings-Connections
Friday morning report: still seeing 500 error on the connections tab in some accounts. On Apr 8, 11:40 am, Doug Williams d...@twitter.com wrote: There were a lot of system issues that could have caused the robots. The site should be much happier as the week goes on. Thanks for your patience. Doug Williams Twitter API Supporthttp://twitter.com/dougw On Wed, Apr 8, 2009 at 4:28 AM, Mobasoft mobat...@gmail.com wrote: Checked again this morning - after seeing robots on the home page and now link to logout (UI flaw) I cleared browser cookies and tried again. Now I see the connections tab and the one authenticated application for that account. On Apr 7, 5:11 pm, Mobasoft mobat...@gmail.com wrote: I have another account, where I could not see the Connections tab, but was able to navigate to the url. I've also just granted OAuth access to that account and I still do not see a Connections tab, and navigating to the connections url still says, No applications have been approved to use your account. I'll assume that it is a Twitter caching problem (which seems to have been a bigger overall problem lately). If it shows up anytime soon, I'll add another reply here. Michael On Apr 7, 4:56 pm, Mobasoft mobat...@gmail.com wrote: Robots. Something is technically wrong. Thanks for noticing—we're going to fix it up and have things back to normal soon. On Apr 7, 4:53 pm, Doug Williams d...@twitter.com wrote: Michael, All of the API development team read this forum so it's the best place for issues like this. As Chad replied, the connections tab is working for me as expected. Can you go into more detail about what you are seeing that seems off? Doug Williams Twitter API Supporthttp://twitter.com/dougw On Tue, Apr 7, 2009 at 2:43 PM, Chad Etzel jazzyc...@gmail.com wrote: Working for me, and displaying all of the authorized apps I've used... -Chad On Tue, Apr 7, 2009 at 5:41 PM, Mobasoft mobat...@gmail.com wrote: I understand that a lot of this OAuth development has been and out of some flux lately, but is thathttps:// twitter.com/account/connections link working for anyone? If there is a more prominent place to ask Twitter dev team directly, please inform me. Thanks, Michael
[twitter-dev] Re: 401 Unauthorized on OAuth calls?
Same here. On Apr 10, 10:19 pm, Dominik Schwind domi...@gmail.com wrote: Hi everyone, since about half an hour ago I seem to be getting 401 Unauthorized responses to my OAuth-ed API calls. Is that a known problem? Regards, Dominik
[twitter-dev] Entity encoding (reprise)
Hi, I notice that the Twitter website doesn't entity encode ampersands after retrieving statuses so it basically allows users to enter quot; into the text box and instead of seeing quot; they get instead. This leads to problems for us API users. With my command line client, using JSON, it would still show up as quot; which would confuse users who are used to the website's conversion of entities. So, in order to make my application present the statuses as they would be shown on the website I have to make it pretend to be a HTML renderer. This is pretty difficult as different browsers do things differently, e.g. some render quot as instead of requiring the semicolon. What I would like to see is the Twitter website start to entity encode ampersands at presentation time, so that what the users enter in the text box is what they see after they hit the 'update' button. After all, the vast majority of users probably don't know what entity encoding is. I know this request is beyond the scope of this list but if the current website behaviour is going to be the expected API data presentation behaviour, I think it should at least be mentioned in the API docs. (P.S. I know about the encoding of and because it's mentioned in the API docs so they're no problem, although it really shouldn't need to be done in my opinion. There are too many assumptions that the strings are going to be used in a web context.) Cheers, -- Andrew
[twitter-dev] sort parameter for friends timeline method?
It would be nice to have a sort parameter for the friends timeline method. i was a little baffled why when I requested hte tweets with a certain since id and a count of 20 it wasn't retrieving hte previous page, then I realized it was counting from the beginning and not the other way. any chance we could get a way to have it return a list of tweets in descending or ascending order?
[twitter-dev] Re: Recommended oAuth application setup for development/staging/production environments with different sub-domain names
If you use one OAuth application for all three be warned that currently if a single user account is being used on all three it will only work on the environment that you last authorized it on. So if you are using your personal account on production and authorized it on development. Production will have old access tokens that will not work until you reauthorize on production. This is a known issue that Twitter is working on. On Fri, Apr 10, 2009 at 02:43, Chad Etzel jazzyc...@gmail.com wrote: In your authorize reuqest URL you can manually set an oauth_callback parameter which will override the URL set in your application setup page. So, you can use one app for all of your different test/dev/staging/live (sub)domains. -Chad On Fri, Apr 10, 2009 at 1:57 AM, Doug dougire...@gmail.com wrote: If I have dev/staging/prod environments defined as follows, do I need to create three separate oAuth apps on Twitter with the corresponding Application Website and Callback URLs defined in each one? 1. http://dev.example.com (pointing to my laptop external IP address) 2. http://staging.example.com (on my webhost server) 3. example.com (on my webhost server) Thanks, Doug -- Abraham Williams | http://the.hackerconundrum.com Hacker | http://abrah.am | http://twitter.com/abraham Web608 | Community Evangelist | http://web608.org This email is: [ ] blogable [x] ask first [ ] private. Sent from Madison, WI, United States
[twitter-dev] Re: sort parameter for friends timeline method?
Not sure if this is best practices, but when using a since_Id param I just throw the max count value at the request (usually 200) and get all the data. Then you can sort it however you want client side. Probably not exactly what you were asking, but it works. Chad On Apr 10, 2009, at 11:32 AM, Chris Westbrook westbch...@gmail.com wrote: It would be nice to have a sort parameter for the friends timeline method. i was a little baffled why when I requested hte tweets with a certain since id and a count of 20 it wasn't retrieving hte previous page, then I realized it was counting from the beginning and not the other way. any chance we could get a way to have it return a list of tweets in descending or ascending order?
[twitter-dev] Re: 401 Unauthorized on OAuth calls?
Guys, Details are essential to help track down claims like these. What are you doing, and more importantly, how are you doing it? Doug Williams Twitter API Support http://twitter.com/dougw On Fri, Apr 10, 2009 at 6:48 AM, Bluespark spo...@gmail.com wrote: Same here. On Apr 10, 10:19 pm, Dominik Schwind domi...@gmail.com wrote: Hi everyone, since about half an hour ago I seem to be getting 401 Unauthorized responses to my OAuth-ed API calls. Is that a known problem? Regards, Dominik
[twitter-dev] Re: http://twitter.com/direct_messages/new.json failed
Gary, direct_messages/new requires a HTTP POST request. I can see from the URL you pasted in the post that you have a query string. If you are sending a POST request you would have no query string. Doug Williams Twitter API Support http://twitter.com/dougw On Thu, Apr 9, 2009 at 10:21 PM, Alex Payne a...@twitter.com wrote: 400 is the response code we return for rate limiting. Are you sure you're making the request using an HTTP POST? What was the body of the response? On Thu, Apr 9, 2009 at 18:22, Gary Zhao garyz...@gmail.com wrote: http://twitter.com/direct_messages/new.json?user=qinqi7text=test I got The remote server returned an error: (400) Bad Request. Anything wrong with this API invocation? Thanks -- Gary http://twitter.com/garyzhao -- Alex Payne - API Lead, Twitter, Inc. http://twitter.com/al3x
[twitter-dev] Re: If your OAuth 'verify_credentials.xml' API just broke....
Thanks for sharing the code. The change notice was here [1] for posterity.
1.
http://groups.google.com/group/twitter-development-talk/browse_frm/thread/5822fbfd5ea857c6/1e6e14b9c96f74ca#1e6e14b9c96f74ca
Doug Williams
Twitter API Support
http://twitter.com/dougw
On Thu, Apr 9, 2009 at 6:52 PM, kosso kos...@gmail.com wrote:
... they appear to have changed the call from a POST to a GET.
I didn't see an update/change about this.
So, in PHP use:
$to = new TwitterOAuth($consumer_key, $consumer_secret,
$twitterOAuthToken, $twitterOAuthSecret);
$content = $to-OAuthRequest('https://twitter.com/account/
verify_credentials.xmlhttps://twitter.com/account/%0Averify_credentials.xml',
array(), 'GET');
In the original example PHP scripts, the call was a POST, which used
to work. Until I saw the API returning 'this method requires a GET.'
this morning.
hth
[twitter-dev] Re: Failed to validate oauth signature or token on status update post?
sorry, I found out my bug, I constructed the wrong request URL. But I can't use POST also, :( On Apr 10, 11:57 am, Chen Jie chenyue...@gmail.com wrote: I got the error on every requests by OAuth, just works fine yesterday.. On Apr 10, 10:27 am, HSL hslee...@gmail.com wrote: Anyone else has the problem that posting a status update through OAuth gives the error: failed to validate oauth signatre or token since a few hours?
[twitter-dev] Re: Failed to validate oauth signature or token on status update post?
I'm getting the same message when trying to update. The signature and token seem fine to me. On Apr 10, 4:27 am, HSL hslee...@gmail.com wrote: Anyone else has the problem that posting a status update through OAuth gives the error: failed to validate oauth signatre or token since a few hours?
[twitter-dev] Re: Trying to send a direct message to myself, getting someone else's direct message back in retunr
Service! Thanks guys @pauly On Apr 10, 1:32 am, Matt Sanford m...@twitter.com wrote: Hi all, The fix for this was just deployed. I'm updating the change log now and will send the standard announcement email. Thanks; — Matt On Apr 9, 2009, at 03:46 PM, Doug Williams wrote: This is a bug and Matt is currently working on the fix. Doug Williams Twitter API Support http://twitter.com/dougw On Thu, Apr 9, 2009 at 3:04 PM, Pauly paulypo...@gmail.com wrote: Just seen someone else twittering @twitterapi with a similar issue... I try to post: http://twitter.com/direct_messages/new.xml?user=foo567text=Ticketmas... and get back the following xml (removed a url). I am following this user, if I try to direct message an account I'm not following I get the expected error message. No direct message is sent in either case. Anyone any idea? I'm posting but with a query string like this (using curl in php), instead of actually posting the params, this is the only way that works for me to update my status, so could be I'm doing something odd there... ?xml version=1.0 encoding=UTF-8? direct_message id/id sender_id19482771/sender_id textCome join me on Utterz! We can have multimedia discussions from our mobile phone o... Join at http://.../text recipient_id13881572/recipient_id created_at/created_at sender_screen_nameMasAdhie/sender_screen_name recipient_screen_namePat_Lorna/recipient_screen_name sender id19482771/id nameMas Adhie/name screen_nameMasAdhie/screen_name locationSemarang/location descriptionsilahkan kontak sya di YM AdiSucipto atau SKYPE ID MasAdhie/description profile_image_urlhttp://s3.amazonaws.com/twitter_production/ profile_images/73051328/Johnny-Depp-and-Wajahku_normal.jpg/ profile_image_url urlhttp://www.100juta.co.cc/url protectedfalse/protected followers_count269/followers_count /sender recipient id13881572/id namePat and Lorna Shanks/name screen_namePat_Lorna/screen_name locationEdmonton, AB. Canada/location descriptionWe teach entrepreneurs how to create, market and monetize presentations for more prospects and profits./description profile_image_urlhttp://s3.amazonaws.com/twitter_production/ profile_images/65659291/sp_logo_300x300_normal.jpg/profile_image_url urlhttp://PatAndLorna.com/url protectedfalse/protected followers_count14596/followers_count /recipient /direct_message
[twitter-dev] Re: Failed to validate oauth signature or token on status update post?
I have the same problem since this morning, pretty strange, looked over my code but I really don't see anything wrong. On Apr 10, 4:27 am, HSL hslee...@gmail.com wrote: Anyone else has the problem that posting a status update through OAuth gives the error: failed to validate oauth signatre or token since a few hours?
[twitter-dev] Re: 401 Unauthorized on OAuth calls?
I;ve created an issue,.. can you all comment there too? http://shortr.me/lz On Apr 10, 12:19 pm, Dominik Schwind domi...@gmail.com wrote: Hi everyone, since about half an hour ago I seem to be getting 401 Unauthorized responses to my OAuth-ed API calls. Is that a known problem? Regards, Dominik
[twitter-dev] Re: Requesting Twitter API
Doug Williams Twitter API Support http://twitter.com/dougw On Thu, Apr 9, 2009 at 10:50 PM, Omer rosen omero...@gmail.com wrote: For some reason I can't find the link to the requesting page of Twitter API. Can someone reply me with the link? Thanks!
[twitter-dev] Re: 401 Unauthorized on OAuth calls?
Before opening an issue [1] it would have been nice to discuss. What are you trying to do? What steps have you taken to debug? Why do you think this is on our end and not a bug in your code? We can't help without knowing what's going on. 1. http://code.google.com/p/twitter-api/issues/detail?id=447 Doug Williams Twitter API Support http://twitter.com/dougw On Fri, Apr 10, 2009 at 8:56 AM, HSL hslee...@gmail.com wrote: I;ve created an issue,.. can you all comment there too? http://shortr.me/lz On Apr 10, 12:19 pm, Dominik Schwind domi...@gmail.com wrote: Hi everyone, since about half an hour ago I seem to be getting 401 Unauthorized responses to my OAuth-ed API calls. Is that a known problem? Regards, Dominik
[twitter-dev] Re: search by link
Squeak Smalltalk Twitter Client at http://code.google.com/p/twitter-client/
[twitter-dev] Re: Changes for April 9, 2009
I appreciate giving back sending DM to myself - you have now helped to have this very important (non disturbing) test method - VERY THANKS On Thu, Apr 9, 2009 at 9:35 PM, Matt Sanford m...@twitter.com wrote: Hi all, Hot on the heels of yesterday's mega-deploy we've put out two small bug fixes for today, 2009-04-09: * Fixed (OAuth): Accented characters in statuses were causing signature error for OAuth clients. This has been corrected. » See: http://code.google.com/p/twitter-api/issues/detail?id=433 * Fixed (REST): Attempting to direct message yourself failed and returned a direct message from cache. You can now direct message yourself again. » See: http://groups.google.com/group/twitter-development-talk/browse_frm/thread/a2f31e0a95807581 Thanks; — Matt Sanford / @mzsanford -- Carlos Crosetti
[twitter-dev] PHP Twitter by Tijs Verkoyen
Changes April 8th break PHP Twitter's verify credentials function.
To fix this find the function (yes, it's spelled wrong)
verifyCrendentials
then update the code from
$response = $this-doCall('account/verify_credentials.xml', array(),
true);
to
$response = $this-doCall('account/verify_credentials.xml', array(),
true, false);
This will switch from a POST request to a GET request, which is
required.
[twitter-dev] Re: Failed to validate oauth signature or token on status update post?
I got a workaround for POST, I removed Authorization info in Header, then the POST request passed. On Apr 10, 8:50 pm, max maxnet...@gmail.com wrote: I have the same problem since this morning, pretty strange, looked over my code but I really don't see anything wrong. On Apr 10, 4:27 am, HSL hslee...@gmail.com wrote: Anyone else has the problem that posting a status update through OAuth gives the error: failed to validate oauth signatre or token since a few hours?
[twitter-dev] Re: Settings-Connections
Hi there, I have seen reports from a few developers about this consistent robot page. I have been looking into this morning and I believe I have a fix. The problem is a bug with how active tokens are handled when an application has been deleted. I'm working on getting the fix reviewed now. I'll let you know once the fix has been deployed. Thanks; — Matt Sanford / @mzsanford On Apr 10, 2009, at 05:19 AM, Mobasoft wrote: Friday morning report: still seeing 500 error on the connections tab in some accounts. On Apr 8, 11:40 am, Doug Williams d...@twitter.com wrote: There were a lot of system issues that could have caused the robots. The site should be much happier as the week goes on. Thanks for your patience. Doug Williams Twitter API Supporthttp://twitter.com/dougw On Wed, Apr 8, 2009 at 4:28 AM, Mobasoft mobat...@gmail.com wrote: Checked again this morning - after seeing robots on the home page and now link to logout (UI flaw) I cleared browser cookies and tried again. Now I see the connections tab and the one authenticated application for that account. On Apr 7, 5:11 pm, Mobasoft mobat...@gmail.com wrote: I have another account, where I could not see the Connections tab, but was able to navigate to the url. I've also just granted OAuth access to that account and I still do not see a Connections tab, and navigating to the connections url still says, No applications have been approved to use your account. I'll assume that it is a Twitter caching problem (which seems to have been a bigger overall problem lately). If it shows up anytime soon, I'll add another reply here. Michael On Apr 7, 4:56 pm, Mobasoft mobat...@gmail.com wrote: Robots. Something is technically wrong. Thanks for noticing—we're going to fix it up and have things back to normal soon. On Apr 7, 4:53 pm, Doug Williams d...@twitter.com wrote: Michael, All of the API development team read this forum so it's the best place for issues like this. As Chad replied, the connections tab is working for me as expected. Can you go into more detail about what you are seeing that seems off? Doug Williams Twitter API Supporthttp://twitter.com/dougw On Tue, Apr 7, 2009 at 2:43 PM, Chad Etzel jazzyc...@gmail.com wrote: Working for me, and displaying all of the authorized apps I've used... -Chad On Tue, Apr 7, 2009 at 5:41 PM, Mobasoft mobat...@gmail.com wrote: I understand that a lot of this OAuth development has been and out of some flux lately, but is thathttps:// twitter.com/account/connections link working for anyone? If there is a more prominent place to ask Twitter dev team directly, please inform me. Thanks, Michael
[twitter-dev] Re: search by link
Search only by source is not supported. Doug Williams Twitter API Support http://twitter.com/dougw On Fri, Apr 10, 2009 at 10:38 AM, joop23 joo...@gmail.com wrote: I was hoping to find a way to search for source through the search api without having to pass in some text. Just source through api. On Apr 9, 11:48 am, Chad Etzel jazzyc...@gmail.com wrote: It should be noted that you can't just search for a source alone, you must pass in some sort of query with it. So you can't really get all tweets from a particular source... One interesting way to use the source data handed back by the search API is to gauge market share for certain keywords/phrases. I created a tool here to do this: http://tweetgrid.com/sources it's interesting to search for different people (e.g. from:user) to see what clients they are frequently using... -Chad On Thu, Apr 9, 2009 at 2:37 PM, Doug Williams d...@twitter.com wrote: The search twitter source:tweetdeck [1] will return any tweet with 'twitter' from the source with parameter 'tweetdeck'. Add your appropriate format to the URL and you're good to go! 1.http://search.twitter.com/search?q=twitter+source%3Atweetdeck Doug Williams Twitter API Support http://twitter.com/dougw On Thu, Apr 9, 2009 at 11:22 AM, joop23 joo...@gmail.com wrote: Hello, Is there a way to search by link on the status message? For instance, I'd like to pull all statuses submitted by TweetDeck application. thank you
[twitter-dev] OAuth Deny action should trigger a Revoke
I was just doing some implementation testing. Here's the scenario: Assumption: Visitor has previously authorized the application. 1) Visitor was in my app 2) Visitor clicks on link to authorize app with Twitter 3) Visitor lands on https://twitter.com/oauth/authorize 4) Visitor enters userid and p/w 5) Visitor clicks Deny 6) Visitor is now stuck over on Twitter The application authorization was not revoked, as it still appears in Twitters Authorized App list for visitor. My assumption would be that visitor would expect the application access to have been revoked when they clicked Deny instead of Allow. Since that is not the case, visitor must now log in to Twitter, navigate to Settings-Connections and then click again to Revoke access.
[twitter-dev] Re: A note on our API change policy
On Fri, Apr 10, 2009 at 1:04 PM, Doug Williams d...@twitter.com wrote: Lastly, lets work together. Tell me what you developers need that we are not currently providing. How can we better manage this communication? Which method of notifications work best for you? Aside from transparency with API changes, what else do you want to know? Keep us posted on what is going to happen not just what already happened with a deploy. Also, sometimes a change in the Twitter UX also means important change to the API. A good example of this recently was the change of the definition of a reply to a mention. This impacted every app that depended on the existing definition of a reply. Having some advance notice to developers that this change was coming would have prevented some problems. Thanks for working on the transparency and communication. Appreciate it. -damon -- http://twitter.com/damon
[twitter-dev] 400 bad request from verify_credentials
Hi, I am getting 400 Bad Request error from Twitter for the API call 'account/verify_credentials'. As per http://apiwiki.twitter.com this occurs when the rate limit of 100 requests per 60 minute is exceeded. But I have verified thrice that the requests have not exceeded this limit at any time. Also I am not receiving any notification in return to the API call, as mentioned in the documentation. What might be the possible cause? This is crucial for our application's performance. Kindly help me out. Thanks
[twitter-dev] Re: 401 Unauthorized on OAuth calls?
Hi,
I'm seeing it on two applications EagleTweet and EagleTweetDev - I
am using the Zend_OAuth library for PHP and I'm updating location
fields for roughly 100 users with their FireEagle location once in a
while. You can see it at http://eagletweet.com/ and I can give you the
API Keys in private mail if you want.
The thing has been running for a about two weeks now and has been
working fine until this friday morning (Central European Time) - since
then the library returns an error with the http code 401
Unauthorized - without any code changes from me, so I figured it
can't really be a bug on my side.
To debug I had my code give me the Zend_Http_Response object:
object(Zend_Http_Response)#49 (5) { [version:protected]= string(3)
1.1 [code:protected]= int(401) [message:protected]= string(12)
Unauthorized [headers:protected]= array(11) { [Date]=
string(29) Fri, 10 Apr 2009 18:44:37 GMT [Server]= string(2) hi
[Status]= string(16) 401 Unauthorized [Cache-control]=
string(21) no-cache, max-age=300 [Content-type]= string(24)
text/html; charset=utf-8 [Set-cookie]= string(182)
_twitter_sess=BAh7BiIKZmxhc2hJQzonQWN0aW9uQ29udHJvbGxlcjo6Rmxhc2g6OkZsYXNo%250ASGFzaHsABjoKQHVzZWR7AA%253D%253D--1164b91ac812d853b877e93ddb612b7471bebc74;
domain=.twitter.com; path=/ [Expires]= string(29) Fri, 10 Apr
2009 18:49:37 GMT [Vary]= string(15) Accept-Encoding
[Content-encoding]= string(4) gzip [Content-length]= string(2)
60 [Connection]= string(5) close } [body:protected]=
string(60) �sK��IMQ(�W(K��LI,IU�O,-�P(�L�K,)-��٩y0y(�+ }
Maybe that helps?
Thanks,
Dominik
On Fri, Apr 10, 2009 at 6:21 PM, Doug Williams d...@twitter.com wrote:
Guys,
Details are essential to help track down claims like these. What are you
doing, and more importantly, how are you doing it?
Doug Williams
Twitter API Support
http://twitter.com/dougw
On Fri, Apr 10, 2009 at 6:48 AM, Bluespark spo...@gmail.com wrote:
Same here.
On Apr 10, 10:19 pm, Dominik Schwind domi...@gmail.com wrote:
Hi everyone,
since about half an hour ago I seem to be getting 401 Unauthorized
responses to my OAuth-ed API calls.
Is that a known problem?
Regards,
Dominik
--
Dominik Schwind
www.lostfocus.de
Other ways to contact me on
www.dominikschwind.com
[twitter-dev] Re: 400 bad request from verify_credentials
Are you making a GET request? Doug Williams Twitter API Support http://twitter.com/dougw On Fri, Apr 10, 2009 at 11:34 AM, nattu natraj1...@gmail.com wrote: Hi, I am getting 400 Bad Request error from Twitter for the API call 'account/verify_credentials'. As per http://apiwiki.twitter.com this occurs when the rate limit of 100 requests per 60 minute is exceeded. But I have verified thrice that the requests have not exceeded this limit at any time. Also I am not receiving any notification in return to the API call, as mentioned in the documentation. What might be the possible cause? This is crucial for our application's performance. Kindly help me out. Thanks
[twitter-dev] Does the Search API have an hourly limit like the main API?
We are debating whether or not we need to authenticate users when making a call against the search API. Thanks
[twitter-dev] Re: 401 Unauthorized on OAuth calls?
Oh, On Fri, Apr 10, 2009 at 8:48 PM, Dominik Schwind domi...@gmail.com wrote: [body:protected]= string(60) � sK��IMQ(�W(K��LI,IU�O,-�P(�L�K,)- ��٩y0y(�+ } That gibberish is just a gzip version of: string(43) Failed to validate oauth signature or token Thx, Dominik
[twitter-dev] Re: Does the Search API have an hourly limit like the main API?
So if we want to make over 100 search API requests in an hour, we need to get whitelisted? On Apr 10, 12:54 pm, Doug Williams d...@twitter.com wrote: There is no authentication for the search API. Rate limiting is based on IP address alone. Doug Williams Twitter API Supporthttp://twitter.com/dougw On Fri, Apr 10, 2009 at 11:49 AM, Brandon Geiger bran...@swarmforce.comwrote: We are debating whether or not we need to authenticate users when making a call against the search API. Thanks
[twitter-dev] my reader is FUBARd after latest API change (since param removed)
Here's your chance to convert me to another application. I've been using Pytwerp to read twitter. Thanks to the latest API change where since was removed, PPyTwerp is now merrily returning the same set of tweets over and over and over again. Busy developer says It could be patched to save a status ID instead of a date string. I don't have time to do this myself at the moment PyTwerp is written in Python (not my language) and I don't have the glimmerins of a clue as to how to change it to use status id instead of date string, or what that means in terms of the Twitter calls or... gack. Is there anyone on this list who can help? Where by help I mean either help me ffix PyTwerp or offer me a recommendation for a replacement? I'll go either way. My requirements: * command-line program (Python, Perl, I'll even take C) * must run on a Unix system, from cron, called (approx) every 10 minutes) 24/7 * results pushed through a small script that does basic filtering * final results stored in text files sample output: __biz__: I've got my gmail inbox down to 15 super important starred emails and now I want to watch TV but I am too tired --- also, my Kindle arrived! -- [[Twitter:biz/statuses/142109][view]] Here's what I''m doing: http://cfcl.com/vlb/Learn/twitter/twitter_reader.shtml Give me a working replacement and I'll update my blog entry.
[twitter-dev] Re: Freelance Twitter API Dev directory?
Hi, please add me too. Twitter username: sscout URL: http://sscout.livejournal.com | http://sscout.wordpress.com Email: ssc...@gmail.com S D A Y :P I develop on HTML (3+) (by hand, or WYSIWYG editors), some CSS, C, Pascal, Assembly Language (I know, I was raised by dinosaurs). and I've been trying to get into PHP, Java and Wiki|*. Currently working in some stuff on http://lyricwiki.org/User:Sscout So if anyone wants to waste time teaching me let me know ^.^ (Meaning, I'll work cheap online for training). I also proofread novels and documents (So I can help with documentation).
[twitter-dev] Source isn't working for me anymore
Since the 7th or the 8th (April) it seems like Twitter is ignoring my source (twitzap). I have confirmed that the source string is being submitted correctly when a status update is posted but all the tweets show as from web on the Twitter website. Any ideas? -rfurlan
[twitter-dev] Re: Source isn't working for me anymore
Your flux capacitor must be on the flimflam. On Fri, Apr 10, 2009 at 4:54 PM, rfurlan rfur...@gmail.com wrote: Since the 7th or the 8th (April) it seems like Twitter is ignoring my source (twitzap). I have confirmed that the source string is being submitted correctly when a status update is posted but all the tweets show as from web on the Twitter website. Any ideas? -rfurlan
[twitter-dev] Em-dash, accented characters in updates: Failed to validate...
Hi, I've been using the em-dash when posting status updates, and apparently this now causes the Twitter API to return Failed to validate... errors. This just started happening within the last 24-48 hours. I am using OAuth (specifically, the PHP library written by Abraham Williams), and my site is http://dora.fm. I noticed in the API changelog that accented characters -- and I'm assuming, characters like the em-dash -- have supposedly been fixed (Fixed (OAuth): Accented characters in statuses were causing signature error for OAuth clients. This has been corrected.) But I'm finding that this is broken NOW and was working fine before. Suggestions? Thanks.
[twitter-dev] Re: Source isn't working for me anymore
It worked for me. How are you submitting your source parameter? Doug Williams Twitter API Support http://twitter.com/dougw On Fri, Apr 10, 2009 at 3:33 PM, Andrew Badera and...@badera.us wrote: Your flux capacitor must be on the flimflam. On Fri, Apr 10, 2009 at 4:54 PM, rfurlan rfur...@gmail.com wrote: Since the 7th or the 8th (April) it seems like Twitter is ignoring my source (twitzap). I have confirmed that the source string is being submitted correctly when a status update is posted but all the tweets show as from web on the Twitter website. Any ideas? -rfurlan
[twitter-dev] Re: Does the Search API have an hourly limit like the main API?
No, search is not limited by the same rate limiter as the REST API. There is still a limit but it is well north of 100 request per hour. You'll receive 503 HTTP responses if the limit is hit. Doug Williams Twitter API Support http://twitter.com/dougw On Fri, Apr 10, 2009 at 11:59 AM, Brandon Geiger bran...@swarmforce.comwrote: So if we want to make over 100 search API requests in an hour, we need to get whitelisted? On Apr 10, 12:54 pm, Doug Williams d...@twitter.com wrote: There is no authentication for the search API. Rate limiting is based on IP address alone. Doug Williams Twitter API Supporthttp://twitter.com/dougw On Fri, Apr 10, 2009 at 11:49 AM, Brandon Geiger bran...@swarmforce.com wrote: We are debating whether or not we need to authenticate users when making a call against the search API. Thanks
[twitter-dev] Re: Settings-Connections
Hi there, A fix for this was deployed a few moments ago. Thanks; — Matt Sanford On Apr 10, 2009, at 05:19 AM, Mobasoft wrote: Friday morning report: still seeing 500 error on the connections tab in some accounts. On Apr 8, 11:40 am, Doug Williams d...@twitter.com wrote: There were a lot of system issues that could have caused the robots. The site should be much happier as the week goes on. Thanks for your patience. Doug Williams Twitter API Supporthttp://twitter.com/dougw On Wed, Apr 8, 2009 at 4:28 AM, Mobasoft mobat...@gmail.com wrote: Checked again this morning - after seeing robots on the home page and now link to logout (UI flaw) I cleared browser cookies and tried again. Now I see the connections tab and the one authenticated application for that account. On Apr 7, 5:11 pm, Mobasoft mobat...@gmail.com wrote: I have another account, where I could not see the Connections tab, but was able to navigate to the url. I've also just granted OAuth access to that account and I still do not see a Connections tab, and navigating to the connections url still says, No applications have been approved to use your account. I'll assume that it is a Twitter caching problem (which seems to have been a bigger overall problem lately). If it shows up anytime soon, I'll add another reply here. Michael On Apr 7, 4:56 pm, Mobasoft mobat...@gmail.com wrote: Robots. Something is technically wrong. Thanks for noticing—we're going to fix it up and have things back to normal soon. On Apr 7, 4:53 pm, Doug Williams d...@twitter.com wrote: Michael, All of the API development team read this forum so it's the best place for issues like this. As Chad replied, the connections tab is working for me as expected. Can you go into more detail about what you are seeing that seems off? Doug Williams Twitter API Supporthttp://twitter.com/dougw On Tue, Apr 7, 2009 at 2:43 PM, Chad Etzel jazzyc...@gmail.com wrote: Working for me, and displaying all of the authorized apps I've used... -Chad On Tue, Apr 7, 2009 at 5:41 PM, Mobasoft mobat...@gmail.com wrote: I understand that a lot of this OAuth development has been and out of some flux lately, but is thathttps:// twitter.com/account/connections link working for anyone? If there is a more prominent place to ask Twitter dev team directly, please inform me. Thanks, Michael
[twitter-dev] Re: Em-dash, accented characters in updates: Failed to validate...
Hi Isaac, The change we implemented seems to have fixed people using a newer version of the Ruby oauth gem but it sounds like it may have broken some other libraries. My guess is that there is an encoding normalization difference between the PHP library and the newest Ruby version right NOW. The spec does have some normalization information [1] [2] and it seems like the Ruby code is doing that work via [3]: def escape(value) URI::escape(value.to_s, OAuth::RESERVED_CHARACTERS) end And that constant is defined as: # reserved character regexp, per section 5.1 RESERVED_CHARACTERS = /[^\w\d\-\.\_\~]/ I know Abraham reads this Google Group so perhaps he and I can get together on Monday and compare some pre-signature strings between Ruby and PHP to figure out what's going on. If you see this Abraham drop me an email otherwise you can expect one from me on Monday to sort this out. Thanks; — Matt [1] - http://oauth.net/core/1.0/#anchor14 [2] - http://oauth.net/core/1.0/#encoding_parameters [3] - http://github.com/mojodna/oauth/blob/dbd946790a882d91fb111ba64331de003c135872/lib/oauth/helper.rb#L9 [4] - http://github.com/mojodna/oauth/blob/dbd946790a882d91fb111ba64331de003c135872/lib/oauth/oauth.rb On Apr 10, 2009, at 03:47 PM, Isaac wrote: Hi, I've been using the em-dash when posting status updates, and apparently this now causes the Twitter API to return Failed to validate... errors. This just started happening within the last 24-48 hours. I am using OAuth (specifically, the PHP library written by Abraham Williams), and my site is http://dora.fm. I noticed in the API changelog that accented characters -- and I'm assuming, characters like the em-dash -- have supposedly been fixed (Fixed (OAuth): Accented characters in statuses were causing signature error for OAuth clients. This has been corrected.) But I'm finding that this is broken NOW and was working fine before. Suggestions? Thanks.
[twitter-dev] Re: http://twitter.com/direct_messages/new.json failed
Exactly. It's my overlook. Thanks Alex and Doug. On Fri, Apr 10, 2009 at 9:25 AM, Doug Williams d...@twitter.com wrote: Gary, direct_messages/new requires a HTTP POST request. I can see from the URL you pasted in the post that you have a query string. If you are sending a POST request you would have no query string. Doug Williams Twitter API Support http://twitter.com/dougw On Thu, Apr 9, 2009 at 10:21 PM, Alex Payne a...@twitter.com wrote: 400 is the response code we return for rate limiting. Are you sure you're making the request using an HTTP POST? What was the body of the response? On Thu, Apr 9, 2009 at 18:22, Gary Zhao garyz...@gmail.com wrote: http://twitter.com/direct_messages/new.json?user=qinqi7text=test I got The remote server returned an error: (400) Bad Request. Anything wrong with this API invocation? Thanks -- Gary http://twitter.com/garyzhao -- Alex Payne - API Lead, Twitter, Inc. http://twitter.com/al3x -- Gary http://twitter.com/garyzhao
[twitter-dev] Re: http://twitter.com/direct_messages/new.json failed
On Fri, Apr 10, 2009 at 12:25, Doug Williams d...@twitter.com wrote: Gary, direct_messages/new requires a HTTP POST request. I can see from the URL you pasted in the post that you have a query string. If you are sending a POST request you would have no query string. Although, it is possible to have a POST with a query string, and doing so will generate the 401 error, even if it's a POST with a valid body. Took me a while to realize this is what was happening. Zac
[twitter-dev] Re: 400 bad request from verify_credentials
No, I am making a POST request. Now I see in the API documentation that it is a GET to be used. But POST used to work till last Wednesday. Was it a change in the API? Thanks.. On Apr 10, 11:48 pm, Doug Williams d...@twitter.com wrote: Are you making a GET request? Doug Williams Twitter API Supporthttp://twitter.com/dougw On Fri, Apr 10, 2009 at 11:34 AM, nattu natraj1...@gmail.com wrote: Hi, I am getting 400 Bad Request error from Twitter for the API call 'account/verify_credentials'. As perhttp://apiwiki.twitter.comthis occurs when the rate limit of 100 requests per 60 minute is exceeded. But I have verified thrice that the requests have not exceeded this limit at any time. Also I am not receiving any notification in return to the API call, as mentioned in the documentation. What might be the possible cause? This is crucial for our application's performance. Kindly help me out. Thanks
[twitter-dev] Re: 400 bad request from verify_credentials
Yes. On Fri, Apr 10, 2009 at 22:26, nattu natraj1...@gmail.com wrote: No, I am making a POST request. Now I see in the API documentation that it is a GET to be used. But POST used to work till last Wednesday. Was it a change in the API? Thanks.. On Apr 10, 11:48 pm, Doug Williams d...@twitter.com wrote: Are you making a GET request? Doug Williams Twitter API Supporthttp://twitter.com/dougw On Fri, Apr 10, 2009 at 11:34 AM, nattu natraj1...@gmail.com wrote: Hi, I am getting 400 Bad Request error from Twitter for the API call 'account/verify_credentials'. As perhttp://apiwiki.twitter.comthis occurs when the rate limit of 100 requests per 60 minute is exceeded. But I have verified thrice that the requests have not exceeded this limit at any time. Also I am not receiving any notification in return to the API call, as mentioned in the documentation. What might be the possible cause? This is crucial for our application's performance. Kindly help me out. Thanks -- Abraham Williams | http://the.hackerconundrum.com Hacker | http://abrah.am | http://twitter.com/abraham Web608 | Community Evangelist | http://web608.org This email is: [ ] blogable [x] ask first [ ] private. Sent from Madison, Wisconsin, United States
