[Feature Request] Repeater limit channel flooding

[jeremeguenther]

I am concerned about the long term ability of the mesh to sustain flood messages for all Channels.

I would like a config feature on repeaters where the repeater can choose to not repeat channel messages over X hops. This would still allow for flood discovery, and memorized long distance routes. But would allow us to exclude the vast majority of channel traffic from far away places we do not care about. In addition to this limitation if we were able to add an exclude list of channels we did not want this restriction to apply to, then we could continue to pass all traffic for the public channel, or known channels like #emergency etc.

[446564]

You can do this better with region scopes, instead of a limit on hops you can say only repeat our-region-scope.

Repeaters can be configured to drop other flood traffic or not, and users can choose to scope their channel messages or not.

You can also create nested scopes unique to each repeater to further control what can go where.