rt/Reticulum
1
0
Fork 0
mirror of https://github.com/markqvist/Reticulum.git synced 2026-10-25 18:40:17 -04:00
Code Issues Projects Releases Packages Wiki Activity Actions

Updated docs

Browse source
This commit is contained in:
Mark Qvist 2026-09-20 01:55:25 +02:00
parent 15e6dd4a88
commit 395241b190
No known key found for this signature in database
2 changed files with 4 additions and 4 deletions
Download patch file Download diff file Expand all files Collapse all files

6
docs/history/2026_09_18_Yes_I_am_Angry.md
View file

@ -210,7 +210,7 @@ Oooooh... Tension. Drama. Tell me more, let's have the juicy details, huh? Outra
The only thing that keeps coming back here is nonsense.
The decisions follow those responsible, over years, and actual the work. Not cry-babies like you. Get used to it.
The decisions follow those responsible, over years, and the actual work. Not cry-babies like you. Get used to it.
> Relicensing a codebase other people contributed to, under MIT terms, with a single unilateral commit, is itself a small act of enclosure.
@ -220,13 +220,13 @@ But your ideology runs so deep now, *that we cannot ourselves decide how we lice
It's *almost* like you've decided you already personally own Reticulum.
> The pattern shows up off the codebase too. In late August 2026, after a badly-behaved crawler hammered **his** NomadNet git node with tens of thousands of requests
> The pattern shows up off the codebase too. In late August 2026, after a badly-behaved crawler hammered his NomadNet git node with tens of thousands of requests
Ah yes, so I got personally mad because it hit *my* node, and had a tantrum?
The scraper was hitting *every node across the entire fucking intermesh*, from a high-bandwidth VPS, with no throttling, no regards for people's radio links, airtime concerns, metered connections or limited compute resources.
For what reason? To gouge **millions** of requests to a broken piece of shit software that an idiot deployed and left running without oversight, trying to infintely download **everything that everyone had ever put on their nodes several times over** on a recursive loop.
For what reason? To gouge tens of **millions** of requests to a broken piece of shit software that an idiot deployed and left running without oversight, trying to infintely download **everything that everyone had ever put on their nodes several times over** on a recursive loop.
Who made that stop? I did, because I contacted the idiot and talked him out of it.

2
docs/source/brandolinis.rst
View file

@ -1079,7 +1079,7 @@ Purpose & Scope
This section provides a concrete example, which future evaluations can use as a template. Its purpose is not to be the last word on this particular subject, but to be an example of how the ideas in this chapter can be applied, and to make the next such examination easier.
The subject of this case study is **Prns**\ , a project published at the repository ``github.com/KenAKAFrosty/Prns``\ , presented as a "ground-up implementation of Reticulum, written in Rust", marketed as faster, safer, and more strictly tested than the reference, and widely promoted with the claim of "up to 89× the throughput" of the reference implementation. The record described below is the project's own, and sourced from its GitHub repository, analyzed locally.
The subject of this case study is **Prns**, a project published at the repository ``github.com/KenAKAFrosty/Prns``, presented as a "ground-up implementation of Reticulum, written in Rust", marketed as faster, safer, and more strictly tested than the reference, widely promoted with the claim of "up to 89× the throughput" of the reference implementation, and an "author" actively engaged in the tactics described in :ref:`A Movement Of A Dozen<brandolinis-recycled-wine>` on online platforms. The record described below is the project's own, and sourced from its GitHub repository, analyzed locally.
.. _brandolinis-project-in-brief: