I think Meshtastic will need to change their default settings to be reliable around cities (CLIENT_MUTE).
MeshCore seems to have built this into the design at the expense of some planning and minor infrastructure. As a result MeshCore feels snappier and more reliable in and around cities. I hope we see more adoption!
Great article! I have been playing with Meshtastic a bit and find the hop count restriction frustrating. I understand why it is there, but I bet a little intelligence in the routing/broadcast protocol would go a long way. However, the node names cannot be beat; looking at you “Boats ‘N Hoes” 😉
I think Meshtastic will need to change their default settings to be reliable around cities (CLIENT_MUTE).
MeshCore seems to have built this into the design at the expense of some planning and minor infrastructure. As a result MeshCore feels snappier and more reliable in and around cities. I hope we see more adoption!
Me too. I like the ad-hoc nature of meshtastic, but meshcore should route better for long distance communication. I run a meshcore node also.
Thanks for sharing. Mesh networks for outdoor companions is something I have been thinking about.
Great article! I have been playing with Meshtastic a bit and find the hop count restriction frustrating. I understand why it is there, but I bet a little intelligence in the routing/broadcast protocol would go a long way. However, the node names cannot be beat; looking at you “Boats ‘N Hoes” 😉
🥔 Mesh Potato
Really interesting and cool project
Thanks, Jon, hope you are well!