<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Skudo</title>
    <link>https://blog.skudo.org</link>
    <description>Notes on building a private email aliasing service.</description>
    <language>en</language>
    <atom:link href="https://blog.skudo.org/feed.xml" rel="self" type="application/rss+xml" />
        <item>
      <title>Why we stopped asking for a username</title>
      <link>https://blog.skudo.org/why-we-stopped-asking-for-a-username</link>
      <guid isPermaLink="true">https://blog.skudo.org/why-we-stopped-asking-for-a-username</guid>
      <pubDate>Wed, 02 Sep 2026 20:54:57 +0000</pubDate>
      <description>Skudo asked for a username before anything else. It was the step with the most ways to fail, for a feature most people never use. Here is what replaced it.</description>
    </item>
        <item>
      <title>What a warrant canary cannot do</title>
      <link>https://blog.skudo.org/what-a-canary-cannot-do</link>
      <guid isPermaLink="true">https://blog.skudo.org/what-a-canary-cannot-do</guid>
      <pubDate>Wed, 02 Sep 2026 20:54:57 +0000</pubDate>
      <description>Warrant canaries are widely published and widely misunderstood. What they prove, the three properties that make one meaningful, and how to read silence.</description>
    </item>
        <item>
      <title>What happens to your address when a shop is breached</title>
      <link>https://blog.skudo.org/what-happens-when-a-shop-is-breached</link>
      <guid isPermaLink="true">https://blog.skudo.org/what-happens-when-a-shop-is-breached</guid>
      <pubDate>Wed, 02 Sep 2026 20:54:57 +0000</pubDate>
      <description>What happens to an email address after a breach, why aliases change the outcome, and what to do on the day you find out about one.</description>
    </item>
      </channel>
</rss>
