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.

Pick whichever fits your comfort level — all three end up in the same place.

  1. Sign in with your IrregularChat SSO account.
  2. Click any link below to open the stub or existing page.
  3. Click Edit this page at the bottom of that page.
  4. Edit the markdown in the split-pane editor and click Save.

Works for any page that already exists (including all stubs on this list).

🌐 Option 2 — GitLab web UI (no local tools, good for new pages)

Section titled “🌐 Option 2 — GitLab web UI (no local tools, good for new pages)”
  1. Open the wiki folder on GitLab:
    git.juntogroups.org → apps/wiki/src/content/docs
  2. Navigate to the right subfolder, click an existing file (pencil to edit) or + → New file to create one.
  3. Add frontmatter, write your content, scroll down to Commit changes.
  4. Commit to a new branch → Create merge request → submit for review.

💻 Option 3 — Obsidian + Git (best for writing multiple pages)

Section titled “💻 Option 3 — Obsidian + Git (best for writing multiple pages)”
Terminal window
git clone https://git.juntogroups.org/irregulars/irregularchat-monorepo.git

Open apps/wiki/src/content/docs as an Obsidian vault, install the Obsidian Git plugin, write pages locally, then push and open a merge request.

Full walkthrough: Obsidian + GitHub Wiki Workflow



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. (page exists — help expand it)
  • privacy/tor-network-guide — Tor Browser, onion services, running a relay or bridge. Common misuses to avoid. (page exists — help expand it)
  • privacy/metadata-hygiene — EXIF stripping, document metadata, geotag scrubbing, browser referrer headers, file-share metadata. (page exists — help expand it)
  • privacy/burner-devices-guide — buying, provisioning, and rotating temporary devices. SIM/eSIM considerations. (page exists — help expand it)
  • privacy/browser-fingerprinting — what fingerprinting is, mitigation strategies, what works vs theater. (page exists — help expand it)
  • privacy/email-anonymity-guide — ProtonMail vs Tutanota vs Skiff vs SimpleLogin/anonaddy aliasing. Threat-model grid. (stub — help fill it in)
  • privacy/opsec-for-activists — operational security for journalists, activists, dissidents. Adversary modeling, comms hygiene. (stub — help fill it in)
  • privacy/cryptocurrency-privacy — privacy-coin comparison (extends the existing Monero page). Mixing, decoy outputs, view keys. (stub — help fill it in)
  • privacy/mixnets-overview — Mixminion, Loopix, Nym. What problem mixnets actually solve vs Tor. (page exists — help expand it)

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

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

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

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. (stub — help fill it in)
  • ai-ml/eval-frameworks — LLM evaluation: golden sets, LLM-as-judge, regressions. (stub — help fill it in)
  • ai-ml/agentic-patterns — tool use, planning, multi-agent orchestration patterns. (stub — help fill it in)
  • ai-ml/local-llm-setup — extends the existing pi-llm page to bigger hardware (consumer GPUs, vLLM, llama.cpp). (stub — help fill it in)
  • ai-ml/prompt-engineering-taxonomy — chain-of-thought, few-shot, structured output, prompt injection defense. (stub — help fill it in)

  1. Sign in via SSO.
  2. Click any GitLab link above to open the Web IDE pre-filled with the correct file path, or click any wiki link and use the Edit this page button at the bottom of the page.
  3. Use this frontmatter:
    ---
    title: "Your Page Title"
    description: "One-line SEO summary"
    tags: ["section", "specific-topic"]
    ---
  4. 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.