Discord

What the Discord Is For

The server exists to make it easier for local people to work on mesh networking, radio experimentation, coverage testing, and practical communications infrastructure together.

A useful network is not just a pile of devices. It needs people sharing what they learn, writing things down, helping beginners, checking whether systems still work, and turning individual tests into community knowledge.

• Ask beginner questions.
• Share node and device notes.
• Coordinate field testing.
• Report what you can hear from different places.
• Discuss MeshCore, Meshtastic, GMRS, ham radio, CB, FRS, and MURS.
• Plan workshops, radio basics sessions, and local demonstrations.
• Track public project updates and soft-launch work.

A Good First Post

A first post does not need to be formal. Something simple is enough.

Mentioning your general area is useful. You do not need to share a private address. Town, neighborhood, or general region is enough.

Useful Channel Types

The exact channel names may change as the server develops, but the basic idea should stay simple.

Welcome and rules

Start here. These channels explain what the server is, how to use it, and what behavior is expected.

Announcements and project updates

For major project updates, soft-launch notes, website changes, planned testing, infrastructure updates, and community sessions.

Node help

For device setup, firmware questions, antenna questions, power issues, MeshCore, Meshtastic, and troubleshooting.

Coverage reports

For field test notes: what was heard, where you tested from, what device and antenna you used, and what conditions were like.

Radio basics

For FRS, GMRS, MURS, CB, Amateur Radio, licensing questions, operating practice, local nets, and beginner radio topics.

Events and workshops

For planning radio basics sessions, “what is mesh?” talks, build nights, library events, club presentations, or informal meetups.

Sharing Coverage Reports

Coverage reports are one of the most useful things people can share. They help the project understand what is reachable from real places, not just what should work on paper.

A useful report includes:

• Date and approximate time.
• General location or public landmark.
• Device used.
• Antenna and placement.
• Power source, if relevant.
• Service or mode tested.
• What was heard.
• What was not heard.
• Terrain, buildings, trees, weather, or other useful notes.

Asking for Node Help

When asking for help with a device, include enough information that someone else can understand the setup.

• Device model.
• Firmware or software version, if known.
• What you are trying to do.
• What already works.
• What is failing.
• Any error messages or logs.
• Antenna and power setup.
• Computer or phone operating system, if relevant.

Photos can help, but check them first. Do not post passwords, private keys, private addresses, or screens with personal information.

Privacy and Safety

Keep reports useful without oversharing. The project benefits from local knowledge, but people should not feel pressured to publish private details.

• Use general locations unless exact location sharing is intentional.
• Do not post someone else’s address or private property details.
• Remove location metadata from photos when needed.
• Do not post private keys, passwords, account tokens, or screenshots showing sensitive details.
• Do not trespass or create safety problems for a radio test.
• Follow the rules for whatever radio service you are using.

Expected Conduct

The server should be useful for beginners and experienced operators. That means keeping the tone practical, patient, and clear.

• Beginner questions are welcome.
• Explain things without talking down to people.
• Disagree with ideas without attacking people.
• Keep emergency claims realistic.
• Do not present the project as an official public safety service.
• Respect privacy, licensing rules, and local law.
• Help turn answers into documentation when possible.

A strong communications project depends on trust. People are more likely to learn, test, and contribute when the space is useful and approachable.

Discord as Project Infrastructure

Discord is not the mesh network itself. It is coordination infrastructure. It helps people organize work around the network.

Over time, the server may be used for:

• Manual status updates.
• Coverage report collection.
• GitHub update notifications.
• Workshop planning.
• Node setup help.
• Public data and map update announcements.

Automated bot integrations may come later, but the first goal is simpler: make sure people have a clear place to ask, report, learn, and coordinate.

Joining

The public invite may change over time. Use the current link on the homepage when joining.