Sovereignty at the Table
Is your hardware truly sovereign? We analyse the ethics behind Bitcoin devices and how to avoid confusing ecosystems.
German speaking users | Deutsch sprechende Nutzer
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.
Curated by
thepurpose
Souveränität am Tisch: Bitcoin Hardware Ethik
Ist deine Hardware wirklich souverän? Wir analysieren die Ethik hinter Bitcoin-Geräten und wie man verwirrende Ökosysteme vermeidet.
“Nostr Clients Are Enough”
Nostr clients are powerful — especially for discovery and interaction. But they are not designed for ownership, authoring, or long-term control. This article explores why clients are essential, but not sufficient, and what changes when you separate discovery from creation.
Writing Isn’t Publishing
Most modern systems collapse writing and publishing into a single action. This creates hidden pressure and limits how ideas develop. This article explores why separating authoring from distribution matters — and how local-first systems restore a healthier way to think, write, and share.
You Shouldn’t Need the Internet to Think
Most modern tools assume constant connectivity. If the network is down, the system stops working. This article explores how that assumption quietly reshapes how we create, think, and work — and why local-first systems restore something deeper than just offline access.
You Don’t Own Your Account
Most people believe they “own” their accounts, data, and identity online. In reality, they have access — not ownership. This article explores how small, everyday failures (like password resets and lockouts) reveal a deeper architectural problem, and why local-first systems change that foundation.
Zwischen Bitcoin und Ego
Heart Words #39 | Die Frequenz des Geldes
Evan writes on nostr
Analysis of the economical and political situation in the United States and its future.
You Don’t Rise Into Clarity, You Build Into It
Clarity is not discovered in abstraction. It is formed through the act of building—over time, through resistance, iteration, and commitment.
Building Without Applause
The absence of recognition is not a signal to stop. It is often the condition required to build something that lasts.
Building Is a Form of Stewardship
Building is not just creation—it is stewardship. It reflects how we manage time, responsibility, and what has been entrusted to us.
Sabbath Is Not a Break. It’s Alignment.
Sabbath is not a recovery mechanism for exhaustion—it is a return to alignment with God as the true source. This article explores how rest reframes work, exposes hidden dependencies, and reshapes the way we build, write, and live.
You Cannot Build What You Refuse to Leave
Sabbath reveals whether we are building in trust or in control. This article explores how our attachment to work exposes hidden dependencies, and why true durability requires the ability to step away.
🔒 Book 2 - Building Local-First Systems - Chap. 9 - Separation of Authoring and Distribution
Most systems tightly couple the act of creating content with the act of publishing it. This creates dependency on networks, platforms, and infrastructure at the moment of creation. Local-first systems must separate these concerns. This chapter defines the distinction between authoring and distribution and explains how decoupling them enables durability, flexibility, and true sovereignty.
🔒 Book 2 - Building Local-First Systems - Chap. 8 - Identity as a First-Class Primitive
Most systems treat identity as an afterthought — something layered on top of functionality through accounts and authentication. Local-first systems cannot. Identity must be foundational, shaping how data is created, signed, verified, and distributed. This chapter defines identity as a first-class primitive and outlines the design implications of building systems around it.
🔒 Book 2 - Building Local-First Systems - Chap 7 - Determinism Over Dynamism
Local-first systems prioritize determinism — predictable, reproducible behavior — over dynamic, server-driven state. This chapter explains why determinism is essential for trust, recoverability, and durability, and how it shapes system design choices around state, execution, and synchronization.
Evan writes on nostr
Forecast of the economic development of Western Asia.
🔒 Book 2 - Building Local-First Systems - Chap 5 - Why SaaS Became the Default
Software-as-a-Service did not become dominant because it was inherently better for users. It became the default because it aligned with the economic incentives of companies and the operational realities of the web. This chapter explores the forces that led to SaaS dominance and why those forces continue to shape modern software architecture.
🔒 Book 2 - Building Local-First Systems - Chap 4 - Data Ownership vs Data Access
Ownership is often confused with visibility. Many systems allow users to see and interact with their data, but stop short of granting true control over it. This chapter clarifies the distinction between owning data and merely accessing it, and explains why local-first systems must prioritize ownership at the structural level.