Released the Continuum Browser Signing Extension as open source. Browser-based signing without tying identities to a specific browser profile. Use existing Nostr experiences while keeping identity management local-first. Not another client — trying to explore a different trust model. #nostr #opensource #bitcoin

OK so I started using Damus Notedeck comparing Damus w/ Primal and some other clients...

And this shows the connection history of successful browser sessions .... (I don't know if anyone is interested...)

Thought I would share this ... This is the console window WITHIN my continuum that shows logging into iris using my browser extension...

6/12 - Would like to start posting articles and notes again — it's been a while. (I was very very prolific for a while but I have been adding a lot to Continuum over the last few weeks. I just want to publish again ... Here are a few topics I’d like to explore: • Continuum Is Not Another Nostr Client • Browser Extensions vs Mobile Signers • Why I Still Prefer Local-First Software • The Hidden Cost of SaaS Logins • What Bitcoin Conferences Get Wrong About Identity • Remote Signing Without Browser Lock-In • From Social Graphs to Service Graphs (just some ideas I have) #Nostr #Bitcoin #LocalFirst #DigitalSovereignty #Identity #SelfCustody #Continuum

checking out Iris (using my browser extension from Continuum).

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