A Discord server for developers and security researchers who would rather ship something than talk about shipping something. One brief a month. Public work. Peer review that bites.
Pick a lane, share the clock
The Developer and Hacker tracks run the same calendar, the same peer vote and the same XP ledger. Only the work differs.
Ship something that runs. Web apps, CLIs, automations, libraries — in whatever language you are trying to get good at.
export function Submission({ entry }: Props) { const { votes, track } = entry; return ( <article data-track={track}> <h3>{entry.title}</h3> <VoteRail count={votes} /> </article> );}Break it, then write it up. Vulnerability research, CTF chains, tooling, and blue-team detections that hold under pressure.
Fixed civil days, no timezone argument. The window opens on the 1st and the results are public by the 29th.
- Build / HackDays 1–21
- Anonymous voteDays 22–27
- ResultsDays 28–31
Syncing cycle clock…
XP comes from submissions, votes received, published writeups and your GitHub activity. Cross a threshold and the bot moves your role in the server — the badge is not decorative.
- Newcomer0–99 XP
- Builder100–499 XP
- Veteran500–1,499 XP
- Elite1,500+ XP
Four steps, one loop
The same rhythm every month. Nothing to apply for, nothing to schedule around — the calendar does it for you.
Any day
One invite, no application. Pick up your role, read the current brief, and say hello in the track channel that matches how you build.
- Two tracks: Developer and Hacker
- Every skill level, every age — beginners included
- Channels for review, pairing, and rabbit-hole research
Simulated output. Run the real thing in the server — the bot replies privately, so your rank-up is yours to share.
Receipts, not promises
Every rank on this board was earned by shipping in public and getting voted on by people who read the code.
Loading projects…
Loading writeups…
Where the work gets read
Most servers are a feed. This one is a workshop with a deadline — and people who will tell you what is wrong with your auth flow.
- 01
Reviews from people who read the diff
Post a repo and get line-level feedback in hours, not a thumbs-up emoji. Security folks read the auth flow; frontend folks read the render path.
- 02
A brief every single month
No blank page. A fresh challenge lands on day one with tiers for wherever you are — first project or tenth CVE.
- 03
Sub-channels for the deep end
Vuln research, red and blue team, CLI tooling, design systems. Small rooms where the conversation actually goes somewhere.
- 04
XP that means something
Ranks sync to Discord roles and the public leaderboard. Ship consistently and the whole server can see it.