Post #1792218
2026-04-29 11:54 UTC
Replies (5)
-
@CarstenBoll@mstdn.dk 2026-04-29 12:55
@kimschulz@social.data.coop @schulz.dk I'm actually not super convinced that Reticulum is so hard for regular people, I mean people who can install a program om their computer or their phone. Installing RNS and MeshChatX or NomadNet is not a lot more complicated than it is to flash a LoRa device with some firmware. Now, I haven't gotten into using LoRa with Reticulum yet, might very well be too complicated, but we'll see when I get to it.
-
@kineticdiplomacy@infosec.exchange 2026-04-29 12:05
@kimschulz@social.data.coop @schulz.dk That's a great writeup, and seems to line up with my own vibes so far. It feels like the tech just isn't there yet.
-
@blackforestmesh@freiburg.social 2026-04-29 12:34
@kimschulz@social.data.coop „they (Companions) only speak directly to Repeaters.“ - that’s not entirely correct… companions can talk to each other when in range and you can also configure them to act as repeaters for a more Meshtastic way of working, but on another frequency as the main mesh network.
-
@ratcatcher@beige.party 2026-04-29 14:20
@kimschulz@social.data.coop How does the ad hoc "Enable Repeat Mode" on a #Meshcore companion device work? Not sure how that fits into the dedicated roles thing. Does it act as a fully functioning repeater AND companion device (like Meshtastic)?
-
@1337@techhub.social 2026-04-29 15:59
@kimschulz@social.data.coop @blog One problem with Meshtastic that we see in my area is that the device with the lowest SNR repeats first. This is used as a proxy for "farthest node," but often, it's just a node with poor placement which causes reliability problems. Meshcore is much more reliable in my area. I think Meshcore is best for a group that can provide good, stable, "infrastructure," and Meshtastic is best for traveling/adhoc networks. I still don't fully understand Reticulum :)