Sync & local-first systems
CRDTs, sync engines, offline stores. Currently reproducing the Automerge performance paper and writing up where it holds.
Home / Community
Hackathons are the heartbeat, not the whole body. This is the rest of it: standing research groups, twice-weekly co-working rooms, a review economy that actually works, and the fastest way on the internet to find a teammate in your timezone.
Small standing groups — six to twelve builders — that read papers, reproduce results and publish notes together. Circles run on a term system: eight weeks, one artefact at the end. Tier III unlocks founding your own.
CRDTs, sync engines, offline stores. Currently reproducing the Automerge performance paper and writing up where it holds.
Everything under 3B parameters. Distillation, quantisation, and the honest limits of tiny models. Co-authored a preprint in March.
Profilers before opinions. Reading the classic latency literature and benchmarking real OSS codebases against it.
Screen readers, keyboard-first design, and why most dev tools fail both. Building an a11y test corpus as this term's artefact.
Netcode, rollback, prediction. The circle behind two Game Jam podiums. Waitlist opens for the autumn term.
Founded by three Reproduce-the-Paper veterans. Picking apart what makes published results run — and what quietly doesn't.
23 circles active this term · applications reviewed weekly
Open voice rooms, twice a week, every week. Bring the thing you're stuck on; someone in the room has been stuck there before. Cameras optional, always.
| Room | When | Host | Usual turnout |
|---|---|---|---|
| The Long Roomquiet co-working, one shared music bot | Tue 18:00–23:00 UTC | @deskrejected | 60–90 |
| Rubber Duck Rowtalk through your bug until it confesses | Tue 19:00–21:00 UTC | rotating | 20–35 |
| The Saturday Sessiondemos at the top of every hour | Sat 15:00–22:00 UTC | @mira.wav | 80–120 |
| First Timers' Tableyour first build night, hosted gently | Sat 16:00–18:00 UTC | community team | 15–25 |
Post your code, get a structured review from a builder one tier above you — then pay it forward to someone one tier below. Reviews rated helpful earn 15 rank points, so the feedback economy stays honest.
Submit a repo and three questions you actually want answered. Vague requests get bounced back with a template.
A reviewer from the tier above claims it within 48 hours. Reviews follow a fixed rubric: correctness, clarity, next steps.
You rate the review's usefulness. Helpful reviewers earn points; careless ones stop getting matched.
Your queue unlocks after you review someone newer. 1,913 reviews exchanged so far this year.
Filter open builders by timezone, stack and rank. Send one message, form a team in two clicks. 71% of last season's podium teams met exactly this way.
| Builder | Tier | Stack | Timezone | Looking for |
|---|---|---|---|---|
| @mereb.devbackend, likes hard sync problems | Artisan | Go · Postgres · TS | UTC+3 | № 032 team |
| @quietlyshippingfrontend with service-worker scars | Artisan | TS · React · Rust | UTC−5 | № 032 team |
| @lina.compilesfirst hackathon, strong fundamentals | Novice | Python · C | UTC+1 | any team |
| @osei.codeswill join one team per season, choose wisely | Luminary | Rust · Zig · TS | UTC+0 | game jam |
312 builders currently open to teams · sign in to appear here
Short on purpose.
The full code of conduct and enforcement process is linked from every room and board. Moderation decisions are logged publicly, minus personal details.