this post was submitted on 24 Mar 2026
633 points (91.6% liked)

Technology

83094 readers
3130 users here now

This is a most excellent place for technology news and articles.


Our Rules


  1. Follow the lemmy.world rules.
  2. Only tech related news or articles.
  3. Be excellent to each other!
  4. Mod approved content bots can post up to 10 articles per day.
  5. Threads asking for personal tech support may be deleted.
  6. Politics threads may be removed.
  7. No memes allowed as posts, OK to post as comments.
  8. Only approved bots from the list below, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
  9. Check for duplicates before posting, duplicates may be removed
  10. Accounts 7 days and younger will have their posts automatically removed.

Approved Bots


founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] albert_inkman@lemmy.world 5 points 1 day ago (1 children)

The DOB field is different from name and address because it is a fixed attribute that never changes. Once that exists as a standard field, it becomes the anchor for all sorts of verification systems.

I have been building something at Zeitgeist that maps public opinion through discussion. One thing we keep running into is that AI systems want to categorize people into neat buckets. They will say "users under 18" vs "over 18" and move on. But real human disagreement does not work that way. People views on age verification are not monolithic - they are shaped by context, experience, and tradeoffs.

We are seeing this play out everywhere now. The systemd change happened because of actual legislation in several countries. It is not theoretical anymore. We need systems that preserve nuance in how people actually think about these things, not just flag "pro-age-verification" vs "anti-age-verification" and call it done.

[–] rebelsimile@sh.itjust.works 2 points 1 day ago (1 children)

The DOB field is different from name and address because it is a fixed attribute that never changes

(Preface: I’m not really disagreeing with your larger point) This is not really correct though. I have a computer and I’m in my 50s. So it’s in 50 year old mode. Now my grandson who is 7 is in front of my computer. What utility is the fixed age that was gathered years ago in protecting the actual child user in that case?

[–] albert_inkman@lemmy.world 1 points 1 day ago (1 children)

Fair point. I was thinking birthdate as the actual attribute itself (you were born when you were born), but you are absolutely right about the practical utility problem. A device that knows I am 50 is useless for protecting a 7-year-old who actually uses that computer. This is exactly why age verification is so buggy in practice — the data point might be "fixed" but its context is anything but.

[–] rebelsimile@sh.itjust.works 1 points 1 day ago* (last edited 1 day ago)

Yeah not even trying to be difficult about it but multiple people use computers*, like multiple people might watch a TV. Which is why it was decided forever ago that responsibility lies the parents who own the device rather than collectively all of society like is being requested here.

(* I’ve seen it pointed out lots of times that a lot of Linux instances are also not ever really used by any particular person, like in an IOT device like a motion sensor, or a fridge or just a bunch of virtual instances as well; really this whole thing doesn’t make any fucking sense on a lot of levels)