I have no idea what Systemd wants to do with a birthdate, but what confuses me is that this specifically was merged to comply with californian law.
Does that mean every reasonably sized political entity can now declare some stupid requirement and somebody has to merge it into Systemd, because if California is important enough so are 1000s of other states, nations and so on?

Anyway, version 260 will probably hit the arch repos soon and I can answer the question:
Will I be able to boot my ThinkPad with security features enabled after more than 4 months of it being bugged.

Tbf...ThinkPads are really obscure hardware and never used it environments that might require some security features (actually tbf those probably don't run bleeding edge distros but eh)

The anti systemd crowd seems to slowly start having a point. Still for all the wrong (truly awful) reasons but it ends with the same result.
Welp. This looks promising…

@Eichi
Tbh, the big achievement will be if it boots the OS without it falling apart. That said, I had a machine that had Arch that was about a year out of date. Of course there was no way to update it the conventional way because pacman would just give up after all the dependencies being broken.

And yes, it's fascinating (in the bad way) how quickly the "OSS behemoths" bent over backwards to comply with the neo-Stasi laws when every other time they kicked the fuss to high heavens.

@Eichi the sheer idea is #cyberfascist bs and I'm glad that #SystemD yeeted it.

@Eichi No, they'd only do this for dictatorships.

So if you want instead some feature for privacy, freedom of speech or other human rights - not gonna happen.
@Eichi My birth date somehow coincides with that of Unix: 1970-01-01, as far as they know (those who are not entitled to that knowledge and will not be read in to the truth)