WEBVTT

00:00:04.044 --> 00:00:06.208
what we can learn from the viral nvidia

00:00:06.288 --> 00:00:08.891
saga graphene eleven graphene's pixel

00:00:08.971 --> 00:00:10.673
eleven support is finally possible

00:00:10.933 --> 00:00:13.257
asterisk and is it good that the average

00:00:13.317 --> 00:00:16.080
person doesn't care about privacy quite a

00:00:16.100 --> 00:00:17.844
hot take all this and more coming up

00:00:17.903 --> 00:00:19.225
on this week in privacy number seventy

00:00:19.265 --> 00:00:20.286
nine so stay tuned

00:00:42.017 --> 00:00:44.118
Welcome back to This Week in Privacy,

00:00:44.218 --> 00:00:46.039
our weekly series where we discuss the

00:00:46.079 --> 00:00:47.499
latest updates with what we've been

00:00:47.539 --> 00:00:49.539
working on within the Privacy Guides

00:00:49.560 --> 00:00:51.901
community and this week's top stories in

00:00:51.981 --> 00:00:54.902
data privacy and cybersecurity while

00:00:55.042 --> 00:00:56.603
answering viewer questions.

00:00:57.124 --> 00:00:59.104
I'm Jordan and this week with me is

00:00:59.405 --> 00:00:59.765
Nate.

00:01:00.384 --> 00:01:02.405
How's it going, Nate?

00:01:02.686 --> 00:01:03.826
Not so bad.

00:01:04.326 --> 00:01:04.887
I can't complain.

00:01:04.986 --> 00:01:05.686
Could be worse, right?

00:01:05.727 --> 00:01:06.227
Could be raining.

00:01:06.308 --> 00:01:06.768
How have you been?

00:01:07.810 --> 00:01:08.230
Yeah, good.

00:01:08.271 --> 00:01:10.734
Really excited to dive into the stories

00:01:10.754 --> 00:01:11.096
this week.

00:01:11.115 --> 00:01:13.560
We've definitely got some interesting ones

00:01:13.579 --> 00:01:14.040
this week.

00:01:14.281 --> 00:01:15.183
Very interesting.

00:01:16.795 --> 00:01:17.234
Really excited.

00:01:17.295 --> 00:01:18.575
Yeah, for sure.

00:01:19.536 --> 00:01:20.436
Let's go ahead and dive in.

00:01:20.837 --> 00:01:22.778
We're going to talk about the big story

00:01:22.817 --> 00:01:24.078
that everybody's been talking about this

00:01:24.117 --> 00:01:27.400
week, which is the NVIDIA scandal.

00:01:28.420 --> 00:01:29.980
But we are a privacy podcast,

00:01:30.021 --> 00:01:31.902
so we're not going to get into a

00:01:31.941 --> 00:01:33.423
lot of the juiciest details.

00:01:34.683 --> 00:01:35.724
We're going to kind of focus on what

00:01:35.763 --> 00:01:37.364
we can learn from a privacy and security

00:01:37.385 --> 00:01:38.025
perspective here.

00:01:38.846 --> 00:01:39.426
But believe it or not,

00:01:39.706 --> 00:01:40.466
I think even though,

00:01:41.108 --> 00:01:41.828
as far as I know,

00:01:41.948 --> 00:01:43.570
none of us watching are CEOs of

00:01:43.611 --> 00:01:45.111
billion-dollar, trillion-dollar companies,

00:01:46.453 --> 00:01:47.454
I think there's still something we can all

00:01:47.474 --> 00:01:47.655
learn.

00:01:47.694 --> 00:01:48.055
But anyways,

00:01:48.376 --> 00:01:49.677
so for any of you who have not

00:01:49.718 --> 00:01:50.278
heard this story,

00:01:50.317 --> 00:01:51.959
the headline here says – this comes from

00:01:52.040 --> 00:01:52.561
Ars Technica.

00:01:52.581 --> 00:01:52.781
It says,

00:01:52.861 --> 00:01:55.504
NVIDIA CEO's affair becomes a national

00:01:55.543 --> 00:01:56.525
security problem.

00:01:57.105 --> 00:01:57.346
And –

00:01:58.659 --> 00:01:59.381
There's, again,

00:01:59.441 --> 00:02:02.162
there's like a million different outlets

00:02:02.203 --> 00:02:02.942
covering this,

00:02:03.022 --> 00:02:04.284
and there's a million different angles to

00:02:04.323 --> 00:02:04.623
this,

00:02:05.004 --> 00:02:05.805
but we're going to try to keep it

00:02:05.844 --> 00:02:06.906
limited to privacy and security.

00:02:07.266 --> 00:02:09.087
So basically, NVIDIA's chief executive,

00:02:09.127 --> 00:02:09.788
Jensen Wang,

00:02:09.828 --> 00:02:11.789
has admitted to having an affair two days

00:02:11.870 --> 00:02:13.631
after the Financial Times reported his

00:02:13.751 --> 00:02:15.692
alleged romantic relationship with a woman

00:02:16.013 --> 00:02:16.393
the U.S.

00:02:16.413 --> 00:02:17.614
intelligence community believes was

00:02:17.653 --> 00:02:19.175
working as a spy for China.

00:02:19.615 --> 00:02:20.955
The Financial Times reported on Friday,

00:02:21.235 --> 00:02:23.418
for the record, Ars Technica just said FT.

00:02:23.497 --> 00:02:24.818
I'm assuming that's Financial Times,

00:02:24.838 --> 00:02:25.879
and I apologize if I get it wrong.

00:02:26.520 --> 00:02:28.001
The FT reported on Friday that the U.S.

00:02:28.020 --> 00:02:29.521
believed Wang had a romantic relationship

00:02:29.542 --> 00:02:30.842
with a Chinese woman who was recruited to

00:02:30.862 --> 00:02:32.484
spy for China's Ministry of State Security

00:02:32.563 --> 00:02:33.645
Intelligence Agency.

00:02:34.104 --> 00:02:35.526
American officials this year wrote a memo

00:02:35.566 --> 00:02:37.106
based on information from U.S.

00:02:37.127 --> 00:02:37.627
intelligence,

00:02:37.948 --> 00:02:39.188
which said the NVIDIA boss had been

00:02:39.209 --> 00:02:40.710
romantically involved with Alice Wang.

00:02:40.930 --> 00:02:41.469
No relation.

00:02:41.949 --> 00:02:42.510
That's actually,

00:02:43.170 --> 00:02:44.692
her name is something completely different

00:02:44.792 --> 00:02:45.793
in Chinese.

00:02:46.193 --> 00:02:47.614
That's just like an Americanized version

00:02:47.653 --> 00:02:48.014
of her name.

00:02:48.735 --> 00:02:49.996
An executive at Megaspeed,

00:02:50.015 --> 00:02:51.776
which is a Singapore-based customer of

00:02:51.917 --> 00:02:52.276
NVIDIA,

00:02:52.356 --> 00:02:53.557
according to people familiar with the

00:02:53.717 --> 00:02:54.079
document.

00:02:56.479 --> 00:02:57.180
Sorry, this isn't a quote.

00:02:57.219 --> 00:02:58.721
So yeah, most people, again,

00:02:58.741 --> 00:02:59.501
if you follow the news,

00:02:59.520 --> 00:03:00.861
you probably know the broad strokes of

00:03:00.882 --> 00:03:02.763
this story, as well as the memes.

00:03:03.462 --> 00:03:05.183
Since this original Ars Technica article

00:03:05.223 --> 00:03:05.683
came out,

00:03:06.144 --> 00:03:07.585
Wong has since admitted to having two

00:03:07.645 --> 00:03:09.405
additional affairs with NVIDIA employees

00:03:09.825 --> 00:03:11.445
and has since stepped down as CEO of

00:03:11.485 --> 00:03:11.846
NVIDIA,

00:03:11.885 --> 00:03:13.866
which I'm going to be a little bit

00:03:13.887 --> 00:03:15.848
snarky and say that's impressive that he

00:03:15.867 --> 00:03:17.528
can be carrying on with four women and

00:03:17.588 --> 00:03:19.770
run a company as CEO.

00:03:21.150 --> 00:03:22.131
I guess he's just not that busy at

00:03:22.151 --> 00:03:22.350
work.

00:03:22.450 --> 00:03:23.491
I've seen a lot of jokes about how

00:03:23.531 --> 00:03:24.852
we can replace him with AI, but...

00:03:25.451 --> 00:03:27.652
Uh, I'll, I'll, I'll get off the snark.

00:03:27.673 --> 00:03:27.832
I don't,

00:03:27.853 --> 00:03:28.973
I don't know if I've had enough coffee

00:03:28.993 --> 00:03:30.253
today for that or maybe too much coffee,

00:03:30.294 --> 00:03:31.555
but, um,

00:03:31.574 --> 00:03:33.514
I'm going to turn it over to Jordan.

00:03:33.936 --> 00:03:35.455
I know that it's a pretty short story,

00:03:35.515 --> 00:03:36.937
but I know, um,

00:03:36.977 --> 00:03:39.578
Jordan especially had a lot of thoughts on

00:03:39.598 --> 00:03:39.897
this one.

00:03:39.918 --> 00:03:40.639
So I'm going to turn it over to

00:03:40.679 --> 00:03:42.038
you and say, uh, again,

00:03:42.579 --> 00:03:44.280
most of us watching this are probably not

00:03:44.460 --> 00:03:46.281
CEOs and super high powered people.

00:03:46.320 --> 00:03:48.282
So what can the average person who is

00:03:48.502 --> 00:03:50.362
probably unlikely to be honeypotted by a

00:03:50.423 --> 00:03:52.343
state intelligence agency take away from

00:03:52.364 --> 00:03:53.243
this story in your opinion?

00:03:54.408 --> 00:03:54.669
I mean,

00:03:54.770 --> 00:03:56.492
I think the first thing that's kind of

00:03:56.552 --> 00:03:57.555
obvious to most people,

00:03:57.675 --> 00:03:59.217
I would hope is obvious,

00:03:59.338 --> 00:04:02.223
is that the biggest issue with

00:04:03.574 --> 00:04:07.455
security is almost never the actual

00:04:07.496 --> 00:04:08.216
software itself.

00:04:08.256 --> 00:04:10.056
It's actually a human that actually makes

00:04:10.076 --> 00:04:10.917
the mistake, right?

00:04:10.956 --> 00:04:12.578
So in this case,

00:04:12.717 --> 00:04:14.117
it was obviously we can't really relate

00:04:14.157 --> 00:04:16.519
this to the average person because like

00:04:16.559 --> 00:04:16.999
Nate said,

00:04:17.499 --> 00:04:19.339
you're not going to be targeted by like

00:04:19.379 --> 00:04:20.961
a state-sponsored spy, right,

00:04:21.120 --> 00:04:21.880
to be honeypotted.

00:04:21.901 --> 00:04:24.161
That's just never going to happen to the

00:04:24.201 --> 00:04:26.163
average person that doesn't have this

00:04:26.283 --> 00:04:28.184
level of unprecedented control, right?

00:04:28.884 --> 00:04:30.024
Because the person we're talking about,

00:04:30.084 --> 00:04:31.605
like NVIDIA is like,

00:04:32.084 --> 00:04:34.446
the largest or if not one of the

00:04:34.485 --> 00:04:36.086
largest companies in the world with,

00:04:36.166 --> 00:04:36.447
you know,

00:04:36.526 --> 00:04:39.348
quite a significant sway over massive

00:04:39.387 --> 00:04:41.069
industries right now, like AI,

00:04:41.408 --> 00:04:43.350
like data centers, just all of this stuff,

00:04:43.389 --> 00:04:43.629
right?

00:04:43.670 --> 00:04:45.250
So it makes sense that he was targeted

00:04:45.290 --> 00:04:45.831
in this way.

00:04:45.951 --> 00:04:48.512
But coming back to the actual, like,

00:04:49.512 --> 00:04:51.273
takeaways that are actually useful for

00:04:51.312 --> 00:04:51.913
people, right?

00:04:53.214 --> 00:04:53.415
You know,

00:04:54.095 --> 00:04:55.896
the main concern that I think most people

00:04:55.916 --> 00:04:58.538
should be should be concerned about is is

00:04:58.579 --> 00:04:59.158
the human link,

00:04:59.178 --> 00:05:01.079
because that's in a lot of ways the

00:05:01.100 --> 00:05:03.242
way that people do get exploited right

00:05:03.302 --> 00:05:05.242
through, you know,

00:05:05.283 --> 00:05:07.064
phishing attacks and all sorts of things

00:05:07.084 --> 00:05:09.887
like this instead of like, you know.

00:05:10.968 --> 00:05:12.610
vulnerability in the software that you use

00:05:12.629 --> 00:05:14.971
getting exploited by some hacker right

00:05:15.012 --> 00:05:17.694
because that's just less likely for a

00:05:17.735 --> 00:05:19.377
single individual to be targeted in that

00:05:19.416 --> 00:05:21.778
way um so i think in this case

00:05:21.819 --> 00:05:24.682
like this one guy who as far as

00:05:24.701 --> 00:05:27.185
we know has like pretty pretty he has

00:05:27.264 --> 00:05:29.487
access to pretty confidential information

00:05:29.507 --> 00:05:32.629
within the company getting targeted by um

00:05:32.911 --> 00:05:33.130
you know

00:05:34.528 --> 00:05:37.209
state-sponsored spies is it makes a lot

00:05:37.228 --> 00:05:38.149
more sense than, you know,

00:05:38.209 --> 00:05:40.411
someone trying to actually exploit

00:05:40.451 --> 00:05:43.673
someone's device because, you know,

00:05:43.692 --> 00:05:45.093
I'm sure that he has personal and

00:05:45.153 --> 00:05:46.973
professional devices lying around and

00:05:47.014 --> 00:05:48.754
that's another vector that could have been

00:05:48.795 --> 00:05:49.495
exploited, right?

00:05:49.516 --> 00:05:49.755
You know,

00:05:49.776 --> 00:05:52.357
just plugging a USB that exploits it.

00:05:52.896 --> 00:05:54.817
Having physical access to devices that

00:05:54.858 --> 00:05:56.999
have sensitive information on them is much

00:05:57.059 --> 00:05:58.980
easier than trying to find like a zero

00:05:59.019 --> 00:06:01.221
day to hack someone's device or whatever,

00:06:01.281 --> 00:06:01.521
right?

00:06:01.541 --> 00:06:01.641
So

00:06:02.302 --> 00:06:04.370
think that's like the main the main thing

00:06:04.389 --> 00:06:05.714
that people should be thinking about right

00:06:05.795 --> 00:06:07.822
is like how

00:06:09.081 --> 00:06:12.403
are there vectors that are more easily

00:06:12.444 --> 00:06:14.625
exploitable that you should be more

00:06:14.665 --> 00:06:15.565
concerned about, right?

00:06:15.605 --> 00:06:18.208
So I don't think the average person needs

00:06:18.228 --> 00:06:20.009
to worry a huge amount about someone

00:06:20.048 --> 00:06:21.410
trying to exploit their device in that

00:06:21.430 --> 00:06:21.629
way.

00:06:21.689 --> 00:06:23.831
But I think just basic security tips,

00:06:23.850 --> 00:06:25.711
like don't plug a USB you find on

00:06:25.732 --> 00:06:27.593
the ground into your computer,

00:06:28.213 --> 00:06:28.874
stuff like this.

00:06:29.834 --> 00:06:30.514
So I don't know.

00:06:30.555 --> 00:06:33.677
This is one of these stories where it's

00:06:34.076 --> 00:06:37.660
very based on the person's actual

00:06:37.680 --> 00:06:38.199
experience

00:06:38.399 --> 00:06:40.300
access to confidential information.

00:06:40.380 --> 00:06:41.401
So, you know,

00:06:42.002 --> 00:06:44.802
it's it's much more it's much less likely

00:06:44.843 --> 00:06:46.483
for that to be a concern for like

00:06:46.524 --> 00:06:48.285
people that are watching this podcast or

00:06:49.185 --> 00:06:50.125
the average person.

00:06:50.185 --> 00:06:50.685
Right.

00:06:50.725 --> 00:06:53.146
So I guess I can throw it back

00:06:53.187 --> 00:06:55.208
to you, Nate.

00:06:55.247 --> 00:06:58.468
Like this could possibly be somewhat of a

00:06:58.528 --> 00:06:59.769
national security concern.

00:06:59.810 --> 00:07:00.029
Right.

00:07:00.050 --> 00:07:02.550
Like because there's so many of these

00:07:02.591 --> 00:07:05.612
chips everywhere and they're in, you know,

00:07:06.012 --> 00:07:06.632
so many things.

00:07:06.853 --> 00:07:06.992
Right.

00:07:08.507 --> 00:07:09.247
Yeah,

00:07:10.949 --> 00:07:12.269
I don't really keep up with that side

00:07:12.310 --> 00:07:14.971
of politics to be honest with you.

00:07:14.990 --> 00:07:15.271
But yeah,

00:07:15.331 --> 00:07:18.574
I know there's – I think it's more

00:07:18.593 --> 00:07:20.894
of an economic competitive thing,

00:07:20.915 --> 00:07:22.196
which I mean I guess sure.

00:07:22.295 --> 00:07:24.577
I could see how you can draw it

00:07:24.598 --> 00:07:26.999
back to China's military strength as well.

00:07:28.500 --> 00:07:29.500
And I'm not saying it's like a far

00:07:29.540 --> 00:07:29.761
fetch.

00:07:29.800 --> 00:07:31.322
I'm just saying like I think it's mostly

00:07:31.322 --> 00:07:33.483
– the US is being really strict right

00:07:33.524 --> 00:07:35.125
now about where chips can be sold.

00:07:36.161 --> 00:07:40.163
Um, because, uh, yeah, because we're,

00:07:40.264 --> 00:07:41.704
we're trying to stay ahead of China in

00:07:41.764 --> 00:07:42.846
the AI arms race.

00:07:42.906 --> 00:07:45.247
And, um, I've, I don't know, I'm not,

00:07:45.387 --> 00:07:45.567
I,

00:07:45.607 --> 00:07:46.687
when I say I don't really keep up

00:07:46.728 --> 00:07:47.528
on it very well as like,

00:07:47.928 --> 00:07:49.288
I know that Nvidia wasn't supposed to sell

00:07:49.309 --> 00:07:50.009
chips to China,

00:07:50.470 --> 00:07:53.572
but then I think like Jensen Wong

00:07:53.651 --> 00:07:54.812
convinced Trump to like,

00:07:54.831 --> 00:07:55.812
give them some kind of.

00:07:56.175 --> 00:07:56.995
exception.

00:07:57.536 --> 00:07:59.137
And now I just saw a story or

00:07:59.158 --> 00:07:59.798
a headline today.

00:07:59.817 --> 00:08:00.718
I didn't read the whole story,

00:08:00.738 --> 00:08:02.060
but I saw a headline about how like

00:08:02.620 --> 00:08:03.961
thousands of chips have turned up in

00:08:04.002 --> 00:08:05.002
certain Chinese hardware.

00:08:05.023 --> 00:08:05.923
And everybody's like, Hey,

00:08:05.983 --> 00:08:06.805
what happened in video?

00:08:06.845 --> 00:08:07.526
How did this happen?

00:08:07.545 --> 00:08:09.286
And I'm like, I'm personally sitting here.

00:08:09.307 --> 00:08:09.827
I'm like, I don't know.

00:08:09.848 --> 00:08:10.869
Didn't you guys say he could, I just,

00:08:11.608 --> 00:08:12.189
but maybe those,

00:08:12.389 --> 00:08:13.531
he wasn't supposed to sell those chips.

00:08:13.550 --> 00:08:13.911
I don't know.

00:08:13.951 --> 00:08:16.033
But yeah, it's, um, I mean, it's,

00:08:16.634 --> 00:08:18.014
I know this isn't really a, what,

00:08:18.095 --> 00:08:19.817
what we're talking about here, but, uh,

00:08:21.261 --> 00:08:24.083
The supply chain of chips is extremely

00:08:24.122 --> 00:08:24.923
precarious right now,

00:08:24.963 --> 00:08:25.903
in case you guys didn't know.

00:08:27.105 --> 00:08:28.285
So yeah, I mean, in a way,

00:08:28.345 --> 00:08:28.685
I think...

00:08:30.125 --> 00:08:31.166
I guess what I'm getting at is I

00:08:31.206 --> 00:08:33.408
feel like national security is not the

00:08:33.568 --> 00:08:34.369
only concern there.

00:08:34.389 --> 00:08:35.149
But yeah, I mean,

00:08:35.269 --> 00:08:37.650
it is a big concern that somebody this

00:08:37.691 --> 00:08:37.870
big,

00:08:37.890 --> 00:08:39.552
that this industry that is so centralized,

00:08:39.591 --> 00:08:40.952
which is, of course, not a good thing,

00:08:41.153 --> 00:08:41.653
I would argue.

00:08:43.794 --> 00:08:45.535
I mean, if somebody had access to...

00:08:46.235 --> 00:08:47.716
jensen wong and i feel like i've said

00:08:47.736 --> 00:08:49.739
this on the show before like generally

00:08:49.759 --> 00:08:51.159
speaking china has a very different

00:08:51.200 --> 00:08:52.541
version of military intelligence than the

00:08:52.640 --> 00:08:54.581
u.s and western countries western

00:08:54.621 --> 00:08:55.883
countries tend to focus on like how many

00:08:55.923 --> 00:08:57.323
troops do you have where they're deployed

00:08:57.543 --> 00:08:59.325
uh how many tanks do you have what

00:08:59.524 --> 00:09:01.866
military technology do you have and china

00:09:01.886 --> 00:09:03.427
cares about that stuff too but they also

00:09:03.467 --> 00:09:05.308
generally tend to care about the big

00:09:05.349 --> 00:09:06.870
picture like what is um

00:09:07.818 --> 00:09:08.278
you know, what,

00:09:08.298 --> 00:09:09.620
what does life look like for the average

00:09:09.700 --> 00:09:11.860
everyday American or German?

00:09:12.361 --> 00:09:14.143
And so even if she wasn't necessarily like

00:09:14.182 --> 00:09:17.424
stealing chip secrets from him, you know,

00:09:17.485 --> 00:09:19.066
it's still just having access to someone

00:09:19.145 --> 00:09:21.746
that powerful is definitely concerning

00:09:21.787 --> 00:09:23.087
from a national security perspective.

00:09:23.128 --> 00:09:23.567
Sure.

00:09:23.607 --> 00:09:27.009
So I don't know if that answered your

00:09:27.049 --> 00:09:28.410
question very well, but yeah, it's,

00:09:28.490 --> 00:09:29.051
it's a,

00:09:29.110 --> 00:09:30.532
I think there's a lot of angles to

00:09:30.572 --> 00:09:31.131
this and that's,

00:09:31.232 --> 00:09:32.352
I think that's why it's been such a

00:09:32.373 --> 00:09:33.533
big story.

00:09:33.594 --> 00:09:33.714
So.

00:09:34.384 --> 00:09:34.644
Right.

00:09:34.764 --> 00:09:36.225
I think also the other thing is just,

00:09:36.245 --> 00:09:36.544
you know,

00:09:36.585 --> 00:09:38.385
we see a lot of these big like

00:09:38.466 --> 00:09:41.927
elite tech CEOs who we just keep seeing

00:09:41.967 --> 00:09:42.707
it over and over again.

00:09:42.748 --> 00:09:44.349
Like they're not really following good

00:09:44.428 --> 00:09:45.610
operational security.

00:09:45.669 --> 00:09:47.850
They're like kind of being a little loose

00:09:48.791 --> 00:09:49.711
with things, you know.

00:09:50.432 --> 00:09:52.413
So it is kind of interesting.

00:09:52.452 --> 00:09:53.894
Like I think this is one thing that

00:09:53.913 --> 00:09:55.573
like organizations should probably take

00:09:55.634 --> 00:09:55.955
note on.

00:09:55.995 --> 00:09:57.115
Like, you know,

00:09:57.754 --> 00:09:59.135
probably do a little bit of like

00:09:59.556 --> 00:10:01.777
background vetting on people that,

00:10:02.018 --> 00:10:02.258
you know,

00:10:03.518 --> 00:10:05.158
that have significant access to the

00:10:05.178 --> 00:10:05.798
company, right?

00:10:05.980 --> 00:10:07.220
I don't know if that's,

00:10:07.360 --> 00:10:08.221
maybe that's too far,

00:10:08.280 --> 00:10:09.902
but like I feel like if it's such

00:10:09.922 --> 00:10:12.043
a huge company with like such a massive

00:10:12.102 --> 00:10:13.923
sway on, like you said,

00:10:13.964 --> 00:10:15.203
like it is like an economic,

00:10:15.725 --> 00:10:16.725
it's an economic thing.

00:10:18.186 --> 00:10:19.927
who has access to the chips, basically,

00:10:21.067 --> 00:10:22.548
who can build AI faster,

00:10:22.769 --> 00:10:25.490
which is currently kind of the situation,

00:10:25.530 --> 00:10:25.910
at least.

00:10:27.312 --> 00:10:27.851
So, yeah,

00:10:27.932 --> 00:10:30.153
I think definitely some more security

00:10:30.193 --> 00:10:31.595
policies could have been in place with

00:10:31.615 --> 00:10:32.394
that, like, you know.

00:10:32.995 --> 00:10:35.817
And, yeah, I'm not really...

00:10:36.256 --> 00:10:37.597
I don't really have too many thoughts,

00:10:37.697 --> 00:10:39.298
like, about the politics of this, because,

00:10:39.339 --> 00:10:40.120
again, this isn't, like,

00:10:40.139 --> 00:10:41.000
a political podcast.

00:10:41.039 --> 00:10:42.922
We're just talking about the privacy and

00:10:42.961 --> 00:10:44.042
security issues here.

00:10:44.783 --> 00:10:45.903
So I think...

00:10:46.764 --> 00:10:48.664
that's sort of like everything that I

00:10:48.705 --> 00:10:50.625
think can be taken away from the

00:10:50.645 --> 00:10:51.206
situation.

00:10:51.567 --> 00:10:51.726
Um,

00:10:53.427 --> 00:10:55.188
as far as like takeaways for like the

00:10:55.229 --> 00:10:57.811
average person, I think just, yeah,

00:10:57.931 --> 00:11:00.913
being more skeptical of a lot of things

00:11:00.932 --> 00:11:04.174
that you see, um, you know,

00:11:04.215 --> 00:11:05.676
humans are the weakest link, like,

00:11:05.696 --> 00:11:05.895
you know,

00:11:05.916 --> 00:11:07.437
phishing links and stuff like that.

00:11:07.976 --> 00:11:09.258
Uh, social engineering,

00:11:09.337 --> 00:11:10.278
all sorts of things like that.

00:11:10.318 --> 00:11:10.619
That's

00:11:11.078 --> 00:11:13.440
something that the average person can be

00:11:14.541 --> 00:11:15.601
targeted by.

00:11:16.322 --> 00:11:16.662
In the end,

00:11:16.701 --> 00:11:18.602
this was like a social engineering attack

00:11:18.623 --> 00:11:21.845
in some ways, because this lady,

00:11:21.924 --> 00:11:24.746
she used her ability to

00:11:25.643 --> 00:11:26.183
you know,

00:11:26.203 --> 00:11:28.206
get into a romantic relationship with the

00:11:28.245 --> 00:11:30.908
CEO to gain access to privileged

00:11:30.948 --> 00:11:31.509
information.

00:11:31.570 --> 00:11:33.493
So that is social engineering in a way.

00:11:34.693 --> 00:11:36.917
And it's certainly possible that someone

00:11:36.937 --> 00:11:38.018
could do the same thing to you,

00:11:38.077 --> 00:11:41.642
but I think it's less of a concern

00:11:41.702 --> 00:11:43.504
for people that don't have access to,

00:11:43.764 --> 00:11:45.287
you know, such a huge corporation.

00:11:47.644 --> 00:11:48.326
Yeah, for sure.

00:11:49.267 --> 00:11:50.308
We did have a couple of questions.

00:11:50.328 --> 00:11:52.211
Somebody commented about the interim CEO.

00:11:52.230 --> 00:11:55.154
I don't know much about her.

00:11:55.336 --> 00:11:57.359
I saw that apparently she was like one

00:11:57.379 --> 00:11:59.861
of the few people in the C-suite who

00:12:00.001 --> 00:12:01.583
was willing to push back on Jensen's

00:12:01.644 --> 00:12:02.605
ideas.

00:12:02.666 --> 00:12:03.147
Yeah.

00:12:04.543 --> 00:12:04.864
I don't know.

00:12:05.144 --> 00:12:06.345
The way that I read that article was

00:12:06.384 --> 00:12:08.886
like in a very adversarial sort of way.

00:12:08.986 --> 00:12:10.607
But that's in my opinion,

00:12:10.648 --> 00:12:11.548
that's a good thing at a company,

00:12:11.609 --> 00:12:12.970
especially when you have somebody like

00:12:12.990 --> 00:12:14.191
Jensen Wong, who's got this like,

00:12:14.530 --> 00:12:14.890
all right,

00:12:15.091 --> 00:12:16.652
we're going to aim for like screw the

00:12:16.672 --> 00:12:16.831
moon.

00:12:16.851 --> 00:12:17.812
We're going to aim for Jupiter.

00:12:17.932 --> 00:12:18.874
And somebody is like, OK,

00:12:18.953 --> 00:12:19.874
and how are we going to get out

00:12:19.894 --> 00:12:20.554
of the atmosphere?

00:12:20.735 --> 00:12:21.335
Like,

00:12:21.434 --> 00:12:22.316
I think that's a good thing to have

00:12:22.336 --> 00:12:22.755
in a person.

00:12:22.796 --> 00:12:24.017
But I don't know much about her.

00:12:24.116 --> 00:12:25.697
I don't know much about her connections or

00:12:26.219 --> 00:12:26.418
her.

00:12:27.259 --> 00:12:28.820
I know she's the CFO,

00:12:28.860 --> 00:12:29.701
the financial officer.

00:12:29.721 --> 00:12:30.741
So I don't know.

00:12:30.841 --> 00:12:32.623
I don't I don't really have an opinion

00:12:32.702 --> 00:12:33.744
on that story personally.

00:12:34.845 --> 00:12:36.245
um i don't know if you have anything

00:12:36.386 --> 00:12:39.090
to say about that um somebody said in

00:12:39.110 --> 00:12:43.956
the chat uh they missed the mastodon live

00:12:43.975 --> 00:12:46.158
stream oh yeah i think i might have

00:12:46.239 --> 00:12:48.260
accidentally scheduled it for tomorrow

00:12:48.321 --> 00:12:50.443
instead of today um i think they just

00:12:50.464 --> 00:12:52.346
said they see it now so they see

00:12:52.365 --> 00:12:53.727
it now okay um

00:12:54.317 --> 00:12:54.857
Yeah, no,

00:12:55.258 --> 00:12:56.639
I'm not sure what happened there.

00:12:57.278 --> 00:12:57.500
Again,

00:12:57.539 --> 00:12:59.039
like it is kind of tricky with time

00:12:59.059 --> 00:12:59.200
zones.

00:12:59.240 --> 00:13:00.480
Like for me, it's Saturday.

00:13:00.821 --> 00:13:01.802
For Nate, it's Friday.

00:13:03.182 --> 00:13:05.482
It's a completely different like it's like

00:13:05.503 --> 00:13:06.264
a different day.

00:13:06.923 --> 00:13:08.345
So sometimes it does get confusing.

00:13:08.865 --> 00:13:09.865
So sorry about that.

00:13:09.905 --> 00:13:10.745
If you didn't see that,

00:13:11.466 --> 00:13:12.547
it should be it should be live now.

00:13:13.447 --> 00:13:15.107
And then like our scheduling software for

00:13:15.148 --> 00:13:17.668
some reason doesn't always switch time

00:13:17.707 --> 00:13:19.269
zones like mine is set to the wrong

00:13:19.308 --> 00:13:19.869
time zone.

00:13:20.948 --> 00:13:22.090
Only by like an hour but I didn't

00:13:22.110 --> 00:13:23.230
know that one time I think I was

00:13:23.250 --> 00:13:24.690
filling in for you so I like scheduled

00:13:24.710 --> 00:13:25.571
all the posts and everything.

00:13:26.091 --> 00:13:27.610
And it like posted halfway through the

00:13:27.671 --> 00:13:29.371
podcast because I didn't realize I was an

00:13:29.412 --> 00:13:30.172
hour off so.

00:13:32.706 --> 00:13:32.807
Yeah.

00:13:32.868 --> 00:13:32.988
Yeah.

00:13:33.048 --> 00:13:35.788
I schedule the posts using the US time.

00:13:35.868 --> 00:13:37.288
And then in the actual app,

00:13:37.328 --> 00:13:38.908
it shows the Australian time.

00:13:38.948 --> 00:13:40.850
It's like, ah, it's confusing.

00:13:40.889 --> 00:13:42.009
It's really confusing.

00:13:42.090 --> 00:13:43.629
So I'm sorry if that happens.

00:13:44.770 --> 00:13:47.731
So yes, again, apologies for that.

00:13:48.231 --> 00:13:49.072
But it should be live now.

00:13:50.798 --> 00:13:50.958
Yeah.

00:13:51.019 --> 00:13:52.039
And then last one, um,

00:13:52.059 --> 00:13:53.321
somebody asked if we think prices are

00:13:53.341 --> 00:13:54.883
going to come down like prices of Ram.

00:13:54.903 --> 00:13:56.024
Uh, I doubt it,

00:13:56.124 --> 00:13:57.845
but I know Nvidia stock price has already

00:13:57.865 --> 00:13:58.105
fallen.

00:13:58.145 --> 00:13:59.025
I'm sure it'll bounce back.

00:13:59.226 --> 00:13:59.527
I don't know.

00:14:00.106 --> 00:14:01.148
We'll, uh, we'll see what the new,

00:14:01.749 --> 00:14:04.390
new CFO slash CEO intern CEO does.

00:14:04.791 --> 00:14:06.413
So, um,

00:14:07.711 --> 00:14:08.591
Yeah, I don't know.

00:14:09.793 --> 00:14:10.774
I think that's all I've got on that

00:14:10.813 --> 00:14:11.094
story.

00:14:11.153 --> 00:14:12.554
Somebody said there's stories coming out

00:14:12.575 --> 00:14:15.096
about how there's far more RAM and GPU

00:14:15.136 --> 00:14:16.759
silicon supply than there is demand.

00:14:16.778 --> 00:14:18.100
And that implies current price gouging is

00:14:18.120 --> 00:14:18.941
entirely artificial.

00:14:18.980 --> 00:14:19.301
You know what?

00:14:19.380 --> 00:14:20.442
It honestly wouldn't surprise me.

00:14:20.581 --> 00:14:21.243
I haven't heard that.

00:14:21.283 --> 00:14:21.582
But I mean,

00:14:21.643 --> 00:14:23.063
we know that the diamond industry has done

00:14:23.083 --> 00:14:23.323
that.

00:14:24.465 --> 00:14:24.605
I mean,

00:14:24.625 --> 00:14:26.006
a lot of industries have done that,

00:14:26.126 --> 00:14:27.668
including ones you would be very surprised

00:14:27.707 --> 00:14:27.908
by.

00:14:27.967 --> 00:14:29.769
So I don't have a comment,

00:14:29.809 --> 00:14:31.610
but it absolutely would not surprise me

00:14:31.630 --> 00:14:31.971
personally.

00:14:32.653 --> 00:14:36.057
But unless you have anything else to add

00:14:36.097 --> 00:14:36.658
to that one,

00:14:37.438 --> 00:14:38.379
I've been keeping an eye on some of

00:14:38.399 --> 00:14:38.899
the chats.

00:14:38.961 --> 00:14:41.043
We don't have any questions in the forum

00:14:41.082 --> 00:14:43.384
yet or the Signal chat.

00:14:44.265 --> 00:14:45.147
I don't think there's been anything in

00:14:45.167 --> 00:14:45.807
Fluxer either.

00:14:45.908 --> 00:14:48.470
So I think we can probably move on

00:14:48.509 --> 00:14:50.753
to our first forum post, if you're ready.

00:14:51.831 --> 00:14:52.152
Awesome.

00:14:52.172 --> 00:14:53.533
Yeah, let's dive into this forum post.

00:14:53.572 --> 00:14:55.594
So as usual, just so everyone knows,

00:14:56.354 --> 00:14:57.653
we do have a community forum at

00:14:57.693 --> 00:14:59.534
discuss.privacyguides.net.

00:14:59.634 --> 00:15:01.716
And we usually talk about like, you know,

00:15:01.735 --> 00:15:03.897
two or three posts that we see every

00:15:03.937 --> 00:15:04.157
week.

00:15:04.216 --> 00:15:07.778
So this one here is about someone who's

00:15:07.818 --> 00:15:09.318
having an issue with a ring camera.

00:15:09.458 --> 00:15:10.240
So the title is,

00:15:10.340 --> 00:15:11.919
my new apartment neighbor installed a ring

00:15:11.940 --> 00:15:13.921
camera pointed directly at my door.

00:15:14.360 --> 00:15:15.062
What should I do?

00:15:15.822 --> 00:15:17.182
My city has a high crime rate,

00:15:17.222 --> 00:15:18.664
but I live in a very safe area

00:15:19.245 --> 00:15:21.386
of town in a suburban apartment complex.

00:15:21.447 --> 00:15:23.328
My building is in the back part of

00:15:23.349 --> 00:15:25.191
the complex, furthest from the road.

00:15:26.851 --> 00:15:27.812
I'm just going to skip some of this

00:15:27.832 --> 00:15:29.955
because I don't want to publicly share

00:15:29.995 --> 00:15:31.476
exactly everything about what they said

00:15:31.496 --> 00:15:32.758
because of privacy reasons.

00:15:35.192 --> 00:15:36.773
I've lived here for years and never had

00:15:36.812 --> 00:15:38.014
any concerns about safety.

00:15:38.374 --> 00:15:40.054
Neighbors have left packages by their door

00:15:40.075 --> 00:15:42.375
for days in plain sight and nothing goes

00:15:42.416 --> 00:15:42.735
missing.

00:15:43.037 --> 00:15:44.537
You're more likely to get a letter from

00:15:44.576 --> 00:15:46.899
management threatening fines for creating

00:15:46.958 --> 00:15:49.440
an eyesore by leaving packages out than to

00:15:49.480 --> 00:15:50.620
have a package stolen.

00:15:51.201 --> 00:15:53.201
A new neighbor directly across the hall

00:15:53.221 --> 00:15:53.643
moved in.

00:15:54.003 --> 00:15:55.202
I haven't actually met them yet,

00:15:55.263 --> 00:15:57.284
but they installed a ring camera and

00:15:57.345 --> 00:15:59.105
they're the only unit that has a camera

00:15:59.125 --> 00:16:00.365
doorbell in my building.

00:16:00.886 --> 00:16:02.707
I've noticed a few camera doorbells in

00:16:02.847 --> 00:16:03.388
other buildings,

00:16:03.467 --> 00:16:05.549
but ninety nine percent of units don't

00:16:05.570 --> 00:16:06.169
have a camera.

00:16:06.590 --> 00:16:08.390
The camera points directly at my door,

00:16:08.530 --> 00:16:10.692
my window and my outdoor closet.

00:16:11.232 --> 00:16:12.274
I can't open my door,

00:16:12.734 --> 00:16:14.955
open my blinds or open my closet without

00:16:14.975 --> 00:16:15.696
being recorded.

00:16:15.956 --> 00:16:17.697
What do you people suggest that I do?

00:16:19.758 --> 00:16:20.837
This is really tricky.

00:16:21.219 --> 00:16:23.698
This is one of these circumstances where

00:16:23.839 --> 00:16:29.802
it's sort of a human issue and you

00:16:29.822 --> 00:16:32.842
can't really solve that simply.

00:16:32.942 --> 00:16:33.302
Right.

00:16:34.043 --> 00:16:35.484
I think basically most people are

00:16:35.504 --> 00:16:36.984
suggesting, you know,

00:16:37.024 --> 00:16:38.585
talking to the neighbor,

00:16:38.625 --> 00:16:40.304
trying to be good faith,

00:16:40.365 --> 00:16:42.186
trying to actually be reasonable.

00:16:43.186 --> 00:16:45.927
in your request and try and find,

00:16:46.086 --> 00:16:46.287
you know,

00:16:46.326 --> 00:16:49.048
a compromise between so you can both be

00:16:49.087 --> 00:16:49.788
happy, right?

00:16:50.307 --> 00:16:51.889
You can have the camera mounted in a

00:16:51.928 --> 00:16:54.489
way where it doesn't film your direct

00:16:54.568 --> 00:16:55.950
door, for instance.

00:16:56.669 --> 00:16:58.850
You know,

00:16:58.890 --> 00:17:00.650
make sure to document everything and

00:17:01.191 --> 00:17:02.932
involve management if it becomes

00:17:02.991 --> 00:17:03.552
difficult.

00:17:04.910 --> 00:17:06.291
the worst, you know, if it goes,

00:17:06.511 --> 00:17:08.273
if it goes badly involve management.

00:17:09.154 --> 00:17:10.056
But I guess I'll throw it back to

00:17:10.096 --> 00:17:10.436
you, Nate.

00:17:10.457 --> 00:17:10.696
Like,

00:17:11.157 --> 00:17:12.318
is this something you've ever dealt with?

00:17:12.398 --> 00:17:12.920
Is this like,

00:17:12.940 --> 00:17:14.582
do you have any suggestions on like how

00:17:14.602 --> 00:17:15.442
to deal with this sort of thing?

00:17:17.189 --> 00:17:18.089
Um, no,

00:17:18.309 --> 00:17:20.671
we did have at my last apartment, um,

00:17:20.691 --> 00:17:23.291
we did have the downstairs neighbor had a

00:17:23.372 --> 00:17:26.653
ring doorbell that was kind of facing, um,

00:17:26.753 --> 00:17:27.615
actually I think it was nest,

00:17:27.835 --> 00:17:28.694
but they had one of those,

00:17:28.855 --> 00:17:29.796
those cameras that was like,

00:17:29.875 --> 00:17:31.175
it was mounted up in the ceiling,

00:17:31.537 --> 00:17:32.616
but because of the layout of the

00:17:32.636 --> 00:17:32.957
apartment,

00:17:33.017 --> 00:17:34.377
I had to walk past it to get

00:17:34.417 --> 00:17:34.758
anywhere.

00:17:35.538 --> 00:17:35.739
Um,

00:17:36.259 --> 00:17:38.119
and unfortunately I did ask management and

00:17:38.140 --> 00:17:39.441
they said that there's no rules against,

00:17:39.500 --> 00:17:40.580
cause I've lived in some apartments where

00:17:40.601 --> 00:17:42.021
you're actually not allowed to have, um,

00:17:42.201 --> 00:17:43.583
video doorbells, which is awesome.

00:17:43.702 --> 00:17:44.884
But yeah,

00:17:44.903 --> 00:17:45.924
they said there's nothing they can really

00:17:45.964 --> 00:17:46.144
do.

00:17:46.346 --> 00:17:49.248
And my solution was just because I would

00:17:49.268 --> 00:17:50.429
leave early in the morning anyways.

00:17:50.548 --> 00:17:52.530
And usually I would I would bring my

00:17:52.550 --> 00:17:54.053
thing is one of my little pet peeves

00:17:54.093 --> 00:17:55.193
is when it rains and the rain gets

00:17:55.213 --> 00:17:55.894
on my glasses.

00:17:56.555 --> 00:17:57.115
And, you know,

00:17:57.135 --> 00:17:58.056
then it's like I can't see.

00:17:58.115 --> 00:17:59.156
So a lot of the time I'll bring

00:17:59.176 --> 00:18:00.479
a hat instead of an umbrella because I

00:18:00.499 --> 00:18:00.598
don't.

00:18:00.999 --> 00:18:02.259
really care as long as it's not like

00:18:02.319 --> 00:18:03.619
pouring obviously i don't really care if

00:18:03.640 --> 00:18:04.740
like my shirt gets a little wet just

00:18:04.759 --> 00:18:06.520
keep it off my glasses so anyways what

00:18:06.560 --> 00:18:08.182
i was gonna say is i would just

00:18:08.221 --> 00:18:09.701
put my hat on um when i would

00:18:09.721 --> 00:18:10.622
go to work in the morning and i

00:18:10.643 --> 00:18:11.982
would just like look straight down at the

00:18:12.022 --> 00:18:13.983
floor so that it wouldn't really catch my

00:18:14.023 --> 00:18:17.244
face um but yeah it's uh

00:18:17.744 --> 00:18:18.205
It's tricky.

00:18:18.226 --> 00:18:18.365
I mean,

00:18:18.385 --> 00:18:19.987
it's definitely it's a soft skills thing.

00:18:20.186 --> 00:18:21.627
And, you know, again,

00:18:21.647 --> 00:18:22.568
I've also said on the podcast,

00:18:22.628 --> 00:18:24.550
one of my personal passing interests,

00:18:24.590 --> 00:18:25.191
I guess you could say,

00:18:25.270 --> 00:18:26.271
is like disaster prep.

00:18:26.412 --> 00:18:26.853
So, you know,

00:18:26.893 --> 00:18:29.535
we have a couple cases of bottled water

00:18:29.575 --> 00:18:31.457
just in case the water needs to get

00:18:31.477 --> 00:18:32.317
shut off or something.

00:18:33.178 --> 00:18:34.479
We have some canned food.

00:18:34.519 --> 00:18:35.380
We have a big thing of rice,

00:18:35.400 --> 00:18:36.339
which I'm super happy about.

00:18:36.359 --> 00:18:36.420
And,

00:18:36.881 --> 00:18:39.442
and that is one thing that I personally

00:18:39.482 --> 00:18:40.784
want to get better at is like meeting

00:18:40.824 --> 00:18:42.384
my neighbors and being on good terms with

00:18:42.424 --> 00:18:42.825
my neighbors.

00:18:42.865 --> 00:18:43.746
Cause that can help out, you know,

00:18:43.766 --> 00:18:44.926
if somebody is like, Hey,

00:18:45.446 --> 00:18:46.768
like this delivery guy came up earlier

00:18:46.788 --> 00:18:47.848
today and he's kind of sniffing around

00:18:47.868 --> 00:18:48.469
your place.

00:18:48.509 --> 00:18:50.190
And I asked him what he needed and

00:18:50.230 --> 00:18:51.151
he just like left, you know,

00:18:51.191 --> 00:18:52.451
like somebody who can kind of look out

00:18:52.471 --> 00:18:52.811
for you.

00:18:54.032 --> 00:18:54.413
But yeah,

00:18:54.432 --> 00:18:55.334
I don't know how to do it.

00:18:55.354 --> 00:18:56.815
I need to ask my wife cause she's

00:18:56.835 --> 00:18:58.296
a wizard at just making friends with

00:18:58.455 --> 00:18:59.517
everybody all the time.

00:19:00.096 --> 00:19:00.837
But yeah,

00:19:01.297 --> 00:19:02.520
Yeah, again,

00:19:02.560 --> 00:19:03.964
it's definitely a soft skills thing,

00:19:04.144 --> 00:19:04.266
and...

00:19:06.210 --> 00:19:08.430
I think most people are generally pretty

00:19:08.470 --> 00:19:08.750
nice.

00:19:08.851 --> 00:19:08.971
Like,

00:19:08.990 --> 00:19:10.090
that's something I've also heard that a

00:19:10.111 --> 00:19:11.330
lot of international people say is that

00:19:11.371 --> 00:19:12.891
Americans are generally really nice

00:19:12.931 --> 00:19:13.230
people.

00:19:13.770 --> 00:19:14.031
And, yeah,

00:19:14.092 --> 00:19:15.172
trying to meet them in this case of,

00:19:15.192 --> 00:19:15.571
like, look,

00:19:15.872 --> 00:19:16.912
I know you're worried about your safety.

00:19:17.511 --> 00:19:18.592
Don't come at them with, like, the whole,

00:19:18.632 --> 00:19:18.791
like,

00:19:18.872 --> 00:19:20.032
I've lived here for years and nothing as

00:19:20.133 --> 00:19:20.873
bad has ever happened.

00:19:20.893 --> 00:19:21.833
But just, like, hey,

00:19:21.952 --> 00:19:24.733
I respect that you care about your safety

00:19:24.753 --> 00:19:25.693
and you're worried about that stuff.

00:19:25.713 --> 00:19:26.894
But, like, I don't know.

00:19:26.973 --> 00:19:28.013
I just feel weird that this thing is

00:19:28.054 --> 00:19:28.894
pointed right at me.

00:19:29.413 --> 00:19:31.394
Can we find some kind of compromise?

00:19:31.454 --> 00:19:31.615
So...

00:19:32.434 --> 00:19:34.297
It's tough, for sure.

00:19:34.517 --> 00:19:38.220
But yeah, that's kind of all I got.

00:19:38.279 --> 00:19:40.121
I don't know if anybody in the chat

00:19:40.141 --> 00:19:42.844
has any better ideas about that one.

00:19:45.422 --> 00:19:45.741
Yeah,

00:19:45.922 --> 00:19:48.403
it's definitely worth looking at your

00:19:48.843 --> 00:19:52.624
specific laws in the area that you live

00:19:52.663 --> 00:19:54.305
because something like this might be

00:19:54.345 --> 00:19:55.746
illegal depending on where you live.

00:19:56.465 --> 00:19:57.746
I'm not sure if that's the case.

00:19:58.066 --> 00:19:59.326
I'm assuming that's probably not the case

00:19:59.406 --> 00:20:01.186
where this person lives because they're

00:20:01.247 --> 00:20:02.288
asking the question anyway.

00:20:03.587 --> 00:20:04.627
I think they did say they were in

00:20:04.647 --> 00:20:05.848
the US, so...

00:20:07.210 --> 00:20:08.411
I don't know if you can confirm or

00:20:08.431 --> 00:20:10.090
deny whether that's actually allowed or

00:20:10.131 --> 00:20:10.330
not.

00:20:11.352 --> 00:20:12.592
Well, in the U.S., yes.

00:20:12.692 --> 00:20:13.272
But again,

00:20:13.313 --> 00:20:14.972
it could depend on the apartment complex.

00:20:15.413 --> 00:20:17.013
Some may have a policy against that.

00:20:17.094 --> 00:20:20.855
And also, their particular state could...

00:20:20.875 --> 00:20:22.277
I don't know.

00:20:22.297 --> 00:20:24.097
The fact that it is facing right into

00:20:24.117 --> 00:20:25.938
their unit could definitely be a thing.

00:20:26.137 --> 00:20:26.679
I'm not sure.

00:20:27.378 --> 00:20:27.959
I'm not a lawyer,

00:20:28.500 --> 00:20:29.440
especially for that state.

00:20:30.440 --> 00:20:30.941
But yeah,

00:20:31.040 --> 00:20:31.901
that is definitely something worth

00:20:31.921 --> 00:20:34.041
checking out.

00:20:34.061 --> 00:20:35.442
Somebody said in the patron chat that...

00:20:36.521 --> 00:20:36.781
My,

00:20:36.821 --> 00:20:38.182
my wife's secret to meeting people is

00:20:38.262 --> 00:20:40.502
ADHD.

00:20:41.064 --> 00:20:42.644
So apparently I just need to have more

00:20:42.703 --> 00:20:46.724
ADHD and then I can, yeah,

00:20:46.765 --> 00:20:47.266
I don't know if that,

00:20:47.286 --> 00:20:48.286
I don't know if that's, yeah,

00:20:48.445 --> 00:20:49.006
I guess so.

00:20:49.026 --> 00:20:49.486
Uh,

00:20:53.285 --> 00:20:54.125
I mean, she definitely does.

00:20:54.664 --> 00:20:55.405
She has ADHD.

00:20:55.445 --> 00:20:57.685
But anyways, yeah,

00:20:57.705 --> 00:20:58.866
we did actually have a question from

00:20:58.906 --> 00:20:59.527
somebody saying,

00:20:59.727 --> 00:21:00.826
do we have any thoughts about the Graphene

00:21:00.846 --> 00:21:02.827
OS tweet saying Pixel XI support is

00:21:03.067 --> 00:21:03.867
delayed?

00:21:05.307 --> 00:21:05.887
Ironically enough,

00:21:05.928 --> 00:21:07.588
that is actually our very next story.

00:21:07.788 --> 00:21:09.648
We're going to talk about the Pixel XI

00:21:09.690 --> 00:21:11.470
and the Graphene situation.

00:21:12.236 --> 00:21:12.516
I mean,

00:21:12.796 --> 00:21:14.136
I guess we can dive into it right

00:21:14.157 --> 00:21:14.397
now.

00:21:14.778 --> 00:21:17.000
So Graphene OS announces Pixel-Eleven

00:21:17.039 --> 00:21:19.040
support can be completed now.

00:21:19.442 --> 00:21:21.303
Graphene OS announced on their Blue Sky

00:21:21.323 --> 00:21:23.284
that Android-seventeen QPR-Two is

00:21:23.324 --> 00:21:25.125
releasing with MTE support for

00:21:25.226 --> 00:21:26.487
Pixel-Eleven phones,

00:21:26.846 --> 00:21:28.248
and they've confirmed it works with

00:21:28.307 --> 00:21:28.969
Graphene OS.

00:21:29.528 --> 00:21:31.310
Despite the security improvements the

00:21:31.431 --> 00:21:32.692
Pixel XI phones bring,

00:21:32.811 --> 00:21:35.294
like QuantumSafe Secure Boot and improved

00:21:35.314 --> 00:21:36.954
Titan III security chip,

00:21:37.075 --> 00:21:39.076
they shipped without MTE support,

00:21:39.416 --> 00:21:41.699
so Graphene OS couldn't be ported to the

00:21:41.739 --> 00:21:42.440
new phones.

00:21:42.880 --> 00:21:44.540
Now the final piece from Google looks to

00:21:44.560 --> 00:21:45.781
be in place for them to be able

00:21:45.801 --> 00:21:48.545
to properly support Pixel XI devices once

00:21:48.684 --> 00:21:51.366
Android-XVII QPR-II releases.

00:21:51.940 --> 00:21:53.641
However, like this person said,

00:21:53.701 --> 00:21:54.521
there's been an update,

00:21:54.902 --> 00:21:57.383
it's been indefinitely delayed due to

00:21:57.423 --> 00:22:00.705
Google not pushing sources for Android,

00:22:00.846 --> 00:22:01.605
as promised.

00:22:02.026 --> 00:22:05.568
Not pushing QPR one and QPR three and

00:22:05.628 --> 00:22:07.089
monthly releases is awful,

00:22:07.369 --> 00:22:08.830
but now it appears they're going to be

00:22:08.871 --> 00:22:11.511
delaying yearly and QPR two releases.

00:22:12.192 --> 00:22:13.933
We'll have to consider that before

00:22:13.973 --> 00:22:14.875
supporting those.

00:22:15.575 --> 00:22:16.914
So that's what they said.

00:22:17.375 --> 00:22:19.016
We can easily work around the monthly

00:22:19.076 --> 00:22:20.435
releases not being pushed,

00:22:20.655 --> 00:22:23.777
but QPR when and QPR three are major

00:22:23.817 --> 00:22:24.257
hassle.

00:22:24.396 --> 00:22:25.837
It ends up causing regressions,

00:22:25.897 --> 00:22:27.617
which are hard to resolve since we still

00:22:27.657 --> 00:22:29.397
have to ship the new firmware,

00:22:29.838 --> 00:22:31.919
drivers and HALS.

00:22:32.778 --> 00:22:34.759
But those aren't designed to work with an

00:22:34.859 --> 00:22:35.420
older release.

00:22:35.779 --> 00:22:36.019
Okay.

00:22:54.409 --> 00:22:58.695
So, I guess, throwing this to you, Nate,

00:22:59.155 --> 00:23:01.098
what are we thinking and does this really

00:23:03.982 --> 00:23:06.586
affect the attractiveness of the new

00:23:06.626 --> 00:23:08.230
Motorola device that's coming out soon?

00:23:10.483 --> 00:23:11.184
Yeah, I mean,

00:23:11.224 --> 00:23:14.146
that's kind of something I've really been

00:23:14.186 --> 00:23:15.969
struggling with is, you know,

00:23:16.910 --> 00:23:19.231
like Golden PJ said here,

00:23:19.291 --> 00:23:20.893
and I'm sure you guys covered this last

00:23:20.913 --> 00:23:22.114
week, is like, man,

00:23:22.555 --> 00:23:25.457
that's sixteen hundred dollars is quite a

00:23:25.497 --> 00:23:26.597
lot in this economy.

00:23:26.679 --> 00:23:27.839
And the thing about it is like for

00:23:27.880 --> 00:23:28.779
graphene users,

00:23:29.401 --> 00:23:31.343
typically graphene users don't want all

00:23:31.383 --> 00:23:32.022
the, you know,

00:23:32.042 --> 00:23:34.625
the AI features and all the fancy stuff.

00:23:36.748 --> 00:23:42.933
that a phone of that hardware would, yeah,

00:23:42.953 --> 00:23:44.955
that that kind of hardware would support.

00:23:45.376 --> 00:23:46.397
So it's really,

00:23:47.278 --> 00:23:48.440
it's almost like paying sixteen hundred

00:23:48.460 --> 00:23:49.480
dollars to get an eight hundred dollar

00:23:49.520 --> 00:23:51.202
phone or maybe even less.

00:23:51.222 --> 00:23:51.462
I don't know.

00:23:51.522 --> 00:23:52.463
I'm not good with hardware,

00:23:52.483 --> 00:23:53.325
but I'm a software guy.

00:23:54.326 --> 00:23:56.248
But yeah, so it's kind of frustrating.

00:23:56.268 --> 00:23:56.768
But on the one hand,

00:23:56.788 --> 00:23:57.910
there's that side of me that's like,

00:23:58.913 --> 00:24:00.974
It shows that there's a demand for a

00:24:01.055 --> 00:24:02.855
non-Google graphene alternative,

00:24:03.336 --> 00:24:04.176
like if you were to buy it.

00:24:04.196 --> 00:24:07.538
And I mean I keep seeing people say

00:24:07.577 --> 00:24:16.725
that Motorola has a habit of these –

00:24:13.981 --> 00:24:15.382
these Motorola phones have a habit of like

00:24:15.402 --> 00:24:17.323
going on serious discount shortly after.

00:24:17.644 --> 00:24:18.544
So I mean maybe in a couple of

00:24:18.564 --> 00:24:20.644
months, it may be eight hundred dollars,

00:24:20.845 --> 00:24:23.625
and that might be a little bit –

00:24:22.768 --> 00:24:23.528
Easier to stomach.

00:24:23.627 --> 00:24:24.388
I don't know, because, yeah,

00:24:24.409 --> 00:24:26.049
it seems like Google,

00:24:26.730 --> 00:24:28.010
intentionally or otherwise,

00:24:29.230 --> 00:24:30.451
I hesitate to attribute everything to

00:24:30.491 --> 00:24:31.352
Malice right off the bat,

00:24:31.372 --> 00:24:32.292
but it's certainly possible.

00:24:32.653 --> 00:24:34.134
It seems like Google is just constantly

00:24:34.153 --> 00:24:35.614
putting up more and more obstacles for

00:24:35.634 --> 00:24:36.934
these custom OSs,

00:24:37.394 --> 00:24:38.556
and it's almost like they don't want to

00:24:38.576 --> 00:24:39.757
come out and admit that they don't want

00:24:39.777 --> 00:24:40.557
to be open anymore,

00:24:40.616 --> 00:24:41.817
but they just don't want to be open

00:24:41.857 --> 00:24:42.238
anymore.

00:24:42.778 --> 00:24:43.198
And, yeah,

00:24:43.278 --> 00:24:44.298
it does kind of make you wonder, like,

00:24:44.338 --> 00:24:46.160
how much longer, even if they want to,

00:24:46.220 --> 00:24:47.579
how much longer can Graphene keep

00:24:47.720 --> 00:24:48.520
supporting these?

00:24:48.641 --> 00:24:49.721
But it's...

00:24:51.067 --> 00:24:52.307
I also have concerns about the hardware.

00:24:52.788 --> 00:24:54.150
The Titan M series is a really,

00:24:54.210 --> 00:24:55.151
really solid chip.

00:24:55.431 --> 00:24:56.791
It's been time-tested and proven,

00:24:57.353 --> 00:24:59.634
and I don't necessarily know that the

00:25:00.095 --> 00:25:01.636
Signature XXVII is going to have the same

00:25:01.676 --> 00:25:03.478
level of hardware protection.

00:25:03.597 --> 00:25:05.859
So I don't know, man.

00:25:06.921 --> 00:25:07.902
It feels like we're in between a rock

00:25:07.922 --> 00:25:09.262
and a hard place right now,

00:25:09.282 --> 00:25:13.406
to be honest.

00:25:13.467 --> 00:25:13.666
Yeah,

00:25:13.707 --> 00:25:15.409
it's definitely – Google is definitely

00:25:15.449 --> 00:25:16.859
putting a –

00:25:17.355 --> 00:25:19.877
putting a dent in, in Graphene OS's plans.

00:25:20.179 --> 00:25:20.318
Uh,

00:25:20.439 --> 00:25:22.961
and it does seem like either they've laid

00:25:23.021 --> 00:25:24.683
off people that usually do the work to

00:25:24.703 --> 00:25:26.205
get these releases out, or, you know,

00:25:26.246 --> 00:25:26.807
like you said,

00:25:26.926 --> 00:25:29.509
there's possibly some sort of malice in,

00:25:29.691 --> 00:25:31.212
and, and, you know, uh,

00:25:32.421 --> 00:25:34.442
you know, negative intent, right?

00:25:34.821 --> 00:25:36.343
But we don't really know exactly what's

00:25:36.363 --> 00:25:38.023
happening because we don't, you know,

00:25:38.044 --> 00:25:39.144
we're not inside Google.

00:25:39.223 --> 00:25:39.904
We don't really know,

00:25:40.285 --> 00:25:41.565
like they're thinking, oh,

00:25:42.006 --> 00:25:43.445
we can destroy Graphene OS.

00:25:43.486 --> 00:25:44.767
Like they're probably not thinking that.

00:25:44.787 --> 00:25:46.867
They're probably just having issues

00:25:46.887 --> 00:25:49.449
getting those releases out because of the

00:25:49.469 --> 00:25:51.009
amount of stuff that they've laid off or

00:25:51.289 --> 00:25:51.931
some other reason.

00:25:52.631 --> 00:25:53.810
And it unfortunately- I was going to say

00:25:53.830 --> 00:25:54.192
too much AI.

00:25:54.231 --> 00:25:54.511
Yeah.

00:25:56.067 --> 00:25:56.767
Too much AI.

00:25:57.028 --> 00:25:57.228
I mean,

00:25:57.268 --> 00:25:58.307
you would think that they would probably

00:25:58.327 --> 00:25:59.929
get it out quicker if they had the

00:25:59.949 --> 00:26:02.211
AI, but I mean, maybe not.

00:26:02.290 --> 00:26:03.551
Maybe that's not helping them.

00:26:03.711 --> 00:26:04.152
I don't know.

00:26:04.172 --> 00:26:05.353
I was going to say,

00:26:05.393 --> 00:26:06.814
unless it's breaking everything like it is

00:26:06.834 --> 00:26:10.076
for Microsoft, who knows?

00:26:10.115 --> 00:26:11.497
So far, it hasn't.

00:26:11.656 --> 00:26:14.518
But I do get concerned with Google because

00:26:14.858 --> 00:26:17.619
they do seem very, very into Google.

00:26:18.221 --> 00:26:20.041
We did get a comment here from...

00:26:23.163 --> 00:26:26.384
hello six four four six um how do

00:26:26.403 --> 00:26:28.045
you browse the internet with disabled

00:26:28.085 --> 00:26:30.066
javascript almost every website a visit

00:26:30.105 --> 00:26:32.266
needs it to work enabling javascript on

00:26:32.326 --> 00:26:33.767
every website after disabling it by

00:26:33.807 --> 00:26:35.867
default leaves a bait a bad taste in

00:26:35.887 --> 00:26:38.588
my mouth and is practically a waste of

00:26:38.628 --> 00:26:41.410
time i feel like you have some thoughts

00:26:41.450 --> 00:26:43.049
on this nate so i'm gonna i'm gonna

00:26:43.069 --> 00:26:44.111
let you answer this one

00:26:45.592 --> 00:26:46.653
What is that supposed to mean?

00:26:47.394 --> 00:26:48.175
I do though, actually.

00:26:48.236 --> 00:26:48.517
Yes.

00:26:48.576 --> 00:26:48.757
No.

00:26:48.797 --> 00:26:49.679
So I,

00:26:49.778 --> 00:26:51.701
in the past I've experimented with a lot

00:26:51.741 --> 00:26:53.525
of different configurations of things

00:26:53.565 --> 00:26:55.847
like, like you block origin in, in,

00:26:57.259 --> 00:26:58.160
I think they call it.

00:26:58.640 --> 00:27:00.101
It's either hard mode or nightmare mode.

00:27:00.461 --> 00:27:01.903
Um, cause if you guys didn't know,

00:27:01.942 --> 00:27:02.083
they're,

00:27:02.403 --> 00:27:04.284
they're not built into you block origin,

00:27:04.365 --> 00:27:05.605
but if you check their official

00:27:05.644 --> 00:27:06.685
documentation on GitHub,

00:27:06.705 --> 00:27:08.207
they have a very great wiki by the

00:27:08.227 --> 00:27:10.169
way on GitHub that I totally recommend

00:27:10.588 --> 00:27:12.451
that explains everything about how it

00:27:12.471 --> 00:27:12.730
works.

00:27:12.750 --> 00:27:13.490
It's super enlightening.

00:27:13.811 --> 00:27:14.311
Um,

00:27:14.332 --> 00:27:15.272
but they explained that they have

00:27:15.313 --> 00:27:15.932
different modes.

00:27:15.952 --> 00:27:18.474
Uh, and, uh, like, I think it's, again,

00:27:18.494 --> 00:27:19.655
it's like one of the hardest modes is

00:27:19.695 --> 00:27:21.438
basically like all JavaScript script

00:27:21.458 --> 00:27:21.877
disabled.

00:27:22.417 --> 00:27:22.557
Um,

00:27:23.479 --> 00:27:25.200
I would say depending on how you're

00:27:25.299 --> 00:27:26.741
browsing the internet with JavaScript

00:27:26.761 --> 00:27:28.982
disabled, yeah, I agree with you.

00:27:29.182 --> 00:27:30.765
I found it to be much more trouble

00:27:30.785 --> 00:27:31.444
than it was worth,

00:27:31.724 --> 00:27:33.346
and I kind of don't think it is

00:27:33.386 --> 00:27:35.407
worth it anymore just because, yeah,

00:27:35.448 --> 00:27:37.189
you end up going in and enabling stuff

00:27:37.490 --> 00:27:37.890
anyways.

00:27:40.050 --> 00:27:41.952
I think from a security perspective,

00:27:42.492 --> 00:27:45.394
I know you usually have to go into

00:27:45.536 --> 00:27:47.416
either like the about config on Firefox or

00:27:47.436 --> 00:27:48.218
the Brave flags,

00:27:48.678 --> 00:27:49.898
or you can just use Movad browser,

00:27:50.679 --> 00:27:52.280
but you can disable like...

00:27:54.498 --> 00:27:55.718
like just-in-time JavaScript,

00:27:55.897 --> 00:27:57.338
which I know that goes a long way

00:27:57.358 --> 00:27:58.798
towards reducing attack surface.

00:28:00.319 --> 00:28:01.681
If anybody's willing to go tinker with

00:28:01.701 --> 00:28:02.240
that kind of stuff,

00:28:02.280 --> 00:28:04.001
that's probably the easiest compromise.

00:28:04.642 --> 00:28:06.083
If you're using something where you can

00:28:06.103 --> 00:28:07.442
block specific scripts, again,

00:28:07.482 --> 00:28:08.344
like you block origin,

00:28:09.023 --> 00:28:10.404
I would say just focus on blocking

00:28:10.444 --> 00:28:11.305
third-party stuff.

00:28:11.845 --> 00:28:12.404
In my experience,

00:28:12.424 --> 00:28:13.645
there's a lot less breakage there.

00:28:14.346 --> 00:28:16.086
Although I do want to point out that

00:28:16.426 --> 00:28:17.448
there have been a lot of,

00:28:18.367 --> 00:28:19.288
I would say, speculation.

00:28:19.347 --> 00:28:20.288
I don't know how proven it is,

00:28:20.608 --> 00:28:21.970
but there is this idea that...

00:28:23.222 --> 00:28:24.363
depending on what you block,

00:28:24.403 --> 00:28:25.903
that could turn into a way to fingerprint

00:28:25.923 --> 00:28:26.064
you.

00:28:26.104 --> 00:28:29.965
Because if you're the only person who's

00:28:30.566 --> 00:28:32.266
blocking third-party JavaScript,

00:28:32.346 --> 00:28:34.106
which I mean, you're not, but just,

00:28:34.267 --> 00:28:34.727
I mean,

00:28:34.767 --> 00:28:36.907
that's why they changed Privacy Badger,

00:28:36.948 --> 00:28:37.107
right?

00:28:37.147 --> 00:28:39.788
Like Privacy Badger used to learn as you

00:28:39.868 --> 00:28:40.529
browse the web,

00:28:40.609 --> 00:28:41.970
it would notice if certain things were

00:28:41.990 --> 00:28:43.030
tracking you and it would block them.

00:28:43.431 --> 00:28:45.070
But then somebody alerted EFF, it's like,

00:28:45.111 --> 00:28:45.451
hey, you know,

00:28:45.471 --> 00:28:46.991
this is creating a unique fingerprint for

00:28:47.031 --> 00:28:47.672
everybody, right?

00:28:48.011 --> 00:28:49.472
So it doesn't do that anymore by default.

00:28:49.492 --> 00:28:50.693
You can enable it, but by default,

00:28:50.733 --> 00:28:51.493
it's just a block list.

00:28:52.215 --> 00:28:53.297
Apparently some people didn't hear that

00:28:53.317 --> 00:28:53.457
news.

00:28:53.477 --> 00:28:54.117
So in case you didn't know,

00:28:54.137 --> 00:28:55.078
I think that happened in like twenty

00:28:55.098 --> 00:28:55.398
eighteen.

00:28:55.839 --> 00:28:58.061
So, yeah, I don't know.

00:28:58.162 --> 00:29:00.203
I would say just focus on like using

00:29:00.424 --> 00:29:01.726
again something like you block origin,

00:29:01.786 --> 00:29:04.209
just block like the major trackers like,

00:29:04.608 --> 00:29:04.828
you know,

00:29:04.888 --> 00:29:06.310
Google Analytics and stuff like that.

00:29:07.571 --> 00:29:08.712
But yeah, in my experience,

00:29:08.732 --> 00:29:11.576
blocking all JavaScript is really a lot

00:29:11.615 --> 00:29:12.537
more hassle than it's worth,

00:29:12.557 --> 00:29:13.778
in my personal opinion.

00:29:13.838 --> 00:29:13.939
So.

00:29:15.535 --> 00:29:16.875
Yeah, just to be clear,

00:29:17.214 --> 00:29:19.836
the reason I said that was because you

00:29:19.895 --> 00:29:21.396
have mentioned that you did really like

00:29:21.596 --> 00:29:22.977
UMatrix in the past,

00:29:23.017 --> 00:29:25.217
which I know definitely has some level of

00:29:26.077 --> 00:29:28.018
JavaScript blocking built in or something.

00:29:28.038 --> 00:29:32.179
That was a good plug-in.

00:29:32.278 --> 00:29:33.038
I missed that one.

00:29:33.058 --> 00:29:33.900
Yeah, I do too.

00:29:33.940 --> 00:29:34.519
I did like it.

00:29:34.759 --> 00:29:38.760
But I think that there is definitely...

00:29:40.663 --> 00:29:40.903
you know,

00:29:40.942 --> 00:29:42.124
things that you can think about about

00:29:42.223 --> 00:29:42.924
risks, right?

00:29:42.944 --> 00:29:43.184
Like,

00:29:43.384 --> 00:29:44.566
every time you're browsing the internet,

00:29:44.586 --> 00:29:44.967
like,

00:29:45.907 --> 00:29:49.089
is this worth the actual trade-off of

00:29:49.170 --> 00:29:50.932
having to basically, you know,

00:29:50.991 --> 00:29:53.534
go through every website and make sure

00:29:53.554 --> 00:29:56.236
that the JavaScript is enabled anyway?

00:29:57.738 --> 00:30:00.140
It kind of breaks accessing the majority

00:30:00.160 --> 00:30:00.779
of the internet.

00:30:00.881 --> 00:30:03.782
And I think for basically the majority of

00:30:03.843 --> 00:30:04.182
people,

00:30:04.242 --> 00:30:06.545
that's a bit too much of a hassle

00:30:06.585 --> 00:30:07.125
to deal with.

00:30:07.405 --> 00:30:07.566
So...

00:30:08.507 --> 00:30:09.448
But like, like Nate said,

00:30:09.468 --> 00:30:10.708
like there's just in time.

00:30:10.788 --> 00:30:12.489
There's also the other one that I don't

00:30:12.509 --> 00:30:14.029
think you mentioned was the V eight

00:30:14.150 --> 00:30:14.750
optimizer.

00:30:14.810 --> 00:30:15.790
You can disable that.

00:30:15.830 --> 00:30:19.353
And that also apparently reduces, um,

00:30:19.393 --> 00:30:22.474
reduces the level of, uh,

00:30:22.494 --> 00:30:23.855
access that JavaScript has.

00:30:23.895 --> 00:30:23.976
Um,

00:30:23.996 --> 00:30:25.517
I wasn't sure if that was the same

00:30:25.557 --> 00:30:26.096
thing or not.

00:30:26.196 --> 00:30:27.077
So, okay.

00:30:27.157 --> 00:30:27.597
Good to know.

00:30:27.657 --> 00:30:28.538
It could be, it could be,

00:30:28.578 --> 00:30:29.179
it could be.

00:30:29.398 --> 00:30:30.200
Um, yeah.

00:30:30.220 --> 00:30:31.800
So V eight optimizer is another thing.

00:30:32.340 --> 00:30:34.001
Um, and yeah,

00:30:34.061 --> 00:30:35.343
I think there's not really much you can

00:30:35.403 --> 00:30:37.144
do in terms of JavaScript these days.

00:30:37.807 --> 00:30:39.970
I personally just leave it on and,

00:30:40.349 --> 00:30:41.471
you know, make sure that I'm,

00:30:41.530 --> 00:30:43.073
I think layering as well is also

00:30:43.113 --> 00:30:43.452
important.

00:30:43.472 --> 00:30:44.913
Like, you know, use ublock origin,

00:30:45.595 --> 00:30:47.036
use DNS blocking,

00:30:48.436 --> 00:30:50.538
have multiple layers of security in that

00:30:50.638 --> 00:30:51.038
aspect.

00:30:51.118 --> 00:30:52.661
And hopefully something,

00:30:53.161 --> 00:30:55.163
if there is something malicious in terms

00:30:55.182 --> 00:30:58.345
of JavaScript, it's blocked automatically.

00:30:59.405 --> 00:31:01.087
But again, there's,

00:31:02.509 --> 00:31:03.609
Someone here actually mentioned,

00:31:04.089 --> 00:31:05.810
I stopped using an Adblock plugin out of

00:31:05.851 --> 00:31:08.132
fingerprinting concerns and instead rely

00:31:08.211 --> 00:31:09.811
on network level Adblock.

00:31:10.813 --> 00:31:12.693
I believe that network level Adblock is

00:31:12.834 --> 00:31:17.935
also fingerprintable because, you know,

00:31:17.976 --> 00:31:19.237
your browser is not going to be able

00:31:19.257 --> 00:31:22.057
to make certain connections when you go to

00:31:22.077 --> 00:31:22.637
a website.

00:31:23.519 --> 00:31:26.599
I'm not sure if that's actually the case

00:31:26.660 --> 00:31:27.280
or not, but...

00:31:28.404 --> 00:31:28.644
Yeah,

00:31:28.726 --> 00:31:29.926
we'll definitely have to look into that

00:31:29.946 --> 00:31:31.449
because I'm not a hundred percent sure on

00:31:31.469 --> 00:31:32.289
the facts on that.

00:31:33.771 --> 00:31:35.714
I, I don't know either.

00:31:37.921 --> 00:31:38.661
I'm going to be honest.

00:31:38.800 --> 00:31:41.842
I think for most of us who do

00:31:41.882 --> 00:31:43.521
not have a particularly high threat model,

00:31:44.021 --> 00:31:45.163
I think we're overthinking it a lot of

00:31:45.182 --> 00:31:45.502
the time.

00:31:47.222 --> 00:31:47.603
Like, yeah,

00:31:47.663 --> 00:31:48.942
if you're blocking all JavaScript,

00:31:48.982 --> 00:31:50.604
I think that... Because on the one hand,

00:31:50.683 --> 00:31:52.463
I think a lot of fingerprinting scripts

00:31:52.564 --> 00:31:53.544
require JavaScript.

00:31:53.624 --> 00:31:54.104
Not all of them.

00:31:54.243 --> 00:31:56.265
I have seen proofs of concept using CSS.

00:31:57.365 --> 00:31:58.224
But I think most of them,

00:31:58.265 --> 00:31:59.526
like Google Analytics, for example,

00:32:00.066 --> 00:32:01.066
require JavaScript.

00:32:01.086 --> 00:32:01.165
Yeah.

00:32:02.307 --> 00:32:03.868
So in theory, by blocking JavaScript,

00:32:03.888 --> 00:32:04.890
you couldn't be fingerprinted.

00:32:05.351 --> 00:32:07.432
But at the same time, I don't know.

00:32:07.554 --> 00:32:11.258
I think it's one of those things where...

00:32:11.337 --> 00:32:13.580
We know so little about fingerprinting,

00:32:13.801 --> 00:32:15.943
and we don't know...

00:32:17.261 --> 00:32:18.942
what they put emphasis on.

00:32:19.782 --> 00:32:20.643
Like companies,

00:32:21.403 --> 00:32:22.963
it's funny because companies that talk

00:32:22.983 --> 00:32:24.544
about fingerprinting, first of all,

00:32:24.564 --> 00:32:25.703
if you look up browser fingerprinting,

00:32:25.983 --> 00:32:27.144
you're gonna find nothing but like

00:32:27.244 --> 00:32:28.704
analytics companies trying to score a new

00:32:28.744 --> 00:32:29.105
client.

00:32:29.464 --> 00:32:30.705
And so of course you can't really trust

00:32:30.746 --> 00:32:32.086
them because of course they're gonna claim

00:32:32.105 --> 00:32:33.666
that they have the world's most accurate

00:32:34.067 --> 00:32:35.487
everything and that's why you should pay

00:32:35.527 --> 00:32:38.347
us five billion dollars a month for our

00:32:38.367 --> 00:32:39.567
stupid product that probably doesn't even

00:32:39.587 --> 00:32:40.048
do anything.

00:32:40.488 --> 00:32:42.769
So it's like nobody is talking about it

00:32:42.808 --> 00:32:44.269
from the other side of the perspective

00:32:44.288 --> 00:32:45.809
where they're like a whistleblower,

00:32:45.849 --> 00:32:46.250
like yeah,

00:32:46.609 --> 00:32:47.571
I used to work for this company.

00:32:47.852 --> 00:32:49.315
Here is exactly how it works.

00:32:49.355 --> 00:32:50.616
Here's exactly what we did.

00:32:50.938 --> 00:32:52.160
Here's the differences between the

00:32:52.180 --> 00:32:52.621
different things.

00:32:52.681 --> 00:32:54.163
So it's honestly,

00:32:54.183 --> 00:32:55.204
it's all just kind of guesswork.

00:32:55.224 --> 00:32:56.007
And I think it's one of those,

00:32:56.047 --> 00:32:59.432
like if, if you're doing like a basic,

00:32:59.452 --> 00:33:00.034
um,

00:33:00.365 --> 00:33:01.185
Even an ad blocker,

00:33:01.286 --> 00:33:02.767
like I think a good ad blocker,

00:33:02.807 --> 00:33:02.946
I mean,

00:33:03.086 --> 00:33:04.688
I'm very biased against ads for a lot

00:33:04.708 --> 00:33:05.067
of reasons.

00:33:05.087 --> 00:33:06.528
That's kind of turning into my personal

00:33:06.548 --> 00:33:07.170
crusade lately.

00:33:07.190 --> 00:33:09.371
But I think it's better than just doing

00:33:09.431 --> 00:33:09.810
nothing.

00:33:09.931 --> 00:33:11.653
And I think there's like a balance.

00:33:11.692 --> 00:33:12.752
Again, if you're blocking everything,

00:33:12.772 --> 00:33:13.614
you're going to stand out.

00:33:14.114 --> 00:33:16.395
But I think just adding uBlock Origin,

00:33:16.435 --> 00:33:18.396
like everybody uses that and stuff like

00:33:18.436 --> 00:33:18.537
that.

00:33:18.656 --> 00:33:20.077
AdGuard Home, somebody pointed out.

00:33:20.117 --> 00:33:22.259
Like I think the basic things that a

00:33:22.299 --> 00:33:24.181
lot of people are using is probably not

00:33:24.221 --> 00:33:24.721
that risky.

00:33:25.082 --> 00:33:26.301
And if your threat model is really that

00:33:26.342 --> 00:33:27.063
high where you're like, no,

00:33:27.123 --> 00:33:28.483
I absolutely cannot afford to be

00:33:28.503 --> 00:33:30.164
fingerprinted, you should be using Tor.

00:33:31.266 --> 00:33:32.428
And then you blend in with everybody.

00:33:34.070 --> 00:33:34.651
Like, I don't know.

00:33:34.912 --> 00:33:35.673
I think it's one of those things that

00:33:35.692 --> 00:33:36.894
we just kind of overthink a little bit

00:33:37.075 --> 00:33:38.277
personally.

00:33:38.938 --> 00:33:39.117
Yeah,

00:33:39.278 --> 00:33:40.660
I think that's definitely a fair point.

00:33:40.960 --> 00:33:43.022
I think the thing is with the DNS

00:33:43.263 --> 00:33:45.386
ad blocking is websites can see what DNS

00:33:45.406 --> 00:33:46.188
server you're using.

00:33:47.188 --> 00:33:47.647
But again,

00:33:47.708 --> 00:33:49.309
if you're using something like AdGuard or

00:33:49.369 --> 00:33:51.030
Piehole, it forwards it.

00:33:51.330 --> 00:33:53.032
It blocks it at the local level,

00:33:53.153 --> 00:33:55.734
and then it forwards that to the actual

00:33:55.775 --> 00:33:57.195
service that you want, right?

00:33:57.236 --> 00:33:59.176
So I'm not sure if that would be...

00:33:59.518 --> 00:34:00.637
That would probably be less

00:34:00.657 --> 00:34:01.679
fingerprintable, I guess,

00:34:01.719 --> 00:34:03.701
if you set it to Google or your

00:34:03.721 --> 00:34:05.402
DNS, your ISP's DNS,

00:34:05.422 --> 00:34:06.282
it wouldn't be as obvious.

00:34:10.302 --> 00:34:11.965
Someone said Brave and AdGuard Home.

00:34:12.304 --> 00:34:15.206
You can use all sorts of tools to

00:34:15.748 --> 00:34:16.807
layer that protection.

00:34:21.431 --> 00:34:21.771
I have a

00:34:23.764 --> 00:34:28.027
I have a pie hole that uses AdGuard

00:34:28.407 --> 00:34:29.947
as the DNS resolver.

00:34:29.967 --> 00:34:30.568
So like you were saying,

00:34:30.608 --> 00:34:31.628
like multiple levels of,

00:34:32.108 --> 00:34:33.148
and I have some of the block lists

00:34:33.188 --> 00:34:33.568
enabled,

00:34:33.628 --> 00:34:35.048
some of the basic block lists enabled on

00:34:35.088 --> 00:34:35.550
the pie hole.

00:34:35.590 --> 00:34:36.510
So there's block lists,

00:34:36.929 --> 00:34:38.431
there's individual things that I've gone

00:34:38.451 --> 00:34:39.070
through and blocked.

00:34:39.530 --> 00:34:40.331
And then there's AdGuard.

00:34:40.351 --> 00:34:41.492
There's like three layers of defense

00:34:41.532 --> 00:34:42.012
there.

00:34:42.052 --> 00:34:42.172
So.

00:34:43.902 --> 00:34:44.561
Um,

00:34:44.581 --> 00:34:45.882
somebody said privacy guides forum is

00:34:46.003 --> 00:34:47.684
unusable on the safest security level on

00:34:47.724 --> 00:34:48.003
tour.

00:34:48.083 --> 00:34:48.304
Yeah.

00:34:48.423 --> 00:34:48.724
I mean,

00:34:49.204 --> 00:34:50.744
most of the internet is unusable on the

00:34:50.784 --> 00:34:52.844
safest security level, even, even on, um,

00:34:53.125 --> 00:34:53.766
Moldad browser.

00:34:53.826 --> 00:34:53.925
I've,

00:34:54.085 --> 00:34:55.925
I've switched Moldad browser recently to

00:34:55.965 --> 00:34:58.266
the, uh, the safer security level,

00:34:58.286 --> 00:34:58.947
like the middle one.

00:34:59.086 --> 00:35:00.688
And I was surprised how many things that

00:35:00.708 --> 00:35:01.007
broke.

00:35:01.108 --> 00:35:02.728
So unfortunately that's,

00:35:02.809 --> 00:35:03.449
that's kind of the trade off.

00:35:04.465 --> 00:35:06.148
Just to be clear about the forum though,

00:35:06.228 --> 00:35:07.449
that's not down to us.

00:35:07.509 --> 00:35:08.989
That's actually Discourse,

00:35:09.050 --> 00:35:11.012
the forum software that we use.

00:35:11.371 --> 00:35:14.235
They don't allow for disabling JavaScript

00:35:14.275 --> 00:35:16.657
for it to work correctly.

00:35:18.217 --> 00:35:20.000
I'm sure there's other forum softwares

00:35:20.019 --> 00:35:22.961
that exist, but for our specific use case,

00:35:23.163 --> 00:35:24.643
Discourse makes the most sense.

00:35:25.445 --> 00:35:26.766
It works for our situation,

00:35:26.887 --> 00:35:29.668
so we can't really switch to something

00:35:29.728 --> 00:35:29.989
else.

00:35:30.949 --> 00:35:32.851
But I can assure you there's no tracking

00:35:32.891 --> 00:35:33.210
scripts.

00:35:33.251 --> 00:35:36.172
There's no malicious JavaScript on the

00:35:36.213 --> 00:35:36.552
forum.

00:35:37.213 --> 00:35:40.235
So I don't think it's a huge issue

00:35:40.434 --> 00:35:42.817
if you can't access it without that.

00:35:42.896 --> 00:35:45.778
But again, if that's a concern,

00:35:45.818 --> 00:35:50.862
then maybe I don't really know.

00:35:50.882 --> 00:35:52.041
I don't really know what to say.

00:35:53.682 --> 00:35:54.123
That's unfortunate.

00:35:54.164 --> 00:35:54.623
Yellow discourse.

00:35:56.106 --> 00:36:01.016
Yeah, go bug discourse about it.

00:36:01.518 --> 00:36:04.945
I think we can move into our site

00:36:05.025 --> 00:36:05.586
updates.

00:36:08.333 --> 00:36:09.235
I think this is probably a good time

00:36:09.255 --> 00:36:09.514
for that.

00:36:09.954 --> 00:36:10.956
So yeah, in a little bit,

00:36:10.996 --> 00:36:12.336
we're going to dive into a hot take

00:36:12.476 --> 00:36:13.958
about how much the average person cares

00:36:13.978 --> 00:36:14.617
about privacy.

00:36:14.657 --> 00:36:15.099
But first,

00:36:15.119 --> 00:36:16.500
we're going to give some quick updates on

00:36:16.519 --> 00:36:18.440
what we've been working on at Privacy

00:36:18.460 --> 00:36:19.141
Guides this week.

00:36:19.762 --> 00:36:20.983
And remember to go ahead and leave your

00:36:21.003 --> 00:36:22.204
questions and comments in the chat.

00:36:22.264 --> 00:36:23.684
I see the chat is very active today.

00:36:23.864 --> 00:36:25.985
And we will definitely get to some of

00:36:26.005 --> 00:36:26.766
those in a moment.

00:36:26.827 --> 00:36:27.226
But first,

00:36:27.327 --> 00:36:29.327
I'm going to hand it over to Jordan

00:36:29.568 --> 00:36:31.829
to talk about some of our more recent

00:36:31.849 --> 00:36:36.273
changes.

00:36:36.293 --> 00:36:37.094
You are muted, friend.

00:36:38.427 --> 00:36:38.847
Sorry.

00:36:38.867 --> 00:36:39.027
Yes,

00:36:39.088 --> 00:36:41.929
so this week we've got some site updates

00:36:41.949 --> 00:36:42.650
that we've pushed,

00:36:43.471 --> 00:36:44.972
mostly just administrative stuff,

00:36:44.992 --> 00:36:47.813
which was updating some issues with GitHub

00:36:47.914 --> 00:36:48.574
Actions,

00:36:48.753 --> 00:36:50.856
and it was mainly to fix some of

00:36:50.876 --> 00:36:53.757
the different language versions that we

00:36:53.797 --> 00:36:54.719
have of the site,

00:36:55.378 --> 00:36:57.561
and that was mostly done by Daniel,

00:36:57.760 --> 00:36:58.762
so that was good.

00:36:59.481 --> 00:37:03.324
There was also a change to the Proton

00:37:03.684 --> 00:37:05.387
mobile app audits,

00:37:06.367 --> 00:37:08.867
which basically just updated some of the

00:37:08.907 --> 00:37:09.509
wording.

00:37:10.489 --> 00:37:10.969
Basically,

00:37:11.289 --> 00:37:14.570
we mentioned that the Proton Drive web

00:37:14.630 --> 00:37:17.612
application was independently audited in

00:37:17.632 --> 00:37:18.572
the twenty twenty one.

00:37:18.773 --> 00:37:21.293
And then we also added a section that

00:37:21.333 --> 00:37:23.114
the Android and iOS apps underwent

00:37:23.175 --> 00:37:24.795
independent security audits by the same

00:37:24.835 --> 00:37:26.096
company in twenty twenty two.

00:37:26.775 --> 00:37:29.137
And we linked to the source there as

00:37:29.197 --> 00:37:29.458
well.

00:37:29.538 --> 00:37:31.519
So that was a good update that someone

00:37:31.579 --> 00:37:32.360
added as well.

00:37:33.481 --> 00:37:34.483
That was good to get that added.

00:37:34.583 --> 00:37:35.342
And as usual,

00:37:35.362 --> 00:37:37.644
we do have news briefs every week.

00:37:37.965 --> 00:37:41.447
That's freer and sometimes Nate does as

00:37:41.487 --> 00:37:41.728
well.

00:37:42.228 --> 00:37:44.090
So this week we had Microsoft Paint

00:37:44.130 --> 00:37:45.771
vulnerability could allow attackers to

00:37:45.811 --> 00:37:47.032
take over your computer.

00:37:47.572 --> 00:37:49.974
Chat GPT lockdown mode bypass could leak

00:37:49.994 --> 00:37:51.577
your chat history without your knowledge.

00:37:52.077 --> 00:37:54.297
And Claude Code leaking secrets and

00:37:54.338 --> 00:37:56.900
passwords in public GitHub repositories.

00:37:57.539 --> 00:37:59.621
So all fun stuff there.

00:38:00.242 --> 00:38:01.442
I guess I can throw it back to

00:38:01.481 --> 00:38:01.963
you though, Nate.

00:38:02.023 --> 00:38:03.384
What are we working on in terms of

00:38:03.403 --> 00:38:04.043
video stuff?

00:38:05.534 --> 00:38:08.436
Yeah, so I know you actually,

00:38:08.516 --> 00:38:10.217
just as we jumped on here for the

00:38:10.237 --> 00:38:10.637
live stream,

00:38:10.657 --> 00:38:12.358
you are doing the final render of our

00:38:12.418 --> 00:38:13.460
Graphene OS video,

00:38:13.639 --> 00:38:16.601
which it's really just an overview about

00:38:16.641 --> 00:38:19.884
what Graphene OS is and why we recommend

00:38:19.903 --> 00:38:20.423
it for people,

00:38:20.565 --> 00:38:23.025
even if they're not a state-level

00:38:23.085 --> 00:38:24.967
politician or activist or journalist or

00:38:24.987 --> 00:38:25.387
anything.

00:38:26.307 --> 00:38:27.989
So hopefully there will be a good...

00:38:31.431 --> 00:38:32.532
it'll be a good video that you can

00:38:32.552 --> 00:38:34.014
share with like your friends and family

00:38:34.494 --> 00:38:36.454
who may not be familiar with graphene and

00:38:36.775 --> 00:38:38.135
kind of give them an overview of like,

00:38:38.175 --> 00:38:39.336
here's some of the cool features.

00:38:39.456 --> 00:38:42.059
And then I have mentioned several times

00:38:42.079 --> 00:38:43.940
that we are also doing an Obtanium

00:38:44.079 --> 00:38:46.340
tutorial, which is fully filmed.

00:38:46.521 --> 00:38:47.942
And just last night, actually,

00:38:47.961 --> 00:38:49.543
I went through and did the first cut

00:38:49.702 --> 00:38:51.565
where I cut out all the mistakes and

00:38:51.585 --> 00:38:52.525
dead space and everything.

00:38:53.525 --> 00:38:55.347
So I just have to add some B-roll

00:38:55.367 --> 00:38:57.068
like screenshots and screen grabs on my

00:38:57.148 --> 00:38:57.347
end.

00:38:57.748 --> 00:38:59.108
And then it will be off to Jordan

00:38:59.128 --> 00:38:59.949
to add any, uh,

00:39:00.469 --> 00:39:01.891
Last minute magic.

00:39:02.512 --> 00:39:03.853
That one should be pretty straightforward,

00:39:03.893 --> 00:39:04.134
I hope.

00:39:04.293 --> 00:39:05.876
But it should be fun.

00:39:07.608 --> 00:39:08.248
Yeah,

00:39:08.268 --> 00:39:09.708
all this is made possible by our

00:39:09.748 --> 00:39:10.250
supporters.

00:39:10.690 --> 00:39:11.550
If you'd like to support us,

00:39:11.590 --> 00:39:12.751
you can sign up for a membership or

00:39:12.791 --> 00:39:14.333
donate at privacyguides.org,

00:39:14.452 --> 00:39:15.532
or you can pick up some swag at

00:39:15.592 --> 00:39:17.034
shop.privacyguides.org.

00:39:17.454 --> 00:39:19.175
Privacy Guides is a nonprofit which

00:39:19.235 --> 00:39:20.737
researches and shares privacy-related

00:39:20.757 --> 00:39:22.878
information and facilitates a community on

00:39:22.918 --> 00:39:24.880
our forum and matrix and Fluxer where

00:39:24.940 --> 00:39:26.541
people can ask questions and get advice

00:39:26.561 --> 00:39:28.161
about staying private online and

00:39:28.202 --> 00:39:29.242
preserving their digital rights.

00:39:29.762 --> 00:39:31.744
Now let's talk about how to

00:39:31.764 --> 00:39:33.425
compartmentalize your social media

00:39:33.485 --> 00:39:33.945
accounts.

00:39:34.106 --> 00:39:35.246
And remember to leave your questions in

00:39:35.266 --> 00:39:36.226
the chat and we will get to them

00:39:36.327 --> 00:39:37.327
in between stories.

00:39:37.927 --> 00:39:38.128
Actually,

00:39:38.168 --> 00:39:39.329
real quick before we jump into that one,

00:39:39.369 --> 00:39:39.829
somebody asked,

00:39:40.489 --> 00:39:41.829
talking about the Proton audit,

00:39:41.909 --> 00:39:44.130
isn't a little bit outdated at this point

00:39:44.170 --> 00:39:45.391
because there have been so many changes

00:39:45.431 --> 00:39:45.891
since then?

00:39:46.891 --> 00:39:47.170
I don't know.

00:39:47.190 --> 00:39:49.132
Do you have a thought on that one?

00:39:49.152 --> 00:39:49.751
I think so.

00:39:50.132 --> 00:39:50.552
I agree.

00:39:51.132 --> 00:39:52.432
I think they should be doing more regular

00:39:52.512 --> 00:39:52.932
audits.

00:39:53.293 --> 00:39:55.414
And it is concerning that it's been

00:39:55.713 --> 00:39:58.074
almost, I guess at this point, four years.

00:39:58.114 --> 00:39:59.614
Four years.

00:39:59.635 --> 00:40:01.516
So that is concerning to hear.

00:40:02.896 --> 00:40:03.396
Obviously,

00:40:03.856 --> 00:40:06.557
we do have not many recommendations.

00:40:07.498 --> 00:40:08.739
when it comes to cloud providers.

00:40:09.019 --> 00:40:10.541
So we kind of have to be a

00:40:10.621 --> 00:40:11.322
bit, you know,

00:40:12.043 --> 00:40:13.423
a little bit more lax when it comes

00:40:13.443 --> 00:40:14.065
to that, right?

00:40:14.105 --> 00:40:15.806
Because otherwise literally nothing would

00:40:15.827 --> 00:40:17.347
be even like,

00:40:17.889 --> 00:40:18.989
we would have nothing on there,

00:40:19.389 --> 00:40:20.911
which I guess is,

00:40:21.952 --> 00:40:23.414
we're trying to find the best possible

00:40:23.474 --> 00:40:23.855
options.

00:40:23.914 --> 00:40:25.175
And this Proton Drive,

00:40:25.336 --> 00:40:26.557
even though they had the audit in

00:40:27.878 --> 00:40:29.019
It's still, you know,

00:40:29.579 --> 00:40:30.641
it's still one of these really good

00:40:30.681 --> 00:40:33.021
services that hasn't shown that they can't

00:40:33.041 --> 00:40:33.942
be trusted, at least.

00:40:34.503 --> 00:40:35.402
But again,

00:40:35.943 --> 00:40:37.724
we should be seeing another audit this

00:40:37.764 --> 00:40:39.005
year, next year.

00:40:39.565 --> 00:40:40.945
We need to see something soon because

00:40:41.485 --> 00:40:41.746
again,

00:40:41.786 --> 00:40:42.646
if it becomes

00:40:43.146 --> 00:40:45.547
One of these things where it takes them

00:40:45.788 --> 00:40:48.228
five years in between audits, it's like,

00:40:48.429 --> 00:40:49.590
well, what's really the point?

00:40:49.630 --> 00:40:51.990
Because like this person said, you know,

00:40:52.610 --> 00:40:54.911
there has been so many changes and audits

00:40:54.992 --> 00:40:56.873
are basically just a snapshot of that

00:40:56.932 --> 00:40:58.393
specific time period, right?

00:40:58.434 --> 00:41:00.173
We know in twenty twenty two that the

00:41:00.253 --> 00:41:00.994
apps were secure.

00:41:01.815 --> 00:41:03.434
But do we know in twenty twenty six

00:41:03.474 --> 00:41:04.376
that they're still secure?

00:41:04.755 --> 00:41:05.496
Probably not.

00:41:05.576 --> 00:41:05.856
Right.

00:41:05.936 --> 00:41:08.556
So that's when it becomes more tricky.

00:41:08.777 --> 00:41:11.438
So I think they should be doing it

00:41:11.518 --> 00:41:12.998
every year, ideally.

00:41:13.338 --> 00:41:13.898
But again,

00:41:13.958 --> 00:41:15.219
these sort of things are pretty,

00:41:16.099 --> 00:41:16.878
pretty expensive.

00:41:17.539 --> 00:41:19.059
So again,

00:41:19.380 --> 00:41:21.159
maybe it's too maybe it's too extreme to

00:41:21.199 --> 00:41:22.420
expect that every single year,

00:41:22.820 --> 00:41:24.800
every two years seems reasonable to me.

00:41:25.240 --> 00:41:25.702
But again,

00:41:28.228 --> 00:41:29.289
I think this is one of these things

00:41:29.329 --> 00:41:31.409
where if you want this to be a

00:41:31.449 --> 00:41:34.253
requirement... Oh, what just happened?

00:41:34.492 --> 00:41:35.873
My camera just went black.

00:41:36.653 --> 00:41:37.875
Yeah, I still hear you.

00:41:38.114 --> 00:41:39.856
I don't know where the camera went.

00:41:39.896 --> 00:41:40.456
Interesting.

00:41:40.597 --> 00:41:41.657
I'm not sure what's happening there.

00:41:42.659 --> 00:41:42.898
Anyway,

00:41:42.918 --> 00:41:44.320
what I was trying to say is if

00:41:44.340 --> 00:41:45.820
you want this to be changed and if

00:41:45.840 --> 00:41:46.742
you want this to become...

00:41:47.322 --> 00:41:48.481
like part of a criteria,

00:41:48.561 --> 00:41:50.342
I would really highly recommend you join

00:41:50.643 --> 00:41:51.382
our forum and,

00:41:51.563 --> 00:41:52.784
and open a thread and say like,

00:41:52.824 --> 00:41:54.563
you know, this should be fixed.

00:41:54.623 --> 00:41:55.885
It should be removed because of this.

00:41:56.125 --> 00:41:57.244
Um, because we do,

00:41:57.364 --> 00:41:58.664
that is the main reason why we make

00:41:58.684 --> 00:42:00.646
changes is because of people in our

00:42:00.686 --> 00:42:02.266
community that want things, um,

00:42:02.326 --> 00:42:02.987
to be changed.

00:42:03.367 --> 00:42:05.126
So yeah, that's,

00:42:05.226 --> 00:42:06.347
that's what I would say to that.

00:42:06.547 --> 00:42:07.668
Um, again,

00:42:08.007 --> 00:42:09.889
we're not completely opposed to that

00:42:09.909 --> 00:42:11.528
becoming, um, a thing.

00:42:11.628 --> 00:42:13.389
I will just quickly disappear though.

00:42:13.789 --> 00:42:14.610
Um, while I fix this.

00:42:18.182 --> 00:42:19.342
All right,

00:42:19.362 --> 00:42:20.844
I will go ahead and jump into our

00:42:20.864 --> 00:42:21.664
next story then,

00:42:22.184 --> 00:42:24.545
which is actually yet another forum

00:42:24.625 --> 00:42:24.965
update.

00:42:25.364 --> 00:42:26.105
I'm gonna be honest with you guys,

00:42:26.125 --> 00:42:27.605
it was a little bit of a,

00:42:27.644 --> 00:42:29.365
not so much a slow news week per

00:42:29.385 --> 00:42:29.626
se,

00:42:29.686 --> 00:42:32.326
but we try really hard to find a

00:42:32.365 --> 00:42:35.067
balance between like big stories and

00:42:35.126 --> 00:42:37.547
stories that actually like affect you

00:42:37.568 --> 00:42:37.927
guys.

00:42:37.987 --> 00:42:38.987
And there's something, you know,

00:42:39.007 --> 00:42:40.148
like a takeaway for you guys.

00:42:40.847 --> 00:42:41.768
And there just weren't a lot of those

00:42:41.789 --> 00:42:42.548
stories this week.

00:42:42.628 --> 00:42:44.949
So, well, Jordan's back.

00:42:44.969 --> 00:42:45.250
I don't know,

00:42:45.269 --> 00:42:46.369
did you wanna take this or you want

00:42:46.389 --> 00:42:46.869
me to take this?

00:42:48.369 --> 00:42:49.030
No, I'm good.

00:42:49.130 --> 00:42:50.110
I can hop on it.

00:42:50.451 --> 00:42:51.251
It's quick anyway.

00:42:51.672 --> 00:42:53.612
This one was just like a post here

00:42:53.713 --> 00:42:55.514
from someone saying they wanted to have

00:42:55.773 --> 00:42:56.695
social media accounts,

00:42:56.735 --> 00:42:59.856
but they wanted them to be safe,

00:43:00.036 --> 00:43:00.436
I guess.

00:43:01.257 --> 00:43:01.536
You know,

00:43:02.257 --> 00:43:04.898
I want some to be public and others

00:43:04.958 --> 00:43:05.918
I want to be anonymous.

00:43:06.019 --> 00:43:07.400
Can I use the same email to create

00:43:07.440 --> 00:43:08.780
all of them or is that compromising?

00:43:09.221 --> 00:43:11.121
Do I have two separate emails for public

00:43:11.141 --> 00:43:12.103
and anonymous accounts?

00:43:13.623 --> 00:43:15.204
They're kind of overwhelmed, basically.

00:43:17.081 --> 00:43:18.688
Facebook can be kind of awful when it

00:43:18.730 --> 00:43:19.532
comes to signups,

00:43:19.552 --> 00:43:20.878
like they don't allow proton mail,

00:43:20.898 --> 00:43:21.561
for instance.

00:43:21.923 --> 00:43:22.123
So...

00:43:23.382 --> 00:43:23.641
yeah,

00:43:24.023 --> 00:43:26.324
kind of just how to create things

00:43:26.885 --> 00:43:29.405
anonymously or slash semi-anonymously,

00:43:29.447 --> 00:43:31.628
like what sort of things should someone be

00:43:31.668 --> 00:43:32.289
looking for?

00:43:33.550 --> 00:43:35.110
Someone did in this post,

00:43:35.451 --> 00:43:36.070
they did respond.

00:43:36.090 --> 00:43:36.411
They said,

00:43:36.831 --> 00:43:38.713
don't use the same email account in your

00:43:38.753 --> 00:43:41.014
real name and pseudo anonymous accounts.

00:43:41.835 --> 00:43:44.597
Don't use Instagram or the Facebook app

00:43:44.617 --> 00:43:47.300
because they have significant access to

00:43:47.420 --> 00:43:48.119
your information.

00:43:48.701 --> 00:43:49.081
So yeah,

00:43:50.768 --> 00:43:52.391
I will say that's first.

00:43:52.873 --> 00:43:53.835
I guess I'll throw it to you, Nate.

00:43:53.855 --> 00:43:55.498
There was another comment there as well

00:43:55.518 --> 00:43:56.501
that someone suggested,

00:43:56.561 --> 00:43:57.903
but do you have any thoughts on this

00:43:58.003 --> 00:43:58.085
one?

00:43:59.574 --> 00:44:00.675
Yeah, I mean, I actually,

00:44:01.114 --> 00:44:01.896
this kind of inspired me.

00:44:01.936 --> 00:44:02.795
I think I want to write a blog

00:44:02.835 --> 00:44:03.255
post now.

00:44:03.356 --> 00:44:04.516
I don't know when it'll come.

00:44:04.657 --> 00:44:06.157
I've got a lot of blog posts in

00:44:06.579 --> 00:44:07.259
the queue right now.

00:44:07.318 --> 00:44:10.260
But this is a common concern,

00:44:10.760 --> 00:44:12.021
even for people that aren't super into

00:44:12.041 --> 00:44:12.481
privacy,

00:44:12.541 --> 00:44:15.864
is people may want one account that they

00:44:15.885 --> 00:44:17.726
just use for, I don't know,

00:44:17.746 --> 00:44:18.806
shit posting or whatever,

00:44:19.447 --> 00:44:22.108
and to another account that's like their

00:44:22.208 --> 00:44:23.849
actual professional account or whatever.

00:44:24.050 --> 00:44:26.751
And if you're not careful, like,

00:44:27.612 --> 00:44:28.934
Facebook will go through and like

00:44:28.994 --> 00:44:29.855
recommend you to ever.

00:44:30.014 --> 00:44:31.516
I've told the story before about how like

00:44:31.536 --> 00:44:32.998
back when I was single years, years ago,

00:44:33.018 --> 00:44:33.880
this is like ten years ago,

00:44:34.501 --> 00:44:36.802
I started talking to a girl and we

00:44:36.822 --> 00:44:38.985
just texted a few times and then she

00:44:39.005 --> 00:44:40.427
showed up on my Facebook is like people

00:44:40.447 --> 00:44:40.827
you may know.

00:44:40.847 --> 00:44:42.050
And I was like, cool, thanks, Facebook.

00:44:42.090 --> 00:44:43.291
I feel like I'm stalking this girl now.

00:44:45.110 --> 00:44:46.711
And Facebook's really aggressive with that

00:44:46.733 --> 00:44:46.992
crap.

00:44:47.032 --> 00:44:49.474
So it's one of those things where I

00:44:49.494 --> 00:44:50.775
wouldn't say it's hard,

00:44:51.396 --> 00:44:52.958
but it requires intentionality.

00:44:53.137 --> 00:44:55.179
And yeah, a lot of people don't realize,

00:44:56.661 --> 00:44:58.882
totally not trying to make fun of anybody

00:44:58.943 --> 00:45:00.003
who doesn't know this stuff, by the way,

00:45:00.063 --> 00:45:02.246
but I always kind of got annoyed by

00:45:02.286 --> 00:45:02.485
like...

00:45:03.467 --> 00:45:04.949
like back on r slash privacy,

00:45:05.489 --> 00:45:06.311
back when I used to go there,

00:45:06.811 --> 00:45:08.353
I would see people asking questions that

00:45:08.393 --> 00:45:09.474
like, oh,

00:45:10.016 --> 00:45:12.139
I signed up for Instagram and Amazon with

00:45:12.159 --> 00:45:14.001
the same account or same username and

00:45:14.021 --> 00:45:15.163
everything, like everything's the same.

00:45:15.704 --> 00:45:17.226
And I don't understand why I'm seeing ads

00:45:17.246 --> 00:45:18.588
for the thing I looked up on Amazon.

00:45:18.628 --> 00:45:19.088
And it's like,

00:45:20.657 --> 00:45:21.657
what do you mean you don't understand?

00:45:21.697 --> 00:45:21.818
Like,

00:45:21.858 --> 00:45:22.918
how do you not know that they can

00:45:22.958 --> 00:45:23.579
tell that's you?

00:45:23.619 --> 00:45:24.320
It's so obvious,

00:45:24.340 --> 00:45:26.222
but a lot of people just don't think

00:45:26.242 --> 00:45:26.961
about that kind of stuff.

00:45:26.981 --> 00:45:27.202
And yeah,

00:45:27.242 --> 00:45:29.704
it can be really overwhelming if, um,

00:45:29.764 --> 00:45:31.045
especially if you're new to this stuff and

00:45:31.206 --> 00:45:31.405
you're,

00:45:31.425 --> 00:45:33.007
you're coming to it for the first time,

00:45:33.027 --> 00:45:34.268
but yeah, things like, um,

00:45:34.449 --> 00:45:36.449
using aliasing email to like separate the

00:45:36.490 --> 00:45:36.971
accounts.

00:45:37.731 --> 00:45:38.271
Um,

00:45:38.311 --> 00:45:40.054
some people mentioned like using VPNs and

00:45:40.074 --> 00:45:41.454
different browsers, um,

00:45:41.474 --> 00:45:43.396
that would probably help different phone

00:45:43.416 --> 00:45:43.797
numbers.

00:45:44.117 --> 00:45:44.277
I mean,

00:45:44.336 --> 00:45:45.737
really just kind of trying to complete,

00:45:46.199 --> 00:45:46.259
uh,

00:45:47.731 --> 00:45:49.112
trying to, Oh my God,

00:45:49.172 --> 00:45:49.992
my brain just blanked on the word,

00:45:50.231 --> 00:45:50.612
treat it,

00:45:50.871 --> 00:45:52.813
trying to treat them as like separate

00:45:52.893 --> 00:45:54.034
identities as much as possible,

00:45:54.054 --> 00:45:55.014
which I know what the phone number thing

00:45:55.054 --> 00:45:57.994
is really difficult, but yeah.

00:45:58.054 --> 00:45:59.115
And it really just depends like what

00:45:59.135 --> 00:46:00.637
you're like one person recommended cycling

00:46:00.677 --> 00:46:01.836
accounts, like start a new account,

00:46:01.876 --> 00:46:02.757
let it age three months,

00:46:03.077 --> 00:46:04.418
then start using it while your usual

00:46:04.438 --> 00:46:05.478
account fades into the past.

00:46:05.798 --> 00:46:05.938
I mean,

00:46:05.958 --> 00:46:07.159
that depends what you're trying to get out

00:46:07.179 --> 00:46:07.760
of it, but yeah,

00:46:07.800 --> 00:46:09.639
that is definitely one strategy for sure.

00:46:10.760 --> 00:46:12.661
I see people have been leaving a lot

00:46:12.742 --> 00:46:12.842
of

00:46:13.987 --> 00:46:14.947
comments here.

00:46:15.248 --> 00:46:16.768
Um,

00:46:16.789 --> 00:46:17.829
somebody said it's difficult to get a

00:46:17.869 --> 00:46:19.230
pseudonymous email account though.

00:46:19.610 --> 00:46:19.769
I mean,

00:46:19.789 --> 00:46:21.070
it depends who you go with and it

00:46:21.090 --> 00:46:22.831
depends how pseudonymous, like it,

00:46:23.431 --> 00:46:24.471
that's always the thing with threat

00:46:24.490 --> 00:46:25.012
modeling, right?

00:46:25.052 --> 00:46:25.592
Like, yeah,

00:46:25.632 --> 00:46:27.072
if you want to make sure that the

00:46:27.192 --> 00:46:29.072
NSA can't figure out who's behind that

00:46:29.092 --> 00:46:30.492
account, that's going to be difficult.

00:46:30.813 --> 00:46:32.034
But if you're just trying to keep like

00:46:32.474 --> 00:46:34.414
LexisNexis from linking those two accounts

00:46:34.434 --> 00:46:35.655
together, I mean,

00:46:36.635 --> 00:46:38.936
I think just using different, uh,

00:46:38.976 --> 00:46:40.556
like simple login emails would probably be

00:46:40.617 --> 00:46:40.876
fine.

00:46:41.757 --> 00:46:42.697
And yeah, like you said,

00:46:42.717 --> 00:46:43.978
with no link at all between that and

00:46:43.998 --> 00:46:44.619
your real identity,

00:46:44.659 --> 00:46:45.518
that's definitely tricky.

00:46:46.579 --> 00:46:46.760
Yeah,

00:46:46.780 --> 00:46:47.519
somebody mentioned they could use

00:46:47.559 --> 00:46:48.280
progressive web apps,

00:46:48.300 --> 00:46:49.380
which are super underrated.

00:46:49.400 --> 00:46:50.320
That's actually one of the reasons I

00:46:50.340 --> 00:46:51.740
wanted to mention this story, I think.

00:46:51.800 --> 00:46:53.181
Or maybe that's our last story.

00:46:53.742 --> 00:46:54.202
I can't remember.

00:46:54.902 --> 00:46:55.983
But yeah,

00:46:56.083 --> 00:46:59.003
PWAs are something that they get mentioned

00:46:59.023 --> 00:46:59.403
a little bit,

00:46:59.423 --> 00:47:00.744
but I feel like people don't talk about

00:47:00.764 --> 00:47:02.364
them enough, in my opinion.

00:47:02.385 --> 00:47:04.405
Definitely.

00:47:05.166 --> 00:47:06.827
I think also the other thing that I

00:47:06.867 --> 00:47:09.389
really like is just separating devices,

00:47:09.688 --> 00:47:12.170
like having separate devices for specific

00:47:12.630 --> 00:47:13.431
purposes, right?

00:47:13.472 --> 00:47:15.534
Because even if you do have to install

00:47:15.554 --> 00:47:16.213
an app, right,

00:47:16.253 --> 00:47:18.215
you've got it on a separate device.

00:47:18.695 --> 00:47:21.036
It doesn't have the actual data there that

00:47:21.077 --> 00:47:22.559
can be accidentally shared, right?

00:47:22.579 --> 00:47:24.579
Because the last thing you want is to

00:47:24.659 --> 00:47:25.219
accidentally...

00:47:26.161 --> 00:47:28.722
accept contact permission on facebook and

00:47:28.762 --> 00:47:31.463
now every single person in your in your

00:47:31.483 --> 00:47:33.465
address book has been sent to facebook and

00:47:33.485 --> 00:47:35.005
now they're suggesting all these people to

00:47:35.045 --> 00:47:36.766
you because that is the way that they

00:47:36.867 --> 00:47:39.768
they kind of connect you basically um your

00:47:39.809 --> 00:47:42.431
contacts is is a big one so you

00:47:42.451 --> 00:47:44.251
know that sort of thing i i'd say

00:47:44.291 --> 00:47:45.873
separate devices if you can afford it

00:47:45.932 --> 00:47:47.193
again it is one of those things where

00:47:47.233 --> 00:47:47.594
it's like

00:47:48.253 --> 00:47:50.715
an expense that not everyone can afford.

00:47:51.637 --> 00:47:53.579
Again, we do recommend Graphene OS,

00:47:53.619 --> 00:47:56.121
so you could do separate profiles for each

00:47:56.181 --> 00:47:56.601
purpose.

00:47:56.721 --> 00:47:58.422
That's another way to compartmentalize

00:47:58.443 --> 00:47:59.163
things a little bit.

00:48:00.585 --> 00:48:01.885
I guess when it comes to accounts,

00:48:01.985 --> 00:48:04.507
I feel like Nate has already mentioned

00:48:05.027 --> 00:48:05.568
everything.

00:48:06.289 --> 00:48:08.331
So I don't really have anything to add

00:48:08.672 --> 00:48:10.213
in terms of that, I would say.

00:48:11.293 --> 00:48:13.956
I did see a comment from somebody here.

00:48:16.362 --> 00:48:16.702
Yes.

00:48:17.063 --> 00:48:18.784
It's also important to recognize whom you

00:48:18.824 --> 00:48:19.744
are trying to separate.

00:48:20.103 --> 00:48:20.704
Your identity,

00:48:20.744 --> 00:48:22.344
much easier to register two Discord

00:48:22.364 --> 00:48:23.824
accounts to separate friends and other

00:48:23.864 --> 00:48:24.405
identities.

00:48:24.965 --> 00:48:26.646
Yeah, so that's kind of the thing, right?

00:48:26.666 --> 00:48:28.686
You know, having separate identities,

00:48:28.726 --> 00:48:33.268
but for different people is one way to

00:48:33.307 --> 00:48:33.768
do that.

00:48:34.009 --> 00:48:34.628
I think it's...

00:48:36.048 --> 00:48:38.329
it's definitely tricky when you start

00:48:38.391 --> 00:48:39.911
meeting people in real life because,

00:48:39.931 --> 00:48:42.293
you know, then you've got like, it's,

00:48:42.572 --> 00:48:44.074
you can't really disconnect your,

00:48:44.193 --> 00:48:48.876
your real like flesh body from to like,

00:48:49.137 --> 00:48:50.378
if you understand what I'm trying to say,

00:48:50.418 --> 00:48:52.260
like you're still the one person,

00:48:52.300 --> 00:48:54.201
but you have two separate identities.

00:48:54.221 --> 00:48:55.320
That's where it becomes trickier.

00:48:57.523 --> 00:48:57.922
But again,

00:48:58.063 --> 00:48:59.483
I think discord is one of those ones

00:48:59.523 --> 00:49:00.045
where it's like,

00:49:00.945 --> 00:49:02.927
Very frustrating to register, you know,

00:49:02.947 --> 00:49:04.710
you need separate phone numbers and all of

00:49:04.730 --> 00:49:05.030
that.

00:49:05.090 --> 00:49:07.173
So again, like, you know,

00:49:07.213 --> 00:49:09.876
stuff like MySudo or I think people in

00:49:09.898 --> 00:49:11.599
the US like to use Google Voice for

00:49:11.619 --> 00:49:11.820
that.

00:49:11.860 --> 00:49:12.221
But again,

00:49:12.701 --> 00:49:14.262
that also could be a concern because then

00:49:14.304 --> 00:49:16.786
Google has access to that information.

00:49:16.927 --> 00:49:17.086
So...

00:49:18.228 --> 00:49:20.672
Separate prepaid SIM cards maybe as well.

00:49:21.411 --> 00:49:23.054
I would recommend that especially because

00:49:23.494 --> 00:49:25.217
a lot of these services require a phone

00:49:25.237 --> 00:49:26.077
number on signup.

00:49:26.117 --> 00:49:26.557
So again,

00:49:27.139 --> 00:49:29.161
buying a separate SIM card specifically

00:49:29.201 --> 00:49:32.344
for Instagram and Facebook that no one

00:49:32.364 --> 00:49:33.967
else has that phone number.

00:49:34.067 --> 00:49:35.829
It's guaranteed for you to not be...

00:49:36.929 --> 00:49:38.510
um suggested to other people because of

00:49:38.530 --> 00:49:40.552
your phone number so i think that's

00:49:40.592 --> 00:49:42.552
definitely one way instagram and and

00:49:42.592 --> 00:49:44.773
facebook kind of creates social maps of

00:49:44.833 --> 00:49:47.695
you um someone here did to have a

00:49:47.735 --> 00:49:49.056
comment though i think i'll throw this

00:49:49.097 --> 00:49:51.737
back to you uh nate who slash what

00:49:51.858 --> 00:49:56.159
is alexis nexus yeah lexus nexus is one

00:49:56.179 --> 00:49:58.902
of the the big data brokers um so

00:49:59.001 --> 00:50:00.342
a lot of the time when we talk

00:50:00.362 --> 00:50:00.882
about like

00:50:01.865 --> 00:50:03.648
Amazon and Facebook and Google collecting

00:50:03.668 --> 00:50:04.088
your data,

00:50:04.128 --> 00:50:07.472
typically they don't sell your data if we

00:50:07.512 --> 00:50:08.211
want to be technical.

00:50:08.753 --> 00:50:12.597
They run ads and they sell access to

00:50:12.637 --> 00:50:13.177
your data.

00:50:14.958 --> 00:50:15.498
However,

00:50:15.559 --> 00:50:17.300
there are certain companies out there like

00:50:17.360 --> 00:50:19.884
LexisNexis that one of their products is

00:50:19.923 --> 00:50:21.946
that they –

00:50:21.505 --> 00:50:23.646
um collect as much data as they can

00:50:24.068 --> 00:50:25.608
and sometimes they will buy it from apps

00:50:25.628 --> 00:50:26.789
you know especially a lot of these smaller

00:50:26.871 --> 00:50:29.652
apps will sell your data to google or

00:50:30.014 --> 00:50:32.235
lexus nexus or there's some other ones i

00:50:32.255 --> 00:50:34.838
think axiom is one um and so they

00:50:34.858 --> 00:50:36.139
are the ones that then a lot of

00:50:36.159 --> 00:50:38.422
the time advertisers who can't collect

00:50:38.442 --> 00:50:40.043
that data on their own so basically not

00:50:40.083 --> 00:50:41.864
google not i mean sometimes google and

00:50:41.905 --> 00:50:43.166
amazon and facebook will go to them but

00:50:43.586 --> 00:50:45.389
Usually their advertising network and

00:50:45.409 --> 00:50:46.590
their data collection networks are so

00:50:46.650 --> 00:50:47.871
extensive they don't really need to.

00:50:48.871 --> 00:50:50.753
But a lot of smaller companies will go

00:50:50.773 --> 00:50:53.355
to LexisNexis and they'll buy – like I

00:50:53.375 --> 00:50:54.757
actually remember back when I lived in

00:50:55.257 --> 00:50:58.179
Texas, I got a mailer one time.

00:50:59.177 --> 00:50:59.597
And for the record,

00:50:59.617 --> 00:51:00.559
I was vegetarian at the time.

00:51:01.219 --> 00:51:02.898
I got a mailer for a barbecue thing

00:51:03.239 --> 00:51:04.039
that was like, oh,

00:51:04.079 --> 00:51:05.039
your birthday is coming up.

00:51:05.079 --> 00:51:05.739
Happy birthday.

00:51:05.780 --> 00:51:05.940
Here,

00:51:05.981 --> 00:51:08.081
come get like a fifty percent off or

00:51:08.121 --> 00:51:08.440
something.

00:51:08.902 --> 00:51:10.922
And I was like super pissed because number

00:51:10.981 --> 00:51:12.422
one, barbecue for a vegetarian.

00:51:12.963 --> 00:51:13.563
And number two,

00:51:13.623 --> 00:51:15.043
like even before I got into privacy,

00:51:15.523 --> 00:51:17.045
I haven't celebrated my birthday in like

00:51:17.125 --> 00:51:17.744
over a decade.

00:51:17.824 --> 00:51:19.164
It's just it's a personal thing.

00:51:20.505 --> 00:51:21.585
It's not like religious or anything.

00:51:21.606 --> 00:51:22.947
It's just like a personal weird quirk of

00:51:22.967 --> 00:51:23.146
mine.

00:51:23.686 --> 00:51:24.226
And so like,

00:51:24.306 --> 00:51:25.527
I was kind of like offended.

00:51:25.547 --> 00:51:27.168
Like I was violently offended that I'm

00:51:27.208 --> 00:51:28.168
like, who are you?

00:51:28.268 --> 00:51:29.528
And how did you get my birthday?

00:51:29.548 --> 00:51:31.530
And I did actually email them and,

00:51:31.650 --> 00:51:32.469
or I called them or something.

00:51:32.489 --> 00:51:32.730
And I'm like,

00:51:32.769 --> 00:51:33.811
where did you get this information?

00:51:33.831 --> 00:51:35.351
And they're like, we bought it from Axiom.

00:51:36.050 --> 00:51:39.012
And I was just like, okay, what?

00:51:39.333 --> 00:51:40.213
Like, yeah.

00:51:40.233 --> 00:51:41.112
So that's where a lot of that stuff

00:51:41.132 --> 00:51:41.572
comes from.

00:51:42.713 --> 00:51:42.974
But yeah.

00:51:44.605 --> 00:51:44.784
Yeah,

00:51:44.804 --> 00:51:46.065
I was going to say the device thing.

00:51:46.585 --> 00:51:48.005
One thing, you know, you did mention that,

00:51:48.025 --> 00:51:48.186
yeah,

00:51:48.206 --> 00:51:50.585
it could be a lot of money potentially

00:51:50.786 --> 00:51:52.686
to have two separate devices and to pay

00:51:52.706 --> 00:51:53.507
for a separate phone number.

00:51:53.867 --> 00:51:55.527
But one thing that could be underrated is

00:51:55.547 --> 00:51:57.427
just holding on to your old devices.

00:51:57.567 --> 00:52:00.367
I mean, like, in my personal opinion,

00:52:00.467 --> 00:52:01.907
if you have a device that you only

00:52:02.007 --> 00:52:04.507
ever turn on once a week and,

00:52:04.588 --> 00:52:04.827
you know,

00:52:04.847 --> 00:52:07.548
that's your device that you use to check

00:52:07.648 --> 00:52:08.929
Instagram or whatever, like,

00:52:09.028 --> 00:52:10.108
I think that's a lot better than putting

00:52:10.208 --> 00:52:12.190
Instagram on your daily driver.

00:52:13.250 --> 00:52:13.389
So...

00:52:14.461 --> 00:52:14.782
I don't know.

00:52:14.822 --> 00:52:17.963
That's my, maybe, maybe a compromise.

00:52:17.983 --> 00:52:19.704
If you can't afford to buy a new,

00:52:20.346 --> 00:52:21.347
a new phone or something,

00:52:21.367 --> 00:52:21.987
or a second phone,

00:52:22.007 --> 00:52:23.347
just hold onto your own old phone when

00:52:23.367 --> 00:52:25.389
you upgrade and use it for throwaway

00:52:25.409 --> 00:52:25.628
stuff.

00:52:25.648 --> 00:52:26.309
That doesn't matter.

00:52:26.369 --> 00:52:26.469
So.

00:52:27.313 --> 00:52:27.713
Yeah,

00:52:27.753 --> 00:52:29.695
someone here also said like Facebook uses

00:52:29.855 --> 00:52:31.215
IP for fingerprinting too,

00:52:31.255 --> 00:52:33.396
so a separate device wouldn't save that.

00:52:33.456 --> 00:52:34.318
Yeah, yeah, definitely.

00:52:34.358 --> 00:52:36.099
Like there's all these sort of things.

00:52:36.119 --> 00:52:38.099
There's so many vectors that we talk

00:52:38.119 --> 00:52:38.340
about.

00:52:38.360 --> 00:52:41.161
It's like using a VPN,

00:52:41.402 --> 00:52:43.083
making sure that you don't connect.

00:52:43.503 --> 00:52:45.324
Like there's all sorts of metadata that

00:52:45.364 --> 00:52:47.385
you don't realize that you're sharing that

00:52:47.425 --> 00:52:49.106
could connect you straight back, like,

00:52:49.126 --> 00:52:49.387
you know,

00:52:50.268 --> 00:52:53.228
I'm sure there's some ridiculous thing

00:52:53.248 --> 00:52:55.208
that they use like Bluetooth scanning or

00:52:55.268 --> 00:52:57.530
Wi-Fi scanning or something like something

00:52:57.550 --> 00:52:58.429
really creepy, right?

00:52:58.570 --> 00:53:00.471
Or something like that, right?

00:53:01.550 --> 00:53:02.210
I can imagine it.

00:53:02.331 --> 00:53:05.871
But I think doing the most that we

00:53:05.891 --> 00:53:09.432
can from at least the known vectors is

00:53:09.472 --> 00:53:11.653
important and using a VPN at the same

00:53:11.693 --> 00:53:11.994
time.

00:53:12.693 --> 00:53:15.056
on a separate device would definitely be

00:53:15.277 --> 00:53:15.717
one of those.

00:53:16.157 --> 00:53:16.597
But again,

00:53:16.637 --> 00:53:18.840
that also gets tricky because signing up

00:53:18.860 --> 00:53:21.742
for accounts with a VPN kind of ties

00:53:21.762 --> 00:53:23.545
back into this comment here that we got

00:53:23.585 --> 00:53:24.284
from Stan.

00:53:25.186 --> 00:53:27.347
When you're using someone else's

00:53:28.088 --> 00:53:30.010
infrastructure or like, you know,

00:53:30.050 --> 00:53:30.911
number in this case,

00:53:31.751 --> 00:53:33.592
there's always the risk that it's tied to

00:53:33.692 --> 00:53:35.393
scammers or like, you know,

00:53:35.413 --> 00:53:37.474
someone who's abusing signups, right?

00:53:37.534 --> 00:53:40.335
So if you use a rented number,

00:53:40.416 --> 00:53:42.077
if you use a rented IP address,

00:53:42.217 --> 00:53:44.418
you're kind of risking that account

00:53:45.030 --> 00:53:47.391
being banned because it's associated with

00:53:48.211 --> 00:53:50.992
uh bad activities that someone's used that

00:53:51.072 --> 00:53:52.693
IP address or in this case a phone

00:53:52.713 --> 00:53:55.574
number to do so um it's kind of

00:53:55.594 --> 00:53:57.393
tricky when it comes to that specifically

00:53:57.713 --> 00:54:00.275
I think one suggestion that I would have

00:54:00.295 --> 00:54:02.496
for like IP addresses is you could try

00:54:02.735 --> 00:54:05.217
traveling to like a library hopping on

00:54:05.237 --> 00:54:07.856
their free wi-fi creating the account at

00:54:07.896 --> 00:54:09.978
the at the library um

00:54:11.246 --> 00:54:11.806
Or, you know,

00:54:11.826 --> 00:54:13.027
just like McDonald's or whatever.

00:54:13.487 --> 00:54:15.168
Any place that has free Wi-Fi, basically.

00:54:15.887 --> 00:54:17.369
So that's a way to kind of bypass

00:54:17.389 --> 00:54:18.068
that, I guess.

00:54:19.070 --> 00:54:19.510
Again, though,

00:54:19.530 --> 00:54:21.731
if you connect with a VPN IP address,

00:54:21.751 --> 00:54:23.411
it still does associate you with that.

00:54:23.552 --> 00:54:24.711
So it's kind of tricky.

00:54:25.373 --> 00:54:26.893
And the rented numbers, I would say,

00:54:27.112 --> 00:54:28.173
is probably less...

00:54:29.474 --> 00:54:30.954
I would probably recommend that less than

00:54:31.014 --> 00:54:32.996
just getting an actual SIM card because at

00:54:33.036 --> 00:54:35.617
least there's some protection and the

00:54:35.858 --> 00:54:37.797
number is actually registered in your name

00:54:37.838 --> 00:54:38.259
instead of...

00:54:39.164 --> 00:54:40.965
the company kind of proxying it, I guess.

00:54:41.405 --> 00:54:42.686
So you don't really own the number in

00:54:42.706 --> 00:54:43.226
that case.

00:54:43.266 --> 00:54:45.588
So that's where it becomes kind of eh,

00:54:45.608 --> 00:54:46.648
because again, you know,

00:54:46.668 --> 00:54:48.829
they could revoke the number or like you

00:54:48.849 --> 00:54:49.010
said,

00:54:49.050 --> 00:54:51.572
it could be used to do illegal stuff.

00:54:51.612 --> 00:54:53.273
So it could be blocked on a bunch

00:54:53.313 --> 00:54:54.833
of services, which is really annoying.

00:54:56.583 --> 00:54:57.364
Yeah, I gotta be honest.

00:54:57.403 --> 00:54:58.085
In my experience,

00:54:58.125 --> 00:55:00.585
those like disposable number services that

00:55:00.625 --> 00:55:01.706
people always talk about online,

00:55:01.726 --> 00:55:02.666
they never work for me.

00:55:02.846 --> 00:55:04.347
Me personally, I don't know what it is.

00:55:04.786 --> 00:55:06.407
I've seen the ones that people like swear

00:55:06.447 --> 00:55:06.788
by them.

00:55:06.827 --> 00:55:07.128
Like, oh,

00:55:07.148 --> 00:55:08.648
I use this to sign up for Discord,

00:55:08.668 --> 00:55:09.688
for Twitter,

00:55:09.728 --> 00:55:10.829
for like all those companies that are

00:55:10.949 --> 00:55:12.590
really strict about using an actual,

00:55:12.969 --> 00:55:14.010
like a real phone number.

00:55:14.590 --> 00:55:16.291
And I've tried several of them and they

00:55:16.391 --> 00:55:17.210
never work for me.

00:55:17.311 --> 00:55:20.731
So, but me, like personally, what I,

00:55:20.751 --> 00:55:22.172
my main thing with those that I'll say

00:55:22.193 --> 00:55:22.652
is,

00:55:22.952 --> 00:55:24.914
is I would never use them for anything

00:55:25.094 --> 00:55:25.795
actually important.

00:55:25.815 --> 00:55:27.036
Like I see people saying like, Oh,

00:55:27.056 --> 00:55:27.876
I want to use it for like a,

00:55:28.438 --> 00:55:29.898
a throwaway Twitter account or whatever.

00:55:29.918 --> 00:55:30.800
And it's like, okay, fine.

00:55:30.840 --> 00:55:32.041
If you know, if it,

00:55:32.061 --> 00:55:32.840
cause my thing is like,

00:55:32.860 --> 00:55:33.822
I don't even think they're going to ban

00:55:33.842 --> 00:55:34.762
you because the phone number,

00:55:35.222 --> 00:55:36.704
my question is what happens when your

00:55:36.724 --> 00:55:38.606
account gets banned and they say, Oh,

00:55:38.646 --> 00:55:39.746
we just texted you a code.

00:55:39.847 --> 00:55:40.567
And it's like, Oh,

00:55:40.907 --> 00:55:41.969
but it was one of those services where

00:55:41.989 --> 00:55:43.349
I only have the phone number for like,

00:55:44.030 --> 00:55:45.190
you're never going to have access to that

00:55:45.210 --> 00:55:45.851
phone number again.

00:55:45.952 --> 00:55:46.913
So now you're just locked out.

00:55:47.293 --> 00:55:49.094
And if it's again, if it's like, um,

00:55:49.974 --> 00:55:52.137
I'm going to be a little bit NSFW

00:55:52.157 --> 00:55:53.199
here just for the sake of it.

00:55:53.239 --> 00:55:55.722
But if it's the account that you use

00:55:55.762 --> 00:55:57.003
on Twitter just to look at porn,

00:55:57.485 --> 00:55:58.326
then it doesn't matter.

00:55:58.626 --> 00:56:00.148
But if it's your actual Twitter account

00:56:00.168 --> 00:56:01.911
that you're using to like build a brand

00:56:02.030 --> 00:56:02.911
and you get locked out,

00:56:03.938 --> 00:56:04.980
Now what?

00:56:05.000 --> 00:56:05.239
You know,

00:56:05.340 --> 00:56:07.940
if it's your actual like bank account,

00:56:07.960 --> 00:56:09.382
like I've seen people recommend that.

00:56:09.402 --> 00:56:09.961
Like, oh,

00:56:09.981 --> 00:56:11.563
I'm trying to use this like SMS pool

00:56:11.583 --> 00:56:12.643
to sign up for my bank account.

00:56:12.983 --> 00:56:13.443
Why?

00:56:14.023 --> 00:56:14.864
That's insane.

00:56:14.985 --> 00:56:16.246
I've been locked out of my bank account

00:56:16.306 --> 00:56:18.487
multiple times for the weirdest stuff for

00:56:18.527 --> 00:56:18.967
some reason.

00:56:19.387 --> 00:56:19.788
And it's like,

00:56:19.867 --> 00:56:21.128
what would I do if it's like, oh,

00:56:21.148 --> 00:56:22.409
I can't prove that I own this bank

00:56:22.449 --> 00:56:22.708
account.

00:56:22.748 --> 00:56:23.630
Like, I don't know.

00:56:23.650 --> 00:56:25.289
That just sounds insane to me personally.

00:56:25.431 --> 00:56:27.711
I would never use it for anything that

00:56:27.791 --> 00:56:29.853
you would be upset losing access to is

00:56:29.932 --> 00:56:31.313
the only piece of advice that I'll give

00:56:31.333 --> 00:56:31.614
for that.

00:56:34.869 --> 00:56:35.869
I know we should move on here in

00:56:35.889 --> 00:56:36.851
a minute, but Foundog said,

00:56:37.110 --> 00:56:38.393
you can fingerprint based on how many

00:56:38.432 --> 00:56:39.914
lines your mouse wheel is configured to

00:56:39.934 --> 00:56:41.797
scroll or the mouse acceleration settings

00:56:41.817 --> 00:56:42.458
you have configured.

00:56:42.478 --> 00:56:43.960
It's wild the things companies can do.

00:56:44.340 --> 00:56:45.141
Yeah, and that's what I mean.

00:56:45.161 --> 00:56:45.360
Again,

00:56:45.501 --> 00:56:47.063
I've seen proofs of concept that

00:56:47.143 --> 00:56:48.764
fingerprinting can work with CSS.

00:56:48.824 --> 00:56:49.166
I've seen

00:56:49.686 --> 00:56:52.608
proofs of concept about fingerprinting um

00:56:52.648 --> 00:56:54.509
you know how many uh extensions you have

00:56:54.548 --> 00:56:55.590
i know we've talked about that in the

00:56:55.610 --> 00:56:57.550
past like it's there's so many different

00:56:57.570 --> 00:56:58.931
ways it's one of those things to me

00:56:58.952 --> 00:56:59.952
it's one of those things where if you're

00:56:59.972 --> 00:57:01.592
not careful you can fall down a rabbit

00:57:01.652 --> 00:57:04.195
hole and absolutely stress yourself out

00:57:04.295 --> 00:57:05.896
over like oh my god but what if

00:57:05.936 --> 00:57:07.757
and it's like but does it really matter

00:57:07.797 --> 00:57:09.318
like for some people yes it does again

00:57:09.657 --> 00:57:11.498
use tor but like for most of us

00:57:11.539 --> 00:57:12.059
it's like it's

00:57:12.500 --> 00:57:14.521
I, again, going back to Brett,

00:57:14.541 --> 00:57:15.742
this is why I stopped going on Reddit,

00:57:16.003 --> 00:57:17.143
but like our slash privacy,

00:57:17.284 --> 00:57:18.726
I used to see people like make posts

00:57:19.045 --> 00:57:21.007
where they would be having like nuclear

00:57:21.128 --> 00:57:22.829
meltdowns because they're like, oh my God,

00:57:23.208 --> 00:57:24.831
I logged into Google one time without my

00:57:24.871 --> 00:57:25.210
VPN.

00:57:25.231 --> 00:57:26.952
Or like I checked Google once or went

00:57:26.972 --> 00:57:27.612
to Google search.

00:57:27.893 --> 00:57:28.653
How screwed am I?

00:57:28.693 --> 00:57:29.795
And it's like, does it,

00:57:30.275 --> 00:57:31.137
are you Edward Snowden?

00:57:31.257 --> 00:57:31.396
Like,

00:57:31.416 --> 00:57:33.659
does it matter if Google got your IP

00:57:33.679 --> 00:57:34.358
address once?

00:57:35.380 --> 00:57:36.521
It's not the end of the world, man.

00:57:36.541 --> 00:57:36.940
Chill.

00:57:37.061 --> 00:57:37.681
I don't know.

00:57:37.722 --> 00:57:37.922
To me,

00:57:38.842 --> 00:57:40.443
there's better ways to spend your energy,

00:57:40.483 --> 00:57:41.264
in my personal opinion.

00:57:41.284 --> 00:57:41.644
I don't know.

00:57:41.864 --> 00:57:43.106
Maybe I'm being a little insensitive,

00:57:43.166 --> 00:57:46.427
but that's... Yeah.

00:57:46.688 --> 00:57:47.248
What do you mean, Nate?

00:57:47.268 --> 00:57:49.050
You've got to disconnect your internet

00:57:49.070 --> 00:57:51.251
connection and go live in the middle of

00:57:51.271 --> 00:57:52.211
the woods or something?

00:57:53.693 --> 00:57:55.914
You know, the more I work in tech,

00:57:55.934 --> 00:57:57.576
the more I understand why so many people

00:57:57.615 --> 00:57:58.556
do that.

00:57:58.597 --> 00:57:59.938
They retire after twenty years in IT,

00:57:59.958 --> 00:58:00.577
and they're like,

00:58:00.617 --> 00:58:01.277
I'm just going to go live in a

00:58:01.318 --> 00:58:01.699
farm,

00:58:01.739 --> 00:58:01.818
and

00:58:02.824 --> 00:58:03.324
I don't know, man.

00:58:03.463 --> 00:58:05.284
I'm going to be honest.

00:58:05.523 --> 00:58:07.045
I've worked very hard to create a life

00:58:07.125 --> 00:58:09.925
where I can disconnect, and I love it.

00:58:10.164 --> 00:58:11.505
Because I am an introvert,

00:58:11.565 --> 00:58:12.266
and I do like to...

00:58:12.286 --> 00:58:13.266
I know we're really off topic now,

00:58:13.286 --> 00:58:14.385
but I'm an introvert.

00:58:14.445 --> 00:58:15.166
I love video games.

00:58:15.206 --> 00:58:15.945
I love movies,

00:58:16.445 --> 00:58:17.606
and I love to stay at home.

00:58:17.987 --> 00:58:19.847
But I love the fact that I can

00:58:19.927 --> 00:58:22.086
shut everything down and just play video

00:58:22.106 --> 00:58:22.327
games.

00:58:22.447 --> 00:58:23.768
I don't get notifications.

00:58:24.108 --> 00:58:25.128
I don't get emails.

00:58:25.447 --> 00:58:27.088
I don't get messages unless they're from

00:58:27.168 --> 00:58:28.208
approved contacts.

00:58:28.528 --> 00:58:30.128
And it is just so wonderful to...

00:58:31.369 --> 00:58:32.809
It's almost as good as touching grass.

00:58:32.889 --> 00:58:33.210
And it's like,

00:58:33.271 --> 00:58:35.672
I'm just going to go play Jurassic World

00:58:35.711 --> 00:58:37.893
Evolution and watch Star Trek.

00:58:38.094 --> 00:58:38.974
And that's going to be my evening.

00:58:38.994 --> 00:58:40.096
That probably is going to be my evening

00:58:40.135 --> 00:58:40.856
tonight, actually.

00:58:40.876 --> 00:58:41.737
That's usually what I do.

00:58:41.936 --> 00:58:43.277
So it's great.

00:58:43.557 --> 00:58:43.958
It's great.

00:58:44.059 --> 00:58:46.000
We should all learn how to disconnect from

00:58:46.280 --> 00:58:46.760
time to time.

00:58:49.541 --> 00:58:49.862
I think I'll,

00:58:49.922 --> 00:58:51.342
I'll read this last comment and then we'll

00:58:51.362 --> 00:58:52.083
jump into the next story.

00:58:52.143 --> 00:58:53.063
Cause we've been on this one for a

00:58:53.103 --> 00:58:54.284
minute, but it says, uh, hello.

00:58:54.304 --> 00:58:55.324
So that reminds me of how I got

00:58:55.385 --> 00:58:56.204
locked out of WhatsApp.

00:58:56.244 --> 00:58:57.286
I got curious if I could set up

00:58:57.306 --> 00:58:59.527
parental access without some verification

00:58:59.567 --> 00:59:00.086
and password.

00:59:00.186 --> 00:59:01.788
I entered that I was born zero days

00:59:01.847 --> 00:59:03.128
ago and had to upload.

00:59:03.248 --> 00:59:05.329
Oh, that's a good one.

00:59:05.469 --> 00:59:05.929
That's funny.

00:59:05.949 --> 00:59:07.630
Um, yeah, yeah.

00:59:07.990 --> 00:59:09.052
That kind of stuff happens, man.

00:59:09.211 --> 00:59:09.552
I, um,

00:59:11.297 --> 00:59:12.739
Oh, what was it just the other day?

00:59:12.918 --> 00:59:13.478
I accidentally,

00:59:13.539 --> 00:59:16.599
I've been messing with changing the ports

00:59:16.760 --> 00:59:19.300
for SSH just for, you know,

00:59:19.320 --> 00:59:20.420
we talked about defense in depth.

00:59:20.521 --> 00:59:21.740
I don't rely on security through

00:59:21.760 --> 00:59:22.601
obscurity, but it's, you know,

00:59:22.922 --> 00:59:24.422
I do the whole, like I disable Rue.

00:59:25.123 --> 00:59:26.402
I make it SSH key login,

00:59:26.682 --> 00:59:27.422
but I was like, yeah, you know,

00:59:27.443 --> 00:59:28.963
I'll stop just like the low level scanners

00:59:29.003 --> 00:59:29.244
and stuff.

00:59:29.264 --> 00:59:31.385
I'll change the port and like completely

00:59:31.425 --> 00:59:32.264
locked myself out of,

00:59:32.304 --> 00:59:34.445
I think it was pure tube the other

00:59:34.485 --> 00:59:34.565
day.

00:59:35.606 --> 00:59:36.487
And then I had to like go to

00:59:36.527 --> 00:59:38.068
Hetzner's website and I had to open their

00:59:38.108 --> 00:59:40.030
console and I had to like enter the

00:59:40.570 --> 00:59:42.572
recovery environment and figure out how to

00:59:42.652 --> 00:59:44.635
edit the, oh man, it was nuts.

00:59:44.675 --> 00:59:45.195
But yeah,

00:59:46.197 --> 00:59:48.338
that's a funny thing about technology is

00:59:48.418 --> 00:59:50.942
you can absolutely lock yourself out if

00:59:50.961 --> 00:59:52.123
you are not being careful.

00:59:53.335 --> 00:59:54.597
But anyways, yeah.

00:59:54.677 --> 00:59:54.878
Okay.

00:59:54.958 --> 00:59:55.197
With that,

00:59:55.217 --> 00:59:56.559
we'll move on to our next story,

00:59:56.940 --> 00:59:58.141
which I'm actually kind of excited about

00:59:58.181 --> 00:59:58.802
this one personally.

00:59:58.882 --> 00:59:59.302
You know, it's funny.

00:59:59.322 --> 01:00:01.344
We were just talking about Facebook and

01:00:01.364 --> 01:00:03.527
Instagram and metadata and all this kind

01:00:03.547 --> 01:00:03.867
of stuff.

01:00:04.347 --> 01:00:06.469
And Brave has announced this new feature

01:00:06.610 --> 01:00:07.990
that removes the tracking data,

01:00:08.211 --> 01:00:09.753
metadata from Instagram and Facebook

01:00:09.773 --> 01:00:10.153
photos.

01:00:10.574 --> 01:00:12.755
So this is starting in desktop version one

01:00:12.815 --> 01:00:13.677
dot nine eight.

01:00:14.237 --> 01:00:14.378
And

01:00:15.418 --> 01:00:16.460
This is actually really interesting.

01:00:16.519 --> 01:00:17.719
So a lot of you guys probably know

01:00:17.739 --> 01:00:19.762
that when you take a photo, you know,

01:00:19.782 --> 01:00:20.902
on your phone or something for most

01:00:20.942 --> 01:00:22.182
people, except for graphene users,

01:00:22.943 --> 01:00:24.545
your camera will automatically record a

01:00:24.605 --> 01:00:25.304
certain amount of metadata.

01:00:25.324 --> 01:00:27.206
And depending on how much access it has,

01:00:27.246 --> 01:00:29.067
it could record things like location and

01:00:29.146 --> 01:00:29.768
date and time,

01:00:30.228 --> 01:00:31.568
or it could just say simple things like,

01:00:31.588 --> 01:00:31.829
you know,

01:00:31.849 --> 01:00:33.969
a pixel eight a took this camera or

01:00:33.989 --> 01:00:34.650
whatever, or photo.

01:00:36.211 --> 01:00:37.672
When you upload that online,

01:00:38.652 --> 01:00:40.114
Most big tech websites.

01:00:40.134 --> 01:00:41.034
And this is the one thing I can

01:00:41.054 --> 01:00:41.835
say good about that.

01:00:41.856 --> 01:00:42.456
Maybe not the one thing,

01:00:42.476 --> 01:00:43.336
but one of the few good things I

01:00:43.356 --> 01:00:43.856
can say about them.

01:00:44.318 --> 01:00:45.699
Most of them will strip that metadata.

01:00:46.039 --> 01:00:46.298
Um,

01:00:46.358 --> 01:00:47.219
I wouldn't be surprised if they're

01:00:47.239 --> 01:00:48.460
recording it and they're storing it

01:00:48.501 --> 01:00:49.242
somewhere on their end,

01:00:49.561 --> 01:00:50.922
but at least publicly, you know,

01:00:50.983 --> 01:00:51.663
most of the time,

01:00:51.804 --> 01:00:53.184
if somebody checks a photo you sent

01:00:53.204 --> 01:00:54.525
through discord or.

01:00:55.226 --> 01:00:56.027
Facebook or whatever.

01:00:56.126 --> 01:00:56.686
As far as I know,

01:00:56.766 --> 01:00:57.827
most of the time they won't really be

01:00:57.867 --> 01:00:58.768
able to pull that metadata.

01:00:59.869 --> 01:01:01.429
This is not so much true on smaller

01:01:01.449 --> 01:01:02.550
platforms like Mastodon.

01:01:02.590 --> 01:01:03.771
So be mindful.

01:01:04.110 --> 01:01:05.512
We definitely encourage you to strip your

01:01:05.612 --> 01:01:07.193
own metadata because then the company

01:01:07.233 --> 01:01:08.853
can't store it on their end either.

01:01:08.934 --> 01:01:09.835
It's definitely a good idea.

01:01:11.436 --> 01:01:12.936
But what's interesting is this story is

01:01:12.976 --> 01:01:14.657
talking about not that metadata that you

01:01:14.757 --> 01:01:15.117
upload,

01:01:15.557 --> 01:01:17.358
but apparently when you upload something

01:01:17.398 --> 01:01:18.340
to Facebook or Instagram,

01:01:18.900 --> 01:01:21.101
there's a uh they add their own piece

01:01:21.141 --> 01:01:25.364
of metadata called the um well they don't

01:01:25.385 --> 01:01:26.606
know what it's called because facebook

01:01:26.626 --> 01:01:29.068
didn't really say here but um they say

01:01:29.108 --> 01:01:30.349
they add a value to the special

01:01:30.409 --> 01:01:32.831
instructions field that starts with fbmd

01:01:32.911 --> 01:01:34.192
and is followed by a long string of

01:01:34.251 --> 01:01:36.373
characters and for those of you watching

01:01:36.413 --> 01:01:39.034
you can see this right here actually and

01:01:39.054 --> 01:01:40.677
uh they say that um

01:01:42.021 --> 01:01:44.364
When you download a photo and upload it

01:01:44.385 --> 01:01:46.047
again, that value stays the same.

01:01:46.547 --> 01:01:47.648
And so even if,

01:01:47.728 --> 01:01:48.650
and I'm sure a lot of you guys

01:01:48.670 --> 01:01:49.050
have seen this,

01:01:49.070 --> 01:01:51.974
if you send like an Instagram link to

01:01:52.094 --> 01:01:53.836
a friend, you can,

01:01:54.759 --> 01:01:55.980
if you know what you're doing and they

01:01:56.000 --> 01:01:56.760
haven't encrypted it,

01:01:57.041 --> 01:01:58.563
you can remove the tracking part of that

01:01:58.603 --> 01:01:58.824
link.

01:01:59.744 --> 01:02:00.786
Um, but what you're,

01:02:00.806 --> 01:02:01.686
what they're saying here is like,

01:02:01.726 --> 01:02:03.166
let's say you want to get really tricky

01:02:03.186 --> 01:02:03.367
with it.

01:02:03.387 --> 01:02:03.567
And like,

01:02:03.606 --> 01:02:04.648
I don't even want to send this personal

01:02:04.748 --> 01:02:04.967
link.

01:02:05.068 --> 01:02:06.188
I don't want Facebook to know that I

01:02:06.228 --> 01:02:06.768
sent this person.

01:02:07.108 --> 01:02:08.869
I'm going to download that picture or

01:02:08.889 --> 01:02:09.530
video or whatever,

01:02:09.891 --> 01:02:11.070
and then send it directly to them.

01:02:11.411 --> 01:02:12.891
When they look at it, Facebook can still,

01:02:12.952 --> 01:02:13.773
or if they upload it,

01:02:13.793 --> 01:02:15.153
Facebook can still tell because this

01:02:15.213 --> 01:02:16.875
freaking thing is buried in the metadata.

01:02:17.494 --> 01:02:17.994
So anyways,

01:02:18.494 --> 01:02:20.356
Brave has now introduced this new feature

01:02:20.775 --> 01:02:22.115
that says when you save an image,

01:02:22.155 --> 01:02:23.675
they remove the identifier before the

01:02:23.715 --> 01:02:24.416
download finishes.

01:02:24.856 --> 01:02:26.157
And when you upload an image,

01:02:26.356 --> 01:02:29.318
they upload a clean copy with no metadata

01:02:29.378 --> 01:02:29.597
on it.

01:02:29.958 --> 01:02:31.717
This is written in C++ with no extra

01:02:31.737 --> 01:02:32.137
library.

01:02:32.157 --> 01:02:33.199
So it stays small and fast.

01:02:33.579 --> 01:02:35.739
And it is posted on GitHub for those

01:02:35.759 --> 01:02:37.239
of you who are more technical and want

01:02:37.260 --> 01:02:37.800
to check it out.

01:02:39.030 --> 01:02:40.932
So yeah,

01:02:40.972 --> 01:02:42.393
I guess right now it only works in

01:02:42.673 --> 01:02:44.514
Facebook and Instagram.

01:02:44.835 --> 01:02:45.755
They say that in the future,

01:02:45.775 --> 01:02:47.157
we would like to remove geolocation,

01:02:47.257 --> 01:02:48.737
device, date, and time data.

01:02:48.798 --> 01:02:50.320
So again, this does not remove everything.

01:02:50.380 --> 01:02:52.981
This only removes that one identifier.

01:02:53.402 --> 01:02:54.762
So we still recommend things like the

01:02:54.782 --> 01:02:56.003
Graphene OS camera, for example,

01:02:56.043 --> 01:02:57.605
which automatically removes metadata.

01:02:58.766 --> 01:02:59.407
Super convenient.

01:02:59.766 --> 01:03:01.188
If you're on an iPhone or you can't

01:03:01.268 --> 01:03:02.969
use the Graphene camera for whatever

01:03:03.009 --> 01:03:03.309
reason,

01:03:03.809 --> 01:03:05.130
a quick and dirty trick is just to

01:03:05.170 --> 01:03:06.211
send it to yourself in Signal.

01:03:07.913 --> 01:03:09.574
I don't know if that removes everything,

01:03:09.614 --> 01:03:10.655
but I know it removes a good chunk

01:03:10.695 --> 01:03:11.056
of stuff.

01:03:11.697 --> 01:03:13.217
I think there is actually one good

01:03:13.277 --> 01:03:15.059
metadata removal tool that I have to go

01:03:15.079 --> 01:03:15.739
looking for again.

01:03:15.940 --> 01:03:16.760
I can't remember what it is.

01:03:16.800 --> 01:03:18.202
But yeah, so again,

01:03:18.242 --> 01:03:19.684
this is like a layer of defense.

01:03:19.923 --> 01:03:22.507
And they say that they are also planning

01:03:22.527 --> 01:03:23.987
to bring this feature to Android and iOS.

01:03:24.509 --> 01:03:26.190
And I personally am hoping that they will

01:03:26.210 --> 01:03:29.313
bring it to other platforms as well.

01:03:29.333 --> 01:03:29.492
I mean,

01:03:29.512 --> 01:03:30.474
I don't know how many platforms are

01:03:30.494 --> 01:03:32.215
tracking you as aggressively as Meta,

01:03:32.335 --> 01:03:32.516
but...

01:03:34.777 --> 01:03:35.318
Yeah,

01:03:35.398 --> 01:03:37.179
I think that's kind of all I've got

01:03:37.260 --> 01:03:37.820
on that one.

01:03:39.501 --> 01:03:40.001
I know, Jordan,

01:03:40.021 --> 01:03:41.282
you mentioned that it would be really cool

01:03:41.302 --> 01:03:43.125
to see other browsers start doing this

01:03:43.144 --> 01:03:44.005
kind of stuff, too.

01:03:44.206 --> 01:03:46.827
Do you have any thoughts on that?

01:03:46.967 --> 01:03:49.110
Every time I hear of Brave adding new

01:03:49.130 --> 01:03:50.610
features like this, it's always like, oh,

01:03:50.650 --> 01:03:51.711
yeah, this should have just been here.

01:03:52.351 --> 01:03:53.813
This should have been by default.

01:03:53.833 --> 01:03:54.873
This should have just been the way that

01:03:54.914 --> 01:03:55.514
it worked.

01:03:55.715 --> 01:03:57.076
It's kind of ridiculous.

01:03:57.175 --> 01:03:59.697
I heard they've got this feature called

01:04:00.539 --> 01:04:01.360
force paste.

01:04:02.019 --> 01:04:02.380
And I'm like,

01:04:02.679 --> 01:04:03.920
why doesn't every browser have that?

01:04:03.960 --> 01:04:05.141
That's so useful.

01:04:05.882 --> 01:04:06.322
Same with this.

01:04:06.382 --> 01:04:06.702
It's like,

01:04:07.222 --> 01:04:08.643
now you don't have to worry about

01:04:08.742 --> 01:04:10.083
uploading and downloading files.

01:04:10.224 --> 01:04:11.003
It'll be clean.

01:04:11.563 --> 01:04:12.684
It's just the way that it should be

01:04:12.704 --> 01:04:13.465
in the first place.

01:04:13.505 --> 01:04:14.726
Because again,

01:04:15.146 --> 01:04:18.027
I think a lot of the specific metadata

01:04:18.067 --> 01:04:21.688
that exists on files is useful when it's

01:04:21.849 --> 01:04:22.630
in your library.

01:04:22.730 --> 01:04:23.789
When it's in your photo library,

01:04:23.809 --> 01:04:24.369
it's like, oh,

01:04:24.469 --> 01:04:25.751
I want to know when this picture was

01:04:25.771 --> 01:04:26.090
taken.

01:04:26.210 --> 01:04:27.992
I want to know all these extra details.

01:04:28.052 --> 01:04:29.853
But when you share that photo,

01:04:30.293 --> 01:04:32.153
you don't want that extra information to

01:04:32.193 --> 01:04:33.914
be shared as well because, you know,

01:04:33.994 --> 01:04:35.875
obviously, like, you know,

01:04:36.014 --> 01:04:40.657
it's something that is... Oh,

01:04:40.677 --> 01:04:42.556
we had a comment here from Firewall's

01:04:42.577 --> 01:04:43.396
Don't Stop Dragons.

01:04:43.737 --> 01:04:44.458
Exif tool.

01:04:46.257 --> 01:04:47.018
I replied to him.

01:04:47.139 --> 01:04:49.039
I don't know if that was it.

01:04:49.059 --> 01:04:49.840
Maybe.

01:04:51.039 --> 01:04:52.501
I think it's a successor to, like,

01:04:52.541 --> 01:04:53.981
Scrambled Exif because I don't think that

01:04:54.061 --> 01:04:55.061
one's maintained anymore.

01:04:55.101 --> 01:04:56.141
So maybe it is Exif tool.

01:04:56.181 --> 01:04:57.922
I'd have to go digging around.

01:04:57.961 --> 01:04:59.802
I really need to remember, but...

01:05:01.157 --> 01:05:01.318
Yeah.

01:05:01.518 --> 01:05:01.677
Yeah.

01:05:01.737 --> 01:05:02.298
Like you were saying,

01:05:02.338 --> 01:05:04.500
like that's brave said that to this data

01:05:04.539 --> 01:05:06.601
might have legitimate uses the metadata

01:05:06.621 --> 01:05:07.601
you were talking about, for example,

01:05:07.681 --> 01:05:09.322
organizing your online photo library.

01:05:09.342 --> 01:05:09.663
Like, you know,

01:05:09.702 --> 01:05:11.945
some people I don't turn on the location

01:05:11.965 --> 01:05:12.565
data, but, you know,

01:05:12.585 --> 01:05:14.005
some people go on vacation and turn it

01:05:14.146 --> 01:05:14.306
on.

01:05:14.405 --> 01:05:16.246
And then like NT, for example,

01:05:16.588 --> 01:05:18.068
will automatically group all that together

01:05:18.088 --> 01:05:18.588
and be like, oh,

01:05:18.628 --> 01:05:21.371
here's your trip to Miami Beach or

01:05:21.391 --> 01:05:21.771
whatever.

01:05:21.911 --> 01:05:22.251
I don't know.

01:05:22.490 --> 01:05:23.032
Don't go to Miami.

01:05:23.931 --> 01:05:24.313
I'm biased.

01:05:24.333 --> 01:05:24.512
Yeah.

01:05:24.532 --> 01:05:28.637
And it's, it's also a safety thing.

01:05:28.657 --> 01:05:30.039
And I think a lot of cases,

01:05:30.458 --> 01:05:30.679
you know,

01:05:30.739 --> 01:05:33.161
that location data is like extremely

01:05:33.222 --> 01:05:34.083
problematic, right?

01:05:34.123 --> 01:05:35.744
Because if someone has access to that,

01:05:35.925 --> 01:05:36.226
you know,

01:05:36.425 --> 01:05:37.967
maybe that picture that you took inside

01:05:37.987 --> 01:05:38.507
your home,

01:05:38.789 --> 01:05:40.431
now they have exact coordinates of where

01:05:40.471 --> 01:05:40.911
you live.

01:05:41.050 --> 01:05:41.692
So it's,

01:05:41.911 --> 01:05:43.813
That is like a pretty big safety concern.

01:05:44.172 --> 01:05:45.713
As far as, like you said, though,

01:05:46.054 --> 01:05:46.873
as far as we know,

01:05:46.934 --> 01:05:49.034
like these big tech companies were not

01:05:49.574 --> 01:05:51.896
just like straight up allowing that data

01:05:51.936 --> 01:05:52.456
to exist.

01:05:53.476 --> 01:05:56.757
Usually they would use it for,

01:05:56.858 --> 01:05:58.559
I know Instagram did do this before,

01:05:58.619 --> 01:06:01.400
but it would give a rough location.

01:06:01.820 --> 01:06:03.981
It would add a location tag to the

01:06:04.021 --> 01:06:06.161
specific photo that you post and it

01:06:06.181 --> 01:06:06.862
wouldn't be, you know,

01:06:07.023 --> 01:06:08.023
a specific location.

01:06:09.282 --> 01:06:10.362
like it wouldn't add the actual

01:06:10.382 --> 01:06:11.864
coordinates that you took the photo,

01:06:12.003 --> 01:06:12.264
right?

01:06:12.344 --> 01:06:14.126
It would just be a general location.

01:06:14.686 --> 01:06:17.507
So whether they use that for, you know,

01:06:17.867 --> 01:06:18.829
I'm sure that, like you said,

01:06:18.869 --> 01:06:20.469
they use that for some other tracking

01:06:20.530 --> 01:06:20.909
purpose.

01:06:20.949 --> 01:06:21.791
I'm sure like, oh,

01:06:21.831 --> 01:06:23.132
you took this photo in this specific

01:06:23.172 --> 01:06:23.592
location.

01:06:23.632 --> 01:06:24.432
Now we know where you've been.

01:06:25.072 --> 01:06:26.353
So, yeah,

01:06:26.554 --> 01:06:27.894
there's lots of lots of cases where

01:06:27.934 --> 01:06:30.115
metadata can can kind of mess you up.

01:06:30.836 --> 01:06:31.577
Firewalls don't stop.

01:06:31.597 --> 01:06:33.599
Dragon said John McAfee.

01:06:33.719 --> 01:06:35.699
I'm not exactly familiar with the John

01:06:35.719 --> 01:06:36.740
McAfee situation,

01:06:36.760 --> 01:06:38.722
but I assume it was it was related

01:06:38.762 --> 01:06:40.382
to like metadata being leaked or something

01:06:40.402 --> 01:06:41.523
like that.

01:06:41.543 --> 01:06:42.304
That'd be my guess.

01:06:42.324 --> 01:06:43.425
Or maybe they were able to figure out

01:06:43.465 --> 01:06:44.686
where he was in the photos.

01:06:45.346 --> 01:06:46.246
So, I mean,

01:06:46.567 --> 01:06:47.688
I know I've said this before, but yeah,

01:06:47.708 --> 01:06:50.730
photos are I'm super paranoid about

01:06:52.043 --> 01:06:54.065
Um, like again, my last apartment, uh,

01:06:54.085 --> 01:06:55.827
that my wife and I,

01:06:55.867 --> 01:06:57.007
when we first moved in and we were

01:06:57.027 --> 01:06:57.887
kind of figuring out like,

01:06:57.927 --> 01:06:59.748
where do we want to put everything?

01:06:59.789 --> 01:06:59.909
Like,

01:06:59.929 --> 01:07:00.809
where do we want to put our desks

01:07:00.829 --> 01:07:01.190
and stuff?

01:07:01.670 --> 01:07:02.831
And I remember telling her, I'm like,

01:07:03.510 --> 01:07:05.072
I will not have my desk facing out

01:07:05.092 --> 01:07:05.472
the window.

01:07:06.072 --> 01:07:07.173
Um, because like,

01:07:07.233 --> 01:07:08.233
even though it was just a street,

01:07:08.295 --> 01:07:08.835
it wasn't like,

01:07:09.195 --> 01:07:11.335
like a clearly visible skyline.

01:07:11.396 --> 01:07:13.077
It's like, Oh, he lives, you know,

01:07:13.117 --> 01:07:13.757
near this city.

01:07:13.797 --> 01:07:14.719
But it was like, I just,

01:07:15.318 --> 01:07:16.199
I know I've seen,

01:07:16.559 --> 01:07:17.519
I think I've told the story about when

01:07:17.559 --> 01:07:18.900
I was in Poland, I, um,

01:07:18.940 --> 01:07:20.141
I was taking a train and

01:07:20.222 --> 01:07:21.822
And I just took a random photo out

01:07:21.862 --> 01:07:23.503
from the train and put it in my

01:07:23.543 --> 01:07:24.103
signal story.

01:07:24.202 --> 01:07:25.583
And one of my friends saw that photo

01:07:25.643 --> 01:07:27.164
and to his defense, he's a geo guesser.

01:07:27.184 --> 01:07:29.344
He does that for fun, but he instantly,

01:07:29.384 --> 01:07:30.043
he's like, Oh,

01:07:30.063 --> 01:07:31.063
you're in this town in Poland.

01:07:31.083 --> 01:07:32.824
And I'm like, am I?

01:07:32.965 --> 01:07:34.065
And I like pulled up the maps and

01:07:34.085 --> 01:07:34.445
I looked at it.

01:07:34.465 --> 01:07:36.525
I'm like, how did you know that?

01:07:36.545 --> 01:07:37.326
And he's like, well, for one,

01:07:37.346 --> 01:07:37.885
they have the,

01:07:38.465 --> 01:07:40.806
the sidewalk stripes are like unique in

01:07:40.847 --> 01:07:41.126
Poland.

01:07:41.166 --> 01:07:41.606
And then he's like,

01:07:41.626 --> 01:07:42.786
but also that building is like,

01:07:43.126 --> 01:07:44.567
I guess like the tallest building in

01:07:44.606 --> 01:07:45.367
Poland or something.

01:07:45.387 --> 01:07:46.847
And yeah, it's, um,

01:07:47.867 --> 01:07:49.929
It's crazy what people can figure out.

01:07:50.369 --> 01:07:51.730
Again, I trusted that person,

01:07:51.750 --> 01:07:53.130
which is why he had access to that

01:07:53.170 --> 01:07:53.731
signal photo.

01:07:53.771 --> 01:07:56.652
But people are pretty wild with what they

01:07:56.672 --> 01:07:59.873
can pull off a photo.

01:07:59.893 --> 01:08:01.554
Kerry said that apparently Vice magazine

01:08:01.594 --> 01:08:02.675
posted an image of him when he was

01:08:02.715 --> 01:08:04.356
on the lam and didn't strip the GPS

01:08:04.416 --> 01:08:04.757
info.

01:08:05.416 --> 01:08:07.637
Womp womp.

01:08:07.677 --> 01:08:08.179
So again, yeah,

01:08:08.759 --> 01:08:11.300
don't depend on Facebook or Vice or

01:08:11.340 --> 01:08:12.740
anybody else to strip the metadata for

01:08:12.820 --> 01:08:12.920
you.

01:08:12.960 --> 01:08:14.282
Make sure you're doing that yourself.

01:08:16.106 --> 01:08:16.506
Definitely.

01:08:16.747 --> 01:08:18.268
We did get a comment here from hello,

01:08:18.307 --> 01:08:19.909
six, four, four, six.

01:08:20.409 --> 01:08:21.730
What are your thoughts on Bluetooth

01:08:21.770 --> 01:08:22.190
security?

01:08:22.230 --> 01:08:22.770
At one point,

01:08:22.791 --> 01:08:24.912
would you decide to not use them and

01:08:24.953 --> 01:08:26.634
switch to cable connected devices,

01:08:26.673 --> 01:08:27.715
which are more secure?

01:08:27.835 --> 01:08:28.354
I assume.

01:08:29.256 --> 01:08:31.037
I think this also comes down to like

01:08:31.337 --> 01:08:32.877
the sort of threats that you're looking

01:08:32.938 --> 01:08:33.338
at, right?

01:08:34.840 --> 01:08:37.201
I wouldn't use a Bluetooth device for

01:08:37.640 --> 01:08:38.561
going on a call,

01:08:38.622 --> 01:08:40.063
talking about something confidential.

01:08:41.243 --> 01:08:41.863
Because again,

01:08:42.083 --> 01:08:43.444
there's like the possibility that someone

01:08:43.465 --> 01:08:45.246
could hack that and like get access to,

01:08:46.167 --> 01:08:47.787
to the content that's being transmitted,

01:08:48.247 --> 01:08:49.488
I think that would be a concern.

01:08:49.948 --> 01:08:50.269
But again,

01:08:50.309 --> 01:08:52.050
if you're just listening to music or a

01:08:52.109 --> 01:08:53.411
podcast or something, it's like,

01:08:54.030 --> 01:08:56.953
is the concern super large?

01:08:57.033 --> 01:08:58.094
I would say not really.

01:08:58.213 --> 01:08:59.854
I think most modern Bluetooth standards

01:08:59.895 --> 01:09:01.655
now, they do use encryption and stuff.

01:09:01.935 --> 01:09:04.636
So the data is not just completely

01:09:04.938 --> 01:09:05.917
accessible to anybody.

01:09:07.719 --> 01:09:10.140
But if you mean by specific like security

01:09:10.180 --> 01:09:10.881
vulnerabilities,

01:09:10.961 --> 01:09:12.261
I think that would be definitely more of

01:09:12.282 --> 01:09:12.862
a concern.

01:09:13.502 --> 01:09:14.063
But again,

01:09:14.483 --> 01:09:16.823
those sort of attacks are relatively rare.

01:09:16.863 --> 01:09:18.444
And I think in a lot of cases,

01:09:18.484 --> 01:09:20.006
just keeping your device updated and

01:09:20.025 --> 01:09:21.306
making sure you're using something that is

01:09:21.386 --> 01:09:24.069
like properly supported is the biggest

01:09:24.109 --> 01:09:26.229
thing rather than, you know,

01:09:27.560 --> 01:09:29.201
trying to be super paranoid about it and

01:09:29.301 --> 01:09:31.081
only using cable connected stuff.

01:09:32.101 --> 01:09:33.682
I think it is definitely a personal

01:09:33.722 --> 01:09:34.443
preference thing.

01:09:34.563 --> 01:09:37.304
Some people just really like wired like

01:09:37.363 --> 01:09:39.045
headphones and that's fine as well.

01:09:39.284 --> 01:09:42.765
So I think you don't have to hack

01:09:42.805 --> 01:09:42.966
me.

01:09:43.246 --> 01:09:45.046
I am always happy to share what music

01:09:45.226 --> 01:09:46.807
I'm listening to or what podcast I'm

01:09:46.847 --> 01:09:47.448
listening to.

01:09:47.547 --> 01:09:49.548
So you don't have to hack me.

01:09:49.588 --> 01:09:51.350
You can just ask.

01:09:52.329 --> 01:09:53.310
I don't believe in having guilty

01:09:53.350 --> 01:09:53.730
pleasures.

01:09:53.791 --> 01:09:55.331
I will openly admit if I'm listening to

01:09:55.390 --> 01:09:56.032
pop music or,

01:09:57.149 --> 01:09:58.230
true crime or whatever.

01:09:58.371 --> 01:09:58.730
I don't care.

01:09:59.771 --> 01:10:00.271
That's fair.

01:10:00.332 --> 01:10:01.853
And also I think the other thing is

01:10:01.912 --> 01:10:03.835
like, uh, it's,

01:10:04.335 --> 01:10:07.176
it's also used for like location tracking.

01:10:07.277 --> 01:10:07.957
I think, you know,

01:10:07.997 --> 01:10:09.557
like you go into stores and like they

01:10:09.578 --> 01:10:11.220
have Bluetooth beacons and all sorts of

01:10:11.239 --> 01:10:11.739
things like that.

01:10:11.819 --> 01:10:13.161
If that's a concern as well,

01:10:13.780 --> 01:10:15.381
I could say like, you know, maybe,

01:10:15.643 --> 01:10:16.203
maybe don't,

01:10:16.302 --> 01:10:18.904
maybe like once you start getting close to

01:10:18.944 --> 01:10:20.586
some shops, maybe turn the Bluetooth off.

01:10:21.770 --> 01:10:23.351
So that actually, yeah, I did.

01:10:23.792 --> 01:10:26.715
I turned off Bluetooth on my pine time.

01:10:26.935 --> 01:10:27.475
So at this point,

01:10:27.515 --> 01:10:29.537
it's honestly just kind of a fancy watch.

01:10:29.697 --> 01:10:30.698
I mean, it wasn't that expensive,

01:10:30.717 --> 01:10:32.019
but you know,

01:10:32.059 --> 01:10:33.319
originally I bought it cause I wanted the

01:10:33.340 --> 01:10:34.900
notifications, but yeah.

01:10:35.020 --> 01:10:36.162
And I guess now that,

01:10:37.162 --> 01:10:38.163
now that I have this like work from

01:10:38.224 --> 01:10:39.564
home job, I try to go,

01:10:40.685 --> 01:10:41.706
I try to run my errands in the

01:10:41.725 --> 01:10:42.867
middle of the day when like,

01:10:42.886 --> 01:10:44.387
there's not as much traffic and hopefully

01:10:44.408 --> 01:10:45.408
everybody else is at work.

01:10:45.949 --> 01:10:47.591
And I noticed that I actually don't use

01:10:47.650 --> 01:10:49.051
headphones as often as I used to.

01:10:49.511 --> 01:10:49.813
I think,

01:10:50.734 --> 01:10:52.134
just because shopping is not as stressful

01:10:52.194 --> 01:10:52.914
as it used to be.

01:10:52.935 --> 01:10:54.574
Uh, so yeah, that's,

01:10:54.635 --> 01:10:55.515
that's kind of the one thing is like,

01:10:55.555 --> 01:10:57.916
I turned the Bluetooth off on this, um,

01:10:57.935 --> 01:10:59.216
for the reason you mentioned with the,

01:10:59.336 --> 01:11:00.136
the beacons.

01:11:00.697 --> 01:11:01.936
And then I have my phone set to

01:11:01.976 --> 01:11:03.516
turn off at like a really quick, like,

01:11:03.537 --> 01:11:04.297
like, like, like, like, like, like, like,

01:11:04.318 --> 01:11:05.037
like, like, like, like, like, like, like,

01:11:05.057 --> 01:11:05.757
like, like, like, seconds or something.

01:11:05.778 --> 01:11:06.457
Um, the Bluetooth.

01:11:06.898 --> 01:11:07.778
So as soon as I get out of

01:11:07.797 --> 01:11:08.118
the car,

01:11:08.158 --> 01:11:09.338
by the time I get to the door,

01:11:09.498 --> 01:11:10.198
it's already off.

01:11:10.238 --> 01:11:13.560
So yeah, that's, that's what I do.

01:11:13.819 --> 01:11:17.060
But yeah, personally, I, uh,

01:11:18.447 --> 01:11:19.007
I'm not great.

01:11:20.007 --> 01:11:24.112
I mean, I have sensory issues.

01:11:24.712 --> 01:11:26.293
I find going outside can be kind of

01:11:26.333 --> 01:11:26.694
loud,

01:11:26.935 --> 01:11:28.775
so I wear headphones basically all the

01:11:28.796 --> 01:11:29.436
time outside.

01:11:31.161 --> 01:11:31.942
It is what it is.

01:11:33.082 --> 01:11:34.264
I'm sure that there's a bunch of stores

01:11:34.283 --> 01:11:35.385
that know that I go there all the

01:11:35.425 --> 01:11:36.905
time because of my Bluetooth beacon.

01:11:36.966 --> 01:11:37.506
But like,

01:11:38.167 --> 01:11:39.887
am I that worried that they know that

01:11:39.948 --> 01:11:40.668
I go there?

01:11:41.489 --> 01:11:43.470
Not particularly like, I don't know.

01:11:43.490 --> 01:11:45.372
It's just like not the biggest threat to

01:11:45.412 --> 01:11:45.853
me, I guess.

01:11:45.893 --> 01:11:48.074
It's not like the huge, a massive concern.

01:11:49.315 --> 01:11:50.356
Could they like, you know,

01:11:50.676 --> 01:11:52.038
if I'm going into a store, there's,

01:11:52.219 --> 01:11:53.220
I'm going to be on camera.

01:11:55.501 --> 01:11:57.162
I'm particularly, you know, I'm not,

01:11:58.956 --> 01:12:00.657
the most normal looking person.

01:12:00.796 --> 01:12:01.796
So, uh, you know, if,

01:12:02.016 --> 01:12:03.297
if someone sees me on camera,

01:12:03.537 --> 01:12:04.478
they're going to know it's me.

01:12:04.717 --> 01:12:05.837
Uh, so like, you know,

01:12:05.898 --> 01:12:08.338
it's not the biggest concern to me again.

01:12:08.658 --> 01:12:08.819
Yeah.

01:12:08.838 --> 01:12:09.779
Like I said, like, you know,

01:12:09.859 --> 01:12:11.399
the tattoos as well, that's, you know,

01:12:11.500 --> 01:12:11.760
things,

01:12:12.461 --> 01:12:14.140
there's identifiers about you that are,

01:12:14.180 --> 01:12:15.561
that are kind of obvious and that make

01:12:15.582 --> 01:12:17.101
you kind of stick out.

01:12:17.141 --> 01:12:18.622
And that, that is like,

01:12:18.643 --> 01:12:19.983
that's a bigger concern, right?

01:12:20.023 --> 01:12:21.764
That would be a more identifying,

01:12:22.264 --> 01:12:23.564
identifying than, you know,

01:12:23.604 --> 01:12:25.005
being scanned by a Bluetooth beacon.

01:12:25.689 --> 01:12:26.789
So, again,

01:12:26.850 --> 01:12:28.350
you've got to kind of take your wins

01:12:28.390 --> 01:12:29.612
where you're going, right?

01:12:30.872 --> 01:12:31.932
I think this sort of thing would be,

01:12:31.953 --> 01:12:33.975
like, more of a concern if it's like,

01:12:34.055 --> 01:12:35.355
oh, you're going to a protest.

01:12:35.655 --> 01:12:37.157
Then I would be like, oh, okay, well,

01:12:37.216 --> 01:12:39.217
maybe you should disable it then, right?

01:12:39.238 --> 01:12:40.298
Because you probably don't want your

01:12:40.319 --> 01:12:42.399
device being scanned then and, you know,

01:12:42.479 --> 01:12:43.661
covering up your body and all that.

01:12:43.740 --> 01:12:44.121
But, like,

01:12:44.521 --> 01:12:46.682
if it's just going to the groceries every

01:12:46.722 --> 01:12:47.384
day, it's like...

01:12:48.104 --> 01:12:48.503
I don't know.

01:12:48.984 --> 01:12:51.225
That's not the biggest threat to me

01:12:51.305 --> 01:12:51.805
exactly.

01:12:52.725 --> 01:12:53.046
But again,

01:12:53.287 --> 01:12:54.627
everyone's threat model is different.

01:12:54.726 --> 01:12:56.528
And if it is a concern that people

01:12:56.568 --> 01:12:57.668
know where you're going,

01:12:57.708 --> 01:13:00.289
then maybe that is something you should be

01:13:01.649 --> 01:13:03.190
using wired devices instead.

01:13:03.270 --> 01:13:04.752
But again, I'm not sure.

01:13:05.935 --> 01:13:06.697
And that's what I was going to say

01:13:06.737 --> 01:13:07.377
too, is, you know, it's,

01:13:07.417 --> 01:13:08.118
what's important to you.

01:13:08.137 --> 01:13:08.578
Like, again,

01:13:08.637 --> 01:13:09.819
now that I'm going shopping in the middle

01:13:09.838 --> 01:13:11.060
of the day where it's not as crowded,

01:13:11.159 --> 01:13:12.341
I don't really need headphones,

01:13:12.782 --> 01:13:14.643
but back at my last job when I

01:13:14.662 --> 01:13:16.003
would have to go like after work or

01:13:16.024 --> 01:13:17.445
on the weekends and it's like super

01:13:17.485 --> 01:13:17.725
crowded.

01:13:17.805 --> 01:13:18.046
And like,

01:13:18.546 --> 01:13:19.827
I don't know what it is with people.

01:13:20.307 --> 01:13:21.269
I feel like I've complained about this

01:13:21.309 --> 01:13:22.229
before is like,

01:13:23.010 --> 01:13:26.091
People become so like low key narcissistic

01:13:26.112 --> 01:13:26.853
in grocery stores.

01:13:27.092 --> 01:13:28.493
Like they just forget that there's other

01:13:28.514 --> 01:13:28.935
people there.

01:13:28.975 --> 01:13:30.416
They'll get into the cereal aisle or any

01:13:30.515 --> 01:13:32.077
aisle and they'll be in the middle of

01:13:32.096 --> 01:13:33.717
the aisle and they'll just stop and stand

01:13:33.738 --> 01:13:34.158
there and be like,

01:13:34.578 --> 01:13:35.739
which cereal do I want?

01:13:35.779 --> 01:13:36.100
And it's like,

01:13:36.140 --> 01:13:37.822
there are six people trying to get past

01:13:37.841 --> 01:13:37.962
you.

01:13:38.421 --> 01:13:40.342
move to one side so people can walk

01:13:40.382 --> 01:13:40.984
past you.

01:13:41.123 --> 01:13:41.844
And like, I don't know.

01:13:41.925 --> 01:13:42.145
It just,

01:13:42.265 --> 01:13:44.006
it would make me so angry that like,

01:13:44.065 --> 01:13:45.186
that's why I would listen,

01:13:45.287 --> 01:13:47.387
like have headphones in is not like a

01:13:47.448 --> 01:13:49.149
sensory thing, but it's like, I'm just,

01:13:49.250 --> 01:13:50.170
I'm going to listen to music.

01:13:50.289 --> 01:13:51.411
I'm going to listen to a podcast.

01:13:51.451 --> 01:13:52.692
I'm going to try not to think about

01:13:52.731 --> 01:13:54.853
how everybody is forgetting that there's a

01:13:55.014 --> 01:13:56.194
hundred and fifty other people in the

01:13:56.213 --> 01:13:58.636
store right now and being completely

01:13:58.655 --> 01:13:59.115
oblivious.

01:13:59.237 --> 01:13:59.396
It's,

01:14:00.056 --> 01:14:01.399
yeah so for me like back then it

01:14:01.418 --> 01:14:03.782
was totally worth it it's like no i'm

01:14:03.801 --> 01:14:05.222
i will lose my mind if i don't

01:14:05.243 --> 01:14:07.826
have a distraction from everyone else but

01:14:07.966 --> 01:14:09.448
now i don't really need that so yes

01:14:09.568 --> 01:14:12.252
it's yeah i don't know i'm with you

01:14:12.271 --> 01:14:14.134
it really depends on what's more important

01:14:14.173 --> 01:14:16.737
not being tracked or not losing your mind

01:14:18.712 --> 01:14:18.891
Yeah,

01:14:18.931 --> 01:14:20.552
it's definitely one of those things to

01:14:20.592 --> 01:14:21.014
consider.

01:14:21.073 --> 01:14:23.095
I guess the other comment we got here

01:14:23.135 --> 01:14:25.197
was from someone on YouTube.

01:14:25.216 --> 01:14:25.577
They said,

01:14:25.636 --> 01:14:27.078
I think Apple forces encryption on

01:14:27.097 --> 01:14:28.719
Bluetooth and have for years.

01:14:29.199 --> 01:14:29.420
Yeah,

01:14:29.500 --> 01:14:30.940
like it is one of these things where,

01:14:30.961 --> 01:14:32.301
you know, modern Bluetooth standards,

01:14:32.322 --> 01:14:33.823
they're all enforcing encryption and

01:14:33.863 --> 01:14:34.063
stuff.

01:14:34.103 --> 01:14:37.505
So the content is most likely going to

01:14:37.545 --> 01:14:38.046
be fine.

01:14:38.086 --> 01:14:39.306
But again, it's like one of those things,

01:14:39.346 --> 01:14:41.007
as soon as you start transmitting things

01:14:41.408 --> 01:14:42.988
like without a wire,

01:14:43.248 --> 01:14:44.770
there's the possibility of it being

01:14:44.831 --> 01:14:46.252
intercepted and, you know...

01:14:47.440 --> 01:14:48.481
That could be a concern.

01:14:48.801 --> 01:14:49.903
It depends, like, you know,

01:14:50.243 --> 01:14:53.425
what the concern is because, again, like,

01:14:55.886 --> 01:14:56.427
what are you doing?

01:14:56.807 --> 01:14:58.168
You're not going to use Wi-Fi then?

01:14:58.349 --> 01:14:58.548
Like,

01:14:58.609 --> 01:14:59.829
you're just going to have everything be,

01:14:59.869 --> 01:15:02.032
like, wired in because of that or, like,

01:15:02.051 --> 01:15:04.493
you know, all sorts of, like,

01:15:04.753 --> 01:15:07.595
wireless transmissions are happening

01:15:07.655 --> 01:15:08.136
everywhere.

01:15:08.235 --> 01:15:11.337
So it's one of those personal decisions,

01:15:11.398 --> 01:15:13.079
I think.

01:15:13.340 --> 01:15:13.579
Agreed.

01:15:15.282 --> 01:15:15.582
All right.

01:15:15.601 --> 01:15:17.984
I think we got one more forum post

01:15:18.003 --> 01:15:19.104
we're going to cover this week.

01:15:19.564 --> 01:15:19.965
Uh,

01:15:19.984 --> 01:15:22.466
this is actually our last story slash

01:15:22.506 --> 01:15:22.827
post.

01:15:22.867 --> 01:15:24.768
So if anybody has been holding onto any

01:15:24.807 --> 01:15:25.269
questions,

01:15:25.309 --> 01:15:26.569
go ahead and drop them in the chat

01:15:26.829 --> 01:15:27.850
and, uh,

01:15:27.890 --> 01:15:29.310
I will let Jordan take this one.

01:15:30.212 --> 01:15:31.273
All right, cool.

01:15:31.813 --> 01:15:31.912
Um,

01:15:31.932 --> 01:15:33.974
so this one is another one from our

01:15:34.054 --> 01:15:36.775
forum that was doing the rounds this week.

01:15:36.836 --> 01:15:38.577
The average person not caring about their

01:15:38.697 --> 01:15:41.319
online privacy is a good thing.

01:15:41.599 --> 01:15:42.359
So, um,

01:15:43.088 --> 01:15:43.708
The person said,

01:15:43.789 --> 01:15:45.130
I know the title sounds crazy,

01:15:45.170 --> 01:15:46.671
but this has been my sentiment as of

01:15:46.712 --> 01:15:47.051
lately.

01:15:47.212 --> 01:15:48.011
Let me elaborate.

01:15:48.512 --> 01:15:50.354
Through my years of casually discussing

01:15:50.394 --> 01:15:51.335
computers, privacy,

01:15:51.435 --> 01:15:53.595
security with people in real life,

01:15:53.676 --> 01:15:55.637
I noticed the total lack of care from

01:15:55.677 --> 01:15:56.557
the average Joe,

01:15:56.898 --> 01:15:59.079
some even working in IT and cybersecurity.

01:15:59.380 --> 01:16:01.220
You point out some very obvious and clear

01:16:01.240 --> 01:16:02.421
invasions of their privacy,

01:16:02.521 --> 01:16:03.143
and you're met with,

01:16:03.283 --> 01:16:04.404
I have nothing to hide.

01:16:04.844 --> 01:16:05.885
What is there to steal?

01:16:05.984 --> 01:16:07.826
My personal data is of no value.

01:16:08.246 --> 01:16:10.307
And just plain old, I don't really care.

01:16:10.908 --> 01:16:12.189
This used to bother me lately,

01:16:12.328 --> 01:16:14.449
but all my cynicism has adopted.

01:16:14.890 --> 01:16:15.690
I have adopted a,

01:16:15.791 --> 01:16:17.231
you don't have to outrun the bear.

01:16:17.551 --> 01:16:18.931
You just have to be more private and

01:16:18.953 --> 01:16:20.913
secure than the average Joe.

01:16:20.993 --> 01:16:23.435
The vast majority of people being careless

01:16:23.454 --> 01:16:25.136
about their privacy is great for people

01:16:25.176 --> 01:16:26.095
who actually care.

01:16:26.537 --> 01:16:30.019
It makes authoritative attacks on privacy

01:16:30.059 --> 01:16:32.739
tools less aggressive and their nets are

01:16:32.800 --> 01:16:33.360
already full.

01:16:34.520 --> 01:16:34.801
Um,

01:16:34.820 --> 01:16:36.682
so that is definitely an interesting

01:16:36.743 --> 01:16:37.703
sentiment, I would say.

01:16:38.104 --> 01:16:39.805
Um, I do think it is,

01:16:39.925 --> 01:16:41.185
there's something to be said about,

01:16:41.265 --> 01:16:43.087
you know,

01:16:43.146 --> 01:16:45.029
not being the lowest common denominator,

01:16:45.328 --> 01:16:48.230
uh, being just slightly better than, uh,

01:16:48.270 --> 01:16:50.172
someone who literally puts zero care in

01:16:50.693 --> 01:16:52.895
goes a long way in terms of security,

01:16:52.954 --> 01:16:53.215
right?

01:16:53.295 --> 01:16:53.515
You know?

01:16:54.005 --> 01:16:55.326
the average person just using the same

01:16:55.365 --> 01:16:56.226
password on everything,

01:16:56.686 --> 01:16:58.287
you've got unique ones on every single

01:16:58.347 --> 01:16:58.408
one.

01:16:58.448 --> 01:17:00.310
That's a significant security improvement

01:17:00.970 --> 01:17:04.533
without much going on, right?

01:17:04.592 --> 01:17:04.712
So...

01:17:06.068 --> 01:17:08.250
Some counterpoints,

01:17:08.390 --> 01:17:10.091
and yet we see many big online platforms

01:17:10.131 --> 01:17:11.653
trying to undermine attempts to use their

01:17:11.693 --> 01:17:12.694
services privately,

01:17:12.894 --> 01:17:14.234
sites that refuse to function if you're

01:17:14.255 --> 01:17:15.775
using a VPN or hardened browser,

01:17:16.176 --> 01:17:17.318
or at least force you to sign in

01:17:17.417 --> 01:17:18.177
if you want to continue.

01:17:18.337 --> 01:17:20.119
The vast majority of people not caring

01:17:20.140 --> 01:17:22.662
about digital privacy also means less

01:17:22.702 --> 01:17:24.764
public support for laws that can protect

01:17:24.783 --> 01:17:27.206
your privacy in areas that personal tech

01:17:27.225 --> 01:17:28.186
solutions can't.

01:17:29.436 --> 01:17:31.057
Everyone else being careless with privacy

01:17:31.158 --> 01:17:32.599
also means that they're less likely to

01:17:32.639 --> 01:17:34.319
protect your privacy when it's in their

01:17:34.359 --> 01:17:34.760
hands.

01:17:34.899 --> 01:17:36.300
They may store something sensitive of

01:17:36.319 --> 01:17:39.242
yours on iCloud with advanced data

01:17:39.282 --> 01:17:41.122
protection turned off or refuse to stop

01:17:41.203 --> 01:17:43.524
using invasive hardware or software that

01:17:43.543 --> 01:17:44.663
will leak information about your

01:17:44.703 --> 01:17:45.324
relationship.

01:17:45.925 --> 01:17:48.185
Low adoption doesn't aid the privacy-aware

01:17:48.305 --> 01:17:48.765
minority.

01:17:49.286 --> 01:17:49.987
On the contrary,

01:17:50.046 --> 01:17:52.448
it makes their signature easy to pick out.

01:17:53.856 --> 01:17:57.122
So I think there's some valid points in

01:17:57.162 --> 01:17:59.163
here that we can pick out.

01:17:59.243 --> 01:18:02.548
I think there's kind of pros and cons

01:18:02.569 --> 01:18:05.533
to each direction of this, right?

01:18:06.134 --> 01:18:08.436
I guess I'll throw it to you, Nate.

01:18:09.158 --> 01:18:09.918
Do you agree with this?

01:18:13.070 --> 01:18:13.931
I mean, no, I don't.

01:18:14.072 --> 01:18:15.792
But to me,

01:18:15.832 --> 01:18:17.752
it's one of those – because it's funny.

01:18:18.113 --> 01:18:19.573
On my website, on my blog,

01:18:19.873 --> 01:18:21.835
I have used that joke about outrunning the

01:18:21.854 --> 01:18:22.774
bear several times.

01:18:23.335 --> 01:18:24.916
And I use it more as like a

01:18:24.975 --> 01:18:28.256
motivational tool for people who are new

01:18:28.277 --> 01:18:32.378
to privacy because privacy has the –

01:18:31.278 --> 01:18:32.760
first of all privacy gets confused with

01:18:32.840 --> 01:18:35.122
anonymity and people keep thinking like oh

01:18:35.582 --> 01:18:37.384
i can like never get on the internet

01:18:37.404 --> 01:18:38.786
again i have to throw away my phone

01:18:38.805 --> 01:18:39.627
i have to go live in a cabin

01:18:39.646 --> 01:18:41.929
in the woods i can't stream anymore i

01:18:41.948 --> 01:18:43.671
have to switch to arch linux and it's

01:18:43.690 --> 01:18:45.893
like privacy is a spectrum like yes if

01:18:45.932 --> 01:18:47.635
you throw your phone away and go live

01:18:47.654 --> 01:18:48.534
in a cabin in the woods you will

01:18:48.555 --> 01:18:50.356
definitely be more private than any of us

01:18:50.396 --> 01:18:52.538
here right now but at the same time

01:18:52.559 --> 01:18:54.461
it's like you know you could just like

01:18:55.502 --> 01:18:57.224
use the Facebook PWA.

01:18:57.264 --> 01:18:58.423
Like we just talked about that earlier.

01:18:58.463 --> 01:19:00.485
You could use that in brave and that's

01:19:00.506 --> 01:19:01.667
going to be a lot more private than

01:19:01.726 --> 01:19:03.908
using the Facebook app and things like

01:19:03.929 --> 01:19:04.168
that.

01:19:04.248 --> 01:19:06.390
And so, um, I, I,

01:19:06.409 --> 01:19:07.730
I do use that line,

01:19:08.671 --> 01:19:09.972
but I don't think it's a good thing.

01:19:10.092 --> 01:19:11.774
I think it's more of a, uh,

01:19:11.814 --> 01:19:12.515
a silver lining.

01:19:13.135 --> 01:19:13.376
Um,

01:19:14.742 --> 01:19:15.622
And yeah, I don't know.

01:19:15.743 --> 01:19:16.944
I kind of agree with all the other

01:19:16.963 --> 01:19:17.203
points.

01:19:17.243 --> 01:19:17.484
It's like,

01:19:17.764 --> 01:19:19.926
we have still seen privacy under attack,

01:19:20.485 --> 01:19:21.987
even though, you know,

01:19:22.747 --> 01:19:24.969
this person said that, you know,

01:19:25.090 --> 01:19:26.930
if it makes attacks on privacy less

01:19:26.951 --> 01:19:28.792
aggressive, I don't know.

01:19:28.832 --> 01:19:30.153
Has anybody been paying attention to chat

01:19:30.172 --> 01:19:33.135
control or the flock cameras that have

01:19:33.154 --> 01:19:34.756
popped up all over the US?

01:19:35.377 --> 01:19:36.757
And that too, like, I think it's,

01:19:38.418 --> 01:19:39.640
I know I've said this many times before,

01:19:39.680 --> 01:19:40.100
but personally,

01:19:40.199 --> 01:19:42.221
I think people do care about privacy.

01:19:42.282 --> 01:19:43.582
It's just one of those things where like,

01:19:45.033 --> 01:19:46.135
I don't know if it's like a learned

01:19:46.175 --> 01:19:47.654
helplessness thing or if people are just

01:19:47.694 --> 01:19:49.515
so overwhelmed with everything else they

01:19:49.555 --> 01:19:50.436
have going on in their lives,

01:19:50.457 --> 01:19:51.497
which I think is totally fair.

01:19:51.537 --> 01:19:53.257
But it's one of those things where like

01:19:53.297 --> 01:19:54.958
people can only care about so many things.

01:19:54.998 --> 01:19:56.679
Like I think all of us would say,

01:19:56.819 --> 01:19:57.920
I care about the environment, right?

01:19:57.960 --> 01:19:58.859
Like every single one of us.

01:19:58.921 --> 01:20:00.280
I don't think there's anyone here who,

01:20:00.440 --> 01:20:00.581
I mean,

01:20:00.600 --> 01:20:01.381
they might say it as a joke in

01:20:01.402 --> 01:20:01.782
the comments,

01:20:01.822 --> 01:20:03.141
but I don't think there's anyone here

01:20:03.182 --> 01:20:04.283
who's genuinely gonna be like, no,

01:20:04.363 --> 01:20:04.903
I hate the planet.

01:20:05.222 --> 01:20:06.764
I want the world to burn and flood

01:20:06.863 --> 01:20:07.384
and all that.

01:20:07.864 --> 01:20:09.966
And yet how many of us have actually

01:20:09.985 --> 01:20:11.886
gone to like a privacy protest or

01:20:11.907 --> 01:20:12.226
something?

01:20:12.947 --> 01:20:14.047
Probably not most of us,

01:20:14.287 --> 01:20:15.389
but that doesn't mean we don't care.

01:20:15.448 --> 01:20:16.048
It's just that like,

01:20:16.069 --> 01:20:18.710
that's not our biggest passion.

01:20:18.729 --> 01:20:19.251
That's not, you know,

01:20:19.270 --> 01:20:21.152
but we would like maybe sign a petition

01:20:21.212 --> 01:20:22.493
or we would like send an email to

01:20:22.533 --> 01:20:23.193
our representatives.

01:20:23.212 --> 01:20:23.453
And like,

01:20:23.813 --> 01:20:25.134
I think everyone's at a different level

01:20:25.194 --> 01:20:25.595
where like,

01:20:25.994 --> 01:20:27.376
just because somebody isn't willing to,

01:20:27.515 --> 01:20:29.856
again, like install cubes on day one,

01:20:30.237 --> 01:20:31.297
doesn't mean they don't care about their

01:20:31.337 --> 01:20:32.538
privacy, but maybe they don't.

01:20:33.198 --> 01:20:34.038
Again, I...

01:20:35.119 --> 01:20:35.739
I'm just gonna mention it.

01:20:36.121 --> 01:20:37.001
A couple of years ago,

01:20:37.121 --> 01:20:38.702
I made a video about PWAs over at

01:20:38.721 --> 01:20:39.282
The New Oil.

01:20:39.761 --> 01:20:41.042
And the reason I made that video is

01:20:41.082 --> 01:20:42.604
because there were literally no videos

01:20:42.623 --> 01:20:42.944
about it.

01:20:43.423 --> 01:20:44.944
Like when I looked up PWAs,

01:20:45.364 --> 01:20:47.466
all I found was technical information for

01:20:47.506 --> 01:20:48.006
developers.

01:20:48.686 --> 01:20:50.667
And it's like, okay, but what about me?

01:20:50.747 --> 01:20:52.188
What about the person who keeps hearing

01:20:52.247 --> 01:20:53.288
online that like, hey,

01:20:53.309 --> 01:20:54.770
if you use a PWA, it's more private.

01:20:55.189 --> 01:20:57.070
I can find like two websites that list

01:20:58.251 --> 01:20:59.631
apps that work as a PWA on your

01:20:59.671 --> 01:20:59.893
phone.

01:21:00.212 --> 01:21:00.712
And that's it.

01:21:00.853 --> 01:21:02.413
I can't find anything explaining what they

01:21:02.475 --> 01:21:03.996
are or how to use them or anything

01:21:04.036 --> 01:21:04.475
like that.

01:21:04.775 --> 01:21:05.756
And that's why I made that video.

01:21:05.796 --> 01:21:07.637
And I think a lot of people just

01:21:07.658 --> 01:21:08.179
fall into that.

01:21:08.559 --> 01:21:08.738
I mean,

01:21:08.859 --> 01:21:10.180
a lot of people don't fall into that

01:21:10.199 --> 01:21:10.761
category of like,

01:21:10.841 --> 01:21:12.301
I'm going to go make the thing, but.

01:21:12.822 --> 01:21:12.981
You know,

01:21:13.042 --> 01:21:13.942
a lot of people like they care,

01:21:13.962 --> 01:21:15.101
but they just don't know where to turn.

01:21:15.141 --> 01:21:17.662
They don't know that using ProtonMail or

01:21:17.703 --> 01:21:20.863
Tudor either or anybody is just like using

01:21:20.923 --> 01:21:21.264
Gmail.

01:21:21.323 --> 01:21:22.463
It's it's super easy.

01:21:22.503 --> 01:21:24.923
They don't know that like a graphene phone

01:21:24.963 --> 01:21:26.765
works almost identically to a regular

01:21:26.864 --> 01:21:27.305
Android.

01:21:27.345 --> 01:21:28.585
They just you know,

01:21:29.284 --> 01:21:30.064
I grew up at a time.

01:21:30.326 --> 01:21:31.305
Sorry, I know I'm ranting.

01:21:31.845 --> 01:21:32.905
I grew up at a time where like

01:21:33.326 --> 01:21:35.487
nobody used Linux unless they were a super

01:21:35.546 --> 01:21:37.386
nerd developer that hated themselves.

01:21:38.083 --> 01:21:39.765
And so I was shocked when I first

01:21:39.784 --> 01:21:40.985
started digging into Linux and I'm like,

01:21:41.765 --> 01:21:42.706
anybody can use this.

01:21:42.786 --> 01:21:43.926
I mean, yeah, at the time,

01:21:43.947 --> 01:21:45.768
maybe not like hardcore content creators

01:21:45.787 --> 01:21:46.247
and gamers,

01:21:46.528 --> 01:21:47.668
but even now it's come so far.

01:21:47.689 --> 01:21:47.948
It's like,

01:21:47.969 --> 01:21:49.470
you can play most games on Linux.

01:21:49.729 --> 01:21:49.909
You know,

01:21:50.010 --> 01:21:52.070
the Linux experiment primarily uses Linux

01:21:52.091 --> 01:21:52.912
to make his videos.

01:21:52.952 --> 01:21:54.872
Like it's come so far now.

01:21:54.912 --> 01:21:56.113
It's like, no, it's not like that anymore.

01:21:56.153 --> 01:21:58.154
It's not super buggy and super awful.

01:21:58.534 --> 01:22:00.274
It's really stable and really polished.

01:22:00.336 --> 01:22:01.975
And just, yeah, I don't know.

01:22:02.055 --> 01:22:02.216
It's...

01:22:03.577 --> 01:22:05.038
I think people do care and I don't

01:22:05.059 --> 01:22:07.140
think it's good that they're not acting on

01:22:07.180 --> 01:22:07.261
it.

01:22:07.341 --> 01:22:07.962
But I mean,

01:22:09.082 --> 01:22:10.083
I'll certainly take advantage of it.

01:22:10.104 --> 01:22:11.005
It's like a political thing.

01:22:11.065 --> 01:22:13.087
Like I may not agree with, you know,

01:22:13.188 --> 01:22:13.387
oh,

01:22:13.427 --> 01:22:14.850
this politician won and now everybody's

01:22:14.869 --> 01:22:16.011
scared they're going to take away guns or

01:22:16.030 --> 01:22:16.310
whatever.

01:22:16.771 --> 01:22:17.332
I don't agree.

01:22:17.391 --> 01:22:18.434
But if I can use that angle to

01:22:18.474 --> 01:22:19.614
get you to care about privacy,

01:22:20.315 --> 01:22:23.118
I'm not above that.

01:22:23.139 --> 01:22:23.279
So.

01:22:23.627 --> 01:22:24.667
Yeah, definitely.

01:22:24.726 --> 01:22:26.787
I think you brought up some good points.

01:22:26.868 --> 01:22:28.689
I think one thing that we've taught,

01:22:28.708 --> 01:22:30.050
we've actually already talked about this

01:22:30.090 --> 01:22:31.750
before, like at Privacy Guides,

01:22:31.770 --> 01:22:33.751
we have an entire section on our website

01:22:34.251 --> 01:22:37.393
that Em wrote about basically how to do

01:22:37.412 --> 01:22:37.592
this,

01:22:37.632 --> 01:22:39.233
how to be like an effective privacy

01:22:39.313 --> 01:22:39.712
advocate,

01:22:39.774 --> 01:22:42.255
how to be like a privacy activist.

01:22:42.354 --> 01:22:44.015
So there's like the Privacy Activist

01:22:44.055 --> 01:22:45.435
Toolbox.

01:22:45.576 --> 01:22:47.896
And it does literally talk about exactly

01:22:47.917 --> 01:22:49.016
what we're talking about right now.

01:22:49.096 --> 01:22:49.697
It says, you know,

01:22:51.899 --> 01:22:54.261
One specific section was expanding your

01:22:54.301 --> 01:22:54.962
perspective.

01:22:55.362 --> 01:22:57.023
Don't stop at individual solutions.

01:22:57.082 --> 01:22:58.545
Consider the collective impact.

01:22:58.944 --> 01:22:59.945
When we think about privacy,

01:22:59.966 --> 01:23:01.787
we often focus on the technical tools that

01:23:01.828 --> 01:23:02.828
we can use to protect it.

01:23:03.168 --> 01:23:04.829
While this is an important component,

01:23:04.890 --> 01:23:06.572
it's crucial not to lose sight of how

01:23:06.631 --> 01:23:08.474
regulations and invasive practices

01:23:08.993 --> 01:23:10.234
impact us collectively.

01:23:10.614 --> 01:23:13.036
So there's some really interesting stuff

01:23:13.256 --> 01:23:17.198
that's part of that specific section of

01:23:17.279 --> 01:23:19.960
that toolbox.

01:23:22.228 --> 01:23:24.029
while it might feel easier to focus on

01:23:24.088 --> 01:23:25.770
our own needs nobody lives in a vacuum

01:23:25.869 --> 01:23:27.951
even if you were able to somehow protect

01:23:28.110 --> 01:23:30.273
all the data you have custody of there

01:23:30.292 --> 01:23:31.912
is a lot of data about you that

01:23:31.972 --> 01:23:33.594
isn't under your control and a lot of

01:23:33.654 --> 01:23:36.855
data about others that impact you so you

01:23:36.876 --> 01:23:39.597
know everyone you interact with is is

01:23:39.618 --> 01:23:41.399
going to be sharing that data um all

01:23:41.418 --> 01:23:43.140
sorts of things like that um

01:23:43.880 --> 01:23:45.740
And there was another specific section

01:23:45.761 --> 01:23:46.902
that I saw that was really good as

01:23:47.042 --> 01:23:47.362
well.

01:23:48.122 --> 01:23:48.983
Be kind to people,

01:23:49.042 --> 01:23:50.644
but relentless with institutions.

01:23:51.125 --> 01:23:51.664
So, you know,

01:23:51.685 --> 01:23:53.166
obviously saying something to someone

01:23:53.206 --> 01:23:56.328
like, oh, you're silly,

01:23:56.347 --> 01:23:57.189
you don't know anything,

01:23:57.288 --> 01:24:00.570
or like you're being silly by using

01:24:00.610 --> 01:24:01.551
Facebook or, you know,

01:24:01.570 --> 01:24:03.613
berating someone for using these not

01:24:03.653 --> 01:24:05.194
private options isn't...

01:24:06.345 --> 01:24:08.305
isn't a good approach, basically.

01:24:08.907 --> 01:24:11.307
Use kindness and patience while working

01:24:11.328 --> 01:24:12.088
with individuals.

01:24:12.128 --> 01:24:13.350
Whenever you talk to individuals,

01:24:13.909 --> 01:24:16.412
make sure to stay calm and

01:24:17.408 --> 01:24:19.170
kind when communicating with them.

01:24:20.430 --> 01:24:24.253
I think aggression or berating somebody

01:24:25.234 --> 01:24:28.157
for their actions is definitely not one

01:24:28.176 --> 01:24:29.778
way to do that.

01:24:29.938 --> 01:24:31.479
But again, it mentions here,

01:24:31.840 --> 01:24:33.201
be relentless with corporations,

01:24:33.261 --> 01:24:35.042
governments and public institutions.

01:24:35.762 --> 01:24:37.884
If there's companies that are abusing your

01:24:37.904 --> 01:24:39.404
data, you can be relentless.

01:24:39.725 --> 01:24:42.967
You don't have to be kind and respectful.

01:24:44.368 --> 01:24:47.292
But, you know, you obviously have to be,

01:24:47.311 --> 01:24:48.493
you know, respect,

01:24:48.512 --> 01:24:50.414
you have to be respectful and polite when

01:24:50.435 --> 01:24:51.296
you're doing that as well.

01:24:51.315 --> 01:24:51.676
Like, you know,

01:24:51.716 --> 01:24:54.760
don't threaten a company or whatever.

01:24:54.800 --> 01:24:56.701
So, yeah, but you can be, you know,

01:24:57.002 --> 01:24:59.845
more direct and not as kind.

01:25:00.484 --> 01:25:04.728
So definitely think about that when you're

01:25:04.768 --> 01:25:05.649
advocating for things.

01:25:06.128 --> 01:25:08.430
It's tricky when it comes to the human

01:25:08.470 --> 01:25:08.871
factor.

01:25:09.030 --> 01:25:10.891
That's always the trickiest because,

01:25:10.912 --> 01:25:11.113
you know,

01:25:11.233 --> 01:25:12.814
we have all these tools and technical

01:25:12.894 --> 01:25:13.814
solutions to things.

01:25:14.314 --> 01:25:15.655
But when it comes down to it,

01:25:15.695 --> 01:25:17.976
like a lot of the privacy issues that

01:25:18.037 --> 01:25:21.140
exist right now are due to, you know,

01:25:21.579 --> 01:25:24.101
specific the way that our society

01:25:24.141 --> 01:25:25.283
functions, for instance.

01:25:25.323 --> 01:25:25.863
Like, you know,

01:25:26.182 --> 01:25:28.545
the advertising industry exists because

01:25:28.664 --> 01:25:29.786
websites need to make money.

01:25:31.826 --> 01:25:33.827
without getting donations or whatever.

01:25:34.487 --> 01:25:36.627
So that is one reason why we have

01:25:36.707 --> 01:25:38.868
such an issue with websites collecting our

01:25:38.889 --> 01:25:39.208
data.

01:25:40.850 --> 01:25:46.511
So just be careful when you're interacting

01:25:46.532 --> 01:25:47.533
with people because I think

01:25:50.030 --> 01:25:52.811
Just caring about yourself and not

01:25:52.872 --> 01:25:55.653
worrying about other people is not really

01:25:55.693 --> 01:25:57.353
an effective solution in the long run,

01:25:58.514 --> 01:25:59.394
is kind of what I was trying to

01:25:59.413 --> 01:25:59.634
say.

01:26:00.213 --> 01:26:02.454
But hopefully I didn't just ramble too

01:26:02.515 --> 01:26:05.115
much there.

01:26:05.155 --> 01:26:06.655
I mean, I probably ramble enough.

01:26:06.695 --> 01:26:08.337
I think it's okay if other people do.

01:26:10.363 --> 01:26:10.444
No,

01:26:10.463 --> 01:26:11.904
I'm glad you mentioned the activism

01:26:11.925 --> 01:26:12.265
toolbox.

01:26:12.284 --> 01:26:14.485
That's privacyguides.org slash activism

01:26:14.786 --> 01:26:15.506
for anyone who didn't know.

01:26:15.527 --> 01:26:17.106
And yeah, Kerry talks about that too.

01:26:17.167 --> 01:26:20.189
Kerry's used that phrase like privacy is a

01:26:20.229 --> 01:26:20.809
team sport.

01:26:20.948 --> 01:26:21.429
He says, you know,

01:26:21.448 --> 01:26:22.550
we all need to care about privacy and

01:26:22.569 --> 01:26:23.930
take simple steps because your data

01:26:24.010 --> 01:26:24.930
overlaps with my data.

01:26:24.970 --> 01:26:26.731
And, you know, that's...

01:26:28.345 --> 01:26:30.006
That's something that somebody said in

01:26:30.345 --> 01:26:31.907
that forum thread is like, yeah,

01:26:32.006 --> 01:26:33.587
if other people don't care about privacy,

01:26:34.148 --> 01:26:34.328
I mean,

01:26:34.349 --> 01:26:35.548
a lot of us have that issue, right?

01:26:35.569 --> 01:26:35.748
You know,

01:26:35.788 --> 01:26:37.189
we go to the doctor's office and it's

01:26:37.229 --> 01:26:37.590
like, oh,

01:26:37.609 --> 01:26:40.011
they're using Zoom for their telehealth

01:26:40.032 --> 01:26:40.271
meetings.

01:26:40.311 --> 01:26:42.092
Now they're using AI to transcribe stuff

01:26:42.113 --> 01:26:43.134
and they don't know.

01:26:43.333 --> 01:26:44.394
And, you know, to their defense,

01:26:44.413 --> 01:26:45.715
they're so busy, they probably don't care.

01:26:45.795 --> 01:26:47.856
But like, you know, you ask the doctor,

01:26:47.877 --> 01:26:48.657
where is that being stored?

01:26:48.676 --> 01:26:49.578
I don't know.

01:26:49.597 --> 01:26:51.538
Go check the privacy policy, which,

01:26:51.599 --> 01:26:52.599
you know, just says LOL.

01:26:52.698 --> 01:26:52.838
So...

01:26:53.920 --> 01:26:55.600
It's a, it is a team sport.

01:26:55.900 --> 01:26:56.841
We do need everyone to care.

01:26:57.360 --> 01:26:58.520
It's like a, it's like her immunity,

01:26:58.820 --> 01:26:59.942
I think is one thing I've compared her

01:26:59.962 --> 01:27:00.462
to in the past.

01:27:02.002 --> 01:27:03.762
And Stan on Twitter says that a Linux

01:27:03.802 --> 01:27:05.082
Mint is so much better than Windows.

01:27:06.042 --> 01:27:06.302
I mean,

01:27:07.444 --> 01:27:08.463
I think it's just really empowering.

01:27:08.503 --> 01:27:09.884
I've told the story before about how years

01:27:09.923 --> 01:27:11.385
ago I got my mom to install Linux

01:27:11.404 --> 01:27:12.085
Mint and she did it.

01:27:13.119 --> 01:27:14.079
pretty much by herself.

01:27:14.659 --> 01:27:15.240
She called me.

01:27:15.280 --> 01:27:16.961
She's like, I found this old laptop.

01:27:16.980 --> 01:27:18.100
I think it was my aunt's laptop.

01:27:18.520 --> 01:27:20.181
And it had Windows Vista or something on

01:27:20.221 --> 01:27:20.301
it.

01:27:20.341 --> 01:27:20.702
And she's like,

01:27:20.801 --> 01:27:22.402
I know enough to know that that's outdated

01:27:22.462 --> 01:27:23.282
and I shouldn't use it.

01:27:23.682 --> 01:27:24.922
And I was like, well, if you're willing,

01:27:25.382 --> 01:27:27.382
here's some instructions to install Linux

01:27:27.422 --> 01:27:27.724
Min.

01:27:28.384 --> 01:27:29.984
And she was able to do it herself

01:27:30.024 --> 01:27:31.203
just from text instructions.

01:27:31.904 --> 01:27:34.244
Privacy is so much easier in some cases

01:27:34.265 --> 01:27:34.904
than people think.

01:27:35.024 --> 01:27:38.006
So yeah, it just feels good.

01:27:40.315 --> 01:27:41.457
I think it's definitely one of those

01:27:41.516 --> 01:27:42.417
situations now.

01:27:42.537 --> 01:27:43.637
I'm not sure if we...

01:27:43.677 --> 01:27:45.739
We didn't talk about this on this week's

01:27:45.779 --> 01:27:46.199
podcast,

01:27:46.239 --> 01:27:48.962
but Microsoft had a massive outage

01:27:49.362 --> 01:27:49.822
recently.

01:27:50.162 --> 01:27:52.404
I think yesterday, most of yesterday.

01:27:53.024 --> 01:27:56.127
And I think people started to realize

01:27:56.266 --> 01:27:58.707
having that reliance on one specific

01:27:58.787 --> 01:28:00.789
company for your operating system,

01:28:01.130 --> 01:28:02.751
your word processing application,

01:28:03.070 --> 01:28:05.632
your communications platform, your,

01:28:05.912 --> 01:28:07.113
I don't know, literally everything.

01:28:07.913 --> 01:28:09.716
So that is one of these situations

01:28:09.775 --> 01:28:09.996
where...

01:28:11.355 --> 01:28:13.356
I'm sure someone running Linux Mint would

01:28:13.377 --> 01:28:16.817
be smiling right now because they're not

01:28:16.856 --> 01:28:18.737
dealing with this massive, massive outage.

01:28:19.677 --> 01:28:20.917
That did happen in the last day.

01:28:20.957 --> 01:28:21.398
But again,

01:28:21.557 --> 01:28:23.518
it wasn't super related to privacy and

01:28:23.557 --> 01:28:23.978
security,

01:28:23.997 --> 01:28:25.779
which is why we didn't bring it up.

01:28:25.878 --> 01:28:28.038
But I guess I could tie it back

01:28:28.059 --> 01:28:28.939
to that a little bit.

01:28:30.559 --> 01:28:32.579
Windows users are not having a good time

01:28:32.819 --> 01:28:33.220
currently.

01:28:34.859 --> 01:28:36.279
Yeah, my sister texted me yesterday.

01:28:36.300 --> 01:28:38.720
She's like, what did she ask?

01:28:38.761 --> 01:28:39.400
Something about like,

01:28:40.523 --> 01:28:42.043
Were you guys affected by the Microsoft

01:28:42.104 --> 01:28:42.363
outage?

01:28:42.384 --> 01:28:44.425
And I was like, no, absolutely not.

01:28:44.484 --> 01:28:45.126
Like, first of all,

01:28:45.466 --> 01:28:46.305
we're kind of big tech.

01:28:46.345 --> 01:28:47.827
We try to keep our dependence on big

01:28:47.867 --> 01:28:49.307
tech services pretty low as it is.

01:28:49.747 --> 01:28:50.387
And secondly,

01:28:50.448 --> 01:28:52.329
like Jonah is just amazingly good at

01:28:52.390 --> 01:28:53.149
sysadmin stuff.

01:28:53.189 --> 01:28:54.350
He's been doing it for years,

01:28:54.411 --> 01:28:57.171
like even before privacy guides.

01:28:57.192 --> 01:29:00.713
And like we self-host probably ninety

01:29:00.753 --> 01:29:02.975
percent of our like next cloud and email

01:29:03.015 --> 01:29:03.996
and everything.

01:29:04.655 --> 01:29:05.716
The only reason I know it's out is

01:29:05.737 --> 01:29:08.658
because I see headlines and I see memes.

01:29:10.359 --> 01:29:12.359
It was a good week for memes.

01:29:12.420 --> 01:29:13.921
Jonah is really on top of it when

01:29:13.961 --> 01:29:15.902
it comes to self-hosting stuff for us.

01:29:16.042 --> 01:29:19.844
A majority of tools that we use on

01:29:19.884 --> 01:29:21.585
the back end is all stuff that he's

01:29:21.625 --> 01:29:23.185
set up and it works really well.

01:29:23.365 --> 01:29:25.065
It is one of those things where it's

01:29:25.105 --> 01:29:30.248
like having that level of control is

01:29:30.288 --> 01:29:30.729
definitely...

01:29:32.966 --> 01:29:34.908
possible because you know if we're doing

01:29:34.967 --> 01:29:38.451
it like hello you know like other people

01:29:38.490 --> 01:29:40.152
could probably do it you know like we're

01:29:40.171 --> 01:29:42.113
not some massive massive organization

01:29:42.213 --> 01:29:44.716
either so again like it is it is

01:29:45.885 --> 01:29:46.985
I think it is a wake-up call.

01:29:47.025 --> 01:29:49.367
And I really genuinely hope that more

01:29:49.667 --> 01:29:50.228
countries,

01:29:50.688 --> 01:29:52.988
because a lot of the times it is

01:29:53.408 --> 01:29:55.010
government services that are using these

01:29:55.050 --> 01:29:56.690
applications, you know,

01:29:57.252 --> 01:29:59.853
a lot of Microsoft in government.

01:30:00.774 --> 01:30:01.833
So again, it's like,

01:30:01.974 --> 01:30:03.395
hopefully it's a wake-up call to them to

01:30:03.414 --> 01:30:04.376
be like, oh,

01:30:04.416 --> 01:30:06.476
maybe we'll host our own NextCloud

01:30:06.537 --> 01:30:08.778
in-house instead, or maybe we'll host,

01:30:09.479 --> 01:30:09.759
you know,

01:30:10.378 --> 01:30:11.699
only office in the house, you know,

01:30:11.760 --> 01:30:12.900
instead to have some sort of

01:30:12.921 --> 01:30:15.122
communications platform, you know,

01:30:15.143 --> 01:30:17.604
they could host like a gypsy or something.

01:30:18.085 --> 01:30:19.506
It would be nice to see people move

01:30:19.546 --> 01:30:21.667
more in that direction away from Microsoft

01:30:21.768 --> 01:30:24.109
and centralizing so much infrastructure,

01:30:24.149 --> 01:30:27.853
especially when it's become such a like

01:30:28.413 --> 01:30:31.055
key operating function of your business.

01:30:31.315 --> 01:30:33.198
A little concerning.

01:30:35.279 --> 01:30:35.439
Yeah.

01:30:35.460 --> 01:30:36.661
Like what did people even do when it

01:30:36.680 --> 01:30:37.081
went down?

01:30:38.990 --> 01:30:39.751
I don't know.

01:30:39.770 --> 01:30:40.751
That was funny because, again,

01:30:41.731 --> 01:30:45.671
at my last job before Privacy Guides,

01:30:46.492 --> 01:30:47.372
I was in the field.

01:30:47.573 --> 01:30:49.393
And so I would see on my RSS

01:30:49.412 --> 01:30:50.033
feed, it's like, oh,

01:30:50.073 --> 01:30:51.132
Microsoft is having an outage.

01:30:51.153 --> 01:30:53.194
And I'm like, well,

01:30:53.253 --> 01:30:54.333
I guess we're not hearing from the project

01:30:54.354 --> 01:30:55.673
managers today.

01:30:55.694 --> 01:30:58.494
Good thing we don't really use computers.

01:30:58.534 --> 01:30:59.274
We know what we're doing.

01:30:59.715 --> 01:31:01.375
So yeah, I don't know.

01:31:01.654 --> 01:31:02.074
It's crazy.

01:31:02.095 --> 01:31:04.296
Anyways.

01:31:04.355 --> 01:31:05.636
That is freaking awesome.

01:31:07.047 --> 01:31:08.171
I think that's all we've got,

01:31:08.231 --> 01:31:09.756
unless there's anything else you wanted to

01:31:09.817 --> 01:31:11.823
add, any last minute thoughts, questions,

01:31:11.863 --> 01:31:12.283
comments?

01:31:13.613 --> 01:31:16.354
I will just quickly check on the forum

01:31:16.416 --> 01:31:17.176
thread that we had.

01:31:17.195 --> 01:31:20.136
We did have one forum thread here.

01:31:20.216 --> 01:31:21.858
I guess just to quickly mention,

01:31:22.257 --> 01:31:23.679
there was someone who did have some, like,

01:31:23.759 --> 01:31:25.500
small questions that I thought we'd get to

01:31:25.520 --> 01:31:27.180
because they did spend the time to write

01:31:27.220 --> 01:31:29.141
up a comment to our thread that we

01:31:29.181 --> 01:31:29.402
made.

01:31:30.822 --> 01:31:33.323
They mentioned specifically two things.

01:31:33.564 --> 01:31:35.784
One was self-hosting against censorship.

01:31:36.185 --> 01:31:38.225
There was a story about autosteasy,

01:31:38.345 --> 01:31:41.467
which they got –

01:31:40.546 --> 01:31:41.046
Basically,

01:31:41.568 --> 01:31:43.128
their entire organization got shut down

01:31:43.168 --> 01:31:44.750
because they got classified as like a

01:31:44.810 --> 01:31:46.490
terrorist organization by the U.S.

01:31:46.511 --> 01:31:46.890
government,

01:31:46.930 --> 01:31:50.832
which ended up meaning that the main

01:31:50.872 --> 01:31:53.054
domain that they had access to got revoked

01:31:53.134 --> 01:31:57.256
because basically the registrar, the no,

01:31:57.296 --> 01:31:57.556
sorry,

01:31:57.796 --> 01:32:00.458
the the top level domain is based in

01:32:00.479 --> 01:32:00.998
the U.S.

01:32:01.038 --> 01:32:01.658
So basically,

01:32:01.699 --> 01:32:04.180
they kind of were forced to withdraw from

01:32:04.600 --> 01:32:07.483
access from from that right um and they

01:32:07.502 --> 01:32:09.323
suggested you know should they have used a

01:32:09.823 --> 01:32:11.503
European domain instead would that have

01:32:11.545 --> 01:32:14.105
protected it and you know using a specific

01:32:14.145 --> 01:32:15.886
country domain or like Italy which is the

01:32:15.926 --> 01:32:18.667
country that Autistica is from would that

01:32:18.688 --> 01:32:20.389
have protected them and I just don't think

01:32:20.429 --> 01:32:22.829
that's the case I think uh in general

01:32:22.869 --> 01:32:24.350
when it when a when a government such

01:32:24.390 --> 01:32:26.952
as the United States basically classifies

01:32:26.971 --> 01:32:28.332
your organization as a terrorist

01:32:28.372 --> 01:32:30.974
organization nobody would wants to touch

01:32:31.014 --> 01:32:31.113
you

01:32:31.354 --> 01:32:33.314
literally no one wants to do business with

01:32:33.335 --> 01:32:34.515
you or interact with you.

01:32:35.715 --> 01:32:37.315
I think you would have the same problem

01:32:37.355 --> 01:32:38.515
if it was in Europe or if it

01:32:38.536 --> 01:32:39.475
was in any country.

01:32:40.756 --> 01:32:41.997
It's just the fact that, you know,

01:32:42.657 --> 01:32:44.597
the United States has quite a big control

01:32:44.698 --> 01:32:47.679
over financial institutions and all sorts

01:32:47.738 --> 01:32:48.298
of things like that.

01:32:48.319 --> 01:32:49.078
That's why, you know,

01:32:49.099 --> 01:32:51.380
sanctions exist and they're so powerful,

01:32:51.420 --> 01:32:51.619
right?

01:32:51.640 --> 01:32:53.300
Because of that.

01:32:53.340 --> 01:32:55.940
So I don't think that would have really

01:32:56.020 --> 01:32:58.381
helped a huge amount in that case

01:32:58.421 --> 01:32:59.042
specifically.

01:33:00.363 --> 01:33:00.863
But again,

01:33:01.144 --> 01:33:02.605
I don't think the average person is going

01:33:02.626 --> 01:33:04.529
to be prescribed as a terrorist

01:33:04.569 --> 01:33:06.051
organization by the US government.

01:33:06.211 --> 01:33:07.873
I was honestly so surprised that it even

01:33:07.913 --> 01:33:08.333
happened.

01:33:08.574 --> 01:33:10.436
So I feel like they're pretty,

01:33:10.698 --> 01:33:12.439
pretty niche and somewhat irrelevant,

01:33:12.460 --> 01:33:14.882
in my opinion, in the grand scheme of,

01:33:15.024 --> 01:33:16.145
you know, internet service.

01:33:17.065 --> 01:33:20.328
providers that do like email and stuff but

01:33:20.347 --> 01:33:22.769
there was another one here that was about

01:33:23.229 --> 01:33:24.328
you didn't get to talk about this because

01:33:24.349 --> 01:33:26.470
you wasn't you weren't on that week but

01:33:26.689 --> 01:33:27.810
I guess I'll throw it to you did

01:33:27.850 --> 01:33:29.832
you have any thoughts on the airplane like

01:33:30.431 --> 01:33:32.493
a Doppler curve think question that they

01:33:32.512 --> 01:33:32.672
had

01:33:34.132 --> 01:33:34.533
Yeah,

01:33:35.814 --> 01:33:37.237
I did put this in the show notes

01:33:37.256 --> 01:33:38.217
last week, but yeah,

01:33:38.337 --> 01:33:39.840
I was busy working on other stuff,

01:33:39.859 --> 01:33:41.261
so I don't know if you guys covered

01:33:41.282 --> 01:33:41.662
it or not.

01:33:41.722 --> 01:33:42.963
But yeah,

01:33:43.083 --> 01:33:44.565
the same person was commenting on that

01:33:44.605 --> 01:33:45.266
story and said,

01:33:45.506 --> 01:33:46.769
I wonder if I would have any airplane

01:33:46.788 --> 01:33:47.729
sounds inside.

01:33:48.390 --> 01:33:49.993
And from what I understand,

01:33:50.012 --> 01:33:51.033
because that was kind of my first thought

01:33:51.054 --> 01:33:52.155
too, and...

01:33:53.832 --> 01:33:54.954
I did a little bit of research,

01:33:55.695 --> 01:33:56.837
which is not super robust.

01:33:56.957 --> 01:33:58.238
I wouldn't stake your life on it.

01:33:58.939 --> 01:33:59.981
But from what I understand,

01:34:00.061 --> 01:34:01.103
if you're inside,

01:34:01.283 --> 01:34:02.465
unless you have the windows open,

01:34:02.925 --> 01:34:04.146
it's probably not...

01:34:06.394 --> 01:34:08.634
probably not going to be to get through

01:34:08.734 --> 01:34:09.135
like the,

01:34:09.175 --> 01:34:10.734
the installation of your building.

01:34:11.454 --> 01:34:11.814
Um,

01:34:11.854 --> 01:34:14.154
certainly not in a usable form that would

01:34:14.194 --> 01:34:16.456
be useful to this, uh, this attack.

01:34:17.036 --> 01:34:17.615
And, uh,

01:34:17.636 --> 01:34:18.996
of course me being an audio guy,

01:34:19.036 --> 01:34:19.917
my first thought is like,

01:34:20.337 --> 01:34:21.377
what about a high pass filter?

01:34:21.417 --> 01:34:23.136
Because it said that it used, um, like,

01:34:23.256 --> 01:34:25.278
like low frequency sounds that were too

01:34:25.318 --> 01:34:26.257
low for humans to hear.

01:34:26.898 --> 01:34:27.938
And, uh, personally,

01:34:28.618 --> 01:34:30.018
I like to put a high pass on

01:34:30.118 --> 01:34:30.939
everybody's voice.

01:34:31.259 --> 01:34:32.279
Um, because I just find that

01:34:32.859 --> 01:34:34.079
in the podcast I listen to,

01:34:34.140 --> 01:34:36.161
the people who don't treat voices at all,

01:34:36.541 --> 01:34:37.881
I find I get ear fatigue a lot

01:34:37.902 --> 01:34:38.302
faster.

01:34:38.762 --> 01:34:40.283
But if they even just basic,

01:34:40.323 --> 01:34:41.625
like especially a podcast like this one

01:34:41.645 --> 01:34:42.305
where we're just talking,

01:34:42.324 --> 01:34:43.086
there's not a lot of music,

01:34:43.105 --> 01:34:44.126
there's not a lot of sound effects.

01:34:45.567 --> 01:34:47.268
If you can roll off a lot of

01:34:47.287 --> 01:34:47.788
that low end,

01:34:47.828 --> 01:34:49.329
which shouldn't really be there anyways,

01:34:49.750 --> 01:34:51.670
you can listen for longer before your ears

01:34:51.689 --> 01:34:52.211
get tired.

01:34:52.951 --> 01:34:54.150
Um, so yeah,

01:34:54.211 --> 01:34:55.850
apparently a high pass filter would also

01:34:55.890 --> 01:34:57.311
work because as the name suggests,

01:34:57.652 --> 01:34:59.712
it allows all the high frequencies to pass

01:35:00.032 --> 01:35:01.652
and cuts off everything below the filter,

01:35:01.952 --> 01:35:04.372
um, which would include things that it's,

01:35:04.453 --> 01:35:05.212
it's one of those things that's,

01:35:05.273 --> 01:35:06.012
it's more of an advanced,

01:35:06.752 --> 01:35:08.134
advanced audio thing where like,

01:35:08.753 --> 01:35:10.453
even if you don't consciously hear it,

01:35:10.573 --> 01:35:12.293
it like builds up and adds noise.

01:35:12.515 --> 01:35:13.774
So yeah.

01:35:14.034 --> 01:35:14.135
Um,

01:35:15.413 --> 01:35:16.414
If you're a content creator,

01:35:16.876 --> 01:35:18.817
use high-pass filters, which, again,

01:35:19.016 --> 01:35:22.439
you shouldn't... If it's just you talking,

01:35:22.541 --> 01:35:23.881
unless you're like Benedict Cumberbatch or

01:35:23.902 --> 01:35:26.844
somebody with a disturbingly deep voice,

01:35:27.104 --> 01:35:28.386
it shouldn't really matter anyways.

01:35:28.445 --> 01:35:29.766
And if you're recording a band,

01:35:30.327 --> 01:35:31.488
you don't need that on the vocals.

01:35:31.507 --> 01:35:32.529
You might need it on the kick drum.

01:35:32.548 --> 01:35:34.070
And again, if you're doing YouTube,

01:35:34.110 --> 01:35:35.271
you add the music in the background,

01:35:35.311 --> 01:35:37.012
that's probably not recorded in the same

01:35:37.052 --> 01:35:37.234
place.

01:35:37.274 --> 01:35:37.974
I don't know.

01:35:39.375 --> 01:35:39.796
Yeah.

01:35:41.537 --> 01:35:41.917
It seems...

01:35:44.063 --> 01:35:45.546
relatively easy.

01:35:45.567 --> 01:35:46.469
I don't know if I want to say

01:35:46.569 --> 01:35:46.809
easy.

01:35:47.891 --> 01:35:49.775
It seems like there are some probably

01:35:49.855 --> 01:35:51.399
pretty effective defenses for anyone who's

01:35:51.439 --> 01:35:51.980
worried about that.

01:35:52.362 --> 01:35:54.206
So that's what I'll say.

01:35:55.487 --> 01:35:55.947
Yeah.

01:35:56.006 --> 01:35:56.926
And I think it is one of those

01:35:56.966 --> 01:35:57.967
scenarios where it's like,

01:35:58.507 --> 01:36:00.127
if the CIA wants to find you,

01:36:00.307 --> 01:36:01.207
they're going to find you.

01:36:02.408 --> 01:36:03.929
Like, I'm sure that there's,

01:36:04.009 --> 01:36:05.788
that's one specific method, right?

01:36:05.809 --> 01:36:07.488
But I keep seeing more and more,

01:36:07.569 --> 01:36:09.510
like that person just kept putting out

01:36:09.550 --> 01:36:11.310
more and more videos, like, oh, I,

01:36:11.350 --> 01:36:13.109
how I identified someone based on the

01:36:13.170 --> 01:36:14.951
lightning strike sounds in the footage.

01:36:14.970 --> 01:36:17.570
And it's just like, it's like, okay, like,

01:36:17.631 --> 01:36:17.951
you know,

01:36:18.451 --> 01:36:19.572
it's getting a little ridiculous,

01:36:19.612 --> 01:36:20.891
but it's like, okay, like,

01:36:22.341 --> 01:36:23.662
that is one of these things where,

01:36:23.702 --> 01:36:24.662
you know,

01:36:24.702 --> 01:36:26.462
there's always evolving techniques to

01:36:26.542 --> 01:36:28.224
extract more information from things.

01:36:28.363 --> 01:36:28.823
And it's like,

01:36:28.963 --> 01:36:30.984
as long as we're staying like somewhat on

01:36:31.024 --> 01:36:32.626
top of things, um,

01:36:33.894 --> 01:36:35.534
I feel like for the average person,

01:36:35.574 --> 01:36:36.335
it's not a concern.

01:36:36.354 --> 01:36:36.734
But again,

01:36:36.755 --> 01:36:38.296
like if someone really wants to find you

01:36:38.315 --> 01:36:41.115
and you post an image or some audio

01:36:41.195 --> 01:36:41.936
or something like that,

01:36:41.957 --> 01:36:43.957
I'm sure there's ridiculous ways that they

01:36:43.976 --> 01:36:46.818
can use to get access to your location.

01:36:48.399 --> 01:36:50.760
But again, like unless someone's super,

01:36:51.100 --> 01:36:53.119
super wants to find out where you live,

01:36:53.180 --> 01:36:56.561
then probably not a great concern, right?

01:36:57.942 --> 01:36:58.402
Yeah,

01:36:58.442 --> 01:36:59.802
that's kind of how I feel is like

01:36:59.842 --> 01:37:00.103
there's,

01:37:01.606 --> 01:37:02.327
it just, to me,

01:37:02.447 --> 01:37:03.667
it feels like if you play the what

01:37:03.707 --> 01:37:05.528
if game forever, you,

01:37:05.547 --> 01:37:06.689
you would just become paralyzed.

01:37:06.748 --> 01:37:08.750
Like, you know, we,

01:37:08.869 --> 01:37:09.810
we live in a world, like you said,

01:37:09.829 --> 01:37:11.390
we're like any video,

01:37:11.530 --> 01:37:12.711
they can pick out the freaking,

01:37:13.390 --> 01:37:14.271
the sidewalk stripe,

01:37:14.311 --> 01:37:15.891
the cross crosswalk stripes.

01:37:16.011 --> 01:37:16.972
As you're driving by,

01:37:17.012 --> 01:37:18.233
they can pick out the skyline.

01:37:18.613 --> 01:37:19.393
Now we have, you know,

01:37:19.412 --> 01:37:20.953
they can pick you out through the wifi

01:37:20.993 --> 01:37:21.974
signals through walls.

01:37:21.993 --> 01:37:23.435
And it's just like, if,

01:37:25.242 --> 01:37:27.384
If we just try to defend against

01:37:27.505 --> 01:37:28.886
everything, I mean,

01:37:28.905 --> 01:37:29.606
that's threat modeling, right?

01:37:29.627 --> 01:37:30.547
That's on the EFF's page.

01:37:31.128 --> 01:37:32.590
Trying to defend against everything all

01:37:32.630 --> 01:37:34.693
the time is impossible and exhausting.

01:37:35.273 --> 01:37:36.715
And so it's like, pick the big things.

01:37:36.755 --> 01:37:37.336
Like, okay,

01:37:37.876 --> 01:37:40.578
don't post a picture of the skyline in

01:37:40.618 --> 01:37:42.400
a unique city where somebody could easily

01:37:42.461 --> 01:37:43.762
triangulate where you are.

01:37:44.804 --> 01:37:45.465
You know, don't...

01:37:47.572 --> 01:37:49.351
things like that like don't post a selfie

01:37:49.391 --> 01:37:50.712
where your mail is visible in the

01:37:50.752 --> 01:37:52.653
background with your address on it or your

01:37:53.113 --> 01:37:55.212
work shirt where people can tell where you

01:37:55.252 --> 01:37:57.873
work you know I don't know it's trying

01:37:57.894 --> 01:37:59.033
to take care of the things that you

01:37:59.073 --> 01:38:00.654
can actually do something about and that

01:38:00.673 --> 01:38:02.295
are most likely to be abused I think

01:38:02.675 --> 01:38:04.055
so at least that's what I try to

01:38:04.074 --> 01:38:06.354
focus on otherwise I will just spiral into

01:38:06.375 --> 01:38:08.895
paranoia and anxiety and get nothing done

01:38:09.155 --> 01:38:13.317
so I will say there's also the alternative

01:38:13.356 --> 01:38:15.356
which is don't share it in the first

01:38:15.396 --> 01:38:15.697
place

01:38:16.515 --> 01:38:18.356
You don't need to share everything that

01:38:18.377 --> 01:38:19.537
you do with everybody.

01:38:20.177 --> 01:38:22.220
It is one of those things where less

01:38:22.260 --> 01:38:23.461
is more, I guess.

01:38:23.480 --> 01:38:24.881
Just don't share as much stuff.

01:38:24.942 --> 01:38:26.762
Don't share so many things on the

01:38:26.802 --> 01:38:27.162
internet.

01:38:28.484 --> 01:38:29.645
Then you don't have to worry about, oh,

01:38:29.704 --> 01:38:31.365
is this audio file that I shared going

01:38:31.386 --> 01:38:33.226
to have the information in there?

01:38:33.247 --> 01:38:34.488
Don't share any audio files.

01:38:34.707 --> 01:38:36.349
Don't share any photos unless you really

01:38:36.368 --> 01:38:36.649
need to.

01:38:36.729 --> 01:38:38.189
And if it's with someone that you trust,

01:38:38.871 --> 01:38:40.591
again, be careful.

01:38:40.692 --> 01:38:42.153
I think posting things publicly,

01:38:42.734 --> 01:38:44.935
you do start having those issues where

01:38:44.994 --> 01:38:46.376
people will be super creepy.

01:38:47.996 --> 01:38:49.176
FirewallstoneStopDragon said,

01:38:49.216 --> 01:38:51.356
with AI and all ground level maps,

01:38:51.436 --> 01:38:53.078
locating someone based on the background

01:38:53.118 --> 01:38:54.497
in the image is going to be scary

01:38:54.537 --> 01:38:54.757
good.

01:38:55.198 --> 01:38:56.158
Automated OSINT.

01:38:56.998 --> 01:38:57.238
Yeah,

01:38:57.578 --> 01:39:00.100
I think that sort of stuff does exist

01:39:00.159 --> 01:39:01.260
already at this point, right?

01:39:01.279 --> 01:39:01.801
Like, you know,

01:39:02.341 --> 01:39:04.801
identifying people based on really weird

01:39:04.822 --> 01:39:05.622
stuff like, oh,

01:39:06.341 --> 01:39:07.801
the picture you took in your hotel room,

01:39:07.881 --> 01:39:09.743
I worked out exactly which hotel you're

01:39:09.762 --> 01:39:11.583
staying at and which exact room that

01:39:11.604 --> 01:39:12.963
you're staying at because of the photos

01:39:12.984 --> 01:39:15.164
that I found of the rooms on the

01:39:15.185 --> 01:39:15.564
internet.

01:39:15.604 --> 01:39:15.864
And then I

01:39:16.744 --> 01:39:18.845
located that to where you're staying.

01:39:19.926 --> 01:39:22.108
There's creepy stuff that AI can do,

01:39:22.167 --> 01:39:24.949
and it automates a lot of the busy

01:39:24.989 --> 01:39:26.449
work that these attacks require,

01:39:26.470 --> 01:39:33.154
which I think is definitely super scary.

01:39:33.453 --> 01:39:37.355
Yeah, for sure.

01:39:37.435 --> 01:39:38.417
I like what you said about don't put

01:39:38.457 --> 01:39:40.377
it out there in the first place.

01:39:40.478 --> 01:39:41.198
Leave some mystery.

01:39:42.139 --> 01:39:43.960
It's okay to not exist a hundred percent

01:39:44.000 --> 01:39:44.260
online.

01:39:45.488 --> 01:39:46.430
Have some mystery in the world.

01:39:46.609 --> 01:39:49.193
The world needs more mystery.

01:39:49.213 --> 01:39:49.634
Definitely.

01:39:50.595 --> 01:39:53.658
I'm not seeing too many questions here

01:39:54.038 --> 01:39:54.899
that we could cover.

01:39:55.881 --> 01:39:57.342
So I guess we can kind of start

01:39:57.363 --> 01:39:58.864
heading out to the outro now,

01:39:58.904 --> 01:40:00.226
unless you had anything you wanted to add.

01:40:01.969 --> 01:40:02.630
I think I'm good.

01:40:03.996 --> 01:40:04.577
Alrighty then.

01:40:04.676 --> 01:40:07.458
So all the updates from this week in

01:40:07.519 --> 01:40:09.159
privacy will be shared on the blog every

01:40:09.180 --> 01:40:09.421
week.

01:40:09.480 --> 01:40:11.101
So sign up with the newsletter or

01:40:11.141 --> 01:40:13.003
subscribe with your favorite RSS reader.

01:40:13.404 --> 01:40:14.484
If you want to stay tuned,

01:40:14.864 --> 01:40:17.488
we also offer a podcast which is available

01:40:17.568 --> 01:40:18.828
on all podcast platforms.

01:40:19.328 --> 01:40:20.010
and RSS,

01:40:20.050 --> 01:40:21.970
which now includes video on supportive

01:40:21.990 --> 01:40:22.511
platforms.

01:40:22.952 --> 01:40:24.894
And this video will also be synced to

01:40:25.054 --> 01:40:25.654
PeerTube.

01:40:26.014 --> 01:40:28.155
Privacy Guides is an impartial nonprofit

01:40:28.235 --> 01:40:30.177
organization that is focused on building a

01:40:30.257 --> 01:40:32.739
strong privacy advocacy community and

01:40:32.760 --> 01:40:35.061
delivering the best digital privacy and

01:40:35.101 --> 01:40:37.444
consumer technology rights advice on the

01:40:37.503 --> 01:40:37.923
internet.

01:40:38.184 --> 01:40:39.524
If you want to support our mission,

01:40:39.585 --> 01:40:40.945
then you can make a donation on our

01:40:40.985 --> 01:40:44.208
website at privacyguides.org slash donate.

01:40:44.668 --> 01:40:46.369
You can make a donation on any page

01:40:46.529 --> 01:40:49.011
on the website by clicking the red heart

01:40:49.171 --> 01:40:51.652
icon located in the top right corner of

01:40:51.692 --> 01:40:52.212
the page.

01:40:52.573 --> 01:40:54.393
You can contribute using standard fiat

01:40:54.412 --> 01:40:57.074
currency via debit or credit card or opt

01:40:57.135 --> 01:41:00.716
to donate anonymously using Monero or with

01:41:00.735 --> 01:41:02.216
your favorite cryptocurrency.

01:41:02.617 --> 01:41:04.497
Becoming a paid member unlocks exclusive

01:41:04.537 --> 01:41:07.078
perks like early access to video content,

01:41:07.458 --> 01:41:08.680
exclusive video content,

01:41:09.100 --> 01:41:11.541
and priority during the This Week in

01:41:11.581 --> 01:41:13.362
Privacy livestream Q&A.

01:41:13.641 --> 01:41:15.283
You'll also get a cool badge on your

01:41:15.302 --> 01:41:18.064
profile in the Privacy Guides forum and

01:41:18.085 --> 01:41:18.625
the warm,

01:41:18.685 --> 01:41:21.386
fuzzy feeling of supporting independent

01:41:21.426 --> 01:41:21.786
media.

01:41:22.207 --> 01:41:23.006
Thanks for watching,

01:41:23.186 --> 01:41:24.908
and we'll see you next week.