API Blacklist policy

[user2017]

I have read in this document https://dev.twitter.com/rest/public/rate-limiting that

If an application abuses the rate limits, it will be blacklisted.

If we have say 10,0000 tweet IDs in our database and want to display them for example via https://dev.twitter.com/rest/reference/get/statuses/lookup or https://dev.twitter.com/rest/reference/get/statuses/show/id

then, if there is high traffic of visitors, the rate will be bypassed and in that case, the API does not respond until the next 15 minute window.

My question is what is the twitter API blacklisting policy in this case ? Is it abuse that due to more number of visitors, the rate limit is exceeded ?

Note - The Oembed twitter point is not suitable for our purpose.

One possible option mentioned in the documentation is caching which we will be exploring. Any other options suggested by the members is appreciated.

[andypiper]

Abuse of the rate limits in this case refers to attempts to circumvent the rate limits (for example by breaking the rules on using multiple application keys for the same purpose). You are not able to exceed the rate limits in normal operation, and if you follow the limits you will be fine.