this post was submitted on 22 May 2026
63 points (93.2% liked)
Privacy
5677 readers
328 users here now
Welcome! This is a community for all those who are interested in protecting their privacy.
Rules
PS: Don't be a smartass and try to game the system, we'll know if you're breaking the rules when we see it!
- Be civil and no prejudice
- Don't promote big-tech software
- No apathy and defeatism for privacy (i.e. "They already have my data, why bother?")
- No reposting of news that was already posted
- No crypto, blockchain, NFTs
- No Xitter links (if absolutely necessary, use xcancel)
Related communities:
Some of these are only vaguely related, but great communities.
- !opensource@programming.dev
- !selfhosting@slrpnk.net / !selfhosted@lemmy.world
- !piracy@lemmy.dbzer0.com
- !drm@lemmy.dbzer0.com
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
You've got it backwards. This is letting them frame the narrative. There's no need to tell anyone else anything about yourself when requesting content. The local device should be where any content filtering happens.
If you're in a kid mode, it should block the incoming content, not rely on a third party to give a shit about blocking itself.
No chance for "whoops we fascismed" that way
Also, my personal suggested approach leaves room for the OS not to disclose age and we're just back to the normal Y/N checkbox or calendar drop down on a website.
Finally, when a website tells the device the content is 18+, the device can't go "but wait, is it the kind of 18+ I'm okay with??" It'll still get blocked either way. End user effect will be the same.
Nothing about my proposal fixes fascism because they can always write a new law with more restrictions. Fascists gonna fascist, but without a working system, they can play the "protect the kids, give pornhub your full ID" card all day.
Except your yes/no it's what traps you in the block all or nothing scenario. Having local devices be able to filter based on content tags would be way easier to implement and allow for nuance.
We have already had keyword filtering for decades.
If I wanted to I can block it at the network, either thru the router or adguard home. Also like YouTube and other non porn/18+ sites do more harm than porn sites for kids.
Keyword filtering is complementary to but not a replacement for age tags. The problem with keywords is they are:
practically infinite, and thus almost impossible to keep on top of an allow/blocklist - you have to be technically savvy and well informed (which does not describe most of the population) to manage a tag list
basically saying you can just ignore laws you disagree with on content access
I agree that there should be more responsibility on parents not governments to decide what their kids can/cannot have access to, but I also am not full libertarian on this view - there is content that is well documented as being clinically inappropriate for children to access and should eb regulated IMO.
Just like we have seat belt or helmet laws, smoking/drinking ages, etc. not everything should be up for people to "do their own research" on, and negligent parents should not be giving their children carte blanche access to the internet.