1: I’m assuming (hoping) this wouldn’t be a full wipe and start over? It should just upgrade right?

Yes, you can upgrade in-place. If I recall correctly, you just have to change the release channel from LTS to non-LTS in the Sources app, then trigger an update (I don’t quite remember how to do)

2: Do I need to do the whole USB route, and if so is there an option to keep everything (I’m hoping, I put a LOT of work into this so far and I don’t remember if that was an option on first install).

No, as I said above. But it’s always a good idea to have backups if you ever need to wipe and re-install.

3: I remember a few apps I installed were specific to Noble, will this break those apps?

Hard to be 100% sure without knowing which apps and how they were installed, but most likely yes as their dependencies might no longer be available on Plucky.

4: It seems like there should be an option to upgrade from the desktop, but I don’t have that option. If I run plasma-distro-release-notifier I should get an update notification right? In which case I can just say “hell yeah!” and it’ll do its thing?

Refer to my first answer

deleted by creator

Considering that my outlook on the future is grim, I would say that I do, yes.

But on the other hand, when I look at my 3yo nephew and how my sister raises him, teaching him inclusiveness, limiting his exposure to screens as much as possible, and encouraging him to draw and go outdoors, it gives me some hope that maybe not all is lost.

What’s your issue exactly?

Personally, I set up Caddy with subdomains like radarr.local.example.tld, added a DNS entry on my domain so that *.local.example.tld points to the local IP of Caddy, then followed this guide so that Caddy issues TLS certificates using the DNS challenge (since the subdomains don’t point to anything accessible from Internet) along with the caddy-docker-proxy plug-in to easily manage upstreams.

Don’t you have any off-site backup? It would help keeping some peace of mind knowing you have a copy somewhere else.

In my experience with unbound, it tends to return expired records in the hope that they are still valid, causing issues with services hosted in the cloud, where IP addresses rotate regularly. What I did was update the serve-expired-ttl setting in unbound’s configuration to 3 hours (down from the default 24h)

It’s a little far-fetched to claim that including full support for Qi 2 on the Pixel 10 is akin to new features heralded by Nexus devices.