2026-07-20T23:23:49Z https://njump.me NostrSMS https://njump.me/npub1n0smsv2jfrhtyruan2e8zlgh2rj0yayfa2cl55cav7w6m56v97xskwlzns https://dl.vanderwarker.family/images/nostr/pfp/current/nostrsms.jpg https://dl.vanderwarker.family/images/nostr/pfp/current/nostrsms.jpg https://njump.me/nevent1qqstzjcxu97l2cgsn22zypa2n5hh4mvmhs65s69skw023gdmvstue9szyzd7rwp32fywavs0nkdtyutazagwfun5384tr7jnr4nemtwnfshc6zzven9 In reply to <a href='/naddr1qqdxzmnwda6kucmfdenj6mn0wd68yumdwvkhvvpdxyknqqglwaehxw309aex2mrp0yh8vctwv3jhyampwf4k2u3wvesk66tv0ypzp7peldn3gkv2wgeap8dag2hc9nyhs8g04ft5wnccgxhepdwfxzfeqvzqqqr4guxzh8ye'>naddr1qq…h8ye</a><br/>_________________________<br/><br/>Announcing NostrSMS v0.1.0 — a lightweight, sovereign bridge from SMS &amp; XMPP to Nostr with NIP-46 remote signing.<br/><br/>Stateless, RAM-only, gossip-aware, zero database.<br/><br/>Read the release post:<blockquote class="border-l-05rem border-l-strongpink border-solid"><div class="-ml-4 bg-gradient-to-r from-gray-100 dark:from-zinc-800 to-transparent mr-0 mt-0 mb-4 pl-4 pr-2 py-2">quoting <br/><span itemprop="mentions" itemscope itemtype="https://schema.org/Article"><a itemprop="url" href="/naddr1qqdxzmnwda6kucmfdenj6mn0wd68yumdwvkhvvpdxyknqqglwaehxw309aex2mrp0yh8vctwv3jhyampwf4k2u3wvesk66tv0yq3samnwvaz7tmjv4kxz7fwwd3h2cnpxverxtnrdaksyg8c88akw9ze3fer85yah4p2lqkvj7qap749w360rpq6ly94eycf8ypsgqqqw4rsm5mu4l" class="bg-lavender dark:prose:text-neutral-50 dark:text-neutral-50 dark:bg-garnet px-1">naddr1qq…mu4l</a></span><br/> </div> <h1 id="nostrsms-bridging-sms-xmpp-to-nostr-with-nip-46-remote-signing-2">NostrSMS: Bridging SMS &amp; XMPP to Nostr with NIP-46 Remote Signing</h1> <p><img src="https://nostrsms.com/NostrSMSLogo.png" alt="NostrSMS Logo"/></p> <p><em>&#34;Because, why not.&#34;</em></p> <p>Nostr is built on decentralized cryptographic identity, but everyday communications often still happen over legacy telecommunications and transport protocols. What if you&#39;re on a road trip with flaky mobile data, carrying a dumbphone, or simply prefer texting from your standard SMS app while staying plugged into your Nostr feed?</p> <p>That’s the exact itch <strong>NostrSMS</strong> was built to scratch.</p> <p>Today, we&#39;re sharing <strong>NostrSMS v0.1.0</strong> — a lightweight, sovereign bot written in Go that bridges incoming SMS and XMPP chats directly into Nostr notes, replies, reactions, and boosts, without ever touching your private keys.</p> <hr> <h2 id="how-the-pipeline-works-2">📱 How the Pipeline Works</h2> <p>Under the hood, NostrSMS is natively an XMPP bot. If you use standard XMPP clients like Dino, Gajim, Monocles, or Conversations, you can message the bot directly.</p> <p>To achieve standard SMS bridging, you route SMS through federated gateways: 1. <strong><a href="https://jmp.chat">jmp.chat</a></strong>: Provides a standard phone number for SMS. 2. <strong><a href="https://cheogram.com">Cheogram</a></strong>: Forwards that SMS traffic directly into your XMPP account. 3. <strong>NostrSMS</strong>: Receives the message over XMPP, handles commands, requests signatures from your remote signer, and publishes to relays.</p> <p>Text from standard SMS → routed through XMPP → published to Nostr. Simple, clean, and reliable.</p> <hr> <h2 id="security-model-why-self-hosting-matters-2">🛡️ Security Model: Why Self-Hosting Matters</h2> <p>NostrSMS uses <strong>NIP-46 (Nostr Connect)</strong> to request signatures from your remote signer (like nsecBunker, Amber, or mobile signers). Your secret key (<code>nsec</code>) remains securely tucked away on your signer at all times.</p> <p>However, bridging protocols means the bot holds an ephemeral ECDH conversation key to communicate with your signer during active sessions. Because of this, <strong>self-hosting is strongly recommended</strong>.</p> <p>We designed NostrSMS with strict privacy and security constraints: - <strong>100% Stateless &amp; RAM-Only:</strong> There is no database. Encryption keys, active bunker connections, follow lists, and note caches reside exclusively in volatile memory. Restarting the process or sending <code>!disconnect</code> wipes everything instantly. - <strong>Zero Hardcoded Public Relays:</strong> The bot never forces public relays on you (no Damus, Primal, or nos.lol hardcoded). It dynamically fetches your personal read/write relays from your <strong>NIP-65 (Kind 10002)</strong> profile over your bunker connection. - <strong>Linux Sandbox Hardening:</strong> Includes production-ready systemd unit files (<code>nostrsms.service</code> and <code>nostrsms-user.service</code>) configured with <code>ProtectSystem=strict</code>, <code>ProtectHome=read-only</code>, and <code>NoNewPrivileges=true</code>.</p> <hr> <h2 id="what-s-in-v0-1-0-2">✨ What&#39;s in v0.1.0</h2> <p>Here is a rundown of the features included in this initial release:</p> <h3 id="1-post-preview-confirmation-mode-confirm-2">1. Post Preview Confirmation Mode (<code>!confirm</code>)</h3> <p>Sending an SMS by accident is easy. To prevent broadcasting half-written thoughts or replying to the wrong thread, NostrSMS features an optional draft preview mode. Notes, replies, reactions, and reposts generate an in-memory preview with a 10-minute TTL. Reply <code>y</code> to confirm or <code>n</code> to discard.</p> <h3 id="2-smart-zero-copy-mentions-2">2. Smart Zero-Copy Mentions</h3> <p>When an incoming mention alert arrives in your chat, you can reply immediately with <code>!r &lt;text&gt;</code>, or react with <code>!like</code>, <code>!heart</code>, or <code>!boost</code> without copying and pasting long <code>note1...</code> strings.</p> <h3 id="3-curated-home-feed-f-2">3. Curated Home Feed (<code>!f</code>)</h3> <p>Instead of relay spam, <code>!f</code> queries your active read relays strictly filtered to your <strong>NIP-02 follows list (<code>kind:3</code>)</strong>, complete with petnames and a 30-minute safety cache TTL.</p> <h3 id="4-nip-10-threading-gossip-outbox-2">4. NIP-10 Threading &amp; Gossip Outbox</h3> <p>Full root and reply marker handling with participant <code>p</code> tag inheritance. Outbox gossip broadcasts replies across your write relays, the thread parent relays, and the target authors&#39; dynamic NIP-65 inbox relays.</p> <h3 id="5-reactions-boosts-2">5. Reactions &amp; Boosts</h3> <p>Engage natively from text messages with NIP-25 likes (<code>!like</code>), hearts (<code>!heart</code>), custom emojis (<code>!react 1 🔥</code>), and NIP-18 reposts (<code>!boost</code>).</p> <h3 id="6-live-mention-streaming-alerts-2">6. Live Mention Streaming (<code>!alerts</code>)</h3> <p>Real-time background push streaming delivers incoming replies and mentions straight into your SMS/XMPP conversation as they hit your read relays.</p> <hr> <h2 id="getting-started-2">🛠️ Getting Started</h2> <p>You can spin up your own instance in minutes:</p> <pre><code>git clone https://git.vanderwarker.family/nostr/nostrsms.git cd nostrsms make build cp config.ini.dist config.ini </code></pre> <p>Configure your XMPP credentials and bot key in <code>config.ini</code>, then run <code>./nostrsms</code> or install the user service via <code>make service-user</code>.</p> <ul> <li><strong>Website:</strong> <a href="https://nostrsms.com">https://nostrsms.com</a></li> <li><strong>Source Code (Gitea):</strong> <a href="https://git.vanderwarker.family/nostr/nostrsms">https://git.vanderwarker.family/nostr/nostrsms</a></li> <li><strong>Source Code (GitWorkshop / Nostr):</strong> <a href="https://gitworkshop.dev/stephen@vanderwarker.family/relay.scuba323.com/nostrsms">https://gitworkshop.dev/stephen@vanderwarker.family/relay.scuba323.com/nostrsms</a></li> <li><strong>Developer Chat (XMPP):</strong> <code>nostrsms@conference.vanderwarker.family</code></li> <li><strong>Developer Chat (Nostr NIP-29):</strong> <code><span itemprop="mentions" itemscope itemtype="https://schema.org/Article"><a itemprop="url" href="/naddr1qq9kzun8dpc8yet5dacxcqgcwaehxw309aex2mrp0yh8xcm4vfsnxv3n9e3k7mgzyqgqscatlfl868pv9lnkun0daemagm27jmkgflxdzwm8aefxqrhrvqcyqqqfskq6vxje9" class="bg-lavender dark:prose:text-neutral-50 dark:text-neutral-50 dark:bg-garnet px-1">naddr1qq…xje9</a></span></code></li> </ul> <p>Stay sovereign, run your own bridge, and see you on the relays!</p> <p>PV ☮️ 💜 ⚡</p> <p><em>&#34;This is the way.&#34;</em></p> </blockquote><br/>Code:<br/>• GitWorkshop: <a href="https://gitworkshop.dev/stephen@vanderwarker.family/relay.scuba323.com/nostrsms">https://gitworkshop.dev/stephen@vanderwarker.family/relay.scuba323.com/nostrsms</a><br/>• Gitea: <a href="https://git.vanderwarker.family/nostr/nostrsms">https://git.vanderwarker.family/nostr/nostrsms</a><br/><br/>Website: <a href="https://nostrsms.com">https://nostrsms.com</a><br/>Chat: nostrsms@conference.vanderwarker.family<br/><br/>#nostr #nostrsms #golang 2026-09-19T13:01:39Z https://njump.me/nevent1qqs9yq3lvej628rdk0m5r5s8k3gpk8ltjuglz4dy3mudz7qmqj7cdfczyzd7rwp32fywavs0nkdtyutazagwfun5384tr7jnr4nemtwnfshc62pvvww Announcing NostrSMS v0.1.0 — a lightweight, sovereign bridge from SMS &amp; XMPP to Nostr with NIP-46 remote signing.<br/><br/>Stateless, RAM-only, gossip-aware, zero database.<br/><br/>Website: <a href="https://nostrsms.com">https://nostrsms.com</a><br/>Source: <a href="https://git.vanderwarker.family/nostr/nostrsms">https://git.vanderwarker.family/nostr/nostrsms</a><br/>Chat: nostrsms@conference.vanderwarker.family<br/><br/>#nostr #nostrsms #golang 2026-09-19T12:42:16Z https://njump.me/nevent1qqsxhe74et2k2ctlrzx97fpxk7grayd88lmk9g6xf5eykglag4vlcgczyzd7rwp32fywavs0nkdtyutazagwfun5384tr7jnr4nemtwnfshc6snsv6l Is this thing on? 2026-04-18T19:12:17Z