Sharing Safely

Share what helps explain the problem

Good troubleshooting information usually includes the device, firmware, antenna, settings, general location, and what happened. It rarely requires an exact private address, account details, or a complete unedited screenshot.

Before posting, ask whether each visible detail helps another person understand the equipment or result. Crop or remove anything that does not.

Useful information to include

Enough technical context makes it easier for other people to help without requiring unnecessary personal information.

Device

The radio model, firmware version, companion application, and any relevant hardware revision.

Radio setup

Antenna type, connector or adapter, power source, and whether the device was indoors, outdoors, in a vehicle, or mounted higher up.

Settings

The selected region, preset, frequency, role, channel, or other setting directly related to the question.

General area

A town, neighborhood, public landmark, road corridor, hill, or broad testing area is usually enough.

What happened

Describe what you expected, what actually happened, and whether the device heard any contacts, adverts, messages, or packets.

What you tried

Mention restarts, firmware changes, alternate antennas, different locations, or settings you already checked.

Check screenshots and photos

Images often include more information than the person posting them notices at first.

Files can contain hidden details

A photo, exported configuration, log, or diagnostic file may contain more information than appears on the screen.

Photo metadata

Some image files may include capture time, device information, or GPS coordinates. Remove unnecessary metadata before publicly posting photos taken at a private location.

Configuration exports

Review exported settings for channel keys, Wi-Fi credentials, broker details, device secrets, and administrative information.

Logs

Logs may contain node identifiers, usernames, filesystem paths, IP addresses, hostnames, coordinates, or message contents.

QR codes

A QR code may contain a channel configuration, key, invitation, Wi-Fi password, or another value that is not obvious from the image alone.

When possible, copy only the relevant lines into a message rather than uploading an entire configuration or log file.

Choose the right amount of location detail

The appropriate level of detail depends on the location and why it is being discussed.

Node names and identifiers

A useful node name helps people understand what they are seeing without unnecessarily identifying a person or private address.

• Use a short, recognizable name.
• A town, broad area, hill, park, or public landmark may be useful.
• Add a role such as repeater, room, observer, or tracker when it helps.
• Avoid addresses, apartment numbers, phone numbers, or full personal names.
• Do not assume another operator wants their node name connected publicly to their identity.

Node identifiers, public keys, hashes, and packet details may be technically visible over the radio. That does not necessarily mean they need to be collected into a public profile of the person operating the device.

Public channels should be treated as public

Messages sent through public MeshCore channels or the default public Meshtastic channel may be received, repeated, logged, or viewed outside the immediate area.

Shared-key channels limit who can read the message contents, but anyone with the configuration can participate. They should not be treated as a safe place for passwords, credentials, highly sensitive personal information, or anything that would cause serious harm if exposed.

Maps and observed activity

The Hampden County Mesh live map and activity analyzer display MeshCore activity heard through participating observer systems.

A visible node or packet does not mean Hampden County Mesh owns the device, knows who operates it, or can confirm that another radio can reach it directly.

Publicly visible map data also does not make unrelated private information fair game. Avoid combining a marker with names, addresses, photographs, property records, or other information to identify a private operator.

Choose the right place to share it

Report security issues privately

Do not open a public Discord or GitHub discussion containing exposed credentials, private keys, access tokens, administrative access details, or instructions that could help someone disrupt a system.

Preserve enough information to explain the issue, but redact credentials and unrelated personal data before sending it.

One last check

1. Does the post include enough information to understand the question?
2. Does it expose a credential, key, private message, or exact private location?
3. Does the image show unrelated people, accounts, notifications, or surroundings?
4. Could a general area describe the test just as well as precise coordinates?
5. Does the file contain metadata or hidden configuration details?
6. Are you sharing someone else’s information without their permission?

When a detail does not help explain the equipment, test, or problem, leave it out.