forked from I2P_Developers/i2p.i2p

this may have unintended consequences, as we need to deal with messages received from skewed clocks, but I believe the two pathways used here are safe (we leave the larger timeout thresholds intact for dealing with remotely generated message times)