The Lemmy.zip Gaming Community

For news, discussions and memes!

Community Rules

This community follows the Lemmy.zip Instance rules, with the inclusion of the following rule:

No NSFW content

You can see Lemmy.zip's rules by going to our Code of Conduct.

What to Expect in Our Code of Conduct:

Respectful Communication: We strive for positive, constructive dialogue and encourage all members to engage with one another in a courteous and understanding manner.
Inclusivity: Embracing diversity is at the core of our community. We welcome members from all walks of life and expect interactions to be conducted without discrimination.
Privacy: Your privacy is paramount. Please respect the privacy of others just as you expect yours to be treated. Personal information should never be shared without consent.
Integrity: We believe in the integrity of speech and action. As such, honesty is expected, and deceptive practices are strictly prohibited.
Collaboration: Whether you're here to learn, teach, or simply engage in discussion, collaboration is key. Support your fellow members and contribute positively to shared learning and growth.

If you enjoy reading legal stuff, you can check it all out at legal.lemmy.zip.

founded 3 years ago

moderators

[–] Petter1@discuss.tchncs.de 5 points 6 months ago* (1 child)

I understand it like you have to force the user to input a date, but I see no requirement that this date has to be verified by the OS to be correct?

And if a user enters a date less than 18 years ago, another account with a date more than 18 years ago has to verify that date

So, what stops a user who is not 18 just enter an older date?

Each app just uses the date set in OS as verification, which honestly is better than each app having to ask for the date individually…

Don’t understand me wrong, I don’t like age verification at all, I would prefer a bill that forces the possibility to flag a user as “kid” and allow/deny categories like social media, payments, adult content, ads etc.
Like an extension of the admin/user setup we already have

And force websites and apps to respect headers/parameters like “denyCat=adult,social,payments,ads”

permalink

fedilink

source

hideshow 1 child comment

[–] a4ng3l@lemmy.world 5 points 6 months ago

See you highlight the issue yourself ; forcing the websites to expose data allowing an initial set of restrictions. Once those are in place extending them beyond the initial « doing the parent’s job » scope is trivial. The infrastructure will be available to block any content.

Once those headers become mandatory to deliver content the days to http freedom are over.

Eventually the system will enforce the correctness of such headers in a way that piracy will be added. Then assisted death and lgbtq topics; I saw propositions along those lines already.

I remember one of those discussions involving European isps representative ; who is to decide on those tags and which to block? Why would 16 yo not being able to discuss a topic or reach out for help on sensitive topics? At what age are they individually mature enough for those topics ?

permalink

fedilink

source

parent