<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Telemetry on VisorCraft News</title><link>https://www.visorcraft.com/news/tags/telemetry/</link><description>Recent content in Telemetry on VisorCraft News</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Tue, 08 Sep 2026 06:00:00 -0500</lastBuildDate><atom:link href="https://www.visorcraft.com/news/tags/telemetry/index.xml" rel="self" type="application/rss+xml"/><item><title>Why We Ship Without Telemetry</title><link>https://www.visorcraft.com/news/2026/09/why-we-ship-without-telemetry/</link><pubDate>Tue, 08 Sep 2026 06:00:00 -0500</pubDate><guid>https://www.visorcraft.com/news/2026/09/why-we-ship-without-telemetry/</guid><description>&lt;p&gt;Somewhere in the last fifteen years the industry decided that shipping software without a phone-home channel was the eccentric choice, and the decision happened so gradually that most teams now add an analytics SDK before they add a settings screen, not because anyone asked for one but because the checklist says so. We looked at that checklist when we started shipping and asked the only question that matters: what would we actually do with the data, and the honest answer was &amp;ldquo;look at a dashboard occasionally and feel informed,&amp;rdquo; which is not a reason to run a surveillance pipe inside somebody else&amp;rsquo;s machine, so every VisorCraft project, the GPL desktop apps and the closed-source MongrelDB alike, ships with no telemetry, no event hooks, no &amp;ldquo;anonymous usage stats,&amp;rdquo; and no opt-out switch, because there is nothing to opt out of.&lt;/p&gt;</description></item></channel></rss>