#1

Is it consider a bad practice to have the same tokens for development and production?

  • If so, can you explain why or point to relevant articles to read?
  • If not, why is there specific reasons to allow for this?
1 Like
#2

Thanks for reaching out here. Have you seen our guide on authentication best practices? This may be what you are looking for here.

Thanks again!

1 Like
#3

Thanks for your suggestion for the article, but it did not answer my question — which is why the same tokens should not be used in both dev and production environment — assuming, for example, that dev is my local machine and production is hosted on a server.

1 Like
#4

Thanks for clarifying. You could use them in both if you wanted to. However, you would be subject to the same caps and rate limits for both environments.

You’d also want to make sure you take a look at our policies and making sure both environments are in accordance with our policies including the Developer Agreement and Policy, Automation Rules, Display Requirements, and/or the Twitter Rules.

2 Likes
#5

Just to be clear: are you saying that if I use different tokens for production + dev then they will each get their rate limits? If so, then yes, it’s clear why you added this distinction. Thank you!

1 Like
#6

Yes, that is correct but you will need to make sure that you are staying within our polices.

2 Likes
#7

Thank you — I have indeed read all of the Twitter policies, and have revisited all of them recently to make sure that my apps to comply with all of your requirements.

I can’t tell if you are hinting that my apps are not — in case you are, please let me know.

1 Like
#8

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.