nitter over IPFS or torrent
with the current limitations of private instances it could be interesting to think about sharing data between instances

it doesn't make sense for each instance to make dozens of requests for the same profile at all times

files with the latest tweets could be created and shared via IPFS with a centralized index that would function as an official tracker

the name used in the index of these files could be `<username>/<unix epoch>/tweets.json`, something similar to web.archive.org

this official tracker could have official mirrors protected by hash system, like  the secure apt mirrors on debian/ubuntu

so if there is a file in IPFS created in the last 60 seconds, the instance could get the data from IPFS instead of Twitter

doing it this way:
1. nitter becomes webscrapping friendly
2. is it possible to use cloudflare to share json without captcha via ipfs
3. nitter remains decentralized
4. the load is much lighter for the instances as images can be shared between multiple instances

the main problem with IPFS is the lack of seeds, this does not seem to be a problem when we are dealing with an already consolidated network of decentralized instances

to increase the number of seeds, torrents could be used so that any visitor with a bit torrent client can download the latest tweets and contribute to maintaining the network with seeds (archive.org has been doing this for years)

this would certainly help a lot to reduce the number of requests made by instances to Twitter