Dear Developers,
the number of Meshcore users and repeaters is rising rapidly. This leads to frequent collisions and the duty cycle being reached prematurely, rendering the network unusable. This issue can be managed through the use of regions. However, since many users (particularly newcomers) do not immediately grasp the concept of regions, many repeater operators have decided to block unscoped traffic using denyf*.
This constitutes a severe restriction that makes it even more difficult for newcomers to get started in this field.
An alternative (and less stringent) approach would be to assign a default scope (predefined within the repeater) to unscoped packets. Naturally, this mechanism should apply only to packets that arrive without a scope; if a packet already arrives with a scope, that existing scope should not be overwritten.
Thank you and best Regards,
Stefan.
Dear Developers,
the number of Meshcore users and repeaters is rising rapidly. This leads to frequent collisions and the duty cycle being reached prematurely, rendering the network unusable. This issue can be managed through the use of regions. However, since many users (particularly newcomers) do not immediately grasp the concept of regions, many repeater operators have decided to block unscoped traffic using
denyf*.This constitutes a severe restriction that makes it even more difficult for newcomers to get started in this field.
An alternative (and less stringent) approach would be to assign a default scope (predefined within the repeater) to unscoped packets. Naturally, this mechanism should apply only to packets that arrive without a scope; if a packet already arrives with a scope, that existing scope should not be overwritten.
Thank you and best Regards,
Stefan.