And I am still having issues. I still can't post status updates from my
application, even though this worked fine on Sunday night.
Ryan
On Tue, Oct 13, 2009 at 2:24 PM, rivv wrote:
>
> My application is no longer able to Authorize Twitter accounts, even
> though I was able too on october 9th.
My application is no longer able to Authorize Twitter accounts, even
though I was able too on october 9th. I am assuming it is because of
this as well, so take from that what you will.
On Oct 12, 7:47 pm, eclipsed4utoo wrote:
> Are people still having issues posting status updates from third pa
Are people still having issues posting status updates from third party
applications? I haven't been able to post all day. Still can't post
now.
There isn't an update on the Twitter status page. I didn't know if
that was because it wasn't fixed yet, or because they just haven't
updated it post
On Mon, Oct 12, 2009 at 4:42 PM, John Kalucki wrote:
>
> We need to get better at
> the status blog, but it's rare that we aren't responding to a site-
> wide issue within moments.
>
> -John Kalucki
> http://twitter.com/jkalucki
> Services, Twitter Inc.
Any idea when that might happen? I've been
Thanks for your offer of help. When additional data from clients would
help, we usually post here and appreciate whatever reports we can get.
We collect statistics throughout the system, so there is a very
complete view of what's going on. In the end, we're usually sorting
through too much inform
Now the website seems fine. However, trying to post a status update from my
desktop client (using OAuth, don't know if that makes a difference), it just
hangs when sending the request. Status updates from twitter.com seem to
work just fine.
Ryan
On Mon, Oct 12, 2009 at 4:19 PM, bear wrote:
>
>
John,
I'm going to be in San Fran the week of Nov 5th, I would love to meet
with the Twitter Ops team on how we (we being Seesmic and possibly
other large consumers of Twitter) can help you guys respond faster to
these issues.
If there was someone (or thing) to poke I could have given you guys
e
We updated the status blog: http://status.twitter.com.
On Oct 12, 12:44 pm, Dewald Pretorius wrote:
> It's now even on Mashable:
>
> http://mashable.com/2009/10/12/http-server-error-twitter/
>
> On Oct 12, 4:36 pm, ryan alford wrote:
>
> > Thanks Dewalt. I was beginning to think something was
It's now even on Mashable:
http://mashable.com/2009/10/12/http-server-error-twitter/
On Oct 12, 4:36 pm, ryan alford wrote:
> Thanks Dewalt. I was beginning to think something was wrong with my app.
> Atleast I know I am not the only one seeing these slow downs.
> Ryan
>
> On Mon, Oct 12, 20
Thanks Dewalt. I was beginning to think something was wrong with my app.
Atleast I know I am not the only one seeing these slow downs.
Ryan
On Mon, Oct 12, 2009 at 3:26 PM, Dewald Pretorius wrote:
>
> Their system must just be overloaded at the moment.
>
> I have been seeing response times in
Their system must just be overloaded at the moment.
I have been seeing response times in the 10+ seconds region per simple
API call since earlier this morning.
Dewald
On Oct 12, 3:56 pm, RTuosto wrote:
> I'm getting this error when looking athttp://www.twitter.comas well
> as user pages. What
11 matches
Mail list logo
