Contribute to Irregularpedia
The community wiki is open-source. Pick a wanted page, write it, earn points. Every accepted PR adds to your scoreboard.
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)
- Sign in at git.irregularchat.com with your IrregularChat SSO (same login as score.irregulars.io)
- Open the issue you want to claim (e.g. wanted-page issues) and comment
/assign me - Click the Web IDE button on the repo (or press . on any GitLab page)
- Create the file at the path the issue tells you (e.g.
apps/wiki/src/content/docs/privacy/tor-network-guide.md) - Use this frontmatter at the top:
--- title: "Your Page Title" description: "One-line SEO summary" tags: ["section", "specific-topic"] --- - Write the page in Markdown. Reference other pages with
[link](/section/slug/) - Click Source Control → commit on a new branch → Create merge request
- 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
- You open a merge request on GitLab — automated checks run
- A reviewer skims the page and approves (or asks for changes)
- Reviewer merges to
main - CI's
deploy-wikijob builds and deploys to irregularpedia.org — live in ~30 seconds - 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/400bounty — 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.
privacy (9)
#52 · Secure Messaging Comparison
#53 · Tor Network Guide
#57 · Email Anonymity Guide
#58 · OPSEC for Activists & Journalists
#59 · Cryptocurrency Privacy
#54 · Metadata Hygiene
#55 · Burner Devices Guide
#56 · Browser Fingerprinting
#60 · Mixnets Overview
military (8)
#61 · GI Bill Complete Guide
#62 · VA Claims Process
#63 · MOS to Civilian Translation
#64 · Transition Timeline & Checklist
#65 · Security Clearance Guide
#66 · OCONUS Transition Resources
#68 · Veteran Benefits Overview
#67 · Reserve & Guard Transition
cybersecurity (10)
#72 · SOC Tooling Overview
#69 · OPSEC Framework
#70 · Threat Modeling
#71 · Enterprise Incident Response
#73 · Red Team Tradecraft
#74 · Blue Team Tools
#75 · Physical Security Guide
#76 · Digital Forensics
#77 · Malware Analysis
#78 · Tracking CVEs and Vulnerabilities
infrastructure (7)
#79 · Reverse Proxy with nginx
#80 · Reverse Proxy with Traefik
#81 · Monitoring with Prometheus + Grafana
#82 · Logging with ELK or Loki
#85 · Infrastructure as Code with Terraform
#83 · Backups with Borg / BorgBase
#84 · Backups with Restic
server-guides (5)
#86 · Kubernetes Setup
#88 · PostgreSQL Server Setup
#89 · Server Hardening
#90 · Disaster Recovery
#87 · Load Balancing with HAProxy
ai-ml (5)
#91 · RAG (Retrieval-Augmented Generation) Patterns
#92 · LLM Evaluation Frameworks
#93 · Agentic AI Patterns
#94 · Local LLM Setup
#95 · Prompt Engineering Taxonomy
radio (3)
#97 · Ham Radio Licensing Tiers
#98 · Meshtastic & Mesh Networking
#96 · GMRS Guide
hardware (1)
#99 · Raspberry Pi Cluster
other (2)
#41 · Render "Bounty" badge on pages with linked GitLab issues
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.
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.
Tip: set your GitLab username on /profile to make future webhook auto-awards more reliable, even if your commit emails differ.