Nitter doesn't use the official API, which seems to be what's broken, instead it talks directly to the undocumented APIs that Twitters normal web interface is b

Nitter doesn't use the official API, which seems to be what's broken, instead it talks directly to the undocumented APIs that Twitters normal web interface is built on. I assume they do it that way to get around all the rate limiting and threat of having access revoked that the official API comes with.