A house is not a building code.

I wrote about using ChatGPT + Codex to derive a protocol specification for Reticulum/LXMF from its Python implementation—turning “look at the source” into something closer to a language-neutral contract, with test vectors to follow.

https://salemdata.net/johnpress/?p=812

#Reticulum #LXMF #Codex #AIcoding #ProtocolDesign #EmbeddedSystems #TBeamSupreme #ESP32

reticulum_nixos_flake/docs/reticulum-great-parcel-game.md at main

reticulum_nixos_flake - Installing reticulum messaging and site tools MeshChat and Nomadnet using NixOS flake

Codeberg.org

@adingbatponder Your explanation is excellent. This kind of high level description ought to help people new to #Reticulum. It would be ideal to tie this into a real specification -- a project I'm about to undertake using thatSFguy's project.

I am at a disadvantage here because I've never heard of https://
wiki.nixos.org/wiki/NixOS [revised URL], I've just focused on Gentoo and whatever other systems I've needed when Gentoo did not have a package for something I wanted to install.

@VogueLaGalere Thanks. It is linked to the reticulum docs 1.3.4 , I hope, but I was not happy with the content of the announces in the allegory... I need to RTFM there more.
@adingbatponder the concept of the old telephone party line comes to mind especially since the radio airwaves are something that one must be careful not to collide with other transmissions. In my testing of several transmitting T-Beams, I think I ran into that problem with the transport unit freely transmitting. I then realize I need to be mindful of avoiding cancellations.