Lots of Small Refinements Today (4/18/2026) Nothing dramatic today. Just a series of small refinements across the product site. Tightened wording. Adjusted layout. Removed a few points of confusion. Individually, none of it feels significant. But taken together, it changes how the whole thing reads. Continuum is becoming clearer — not because of one big idea, but because of many small corrections. Less friction. Less explanation needed. More obvious what it is (and what it isn’t). This kind of work is easy to dismiss. But it’s also the work that makes everything else possible. #Continuum #BuildingInPublic #LocalFirst #SelfCustody #IndieDev #ProductDevelopment

**Self-Custody Is Not Selfish** There’s a quiet assumption that keeps coming up whenever I talk about self-custody, sovereignty, or owning your identity and your work. Or at least, I get the impression people are thinking something along these lines—even if they don’t say it directly. It sounds something like this: > “Isn’t that… a bit selfish?” As if choosing to hold your own keys, manage your own identity, and take responsibility for your digital life is somehow a withdrawal from others. But it’s actually the opposite. Self-custody is not about isolation. It’s about responsibility. When you rely entirely on platforms to hold your identity, your work, and your relationships, you’re not becoming more connected—you’re becoming more dependent. And that dependency doesn’t just affect you. It affects everyone you interact with. If your account disappears, your writing disappears. If your access is revoked, your voice is gone. If the platform changes, your relationships are reshaped without your consent. That instability ripples outward. Self-custody, on the other hand, creates something much more durable. When you own your identity: * your words persist * your relationships are portable * your presence is not subject to permission That doesn’t isolate you—it makes you a more reliable participant in a shared network. Sovereignty is not about cutting yourself off. It’s about showing up with something real that cannot be taken away. It means: * you can give without fear of losing everything * you can build without asking permission * you can connect without being mediated or reshaped That’s not selfish. That’s foundational. In fact, dependence on centralized systems often creates the opposite of generosity: * fear of loss * pressure to conform * incentives to perform instead of create Self-custody removes those pressures. It restores a kind of quiet confidence: > What I have is mine to steward—and therefore mine to share. That’s the key distinction. Selfishness hoards. Sovereignty **stewards**. One is rooted in fear. The other is rooted in responsibility. And in a world where so much is fragile, rented, and reversible… There is something deeply *relational* about being someone who actually owns what they bring to the table. #selfcustody #sovereignty #continuum #nostr #ownership #digitalidentity #localfirst

Note 3 — Not Writing for Platforms (4/18/2026) One thing I’m becoming more convinced of: You can’t let other people — or platforms — dictate what you produce. If you’re watching engagement, waiting for feedback, or shaping your work around what “performs”… you’ve already given up control. That’s not authorship. That’s reaction. Publishing should not depend on: an algorithm a feed validation from others It should come from clarity. Write it. Sign it. Publish it. Whether it gets engagement or not is secondary. That’s part of why I built Continuum in the first place. Not to chase attention — but to remove dependence on it. #writing #sovereignty #nostr #continuum #independentcreator

Note 2 — Focused Versions of Continuum (4/18/2026) I’ve been thinking about something interesting: What if Continuum wasn’t one thing… but a set of focused tools? Instead of a full system, imagine: a version just for DMs a version just for short notes a version just for long-form writing a version just for identity + signing Each one simple. Clear. Purpose-built. Most software tries to do everything. Continuum might actually get stronger by doing less — but doing it extremely well in specific contexts. Not sure where this goes yet, but it feels like the right direction to explore. #continuum #productthinking #minimalism #nostr #softwaredesign

Note 1 — This Week’s Releases (4/18/2026) A solid week of progress on Continuum. v1.6.7.4 and v1.6.7.5 weren’t flashy, but they mattered. Identity editing is now real: add an nsec to an existing identity validate key pairs edit timezone auto-detect local timezone on creation That alone removes a lot of friction. But the bigger shift is workspace control: export workspace (full backup zip) import workspace (continuum-backup.zip) clear workspace (reset everything cleanly) You can now move your entire environment between machines and actually trust that it will come back intact. Also tightened up the Mac install flow: proper DMG with Applications shortcut simpler downloads page (less confusion, fewer steps) Nothing here is hype. Just making the system more complete and more usable. Next up: relay list editing per identity. #continuum #buildinpublic #nostr #sovereignty #localfirst

Excellent !! Thanks for writing this!!

First test sending a note from windows app continuum download (v1.6.7.4)

This was a great article and I apply the very principles you bring out in my work with Continuum.

To author is to create. To authorize is to grant authorship rights. To publish is to make the creation public. #Continuum #Authorship #Publishing #LocalFirst #DigitalSovereignty

Another note - 4/11/2026 **PUBLIC** and **PUBLISH** are also closey related. The act of **AUTHORING** is creation. The act of **PUBLISHING** is to make that creation **PUBLIC**. This is another distinction that many systems collapse into a single gesture. In Continuum, the stages are explicit: - **author** → create - **authorize** → sign - **publish** → make public Creation, authority, and distribution are distinct acts. That distinction is foundational. #Continuum #Authorship #Publishing #LocalFirst #DigitalSovereignty

Note - Saturday (early) April 11, 2026 -- **AUTHOR**, **AUTHORITY**, and **AUTHORIZED** all come from **AUTHOR**. I just realized that **AUTHOR**, **AUTHORITY**, and **AUTHORIZED** are actually related in spirit, even though in modern English they have taken on distinct meanings. That connection suddenly clarified something foundational in Continuum’s model: Only an **AUTHORized NPUB** can **AUTHOR**. A public identity (**NPUB**) may be present locally in read-only form (**no NSEC**), but it cannot sign, or originate content unless it carries signing authority. To authorize means, quite literally, to grant the right to perform a specific action. In Continuum, that means the right to author specific content or perform specific actions on behalf of that identity. This feels like more than wordplay. It expresses the architecture itself: **authorship requires authority.** #Continuum #LocalFirst #Authorship #Authority #Nostr #DigitalSovereignty

4/10/2026 Noe 3 Getting more than 1,000 sats for something I created felt really good. Not even about the amount as much as the signal. After all the hours in Continuum and writing the book, it felt good to know something I made connected enough for someone to support it directly. #Bitcoin #Sats #CreatorEconomy #Continuum

4/10/2026 Note 2 Today someone bought *Building Continuum: Local Authority in a Networked World* in sats. That meant a lot to me. I was also introduced to the wormhole.app (secure encrypted file sharing app) in the process, which was a nice unexpected bonus. A good signal on a day that already felt meaningful. #Bitcoin #Sats #BuildingContinuum #BuilderJournal

4/10/2026 - Continuum now supports all 4 major ways I wanted people to run it: - local source (great for Linux / dev environments) - Docker - native Windows - native macOS This feels like a real milestone because it removes a lot of install friction and makes the ideas in *Building Continuum* much more tangible. #Continuum #CrossPlatform #LocalFirst #BuildInPublic

Note 3 - 4/9/2026 ** Why the obsession with local-first? ** Because ownership matters. Your writing should not live only in someone else’s cloud. Your identity should not depend on a password reset flow. Your work should remain yours even when offline. Local-first is not just a technical choice. It is a statement about authority. #LocalFirst #DigitalSovereignty

Note 2 - 4/9/2026 ** Continuum is now easier than ever to get started with. ** For many users, the biggest barrier was setup friction. That is why the native Mac and Windows builds mattered so much. Download. Open. Begin writing. Local-first should not mean difficult. It should mean freedom without friction. #Continuum #Sovereignty

Note 1 - 4/9/2026 ** v1.6.7 is now out. ** Native Mac build. Native Windows build. Docker build. All now running from a unified code base. This has been a major milestone for Continuum. The goal remains the same: make local-first authorship and identity easier to use across platforms. More to come. #Continuum #LocalFirst #Release

Very well said!

4/8/2025 Quiet but important milestone today. I left Continuum running overnight in Docker with the laptop closed. This morning I reopened, refreshed the browser, switched identities, refreshed relays, sent a test note, and scheduled another test note. Everything went through normally. No freeze. This is the kind of invisible progress that builds real trust in the product. #buildinpublic #continuum #localfirst

Verify, don’t trust. We say that about Bitcoin. But it applies in many areas of life — and especially in places like Nostr. Words are cheap. Intentions are cheap. A like doesn’t mean much. People will say things in the moment: “Great article.” “Well said.” “I’ll check out the download.” But unless those words are followed by action, they remain only sentiment. This is the reality. Verify, don’t trust. #Bitcoin #Nostr #Sovereignty