Linux
Welcome to c/linux!
Welcome to our thriving Linux community! Whether you're a seasoned Linux enthusiast or just starting your journey, we're excited to have you here. Explore, learn, and collaborate with like-minded individuals who share a passion for open-source software and the endless possibilities it offers. Together, let's dive into the world of Linux and embrace the power of freedom, customization, and innovation. Enjoy your stay and feel free to join the vibrant discussions that await you!
Rules:
-
Stay on topic: Posts and discussions should be related to Linux, open source software, and related technologies.
-
Be respectful: Treat fellow community members with respect and courtesy.
-
Quality over quantity: Share informative and thought-provoking content.
-
No spam or self-promotion: Avoid excessive self-promotion or spamming.
-
No NSFW adult content
-
Follow general lemmy guidelines.
view the rest of the comments
I mean, it's basically an optional gecos field. That feels a bit like writing off *nix as a whole because /etc/passwd has a place to put your phone number.
It always starts off as optional as a form of normalization...Then gradually the boundaries are pushed until we get in a worse situation. So, I won't accept any form of age verification, optional or otherwise.
Yeah, with GECOS introducing the GECOS field, they normalized name verification, phone number verification, email address verification as well as location verification. So soon we should see those becoming mandatory and controlled.
Oh wait, that was 64 years ago, so by now we should already be in literally 1984, actually?! Or is it that no one actually gives a fuck about a handful of programs trying to read user data that no one set, and if they set it, set it to a nonsencial/false value without any component verifying anything?
The problem isn't libraries adding more optional field to their capabilites, but management systems (such as a distros installer) making them mandatory against user will. That is what users should actually object to. No installer or component I know actually sets the location field. However, some are already planing to require the birth of date field, which is the actual start to pushing any boundaries. So start protesting there.
Or, if you actually think that simple standards for how user data is stored is already malicious verification, your only option is probably, unironically, TempleOS, as even DOS stores user information, Country + TZ, available for other programs to fetch.
i would agree if this isn't open source. what you said is nearly impossible for open source software
Too true. And good on you.