[twitter-dev] Invalid / used nonce
Hello everybody, Yesterday I was exposing an issue I encoutered. My code was working perfectly, and then I started having a 401 error code with this error message : errorInvalid / used nonce/error when I make API calls. I thought it was solved because yesterday I did some API calls that made it through. However this issue is still here today. Actually, when I make API calls (POST, GET or OAuth requests), sometimes everything works fine, sometimes i have the Invalid / used nonce error. As I told Taylor yesterday, I am sure that that the system time is correct (because when I change it, nothing works), and because as I said, when i try to send a request with the exact same code running, sometimes it fails, sometimes it does not. Here are dumps of the communications I tried to send a tweet, had an error : http://pastebin.com/ur2JYtnM A few seconds later, i run the exact same code and it is valid : http://pastebin.com/6knpLHBW (I will reset my key and secret ^^) I really do not know where the issue comes from, because the code was running flawlessly last week! Any kind of help appreciated. Regards. Mounir Regragui
[twitter-dev] Expire remove oAuth access_token via API
Excuse the redundancy of this question if it's been asked already, but prior Google searches didn't turn up any clear guidelines. Is there a way presently to have a user disqualify/expire their access_token for a given application via an API call? I understand that we can just drop the access_token on our side and not use it again, but I believe the connection to the application would still exist in the user_profile which might lead to user confusion later on? What's the correct way to handle this? Should we be providing links back into the twitter web portal to manage it? Thanks. BJ
[twitter-dev] Uploading photo w\ OAuth echo
Hi. I also keep getting 401 from Twitpic. Just to make sure - do we need to add the realm to the signature calculation ? Or only to the header ? Thanks for the help, Roi.
Re: [twitter-dev] Re: Open Source CMS Module and Consumer Secret
On Tue, Jul 27, 2010 at 17:02, M. Edward (Ed) Borasky zn...@borasky-research.net wrote: There are plenty of open source *library* developers, and plenty of applications that use open source libraries, but not all that many open source full applications. The only ones I can think of at the moment are Gwibber (Gnome), Choqok (KDE), mine (Social Media Analytics Research Toolkit), Spaz, get2gnow, and ttytter. It's not quite ready for civilian usage and I've been lax with new development work while waiting for Twitter to figure out this particular issue, but http://github.com/genehack/app-status-skein is a full application too. chrs, john.
[twitter-dev] Re: Non-web application Authorization - Granting Multiple Times
Hi Talyor, Thanks for your input. It helped. :) And now I can cache the data (oauth_token_secret and oauth_token) to avoid multiple authorizations. -Gaurav www.mastergaurav.com On Jul 28, 8:03 pm, Taylor Singletary taylorsinglet...@twitter.com wrote: Hi Gaurav, Once you've gone through all the steps of OAuth and have acquired an access token (made up of an oauth_token and oauth_token_secret), you can then persist the access token in whatever means of storage your application uses. Then, when making an API call on behalf of a Twitter user for whom you've acquired an access token, you use your stored tokens instead of renegotiating for them. How to instantiate your OAuth stack's Access Token is different from library to library, but there are some tips that apply here:http://bit.ly/1token Taylor On Wed, Jul 28, 2010 at 3:35 AM, Gaurav Vaish gaurav.va...@gmail.comwrote: Hi, Using Twitter4J API, I have been able to successfully fetch the data and perform an status update using OAuth. Here are the results:http://twitter.com/mastergaurav/status/19730194057 (Positive Results) Problem -- Once a user grants access to the user, how can I reuse the granted access permission over and over again? Currently, I use Customer Key and Secret to get OAuth Request Token (by first hittinghttps://twitter.com/oauth/request_token) And I would not like to hit it over and over again for the same user (until the permissions are revoked). How can I achieve the same... -Gaurav
Re: [twitter-dev] Need inputs to implement Twitter app using xAuth
Thanks a lot Ernandes and Abraham. Regards, Sambath On Wed, Jul 28, 2010 at 9:33 PM, Abraham Williams 4bra...@gmail.com wrote: Twitter4j supports xAuth: http://goo.gl/ZmM2 Abraham - Abraham Williams | Hacker Advocate | http://abrah.am @abraham | http://projects.abrah.am | http://blog.abrah.am This email is: [ ] shareable [x] ask first [ ] private. On Wed, Jul 28, 2010 at 02:29, Sambath Chandran sambat...@gmail.comwrote: All, I am implementing an application to receive and the latest tweet from the twitter. After refering to twitter website, I concluded to use xAuth authentication for my development. Can anybody let me know is there any ready to use java library for xAuth? Basially I want to know to how to make xAuth work with Java. Thanks, Sambath
Re: [twitter-dev] Need inputs to implement Twitter app using xAuth
But I just want to know one thing. How much difficult to implement making xAuth call in Java without any libraries? Thanks, Sambath On Thu, Jul 29, 2010 at 11:29 AM, Sambath Chandran sambat...@gmail.comwrote: Thanks a lot Ernandes and Abraham. Regards, Sambath On Wed, Jul 28, 2010 at 9:33 PM, Abraham Williams 4bra...@gmail.comwrote: Twitter4j supports xAuth: http://goo.gl/ZmM2 Abraham - Abraham Williams | Hacker Advocate | http://abrah.am @abraham | http://projects.abrah.am | http://blog.abrah.am This email is: [ ] shareable [x] ask first [ ] private. On Wed, Jul 28, 2010 at 02:29, Sambath Chandran sambat...@gmail.comwrote: All, I am implementing an application to receive and the latest tweet from the twitter. After refering to twitter website, I concluded to use xAuth authentication for my development. Can anybody let me know is there any ready to use java library for xAuth? Basially I want to know to how to make xAuth work with Java. Thanks, Sambath
[twitter-dev] Re: How to check specific user is in my list?
Is this possible? I've been searching the API docs, etc. and can't find anything on how to return just my lists a particular user is on. It'd be nice if we could do this: http://api.twitter.com/1/twitterapidocs/lists.xml?user_id=12345 Anybody, anybody? :-) On Jul 26, 8:46 pm, Nara ijwc...@gmail.com wrote: Now I'm using GET list members id method to check user is a member of the specified list. But if user has a lot of list, this method takes a long time to check. (because it requires one request to check one list) anyone have any better ideas about this problem?
[twitter-dev] Twitter site URL hijacks my sharepoint portal page
I have a sharepoint portal page with few web parts. One of these web parts is a sharepoint page viewer web part. When I configure the page viewer web part with the URL www.twitter.com and click on OK button, my portal page is hijacked and redirected to twitter home page. I am not able to open and edit my portal page now. As soon as I open my portal page in IE, it redirects to twitter page. I am using IE 8.
[twitter-dev] accented words
When I try to send an update containing accented words, the api throws an error: Incorrect signature. What can I do?
Re: [twitter-dev] accented words
On 07/29/10 16:40, David Tavárez wrote: When I try to send an update containing accented words, the api throws an error: Incorrect signature. What can I do? It sounds like you're not encoding characters properly -- see http://groups.google.com/group/twitter-development-talk/msg/12d17a57566e2ad1?hl=en_US Dave
Re: [twitter-dev] API HTTP Post statuses/update.xml
For instance, set up the my database to create 200 tweets to post to a account. It ran at 11:49 AM EST. I noticed that 127 tweets were posted and the remaining got kicked with the error response. Not sure if there is a limit of 127 I thought it was 150 limit per hour. This also does not hit the 1000 daily limit since it was only 200 tweets. I will try this again in about 1 hour. I should be able to start tweeting again. Let me know what you think? On Wed, Jul 28, 2010 at 12:19 PM, Eric Mortensen emort...@gmail.com wrote: But, It appears did not hit a 1000 update limit since after an hour and can start updates again. That why it appears to be an hourly limit. Not to mention when this started I did not even have a 1000 tweets total on the account. That is why it can't be the 1000 a day limit. There is should be another reason for this. On Tue, Jul 27, 2010 at 6:56 PM, Matt Harris thematthar...@twitter.comwrote: Hey Eric, That error is the Twitter Limits kicking in saying there are too many status updates being posted by the account. This isn't an API rate limit but a natural limit which applies to all of Twitter. A user may not Twitter more than 1000 updates a day (this includes retweets). More information on these limits are explained on the page I linked to before: http://support.twitter.com/forums/10711/entries/15364 Hope that clarifies the what is happening. Matt On Tue, Jul 27, 2010 at 12:27 PM, Eric Mortensen emort...@gmail.comwrote: Here is a response: ?xml version=1.0 encoding=UTF-8? hash errorUser is over daily status update limit./error request/1/statuses/update.xml/request /hash On Thu, Jul 15, 2010 at 5:41 PM, Matt Harris thematthar...@twitter.comwrote: Hey Eric, Sorry that help article didn't answer your question. Can you provide the actual HTTP request being made and the HTTP response you get back? We're interested in the response body content in particular. Also, remember we disable basic authentication on August 16th so you want to switch to that method of authentication now. Matt On Thu, Jul 15, 2010 at 12:46 PM, Eric Mortensen emort...@gmail.comwrote: Unfortunately not. Do you have anything else that might explain it? On Thu, Jul 15, 2010 at 1:48 PM, Matt Harris thematthar...@twitter.com wrote: Hi Eric, In addition to the API Rate Limits there are general usage limits which apply to all of Twitter, including the website. These limits restrict various actions including the number of updates that can be posted per day. You can read more about Twitter Limits on our help website: http://support.twitter.com/forums/10711/entries/15364 Hope that answers your question, Matt On Thu, Jul 15, 2010 at 10:11 AM, Eric emort...@gmail.com wrote: It appears that I am hitting a 150 post rate limit when I use the statuses/update.xml api to update a twitter account eventhough I should not have this limit doing only a post. Is there a reason why? Here is the code I am using from oracle to do this: create or replace PACKAGE BODY tweet AS twit_host VARCHAR2(255) := 'api.twitter.com'; twit_protocol VARCHAR2(10) := 'http://'; -- URL for status updates tweet_url VARCHAR2(255) := '/1/statuses/update.xml'; FUNCTION tweet ( p_user IN VARCHAR2, p_pwd IN VARCHAR2, p_string IN VARCHAR2, p_proxy_url IN VARCHAR2 DEFAULT NULL, p_no_domains IN VARCHAR2 DEFAULT NULL ) RETURN BOOLEAN AS v_req UTL_HTTP.REQ; -- HTTP request ID v_resp UTL_HTTP.RESP; -- HTTP response ID v_value VARCHAR2(1024); -- HTTP response data v_status VARCHAR2(160); -- Status of the request v_call VARCHAR2(2000); -- The request URL v_log_value varchar2(4000) := 'status'; BEGIN -- Twitter update url v_call := twit_protocol || twit_host || tweet_url; -- encoded status string v_status := utl_url.escape( url = 'status=' || SUBSTR( short_url.encode_text(p_string) , 1,140)); -- Authenticate via proxy -- Proxy string looks like 'http://username:passw...@proxy.com' -- p_no_domains is a list of domains not to use the proxy for -- These settings override the defaults that are configured at the database level IF p_proxy_url IS NOT NULL THEN Utl_Http.set_proxy ( proxy = p_proxy_url, no_proxy_domains = p_no_domains ); END IF; -- Has to be a POST for status update v_req := UTL_HTTP.BEGIN_REQUEST( url = v_call, method ='POST'); -- Pretend we're a moz browser UTL_HTTP.SET_HEADER( r = v_req, name = 'User-Agent', value = 'Mozilla/4.0'); -- Pretend we're coming from an html form UTL_HTTP.SET_HEADER( r = v_req, name = 'Content-Type', value = 'application/x-www-form-urlencoded'); -- Set the length of the input UTL_HTTP.SET_HEADER( r = v_req, name =
Re: [twitter-dev] Invalid / used nonce
Hi Mounir, In this case I'm fairly confident then that it's the Twitter API implementation of OAuth that's at fault here and these invalid nonce errors are spurious for you. While I hate to suggest working around bugs like this, it might be your best strategy -- if you encounter an invalid nonce error, pause for a few moments, regenerate the request with a different nonce and timestamp, and try again. If you find a case where it's repeatably throwing you this error, for example -- you notice that it only happens for a certain access token, or it only happens when you're using certain characters in the POST body or nonce -- then please bring it to our attention. Scalability projects, among other things, have prevented our engineering team from rolling out a reimplementation of our OAuth back end that will fix aggravating issues like these, among other things. Taylor On Thu, Jul 29, 2010 at 12:43 AM, Mounir Regragui reg.mou...@gmail.comwrote: Hello everybody, Yesterday I was exposing an issue I encoutered. My code was working perfectly, and then I started having a 401 error code with this error message : errorInvalid / used nonce/error when I make API calls. I thought it was solved because yesterday I did some API calls that made it through. However this issue is still here today. Actually, when I make API calls (POST, GET or OAuth requests), sometimes everything works fine, sometimes i have the Invalid / used nonce error. As I told Taylor yesterday, I am sure that that the system time is correct (because when I change it, nothing works), and because as I said, when i try to send a request with the exact same code running, sometimes it fails, sometimes it does not. Here are dumps of the communications I tried to send a tweet, had an error : http://pastebin.com/ur2JYtnM A few seconds later, i run the exact same code and it is valid : http://pastebin.com/6knpLHBW (I will reset my key and secret ^^) I really do not know where the issue comes from, because the code was running flawlessly last week! Any kind of help appreciated. Regards. Mounir Regragui
[twitter-dev] Lists api response is slow
Hi, The response of the below api is very slow. http://api.twitter.com/1/63482118/lists/memberships.xml?cursor=-1 I am not getting whether, is there any problem in the code or problem with the twitter api.But in the logs i able to see many connection timed out exceptions. Regards, Siva
Re: [twitter-dev] Twitter site URL hijacks my sharepoint portal page
On Thu, Jul 29, 2010 at 4:29 AM, Hemanth hemant...@gmail.com wrote: I have a sharepoint portal page with few web parts. One of these web parts is a sharepoint page viewer web part. When I configure the page viewer web part with the URL www.twitter.com and click on OK button, my portal page is hijacked and redirected to twitter home page. I am not able to open and edit my portal page now. As soon as I open my portal page in IE, it redirects to twitter page. I am using IE 8. Twitter employs some frame-busting code to defeat using the site in an IFRAME. This is intended to stop click jacking attacks and may be the root cause of this behavior. -j
[twitter-dev] Re: C# Issues With Special Characters
We meet again online and thank you Taylor!
On Jul 28, 1:28 pm, Taylor Singletary taylorsinglet...@twitter.com
wrote:
Hi Milo,
Though the process of URL encoding for OAuth is usually handled well by URL
encoding libraries, there are times when they don't do the right things as
far as what OAuth is expecting. Things like encoding ~ characters when
they are to remain unencoded, for example.
One thing you want to verify is that you are first URL escaping characters
in POST and query strings correctly -- according to the HTTP spec, rather
than the OAuth spec. Any character that needs URL escaping/% encoding in a
POST body needs to be encoded correctly before you even get to the OAuth
part of calculations. OAuth then prescribes that certain characters be %
encoded -- if your POST body already includes %-encoded characters, this
usually means that for the OAuth signature base string they need to encoded
again.
I have an example on github of nearly every possible UTF-8 character and how
it should be represented at different stages of the request
here:http://github.com/episod/oauth-utf8-character-map
TaylorOn Wed, Jul 28, 2010 at 10:02 AM, MiloCaruso milocar...@gmail.com
wrote:
I am using a built in url encoding method that was included in the
oAuth library. I have seen it referenced many times and it is supposed
to work to url encode.
On Jul 28, 11:00 am, Cameron Kaiser spec...@floodgap.com wrote:
I have searched and searched and not found a good solution to being
able to send special characters in status updates using c#. I can send
status updates that contain most ASCII characters (but not all).
fore example, this would work:
I love twitter
but this will fail:
twitter = love
I am using oAuth and the error I get back is that I am
unauthenticated. This would indicate that my signature is not being
generated correctly. In the one that fails I know that it is the =
that is causing the issue but can't seem to get around this. I get the
same when I use any kind of Unicode character as well.
Does anyone have any ideas or suggestions?
How are you encoding each of those tweets in your OAuth requests?
--
personal:
http://www.cameronkaiser.com/--
Cameron Kaiser * Floodgap Systems *www.floodgap.com*
ckai...@floodgap.com
-- Madness takes its toll. Have exact change ready.
---
Re: [twitter-dev] API HTTP Post statuses/update.xml
Why not? If Twitter states I can send 150 an hour or 1000 a day I should be able to. Not my rules its twitters. So I guess it needs to be written somewhere that 42 per hour is the limit. I am just trying to understand why it appears that I am hitting a limit when i am only doing what twitter apparently allows. The limit I see is possibly the number of messages sent at one time and twitter can't handle it and throws the error I have been receiving. So if that exists than I understand. I just need to know where it is stated. The error message appears to wrong as well since I can still send tweets and it has been a couple hours later. Then I can tell the program manager that this is why we can't send this many messages because of this limit. Maybe what will help is a link stating that there are protections that prevent a certain number of updates/tweets happening at once. Thanks On Thu, Jul 29, 2010 at 3:22 PM, Matt Harris thematthar...@twitter.comwrote: Why are you sending so many Tweets? It sounds like you are being restricted because you are sending too many per hour. The limit of updates per day exists but there are protections to prevent all those updates happening at once. I'm not familiar with the code that handles the measure windows or what the limits are but consider that 1000 tweets per day is approx 42 per hour. Matt On Thu, Jul 29, 2010 at 8:59 AM, Eric Mortensen emort...@gmail.comwrote: For instance, set up the my database to create 200 tweets to post to a account. It ran at 11:49 AM EST. I noticed that 127 tweets were posted and the remaining got kicked with the error response. Not sure if there is a limit of 127 I thought it was 150 limit per hour. This also does not hit the 1000 daily limit since it was only 200 tweets. I will try this again in about 1 hour. I should be able to start tweeting again. Let me know what you think? On Wed, Jul 28, 2010 at 12:19 PM, Eric Mortensen emort...@gmail.comwrote: But, It appears did not hit a 1000 update limit since after an hour and can start updates again. That why it appears to be an hourly limit. Not to mention when this started I did not even have a 1000 tweets total on the account. That is why it can't be the 1000 a day limit. There is should be another reason for this. On Tue, Jul 27, 2010 at 6:56 PM, Matt Harris thematthar...@twitter.comwrote: Hey Eric, That error is the Twitter Limits kicking in saying there are too many status updates being posted by the account. This isn't an API rate limit but a natural limit which applies to all of Twitter. A user may not Twitter more than 1000 updates a day (this includes retweets). More information on these limits are explained on the page I linked to before: http://support.twitter.com/forums/10711/entries/15364 Hope that clarifies the what is happening. Matt On Tue, Jul 27, 2010 at 12:27 PM, Eric Mortensen emort...@gmail.comwrote: Here is a response: ?xml version=1.0 encoding=UTF-8? hash errorUser is over daily status update limit./error request/1/statuses/update.xml/request /hash On Thu, Jul 15, 2010 at 5:41 PM, Matt Harris thematthar...@twitter.com wrote: Hey Eric, Sorry that help article didn't answer your question. Can you provide the actual HTTP request being made and the HTTP response you get back? We're interested in the response body content in particular. Also, remember we disable basic authentication on August 16th so you want to switch to that method of authentication now. Matt On Thu, Jul 15, 2010 at 12:46 PM, Eric Mortensen emort...@gmail.comwrote: Unfortunately not. Do you have anything else that might explain it? On Thu, Jul 15, 2010 at 1:48 PM, Matt Harris thematthar...@twitter.com wrote: Hi Eric, In addition to the API Rate Limits there are general usage limits which apply to all of Twitter, including the website. These limits restrict various actions including the number of updates that can be posted per day. You can read more about Twitter Limits on our help website: http://support.twitter.com/forums/10711/entries/15364 Hope that answers your question, Matt On Thu, Jul 15, 2010 at 10:11 AM, Eric emort...@gmail.com wrote: It appears that I am hitting a 150 post rate limit when I use the statuses/update.xml api to update a twitter account eventhough I should not have this limit doing only a post. Is there a reason why? Here is the code I am using from oracle to do this: create or replace PACKAGE BODY tweet AS twit_host VARCHAR2(255) := 'api.twitter.com'; twit_protocol VARCHAR2(10) := 'http://'; -- URL for status updates tweet_url VARCHAR2(255) := '/1/statuses/update.xml'; FUNCTION tweet ( p_user IN VARCHAR2, p_pwd IN VARCHAR2, p_string IN VARCHAR2, p_proxy_url IN VARCHAR2 DEFAULT NULL, p_no_domains IN VARCHAR2 DEFAULT NULL ) RETURN BOOLEAN AS v_req UTL_HTTP.REQ; -- HTTP request ID
[twitter-dev] Re: API HTTP Post statuses/update.xml
From personal experience the limit is around 150 per hour. That number has been raised/lowered in the past and yes the error message is misleading. It is possible that the 150 per hour is just a hard limit and 1000 per day is a policy limit. Either way if you can technically post 150 an hour that's as many as you're going to be able to do. Unless you present a very very good case to Twitter I don't believe this limit can be raised. I know the link Matt gave has some solid numbers but I wouldn't expect any more detail than that. It's been mentioned in this group before that exact numbers can't be given about some limits. They can change at any time and spammers could use that info to fly under the spam team's radar. On Jul 29, 3:50 pm, Eric Mortensen emort...@gmail.com wrote: Why not? If Twitter states I can send 150 an hour or 1000 a day I should be able to. Not my rules its twitters. So I guess it needs to be written somewhere that 42 per hour is the limit. I am just trying to understand why it appears that I am hitting a limit when i am only doing what twitter apparently allows. The limit I see is possibly the number of messages sent at one time and twitter can't handle it and throws the error I have been receiving. So if that exists than I understand. I just need to know where it is stated. The error message appears to wrong as well since I can still send tweets and it has been a couple hours later. Then I can tell the program manager that this is why we can't send this many messages because of this limit. Maybe what will help is a link stating that there are protections that prevent a certain number of updates/tweets happening at once. Thanks On Thu, Jul 29, 2010 at 3:22 PM, Matt Harris thematthar...@twitter.comwrote: Why are you sending so many Tweets? It sounds like you are being restricted because you are sending too many per hour. The limit of updates per day exists but there are protections to prevent all those updates happening at once. I'm not familiar with the code that handles the measure windows or what the limits are but consider that 1000 tweets per day is approx 42 per hour. Matt On Thu, Jul 29, 2010 at 8:59 AM, Eric Mortensen emort...@gmail.comwrote: For instance, set up the my database to create 200 tweets to post to a account. It ran at 11:49 AM EST. I noticed that 127 tweets were posted and the remaining got kicked with the error response. Not sure if there is a limit of 127 I thought it was 150 limit per hour. This also does not hit the 1000 daily limit since it was only 200 tweets. I will try this again in about 1 hour. I should be able to start tweeting again. Let me know what you think? On Wed, Jul 28, 2010 at 12:19 PM, Eric Mortensen emort...@gmail.comwrote: But, It appears did not hit a 1000 update limit since after an hour and can start updates again. That why it appears to be an hourly limit. Not to mention when this started I did not even have a 1000 tweets total on the account. That is why it can't be the 1000 a day limit. There is should be another reason for this. On Tue, Jul 27, 2010 at 6:56 PM, Matt Harris thematthar...@twitter.comwrote: Hey Eric, That error is the Twitter Limits kicking in saying there are too many status updates being posted by the account. This isn't an API rate limit but a natural limit which applies to all of Twitter. A user may not Twitter more than 1000 updates a day (this includes retweets). More information on these limits are explained on the page I linked to before: http://support.twitter.com/forums/10711/entries/15364 Hope that clarifies the what is happening. Matt On Tue, Jul 27, 2010 at 12:27 PM, Eric Mortensen emort...@gmail.comwrote: Here is a response: ?xml version=1.0 encoding=UTF-8? hash errorUser is over daily status update limit./error request/1/statuses/update.xml/request /hash On Thu, Jul 15, 2010 at 5:41 PM, Matt Harris thematthar...@twitter.com wrote: Hey Eric, Sorry that help article didn't answer your question. Can you provide the actual HTTP request being made and the HTTP response you get back? We're interested in the response body content in particular. Also, remember we disable basic authentication on August 16th so you want to switch to that method of authentication now. Matt On Thu, Jul 15, 2010 at 12:46 PM, Eric Mortensen emort...@gmail.comwrote: Unfortunately not. Do you have anything else that might explain it? On Thu, Jul 15, 2010 at 1:48 PM, Matt Harris thematthar...@twitter.com wrote: Hi Eric, In addition to the API Rate Limits there are general usage limits which apply to all of Twitter, including the website. These limits restrict various actions including the number of updates that can be posted per day. You can read more about Twitter Limits on our help website:
Re: [twitter-dev] API HTTP Post statuses/update.xml
Hey Eric, The 150 limit you refer to relates to GET requests to the API. This is documented on our developer resources site at http://dev.twitter.com/pages/rate-limiting#rest. So information is collected in the same place i'll explain the rate limiting concepts of interest in this message. In our rate limiting document we state: Rate limits are applied to methods that request information with the HTTP GET command. Generally API methods that use HTTP POST to submit data to Twitter are not rate limited, however some methods are being rate limited now. Every method in the API Documentation explains if it is rate limited or not. We go on to say: API methods which are not directly rate limited are still controlled by the daily update and follower limits to promote healthy use and discourage spam. These Twitter Limits are described on our help site. The Twitter Limits links to our help document here: http://support.twitter.com/forums/10711/entries/15364 In that help document we state: Updates: 1,000 per day. The daily update limit is further broken down into smaller limits for semi-hourly intervals. Retweets are counted as updates. and go on to say: These limits include actions from all devices including web, mobile, phone, API, etc. API requests from all third-party applications are tracked against the hourly API limit. People who use multiple third-party applications with their account will therefore reach the API limit more quickly. and ... These limits may be temporarily reduced during periods of heavy site usage. In such cases, we will post an update at the Twitter Status blog. The 150 you refer to, assuming you are using Basic Authentication, is the total number of API rate limited requests an IP is permitted to make per hour. If you use OAuth (which you must do before August 16th) you get 350 API rate limited requests per hour. These requests are not the same ones as those which update your status though. We do say you can send up to 1000 updates (including retweets) in a day. My example of 42 updates per hour was simply dividing 1000/24 to give an indication of how sending 200 updates is a very large number of Tweets to be sending in one hourly interval. As natefanaro has said, exact hourly limits are not published or released to avoid abuse. I hope the explanation above explains rate limiting and how it applies differently to read and write requests. Best, Matt On Thu, Jul 29, 2010 at 12:50 PM, Eric Mortensen emort...@gmail.com wrote: Why not? If Twitter states I can send 150 an hour or 1000 a day I should be able to. Not my rules its twitters. So I guess it needs to be written somewhere that 42 per hour is the limit. I am just trying to understand why it appears that I am hitting a limit when i am only doing what twitter apparently allows. The limit I see is possibly the number of messages sent at one time and twitter can't handle it and throws the error I have been receiving. So if that exists than I understand. I just need to know where it is stated. The error message appears to wrong as well since I can still send tweets and it has been a couple hours later. Then I can tell the program manager that this is why we can't send this many messages because of this limit. Maybe what will help is a link stating that there are protections that prevent a certain number of updates/tweets happening at once. Thanks On Thu, Jul 29, 2010 at 3:22 PM, Matt Harris thematthar...@twitter.comwrote: Why are you sending so many Tweets? It sounds like you are being restricted because you are sending too many per hour. The limit of updates per day exists but there are protections to prevent all those updates happening at once. I'm not familiar with the code that handles the measure windows or what the limits are but consider that 1000 tweets per day is approx 42 per hour. Matt On Thu, Jul 29, 2010 at 8:59 AM, Eric Mortensen emort...@gmail.comwrote: For instance, set up the my database to create 200 tweets to post to a account. It ran at 11:49 AM EST. I noticed that 127 tweets were posted and the remaining got kicked with the error response. Not sure if there is a limit of 127 I thought it was 150 limit per hour. This also does not hit the 1000 daily limit since it was only 200 tweets. I will try this again in about 1 hour. I should be able to start tweeting again. Let me know what you think? On Wed, Jul 28, 2010 at 12:19 PM, Eric Mortensen emort...@gmail.comwrote: But, It appears did not hit a 1000 update limit since after an hour and can start updates again. That why it appears to be an hourly limit. Not to mention when this started I did not even have a 1000 tweets total on the account. That is why it can't be the 1000 a day limit. There is should be another reason for this. On Tue, Jul 27, 2010 at 6:56 PM, Matt Harris thematthar...@twitter.com wrote: Hey Eric, That error is the Twitter Limits kicking in saying there
Re: [twitter-dev] Re: API HTTP Post statuses/update.xml
Thanks. Sounds good. How about this to bake your noodle. Not to be a dead horse. But, looking here http://dev.twitter.com/doc/post/statuses/update it appears as though the statuses/update does not have a rate limit, other than the 1000 limit for the day that applies regardless which i have not hit. Figure it all seems confusing. Still appears that I should not even have an hourly limit with this api only the daily 1000. I guess rules of thumb although I would like to have not gotten rate limited until a higher number than the ~150 because of to much at one time. So the 150 is only for GET not POST. POST is what I do. So it looks like the 1000 is what I do hit and something that governs that limit seems to have a condition that states that if there is a lot of statuses/update within a certain time period flag the account with this rate limit for the next hour or so. On Thu, Jul 29, 2010 at 4:59 PM, natefanaro natefan...@gmail.com wrote: From personal experience the limit is around 150 per hour. That number has been raised/lowered in the past and yes the error message is misleading. It is possible that the 150 per hour is just a hard limit and 1000 per day is a policy limit. Either way if you can technically post 150 an hour that's as many as you're going to be able to do. Unless you present a very very good case to Twitter I don't believe this limit can be raised. I know the link Matt gave has some solid numbers but I wouldn't expect any more detail than that. It's been mentioned in this group before that exact numbers can't be given about some limits. They can change at any time and spammers could use that info to fly under the spam team's radar. On Jul 29, 3:50 pm, Eric Mortensen emort...@gmail.com wrote: Why not? If Twitter states I can send 150 an hour or 1000 a day I should be able to. Not my rules its twitters. So I guess it needs to be written somewhere that 42 per hour is the limit. I am just trying to understand why it appears that I am hitting a limit when i am only doing what twitter apparently allows. The limit I see is possibly the number of messages sent at one time and twitter can't handle it and throws the error I have been receiving. So if that exists than I understand. I just need to know where it is stated. The error message appears to wrong as well since I can still send tweets and it has been a couple hours later. Then I can tell the program manager that this is why we can't send this many messages because of this limit. Maybe what will help is a link stating that there are protections that prevent a certain number of updates/tweets happening at once. Thanks On Thu, Jul 29, 2010 at 3:22 PM, Matt Harris thematthar...@twitter.com wrote: Why are you sending so many Tweets? It sounds like you are being restricted because you are sending too many per hour. The limit of updates per day exists but there are protections to prevent all those updates happening at once. I'm not familiar with the code that handles the measure windows or what the limits are but consider that 1000 tweets per day is approx 42 per hour. Matt On Thu, Jul 29, 2010 at 8:59 AM, Eric Mortensen emort...@gmail.com wrote: For instance, set up the my database to create 200 tweets to post to a account. It ran at 11:49 AM EST. I noticed that 127 tweets were posted and the remaining got kicked with the error response. Not sure if there is a limit of 127 I thought it was 150 limit per hour. This also does not hit the 1000 daily limit since it was only 200 tweets. I will try this again in about 1 hour. I should be able to start tweeting again. Let me know what you think? On Wed, Jul 28, 2010 at 12:19 PM, Eric Mortensen emort...@gmail.com wrote: But, It appears did not hit a 1000 update limit since after an hour and can start updates again. That why it appears to be an hourly limit. Not to mention when this started I did not even have a 1000 tweets total on the account. That is why it can't be the 1000 a day limit. There is should be another reason for this. On Tue, Jul 27, 2010 at 6:56 PM, Matt Harris thematthar...@twitter.comwrote: Hey Eric, That error is the Twitter Limits kicking in saying there are too many status updates being posted by the account. This isn't an API rate limit but a natural limit which applies to all of Twitter. A user may not Twitter more than 1000 updates a day (this includes retweets). More information on these limits are explained on the page I linked to before: http://support.twitter.com/forums/10711/entries/15364 Hope that clarifies the what is happening. Matt On Tue, Jul 27, 2010 at 12:27 PM, Eric Mortensen emort...@gmail.comwrote: Here is a response: ?xml version=1.0 encoding=UTF-8? hash errorUser is over daily status update limit./error
[twitter-dev] Re: Need inputs to implement Twitter app using xAuth
Like to ask if I use Twitter4J xAuth, then I don't need to add Java OAuth lib to Android, right? On Jul 28, 11:20 pm, Sambath Chandran sambat...@gmail.com wrote: But I just want to know one thing. How much difficult to implement making xAuth call in Java without any libraries? Thanks, Sambath On Thu, Jul 29, 2010 at 11:29 AM, Sambath Chandran sambat...@gmail.comwrote: Thanks a lot Ernandes and Abraham. Regards, Sambath On Wed, Jul 28, 2010 at 9:33 PM, Abraham Williams 4bra...@gmail.comwrote: Twitter4j supports xAuth:http://goo.gl/ZmM2 Abraham - Abraham Williams | Hacker Advocate |http://abrah.am @abraham |http://projects.abrah.am|http://blog.abrah.am This email is: [ ] shareable [x] ask first [ ] private. On Wed, Jul 28, 2010 at 02:29, Sambath Chandran sambat...@gmail.comwrote: All, I am implementing an application to receive and the latest tweet from the twitter. After refering to twitter website, I concluded to use xAuth authentication for my development. Can anybody let me know is there any ready to use java library for xAuth? Basially I want to know to how to make xAuth work with Java. Thanks, Sambath
[twitter-dev] Re: Searching for tweets by place_id
Hi!! I'm developping http://metaki.com (Alpha version) but I have troubles with geocode lat, lon and tweets... You may see my last question with no answer :b http://groups.google.com/group/twitter-development-talk/browse_thread/thread/fb9e284bed19d31a Any help will be appreciate ;) Daniel On 29 jul, 00:56, Matt Harris thematthar...@twitter.com wrote: Hi Benn, In search you can use the parameter place:place_id to restrict results to public Tweets from a known place. You will need to know the place_id that we use first. For example, to see all Tweets from Twitter HQ (place_id = 247f43d441defc03) I would make this request: curlhttp://search.twitter.com/search.json?q=place%3A247f43d441defc03 Best, Matt On Wed, Jul 28, 2010 at 9:52 PM, benn bno...@gmail.com wrote: Is there a way to search for tweets by place_id? Or can we only use a geo search with a very small radiues? -- Matt Harris Developer Advocate, Twitterhttp://twitter.com/themattharris
