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.

I didn’t say that.

Listen, I’ve got nothing against you hating AI. There’s lots of valid reasons to be concerned, especially with the implications for the future of jobs and work. The way corporations are adopting AI is legitimately concerning.

Just don’t pretend it’s about the environment when it’s not. That isn’t just an unconvincing argument, it hurts the environmental movement generally.

It’s the plastic straws all over again. You understand that the stupid straws debate did the environment no favors right? Fighting AI as an environmental issue is much worse because the AI is coming, and you will lose that fight. If you’re arguing for more controls about water and power use, I’m with you. If you’re arguing for a carbon tax, I will sing your praises. If you’re trying to fight the idea of AI itself, and pretending that it’s about the environment, that’s where I have a problem.

The TPM exists because it’s useful to support use cases where you want your passkeys tied to a device. It isn’t a Microsoft thing either. I run Linux - my computer has a TPM. I can’t use it because Linux support for the TPM is weak still, but it’s there! You probably have one too if your computer was made in the last decade.

By default, even on Windows, your website passkeys aren’t stored in the TPM. No one is forcing you to store your passkeys on the TPM.

And they won’t, because it’s a bloody stupid idea that benefits no one.

Microsoft wants your passkeys synced across devices because that’s how you get lock in. If the passkeys are stuck on the computer you made them on, then you may as well buy a Mac for your next computer because those passkeys are gone either way! If the passkeys are in Microsoft Password Manager though, now migrating to a Mac is harder.

[forget]
keep-daily = 10
keep-weekly = 4

Daily backups are cheap because of de-duplication. I keep a few weekly backups in case it takes me a bit to notice something went wrong. I don’t usually back up logs.

I could probably drop the weekly backups without much risk, but I’ve got the space.

Sure.

Do you think that’s a reasonable reason to hate gen AI?

There are absolutely issues around the rollout of AI. I haven’t seen anyone disagree with that. That’s just not a good argument for being opposed to the technology. That might be a reasonable reason to hate xAI or Microsoft (and I do!). It’s definitely a reasonable reason to have concerns about how we’re doing this. You should be concerned.

It’s not a reasonable reason to hate the technology itself.

You’re free to hate GenAI all you like as far as I’m concerned. Just be honest about your reasons, and don’t pretend it’s about the environment if you don’t care enough to even look at the numbers.

Have you actually looked into the real environmental impact of AI is compared to, say, eating meat, driving a car, or taking a yearly plane flight? It’s a rounding error. Have you looked into the numbers? Compared the environmental impact of your AI use to the environmental impact of taking a yearly vacation on a plane?

The RAM shortage is real, but very temporary. Check the news today! Chip stocks like Sk Hynix are way down because people are worried about over-production. The fact that a new technology caused a temporary shortage in a resource just isn’t even a coherent argument against the technology. There’s discussion to be had here about whether we should as a civilization reserve some resources for other industries. That’s a discussion we could have. But the idea that AI caused a temporary shortage in RAM, so that makes it bad is… like, really ridiculous? You must see that that doesn’t even make sense as an argument?

These are not arguments that hold up to scrutiny. You should consider whether you accepted these arguments because you looked into the details and they actually make sense, or if you accepted them because they’re telling you what you want to believe.

Memorizing passwords doesn’t scale well.

You’ve likely got dozens of accounts. You’re not going to memorize a password for every account. Re-using passwords is a serious security problem though. Poorly secured sites get their password databases leaked all the time. If you use the same password on lots of sites, it’s basically a sure thing that the hashes are out there on the darkweb already along with your email, and your password is compromised.

Also, typing your email password into an unsecured library computer is a terrible idea. It is ridiculously easy for someone to install a keylogger and gather emails and passwords. In the past, your main protection was that it wasn’t worth anyone’s time to break into the computers, install keyloggers, collect lists of passwords, then figure out how to use them to get money. But with LLMs that can all be automated. It has become ridiculously cheap, and can be done by someone with a bot farm in Russia.

A password manager largely fixes the first problem, but at that point you need a device with your password manager with you to log in anyway. And the password manager doesn’t fix the second problem at all.

I’m just not convinced that mandatory hardware attestation is actually a real problem we need to worry about.

Like, yes, people with high security jobs will have that for sure. And they should.

But large companies that want customers? They want to make it as easy as possible for their customers to connect. They’re not going to force people to have a hardware device which if damaged or lost will lose them a customer. That’s just not what they want.

And… honestly, you should probably buy 3. Losing your main key only to find out that your backup key broke a month ago and you haven’t been testing it is a real risk.

They’re actually not tied to a device. They can be synced across devices.

Bitwarden, 1Password, Dashlane, Google, Apple, and Microsoft will all do passkey syncing for you.

We don’t yet have a good Linux native passkey store. I believe the credentialsd project is working on a spec for that. Once that’s up and running I would expect to see some options for syncing without relying on a third party service (though, you can self-host bitwarden right now). It’s definitely not seamless on Linux yet though.

They really aren’t a trap. They’re a well designed standard. The tooling around them isn’t quite perfect yet, but they’re a huge improvement over passwords.

People upvote because they hate change.

I think people are right that the solution here isn’t to try a different project.

Instead of being confrontational about it, though, I’d recommend a different aproach.

evelyn: .lol 😜

you: I know! I know. The branding is pretty silly. But this really is the right tool for the task. Unesco and Wikimedia use it. And we can do our own branding for $50/month. 🤷

A lot can be fixed by just acknowledging people. They’re trying to evaluate something they don’t understand, and having a reaction. It’s not even unreasonable. The right thing to do is just acknowledge and move on.

Usually that’s all it takes. Don’t let yourself be embarrassed when you’re being reasonable. If they won’t move on, that’s the point where I start thinking about job applications somewhere else.

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.

GPL (and copyleft generally) gets way more attention than it should. In the wild, MIT and similar permissive licenses are by far the most common. Linux is on GPL, but that may be a historical artifact as much as anything. I don’t know if Linus himself would choose it if he were making the choice today.

The wider FOSS community, in my experience, leans permissive rather than copyleft. The copyleft people are just loud.

EDIT: To be clear, when I say I don’t know what choice Linus would make today, I don’t mean that I’m skeptical he’d choose GPL. I literally just mean that I don’t know. He’s been quite clear that he’s not a principled believer in copyleft, but it does have real advantages for a project like the Linux kernel.