[twitter-dev] API requests take 20-30 seconds
Hi, I noticed that api requests from my server (rate limit is 2) take up to 20-30 seconds. The rate limit status says that there are 2 hits remaining, but that request itself also takes 30s. DNS resolving & pinging twitter.com works great and as fast as usual. I mailed to a...@twitter.com two days ago but no response yet :( Thanks, Niklas Hellenbart http://twunfollow.com/
[twitter-dev] Wrong follower list
Hi folks, I recognized that I get follower lists (http://twitter.com/followers/ ids.xml) for a certain user (twitter id: 61899438) that are not correct. From time to time the id 80514185 appears in it (that's wrong, 80514185 isn't following this user) and the ids 14420915, 19360476, 19675319, 21239364, 26772579 who are following are not in the list. Every time I get a wrong list exactly the same ids are missing/too much. Cheers, Niklas (twunfollow.com)
[twitter-dev] "Unauthorized: Incorrect signature" for protected users
Hi folks, every time requesting the follower or friends id-list (api call followers/ids & friends/ids) or calling account/verify_credentials with valid oauth credentials I get an 401 error "Unauthorized: Incorrect signature". Methods like statuses/update using the same creden are fine. I tried Zend_Oauth in several versions from a whitelisted client but only requests with users that are not protected are successful. Has anybody similar problems? ps: the system time is correct Cheers, Niklas -- 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: "Unauthorized: Incorrect signature" for protected users
Thanks very much! Checking the base string showed that a POST request was made instead of GET, shame on me :-D On 15 Dez., 01:57, Matt Harris wrote: > Ni Niklas, > > In most of these cases the issue is to do with character encoding, > specifically commas not being encoded as %2C properly. Could you share your > basestring so we can check this. > > Best, > @themattharris > Developer Advocate, Twitterhttp://twitter.com/themattharris > > On Tue, Dec 14, 2010 at 3:48 PM, Niklas Hellenbart < > > niklas.hellenb...@gmail.com> wrote: > > Hi folks, > > > every time requesting the follower or friends id-list (api call > > followers/ids & friends/ids) or calling account/verify_credentials > > with valid oauth credentials I get an 401 error "Unauthorized: > > Incorrect signature". Methods like statuses/update using the same > > creden are fine. I tried Zend_Oauth in several versions from a > > whitelisted client but only requests with users that are not protected > > are successful. > > Has anybody similar problems? > > > ps: the system time is correct > > > Cheers, > > Niklas > > > -- > > 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: Rate Limiting
I've got the same problem, according to the api response the reset time is in the past. On 6 Jul., 14:20, artesea wrote: > I'm being locked out on my account using the API and I'm seeing > reports from others. At the moment making a request > tohttp://api.twitter.com/version/account/rate_limit_status.jsoncomes > back saying I have 8 calls left and it will be reset at 07:54, but the > time is currently 13:18! > The time for the reset has been the same since at least 8am.
[twitter-dev] Re: Rate Limiting
For my whitelisted client everything is fine again, limit is up at 20k again :) On Jul 7, 12:40 pm, artesea wrote: > And again I'm locked out. 400 is saying "Rate limit exceeded. Clients > may not make more than 150 requests per hour.", > however rate_limit_status is saying "You have 145 api calls left until > 12:20 when it will be reset to 150." (local time 11:39) > > On Jul 6, 10:59 pm, Rich wrote: > > > Yep I'm now locked out of my own account with this issue > > > On Jul 6, 10:38 pm, Matt Harris wrote: > > > > We are aware rate limits are being reported incorrectly. We are tracking > > > the > > > issue on the API > > > tracker:http://code.google.com/p/twitter-api/issues/detail?id=1728 > > > > Matt > > > > On Tue, Jul 6, 2010 at 10:10 AM, Johnson wrote: > > > > I want to know what's the metrics of this dynamic logout. > > > > I have several twitter account/twitter development accounts. > > > > It started around 1am PST, one of my account keep getting 400. I woke > > > > up this morning, that only account is still getting 400. > > > > I tried a different pair comsumer key/token using twurl, it works. > > > > I tried on mobile, Echolfon, failed, but twitbird goes thru. > > > > Obviously the web works! > > > > What other experiments do u want me to run? > > > > Are twitter giving favor on specific accounts? > > > > > On Jul 6, 9:57 am, Pascal Jürgens > > > > wrote: > > > > > Just a sidenote: This can be coincidental. Unless you try several > > > > > dozen > > > > times with each client, no valid inference can be drawn from the tests. > > > > > > Pascal > > > > > On Jul 6, 2010, at 18:46 , Johnson wrote: > > > > > > > I notice that the rate limit is application specific. I've tried a > > > > > > few > > > > > > clients, some of them goes thru, some don't. > > > > -- > > > > Matt Harris > > > Developer Advocate, Twitterhttp://twitter.com/themattharris
