From 156ce9cd34420dd06985746bb530c8fff006316e Mon Sep 17 00:00:00 2001 From: Mark Qvist Date: Thu, 25 Jun 2026 21:17:34 +0200 Subject: [PATCH] Updated readme --- README.md | 12 ++++++------ README.mu | 8 ++++---- 2 files changed, 10 insertions(+), 10 deletions(-) diff --git a/README.md b/README.md index d63c0e38..2e2f8b2e 100755 --- a/README.md +++ b/README.md @@ -85,16 +85,16 @@ The Reticulum Protocol is defined entirely and authoritatively by this reference implementation, and its associated manual. It is maintained by Mark Qvist, identified by the Reticulum Identity ``. +No second-order protocol specification derivatives currently do, or will ever exist. You can't get a better specification than one that is executable, functional, testable, deployed and operating 24/7 across the planet. + +There is not, and never will be a separate, derived "formal spec", "RFC" or anything similar for Reticulum: + +**The reference implementation *is* the final, authoritative specification.** + 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. -No second-order protocol specification derivatives currently do, or will ever exist. You cannot get a better specification, than one that is executable, functional, testable, deployed and operating 24/7 across the planet. - -There is not, and never will be an "official" external, derived "formal spec", "RFC" or anything similar for Reticulum: - -**The reference implementation *is* the final, authoritative specification.** - The reference implementation is licensed under the Reticulum License. The Reticulum Protocol was dedicated to the Public Domain in 2016. diff --git a/README.mu b/README.mu index f22a67e4..2d361909 100644 --- a/README.mu +++ b/README.mu @@ -58,14 +58,14 @@ You can also download the `_`!`[Reticulum manual as a PDF`:/file/artifact`g=reti The Python code in this repository is the Reference Implementation of Reticulum. The Reticulum Protocol is defined entirely and authoritatively by this reference implementation, and its associated manual. It is maintained by Mark Qvist, identified by the Reticulum Identity `B333`b. -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. +No second-order protocol specification derivatives currently do, or will ever exist. You can't get a better specification than one that is executable, functional, testable, deployed and operating 24/7 across the planet. -No second-order protocol specification derivatives currently do, or will ever exist. You cannot get a better specification, than one that is executable, functional, testable, deployed and operating 24/7 across the planet. - -There is not, and never will be an "official" external, derived "formal spec", "RFC" or anything similar for Reticulum: +There is not, and never will be a separate, derived "formal spec", "RFC" or anything similar for Reticulum: `!The reference implementation `*is`* the final, authoritative specification.`! +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 reference implementation is licensed under the Reticulum License. The Reticulum Protocol was dedicated to the Public Domain in 2016.