Network Policies
These policies govern the use of the Inland NW Mesh network and its infrastructure. They exist to keep the network reliable, accessible, and welcoming for everyone. This is a living document and will be updated as the network grows and the community develops consensus.
Contents
- General Use
- Acceptable Use
- Repeater Standards
- Naming Conventions
- Radio and Frequency Standards
- Privacy and Encryption
- Community Standards
- Enforcement
General Use
The Inland NW Mesh network is a shared, community-owned resource. Use of the network is a privilege, not a right. By participating in the network — whether as a client user, repeater operator, or contributor — you agree to these policies.
The network operates under FCC Part 15 rules for unlicensed operation in the 915 MHz ISM band. All users are responsible for ensuring their equipment and usage complies with applicable FCC regulations and local laws.
Acceptable Use
Permitted uses:
- Personal text communication, messaging, and coordination
- Emergency and disaster communications
- Community outreach, events, and group coordination
- Network testing, diagnostics, and development
- Educational and experimental use consistent with the network's mission
Prohibited uses:
- Harassment, threats, or abusive communication directed at any person
- Transmission of illegal content of any kind
- Intentional interference with network operations, including jamming, flooding, or denial-of-service activity
- Attempting to gain unauthorized access to repeaters, room servers, or other nodes
- Using the network for commercial advertising or spam
- Impersonating other users or nodes
- Transmitting content that violates applicable laws
The network is provided as-is with no guarantees of availability, security, or message delivery. Do not rely on it as your sole means of emergency communication.
Repeater Standards
Repeaters are the backbone of the network. Operators who deploy repeaters take on responsibility for maintaining them in good working order and in compliance with these policies.
Repeater operators agree to:
- Keep the repeater on a fixed, semi-permanent location — mobile repeaters cause routing instability
- Use the correct regional radio preset — USA/Canada (Recommended): 910.525 MHz, SF7, BW62.5
- Set an admin password to protect the repeater from unauthorized configuration changes
- Leave the guest password blank or set a simple guest password so community members can view stats and neighbors
- Set flood advert interval to a minimum of 6 hours to reduce unnecessary network traffic (24 hours or longer preferred for established nodes)
- Include owner contact info in the repeater's owner info field (callsign, email, or Discord handle)
- Respond to reasonable requests from network coordinators regarding repeater configuration
- Remove or disable a repeater that is causing network issues if asked by the coordination team
Repeater placement guidance:
- Prioritize elevation and line of sight — height is the single biggest factor in coverage
- Coordinate with the community on Discord before deploying in areas that already have good coverage
- Solar-powered outdoor installs are strongly preferred for repeaters — they keep the network running during power outages
Naming Conventions
Clear, consistent naming helps everyone identify nodes on the network.
Clients:
- Use your name, callsign, or a recognizable handle
- Avoid generic names like "Node" or "Device" that make it hard to identify who you are
Repeaters:
- Use a descriptive location-based name that helps identify where the repeater is
- Recommended format:
[Location]-[Descriptor]— for example:SpokaneValley-High,CdA-Tower,Palouse-Solar - Avoid names that could be confused with other repeaters already on the network
- Licensed amateur radio operators are encouraged to include their callsign in the owner info field
Radio and Frequency Standards
All nodes on the Inland NW Mesh must use the same radio settings to communicate with each other.
| Parameter | Value |
|---|---|
| Preset | USA/Canada (Recommended) |
| Frequency | 910.525 MHz |
| Spreading Factor | SF7 |
| Bandwidth | BW62.5 kHz |
| Coding Rate | CR5 |
Do not change frequency, bandwidth, or spreading factor without coordination with the network group. Nodes on different settings will not communicate with the rest of the mesh.
Transmit power should be set to the maximum legal and safe value supported by your hardware. Most boards support 22 dBm. Do not exceed your hardware's rated output.
Privacy and Encryption
All direct messages on MeshCore are end-to-end encrypted using AES-256. Each device has a unique cryptographic identity.
- Do not share or publish your private key
- Do not attempt to intercept or decrypt other users' private messages
- Be aware that channel messages are visible to all members of that channel
- Node names, positions, and public keys transmitted via adverts are visible to anyone on the mesh
The network does not collect or store user data centrally. Message history may be stored on room servers you connect to — be aware of this when using shared room servers.
Community Standards
Inland NW Mesh is a volunteer community. We expect everyone to treat each other with respect.
- Be welcoming to new members — everyone starts somewhere
- Share knowledge and help others troubleshoot
- Raise concerns or disagreements constructively — on Discord or via email
- Credit others' work and contributions
- Remember this network exists to serve the whole community, not any individual
Enforcement
Inland NW Mesh is a volunteer-run community with no formal enforcement mechanism at this time. We rely on community good faith and self-governance.
If you observe a violation of these policies:
- Report it in the Discord to the coordination team
- Contact us at spokanemesh@gmail.com for serious concerns
Repeated or serious violations may result in removal from the Discord community and coordination of repeater exclusion with other network operators.
Once Inland NW Mesh achieves 501(c)(3) status, these policies will be formalized as part of the organization's governance documents.
Last updated: May 2026. These policies are a draft and subject to community review and revision.