<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"><channel><title>the facko space — Field Notes</title><description>Field notes on systems, privacy, automation, and digital culture.</description><link>https://thefacko.decortel.de</link><language>en</language><item><title>GPU passthrough broke again</title><link>https://thefacko.decortel.de/notes/gpu-passthrough-again</link><guid isPermaLink="true">https://thefacko.decortel.de/notes/gpu-passthrough-again</guid><description>The RX 7600 XT guest stopped responding again. The VM list still looked reassuring. A closer status check reported an internal error.

This time the card was still on the PCI bus. Stopping the guest worked. Starting it with the GPU attached did not. The host reboot brought inference back.

The failure happened while idle, which weakened the earlier theory about load being the trigger. Firmware polling and runtime power management became the next things to test. They are a working hypothesis, not a proven cause.

The practical lesson: “running” is a process state. It is not a health check. A small inference request tells me more than the green status label.</description><pubDate>Thu, 03 Sep 2026 00:00:00 GMT</pubDate><category>Proxmox</category><category>GPU</category><category>recovery</category></item><item><title>One dashboard is enough</title><link>https://thefacko.decortel.de/notes/one-dashboard</link><guid isPermaLink="true">https://thefacko.decortel.de/notes/one-dashboard</guid><description>The Home Assistant sidebar had accumulated several ways to get to roughly the same controls. The useful change was making one room-oriented dashboard the starting point and moving the old ones out of the way.

A missing sensor value also needed to stay missing. Turning “unavailable” into zero makes a tidy graph and a misleading room.

The next pass is about physical behavior: the dimmer, the scene, and the dashboard should agree about what just happened.</description><pubDate>Wed, 02 Sep 2026 00:00:00 GMT</pubDate><category>Home Assistant</category><category>interfaces</category><category>maintenance</category></item><item><title>Quiet systems</title><link>https://thefacko.decortel.de/notes/quiet-systems</link><guid isPermaLink="true">https://thefacko.decortel.de/notes/quiet-systems</guid><description>The best infrastructure is the kind nobody notices. A cron job that has run without incident for three years earns more trust than any dashboard. Optimizing for silence — not throughput, not features — changes which decisions look correct.

Most incidents I&apos;ve traced back start with someone trying to make a quiet system louder: more logging, more alerts, more surface area to fail on. Instrumentation is not the same as understanding.</description><pubDate>Tue, 02 Jun 2026 00:00:00 GMT</pubDate><category>systems</category><category>field</category></item><item><title>Automation as leverage, not identity</title><link>https://thefacko.decortel.de/notes/automation-as-leverage</link><guid isPermaLink="true">https://thefacko.decortel.de/notes/automation-as-leverage</guid><description>A script that saves twenty minutes a day is worth more than a personality built around &quot;being an automation person.&quot; The former compounds. The latter has to be defended in meetings.

Rule I keep coming back to: automate the boring, reversible, well-understood steps first. Leave judgment calls to a human until the system has earned the right to make them unsupervised.</description><pubDate>Mon, 18 May 2026 00:00:00 GMT</pubDate><category>automation</category><category>leverage</category></item><item><title>Notes on private infrastructure</title><link>https://thefacko.decortel.de/notes/private-infrastructure</link><guid isPermaLink="true">https://thefacko.decortel.de/notes/private-infrastructure</guid><description>Moved another service off a third-party SaaS this month and onto the homelab. Not out of ideology — out of a preference for owning the failure modes. When something breaks now, I know exactly why.

The tradeoff nobody advertises: self-hosting trades convenience for legibility. You lose a support ticket queue and gain a system you can actually reason about end to end.</description><pubDate>Thu, 30 Apr 2026 00:00:00 GMT</pubDate><category>self-hosting</category><category>privacy</category></item><item><title>AI workflows, minus the hype</title><link>https://thefacko.decortel.de/notes/ai-workflows-without-hype</link><guid isPermaLink="true">https://thefacko.decortel.de/notes/ai-workflows-without-hype</guid><description>Treating a language model as a junior collaborator with no memory and occasional confidence problems has been more useful than treating it as an oracle. It drafts, it doesn&apos;t decide.

The workflows that stuck: first-pass summarization, boilerplate generation, and rubber-duck debugging. The ones that didn&apos;t: anything requiring the model to know something true about the world today.</description><pubDate>Fri, 10 Apr 2026 00:00:00 GMT</pubDate><category>ai</category><category>workflows</category></item><item><title>Digital hygiene, revisited</title><link>https://thefacko.decortel.de/notes/digital-hygiene</link><guid isPermaLink="true">https://thefacko.decortel.de/notes/digital-hygiene</guid><description>Rotated credentials, pruned OAuth grants, and read through a year of third-party app permissions I&apos;d forgotten I&apos;d approved. Half of them belonged to services that no longer exist.

Hygiene work is unglamorous and produces no artifact worth showing anyone. It only ever prevents things — which is exactly why it gets skipped until it doesn&apos;t.</description><pubDate>Sun, 22 Mar 2026 00:00:00 GMT</pubDate><category>privacy</category><category>hygiene</category></item></channel></rss>