You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was thinking how to do an i2p implementation.
And I realised somethings, some transport need configuration on the client to works, but this config may change from one client to an other.
It could be done by adding a way to register vias.
Vias is just a protocol (name or code) with the coresponding multiaddr used to access this protocol.
After I should be able to seemlessly connect to onion address because libp2p should automaticaly encapsulate all onion address with my proxy.
So /onion/hereexampleonionaddr seemlessly mutate to /ip4/127.0.0.1/tcp/9050/socks5/onion/hereexampleonionaddr but only on my node.
Here the example with cjdns is just to demonstrate it could be used with all kind of proxy, but for a specifical cjdns connection autorelay is probably better because all connection will pass through the seted proxy while autorelay automaticaly do new relay.
You can also see i2p have 2 proxy, that just for fail over (implementation managed, it could also be used for load balancing).
But I think this is prettier if we do that with :
But that not vanilla json.
In the code that could be managed with some function like addViaToProtocol(ProtocolCode, Multiaddr), clearProtocolVia(ProtocolCode) and maybe removeViaToProtocol(ProtocolCode, Multiaddr).
That could be usefull for very easy i2p, onion, cjdns, ... implementation via a manual configuration.
First configure your hidden service, then add the hidden services address in announce and finaly add your proxy.
The text was updated successfully, but these errors were encountered:
I was thinking how to do an i2p implementation.
And I realised somethings, some transport need configuration on the client to works, but this config may change from one client to an other.
It could be done by adding a way to register vias.
Vias is just a protocol (name or code) with the coresponding multiaddr used to access this protocol.
How it could looks in a json config file :
After I should be able to seemlessly connect to onion address because libp2p should automaticaly encapsulate all onion address with my proxy.
So
/onion/hereexampleonionaddr
seemlessly mutate to/ip4/127.0.0.1/tcp/9050/socks5/onion/hereexampleonionaddr
but only on my node.Here the example with cjdns is just to demonstrate it could be used with all kind of proxy, but for a specifical cjdns connection autorelay is probably better because all connection will pass through the seted proxy while autorelay automaticaly do new relay.
You can also see i2p have 2 proxy, that just for fail over (implementation managed, it could also be used for load balancing).
But I think this is prettier if we do that with :
But that not vanilla json.
In the code that could be managed with some function like
addViaToProtocol(ProtocolCode, Multiaddr)
,clearProtocolVia(ProtocolCode)
and mayberemoveViaToProtocol(ProtocolCode, Multiaddr)
.That could be usefull for very easy i2p, onion, cjdns, ... implementation via a manual configuration.
First configure your hidden service, then add the hidden services address in announce and finaly add your proxy.
The text was updated successfully, but these errors were encountered: