The insidious urge to fix what ain't broke has arisen. I'll probably follow the official documentation, unless someone has a better suggestion.
I'm not running anything unusual and I haven't done much, if any, "customization". I update packages maybe a couple of times a week, so they're current.
Should I go ahead and put myself through this now, or wait until support is dropped and I'm forced?

The design is pretty straight forward: a V notch bisected by a straightedge, but aligning it during glue up was tricky. If I make another I'll think about fitting the straightedge into a rabbet or something so it's not sliding around.

Used up a perfect piece of scrap, too. Now I'll have to make a glueup for the body of the righty version.
I'm going to leave the lefty 90% finished and do the final 10% if I ever find a need for it.

The base is dovetailed at the corners and the uprights are lapped in. I have to complicate everything.

edit:
I needed to edit ~/.config/qui/config.toml and bind the host to "0.0.0.0"

I'm running Debian (12) and I just installed qui, a single binary dropped in /usr/local/bin. When I fire it up, I can access the web interface on the local machine via localhost:7476, but I cannot access it over the LAN via the server's IP. Firefox just says 'Unable to connect'.
I can access a dozen other services over the LAN, and as far as I'm aware there's no firewall enabled by default.
What gives?

The author notes that players generally do not finish games and suggests that designing in terms of gameplay loops leads to a certain kind of boring and predictable experience. They suggest that the modern medium of games is much more flexible and capable of more variety.

It's made of cherry because that's what I have a lot of now.
The shape is based on an Atkins Perfection template I have, but I had to cut it up and move things around to account for the unusual hole pattern.