Reply to post:

In the end he may still be right. A graphql request for a Twitter timeline probably fans out god knows how many remote requests to resolve the final result. It's to be expected the engineers working on this hot pile of garbage (not their fault) feel a need to defend their (life's) work vehemently, who wouldn't.