Awesome, thanks Matt, seems to be all working normally here too.
On Jul 10, 10:37 am, Matt Sanford <m...@twitter.com> wrote: > Hi all, > > The issue has been fixed and from my testing it looks like things > are back to normal. > > Sorry for the disruption; > – Matt Sanford / @mzsanford > Twitter Dev > > On Jul 9, 2009, at 4:38 PM, dean.j.robinson wrote: > > > > > Thanks for the super speedy response Matt. > > > On Jul 10, 9:26 am, Matt Sanford <m...@twitter.com> wrote: > >> Hi all, > > >> Some changes were just deployed and it looks like there may be a > >> bug. I'm looking into it now … hold tight and I'll update you all > >> when > >> I know more. > > >> Thanks; > >> – Matt Sanford / @mzsanford > >> Twitter Dev > > >> On Jul 9, 2009, at 4:25 PM, dean.j.robinson wrote: > > >>> Everyone just magically got logged out of my hahlo4 beta, which was > >>> working fine an hour ago, and now when they reauthorize its not > >>> sticking. > > >>> OAuth login works fine, redirect back to hahlo4, but all api calls > >>> are > >>> returning 401 status codes. > > >>> Saw mention in another topic regarding whether twitter.com > >>> orwww.twitter.com > >>> should be used when making api call, all my calls are currently > >>> using > >>>https://twitter.com > > >>> Anyone else experiencing anything similar?