examples

A little hard to find, but this is well described in https://github.com/ipfs/examples/blob/5d77470eb5ae944aa54093....

Encrypt the files before adding to IPFS and then decrypt after receiving them. Support for encryption will be built-in into IPFS in the future but for now, this solution works. There is a issue tracking this here: https://github.com/ipfs/faq/issues/6 Also, when adding files yourself, those files become pinned by the default. Getting files won't pin automatically however. You have some more information about pinning here: https://github.com/ipfs/examples/tree/master/examples/pinnin...

There isnt a doc available yet, but there are two key properties. The first is, you can create mutable IPFS archives by generating a keypair; the pubkey becomes the identifier, and new versions are signed by the private key. The second property is, you can use DNS TXT records to provide shortnames that map to the pubkey (or, I believe, to a static hash-id also). Run 'dig txt ipfs.io' to see an example. EDIT: this is also helpful https://github.com/ipfs/examples/tree/master/examples/ipns

If we're talking about linking names to resources, ipfs/ipns is not a different thing https://github.com/ipfs/examples/tree/master/examples/ipns

Another problem is why we at all need to rely on any third-party hosting services while we have our own computers connected to the Internet. In this regard, I have high hopes for content-addressable distributed systems. Currently, IPFS [1] looks most promising to me. It's easy to publish a static website to it [2], and public gateways are available to make the site accessible to readers who do not run their own nodes. While IPNS (the naming system) does not seem to work reliably yet, hash of the current version of the web site can be published in a special DNS TXT record, and if that same domain points to IP address of a public gateway, the web site will be simply accessible via that domain. [1] https://ipfs.io/ [2] https://github.com/ipfs/examples/tree/master/examples/websit...

In May I contributed an example to the IPFS documentation. (https://github.com/insanity54/website/commit/64db436e33662f2..., https://github.com/ipfs/examples/pull/5/commits) At that time, the site was served by github pages, but parts of the site, including the examples, were served by IPFS. On IRC, I had heard of plans to migrate the entire site to IPFS once IPNS was ready. EDIT: seems like it's all IPFS now https://botbot.me/freenode/ipfs/search/?q=github+pages EDIT2: Better link. https://botbot.me/freenode/ipfs/2015-08-22/?msg=47828655&pag... (The way the IPFS gateways work is you run them on a machine and bind to port 80 or whatever. Then in your DNS TXT records, you put the hash of the content you want to serve, and the gateway picks up on this and fetches the hash from the network.)

There is some documentation about IPNS here: https://github.com/ipfs/examples/tree/master/examples/ipns