just like the GECOS field in /etc/passwd isn't surveillance
Geofencing isn't surveillance either, but at least that one actually creates problems and you'd want it removed. If you don't want your account age signal to bother you, just set it to over-18?
Laying the infrastructure for surveillance qualifies.
Reporting age brackets to applications or websites via API definitely qualifies. (It reveals private information about the user.)
I will proactively remove any such fields or signals from my installs, thank you very much. Although fortunately all of the OSes I use have signaled noncompliance.
How is it different from anything else that gets reported to applications, like the username? Knowing my name is "George" is actually much worse than knowing I'm over 18.
> age signaling and age-bracket APIs
are not surveillance?
just like the GECOS field in /etc/passwd isn't surveillance
Geofencing isn't surveillance either, but at least that one actually creates problems and you'd want it removed. If you don't want your account age signal to bother you, just set it to over-18?
Laying the infrastructure for surveillance qualifies.
Reporting age brackets to applications or websites via API definitely qualifies. (It reveals private information about the user.)
I will proactively remove any such fields or signals from my installs, thank you very much. Although fortunately all of the OSes I use have signaled noncompliance.
How is it different from anything else that gets reported to applications, like the username? Knowing my name is "George" is actually much worse than knowing I'm over 18.
6 replies →
Found via: https://lists.debian.org/debian-devel/2026/03/msg00199.html
Looks like a well-structured approach.