Hampden County Mesh

Guides / Sharing Safely

Sharing Safely

Photos, screenshots, map notes, and setup details can help other people learn. Share enough to be useful, but do not expose private locations, credentials, private messages, or someone else’s details.

Do not post private keys, passwords, broker credentials, Wi-Fi details, exact private node locations, private messages, or information someone else did not agree to share.
Safe to Share Do Not Share Locations Photos Screenshots Maps Security

Usually safe to share

These details are usually fine in public channels, public website material, or GitHub issues, as long as they do not reveal something private by context.

Area

Broad location context

A town, public place, hill, road corridor, or broad area can help people understand local results without exposing a private address.

Device

Setup basics

Device model, system, firmware version, antenna type, power type, and general placement are usually useful.

Testing

Short observations

Reports like “active near a public park” or “window placement worked better” are more useful than broad claims.

Docs

Corrections

Broken links, outdated guide information, confusing wording, and public tool corrections are good GitHub or Discord items.

  • Town, broad area, or public landmark.
  • Public park, public trail, public hill, road corridor, or event location.
  • Device model, radio system, and general role.
  • General antenna type, such as stock antenna, whip antenna, or outdoor antenna.
  • General placement, such as indoors, window, outside, vehicle, or elevated.
  • Battery, USB, wall power, or solar as a general power type.
  • Non-sensitive app or firmware version information.
  • Questions about public documentation, public tools, or general setup problems.

Do not share publicly

Some information can create privacy or security problems if it is posted in a public channel, issue, screenshot, photo, map, or social post.

  • Private keys.
  • Passwords.
  • Broker credentials.
  • Wi-Fi names or Wi-Fi passwords.
  • Private IP addresses or admin URLs.
  • Exact home addresses.
  • Exact private node coordinates without clear permission.
  • Private messages or screenshots with sensitive details.
  • Someone else’s setup details without permission.
  • Names, photos, or identifying details of vulnerable people without consent.
  • Photos that reveal private addresses, license plates, screens, badges, or reflections.
  • Information that would make it easy to tamper with, access, or identify a private installation.

Location sharing

Location detail should match the situation. A public meetup at a library can be specific. A private home node usually should not be.

Better public examples

  • “Monson area.”
  • “Near downtown Springfield.”
  • “Fountain Park.”
  • “Near Mount Tom.”
  • “Southwick area.”
  • “Along part of Route 20.”

Avoid for private locations

  • Exact street address.
  • Exact home coordinates.
  • Photos that clearly identify a private house or driveway.
  • Node names that include a private address or apartment number.
  • Detailed directions to a private installation.

Public places, event locations, and permission-based installs are different from private homes. When in doubt, use a broader area.

Photos

Photos can make the site and Discord more useful, but check them before posting.

Before sharing a photo

  • Did anyone visible in the photo agree to be included?
  • Does the photo show a private address, license plate, badge, screen, or reflection?
  • Does the photo reveal a private node location?
  • Does the photo include location metadata?
  • Would cropping the photo make it safer?
  • Would a close-up of the device be better than a wide shot of the location?

Usually useful photos

  • A close-up of a device, antenna, case, or battery setup.
  • A node on a table at a public meetup or demo.
  • A public-safe photo of a park, hill, trail, or general terrain.
  • A wiring or mounting example with private details removed.
  • A photo that helps explain a guide or beginner question.

Screenshots

Screenshots often reveal more than expected. Check the whole image before posting it.

  • Blur or crop private messages.
  • Remove keys, passwords, tokens, and credentials.
  • Remove private coordinates when they are not needed.
  • Remove admin URLs, private IP addresses, and local network names.
  • Check browser tabs, bookmarks, usernames, and notification popups.
  • Check app screens for phone names, contact names, and hidden account details.

A cropped screenshot of the specific issue is usually better than a full-screen image.

Maps and observed activity

Maps, dashboards, observers, MQTT feeds, logs, analyzers, and health-check tools can be useful, but they need context. A point on a map does not always mean your device can directly reach that point over radio.

Some map information may come from an observer, an internet-connected path, delayed data, a public feed, a mobile device, or another region. Do not assume one group owns or controls every marker, packet, node, or message shown on a public tool.

Be careful before reposting map screenshots with extra location details. A public marker does not automatically mean it is safe to add more information about that device or person.

Node names

A good node name helps people understand what they are seeing without revealing too much.

  • Use a short, recognizable name.
  • Use a town, area, hill, park, or general landmark when appropriate.
  • Use a role if it helps, such as portable, repeater, room, or observer.
  • Avoid exact addresses, apartment numbers, phone numbers, or private personal details.

For public or semi-public devices, a general name is usually better than a name that points directly to a private home.

Community alerts and public channels

Public or shared channels can be useful for local awareness, but they should not be treated like private secure messaging.

Keep reports plain and avoid posting names, private addresses, photos of uninvolved people, or details that could put someone at more risk. If something is sensitive, share less in public and use an appropriate trusted contact or group instead.

Where to share

Use the place that fits the information.

Discord

Questions and discussion

Best for setup help, device choices, local testing, safe photos, screenshots with private details removed, and informal discussion.

GitHub

Website and documentation

Best for broken links, guide corrections, public documentation changes, and issues related to the website or repository.

Email

Sensitive or direct contact

Best for security issues, contact questions, event ideas, or anything that should not start in a public channel.

Maps

Observed activity tools

Best for local context, but use maps carefully and avoid adding extra private detail to public map screenshots.

Security issues

Do not post sensitive security issues in a public Discord channel, public GitHub issue, public screenshot, or public social post.

Use the security contact for anything involving exposed credentials, private keys, access tokens, private infrastructure details, or anything that could help someone access or disrupt a system.

security@hampdencountymesh.org

Before sharing checklist

A short check can prevent most problems.

  • Does this include a private address or exact private coordinates?
  • Does this include a password, key, token, broker credential, or Wi-Fi detail?
  • Does this include someone else’s setup, name, message, or location without permission?
  • Does this screenshot show more than the specific issue?
  • Does this photo show a plate, badge, address, screen, reflection, or private location?
  • Would a town, area, or public landmark be enough?
  • Would this be better sent by email instead of posted publicly?

Ask before posting sensitive details

If you are unsure whether something is safe to post, ask in general terms first. Do not paste credentials, exact private locations, or sensitive screenshots just to ask whether they are sensitive.

Join Discord