On Wed, 4 Oct 2017, Alex Smith wrote:
Far too powerful, given how difficult it can be for some clients to
display anomalous Date: headers.
Could lead to some interesting time paradoxes, too (given that changing
the gamestate as though the message were sent at some other time than
the time the message was actually sent could potentially change the
timing at which the message self-ratifies, leading it to maybe self-
ratify multiple times). I'm not sure if there's any situation that's
outright broken, but it's confusing to think about.
Whoops, that does seem annoying.
Greetings,
Ørjan.
