Open HulaHoopWhonix opened 8 years ago
The continued growth and evolution of i2p is extraordinarily important to me, and I will present this to the i2p, i2pd, and Kovri core developers, but there are a few obstacles to it being in core i2p at this time, foremost being that the SAM bridge isn't activated by default in any of the implementations. Which is done for some good reasons. I do not know how to integrate it into i2p on my own, but I will do my best to make it so.
So I know it's been a while, but I haven't stopped working on it and in the past month or so, it has become fairly usable and stable. I'm still refining a few things, and I'm still deciding how I'll implement addresshelpers, but it will browse most eepSites normally. The only one I've had any trouble, with, actually is i2p-projekt.i2p, which used to crash the proxy unpredictably, but since I did a few workarounds and stability improvements just hangs when mostly loaded. I have not exactly figured out why yet. From what I can tell, i2pd is shipping with the SAM bridge enabled on Debian too, so, once I finish the last few features and I've got some automatic testing in place, I'll start approaching the community with it.
Great work. This is an important security feature. Can you please include this in I2P by default?