When Nitter first came around, it was incredible. It really goes to show just how easy it would be for Twitter to provide a fast and accessible version of their site if that was their goal. Too bad it isn’t and Nitter instances will forever run into rate limiting.
The old rate limit errors were false flags caused by a bug in the API token parser. Nitter instances have yet to run into a real rate limit.
I see. Thanks for the information.