<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Privacy on Erik&#39;s Blog</title>
    <link>https://blog.mtnlyons.dev/tags/privacy/</link>
    <description>Recent content in Privacy on Erik&#39;s Blog</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 27 Oct 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://blog.mtnlyons.dev/tags/privacy/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Hosting a Hugo Blog on Cloudflare Pages with a Custom Domain</title>
      <link>https://blog.mtnlyons.dev/posts/hosting-hugo-blog-cloudflare-pages/</link>
      <pubDate>Tue, 27 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://blog.mtnlyons.dev/posts/hosting-hugo-blog-cloudflare-pages/</guid>
      <description>&lt;h2 id=&#34;the-problem&#34;&gt;The Problem&lt;/h2&gt; &lt;p&gt;I run my blog as a static Hugo site and initially hosted it on a self-hosted Forgejo instance behind Tailscale. I covered that setup in &lt;a href=&#34;https://blog.mtnlyons.dev/posts/setup-blog/&#34;&gt;my earlier post about setting up the blog with Forgejo and Tailscale&lt;/a&gt; . That worked fine for tailnet-only access, but I wanted to make the blog publicly available without exposing my home network to the internet, no DDoS vectors, no port forwarding, no risk of someone finding an open SSH or web service on my LAN.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Backing Up Desktop Files with Proton Drive CLI and Cron</title>
      <link>https://blog.mtnlyons.dev/posts/backing-up-desktop-files-with-proton-drive-cli/</link>
      <pubDate>Mon, 26 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://blog.mtnlyons.dev/posts/backing-up-desktop-files-with-proton-drive-cli/</guid>
      <description>&lt;h2 id=&#34;why-not-the-desktop-app&#34;&gt;Why Not the Desktop App?&lt;/h2&gt; &lt;p&gt;Proton Drive offers a desktop sync application that keeps files in real-time sync between your machine and the cloud. It works well for many people, but I prefer the CLI approach for one reason: &lt;strong&gt;control&lt;/strong&gt;.&lt;/p&gt;&#xA;&lt;p&gt;With the CLI, I decide exactly &lt;em&gt;what&lt;/em&gt; gets backed up, &lt;em&gt;when&lt;/em&gt;, and &lt;em&gt;how&lt;/em&gt;. Combined with cron jobs, this gives me predictable, auditable backups without background processes eating resources or silently overwriting things I didn&amp;rsquo;t intend.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
