• Venia Silente@lemmy.dbzer0.com
    link
    fedilink
    English
    arrow-up
    25
    ·
    8 hours ago

    Fields like name and location do not have any expectation for the information being valid or accurate (see eg.: adduser).

    DOB is different. It comes from a legal expectation that correctness of the information will be enforced somehow. If going by the Colorado and NY law proposals, IIRC, by using biometrics at the time of system install.

    • P03 Locke@lemmy.dbzer0.com
      link
      fedilink
      English
      arrow-up
      1
      ·
      37 minutes ago

      DOB is different. It comes from a legal expectation that correctness of the information will be enforced somehow.

      [citation needed]

    • Aatube@lemmy.dbzer0.com
      link
      fedilink
      English
      arrow-up
      1
      ·
      edit-2
      3 hours ago

      not even said laws have an expectation that the date of birth provided would be accurate. the colorado bill just says “require[] an account holder to indicate” and never defines “indicate”, the ny bill says “request an age category signal” and never defines “signal”, so i assume they’re like the california law which has been verified to be just “enter your date of birth in this text field/dropdown and we’ll trust you girl”. i don’t think any of that involves biometrics

      there’s no alien intelligence or protocol specification in systemd that ensures or says the dob field must be accurate either