Post #1698733
2026-04-21 06:38 UTC
Replies (5)
-
@CarstenBoll@mstdn.dk 2026-04-21 06:43
@kimschulz@social.data.coop Currently, it seems to me that most Meshtastic people are moving to MeshCore. Have you looked into that? :)
-
@soeren@floss.social 2026-04-21 09:34
@kimschulz@social.data.coop Do you recommend any of these for a total newcomer to #reticulum? https://reticulum.network/manual/hardware.html#rnode-supported Or should I look at something else? It seems quite overwhelming picking the "right" one(s).
-
@MrManor@social.data.coop 2026-04-22 05:40
@kimschulz@social.data.coop Interesting read. I'm still on the fence observing some of my friends playing with Meshtastic.
-
To answer the question post at the end of the blog post, I am doing a bit of both. We haven't hit the wall on meshtastic usage around here, although I am starting to go to mesh core because it's much simpler and uses the airwaves a little more cleanly. Reticulum is something I've played with and enjoy from what I've seen of it so far, but it definitely could use some polish to make it simpler for the average person to use. I'm also waiting on some more things to be able to be done over reticulum. For example, I found out the other day that through an application pair called RServer and MeshBrowser you can do HTTP over reticulum. nomadNet is great, but many more people understand HTTP, or at least how to build websites for HTTP.
-
@marsik@witter.cz 2026-04-29 14:51
@kimschulz@social.data.coop Reticulum is not perfect either. It encrypts everything and uses pre-negotiated links. So far so good. Sadly there are possible de-anonymization attack vectors I found when digging around in the code and protocol: https://witter.cz/@marsik/116458707129395348 The Meshcore model is semi-commercial indeed and the lack of a clear protocol description prevents alternative open firmwares from being implemented reliably. As a HAM I prefer open plaintext APRS and Winlink for the off grid emergency messaging.