This isn’t so strong on the coding part, but touch in some degree on this regard. The focus is on the data storage and access of data. I hope you like this post.

All feedback is welcome.

  • Shin@piefed.socialOP
    link
    fedilink
    English
    arrow-up
    3
    ·
    5 days ago

    Usually done with a government issued ID, which wasn’t digital, the moment it is digital how to prevent from being used (the information) without your consent?

    • Nighed@feddit.uk
      link
      fedilink
      English
      arrow-up
      2
      ·
      5 days ago

      Plenty of ways.

      The way I would look at is a government portal that a site can send a query to “Is this person over 16?” The site would show you a code that you put into the portal (after logging in) to match that claim to your ID. That way, data is only accessed if you approve its access, the site doesn’t actually know who you are, just that you are over 16, and theoretically, the government doesn’t know who was requesting (although I can see there being issues with spam).

      This could probably be improved with a government ID app and some QR codes etc. The problem is that for this to work the Government portal has to be built with a privacy focus, not a spying on you focus.

      • Shin@piefed.socialOP
        link
        fedilink
        English
        arrow-up
        1
        ·
        5 days ago

        In my blog post I describe a similar flow for data access that follows similar steps.

        Looks like we were thinking on the same path.