Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
I2P Natively Supported #240
Brief Description: Support for I2P natively
Operating System (OS and version): Linux / Windows / OS X / *nix
Due to the limitations of Tor, and its (let's be honest) being a haven of malfeasance, the alternative of I2P (which robustly supports UDP and addresses DHT limitations by design -- one of its intended use cases to support pseudonymous Bittorrent clients) should be explored.
More than a cursory glance at I2P will reveal a small but significant skilled and motivated base of programmers in the I2P community who have provided many working implementations of software (as a thread on the Subreddit at /I2P/ mentioned recently, on the topic of OpenBazaar, that I2P devs have themselves built many working implementations of software like Zeronet, Bittorrent, Vuze, et cetera. The common thread, for all, has been that the I2P development community is so niche that these programs often become stale and lose development interest because the end up as a "proof of concept" and the initial project creators don't put forth any substantial efforts to supporting the community.
For those concerned about exposing their IP addresses, and simply having a rather MINIMAL expectation of some privacy, have you thought about supporting I2P? I understand the mantra "just use a VPN," but VPNs fail open, thus revealing the user's IP adress, without her taking great strides to ensure they close their internet connection if the VPN connection hiccups.
Moreover, many would prefer to run OpenBazaar-Server on their own hardware as opposed to trusting a VPS to manage it. This is just obviously overhead for many who want (such as myself, and I KNOW others) a rather straightforward use case to do three things simultaneously:
OpenBazaar is not, by design, a good fit for Tor. I2P solves all the problems inherent to the OB design and I think that by OB supporting it natively, the problem that's been seen in other projects where I2P developers have had to take the reigns out of the gates, it's been shown that support wanes and then just dies as the native projects themselves continue unabated. Please show some regard for those who don't want their IP exposed to the world and value their privacy to do so.
I was working in this days on outproxying the OB connection through I2P.
The change could be made without too much of an effort if using onioncat on top of it, so that instead of a b32 (the basic identity used in I2P) you may have a ipv6 to identify the node, which of course would not be the real one.
I don't see any reason not to set it as default and only network. Right now OB does not protect the less tech-savy, and is forcing anyone to buy a VPN or looking for other means of protection by design, which adds a layer of complexity for the end user.
There are ways to do it, and while still in testing it won't take too long, but the more the network grows the more difficult it will be to implement such an upgrade in a flawless and simple way.
A couple of weeks of delay in the project looks like a good tradeoff for really coming out with a full working, protected and "battery included" software.
If I can be of some help in testing or anything please let me know, I'm not a programmer but I'd be glad to help.
I joined the slack and:
Hi! I'm one of the developers of I2P. I agree with the OP that having something like OpenBazaar get I2P support would be really neat! I'm posting here so you know I am happy to answer questions :)
I haven't yet grepped the source and don't know anything about how your existing backend works, but in case it is useful, there are currently two Python libraries for I2P (both backed by the SAMv3 API):
What use case do you mean?