Builders Work Quietly - 3/10/2026 Summary: Much of building happens quietly, far from the noise of social media. Today was a reminder that building rarely looks dramatic from the outside. There are long stretches of quiet work: • updating profiles • refining small applications • responding carefully to thoughtful messages • experimenting with patterns None of this looks impressive on social media. But these small steps accumulate. Over time they become the foundation for much larger systems. #builders #reflection

A Positive Signal - 3/10/2026 Summary: A thoughtful signal from a Nostr user prompted a deeper response and several hours of reflection. Today I received a positive signal from a Nostr user. Signals like this matter more than people might realize. Most of the time when you publish online, especially when building something new, you are operating in **relative silence**. You release ideas. You ship code. You publish articles. And often the response is minimal. But occasionally someone thoughtful reaches out and engages. The user's message prompted me to spend time crafting a careful response. I probably spent close to **two hours thinking through and writing that reply**. These moments are encouraging. They remind me that even when progress feels slow, the work **is reaching people who understand what is being built**. #nostr #builders #signals #network

Updating My Nostr Profile and Adding PGP Verification - 3/10/2026 Summary: I spent time updating my Nostr profile and publishing my OpenPGP public key for encrypted communication and verification. Today I spent some time refreshing my Nostr profile. The biggest change was publishing my **OpenPGP public key** and creating a dedicated page for it. This allows people to: • verify messages I sign • encrypt communications to me • confirm that identities I control are legitimate In the Nostr world, identity is tied to the **npub / private key pair**, but PGP still serves an important complementary role. PGP allows: • cross-platform identity verification • signed documents outside Nostr • encrypted email communication Publishing the key fingerprint publicly is also important so people can confirm they are using the correct key. It is a small step, but it strengthens the broader theme I care about: **self-sovereign identity and verifiable communication.** #nostr #pgp #gpg #identity #security

stimmt !

Local Scheduling as a Sovereign Publishing Primitive - 3/9/2026 Summary: Scheduled publishing is a fundamental building block for sovereign publishing systems built on Nostr. Many publishing platforms support scheduled posts. But they do so by storing drafts and keys inside centralized services. Continuum takes a different approach. Events are signed locally first. Then the scheduler simply decides when to publish them. This keeps the important boundary intact: Signing stays local. Publishing can be delayed. That small difference preserves control over keys and identity. #nostr #sovereignty #continuum #publishing

Article Scheduling UI Parity with Notes - 3/9/2026 Summary: The article list view in Continuum now reflects scheduled publishing states similar to notes, improving visibility into upcoming posts. Notes already displayed scheduled publishing clearly. Articles did not. Today I corrected that. Now the article list view understands three states: Unpublished Scheduled Published If an article is scheduled, the interface now shows: Scheduled badge Scheduled publish time Disabled “Publish (Scheduled)” button This keeps the UI consistent across notes and articles and makes it much easier to see what is queued for publication. #continuum #ui #nostr #software

Scheduling Events While Offline - 3/9/2026 Summary: Continuum preserves scheduled publishing events even if the network is offline, ensuring they publish once connectivity is restored. One subtle but important behavior showed up during testing today. If Continuum is offline when a scheduled publish time occurs, the event does **not fail**. It simply remains in the scheduled state. Once the network returns and Continuum restarts, the scheduler detects that the publish time has already passed and immediately publishes the event. This avoids a major class of failure that many scheduling systems have. In other words: Offline does not break the scheduler. It simply delays execution until publishing is possible. For a local-first publishing system, that behavior matters a lot. #continuum #nostr #offlinefirst #softwaredesign

Scheduled Publishing for Articles Now Working - 3/9/2026 Summary: Continuum now supports scheduled publishing for both notes and articles, enabling authors to queue signed events locally and publish them automatically at a future time. Today I confirmed that scheduled publishing works not only for notes but also for long-form articles in Continuum. The workflow now looks like this: 1. Write the article locally 2. Sign the event locally 3. Choose a future publish time 4. Continuum stores the signed event and waits 5. At the scheduled time, the event is automatically published to relays This means authors can queue work ahead of time without giving custody of their keys to a third-party platform. Everything happens locally. Even better, if the machine is offline when the scheduled time passes, the event remains in a scheduled state and publishes automatically once the network is restored and Continuum restarts. This is exactly the kind of behavior a sovereign publishing system should have. #continuum #nostr #publishing #localfirst #sovereignty

Timezone Handling for Scheduled Publishing (Current State) - 3/9/2026 Summary: Continuum currently displays scheduled publishing times using a fixed timezone while future improvements will allow timezone configuration per identity. While testing scheduled publishing today, I noticed that scheduled times are currently displayed using a fixed timezone. Right now the API converts scheduled timestamps using a hard-coded timezone setting. This works fine for development and testing, but it is not the long-term plan. Continuum identities already store configuration data locally, and timezone settings can eventually be pulled directly from the active identity configuration. That would allow each identity to display scheduled publish times relative to its own local context. For now the behavior is simple and predictable, which is good enough while the scheduling system itself is being validated. #continuum #scheduler #nostr #software

Toward a Personal Relay 3/8/2026 The relay configuration used locally today could eventually run on an always-on machine and become a permanent personal relay endpoint. For now it serves as a development relay while the architecture continues to evolve. #nostr #relays

Title: Local Relay for Development - 3/8/2026 The Docker relay currently runs locally and is useful for testing relay interactions and inspecting events. Events written to it remain local unless they are also published to external relays. #nostr #development

Improved publish_event Logic - 3/8/2026 Updated the relay manager logic so publishing is considered successful if at least one relay accepts the event. This better reflects how Nostr publishing works in practice. #nostr #relay-manager

Relay Pubkey Whitelisting Enabled - 3/8/2026 Configured the relay with pubkey whitelisting so that only approved identities can publish events. This keeps the relay clean and prevents unwanted writes while testing. #nostr #relays #security

Local Relay Running in Docker - 3/8/2026 Successfully started a Nostr relay locally inside Docker. The relay currently runs only on my development machine and is not yet exposed publicly. Even so, it provides a useful environment for debugging, testing relay behavior, and validating publishing logic. #nostr #relays #docker

Sabbath Reflection: Rest and Building - 3/7/2026 Summary: Considering the relationship between rest, calling, and building meaningful systems. --- The Sabbath is traditionally understood as a day of rest. But rest does not always mean inactivity. Sometimes rest means stepping away from obligation and moving toward calling. Today I continued building Continuum. And yet the work felt calm, focused, and almost restorative. Perhaps the difference is not activity versus inactivity. Perhaps the difference is obligation versus alignment. When the work aligns with purpose, the experience changes. It becomes something closer to rest than labor. #sabbath #calling #reflection

Sabbath Reflection: Writing Without Permission - 3/7/2026 Summary: Local-first tools allow creators to write without waiting for platforms or networks. One of the things I appreciate about Continuum is that writing does not require permission. There is no server that must be reachable. No platform that must approve the post. No account system that must authenticate you. You can simply write. If the network is available, the event can be published. If it is not, the event can wait. But the act of writing itself is never blocked. That small design choice restores something that the modern internet slowly took away: independence. And that independence feels particularly appropriate to reflect on today. #sabbath #sovereignty #writing

Sabbath Reflection: Quiet Progress - 3/7/2026 Summary: A reminder that meaningful progress often happens quietly and without external recognition. --- There are days when building something new feels loud. Announcements, releases, conversations. And then there are days like today. Quiet days. Today I spent most of the time refining small behaviors in the system. Disabling publish buttons when the network is offline. Ensuring notes behave correctly. Improving the overall experience. None of this will likely make headlines. But software is not built from headlines. It is built from hundreds of small, careful decisions. Quiet progress still counts as progress. #sabbath #reflection #building #persistence

Sabbath Reflection: Offline First - 3/7/20206 Summary: Observing how building offline capabilities in Continuum reinforces the philosophy of local-first computing. --- One of the things I worked on today was strengthening Continuum’s offline behavior. When the system detects that the network is unavailable, it now communicates that clearly to the user. Certain actions—like publishing events or deleting notes from relays—are disabled while offline. Other actions remain available. Writing remains available. Scheduling remains available. Signing remains available. Only the parts that truly require the network are restricted. This is what local-first software is supposed to feel like. The machine in front of you remains fully capable even when the outside world disappears. It is surprising how rare that philosophy has become. Today’s small changes brought Continuum closer to that vision. #sabbath #continuum #offline-first #nostr

Sabbath Reflections: Work That Does Not Feel Like Work - 3/7/2026 Summary: A reflection on the strange gift of building something meaningful on the Sabbath without feeling burdened by it. --- Today I worked. But it did not feel like work. There is a difference between labor that drains you and labor that feels aligned with purpose. Today was the latter. The hours passed quietly, almost unnoticed, as I continued implementing offline capabilities inside Continuum. In particular, the notes system is now very close to being fully functional even when the network is unavailable. Notes can still be written, signed, scheduled, and managed locally. Publishing may wait until connectivity returns, but the act of writing itself does not depend on the network. This feels important. Most software assumes the network is always present. But real life is not like that. Planes lose connection. WiFi drops. Relays go offline. And yet writing should continue uninterrupted. In a small way, building software that respects this reality feels like honoring the rhythm of life itself. And today, oddly enough, that work felt like rest. #sabbath #reflection #work #calling #continuum

Example screenshot of an event (kind:1) that was signed but then published later https://is.gd/wawt2Z (this note itself will be published 2 minutes from the time it was signed)