Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

I2P support #303

Open
snex opened this issue Aug 20, 2024 · 2 comments
Open

I2P support #303

snex opened this issue Aug 20, 2024 · 2 comments
Labels
enhancement New feature or request

Comments

@snex
Copy link

snex commented Aug 20, 2024

Describe the solution you'd like

It would be very cool if bitmagnet had built-in I2P support. See https://geti2p.net if you are unfamiliar. Essentially I2P is similar to Tor but there are no exit nodes.

Describe alternatives you've considered

Doing this from scratch. Seems like a waste of effort.

Additional context

If you would like to know more, please join us on the postman I2P IRC server #saltr channel.

@snex snex added the enhancement New feature or request label Aug 20, 2024
@leofidus
Copy link

That'd be quite interesting. What separates i2p from tor is that there's a lot of i2p-internal torrent traffic that doesn't interact with the clearnet at all. It's like its own little torrent bubble.

@eyedeekay
Copy link

We have some fairly extensive Go libraries with I2P implementations of net.Conn, net.PacketConn, and net.Addr allowing developers to drop them in where possible. onramp can be configured to use the address format that the in-I2P DHT expects. So if you make use of the net.* interface types in the existing code then we can make implementation very straightforward.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants