[twitter-dev] Re: XAuth 401 error

[J.D.]

For desktop apps using oAuth, the timestamp issue causing 401 errors
is a big problem. People's desktops have all sorts of crazy times set
on them. This means now every application that uses Twitter oAuth
needs to have code written to sync/modify its time with Twitter's.
It's a pain.

-- 
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?hl=en

[twitter-dev] Re: XAuth 401 error

[J.D.]

Sure. I implemented it and it was not hard, just one more thing to
deal with, that's all.  :)

-- 
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?hl=en

[twitter-dev] Re: verify_credentials limit

[J.D.]

On Aug 7, 2:07 am, kosmo76 iiiso...@gmail.com wrote:
 Try like this http://twitter.com/users/show.xml;

I don't understand how that is is relevant, I could do that whether I
was authenticated or not.

[twitter-dev] verify_credentials limit

[J.D.]

Any news as to why a call with valid credentials does not reset this
limit? I've optimized my application to only call this API once each
time it is used, but people can still run in to the 15 calls per hour
limit. Is there really a security issue with resetting it after a
valid call?

[twitter-dev] Re: verify_credentials limit

[J.D.]

I also wanted to mention this limit makes it incredibly frustrating
when testing the application. I have to have a special condition so
the application doesn't call the api when running tests, or I will
quite easily reach the 15 call limit and then have to wait a full hour
before continuing.

[twitter-dev] Too many requests in this time period. Try again later.

[J.D.]

Today I started getting this error, even only after a handful of API
calls. Is this a new change? I've tested with two accounts, one that
is whitelisted and another that is not. I'm getting this from both
accounts after only 30 or 40 calls.

403  Too many requests in this time period. Try again later.

[twitter-dev] Re: Too many requests in this time period. Try again later.

[J.D.]

Hi Kevin,

It's downloading info for a social graph (all the users followers), so
fairly quickly. Do I need to add a sleep between calls to statuses/
followers?

J.D.

[twitter-dev] Re: Too many requests in this time period. Try again later.

[J.D.]

WRT the sleep, I've never had to in the past. It just started failing.

[twitter-dev] Re: Too many requests in this time period. Try again later.

[J.D.]

 are you calling the verify credentials call? they started limiting
 that call to 15 requests per hour due to an attack vulnerability.

Ah yes, as a matter of fact I am. I was calling it each time my
application started, I'll refactor that. Thanks!

J.D.

[twitter-dev] Re: Too many requests in this time period. Try again later.

[J.D.]

I can see why this api should be limited, but it seems (from the
outside, I'm sure maybe there are other reasons) like if the
credentials are correct, it shouldn't count against the limit. Only
limit if the attempts are bad (someone is fishing).

J.D.

[twitter-dev] Re: Failed API returning over capacity HTML page content

[J.D.]

On Jul 15, 9:09 am, Nick Arnett nick.arn...@gmail.com wrote:
 My code waits a few seconds and tries again if the JSON parse
 fails.  A bunch of fails in a row and it gives up.

Thanks. I have similar code around the web calls, but had not put it
around the json parse yet.

[twitter-dev] Re: Failed API returning over capacity HTML page content

[J.D.]

 Whether talking to the Twitter API or any other API on the web, always check
 the response code before attempting to do any processing of the response
 body. Proceed only if you got a 200 (or the response code you expected for
 that particular operation). Many things can go wrong in the process of
 making an HTTP request between your computer and our servers.

I'm fairly certain I did get a 200, but I got html instead of the json
I requested.

[twitter-dev] Failed API returning over capacity HTML page content

[J.D.]

I'm getting a bunch of exceptions logged tonight where the API is
returning the actual html content for the Over capacity web page,
instead of an error code. That isn't expected, is it? I would expect
one of the 500 error codes.

J.D.

[twitter-dev] Re: rate_limit_status called from .NET WebClient class

[J.D.]

Cool, thanks James.

[twitter-dev] rate_limit_status called from .NET WebClient class

[J.D.]

I must be doing something wrong. If I call rate_limit_status with
CURL, I can see 2 different counts, depending on if I pass my
credentials or not. If I do the same thing from a .NET application, I
always get the non-authenticated (IP address limit) results.

I know setting the WebClient credentials this way works, as I call
other twitter API's after authenticating, plus I can call
verify_credentials this way and it works.

Can anyone see what I'm missing or screwing up?

  public void TestLimitInfo()
  {
 WebClient wc = new WebClient();
 wc.Credentials = new NetworkCredential( myuser, mypass );

 string data = wc.DownloadString( http://twitter.com/account/
rate_limit_status.json );
 MessageBox.Show( data );

  }  // GetLimitInfo

TIA,
J.D.