Nagle's Algorithm essentially holds packet data if there has not been an ack (acknowledgement of receipt) for the previous sent packet, and keeps buffering until the ack has been received. The reason this can cause issues with lag is highlighted beautifully with The Navel (Hard Mode). When I am well out of the way of his landslide before the timer finishes (and not just as it finishes but over a second before it finishes) and it still hits me (happened a few nights ago) this means that stuff going on on the server side outpaced what happened on my side. I don't know how much this will help though unless SE sucks at network programming since most skilled network coders just bypass Nagle's Algorithm altogether. I guess that's a big assumption to make though considering the reported server-side validation issues (in before my post gets deleted just for mentioning it lol)