Diff: [root] @ 0ffffe03a16 | faq | css

Remove links to merged patches

File: ipfs-overview [Diff]

diff --git a/ipfs-overview b/ipfs-overview
index 32987c4..32ab98b 100644
-- a/ipfs-overview
++ b/ipfs-overview
@@ -26,7 +26,7 @@ h2. Practical data storage

h3. Gateways

There are public HTTP gateways which allow to access IPFS without installing software. Most well-know is at [:https://ipfs.io], just add @/ipfs/<hash>@ or @/ipns/<hash>@ to access data. Bitcheese.net has "its own gateway":http://ipfs.bitcheese.net, but it works only for data already hosted by the server. Here's a "patch if you want to make your own restricted gateway":https://github.com/ipfs/go-ipfs/pull/4150.

h3. IPNS

@@ -78,8 +78,6 @@ It's also sometimes desireable to attach filename to the file linked. Creating a

ipfs:/ipfs/QmBar?context=/ipfs/QmFoo/foo/bar&ipns=/ipns/QmLink&filename=file.mp3

I made a "patch for go-ipfs that handles that for gateway links":https://github.com/ipfs/go-ipfs/pull/4177.

h3. Keeping content available

Downloading content in IPFS automatically seeds it, but go-ipfs daemon also supports "pinning", If you want content alive, you can @ipfs pin add@ it. Unfortunately, IPNS pins (both ipns entry itself and updated contents) are not implemented yet.

By Voker57 on 2019-03-18 13:46:27 +0200 Powered by bitcheese wiki engine