Git-Mirrors/reticulum_website
1
0
Fork 0
mirror of https://github.com/markqvist/reticulum_website.git synced 2025-08-09 15:02:12 -04:00
Code Issues Projects Releases Packages Wiki Activity Actions

Updated github build

Browse source
This commit is contained in:
Mark Qvist 2024-01-03 12:05:07 +01:00
parent 54137870d4
commit a396ef4ed9
7 changed files with 7 additions and 7 deletions
Download patch file Download diff file Expand all files Collapse all files

2
docs/start.html
View file

@ -59,7 +59,7 @@ you want to do. For full details and examples, have a look at the <a href="manua
<p><strong>Please Note!</strong> If you use the <code>rnspure</code> package to run Reticulum on systems that do not support <a href="https://github.com/pyca/cryptography">PyCA/cryptography</a>, it is important that you read and understand the <a href="crypto.html">Cryptographic Primitives</a> section of this site.</p>
<h2>Performance</h2>
<p>Reticulum targets a <em>very</em> wide usable performance envelope, but prioritises functionality and performance over low-bandwidth mediums. The goal is to provide a dynamic performance envelope from 250 bits per second, to 1 gigabit per second on normal hardware.</p>
<p>Currently, the usable performance envelope is approximately 500 bits per second to 20 megabits per second, with physical mediums faster than that not being saturated. Performance beyond the current level is intended for future upgrades, but not highly prioritised until the wire format and API has been locked in.</p>
<p>Currently, the usable performance envelope is approximately 150 bits per second to 40 megabits per second, with physical mediums faster than that not being saturated. Performance beyond the current level is intended for future upgrades, but not highly prioritised until the wire format and API has been locked in.</p>
<p align="right"><a href="hardware.html">Next Topic: Supported Hardware</a></p>
</body>
</html>