this is how to rebuild #nitter:
- dont use api
- create lots of user accounts
- these user account are the backbone, but keep ther usernames secret. only nitter server knows which user accounts it has access to
- create network of nitter servers
- whenever someone accesses nitter, use one of these user accounts to proxy content request
- use browser automation to make these proxy requests
- x wont know nitter was even used