aboutsummaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorpukkamustard <pukkamustard@posteo.net>2020-11-28 12:01:10 +0100
committerpukkamustard <pukkamustard@posteo.net>2020-11-28 15:55:06 +0100
commit7f69176d585d7702ca3a7e5a67f2920a52906356 (patch)
tree9099b0dbc6be4304adbec3420033a53e391cec1e /doc
parentab0a4eafa62c9ceafd55c06d344952cc7588b874 (diff)
examples/ipfs.org: A demo on how to use IPFS with ERIS
Diffstat (limited to 'doc')
-rw-r--r--doc/eris.adoc2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/eris.adoc b/doc/eris.adoc
index c754487..6c1ef4a 100644
--- a/doc/eris.adoc
+++ b/doc/eris.adoc
@@ -379,7 +379,7 @@ Transport mechanisms include:
- HTTP: A simple HTTP endpoint can be used to dereference blocks
- Sneakernet: Blocks can be transported on a physical medium such as a USB stick
-More interesting transport and storage layers use the fact that blocks are content-addressed. For example the peer-to-peer network https://ipfs.io/[IPFS] can be used to store and transport blocks (see the https://gitlab.com/openengiadina/eris/-/blob/main/examples/ipfs.scm[example] using the reference Guile implementation). The major advantages over using IPFS directly include:
+More interesting transport and storage layers use the fact that blocks are content-addressed. For example the peer-to-peer network https://ipfs.io/[IPFS] can be used to store and transport blocks (see the https://gitlab.com/openengiadina/eris/-/blob/main/examples/ipfs.org[example] using the reference Guile implementation). The major advantages over using IPFS directly include:
- Content is encrypted and not readable to IPFS peers without the read capability.
- Identifier of blocks and encoded content is not tied to the IPFS network. Applications can transparently use IPFS or any other storage/transport mechanism.