Part of it is DDOS response, part of it is API issues... as one of the updates most recently noted with the "known issues" list.
On Aug 8, 11:42 pm, Bill Kocik <bko...@gmail.com> wrote: > On Aug 9, 2:28 am, chinaski007 <chinaski...@gmail.com> wrote: > > > You're wrong. > > > If you check the tweets of the other main Twitter developers, you will > > see that they are doing sushi, rock concerts, weddings, watching > > movies on Saturday afternoon, etc. And while "getting married" is > > certainly a legitimate excuse, some of the other activities, during > > this major upheaval, are certainly questionable! > > Oh...I get it, you think that the developers are the right people to > handle a DDoS attack. I'm afraid I have some bad news for you: you're > wrong. > > And because not *all* the developers are sweating it out at Twitter > HQ, that means no one's working on it. I can't argue with that logic. > Seriously, I can't.
