The channels we use in the Inland Northwest. Scan the QR with your phone, or tap Add if you are reading this on the device running your MeshCore client. Either way the channel is added for you — there is no key to type in.
#inw and #INW are two
different channels that cannot hear each other. Use the links below rather than
typing names by hand, and you will always land in the right place.
Everyday channels for the Inland Northwest mesh.
Public
Default MeshCore channel — every client has it out of the box
8b3387e9c5cdea6ac9e5edbaa115cd72
One channel per county, for emergency traffic only. Join the ones you are in or near. Keeping them quiet is what makes them useful.
#geg- prefix? A hashtag channel's key comes
from its name alone, so a channel name is global — every node running
MeshCore anywhere that uses #weather is on the same channel we would
be. We tried the plain names and abandoned them: #weather,
#test, #bot and #ping filled with traffic
from other parts of the mesh, which crowds out local conversation and wastes
airtime relaying messages nobody here is part of.
#geg-weather, #geg-test, #geg-bot and
#geg-ping instead. The prefix is not magic — it is simply a name
unlikely to be picked elsewhere, which is all it takes to keep a channel local.
puw stands in for the Pullman / Moscow area. Regions are how
repeaters decide which traffic to carry, and the Spokane one currently covers a
few hundred of them. You can see the map, find your repeater and get its
configuration on the Region Builder page.
geg for both keeps the naming consistent — it does not mean the
channel is restricted to that area. Anyone can join it; the name simply makes it
unlikely that someone far away picks the same one by accident.
Channels are joined, not owned — anyone who knows a name can join, and the key is derived from the name itself, so nothing here is secret. Treat every channel as public.
Public is the MeshCore default and uses a fixed well-known key; the
rest derive theirs from the channel name.