Systemd added a birthDate field in userdb to "comply" with the new age verification laws[1]
Since GardenerDB is meant to work as well as possible as a drop-in to systemd-userdb, I am forced to also add this field, but I refuse to properly implement it
GardenerDB will hardcode the birth date to be 1998-07-06 for every user, any application that accesses that field for whatever reason will be happy to have that field, and the user will be happy that they don't have to reveal their actual age.

https://git.pinkro.se/Rose/gardenhouse/gardenerdb.git/commit/?id=37dc6f53ce091965c006cf273c88dd352b197587

1: https://github.com/systemd/systemd/pull/40954
gardenerdb.git - Drop-in standalone implementation of systemd-userdb

@rose
Why not hardcoding e.g.
1998-02-29? On this day, no one was born because this day did not exist. 😂
lmao that would also be funny
i went with 1998-07-06 because that's when Lain aired in japan
@rose @rzbrk i wouldve let the user pick between the release dates of doom, quakes 1-3 and half life

@coolbean Half-Life (>=18), GTA IV (16-18), Minecraft (13-16), Doom 2016 (<=13)

4 age brackets. perfectly AB 1043 compliant.

@rose @rzbrk

@rzbrk @rose Depending on if the day is broken-down or an epoch time, you might not even be able to represent that. Even if it is broken-down, a value that doesn't round-trip might make other things break.

@dalias
The idea of my proposal WAS to break things. 😉 I understood, that the field in the DB serves only one purpose: age verification.

But thank you for the technical details. It might not be feasible in every case to just present a non-existing day.

@rose

@rzbrk @dalias @rose

The best way to break any system is to provide a problem that bypasses its error checking. If something causes an exception (for example an invalid date) then they can fix that problem pretty easily, or at least flag it to management.