Performance: ugh yes. The GO implementation is a CPU and RAM hog. Basically, you cannot run it on a cheap vps, where you could easily run apache or nginx. Ther

Performance: ugh yes. The GO implementation is a CPU and RAM hog. Basically, you cannot run it on a cheap vps, where you could easily run apache or nginx. There's also significant bandwidth costs from a distributed hash table. That's a design implementation that really can't be avoided as the nature of dHT's. Running this on phones will blow through your monthly quota pretty quickly just on announce traffic. I'm not well versed in GO, so I can't! However there's a LOT of customizations and settings you can turn off/on. For example, you can create a private IPFS network of just your machines. Or you can create piracy networks of friends. That sort of thing. Just my complaints about the defaults are what I would classify as unsafe. As for running through Tor or I2p, well yeah. I worked with another user who ended up figuring out a way to do it through Tor that only shared an internal 192.168.0.0/24 address. Basically they firewalled all internet comms other than Tor and forced through it. Also had to do MAC randomization because IPFS also shares that. The IPFS folks initially said they were going to first-class Tor support. But when it got hard, they backed out. My guess was that would have turned IPFS into the biggest unstoppable piracy net. And Benet and gang were busy with filecoin. Tor doesn't make money, and has the smell of unsavoriness. My recommendation is to get 2 machines, and bring them both up with a trivial 'hello.txt' file and prove all the details you can about the other. I don't think the protocol changed much... But I could be wrong. I left using it because of massive resource usage, high network bandwidth, and user-hostile hosting environment due to insecure and everything-shared environment.