ID10T Techcast
ID10T Techcast is a weekly podcast where Tyler Woodward, a broadcast engineer, goes over the past week's news in Linux, tech and broadcasting and tells you what he thinks about it. Episodes run 15 to 30 minutes.
Every episode runs through the week's stories, like Linux security holes and open source, Big Tech and AI companies, the FCC, and radio and TV, then ends with one longer opinion piece. Some weeks it's a security hole, some weeks it's why radio isn't dead yet.
The show is for right to repair, privacy, a real nationwide US privacy law like Europe's GDPR, decentralized social media like Mastodon and Bluesky, and independent and community radio. It's critical of big corporations, tech billionaires and AI companies, and it calls out both political parties when they earn it. Everything's explained in plain English, no jargon.
More at ID10T.fm.
ID10T Techcast
Stop renting your own life back from Google, Apple, and Meta
Use Left/Right to seek, Home/End to jump to start or end. Hold shift to jump forward or backward.
Everyone repeats the line that the cloud is just someone else's computer, and then keeps handing over their whole life to it anyway. I get into what that actually means once you stop laughing at it: they write the rules, they change them whenever they want, and they can lock you out of your own photos and emails without warning.
I walk through what Google, Microsoft, Meta, and Apple actually do with your data versus what people assume, then break down the 2022 LastPass breach as the clearest example of what happens when everyone's information gets piled into one company's server. From there I get into what self hosting actually looks like now, from a box on a shelf in your house to a rented VPS, plus tools like Vaultwarden and Immich ("Image") that let you run your own passwords and photos without handing them over to a corporation.
This isn't a burn it all down pitch. I still use iCloud myself and I say so. It's a real look at how much control you're giving away by default and what it would actually take to get some of it back, which is exactly what digital ownership and tech accountability are supposed to be about.
Follow ID10T Techcast
Instagram: https://www.instagram.com/id10ttechcast
Threads: https://www.threads.com/@id10ttechcast
Facebook: https://facebook.com/id10ttechcast
Everything else is at https://ID10T.fm
00:00:00.520 --> 00:00:04.360
There's this line that gets thrown around a lot,
00:00:04.879 --> 00:00:09.480
you know, the cloud is someone else's computer
00:00:09.480 --> 00:00:14.460
and everyone kind of sort of gets that I mean
00:00:14.460 --> 00:00:20.239
your data, you know, your your files your Photos
00:00:20.239 --> 00:00:23.640
your bank statements your tax records, whatever
00:00:23.640 --> 00:00:26.800
that you might that you may have sitting out
00:00:26.800 --> 00:00:30.250
there on the cloud It's you know, it's not some
00:00:30.250 --> 00:00:34.229
random guy's Basement on his computer or something.
00:00:34.229 --> 00:00:37.530
It's on a company a corporate server, you know
00:00:37.530 --> 00:00:41.189
Google or Microsoft or Apple, you know, it's
00:00:41.189 --> 00:00:45.009
on one of their systems but essentially it's
00:00:45.009 --> 00:00:49.649
the same thing your data is on someone else's
00:00:49.649 --> 00:00:54.829
hardware and You know, I I think we need to talk
00:00:54.829 --> 00:00:58.649
about that. We need to kind of sit here and think
00:00:58.649 --> 00:01:03.770
about that because I mean are there alternatives
00:01:03.770 --> 00:01:07.989
than just you know other than putting your whole
00:01:07.989 --> 00:01:11.790
life out there on the internet somewhere on someone
00:01:11.790 --> 00:01:17.269
else's server I mean because it's true and once
00:01:17.269 --> 00:01:22.769
you start peeling the label back man it's hard
00:01:22.769 --> 00:01:30.349
to unsee it I'm Tyler. Thanks for being here.
00:01:30.569 --> 00:01:33.549
This is the Tyler Woodward Project. And today,
00:01:34.109 --> 00:01:36.689
well, we're going to talk about that line, that
00:01:36.689 --> 00:01:40.390
your data, you know, your stuff in the cloud
00:01:40.390 --> 00:01:48.090
is on someone else's computer. And, you know,
00:01:48.170 --> 00:01:50.890
about pulling your personal data back off of
00:01:50.890 --> 00:01:56.390
those computers and putting that onto systems
00:01:56.390 --> 00:02:02.760
that you own. your own hardware or at least Hardware
00:02:02.760 --> 00:02:07.659
that you lease and control that you have the
00:02:07.659 --> 00:02:16.419
root privileges for And like always This is always
00:02:16.419 --> 00:02:19.300
my read on it my opinions you can take it or
00:02:19.300 --> 00:02:22.199
leave it you know the rest of what I do is over
00:02:22.199 --> 00:02:27.240
at Tyler Woodward dot me and before I get going
00:02:27.599 --> 00:02:30.199
I'm not going to stand here and pretend I've
00:02:30.199 --> 00:02:36.180
got all this figured out. Right now, today, half
00:02:36.180 --> 00:02:41.000
of my life is still sitting out there on Apple
00:02:41.000 --> 00:02:44.300
servers and probably a little bit on Google.
00:02:44.699 --> 00:02:48.879
I use iCloud. I've got a MacBook Neo. I've got
00:02:48.879 --> 00:02:52.719
an iPhone. My kids got iPads. My wife's got an
00:02:52.719 --> 00:02:55.060
iPhone. you know, all of our stuff's out there
00:02:55.060 --> 00:02:57.800
on iCloud. I pay for the extra iCloud storage
00:02:57.800 --> 00:03:05.580
so we can back all those devices up. And I'm
00:03:05.580 --> 00:03:11.319
working on it. I'm trying to not rely on that
00:03:11.319 --> 00:03:18.020
so much. I'm trying to take a, I don't know,
00:03:18.099 --> 00:03:21.300
a measured approach to keeping my stuff off of
00:03:21.300 --> 00:03:24.800
there. So, you know, this isn't a lecture from
00:03:24.800 --> 00:03:28.960
a guy on the other side. I'm just another dude
00:03:28.960 --> 00:03:31.699
out there in the middle of it, just thinking
00:03:31.699 --> 00:03:34.900
about this out loud. And hopefully maybe I can
00:03:34.900 --> 00:03:38.979
spark some interest in some of you to rethink
00:03:38.979 --> 00:03:45.159
what we're putting out there in the world. So
00:03:45.159 --> 00:03:52.650
let's talk about the part Nobody's really arguing
00:03:52.650 --> 00:03:59.310
with about anymore Your whole life a good chunk
00:03:59.310 --> 00:04:02.310
of it probably by this point is sitting on their
00:04:02.310 --> 00:04:07.650
computers and the fine print it Sorta allows
00:04:07.650 --> 00:04:12.949
them to do a lot with that data. I Want to be
00:04:12.949 --> 00:04:17.529
fair here because a couple of these lines They're
00:04:17.529 --> 00:04:23.540
real they're facts now Google says it doesn't
00:04:23.540 --> 00:04:28.060
train its AI on your Gmail, and it doesn't scan
00:04:28.060 --> 00:04:31.060
your drive to sell you ads. And as far as anyone
00:04:31.060 --> 00:04:36.079
can tell, that's true. I mean, take it with a
00:04:36.079 --> 00:04:40.620
grain of salt. I don't trust the big corporate
00:04:40.620 --> 00:04:46.560
overlords with the data anymore. It's kind of
00:04:46.560 --> 00:04:51.110
a murky area, but we'll move on. Microsoft, that's
00:04:51.110 --> 00:04:57.269
another one. Microsoft had a whole panic a while
00:04:57.269 --> 00:05:03.350
back about it feeding your Word documents into
00:05:03.350 --> 00:05:09.509
its AI. Copilot. And when people started actually
00:05:09.509 --> 00:05:14.389
digging into it, well, that sort of fell apart.
00:05:15.149 --> 00:05:17.649
It didn't hold any water, or as far as we can
00:05:17.649 --> 00:05:24.269
tell, it's not true. But then there's Meta, which
00:05:24.269 --> 00:05:30.949
in 2024 changed the rules so your public Facebook
00:05:30.949 --> 00:05:35.089
and Instagram posts and your photos train their
00:05:35.089 --> 00:05:41.449
AI straight up. Now, they paused it in Europe
00:05:41.449 --> 00:05:45.870
when regulators called them out on it and started
00:05:45.870 --> 00:05:49.589
pressuring them. And then they flipped it back
00:05:49.589 --> 00:05:54.370
on over there in 2025. So, you know here in the
00:05:54.370 --> 00:06:01.350
States We don't have the same Set of data protections
00:06:01.350 --> 00:06:05.410
that they have over there in Europe now It would
00:06:05.410 --> 00:06:07.589
be a whole other argument on another episode
00:06:07.589 --> 00:06:10.189
I really think we should have probably, you know,
00:06:10.389 --> 00:06:13.110
probably adopt some of those but you know, you
00:06:13.110 --> 00:06:16.220
got the lobbyist out there Waving all the money
00:06:16.220 --> 00:06:19.540
around so they don't actually pass any any real,
00:06:19.540 --> 00:06:23.779
you know concrete data protection laws for us,
00:06:23.800 --> 00:06:26.939
but Like I said, that's a whole another episode
00:06:26.939 --> 00:06:33.860
Here in the States There's basically no opting
00:06:33.860 --> 00:06:37.160
out of out of what they collect over here either
00:06:37.160 --> 00:06:42.300
so You know, it's it's a mixed bag and I'm not
00:06:42.300 --> 00:06:47.180
gonna tell you All three are reading every word
00:06:47.180 --> 00:06:52.620
you type, because that's not really it. What's
00:06:52.620 --> 00:06:56.120
true, though, is simpler. It is their machine.
00:06:57.259 --> 00:07:03.579
The terms let them do what they want. The defaults
00:07:03.579 --> 00:07:09.360
lean toward yes. And your stuff gets scanned
00:07:09.360 --> 00:07:11.959
and sorted all day just to run their product.
00:07:13.819 --> 00:07:18.939
Now that part it's not a conspiracy. That's just
00:07:18.939 --> 00:07:23.379
a normal Tuesday Now I'm not here to make you
00:07:23.379 --> 00:07:26.019
feel bad about putting all your data out there
00:07:26.019 --> 00:07:29.240
on Google or Microsoft or Apple meta, whatever
00:07:29.240 --> 00:07:34.000
I'm here because I think The usual conversation
00:07:34.000 --> 00:07:38.860
about it is a dead end people argue about whether
00:07:38.860 --> 00:07:42.379
you should trust these companies whether they're
00:07:41.899 --> 00:07:46.899
you know, the privacy policies are fair, whether
00:07:46.899 --> 00:07:52.220
you've got anything to hide. And I think that
00:07:52.220 --> 00:07:56.759
whole frame is a trap in itself. The question
00:07:56.759 --> 00:08:01.680
was never whether you trust them. The question
00:08:01.680 --> 00:08:05.240
is why you're handing them your data at all.
00:08:07.079 --> 00:08:11.220
Because here's what, quote, someone else's computer
00:08:11.500 --> 00:08:16.000
actually means once you stop kind of chuckling
00:08:16.000 --> 00:08:22.759
about that line when it's their computer they
00:08:22.759 --> 00:08:26.399
make the rules they change them whenever they
00:08:26.399 --> 00:08:30.920
want and you find out usually afterwards or months
00:08:30.920 --> 00:08:34.919
maybe a year down the line when some security
00:08:34.919 --> 00:08:38.700
researcher uncovers it because they didn't publicly
00:08:38.700 --> 00:08:43.610
disclose it Meta has done that a few times. But
00:08:43.610 --> 00:08:47.149
again, they make the rules. They change them
00:08:47.149 --> 00:08:50.990
whenever they want. And again, you may find out
00:08:50.990 --> 00:08:57.230
afterwards. They can decide your account is done
00:08:57.230 --> 00:09:00.230
and lock you out of your own photos, your own
00:09:00.230 --> 00:09:04.210
email, years and years of your life. And there's
00:09:04.210 --> 00:09:13.470
no one to call. You were a guest in their sandbox.
00:09:14.809 --> 00:09:17.570
They can lock that door on you whenever they
00:09:17.570 --> 00:09:24.269
want. And then, you know, and then there's one
00:09:24.269 --> 00:09:30.629
more piece of that, the big one. When the government
00:09:30.629 --> 00:09:37.169
comes asking, they're the ones who answer, not
00:09:37.169 --> 00:09:39.669
you. And the ones answering? I'm talking about
00:09:39.669 --> 00:09:43.009
Microsoft and Apple and Meta and Google and all
00:09:43.009 --> 00:09:48.809
these other big tech conglomerates. Meta's own
00:09:48.809 --> 00:09:55.210
transparency report says it got over 320 ,000
00:09:55.210 --> 00:09:58.750
government requests for user data in just the
00:09:58.750 --> 00:10:03.129
first half of 2024 alone. And three quarters
00:10:03.129 --> 00:10:09.070
of the U .S. The ones that come from the US came
00:10:09.070 --> 00:10:13.370
with a gag order. So they legally couldn't even
00:10:13.370 --> 00:10:18.750
tell you it happened. One study found Google,
00:10:19.529 --> 00:10:24.669
Meta, and Apple handed US authorities data on
00:10:24.669 --> 00:10:29.149
more than three and a half million accounts over
00:10:29.149 --> 00:10:37.090
about a decade. I mean... You can't you can't
00:10:37.090 --> 00:10:43.629
hand over What you don't hold So sit with that
00:10:43.629 --> 00:10:46.830
one because it's basically where the show is
00:10:46.830 --> 00:10:57.610
going right now Let me give you the Clearest
00:10:57.610 --> 00:11:01.110
example of why this setup is actually a problem,
00:11:01.110 --> 00:11:04.669
you know, not just bashing the companies who
00:11:04.669 --> 00:11:11.009
run it. Let's talk about LastPass. LastPass,
00:11:11.009 --> 00:11:13.809
if you've never heard of them, they're a password
00:11:13.809 --> 00:11:16.129
manager company. I mean, I think they do a few
00:11:16.129 --> 00:11:21.629
other things, but their bread and butter is password
00:11:21.629 --> 00:11:30.710
management. Millions of users back in 2022, LastPass
00:11:30.710 --> 00:11:34.909
got broken into. And the thing that got taken
00:11:34.909 --> 00:11:37.830
wasn't, you know, one person's passwords, it
00:11:37.830 --> 00:11:46.389
was a backup of the entire vault database. Everybody's.
00:11:46.590 --> 00:11:50.029
Every last pass customers encrypted vault sitting
00:11:50.029 --> 00:11:55.409
together in one single cloud bucket, copied and
00:11:55.409 --> 00:11:59.269
they walked right out the door in one single
00:11:59.269 --> 00:12:04.840
breach. Now, Credit, where credit is due, the
00:12:04.840 --> 00:12:08.039
actual passwords inside those vaults, as I mentioned
00:12:08.039 --> 00:12:13.440
a minute ago, they were encrypted. Locked behind
00:12:13.440 --> 00:12:18.379
each person's master password. A master password,
00:12:18.399 --> 00:12:21.480
if you've never used a password manager before,
00:12:22.039 --> 00:12:24.340
is the password to get you in the door to get
00:12:24.340 --> 00:12:26.799
to all the other passwords that you have saved
00:12:26.799 --> 00:12:33.169
in there. you know a password manager you only
00:12:33.169 --> 00:12:36.230
have to remember one password instead of 300
00:12:36.230 --> 00:12:39.669
different ones is essentially what a master password
00:12:39.669 --> 00:12:47.169
is but the master passwords last pass they don't
00:12:47.169 --> 00:12:53.830
store those so getting the vault i mean yeah
00:12:53.830 --> 00:12:56.149
they got the vault but they couldn't read the
00:12:56.149 --> 00:13:00.370
vault without that password now if your master
00:13:00.370 --> 00:13:04.980
password was long and weird and unique, your
00:13:04.980 --> 00:13:07.620
stuff is probably good. You're probably fine.
00:13:08.879 --> 00:13:14.399
But two things. One, sitting right next to that
00:13:14.399 --> 00:13:18.740
encryption, not encrypted at all, was your email,
00:13:19.919 --> 00:13:22.779
your billing address, your phone number, and
00:13:22.779 --> 00:13:27.080
every single website you'd ever saved a login
00:13:27.080 --> 00:13:34.470
for. Yeah, they may not have that password, but
00:13:34.470 --> 00:13:40.049
they know where you've been That part was just
00:13:40.049 --> 00:13:44.629
readable for everybody no master password required
00:13:44.629 --> 00:13:52.490
in two If your master password Wasn't great You
00:13:52.490 --> 00:13:56.350
know wasn't strong wasn't 15 plus characters
00:13:56.350 --> 00:13:59.720
with Special characters and hieroglyphics and
00:13:59.720 --> 00:14:03.980
the blood of your firstborn The attacker I mean
00:14:03.980 --> 00:14:09.059
They possibly could have cracked it They could
00:14:09.059 --> 00:14:12.580
have got in the door forever no rate limit no
00:14:12.580 --> 00:14:18.659
lockout no way for you to even know That that
00:14:18.659 --> 00:14:21.620
they ever get into it because it was all offline
00:14:21.620 --> 00:14:26.720
once they grabbed it People are still getting
00:14:26.919 --> 00:14:29.460
crypto wallets drained today from vaults that
00:14:29.460 --> 00:14:36.440
were stolen back in 2022 now the other part i
00:14:36.440 --> 00:14:39.460
want you to take away from this is uh you know
00:14:39.460 --> 00:14:42.799
one break -in got everybody and the only reason
00:14:42.799 --> 00:14:45.779
one break -in could get everybody is that everybody's
00:14:45.779 --> 00:14:49.360
data was piled into the same bucket the same
00:14:49.360 --> 00:15:00.889
place on the same company server that pile is
00:15:00.889 --> 00:15:06.370
what makes it worth attacking I mean right if
00:15:06.370 --> 00:15:08.110
all your data is there they only got to go to
00:15:08.110 --> 00:15:13.009
one spot it's a pretty good attack surface you
00:15:13.009 --> 00:15:15.669
you know out there hosting your own stuff on
00:15:15.669 --> 00:15:20.190
your own box I mean you're just a one person
00:15:20.190 --> 00:15:25.789
and a see the digital abyss Now, I'm not saying
00:15:25.789 --> 00:15:27.889
that makes you safe, but it makes you less of
00:15:27.889 --> 00:15:35.509
a target. You know, you're just one boring target
00:15:35.509 --> 00:15:40.929
out of millions, not really a jackpot. So, you
00:15:40.929 --> 00:15:43.409
know, that's the pitch. Stop putting the crown
00:15:43.409 --> 00:15:45.409
jewels out there on other people's computers.
00:15:46.330 --> 00:15:49.330
Put all of your, you know, put your eggs in your
00:15:49.330 --> 00:15:56.120
own basket. And I know how that sounds. So, you
00:15:56.120 --> 00:15:58.480
know, let me be let me be a little honest with
00:15:58.480 --> 00:16:01.899
you Because a sharp person is already ahead of
00:16:01.899 --> 00:16:04.620
me here. I know someone's probably already banging
00:16:04.620 --> 00:16:08.700
on the keyboard typing in the comments When I
00:16:08.700 --> 00:16:13.659
say host it yourself There is a spectrum of what
00:16:13.659 --> 00:16:18.700
that means One end is a machine in your own damn
00:16:18.700 --> 00:16:22.909
house on your own shelf on your own desk your
00:16:22.909 --> 00:16:27.789
own little NAS, a little box and a closet. You
00:16:27.789 --> 00:16:32.549
know, that's that's completely yours. The other
00:16:32.549 --> 00:16:37.570
end is renting a, you know, a virtual server,
00:16:37.750 --> 00:16:43.049
a VPS virtual private server, which, yes, is
00:16:43.049 --> 00:16:47.029
technically still someone else's computer. Fair.
00:16:47.409 --> 00:16:50.169
I will give you that, but it's a different animal.
00:16:50.529 --> 00:16:53.799
You're renting the bare metal running your own
00:16:53.799 --> 00:16:56.679
software putting your own encrypted stuff on
00:16:56.679 --> 00:16:59.840
it and their business is renting you the metal
00:16:59.840 --> 00:17:05.480
not reading what you store in your little slice
00:17:05.480 --> 00:17:11.920
of of the uh the data center you have the root
00:17:11.920 --> 00:17:14.700
credentials it's yours you're running it until
00:17:14.700 --> 00:17:16.859
you decide to quit paying that bill or delete
00:17:16.859 --> 00:17:24.099
that server it's it's yours now I mean it's not
00:17:24.099 --> 00:17:27.440
perfect, but it's a long way from handing Google
00:17:27.440 --> 00:17:58.160
the keys to the kingdom. Okay, so What do you
00:17:58.160 --> 00:18:02.299
actually run? This stuff is real it works and
00:18:02.299 --> 00:18:06.099
most people have no idea how far it has come
00:18:06.099 --> 00:18:10.920
You know, let's talk about passwords vault warding
00:18:10.920 --> 00:18:15.700
It works with all the normal bit warden apps
00:18:15.700 --> 00:18:19.859
bit warden is like last pass They're they're
00:18:19.859 --> 00:18:26.089
a password manager except With Volt Warden, it's
00:18:26.089 --> 00:18:29.309
a copy that you run, but you can still use the
00:18:29.309 --> 00:18:32.390
official Bitwarden apps to get to your passwords,
00:18:32.630 --> 00:18:36.069
your notes, your encrypted files and whatever
00:18:36.069 --> 00:18:42.809
you store on there. The Volt through Volt Warden
00:18:42.809 --> 00:18:46.789
lives on your machine, not the company's. So
00:18:46.789 --> 00:18:50.940
your blast radius is only you. Not everybody
00:18:50.940 --> 00:18:54.960
else not all million other plus people the other
00:18:54.960 --> 00:19:01.779
one is photos This one That you know, this is
00:19:01.779 --> 00:19:05.819
the one that gets the people I'm itch. I Think
00:19:05.819 --> 00:19:09.240
I pronounced that right. What is it? I am ICH
00:19:09.240 --> 00:19:13.759
I'm Mitch That's how I've been saying it. I'm
00:19:13.759 --> 00:19:15.240
probably wrong. Tell me how you would pronounce
00:19:15.240 --> 00:19:21.140
it or the the correct way It does basically everything
00:19:21.140 --> 00:19:24.000
that Google Photos does. The auto -backup, the
00:19:24.000 --> 00:19:27.160
face recognition, search your library for the
00:19:27.160 --> 00:19:31.920
dog or for a beach or your grandmother, all of
00:19:31.920 --> 00:19:37.460
it. Except it runs on your own hardware and nothing
00:19:37.460 --> 00:19:42.720
gets uploaded anywhere for an AI model to learn
00:19:42.720 --> 00:19:49.539
from. Once you see it running, I mean, it's hard
00:19:49.539 --> 00:19:52.720
to believe that, you know, that's real, but it
00:19:52.720 --> 00:19:56.700
is. Try it, run it, spin it up. The other one
00:19:56.700 --> 00:20:04.440
is files. That sweet spot for Google Drive or
00:20:04.440 --> 00:20:10.420
Dropbox or Box .com, one of those. You can run
00:20:10.420 --> 00:20:15.640
Nextcloud or Owncloud, either one of those. Your
00:20:15.640 --> 00:20:19.299
documents sync across your devices. They're just
00:20:19.299 --> 00:20:22.700
not sitting in a system that might quietly start
00:20:22.700 --> 00:20:26.339
feeding it when they decide to change that privacy
00:20:26.339 --> 00:20:30.720
policy to train their AI models on. Using Nextcloud
00:20:30.720 --> 00:20:34.299
or own cloud, well, you control that data. And
00:20:34.299 --> 00:20:37.799
if you didn't want to use iMitch or Vault Warden,
00:20:38.279 --> 00:20:40.940
the other nice benefit of Nextcloud or own cloud
00:20:40.940 --> 00:20:44.349
is There's, there's plugins, there's modules.
00:20:44.650 --> 00:20:48.309
You can tack onto it. You can, you can use an
00:20:48.309 --> 00:20:51.470
X cloud or own cloud to put your, your photos
00:20:51.470 --> 00:20:55.250
or your passwords, or you could even, I mean,
00:20:55.289 --> 00:20:59.289
you can even use it to run your email through
00:20:59.289 --> 00:21:02.430
and notes and do teams call it. Well, not teams,
00:21:02.630 --> 00:21:04.710
Microsoft teams, but you know, video calls and
00:21:04.710 --> 00:21:06.369
chats and other things like that. If you ran
00:21:06.369 --> 00:21:08.269
it for a business, or even if you just wanted
00:21:08.269 --> 00:21:10.890
to do it for your family, I mean, next cloud.
00:21:11.049 --> 00:21:13.950
and own cloud they're very powerful tools and
00:21:13.950 --> 00:21:17.349
they're free you can host them yourself right
00:21:17.349 --> 00:21:20.769
now you can go pay 20 bucks a month for a vps
00:21:20.769 --> 00:21:24.890
out there and control it or you know you get
00:21:24.890 --> 00:21:27.549
yourself a decent used computer with a good size
00:21:27.549 --> 00:21:31.210
drive you know maybe 16 gigs of ram doesn't have
00:21:31.210 --> 00:21:34.069
to be ddr5 what's overly priced right now you
00:21:34.069 --> 00:21:37.630
could set that up at home use a dynamic dns if
00:21:37.630 --> 00:21:39.910
you don't get a static ip at home bam you're
00:21:39.910 --> 00:21:45.269
set man And the other benefit of next cloud and
00:21:45.269 --> 00:21:47.650
own cloud is your documents sync across all your
00:21:47.650 --> 00:21:50.549
devices, just like Google, just like Apple, just
00:21:50.549 --> 00:21:55.269
like Microsoft's OneDrive. You know, again, they're
00:21:55.269 --> 00:21:58.609
not just sitting in a system that might quietly
00:21:58.609 --> 00:22:03.390
start feeding them into next year's AI. And then
00:22:03.390 --> 00:22:10.049
my favorite. Because this one is so fucking stupid.
00:22:10.569 --> 00:22:16.950
Your own TV shows Plex Yeah Plex used to be the
00:22:16.950 --> 00:22:21.529
gold standard here For years the app that made
00:22:21.529 --> 00:22:25.670
a pile of your own video files feel like a real
00:22:25.670 --> 00:22:31.750
state -of -the -art streaming service Well That
00:22:31.750 --> 00:22:35.289
was true and till they Decided they wanted you
00:22:35.289 --> 00:22:39.269
know they wanted to and shitify their own damn
00:22:39.269 --> 00:22:42.079
product because that seems to be what everybody's
00:22:42.079 --> 00:22:47.119
doing now and that's i mean that's not me being
00:22:47.119 --> 00:22:50.619
cute go google it all the crap that plex has
00:22:50.619 --> 00:22:55.000
been pulling and that's a real word for it if
00:22:55.000 --> 00:22:56.960
you've never heard of in shitification go look
00:22:56.960 --> 00:23:00.359
it up corey doctorow awesome book go look that
00:23:00.359 --> 00:23:08.319
up plex they make you log into your own account
00:23:08.589 --> 00:23:11.849
even to watch a file on your own hard drive,
00:23:12.269 --> 00:23:14.549
on your own network that could be sitting on
00:23:14.549 --> 00:23:23.089
a computer across the room from you. Your watch
00:23:23.089 --> 00:23:27.009
history routes through their servers. And this
00:23:27.009 --> 00:23:33.410
year, back in July of 2026, they tripled the
00:23:33.410 --> 00:23:42.099
price of their lifetime pass. to like $749 and
00:23:42.099 --> 00:23:45.359
started charging just to watch your own server
00:23:45.359 --> 00:23:48.900
when you're away from home. Previously, before
00:23:48.900 --> 00:23:52.859
that, even if you were a free Plex subscriber,
00:23:54.500 --> 00:23:58.000
I think it was free, or at least, you know, Plex
00:23:58.000 --> 00:24:01.039
pass, you could take your media. Well, no, it
00:24:01.039 --> 00:24:02.579
had to be free because they started charging
00:24:02.579 --> 00:24:04.480
for it. That was the whole point of that comment,
00:24:04.480 --> 00:24:08.230
I guess. I'm an idiot. Don't... ignore me um
00:24:08.230 --> 00:24:10.630
but you could at least take your own media files
00:24:10.630 --> 00:24:12.990
and watch them wherever you want on your phone
00:24:12.990 --> 00:24:15.869
you know taking your apple tv with you your roku
00:24:15.869 --> 00:24:19.930
stick into a hotel you could watch it i mean
00:24:19.930 --> 00:24:23.029
you had to play you had to pay for plex pass
00:24:23.029 --> 00:24:26.190
for sure if you wanted to take like an hd home
00:24:26.190 --> 00:24:28.910
run and have local tv like transcoding and the
00:24:28.910 --> 00:24:30.849
dvr features and all that stuff i know you had
00:24:30.849 --> 00:24:35.460
to pay for that which is why i'm a plex pass
00:24:35.460 --> 00:24:39.779
member because I have an HD home run taking my
00:24:39.779 --> 00:24:44.759
local ATSC feeds and yeah, I got a nice pretty
00:24:44.759 --> 00:24:48.960
electronic program guide with it. That part is
00:24:48.960 --> 00:24:53.140
still genuinely useful with Plex, but the tripling
00:24:53.140 --> 00:24:56.640
of the price and scaling it back. So you got
00:24:56.640 --> 00:24:59.099
to pay in order to watch just your own local
00:24:59.099 --> 00:25:02.519
stuff that's right there at home because everything's
00:25:02.519 --> 00:25:06.500
got to traverse through the Plex servers. I mean,
00:25:06.900 --> 00:25:09.440
it might be a strong piece of language here,
00:25:09.900 --> 00:25:13.160
but fuck Plex for that one. Honestly, I mean,
00:25:13.259 --> 00:25:16.960
come on. Now, what's the alternative to Plex?
00:25:18.039 --> 00:25:20.640
Well, you got Jellyfin. That's an open standard
00:25:20.640 --> 00:25:24.180
now, forked off a media server that went proprietary
00:25:24.180 --> 00:25:27.359
back in 2018. You want to know what's awesome
00:25:27.359 --> 00:25:30.720
about Jellyfin? You don't need an account. It
00:25:30.720 --> 00:25:33.640
doesn't need the phone home, zero telemetry,
00:25:34.250 --> 00:25:38.630
And that's by design. It's not a setting you
00:25:38.630 --> 00:25:41.569
have to dig for. It just serves your movies,
00:25:41.809 --> 00:25:45.670
your TV shows, whatever, to your devices and
00:25:45.670 --> 00:25:49.230
stays out of your business. And it keeps going.
00:25:50.069 --> 00:25:52.089
I got a whole list of other tools here. You got
00:25:52.089 --> 00:25:54.730
Trillium, Outline, a little tool called Memos,
00:25:54.890 --> 00:25:58.930
all self -hosted. So the text stays on a file
00:25:58.930 --> 00:26:01.230
on your machine instead of... getting shipped
00:26:01.230 --> 00:26:05.490
off to some AI sub processor the instant you
00:26:05.490 --> 00:26:12.349
touch a smart feature. If you've never looked
00:26:12.349 --> 00:26:16.269
up memos or outline or Trillium, very, very good
00:26:16.269 --> 00:26:21.750
note taking tools. Now I, I like Obsidian. Obsidian
00:26:21.750 --> 00:26:24.150
I run because everything is stored and marked
00:26:24.150 --> 00:26:26.930
down files on my machine. I pay for their sync
00:26:26.930 --> 00:26:30.799
service, which is like Don't know if it's five
00:26:30.799 --> 00:26:33.559
or ten bucks a month, but it sinks it between
00:26:33.559 --> 00:26:35.880
my devices, but it doesn't sit on their servers
00:26:35.880 --> 00:26:41.680
So that's another one you could use Let's talk
00:26:41.680 --> 00:26:45.500
about your group chats, you know things that
00:26:45.500 --> 00:26:52.019
are gonna get you off of discord Matrix That's
00:26:52.019 --> 00:26:54.900
self -hostable. I ran one of those for a little
00:26:54.900 --> 00:26:56.799
while didn't find a use for it shut it down,
00:26:56.799 --> 00:26:59.880
but that's a good option and the other benefit
00:26:59.880 --> 00:27:03.579
of matrix is it is end -to -end encrypted and
00:27:03.579 --> 00:27:06.960
this isn't just you know fringe hobbyists type
00:27:06.960 --> 00:27:10.200
stuff it's what chunks of the french and german
00:27:10.200 --> 00:27:12.119
governments run their own internal messaging
00:27:12.119 --> 00:27:16.900
on so i mean it's got the check mark for the
00:27:16.900 --> 00:27:22.819
government usage and the reason they moved all
00:27:22.819 --> 00:27:25.680
their messaging and chats over there is because
00:27:25.680 --> 00:27:31.400
they got nervous about what the American companies,
00:27:31.599 --> 00:27:34.900
the Googles, the Microsofts were doing before
00:27:34.900 --> 00:27:39.019
we even noticed. Your project boards. Let's talk
00:27:39.019 --> 00:27:43.599
about that. Your Trilio, your Asana focal board
00:27:43.599 --> 00:27:47.559
does all that. Though, you know, I'm going to
00:27:47.559 --> 00:27:51.359
be straight with you. It's not getting much active
00:27:51.359 --> 00:27:57.059
development right now. So, you know, go in eyes
00:27:57.059 --> 00:28:01.789
open on that one. Careful and remote desktop
00:28:01.789 --> 00:28:06.430
You know to get you away from team viewer those
00:28:06.430 --> 00:28:10.049
sort of tools. There's rest desk where the connection
00:28:10.049 --> 00:28:14.289
between your two machines Never has to touch
00:28:14.289 --> 00:28:20.750
a stranger's relay server It's all yours. I Mean
00:28:20.750 --> 00:28:23.710
I gave you a lot of tools there. I rattled off
00:28:23.710 --> 00:28:26.930
a lot You don't have to do all of that at once
00:28:27.880 --> 00:28:30.059
And I think that's the pitfall a lot of people
00:28:30.059 --> 00:28:32.779
make when they dive head -first into self -hosting.
00:28:32.839 --> 00:28:35.440
They try to run everything. No, just pick one
00:28:35.440 --> 00:28:42.099
tool. Pick a Nexcloud or Jellyfin or Memos. Just
00:28:42.099 --> 00:28:46.720
pick a couple. Because, yeah, looking at that
00:28:46.720 --> 00:28:50.980
list and deciding it's going to be another job
00:28:50.980 --> 00:28:53.680
for you, that's not what I want to do. Just pick
00:28:53.680 --> 00:28:57.539
one, start there. Now a few other things we got
00:28:57.539 --> 00:29:03.599
to cover. One, none of this is about being paranoid.
00:29:04.420 --> 00:29:08.539
And it's definitely not, you know, trying to
00:29:08.539 --> 00:29:11.420
think of the best way to say this, it's definitely
00:29:11.420 --> 00:29:15.400
not about having something to hide. It's not,
00:29:15.599 --> 00:29:19.660
you know, it's about not leaving your front door
00:29:19.660 --> 00:29:24.039
open just because nobody's walked in yet. Your
00:29:24.039 --> 00:29:30.789
stuff, Being private is sort of kind of this
00:29:30.789 --> 00:29:34.789
default you're supposed to get or at least I
00:29:34.789 --> 00:29:38.049
feel it should. If you're gonna trust someone
00:29:38.049 --> 00:29:41.890
with your personal data, your photos, your files,
00:29:42.329 --> 00:29:45.289
whatever they, excuse me, whatever they are,
00:29:46.289 --> 00:29:51.750
you should at least have some sense that your
00:29:51.750 --> 00:29:56.910
data is protected and is not going to be used
00:29:56.910 --> 00:30:04.809
against you or used to feed some AI model. I
00:30:04.809 --> 00:30:09.309
feel like that's nice default to have, right?
00:30:09.869 --> 00:30:13.569
You shouldn't have to earn that back. And again,
00:30:14.509 --> 00:30:17.910
if we here in the United States had good privacy
00:30:17.910 --> 00:30:20.730
data laws like Europe, we wouldn't be having
00:30:20.730 --> 00:30:26.789
this conversation. Now another, This isn't you
00:30:26.789 --> 00:30:30.029
Against the security team. Nobody's saying you'll
00:30:30.029 --> 00:30:33.109
Defend your box better than Google defends theirs
00:30:33.109 --> 00:30:34.950
because I know there's gonna be the security
00:30:34.950 --> 00:30:39.349
people out there the point is When it's yours
00:30:39.349 --> 00:30:45.410
yours your one Small target and when it's theirs
00:30:45.410 --> 00:30:50.210
your one entry in a pile worth of fortune to
00:30:50.210 --> 00:30:53.740
crack now You still gotta protect your stuff.
00:30:53.819 --> 00:30:56.559
You still gotta take basic measures. We're not
00:30:56.559 --> 00:30:58.519
covering all that today. I'm just giving you
00:30:58.519 --> 00:31:00.920
some options that you can use if you wanted to
00:31:00.920 --> 00:31:03.940
self -host some of your own goodies, your own
00:31:03.940 --> 00:31:08.099
passwords, your own photos, your own files. We
00:31:08.099 --> 00:31:10.119
can get into a whole other list of the security
00:31:10.119 --> 00:31:15.480
stuff in a different episode. One other. Start
00:31:15.480 --> 00:31:22.579
with the one that bugs you the most. photos for
00:31:22.579 --> 00:31:27.160
a lot of people because Obviously photos. That's
00:31:27.160 --> 00:31:30.900
the personal one. You know your kids your Relatives,
00:31:30.920 --> 00:31:33.319
maybe your your parents or your grandparents
00:31:33.319 --> 00:31:36.160
who have passed away and you have those Those
00:31:36.160 --> 00:31:38.940
those memories those photos that are cherished
00:31:38.940 --> 00:31:43.079
and you don't want to lose those That's the one
00:31:43.079 --> 00:31:46.960
That I think people should start with Get that
00:31:46.960 --> 00:31:49.279
off of someone else's computer and on to yours
00:31:49.960 --> 00:31:55.519
and just notice how it feels to know exactly
00:31:55.519 --> 00:31:58.799
where it's living. You know, because right now
00:31:58.799 --> 00:32:02.420
it syncs up. Nobody really thinks about it. But
00:32:02.420 --> 00:32:05.420
the other thing that the likes of Google are
00:32:05.420 --> 00:32:09.599
doing is, you know, they're cutting back on the
00:32:09.599 --> 00:32:14.680
storage they give you. And the Gmail users, they
00:32:14.680 --> 00:32:17.579
found that out the hard way. Inboxes started
00:32:17.579 --> 00:32:22.200
filling up, realized that, hey, Data that storage
00:32:22.200 --> 00:32:26.319
that's getting pricey nowadays because of AI
00:32:26.319 --> 00:32:29.900
So these companies have to dial it back just
00:32:29.900 --> 00:32:34.839
like everybody else is having to and There was
00:32:34.839 --> 00:32:36.519
another point I was gonna make and I completely
00:32:36.519 --> 00:32:43.460
blanked on it now Yeah, I just had a brain fart
00:32:43.460 --> 00:32:47.039
in the middle of recording this oh well, I'm
00:32:47.039 --> 00:32:49.200
sure I'll Remember it as soon as I'm done with
00:32:49.200 --> 00:32:55.319
this episode Now coming back full circle, you
00:32:55.319 --> 00:32:58.960
know the cloud it's someone else's computer That's
00:32:58.960 --> 00:33:03.079
the whole thing It's it's not evil. It's just
00:33:03.079 --> 00:33:05.700
true and you're allowed to decide you'd rather
00:33:06.620 --> 00:33:09.759
Have it be on your own system your own hardware
00:33:09.759 --> 00:33:11.980
in your own house on your own internet connection
00:33:11.980 --> 00:33:14.759
Or if you want to go to VPS route on a trusted
00:33:14.759 --> 00:33:17.400
server that you hold the root credentials for
00:33:17.400 --> 00:33:21.299
I Remember what I was gonna say now Remember
00:33:21.299 --> 00:33:24.940
that if the product is Or I should say if the
00:33:24.940 --> 00:33:31.039
service is free You are the product Remember
00:33:31.039 --> 00:33:34.829
that that's the show it was a long one we're
00:33:34.829 --> 00:33:37.529
passing like 33 minutes right now if you want
00:33:37.529 --> 00:33:39.910
to keep up with it subscribe wherever you might
00:33:39.910 --> 00:33:42.250
be listening and if you've got a second drop
00:33:42.250 --> 00:33:45.269
a five star rating on apple podcast spotify youtube
00:33:45.269 --> 00:33:47.289
music wherever you're listening and if you'd
00:33:47.289 --> 00:33:51.150
rather just talk you can call you can leave a
00:33:51.150 --> 00:33:58.109
voicemail or you can text me 608 -668 -4702 again
00:33:58.109 --> 00:34:03.200
608 -668 For 702 you can leave a voicemail or
00:34:03.200 --> 00:34:05.039
you can text that number and hey who knows I
00:34:05.039 --> 00:34:07.619
might read it or play it on the next show And
00:34:07.619 --> 00:34:09.500
if you want to buy me a cup of coffee just to
00:34:09.500 --> 00:34:12.219
say thanks for doing this you can do that over
00:34:12.219 --> 00:34:15.820
at Tyler Woodward dot me That's it. It's all
00:34:15.820 --> 00:34:18.039
I got for you. I'll catch you guys next week
People on this episode
Podcasts we love
Check out these other fine podcasts recommended by us, not an algorithm.
Today, Explained
Vox
Apple News Today
Apple News
Syntax - Tasty Web Development Treats
Wes Bos & Scott Tolinski - Full Stack JavaScript Web Developers
Sightings
REVERB
Search Engine
PJ Vogt
This Week In Radio Tech (TWiRT)
guysfromqueens
Heavyweight
Pushkin Industries
Darknet Diaries
Jack Rhysider
Buzzcast
Buzzsprout
Archer's Line Podcast
Rob Archer
Decoder with Nilay Patel
The Verge
Uncanny Valley | WIRED
WIRED
Primary Technology
Stephen Robles and Jason Aten
Press Pause with Bill McLean
Bill McLean
Hard Fork
The New York Times