I am very anti-age-verification laws, because they tend to be pro-identification-laws. But adding a simple field signifying the age of the current user is probably as good as it gets, although i would have preferred a single-bit-solution (of age/not of age) or at max 2 bits (<14, <16, <18, of age). Using this to go after Systemd again is a) not gonna work, because it’s here to stay and b) i am very interested in how others will implement the legal requirements.
Your country’s definition of “of age” and my country’s definition of it is likely to differ. Easier to just implement a birthdate field than try to cover all the global legislations for these things. Especially when there are multiple conditions for “of age” in a single country. Old enough to vote? Old enough to drink? Those are often not the same.
I am very anti-age-verification laws, because they tend to be pro-identification-laws. But adding a simple field signifying the age of the current user is probably as good as it gets, although i would have preferred a single-bit-solution (of age/not of age) or at max 2 bits (<14, <16, <18, of age). Using this to go after Systemd again is a) not gonna work, because it’s here to stay and b) i am very interested in how others will implement the legal requirements.
Your country’s definition of “of age” and my country’s definition of it is likely to differ. Easier to just implement a birthdate field than try to cover all the global legislations for these things. Especially when there are multiple conditions for “of age” in a single country. Old enough to vote? Old enough to drink? Those are often not the same.