Platform Status Update, Tuesday 2:00pm PST

[Ryan Sarver]

Thanks to everyone who sent in detailed issue reports we have been
able to tune the system to recognize the traffic better and things
seem to be running well. We will continue to closely monitor the
system and tune as needed. Your detailed reports are very important in
helping us teach the system what your request patterns look like.

One thing we have noticed and is generally a good coding practice -
make sure that if you open a connection for a request that you close
that connection before exiting out or you may run the risk of looking
like malicious traffic.

Please continue to operate your systems as you normally would and
notify us when you have issues with the detailed information, which
I've include here for the sake of consistency:

1. The IP of the machine making requests to the Twitter API. If you're
behind NAT, please be sure to send us your *external* IP.
2. The IP address of the machine you're contacting in the Twitter
cluster. You can find this on UNIX machines via the "host" or
"nslookup" commands, and on Windows machines via the "nslookup"
command.
3. The Twitter API URL (method) you're requesting and any other
details about the request (GET vs. POST, parameters, headers, etc.).
4. Your host operating system, browser (including version), relevant
cookies, and any other pertinent information about your environment.
5. What kind of network connection you have and from which provider,
and what kind of network connectivity devices you're using.

Thanks again for all of your support and let us know if you continue
to see any issues.

Best, Ryan
@rsarver

[djc8080]

We reported/documented inconsistent, incorrect responses on statuses/
followers, statuses/friends. After a few reboots, to correct
connections that have been left open, all the accounts are working.
We'll be monitoring for any additional problems. Thanks for the fast
response - after our report today.

Hopefully, the problems have been resolved for other developers as
well.

[djc8080]

Oops. spoke too soon. Still eradic problems - same symptoms. Incorrect
rate_limit response on statuses/followers when ..ids calls work
perfectly on the same account.

[deepikagupta]

Hi,

I am facing problem while Deleting any Tweet from my application.
http://www.twitter.com/statuses/destroy/id.xml always gives me 400
status code but also deletes the tweet. So in my application it is
caught as an exception only and error message is shown to user even
though tweet is deleted.
I am facing this issue only while deleting tweets and mentions. HTTP
request for delete seems to be working fine with direct messages and
favorites.

Please Help me!!!

[lepah]

Hi, I'm having the same issue form my iphone twitter app, I'm deleting
status via http://www.twitter.com/statuses/destroy/id.xml and I'm
always getting a status 400 error which my app displays to the user
even though the status was deleted.

is this a permanent change to the API??

thanks,
Matt

[srikanth reddy]

Its been more than 2 days . The problem is not only with API.
I tried deleting a tweet from web but all i could see is a flashing dot . It is not removing the entry.
If i refresh manually then the tweet gets deleted.

Srikanth