![Text of a dialog box shown when you click the link to Jon Ostrower's Mastodon profile: Warning: this link may be unsafe https://mastodon.world/@jonostrower The link you are trying to access has been identified by Twitter or our partners as being potentially spammy or unsafe, in accordance with Twitter’s URL Policy. This link could fall into any of the below categories: • malicious links that could steal personal information or harm electronic devices • spammy links that mislead people or disrupt their experience • violent or misleading content that could lead to real-world harm • certain categories of content that, if posted directly on Twitter, are a violation of the Twitter Rules ["Back to previous page" button] Ignore this warning and continue](https://pbs.twimg.com/media/FkGwy6VXoAIYpP_.jpg?name=small&format=webp)
ALT Text of a dialog box shown when you click the link to Jon Ostrower's Mastodon profile: Warning: this link may be unsafe https://mastodon.world/@jonostrower The link you are trying to access has been identified by Twitter or our partners as being potentially spammy or unsafe, in accordance with Twitter’s URL Policy. This link could fall into any of the below categories: • malicious links that could steal personal information or harm electronic devices • spammy links that mislead people or disrupt their experience • violent or misleading content that could lead to real-world harm • certain categories of content that, if posted directly on Twitter, are a violation of the Twitter Rules ["Back to previous page" button] Ignore this warning and continue
![Elon Musk @elonmusk I was told ~1200 RPCs independently by several engineers at Twitter, which matches # of microservices. The ex-employee is wrong. Same app in US takes ~2 secs to refresh (too long), but ~20 secs in India, due to bad batching/verbose comms. Actually useful data transferred is low. Popeska @Popeska The batching is done server-side where the initial client request doesn't matter - GraphQL resolves the request across the microservices and then sends it back. The internal graph is the same regardless of request origin Elon Musk @elonmusk 2h How many serial requests are made by app to refresh timeline? Popeska Just one! You can look at your network tab in Chrome - it's this one. [screenshot of… a list of codey stuff] Popeska (have not worked at twitter - just poking around)](https://pbs.twimg.com/media/Fhiv35-VEAArytR.jpg?name=small&format=webp)
ALT Elon Musk @elonmusk I was told ~1200 RPCs independently by several engineers at Twitter, which matches # of microservices. The ex-employee is wrong. Same app in US takes ~2 secs to refresh (too long), but ~20 secs in India, due to bad batching/verbose comms. Actually useful data transferred is low. Popeska @Popeska The batching is done server-side where the initial client request doesn't matter - GraphQL resolves the request across the microservices and then sends it back. The internal graph is the same regardless of request origin Elon Musk @elonmusk 2h How many serial requests are made by app to refresh timeline? Popeska Just one! You can look at your network tab in Chrome - it's this one. [screenshot of… a list of codey stuff] Popeska (have not worked at twitter - just poking around)
































