linvi
commented
4 years ago Effectively Twitter V5 does not support the V2 rate limits. This is a work that will need to be done for version 5.1.
In the meantime I recommend you manage the rate limits manually.
Here is a ticket opened for this already https://github.com/linvi/tweetinvi/issues/1006.
The current logic for handling rate limits does not seem to work as I had expected for the V2 search endpoint. The 1.1 rate limit status endpoint cannot be used to retrieve values for this endpoint and the rate limit cache logic does not create entries from rate limit headers returned whilst querying for this endpoint either. How would you suggest adding the rate limit for this endpoint and allow it to be managed and updated by your cache update mechanism. To better understand how to resolve this issue could you also give your rationale for the cache update mechanism always supplying false as the argument for 'create new entries if they do not exist' so I can avoid violating the intention of that code. I am using v5 in track and wait mode. Thanks