IPFS via Tor

Mirimir mirimir at riseup.net
Sun Oct 30 00:26:26 PDT 2016


So hey, IPFS works with a Tor/OnionCat-linked proxy even better than
Freenet does :) Or LizardFS. Because IPFS is a bloody swarm, and it
seems fine with latency. Also, as with Freenet, it seems possible to
extend the IPFS swarm into OnionCat IPv6 address space. So one could add
stuff to IPFS from several onions, access it via IPFS gateways (clearnet
and onion) and tolerate considerable loss of source onions.

And speed is impressive! My Freenet/OnionCat guide at erehwon.dev.null
<http://dbshmc5frbchaum2.onion/Freenet-OnionCat.html> loads rather
slowly, given high latency with multiple proxy layers. But after adding
from my node to IPFS, it loads quickly via the official IPFS gateway:
<https://ipfs.io/ipfs/QmP9FXUN3t8yUJnJerkj57cfzFYbgPmKV2QsCY8M2NHFqf
/Freenet-OnionCat.html>. It also loads quickly via a volunteer public
onion gateway: <http://ipfs4uvgthshqonk.onion/ipfs/
QmP9FXUN3t8yUJnJerkj57cfzFYbgPmKV2QsCY8M2NHFqf/Freenet-OnionCat.html>.

The downside is that, by default, nodes route for the entire IPFS swarm.
That currently means ~2 GB per day. But that can be decreased
substantially by running in dhtclient mode. OnionCat-only nodes would be
probably be OK with that, and only clearnet/OnionCat gateways would need
full routing. Alternatively, one could have an isolated IPFS swarm in
OnionCat IPv6 address space, with much less throughput.



More information about the cypherpunks mailing list