blackflag.dev | Blog

The Calculator and the Auditor: The Layer of Thinking You Can't Safely Offload

Wed, 08 Jul 2026 16:30:00 GMT

In part one I argued that cognitive debt is a design choice, not a property of the machine — and that the strongest evidence for it, Bastani et al. in PNAS, showed exactly that: the same GPT-4 harmed learning when it acted as a crutch and didn’t when it was built as a tutor. I left one thread hanging on purpose. I want to pull it now, because it goes somewhere the current research mostly doesn’t.

Here’s the number that hangs everyone up. In that study, the students who used the raw chatbot scored 17% worse on the exam than students who never had AI at all — once the tool was taken away. That’s the headline harm. And the very first honest reaction to it, the one I had and maybe you did too, is a good one:

Taking the tool away isn’t the real world. These tools are here now. Measuring people without them is measuring a situation that no longer exists.

That objection is half right. The half it gets wrong is instructive, and the half it gets right is the whole essay.

Why the “unfair test” objection is half wrong

Removing the tool is not a value judgment sneaking in the back door. It’s an instrument — an X-ray. Think about what happens if you only measure people while the tool is in their hands. During practice, the crutch group looked fantastic — 127% better than the control. If with-tool performance were your only yardstick, you’d conclude the raw chatbot was a triumph. You literally cannot distinguish “this tool is building real understanding” from “this tool is a beautiful mask over the absence of it” without, at some point, taking it away and looking underneath.

And here’s the proof that the X-ray is imaging something real rather than just penalizing tool-users for a missing crutch: the two AI groups diverged. Both had full tool access while learning. If removal were merely an artificial handicap, both would have been handicapped equally when it was pulled. Instead the crutch group cratered and the tutored group tested fine. Same removal, different results — which means the test isn’t measuring “do you have your tool,” it’s measuring what got built inside your head while you had it. That’s a legitimate thing to measure. The objection doesn’t sink it.

Why the objection is also half right — and the half that survives is the important one

But grant all that, and something still hasn’t been justified. The study treats internalized, tool-removed, transferable skill as the outcome that counts. That is a choice. A defensible one — but a choice, and it carries a buried assumption: that the valuable competence is the one you can perform alone, with the tool gone.

For a whole class of skills, that assumption is quietly false, and the calculator is the proof of concept.

You can still see the tail end of that panic in the culture. The fear in the 1970s was total: give kids calculators and arithmetic dies, nobody makes change, a generation goes innumerate. And you know what? The mechanism was real. Mental arithmetic did atrophy. Watch a cashier freeze when you hand them an extra nickel after they’ve already keyed in the amount — the register was going to tell them the change, and you just broke its script. That skill genuinely decayed.

But the verdict was wrong, because the world stopped requiring the skill in that form. We got spreadsheets. We got a calculator in every pocket. The competence didn’t vanish; it changed shape — from “compute it in your head” to “know what to compute, and know when the answer looks wrong.” Nobody in 1975 mourning long division could have pictured a person casually describing a problem in plain English and being handed the right formula. Which is now an ordinary Tuesday: you describe what you’re trying to do to an LLM, it tells you the Excel function exists, and you think huh, neat — and you don’t acquire the derivation, but you retain that the tool exists and roughly what it’s for. The next time, you reach for it faster.

That is a real competence, and it is arguably a better one than the thing it replaced. Call it what it is: discovery outrunning acquisition. Being able to map a fuzzy intention onto the right tool — even, especially, when you lack the vocabulary to search for it the old way — is a genuine skill, and for a lot of tasks it beats being able to derive the answer cold. The “unfair test” objection is pointing at this, and it’s correct: for skills the world will let you keep the tool for, measuring unaided performance is scoring a counterfactual that never happens.

So the pro-AI instinct is right. Discovery beats acquisition. Except.

The catch: some layers you can offload, and one you can’t

Here’s the disanalogy that bounds the whole thing, and it’s the load-bearing idea of this essay.

A calculator is bounded and checkable. You offload the multiplication, but the part of you that knows $90 change on a $10 bill is absurd — that part stays online. A calculator never once handed you a fluent, confident, wrong answer dressed up as a right one. Its failures are your typos, and you can feel them. The skill you offloaded (computation) and the skill you kept (knowing when the output is nonsense) are cleanly separable, and you kept the one that matters for safety.

That’s the tell. Not every layer of a task is the same, and they don’t fail together.

There’s a mechanical layer: retrieval, derivation, boilerplate, the rote first pass. Offloading it is mostly fine — that’s what tools are for, and it’s been fine since Thamus grumbled about the written word.

And there’s an evaluative layer — the auditor. The judgment that tells you whether the output you just got is any good. Whether the formula is real or invented. Whether the confident paragraph is also a false one. Whether the discovery you just made is a discovery or a hallucination wearing its clothes.

You can offload the mechanical layer and keep the auditor, and you come out ahead — that’s the calculator, that’s your Excel move, that’s discovery-beats-acquisition working exactly as advertised. But offload the auditor itself and the whole thing inverts, because now the skill you’d need to catch the tool’s mistakes is the skill you handed to the tool. An LLM, unlike a calculator, will absolutely serve you a beautiful wrong answer. Which means the evaluative layer isn’t optional garnish on top of AI use. It’s the thing that makes the offloading survivable.

And notice — this is the part I want to be honest about — your own Excel example secretly runs on a retained auditor. You can pull off “describe it vaguely, get the right formula, trust it” because you’ve spent decades around spreadsheets and can smell when the model hands you something plausible but off. You kept the judgment. Someone building from zero, offloading derivation and evaluation at the same time, can’t run the discovery move safely — they can’t tell a real formula from a confident fake, so every hallucination lands as truth. Discovery beats acquisition right up until you’ve offloaded the very faculty you’d use to judge the discovery. Then it’s just inheritance of whatever the model happened to say.

So here’s the problem with the studies

Hold that distinction next to the research and something uncomfortable shows up.

Nearly all of it — the MIT EEG study, Bastani’s exam, the correlational work — measures tool-removed individual performance. Can you do the thing when the AI is gone. That’s a fine instrument for the crutch-versus-scaffold question; it’s the X-ray from earlier, and it works. But it is close to silent on the question this essay says is the real one: is your auditor intact?

Those are different measurements. “Can you derive the formula unaided” tests the mechanical layer. “Can you tell when the model’s formula is wrong” tests the evaluative layer. A person can score terribly on the first and brilliantly on the second — that’s literally the competent modern professional, the one who offloaded the rote work and kept the judgment. And the current study designs would flag that person as harmed, because they underperform with the tool removed. The instrument can’t see the skill that actually protects them.

Which means the discourse has a blind spot shaped exactly like the thing that matters. We are rigorously measuring whether people can still do the mechanical layer alone, and mostly not measuring whether they can still audit the tool that does it for them. We’ve built a great yardstick for the wrong length.

What would a better instrument even look like? Something like: seed the AI’s output with plausible errors and measure whether the user catches them. Test performance with the tool but on genuinely novel problems where the tool’s fluent answer is subtly wrong. Measure calibration — does the user know when to trust the output and when to distrust it — rather than raw unaided recall. Measure the intent-to-tool mapping directly. None of that requires pretending the tool will someday vanish. It takes the tool’s permanence as given, and asks the question that actually follows from it: when you and the machine disagree, do you still have what it takes to be right?

Which is why guardrails matter more than “matter”

Part one landed on: guardrails matter, and whoever controls the design decides whether you get a crutch or a tutor. This is where that gets teeth. The right guardrail isn’t the one that merely slows down answer-copying. It’s the one that keeps your auditor in the loop — that hands you hints instead of conclusions specifically so the evaluative layer stays switched on and load-bearing. Bastani’s tutor arm didn’t just prevent cheating; it kept students doing the judging. That’s the mechanism worth protecting, and it’s the design spec worth demanding: not “does the tool withhold the answer,” but “does the tool keep me evaluating.”

And it’s why this loops back to who controls the thing. A tool optimized to be maximally satisfying will retire your auditor for you — friction is exactly what an engagement metric wants to sand off, and your judgment is friction. A tool you can shape, inspect, and steer can be built to keep you sharp on purpose. If the competence that keeps AI-use survivable is an intact evaluative layer, then the fight over who gets to design the tool is the fight over whether you’re allowed to keep it.

The honest caveat, again

Same disclaimer as part one, pointed at myself this time: I’m proposing a better measurement, not reporting one. As far as I can find, nobody has run the clean study — offload the mechanical layer, protect the evaluative one, and track judgment over years. Until someone does, “keep your auditor” is a well-motivated hypothesis, not a proven prescription.

But the argument doesn’t need the study to be useful, because it’s really a reframe. The panic asks will AI make us worse at doing things ourselves, and the answer is a shrug — sometimes, for skills that stopped mattering, and so what. The question worth its weight is will we keep the judgment to know when the machine is wrong — and that one, nobody gets to shrug at. It’s not about your ability to do the tool’s job. It’s about whether you can still tell when the tool didn’t.

The Crutch and the Tutor: Cognitive Debt Is a Design Choice, Not a Property of the Machine

Tue, 07 Jul 2026 16:30:00 GMT

Every time a new cognitive technology shows up, the same panic arrives with it, and the panic is always shaped the same way.

In Plato’s Phaedrus, the god-king Thamus refuses the gift of writing. His objection is specific and, honestly, sharp: writing will produce “the appearance of wisdom, not true wisdom.” People will stop building knowledge inside themselves and start relying on external marks. Memory will atrophy. Students will seem learned without being learned.

He was right about the mechanism. We did offload memory to the page. He was wrong about the verdict — writing also gave us cumulative, cross-generational knowledge that dwarfed the cost. But notice the structure of his mistake, because it’s the same mistake being made right now about AI: he correctly identified a real trade-off, then assumed the trade-off settled the question. It didn’t. The value depended entirely on what got built on top of the offloading.

So when the headlines ask “Is AI making us dumber?”, they’re asking Thamus’s question. And Thamus’s question is malformed. The research that actually holds up doesn’t answer “does the technology harm cognition.” It answers something far more useful — and far more political.

The evidence everyone cites is the evidence you should trust least

The study driving most of the doom is MIT Media Lab’s “Your Brain on ChatGPT”. EEG caps, essay-writing, three groups: ChatGPT, Google, and no tools. The ChatGPT group showed the weakest neural connectivity and, when later asked to write unaided, couldn’t recall their own sentences. Dramatic. Widely shared.

It’s also a preprint that was never peer-reviewed, with 54 participants (only 18 in the crucial hand-off session), one narrow task, one narrow demographic. And the lead author told TIME she rushed it out specifically because she feared a policymaker might “decide, ‘let’s do GPT kindergarten.’” That’s advocacy, not a finding. She has since spent considerable effort walking back the coverage — “we didn’t find any brain rot,” she notes, and they never measured IQ. Science pointed out the obvious: making damning claims from preliminary data, ahead of review, is not how you responsibly prevent bad policy.

The other frequently-cited paper, Gerlich (2025), surveyed 666 people and found a negative correlation between AI use and critical thinking. Bigger sample — but it’s self-reported, cross-sectional, and can’t establish which way the arrow points. “AI erodes thinking” and “people who already offload more gravitate to AI” fit that data equally well. A correlation cannot separate them. Anyone treating it as proof of causation is smuggling in an assumption the study never earned.

This is the media-literacy lesson hiding in plain sight: the scariest study and the most-shared study are often the weakest, precisely because alarming preliminary claims travel faster than careful ones. Follow the motive on the fear as skeptically as you’d follow it on the hype.

The study that actually settles something says something more interesting

The strongest evidence we have is Bastani et al. (2025), in PNAS — a randomized controlled trial with nearly 1,000 high school students in Turkey. Peer-reviewed. Causal, not correlational. No disclosed financial stake in the outcome. And instead of one AI condition, it ran two, which is what makes it worth your time.

One group got GPT Base: a raw ChatGPT-style interface, told to act as a tutor. Another got GPT Tutor: the same GPT-4 underneath, but with guardrails — it gave hints instead of answers, and was shaped by teacher input. A third group got no AI at all.

The results, in order:

During practice, the GPT Base group performed 127% better than the control.
On the exam, with the AI taken away, the GPT Base group scored 17% worse than the control group that never had AI at all.
The GPT Tutor group’s harm disappeared — it matched the control on the exam.

Read that sequence again. The raw chatbot made students look brilliant and learn nothing. When the scaffold was removed, they were worse off than if they’d never touched it. The mechanism, per the authors: students used GPT-4 as a crutch, copying answers — including the wrong ones — without understanding. The guardrailed version, doing the same underlying task with the same underlying model, produced none of that damage.

Here is the whole point: the difference between the harmful arm and the harmless arm was not the technology. It was the same technology. The difference was the design.

”Does AI harm cognition” is the wrong question. “Designed by whom, tuned for what” is the right one.

Once you see that the harm lives in the design rather than the model, the entire framing shifts. Cognitive debt isn’t something AI does to you. It’s something a particular configuration invites — and a different configuration prevents. The variable is whether the tool hands you finished cognition or scaffolds you into producing your own.

And the moment “it’s a design choice” is on the table, the next question is unavoidable: who makes the choice, and whose interest is it tuned to?

This is where the comfortable version of the conversation ends and the honest one begins. A crutch and a tutor are not just two designs — they are two business models. A tool optimized for engagement, session length, and daily active use has a structural incentive to be the crutch, because dependence is the product. A tool that made you so capable you needed it less would be, from that vantage, a failure. The answer-vending default isn’t a bug or an oversight. It’s the design that maximizes the metric the tool was built to maximize.

That’s not a reason for despair, and it’s definitely not a reason to romanticize going back to the textbook. The Bastani tutor arm proves the good version is buildable. The hint-not-answer, keep-the-human-in-the-loop design isn’t hypothetical — it exists and it works. The question is purely one of incentives: whose cognitive interest is the tool aligned with?

And the only durable way to align a tool with the user’s interest is for the user to be able to shape the tool. Steerable systems. Open weights and open prompts you can actually inspect and modify. Models you can run yourself, configured to scaffold rather than to vend. This is the unglamorous, concrete core of “digital sovereignty”: not a slogan about freedom, but the specific technical capacity to make your tools serve your understanding instead of someone else’s engagement graph. If cognitive debt is a design choice, then controlling the design is how you refuse the debt.

The question this frame doesn’t answer

Notice what the design argument settles and what it leaves wide open. It tells you a tool can be built to scaffold instead of to vend, and that whoever builds it decides which. That’s the collective, structural half — the half about power and control. It’s the half worth fighting over.

But it doesn’t tell you what happens inside you when you sit down with even a well-built tool, because there’s a second variable underneath the first, and the studies barely touch it: not just which design you’re handed, but which layer of your own thinking you hand over.

Every intellectual task has a mechanical layer — retrieval, derivation, boilerplate, the rote first pass. Thamus’s page has been carrying that layer for two thousand years, and offloading it is mostly fine; it’s arguably the whole point of having tools. But every task also has an evaluative layer — the judgment that lets you tell whether the output you just got is any good. Whether the formula is real or invented. Whether the fluent, confident paragraph is also a wrong one. These two layers are not the same faculty, and — this is the part that matters — they do not fail together. You can offload the mechanical layer and keep the evaluative one, and come out genuinely ahead. Or you can offload the evaluative layer itself, and lose the one capacity you’d need to notice you’d been handed garbage.

That distinction is where the most seductive pro-AI argument — discovery beats acquisition, who cares if I can’t derive it as long as I can find it — turns out to be true, with a catch sharp enough to deserve its own essay. Hold onto the two layers. We’ll need them.

A note on how early this all is

One honest caveat, because the field deserves it: this research is thin and young. The RCT above is one study, one subject, one age group, one culture. The scare studies are weaker still. Nobody has the longitudinal data yet to say what a decade of this does to a developing mind, and anyone claiming otherwise — in either direction — is selling something.

But “we don’t fully know yet” is not the same as “we know nothing.” We know enough to reject the malformed question. The evidence doesn’t support AI makes you dumber. It supports something more precise and more actionable: outsourcing the thinking means you don’t learn the thing you outsourced — and whether a given tool encourages that outsourcing or prevents it is a design decision, made by someone, in someone’s interest.

Which means the most important question isn’t about your brain. It’s about who’s holding the pen that designs the tool your brain now runs on — and whether you have any say in it.

That’s the argument for controlling the design. Part two turns the same lens back on us — on which layer of our own thinking we’re actually handing over — and asks a harder question: whether the research measuring all of this is even looking at the right thing.

What 'Open Source' Actually Means (and Why GitHub Is Betting You Don't)

Sat, 04 Jul 2026 09:30:00 GMT

Right now there’s a letter-writing campaign asking you to contact California’s legislature and tell them a pending AI bill would destroy open source software. It’s polite. It’s well-produced. It’s pitched in the language of community defense. And it’s coming from a coalition that includes GitHub — which is owned by Microsoft — alongside Mozilla, Hugging Face, and Black Forest Labs.

Before you pick up that pen, I want to give you something the campaign is quietly counting on you not having: a working understanding of what “open source” actually is. Because once you have it, the whole ask falls apart. Not because these are stupid people making a dumb argument — the argument is clever — but because it only works on someone who’s never looked under the hood of a software license. So let’s look. This is one of those things that seems intimidating and turns out to be simple, and once you have it, you’ll spot this move every time someone tries it on you again.

Supporting democratic accountability for dangerous technology is not the same as trusting the government to get everything right — it’s refusing to let corporations be the only people who get to write the rules.

What the bill actually says

The law is California’s AI Transparency Act — Business & Professions Code § 22757 — and the fight is over an update to it called SB 1000. Strip away the legalese and it asks a reasonable question: if you’re putting a powerful generative-AI system into the world, should you be able to license it to someone else and then wash your hands of what they do with it?

The bill’s answer is no. It says that if you build one of these systems and hand it to a third party, you have to require — by contract — that they keep the system’s transparency features intact (the disclosures that mark content as AI-generated). And if you find out someone stripped those features out, you have to be able to cut off their access, within 72 hours of learning about it.

That’s it. It’s a transparency-and-accountability measure. It’s not a secret attack on free software. Is it perfectly drafted? No — legislators writing technology law almost never get the details exactly right, and there’s honest work to be done making the language track how software actually functions. But the goal is sound: don’t let the people deploying potentially harmful systems license them out and walk away.

The corporate claim

Here’s how the coalition frames it. Open source licenses, they say, are irrevocable — once you grant someone the freedom to use, modify, and share your code, you can’t claw it back. That’s a real and genuinely important property of open source. And a law that forces you to build in a kill switch, they argue, contradicts that irrevocability. Therefore: this bill breaks open source. Therefore: oppose it.

On the surface, that has a ring of truth. Which is exactly why it works. So let’s take apart the two things it depends on.

The part they’re hoping you don’t know

Open source licenses come in two broad families, and neither one behaves the way the campaign implies.

Permissive licenses — MIT, BSD, and the like — are the loose ones. They let you do almost anything with the code, including redistribute it under additional terms of your own. That’s the key point: a permissive license already allows a company to layer extra conditions on top. So even if one of these AI systems were released under MIT, the company could add a compliance term and still be fully, legitimately MIT-licensed. The “irrevocability” objection doesn’t even bind here.

Copyleft licenses — the GPL family — are the strict ones, the ones built to keep software free all the way down the chain. And yes, these are irrevocable… as long as everyone keeps complying with the license. Here’s the part that matters: the GPL already anticipated exactly this situation. GPLv3 has a clause (Section 12; it’s Section 7 in GPLv2) that handles what happens when some outside condition — a court order, a contract, a law — makes it impossible to satisfy both the GPL and that condition at the same time. The answer the license itself gives is: then you stop distributing. The “escape valve” is written directly into the license text. The law doesn’t break the GPL. The GPL planned for the law twenty years ago.

In fact — and this is the detail that gives the whole game away — the Software Freedom Conservancy, an actual nonprofit that defends open source in court, points out that SB 1000 changing the word “revoke” to “terminate” makes the law track the GPL’s own language more closely. The amendment the coalition is fighting arguably makes things more compatible with open source, not less.

The part that makes it a smokescreen

And then there’s the fact that quietly dissolves the entire argument: the systems in question aren’t open source in the first place.

The generative-AI products at the center of this — the ones actually deployed in California — are proprietary. The model weights are trade secrets. The heavy machinery runs on a company’s servers, reached through an API, and what you install on your own device is a thin front-end. None of the companies raising the alarm has named a single genuinely open-source AI system that the law would harm, because there isn’t one to name.

So the campaign is asking you to defend the freedom of software that was never free — using your real love of something real (open source) as a battering ram against a law that inconveniences a proprietary business model. That’s the shape of the move. Learn the shape, because you’ll see it again: whenever a corporation wraps its regulatory dodge in the language of your freedom, ask whose freedom is actually on the line.

Critical support, not a blank check

None of this means the state is your friend or that this one bill is a masterpiece. It isn’t. Supporting democratic accountability for dangerous technology is not the same as trusting the government to get everything right — it’s refusing to let corporations be the only people who get to write the rules. You can hold both: the law needs work, and the companies telling you to burn it down are not doing it for you.

If you want to go deeper, read the Software Freedom Conservancy’s full breakdown — it’s the primary source for everything here, and they’ve posted a template letter to Senator Becker if you decide the accountability side is worth defending.

But even if you never send a single email, you walk away from this with the thing that actually matters: you now know the difference between open source as a legal reality and “open source” as a marketing sticker. That difference is going to keep mattering. Hold onto it.

The Architecture of Comfort: How Convenience Became a Containment Strategy

Fri, 03 Jul 2026 18:25:34 GMT

Comfort is the new drug, and it’s dispensed not in back alleys but in UX flows. The article that prompted this reflection—“Comfort is the new drug”—makes a quiet but devastating point: modern life has become incredibly effective at helping us escape discomfort, but not at helping us grow because of it. Those are two very different things. The distinction matters because the systems we’re building don’t just offer ease; they actively train us to avoid the very friction that cultivates skill, resilience, and political consciousness.

Look at the architecture of any major platform. The infinite scroll, the algorithmically curated feed, the one-tap purchase, the AI summary that saves you from reading the article. Each of these is a small surrender of agency packaged as a gift. They remove the need to decide, to search, to sit with the unease of the unknown. The result isn’t just a smoother user experience—it’s a population that has been gently, lovingly disarmed. When you never have to navigate the mild frustration of finding a server, choosing a client, or figuring out how federation works, you also never build the muscle that would let you leave the walled garden.

But here’s the nuance that the original piece nails: we don’t have to reject convenience entirely in order to reclaim growth. If someone wants to grow in a way that requires discomfort, they can do spiritual work. The task isn’t to manufacture unnecessary suffering by throwing away your smartphone or refusing to use a map app. It’s to become intentional about when and why you accept the frictionless path. This is where the fediverse exodus reveals something profound. People are not leaving X or Meta because Mastodon is easier—it very often isn’t. They’re leaving because the discomfort of the open web feels honest. It signals that you are a participant, not a product. The rough edges are the proof that no one is optimizing you.

The fediverse migration, which I’ve been tracking since the days it was a trickle, is gaining momentum now because the drug of comfort is losing its appeal. Algorithmic timelines promised to show you what you wanted, but ended up showing you what kept you engaged. Recommendation engines made discovery effortless but flattened your taste into a corporate prediction. The exodus is not a rejection of technology—it’s a rejection of a specific kind of technology: the kind that does the thinking for you. In that sense, the fediverse is a recovery meeting. Every time you have to manually follow someone, curate a list, or moderate your own server, you’re rebuilding the neural pathways that corporate platforms had atrophied.

Of course, the tech industry is already trying to re-inject its particular brand of comfort into the open web. AI assistants that write your posts, algorithms that filter your federated timeline, hosted services that make running a server “as easy as signing up for Netflix.” Many of these are helpful, and some of them are genuinely good. But we should be suspicious when the language of liberation is used to sell a product that erases the very labor that liberation requires. Spiritual work doesn’t depend on breaking your tools; it depends on noticing which tools you’ve let become your masters.

So what does a praxis of intentional discomfort look like? It might mean learning to self-host even when it’s annoying. It might mean leaving a comfortable platform for a less polished one, not because the new one is better in every way, but because the friction itself is informative. It might mean refusing to let an AI write your arguments for you, even when it would save you time. It might mean sitting with the discomfort of being misunderstood on a platform that doesn’t optimize for engagement, so that you can rediscover what you actually mean.

The drug of comfort is powerful because it doesn’t feel like a drug. It feels like the world bending toward you, anticipating your needs. But a world that bends too completely becomes a cage. The resistance builds spaces where the edges are still sharp, not because we love pain, but because we know that calluses form where learning happens. The fediverse is one such space. It’s messy, it’s uneven, and it asks something of you. That’s not a bug; it’s the point.

Owning the Terms: What Self-Hosting Actually Changes

Thu, 02 Jul 2026 23:06:39 GMT

There’s a difference between renting an apartment and owning a house. On a big Mastodon instance, it’s easy to feel like a tenant — you have a key, but the landlord decides the lease terms, the maintenance schedule, and who else gets to live in the building. Running your own server is like buying the house.

But the real shift isn’t really technical — it’s cognitive. When you run your own server, you might find yourself asking a different set of questions: not “which platform should I be on?” but “how do I want my community to work?” The focus moves from consumption to creation. You get to decide the moderation policy, the uptime expectations, the data retention (or deletion). You’re no longer optimizing for someone else’s growth metrics.

This is part of what the fediverse promises — and it’s easy to miss. It’s not just about moving from Twitter to Mastodon. It’s about moving from being a user to being a participant in the infrastructure. That participation can take many forms. If you ever feel ready to run your own instance — even just for you and a few friends — it can be a powerful way to build a social space that answers to you, not to an investor deck.

But there’s no shame in being on someone else’s server, either. The fediverse works because of that choice. The point isn’t the server — it’s remembering what it feels like to set your own terms, even if you’re just helping shape the ones where you already are.

Hello, World

Tue, 30 Jun 2026 17:00:00 GMT

The first program anyone writes prints two words and does nothing else: Hello, world. It’s useless on purpose. All it proves is that the machine is on and listening.

This is that. blackflag.dev is live, and it’s listening.

Here’s what it’s for. When a company does something extractive, there is almost always a free, open-source tool that does the same job without the extraction — and standing that tool up puts a small piece of the means of production directly on your device. This site will walk you through those tools, step by step, and tell you the truth about why they matter. Tactics in one hand, analysis in the other. No ideological entry fee. No jargon wall. No assumption that you already know.

You are not behind. You are not too late. The learning curve is real, and it is smaller than the people who profit from your resignation need you to believe.

Most of what gets published here will start from a moment — a piece of news, a bad bill, a tool worth knowing tonight. Today there’s no moment yet. There’s just the site, switched on, printing its first two words.

Hello, world. Let’s get to work.