[Feature request] [important] Region scope support. (And: Add "Scan for regions" functionality.) #109

New Issue

2026-10-27T15:38:57+01:00

adam commented

2026-10-27 15:38:57 +01:00

I miss the ability to set a region (scope) for outgoing messages.

I hereby feature wish that a scope can be set on a per-channel basis and a per-contact basis (including connection to repeaters/ roomservers, since it might be important for path discovery flood packets) directly on the device.

Together with this also the feature to "scan for regions" (I think it is part of "repeater discovery protocol" to query nearby repeaters for regions they have configured) should be implemented.

(v0.9.10/ v0.9.11 and maybe later, T-Deck Plus.)

Regards!

I miss the ability to set a region (scope) for outgoing messages. I hereby feature wish that a scope can be set on a per-channel basis and a per-contact basis (including connection to repeaters/ roomservers, since it might be important for path discovery flood packets) directly on the device. Together with this also the feature to "scan for regions" (I think it is part of "repeater discovery protocol" to query nearby repeaters for regions they have configured) should be implemented. (v0.9.10/ v0.9.11 and maybe later, T-Deck Plus.) Regards!

adam closed this issue

2026-10-27 15:38:57 +01:00

adam commented

2026-10-27 15:38:58 +01:00

This actually is strongly needed since more and more communities switch to forced region scoping.

Without region support, MeshCore will be not usable anymore in those areas.

Regards!

This actually is strongly needed since more and more communities switch to forced region scoping. Without region support, MeshCore will be not usable anymore in those areas. Regards!

adam commented

2026-10-27 15:38:59 +01:00

I just want to ping here, @dabeani, since I think this is the most important thing to go forward right now because there are more and more areas where messages without region scope are not forwarded by repeaters anymore.

I just want to ping here, @dabeani, since I think this is the most important thing to go forward right now because there are more and more areas where messages without region scope are not forwarded by repeaters anymore.

adam commented

2026-10-27 15:39:00 +01:00

Uff, sorry did not update this issue!
Implemented in v0.9.12, the only thing what is missing there - you cannot set the global wildcard flood to deny. Will come soon.

But the per channel region scopes are in v0.9.12 implemented 👌

Uff, sorry did not update this issue! Implemented in v0.9.12, the only thing what is missing there - you cannot set the global wildcard flood to deny. Will come soon. But the per channel region scopes are in v0.9.12 implemented 👌

adam commented

2026-10-27 15:39:00 +01:00

the only thing what is missing there - you cannot set the global wildcard flood to deny. Will come soon.

Ehm, this is a repeater setting anyway, so why does it matter at all for "MC Term"?

> the only thing what is missing there - you cannot set the global wildcard flood to deny. Will come soon. Ehm, this is a repeater setting anyway, so why does it matter at all for "MC Term"?

adam commented

2026-10-27 15:39:01 +01:00

Ehm, this is a repeater setting anyway, so why does it matter at all for "MC Term"?

totally right, until now this is not needed in companions :)

> Ehm, this is a repeater setting anyway, so why does it matter at all for "MC Term"? totally right, until now this is not needed in companions :)

adam referenced this issue

2026-10-27 15:43:23 +01:00

[Feature wish] Region support: Discover regions. #193

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: adam/meshcore#109