Awesome, thanks for the detailed answer!

I just wish they made toddler clothes in my size.

Do you still start in 1st? Do you skip gears?

Hopefully you can publish in an open-access journal — if not it would be great if you could share an arXiv preprint :)

I’d say it gets a little different with command line utilities — maybe “utility” is the appropriate term here, but I’d call something like grep a program, not an application (again — “utility” also works).

To be sure, grep is extremely powerful, but its scope is limited.

Physics is like sex: sure, it may give some practical results, but that’s not why we do it.

— Richard P. Feynman

I think the same is true for a lot of folks and self hosting. Sure, having data in our own hands is great, and yes avoiding vendor lock-in is nice. But at the end of the day, it’s nice to have computers seem “fun” again.

At least, that’s my perspective.

Whatever you decide for your laptop, I’m a proponent of a barebones off-site setup if you’re trying for 3-2-1 backup or similar.

I use a raspberry pi 3 with a single HD (ZFS) retaining some number of daily/weekly/monthly snapshots. Daily rsync, everything over WireGuard+VPS (TailScale would work too).

from stdlib.h import cout

Wait this looks wrong, shit…

Anything can use it, but I think by convention it’s used for http on a non-privileged port.

Same — rsync to a pi 3 with a (single) ZFS drive at family’s house. Retain some daily/weekly/monthly snapshots.

I have a (free) VPS with static IPv4 which is how I connect everything.

Both the VPS and the remote site have limited network speed (I think 50Mbps for VPS), so the initial sync was done sneakernet (well…“airplane net”). Nightly rsync is no problem bandwidth-wise, and is mostly just any new videos I’ve uploaded to my local Immich instance.

It is “backwards” from some other commands — usually you run copy/rsync/link from source to destination, but with tar the destination (tarball) is specified before the source (directory/files).

That, and the flags not needing dashes always just throws me for a loop.

And the icing on the cake is that I don’t use tar for tarring that often, so I lose all muscle memory (untaring a tgz or tar.bz2 is frequent enough that I can usually get that right at least…).

“…and there are no comments, because it’s Self Documenting™”

Modern bots are bad, but the old school IRC (maybe early Battle.net?) bots… I’m cool making an exception for them if you are.

Fail2ban config can get fairly involved in my experience. I’m probably not doing it the right way, as I wrote a bunch of web server ban rules — anyone trying to access wpadmin gets banned, for instance (I don’t use WordPress, and if I did, it wouldn’t be accessible from my public facing reverse proxy).

I just skimmed my nginx logs and looked for anything funky and put that in a ban rule, basically.

I can only remember this because I initially didn’t learn about xargs — so any time I need to loop over something I tend to use for var in $(cmd) instead of cmd | xargs. It’s more verbose but somewhat more flexible IMHO.

So I run loops a lot on the command line, not just in shell scripts.

Some bulk food stores let you bring your own. You put a sticker on them with the bulk item # and also the dry weight, so it’s a little more work, but then you can put your jars to use!

I think mplayer has an ASCII output mode (VLC, too?), and I believe youtube-dl can output to stdout.

The rest is, as they say, left as an exercise to the reader.

You can turn it off, at least for ext4: https://lwn.net/Articles/784041/

Although you can use case insensitive filesystems with Linux, and case sensitive filesystems with macOS. I believe the case sensitivity is a function of the specific filesystem — but yeah, practically, the root for Linux is always case sensitive, and APFS ain’t is only if you ask it to be ( https://support.apple.com/lv-lv/guide/disk-utility/dsku19ed921c/mac ).

Baking is chemistry, cooking is jazz.