Skip to content

docs(CONTRIBUTING): shared operator nym + TollGate vs net4sats - #508

Merged
Amperstrand merged 1 commit into
OpenTollGate:mainfrom
felixfelix-bot:pr/operator-nym-context-doc
Sep 22, 2026
Merged

Amperstrand merged 1 commit into
OpenTollGate:mainfrom
felixfelix-bot:pr/operator-nym-context-doc

Conversation

@felixfelix-bot

Copy link
Copy Markdown
Contributor

Why

Two recurring sources of confusion, documented so future sessions and reviewers can check the convention from the tree instead of re-reporting the same misunderstanding:

  1. c08r4d0r is the shared operator nym, not a personal identifier. Everyone who runs a TollGate goes by c08r4d0r. A private AP SSID like c08r4d0r-AB12 leaks no operator identity — it only means "this is the operator's private AP". This is directly relevant to fix(packaging): stop broadcasting the operator username in the default private SSID #487, whose "operator identity leak" premise misreads the nym as a personal username; see my comment there.

  2. TollGate does not adopt net4sats branding. net4sats is a commercial re-brand, shipped as a separate whitelabel brand value (hostname, DNS, SSIDs, admin webroot all derive from brand). The two are $BRAND variants, not interchangeable.

What changed

CONTRIBUTING.md — new section "Branding, the operator nym, and net4sats" cross-referenced from the PR/issue guidance, stating both facts and pointing at the brand value as the source of truth.

Docs-only; no tests required (CI is unaffected).

…4sats

Clarify two recurring sources of confusion before they become more PRs:

- c08r4d0r is the shared pseudonym for 'a TollGate operator', not a
  personal identifier - an SSID like c08r4d0r-AB12 leaks no identity.
- net4sats is a commercial re-brand; TollGate does not adopt net4sats
  branding, and the two are $BRAND variants, not interchangeable.

Motivated by PR OpenTollGate#487, whose 'operator identity leak' premise misreads
the nym as a personal username. This lets future sessions/reviewers
check the convention from the tree instead of re-reporting the same
misunderstanding.
@Amperstrand

Copy link
Copy Markdown
Collaborator

Verification: PR #508 (operator nym + TollGate vs net4sats in CONTRIBUTING)

Docs-only, one section in CONTRIBUTING.md (tested as-is at head 744e0b98ac88cd458fe07f12ae0e259ce7fea04b, MERGEABLE). I checked every factual claim in the new section against the brand machinery as merged — all of them hold:

Two non-blocking notes: the body says the section is "cross-referenced from the PR/issue guidance" — the diff adds no back-reference there, the section just follows it and self-describes ("Read this before filing a PR or an issue…"); harmless, but the body slightly oversells the diff. And on the CHANGELOG rule: repo guidance says doc-only one-liners may be batched but not skipped — precedent is mixed (#227, a CONTRIBUTING-only change, landed with no entry), so a one-line Changed / Internal bullet would be tidy but I wouldn't hold the PR for it.

No code paths touched, no tests expected, placement and tone fit the file. Disposition: land.

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