I think the twitter service is still down due to the DDOS attacks. Its
not allowing to register new applications. I am trying to make my
application work for the past 2 days now and without any success.
Fails during authentication. Some issue with the oauth module.


On Aug 10, 3:23 am, Eric <eric.gaygesh...@sbcglobal.net> wrote:
> Any idea when the limit will be increased to 20,000? I'm sure myself
> as well as other sites are suffering a bit because of the limitation
> of API calls.
>
> On Aug 7, 4:54 pm, Chad Etzel <c...@twitter.com> wrote:
>
>
>
> > Hi Paul (and everyone),
>
> > Thanks for your appreciation and your comments.
>
> > On a personal note: I started my support role this week, which is
> > supposed to be part-time. Well, as you can imagine that went out the
> > window. I have all but abandoned my other work-related
> > responsibilities for the past two days in order to help with the API
> > communications with Twitter.
>
> > As you noted, when your site goes down you get a lot of email.
> > Likewise, there is an amazing flood of emails coming into Twitter (not
> > counting this dev-list) all asking similar questions and demanding
> > answers. This has created a DDoS on the API Support team's time, in a
> > manner of speaking :)
>
> > I think Ryan did a good job communicating what we do and don't know in
> > his email this morning, and we have tried to communicate things when
> > we can.
>
> > During the course of this DDoS, the attackers have changed tactics and
> > so our Ops team have had to change their tactics in defense of the
> > attack. This is happening so often that we don't want to communicate
> > something out to the community that will be nullified by the next
> > move. Our opinion is, that would create more thrashing and frustration
> > from the community. We have been trying to communicate workarounds and
> > information that has become permanent or stable as a way to deal with
> > the attacks.
>
> > As Peter noted, we have nothing new to share at the moment, except to
> > say that this thing is still ongoing, and we're having to ride it out
> > with you guys. We certainly know that the 3rd party apps make Twitter
> > great (I've had to tweak code on my personal apps as well), and we
> > don't want to alienate you.  Unfortunately we don't have an ETA on
> > resolving all of the problems because we don't have an ETA on the DDoS
> > :)
>
> > We will continue to post updates as we can.  Again, we know this sucks
> > for you guys, and we really do appreciate everyone being patient with
> > us.
>
> > Thanks,
> > -Chad
>
> > On Fri, 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 theoauthsituation 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.
>
> > > Paul
>
> > > 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.
>
> > >> Thanks,
> > >> -Chad- Hide quoted text -
>
> - Show quoted text -

Reply via email to