

I’m surprised Ubuntu wasn’t using systemd-timesyncd. It seems like something they’d like based on the prefix.


I’m surprised Ubuntu wasn’t using systemd-timesyncd. It seems like something they’d like based on the prefix.


OP is presenting to Adobe.com with an inability to combine two PDFs and a lack of subscription fatigue.


I’ve used Little Snitch on macOS, but I agree that a closed-source blob won’t fly on Linux. OpenSnitch exists, though I haven’t tried that one.


Can I just do an apt remove —purge systemd-ageverificationd and call it a day, or do I need to edit /etc/systemd/ageverificationd/birthday.conf and call it a day?


I don’t agree with this law, but having an age verification API as an open-source modular component is the best way to do it. Build in privacy controls and permissions so you know what’s being sent, where, and when. Make sure we know to edit $HOME/.config/systemd/ageverificationd/birthday.conf whenever we want (yeah, I wouldn’t be surprised if systemd handled this, too).
Don’t forget the off switch and don’t give it unnecessary dependencies. Let me be able to install it if I need it (spoilers: I won’t) and if you include it by default, let me be able to remove it without removing the whole GUI.
I wound up switching to Debian. It’s stable. It works. It lets me tinker and upgrade some packages without compromising the whole system.
My only gripe is that OS upgrades are a manual process. I miss Ubuntu’s do-release-upgrade command, though following a process isn’t hard.


Agreed. I use Secure Boot on my Linux systems with my own keys. Let’s not confuse it with Restricted Boot, which is awful.


Nah, he Base4017’d it. That’s Base64 plus all the emojis. It’s actually quite efficient.


Good question. It seems like Debian has been speeding up a bit. The software is still a bit older, but it’s not too far behind compared to some other Debian releases. I switched and it’s been rock solid, despite me running a Trixie Backports system.
Agreed! Though give me the backports any day.
It’ll probably happen in the next few years. Compiling for PowerPC went away after macOS dropped it, and it was the same story for i386. Running and targeting x86_64 will soon be a distant memory.
That being said, if you have a Mac/Hackintosh/VM with an older Xcode, keep it! You can still compile with the old version, compile with the new version, and stick the results together with the
lipocommand. I wrote a simple C CLI app and I can put five architectures in one binary if I want (ppc, ppc64, i386, x86_64, arm64) and it’ll run on any macOS/Mac OS X version ever made.