WEBVTT

00:00:00.200 --> 00:00:02.960
Here's a question that really shouldn't be that

00:00:02.960 --> 00:00:06.400
hard in 2026. You just walked off of a transmitter

00:00:06.400 --> 00:00:10.019
site. Your phone is full of photos, antenna connections,

00:00:11.119 --> 00:00:15.800
transmission line routing, the inside of a combiner

00:00:15.800 --> 00:00:17.859
cabinet that you've been trying to document for

00:00:17.859 --> 00:00:21.399
the last three months, maybe some wiring diagrams,

00:00:21.780 --> 00:00:24.500
how things are currently hooked up. Your laptop

00:00:24.500 --> 00:00:27.839
is sitting right there, right next to you. They're

00:00:27.839 --> 00:00:30.839
on the same Wi -Fi and somehow the default answer

00:00:30.839 --> 00:00:34.380
for most people is either email it to yourself

00:00:34.380 --> 00:00:38.560
or upload it to Dropbox, OneDrive, Google Drive

00:00:38.560 --> 00:00:42.140
and download it on the other side. You literally

00:00:42.140 --> 00:00:46.780
just bounce the photo of your transmission line

00:00:46.780 --> 00:00:51.020
to another state just to get it from your phone

00:00:51.020 --> 00:00:54.969
to your laptop. And look, if you're in the Apple

00:00:54.969 --> 00:00:58.810
world, AirDrop handles this and handles it pretty

00:00:58.810 --> 00:01:02.969
well. But most engineers I know are not fully

00:01:02.969 --> 00:01:07.430
in one ecosystem. They're not fully in the Apple

00:01:07.430 --> 00:01:10.930
world, Windows world, what have you. Maybe you've

00:01:10.930 --> 00:01:15.430
got a Windows machine at the shop, a Linux box

00:01:15.430 --> 00:01:18.209
in the rack, an Android phone in your pocket,

00:01:18.530 --> 00:01:21.109
and whoever you're working with that day just

00:01:21.109 --> 00:01:24.549
so happens to have an iPhone. The second anything

00:01:24.549 --> 00:01:27.590
non -Apple shows up, AirDrop just stops, doesn't

00:01:27.590 --> 00:01:31.969
try, doesn't negotiate, just done. This is the

00:01:31.969 --> 00:01:33.890
Tyler Woodward Project, and today I want to talk

00:01:33.890 --> 00:01:36.969
about a tool that solves this without asking

00:01:36.969 --> 00:01:40.489
you to pledge your allegiance to any one ecosystem.

00:01:41.109 --> 00:01:44.170
The app is called Localsend. It's free, it's

00:01:44.170 --> 00:01:47.129
open source, and it moves files directly between

00:01:47.129 --> 00:01:51.109
devices on your local network. Windows, macOS,

00:01:51.310 --> 00:01:55.590
Linux, Android, iOS, All of them, same app, same

00:01:55.590 --> 00:01:58.129
experience, no cloud provider in the middle,

00:01:58.590 --> 00:02:01.709
no accounts. No, please update your payment method

00:02:01.709 --> 00:02:05.849
before you can share this PDF. Just your devices

00:02:05.849 --> 00:02:09.210
talking to each other on whatever network you're

00:02:09.210 --> 00:02:11.490
on. I'm going to walk you through how it actually

00:02:11.490 --> 00:02:14.689
works, where it's actually useful for broadcast

00:02:14.689 --> 00:02:17.750
engineering, where it might fall a little short.

00:02:18.210 --> 00:02:20.789
Why I think this is one of those quiet tools

00:02:20.789 --> 00:02:25.020
that deserves Way more attention in this industry

00:02:25.020 --> 00:02:35.300
than it currently gets So let's start with the

00:02:35.300 --> 00:02:39.280
basics local send is a peer -to -peer file transfer

00:02:39.280 --> 00:02:43.419
app You can install it on all your devices and

00:02:43.419 --> 00:02:45.479
as long as they're on the same local network

00:02:45.479 --> 00:02:48.800
They show up in a list and you can send stuff

00:02:48.800 --> 00:02:52.319
between them. That's the entire pitch But the

00:02:52.319 --> 00:02:55.259
details, I mean, they do matter. Because the

00:02:55.259 --> 00:02:57.719
details are what makes this different from just

00:02:57.719 --> 00:03:02.780
another file sharing app. First, it's genuinely

00:03:02.780 --> 00:03:08.439
cross -platform. Windows, macOS, Linux, Android,

00:03:08.780 --> 00:03:14.539
iOS, all supported as equals. Linux is not an

00:03:14.539 --> 00:03:18.159
afterthought here. You get Debian packages, app

00:03:18.159 --> 00:03:21.560
images, arm builds for raspberry pi the whole

00:03:21.560 --> 00:03:24.819
spread all of it that matters if you're running

00:03:24.819 --> 00:03:30.360
a mixed shop which in broadcast is everyone second

00:03:30.360 --> 00:03:34.159
it's fully offline not offline with an asterisk

00:03:34.159 --> 00:03:38.300
not offline but we ping a server for discovery

00:03:38.300 --> 00:03:43.120
there is no local send cloud your data goes from

00:03:43.120 --> 00:03:47.240
the you know your device device a to device b

00:03:47.229 --> 00:03:50.349
over your local area network. And that's where

00:03:50.349 --> 00:03:54.650
the story ends. Third, it's open source. No ads,

00:03:54.789 --> 00:03:57.270
no tracking, no data collection. The code and

00:03:57.270 --> 00:04:01.469
the protocol are both on GitHub. If you want

00:04:01.469 --> 00:04:04.569
to know exactly what it's doing, you can read

00:04:04.569 --> 00:04:09.069
it for yourself. Now, let me walk you through

00:04:09.069 --> 00:04:12.490
what actually happens when you tap send. Because

00:04:12.490 --> 00:04:14.629
once you understand it, you'll also understand

00:04:14.629 --> 00:04:19.600
why it breaks when it breaks. Both devices need

00:04:19.600 --> 00:04:22.519
to be on the same local network, same Wi -Fi

00:04:22.519 --> 00:04:27.720
SSID, same ethernet segment, or a setup where

00:04:27.720 --> 00:04:32.480
those share a subnet. If your phone is on the

00:04:32.480 --> 00:04:36.399
shop Wi -Fi and your laptop is on the guest SSID,

00:04:37.100 --> 00:04:39.839
they might feel close, but they're invisible

00:04:39.839 --> 00:04:44.100
to each other. Different VLANs, different broadcast

00:04:44.100 --> 00:04:48.860
domains, local SIN, can't send across that. From

00:04:48.860 --> 00:04:53.939
there, each local send instance runs a small

00:04:53.939 --> 00:04:59.459
HTTPS server, typically on port 53317, and uses

00:04:59.459 --> 00:05:01.759
local network announcements so other devices

00:05:01.759 --> 00:05:06.000
can find it. From your side, you just see a list

00:05:06.000 --> 00:05:09.899
of friendly device names. Tyler PC, Tyler Pixel,

00:05:10.100 --> 00:05:14.839
Tyler ThinkPad. Behind the scenes, That's IP

00:05:14.839 --> 00:05:17.839
addresses and service discovery doing the work

00:05:17.839 --> 00:05:21.699
When you pick a target and send the file local

00:05:21.699 --> 00:05:25.360
send opens a direct HTTPS connection between

00:05:25.360 --> 00:05:28.860
the two you know the two devices and Streams

00:05:28.860 --> 00:05:32.740
the data across it no relay. No middleman speed

00:05:32.740 --> 00:05:37.360
is basically whatever your land can handle on

00:05:37.360 --> 00:05:40.540
decent Wi -Fi 6 or ethernet people regularly

00:05:40.839 --> 00:05:44.019
You know, see 20 to 50 plus megabytes per second.

00:05:44.579 --> 00:05:47.300
The bottleneck is your hardware and your disk,

00:05:47.560 --> 00:05:52.360
not some cloud rate limit. All transfers are

00:05:52.360 --> 00:05:54.720
wrapped in TLS with self -signed certificates

00:05:54.720 --> 00:05:58.500
that each device generates locally. So even on

00:05:58.500 --> 00:06:02.120
a shared network, someone passively sniffing

00:06:02.120 --> 00:06:06.420
traffic just sees encrypted blobs. And because

00:06:06.420 --> 00:06:10.970
it's open source, this isn't trust us. You can

00:06:10.970 --> 00:06:14.269
look at the protocol spec. You can read the code,

00:06:14.449 --> 00:06:17.110
build it from source if you're the paranoid type.

00:06:17.930 --> 00:06:21.910
And that's not a criticism. Being paranoid is

00:06:21.910 --> 00:06:24.250
kind of, well, you're doing the correct thing

00:06:24.250 --> 00:06:29.509
in this industry nowadays. Okay. So let's talk

00:06:29.509 --> 00:06:33.310
about where this actually fits in the broadcast

00:06:33.310 --> 00:06:36.490
workflow. Because the use cases are different

00:06:36.490 --> 00:06:41.009
from, I just want to send a photo. to my wife.

00:06:41.370 --> 00:06:43.949
Site documentation. This is probably the biggest

00:06:43.949 --> 00:06:46.949
one for me. You go out to a site, you shoot some

00:06:46.949 --> 00:06:50.550
photos of a rack layout, the coax runs, the grounding

00:06:50.550 --> 00:06:53.250
system, the antenna connections. You've got maybe

00:06:53.250 --> 00:06:56.870
let's say 40, 50 photos on your phone by the

00:06:56.870 --> 00:07:00.370
time you leave. Getting those onto your laptop

00:07:00.370 --> 00:07:04.110
to actually label them, organize them, put them

00:07:04.110 --> 00:07:07.639
in a folder. maybe add them to whatever site

00:07:07.639 --> 00:07:10.959
documentation setup you have, that friction,

00:07:10.980 --> 00:07:16.279
it's real. If you're an Android to Windows person,

00:07:16.339 --> 00:07:19.540
you're either plugging in a USB cable or bouncing

00:07:19.540 --> 00:07:22.879
everything through Google Photos or a cloud drive

00:07:22.879 --> 00:07:25.660
and hoping the upload didn't compress them in

00:07:25.660 --> 00:07:31.740
the garbage. Local send, you open the app, you...

00:07:31.800 --> 00:07:35.160
see your laptop in the list, select all the photos,

00:07:36.040 --> 00:07:40.180
they land in your download folder at full resolution,

00:07:40.579 --> 00:07:43.720
zero compression, and about 10 seconds on a really

00:07:43.720 --> 00:07:47.180
good hotspot. Let's talk about manuals and PDFs.

00:07:47.220 --> 00:07:50.699
This one, I use it for, I use this constantly.

00:07:51.060 --> 00:07:58.279
You've got a PDF of an Orban 8500 manual on your

00:07:58.279 --> 00:08:00.860
laptop. You're standing at the rack. and you

00:08:00.860 --> 00:08:05.980
want to reference the AGC parameter table, whatever,

00:08:06.180 --> 00:08:08.060
without going back to your laptop constantly.

00:08:09.680 --> 00:08:13.079
Or you've got a spec sheet. Your colleague just

00:08:13.079 --> 00:08:15.759
emailed you on your phone and you need it on

00:08:15.759 --> 00:08:17.620
the machine that's actually connected to the

00:08:17.620 --> 00:08:21.220
equipment. LocalSend makes that a five second

00:08:21.220 --> 00:08:23.579
problem instead of let me email this to myself

00:08:23.579 --> 00:08:26.589
and hope the attachment. you know, doesn't get

00:08:26.589 --> 00:08:30.149
eaten by the virus scanner or whatever on your

00:08:30.149 --> 00:08:33.850
email hosting service. Firmware and config files.

00:08:34.730 --> 00:08:37.830
This is where cross -platform matters most. Picture

00:08:37.830 --> 00:08:40.549
this. You've got a config backup from a Telo

00:08:40.549 --> 00:08:43.389
system on your Windows machine. You need to move

00:08:43.389 --> 00:08:46.809
it to a MacBook because that's what the other

00:08:46.809 --> 00:08:50.690
engineer on the project is using. Or you've got

00:08:50.690 --> 00:08:56.470
a firmware update on your Linux workstation and

00:08:56.470 --> 00:09:00.529
you need to get it onto USB Drive that's formatted

00:09:00.529 --> 00:09:05.070
on a Windows laptop. LocalSend handles all those

00:09:05.070 --> 00:09:07.450
transfers cleanly without you having to care

00:09:07.450 --> 00:09:11.970
what OS either device is using. I got a couple

00:09:11.970 --> 00:09:15.889
more, stick with me here. iOS to Windows. We

00:09:15.889 --> 00:09:19.590
know how painful that can be. If you have an

00:09:19.590 --> 00:09:23.220
iPhone and a Windows machine, There is genuinely

00:09:23.220 --> 00:09:26.559
no good native way to move files between them.

00:09:27.139 --> 00:09:31.179
You can use iCloud. Sure, but that requires everyone

00:09:31.179 --> 00:09:35.419
to have an Apple ID and a cloud subscription.

00:09:36.039 --> 00:09:38.779
You can plug in a USB cable, but then you're

00:09:38.779 --> 00:09:41.820
dealing with iTunes or the Windows Photos app,

00:09:42.919 --> 00:09:47.240
which is its own nightmare. LocalSend makes iOS

00:09:47.240 --> 00:09:50.840
and Windows talk to each other. like they were

00:09:50.840 --> 00:09:55.379
designed to do that from the start. Which, well,

00:09:55.460 --> 00:09:59.340
we clearly know they weren't. And again, couple

00:09:59.340 --> 00:10:01.980
more. Android to Mac, same problem, different

00:10:01.980 --> 00:10:04.940
direction. Apple doesn't support Android file

00:10:04.940 --> 00:10:10.240
transfer natively on any meaningful way. LocalSend,

00:10:10.539 --> 00:10:13.399
again, is the answer. Install it on the Pixel,

00:10:13.960 --> 00:10:16.940
install it on the MacBook, same network, done.

00:10:18.259 --> 00:10:24.340
Linux. to anything This one. Oh my god. I feel

00:10:24.340 --> 00:10:30.019
this one personally If you run Linux, you know

00:10:30.019 --> 00:10:33.620
the routine most consumer filed tools either

00:10:33.620 --> 00:10:37.740
don't support Linux at all or They throw you

00:10:37.740 --> 00:10:40.700
a half -baked web UI and pretend that counts

00:10:40.700 --> 00:10:45.840
in some meaningful way KDE connects is great

00:10:45.840 --> 00:10:50.070
if you're in the KDE desktop environment world,

00:10:50.830 --> 00:10:53.850
but it gets rough on non -KDE setups and basically

00:10:53.850 --> 00:10:57.830
doesn't exist on Apple platforms. Except maybe

00:10:57.830 --> 00:11:01.690
the iPhone, I think. LocalSend treats Linux like

00:11:01.690 --> 00:11:05.049
a first -class citizen. There are Debian packages,

00:11:05.549 --> 00:11:09.110
app images, arm builds, same app, same features,

00:11:09.470 --> 00:11:13.830
same flow as every other platform. For a community

00:11:13.830 --> 00:11:17.820
that's used to being an afterthought, That actually

00:11:17.820 --> 00:11:22.799
means a lot to us. You have no idea. Let me also

00:11:22.799 --> 00:11:24.860
talk about what this looks like in the field.

00:11:26.320 --> 00:11:28.980
You're at a remote site. You got no internet

00:11:28.980 --> 00:11:32.299
connection or maybe some garbage DSL connection

00:11:32.299 --> 00:11:35.360
out in the boonies. Maybe you're on hotel wifi,

00:11:35.919 --> 00:11:38.340
a cellular hotspot, whatever. You throw up a

00:11:38.340 --> 00:11:41.960
travel router. You tether your phone. Now you've

00:11:41.960 --> 00:11:44.539
got a tiny little local network. Locosyn works

00:11:44.539 --> 00:11:49.000
perfectly on that. You're not depending on upload

00:11:49.000 --> 00:11:51.980
bandwidth. You're not waiting for a cloud sync.

00:11:52.080 --> 00:11:54.919
It's just your devices, your little network bubble

00:11:54.919 --> 00:11:58.580
and direct transfers at whatever land speed it

00:11:58.580 --> 00:12:03.779
can support. That's where the no internet required

00:12:03.779 --> 00:12:05.980
thing stops being a bullet point and becomes

00:12:05.980 --> 00:12:12.860
an actual useful thing. You're at a transmitter

00:12:12.860 --> 00:12:15.250
site, let's say at 11 o 'clock at night. Trying

00:12:15.250 --> 00:12:17.409
to document what you just fixed before you drive

00:12:17.409 --> 00:12:21.389
home. The last thing you want to do is have to

00:12:21.389 --> 00:12:24.389
wait for your cloud drive to sync through a weak

00:12:24.389 --> 00:12:27.610
cell signal. I've done that way too many times.

00:12:29.009 --> 00:12:32.590
Now, let's be honest about where this goes sideways,

00:12:32.590 --> 00:12:34.309
because yeah, I'm not just going to give you

00:12:34.309 --> 00:12:35.750
the benefits. I'm also going to give you the

00:12:35.750 --> 00:12:38.730
pitfalls as well. The number one complaint you'll

00:12:38.730 --> 00:12:42.879
see is my devices don't see each other. And almost

00:12:42.879 --> 00:12:45.039
every time, the answer is not that local send

00:12:45.039 --> 00:12:48.419
is broken, it's that your network is doing exactly

00:12:48.419 --> 00:12:52.379
what someone configured it to do. Different SSIDs,

00:12:52.620 --> 00:12:55.820
maybe different VLANs, your phone is on the guest

00:12:55.820 --> 00:12:59.379
Wi -Fi, laptop is on the main Wi -Fi. They can't

00:12:59.379 --> 00:13:02.159
find each other. Pretty straightforward, right?

00:13:02.419 --> 00:13:04.519
Move them to the same Wi -Fi network, the same

00:13:04.519 --> 00:13:09.120
SSID or the same VLAN. AP isolation, some routers.

00:13:09.340 --> 00:13:12.320
especially in default configurations, prevent

00:13:12.320 --> 00:13:15.720
devices on the same SSID from talking to each

00:13:15.720 --> 00:13:18.659
other directly. That kills local send discovery

00:13:18.659 --> 00:13:21.779
instantly. Usually you can fix that by turning

00:13:21.779 --> 00:13:29.240
off client isolation. VPN interference. If you're

00:13:29.240 --> 00:13:32.340
running a VPN tunnel that's routing all your

00:13:32.340 --> 00:13:34.779
traffic through a tunnel, your device might not

00:13:34.779 --> 00:13:38.500
treat the local network as actual local anymore.

00:13:38.759 --> 00:13:41.820
LocalSend discovery, you know, the packets are

00:13:41.820 --> 00:13:44.139
getting swallowed by that tunnel. So that's not

00:13:44.139 --> 00:13:47.200
going to work. Check that firewall on Windows,

00:13:47.419 --> 00:13:53.240
especially if you denied the allow this app on

00:13:53.240 --> 00:13:56.440
private networks prompt, you've blocked it on

00:13:56.440 --> 00:13:59.700
Linux. If your inbound ports are locked down

00:13:59.700 --> 00:14:03.700
with IP tables or UFW, same deal. LocalSend needs

00:14:03.700 --> 00:14:09.610
to listen on port 53317. What else is there?

00:14:10.769 --> 00:14:13.929
Mobile OS background restrictions. Both Android

00:14:13.929 --> 00:14:17.649
and iOS aggressively will kill apps in the background

00:14:17.649 --> 00:14:20.950
to save battery. If local send isn't in the foreground,

00:14:21.149 --> 00:14:24.110
it might not be discoverable. So check that.

00:14:24.129 --> 00:14:26.269
Make sure you actually have it open right there

00:14:26.269 --> 00:14:29.769
on your screen. My mental model kind of goes

00:14:29.769 --> 00:14:32.889
to this. First, you know, check the SSID, check

00:14:32.889 --> 00:14:37.240
the VLAN, check VPN, check firewall. In really

00:14:37.240 --> 00:14:45.559
that order, then you can blame the app. Here's

00:14:45.559 --> 00:14:48.179
the quick setup checklist if you want to hit

00:14:48.179 --> 00:14:53.200
the ground running. Install from the official

00:14:53.200 --> 00:14:56.440
sources, the app store on iPhone, Google Play

00:14:56.440 --> 00:14:59.419
on Android, the project's own download page or

00:14:59.419 --> 00:15:02.700
your distro's package manager. Don't grab random

00:15:02.700 --> 00:15:07.789
clones from sketchy mirror sites. Name your device

00:15:07.789 --> 00:15:11.389
as something useful like Tyler -PC, Tyler -Pixel,

00:15:11.509 --> 00:15:16.210
Tyler -ThinkPad. Future you is really going to

00:15:16.210 --> 00:15:18.909
appreciate it when you're in a hurry and there

00:15:18.909 --> 00:15:21.269
are four unnamed devices in the list and you're

00:15:21.269 --> 00:15:23.629
trying to figure out which one's which. Verify

00:15:23.629 --> 00:15:25.570
your network. Make sure all devices are on the

00:15:25.570 --> 00:15:29.679
same SSID or subnet. Turn off IP isolation, client

00:15:29.679 --> 00:15:32.379
isolation if your router has that sort of stuff

00:15:32.379 --> 00:15:34.299
enabled on the network you're trying to use.

00:15:34.779 --> 00:15:37.340
If you're on a VPN, either disconnect it or set

00:15:37.340 --> 00:15:42.000
up a split tunnel for local traffic. Allow it

00:15:42.000 --> 00:15:44.080
through your firewall on the device. On Windows,

00:15:44.120 --> 00:15:47.039
say yes to the private network prompt. On Linux,

00:15:47.240 --> 00:15:51.679
make sure port 53317, TCP, and UDP are open.

00:15:52.080 --> 00:15:54.580
And on macOS, accept the incoming connections

00:15:54.580 --> 00:15:58.740
dialog. Set a same download folder that you can

00:15:58.740 --> 00:16:02.000
remember. On desktop, point it somewhere you'll

00:16:02.000 --> 00:16:04.100
actually be able to get to or look or remember.

00:16:04.539 --> 00:16:07.659
On mobile, know where files land so they don't

00:16:07.659 --> 00:16:09.659
feel like they just disappeared into a black

00:16:09.659 --> 00:16:13.340
hole somewhere. And then, tell people you work

00:16:13.340 --> 00:16:17.279
with that this exists. It's a hundred times more

00:16:17.279 --> 00:16:21.440
useful when the whole team is using it. After

00:16:21.440 --> 00:16:24.169
all that, here's where I land on this. You don't

00:16:24.169 --> 00:16:27.809
need to be locked into Apple's ecosystem or or

00:16:27.809 --> 00:16:31.870
even Google's or anyone to get fast and reliable

00:16:31.870 --> 00:16:35.789
nearby file sharing. LocalSyn proves that the

00:16:35.789 --> 00:16:39.409
basic networking your Wi -Fi already does is

00:16:39.409 --> 00:16:43.409
more than capable of handling this. And it does

00:16:43.409 --> 00:16:46.929
it all with encryption without the cloud and

00:16:46.929 --> 00:16:52.190
without asking for a dime. AirDrop is fine if

00:16:52.190 --> 00:16:55.370
it works for you. keep using it i got no problem

00:16:55.370 --> 00:16:57.210
with that i'm just trying to give you some alternatives

00:16:57.210 --> 00:17:00.429
but if you're an engineer who runs a mixed shop

00:17:00.429 --> 00:17:03.990
and honestly that's probably most of us and you're

00:17:03.990 --> 00:17:06.549
tired of the friction of moving files between

00:17:06.549 --> 00:17:14.210
oses local send is a really good answer to that

00:17:14.210 --> 00:17:17.789
frustration pick pick the two devices that give

00:17:17.789 --> 00:17:20.529
you the most trouble install local send on both

00:17:20.529 --> 00:17:23.140
give it a few minutes I think you'll be surprised

00:17:23.140 --> 00:17:25.500
at how fast this becomes the way you do it going

00:17:25.500 --> 00:17:29.500
forward. That's the whole show. If you want more

00:17:29.500 --> 00:17:31.700
episodes like this, visit TylerWoodward .me for

00:17:31.700 --> 00:17:34.720
show notes, links and the ways to support the

00:17:34.720 --> 00:17:37.779
show. Follow me at TylerWoodward .me on threads,

00:17:38.160 --> 00:17:41.099
blue sky, Instagram. You can also reach me on

00:17:41.099 --> 00:17:43.440
matrix if you want matrix .TylerWoodward .me

00:17:43.440 --> 00:17:45.480
and subscribe and rate the show on your favorite

00:17:45.480 --> 00:17:49.019
podcast platform. If you know another engineer.

00:17:49.889 --> 00:17:52.089
who's still emailing site photos to themselves,

00:17:52.630 --> 00:17:55.329
just get them off the phone. Do them a favor,

00:17:55.529 --> 00:17:58.109
send them this episode. I'll catch you next week.