Age Verification is Incompatible with the Internet - Jonah Aragon
www.jonaharagon.com
external-link
The recent move among U.S. states to add digital “age verification” to websites which serve adult content is a troubling one. Digital age verification systems are rife with privacy concerns, many requiring you to upload your government ID to third-party vendors or even directly to the website in question. Privacy advocates and companies within the […]

Or we could, y’know, stop trying to exclude young people from literally every possible expression or exploration of their own sexuality…

I think this article makes a pretty big leap in the middle. There’s really no reason that the operating system needs to be involved in the “Private” solution. It could just as easily be a website or a browser plugin. All you need is your government of choice to have some way to provide a token with whatever important bits necessary in it (“Yes this person is over 18 and a resident of WA”). You could even have third party sites/libraries that could read that token and verify what it contains.

The last third of the article is all based on that giant leap.

bitwolf
link
fedilink
English
16M

OIDC is designed around this capability, I could already imagine a big country flag themed “Sign in with Govt ID” button on websites like we do with other options.

Create a post

In the digital age, protecting your personal information might seem like an impossible task. We’re here to help.

This is a community for sharing news about privacy, posting information about cool privacy tools and services, and getting advice about your privacy journey.


You can subscribe to this community from any Kbin or Lemmy instance:

Learn more…


Check out our website at privacyguides.org before asking your questions here. We’ve tried answering the common questions and recommendations there!

Want to get involved? The website is open-source on GitHub, and your help would be appreciated!


This community is the “official” Privacy Guides community on Lemmy, which can be verified here. Other “Privacy Guides” communities on other Lemmy servers are not moderated by this team or associated with the website.


Moderation Rules:

  1. We prefer posting about open-source software whenever possible.
  2. This is not the place for self-promotion if you are not listed on privacyguides.org. If you want to be listed, make a suggestion on our forum first.
  3. No soliciting engagement: Don’t ask for upvotes, follows, etc.
  4. Surveys, Fundraising, and Petitions must be pre-approved by the mod team.
  5. Be civil, no violence, hate speech. Assume people here are posting in good faith.
  6. Don’t repost topics which have already been covered here.
  7. News posts must be related to privacy and security, and your post title must match the article headline exactly. Do not editorialize titles, you can post your opinions in the post body or a comment.
  8. Memes/images/video posts that could be summarized as text explanations should not be posted. Infographics and conference talks from reputable sources are acceptable.
  9. No help vampires: This is not a tech support subreddit, don’t abuse our community’s willingness to help. Questions related to privacy, security or privacy/security related software and their configurations are acceptable.
  10. No misinformation: Extraordinary claims must be matched with evidence.
  11. Do not post about VPNs or cryptocurrencies which are not listed on privacyguides.org. See Rule 2 for info on adding new recommendations to the website.
  12. General guides or software lists are not permitted. Original sources and research about specific topics are allowed as long as they are high quality and factual. We are not providing a platform for poorly-vetted, out-of-date or conflicting recommendations.

Additional Resources:

  • 1 user online
  • 4 users / day
  • 34 users / week
  • 91 users / month
  • 1.14K users / 6 months
  • 1 subscriber
  • 661 Posts
  • 11.1K Comments
  • Modlog