WEBVTT
Kind: captions
Language: en

00:00:00.040 --> 00:00:05.700
In 2027, your operating system is going to ask you how old you are in California.

00:00:05.880 --> 00:00:13.740
Now, there was a Linux car vet, and there is a good, a bad, and an ugly angle to this.

00:00:13.980 --> 00:00:21.000
As the bill stands, Windows, Mac OS, iOS, Android will still be asking how old you are at setup in

00:00:21.200 --> 00:00:26.660
2027. Now, I live in California. I don't want this on any of my devices. And even if I'm running

00:00:26.680 --> 00:00:30.760
open source software, I don't think my non-technical friends and family should deal with these

00:00:31.100 --> 00:00:40.640
consequences. So AB 1856 passed 39 to 0 in the Senate and 69 to 0 on the Assembly concurrence,

00:00:40.710 --> 00:00:46.500
and it's on Newsom's desk unsigned at the time of recording. This is the version of an age law

00:00:46.500 --> 00:00:50.960
that people in my comments and myself previously were kind of asking for. It doesn't ask for any

00:00:51.110 --> 00:00:56.640
IDs. There's no birthdays. It's just age brackets that you self-report. The law requires the

00:00:56.660 --> 00:01:04.660
the operating system, that means Windows, macOS, iOS, to provide an interface at account setup that

00:01:04.900 --> 00:01:10.140
requires you, the account holder, to indicate your birth date, age, or both. Keep in mind,

00:01:10.140 --> 00:01:16.540
the word here is indicate, not verify, not authenticate, not validate. No ID, no passports,

00:01:16.770 --> 00:01:22.060
no selfies, no credit cards, no database checks. So the first thing that's said in here is that

00:01:22.020 --> 00:01:27.960
open source is out. The other good news is that the whole web nearly got pulled in and didn't.

00:01:27.960 --> 00:01:31.960
And I actually think that's the bigger win than just open source. Every website, every browser

00:01:32.360 --> 00:01:37.200
had this age bracketing scheme. So that's kind of the good. Now, the bad.

00:01:39.040 --> 00:01:43.760
The exemption lives in the definition of an operating system provider, right? That means

00:01:43.880 --> 00:01:48.540
you're an open source operating system. It's not in the definition of the developer. Again,

00:01:48.660 --> 00:01:50.060
based on my read of this.

00:01:50.100 --> 00:01:52.660
So that means if you're Brave Browser, ProtonVPN,

00:01:53.560 --> 00:01:54.760
ProtonPass, Onion Browser,

00:01:55.020 --> 00:01:56.420
literally any open source tool,

00:01:56.780 --> 00:01:59.440
all of those have to still request your age signal

00:01:59.780 --> 00:02:01.080
based on my read of this.

00:02:01.260 --> 00:02:02.780
And so I'm not really clear

00:02:02.860 --> 00:02:04.360
on how this is going to actually look

00:02:04.500 --> 00:02:06.300
for like an independent app developer

00:02:06.780 --> 00:02:07.860
who literally doesn't even wanna collect

00:02:08.060 --> 00:02:09.140
any data about its users.

00:02:09.340 --> 00:02:11.020
What the law is really trying to guarantee

00:02:11.160 --> 00:02:12.400
is that a developer can't say

00:02:12.500 --> 00:02:14.680
we didn't know a person's age.

00:02:15.140 --> 00:02:17.500
Once an app has legally been handed your age bracket,

00:02:17.740 --> 00:02:20.520
every other child safety law in the book starts applying to it.

00:02:20.520 --> 00:02:25.880
So this is kind of a gateway to allow many other things to be included in these apps

00:02:25.880 --> 00:02:27.940
that wouldn't normally be a part of the experience.

00:02:28.180 --> 00:02:33.660
So I look at this as more of opening up the floodgates to allow much worse things to happen,

00:02:33.960 --> 00:02:38.780
not necessarily this law per se being a direct problem.

00:02:39.060 --> 00:02:42.380
I really want to try to get that across because if you read this literally,

00:02:42.400 --> 00:02:46.040
it doesn't sound too bad, but when you see the kind of floodgates that get opened

00:02:46.400 --> 00:02:49.440
and the liability that gets put on individual developers,

00:02:50.000 --> 00:02:51.420
I start asking more questions.

00:02:51.720 --> 00:02:52.780
I'm not a legal expert,

00:02:52.860 --> 00:02:54.500
but again, these are the questions that I have

00:02:54.500 --> 00:02:55.220
when I'm reading this.

00:02:55.300 --> 00:02:57.540
Because this doesn't stop ID verification.

00:02:57.860 --> 00:02:59.280
It just doesn't require it.

00:02:59.360 --> 00:03:01.500
Now, I have more concerns in the ugly,

00:03:01.660 --> 00:03:03.600
but before then, a quick message from our sponsor.

00:03:04.640 --> 00:03:06.360
Real quick, because this fits into everything

00:03:06.420 --> 00:03:07.240
that we're talking about.

00:03:07.440 --> 00:03:09.300
We're basically being asked to prove

00:03:09.400 --> 00:03:11.000
who we are for everything now,

00:03:11.020 --> 00:03:13.700
and the money side of it is kind of the worst part.

00:03:14.080 --> 00:03:15.379
Think about how much of yourself

00:03:15.400 --> 00:03:20.140
you have to hand over just to move your money, even if it's a few dollars. Your ID, your face,

00:03:20.210 --> 00:03:24.680
your address, sometimes a reason for the transaction, all to just prove that you're

00:03:24.800 --> 00:03:29.620
allowed to spend your own money. And all of it gets logged and profiled alongside all your other

00:03:29.840 --> 00:03:34.600
data. But it really does not have to work that way. And one of the tools that I use to try to

00:03:34.780 --> 00:03:38.220
fight against this is CakeWallet. Now, a lot of people think CakeWallet's just for Monero,

00:03:38.290 --> 00:03:43.940
but it has Bitcoin, Litecoin, Zcash, Monero, all living in one free open source non-custodial app,

00:03:44.020 --> 00:03:47.980
which means it's your coins, no accounts, not even an email is required.

00:03:48.360 --> 00:03:51.560
And if you want to, they have CakePay, which lets you spend that currency

00:03:52.040 --> 00:03:55.520
almost virtually anywhere, whether in-store or online.

00:03:55.840 --> 00:03:58.000
The cool part is you wouldn't even realize that under the hood,

00:03:58.100 --> 00:04:00.280
it's running some of the best privacy technology out there

00:04:00.280 --> 00:04:02.360
and baking it right into each one of those coins.

00:04:02.660 --> 00:04:04.980
So it's not just Monero that gets to be private anymore.

00:04:05.400 --> 00:04:06.960
The other stuff gets some benefit too.

00:04:07.340 --> 00:04:08.820
For context, these things aren't hypothetical.

00:04:09.100 --> 00:04:13.139
The creator of CakeWallet, Vic, recently had his own Chase account temporarily frozen

00:04:13.160 --> 00:04:18.720
because he sent a $90 transaction to himself that they flagged as potential fraud. So why not use a

00:04:18.900 --> 00:04:23.040
technology that makes that impossible and puts you back in a driver's seat, all without needing

00:04:23.270 --> 00:04:27.740
your ID? Go download Cake Wallet and try it for yourself. Own your money and take back your

00:04:27.930 --> 00:04:32.260
privacy. It's completely free and open source at cakewallet.com. Or again, it's in the description.

00:04:32.630 --> 00:04:39.259
Now back to the video. To kick off the ugly, I want to refer to a comment that I've seen

00:04:39.260 --> 00:04:43.740
over and over, and it actually reflects a position that I used to have. That is that we can just

00:04:43.940 --> 00:04:48.200
solve this with technology. If we just have zero knowledge proofs, if something's privacy friendly,

00:04:48.720 --> 00:04:53.960
then it's fine. And guys, here's the thing. I would argue this law actually is better than

00:04:54.140 --> 00:04:58.780
zero knowledge proofs. This doesn't even require a birthday. It just hands them a bracket and you

00:04:58.880 --> 00:05:02.960
just have to say what the bracket is. Like nothing's actually verifying that you're telling the truth.

00:05:03.200 --> 00:05:07.499
And let's say that my concerns in the bad section don't pan out. Let's say liability is never really

00:05:07.520 --> 00:05:13.040
a thing. Let's say no bad issues come as a result of it. When we decide what parts of the internet

00:05:13.240 --> 00:05:19.420
or what apps or what data, what information can only be accessed by certain people, it already

00:05:19.800 --> 00:05:24.580
splits a parallel internet. We stop having a single internet that's one single source of truth.

00:05:25.060 --> 00:05:28.140
I was just talking about this with my partner before I was recording, and kind of the analogy

00:05:28.170 --> 00:05:32.880
I was using is, imagine a library, and now there was a law that libraries had to prevent kids from

00:05:32.900 --> 00:05:38.000
getting access to, let's just say, books that weren't fit for children, something broad like

00:05:38.160 --> 00:05:43.060
how these laws are written, then we have to start asking, okay, so what is considered not fit for

00:05:43.200 --> 00:05:47.380
children? Oh, how do we verify their ages? What about the 14-year-old that got into college and

00:05:47.460 --> 00:05:52.840
needs access to a book that adults normally get access to? Are adults able to rent a book on behalf

00:05:53.120 --> 00:05:57.720
of the kids? How are we going to verify their ages in a privacy-respecting manner? See, guys,

00:05:57.840 --> 00:05:59.860
this isn't actually a tech problem.

00:06:00.050 --> 00:06:02.340
We're trying to solve something

00:06:02.590 --> 00:06:04.360
in the technological landscape

00:06:04.600 --> 00:06:06.820
that's still ultimately a human problem.

00:06:07.320 --> 00:06:09.300
And it's this issue of freedom of information

00:06:09.780 --> 00:06:10.860
that is still applicable,

00:06:11.190 --> 00:06:13.260
even if we do it in a privacy-respecting way.

00:06:13.340 --> 00:06:15.920
So it's good that we got that open source exemption.

00:06:16.100 --> 00:06:17.000
I'm happy about it.

00:06:17.100 --> 00:06:19.680
That's why this video is titled Good, Bad, and Ugly.

00:06:20.040 --> 00:06:21.580
And this is one more reason

00:06:21.760 --> 00:06:23.560
that I can push people to start using Linux.

00:06:23.690 --> 00:06:24.880
And I mean that seriously.

00:06:24.910 --> 00:06:26.040
I think this is one more reason

00:06:26.050 --> 00:06:27.800
to start using open source operating systems

00:06:27.820 --> 00:06:29.560
You're less impacted by crap like this.

00:06:29.970 --> 00:06:31.020
But guys, what does that tell us?

00:06:31.220 --> 00:06:34.580
My channel isn't designed for just open source nerds.

00:06:34.660 --> 00:06:35.780
We do that.

00:06:35.870 --> 00:06:40.540
I still talk about those tools, but this is not just a you must use these two tools and

00:06:40.700 --> 00:06:42.820
everything else is garbage, screw you kind of channel.

00:06:43.060 --> 00:06:46.060
This is a channel where I still build an iOS privacy guide.

00:06:46.060 --> 00:06:48.120
I talk about making Windows more private.

00:06:48.540 --> 00:06:53.100
The goal is to make it so that anybody out there doesn't necessarily have to change their

00:06:53.210 --> 00:06:55.860
entire life just to gain a little bit of safety online.

00:06:56.200 --> 00:07:00.740
These laws actually target the people who are already most impacted by privacy and security

00:07:01.200 --> 00:07:05.520
issues who are not on open source tools, which I feel is double unfair to those individuals.

00:07:06.300 --> 00:07:12.440
Ultimately, my thesis slash main point to make is that this is actually the best version

00:07:12.680 --> 00:07:15.040
of this law I think we can possibly get.

00:07:15.380 --> 00:07:19.560
There are no IDs, no birthdays required, no biometrics.

00:07:19.840 --> 00:07:24.380
This is the exact thing that maybe me a year or two ago would have asked for.

00:07:24.480 --> 00:07:27.900
And it's the thing I see a lot of people in the comments ask for every time this comes up.

00:07:28.460 --> 00:07:33.000
And this still splits the internet into two, one that's censored and one that isn't.

00:07:33.320 --> 00:07:36.400
So I don't think that this is an argument anymore for better implementation.

00:07:37.260 --> 00:07:40.320
I think my argument just ultimately is against the whole idea.

00:07:40.860 --> 00:07:41.780
So that's kind of the thesis.

00:07:41.960 --> 00:07:45.140
But let's actually have some action steps, as I always like to finish these videos.

00:07:45.580 --> 00:07:47.340
First, go look at your devices right now.

00:07:47.500 --> 00:07:50.560
This already exists on iOS in different regions around the world.

00:07:50.920 --> 00:07:53.880
So check your settings, your Apple account, age range for apps.

00:07:54.320 --> 00:07:58.760
Most people watching this have no idea that settings already on and activated on their

00:07:58.920 --> 00:08:01.440
phone to make some easy swaps.

00:08:01.790 --> 00:08:02.500
Not everything.

00:08:02.670 --> 00:08:04.500
You don't have to move to Linux overnight.

00:08:04.870 --> 00:08:09.820
You can start with basic things like your browser, your VPN, your password manager.

00:08:10.260 --> 00:08:14.840
If these kind of tools are eventually going to have to start asking for your age bracket,

00:08:14.910 --> 00:08:19.000
you want to make sure you're using open source privacy respecting tools that are going to

00:08:19.220 --> 00:08:20.720
handle that data sensitively.

00:08:20.890 --> 00:08:23.760
Or maybe if we're lucky, they're not going to have to request that data at all.

00:08:23.940 --> 00:08:27.460
And if you want to know what these tools look like, I made a top encrypted services video that

00:08:27.890 --> 00:08:31.080
people really seem to enjoy and I think really gets people started on the right tools.

00:08:31.370 --> 00:08:34.060
So check that out down in the description or in the card.

00:08:34.419 --> 00:08:38.280
Three, and I know that people are critical of this, but I'm going to keep saying it.

00:08:38.419 --> 00:08:39.159
This does matter.

00:08:39.460 --> 00:08:44.300
Six months ago, this law literally had no open source exemption and it was going to cover

00:08:44.700 --> 00:08:47.240
every website and every browser in California.

00:08:47.660 --> 00:08:52.599
But developers and the EFF and many other people who got involved actually changed both of those

00:08:52.620 --> 00:08:58.520
things after the law was already signed. So reach out to companies, reach out to politicians,

00:08:59.280 --> 00:09:03.820
contact them, actually express how you feel about these things and not just in California,

00:09:04.200 --> 00:09:07.620
because this stuff is spreading all around the world. If you want to keep up with stories like

00:09:07.740 --> 00:09:10.980
this, you can join our newsletter down in the description. And if you like what we're doing,

00:09:11.420 --> 00:09:15.060
you can also support us directly. I have a private signal group so you can mingle with other people

00:09:15.110 --> 00:09:19.520
who are passionate about this. I also have an RSS feed that I personally maintain. So if you just

00:09:19.540 --> 00:09:24.500
want to keep up with this news. All the resources to do that are in the description. I want to thank

00:09:24.580 --> 00:09:28.120
you all for supporting us. If you already do, we couldn't do this without our Techlorians. And of

00:09:28.140 --> 00:09:32.320
course, I want to thank our sponsor, this video, Cake Wallet. And I will see you all next time on

00:09:32.460 --> 00:09:34.540
Techlore. Thank you for watching and don't forget to get involved.

