hack.build

HACKING YOUR
HACKERSPACE

How communities work, and why they break. A post-mortem of one lab's worst year.

Moheeb Zara · hack.build · 17 years inside HeatSync Labs, Mesa AZ
Teardown 2026 · Portland
who's talking

Moheeb Zara

Moheeb Zara

Developer advocate and creative technologist. Ten-plus years bridging hardware and software communities.

Open-source tools, hardware tutorials, and browser-based creative apps. Former HeatSync Labs board member, co-organizer of the first Southwest Maker Festival; developer advocacy at SignalWire and others.

Hardware hacker and new media artist. Things that blink, move, and occasionally need a fire extinguisher.

Partner at devEco Consulting.

hack.build @virgilvox · Mesa, Arizona · hack.build
things i've built

A few of my projects.

LumenCanvas

Browser-native projection mapping. Drag-warp, live-code, cast wirelessly.

lumencanvas.studio
LATCH

Open-source node programming for audio-visual, 3D, and IoT.

latch.design
devEco

A publishing platform for hardware projects. Share builds, docs, BOMs, and write-ups.

deveco.io
Zeenster

Make printable zines in your browser. Free and open-source.

zeenster.com
the space
HeatSync Labs logo

HeatSync Labs

Arizona's first hackerspace: a community-run workshop in Mesa, founded in the 2009 wave and still open seventeen years later.

Front window: diverse, inclusive, welcoming, safe space for everyoneEntranceMain hallWood shopElectronics benchLaser cutters
Member-run 501(c)(3) in Mesa, AZ. It is the case study behind every number in this talk. Space photos: heatsynclabs.org
the space, in use

It runs on people, not machines.

Cutting parts on the bandsaw
Cutting parts on the bandsaw
Wiring an LED build
Wiring an LED build
Weeding vinyl is hard
“Weeding vinyl is hard.”
Members at work at HeatSync Labs.
first, the word

What is a hackerspace?

A community-operated workshop. Members share tools, knowledge, and rent. Nobody owns it the way a business is owned, so the members govern it themselves.

The bait

Laser cutters, 3D printers, a wood shop, an electronics bench.

The point

People who will teach you, help you, and expect the same back.

The experiment

Norms instead of rules. Trust instead of hierarchy. Culture instead of coercion.

the sentence to defend

Not a subscription.

"Membership is a donation to a community, not a subscription to a service." HeatSync Labs Member Handbook

The stakes:the experiment is winnable and losable, and the movement keeps the death records to prove it. Half of governance is defending that one sentence.

first, some context

Where This Comes From

A movement with a history, a politics, and a documented body count.

where spaces came from

Europe built the prototype.

1981
Chaos Computer Club, founded in West Berlin at a table salvaged from an anarchist commune.
1995
c-base, Berlin. A space station under the city that outlived its founders.
2006
Metalab, Vienna. Open door, dues, members, projects, drama, survival.
2007
At 24C3, Ohlig and Weiler present the Hackerspace Design Patterns.
The most influential governance document this movement produced was a conference talk's slide deck. Anyone could copy it, and everyone did.
Ohlig and Weiler, "A Hacker Space Design Pattern Catalogue," 24C3, Dec 2007
the johnny appleseed

"We all knew we would start hackerspaces when we got home. And we all did."

Mitch Altman co-founded Noisebridge, which raised $12,000 in 24 hours for its first month's rent. Then he spent fifteen years teaching soldering and dropping door keys off stages.

"Your hometown needs a hackerspace. It's the only way they've ever happened: people like you started them." Altman · TEDxBrussels 2012 · CCC 2016 · WHYcast 2024
2008 to 2009

78 spaces to hundreds in two years.

2008
NYC Resistor, HacDC, Noisebridge. hackerspaces.org launches with 78 spaces
2009
"Robot Shark Laser!" at DEF CON. The count climbs into the hundreds
The Last HOPE, 2008: "Building Hacker Spaces Everywhere: Your Excuses Are Invalid."
First archived hackerspaces.org list: 78 rows, Wayback capture Jul 2008
the same year as the boom

The autopsy was published in advance.

In May 2009, while the wave was still cresting, the Vienna art group monochrom published "Hacking the Spaces." Their argument: capitalism recuperates its own opposition. Squats become real estate. Hackerspaces become talent pipelines.

"the political approach faded away on en route into tiny geeky workshop paradises" monochrom (Grenzfurthner and Schneider), May 2009 · quoted as written

A family argument, not an outside attack:Grenzfurthner sat on the hackerspaces panel at The Next HOPE the following year, next to Altman.

Cite the essay directly at monochrom.at/hacking-the-spaces
community, not clubhouse

Everyone wants a village.
Nobody wants to be a villager.

as the saying goes; author unknown

Hackerspaces are mutual aid with power tools. No bosses, a free shelf, give what you can, maintain what you use. That is not a metaphor. It is the operating model, and it has a lineage.

the honest version

Context, never a litmus test.

Hackerspaces run on anarchist habits even when nobody says so out loud: no bosses, a free shelf, give what you can. Plenty of members would still reject the label, and they have a point. The movement grew from two roots at once, one radical and political, one tech-first and deliberately apolitical, and most spaces are a mix of both.

Members hold every kind of politics. Knowing where the model comes from is context, never a litmus test.
maxigas, "Hacklabs and Hackerspaces," 2012 · monochrom, 2009, for the argument this answers
start at the ending

45 – 5

Seventeen days ago, my hackerspace voted to remove a board member. Calm room. Record turnout. One evening. Nobody lost their membership.

That boring evening is the happiest ending in this talk. Here is why.
the name is the joke

Our governance meeting has been called "Hack Your Hackerspace" since 2009.

562
times it has run
16
years carrying the name
2026
the year it finally meant it

Most months we vote on card access and someone mops. This is the story of the year we had to hack the hackerspace with the case open and the power on.

why this talk exists

The evangelists went quiet.

Around 2009 you could not attend a hacker conference without someone telling you to go home and start a hackerspace. Hundreds of people did.

Then the talks stopped, and almost nobody came back to report how it went. Twenty talks on how to get a lease, and roughly none on what happens in year twelve when two people who built the place stop speaking.

So this is the missing report. An autopsy on a patient who is still standing.
part one

The Findings

The durable lessons from the data and the movement record, each with its receipt.

what actually died

The hype layer collapsed.

I scraped the movement's own wiki in January and mapped every space that ever appeared. New foundings peaked at 282 in 2012. Last year the number was 14.

hackerspace.sh/atlas, wiki dump Jan 2 2026 · curve smoothed; pinned figures are from the scrape
the inversion

The layer with the money is the layer that died.

2017
TechShop: 10 locations, 9,000+ members, closed in a single day
2019
Maker Media shuts down. Make: survives as a community revival
1,219
of 2,551 wiki-listed spaces still marked active
The commercial layer the critics warned about is the layer that died. The janitorial co-ops survived. Nobody predicted that order.
the fork in the name

Same tools. Different politics.

The maker fork

2012: MAKE takes a DARPA grant to put makerspaces in a thousand high schools. Venture capital, tuition, staff, press.

The hacker fork

Mitch Altman steps away from Maker Faire over that grant. Dues, drama, and sweeping your own floors.

Cavalcanti, Make: 2013 · makezine DARPA coverage 2012 · maxigas, JoPP 2012
the finding that runs the whole talk

Money is the coroner's report, not the cause of death.

74%
of income is member dues
83%
of expenses are rent and utilities
$0
discretionary budget in year 16

Remember TechShop. Ten locations, nine thousand members, real money, dead in a day. The record says friction and burnout, with the empty account arriving at the end. "We are treading water, not drowning."

Jenny List, "When Hackerspace Directors Burn Out," Hackaday, Apr 2018
sorted by hours

A janitorial co-op with classrooms attached.

open hours5,617 h
coffee and coworking3,676 h
classes2,081 h
cleaning and maintenance1,716 h
social events1,083 h

The longest-running program is not the laser.It is coffee and coworking: 613 sessions across 13 years. That sentence is a compliment.

sensor two: read honestly

The loud channel is not the space.

When our conflict got loud it felt like the whole building was on fire. So I counted.

117
channels in the chat archive
30
held the conflict
87
held sewing, cats, lockpicking, lasers

Calibration:read the fights as a portrait of the community under stress, never a portrait of the community. This rule cuts against me too.

sensor one: ask

A survey hears the people who left.

28
responses
68%
feel welcome
77%
feel safe

The exit is silent:people who feel unsafe do not argue. They stop coming, and a count falling by ones never triggers an alarm.

HeatSync Labs community sentiment survey, anonymized, n=28 · cf. Hirschman, 1970
sensor three: where the talk goes

Conflict moves the talk out of public view.

Hypothesis: the harder a conversation is to have, the smaller the room it happens in. As tension rises, reading shifts from open channels to private DMs; when it resolves, it comes back out.

the pattern

Public reads (purple) and DMs (red) trade places as tension rises and falls. At the sharpest moments the split can flip almost completely, then snap back once it settles.

the refinement

It is the type of conflict, not its size. A public blow-up stays public, because everyone crowds in to watch. Coordination, planning, and anything sensitive move to DMs, out of view.

One space's Slack read-location data across a month of governance conflict. A read, not a send, and a daily percentage, so low-traffic days swing hard. The quiet tell is the private band (navy) rising through the acute stretch.
try it: where does the talk go?

Different conflicts land in different rooms.

Pick a situation and watch the same members redistribute across public channels, private channels, and DMs.

where the reading goes
Public channels
80%
Private channels
5%
Direct messages
15%
Business as usual: most reading happens out in the open, where anyone can join and the norms stay visible.

The rule it draws out:loudness is public, but risk is private. A space that only watches its public channels is blind to most of its own conflict.

what the archive taught

Four things the fights kept proving.

  • The visible flashpoint is never the real cause. Blowups are cumulative frustration finding an exit.
  • The long-tenure members who left did not leave over fights. They left over how their proposals were treated. How you say no matters more than whether you say no.
  • Text escalates. Presence heals. A two-hundred-message thread war resolves in one calm evening in a room.
  • High accountability expectations look more contentious and are actually more functional.
cf. Suler, "The Online Disinhibition Effect," 2004 · Friedman and Currall, 2003
everything had a name already

None of our drama was original.

What we livedWho named itYear
The recall election we ratifiedLos Angeles voters1903
Informal groups still have power structuresJo Freeman1972
Commons survive on written rulesElinor Ostrom1990
A group is its own worst enemyClay Shirky2003
The person everyone works aroundPervocracy2012
Software defaults hand founders powerNathan Schneider2024
Patterns this old have patches. Every space rediscovers them at retail price, in production. You do not have to.
the crisis, on a timeline

The institution failed by design.

MARCH 2025
Bylaws grow from 22.6KB to 30.9KB in unreviewed same-day edits by one account. 2009 baseline: 9.3KB.
NOVEMBER 2025
Seven members file a formal conduct complaint about a board member's public statements. It stalls.

Acting on it required a unanimous board vote. That is a veto held by the accused's allies. That rule had been sleeping in the 2009 bylaws for seventeen years.

part two

How We Got Here

The method: read the source, run the sims, audit your own side.

a space's source code is its records

60,330 documents, every claim tagged.

939
wiki pages, 5,419 revisions
8
years of chat export
16
years of calendar
[VERIFIED]primary document, quoted or cited directly
[INFERRED]a reasonable reading, labeled as a reading
[CONFLICT]sources disagree, and the disagreement is preserved
how we know: the wiki does not forget

Diff the revisions and the change has a fingerprint.

939
wiki pages
5,419
revisions, 263 contributors
2
same-day 2025 edits that rewrote the bylaws

A pass over the full history pinned exactly when and how the bylaws changed. Any space with a wiki can run this on itself.

HeatSync Labs wiki revision history, parsed page by page
the game that started this

Trust is a game. Literally.

Nicky Case's "The Evolution of Trust," a playable version of Axelrod's tournaments. Your opponent is a copycat: it repays whatever you did last round. Five rounds. Play it honestly.

Five rounds vs the copycat
You
0
Them
0
Round
1 OF 5
Both cooperate: +2 each. Cheat a cooperator: +3 for you, -1 for them. Both cheat: 0. Your call.

The copycat is most of your members. Whatever you do echoes.

Nicky Case, 2017 · Axelrod, 1984 · brought to me by Mickey McManus
the cascade

Trust updates in public are contagious.

Click any member to break trust in public, or use the button. Then race the two kinds of repair.

The betrayal cascade
Green nodes trust. Break one and watch everyone update their model at once.

Visible public repair rebuilds faster than years of quiet one-on-one work. Most people repair in private, which is backwards.

cf. Slovic, the asymmetry principle, 1993 · Tyler, 1990
the one law under all the others

Scale breaks vibes.

Filled squares know the unwritten norms; hollow ones are guessing. Grow the space, then press the button nobody wants to press.

"We all just know" has a load limit
10
Relationships
45
Norm coverage
100%
Mode
GARAGE MODE
Small enough: norms travel by osmosis. No rules needed yet.
cf. Freeman, "The Tyranny of Structurelessness," 1972 · Shirky, 2003 · Dunbar, 1992
the cast

Six people, every space.

Click each card. Be honest about which are you.

The Builder

Fixes the printer at 2am. Ships.

The Builder

WATCH FOR: burnout, then a quiet exit. Their departure is how decline starts.
FLIP

The Talker

Loves meetings and opinions.

The Talker

WATCH FOR: "I think we should" with no follow-up. Deciding belongs to whoever does.
FLIP

The Lurker

Pays dues, says little, is the majority.

The Lurker

WATCH FOR: their dues keep the lights on; a space of only lurkers is fragile.
FLIP

The Founder

Built it. Carries the memory.

The Founder

WATCH FOR: nostalgia as an anchor. The hardest thing a founder does is let go.
FLIP

The Newbie

Asks "why" about sacred cows.

The Newbie

WATCH FOR: no onboarding, no return visit. They decide in five minutes.
FLIP

The Drama

???

The Drama

NOT A PERSON. Any archetype under enough stress. One is too many. Including you.
FLIP
Once you can name them, conflict gets legible.
who does the work

Glamour bias, simulated.

Two kinds of work every month. Advance the months and watch who takes what.

One month per click
Fun tasks done
0
Chores done
0
One Builder's burnout0%
This month: laser class, new CNC build, clean the bathroom, update the wiki...

The spreadsheet looks healthy right up to the resignation. The lasers are louder than the brooms.

Williams and Multhaup, HBR, Mar 2018 · burnout kills more spaces than rent: Hackaday, 2018
case file 3, playable

"Don't leave tools near Bob."

Every community risks tolerating someone the rest work around, like a broken step everybody skips. Three moves, one that works. Send a new member up.

The missing stair
The workaround is knowledge, and knowledge does not onboard. Send someone up.

Healthy communities fix the stair, not the people around it.

Pervocracy, "The Missing Stair," 2012 · exit beats voice: Hirschman, 1970
the trust economy

Two currencies. Months to mint, seconds to burn.

Procedural trust

The rules work even when people are mad. Written down. Survives turnover. Rebuildable by design.

Personal trust

You believe this specific human follows through. Built over years. Outlives any procedure.

handbook trust economy
the discipline mattered more than the volume

The same skepticism for my own side.

Asking whether you are wrong, while you build the case, is what separates an investigation from a witch hunt.

Repeated audits, and more than one set of eyes, went looking for my own errors, including whether I was part of the harm. One pass killed a claim I had repeated for years. That is the only reason I trust the rest of it.

the audit you run on yourself

The mirror.

I held the receipts and wrote the patch. That position has failure modes. Flip each virtue.

The returning hero

comes back with energy and fixes

The invader

Experienced as an invasion even when every change is good. Set the pace with the people who stayed.
FLIP

The systems builder

writes it all down

The benevolent sovereign

Whoever holds the receipts shapes the truth. I am that person in this story. Naming it is the only defense.
FLIP

The prosecutor

right about the harm

The identity threat

You cannot repair through an identity threat. Make it safe to be a good person who did a harmful thing. That applies to you too.
FLIP
If the analysis makes everyone look bad except the analyst, it is not analysis.
part three

For Your Space

The copyable kit: the parameters, the patch, the platform.

the default operating system

Do-ocracy: who does, decides.

Authority earned through action, not election. Genuinely great, and it fails three specific ways.

Vetocracy

People who do none of the work blocking the people who do all of it.

Glamour bias

Fun work gets claimed. Chores pile on the same few, meeting after meeting.

One-way doors

"Oops, I threw out that pile of parts." You cannot un-paint a room purple.

The patch is one habit: you never need permission, you always say what you are about to do.
three shapes trust makes

Patterns to watch for.

Newcomer barrier

Members trust each other. New members start at zero. Without onboarding they feel excluded and disappear.

Clique formation

Uneven trust makes subgroups. Sometimes specialization, sometimes the fault line the next conflict runs along.

Evaporative cooling

Tolerated bad behavior drives out the best members first, concentrating the problem in who remains.

Even one tolerated bad actor can reset an entire culture. Boundaries protect the flock.
Yudkowsky 2007 · Felps et al., "Bad Apples," 2006
the same result, feathered

Select for the flock.

In animal breeding, selecting the best individual hens bred bullies and cut the yield; selecting the best whole flocks raised it 160%. A community runs on the same math: reward the loudest stars and you breed friction; reward the health of the whole room and everyone gains.

Selfishness beats altruism inside a group. Altruistic groups beat selfish groups. So build for the flock, not the stars.
Group-selection result attributed to D.S. Wilson, cited via McManus, t-1ventures, 2021
the full menu

Six ways a room full of people can decide.

Every hackerspace runs on one of these, or a blend. Naming the model you are actually using is half the work.

Do-ocracy

Authority follows action. Whoever does the work makes the call.

Breaks when: nobody owns the boring or the irreversible.
Consensus

Nothing passes while anyone still actively blocks it. Everyone has to consent.

Breaks when: one holdout can freeze the whole room.
Consent / Sociocracy

Not "is this best?" but "good enough for now, safe enough to try?" Decided in small circles.

Breaks when: run loosely, without the training it needs.
Majority democracy

Members vote, more than half wins. One member, one vote.

Breaks when: 51% can steamroll the other 49 every time.
Representative board

Members elect a board that decides between meetings.

Breaks when: it drifts from the floor and no one is watching.
Benevolent dictator

One founder or leader has the final say. Fast and coherent.

Breaks when: they burn out, or stop being benevolent.
MOST HEALTHY SPACES RUN SEVERAL AT ONCE. WRITE DOWN WHICH DECISIONS BELONG TO WHICH MODE.
who decides what

"Should we buy a $5,000 CNC router?"

Same question, four operating systems. Click each.

One purchase, four constitutions
Time to decide
?
Who was heard
?
Pick an operating system and see how the same purchase plays out.
Healthy spaces blend all four. Write down which decisions belong to which mode.
two schools on conduct

One rule, or write it all down.

Noisebridge: one rule

"Be excellent to each other." In practice it rests on a stack: standards, an anti-harassment policy, a conflict ladder, a ban list. Their own wiki names the flaw.

Gent: write it down

Conflict nearly killed their space. Afterward they wrote the whole hidden layer down and published it as a forkable repo.

noisebridge.net/wiki · github.com/0x20/hackerspace-blueprint
sorting the fights

Not everything uncomfortable is an attack.

Essential

Real differences over direction and shared resources. Necessary for growth.

Inessential

Personal attacks, grudges, territory. Destroys communities through quiet departure.

The tell is the target:direction and shared resources, or identity and territory.

cf. Jehn, 1995 · Guetzkow and Gyr, 1954. Even task conflict is net-negative (De Dreu and Weingart, 2003): "essential" means necessary, not free.
the space that wrote it all down

They learned the hard way.

"We had two rules: be excellent to each other and decide everything by consensus. We thought normal human interaction and common sense would solve all problems. Sadly, this was not true: internal conflict almost killed our hackerspace." 0x20 Hackerspace Gent, the Hackerspace Blueprint
A working conduct code needs: tiers, minimum consequences, a clock the board must meet, and enforcement the accused's allies cannot veto.
the gate without a gate

Safe space is a claim you have to back.

Signal at the door

What hangs on the walls, who is in the photos, how the first five minutes feel. Signaling self-selects your culture without a gate.

Teeth behind it

A code of conduct without enforcement is decorative, and everyone can tell. Rules without process are theater.

The nuance

Radical inclusivity does not mean tolerating bigotry. Refusing bigotry does not require policing thought.

A space with no gate gets missing stairs; a space with a hard gate becomes a cult.
the actual job

Running a space is mostly people work.

Train mediators

Conflict-resolution training is core infrastructure, like the fire extinguisher. Hold space without micromanaging or overstepping.

Build the ladder

Direct conversation, then a neutral third party, then the formal process. Safety concerns skip to formal.

Welcome on purpose

A newcomer decides in five minutes. The welcome is whoever looks up and says, hey, what are you working on?

Zehr 1990 · Mingus, pod mapping, 2016 · brown 2020
who runs this place

Six constitutions, one teardown.

I compared six sets of bylaws line by line: Noisebridge, Sudo Room, Hacker Dojo, All Hands Active, 0x20 Gent, and ours.

The power map

On paper, power sits with members or boards. In practice a third pole runs every space: whoever does the work.

The twins

Noisebridge and Hacker Dojo are textual near-twins, the same template, at opposite ends of the power map.

The honest one

Gent wrote the hidden layer down: a cookbook with its rationale attached, amended by pull request.

READ YOUR BYLAWS BEFORE THEY GET INTERESTING
what survival costs

Never comfortable. Never fatal.

YearRevenueExpensesNet
2011$58K$34K+$24K
2019$95K$71K+$24K
2023$57K$69K-$12K
2025$54K$56K-$2K
IRS 990-EZ via ProPublica, EIN 27-1277735 · 2025 figures year to date through November
name the loop

You just watched the lifecycle.

FOUNDhigh trust, low structure
GROWnorms stop scaling
STRESSlabor strains
BURNa few do most, then leave
RENEWor die

The burnout spiral: a few do most of the work, build quiet resentment, then leave suddenly. The knowledge leaves with them. Average program lifespan at my space: 3.5 years, each living and dying with its champion.

cf. Iriberri and Leroy, 2009 · the Sine Curve Pattern, 24C3, 2007
if you write bylaws this year

The parameters every space must set.

An undefined parameter has a default: whoever is loudest, whenever it happens.

the question every space has to answerour version
LEGITIMACY · how many people make a decision binding?8 at a meeting
RECALL · who can force a vote on power, without power's consent?8 members, or 10%
CLOCK · how fast must the org answer a report or petition?48h ack, 30 to 60 day vote
RATE LIMIT · how often can the same fight rerun?6-month cooldown
REMOVAL · what threshold takes a seat?2/3 of votes cast
MONEY · how many hands on every dollar?2 signatures
ACCESS · who grants 24/7 trust, and how is it revoked?vote of 5+ cardholders
CONDUCT · what is unacceptable, and who cannot veto enforcement?never the accused's allies
Ostrom, Governing the Commons, 1990. Healthy spaces implement it by accident. Write it on purpose.
the patch

We wrote a recall switch.

Member-called special elections. A fixed number of members, or ten percent of cardholders, forces a confidence vote on any board seat. Cities have had recall since 1903. Most hackerspace bylaws still do not.

Route around the veto

Never place removal power solely inside the group that would have to remove itself.

Higher role, higher bar

Removal from a role is not removal from the community.

Guard the valve

Every safety valve is also an attack surface.

Design every clause for the day it gets pointed at your side. Someday it will be.
municipal recall: Los Angeles, 1903 · "vetocracy": Fukuyama, 2011
tooling encodes ethics

Artifacts have politics.

Every rule you write and every default you ship is a decision about how you treat people. Build them around compassion, not raw enforcement.

  • A lapsed member is a person, not a churned customer. Design for their return, not their deletion.
  • A missed payment is a reason to check in, not a reason to lock someone out. Grace first, rules second.
  • Write the humane exception before you need it: the member who got sick, went broke, or drifted off and wants back in.
cf. Langdon Winner, "Do Artifacts Have Politics?", 1980 · Lessig, Code, 1999
what seventeen years compressed into

Five findings.

  • Culture beats structure. Healthy culture with minimal rules beats elaborate bylaws with toxic people.
  • Do-ocracy needs guardrails. Growing spaces need mechanisms for the decisions that cannot be undone.
  • Trust is the real currency. None of it works without members trusting each other.
  • Fix the missing stairs. Rules without enforcement are decorative.
  • Plan for succession. Burnout kills more spaces than rent. Make stepping back normal.
"In the end, running a hackerspace is an HR problem." Jenny List, Hackaday, 2018
HeatSync Labs Member Handbook, 2026
the skill under all of it

Hold both.

Real harm, and a real person worth compassion. A right outcome, and a dirty process. The maturity that lets a community survive a crisis is refusing the single clean verdict.

the ending, again. now you can read it

45 – 5

July 9, 2026. More than fifty members in the room, a turnout record. The seat changed hands. Nobody lost their membership.

Procedural trust, built while everyone was still mad. That is the hack.

The room, in person, healed what the channels inflamed. The mechanism held because it was ratified before anyone needed it.

A community is not a product.
It is a practice.

Being the villager is the whole job. Keep showing up. Keep building trust. Keep fixing stairs.

"Your hometown needs a hackerspace. It's the only way they've ever happened: people like you started them." Mitch Altman
everything ships

It all ships.

the self-hostable management platform

A self-hostable platform for running a space: members, dues, doors, classes. Plus the research kit: the atlas, the games, the handbook, the field notes. All open.

hackerspace.sh
and then everyone plays

Spin Up a Hackerspace

doot.games

5 minutes, 9 rounds. Name a space, ratify a bylaw, survive the quiz.

doot.games/g/g_dbcbcd522c14

Room code:

Scan the next slide to play.

scan to join

Play it on your phone.

Room code:

scan to join the room on screen

or host your own later

Run it yourself anytime.

doot.games/g/g_dbcbcd522c14

Host on a screen, play on phones.

hack.build

hack.build

hack.build · hackerspace.sh · @virgilvox

Be excellent.

acknowledgements & references

Standing on.

Movement & governance

Ohlig & Weiler (2007) · monochrom (2009) · maxigas (2012) · Ostrom (1990) · Freeman (1972) · Shirky (2003) · Fukuyama (2011) · Nathan Schneider (2024) · the Noisebridge wiki · the 0x20 Hackerspace Blueprint

Trust, conflict & repair

Axelrod (1984) · Nicky Case (2017) · Slovic (1993) · Tyler (1990) · Jehn (1995) · Suler (2004) · Hirschman (1970) · Pervocracy (2012) · Yudkowsky (2007) · Felps et al. (2006) · Williams (2018) · Zehr (1990) · Mingus (2016) · brown (2020)

Political lineage & primary sources

Kropotkin (1902) · Popper (1945) · Winner (1980) · Spade (2020) · HeatSync calendar, wiki, and chat archives · the survey (n=28) · IRS 990-EZ via ProPublica · the Member Handbook · the July 9, 2026 minutes

Thank you:the folks from Noisebridge, Hacker Dojo, All Hands Active, Hive76, Pumping Station: One, CRASH Space and Sudo Room; Hackerspace Gent for publishing their scars; Mitch Altman for the movement's memory and its keys; Mickey McManus for pointing at the trust game; Nicky Case for building it; and HeatSync Labs, the beloved substrate.

Full annotated bibliography and slides at hack.build
← → navigate · F fullscreen · P presenter · demos are live
PRESENTER
waiting for stage window
Now · 1 / 60
Next up
Elapsed
0:00
Target
This slide
0:00
Press Start, then drive with Next / Prev or the arrow keys.
Doot room code (drives audience QR)
blank = QR links straight to the game
target pace —