From eb33949135113fccb044e2117efda3a7b716a91d Mon Sep 17 00:00:00 2001 From: Steven Allen Date: Mon, 18 Feb 2019 13:23:27 -0800 Subject: [PATCH] CHANGELOG: NoFetch doesn't _only_ serve pinned content License: MIT Signed-off-by: Steven Allen --- CHANGELOG.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index 20e8501b7..a18b0a20d 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -34,8 +34,8 @@ For example: On to the gateway, there's a new `Gateway.NoFetch` option to configure the gateway to only serve locally present files. This makes it possible to run an -IPFS node as a gateway to serve content of _your_ choosing (i.e., stuff you've -pinned locally) but no other content. +IPFS node as a gateway to serve content of _your_ choosing without acting like a +public proxy. #### Adding And Pinning Content