[_rlms]

Thanks for contributing to I2P!

Do you have any thoughts on HORNET? Could I2P benefit from a more stateless routing mechanism as opposed to tunnels in the far future?

Are any of the devs going to defcon this year? I tried to get a small meetup going last year in the privacy village but no turnout, would love to make something official.

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?

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?

[robert_foss]

> 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

[kodablah]

I am quite interested in go-i2p myself. How usable is it?

As for HORNET, I saw a minor Go impl of the ideas [0] along w/ a tiny mailing list post [1]. While it does appear to be made for backbone network devices, I believe the concept of onion routing w/ basically multi-hop TLS can be done in layer 7. I think the one thing missing is an implementation people can use and depend on (definitely outside of my present abilities).

0 - https://github.com/LightningNetwork/lightning-onion 1 - https://lists.linuxfoundation.org/pipermail/lightning-dev/20...

[_rlms]

Not usable yet, still implementing and testing the data structures. Thanks for those links, very interesting!

[arpstick]

I don't think it's much of an issue to work on i2p in the clear. It may be that is a main component why tor was able to thrive so well, their developers weren't shadowy internet nyms so people felt more comfortable giving money to fund them. The dev channel is also on freenode via #i2p-dev if anyone wants to join and contribute.

[plasticmachine]

Some of the Monero Kovri developers are known, public people, there's no problem with that at all if you choose to be public. There's really no longer as much of a stigma for people who are working on privacy projects:)

[matiasb]

Nice, I would love to contribute!