Recorded on 5/15/2026 at 07:17 PM PDT
View Video
[00:00:01.190 --> 00:00:03.390] All right, I'm [00:00:03.390 --> 00:00:04.480] going to cruise [00:00:04.480 --> 00:00:07.050] through this little [00:00:07.050 --> 00:00:07.790] area here. [00:00:07.790 --> 00:00:10.460] It's been tricky [00:00:10.460 --> 00:00:14.320] with the signal. [00:00:14.320 --> 00:00:18.850] And yeah, so there [00:00:18.850 --> 00:00:19.710] we go. [00:00:19.710 --> 00:00:21.120] I got a nice little [00:00:21.120 --> 00:00:22.690] warning there that [00:00:22.690 --> 00:00:24.240] service is [00:00:24.240 --> 00:00:25.960] struggling. [00:00:25.960 --> 00:00:28.780] Okay, but now it [00:00:28.780 --> 00:00:33.330] has subsided. [00:00:33.330 --> 00:00:33.980] So we'll see what [00:00:33.980 --> 00:00:34.850] this looks like. [00:00:34.850 --> 00:00:39.810] Okay, there it [00:00:39.810 --> 00:00:41.040] comes again. [00:00:41.040 --> 00:00:42.020] Give me a warning. [00:00:42.960 --> 00:00:43.860] And what that means [00:00:43.860 --> 00:00:44.570] is that, I mean, [00:00:44.570 --> 00:00:45.380] you can't see this, [00:00:45.380 --> 00:00:47.250] but the app is [00:00:47.250 --> 00:00:51.650] trying to stream, [00:00:51.650 --> 00:00:51.750] right? [00:00:51.740 --> 00:00:52.670] It's trying to, [00:00:52.670 --> 00:00:53.620] like, send this [00:00:53.620 --> 00:00:55.610] signal broadcast. [00:00:55.610 --> 00:00:58.240] And if it cannot [00:00:58.240 --> 00:01:00.020] connect with the [00:01:00.020 --> 00:01:03.770] streaming server, [00:01:03.770 --> 00:01:04.800] then, you know, [00:01:04.800 --> 00:01:05.440] this is confusing [00:01:05.440 --> 00:01:05.910] to people. [00:01:05.910 --> 00:01:06.390] Like, they don't [00:01:06.390 --> 00:01:07.110] understand anything. [00:01:07.110 --> 00:01:09.120] So, again, this is [00:01:09.120 --> 00:01:10.150] a transmission, [00:01:10.150 --> 00:01:10.740] right? [00:01:10.740 --> 00:01:11.760] This is a broadcast. [00:01:11.760 --> 00:01:13.430] Oop, I'm just going [00:01:13.430 --> 00:01:13.780] to pee. [00:01:14.560 --> 00:01:17.220] So it needs to [00:01:17.220 --> 00:01:18.420] connect to a [00:01:18.420 --> 00:01:19.660] service. [00:01:19.660 --> 00:01:20.840] And there are a lot [00:01:20.840 --> 00:01:21.770] of variables. [00:01:21.770 --> 00:01:23.620] That's what makes [00:01:23.620 --> 00:01:24.300] this kind of [00:01:24.300 --> 00:01:24.900] ambitious and [00:01:24.900 --> 00:01:25.710] complicated and [00:01:25.710 --> 00:01:28.180] difficult and a lot [00:01:28.180 --> 00:01:30.170] different than [00:01:30.170 --> 00:01:32.590] maybe past efforts [00:01:32.590 --> 00:01:35.710] to, you know, build [00:01:35.710 --> 00:01:37.300] a service like this [00:01:37.300 --> 00:01:38.070] where you just [00:01:38.070 --> 00:01:38.940] record things on [00:01:38.940 --> 00:01:39.710] your phone and [00:01:39.710 --> 00:01:40.870] upload them. [00:01:42.800 --> 00:01:48.070] So, yeah, there's a [00:01:48.070 --> 00:01:49.530] lot of variables, [00:01:49.530 --> 00:01:51.280] including, right, [00:01:51.280 --> 00:01:52.600] of course, do you [00:01:52.600 --> 00:01:54.040] have a good network [00:01:54.040 --> 00:01:55.520] connection to your [00:01:55.520 --> 00:01:58.680] provider, right? [00:01:58.680 --> 00:01:59.670] In my case, it's AT&T [00:01:59.670 --> 00:02:00.530] here in the United [00:02:00.530 --> 00:02:01.700] States in Southern [00:02:01.700 --> 00:02:02.360] California. [00:02:02.780 --> 00:02:04.350] But then, even if I [00:02:04.350 --> 00:02:05.020] have a good [00:02:05.020 --> 00:02:06.180] connection to my [00:02:06.180 --> 00:02:08.270] provider, do I have [00:02:08.270 --> 00:02:09.390] a good connection [00:02:09.390 --> 00:02:10.740] to the streaming [00:02:10.740 --> 00:02:11.730] server, right? [00:02:11.730 --> 00:02:12.860] So imagine if, you [00:02:12.860 --> 00:02:14.290] know, I could have [00:02:14.290 --> 00:02:15.170] full bars, but I'm [00:02:15.170 --> 00:02:16.110] trying to connect [00:02:16.110 --> 00:02:17.830] to a computer and [00:02:17.830 --> 00:02:18.800] the computer is off, [00:02:18.800 --> 00:02:19.660] right? [00:02:19.660 --> 00:02:21.100] Well, then a [00:02:21.100 --> 00:02:22.420] streaming server is [00:02:22.420 --> 00:02:23.790] just a computer. [00:02:23.790 --> 00:02:24.770] And if that [00:02:24.770 --> 00:02:25.640] computer is off, [00:02:25.640 --> 00:02:26.440] then it doesn't [00:02:26.440 --> 00:02:27.250] matter how many [00:02:27.250 --> 00:02:28.060] bars I have, I'm [00:02:28.060 --> 00:02:28.570] not going to be [00:02:28.570 --> 00:02:30.680] able to connect. [00:02:30.970 --> 00:02:31.900] So that's a [00:02:31.900 --> 00:02:33.040] variable that's, [00:02:33.040 --> 00:02:35.130] you know, included [00:02:35.130 --> 00:02:35.710] here. [00:02:35.710 --> 00:02:36.670] And there are so [00:02:36.670 --> 00:02:37.920] many, you know, [00:02:37.920 --> 00:02:40.050] different ways that [00:02:40.050 --> 00:02:41.310] that connection can [00:02:41.310 --> 00:02:42.990] get compromised. [00:02:42.990 --> 00:02:45.270] So it's really [00:02:45.270 --> 00:02:47.400] amazing that it [00:02:47.400 --> 00:02:49.150] works at all. [00:02:49.150 --> 00:02:50.330] And that's where we're [00:02:50.330 --> 00:02:51.170] at right now with [00:02:51.170 --> 00:02:51.610] network [00:02:51.610 --> 00:02:52.790] connectivity. [00:02:52.790 --> 00:02:55.050] It's getting better. [00:02:55.050 --> 00:02:56.180] You know, this was [00:02:56.180 --> 00:02:57.260] not possible even [00:02:57.260 --> 00:02:58.320] just a few years [00:02:58.320 --> 00:02:58.560] ago. [00:02:58.560 --> 00:02:59.490] So it's pretty [00:02:59.490 --> 00:03:00.300] exciting. [00:03:00.300 --> 00:03:01.020] All right, we'll [00:03:01.020 --> 00:03:01.600] leave it at that [00:03:01.600 --> 00:03:02.260] and we'll see what [00:03:02.260 --> 00:03:02.750] that looks like [00:03:02.750 --> 00:03:03.850] later.