If you use the Twurl console, you're using your apps -- transparently behind
the scenes it issues the Twurl console an access token and makes calls on
your behalf.
I'll look to get this business with read/write access resolved quickly.
Taylor Singletary
Developer Advocate, Twitter
Ah, okay, that makes sense. It took the first app in the list and
automatically authorized it, and the first app in my list happens to
be a placeholder app.
On Apr 16, 12:22 pm, Taylor Singletary taylorsinglet...@twitter.com
wrote:
If you use the Twurl console, you're using your apps --
In that case, you might not want to edit your app settings through
dev. because since early this morning, the old edit URL [1] has been
throwing a fail whale. You won't be able to restore your r/w setting.
[1] http://twitter.com/oauth_clients/details/
On Apr 15, 5:12 pm, Mike Davis (mcdavis)
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 [1] has been
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
