This reverts commit acb6624, reversing changes made to ba1caf0.
Revert "userdb: add birthDate field to JSON user records (#40954)"
After extensive community discussion, legal review and c...
It’s an optional field in the userdb JSON object. It’s not a policy engine, not an API for apps. We just define the field, so that it’s standardized iff people want to store the date there, but it’s entirely optional.
Hence, please move your discussion elsewhere, you are misunderstanding what systemd does here. It enforces zero policy, it leaves that up for other parts of the system.
And sorry, I am really not interested in these discussions here. it’s not the right place for this, and please don’t bring it here. Thank you.
Especially given that a lot of us are interested in content filtering, just that we want to be in control of what we’re subjected to, cf adblockers.
I’d be super fine with it if I could tune, say, the YouTube app on our TV to not subject me to ads for illegal gambling sites, fossil fuels, vacations in authoritarian regimes, etc.
But that’s exactly what they don’t want us to have control over, because that means lost income.
https://github.com/systemd/systemd/pull/41179#issuecomment-4090834541
I think the response given is unwarranted. Sure lots of heated discussion in other places but this was a PR, and a well presented one too.
This data should not be on the system level at all. What’s next, gender? Race? We all know why this was done, and doing it was shameful.
Especially given that a lot of us are interested in content filtering, just that we want to be in control of what we’re subjected to, cf adblockers.
I’d be super fine with it if I could tune, say, the YouTube app on our TV to not subject me to ads for illegal gambling sites, fossil fuels, vacations in authoritarian regimes, etc.
But that’s exactly what they don’t want us to have control over, because that means lost income.
https://en.wikipedia.org/wiki/Slippery_slope