Planning to host a Nix caching server, and have CI build all package and NixOS outputs on every push to git, then in turn pushing the output artifacts to the cache. Would save me a good chunk of time when tinkering with VMs that haven't seen manual updates in a while.
Only thing is, I'm not sure how to approach building and caching NixOS configs that receive agenix secrets in their input. Obviously those should not be cached...
You do not need your fingerprint or any other biometric to use a passkey.
You do not lose access to passkeys when you lose your device.
Yes, and I do werether the recipient also knows how to use it.
So, for like, 1% of my mails.
More like: paying someone to maintain the hardware.
Anyways.
Just FYI, your mails with a provider like Proton are not E2E encrypted unless you exclusively wrote with other Proton customers (in which case I assume they are. No idea). Otherwise it's just encrypted at rest.
I dint really see the benefit over doing it completely yourself, not even offering metadata to a provider, and also having encryption at rest, while maintaining full compatibility with mail clients 🤔
I can access my password manager via the browser from any device.
Not a VPS.
You can store Passkeys in open source password managers.
I don't know most of my passwords, so the step to passkeys doesn't feel like a big one. I also really like the flow of pressing Login; Bitwarden pops up a prompt without me initiating it; I press confirm. Done, logged in, and arguably more secure due to the surrounding phishing and shared secrets benefits.
We host most stuff at home, and then additionally some services at Hetzner on an (auctioned) root server. Bloody nice to get really good hardware for cheap, plus unlimited data with either 1 or 10Gbit synchronous network speed, a dedicated IPv4,...
Stuff like my mail server lives there because it HAS to be available, and doing it at home, and doing it well, is next to impossible.
I'm planning a nix hydra + cache server, which will probably also live on the Hetzner server, simply because it'll have pretty intense jobs to run a lot of the time and I'm not a fan of having the noise of spun-up fans at home.
Both solutions have their place, is what I'm saying / agreeing.
Through borg, I have the Option to go back to any point in time with the backups. I will probably never need this, hence why it happens in this step, not on the rsync job to the NAS.
Things like movies and tv shows are not backed up, they are replaceable. All in all, about 2tb of documents, pictures, and VM state is backed up to Hetzner, out of the 16tb on the NAS.
Pick and choose your battles.
I will never understand why people wear wear-once, then throw-away clothes.
- Cheers, typing this from within my 8-year-old coat that'll stay in use at least another 8
Yeah, all of the above, but also: blacklisting Pinterest from all my searches is almost worth the ten bucks a month on its own, lmao.