We want the capacity of the network to scale by 10-100 times. This requires that 90-99% of the flood traffic stops being spread around, which requires that it becomes super-easy for users to stop spreading flood traffic around. This can be done by using regional channels for most communication.
In order to make it super-easy to create local region-encoded channels, use the first part of a channel with dash for region:
These chat channels would automatically be encoded with "berlin" region, no matter what:
#berlin-chat
#berlin-test
#berlin-hamradio
#berlin-net
Or if there is no "berlin" region, and but repeaters support "de" for Germany, and "de" is the only region configured in the local repeaters, just make chat channels like:
#de-berlin
#de-hamburg
#de-bremen
and these chat channels will immediately work, and all communication will be "de" region encoded for all participants.
The repeater admins decide what regions are available, and then anyone can make chat channels based on these regions.
See also discussion ticket #2230
We want the capacity of the network to scale by 10-100 times. This requires that 90-99% of the flood traffic stops being spread around, which requires that it becomes super-easy for users to stop spreading flood traffic around. This can be done by using regional channels for most communication.
In order to make it super-easy to create local region-encoded channels, use the first part of a channel with dash for region:
These chat channels would automatically be encoded with "berlin" region, no matter what:
#berlin-chat
#berlin-test
#berlin-hamradio
#berlin-net
Or if there is no "berlin" region, and but repeaters support "de" for Germany, and "de" is the only region configured in the local repeaters, just make chat channels like:
#de-berlin
#de-hamburg
#de-bremen
and these chat channels will immediately work, and all communication will be "de" region encoded for all participants.
The repeater admins decide what regions are available, and then anyone can make chat channels based on these regions.
See also discussion ticket #2230