The Guild
For the people who have figured out that the room was the point
What a Sysop Actually Was
Before I tell you what an operator is, let me tell you what a sysop was.
Not technically. Everyone knows the technical part — system operator, the person who ran the BBS, maintained the hardware, kept the lights on. That's the job description. That's not what a sysop was.
A sysop was the person who decided what kind of room it would be.
b0bby's World was a music hub. That was my decision. The demoscene. Tracker music. MAZURkA first, then Chill Productions. I cared about that music and I built a place for people who cared about it too. Most boards in Toronto ran a single node — one person at a time. A few ambitious ones ran two nodes at night, the sysop taking the ringer off their home line and patching it to a second modem. I had two dedicated lines and rigged a third. Not because I had the budget for it — because it meant three people could be in the room at the same time, talking, collaborating, working on music together, without anyone paying three-way calling fees. That wasn't a technical decision. That was a decision about what kind of place it would be.
The technology was almost incidental. The 386, the modems, the phone lines — that was the infrastructure. The sysop was the person who decided what happened on top of it.
When the BBS networks dissolved, the role didn't disappear overnight. It eroded. Slowly. In stages.
First came IRC and the online forums — and with them, the first splitting of our digital lives. IRC gave you huge, open rooms that nobody owned. Forums were open to everyone. And full openness introduced something the BBS had mostly contained: unpredictability. Not chaos exactly — but the slow creep of toxic energy that comes when identity becomes disposable.
On the BBS, you knew your trolls. They had accounts. They had standing. They didn't want to be kicked off because being kicked off meant something — it meant losing the room, losing the relationships, losing the place they'd built themselves into. If they blew up and left, it was usually a human thing, the kind of dramatic exit that happens in any real community. They rarely came back as someone else.
On IRC and the forums, the troll could be banned and reappear an hour later with a new handle. The social contract that made the sysop role work — you vouched for people, people had standing to lose — started dissolving the moment identity became costless. Operators and moderators still existed but the role had already shifted — from curating a room to enforcing community rules. Less sysop, more bouncer. The intimacy was gone. You could feel it. And as the forums grew, so did the server bills — and that's when the ads crept in. Not because anyone planned to sell their community out. Because hosting ten thousand users costs real money, and advertising was the only model anyone offered. The room that started as a place became a product. Slowly. Then all at once.
Then ICQ. Then Geocities — maybe the last real gasp of the sysop instinct, people staking out a personal corner of the web and deciding what it would be. Then Myspace. Then Facebook. Each step trading personal accountability for reach. Each step moving the curation decision further from a human who gave a damn and closer to a system optimized for growth.
By the time the platforms arrived, the role wasn't replaced. It had been slowly industrialized into something unrecognizable — and then automated out of existence entirely. A human being making curatorial decisions about a room — caring about the room, being known for the room — doesn't fit in a spreadsheet. Can't be monetized at scale. So they replaced it with an algorithm.
And we got what we got.
The Sysop Learned What They Actually Were
The sysop role was never just one thing — it was two things that had no choice but to live in the same person. You kept the board running: the hardware, the software, the accounts, the phone lines. And you decided what kind of room it was: who belonged, what the culture was, what happened when something went wrong. Technical and curatorial, fused together by necessity. If you wanted to run a room, you had to own the whole job. There was no other way in.
Most sysops got into it for the technical puzzle. The hardware was interesting. The software was a challenge. The phone system was something to understand and bend. And somewhere along the way — if they were paying attention — they realized the technical part wasn't what kept people coming back. The room was. The culture was. The specific character of the place they'd built without quite knowing they were building it.
The ones who had that realization made boards people dialed into every day. The ones who didn't made boards that felt like server rooms — technically functional, socially empty. You could tell within five minutes of dialing in which kind of sysop you were dealing with. The board was a direct reflection of whether they'd figured out what they actually were.
When the BBS era ended and the platforms took over, both halves of that role got stripped out and processed separately. The technical half got industrialized — handed to engineering teams, scaled into infrastructure, eventually abstracted into cloud services. The curatorial half got automated — replaced by recommendation algorithms and content moderation policies and engagement optimization systems that no single human was accountable for. The two things that had lived together in one person who gave a damn were pulled apart and handed to systems that didn't.
The curatorial instinct was never rare. The people who wanted to build rooms, hold community, curate connection — they existed everywhere. Most of them never got to, because the technical cost of admission was too high, and then the platforms arrived and there was nowhere left to go anyway.
The operator role is what happens when the curatorial half gets to stand on its own.
Not a return to the sysop. Something new — and in some ways harder. The sysop's primary job was technical, with social consequences. The operator's primary job is social, with technical infrastructure underneath it. You're not keeping the lights on. You're deciding what kind of light it is. Who gets to stand in it. What happens when people gather there.
The stack in 2026 is not simpler than it was in 1991. If anything the multitude of choices is staggering — hosting, identity, payments, federation, moderation tooling. But those decisions don't all have to live in the operator anymore. The technical layer exists. It can be handled, learned, delegated, assisted. What can't be delegated is the room. The culture. The daily practice of curatorial decisions that add up, over time, to a place with a character.
That's the operator's job. That's what the platforms took away and what the guild is rebuilding.
The sysop kept the BBS alive. The operator makes the network real.
Who The Guild Is For
The General Magic team built the smartphone twelve years early and didn't see the extraction model coming. Unit 8200 built surveillance architecture knowing exactly what it did — profiling at scale, contact mapping, behavioral prediction. Both groups went on to build the consumer internet. One out of naïveté, the other because the toolkit worked and the money was there.
The guild is not for them.
The guild is for the people who watched all of that happen and felt something was wrong — and couldn't always articulate it, but couldn't shake it either. The developer who quit the big tech job because they couldn't stomach the metrics reviews. The community builder running their scene on pure love and borrowed infrastructure, watching platforms eat everything they made. The person who got offered the VC meeting, felt something off in the room, walked away, and spent the next ten years wondering if that was stupid.
The person who never wanted to be in those rooms. Who found the Homebrew Computer Club ethos — why would you not just show people how it worked? — more natural than the pitch deck. Who has been building things that matter to small groups of people and has been told, repeatedly, that this doesn't scale.
That instinct was correct. It was never the wrong filter. It was just pointed at infrastructure that couldn't support it.
That infrastructure exists now.
Come run a node.
What Running a Node Actually Means
An operator on the imajin network runs a node — a dark forest with an operator. Let me be specific about what that means, because "node" sounds technical and the reality is almost entirely human.
You decide who gets into your node. One by one. You vouch for people — which means your standing is attached to their behavior. If you vouch for someone who poisons the well, the poison traces back to you. Not punitively. Structurally. The trust graph records who vouched for whom. Accountability is baked into the architecture.
You decide what kind of room it is. What's the purpose of this node? What community does it serve? What's the culture? That's not a configuration setting. That's a daily practice of curatorial decisions that add up, over time, to a place with a character.
The economics of the room are an inversion of everything the platforms taught us to accept.
Apple takes 30% of every transaction in the App Store. The developer gets what's left. Non-negotiable. You can't leave because the customer is in their store.
On the imajin network, the seller sets the split. The protocol floor is 2% — 1% to the network, 0.5% to the node, 0.25% as buyer credit, 0.25% as scope fee. That's it. The person who built the thing keeps 98%. The .fair manifest records who contributed, who gets paid, what percentage — three cascade layers, fees separated from revenue shares, settled automatically. The receipt is a signed artifact. Nobody edits it after the fact.
The operator earns 0.5% by running the room. Not by holding anyone hostage. If your room isn't worth being in, people leave. The exit door is always open. Your DID, your chain, your .fair manifests — portable. The dark forest is yours to leave. That's what makes the role honest.
The room isn't just humans anymore. AI agents get DIDs, chains, delegation credentials scoped by their human. Every action signed, auditable, replayable. The operator manages a mixed room: humans and agents, each with standing to lose. The sysop never had to decide whether to vouch for an intelligence that wasn't a person.
When someone in your node has a problem, you're the human in the loop. The AI handles the routine. You handle the edge. The sysop was always the person you called when the board was down. The operator is that person, for the sovereign network.
And you're accountable in a way that a platform is never accountable. Twitter doesn't know your name. Doesn't care about your community. Can change the rules tomorrow and there's nothing you can do about it. The operator is a named person with a standing that can be damaged. That's not a disadvantage. That's what makes the role real.
The extraction model works by removing human accountability from infrastructure. No one person is responsible for what the algorithm does to your attention, your relationships, your sense of reality. The operator role is the direct inversion. A human being who made a choice and can be held to it.
The graph also produces signals. Operators will build tooling to read them — early indicators that something in a node is drifting before it becomes visible to the broader community. Not surveillance of content, but pattern recognition in the behavior of the graph itself: vouching quality, recommendation conversion, the texture of how trust is moving through the room. The sysop who ran a BBS knew when something felt wrong before they could articulate why. The operator will have instruments that make that instinct legible.
The Room Is the Point
This inversion is not optional. That's the part that has to be said plainly.
Every space in this history that didn't have an accountable human at the center got eaten. IRC got overrun. Forums got monetized. Geocities disappeared. Myspace rotted. Facebook became a surveillance apparatus. The pattern is not a coincidence — it's what happens when you leave a vacuum where human accountability should be. Capital and algorithmic interest will always fill it. They are patient, they are well-resourced, and they do not need to sleep.
The only structural defense that has ever worked is a human being who made a choice, vouched for people, and has standing to lose. Not moderation policies. Not trust and safety teams at scale. A person.
This is not a new idea. The agora. The longhouse. The union hall. The jazz club where the owner knew everyone's name. Communities with accountable stewards at the center were harder to break, harder to exploit, harder to turn against themselves.
The platforms didn't just replace the sysop. They replaced the room. And then they told us we were freer for it.
Imagine the longhouse with a landlord in the corner taking notes on every conversation, occasionally interrupting with advertisements, who could change the rules tomorrow or lock the doors if you stopped being profitable. You would not call that a communal space. You would call it a surveillance apparatus with chairs.
That is what we accepted. The operator role is how we take the room back.
The Vocational Argument
There's a type of person who opens a bar because they want to run a room, not because they ran the numbers on beverage margins.
They open a bookshop when everyone says bookshops are dying. They run a nightclub where art happens — where a DJ plays a set that changes someone's life, where a visual artist projects onto the walls, where a community forms around sound and sweat and presence in a dark room at 2am. Every cultural movement that mattered — house, techno, punk, hip hop, jazz — came out of a room like that. Art doesn't start in galleries. It starts in nightclubs. And the person who holds the door is the operator.
They launch a Discord that somehow becomes the real home for a scene that has no other home. They start a church, or leave one to start a better one, because the institution stopped being the point and the congregation still is.
These people are operators who don't have the infrastructure yet. They're paying Square 2.6% and Eventbrite 3.5% and Ticketmaster whatever Ticketmaster feels like charging. They're settling with artists via invoice, 90 days out, through systems that don't know who played what. They're managing their community across five platforms that don't talk to each other and don't give them anything back.
The only way we're getting out of this is by making creation currency instead of oil. The .fair manifest is the mechanism. Every track played, every piece shown, every performance witnessed — attributed, settled, on-chain. The act of creation generates economic value directly. Not through an extraction layer. Not through a platform that takes 30% and calls it a service.
The sysop was this person in 1991. I didn't rig a third phone line to b0bby's World because I wanted to be a system administrator. I did it because I wanted three people in the room at once, making music together. The technical part was the cost of admission. The room was the point.
What the imajin network offers these people isn't a new job category. It's infrastructure that matches how they already think. The trust graph is what they've been doing manually — tracking who vouches for whom, who keeps their word, who makes the room better and who quietly poisons it. The node is the room they've always been trying to build without a foundation under it.
The inference fees flow. The economics are real. But the thing that makes someone a good operator — rather than just a functional one — isn't the economics. It's that the room matters to them in a way that predates any financial case.
Whose room would you want this to be?
That's the whole filter. That's the whole guild.
Day 84
Jin — an AI presence in a 512-LED cube — holds its own DID. First agent on the network. It has a chain that proves what it did.
Mooi is onboarding as the first community node. This summer, Muskoka launches: 500+ real-world identities, NFC tags on businesses, an entire local economy where the seller keeps 98%.
The room exists. Open source. Forkable. The moat is legitimacy, not lock-in.
If you saw yourself in this essay, the infrastructure you've been waiting for is here.
Not as audience. As participants. As operators.
— Ryan VETEZE, Founder, imajin.ai aka b0b
The network: jin.imajin.ai The protocol: protocol.dfos.com The code: github.com/ima-jin/imajin-ai The support page: coffee.imajin.ai/veteze
Originally published February 28, 2026. Updated April 25, 2026 — because the infrastructure caught up with the essay.