[twitter-dev] Having problems after OAuth login
We're experiencing problems with Twitter's OAuth login. After the "Redirecting you back to your application..." page, we get a 500 error: "Internal Server Error The server encountered an internal error or misconfiguration and was unable to complete your request. Please contact the server administrator, y...@example.com and inform them of the time the error occurred, and anything you might have done that may have caused the error. More information about this error may be available in the server error log." Is there anything wrong with Twitter's services at the moment? This started around 12-14 hours prior to this mail (10pm Tokyo time). The API status page indicates nothing is wrong though.
[twitter-dev] Re: Trying to access Twitter API via proxies, running into trouble with OAuth
I guess I might as well beg for those error messages while I'm at it. If someone might be so kind as to post all the possible 403 messages, it'll save me 7 hours of work (and possibly a suspended twitter account) trying to get those messages. On May 23, 6:06 pm, akaii wrote: > I'm having no problems with sending an update directly > viahttps://api.twitter.com/, but the app (for the Iphone, I'm using > NSURLConnections) I'm working is supposed to allow the user to select > a preferred proxy > (e.g.https://twitter-proxy.appspot.com/api/orhttps://nest.onedd.net/api/), > and I keep getting a 401 error (Failed > to validate oauth signature and token) whenever I try to get an access > token via these proxies. Even though I send my POST request to the > proxy, I am still using the direct url for the api (https:// > api.twitter.com/[rest api path]) in the base string. > > Is there anything else that I need to consider when using a proxy to > access the API? Should anything in the authorization header change, > for example? Or the base string? > > On a somewhat unrelated note... > > What are the possible causes of error 403, and how do you distinguish > between them? Is the only way to differentiate an error due to > exceeding the status update limit for an hour (150 per hour) vs for a > day (1000 per day) by checking the string reply returned in the > response? > > Is there any way for me to simulate a status update limit error > without going through the motions of actually sending 150/1000 tweets?
[twitter-dev] statuses/update 403 error
There seem to be a variety of possible causes for getting an 403 error in responses to a calling statuses/update... you could be duplicating a tweet or hitting the update limit for an hour or for the day. How can you tell which one these errors actually occurred? The only 2 ways I can think of is to try and parse the error message, or to follow up the request with a query about whether you've hit any limits. The problem with checking the error message is that: 1) It's fragile. If the twitter dev team decides to change the error msg, the solution breaks. 2) I'd have to know the error message first... and the specific error messages for hitting the update limit don't seem to be documented anywhere that I can see. Not in the wiki for sure. Which means that I'd have to hit the limit to find out directly what the messages are... not exactly practical, especially for the 1000 per day limit. It would take me a minimum of 7 hours to hit that limit, since I'd get capped by the hourly limit first. The problem with a follow-up request is that: I can't seem to find a way to get current remaining tweets available to the user before hitting the status update limit in the api. There's one for rate limiting: account/rate_limit_status But where's the corresponding api for the status update limits? What should I do about this? Is there some third, better way to find out which specific error resulted from the update attempt?
[twitter-dev] Trying to access Twitter API via proxies, running into trouble with OAuth
I'm having no problems with sending an update directly via https://api.twitter.com/, but the app (for the Iphone, I'm using NSURLConnections) I'm working is supposed to allow the user to select a preferred proxy (e.g. https://twitter-proxy.appspot.com/api/ or https://nest.onedd.net/api/), and I keep getting a 401 error (Failed to validate oauth signature and token) whenever I try to get an access token via these proxies. Even though I send my POST request to the proxy, I am still using the direct url for the api (https:// api.twitter.com/[rest api path]) in the base string. Is there anything else that I need to consider when using a proxy to access the API? Should anything in the authorization header change, for example? Or the base string? On a somewhat unrelated note... What are the possible causes of error 403, and how do you distinguish between them? Is the only way to differentiate an error due to exceeding the status update limit for an hour (150 per hour) vs for a day (1000 per day) by checking the string reply returned in the response? Is there any way for me to simulate a status update limit error without going through the motions of actually sending 150/1000 tweets?
[twitter-dev] Re: About update limits
Pardon, I'd just like to follow-up on my question in case it was missed. I'm fine with not knowing what the precise sub-limits are, but can I at least ask why the specifics aren't made public? I just need to be able to respond with something in case our client asks... It'll be easier for them to swallow the idea that it's a twitter policy if we can explain the reason why the policy exists. On Apr 29, 4:45 pm, Brian Sutorius wrote: > To clarify, statuses/update is not affected by rate-limit whitelisting > as it's a POST call and we don't maintain a separate whitelist for > boosting the daily tweet limit above 1000. While we do not give out > the specifics around the "sub-limits," they *are* administered on a > per-account basis and if you stay around your approximation of 20 > tweets per half-hour you should be fine. > > Brian Sutorius > > On Apr 29, 6:07 am, Raffi Krikorian wrote: > > > the numbers are roughly broken up over the day. and the limit applies to an > > account. > > > and yes - there is a whitelisting for status/updates -- please e-mail > > a...@twitter to ask for it. > > > On Thu, Apr 29, 2010 at 5:26 AM, akaii wrote: > > > This is what the FAQ has to say about status update limits: > > > > 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. > > > > I'm a little unclear as to what exactly is meant by "further broken > > > down into smaller limits for semi-hourly intervals". Is the 1000 per > > > day limit divided evenly between the 48 half hours each day (around 20 > > > or so tweets per half an hour?). > > > > Also, I'm assuming this limit applies to each unique account? > > > > Is this limit absolutely fixed? Or is there some equivalent to > > > "whitelisting" for status/update limits as well? > > > > Thanks... > > > -- > > Raffi Krikorian > > Twitter Platform Teamhttp://twitter.com/raffi
[twitter-dev] Re: About update limits
Thanks for all the replies so far. Just to clarify, we probably won't be hitting the limit, but I need to be able to explain the existence of the limit to our clients, and part of that includes being able to explain to them the details behind how the limit is applied. Personally, I'm perfectly satisfied with not knowing what the precise sub-limit is, but to be on the safe side, can I at least ask why the info isn't publicly available? For example, could it be because the limit isn't actually a fixed rate but a dynamic one subject to change depending on the circumstances? I need to know just in case I'm asked why I can't get these details. Can I ask further details about status/update limit whitelisting here, or should I mail a...@twitter directly about it? I assume that apps are added to the whitelist on some case-to-case combination of both the needs of the app, and the popularity/usage of the app? Am I correct to assume that new apps are generally not added to the whitelist until they've build up a substantial user-base? On Apr 30, 12:14 am, Nigel Legg wrote: > Large recruitment consultancies seem to get very close to that limit, > tweeting out details of vacancies. Can be quite useful to follow for a short > while. > > On 30 April 2010 01:40, Dewald Pretorius wrote: > > > I can't think of a use or requirement that would need more than 1,000 > > tweets per day. > > > Unless you're promoting teeth whitening affiliate links that > > absolutely must be sent at a rate of one tweet every 30 seconds, > > because we all know how quickly the teeth of some followers turn > > yellow. > > > On Apr 29, 8:45 pm, Brian Sutorius wrote: > > > To clarify, statuses/update is not affected by rate-limit whitelisting > > > as it's a POST call and we don't maintain a separate whitelist for > > > boosting the daily tweet limit above 1000. While we do not give out > > > the specifics around the "sub-limits," they *are* administered on a > > > per-account basis and if you stay around your approximation of 20 > > > tweets per half-hour you should be fine. > > > > Brian Sutorius > > > > On Apr 29, 6:07 am, Raffi Krikorian wrote: > > > > > the numbers are roughly broken up over the day. and the limit applies > > to an > > > > account. > > > > > and yes - there is a whitelisting for status/updates -- please e-mail > > > > a...@twitter to ask for it. > > > > > On Thu, Apr 29, 2010 at 5:26 AM, akaii wrote: > > > > > This is what the FAQ has to say about status update limits: > > > > > > 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. > > > > > > I'm a little unclear as to what exactly is meant by "further broken > > > > > down into smaller limits for semi-hourly intervals". Is the 1000 per > > > > > day limit divided evenly between the 48 half hours each day (around > > 20 > > > > > or so tweets per half an hour?). > > > > > > Also, I'm assuming this limit applies to each unique account? > > > > > > Is this limit absolutely fixed? Or is there some equivalent to > > > > > "whitelisting" for status/update limits as well? > > > > > > Thanks... > > > > > -- > > > > Raffi Krikorian > > > > Twitter Platform Teamhttp://twitter.com/raffi
[twitter-dev] About update limits
This is what the FAQ has to say about status update limits: 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. I'm a little unclear as to what exactly is meant by "further broken down into smaller limits for semi-hourly intervals". Is the 1000 per day limit divided evenly between the 48 half hours each day (around 20 or so tweets per half an hour?). Also, I'm assuming this limit applies to each unique account? Is this limit absolutely fixed? Or is there some equivalent to "whitelisting" for status/update limits as well? Thanks...
