Replies: 2 comments 1 reply
-
|
It would be a great way to implement the region scope, as general users won't be adding it themselves to the channels. |
Beta Was this translation helpful? Give feedback.
1 reply
-
|
The ideas in #2030 would also drastically enhance the user experience regarding using scopes. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Needs
When some small subregions do not have stable connectivity to other parts of the network, we need channels where participants can communicate reliably, and that doesn't overflow to the rest of the network.
This can be achieved by creating a #testcity channel with a testcity region, but it requires ALL repeaters and ALL clients to set this up correctly. But this is very tedious and complex, and usually goes wrong when new clients join.
Solution
A channel name with #! prefix automatically implies a region, so that:
#!mychannel implies the "mychannel" region
Examples
#!direct -> requires the repeater to have region "direct" in order to forward it. Since no repeater has this by default, this channel is for repeater-less communication.
#!dk3400 -> is only available in zipcode 3400 in Denmark, where all repeaters forward the "dk3400" region.
#!WhiteBullRanch -> is only available near the WhiteBullRanch, using the repeater set up by the White Bull Ranch.
#!andysupplyshop -> Only those close to Andy's supply shop get messages during an emergency
#!pizzashop -> Only those close to the pizza shop can send an order this way.
#!scoutcamp -> is only available within the scout camp, using the scout camp repeaters who know the "scoutcamp" region
Added benefits
How to implement:
The sender automatically applies the corresponding region when #! prefix is detected.
Beta Was this translation helpful? Give feedback.
All reactions