That is (or is not) happening regardless of systemd involvement. This is just a place to store the value. Not having such a place in systemd would just mean it is stored in some other place. This doesn’t make it significantly easier to implement age verification nor would reverting it make it significantly harder. It’s just a field that may be used by people who are legally obligated to store or read that data.
Every rant about systemd is a wasted opportunity to yell at someone who deserves it, honestly. Focus on the people pushing age verification laws or doing age verification.
“Verify” is a strong word, if the age in there isn’t actually verified. If I say my realName is Nunya Bissnis, my location is Atlantis and my birthDate is 1970-01-01, who’s going to check if that’s at all accurate?
Maybe there should be a way to randomise it. Maybe there could be a script to automatically update my DoB entry to “Today - 18 years” every day. Or maybe there are some default values we could use that make it hard to track, like John Doe, 1970-01-01.
Or maybe we just don’t enforce entering anything. Given it’s not a thing in every jurisdiction, there needs to be a toggle to activate sharing it anyway. Be a shame if people found a way to trick the system.
Though the proposed Flatpak change works by responding to age brackets rather than specific dates. That would also obscure it a little, but be enough for parental controls. Whether those are reasonable is a different discussion I don’t feel like having at the moment.
Again, you’re right that it would help narrow it down, which might make it an arms race akin to security, where we’d have to keep finding ways to mess with the tracking, but there are more implementation layers that I imagine will be harder to enforce.
I also agree that it’s iffy, just as the realName and location fields, but it’s not quite as bad as all the newly-minted systemd haters make it out to be. If you’re an OG hater looking for more reasons, sure, be my guest.
systemd is introducing birthDate as a user json field, if that’s what you mean with rumor.
The PR to revert that change was not merged:
https://github.com/systemd/systemd/pull/41179
Next the OS will have to verify this is correct
Be like grapheneos and say no to age verification
That is (or is not) happening regardless of systemd involvement. This is just a place to store the value. Not having such a place in systemd would just mean it is stored in some other place. This doesn’t make it significantly easier to implement age verification nor would reverting it make it significantly harder. It’s just a field that may be used by people who are legally obligated to store or read that data.
Every rant about systemd is a wasted opportunity to yell at someone who deserves it, honestly. Focus on the people pushing age verification laws or doing age verification.
It’s another domino fallen, another step towards absolute control
I don’t think that’s a reasonable assessment of this change
It was added with a note specifically that the implementation was related to a law that was described as stupid.
I think it’s pretty clear exactly what this was being put in for, and why two MSFT devs were ready to approve.
There’s no “it was just…” about this, it was step one of a coordinated plan that has not been abandoned.
Poettering doesn’t work for Microsoft.
Poettering only very recently left microslop
Yes, that’s another way of saying what I said…
The approver of the pull request does…
I agree, your point?
So apps can look at it and verify the users age? 🤔
“Verify” is a strong word, if the age in there isn’t actually verified. If I say my realName is Nunya Bissnis, my location is Atlantis and my birthDate is 1970-01-01, who’s going to check if that’s at all accurate?
It’s really a declaration, or an assertion.
Doesn’t matter if it’s accurate. Now they have more unique data points to help track your digital footprint.
Good point.
Maybe there should be a way to randomise it. Maybe there could be a script to automatically update my DoB entry to “Today - 18 years” every day. Or maybe there are some default values we could use that make it hard to track, like John Doe, 1970-01-01.
Or maybe we just don’t enforce entering anything. Given it’s not a thing in every jurisdiction, there needs to be a toggle to activate sharing it anyway. Be a shame if people found a way to trick the system.
Though the proposed Flatpak change works by responding to age brackets rather than specific dates. That would also obscure it a little, but be enough for parental controls. Whether those are reasonable is a different discussion I don’t feel like having at the moment.
Again, you’re right that it would help narrow it down, which might make it an arms race akin to security, where we’d have to keep finding ways to mess with the tracking, but there are more implementation layers that I imagine will be harder to enforce.
I also agree that it’s iffy, just as the realName and location fields, but it’s not quite as bad as all the newly-minted systemd haters make it out to be. If you’re an OG hater looking for more reasons, sure, be my guest.
If someone populates it and if apps do it. The “debate” is whether this is something systemd should or should not have done.
I only mean the verification is clearly in the app that uses it then.