this post was submitted on 24 Mar 2026
470 points (90.7% liked)
Technology
83027 readers
3355 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related news or articles.
- Be excellent to each other!
- 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, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
- Check for duplicates before posting, duplicates may be removed
- 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
view the rest of the comments
You do know that this is a slippery slope argument, right?
You would have to demonstrate that there is an intention there to require third party services to validate the age of users using Linux... Or that there is an intention to do so by systemd and the broader open source developers.
I don't think it will be easily possible to lock out every Linux system from the internet that doesn't implement some kind of hardware DRM mechanism to make sure that the user cannot just change the date of birth with root permissions.
No, they don't.
You , as the party making the accusation of fallacy would be required to prove that the expectation of escalation is unreasonable or that the intention was not there.
edit: asking for an explanation of their thoughts around the issue is fine, but a requirement it is not.
I do understand that, but I think you are applying a post hoc rationalisation to the change. For example, examining the change through the lens of intended use - you can't - there is no such use of the field today - it's tomorrow's use that is potentially problematic. I don't want to wait until a bad actor applies the field, I want to stop the field from existing.
This change is not happening in isolation. There is currently a general trend towards de-anonymising users, and this DOB field is a step in that direction.
The only real question is, do I want my computer storing more, or less, personally identifying information. Given that I don't trust ANY use which may be later enabled by this change, my answer is 'less'.
Maybe this is the issue. I have no problems with parents setting the age of the children in their account in order limit their access to certain content.
And there clearly exists a use-case for that.
My main issue is when it comes to third-party age/identity verification services. Centralized age or identity verification is bad.
I'd rather give parents the tools to set individual restrictions locally on their devices, then pushing for a global internet based age filter.