How communities work, and why they break. A post-mortem of one lab's worst year.
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.
Browser-native projection mapping. Drag-warp, live-code, cast wirelessly.
lumencanvas.studioOpen-source node programming for audio-visual, 3D, and IoT.
latch.designA publishing platform for hardware projects. Share builds, docs, BOMs, and write-ups.
deveco.ioMake printable zines in your browser. Free and open-source.
zeenster.comArizona's first hackerspace: a community-run workshop in Mesa, founded in the 2009 wave and still open seventeen years later.
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.
Laser cutters, 3D printers, a wood shop, an electronics bench.
People who will teach you, help you, and expect the same back.
Norms instead of rules. Trust instead of hierarchy. Culture instead of coercion.
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.
A movement with a history, a politics, and a documented body count.
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.
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.
A family argument, not an outside attack:Grenzfurthner sat on the hackerspaces panel at The Next HOPE the following year, next to Altman.
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.
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.
Seventeen days ago, my hackerspace voted to remove a board member. Calm room. Record turnout. One evening. Nobody lost their membership.
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.
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.
The durable lessons from the data and the movement record, each with its receipt.
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.
2012: MAKE takes a DARPA grant to put makerspaces in a thousand high schools. Venture capital, tuition, staff, press.
Mitch Altman steps away from Maker Faire over that grant. Dues, drama, and sweeping your own floors.
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."
| open hours | 5,617 h |
| coffee and coworking | 3,676 h |
| classes | 2,081 h |
| cleaning and maintenance | 1,716 h |
| social events | 1,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.
When our conflict got loud it felt like the whole building was on fire. So I counted.
Calibration:read the fights as a portrait of the community under stress, never a portrait of the community. This rule cuts against me too.
The exit is silent:people who feel unsafe do not argue. They stop coming, and a count falling by ones never triggers an alarm.
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.
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.
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.
Pick a situation and watch the same members redistribute across public channels, private channels, and DMs.
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 we lived | Who named it | Year |
|---|---|---|
| The recall election we ratified | Los Angeles voters | 1903 |
| Informal groups still have power structures | Jo Freeman | 1972 |
| Commons survive on written rules | Elinor Ostrom | 1990 |
| A group is its own worst enemy | Clay Shirky | 2003 |
| The person everyone works around | Pervocracy | 2012 |
| Software defaults hand founders power | Nathan Schneider | 2024 |
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.
The method: read the source, run the sims, audit your own side.
| [VERIFIED] | primary document, quoted or cited directly |
| [INFERRED] | a reasonable reading, labeled as a reading |
| [CONFLICT] | sources disagree, and the disagreement is preserved |
A pass over the full history pinned exactly when and how the bylaws changed. Any space with a wiki can run this on itself.
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.
The copycat is most of your members. Whatever you do echoes.
Click any member to break trust in public, or use the button. Then race the two kinds of repair.
Visible public repair rebuilds faster than years of quiet one-on-one work. Most people repair in private, which is backwards.
Filled squares know the unwritten norms; hollow ones are guessing. Grow the space, then press the button nobody wants to press.
Click each card. Be honest about which are you.
Fixes the printer at 2am. Ships.
Loves meetings and opinions.
Pays dues, says little, is the majority.
Built it. Carries the memory.
Asks "why" about sacred cows.
???
Two kinds of work every month. Advance the months and watch who takes what.
The spreadsheet looks healthy right up to the resignation. The lasers are louder than the brooms.
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.
Healthy communities fix the stair, not the people around it.
The rules work even when people are mad. Written down. Survives turnover. Rebuildable by design.
You believe this specific human follows through. Built over years. Outlives any procedure.
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.
I held the receipts and wrote the patch. That position has failure modes. Flip each virtue.
comes back with energy and fixes
writes it all down
right about the harm
The copyable kit: the parameters, the patch, the platform.
Authority earned through action, not election. Genuinely great, and it fails three specific ways.
People who do none of the work blocking the people who do all of it.
Fun work gets claimed. Chores pile on the same few, meeting after meeting.
"Oops, I threw out that pile of parts." You cannot un-paint a room purple.
Members trust each other. New members start at zero. Without onboarding they feel excluded and disappear.
Uneven trust makes subgroups. Sometimes specialization, sometimes the fault line the next conflict runs along.
Tolerated bad behavior drives out the best members first, concentrating the problem in who remains.
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.
Every hackerspace runs on one of these, or a blend. Naming the model you are actually using is half the work.
Authority follows action. Whoever does the work makes the call.
Nothing passes while anyone still actively blocks it. Everyone has to consent.
Not "is this best?" but "good enough for now, safe enough to try?" Decided in small circles.
Members vote, more than half wins. One member, one vote.
Members elect a board that decides between meetings.
One founder or leader has the final say. Fast and coherent.
Same question, four operating systems. Click each.
"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.
Conflict nearly killed their space. Afterward they wrote the whole hidden layer down and published it as a forkable repo.
Real differences over direction and shared resources. Necessary for growth.
Personal attacks, grudges, territory. Destroys communities through quiet departure.
The tell is the target:direction and shared resources, or identity and territory.
What hangs on the walls, who is in the photos, how the first five minutes feel. Signaling self-selects your culture without a gate.
A code of conduct without enforcement is decorative, and everyone can tell. Rules without process are theater.
Radical inclusivity does not mean tolerating bigotry. Refusing bigotry does not require policing thought.
Conflict-resolution training is core infrastructure, like the fire extinguisher. Hold space without micromanaging or overstepping.
Direct conversation, then a neutral third party, then the formal process. Safety concerns skip to formal.
A newcomer decides in five minutes. The welcome is whoever looks up and says, hey, what are you working on?
I compared six sets of bylaws line by line: Noisebridge, Sudo Room, Hacker Dojo, All Hands Active, 0x20 Gent, and ours.
On paper, power sits with members or boards. In practice a third pole runs every space: whoever does the work.
Noisebridge and Hacker Dojo are textual near-twins, the same template, at opposite ends of the power map.
Gent wrote the hidden layer down: a cookbook with its rationale attached, amended by pull request.
| Year | Revenue | Expenses | Net |
|---|---|---|---|
| 2011 | $58K | $34K | +$24K |
| 2019 | $95K | $71K | +$24K |
| 2023 | $57K | $69K | -$12K |
| 2025 | $54K | $56K | -$2K |
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.
An undefined parameter has a default: whoever is loudest, whenever it happens.
| the question every space has to answer | our 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 |
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.
Never place removal power solely inside the group that would have to remove itself.
Removal from a role is not removal from the community.
Every safety valve is also an attack surface.
Every rule you write and every default you ship is a decision about how you treat people. Build them around compassion, not raw enforcement.
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.
July 9, 2026. More than fifty members in the room, a turnout record. The seat changed hands. Nobody lost their membership.
The room, in person, healed what the channels inflamed. The mechanism held because it was ratified before anyone needed it.
Being the villager is the whole job. Keep showing up. Keep building trust. Keep fixing stairs.
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.
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.
Room code: —
scan to join the room on screen
doot.games/g/g_dbcbcd522c14
Host on a screen, play on phones.
hack.build · hackerspace.sh · @virgilvox
Be excellent.
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
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)
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.