• mabeledo@lemmy.world
    link
    fedilink
    arrow-up
    6
    arrow-down
    2
    ·
    11 hours ago

    Neither does systemd. They are optional.

    LDAP has had a birth date field for like 20 years now. Is it “complicit” as well?

    • Viceversa@lemmy.world
      link
      fedilink
      arrow-up
      2
      arrow-down
      3
      ·
      edit-2
      7 hours ago

      Neither does systemd. They are optional.

      Fields are optional, but developers of systemd consciously implemented those fields.

      And in a DB that’s not the case.

      • mabeledo@lemmy.world
        link
        fedilink
        arrow-up
        3
        arrow-down
        1
        ·
        10 hours ago

        systemd devs successfully rage baited you and a bunch of others. It’s time to let it go.

        But if you don’t want to, let me ask, how do you think a data field with no connection to any access control subsystem, is going to prevent anyone from logging in?

        • Viceversa@lemmy.world
          link
          fedilink
          arrow-up
          2
          arrow-down
          3
          ·
          10 hours ago

          systemd devs successfully rage baited you and a bunch of others

          Should that be their goal?

          • anyhow2503@lemmy.world
            link
            fedilink
            arrow-up
            4
            arrow-down
            1
            ·
            9 hours ago

            It isn’t. I’m pretty sure the dev working on that userdb field didn’t plan on getting death threats on github and said as much afterwards.