A Reticulum Protocol Specification, Extracted from the Implementation
Started by p1ld7a 8279b6a997b08071... ·
Hello all,
I saw this post on Mastodon and thought it might be interesting to share it here as well: https://salemdata.net/johnpress/?p=861
I’m not quite sure what the intended goal of this is
The manual and API reference document everything already.
A read over of Transport.py will tell you the rest of the nuances
This is also littered with mistakes too, and weird text encoding errors. I will cover the mistakes in the next post.
This is getting beyond frustrating to deal with as people seem to just be throwing shit at LLMs for no other reason than they can
Hmm, I personally, do no think that the manual and API reference doc is everything that is ever needed and would definately welcome a formal spec. However, I see that this is quote a big task and needs constant updating as well, since reticulum is still moving rapidly at this point.