Skip to content

Have bridge repeaters drop unscoped messages in ON/QC proposal - #103

Merged
MrAlders0n merged 1 commit into
mainfrom
onqc-scopes-bridge-unscoped
Sep 24, 2026
Merged

MrAlders0n merged 1 commit into
mainfrom
onqc-scopes-bridge-unscoped

Conversation

@MrAlders0n

Copy link
Copy Markdown
Member

Bridge repeaters that link two city zones (Rigaud example) now drop messages with no scope (region denyf *); every other repeater keeps * allowed. New users who haven't set a scope still reach their whole city, but unscoped traffic no longer floods the next city. Bots and MeshMapper scoped to their city stay contained.

  • Rigaud example uses region denyf *, with a line-by-line explanation and a warning that the bridge must be the only link between the zones
  • New "Who hears what" section: three route diagrams (unscoped new user, city-scoped bot, onqc DM) and a table of seven message types across Ottawa repeaters, the Rigaud bridge and Montréal repeaters
  • Short-version bullet and rollout updated; the 3-hop unscoped cap becomes "only if needed", since a mesh-wide cap would cut new users off inside their own city
  • English and French

🤖 Generated with Claude Code

https://claude.ai/code/session_014hemhbrLw8SD8kkR1hdxMK

@MrAlders0n
MrAlders0n merged commit 5ac420f into main Sep 24, 2026
8 checks passed
@MrAlders0n
MrAlders0n deleted the onqc-scopes-bridge-unscoped branch September 24, 2026 20:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant