Recent releases of Android famously ignore/bypass any local (i.e., self-hosted) nameserver passed along by DHCP or specified in a wifi profile, in favor of Google's own public nameservers. The only other option is to enable "Private DNS" (DNS over HTTPS, or DoH) in the global network settings for your devices. The stated reason for this are easy to understand: to avoid compromising security or privacy when connecting to random wifi networks. But we all know there's more to it than that. The most charitable explanation would be that Google (and others, including Mozilla) is fixated on getting everyone on DoH, even at the cost of frustrating we few peasants who want to run our own local DNS. Let them eat cake.

There are a few alternatives available to those of us who would like to address local hosts and services on our home networks by name, rather than IP address:

1. Apple mDNS. Like Microsoft's legacy WINS, mDNS still isn't very reliable and won't work for hosts and device

WARNING: Mozilla has a habit of changing the order and content of Firefox settings on different platforms and between versions (they seem to especially enjoy stripping options out of their mobile versions). Those changes may not be reflected here (I already have a day job).

The following procedure was tested with Firefox 136 (64-bit) on Ubuntu 22.04 LTS running the default Gnome desktop.

For Ubuntu Desktop I use the binary installer (https://www.mozilla.org/en-US/firefox/new/) and basically follow the official documentation for system installation [1]. To allow automatic updates I set permissions so my user has write permissions over /opt/firefox (on my systems I'm a member of the local staff group, so I do ```sudo chown -R root:staff /opt/fir

This is my public key:

-----BEGIN PGP PUBLIC KEY BLOCK-----

mQENBFkd45EBCADEL7qh/BTL3IjjBuZX1orf5J8QnCYbqFN63/z8YSUxPN1vfao0
+ZU9xKEbkfdbNZl7GfMz5wyOr8tXU13orbaaoL9ZbPTCG/B9fy1BFgo3d/5JExd2
x7gveSCVpAEBPFpTaDjPjSZEdXAUCqYLEBLLDipGNZKxkbWZYLeDzOoBbL8P9Mob

Alexandre Lotte, the author of icsp describes it as a "Small, fast and simple command-line tool to conver calendar exports (.ics files) into TSV/CSV files for easy analysis and usage in broader use-cases."

And so it is.

I had accidentally imported a holiday calendar into my default Proton Calendar, when I realized two very horrible things: (1) I had no backup; and (2) no one really provides tools for removing entries from calendars in bulk. Later, I would add "Proton Calendar doesn't have a versioning system". But then, no one else does either.

I was screwed.

A few minutes (OK, about a half hour) of searching the Internet, and I found icsp: which turned out to be everything its author wrote that it is.

NOTE: This was written while experimenting with using podman in lieu of docker. But please be aware that not all docker solutions are compatible with podman, and some may still require root even under podman.

Going rootless is one of the main reasons for switching to podman. But if you're running shared services on server for internal users and don't want a separate account for each app, creating a special (non-privileged) account for all pods may be the answer.

This work was done on Ubuntu 22.04 LTS using the shipping Ubuntu package for podman (podman-3.4.4+ds1-1ubuntu1).

Install podman and enable the podman.socket service (I'm using the version in my distro's official repository):

NOTE: This was written while I was experimenting with using podman in lieu of docker, something I'm now looking at again. Not all docker images work with podman, so be prepared to struggle with the system and to engage in many fruitless Internet searches.

OK, so who knew podman containers won't automatically start on reboot? Yeah. Me neither.

Found out after a family member complained about getting a 500 error when trying to reach a PiGallery2 instance I had set up on the home server.

Fixing this is easy, as detailed in Pratham Patel's "How to Autostart Podman Containers?" over on Linux Handbook: A systemd servic

Running Ubuntu 22.04 LTS with Ubuntu Desktop on X11.

After setting dock (dash to dock extension) to auto-hide, it won't reappear if any app is full screen.

Turn off "require-pressure-to-show" in dconf settings for dock.

1. Open dconf-editor and go to org > gnome > shell > exensions > dash-to-dock

UPDATE: According to the Ubuntu bug history cited below, this problem was fixed with an update of ubuntu-drivers-common on September 10, 2024. After removing the workaround udev rule and verifying the package was updated on my system, I confirmed that the troublesome behavior didn't return for me. That said, at least one other person has advised that they're still experiencing it even with the workaround.

Got bit by Ubuntu Linux bug #2060268 on the latest kernel update for 22.04 LTS (6.8.0-40-generic).

As in the bug report (and many forum posts across the Internet) this appears to be due to a collision between the simpledrm kernel module and NVIDIA drivers. The symptom is a nonexistent display device being assigned as card0. The practical effect is to throw off any previous configuration of the display system (display 1 becoming display 2, display 2 becoming display 3). As a result, customization

My preferred settings for Google Chrome on Android:

Updated for version 127.0.6533.64

• DO NOT turn on sync, or Disable

• Search engine: Your Favorite Search Engine
• Google Password Manager: Settings - Disable all

Following are my preferred settings for Google Chrome desktop (Updated for version 127.0.6533.88):

• User Profile: No change
• Sync and Google Services: Disable all

• Google Password Manager: Settings - Disable all