Don’t get me wrong, I’m all for privacy. But between setting up the birthdate when creating my children’s local account on their computers, and having to send a copy of their ID to every platform under the sun, I’d easily chose the former.
I’d even agree to a simple protocol (HTTP X-Over-18 / X-Over-21 headers?) to that.
It’s a slippery slope and also regulatory capture as the only ones with the means to actually pull this off are the Big Tech companies.
But between setting up the birthdate when creating my children’s local account on their computers, and having to send a copy of their ID to every platform under the sun, I’d easily chose the former.
That’s your decision. The rest of us shouldn’t be forced into it just because you’re to lazy to watch what your kids are doing online. If a website thinks they need to my my age they can ask me and I’ll decide if I want to provide it or not. I don’t want my OS just handing it out to anyone who asks.
Because I don’t give a shit what your kids do on the Internet, and there are already plenty of tools for you to curate the experience for them.
Because I should not have to. Im fine with them selling specially child computers that are listed as under 18 you can buy for your kids but I don’t want that crap on mine.
So
- Unenforceable
- Inaccurate
- Over-reaching
- PII not protected
What’s wrong with it then? By the numbers, it seems everything is wrong with it.
When you go order something from Amazon, you’re using about 15-20 computers in a row; probably more. PROVE you have the right. Yes, the server farm you’re using to make an order is included, and it’s a lot of machines.
Who pays to make sure Ticketmaster server farm is ‘used’ by age-appropriate customers and the code to check that is installed and maintained? Why, you, of course. The order panel at the burger joint? You, eventually. Toll ticket at Airport Parking? You’re gonna love this. Guess what’s in your cable box? Guess how often you’ll have to have your face scanned just to turn on the TV? TV too. Fancy thermostat? There’s a computer Nesting in there. Scan that face, bucko; on the new unit you have to buy because, dude, that and your microwave just became e-waste.
The list is unending. The implementation is shit. The data leak has already been shown with … discord, right?
Lots of the criticisms will eventually start sounding like seatbelt law opponents. Lots of “it should be optional, if you want to do it that’s fine but don’t force me to, I feel safer without it, it’s each individual’s responsibility and shouldn’t be mandated, etc” types of arguments.
The problem with the current implementation is that it isn’t done privately. There are several ways to do secure and private age verifications, where your device never passes your browsing history off to the government, and the individual sites never get your personal info. But lawmakers have been lobbied by companies who want to insert themselves as the age verifiers to skim your data. So the current laws being passed are written in such a way that they’ll result in massive privacy violations.
If opponents truly wanted to prevent privacy violations, they would be devising ways to get lawmakers on board with secure age verification. That way the laws would actually reflect best practices, and wouldn’t just result in less privacy. But they’re still trapped in the knee jerk “but my privacy” reactions, which shuts down any further discussion and leaves the door wide open for lobbyists to write and pass whatever legislation they want.
It’s not just a privacy issue. Regulatory capture is a problem too. It encumbers small services to the point where they can’t afford to exist, and the only winners are the walled gardens. And it’s also logistically an impossible thing to attempt to regulate at scale.
Are we sure parental control methods were proven to be fundamentally inadequate for the situation? There’s no bulletproof security method to guard this data, so the discussion is about weighing privacy loss vs child safety, against existing methods (or improving other methods). Also the choice to set the age is in the hands of the parent, so I don’t see the benefit besides enabling the kid to choose app in a more self served manner (which you probably don’t want to allow).
Seatbelts are there because it’s obvious you’re not in control of other drivers, even if your car has all the safety controls. The downsides are minuscule in comparison to the privacy discussion, in my opinion.
Slightly off topic, but I used DansGuardian when my kids were young. Works great.
Because it has little to do with protecting anyone and is another gross violation of privacy to serve corporate interests.
Show us your ID, then. Or even just your age. Now your children too.
Don’t want to? That’s why.
The issue with “children” local accounts (assuming they ever remained 100% local anyway) is that for it to be effective, you would have to control who install the OS for it to be effective.
I have been managing my own OS install since I was a teen, so I could have just created an adult account for me. But, okay, you could say that you could just regularly check your child hasn’t reinstalled the machine.
Well, see, they could just install a Virtual Machine. There is plenty of Virtual Machine software out there, and then we’re back at whoever installs it being responsible for filling in that information. And Virtual Machines are very useful for a bunch of things: from running software not made for your hardware (see Android emulators, WSL), to being safer around dodgy software.
You could counter that by not letting them install things with your permissions… but there are portable versions of software that people make for a bunch of reasons which don’t recall an installation. And I am not talking about hypotheticals: back when I was in school people would carry portable versions of games in USB sticks to copy around school machines so they could play video games during IT class.
Never mind that it means that whenever they want to install something, they will poke you about it, and now you’re on the hook for reviewing that. Which you should already be doing because you care about what your child does and they don’t have the years of experience to not break their OS.
But if you are doing that, why not use proper parental control software that let’s you have much finer-grained control over what they can see or not online, along with other controls around how much time they can spend on the machine and a few nicer things?
Its the principle for me
On the one hand, it is a privacy nightmare.
On the other hand, those laws are so badly written, they will apply to things you would never consider an issue. E.g. a security camera, a router, a NAS. For each of them, the law applies, because they have an OS, they are attached to a network, and they have logins. Think about it, and it basically applies to any network enabled device.
But between setting up the birthdate when creating my children’s local account on their computers, and having to send a copy of their ID to every platform under the sun, I’d easily chose the former.
This is how they move the goalpost. They changed the argument.
You currently can just create a local account - period. It’s yours. No tracking. No personal info.
But now you’re accepting that you’re willing to give a third party information, even just a little.
The next argument is: “If giving your age is okay, why not your home address?”
This is what police do to fish information out of you.
I’d even agree to a simple protocol (HTTP X-Over-18 / X-Over-21 headers?) to that.
In a era where privacy conscious people don’t even connect their TV to the internet… This is okay to you?
You went from “Why do they want my information?”
To
“I’m not concerned with sharing my age. But how should we do it?”
And that itself is the root issue.
Also this goalpost will move almost immediately. What if the parent doesn’t understand why the OS is asking for a DOB and they type whatever? What if the parent doesn’t log out and the kids use the adult account? What if the kid is really smart and bypasses the check (I think this could actually get bypassed easily)?
Rather than rolling back this rule they’ll just go even further and say the OS must analyze every action and utilize every input (e.g. microphone, camera) to determine the age of the current user and that controls need to be at the hardware level and OSes need to get state certified, etc. Before long only Windows, Apple, Google, and maybe RedHat can comply. An entire community of Linux enthusiasts destroyed. And as some bills have stated, rather vaguely, this can apply to something as simple as a calculator!
Also this goalpost will move almost immediately. What if the parent doesn’t understand why the OS is asking for a DOB and they type whatever?
Which we have already seen with content ratings. Instead of using the rating to inform themselves on what content to allow their child, they basically relied on the retailers/theatres not selling access to people below the age.
Having a gatekeeper behind what you can use on your own hardware is always bad.
Because they don’t care about your age. They want to tie you to your ID, so everything you say and do online can be tracked and tied to you as a person.
Meanwhile the leader of one of their countries has raped women and teenagers and even a couple of children, but they don’t do anything about it. But you can be jailed for decades for seeing a picture or video of it. But the actual act? They don’t care about that. (I’m saying you can be jailed for simply seeing CSAM online, but if you’re a billionaire actually doing the things, you won’t be tried for the actual CSA being recorded.)
So as you can see, it’s not your age, but your identity.
Most people think the Nazis only locked up Jews. Some realise they also locked up minorities. Historians know it was also anyone who disagreed with them. Anyone who spoke out against them. Anyone who wouldn’t wear the armband. And they’re afraid history will repeat. And they’re right to be afraid.
Most people think the Nazis only locked up Jews. Some realise they also locked up minorities.
They started with the impoverished, queer, and disabled.





