How can a single instance serve many clients and not get rate limited?
From my arguably limited understanding of this project (#706), I'm lead to believe all traffic that normally would be sent from the client browser to twitter, has to go through nitter which only then communicates with the public twitter API on behalf of the user.

If that is in fact the case, how come this service can even function when more than one person is actively using it?

From my experience the guest twitter API is not entirely ratelimit-less, and even with modest intervals (on the order of 10s of seconds) between requests I sometimes would still trip some limit on my token, when making no more than 40 reqs in total.

**So, as per the title of this issue, _how does nitter avoid this happening to a single instance?_**

At this point my motivation behind writing this is a little blurry, but there is one conclusion that I'm sure of and it leads my to ask,
Why isn't nitter an entirely in-browser addon?
That would surely help the (_nonexistent?_) problem by making each user do their own requests? 