@Xeha
@orignal
Arch
Danny
Irc2PGuest28384
Irc2PGuest75631
Irc2PGuest81267
Over
R4SAS
RN
ReturningNovice
StormyCloud
Strykar
U1F642
acetone
ahiru
ananas
duanin2
fidoid_
i2potus
ice_juice
itsAMe_
luvme3
mareki2p
n2_
pinotto
poriori
qend-irc2p
r00tobo
r00tobo[2]
rapidash
sexy
uberius
x74a6
yeti
FatherTime
Hello i2pd team. I have read about the strengths and weaknesses of i2p and one point that I've seen others discuss is the lack of advanced configuration for HTTP/SOCKS proxy. Currently there is only one local destination for HTTP/SOCKS proxy, which is a unique identifier until the tunnels are reloaded. From what I understand the i2p router could in theory have different tunnels for different base64
FatherTime
addresses on the network, so that for example one eepsite(or group of eepsites) would see one local destination while another group would see another. Also being able to reload certain tunnels manually or at scheduled time intervals would help as well. If this interests you would you consider creating a Kuno (https://kuno.anne.media), or other donation fund outlining how you would implement this
FatherTime
improvement and what amount of funds you would need so that I and others like me can help you improve i2pd?
Xeha
FatherTime_: Regarding funding and alike, thats something for orignal to answer.
Xeha
You can have as many tunnels as you want. Just add more socks tunnels to your tunnels.conf.d/tunnels.conf
Xeha
socks5 is not recommended to browse eepsites. use an http proxy for that, as it removes header informations for privacy