[twitter-dev] Re: Urls shorting connection successes
Well , I tried the URL shorting ! and twitter do this automatically if the status characters are more than 160 ! just 1 problem now ! how can I make sure that twitter API is ok ? is there and OAUTH method to do so ??
[twitter-dev] statuses/update: Expect: 100-Continue header rejected
I've been playing with oacurl https://code.google.com/apis/buzz/v1/oacurl.html and tried to use it to send a tweet. oacurl sends Expect: 100-Continue but Twitter rejects this with we only allow the 100-continue expectation. This seems to violate http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.20 Comparison of expectation values is case-insensitive for unquoted tokens (including the 100-continue token). Is this fixable, or avoidable in the meantime? (I know about twurl, but oacurl seems generic - can I use twurl to make oauth calls to MySpace?) Output from oacurl (duplicate content snipped) is below: /c/download: echo status=Testing+oacurl | java -cp oacurl-1.0.0.jar com.google.oacurl.Fetch -X POST -v http://api.twitter.com/1/statuses/update.json POST /1/statuses/update.json HTTP/1.1 Content-Type: application/atom+xml Authorization: OAuth oauth_token=34507306-x, oauth_consumer_key=x, oauth_signature_method=HMAC-SHA1, oauth_timestamp=1274334015, oauth_nonce=508570714177400, oauth_version=1.0, oauth_signature=x Transfer-Encoding: chunked Host: api.twitter.com Connection: Keep-Alive User-Agent: Apache-HttpClient/4.0 (java 1.5) Expect: 100-Continue HTTP/1.1 417 Expectation Failed Date: Thu, 20 May 2010 05:38:21 GMT Server: hi Vary: Accept-Encoding Content-Length: 364 Connection: close Content-Type: text/html; charset=iso-8859-1 !DOCTYPE HTML PUBLIC -//IETF//DTD HTML 2.0//EN htmlhead title417 Expectation Failed/title /headbody h1Expectation Failed/h1 pThe expectation given in the Expect request-header field could not be met by this server./p pThe client sentpre Expect: 100-Continue /pre but we only allow the 100-continue expectation./p /body/html -- Richard
[twitter-dev] Twitter does not allow to login
Hello, I have an iphone applicaton in which I am using XAuthTwitterEngineDemo source code downloaded from github. Primarily it was working fine. Suddenly it stopped working. When ever I login it gives Authentication error like Please check your username and password and try again. I am giving correct username and password. It was working fine previously. Even tried another consumer ke and sectet key but it stills gives same error. I am not getting any idea about that. What should I do. Please help me
[twitter-dev] friends.xml fails for some accounts
Hello, I'm building a small fun application can be found here: http://godstroke.com/exterminatweet/ I'ts on flash/flex4. I'm using a php proxy page to cross over the crossdomain.xml problem. I send gateway.php?u=username , than it calls the service: http://api.twitter.com/1/statuses/friends.xml?screen_name=username . It works perfectly fine on my account @godstroke but fails on some accounts. First I thought it may be happening because they are protected accounts. But no, for example speedbrkr and emrebuyukoazkan are failing. You can view the source by right click-view source on flash application. What I'm exactly asking is, is there any option on twitter accounts to make them inaccessible by twitter rest api? Or, most probably just a coincidence users from my country TR are working, but others are failing, is there a encoding issue among users from different countires? How come these two xml responses are different, last one fails: http://godstroke.com/exterminatweet/gateway.php?u=godstroke http://godstroke.com/exterminatweet/gateway.php?u=emrebuyukozkan thanks.
[twitter-dev] Checking Application Rate Limit
Our app authenticates users with Twitter (using oAuth) and then sends API calls like 1. users show 2. status friends These calls do NOT require authentication but we want them to count against user's limit -- so it goes to 150/hr on users quota and NOT the app quota. However, even after making sure that the user is authenticated, these are not deducting the user's limit. curl -u user:password http://api.twitter.com/1/account/rate_limit_status.xml gives the same number - it does not get deducted. It seems that they are still getting counted in the app quota of 150/ hr. Q1. How do we check if the app quota is getting deducted? Q2. How do we create/make the api calls so that they count against the user's quota? Thanks
[twitter-dev] Re: Incorrect signature when calling update url /1/statuses/update.xml
Hi Taylor,
I am using Curl to update status.
I use POST method.
The new status is not included in the headers, but is included in the
POST body and in the signature base string.
Also (and this Curl does automatically for me) I am sending the
following header:
Content-Type: application/x-www-form-urlencoded.
My new status value is URL encoded (UTF-8).
And now to the business itself:
I know my signature method is correct since I am able to update single
word statuses with no special characters, such as: hello, ok,
magnificent and such. They work just fine.
But when trying to update statuses with characters such as: , !,
@. It will throw me with a 401:
{request:/1/statuses/update.json,error:Incorrect
signature}
I'm attaching here the curl verbose:
curl -v -X POST -H 'Authorization: OAuth
oauth_nonce=5671352764895675466, oauth_signature_method=HMAC-SHA1,
oauth_timestamp=1274355202, oauth_consumer=**,
oauth_signature=**,
oauth_version=1.0,
oauth_token=**' -d
status=magnificent https://api.twitter.com/1/statuses/update.json
* About to connect() to api.twitter.com port 443 (#0)
* Trying 128.242.240.61... connected
* Connected to api.twitter.com (128.242.240.61) port 443 (#0)
* successfully set certificate verify locations:
* CAfile: none
CApath: /etc/ssl/certs
* SSLv3, TLS handshake, Client hello (1):
* SSLv3, TLS handshake, Server hello (2):
* SSLv3, TLS handshake, CERT (11):
* SSLv3, TLS handshake, Server finished (14):
* SSLv3, TLS handshake, Client key exchange (16):
* SSLv3, TLS change cipher, Client hello (1):
* SSLv3, TLS handshake, Finished (20):
* SSLv3, TLS change cipher, Client hello (1):
* SSLv3, TLS handshake, Finished (20):
* SSL connection using AES256-SHA
* Server certificate:
*subject: C=US; O=*.twitter.com; OU=GT57932074; OU=See
www.rapidssl.com/resources/cps (c)09; OU=Domain Control Validated -
RapidSSL(R); CN=*.twitter.com
*start date: 2009-05-26 12:14:57 GMT
*expire date: 2010-07-27 06:10:16 GMT
*common name: *.twitter.com (matched)
*issuer: C=US; O=Equifax Secure Inc.; CN=Equifax Secure Global
eBusiness CA-1
*SSL certificate verify ok.
POST /1/statuses/update.json HTTP/1.1
User-Agent: curl/7.19.7 (i486-pc-linux-gnu) libcurl/7.19.7 OpenSSL/0.9.8k
zlib/1.2.3.3 libidn/1.15
Host: api.twitter.com
Accept: */*
Authorization: OAuth oauth_nonce=5671352764895675466,
oauth_signature_method=HMAC-SHA1, oauth_timestamp=1274355202,
oauth_consumer_key=**,
oauth_signature=**,
oauth_version=1.0, oauth_token=**
Content-Length: 18
Content-Type: application/x-www-form-urlencoded
HTTP/1.1 200 OK
Date: Thu, 20 May 2010 11:27:15 GMT
Server: hi
Status: 200 OK
X-Transaction: 1274354835-66746-24190
ETag: 61a0fc27a676be7b50eb72042998d554
Last-Modified: Thu, 20 May 2010 11:27:15 GMT
X-Runtime: 0.18394
Content-Type: application/json; charset=utf-8
Content-Length: 1212
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=62.219.129.78.1274354835642625; path=/; expires=Thu,
27-May-10 11:27:15 GMT; domain=.twitter.com
Set-Cookie: guest_id=127435483564553842; path=/; expires=Sat, 19 Jun
2010 11:27:15 GMT
Set-Cookie: lang=en; path=/
Set-Cookie:
_twitter_sess=BAh7CjoRdHJhbnNfcHJvbXB0MDoPY3JlYXRlZF9hdGwrCMegd7UoAToMY3Ny
%250AZl9pZCIlNTUxMThjYjg0ZTc2MTU2MzAwZWM1MjA1NGMxMmNlZGM6B2lkIiVm
%250AOTdiMWFlNTc4OGZhODM2NjRkZTRhMTdkMTgxOGFlMSIKZmxhc2hJQzonQWN0%250AaW9uQ29udHJvbGxlcjo6Rmxhc2g6OkZsYXNoSGFzaHsABjoKQHVzZWR7AA
%253D%253D--0b5f5cee23124380fd2db90ff369fee30c0122d9;
domain=.twitter.com; path=/
Vary: Accept-Encoding
Connection: close
{in_reply_to_user_id:null,contributors:null,source:a href=
\http://www.snaptu.com\; rel=\nofollow\Snaptu Mobile/
a,created_at:Thu May 20 11:27:15 +
2010,in_reply_to_screen_name:null,place:null,favorited:false,truncated:false,in_reply_to_status_id:null,coordinates:null,user:
{favourites_count:
2,description:*,contributors_enabled:false,lang:en,profile_link_color:ff,profile_image_url:http://
s.twimg.com/a/1274144130/images/
default_profile_2_normal.png,geo_enabled:false,time_zone:Greenland,profile_sidebar_fill_color:e0ff92,screen_name:SnaptuDummy,following:false,verified:false,created_at:Sun
Mar 22 13:31:04 + 2009,profile_background_image_url:http://
s.twimg.com/a/1274144130/images/themes/theme1/
bg.png,profile_background_tile:false,followers_count:
24,protected:false,url:http://
www.snaptu.com,name:*,friends_count:*,profile_sidebar_border_color:87bc44,profile_background_color*
Closing connection #0
* SSLv3, TLS alert, Client hello (1):
:9ae4e8,location:Israel,id:25817409,statuses_count:
Re: [twitter-dev] statuses/update: Expect: 100-Continue header rejected
[Charset ISO-8859-1 unsupported, filtering to ASCII...] I've been playing with oacurl https://code.google.com/apis/buzz/v1/oacurl.html and tried to use it to send a tweet. oacurl sends Expect: 100-Continue but Twitter rejects this with we only allow the 100-continue expectation. This seems to violate http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.20 Comparison of expectation values is case-insensitive for unquoted tokens (including the 100-continue token). Is this fixable, or avoidable in the meantime? (I know about twurl, but oacurl seems generic - can I use twurl to make oauth calls to MySpace?) Just change the header to simply send a blank Expect:. With regular cURL a simple -H Expect: will work. -- personal: http://www.cameronkaiser.com/ -- Cameron Kaiser * Floodgap Systems * www.floodgap.com * ckai...@floodgap.com -- I couldn't care less about apathy. -
[twitter-dev] search api :slowdown or throttling?
Our app uses the search api extensively and we've noticed that the response time has fallen dramatically for aggregates of search requests in the past days . Is that really the case? Our production app is using basic auth at the moment, and we're wondering if that's a factor in this? jeffrey greenberg
Re: [twitter-dev] Re: Incorrect signature when calling update url /1/statuses/update.xml
Hi Onn,
It's best to consider all space characters as %20 when building both your
POST body and signature base string -- instead of using or +, just get
right down to it as %20.
I'll show you how a pretty varied string of characters would be correctly
encoded both for the POST body and signature base string:
Given that you want to set a status that says: I can tweet many kinds of
characters ! (* $ @ 漢字 عربي)
Your POST body should have that string encoded as:
status=I%20can%20tweet%20many%20kinds%20of%20characters%20%21%20%28%2A%20%24%20%40%20%E6%BC%A2%E5%AD%97%20%D8%B9%D8%B1%D8%A8%D9%8A%29
Which when passed into your Signature Base String will get URL escaped
again:
POSThttp%3A%2F%2Fapi.twitter.com
%2F1%2Fstatuses%2Fupdate.xmloauth_consumer_key%3Dri8JxYK2ddwSV5xIUfNNvQ%26oauth_nonce%3DFt6p0YgKlI2Htdk3WLE4mthwQXVpWc9Nv9ApzoQKUg%26oauth_signature_method%3DHMAC-SHA1%26oauth_timestamp%3D1274362505%26oauth_token%3D119476949-gF0B5O1Wwa2UqqIwopAhQtQVTzmfSIOSiHQS7Vf8%26oauth_version%3D1.0%26status%3DI%2520can%2520tweet%2520many%2520kinds%2520of%2520characters%2520%2521%2520%2528%252A%2520%2524%2520%2540%2520%25E6%25BC%25A2%25E5%25AD%2597%2520%25D8%25B9%25D8%25B1%25D8%25A8%25D9%258A%2529
The Content-Length for that fully-encoded POST body will be: 69
And when Twitter spits the status back at you, in my case in XML:
?xml version=1.0 encoding=UTF-8?
status
created_atThu May 20 13:35:04 + 2010/created_at
id14361447181/id
textI can tweet many kinds of characters ! (* $ @ #28450;#23383;
#1593;#1585;#1576;#1610;)/text
sourcelt;a href=quot;http://realitytechnicians.comquot;
rel=quot;nofollowquot;gt;Crying Indianlt;/agt;/source
truncatedfalse/truncated
in_reply_to_status_id/in_reply_to_status_id
in_reply_to_user_id/in_reply_to_user_id
favoritedfalse/favorited
in_reply_to_screen_name/in_reply_to_screen_name
user
id119476949/id
nameOAuth Dancer/name
screen_nameoauth_dancer/screen_name
locationSan Francisco, CA/location
description/description
profile_image_url
http://a3.twimg.com/profile_images/730275945/oauth-dancer_normal.jpg
/profile_image_url
urlhttp://bit.ly/oauth-dancer/url
protectedfalse/protected
followers_count11/followers_count
profile_background_colorC0DEED/profile_background_color
profile_text_color33/profile_text_color
profile_link_color0084B4/profile_link_color
profile_sidebar_fill_colorDDEEF6/profile_sidebar_fill_color
profile_sidebar_border_colorC0DEED/profile_sidebar_border_color
friends_count11/friends_count
created_atWed Mar 03 19:37:35 + 2010/created_at
favourites_count0/favourites_count
utc_offset/utc_offset
time_zone/time_zone
profile_background_image_url
http://a3.twimg.com/profile_background_images/80151733/oauth-dance.png
/profile_background_image_url
profile_background_tiletrue/profile_background_tile
notificationsfalse/notifications
geo_enabledfalse/geo_enabled
verifiedfalse/verified
followingfalse/following
statuses_count31/statuses_count
langen/lang
contributors_enabledfalse/contributors_enabled
/user
geo/
coordinates/
place/
contributors/
/status
Hope this helps.
Taylor
On Thu, May 20, 2010 at 5:03 AM, Onn E onn.elbo...@gmail.com wrote:
Hi Taylor,
I am using Curl to update status.
I use POST method.
The new status is not included in the headers, but is included in the
POST body and in the signature base string.
Also (and this Curl does automatically for me) I am sending the
following header:
Content-Type: application/x-www-form-urlencoded.
My new status value is URL encoded (UTF-8).
And now to the business itself:
I know my signature method is correct since I am able to update single
word statuses with no special characters, such as: hello, ok,
magnificent and such. They work just fine.
But when trying to update statuses with characters such as: , !,
@. It will throw me with a 401:
{request:/1/statuses/update.json,error:Incorrect
signature}
I'm attaching here the curl verbose:
curl -v -X POST -H 'Authorization: OAuth
oauth_nonce=5671352764895675466, oauth_signature_method=HMAC-SHA1,
oauth_timestamp=1274355202, oauth_consumer=**,
oauth_signature=**,
oauth_version=1.0,
oauth_token=**' -d
status=magnificent https://api.twitter.com/1/statuses/update.json
* About to connect() to api.twitter.com port 443 (#0)
* Trying 128.242.240.61... connected
* Connected to api.twitter.com (128.242.240.61) port 443 (#0)
* successfully set certificate verify locations:
* CAfile: none
CApath: /etc/ssl/certs
* SSLv3, TLS handshake, Client hello (1):
* SSLv3, TLS handshake, Server hello (2):
* SSLv3, TLS handshake, CERT (11):
* SSLv3, TLS handshake, Server finished (14):
* SSLv3, TLS handshake, Client key exchange (16):
* SSLv3, TLS change cipher, Client hello (1):
* SSLv3, TLS handshake, Finished
[twitter-dev] xml formatted data?
Hi there, Can somebody here tell me that why I am getting .xml format data as only values and not in key-value pair? Suppose request url is : http://api.twitter.com/1/account/rate_limit_status.xml response is: 143 150 1274354584 2010-05-20T11:23:04+00:00 why I am not getting key:value pair as getting previously. Please help me on this. Thank you in advance. Rushi
Re: [twitter-dev] search api :slowdown or throttling?
Hi Jeff, We've been having some general performance issues recently ( http://status.twitter.com/ ). If you're a heavy user of the search API, you may be better served by our Streaming API ( http://apiwiki.twitter.com/Streaming-API-Documentation ). Taylor Singletary Developer Advocate, Twitter http://twitter.com/episod On Thu, May 20, 2010 at 6:44 AM, Jeffrey Greenberg jeffreygreenb...@gmail.com wrote: Our app uses the search api extensively and we've noticed that the response time has fallen dramatically for aggregates of search requests in the past days . Is that really the case? Our production app is using basic auth at the moment, and we're wondering if that's a factor in this? jeffrey greenberg
Re: [twitter-dev] xml formatted data?
Hi Rushi, I haven't seen behavior like this before. How are you reading the response? Are you sure you're looking at the raw response sent in the HTTP request? Are you using a web browser or a library that might be processing the XML incorrectly or rendering the XML as if it were HTML (which is what sounds most likely)? Taylor Singletary Developer Advocate, Twitter http://twitter.com/episod On Thu, May 20, 2010 at 6:58 AM, Rushikesh Bhanage rishibhan...@gmail.comwrote: Hi there, Can somebody here tell me that why I am getting .xml format data as only values and not in key-value pair? Suppose request url is : http://api.twitter.com/1/account/rate_limit_status.xml response is: 143 150 1274354584 2010-05-20T11:23:04+00:00 why I am not getting key:value pair as getting previously. Please help me on this. Thank you in advance. Rushi
[twitter-dev] re: json response shape
Is there anywhere in the documentation that shows what fields you could expect in the json responses for the api methods or is it just a case of hit the service and work out what fields there are to play with from the responses?
Re: [twitter-dev] Re: No oauth_verifier in custom URI (Desktop)
Hi Jeena, We have a fix queued for deploy sometime in the next week or so. I'll let you know when it's available. Taylor Singletary Developer Advocate, Twitter http://twitter.com/episod On Sun, May 16, 2010 at 2:47 AM, Jeena jeenaparad...@gmail.com wrote: Something new on this topic? /Jeena
Re: [twitter-dev] Oauth authentication - reg
Hi Suresh, This library for AS3 supports OAuth, though I can't speak to how well-written or to-spec it is. http://code.google.com/p/oauth-as3/ Taylor Singletary Developer Advocate, Twitter http://twitter.com/episod On Tue, May 18, 2010 at 11:46 AM, Suresh Kumar suresh.aa...@gmail.comwrote: Hi, Is there any api for as3 available? Suresh Kumar On Tue, May 18, 2010 at 7:10 PM, Taylor Singletary taylorsinglet...@twitter.com wrote: Hi, Basic authentication, which is the method of sending a username and password on each API call through HTTP Basic Auth, is going away in June. The best path to implementing secure authentication that doesn't put users at risk is OAuth ( http://dev.twitter.com/pages/auth_overview and http://dev.twitter.com/pages/auth ) For certain kinds of applications that do not have ready access to a web browser and who would rather eschew the entire OAuth out-of-band flow (which is more appropriate and introduces less risk at the cost of what some may perceive as a poorer user experience), we offer xAuth on an approval-basis. xAuth still requires implementing most of the OAuth standard, but allows you to exchange a username and password, with the user's permission, for an OAuth access token. You would then dispose of the login and password given by the user and use an access token, which the user can revoke at any time, to access resources on the member's behalf. You can read about xAuth at http://dev.twitter.com/pages/xauth . Taylor Singletary Developer Advocate, Twitter http://twitter.com/episod On Tue, May 18, 2010 at 5:58 AM, Sigma suresh.aa...@gmail.com wrote: Hi, I'm a newbie. i want to know how to get username and password from folks accessing my application and tweet on behalf of them? Is this the basic authentication twitter is about to close by june? And is there any way to get this work done? i don't know where to start. kindly reply with tutorials or explanations. Thanks in Advance.
Re: [twitter-dev] leave API problem
notifications/leave stops the authenticating user from receiving SMS notifications of the specified user's tweets. If you'd like to unfollow a user, you're looking for friendships/destroy: http://dev.twitter.com/doc/post/friendships/destroy -- Chris Thomson On May 20, 2010, at 12:05 PM, roteva wrote: Hello, I am seeing a problem using https://api.twitter.com/1/notifications/leave.xml, (with oauth) in that it returns a good status (200), with the correct user info specifying the user I want to un-follow. However, the follow/friend status is unchanged. AM I using the wrong API method to unfollow? Thanks for any hints, Bernd
[twitter-dev] Re: Incorrect signature when calling update url /1/statuses/update.xml
Taylor, I am having a very similar problem. I think I am missing some crucial point about the encoding method that needs to be used with twitter. THe library I am working on has successfully authenticated using Oauth with twitter. I have my access_token and access_token_secret and I want to update my twitter status. If I only send one word as my status, the update works. If I send two words separated by a space the update does not work. I get back a 401 unauthorized response to the udpate request. My signing base string POST request and response are below. As noted I have already negotiated and OAuth access token so I don't show that information. I noticed one thing in your example that is different from my code. In my signing base string a space is encoded as %20. In yours, a space is encoded as %2520. Do you have any ideas what the difference is between your encoding method and mine? Here is my signature base string: POSThttp%3A%2F%2Fapi.twitter.com%2F1%2Fstatuses %2Fupdate.xmloauth_consumer_key%3Dbt7VUyYJ4adSHxIrGJYFxQ%26oauth_nonce %3DISJERMBJCAQEYGUAWXAKQXTFPGFATRFUOQORGAMD%26oauth_signature_method %3DHMAC-SHA1%26oauth_timestamp%3D1274372472%26oauth_token %3D136131415-1kvYKiXUP8kS7yq39cGqmruDzvsF7uOoLPSK7Eh1%26oauth_version %3D1.0%26status%3Dtest%20this And the POST request I made follows below: POST http://api.twitter.com/1/statuses/update.xml HTTP/1.1 Authorization: OAuth oauth_consumer_key=bt7VUyYJ4adSHxIrGJYFxQ, oauth_nonce=ISJERMBJCAQEYGUAWXAKQXTFPGFATRFUOQORGAMD, oauth_signature_method=HMAC-SHA1, oauth_timestamp=1274372472, oauth_token=136131415-1kvYKiXUP8kS7yq39cGqmruDzvsF7uOoLPSK7Eh1, oauth_version=1.0, oauth_signature=mkF7LWE4UqscMsjUlLQTRJFDFhg%3D Content-Type: application/x-www-form-urlencoded Host: api.twitter.com Content-Length: 18 Expect: 100-continue status=test%20this And the POST response HTTP/1.1 401 Unauthorized Connection: Keep-Alive Connection: Proxy-Support Content-Length: 135 Via: 1.1 RED-PRXY-21 Expires: Thu, 20 May 2010 16:51:16 GMT Date: Thu, 20 May 2010 16:21:16 GMT Content-Type: application/xml; charset=utf-8 Server: hi Proxy-Support: Session-Based-Authentication Status: 401 Unauthorized WWW-Authenticate: Basic realm=Twitter API Cache-Control: no-cache, max-age=1800 Set-Cookie: k=131.107.0.71.1274372476598501; path=/; expires=Thu, 27- May-10 16:21:16 GMT; domain=.twitter.com Set-Cookie: guest_id=127437247670844927; path=/; expires=Sat, 19 Jun 2010 16:21:16 GMT Set-Cookie: _twitter_sess=BAh7CDoPY3JlYXRlZF9hdGwrCDLPhLYoAToHaWQiJTE1M2MzMzg5ODc4MzI4%250ANDlkMWMwYjFlMzZkMTlkYTdkIgpmbGFzaElDOidBY3Rpb25Db250cm9sbGVy %250AOjpGbGFzaDo6Rmxhc2hIYXNoewAGOgpAdXNlZHsA-- c409bb092a71a15b4823075255ee464267520fba; domain=.twitter.com; path=/ Vary: Accept-Encoding ?xml version=1.0 encoding=UTF-8? hash request/1/statuses/update.xml/request errorIncorrect signature/error /hash On May 20, 6:45 am, Taylor Singletary taylorsinglet...@twitter.com wrote: Hi Onn, It's best to consider all space characters as %20 when building both your POST body and signature base string -- instead of using or +, just get right down to it as %20. I'll show you how a pretty varied string of characters would be correctly encoded both for the POST body and signature base string: Given that you want to set a status that says: I can tweet many kinds of characters ! (* $ @ 漢字 عربي) Your POST body should have that string encoded as: status=I%20can%20tweet%20many%20kinds%20of%20characters%20%21%20%28%2A%20%24%20%40%20%E6%BC%A2%E5%AD%97%20%D8%B9%D8%B1%D8%A8%D9%8A%29 Which when passed into your Signature Base String will get URL escaped again: POSThttp%3A%2F%2Fapi.twitter.com %2F1%2Fstatuses%2Fupdate.xmloauth_consumer_key%3Dri8JxYK2ddwSV5xIUfNNvQ%26oauth_nonce%3DFt6p0YgKlI2Htdk3WLE4mthwQXVpWc9Nv9ApzoQKUg%26oauth_signature_method%3DHMAC-SHA1%26oauth_timestamp%3D1274362505%26oauth_token%3D119476949-gF0B5O1Wwa2UqqIwopAhQtQVTzmfSIOSiHQS7Vf8%26oauth_version%3D1.0%26status%3DI%2520can%2520tweet%2520many%2520kinds%2520of%2520characters%2520%2521%2520%2528%252A%2520%2524%2520%2540%2520%25E6%25BC%25A2%25E5%25AD%2597%2520%25D8%25B9%25D8%25B1%25D8%25A8%25D9%258A%2529 The Content-Length for that fully-encoded POST body will be: 69 And when Twitter spits the status back at you, in my case in XML: ?xml version=1.0 encoding=UTF-8? status created_atThu May 20 13:35:04 + 2010/created_at id14361447181/id textI can tweet many kinds of characters ! (* $ @ #28450;#23383; #1593;#1585;#1576;#1610;)/text sourcelt;a href=quot;http://realitytechnicians.com; rel=quot;nofollowquot;gt;Crying Indianlt;/agt;/source truncatedfalse/truncated in_reply_to_status_id/in_reply_to_status_id in_reply_to_user_id/in_reply_to_user_id favoritedfalse/favorited in_reply_to_screen_name/in_reply_to_screen_name user id119476949/id nameOAuth Dancer/name screen_nameoauth_dancer/screen_name locationSan Francisco, CA/location description/description
Re: [twitter-dev] Re: Basic authentication
On Tue, May 18, 2010 at 2:13 PM, Eric wetr...@gmail.com wrote: We are using the Streaming API and will only be using our own credentials. Our experience with OAuth in other services has not been positive, so like TJ says huge hassle for no gain. Although I was able to finally adapt to Oauth (thanks for Abraham and thanks to Scott), I agree that for folks who have web apps that do not require them to collect other people's logins, or to give their own to a third party, that it does seem a shame that provisions haven't been made to let those apps continue as is. Sorta looks like fixing what aint broke.
Re: [twitter-dev] Checking Application Rate Limit
Our implementation here is less than optimal at the moment during the transition from basic auth to OAuth. At least as it currently stands, you should think of API methods that require authentication to mean requires an access token with OAuth. In Basic Auth, it meant that you needed to provide a user and password with the request. If the API method doesn't require authentication that means that you don't need an access token to complete the request. Today, Twitter doesn't support two-legged OAuth, which would be the means that your application could identify itself to Twitter and make requests without an access token. This would be the most appropriate way for Twitter to handle calls that are essentially consumer-to-service-provider without a user. Without two-legged OAuth support at Twitter yet, your best bet might be to not use authentication at all when accessing resources that don't require auth -- meaning, you just do simple REST calls without identifying yourself with any OAuth parameters, basic auth, or otherwise (though a User-Agent is always appreciated). Your requests would then be applied to the general whitelist yielded solely to a requesting IP address. Long-term, the right thing for Twitter to do here is support two-legged OAuth. When your application is doing something that doesn't involve a user in some way, you'd sign your requests and identify yourself as your application while accessing the resource, but would not be supplying an access token. In this scenario, all API requests, whether they require authentication by a member or not, would require application-level authorization. Taylor Singletary Developer Advocate, Twitter http://twitter.com/episod On Thu, May 20, 2010 at 1:20 AM, ALSPL ritikasan...@gmail.com wrote: Our app authenticates users with Twitter (using oAuth) and then sends API calls like 1. users show 2. status friends These calls do NOT require authentication but we want them to count against user's limit -- so it goes to 150/hr on users quota and NOT the app quota. However, even after making sure that the user is authenticated, these are not deducting the user's limit. curl -u user:password http://api.twitter.com/1/account/rate_limit_status.xml gives the same number - it does not get deducted. It seems that they are still getting counted in the app quota of 150/ hr. Q1. How do we check if the app quota is getting deducted? Q2. How do we create/make the api calls so that they count against the user's quota? Thanks
[twitter-dev] Is OAuth working for *anyone* out there?
For the last few days, *every* single OAuth request I issue has been met with a 401. Also, trying to access this URL, the OAuth app details page for Twitter Karma, results in a fail whale - consistently: http://twitter.com/oauth_clients/details/1574 Is OAuth down for everyone, or just me? -- Dossy Shiobara | do...@panoptic.com | http://dossy.org/ Panoptic Computer Network | http://panoptic.com/ He realized the fastest way to change is to laugh at your own folly -- then you can let go and quickly move on. (p. 70)
[twitter-dev] Re: leave API problem
On May 20, 12:12 pm, Chris Thomson chri...@chris24.ca wrote: notifications/leave stops the authenticating user from receiving SMS notifications of the specified user's tweets. If you'd like to unfollow a user, you're looking for friendships/destroy:http://dev.twitter.com/doc/post/friendships/destroy -- Chris Thomson Yes that would explain it. Thank you. Bernd On May 20, 2010, at 12:05 PM, roteva wrote: Hello, I am seeing a problem using https://api.twitter.com/1/notifications/leave.xml, (with oauth) in that it returns a good status (200), with the correct user info specifying the user I want to un-follow. However, the follow/friend status is unchanged. AM I using the wrong API method to unfollow? Thanks for any hints, Bernd
Re: [twitter-dev] Is OAuth working for *anyone* out there?
Hi Dossy, While we have been having some performance issues that should give you occasional 401s, it shouldn't be as widespread as the experience you've been having. When we throw a 401, we typically provide an error message within the body of the response -- if you can share that it would be helpful. Also, you can find a version of your OAuth application details page on the new home at dev.twitter.com by browsing to http://dev.twitter.com/apps/show/1574 -- it doesn't try to report to you the # of access tokens registered to your application, which is the cause of failure in the old interface. The old interface will redirect to the new interface soon. Has anything about your environment changed? Have you reset your consumer key or secret? Does this happen for all access tokens or is there a specific access token that you use that is failing? Is it possible that access token's access was revoked? The error message provided on 401s will help shine some light on some of this. One recent change we made is that if you're trying to access resources that don't require authentication, but you are still providing OAuth credentials and those credentials are invalid, we no longer provide the data but instead properly inform you that your credentials aren't valid. Which, if any, OAuth library do you use? Thanks, Taylor Singletary Developer Advocate, Twitter http://twitter.com/episod On Thu, May 20, 2010 at 10:21 AM, Dossy Shiobara do...@panoptic.com wrote: For the last few days, *every* single OAuth request I issue has been met with a 401. Also, trying to access this URL, the OAuth app details page for Twitter Karma, results in a fail whale - consistently: http://twitter.com/oauth_clients/details/1574 Is OAuth down for everyone, or just me? -- Dossy Shiobara | do...@panoptic.com | http://dossy.org/ Panoptic Computer Network | http://panoptic.com/ He realized the fastest way to change is to laugh at your own folly -- then you can let go and quickly move on. (p. 70)
Re: [twitter-dev] Is OAuth working for *anyone* out there?
On 5/20/10 3:16 PM, Taylor Singletary wrote: While we have been having some performance issues that should give you occasional 401s, it shouldn't be as widespread as the experience you've been having. OK, you know, until *literally* 60 seconds ago, requests for http://twitter.com/oauth_clients/details/1574 were returning 502 fail whales. NOW, it just loaded. OK, who fixed it just now? What was broken? When we throw a 401, we typically provide an error message within the body of the response -- if you can share that it would be helpful. As I said in my email the other day: HTTP 401, Failed to validate oauth signature and token Has anything about your environment changed? Sadly, no. I wish it were that simple. Have you reset your consumer key or secret? No, and I just verified again that it still matches what is showing in the Twitter OAuth apps page. Does this happen for all access tokens or is there a specific access token that you use that is failing? Is it possible that access token's access was revoked? The error message provided on 401s will help shine some light on some of this. It's happening on the very first, and every single, /oauth/request_token API call. One recent change we made is that if you're trying to access resources that don't require authentication, but you are still providing OAuth credentials and those credentials are invalid, we no longer provide the data but instead properly inform you that your credentials aren't valid. Again, I'm not even getting as far as making a Twitter API call any more. The whole OAuth process is failing at the request_token endpoint. Which, if any, OAuth library do you use? Homegrown. Has been working for over a year, and has not been modified the entire time. -- Dossy Shiobara | do...@panoptic.com | http://dossy.org/ Panoptic Computer Network | http://panoptic.com/ He realized the fastest way to change is to laugh at your own folly -- then you can let go and quickly move on. (p. 70)
Re: [twitter-dev] Is OAuth working for *anyone* out there?
Sorry you're having trouble, Dossy. Can you share the complete path you're using to fetch a request token (with host, domain, protocol, path, and any query parameters), your signature base string, and an authorization header if you're using header-based auth? Taylor Singletary Developer Advocate, Twitter http://twitter.com/episod On Thu, May 20, 2010 at 12:29 PM, Dossy Shiobara do...@panoptic.com wrote: On 5/20/10 3:16 PM, Taylor Singletary wrote: While we have been having some performance issues that should give you occasional 401s, it shouldn't be as widespread as the experience you've been having. OK, you know, until *literally* 60 seconds ago, requests for http://twitter.com/oauth_clients/details/1574 were returning 502 fail whales. NOW, it just loaded. OK, who fixed it just now? What was broken? When we throw a 401, we typically provide an error message within the body of the response -- if you can share that it would be helpful. As I said in my email the other day: HTTP 401, Failed to validate oauth signature and token Has anything about your environment changed? Sadly, no. I wish it were that simple. Have you reset your consumer key or secret? No, and I just verified again that it still matches what is showing in the Twitter OAuth apps page. Does this happen for all access tokens or is there a specific access token that you use that is failing? Is it possible that access token's access was revoked? The error message provided on 401s will help shine some light on some of this. It's happening on the very first, and every single, /oauth/request_token API call. One recent change we made is that if you're trying to access resources that don't require authentication, but you are still providing OAuth credentials and those credentials are invalid, we no longer provide the data but instead properly inform you that your credentials aren't valid. Again, I'm not even getting as far as making a Twitter API call any more. The whole OAuth process is failing at the request_token endpoint. Which, if any, OAuth library do you use? Homegrown. Has been working for over a year, and has not been modified the entire time. -- Dossy Shiobara | do...@panoptic.com | http://dossy.org/ Panoptic Computer Network | http://panoptic.com/ He realized the fastest way to change is to laugh at your own folly -- then you can let go and quickly move on. (p. 70)
Re: [twitter-dev] Re: Incorrect signature when calling update url /1/statuses/update.xml
FYI - I am writing a .Net based library and so I currently use System.Uri.EscapeDataStringhttp://msdn.microsoft.com/en-us/library/system.uri.escapedatastring.aspxto do my escaping I don't know what that routine is, but if it's not RFC 3986 compliant, it won't work. You might want to roll your own, it's a couple lines of code and a regex. -- personal: http://www.cameronkaiser.com/ -- Cameron Kaiser * Floodgap Systems * www.floodgap.com * ckai...@floodgap.com -- EH! STEVE! ---
Re: [twitter-dev] Is OAuth working for *anyone* out there?
Hey guys, Don't know if this is related, but I was testing a friend's iPad app this morning which uses xAuth. When setting up a new account in his app, the app authorizes in my Connections tab. However, whenever his app tries to use the tokens, we get an immediate HTTP 401. None of the calls with the tokens he has received are working for accessing. His account, which was auth'd (tokens retreived) over a month ago, still works ok with his app, but my new setup with the same client codebase is now failing. It seems like there might be something wrong with the OAuth tokens being issued, but that seems kinda crazy that there could be a problem that widespread. -damon On Thu, May 20, 2010 at 2:29 PM, Dossy Shiobara do...@panoptic.com wrote: On 5/20/10 3:16 PM, Taylor Singletary wrote: While we have been having some performance issues that should give you occasional 401s, it shouldn't be as widespread as the experience you've been having. OK, you know, until *literally* 60 seconds ago, requests for http://twitter.com/oauth_clients/details/1574 were returning 502 fail whales. NOW, it just loaded. OK, who fixed it just now? What was broken? When we throw a 401, we typically provide an error message within the body of the response -- if you can share that it would be helpful. As I said in my email the other day: HTTP 401, Failed to validate oauth signature and token Has anything about your environment changed? Sadly, no. I wish it were that simple. Have you reset your consumer key or secret? No, and I just verified again that it still matches what is showing in the Twitter OAuth apps page. Does this happen for all access tokens or is there a specific access token that you use that is failing? Is it possible that access token's access was revoked? The error message provided on 401s will help shine some light on some of this. It's happening on the very first, and every single, /oauth/request_token API call. One recent change we made is that if you're trying to access resources that don't require authentication, but you are still providing OAuth credentials and those credentials are invalid, we no longer provide the data but instead properly inform you that your credentials aren't valid. Again, I'm not even getting as far as making a Twitter API call any more. The whole OAuth process is failing at the request_token endpoint. Which, if any, OAuth library do you use? Homegrown. Has been working for over a year, and has not been modified the entire time. -- Dossy Shiobara | do...@panoptic.com | http://dossy.org/ Panoptic Computer Network | http://panoptic.com/ He realized the fastest way to change is to laugh at your own folly -- then you can let go and quickly move on. (p. 70) -- http://twitter.com/damon http://blog.damonc.com
Re: [twitter-dev] Is OAuth working for *anyone* out there?
i support dossy too From: Taylor Singletary taylorsinglet...@twitter.com To: twitter-development-talk@googlegroups.com Sent: Thu, May 20, 2010 1:27:26 PM Subject: Re: [twitter-dev] Is OAuth working for *anyone* out there? Sorry you're having trouble, Dossy. Can you share the complete path you're using to fetch a request token (with host, domain, protocol, path, and any query parameters), your signature base string, and an authorization header if you're using header-based auth? Taylor Singletary Developer Advocate, Twitter http://twitter.com/episod On Thu, May 20, 2010 at 12:29 PM, Dossy Shiobara do...@panoptic.com wrote: On 5/20/10 3:16 PM, Taylor Singletary wrote: While we have been having some performance issues that should give you occasional 401s, it shouldn't be as widespread as the experience you've been having. OK, you know, until *literally* 60 seconds ago, requests for http://twitter.com/oauth_clients/details/1574 were returning 502 fail whales. NOW, it just loaded. OK, who fixed it just now? What was broken? When we throw a 401, we typically provide an error message within the body of the response -- if you can share that it would be helpful. As I said in my email the other day: HTTP 401, Failed to validate oauth signature and token Has anything about your environment changed? Sadly, no. I wish it were that simple. Have you reset your consumer key or secret? No, and I just verified again that it still matches what is showing in the Twitter OAuth apps page. Does this happen for all access tokens or is there a specific access token that you use that is failing? Is it possible that access token's access was revoked? The error message provided on 401s will help shine some light on some of this. It's happening on the very first, and every single, /oauth/request_token API call. One recent change we made is that if you're trying to access resources that don't require authentication, but you are still providing OAuth credentials and those credentials are invalid, we no longer provide the data but instead properly inform you that your credentials aren't valid. Again, I'm not even getting as far as making a Twitter API call any more. The whole OAuth process is failing at the request_token endpoint. Which, if any, OAuth library do you use? Homegrown. Has been working for over a year, and has not been modified the entire time. -- Dossy Shiobara | do...@panoptic.com| http://dossy.org/ Panoptic Computer Network | http://panoptic.com/ He realized the fastest way to change is to laugh at your own folly -- then you can let go and quickly move on. (p. 70)
Re: [twitter-dev] Re: Incorrect signature when calling update url /1/statuses/update.xml
my code 401 . From: Cameron Kaiser spec...@floodgap.com To: twitter-development-talk@googlegroups.com Sent: Thu, May 20, 2010 1:28:44 PM Subject: Re: [twitter-dev] Re: Incorrect signature when calling update url /1/statuses/update.xml FYI - I am writing a .Net based library and so I currently use System.Uri.EscapeDataStringhttp://msdn.microsoft.com/en-us/library/system.uri.escapedatastring.aspxto do my escaping I don't know what that routine is, but if it's not RFC 3986 compliant, it won't work. You might want to roll your own, it's a couple lines of code and a regex. -- personal: http://www.cameronkaiser.com/ -- Cameron Kaiser * Floodgap Systems * www.floodgap.com * ckai...@floodgap.com -- EH! STEVE! ---
[twitter-dev] Re: oAuth Echo problems
Does anyone have a sample code for PHP? I'm having some trouble creating the OAuth headers. On May 19, 10:22 am, uprise78 des...@gmail.com wrote: Works like a charm now. Thanks!
Re: [twitter-dev] Re: Incorrect signature when calling update url /1/statuses/update.xml
I will write my own if I have to. But before I do, I'd like to understand as many details as possible about the specifics of Twitter's RFC 3986 behavior. In my experience with RFC specs, they usually provide a lot of detail but they almost always leave some of those details to be interpreted by implementors and those interpretations are not always the same. No spec is perfect. On Thu, May 20, 2010 at 1:28 PM, Cameron Kaiser spec...@floodgap.comwrote: FYI - I am writing a .Net based library and so I currently use System.Uri.EscapeDataString http://msdn.microsoft.com/en-us/library/system.uri.escapedatastring.aspx to do my escaping I don't know what that routine is, but if it's not RFC 3986 compliant, it won't work. You might want to roll your own, it's a couple lines of code and a regex. -- personal: http://www.cameronkaiser.com/ -- Cameron Kaiser * Floodgap Systems * www.floodgap.com * ckai...@floodgap.com -- EH! STEVE! ---
[twitter-dev] Re: oAuth Echo Enabled Providers
This is now active on Twitgoo. You can see the documentation here: http://twitgoo.com/docs/Content/Developer/upload.htm On May 19, 9:05 am, Justin Hart onyxra...@gmail.com wrote: I am the lead dev on Twitgoo and I just built full echo support for 'upload' there. Its on the beta site right now, so if you want to test, please contact me for the info, otherwise it should be out by the end of the week. It will have full support of header, query string and multipart body parameters. On May 17, 2:47 pm, Rich rhyl...@gmail.com wrote: With the impending switch off of Basic Auth, should we keep a list of media providers and external services that have already made the switch to oAuth Echo. So far I've found and tested TwitPic - full oAuth Echo support TwitVid - oAuth Echo by sending as a URL parameter I know MobyPicture intend to have oAuth Echo enabled this month. Any others any one knows of?
[twitter-dev] Re: website and OAuth
i'm facing an equal scenario like the one above... i'm running a website where 2 to 3 users post status updates to that site which are posted then to twitteraccounts of the corresponding user. so basically i want to send updates to 2 or 3 twitter accounts via a php script. the users send their status updates via e-mails to the website and the script updates the website and posts to the twitter account of the user who has send in the status update. do i need to implement the whole OAuth process or can i use single tokens? thanks in advance! Claudio On May 11, 4:11 pm, glenn gillen gl...@rubypond.com wrote: Dan, I've taken a stab at answering your questions below: now from my understanding i need to change this over to start using OAuth is this correct? the system does it all back end so my bloggers dont write anything it auto does it for you, it posts to the one single twitter account. Yes you will need to switch over. now do i need to change to OAuth to get this to run when the date finally comes around, if so do i need to create an application? as it isnt really an application as such, this is the bit that confuses me a bit. You can switch over immediately, there's no need to wait until the cutoff date comes around. And yes you will need to create an application, it's just that this particular application will only. Details on some OAuth libraries (including PHP ones):http://apiwiki.twitter.com/OAuth-Examples Details on how to easily get a single token:http://dev.twitter.com/pages/oauth_single_token so i guess the question is do i need to change to oAuth and should i create an application if so would i need to create a callback URL as there wont be any callbacks as such would there as i would only be posting to my twitter feed. The single token approach can avoid the need for callbacks, so long as you don't need to tweet to other users accounts. -- Glenn Gillenhttp://glenngillen.com/
Re: [twitter-dev] Is OAuth working for *anyone* out there?
Just tried establishing a new connection to a different account with Twitterrific (which I believe uses xAuth) and it worked fine. So, there is presumably a bug in the iPad client I was testing. Unrelated. -damon On Thu, May 20, 2010 at 3:33 PM, Damon Clinkscales sca...@pobox.com wrote: Hey guys, Don't know if this is related, but I was testing a friend's iPad app this morning which uses xAuth. When setting up a new account in his app, the app authorizes in my Connections tab. However, whenever his app tries to use the tokens, we get an immediate HTTP 401. None of the calls with the tokens he has received are working for accessing. His account, which was auth'd (tokens retreived) over a month ago, still works ok with his app, but my new setup with the same client codebase is now failing. It seems like there might be something wrong with the OAuth tokens being issued, but that seems kinda crazy that there could be a problem that widespread. -damon
Re: [twitter-dev] Is OAuth working for *anyone* out there?
Hi Damon, We've heard some reports of iPads setting their dates/clocks incorrectly -- sometimes back to 1969. If the client application uses the date/time on the machine (rather than querying it from some other source), and the date/time isn't within 5 minutes or so of our clocks, it results in a failed request. One work around is for clients to adjust their concept of the current time by looking at the HTTP headers we send on a failed request (which includes our server clock), or to use an external service to fetch the time prior to making a request. Taylor Singletary Developer Advocate, Twitter http://twitter.com/episod On Thu, May 20, 2010 at 2:04 PM, Damon Clinkscales sca...@pobox.com wrote: Just tried establishing a new connection to a different account with Twitterrific (which I believe uses xAuth) and it worked fine. So, there is presumably a bug in the iPad client I was testing. Unrelated. -damon On Thu, May 20, 2010 at 3:33 PM, Damon Clinkscales sca...@pobox.com wrote: Hey guys, Don't know if this is related, but I was testing a friend's iPad app this morning which uses xAuth. When setting up a new account in his app, the app authorizes in my Connections tab. However, whenever his app tries to use the tokens, we get an immediate HTTP 401. None of the calls with the tokens he has received are working for accessing. His account, which was auth'd (tokens retreived) over a month ago, still works ok with his app, but my new setup with the same client codebase is now failing. It seems like there might be something wrong with the OAuth tokens being issued, but that seems kinda crazy that there could be a problem that widespread. -damon
[twitter-dev] Suddenly only getting search results from the past 24 hours...
Hi everyone, I'm relatively new to using APIs. I completed a data visualization project about a month ago and everything worked fine at that time. But now, when I run the app, I only get search results from the past day rather than the past seven days. I don't get any errors when this happens. Nothing has changed about my application, I haven't touched it for almost a month. What could have happened between that time? What might be causing this and how can I fix it? Btw, I'm using the Tweetr AS3 Library which uses HTTP GET and retrieves atom results. Thanks, Ed
Re: [twitter-dev] Is OAuth working for *anyone* out there?
On Thu, May 20, 2010 at 4:16 PM, Taylor Singletary taylorsinglet...@twitter.com wrote: Hi Damon, We've heard some reports of iPads setting their dates/clocks incorrectly -- sometimes back to 1969. If the client application uses the date/time on the machine (rather than querying it from some other source), and the date/time isn't within 5 minutes or so of our clocks, it results in a failed request. One work around is for clients to adjust their concept of the current time by looking at the HTTP headers we send on a failed request (which includes our server clock), or to use an external service to fetch the time prior to making a request. Taylor Singletary Developer Advocate, Twitter Thanks Taylor. -damon
Re: [twitter-dev] Is OAuth working for *anyone* out there?
Dossy, to echo my comment to Damon -- can you check the timestamps on your server that is issuing requests? If every call of yours is failing, it's possible that that is why. Taylor Singletary Developer Advocate, Twitter http://twitter.com/episod On Thu, May 20, 2010 at 12:29 PM, Dossy Shiobara do...@panoptic.com wrote: On 5/20/10 3:16 PM, Taylor Singletary wrote: While we have been having some performance issues that should give you occasional 401s, it shouldn't be as widespread as the experience you've been having. OK, you know, until *literally* 60 seconds ago, requests for http://twitter.com/oauth_clients/details/1574 were returning 502 fail whales. NOW, it just loaded. OK, who fixed it just now? What was broken? When we throw a 401, we typically provide an error message within the body of the response -- if you can share that it would be helpful. As I said in my email the other day: HTTP 401, Failed to validate oauth signature and token Has anything about your environment changed? Sadly, no. I wish it were that simple. Have you reset your consumer key or secret? No, and I just verified again that it still matches what is showing in the Twitter OAuth apps page. Does this happen for all access tokens or is there a specific access token that you use that is failing? Is it possible that access token's access was revoked? The error message provided on 401s will help shine some light on some of this. It's happening on the very first, and every single, /oauth/request_token API call. One recent change we made is that if you're trying to access resources that don't require authentication, but you are still providing OAuth credentials and those credentials are invalid, we no longer provide the data but instead properly inform you that your credentials aren't valid. Again, I'm not even getting as far as making a Twitter API call any more. The whole OAuth process is failing at the request_token endpoint. Which, if any, OAuth library do you use? Homegrown. Has been working for over a year, and has not been modified the entire time. -- Dossy Shiobara | do...@panoptic.com | http://dossy.org/ Panoptic Computer Network | http://panoptic.com/ He realized the fastest way to change is to laugh at your own folly -- then you can let go and quickly move on. (p. 70)
Re: [twitter-dev] Is OAuth working for *anyone* out there?
I'll send it to you privately, off-list. On 5/20/10 4:27 PM, Taylor Singletary wrote: Sorry you're having trouble, Dossy. Can you share the complete path you're using to fetch a request token (with host, domain, protocol, path, and any query parameters), your signature base string, and an authorization header if you're using header-based auth? -- Dossy Shiobara | do...@panoptic.com | http://dossy.org/ Panoptic Computer Network | http://panoptic.com/ He realized the fastest way to change is to laugh at your own folly -- then you can let go and quickly move on. (p. 70)
Re: [twitter-dev] Is OAuth working for *anyone* out there?
AHA! I just checked, somehow my system clock is off (slow) by ~3 hours. Somehow, NTP died and time sync stopped. I'm not sure how that happened, but I restarted ntpd everywhere, and OAuth is working again! Would it be a huge deal to ask that if the OAuth request is being refused due to the oauth_timestamp, that the 401 response body reflect this fact? Could have saved me 3+ days of head-scratching. On 5/20/10 5:16 PM, Taylor Singletary wrote: Hi Damon, We've heard some reports of iPads setting their dates/clocks incorrectly -- sometimes back to 1969. If the client application uses the date/time on the machine (rather than querying it from some other source), and the date/time isn't within 5 minutes or so of our clocks, it results in a failed request. One work around is for clients to adjust their concept of the current time by looking at the HTTP headers we send on a failed request (which includes our server clock), or to use an external service to fetch the time prior to making a request. -- Dossy Shiobara | do...@panoptic.com | http://dossy.org/ Panoptic Computer Network | http://panoptic.com/ He realized the fastest way to change is to laugh at your own folly -- then you can let go and quickly move on. (p. 70)
[twitter-dev] Re: oAuth Echo Enabled Providers
Look's like TwitPic's oAuth Echo has broken again, can anyone else confirm? On May 20, 9:49 pm, Justin Hart onyxra...@gmail.com wrote: This is now active on Twitgoo. You can see the documentation here:http://twitgoo.com/docs/Content/Developer/upload.htm On May 19, 9:05 am, Justin Hart onyxra...@gmail.com wrote: I am the lead dev on Twitgoo and I just built full echo support for 'upload' there. Its on the beta site right now, so if you want to test, please contact me for the info, otherwise it should be out by the end of the week. It will have full support of header, query string and multipart body parameters. On May 17, 2:47 pm, Rich rhyl...@gmail.com wrote: With the impending switch off of Basic Auth, should we keep a list of media providers and external services that have already made the switch to oAuth Echo. So far I've found and tested TwitPic - full oAuth Echo support TwitVid - oAuth Echo by sending as a URL parameter I know MobyPicture intend to have oAuth Echo enabled this month. Any others any one knows of?
[twitter-dev] Re: Is OAuth working for *anyone* out there?
I'm now starting to get near constant 401's to oAuth echo requests when it was working perfectly. It intermittently works, but litterally 1 in every 10 requests works On May 20, 10:38 pm, Dossy Shiobara do...@panoptic.com wrote: AHA! I just checked, somehow my system clock is off (slow) by ~3 hours. Somehow, NTP died and time sync stopped. I'm not sure how that happened, but I restarted ntpd everywhere, and OAuth is working again! Would it be a huge deal to ask that if the OAuth request is being refused due to the oauth_timestamp, that the 401 response body reflect this fact? Could have saved me 3+ days of head-scratching. On 5/20/10 5:16 PM, Taylor Singletary wrote: Hi Damon, We've heard some reports of iPads setting their dates/clocks incorrectly -- sometimes back to 1969. If the client application uses the date/time on the machine (rather than querying it from some other source), and the date/time isn't within 5 minutes or so of our clocks, it results in a failed request. One work around is for clients to adjust their concept of the current time by looking at the HTTP headers we send on a failed request (which includes our server clock), or to use an external service to fetch the time prior to making a request. -- Dossy Shiobara | do...@panoptic.com |http://dossy.org/ Panoptic Computer Network |http://panoptic.com/ He realized the fastest way to change is to laugh at your own folly -- then you can let go and quickly move on. (p. 70)
[twitter-dev] Re: oAuth Echo Enabled Providers
Scrap that, looks like oAuth echo is almost totally broken right now, only Twitgoo seems to be working, both MobyPicture and TwitPic constantly return a 401, and on the very odd occasion one does make it through Twitter itself returns a 500 status error (even though it actually posts the message) On May 20, 11:00 pm, Rich rhyl...@gmail.com wrote: Look's like TwitPic's oAuth Echo has broken again, can anyone else confirm? On May 20, 9:49 pm, Justin Hart onyxra...@gmail.com wrote: This is now active on Twitgoo. You can see the documentation here:http://twitgoo.com/docs/Content/Developer/upload.htm On May 19, 9:05 am, Justin Hart onyxra...@gmail.com wrote: I am the lead dev on Twitgoo and I just built full echo support for 'upload' there. Its on the beta site right now, so if you want to test, please contact me for the info, otherwise it should be out by the end of the week. It will have full support of header, query string and multipart body parameters. On May 17, 2:47 pm, Rich rhyl...@gmail.com wrote: With the impending switch off of Basic Auth, should we keep a list of media providers and external services that have already made the switch to oAuth Echo. So far I've found and tested TwitPic - full oAuth Echo support TwitVid - oAuth Echo by sending as a URL parameter I know MobyPicture intend to have oAuth Echo enabled this month. Any others any one knows of?
[twitter-dev] Re: oAuth Echo Enabled Providers
A bit more debugging and oAuth Echo only seems to be broken over SSL, change the realm, provider and signing request to http://api.twitter.com/1/account/verify_credentials.json instead of https://api.twitter.com/1/account/verify_credentials.json and it'll go through On May 20, 11:23 pm, Rich rhyl...@gmail.com wrote: Scrap that, looks like oAuth echo is almost totally broken right now, only Twitgoo seems to be working, both MobyPicture and TwitPic constantly return a 401, and on the very odd occasion one does make it through Twitter itself returns a 500 status error (even though it actually posts the message) On May 20, 11:00 pm, Rich rhyl...@gmail.com wrote: Look's like TwitPic's oAuth Echo has broken again, can anyone else confirm? On May 20, 9:49 pm, Justin Hart onyxra...@gmail.com wrote: This is now active on Twitgoo. You can see the documentation here:http://twitgoo.com/docs/Content/Developer/upload.htm On May 19, 9:05 am, Justin Hart onyxra...@gmail.com wrote: I am the lead dev on Twitgoo and I just built full echo support for 'upload' there. Its on the beta site right now, so if you want to test, please contact me for the info, otherwise it should be out by the end of the week. It will have full support of header, query string and multipart body parameters. On May 17, 2:47 pm, Rich rhyl...@gmail.com wrote: With the impending switch off of Basic Auth, should we keep a list of media providers and external services that have already made the switch to oAuth Echo. So far I've found and tested TwitPic - full oAuth Echo support TwitVid - oAuth Echo by sending as a URL parameter I know MobyPicture intend to have oAuth Echo enabled this month. Any others any one knows of?
[twitter-dev] Re: oAuth Echo Enabled Providers
Does anyone have an example of a PHP Library to interact with these libraries via Oauth Echo? I would be interested or to see some sample code. On May 20, 6:44 pm, Rich rhyl...@gmail.com wrote: A bit more debugging and oAuth Echo only seems to be broken over SSL, change the realm, provider and signing request tohttp://api.twitter.com/1/account/verify_credentials.jsoninstead ofhttps://api.twitter.com/1/account/verify_credentials.jsonand it'll go through On May 20, 11:23 pm, Rich rhyl...@gmail.com wrote: Scrap that, looks like oAuth echo is almost totally broken right now, only Twitgoo seems to be working, both MobyPicture and TwitPic constantly return a 401, and on the very odd occasion one does make it through Twitter itself returns a 500 status error (even though it actually posts the message) On May 20, 11:00 pm, Rich rhyl...@gmail.com wrote: Look's like TwitPic's oAuth Echo has broken again, can anyone else confirm? On May 20, 9:49 pm, Justin Hart onyxra...@gmail.com wrote: This is now active on Twitgoo. You can see the documentation here:http://twitgoo.com/docs/Content/Developer/upload.htm On May 19, 9:05 am, Justin Hart onyxra...@gmail.com wrote: I am the lead dev on Twitgoo and I just built full echo support for 'upload' there. Its on the beta site right now, so if you want to test, please contact me for the info, otherwise it should be out by the end of the week. It will have full support of header, query string and multipart body parameters. On May 17, 2:47 pm, Rich rhyl...@gmail.com wrote: With the impending switch off of Basic Auth, should we keep a list of media providers and external services that have already made the switch to oAuth Echo. So far I've found and tested TwitPic - full oAuth Echo support TwitVid - oAuth Echo by sending as a URL parameter I know MobyPicture intend to have oAuth Echo enabled this month. Any others any one knows of?
[twitter-dev] Fetching @mentions not longer working
Hello,
I used to have this code working, but suddenly I can't fetch
@mentions.
Here are some sample lines of code and the output I'm getting:
$twitter = new TwitterOAuth($TWITTER_CONSUMER_KEY,
$TWITTER_CONSUMER_SECRET, $access_key, $secret_key);
$feeds = $twitter-OAuthRequest(http://api.twitter.com/1/statuses/
mention.json, 'GET', array(count=25));
$feeds = json_decode($feeds);
Normally this would return me a JSON object with the authenticated
user @mentions. But now I get this:
{request:/1/statuses/mention.json?
count=25oauth_consumer_key=REMOVEDoauth_nonce=REMOVEDoauth_signature=REMOVEDoauth_signature_method=HMAC-
SHA1oauth_timestamp=1274394259oauth_token=oauth_version=1.0a,error:Not
found}
I removed my tokens and keys from the above output, but you can get an
idea with the copied text above.
Any idea what could be wrong?
Thanks!
[twitter-dev] Newbie question - please help.
Hello, I want to develop a web-based application that will search for the most favorited tweets for a given hashtag. For example, a user may type cerati in a textbox and the application will return the tweets that contain the hashtag #cerati and have been favorited more than x (3, 4, 5) times. My questions are: - Is this possible? - If so, what method should I use? It appears to me that if I use the search API I don't get a favourite_count among the results. And I can't specify something like minimum amount of times tweet was favorited as a parameter. Or maybe I can use the search API to get the tweets that contain the hashtag and then iterate thorugh the list to obtain the number of times each tweet was favorited? Another alternative: instead of doing this with the public timeline (ideal solution) do it for all tweets by the users a person is following. Can this be done? Thanks for your help. Gustavo
[twitter-dev] Re: Invalid / used nonce but only for certain user names?
Hey, We are getting this error, but Twitter is also sending back a valid response. To clarify, if we post an update, the update appears in the timeline but twitter returns a 401 error code (with the nonce message). Same applies to friends timeline sometimes too. Cheers David http://m.tweete.net On Apr 30, 12:46 am, Taylor Singletary taylorsinglet...@twitter.com wrote: We have a weird error condition in the OAuth implementation right now that throws invalid nonce errors when it's not necessarily the issue. We're still tracking what exactly causes this down, but believe that it's not applicable to the OAuth implementation rewrite we'll soon be rolling out. In the meantime, when you get this error and you're fairly certain you've never used the nonce before, if you can provide a signature base string and authorization header corresponding to the failed request it will give us better visibility into possible causation. Thanks! Taylor Singletary Developer Advocate, Twitterhttp://twitter.com/episod On Wed, Apr 28, 2010 at 7:15 PM, Dewald Pretorius dpr...@gmail.com wrote: Cory, I have had similar issues. When you get that 401 error, you need to back off for a second or two, recalculate the nonce, and then resubmit the request. On Apr 28, 10:52 pm, Cory cory.imdi...@gmail.com wrote: Anyone have any ideas about this? I'm really not sure where to go or what to check from here, and I need to get this taken care of. Any information would be appreciated!
Re: [twitter-dev] Fetching @mentions not longer working
Am 21.05.2010 um 00:34.43 schrieb Guillermo: $feeds = $twitter-OAuthRequest(http://api.twitter.com/1/statuses/ mention.json, 'GET', array(count=25)); Please note its 'mentions', not 'mention' :) http://dev.twitter.com/doc/get/statuses/mentions Gruß, Felix Kunsmann - fe...@kunsmann.eu -- Blog: http://felix-kunsmann.de/ Galerie: http://galerie.kunsmann.eu/
Re: [twitter-dev] Fetching @mentions not longer working
Hi Guillermo,
In your code here, it shows you requesting from
api.twitter.com/1/statuses/mention.json when you should be accessing the
plural form api.twitter.com/1/statuses/mentions.json -- which is why you're
getting a Not Found error.
But to be fair, we have been having some issues this week. They will be
ironed out soon.
Taylor
On Thu, May 20, 2010 at 3:34 PM, Guillermo pulsor...@gmail.com wrote:
Hello,
I used to have this code working, but suddenly I can't fetch
@mentions.
Here are some sample lines of code and the output I'm getting:
$twitter = new TwitterOAuth($TWITTER_CONSUMER_KEY,
$TWITTER_CONSUMER_SECRET, $access_key, $secret_key);
$feeds = $twitter-OAuthRequest(http://api.twitter.com/1/statuses/
mention.json, 'GET', array(count=25));
$feeds = json_decode($feeds);
Normally this would return me a JSON object with the authenticated
user @mentions. But now I get this:
{request:/1/statuses/mention.json?
count=25oauth_consumer_key=REMOVEDoauth_nonce=REMOVEDoauth_signature=REMOVEDoauth_signature_method=HMAC-
SHA1oauth_timestamp=1274394259oauth_token=oauth_version=1.0a,error:Not
found}
I removed my tokens and keys from the above output, but you can get an
idea with the copied text above.
Any idea what could be wrong?
Thanks!
Re: [twitter-dev] Re: Incorrect signature when calling update url /1/statuses/update.xml
I will write my own if I have to. But before I do, I'd like to understand as many details as possible about the specifics of Twitter's RFC 3986 behavior. This is the regex I'm using, which is known to work: $x =~ s/([^-0-9a-zA-Z._~])/%.uc(unpack(H2,$1))/eg; In short, letters, numbers, and the set of -._~ are NOT URL encoded. Everything else is. Note this routine is not 100% UTF-8 safe as written; I have other code that handles that, so you may need to do that as your library warrants. -- personal: http://www.cameronkaiser.com/ -- Cameron Kaiser * Floodgap Systems * www.floodgap.com * ckai...@floodgap.com -- People are weird. -- Law Order SVU ---
[twitter-dev] Re: How to use PHP Twitter Search API with the operators OR SINCE HASHTAG etc
Somebody may help me? Thanks. On 18 maio, 22:40, giustin tgiu...@gmail.com wrote: Hi, people! I'm here again to question a more thing: We suppose the experiences and links explain above. If I wanna use PHP Twitter Search by Ryan Faerman (http://greenservr.com/projects/ twittersearch/TwitterSearch.phps) to search using two tags with the operator OR: URL API/brasil+OR+copa. Its will returns tweets thats contain brasil or copa. But, how can I know what the tag that found the tweet? We suppose 60 tags: URL API/brasil+OR+copa+OR+tag3+OR+tag4... Now, if I need to save in a database the tweets found and the tags that were used to find this tweet, how can I do? What is your suggestion? The API does can result something like this to me? I thought about a parser (to iterator) the string twitter, and compare until find them, but it is redundancy of process, cause you use the API to found the tweets, and after you need to find the tags in the tweet already found. Somebody save me? On 17 maio, 00:26, giustin tgiu...@gmail.com wrote: Hi, myself and dears mates! :) It is very simple, but I'm not saw before. So, a example with the operator OR is: http://www.portabilis.com.br/tcc/search_PHP_API/index.php?twitterq=br... Thanks. On 17 maio, 00:04, giustin tgiu...@gmail.com wrote: Hi, Using the PHP Twitter Search by Ryan Faerman, I'm trying to create a mashup to my final university project. The class is that:http://greenservr.com/projects/twittersearch/TwitterSearch.phps What I would like to know? In the Search API Twitter, you can use many methods, and I dont know if this class include all them. Examples: 1. searching tweets with tags brasil or copa since 2010-05-15.http://search.twitter.com/search?q=brasil+OR+copa+since%3A2010-05-15 2. just using the operator OR, to the tags twitter or you:http://search.twitter.com/search?q=twitter+OR+you 3. With the #hashtag:http://search.twitter.com/search?q=%23twitter FONT:http://search.twitter.com/operators Looking at the TwitterSearch.phps, how can I create a script to bring the results to me using OR ou SINCE operators? Look up my example: http://www.portabilis.com.br/tcc/search_PHP_API/index.php?twitterq=br... The link above bring me tweets that exists brasil AND copa tags. I dont wanna AND but OR operator. Someone could help me with this? Regards,
Re: [twitter-dev] Re: Incorrect signature when calling update url /1/statuses/update.xml
Thanks a lot Cameron! I was just sitting down to write my lib, planning on doing as you suggest below. On Thu, May 20, 2010 at 5:06 PM, Cameron Kaiser spec...@floodgap.comwrote: I will write my own if I have to. But before I do, I'd like to understand as many details as possible about the specifics of Twitter's RFC 3986 behavior. This is the regex I'm using, which is known to work: $x =~ s/([^-0-9a-zA-Z._~])/%.uc(unpack(H2,$1))/eg; In short, letters, numbers, and the set of -._~ are NOT URL encoded. Everything else is. Note this routine is not 100% UTF-8 safe as written; I have other code that handles that, so you may need to do that as your library warrants. -- personal: http://www.cameronkaiser.com/ -- Cameron Kaiser * Floodgap Systems * www.floodgap.com * ckai...@floodgap.com -- People are weird. -- Law Order SVU ---
[twitter-dev] Re: Is OAuth working for *anyone* out there?
Just a quick follow-up to the comment from Damon above, because it was my app he was testing that broke. It was a client bug. I've confirmed that everything's working great with xAuth after I fixed it. Thanks Taylor for the tip about dates/clocks, too. -- Manton Reece http://www.manton.org/
[twitter-dev] Re: oAuth Echo Enabled Providers
Hi Rich- Nice catch! During one of our deployments today, we mistakingly switched the OAuth Echo API to use Twitter's Non-SSL Endpoint. I just pushed a fix for it- can you let me know if everything works correctly for you again? (Coincidently, the deployment that turned off SSL for the API was turning SSL on for another part of the website. :P) Thanks! Steve Corona Twitpic On May 20, 6:44 pm, Rich rhyl...@gmail.com wrote: A bit more debugging and oAuth Echo only seems to be broken over SSL, change the realm, provider and signing request tohttp://api.twitter.com/1/account/verify_credentials.jsoninstead ofhttps://api.twitter.com/1/account/verify_credentials.jsonand it'll go through On May 20, 11:23 pm, Rich rhyl...@gmail.com wrote: Scrap that, looks like oAuth echo is almost totally broken right now, only Twitgoo seems to be working, both MobyPicture and TwitPic constantly return a 401, and on the very odd occasion one does make it through Twitter itself returns a 500 status error (even though it actually posts the message) On May 20, 11:00 pm, Rich rhyl...@gmail.com wrote: Look's like TwitPic's oAuth Echo has broken again, can anyone else confirm? On May 20, 9:49 pm, Justin Hart onyxra...@gmail.com wrote: This is now active on Twitgoo. You can see the documentation here:http://twitgoo.com/docs/Content/Developer/upload.htm On May 19, 9:05 am, Justin Hart onyxra...@gmail.com wrote: I am the lead dev on Twitgoo and I just built full echo support for 'upload' there. Its on the beta site right now, so if you want to test, please contact me for the info, otherwise it should be out by the end of the week. It will have full support of header, query string and multipart body parameters. On May 17, 2:47 pm, Rich rhyl...@gmail.com wrote: With the impending switch off of Basic Auth, should we keep a list of media providers and external services that have already made the switch to oAuth Echo. So far I've found and tested TwitPic - full oAuth Echo support TwitVid - oAuth Echo by sending as a URL parameter I know MobyPicture intend to have oAuth Echo enabled this month. Any others any one knows of?
[twitter-dev] Re: oAuth Echo Enabled Providers
It's working great now. Many thanks Steve On May 21, 4:22 am, Steve C st...@twitpic.com wrote: Hi Rich- Nice catch! During one of our deployments today, we mistakingly switched the OAuth Echo API to use Twitter's Non-SSL Endpoint. I just pushed a fix for it- can you let me know if everything works correctly for you again? (Coincidently, the deployment that turned off SSL for the API was turning SSL on for another part of the website. :P) Thanks! Steve Corona Twitpic On May 20, 6:44 pm, Rich rhyl...@gmail.com wrote: A bit more debugging and oAuth Echo only seems to be broken over SSL, change the realm, provider and signing request tohttp://api.twitter.com/1/account/verify_credentials.jsoninsteadofhttps://api.twitter.com/1/account/verify_credentials.jsonandit'll go through On May 20, 11:23 pm, Rich rhyl...@gmail.com wrote: Scrap that, looks like oAuth echo is almost totally broken right now, only Twitgoo seems to be working, both MobyPicture and TwitPic constantly return a 401, and on the very odd occasion one does make it through Twitter itself returns a 500 status error (even though it actually posts the message) On May 20, 11:00 pm, Rich rhyl...@gmail.com wrote: Look's like TwitPic's oAuth Echo has broken again, can anyone else confirm? On May 20, 9:49 pm, Justin Hart onyxra...@gmail.com wrote: This is now active on Twitgoo. You can see the documentation here:http://twitgoo.com/docs/Content/Developer/upload.htm On May 19, 9:05 am, Justin Hart onyxra...@gmail.com wrote: I am the lead dev on Twitgoo and I just built full echo support for 'upload' there. Its on the beta site right now, so if you want to test, please contact me for the info, otherwise it should be out by the end of the week. It will have full support of header, query string and multipart body parameters. On May 17, 2:47 pm, Rich rhyl...@gmail.com wrote: With the impending switch off of Basic Auth, should we keep a list of media providers and external services that have already made the switch to oAuth Echo. So far I've found and tested TwitPic - full oAuth Echo support TwitVid - oAuth Echo by sending as a URL parameter I know MobyPicture intend to have oAuth Echo enabled this month. Any others any one knows of?
[twitter-dev] Re: statuses/update: Expect: 100-Continue header rejected
On May 20, 10:38 pm, Cameron Kaiser spec...@floodgap.com wrote: I've been playing with oacurlhttps://code.google.com/apis/buzz/v1/oacurl.html and tried to use it to send a tweet. oacurl sends Expect: 100-Continue but Twitter rejects this with we only allow the 100-continue expectation. Is this fixable, or avoidable in the meantime? (I know about twurl, but oacurl seems generic - can I use twurl to make oauth calls to MySpace?) Just change the header to simply send a blank Expect:. With regular cURL a simple -H Expect: will work. Thanks for your reply. Although oacurl supports -H like curl, using -H Expect: adds a second Expect: header to the request, the Twitter server still fails because of Expect: 100-Continue. I'll raise the oacurl bug with one of the authors, but that still leaves a bug in Twitter's handling of Expect:. /c/download: echo status=Testing+oacurl | java -cp oacurl-1.0.0.jar com.google.oacurl.Fetch -X POST -H Expect: -v http://api.twitter.com/1/statuses/update.json POST /1/statuses/update.json HTTP/1.1 Content-Type: application/atom+xml Expect: Authorization: OAuth oauth_token=34507306-fJYSoMdju3Vv9SecfdyCUbYu5JdlIPLyaVN3xElNw, oauth_consumer_key=FFUZwLopTkug9Dlj1KamA, oauth_signature_method=HMAC-SHA1, oauth_timestamp=1274396737, oauth_nonce=571291495191528, oauth_version=1.0, oauth_signature=CqiI%2FY%2Br96PGVPkCSClqnkmfHAo%3D Transfer-Encoding: chunked Host: api.twitter.com Connection: Keep-Alive User-Agent: Apache-HttpClient/4.0 (java 1.5) Expect: 100-Continue status=Testing+oacurl[\n] -- Richard
[twitter-dev] Re: oAuth Echo Enabled Providers
Has anyone gotten OAuth Echo to work with Twitpic or Twitgoo? So far, my attempts have been a complete failure. No matter what I try, I get a 401 back with the error message Authentication needed. On May 20, 6:29 pm, Greg gregory.av...@gmail.com wrote: Does anyone have an example of a PHP Library to interact with these libraries via Oauth Echo? I would be interested or to see some sample code. On May 20, 6:44 pm, Rich rhyl...@gmail.com wrote: A bit more debugging and oAuth Echo only seems to be broken over SSL, change the realm, provider and signing request tohttp://api.twitter.com/1/account/verify_credentials.jsoninsteadofhttps://api.twitter.com/1/account/verify_credentials.jsonandit'll go through On May 20, 11:23 pm, Rich rhyl...@gmail.com wrote: Scrap that, looks like oAuth echo is almost totally broken right now, only Twitgoo seems to be working, both MobyPicture and TwitPic constantly return a 401, and on the very odd occasion one does make it through Twitter itself returns a 500 status error (even though it actually posts the message) On May 20, 11:00 pm, Rich rhyl...@gmail.com wrote: Look's like TwitPic's oAuth Echo has broken again, can anyone else confirm? On May 20, 9:49 pm, Justin Hart onyxra...@gmail.com wrote: This is now active on Twitgoo. You can see the documentation here:http://twitgoo.com/docs/Content/Developer/upload.htm On May 19, 9:05 am, Justin Hart onyxra...@gmail.com wrote: I am the lead dev on Twitgoo and I just built full echo support for 'upload' there. Its on the beta site right now, so if you want to test, please contact me for the info, otherwise it should be out by the end of the week. It will have full support of header, query string and multipart body parameters. On May 17, 2:47 pm, Rich rhyl...@gmail.com wrote: With the impending switch off of Basic Auth, should we keep a list of media providers and external services that have already made the switch to oAuth Echo. So far I've found and tested TwitPic - full oAuth Echo support TwitVid - oAuth Echo by sending as a URL parameter I know MobyPicture intend to have oAuth Echo enabled this month. Any others any one knows of?
[twitter-dev] Favorite create API which is the right one?
As per apiwiki.twitter.com create favorite is http://api.twitter.com/1/favorites/create/*id*.*format* dev.twitter.com says its http://api.twitter.com/*version*/favorites/:id/create.*format *So which is the right one? -- Jebu Ittiachen jebu.ittiac...@gmail.com
[twitter-dev] Re: oAuth Echo Enabled Providers
Yeah they work fine, remember you don't oAuth sign the ACTUAL request to Twitpic or Twitgoo, you make a fake called to Twitter's verify_credentials page, take that header and add it to the one your send to Twitpic with a different name On May 21, 1:32 am, gotosleep gotosl...@gmail.com wrote: Has anyone gotten OAuth Echo to work with Twitpic or Twitgoo? So far, my attempts have been a complete failure. No matter what I try, I get a 401 back with the error message Authentication needed. On May 20, 6:29 pm, Greg gregory.av...@gmail.com wrote: Does anyone have an example of a PHP Library to interact with these libraries via Oauth Echo? I would be interested or to see some sample code. On May 20, 6:44 pm, Rich rhyl...@gmail.com wrote: A bit more debugging and oAuth Echo only seems to be broken over SSL, change the realm, provider and signing request tohttp://api.twitter.com/1/account/verify_credentials.jsoninsteadofhttp...go through On May 20, 11:23 pm, Rich rhyl...@gmail.com wrote: Scrap that, looks like oAuth echo is almost totally broken right now, only Twitgoo seems to be working, both MobyPicture and TwitPic constantly return a 401, and on the very odd occasion one does make it through Twitter itself returns a 500 status error (even though it actually posts the message) On May 20, 11:00 pm, Rich rhyl...@gmail.com wrote: Look's like TwitPic's oAuth Echo has broken again, can anyone else confirm? On May 20, 9:49 pm, Justin Hart onyxra...@gmail.com wrote: This is now active on Twitgoo. You can see the documentation here:http://twitgoo.com/docs/Content/Developer/upload.htm On May 19, 9:05 am, Justin Hart onyxra...@gmail.com wrote: I am the lead dev on Twitgoo and I just built full echo support for 'upload' there. Its on the beta site right now, so if you want to test, please contact me for the info, otherwise it should be out by the end of the week. It will have full support of header, query string and multipart body parameters. On May 17, 2:47 pm, Rich rhyl...@gmail.com wrote: With the impending switch off of Basic Auth, should we keep a list of media providers and external services that have already made the switch to oAuth Echo. So far I've found and tested TwitPic - full oAuth Echo support TwitVid - oAuth Echo by sending as a URL parameter I know MobyPicture intend to have oAuth Echo enabled this month. Any others any one knows of?
Re: [twitter-dev] Re: Is OAuth working for *anyone* out there?
I've been keeping track of the major oAuth issues that developers report to me. I've also hit these a few times myself. 1. The date/time on your machine must be accurate. Make sure you’ve performed a recent sync with a known time source. 2. If you’re trying to call a Twitter API method that will update data, the oAuth setup must be Read/Write on Twitter.com/oAuth. 3. Recheck all of your querystring variables for proper encoding. The method that you use for encoding querystring variables may not be oAuth compliant.
[twitter-dev] Re: oAuth Echo Enabled Providers
This are the providers I currently user that don't seem to have switched to oAuth Echo yet - yFrog - Raffi mentioned they have been working with them, but I don't see the end point yet - TweetPhoto - they have an implementation where you send your consumer secret key but I'm not going to do that! - TwitrPix - img.ly These I know work - TwitPic - Twitgoo - MobyPicture This one claims to have oAuth Echo support but just always responds that you haven't defined a username and/or password - Pikchur Any others anyone knows about? On May 21, 1:32 am, gotosleep gotosl...@gmail.com wrote: Has anyone gotten OAuth Echo to work with Twitpic or Twitgoo? So far, my attempts have been a complete failure. No matter what I try, I get a 401 back with the error message Authentication needed. On May 20, 6:29 pm, Greg gregory.av...@gmail.com wrote: Does anyone have an example of a PHP Library to interact with these libraries via Oauth Echo? I would be interested or to see some sample code. On May 20, 6:44 pm, Rich rhyl...@gmail.com wrote: A bit more debugging and oAuth Echo only seems to be broken over SSL, change the realm, provider and signing request tohttp://api.twitter.com/1/account/verify_credentials.jsoninsteadofhttp...go through On May 20, 11:23 pm, Rich rhyl...@gmail.com wrote: Scrap that, looks like oAuth echo is almost totally broken right now, only Twitgoo seems to be working, both MobyPicture and TwitPic constantly return a 401, and on the very odd occasion one does make it through Twitter itself returns a 500 status error (even though it actually posts the message) On May 20, 11:00 pm, Rich rhyl...@gmail.com wrote: Look's like TwitPic's oAuth Echo has broken again, can anyone else confirm? On May 20, 9:49 pm, Justin Hart onyxra...@gmail.com wrote: This is now active on Twitgoo. You can see the documentation here:http://twitgoo.com/docs/Content/Developer/upload.htm On May 19, 9:05 am, Justin Hart onyxra...@gmail.com wrote: I am the lead dev on Twitgoo and I just built full echo support for 'upload' there. Its on the beta site right now, so if you want to test, please contact me for the info, otherwise it should be out by the end of the week. It will have full support of header, query string and multipart body parameters. On May 17, 2:47 pm, Rich rhyl...@gmail.com wrote: With the impending switch off of Basic Auth, should we keep a list of media providers and external services that have already made the switch to oAuth Echo. So far I've found and tested TwitPic - full oAuth Echo support TwitVid - oAuth Echo by sending as a URL parameter I know MobyPicture intend to have oAuth Echo enabled this month. Any others any one knows of?
