

Hopefully you can publish in an open-access journal — if not it would be great if you could share an arXiv preprint :)
Hopefully you can publish in an open-access journal — if not it would be great if you could share an arXiv preprint :)
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).
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.
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
My comment from another thread: https://startrek.website/comment/16491624
tl;dr: tiny production, would be astonished if they got $6k out of it, and that’s not counting time, props, transportation, etc.
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!
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.
Newer macOS is not Unix certified.
It’s UNIX 03 compliant https://en.m.wikipedia.org/wiki/Single_UNIX_Specification
One or two Linux distros were (are?) UNIX certified, though.
Haha yeah that was the counter example I was thinking of. I agree completely — you could make a Gentoo from source beginner distro, and I think you could make it reasonably “idiot proof,” but it would still be a bad user experience most likely (too much time spent compiling).
If your distro can’t be forked into a “beginner distro” then it’s fundamentally flawed IMHO.
To be clear, I’ve used Arch as my daily drivers for a while, and while it’s not the best fit for my needs (I use Debian mostly), there’s nothing that I experienced that was incompatible with a “beginner” distro.
You can also drop cache for debugging by running something like echo 3 | sudo tee /proc/sys/vm/drop-caches
But remember that the kernel knows best — this RAM will automatically be freed up when needed and you should never run this except for debugging (or maybe benchmarking).
I switched from raspberry pi and orange pi to a cheap Intel NUC, and I think it’s just a much nicer experience.
The pi is great fun, but the HW transcoding on a NUC “just works,” and the SSD and 16GB RAM opens a lot of doors. My N100 NUC was less than $150, and it included everything (case, power supply, 500GB SSD).
My pi found new life as an off-site backup: attach a big HDD, set up WireGuard, and have a cronjob do daily rsync and snapshots. I have it set up at in-laws, and it works great.
Can you explain the Ethernet requirement more? Was that just that the computer didn’t have WiFi, or was it set up such that only the wired interface worked with their VPN, or…?
Can you explain your travel router situation? Did you use the travel router to access WiFi and provide an Ethernet port for the computer (I think this is called “WISP mode”)? Or was this an 4G/5G router?
In any event, at least on Android you can connect to WiFi and tether to a computer over USB. It’s very useful for setting up a computer without WiFi drivers, as Linux will almost always recognize the shared Internet (so, it’s functionally a USB wifi dongle with very good driver support).