<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Go on David Pinkerton</title>
    <link>https://blog.dpinkerton.com/tags/go/</link>
    <description>Recent content in Go on David Pinkerton</description>
    <generator>Hugo -- 0.154.5</generator>
    <language>en-us</language>
    <lastBuildDate>Sat, 11 Apr 2026 18:00:00 +1000</lastBuildDate>
    <atom:link href="https://blog.dpinkerton.com/tags/go/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>I Built a Dead Man&#39;s Switch That Watches My Nostr Activity</title>
      <link>https://blog.dpinkerton.com/posts/nostr-dead-man-switch/</link>
      <pubDate>Sat, 11 Apr 2026 18:00:00 +1000</pubDate>
      <guid>https://blog.dpinkerton.com/posts/nostr-dead-man-switch/</guid>
      <description>&lt;p&gt;A dead man&amp;rsquo;s switch triggers actions if you stop responding. The existing ones — &lt;a href=&#34;https://github.com/alpyxn/aeterna&#34;&gt;Aeterna&lt;/a&gt;, &lt;a href=&#34;https://github.com/giovantenne/lastsignal&#34;&gt;LastSignal&lt;/a&gt; — require periodic manual check-ins. That works. But Nostr already has a better signal: every post, reaction, zap, and repost is a cryptographically signed event tied to your public key. Your normal usage is proof of life.&lt;/p&gt;
&lt;p&gt;I built &lt;a href=&#34;https://github.com/AusDavo/nostr-dead-man-switch&#34;&gt;nostr-dead-man-switch&lt;/a&gt; to use that signal. It subscribes to relays, watches for any event from my npub, and resets its timer on activity. If I go quiet for long enough and don&amp;rsquo;t respond to warning DMs, it fires off emails, webhooks, or Nostr notes to the people who need to know.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
