this post was submitted on 04 Jan 2024
453 points (98.1% liked)
Technology
59569 readers
4136 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related content.
- Be excellent to each another!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, to ask if your bot can be added please contact us.
- Check for duplicates before posting, duplicates may be removed
Approved Bots
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
No. They would rather effective age verification that doesn't negatively impact the privacy and liberties of their users. They want a solution, not just a ham fisted excuse to start building the foundations of a social credit system
While care is required, designing a system that only proves that someone is over a specific age is possible without leaking much additional information.
For example a request for age verification can be generated and signed by the porn site. All it needs is a unique ID and the signature. It should expire quickly and can only be used once.
The person identifying themself can send this request to a certifying party (the government in the EU where we trust governments, or I guess some terrible for profit company in the USA because they privatize everyday). The certifying party can sign the request, since they know how old the person is.
The person then returns this verification to the porn site.
In this scenario the porn site never learns anything about the user other than that they are above a given age. The certifying party only knows that the person has gotten an age verification, but not why or where.
There is still possible collusion between the porn site and the verifying party, but in that case the system is not really needed at all. Also metadata tracking is possible (like when a person gets a request and has network traffic to a porn site), but can be mitigated if a user is concerned.
Bruh you really just reinvented tracking cookies
Did I? I'm not sure how. The person visiting would only use the verification request once. It's only good for a single request. How could this be used for tracking?
You didn't... If anything you've described something closer to OAuth or JWT. You're just getting hit by people who don't know how cookies actually work.