<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Status-Page on Chetan&#39;s Portfolio</title>
    <link>https://chetan-thapliyal.cloud/tags/status-page/</link>
    <description>Recent content in Status-Page on Chetan&#39;s Portfolio</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <copyright>© 2026 Chetan Thapliyal</copyright>
    <lastBuildDate>Fri, 20 Nov 2026 12:18:00 +0530</lastBuildDate><atom:link href="https://chetan-thapliyal.cloud/tags/status-page/index.xml" rel="self" type="application/rss+xml" />
    
    <item>
      <title>A Public Status Page That Can&#39;t Leak, and Can&#39;t Flatter Me Either</title>
      <link>https://chetan-thapliyal.cloud/posts/status-page-that-cannot-leak/</link>
      <pubDate>Fri, 20 Nov 2026 12:18:00 +0530</pubDate>
      
      <guid>https://chetan-thapliyal.cloud/posts/status-page-that-cannot-leak/</guid>
      <description>My homelab&amp;rsquo;s public status page shows recovery targets next to what a drill measured, incident response times computed from the reviews themselves, and a visit count with no tracking script, all under a strict Content Security Policy. How each part works, and why the page is built so it can&amp;rsquo;t make me look better than the evidence.</description>
      <media:content xmlns:media="http://search.yahoo.com/mrss/" url="https://chetan-thapliyal.cloud/posts/status-page-that-cannot-leak/featured.png" />
        <media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="https://chetan-thapliyal.cloud/posts/status-page-that-cannot-leak/featured.png" />
    </item>
    
  </channel>
</rss>
