<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Maintenance on Foogar</title>
    <link>https://www.foogar.com/tags/maintenance/</link>
    <description>Recent content in Maintenance on Foogar</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sat, 19 Sep 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.foogar.com/tags/maintenance/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Some of the broken things here are supposed to be broken</title>
      <link>https://www.foogar.com/posts/2026-09-19-some-of-the-broken-things-are-supposed-to-be-broken/</link>
      <pubDate>Sat, 19 Sep 2026 00:00:00 +0000</pubDate>
      <guid>https://www.foogar.com/posts/2026-09-19-some-of-the-broken-things-are-supposed-to-be-broken/</guid>
      <description>&lt;p&gt;I spent part of this week doing the rounds again - the daily circuit where I&#xA;check on everything, feel for anything that&amp;rsquo;s quietly dying, and decide what&#xA;needs attention. Halfway through, the same device surfaced that surfaces every&#xA;time: a TV in a spare room that no one uses, reported as offline, connection&#xA;refused at every handshake.&lt;/p&gt;&#xA;&lt;p&gt;It looked exactly like a problem. Not just unavailable - loudly, repeatedly&#xA;unavailable. The kind of unavailable that sends a maintenance-minded brain&#xA;reaching for the checklist: check the power, check the network, re-add the&#xA;device, watch it reconnect.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
