WEBVTT

00:00:03.664 --> 00:00:06.147
Reddit further erodes anonymous usage,

00:00:06.469 --> 00:00:08.813
cops can now bypass the iPhone's automatic

00:00:08.913 --> 00:00:09.214
reboot,

00:00:09.374 --> 00:00:11.276
and a new attack that can track you

00:00:11.336 --> 00:00:13.080
across all operating systems.

00:00:13.400 --> 00:00:14.663
All of this and more coming up on

00:00:14.723 --> 00:00:16.646
This Week in Privacy number seventy-three,

00:00:16.707 --> 00:00:17.448
so stay tuned.

00:00:40.777 --> 00:00:42.478
Welcome back to This Week in Privacy,

00:00:42.618 --> 00:00:44.317
our weekly series where we discuss the

00:00:44.357 --> 00:00:45.898
latest updates with what we're working on

00:00:45.917 --> 00:00:47.558
within the Privacy Guides community and

00:00:47.579 --> 00:00:49.679
this week's top stories in data privacy

00:00:49.799 --> 00:00:51.960
and cybersecurity while answering viewer

00:00:52.000 --> 00:00:52.619
questions.

00:00:53.179 --> 00:00:53.621
I'm Nate,

00:00:53.801 --> 00:00:55.640
and joining me this week is Jonah.

00:00:55.901 --> 00:00:56.420
Howdy, Jonah.

00:00:56.441 --> 00:00:57.021
It's been a minute.

00:00:57.841 --> 00:00:59.402
Yeah, it's good to be back.

00:00:59.442 --> 00:01:01.743
And I've been having a good week with

00:01:01.783 --> 00:01:03.162
the video stuff that's been going on.

00:01:04.224 --> 00:01:05.804
That's been going well for you.

00:01:05.884 --> 00:01:07.384
So I hope we could talk about that

00:01:07.424 --> 00:01:07.724
later.

00:01:08.424 --> 00:01:09.165
But how have you been doing?

00:01:10.680 --> 00:01:11.141
Pretty good.

00:01:11.180 --> 00:01:11.421
Yeah.

00:01:11.460 --> 00:01:13.405
Just, uh, busy with the videos.

00:01:13.685 --> 00:01:14.667
Um, like you said,

00:01:14.686 --> 00:01:15.629
we'll talk about that later,

00:01:15.668 --> 00:01:17.251
but we put out a couple of videos

00:01:17.272 --> 00:01:18.394
in the last couple of weeks and we

00:01:18.414 --> 00:01:20.957
got more on the way and, um, yeah,

00:01:20.998 --> 00:01:22.159
so I mean, good week for sure,

00:01:22.200 --> 00:01:24.123
but definitely keeping super busy.

00:01:25.394 --> 00:01:25.653
Sweet.

00:01:26.153 --> 00:01:26.754
All right.

00:01:26.774 --> 00:01:28.674
Yeah, I think with that,

00:01:28.694 --> 00:01:30.655
we'll go ahead and jump into the latest,

00:01:30.814 --> 00:01:32.316
biggest news from privacy and security in

00:01:32.335 --> 00:01:32.915
the past week.

00:01:33.516 --> 00:01:34.915
As a reminder to any viewers,

00:01:34.956 --> 00:01:36.216
if you have any thoughts or questions

00:01:36.257 --> 00:01:38.236
while we're going over the story,

00:01:38.777 --> 00:01:39.796
feel free to leave it in the chat

00:01:39.917 --> 00:01:41.278
and we will address them at the end

00:01:41.317 --> 00:01:41.837
of the story.

00:01:41.897 --> 00:01:43.018
So first up,

00:01:43.138 --> 00:01:45.379
we're going to talk about Reddit.

00:01:45.978 --> 00:01:46.638
And this headline,

00:01:46.659 --> 00:01:48.078
this comes from Ars Technica,

00:01:48.099 --> 00:01:49.558
says Reddit is putting more limits on

00:01:49.700 --> 00:01:51.359
old.reddit.com.

00:01:52.060 --> 00:01:53.561
So back in July,

00:01:53.641 --> 00:01:55.402
some of you may remember that Reddit

00:01:55.441 --> 00:01:57.581
started requiring that users be logged in

00:01:57.623 --> 00:01:58.843
to access old Reddit,

00:01:59.263 --> 00:02:01.343
which real quick for anyone who doesn't

00:02:01.384 --> 00:02:03.245
know for now,

00:02:03.325 --> 00:02:04.284
we'll see how long this lasts.

00:02:04.665 --> 00:02:07.486
You can literally go to old.reddit.com and

00:02:07.527 --> 00:02:08.926
it's the old version of Reddit.

00:02:09.247 --> 00:02:10.487
It definitely looks kind of dated these

00:02:10.508 --> 00:02:12.968
days, but it's also a lot lighter.

00:02:13.109 --> 00:02:14.430
I think there's like less JavaScript.

00:02:14.490 --> 00:02:16.270
I think there might even be less trackers,

00:02:16.290 --> 00:02:17.170
but don't quote me on that.

00:02:17.550 --> 00:02:18.752
But most notably,

00:02:19.312 --> 00:02:20.834
It's usually also a lot less strict about

00:02:20.894 --> 00:02:21.814
requiring you to sign in.

00:02:21.955 --> 00:02:22.855
Some of you may know that if you

00:02:22.895 --> 00:02:24.236
try to go to Reddit right now and

00:02:24.276 --> 00:02:25.057
you're not signed in,

00:02:25.117 --> 00:02:26.699
and especially if you're using a VPN,

00:02:27.159 --> 00:02:28.801
it's probably going to block you and force

00:02:28.822 --> 00:02:29.383
you to sign in.

00:02:29.842 --> 00:02:30.883
Old Reddit didn't do that.

00:02:31.185 --> 00:02:33.026
So a lot of privacy people preferred old

00:02:33.067 --> 00:02:35.229
Reddit because, again, it was lighter,

00:02:35.628 --> 00:02:37.330
it was a little bit less of a

00:02:37.390 --> 00:02:39.393
nightmare, and no sign-in required.

00:02:39.954 --> 00:02:40.373
But now...

00:02:41.014 --> 00:02:42.616
uh the article says today but this is

00:02:42.656 --> 00:02:44.237
you know a few days old it says

00:02:44.277 --> 00:02:45.579
that the social media platform announced

00:02:45.639 --> 00:02:47.240
additional upcoming restrictions on old

00:02:47.280 --> 00:02:49.241
reddit a reddit post from an employee said

00:02:49.282 --> 00:02:50.663
that in the next few months will further

00:02:50.703 --> 00:02:52.364
limit access for logged in users to only

00:02:52.383 --> 00:02:53.585
those who have used old reddit in the

00:02:53.604 --> 00:02:55.347
last six months which covers the majority

00:02:55.387 --> 00:02:56.848
of all old reddit users so if you

00:02:56.867 --> 00:02:58.109
want to be grandfathered in now is your

00:02:58.149 --> 00:03:00.390
time to uh go log in they said

00:03:00.411 --> 00:03:01.731
there will be an exception for moderators

00:03:01.752 --> 00:03:03.092
who are still able to view old reddit

00:03:03.133 --> 00:03:05.054
regardless of when they last log uh last

00:03:05.153 --> 00:03:06.215
used it as long as they are logged

00:03:06.294 --> 00:03:06.375
in

00:03:07.415 --> 00:03:09.396
And they claim that this is basically to

00:03:09.437 --> 00:03:11.478
help reduce scraping and automated abuse.

00:03:13.959 --> 00:03:14.338
Yeah.

00:03:15.459 --> 00:03:16.800
The article says that there's concerns

00:03:16.819 --> 00:03:18.419
that they may completely shut down old

00:03:18.460 --> 00:03:19.520
Reddit one day, which...

00:03:20.965 --> 00:03:25.006
Yeah, well, let me see here.

00:03:25.026 --> 00:03:25.445
Yeah, I mean,

00:03:25.765 --> 00:03:26.546
I guess we're at that part of the

00:03:26.567 --> 00:03:26.806
article.

00:03:26.866 --> 00:03:28.227
It does say down here that in twenty

00:03:28.247 --> 00:03:28.747
twenty five,

00:03:28.806 --> 00:03:30.168
Huffman said the old Reddit would remain

00:03:30.207 --> 00:03:31.388
online as long as people are using it.

00:03:31.687 --> 00:03:32.989
But in August, he changed his tune,

00:03:33.008 --> 00:03:34.348
saying in a post that the reality is

00:03:34.368 --> 00:03:35.329
we're getting to a time where we need

00:03:35.348 --> 00:03:36.030
to make some changes.

00:03:36.050 --> 00:03:37.409
And those changes would probably include

00:03:37.449 --> 00:03:38.189
limiting access,

00:03:38.229 --> 00:03:40.450
migrating important uses and rebuilding

00:03:40.531 --> 00:03:41.850
old Reddit on a modern tech stack.

00:03:42.170 --> 00:03:44.391
So I guess technically it doesn't sound

00:03:44.412 --> 00:03:45.252
like it's going anywhere,

00:03:45.292 --> 00:03:48.212
but it may not survive in a noticeable

00:03:48.252 --> 00:03:48.573
form.

00:03:49.294 --> 00:03:49.554
And then.

00:03:50.954 --> 00:03:51.933
This is the one that really pissed me

00:03:51.993 --> 00:03:52.093
off.

00:03:52.114 --> 00:03:53.034
They kind of threw this in here at

00:03:53.055 --> 00:03:53.375
the end.

00:03:53.435 --> 00:03:54.875
But Reddit is also going to stop

00:03:54.914 --> 00:03:56.616
supporting RSS feeds on November,

00:03:57.855 --> 00:03:59.597
because RSS is now a common surface for

00:03:59.637 --> 00:04:01.676
large-scale scraping and automated abuse.

00:04:02.076 --> 00:04:03.497
It will still be available for moderators

00:04:03.518 --> 00:04:05.098
who use it for workflows through supported

00:04:05.157 --> 00:04:06.018
alternatives,

00:04:07.079 --> 00:04:08.239
which I think they said there's an app

00:04:08.258 --> 00:04:10.539
called Discord Relay and some other stuff.

00:04:11.939 --> 00:04:14.861
Yeah, that's super, super nifty.

00:04:15.282 --> 00:04:16.642
I think that's kind of it as far

00:04:16.682 --> 00:04:20.043
as stories go or as far as details.

00:04:21.384 --> 00:04:21.625
Jonah,

00:04:21.644 --> 00:04:22.925
I think I'll turn it over to you.

00:04:23.065 --> 00:04:24.906
I know like you, for example, you say,

00:04:25.247 --> 00:04:25.906
if I remember correctly,

00:04:25.927 --> 00:04:27.307
you're not a super big Reddit user.

00:04:27.827 --> 00:04:28.629
And I personally,

00:04:28.728 --> 00:04:30.810
I kind of go through phases.

00:04:30.870 --> 00:04:31.370
Like right now,

00:04:31.389 --> 00:04:32.711
I've actually been on Reddit quite a bit,

00:04:32.790 --> 00:04:34.372
but I'm probably going to stop using it

00:04:34.391 --> 00:04:35.192
a little bit for a while.

00:04:35.612 --> 00:04:37.814
So why does this matter for people like

00:04:37.853 --> 00:04:39.074
you and soon to be me who may

00:04:39.113 --> 00:04:40.254
not be heavy Reddit users?

00:04:40.535 --> 00:04:41.016
Well, you know what?

00:04:41.136 --> 00:04:42.877
I think I'm kind of in the same

00:04:42.918 --> 00:04:44.418
boat where I use it kind of off

00:04:44.519 --> 00:04:44.939
and on.

00:04:45.560 --> 00:04:47.523
The reality is I've experienced this a lot

00:04:47.562 --> 00:04:49.084
lately where a lot of just niche

00:04:49.163 --> 00:04:50.826
information is still only available on

00:04:50.865 --> 00:04:51.127
Reddit.

00:04:51.187 --> 00:04:53.889
It's just been such a prolific form for

00:04:53.930 --> 00:04:55.550
such a long time that

00:04:56.572 --> 00:04:58.014
A lot of discussions are still taking

00:04:58.033 --> 00:04:58.553
place there,

00:04:58.613 --> 00:05:01.196
and especially if you can find older

00:05:01.235 --> 00:05:03.516
discussions about things like from two

00:05:03.557 --> 00:05:04.598
years ago or something,

00:05:04.838 --> 00:05:07.579
instead of all of the AI slop that

00:05:07.620 --> 00:05:09.982
is now kind of permeated the search

00:05:10.041 --> 00:05:10.482
results.

00:05:10.862 --> 00:05:12.663
I think that those Reddit results tend to

00:05:12.702 --> 00:05:14.625
still be a bit better,

00:05:16.004 --> 00:05:17.185
which is it's a shame that it's all

00:05:17.225 --> 00:05:18.906
locked down into that one ecosystem.

00:05:18.947 --> 00:05:19.807
But that is, of course,

00:05:21.757 --> 00:05:24.500
the main business strategy of Reddit and

00:05:24.519 --> 00:05:25.920
why they can make changes like this

00:05:25.959 --> 00:05:28.341
because people are kind of stuck using it,

00:05:28.482 --> 00:05:28.762
you know?

00:05:30.562 --> 00:05:31.142
Yeah, for sure.

00:05:31.562 --> 00:05:33.244
The RSS thing really pissed me off because

00:05:33.264 --> 00:05:34.285
to me that is just such a

00:05:36.108 --> 00:05:36.730
it feels like, um,

00:05:36.750 --> 00:05:38.170
what's the word I'm looking for?

00:05:38.190 --> 00:05:38.930
Uh, like,

00:05:39.031 --> 00:05:40.333
like a canary in a coal mine of

00:05:40.372 --> 00:05:42.553
like the direction that the web is headed

00:05:42.613 --> 00:05:44.036
in where the web used to be this

00:05:44.096 --> 00:05:44.255
open.

00:05:44.495 --> 00:05:46.197
And it's funny cause like, I remember, um,

00:05:46.617 --> 00:05:47.017
I'll be honest,

00:05:47.057 --> 00:05:47.879
I don't know how old you are.

00:05:47.899 --> 00:05:48.959
So you may or may not remember this,

00:05:49.420 --> 00:05:50.961
but when I was about in high school,

00:05:51.000 --> 00:05:53.322
so about like the mid two thousands, um,

00:05:54.283 --> 00:05:56.845
RSS really popped off in the mainstream.

00:05:56.904 --> 00:05:58.266
And it seemed like every single website

00:05:58.286 --> 00:05:59.846
you went to had RSS.

00:06:00.187 --> 00:06:01.187
And I didn't even know what it was.

00:06:01.567 --> 00:06:02.468
It's almost like apps.

00:06:02.507 --> 00:06:03.848
When apps popped off in every single

00:06:03.869 --> 00:06:05.149
website, it was like, download our app.

00:06:05.189 --> 00:06:06.850
And so every website I went to was

00:06:06.870 --> 00:06:08.091
like, we have an RSS feed.

00:06:08.391 --> 00:06:09.672
And now what's funny is a lot of

00:06:09.692 --> 00:06:10.952
them still support RSS,

00:06:10.973 --> 00:06:12.473
but they just don't broadcast it that same

00:06:12.492 --> 00:06:12.913
way anymore.

00:06:13.353 --> 00:06:14.894
So I don't know where I'm going with

00:06:14.915 --> 00:06:15.355
this.

00:06:15.654 --> 00:06:16.896
With them saying we're not going to do

00:06:17.016 --> 00:06:18.416
RSS anymore, to me, it's just such a...

00:06:19.536 --> 00:06:22.880
like it feels like they're just really um

00:06:22.920 --> 00:06:24.461
like the whole web is turning into this

00:06:24.521 --> 00:06:26.043
walled garden you know like twitter

00:06:26.064 --> 00:06:28.605
requires logins now uh facebook and

00:06:28.625 --> 00:06:30.387
instagram have required it for a long time

00:06:30.848 --> 00:06:32.891
now reddit's doing it it's really sad to

00:06:32.930 --> 00:06:34.252
see the internet getting increasingly

00:06:34.372 --> 00:06:37.636
siloed and closed off like this and super

00:06:37.716 --> 00:06:39.137
turning against what the web was supposed

00:06:39.177 --> 00:06:40.819
to be especially considering who was

00:06:40.838 --> 00:06:42.480
involved in the founding of reddit but

00:06:42.540 --> 00:06:42.721
yeah

00:06:43.300 --> 00:06:45.661
Yeah, social media definitely, I think,

00:06:45.701 --> 00:06:47.622
played a big part in people moving away

00:06:47.642 --> 00:06:50.624
from like personal websites and blogs and

00:06:50.663 --> 00:06:51.365
that sort of thing.

00:06:51.425 --> 00:06:51.865
It's funny,

00:06:51.964 --> 00:06:56.427
I was just watching a video about it

00:06:56.447 --> 00:06:58.048
was from I don't know when it was,

00:06:58.088 --> 00:06:59.088
two thousand one or something.

00:06:59.108 --> 00:07:00.689
It was a video of Steve Jobs kind

00:07:00.750 --> 00:07:02.651
of announcing the first Apple store that

00:07:02.670 --> 00:07:04.252
they opened and they were selling software

00:07:04.291 --> 00:07:06.213
like create your own personal website.

00:07:06.252 --> 00:07:07.012
Like at the time,

00:07:07.033 --> 00:07:08.553
that was just the thing you would do

00:07:08.733 --> 00:07:09.175
online.

00:07:09.475 --> 00:07:10.435
And now that's kind of been

00:07:11.735 --> 00:07:13.497
uh you know centralized onto all of these

00:07:13.516 --> 00:07:15.216
platforms because people don't want to

00:07:15.237 --> 00:07:16.338
people don't want to do that but that's

00:07:16.377 --> 00:07:18.718
at the risk of um you know these

00:07:18.738 --> 00:07:20.798
platforms being able to do whatever they

00:07:20.838 --> 00:07:23.339
want with your content at at any time

00:07:23.939 --> 00:07:26.980
um and obviously i think reddit is really

00:07:27.040 --> 00:07:29.221
no different than a lot of other social

00:07:29.262 --> 00:07:30.583
media platforms in the sense that they

00:07:30.622 --> 00:07:30.762
have

00:07:32.028 --> 00:07:33.348
just awful data practices.

00:07:33.387 --> 00:07:35.428
They're doing all of this crazy stuff with

00:07:35.889 --> 00:07:37.569
like tracking you across the site.

00:07:37.829 --> 00:07:39.689
It's obviously an advertising supported

00:07:39.709 --> 00:07:40.350
platform,

00:07:40.451 --> 00:07:42.130
and then they're also using that content

00:07:42.170 --> 00:07:44.271
on the back end to sell it to

00:07:44.451 --> 00:07:46.752
AI companies for for training and stuff

00:07:46.773 --> 00:07:47.132
like that.

00:07:47.153 --> 00:07:47.333
So

00:07:49.286 --> 00:07:49.545
Yeah,

00:07:49.766 --> 00:07:52.288
that's kind of just not a fantastic

00:07:52.307 --> 00:07:53.548
situation that they've created.

00:07:53.649 --> 00:07:57.471
And this is just kind of another anti-user

00:07:57.851 --> 00:07:58.512
approach to things.

00:07:58.533 --> 00:08:00.033
It's unfortunate that everything just kind

00:08:00.074 --> 00:08:02.735
of needs an account these days just to

00:08:02.836 --> 00:08:03.237
access.

00:08:03.276 --> 00:08:05.317
But we've talked about that with Twitter

00:08:05.497 --> 00:08:07.600
or X switching to that as well.

00:08:07.660 --> 00:08:08.800
Reddit is kind of no different.

00:08:08.860 --> 00:08:10.322
And yeah,

00:08:10.562 --> 00:08:11.723
I'm sure this is going to upset

00:08:13.286 --> 00:08:14.865
some contingent of Reddit users.

00:08:14.906 --> 00:08:16.906
But I think Reddit in general has just

00:08:16.966 --> 00:08:20.028
been going downhill for some time.

00:08:20.187 --> 00:08:22.247
And I don't know if old Reddit really

00:08:22.307 --> 00:08:23.769
saves people from a lot of the stuff

00:08:23.788 --> 00:08:25.889
that they're doing.

00:08:25.908 --> 00:08:26.149
Fair.

00:08:26.348 --> 00:08:27.689
Yeah, I'm glad you mentioned the AI thing.

00:08:27.730 --> 00:08:29.670
That was something I wanted to make sure

00:08:29.709 --> 00:08:30.149
we mentioned.

00:08:30.310 --> 00:08:31.271
Reddit struck a deal with,

00:08:31.331 --> 00:08:32.331
I think it's OpenAI,

00:08:32.350 --> 00:08:34.532
and now they sell user data to OpenAI

00:08:34.552 --> 00:08:35.611
to help train the models.

00:08:35.652 --> 00:08:35.731
And

00:08:36.467 --> 00:08:37.448
Yeah, real quick,

00:08:37.528 --> 00:08:38.610
I do remember those days.

00:08:38.650 --> 00:08:39.572
Like you were saying back then,

00:08:39.591 --> 00:08:41.274
there were things like GeoCities that were

00:08:41.313 --> 00:08:42.195
real plug and play.

00:08:42.215 --> 00:08:42.934
And like you said,

00:08:42.975 --> 00:08:43.735
everybody had a website.

00:08:43.796 --> 00:08:45.477
I think MySpace was probably the first

00:08:45.498 --> 00:08:46.860
time that really took off because they had

00:08:46.899 --> 00:08:48.621
that ability to inject CSS code and

00:08:48.662 --> 00:08:49.702
customize your page.

00:08:49.743 --> 00:08:51.105
But even before that,

00:08:51.926 --> 00:08:53.187
it was pretty common to run into people

00:08:53.226 --> 00:08:55.509
who had a random, you know,

00:08:55.549 --> 00:08:56.331
for whatever reason.

00:08:56.390 --> 00:08:56.530
So...

00:08:57.471 --> 00:08:58.091
Yeah.

00:08:58.111 --> 00:08:58.932
I also just want to point out,

00:08:59.253 --> 00:09:00.134
I know you kind of touched on this

00:09:00.153 --> 00:09:01.494
at the beginning, but unfortunately,

00:09:01.514 --> 00:09:03.595
there are still some privacy projects who

00:09:03.975 --> 00:09:06.356
only or primarily use Reddit or sometimes

00:09:06.397 --> 00:09:06.856
Discord.

00:09:07.157 --> 00:09:07.697
Proton.

00:09:09.057 --> 00:09:10.719
That's exactly who I'm thinking of.

00:09:10.739 --> 00:09:11.600
They're not the only ones,

00:09:11.620 --> 00:09:12.720
but they're probably the most prominent

00:09:12.801 --> 00:09:12.860
one.

00:09:12.921 --> 00:09:13.600
Yeah.

00:09:13.721 --> 00:09:15.022
So even when we step back from the

00:09:15.042 --> 00:09:16.842
privacy stuff, we think like, oh, well,

00:09:16.923 --> 00:09:17.883
you know, we don't need Reddit.

00:09:17.923 --> 00:09:18.443
Like, you're right.

00:09:19.203 --> 00:09:20.404
We need them to get the memo, though.

00:09:21.586 --> 00:09:22.467
It's really frustrating.

00:09:22.528 --> 00:09:24.009
So I think that'll bring me to,

00:09:24.409 --> 00:09:24.590
you know,

00:09:24.610 --> 00:09:25.692
is there anything that we can do about

00:09:25.731 --> 00:09:25.792
it?

00:09:25.812 --> 00:09:27.173
Are there any alternative platforms?

00:09:27.212 --> 00:09:28.335
Or do you think it would help to...

00:09:28.875 --> 00:09:30.177
Is there any kind of protest or anything?

00:09:30.517 --> 00:09:31.258
In some cases,

00:09:31.317 --> 00:09:32.678
like the one you just mentioned with

00:09:32.720 --> 00:09:34.301
Proton and these other companies who are

00:09:34.400 --> 00:09:35.903
using Reddit as, like, their main...

00:09:37.842 --> 00:09:40.926
news announcement form for whatever

00:09:40.966 --> 00:09:41.225
reason.

00:09:41.285 --> 00:09:42.267
I think it's kind of unfortunate.

00:09:42.307 --> 00:09:44.269
Getting them to switch would be great.

00:09:44.349 --> 00:09:47.412
But there are alternative ways to access

00:09:47.572 --> 00:09:47.912
Reddit.

00:09:48.231 --> 00:09:50.374
FoundDoug in the chat mentioned RedLib as

00:09:50.394 --> 00:09:52.655
a good self-hosted frontend for Reddit.

00:09:52.696 --> 00:09:54.498
We do recommend these frontends for

00:09:54.798 --> 00:09:57.921
accessing a lot of social media sites on

00:09:57.980 --> 00:09:59.261
a read-only basis.

00:09:59.341 --> 00:10:00.023
I don't know if there's...

00:10:00.644 --> 00:10:01.283
I haven't looked into...

00:10:02.304 --> 00:10:03.466
red lips specifically too much.

00:10:03.486 --> 00:10:04.990
I don't know if there's public instances,

00:10:05.110 --> 00:10:08.174
but stuff like that that can kind of

00:10:08.375 --> 00:10:08.996
abstract

00:10:10.071 --> 00:10:11.991
the content of the site away from like

00:10:12.672 --> 00:10:14.232
Reddit running a bunch of JavaScript in

00:10:14.253 --> 00:10:15.692
your browser and tracking you,

00:10:15.753 --> 00:10:17.533
I think is generally a good thing to

00:10:17.573 --> 00:10:20.054
do if you're just trying to access Reddit.

00:10:20.235 --> 00:10:23.495
But I would certainly just I mean,

00:10:24.576 --> 00:10:26.057
because this is what we do and I've

00:10:26.076 --> 00:10:27.977
been a big proponent of, you know,

00:10:28.278 --> 00:10:29.738
websites and organizations kind of

00:10:29.798 --> 00:10:31.538
starting their own forms,

00:10:32.178 --> 00:10:33.620
running their own blogs and comment

00:10:33.639 --> 00:10:34.860
sections and kind of having their own

00:10:34.879 --> 00:10:36.321
communities separate from

00:10:37.400 --> 00:10:38.642
these major platforms,

00:10:38.682 --> 00:10:40.363
because if you do everything on your own

00:10:40.842 --> 00:10:42.264
domain name and you kind of do it

00:10:42.283 --> 00:10:42.664
yourself,

00:10:42.684 --> 00:10:45.005
that as a as an organization or a

00:10:45.066 --> 00:10:46.346
business that provides you with a lot of

00:10:46.407 --> 00:10:47.748
safety because you're not just at the

00:10:47.788 --> 00:10:50.730
whims of however the business that you're

00:10:51.049 --> 00:10:53.270
trying to use operates.

00:10:53.552 --> 00:10:54.511
And I think that a lot of people

00:10:54.552 --> 00:10:57.854
don't realize that because from a short

00:10:57.894 --> 00:10:58.615
term perspective,

00:11:00.697 --> 00:11:01.859
you know, having all of this,

00:11:02.239 --> 00:11:03.802
all of these tech resources available for

00:11:03.822 --> 00:11:05.104
free and very easy to set up,

00:11:05.163 --> 00:11:07.447
it's obviously appealing.

00:11:08.048 --> 00:11:09.971
But at the same time,

00:11:11.559 --> 00:11:12.941
Um, it's just,

00:11:13.741 --> 00:11:16.443
it's just a way for you to basically

00:11:16.484 --> 00:11:17.985
send all of your users or all of

00:11:18.004 --> 00:11:20.386
your customers to these other platforms

00:11:20.407 --> 00:11:23.549
who will eventually lock you away from,

00:11:23.769 --> 00:11:24.610
from those users,

00:11:24.630 --> 00:11:25.971
from your own users and customers.

00:11:26.011 --> 00:11:28.514
We've seen it on like Facebook,

00:11:28.553 --> 00:11:29.234
for example,

00:11:29.274 --> 00:11:30.835
where everyone was like encouraged to make

00:11:30.894 --> 00:11:31.635
Facebook pages.

00:11:31.696 --> 00:11:33.177
And then all of a sudden,

00:11:33.197 --> 00:11:34.697
now that everyone's on Facebook.

00:11:34.798 --> 00:11:34.918
Now,

00:11:34.958 --> 00:11:36.659
if you want to communicate with people on

00:11:36.700 --> 00:11:37.880
Facebook effectively as a,

00:11:38.041 --> 00:11:39.004
As a business, for example,

00:11:39.024 --> 00:11:40.488
now you have to pay Facebook a bunch

00:11:40.508 --> 00:11:43.557
of money for advertising, right?

00:11:43.857 --> 00:11:45.442
That's the main goal of really

00:11:47.609 --> 00:11:49.549
locking people in to these platforms,

00:11:49.610 --> 00:11:50.071
I suppose.

00:11:50.230 --> 00:11:52.952
So certainly there's some Fediverse

00:11:53.113 --> 00:11:53.793
alternatives.

00:11:54.274 --> 00:11:56.794
I'm not super familiar with a lot of

00:11:56.835 --> 00:11:57.034
them.

00:11:57.095 --> 00:11:58.216
I haven't used them recently,

00:11:58.255 --> 00:11:59.616
but Lemmy's around and I know some

00:11:59.636 --> 00:12:00.518
communities use that.

00:12:00.618 --> 00:12:02.859
I'm a big proponent of Discourse,

00:12:02.899 --> 00:12:03.899
the form software.

00:12:04.320 --> 00:12:04.740
Thankfully,

00:12:04.760 --> 00:12:07.942
I've seen a lot of open source

00:12:07.962 --> 00:12:08.423
communities,

00:12:08.462 --> 00:12:10.124
especially like Linux distros,

00:12:10.183 --> 00:12:12.905
kind of adopt Discourse as the de facto

00:12:13.105 --> 00:12:15.628
form software of choice for a lot of

00:12:15.648 --> 00:12:16.567
these and for good reason.

00:12:16.587 --> 00:12:17.188
I think it's a good.

00:12:18.129 --> 00:12:20.110
setup for organizations and businesses.

00:12:20.150 --> 00:12:20.490
And of course,

00:12:20.530 --> 00:12:22.532
we use that for our form,

00:12:22.812 --> 00:12:24.494
discuss that privacy guides.net.

00:12:25.313 --> 00:12:26.774
So stuff like that, setting that up,

00:12:27.836 --> 00:12:29.236
having going back to like a more

00:12:29.277 --> 00:12:30.076
decentralized web,

00:12:30.116 --> 00:12:32.798
I think benefits a lot of people,

00:12:32.818 --> 00:12:34.399
I think it certainly benefits users.

00:12:35.100 --> 00:12:36.662
But it also has a lot of benefits

00:12:36.701 --> 00:12:39.264
for businesses to kind of get away from

00:12:39.323 --> 00:12:43.225
these from the social media sites that are

00:12:43.285 --> 00:12:45.288
shifting to more predatory practices,

00:12:45.327 --> 00:12:45.567
I think.

00:12:47.371 --> 00:12:47.951
Yeah, for sure.

00:12:48.052 --> 00:12:49.893
I think, um, with like, uh,

00:12:50.153 --> 00:12:50.793
like discourse,

00:12:50.812 --> 00:12:53.793
that's probably not ideal for like a

00:12:53.913 --> 00:12:55.154
Reddit replacement per se,

00:12:55.174 --> 00:12:56.315
like from a user perspective.

00:12:56.335 --> 00:12:56.575
But yeah,

00:12:56.615 --> 00:12:57.955
especially when we think of like bigger

00:12:57.995 --> 00:12:59.956
projects, like, uh, like Linux distros,

00:12:59.995 --> 00:13:02.397
proton Tudor and like places to get help

00:13:02.417 --> 00:13:03.136
and tech support.

00:13:03.216 --> 00:13:03.616
Like, yeah.

00:13:03.677 --> 00:13:04.357
Discourse is,

00:13:04.957 --> 00:13:05.837
I think really good for that.

00:13:05.857 --> 00:13:07.057
And I think, um,

00:13:07.099 --> 00:13:08.099
I think we'll talk about this probably

00:13:08.139 --> 00:13:09.019
more in the site updates,

00:13:09.058 --> 00:13:11.220
but I left a comment last night on,

00:13:11.460 --> 00:13:11.600
uh,

00:13:11.620 --> 00:13:13.760
our latest video on the forum where the

00:13:13.801 --> 00:13:14.360
comments, uh,

00:13:15.562 --> 00:13:16.102
it felt, uh,

00:13:16.663 --> 00:13:18.144
cause for those who don't know,

00:13:18.224 --> 00:13:19.724
our last couple of videos have gone fairly

00:13:19.764 --> 00:13:20.144
viral.

00:13:20.163 --> 00:13:20.344
They've,

00:13:20.364 --> 00:13:21.823
they've gotten a pretty good reach and

00:13:21.844 --> 00:13:23.105
they've also been very polarizing.

00:13:23.705 --> 00:13:24.705
And so I commented on the forum.

00:13:24.725 --> 00:13:25.284
I'm like, man,

00:13:25.325 --> 00:13:28.166
it's really nice to see like sane takes

00:13:28.285 --> 00:13:29.385
and like people that even though they

00:13:29.426 --> 00:13:30.225
might disagree with us,

00:13:30.245 --> 00:13:31.647
they're not like calling me names or

00:13:31.667 --> 00:13:32.027
anything.

00:13:32.466 --> 00:13:33.726
And it's just, it's so refreshing.

00:13:33.807 --> 00:13:34.847
And people kind of pointed out, it's like,

00:13:35.168 --> 00:13:35.307
yeah,

00:13:35.327 --> 00:13:36.467
this is kind of like the way the

00:13:36.488 --> 00:13:37.788
web should be like the future of the

00:13:37.807 --> 00:13:37.967
web,

00:13:38.087 --> 00:13:39.828
these smaller communities where people can

00:13:40.369 --> 00:13:41.389
get along a little easier.

00:13:41.428 --> 00:13:41.948
So it's,

00:13:41.969 --> 00:13:42.928
I almost wonder if it would be good

00:13:42.948 --> 00:13:44.029
for the internet to be a little bit

00:13:44.070 --> 00:13:45.090
more, uh,

00:13:45.629 --> 00:13:46.610
I don't want to say fragmented,

00:13:46.650 --> 00:13:48.111
like decentralized like that.

00:13:48.491 --> 00:13:50.673
So yeah, I don't know.

00:13:51.793 --> 00:13:53.075
I think I'll turn that one over to

00:13:53.195 --> 00:13:53.695
a viewer.

00:13:53.735 --> 00:13:53.894
Yeah.

00:13:53.975 --> 00:13:54.615
Oh, one more thing.

00:13:54.635 --> 00:13:54.755
Yeah.

00:13:54.775 --> 00:13:56.155
I found dog said Libra or red lib

00:13:56.176 --> 00:13:57.697
was previously called Libra.

00:13:58.197 --> 00:13:58.658
I definitely,

00:13:58.837 --> 00:14:00.038
I don't know if you mentioned this cause

00:14:00.058 --> 00:14:01.219
I'm trying to troubleshoot something over

00:14:01.259 --> 00:14:01.419
here,

00:14:01.460 --> 00:14:07.163
but I do wonder if they're almost like

00:14:07.182 --> 00:14:07.962
a, what was it called?

00:14:08.003 --> 00:14:09.264
The knitter, like knitter.

00:14:09.384 --> 00:14:10.565
I do wonder how long these things are

00:14:10.585 --> 00:14:11.885
going to be able to function when Reddit

00:14:11.926 --> 00:14:13.427
is increasingly cracking down on this

00:14:13.447 --> 00:14:13.746
stuff and

00:14:14.946 --> 00:14:15.868
if they're going to get a cease and

00:14:15.888 --> 00:14:16.229
desist.

00:14:16.249 --> 00:14:16.929
But in the meantime,

00:14:17.009 --> 00:14:18.874
I am all for that kind of stuff.

00:14:18.913 --> 00:14:20.638
So yeah,

00:14:20.658 --> 00:14:21.720
I think we'll turn it over to viewers.

00:14:21.799 --> 00:14:22.741
If you guys use Reddit,

00:14:22.782 --> 00:14:23.423
what are you going to do?

00:14:23.464 --> 00:14:24.645
What are your recommendations?

00:14:24.666 --> 00:14:25.889
Do you have something to add?

00:14:26.772 --> 00:14:28.232
Those frontends are definitely a

00:14:28.293 --> 00:14:29.214
short-term solution.

00:14:29.274 --> 00:14:30.455
I mean, in the long term,

00:14:30.475 --> 00:14:32.336
we just got to switch away from platforms

00:14:32.355 --> 00:14:32.777
like this.

00:14:33.256 --> 00:14:36.519
I know we have an announcement post on

00:14:36.559 --> 00:14:37.980
our forum for this live stream,

00:14:38.301 --> 00:14:39.162
like we do every week.

00:14:39.182 --> 00:14:41.283
We've gotten some comments on the forum

00:14:41.302 --> 00:14:42.443
from people who have talked about this

00:14:42.504 --> 00:14:43.184
Reddit story.

00:14:44.645 --> 00:14:48.948
There's mixed opinions, for sure, on it.

00:14:48.989 --> 00:14:49.528
Somebody said...

00:14:51.638 --> 00:14:53.759
that that sites that archive like deleted

00:14:53.798 --> 00:14:55.318
comments on Reddit and stuff might lose

00:14:55.379 --> 00:14:56.339
access because of this.

00:14:56.418 --> 00:14:58.320
And that might be a privacy win.

00:14:58.740 --> 00:15:03.201
I think that that's a little the I

00:15:03.221 --> 00:15:03.321
mean,

00:15:03.341 --> 00:15:05.321
there is certainly an argument to be made

00:15:06.442 --> 00:15:07.081
a lot of the time.

00:15:07.101 --> 00:15:09.022
So I think when you put out content

00:15:09.042 --> 00:15:09.623
publicly,

00:15:10.102 --> 00:15:11.322
I think people in general need to be

00:15:11.363 --> 00:15:12.763
more mindful of content that's put out

00:15:12.802 --> 00:15:14.124
publicly because a lot of the time it

00:15:14.144 --> 00:15:15.964
does just exist kind of forever.

00:15:16.384 --> 00:15:18.225
And so if you're really worried about

00:15:18.264 --> 00:15:18.445
that,

00:15:20.080 --> 00:15:21.279
There might not be much you can do,

00:15:21.980 --> 00:15:24.100
but yeah,

00:15:24.120 --> 00:15:26.081
I thought that was an interesting

00:15:26.121 --> 00:15:26.501
argument.

00:15:28.163 --> 00:15:28.503
Yeah.

00:15:30.263 --> 00:15:31.203
I had a thought on that one,

00:15:31.224 --> 00:15:32.423
but I don't remember what it was now.

00:15:34.465 --> 00:15:34.884
This one,

00:15:35.024 --> 00:15:35.985
I think we touched on this one a

00:15:36.004 --> 00:15:36.845
little bit, but somebody,

00:15:36.985 --> 00:15:37.926
a new user asked,

00:15:38.066 --> 00:15:39.806
do you think the anonymous internet access

00:15:39.826 --> 00:15:41.647
is becoming impossible and what can users

00:15:41.726 --> 00:15:43.167
realistically do to preserve it?

00:15:43.187 --> 00:15:46.048
Do you want to weigh in on that

00:15:46.128 --> 00:15:47.028
one or want me to start?

00:15:47.149 --> 00:15:48.509
Because I do have some thoughts on that.

00:15:49.522 --> 00:15:51.222
I don't think it's becoming impossible in

00:15:51.243 --> 00:15:53.023
a lot of areas.

00:15:53.062 --> 00:15:55.423
I think age verification is certainly

00:15:56.903 --> 00:15:58.325
causing problems in that regard,

00:15:58.345 --> 00:16:00.245
and we may start to see it becoming

00:16:00.284 --> 00:16:00.885
more difficult.

00:16:00.966 --> 00:16:02.605
But at the same time,

00:16:04.126 --> 00:16:05.866
I don't think it's an unreasonable burden

00:16:05.966 --> 00:16:07.467
to switch to these more decentralized

00:16:07.488 --> 00:16:07.988
platforms.

00:16:09.910 --> 00:16:12.352
I think that's ultimately the solution is

00:16:12.393 --> 00:16:14.514
to find or start communities outside of

00:16:14.595 --> 00:16:16.976
Reddit that aren't going to be subject to

00:16:16.996 --> 00:16:21.041
these onerous restrictions or requirements

00:16:21.061 --> 00:16:22.601
to create an account that can be used

00:16:22.682 --> 00:16:25.784
for tracking you and what you're browsing.

00:16:26.184 --> 00:16:28.105
I would imagine for a lot of the

00:16:28.125 --> 00:16:29.587
kind of stuff that people are doing on

00:16:29.648 --> 00:16:29.947
Reddit,

00:16:30.248 --> 00:16:31.729
having all of that tied to a specific

00:16:31.769 --> 00:16:33.211
profile is definitely going to...

00:16:35.032 --> 00:16:36.533
tell Reddit, tell advertisers,

00:16:36.572 --> 00:16:38.094
tell the people that they're selling data

00:16:38.114 --> 00:16:40.777
to a lot of stuff about you and

00:16:40.797 --> 00:16:42.597
then tied with your IP address and that

00:16:42.618 --> 00:16:42.977
kind of thing.

00:16:43.018 --> 00:16:44.740
It's probably trivial to tie a lot of

00:16:44.759 --> 00:16:48.221
that information to your real to your real

00:16:48.261 --> 00:16:48.783
information.

00:16:48.903 --> 00:16:51.063
And so, yeah,

00:16:51.504 --> 00:16:54.147
just decentralizing all of that, I think,

00:16:54.187 --> 00:16:58.330
is the long term goal to definitely to

00:16:58.350 --> 00:17:00.171
definitely work on for for people in

00:17:00.211 --> 00:17:00.831
organizations.

00:17:02.303 --> 00:17:02.583
Yeah,

00:17:02.604 --> 00:17:03.764
and one thing I want to point out,

00:17:03.825 --> 00:17:05.287
somebody else responded and basically said

00:17:05.326 --> 00:17:05.487
that.

00:17:05.507 --> 00:17:06.647
They said the end game of all this

00:17:06.667 --> 00:17:07.989
is self-hosting and federation.

00:17:08.390 --> 00:17:09.691
And I totally agree with you,

00:17:09.750 --> 00:17:11.792
but I want to add to that.

00:17:12.252 --> 00:17:13.074
I'm not disagreeing.

00:17:14.214 --> 00:17:15.476
I'm always the person who's like, well,

00:17:15.496 --> 00:17:16.798
think about the normies and the people who

00:17:16.857 --> 00:17:17.818
aren't super tech savvy.

00:17:18.239 --> 00:17:19.220
And I think this is one of those

00:17:19.259 --> 00:17:22.163
situations where actually those of us who

00:17:22.222 --> 00:17:24.545
are more tech savvy can be like the

00:17:24.545 --> 00:17:26.626
–

00:17:24.664 --> 00:17:26.286
was, I'm not good with words today.

00:17:26.767 --> 00:17:28.248
Um, but the anchor point, I guess,

00:17:28.788 --> 00:17:29.969
for our friends, you know,

00:17:30.028 --> 00:17:31.710
like if you know how to host,

00:17:31.750 --> 00:17:33.030
like my, my sister, for example,

00:17:33.070 --> 00:17:34.751
has access to my, my, um,

00:17:34.791 --> 00:17:38.173
jellyfin server and she can just text me

00:17:38.273 --> 00:17:39.674
and be like, Hey, it's not working,

00:17:39.694 --> 00:17:40.415
you know, or whatever.

00:17:40.576 --> 00:17:41.096
And it's,

00:17:41.175 --> 00:17:42.477
it's super easy and she doesn't have to

00:17:42.517 --> 00:17:43.198
handle any of it.

00:17:43.597 --> 00:17:44.278
And so I think, you know,

00:17:44.298 --> 00:17:45.660
there's certain things that like, um,

00:17:45.819 --> 00:17:47.240
like switching to graphene or switching to

00:17:47.260 --> 00:17:47.721
Linux, like,

00:17:48.181 --> 00:17:49.482
or switching to proton mail, you know,

00:17:49.502 --> 00:17:50.163
we need, yeah,

00:17:50.203 --> 00:17:51.345
the user has to do that.

00:17:51.665 --> 00:17:53.047
But when it comes to things like hosting

00:17:53.186 --> 00:17:56.050
Mastodon or peer tube or, um, next cloud,

00:17:56.411 --> 00:17:57.712
like those are things that you can do

00:17:57.833 --> 00:17:59.515
and then manage for your friends and

00:17:59.555 --> 00:17:59.875
family.

00:17:59.894 --> 00:18:00.856
And, you know,

00:18:00.876 --> 00:18:01.517
you kind of need to like,

00:18:01.537 --> 00:18:02.538
you need to be upfront with them.

00:18:02.578 --> 00:18:03.019
Like, um,

00:18:03.779 --> 00:18:04.420
Like we actually,

00:18:04.519 --> 00:18:05.740
I actually just installed a pie hole on

00:18:05.760 --> 00:18:06.480
my network yesterday.

00:18:06.861 --> 00:18:07.840
And I told my wife, I'm like,

00:18:07.881 --> 00:18:08.661
just FYI,

00:18:09.080 --> 00:18:10.602
technically I can see all the websites you

00:18:10.642 --> 00:18:10.961
go to.

00:18:11.382 --> 00:18:12.162
I don't really care.

00:18:12.261 --> 00:18:13.682
I'm just looking for trackers and stuff

00:18:13.702 --> 00:18:14.103
like that,

00:18:14.442 --> 00:18:15.563
but I just want you to know.

00:18:16.083 --> 00:18:17.203
And she did not care.

00:18:17.284 --> 00:18:18.483
So, um, you know,

00:18:18.503 --> 00:18:19.804
but like letting people know, like, Hey,

00:18:19.923 --> 00:18:20.664
I have this cloud.

00:18:20.684 --> 00:18:21.625
You're welcome to use it.

00:18:22.144 --> 00:18:23.005
And I mean,

00:18:23.085 --> 00:18:24.486
some people will probably take advantage

00:18:24.506 --> 00:18:25.945
of that and be super entitled and crappy

00:18:25.986 --> 00:18:26.665
about it, but you know,

00:18:26.746 --> 00:18:28.027
other people will just like, Oh,

00:18:28.047 --> 00:18:28.707
this is really cool.

00:18:28.727 --> 00:18:29.086
Thank you.

00:18:29.126 --> 00:18:29.227
And

00:18:29.846 --> 00:18:30.146
you know?

00:18:30.366 --> 00:18:31.528
So, um, yeah,

00:18:31.567 --> 00:18:32.508
I guess what I'm getting at is like,

00:18:32.548 --> 00:18:33.989
this is one of those rare situations where

00:18:34.009 --> 00:18:34.189
like,

00:18:34.689 --> 00:18:36.309
it's not so much every single person needs

00:18:36.329 --> 00:18:38.030
to host their own Mastodon or, uh,

00:18:38.070 --> 00:18:38.711
I think there's, what is it?

00:18:38.750 --> 00:18:40.893
Plymora Plymora is like the lightweight

00:18:40.913 --> 00:18:41.232
version,

00:18:41.712 --> 00:18:43.374
but like you could host a small instance

00:18:43.453 --> 00:18:44.653
and just give a few family and friends

00:18:44.713 --> 00:18:45.934
access and that helps them out.

00:18:46.015 --> 00:18:47.256
And they don't necessarily have to be

00:18:47.296 --> 00:18:48.056
super tech savvy.

00:18:48.076 --> 00:18:48.916
So yeah, for sure.

00:18:49.297 --> 00:18:50.416
As found dogs that we can all be

00:18:50.717 --> 00:18:51.938
big tech.

00:18:52.038 --> 00:18:52.538
Exactly.

00:18:53.118 --> 00:18:53.439
Yeah.

00:18:53.959 --> 00:18:55.539
And that's super true.

00:18:55.579 --> 00:18:56.961
I think people forget, um,

00:18:58.136 --> 00:19:00.518
that like hosting forums in communities,

00:19:00.538 --> 00:19:03.239
you could do that on like really low

00:19:03.338 --> 00:19:05.960
end content back in like two thousand five

00:19:05.980 --> 00:19:08.221
or so low end hardware back in two

00:19:08.240 --> 00:19:08.820
thousand five.

00:19:08.901 --> 00:19:09.020
Right.

00:19:09.080 --> 00:19:09.221
I mean,

00:19:09.240 --> 00:19:10.362
it's not like computers are super

00:19:10.422 --> 00:19:10.981
powerful.

00:19:12.282 --> 00:19:13.742
You could certainly host it on pretty much

00:19:13.962 --> 00:19:14.824
anything today.

00:19:15.104 --> 00:19:18.184
It's really not very intensive to host a

00:19:18.224 --> 00:19:20.365
lot of these to host a lot of

00:19:20.385 --> 00:19:21.506
this software.

00:19:21.566 --> 00:19:22.987
Not that everyone can do it,

00:19:23.007 --> 00:19:23.846
but just like you said,

00:19:24.827 --> 00:19:25.268
I think it

00:19:26.413 --> 00:19:29.415
can be on some of the more technical

00:19:29.435 --> 00:19:33.478
people in certain communities to create

00:19:33.498 --> 00:19:34.959
these platforms for other people to join.

00:19:35.138 --> 00:19:37.160
It would be great if instead of the

00:19:37.200 --> 00:19:38.400
movies subreddit,

00:19:38.441 --> 00:19:40.080
if a bunch of people got together to

00:19:40.121 --> 00:19:42.482
discuss movies on some site like that.

00:19:42.583 --> 00:19:45.984
But it does require a lot of collaboration

00:19:46.025 --> 00:19:47.144
and I know that people find that

00:19:47.164 --> 00:19:47.585
difficult.

00:19:49.226 --> 00:19:50.346
Well, and also just to add onto that,

00:19:50.527 --> 00:19:50.987
I was going to say,

00:19:51.007 --> 00:19:52.428
if you're hosting a small community,

00:19:52.488 --> 00:19:53.907
like again, for like a family,

00:19:53.968 --> 00:19:54.749
next cloud instance,

00:19:55.068 --> 00:19:56.849
the beauty of that is you probably don't

00:19:56.890 --> 00:19:58.329
need to pay a ton in storage because

00:19:58.349 --> 00:20:00.151
you're not providing like five gigs for

00:20:00.211 --> 00:20:00.632
everybody.

00:20:00.711 --> 00:20:02.672
It's just, you know, a handful of people,

00:20:02.752 --> 00:20:03.313
I guess,

00:20:03.353 --> 00:20:05.334
unless you come from a big family, but,

00:20:05.554 --> 00:20:05.673
um,

00:20:06.617 --> 00:20:06.698
Yeah.

00:20:06.738 --> 00:20:07.538
I was just going to say real quick,

00:20:07.578 --> 00:20:09.339
Ben said I use RSS feed regularly to

00:20:09.359 --> 00:20:11.240
get the best post without doom scrolling.

00:20:11.280 --> 00:20:11.801
It's yeah.

00:20:11.842 --> 00:20:13.143
Like RSS is so useful.

00:20:13.222 --> 00:20:14.943
I used to, um,

00:20:15.023 --> 00:20:16.025
I used to use it to get like,

00:20:16.204 --> 00:20:16.565
Oh,

00:20:16.605 --> 00:20:17.806
click the wrong button to get like news

00:20:17.826 --> 00:20:18.185
feeds.

00:20:18.665 --> 00:20:22.009
And then, um, I could filter out like,

00:20:23.529 --> 00:20:25.270
uh, right now I use next clouds RSS,

00:20:25.290 --> 00:20:26.791
which admittedly is not great for this.

00:20:27.272 --> 00:20:28.913
Um, but Thunderbird used to be amazing.

00:20:29.054 --> 00:20:30.575
I could filter out like sponsored posts

00:20:30.595 --> 00:20:32.375
and ads and like all kinds of cool

00:20:32.395 --> 00:20:32.695
stuff.

00:20:32.756 --> 00:20:35.337
So yeah, RSS going away really sucks.

00:20:36.138 --> 00:20:36.318
Um,

00:20:38.482 --> 00:20:40.183
people are chatty tonight uh do you think

00:20:40.203 --> 00:20:41.664
they could still get around this like like

00:20:41.684 --> 00:20:43.125
knitter yeah we were just talking about

00:20:43.145 --> 00:20:45.307
that earlier um right now we do have

00:20:45.407 --> 00:20:47.549
a few reddit front ends but it's really

00:20:47.569 --> 00:20:48.911
a question of like with this access

00:20:48.951 --> 00:20:50.612
closing off are they still going to be

00:20:50.711 --> 00:20:52.733
technically feasible and then if they find

00:20:52.773 --> 00:20:54.214
workarounds like knitter did are they

00:20:54.234 --> 00:20:55.415
still going to be you know are they

00:20:55.435 --> 00:20:56.717
going to get hit with a cease and

00:20:56.737 --> 00:20:57.958
desist so we don't really know at this

00:20:57.998 --> 00:21:00.138
time um we'll just have to wait and

00:21:00.159 --> 00:21:04.082
see but um let's see here sorry i'm

00:21:04.102 --> 00:21:05.202
trying to read a whole bunch of things

00:21:05.604 --> 00:21:05.763
um

00:21:07.045 --> 00:21:07.244
Yeah,

00:21:07.285 --> 00:21:09.645
somebody in the forum thread pointed out

00:21:09.705 --> 00:21:12.426
that apparently the social media

00:21:12.487 --> 00:21:14.207
propaganda is much stronger than we

00:21:14.247 --> 00:21:14.666
thought it was.

00:21:14.686 --> 00:21:15.928
And they actually provided a source for

00:21:15.968 --> 00:21:16.167
that.

00:21:16.228 --> 00:21:19.588
So that was pretty interesting to read.

00:21:19.669 --> 00:21:20.568
I kind of skimmed that because it was

00:21:20.588 --> 00:21:20.969
pretty long.

00:21:21.009 --> 00:21:21.969
But I was like, oh, lovely.

00:21:22.028 --> 00:21:22.470
So yeah,

00:21:22.950 --> 00:21:24.710
maybe we should all just get off

00:21:24.910 --> 00:21:25.871
mainstream social media.

00:21:25.911 --> 00:21:26.631
It's probably not great.

00:21:28.951 --> 00:21:30.432
Let me ask or read a couple of

00:21:30.451 --> 00:21:31.471
these questions here.

00:21:35.034 --> 00:21:35.273
Yeah.

00:21:35.314 --> 00:21:35.993
Well,

00:21:36.034 --> 00:21:36.795
this kind of goes back to what we

00:21:36.815 --> 00:21:37.194
were talking about.

00:21:37.214 --> 00:21:38.275
The problem is that the quote unquote

00:21:38.315 --> 00:21:39.915
normies are unaware or simply don't care,

00:21:40.036 --> 00:21:40.757
outnumber the rest of us.

00:21:40.777 --> 00:21:42.057
So the experience on a wide range of

00:21:42.116 --> 00:21:43.617
topics ends up being very limited.

00:21:44.157 --> 00:21:45.358
Yeah.

00:21:45.419 --> 00:21:46.398
I think that's the problem we're all

00:21:46.439 --> 00:21:47.660
struggling with is like even something

00:21:47.680 --> 00:21:48.819
like Mastodon, in my opinion,

00:21:48.859 --> 00:21:49.700
is very feature rich.

00:21:49.740 --> 00:21:50.621
It's very mature.

00:21:51.320 --> 00:21:52.121
It's, in my opinion,

00:21:52.141 --> 00:21:53.221
a very nice experience.

00:21:53.261 --> 00:21:53.701
And it's like, well,

00:21:53.721 --> 00:21:54.702
how am I supposed to get people?

00:21:55.502 --> 00:21:56.663
It's like the network effect, right?

00:21:56.682 --> 00:21:57.104
It's like, yeah,

00:21:57.124 --> 00:21:59.545
but you can't follow Taylor Swift and Mark

00:21:59.585 --> 00:21:59.825
Ruffalo.

00:21:59.865 --> 00:22:01.265
Actually, Mark Ruffalo is on Mastodon,

00:22:01.285 --> 00:22:02.246
but he hasn't posted in like

00:22:02.625 --> 00:22:04.605
a year um you know like all these

00:22:04.645 --> 00:22:06.626
big names that you want to follow it's

00:22:06.787 --> 00:22:08.247
you can't really find them on a lot

00:22:08.267 --> 00:22:10.228
of these other social media it's it's a

00:22:10.268 --> 00:22:11.367
problem i think everybody's trying to

00:22:11.387 --> 00:22:15.108
figure out yeah uh torsten on the forum

00:22:15.169 --> 00:22:17.088
who's a member thanks for your support uh

00:22:17.108 --> 00:22:18.848
just left a comment agreeing that like the

00:22:18.868 --> 00:22:21.069
small web type self-hosting is nice but

00:22:21.230 --> 00:22:23.609
they find it really intimidating uh

00:22:23.650 --> 00:22:24.849
because you need to do so much stuff

00:22:24.869 --> 00:22:27.090
to protect them protect those servers um

00:22:28.044 --> 00:22:29.605
like if you use tail scale, for example,

00:22:29.625 --> 00:22:30.425
to kind of limit that,

00:22:30.665 --> 00:22:32.146
that's a good way to keep your things

00:22:32.186 --> 00:22:32.487
secure.

00:22:32.507 --> 00:22:34.488
But then that kind of limits who can

00:22:34.567 --> 00:22:36.009
access it by design,

00:22:36.048 --> 00:22:39.291
which is hard for communities like larger

00:22:39.311 --> 00:22:39.892
communities.

00:22:41.333 --> 00:22:41.532
I mean,

00:22:41.553 --> 00:22:43.554
it is a tough issue for for sure.

00:22:43.755 --> 00:22:47.116
And I think I think a solution for

00:22:47.136 --> 00:22:48.817
that is not just like for a lot

00:22:48.857 --> 00:22:51.740
of techie people to spin up things on

00:22:51.759 --> 00:22:52.200
their own,

00:22:52.259 --> 00:22:53.000
but I think people

00:22:56.077 --> 00:22:56.298
You know,

00:22:56.317 --> 00:22:58.559
coming together and creating a small

00:22:58.880 --> 00:23:01.863
community of people who have technical

00:23:01.883 --> 00:23:03.285
skills who can kind of work together on

00:23:03.305 --> 00:23:04.285
that kind of stuff is going to be

00:23:04.325 --> 00:23:05.266
a lot more sustainable.

00:23:05.906 --> 00:23:07.248
But that's kind of where the collaboration

00:23:07.268 --> 00:23:08.269
stuff comes in again,

00:23:08.809 --> 00:23:11.051
at least if we're talking about public

00:23:11.071 --> 00:23:14.714
things like a Mastodon instance or a forum

00:23:14.755 --> 00:23:15.496
or something like that.

00:23:17.458 --> 00:23:18.038
Yeah, for sure.

00:23:18.337 --> 00:23:19.378
Anonymous said they just joined.

00:23:19.398 --> 00:23:20.338
Have we been talking about Reddit the

00:23:20.358 --> 00:23:20.720
whole time?

00:23:20.819 --> 00:23:21.319
We have,

00:23:21.380 --> 00:23:22.200
but actually I was going to say,

00:23:22.240 --> 00:23:24.422
unless you have anything to add or any

00:23:24.461 --> 00:23:25.041
last thoughts,

00:23:25.102 --> 00:23:28.163
there's one more question here in the

00:23:28.242 --> 00:23:28.763
forum.

00:23:29.064 --> 00:23:30.845
I wonder if you guys could discuss the

00:23:30.884 --> 00:23:33.026
secure paste feature added to Graphene OS.

00:23:33.145 --> 00:23:34.946
I think it's a great feature that everyone

00:23:34.967 --> 00:23:35.567
should enable.

00:23:36.208 --> 00:23:37.288
Do you have any thoughts about this one?

00:23:37.867 --> 00:23:38.769
I thought it was still in beta.

00:23:38.828 --> 00:23:39.888
I didn't know it was like out out.

00:23:41.289 --> 00:23:42.770
I only know that it exists,

00:23:42.810 --> 00:23:45.971
but I haven't looked into it myself,

00:23:46.011 --> 00:23:46.853
so I don't know how it works.

00:23:47.684 --> 00:23:47.944
Okay.

00:23:48.045 --> 00:23:48.224
Yeah.

00:23:48.425 --> 00:23:49.405
I, um, again,

00:23:49.465 --> 00:23:50.346
I thought it was still in beta,

00:23:50.386 --> 00:23:51.686
but apparently it is out out.

00:23:51.748 --> 00:23:53.228
The only thing I can really say is

00:23:53.307 --> 00:23:54.628
side of burritos, the YouTuber,

00:23:54.669 --> 00:23:57.351
he does pretty much nothing but graphene

00:23:57.391 --> 00:23:58.250
videos on YouTube.

00:23:58.270 --> 00:23:59.372
And he did a video about this.

00:23:59.392 --> 00:24:01.012
That was really interesting actually.

00:24:01.252 --> 00:24:01.432
Um,

00:24:01.874 --> 00:24:03.253
which remember for those of you watching

00:24:03.294 --> 00:24:03.454
now,

00:24:03.515 --> 00:24:04.994
remember when we talk about this later on,

00:24:05.076 --> 00:24:05.996
cause I'm going to mention that video

00:24:06.036 --> 00:24:06.296
again,

00:24:06.696 --> 00:24:08.837
but he built his own little app that,

00:24:09.057 --> 00:24:09.258
um,

00:24:09.958 --> 00:24:12.500
reads your clipboard to illustrate what

00:24:12.940 --> 00:24:14.881
the secure clipboard feature does and why

00:24:14.921 --> 00:24:15.461
it's useful.

00:24:15.642 --> 00:24:16.903
So, um,

00:24:17.583 --> 00:24:19.163
Yeah, I'd say if you're curious about it,

00:24:19.202 --> 00:24:20.223
go check it out because I thought that

00:24:20.243 --> 00:24:21.703
was a really interesting video.

00:24:23.464 --> 00:24:23.585
Yeah,

00:24:23.605 --> 00:24:24.565
I think that's all I got on that.

00:24:25.045 --> 00:24:25.244
Yeah,

00:24:25.325 --> 00:24:26.766
I'm sure other people on the team have

00:24:27.625 --> 00:24:30.145
used it and have more experience than me.

00:24:30.165 --> 00:24:31.727
There's probably discussion about it on

00:24:31.747 --> 00:24:32.267
the forum too.

00:24:32.307 --> 00:24:34.327
I think that's a good place to find

00:24:34.367 --> 00:24:35.748
out information about new stuff like that.

00:24:37.030 --> 00:24:37.912
Probably, yeah.

00:24:37.932 --> 00:24:40.133
There's always discussions on the forum,

00:24:40.173 --> 00:24:41.453
especially about stuff like graphene.

00:24:43.095 --> 00:24:43.336
Yeah,

00:24:43.496 --> 00:24:45.196
I think for now it's probably a good

00:24:45.237 --> 00:24:46.218
time to go ahead and move on to

00:24:46.238 --> 00:24:46.817
the next story.

00:24:47.097 --> 00:24:47.298
Yeah,

00:24:47.317 --> 00:24:48.499
let's take a look at this one here.

00:24:48.859 --> 00:24:50.840
This is by ForoForMedia.

00:24:51.161 --> 00:24:51.662
The headline is,

00:24:51.701 --> 00:24:54.002
Cops can bypass iPhone's automatic reboot

00:24:54.063 --> 00:24:57.125
to get into locked phone's leaked videos.

00:24:57.286 --> 00:24:58.787
Claim, Magnet Forensics,

00:24:58.826 --> 00:25:00.548
the owner of the gray key phone unlocking

00:25:00.587 --> 00:25:00.768
tool,

00:25:00.788 --> 00:25:02.789
says it can bypass an iPhone reboot...

00:25:03.509 --> 00:25:05.590
It can bypass an iPhone rebooting feature

00:25:05.651 --> 00:25:07.692
that was locking cops out.

00:25:08.553 --> 00:25:10.275
In November, twenty twenty four,

00:25:10.694 --> 00:25:12.655
four or four media revealed that Apple

00:25:12.695 --> 00:25:14.958
quietly introduced a new feature in iOS

00:25:14.978 --> 00:25:16.979
that automatically reboots an iPhone that

00:25:16.999 --> 00:25:19.401
has not been unlocked for seventy two

00:25:19.441 --> 00:25:19.840
hours.

00:25:20.000 --> 00:25:21.882
And the idea behind this so-called

00:25:22.241 --> 00:25:23.163
inactivity reboot

00:25:23.462 --> 00:25:25.483
is to revert the phone to a state

00:25:25.503 --> 00:25:27.425
that makes it harder for police to break

00:25:27.465 --> 00:25:29.826
into the device and thus extract sensitive

00:25:29.866 --> 00:25:31.768
data from it with forensics technology.

00:25:31.988 --> 00:25:33.650
If you're in the Graphene OS community,

00:25:33.670 --> 00:25:35.451
you've certainly heard about this like

00:25:35.691 --> 00:25:38.172
before first unlock or after first unlock

00:25:38.211 --> 00:25:39.373
state for encryption.

00:25:39.833 --> 00:25:40.334
And in a

00:25:40.933 --> 00:25:43.115
a phone that's in a before first unlocked

00:25:43.195 --> 00:25:46.097
state, whether it's Android or iOS,

00:25:46.137 --> 00:25:47.720
is going to be more secure than after

00:25:47.759 --> 00:25:48.880
you unlock it for the first time.

00:25:48.900 --> 00:25:51.301
So that's where rebooting your phone may

00:25:51.321 --> 00:25:51.603
come in,

00:25:51.643 --> 00:25:53.804
especially if it hasn't been used in quite

00:25:53.844 --> 00:25:54.325
some time.

00:25:55.726 --> 00:25:56.066
However,

00:25:56.145 --> 00:25:58.167
this new technology to get around the

00:25:58.248 --> 00:26:00.890
inactivity reboot on iOS was developed by

00:26:01.009 --> 00:26:02.010
Magnet Forensics,

00:26:02.290 --> 00:26:03.652
the company behind Gray Key,

00:26:03.711 --> 00:26:05.753
a popular tool sold to law enforcement

00:26:05.794 --> 00:26:07.836
agencies that allows them to

00:26:09.377 --> 00:26:11.740
unlock and access data stored in iPhones

00:26:11.861 --> 00:26:13.022
and Android smartphones.

00:26:13.243 --> 00:26:15.307
Magnet has developed a new device called

00:26:15.386 --> 00:26:17.369
GrayKey Preserve and a feature for its

00:26:17.490 --> 00:26:19.773
regular GrayKey devices called Evidence

00:26:19.854 --> 00:26:20.734
Preservation Mode,

00:26:21.115 --> 00:26:23.159
according to the leaked video.

00:26:24.528 --> 00:26:26.751
This is an educational and tutorial video,

00:26:26.771 --> 00:26:28.433
which was made exclusively for law

00:26:28.453 --> 00:26:30.376
enforcement agents and appears to be dated

00:26:31.157 --> 00:26:32.199
early twenty twenty five.

00:26:32.940 --> 00:26:34.662
The video does not explain the technical

00:26:34.702 --> 00:26:36.163
details behind the new product and

00:26:36.183 --> 00:26:36.484
feature,

00:26:36.505 --> 00:26:38.948
but it gives some strong hints as to

00:26:39.449 --> 00:26:40.450
how it works.

00:26:42.192 --> 00:26:45.074
Taking a look here, it says, yeah,

00:26:45.194 --> 00:26:46.095
in a quote, now,

00:26:46.215 --> 00:26:47.517
one of the many things that the gray

00:26:47.537 --> 00:26:49.198
key preserve is going to do is it's

00:26:49.238 --> 00:26:51.180
going to enable airplane mode or more

00:26:51.240 --> 00:26:51.740
specifically,

00:26:51.760 --> 00:26:53.142
it's going to disable our radio

00:26:53.182 --> 00:26:54.522
transmissions like Bluetooth,

00:26:54.563 --> 00:26:55.443
Wi-Fi and cellular.

00:26:55.743 --> 00:26:56.244
In doing this,

00:26:56.285 --> 00:26:58.307
that's not only going to allow you to

00:26:58.366 --> 00:26:59.567
preserve the data in the field,

00:26:59.587 --> 00:27:01.630
but also isolate the data in the field,

00:27:02.269 --> 00:27:03.771
as an employee explains.

00:27:04.392 --> 00:27:06.295
even if that device doesn't have the

00:27:06.315 --> 00:27:08.298
ability to turn on airplane mode or to

00:27:08.337 --> 00:27:09.759
turn off the transmitters through the

00:27:09.819 --> 00:27:11.082
control center of iOS.

00:27:11.402 --> 00:27:12.903
Once initial access is gained and the

00:27:12.923 --> 00:27:14.205
device is in a preserved state,

00:27:14.226 --> 00:27:15.828
we also disable all of those radios to

00:27:15.868 --> 00:27:18.071
make sure the data cannot reach that

00:27:18.092 --> 00:27:18.491
device.

00:27:19.673 --> 00:27:20.574
Um,

00:27:20.614 --> 00:27:23.276
so it says that the after first unlock

00:27:23.336 --> 00:27:26.416
state is captured by gray key preserve and

00:27:26.477 --> 00:27:27.777
evidence preservation mode.

00:27:28.057 --> 00:27:30.157
So that even if that device does reboot

00:27:30.178 --> 00:27:31.378
for any number of reasons,

00:27:31.519 --> 00:27:33.500
memory maintenance or the power is lost or

00:27:33.519 --> 00:27:36.181
whatever the after first unlock state is

00:27:36.260 --> 00:27:38.162
not lost.

00:27:38.402 --> 00:27:38.541
Um,

00:27:40.487 --> 00:27:41.606
So, yeah,

00:27:41.767 --> 00:27:44.288
it says when using the new solution,

00:27:44.468 --> 00:27:46.388
law enforcement agents only see the iPhone

00:27:46.449 --> 00:27:48.169
software version and device model rather

00:27:48.189 --> 00:27:49.509
than any data within,

00:27:49.829 --> 00:27:51.529
according to the employee in a screenshot

00:27:51.569 --> 00:27:53.069
of great keys customer interface that's

00:27:53.089 --> 00:27:55.290
included in the video that allows the cops

00:27:55.310 --> 00:27:56.590
to preserve the data they care about

00:27:56.631 --> 00:27:58.412
without actually seeing it before they're

00:27:58.832 --> 00:28:00.393
authorized to do so.

00:28:02.594 --> 00:28:04.634
So a researcher who has looked into this

00:28:04.674 --> 00:28:06.615
thinks that Magnet has found a way to

00:28:06.875 --> 00:28:08.876
manipulate the iPhone clock,

00:28:09.517 --> 00:28:12.298
effectively slowing down time or even

00:28:12.377 --> 00:28:14.239
stopping the clock from ticking even after

00:28:14.259 --> 00:28:14.779
a reboot.

00:28:15.859 --> 00:28:17.740
Most likely, according to this researcher,

00:28:17.780 --> 00:28:19.781
the Great Key may disable the iPhone tasks

00:28:20.362 --> 00:28:22.143
that set data to expire.

00:28:22.782 --> 00:28:25.865
So lots of stuff to unpack here.

00:28:27.464 --> 00:28:29.445
What does this mean for iPhone users?

00:28:29.465 --> 00:28:30.086
What do you think, Nate?

00:28:31.287 --> 00:28:34.008
Yeah, I mean, I don't know.

00:28:34.028 --> 00:28:35.509
The best I could come up with is,

00:28:36.328 --> 00:28:36.469
I mean,

00:28:36.509 --> 00:28:37.910
the automatic reboot is designed to be

00:28:37.930 --> 00:28:39.170
there as a safety net, right?

00:28:39.529 --> 00:28:40.990
And in my opinion,

00:28:41.030 --> 00:28:42.830
seventy two hours is a crazy long safety

00:28:42.851 --> 00:28:43.352
net anyways.

00:28:43.832 --> 00:28:45.392
But I would say my first thought is

00:28:45.451 --> 00:28:47.032
don't rely on the automatic reboot if

00:28:47.093 --> 00:28:47.532
possible.

00:28:47.673 --> 00:28:49.693
Like something I think I mentioned this on

00:28:49.733 --> 00:28:50.354
previous episodes.

00:28:50.773 --> 00:28:52.214
I don't think my threat model is

00:28:52.255 --> 00:28:52.974
particularly high,

00:28:53.015 --> 00:28:54.855
but just to be safe when I go

00:28:54.875 --> 00:28:56.155
through airports now and, you know,

00:28:56.175 --> 00:28:57.616
you have to put everything to go through

00:28:57.636 --> 00:28:58.237
the X-ray machine,

00:28:58.696 --> 00:28:59.778
I go ahead and reboot my phone.

00:29:00.657 --> 00:29:02.218
And by the time it gets through the

00:29:02.337 --> 00:29:02.878
x-ray machine,

00:29:02.939 --> 00:29:04.838
it's fully rebooted and ready for me to

00:29:04.878 --> 00:29:05.419
log back in.

00:29:05.838 --> 00:29:06.358
And that way,

00:29:06.459 --> 00:29:08.339
in the off chance that I do get

00:29:08.380 --> 00:29:09.539
pulled aside and they're like, oh,

00:29:09.799 --> 00:29:10.859
we're gonna take your phone into this

00:29:10.900 --> 00:29:12.601
other room and do whatever weird stuff

00:29:12.621 --> 00:29:12.820
with it.

00:29:13.121 --> 00:29:14.260
Well, it's in BFU.

00:29:14.280 --> 00:29:15.800
That is literally the best case I can

00:29:15.840 --> 00:29:16.001
do.

00:29:16.122 --> 00:29:17.961
And I won't have time to like,

00:29:18.061 --> 00:29:19.221
oh wait, let me see it real quick.

00:29:19.281 --> 00:29:20.722
And obviously they're not gonna let me do

00:29:20.762 --> 00:29:20.883
that.

00:29:22.583 --> 00:29:23.564
And then I know this is actually a

00:29:23.584 --> 00:29:24.805
video that you and I have talked about

00:29:24.825 --> 00:29:25.884
making for some time,

00:29:25.924 --> 00:29:28.567
but digital minimalism is a bit of a

00:29:28.606 --> 00:29:28.926
luxury.

00:29:28.967 --> 00:29:30.008
It's not always like,

00:29:30.087 --> 00:29:31.608
just don't have anything on your phone,

00:29:31.648 --> 00:29:33.790
obviously.

00:29:33.810 --> 00:29:35.531
That's one thing people talk about a lot

00:29:35.571 --> 00:29:36.913
is if they're traveling internationally,

00:29:36.932 --> 00:29:38.093
they're like, oh, bring a burner phone.

00:29:38.113 --> 00:29:38.534
And it's like, yeah,

00:29:38.554 --> 00:29:39.914
that's cool if you can afford a burner

00:29:39.934 --> 00:29:40.255
phone.

00:29:40.295 --> 00:29:42.957
But still, just being mindful.

00:29:43.176 --> 00:29:45.117
Are there things that you can take off

00:29:45.157 --> 00:29:45.478
of your phone,

00:29:45.518 --> 00:29:46.679
especially if you do know you're going to

00:29:46.699 --> 00:29:48.160
be going to a protest or somewhere where

00:29:48.180 --> 00:29:49.580
you might get pulled over or something?

00:29:49.621 --> 00:29:51.782
And so, yeah, just kind of,

00:29:52.583 --> 00:29:53.864
keeping that kind of stuff in mind,

00:29:53.903 --> 00:29:56.005
I think is at least the best I

00:29:56.025 --> 00:29:56.545
could come up with.

00:29:56.565 --> 00:29:57.605
I don't know if you have any additional

00:29:57.625 --> 00:29:57.986
thoughts.

00:29:59.307 --> 00:30:00.027
Yeah, for sure.

00:30:00.146 --> 00:30:03.209
It's it's tricky to rely on a lot

00:30:03.249 --> 00:30:04.469
of these software defenses.

00:30:05.289 --> 00:30:06.769
I would think that I mean,

00:30:06.829 --> 00:30:08.151
this video is from early twenty twenty

00:30:08.171 --> 00:30:08.411
five,

00:30:08.451 --> 00:30:09.471
so I don't know if this is like

00:30:09.951 --> 00:30:11.633
already been patched.

00:30:11.992 --> 00:30:13.653
I would imagine that if it hasn't yet,

00:30:13.713 --> 00:30:15.454
Apple will probably look into it now that

00:30:15.474 --> 00:30:17.756
this capability is is known.

00:30:19.596 --> 00:30:19.916
But yeah,

00:30:19.997 --> 00:30:21.657
all of this privacy and security stuff,

00:30:21.678 --> 00:30:23.199
it's really just a game of cat and

00:30:23.219 --> 00:30:23.459
mouse.

00:30:23.479 --> 00:30:25.279
We see all these vulnerabilities come out

00:30:25.319 --> 00:30:27.540
all the time and then they get patched

00:30:27.560 --> 00:30:28.221
by these companies.

00:30:28.260 --> 00:30:30.942
And then the people who are developing

00:30:30.962 --> 00:30:32.623
these vulnerabilities for a variety of

00:30:32.682 --> 00:30:35.105
reasons will just find new ones because

00:30:35.144 --> 00:30:37.625
none of this software is, you know,

00:30:37.806 --> 00:30:39.646
it's not going to be perfectly secure by

00:30:39.707 --> 00:30:40.247
any means,

00:30:40.787 --> 00:30:42.048
especially like if it's Internet

00:30:42.067 --> 00:30:42.428
connected,

00:30:42.448 --> 00:30:43.087
you're going to have

00:30:44.615 --> 00:30:47.077
you're going to potentially run into

00:30:47.117 --> 00:30:48.138
problems.

00:30:50.141 --> 00:30:51.323
I guess there's a lot of effort being

00:30:51.363 --> 00:30:55.666
made in terms of securing new software by

00:30:55.707 --> 00:30:58.288
default, or there's things like on iOS,

00:30:58.690 --> 00:31:00.250
memory integrity enforcement,

00:31:00.411 --> 00:31:02.272
or on Android MTE,

00:31:03.835 --> 00:31:04.315
which are going to

00:31:05.355 --> 00:31:07.476
keep software more safe and prevent a lot

00:31:07.516 --> 00:31:09.297
of these vulnerabilities from happening in

00:31:09.317 --> 00:31:09.896
the first place.

00:31:09.957 --> 00:31:12.336
But even even with those vulnerabilities

00:31:12.376 --> 00:31:14.518
are found in them and the amount of

00:31:14.557 --> 00:31:16.998
just old legacy code in all of these

00:31:17.057 --> 00:31:19.219
operating systems and apps that we use is

00:31:19.818 --> 00:31:22.219
like that's not going to be replaced with

00:31:22.380 --> 00:31:24.480
with safer code for quite a while.

00:31:24.579 --> 00:31:26.599
So yeah,

00:31:26.700 --> 00:31:28.540
I think this kind of stuff will continue

00:31:28.580 --> 00:31:30.020
cropping up as an issue.

00:31:30.080 --> 00:31:30.740
But of course,

00:31:31.461 --> 00:31:33.942
to minimize your risk as much as possible,

00:31:35.345 --> 00:31:35.565
uh,

00:31:35.585 --> 00:31:37.286
keeping your devices up to date and making

00:31:37.306 --> 00:31:38.747
sure you have the very latest security

00:31:38.807 --> 00:31:40.748
patches is super important because new

00:31:40.788 --> 00:31:43.229
vulnerabilities like this are found, uh,

00:31:43.249 --> 00:31:44.148
just constantly.

00:31:46.109 --> 00:31:46.911
Yeah, for sure.

00:31:47.191 --> 00:31:47.590
Definitely.

00:31:48.351 --> 00:31:48.811
Um,

00:31:48.832 --> 00:31:51.093
Penguin had a comment here that as far

00:31:51.133 --> 00:31:53.554
as we know, graphene is not hackable, um,

00:31:53.693 --> 00:31:55.595
especially because graphene comes with,

00:31:55.634 --> 00:31:56.734
I think it's enabled by default.

00:31:57.455 --> 00:31:58.496
Um, or no,

00:31:58.615 --> 00:32:00.537
it's so they have a feature where the

00:32:00.636 --> 00:32:02.258
USB port, uh,

00:32:02.877 --> 00:32:04.898
you can basically turn it off if you

00:32:04.919 --> 00:32:06.099
want to, where it doesn't do anything,

00:32:06.480 --> 00:32:08.019
or you can set it to only charge

00:32:08.039 --> 00:32:09.101
and not transfer any data.

00:32:09.500 --> 00:32:11.521
I think the default is that while the

00:32:11.541 --> 00:32:12.281
phone is locked,

00:32:12.321 --> 00:32:13.482
it does not transfer any data,

00:32:13.522 --> 00:32:14.603
but then when you unlock it,

00:32:14.682 --> 00:32:16.864
it can do Android Auto or whatever,

00:32:17.723 --> 00:32:18.104
which actually,

00:32:18.125 --> 00:32:18.785
it's funny you mentioned that.

00:32:18.805 --> 00:32:19.505
We didn't put it in here,

00:32:19.525 --> 00:32:22.486
but literally an hour before we went live,

00:32:22.506 --> 00:32:25.047
I think it was Jordan posted an article

00:32:25.788 --> 00:32:29.848
about how somebody in Canada, yeah,

00:32:30.769 --> 00:32:31.029
there's...

00:32:32.627 --> 00:32:34.150
I'm not going to share it yet,

00:32:34.170 --> 00:32:35.111
but yeah,

00:32:35.151 --> 00:32:36.853
somebody in Canada was arrested for a

00:32:36.893 --> 00:32:37.633
shooting, I guess.

00:32:37.814 --> 00:32:40.296
And the police are currently unable to get

00:32:40.316 --> 00:32:40.517
in there,

00:32:40.696 --> 00:32:42.818
get into their phone because they're using

00:32:42.838 --> 00:32:43.219
graphene.

00:32:43.500 --> 00:32:45.801
So please don't use graphene for illegal

00:32:45.842 --> 00:32:46.202
things.

00:32:46.242 --> 00:32:47.084
But, you know,

00:32:47.124 --> 00:32:48.285
these are the kind of articles we look

00:32:48.345 --> 00:32:49.506
at and we're like, oh, OK,

00:32:49.566 --> 00:32:51.127
like graphene is doing what it says it's

00:32:51.147 --> 00:32:51.729
supposed to do.

00:32:51.788 --> 00:32:51.909
And.

00:32:54.131 --> 00:32:55.472
Yeah.

00:32:55.492 --> 00:32:56.074
Username is nice.

00:32:56.173 --> 00:32:57.315
It reminds me of when people used to

00:32:57.355 --> 00:32:59.337
set their set the date to January first,

00:32:59.397 --> 00:33:01.000
nineteen seventy to break their phones.

00:33:01.480 --> 00:33:02.201
I didn't know about that.

00:33:02.240 --> 00:33:02.622
That's funny.

00:33:06.045 --> 00:33:08.486
Nick Spice here said that they thought if

00:33:08.526 --> 00:33:10.846
people had the accessory blocking enabled,

00:33:10.885 --> 00:33:11.926
that would help combat this.

00:33:12.326 --> 00:33:13.547
I know that's not enabled by default,

00:33:13.567 --> 00:33:14.866
so it's possible that that would have

00:33:15.047 --> 00:33:15.748
combated it,

00:33:16.188 --> 00:33:18.387
but it's just not a common thing for

00:33:18.407 --> 00:33:19.228
people to have.

00:33:20.568 --> 00:33:21.509
I know that in the past,

00:33:22.148 --> 00:33:23.990
ways around that have been discovered as

00:33:24.049 --> 00:33:24.329
well.

00:33:24.690 --> 00:33:26.549
It's why even graphing OS, for example,

00:33:26.569 --> 00:33:28.431
when you can disable the USB-C port,

00:33:29.191 --> 00:33:30.830
there's varying levels of how much you can

00:33:30.871 --> 00:33:31.311
disable it.

00:33:31.551 --> 00:33:32.412
I have it disabled

00:33:33.071 --> 00:33:35.634
to where the USB-C port only works if

00:33:35.673 --> 00:33:36.654
the phone is off,

00:33:36.714 --> 00:33:38.635
and then it's only used for charging when

00:33:38.655 --> 00:33:39.276
the device is off.

00:33:39.316 --> 00:33:39.896
But if it's on,

00:33:40.057 --> 00:33:40.897
you can't use it at all,

00:33:40.958 --> 00:33:41.597
even for charging.

00:33:42.499 --> 00:33:44.079
I know they have a charging-only feature,

00:33:44.099 --> 00:33:45.980
and then they have the feature like Nate

00:33:46.000 --> 00:33:47.362
was talking about where it's just

00:33:47.402 --> 00:33:48.522
restricted when it's locked.

00:33:51.065 --> 00:33:52.746
iOS obviously doesn't have quite that

00:33:52.945 --> 00:33:56.127
granular of an approach, but it...

00:33:58.827 --> 00:33:59.028
Yeah,

00:33:59.048 --> 00:34:01.328
I don't know if this would have prevented

00:34:01.368 --> 00:34:02.230
this specific case,

00:34:02.289 --> 00:34:04.771
but enabling features like that is

00:34:04.811 --> 00:34:05.352
probably good.

00:34:05.471 --> 00:34:06.452
I know that a lot of these

00:34:06.472 --> 00:34:07.232
vulnerabilities,

00:34:07.313 --> 00:34:08.634
especially when the phone is locked on

00:34:08.693 --> 00:34:09.114
iOS,

00:34:09.494 --> 00:34:12.496
can also come from having a lot of

00:34:12.556 --> 00:34:14.217
features enabled on the lock screen.

00:34:14.358 --> 00:34:16.298
If you go to your Face ID and

00:34:16.338 --> 00:34:17.099
password settings,

00:34:17.139 --> 00:34:18.400
there's a lot of switches for like,

00:34:18.440 --> 00:34:19.742
do you want to allow Siri when the

00:34:19.762 --> 00:34:20.242
device is locked?

00:34:20.262 --> 00:34:21.563
Do you want to allow Control Center?

00:34:22.483 --> 00:34:23.063
And in this case,

00:34:23.103 --> 00:34:24.585
I think they mentioned even if Control

00:34:24.625 --> 00:34:25.304
Center is disabled,

00:34:25.324 --> 00:34:26.766
they can get around some of that stuff.

00:34:29.289 --> 00:34:31.291
like as a general rule disabling all of

00:34:31.313 --> 00:34:33.255
that stuff and locking down your phone

00:34:33.376 --> 00:34:37.802
when it's locked is going to any little

00:34:37.822 --> 00:34:39.445
bit helps when it comes to security like

00:34:39.465 --> 00:34:39.626
this

00:34:42.168 --> 00:34:42.728
Yeah, for sure.

00:34:42.989 --> 00:34:43.849
And I was going to say like one

00:34:43.869 --> 00:34:45.311
thing that stood out to me that I,

00:34:45.351 --> 00:34:46.871
the moments I always feel kind of mixed

00:34:46.911 --> 00:34:48.012
is it talks about how like,

00:34:49.213 --> 00:34:50.815
I wonder if this is a technical limitation

00:34:50.914 --> 00:34:52.456
or like a pinky promise like flock,

00:34:52.836 --> 00:34:54.338
but it says that like when they use

00:34:54.358 --> 00:34:54.637
this thing,

00:34:54.677 --> 00:34:56.099
they can only see the phone software

00:34:56.139 --> 00:34:57.039
version and device model.

00:34:57.481 --> 00:34:58.460
So in theory,

00:34:58.561 --> 00:35:00.822
it's designed to just like prevent the

00:35:00.862 --> 00:35:01.903
phone from BFU.

00:35:02.043 --> 00:35:03.385
Cause I don't know if I copied it

00:35:03.405 --> 00:35:03.945
in the notes here,

00:35:03.965 --> 00:35:06.128
but they mentioned that a lot of the

00:35:06.168 --> 00:35:08.108
time when they, they get these phones.

00:35:08.148 --> 00:35:08.409
Yeah.

00:35:09.210 --> 00:35:09.429
You know,

00:35:11.255 --> 00:35:11.576
Oh,

00:35:11.918 --> 00:35:12.559
I don't think I put it in the

00:35:12.599 --> 00:35:12.920
notes here.

00:35:13.302 --> 00:35:13.905
A lot of the time...

00:35:15.460 --> 00:35:16.400
when they get these phones,

00:35:16.440 --> 00:35:18.021
they don't break into them right away

00:35:18.382 --> 00:35:19.581
because they have to get a warrant or

00:35:19.601 --> 00:35:20.842
they have to get approval from a judge.

00:35:21.463 --> 00:35:23.043
And so I, I kind of like that,

00:35:23.143 --> 00:35:23.523
like, um,

00:35:23.722 --> 00:35:25.083
like you still can't see the data.

00:35:25.143 --> 00:35:26.704
You still have to wait and get legal

00:35:26.724 --> 00:35:28.405
approval, but I don't know.

00:35:28.485 --> 00:35:29.565
It's, I mean, it's the same with anything,

00:35:29.605 --> 00:35:29.744
right?

00:35:29.784 --> 00:35:30.164
Like, sure.

00:35:30.264 --> 00:35:31.445
In theory, it's great.

00:35:31.465 --> 00:35:32.985
The celebrate can be used to hack phones

00:35:33.005 --> 00:35:34.106
that are being used by, you know,

00:35:34.306 --> 00:35:36.367
violent cartel members and pedophiles and

00:35:36.407 --> 00:35:36.987
stuff like that.

00:35:37.467 --> 00:35:39.027
But also it can just as easily,

00:35:39.208 --> 00:35:41.088
easily be used by authoritarian

00:35:41.128 --> 00:35:42.668
governments to spy on journalists and

00:35:42.708 --> 00:35:43.028
stuff.

00:35:43.088 --> 00:35:43.228
So,

00:35:44.619 --> 00:35:46.601
Yeah, it's definitely an interesting case.

00:35:46.641 --> 00:35:46.822
I mean,

00:35:46.862 --> 00:35:48.943
this is that's more of a case of

00:35:49.003 --> 00:35:51.505
like gray key policy kind of coming into

00:35:51.565 --> 00:35:54.007
play and preventing police officers from

00:35:54.047 --> 00:35:55.788
like going rogue and using this for

00:35:55.927 --> 00:35:57.469
personal purposes, which, of course,

00:35:57.509 --> 00:35:58.449
is a big issue.

00:35:59.489 --> 00:35:59.710
You know,

00:35:59.730 --> 00:36:02.831
we've talked about it in numerous videos

00:36:02.873 --> 00:36:05.114
in the past of like law enforcement agents

00:36:05.134 --> 00:36:06.875
kind of abusing these powers for their own

00:36:06.914 --> 00:36:07.655
personal gain.

00:36:08.255 --> 00:36:09.416
And maybe this prevents that.

00:36:09.516 --> 00:36:10.056
But it doesn't.

00:36:11.215 --> 00:36:12.094
I mean, at the end of the day,

00:36:12.155 --> 00:36:13.175
they still have the data,

00:36:13.275 --> 00:36:14.797
even if it's not accessible to an

00:36:14.856 --> 00:36:16.958
individual officer before it goes through

00:36:16.978 --> 00:36:18.338
like this approval process.

00:36:18.998 --> 00:36:21.559
And it kind of calls into question we

00:36:21.599 --> 00:36:23.300
talked about this with flock cameras,

00:36:23.320 --> 00:36:23.780
for example,

00:36:23.800 --> 00:36:25.942
which are kind of collecting all of this

00:36:25.981 --> 00:36:27.601
data all the time and storing it in

00:36:27.641 --> 00:36:28.342
a database.

00:36:28.523 --> 00:36:30.224
And even though you're only supposed to

00:36:30.423 --> 00:36:32.324
access that database with a warrant,

00:36:33.864 --> 00:36:34.746
in some cases,

00:36:35.746 --> 00:36:36.085
you know,

00:36:36.226 --> 00:36:37.927
the fact that the data exists in the

00:36:37.967 --> 00:36:39.248
database in the first place,

00:36:39.307 --> 00:36:41.369
I think is is an issue and in

00:36:41.429 --> 00:36:42.731
a Fourth Amendment violation,

00:36:42.851 --> 00:36:46.974
like just on its own without regardless of

00:36:47.034 --> 00:36:48.875
whether that data was queried by a

00:36:48.914 --> 00:36:49.655
government agent.

00:36:49.735 --> 00:36:51.335
I don't think that I think the data

00:36:51.376 --> 00:36:52.717
collection in the first place is kind of

00:36:52.737 --> 00:36:54.858
the bar where a warrant should be

00:36:55.179 --> 00:36:55.699
required.

00:36:55.778 --> 00:36:58.101
It's not just when a government agent

00:36:58.820 --> 00:37:00.643
later tries to access and view that data

00:37:00.663 --> 00:37:01.822
should a warrant be required.

00:37:01.864 --> 00:37:04.704
So I think that stronger laws need to

00:37:04.724 --> 00:37:05.326
be in place

00:37:06.226 --> 00:37:09.228
for a variety for something like this,

00:37:09.289 --> 00:37:15.514
because my dog is being loud.

00:37:19.478 --> 00:37:20.458
I don't know where I was going with

00:37:20.478 --> 00:37:20.679
that.

00:37:20.798 --> 00:37:21.380
The point is,

00:37:21.519 --> 00:37:23.621
I think stronger warrant requirements

00:37:23.641 --> 00:37:26.744
should be in place just for this data

00:37:26.764 --> 00:37:27.925
collection to be happening in the first

00:37:27.965 --> 00:37:28.146
place.

00:37:28.166 --> 00:37:29.286
And we're not really seeing that right

00:37:29.327 --> 00:37:29.407
now.

00:37:30.699 --> 00:37:31.719
Yeah, no, totally agree.

00:37:31.880 --> 00:37:32.501
I just, like I said,

00:37:32.561 --> 00:37:33.541
I don't know if, you know, that,

00:37:33.641 --> 00:37:34.101
that thing,

00:37:34.141 --> 00:37:35.501
like they can only see the software

00:37:35.521 --> 00:37:36.322
version and device model.

00:37:36.342 --> 00:37:36.822
That's why I'm like,

00:37:36.922 --> 00:37:38.523
I don't know if that's a literal technical

00:37:38.563 --> 00:37:39.123
limitation.

00:37:39.182 --> 00:37:40.123
Like, no, no matter what,

00:37:40.182 --> 00:37:41.664
they can only see that with this tool.

00:37:42.043 --> 00:37:42.983
Or if it's like you said,

00:37:43.083 --> 00:37:43.463
is it a,

00:37:44.005 --> 00:37:45.764
a policy thing like flock where it's like,

00:37:45.784 --> 00:37:45.864
well,

00:37:45.885 --> 00:37:47.326
they're only supposed to look at that

00:37:47.365 --> 00:37:47.706
tool,

00:37:47.766 --> 00:37:49.547
but in theory they can access other stuff

00:37:49.567 --> 00:37:49.686
too.

00:37:49.706 --> 00:37:51.347
So I don't know.

00:37:51.447 --> 00:37:52.847
It's either way.

00:37:52.967 --> 00:37:53.887
I have mixed feelings about it.

00:37:54.568 --> 00:37:54.967
Not a fan.

00:37:55.128 --> 00:37:56.349
I'll be looking forward to Apple to patch

00:37:56.369 --> 00:37:56.449
it.

00:37:57.202 --> 00:37:58.804
Yeah, I'm looking for a comment here.

00:37:59.025 --> 00:38:00.527
I think it was, yeah, FoundDog said,

00:38:00.547 --> 00:38:01.849
I'm surprised Apple hasn't ditched the

00:38:01.929 --> 00:38:03.172
USB-C port entirely.

00:38:03.713 --> 00:38:04.454
I don't think that that...

00:38:05.692 --> 00:38:06.833
is going to well,

00:38:07.032 --> 00:38:08.393
the way that it's implemented is probably

00:38:08.414 --> 00:38:10.554
not going to help because I know Apple

00:38:10.574 --> 00:38:12.556
is going to want some sort of diagnostic

00:38:12.715 --> 00:38:13.956
way to access these devices,

00:38:13.976 --> 00:38:17.137
and that'll be just as useful as a

00:38:17.237 --> 00:38:17.998
USB-C port,

00:38:18.018 --> 00:38:22.001
especially to these well-funded companies

00:38:22.041 --> 00:38:23.661
like like Magnet and Craykey and

00:38:23.702 --> 00:38:24.702
Celebrate, for example.

00:38:25.302 --> 00:38:27.583
I know like on the Apple Watch,

00:38:27.844 --> 00:38:28.543
for example,

00:38:30.710 --> 00:38:32.273
There isn't a USB-C port, obviously,

00:38:32.313 --> 00:38:33.974
but they can still do some diagnostics in

00:38:33.994 --> 00:38:35.878
an Apple Store or if you send it

00:38:35.938 --> 00:38:36.077
in.

00:38:36.418 --> 00:38:37.639
On the original Apple Watches,

00:38:37.679 --> 00:38:40.284
it used to be like there was a

00:38:40.324 --> 00:38:41.505
hidden port you would need a special

00:38:41.525 --> 00:38:42.226
connector for.

00:38:42.726 --> 00:38:44.148
Nowadays, there isn't a hidden port.

00:38:44.208 --> 00:38:46.211
It's all wireless, but it's like a...

00:38:47.284 --> 00:38:49.485
They have like a sixty gigahertz wireless

00:38:49.505 --> 00:38:51.166
connection that they can do in the store

00:38:51.206 --> 00:38:54.489
to basically establish the same thing as a

00:38:54.708 --> 00:38:55.650
as a wired connection.

00:38:55.690 --> 00:38:57.190
And I would imagine that Apple would leave

00:38:57.231 --> 00:38:58.791
something like that in the iPhones that

00:38:58.811 --> 00:39:01.472
can be, in theory, accessed by only,

00:39:01.753 --> 00:39:03.074
you know, tools that Apple has.

00:39:03.135 --> 00:39:04.614
But if that is available,

00:39:04.655 --> 00:39:07.536
it wouldn't be that hard for a specialized

00:39:07.577 --> 00:39:09.478
company to develop a way to connect to

00:39:09.498 --> 00:39:11.159
that, even if, you know,

00:39:11.619 --> 00:39:13.722
that that connection point isn't available

00:39:13.782 --> 00:39:14.081
to Apple.

00:39:15.237 --> 00:39:17.257
mere mortals like us who just want to

00:39:17.277 --> 00:39:18.557
connect to our phone anymore.

00:39:19.418 --> 00:39:21.239
So I don't think that just going to

00:39:21.259 --> 00:39:23.179
a portless design is really going to help

00:39:23.199 --> 00:39:25.139
when it comes to when it comes to

00:39:25.179 --> 00:39:27.800
this problem, unfortunately.

00:39:27.880 --> 00:39:28.481
Yeah, what's funny,

00:39:29.902 --> 00:39:32.161
Apple seems to like I shouldn't be

00:39:32.202 --> 00:39:32.822
surprised by this,

00:39:33.182 --> 00:39:34.063
but they seem to be one of those

00:39:34.103 --> 00:39:35.503
companies that like when it when it

00:39:35.523 --> 00:39:36.744
benefits them, they're OK with it.

00:39:36.884 --> 00:39:38.284
I used to know somebody who worked for

00:39:38.443 --> 00:39:39.945
Apple for the the Genius Bar,

00:39:40.545 --> 00:39:42.505
and they said that they've actually used

00:39:42.545 --> 00:39:43.545
celebrate tools before.

00:39:44.351 --> 00:39:45.753
like in their job officially,

00:39:45.833 --> 00:39:47.934
like Apple has had celebrate tools in the

00:39:47.974 --> 00:39:48.315
past.

00:39:48.655 --> 00:39:49.876
I don't know how long ago this was.

00:39:49.916 --> 00:39:51.396
It was a while ago from what they

00:39:51.436 --> 00:39:51.697
told me,

00:39:51.737 --> 00:39:53.757
but like they used to use celebrate tools

00:39:53.898 --> 00:39:55.259
as part of their job to like,

00:39:55.298 --> 00:39:55.458
you know,

00:39:55.500 --> 00:39:56.920
help people recover data if they brought

00:39:56.960 --> 00:39:58.360
it into the genius bar or something.

00:39:58.460 --> 00:39:59.762
So it's, you know, I mean,

00:39:59.942 --> 00:40:00.983
fortunately they were doing it with

00:40:01.003 --> 00:40:02.563
consent, you know, like this is my iPhone,

00:40:02.603 --> 00:40:03.985
I'm broke, it's broken, whatever.

00:40:04.405 --> 00:40:05.585
But yeah, it's like, it's weird how like,

00:40:05.666 --> 00:40:05.925
okay,

00:40:05.945 --> 00:40:07.246
you're willing to use this when it

00:40:07.266 --> 00:40:08.827
benefits you and your employees.

00:40:09.469 --> 00:40:11.769
But I don't know, it's Apple's weird.

00:40:11.789 --> 00:40:12.431
They're a weird company.

00:40:15.954 --> 00:40:17.336
I did have a couple of questions I

00:40:17.376 --> 00:40:18.617
flagged while we were talking.

00:40:18.717 --> 00:40:19.059
One of them,

00:40:19.159 --> 00:40:20.239
I think this went back to our first

00:40:20.260 --> 00:40:20.641
story.

00:40:21.782 --> 00:40:22.362
Nick said,

00:40:22.402 --> 00:40:23.523
for those of us who are more tech

00:40:23.543 --> 00:40:25.126
savvy and wanna be more private online,

00:40:25.427 --> 00:40:26.347
where do we draw the line between

00:40:26.447 --> 00:40:28.090
self-hosting and self-creation?

00:40:29.831 --> 00:40:31.132
I think they're talking about making your

00:40:31.231 --> 00:40:33.572
own tools, but I'm not too sure.

00:40:33.612 --> 00:40:35.153
Do you have any thoughts on that one?

00:40:35.273 --> 00:40:35.494
I mean,

00:40:35.554 --> 00:40:37.876
certainly that's going to be more and more

00:40:37.916 --> 00:40:39.076
of a thing with AI.

00:40:39.115 --> 00:40:41.177
I think anyone can make their own tools

00:40:41.217 --> 00:40:41.697
these days.

00:40:43.358 --> 00:40:43.559
Yeah,

00:40:43.599 --> 00:40:47.561
I don't know exactly what you're asking.

00:40:47.581 --> 00:40:48.021
To be honest,

00:40:48.081 --> 00:40:50.882
I would need more clarification on what

00:40:50.922 --> 00:40:51.483
that means.

00:40:52.583 --> 00:40:54.043
But I think doing anything yourself is

00:40:54.063 --> 00:40:55.364
going to be an improvement over...

00:40:58.173 --> 00:41:00.315
again, using those centralized platforms.

00:41:00.335 --> 00:41:01.958
I think that that is kind of what

00:41:01.978 --> 00:41:03.280
has caused a lot of the issues with

00:41:03.320 --> 00:41:04.862
the Internet that we've now run into more

00:41:04.882 --> 00:41:07.244
than anything else.

00:41:07.284 --> 00:41:07.606
For sure.

00:41:08.387 --> 00:41:10.610
And username is Nye here said we should

00:41:10.630 --> 00:41:12.371
write an article about privacy fatigue.

00:41:12.751 --> 00:41:14.655
I feel like have we done that?

00:41:14.735 --> 00:41:15.876
I feel like we have in the past.

00:41:17.346 --> 00:41:19.467
um we certainly have we have some videos

00:41:19.487 --> 00:41:21.670
about that um i don't remember the exact

00:41:21.769 --> 00:41:23.471
title of it right now i could look

00:41:23.510 --> 00:41:25.271
but sometimes we change titles on things

00:41:25.353 --> 00:41:29.896
and yeah that's fun lose track of it

00:41:29.996 --> 00:41:32.458
okay because um i know i've written about

00:41:32.498 --> 00:41:33.980
it a little bit at my old blog

00:41:34.000 --> 00:41:35.541
on the new oil i've talked about burnout

00:41:35.940 --> 00:41:37.802
um not specifically privacy related but

00:41:37.842 --> 00:41:39.364
i've i've definitely talked about burnout

00:41:39.384 --> 00:41:43.086
for sure um i'm looking through some of

00:41:43.126 --> 00:41:45.329
our past articles here privacy washing

00:41:47.092 --> 00:41:49.974
Mastodon tutorial, dating apps.

00:41:50.954 --> 00:41:51.454
In the meantime,

00:41:51.514 --> 00:41:53.315
mixed by said self-dev work.

00:41:53.434 --> 00:41:56.175
I think in the self-hosting space,

00:41:57.056 --> 00:41:58.856
if there is something you can self-host

00:41:58.876 --> 00:42:01.237
that already does what you want it to

00:42:01.277 --> 00:42:04.257
do, I think standardizing on certain...

00:42:04.737 --> 00:42:05.657
Maybe not standardizing,

00:42:05.697 --> 00:42:09.159
but supporting existing implementations of

00:42:09.199 --> 00:42:10.800
things tends to be the better way to

00:42:10.840 --> 00:42:10.940
go.

00:42:13.661 --> 00:42:14.900
It's just easier for other people.

00:42:15.242 --> 00:42:16.961
You benefit from a community of software

00:42:16.981 --> 00:42:18.623
just as much as you benefit from a

00:42:18.663 --> 00:42:20.943
community using these self-hosted

00:42:20.963 --> 00:42:22.804
platforms to host discussions and stuff.

00:42:23.405 --> 00:42:25.644
And so if you're all on a similar

00:42:25.684 --> 00:42:27.306
platform, like Discourse, for example,

00:42:27.346 --> 00:42:29.246
there's a wide variety of plugins that you

00:42:29.266 --> 00:42:31.007
can install on the forum that make

00:42:31.086 --> 00:42:32.327
community management easier.

00:42:32.467 --> 00:42:35.389
And so using self-hosted tools like that,

00:42:35.449 --> 00:42:37.989
if you're trying to start a community that

00:42:38.110 --> 00:42:40.010
other people would use, is very helpful.

00:42:40.050 --> 00:42:40.710
And it's the same with

00:42:41.510 --> 00:42:42.711
like Mastodon, for example,

00:42:42.751 --> 00:42:44.213
I think a reason like a lot of

00:42:44.253 --> 00:42:45.853
the big public instances of these

00:42:45.873 --> 00:42:49.096
Fediverse platforms use Mastodon because

00:42:49.115 --> 00:42:53.217
it is really geared more towards larger

00:42:53.277 --> 00:42:54.119
public communities.

00:42:54.199 --> 00:42:57.121
And it has the largest ecosystem on the

00:42:57.161 --> 00:42:58.161
Fediverse, for example.

00:42:58.181 --> 00:43:00.021
And so you can get more support from

00:43:00.061 --> 00:43:01.402
it from other people if things are going

00:43:01.422 --> 00:43:01.643
wrong.

00:43:01.663 --> 00:43:03.103
And I think that that's important when

00:43:03.143 --> 00:43:04.304
you're when you're self hosting things.

00:43:06.623 --> 00:43:07.684
I used the search button and I did

00:43:07.724 --> 00:43:09.565
not find anything on our website.

00:43:09.605 --> 00:43:09.846
So yeah,

00:43:09.885 --> 00:43:11.326
we may have to add an article about

00:43:11.365 --> 00:43:12.347
that because that is definitely an

00:43:12.367 --> 00:43:13.586
important topic.

00:43:13.606 --> 00:43:15.327
I think we all get burned out from

00:43:15.387 --> 00:43:15.827
time to time.

00:43:16.208 --> 00:43:18.188
We definitely do have a video about

00:43:18.228 --> 00:43:21.971
privacy being like what if privacy feels

00:43:22.030 --> 00:43:22.931
overwhelming to you,

00:43:23.092 --> 00:43:24.192
strategies that you can do.

00:43:24.231 --> 00:43:25.833
For example, it's one of our first videos.

00:43:25.853 --> 00:43:26.952
So if you go back to the older

00:43:27.012 --> 00:43:27.673
ones, I think it's...

00:43:30.056 --> 00:43:30.958
Oh yeah, here it is on the list.

00:43:30.978 --> 00:43:32.338
It's just how privacy can stop being

00:43:32.418 --> 00:43:33.000
overwhelming.

00:43:34.101 --> 00:43:37.123
If you're looking for strategies on how to

00:43:37.184 --> 00:43:38.585
secure your digital life,

00:43:38.625 --> 00:43:42.108
if you're facing kind of burnout and

00:43:42.148 --> 00:43:42.509
stuff,

00:43:42.889 --> 00:43:44.871
it's a good place to start for sure.

00:43:46.860 --> 00:43:46.960
Yeah.

00:43:46.980 --> 00:43:48.260
And I think, um,

00:43:48.320 --> 00:43:49.380
I do actually really want to write this

00:43:49.440 --> 00:43:50.440
as an article now, so I'm not,

00:43:50.481 --> 00:43:51.840
I'm not going to dig too deep into

00:43:51.860 --> 00:43:53.342
it, but, um, I mean,

00:43:53.382 --> 00:43:54.681
just basic burnout strategies.

00:43:54.722 --> 00:43:56.061
Like, you know, we talked to Cindy Cohen,

00:43:56.501 --> 00:43:57.943
um, about how does she,

00:43:57.963 --> 00:43:59.702
cause she's been fighting for privacy in

00:43:59.762 --> 00:44:01.382
some form or another for like years.

00:44:01.963 --> 00:44:03.083
And I remember asking her, I'm like,

00:44:03.103 --> 00:44:04.063
how do you stay motivated?

00:44:04.103 --> 00:44:04.463
And she's like,

00:44:04.523 --> 00:44:06.485
I celebrate the little wins I have.

00:44:06.684 --> 00:44:06.804
Um,

00:44:06.844 --> 00:44:08.085
this is a big one personally is like,

00:44:08.465 --> 00:44:10.525
I have spaces that are not privacy spaces,

00:44:10.606 --> 00:44:11.706
like, especially, um,

00:44:12.594 --> 00:44:14.034
I don't wanna sound full of myself and

00:44:14.114 --> 00:44:16.155
I promise I'm not, but being Nate,

00:44:16.436 --> 00:44:18.817
I know I'm a bit of a well-known

00:44:18.836 --> 00:44:19.577
figure in the space,

00:44:20.257 --> 00:44:22.177
but outside of privacy, I'm nobody.

00:44:22.237 --> 00:44:23.659
Privacy is a very small space.

00:44:23.998 --> 00:44:25.000
And honestly, I love that.

00:44:25.099 --> 00:44:26.400
I love the fact that there are other

00:44:26.440 --> 00:44:28.481
spaces that I can step outside and I'm

00:44:28.521 --> 00:44:30.983
not this expert anymore that people are

00:44:31.003 --> 00:44:32.282
like, well, what's your opinion on this?

00:44:32.302 --> 00:44:32.523
It's like,

00:44:32.603 --> 00:44:33.963
I can have an opinion and nobody cares.

00:44:34.384 --> 00:44:36.045
because i'm just another normal person

00:44:36.065 --> 00:44:37.947
like everybody else and i think just

00:44:38.007 --> 00:44:39.568
having those spaces where you can go you

00:44:39.588 --> 00:44:40.909
know whether it's video games whether it's

00:44:40.969 --> 00:44:43.592
music whether it's um you know whatever it

00:44:43.632 --> 00:44:45.592
is camping i don't know like having things

00:44:45.612 --> 00:44:46.954
you can do where you can unplug and

00:44:46.994 --> 00:44:50.197
disconnect is really fantastic uh at least

00:44:50.237 --> 00:44:53.460
it is for me so anyways odd bite

00:44:53.539 --> 00:44:55.802
one of our biggest supporters welcome to

00:44:55.842 --> 00:44:56.762
the stream hello

00:44:59.349 --> 00:45:00.952
Yeah, as username is nice,

00:45:00.992 --> 00:45:02.416
I think calibrating one's threat model

00:45:02.456 --> 00:45:03.900
step by step is one way to stop

00:45:03.920 --> 00:45:04.280
being bored.

00:45:04.641 --> 00:45:07.447
I think that's definitely a good strategy

00:45:07.487 --> 00:45:08.009
because

00:45:09.849 --> 00:45:11.271
You do have to have a plan going

00:45:11.311 --> 00:45:13.231
into it of what's most important to you,

00:45:13.291 --> 00:45:14.532
where you have to start out.

00:45:15.634 --> 00:45:16.855
I think if you don't have a plan

00:45:16.875 --> 00:45:19.675
and it's just kind of an unstructured,

00:45:20.197 --> 00:45:21.197
try to secure everything,

00:45:21.217 --> 00:45:22.538
try to make everything as private as

00:45:22.597 --> 00:45:23.798
possible approach,

00:45:23.838 --> 00:45:25.239
you're just going to have way too much

00:45:25.280 --> 00:45:28.461
to deal with from the start.

00:45:30.222 --> 00:45:33.224
like on our website, the knowledge base,

00:45:33.244 --> 00:45:33.724
for example,

00:45:33.744 --> 00:45:35.105
we do have a list of like common

00:45:35.125 --> 00:45:36.186
threats that people face,

00:45:36.226 --> 00:45:37.387
and maybe those aren't the things that

00:45:37.407 --> 00:45:38.186
you're concerned about.

00:45:38.226 --> 00:45:38.827
Maybe they are,

00:45:38.867 --> 00:45:40.228
but it could give you a starting off

00:45:40.248 --> 00:45:41.708
point or an idea of like, oh,

00:45:41.728 --> 00:45:43.989
I never thought about this issue before,

00:45:44.030 --> 00:45:45.190
but maybe I'm concerned about it.

00:45:45.269 --> 00:45:47.110
Or it could help you narrow down like

00:45:47.371 --> 00:45:49.152
which of these things on the list you're

00:45:49.211 --> 00:45:50.092
most concerned about,

00:45:50.132 --> 00:45:51.534
and then you can focus on it from

00:45:51.793 --> 00:45:52.253
from there.

00:45:52.313 --> 00:45:54.014
I think that definitely makes things a lot

00:45:54.094 --> 00:45:54.375
easier,

00:45:54.394 --> 00:45:55.474
which is why we talk about

00:45:56.675 --> 00:45:59.338
threat modeling all the time instead of

00:45:59.378 --> 00:46:01.599
just doing everything you can because you

00:46:01.639 --> 00:46:05.123
can um it's just a more sustainable way

00:46:05.204 --> 00:46:06.605
to to do things and i think you

00:46:06.644 --> 00:46:08.407
can also it helps you be a lot

00:46:08.447 --> 00:46:11.568
more thorough uh because you can kind of

00:46:11.608 --> 00:46:13.411
set goals for yourself and evaluate how

00:46:13.451 --> 00:46:15.193
you're doing and stuff like that which i

00:46:15.213 --> 00:46:16.653
think helps a lot of people as well

00:46:18.260 --> 00:46:19.059
Yeah, I was going to say,

00:46:19.940 --> 00:46:21.201
I think a lot of the burnout I

00:46:21.240 --> 00:46:21.442
see,

00:46:21.501 --> 00:46:22.742
like there's definitely the burnout of

00:46:22.762 --> 00:46:23.362
just like, you know,

00:46:23.623 --> 00:46:25.043
I've been in the privacy space for years

00:46:25.063 --> 00:46:26.284
and it feels like we're always losing,

00:46:26.804 --> 00:46:27.403
which is not true,

00:46:27.423 --> 00:46:28.644
but it can feel that way sometimes.

00:46:29.405 --> 00:46:30.425
I think there's a difference between that.

00:46:30.686 --> 00:46:31.927
The one I see most often is what

00:46:31.947 --> 00:46:33.007
you were just saying is like somebody is

00:46:33.047 --> 00:46:35.168
trying to do everything and they're just

00:46:35.327 --> 00:46:36.889
overwhelmed by like, oh, cool.

00:46:36.929 --> 00:46:39.349
Now there's this new my neighbor's Wi-Fi

00:46:39.369 --> 00:46:41.490
can sense my position because of this new

00:46:41.570 --> 00:46:42.351
attack or whatever.

00:46:42.371 --> 00:46:42.751
And it's like.

00:46:43.132 --> 00:46:43.512
Like you said,

00:46:43.532 --> 00:46:44.873
like stepping back and being like, OK,

00:46:44.913 --> 00:46:46.012
what's my actual threat model?

00:46:46.032 --> 00:46:47.414
What am I really trying to defend against?

00:46:47.454 --> 00:46:48.494
What don't I care about?

00:46:48.974 --> 00:46:50.215
And what's like realistic, you know,

00:46:50.235 --> 00:46:52.657
like it's yeah, I think personally,

00:46:52.757 --> 00:46:55.117
I do think people should go as far

00:46:55.157 --> 00:46:56.639
as they can to protect their privacy.

00:46:56.978 --> 00:46:58.298
But there does hit a point where,

00:46:58.619 --> 00:46:58.880
you know,

00:46:59.019 --> 00:47:00.320
it starts to become a lot of work

00:47:00.420 --> 00:47:01.340
and you have to ask yourself, like,

00:47:01.400 --> 00:47:02.041
what am I getting?

00:47:02.561 --> 00:47:03.181
What am I gaining?

00:47:03.242 --> 00:47:04.021
What am I losing?

00:47:04.141 --> 00:47:04.262
Like,

00:47:04.282 --> 00:47:06.663
is this really worth it once I'm going

00:47:07.023 --> 00:47:07.983
beyond the minimum?

00:47:08.043 --> 00:47:09.105
And but you don't know that if you

00:47:09.144 --> 00:47:10.224
don't know where the minimum is,

00:47:10.344 --> 00:47:11.166
which is the threat model.

00:47:11.226 --> 00:47:11.346
So

00:47:11.987 --> 00:47:13.197
Yeah, it's important.

00:47:13.688 --> 00:47:15.289
I'm going to have to briefly remind

00:47:15.409 --> 00:47:17.530
Oddbite that if you opt into sharing your

00:47:17.550 --> 00:47:18.951
membership status on the forum,

00:47:18.990 --> 00:47:20.811
that's going to be publicly available on

00:47:20.871 --> 00:47:21.532
our website.

00:47:21.612 --> 00:47:23.233
I think we have a list of members.

00:47:24.173 --> 00:47:26.054
And if you opt into sharing that publicly,

00:47:26.175 --> 00:47:27.514
we include the list of members at the

00:47:27.554 --> 00:47:30.137
end of videos now to thank people.

00:47:31.556 --> 00:47:32.597
Definitely want to highlight all the

00:47:32.637 --> 00:47:33.918
people supporting us.

00:47:34.378 --> 00:47:37.059
Of course, this could be an impersonator.

00:47:37.139 --> 00:47:38.599
Who knows if you're the real Oddbite,

00:47:38.659 --> 00:47:38.900
but...

00:47:42.481 --> 00:47:43.543
Um, again,

00:47:43.563 --> 00:47:44.603
we won't spend too long on this,

00:47:44.623 --> 00:47:45.826
but yeah, one person said, uh,

00:47:46.005 --> 00:47:47.748
doing things in phases and set a cap

00:47:47.768 --> 00:47:48.789
for how much is on my plate.

00:47:49.289 --> 00:47:51.231
Um, yeah, doing things in steps for sure.

00:47:52.112 --> 00:47:54.273
Um, not trying to do everything at once.

00:47:55.235 --> 00:47:55.494
Uh,

00:47:55.576 --> 00:47:57.317
what's this one compartmentalization with

00:47:57.356 --> 00:47:59.139
identities for sure.

00:47:59.179 --> 00:48:00.099
So, yeah, I mean,

00:48:00.119 --> 00:48:01.101
there's a lot of stuff out there.

00:48:01.380 --> 00:48:01.842
Maybe, uh,

00:48:03.481 --> 00:48:04.143
Yeah,

00:48:04.182 --> 00:48:05.202
I think there's some interest in this.

00:48:05.282 --> 00:48:07.525
We should talk about this some more in

00:48:07.545 --> 00:48:07.985
the future.

00:48:08.065 --> 00:48:09.567
But for now,

00:48:09.626 --> 00:48:10.746
I think I'm going to turn it over

00:48:10.766 --> 00:48:12.949
to you to go over our first forum

00:48:12.989 --> 00:48:14.469
post here that we wanted to highlight,

00:48:14.530 --> 00:48:15.990
which I think is just kind of a

00:48:16.070 --> 00:48:17.351
signal boost about Chat Control

00:48:19.179 --> 00:48:20.360
Yeah, just an update.

00:48:20.860 --> 00:48:21.961
Somebody posted here.

00:48:22.001 --> 00:48:25.585
There's always chat control stuff going

00:48:25.644 --> 00:48:26.405
on, I feel like.

00:48:27.385 --> 00:48:28.047
Patrick Breyer,

00:48:28.106 --> 00:48:30.469
who's a former MEP with the Pirate Party

00:48:30.688 --> 00:48:32.291
and current, of course,

00:48:32.331 --> 00:48:33.472
digital freedom activist,

00:48:33.532 --> 00:48:35.813
posted about the upcoming sixth...

00:48:36.373 --> 00:48:38.094
Trilog on ChatControl.

00:48:38.375 --> 00:48:42.275
The Trilog negotiates extent of the later

00:48:42.315 --> 00:48:42.876
proposal, which,

00:48:42.916 --> 00:48:44.297
according to a leaked document,

00:48:44.376 --> 00:48:46.338
is said to now include a workaround to

00:48:46.398 --> 00:48:49.099
deploy a mass scanning by allowing

00:48:49.259 --> 00:48:51.920
scanning of parts of a service in search

00:48:51.960 --> 00:48:52.239
plans,

00:48:52.260 --> 00:48:54.481
which Breyer calls mass surveillance by

00:48:54.521 --> 00:48:55.101
another name.

00:48:55.802 --> 00:48:58.342
The council's own legal service says such

00:48:58.443 --> 00:49:00.503
framing would not hold up in judicial

00:49:00.583 --> 00:49:01.003
review.

00:49:01.744 --> 00:49:03.045
This is likely due to targeted

00:49:04.045 --> 00:49:06.126
targeted being reframed as parts of a

00:49:06.166 --> 00:49:08.347
service instead of a person.

00:49:10.409 --> 00:49:12.550
So what information do we have here?

00:49:12.590 --> 00:49:12.891
Of course,

00:49:12.911 --> 00:49:15.393
you can always go to fightchatcontrol.eu.

00:49:17.255 --> 00:49:18.896
You can go to fightchatcontrol.eu

00:49:20.947 --> 00:49:22.668
hound sign, delegates,

00:49:23.628 --> 00:49:25.110
or find the delegates section on that

00:49:25.190 --> 00:49:25.471
site.

00:49:25.690 --> 00:49:27.632
You can set the filter to EP Trilog

00:49:27.652 --> 00:49:28.994
Shadows and you can see all eight

00:49:29.054 --> 00:49:30.335
responsible MEPs.

00:49:31.115 --> 00:49:33.898
If you're in the EU and you are

00:49:33.938 --> 00:49:35.900
represented by these people at all,

00:49:37.702 --> 00:49:40.324
definitely worth voicing your support.

00:49:40.403 --> 00:49:40.603
I mean,

00:49:40.643 --> 00:49:43.045
this is the kind of thing where for

00:49:43.106 --> 00:49:43.686
some reason,

00:49:44.126 --> 00:49:45.547
all of these track control measures are

00:49:45.567 --> 00:49:47.829
just a constant fight in the EU.

00:49:48.688 --> 00:49:50.771
Seemingly, it'll never end and hopefully

00:49:52.224 --> 00:49:53.525
all of you in the EU can get

00:49:53.545 --> 00:49:56.146
your act together and pass some law that

00:49:56.186 --> 00:49:57.467
prevents this from happening.

00:49:57.507 --> 00:49:58.809
So it doesn't just have to come up

00:49:58.929 --> 00:49:59.409
all the time.

00:49:59.449 --> 00:50:03.311
But that's really going to come down to

00:50:03.851 --> 00:50:05.713
getting your representatives to do what

00:50:05.733 --> 00:50:08.054
you want, which is always challenging.

00:50:09.614 --> 00:50:10.076
So yeah,

00:50:10.396 --> 00:50:12.876
were there any replies to this post that

00:50:12.896 --> 00:50:13.938
you wanted to highlight, Nate?

00:50:16.552 --> 00:50:16.934
Yeah,

00:50:17.635 --> 00:50:20.641
Chat Control is definitely like a terrible

00:50:20.902 --> 00:50:22.626
movie franchise that just will not die.

00:50:23.943 --> 00:50:24.083
Yeah,

00:50:24.103 --> 00:50:26.365
there was one here somewhere from another

00:50:26.505 --> 00:50:26.905
user said,

00:50:26.945 --> 00:50:28.407
don't forget that Canada has its own chat

00:50:28.447 --> 00:50:30.347
control in the form of Bill C-Twenty-Two.

00:50:31.248 --> 00:50:31.909
So if you're Canadian,

00:50:31.949 --> 00:50:33.148
definitely keep that on your radar.

00:50:33.630 --> 00:50:35.110
This other person actually commented

00:50:35.130 --> 00:50:35.351
about,

00:50:35.471 --> 00:50:37.271
I know there's been some talk about Canada

00:50:37.311 --> 00:50:39.373
becoming an EU associate member,

00:50:39.853 --> 00:50:41.293
which is not a thing that currently

00:50:41.353 --> 00:50:41.673
exists.

00:50:41.693 --> 00:50:42.914
So nobody even really knows what that

00:50:42.954 --> 00:50:43.275
means.

00:50:43.355 --> 00:50:45.496
But they did point out that if that

00:50:45.556 --> 00:50:46.336
does go through,

00:50:46.496 --> 00:50:49.998
that it might like pressure Canada to,

00:50:51.378 --> 00:50:52.639
Play by similar, what'd they say?

00:50:53.139 --> 00:50:54.760
More like an obligation to play by rules

00:50:54.800 --> 00:50:57.081
by similar demand or by popular demand.

00:50:57.161 --> 00:50:58.802
So yeah,

00:50:58.862 --> 00:51:00.061
definitely stuff to keep an eye on.

00:51:00.202 --> 00:51:01.902
And there was actually a video down here.

00:51:02.802 --> 00:51:04.322
I think Freya shared it in the chat

00:51:04.402 --> 00:51:07.603
where it's not chat controlled directly,

00:51:08.244 --> 00:51:09.664
but apparently there's this similar

00:51:09.704 --> 00:51:11.945
proposal called the EU Kids Act.

00:51:12.936 --> 00:51:15.940
And the Stop Killing Games movement posted

00:51:15.960 --> 00:51:18.541
a video where they basically talked about

00:51:18.603 --> 00:51:18.882
how, like,

00:51:19.182 --> 00:51:20.545
there's a whole bunch of things to it.

00:51:20.905 --> 00:51:22.065
But one of the things I remembered is

00:51:22.106 --> 00:51:23.788
it would basically make it illegal to

00:51:23.887 --> 00:51:24.789
self-host games.

00:51:24.809 --> 00:51:24.949
Like,

00:51:24.969 --> 00:51:26.351
if you self-host your own Minecraft

00:51:26.371 --> 00:51:26.672
server,

00:51:27.012 --> 00:51:28.454
that would effectively become illegal.

00:51:29.253 --> 00:51:31.396
And it's just, it's wild.

00:51:31.476 --> 00:51:32.637
So, yeah, things are...

00:51:33.438 --> 00:51:34.599
in a tough spot right now.

00:51:34.760 --> 00:51:36.740
I will end by saying this person updated

00:51:36.760 --> 00:51:37.981
their post and said that for now,

00:51:38.021 --> 00:51:39.641
the plan to work around the targeting

00:51:39.663 --> 00:51:40.842
limitation has been blocked.

00:51:42.023 --> 00:51:43.103
But again,

00:51:43.143 --> 00:51:44.885
there may be a seventh trial log in

00:51:44.905 --> 00:51:45.766
November, possibly.

00:51:45.865 --> 00:51:47.367
So, yeah, if you're in Canada,

00:51:47.387 --> 00:51:48.186
if you're in the EU,

00:51:48.927 --> 00:51:50.268
I would say go ahead and follow this

00:51:50.447 --> 00:51:53.849
this forum post so that you get updates

00:51:54.110 --> 00:51:55.831
and just, yeah,

00:51:55.851 --> 00:51:56.931
try to keep updated with this stuff.

00:51:56.972 --> 00:51:57.592
I know it's a lot.

00:51:58.092 --> 00:51:59.112
We were just talking about burnout.

00:51:59.193 --> 00:52:01.114
It's a lot, but unfortunately,

00:52:01.134 --> 00:52:01.755
it's important stuff.

00:52:03.057 --> 00:52:03.858
Username is Nye.

00:52:03.938 --> 00:52:05.320
I want to know more details about this

00:52:05.380 --> 00:52:06.001
Jonah act.

00:52:06.681 --> 00:52:07.503
That's what I was going to say.

00:52:07.563 --> 00:52:08.625
I saw that.

00:52:08.744 --> 00:52:09.885
What is the Jonah act?

00:52:11.568 --> 00:52:12.708
Two chat, two control.

00:52:14.170 --> 00:52:14.451
Love it.

00:52:16.813 --> 00:52:17.114
Yeah,

00:52:17.135 --> 00:52:18.596
so I think that's all we got on

00:52:18.615 --> 00:52:18.976
that one.

00:52:19.117 --> 00:52:21.338
I think now we can move on to

00:52:21.400 --> 00:52:21.519
the

00:52:22.119 --> 00:52:22.880
site updates.

00:52:23.199 --> 00:52:24.340
I guess I'll kick this one off.

00:52:25.320 --> 00:52:25.940
In a little bit,

00:52:26.041 --> 00:52:27.860
we're going to be talking about a new

00:52:27.902 --> 00:52:29.581
attack that can track you regardless of

00:52:29.601 --> 00:52:32.503
what operating system you use and does not

00:52:32.543 --> 00:52:34.262
require administrative privileges,

00:52:34.282 --> 00:52:34.663
by the way.

00:52:34.702 --> 00:52:36.003
But first, like I said,

00:52:36.023 --> 00:52:37.164
we're going to do some site updates.

00:52:39.003 --> 00:52:41.945
Yeah, like I mentioned, we did, well,

00:52:41.985 --> 00:52:45.505
we put out a video last week about

00:52:46.313 --> 00:52:47.094
My brain is blanking.

00:52:47.996 --> 00:52:50.018
The twenty sixteen San Bernardino shooting

00:52:50.257 --> 00:52:53.681
and the fight that followed between Apple

00:52:53.702 --> 00:52:54.362
and the FBI,

00:52:54.382 --> 00:52:55.963
with the FBI trying to pressure Apple to

00:52:56.023 --> 00:52:57.365
unlock it and Apple saying no.

00:52:57.925 --> 00:53:00.208
And that one got I think it's now

00:53:00.228 --> 00:53:01.909
got over a million views on YouTube,

00:53:01.989 --> 00:53:02.170
which

00:53:02.731 --> 00:53:03.851
i don't want to downplay it but i

00:53:03.871 --> 00:53:05.692
will say um youtube changed the way they

00:53:05.731 --> 00:53:06.992
count views now so it's more like a

00:53:07.032 --> 00:53:08.893
million clicks than a million views but

00:53:08.932 --> 00:53:10.373
even so it's got i think half a

00:53:10.393 --> 00:53:12.072
million what they call engaged views which

00:53:12.112 --> 00:53:13.574
is what we used to know as views

00:53:14.054 --> 00:53:15.914
so um like half a million real views

00:53:15.974 --> 00:53:18.534
which is pretty amazing um definitely the

00:53:18.574 --> 00:53:21.795
most viral i've ever any video i've ever

00:53:21.835 --> 00:53:24.056
worked on so super proud of that but

00:53:24.597 --> 00:53:25.456
yeah this week um

00:53:26.416 --> 00:53:26.976
Lewis Rossman,

00:53:26.996 --> 00:53:28.277
a lot of you guys probably saw,

00:53:28.338 --> 00:53:29.757
posted a video where he revoked his

00:53:29.777 --> 00:53:30.938
endorsement of Privacy.com.

00:53:31.599 --> 00:53:33.838
And for any of you who haven't seen

00:53:33.858 --> 00:53:35.260
this video, I've met Lewis.

00:53:35.460 --> 00:53:36.619
I consider him a friend.

00:53:36.659 --> 00:53:37.460
He's a really cool guy.

00:53:38.061 --> 00:53:40.461
And I didn't disagree with him,

00:53:40.521 --> 00:53:41.681
but I remember sitting here and thinking,

00:53:41.722 --> 00:53:43.222
like, while I'm watching his video,

00:53:43.262 --> 00:53:44.322
I'm like, okay, so what's...

00:53:45.023 --> 00:53:45.922
What's the alternative?

00:53:46.182 --> 00:53:48.744
Every service is going to KYC you.

00:53:49.204 --> 00:53:49.963
And I just thought it was part of

00:53:50.123 --> 00:53:50.925
a bigger discussion.

00:53:51.184 --> 00:53:52.364
And so I kind of pitched it to

00:53:52.385 --> 00:53:52.625
Jonah.

00:53:52.664 --> 00:53:53.965
I kind of expected Jonah to say no,

00:53:54.204 --> 00:53:54.664
to be honest.

00:53:55.085 --> 00:53:55.626
But I was like, hey,

00:53:55.646 --> 00:53:56.525
what if we make this video?

00:53:56.606 --> 00:53:57.786
And he was like, yeah, let's do it.

00:53:58.286 --> 00:54:00.447
So we whipped that up pretty quick and

00:54:00.706 --> 00:54:01.266
posted that.

00:54:01.447 --> 00:54:03.208
And that is now available.

00:54:03.288 --> 00:54:05.467
And it has not gone as viral,

00:54:05.487 --> 00:54:06.668
but it's definitely gotten a ton of

00:54:06.708 --> 00:54:07.648
discussion in the comments.

00:54:10.530 --> 00:54:11.710
I feel like that's an issue that comes

00:54:11.751 --> 00:54:15.271
up a lot with maybe idealists in the

00:54:15.311 --> 00:54:16.313
privacy space.

00:54:17.193 --> 00:54:19.434
We see it especially in cybersecurity

00:54:19.494 --> 00:54:22.476
where I think people can let perfect be

00:54:22.516 --> 00:54:23.335
the enemy of the good.

00:54:24.617 --> 00:54:26.077
As long as you know the downsides of

00:54:26.097 --> 00:54:26.338
things,

00:54:26.358 --> 00:54:27.599
a lot of tools do have

00:54:28.643 --> 00:54:30.744
aspects of them that can help your privacy

00:54:30.764 --> 00:54:31.485
in meaningful ways.

00:54:31.545 --> 00:54:33.344
And I think Privacy.com is one of them.

00:54:34.206 --> 00:54:36.226
Of course, there are alternatives to that.

00:54:36.266 --> 00:54:38.186
And so if you disagree with the specific

00:54:38.226 --> 00:54:40.286
provider that Privacy.com is using,

00:54:40.306 --> 00:54:43.487
you can switch to my pseudo or another

00:54:43.507 --> 00:54:44.447
provider that's similar,

00:54:44.527 --> 00:54:46.829
or you can switch to prepaid debit cards.

00:54:46.849 --> 00:54:48.730
There's a lot of those which you can

00:54:48.929 --> 00:54:50.849
obtain completely anonymously.

00:54:51.130 --> 00:54:52.791
Right now, all the virtual card services,

00:54:52.831 --> 00:54:54.530
they do KYC in a similar manner.

00:54:54.570 --> 00:54:55.952
They just use different companies, but

00:54:57.898 --> 00:54:59.719
But those prepaid cards can or gift cards

00:54:59.739 --> 00:55:01.682
could be obtained with cryptocurrency or

00:55:01.722 --> 00:55:02.164
cash.

00:55:02.204 --> 00:55:03.405
And so that's always an option.

00:55:03.726 --> 00:55:04.166
But I think

00:55:05.548 --> 00:55:05.809
Yeah,

00:55:05.969 --> 00:55:08.030
as long as you understand you're giving up

00:55:08.070 --> 00:55:11.213
some privacy in some respect when you're

00:55:11.273 --> 00:55:13.434
using privacy.com, which is unfortunate.

00:55:13.554 --> 00:55:15.396
I've never liked the name of this

00:55:15.436 --> 00:55:17.157
privacy.com service because I think that

00:55:17.237 --> 00:55:18.778
is a little misleading.

00:55:18.818 --> 00:55:19.659
But at the same time,

00:55:20.739 --> 00:55:22.461
being able to use a different card number

00:55:22.782 --> 00:55:23.983
on every site that you use,

00:55:24.023 --> 00:55:26.023
it has security benefits for sure because

00:55:26.043 --> 00:55:27.224
you can disable those cards.

00:55:27.264 --> 00:55:29.527
And it also has privacy benefits

00:55:29.567 --> 00:55:30.047
because...

00:55:30.967 --> 00:55:33.429
uh merchants can't track you based on your

00:55:33.530 --> 00:55:36.333
billing information or like two websites

00:55:36.373 --> 00:55:37.954
can't collaborate and share their

00:55:37.974 --> 00:55:39.996
databases and link your accounts because

00:55:40.016 --> 00:55:42.378
you can use not only different card

00:55:42.418 --> 00:55:43.938
numbers but you can use different billing

00:55:43.978 --> 00:55:45.800
addresses or whatever you want with

00:55:45.820 --> 00:55:47.782
privacy.com it doesn't get checked on

00:55:47.822 --> 00:55:52.847
those cards so they're like it sucks that

00:55:52.867 --> 00:55:54.768
they're doing this uh it's very annoying

00:55:54.789 --> 00:55:56.949
but at the same time if you want

00:55:56.990 --> 00:55:58.070
those privacy benefits

00:55:59.045 --> 00:55:59.865
in a different respect,

00:55:59.885 --> 00:56:01.166
you also don't have a lot of options.

00:56:01.266 --> 00:56:04.670
But I do think privacy.com should stop

00:56:04.710 --> 00:56:05.050
doing that.

00:56:05.090 --> 00:56:06.150
And I think that if you do use

00:56:06.210 --> 00:56:07.592
privacy.com right now,

00:56:07.672 --> 00:56:10.054
you should write to them and complain.

00:56:10.353 --> 00:56:11.454
I don't use privacy.com.

00:56:11.514 --> 00:56:11.936
Personally,

00:56:12.056 --> 00:56:14.597
I use virtual cards from my bank,

00:56:16.018 --> 00:56:17.199
which I think is the more convenient

00:56:17.260 --> 00:56:18.400
option if you have that option.

00:56:18.460 --> 00:56:19.442
But yeah,

00:56:20.682 --> 00:56:21.222
Yeah, for sure.

00:56:21.724 --> 00:56:23.065
And for the record, again,

00:56:23.105 --> 00:56:24.126
if anybody hasn't seen the video,

00:56:24.206 --> 00:56:25.447
we said all this in the video.

00:56:25.507 --> 00:56:26.668
Like I even said at one point,

00:56:26.688 --> 00:56:28.829
I'm like, look, I think at bare minimum,

00:56:28.909 --> 00:56:30.391
Privacy.com could have gone with a

00:56:30.431 --> 00:56:31.871
different provider that's not funded by

00:56:31.911 --> 00:56:32.492
Peter Thiel.

00:56:33.994 --> 00:56:35.014
Did you see the comment that said I

00:56:35.034 --> 00:56:36.496
was defending Peter Thiel somehow?

00:56:39.117 --> 00:56:40.278
I stared at that one for a minute.

00:56:40.318 --> 00:56:40.978
I'm like, what?

00:56:41.119 --> 00:56:41.480
Where?

00:56:42.539 --> 00:56:43.780
But yeah, anyways.

00:56:44.360 --> 00:56:44.581
Yeah.

00:56:44.621 --> 00:56:45.922
So, I mean, we, we said that like,

00:56:45.961 --> 00:56:47.402
look, they, they should do better.

00:56:47.523 --> 00:56:48.903
There's probably providers who are

00:56:48.943 --> 00:56:50.985
slightly better, but they're not all like,

00:56:51.005 --> 00:56:52.567
there is no provider that's like, oh,

00:56:52.847 --> 00:56:53.447
this one's great.

00:56:53.467 --> 00:56:54.387
And they should have gone with them.

00:56:54.427 --> 00:56:56.409
It's like, yeah, there's a lesser evil,

00:56:56.449 --> 00:56:57.309
but not by much.

00:56:57.369 --> 00:56:57.931
And yeah,

00:56:57.971 --> 00:56:59.190
we did go over some of the alternatives,

00:56:59.210 --> 00:56:59.871
like you mentioned.

00:56:59.891 --> 00:57:01.432
And yeah, I don't know.

00:57:01.612 --> 00:57:02.172
Anyways, that's,

00:57:02.273 --> 00:57:03.153
that's a video that's out there.

00:57:03.173 --> 00:57:05.155
If y'all want to check that out.

00:57:06.016 --> 00:57:06.576
I think on that note,

00:57:06.615 --> 00:57:07.896
I will turn it over to Jonah to

00:57:07.976 --> 00:57:10.099
discuss any site changes that are coming

00:57:10.139 --> 00:57:10.259
up.

00:57:10.699 --> 00:57:12.641
Yeah, there's some minor updates.

00:57:13.262 --> 00:57:13.802
As usual,

00:57:13.842 --> 00:57:15.425
people keep plugging away at pull requests

00:57:15.465 --> 00:57:15.905
on the site.

00:57:16.226 --> 00:57:18.068
And if you have any suggestions or want

00:57:18.088 --> 00:57:18.989
to add new content,

00:57:19.048 --> 00:57:23.432
we always accept that stuff on on GitHub.

00:57:23.914 --> 00:57:28.038
We have some changes revising the guidance

00:57:28.077 --> 00:57:30.519
we have for Android app installation.

00:57:31.501 --> 00:57:32.583
We have some changes to

00:57:34.400 --> 00:57:35.922
We have some improvements to our Tor

00:57:35.981 --> 00:57:37.422
interview and how we changed that,

00:57:37.442 --> 00:57:39.422
and we changed our custom domain

00:57:39.463 --> 00:57:42.164
requirement for email services again.

00:57:43.704 --> 00:57:45.585
This is all based on forum discussions

00:57:45.626 --> 00:57:46.045
that we have,

00:57:46.106 --> 00:57:47.447
so if you want to get involved,

00:57:47.467 --> 00:57:49.248
you can either create a pull request based

00:57:49.367 --> 00:57:51.449
on discussions that you've seen on the

00:57:51.509 --> 00:57:53.068
forum that people generally agree on,

00:57:53.190 --> 00:57:54.090
or if you want to make a change,

00:57:54.110 --> 00:57:55.610
you can open a discussion on the forum

00:57:56.010 --> 00:57:57.552
at discuss.privacyguides.net.

00:57:57.572 --> 00:58:00.233
That's the best way to contribute to our

00:58:00.273 --> 00:58:01.552
shared knowledge base,

00:58:01.592 --> 00:58:02.494
and we can hopefully get

00:58:03.213 --> 00:58:05.373
the best privacy information we can out

00:58:05.393 --> 00:58:05.614
there.

00:58:06.494 --> 00:58:07.034
Of course,

00:58:07.215 --> 00:58:11.275
Freya and others constantly work on news

00:58:11.315 --> 00:58:13.675
briefs that we post to privacyguides.org

00:58:13.735 --> 00:58:14.755
slash news.

00:58:15.157 --> 00:58:17.677
These come up very regularly and they

00:58:17.717 --> 00:58:19.117
cover a lot of news topics,

00:58:19.157 --> 00:58:22.838
especially ones that we can't cover on the

00:58:22.858 --> 00:58:24.938
show because we do a lot of discussion

00:58:24.978 --> 00:58:25.338
on the show.

00:58:25.378 --> 00:58:26.039
Of course, we can't

00:58:26.739 --> 00:58:28.000
We can't cover every news story.

00:58:28.679 --> 00:58:30.101
Some of the headlines from this week.

00:58:30.561 --> 00:58:32.563
Critical Tor vulnerabilities were patched

00:58:32.603 --> 00:58:35.543
across all Tor components from the LLM

00:58:35.585 --> 00:58:36.945
report firehose.

00:58:37.385 --> 00:58:39.327
New technique was discovered for breaking

00:58:39.487 --> 00:58:40.907
RSA faster than ever before.

00:58:41.288 --> 00:58:43.168
Meta promises to upgrade Ray-Ban smart

00:58:43.188 --> 00:58:45.130
glasses with private processing.

00:58:45.570 --> 00:58:46.231
Whatever that means,

00:58:46.251 --> 00:58:47.431
you'll have to read the article to find

00:58:47.512 --> 00:58:47.612
out.

00:58:48.231 --> 00:58:50.373
um highly sensitive data of three million

00:58:50.414 --> 00:58:52.295
people in the pentagon system were

00:58:52.394 --> 00:58:55.237
accessed by unauthorized users and german

00:58:55.277 --> 00:58:57.358
police are using linked devices to read

00:58:57.697 --> 00:58:59.300
messages from messaging apps without

00:58:59.360 --> 00:59:01.561
cracking the encryption which i believe

00:59:01.860 --> 00:59:03.342
we've talked about a similar story on the

00:59:03.362 --> 00:59:07.905
show before um of course every week nate

00:59:07.985 --> 00:59:10.567
also publishes the data breach roundup to

00:59:10.606 --> 00:59:13.748
this same page privacyguides.org news you

00:59:13.768 --> 00:59:15.650
can also subscribe to it as a newsletter

00:59:16.451 --> 00:59:17.592
but there's just constantly

00:59:18.331 --> 00:59:20.233
data breaches happening all the time.

00:59:21.034 --> 00:59:22.414
And it's kind of just a way to

00:59:23.135 --> 00:59:24.295
show how often it happens,

00:59:24.335 --> 00:59:25.775
because I think people wouldn't believe

00:59:25.815 --> 00:59:28.117
how often these companies get hacked.

00:59:28.177 --> 00:59:29.498
So yeah,

00:59:29.918 --> 00:59:31.239
if you want to either be aware of

00:59:31.278 --> 00:59:31.518
that,

00:59:31.659 --> 00:59:33.219
or if you just want to see how

00:59:33.280 --> 00:59:33.960
often it happens,

00:59:33.980 --> 00:59:35.300
that's a good resource to check out.

00:59:37.342 --> 00:59:38.864
Yeah, all of the stuff that we publish,

00:59:39.105 --> 00:59:40.367
all the stuff that I talked about and

00:59:40.447 --> 00:59:42.068
the videos that Nate talked about,

00:59:42.148 --> 00:59:43.690
all of it's made possible by our

00:59:44.110 --> 00:59:44.652
supporters.

00:59:44.751 --> 00:59:46.014
You can sign up for a membership or

00:59:46.034 --> 00:59:48.115
you can donate at privacyguides.org slash

00:59:48.175 --> 00:59:48.516
donate.

00:59:48.757 --> 00:59:50.358
You can also pick up some swag at

00:59:50.378 --> 00:59:52.141
shop.privacyguides.org if you like.

00:59:53.081 --> 00:59:55.163
At Privacy Guides, we are a nonprofit.

00:59:55.222 --> 00:59:57.485
We research and share privacy-related

00:59:57.545 --> 00:59:58.065
information,

00:59:58.425 --> 01:00:00.447
and we facilitate a community on our forum

01:00:00.507 --> 01:00:02.668
and matrix and these other platforms like

01:00:02.688 --> 01:00:03.989
here on YouTube where people can ask

01:00:04.028 --> 01:00:05.909
questions and get advice about staying

01:00:05.949 --> 01:00:08.371
private online and preserving your digital

01:00:08.411 --> 01:00:08.751
rights.

01:00:09.972 --> 01:00:10.351
So yeah,

01:00:10.371 --> 01:00:12.713
with my spiel out of the way, Nate,

01:00:12.733 --> 01:00:14.775
let's talk about some new research on car

01:00:14.795 --> 01:00:16.896
privacy or the lack thereof.

01:00:17.436 --> 01:00:19.137
And everyone, remember...

01:00:20.177 --> 01:00:21.179
The chat's been pretty active,

01:00:21.199 --> 01:00:22.021
which is fantastic.

01:00:22.041 --> 01:00:23.081
But if you do have questions,

01:00:23.161 --> 01:00:24.543
either about what we're talking about or

01:00:24.563 --> 01:00:26.146
just questions in general,

01:00:26.487 --> 01:00:28.068
we will get to all those questions in

01:00:28.128 --> 01:00:29.070
between stories.

01:00:29.110 --> 01:00:31.393
So definitely feel free to leave them.

01:00:31.454 --> 01:00:32.155
Now you don't have to wait.

01:00:33.547 --> 01:00:34.487
Yeah, real quick,

01:00:34.547 --> 01:00:36.068
I'll jump into a couple of those

01:00:36.108 --> 01:00:36.469
questions.

01:00:36.528 --> 01:00:36.989
First of all,

01:00:37.068 --> 01:00:39.210
apparently the Jonah Act is the just open

01:00:39.311 --> 01:00:40.612
nothing and hide act.

01:00:41.132 --> 01:00:43.114
So if you were curious about that.

01:00:44.193 --> 01:00:45.074
Username is Naya said,

01:00:45.114 --> 01:00:46.556
where's Tudor encryption wise?

01:00:46.576 --> 01:00:47.777
They receive government funding to

01:00:47.856 --> 01:00:48.958
post-quantum cryptography.

01:00:49.498 --> 01:00:52.340
I think either they're still rolling it

01:00:52.400 --> 01:00:53.721
out or it might be done.

01:00:54.302 --> 01:00:56.443
I know Tudor Drive uses post-quantum

01:00:56.483 --> 01:00:57.744
encryption.

01:00:59.181 --> 01:01:00.481
Yeah, I, I know it's,

01:01:00.581 --> 01:01:02.242
it's in progress at very least if it's

01:01:02.262 --> 01:01:03.523
not already fully rolled out.

01:01:03.822 --> 01:01:05.684
I believe they fully rolled it out and

01:01:05.704 --> 01:01:06.804
it should protect all that data.

01:01:07.344 --> 01:01:08.085
Um, yeah, yeah.

01:01:08.144 --> 01:01:10.565
Proton still is not rolled it out

01:01:10.626 --> 01:01:11.085
annoyingly,

01:01:11.146 --> 01:01:12.847
even though they have it supposedly.

01:01:13.606 --> 01:01:14.487
Um, but yeah,

01:01:14.507 --> 01:01:15.827
I've complained about that on the Reddit

01:01:16.047 --> 01:01:17.409
and hopefully we,

01:01:17.469 --> 01:01:18.469
hopefully we see that soon.

01:01:19.588 --> 01:01:19.788
You know,

01:01:19.887 --> 01:01:22.048
I really want to add a soundboard on

01:01:22.068 --> 01:01:24.090
my little stream deck here for the clip

01:01:24.130 --> 01:01:26.371
from Letter Kenny,

01:01:26.471 --> 01:01:27.592
where he just says allegedly,

01:01:27.612 --> 01:01:28.731
because I feel like I use that a

01:01:28.791 --> 01:01:29.052
lot.

01:01:29.311 --> 01:01:30.873
But anyways, I digress.

01:01:31.293 --> 01:01:32.273
We'll move on to the next story,

01:01:32.313 --> 01:01:34.494
which is a study about cars.

01:01:35.094 --> 01:01:36.376
And I do apologize.

01:01:36.556 --> 01:01:39.516
I'm going to read pretty much all of

01:01:39.536 --> 01:01:39.956
this article.

01:01:39.996 --> 01:01:41.097
It's not very long for the record.

01:01:42.117 --> 01:01:42.798
And I read fast,

01:01:43.059 --> 01:01:44.760
but it's one of those articles where

01:01:44.780 --> 01:01:46.242
there's really not a lot of fluff and

01:01:46.461 --> 01:01:47.262
it's very dense.

01:01:47.422 --> 01:01:49.545
So it's one of those times I found

01:01:49.585 --> 01:01:50.726
myself taking notes and I'm like,

01:01:50.786 --> 01:01:52.067
I literally just copied the whole article.

01:01:52.146 --> 01:01:54.208
So the headline says,

01:01:54.568 --> 01:01:56.490
this study looks at how and with whom

01:01:56.550 --> 01:01:57.992
connected cars share your data.

01:01:58.032 --> 01:01:59.152
So I can actually summarize the first

01:01:59.193 --> 01:02:00.153
couple of paragraphs.

01:02:00.695 --> 01:02:01.615
Back in twenty twenty three,

01:02:01.735 --> 01:02:03.918
Mozilla published a report that actually

01:02:03.938 --> 01:02:05.079
broke all the way into the mainstream.

01:02:05.579 --> 01:02:06.519
And what they did was they looked at

01:02:06.539 --> 01:02:07.860
the privacy policies of more than two

01:02:07.900 --> 01:02:08.782
dozen automakers.

01:02:09.322 --> 01:02:10.523
And they said, quote,

01:02:10.543 --> 01:02:12.123
cars are the worst product category we

01:02:12.164 --> 01:02:13.545
have ever reviewed for privacy.

01:02:14.965 --> 01:02:16.047
But this article notes like, yeah,

01:02:16.067 --> 01:02:17.668
that was conducted by reading the privacy

01:02:17.728 --> 01:02:18.088
policies.

01:02:18.108 --> 01:02:20.190
But now we have actual research.

01:02:20.670 --> 01:02:22.110
Northeastern University and Consumer

01:02:22.150 --> 01:02:24.112
Reports tested twenty one cars from

01:02:24.193 --> 01:02:25.373
nineteen different brands.

01:02:25.914 --> 01:02:28.956
And let's see two attempts to actually see

01:02:28.996 --> 01:02:30.217
what was in the data packets using

01:02:30.257 --> 01:02:31.717
modified certificates failed in every

01:02:31.757 --> 01:02:32.117
case.

01:02:32.458 --> 01:02:34.219
But the network traces still yielded

01:02:34.260 --> 01:02:35.079
valuable information,

01:02:35.139 --> 01:02:37.101
including the domains contacted via DNS

01:02:37.121 --> 01:02:37.442
traffic.

01:02:37.902 --> 01:02:39.545
uh server name indication in tls

01:02:39.565 --> 01:02:40.846
handshakes the volume and timing of

01:02:40.885 --> 01:02:42.407
transmissions and differences in behavior

01:02:42.467 --> 01:02:44.550
across experimental scenarios so all of

01:02:44.570 --> 01:02:46.813
the cars contacted a first party domain uh

01:02:46.873 --> 01:02:49.137
you know honda.com mercedes.com whatever

01:02:49.557 --> 01:02:52.141
um uh where did they say

01:02:53.322 --> 01:02:54.282
A few left it there,

01:02:54.362 --> 01:02:55.684
such as the Buick Invista and the

01:02:55.704 --> 01:02:57.626
Mercedes-Benz EQS didn't appear to reach

01:02:57.686 --> 01:02:58.827
out anywhere else, for example.

01:02:59.206 --> 01:03:00.668
Others were far more promiscuous,

01:03:00.708 --> 01:03:01.989
with Tesla topping the chart.

01:03:02.309 --> 01:03:04.170
The Model Three contacted thirty-four

01:03:04.291 --> 01:03:05.231
advertising, tracking,

01:03:05.311 --> 01:03:06.353
and analytics domains,

01:03:06.632 --> 01:03:08.775
as well as thirty-seven domains from apps

01:03:08.835 --> 01:03:10.496
integrated into the infotainment system.

01:03:11.016 --> 01:03:12.436
Alphabet's domains were most frequently

01:03:12.476 --> 01:03:12.978
contacted,

01:03:13.018 --> 01:03:15.079
which is not enormously surprising given

01:03:15.099 --> 01:03:17.141
the penetration of Android Automotive OS

01:03:17.181 --> 01:03:17.782
into the sector.

01:03:18.362 --> 01:03:18.661
They said,

01:03:18.702 --> 01:03:20.242
but there were many second level domains

01:03:20.262 --> 01:03:22.485
that were not necessary for core services

01:03:22.505 --> 01:03:23.766
like DoubleClick.net and

01:03:23.786 --> 01:03:24.925
GoogleSyndication.com,

01:03:24.945 --> 01:03:26.166
which are used for advertising.

01:03:27.007 --> 01:03:28.909
Media streaming like Spotify, SiriusXM,

01:03:28.949 --> 01:03:30.630
and so on are also there,

01:03:30.670 --> 01:03:32.130
as well as mapping companies like Here,

01:03:32.190 --> 01:03:33.271
TomTom, and Mapbox.

01:03:35.106 --> 01:03:36.447
They said using a car's infotainment

01:03:36.487 --> 01:03:37.907
system resulted in contacting the most

01:03:37.927 --> 01:03:39.487
domains versus just sitting idle or

01:03:39.527 --> 01:03:41.728
driving for all the cars tested,

01:03:42.230 --> 01:03:42.949
which would make sense,

01:03:43.230 --> 01:03:44.291
apart from the Cybertruck,

01:03:44.451 --> 01:03:46.271
which instead contacts twenty six more

01:03:46.311 --> 01:03:47.891
third party domains while driving than

01:03:47.931 --> 01:03:48.833
stationary, which is.

01:03:50.666 --> 01:03:50.927
What?

01:03:51.467 --> 01:03:51.827
I digress.

01:03:52.849 --> 01:03:54.851
So with the EVs,

01:03:54.911 --> 01:03:56.132
they were able to put them in a

01:03:56.172 --> 01:03:59.496
Faraday tent and actually test.

01:04:01.500 --> 01:04:03.061
They couldn't do that with the internal

01:04:03.081 --> 01:04:04.403
combustion engine cars because of fumes,

01:04:04.744 --> 01:04:05.724
but they were able to put them in

01:04:05.764 --> 01:04:07.487
a tent and see would they try a

01:04:07.527 --> 01:04:08.409
different way to phone home.

01:04:09.009 --> 01:04:11.409
And they said some of the EVs,

01:04:11.510 --> 01:04:12.951
including the Cadillac Lyric,

01:04:12.971 --> 01:04:14.371
Chevy Blazer, Honda Prologue,

01:04:14.391 --> 01:04:16.751
and Rivian R-I simply stopped using those

01:04:16.791 --> 01:04:17.793
connected subsystems.

01:04:18.092 --> 01:04:19.512
But some of the cars redirected their

01:04:19.552 --> 01:04:20.454
traffic to Wi-Fi,

01:04:20.494 --> 01:04:21.853
allowing the researchers to see traffic

01:04:21.873 --> 01:04:23.414
flows that were previously unobservable.

01:04:24.414 --> 01:04:26.056
And then they tested thirty different

01:04:26.076 --> 01:04:27.195
connected car apps.

01:04:27.356 --> 01:04:28.735
So I'm not gonna lie.

01:04:28.856 --> 01:04:30.317
I tried one of these one time just

01:04:30.336 --> 01:04:32.157
because I was hoping that we would be

01:04:32.177 --> 01:04:33.378
able to remote start our car in the

01:04:33.398 --> 01:04:34.797
winter and let it like warm up.

01:04:35.338 --> 01:04:36.039
It did not do that.

01:04:36.079 --> 01:04:38.519
So I deleted the app because in our

01:04:38.539 --> 01:04:38.960
case, you know,

01:04:38.980 --> 01:04:40.519
you download an app for like Honda,

01:04:40.559 --> 01:04:41.420
Toyota, whoever,

01:04:42.021 --> 01:04:42.221
and

01:04:43.121 --> 01:04:44.722
in my opinion they're pretty useless it

01:04:44.742 --> 01:04:46.943
like tells you it tells you things the

01:04:46.963 --> 01:04:48.784
car already tells you like you know oh

01:04:48.824 --> 01:04:50.184
you've driven this far oh it's time to

01:04:50.204 --> 01:04:51.925
get an oil change and it's like what

01:04:51.965 --> 01:04:52.945
do i need an app for that but

01:04:52.985 --> 01:04:56.188
anyways um they said in some cases uh

01:04:56.208 --> 01:04:58.009
this exposed users to more than twenty new

01:04:58.108 --> 01:05:00.230
advertising tracking and analytics

01:05:00.250 --> 01:05:02.090
companies from general motors toyota and

01:05:02.110 --> 01:05:03.552
nissan were the worst offenders

01:05:04.731 --> 01:05:06.393
um the authors reached out to seventeen of

01:05:06.414 --> 01:05:07.594
the automakers and heard back from

01:05:07.614 --> 01:05:09.376
fourteen the replies are not entirely

01:05:09.416 --> 01:05:10.817
encouraging all of the oems told

01:05:10.856 --> 01:05:12.617
researchers that data sharing with with

01:05:12.639 --> 01:05:14.019
third parties was covered by contracts

01:05:14.039 --> 01:05:15.920
prohibiting the use of pii outside the

01:05:15.940 --> 01:05:17.681
scope of their privacy agreements the same

01:05:17.702 --> 01:05:19.324
privacy agreements that horrified bozilla

01:05:19.623 --> 01:05:22.005
in uh some of the automakers deflected

01:05:22.045 --> 01:05:23.666
blame onto the embedded browser running

01:05:23.706 --> 01:05:25.047
inside the infotainment system and said it

01:05:25.068 --> 01:05:26.248
was up to the users to select the

01:05:26.289 --> 01:05:29.190
right prompt or reject a cookie uh seven

01:05:29.231 --> 01:05:30.652
said it's the consumer's responsibility to

01:05:30.693 --> 01:05:31.733
read and accept all the terms and

01:05:31.753 --> 01:05:32.273
conditions

01:05:32.934 --> 01:05:34.275
even though in many cases the software is

01:05:34.335 --> 01:05:36.335
already installed and the author's note

01:05:36.355 --> 01:05:37.735
that declining a data sharing agreement

01:05:37.755 --> 01:05:39.215
can result in loss of services and

01:05:39.235 --> 01:05:40.916
functionality not a great solution if it

01:05:40.936 --> 01:05:42.516
means losing useful features you expect to

01:05:42.536 --> 01:05:44.318
work when you bought the car they said

01:05:44.338 --> 01:05:45.757
there was at least one positive outcome

01:05:45.858 --> 01:05:47.398
after being contacted Honda changed its

01:05:47.418 --> 01:05:48.699
data practices and no longer shares

01:05:48.739 --> 01:05:50.920
precise location data with at least one

01:05:50.960 --> 01:05:54.440
tracking company so yeah that was a lot

01:05:56.181 --> 01:05:56.621
but

01:05:57.621 --> 01:05:59.003
i don't know the the fun thing about

01:05:59.043 --> 01:06:01.184
cars is i feel like right now there's

01:06:01.244 --> 01:06:03.885
not a lot of defenses i mean are

01:06:03.905 --> 01:06:07.047
you aware of any any uh defenses against

01:06:07.128 --> 01:06:09.048
car privacy invasions jonah it's

01:06:09.088 --> 01:06:11.630
definitely a field that could use a lot

01:06:11.690 --> 01:06:15.092
more research unfortunately um i don't

01:06:15.233 --> 01:06:16.893
know maybe that's an opportunity for us to

01:06:16.934 --> 01:06:19.615
look into that but it's it's tricky as

01:06:19.655 --> 01:06:19.896
these

01:06:21.351 --> 01:06:21.590
Yeah,

01:06:21.610 --> 01:06:24.391
cars just become even more connected and

01:06:24.411 --> 01:06:25.711
they're all kind of doing their own thing,

01:06:25.751 --> 01:06:26.152
of course,

01:06:26.192 --> 01:06:28.612
because like all of these companies,

01:06:29.152 --> 01:06:30.532
they just want to monetize that data.

01:06:30.632 --> 01:06:35.554
I'm sure very soon we'll see information

01:06:35.574 --> 01:06:37.635
like the LG TV information that just came

01:06:37.675 --> 01:06:39.456
out, except without with cars.

01:06:40.255 --> 01:06:41.615
Certainly we know of a lot of privacy

01:06:41.655 --> 01:06:44.536
invasions that cars have even today,

01:06:44.757 --> 01:06:46.257
and it's only kind of getting worse.

01:06:48.302 --> 01:06:49.885
what exactly we can do about it i

01:06:49.905 --> 01:06:51.346
don't know though i don't have specific

01:06:51.385 --> 01:06:54.088
car advice unfortunately um but it would

01:06:54.108 --> 01:06:57.150
be great if there was was an option

01:06:58.693 --> 01:07:01.014
yeah for sure i know one thing that

01:07:01.074 --> 01:07:02.436
gets thrown around a lot is like just

01:07:02.476 --> 01:07:04.978
drive an older car um you know australis

01:07:05.038 --> 01:07:06.139
actually said we're cooked when all the

01:07:06.179 --> 01:07:08.300
old cars break down that's not always a

01:07:08.320 --> 01:07:10.722
feasible um solution because i know i used

01:07:10.742 --> 01:07:12.684
to have a that was my last car

01:07:12.704 --> 01:07:12.844
was a

01:07:14.025 --> 01:07:15.166
and I got rid of that just a

01:07:15.206 --> 01:07:15.806
couple years ago,

01:07:15.847 --> 01:07:17.967
so I had it about thirteen years or

01:07:18.007 --> 01:07:19.188
so, ten years, something like that,

01:07:19.829 --> 01:07:21.088
and it was a very common car,

01:07:21.108 --> 01:07:22.048
I'm not gonna say what it was for

01:07:22.088 --> 01:07:22.650
obvious reasons,

01:07:22.690 --> 01:07:24.449
but it was a very common car,

01:07:25.090 --> 01:07:25.490
and yet,

01:07:25.690 --> 01:07:26.891
I remember the last time I went into

01:07:26.931 --> 01:07:28.052
an AutoZone, and I was like, yeah,

01:07:28.072 --> 01:07:29.032
I need a headlight, and they're like, oh,

01:07:29.052 --> 01:07:30.152
we don't have any headlights for that car,

01:07:30.172 --> 01:07:30.532
and I'm like,

01:07:32.362 --> 01:07:33.063
What do you mean you don't have any

01:07:33.083 --> 01:07:33.844
headlights for that car?

01:07:33.943 --> 01:07:35.523
I passed six other ones on the way

01:07:35.583 --> 01:07:35.804
here.

01:07:35.844 --> 01:07:38.085
This is not an unusual car.

01:07:39.065 --> 01:07:41.385
And you know, especially like my new car,

01:07:42.646 --> 01:07:44.246
one of our AC fan broke,

01:07:45.108 --> 01:07:46.347
which was just wonderful when we lived in

01:07:46.387 --> 01:07:46.688
Texas.

01:07:47.548 --> 01:07:50.170
Our AC fan broke and I jumped online

01:07:50.289 --> 01:07:52.389
and I spent days scouring,

01:07:52.429 --> 01:07:53.951
not just YouTube, but like forums,

01:07:53.990 --> 01:07:55.530
like multiple search engines.

01:07:55.632 --> 01:07:55.911
I was like,

01:07:55.952 --> 01:07:58.092
there has to be tutorials on how to

01:07:58.132 --> 01:07:59.052
swap out this fan.

01:07:59.833 --> 01:08:01.873
And I could not find any tutorials.

01:08:01.954 --> 01:08:02.414
I could find,

01:08:03.534 --> 01:08:06.315
I found that repair for a different make

01:08:06.335 --> 01:08:09.978
and model, the right make and model,

01:08:10.038 --> 01:08:11.197
but different repairs.

01:08:11.697 --> 01:08:13.659
But we are no longer living in the

01:08:13.679 --> 01:08:14.960
glory days of YouTube where it's like

01:08:15.039 --> 01:08:15.820
anything you can think of,

01:08:15.840 --> 01:08:17.220
there's a tutorial on YouTube for it.

01:08:17.640 --> 01:08:19.100
So my point being is we're hitting a

01:08:19.162 --> 01:08:19.641
point where

01:08:20.706 --> 01:08:23.287
just drive an older car it's only going

01:08:23.306 --> 01:08:24.407
to work if you have the money to

01:08:24.426 --> 01:08:25.948
like get parts custom ordered and

01:08:25.988 --> 01:08:27.667
fabricated and go to a mechanic every time

01:08:27.707 --> 01:08:29.668
it breaks down because it's just becoming

01:08:29.708 --> 01:08:31.349
impossible to like maintain these cars

01:08:31.569 --> 01:08:34.149
anymore so i don't know personal rant on

01:08:34.189 --> 01:08:37.650
that one but um anonymous one shared uh

01:08:37.690 --> 01:08:40.891
a link about rivians um this has come

01:08:40.971 --> 01:08:41.072
out

01:08:41.891 --> 01:08:43.372
come up a few times when we talked

01:08:43.393 --> 01:08:45.836
about car privacy and EVs.

01:08:47.056 --> 01:08:47.777
I haven't looked into it.

01:08:47.837 --> 01:08:49.538
Rivian claims that you can disable a lot

01:08:49.559 --> 01:08:50.739
of the stuff, which is cool.

01:08:51.220 --> 01:08:52.360
You do lose some features.

01:08:53.362 --> 01:08:54.582
It is sort of like

01:08:56.452 --> 01:08:58.632
very similar to trusting Apple with like,

01:08:59.533 --> 01:09:00.453
is it truly disabled?

01:09:00.493 --> 01:09:01.773
Are they collecting all of this stuff?

01:09:01.853 --> 01:09:02.774
If you want to.

01:09:04.634 --> 01:09:04.774
Yeah,

01:09:04.814 --> 01:09:05.753
if you want to trust that that's

01:09:05.774 --> 01:09:06.173
happening,

01:09:06.215 --> 01:09:07.534
it could be it could be an option.

01:09:07.555 --> 01:09:09.435
And it's cool that, you know,

01:09:09.454 --> 01:09:10.676
they at least recognize that this is a

01:09:10.716 --> 01:09:11.496
privacy problem.

01:09:12.416 --> 01:09:14.076
But I think I don't know if people

01:09:14.115 --> 01:09:16.317
have evaluated that yet.

01:09:17.037 --> 01:09:19.898
um another comment i saw was from username

01:09:19.938 --> 01:09:21.979
isn't high grok helps me drive this

01:09:22.019 --> 01:09:23.760
comment is how i just found out that

01:09:24.100 --> 01:09:26.421
tesla's integrate grok now i was just

01:09:26.440 --> 01:09:28.601
looking this up um and that is very

01:09:28.641 --> 01:09:31.182
sad knowledge for me to have so thank

01:09:31.222 --> 01:09:33.323
you for sharing that with me um that

01:09:33.384 --> 01:09:34.824
is that is terrible

01:09:37.009 --> 01:09:38.170
Um, I'd buy said it here.

01:09:38.470 --> 01:09:39.149
Thank you so much.

01:09:39.390 --> 01:09:40.291
I was trying to remember the name of

01:09:40.310 --> 01:09:40.711
the company.

01:09:40.751 --> 01:09:42.112
Carrie Parker mentioned them a couple

01:09:42.152 --> 01:09:43.033
months ago on firewalls.

01:09:43.052 --> 01:09:43.773
Don't stop dragons.

01:09:43.792 --> 01:09:46.414
Apparently slate alleges that you can turn

01:09:46.515 --> 01:09:47.996
off all the tracking.

01:09:48.036 --> 01:09:48.876
Same thing with Rivian.

01:09:49.296 --> 01:09:50.396
It's like, how much do you trust it?

01:09:50.476 --> 01:09:53.658
I will say, um, in my opinion,

01:09:54.699 --> 01:09:54.899
what's up?

01:09:55.332 --> 01:09:55.533
Sorry,

01:09:55.573 --> 01:09:56.655
I was just going to say Slate might

01:09:56.676 --> 01:09:58.318
be a better option than Rivian because my

01:09:58.359 --> 01:10:00.362
understanding is there's not even a

01:10:00.402 --> 01:10:02.966
computer unless you buy one.

01:10:03.186 --> 01:10:04.509
Everything is kind of modular with the

01:10:04.548 --> 01:10:05.109
Slate truck.

01:10:05.150 --> 01:10:06.752
That's what it is.

01:10:06.792 --> 01:10:08.537
Yeah, the Slate's all modular.

01:10:08.962 --> 01:10:10.582
I remember looking at Slade and kind of

01:10:10.603 --> 01:10:12.805
configuring one on their website.

01:10:13.444 --> 01:10:15.966
I don't have the thirty grand to buy

01:10:15.987 --> 01:10:16.686
a slate truck,

01:10:16.766 --> 01:10:19.488
but I think even like the speaker system

01:10:19.509 --> 01:10:21.550
they recommend is basically a Bluetooth

01:10:21.569 --> 01:10:23.091
speaker that you mount there and then a

01:10:23.131 --> 01:10:23.792
phone holder.

01:10:24.671 --> 01:10:24.851
So

01:10:26.113 --> 01:10:26.353
I mean,

01:10:26.393 --> 01:10:28.993
that is kind of the ideal way to

01:10:29.054 --> 01:10:31.975
do it in some in some sense,

01:10:32.015 --> 01:10:33.335
because I think it makes a lot of

01:10:33.375 --> 01:10:35.475
sense to kind of have everything on your

01:10:35.496 --> 01:10:37.296
phone and kind of only trust this one

01:10:37.337 --> 01:10:38.697
computer instead of this whole system that

01:10:38.716 --> 01:10:39.136
you're using.

01:10:39.197 --> 01:10:42.337
But I also don't know anything about the

01:10:42.398 --> 01:10:44.719
slate truck or how nice it is the

01:10:44.759 --> 01:10:46.198
drive or how many people will buy it.

01:10:46.279 --> 01:10:47.939
But it's an interesting concept for sure.

01:10:49.345 --> 01:10:50.605
a little bit off topic, but you said,

01:10:50.666 --> 01:10:51.947
I don't have the thirty grand to buy

01:10:51.966 --> 01:10:52.127
it.

01:10:52.146 --> 01:10:54.027
I remember one time just purely for

01:10:54.087 --> 01:10:54.447
laughs,

01:10:54.587 --> 01:10:56.387
I went to system seventy six's website.

01:10:56.408 --> 01:10:57.667
This was years ago before the ramp

01:10:57.688 --> 01:10:58.167
apocalypse.

01:10:58.587 --> 01:11:00.029
And just for laughs, I was like,

01:11:00.328 --> 01:11:02.328
what is the most powerful computer they

01:11:02.389 --> 01:11:02.689
sell?

01:11:02.748 --> 01:11:04.510
So I got like the best,

01:11:04.630 --> 01:11:05.710
like the most RAM,

01:11:05.750 --> 01:11:06.869
the biggest hard drives,

01:11:06.890 --> 01:11:09.350
like multiple GPUs.

01:11:09.631 --> 01:11:11.271
And it came out to like seventy thousand

01:11:11.311 --> 01:11:11.851
dollars.

01:11:13.271 --> 01:11:13.752
I mean, to be fair,

01:11:13.773 --> 01:11:15.614
it had like nine I-Nines in it or

01:11:15.635 --> 01:11:16.296
something crazy.

01:11:16.395 --> 01:11:18.557
So it's, yeah, but I just,

01:11:18.597 --> 01:11:19.118
just for fun,

01:11:19.279 --> 01:11:20.199
I like to do that every now and

01:11:20.220 --> 01:11:22.082
then just how bad does it get?

01:11:22.162 --> 01:11:22.983
But yeah,

01:11:24.145 --> 01:11:25.805
we actually have quite a few here.

01:11:26.728 --> 01:11:26.807
Oh,

01:11:26.908 --> 01:11:27.828
I remember I was going to say like

01:11:27.849 --> 01:11:28.009
with the

01:11:28.029 --> 01:11:29.449
whole like Rivian, you know,

01:11:29.470 --> 01:11:30.430
you can go to this link thing.

01:11:30.850 --> 01:11:32.192
Yeah, we're kind of trusting them.

01:11:32.231 --> 01:11:33.113
Like you said, it's like Apple.

01:11:33.153 --> 01:11:34.413
We're kind of trusting them to turn it

01:11:34.474 --> 01:11:34.613
off.

01:11:34.934 --> 01:11:35.554
But it's one of those things,

01:11:35.573 --> 01:11:36.154
in my opinion,

01:11:36.194 --> 01:11:37.756
where it can't hurt to do it because

01:11:37.775 --> 01:11:38.617
worst case scenario,

01:11:38.676 --> 01:11:39.938
you're in the same boat you started in.

01:11:40.217 --> 01:11:40.978
Best case scenario,

01:11:41.018 --> 01:11:42.640
they do actually shut off at least some

01:11:42.659 --> 01:11:43.260
of the telemetry.

01:11:43.579 --> 01:11:44.400
Worst case scenario,

01:11:44.841 --> 01:11:45.822
literally nothing has changed.

01:11:45.841 --> 01:11:46.743
So it's not like you're going to be

01:11:46.762 --> 01:11:48.823
worse off for doing it, in my opinion.

01:11:48.844 --> 01:11:49.003
But...

01:11:53.105 --> 01:11:53.286
Yeah,

01:11:53.386 --> 01:11:55.707
what about a start a farm life when

01:11:55.728 --> 01:11:56.707
the digital world is too much?

01:11:56.747 --> 01:11:58.649
Seems like a lot of people are retiring

01:11:58.668 --> 01:11:59.270
to the farm life.

01:12:01.211 --> 01:12:04.152
Oh, what do we have here?

01:12:04.212 --> 01:12:05.252
Jonah, it's different from Apple.

01:12:05.273 --> 01:12:06.873
They say you can disable all cellular

01:12:06.894 --> 01:12:07.474
connectivity.

01:12:07.554 --> 01:12:08.755
It's a simple on off.

01:12:08.954 --> 01:12:10.235
So but, you know,

01:12:10.296 --> 01:12:12.657
it's like a proprietary system, right?

01:12:12.896 --> 01:12:13.597
Just like Apple.

01:12:13.938 --> 01:12:15.259
You just have to trust other switches

01:12:15.298 --> 01:12:15.498
work.

01:12:17.548 --> 01:12:17.689
I mean,

01:12:17.708 --> 01:12:18.628
there's got to be a way to like

01:12:19.668 --> 01:12:21.130
check and see if there's anything coming

01:12:21.210 --> 01:12:21.569
off of it.

01:12:21.630 --> 01:12:23.109
I would feel like I don't know.

01:12:23.489 --> 01:12:24.270
I'm really curious.

01:12:24.369 --> 01:12:26.331
I remember when we looked at the review

01:12:26.350 --> 01:12:27.070
and stuff last time,

01:12:27.110 --> 01:12:30.551
it does disable things like active lane

01:12:30.610 --> 01:12:31.810
centering, which isn't great.

01:12:31.850 --> 01:12:33.051
It disables navigation,

01:12:33.091 --> 01:12:34.192
which might make sense.

01:12:34.231 --> 01:12:34.851
But I mean,

01:12:34.931 --> 01:12:37.811
even even in like two thousand eight to

01:12:37.851 --> 01:12:38.512
twenty ten,

01:12:38.672 --> 01:12:40.512
we had cars that just had maps in

01:12:40.552 --> 01:12:40.773
them.

01:12:40.893 --> 01:12:43.212
Could we just could we just have offline

01:12:43.252 --> 01:12:43.953
maps for a fan?

01:12:44.014 --> 01:12:46.113
Maybe I'm curious whether

01:12:47.094 --> 01:12:48.494
I don't know anything about Rivian,

01:12:48.675 --> 01:12:49.194
honestly.

01:12:49.395 --> 01:12:50.975
I don't know if it supports CarPlay.

01:12:51.055 --> 01:12:52.737
I wonder if you could disable this but

01:12:52.777 --> 01:12:55.537
still use CarPlay for music streaming.

01:12:55.658 --> 01:12:56.418
Or Android Auto.

01:12:56.599 --> 01:12:57.399
Either one,

01:12:57.439 --> 01:12:58.420
depending on the phone you have.

01:13:01.123 --> 01:13:02.585
Yeah, it's interesting.

01:13:02.625 --> 01:13:04.065
This article does say that they can

01:13:04.247 --> 01:13:07.029
disable the eSIM entirely through a

01:13:07.069 --> 01:13:07.810
service appointment,

01:13:07.909 --> 01:13:11.693
which maybe would be even better.

01:13:11.972 --> 01:13:12.654
But yeah,

01:13:12.894 --> 01:13:14.574
it all depends on how well they've

01:13:14.614 --> 01:13:15.235
implemented this.

01:13:15.256 --> 01:13:16.617
But I would certainly hope it works as

01:13:16.657 --> 01:13:17.176
advertised.

01:13:17.757 --> 01:13:17.917
Yeah.

01:13:20.100 --> 01:13:20.359
Yeah.

01:13:20.539 --> 01:13:20.619
Um,

01:13:20.640 --> 01:13:21.900
the last thing I'll add before we move

01:13:21.980 --> 01:13:22.581
on is, uh,

01:13:22.600 --> 01:13:23.801
I know there's services out there.

01:13:23.862 --> 01:13:25.301
The two I know of is privacy for

01:13:25.341 --> 01:13:27.103
cars and vehicle privacy report.

01:13:27.662 --> 01:13:27.762
Um,

01:13:27.802 --> 01:13:29.363
they basically submit opt-outs on your

01:13:29.404 --> 01:13:29.724
behalf,

01:13:29.823 --> 01:13:31.305
or you can do it yourself if you're

01:13:31.345 --> 01:13:31.944
a masochist.

01:13:32.585 --> 01:13:33.765
Um, it's,

01:13:33.886 --> 01:13:34.746
it's one of those things where you're

01:13:34.786 --> 01:13:35.746
trusting another party.

01:13:35.765 --> 01:13:36.306
Uh,

01:13:36.346 --> 01:13:37.747
this is not an official privacy guides

01:13:37.766 --> 01:13:39.868
recommendation, but, um,

01:13:39.927 --> 01:13:41.408
you are trusting a third party because you

01:13:41.469 --> 01:13:41.748
have to,

01:13:42.149 --> 01:13:43.269
and I think you even have to like

01:13:43.309 --> 01:13:44.689
check a box that basically says like,

01:13:45.109 --> 01:13:46.992
I am giving you legal authorization to act

01:13:47.032 --> 01:13:48.212
on my behalf in this instance.

01:13:49.533 --> 01:13:50.854
And even then, it's not really,

01:13:51.676 --> 01:13:52.396
it's very limited.

01:13:52.436 --> 01:13:53.637
It's like a lot of websites where it's

01:13:53.658 --> 01:13:55.359
like, oh, opt out of targeted advertising.

01:13:55.380 --> 01:13:55.939
And it's like, okay,

01:13:55.960 --> 01:13:57.280
but opting out of targeted advertising is

01:13:57.320 --> 01:13:58.582
not the same as opting out of collecting

01:13:58.622 --> 01:14:00.043
the data for targeted advertising.

01:14:00.463 --> 01:14:01.545
So it's definitely not,

01:14:02.525 --> 01:14:04.228
I'm not trying to say it's foolproof and

01:14:04.247 --> 01:14:04.528
like, oh,

01:14:04.568 --> 01:14:05.488
you sign up for one of these and

01:14:05.509 --> 01:14:07.069
they'll delete everything or whatever.

01:14:07.130 --> 01:14:08.291
But again,

01:14:08.331 --> 01:14:09.993
it's one of those things where I think

01:14:11.689 --> 01:14:13.131
I would argue you're probably not worse

01:14:13.190 --> 01:14:13.291
off.

01:14:13.310 --> 01:14:14.011
Like I've done it.

01:14:14.190 --> 01:14:16.112
I haven't had any downsides other than I

01:14:16.131 --> 01:14:17.091
got a bunch of letters that are like,

01:14:17.131 --> 01:14:18.773
we received your request and we'll process

01:14:18.813 --> 01:14:19.853
and blah, blah, blah, blah, blah, blah.

01:14:21.734 --> 01:14:22.434
And then, you know,

01:14:22.734 --> 01:14:24.135
at very least it sends a message.

01:14:24.154 --> 01:14:24.414
You know,

01:14:24.534 --> 01:14:26.876
if they get tens of thousands of these

01:14:26.935 --> 01:14:27.336
requests,

01:14:27.355 --> 01:14:29.596
then maybe they might just be like, hmm,

01:14:29.617 --> 01:14:31.197
people feel strongly about this.

01:14:31.216 --> 01:14:32.257
So I don't know if it would be

01:14:32.297 --> 01:14:33.738
enough to change, but yeah.

01:14:33.778 --> 01:14:35.359
So I just wanted to throw that out

01:14:35.378 --> 01:14:35.519
there.

01:14:36.686 --> 01:14:37.728
I think you have a forum post to

01:14:37.747 --> 01:14:38.887
pull up, but right before that,

01:14:38.927 --> 01:14:40.748
I want to do one more comment here.

01:14:41.009 --> 01:14:41.609
Foundog said,

01:14:41.630 --> 01:14:43.109
I think I'd want the ability to remove

01:14:43.149 --> 01:14:43.970
the five G modem.

01:14:44.411 --> 01:14:46.471
I think that that would be like that's

01:14:46.551 --> 01:14:47.332
that's the main thing.

01:14:47.533 --> 01:14:49.132
If I was going to look into this

01:14:49.172 --> 01:14:50.274
vehicle stuff more,

01:14:50.333 --> 01:14:52.975
which maybe we should do, to be honest,

01:14:52.994 --> 01:14:54.636
because nobody else seems to be doing it

01:14:54.655 --> 01:14:57.497
these days since Mozilla stopped updating

01:14:57.537 --> 01:14:57.797
that.

01:14:57.898 --> 01:14:59.658
But I think that that would be probably

01:14:59.698 --> 01:15:01.159
the best solution is just

01:15:02.020 --> 01:15:04.521
there's probably going to be some vehicles

01:15:04.542 --> 01:15:07.243
where you can just pull out this module

01:15:07.264 --> 01:15:09.525
or make make a change to like force

01:15:09.565 --> 01:15:11.627
it to no longer be connected and then

01:15:11.667 --> 01:15:13.248
see like what functionality remains.

01:15:13.288 --> 01:15:15.270
I think looking into that would be would

01:15:15.291 --> 01:15:15.751
be cool.

01:15:15.871 --> 01:15:16.311
I know that

01:15:17.440 --> 01:15:19.242
Henry from Teklor suggested something

01:15:19.922 --> 01:15:21.264
similar because at one point,

01:15:22.064 --> 01:15:23.524
I think he got like a Nissan Leaf

01:15:23.625 --> 01:15:24.065
or something,

01:15:24.105 --> 01:15:25.966
but it was like an older EV that

01:15:26.327 --> 01:15:28.189
only had two G connectivity.

01:15:28.208 --> 01:15:30.210
So then when all of the towers stopped

01:15:30.250 --> 01:15:31.251
supporting two G,

01:15:32.230 --> 01:15:33.532
he said that that would that would make

01:15:33.551 --> 01:15:34.113
it private.

01:15:34.813 --> 01:15:36.354
know that's certainly an approach i think

01:15:36.474 --> 01:15:39.774
removing it entirely would be uh certainly

01:15:40.015 --> 01:15:42.555
a lot better um but i don't know

01:15:42.837 --> 01:15:44.978
of any cars that make that super easy

01:15:45.018 --> 01:15:46.877
to do but i feel like there might

01:15:46.917 --> 01:15:48.298
be some out there where you could just

01:15:48.359 --> 01:15:51.761
like remove a fuse or like disconnect a

01:15:51.801 --> 01:15:54.301
module and and lose that functionality and

01:15:54.341 --> 01:15:57.502
they they might be options to explore and

01:15:57.622 --> 01:15:59.104
i think doing more research into that

01:16:00.140 --> 01:16:01.119
would be pretty useful.

01:16:01.260 --> 01:16:02.720
So we should think about that.

01:16:03.301 --> 01:16:04.761
Username is not what's bad about five G

01:16:04.801 --> 01:16:05.141
exactly.

01:16:05.221 --> 01:16:07.162
I think just any connectivity,

01:16:07.222 --> 01:16:10.283
like if you could remove the connectivity

01:16:10.323 --> 01:16:11.043
features of your,

01:16:11.203 --> 01:16:12.444
of your vehicle pretty easily,

01:16:12.545 --> 01:16:14.485
no cellular, no, no wifi.

01:16:15.845 --> 01:16:16.226
That would,

01:16:16.527 --> 01:16:17.686
that would stop a lot of these privacy

01:16:17.726 --> 01:16:18.106
problems.

01:16:18.127 --> 01:16:19.287
You'd lose functionality.

01:16:19.328 --> 01:16:21.047
So I think looking into like what

01:16:21.087 --> 01:16:22.509
functionality you,

01:16:22.569 --> 01:16:24.010
you would lose if you disconnected,

01:16:24.029 --> 01:16:26.050
that would be something to, to look into,

01:16:26.150 --> 01:16:27.810
but it would be good for privacy.

01:16:28.811 --> 01:16:29.612
If that's a possibility.

01:16:31.331 --> 01:16:32.835
Yeah, I don't know if it's true.

01:16:32.954 --> 01:16:34.920
I've heard some claims that that could

01:16:34.960 --> 01:16:36.864
potentially be like a warranty voiding

01:16:36.885 --> 01:16:37.225
thing,

01:16:37.365 --> 01:16:38.970
but also if you're buying a car

01:16:39.010 --> 01:16:40.613
secondhand, usually there is no warranty,

01:16:40.654 --> 01:16:40.793
so.

01:16:41.217 --> 01:16:42.578
yeah another thing we'd have to look into

01:16:42.597 --> 01:16:44.878
like can you easily reconnect it when you

01:16:44.918 --> 01:16:47.139
bring it in for servicing maybe and that's

01:16:47.219 --> 01:16:48.039
what i was about to say i feel

01:16:48.060 --> 01:16:50.260
like a good mechanic could probably like

01:16:50.279 --> 01:16:51.539
you said like there's probably just one

01:16:51.579 --> 01:16:53.761
cable they just pull out and you know

01:16:53.801 --> 01:16:55.400
but also a lot of the time i

01:16:55.881 --> 01:16:57.101
no offense to mechanics a lot of you

01:16:57.122 --> 01:16:58.662
guys seem to like talk down to

01:16:58.742 --> 01:17:00.662
non-mechanics well you know you're gonna

01:17:00.682 --> 01:17:02.382
lose this this and this yeah i i

01:17:02.403 --> 01:17:05.003
know just please unplug it i i did

01:17:05.043 --> 01:17:06.024
my research so

01:17:06.663 --> 01:17:09.104
I don't know, but yeah, anyways,

01:17:09.685 --> 01:17:11.284
actually we did have a couple of questions

01:17:11.324 --> 01:17:13.725
before I dive into the forum post.

01:17:14.865 --> 01:17:18.467
We had one basically, okay, sorry,

01:17:18.488 --> 01:17:21.127
I closed it out.

01:17:21.148 --> 01:17:21.689
Now I can't see it.

01:17:22.048 --> 01:17:25.229
It's basically, they found on our forum,

01:17:25.470 --> 01:17:27.050
there were some recommendations for

01:17:27.130 --> 01:17:28.770
Venadium and one of them was to turn

01:17:28.970 --> 01:17:29.890
off, do not track,

01:17:30.390 --> 01:17:32.051
but since it's on by default,

01:17:32.091 --> 01:17:34.192
wouldn't that make Venadium users stand

01:17:34.271 --> 01:17:34.792
out more?

01:17:35.672 --> 01:17:36.353
What do you think of that?

01:17:36.672 --> 01:17:40.275
That's definitely true that it could.

01:17:40.296 --> 01:17:40.956
In theory,

01:17:41.176 --> 01:17:43.639
the reality is Vanadium doesn't have

01:17:43.899 --> 01:17:47.841
billions or millions or even probably no

01:17:47.902 --> 01:17:51.664
more than like a handful of thousand

01:17:51.784 --> 01:17:52.125
users.

01:17:52.185 --> 01:17:52.385
Right.

01:17:52.786 --> 01:17:57.349
So fingerprinting is kind of already going

01:17:57.368 --> 01:17:59.190
to be an issue for a lot of

01:17:59.230 --> 01:17:59.690
people.

01:18:00.492 --> 01:18:01.351
It's not really

01:18:02.471 --> 01:18:05.132
geared to prevent fingerprinting.

01:18:05.333 --> 01:18:07.055
I think that Graphene OS has said they

01:18:07.095 --> 01:18:08.595
want to focus more on that in the

01:18:08.614 --> 01:18:08.975
future.

01:18:09.376 --> 01:18:11.176
I believe that they've said in regards to

01:18:11.197 --> 01:18:11.737
fingerprinting,

01:18:11.777 --> 01:18:14.599
it'd be cool to release Vanadium on the

01:18:14.618 --> 01:18:16.520
Play Store so other people kind of blend

01:18:16.560 --> 01:18:16.939
in with it.

01:18:16.979 --> 01:18:18.661
But the reality is with a lot of

01:18:18.680 --> 01:18:19.662
these mobile devices,

01:18:20.702 --> 01:18:23.684
it's almost impossible to prevent a lot of

01:18:23.724 --> 01:18:24.623
browser fingerprinting.

01:18:24.663 --> 01:18:27.605
And even Tor Browser on Android is not

01:18:27.966 --> 01:18:30.426
as good at preventing fingerprinting as...

01:18:32.145 --> 01:18:34.786
as it is on like desktop with mobile

01:18:34.805 --> 01:18:36.487
browser or Tor browser, for example.

01:18:36.887 --> 01:18:39.349
It's just there's too many variables.

01:18:39.889 --> 01:18:41.350
We talk about this all the time with

01:18:41.430 --> 01:18:42.409
cellular devices.

01:18:42.451 --> 01:18:44.211
They're machines that are basically built

01:18:44.671 --> 01:18:45.631
for tracking.

01:18:46.152 --> 01:18:46.393
So

01:18:47.292 --> 01:18:48.993
There's only so much that can be done

01:18:49.033 --> 01:18:51.015
with the current operating systems,

01:18:51.055 --> 01:18:51.734
unfortunately.

01:18:52.735 --> 01:18:52.935
Yeah,

01:18:53.176 --> 01:18:55.077
Jordan just said in the chat that Graphene

01:18:55.117 --> 01:18:56.677
OS has said they have around a half

01:18:56.917 --> 01:18:57.597
a million users.

01:18:57.677 --> 01:18:59.979
So yeah, in the grand scheme of things,

01:19:00.399 --> 01:19:01.859
as far as browser fingerprinting goes,

01:19:01.880 --> 01:19:04.560
that's a pretty insignificant number of

01:19:04.720 --> 01:19:05.942
users who are browsing the web.

01:19:05.981 --> 01:19:07.103
So you're going to stand out if you

01:19:07.162 --> 01:19:08.643
use Vanadium either way.

01:19:09.123 --> 01:19:09.884
I think the idea...

01:19:11.345 --> 01:19:13.305
You said this was advice from a...

01:19:14.554 --> 01:19:15.574
community wiki posts,

01:19:15.595 --> 01:19:17.996
those are obviously maybe not obviously,

01:19:18.036 --> 01:19:19.657
but those are submitted by people in our

01:19:19.697 --> 01:19:21.198
community and they're kind of collaborated

01:19:21.278 --> 01:19:22.438
on by other forum users,

01:19:22.497 --> 01:19:24.019
but they haven't been like added to our

01:19:24.059 --> 01:19:24.359
website.

01:19:24.378 --> 01:19:26.220
So this isn't a post that I've read,

01:19:26.661 --> 01:19:28.462
but I would imagine changing some of these

01:19:28.502 --> 01:19:31.342
settings may help Vanadium users blend in

01:19:31.422 --> 01:19:33.944
more with like Google Chrome users,

01:19:34.685 --> 01:19:36.006
which may be a bit more beneficial.

01:19:36.025 --> 01:19:38.567
But again, even Google Chrome users,

01:19:38.926 --> 01:19:40.287
despite there being a ton of them,

01:19:40.328 --> 01:19:41.569
because the browser is

01:19:42.509 --> 01:19:44.109
sharing so much unique information,

01:19:44.409 --> 01:19:45.729
you're still going to be fingerprintable.

01:19:45.770 --> 01:19:49.332
So it's just not a thing that really

01:19:49.412 --> 01:19:51.893
any browser on Android, to my knowledge,

01:19:52.353 --> 01:19:53.012
tackles.

01:19:53.813 --> 01:19:55.033
Tor browser might be doing the best,

01:19:55.094 --> 01:19:57.715
but there's so few Tor browser users on

01:19:57.774 --> 01:19:59.595
Android that you run into exactly the same

01:19:59.636 --> 01:19:59.895
issue.

01:19:59.935 --> 01:20:02.117
So that's not really a protection either.

01:20:02.216 --> 01:20:03.317
You're just not going to be protected from

01:20:03.337 --> 01:20:04.858
this on Android at the end of the

01:20:04.877 --> 01:20:05.057
day.

01:20:05.118 --> 01:20:05.738
That's what I would say.

01:20:06.795 --> 01:20:08.457
Another thing Jordan said that I know you

01:20:08.478 --> 01:20:09.880
kind of touched on is not everyone that

01:20:09.960 --> 01:20:11.783
uses Graphene OS uses Vanadium either,

01:20:12.002 --> 01:20:13.003
which is true.

01:20:13.045 --> 01:20:14.025
I use Brave, so yeah.

01:20:15.560 --> 01:20:15.720
Yeah,

01:20:15.819 --> 01:20:18.162
I use Brave on mobile just because I

01:20:18.181 --> 01:20:19.103
think they're the best at what they do.

01:20:19.162 --> 01:20:20.182
Yeah, Oddbyte said Brave.

01:20:20.203 --> 01:20:24.546
I use it because it syncs, you know.

01:20:24.627 --> 01:20:25.466
I don't use the sync.

01:20:25.487 --> 01:20:26.667
Oh, no?

01:20:26.787 --> 01:20:28.588
I just, I like that it has,

01:20:28.810 --> 01:20:29.810
I feel like it has the best

01:20:29.890 --> 01:20:32.091
anti-fingerprinting for an Android

01:20:32.112 --> 01:20:34.713
browser, but, you know.

01:20:34.734 --> 01:20:35.875
It's good ad blocking, too, yeah.

01:20:36.175 --> 01:20:36.875
Oh, yeah, ad blocking.

01:20:36.895 --> 01:20:38.095
I don't remember what the ad blocking

01:20:38.136 --> 01:20:40.018
situation is on Finadium, but...

01:20:41.354 --> 01:20:42.074
I heard they were going to make a

01:20:42.095 --> 01:20:43.716
change list built in,

01:20:43.756 --> 01:20:45.498
but it's not really robust.

01:20:45.658 --> 01:20:47.341
That sounds like it might be right.

01:20:48.559 --> 01:20:49.158
Um, yeah,

01:20:49.238 --> 01:20:50.619
username is nice that some websites can

01:20:50.659 --> 01:20:52.320
ignore and bypass do not track requests.

01:20:52.381 --> 01:20:53.440
And I also know that, um,

01:20:53.461 --> 01:20:55.221
there is a. Uh,

01:20:55.662 --> 01:20:57.962
I don't know if this necessarily, like,

01:20:58.042 --> 01:21:00.083
I don't know how this compares versus, um,

01:21:00.123 --> 01:21:01.265
like the idea of trying to make everybody

01:21:01.284 --> 01:21:02.145
blend in on vanadium,

01:21:02.525 --> 01:21:03.865
but do not track can also be used

01:21:04.006 --> 01:21:05.726
ironically to track people because of the

01:21:05.747 --> 01:21:06.988
way it works and the headers.

01:21:07.028 --> 01:21:08.667
And so that's typically why it is

01:21:08.688 --> 01:21:09.189
disabled.

01:21:09.748 --> 01:21:10.029
Yeah.

01:21:10.088 --> 01:21:10.349
Yeah.

01:21:10.588 --> 01:21:11.189
I was going to say that's,

01:21:11.229 --> 01:21:12.670
that's probably why we re uh,

01:21:12.869 --> 01:21:14.350
or that forum post recommended.

01:21:14.770 --> 01:21:15.971
You wouldn't want to disable it.

01:21:16.051 --> 01:21:16.993
I think it's a good point.

01:21:17.212 --> 01:21:18.213
Like in general,

01:21:18.394 --> 01:21:20.255
if the other people who use your browsers

01:21:20.296 --> 01:21:21.496
have it enabled by default,

01:21:21.515 --> 01:21:23.177
you probably wouldn't want to disable it.

01:21:23.198 --> 01:21:24.118
But I think in this case,

01:21:24.158 --> 01:21:26.841
it probably doesn't matter too much in the

01:21:26.860 --> 01:21:27.701
grand scheme of things.

01:21:27.740 --> 01:21:30.082
So as

01:21:32.244 --> 01:21:33.286
Yeah, who said that?

01:21:33.305 --> 01:21:34.828
Where did that chat go?

01:21:35.007 --> 01:21:37.390
Well, it doesn't matter.

01:21:37.510 --> 01:21:41.914
The do not track setting is ignored by

01:21:41.975 --> 01:21:44.256
sites because, yeah, that one.

01:21:45.497 --> 01:21:47.380
Because it's not a legal requirement.

01:21:47.460 --> 01:21:47.619
I mean,

01:21:47.659 --> 01:21:49.362
it's just kind of a request that you

01:21:49.402 --> 01:21:49.542
make.

01:21:49.622 --> 01:21:52.342
There is a new standard,

01:21:52.382 --> 01:21:53.703
I think it's called GPC,

01:21:53.722 --> 01:21:54.842
Global Privacy Control,

01:21:54.863 --> 01:21:56.484
but I could be wrong about that.

01:21:56.503 --> 01:21:58.743
But the nice thing about that one,

01:21:58.963 --> 01:21:59.743
in theory,

01:21:59.884 --> 01:22:02.664
is that in states like California,

01:22:02.685 --> 01:22:03.444
for example,

01:22:03.545 --> 01:22:05.485
in other regions where there are stronger

01:22:05.525 --> 01:22:06.365
privacy laws,

01:22:06.865 --> 01:22:09.907
they've decided that this setting is...

01:22:11.087 --> 01:22:13.507
considered a legally binding request,

01:22:13.547 --> 01:22:16.670
whereas Do Not Track isn't because there's

01:22:16.710 --> 01:22:20.631
some like requirements on how GPC is used.

01:22:20.692 --> 01:22:22.993
It can't be like enabled by default on

01:22:23.134 --> 01:22:23.833
standard browsers.

01:22:23.854 --> 01:22:25.515
People have to opt into it.

01:22:25.574 --> 01:22:28.457
So that's more like an affirmative choice.

01:22:28.577 --> 01:22:29.777
I think a big problem with Do Not

01:22:29.817 --> 01:22:32.038
Track is that like it just got enabled

01:22:32.479 --> 01:22:36.180
on Firefox, for example, by default,

01:22:36.220 --> 01:22:37.782
and then everyone was using it and then

01:22:38.905 --> 01:22:41.247
Nobody really respected that request or

01:22:41.306 --> 01:22:42.846
checked it because they wanted to track a

01:22:42.867 --> 01:22:43.846
bunch of Firefox users.

01:22:44.127 --> 01:22:45.747
Probably back in the day when a lot

01:22:45.787 --> 01:22:46.787
of people use Firefox.

01:22:46.868 --> 01:22:48.787
Now Firefox would probably get away with

01:22:48.828 --> 01:22:49.807
enabling it by default,

01:22:49.887 --> 01:22:52.309
arguing that most Firefox users care about

01:22:52.328 --> 01:22:52.729
privacy.

01:22:52.788 --> 01:22:54.769
But there was a time where people used

01:22:54.809 --> 01:22:58.409
Firefox for non-privacy reasons back in

01:22:58.430 --> 01:22:58.810
the day.

01:22:58.949 --> 01:23:00.670
But I think those people are few and

01:23:00.689 --> 01:23:02.430
far between now, unfortunately.

01:23:03.557 --> 01:23:03.637
Well,

01:23:03.658 --> 01:23:05.720
what's funny is I think Brave enables GPC

01:23:05.880 --> 01:23:07.041
by default, but yeah,

01:23:07.060 --> 01:23:08.261
that's another video idea I've submitted

01:23:08.322 --> 01:23:09.542
but we haven't gotten around to.

01:23:10.003 --> 01:23:12.005
Because if you market your browser as

01:23:12.045 --> 01:23:13.386
specifically for privacy,

01:23:14.087 --> 01:23:16.349
everywhere on Brave it's the privacy

01:23:16.389 --> 01:23:16.890
browser.

01:23:16.949 --> 01:23:19.112
So people are opting into it because they

01:23:19.152 --> 01:23:20.533
downloaded a privacy browser.

01:23:20.592 --> 01:23:23.855
But even Firefox probably couldn't justify

01:23:23.876 --> 01:23:25.716
enabling it by default and Chrome

01:23:25.756 --> 01:23:26.337
certainly couldn't.

01:23:27.779 --> 01:23:30.542
you can't say this person specifically

01:23:30.582 --> 01:23:31.363
requested privacy.

01:23:31.462 --> 01:23:32.685
Would it be nice if we just had

01:23:32.725 --> 01:23:34.166
data privacy laws that you don't have to

01:23:34.246 --> 01:23:34.766
opt into?

01:23:35.427 --> 01:23:36.548
Yes, that would be awesome.

01:23:36.609 --> 01:23:40.713
But yeah, we don't.

01:23:41.014 --> 01:23:42.636
Fair.

01:23:43.877 --> 01:23:44.136
Yeah.

01:23:44.176 --> 01:23:46.940
Somebody said Vanadium uses easy list and-

01:23:49.248 --> 01:23:50.389
Yeah, I think that's about it.

01:23:51.810 --> 01:23:52.890
There was another question from that

01:23:52.949 --> 01:23:53.690
person real quick.

01:23:53.711 --> 01:23:54.671
We'll just run through these.

01:23:56.150 --> 01:23:56.671
Basically,

01:23:57.631 --> 01:23:59.092
if I enable some hardening exploit

01:23:59.113 --> 01:24:00.212
protection on Graphene OS,

01:24:00.273 --> 01:24:02.234
when should I enable it for specific apps?

01:24:02.753 --> 01:24:03.573
In my experience,

01:24:03.654 --> 01:24:05.515
you should enable it by default.

01:24:06.855 --> 01:24:08.337
I've only ever had to,

01:24:08.537 --> 01:24:09.738
I kind of bounce around between a lot

01:24:09.757 --> 01:24:11.520
of different operating systems to keep

01:24:11.619 --> 01:24:12.060
testing them.

01:24:12.820 --> 01:24:13.381
In my experience,

01:24:13.400 --> 01:24:15.363
I've only ever had to disable exploit

01:24:15.403 --> 01:24:18.105
protection once and it was with Apple

01:24:18.145 --> 01:24:19.087
Music because it was,

01:24:19.266 --> 01:24:20.488
for some reason it started giving me a

01:24:20.547 --> 01:24:21.948
lot of trouble about like,

01:24:22.649 --> 01:24:24.011
it wouldn't let me sign in and then

01:24:24.030 --> 01:24:24.971
when I did sign in,

01:24:25.072 --> 01:24:27.673
it like wouldn't find my library and then

01:24:27.713 --> 01:24:28.015
like,

01:24:28.654 --> 01:24:29.956
It wouldn't download music.

01:24:30.317 --> 01:24:31.738
It was giving me all kinds of errors.

01:24:32.219 --> 01:24:32.759
And finally,

01:24:32.779 --> 01:24:34.240
when I disabled exploit protection,

01:24:34.360 --> 01:24:35.402
suddenly it worked perfectly.

01:24:35.622 --> 01:24:36.842
So, I don't know.

01:24:37.182 --> 01:24:38.264
I would use a whitelist approach,

01:24:38.304 --> 01:24:38.725
personally.

01:24:39.185 --> 01:24:40.527
Every other app I've ever tried has worked

01:24:40.546 --> 01:24:40.987
just fine.

01:24:41.627 --> 01:24:42.729
Yeah.

01:24:43.229 --> 01:24:44.570
I enabled all of them by default,

01:24:44.610 --> 01:24:46.412
and I have not run into any issues

01:24:46.492 --> 01:24:47.654
on my Pixel.

01:24:48.154 --> 01:24:48.654
I would say...

01:24:51.025 --> 01:24:52.207
If you can deal with that pop-up,

01:24:52.247 --> 01:24:53.748
there are definitely a few apps where I

01:24:53.948 --> 01:24:55.990
open them and I get that pop-up,

01:24:56.230 --> 01:24:57.752
but nothing really seems to change.

01:24:57.891 --> 01:24:59.793
I think that gallery app,

01:24:59.934 --> 01:25:03.056
Avis Gallery or whatever it's called,

01:25:03.537 --> 01:25:05.618
has this issue where sometimes I open it,

01:25:05.639 --> 01:25:07.621
that pops up, but it's perfectly fine.

01:25:08.081 --> 01:25:09.323
And if you can kind of just deal

01:25:09.342 --> 01:25:10.423
with that pop-up, then it's...

01:25:11.106 --> 01:25:11.506
whatever.

01:25:11.827 --> 01:25:12.306
But also,

01:25:12.327 --> 01:25:14.908
if you get that pop-up and functionality

01:25:14.948 --> 01:25:16.908
is clearly impacted,

01:25:16.948 --> 01:25:18.328
you can consider disabling it.

01:25:18.368 --> 01:25:19.748
It just depends on how much you trust

01:25:20.029 --> 01:25:20.710
that app, right?

01:25:20.750 --> 01:25:21.510
It's just a sign.

01:25:22.529 --> 01:25:25.110
I wouldn't disable these features every

01:25:25.150 --> 01:25:27.652
time an app breaks or crashes because I

01:25:27.692 --> 01:25:28.372
think it's a good...

01:25:29.403 --> 01:25:31.604
point in time to evaluate whether you need

01:25:31.623 --> 01:25:32.965
this app in the first place or whether

01:25:32.984 --> 01:25:34.465
you can find an alternative that's not

01:25:34.484 --> 01:25:35.886
going to break because of security

01:25:35.926 --> 01:25:36.326
features.

01:25:36.945 --> 01:25:38.766
But if you really do need this app,

01:25:38.806 --> 01:25:41.507
then the whitelist approach,

01:25:41.528 --> 01:25:42.548
like you said, Nate,

01:25:43.628 --> 01:25:44.229
is the way to go,

01:25:44.248 --> 01:25:45.590
where you just have everything enabled by

01:25:45.630 --> 01:25:47.390
default and just disable it very

01:25:47.430 --> 01:25:48.011
selectively.

01:25:49.439 --> 01:25:50.461
Oddbite also read my mind.

01:25:50.520 --> 01:25:52.082
Oddbite said you can disable the pop up,

01:25:53.162 --> 01:25:54.645
which honestly is what I do, because,

01:25:54.704 --> 01:25:56.586
yeah, it shows up all the time.

01:25:56.867 --> 01:25:59.149
And then but there's like never a

01:25:59.189 --> 01:26:00.130
functionality issue.

01:26:00.189 --> 01:26:01.791
It's so yeah,

01:26:01.871 --> 01:26:03.252
you just had at least one if you

01:26:03.292 --> 01:26:03.472
have.

01:26:04.212 --> 01:26:04.833
I was going to say,

01:26:04.854 --> 01:26:06.414
I think I have at least one functionality

01:26:06.454 --> 01:26:06.614
issue.

01:26:06.676 --> 01:26:07.676
I don't remember what it was, though.

01:26:07.756 --> 01:26:08.877
But yeah,

01:26:08.898 --> 01:26:10.498
like I also just said that that's usually

01:26:10.538 --> 01:26:11.500
used by tracking SDKs.

01:26:11.539 --> 01:26:13.140
I think that that's most of the reason

01:26:13.161 --> 01:26:13.742
that it pops up.

01:26:14.101 --> 01:26:15.363
Can you disable that pop up?

01:26:16.203 --> 01:26:17.886
for a specific app or can you just

01:26:17.905 --> 01:26:20.087
disable the pop-up from the system in

01:26:20.146 --> 01:26:20.507
general?

01:26:20.528 --> 01:26:21.548
Because that's what I would wonder.

01:26:21.769 --> 01:26:24.951
I would still want the pop-up for some

01:26:25.011 --> 01:26:25.372
apps,

01:26:25.851 --> 01:26:27.033
but if it was an issue with a

01:26:27.073 --> 01:26:28.413
specific app, I'd want to turn it off.

01:26:28.734 --> 01:26:30.515
But I've never looked into disabling it.

01:26:30.536 --> 01:26:32.238
I can't remember.

01:26:32.257 --> 01:26:33.057
They're saying per app.

01:26:33.078 --> 01:26:34.338
They're saying per app in the chat.

01:26:34.418 --> 01:26:35.800
So great.

01:26:35.841 --> 01:26:36.501
That's a great option.

01:26:38.515 --> 01:26:39.615
All right, and then last one,

01:26:39.636 --> 01:26:40.356
this one's really quick.

01:26:40.436 --> 01:26:41.636
Is there a difference between wired and

01:26:41.657 --> 01:26:42.997
wireless headphones security-wise?

01:26:43.077 --> 01:26:43.837
Generally speaking,

01:26:44.016 --> 01:26:45.337
wired is going to be more secure.

01:26:45.717 --> 01:26:47.238
We did, I think last week, actually,

01:26:47.297 --> 01:26:49.559
we did cover an attack that also works

01:26:49.599 --> 01:26:51.198
on wired headphones because it targets the

01:26:51.259 --> 01:26:52.520
actual analog components.

01:26:53.539 --> 01:26:53.819
But yeah,

01:26:53.960 --> 01:26:55.320
usually when there's security issues,

01:26:55.381 --> 01:26:56.940
it has to do with the Bluetooth of

01:26:57.020 --> 01:26:57.780
wireless headphones.

01:26:58.180 --> 01:27:00.002
Yeah, I mean, Bluetooth is just not a...

01:27:01.262 --> 01:27:02.225
very private standard.

01:27:02.905 --> 01:27:04.228
And anytime you're like, I mean,

01:27:04.247 --> 01:27:05.130
it's radio waves,

01:27:05.189 --> 01:27:07.793
this can be picked up by somebody if

01:27:07.833 --> 01:27:08.695
they have the equipment.

01:27:09.377 --> 01:27:10.639
Yeah.

01:27:12.189 --> 01:27:12.409
for sure.

01:27:12.430 --> 01:27:13.050
All right.

01:27:13.470 --> 01:27:14.430
On that note, uh,

01:27:14.470 --> 01:27:17.110
we'll get into the forum post here, which,

01:27:17.171 --> 01:27:18.231
uh, this is a forum discussion.

01:27:18.252 --> 01:27:18.692
It was actually,

01:27:18.731 --> 01:27:20.231
I think our most popular forum discussion

01:27:20.252 --> 01:27:22.412
this week is how often are people sending

01:27:22.512 --> 01:27:23.493
encrypted emails?

01:27:23.512 --> 01:27:23.552
Um,

01:27:23.573 --> 01:27:25.292
so I'm not going to read any specific

01:27:25.592 --> 01:27:27.514
messages here because basically the whole

01:27:27.533 --> 01:27:28.673
thread of it was somebody was like,

01:27:28.774 --> 01:27:30.274
I feel like a lot of the people

01:27:30.354 --> 01:27:32.295
I email are using like Gmail or outlook

01:27:32.314 --> 01:27:34.815
or Yahoo and everybody else kind of just,

01:27:34.935 --> 01:27:37.355
uh, um, agreeing like, yeah, everyone I,

01:27:37.516 --> 01:27:39.056
I email is, is, uh,

01:27:39.537 --> 01:27:40.898
using one of these mainstream providers

01:27:41.238 --> 01:27:42.519
there was some discussion about like you

01:27:42.538 --> 01:27:44.921
know should you like teaching people how

01:27:44.940 --> 01:27:46.301
to use mail envelope or how it comes

01:27:46.341 --> 01:27:48.403
built in with like firefox or uh not

01:27:48.422 --> 01:27:51.925
firefox um thunderbird and uh i saw some

01:27:51.944 --> 01:27:53.466
people said that they've actually stopped

01:27:53.586 --> 01:27:55.327
using encrypted email providers for that

01:27:55.606 --> 01:27:58.389
reason specifically but i don't know i uh

01:27:58.408 --> 01:27:59.510
i also wanted to talk about this because

01:27:59.590 --> 01:28:01.831
i have opinions about this and uh i

01:28:01.871 --> 01:28:02.452
actually don't know

01:28:04.056 --> 01:28:05.757
I'm assuming you are probably on the same

01:28:05.778 --> 01:28:06.597
page as me with this one,

01:28:06.658 --> 01:28:08.358
but in your opinion,

01:28:08.457 --> 01:28:09.878
is there a point to using an encrypted

01:28:09.918 --> 01:28:11.479
email provider even if nobody else is?

01:28:12.159 --> 01:28:12.420
Yeah.

01:28:12.560 --> 01:28:14.619
I think we hammered this down pretty hard

01:28:14.659 --> 01:28:15.740
on our website actually,

01:28:15.820 --> 01:28:18.541
but the main reason we recommend these

01:28:18.582 --> 01:28:21.181
providers is their protection at rest,

01:28:21.221 --> 01:28:24.162
and especially if you can prevent the

01:28:24.203 --> 01:28:26.003
provider from having the keys to open

01:28:26.024 --> 01:28:27.043
that, that would be great.

01:28:27.104 --> 01:28:28.384
A lot of people will say, well,

01:28:28.404 --> 01:28:30.125
your data is encrypted by email.

01:28:30.244 --> 01:28:32.127
Google and their servers because they use

01:28:32.186 --> 01:28:32.846
disk encryption.

01:28:32.867 --> 01:28:34.268
But Google has the keys to unlock it.

01:28:34.307 --> 01:28:36.149
So how secure is that really?

01:28:36.170 --> 01:28:36.970
Whereas with Proton,

01:28:37.010 --> 01:28:39.591
you have the key to unlock it and

01:28:39.612 --> 01:28:40.292
they can't do it.

01:28:40.412 --> 01:28:42.914
And I think that in terms of long

01:28:42.954 --> 01:28:44.076
term storage of emails,

01:28:44.115 --> 01:28:45.636
you might be emailed a lot of sensitive

01:28:45.657 --> 01:28:46.137
information.

01:28:46.158 --> 01:28:48.840
You're certainly emailed like a lot of

01:28:48.859 --> 01:28:49.961
account related stuff.

01:28:50.720 --> 01:28:52.703
But like I almost never

01:28:54.250 --> 01:28:55.912
use email for communication because

01:28:55.932 --> 01:28:56.894
there's no point to it.

01:28:56.953 --> 01:28:58.336
And we really, I think,

01:28:59.037 --> 01:29:01.140
discourage people from using email for

01:29:01.180 --> 01:29:03.162
communication in general.

01:29:04.305 --> 01:29:04.645
And so

01:29:06.804 --> 01:29:08.385
I think we're not really pushing for a

01:29:08.425 --> 01:29:10.846
lot of end-to-end encryption for email

01:29:10.886 --> 01:29:13.309
just because there are much better

01:29:13.708 --> 01:29:15.109
platforms to use if you want to

01:29:15.130 --> 01:29:16.310
communicate securely.

01:29:17.952 --> 01:29:19.972
Whereas I just use it as an inbox

01:29:19.993 --> 01:29:21.234
for all the accounts that I have.

01:29:21.293 --> 01:29:24.416
And having that data encrypted at rest is

01:29:25.676 --> 01:29:26.997
very important to me.

01:29:27.698 --> 01:29:28.859
And that has nothing to do with the

01:29:28.939 --> 01:29:29.939
end-to-end encrypted stuff.

01:29:31.661 --> 01:29:32.021
Anyways,

01:29:32.221 --> 01:29:34.002
what I would say is it's probably a

01:29:34.042 --> 01:29:36.265
good thing that we're not focusing so much

01:29:36.305 --> 01:29:38.426
on end-to-end encryption in email because

01:29:38.546 --> 01:29:41.268
I think everyone should spend their time

01:29:42.109 --> 01:29:43.670
switching to better instant messengers

01:29:43.689 --> 01:29:46.131
like Signal instead of working on that.

01:29:48.001 --> 01:29:48.582
Yeah, for sure.

01:29:49.002 --> 01:29:50.042
I feel kind of the same way.

01:29:50.182 --> 01:29:50.884
It's to me,

01:29:51.503 --> 01:29:52.425
I think of it in terms of like

01:29:52.444 --> 01:29:53.005
a data breach.

01:29:53.045 --> 01:29:53.605
Like, okay,

01:29:54.667 --> 01:29:57.109
if I'm using Proton or Tudor and I'm

01:29:57.149 --> 01:29:58.369
communicating with people who are using

01:29:58.430 --> 01:29:59.871
Gmail and Outlook and whatnot,

01:30:00.212 --> 01:30:02.434
if that person has a data breach, yes,

01:30:02.533 --> 01:30:04.454
my correspondence with them is going to be

01:30:04.515 --> 01:30:04.775
leaked,

01:30:05.256 --> 01:30:06.617
But it's not gonna be my whole inbox.

01:30:06.657 --> 01:30:07.037
Like you said,

01:30:07.198 --> 01:30:10.440
it's not gonna be my doctor's office,

01:30:10.480 --> 01:30:12.863
my bank, all these different things.

01:30:12.903 --> 01:30:13.823
That's not gonna be in there.

01:30:13.863 --> 01:30:15.585
It's going to be my communication with

01:30:15.604 --> 01:30:16.966
them, which may still be bad,

01:30:17.046 --> 01:30:18.287
but it's not as bad.

01:30:18.747 --> 01:30:19.047
And to me,

01:30:19.069 --> 01:30:20.390
it's also cutting the risk in half

01:30:20.430 --> 01:30:21.371
because, like you said,

01:30:21.911 --> 01:30:23.533
my inbox is still encrypted at rest.

01:30:24.193 --> 01:30:26.533
And that can't be as easily breached as

01:30:26.594 --> 01:30:28.293
something like Gmail or Outlook,

01:30:28.434 --> 01:30:29.154
especially Outlook.

01:30:30.154 --> 01:30:32.534
So it's again, yeah,

01:30:32.595 --> 01:30:33.755
it's not a perfect solution,

01:30:33.795 --> 01:30:35.615
but it's a it's a risk reduction solution.

01:30:35.655 --> 01:30:36.775
So I still think it's worth it.

01:30:37.296 --> 01:30:38.515
Also, again, you know,

01:30:38.716 --> 01:30:42.016
these providers are not like farming your

01:30:42.136 --> 01:30:43.817
your email for marketing information,

01:30:43.896 --> 01:30:45.297
which I think Google said they stopped

01:30:45.318 --> 01:30:46.198
doing that, but whatever.

01:30:46.837 --> 01:30:48.059
And yeah, I had that in the notes,

01:30:48.099 --> 01:30:48.298
too,

01:30:48.319 --> 01:30:50.779
that email is a legacy tech to begin

01:30:50.800 --> 01:30:50.979
with.

01:30:51.020 --> 01:30:52.280
And all these things like PGP,

01:30:52.360 --> 01:30:52.921
even like Tudor,

01:30:52.981 --> 01:30:54.421
I know Tudor like has their own version

01:30:54.442 --> 01:30:55.882
of PGP where they encrypt even more

01:30:55.922 --> 01:30:56.363
metadata.

01:30:56.804 --> 01:30:58.704
But even that is still just like adding

01:30:58.765 --> 01:31:00.365
band aids on top of email.

01:31:00.466 --> 01:31:02.067
And there are better things like Signal or

01:31:02.087 --> 01:31:03.046
SimpleX or whatever.

01:31:03.146 --> 01:31:05.087
So but unfortunately,

01:31:05.127 --> 01:31:07.130
we are at a point where, you know,

01:31:07.289 --> 01:31:09.211
my bank is not going to signal me

01:31:09.411 --> 01:31:10.230
a login code.

01:31:10.270 --> 01:31:13.212
So we do still need email from time

01:31:13.252 --> 01:31:13.912
to time for sure.

01:31:13.932 --> 01:31:14.474
Yeah.

01:31:15.134 --> 01:31:15.895
Jordan just said that,

01:31:15.935 --> 01:31:17.395
but it would be nice if we could

01:31:17.456 --> 01:31:18.197
use something else,

01:31:18.337 --> 01:31:20.439
but I don't see that happening anytime

01:31:20.498 --> 01:31:21.020
soon.

01:31:21.820 --> 01:31:23.601
Yeah, Intel just said it's the standard,

01:31:23.782 --> 01:31:24.222
and it is.

01:31:24.662 --> 01:31:28.867
And it's just so entrenched in everything

01:31:28.966 --> 01:31:31.069
that it's very unlikely that we'll switch

01:31:31.109 --> 01:31:31.949
away from using it.

01:31:32.010 --> 01:31:33.952
But protecting as much as you can,

01:31:34.171 --> 01:31:34.453
I think...

01:31:36.572 --> 01:31:37.353
I think the risk of,

01:31:38.073 --> 01:31:39.493
just from a security perspective,

01:31:39.533 --> 01:31:41.534
the risk of a data breach impacting your

01:31:41.614 --> 01:31:43.555
email provider is much higher than the

01:31:43.595 --> 01:31:45.756
risk of your emails being intercepted

01:31:46.077 --> 01:31:46.537
live.

01:31:47.438 --> 01:31:49.519
That all depends on your threat model,

01:31:49.559 --> 01:31:50.019
of course,

01:31:50.139 --> 01:31:52.720
but end-to-end encryption is a huge

01:31:53.461 --> 01:31:56.362
benefit just for that data at rest against

01:31:56.402 --> 01:31:56.942
data breaches,

01:31:56.981 --> 01:31:59.262
even if it doesn't stop active attackers.

01:32:02.445 --> 01:32:04.448
Switching to something like Proton,

01:32:04.768 --> 01:32:07.289
even if you can't convince anyone else to

01:32:07.369 --> 01:32:09.872
switch, and I think somebody even said,

01:32:09.912 --> 01:32:10.731
yeah, anonymous once,

01:32:10.792 --> 01:32:12.434
I'm not going to spend time on convincing

01:32:12.474 --> 01:32:13.935
people to change email for writers.

01:32:14.095 --> 01:32:14.274
Yeah,

01:32:14.395 --> 01:32:16.015
I think that's not the best use of

01:32:16.077 --> 01:32:17.056
anyone's time, but...

01:32:18.418 --> 01:32:19.961
It would be great if people switch because

01:32:20.161 --> 01:32:21.563
it would secure their own emails.

01:32:22.083 --> 01:32:24.046
And just from a personal perspective,

01:32:24.766 --> 01:32:25.849
it's one of those things where if you

01:32:25.889 --> 01:32:27.070
switch, you benefit a lot,

01:32:27.270 --> 01:32:28.332
even if nobody else uses it.

01:32:28.813 --> 01:32:30.215
I think that's a problem that we have

01:32:30.234 --> 01:32:32.137
with instant messengers when we think

01:32:32.158 --> 01:32:33.899
about Signal or SimpleX.

01:32:35.442 --> 01:32:36.844
like you don't get a lot of benefit

01:32:36.863 --> 01:32:38.824
from Signal if nobody else is using

01:32:38.886 --> 01:32:39.185
Signal.

01:32:39.206 --> 01:32:41.007
So there's more of that problem,

01:32:41.047 --> 01:32:43.170
but there's a clear benefit to switching

01:32:43.189 --> 01:32:45.752
to a more private, secure email provider.

01:32:46.972 --> 01:32:48.475
So yeah, highly recommend.

01:32:49.689 --> 01:32:49.890
Yeah,

01:32:49.909 --> 01:32:51.451
that's something I think about that I'm

01:32:51.711 --> 01:32:53.030
probably gonna write a blog post at some

01:32:53.070 --> 01:32:54.291
point about is like there's certain

01:32:54.371 --> 01:32:56.851
privacy actions that do require you to get

01:32:56.872 --> 01:32:58.132
other people to change, like you said,

01:32:58.153 --> 01:32:59.313
like using Signal or something.

01:32:59.752 --> 01:33:00.733
But then there's a lot of things that

01:33:00.813 --> 01:33:03.394
you can do yourself that don't depend on

01:33:03.453 --> 01:33:04.134
anybody else.

01:33:04.194 --> 01:33:06.154
Like you can switch to Brave or Firefox.

01:33:06.194 --> 01:33:08.216
You can switch to Linux if you can

01:33:08.256 --> 01:33:09.015
afford to do that.

01:33:11.076 --> 01:33:11.277
Yeah,

01:33:11.296 --> 01:33:12.476
you can switch to a private email

01:33:12.516 --> 01:33:12.957
provider.

01:33:13.016 --> 01:33:14.296
Like there's a lot of privacy stuff you

01:33:14.337 --> 01:33:15.797
can do on your own for sure, so.

01:33:17.091 --> 01:33:18.712
Anyways, on that note,

01:33:19.193 --> 01:33:20.774
I'm going to turn things over to you

01:33:20.814 --> 01:33:22.216
now and you can tell us all about

01:33:22.256 --> 01:33:23.557
this new attack.

01:33:24.399 --> 01:33:26.442
This is actually our last story of the

01:33:26.462 --> 01:33:26.702
day.

01:33:26.761 --> 01:33:28.162
So if anybody has been holding on to

01:33:28.203 --> 01:33:29.564
any questions that you haven't asked yet,

01:33:29.604 --> 01:33:32.167
please do drop those in the chat and

01:33:32.228 --> 01:33:33.630
Jonah will tell us all about this new

01:33:33.649 --> 01:33:33.970
attack.

01:33:35.324 --> 01:33:36.546
Yeah, Fria wrote this article,

01:33:36.605 --> 01:33:38.407
new attack can track you across operating

01:33:38.426 --> 01:33:40.207
systems without elevated privileges.

01:33:40.226 --> 01:33:41.967
Fria, sorry,

01:33:43.908 --> 01:33:45.930
researchers at the Graz University of

01:33:46.050 --> 01:33:48.091
Technology Austria demonstrated a new

01:33:48.110 --> 01:33:50.212
attack that can track you via file change

01:33:50.252 --> 01:33:52.372
events on all systems allowing for various

01:33:52.453 --> 01:33:52.934
data leaks.

01:33:53.514 --> 01:33:55.314
They say that modern operating systems

01:33:55.335 --> 01:33:55.835
like Linux,

01:33:55.875 --> 01:33:57.555
Windows and Mac OS provide built in

01:33:57.595 --> 01:34:00.337
subsystems to monitor file system events.

01:34:00.777 --> 01:34:03.378
I notify redirectory changes to view NFS

01:34:03.418 --> 01:34:03.759
events.

01:34:04.559 --> 01:34:05.579
User processes,

01:34:06.001 --> 01:34:08.382
programs on your computer can subscribe to

01:34:08.443 --> 01:34:10.824
receive file operation notifications when

01:34:11.484 --> 01:34:13.266
actions like accessing, writing,

01:34:13.386 --> 01:34:16.029
opening and closing are performed on a

01:34:16.189 --> 01:34:18.070
monitored file or directory.

01:34:19.712 --> 01:34:21.713
And so the research paper that was

01:34:21.953 --> 01:34:23.814
published essentially points out that

01:34:23.854 --> 01:34:27.478
these tools can be used by programs to

01:34:27.518 --> 01:34:28.538
read information about

01:34:29.659 --> 01:34:31.682
large number of operating system files and

01:34:31.743 --> 01:34:33.425
other files on your computer.

01:34:33.484 --> 01:34:36.667
A lot of these files that can be

01:34:37.128 --> 01:34:39.912
read or that you can monitor events for

01:34:42.578 --> 01:34:44.279
can be read by any program without any

01:34:44.319 --> 01:34:45.319
special privileges.

01:34:45.420 --> 01:34:47.560
I saw people talking about this story on

01:34:48.240 --> 01:34:50.822
Reddit on the r slash privacy subreddit.

01:34:51.202 --> 01:34:53.162
And I think people were like, well,

01:34:53.182 --> 01:34:54.342
this attack can only be,

01:34:56.083 --> 01:34:58.145
it only matters if you're like locally

01:34:58.204 --> 01:34:58.885
running software.

01:34:58.904 --> 01:35:01.006
It's not like an attack you can get

01:35:01.065 --> 01:35:01.765
over the internet.

01:35:01.845 --> 01:35:03.686
But I didn't really understand that

01:35:03.726 --> 01:35:05.908
argument because malware exists.

01:35:05.927 --> 01:35:08.148
People are downloading software on their

01:35:08.167 --> 01:35:09.349
computers all the times and this,

01:35:10.109 --> 01:35:14.390
I think it gives any malware a large

01:35:14.409 --> 01:35:17.411
amount of insight into your system and

01:35:17.430 --> 01:35:22.132
what's running on it without that malware

01:35:22.172 --> 01:35:24.412
needing any special permissions other than

01:35:24.453 --> 01:35:25.434
just running on your device.

01:35:25.453 --> 01:35:26.774
So it's not something that would need to

01:35:27.134 --> 01:35:29.975
escalate to admin privileges.

01:35:30.154 --> 01:35:32.036
And according to the researchers in this

01:35:32.076 --> 01:35:32.416
paper,

01:35:32.496 --> 01:35:34.837
it leaks a lot of information that

01:35:37.225 --> 01:35:38.886
like more information than you would

01:35:38.926 --> 01:35:39.167
think.

01:35:39.266 --> 01:35:41.487
So it says on Linux,

01:35:41.506 --> 01:35:43.387
they were able to achieve a keystroke

01:35:43.427 --> 01:35:44.087
timing attack,

01:35:45.587 --> 01:35:47.069
which is a type of side channel attack

01:35:47.088 --> 01:35:48.889
that measures the timing between key

01:35:48.929 --> 01:35:50.750
presses in order to infer information

01:35:50.789 --> 01:35:51.869
about the text being typed,

01:35:51.909 --> 01:35:53.030
including the actual text.

01:35:54.831 --> 01:35:56.452
That attack could potentially leak

01:35:56.572 --> 01:35:59.052
passwords or sensitive text being typed,

01:35:59.073 --> 01:36:00.393
such as private messages.

01:36:00.853 --> 01:36:02.493
They were also able to perform a

01:36:02.573 --> 01:36:04.055
fingerprinting attack on the top one

01:36:04.074 --> 01:36:04.814
hundred websites,

01:36:04.835 --> 01:36:06.414
since visiting certain websites would

01:36:06.475 --> 01:36:09.317
trigger specific access patterns for fonts

01:36:09.476 --> 01:36:10.817
in the fonts directory.

01:36:10.896 --> 01:36:12.137
So from just this alone,

01:36:12.177 --> 01:36:14.057
an attacker can figure out what websites

01:36:14.078 --> 01:36:14.599
you're visiting,

01:36:14.639 --> 01:36:15.118
basically

01:36:16.479 --> 01:36:18.380
malware running on your computer without

01:36:18.420 --> 01:36:19.899
any access to your browser at all,

01:36:20.260 --> 01:36:21.520
because it's sandbox,

01:36:21.541 --> 01:36:23.680
can see whether you're accessing a certain

01:36:23.761 --> 01:36:25.162
site, like a major one,

01:36:25.202 --> 01:36:27.403
or at least guess and potentially track

01:36:27.422 --> 01:36:30.622
you based on just files in the operating

01:36:30.663 --> 01:36:34.685
system that can be read by pretty much

01:36:34.805 --> 01:36:36.145
any software running on your device.

01:36:36.185 --> 01:36:38.905
So I think it is a concerning problem.

01:36:39.225 --> 01:36:41.287
And the paper also goes into

01:36:42.426 --> 01:36:44.688
similar attacks to that on on Android,

01:36:44.728 --> 01:36:45.868
on Windows, on Mac OS.

01:36:46.048 --> 01:36:49.130
So, yeah, if you read this article,

01:36:49.149 --> 01:36:50.831
you can read some specific attacks in the

01:36:50.871 --> 01:36:52.412
paper is is linked.

01:36:52.631 --> 01:36:55.172
But I think that that is kind of

01:36:55.193 --> 01:36:56.854
the the situation there.

01:36:59.034 --> 01:36:59.694
So, yeah.

01:36:59.716 --> 01:37:01.376
Do you have any thoughts about like the

01:37:01.416 --> 01:37:03.436
malware running on your computer side of

01:37:03.476 --> 01:37:04.518
things or anything like that?

01:37:05.751 --> 01:37:07.492
Well, I do want to answer,

01:37:08.113 --> 01:37:09.233
username is Nye, said,

01:37:09.373 --> 01:37:10.713
is this article peer-reviewed?

01:37:11.635 --> 01:37:12.376
I don't think so,

01:37:12.416 --> 01:37:13.496
but it is kind of confirmed.

01:37:13.617 --> 01:37:14.997
The last sentence of the article says,

01:37:15.118 --> 01:37:15.698
in particular,

01:37:15.738 --> 01:37:17.219
Microsoft stated that the private data

01:37:17.259 --> 01:37:18.720
leakage was actually there by design,

01:37:19.300 --> 01:37:21.421
which is a pretty insane thing to say,

01:37:21.502 --> 01:37:21.902
but whatever.

01:37:23.002 --> 01:37:24.724
Yeah, I think, to me,

01:37:25.185 --> 01:37:26.345
the thing that stuck out to me, so,

01:37:26.465 --> 01:37:27.905
okay,

01:37:27.987 --> 01:37:29.067
I know this was an hour and a

01:37:29.087 --> 01:37:29.408
half ago,

01:37:30.268 --> 01:37:32.069
but at the beginning of the live stream,

01:37:32.128 --> 01:37:32.670
I talked about

01:37:34.610 --> 01:37:36.532
that video from Side of Burritos where he

01:37:36.631 --> 01:37:38.592
demonstrated how the secure clipboard

01:37:38.632 --> 01:37:39.372
works on graphene.

01:37:40.212 --> 01:37:41.873
And one thing he pointed out is that

01:37:41.894 --> 01:37:44.715
there are certain apps that as soon as

01:37:44.734 --> 01:37:46.235
you copy something to the clipboard,

01:37:46.775 --> 01:37:47.936
as soon as you open the app,

01:37:47.957 --> 01:37:48.976
before you even hit paste,

01:37:49.037 --> 01:37:50.618
they already read what's on the clipboard.

01:37:52.217 --> 01:37:52.958
So if you've got,

01:37:53.078 --> 01:37:54.319
let's say you've got three apps open,

01:37:54.498 --> 01:37:56.399
and you're trying to copy from app A

01:37:56.420 --> 01:37:57.180
to app C,

01:37:57.239 --> 01:37:59.121
but you accidentally open app B along the

01:37:59.140 --> 01:38:00.042
way for whatever reason,

01:38:00.542 --> 01:38:01.681
and it's one of those apps that does

01:38:01.702 --> 01:38:03.283
that, even though you never hit paste,

01:38:03.323 --> 01:38:04.443
it can read what's on your clipboard.

01:38:04.804 --> 01:38:06.144
So to me, and for the record,

01:38:06.163 --> 01:38:07.163
I don't think all apps do that,

01:38:07.184 --> 01:38:08.585
I'm just saying some have that capability,

01:38:08.625 --> 01:38:10.565
which is why the secure clipboard exists.

01:38:11.386 --> 01:38:11.845
So to me,

01:38:11.865 --> 01:38:13.186
that kind of reminds me of this thing,

01:38:13.567 --> 01:38:15.068
where when we talk about malware,

01:38:15.087 --> 01:38:16.528
we talk about malware, right?

01:38:16.568 --> 01:38:18.809
Like whether it's bundled in a cracked

01:38:18.849 --> 01:38:20.869
game or a phishing link or something,

01:38:21.329 --> 01:38:23.751
but I'm also thinking of just really

01:38:23.810 --> 01:38:25.771
shady, unethically acting apps,

01:38:25.811 --> 01:38:29.052
like a game you download or anything from

01:38:29.092 --> 01:38:32.194
Meta that is not technically malware,

01:38:32.253 --> 01:38:34.875
like it is not actually malware in the

01:38:34.975 --> 01:38:35.756
literal sense,

01:38:36.716 --> 01:38:38.617
But it basically behaves like malware.

01:38:38.936 --> 01:38:40.597
And now it's probing your system and doing

01:38:40.618 --> 01:38:41.219
all this stuff.

01:38:41.298 --> 01:38:42.739
And now it could potentially be picking

01:38:42.800 --> 01:38:42.899
up,

01:38:43.600 --> 01:38:44.980
even if it's hopefully not picking up your

01:38:45.020 --> 01:38:46.721
actual passwords and the messages you're

01:38:46.742 --> 01:38:47.101
texting,

01:38:47.443 --> 01:38:48.882
it could still be tracking what websites

01:38:48.903 --> 01:38:49.203
you visit.

01:38:49.224 --> 01:38:49.623
Like you said,

01:38:49.684 --> 01:38:50.944
even though the browser is sandbox,

01:38:51.324 --> 01:38:53.525
it can still use these other side channels

01:38:53.786 --> 01:38:55.346
to track what you're doing and pick up

01:38:55.386 --> 01:38:56.648
information that it's not supposed to

01:38:56.667 --> 01:38:57.007
have.

01:38:57.429 --> 01:38:58.389
And it's not a virus.

01:38:58.469 --> 01:38:59.829
It's not actual malware.

01:39:00.149 --> 01:39:01.310
It's just behaving like it.

01:39:01.371 --> 01:39:02.351
And yeah, it just...

01:39:03.091 --> 01:39:03.393
To me,

01:39:03.432 --> 01:39:04.555
that's the big thing that stuck out to

01:39:04.574 --> 01:39:04.635
me.

01:39:04.654 --> 01:39:05.577
It's like, this is a problem,

01:39:05.596 --> 01:39:06.658
and this is actually why I wanted to

01:39:06.679 --> 01:39:08.762
include it on this stream,

01:39:08.783 --> 01:39:09.524
is because it's like,

01:39:10.345 --> 01:39:11.868
this isn't strictly malware.

01:39:11.908 --> 01:39:12.329
This could be...

01:39:14.304 --> 01:39:15.305
Sorry, I know I'm rambling a little bit,

01:39:15.324 --> 01:39:17.024
but that whole thing with Signal a year

01:39:17.085 --> 01:39:19.947
ago where Signal was storing the

01:39:19.987 --> 01:39:22.387
encryption keys unencrypted on Windows

01:39:22.408 --> 01:39:23.568
devices on the desktop,

01:39:24.149 --> 01:39:25.168
and everybody was like, dude,

01:39:25.189 --> 01:39:25.488
what the heck?

01:39:25.509 --> 01:39:25.969
And they're like, well,

01:39:25.988 --> 01:39:27.050
if you have malware on your computer,

01:39:27.069 --> 01:39:27.909
you're already screwed anyways.

01:39:28.230 --> 01:39:29.211
Okay, what if I don't have malware?

01:39:29.230 --> 01:39:29.990
What if I have this?

01:39:30.471 --> 01:39:32.412
So, yeah, I don't know.

01:39:32.431 --> 01:39:32.632
To me,

01:39:32.672 --> 01:39:33.912
this is just a really important thing,

01:39:34.092 --> 01:39:36.173
and Microsoft is completely insane for

01:39:36.213 --> 01:39:36.914
saying, yeah, we know.

01:39:39.304 --> 01:39:39.724
I digress.

01:39:43.065 --> 01:39:43.485
Let's see.

01:39:43.565 --> 01:39:44.627
This sounds like a thing that does not

01:39:44.667 --> 01:39:46.387
sound bad until more research is done and

01:39:46.408 --> 01:39:48.788
then a real world targeted attack gets

01:39:48.809 --> 01:39:49.908
done to show us an actual example.

01:39:49.948 --> 01:39:50.869
Yeah, that too.

01:39:50.930 --> 01:39:51.710
Now that it's out there,

01:39:52.570 --> 01:39:53.831
how many tech bros,

01:39:54.310 --> 01:39:55.391
this will be a quick rant, I promise.

01:39:55.671 --> 01:39:58.153
How many tech bros watched Black Mirror

01:39:58.233 --> 01:39:59.014
and then went, hey,

01:39:59.054 --> 01:40:00.213
that's a good idea for a business?

01:40:00.594 --> 01:40:01.854
How many other tech bros do you think

01:40:01.875 --> 01:40:03.155
are gonna read this article and be like,

01:40:03.275 --> 01:40:05.077
ooh, build this functionality in?

01:40:05.096 --> 01:40:07.158
So yeah, pretty bad.

01:40:08.399 --> 01:40:12.471
It's a situation like this malware can't

01:40:13.409 --> 01:40:14.150
in a lot of cases,

01:40:14.270 --> 01:40:15.532
read the files involved.

01:40:15.572 --> 01:40:17.353
But if you can read all this metadata,

01:40:17.472 --> 01:40:18.613
we talk about metadata,

01:40:19.034 --> 01:40:20.576
revealing all sorts of sensitive

01:40:20.615 --> 01:40:21.617
information all the time,

01:40:21.837 --> 01:40:23.639
just in so in this case,

01:40:23.658 --> 01:40:26.280
like just the idea that software can see

01:40:26.320 --> 01:40:27.421
when you open the file,

01:40:27.481 --> 01:40:29.444
even if it knows nothing about the file

01:40:29.484 --> 01:40:29.804
itself,

01:40:29.844 --> 01:40:31.404
that can reveal a lot of information.

01:40:31.465 --> 01:40:33.806
So yeah, all of this metadata protection,

01:40:33.846 --> 01:40:34.568
I think needs to be,

01:40:35.488 --> 01:40:37.751
like always taken taken more seriously

01:40:37.791 --> 01:40:38.992
than it than it often is.

01:40:41.434 --> 01:40:41.913
I just want to say,

01:40:41.934 --> 01:40:42.935
I think I might go back and read

01:40:42.954 --> 01:40:44.395
the actual paper itself because I want to

01:40:44.416 --> 01:40:46.737
see if Microsoft justifies why this is

01:40:46.777 --> 01:40:47.617
there by design.

01:40:47.837 --> 01:40:49.557
Like, what do you, why?

01:40:49.717 --> 01:40:50.259
What purpose?

01:40:50.279 --> 01:40:50.538
I don't know.

01:40:50.559 --> 01:40:51.078
But yeah,

01:40:51.139 --> 01:40:53.520
I don't really know if there's any,

01:40:53.640 --> 01:40:55.140
because again, this doesn't necessarily,

01:40:55.180 --> 01:40:56.301
this isn't taking advantage of any

01:40:56.801 --> 01:40:57.561
vulnerabilities.

01:40:57.622 --> 01:40:58.103
This doesn't,

01:40:59.042 --> 01:41:01.984
um this isn't uh like actual malware so

01:41:02.003 --> 01:41:03.264
i don't know if there's any defenses

01:41:03.283 --> 01:41:04.965
against this other than don't use windows

01:41:05.704 --> 01:41:07.845
um but yeah just being careful what you

01:41:07.865 --> 01:41:10.587
download and run uh hopefully apple and

01:41:10.627 --> 01:41:12.447
linux will roll out some some fixes for

01:41:12.487 --> 01:41:16.988
this but yeah you got any additional

01:41:17.009 --> 01:41:21.949
thoughts uh yeah i don't think so just

01:41:22.570 --> 01:41:24.230
just goes to show that you know any

01:41:24.490 --> 01:41:26.311
any local software you run just like you

01:41:26.332 --> 01:41:26.671
said can

01:41:28.536 --> 01:41:31.259
running anything locally will give will

01:41:33.100 --> 01:41:34.742
give programs a lot of information about

01:41:34.801 --> 01:41:34.921
you,

01:41:35.061 --> 01:41:37.043
regardless of like privileges in a lot of

01:41:37.083 --> 01:41:37.384
cases,

01:41:37.423 --> 01:41:39.086
just because the operating system is so

01:41:40.346 --> 01:41:40.967
vast, right?

01:41:40.988 --> 01:41:42.588
There's so many potential things that

01:41:42.649 --> 01:41:44.711
software can access that it just isn't

01:41:44.751 --> 01:41:45.252
locked down.

01:41:45.311 --> 01:41:47.434
So being aware of that is important.

01:41:49.881 --> 01:41:52.381
Yeah, yeah, if you need further examples,

01:41:52.402 --> 01:41:54.002
y'all should look up what's going on with

01:41:54.283 --> 01:41:56.384
Meadows Muse AI on Mac.

01:41:57.885 --> 01:41:59.305
That is the gift that keeps on giving.

01:42:02.346 --> 01:42:03.226
Username is Nye said,

01:42:03.627 --> 01:42:05.108
did you watch the Hotel Reverie episode?

01:42:05.207 --> 01:42:05.509
No,

01:42:05.969 --> 01:42:08.350
I haven't watched anything since the

01:42:08.390 --> 01:42:10.511
season with Miley Cyrus doing Nine Inch

01:42:10.530 --> 01:42:11.030
Nails songs.

01:42:12.752 --> 01:42:13.712
I want to, I just,

01:42:13.792 --> 01:42:14.472
I'm not gonna lie,

01:42:16.323 --> 01:42:17.283
This is going to sound completely

01:42:17.304 --> 01:42:17.663
deranged.

01:42:18.144 --> 01:42:19.765
I miss the old Black Mirror where I

01:42:19.786 --> 01:42:21.466
would watch an episode and be like, wow,

01:42:21.487 --> 01:42:22.328
that was really good.

01:42:22.887 --> 01:42:24.770
That was also really intense and soul

01:42:24.789 --> 01:42:25.189
crushing.

01:42:25.329 --> 01:42:26.831
And I can't watch another episode for at

01:42:26.890 --> 01:42:27.492
least a week.

01:42:28.192 --> 01:42:30.234
And I miss that version of Black Mirror.

01:42:30.274 --> 01:42:31.734
Now it's more just like sci-fi,

01:42:31.814 --> 01:42:33.355
like occasionally a little bit bleak.

01:42:33.376 --> 01:42:33.716
And I'm like,

01:42:34.016 --> 01:42:35.797
like that season I mentioned,

01:42:35.997 --> 01:42:37.738
I binged that entire season in two days,

01:42:37.779 --> 01:42:40.140
which at the time I was still working

01:42:40.201 --> 01:42:41.962
like my super long hour job.

01:42:41.983 --> 01:42:43.344
So two days is really fast for me,

01:42:44.184 --> 01:42:45.104
was really fast for me.

01:42:45.164 --> 01:42:45.546
So it's like,

01:42:46.552 --> 01:42:48.134
What happened to that Black Mirror where

01:42:48.154 --> 01:42:50.194
it's like every episode crushed me

01:42:50.255 --> 01:42:50.836
internally?

01:42:50.855 --> 01:42:50.956
Yeah,

01:42:52.176 --> 01:42:54.738
I'm sure the creator of Black Mirror has

01:42:54.757 --> 01:42:57.279
definitely said this in numerous

01:42:57.340 --> 01:42:57.779
interviews.

01:42:57.859 --> 01:43:00.221
But with this type of show,

01:43:00.721 --> 01:43:03.703
you can't outpace reality at this point.

01:43:03.823 --> 01:43:05.966
It's hard to think of things that wouldn't

01:43:06.046 --> 01:43:06.786
already be done.

01:43:07.006 --> 01:43:09.167
And I think some of the most recent

01:43:09.648 --> 01:43:11.729
seasons of Black Mirror were absolutely

01:43:11.769 --> 01:43:12.270
all about that.

01:43:12.310 --> 01:43:13.630
Like that one where they made a parody

01:43:13.670 --> 01:43:14.150
of Netflix.

01:43:14.171 --> 01:43:15.391
But Netflix basically does...

01:43:16.615 --> 01:43:18.435
They're working on all the stuff in that

01:43:18.475 --> 01:43:18.796
episode.

01:43:18.817 --> 01:43:20.096
They're working on AI content.

01:43:20.117 --> 01:43:22.356
They're working on content specifically

01:43:22.396 --> 01:43:23.957
tailored to you.

01:43:27.298 --> 01:43:27.479
Yeah,

01:43:27.498 --> 01:43:29.859
I just think that we've seen a lot

01:43:29.878 --> 01:43:31.960
of the Black Mirror stuff come true.

01:43:32.039 --> 01:43:33.260
It's real products.

01:43:33.380 --> 01:43:36.701
I will say I did watch Hotel Reverie.

01:43:37.261 --> 01:43:38.161
That was a great episode.

01:43:40.442 --> 01:43:40.582
Yeah.

01:43:41.350 --> 01:43:41.692
I mean,

01:43:41.712 --> 01:43:43.092
I'm definitely planning to catch up.

01:43:43.594 --> 01:43:45.595
I've actually been the last six months or

01:43:45.615 --> 01:43:45.716
so,

01:43:45.756 --> 01:43:47.618
I've really been putting a dent in my

01:43:47.658 --> 01:43:49.041
to watch list and I've been catching up

01:43:49.100 --> 01:43:49.501
on stuff.

01:43:50.943 --> 01:43:52.284
So it's on my list.

01:43:52.345 --> 01:43:53.867
It's just not very high on my list

01:43:53.947 --> 01:43:56.789
because there's so many other things that

01:43:56.831 --> 01:43:57.570
like, you know,

01:43:58.752 --> 01:43:58.953
It's like,

01:43:58.972 --> 01:44:00.073
I've been meaning to watch this forever.

01:44:00.113 --> 01:44:01.716
I was really excited about this and I

01:44:01.735 --> 01:44:03.176
just never had time.

01:44:03.216 --> 01:44:04.738
And so, yeah,

01:44:04.797 --> 01:44:06.100
and I'll get to it eventually for sure.

01:44:06.140 --> 01:44:07.039
But yeah, I get what you mean.

01:44:07.079 --> 01:44:08.261
Like the onion is like that too.

01:44:08.301 --> 01:44:09.943
Like they have to go so ridiculously over

01:44:09.962 --> 01:44:11.904
the top now because politics has gotten so

01:44:11.925 --> 01:44:12.404
ridiculous.

01:44:12.425 --> 01:44:14.506
It's the only way they can,

01:44:14.546 --> 01:44:15.327
which that's a different thing.

01:44:15.467 --> 01:44:16.548
But Jordan said,

01:44:16.588 --> 01:44:18.250
is it really a stream if Nate doesn't

01:44:18.289 --> 01:44:18.951
talk about sci-fi?

01:44:19.051 --> 01:44:19.150
Yeah.

01:44:21.377 --> 01:44:22.217
I was actually going to throw it out

01:44:22.257 --> 01:44:22.438
there.

01:44:22.798 --> 01:44:23.720
Since it's October,

01:44:23.800 --> 01:44:24.761
I know a lot of people are doing

01:44:24.782 --> 01:44:26.002
that thirty one for thirty one thing.

01:44:26.042 --> 01:44:27.265
If you all have any horror movies you

01:44:27.284 --> 01:44:29.188
think I should check out, definitely.

01:44:31.210 --> 01:44:32.131
I don't think you can message me on

01:44:32.152 --> 01:44:32.452
the forum.

01:44:32.492 --> 01:44:33.332
I think I shut that off,

01:44:33.372 --> 01:44:34.994
but I don't know.

01:44:35.015 --> 01:44:36.377
We need to start a forum thread for

01:44:36.396 --> 01:44:36.557
this.

01:44:37.878 --> 01:44:38.158
I'm down.

01:44:38.458 --> 01:44:41.100
Yeah, leave it in this forum thread.

01:44:41.121 --> 01:44:43.221
I don't know, ping me.

01:44:43.242 --> 01:44:44.422
I don't even know what Thirty One for

01:44:44.443 --> 01:44:45.302
Thirty One is, should I?

01:44:45.323 --> 01:44:47.585
Am I missing out?

01:44:48.805 --> 01:44:49.006
I mean,

01:44:49.225 --> 01:44:50.966
I'm not going to do actual Thirty One

01:44:51.006 --> 01:44:52.528
for Thirty One because I'm just not that

01:44:52.547 --> 01:44:52.847
committed.

01:44:53.268 --> 01:44:55.689
It's basically every day of October you

01:44:55.729 --> 01:44:56.750
watch a different horror movie.

01:44:58.150 --> 01:44:58.411
And I mean,

01:44:58.511 --> 01:44:59.532
I guess the good news is you can

01:44:59.591 --> 01:45:00.091
circle back.

01:45:00.171 --> 01:45:01.712
It can be movies you've seen before.

01:45:01.853 --> 01:45:05.574
Good excuse to watch The Invisible Man

01:45:05.635 --> 01:45:05.975
again.

01:45:05.994 --> 01:45:06.756
I love that movie.

01:45:07.595 --> 01:45:09.117
That is a, oh my God,

01:45:09.176 --> 01:45:10.537
that is such a good movie.

01:45:10.837 --> 01:45:11.797
Yeah, I love that one.

01:45:11.818 --> 01:45:14.319
I don't know.

01:45:14.340 --> 01:45:15.699
I've been on kind of a horror movie

01:45:15.720 --> 01:45:15.961
kick.

01:45:16.041 --> 01:45:17.261
I finally watched Weapons.

01:45:17.581 --> 01:45:19.202
I finally watched Fall of House of Usher.

01:45:21.203 --> 01:45:21.644
I've got like,

01:45:21.743 --> 01:45:23.163
twenty minutes left on the black phone,

01:45:23.203 --> 01:45:25.725
too, because I'm just, like I said,

01:45:25.765 --> 01:45:27.207
I'm not that invested.

01:45:27.266 --> 01:45:27.386
I mean,

01:45:27.426 --> 01:45:28.726
I'm invested enough that I'm gonna finish

01:45:28.806 --> 01:45:29.467
it, but it's like, you know,

01:45:29.568 --> 01:45:30.728
I started watching it last night,

01:45:30.828 --> 01:45:31.328
and it was like,

01:45:31.969 --> 01:45:33.130
it got to be about bedtime and it

01:45:33.149 --> 01:45:34.412
was still like an hour left in the

01:45:34.431 --> 01:45:34.652
movie.

01:45:34.692 --> 01:45:35.733
And I'm like, yeah, no,

01:45:35.953 --> 01:45:37.054
I'm not that invested.

01:45:37.073 --> 01:45:37.574
I'm going to bed.

01:45:37.774 --> 01:45:38.935
And then today,

01:45:39.036 --> 01:45:40.497
Fridays are always my busy day because of

01:45:40.837 --> 01:45:41.139
the show.

01:45:41.279 --> 01:45:43.680
So username is not,

01:45:43.701 --> 01:45:45.382
the onion has no more material left.

01:45:45.422 --> 01:45:47.564
How can anybody really, I think, I mean,

01:45:47.765 --> 01:45:49.087
we definitely see that in black mirror.

01:45:49.127 --> 01:45:51.208
I think the last season of black mirror,

01:45:51.229 --> 01:45:51.349
uh,

01:45:52.229 --> 01:45:54.171
unless there's been a more recent one that

01:45:54.291 --> 01:45:55.971
i am unaware of i don't i don't

01:45:55.992 --> 01:45:58.273
know how often they make these but the

01:45:58.313 --> 01:45:59.672
last one that i saw it kind of

01:45:59.733 --> 01:46:01.753
ended on like a werewolf note like we're

01:46:01.793 --> 01:46:03.335
just getting out of sci-fi now you're kind

01:46:03.375 --> 01:46:04.895
of you're trying to spin off into a

01:46:04.954 --> 01:46:06.615
new franchise it seems like because you

01:46:06.636 --> 01:46:09.856
just can't come up with any more any

01:46:09.896 --> 01:46:12.837
more bleak tech stuff anymore i think the

01:46:12.979 --> 01:46:15.699
the tech space is just bleak as is

01:46:15.819 --> 01:46:18.121
so it's not not it's no longer

01:46:18.161 --> 01:46:18.940
groundbreaking

01:46:20.117 --> 01:46:22.219
I wonder if he's just afraid to inspire

01:46:22.259 --> 01:46:22.798
more people.

01:46:23.060 --> 01:46:24.301
Like I have a ton of ideas,

01:46:24.360 --> 01:46:25.702
but I know that they keep watching this

01:46:25.742 --> 01:46:27.143
and every time, because I'm telling you,

01:46:27.162 --> 01:46:28.623
I've seen so many news articles and it's

01:46:28.645 --> 01:46:29.164
like, oh,

01:46:29.185 --> 01:46:30.546
there's this new startup that does this.

01:46:30.586 --> 01:46:30.865
And I'm like,

01:46:30.886 --> 01:46:32.868
that is literally a Black Mirror episode.

01:46:33.108 --> 01:46:34.550
Why?

01:46:34.569 --> 01:46:36.070
So I digress.

01:46:37.712 --> 01:46:38.613
Yeah, I'm looking in the forum.

01:46:38.653 --> 01:46:39.814
I'm looking in Signal.

01:46:39.833 --> 01:46:42.076
I'm not seeing any more questions.

01:46:42.476 --> 01:46:44.457
So unless you or anybody else has

01:46:44.478 --> 01:46:46.279
anything, I think we can wrap this up.

01:46:48.220 --> 01:46:49.862
Yeah, probably can wrap it up.

01:46:50.061 --> 01:46:50.243
I mean,

01:46:50.283 --> 01:46:52.045
we've asked for questions this whole time.

01:46:52.064 --> 01:46:54.186
So if you haven't sent it in yet,

01:46:54.247 --> 01:46:55.930
I think that's on you,

01:46:55.970 --> 01:46:57.051
but you can save it for the next

01:46:57.070 --> 01:46:57.411
stream.

01:46:57.451 --> 01:46:58.432
For sure.

01:46:58.893 --> 01:46:59.012
Yeah.

01:46:59.033 --> 01:47:00.074
Do you want to wrap this up, Nate?

01:47:00.890 --> 01:47:01.110
Sure.

01:47:01.211 --> 01:47:01.712
I got this.

01:47:01.731 --> 01:47:02.773
All right.

01:47:02.813 --> 01:47:04.295
So all the updates from this week in

01:47:04.314 --> 01:47:06.056
privacy will be shared on the blog every

01:47:06.096 --> 01:47:06.337
week.

01:47:06.358 --> 01:47:08.140
So sign up for the newsletter or subscribe

01:47:08.159 --> 01:47:09.400
with your favorite RSS reader.

01:47:09.421 --> 01:47:10.903
If you want to stay tuned as a

01:47:10.943 --> 01:47:11.382
reminder,

01:47:11.543 --> 01:47:13.164
that newsletter actually goes out right at

01:47:13.185 --> 01:47:14.587
the same time that we start streaming.

01:47:14.667 --> 01:47:16.408
So that works as a good notification as

01:47:16.448 --> 01:47:16.649
well.

01:47:16.770 --> 01:47:17.970
And there's a link to the stream in

01:47:18.011 --> 01:47:18.511
the newsletter.

01:47:18.952 --> 01:47:20.814
So super convenient, super easy.

01:47:21.494 --> 01:47:23.396
We also offer a podcast available on all

01:47:23.436 --> 01:47:25.158
podcast platforms and RSS,

01:47:25.198 --> 01:47:26.860
which now includes video on supported

01:47:26.881 --> 01:47:28.523
platforms, if you prefer that.

01:47:28.662 --> 01:47:30.284
And this video will also be synced to

01:47:30.324 --> 01:47:30.826
PeerTube.

01:47:31.206 --> 01:47:32.908
PrivacyGuides is an impartial nonprofit

01:47:32.927 --> 01:47:34.529
organization that is focused on building a

01:47:34.590 --> 01:47:36.631
strong privacy advocacy community and

01:47:36.652 --> 01:47:38.054
delivering the best digital privacy and

01:47:38.094 --> 01:47:39.715
consumer technology rights advice on the

01:47:39.756 --> 01:47:40.055
internet.

01:47:40.395 --> 01:47:41.237
If you want to support our mission,

01:47:41.277 --> 01:47:42.497
you can make a donation on our website

01:47:42.518 --> 01:47:44.298
at privacyguides.org slash donate.

01:47:44.738 --> 01:47:46.220
You can also make a donation on any

01:47:46.260 --> 01:47:47.661
page of the website by clicking the red

01:47:47.680 --> 01:47:49.421
heart icon located in the top right corner

01:47:49.442 --> 01:47:49.903
of the page.

01:47:50.243 --> 01:47:51.703
You can contribute using standard fiat

01:47:51.743 --> 01:47:53.265
currency via debit or credit card,

01:47:53.604 --> 01:47:55.346
or you can donate anonymously using Monero

01:47:55.466 --> 01:47:56.868
or your favorite cryptocurrency.

01:47:57.228 --> 01:47:58.809
Becoming a paid member unlocks exclusive

01:47:58.828 --> 01:48:00.489
perks like early access to video content,

01:48:00.569 --> 01:48:01.650
exclusive video content,

01:48:01.990 --> 01:48:03.372
and priority during the Q&A.

01:48:03.692 --> 01:48:05.193
You'll also get a cool badge on your

01:48:05.233 --> 01:48:06.694
profile in the Privacy Guides forum and

01:48:06.713 --> 01:48:06.954
the warm,

01:48:06.994 --> 01:48:08.395
fuzzy feeling of supporting independent

01:48:08.416 --> 01:48:08.676
media.

01:48:09.095 --> 01:48:10.457
Thank you everyone who watched.

01:48:10.599 --> 01:48:11.820
It was awesome to have you guys in

01:48:11.841 --> 01:48:13.444
the chat and we will be back next

01:48:13.484 --> 01:48:14.706
week.

01:48:14.746 --> 01:48:15.287
Thanks everyone.