<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Email on VisorCraft News</title><link>https://www.visorcraft.com/news/tags/email/</link><description>Recent content in Email on VisorCraft News</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Tue, 15 Sep 2026 06:00:00 -0500</lastBuildDate><atom:link href="https://www.visorcraft.com/news/tags/email/index.xml" rel="self" type="application/rss+xml"/><item><title>Self-Hosting Your Terminal and Your Inbox</title><link>https://www.visorcraft.com/news/2026/09/self-hosting-your-terminal-and-your-inbox/</link><pubDate>Tue, 15 Sep 2026 06:00:00 -0500</pubDate><guid>https://www.visorcraft.com/news/2026/09/self-hosting-your-terminal-and-your-inbox/</guid><description>&lt;p&gt;Most of what people call &amp;ldquo;moving to the cloud&amp;rdquo; is really &amp;ldquo;moving to someone else&amp;rsquo;s convenience layer,&amp;rdquo; and the pattern repeats across every category of software you touch daily: the terminal session lives on a hosted dev box you rent by the hour, the inbox lives in a web UI where the provider reads the same screen you do, and in both cases the trade was never negotiated, it just happened one default at a time, because the alternative used to mean running your own server and that phrase has been scaring people off since the first shared hosting ad. The strange part, the part worth writing about, is that the server work stopped being the hard part years ago, and what actually keeps people on the hosted version now is a pile of small papercuts, the missing right-click, the awkward mobile client, the one feature the local tool never quite had, so the way you take a piece of your digital life back is not a migration plan, it is finding those papercuts and deleting them one at a time.&lt;/p&gt;</description></item></channel></rss>