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).
Others mentioned virtualization — I have had issues with COW filesystems (btrfs), as COW does not always play nicely with VM drives (extreme fragmentation and very poor performance).
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.
Maybe there’s some interplay between amd64 and x64 architectures.
AMD64 and x64 are the same thing. Do you mean AMD64 and x86? There is definitely interplay there, as AMD64 implements the x86-32 instruction set.
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…).
Interesting, TIL — thanks!
Books has become e-books.
To some extent — but have you been to a hip bookstore recently? They exist, and are very much alive.
Cashless requires power all the way from PoS to wherever the servers live.
Edit: see below
You mentioned ham radio — definitely fun! It’s a process to get into it though, as you need to study/pass an exam, and then you need a radio. Radios range from cheap ($25 or so) in the VHF/UHF (“walkie talkie”-style) to more expensive for an HF rig ($1000 range for 100W HF). If you want to get into low power (“QRP”) it can be much cheaper. You also need a fair amount of space for a good antenna setup…
There are tons of different communication modes, some without a computer and, like you mentioned, some that use computers. wsjtx and fldigi are popular programs.
Good luck!
“…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.
A lot of non-graphical utilities — basically the *NIX coreutils, plus stuff like rsync, ssh, compression/archival tools (tar, gzip, bzip2, etc.), grep, and the like. Git also comes to mind.
I think part of this is that the UNIX philosophy is “developer friendly” — tell a good dev they need to make a compression utility that follows this protocol, and they will make a compression utility that follows the protocol.
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.
Judging by the camera angle, OP may have been today years old when they learned this as well (I learned it well into my 30s, too).
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.
Hopefully you can publish in an open-access journal — if not it would be great if you could share an arXiv preprint :)