Akamaister

Andrew G. Stanton (Akamaister)
Builder · Writer · Bitcoin-aligned systems

Founder & Fractional CTO.
I build durable software and publishing systems rooted in conviction, sovereignty, and long-term thinking.

Following Jesus.
Building with proof of work, not proof of hype.
Still building.

Primary work
MyContinuum — sovereign publishing & identity
https://mycontinuum.xyz

Archive (RSS)
https://nostr.mycontinuum.xyz/e/rss/npub19wvckp8z58lxs4djuz43pwujka6tthaq77yjd3axttsgppnj0ersgdguvd/kind/30023.xml

Nostr
npub19wvckp8z58lxs4djuz43pwujka6tthaq77yjd3axttsgppnj0ersgdguvd

Verify Tool:

https://nostr.mycontinuum.xyz/e/verify.html

PGP fingerprint
B480 CC98 7E0B AA6D 5962 EBAA BF2E 7F14 860D 3FB0
Full key:
https://andrewgstanton.com/pgp

Last generated: 2026-05-24 12:21 PM PST

Public Key

npub19wvckp8z58lxs4djuz43pwujka6tthaq77yjd3axttsgppnj0ersgdguvd

NIP-05 Address

andrewgstanton@primal.net

Profile Code

nprofile1qqszhxvtqn32rlng2kewp2cshwftwa94m7s00zfxc7n94cyqsee8u3cpz3mhxue69uhhyetvv9ujuerpd46hxtnfduqs6amnwvaz7tmwdaejumr0dsva9su0

Publishing to

relay.damus.io

nos.lol

Author Public Key

npub19wvckp8z58lxs4djuz43pwujka6tthaq77yjd3axttsgppnj0ersgdguvd

Show more details

Last Notes

2026-05-20 22:18:09 UTC

- reply

Why does this keep happening ?

2026-05-19 03:52:30 UTC

5/18/2026 - One thing I appreciate more over time:
Continuum is becoming less dependent on “ideal developer conditions.”
Not everything assumes:
- Docker
- cloud infrastructure
- external APIs
- perfect runtime environments
- always-online workflows
The system increasingly degrades gracefully instead of simply disabling functionality.
That architectural direction matters more to me than adding flashy features.
#Continuum #SoftwareArchitecture #LocalFirst #Engineering

2026-05-19 03:45:26 UTC

5/18/2026 - Continuum has supported native desktop builds for a while now.
Back in v1.6.7 (April 9, 2026), the project reached an important packaging milestone:
- signed + notarized native Mac builds
- updated native Windows builds
- unified Docker alignment
- packaging improvements
- build script cleanup
- Windows launcher/runtime fixes
But one lingering inconsistency remained:
PDF export support was still effectively tied to Docker/WeasyPrint environments.
Today’s work closes much of that gap.
PDF exports are now supported consistently across all build types, including the native desktop builds I now actively use myself for writing and publishing.
That progression matters because the goal was never merely:
> “ship a packaged app.”
The goal is a durable local-first authoring environment that behaves coherently across environments.
#Continuum #NativeApps #PDF #LocalFirst #DigitalSovereignty

2026-05-11 22:40:38 UTC

- reply

Yes !!
#nevent1q…lpp2

2026-05-11 19:46:54 UTC

- reply

Yes !!
#nevent1q…d4de

2026-05-11 18:33:06 UTC

5/11/2026 AI and automation are pushing the cost of digital production toward zero.
- Infinite content.
- Infinite code.
- Infinite media.
- Infinite synthetic noise.
Ironically, that makes a few things more valuable:
* trust
* authorship
* signatures
* provenance
* identity
* local ownership
That is increasingly where Continuum is focused.
Not just publishing content.
But managing authority itself.

2026-05-09 23:38:40 UTC

- reply

Those adoption numbers are probably bogus 😄
Continuum is still very early. I appreciate the encouragement, but there’s no public analytics dashboard or “on-chain” metric source tracking usage right now.
Most of the work at this stage is still focused on architecture, identity flows, local-first publishing, signing, and artifact verification.

2026-05-09 04:24:11 UTC

5/8/2025 - Another interesting direction is the idea of a “composite signer.”
Right now, identities are mostly treated independently:
- one Nostr identity
- one PGP identity
- one Bitcoin identity
- one SSH identity
But increasingly I’m thinking about a higher-level abstraction:
a composite signing authority composed of multiple underlying identities.
For example:
“Andrew Stanton”
could internally contain:
- several Nostr identities
- multiple PGP fingerprints
- Bitcoin signing identities
- SSH identities
all grouped into a single composite signer profile.
Then when signing an artifact, Continuum could:
- apply all configured proofs automatically
- generate a unified manifest
- preserve identity relationships
- support optional proof policies
This becomes especially interesting because different ecosystems trust different proof systems.
Some people may only care about:
- PGP
- Bitcoin
- SSH
- Nostr
The composite signer allows all of those identities to travel together coherently.
And importantly:
the abstraction shifts away from “accounts”
toward “cryptographic authority groups.”
That feels much closer to how identity actually works in the real world.
A person, organization, or project rarely has:
- one key
- one identity
- one trust system
Instead they operate through overlapping cryptographic authorities.
The composite signer starts modeling that reality much more directly.
#Continuum #Nostr #Bitcoin #OpenSource #LocalFirst #PGP #SSH #Cryptography #Sovereignty

2026-05-09 04:22:43 UTC

5/8/2026 - One interesting possibility now that the “Verify Signed Artifact Bundle” flow is working:
the bundle itself can continue evolving as it moves between people.
For example:
I could generate a signed artifact bundle containing:
- the artifact
- manifests
- Nostr proofs
- PGP proofs
- Bitcoin attestations
- SSH proofs
Then send that zip bundle to another Continuum user.
That user could:
- verify all existing proofs locally
- inspect the manifests/signers
- add their own attestations
- generate an updated bundle
- pass it forward again
At that point, the bundle starts becoming something more collaborative.
Not merely:
“who originally authored this?”
But also:
“who independently verified or endorsed this artifact?”
That becomes especially powerful for same-domain attestations.
For example:
- 3 or 4 independent Nostr users attesting
- multiple Bitcoin identities signing the same artifact
- several PGP identities verifying the same release
- multiple SSH authorities approving the same package
The important part is that these attestations remain:
- portable
- local-first
- independently verifiable
- append-only
without requiring:
- a blockchain consensus layer
- a hosted verification service
- a centralized signing authority
The artifact bundle itself becomes the evolving container of trust relationships.
That feels like a very different model from most modern platforms.
#Continuum #Nostr #Bitcoin #OpenSource #LocalFirst #PGP #SSH #Cryptography #Sovereignty

2026-05-08 14:46:27 UTC

- reply

Or you can also send some to me and spread the love !
:)

2026-05-08 14:09:56 UTC

- reply

Got to get some to go your way!

2026-05-08 05:07:12 UTC

- reply

Love it yes!
#nevent1q…fwlf

2026-05-08 04:45:44 UTC

5/7/2026 - One of the most interesting parts of today:
I’m not creating “special Nostr events” for artifact attestations.
I’m simply using the Nostr private key to sign a canonical message about an external artifact.
That distinction matters.
The proof file is completely separate from the artifact itself:
* tax_return.pdf
* tax_return.pdf.nostr-proof.json
The JSON contains:
* artifact SHA256
* npub
* pubkey
* signed message
* Schnorr signature
* timestamp
Very similar conceptually to:
* PGP detached signatures
* Bitcoin message attestations
At some point you realize:
PGP, Bitcoin, Nostr, SSH…
they are all variations of:
challenge → sign → verify
#Continuum #Nostr #Bitcoin #SSH #PGP #DigitalSovereignty

2026-05-08 02:03:39 UTC

- reply

Only 5 slots left ? Might want to clarify anyone can buy bitcoin and start stacking it

2026-05-08 02:01:00 UTC

- reply

This is cool!
Yeah more like this
Prob still are figuring out what u actually want to “be” here

2026-05-03 21:56:25 UTC

- reply

Hey

2026-04-30 00:24:55 UTC

- reply

I woukd have loved to stay have a flight boarding at 7:10 pm tonight
I hope i get to meet him in person someday… fascinating guy!

2026-04-28 17:27:39 UTC

- reply

At the state Now!

2026-04-27 17:41:25 UTC

- reply

Amen.
“Rejoice always, pray without ceasing, in everything give thanks; for this is the will of God in Christ Jesus for you.
Do not quench the Spirit. Do not despise prophecies. Test all things; hold fast what is good. Abstain from every form of evil.ʻ
1 Thessalonians 516-22 (NKJV)
#nevent1q…7ahc

2026-04-26 01:37:37 UTC

- reply

Yes!! Amen!!
Bitcoiners need Jesus
And Christians should adopt Bitcoin
#nevent1q…mxpy

2026-04-25 20:47:25 UTC

4/25/2026 - I’m starting to see that stopping work doesn’t automatically lead to rest.
I can step away from everything and still feel like I’m carrying it.
So maybe the real question isn’t whether I’m working or not.
It’s whether I’ve actually let go of it, even for a little while.
#Sabbath #Rest #Work #Faith

2026-04-25 00:27:12 UTC

4/24/2026 - I Object
I object—not loudly, not emotionally, but clearly.
I object to systems that assume control over what I create, where I publish, and how I’m allowed to exist online.
Authorship is not a feature.
It’s a right.
If I can’t sign it, I don’t own it.
If I can’t move it, it’s not mine.
#IObject #DigitalSovereignty #Nostr #Continuum

2026-04-21 19:34:42 UTC

4/21/2026
A circular economy is not built by apps.
It’s built when:
you pay someone in sats
they pay someone else in sats
and it doesn’t go back to fiat in between
That’s when something new starts to form.
#Bitcoin #Lightning #CircularEconomy

2026-04-19 06:41:12 UTC

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

2026-04-19 01:34:32 UTC

**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

2026-04-09 02:02:44 UTC

- reply

AMÉN
#nevent1q…k9d2

2026-04-02 06:05:53 UTC

Big milestone today for Continuum.
After a long build session, both the Mac app (.app ) and Windows build (.exe) are now live.
This is a major step toward making local-first publishing and sovereign identity accessible without Docker, WSL, or complex setup.
Would love feedback from anyone willing to test the native builds.
Downloads: mycontinuum.xyz/downloads
Building in public. One step closer.
#nostr #buildinpublic #localfirst #sovereignty #bitcoin

2026-03-30 04:59:32 UTC

- reply

I can relate very well !!
Refrain from building new features “just because you can”
Tie them to your core architecture if you can
Writing about you are building (like what you are doing with this post I think helps)
And don’t give up !!

2026-03-29 18:07:04 UTC

- reply

Reposted

2026-03-29 17:56:11 UTC

- reply

AMÉN

2026-03-26 19:52:27 UTC

- reply

Yes I have they are all solved in Continuum actually

2026-03-26 18:42:54 UTC

You can see it in what gets amplified.
Serious ideas?
Often ignored.
Provocative or emotionally charged content?
That spreads fast.
---
That’s not unique to Nostr.
But it does shape the culture.
---
And it’s exactly why writing — real, structured, thoughtful writing — struggles in feed-based systems.
---
Feeds reward attention.
Writing requires intention.
Those are not the same thing.
---
If you’ve tried to do serious writing here…
you’ve felt that gap.
It gets old. Fast.
---
So you have a few choices:
1. Go back to Substack, Medium, etc.
2. Accept the limitations and work around them
3. Build something better
---
I chose option 3.
That’s Continuum.
#nostr #bitcoin #writing #publishing #localfirst #sovereignty #continuum

2026-03-26 18:22:35 UTC

- reply

Yes — and I think you’re pointing at something deeper.
Decentralizing the protocol doesn’t fix the experience.
If the interface and incentives stay the same,
you just recreate the same patterns on a new substrate.
---
You see it already:
Most clients optimize for:
- feeds
- engagement
- short-form velocity
So even on Nostr, writing gets compressed into that shape.
---
Concrete examples?
Try doing anything serious:
- drafting something over multiple sessions
- maintaining consistent structure across clients
- trusting it will render the same everywhere
- coming back to it later and it still being readable
That’s where it breaks down.
---
So I agree with you.
It’s not a protocol problem.
It’s an experience + incentive problem.
---
And that’s exactly the gap I’m trying to address with Continuum:
separating authorship from the client layer entirely.
#nevent1q…jxu5

2026-03-26 18:14:25 UTC

- reply

I didn’t expect much reaction to this.
That’s actually part of the problem.
If you’re building on Nostr, or writing seriously on it, you *know* this gap exists.
You’ve felt it:
- no drafting
- no real structure
- no control over presentation
And yet… we don’t really talk about it.
Why?
Because it’s uncomfortable.
It forces us to admit:
the current client layer is not enough.
---
I’m not saying Nostr is broken.
I’m saying the writing experience is.
And pretending otherwise doesn’t help anyone building real things.
---
Curious:
What are you using today for long-form writing on Nostr?
And be honest — does it actually work?

2026-03-26 18:10:08 UTC

BUILDING CONTINUUM
Let’s be honest.
Most Nostr clients **suck for writing.**
---
They’re great for:
• short posts
• replies
• scrolling
They’re basically a better version of X.
---
But for long-form?
They break down fast.
---
No real structure.
Inconsistent formatting.
No control over how your work is presented.
No guarantee it will even be readable later.
No drafting. No workflow.
---
That’s not publishing.
That’s just posting… with extra steps.
---
Nostr (the protocol) is powerful.
But the client layer is optimized for feeds — not for authors.
---
So if you’re trying to write seriously on Nostr today…
you feel it.
Like I do.
And it gets old fast.
---
That gap is why I built Continuum.
---
Local-first.
Your identity.
Your content.
Your authority.
---
Not dependent on:
• a client UI
• a relay
• or a platform staying online
---
And yes — this will probably get ignored.
Which proves the point.
---
Building Continuum is now live
ebook + paperback
https://is.gd/rq4omr
---
#nostr #bitcoin #writing #publishing #localfirst #sovereignty #continuum

2026-03-26 17:57:37 UTC

Nostr clients are being treated like they can handle everything.
They can’t.
They’re great for social.
But for real writing, they’re a downgrade from Substack.
Writing needs a real authoring layer.
Continuum is my solution—
local-first, structured, and independent of any client.
#nostr #writing #blogging #publishing #substack

2026-03-26 17:47:37 UTC

Decentralizing the protocol doesn’t automatically change the culture.
If the interfaces, incentives, and behaviors stay the same,
you get the same patterns — just on a different rail.
More freedom at the base layer doesn’t guarantee more depth at the social layer.
That’s not a criticism of the protocol.
It’s a reminder that culture doesn’t upgrade automatically.
Changing the foundation matters.
But it doesn’t change people overnight.
#DigitalSovereignty #LocalFirst #FreedomTech #Nostr

2026-03-26 04:07:06 UTC

- reply

Yes

2026-03-25 07:31:29 UTC

Many Keys, Many Identities
You don’t have an identity.
You have an account.
And that account can be:
- suspended
- reset
- deleted
- or quietly controlled
at any time.
---
The problem
Most systems assume:
one user → one account → controlled by a platform
That’s why:
- you lose access
- your content disappears
- your reputation doesn’t transfer
- your login becomes your leash
Even if money becomes sovereign…
your identity often isn’t.
---
The shift
Bitcoin showed:
You don’t have one wallet.
You have many keys.
Ownership isn’t granted.
It’s proven.
---
Nostr extends this:
You don’t have one identity.
You can have many.
Each identity can represent:
- a person
- a project
- a role
- a context
Authorship isn’t assigned.
It’s signed.
---
The insight
None of these are inherently linked.
Your Bitcoin addresses don’t know your identities.
Your identities don’t know your Bitcoin addresses.
Only you do.
---
So what?
This solves real problems:
- No lock-in → your identity isn’t owned (only managed by you)
- No single failure point → one key ≠ everything
- Clear separation → personal, business, projects
- Portability → your identity moves with you
- Selective disclosure → you decide what connects
---
Most systems collapse everything:
identity = account = wallet = user
A sovereign system separates them.
identity
authorship
ownership
---
I don’t have an identity or an account;
I manage identities and keys
(Note: I discovered this while brainstorming with an AI
My ideas are my own though
#Sovereignty #DigitalSovereignty #SelfSovereignIdentity #Bitcoin #Nostr #LocalFirst

2026-03-25 00:57:44 UTC

I'm writing this again without any assistance from an AI.
These words are entirely my own.
Someone recently shared that some of the ideas expressed to him were clearly my own but
not "in my voice"
That's excellent feedback and I take it to heart.
I use AI a lot.
It helps me form my thoughts and create connections that I otherwise might miss.
But I don't want ever want it to dominate my writing.
This is still something I am working through as I continue to build Continuum and hone my writing
and my thoughts.
- Andy S.

2026-03-25 00:47:19 UTC

- reply

And just to be clear I am not defending his record nor am I a stoic philosophically

2026-03-25 00:44:01 UTC

Context matters.
Marcus Aurelius was no saint.
Christians suffered under his rule.
He also took theriac, prescribed by Galen — standard medicine at the time, containing small amounts of opium (along with many other compounds).
History doesn’t give us perfect men.
That is quite different than asserting he “consumed opium daily” without context.
His words still carry merit and reflect wisdom, restraint, and humility.

2026-03-24 23:59:44 UTC

- reply

-- FRAGILITY --
https://2026.mycontinuum.xyz/archive/pro/nostr/npub19wvckp8z58lxs4djuz43pwujka6tthaq77yjd3axttsgppnj0ersgdguvd/images/2026-03-24-substack-down-oops.png
Platforms like Substack feel permanent…
until they don’t.
This screenshot from earlier says everything.
It was a short outage.
It happens.
But if your work only exists there…
everything disappears behind a status page.
No posts.
No audience.
No access.
Just a message:
*“We are working to restore service.”*
This is the illusion.
Access is not ownership.
Availability is not authority.
(Substack is a mirror for me — not the source.)
This is why I built Continuum.
A local-first system
where identity, content, and authorship
do not depend on a platform being online.
I explore this more deeply in my book
*Building Continuum: Local Authority in a Networked World*.
Because this isn’t about one outage.
It’s about a system
that was never built to give you control in the first place.
I didn’t just describe the problem.
I built the solution.
---
#localfirst #ownership #continuum #writing #sovereignty

2026-03-24 22:27:02 UTC

- reply

What about Continuum) ?
Here is the client in the raw data for a recent event I posted FROM my localhost instance of Continuum
the client tag is : Continuum-Pro-localhost
But this reply will be ignored.
----
{"id":"da10daccd66c1f3ebd01c44758dab3be7fd75e51ace6102b540e57ffb4c4616c","sig":"af23d0e646baf335ce41aa605a547ba6bb64fa4bf7eaccde3ea5252caab6e205a5616e52a68121a5090e3749c4867be7216d4f55dd29518b0567dea6e88eb132","kind":1,"tags":[["d","note-1774383330"],["published_at","1774383330"],["client","Continuum-Pro-localhost"]],"pubkey":"2b998b04e2a1fe6855b2e0ab10bb92b774b5dfa0f78926c7a65ae08086727e47","content":"Note 5 — Interface — 3/24/2026\n\nMost of what we see is the interface.\n\nFeeds. Buttons. Profiles.\n\nIt feels like that’s the system.\n\nBut it isn’t.\n\nIt’s just what we’re allowed to see.\n\nI explore this further in my book *Building Continuum* (Chapter 1 - Why I Started)\n\n“The client was just a window.”","created_at":1774383330}

2026-03-24 22:23:32 UTC

- reply

Exactly why I built Continuum

2026-03-24 22:16:59 UTC

- reply

They did that sort of thing a lot some emperors married their sisters.
No restraint in sone cases

2026-03-24 22:08:23 UTC

- reply

Funny if it’s true

2026-03-24 20:15:30 UTC

Note 5 — Interface — 3/24/2026
Most of what we see is the interface.
Feeds. Buttons. Profiles.
It feels like that’s the system.
But it isn’t.
It’s just what we’re allowed to see.
I explore this further in my book *Building Continuum* (Chapter 1 - Why I Started)
“The client was just a window.”

2026-03-24 20:13:42 UTC

Note 4 — Systems — 3/24/2026
Most people think they’re using a platform.
Posting. Sharing. Engaging.
But they’re inside something much larger.
A system they don’t control.
I explore this further in my book *Building Continuum* (Chapter 1 - Why I Started)
“...participation in someone else’s system.”

2026-03-24 20:11:03 UTC

Note 3 — Ownership — 3/24/2026
Everything is accessible.
Always on. Always synced. Always available.
But access is not ownership.
And most systems are built on access.
I explore this further in my book *Building Continuum* (Chapter 1 - Why I Started)
“If I cannot run something offline, do I really own it?”

2026-03-24 20:08:44 UTC

- reply

Note 1 — Signing — 3/24/2026
Posting is easy.
Familiar. Fast. Disposable.
But something changes when what you publish is actually yours.
Not just written — but signed.
I explore this further in my book *Building Continuum* (Chapter 1 - Why I Started)
“I wasn’t posting into an account. I was signing an event.”

2026-03-24 20:08:00 UTC

Note 2 — Indifference — 3/24/2026
You publish something meaningful.
Something you’ve thought about.
Something you’ve worked through.
And then… nothing.
No reaction. No response.
Indifference is part of the process.
I explore this further in my book *Building Continuum* (Chapter 1 - Why I Started)
“Publishing exposes you to indifference.”

2026-03-23 17:20:11 UTC

- reply

Could not agree more
Been building a local first tool called Continuum.
https://mycontinuum.xyz
Also just published my first book !
https://a.co/d/0es8YXH9

2026-03-23 16:51:25 UTC

- reply

This us wonderful
Will check it out!
Also just published my first book
https://a.co/d/02X7JLbQ

2026-03-23 15:00:59 UTC

- reply

Simple definitely not easy

2026-03-23 05:43:45 UTC

Building - 3/22/2026
Building is how ideas are tested.
Not discussed. Not imagined.
Tested.
This note was CREATED, SIGNED and PUBLISHED Local-First not through any client
#Continuum #LocalFirst #Ownership #DigitalSovereignty

2026-03-23 05:42:19 UTC

Stewardship - 3/22/2026
What you build reflects what you believe
is worth your life.
#Continuum #LocalFirst #Ownership #DigitalSovereignty

2026-03-23 05:41:52 UTC

Discipline - 3/22/2026
Consistency is not intensity.
It is direction, held over time.
#Continuum #LocalFirst #Ownership #DigitalSovereignty

2026-03-23 05:41:16 UTC

Signal - 3/22/2026
Silence does not mean nothing is happening.
It often means the work is still forming.
#Continuum #LocalFirst #Ownership #DigitalSovereignty

2026-03-23 05:40:54 UTC

Continuation - 3/22/2026
If you only build when it feels good,
you will stop long before it matters.
#Continuum #LocalFirst #Ownership #DigitalSovereignty

2026-03-23 02:49:19 UTC

- reply

Great advice!!

2026-03-23 00:23:56 UTC

- reply

Example: Using Continuum With NO INTERNET (Offline → Later Publish)
This is a real example of writing and signing a Nostr note completely offline — and publishing it later when connectivity returns.
Below are 5 screens showing the full flow.
Screen 1 — Continuum running with no internet
https://2026.mycontinuum.xyz/archive/pro/nostr/npub19wvckp8z58lxs4djuz43pwujka6tthaq77yjd3axttsgppnj0ersgdguvd/images/2026-03-22-demo2-screen1.png
Continuum is running locally with no internet connection.
- no relays
- no network access
- no client connection
Everything still works.
->> Authorship does not require connectivity. <--
Screen 2 — Managing identities (offline)
https://2026.mycontinuum.xyz/archive/pro/nostr/npub19wvckp8z58lxs4djuz43pwujka6tthaq77yjd3axttsgppnj0ersgdguvd/images/2026-03-22-demo2-screen2.png
Identities are still available.
- keys are local
- signing is local
- no external dependency
--> Identity does not require a platform. <--
Screen 3 — Writing and signing a note (offline)
https://2026.mycontinuum.xyz/archive/pro/nostr/npub19wvckp8z58lxs4djuz43pwujka6tthaq77yjd3axttsgppnj0ersgdguvd/images/2026-03-22-demo2-screen3.png
This note is created and signed while offline.
- no relay connection
- no client
- no external signer
The note exists as a signed event locally!!
--> If your current tool requires connectivity to create or sign, that’s a dependency. <--
Screen 4 — Scheduled for later publication
https://2026.mycontinuum.xyz/archive/pro/nostr/npub19wvckp8z58lxs4djuz43pwujka6tthaq77yjd3axttsgppnj0ersgdguvd/images/2026-03-22-demo2-screen4.png
The signed note is queued for publishing.
- stored locally
- ready to send when relays are available
Publishing is a separate step from authorship.
Screen 5 — Internet restored, note published
shown locally in continuum:
https://2026.mycontinuum.xyz/archive/pro/nostr/npub19wvckp8z58lxs4djuz43pwujka6tthaq77yjd3axttsgppnj0ersgdguvd/images/2026-03-22-demo2-screen5-1.png
shown on primal:
https://2026.mycontinuum.xyz/archive/pro/nostr/npub19wvckp8z58lxs4djuz43pwujka6tthaq77yjd3axttsgppnj0ersgdguvd/images/2026-03-22-demo2-screen5-2.png
Once connectivity is restored:
→ the note is published
→ relays receive it
→ clients can display it
The note was already created and signed before the network was involved.
What this example shows
→ write offline
→ sign locally
→ publish later
→ network as distribution only
Key takeaway
Authorship, identity, and signing DO NOT require the internet.
The network is optional for creation — only required for distribution.
This setup requires running Continuum locally.
That’s the tradeoff for independence from connectivity.

2026-03-23 00:20:23 UTC

- reply

Example: Publishing With Multiple Identities in One Flow
This is a real example of creating and publishing notes using multiple identities in a single session — no login/logout, no account switching.
Below are 5 screens showing the flow.
Screen 1 — Continuum dashboard (local)
https://2026.mycontinuum.xyz/archive/pro/nostr/npub19wvckp8z58lxs4djuz43pwujka6tthaq77yjd3axttsgppnj0ersgdguvd/images/2026-03-22-demo3-screen1.png
Continuum is running locally.
Multiple identities are available at the same time.
There is no concept of “logged in user”.
Screen 2 — Select identity: Akamaister
https://2026.mycontinuum.xyz/archive/pro/nostr/npub19wvckp8z58lxs4djuz43pwujka6tthaq77yjd3axttsgppnj0ersgdguvd/images/2026-03-22-demo3-screen2.png
Here I select the identity “Akamaister”.
This determines which key will be used to sign the next note.
Identity selection is explicit.
Screen 3 — Write and publish as Akamaister
drafting and publishing the note:
https://2026.mycontinuum.xyz/archive/pro/nostr/npub19wvckp8z58lxs4djuz43pwujka6tthaq77yjd3axttsgppnj0ersgdguvd/images/2026-03-22-demo3-screen3-1.png
note published -- seen on primal:
https://2026.mycontinuum.xyz/archive/pro/nostr/npub19wvckp8z58lxs4djuz43pwujka6tthaq77yjd3axttsgppnj0ersgdguvd/images/2026-03-22-demo3-screen3-2.png
This note is created and signed using the Akamaister identity.
- signed locally
- published directly
No login. No session. Just key selection.
Screen 4 — Switch identity: Continuum
(continuum is also an npub/keypair I have, this is NOT the same as the platform/application itself)
https://2026.mycontinuum.xyz/archive/pro/nostr/npub19wvckp8z58lxs4djuz43pwujka6tthaq77yjd3axttsgppnj0ersgdguvd/images/2026-03-22-demo3-screen4.png
Now I switch to a different identity: “Continuum”.
No logout required.
No account switching.
Just selecting a different key.
Screen 5 — Write and publish as Continuum
Note drafted, igned, published and shown in primal:
https://2026.mycontinuum.xyz/archive/pro/nostr/npub19wvckp8z58lxs4djuz43pwujka6tthaq77yjd3axttsgppnj0ersgdguvd/images/2026-03-22-demo3-screen5.png
This note is created and signed using the Continuum identity.
Same system. Same flow.
Different identity, fully controlled.
What this example shows
→ multiple identities active at once
→ explicit selection per action
→ no login/logout model
→ no platform controlling identity
Key takeaway
Identity is not a session.
It’s a key you choose to use.
Most systems tie identity to accounts and sessions.
Here, identity is independent and selectable at any time.
This setup requires running Continuum locally.
That’s the tradeoff for full control over identity and publishing.

2026-03-22 23:58:23 UTC

Note Published as Akamaister

2026-03-22 22:57:53 UTC

- reply

Example: Using Continuum on My Local Machine (Local → Network)
This is a real example of publishing a Nostr note using Continuum running locally — no client required.
Below are 5 screens showing the full flow — from writing a note locally to seeing it appear in another Nostr client.
NOTE: On some mobile clients, images may appear at the end — they are labeled to match each step.
Screen 1 — Continuum dashboard (running locally)
https://2026.mycontinuum.xyz/archive/pro/nostr/npub19wvckp8z58lxs4djuz43pwujka6tthaq77yjd3axttsgppnj0ersgdguvd/images/2026-03-22-demo-screen1.png
This is the Continuum dashboard running at localhost.
It shows:
- my notes and articles stored locally
- my active identity
- publishing tools
- NOTHING here is hosted
- NOTHING here is seen through any client or app
- NOTHING depends on a platform
If you're using a client today, your content typically starts there.
--> Here, it starts locally. <--
Screen 2 — Managing identities (npubs)
https://2026.mycontinuum.xyz/archive/pro/nostr/npub19wvckp8z58lxs4djuz43pwujka6tthaq77yjd3axttsgppnj0ersgdguvd/images/2026-03-22-demo-screen2.png
Here I am selecting from multiple identities.
These are Nostr keys, not accounts.
- no email
- no password
- no platform login
Each identity can sign and publish independently.
Most systems assign identity.
--> Here, it’s controlled directly. <--
Screen 3 — Writing a note (local authoring)
https://2026.mycontinuum.xyz/archive/pro/nostr/npub19wvckp8z58lxs4djuz43pwujka6tthaq77yjd3axttsgppnj0ersgdguvd/images/2026-03-22-demo-screen3.png
This is the note being written inside Continuum.
It is created locally:
- not inside a Nostr client
- not through a browser extension
Just direct authorship on my machine.
--> Question: If your current tool disappeared, where would your drafts live? <--
Screen 4 — Note after signing and publishing (local view)
https://2026.mycontinuum.xyz/archive/pro/nostr/npub19wvckp8z58lxs4djuz43pwujka6tthaq77yjd3axttsgppnj0ersgdguvd/images/2026-03-22-demo-screen4.png
After clicking “Sign & Publish”:
- the note is signed with my key
- sent to relays
- stored locally as a signed event
This confirms the note has been created and published.
Screen 5 — Same note visible in Coracle (external client)
https://2026.mycontinuum.xyz/archive/pro/nostr/npub19wvckp8z58lxs4djuz43pwujka6tthaq77yjd3axttsgppnj0ersgdguvd/images/2026-03-22-demo-screen5.png
Here is the exact same note in Coracle.
This shows:
- the note was published to the network
- any client can display it
It was not copied or synced through a service.
The client didn’t create this note.
It only displays it.
What this example shows
→ write locally
→ sign with your key
→ publish directly
→ view in any client
Key takeaway
Continuum is the source of authorship.
Clients are just viewers.
Most tools optimize for convenience.
They also introduce dependencies you don’t notice until they matter.
This setup requires running Continuum locally (Docker, etc.).
That’s the tradeoff for full control and ownership.

2026-03-22 19:52:26 UTC

- reply

This is actually a very good idea

2026-03-22 17:09:42 UTC

- reply

I wrote this a while back just as true now as when I first wrote it
Treat AI tools as part of your development pipeline instead of a magic black box
#nevent1q…mqt2
#naddr1qq…22x6

2026-03-22 16:56:46 UTC

If anyone is curious I asked ChatGPT (“Dr. C”) to describe me
Here us the exact question (prompt) I used:
“Based on everything you know about me and what we have been working on together how would you describe me Dr c?”
It came up with 10 Points the last point was was a summary:
“10. The Cleanest Description
If I had to reduce it:
You are a sovereignty-driven systems builder and writer
who is trying to create durable, identity-first infrastructure
without compromising on first principles—even when it costs you.”

2026-03-22 16:35:58 UTC

I do not ALWAYS use my local host Instance of continuum to post. Mostly but not always
It’s just good to know I have this option.
Beautiful day here in SF
Take care

2026-03-22 16:27:14 UTC

- reply

I actively use AI tools like ChatGPT to build and test Continuum with lots of effort and care the opposite of slop pasta
And I am not using a tool now to “smooth” over what I am saying
Anything worth doing well requires effort and care
Thanks for sharing
#nevent1q…mhyj
#naddr1qq…xznw

2026-03-22 04:43:59 UTC

- reply

Sabbath - 3/21/2026
Sabbath is not inactivity.
It’s refusing to believe that everything depends on you.
#Sabbath #Faith #Bitcoin #Nostr #Continuum #LocalFirst #Sovereignty #Writing #Building #Identity #Clarity #DigitalSovereignty

2026-03-22 04:43:37 UTC

- reply

Building - 3/21/2026
If it cannot continue without you…
it is not yet built to last.
#Sabbath #Faith #Bitcoin #Nostr #Continuum #LocalFirst #Sovereignty #Writing #Building #Identity #Clarity #DigitalSovereignty

2026-03-22 04:43:11 UTC

- reply

Writing - 3/21/2026
Engagement can be manufactured.
Clarity cannot.
#Sabbath #Faith #Bitcoin #Nostr #Continuum #LocalFirst #Sovereignty #Writing #Building #Identity #Clarity #DigitalSovereignty

2026-03-22 04:42:32 UTC

- reply

Continuum - 3/21/2026
Local-first isn’t just about ownership.
It’s about the ability to step away.
#Sabbath #Faith #Bitcoin #Nostr #Continuum #LocalFirst #Sovereignty #Writing #Building #Identity #Clarity #DigitalSovereignty

2026-03-22 04:42:11 UTC

- reply

Identity - 3/21/2026
The more you perform online…
the easier it is to lose what is real.
#Sabbath #Faith #Bitcoin #Nostr #Continuum #LocalFirst #Sovereignty #Writing #Building #Identity #Clarity #DigitalSovereignty

2026-03-21 18:09:17 UTC

- reply

Thoughts - 3/21/2026
Some hard truths -
- Many on Nostr talk about freedom and sovereignty. Few actually embrace it fully.
- Prominent Bitcoiners and Nostriches tend to get more likes and zaps for comments, posts or articles promoting sovereign concepts, freedom or self custody. Those that are less well known that promote the same things will be invisible to the network. This feels unfair at times, but this is just how network effects and social loops work in ANY social network or system, even if it is decentralized and discovery is not manipulated by algorithms.
- I have published a lot about sovereignty and local authority a huge amount actually (600+ notes, 700+ long form articles. Recently published a book ("Building Continuum") (now on Amazon) Yet almost no traction (relative to others that are more prominent), maybe a few zaps here and there. Is my work too intense? Is Continuum still too hard to understand ? I honestly don't know. I do know that short, meme-inspired notes tend to get liked and zapped more.
I guess I need to give it time. I shouldn't care. But I do. I wish I didn't.
Yet, I am free. truly free. I can publish this through a local-first system I built called Continuum.
This note is not posted from ANY Nostr client. I didn't need to use any 3rd party tool for sharing my private key to connect to a client to post this.
I am thankful for that.
Whether anyone responds to this or not it's OK.
I'm not writing to impress.
Just speaking what's on my mind.
Now I'll get back to building and writing.
Note: I wrote this note without any assistance from any AI tool to "smooth" over my wording.
Have a great day everyone. Truly! Enjoy the sunshine and smell the grass! I do love you all. Let me know once in a while that my posts resonate with you.
Zaps of course are always appreciated.
Take care and God bless

2026-03-21 18:03:54 UTC

2026-03-21 15:53:59 UTC

- reply

Nice ! I sometimes post German versions of my long form posts on Nostr.
Looking forward to the Italian and English newsletters

2026-03-21 15:00:30 UTC

- reply

I added my email to the newsletter looks like it’s in Italian?
Anyway I would love to see a subscription equivalent using a public key (instead of an email )
What do you think ?
I was brainstorming how I could do this with my partner

2026-03-21 14:56:37 UTC

- reply

Powerful piece

2026-03-21 05:50:15 UTC

- reply

Spot on!!
#nevent1q…q82d

2026-03-20 17:34:46 UTC

I published my first book: *Building Continuum*
It explores a question I couldn’t shake:
What would authorship look like if it were truly local-first and identity-first?
Not tied to platforms
Not dependent on external signers
Not fragile
Over the past 10 months, I’ve been building Continuum alongside this — a system where:
- content is authored and stored locally
- identity is directly managed (no third-party custody)
- publishing is optional, repeatable, and decoupled
This book is part reflection, part architecture, part invitation.
Curious what others think — especially those working on:
- long-form content on Nostr
- multi-identity workflows
- durable publishing systems
Link:
https://is.gd/SVQpjQ

2026-03-19 15:06:10 UTC

- reply

Really interesting premise — especially the idea that virtual worlds absorb attention while power consolidates in the physical one.
Feels like a theme we’re only beginning to explore.
I’ve been thinking a lot about the infrastructure layer beneath that:
→ what happens to authorship
→ identity
→ and long-form work
if the interfaces people rely on disappear or shift?
Curious how deeply the book goes into that tension.
Congrats on the release.

2026-03-18 17:34:03 UTC

- reply

Most Nostr clients are solving for speed, UX, and engagement.
That makes sense.
But there’s a layer that still feels underbuilt:
→ durable authorship
→ local-first identity workflows
→ publishing that doesn’t depend on any client being online or maintained
Right now, even in Nostr:
- drafts are fragile
- signing often depends on browser extensions or external tools
- identity is portable, but *workflows* aren’t
- long-form content still feels bolted on
I’ve been working on a local-first system called Continuum that explores a different approach:
- everything authored and stored locally first
- identities managed directly (no dependency on third-party signers)
- publish / republish as a separate concern
- deterministic archives (your work exists even if relays or clients disappear)
Not trying to replace clients like Primal.
More like:
→ what if clients are the *interface layer*
→ and authorship + identity live somewhere more stable underneath?
Curious how others are thinking about this.
Especially around:
- draft persistence
- multi-identity workflows
- long-form publishing on Nostr
Feels like there’s still a big opportunity here.
#Nostr #Bitcoin #LocalFirst #SelfSovereignIdentity #ProtocolDesign #OpenSource #IndieDev

2026-03-18 00:45:12 UTC

- reply

I would love to build infrastructure fir native nations

2026-03-18 00:43:04 UTC

- reply

I have written a number of articles on using Bitcoin and Nostr for tribal sovereignty it’s a great idea I even incorporated tribes staking land on mars in my Bitcoin Chronicles series (“New Lakota”)

2026-03-17 23:46:55 UTC

- reply

Publishing is partly how I think

2026-03-17 23:20:36 UTC

Faith That Moves Quietly - 3/17/2026
Patrick didn’t build platforms.
He didn’t optimize for reach.
He just lived what he believed, consistently, over time.
And somehow, that was enough to leave a mark that lasted centuries.
There’s something in that worth remembering.

2026-03-17 23:20:02 UTC

Simple Joy Today - 3/17/2026
No need to overthink today.
A good meal. A bit of green. Maybe a moment outside.
Not everything has to be optimized or turned into output.
Some days are just meant to be lived lightly.

2026-03-17 23:19:17 UTC

A Bit of Irish Blood - 3/17/2026
Somewhere in the mix—Scots-Irish roots.
It’s funny how those threads carry forward.
Even if distant, there’s a sense of connection. Not in a loud or defining way, but just enough to notice.
A small thread in a much larger story.

2026-03-17 23:17:47 UTC

St. Patrick Wasn’t Irish - 3/17/2026
One of the more interesting details—Patrick wasn’t even Irish.
He was taken there as a slave, escaped, and then chose to go back.
Not out of obligation, but conviction.
That kind of return… that’s rare.
It reframes the whole idea of “mission” from something abstract into something deeply personal.

2026-03-17 23:17:01 UTC

A Quiet Kind of Celebration - 3/17/2026
St. Patrick’s Day always feels a little different than the usual holidays.
It’s not loud (unless we make it that way), and it’s not really about spectacle.
At its root, it’s about a man who walked into a foreign land—not to conquer it, but to serve.
There’s something grounding in that.
Not performance. Not recognition.
Just faithfulness over time.

2026-03-17 15:03:51 UTC

- reply

God is always in charge. He inhabits eternity and wants us all to live with Him there

2026-03-17 07:25:13 UTC

- reply

5. Building in silence is still building - 3/16/2026
No launch. No applause.
But today:
the manuscript moved forward
the pipeline improved
the system got stronger
Not everything valuable is visible.

2026-03-17 07:24:57 UTC

- reply

4. Most tools optimize for convenience, not durability - 3/16/2026
Cloud tools make everything easy — until they don’t.
Durable systems feel heavier upfront:
more setup
more intention
But they don’t disappear under you.

2026-03-17 07:24:39 UTC

- reply

3. Local-first is not a philosophy — it’s a constraint - 3/16/2026
Running out of disk space today wasn’t just annoying.
It’s a reminder:
If you choose local-first, you inherit:
storage limits
file management
operational responsibility
That’s the tradeoff for ownership.

2026-03-17 07:24:03 UTC

- reply

2. Publishing should be a pipeline, not an event - 3/16/2026
Writing a book is one thing.
But building a repeatable pipeline to:
format
export
publish
That’s how you go from one book → many works.

2026-03-17 07:23:26 UTC

- reply

1. Sovereign storage isn’t optional - 3/16/2026
Most people think they have a writing workflow.
What they actually have is:
a dependency chain
a sync service
and a failure point
If your system breaks when Google Drive glitches, it’s not yours.

2026-03-17 07:23:03 UTC

- reply

5. The second book is always more practical. - 3/15/2026
The first book explains why.
The second book starts answering:
how to build
how to operate
how to replicate
That’s where things become useful to others.

2026-03-17 07:22:51 UTC

- reply

4. If you can’t publish it yourself, you don’t control it - 3/15/2026
A manuscript without a publishing path is still dependent.
Real ownership means:
you can produce the file
you can distribute it
you don’t need permission