oscardejarjayes

restic to a local server and to cloud storage. it varies by device, but usually just everything in /home/. The rest of the operating system should be reproducible, whether through images, ansible, nix, or guix, given the information in /home/.

scheduling is done through systemd, usually (or the non-systemd equivalent). I use BackBlaze now, but I switch around occasionally. restic has policy based snapshot removal, and a prune option.

It doesn't seem like there's any enforcement method, just "social influence".

In other words, they made a scoreboard.

You could try using Hashicorp's Packer to generate images repeatably (usually more meant for cloud images though). Or NixOS (like others have mention), or Guix (like NixOS, but better in some ways, worse in others). You could make it an Ansible playbook, which would let you both make configured images, and just configure machines that already have an OS.

I do something similar with archiso, fwiw, but that only works with Arch Linux.

Would you want to change your distribution, or just keep Debian with some tools to automate?

I'm on the web on computer, and I see the alt text when I hover over the image.

Annas archive exists

Make a plugin to a non-vim editor that properly emulates the vim experience, with the non-vim GUI.

Or, if that doesn't work well enough, fork them.

Failing that, you could just accept your fate. I love my neovim install.

Exciting! Sort of interestingly, I never dual booted or anything, I just jumped straight to Linux.

Honestly, it's really not that bad. Linux has come a long way since I started out, and while I usually make it harder for myself than it needs to be, I've seen young middle schoolers installing and using Linux, I've seen retired professional musicians with no technical background install and use Linux. Especially with all these new fancy atomic desktops, like Silverblue, Bazzite, and Kinoite. Admittedly, I have managed to break a Kinoite installation (doing stuff I probably shouldn't have been doing), but fixing it felt magical. Just roll back to when it wasn't borked, then update it.

I did a lot of not so nice things to that installation (it was a bit of a test, to see how fragile it was), and it's still running now!

imo you should, before nuking your account, make a backup of everything you said, and maybe some of the surrounding context, and then host it on a website. Just make sure your website is all properly indexed, and shows up when you use the right search terms. I have no idea what the legality of such an undertaking would be, but it would be cool. Or, if you don't want to bother with that, you could try writing some blog posts based off of the correct answers you gave to obscure questions.

But really, it all depends on what you did with you Reddit account. If you answered people's obscure questions, you should keep that information. Would someone look up a question you answered? Did you talk a lot in more technical subreddits? Did those arguments you have result in any positive change? But if you spent all your time on big threads with thousands of other people replying, or did a bunch of lurking, maybe your account isn't worth keeping.

If you account is only of value to you, maybe just downoad a copy of everyhting you've said on there, then nuke your account with some tool.

significant other, probably

I almost thought you were that bot that changes youtube links to invidious ones, lol.

Yeah, those tend to be good (well, tux.pizza is a bit of an exception, it shows the error that the others fixed). It's a little annoying that a lot of the invidious instances that work won't show up when you do the "switch instance" thing on an instance that doesn't work, but it makes a bit of sense, not wanting to get overwhelmed, or trying to not get too noticed.

Yeah, youtube breaks things all too frequently, and a lot of the time these projects can't push out updates fast enough. A lot of invidious instances sadly don't work (as of the last time I checked them, a few days ago), but a few usually work because they merge patches before upstream does. inv[dot]nadeko[dot]net comes to mind.