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
The good side: I feel it might enables me to better setup parental control in the future. If software read from the age field, then the blocking can be more robust than a simple DNS sink hole by pihole, which is really easy to get around, with mobile data or directly visiting IP address.
I do find this field is fundamentally different from verification using government issued ID (yet). I will definitely fight the next one, but I am kind of okay with this one.
Cons: it is additional fingerprint parameter, I hope the xdg-desktop protocol can be implemented to give out as little information as possible for the age field, instead of just handing the birthday field to every app that ask for it. And I hope all adult who don't have any age-based content filtering needs will opt to leave the field empty.
I think xdg-desktop protocol was already rejected
Seems like this one still exists https://github.com/flatpak/xdg-desktop-portal/pull/1922
Its similar but not the same. Original was for input birthdate but this one is for specify general age group