aboutsummaryrefslogtreecommitdiff
path: root/content/blog/2022-ipfs
diff options
context:
space:
mode:
authorQuentin Dufour <quentin@deuxfleurs.fr>2022-06-10 17:59:55 +0200
committerQuentin Dufour <quentin@deuxfleurs.fr>2022-06-10 17:59:55 +0200
commitb1ff241de84d4f46d9f522ce096df9c83b355ec3 (patch)
tree12bfa3d73509e4128212338eb9c8ceab1c3e4e33 /content/blog/2022-ipfs
parent7c951f4376d380fb679d0f8a60959f217e4ca5e4 (diff)
downloadgaragehq.deuxfleurs.fr-b1ff241de84d4f46d9f522ce096df9c83b355ec3.tar.gz
garagehq.deuxfleurs.fr-b1ff241de84d4f46d9f522ce096df9c83b355ec3.zip
Add an adjective
Diffstat (limited to 'content/blog/2022-ipfs')
-rw-r--r--content/blog/2022-ipfs/index.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/content/blog/2022-ipfs/index.md b/content/blog/2022-ipfs/index.md
index 848778d..64695e6 100644
--- a/content/blog/2022-ipfs/index.md
+++ b/content/blog/2022-ipfs/index.md
@@ -178,7 +178,7 @@ Furthermore, we are not hammering anymore our backend with requests on objects t
After discussing with the developpers, it is possible to go even further by running Peergos without IPFS:
this is what they do for some of their tests. At the same time, if you increase the size
-of a block, you might have a non-federated but efficient end-to-end encrypted "cloud storage" that works over Garage,
+of a block, you might have a non-federated but efficient end-to-end encrypted "cloud storage" that works well over Garage,
with your clients directly hitting the S3 API!
If federation is a hard requirement for your, the next step would be to gradually allowing back our node to connect to the IPFS network,