50wiki pages wanted
50unclaimed
4875points up for grabs

How to write a wiki page

You don't need to clone the repo. The fastest path is the GitLab Web IDE in your browser.

Path A — Edit in your browser (recommended for small changes)

  1. Sign in at git.irregularchat.com with your IrregularChat SSO (same login as score.irregulars.io)
  2. Open the issue you want to claim (e.g. wanted-page issues) and comment /assign me
  3. Click the Web IDE button on the repo (or press . on any GitLab page)
  4. Create the file at the path the issue tells you (e.g. apps/wiki/src/content/docs/privacy/tor-network-guide.md)
  5. Use this frontmatter at the top:
    ---
    title: "Your Page Title"
    description: "One-line SEO summary"
    tags: ["section", "specific-topic"]
    ---
  6. Write the page in Markdown. Reference other pages with [link](/section/slug/)
  7. Click Source Control → commit on a new branch → Create merge request
  8. Put Closes #<issue iid> in the MR description so the bounty auto-awards on merge

Path B — Clone locally (for big writeups, multi-page changes, or local preview)

git clone https://git.irregularchat.com/irregulars/irregularchat-monorepo.git
cd irregularchat-monorepo/apps/wiki
pnpm install
pnpm dev          # localhost:4321 — live-reload preview

# Create your page
vim src/content/docs/privacy/tor-network-guide.md

# Verify the build is clean
pnpm run build

# Commit and push to a new branch
git checkout -b wiki/tor-network-guide
git add src/content/docs/privacy/tor-network-guide.md
git commit -m "feat(wiki): add Tor Network Guide"
git push -u origin wiki/tor-network-guide
# Open the MR link printed in stdout

What happens after you push

  1. You open a merge request on GitLab — automated checks run
  2. A reviewer skims the page and approves (or asks for changes)
  3. Reviewer merges to main
  4. CI's deploy-wiki job builds and deploys to irregularpedia.org — live in ~30 seconds
  5. The scoreboard's GitLab webhook fires:
    • +40 merge_pr — for any merged PR
    • +10 wiki_edit — if the MR touches wiki content
    • +50 first_contribution — one-time bonus on your first ever PR
    • +25/50/100/200/400 bounty — if the MR closes a tagged issue

Tips

  • A solid stub beats no page. Don't wait until it's perfect — ship and iterate. Backlinks surface inbound interest as soon as the page exists.
  • Cite authoritative sources. Especially for cybersecurity, military, and privacy — readers act on this content.
  • Link sideways. Internal links to 2–3 related pages multiply discoverability via the auto-generated backlinks index.
  • Email match matters. Your GitLab commit email must match the email on your scoreboard account, or points won't land. Check your profile.

Wanted pages by section

Sourced from /community/wanted-pages. Each entry is a GitLab issue you can claim.

XS · 25 S · 50 M · 100 L · 200 XL · 400

privacy (9)

M · 100 pts privacy

#52 · Secure Messaging Comparison

M · 100 pts privacy

#53 · Tor Network Guide

M · 100 pts privacy

#57 · Email Anonymity Guide

M · 100 pts privacy

#58 · OPSEC for Activists & Journalists

M · 100 pts privacy

#59 · Cryptocurrency Privacy

S · 50 pts privacy

#54 · Metadata Hygiene

S · 50 pts privacy

#55 · Burner Devices Guide

S · 50 pts privacy

#56 · Browser Fingerprinting

S · 50 pts privacy

#60 · Mixnets Overview

military (8)

L · 200 pts military

#61 · GI Bill Complete Guide

L · 200 pts military

#62 · VA Claims Process

L · 200 pts military

#63 · MOS to Civilian Translation

M · 100 pts military

#64 · Transition Timeline & Checklist

M · 100 pts military

#65 · Security Clearance Guide

M · 100 pts military

#66 · OCONUS Transition Resources

M · 100 pts military

#68 · Veteran Benefits Overview

S · 50 pts military

#67 · Reserve & Guard Transition

cybersecurity (10)

L · 200 pts cybersecurity

#72 · SOC Tooling Overview

M · 100 pts cybersecurity

#69 · OPSEC Framework

M · 100 pts cybersecurity

#70 · Threat Modeling

M · 100 pts cybersecurity

#71 · Enterprise Incident Response

M · 100 pts cybersecurity

#73 · Red Team Tradecraft

M · 100 pts cybersecurity

#74 · Blue Team Tools

M · 100 pts cybersecurity

#75 · Physical Security Guide

M · 100 pts cybersecurity

#76 · Digital Forensics

M · 100 pts cybersecurity

#77 · Malware Analysis

S · 50 pts cybersecurity

#78 · Tracking CVEs and Vulnerabilities

infrastructure (7)

M · 100 pts infrastructure

#79 · Reverse Proxy with nginx

M · 100 pts infrastructure

#80 · Reverse Proxy with Traefik

M · 100 pts infrastructure

#81 · Monitoring with Prometheus + Grafana

M · 100 pts infrastructure

#82 · Logging with ELK or Loki

M · 100 pts infrastructure

#85 · Infrastructure as Code with Terraform

S · 50 pts infrastructure

#83 · Backups with Borg / BorgBase

S · 50 pts infrastructure

#84 · Backups with Restic

server-guides (5)

L · 200 pts server-guides

#86 · Kubernetes Setup

M · 100 pts server-guides

#88 · PostgreSQL Server Setup

M · 100 pts server-guides

#89 · Server Hardening

M · 100 pts server-guides

#90 · Disaster Recovery

S · 50 pts server-guides

#87 · Load Balancing with HAProxy

ai-ml (5)

M · 100 pts ai-ml

#91 · RAG (Retrieval-Augmented Generation) Patterns

M · 100 pts ai-ml

#92 · LLM Evaluation Frameworks

M · 100 pts ai-ml

#93 · Agentic AI Patterns

M · 100 pts ai-ml

#94 · Local LLM Setup

M · 100 pts ai-ml

#95 · Prompt Engineering Taxonomy

radio (3)

M · 100 pts radio

#97 · Ham Radio Licensing Tiers

M · 100 pts radio

#98 · Meshtastic & Mesh Networking

S · 50 pts radio

#96 · GMRS Guide

hardware (1)

M · 100 pts hardware

#99 · Raspberry Pi Cluster

other (2)

Other ways to earn points

  • Review someone else's PR — +15 pts (when the webhook detects an approval)
  • Fix a typo or expand an existing wiki page — +10 pts wiki_edit, doesn't need a wanted-page issue
  • Claim a non-wiki bounty — see the full bounties page
  • Answer a Q&A question — +15 pts, +30 if it gets marked solved

Found a bug? Report it for points

Custom points awarded if accepted, based on severity. Use this for any non-trivial bug — UI glitches all the way up to security findings. Sensitive findings (RCE, key disclosure, auth bypass) should NEVER be posted as a public GitLab issue — submit through this form instead.

Severity rubric for security bugs:

  • low — 50 pts (info disclosure, harmless open redirect)
  • medium — 150 pts (CSRF, low-priv XSS, idempotency abuse)
  • high — 300 pts (auth bypass, SSRF, hardcoded secret, read-only SQLi)
  • critical — 500 pts (admin-priv auth bypass, mutating SQLi, key disclosure exposing user data, webhook signature bypass)
  • rce — 750 pts (remote code/command execution, sandbox escape)

Non-security bugs default to report_bug (25 pts) but admin can boost via admin_award.

Login to submit a bug report

For sensitive findings you can also email security@irregularchat.com or DM an admin on Signal. Do not post unfixed vulnerabilities as public issues.

Missed award? Claim it here

If you merged a PR and the webhook didn't auto-award your points (commit author email didn't match your scoreboard email, or your fork's email setting differed), paste the merged-PR URL below. If your scoreboard email or GitLab username matches the MR author, points award immediately. Otherwise an admin reviews within a few days.

Login to submit a claim

Tip: set your GitLab username on /profile to make future webhook auto-awards more reliable, even if your commit emails differ.

↑ Top