Noticing the downtime with oAuth now...
On Aug 15, 8:05 pm, Ritvvij <ritvi...@gmail.com> wrote: > Phew! thanks a lot.. i spent whole day thinking where I messed up the > code. :-) > > On Aug 15, 10:03 pm, goodtest <goodtest...@gmail.com> wrote: > > > > > Same here. New users can't authorize. After pressing 'Approve', it > > takes for ever and ends up in a blank-page > > withhttp://twitter.com/oauth/authorize > > url. > > > On Aug 15, 6:51 pm, Ritvvij <ritvi...@gmail.com> wrote: > > > > Hi could this be the reason why? > > > > On clicking authenticate user, my application moves to twitter. When > > > the user presses APPROVE, it waits like forever and then goes to a > > > blank page with url as "http://twitter.com/oauth/authorize"; instead > > > of my call back URL. ?? > > > > Please advise. > > > Till last night my app was working, and since today morning, even > > > right now, its down. :-( > > > > On Aug 15, 8:21 pm, Sean Callahan <seancalla...@gmail.com> wrote: > > > > > Thanks for the reply Doug. Any new news? Still not able to login > > > > using basic auth on TweetPhoto. Do you have any ETA as to when we'll > > > > be restored? > > > > > On Aug 15, 1:29 pm, Doug Williams <d...@twitter.com> wrote: > > > > > > Sean,At this time we are monitoring the situation and containing > > > > > issues as > > > > > we see them. Let's hold off on restoration requests until things > > > > > stabilize. > > > > > > Thanks, > > > > > Doug > > > > > > On Sat, Aug 15, 2009 at 1:17 PM, Sean Callahan > > > > > <seancalla...@gmail.com>wrote: > > > > > > > Thanks for the update Doug. Users on TweetPhoto are not able to > > > > > > login. > > > > > > I've added an alert notification on our > > > > > > homepage,http://TweetPhoto.com, > > > > > > to make them aware of the issues linking to the Twitter status blog. > > > > > > Will you need our IPs again to whitelist them or are you good to go. > > > > > > Please let me know how I can be of service. > > > > > > > -Sean > > > > > > > On Aug 15, 12:37 pm, Sam Street <sam...@gmail.com> wrote: > > > > > > > I haven't experienced any downtime or lack of connectivity so far. > > > > > > > > On Aug 15, 7:16 pm, dougw <d...@twitter.com> wrote: > > > > > > > > > Looks like I forgot the link to the status blog. > > > > > > > > > [1] > > > > > >http://status.twitter.com/post/163603406/working-on-unexpected-downtime > > > > > > > > > Thanks, > > > > > > > > Doug > > > > > > > > > On Aug 15, 11:08 am, Doug Williams <d...@twitter.com> wrote: > > > > > > > > > > Hi all --If you have been monitoring our status blog [1] or > > > > > > > > > been to > > > > > > > > > Twitter.com today you have noticed that we are once again > > > > > > experiencing > > > > > > > > > problems due to external causes. The issues causing the > > > > > > > > > downtime > > > > > > require > > > > > > > > > that we once again take measures to bring the site back > > > > > > > > > online. > > > > > > > > > > The first step our operations team must take will likely > > > > > > > > > cause API > > > > > > downtime, > > > > > > > > > especially affecting OAuth. We apologize for the > > > > > > > > > inconvenience and we > > > > > > will > > > > > > > > > work quickly to reduce the impact to the API. We appreciate > > > > > > > > > your > > > > > > patience > > > > > > > > > and I will update you as soon as we know more. > > > > > > > > > > Thanks, > > > > > > > > > Doug
