23 ms·
And also IPFS rats our to the whole world all your network interfaces, MAC addresses, and internal network configs. And even after multiple requests of support
by mystraline 10mo ago
And also IPFS rats our to the whole world all your network interfaces, MAC addresses, and internal network configs.
And even after multiple requests of supporting a Tor mode, have routinely ignored that with "but its too hard!"
And, I quit running IPFS back in the .31 version after adding some chat logs to my local machine's share, and found a google crawler within 1 hour and fully indexed them.
No thanks.
- flipped 10mo agoWhat? That's the laziest argument against IPFS. Bind it on one interface or just use a VM.
- mystraline 10mo agoDefaults absolutely matter. And no, I dont my whole internal network enumerable because of 'convenience'.
- flipped 10mo agoI don't think the kind of crowd IPFS attracts would wanna use the default config. Most ould choose to configure according to their setup.
- anthk 10mo agoYou are right; it's a bit of a excuse. Tons of small services under Unix (by default) listen on several interfaces and networks. I think Bitlbee itself listened on 0.0.0.0 instead of localhost. Ditto with some UPNP/DLNA daemons. It takes very little to set up IPFS to just listen to tun0, disable routing (let ygg do its job) and throttle the bw a little so it doesn't hog the whole network. I would be surprised if the Kubo/IPFS developers didn't already configure Ygg for themselves, as both are software written in Go. The author of NNCP https://nncp.mirrors.quux.org/ https://nncp.mirrors.quux.org/ (and the other author from Tofuproxy) are pretty much aware of Yggdrasil.
- anthk 10mo agoIPFS support interface binding, hard disk quotas, working as a router or not, and bandwidth quotas among several settings. Yes, by default can be a bit intensive.