Re: [twitter-dev] Re: Creating or editing applications through dev.twitter.com causes apps to lose write access
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 http://twitter.com/episod On Thu, Apr 15, 2010 at 3:06 PM, Dewald Pretorius dpr...@gmail.com wrote: 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 [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) mcda...@gmail.com wrote: When creating or editing an app through the new dev.twitter.comsite, 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 - -- Subscription settings: http://groups.google.com/group/twitter-development-talk/subscribe?hl=en
[twitter-dev] Re: Creating or editing applications through dev.twitter.com causes apps to lose write access
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 -- 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, Twitterhttp://twitter.com/episod On Thu, Apr 15, 2010 at 3:06 PM, Dewald Pretorius dpr...@gmail.com wrote: Every single time I go tohttps://twitter.com/appsand 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 [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) mcda...@gmail.com wrote: When creating or editing an app through the new dev.twitter.comsite, 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 - -- Subscription settings:http://groups.google.com/group/twitter-development-talk/subscribe?hl=en- Hide quoted text - - Show quoted text -
[twitter-dev] Re: Creating or editing applications through dev.twitter.com causes apps to lose write access
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) 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?
[twitter-dev] Re: Creating or editing applications through dev.twitter.com causes apps to lose write access
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 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) 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? -- To unsubscribe, reply using remove me as the subject.
[twitter-dev] Re: Creating or editing applications through dev.twitter.com causes apps to lose write access
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 [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) 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 -
