From: i2p.net Feedback submission
When people set up I2P, they expect an ecosystem where a user can't be tracked site-to-site, or where site operators can't infer information about them based on when they visit. I have seen in a few cases people being disappointed that the default behavior in both I2Pd and Java I2P being the persistence of client tunnel keys for the HTTP proxy. I recommend changing the defaults to something like: Close client tunnels after specified idle period: 60 minutes New Keys on Reopen: Enable.
From: i2p.net Feedback submission
When people set up I2P, they expect an ecosystem where a user can't be tracked site-to-site, or where site operators can't infer information about them based on when they visit. I have seen in a few cases people being disappointed that the default behavior in both I2Pd and Java I2P being the persistence of client tunnel keys for the HTTP proxy. I recommend changing the defaults to something like: Close client tunnels after specified idle period: 60 minutes New Keys on Reopen: Enable.