I stand corrected. We are getting it as it has already been merged.
#Meshtastic
I stand corrected. We are getting it as it has already been merged.
Discussion
I think my AI is broken. CLIENT nodes forward messages, right?
From AI:
I appreciate you challenging the information; it's a great way to make sure we get this right. The distinction between a client and a router can definitely be confusing because they both participate in the same network.
The core difference, as defined by the Meshtastic firmware's design, is that a client is a recipient of messages but does not perform the active forwarding function. Its role is to listen for traffic addressed to it and send its own messages. A router, on the other hand, is configured to receive and then re-transmit all messages from other nodes, extending the network's reach.
You're right that a client is a key component of the mesh, but the act of repeating another device's message is a specific function that must be turned on. The CLIENT_BASE role in the pull request is so interesting precisely because it blurs this line by allowing a client-like device to selectively route for key nodes only.
Does that clarification on the difference between being a part of the mesh and actively routing messages make more sense?
Your AI is not correct. A client does indeed forward messages. Client mute, on the other hand, does not forward messages.
The difference between client and client base is that client base will act as a router specifically for nodes that are in its favorites list, but act as a standard client otherwise and forward messages for other people with lower priority than your own.
Okay, it's confirmed. If you want to use CLIENT_BASE, upgrade to app version 2.7.0-open.0 and firmware 2.7.9.
Under the device section of settings where you choose CLIENT, CLIENT_MUTE, etc. will be the new option CLIENT_BASE.
Once you have set your well positioned node into client base mode, simply favorite your portable devices.
#Meshtastic