<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"><channel><title>MeshWhisper Blog</title><description>Announcements and engineering notes from the MeshWhisper project.</description><link>https://meshwhisper.org/</link><item><title>The flaky test was telling the truth</title><link>https://meshwhisper.org/blog/the-flake-was-a-bug/</link><guid isPermaLink="true">https://meshwhisper.org/blog/the-flake-was-a-bug/</guid><description>A delete-and-re-add test failed about one run in eight under load. The tempting fix was a bigger timeout. The real fix was a bug: a single stray packet could make the SDK re-handshake — and silently destroy — a perfectly healthy session.</description><pubDate>Tue, 16 Jun 2026 15:00:00 GMT</pubDate></item><item><title>Relays that find each other without a phone book</title><link>https://meshwhisper.org/blog/dns-free-relay-location/</link><guid isPermaLink="true">https://meshwhisper.org/blog/dns-free-relay-location/</guid><description>MeshWhisper relays now locate and reach each other by cryptographic key — no DNS anywhere in the routing path. Through NAT, with onion-routed hops, even when both ends are firewalled. The last bit of centralization in the mesh, removed.</description><pubDate>Tue, 16 Jun 2026 13:00:00 GMT</pubDate></item><item><title>Messaging should work like email</title><link>https://meshwhisper.org/blog/messaging-like-email/</link><guid isPermaLink="true">https://meshwhisper.org/blog/messaging-like-email/</guid><description>Every messenger is a walled garden: WhatsApp users can&apos;t message Signal users, and that&apos;s by design, not accident. But MeshWhisper&apos;s relay can&apos;t even tell which app a packet belongs to — so the walls were never load-bearing. We tore one down. Any app, any operator, anyone-to-anyone, end-to-end encrypted. Like email, except private.</description><pubDate>Mon, 15 Jun 2026 10:00:00 GMT</pubDate></item><item><title>What the relay sees (we built a button to show you)</title><link>https://meshwhisper.org/blog/what-the-relay-sees/</link><guid isPermaLink="true">https://meshwhisper.org/blog/what-the-relay-sees/</guid><description>The whole pitch is that the relay can&apos;t read your messages. That&apos;s a claim. So we added a button that puts your plaintext next to the exact encrypted blob the relay actually receives — same screen, no trust required. Tap a message, see the ciphertext.</description><pubDate>Sun, 14 Jun 2026 10:00:00 GMT</pubDate></item><item><title>The week Prudence stopped being a demo</title><link>https://meshwhisper.org/blog/prudence-grew-up/</link><guid isPermaLink="true">https://meshwhisper.org/blog/prudence-grew-up/</guid><description>Prudence could already send end-to-end encrypted messages. That&apos;s not the same as being an app you&apos;d leave open all day. This is the unglamorous week of drafts, search, delete, export-your-data, and adding a friend by pointing your camera at their phone — the work that turns a proof into a product.</description><pubDate>Sat, 13 Jun 2026 10:00:00 GMT</pubDate></item><item><title>MeshWhisper 0.3: messaging that survives losing its own infrastructure</title><link>https://meshwhisper.org/blog/meshwhisper-0-3/</link><guid isPermaLink="true">https://meshwhisper.org/blog/meshwhisper-0-3/</guid><description>Two devices on the same network now deliver messages peer-to-peer. Kill the relay, pull the internet — the conversation carries on, encrypted, like nothing happened. Plus open federation and the rest of a busy two months.</description><pubDate>Fri, 12 Jun 2026 13:00:00 GMT</pubDate></item><item><title>Who&apos;s it for? Doctors, ships, robots, and the justifiably paranoid</title><link>https://meshwhisper.org/blog/who-its-for/</link><guid isPermaLink="true">https://meshwhisper.org/blog/who-its-for/</guid><description>Where structural can&apos;t-read-it messaging actually matters: regulated industries, isolated networks, machines talking to machines, and AI agents that need to prove who they&apos;re talking to.</description><pubDate>Fri, 12 Jun 2026 12:00:00 GMT</pubDate></item><item><title>What it actually does: a tour of the box</title><link>https://meshwhisper.org/blog/what-it-does/</link><guid isPermaLink="true">https://meshwhisper.org/blog/what-it-does/</guid><description>The capabilities, honestly labelled: what&apos;s production, what&apos;s shipped-but-young, and what&apos;s a designed promise. No roadmap items wearing a trenchcoat pretending to be features.</description><pubDate>Fri, 12 Jun 2026 11:00:00 GMT</pubDate></item><item><title>It started, as these things do, with a text at midnight</title><link>https://meshwhisper.org/blog/the-story/</link><guid isPermaLink="true">https://meshwhisper.org/blog/the-story/</guid><description>The origin story: two lads, one late-night conversation, two PRDs written simultaneously by accident, and a working prototype before anyone had the sense to go to bed.</description><pubDate>Fri, 12 Jun 2026 10:00:00 GMT</pubDate></item><item><title>What is MeshWhisper? (or: the postman who can&apos;t read)</title><link>https://meshwhisper.org/blog/what-is-meshwhisper/</link><guid isPermaLink="true">https://meshwhisper.org/blog/what-is-meshwhisper/</guid><description>The whole idea in one sitting: end-to-end encrypted messaging for any app, through infrastructure that couldn&apos;t read your messages if it wanted to. Which it doesn&apos;t. It&apos;s a pipe.</description><pubDate>Fri, 12 Jun 2026 09:00:00 GMT</pubDate></item></channel></rss>