Repository navigation
Have bridge repeaters drop unscoped messages in ON/QC proposal - #103
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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.region denyf *, with a line-by-line explanation and a warning that the bridge must be the only link between the zonesonqcDM) and a table of seven message types across Ottawa repeaters, the Rigaud bridge and Montréal repeaters🤖 Generated with Claude Code
https://claude.ai/code/session_014hemhbrLw8SD8kkR1hdxMK