Skip to content

docs: stop hardcoding the default PSK and preset names - #32

Open
rancur wants to merge 1 commit into
ArizonaMeshtasticCommunity:mainfrom
rancur:claude/split-02-dehardcode-presets
Open

docs: stop hardcoding the default PSK and preset names#32
rancur wants to merge 1 commit into
ArizonaMeshtasticCommunity:mainfrom
rancur:claude/split-02-dehardcode-presets

Conversation

@rancur

@rancur rancur commented Jul 31, 2026

Copy link
Copy Markdown
Contributor

The privacy page quotes the default key literally as AQ== and names
LongFast/MediumFast, and Suggested Channels lists MediumFast as a row in the
community channel table — which reads as an invitation to add your own primary
channel a second time as a secondary. Replaced with the general description in
both places, dropped the row, and collapsed the Android accordion so both
platform sections start the same way.

What to look at: Suggested Channels → the table and the two platform
accordions; Privacy Policy → "public-channel data is not private".

Not in this PR: the "your primary is separate" callout, which needs the Start
Here page. It ships in PR 6.

Preview: https://rancur.github.io/azmsh-site/preview/split-02-dehardcode-presets/

The default key is quoted literally as `AQ==` on the privacy page and the
Suggested Channels table lists `MediumFast` as if it were one of the
community channels. Both bake a specific preset into pages that should
describe the general case, and the MediumFast row invites newcomers to add
their primary channel a second time as a secondary one.

- privacy.md: describe the default key rather than quoting it, and say
  "the common modem presets" instead of naming LongFast/MediumFast.
- suggested_channels.md: drop the MediumFast row from the community table
  and say "the default preset" in the Android and iOS walkthroughs.
- Collapse the Android accordion by default so both platform sections
  start in the same state.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_018pAXdnH4iJEpsWMTYy9hhn
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.

2 participants