Ahmen Paul, glad I'm not the only one that shares you sentiments. I had previously emailed Ryan something similar. What surprises me is how little they care to share with the developers who made thier service what it is.

I also can't fathom how many other developers have yet to tell Twitter this and act like this is new. This DDoS has gone on for 2 days and counting and 29 hours for them to say something ro us developers is really unprofessional.


On Aug 7, 2009, at 7:16 PM, Paul Kinlan <paul.kin...@gmail.com> wrote:

Hi Chad,

I think we all appreciate the pressure you are under and the flak that you are taking for events outside your control, and we all wish we could help more.

But for an open communications company that is postioning itself as the future platform for messaging - there has been so little communication and feedback to the developers in your community that it is simply shocking.

Little things such as statements that we as developers can use to pass to our users with regards to issues currently affecting the service would help immensly. I have spent my Friday night responding to over 150 emails asking why twollo is down - all I can say is I think it is related to current events and Twitter aren't telling us anything. This doesn't inspire confidence in users of my service and of twitters'

The situation is reminisent to the oauth situation the other month. Next to no communication at all.

We all love your service and want to build on top of it and help it grow and our own services too.

From my own, probably selfish point of view the app engine is completly blocked at the moment and as far as I can tell we have no indication if it is up yet - I can't tell correctly as I am in bed writing this.


On 7 Aug 2009, at 21:09, Chad Etzel <c...@twitter.com> wrote:

Hello all,

We have been flooded with emails asking why whitelisted IPs have been
reduced from the 20k rate-limit down to the normal 150 rate-limit.
This is a known issue and we are working as hard as we can on
resolving it. We thank you for your patience as we are dealing with
everything going on with the DDoS.


Reply via email to