Parent: #137. Source-verified: a private channel gives privacy (PSK) but NOT containment — channel messages flood unscoped by default and are relayed network-wide by any same-preset repeater without needing the PSK. Three deployment models; the bearer must expose preset + scope as first-class operator config:
- A. public preset, unscoped — free public-repeater carriage, floods all (good-citizen-controlled; only for light traffic).
- B. public preset, scoped — flood-scope (
SET_FLOOD_SCOPE_KEY) so public repeaters drop our floods; needs our own scoped Repeater-firmware nodes to carry between non-adjacent DAPPS nodes.
- C. dedicated preset (freq/SF) — total physical isolation, own infra, least config risk.
Caveats (verified): flood scope is a routing label not a secret (the $-private keystore is stubbed); scoping is global/off-by-default/not-per-channel; no sender hop-TTL (only zero-hop vs full flood). See README "Containment" for citations.
Parent: #137. Source-verified: a private channel gives privacy (PSK) but NOT containment — channel messages flood unscoped by default and are relayed network-wide by any same-preset repeater without needing the PSK. Three deployment models; the bearer must expose preset + scope as first-class operator config:
SET_FLOOD_SCOPE_KEY) so public repeaters drop our floods; needs our own scoped Repeater-firmware nodes to carry between non-adjacent DAPPS nodes.Caveats (verified): flood scope is a routing label not a secret (the
$-private keystore is stubbed); scoping is global/off-by-default/not-per-channel; no sender hop-TTL (only zero-hop vs full flood). See README "Containment" for citations.