I have a few LoRa radios running Meshtastic and they're fun to play with, but I wouldn't rely on them in a critical situation. It's too easy to accidentally configure a node incorrectly and cause problems for nearby nodes.

Perhaps someday the project will settle on a handful of sensible presets for different use cases. Even better would be if more of the options were managed dynamically by the software itself, things like adjusting timeouts and hops based on current network utilization and previous transmission success rate, or automatically tweaking the role based on the current mesh toplolgy, that sort of thing.

regional meshes may have suggested configuration. for example bay area mesh https://bayme.sh/docs/getting-started/recommended-settings/

i installed a node week ago. honestly, it is somewhat underwhelming