• aksdb@lemmy.world
      link
      fedilink
      arrow-up
      0
      ·
      29 days ago

      How would the current approach help?

      Its not invasive yet (no third party, no ID, no verification; its basically just another user controlled date field that is not even exposed). So it is not lowering any barrier in that regard.

      It’s also not a helpful intermediary step for harder measures, because as soon as you want a third party to do attestation, storing that on a user controlled device is just unnecessary complexity and risk of circumvention. It would be easier and safer (for those introducing it) to just let the attesting party talk to the providers directly.

        • aksdb@lemmy.world
          link
          fedilink
          arrow-up
          0
          ·
          29 days ago

          Isn’t that level already socially normalized? Every second website asks me for my birthday to derive my age for as long as I can think. Many of them ask me basically every time I use them (even Steam, where I am logged in and my payment history alone should imply that I am old enough).

            • aksdb@lemmy.world
              link
              fedilink
              arrow-up
              0
              ·
              29 days ago

              The US bills I have read also don’t enforce any real age (how could they). They require the birthday to be stored on the device for the device to reply with the info if the user is within a certain age bracket. But nowhere did I see anything that would force users to store their truthful birthday. All that it would do is making the already existing age checks much more convenient and giving parents the opportunity to make them slightly more secure.