From a396ef4ed92756d9a9a4d3f58fa02c76de9998f1 Mon Sep 17 00:00:00 2001 From: Mark Qvist Date: Wed, 3 Jan 2024 12:05:07 +0100 Subject: [PATCH] Updated github build --- docs/start.html | 2 +- docs/start_de.html | 2 +- docs/start_jp.html | 2 +- docs/start_pl.html | 2 +- docs/start_pt-br.html | 2 +- docs/start_tr.html | 2 +- docs/start_zh-cn.html | 2 +- 7 files changed, 7 insertions(+), 7 deletions(-) diff --git a/docs/start.html b/docs/start.html index 158b572..9a4fe4f 100644 --- a/docs/start.html +++ b/docs/start.html @@ -59,7 +59,7 @@ you want to do. For full details and examples, have a look at the PyCA/cryptography, it is important that you read and understand the Cryptographic Primitives section of this site.
Reticulum targets a very 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.
-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.
+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.