Every single time I go to https://twitter.com/apps and click the linked name of my app, I get an over capacity fail whale.
I also just now noticed that there was an approved app in my Connections tab, which said the app was authorized today at 5:17 AM. And I *most* certainly did not authorize that app today (or ever). It's one of my "placeholder" apps, and I use those consumer keys absolutely nowhere. On Apr 15, 5:40 pm, "Mike Davis (mcdavis)" <mcda...@gmail.com> wrote: > Yeah, I was able to switch my app back via the old page, but just > wanted to bring it to attention. > > On Apr 15, 4:35 pm, Dewald Pretorius <dpr...@gmail.com> wrote: > > > > > In that case, you might not want to edit your app settings through > > dev. because since early this morning, the old edit URL  has been > > throwing a fail whale. You won't be able to restore your r/w setting. > > > http://twitter.com/oauth_clients/details/ > > > On Apr 15, 5:12 pm, "Mike Davis (mcdavis)" <mcda...@gmail.com> wrote: > > > > When creating or editing an app through the new dev.twitter.com site, > > > the application will lose (or never be permitted) "write access" and > > > will only have "read access". > > > > The options to choose between "read access" or "read & write access" > > > that's on the old oAuth page are no longer accessible on the new dev > > > page. > > > > Is this being done away with or was it just left out?- Hide quoted text - > > - Show quoted text -