From 078dcc88a9c9f0d883d6b7d9615abb9f7543a817 Mon Sep 17 00:00:00 2001 From: John Turpish <97759690+John-LittleBearLabs@users.noreply.github.com> Date: Mon, 22 May 2023 14:21:03 -0400 Subject: [PATCH] Update src/_blog/2023-05-multi-gateway-browser-client.md Co-authored-by: Marcin Rataj --- src/_blog/2023-05-multi-gateway-browser-client.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/_blog/2023-05-multi-gateway-browser-client.md b/src/_blog/2023-05-multi-gateway-browser-client.md index 6d9e77a5..233f9be0 100644 --- a/src/_blog/2023-05-multi-gateway-browser-client.md +++ b/src/_blog/2023-05-multi-gateway-browser-client.md @@ -47,7 +47,7 @@ Or preferably (when [Origin isolation](https://en.wikipedia.org/wiki/Same-origin >[https://bafybeihpy2n6vwt2jjq5gusv23ajtilzbao3ekfb2hiev2xvuxscdxqcp4.ipfs.dweb.link/](https://bafybeihpy2n6vwt2jjq5gusv23ajtilzbao3ekfb2hiev2xvuxscdxqcp4.ipfs.dweb.link/) -In each case, you're delegating all the "IPFS stuff" to a particular node. This is effective for completing requests, but has some trade-offs. +In each case, you're delegating all the "IPFS stuff", including CID (hash) verification, to a particular node. This is effective for completing requests, but has some trade-offs, including the privacy and integrity risks when using a remote gateway provided by a third-party. ### Performance