View source for MeshCore/Scopes

{{DISPLAYTITLE:Scopes}}
<span id="meshcore-scopes"></span>
== MeshCore Scopes ==

<div class="sm-cx sm-cx-success">

'''Quick start for most users:''' open the app, go to '''Experimental Settings''', set '''Default Scope Region''' to <code>sco</code>. That is all you need for normal Scottish traffic.


</div>
<div class="sm-cx sm-cx-warning">

'''Watch out:''' if you do not have a suitable '''scope''' set, repeaters on the Scottish MeshCore network wont forward your traffic. You can end up '''shouting into the void'''. Check your default scope and each channel’s scope before you count on messages reaching anyone.


</div>
Scope is the single setting that makes or breaks whether your messages go anywhere on ScotMesh. The channel name is for people — the scope is for the mesh. Set your '''default''' to <code>sco</code>, then adjust per channel when you need something narrower.

<div class="sm-cx sm-cx-info">

'''ScotMesh setup:''' Under '''Experimental Settings''', set the default scope region to <code>sco</code>, and keep <code>ioi</code> available in your scope list as well so you can pick it when you need it. For each channel, set scope to match '''where the traffic should travel'''—for example <code>#edinburgh</code> with <code>edi</code>. On '''<code>#ireland</code>''', you may use '''<code>ioi</code> or <code>sco</code>''': use <code>ioi</code> when the message should ride the Island of Ireland scoped path (IOI peering); use <code>sco</code> when you want the same channel but Scotland-wide scoped carriage on the mesh.


</div>
<span id="why-scope-matters"></span>
=== 🤷 Why scope matters ===

Without scope, repeaters have no way to know whether to carry your traffic. With it, messages travel through exactly the right part of the network.

* Keep Scottish traffic inside Scotland where appropriate.
* Allow controlled traffic to and from the Island of Ireland (IOI peering).
* Reduce unnecessary flooding.
* Keep the network easier to grow.

For example channel names and typical scopes, see [[MeshCore/Channels|Channels]]. For repeater region codes, see [[MeshCore/Regions|Regions]].

<span id="what-region-scope-means"></span>
=== 🗺️ What region scope means ===

Think of scope like a postcode on a letter — it tells the mesh where the message is meant to go.

<syntaxhighlight lang="text">sco = Scotland-wide
edi = Edinburgh area (example local)
ioi = Island of Ireland (IOI peering)</syntaxhighlight>
A message scoped to <code>sco</code> is forwarded by repeaters that carry <code>sco</code>as a region. A message scoped to <code>ioi</code> is forwarded by repeaters that carry <code>ioi</code>as a region. If scope is missing or wrong for your path, the message will go nowhere, it is dropped and ceases to exist.

<span id="wildcard-forwarding-is-not-allowed"></span>
=== 🚫 Wildcard forwarding is not allowed ===

The wildcard marker is <code>*</code>. Do not rely on it for routing — the Scottish MeshCore setup expects explicit region scopes.

In the '''Companion App''', your channel scope should always be a '''real region code''' (<code>sco</code>, <code>gla</code>, <code>ioi</code>, and so on). On '''repeaters''', CLI examples sometimes show <code>*</code> as the '''parent''' in a region tree (for example <code>region put sco *</code>); that is a different idea from wildcard '''forwarding''' and is covered in [[MeshCore/Regions|Regions]].

<span id="documented-scope-codes"></span>
=== 📋 Documented scope codes ===

{| class="wikitable"
|-
! Scope
! Typical use
|-
| <code>sco</code>
| Scotland-wide traffic
|-
| <code>cen</code>
| Central Scotland
|-
| <code>fif</code>
| Fife
|-
| <code>tay</code>
| Tayside
|-
| <code>gla</code>
| Glasgow area
|-
| <code>edi</code>
| Edinburgh area
|-
| <code>fal</code>
| Falkirk area
|-
| <code>sti</code>
| Stirling area
|-
| <code>per</code>
| Perth area
|-
| <code>dun</code>
| Dundee area
|-
| <code>ioi</code>
| Island of Ireland / IOI peering
|}

For most day-to-day traffic in Scotland, '''<code>sco</code>''' is the right default. Use a '''local''' code when traffic should stay in that area, regardless of channel name.

<span id="default-scope-and-per-channel-scope"></span>
=== ⚙️ Default scope and per-channel scope ===

On ScotMesh, set your '''default''' scope region to <code>sco</code>. In the mobile app this is usually under '''Experimental Settings'''. Flood packets from the companion then use <code>sco</code> unless a '''group channel''' has its own scope.

'''Per-channel scope overrides the default.''' Examples:

* <code>#glasgow</code> with <code>gla</code> keeps traffic in the Glasgow-area part of the mesh.
* '''<code>#ireland</code> with <code>ioi</code>''' — message is scoped for the Island of Ireland path (IOI peering repeaters).
* '''<code>#ireland</code> with <code>sco</code>''' — same channel name, but the packet is Scotland-wide scoped; repeaters treat it like other <code>sco</code> traffic.

Keep both <code>sco</code> and <code>ioi</code> in your available scopes so you can switch. For background, see MeshCore [https://blog.meshcore.io/2026/04/17/default-scope Default Scope Region].

<span id="how-to-set-region-scope-in-the-companion-app"></span>
=== 📱 How to set region scope in the Companion App ===

Menus vary by app version and platform; the usual flow is:

<syntaxhighlight lang="text">1. Open the MeshCore Companion App
2. Open the channel you want to use
3. Open the channel options or channel menu
4. Find the region scope option
5. Select or add the region code you need
6. Send with that scope active</syntaxhighlight>
Often the channel menu includes something like '''Set Region Scope''', then you pick or type the code (for example <code>sco</code>, <code>edi</code>, or <code>ioi</code>).

<span id="examples"></span>
=== 💬 Examples ===

'''Scotland-wide'''

<syntaxhighlight lang="text">Channel: #scotland
Scope:   sco</syntaxhighlight>
'''Local (example)'''

<syntaxhighlight lang="text">Channel: #glasgow
Scope:   gla</syntaxhighlight>
'''<code>#ireland</code> with Island of Ireland scope'''

<syntaxhighlight lang="text">Channel: #ireland
Scope:   ioi</syntaxhighlight>
'''<code>#ireland</code> with Scotland-wide scope'''

<syntaxhighlight lang="text">Channel: #ireland
Scope:   sco</syntaxhighlight>
The channel name does not set scope by itself — you still choose <code>ioi</code> or <code>sco</code> (or another code) in the channel settings.

<span id="quick-choices"></span>
=== ⚡ Quick choices ===

* Normal Scottish chat: default <code>sco</code>, or <code>#scotland</code> with <code>sco</code>.
* Local-only: local scope such as <code>edi</code> or <code>gla</code> when traffic should stay in that area.
* '''<code>#ireland</code>:''' <code>ioi</code> for IOI-scoped path, '''<code>sco</code>''' when you want Scotland-wide scoped carriage on that channel.
* Tests: <code>#test</code> with whichever scope you are testing (<code>tay</code>, <code>sco</code>, …).

If you are unsure, '''<code>sco</code>''' is the safe general default for Scottish-side traffic.

<span id="what-to-avoid"></span>
=== ❌ What to avoid ===

* Sending traffic with no region scope.
* Relying on wildcard forwarding.
* Assuming the channel name alone chooses routing.

<span id="summary"></span>
=== 📝 Summary ===

<syntaxhighlight lang="text">Default: sco on ScotMesh
Override per channel when needed
#ireland: ioi OR sco
Local: use the local code when traffic should stay local
Check your companion app is scoped before you send your initial messages</syntaxhighlight>
Getting scope right keeps mesh traffic logical and the mesh relaible, easier to use and simpler to grow.