If you have not checked out IPFS you should do it: https://ipfs.io
It looks like a great match for Namecoin as it allows storage of files by hash very easily. Note that ipfs is not anonymous: https://github.com/ipfs/faq/issues/18
I have created a patch that adds IPFS support to NMControl: https://github.com/namecoin/nmcontrol/pull/118
And added a few lines to bitproxy (experimental .bit proxy resolver) to support, too: https://github.com/phelix/bitproxy
Using these it is possible to browse ipfs websites via .bit
http://testipfs.bit/ipfs/QmccqhJg5wm5kN ... ext%20here
Linking to a file securely is just a matter of adding a link to a value - we just need to figure out the format.
IPFS support
-
- Posts: 2001
- Joined: Tue Jun 05, 2012 6:25 am
- os: linux
Re: IPFS support
We should definitely talk to the IPFS people about exactly how the JSON format should work. Also worth figuring out whether an intermediate proxy is a safe/good way to do it. (I know intermediate proxies are tricky to do right in Tor's case; no idea what quirks IPFS might have.)phelix wrote:If you have not checked out IPFS you should do it: https://ipfs.io
It looks like a great match for Namecoin as it allows storage of files by hash very easily. Note that ipfs is not anonymous: https://github.com/ipfs/faq/issues/18
I have created a patch that adds IPFS support to NMControl: https://github.com/namecoin/nmcontrol/pull/118
And added a few lines to bitproxy (experimental .bit proxy resolver) to support, too: https://github.com/phelix/bitproxy
Using these it is possible to browse ipfs websites via .bit
http://testipfs.bit/ipfs/QmccqhJg5wm5kN ... ext%20here
Linking to a file securely is just a matter of adding a link to a value - we just need to figure out the format.