aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorpukkamustard <pukkamustard@posteo.net>2021-09-19 19:34:42 +0200
committerpukkamustard <pukkamustard@posteo.net>2021-09-19 19:34:42 +0200
commitf7eeea4aba15cab9e26d81c27407ab617428e1f1 (patch)
tree9f8733c07a1eddafb48c0508dcf7dc5515850890
parentb44ff1dde6d2ba7d65781491ca2061a6ed0b7cbd (diff)
spec: Link to eris and guile-eris repository on inqlab.net (instead of Gitlab)
-rw-r--r--public/index.html10
-rw-r--r--spec/eris.adoc8
2 files changed, 9 insertions, 9 deletions
diff --git a/public/index.html b/public/index.html
index 68baa52..f495317 100644
--- a/public/index.html
+++ b/public/index.html
@@ -1394,7 +1394,7 @@ If the length of the last content block is exactly block size, then padding will
<p>The encoding process can be implemented to encode a stream of content while immediately outputting encrypted blocks when ready and eagerly collecting reference-key pairs to nodes. This allows the encoding of larger-than-memory content.</p>
</div>
<div class="paragraph">
-<p>For an example, see <a href="https://gitlab.com/openengiadina/eris/-/raw/main/eris/encode.scm">the reference Guile implementation</a>.</p>
+<p>For an example, see <a href="https://inqlab.net/git/guile-eris.git/tree/eris/encode.scm">the reference Guile implementation</a>.</p>
</div>
</div>
</div>
@@ -1434,7 +1434,7 @@ ERIS-Decode(BLOCK-SIZE, LEVEL, ROOT-REFERENCE, ROOT-KEY):
</dl>
</div>
<div class="paragraph">
-<p>A streaming decoding procedure can be implemented where the content can be output block wise and does not need to be kept in memory for unpadding. For an example, see <a href="https://gitlab.com/openengiadina/eris/-/raw/main/eris/decode.scm">the reference Guile implementation</a>.</p>
+<p>A streaming decoding procedure can be implemented where the content can be output block wise and does not need to be kept in memory for unpadding. For an example, see <a href="https://inqlab.net/git/guile-eris.git/tree/eris/decode.scm">the reference Guile implementation</a>.</p>
</div>
<div class="sect3">
<h4 id="_random_access"><a class="anchor" href="#_random_access"></a>2.5.1. Random Access</h4>
@@ -1584,7 +1584,7 @@ ERIS-Decode(BLOCK-SIZE, LEVEL, ROOT-REFERENCE, ROOT-KEY):
</ul>
</div>
<div class="paragraph">
-<p>More interesting transport and storage layers use the fact that blocks are content-addressed. For example the peer-to-peer network <a href="https://ipfs.io/">IPFS</a> can be used to store and transport blocks (see the <a href="https://gitlab.com/openengiadina/eris/-/blob/main/examples/ipfs.org">example</a> using the reference Guile implementation). The major advantages over using IPFS directly include:</p>
+<p>More interesting transport and storage layers use the fact that blocks are content-addressed. For example the peer-to-peer network <a href="https://ipfs.io/">IPFS</a> can be used to store and transport blocks (see the <a href="https://inqlab.net/git/guile-eris.git/tree/examples/ipfs.org">example</a> using the reference Guile implementation). The major advantages over using IPFS directly include:</p>
</div>
<div class="ulist">
<ul>
@@ -1648,7 +1648,7 @@ ERIS-Decode(BLOCK-SIZE, LEVEL, ROOT-REFERENCE, ROOT-KEY):
<div class="sect2">
<h3 id="_machine_readable"><a class="anchor" href="#_machine_readable"></a>4.1. Machine Readable</h3>
<div class="paragraph">
-<p>A set of test vectors are provided in the <a href="https://gitlab.com/openengiadina/eris/-/tree/main/test-vectors">ERIS repository</a>. Implementations of the ERIS encoding MUST be able to satisfy the test vectors.</p>
+<p>A set of test vectors are provided in the <a href="https://inqlab.net/git/guile-eris.git/tree/test-vectors">ERIS repository</a>. Implementations of the ERIS encoding MUST be able to satisfy the test vectors.</p>
</div>
<div class="paragraph">
<p>The test vectors are given as machine-readable JSON files. For example the test vector <code>eris-test-vector-00.json</code>:</p>
@@ -2057,7 +2057,7 @@ ERIS-Decode(BLOCK-SIZE, LEVEL, ROOT-REFERENCE, ROOT-KEY):
</div>
<div id="footer">
<div id="footer-text">
-Last updated 2021-09-15 12:26:26 +0200
+Last updated 2021-09-19 19:30:54 +0200
</div>
</div>
</body>
diff --git a/spec/eris.adoc b/spec/eris.adoc
index be7cb56..42d9417 100644
--- a/spec/eris.adoc
+++ b/spec/eris.adoc
@@ -304,7 +304,7 @@ Collect-RK-Pairs(INPUT-RK-PAIRS, CONVERGENCE-SECRET, BLOCK-SIZE):
The encoding process can be implemented to encode a stream of content while immediately outputting encrypted blocks when ready and eagerly collecting reference-key pairs to nodes. This allows the encoding of larger-than-memory content.
-For an example, see https://gitlab.com/openengiadina/eris/-/raw/main/eris/encode.scm[the reference Guile implementation].
+For an example, see https://inqlab.net/git/guile-eris.git/tree/eris/encode.scm[the reference Guile implementation].
=== Decoding
@@ -333,7 +333,7 @@ Where the block-storage can be accessed as follows:
`Block-Storage-Get(REFERENCE)` :: Returns a block such that `Blake2b-256(Block-Storage-Get(REFERENCE)) == REFERENCE` or throws an error.
-A streaming decoding procedure can be implemented where the content can be output block wise and does not need to be kept in memory for unpadding. For an example, see https://gitlab.com/openengiadina/eris/-/raw/main/eris/decode.scm[the reference Guile implementation].
+A streaming decoding procedure can be implemented where the content can be output block wise and does not need to be kept in memory for unpadding. For an example, see https://inqlab.net/git/guile-eris.git/tree/eris/decode.scm[the reference Guile implementation].
==== Random Access
@@ -403,7 +403,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.org[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://inqlab.net/git/guile-eris.git/tree/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.
@@ -435,7 +435,7 @@ We believe that the best suited mechanism for handling mutability depends on con
=== Machine Readable
-A set of test vectors are provided in the https://gitlab.com/openengiadina/eris/-/tree/main/test-vectors[ERIS repository]. Implementations of the ERIS encoding MUST be able to satisfy the test vectors.
+A set of test vectors are provided in the https://inqlab.net/git/guile-eris.git/tree/test-vectors[ERIS repository]. Implementations of the ERIS encoding MUST be able to satisfy the test vectors.
The test vectors are given as machine-readable JSON files. For example the test vector `eris-test-vector-00.json`: