Andres4NY

@somegeek @jobbies This is a good read. I was rather amused by your "TODO: How to use Git offline? Offline merge requests?" section, though. Git was written by people who literally email each other patches. It's offline-first, with online stuff tacked on there. You can copy a cloned git repo to a usb stick and give it to someone, and now they have the entire history. Of course merge requests and bug tracking are separate (I understand what you meant w/ the TODO), but git itself is already there.

@pfr @nikodindon That assumes it won't get worse, which I hope it does. AI companies have forced me to take down web stuff that I had running for almost 20 decades, because their scrapers are so aggressive.

@h333d @Holytimes Oh no, I write the same way! I can't wait to be accused of being an AI the next time I publish something. 😂

@rimu @Dust0741 Also, even if openwrt stops supporting it.. If you have a router or firewall or something in front of your access point, then running an old version of openwrt isn't really that much of a risk if we're talking about residential wifi w/out a lot of coverage.

And that's assuming you'd want to stick with a model that openwrt has dropped support for. If they do drop support in a few years, you could buy a newer (better supported) older model again for $40.

@kiol Syncthing? Restic? All packaged nicely in Debian, no need for containers. I do use Ansible (rather than backups) for ensuring if a drive dies, I can reproduce the configuration. That's still very much a work-in-progress though, as there's stuff I set up before I started using Ansible...

@kiol And then there's the stuff that's not packaged in Debian, like navidrome. I use a container for that for simplicity, and because if it breaks it's not a big deal - temporary downtime of email is bad, temporary downtime of my streaming flac server means I just re-listen to the stuff that my subsonic clients have cached locally.

@kiol On the other hand, for doing builds (debian packages and random other stuff), I'll use podman containers. I've got a self-built build environment that I trust (debootstrap'd), and it's pretty simple to create a new build env container for some package, and wipe it when it gets too messy over time and create a new one. And for building larger packages I've got ccache, which doesn't get wiped by each different build; I've got multiple chromium build containers w/ ccache, llvm build env, etc

@kiol I mean, I use both. If something has a Debian package and is well-maintained, I'll happily use that. For example, prosody is packaged nicely, there's no need for a container there. I also don't want to upgrade to the latest version all the time. Or Dovecot, which just had a nasty cache bug in the latest version that allows people to view other peoples' mailboxes. Since I'm still on Debian 12 on my mail server, I remain unaffected and I can let the bugs be shaken out before I upgrade.

@MimicJar @moseschrute *touches finger to earpiece*

...hang on, I'm getting word that the most recent edition of this book will crash your nvram's firmware