Screenshot of browser signing activity

Posting here (on iris.to) while using my browser extension sigining from my keys on Continuum (localhost)...
Created a note using a browser (NIP-07) I created that runs in tandem with my local Continuum Instance
Here is a screenshot

Just signed in using my own NIP-07 browser extension (associated w/ Continuum)
Running another test please ignore…
Just signed in using my own NIP-07 extension (connected to my localhost continuum for signing ... very cool
I don't need alby or any other 3rd party
Built the browser extension (with some help but it works very well!
6/3/2026 - Released Continuum v1.6.8.0 today.
A smaller release focused on usability and runtime management:
• Added an application console window
• Reorganized tools and buttons for easier navigation
• Added a shutdown application tool for clean shutdown of native and local builds
A lot of cleanup behind the scenes as well.
#continuum #nostr #buildinpublic #opensource
#Continuum #Nostr #DeveloperTools #LocalFirst #SelfSovereign #ProductUpdate
Just a test …
Great article!
I have written about the same themes you address here in some of my previous articles.
We need to emphasize these themes more!
Thank you for sharing!
This is sending a note after adding/updating my relay lst
On Temptation:
“Do not love the world or the things in the world.
If anyone loves the world, the love of the Father is not in him.
For all that is in the world—the desires of the flesh and the desires of the eyes and pride of life—is not from the Father but is from the world.
And the world is passing away along with its desires, but whoever does the will of God abides forever.”
— 1 John 2:15–17 (ESV) | First Epistle of John
——
Have you noticed that many platforms don’t merely contain temptation — they algorithmically AMPLIFY and reward it because those impulses reliably generate:
* attention
* engagement
* outrage
* envy
* desire
* comparison
* emotional compulsion
You can almost map the dynamics directly:
* Lust of the flesh
impulse gratification, addiction loops, emotional indulgence, compulsive consumption
* Lust of the eyes
endless visual comparison, curated lifestyles, envy, coveting, spectacle
* Pride of life
status signaling, follower counts, personal branding, public validation, performative identity
So what do we do?
Fight these impulses.
Or put another way:
“Stay humble and stack sats.”
Mind your own business.
Do meaningful work.
Don’t spend your life chasing things that will never satisfy.
#InChristAlone
I have wrestled a lot with the ideas you bring up in this article
Thank you for sharing.
5/21/2026 - Step 1 of the new Archive Sync Service inside Continuum:
Testing whether kind:1 notes can be reliably persisted into the archive layer directly from within the application runtime itself.
This flow currently:
* exports kind:1 events from the local Continuum database
* writes JSON + markdown projections into the local archive repositories
* updates history tracking
* commits archive changes via git
* synchronizes updates to the remote archive origins
One important realization during this work:
The archive itself exists locally *before* git synchronization occurs.
Meaning:
A failed git push does not necessarily mean the archival step failed.
The event may already exist inside the local archive repositories even if remote synchronization later fails.
This is gradually becoming something very different from normal “Nostr app” workflows.
Less focused on feeds/timelines.
More focused on:
* local-first authorship
* persistence
* archival continuity
* structured historical storage
* optional synchronization layers
#Continuum #Nostr #LocalFirst #Archival #DigitalSovereignty
This is a very powerful piece. Thank you for sharing it
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
5/18/2026 - Interesting feeling tonight:
The native Continuum build no longer feels like a packaged demo of the project.
It increasingly feels like the actual environment the project was aiming toward all along.
That shift is hard to quantify technically, but very obvious experientially once you begin using the compiled app itself daily for real writing, editing, exports, and publishing workflows.
#Continuum #LocalFirst #NativeApps #Nostr
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