[jmclnx]

This is a no win situation and I think systemd is making this change too early. But I have read that field is optional.

But my main concern with this is applications like Firefox will eventually require this systemd age specific field and a standard systemd function to call. That means this age field will need to be populated and thus locking out the *BSDs and non-systemd Linux.

If that happens, this makes the systemd critics 100% right, systemd is being forced upon all distros by various upstream applocations.

[Bender]

My gaming machines that I do not browse the web with have systemd (CachyOS) but my daily drivers do not. Should a website lock me out because I don't have some age API then in my view the problem has solved itself. The website has effectively blocked itself without me having to given the one and only correct way to age gate a site in my view is with the RTA header [1] that would trigger parental controls if optionally enabled on ones device. Every other path that involves exchanging data whether verified or not, anonymized or not can only lead to future evil shenanigans.

[1] - https://news.ycombinator.com/item?id=46152074

[logicchains]

>But my main concern with this is applications like Firefox will eventually require this systemd age specific field and a standard systemd function to call. That means this age field will need to be populated and this locking out the *BSDs and non-systemd Linux.

The risk is real, and the solution is to move away from systemd now, not wait until it's too late. Whatever conveniences it brings over other init systems are certainly not enough to justify giving up online anonymity forever.

[skydhash]

> Whatever conveniences it brings over other init systems

You see people rave about the greatness of systemd, then they turn to deploy their applications using Docker and some s6 config.