<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0">
  <channel>
    <title>SteadyWatch status updates</title>
    <link>https://status.steadywatch.org/</link>
    <description>Plain-English status updates for steadywatch.org itself. The watchman keeps a page on the watchman.</description>
    <language>en-us</language>
    <item>
      <title>steadywatch.org went live</title>
      <link>https://status.steadywatch.org/</link>
      <guid isPermaLink="false">steadywatch-self-1</guid>
      <pubDate>Mon, 25 Aug 2026 03:55:00 +0000</pubDate>
      <description>The domain was registered, the homepage deployed, and the three founding member status pages went live on their own domains, all in one day.</description>
    </item>
    <item>
      <title>We failed our own test, then fixed it</title>
      <link>https://status.steadywatch.org/</link>
      <guid isPermaLink="false">steadywatch-self-2</guid>
      <pubDate>Mon, 25 Aug 2026 05:35:00 +0000</pubDate>
      <description>A full audit found our pages serving none of the browser protections we grade other sites on, and our content policy silently blocking the page analytics. Both fixed and verified within the hour, and written down here because a status page that hides its own mistakes is not worth trusting.</description>
    </item>
    <item>
      <title>Plain http now forwards to https</title>
      <link>https://status.steadywatch.org/</link>
      <guid isPermaLink="false">steadywatch-self-3</guid>
      <pubDate>Mon, 25 Aug 2026 06:05:00 +0000</pubDate>
      <description>A second look found plain http serving the page instead of forwarding to the secure address. The forward is now in place, and this page exists so findings like this are public.</description>
    </item>
  </channel>
</rss>
