Support i2p eepsites

[FiloSottile]

i2p supports HTTP sites with the TLD .i2p, called eepsites.
It would be great to support those, also.

Analogue to #80

--- Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/14807170-support-i2p-eepsites?utm_campaign=plugin&utm_content=tracker%2F318575&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F318575&utm_medium=issues&utm_source=github).

[fpietrosanti]

I2P Tunnel does provide SOCKS access: http://www.i2p2.de/i2ptunnel.html

Other references:
http://www.i2p2.de/how_networkcomparisons

From https://tails.boum.org/doc/anonymous_internet/i2p/index.en.html
"I2P is an alternative anonymity network to Tor which supports most common Internet activities like web browsing, email, filesharing etc. Unlike Tor, whose main focus arguably is on accessing sites from the "normal" Internet, I2P is more oriented towards being a closed darknet, separate from the "normal" Internet. Any one running I2P can run an anonymous server, a so called Eepsite, that is only accessible within I2P using the .i2p top level domain (similar to .onion for Tor hidden services). "

The Tor2web implementation of Socks use "Optimistic Data" that means it maybe incompatible by default with I2P Socks proxy implementation and require minor tweaking.

[str4d]

Support for I2P eepsites is definitely possible, there already exist other I2P inproxies (e.g. *.i2p.us) using unknown backends. I haven't looked at the Tor2web code, but wrt SOCKS, I2P's SOCKS client tunnel implementation should be standard from the perspective of a connecting application (there are a few I2P-specific tweaks on the inside). It is an incomplete implementation (UDP is not implemented yet) and not rigorously tested, but any problems can and will be fixed.