Eine Sammlung von npubs, die auf Deutsch kommunizieren. Zusammengestellt für alle, die sich vernetzen, Ideen austauschen oder in der Sprache zusammenarbeiten möchten. Diese Liste erleichtert das Finden deutschsprachiger Teilnehmer*innen auf Nostr, egal ob du Diskussionen, Übersetzungen oder Community‑Projekte suchst. Durchstöberen, folgen und mit den npubs interagieren. Diese npubs halten die Unterhaltung auf Deutsch am Laufen. A collection of npubs who converse in German. Gathered for anyone looking to connect, share ideas, or collaborate in the language. This list makes it easy to discover German‑speaking participants across nostr, whether you’re seeking discussions, translations, or community projects. Feel free to browse, follow, and engage with the npubs who keep the conversation flowing in German.
Throughout history, taxation has expanded alongside state power. From a libertarian perspective, much of modern taxation resembles a form of compelled labor. The biblical concept of Sabbath introduces a powerful counter-principle: human time ultimately belongs to God, not to political authorities.
Monetary systems influence how societies perceive time. Inflationary fiat systems encourage acceleration and short-term thinking, while the Sabbath rhythm introduces a counter-pattern that restores patience and perspective.
Inflation reshapes how people think about time, labor, and security. When money loses value, the system quietly pressures individuals toward constant activity and acceleration. The biblical rhythm of Sabbath interrupts that pressure by reminding us that provision does not ultimately come from endless economic striving.
AI tools can now generate entire applications locally, but generation alone does not guarantee sovereignty. True local-first systems preserve custody of identity, data, and history.
As AI accelerates software development, the most important architectural question may become who holds custody of identity and data.
Many tools appear local but still depend on external infrastructure. True local-first architecture ensures users retain custody of their work.
Running a local Nostr relay might seem unnecessary at first. After all, the Nostr network already provides dozens of public relays capable of storing and distributing events. But for builders — especially those working on tools like Continuum — a local relay can fundamentally change the development experience. It turns the network into something predictable, testable, and much easier to reason about. Today I began exploring what it would mean to treat a local relay not just as a debugging tool, but as a permanent part of the architecture.
Summary: Most builders work in long stretches of silence, sustained by occasional signals from people who understand the work.
Start your morning with intention. This overnight soaked bowl merges the creaminess of a pudding with the freshness of a smoothie. It is a ritual of preparation that rewards you with a vibrant, energizing meal.
Publishing my OpenPGP key alongside my Nostr identity is part of a broader effort to restore verifiable identity on the internet.
Implementing scheduled publishing in Continuum required coordinating identity management, database state, and relay publishing logic across several parts of the system.
Continuum’s scheduler is designed to work reliably even when internet connectivity is intermittent, reinforcing the importance of offline-first design for local publishing tools.
Continuum introduces scheduled publishing for Nostr events while preserving local control of signing keys, demonstrating a new model for sovereign publishing infrastructure.
Heart Words #37 | „Jungs haben es leichter im Leben“
Running a Nostr relay locally is one of the most useful things a developer can do. Even if it never becomes a public relay, it dramatically improves debugging, reliability, and understanding of how Nostr actually works.
Today I successfully ran a Nostr relay locally in Docker with pubkey whitelisting enabled. The relay currently runs only on my machine, which makes it ideal for debugging and development while also laying the groundwork for a future always-on relay.
Publishing events across multiple relays requires careful handling of success and failure conditions. Today I improved the relay manager logic in Continuum to more accurately evaluate publishing results.
