Updates & corrections
Technical articles can outlive the software version, the hardware or my first understanding of the problem. This page records substantial corrections and changes to a conclusion. It is not a diary of every paragraph added or comma moved.
A useful correction should say what was wrong, what the better evidence shows and whether the practical advice changes. Quietly polishing a mistaken claim may make a page prettier, but it does not help someone who relied on the earlier version.
Revised the VPN, monitoring and security articles to make illustrative scenarios unmistakable. Removed unnecessary equipment specifics from the supporting pages and expanded the background on why someone would choose a NAS, a media platform, managed networking or a monitoring tool. The site should distinguish a documented personal result from an explanation of how a system generally works.
What belongs here
If a new test changes the diagnosis, a product behaves differently after an update or a claim was too broad for the evidence, I want that recorded. A typo correction does not need an announcement. A revised recommendation does.
The distinction matters on a site about troubleshooting: someone may return months later expecting the same advice. A date and a short explanation let them decide whether the change affects what they plan to do.
How to read older notes
An account of what happened in my home can show a useful way to reason through a failure. It cannot prove that another person's hardware will produce the same outcome. Product updates, different playback devices and different network conditions can all change the result.
That is why I try to include the limits of each conclusion. If I discover a better explanation, the article should change along with this log. The internet has enough confident old instructions without my help.