I think the entire architecture would have to be rewritten. Talking about the protocols involved is getting lost in the weeds. I'm looking at this from the per

I think the entire architecture would have to be rewritten. Talking about the protocols involved is getting lost in the weeds. I'm looking at this from the perspective of the user experience and the physics limitations, and I'm observing that they fit very well together. The point is that a non technical user sees Twitter, fundamentally, as a place to send one way messages out, and to consume one-way incoming broadcast messages. And, crucially, the exact time of sending or receiving isn't a significant aspect of the UX. You just log in and see what showed up in the queue over the last n minutes. If you want to say something, just send a message; you don't really care when it's received, because Twitter is fundamentally all about checking your feed whenever you feel like it, and 23 minutes latency is nothing. The user experience fits the physics limitations. Who cares what the current implementation looks like.