Re: [twitter-dev] Re: oAuth reporting a status update error when none exists
What does $connection-http_code return after calling $connection-post when
you get the duplicate error message?
Abraham
-
Abraham Williams | Hacker Advocate | abrah.am
@abraham https://twitter.com/abraham | github.com/abraham | blog.abrah.am
This email is: [ ] shareable [x] ask first [ ] private.
On Mon, Nov 29, 2010 at 23:58, EastSideDev eastside...@gmail.com wrote:
I double-checked my code, and I'm only calling statuses/update once:
$connection = new TwitterOAuth($ctck, $ctcks, $ot,$ots);
$opResult = $connection-post('statuses/update',
array('status' = $statusUpdate), TRUE);
if (!$opResult['id']) {
$msgText .= $opResult['error']. ;
}
This is code that was working fine, until recently (no changes).
On Nov 29, 10:00 pm, Abraham Williams 4bra...@gmail.com wrote:
It sound to me like your code might be making the same API request twice.
This would result in the status getting posted and the error message you
end
up with.
If you are commonly creating statuses with the same text it might just
seem
like a new status is getting posted when they are not.
Abraham
-
Abraham Williams | Hacker Advocate | abrah.am
@abraham https://twitter.com/abraham | github.com/abraham |
blog.abrah.am
This email is: [ ] shareable [x] ask first [ ] private.
On Mon, Nov 29, 2010 at 20:18, EastSideDev eastside...@gmail.com
wrote:
I have an application that uses oAuth to post a tweet on behalf of a
user. I noticed today that when I do a status update, I'm getting a
Status is a duplicate error message, when in fact the status posted
correctly.
I have not changed my code, and I am using the Twitter oAuth library
(same code been working fine since June). Are we experiencing some API
issues?
--
Twitter developer documentation and resources:
http://dev.twitter.com/doc
API updates via Twitter:http://twitter.com/twitterapi
Issues/Enhancements Tracker:
http://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
http://groups.google.com/group/twitter-development-talk
--
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker:
http://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
http://groups.google.com/group/twitter-development-talk
--
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
http://groups.google.com/group/twitter-development-talk
[twitter-dev] Re: Where can I find the updated rate limit after OAuth?
This is awesome... Thank you.. Will start playing with your suggestion. Best, Randolph On Nov 30, 2:59 am, Taylor Singletary taylorsinglet...@twitter.com wrote: statuses/followers and statuses/friends don't require authentication and are likely subject to this condition. When calling these resources, are you explicitly providing the user_id or screen_name? These methods are some of the oldest offered in the API and aren't really the best choices for consuming data of that nature. You would be better positioned to use friends/ids and followers/ids in conjunction with users/lookup Taylor On Mon, Nov 29, 2010 at 10:54 AM, m36tb6ll raeste...@gmail.com wrote: Thanks for the reply, Taylor... Are the API requests statuses/followers and statuses/friends included in the public-only resources that you are referring to? Or, I'm I not making any sense? :) Randolph On Nov 30, 2:19 am, Taylor Singletary taylorsinglet...@twitter.com wrote: There are some API methods that don't have the concept of an unauthenticated user -- these public-only resources will not consider OAuth credentials when calculating the rate limit. We are looking to make the application of rate limiting across resources, regardless of whether the resource expects auth or not, consistent in the future. Taylor On Mon, Nov 29, 2010 at 10:05 AM, Randolph Estebat raeste...@gmail.com wrote: Thanks for the reply, Igor... Yes it should be. The problem is that the headers are giving me the limit 150 rather than the expected 350 after OAuth. Any ideas why this is the case? Thanks again. On Mon, Nov 29, 2010 at 8:17 PM, Igor Kharin igorkha...@gmail.com wrote: All rate limited methods responses include X-Ratelimit-Remaining and X-Ratelimit-Limit HTTP-headers, use them or http://dev.twitter.com/doc/get/account/rate_limit_status On Fri, Nov 26, 2010 at 1:55 PM, m36tb6ll raeste...@gmail.com wrote: Hi! I am a newbie in the field and am working on my first twitter web app. I have created a variable loop timer using rate_limit_status which works well in maximizing the usage of the twitter API without going over the hourly limits. Now that I have incorporated OAuth, I was expecting to see the limit increase from 150 (unauthenticated requests) to 350 (authenticated requests). But, I am still seeing the 150 limit both in the response headers and Firebug when calling rate_limit_status API after OAuth. Is there something I'm missing here? Your help would be greatly appreciated. Thanks in advance... -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter:http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter:http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Randolph Estebat -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter:http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources:http://dev.twitter.com/doc API updates via Twitter:http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] collecting tweet message ids
Hi Matt, thanks for clearing up my questions! -- Kind Regards, Rajinder Yadav On 10-11-29 05:09 PM, Matt Harris wrote: Hi Rajinder, We would really like to offer access to the historical timeline but our infrastructure doesn't allow access to anymore than 3200 right now. The Tweets are safe and have not been deleted or lost, they are just not available. We also don't have a timeline for access to historical tweets right now. In answer to your second question, when there are no more statuses available we'll return an HTTP 200 with an empty timeline. For example: JSON: [] XML: ?xml version=1.0 encoding=UTF-8? statuses type=array /statuses Best, @themattharris Developer Advocate, Twitter http://twitter.com/themattharris On Mon, Nov 29, 2010 at 10:42 AM, Rajinder Yadav devguy.ca http://devguy.ca@gmail.com http://gmail.com wrote: On Mon, Nov 29, 2010 at 12:27 PM, Matt Harris thematthar...@twitter.com mailto:thematthar...@twitter.com wrote: Hi Rajinder. The user_timeline returns upto 200 statuses per page starting with the most recent. To retrieve a complete page of 200 you will want to make a request similar to: http://api.twitter.com/1/statuses/user_timeline.json?count=200\include_rts=1 http://api.twitter.com/1/statuses/user_timeline.json?count=200\include_rts=1 This request will return upto the most recent 200 statuses. To retrieve the next 200 you would make this request: http://api.twitter.com/1/statuses/user_timeline.json?count=200\include_rts=1\page=2 http://api.twitter.com/1/statuses/user_timeline.json?count=200\include_rts=1\page=2 When requesting this many statuses at once you may get a 503 error response from us. If this happens wait a few seconds and try the request again. Hope that helps, @themattharris Developer Advocate, Twitter http://twitter.com/themattharris Hi Matt, thanks, that is a better solution than what I have been using. Questions, am I limited up to only 3200 statuses? is it possible to go beyond this limit and get the entire statues for a user? When there are no more status request (empty set), what http error code can I expect. Likewise if 3200 status is a hard limit what http error will I get when this limit is hit? Finally if I have exceeded my rate limit what is the http code returned? Kind Regards, Rajinder Yadav -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] Re: Best scalable method to process mentions
I think I could not make myself clear! My app already processes new tweets in a scheduled manner, and stores the results in a database accordingly (using this API method: http://dev.twitter.com/doc/get/statuses/mentions). I don't get why would I use stream API and how it would help? On Nov 30, 4:04 am, fbparis fbou...@gmail.com wrote: I guess you should use the stream api to get mentions in real time. No need to process it directly, you could code a simple client connected to the stream api which record new mention in database, then launch your script time to time and get the mentions via the database rather than via the twitter api. On Nov 30, 1:25 am, Serdar ser...@guzelanket.com wrote: Hi I have just launched my first twitter application. Basically: -People send a tweet that mentions @appName (authorizing not needed) -App checks for new @appName mentions *from time to time*, and process them. There is a max mentions limit (200) that can be retrieved at a time via API. I know I'm not hitting this limit soon with the app but I want to code a scalable method fo get mentions. Unfortunaltely we do not have the option to get mentions in the 'oldest first' order. This causes a little tricky code for getting mentions in chunks and not missing older tweets. (Suppose you had 200+ mentions since last check). For testing I limit, 'max mentions to get at a time' to 10, in my code and it seems to be working. I won't go into more details... -I would like to know if any of you have coded something similar? -Would love to see an alternative, as I'm not happy with my code! -Is there an API method I could use for this purpose, which would make things easier? Thanks, Serdar. -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] accesstoken object
i can't english i use google Translate I'm developing a web application using Twitter4j my page show my twitter mention always consumerKey and consumerSecret using the oauth was confirm on my twitter i don't want to confirm everytime AccessToken accessToken = new AccessToken (209367381- tozr8sPBL7DgEmjBEHEcdVIkh8b5wIm37MWGWYCI, laBCexn91AePaXaiOrmmVPAxYd5BMxl1J6MGoLUaN4); Why, when so accessToken does not create objects properly? what cat do dev.twitter.com generated by the Access Token and Access Token Secret By twitter every time I log on I have to get accesstoken? -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] Re: randomly 401 error
Hello, I follow the lexicographical order but still get incorrect signature. http://9.share.photo.xuite.net/u9011022/19d31e2/4424859/171241799_x.jpg Since the frequency is randomly, the algorithm should be ok when success. On 11月30日, 上午2時39分, themattharris thematthar...@twitter.com wrote: Hi Alvin, The error in that response tells me your signature is incorrect. Double check you are generating your signature using the algorithm described here: http://dev.twitter.com/auth#signing-requests In particular I notice the parameters in your GET request are not in lexicographical order, and so I wonder if they may not be in order in your signature base string. Best, Matt On Nov 24, 10:10 pm, Alvin Wang alvin0...@gmail.com wrote: hello, Matt After removing the symbol and parameter realm, the frequency of 401 is lower. But it becomes the problem as I attach below http://9.share.photo.xuite.net/u9011022/19d319b/4424859/170775808_x.jpg On 11月25日, 上午2時32分, Matt Harris thematthar...@twitter.com wrote: Hey Alvin, Your URL looks badly formed as it includes .../home_timeline.json?count=5 I would expect to see .../home_timeline.json?count=5... (so no after the ?). You also have realm in your query string when it isn't needed. Realm is optional and when used, is only used in the Authorization header. When using OAuth in the query string you shouldn't pass realm. Your parameters should also be in lexicographical order. In your case I would have expected your URL to look like this: http://api.twitter.com/1/statuses/home_timeline.json?count=5oauth_co... page=1 You can read more about signing requests on our developer resources site: http://dev.twitter.com/pages/auth#signing-requests Best @themattharris Developer Advocate, Twitterhttp://twitter.com/themattharris 2010/11/23 Alvin Wang alvin0...@gmail.com hello Matt, here is the image when 401 occurs. http://dl.dropbox.com/u/162763/1.png On 11月23日, 下午2時17分, Matt Harris thematthar...@twitter.com wrote: Hey Alvin, So the community and developers can help you we'll need to know a little bit more about the error you are receiving. Things like the API request you are making, the request basestring, and the full response you get back are good things to include. Be careful to not include any passwords or OAuth secrets in anything you share. Best, @themattharris Developer Advocate, Twitterhttp://twitter.com/themattharris 2010/11/22 Alvin Wang alvin0...@gmail.com Are there any other solutions? Retry will still got 401 randomly. Just wondering is there any twitter tech person can help? On 11月23日, 上午3時28分, Nick Bradbury nick.bradb...@gmail.com wrote: I also ran into this problem, even though I knew the signature was fine. This post from a Twitter Developer Advocate indicates that a401may be due to Twitter being stressed: http://www.devcomments.com/re-intermittent-401-and-502-during-oauth-p... In my case, ignoring the401and resending the request a little later solved the problem the majority of the time. On Nov 22, 2:43 am, Alvin Wang alvin0...@gmail.com wrote: Hi, I am currently developing an application using twitter api. However, i will ramdomly receive401error (invalid signature). Sometime it's working fine but sometime are not. Can you please help us to resolve this problem? BR, Alvin- 隱藏被引用文字 - - 顯示被引用文字 - -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter:http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources:http://dev.twitter.com/doc API updates via Twitter:http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] Totally Stuck - Getting Incorrect signature error trying to update status using OAuth
Hi,
I'm trying to add (what I thought would be) a simple feature to a game
I developed - allow the users to post their scores to twitter. Since
my app is a game for the webOS platform, I felt xauth was the best way
to implement this. I already got xauth approval from Twitter. I also
have been able to request access tokens without any trouble.
However, when it comes down to using the oauth token and oauth secret,
I am totally 100% stuck.
I've spent a few days on this, and I've tried changing small things,
changing it back, it's driving me crazy, and no matter what I do I
always get this response:
failed to post to twitter: {request:\/1\/statuses\/
update.json,error:Incorrect signature}
Here is my code for constructing the and signing base string:
var updateUrl = http://api.twitter.com/1/statuses/update.json;;
var timestamp = Math.floor( (new Date(dt.toUTCString() )).getTime()/
1000);
var update_data=
'oauth_consumer_key=' +
encodeURIComponent(constants.consumerKey) +
'oauth_nonce=' + encodeURIComponent(nonce) +
'oauth_signature_method=HMAC-SHA1' +
'oauth_timestamp=' + timestamp +
'oauth_token='+encodeURIComponent(o_auth_token) +
'oauth_version=1.0' +
'status='+encodeURIComponent(wow);
var base_string = POST + encodeURIComponent(updateUrl)
+ + encodeURIComponent(update_data);
var oauth_signature =
b64_hmac_sha1(constants.consumerSecret++o_auth_secret,
base_string);
o_auth_token and o_auth_secret are set prior to this block of code by
parsing the response from the access token url call.
And here is my code for building the authorization header:
var auth_header = 'OAuth
realm=,oauth_consumer_key='+constants.consumerKey +
',oauth_nonce='+nonce
+',oauth_signature='+oauth_signature+
',oauth_signature_method=HMAC-
SHA1,oauth_timestamp='+ timestamp +
',oauth_token='+o_auth_token
+',oauth_version=1.0';
I've checked that my signature message matches when plugging in
applicable values using this tool:
http://oauth.googlecode.com/svn/code/javascript/example/signature.html
So it is NOT an issue with signing...
And here is an output base string I get before signing:
POSThttp%3A%2F%2Fapi.twitter.com%
2F1%2Fstatuses%2Fupdate.jsonoauth_consumer_key
%3DJxPeA0aTWPfkULuWu80dyA%26oauth
_nonce%3DIpx2fKgwUXlQ18d%26oauth_signature_method%3DHMAC-
SHA1%26oauth_timestamp%
3D1291099840%26oauth_token%3D186684223-
buwCSVt0NJQ7BDUo0q5OZo4jWjgSCDhPT2IBEGRF%
26oauth_version%3D1.0%26status%3Dwow
and here is the authorization header i sent:
OAuth
realm=,oauth_consumer_key=JxPeA0aTWPfkULuWu80dyA,oauth_nonce=Ipx2fKgwUXlQ18d,oauth_signature=OzJHTccP
%2FNurB5I1MrP2CUkGAyQ%3D,oauth_signature_method=HMAC-
SHA1,oauth_timestamp=1291099840,oauth_token=186684223-
buwCSVt0NJQ7BDUo0q5OZo4jWjgSCDhPT2IBEGRF,oauth_version=1.0
Some things I'm not sure of:
1. Is that first realm= thing needed in the auth header?
2. If I generate unix time using the local time zone, will that cause
an incorrect signature since it would be say pacific time not UTC
time? (seems to work ok to get the the access tokens though...)
3. Are spaces correct after each comma in the auth header, or not, or
does it matter?
4. Does the order matter in the auth header?
Thanks a lot for all the help, I'm beat and giving up on this for the
evening.
--
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
http://groups.google.com/group/twitter-development-talk
[twitter-dev] Re: randomly 401 error
Hey, still same. http://9.share.photo.xuite.net/u9011022/19d31e2/4424859/171241799_x.jpg On 11月30日, 上午2時39分, themattharris thematthar...@twitter.com wrote: Hi Alvin, The error in that response tells me your signature is incorrect. Double check you are generating your signature using the algorithm described here: http://dev.twitter.com/auth#signing-requests In particular I notice the parameters in your GET request are not in lexicographical order, and so I wonder if they may not be in order in your signature base string. Best, Matt On Nov 24, 10:10 pm, Alvin Wang alvin0...@gmail.com wrote: hello, Matt After removing the symbol and parameter realm, the frequency of 401 is lower. But it becomes the problem as I attach below http://9.share.photo.xuite.net/u9011022/19d319b/4424859/170775808_x.jpg On 11月25日, 上午2時32分, Matt Harris thematthar...@twitter.com wrote: Hey Alvin, Your URL looks badly formed as it includes .../home_timeline.json?count=5 I would expect to see .../home_timeline.json?count=5... (so no after the ?). You also have realm in your query string when it isn't needed. Realm is optional and when used, is only used in the Authorization header. When using OAuth in the query string you shouldn't pass realm. Your parameters should also be in lexicographical order. In your case I would have expected your URL to look like this: http://api.twitter.com/1/statuses/home_timeline.json?count=5oauth_co... page=1 You can read more about signing requests on our developer resources site: http://dev.twitter.com/pages/auth#signing-requests Best @themattharris Developer Advocate, Twitterhttp://twitter.com/themattharris 2010/11/23 Alvin Wang alvin0...@gmail.com hello Matt, here is the image when 401 occurs. http://dl.dropbox.com/u/162763/1.png On 11月23日, 下午2時17分, Matt Harris thematthar...@twitter.com wrote: Hey Alvin, So the community and developers can help you we'll need to know a little bit more about the error you are receiving. Things like the API request you are making, the request basestring, and the full response you get back are good things to include. Be careful to not include any passwords or OAuth secrets in anything you share. Best, @themattharris Developer Advocate, Twitterhttp://twitter.com/themattharris 2010/11/22 Alvin Wang alvin0...@gmail.com Are there any other solutions? Retry will still got 401randomly. Just wondering is there any twitter tech person can help? On 11月23日, 上午3時28分, Nick Bradbury nick.bradb...@gmail.com wrote: I also ran into this problem, even though I knew the signature was fine. This post from a Twitter Developer Advocate indicates that a401may be due to Twitter being stressed: http://www.devcomments.com/re-intermittent-401-and-502-during-oauth-p... In my case, ignoring the401and resending the request a little later solved the problem the majority of the time. On Nov 22, 2:43 am, Alvin Wang alvin0...@gmail.com wrote: Hi, I am currently developing an application using twitter api. However, i will ramdomly receive401error (invalid signature). Sometime it's working fine but sometime are not. Can you please help us to resolve this problem? BR, Alvin- 隱藏被引用文字 - - 顯示被引用文字 - -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter:http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources:http://dev.twitter.com/doc API updates via Twitter:http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] language and geocode problem
Hi, has somebody noticed that there are problems filtering the search with language and geocode? This search gives only few tweets or nothing: http://search.twitter.com/search.atom?lang=enq=me and with italian ther's no way to get results: http://search.twitter.com/search.atom?lang=itq=calcio thanks Mazz -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] Tweet Button Shows 0 after refresh
Hello everyone, i want to add a tweet button on a page and i am trying to test it locally before adding it online ,and the problem i am facing is that after i tweet the count changes to 1 which is correct , but if i refresh the page the count number goes back to 0. Please can u help or advise?? this is the code i am using: lia href=http://twitter.com/share; class=twitter-share-button data-count=horizontal related=twitterapi text=Twitter%20Status data-url=$url data-counturl=$url data-via=Zain_KSATweet/ascript type=text/javascript src=http://platform.twitter.com/widgets.js;/script/li where $ur l=http://www.sa.zain.com/autoforms/portal/home/personal/ friendspluspackage can anyone help or suggest anything? thank you -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] language and geocode problem
Yes. Everyone has noticed. They say they are working on it. The search API is code they don't seem too happy about, since it is acquired from Summize, but this time they are finally going to have to fix it. On Tue, Nov 30, 2010 at 8:27 AM, mazz sen...@gmail.com wrote: Hi, has somebody noticed that there are problems filtering the search with language and geocode? This search gives only few tweets or nothing: http://search.twitter.com/search.atom?lang=enq=me and with italian ther's no way to get results: http://search.twitter.com/search.atom?lang=itq=calcio thanks Mazz -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Adam Green Twitter API Consultant and Trainer http://140dev.com @140dev -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] Secure version of profile_image_url?
Making a call to account/verify_credentials and retrieving profile_image_url. Is there a HTTPS version I can reference? Thanks! -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] Re: delimited (streaming API) now default?
On Nov 29, 12:07 pm, Matt Harris thematthar...@twitter.com wrote: What I did notice is that 0x6EF = 1775 and 0x710 = 1808 -- in both cases the Hex values are 6 bytes longer than the object we are returning. This came up in March, see: http://groups.google.com/group/twitter-development-talk/msg/69131a43f64638b2? Net: it appears that the client is consuming the stream raw and not decoding the chunked transfer encoding. -- -ed costello -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] Re: language and geocode problem
Currently it looks like any geo based search queries are returning zero result. ex, on New York: http://search.twitter.com/search.json?geocode=40.739454,-73.883743,75km The question is: what is the expected timeframe for a fix on this? hours, days, weeks? They only say Engineering working on a fix. See https://twitter.com/#!/twitterapi/status/9262744515645440 http://twitter.com/#!/twitterapi/status/9636345710379008 Colin On Nov 30, 8:27 am, mazz sen...@gmail.com wrote: Hi, has somebody noticed that there are problems filtering the search with language and geocode? This search gives only few tweets or nothing:http://search.twitter.com/search.atom?lang=enq=me and with italian ther's no way to get results:http://search.twitter.com/search.atom?lang=itq=calcio thanks Mazz -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] Local searches on Search API not working
I'm consistently getting no results for a variety of Search API queries using the geocode parameter. For example: http://search.twitter.com/search.json?q=beerrpp=100page=1geocode=41.938682556152344,-87.6544189453125,100miresult_type=recent http://search.twitter.com/search.json?q=tuesdayrpp=100page=1geocode=41.938682556152344,-87.6544189453125,100miresult_type=recent This is with 100 miles of Chicago. We all know that someone who's geocoded will tweet about either beer or tuesday, near Chicago (especially the former). I've tried other locations as well. -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] Re: Any progress on Favorites API?
Thanks - I guess I'm just highlighting that there's at least one developer who's still interested in seeing the favourites updated, and I'm optimistically wondering if Twitter can provide any comment on where it's at in the planning. I, too, am interested. It would also be nice to get a total count of favorites included in the response. That is, this user has 63 favorites. As it stands, you have to iteratively page until you get to a page with count less than 20. Bill -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] Re: Best scalable method to process mentions
You should use Site Streams to gather mentions for a large number of users, or User Streams to gather for a single user. Otherwise you will run into API rate limits and other issues. -John Kalucki http://twitter.com/jkalucki Twitter, Inc. On Tue, Nov 30, 2010 at 4:09 AM, Serdar ser...@guzelanket.com wrote: I think I could not make myself clear! My app already processes new tweets in a scheduled manner, and stores the results in a database accordingly (using this API method: http://dev.twitter.com/doc/get/statuses/mentions). I don't get why would I use stream API and how it would help? On Nov 30, 4:04 am, fbparis fbou...@gmail.com wrote: I guess you should use the stream api to get mentions in real time. No need to process it directly, you could code a simple client connected to the stream api which record new mention in database, then launch your script time to time and get the mentions via the database rather than via the twitter api. On Nov 30, 1:25 am, Serdar ser...@guzelanket.com wrote: Hi I have just launched my first twitter application. Basically: -People send a tweet that mentions @appName (authorizing not needed) -App checks for new @appName mentions *from time to time*, and process them. There is a max mentions limit (200) that can be retrieved at a time via API. I know I'm not hitting this limit soon with the app but I want to code a scalable method fo get mentions. Unfortunaltely we do not have the option to get mentions in the 'oldest first' order. This causes a little tricky code for getting mentions in chunks and not missing older tweets. (Suppose you had 200+ mentions since last check). For testing I limit, 'max mentions to get at a time' to 10, in my code and it seems to be working. I won't go into more details... -I would like to know if any of you have coded something similar? -Would love to see an alternative, as I'm not happy with my code! -Is there an API method I could use for this purpose, which would make things easier? Thanks, Serdar. -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] Re: Best scalable method to process mentions
So if I use User Streams, my app doesn't have to keep track of which mentions have not been proceeded yet *that is older than the last recieved mention*, because it returns all available mentions without a max limit in a single query? All I need is to get tweets that mention @appName. I also do not want to ask for My app rests here by the way: http://guzelanket.com/puanla/ (unfortunately no English version for now) Thanks. On Nov 30, 8:14 pm, John Kalucki j...@twitter.com wrote: You should use Site Streams to gather mentions for a large number of users, or User Streams to gather for a single user. Otherwise you will run into API rate limits and other issues. -John Kaluckihttp://twitter.com/jkalucki Twitter, Inc. On Tue, Nov 30, 2010 at 4:09 AM, Serdar ser...@guzelanket.com wrote: I think I could not make myself clear! My app already processes new tweets in a scheduled manner, and stores the results in a database accordingly (using this API method: http://dev.twitter.com/doc/get/statuses/mentions). I don't get why would I use stream API and how it would help? On Nov 30, 4:04 am, fbparis fbou...@gmail.com wrote: I guess you should use the stream api to get mentions in real time. No need to process it directly, you could code a simple client connected to the stream api which record new mention in database, then launch your script time to time and get the mentions via the database rather than via the twitter api. On Nov 30, 1:25 am, Serdar ser...@guzelanket.com wrote: Hi I have just launched my first twitter application. Basically: -People send a tweet that mentions @appName (authorizing not needed) -App checks for new @appName mentions *from time to time*, and process them. There is a max mentions limit (200) that can be retrieved at a time via API. I know I'm not hitting this limit soon with the app but I want to code a scalable method fo get mentions. Unfortunaltely we do not have the option to get mentions in the 'oldest first' order. This causes a little tricky code for getting mentions in chunks and not missing older tweets. (Suppose you had 200+ mentions since last check). For testing I limit, 'max mentions to get at a time' to 10, in my code and it seems to be working. I won't go into more details... -I would like to know if any of you have coded something similar? -Would love to see an alternative, as I'm not happy with my code! -Is there an API method I could use for this purpose, which would make things easier? Thanks, Serdar. -- Twitter developer documentation and resources:http://dev.twitter.com/doc API updates via Twitter:http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] Re: oAuth reporting a status update error when none exists
I am getting this:
[request] = /1/statuses/update.json
[error] = Status is a duplicate.
On Nov 30, 12:09 am, Abraham Williams 4bra...@gmail.com wrote:
What does $connection-http_code return after calling $connection-post when
you get the duplicate error message?
Abraham
-
Abraham Williams | Hacker Advocate | abrah.am
@abraham https://twitter.com/abraham | github.com/abraham | blog.abrah.am
This email is: [ ] shareable [x] ask first [ ] private.
On Mon, Nov 29, 2010 at 23:58, EastSideDev eastside...@gmail.com wrote:
I double-checked my code, and I'm only calling statuses/update once:
$connection = new TwitterOAuth($ctck, $ctcks, $ot,$ots);
$opResult = $connection-post('statuses/update',
array('status' = $statusUpdate), TRUE);
if (!$opResult['id']) {
$msgText .= $opResult['error']. ;
}
This is code that was working fine, until recently (no changes).
On Nov 29, 10:00 pm, Abraham Williams 4bra...@gmail.com wrote:
It sound to me like your code might be making the same API request twice.
This would result in the status getting posted and the error message you
end
up with.
If you are commonly creating statuses with the same text it might just
seem
like a new status is getting posted when they are not.
Abraham
-
Abraham Williams | Hacker Advocate | abrah.am
@abraham https://twitter.com/abraham | github.com/abraham |
blog.abrah.am
This email is: [ ] shareable [x] ask first [ ] private.
On Mon, Nov 29, 2010 at 20:18, EastSideDev eastside...@gmail.com
wrote:
I have an application that uses oAuth to post a tweet on behalf of a
user. I noticed today that when I do a status update, I'm getting a
Status is a duplicate error message, when in fact the status posted
correctly.
I have not changed my code, and I am using the Twitter oAuth library
(same code been working fine since June). Are we experiencing some API
issues?
--
Twitter developer documentation and resources:
http://dev.twitter.com/doc
API updates via Twitter:http://twitter.com/twitterapi
Issues/Enhancements Tracker:
http://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
http://groups.google.com/group/twitter-development-talk
--
Twitter developer documentation and resources:http://dev.twitter.com/doc
API updates via Twitter:http://twitter.com/twitterapi
Issues/Enhancements Tracker:
http://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
http://groups.google.com/group/twitter-development-talk
--
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
http://groups.google.com/group/twitter-development-talk
[twitter-dev] Re: Local searches on Search API not working
You should follow @twitterapi as they Tweeted there was a problem with this earlier today On Nov 30, 12:33 pm, Aaron Rankin aran...@sproutsocial.com wrote: I'm consistently getting no results for a variety of Search API queries using the geocode parameter. For example: http://search.twitter.com/search.json?q=beerrpp=100page=1geocode=4... http://search.twitter.com/search.json?q=tuesdayrpp=100page=1geocod... This is with 100 miles of Chicago. We all know that someone who's geocoded will tweet about either beer or tuesday, near Chicago (especially the former). I've tried other locations as well. -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] Twitter as a cell phone feature
Hello For my technology and society class, I'm required to make up a technology/invention that does not exist. so i came up with a cell phone application that scans barcodes of items in stores and provides costumers with full information. I also want to add twitter as a feature, so costumers can share the information. Can someone please tell me the steps to how to build a twitter feature into this application? Thank you very much. -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] Differences between trends and trends/current??
Hi Ed, trends/current is the most appropriate and informationally dense end point and will stick around. Taylor On Mon, Nov 29, 2010 at 7:24 PM, M. Edward (Ed) Borasky zn...@borasky-research.net wrote: I'm starting to write some code that uses the trends portions of the API. I notice that there are two similar endpoints, 'GET trends and GET trends/current. They look pretty much alike in the documentation, except for a minor format difference in the returned JSON. However, if I actually use the Try it option, it looks like GET trends/current returns more information. Given that my application is a data collector, I'd obviously prefer more information and plan to code using GET trends/current. Is this just a documentation glitch, or is the new format from GET trends/current an undocumented feature that might disappear? -- M. Edward (Ed) Borasky http://borasky-research.net http://twitter.com/znmeb A mathematician is a device for turning coffee into theorems. - Paul Erdos -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] Re: Trends data not updating for woeid = 4118 (Toronto) since Nov 22
Hey Matt, Excellent! fresh trend data following in for woeid = 4118 aka Toronto Many Thanks to the team for the fix! Ian http://www.Twendr.com , your Twitter Trends Dashboard, extremely Beta On Nov 29, 5:13 pm, Matt Harris thematthar...@twitter.com wrote: Hi Ian, Thanks for letting us know about this. The team found an issue in the code and have been working on a fix. You should see the trends updated over the next few hours (if they aren't already). Best, @themattharris Developer Advocate, Twitterhttp://twitter.com/themattharris On Fri, Nov 26, 2010 at 12:28 PM, Ian Irving ian.irv...@gmail.com wrote: pollinghttp://api.twitter.com/1/trends/4118.json has been returning the same data set since ~ Nov 22 in fact the data set reports as_of: 2010-11-26T20:18:43Z created_at: 2010-11-22T22:13:28Z I've retrieved a few other locations and not seen a problem. -- Twitter developer documentation and resources:http://dev.twitter.com/doc API updates via Twitter:http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] Differences between trends and trends/current??
Thanks!! I'm also looking at the local trends API - there seems to be a world-wide endpoint there (WOEID=1) and the documentation there indicates that there's a caching frequency of five minutes. So that's probably what I'll go with. -- M. Edward (Ed) Borasky http://borasky-research.net http://twitter.com/znmeb A mathematician is a device for turning coffee into theorems. - Paul Erdos Quoting Taylor Singletary taylorsinglet...@twitter.com: Hi Ed, trends/current is the most appropriate and informationally dense end point and will stick around. Taylor On Mon, Nov 29, 2010 at 7:24 PM, M. Edward (Ed) Borasky zn...@borasky-research.net wrote: I'm starting to write some code that uses the trends portions of the API. I notice that there are two similar endpoints, 'GET trends and GET trends/current. They look pretty much alike in the documentation, except for a minor format difference in the returned JSON. However, if I actually use the Try it option, it looks like GET trends/current returns more information. Given that my application is a data collector, I'd obviously prefer more information and plan to code using GET trends/current. Is this just a documentation glitch, or is the new format from GET trends/current an undocumented feature that might disappear? -- M. Edward (Ed) Borasky http://borasky-research.net http://twitter.com/znmeb A mathematician is a device for turning coffee into theorems. - Paul Erdos -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] Re: Getting tweets from users following a particular user
Is there a nice way of making such a list? Or is it going to involve something horrible? On Nov 30, 1:58 am, fbparis fbou...@gmail.com wrote: Simply create an account to follow them :) Or make a list... On Nov 30, 1:51 am, Louis louis...@gmail.com wrote: I was under the impression that using 'follow' simply returns tweets or retweets which were originally created by, or were in reply to, a specific user - I'm interested in getting *any* tweet from all users following this special user (sampled possibly). For example, I could use it to see what people who follow @Microsoft talk about, Microsoft related or not. On Nov 29, 9:12 pm, M. Edward (Ed) Borasky zn...@borasky- research.net wrote: Quoting Louis louis...@gmail.com: I'd like to stream tweets from the set of users which follow a specific user. Is there a way to do this directly, or a way to get a list of such users, so I can then specify to filter tweets from them only? It depends on how many followers the user has. Up to 5000, you can do it with the follow parameter either on the filter Streaming endpoint or on User Streams. Over 5000, you will need to get elevated access via Gnip. -- M. Edward (Ed) Boraskyhttp://borasky-research.nethttp://twitter.com/znmeb A mathematician is a device for turning coffee into theorems. - Paul Erdos -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] Re: oAuth reporting a status update error when none exists
I am afraid Twitter has added this error - don't allow any duplicate
tweet at least from Twitter API. I have to add random text to bypass
this 403 error.
On Nov 30, 11:11 am, EastSideDev eastside...@gmail.com wrote:
I am getting this:
[request] = /1/statuses/update.json
[error] = Status is a duplicate.
On Nov 30, 12:09 am, Abraham Williams 4bra...@gmail.com wrote:
What does $connection-http_code return after calling $connection-post when
you get the duplicate error message?
Abraham
-
Abraham Williams | Hacker Advocate | abrah.am
@abraham https://twitter.com/abraham | github.com/abraham | blog.abrah.am
This email is: [ ] shareable [x] ask first [ ] private.
On Mon, Nov 29, 2010 at 23:58, EastSideDev eastside...@gmail.com wrote:
I double-checked my code, and I'm only calling statuses/update once:
$connection = new TwitterOAuth($ctck, $ctcks, $ot,$ots);
$opResult = $connection-post('statuses/update',
array('status' = $statusUpdate), TRUE);
if (!$opResult['id']) {
$msgText .= $opResult['error']. ;
}
This is code that was working fine, until recently (no changes).
On Nov 29, 10:00 pm, Abraham Williams 4bra...@gmail.com wrote:
It sound to me like your code might be making the same API request
twice.
This would result in the status getting posted and the error message you
end
up with.
If you are commonly creating statuses with the same text it might just
seem
like a new status is getting posted when they are not.
Abraham
-
Abraham Williams | Hacker Advocate | abrah.am
@abraham https://twitter.com/abraham | github.com/abraham |
blog.abrah.am
This email is: [ ] shareable [x] ask first [ ] private.
On Mon, Nov 29, 2010 at 20:18, EastSideDev eastside...@gmail.com
wrote:
I have an application that uses oAuth to post a tweet on behalf of a
user. I noticed today that when I do a status update, I'm getting a
Status is a duplicate error message, when in fact the status posted
correctly.
I have not changed my code, and I am using the Twitter oAuth library
(same code been working fine since June). Are we experiencing some API
issues?
--
Twitter developer documentation and resources:
http://dev.twitter.com/doc
API updates via Twitter:http://twitter.com/twitterapi
Issues/Enhancements Tracker:
http://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
http://groups.google.com/group/twitter-development-talk
--
Twitter developer documentation and resources:http://dev.twitter.com/doc
API updates via Twitter:http://twitter.com/twitterapi
Issues/Enhancements Tracker:
http://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
http://groups.google.com/group/twitter-development-talk
--
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
http://groups.google.com/group/twitter-development-talk
[twitter-dev] Re: oAuth reporting a status update error when none exists
I am not doing any duplicates. I tested the app on a brand new Twitter
account, and did only a single status update. The update was actually
done, but I am still receiving the error message. I implemented
temporary fix (ignore the error code), but that's an ugly solution.
On Nov 30, 5:26 pm, Bess bess...@gmail.com wrote:
I am afraid Twitter has added this error - don't allow any duplicate
tweet at least from Twitter API. I have to add random text to bypass
this 403 error.
On Nov 30, 11:11 am, EastSideDev eastside...@gmail.com wrote:
I am getting this:
[request] = /1/statuses/update.json
[error] = Status is a duplicate.
On Nov 30, 12:09 am, Abraham Williams 4bra...@gmail.com wrote:
What does $connection-http_code return after calling $connection-post
when
you get the duplicate error message?
Abraham
-
Abraham Williams | Hacker Advocate | abrah.am
@abraham https://twitter.com/abraham | github.com/abraham |
blog.abrah.am
This email is: [ ] shareable [x] ask first [ ] private.
On Mon, Nov 29, 2010 at 23:58, EastSideDev eastside...@gmail.com wrote:
I double-checked my code, and I'm only calling statuses/update once:
$connection = new TwitterOAuth($ctck, $ctcks, $ot,$ots);
$opResult = $connection-post('statuses/update',
array('status' = $statusUpdate), TRUE);
if (!$opResult['id']) {
$msgText .= $opResult['error']. ;
}
This is code that was working fine, until recently (no changes).
On Nov 29, 10:00 pm, Abraham Williams 4bra...@gmail.com wrote:
It sound to me like your code might be making the same API request
twice.
This would result in the status getting posted and the error message
you
end
up with.
If you are commonly creating statuses with the same text it might just
seem
like a new status is getting posted when they are not.
Abraham
-
Abraham Williams | Hacker Advocate | abrah.am
@abraham https://twitter.com/abraham | github.com/abraham |
blog.abrah.am
This email is: [ ] shareable [x] ask first [ ] private.
On Mon, Nov 29, 2010 at 20:18, EastSideDev eastside...@gmail.com
wrote:
I have an application that uses oAuth to post a tweet on behalf of a
user. I noticed today that when I do a status update, I'm getting a
Status is a duplicate error message, when in fact the status
posted
correctly.
I have not changed my code, and I am using the Twitter oAuth library
(same code been working fine since June). Are we experiencing some
API
issues?
--
Twitter developer documentation and resources:
http://dev.twitter.com/doc
API updates via Twitter:http://twitter.com/twitterapi
Issues/Enhancements Tracker:
http://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
http://groups.google.com/group/twitter-development-talk
--
Twitter developer documentation and resources:http://dev.twitter.com/doc
API updates via Twitter:http://twitter.com/twitterapi
Issues/Enhancements Tracker:
http://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
http://groups.google.com/group/twitter-development-talk
--
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] Differences between trends and trends/current??
Hey Ed, Yes, the local trends supports a woeid of 1 for 'the world'. The other available woeid's can be found by querying: https://api.twitter.com/1/trends/available.json Best, @themattharris Developer Advocate, Twitter http://twitter.com/themattharris On Tue, Nov 30, 2010 at 4:55 PM, M. Edward (Ed) Borasky zn...@borasky-research.net wrote: Thanks!! I'm also looking at the local trends API - there seems to be a world-wide endpoint there (WOEID=1) and the documentation there indicates that there's a caching frequency of five minutes. So that's probably what I'll go with. -- M. Edward (Ed) Borasky http://borasky-research.net http://twitter.com/znmeb A mathematician is a device for turning coffee into theorems. - Paul Erdos Quoting Taylor Singletary taylorsinglet...@twitter.com: Hi Ed, trends/current is the most appropriate and informationally dense end point and will stick around. Taylor On Mon, Nov 29, 2010 at 7:24 PM, M. Edward (Ed) Borasky zn...@borasky-research.net wrote: I'm starting to write some code that uses the trends portions of the API. I notice that there are two similar endpoints, 'GET trends and GET trends/current. They look pretty much alike in the documentation, except for a minor format difference in the returned JSON. However, if I actually use the Try it option, it looks like GET trends/current returns more information. Given that my application is a data collector, I'd obviously prefer more information and plan to code using GET trends/current. Is this just a documentation glitch, or is the new format from GET trends/current an undocumented feature that might disappear? -- M. Edward (Ed) Borasky http://borasky-research.net http://twitter.com/znmeb A mathematician is a device for turning coffee into theorems. - Paul Erdos -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] Re: oAuth reporting a status update error when none exists
Hi,
So the 403 duplicate status means the message you are sending is the same as
the last message in the users timeline.
When you say the post is posting correctly, how are you validating that this
has happened?
Also, can you show an example request that you are making, for example:
http://api.twitter.com/1/statuses/update.json
POST: status=my text
Values from a real request would be helpful to identify what could be
causing us to think the update is a duplicate.
Best,
@themattharris
Developer Advocate, Twitter
http://twitter.com/themattharris
On Tue, Nov 30, 2010 at 5:34 PM, EastSideDev eastside...@gmail.com wrote:
I am not doing any duplicates. I tested the app on a brand new Twitter
account, and did only a single status update. The update was actually
done, but I am still receiving the error message. I implemented
temporary fix (ignore the error code), but that's an ugly solution.
On Nov 30, 5:26 pm, Bess bess...@gmail.com wrote:
I am afraid Twitter has added this error - don't allow any duplicate
tweet at least from Twitter API. I have to add random text to bypass
this 403 error.
On Nov 30, 11:11 am, EastSideDev eastside...@gmail.com wrote:
I am getting this:
[request] = /1/statuses/update.json
[error] = Status is a duplicate.
On Nov 30, 12:09 am, Abraham Williams 4bra...@gmail.com wrote:
What does $connection-http_code return after calling
$connection-post when
you get the duplicate error message?
Abraham
-
Abraham Williams | Hacker Advocate | abrah.am
@abraham https://twitter.com/abraham | github.com/abraham |
blog.abrah.am
This email is: [ ] shareable [x] ask first [ ] private.
On Mon, Nov 29, 2010 at 23:58, EastSideDev eastside...@gmail.com
wrote:
I double-checked my code, and I'm only calling statuses/update
once:
$connection = new TwitterOAuth($ctck, $ctcks, $ot,$ots);
$opResult = $connection-post('statuses/update',
array('status' = $statusUpdate), TRUE);
if (!$opResult['id']) {
$msgText .= $opResult['error']. ;
}
This is code that was working fine, until recently (no changes).
On Nov 29, 10:00 pm, Abraham Williams 4bra...@gmail.com wrote:
It sound to me like your code might be making the same API
request twice.
This would result in the status getting posted and the error
message you
end
up with.
If you are commonly creating statuses with the same text it might
just
seem
like a new status is getting posted when they are not.
Abraham
-
Abraham Williams | Hacker Advocate | abrah.am
@abraham https://twitter.com/abraham | github.com/abraham |
blog.abrah.am
This email is: [ ] shareable [x] ask first [ ] private.
On Mon, Nov 29, 2010 at 20:18, EastSideDev
eastside...@gmail.com
wrote:
I have an application that uses oAuth to post a tweet on behalf
of a
user. I noticed today that when I do a status update, I'm
getting a
Status is a duplicate error message, when in fact the status
posted
correctly.
I have not changed my code, and I am using the Twitter oAuth
library
(same code been working fine since June). Are we experiencing
some API
issues?
--
Twitter developer documentation and resources:
http://dev.twitter.com/doc
API updates via Twitter:http://twitter.com/twitterapi
Issues/Enhancements Tracker:
http://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
http://groups.google.com/group/twitter-development-talk
--
Twitter developer documentation and resources:
http://dev.twitter.com/doc
API updates via Twitter:http://twitter.com/twitterapi
Issues/Enhancements Tracker:
http://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
http://groups.google.com/group/twitter-development-talk
--
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker:
http://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
http://groups.google.com/group/twitter-development-talk
--
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] Re: randomly 401 error
Hi Alvin, I notice in your request that you are sending a Basic Authentication header in addition to the OAuth. Specifically the line: Authorization: Basic When using OAuth this is not required and will be confusing the request. Specifically you are sending OAuth in the request but telling the API to authorise using Basic Auth. What you should do is either drop the Authorization header completley, or move the OAuth parameters into the Authorization header. A possible reason why some of your requests are working and others are failing is that some methods do not require authentication. In those cases the failing authentication details you are sending are being ignored and the request is most likely running unauthenticated. Best, @themattharris Developer Advocate, Twitter http://twitter.com/themattharris 2010/11/30 Alvin Wang alvin0...@gmail.com Hey, still same. http://9.share.photo.xuite.net/u9011022/19d31e2/4424859/171241799_x.jpg On 11月30日, 上午2時39分, themattharris thematthar...@twitter.com wrote: Hi Alvin, The error in that response tells me your signature is incorrect. Double check you are generating your signature using the algorithm described here: http://dev.twitter.com/auth#signing-requests In particular I notice the parameters in your GET request are not in lexicographical order, and so I wonder if they may not be in order in your signature base string. Best, Matt On Nov 24, 10:10 pm, Alvin Wang alvin0...@gmail.com wrote: hello, Matt After removing the symbol and parameter realm, the frequency of 401 is lower. But it becomes the problem as I attach below http://9.share.photo.xuite.net/u9011022/19d319b/4424859/170775808_x.jpg On 11月25日, 上午2時32分, Matt Harris thematthar...@twitter.com wrote: Hey Alvin, Your URL looks badly formed as it includes .../home_timeline.json?count=5 I would expect to see .../home_timeline.json?count=5... (so no after the ?). You also have realm in your query string when it isn't needed. Realm is optional and when used, is only used in the Authorization header. When using OAuth in the query string you shouldn't pass realm. Your parameters should also be in lexicographical order. In your case I would have expected your URL to look like this: http://api.twitter.com/1/statuses/home_timeline.json?count=5oauth_co... page=1 You can read more about signing requests on our developer resources site: http://dev.twitter.com/pages/auth#signing-requests Best @themattharris Developer Advocate, Twitterhttp://twitter.com/themattharris 2010/11/23 Alvin Wang alvin0...@gmail.com hello Matt, here is the image when 401 occurs. http://dl.dropbox.com/u/162763/1.png On 11月23日, 下午2時17分, Matt Harris thematthar...@twitter.com wrote: Hey Alvin, So the community and developers can help you we'll need to know a little bit more about the error you are receiving. Things like the API request you are making, the request basestring, and the full response you get back are good things to include. Be careful to not include any passwords or OAuth secrets in anything you share. Best, @themattharris Developer Advocate, Twitterhttp://twitter.com/themattharris 2010/11/22 Alvin Wang alvin0...@gmail.com Are there any other solutions? Retry will still got 401randomly. Just wondering is there any twitter tech person can help? On 11月23日, 上午3時28分, Nick Bradbury nick.bradb...@gmail.com wrote: I also ran into this problem, even though I knew the signature was fine. This post from a Twitter Developer Advocate indicates that a401may be due to Twitter being stressed: http://www.devcomments.com/re-intermittent-401-and-502-during-oauth-p... In my case, ignoring the401and resending the request a little later solved the problem the majority of the time. On Nov 22, 2:43 am, Alvin Wang alvin0...@gmail.com wrote: Hi, I am currently developing an application using twitter api. However, i will ramdomly receive401error (invalid signature). Sometime it's working fine but sometime are not. Can you please help us to resolve this problem? BR, Alvin- 隱藏被引用文字 - - 顯示被引用文字 - -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter:http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter:http://twitter.com/twitterapi
[twitter-dev] Re: language and geocode problem
They're working on a fix. That's all. People always asking timeframe to coders make me mad.. If your car refuses to start and you have no idea why, and someone bugging you every 2 minutes : how long before it works ? What would you say.. On Nov 30, 5:47 pm, Colin Surprenant colin.surpren...@gmail.com wrote: Currently it looks like any geo based search queries are returning zero result. ex, on New York:http://search.twitter.com/search.json?geocode=40.739454,-73.883743,75km The question is: what is the expected timeframe for a fix on this? hours, days, weeks? They only say Engineering working on a fix. See https://twitter.com/#!/twitterapi/status/9262744515645440http://twitter.com/#!/twitterapi/status/9636345710379008 Colin On Nov 30, 8:27 am, mazz sen...@gmail.com wrote: Hi, has somebody noticed that there are problems filtering the search with language and geocode? This search gives only few tweets or nothing:http://search.twitter.com/search.atom?lang=enq=me and with italian ther's no way to get results:http://search.twitter.com/search.atom?lang=itq=calcio thanks Mazz -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] language and geocode problem
For what it's worth, these Search API issues should be fixed now. Sorry about the mess. Taylor On Tuesday, November 30, 2010, fbparis fbou...@gmail.com wrote: They're working on a fix. That's all. People always asking timeframe to coders make me mad.. If your car refuses to start and you have no idea why, and someone bugging you every 2 minutes : how long before it works ? What would you say.. On Nov 30, 5:47 pm, Colin Surprenant colin.surpren...@gmail.com wrote: Currently it looks like any geo based search queries are returning zero result. ex, on New York:http://search.twitter.com/search.json?geocode=40.739454,-73.883743,75km The question is: what is the expected timeframe for a fix on this? hours, days, weeks? They only say Engineering working on a fix. See https://twitter.com/#!/twitterapi/status/9262744515645440http://twitter.com/#!/twitterapi/status/9636345710379008 Colin On Nov 30, 8:27 am, mazz sen...@gmail.com wrote: Hi, has somebody noticed that there are problems filtering the search with language and geocode? This search gives only few tweets or nothing:http://search.twitter.com/search.atom?lang=enq=me and with italian ther's no way to get results:http://search.twitter.com/search.atom?lang=itq=calcio thanks Mazz -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] Problem - SSL CA cert
Thanks for quick reply. I will check it and reply the status soon. Regards, George On Tue, Nov 30, 2010 at 11:38 PM, John Adams j...@twitter.com wrote: On Mon, Nov 29, 2010 at 11:11 PM, Georgooty varghese georgo...@gmail.comwrote: Dear Twitter, I wont be able to log in to twitter insecure using twitter(using curl command line tool, you disable this with -k/--insecure). But facebook has no problem. Why this? I think that client need a certifuication? Is it right? Twitter uses an EV Certificate issued by Verisign. Facebook uses a 3rd party EV Certificate, which is not issued by Verisign. Some versions of curl do not ship with a proper certificate chain. That's why you're having issues verifying the certificate. The attached CA Bundle file will fix your issue. While it's 239K, you really only need the CA and Intermediate certs in this file for Verisign. You can remove the rest. This file gets loaded in your code with: curl_easy_setopt(m_hcURL, CURLOPT_CAINFO,curl-ca-bundle.crt)); Your hardware may also have additional dependencies on having an accurate, real-time clock, depending on how you communicate with the API and what level of verification you do on SSL certs. Make sure that's set correctly as well. -j -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] Running multiple streaming client on the same machine
I have a question about the streaming API. We got one server where we run two streaming API clients , each one follow different account list and have a separate processing for the incoming tweets. Is there any limitation of running these two clients on the same machine ? can it cause any issues with the rate limit ? (right now we're under the shadow access control). -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] Problem - SSL CA cert
Dear Twitter, I have checked. But its not working. I tried the curl-ca-bundle.crt file and also tried ca-certificates.crt files that comes with Ubuntu-10.04 In both cases I am getting the following error . “Info: error:140D108E:SSL routines:TLS1_CHANGE_CIPHER_STATE:compression library error” I have attached the log file with this mail Command I used curl --capath /etc/ssl/certs/ --cacert /etc/ssl/certs/ca-certificates.crt --trace /etc/error.txt https://api.twitter.com curl --capath /etc/ssl/certs/ --cacert /etc/ssl/certs/ curl-ca-bundle.crt --trace /etc/error.txt https://api.twitter.com Anybody please help meI am waiting for your reply. Regards, George On Tue, Nov 30, 2010 at 11:38 PM, John Adams j...@twitter.com wrote: On Mon, Nov 29, 2010 at 11:11 PM, Georgooty varghese georgo...@gmail.comwrote: Dear Twitter, I wont be able to log in to twitter insecure using twitter(using curl command line tool, you disable this with -k/--insecure). But facebook has no problem. Why this? I think that client need a certifuication? Is it right? Twitter uses an EV Certificate issued by Verisign. Facebook uses a 3rd party EV Certificate, which is not issued by Verisign. Some versions of curl do not ship with a proper certificate chain. That's why you're having issues verifying the certificate. The attached CA Bundle file will fix your issue. While it's 239K, you really only need the CA and Intermediate certs in this file for Verisign. You can remove the rest. This file gets loaded in your code with: curl_easy_setopt(m_hcURL, CURLOPT_CAINFO,curl-ca-bundle.crt)); Your hardware may also have additional dependencies on having an accurate, real-time clock, depending on how you communicate with the API and what level of verification you do on SSL certs. Make sure that's set correctly as well. -j -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk == Info: SSLv3, TLS handshake, Client hello (1): = Send SSL data, 108 bytes (0x6c) : 01 00 00 68 03 01 4c f4 e3 8f 1f c6 be 81 5c ca ...h..L...\. 0010: 25 3e 9e 7f 75 dd 06 fc b3 ce b0 7f 5c 5c fc d5 %.u..\\.. 0020: 1b bb 1b ae 04 ee 00 00 26 00 39 00 38 00 35 00 .9.8.5. 0030: 16 00 13 00 0a 00 33 00 32 00 2f 00 07 00 05 00 ..3.2./. 0040: 04 00 15 00 12 00 09 00 14 00 11 00 08 00 03 02 0050: 01 00 00 18 00 00 00 14 00 12 00 00 0f 61 70 69 .api 0060: 2e 74 77 69 74 74 65 72 2e 63 6f 6d .twitter.com == Info: SSLv3, TLS handshake, Server hello (2): = Recv SSL data, 74 bytes (0x4a) : 02 00 00 46 03 01 4c f4 e3 8f ff 96 8b 4b c1 48 ...F..L..K.H 0010: c5 e6 a5 e6 79 46 7e a9 1e ed 3d 55 86 56 f0 28 yF~...=U.V.( 0020: 1a 60 1c 1e 88 00 20 19 f1 fc ab 00 28 0f 51 94 .` .(.Q. 0030: 1c 0f 63 90 89 34 0c cd 5b 36 c0 34 47 ec 9d db ..c..4..[6.4G... 0040: 61 7e fe f3 12 70 fc 00 39 01 a~...p..9. == Info: SSLv3, TLS handshake, CERT (11): = Recv SSL data, 1040 bytes (0x410) : 0b 00 04 0c 00 04 09 00 04 06 30 82 04 02 30 82 ..0...0. 0010: 03 6b a0 03 02 01 02 02 03 13 e1 36 30 0d 06 09 .k.60... 0020: 2a 86 48 86 f7 0d 01 01 05 05 00 30 4e 31 0b 30 *.H0N1.0 0030: 09 06 03 55 04 06 13 02 55 53 31 10 30 0e 06 03 ...UUS1.0... 0040: 55 04 0a 13 07 45 71 75 69 66 61 78 31 2d 30 2b UEquifax1-0+ 0050: 06 03 55 04 0b 13 24 45 71 75 69 66 61 78 20 53 ..U...$Equifax S 0060: 65 63 75 72 65 20 43 65 72 74 69 66 69 63 61 74 ecure Certificat 0070: 65 20 41 75 74 68 6f 72 69 74 79 30 1e 17 0d 31 e Authority0...1 0080: 30 30 37 31 33 31 30 34 30 31 36 5a 17 0d 31 31 00713104016Z..11 0090: 30 38 31 35 31 32 35 35 31 37 5a 30 81 e1 31 29 0815125517Z0..1) 00a0: 30 27 06 03 55 04 05 13 20 5a 79 73 32 64 4a 4a 0'..U... Zys2dJJ 00b0: 30 39 45 50 6f 45 56 47 58 59 74 65 67 49 64 78 09EPoEVGXYtegIdx 00c0: 47 33 4f 5a 74 45 4f 69 62 31 0b 30 09 06 03 55 G3OZtEOib1.0...U 00d0: 04 06 13 02 55 53 31 16 30 14 06 03 55 04 0a 0c US1.0...U... 00e0: 0d 2a 2e 74 77 69 74 74 65 72 2e 63 6f 6d 31 13 .*.twitter.com1. 00f0: 30 11 06 03 55 04 0b 13 0a 47 54 35 37 39 33 32 0...UGT57932 0100: 30 37 34 31 31 30 2f 06 03 55 04 0b 13 28 53 65 074110/..U...(Se 0110: 65 20 77 77 77 2e 72 61 70 69 64 73 73 6c 2e 63 e www.rapidssl.c 0120: 6f 6d 2f 72 65 73 6f 75 72 63 65 73 2f 63 70 73 om/resources/cps 0130: 20 28 63 29 31 30 31 2f 30 2d 06 03 55 04 0b 13 (c)101/0-..U...
Re: [twitter-dev] Problem - SSL CA cert
_Info: error:140D108E:SSL routines:TLS1_CHANGE_CIPHER_STATE:compression library error_ This suggests a problem in your crypto library, or less likely zlib. -- personal: http://www.cameronkaiser.com/ -- Cameron Kaiser * Floodgap Systems * www.floodgap.com * ckai...@floodgap.com -- Never say never again. - -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] Problem - SSL CA cert
Dear Twitter, I dont understand about crypto libray or less likely zlib... Could u please give a description for this. What do this for twitter ? Where is get from or less likely zlib.? I am waiting for your reply Regards, George On Wed, Dec 1, 2010 at 10:27 AM, Cameron Kaiser spec...@floodgap.comwrote: _Info: error:140D108E:SSL routines:TLS1_CHANGE_CIPHER_STATE:compression library error_ This suggests a problem in your crypto library, or less likely zlib. -- personal: http://www.cameronkaiser.com/ -- Cameron Kaiser * Floodgap Systems * www.floodgap.com * ckai...@floodgap.com -- Never say never again. - -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] Problem - SSL CA cert
_Info: error:140D108E:SSL routines:TLS1_CHANGE_CIPHER_STATE:compression library error_ This suggests a problem in your crypto library, or less likely zlib. I dont understand about crypto libray or less likely zlib... Could u please give a description for this. What do this for twitter ? This is getting off-topic for this list, but in brief, this refers to your cryptographic library which is being used to handle the encryption and decryption to Twitter's SSL server. zlib refers to the specific compression library your system likely uses (and you will note that this is referenced in the error above). Many crypto libraries use zlib. You should make sure that your cryptographic software, such as NSS or OpenSSL, passes all of its built-in self-tests such as by running 'make test' in the source directory for your crypto distro. If it doesn't work, SSL through libcurl won't either. If you're still not sure what this is, you probably should be referring to the libcurl documentation for more. libcurl can use either NSS or OpenSSL. -- personal: http://www.cameronkaiser.com/ -- Cameron Kaiser * Floodgap Systems * www.floodgap.com * ckai...@floodgap.com -- You can't kill me because I've got magic aaargh. -- Terry Pratchett -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
