SunshineSay no to any age verification taking root
WildmimicI 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.
WaxRhetoricalYour 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.
Most of the laws aim for social media, so the 2 bit solution should be enough for most legislation. I would propose an “Birthday” field for legislations where an exact date is needed (which shouldn’t be, because it’s allowing every tracker to identify the DoB) and the “2 bits” for the rest. In my country the ages are 16 for drinking beer/voting and 18 for “mature"/hard liquors/tobacco.