Bonus points: use non-qwerty keyboard for added obfuscation (but keep the qwerty key caps of course).

It’s nerf or and nuttin’

FTFY

I hope I’m wrong! I’d definitely consider buying some — hopefully you can report back with results. If they’re slower than advertised but have the actual capacity that’d still be awesome!

This looks like it might be it:

https://www.tomshardware.com/pc-components/ssds/buyer-beware-fake-samsung-1080-pro-4tb-ssd-promising-unbelievable-158-gbs-speeds-for-dollar43-is-too-good-to-be-true

The drive doesn’t provide 4TB of storage either, considering the single NAND chip. That means if you were to attempt to write that much data to the SSD, at some point it would either fail or start overwriting existing data.

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.

Hah not at all! I need to remind myself to hydrate and fuel constantly if I’m doing any sort of exercise.

If you’re exercising and you drink because you’re thirsty, you probably waited too long to hydrate.

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.

That’s what I heard about Chevy’s, too.

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.

I mean, vigorous physical exercise is one of the most mentally relaxing activities, in a way (at least for me). Go for a 100km bike ride in hilly terrain, push yourself on the climbs, and just kind of let your mind wander. It’s not edible-and-David-Attenborough relaxing, but it is relaxing in its own way.

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…).

At work on a slack it just means “I’m watching this discussion.”

To each their own though? I can’t imagine why anyone would want something other than i3 (or similar), because almost by definition the DE is not the program I fired up my computer to interact with, and i3 “gets out of the way better” than most others in my experience.

But…that’s just my use case. It’s a horrible UX for most people, just happens to work well for me.

I feel old…when I was learning how to run Linux I started with an old 386 (maybe 486?) my dad wasn’t using. I think it had 32MB RAM, which was fancy for those machines.

We had dial up at the time, so only one machine could be on the Internet. So, I set up a modem on the x86, plugged into an Ethernet hub (switch?), and learned enough ipchains (this was before iptables) to share a connection. It also ran Samba, an AFP server, and probably FTP and HTTP (just for local access) — but it worked for filesharing.

It could also run MP3 streaming software which amused me because the machine itself was too slow to decode MP3 (but that’s not necessary to stream).