# microReticulum Updates and Technical Discussion _Build Guides · started by gdane on Sat, May 23, 2026 3:23 PM_ Tags: Question, Discussion, Help --- ## Original post **gdane** · Sat, May 23, 2026 3:23 PM Welcome to the **microReticulum Updates and Technical Discussion** thread. This thread serves as the central place for announcements related to new microReticulum releases, including bug fixes, new features, performance improvements, compatibility changes, and development milestones. In addition to release updates, the thread is open for technical discussion covering topics such as architecture and design decisions, implementation details, integrations, troubleshooting, optimization, deployment experiences, and general development feedback. Whether you are following project progress, testing new releases, integrating microReticulum into your own applications, or contributing ideas and improvements, you are encouraged to participate in the discussion. Note that discussions are expected to remain respectful, constructive, and productive. Offensive, disruptive, or non-constructive posts may be removed in order to maintain a healthy and collaborative community environment. Let's build together! [microReticulum GitHub Repo](https://github.com/attermann/microReticulum) --- ## Reply 1 **gdane** · Sat, May 23, 2026 3:37 PM A quick announcement... I know there has been a lot of interest in `Resource` support in microReticulum over the past months (even years), and I'm happy to announce that it has finally arrived! I've also added an example project `nomadnet` in the repo that demonstrates a very basic NomadNet client and server. Note however that microReticulum presently does not have support for compressed content, so most pages delivered by standard NomadNet will fail to be received unless compression is disabled. The reason for this omission lies in the compression algorithm bz2 used by RNS which is *extremely* resource-intensive and not embedded-friendly at all, but this is a discussion for another day. Note that `Resource` support is currently only available in the `master` branch of the microReticulum repo and not in any release (yet). Please treat it as "experimental" for the time being while we work to get more interop testing behind us. In the meantime, feel free to play. Cheers! --- ## Reply 2 **daylight-hub** · Sat, May 23, 2026 6:08 PM Is there a way that the microReticulum transport nodes can show up in my network visualization panel on MeshchatX which is connected to a standard RNode? It would be great to confirm that the transport node is indeed up and running. --- ## Reply 3 **Zenith** · Sat, May 23, 2026 6:16 PM **gdane** wrote: > A quick announcement... > > I know there has been a lot of interest in `Resource` support in microReticulum over the past months (even years), and I'm happy to announce that it has finally arrived! > > I've also added an example project `nomadnet` in the repo that demonstrates a very basic NomadNet client and server. Note however that microReticulum presently does not have support for compressed content, so most pages delivered by standard NomadNet will fail to be received unless compression is disabled. The reason for this omission lies in the compression algorithm bz2 used by RNS which is *extremely* resource-intensive and not embedded-friendly at all, but this is a discussion for another day. > > Note that `Resource` support is currently only available in the `master` branch of the microReticulum repo and not in any release (yet). Please treat it as "experimental" for the time being while we work to get more interop testing behind us. In the meantime, feel free to play. > > Cheers! This is so awesome. Great work Attermann!!! As a side note, for any LXMF implementations in the future that target microControllers where bzip isn't possible - there is compression support signalling with the `SF_COMPRESSION` flag :) https://github.com/markqvist/LXMF/commit/72932eea28074420defd02b6eb3e5e09a126e4ee --- ## Reply 4 **Anonymous** · Sun, May 24, 2026 12:30 AM **daylight-hub** wrote: > Is there a way that the microReticulum transport nodes can show up in my network visualization panel on MeshchatX which is connected to a standard RNode? It would be great to confirm that the transport node is indeed up and running. Not yet, but that has actually been the motivation behind finally getting Resource implemented, so that transport nodes can have a mechanism to share instrumentation with other nodes on the network. I haven't decide if I will implement a NomadNet-type interface, or extend the existing management endpoints already in RNS and recently (partially, wip) implemented in microReticulum. Of course you don't have to wait for me either. You could roll your own firmware based on microReticulum_Firmware, and add in whatever endpoint you like using microReticulum code and the `nomednet` example as a guide. --- ## Reply 5 **Anonymous** · Sun, May 24, 2026 12:31 AM **Zenith** wrote: > **gdane** wrote: > > A quick announcement... > > > > I know there has been a lot of interest in `Resource` support in microReticulum over the past months (even years), and I'm happy to announce that it has finally arrived! > > > > I've also added an example project `nomadnet` in the repo that demonstrates a very basic NomadNet client and server. Note however that microReticulum presently does not have support for compressed content, so most pages delivered by standard NomadNet will fail to be received unless compression is disabled. The reason for this omission lies in the compression algorithm bz2 used by RNS which is *extremely* resource-intensive and not embedded-friendly at all, but this is a discussion for another day. > > > > Note that `Resource` support is currently only available in the `master` branch of the microReticulum repo and not in any release (yet). Please treat it as "experimental" for the time being while we work to get more interop testing behind us. In the meantime, feel free to play. > > > > Cheers! > > This is so awesome. Great work Attermann!!! > > As a side note, for any LXMF implementations in the future that target microControllers where bzip isn't possible - there is compression support signalling with the `SF_COMPRESSION` flag :) > > https://github.com/markqvist/LXMF/commit/72932eea28074420defd02b6eb3e5e09a126e4ee Awesome thanks for the heads-up. That would be a really nice addition to NomadNet too. --- ## Reply 6 **Zenith** · Sun, May 24, 2026 12:58 AM That could probably be done too. In the long run, I think it would be very nice to see some type of feature flag happen on the link level, and maybe even options for different compression like zstd. Much like how MTU is negotiated. --- ## Reply 7 **Torlando** · Sun, May 24, 2026 5:03 AM **gdane** wrote: > A quick announcement... > > I know there has been a lot of interest in `Resource` support in microReticulum over the past months (even years), and I'm happy to announce that it has finally arrived! > > I've also added an example project `nomadnet` in the repo that demonstrates a very basic NomadNet client and server. Note however that microReticulum presently does not have support for compressed content, so most pages delivered by standard NomadNet will fail to be received unless compression is disabled. The reason for this omission lies in the compression algorithm bz2 used by RNS which is *extremely* resource-intensive and not embedded-friendly at all, but this is a discussion for another day. > > Note that `Resource` support is currently only available in the `master` branch of the microReticulum repo and not in any release (yet). Please treat it as "experimental" for the time being while we work to get more interop testing behind us. In the meantime, feel free to play. > > Cheers! Awesome! I spent a few cycles in the last few weeks grafting pyxis onto microReticulum 0.3.0, since I had formed it back in December or something, and you had much nicer solutions for several of the problems I had to solve along the way to get it working. Will happily spend a few more using your Resource implementation! ---