Updated docs

This commit is contained in:
Mark Qvist 2026-01-10 23:03:55 +01:00
commit ab2ab37844
4 changed files with 22 additions and 22 deletions

View file

@ -45,15 +45,15 @@ could change if absolutely warranted.
Reference Implementation
========================
The Python code, for which this documentation is written, is the Reference Implementation of
Reticulum, and compatibility with the Reticulum protocol is defined as having
full interoperability, and sufficient functional parity with this reference implementation.
The Python code, for which this documentation is written, and known as the Reticulum Network Stack,
is the Reference Implementation of Reticulum. The Reticulum Protocol is defined entirely
and authoritatively by this reference implementation, and this manual. It is maintained by Mark Qvist.
Any specific protocol implementation that achieves this is Reticulum. Any that does
not is not Reticulum.
Compatibility with the Reticulum protocol is defined as having full interoperability,
and sufficient functional parity with this reference implementation. Any specific protocol
implementation that achieves this is Reticulum. Any that does not is not Reticulum.
The protocol design and reference implementation for Reticulum was carried out by Mark Qvist between 2014
and 2022. It is licensed under the :ref:`Reticulum License <license>`.
The reference implementation is licensed under the :ref:`Reticulum License <license>`.
The Reticulum Protocol was dedicated to the public domain in 2016.

File diff suppressed because one or more lines are too long

View file

@ -296,13 +296,13 @@ could change if absolutely warranted.</p>
</section>
<section id="reference-implementation">
<h2>Reference Implementation<a class="headerlink" href="#reference-implementation" title="Link to this heading"></a></h2>
<p>The Python code, for which this documentation is written, is the Reference Implementation of
Reticulum, and compatibility with the Reticulum protocol is defined as having
full interoperability, and sufficient functional parity with this reference implementation.</p>
<p>Any specific protocol implementation that achieves this is Reticulum. Any that does
not is not Reticulum.</p>
<p>The protocol design and reference implementation for Reticulum was carried out by Mark Qvist between 2014
and 2022. It is licensed under the <a class="reference internal" href="license.html#license"><span class="std std-ref">Reticulum License</span></a>.</p>
<p>The Python code, for which this documentation is written, and known as the Reticulum Network Stack,
is the Reference Implementation of Reticulum. The Reticulum Protocol is defined entirely
and authoritatively by this reference implementation, and this manual. It is maintained by Mark Qvist.</p>
<p>Compatibility with the Reticulum protocol is defined as having full interoperability,
and sufficient functional parity with this reference implementation. Any specific protocol
implementation that achieves this is Reticulum. Any that does not is not Reticulum.</p>
<p>The reference implementation is licensed under the <a class="reference internal" href="license.html#license"><span class="std std-ref">Reticulum License</span></a>.</p>
<p>The Reticulum Protocol was dedicated to the public domain in 2016.</p>
</section>
<section id="what-does-reticulum-offer">

View file

@ -45,15 +45,15 @@ could change if absolutely warranted.
Reference Implementation
========================
The Python code, for which this documentation is written, is the Reference Implementation of
Reticulum, and compatibility with the Reticulum protocol is defined as having
full interoperability, and sufficient functional parity with this reference implementation.
The Python code, for which this documentation is written, and known as the Reticulum Network Stack,
is the Reference Implementation of Reticulum. The Reticulum Protocol is defined entirely
and authoritatively by this reference implementation, and this manual. It is maintained by Mark Qvist.
Any specific protocol implementation that achieves this is Reticulum. Any that does
not is not Reticulum.
Compatibility with the Reticulum protocol is defined as having full interoperability,
and sufficient functional parity with this reference implementation. Any specific protocol
implementation that achieves this is Reticulum. Any that does not is not Reticulum.
The protocol design and reference implementation for Reticulum was carried out by Mark Qvist between 2014
and 2022. It is licensed under the :ref:`Reticulum License <license>`.
The reference implementation is licensed under the :ref:`Reticulum License <license>`.
The Reticulum Protocol was dedicated to the public domain in 2016.