Hacker News new | ask | show | jobs
by icebraining 3067 days ago
As far as I understand it, proxying it is dangerous because IPFS will announce all your IPs so that the shortest routes can be established. You probably need to run it in a VM/container that only has access to Tor and no other network adapter.
3 comments

Ah, good to know.

I love the idea behind IPFS but it just doesn't feel mature enough yet. The documentation, examples, consistent APIs, etc, don't seem very solidified.

Thanks! We're hard at work making everything better, especially the documentation and examples bit, but lots of work on the APIs as well.

If you have anything concrete to suggest or help out with, please open up a issue in the relevant repository, this would be the entrypoint to find your way around in our Github organization: https://github.com/ipfs/ipfs

Disclaimer: I work for Protocol Labs on IPFS

I want to contribute, experienced senior web dev. Where do I get started?
Jump into #ipfs on freenode (IRC) and tell us what area you want to contribute to and someone can point you in the right direction.

Otherwise, assuming you know JavaScript, https://github.com/ipfs/js-ipfs/issues?q=is%3Aopen+is%3Aissu... is a great place to start.

If you have some Golang experience, https://github.com/ipfs/go-ipfs/issues?q=is%3Aopen+is%3Aissu... should work to find you some beginner issues.

> announce all your IPs

That's configurable. Check the format for the config here: https://github.com/ipfs/go-ipfs/blob/master/docs/config.md#a...

Keyword being `Announce` and `NoAnnounce`

It's pretty easy to configure ipfs to not advertise internal IP addresses.

Though it really should be the default behavior.