2026/04/17/default-scope

[giscus[bot]]

2026/04/17/default-scope

Hopefully the last of the missing pieces for region filtering is now here.

https://blog.meshcore.io/2026/04/17/default-scope

[flo1o1]

If the default companion scope is the same for all, then there is not much of a difference compared to the null scope, and I assume it will be blocked quite soon as well (at least in Germany).

It would be great if the default region would be set automatically to something useful, e. g. an ISO 3166-1 alpha-2 country code, depending on the user's location (find out by first GPS signal or ask the user).

[dybdahl24]

Being in Denmark close to sweden, it would be a disaster to have country-specific regions. I am also trying to see if the Danish island Bornholm will be able to connect to Poland, Germany and Sweden, that would make a lot of sense.

So if regions are used, any user close to a region border would need at least 2 default regions.

[recrof]

it would be a disaster to have country-specific regions

it's pretty disastrous to not have default region on large meshes that have noisy neighbours. pre-1.15.0, you could not "firewall" yourself. sometimes you don't want to have everyone in one mesh. you can still create one bigger region with multiple countries if you prefer. you'll never be able to connect whole europe in single mesh without killing the whole network.

[dybdahl24]

Our area (Copenhagen) is pretty far away from noisy neighbours, so the automatic filtering based on hop count seems to handle that problem for us.

In Copenhagen, the main problems seems to be our own traffic inside our region.