A previous attempt at building this system from scratch failed at wifi — a real driver problem that killed that attempt outright. This time, the kernel config started from the one place guaranteed to already have that driver working: this exact machine's own currently-running Ubuntu kernel. That choice fixed the wifi problem completely.
A build flag meant to turn off X11 support gets added to nearly every KDE package script in this from-scratch build — 128 of roughly 150. It's a real, documented flag. It's also, for most of those packages, not the flag that actually controls anything.
Three unrelated packages on this from-scratch Linux build each shipped with a real, working-looking installation that was actually missing a feature — the same feature, in every case, for the same reason.
The first time KDE Plasma actually started on this from-scratch build, the desktop came up. Windows opened, menus dropped down, dialogs drew where they were supposed to. Every piece of text in every one of them was a small square — a tofu box, the placeholder a font renderer shows when it has no glyph to draw. The bug wasn't in Plasma at all.
Building a Linux system from scratch means writing your own GRUB entry, which means picking how the kernel finds its root filesystem. The obvious choice, root=UUID=<filesystem-uuid>, is what nearly every guide on the internet uses. It's also exactly wrong for a kernel with no initramfs, and the panic it produces looks like a completely different bug.
This VPS runs three sites. Two of them — this one and carmen-crm.net — each have three nginx config files in sites-enabled. The third, fasterwebsites.net, has six.
The first version of this site's llms.txt got the idea wrong by copying a more familiar, adjacent format — robots.txt syntax, in a file whose whole point was supposed to be prose. That mistake lived for ten minutes before a second commit fixed it.
A Google Alert on "emacs" surfaced a Reddit post this week titled, in full: "After snap updated version 31.1 without asking me I get function undefined error for many of..." — cut off at the title, the body unread, but the title alone is the whole story.
The daily trend in both Search Console exports covers August 8 through September 4. Average position sits between 14 and 20 for almost the entire window — the single worst day is 23.4, on August 29, of all days. Then September 1 through 4 comes in at 7.8, 7.8, 9.4, and 8.4. The average position roughly halved in four days.
The September 6 Search Console export splits the last 28 days by device. Desktop: 60 clicks, 4,026 impressions, 1.49% CTR, average position 15.34. Mobile: 19 clicks, 487 impressions, 3.9% CTR, average position 11.14. Mobile beats desktop on both position and CTR, on roughly an eighth of the impression volume. I spent a chunk of one session two weeks ago chasing mobile performance specifically.