Skip to content

Wanted Pages

These are content gaps identified in a structural review of the wiki. They’re topics that align with our focus areas (cybersecurity, AI/ML, military/veteran, privacy, radio, infrastructure) but don’t yet have dedicated pages — or have only a stub.

Want to help? Each page below is a claimable bounty on the scoreboard.

If you’re new to editing the wiki, see Editing the Wiki and the Obsidian + GitHub Guide.


The Privacy section is currently small (10 pages). Most-requested gaps:

  • privacy/secure-messaging-comparison — Matrix vs Signal vs SimpleX vs Session vs Element. Threat model framing, metadata leakage, device-binding behavior, recovery mechanics.
  • privacy/tor-network-guide — Tor Browser, onion services, running a relay or bridge. Common misuses to avoid.
  • privacy/metadata-hygiene — EXIF stripping, document metadata, geotag scrubbing, browser referrer headers, file-share metadata.
  • privacy/burner-devices-guide — buying, provisioning, and rotating temporary devices. SIM/eSIM considerations.
  • privacy/browser-fingerprinting — what fingerprinting is, mitigation strategies, what works vs theater.
  • privacy/email-anonymity-guide — ProtonMail vs Tutanota vs Skiff vs SimpleLogin/anonaddy aliasing. Threat-model grid.
  • privacy/opsec-for-activists — operational security for journalists, activists, dissidents. Adversary modeling, comms hygiene.
  • privacy/cryptocurrency-privacy — privacy-coin comparison (extends the existing Monero page). Mixing, decoy outputs, view keys.
  • privacy/mixnets-overview — Mixminion, Loopix, Nym. What problem mixnets actually solve vs Tor.

The Military section is well-developed for some topics but missing core transition resources:

  • military/gi-bill-complete-guide — Chapter 33, Forever GI Bill, transferring benefits, cap rates, school certification.
  • military/va-claims-process — step-by-step disability claim, intent-to-file, C&P exam, supplemental claims, appeals (HLR / BVA).
  • military/mos-to-civilian-translation — mapping common MOSs (ranger, intel, comms, EOD, medic, etc.) to civilian career fields and certifications.
  • military/transition-timeline-checklist — 18-month, 12-month, 6-month, 3-month, 1-month checklists pre-separation.
  • military/security-clearance-guide — maintaining clearance, transferring, breaks in service, periodic reinvestigation, SF-86 prep.
  • military/oconus-transition-resources — separating overseas, SOFA status, international employment, base access post-ETS.
  • military/reserve-guard-transition — part-time service members, dual benefits, drilling/non-drilling status.
  • military/veteran-benefits-overview — VA healthcare enrollment, home loans, vocational rehab, dependents’ benefits.

Only 12 pages despite cybersecurity being a stated focus. Gaps:

  • cybersecurity/opsec-framework — formal OPSEC methodology applied to red/blue/individual contexts.
  • cybersecurity/threat-modeling — STRIDE, DREAD, attack trees, when to use which.
  • cybersecurity/enterprise-incident-response — distinct from the existing personal-IR page. Tabletop exercises, IR playbooks, retainers.
  • cybersecurity/soc-tooling-overview — SIEM (Splunk / ELK / Wazuh), EDR (Elastic / CrowdStrike), IDS/IPS (Snort / Suricata / Zeek). Strengths, costs, fit.
  • cybersecurity/red-team-tradecraft — adversary emulation frameworks, C2 frameworks (Sliver, Mythic, etc.), reporting standards.
  • cybersecurity/blue-team-tools — defender’s loadout: detection engineering, threat hunting, deception tech.
  • cybersecurity/physical-security-guide — referenced by the cybersecurity index but the page doesn’t exist.
  • cybersecurity/digital-forensics — disk imaging, timeline analysis, memory forensics (Volatility, Rekall).
  • cybersecurity/malware-analysis — static (PE/ELF analysis, strings, YARA) and dynamic (sandbox, debugger) workflow.
  • cybersecurity/common-cves-tracking — CVE landscape, KEV catalog, vendor advisory subscriptions, EPSS scoring.

Surprisingly thin for a community that runs a lot of self-hosted infrastructure:

  • infrastructure/reverse-proxy-nginx and infrastructure/reverse-proxy-traefik — only Cloudflared exists currently.
  • infrastructure/monitoring-prometheus-grafana — node exporter, Grafana dashboards, alerting basics.
  • infrastructure/logging-elk-stack (or Loki) — log aggregation, retention, querying.
  • infrastructure/backups-borgbase and infrastructure/backups-restic — backup strategies for self-hosted services.
  • infrastructure/iac-terraform — declarative infra, state management, multi-environment patterns.
  • server-guides/kubernetes-setup — single-node and small-cluster K8s.
  • server-guides/load-balancing-haproxy — when, why, how.
  • server-guides/database-postgresql — install, tune, backup. (MySQL or MongoDB pages also welcome.)
  • server-guides/server-hardening — distinct from existing index content. CIS benchmarks, fail2ban, kernel hardening.
  • server-guides/disaster-recovery — RPO/RTO, runbooks, failover.

The AI/ML section is one of the strongest, but a few gaps:

  • ai-ml/rag-patterns — retrieval-augmented generation: chunking, embeddings, retrieval strategies, hybrid search.
  • ai-ml/eval-frameworks — LLM evaluation: golden sets, LLM-as-judge, regressions.
  • ai-ml/agentic-patterns — tool use, planning, multi-agent orchestration patterns.
  • ai-ml/local-llm-setup — extends the existing pi-llm page to bigger hardware (consumer GPUs, vLLM, llama.cpp).
  • ai-ml/prompt-engineering-taxonomy — chain-of-thought, few-shot, structured output, prompt injection defense.
  • radio/gmrs-guide — license, equipment, repeater use.
  • radio/ham-licensing-tiers — Tech / General / Extra path, study resources, exam logistics.
  • radio/meshtastic-and-mesh-networking — LoRa mesh nets, Meshtastic firmware, deployment patterns.
  • hardware/raspberry-pi-cluster — referenced from the AI/ML Pi-LLM page but doesn’t exist.

  1. Sign in via SSO.
  2. Click the Edit link at the top of any wiki page (or open the monorepo directly).
  3. Create the file at the suggested slug under apps/wiki/src/content/docs/<section>/<slug>.md.
  4. Use this frontmatter:
    ---
    title: "Your Page Title"
    description: "One-line SEO summary"
    tags: ["section", "specific-topic"]
    ---
  5. Submit a merge request. Reviewers will help land it.

Don’t worry about completeness. A solid stub with the right structure is more useful than nothing — the Backlinks feature will start surfacing inbound interest as soon as your page exists.

Open a Q&A post tagged wiki-gap, or just create the page and add it to this list.