• Venia Silente@lemmy.dbzer0.com
    link
    fedilink
    English
    arrow-up
    33
    arrow-down
    11
    ·
    3 days 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.

    • Aatube@lemmy.dbzer0.com
      link
      fedilink
      English
      arrow-up
      8
      arrow-down
      1
      ·
      edit-2
      3 days 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

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

        Wow, picking choice words only in sections of the laws and proposals. At least try and engage in honest discussion, mate,

        Honestly, just go check Ageless Linux’s site. They have a complete rundown on how and where does each law’s expectation come from.

        Just one (1) example:

        SB 142 — App Store Accountability Act

        Requires “commercially reasonable” method. In other words, the powerful agents of the market (the Googles, the Facebooks, the NSAs) get to choose what you have to do to validate. Could even require biometrics.

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

        That’s because systemd, a well-known Microslop infection into the Linux ecosystem, is using the wayland playbook: specify nothing, leave to other projects the task and legal weight of implementation. All systemd has to do is to ship the field, then other projects are delegated the task of entering in a “legally compliant” way.

    • P03 Locke@lemmy.dbzer0.com
      link
      fedilink
      English
      arrow-up
      13
      arrow-down
      1
      ·
      3 days ago

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

      [citation needed]