I view etiquette much like the parent post, but would reframe it in terms of computer things (though it’s similar for diplomacy): it’s protocol, and if you foll

I view etiquette much like the parent post, but would reframe it in terms of computer things (though it’s similar for diplomacy): it’s protocol, and if you follow it you know what to expect; further, if it’s not followed, the results are undefined. Want to start talking IP? Send a SYN to an address, expect an ACK, and send a SYN/ACK. If you don’t hear an ACK, … maybe the server didn’t hear you. Or doesn’t like you. Or someone nearby threw your request in the trash. Or someone near them threw your request in the trash. Or the transport doesn’t know how to get it there. Granted, it’s a leaky abstraction and etiquette and protocol are different in diplomacy, but I just find viewing it through a neutral lens of “shaping my expectations about how this flows” useful.