The optional birthDate field gives other projects a standardized data source for age verification compliance.

  • oatscoop@midwest.social
    link
    fedilink
    arrow-up
    0
    ·
    2 months ago

    I agree with you, however I still see it as a problem given with how I’m certain it’s going to be used. It will be used to gather demographic data and help fingerprint users/devices. It’s widespread adoption will cause it to become nearly mandatory to use the mainstream internet.

    “Oh, your device doesn’t report the user’s age range? Sorry, our service isn’t available for you.”

    • kaiyo@piefed.ca
      link
      fedilink
      English
      arrow-up
      0
      ·
      2 months ago

      If, and I do stress if applications require it filled out, there are simply going to be an awful lot of epoch birthdates in their data. And frankly a lot of people, myself included, who will step up and write replacements to these applications in order to give a giant middle finger to authoritarian governments/companies as a result.

      It’s very mild this, and as it has no ‘verification’, it’s just a meaningless string of numbers.