I’ve always treated my home server with public facing services as presumptively compromised. I don’t put any data on there I wouldn’t want to see become public, and any data I actually care about losing is backed up to the cloud with an append-only key. The NixOS config lives in a git repo not on the server. If something bad happens, I can wipe the machine clean, redeploy the image, restore my backups, and we’re back to the status quo.
So, my threat model hasn’t changed much!
note that you probably need to trust the remote household with your data
Probably not actually. Borgbackup (and any sensible encrypted backup system really), does client side encryption. So the data should be encrypted before it’s even sent down the wire. The remote household shouldn’t be able to access the data without the encryption key/password.
I mean, they will have to trust the remote household not to destroy the data, but that’s pretty much an unavoidable limitation.
So… your evidence for slop is that he made a patch, they caught an issue in the review process, and then he had to go on vacation so he asked another maintainer to take over to get the change done correctly in the merge window?
How is that not the process working exactly as intended?
Also, Julius Caesar from Xena!
It doesn’t even have to be only for known devices. Once you’ve compromised one device, you can just phone home to have a full powered LLM do your work.
The only real use cases for this would be on closed networks with no internet access, or networks where the traffic is closely monitored. Like, yeah, if I’m trying to hack the CIA, maybe I consider something like this. For the vast majority of devices and networks, this is inefficient and unnecessary.
I mean, it is kind of cool. But vanishingly few organizations have tight enough security that this is worth doing.
Yeah. Once you spend an afternoon debugging a failing cron job, the 5 minutes needed to write the boilerplate starts to feel pretty ok though.
I’ve never had to spend an afternoon debugging a failing systemd timer in the years since I made the switch.
It’s not. But the systemd timer has more robust logging and monitoring, and much more explicit and readable syntax.
Once you get used to systemd timers, it’s really hard to see why you wouldn’t use them if your system has systemd. Unless writing crontabs by hand makes you feel like a hacker I guess. I’m not even being totally sarcastic about that - there is a fun retro feel to cron.
As much as this idea makes me feel good, pretending that the results of a vocabulary test are a reasonable measure of cognitive ability is the purest of pseudo-science.
As a community we shouldn’t be spreading this kind of nonsense.
100% agreed, though I’m in the “neither is ideal” camp. My favorite language, by a long way at this point is Rust.
It’s not functional, but borrows a lot of functional idioms while avoiding the pain points functional language usually hit in exchange for losing the purity of functional languages.