> Thanks for contributing to I2P!
;) My contributions are relatively minor and I2P (as well as other crypto systems) is something I really believe in.
> Do you have any thoughts on HORNET? Could I2P benefit from a more stateless routing mechanism as opposed to tunnels in the far future?
It's been a while since I read the HORNET paper, but as I remember it, HORNET relied heavily on ISP level cooperation which is just not realistic.
However, the idea of reducing state is a very good one. Going forward I hope to see more cryptographic systems that aspire to reduce overall state.
> I'm working on Go implementation here: https://github.com/hkparker/go-i2p. Haven't made to irc2p to introduce myself yet but I will. Are there any devs who might be interested in contributing?
Currently there are 3 implementations of I2P apart from yours. The original java one, i2pd[1] and kovri[2]. We all cooperate and discuss specifications to maintain interoperability. However the alternative implementations are not maintained under the I2P project as the developers of them desire to be separate.
I was previously unaware of your Go implementation, but you should definitely head over to #i2p-dev and say hi. You can find me under the nick hottuna there.
> Privacy of developers seems a priority. Without any detail of course, can you comment on how necessary this has been. Is it irresponsible of me to work on an implementation in the clear?
About privacy, people have taken various stances. Some a truly anonymous, some are semi anonymous, and some like me are not anonymous. Maintaining privacy for a while might be a good idea. You can always get less anonymous, but going the other way is harder.
[1] https://github.com/PurpleI2P/i2pd
[2] https://github.com/monero-project/kovri