In my head it was definitely Cave.
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).
“Can you hold it” was meant as “abstain from pooping for just a little longer,” but was instead interpreted as, “poop, and then hold the poop in your hands.”
If you lose power, you can use one of these cables to power your house (or at least, the part of your house on that phase).
This is not how you should do this, but it can work. It is not a good idea (possibly illegal?).
Hopefully you can publish in an open-access journal — if not it would be great if you could share an arXiv preprint :)
You said that no one…
I don’t think that was the parent commenter though…
You experience the passage of time as ever increasing in speed, and before long the universe has died, leaving you — immortal and sentient — alone in the cold, dead cosmos, for eternity.
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.
Sounds like the opposite reasoning may have some truth:
“Cardinal George of Chicago, of happy memory, was one of my great mentors, and he said: ‘Look, until America goes into political decline, there won’t be an American pope.’ And his point was, if America is kind of running the world politically, culturally, economically, they don’t want America running the world religiously. So, I think there’s some truth to that, that we’re such a superpower and so dominant, they don’t wanna give us, also, control over the church.”
Nah just give them the .tex
source and let them deal with it.
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…).
It’s a pretty standard bandwidth/latency tradeoff in my view: email is high bandwidth (it’s in writing, you can re-read, etc.), whereas phone is low latency (several back-and-forth explanations can happen in seconds). Each has its place.
If social anxiety is a factor, that’s a perfectly valid, but separate, issue.