<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Macrogol's Blog</title><link>https://blog.macrogol.xyz/</link><description>Recent content on Macrogol's Blog</description><generator>Hugo -- 0.162.1</generator><language>en</language><copyright>CC BY-SA 4.0</copyright><lastBuildDate>Wed, 02 Sep 2026 10:03:14 +0200</lastBuildDate><atom:link href="https://blog.macrogol.xyz/index.xml" rel="self" type="application/rss+xml"/><item><title>How to Fake Someone Else's Blog Under a Different Name</title><link>https://blog.macrogol.xyz/en/faking-your-own-blog/</link><pubDate>Tue, 01 Sep 2026 00:00:00 +0000</pubDate><guid>https://blog.macrogol.xyz/en/faking-your-own-blog/</guid><description>&lt;p&gt;Suppose you want to run someone else&amp;rsquo;s blog.
Not steal it, exactly.
Just quietly continue it under a name that is legally distinct enough that nobody sends an email.
Keep the posts, keep the opinions about &lt;code&gt;inotify&lt;/code&gt;, keep the layout override you never finished.
Only the name on the door changes.&lt;/p&gt;
&lt;p&gt;This is a short guide.
The someone else, in my case, is me.&lt;/p&gt;
&lt;h2 id="step-1-pick-a-name-that-is-close-but-not-too-close"&gt;Step 1: pick a name that is close, but not too close&lt;/h2&gt;
&lt;p&gt;The new name has to clear a few bars.
It must be pronounceable by a human who is not currently looking at it.
It must survive a domain registrar without a hyphen.
It must not already be a Mastodon instance run by someone with more free time and more anger than you.&lt;/p&gt;</description></item><item><title>Laptop archeology – or – how to install NixOS 24.11 on a 25 year old laptop</title><link>https://blog.macrogol.xyz/en/nixos-on-fossils/</link><pubDate>Wed, 15 Jan 2025 00:00:00 +0000</pubDate><guid>https://blog.macrogol.xyz/en/nixos-on-fossils/</guid><description>&lt;p&gt;Earlier this year I brought an old laptop to my home my grandfather once gave.
It is a relict from roughly 1999, with which I&amp;rsquo;ve already played around some nine years ago.&lt;/p&gt;
&lt;p&gt;Prior to &lt;a href="https://events.ccc.de/congress/2024/infos/startpage.html"&gt;38C3&lt;/a&gt; I had the idea to bring it to the congress so people could mess around with it.
In the end, I was the one messing around with it, fighting to get some operating systems installed on this poor thing.&lt;/p&gt;</description></item><item><title>Nextcloud and inotify limits</title><link>https://blog.macrogol.xyz/en/nextcloud-inotify/</link><pubDate>Sun, 24 Mar 2024 00:00:00 +0000</pubDate><guid>https://blog.macrogol.xyz/en/nextcloud-inotify/</guid><description>&lt;p&gt;Since some weeks I got a strange error message from the Nextcloud client on startup: &lt;code&gt;Changes in synchronized folders could not be tracked reliably&lt;/code&gt;.
At first, I ignored it, but I noticed Nextcloud wouldn&amp;rsquo;t sync local changes reliably to the server.
After I lost a git commit (yes, I sync some git repos over Nextcloud), I took the issue seriously.&lt;/p&gt;
&lt;p&gt;I knew this was related to a Linux feature called &lt;code&gt;inotify&lt;/code&gt;.
With it, you can monitor files or directories and get notified by the kernel whenever the selected events happen on those elements.
I searched the Nextcloud client and nixpkgs changelogs, but didn&amp;rsquo;t find anything related to my problem.
Then I searched in the Nextcloud client source code and &lt;a href="https://github.com/nextcloud/desktop/blob/v3.12.2/src/gui/folder.cpp#L1495"&gt;found&lt;/a&gt; the dialog I saw.
However, that didn&amp;rsquo;t help me either.&lt;/p&gt;</description></item><item><title>Increasing Privacy in Mail Clients</title><link>https://blog.macrogol.xyz/en/mail-privacy/</link><pubDate>Sun, 10 Sep 2023 00:00:00 +0000</pubDate><guid>https://blog.macrogol.xyz/en/mail-privacy/</guid><description>&lt;p&gt;Mail clients are notorious for sending information not really required for mail conversations.
They leak their identity and version number, sometimes even the operating system in &lt;code&gt;User-Agent&lt;/code&gt; and &lt;code&gt;X-Mailer&lt;/code&gt; headers.
They leak the locally set time zone in the &lt;code&gt;Date&lt;/code&gt; header.
And sometimes they leak the private IP addresses during mail sending.&lt;/p&gt;
&lt;p&gt;Here I document some settings to hide this information in my preferred mail clients.
&lt;strong&gt;Note:&lt;/strong&gt; Hiding this metadata might not be enough to fully disguise your choice of mail clients.
The ordering of mail headers was not tackled, behavior with attachments varies equally high and other details disclose the mail client identity.&lt;/p&gt;</description></item><item><title>Hosting a Mail Server at Home</title><link>https://blog.macrogol.xyz/en/mail-server-at-home/</link><pubDate>Sun, 14 May 2023 00:00:00 +0000</pubDate><guid>https://blog.macrogol.xyz/en/mail-server-at-home/</guid><description>&lt;p&gt;I&amp;rsquo;m using &lt;a href="https://nixos.org/"&gt;NixOS&lt;/a&gt; since over a year for most of my server stuff and I&amp;rsquo;m loving it.
One of the missing services was my email setup, originally deployed on Debian 10, later upgraded to Debian 11.
I followed a &lt;a href="https://www.c0ffee.net/blog/mail-server-guide"&gt;setup guide&lt;/a&gt; and was quite happy, tweaking it over the years to my needs.
Roughly, the software stack consists of Postfix as the &lt;a href="https://en.wikipedia.org/wiki/Message_transfer_agent"&gt;MTA&lt;/a&gt; (&amp;ldquo;SMTP server&amp;rdquo;), Dovecot as the &lt;a href="https://en.wikipedia.org/wiki/Message_delivery_agent"&gt;MDA&lt;/a&gt; (&amp;ldquo;IMAP server&amp;rdquo;) and rspamd including its requirement, redis, for spam protection and SPF/DKIM/DMARC verification as well as DKIM signing for outgoing mail.
I avoided a webmail service to keep things simple and I already use standard mail clients across my personal devices anyway.&lt;/p&gt;</description></item></channel></rss>