#lxmf — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #lxmf, aggregated by home.social.
-
Dat belooft vandaag weer een reticulum dagje te worden.
Gevonden site https://scotmesh.net met veel nieuwe leuke opties oa OTA firmware updates , solar seed p1 firmware , rrc / lxmf koppeling .. oftewel veel nieuw speelgoed. -
Dat belooft vandaag weer een reticulum dagje te worden.
Gevonden site https://scotmesh.net met veel nieuwe leuke opties oa OTA firmware updates , solar seed p1 firmware , rrc / lxmf koppeling .. oftewel veel nieuw speelgoed. -
Dat belooft vandaag weer een reticulum dagje te worden.
Gevonden site https://scotmesh.net met veel nieuwe leuke opties oa OTA firmware updates , solar seed p1 firmware , rrc / lxmf koppeling .. oftewel veel nieuw speelgoed. -
Dat belooft vandaag weer een reticulum dagje te worden.
Gevonden site https://scotmesh.net met veel nieuwe leuke opties oa OTA firmware updates , solar seed p1 firmware , rrc / lxmf koppeling .. oftewel veel nieuw speelgoed. -
Dat belooft vandaag weer een reticulum dagje te worden.
Gevonden site https://scotmesh.net met veel nieuwe leuke opties oa OTA firmware updates , solar seed p1 firmware , rrc / lxmf koppeling .. oftewel veel nieuw speelgoed. -
One Protocol, Many Engines: Reticulum's New Rust Implementations
When I wrote LPWAN Meshes: Reticulum, Where I Landed earlier this year, I covered Reticulum as Mark Qvist’s reference Python implementation: rnsd, Sideband, NomadNet, all built on RNS. That was accurate at the time, and it undersold what was already starting to happen underneath it. Reticulum was never meant to be a Python project. It is a protocol specification, and a protocol specification with only one implementation isn’t decentralised yet, it’s just a single point of failure with good branding.https://web.brid.gy/r/https://gaggl.com/blogs/2026-09-01-one-protocol-many-engines/
-
Sensor Data Over Reticulum: LXMF, Propagation Nodes, and the Low-Power Case
LPWAN Meshes: Reticulum, Where I Landed covered Reticulum as a communications stack: transport-agnostic, cryptographically addressed, built for chat and file transfer over LoRa, packet radio, or whatever medium is available. This post is narrower on purpose: it breaks down the specific mechanics of moving a sensor reading, not a conversation, through Reticulum: which delivery method to pick, what a reading actually costs in packets and bits per second, and what already exists in the open-source community to build on rather than reinvent.https://web.brid.gy/r/https://gaggl.com/blogs/2026-08-19-sensor-telemetry-over-reticulum/
-
Sensor Data Over Reticulum: LXMF, Propagation Nodes, and the Low-Power Case
LPWAN Meshes: Reticulum, Where I Landed covered Reticulum as a communications stack: transport-agnostic, cryptographically addressed, built for chat and file transfer over LoRa, packet radio, or whatever medium is available. This post is narrower on purpose: it breaks down the specific mechanics of moving a sensor reading, not a conversation, through Reticulum: which delivery method to pick, what a reading actually costs in packets and bits per second, and what already exists in the open-source community to build on rather than reinvent.https://fed.brid.gy/r/https://gaggl.com/blogs/2026-08-19-sensor-telemetry-over-reticulum/
-
A #nixos #flake that builds a #derivation that #package & install #nomadnet 0.1.0 & #meshchat 1.1.0 from #github python source code. For #reticulum #network. This is a beta work in progress, done using chatGPT iteratively, and is my first attempt at packaging something for nixos. Time will tell if this holds up. Uses python #setuptools & #buildPythonPackage
#lxmf ver 0.8.0
#rns ver 1.0.0 https://codeberg.org/adingbatponder/reticulum_nixos_flake#nixospackages This is experimental and beta - see readme file for issues
-
If a #reticulum #meshchat instance with a #lxmf address on one computing device has 4 identical #lora #rnodes #rnode interfaces, each with same settings of frequency #spreadingfactor #sf, each rnode having a #directional #yagi #antenna in close vicinity, will transmission to a sender of a #deliveryconfirmation (#downlink) from 1 antenna to the sender's direction, be messed up due to local #collision at rnode 1 of different attempted #acknowledgement signals of the other 3 near rnodes?