lfg2025/archy
1
0
Fork 0
Code Issues 11 Pull Requests Actions Packages Projects Releases 12 Wiki Activity

Require standard MeshCore public channels and defer custom channels

Browse Source
This commit is contained in:
archipelago
2026-10-06 02:00:56 -04:00
parent e110dd1c0c
commit 5c0b6402ed
1 changed files with 10 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/post-1.9.0-work-backlog.md
+10
View File
@@ -350,3 +350,13 @@ investigation for this scoped task; earlier hardware deferral is not a pass.
listener stability, restart/reconnect and meaningful negative cases. Record listener stability, restart/reconnect and meaningful negative cases. Record
firmware/builds, radios, conditions and results. Simulated or headless checks firmware/builds, radios, conditions and results. Simulated or headless checks
alone do not constitute RF acceptance or a claim of flawless operation. alone do not constitute RF acceptance or a claim of flawless operation.
### MeshCore channel scope clarification
The operator explicitly requires the standard MeshCore public channel(s) used
by the wider community, not an Archipelago-specific/custom channel. Verify the
current official default channel identity/key/configuration and interoperability
with standard MeshCore clients on the selected UK RF plan. Two Archipelago radios
agreeing with each other on a private/custom channel is not acceptance. Custom
channel creation/configuration is deferred to later work and must not be added
as a substitute for repairing the standard public-channel experience.