Who needs @GossiTheDog when I can get all my JLR updates from a YouTuber whose most notable skills include crashing cars for fun that regular people could never afford. And his sidekick, Ian.

Who needs @GossiTheDog when I can get all my JLR updates from a YouTuber whose most notable skills include crashing cars for fun that regular people could never afford. And his sidekick, Ian.
@1password I just got your email about Comet.
"The AI" is in the Comet side, right? Not 1Password?
After what feels like too many days, and many false starts by trying to unpick someone else's code, tonight I finally successfully deployed a basic #NixOS VM on my Mac, with some homelab services installed as native NixOS services rather than containers, behind an ACME-enabled Caddy proxy and SOPS secrets.
Not sure I get what all the fuss is about, but job number 2 is try and abstract all of that so it can also be deployed on x86_64 and potentially try it on my NAS. Maybe then I'll get it.
The privacy team might claim they don't have a list of all the forums they own. But I do.
Is it a dick move to send all 1123 domain names over and ask for any data on any of them? Feels like if that's the system they've created for themselves then that isn't my problem...
The Project Like lots of my basement-dwelling geek comrades, I have a home-made NAS hooked to my LAN. I’m a man of simple tastes, easily satisfied with: SMB/NFS/rsync Jellyfin, including some transcoding for ‘difficult’ files Various containers, such as the Unifi Network Application controller for my wireless AP I had an old rig based on a venerable Xeon E5472 and a 2007-ish Gigabyte motherboard (with its amazing PCI slots !), which while suprisingly still very functional, was not terribly energy efficient at 100W+ power draw. Unfortunately, the proverbial writing was on the wall, as EL9 (and therefore its derivatives Rocky Linux and Alma Linux) dropped support for everything earlier than x86-64-v2 architecture, and my goold old Xeon chap didn’t make the cut …