While I’ve developed several applications , two fields (Consumer key, Consumer secret) were required and two (Access token, Access token secret) WERE NOT REQUIRED on the menu “Home>My Applications>Application>OAuth tool“ on dev.twitter.com. Recently I found two fields (Access token, Access token secret) change to REQUIRED (posted on March 15th).
Our first test with two blank fields was OK, however, after two fields have created by pressing “See OAuth signature for this request”, we have problem using REST API Rate Limiting.
- Is it OK those fields (Access token, Access token secret) to be blank?
- We have another apps using this API. We wonder need to change all other apps according to this changed policy.
- If previously developed Apps are not affected by changed policy, can we also remove already created values?
- When does the policy on Rate Limiting in Ver 1.1 change? (I found “Updated on Fri, 2013-03-15 09:32” on https://dev.twitter.com/docs/rate-limiting/1.1)
Thanks for your support in advance,