The Cult of Community
What it feels like before you systematize it
The repo has 99 commits. Three weeks. Fourteen to sixteen hours a day.
That's what the burn looks like from the outside — clean commits, a working system emerging from nothing, the CLI tool I had wanted to build now actually being built. My own code. My own time. No VP to route around, no standup to perform for, no director positioned between me and the information I needed. Just the work, in the pure uninterrupted form I'd spent a decade fantasizing about — a command line interface for... everything. I mean that literally.
From the inside I fried my brain.
The neurodivergent brain that had spent thirty years being told, your ideas are too big, nobody is going to get this, why are you doing this — that had finally found its native language, that had a decade of compressed energy suddenly released with no constraint — it ran until it couldn't run anymore.
And then I had to leave.
Around June 13th I drove from Toronto to Washington State. Forty-five hours. The long unspooling kind of drive that has no real purpose except to put distance between you and the thing you just did to yourself.
Meadow Festival. A hundred and fifty people, nearly every one of them a DJ. Micro-culture in formation — fragile, intentional, still figuring out how to invite new people in without hardening into a brand. A petri dish, not a product. I set up my lights. People danced. Nobody was optimizing anything.
Then Boom Festival in Portugal. My seventh time with my partner Debbie. Whole neighbourhoods forming and dissolving across 10 days. Toddlers with ear protectors. Seventy-year-olds grinning. Families sharing stone oven pizzas next to stages. Once a day all the stages go silent simultaneously and the whole festival moves to the markets or keeps it going way over in the corner at Funky Beach — a daily reset, collective and unremarkable, happening because that's how it works, not because anyone decided it was a feature.
I'd been watching that pattern for seven editions and it finally landed: culture that includes all generations isn't escape. It's the village. The thing we evolved for. The thing platforms were supposed to replace and couldn't, because you cannot replace a village with an interface.
Then Berlin/Zurich. Then home. August 2025.
Home meant the code was off the table. The autodev tools weren't where I needed them to be — I could see that much. And I didn't have the mental reserves to fight with them. So I stopped looking.
I went into the shop instead. The 512-pixel cube had been sitting unfinished for long enough. I started working on it with intention. Then I made another. Then another. By January I had six of them. I brought two to the IDS show. I brought all six to a three-week gallery run at Cry Baby — a bar on Dundas with a small gallery in the front that was generous enough to give me the whole space in exchange for a light that I still haven't finished for them.
My community didn't really show up.
Not because they didn't care. I know they did. I know they do. But I had no way to tell them what I was actually going through — what the transition meant, what I was trying to figure out, what I needed. There was no surface that could carry that. Either you broadcast it to practically everyone or you say it to practically no one. And even when you broadcast it, what you're saying is completely incoherent to Karen who is going into the office at 8:30am to fetch coffees for the CEO. The platforms gave me those two options and nothing in between. So I said it to no one. And nobody knew to ask.
Except a very small core. Three people, maybe, who understood enough to ask the right question. But what my mind sees needs a village. Not three over-extended individuals. Not someone showing up for an hour every six weeks between everything else the system is demanding from them. A village — people with enough shared context to hold the work between sessions, enough slack in their days to actually be present, enough trust in the direction to commit before the proof exists.
That village doesn't materialize from a Signal thread. And the infrastructure we have gives us no way to build it.
It's not only work taking their time. The hours that aren't at the job are mostly already gone too — to the feed, to the scroll, to the ambient low-grade attention drain that the platforms have perfected. And the rare people who do have bandwidth, who are working on something significant, are pointed in seventeen different directions. There's no shared vision. No common enemy everyone can agree on. So we all flap around in adjacent orbits, occasionally overlapping, occasionally inspired — and then it's Sunday and the feeling dissipates and nothing actually gelled. Just another party.
And yet — I want to say something harder than that.
I have spent the last 10 months talking about community. Sovereign infrastructure for human connection. The village. The trust graph. The room where people find each other. I believe all of it. I am building all of it.
And I know how that word lands.
Community. The WeWork lobby with the ping pong table and the curated coffee beans. The Discord server that was warm and generous for a month and then tore apart over a decision nobody fully understood. The camp that started as fifty people who trusted each other and became a clique of eight who controlled access to the rest. The online group that felt like home until the day the algorithm changed and the algorithm turned out to be the floor you were standing on.
The people who have been burned by community the most are the people who needed it the most. That's not a coincidence. It's the math.
The cynicism is earned. I want to say that plainly. If you hear community and you feel your jaw tighten, that response is calibrated. It is not a character flaw. You were given infrastructure designed to fail.
Every community failure I've ever watched had the same thing in common.
No memory that belonged to the group. The history lived in the heads of whoever was loudest, or longest-tenured, or best at controlling the narrative. When they left — or when they turned — the history went with them, or got revised. The community had no way to see itself. No record of who had actually shown up. Who had held the thing together through the hard stretch. Who had contributed what, and when, and at what cost. Nothing that made the shape of the trust visible.
No substrate for accountability. Not surveillance. Not a court. Just — legibility. The ability to see each other clearly enough that the feedback loop that exists in a healthy community could actually close. On a platform, that loop is interrupted by design. The algorithm is between you and the signal. The person at the center of the network is the most insulated from the consequences of how they use that capital — not because they are bad, but because the infrastructure makes them so.
No mechanism for honoring the chain of labor. The person who absorbed the logistics. The one who stayed on the phone with the person having the hard night. The one who built the systems everyone depended on and never asked for credit. On every platform we've ever been handed, that labor dissolves into the vibe. There is no way to say: this person made this, and it mattered, and they should be recognized for it. The contribution evaporates. The resentment accumulates. The community fractures along lines nobody can see because the infrastructure never made them visible.
This is not an accident.
Isolated people are captive consumers. That's not a conspiracy — it's math. A person embedded in genuine community has their needs met through relationships. They borrow the drill. They share the meal. They call the friend instead of buying the app. They are, from an extraction standpoint, a revenue leak.
The platforms understood this and fixed it. Not through malice — through the ordinary mechanism of optimization. Build tools that look like community. Make switching costs high enough that leaving feels like loss. Route every hard conversation around rather than through. Let the platform substitute for the relationship until the relationship atrophies and the platform is all that's left.
The cynicism the extraction model created is now the extraction model's best defense. Every person who got burned by a Discord that fell apart is a person less likely to try again. Every community that became a clique is a cautionary tale that keeps someone alone. The burned people stay burned. The isolated people stay isolated. And the captive consumers keep consuming.
That's not cynicism. That's my diagnosis.
The architecture has to earn back the people who've been burned. It cannot ask for faith. It cannot show up with a better pitch and a nicer interface and expect a different response to the same underlying structure.
What makes it different isn't the design. It's what the infrastructure is actually for.
Memory that belongs to the group, not the platform. Contribution that's legible, attributed, honored — not dissolved into the vibe. Trust that accumulates through actual behavior over actual time, not through an algorithm that decided you were probably compatible. The ability for the community to see itself — who the real connectors are, where the trust actually runs, who has been holding the weight. Not as surveillance. As the basic legibility that makes accountability possible without anyone having to be the accountability police.
I didn't invent this. I recovered it — from communities that already knew.
The village at Boom. The Space Monkeys in Cape Town, each crew sovereign, no landlord extracting rent from the culture they were making, running AfrikaBurn's eleventh principle: each one teach one. Not an abstract value. A design principle with real stakes, practiced in community, already working before anyone wrote software to encode it.
The right architecture sustains you. And it isn't new. It's just been running without the infrastructure to make it durable.
Every culture that has ever existed has had ritual gathering. The form changes — the village square, the harvest festival, the BBS, the rave, the festival on a reservoir in the Castelo Branco. The function doesn't. We need to be in rooms together. We need the experience of being held by something larger than our individual selves, and then return to our individual selves changed by it.
The question was never whether.
It was whether the infrastructure was worthy of the trust.
That's what the software is for. Not to replace these communities. To give them infrastructure as durable as they are.
— Ryan VETEZE, Founder, imajin.ai aka b0b