Post #810156

The CA & CO laws are terrible and written by people who understand nothing to our field, fuck that, it sucks. It reeks silicon valley. I shall vomit. But see, my 10 yo daughter is running Arch (btw, she absolutely loves it), obviously administered by yours truly. She has (also obviously) no sudo powers. What I would like for her (and all other kids in the future) is adult websites to be *required* to identify themselves as such. It can be a header, a DNS record, a .well-known or something new but something simple. A "signal", as they call it, like the little growth bros they are. Then I want to locally configure her account as a child account (in userdb, for instance). Now, should resources be pulled from these websites, a *local* process would be able to block them, based on that local config. Of course, if a nsfw website failed to identify as nsfw, fines should be involved. I think this is what these bills should have been. But of course, they aren't. Protecting kids is not the purpose...