The question is whether we're fetching this off of the same APIs i.e. Twitter themselves are using, or if we're scraping it from server-side rendered sites. If we're attemtping to do it via their open APIs we're going to be hitting rate-limits, and probably also face liability. What if there was some service that you could run on different computers, that each had their Twitter API tokens, and then we'd distribute the requests to different hosts, so that it could not be tracked.