[Feature Request] Client_Base Assumed Well Place and Receives Rebroadcast Priority

[Ryu945]

I am breaking this idea out into its own separate discussion as was recommended to me.

#8189

#8117

For the most part, every device is considered either extremely well placed and a Router or just a regular client. There is no distinction between devices not as well placed as a Router and as poorly place as a pocket node. These moderately placed devices, like rooftop nodes, could reduce bandwidth usage if they had some level of rebroadcast priority as they can cover much further areas and it would require the network to rebroadcast less. It could also improve coverage as it can prevent a poorly placed node from rebroadcasting.

The idea is to use the already existing Client_Base role. Assume it is well place and take a flat amount off its rebroadcast delay. This only applies to non white listed nodes as it acts like a router for white listed nodes. I don't know how much this reduction should be but perhaps calculate the SNR loss for going an additional 100 - 200m distance in an open field for all the frequencies used by Meshtastic. Then use that modified SNR to calculate the rebroadcast delay.

[Ryu945]

Thoughts?

[Ryu945]

After talking with someone, Client_Base being assumed to be in a good location is an assumption that should not be made. It would be better if Client and Client_Base had a check box where you could tell the device that it is in a good location instead.

[korbinianbauer]

If the location of the node doesn't justify CLIENT or CLIENT_BASE, it should probably be set to CLIENT_MUTE.

[Ryu945]

This is about Client and Client_Base that can have a much better location then other Client and Cilent_Base.