Post #3835431
2026-07-15 12:38 UTC
my local mesh is switching to meshcore. i am open to change, but i have been unable to find the answer to the question of: "why is meshcore better and why couldn't the improvements been added to meshtastic?". just like 2 sentences, that's all i wanna know.
because although i'm not an RF expert, developing a competing (non-compatible, right?) standard in crowded, public bands ought to have been done for a VERY good reason.
#meshcore #meshtastic
Replies (1)
-
@marsik@witter.cz 2026-07-15 13:01
@tyzbit@toot.now MeshCore defaults are tailored towards infrastructure and more users. Only well placed nodes are repeaters and telemetry is limited. Meshtastic focuses on ad-hoc small groups in places without infrastructure. That is why clients repeat and send more telemetry. Use CLIENT_MUTE, limit telemetry, set faster preset and you get almost the same thing. Tech note: I like protobuf tag based packets in MT more (vs hand coded in MC). And MC author did not like GPL: https://buymeacoffee.com/ripplebiz/meshtastic-a-dead-end