Special scopes

[dl9sau]

I like to discuss the following three scopes with special meaning:

Scope ‚#direct‘.
User likes to talk direct with no repeats. Nothing needs to be done here, since no repeater has configured this region and thus will ignore this packet ;)

Scope ‚#local‘.
Idea: only one repeater hop. Very local area. If repeater hears scope ‚#local‘ AND the packet is heard directly (recorded path is empty) it repeats; if recorded path empty, it drops the packet.
Should be a default in firmware, and Sysop can disable it by configureing ‚deny local‘. Per default, Sysop should have nothing to do for having this feature being active.

Scope ‚#region‘:
Idea: ideal for travellers. You do not need to scan for regions and change channel scope settings, nor send unscoped. User sets scope ‚#region‘ and all repeaters of that region repeat it. How: Example City of Berlin. Repeater has regions like #de, #de-ost, #de-be. Sysop configures region ‚#region‘ as an alias to ,#de-be‘. User sends to scope ‚#region‘; the repeater changes during repeat the hash byte for ‚#region‘ to that one where the alias points to to, i.e. ‚#de-be‘. Repeater‘s neighbor sees region ‚#de-be‘ in the scope of the repeated packet and also repeats the packet. Next neighbor is in Brandenburg and packet stops here.
In the repeater default config, there‘s no preconfigured alias, because we do not know which of the configured region-names is the intended range for the region ‚#region‘.
-> Sysop needs to configure this alias by intend. And he should be encouraged: Perhaps firmware reminds him to set an alias while he configures the regions of his repeater.

[msmuenchen]

I fear the scope "current region" thing will not work out in practice due to message-authentication, or lead to duplicate/confusing packets should two repeaters with a different alias-region hear the same original message broadcast - repeater A would repeat it with the scope changed to region A, repeater B with the scope changed to region B.

[dl9sau]

dupes: Gut point

But if repeater a is in Berlin (de-be) and repeader B is in Brandenburg (de-bb) there,s no duplicate because Berlin repeaters do not repeat Brandenburg.

If region ,region' is heard and translated by two more fine granular scoped repeaters in de-be-mitte and de-be-neukoeln, there may be 10 repeaters producing very local dupes. I think a dupe detection (user with packet it) could mitigate even that case.

Without this feature, a travelling user likely sends just to scope de, focring abt 1000 repeaters to repeat without need, or he floods unscoped through half of europe.

What impacts the net more, 0 to accidently 10 dupes (when sysop do not agree for a regional setup), or 1000++ repeaters forearding a message no one is interested in?

[msmuenchen]

But if repeater a is in Berlin (de-be) and repeader B is in Brandenburg (de-bb) there,s no duplicate because Berlin repeaters do not repeat Brandenburg.

The problem is border repeaters that have both regions set up. What should they default to? See here for an explanation: https://meshcore-de.fyi/meshcore:allgemeines:regions:definieren#duerfen_sich_regions_ueberlappen