[twitter-dev] Re: NO API CONNECTION, BUT STILL FULLY BLOCKED
Yea, and we all threatened to go to Pownce. That didn't go so well (seeing that Pownce is now dead) dave On Aug 9, 3:05 pm, Dossy Shiobara wrote: > On 8/9/09 1:53 PM, David Fisher wrote: > > > Anyone that was around in 2006/2007 knows that Twitter was excessively > > unstable then, and people didn't whine/complain as much. > > Sure we did, there were just fewer of us at the time. Weren't you > around in 2006/2007? Perhaps you have a short memory retention. > > -- > Dossy Shiobara | do...@panoptic.com |http://dossy.org/ > Panoptic Computer Network |http://panoptic.com/ > "He realized the fastest way to change is to laugh at your own > folly -- then you can let go and quickly move on." (p. 70)
[twitter-dev] Re: NO API CONNECTION, BUT STILL FULLY BLOCKED
On 8/9/09 1:53 PM, David Fisher wrote: Anyone that was around in 2006/2007 knows that Twitter was excessively unstable then, and people didn't whine/complain as much. Sure we did, there were just fewer of us at the time. Weren't you around in 2006/2007? Perhaps you have a short memory retention. -- Dossy Shiobara | do...@panoptic.com | http://dossy.org/ Panoptic Computer Network | http://panoptic.com/ "He realized the fastest way to change is to laugh at your own folly -- then you can let go and quickly move on." (p. 70)
[twitter-dev] Re: NO API CONNECTION, BUT STILL FULLY BLOCKED
They haven't overreacted. If you think you can do better, then apply for a job with them. Have you tried your account from multiple IP blocks? They have faced a crushing attack. They are working on it and they have worked hard to communicate with us the status of things. Anyone that was around in 2006/2007 knows that Twitter was excessively unstable then, and people didn't whine/complain as much. They've gotten better but they don't have the capacity to serve traffic and handle a DDoS attack at the same time. Your ticket will be dealt with and they are working to resolve overall issues before they address specific people. dave fisher/@tibbon webecologyproject.org On Aug 9, 10:30 am, chuckblakeman wrote: > For what it's worth. I am a Twitter use who does not use TweetDeck, > TweetLater, or any other 3rd party software doing API calls to > Twitter. I use Twitter directly without any connection to other API > calls. > > Since Wednesday I have not been able to use any Twitter functions and > as of Friday evening I was no longer even able to sign in and watch > the Tweet stream helplessly. Login function has been disabled since > then. > > So they are not just blocking majore APIs - for some reason my direct > Twitter account has been blocked by Twitter as well. I've sent two > tickets and one email to support over the last three days with no > response. > > They have clearly over-reacted to this issue.
