Open ghost opened 7 years ago
I think the way I2P works makes it too slow for a/v calling.
Not very familiar with i2p, but I was under the impression that any application can use the i2p network without the application having any i2p support, isn't that so? Not sure how i2p achieves that though, so depending on what it does there might be some issue particular to Tox that centralized applications like IRC wouldn't have. For example, it might be possible for some Tox client on the i2p network to purposely insert clearnet IPs addresses into DHT in order to leak clearnet IPs of some Tox users in i2p, which is probably not something that is desired. Think of it like clearnet IP img html tag insets into i2p hiddennet websites.
One thing I noticed in the Tox spec is that only IPv4 and IPv6 addresses are used. I2P needs a full domain to interpret the destination. With the exception of that, Tox doesnt "need" a PR to support it, but would greatly benefit from integration and optimizations.
I can see a situation where text and keep alive packets can be sent via I2P, and direct clearnet connections can be made for audio and video. Id have to read more on the Tox spec first before I start looking into it.
As a casual I2P users I just wanted to say thanks for working on this, I would be interested in using it. 👍
Seems pretty interesting, and maybe spinning up multiple I2P tunnels and spreading the load between those. I am working with i2pd on other projects, so if there is enough interest I can make it myself. Of course converting 100 percent is impossible while keeping backwards compat, but maybe make I2P only/clearnet/both as a setting