I shall try that. 🤔

I use k3s with Calico so I can have k8s network policies for each service I’m running.

I use Restic and also use Backrest to have a UI to browse my repos. I would use Backrest for everything, but I’d rather have my backup config completely source controlled.

I have @home and @ subvolumes, with Timeshift taking automated weekly snapshots of @ with all of the system directories, but don’t I bother with @home since that gets backed up in other ways.

I recently setup Mint with btrfs Timeshift, and grub-btrfs to make it more like OpenSUSE. It’s more work to do that with Mint, but I’ve tried customizing other distros to make them more like Mint and have come to the conclusion I just like Mint.

You mean the QA teams a lot of companies laid off because management decided the developers (and now AI) can just write all the automated tests?

Agreed, that’s why comments exist, IMO, but should be used sparingly.

I set a static IP for my Windows partition and block it from internet with my firewall. It’s hostile malware that must be quarantined. My Linux partition has a different IP that is not blocked.

On a related note, I jack up my Mint install a few times a year with nobody to blame but myself. I recently reinstalled it with btrfs, Timeshift with automatic snapshots, and btrfs-grub so I can boot from a snapshot instead of troubleshooting or reinstalling. I realize other distros like openSUSE are more or less setup like this out of the box or offer full immutability, but I like Mint.

Well-structured code with clear naming > comments. For example, a pet peeve of mine is seeing a long function with comments preceding each section of code instead of moving each section into a smaller function with a name that clearly describes what it does. The best comments are no comments.

Discord 😬

Edit:

DuckDuckGo’s AI says this, which sounds interesting if true, though it doesn’t provide a source to confirm:

Chaptarr is an upcoming project that is a heavily revamped fork of Readarr, currently in closed Alpha phase, and aims to improve interoperability with Readarr. You can find more information and updates on its development on GitHub

Yeah, true, maybe not as big of a problem in that case.

Radiation is another challenge for computers in space, so just expecting to stick existing hardware in a space data center won’t work as expected. Massive shielding or more specialized hardware and software will be required like what is described here: https://www.nasa.gov/missions/artemis/clps/nasa-to-test-solution-for-radiation-tolerant-computing-in-space/

Existing hardware might work with a lot of mass for shielding, but as others have already mentioned, the rocket equation.

Here’s a highly relevant excerpt:

computers in space are susceptible to ionizing solar and cosmic radiation. Just one high-energy particle can trigger a so-called “single event effect,” causing minor data errors that lead to cascading malfunctions, system crashes, and permanent damage

I originally thought it was one of my drives in my RAID1 array that was failing, but I noticed copying data was yielding btrfs corruption errors on both drives that could not be fixed with a scrub and I was also getting btrfs corruption errors on the root volume as well. I figured it would be quite an odd coincidence if my main SSD and 2 hard disks all went bad and I happened upon an article talking about how corrupt data can also occur if the RAM is bad. I also ran SMART tests and everything came back with a clean bill of health. So, I installed and booted into Memtester86+ and it immediately started showing errors on the single 16Gi stick I was using. I happened to have a spare stick that was a different brand, and that one passed the memory test with flying colors. After that, all the corruption errors went away and everything has been working perfectly ever since.

I will also say that legacy file systems like ext4 with no checksums wouldn’t even complain about corrupt data. I originally had ext4 on my main drive and at one point thought my OS install went bad, so I reinstalled with btrfs on top of LUKS and saw I was getting corruption errors on the main drive at that point, so it occurred to me that 3 different drives could not have possibly had a hardware failure and something else must be going on. I was also previously using ext4 and mdadm for my RAID1 and migrated it to btrfs a while back. I was previously noticing as far back as a year ago that certain installers, etc. that previously worked no longer worked, which happened infrequently and didn’t really register with me as a potential hardware problem at the time, but I think the RAM was actually progressively going bad for quite a while. btrfs with regular scrubs would’ve made it abundantly clear much sooner that I had files getting corrupted and that something was wrong.

So, I’m quite convinced at this point that RAID is not a backup, even with the abilities of btrfs to self-heal, and simply copying data elsewhere is not a backup, because something like bad RAM in both cases can destroy data during the copying process, whereas older snapshots in the cloud will survive such a hardware failure. Older data backed up that wasn’t coped with faulty RAM may be fine as well, but you’re taking a chance that a recent update may overwrite good data with bad data. I was previously using Rclone for most backups while testing Restic with daily, weekly, and monthly snapshots for a small subset of important data the last few months. After finding some data that was only recoverable in a previous Restic snapshot, I’ve since switched to using Restic exclusively for anything important enough for cloud backups. I was mainly concerned about the space requirements of keeping historical snapshots, and I’m still working on tweaking retention policies and taking separate snapshots of different directories with different retention policies according risk tolerance for each directory I’m backing up. For some things, I think even btrfs local snapshots would suffice with the understanding that it’s to reduce recovery time, but isn’t really a backup . However, any irreplaceable data really needs monthly Restic snapshots in the cloud. I suppose if don’t have something like btrfs scrubs to alert you that you have a problem, even snapshots from months ago may have an unnoticed problem.

Don’t understand the downvotes. This is the type of lesson people have learned from losing data and no sense in learning it the hard way yourself.

TS transpiles to JS, and then when that JS is executed in Deno, Node.js, a Blink browser like Chrome, etc., it gets just in time compiled to native machine code instead of getting interpreted. Hope that helps.

The JavaScript code is compiled to native and is heavily optimized, as opposed to being interpreted.

Having a synced copy elsewhere is not an adequate backup and snapshots are pretty important. I recently had RAM go bad and my most recent backups had corrupt data, but having previous snapshots saved the day.

I had to deal with large JavaScript codebases targeting IE8 back in the day and probably would’ve slapped anyone back then who suggested using JavaScript for everything. I have to say, though, that faster runtimes like v8 and TypeScript have done wonders, and TypeScript nowadays is actually one of my favorite languages.

Maybe they’ll use and contribute to Plasma Bigscreen? Probably not, but I’d love to see Bigscreen get more love.

I can’t see paying more than a few hundred for this form factor. Love my Steam Deck, but for the times when I feel like being treated to a nicer gaming experience, that’s when it’s time to break out the real gaming rig with a 4K screen or a VR headset. With such a small screen, streaming games to the Deck on max settings via Moonlight / Sunshine doesn’t really look that much different than the same game on medium settings running on the Deck, so paying double or triple for a slightly more powerful machine with a slightly better screen doesn’t make a lot of sense for me.