Don’t “try” to fall asleep (it is involuntary), just make the safe & comfortable feelings so your mind knows it is okay to fall asleep.

Because sometimes I would rather things be slow than blurry, and my workstation monitor is >1080p.

We really need to get past the 1080p barrier. AFAICS there is one economical KVM solution for that, and several costly enterprise kits. Surely the actual hardware cost/difference per-unit would be quite small now?

Maybe something to do with vapor pressure?

There’s a good idea and some real potential here, but it didn’t quite land for me.

Sounds like you might want the “-AlwaysShared” option of Xvnc. Ref: https://tigervnc.org/doc/Xvnc.html

Why has nobody mentioned package managers? I can’t be the only one who cares about that…

3am

Flight of the bumblebee.

Another missed opportunity to bring back the headphone jack.

A twist on Oliver Twist with Churro twists.

NGL… I kinda want to tell someone to reduce their beanage without any context, and walk away.

Well, if they are neatly hung and countable, I have too many. If they are in a wash basin dissolved in acid (akin to refried beans), then maybe I have too much?

tachypsychia? bradypsychia?

So instead of keeping a phone roughly the size of a pocket in your pocket, they expect us to want to put “bricks” in our pockets that unfold into phones.

Sounds easy. Well, straight-forward, at least. For such things i use “zim” (a desktop wiki). Tangibles (like a motherboard) get a page that contains “links” to all the variables and components you want to track/index (the actual target pages don’t actually have to exist). I would the drop that page in a hierarchy of containers (building, room, box, etc).

Organized this way, you can locate a tangible using any of the backlinks (like, by component), and reference the page path if you actually need to lay hands on it in the future. There is also a search feature, but i find myself using the backlinks for more frequently.

Also, by organizing the pages into a container hierarchy, it makes it easy to shift things around when physical things move (as all the sub-pages come along for the ride).

You seem to have created a pocket universe where it is both night and day simulatenously.

For love as a standalone word, “value” is the most drop-in-compatible word. To say “i love you” is to say “i value you”.

The form of “in love” is a far greater mystery to me, and i usually just consider the speaker to mean something like “obsessed” or “infatuated”.

Doctor: You must be allergic, what did you eat?

Me: It’s proprietary.

TrueNAS scale helps a lot, as it makes many popular apps just a few clicks away. Or for more power-users, stuff like the linux cockpit also really helps.

To directly answer your questions…

• In the event of DB corruption (which hasn’t happened to me yet) I would probably rollback that app to the previous snapshot. I suspect that TrueNAS having ZFS as an underlayment may help in this regard, as it actually detects bitrot and bitflips, which may be the underlying cause of such corruption.
• In the case where a device breaks… if it’s a hard drive that broke, I just pop in a new one and add it to the degraded mirror set. If it’s “something else” that broke, my plan is to pop one of the mirror shards into a spare PoS computer (as truenas scale runs on common x86 hardware) and deal with the ugly-factor until I repair or replace the bigger issue.
• The only way to defend against a cloud provider is replication, so plan accordingly if that is a concern.
• If by “sync’d confidentially” you mean encrypted in transit, I’m pretty sure that TrueNAS has built in replication over SSH. If you meant TNO, then you probably want to build your setup over a cryfs filesystem so no cleartext bits hit the cloud, although on second thought… it’s not really meant for multi-master synchronization… my case just happens to fit it (only one device writes)… so there is probably a better choice for this.
• Setup is a hassle? Yes… just be sure that you invest that hassle into something permanent, if not something like a TrueNAS configuration (where the config gets carried along for the ride with the data) then maybe something like ansible scripts (which is machine-readable documentation). Depending on your organization skills, even hand-written notes or making your own “meta” software packages (with only dependencies & install scripts) might work. What you don’t want to do is manually tweak a linux install, and then forget what is “special” about that server or what is relying on it.
• How safe is my setup? Depends… I still need to start rotating a mirror shard as an offsite backup, so not very robust against a site disaster; Security-wise… I’ve got a lot of private bits, and it works for my needs… as far as I know :)
• Still enthusiastic? I try to see everything as both temporary and a work-in-progress. This can be good in ways because nothing has to be perfect, but can be bad in ways that my setup at any given time is an ugly amalgamation of different experimental ideas that may or may not survive the next “iteration”. For example, I still have centos 7 & python 2 stuff that needs to be migrated or obsoleted.