idea: dont make every node a client

[shortwavesurfer2009]

Currently, the default behavior, when starting a new meshtastic node, is to put it in client mode.

My idea would be to have some small subset of these nodes go to client-mute-by-default instead of client. Say 25%. The thought is that this would reduce channel congestion while keeping enough nodes as client to continue doing a decent job at routing. The user could easily change this in the settings if they determine that their node needs to be in client and was put in client mute by default.

A dumb person's way of implementing this might be to choose a random number between 1 and 4, when the L-O-R-A modem preset is done. If the number is 1, it would go into client mute. If it was 2, 3, or 4, it would go to client mode. This would make 25% of the nodes be client mute by default.

Edit: https://lemmy.zip/post/54064048

[korbinianbauer]

There's been some discussion about automatically choosing roles, but we haven't reached conclusion what would be good heuristics for choosing so far.

Doing it randomly is probably the worst idea so far, no offense 😄 ❤️

A fixed ratio of nodes not relaying is not a good idea. In very dense meshes it won't help much, while in very sparse meshes it will break the only working route.

[radektkacik]

Maybe is not the best to call it as Client. As I started with MT I didn't know I am rebroadcasting all messages.
It could be named like ClientRepeater or something.

[shortwavesurfer2009]

Maybe is not the best to call it as Client. As I started with MT I didn't know I am rebroadcasting all messages. It could be named like ClientRepeater or something.

Client doesn't rebroadcast all messages. It rebroadcasts messages that it has only heard one time.