Community etiquette
A shared radio network works only if everyone treats the airwaves with care. LoRa has very little bandwidth, so small habits make a big difference.
The short version
- Be kind. Treat everyone the way you would on the street.
- Keep messages short and don't flood the channel.
- Don't share private information on public channels.
- Leave settings at their defaults unless you know why you're changing them.
- Ask before putting up shared infrastructure.
On any mesh channel
- Assume public channels are public. Don't post addresses, phone numbers, travel plans, or anything you wouldn't say on a street corner. Anyone with the channel key can read it.
- Keep it short. Bandwidth is tiny. Skip long messages, repeated “testing” messages, and chain posts. A single test is plenty.
- Don't spam. Keep position and telemetry updates at sensible intervals. Frequent broadcasts use up airtime that everyone shares.
- Protect others' privacy. Don't post other people's locations, real names, or private conversations.
- Use a friendly node name. A nickname is fine. Avoid offensive names and don't put private details in it.
- Be patient with newcomers. Everyone starts out confused. Answer questions kindly.
- Don't rely on it for emergencies. Call 911 first.
Meshtastic
- Stay on the Client role. Router and Repeater roles rebroadcast aggressively, and the project advises against them unless you have a specific reason and a strategic location. Too many cause collisions and shorter effective range.
- Use Client Mute for extra nodes. If you have several nodes, let only one or two relay.
- Leave the hop limit at 3. Raising it tends to increase congestion. Fix placement first.
- Match the local settings. Use the region and modem preset listed on the St. Paul page. Don't change shared settings on a community node without telling the group.
- Be careful with location and MQTT. Position sharing reveals where you are to everyone on the channel, and public MQTT can publish node locations online.
MeshCore
- Start with a companion. Companions don't relay other people's traffic by default, so they're safe to run anywhere. Leave the separate “off-grid” repeat mode off on the public mesh.
- Coordinate repeaters. Repeaters are shared infrastructure. Talk to the local group before putting one up so placement and settings fit the network.
- Use official firmware and tools from meshcore.io.
- Change default passwords on room servers and repeaters, and don't share admin access widely.
Hosting a node for the community
- Get permission from the property owner.
- Keep it maintained: check batteries, connectors, and firmware, and fix it or take it down if it stops working.
- Give the group a way to contact you and note its location, height, and role.
- If you move or remove it, tell people. Others may depend on it.
Voice repeaters (ham and GMRS)
- Listen first. Make sure the repeater is free before you transmit.
- Identify properly. Give your call sign as the rules require. See the ham and GMRS pages.
- Keep transmissions short and leave gaps so others can join.
- Yield to emergencies. Stop at once if someone has urgent traffic.
- Respect closed repeaters. Some repeaters are private. Ask the owner for permission before using one that isn't listed as open.
- Be courteous on nets. Wait for net control, and don't interrupt a scheduled net.
Illegal or harmful content has no place on any of these networks. If someone is in danger, contact the authorities.
Sources
- Meshtastic configuration tips
- Meshtastic: choosing the right device role
- MeshCore FAQ (official docs)
- Meshtastic LoRa configuration
These pages are general guidance gathered from project documentation and community sources, last reviewed November 17, 2026. Firmware and apps change, so check each project's current docs.