Hi Guys I've seen this too. However. If you re-visit the page a couple of minutes later it'll load just fine. We had this for @socialiteapp and whilst the initial load wouldn't work, visiting the page a few minutes later would work just fine.
Cheers! -N On Mar 11, 8:59 am, Tim Haines <tmhai...@gmail.com> wrote: > Email them offlist and I'm sure they'll look it up for you. > > Sent from my iPhone > > On 11/03/2010, at 9:51 PM, Jesse Stay <jesses...@gmail.com> wrote: > > > > > So how do I verify my consumer key is correct? I would imagine that > > page would be pretty important - how can you edit your app without it? > > > I'm also curious about why I'm being prompted for basic auth > > onhttp://api.twitter.com/oauth/access_token > > > Thanks, > > > Jesse > > > On Thu, Mar 11, 2010 at 1:37 AM, Tim Haines <tmhai...@gmail.com> > > wrote: > > There's a bug in that page. If your app has too many users, it > > fails to load. Mark (or was it Raffi?) said they were fixing it > > last year, but I guess it's pretty low on the priority list. > > > Tim. > > > On Thu, Mar 11, 2010 at 9:26 PM, Jesse Stay <jesses...@gmail.com> > > wrote: > > I'm trying to access my app page here: > > >http://twitter.com/oauth_clients/details/61 > > > and I keep getting the over capacity fail whale message. In > > addition, when I pass my request_token, verifier, etc. to the > > access_token method > > (http://api.twitter.com/oauth/access_token?oauth_consumer_key=...blah.... > > ) in a normal browser window it prompts me for a plain auth username > > and password - is this normal behavior when testing in the browser? > > > Thanks, > > > Jesse
