• cley_faye@lemmy.world
    link
    fedilink
    English
    arrow-up
    15
    arrow-down
    1
    ·
    10 hours ago

    The biggest defense for this I see is:

    • it’s not bad now
    • it’s not mandatory
    • it will remain unused like the other fields that were previously there
    • you can put anything in it

    Then, tell me, why bother adding this in the first place, exactly at the time governments are looking toward full control of everybody’s computers? If it’s that innocent and useless, either someone really likes throwing shit up, or it won’t stop there.

    And given the slate of other things that “didn’t stop there” in the past few years, you know, it cost nothing to be cautious. Especially if it’s “so useless you won’t even notice it’s there” after all.

    • FauxLiving@lemmy.world
      link
      fedilink
      English
      arrow-up
      1
      ·
      4 hours ago

      Then, tell me, why bother adding this in the first place, exactly at the time governments are looking toward full control of everybody’s computers? If it’s that innocent and useless, either someone really likes throwing shit up, or it won’t stop there.

      It’s there because systemd is the place that makes the most sense to store that kind of data.

      Systemd stores user details.

      This is a user detail.

      So, storing it in systemd makes the most sense.

      The alternative is having every individual program try to store data about the user in their own, non-interoperatble formats. That’s a needless complication when systemd already stores user details

      This field will not affect you unless you choose to let it. You get to pick what software is installed on your system. Unless you choose to use an application that validates your birthdate, the field does absolutely nothing.

      For people who want to use birth date (say, maybe people with multiple kids) it makes way more sense to store that detail about the user along with every other detail about the user that’s stored on the system.