What about those using the regular API, via both Basic Auth and OAuth,
is there anything at all we can do to stop getting endless 408's ?
I'm guessing that since even twitter.com itself is still very
"inconsistent", for lack of a better word, theres probably nothing
much more we can do than just wait.
On Aug 7, 7:22 am, Shannon Clark <shannon.cl...@gmail.com> wrote:
> Not specific to only developers but at the momenthttp://search.twitter.com
> is not loading on my iPhone though search via an iPhone app
> (twitterfon is what I tried) is working.
> Sent from my iPhone
> On Aug 6, 2009, at 2:19 PM, John Kalucki <jkalu...@gmail.com> wrote:
> > Some users were unable to connect to the Streaming API at various
> > times during the DDoS. This has been fixed for the majority of
> > Streaming API clients. The connection count is now approaching
> > yesterday's count.
> > If your Streaming API client is still receiving 409 redirects,
> > connection timeouts, or any other issue that started today, please
> > contact me with your account name and IP address, and I'll work to
> > resolve the issue.
> > -John Kalucki
> > Services, Twitter Inc.