WEBVTT Kind: captions Language: en 00:00:00.960 --> 00:00:02.149 align:start position:0% So,<00:00:01.199> there's<00:00:01.439> been<00:00:01.520> an<00:00:01.760> interesting 00:00:02.149 --> 00:00:02.159 align:start position:0% So, there's been an interesting 00:00:02.159 --> 00:00:04.070 align:start position:0% So, there's been an interesting narrative<00:00:02.560> playing<00:00:02.879> out<00:00:03.040> in<00:00:03.200> the<00:00:03.360> world<00:00:03.520> of<00:00:03.679> AI 00:00:04.070 --> 00:00:04.080 align:start position:0% narrative playing out in the world of AI 00:00:04.080 --> 00:00:06.550 align:start position:0% narrative playing out in the world of AI right<00:00:04.319> now<00:00:04.799> and<00:00:05.040> I've<00:00:05.359> just<00:00:05.520> been<00:00:05.839> absolutely 00:00:06.550 --> 00:00:06.560 align:start position:0% right now and I've just been absolutely 00:00:06.560 --> 00:00:08.470 align:start position:0% right now and I've just been absolutely fascinated<00:00:07.120> by<00:00:07.279> it<00:00:07.759> and<00:00:07.919> that's<00:00:08.160> the<00:00:08.320> whole 00:00:08.470 --> 00:00:08.480 align:start position:0% fascinated by it and that's the whole 00:00:08.480 --> 00:00:10.950 align:start position:0% fascinated by it and that's the whole narrative<00:00:08.960> of<00:00:09.200> the<00:00:10.000> openw<00:00:10.400> weight<00:00:10.639> models 00:00:10.950 --> 00:00:10.960 align:start position:0% narrative of the openw weight models 00:00:10.960 --> 00:00:13.270 align:start position:0% narrative of the openw weight models versus<00:00:11.200> the<00:00:11.440> closed<00:00:11.840> weight<00:00:12.080> models<00:00:12.639> and<00:00:12.960> that 00:00:13.270 --> 00:00:13.280 align:start position:0% versus the closed weight models and that 00:00:13.280 --> 00:00:15.990 align:start position:0% versus the closed weight models and that whole<00:00:13.679> storyline<00:00:14.639> sort<00:00:14.880> of<00:00:15.200> accelerated<00:00:15.839> this 00:00:15.990 --> 00:00:16.000 align:start position:0% whole storyline sort of accelerated this 00:00:16.000 --> 00:00:17.910 align:start position:0% whole storyline sort of accelerated this week.<00:00:16.240> Earlier<00:00:16.560> this<00:00:16.800> week,<00:00:17.039> OpenAI<00:00:17.680> showed 00:00:17.910 --> 00:00:17.920 align:start position:0% week. Earlier this week, OpenAI showed 00:00:17.920 --> 00:00:20.070 align:start position:0% week. Earlier this week, OpenAI showed off<00:00:18.160> the<00:00:18.400> first<00:00:18.560> results<00:00:18.880> from<00:00:19.119> its<00:00:19.359> Jalapeno 00:00:20.070 --> 00:00:20.080 align:start position:0% off the first results from its Jalapeno 00:00:20.080 --> 00:00:22.230 align:start position:0% off the first results from its Jalapeno chip.<00:00:20.400> This<00:00:20.560> is<00:00:20.640> an<00:00:20.880> AI<00:00:21.279> inference<00:00:21.840> chip<00:00:22.080> that 00:00:22.230 --> 00:00:22.240 align:start position:0% chip. This is an AI inference chip that 00:00:22.240 --> 00:00:24.230 align:start position:0% chip. This is an AI inference chip that they're<00:00:22.480> building<00:00:23.039> to<00:00:23.359> try<00:00:23.519> to<00:00:23.760> release 00:00:24.230 --> 00:00:24.240 align:start position:0% they're building to try to release 00:00:24.240 --> 00:00:26.790 align:start position:0% they're building to try to release reliance<00:00:24.880> on<00:00:25.519> Nvidia.<00:00:26.160> They<00:00:26.320> announced<00:00:26.640> that 00:00:26.790 --> 00:00:26.800 align:start position:0% reliance on Nvidia. They announced that 00:00:26.800 --> 00:00:28.390 align:start position:0% reliance on Nvidia. They announced that they<00:00:26.960> were<00:00:27.039> working<00:00:27.199> on<00:00:27.439> it<00:00:27.840> not<00:00:28.080> too<00:00:28.320> long 00:00:28.390 --> 00:00:28.400 align:start position:0% they were working on it not too long 00:00:28.400 --> 00:00:30.390 align:start position:0% they were working on it not too long ago,<00:00:28.880> but<00:00:29.039> they<00:00:29.279> finally<00:00:29.599> showed<00:00:29.840> off<00:00:30.080> some 00:00:30.390 --> 00:00:30.400 align:start position:0% ago, but they finally showed off some 00:00:30.400 --> 00:00:32.310 align:start position:0% ago, but they finally showed off some results<00:00:30.720> of<00:00:30.960> what<00:00:31.119> it's<00:00:31.439> capable<00:00:31.679> of.<00:00:32.000> We<00:00:32.239> can 00:00:32.310 --> 00:00:32.320 align:start position:0% results of what it's capable of. We can 00:00:32.320 --> 00:00:34.709 align:start position:0% results of what it's capable of. We can see<00:00:32.480> here<00:00:32.719> on<00:00:33.200> openweight<00:00:33.920> models,<00:00:34.399> it's 00:00:34.709 --> 00:00:34.719 align:start position:0% see here on openweight models, it's 00:00:34.719 --> 00:00:37.030 align:start position:0% see here on openweight models, it's getting<00:00:34.960> upwards<00:00:35.360> of<00:00:35.680> 104<00:00:36.480> times<00:00:36.719> the 00:00:37.030 --> 00:00:37.040 align:start position:0% getting upwards of 104 times the 00:00:37.040 --> 00:00:38.950 align:start position:0% getting upwards of 104 times the performance.<00:00:37.680> Now,<00:00:37.840> they<00:00:38.000> tested<00:00:38.399> this<00:00:38.640> on 00:00:38.950 --> 00:00:38.960 align:start position:0% performance. Now, they tested this on 00:00:38.960 --> 00:00:41.430 align:start position:0% performance. Now, they tested this on public<00:00:39.360> models<00:00:39.840> on<00:00:40.160> purpose<00:00:40.719> because<00:00:41.200> it's 00:00:41.430 --> 00:00:41.440 align:start position:0% public models on purpose because it's 00:00:41.440 --> 00:00:43.270 align:start position:0% public models on purpose because it's much<00:00:41.680> more<00:00:41.920> verifiable.<00:00:42.719> Other<00:00:42.960> companies 00:00:43.270 --> 00:00:43.280 align:start position:0% much more verifiable. Other companies 00:00:43.280 --> 00:00:45.350 align:start position:0% much more verifiable. Other companies can<00:00:43.440> go<00:00:43.600> and<00:00:43.760> use<00:00:44.000> other<00:00:44.320> chips<00:00:44.719> and<00:00:44.960> see<00:00:45.200> what 00:00:45.350 --> 00:00:45.360 align:start position:0% can go and use other chips and see what 00:00:45.360 --> 00:00:47.430 align:start position:0% can go and use other chips and see what sort<00:00:45.520> of<00:00:45.680> performance<00:00:46.079> they<00:00:46.239> can<00:00:46.399> get<00:00:46.480> on<00:00:46.719> GPT 00:00:47.430 --> 00:00:47.440 align:start position:0% sort of performance they can get on GPT 00:00:47.440 --> 00:00:50.709 align:start position:0% sort of performance they can get on GPT OSS<00:00:48.079> or<00:00:48.399> Deep<00:00:48.719> Seagar<00:00:49.200> 1,<00:00:49.680> etc.<00:00:50.079> However,<00:00:50.480> they 00:00:50.709 --> 00:00:50.719 align:start position:0% OSS or Deep Seagar 1, etc. However, they 00:00:50.719 --> 00:00:54.389 align:start position:0% OSS or Deep Seagar 1, etc. However, they can't<00:00:50.960> really<00:00:51.200> go<00:00:51.440> and<00:00:52.000> test<00:00:52.399> GPT<00:00:53.120> 5.6<00:00:53.760> 6<00:00:54.079> on 00:00:54.389 --> 00:00:54.399 align:start position:0% can't really go and test GPT 5.6 6 on 00:00:54.399 --> 00:00:56.069 align:start position:0% can't really go and test GPT 5.6 6 on different<00:00:54.800> chips<00:00:55.120> since<00:00:55.360> those<00:00:55.520> all<00:00:55.680> run<00:00:55.840> in 00:00:56.069 --> 00:00:56.079 align:start position:0% different chips since those all run in 00:00:56.079 --> 00:00:58.310 align:start position:0% different chips since those all run in OpenAI's<00:00:56.719> cloud.<00:00:57.120> They<00:00:57.360> do<00:00:57.600> however<00:00:58.000> claim 00:00:58.310 --> 00:00:58.320 align:start position:0% OpenAI's cloud. They do however claim 00:00:58.320 --> 00:00:59.670 align:start position:0% OpenAI's cloud. They do however claim that<00:00:58.559> in<00:00:58.719> their<00:00:58.879> internal<00:00:59.359> testing, 00:00:59.670 --> 00:00:59.680 align:start position:0% that in their internal testing, 00:00:59.680 --> 00:01:01.990 align:start position:0% that in their internal testing, Jalapeno's<00:01:00.399> advantage<00:01:00.800> widened<00:01:01.359> further<00:01:01.760> on 00:01:01.990 --> 00:01:02.000 align:start position:0% Jalapeno's advantage widened further on 00:01:02.000 --> 00:01:04.070 align:start position:0% Jalapeno's advantage widened further on their<00:01:02.160> own<00:01:02.320> Frontier<00:01:02.879> Open<00:01:03.120> AAI<00:01:03.440> models.<00:01:03.920> Now, 00:01:04.070 --> 00:01:04.080 align:start position:0% their own Frontier Open AAI models. Now, 00:01:04.080 --> 00:01:05.590 align:start position:0% their own Frontier Open AAI models. Now, this<00:01:04.239> is<00:01:04.400> interesting<00:01:04.720> to<00:01:04.960> me<00:01:05.119> because<00:01:05.360> it 00:01:05.590 --> 00:01:05.600 align:start position:0% this is interesting to me because it 00:01:05.600 --> 00:01:07.990 align:start position:0% this is interesting to me because it shows<00:01:05.840> that<00:01:06.000> OpenAI<00:01:06.720> is<00:01:07.040> actively<00:01:07.600> taking 00:01:07.990 --> 00:01:08.000 align:start position:0% shows that OpenAI is actively taking 00:01:08.000 --> 00:01:10.710 align:start position:0% shows that OpenAI is actively taking steps<00:01:08.560> to<00:01:08.880> release<00:01:09.360> reliance<00:01:09.840> on<00:01:10.080> Nvidia 00:01:10.710 --> 00:01:10.720 align:start position:0% steps to release reliance on Nvidia 00:01:10.720 --> 00:01:12.630 align:start position:0% steps to release reliance on Nvidia chips.<00:01:11.119> Now,<00:01:11.360> they<00:01:11.520> recently<00:01:12.000> partnered<00:01:12.479> up 00:01:12.630 --> 00:01:12.640 align:start position:0% chips. Now, they recently partnered up 00:01:12.640 --> 00:01:15.990 align:start position:0% chips. Now, they recently partnered up with<00:01:13.040> Cerebrris<00:01:13.760> to<00:01:14.159> do<00:01:14.560> ultraast<00:01:15.280> inference 00:01:15.990 --> 00:01:16.000 align:start position:0% with Cerebrris to do ultraast inference 00:01:16.000 --> 00:01:17.990 align:start position:0% with Cerebrris to do ultraast inference with<00:01:16.159> their<00:01:16.400> chips<00:01:16.880> and<00:01:17.119> now<00:01:17.280> it<00:01:17.520> even<00:01:17.759> seems 00:01:17.990 --> 00:01:18.000 align:start position:0% with their chips and now it even seems 00:01:18.000 --> 00:01:19.830 align:start position:0% with their chips and now it even seems like<00:01:18.159> they're<00:01:18.400> making<00:01:18.640> like<00:01:18.880> a<00:01:19.200> competing 00:01:19.830 --> 00:01:19.840 align:start position:0% like they're making like a competing 00:01:19.840 --> 00:01:21.510 align:start position:0% like they're making like a competing chip<00:01:20.159> to<00:01:20.400> what<00:01:20.560> they<00:01:20.720> were<00:01:20.799> getting<00:01:20.960> from<00:01:21.200> the 00:01:21.510 --> 00:01:21.520 align:start position:0% chip to what they were getting from the 00:01:21.520 --> 00:01:23.270 align:start position:0% chip to what they were getting from the Cerebrris<00:01:22.159> chip.<00:01:22.479> One<00:01:22.640> thing<00:01:22.799> that<00:01:23.040> is 00:01:23.270 --> 00:01:23.280 align:start position:0% Cerebrris chip. One thing that is 00:01:23.280 --> 00:01:25.030 align:start position:0% Cerebrris chip. One thing that is important<00:01:23.600> to<00:01:23.840> note<00:01:24.080> though<00:01:24.320> is<00:01:24.560> that<00:01:24.720> these 00:01:25.030 --> 00:01:25.040 align:start position:0% important to note though is that these 00:01:25.040 --> 00:01:27.190 align:start position:0% important to note though is that these are<00:01:25.200> specifically<00:01:25.759> for<00:01:26.240> inference.<00:01:26.960> So 00:01:27.190 --> 00:01:27.200 align:start position:0% are specifically for inference. So 00:01:27.200 --> 00:01:29.270 align:start position:0% are specifically for inference. So inference<00:01:27.680> is<00:01:27.920> essentially<00:01:28.400> when<00:01:28.640> you<00:01:28.799> type<00:01:29.040> a 00:01:29.270 --> 00:01:29.280 align:start position:0% inference is essentially when you type a 00:01:29.280 --> 00:01:31.350 align:start position:0% inference is essentially when you type a prompt<00:01:29.680> and<00:01:30.000> you<00:01:30.159> get<00:01:30.240> the<00:01:30.479> output.<00:01:30.960> That<00:01:31.200> is 00:01:31.350 --> 00:01:31.360 align:start position:0% prompt and you get the output. That is 00:01:31.360 --> 00:01:34.230 align:start position:0% prompt and you get the output. That is the<00:01:31.600> inference<00:01:32.240> phase<00:01:32.720> of<00:01:33.040> AI.<00:01:33.600> These<00:01:33.840> chips 00:01:34.230 --> 00:01:34.240 align:start position:0% the inference phase of AI. These chips 00:01:34.240 --> 00:01:36.870 align:start position:0% the inference phase of AI. These chips don't<00:01:34.479> appear<00:01:34.720> to<00:01:34.880> be<00:01:35.119> designed<00:01:35.759> for<00:01:36.320> actually 00:01:36.870 --> 00:01:36.880 align:start position:0% don't appear to be designed for actually 00:01:36.880 --> 00:01:39.190 align:start position:0% don't appear to be designed for actually training<00:01:37.439> brand<00:01:37.759> new<00:01:38.000> models<00:01:38.720> which<00:01:38.960> they 00:01:39.190 --> 00:01:39.200 align:start position:0% training brand new models which they 00:01:39.200 --> 00:01:42.310 align:start position:0% training brand new models which they will<00:01:39.360> likely<00:01:39.920> still<00:01:40.320> go<00:01:40.560> to<00:01:41.040> Nvidia<00:01:41.600> to<00:01:41.840> do<00:01:42.240> at 00:01:42.310 --> 00:01:42.320 align:start position:0% will likely still go to Nvidia to do at 00:01:42.320 --> 00:01:44.550 align:start position:0% will likely still go to Nvidia to do at least<00:01:42.640> in<00:01:42.880> the<00:01:43.040> near<00:01:43.280> term.<00:01:43.680> However,<00:01:44.240> this 00:01:44.550 --> 00:01:44.560 align:start position:0% least in the near term. However, this 00:01:44.560 --> 00:01:46.710 align:start position:0% least in the near term. However, this story<00:01:44.799> gets<00:01:45.119> even<00:01:45.520> more<00:01:45.920> interesting. 00:01:46.710 --> 00:01:46.720 align:start position:0% story gets even more interesting. 00:01:46.720 --> 00:01:49.190 align:start position:0% story gets even more interesting. According<00:01:47.119> to<00:01:47.360> the<00:01:47.759> information,<00:01:48.479> Nvidia 00:01:49.190 --> 00:01:49.200 align:start position:0% According to the information, Nvidia 00:01:49.200 --> 00:01:51.910 align:start position:0% According to the information, Nvidia agreed<00:01:49.680> to<00:01:50.000> buy<00:01:50.479> hugging<00:01:50.960> face.<00:01:51.439> Now,<00:01:51.680> I 00:01:51.910 --> 00:01:51.920 align:start position:0% agreed to buy hugging face. Now, I 00:01:51.920 --> 00:01:53.749 align:start position:0% agreed to buy hugging face. Now, I emphasized<00:01:52.560> according<00:01:52.880> to<00:01:52.960> the<00:01:53.200> information 00:01:53.749 --> 00:01:53.759 align:start position:0% emphasized according to the information 00:01:53.759 --> 00:01:55.990 align:start position:0% emphasized according to the information because<00:01:54.000> neither<00:01:54.399> HuggingFace<00:01:55.119> or<00:01:55.360> Nvidia 00:01:55.990 --> 00:01:56.000 align:start position:0% because neither HuggingFace or Nvidia 00:01:56.000 --> 00:01:57.990 align:start position:0% because neither HuggingFace or Nvidia have<00:01:56.240> publicly<00:01:56.640> made<00:01:56.880> an<00:01:57.119> announcement<00:01:57.600> about 00:01:57.990 --> 00:01:58.000 align:start position:0% have publicly made an announcement about 00:01:58.000 --> 00:02:00.630 align:start position:0% have publicly made an announcement about this<00:01:58.479> as<00:01:58.719> of<00:01:58.880> the<00:01:59.119> time<00:01:59.280> of<00:01:59.680> me<00:02:00.000> recording<00:02:00.399> it. 00:02:00.630 --> 00:02:00.640 align:start position:0% this as of the time of me recording it. 00:02:00.640 --> 00:02:01.990 align:start position:0% this as of the time of me recording it. Now,<00:02:00.799> if<00:02:00.880> you're<00:02:01.040> not<00:02:01.200> familiar<00:02:01.439> with<00:02:01.600> Hugging 00:02:01.990 --> 00:02:02.000 align:start position:0% Now, if you're not familiar with Hugging 00:02:02.000 --> 00:02:04.630 align:start position:0% Now, if you're not familiar with Hugging Face,<00:02:02.320> Hugging<00:02:02.719> Face<00:02:03.040> is<00:02:03.439> like<00:02:03.840> the<00:02:04.159> GitHub 00:02:04.630 --> 00:02:04.640 align:start position:0% Face, Hugging Face is like the GitHub 00:02:04.640 --> 00:02:07.030 align:start position:0% Face, Hugging Face is like the GitHub for<00:02:04.960> AI<00:02:05.520> models.<00:02:06.000> When<00:02:06.320> companies<00:02:06.640> go<00:02:06.799> and 00:02:07.030 --> 00:02:07.040 align:start position:0% for AI models. When companies go and 00:02:07.040 --> 00:02:08.790 align:start position:0% for AI models. When companies go and make<00:02:07.200> open<00:02:07.600> weight<00:02:07.920> models<00:02:08.160> and<00:02:08.399> they<00:02:08.560> go<00:02:08.640> and 00:02:08.790 --> 00:02:08.800 align:start position:0% make open weight models and they go and 00:02:08.800 --> 00:02:11.190 align:start position:0% make open weight models and they go and make<00:02:08.959> them<00:02:09.280> publicly<00:02:09.759> available<00:02:10.239> to<00:02:10.479> anybody, 00:02:11.190 --> 00:02:11.200 align:start position:0% make them publicly available to anybody, 00:02:11.200 --> 00:02:13.110 align:start position:0% make them publicly available to anybody, they<00:02:11.520> typically<00:02:12.000> go<00:02:12.239> and<00:02:12.480> store<00:02:12.800> those 00:02:13.110 --> 00:02:13.120 align:start position:0% they typically go and store those 00:02:13.120 --> 00:02:15.510 align:start position:0% they typically go and store those weights<00:02:13.520> on<00:02:13.760> HuggingFace.<00:02:14.640> Now,<00:02:14.879> HuggingFace 00:02:15.510 --> 00:02:15.520 align:start position:0% weights on HuggingFace. Now, HuggingFace 00:02:15.520 --> 00:02:18.070 align:start position:0% weights on HuggingFace. Now, HuggingFace is<00:02:15.680> also<00:02:16.160> a<00:02:16.400> GPU<00:02:16.959> provider.<00:02:17.440> You<00:02:17.680> can<00:02:17.760> go<00:02:17.920> on 00:02:18.070 --> 00:02:18.080 align:start position:0% is also a GPU provider. You can go on 00:02:18.080 --> 00:02:20.550 align:start position:0% is also a GPU provider. You can go on their<00:02:18.319> site<00:02:18.560> and<00:02:19.120> essentially<00:02:19.520> rent<00:02:19.920> GPUs 00:02:20.550 --> 00:02:20.560 align:start position:0% their site and essentially rent GPUs 00:02:20.560 --> 00:02:22.550 align:start position:0% their site and essentially rent GPUs from<00:02:20.800> them<00:02:21.280> to<00:02:21.599> play<00:02:21.840> around<00:02:22.080> with<00:02:22.319> the 00:02:22.550 --> 00:02:22.560 align:start position:0% from them to play around with the 00:02:22.560 --> 00:02:24.309 align:start position:0% from them to play around with the various<00:02:22.879> models<00:02:23.200> that<00:02:23.440> are<00:02:23.680> available<00:02:24.000> on 00:02:24.309 --> 00:02:24.319 align:start position:0% various models that are available on 00:02:24.319 --> 00:02:26.070 align:start position:0% various models that are available on their<00:02:24.480> site.<00:02:24.720> Now,<00:02:24.959> here's<00:02:25.120> why<00:02:25.280> I<00:02:25.440> find<00:02:25.680> this 00:02:26.070 --> 00:02:26.080 align:start position:0% their site. Now, here's why I find this 00:02:26.080 --> 00:02:28.070 align:start position:0% their site. Now, here's why I find this super<00:02:26.480> fascinating.<00:02:27.040> You<00:02:27.200> have<00:02:27.280> OpenAI<00:02:27.840> over 00:02:28.070 --> 00:02:28.080 align:start position:0% super fascinating. You have OpenAI over 00:02:28.080 --> 00:02:29.589 align:start position:0% super fascinating. You have OpenAI over here<00:02:28.319> starting<00:02:28.560> to<00:02:28.720> build<00:02:28.879> their<00:02:29.120> own<00:02:29.280> chips 00:02:29.589 --> 00:02:29.599 align:start position:0% here starting to build their own chips 00:02:29.599 --> 00:02:31.990 align:start position:0% here starting to build their own chips for<00:02:29.840> inference<00:02:30.560> chips<00:02:30.879> that<00:02:31.040> they<00:02:31.440> would<00:02:31.680> have 00:02:31.990 --> 00:02:32.000 align:start position:0% for inference chips that they would have 00:02:32.000 --> 00:02:34.229 align:start position:0% for inference chips that they would have bought<00:02:32.319> from<00:02:32.640> Nvidia<00:02:33.280> if<00:02:33.519> they<00:02:33.760> didn't<00:02:34.000> start 00:02:34.229 --> 00:02:34.239 align:start position:0% bought from Nvidia if they didn't start 00:02:34.239 --> 00:02:36.309 align:start position:0% bought from Nvidia if they didn't start making<00:02:34.480> them<00:02:34.720> themselves.<00:02:35.440> You<00:02:35.599> have<00:02:35.760> Meta 00:02:36.309 --> 00:02:36.319 align:start position:0% making them themselves. You have Meta 00:02:36.319 --> 00:02:37.990 align:start position:0% making them themselves. You have Meta starting<00:02:36.640> to<00:02:36.800> build<00:02:37.200> their<00:02:37.519> own<00:02:37.680> chips 00:02:37.990 --> 00:02:38.000 align:start position:0% starting to build their own chips 00:02:38.000 --> 00:02:40.150 align:start position:0% starting to build their own chips inhouse.<00:02:38.720> You<00:02:38.879> have<00:02:39.040> Google<00:02:39.360> who's<00:02:39.760> already 00:02:40.150 --> 00:02:40.160 align:start position:0% inhouse. You have Google who's already 00:02:40.160 --> 00:02:41.430 align:start position:0% inhouse. You have Google who's already building<00:02:40.480> their<00:02:40.720> own<00:02:40.800> chips<00:02:41.120> with<00:02:41.280> their 00:02:41.430 --> 00:02:41.440 align:start position:0% building their own chips with their 00:02:41.440 --> 00:02:43.990 align:start position:0% building their own chips with their TPUs.<00:02:42.239> And<00:02:42.400> as<00:02:42.640> these<00:02:42.959> AI<00:02:43.360> companies<00:02:43.760> get 00:02:43.990 --> 00:02:44.000 align:start position:0% TPUs. And as these AI companies get 00:02:44.000 --> 00:02:45.670 align:start position:0% TPUs. And as these AI companies get bigger<00:02:44.160> and<00:02:44.400> bigger<00:02:44.720> and<00:02:45.040> start<00:02:45.280> trying<00:02:45.519> to 00:02:45.670 --> 00:02:45.680 align:start position:0% bigger and bigger and start trying to 00:02:45.680 --> 00:02:49.110 align:start position:0% bigger and bigger and start trying to own<00:02:46.239> more<00:02:46.640> of<00:02:46.879> the<00:02:47.599> stack<00:02:48.080> themselves,<00:02:48.959> it 00:02:49.110 --> 00:02:49.120 align:start position:0% own more of the stack themselves, it 00:02:49.120 --> 00:02:50.869 align:start position:0% own more of the stack themselves, it could<00:02:49.280> start<00:02:49.440> to<00:02:49.680> shift<00:02:49.920> some<00:02:50.080> business<00:02:50.480> away 00:02:50.869 --> 00:02:50.879 align:start position:0% could start to shift some business away 00:02:50.879 --> 00:02:53.910 align:start position:0% could start to shift some business away from<00:02:51.280> Nvidia.<00:02:51.920> But<00:02:52.080> Nvidia<00:02:52.640> is<00:02:52.959> going<00:02:53.360> allin 00:02:53.910 --> 00:02:53.920 align:start position:0% from Nvidia. But Nvidia is going allin 00:02:53.920 --> 00:02:55.990 align:start position:0% from Nvidia. But Nvidia is going allin on<00:02:54.319> open-source.<00:02:55.200> All<00:02:55.360> of<00:02:55.519> the<00:02:55.680> models 00:02:55.990 --> 00:02:56.000 align:start position:0% on open-source. All of the models 00:02:56.000 --> 00:02:58.390 align:start position:0% on open-source. All of the models Nvidia's<00:02:56.720> been<00:02:56.879> developing<00:02:57.440> and<00:02:57.760> releasing 00:02:58.390 --> 00:02:58.400 align:start position:0% Nvidia's been developing and releasing 00:02:58.400 --> 00:03:00.630 align:start position:0% Nvidia's been developing and releasing have<00:02:58.720> been<00:02:59.040> these<00:02:59.440> openweight<00:03:00.080> models<00:03:00.400> that 00:03:00.630 --> 00:03:00.640 align:start position:0% have been these openweight models that 00:03:00.640 --> 00:03:03.270 align:start position:0% have been these openweight models that anybody<00:03:01.200> can<00:03:01.440> use.<00:03:02.080> Now,<00:03:02.560> most<00:03:02.800> of<00:03:02.959> them<00:03:03.120> are 00:03:03.270 --> 00:03:03.280 align:start position:0% anybody can use. Now, most of them are 00:03:03.280 --> 00:03:05.350 align:start position:0% anybody can use. Now, most of them are too<00:03:03.519> big<00:03:03.680> to<00:03:03.920> run<00:03:04.159> on<00:03:04.400> a<00:03:04.640> personal<00:03:04.959> computer, 00:03:05.350 --> 00:03:05.360 align:start position:0% too big to run on a personal computer, 00:03:05.360 --> 00:03:06.790 align:start position:0% too big to run on a personal computer, so<00:03:05.519> you<00:03:05.680> need<00:03:05.760> to<00:03:05.840> go<00:03:06.000> and<00:03:06.159> run<00:03:06.319> them<00:03:06.400> in<00:03:06.560> a 00:03:06.790 --> 00:03:06.800 align:start position:0% so you need to go and run them in a 00:03:06.800 --> 00:03:09.350 align:start position:0% so you need to go and run them in a cloud.<00:03:07.120> hugging<00:03:07.599> face<00:03:08.000> is<00:03:08.319> where<00:03:08.640> people<00:03:09.040> go 00:03:09.350 --> 00:03:09.360 align:start position:0% cloud. hugging face is where people go 00:03:09.360 --> 00:03:11.589 align:start position:0% cloud. hugging face is where people go oftent<00:03:09.760> times<00:03:10.080> to<00:03:10.400> run<00:03:10.640> these<00:03:10.959> models<00:03:11.280> in<00:03:11.440> the 00:03:11.589 --> 00:03:11.599 align:start position:0% oftent times to run these models in the 00:03:11.599 --> 00:03:13.990 align:start position:0% oftent times to run these models in the cloud<00:03:11.920> now.<00:03:12.159> And<00:03:12.319> if<00:03:12.560> Nvidia<00:03:13.280> owns<00:03:13.599> all<00:03:13.840> of 00:03:13.990 --> 00:03:14.000 align:start position:0% cloud now. And if Nvidia owns all of 00:03:14.000 --> 00:03:16.229 align:start position:0% cloud now. And if Nvidia owns all of that<00:03:14.239> infrastructure<00:03:15.040> to<00:03:15.440> run<00:03:15.680> these<00:03:16.000> models 00:03:16.229 --> 00:03:16.239 align:start position:0% that infrastructure to run these models 00:03:16.239 --> 00:03:17.990 align:start position:0% that infrastructure to run these models in<00:03:16.400> the<00:03:16.560> cloud<00:03:16.959> and<00:03:17.200> more<00:03:17.360> and<00:03:17.519> more<00:03:17.760> people 00:03:17.990 --> 00:03:18.000 align:start position:0% in the cloud and more and more people 00:03:18.000 --> 00:03:20.149 align:start position:0% in the cloud and more and more people start<00:03:18.239> switching<00:03:18.560> to<00:03:18.879> openw<00:03:19.280> weight<00:03:19.599> models, 00:03:20.149 --> 00:03:20.159 align:start position:0% start switching to openw weight models, 00:03:20.159 --> 00:03:22.710 align:start position:0% start switching to openw weight models, well<00:03:20.319> then<00:03:20.720> Nvidia's<00:03:21.519> no<00:03:21.840> longer<00:03:22.159> going<00:03:22.319> to<00:03:22.480> be 00:03:22.710 --> 00:03:22.720 align:start position:0% well then Nvidia's no longer going to be 00:03:22.720 --> 00:03:25.350 align:start position:0% well then Nvidia's no longer going to be as<00:03:23.120> reliant<00:03:23.519> on<00:03:23.760> the<00:03:24.000> open<00:03:24.319> AIs<00:03:24.720> and<00:03:24.800> the<00:03:24.959> metas 00:03:25.350 --> 00:03:25.360 align:start position:0% as reliant on the open AIs and the metas 00:03:25.360 --> 00:03:27.509 align:start position:0% as reliant on the open AIs and the metas of<00:03:25.519> the<00:03:25.680> world<00:03:25.920> for<00:03:26.239> this<00:03:26.480> inference<00:03:27.040> compute 00:03:27.509 --> 00:03:27.519 align:start position:0% of the world for this inference compute 00:03:27.519 --> 00:03:29.589 align:start position:0% of the world for this inference compute because<00:03:27.840> now<00:03:28.239> everybody<00:03:28.640> that's<00:03:29.040> moving<00:03:29.280> to 00:03:29.589 --> 00:03:29.599 align:start position:0% because now everybody that's moving to 00:03:29.599 --> 00:03:31.430 align:start position:0% because now everybody that's moving to openweight<00:03:30.159> models<00:03:30.640> is<00:03:30.879> now<00:03:31.120> going<00:03:31.280> to 00:03:31.430 --> 00:03:31.440 align:start position:0% openweight models is now going to 00:03:31.440 --> 00:03:33.910 align:start position:0% openweight models is now going to directly<00:03:31.840> go<00:03:32.000> to<00:03:32.159> an<00:03:32.319> Nvidia<00:03:32.959> company<00:03:33.519> to<00:03:33.760> get 00:03:33.910 --> 00:03:33.920 align:start position:0% directly go to an Nvidia company to get 00:03:33.920 --> 00:03:35.830 align:start position:0% directly go to an Nvidia company to get their<00:03:34.239> inference<00:03:34.799> provided.<00:03:35.360> So<00:03:35.599> they're 00:03:35.830 --> 00:03:35.840 align:start position:0% their inference provided. So they're 00:03:35.840 --> 00:03:37.589 align:start position:0% their inference provided. So they're betting<00:03:36.159> that<00:03:36.480> openweight<00:03:37.040> models<00:03:37.360> are<00:03:37.519> going 00:03:37.589 --> 00:03:37.599 align:start position:0% betting that openweight models are going 00:03:37.599 --> 00:03:39.190 align:start position:0% betting that openweight models are going to<00:03:37.680> get<00:03:37.840> bigger<00:03:38.080> and<00:03:38.239> bigger<00:03:38.480> and<00:03:38.720> bigger<00:03:38.959> and 00:03:39.190 --> 00:03:39.200 align:start position:0% to get bigger and bigger and bigger and 00:03:39.200 --> 00:03:40.710 align:start position:0% to get bigger and bigger and bigger and take<00:03:39.360> away<00:03:39.599> more<00:03:39.760> and<00:03:40.000> more<00:03:40.159> market<00:03:40.480> share 00:03:40.710 --> 00:03:40.720 align:start position:0% take away more and more market share 00:03:40.720 --> 00:03:42.949 align:start position:0% take away more and more market share from<00:03:40.959> the<00:03:41.200> closed<00:03:41.599> models<00:03:42.080> and<00:03:42.319> with<00:03:42.560> owning 00:03:42.949 --> 00:03:42.959 align:start position:0% from the closed models and with owning 00:03:42.959 --> 00:03:44.949 align:start position:0% from the closed models and with owning hugging<00:03:43.360> face<00:03:43.840> they're<00:03:44.080> going<00:03:44.159> to<00:03:44.239> be<00:03:44.480> the 00:03:44.949 --> 00:03:44.959 align:start position:0% hugging face they're going to be the 00:03:44.959 --> 00:03:47.509 align:start position:0% hugging face they're going to be the dominant<00:03:45.599> compute<00:03:46.080> provider<00:03:46.720> of<00:03:47.040> everybody 00:03:47.509 --> 00:03:47.519 align:start position:0% dominant compute provider of everybody 00:03:47.519 --> 00:03:49.509 align:start position:0% dominant compute provider of everybody running<00:03:47.840> open<00:03:48.239> models<00:03:48.799> and<00:03:48.959> there<00:03:49.120> is<00:03:49.360> some 00:03:49.509 --> 00:03:49.519 align:start position:0% running open models and there is some 00:03:49.519 --> 00:03:51.990 align:start position:0% running open models and there is some data<00:03:50.080> showing<00:03:50.560> that<00:03:50.799> we<00:03:51.040> are<00:03:51.200> seeing<00:03:51.519> more<00:03:51.760> and 00:03:51.990 --> 00:03:52.000 align:start position:0% data showing that we are seeing more and 00:03:52.000 --> 00:03:54.710 align:start position:0% data showing that we are seeing more and more<00:03:52.480> people<00:03:52.799> and<00:03:53.120> companies<00:03:53.680> move<00:03:53.920> to<00:03:54.319> openw 00:03:54.710 --> 00:03:54.720 align:start position:0% more people and companies move to openw 00:03:54.720 --> 00:03:56.630 align:start position:0% more people and companies move to openw weightight<00:03:55.040> models.<00:03:55.680> So<00:03:55.920> check<00:03:56.159> this<00:03:56.319> out. 00:03:56.630 --> 00:03:56.640 align:start position:0% weightight models. So check this out. 00:03:56.640 --> 00:03:58.710 align:start position:0% weightight models. So check this out. This<00:03:56.799> is<00:03:56.879> a<00:03:57.040> post<00:03:57.200> from<00:03:57.439> the<00:03:57.680> CEO<00:03:58.000> of<00:03:58.159> Verscell 00:03:58.710 --> 00:03:58.720 align:start position:0% This is a post from the CEO of Verscell 00:03:58.720 --> 00:04:00.789 align:start position:0% This is a post from the CEO of Verscell and<00:03:58.959> he's<00:03:59.120> showing<00:03:59.360> that<00:03:59.599> 2<00:03:59.840> months<00:04:00.080> ago<00:04:00.560> most 00:04:00.789 --> 00:04:00.799 align:start position:0% and he's showing that 2 months ago most 00:04:00.799 --> 00:04:02.949 align:start position:0% and he's showing that 2 months ago most of<00:04:00.879> the<00:04:01.040> tokens<00:04:01.360> on<00:04:01.519> Verscell's<00:04:02.080> AI<00:04:02.480> gateway 00:04:02.949 --> 00:04:02.959 align:start position:0% of the tokens on Verscell's AI gateway 00:04:02.959 --> 00:04:07.110 align:start position:0% of the tokens on Verscell's AI gateway were<00:04:03.200> going<00:04:03.439> to<00:04:03.840> closedweight<00:04:04.720> models,<00:04:05.360> 71.6% 00:04:07.110 --> 00:04:07.120 align:start position:0% were going to closedweight models, 71.6% 00:04:07.120 --> 00:04:10.149 align:start position:0% were going to closedweight models, 71.6% with<00:04:07.360> only<00:04:07.680> 28.4%<00:04:09.040> going<00:04:09.360> to<00:04:09.519> openweight 00:04:10.149 --> 00:04:10.159 align:start position:0% with only 28.4% going to openweight 00:04:10.159 --> 00:04:12.229 align:start position:0% with only 28.4% going to openweight models.<00:04:10.640> Fast<00:04:10.959> forward<00:04:11.200> to<00:04:11.439> this<00:04:11.680> week<00:04:12.000> and 00:04:12.229 --> 00:04:12.239 align:start position:0% models. Fast forward to this week and 00:04:12.239 --> 00:04:15.910 align:start position:0% models. Fast forward to this week and now<00:04:12.560> open<00:04:12.959> models<00:04:13.760> account<00:04:14.080> for<00:04:14.560> 62%<00:04:15.599> of<00:04:15.760> the 00:04:15.910 --> 00:04:15.920 align:start position:0% now open models account for 62% of the 00:04:15.920 --> 00:04:19.349 align:start position:0% now open models account for 62% of the token<00:04:16.320> usage<00:04:16.880> versus<00:04:17.519> 38%<00:04:18.560> for<00:04:18.799> the<00:04:19.040> closed 00:04:19.349 --> 00:04:19.359 align:start position:0% token usage versus 38% for the closed 00:04:19.359 --> 00:04:21.670 align:start position:0% token usage versus 38% for the closed usage.<00:04:19.840> Now<00:04:20.079> there<00:04:20.239> is<00:04:20.400> a<00:04:20.560> caveat<00:04:21.120> to<00:04:21.280> this. 00:04:21.670 --> 00:04:21.680 align:start position:0% usage. Now there is a caveat to this. 00:04:21.680 --> 00:04:23.830 align:start position:0% usage. Now there is a caveat to this. When<00:04:21.840> we<00:04:22.000> go<00:04:22.079> to<00:04:22.160> their<00:04:22.400> AI<00:04:22.720> gateway<00:04:23.440> model 00:04:23.830 --> 00:04:23.840 align:start position:0% When we go to their AI gateway model 00:04:23.840 --> 00:04:25.830 align:start position:0% When we go to their AI gateway model leaderboard<00:04:24.479> here,<00:04:24.880> here's<00:04:25.120> the<00:04:25.360> graph<00:04:25.600> that 00:04:25.830 --> 00:04:25.840 align:start position:0% leaderboard here, here's the graph that 00:04:25.840 --> 00:04:28.150 align:start position:0% leaderboard here, here's the graph that he<00:04:26.080> was<00:04:26.240> showing<00:04:26.639> showing<00:04:26.880> the<00:04:27.120> token<00:04:27.520> volume. 00:04:28.150 --> 00:04:28.160 align:start position:0% he was showing showing the token volume. 00:04:28.160 --> 00:04:30.230 align:start position:0% he was showing showing the token volume. So<00:04:28.400> back<00:04:28.639> here,<00:04:29.040> blue<00:04:29.280> is<00:04:29.440> the<00:04:29.600> open<00:04:29.919> weight, 00:04:30.230 --> 00:04:30.240 align:start position:0% So back here, blue is the open weight, 00:04:30.240 --> 00:04:31.990 align:start position:0% So back here, blue is the open weight, yellow<00:04:30.560> is<00:04:30.800> the<00:04:30.960> closed<00:04:31.360> weight,<00:04:31.680> closed 00:04:31.990 --> 00:04:32.000 align:start position:0% yellow is the closed weight, closed 00:04:32.000 --> 00:04:33.510 align:start position:0% yellow is the closed weight, closed weight<00:04:32.240> models<00:04:32.560> were<00:04:32.800> getting<00:04:33.040> most<00:04:33.199> of<00:04:33.360> the 00:04:33.510 --> 00:04:33.520 align:start position:0% weight models were getting most of the 00:04:33.520 --> 00:04:35.590 align:start position:0% weight models were getting most of the token<00:04:33.919> usage.<00:04:34.479> However,<00:04:34.800> there<00:04:34.960> is<00:04:35.120> a<00:04:35.280> drop 00:04:35.590 --> 00:04:35.600 align:start position:0% token usage. However, there is a drop 00:04:35.600 --> 00:04:37.270 align:start position:0% token usage. However, there is a drop down<00:04:35.840> here<00:04:36.080> that<00:04:36.400> shows<00:04:36.560> the<00:04:36.800> amount<00:04:37.040> of 00:04:37.270 --> 00:04:37.280 align:start position:0% down here that shows the amount of 00:04:37.280 --> 00:04:39.990 align:start position:0% down here that shows the amount of requests.<00:04:38.080> If<00:04:38.320> we<00:04:38.479> select<00:04:38.880> requests<00:04:39.680> that 00:04:39.990 --> 00:04:40.000 align:start position:0% requests. If we select requests that 00:04:40.000 --> 00:04:41.749 align:start position:0% requests. If we select requests that tells<00:04:40.240> us<00:04:40.400> a<00:04:40.800> little<00:04:40.960> bit<00:04:41.120> different<00:04:41.360> of<00:04:41.520> a 00:04:41.749 --> 00:04:41.759 align:start position:0% tells us a little bit different of a 00:04:41.759 --> 00:04:43.990 align:start position:0% tells us a little bit different of a story.<00:04:42.240> It<00:04:42.400> tells<00:04:42.560> us<00:04:42.800> that<00:04:43.120> most<00:04:43.520> people<00:04:43.759> that 00:04:43.990 --> 00:04:44.000 align:start position:0% story. It tells us that most people that 00:04:44.000 --> 00:04:45.909 align:start position:0% story. It tells us that most people that are<00:04:44.160> using<00:04:44.400> this<00:04:44.639> gateway<00:04:45.120> are<00:04:45.440> still<00:04:45.680> making 00:04:45.909 --> 00:04:45.919 align:start position:0% are using this gateway are still making 00:04:45.919 --> 00:04:48.790 align:start position:0% are using this gateway are still making their<00:04:46.320> requests<00:04:47.199> to<00:04:47.520> closedweight<00:04:48.240> models. 00:04:48.790 --> 00:04:48.800 align:start position:0% their requests to closedweight models. 00:04:48.800 --> 00:04:52.390 align:start position:0% their requests to closedweight models. It's<00:04:49.040> still<00:04:49.360> 62%<00:04:50.320> closed<00:04:50.720> weight<00:04:50.960> to<00:04:51.199> 38%<00:04:52.080> open 00:04:52.390 --> 00:04:52.400 align:start position:0% It's still 62% closed weight to 38% open 00:04:52.400 --> 00:04:55.110 align:start position:0% It's still 62% closed weight to 38% open weight<00:04:52.720> on<00:04:53.120> actual<00:04:53.840> requests<00:04:54.240> to<00:04:54.479> the<00:04:54.639> models. 00:04:55.110 --> 00:04:55.120 align:start position:0% weight on actual requests to the models. 00:04:55.120 --> 00:04:56.790 align:start position:0% weight on actual requests to the models. But<00:04:55.199> the<00:04:55.360> amount<00:04:55.520> of<00:04:55.680> tokens<00:04:56.160> being<00:04:56.400> used, 00:04:56.790 --> 00:04:56.800 align:start position:0% But the amount of tokens being used, 00:04:56.800 --> 00:04:58.550 align:start position:0% But the amount of tokens being used, well,<00:04:57.040> it's<00:04:57.280> pretty<00:04:57.520> clear<00:04:57.759> that<00:04:58.080> the<00:04:58.320> open 00:04:58.550 --> 00:04:58.560 align:start position:0% well, it's pretty clear that the open 00:04:58.560 --> 00:05:00.790 align:start position:0% well, it's pretty clear that the open models<00:04:58.960> just<00:04:59.199> use<00:04:59.440> a<00:04:59.680> lot<00:04:59.840> more<00:05:00.160> tokens. 00:05:00.790 --> 00:05:00.800 align:start position:0% models just use a lot more tokens. 00:05:00.800 --> 00:05:02.310 align:start position:0% models just use a lot more tokens. Saying<00:05:01.040> that,<00:05:01.280> we<00:05:01.440> are<00:05:01.600> seeing<00:05:01.759> more<00:05:01.919> and<00:05:02.080> more 00:05:02.310 --> 00:05:02.320 align:start position:0% Saying that, we are seeing more and more 00:05:02.320 --> 00:05:04.390 align:start position:0% Saying that, we are seeing more and more requests<00:05:02.960> recently<00:05:03.600> going<00:05:03.840> to<00:05:04.000> more<00:05:04.160> of<00:05:04.240> the 00:05:04.390 --> 00:05:04.400 align:start position:0% requests recently going to more of the 00:05:04.400 --> 00:05:06.070 align:start position:0% requests recently going to more of the openweight<00:05:04.960> models.<00:05:05.440> So,<00:05:05.600> yeah,<00:05:05.759> I<00:05:05.919> think 00:05:06.070 --> 00:05:06.080 align:start position:0% openweight models. So, yeah, I think 00:05:06.080 --> 00:05:08.629 align:start position:0% openweight models. So, yeah, I think that<00:05:06.320> Nvidia<00:05:07.120> acquiring<00:05:07.600> hugging<00:05:08.000> face,<00:05:08.320> if 00:05:08.629 --> 00:05:08.639 align:start position:0% that Nvidia acquiring hugging face, if 00:05:08.639 --> 00:05:10.469 align:start position:0% that Nvidia acquiring hugging face, if true,<00:05:09.039> is<00:05:09.280> actually<00:05:09.520> a<00:05:09.759> pretty<00:05:10.000> big<00:05:10.160> deal 00:05:10.469 --> 00:05:10.479 align:start position:0% true, is actually a pretty big deal 00:05:10.479 --> 00:05:13.189 align:start position:0% true, is actually a pretty big deal because<00:05:10.800> again,<00:05:11.120> it<00:05:11.360> is<00:05:11.520> Nvidia<00:05:12.320> betting<00:05:12.800> that 00:05:13.189 --> 00:05:13.199 align:start position:0% because again, it is Nvidia betting that 00:05:13.199 --> 00:05:15.830 align:start position:0% because again, it is Nvidia betting that open<00:05:13.600> weight<00:05:13.919> is<00:05:14.639> more<00:05:14.960> of<00:05:15.120> the<00:05:15.280> future.<00:05:15.680> And 00:05:15.830 --> 00:05:15.840 align:start position:0% open weight is more of the future. And 00:05:15.840 --> 00:05:17.670 align:start position:0% open weight is more of the future. And to<00:05:16.000> round<00:05:16.240> this<00:05:16.479> whole<00:05:16.800> discussion<00:05:17.280> out, 00:05:17.670 --> 00:05:17.680 align:start position:0% to round this whole discussion out, 00:05:17.680 --> 00:05:18.870 align:start position:0% to round this whole discussion out, there<00:05:17.840> was<00:05:18.000> another<00:05:18.240> thing<00:05:18.400> that<00:05:18.639> happened 00:05:18.870 --> 00:05:18.880 align:start position:0% there was another thing that happened 00:05:18.880 --> 00:05:20.310 align:start position:0% there was another thing that happened this<00:05:19.120> week<00:05:19.280> that,<00:05:19.520> you<00:05:19.680> know,<00:05:19.840> kind<00:05:20.000> of<00:05:20.080> adds 00:05:20.310 --> 00:05:20.320 align:start position:0% this week that, you know, kind of adds 00:05:20.320 --> 00:05:21.990 align:start position:0% this week that, you know, kind of adds to<00:05:20.479> the<00:05:20.639> story<00:05:20.880> as<00:05:21.120> well,<00:05:21.440> and<00:05:21.600> that's<00:05:21.759> the 00:05:21.990 --> 00:05:22.000 align:start position:0% to the story as well, and that's the 00:05:22.000 --> 00:05:24.230 align:start position:0% to the story as well, and that's the fact<00:05:22.160> that<00:05:22.479> Apple<00:05:22.880> just<00:05:23.120> introduced<00:05:23.680> some<00:05:23.919> new 00:05:24.230 --> 00:05:24.240 align:start position:0% fact that Apple just introduced some new 00:05:24.240 --> 00:05:26.469 align:start position:0% fact that Apple just introduced some new chips.<00:05:24.800> This<00:05:24.960> week,<00:05:25.199> they<00:05:25.440> announced<00:05:25.759> the<00:05:26.000> M6 00:05:26.469 --> 00:05:26.479 align:start position:0% chips. This week, they announced the M6 00:05:26.479 --> 00:05:29.189 align:start position:0% chips. This week, they announced the M6 and<00:05:26.720> the<00:05:26.880> M5<00:05:27.520> Ultra,<00:05:28.000> and<00:05:28.240> these<00:05:28.479> are<00:05:28.720> designed 00:05:29.189 --> 00:05:29.199 align:start position:0% and the M5 Ultra, and these are designed 00:05:29.199 --> 00:05:32.070 align:start position:0% and the M5 Ultra, and these are designed for<00:05:29.520> AI<00:05:29.919> compute.<00:05:30.400> These<00:05:30.639> are<00:05:30.800> designed<00:05:31.360> to<00:05:31.840> be 00:05:32.070 --> 00:05:32.080 align:start position:0% for AI compute. These are designed to be 00:05:32.080 --> 00:05:34.710 align:start position:0% for AI compute. These are designed to be devices<00:05:32.880> that<00:05:33.199> live<00:05:33.360> on<00:05:33.600> your<00:05:33.840> desktop<00:05:34.479> that 00:05:34.710 --> 00:05:34.720 align:start position:0% devices that live on your desktop that 00:05:34.720 --> 00:05:37.270 align:start position:0% devices that live on your desktop that can<00:05:34.880> run<00:05:35.120> your<00:05:35.440> compute<00:05:35.919> completely<00:05:36.720> locally. 00:05:37.270 --> 00:05:37.280 align:start position:0% can run your compute completely locally. 00:05:37.280 --> 00:05:40.230 align:start position:0% can run your compute completely locally. And<00:05:37.440> this<00:05:37.600> M5<00:05:38.160> Ultra<00:05:38.560> chip<00:05:38.880> is<00:05:39.280> insane.<00:05:39.919> I'm 00:05:40.230 --> 00:05:40.240 align:start position:0% And this M5 Ultra chip is insane. I'm 00:05:40.240 --> 00:05:42.469 align:start position:0% And this M5 Ultra chip is insane. I'm currently<00:05:40.560> running<00:05:40.800> an<00:05:41.039> M3<00:05:41.600> Ultra<00:05:42.080> and<00:05:42.320> this 00:05:42.469 --> 00:05:42.479 align:start position:0% currently running an M3 Ultra and this 00:05:42.479 --> 00:05:46.230 align:start position:0% currently running an M3 Ultra and this has<00:05:42.960> 4.5<00:05:43.919> times<00:05:44.240> the<00:05:44.560> peak<00:05:44.960> GPU<00:05:45.600> compute<00:05:46.000> for 00:05:46.230 --> 00:05:46.240 align:start position:0% has 4.5 times the peak GPU compute for 00:05:46.240 --> 00:05:49.270 align:start position:0% has 4.5 times the peak GPU compute for AI<00:05:46.800> and<00:05:47.120> my<00:05:47.360> computer<00:05:47.759> right<00:05:48.000> now<00:05:48.639> is<00:05:49.039> an 00:05:49.270 --> 00:05:49.280 align:start position:0% AI and my computer right now is an 00:05:49.280 --> 00:05:51.749 align:start position:0% AI and my computer right now is an insanely<00:05:49.840> good<00:05:50.160> AI<00:05:50.720> computer.<00:05:51.199> They're<00:05:51.440> also 00:05:51.749 --> 00:05:51.759 align:start position:0% insanely good AI computer. They're also 00:05:51.759 --> 00:05:53.510 align:start position:0% insanely good AI computer. They're also releasing<00:05:52.160> it<00:05:52.320> in<00:05:52.560> versions<00:05:52.960> all<00:05:53.120> the<00:05:53.280> way<00:05:53.360> up 00:05:53.510 --> 00:05:53.520 align:start position:0% releasing it in versions all the way up 00:05:53.520 --> 00:05:57.189 align:start position:0% releasing it in versions all the way up to<00:05:53.759> 512<00:05:54.800> GB<00:05:55.360> of<00:05:55.600> unified<00:05:56.160> memory,<00:05:56.560> which<00:05:56.800> means 00:05:57.189 --> 00:05:57.199 align:start position:0% to 512 GB of unified memory, which means 00:05:57.199 --> 00:05:59.670 align:start position:0% to 512 GB of unified memory, which means pretty<00:05:57.440> much<00:05:57.600> most<00:05:57.759> of<00:05:57.919> that<00:05:58.160> 512<00:05:58.800> GB<00:05:59.360> can<00:05:59.520> be 00:05:59.670 --> 00:05:59.680 align:start position:0% pretty much most of that 512 GB can be 00:05:59.680 --> 00:06:02.390 align:start position:0% pretty much most of that 512 GB can be used<00:05:59.919> as<00:06:00.240> essentially<00:06:00.720> VRAM<00:06:01.360> for<00:06:01.600> running<00:06:01.919> AI 00:06:02.390 --> 00:06:02.400 align:start position:0% used as essentially VRAM for running AI 00:06:02.400 --> 00:06:03.990 align:start position:0% used as essentially VRAM for running AI models.<00:06:02.960> Now,<00:06:03.199> they're<00:06:03.440> not<00:06:03.600> going<00:06:03.680> to<00:06:03.840> be 00:06:03.990 --> 00:06:04.000 align:start position:0% models. Now, they're not going to be 00:06:04.000 --> 00:06:07.110 align:start position:0% models. Now, they're not going to be cheap.<00:06:04.479> an<00:06:04.720> M5<00:06:05.280> Ultra<00:06:05.759> with<00:06:05.919> only<00:06:06.080> a<00:06:06.319> 1<00:06:06.560> TBTE 00:06:07.110 --> 00:06:07.120 align:start position:0% cheap. an M5 Ultra with only a 1 TBTE 00:06:07.120 --> 00:06:09.029 align:start position:0% cheap. an M5 Ultra with only a 1 TBTE hard<00:06:07.360> drive<00:06:07.840> is<00:06:08.080> still<00:06:08.319> going<00:06:08.400> to<00:06:08.560> cost<00:06:08.800> you 00:06:09.029 --> 00:06:09.039 align:start position:0% hard drive is still going to cost you 00:06:09.039 --> 00:06:11.909 align:start position:0% hard drive is still going to cost you almost<00:06:09.600> 11<00:06:10.000> grand.<00:06:10.479> And<00:06:10.560> that's<00:06:10.720> for<00:06:10.880> the<00:06:11.039> 256 00:06:11.909 --> 00:06:11.919 align:start position:0% almost 11 grand. And that's for the 256 00:06:11.919 --> 00:06:13.749 align:start position:0% almost 11 grand. And that's for the 256 GB<00:06:12.479> version.<00:06:12.880> They<00:06:13.120> haven't<00:06:13.360> released<00:06:13.600> the 00:06:13.749 --> 00:06:13.759 align:start position:0% GB version. They haven't released the 00:06:13.759 --> 00:06:16.469 align:start position:0% GB version. They haven't released the price<00:06:13.919> of<00:06:14.080> the<00:06:14.319> 512<00:06:15.039> GB<00:06:15.600> version<00:06:15.840> yet.<00:06:16.240> But<00:06:16.319> the 00:06:16.469 --> 00:06:16.479 align:start position:0% price of the 512 GB version yet. But the 00:06:16.479 --> 00:06:18.550 align:start position:0% price of the 512 GB version yet. But the bigger<00:06:16.800> point<00:06:17.120> being<00:06:17.440> here<00:06:17.919> is<00:06:18.160> that<00:06:18.319> we're 00:06:18.550 --> 00:06:18.560 align:start position:0% bigger point being here is that we're 00:06:18.560 --> 00:06:20.790 align:start position:0% bigger point being here is that we're starting<00:06:18.800> to<00:06:18.960> get<00:06:19.280> more<00:06:19.520> and<00:06:19.840> more<00:06:20.240> devices 00:06:20.790 --> 00:06:20.800 align:start position:0% starting to get more and more devices 00:06:20.800 --> 00:06:23.830 align:start position:0% starting to get more and more devices that<00:06:21.039> are<00:06:21.360> very<00:06:21.759> capable<00:06:22.479> of<00:06:22.800> running<00:06:23.440> really 00:06:23.830 --> 00:06:23.840 align:start position:0% that are very capable of running really 00:06:23.840 --> 00:06:25.350 align:start position:0% that are very capable of running really good<00:06:24.080> models<00:06:24.479> at<00:06:24.720> home.<00:06:24.960> Like<00:06:25.120> you're<00:06:25.280> going 00:06:25.350 --> 00:06:25.360 align:start position:0% good models at home. Like you're going 00:06:25.360 --> 00:06:26.790 align:start position:0% good models at home. Like you're going to<00:06:25.440> be<00:06:25.600> able<00:06:25.759> to<00:06:25.919> run<00:06:26.080> these<00:06:26.319> really<00:06:26.560> good 00:06:26.790 --> 00:06:26.800 align:start position:0% to be able to run these really good 00:06:26.800 --> 00:06:29.110 align:start position:0% to be able to run these really good models<00:06:27.120> coming<00:06:27.280> out<00:06:27.440> of<00:06:27.600> ZAI,<00:06:28.240> like<00:06:28.400> the<00:06:28.560> GLM 00:06:29.110 --> 00:06:29.120 align:start position:0% models coming out of ZAI, like the GLM 00:06:29.120 --> 00:06:30.070 align:start position:0% models coming out of ZAI, like the GLM models.<00:06:29.440> You're<00:06:29.600> going<00:06:29.600> to<00:06:29.759> be<00:06:29.759> able<00:06:29.840> to<00:06:29.919> run 00:06:30.070 --> 00:06:30.080 align:start position:0% models. You're going to be able to run 00:06:30.080 --> 00:06:31.430 align:start position:0% models. You're going to be able to run some<00:06:30.240> of<00:06:30.319> the<00:06:30.400> DeepSeek<00:06:30.960> models.<00:06:31.199> you're 00:06:31.430 --> 00:06:31.440 align:start position:0% some of the DeepSeek models. you're 00:06:31.440 --> 00:06:32.550 align:start position:0% some of the DeepSeek models. you're going to<00:06:31.520> be<00:06:31.600> able<00:06:31.680> to<00:06:31.840> run<00:06:32.000> some<00:06:32.160> of<00:06:32.240> these 00:06:32.550 --> 00:06:32.560 align:start position:0% going to be able to run some of these 00:06:32.560 --> 00:06:34.710 align:start position:0% going to be able to run some of these bigger<00:06:32.960> Quinn<00:06:33.360> models<00:06:33.600> on<00:06:33.840> this<00:06:34.000> thing.<00:06:34.400> And<00:06:34.560> I 00:06:34.710 --> 00:06:34.720 align:start position:0% bigger Quinn models on this thing. And I 00:06:34.720 --> 00:06:36.710 align:start position:0% bigger Quinn models on this thing. And I mean,<00:06:34.880> it's<00:06:35.120> only<00:06:35.360> a<00:06:35.520> matter<00:06:35.759> of<00:06:36.000> time<00:06:36.400> before 00:06:36.710 --> 00:06:36.720 align:start position:0% mean, it's only a matter of time before 00:06:36.720 --> 00:06:38.950 align:start position:0% mean, it's only a matter of time before we're<00:06:36.880> going<00:06:36.960> to<00:06:37.039> get<00:06:37.120> like<00:06:37.360> Fable<00:06:37.840> level<00:06:38.240> GPT 00:06:38.950 --> 00:06:38.960 align:start position:0% we're going to get like Fable level GPT 00:06:38.960 --> 00:06:42.550 align:start position:0% we're going to get like Fable level GPT 5.6<00:06:40.000> soul<00:06:40.479> level<00:06:40.880> models<00:06:41.360> that<00:06:41.600> will<00:06:41.840> run<00:06:42.080> on<00:06:42.319> a 00:06:42.550 --> 00:06:42.560 align:start position:0% 5.6 soul level models that will run on a 00:06:42.560 --> 00:06:44.070 align:start position:0% 5.6 soul level models that will run on a computer<00:06:42.880> like<00:06:43.120> this.<00:06:43.600> But<00:06:43.680> I've<00:06:43.919> been 00:06:44.070 --> 00:06:44.080 align:start position:0% computer like this. But I've been 00:06:44.080 --> 00:06:45.749 align:start position:0% computer like this. But I've been finding<00:06:44.319> this<00:06:44.639> whole<00:06:44.960> story<00:06:45.440> just 00:06:45.749 --> 00:06:45.759 align:start position:0% finding this whole story just 00:06:45.759 --> 00:06:47.430 align:start position:0% finding this whole story just fascinating<00:06:46.400> watching<00:06:46.639> the<00:06:46.800> open<00:06:47.120> source 00:06:47.430 --> 00:06:47.440 align:start position:0% fascinating watching the open source 00:06:47.440 --> 00:06:49.029 align:start position:0% fascinating watching the open source versus<00:06:47.680> closed<00:06:48.000> source<00:06:48.240> battle.<00:06:48.800> If<00:06:48.960> you 00:06:49.029 --> 00:06:49.039 align:start position:0% versus closed source battle. If you 00:06:49.039 --> 00:06:51.110 align:start position:0% versus closed source battle. If you would<00:06:49.199> have<00:06:49.280> asked<00:06:49.520> me<00:06:49.680> 3<00:06:49.919> or<00:06:50.080> 4<00:06:50.240> years<00:06:50.400> ago,<00:06:50.880> I 00:06:51.110 --> 00:06:51.120 align:start position:0% would have asked me 3 or 4 years ago, I 00:06:51.120 --> 00:06:52.710 align:start position:0% would have asked me 3 or 4 years ago, I would<00:06:51.199> have<00:06:51.360> told<00:06:51.520> you<00:06:51.919> I<00:06:52.240> don't<00:06:52.400> see 00:06:52.710 --> 00:06:52.720 align:start position:0% would have told you I don't see 00:06:52.720 --> 00:06:54.870 align:start position:0% would have told you I don't see openweight<00:06:53.360> models<00:06:53.840> catching<00:06:54.319> up<00:06:54.479> to<00:06:54.639> the 00:06:54.870 --> 00:06:54.880 align:start position:0% openweight models catching up to the 00:06:54.880 --> 00:06:57.350 align:start position:0% openweight models catching up to the closed<00:06:55.280> weight<00:06:55.600> anytime<00:06:56.080> soon.<00:06:56.800> And<00:06:56.960> here<00:06:57.120> we 00:06:57.350 --> 00:06:57.360 align:start position:0% closed weight anytime soon. And here we 00:06:57.360 --> 00:06:59.510 align:start position:0% closed weight anytime soon. And here we are<00:06:57.520> a<00:06:57.759> few<00:06:57.840> years<00:06:58.080> later<00:06:58.479> and<00:06:58.800> like<00:06:59.199> we're 00:06:59.510 --> 00:06:59.520 align:start position:0% are a few years later and like we're 00:06:59.520 --> 00:07:01.270 align:start position:0% are a few years later and like we're this<00:06:59.759> close.<00:07:00.240> Speaking<00:07:00.560> of<00:07:00.720> openweight 00:07:01.270 --> 00:07:01.280 align:start position:0% this close. Speaking of openweight 00:07:01.280 --> 00:07:03.589 align:start position:0% this close. Speaking of openweight models,<00:07:01.840> we<00:07:02.080> got<00:07:02.319> two<00:07:02.639> new<00:07:02.880> models<00:07:03.280> this<00:07:03.520> week 00:07:03.589 --> 00:07:03.599 align:start position:0% models, we got two new models this week 00:07:03.599 --> 00:07:05.029 align:start position:0% models, we got two new models this week that<00:07:03.840> I<00:07:04.000> want<00:07:04.080> to<00:07:04.160> talk<00:07:04.319> about<00:07:04.479> real<00:07:04.720> quick. 00:07:05.029 --> 00:07:05.039 align:start position:0% that I want to talk about real quick. 00:07:05.039 --> 00:07:08.230 align:start position:0% that I want to talk about real quick. First,<00:07:05.280> we<00:07:05.440> got<00:07:05.680> GLM<00:07:06.400> 5.3<00:07:07.280> Flash.<00:07:07.919> And<00:07:08.080> this 00:07:08.230 --> 00:07:08.240 align:start position:0% First, we got GLM 5.3 Flash. And this 00:07:08.240 --> 00:07:10.070 align:start position:0% First, we got GLM 5.3 Flash. And this model<00:07:08.560> kind<00:07:08.720> of<00:07:08.800> flew<00:07:09.039> under<00:07:09.280> the<00:07:09.440> radar<00:07:09.759> and 00:07:10.070 --> 00:07:10.080 align:start position:0% model kind of flew under the radar and 00:07:10.080 --> 00:07:11.909 align:start position:0% model kind of flew under the radar and launched<00:07:10.400> in<00:07:10.639> stealth<00:07:11.039> like<00:07:11.280> a<00:07:11.520> week<00:07:11.599> or<00:07:11.759> two 00:07:11.909 --> 00:07:11.919 align:start position:0% launched in stealth like a week or two 00:07:11.919 --> 00:07:14.550 align:start position:0% launched in stealth like a week or two ago<00:07:12.319> under<00:07:12.639> the<00:07:12.800> name<00:07:13.199> Ox<00:07:13.759> Alpha.<00:07:14.160> And<00:07:14.319> when<00:07:14.479> we 00:07:14.550 --> 00:07:14.560 align:start position:0% ago under the name Ox Alpha. And when we 00:07:14.560 --> 00:07:16.230 align:start position:0% ago under the name Ox Alpha. And when we look<00:07:14.639> at<00:07:14.720> the<00:07:14.880> benchmarks<00:07:15.440> here,<00:07:15.680> again,<00:07:16.000> Deep 00:07:16.230 --> 00:07:16.240 align:start position:0% look at the benchmarks here, again, Deep 00:07:16.240 --> 00:07:18.150 align:start position:0% look at the benchmarks here, again, Deep Suite<00:07:16.560> is<00:07:16.720> kind<00:07:16.880> of<00:07:16.960> the<00:07:17.120> one<00:07:17.280> that<00:07:17.520> I<00:07:17.759> pay<00:07:17.919> the 00:07:18.150 --> 00:07:18.160 align:start position:0% Suite is kind of the one that I pay the 00:07:18.160 --> 00:07:19.749 align:start position:0% Suite is kind of the one that I pay the most<00:07:18.319> attention<00:07:18.720> to<00:07:19.039> because<00:07:19.280> I<00:07:19.520> think<00:07:19.599> it's 00:07:19.749 --> 00:07:19.759 align:start position:0% most attention to because I think it's 00:07:19.759 --> 00:07:22.070 align:start position:0% most attention to because I think it's the<00:07:20.000> most<00:07:20.160> accurate<00:07:20.639> to<00:07:21.199> like<00:07:21.440> actually<00:07:21.759> what 00:07:22.070 --> 00:07:22.080 align:start position:0% the most accurate to like actually what 00:07:22.080 --> 00:07:24.150 align:start position:0% the most accurate to like actually what we'll<00:07:22.319> feel<00:07:22.639> when<00:07:22.880> we're<00:07:23.120> coding<00:07:23.680> with<00:07:23.919> these 00:07:24.150 --> 00:07:24.160 align:start position:0% we'll feel when we're coding with these 00:07:24.160 --> 00:07:26.950 align:start position:0% we'll feel when we're coding with these models.<00:07:24.560> And<00:07:24.720> this<00:07:24.880> one<00:07:25.039> scored<00:07:25.280> a<00:07:25.520> 63.4, 00:07:26.950 --> 00:07:26.960 align:start position:0% models. And this one scored a 63.4, 00:07:26.960 --> 00:07:30.230 align:start position:0% models. And this one scored a 63.4, which<00:07:27.360> outperforms<00:07:28.400> Opus<00:07:28.960> 4.8.<00:07:29.520> and<00:07:29.840> falls 00:07:30.230 --> 00:07:30.240 align:start position:0% which outperforms Opus 4.8. and falls 00:07:30.240 --> 00:07:32.870 align:start position:0% which outperforms Opus 4.8. and falls just<00:07:30.560> shy<00:07:30.960> of<00:07:31.280> Google's<00:07:31.840> like<00:07:32.160> most<00:07:32.479> recent 00:07:32.870 --> 00:07:32.880 align:start position:0% just shy of Google's like most recent 00:07:32.880 --> 00:07:35.510 align:start position:0% just shy of Google's like most recent model<00:07:33.280> Gemini<00:07:33.759> 3.7<00:07:34.400> Flash.<00:07:34.880> I<00:07:35.039> also<00:07:35.280> think 00:07:35.510 --> 00:07:35.520 align:start position:0% model Gemini 3.7 Flash. I also think 00:07:35.520 --> 00:07:37.589 align:start position:0% model Gemini 3.7 Flash. I also think this<00:07:35.759> chart<00:07:36.080> right<00:07:36.319> here<00:07:36.560> is<00:07:36.880> very<00:07:37.199> very 00:07:37.589 --> 00:07:37.599 align:start position:0% this chart right here is very very 00:07:37.599 --> 00:07:39.670 align:start position:0% this chart right here is very very telling.<00:07:38.160> So<00:07:38.319> on<00:07:38.479> the<00:07:38.639> left<00:07:38.880> side<00:07:39.360> you've<00:07:39.599> got 00:07:39.670 --> 00:07:39.680 align:start position:0% telling. So on the left side you've got 00:07:39.680 --> 00:07:41.909 align:start position:0% telling. So on the left side you've got the<00:07:39.840> artificial<00:07:40.400> analysis<00:07:41.199> intelligence 00:07:41.909 --> 00:07:41.919 align:start position:0% the artificial analysis intelligence 00:07:41.919 --> 00:07:44.390 align:start position:0% the artificial analysis intelligence index.<00:07:42.479> This<00:07:42.639> is<00:07:42.800> sort<00:07:42.960> of<00:07:43.039> a<00:07:43.280> combined<00:07:43.919> score 00:07:44.390 --> 00:07:44.400 align:start position:0% index. This is sort of a combined score 00:07:44.400 --> 00:07:45.510 align:start position:0% index. This is sort of a combined score across<00:07:44.720> a<00:07:44.960> whole<00:07:45.039> bunch<00:07:45.199> of<00:07:45.360> different 00:07:45.510 --> 00:07:45.520 align:start position:0% across a whole bunch of different 00:07:45.520 --> 00:07:47.909 align:start position:0% across a whole bunch of different benchmarks<00:07:46.240> to<00:07:46.479> kind<00:07:46.639> of<00:07:47.120> pick<00:07:47.360> the 00:07:47.909 --> 00:07:47.919 align:start position:0% benchmarks to kind of pick the 00:07:47.919 --> 00:07:50.230 align:start position:0% benchmarks to kind of pick the objectively<00:07:48.960> smartest<00:07:49.440> model.<00:07:49.919> On<00:07:50.080> the 00:07:50.230 --> 00:07:50.240 align:start position:0% objectively smartest model. On the 00:07:50.240 --> 00:07:53.029 align:start position:0% objectively smartest model. On the bottom<00:07:50.880> you've<00:07:51.120> got<00:07:51.520> your<00:07:52.000> compute<00:07:52.479> cost. 00:07:53.029 --> 00:07:53.039 align:start position:0% bottom you've got your compute cost. 00:07:53.039 --> 00:07:56.550 align:start position:0% bottom you've got your compute cost. This<00:07:53.360> red<00:07:53.599> dot<00:07:53.919> here<00:07:54.080> is<00:07:54.240> where<00:07:54.479> GLM<00:07:55.120> 5.3<00:07:56.000> Flash 00:07:56.550 --> 00:07:56.560 align:start position:0% This red dot here is where GLM 5.3 Flash 00:07:56.560 --> 00:07:59.110 align:start position:0% This red dot here is where GLM 5.3 Flash sits.<00:07:57.120> So,<00:07:57.360> as<00:07:57.520> far<00:07:57.680> as<00:07:57.840> intelligence<00:07:58.479> goes, 00:07:59.110 --> 00:07:59.120 align:start position:0% sits. So, as far as intelligence goes, 00:07:59.120 --> 00:08:02.070 align:start position:0% sits. So, as far as intelligence goes, it's<00:07:59.360> right<00:07:59.599> around<00:08:00.000> Quinn<00:08:00.479> 3.8<00:08:01.199> max<00:08:01.520> level, 00:08:02.070 --> 00:08:02.080 align:start position:0% it's right around Quinn 3.8 max level, 00:08:02.080 --> 00:08:05.350 align:start position:0% it's right around Quinn 3.8 max level, but<00:08:02.639> way<00:08:03.440> cheaper<00:08:03.840> to<00:08:04.080> run.<00:08:04.479> And<00:08:04.720> notice<00:08:05.120> how 00:08:05.350 --> 00:08:05.360 align:start position:0% but way cheaper to run. And notice how 00:08:05.360 --> 00:08:07.029 align:start position:0% but way cheaper to run. And notice how some<00:08:05.520> of<00:08:05.599> these<00:08:05.840> other<00:08:06.080> models<00:08:06.479> aren't<00:08:06.800> even 00:08:07.029 --> 00:08:07.039 align:start position:0% some of these other models aren't even 00:08:07.039 --> 00:08:09.110 align:start position:0% some of these other models aren't even that<00:08:07.280> big<00:08:07.440> of<00:08:07.599> a<00:08:07.759> jump.<00:08:08.080> Claude<00:08:08.400> Opus<00:08:08.800> 5, 00:08:09.110 --> 00:08:09.120 align:start position:0% that big of a jump. Claude Opus 5, 00:08:09.120 --> 00:08:12.629 align:start position:0% that big of a jump. Claude Opus 5, Claude<00:08:09.520> Fable<00:08:09.919> 5,<00:08:10.240> GPT<00:08:10.879> 5.6<00:08:11.520> Soul.<00:08:12.000> Like,<00:08:12.319> not 00:08:12.629 --> 00:08:12.639 align:start position:0% Claude Fable 5, GPT 5.6 Soul. Like, not 00:08:12.639 --> 00:08:15.510 align:start position:0% Claude Fable 5, GPT 5.6 Soul. Like, not a<00:08:12.960> massive<00:08:13.680> intelligence<00:08:14.400> leap<00:08:14.879> over<00:08:15.280> what 00:08:15.510 --> 00:08:15.520 align:start position:0% a massive intelligence leap over what 00:08:15.520 --> 00:08:18.390 align:start position:0% a massive intelligence leap over what you're<00:08:15.759> getting<00:08:15.919> over<00:08:16.160> GLM<00:08:16.879> 5.3<00:08:17.680> Flash. 00:08:18.390 --> 00:08:18.400 align:start position:0% you're getting over GLM 5.3 Flash. 00:08:18.400 --> 00:08:20.710 align:start position:0% you're getting over GLM 5.3 Flash. Everything<00:08:18.800> that<00:08:19.120> falls<00:08:19.440> into<00:08:19.759> this<00:08:20.080> red<00:08:20.400> box 00:08:20.710 --> 00:08:20.720 align:start position:0% Everything that falls into this red box 00:08:20.720 --> 00:08:22.469 align:start position:0% Everything that falls into this red box that<00:08:20.960> you're<00:08:21.120> seeing<00:08:21.360> here<00:08:21.680> is<00:08:22.000> basically 00:08:22.469 --> 00:08:22.479 align:start position:0% that you're seeing here is basically 00:08:22.479 --> 00:08:25.270 align:start position:0% that you're seeing here is basically both<00:08:22.800> dumber<00:08:23.280> and<00:08:23.520> more<00:08:23.840> expensive<00:08:24.479> than<00:08:24.720> GLM 00:08:25.270 --> 00:08:25.280 align:start position:0% both dumber and more expensive than GLM 00:08:25.280 --> 00:08:27.909 align:start position:0% both dumber and more expensive than GLM 5.3<00:08:26.000> Flash.<00:08:26.400> And<00:08:26.639> that<00:08:26.879> includes<00:08:27.199> models<00:08:27.599> like 00:08:27.909 --> 00:08:27.919 align:start position:0% 5.3 Flash. And that includes models like 00:08:27.919 --> 00:08:30.869 align:start position:0% 5.3 Flash. And that includes models like Gemini<00:08:28.479> 3.7<00:08:29.280> Flash,<00:08:29.759> Claude<00:08:30.160> Sonnet<00:08:30.560> 5, 00:08:30.869 --> 00:08:30.879 align:start position:0% Gemini 3.7 Flash, Claude Sonnet 5, 00:08:30.879 --> 00:08:34.070 align:start position:0% Gemini 3.7 Flash, Claude Sonnet 5, Gemini<00:08:31.440> 3.1<00:08:32.159> Pro,<00:08:32.560> DeepSeek<00:08:33.120> V4.<00:08:33.839> These 00:08:34.070 --> 00:08:34.080 align:start position:0% Gemini 3.1 Pro, DeepSeek V4. These 00:08:34.080 --> 00:08:36.870 align:start position:0% Gemini 3.1 Pro, DeepSeek V4. These models<00:08:34.399> are<00:08:34.640> all<00:08:34.880> more<00:08:35.200> expensive<00:08:35.919> and<00:08:36.479> less 00:08:36.870 --> 00:08:36.880 align:start position:0% models are all more expensive and less 00:08:36.880 --> 00:08:39.190 align:start position:0% models are all more expensive and less intelligent,<00:08:37.680> which<00:08:37.919> is<00:08:38.080> why<00:08:38.399> this<00:08:38.880> model 00:08:39.190 --> 00:08:39.200 align:start position:0% intelligent, which is why this model 00:08:39.200 --> 00:08:41.670 align:start position:0% intelligent, which is why this model release<00:08:39.599> is<00:08:39.919> kind<00:08:40.159> of<00:08:40.240> a<00:08:40.479> big<00:08:40.719> deal.<00:08:41.200> It<00:08:41.440> just 00:08:41.670 --> 00:08:41.680 align:start position:0% release is kind of a big deal. It just 00:08:41.680 --> 00:08:44.310 align:start position:0% release is kind of a big deal. It just made<00:08:41.919> a<00:08:42.479> big<00:08:42.959> chunk<00:08:43.200> of<00:08:43.440> models<00:08:43.919> kind<00:08:44.159> of 00:08:44.310 --> 00:08:44.320 align:start position:0% made a big chunk of models kind of 00:08:44.320 --> 00:08:45.829 align:start position:0% made a big chunk of models kind of obsolete.<00:08:44.959> And<00:08:45.040> if<00:08:45.200> you're<00:08:45.360> curious<00:08:45.519> how<00:08:45.680> it 00:08:45.829 --> 00:08:45.839 align:start position:0% obsolete. And if you're curious how it 00:08:45.839 --> 00:08:47.750 align:start position:0% obsolete. And if you're curious how it performed<00:08:46.080> on<00:08:46.320> Beautybench,<00:08:47.200> here's<00:08:47.440> what<00:08:47.600> we 00:08:47.750 --> 00:08:47.760 align:start position:0% performed on Beautybench, here's what we 00:08:47.760 --> 00:08:49.990 align:start position:0% performed on Beautybench, here's what we got.<00:08:48.000> Now,<00:08:48.480> it<00:08:48.640> was<00:08:48.800> during<00:08:49.040> a<00:08:49.279> period<00:08:49.519> where<00:08:49.760> I 00:08:49.990 --> 00:08:50.000 align:start position:0% got. Now, it was during a period where I 00:08:50.000 --> 00:08:51.670 align:start position:0% got. Now, it was during a period where I was<00:08:50.080> able<00:08:50.240> to<00:08:50.399> use<00:08:50.560> the<00:08:50.720> model<00:08:51.040> for<00:08:51.200> free.<00:08:51.600> So, 00:08:51.670 --> 00:08:51.680 align:start position:0% was able to use the model for free. So, 00:08:51.680 --> 00:08:53.190 align:start position:0% was able to use the model for free. So, I'll<00:08:51.920> probably<00:08:52.160> run<00:08:52.320> it<00:08:52.480> again<00:08:52.640> to<00:08:52.880> get<00:08:52.959> an 00:08:53.190 --> 00:08:53.200 align:start position:0% I'll probably run it again to get an 00:08:53.200 --> 00:08:55.350 align:start position:0% I'll probably run it again to get an actual<00:08:53.519> accurate<00:08:54.000> cost.<00:08:54.399> And<00:08:54.560> it<00:08:54.720> also<00:08:54.959> ran<00:08:55.200> it 00:08:55.350 --> 00:08:55.360 align:start position:0% actual accurate cost. And it also ran it 00:08:55.360 --> 00:08:57.829 align:start position:0% actual accurate cost. And it also ran it when<00:08:55.600> it<00:08:55.760> was<00:08:55.920> called<00:08:56.160> ox<00:08:56.640> alpha.<00:08:57.200> So<00:08:57.360> the<00:08:57.600> name 00:08:57.829 --> 00:08:57.839 align:start position:0% when it was called ox alpha. So the name 00:08:57.839 --> 00:08:59.670 align:start position:0% when it was called ox alpha. So the name needs<00:08:58.000> to<00:08:58.160> be<00:08:58.240> updated<00:08:58.640> here.<00:08:58.959> But<00:08:59.040> it<00:08:59.200> took<00:08:59.440> 12 00:08:59.670 --> 00:08:59.680 align:start position:0% needs to be updated here. But it took 12 00:08:59.680 --> 00:09:02.710 align:start position:0% needs to be updated here. But it took 12 minutes<00:08:59.920> to<00:09:00.160> run,<00:09:00.480> used<00:09:00.880> 46,000<00:09:01.760> tokens,<00:09:02.480> and 00:09:02.710 --> 00:09:02.720 align:start position:0% minutes to run, used 46,000 tokens, and 00:09:02.720 --> 00:09:06.150 align:start position:0% minutes to run, used 46,000 tokens, and came<00:09:02.880> in<00:09:03.120> at<00:09:03.279> a<00:09:03.519> 5.4,<00:09:04.480> which<00:09:04.640> on<00:09:04.880> my<00:09:05.200> very,<00:09:05.440> very 00:09:06.150 --> 00:09:06.160 align:start position:0% came in at a 5.4, which on my very, very 00:09:06.160 --> 00:09:08.389 align:start position:0% came in at a 5.4, which on my very, very subjective<00:09:06.880> leaderboard<00:09:07.440> here<00:09:07.760> puts<00:09:08.080> it<00:09:08.240> at 00:09:08.389 --> 00:09:08.399 align:start position:0% subjective leaderboard here puts it at 00:09:08.399 --> 00:09:11.509 align:start position:0% subjective leaderboard here puts it at number<00:09:08.800> 25<00:09:09.440> overall.<00:09:10.000> But<00:09:10.160> we<00:09:10.320> got<00:09:10.800> another 00:09:11.509 --> 00:09:11.519 align:start position:0% number 25 overall. But we got another 00:09:11.519 --> 00:09:13.829 align:start position:0% number 25 overall. But we got another open-<00:09:11.839> source<00:09:12.160> model<00:09:12.480> this<00:09:12.720> week<00:09:12.959> as<00:09:13.200> well.<00:09:13.600> We 00:09:13.829 --> 00:09:13.839 align:start position:0% open- source model this week as well. We 00:09:13.839 --> 00:09:16.870 align:start position:0% open- source model this week as well. We got<00:09:14.240> Quinn<00:09:14.720> 3.8<00:09:15.519> Flash.<00:09:16.000> Now,<00:09:16.320> recently,<00:09:16.720> we 00:09:16.870 --> 00:09:16.880 align:start position:0% got Quinn 3.8 Flash. Now, recently, we 00:09:16.880 --> 00:09:20.070 align:start position:0% got Quinn 3.8 Flash. Now, recently, we got<00:09:17.120> Quinn<00:09:17.680> 3.827B,<00:09:18.160> 827B,<00:09:19.519> which<00:09:19.760> was<00:09:19.839> a 00:09:20.070 --> 00:09:20.080 align:start position:0% got Quinn 3.827B, 827B, which was a 00:09:20.080 --> 00:09:22.389 align:start position:0% got Quinn 3.827B, 827B, which was a really<00:09:20.320> good<00:09:20.480> model<00:09:20.720> for<00:09:21.040> running<00:09:21.360> locally<00:09:21.839> on 00:09:22.389 --> 00:09:22.399 align:start position:0% really good model for running locally on 00:09:22.399 --> 00:09:24.949 align:start position:0% really good model for running locally on high-end<00:09:23.040> consumer<00:09:23.600> GPU.<00:09:24.160> This<00:09:24.320> one<00:09:24.480> is<00:09:24.720> a 00:09:24.949 --> 00:09:24.959 align:start position:0% high-end consumer GPU. This one is a 00:09:24.959 --> 00:09:27.269 align:start position:0% high-end consumer GPU. This one is a little<00:09:25.040> bit<00:09:25.279> bigger.<00:09:25.680> It's<00:09:26.320> 125<00:09:26.800> billion 00:09:27.269 --> 00:09:27.279 align:start position:0% little bit bigger. It's 125 billion 00:09:27.279 --> 00:09:29.430 align:start position:0% little bit bigger. It's 125 billion parameters.<00:09:27.920> Like<00:09:28.080> that<00:09:28.320> new<00:09:28.480> M5<00:09:28.880> Ultra<00:09:29.200> would 00:09:29.430 --> 00:09:29.440 align:start position:0% parameters. Like that new M5 Ultra would 00:09:29.440 --> 00:09:31.590 align:start position:0% parameters. Like that new M5 Ultra would run<00:09:29.680> this<00:09:29.920> model<00:09:30.320> probably,<00:09:30.800> but<00:09:31.040> most<00:09:31.279> likely 00:09:31.590 --> 00:09:31.600 align:start position:0% run this model probably, but most likely 00:09:31.600 --> 00:09:32.949 align:start position:0% run this model probably, but most likely you're<00:09:31.839> going<00:09:31.920> to<00:09:32.000> want<00:09:32.160> to<00:09:32.320> run<00:09:32.399> it<00:09:32.560> in<00:09:32.720> a 00:09:32.949 --> 00:09:32.959 align:start position:0% you're going to want to run it in a 00:09:32.959 --> 00:09:34.870 align:start position:0% you're going to want to run it in a cloud.<00:09:33.279> It<00:09:33.519> does<00:09:33.680> decent<00:09:33.920> on<00:09:34.160> the<00:09:34.240> Deep<00:09:34.560> Suite 00:09:34.870 --> 00:09:34.880 align:start position:0% cloud. It does decent on the Deep Suite 00:09:34.880 --> 00:09:37.190 align:start position:0% cloud. It does decent on the Deep Suite benchmark,<00:09:35.440> and<00:09:35.600> on<00:09:35.839> artificial<00:09:36.399> analysis, 00:09:37.190 --> 00:09:37.200 align:start position:0% benchmark, and on artificial analysis, 00:09:37.200 --> 00:09:40.949 align:start position:0% benchmark, and on artificial analysis, it<00:09:37.440> falls<00:09:37.839> at<00:09:38.080> about<00:09:38.240> a<00:09:38.560> 56<00:09:39.519> compared<00:09:39.839> to<00:09:40.000> a<00:09:40.320> 57 00:09:40.949 --> 00:09:40.959 align:start position:0% it falls at about a 56 compared to a 57 00:09:40.959 --> 00:09:42.470 align:start position:0% it falls at about a 56 compared to a 57 from<00:09:41.120> the<00:09:41.279> model<00:09:41.519> we<00:09:41.760> were<00:09:41.839> just<00:09:42.000> looking<00:09:42.160> at, 00:09:42.470 --> 00:09:42.480 align:start position:0% from the model we were just looking at, 00:09:42.480 --> 00:09:46.230 align:start position:0% from the model we were just looking at, GLM<00:09:42.959> 5.3<00:09:43.519> Flash.<00:09:44.000> Quinn<00:09:44.399> 3.8<00:09:45.040> Flash<00:09:45.600> generated 00:09:46.230 --> 00:09:46.240 align:start position:0% GLM 5.3 Flash. Quinn 3.8 Flash generated 00:09:46.240 --> 00:09:48.310 align:start position:0% GLM 5.3 Flash. Quinn 3.8 Flash generated this<00:09:46.480> on<00:09:46.800> beauty<00:09:47.200> bench.<00:09:47.680> It<00:09:47.839> took<00:09:48.000> a<00:09:48.160> little 00:09:48.310 --> 00:09:48.320 align:start position:0% this on beauty bench. It took a little 00:09:48.320 --> 00:09:50.310 align:start position:0% this on beauty bench. It took a little over<00:09:48.480> a<00:09:48.640> penny<00:09:48.880> to<00:09:49.040> generate,<00:09:49.519> just<00:09:49.760> under<00:09:50.080> 5 00:09:50.310 --> 00:09:50.320 align:start position:0% over a penny to generate, just under 5 00:09:50.320 --> 00:09:53.269 align:start position:0% over a penny to generate, just under 5 minutes<00:09:50.640> and<00:09:50.959> used<00:09:51.519> 26,000<00:09:52.560> tokens. 00:09:53.269 --> 00:09:53.279 align:start position:0% minutes and used 26,000 tokens. 00:09:53.279 --> 00:09:55.350 align:start position:0% minutes and used 26,000 tokens. Interestingly,<00:09:54.000> this<00:09:54.240> one<00:09:54.480> got<00:09:54.800> ranked<00:09:55.120> at 00:09:55.350 --> 00:09:55.360 align:start position:0% Interestingly, this one got ranked at 00:09:55.360 --> 00:09:58.630 align:start position:0% Interestingly, this one got ranked at number<00:09:55.680> 19,<00:09:56.320> which<00:09:56.640> came<00:09:56.880> in<00:09:57.200> below<00:09:57.920> what<00:09:58.160> my 00:09:58.630 --> 00:09:58.640 align:start position:0% number 19, which came in below what my 00:09:58.640 --> 00:10:02.310 align:start position:0% number 19, which came in below what my AI<00:09:59.200> ranking<00:09:59.760> thought<00:10:00.080> of<00:10:00.320> Quinn<00:10:00.720> 3.827B. 00:10:02.310 --> 00:10:02.320 align:start position:0% AI ranking thought of Quinn 3.827B. 00:10:02.320 --> 00:10:03.590 align:start position:0% AI ranking thought of Quinn 3.827B. But<00:10:02.480> again,<00:10:02.640> the<00:10:02.880> rankings<00:10:03.200> here<00:10:03.360> don't 00:10:03.590 --> 00:10:03.600 align:start position:0% But again, the rankings here don't 00:10:03.600 --> 00:10:05.509 align:start position:0% But again, the rankings here don't really<00:10:03.839> matter.<00:10:04.240> You<00:10:04.399> can<00:10:04.560> just<00:10:04.800> use<00:10:05.040> your<00:10:05.279> own 00:10:05.509 --> 00:10:05.519 align:start position:0% really matter. You can just use your own 00:10:05.519 --> 00:10:07.350 align:start position:0% really matter. You can just use your own eyes<00:10:05.920> and<00:10:06.160> determine<00:10:06.560> which<00:10:06.800> one<00:10:06.959> you<00:10:07.120> think 00:10:07.350 --> 00:10:07.360 align:start position:0% eyes and determine which one you think 00:10:07.360 --> 00:10:08.870 align:start position:0% eyes and determine which one you think did<00:10:07.519> a<00:10:07.680> better<00:10:07.839> job.<00:10:08.080> Here's<00:10:08.399> another<00:10:08.640> cool 00:10:08.870 --> 00:10:08.880 align:start position:0% did a better job. Here's another cool 00:10:08.880 --> 00:10:10.389 align:start position:0% did a better job. Here's another cool update<00:10:09.200> that's<00:10:09.440> been<00:10:09.519> out<00:10:09.680> for<00:10:10.000> a<00:10:10.240> little 00:10:10.389 --> 00:10:10.399 align:start position:0% update that's been out for a little 00:10:10.399 --> 00:10:12.070 align:start position:0% update that's been out for a little while<00:10:10.560> now,<00:10:10.959> but<00:10:11.120> I<00:10:11.279> just<00:10:11.440> came<00:10:11.600> up<00:10:11.760> with<00:10:11.839> a 00:10:12.070 --> 00:10:12.080 align:start position:0% while now, but I just came up with a 00:10:12.080 --> 00:10:13.590 align:start position:0% while now, but I just came up with a cool<00:10:12.240> new<00:10:12.399> way<00:10:12.480> to<00:10:12.720> use<00:10:12.800> it.<00:10:13.040> I'm<00:10:13.279> going<00:10:13.360> to<00:10:13.440> use 00:10:13.590 --> 00:10:13.600 align:start position:0% cool new way to use it. I'm going to use 00:10:13.600 --> 00:10:16.230 align:start position:0% cool new way to use it. I'm going to use chatbt<00:10:14.399> sites<00:10:14.800> inside<00:10:15.120> of<00:10:15.200> the<00:10:15.360> Codex<00:10:15.839> app<00:10:16.000> to 00:10:16.230 --> 00:10:16.240 align:start position:0% chatbt sites inside of the Codex app to 00:10:16.240 --> 00:10:19.269 align:start position:0% chatbt sites inside of the Codex app to turn<00:10:16.560> my<00:10:16.880> spreadsheet<00:10:17.519> of<00:10:17.920> social<00:10:18.320> media<00:10:18.720> data 00:10:19.269 --> 00:10:19.279 align:start position:0% turn my spreadsheet of social media data 00:10:19.279 --> 00:10:21.590 align:start position:0% turn my spreadsheet of social media data into<00:10:19.519> a<00:10:19.680> live<00:10:20.079> performance<00:10:20.720> dashboard<00:10:21.279> that 00:10:21.590 --> 00:10:21.600 align:start position:0% into a live performance dashboard that 00:10:21.600 --> 00:10:23.910 align:start position:0% into a live performance dashboard that my<00:10:21.839> whole<00:10:22.079> team<00:10:22.399> can<00:10:22.640> access<00:10:23.040> and<00:10:23.279> use.<00:10:23.680> So 00:10:23.910 --> 00:10:23.920 align:start position:0% my whole team can access and use. So 00:10:23.920 --> 00:10:25.509 align:start position:0% my whole team can access and use. So inside<00:10:24.160> the<00:10:24.320> Codex<00:10:24.800> app,<00:10:24.959> I'm<00:10:25.120> just<00:10:25.279> going<00:10:25.360> to 00:10:25.509 --> 00:10:25.519 align:start position:0% inside the Codex app, I'm just going to 00:10:25.519 --> 00:10:28.310 align:start position:0% inside the Codex app, I'm just going to type<00:10:26.000> at<00:10:26.320> sites<00:10:26.880> and<00:10:27.120> say<00:10:27.440> build<00:10:27.680> me<00:10:27.839> a<00:10:28.079> social 00:10:28.310 --> 00:10:28.320 align:start position:0% type at sites and say build me a social 00:10:28.320 --> 00:10:30.150 align:start position:0% type at sites and say build me a social media<00:10:28.640> performance<00:10:29.120> dashboard<00:10:29.519> that<00:10:29.839> tracks 00:10:30.150 --> 00:10:30.160 align:start position:0% media performance dashboard that tracks 00:10:30.160 --> 00:10:32.230 align:start position:0% media performance dashboard that tracks all<00:10:30.399> my<00:10:30.640> platforms<00:10:31.279> and<00:10:31.519> that<00:10:31.680> I<00:10:31.920> can<00:10:32.079> share 00:10:32.230 --> 00:10:32.240 align:start position:0% all my platforms and that I can share 00:10:32.240 --> 00:10:34.310 align:start position:0% all my platforms and that I can share with<00:10:32.480> my<00:10:32.720> team.<00:10:33.120> And<00:10:33.200> then<00:10:33.519> sites<00:10:33.920> will<00:10:34.160> create 00:10:34.310 --> 00:10:34.320 align:start position:0% with my team. And then sites will create 00:10:34.320 --> 00:10:37.269 align:start position:0% with my team. And then sites will create the<00:10:34.480> website<00:10:35.120> plus<00:10:35.519> handle<00:10:36.399> everything<00:10:36.800> else 00:10:37.269 --> 00:10:37.279 align:start position:0% the website plus handle everything else 00:10:37.279 --> 00:10:39.030 align:start position:0% the website plus handle everything else like<00:10:37.440> the<00:10:37.680> hosting<00:10:38.000> and<00:10:38.160> the<00:10:38.320> authentication 00:10:39.030 --> 00:10:39.040 align:start position:0% like the hosting and the authentication 00:10:39.040 --> 00:10:41.750 align:start position:0% like the hosting and the authentication and<00:10:39.519> even<00:10:39.839> a<00:10:40.160> built-in<00:10:40.720> database.<00:10:41.360> Now,<00:10:41.600> the 00:10:41.750 --> 00:10:41.760 align:start position:0% and even a built-in database. Now, the 00:10:41.760 --> 00:10:43.430 align:start position:0% and even a built-in database. Now, the underlying<00:10:42.160> data<00:10:42.480> is<00:10:42.720> coming<00:10:42.959> from<00:10:43.200> this 00:10:43.430 --> 00:10:43.440 align:start position:0% underlying data is coming from this 00:10:43.440 --> 00:10:45.190 align:start position:0% underlying data is coming from this spreadsheet<00:10:44.000> that<00:10:44.240> tracks<00:10:44.560> my<00:10:44.800> audience 00:10:45.190 --> 00:10:45.200 align:start position:0% spreadsheet that tracks my audience 00:10:45.200 --> 00:10:46.949 align:start position:0% spreadsheet that tracks my audience across<00:10:45.600> YouTube,<00:10:46.079> the<00:10:46.240> Future<00:10:46.560> Tools 00:10:46.949 --> 00:10:46.959 align:start position:0% across YouTube, the Future Tools 00:10:46.959 --> 00:10:49.269 align:start position:0% across YouTube, the Future Tools newsletter,<00:10:47.760> Instagram,<00:10:48.480> LinkedIn,<00:10:49.120> Tik 00:10:49.269 --> 00:10:49.279 align:start position:0% newsletter, Instagram, LinkedIn, Tik 00:10:49.279 --> 00:10:52.230 align:start position:0% newsletter, Instagram, LinkedIn, Tik Tok,<00:10:49.839> X,<00:10:50.320> Threads,<00:10:50.880> and<00:10:51.200> even<00:10:51.600> Facebook.<00:10:52.079> So 00:10:52.230 --> 00:10:52.240 align:start position:0% Tok, X, Threads, and even Facebook. So 00:10:52.240 --> 00:10:53.750 align:start position:0% Tok, X, Threads, and even Facebook. So now<00:10:52.399> my<00:10:52.640> team<00:10:52.800> can<00:10:53.040> quickly<00:10:53.360> see<00:10:53.519> our 00:10:53.750 --> 00:10:53.760 align:start position:0% now my team can quickly see our 00:10:53.760 --> 00:10:55.750 align:start position:0% now my team can quickly see our audience,<00:10:54.320> weekly<00:10:54.720> growth,<00:10:55.200> and<00:10:55.440> which 00:10:55.750 --> 00:10:55.760 align:start position:0% audience, weekly growth, and which 00:10:55.760 --> 00:10:57.990 align:start position:0% audience, weekly growth, and which platforms<00:10:56.320> are<00:10:56.560> moving<00:10:56.880> the<00:10:57.120> fastest.<00:10:57.839> And 00:10:57.990 --> 00:10:58.000 align:start position:0% platforms are moving the fastest. And 00:10:58.000 --> 00:10:59.750 align:start position:0% platforms are moving the fastest. And now<00:10:58.160> we<00:10:58.320> can<00:10:58.480> even<00:10:58.720> build<00:10:58.959> and<00:10:59.200> refine<00:10:59.519> the 00:10:59.750 --> 00:10:59.760 align:start position:0% now we can even build and refine the 00:10:59.760 --> 00:11:02.310 align:start position:0% now we can even build and refine the site<00:11:00.079> together<00:11:00.640> and<00:11:01.040> connect<00:11:01.360> it<00:11:01.519> to<00:11:01.680> a<00:11:01.920> custom 00:11:02.310 --> 00:11:02.320 align:start position:0% site together and connect it to a custom 00:11:02.320 --> 00:11:04.310 align:start position:0% site together and connect it to a custom domain<00:11:02.720> if<00:11:02.959> we<00:11:03.120> want.<00:11:03.279> With<00:11:03.519> site<00:11:03.839> analytics, 00:11:04.310 --> 00:11:04.320 align:start position:0% domain if we want. With site analytics, 00:11:04.320 --> 00:11:06.470 align:start position:0% domain if we want. With site analytics, I<00:11:04.560> can<00:11:04.720> see<00:11:04.880> basic<00:11:05.279> performance<00:11:05.760> metrics<00:11:06.240> like 00:11:06.470 --> 00:11:06.480 align:start position:0% I can see basic performance metrics like 00:11:06.480 --> 00:11:08.870 align:start position:0% I can see basic performance metrics like visitors<00:11:06.959> and<00:11:07.200> page<00:11:07.440> views.<00:11:08.000> And<00:11:08.399> the<00:11:08.640> really 00:11:08.870 --> 00:11:08.880 align:start position:0% visitors and page views. And the really 00:11:08.880 --> 00:11:11.350 align:start position:0% visitors and page views. And the really interesting<00:11:09.279> part<00:11:09.519> is<00:11:09.760> this<00:11:10.000> new<00:11:10.399> web<00:11:10.720> MCP 00:11:11.350 --> 00:11:11.360 align:start position:0% interesting part is this new web MCP 00:11:11.360 --> 00:11:12.870 align:start position:0% interesting part is this new web MCP support.<00:11:11.760> You<00:11:11.920> can<00:11:12.000> build<00:11:12.240> predetermined 00:11:12.870 --> 00:11:12.880 align:start position:0% support. You can build predetermined 00:11:12.880 --> 00:11:15.269 align:start position:0% support. You can build predetermined actions<00:11:13.279> into<00:11:13.519> the<00:11:13.760> site<00:11:14.000> that<00:11:14.320> compatible<00:11:14.880> AI 00:11:15.269 --> 00:11:15.279 align:start position:0% actions into the site that compatible AI 00:11:15.279 --> 00:11:17.590 align:start position:0% actions into the site that compatible AI agents<00:11:15.839> can<00:11:16.000> use<00:11:16.320> instead<00:11:16.720> of<00:11:16.880> the<00:11:17.120> agent 00:11:17.590 --> 00:11:17.600 align:start position:0% agents can use instead of the agent 00:11:17.600 --> 00:11:19.670 align:start position:0% agents can use instead of the agent blindly<00:11:18.240> clicking<00:11:18.640> around<00:11:18.800> the<00:11:19.040> page.<00:11:19.519> This 00:11:19.670 --> 00:11:19.680 align:start position:0% blindly clicking around the page. This 00:11:19.680 --> 00:11:22.150 align:start position:0% blindly clicking around the page. This is<00:11:19.760> a<00:11:20.000> really<00:11:20.399> easy<00:11:20.720> way<00:11:20.959> to<00:11:21.200> build<00:11:21.519> tiny 00:11:22.150 --> 00:11:22.160 align:start position:0% is a really easy way to build tiny 00:11:22.160 --> 00:11:24.710 align:start position:0% is a really easy way to build tiny pieces<00:11:22.560> of<00:11:22.880> custom<00:11:23.360> software<00:11:23.839> for<00:11:24.079> your<00:11:24.240> team 00:11:24.710 --> 00:11:24.720 align:start position:0% pieces of custom software for your team 00:11:24.720 --> 00:11:26.389 align:start position:0% pieces of custom software for your team without<00:11:25.279> dealing<00:11:25.600> with<00:11:25.760> all<00:11:26.000> of<00:11:26.079> the 00:11:26.389 --> 00:11:26.399 align:start position:0% without dealing with all of the 00:11:26.399 --> 00:11:28.550 align:start position:0% without dealing with all of the infrastructure<00:11:27.120> that<00:11:27.440> you<00:11:27.760> normally<00:11:28.160> need. 00:11:28.550 --> 00:11:28.560 align:start position:0% infrastructure that you normally need. 00:11:28.560 --> 00:11:30.069 align:start position:0% infrastructure that you normally need. So<00:11:28.720> if<00:11:28.880> you<00:11:28.959> want<00:11:29.040> to<00:11:29.200> try<00:11:29.360> sites<00:11:29.760> out<00:11:29.920> for 00:11:30.069 --> 00:11:30.079 align:start position:0% So if you want to try sites out for 00:11:30.079 --> 00:11:31.509 align:start position:0% So if you want to try sites out for yourself,<00:11:30.640> head<00:11:30.800> to<00:11:30.959> the<00:11:31.040> link<00:11:31.200> in<00:11:31.360> the 00:11:31.509 --> 00:11:31.519 align:start position:0% yourself, head to the link in the 00:11:31.519 --> 00:11:33.350 align:start position:0% yourself, head to the link in the description<00:11:31.920> box<00:11:32.160> to<00:11:32.399> download<00:11:32.640> the<00:11:32.800> Codex 00:11:33.350 --> 00:11:33.360 align:start position:0% description box to download the Codex 00:11:33.360 --> 00:11:35.509 align:start position:0% description box to download the Codex app.<00:11:33.839> And<00:11:34.000> thanks<00:11:34.320> so<00:11:34.480> much<00:11:34.560> to<00:11:34.720> OpenAI<00:11:35.279> for 00:11:35.509 --> 00:11:35.519 align:start position:0% app. And thanks so much to OpenAI for 00:11:35.519 --> 00:11:37.190 align:start position:0% app. And thanks so much to OpenAI for supporting<00:11:35.839> my<00:11:36.079> channel<00:11:36.399> and<00:11:36.640> sponsoring 00:11:37.190 --> 00:11:37.200 align:start position:0% supporting my channel and sponsoring 00:11:37.200 --> 00:11:39.190 align:start position:0% supporting my channel and sponsoring this<00:11:37.440> portion<00:11:37.920> of<00:11:38.160> today's<00:11:38.480> video.<00:11:38.880> We<00:11:39.040> also 00:11:39.190 --> 00:11:39.200 align:start position:0% this portion of today's video. We also 00:11:39.200 --> 00:11:40.710 align:start position:0% this portion of today's video. We also got<00:11:39.360> like<00:11:39.440> a<00:11:39.600> flurry<00:11:39.920> of<00:11:40.079> new<00:11:40.320> announcements 00:11:40.710 --> 00:11:40.720 align:start position:0% got like a flurry of new announcements 00:11:40.720 --> 00:11:42.310 align:start position:0% got like a flurry of new announcements out<00:11:40.959> of<00:11:41.120> Google<00:11:41.440> this<00:11:41.680> week.<00:11:41.920> They<00:11:42.079> released 00:11:42.310 --> 00:11:42.320 align:start position:0% out of Google this week. They released 00:11:42.320 --> 00:11:44.389 align:start position:0% out of Google this week. They released an<00:11:42.560> updated<00:11:42.959> version<00:11:43.200> of<00:11:43.360> their<00:11:43.680> video<00:11:44.000> model 00:11:44.389 --> 00:11:44.399 align:start position:0% an updated version of their video model 00:11:44.399 --> 00:11:47.350 align:start position:0% an updated version of their video model called<00:11:44.640> Gemini<00:11:45.120> Omni<00:11:45.680> 1.1<00:11:46.560> Flash.<00:11:47.120> I'm 00:11:47.350 --> 00:11:47.360 align:start position:0% called Gemini Omni 1.1 Flash. I'm 00:11:47.360 --> 00:11:49.509 align:start position:0% called Gemini Omni 1.1 Flash. I'm guessing<00:11:47.680> their<00:11:47.920> VO<00:11:48.320> model<00:11:48.640> is<00:11:48.959> pretty<00:11:49.279> much 00:11:49.509 --> 00:11:49.519 align:start position:0% guessing their VO model is pretty much 00:11:49.519 --> 00:11:51.670 align:start position:0% guessing their VO model is pretty much done<00:11:49.760> for<00:11:50.079> cuz<00:11:50.399> everything<00:11:50.720> seems<00:11:51.040> to<00:11:51.200> be<00:11:51.360> this 00:11:51.670 --> 00:11:51.680 align:start position:0% done for cuz everything seems to be this 00:11:51.680 --> 00:11:53.670 align:start position:0% done for cuz everything seems to be this new<00:11:52.000> Omni<00:11:52.480> model.<00:11:52.800> We<00:11:53.040> can<00:11:53.120> see<00:11:53.279> this<00:11:53.440> new 00:11:53.670 --> 00:11:53.680 align:start position:0% new Omni model. We can see this new 00:11:53.680 --> 00:11:56.069 align:start position:0% new Omni model. We can see this new model<00:11:53.839> is<00:11:54.079> the<00:11:54.399> same<00:11:54.640> price<00:11:55.200> as<00:11:55.519> the<00:11:55.760> previous 00:11:56.069 --> 00:11:56.079 align:start position:0% model is the same price as the previous 00:11:56.079 --> 00:11:58.949 align:start position:0% model is the same price as the previous model.<00:11:56.640> 10<00:11:56.880> cents<00:11:57.120> for<00:11:57.360> a<00:11:57.519> 720p<00:11:58.320> output.<00:11:58.800> We 00:11:58.949 --> 00:11:58.959 align:start position:0% model. 10 cents for a 720p output. We 00:11:58.959 --> 00:12:01.910 align:start position:0% model. 10 cents for a 720p output. We can<00:11:59.120> also<00:11:59.279> do<00:11:59.360> a<00:11:59.519> 360p<00:12:00.399> output,<00:12:00.880> 1080p,<00:12:01.519> and<00:12:01.680> a 00:12:01.910 --> 00:12:01.920 align:start position:0% can also do a 360p output, 1080p, and a 00:12:01.920 --> 00:12:04.630 align:start position:0% can also do a 360p output, 1080p, and a 4K<00:12:02.320> output.<00:12:02.800> The<00:12:03.040> 360p<00:12:03.839> is<00:12:04.079> nice<00:12:04.160> if<00:12:04.399> you<00:12:04.480> want 00:12:04.630 --> 00:12:04.640 align:start position:0% 4K output. The 360p is nice if you want 00:12:04.640 --> 00:12:06.710 align:start position:0% 4K output. The 360p is nice if you want like<00:12:04.880> a<00:12:05.200> quick<00:12:05.600> generation<00:12:06.160> just<00:12:06.320> to<00:12:06.480> like 00:12:06.710 --> 00:12:06.720 align:start position:0% like a quick generation just to like 00:12:06.720 --> 00:12:08.069 align:start position:0% like a quick generation just to like test<00:12:06.959> to<00:12:07.200> see<00:12:07.279> how<00:12:07.519> something<00:12:07.760> might<00:12:08.000> come 00:12:08.069 --> 00:12:08.079 align:start position:0% test to see how something might come 00:12:08.079 --> 00:12:09.350 align:start position:0% test to see how something might come out.<00:12:08.320> And<00:12:08.480> if<00:12:08.560> you<00:12:08.639> think<00:12:08.800> it<00:12:08.959> does<00:12:09.040> a<00:12:09.200> good 00:12:09.350 --> 00:12:09.360 align:start position:0% out. And if you think it does a good 00:12:09.360 --> 00:12:11.430 align:start position:0% out. And if you think it does a good job,<00:12:09.600> I<00:12:09.760> guess<00:12:09.920> you<00:12:10.079> can<00:12:10.160> always<00:12:10.480> do<00:12:10.880> a<00:12:11.200> new 00:12:11.430 --> 00:12:11.440 align:start position:0% job, I guess you can always do a new 00:12:11.440 --> 00:12:13.509 align:start position:0% job, I guess you can always do a new generation<00:12:11.920> at<00:12:12.160> a<00:12:12.320> higher<00:12:12.560> resolution.<00:12:13.279> The 00:12:13.509 --> 00:12:13.519 align:start position:0% generation at a higher resolution. The 00:12:13.519 --> 00:12:15.350 align:start position:0% generation at a higher resolution. The new<00:12:13.680> model<00:12:13.920> can<00:12:14.079> analyze<00:12:14.480> up<00:12:14.639> to<00:12:14.800> 10<00:12:15.040> seconds 00:12:15.350 --> 00:12:15.360 align:start position:0% new model can analyze up to 10 seconds 00:12:15.360 --> 00:12:18.230 align:start position:0% new model can analyze up to 10 seconds of<00:12:15.519> prior<00:12:16.000> context.<00:12:16.800> You<00:12:16.959> can<00:12:17.120> specify<00:12:18.000> start 00:12:18.230 --> 00:12:18.240 align:start position:0% of prior context. You can specify start 00:12:18.240 --> 00:12:20.230 align:start position:0% of prior context. You can specify start and<00:12:18.560> end<00:12:18.800> frames<00:12:19.200> so<00:12:19.360> that<00:12:19.519> you<00:12:19.680> can<00:12:19.839> have<00:12:20.000> them 00:12:20.230 --> 00:12:20.240 align:start position:0% and end frames so that you can have them 00:12:20.240 --> 00:12:22.230 align:start position:0% and end frames so that you can have them animate<00:12:20.800> between<00:12:21.360> or<00:12:21.600> do<00:12:21.760> like<00:12:22.000> cool 00:12:22.230 --> 00:12:22.240 align:start position:0% animate between or do like cool 00:12:22.240 --> 00:12:25.110 align:start position:0% animate between or do like cool transitions<00:12:22.800> and<00:12:23.040> things.<00:12:23.360> Do<00:12:23.600> drast 00:12:25.110 --> 00:12:25.120 align:start position:0% transitions and things. Do drast 00:12:25.120 --> 00:12:27.509 align:start position:0% transitions and things. Do drast upscale<00:12:25.600> to<00:12:25.839> 4K.<00:12:26.480> Add<00:12:26.800> video<00:12:27.040> reference. 00:12:27.509 --> 00:12:27.519 align:start position:0% upscale to 4K. Add video reference. 00:12:27.519 --> 00:12:28.790 align:start position:0% upscale to 4K. Add video reference. Seems<00:12:27.760> like<00:12:27.839> a<00:12:28.000> lot<00:12:28.079> of<00:12:28.079> the<00:12:28.240> same<00:12:28.399> stuff<00:12:28.560> we 00:12:28.790 --> 00:12:28.800 align:start position:0% Seems like a lot of the same stuff we 00:12:28.800 --> 00:12:30.470 align:start position:0% Seems like a lot of the same stuff we were<00:12:28.880> able<00:12:29.040> to<00:12:29.120> do<00:12:29.279> with<00:12:29.440> the<00:12:29.600> original<00:12:29.920> Omni. 00:12:30.470 --> 00:12:30.480 align:start position:0% were able to do with the original Omni. 00:12:30.480 --> 00:12:32.550 align:start position:0% were able to do with the original Omni. It's<00:12:30.639> just<00:12:30.880> we<00:12:31.120> have<00:12:31.360> better<00:12:31.920> quality 00:12:32.550 --> 00:12:32.560 align:start position:0% It's just we have better quality 00:12:32.560 --> 00:12:34.710 align:start position:0% It's just we have better quality versions<00:12:33.120> and<00:12:33.440> a<00:12:33.600> little<00:12:33.680> bit<00:12:33.839> more<00:12:34.079> context. 00:12:34.710 --> 00:12:34.720 align:start position:0% versions and a little bit more context. 00:12:34.720 --> 00:12:36.710 align:start position:0% versions and a little bit more context. Here's<00:12:34.959> some<00:12:35.200> examples<00:12:35.760> with<00:12:36.000> the<00:12:36.160> prompts<00:12:36.560> on 00:12:36.710 --> 00:12:36.720 align:start position:0% Here's some examples with the prompts on 00:12:36.720 --> 00:12:44.790 align:start position:0% Here's some examples with the prompts on the<00:12:36.880> screen.<00:12:37.843> [music] 00:12:44.790 --> 00:12:44.800 align:start position:0% 00:12:44.800 --> 00:12:52.470 align:start position:0% Start<00:12:45.120> and<00:12:45.279> end<00:12:45.600> frame. 00:12:52.470 --> 00:12:52.480 align:start position:0% 00:12:52.480 --> 00:12:55.110 align:start position:0% A<00:12:52.639> microscopic<00:12:53.440> view<00:12:53.600> of<00:12:53.839> iridescent<00:12:54.560> marine 00:12:55.110 --> 00:12:55.120 align:start position:0% A microscopic view of iridescent marine 00:12:55.120 --> 00:12:58.470 align:start position:0% A microscopic view of iridescent marine dios<00:12:56.240> displaying<00:12:56.639> integrate<00:12:57.200> glass<00:12:57.839> silica 00:12:58.470 --> 00:12:58.480 align:start position:0% dios displaying integrate glass silica 00:12:58.480 --> 00:13:00.069 align:start position:0% dios displaying integrate glass silica shells<00:12:58.880> with<00:12:59.040> breathtaking<00:12:59.680> natural 00:13:00.069 --> 00:13:00.079 align:start position:0% shells with breathtaking natural 00:13:00.079 --> 00:13:02.150 align:start position:0% shells with breathtaking natural symmetry 00:13:02.150 --> 00:13:02.160 align:start position:0% symmetry 00:13:02.160 --> 00:13:06.069 align:start position:0% symmetry etc.<00:13:03.279> Interestingly<00:13:04.000> over<00:13:04.240> on<00:13:04.720> arena.ai 00:13:06.069 --> 00:13:06.079 align:start position:0% etc. Interestingly over on arena.ai 00:13:06.079 --> 00:13:08.790 align:start position:0% etc. Interestingly over on arena.ai under<00:13:06.320> the<00:13:06.480> texttovideo<00:13:07.279> arena<00:13:07.760> Gemini<00:13:08.240> Omni 00:13:08.790 --> 00:13:08.800 align:start position:0% under the texttovideo arena Gemini Omni 00:13:08.800 --> 00:13:11.670 align:start position:0% under the texttovideo arena Gemini Omni 1.1<00:13:09.440> Flash<00:13:09.839> is<00:13:10.079> the<00:13:10.240> new<00:13:10.480> top<00:13:10.880> model<00:13:11.200> there.<00:13:11.519> If 00:13:11.670 --> 00:13:11.680 align:start position:0% 1.1 Flash is the new top model there. If 00:13:11.680 --> 00:13:13.350 align:start position:0% 1.1 Flash is the new top model there. If you<00:13:11.760> don't<00:13:11.920> know<00:13:12.000> what<00:13:12.240> Arena<00:13:12.720> is,<00:13:13.120> it's 00:13:13.350 --> 00:13:13.360 align:start position:0% you don't know what Arena is, it's 00:13:13.360 --> 00:13:15.590 align:start position:0% you don't know what Arena is, it's basically<00:13:13.760> like<00:13:13.920> a<00:13:14.160> blind<00:13:14.720> test.<00:13:15.279> You<00:13:15.440> give 00:13:15.590 --> 00:13:15.600 align:start position:0% basically like a blind test. You give 00:13:15.600 --> 00:13:18.310 align:start position:0% basically like a blind test. You give Arena<00:13:16.079> a<00:13:16.320> prompt.<00:13:16.800> It<00:13:16.959> gives<00:13:17.120> you<00:13:17.279> two<00:13:17.600> outputs 00:13:18.310 --> 00:13:18.320 align:start position:0% Arena a prompt. It gives you two outputs 00:13:18.320 --> 00:13:20.389 align:start position:0% Arena a prompt. It gives you two outputs from<00:13:18.560> two<00:13:18.880> different<00:13:19.120> video<00:13:19.519> models,<00:13:20.160> not 00:13:20.389 --> 00:13:20.399 align:start position:0% from two different video models, not 00:13:20.399 --> 00:13:22.389 align:start position:0% from two different video models, not telling<00:13:20.639> you<00:13:20.800> which<00:13:21.120> model<00:13:21.440> is<00:13:21.680> which.<00:13:22.000> It<00:13:22.240> can 00:13:22.389 --> 00:13:22.399 align:start position:0% telling you which model is which. It can 00:13:22.399 --> 00:13:24.310 align:start position:0% telling you which model is which. It can be<00:13:22.560> any<00:13:22.880> model<00:13:23.200> that's<00:13:23.360> in<00:13:23.519> their<00:13:23.680> database. 00:13:24.310 --> 00:13:24.320 align:start position:0% be any model that's in their database. 00:13:24.320 --> 00:13:25.910 align:start position:0% be any model that's in their database. You<00:13:24.560> pick<00:13:24.720> which<00:13:24.959> one<00:13:25.120> is<00:13:25.279> your<00:13:25.519> favorite 00:13:25.910 --> 00:13:25.920 align:start position:0% You pick which one is your favorite 00:13:25.920 --> 00:13:27.829 align:start position:0% You pick which one is your favorite between<00:13:26.240> the<00:13:26.480> two<00:13:26.720> and<00:13:26.959> then<00:13:27.120> after<00:13:27.440> enough 00:13:27.829 --> 00:13:27.839 align:start position:0% between the two and then after enough 00:13:27.839 --> 00:13:29.590 align:start position:0% between the two and then after enough people<00:13:28.079> have<00:13:28.320> done<00:13:28.480> their<00:13:28.720> voting,<00:13:29.440> that's 00:13:29.590 --> 00:13:29.600 align:start position:0% people have done their voting, that's 00:13:29.600 --> 00:13:31.030 align:start position:0% people have done their voting, that's how<00:13:29.760> you<00:13:29.920> get<00:13:30.000> the<00:13:30.240> ranking.<00:13:30.560> So,<00:13:30.720> it's<00:13:30.880> a 00:13:31.030 --> 00:13:31.040 align:start position:0% how you get the ranking. So, it's a 00:13:31.040 --> 00:13:34.150 align:start position:0% how you get the ranking. So, it's a blind<00:13:31.360> test<00:13:31.680> of<00:13:32.079> user<00:13:32.560> preference.<00:13:33.360> And<00:13:33.680> Omni 00:13:34.150 --> 00:13:34.160 align:start position:0% blind test of user preference. And Omni 00:13:34.160 --> 00:13:36.550 align:start position:0% blind test of user preference. And Omni 1.1<00:13:34.720> Flash<00:13:35.040> is<00:13:35.279> winning<00:13:35.519> in<00:13:35.760> text<00:13:35.920> to<00:13:36.160> video. 00:13:36.550 --> 00:13:36.560 align:start position:0% 1.1 Flash is winning in text to video. 00:13:36.560 --> 00:13:39.350 align:start position:0% 1.1 Flash is winning in text to video. And<00:13:36.720> in<00:13:37.040> image<00:13:37.360> to<00:13:37.600> video,<00:13:38.000> it<00:13:38.240> is<00:13:38.639> second<00:13:39.120> only 00:13:39.350 --> 00:13:39.360 align:start position:0% And in image to video, it is second only 00:13:39.360 --> 00:13:42.069 align:start position:0% And in image to video, it is second only behind<00:13:39.920> Miniax<00:13:40.639> and<00:13:40.880> not<00:13:41.040> by<00:13:41.279> a<00:13:41.440> wide<00:13:41.680> margin. 00:13:42.069 --> 00:13:42.079 align:start position:0% behind Miniax and not by a wide margin. 00:13:42.079 --> 00:13:44.150 align:start position:0% behind Miniax and not by a wide margin. But<00:13:42.160> you<00:13:42.320> can<00:13:42.399> also<00:13:42.639> see<00:13:43.120> not<00:13:43.279> a<00:13:43.519> ton<00:13:43.600> of<00:13:43.760> votes 00:13:44.150 --> 00:13:44.160 align:start position:0% But you can also see not a ton of votes 00:13:44.160 --> 00:13:45.750 align:start position:0% But you can also see not a ton of votes yet.<00:13:44.560> It's<00:13:44.800> still<00:13:44.959> early.<00:13:45.360> Now,<00:13:45.519> their 00:13:45.750 --> 00:13:45.760 align:start position:0% yet. It's still early. Now, their 00:13:45.760 --> 00:13:47.509 align:start position:0% yet. It's still early. Now, their announcement<00:13:46.160> here<00:13:46.399> says<00:13:46.639> you<00:13:46.880> can<00:13:46.959> build<00:13:47.279> in 00:13:47.509 --> 00:13:47.519 align:start position:0% announcement here says you can build in 00:13:47.519 --> 00:13:50.550 align:start position:0% announcement here says you can build in AI<00:13:48.079> Studio<00:13:48.720> using<00:13:49.040> your<00:13:49.200> API<00:13:49.680> key.<00:13:50.160> Or<00:13:50.399> if 00:13:50.550 --> 00:13:50.560 align:start position:0% AI Studio using your API key. Or if 00:13:50.560 --> 00:13:52.629 align:start position:0% AI Studio using your API key. Or if you're<00:13:50.800> a<00:13:51.200> AI<00:13:51.600> Plus<00:13:51.839> Pro<00:13:52.079> or<00:13:52.240> Ultra 00:13:52.629 --> 00:13:52.639 align:start position:0% you're a AI Plus Pro or Ultra 00:13:52.639 --> 00:13:54.230 align:start position:0% you're a AI Plus Pro or Ultra subscriber,<00:13:53.200> you<00:13:53.360> could<00:13:53.519> use<00:13:53.600> it<00:13:53.760> inside<00:13:54.079> of 00:13:54.230 --> 00:13:54.240 align:start position:0% subscriber, you could use it inside of 00:13:54.240 --> 00:13:56.389 align:start position:0% subscriber, you could use it inside of Google<00:13:54.639> Flow.<00:13:55.120> So,<00:13:55.360> first<00:13:55.519> I<00:13:55.680> went<00:13:55.760> to<00:13:55.920> AI 00:13:56.389 --> 00:13:56.399 align:start position:0% Google Flow. So, first I went to AI 00:13:56.399 --> 00:13:58.470 align:start position:0% Google Flow. So, first I went to AI Studio<00:13:56.880> and<00:13:57.120> have<00:13:57.279> tried<00:13:57.519> to<00:13:57.600> prompt<00:13:58.000> multiple 00:13:58.470 --> 00:13:58.480 align:start position:0% Studio and have tried to prompt multiple 00:13:58.480 --> 00:14:00.150 align:start position:0% Studio and have tried to prompt multiple times<00:13:58.720> and<00:13:58.880> I<00:13:59.120> keep<00:13:59.279> getting<00:13:59.519> an<00:13:59.760> internal 00:14:00.150 --> 00:14:00.160 align:start position:0% times and I keep getting an internal 00:14:00.160 --> 00:14:02.230 align:start position:0% times and I keep getting an internal server<00:14:00.639> error.<00:14:00.959> I<00:14:01.279> don't<00:14:01.440> know<00:14:01.600> if<00:14:01.760> I'm<00:14:02.000> doing 00:14:02.230 --> 00:14:02.240 align:start position:0% server error. I don't know if I'm doing 00:14:02.240 --> 00:14:04.150 align:start position:0% server error. I don't know if I'm doing something<00:14:02.480> wrong.<00:14:02.880> I<00:14:03.040> even<00:14:03.360> went<00:14:03.600> and 00:14:04.150 --> 00:14:04.160 align:start position:0% something wrong. I even went and 00:14:04.160 --> 00:14:07.030 align:start position:0% something wrong. I even went and pre-added<00:14:05.040> money<00:14:05.279> in.<00:14:05.680> So,<00:14:05.760> I<00:14:06.000> put<00:14:06.240> $25<00:14:06.880> in 00:14:07.030 --> 00:14:07.040 align:start position:0% pre-added money in. So, I put $25 in 00:14:07.040 --> 00:14:08.550 align:start position:0% pre-added money in. So, I put $25 in here<00:14:07.279> so<00:14:07.360> I<00:14:07.519> have<00:14:07.680> credits<00:14:08.000> and<00:14:08.240> I<00:14:08.399> still 00:14:08.550 --> 00:14:08.560 align:start position:0% here so I have credits and I still 00:14:08.560 --> 00:14:10.069 align:start position:0% here so I have credits and I still couldn't<00:14:08.800> get<00:14:08.880> it<00:14:09.040> to<00:14:09.199> work.<00:14:09.440> So,<00:14:09.519> I<00:14:09.680> took<00:14:09.920> my 00:14:10.069 --> 00:14:10.079 align:start position:0% couldn't get it to work. So, I took my 00:14:10.079 --> 00:14:13.269 align:start position:0% couldn't get it to work. So, I took my prompt<00:14:10.480> over<00:14:10.720> to<00:14:11.120> Flo<00:14:11.600> because<00:14:11.839> I<00:14:12.160> am<00:14:12.480> an<00:14:12.800> ultra 00:14:13.269 --> 00:14:13.279 align:start position:0% prompt over to Flo because I am an ultra 00:14:13.279 --> 00:14:15.350 align:start position:0% prompt over to Flo because I am an ultra subscriber.<00:14:14.079> And<00:14:14.480> this<00:14:14.720> was<00:14:14.800> the<00:14:14.959> prompt<00:14:15.199> I 00:14:15.350 --> 00:14:15.360 align:start position:0% subscriber. And this was the prompt I 00:14:15.360 --> 00:14:17.110 align:start position:0% subscriber. And this was the prompt I gave<00:14:15.519> it.<00:14:15.760> A<00:14:15.920> video<00:14:16.079> of<00:14:16.240> a<00:14:16.399> robot<00:14:16.720> wearing<00:14:16.959> a 00:14:17.110 --> 00:14:17.120 align:start position:0% gave it. A video of a robot wearing a 00:14:17.120 --> 00:14:18.710 align:start position:0% gave it. A video of a robot wearing a hat<00:14:17.279> that<00:14:17.440> says<00:14:17.600> future<00:14:18.000> tools<00:14:18.160> on<00:14:18.320> it.<00:14:18.480> Break 00:14:18.710 --> 00:14:18.720 align:start position:0% hat that says future tools on it. Break 00:14:18.720 --> 00:14:20.230 align:start position:0% hat that says future tools on it. Break dances<00:14:19.120> in<00:14:19.279> front<00:14:19.360> of<00:14:19.440> a<00:14:19.600> castle<00:14:19.839> where<00:14:20.000> a 00:14:20.230 --> 00:14:20.240 align:start position:0% dances in front of a castle where a 00:14:20.240 --> 00:14:22.634 align:start position:0% dances in front of a castle where a dragon<00:14:20.560> flies<00:14:21.040> overhead. 00:14:22.634 --> 00:14:22.644 align:start position:0% dragon flies overhead. 00:14:22.644 --> 00:14:31.670 align:start position:0% dragon flies overhead. [music] 00:14:31.670 --> 00:14:31.680 align:start position:0% 00:14:31.680 --> 00:14:34.790 align:start position:0% My<00:14:31.920> initial<00:14:32.399> thought<00:14:32.639> is<00:14:33.199> okay.<00:14:34.320> Again,<00:14:34.560> I've 00:14:34.790 --> 00:14:34.800 align:start position:0% My initial thought is okay. Again, I've 00:14:34.800 --> 00:14:36.470 align:start position:0% My initial thought is okay. Again, I've talked<00:14:34.959> about<00:14:35.120> this<00:14:35.279> a<00:14:35.440> bit<00:14:35.600> lately.<00:14:36.079> I'm<00:14:36.240> less 00:14:36.470 --> 00:14:36.480 align:start position:0% talked about this a bit lately. I'm less 00:14:36.480 --> 00:14:38.870 align:start position:0% talked about this a bit lately. I'm less and<00:14:36.720> less<00:14:36.959> impressed<00:14:37.360> by<00:14:37.760> video<00:14:38.160> models<00:14:38.480> these 00:14:38.870 --> 00:14:38.880 align:start position:0% and less impressed by video models these 00:14:38.880 --> 00:14:40.389 align:start position:0% and less impressed by video models these days.<00:14:39.199> And<00:14:39.279> this<00:14:39.440> one,<00:14:39.600> I<00:14:39.839> do<00:14:40.000> see<00:14:40.160> some 00:14:40.389 --> 00:14:40.399 align:start position:0% days. And this one, I do see some 00:14:40.399 --> 00:14:42.310 align:start position:0% days. And this one, I do see some wonkiness<00:14:41.040> in<00:14:41.279> it.<00:14:41.440> The<00:14:41.680> castle<00:14:42.000> in<00:14:42.160> the 00:14:42.310 --> 00:14:42.320 align:start position:0% wonkiness in it. The castle in the 00:14:42.320 --> 00:14:44.470 align:start position:0% wonkiness in it. The castle in the background<00:14:42.639> looks<00:14:42.959> fine,<00:14:43.279> but<00:14:43.519> my<00:14:43.760> robot,<00:14:44.240> for 00:14:44.470 --> 00:14:44.480 align:start position:0% background looks fine, but my robot, for 00:14:44.480 --> 00:14:46.150 align:start position:0% background looks fine, but my robot, for some<00:14:44.639> reason,<00:14:44.880> the<00:14:45.120> head<00:14:45.360> just<00:14:45.519> pops<00:14:45.839> off, 00:14:46.150 --> 00:14:46.160 align:start position:0% some reason, the head just pops off, 00:14:46.160 --> 00:14:48.629 align:start position:0% some reason, the head just pops off, falls<00:14:46.399> on<00:14:46.639> the<00:14:46.800> ground,<00:14:47.040> and<00:14:47.199> then<00:14:47.760> apparently 00:14:48.629 --> 00:14:48.639 align:start position:0% falls on the ground, and then apparently 00:14:48.639 --> 00:14:50.949 align:start position:0% falls on the ground, and then apparently it's<00:14:48.880> got<00:14:49.040> the<00:14:49.279> same<00:14:49.519> hat<00:14:49.839> on<00:14:50.160> both<00:14:50.399> sides<00:14:50.720> and 00:14:50.949 --> 00:14:50.959 align:start position:0% it's got the same hat on both sides and 00:14:50.959 --> 00:14:53.269 align:start position:0% it's got the same hat on both sides and the<00:14:51.120> same<00:14:51.279> face<00:14:51.600> on<00:14:51.839> both<00:14:52.000> sides.<00:14:52.560> Although, 00:14:53.269 --> 00:14:53.279 align:start position:0% the same face on both sides. Although, 00:14:53.279 --> 00:14:55.030 align:start position:0% the same face on both sides. Although, when<00:14:53.519> you<00:14:53.680> look<00:14:53.760> at<00:14:53.839> it<00:14:54.079> here,<00:14:54.320> it<00:14:54.560> clearly 00:14:55.030 --> 00:14:55.040 align:start position:0% when you look at it here, it clearly 00:14:55.040 --> 00:14:56.870 align:start position:0% when you look at it here, it clearly doesn't.<00:14:55.600> So,<00:14:55.839> that's<00:14:56.000> a<00:14:56.160> little<00:14:56.320> funky.<00:14:56.800> And 00:14:56.870 --> 00:14:56.880 align:start position:0% doesn't. So, that's a little funky. And 00:14:56.880 --> 00:14:58.230 align:start position:0% doesn't. So, that's a little funky. And then<00:14:57.040> there's<00:14:57.199> some<00:14:57.360> wonkiness<00:14:57.839> when<00:14:58.079> he 00:14:58.230 --> 00:14:58.240 align:start position:0% then there's some wonkiness when he 00:14:58.240 --> 00:15:01.280 align:start position:0% then there's some wonkiness when he starts<00:14:58.560> doing<00:14:58.800> his<00:14:59.040> like<00:14:59.440> ground<00:15:00.160> moves<00:15:00.560> here. 00:15:01.280 --> 00:15:01.290 align:start position:0% starts doing his like ground moves here. 00:15:01.290 --> 00:15:02.550 align:start position:0% starts doing his like ground moves here. [laughter]<00:15:01.519> Like,<00:15:01.760> yeah,<00:15:02.000> it's<00:15:02.240> just<00:15:02.399> a 00:15:02.550 --> 00:15:02.560 align:start position:0% [laughter] Like, yeah, it's just a 00:15:02.560 --> 00:15:04.470 align:start position:0% [laughter] Like, yeah, it's just a little<00:15:02.800> awkward.<00:15:03.360> The<00:15:03.600> consistency<00:15:04.079> of<00:15:04.320> the 00:15:04.470 --> 00:15:04.480 align:start position:0% little awkward. The consistency of the 00:15:04.480 --> 00:15:06.310 align:start position:0% little awkward. The consistency of the castle<00:15:04.880> and<00:15:05.120> the<00:15:05.279> dragon<00:15:05.680> are<00:15:05.920> really<00:15:06.079> good 00:15:06.310 --> 00:15:06.320 align:start position:0% castle and the dragon are really good 00:15:06.320 --> 00:15:07.910 align:start position:0% castle and the dragon are really good between<00:15:06.720> scenes,<00:15:07.120> though.<00:15:07.360> That's<00:15:07.600> one<00:15:07.760> thing 00:15:07.910 --> 00:15:07.920 align:start position:0% between scenes, though. That's one thing 00:15:07.920 --> 00:15:09.910 align:start position:0% between scenes, though. That's one thing that's<00:15:08.160> gotten<00:15:08.399> a<00:15:08.639> lot<00:15:08.800> better<00:15:09.120> over<00:15:09.440> time<00:15:09.600> is 00:15:09.910 --> 00:15:09.920 align:start position:0% that's gotten a lot better over time is 00:15:09.920 --> 00:15:11.750 align:start position:0% that's gotten a lot better over time is consistency.<00:15:10.560> When<00:15:10.720> it<00:15:10.880> switches<00:15:11.279> scenes<00:15:11.600> and 00:15:11.750 --> 00:15:11.760 align:start position:0% consistency. When it switches scenes and 00:15:11.760 --> 00:15:13.350 align:start position:0% consistency. When it switches scenes and then<00:15:12.000> comes<00:15:12.240> back<00:15:12.399> to<00:15:12.560> the<00:15:12.720> same<00:15:12.959> scene, 00:15:13.350 --> 00:15:13.360 align:start position:0% then comes back to the same scene, 00:15:13.360 --> 00:15:14.550 align:start position:0% then comes back to the same scene, things<00:15:13.600> look<00:15:13.760> really<00:15:14.000> good.<00:15:14.320> That's 00:15:14.550 --> 00:15:14.560 align:start position:0% things look really good. That's 00:15:14.560 --> 00:15:16.069 align:start position:0% things look really good. That's something<00:15:14.720> that's<00:15:15.040> really,<00:15:15.360> really<00:15:15.680> improved 00:15:16.069 --> 00:15:16.079 align:start position:0% something that's really, really improved 00:15:16.079 --> 00:15:17.990 align:start position:0% something that's really, really improved with<00:15:16.240> AI<00:15:16.560> video<00:15:16.880> models.<00:15:17.279> Google<00:15:17.680> also 00:15:17.990 --> 00:15:18.000 align:start position:0% with AI video models. Google also 00:15:18.000 --> 00:15:20.790 align:start position:0% with AI video models. Google also released<00:15:18.560> a<00:15:19.040> new<00:15:19.440> transcription<00:15:20.399> model, 00:15:20.790 --> 00:15:20.800 align:start position:0% released a new transcription model, 00:15:20.800 --> 00:15:23.350 align:start position:0% released a new transcription model, Gemini<00:15:21.279> 3.5<00:15:22.000> Transcribe.<00:15:22.800> Now,<00:15:22.959> this<00:15:23.120> is 00:15:23.350 --> 00:15:23.360 align:start position:0% Gemini 3.5 Transcribe. Now, this is 00:15:23.360 --> 00:15:25.030 align:start position:0% Gemini 3.5 Transcribe. Now, this is pretty<00:15:23.600> much<00:15:23.760> exactly<00:15:24.160> what<00:15:24.320> it<00:15:24.480> sounds<00:15:24.720> like. 00:15:25.030 --> 00:15:25.040 align:start position:0% pretty much exactly what it sounds like. 00:15:25.040 --> 00:15:26.550 align:start position:0% pretty much exactly what it sounds like. It's,<00:15:25.360> you<00:15:25.519> know,<00:15:25.760> their<00:15:26.000> version<00:15:26.240> of 00:15:26.550 --> 00:15:26.560 align:start position:0% It's, you know, their version of 00:15:26.560 --> 00:15:28.949 align:start position:0% It's, you know, their version of Whisper,<00:15:27.040> but<00:15:27.360> apparently<00:15:28.079> more<00:15:28.399> accurate 00:15:28.949 --> 00:15:28.959 align:start position:0% Whisper, but apparently more accurate 00:15:28.959 --> 00:15:30.629 align:start position:0% Whisper, but apparently more accurate than<00:15:29.360> everything<00:15:29.680> else<00:15:29.920> that's<00:15:30.240> out<00:15:30.320> there. 00:15:30.629 --> 00:15:30.639 align:start position:0% than everything else that's out there. 00:15:30.639 --> 00:15:32.949 align:start position:0% than everything else that's out there. And<00:15:30.800> it's<00:15:31.120> available<00:15:31.440> in<00:15:31.600> the<00:15:31.760> Gemini<00:15:32.320> app<00:15:32.560> on 00:15:32.949 --> 00:15:32.959 align:start position:0% And it's available in the Gemini app on 00:15:32.959 --> 00:15:36.150 align:start position:0% And it's available in the Gemini app on MacOSS,<00:15:34.079> Rambler<00:15:34.639> on<00:15:34.959> Android,<00:15:35.680> and<00:15:35.920> coming 00:15:36.150 --> 00:15:36.160 align:start position:0% MacOSS, Rambler on Android, and coming 00:15:36.160 --> 00:15:38.310 align:start position:0% MacOSS, Rambler on Android, and coming soon<00:15:36.399> to<00:15:36.639> Chrome,<00:15:37.120> but<00:15:37.360> you<00:15:37.519> also<00:15:37.760> have<00:15:37.920> it<00:15:38.160> in 00:15:38.310 --> 00:15:38.320 align:start position:0% soon to Chrome, but you also have it in 00:15:38.320 --> 00:15:40.389 align:start position:0% soon to Chrome, but you also have it in the<00:15:38.560> various<00:15:39.040> enterprise<00:15:39.600> platforms,<00:15:40.160> and 00:15:40.389 --> 00:15:40.399 align:start position:0% the various enterprise platforms, and 00:15:40.399 --> 00:15:42.230 align:start position:0% the various enterprise platforms, and via<00:15:40.639> the<00:15:40.880> API<00:15:41.279> if<00:15:41.519> you'd<00:15:41.680> want<00:15:41.760> to<00:15:41.839> use<00:15:41.920> it. 00:15:42.230 --> 00:15:42.240 align:start position:0% via the API if you'd want to use it. 00:15:42.240 --> 00:15:44.790 align:start position:0% via the API if you'd want to use it. Google<00:15:42.560> also<00:15:42.800> added<00:15:43.120> some<00:15:43.279> new<00:15:43.519> AI<00:15:44.000> features 00:15:44.790 --> 00:15:44.800 align:start position:0% Google also added some new AI features 00:15:44.800 --> 00:15:47.189 align:start position:0% Google also added some new AI features for<00:15:45.279> travel<00:15:45.760> inside<00:15:46.079> of<00:15:46.160> the<00:15:46.320> AI<00:15:46.720> mode<00:15:46.880> in 00:15:47.189 --> 00:15:47.199 align:start position:0% for travel inside of the AI mode in 00:15:47.199 --> 00:15:49.189 align:start position:0% for travel inside of the AI mode in search.<00:15:47.600> It<00:15:47.839> can<00:15:47.920> track<00:15:48.240> flight<00:15:48.639> prices<00:15:49.040> for 00:15:49.189 --> 00:15:49.199 align:start position:0% search. It can track flight prices for 00:15:49.199 --> 00:15:50.790 align:start position:0% search. It can track flight prices for you<00:15:49.440> now.<00:15:49.759> It'll<00:15:50.000> show<00:15:50.079> you<00:15:50.160> in<00:15:50.320> both<00:15:50.560> price 00:15:50.790 --> 00:15:50.800 align:start position:0% you now. It'll show you in both price 00:15:50.800 --> 00:15:52.629 align:start position:0% you now. It'll show you in both price and<00:15:51.040> points,<00:15:51.519> and<00:15:51.680> you<00:15:51.839> can<00:15:52.000> apparently<00:15:52.320> book 00:15:52.629 --> 00:15:52.639 align:start position:0% and points, and you can apparently book 00:15:52.639 --> 00:15:55.110 align:start position:0% and points, and you can apparently book hotels<00:15:53.199> directly<00:15:53.680> inside<00:15:54.000> of<00:15:54.160> AI<00:15:54.560> mode<00:15:54.800> in 00:15:55.110 --> 00:15:55.120 align:start position:0% hotels directly inside of AI mode in 00:15:55.120 --> 00:15:57.030 align:start position:0% hotels directly inside of AI mode in search<00:15:55.440> now,<00:15:55.759> as<00:15:56.000> well.<00:15:56.320> There's<00:15:56.560> also<00:15:56.720> a<00:15:56.880> new 00:15:57.030 --> 00:15:57.040 align:start position:0% search now, as well. There's also a new 00:15:57.040 --> 00:15:59.189 align:start position:0% search now, as well. There's also a new update<00:15:57.360> to<00:15:57.680> Gemini<00:15:58.240> notebook,<00:15:58.720> previously 00:15:59.189 --> 00:15:59.199 align:start position:0% update to Gemini notebook, previously 00:15:59.199 --> 00:16:01.269 align:start position:0% update to Gemini notebook, previously known<00:15:59.440> as<00:15:59.600> Notebook<00:16:00.160> LM.<00:16:00.639> You<00:16:00.800> can<00:16:00.959> now 00:16:01.269 --> 00:16:01.279 align:start position:0% known as Notebook LM. You can now 00:16:01.279 --> 00:16:04.069 align:start position:0% known as Notebook LM. You can now incorporate<00:16:02.160> books<00:16:02.480> that<00:16:02.800> you<00:16:02.959> own<00:16:03.600> directly 00:16:04.069 --> 00:16:04.079 align:start position:0% incorporate books that you own directly 00:16:04.079 --> 00:16:06.150 align:start position:0% incorporate books that you own directly into<00:16:04.480> your<00:16:04.720> notebook.<00:16:05.199> So,<00:16:05.360> they<00:16:05.519> say,<00:16:05.680> "We've 00:16:06.150 --> 00:16:06.160 align:start position:0% into your notebook. So, they say, "We've 00:16:06.160 --> 00:16:08.069 align:start position:0% into your notebook. So, they say, "We've built<00:16:06.399> the<00:16:06.639> ability<00:16:06.880> to<00:16:07.040> add<00:16:07.279> select<00:16:07.600> ebooks 00:16:08.069 --> 00:16:08.079 align:start position:0% built the ability to add select ebooks 00:16:08.079 --> 00:16:09.910 align:start position:0% built the ability to add select ebooks you've<00:16:08.320> purchased<00:16:08.639> from<00:16:08.880> Google<00:16:09.199> Playbooks 00:16:09.910 --> 00:16:09.920 align:start position:0% you've purchased from Google Playbooks 00:16:09.920 --> 00:16:12.710 align:start position:0% you've purchased from Google Playbooks directly<00:16:10.560> to<00:16:11.040> a<00:16:11.519> Gemini<00:16:12.000> notebook."<00:16:12.480> So,<00:16:12.560> you 00:16:12.710 --> 00:16:12.720 align:start position:0% directly to a Gemini notebook." So, you 00:16:12.720 --> 00:16:14.230 align:start position:0% directly to a Gemini notebook." So, you would<00:16:12.800> have<00:16:12.959> had<00:16:13.120> to<00:16:13.279> purchase<00:16:13.519> it<00:16:13.759> through, 00:16:14.230 --> 00:16:14.240 align:start position:0% would have had to purchase it through, 00:16:14.240 --> 00:16:16.310 align:start position:0% would have had to purchase it through, you<00:16:14.399> know,<00:16:14.720> Google's<00:16:15.199> book<00:16:15.440> platform.<00:16:16.000> It's<00:16:16.160> a 00:16:16.310 --> 00:16:16.320 align:start position:0% you know, Google's book platform. It's a 00:16:16.320 --> 00:16:17.829 align:start position:0% you know, Google's book platform. It's a pretty<00:16:16.480> cool<00:16:16.720> feature,<00:16:17.199> but<00:16:17.440> personally, 00:16:17.829 --> 00:16:17.839 align:start position:0% pretty cool feature, but personally, 00:16:17.839 --> 00:16:19.749 align:start position:0% pretty cool feature, but personally, when<00:16:18.079> I<00:16:18.240> do<00:16:18.399> buy<00:16:18.560> ebooks,<00:16:19.040> it's<00:16:19.279> mostly<00:16:19.600> on 00:16:19.749 --> 00:16:19.759 align:start position:0% when I do buy ebooks, it's mostly on 00:16:19.759 --> 00:16:23.269 align:start position:0% when I do buy ebooks, it's mostly on Kindle.<00:16:20.560> And<00:16:20.880> if<00:16:21.199> you<00:16:21.360> use<00:16:21.759> anti-gravity<00:16:22.880> to 00:16:23.269 --> 00:16:23.279 align:start position:0% Kindle. And if you use anti-gravity to 00:16:23.279 --> 00:16:25.829 align:start position:0% Kindle. And if you use anti-gravity to do<00:16:23.519> your<00:16:23.759> coding,<00:16:24.399> they<00:16:24.720> finally<00:16:25.199> added<00:16:25.519> a 00:16:25.829 --> 00:16:25.839 align:start position:0% do your coding, they finally added a 00:16:25.839 --> 00:16:27.670 align:start position:0% do your coding, they finally added a remote<00:16:26.320> control<00:16:26.720> feature.<00:16:27.199> This<00:16:27.360> is<00:16:27.440> a 00:16:27.670 --> 00:16:27.680 align:start position:0% remote control feature. This is a 00:16:27.680 --> 00:16:29.829 align:start position:0% remote control feature. This is a feature<00:16:27.920> that<00:16:28.240> pretty<00:16:28.560> much<00:16:28.880> every<00:16:29.360> other 00:16:29.829 --> 00:16:29.839 align:start position:0% feature that pretty much every other 00:16:29.839 --> 00:16:32.710 align:start position:0% feature that pretty much every other sort<00:16:30.079> of<00:16:30.320> AI<00:16:30.720> enabled<00:16:31.279> IDE<00:16:31.839> has<00:16:32.079> had<00:16:32.320> for<00:16:32.480> a 00:16:32.710 --> 00:16:32.720 align:start position:0% sort of AI enabled IDE has had for a 00:16:32.720 --> 00:16:35.350 align:start position:0% sort of AI enabled IDE has had for a while<00:16:32.880> now,<00:16:33.360> but<00:16:33.600> now<00:16:33.839> it<00:16:34.079> is<00:16:34.320> also<00:16:34.720> inside<00:16:35.120> of 00:16:35.350 --> 00:16:35.360 align:start position:0% while now, but now it is also inside of 00:16:35.360 --> 00:16:37.350 align:start position:0% while now, but now it is also inside of anti-gravity.<00:16:36.320> Remote<00:16:36.639> control<00:16:36.959> allows<00:16:37.199> you 00:16:37.350 --> 00:16:37.360 align:start position:0% anti-gravity. Remote control allows you 00:16:37.360 --> 00:16:39.189 align:start position:0% anti-gravity. Remote control allows you to<00:16:37.440> connect<00:16:37.759> and<00:16:38.079> drive<00:16:38.320> your<00:16:38.480> anti-gravity 00:16:39.189 --> 00:16:39.199 align:start position:0% to connect and drive your anti-gravity 00:16:39.199 --> 00:16:40.790 align:start position:0% to connect and drive your anti-gravity sessions<00:16:39.680> running<00:16:40.000> across<00:16:40.320> your<00:16:40.560> different 00:16:40.790 --> 00:16:40.800 align:start position:0% sessions running across your different 00:16:40.800 --> 00:16:42.550 align:start position:0% sessions running across your different machines<00:16:41.360> like<00:16:41.600> laptop,<00:16:42.079> servers,<00:16:42.399> and 00:16:42.550 --> 00:16:42.560 align:start position:0% machines like laptop, servers, and 00:16:42.560 --> 00:16:44.550 align:start position:0% machines like laptop, servers, and desktops.<00:16:43.199> All<00:16:43.360> you<00:16:43.519> need<00:16:43.600> is<00:16:43.759> a<00:16:43.920> web<00:16:44.079> browser. 00:16:44.550 --> 00:16:44.560 align:start position:0% desktops. All you need is a web browser. 00:16:44.560 --> 00:16:46.230 align:start position:0% desktops. All you need is a web browser. while<00:16:44.800> you<00:16:44.959> have<00:16:45.120> your<00:16:45.360> web<00:16:45.519> browser<00:16:45.920> handy. 00:16:46.230 --> 00:16:46.240 align:start position:0% while you have your web browser handy. 00:16:46.240 --> 00:16:47.590 align:start position:0% while you have your web browser handy. You're<00:16:46.320> able<00:16:46.480> to<00:16:46.560> remotely<00:16:46.959> connect<00:16:47.199> to<00:16:47.440> each 00:16:47.590 --> 00:16:47.600 align:start position:0% You're able to remotely connect to each 00:16:47.600 --> 00:16:49.110 align:start position:0% You're able to remotely connect to each of<00:16:47.759> your<00:16:47.920> different<00:16:48.320> machines<00:16:48.800> running 00:16:49.110 --> 00:16:49.120 align:start position:0% of your different machines running 00:16:49.120 --> 00:16:51.110 align:start position:0% of your different machines running anti-gravity<00:16:49.920> and<00:16:50.160> retain<00:16:50.480> full<00:16:50.800> access<00:16:50.959> to 00:16:51.110 --> 00:16:51.120 align:start position:0% anti-gravity and retain full access to 00:16:51.120 --> 00:16:52.629 align:start position:0% anti-gravity and retain full access to your<00:16:51.279> files,<00:16:51.600> workspaces,<00:16:52.160> build<00:16:52.320> tools, 00:16:52.629 --> 00:16:52.639 align:start position:0% your files, workspaces, build tools, 00:16:52.639 --> 00:16:54.069 align:start position:0% your files, workspaces, build tools, credentials,<00:16:53.279> etc.<00:16:53.600> Again,<00:16:53.839> this<00:16:54.000> is 00:16:54.069 --> 00:16:54.079 align:start position:0% credentials, etc. Again, this is 00:16:54.079 --> 00:16:55.350 align:start position:0% credentials, etc. Again, this is something<00:16:54.160> we've<00:16:54.399> had<00:16:54.560> in<00:16:54.720> Codeex<00:16:55.120> for<00:16:55.279> a 00:16:55.350 --> 00:16:55.360 align:start position:0% something we've had in Codeex for a 00:16:55.360 --> 00:16:56.870 align:start position:0% something we've had in Codeex for a while<00:16:55.519> now.<00:16:55.839> We've<00:16:56.000> had<00:16:56.079> it<00:16:56.240> in<00:16:56.320> Claude<00:16:56.720> Code 00:16:56.870 --> 00:16:56.880 align:start position:0% while now. We've had it in Claude Code 00:16:56.880 --> 00:16:59.030 align:start position:0% while now. We've had it in Claude Code for<00:16:57.040> a<00:16:57.199> bit<00:16:57.279> now.<00:16:57.839> It's<00:16:58.000> been<00:16:58.079> in<00:16:58.320> cursor<00:16:58.720> for<00:16:58.880> a 00:16:59.030 --> 00:16:59.040 align:start position:0% for a bit now. It's been in cursor for a 00:16:59.040 --> 00:17:00.949 align:start position:0% for a bit now. It's been in cursor for a bit<00:16:59.199> now.<00:16:59.600> And<00:16:59.759> well,<00:17:00.240> you<00:17:00.480> could<00:17:00.560> do<00:17:00.639> it<00:17:00.800> in 00:17:00.949 --> 00:17:00.959 align:start position:0% bit now. And well, you could do it in 00:17:00.959 --> 00:17:02.550 align:start position:0% bit now. And well, you could do it in anti-gravity<00:17:01.600> now,<00:17:01.759> too.<00:17:02.000> Now,<00:17:02.160> it<00:17:02.320> has<00:17:02.480> been 00:17:02.550 --> 00:17:02.560 align:start position:0% anti-gravity now, too. Now, it has been 00:17:02.560 --> 00:17:04.150 align:start position:0% anti-gravity now, too. Now, it has been a<00:17:02.800> really,<00:17:02.959> really<00:17:03.279> busy<00:17:03.600> week,<00:17:03.759> and<00:17:04.000> I've 00:17:04.150 --> 00:17:04.160 align:start position:0% a really, really busy week, and I've 00:17:04.160 --> 00:17:06.470 align:start position:0% a really, really busy week, and I've shared<00:17:04.400> a<00:17:04.640> lot<00:17:04.799> already.<00:17:05.520> And<00:17:05.679> I<00:17:05.919> still<00:17:06.160> have 00:17:06.470 --> 00:17:06.480 align:start position:0% shared a lot already. And I still have 00:17:06.480 --> 00:17:08.390 align:start position:0% shared a lot already. And I still have quite<00:17:06.799> a<00:17:07.039> few<00:17:07.199> more<00:17:07.439> things<00:17:07.679> I<00:17:07.919> want<00:17:08.000> to<00:17:08.160> share, 00:17:08.390 --> 00:17:08.400 align:start position:0% quite a few more things I want to share, 00:17:08.400 --> 00:17:09.590 align:start position:0% quite a few more things I want to share, but<00:17:08.640> I'm<00:17:08.799> just<00:17:08.880> going<00:17:08.959> to<00:17:09.039> run<00:17:09.199> through<00:17:09.360> them 00:17:09.590 --> 00:17:09.600 align:start position:0% but I'm just going to run through them 00:17:09.600 --> 00:17:14.710 align:start position:0% but I'm just going to run through them super<00:17:10.000> quick<00:17:10.160> in<00:17:10.319> a<00:17:10.559> rapid<00:17:10.880> fire. 00:17:14.710 --> 00:17:14.720 align:start position:0% 00:17:14.720 --> 00:17:16.309 align:start position:0% We<00:17:14.959> got<00:17:15.039> a<00:17:15.280> couple<00:17:15.439> additional<00:17:15.839> updates<00:17:16.240> out 00:17:16.309 --> 00:17:16.319 align:start position:0% We got a couple additional updates out 00:17:16.319 --> 00:17:19.829 align:start position:0% We got a couple additional updates out of<00:17:16.480> OpenAI.<00:17:17.120> ChatGPT<00:17:17.919> work<00:17:18.240> can<00:17:18.559> now<00:17:18.880> use<00:17:19.439> its 00:17:19.829 --> 00:17:19.839 align:start position:0% of OpenAI. ChatGPT work can now use its 00:17:19.839 --> 00:17:21.829 align:start position:0% of OpenAI. ChatGPT work can now use its computer<00:17:20.319> and<00:17:20.640> browser<00:17:21.039> to<00:17:21.280> sign<00:17:21.520> into 00:17:21.829 --> 00:17:21.839 align:start position:0% computer and browser to sign into 00:17:21.839 --> 00:17:24.150 align:start position:0% computer and browser to sign into websites<00:17:22.400> on<00:17:22.640> both<00:17:22.880> web<00:17:23.120> and<00:17:23.439> mobile.<00:17:23.839> Now,<00:17:24.000> if 00:17:24.150 --> 00:17:24.160 align:start position:0% websites on both web and mobile. Now, if 00:17:24.160 --> 00:17:26.390 align:start position:0% websites on both web and mobile. Now, if you're<00:17:24.319> using<00:17:24.480> the<00:17:24.640> ChatGpt<00:17:25.520> app,<00:17:25.839> it<00:17:26.079> has<00:17:26.160> a 00:17:26.390 --> 00:17:26.400 align:start position:0% you're using the ChatGpt app, it has a 00:17:26.400 --> 00:17:27.990 align:start position:0% you're using the ChatGpt app, it has a built-in<00:17:26.799> browser<00:17:27.280> which<00:17:27.520> can<00:17:27.679> remember 00:17:27.990 --> 00:17:28.000 align:start position:0% built-in browser which can remember 00:17:28.000 --> 00:17:29.750 align:start position:0% built-in browser which can remember passwords<00:17:28.480> and<00:17:28.720> things<00:17:28.880> like<00:17:29.039> that.<00:17:29.360> But<00:17:29.520> this 00:17:29.750 --> 00:17:29.760 align:start position:0% passwords and things like that. But this 00:17:29.760 --> 00:17:31.669 align:start position:0% passwords and things like that. But this is<00:17:29.919> now<00:17:30.240> available<00:17:30.640> on<00:17:30.880> the<00:17:31.039> web<00:17:31.360> version. 00:17:31.669 --> 00:17:31.679 align:start position:0% is now available on the web version. 00:17:31.679 --> 00:17:33.510 align:start position:0% is now available on the web version. Here's<00:17:31.919> an<00:17:32.080> example<00:17:32.320> they<00:17:32.559> give<00:17:32.799> to<00:17:33.039> log<00:17:33.280> into 00:17:33.510 --> 00:17:33.520 align:start position:0% Here's an example they give to log into 00:17:33.520 --> 00:17:36.549 align:start position:0% Here's an example they give to log into DMV<00:17:34.240> and<00:17:34.559> help<00:17:34.799> me<00:17:35.440> replace<00:17:35.840> my<00:17:36.080> driver's 00:17:36.549 --> 00:17:36.559 align:start position:0% DMV and help me replace my driver's 00:17:36.559 --> 00:17:38.230 align:start position:0% DMV and help me replace my driver's license.<00:17:37.039> And<00:17:37.200> you<00:17:37.360> can<00:17:37.440> see<00:17:37.600> it<00:17:37.760> logs<00:17:38.080> into 00:17:38.230 --> 00:17:38.240 align:start position:0% license. And you can see it logs into 00:17:38.240 --> 00:17:40.549 align:start position:0% license. And you can see it logs into the<00:17:38.480> site<00:17:38.720> and<00:17:39.120> then<00:17:39.440> asks<00:17:39.760> you<00:17:40.000> to<00:17:40.240> continue 00:17:40.549 --> 00:17:40.559 align:start position:0% the site and then asks you to continue 00:17:40.559 --> 00:17:42.470 align:start position:0% the site and then asks you to continue with<00:17:40.799> your<00:17:40.960> password<00:17:41.520> and<00:17:41.760> it<00:17:41.919> can<00:17:42.080> log<00:17:42.240> in 00:17:42.470 --> 00:17:42.480 align:start position:0% with your password and it can log in 00:17:42.480 --> 00:17:44.789 align:start position:0% with your password and it can log in with<00:17:42.720> things<00:17:42.960> like<00:17:43.280> one<00:17:43.600> password<00:17:44.000> or<00:17:44.400> your 00:17:44.789 --> 00:17:44.799 align:start position:0% with things like one password or your 00:17:44.799 --> 00:17:47.270 align:start position:0% with things like one password or your built-in<00:17:45.360> password<00:17:45.840> manager.<00:17:46.400> And<00:17:46.640> it<00:17:46.880> never 00:17:47.270 --> 00:17:47.280 align:start position:0% built-in password manager. And it never 00:17:47.280 --> 00:17:49.590 align:start position:0% built-in password manager. And it never actually<00:17:48.000> knows<00:17:48.320> your<00:17:48.640> passwords.<00:17:49.360> Now, 00:17:49.590 --> 00:17:49.600 align:start position:0% actually knows your passwords. Now, 00:17:49.600 --> 00:17:51.110 align:start position:0% actually knows your passwords. Now, personally,<00:17:50.000> I<00:17:50.240> still<00:17:50.400> like<00:17:50.559> using<00:17:50.720> the<00:17:50.880> chat 00:17:51.110 --> 00:17:51.120 align:start position:0% personally, I still like using the chat 00:17:51.120 --> 00:17:53.270 align:start position:0% personally, I still like using the chat GPT<00:17:51.600> app<00:17:51.919> better<00:17:52.240> cuz<00:17:52.400> it<00:17:52.559> will<00:17:52.720> just<00:17:52.880> open<00:17:53.039> the 00:17:53.270 --> 00:17:53.280 align:start position:0% GPT app better cuz it will just open the 00:17:53.280 --> 00:17:55.590 align:start position:0% GPT app better cuz it will just open the browser<00:17:53.600> and<00:17:53.760> then<00:17:54.000> log<00:17:54.320> in<00:17:54.720> for<00:17:54.960> you<00:17:55.280> using 00:17:55.590 --> 00:17:55.600 align:start position:0% browser and then log in for you using 00:17:55.600 --> 00:17:56.870 align:start position:0% browser and then log in for you using whatever<00:17:55.919> saved<00:17:56.160> credentials<00:17:56.640> you<00:17:56.799> have 00:17:56.870 --> 00:17:56.880 align:start position:0% whatever saved credentials you have 00:17:56.880 --> 00:17:58.870 align:start position:0% whatever saved credentials you have inside<00:17:57.120> of<00:17:57.200> the<00:17:57.280> chat<00:17:57.600> GPT<00:17:58.000> browser.<00:17:58.480> But<00:17:58.720> if 00:17:58.870 --> 00:17:58.880 align:start position:0% inside of the chat GPT browser. But if 00:17:58.880 --> 00:18:00.870 align:start position:0% inside of the chat GPT browser. But if you<00:17:59.039> like<00:17:59.280> to<00:17:59.440> use<00:17:59.600> the<00:17:59.760> web<00:18:00.000> browser<00:18:00.320> version, 00:18:00.870 --> 00:18:00.880 align:start position:0% you like to use the web browser version, 00:18:00.880 --> 00:18:02.789 align:start position:0% you like to use the web browser version, this<00:18:01.039> is<00:18:01.120> a<00:18:01.360> pretty<00:18:01.679> cool<00:18:02.000> new<00:18:02.240> quality<00:18:02.640> of 00:18:02.789 --> 00:18:02.799 align:start position:0% this is a pretty cool new quality of 00:18:02.799 --> 00:18:04.230 align:start position:0% this is a pretty cool new quality of life<00:18:02.960> update<00:18:03.360> feature<00:18:03.600> as<00:18:03.760> well.<00:18:04.000> There's 00:18:04.230 --> 00:18:04.240 align:start position:0% life update feature as well. There's 00:18:04.240 --> 00:18:06.150 align:start position:0% life update feature as well. There's another<00:18:04.480> new<00:18:04.640> feature<00:18:04.799> inside<00:18:05.039> of<00:18:05.200> chat<00:18:05.520> GPT 00:18:06.150 --> 00:18:06.160 align:start position:0% another new feature inside of chat GPT 00:18:06.160 --> 00:18:08.230 align:start position:0% another new feature inside of chat GPT work<00:18:06.480> on<00:18:06.640> web<00:18:06.880> and<00:18:07.120> mobile.<00:18:07.520> If<00:18:07.679> you're<00:18:07.840> on<00:18:08.000> a 00:18:08.230 --> 00:18:08.240 align:start position:0% work on web and mobile. If you're on a 00:18:08.240 --> 00:18:10.470 align:start position:0% work on web and mobile. If you're on a plus<00:18:08.480> or<00:18:08.640> a<00:18:08.880> pro<00:18:09.120> plan,<00:18:09.679> you<00:18:09.840> can<00:18:09.919> now<00:18:10.160> have 00:18:10.470 --> 00:18:10.480 align:start position:0% plus or a pro plan, you can now have 00:18:10.480 --> 00:18:13.110 align:start position:0% plus or a pro plan, you can now have tasks<00:18:11.039> run<00:18:11.520> based<00:18:11.760> on<00:18:12.080> things<00:18:12.400> changing<00:18:12.799> in 00:18:13.110 --> 00:18:13.120 align:start position:0% tasks run based on things changing in 00:18:13.120 --> 00:18:15.270 align:start position:0% tasks run based on things changing in places<00:18:13.360> like<00:18:13.600> Slack,<00:18:14.000> Gmail,<00:18:14.400> and<00:18:14.640> GitHub. 00:18:15.270 --> 00:18:15.280 align:start position:0% places like Slack, Gmail, and GitHub. 00:18:15.280 --> 00:18:16.950 align:start position:0% places like Slack, Gmail, and GitHub. So,<00:18:15.600> in<00:18:15.760> the<00:18:15.919> past,<00:18:16.240> you've<00:18:16.480> got<00:18:16.640> this 00:18:16.950 --> 00:18:16.960 align:start position:0% So, in the past, you've got this 00:18:16.960 --> 00:18:18.789 align:start position:0% So, in the past, you've got this scheduled<00:18:17.360> tab<00:18:17.679> here,<00:18:18.000> and<00:18:18.240> you<00:18:18.400> can<00:18:18.480> have<00:18:18.640> it 00:18:18.789 --> 00:18:18.799 align:start position:0% scheduled tab here, and you can have it 00:18:18.799 --> 00:18:20.470 align:start position:0% scheduled tab here, and you can have it schedule<00:18:19.120> a<00:18:19.280> task<00:18:19.520> to<00:18:19.760> run,<00:18:20.000> you<00:18:20.160> know,<00:18:20.240> every 00:18:20.470 --> 00:18:20.480 align:start position:0% schedule a task to run, you know, every 00:18:20.480 --> 00:18:22.950 align:start position:0% schedule a task to run, you know, every day<00:18:20.640> at<00:18:20.880> 2:00.<00:18:21.600> Now,<00:18:21.760> you<00:18:22.000> can<00:18:22.080> say<00:18:22.400> schedule<00:18:22.720> a 00:18:22.950 --> 00:18:22.960 align:start position:0% day at 2:00. Now, you can say schedule a 00:18:22.960 --> 00:18:25.110 align:start position:0% day at 2:00. Now, you can say schedule a task<00:18:23.200> every<00:18:23.520> time<00:18:23.600> I<00:18:23.840> get<00:18:24.080> this<00:18:24.480> Slack<00:18:24.880> message 00:18:25.110 --> 00:18:25.120 align:start position:0% task every time I get this Slack message 00:18:25.120 --> 00:18:27.350 align:start position:0% task every time I get this Slack message or<00:18:25.440> schedule<00:18:25.760> a<00:18:25.919> task<00:18:26.160> every<00:18:26.400> time<00:18:26.640> this<00:18:26.960> Gmail 00:18:27.350 --> 00:18:27.360 align:start position:0% or schedule a task every time this Gmail 00:18:27.360 --> 00:18:29.590 align:start position:0% or schedule a task every time this Gmail message<00:18:27.679> comes<00:18:27.919> across.<00:18:28.480> So,<00:18:28.799> more<00:18:29.039> ways<00:18:29.360> to 00:18:29.590 --> 00:18:29.600 align:start position:0% message comes across. So, more ways to 00:18:29.600 --> 00:18:31.510 align:start position:0% message comes across. So, more ways to have<00:18:29.919> automations<00:18:30.640> fire<00:18:30.960> off<00:18:31.120> on<00:18:31.360> your 00:18:31.510 --> 00:18:31.520 align:start position:0% have automations fire off on your 00:18:31.520 --> 00:18:33.990 align:start position:0% have automations fire off on your behalf.<00:18:31.840> OpenAI<00:18:32.559> also<00:18:32.880> dropped<00:18:33.200> the<00:18:33.440> price<00:18:33.760> on 00:18:33.990 --> 00:18:34.000 align:start position:0% behalf. OpenAI also dropped the price on 00:18:34.000 --> 00:18:36.549 align:start position:0% behalf. OpenAI also dropped the price on their<00:18:34.160> most<00:18:34.400> powerful<00:18:34.960> model.<00:18:35.440> So<00:18:35.600> their<00:18:35.840> GPT 00:18:36.549 --> 00:18:36.559 align:start position:0% their most powerful model. So their GPT 00:18:36.559 --> 00:18:39.909 align:start position:0% their most powerful model. So their GPT 5.6<00:18:37.520> Soul<00:18:37.919> model<00:18:38.320> is<00:18:38.559> actually<00:18:38.960> 20%<00:18:39.600> cheaper 00:18:39.909 --> 00:18:39.919 align:start position:0% 5.6 Soul model is actually 20% cheaper 00:18:39.919 --> 00:18:41.590 align:start position:0% 5.6 Soul model is actually 20% cheaper for<00:18:40.160> the<00:18:40.320> next<00:18:40.480> three<00:18:40.720> months.<00:18:41.200> So<00:18:41.360> that's 00:18:41.590 --> 00:18:41.600 align:start position:0% for the next three months. So that's 00:18:41.600 --> 00:18:42.870 align:start position:0% for the next three months. So that's pretty<00:18:41.840> cool<00:18:42.000> as<00:18:42.160> well.<00:18:42.320> Moving<00:18:42.559> on<00:18:42.640> to 00:18:42.870 --> 00:18:42.880 align:start position:0% pretty cool as well. Moving on to 00:18:42.880 --> 00:18:45.029 align:start position:0% pretty cool as well. Moving on to Anthropic<00:18:43.520> news.<00:18:43.919> Claude<00:18:44.320> is<00:18:44.480> getting<00:18:44.720> its 00:18:45.029 --> 00:18:45.039 align:start position:0% Anthropic news. Claude is getting its 00:18:45.039 --> 00:18:47.110 align:start position:0% Anthropic news. Claude is getting its own<00:18:45.280> browser<00:18:45.840> inside<00:18:46.160> of<00:18:46.400> Co-work.<00:18:46.960> You<00:18:47.039> know, 00:18:47.110 --> 00:18:47.120 align:start position:0% own browser inside of Co-work. You know, 00:18:47.120 --> 00:18:49.510 align:start position:0% own browser inside of Co-work. You know, we<00:18:47.440> saw<00:18:47.919> this<00:18:48.160> happen<00:18:48.400> in<00:18:48.640> Codeex<00:18:49.280> and 00:18:49.510 --> 00:18:49.520 align:start position:0% we saw this happen in Codeex and 00:18:49.520 --> 00:18:51.909 align:start position:0% we saw this happen in Codeex and Anthropic<00:18:50.320> likes<00:18:50.559> to<00:18:50.799> steal<00:18:51.200> OpenAI's 00:18:51.909 --> 00:18:51.919 align:start position:0% Anthropic likes to steal OpenAI's 00:18:51.919 --> 00:18:54.070 align:start position:0% Anthropic likes to steal OpenAI's homework<00:18:52.240> and<00:18:52.480> whatever<00:18:52.880> a<00:18:53.120> feature<00:18:53.760> looks 00:18:54.070 --> 00:18:54.080 align:start position:0% homework and whatever a feature looks 00:18:54.080 --> 00:18:56.150 align:start position:0% homework and whatever a feature looks cool<00:18:54.240> that<00:18:54.480> OpenAI<00:18:55.120> does,<00:18:55.360> Enthropic<00:18:56.000> seems 00:18:56.150 --> 00:18:56.160 align:start position:0% cool that OpenAI does, Enthropic seems 00:18:56.160 --> 00:18:57.750 align:start position:0% cool that OpenAI does, Enthropic seems to<00:18:56.320> roll<00:18:56.480> it<00:18:56.640> into<00:18:56.880> their<00:18:57.120> products<00:18:57.440> these 00:18:57.750 --> 00:18:57.760 align:start position:0% to roll it into their products these 00:18:57.760 --> 00:19:00.230 align:start position:0% to roll it into their products these days<00:18:57.919> as<00:18:58.160> well.<00:18:58.480> Codex<00:18:59.039> has<00:18:59.200> its<00:18:59.440> own<00:18:59.679> browser. 00:19:00.230 --> 00:19:00.240 align:start position:0% days as well. Codex has its own browser. 00:19:00.240 --> 00:19:02.070 align:start position:0% days as well. Codex has its own browser. Couple<00:19:00.640> weeks<00:19:00.880> later,<00:19:01.280> Claude<00:19:01.679> is<00:19:01.840> like, 00:19:02.070 --> 00:19:02.080 align:start position:0% Couple weeks later, Claude is like, 00:19:02.080 --> 00:19:04.230 align:start position:0% Couple weeks later, Claude is like, "Yeah,<00:19:02.640> us<00:19:03.039> too."<00:19:03.360> Although<00:19:03.679> I<00:19:03.840> don't<00:19:04.080> believe 00:19:04.230 --> 00:19:04.240 align:start position:0% "Yeah, us too." Although I don't believe 00:19:04.240 --> 00:19:06.789 align:start position:0% "Yeah, us too." Although I don't believe it's<00:19:04.559> available<00:19:05.280> quite<00:19:05.679> yet.<00:19:06.160> Yeah.<00:19:06.400> So,<00:19:06.480> we 00:19:06.789 --> 00:19:06.799 align:start position:0% it's available quite yet. Yeah. So, we 00:19:06.799 --> 00:19:08.470 align:start position:0% it's available quite yet. Yeah. So, we see<00:19:06.960> the<00:19:07.120> built-in<00:19:07.520> browser<00:19:07.840> is<00:19:08.000> rolling<00:19:08.240> out 00:19:08.470 --> 00:19:08.480 align:start position:0% see the built-in browser is rolling out 00:19:08.480 --> 00:19:10.470 align:start position:0% see the built-in browser is rolling out over<00:19:08.720> the<00:19:08.880> coming<00:19:09.120> weeks<00:19:09.360> to<00:19:09.600> Pro,<00:19:09.919> Max,<00:19:10.240> and 00:19:10.470 --> 00:19:10.480 align:start position:0% over the coming weeks to Pro, Max, and 00:19:10.480 --> 00:19:13.270 align:start position:0% over the coming weeks to Pro, Max, and Teams<00:19:10.960> plans<00:19:11.440> on<00:19:11.760> Claude<00:19:12.160> desktop<00:19:12.720> app<00:19:12.960> on 00:19:13.270 --> 00:19:13.280 align:start position:0% Teams plans on Claude desktop app on 00:19:13.280 --> 00:19:16.070 align:start position:0% Teams plans on Claude desktop app on MacOSS,<00:19:14.240> Windows,<00:19:14.720> and<00:19:15.120> Linux.<00:19:15.760> They 00:19:16.070 --> 00:19:16.080 align:start position:0% MacOSS, Windows, and Linux. They 00:19:16.080 --> 00:19:18.070 align:start position:0% MacOSS, Windows, and Linux. They announced<00:19:16.480> that<00:19:16.640> it's<00:19:16.960> coming,<00:19:17.360> but<00:19:17.600> it's<00:19:17.840> not 00:19:18.070 --> 00:19:18.080 align:start position:0% announced that it's coming, but it's not 00:19:18.080 --> 00:19:20.630 align:start position:0% announced that it's coming, but it's not here<00:19:18.400> yet.<00:19:18.799> But<00:19:18.880> they<00:19:19.120> also<00:19:19.280> have<00:19:19.600> Claude<00:19:20.160> in 00:19:20.630 --> 00:19:20.640 align:start position:0% here yet. But they also have Claude in 00:19:20.640 --> 00:19:22.310 align:start position:0% here yet. But they also have Claude in Chrome,<00:19:21.039> which<00:19:21.280> is<00:19:21.360> now<00:19:21.760> generally 00:19:22.310 --> 00:19:22.320 align:start position:0% Chrome, which is now generally 00:19:22.320 --> 00:19:24.390 align:start position:0% Chrome, which is now generally available,<00:19:22.880> which<00:19:23.120> is<00:19:23.200> a<00:19:23.440> Chrome<00:19:23.760> extension 00:19:24.390 --> 00:19:24.400 align:start position:0% available, which is a Chrome extension 00:19:24.400 --> 00:19:26.390 align:start position:0% available, which is a Chrome extension that<00:19:24.720> will<00:19:25.039> basically,<00:19:25.600> you<00:19:25.760> know,<00:19:25.919> summarize 00:19:26.390 --> 00:19:26.400 align:start position:0% that will basically, you know, summarize 00:19:26.400 --> 00:19:28.230 align:start position:0% that will basically, you know, summarize articles<00:19:26.799> for<00:19:27.039> you<00:19:27.200> on<00:19:27.360> the<00:19:27.520> web.<00:19:27.760> It<00:19:28.000> will 00:19:28.230 --> 00:19:28.240 align:start position:0% articles for you on the web. It will 00:19:28.240 --> 00:19:30.230 align:start position:0% articles for you on the web. It will fill<00:19:28.400> in<00:19:28.720> details<00:19:29.120> for<00:19:29.360> you.<00:19:29.760> it<00:19:29.919> can<00:19:30.080> actually 00:19:30.230 --> 00:19:30.240 align:start position:0% fill in details for you. it can actually 00:19:30.240 --> 00:19:32.710 align:start position:0% fill in details for you. it can actually click<00:19:30.559> around,<00:19:30.960> but<00:19:31.120> it<00:19:31.360> is<00:19:31.600> pretty<00:19:32.080> slow.<00:19:32.559> So, 00:19:32.710 --> 00:19:32.720 align:start position:0% click around, but it is pretty slow. So, 00:19:32.720 --> 00:19:35.430 align:start position:0% click around, but it is pretty slow. So, I'm<00:19:32.960> hoping<00:19:33.600> when<00:19:33.919> they<00:19:34.240> actually<00:19:34.880> build<00:19:35.200> the 00:19:35.430 --> 00:19:35.440 align:start position:0% I'm hoping when they actually build the 00:19:35.440 --> 00:19:37.750 align:start position:0% I'm hoping when they actually build the browser<00:19:35.919> into<00:19:36.320> their<00:19:36.720> app,<00:19:37.039> that<00:19:37.200> will<00:19:37.360> be<00:19:37.520> a 00:19:37.750 --> 00:19:37.760 align:start position:0% browser into their app, that will be a 00:19:37.760 --> 00:19:39.430 align:start position:0% browser into their app, that will be a much<00:19:38.000> faster<00:19:38.400> way<00:19:38.559> to<00:19:38.720> do<00:19:38.880> a<00:19:39.039> lot<00:19:39.120> of<00:19:39.200> those 00:19:39.430 --> 00:19:39.440 align:start position:0% much faster way to do a lot of those 00:19:39.440 --> 00:19:41.110 align:start position:0% much faster way to do a lot of those things.<00:19:39.760> Enthropic<00:19:40.400> also<00:19:40.640> announced<00:19:40.960> this 00:19:41.110 --> 00:19:41.120 align:start position:0% things. Enthropic also announced this 00:19:41.120 --> 00:19:42.710 align:start position:0% things. Enthropic also announced this week<00:19:41.280> that<00:19:41.520> Claude's<00:19:42.000> memory<00:19:42.320> works 00:19:42.710 --> 00:19:42.720 align:start position:0% week that Claude's memory works 00:19:42.720 --> 00:19:44.390 align:start position:0% week that Claude's memory works everywhere.<00:19:43.360> So,<00:19:43.600> starting<00:19:43.919> today,<00:19:44.160> the 00:19:44.390 --> 00:19:44.400 align:start position:0% everywhere. So, starting today, the 00:19:44.400 --> 00:19:46.789 align:start position:0% everywhere. So, starting today, the memory<00:19:44.640> you<00:19:44.799> use<00:19:44.960> in<00:19:45.200> chat<00:19:45.520> is<00:19:45.760> the<00:19:45.919> same<00:19:46.160> as<00:19:46.480> in 00:19:46.789 --> 00:19:46.799 align:start position:0% memory you use in chat is the same as in 00:19:46.799 --> 00:19:49.110 align:start position:0% memory you use in chat is the same as in Claude<00:19:47.280> Co-work.<00:19:47.840> Co-work<00:19:48.320> now<00:19:48.559> has<00:19:48.799> memory, 00:19:49.110 --> 00:19:49.120 align:start position:0% Claude Co-work. Co-work now has memory, 00:19:49.120 --> 00:19:50.950 align:start position:0% Claude Co-work. Co-work now has memory, and<00:19:49.280> it's<00:19:49.520> the<00:19:49.679> same<00:19:49.760> one<00:19:50.000> you<00:19:50.160> use<00:19:50.320> in<00:19:50.559> chat, 00:19:50.950 --> 00:19:50.960 align:start position:0% and it's the same one you use in chat, 00:19:50.960 --> 00:19:52.710 align:start position:0% and it's the same one you use in chat, leading<00:19:51.200> to<00:19:51.360> less<00:19:51.679> reexplaining<00:19:52.240> and<00:19:52.480> more 00:19:52.710 --> 00:19:52.720 align:start position:0% leading to less reexplaining and more 00:19:52.720 --> 00:19:53.909 align:start position:0% leading to less reexplaining and more picking<00:19:52.960> up<00:19:53.120> where<00:19:53.280> you<00:19:53.360> left<00:19:53.520> off.<00:19:53.760> When 00:19:53.909 --> 00:19:53.919 align:start position:0% picking up where you left off. When 00:19:53.919 --> 00:19:55.669 align:start position:0% picking up where you left off. When Co-works<00:19:54.559> a<00:19:54.720> task<00:19:54.880> in<00:19:55.039> the<00:19:55.200> cloud,<00:19:55.520> what 00:19:55.669 --> 00:19:55.679 align:start position:0% Co-works a task in the cloud, what 00:19:55.679 --> 00:19:57.590 align:start position:0% Co-works a task in the cloud, what Claude<00:19:56.080> remembers<00:19:56.559> from<00:19:56.799> your<00:19:57.039> chats<00:19:57.360> is 00:19:57.590 --> 00:19:57.600 align:start position:0% Claude remembers from your chats is 00:19:57.600 --> 00:19:59.430 align:start position:0% Claude remembers from your chats is there,<00:19:57.840> and<00:19:58.080> vice<00:19:58.320> versa.<00:19:58.720> So<00:19:58.960> you<00:19:59.120> can<00:19:59.280> sort 00:19:59.430 --> 00:19:59.440 align:start position:0% there, and vice versa. So you can sort 00:19:59.440 --> 00:20:01.110 align:start position:0% there, and vice versa. So you can sort of<00:19:59.600> plan<00:19:59.919> out<00:20:00.160> something<00:20:00.400> you<00:20:00.640> want<00:20:00.720> to<00:20:00.799> do<00:20:00.960> in 00:20:01.110 --> 00:20:01.120 align:start position:0% of plan out something you want to do in 00:20:01.120 --> 00:20:03.669 align:start position:0% of plan out something you want to do in a<00:20:01.280> regular<00:20:01.679> chat.<00:20:02.160> Jump<00:20:02.400> over<00:20:02.559> to<00:20:02.799> co-work<00:20:03.440> and 00:20:03.669 --> 00:20:03.679 align:start position:0% a regular chat. Jump over to co-work and 00:20:03.679 --> 00:20:05.590 align:start position:0% a regular chat. Jump over to co-work and have<00:20:03.919> co-work<00:20:04.400> execute<00:20:04.799> it<00:20:05.039> and<00:20:05.200> it<00:20:05.360> will 00:20:05.590 --> 00:20:05.600 align:start position:0% have co-work execute it and it will 00:20:05.600 --> 00:20:07.190 align:start position:0% have co-work execute it and it will remember<00:20:05.840> what<00:20:06.080> you<00:20:06.240> chatted<00:20:06.640> about<00:20:06.799> in<00:20:07.039> a 00:20:07.190 --> 00:20:07.200 align:start position:0% remember what you chatted about in a 00:20:07.200 --> 00:20:09.190 align:start position:0% remember what you chatted about in a previous<00:20:07.679> chat.<00:20:08.080> By<00:20:08.320> default,<00:20:08.720> Claude<00:20:09.039> does 00:20:09.190 --> 00:20:09.200 align:start position:0% previous chat. By default, Claude does 00:20:09.200 --> 00:20:10.950 align:start position:0% previous chat. By default, Claude does not<00:20:09.360> store<00:20:09.600> topics<00:20:09.919> related<00:20:10.240> to<00:20:10.400> personal<00:20:10.720> or 00:20:10.950 --> 00:20:10.960 align:start position:0% not store topics related to personal or 00:20:10.960 --> 00:20:12.630 align:start position:0% not store topics related to personal or sensitive<00:20:11.440> subject<00:20:11.760> matter<00:20:12.080> like<00:20:12.320> health, 00:20:12.630 --> 00:20:12.640 align:start position:0% sensitive subject matter like health, 00:20:12.640 --> 00:20:14.230 align:start position:0% sensitive subject matter like health, race,<00:20:12.960> ethnicity,<00:20:13.520> religious<00:20:13.840> beliefs, 00:20:14.230 --> 00:20:14.240 align:start position:0% race, ethnicity, religious beliefs, 00:20:14.240 --> 00:20:16.789 align:start position:0% race, ethnicity, religious beliefs, politics,<00:20:14.960> etc.<00:20:15.520> But<00:20:15.679> you<00:20:15.919> can<00:20:16.080> go<00:20:16.320> in<00:20:16.559> and 00:20:16.789 --> 00:20:16.799 align:start position:0% politics, etc. But you can go in and 00:20:16.799 --> 00:20:18.950 align:start position:0% politics, etc. But you can go in and change<00:20:17.200> what<00:20:17.440> it<00:20:17.760> does<00:20:18.080> save<00:20:18.320> about<00:20:18.559> you<00:20:18.720> and 00:20:18.950 --> 00:20:18.960 align:start position:0% change what it does save about you and 00:20:18.960 --> 00:20:20.789 align:start position:0% change what it does save about you and what<00:20:19.200> you<00:20:19.360> don't<00:20:19.520> want<00:20:19.600> it<00:20:19.840> to<00:20:20.000> remember<00:20:20.480> about 00:20:20.789 --> 00:20:20.799 align:start position:0% what you don't want it to remember about 00:20:20.799 --> 00:20:22.630 align:start position:0% what you don't want it to remember about your<00:20:21.039> conversations.<00:20:21.840> Jumping<00:20:22.160> back<00:20:22.240> to<00:20:22.400> the 00:20:22.630 --> 00:20:22.640 align:start position:0% your conversations. Jumping back to the 00:20:22.640 --> 00:20:24.710 align:start position:0% your conversations. Jumping back to the conversation<00:20:23.039> about<00:20:23.360> AI<00:20:23.760> running<00:20:24.000> locally, 00:20:24.710 --> 00:20:24.720 align:start position:0% conversation about AI running locally, 00:20:24.720 --> 00:20:28.789 align:start position:0% conversation about AI running locally, Perplexity's<00:20:25.919> computer<00:20:26.799> now<00:20:27.120> has<00:20:27.679> a<00:20:28.159> portable 00:20:28.789 --> 00:20:28.799 align:start position:0% Perplexity's computer now has a portable 00:20:28.799 --> 00:20:30.950 align:start position:0% Perplexity's computer now has a portable computer<00:20:29.360> which<00:20:29.600> is<00:20:29.919> local.<00:20:30.320> So<00:20:30.480> the<00:20:30.720> model 00:20:30.950 --> 00:20:30.960 align:start position:0% computer which is local. So the model 00:20:30.960 --> 00:20:32.950 align:start position:0% computer which is local. So the model harness<00:20:31.520> conversation<00:20:32.000> and<00:20:32.159> trajectory<00:20:32.799> all 00:20:32.950 --> 00:20:32.960 align:start position:0% harness conversation and trajectory all 00:20:32.960 --> 00:20:34.630 align:start position:0% harness conversation and trajectory all live<00:20:33.200> on<00:20:33.280> the<00:20:33.440> user's<00:20:33.840> machine.<00:20:34.320> However, 00:20:34.630 --> 00:20:34.640 align:start position:0% live on the user's machine. However, 00:20:34.640 --> 00:20:36.149 align:start position:0% live on the user's machine. However, work<00:20:34.880> that<00:20:35.039> needs<00:20:35.280> the<00:20:35.440> outside<00:20:35.760> world<00:20:36.000> such 00:20:36.149 --> 00:20:36.159 align:start position:0% work that needs the outside world such 00:20:36.159 --> 00:20:37.909 align:start position:0% work that needs the outside world such as<00:20:36.320> web<00:20:36.559> search<00:20:36.880> connectors<00:20:37.200> or<00:20:37.440> escalation 00:20:37.909 --> 00:20:37.919 align:start position:0% as web search connectors or escalation 00:20:37.919 --> 00:20:39.830 align:start position:0% as web search connectors or escalation to<00:20:38.080> a<00:20:38.240> stronger<00:20:38.559> advisor<00:20:39.039> model<00:20:39.280> on<00:20:39.440> the<00:20:39.600> cloud 00:20:39.830 --> 00:20:39.840 align:start position:0% to a stronger advisor model on the cloud 00:20:39.840 --> 00:20:41.669 align:start position:0% to a stronger advisor model on the cloud is<00:20:40.080> invoked<00:20:40.480> only<00:20:40.720> when<00:20:40.960> necessary<00:20:41.440> and 00:20:41.669 --> 00:20:41.679 align:start position:0% is invoked only when necessary and 00:20:41.679 --> 00:20:43.830 align:start position:0% is invoked only when necessary and always<00:20:42.000> gated<00:20:42.400> by<00:20:42.559> the<00:20:42.720> user.<00:20:43.120> Local<00:20:43.440> models 00:20:43.830 --> 00:20:43.840 align:start position:0% always gated by the user. Local models 00:20:43.840 --> 00:20:46.149 align:start position:0% always gated by the user. Local models carry<00:20:44.159> no<00:20:44.320> inference<00:20:44.799> fee.<00:20:45.280> So<00:20:45.440> the<00:20:45.679> system<00:20:45.919> is 00:20:46.149 --> 00:20:46.159 align:start position:0% carry no inference fee. So the system is 00:20:46.159 --> 00:20:47.750 align:start position:0% carry no inference fee. So the system is private<00:20:46.480> and<00:20:46.720> cost-effective<00:20:47.440> by 00:20:47.750 --> 00:20:47.760 align:start position:0% private and cost-effective by 00:20:47.760 --> 00:20:49.750 align:start position:0% private and cost-effective by construction.<00:20:48.559> So<00:20:48.720> they're<00:20:48.960> using<00:20:49.440> small 00:20:49.750 --> 00:20:49.760 align:start position:0% construction. So they're using small 00:20:49.760 --> 00:20:52.310 align:start position:0% construction. So they're using small efficient<00:20:50.240> models<00:20:50.559> like<00:20:50.880> Nvidia's<00:20:51.360> Neotron, 00:20:52.310 --> 00:20:52.320 align:start position:0% efficient models like Nvidia's Neotron, 00:20:52.320 --> 00:20:55.510 align:start position:0% efficient models like Nvidia's Neotron, Quinn<00:20:52.720> 3.6,<00:20:53.679> Quinn<00:20:54.080> 3.8,<00:20:54.799> and<00:20:55.039> it<00:20:55.200> does<00:20:55.280> say 00:20:55.510 --> 00:20:55.520 align:start position:0% Quinn 3.6, Quinn 3.8, and it does say 00:20:55.520 --> 00:20:57.830 align:start position:0% Quinn 3.6, Quinn 3.8, and it does say systems<00:20:55.919> such<00:20:56.080> as<00:20:56.240> the<00:20:56.400> Nvidia<00:20:56.880> DGX<00:20:57.360> Spark<00:20:57.679> can 00:20:57.830 --> 00:20:57.840 align:start position:0% systems such as the Nvidia DGX Spark can 00:20:57.840 --> 00:21:00.149 align:start position:0% systems such as the Nvidia DGX Spark can now<00:20:58.080> run<00:20:58.240> these<00:20:58.480> models<00:20:58.799> locally.<00:20:59.520> So<00:21:00.000> you 00:21:00.149 --> 00:21:00.159 align:start position:0% now run these models locally. So you 00:21:00.159 --> 00:21:02.230 align:start position:0% now run these models locally. So you must<00:21:00.400> need<00:21:00.559> a<00:21:00.880> pretty<00:21:01.200> decent<00:21:01.679> system<00:21:01.919> to<00:21:02.159> be 00:21:02.230 --> 00:21:02.240 align:start position:0% must need a pretty decent system to be 00:21:02.240 --> 00:21:04.390 align:start position:0% must need a pretty decent system to be able<00:21:02.400> to<00:21:02.559> run<00:21:02.880> this<00:21:03.200> local<00:21:03.600> computer<00:21:04.000> model. 00:21:04.390 --> 00:21:04.400 align:start position:0% able to run this local computer model. 00:21:04.400 --> 00:21:05.830 align:start position:0% able to run this local computer model. Basically,<00:21:04.799> my<00:21:05.039> understanding<00:21:05.440> is<00:21:05.600> that 00:21:05.830 --> 00:21:05.840 align:start position:0% Basically, my understanding is that 00:21:05.840 --> 00:21:07.909 align:start position:0% Basically, my understanding is that Perplexity<00:21:06.640> built<00:21:06.960> their<00:21:07.120> own<00:21:07.280> version<00:21:07.520> of<00:21:07.679> an 00:21:07.909 --> 00:21:07.919 align:start position:0% Perplexity built their own version of an 00:21:07.919 --> 00:21:10.549 align:start position:0% Perplexity built their own version of an OpenClaw<00:21:08.640> or<00:21:08.960> Hermes<00:21:09.520> agent<00:21:09.919> that<00:21:10.159> will<00:21:10.320> just 00:21:10.549 --> 00:21:10.559 align:start position:0% OpenClaw or Hermes agent that will just 00:21:10.559 --> 00:21:12.710 align:start position:0% OpenClaw or Hermes agent that will just run<00:21:10.720> on<00:21:10.960> your<00:21:11.200> computer<00:21:11.679> and<00:21:11.919> do<00:21:12.240> tasks<00:21:12.559> that 00:21:12.710 --> 00:21:12.720 align:start position:0% run on your computer and do tasks that 00:21:12.720 --> 00:21:14.230 align:start position:0% run on your computer and do tasks that you<00:21:12.880> need<00:21:12.960> it<00:21:13.120> to<00:21:13.200> do<00:21:13.360> on<00:21:13.520> your<00:21:13.679> computer.<00:21:14.000> It 00:21:14.230 --> 00:21:14.240 align:start position:0% you need it to do on your computer. It 00:21:14.240 --> 00:21:16.549 align:start position:0% you need it to do on your computer. It will<00:21:14.480> run<00:21:14.880> local<00:21:15.200> models.<00:21:15.760> It<00:21:16.000> will<00:21:16.159> go<00:21:16.320> off 00:21:16.549 --> 00:21:16.559 align:start position:0% will run local models. It will go off 00:21:16.559 --> 00:21:18.549 align:start position:0% will run local models. It will go off and<00:21:16.720> use<00:21:16.960> cloud<00:21:17.280> models<00:21:17.600> when<00:21:17.919> necessary,<00:21:18.400> but 00:21:18.549 --> 00:21:18.559 align:start position:0% and use cloud models when necessary, but 00:21:18.559 --> 00:21:20.070 align:start position:0% and use cloud models when necessary, but it'll<00:21:18.799> ask<00:21:18.960> your<00:21:19.120> permission<00:21:19.440> first.<00:21:19.919> But 00:21:20.070 --> 00:21:20.080 align:start position:0% it'll ask your permission first. But 00:21:20.080 --> 00:21:22.630 align:start position:0% it'll ask your permission first. But it's<00:21:20.240> kind<00:21:20.400> of<00:21:20.559> designed<00:21:20.960> for<00:21:21.520> really<00:21:22.000> decent 00:21:22.630 --> 00:21:22.640 align:start position:0% it's kind of designed for really decent 00:21:22.640 --> 00:21:24.710 align:start position:0% it's kind of designed for really decent computers<00:21:23.120> that<00:21:23.440> have<00:21:23.600> a<00:21:23.760> lot<00:21:23.919> of<00:21:24.240> compute 00:21:24.710 --> 00:21:24.720 align:start position:0% computers that have a lot of compute 00:21:24.720 --> 00:21:26.549 align:start position:0% computers that have a lot of compute capacity,<00:21:25.360> seeing<00:21:25.600> as<00:21:25.760> they<00:21:25.919> called<00:21:26.159> out<00:21:26.320> a 00:21:26.549 --> 00:21:26.559 align:start position:0% capacity, seeing as they called out a 00:21:26.559 --> 00:21:29.190 align:start position:0% capacity, seeing as they called out a DGX<00:21:27.200> Spark,<00:21:27.600> which<00:21:27.840> is,<00:21:28.080> you<00:21:28.159> know,<00:21:28.480> a<00:21:28.720> roughly 00:21:29.190 --> 00:21:29.200 align:start position:0% DGX Spark, which is, you know, a roughly 00:21:29.200 --> 00:21:32.870 align:start position:0% DGX Spark, which is, you know, a roughly $4,000<00:21:30.240> box<00:21:30.559> for<00:21:31.200> 128<00:21:31.600> GB<00:21:32.000> of<00:21:32.080> VRAM.<00:21:32.559> So,<00:21:32.720> not 00:21:32.870 --> 00:21:32.880 align:start position:0% $4,000 box for 128 GB of VRAM. So, not 00:21:32.880 --> 00:21:35.110 align:start position:0% $4,000 box for 128 GB of VRAM. So, not quite<00:21:33.200> accessible<00:21:33.679> to<00:21:34.000> everybody<00:21:34.559> yet,<00:21:34.880> but 00:21:35.110 --> 00:21:35.120 align:start position:0% quite accessible to everybody yet, but 00:21:35.120 --> 00:21:37.510 align:start position:0% quite accessible to everybody yet, but like<00:21:35.440> this<00:21:35.679> is<00:21:35.760> their<00:21:36.080> local<00:21:36.480> version<00:21:36.799> of<00:21:37.120> a 00:21:37.510 --> 00:21:37.520 align:start position:0% like this is their local version of a 00:21:37.520 --> 00:21:40.230 align:start position:0% like this is their local version of a openclaw<00:21:38.080> Hermes<00:21:38.720> kind<00:21:38.960> of<00:21:39.280> agent<00:21:39.760> harness 00:21:40.230 --> 00:21:40.240 align:start position:0% openclaw Hermes kind of agent harness 00:21:40.240 --> 00:21:42.230 align:start position:0% openclaw Hermes kind of agent harness thing.<00:21:40.640> Let's<00:21:40.880> talk<00:21:40.960> about<00:21:41.200> AI<00:21:41.600> music<00:21:41.919> for<00:21:42.080> a 00:21:42.230 --> 00:21:42.240 align:start position:0% thing. Let's talk about AI music for a 00:21:42.240 --> 00:21:44.390 align:start position:0% thing. Let's talk about AI music for a second.<00:21:42.559> Dr.<00:21:42.880> Andre<00:21:43.280> admitted<00:21:43.679> that<00:21:43.919> he<00:21:44.080> uses 00:21:44.390 --> 00:21:44.400 align:start position:0% second. Dr. Andre admitted that he uses 00:21:44.400 --> 00:21:46.950 align:start position:0% second. Dr. Andre admitted that he uses AI<00:21:44.799> to<00:21:44.960> produce<00:21:45.280> songs,<00:21:45.760> which<00:21:46.000> is<00:21:46.159> a<00:21:46.559> very 00:21:46.950 --> 00:21:46.960 align:start position:0% AI to produce songs, which is a very 00:21:46.960 --> 00:21:49.029 align:start position:0% AI to produce songs, which is a very risky<00:21:47.440> thing<00:21:47.600> for<00:21:47.840> an<00:21:48.080> artist<00:21:48.400> to<00:21:48.640> do<00:21:48.799> these 00:21:49.029 --> 00:21:49.039 align:start position:0% risky thing for an artist to do these 00:21:49.039 --> 00:21:50.630 align:start position:0% risky thing for an artist to do these days.<00:21:49.440> He<00:21:49.600> said,<00:21:49.679> "I<00:21:50.000> don't<00:21:50.080> see<00:21:50.240> it<00:21:50.320> as<00:21:50.480> a 00:21:50.630 --> 00:21:50.640 align:start position:0% days. He said, "I don't see it as a 00:21:50.640 --> 00:21:52.549 align:start position:0% days. He said, "I don't see it as a threat.<00:21:50.960> I<00:21:51.200> think<00:21:51.360> the<00:21:51.600> only<00:21:51.840> people<00:21:52.080> that<00:21:52.400> see 00:21:52.549 --> 00:21:52.559 align:start position:0% threat. I think the only people that see 00:21:52.559 --> 00:21:54.149 align:start position:0% threat. I think the only people that see it<00:21:52.720> as<00:21:52.799> a<00:21:52.960> threat<00:21:53.200> are<00:21:53.360> the<00:21:53.600> people<00:21:53.679> who<00:21:53.919> have 00:21:54.149 --> 00:21:54.159 align:start position:0% it as a threat are the people who have 00:21:54.159 --> 00:21:55.909 align:start position:0% it as a threat are the people who have trouble<00:21:54.640> creating."<00:21:55.200> I<00:21:55.360> had<00:21:55.520> a<00:21:55.679> discussion 00:21:55.909 --> 00:21:55.919 align:start position:0% trouble creating." I had a discussion 00:21:55.919 --> 00:21:57.590 align:start position:0% trouble creating." I had a discussion with<00:21:56.080> a<00:21:56.320> few<00:21:56.400> people<00:21:56.559> a<00:21:56.799> few<00:21:56.880> days<00:21:57.039> ago.<00:21:57.360> They 00:21:57.590 --> 00:21:57.600 align:start position:0% with a few people a few days ago. They 00:21:57.600 --> 00:21:59.909 align:start position:0% with a few people a few days ago. They were<00:21:57.760> against<00:21:58.080> AI.<00:21:58.640> And<00:21:58.799> I'm<00:21:58.960> like,<00:21:59.280> okay,<00:21:59.760> you 00:21:59.909 --> 00:21:59.919 align:start position:0% were against AI. And I'm like, okay, you 00:21:59.919 --> 00:22:01.190 align:start position:0% were against AI. And I'm like, okay, you sound<00:22:00.159> like<00:22:00.320> the<00:22:00.480> person<00:22:00.640> that<00:22:00.880> would<00:22:01.039> have 00:22:01.190 --> 00:22:01.200 align:start position:0% sound like the person that would have 00:22:01.200 --> 00:22:02.870 align:start position:0% sound like the person that would have been<00:22:01.360> against<00:22:01.679> the<00:22:01.840> drum<00:22:02.159> machine<00:22:02.480> when<00:22:02.720> it 00:22:02.870 --> 00:22:02.880 align:start position:0% been against the drum machine when it 00:22:02.880 --> 00:22:04.870 align:start position:0% been against the drum machine when it came<00:22:02.960> out<00:22:03.200> or<00:22:03.440> synthesizers<00:22:04.159> right<00:22:04.400> now.<00:22:04.559> I<00:22:04.720> do 00:22:04.870 --> 00:22:04.880 align:start position:0% came out or synthesizers right now. I do 00:22:04.880 --> 00:22:07.350 align:start position:0% came out or synthesizers right now. I do have<00:22:04.960> my<00:22:05.200> own<00:22:05.360> take<00:22:05.600> on<00:22:05.840> AI<00:22:06.320> music.<00:22:06.720> And<00:22:06.880> I 00:22:07.350 --> 00:22:07.360 align:start position:0% have my own take on AI music. And I 00:22:07.360 --> 00:22:09.750 align:start position:0% have my own take on AI music. And I agree<00:22:07.679> with<00:22:07.919> Dr.<00:22:08.240> Dre.<00:22:08.559> I<00:22:08.799> think<00:22:08.960> AI<00:22:09.360> is<00:22:09.520> a 00:22:09.750 --> 00:22:09.760 align:start position:0% agree with Dr. Dre. I think AI is a 00:22:09.760 --> 00:22:12.149 align:start position:0% agree with Dr. Dre. I think AI is a great<00:22:09.919> tool<00:22:10.240> to<00:22:10.480> assist<00:22:10.880> with<00:22:11.120> music.<00:22:11.600> Where<00:22:11.919> I 00:22:12.149 --> 00:22:12.159 align:start position:0% great tool to assist with music. Where I 00:22:12.159 --> 00:22:13.830 align:start position:0% great tool to assist with music. Where I think<00:22:12.240> the<00:22:12.559> line<00:22:12.880> should<00:22:13.039> be<00:22:13.200> drawn<00:22:13.440> and<00:22:13.600> where 00:22:13.830 --> 00:22:13.840 align:start position:0% think the line should be drawn and where 00:22:13.840 --> 00:22:15.909 align:start position:0% think the line should be drawn and where I'm<00:22:14.000> not<00:22:14.080> a<00:22:14.240> fan<00:22:14.400> of<00:22:14.480> AI<00:22:14.880> music<00:22:15.200> is<00:22:15.440> just<00:22:15.679> like 00:22:15.909 --> 00:22:15.919 align:start position:0% I'm not a fan of AI music is just like 00:22:15.919 --> 00:22:18.230 align:start position:0% I'm not a fan of AI music is just like prompting<00:22:16.320> a<00:22:16.559> whole<00:22:16.799> song<00:22:17.120> into<00:22:17.440> existence, 00:22:18.230 --> 00:22:18.240 align:start position:0% prompting a whole song into existence, 00:22:18.240 --> 00:22:20.070 align:start position:0% prompting a whole song into existence, right?<00:22:18.480> Like<00:22:18.640> going<00:22:18.880> to<00:22:19.039> Sunno,<00:22:19.600> creating<00:22:19.840> a 00:22:20.070 --> 00:22:20.080 align:start position:0% right? Like going to Sunno, creating a 00:22:20.080 --> 00:22:22.310 align:start position:0% right? Like going to Sunno, creating a song<00:22:20.320> that<00:22:20.720> sounds<00:22:21.039> like<00:22:21.280> any<00:22:21.520> other<00:22:21.840> band, 00:22:22.310 --> 00:22:22.320 align:start position:0% song that sounds like any other band, 00:22:22.320 --> 00:22:24.149 align:start position:0% song that sounds like any other band, and<00:22:22.480> then<00:22:22.640> putting<00:22:22.880> it<00:22:22.960> up<00:22:23.120> on<00:22:23.360> Spotify<00:22:23.840> and 00:22:24.149 --> 00:22:24.159 align:start position:0% and then putting it up on Spotify and 00:22:24.159 --> 00:22:26.070 align:start position:0% and then putting it up on Spotify and saying,<00:22:24.320> "I<00:22:24.640> created<00:22:24.960> this."<00:22:25.360> No,<00:22:25.679> you<00:22:25.840> just 00:22:26.070 --> 00:22:26.080 align:start position:0% saying, "I created this." No, you just 00:22:26.080 --> 00:22:28.149 align:start position:0% saying, "I created this." No, you just prompted<00:22:26.559> that<00:22:26.880> song.<00:22:27.280> However,<00:22:27.760> I've<00:22:28.000> played 00:22:28.149 --> 00:22:28.159 align:start position:0% prompted that song. However, I've played 00:22:28.159 --> 00:22:29.750 align:start position:0% prompted that song. However, I've played around<00:22:28.400> with<00:22:28.640> Sunno<00:22:29.039> a<00:22:29.120> lot.<00:22:29.440> I<00:22:29.600> actually 00:22:29.750 --> 00:22:29.760 align:start position:0% around with Sunno a lot. I actually 00:22:29.760 --> 00:22:31.350 align:start position:0% around with Sunno a lot. I actually think<00:22:29.840> it's<00:22:30.080> a<00:22:30.320> really,<00:22:30.559> really<00:22:30.799> fun<00:22:31.039> tool. 00:22:31.350 --> 00:22:31.360 align:start position:0% think it's a really, really fun tool. 00:22:31.360 --> 00:22:33.350 align:start position:0% think it's a really, really fun tool. It's<00:22:31.520> a<00:22:31.679> blast<00:22:31.840> to<00:22:32.080> make<00:22:32.240> silly<00:22:32.640> songs<00:22:32.880> for<00:22:33.120> my 00:22:33.350 --> 00:22:33.360 align:start position:0% It's a blast to make silly songs for my 00:22:33.360 --> 00:22:35.190 align:start position:0% It's a blast to make silly songs for my own<00:22:33.520> personal<00:22:33.840> use<00:22:34.159> and<00:22:34.559> listen<00:22:34.799> to<00:22:34.880> them<00:22:35.039> and 00:22:35.190 --> 00:22:35.200 align:start position:0% own personal use and listen to them and 00:22:35.200 --> 00:22:36.710 align:start position:0% own personal use and listen to them and play<00:22:35.440> them<00:22:35.520> for<00:22:35.679> my<00:22:35.840> family<00:22:36.080> and<00:22:36.240> we<00:22:36.480> laugh 00:22:36.710 --> 00:22:36.720 align:start position:0% play them for my family and we laugh 00:22:36.720 --> 00:22:38.070 align:start position:0% play them for my family and we laugh about<00:22:36.880> it.<00:22:37.120> But<00:22:37.280> I'm<00:22:37.440> not<00:22:37.520> a<00:22:37.679> big<00:22:37.760> fan<00:22:37.919> of 00:22:38.070 --> 00:22:38.080 align:start position:0% about it. But I'm not a big fan of 00:22:38.080 --> 00:22:39.590 align:start position:0% about it. But I'm not a big fan of publishing<00:22:38.480> them<00:22:38.720> and<00:22:39.039> trying<00:22:39.200> to<00:22:39.360> fool 00:22:39.590 --> 00:22:39.600 align:start position:0% publishing them and trying to fool 00:22:39.600 --> 00:22:41.190 align:start position:0% publishing them and trying to fool people<00:22:39.760> into<00:22:40.000> thinking<00:22:40.240> that<00:22:40.400> they're<00:22:40.720> real. 00:22:41.190 --> 00:22:41.200 align:start position:0% people into thinking that they're real. 00:22:41.200 --> 00:22:42.870 align:start position:0% people into thinking that they're real. Something<00:22:41.440> that<00:22:41.679> is<00:22:42.159> really,<00:22:42.400> really<00:22:42.640> fun 00:22:42.870 --> 00:22:42.880 align:start position:0% Something that is really, really fun 00:22:42.880 --> 00:22:44.950 align:start position:0% Something that is really, really fun though<00:22:42.960> is<00:22:43.200> I've<00:22:43.440> grabbed<00:22:43.679> my<00:22:43.919> guitars<00:22:44.400> before 00:22:44.950 --> 00:22:44.960 align:start position:0% though is I've grabbed my guitars before 00:22:44.960 --> 00:22:46.549 align:start position:0% though is I've grabbed my guitars before and<00:22:45.200> started<00:22:45.360> to<00:22:45.520> play<00:22:45.679> like<00:22:45.840> a<00:22:46.000> little<00:22:46.159> riff, 00:22:46.549 --> 00:22:46.559 align:start position:0% and started to play like a little riff, 00:22:46.559 --> 00:22:49.270 align:start position:0% and started to play like a little riff, put<00:22:46.720> that<00:22:46.880> into<00:22:47.840> Sunno<00:22:48.320> play<00:22:48.480> drums<00:22:48.880> over<00:22:49.120> the 00:22:49.270 --> 00:22:49.280 align:start position:0% put that into Sunno play drums over the 00:22:49.280 --> 00:22:50.870 align:start position:0% put that into Sunno play drums over the riff<00:22:49.520> that<00:22:49.679> I<00:22:49.840> made.<00:22:50.159> Now<00:22:50.320> it's<00:22:50.559> like<00:22:50.640> a 00:22:50.870 --> 00:22:50.880 align:start position:0% riff that I made. Now it's like a 00:22:50.880 --> 00:22:52.870 align:start position:0% riff that I made. Now it's like a collaborative<00:22:51.440> thing<00:22:51.679> between<00:22:52.000> me<00:22:52.159> and<00:22:52.400> AI. 00:22:52.870 --> 00:22:52.880 align:start position:0% collaborative thing between me and AI. 00:22:52.880 --> 00:22:54.470 align:start position:0% collaborative thing between me and AI. And<00:22:53.039> that's<00:22:53.360> really<00:22:53.600> really<00:22:53.919> fun.<00:22:54.159> So<00:22:54.320> I 00:22:54.470 --> 00:22:54.480 align:start position:0% And that's really really fun. So I 00:22:54.480 --> 00:22:55.990 align:start position:0% And that's really really fun. So I definitely<00:22:54.799> think<00:22:54.880> there's<00:22:55.120> like<00:22:55.440> levels<00:22:55.760> to 00:22:55.990 --> 00:22:56.000 align:start position:0% definitely think there's like levels to 00:22:56.000 --> 00:22:58.230 align:start position:0% definitely think there's like levels to AI<00:22:56.400> music.<00:22:56.799> And<00:22:57.120> I<00:22:57.280> think<00:22:57.440> just<00:22:57.679> prompting<00:22:58.000> a 00:22:58.230 --> 00:22:58.240 align:start position:0% AI music. And I think just prompting a 00:22:58.240 --> 00:22:59.909 align:start position:0% AI music. And I think just prompting a song<00:22:58.400> into<00:22:58.720> existence<00:22:59.200> and<00:22:59.440> saying,<00:22:59.600> "Look, 00:22:59.909 --> 00:22:59.919 align:start position:0% song into existence and saying, "Look, 00:22:59.919 --> 00:23:02.789 align:start position:0% song into existence and saying, "Look, I'm<00:23:00.080> a<00:23:00.240> musician<00:23:00.720> now." 00:23:02.789 --> 00:23:02.799 align:start position:0% I'm a musician now." 00:23:02.799 --> 00:23:04.950 align:start position:0% I'm a musician now." I<00:23:03.039> don't<00:23:03.200> know<00:23:03.280> about<00:23:03.440> that.<00:23:03.760> but<00:23:04.080> using<00:23:04.480> AI 00:23:04.950 --> 00:23:04.960 align:start position:0% I don't know about that. but using AI 00:23:04.960 --> 00:23:07.590 align:start position:0% I don't know about that. but using AI tools<00:23:05.280> to<00:23:05.600> assist<00:23:06.000> in<00:23:06.480> making<00:23:06.880> cool<00:23:07.200> music 00:23:07.590 --> 00:23:07.600 align:start position:0% tools to assist in making cool music 00:23:07.600 --> 00:23:09.909 align:start position:0% tools to assist in making cool music where<00:23:07.840> it's<00:23:08.080> like<00:23:08.559> a<00:23:08.799> collaborator<00:23:09.440> with<00:23:09.600> you. 00:23:09.909 --> 00:23:09.919 align:start position:0% where it's like a collaborator with you. 00:23:09.919 --> 00:23:11.110 align:start position:0% where it's like a collaborator with you. I'm<00:23:10.240> actually<00:23:10.400> pretty<00:23:10.640> cool<00:23:10.720> with<00:23:10.880> that. 00:23:11.110 --> 00:23:11.120 align:start position:0% I'm actually pretty cool with that. 00:23:11.120 --> 00:23:12.390 align:start position:0% I'm actually pretty cool with that. That's<00:23:11.280> just<00:23:11.440> my<00:23:11.520> take.<00:23:11.760> And<00:23:11.919> speaking<00:23:12.159> of 00:23:12.390 --> 00:23:12.400 align:start position:0% That's just my take. And speaking of 00:23:12.400 --> 00:23:14.149 align:start position:0% That's just my take. And speaking of music,<00:23:12.880> this<00:23:13.039> is<00:23:13.200> really<00:23:13.440> interesting.<00:23:13.919> The 00:23:14.149 --> 00:23:14.159 align:start position:0% music, this is really interesting. The 00:23:14.159 --> 00:23:16.149 align:start position:0% music, this is really interesting. The company<00:23:14.400> Stability<00:23:14.960> AI<00:23:15.360> just<00:23:15.600> raised<00:23:15.840> a<00:23:16.000> new 00:23:16.149 --> 00:23:16.159 align:start position:0% company Stability AI just raised a new 00:23:16.159 --> 00:23:18.230 align:start position:0% company Stability AI just raised a new round<00:23:16.320> of<00:23:16.559> funding<00:23:16.880> and<00:23:17.120> they<00:23:17.360> actually<00:23:17.760> have 00:23:18.230 --> 00:23:18.240 align:start position:0% round of funding and they actually have 00:23:18.240 --> 00:23:21.350 align:start position:0% round of funding and they actually have music<00:23:18.799> generators<00:23:19.760> under<00:23:20.159> their<00:23:20.799> umbrella<00:23:21.200> of 00:23:21.350 --> 00:23:21.360 align:start position:0% music generators under their umbrella of 00:23:21.360 --> 00:23:23.029 align:start position:0% music generators under their umbrella of tools<00:23:21.679> they've<00:23:22.000> built.<00:23:22.240> And<00:23:22.400> the<00:23:22.640> investors 00:23:23.029 --> 00:23:23.039 align:start position:0% tools they've built. And the investors 00:23:23.039 --> 00:23:25.350 align:start position:0% tools they've built. And the investors that<00:23:23.360> just<00:23:23.600> invested<00:23:24.240> are<00:23:24.480> comprised<00:23:24.960> of 00:23:25.350 --> 00:23:25.360 align:start position:0% that just invested are comprised of 00:23:25.360 --> 00:23:27.750 align:start position:0% that just invested are comprised of Electronic<00:23:26.000> Arts,<00:23:26.640> Sony<00:23:27.039> Music<00:23:27.360> Group, 00:23:27.750 --> 00:23:27.760 align:start position:0% Electronic Arts, Sony Music Group, 00:23:27.760 --> 00:23:29.669 align:start position:0% Electronic Arts, Sony Music Group, Universal<00:23:28.240> Music<00:23:28.559> Group,<00:23:28.960> Warner<00:23:29.360> Music 00:23:29.669 --> 00:23:29.679 align:start position:0% Universal Music Group, Warner Music 00:23:29.679 --> 00:23:31.510 align:start position:0% Universal Music Group, Warner Music Group,<00:23:30.080> and<00:23:30.320> more.<00:23:30.720> So,<00:23:30.880> I<00:23:31.039> think<00:23:31.120> this<00:23:31.360> kind 00:23:31.510 --> 00:23:31.520 align:start position:0% Group, and more. So, I think this kind 00:23:31.520 --> 00:23:34.230 align:start position:0% Group, and more. So, I think this kind of<00:23:31.679> tells<00:23:31.919> us<00:23:32.080> that<00:23:32.559> the<00:23:32.880> music<00:23:33.280> industry,<00:23:33.919> the 00:23:34.230 --> 00:23:34.240 align:start position:0% of tells us that the music industry, the 00:23:34.240 --> 00:23:36.950 align:start position:0% of tells us that the music industry, the big<00:23:34.799> studios,<00:23:35.440> aren't<00:23:35.760> necessarily<00:23:36.480> against 00:23:36.950 --> 00:23:36.960 align:start position:0% big studios, aren't necessarily against 00:23:36.960 --> 00:23:39.510 align:start position:0% big studios, aren't necessarily against AI.<00:23:37.520> They're<00:23:37.840> actively<00:23:38.559> investing<00:23:39.039> in<00:23:39.280> it. 00:23:39.510 --> 00:23:39.520 align:start position:0% AI. They're actively investing in it. 00:23:39.520 --> 00:23:41.029 align:start position:0% AI. They're actively investing in it. They<00:23:39.760> just,<00:23:40.080> you<00:23:40.240> know,<00:23:40.400> don't<00:23:40.640> want<00:23:40.720> to<00:23:40.880> be 00:23:41.029 --> 00:23:41.039 align:start position:0% They just, you know, don't want to be 00:23:41.039 --> 00:23:43.669 align:start position:0% They just, you know, don't want to be cut<00:23:41.280> out<00:23:41.440> of<00:23:41.520> the<00:23:41.679> loop<00:23:41.919> of<00:23:42.320> making<00:23:42.799> money<00:23:43.280> on 00:23:43.669 --> 00:23:43.679 align:start position:0% cut out of the loop of making money on 00:23:43.679 --> 00:23:45.990 align:start position:0% cut out of the loop of making money on AI<00:23:44.159> music.<00:23:44.720> Time<00:23:45.039> magazine<00:23:45.440> released<00:23:45.760> their 00:23:45.990 --> 00:23:46.000 align:start position:0% AI music. Time magazine released their 00:23:46.000 --> 00:23:48.470 align:start position:0% AI music. Time magazine released their list<00:23:46.159> of<00:23:46.480> 100<00:23:46.960> most<00:23:47.280> influential<00:23:47.919> people<00:23:48.240> at 00:23:48.470 --> 00:23:48.480 align:start position:0% list of 100 most influential people at 00:23:48.480 --> 00:23:50.526 align:start position:0% list of 100 most influential people at AI,<00:23:48.960> and<00:23:49.200> it's<00:23:49.360> an<00:23:49.600> absolute<00:23:50.240> joke. 00:23:50.526 --> 00:23:50.536 align:start position:0% AI, and it's an absolute joke. 00:23:50.536 --> 00:23:51.110 align:start position:0% AI, and it's an absolute joke. [laughter] 00:23:51.110 --> 00:23:51.120 align:start position:0% [laughter] 00:23:51.120 --> 00:23:53.110 align:start position:0% [laughter] Now,<00:23:51.440> don't<00:23:51.679> get<00:23:51.840> me<00:23:51.919> wrong,<00:23:52.320> there's<00:23:52.720> a<00:23:52.960> ton 00:23:53.110 --> 00:23:53.120 align:start position:0% Now, don't get me wrong, there's a ton 00:23:53.120 --> 00:23:55.029 align:start position:0% Now, don't get me wrong, there's a ton of<00:23:53.280> people<00:23:53.520> that<00:23:53.679> I<00:23:53.919> do<00:23:54.080> think<00:23:54.320> deserve<00:23:54.720> to<00:23:54.880> be 00:23:55.029 --> 00:23:55.039 align:start position:0% of people that I do think deserve to be 00:23:55.039 --> 00:23:56.630 align:start position:0% of people that I do think deserve to be on<00:23:55.280> this<00:23:55.520> list.<00:23:55.840> I<00:23:56.080> definitely<00:23:56.320> think<00:23:56.480> the 00:23:56.630 --> 00:23:56.640 align:start position:0% on this list. I definitely think the 00:23:56.640 --> 00:23:59.669 align:start position:0% on this list. I definitely think the OpenAI<00:23:57.280> team,<00:23:57.600> Elon<00:23:58.000> Musk,<00:23:58.480> Daario,<00:23:59.280> Peter 00:23:59.669 --> 00:23:59.679 align:start position:0% OpenAI team, Elon Musk, Daario, Peter 00:23:59.679 --> 00:24:02.870 align:start position:0% OpenAI team, Elon Musk, Daario, Peter Steinberger,<00:24:00.640> Mikey<00:24:01.120> Scholamman,<00:24:01.840> Fay<00:24:02.400> Lee, 00:24:02.870 --> 00:24:02.880 align:start position:0% Steinberger, Mikey Scholamman, Fay Lee, 00:24:02.880 --> 00:24:05.350 align:start position:0% Steinberger, Mikey Scholamman, Fay Lee, Ilia<00:24:03.360> Suskiver,<00:24:04.080> Mirror<00:24:04.400> Morati,<00:24:05.039> these<00:24:05.280> are 00:24:05.350 --> 00:24:05.360 align:start position:0% Ilia Suskiver, Mirror Morati, these are 00:24:05.360 --> 00:24:06.870 align:start position:0% Ilia Suskiver, Mirror Morati, these are all<00:24:05.600> people<00:24:05.840> that<00:24:06.000> I<00:24:06.240> think<00:24:06.400> absolutely 00:24:06.870 --> 00:24:06.880 align:start position:0% all people that I think absolutely 00:24:06.880 --> 00:24:08.950 align:start position:0% all people that I think absolutely deserve<00:24:07.200> to<00:24:07.360> be<00:24:07.440> on<00:24:07.600> that<00:24:07.760> list.<00:24:08.240> However, 00:24:08.950 --> 00:24:08.960 align:start position:0% deserve to be on that list. However, 00:24:08.960 --> 00:24:11.269 align:start position:0% deserve to be on that list. However, Jensen<00:24:09.440> Hong,<00:24:10.000> the<00:24:10.240> person<00:24:10.400> who's<00:24:10.960> making 00:24:11.269 --> 00:24:11.279 align:start position:0% Jensen Hong, the person who's making 00:24:11.279 --> 00:24:13.269 align:start position:0% Jensen Hong, the person who's making this<00:24:11.600> happen<00:24:12.080> through<00:24:12.320> all<00:24:12.480> of<00:24:12.640> this<00:24:12.880> compute 00:24:13.269 --> 00:24:13.279 align:start position:0% this happen through all of this compute 00:24:13.279 --> 00:24:14.630 align:start position:0% this happen through all of this compute that<00:24:13.440> he's<00:24:13.679> providing<00:24:13.919> to<00:24:14.080> all<00:24:14.320> of<00:24:14.400> these 00:24:14.630 --> 00:24:14.640 align:start position:0% that he's providing to all of these 00:24:14.640 --> 00:24:16.070 align:start position:0% that he's providing to all of these companies,<00:24:15.200> one<00:24:15.360> of<00:24:15.440> the<00:24:15.600> people<00:24:15.760> that's 00:24:16.070 --> 00:24:16.080 align:start position:0% companies, one of the people that's 00:24:16.080 --> 00:24:18.470 align:start position:0% companies, one of the people that's probably<00:24:16.559> shaped<00:24:17.039> the<00:24:17.360> like<00:24:17.600> AI<00:24:18.000> revolution 00:24:18.470 --> 00:24:18.480 align:start position:0% probably shaped the like AI revolution 00:24:18.480 --> 00:24:21.430 align:start position:0% probably shaped the like AI revolution the<00:24:18.720> most.<00:24:19.120> Deis<00:24:19.520> Habibus,<00:24:20.159> the<00:24:20.320> ex<00:24:20.720> CEO<00:24:21.200> of 00:24:21.430 --> 00:24:21.440 align:start position:0% the most. Deis Habibus, the ex CEO of 00:24:21.440 --> 00:24:23.669 align:start position:0% the most. Deis Habibus, the ex CEO of DeepMind,<00:24:22.080> who<00:24:22.400> literally<00:24:22.720> has<00:24:22.960> a<00:24:23.120> Nobel 00:24:23.669 --> 00:24:23.679 align:start position:0% DeepMind, who literally has a Nobel 00:24:23.679 --> 00:24:26.310 align:start position:0% DeepMind, who literally has a Nobel Prize<00:24:24.080> for<00:24:24.320> his<00:24:24.559> AI<00:24:24.960> with<00:24:25.120> AlphaFold.<00:24:25.919> Andre 00:24:26.310 --> 00:24:26.320 align:start position:0% Prize for his AI with AlphaFold. Andre 00:24:26.320 --> 00:24:28.470 align:start position:0% Prize for his AI with AlphaFold. Andre Carpathy<00:24:27.039> who's<00:24:27.279> literally<00:24:27.679> the<00:24:28.000> most 00:24:28.470 --> 00:24:28.480 align:start position:0% Carpathy who's literally the most 00:24:28.480 --> 00:24:32.070 align:start position:0% Carpathy who's literally the most followed<00:24:29.039> voice<00:24:29.440> on<00:24:29.840> X<00:24:30.559> around<00:24:31.039> AI<00:24:31.600> and<00:24:31.840> even 00:24:32.070 --> 00:24:32.080 align:start position:0% followed voice on X around AI and even 00:24:32.080 --> 00:24:34.390 align:start position:0% followed voice on X around AI and even like<00:24:32.400> Mark<00:24:32.720> Zuckerberg<00:24:33.279> who's<00:24:33.600> trying<00:24:33.919> to<00:24:34.159> be 00:24:34.390 --> 00:24:34.400 align:start position:0% like Mark Zuckerberg who's trying to be 00:24:34.400 --> 00:24:37.669 align:start position:0% like Mark Zuckerberg who's trying to be like<00:24:34.720> the<00:24:35.039> voice<00:24:35.520> of<00:24:35.919> openweight<00:24:36.799> models<00:24:37.360> and 00:24:37.669 --> 00:24:37.679 align:start position:0% like the voice of openweight models and 00:24:37.679 --> 00:24:39.590 align:start position:0% like the voice of openweight models and push<00:24:37.919> that<00:24:38.080> forward.<00:24:38.640> All<00:24:38.799> of<00:24:38.880> these<00:24:39.200> people 00:24:39.590 --> 00:24:39.600 align:start position:0% push that forward. All of these people 00:24:39.600 --> 00:24:41.830 align:start position:0% push that forward. All of these people are<00:24:39.840> like<00:24:40.159> pretty<00:24:40.559> influential<00:24:41.279> and<00:24:41.600> they 00:24:41.830 --> 00:24:41.840 align:start position:0% are like pretty influential and they 00:24:41.840 --> 00:24:44.870 align:start position:0% are like pretty influential and they didn't<00:24:42.159> make<00:24:42.400> the<00:24:42.559> list<00:24:43.039> yet<00:24:43.600> somehow<00:24:44.480> Paris 00:24:44.870 --> 00:24:44.880 align:start position:0% didn't make the list yet somehow Paris 00:24:44.880 --> 00:24:47.430 align:start position:0% didn't make the list yet somehow Paris Hilton<00:24:45.279> is<00:24:45.440> on<00:24:45.600> the<00:24:45.760> list.<00:24:46.240> Joseph<00:24:46.640> Gordon<00:24:47.039> Lev 00:24:47.430 --> 00:24:47.440 align:start position:0% Hilton is on the list. Joseph Gordon Lev 00:24:47.440 --> 00:24:50.070 align:start position:0% Hilton is on the list. Joseph Gordon Lev is<00:24:47.600> on<00:24:47.760> the<00:24:47.840> list.<00:24:48.159> Bernie<00:24:48.640> Sanders<00:24:49.360> is<00:24:49.600> on<00:24:49.840> the 00:24:50.070 --> 00:24:50.080 align:start position:0% is on the list. Bernie Sanders is on the 00:24:50.080 --> 00:24:52.950 align:start position:0% is on the list. Bernie Sanders is on the list.<00:24:50.559> Like<00:24:50.960> what?<00:24:51.679> And<00:24:51.919> the<00:24:52.159> reason<00:24:52.400> Paris 00:24:52.950 --> 00:24:52.960 align:start position:0% list. Like what? And the reason Paris 00:24:52.960 --> 00:24:54.630 align:start position:0% list. Like what? And the reason Paris Hilton<00:24:53.360> is<00:24:53.440> on<00:24:53.600> the<00:24:53.679> list<00:24:53.840> is<00:24:54.000> that<00:24:54.159> she's<00:24:54.400> an 00:24:54.630 --> 00:24:54.640 align:start position:0% Hilton is on the list is that she's an 00:24:54.640 --> 00:24:56.710 align:start position:0% Hilton is on the list is that she's an advocate<00:24:55.120> against<00:24:55.520> deep<00:24:55.840> fakes.<00:24:56.400> I<00:24:56.559> mean, 00:24:56.710 --> 00:24:56.720 align:start position:0% advocate against deep fakes. I mean, 00:24:56.720 --> 00:24:58.870 align:start position:0% advocate against deep fakes. I mean, nothing<00:24:57.039> against<00:24:57.520> any<00:24:57.760> of<00:24:58.000> those<00:24:58.320> people. 00:24:58.870 --> 00:24:58.880 align:start position:0% nothing against any of those people. 00:24:58.880 --> 00:25:01.269 align:start position:0% nothing against any of those people. They<00:24:59.039> just<00:24:59.279> don't<00:24:59.520> deserve<00:24:59.840> to<00:25:00.159> be<00:25:00.640> on<00:25:00.880> a<00:25:01.039> list 00:25:01.269 --> 00:25:01.279 align:start position:0% They just don't deserve to be on a list 00:25:01.279 --> 00:25:03.669 align:start position:0% They just don't deserve to be on a list of<00:25:01.440> the<00:25:01.679> most<00:25:01.919> influential<00:25:02.559> voices<00:25:02.880> in<00:25:03.120> AI. 00:25:03.669 --> 00:25:03.679 align:start position:0% of the most influential voices in AI. 00:25:03.679 --> 00:25:05.350 align:start position:0% of the most influential voices in AI. Take<00:25:03.840> it<00:25:04.000> from<00:25:04.240> me,<00:25:04.640> somebody<00:25:04.960> who<00:25:05.200> is 00:25:05.350 --> 00:25:05.360 align:start position:0% Take it from me, somebody who is 00:25:05.360 --> 00:25:08.310 align:start position:0% Take it from me, somebody who is literally<00:25:05.919> in<00:25:06.159> the<00:25:06.320> weeds<00:25:06.720> of<00:25:06.880> AI<00:25:07.600> every 00:25:08.310 --> 00:25:08.320 align:start position:0% literally in the weeds of AI every 00:25:08.320 --> 00:25:11.510 align:start position:0% literally in the weeds of AI every single<00:25:09.120> day.<00:25:09.600> I<00:25:09.840> read<00:25:10.159> every<00:25:10.559> bit<00:25:10.720> of<00:25:10.960> news.<00:25:11.360> I 00:25:11.510 --> 00:25:11.520 align:start position:0% single day. I read every bit of news. I 00:25:11.520 --> 00:25:13.029 align:start position:0% single day. I read every bit of news. I read<00:25:11.679> all<00:25:11.919> the<00:25:12.080> articles.<00:25:12.480> I<00:25:12.720> read<00:25:12.799> the 00:25:13.029 --> 00:25:13.039 align:start position:0% read all the articles. I read the 00:25:13.039 --> 00:25:15.269 align:start position:0% read all the articles. I read the research<00:25:13.520> papers.<00:25:14.000> I<00:25:14.240> watch<00:25:14.480> the<00:25:14.799> YouTube 00:25:15.269 --> 00:25:15.279 align:start position:0% research papers. I watch the YouTube 00:25:15.279 --> 00:25:18.149 align:start position:0% research papers. I watch the YouTube videos.<00:25:15.760> I<00:25:16.240> scroll<00:25:16.559> the<00:25:16.799> threads.<00:25:17.440> I<00:25:17.760> try<00:25:18.000> the 00:25:18.149 --> 00:25:18.159 align:start position:0% videos. I scroll the threads. I try the 00:25:18.159 --> 00:25:20.789 align:start position:0% videos. I scroll the threads. I try the tools.<00:25:18.559> I<00:25:18.799> am<00:25:18.960> in<00:25:19.200> the<00:25:19.440> thick<00:25:19.600> of<00:25:19.760> it<00:25:20.159> every 00:25:20.789 --> 00:25:20.799 align:start position:0% tools. I am in the thick of it every 00:25:20.799 --> 00:25:23.590 align:start position:0% tools. I am in the thick of it every single<00:25:21.520> day.<00:25:22.080> These<00:25:22.400> are<00:25:22.559> not<00:25:22.880> influential 00:25:23.590 --> 00:25:23.600 align:start position:0% single day. These are not influential 00:25:23.600 --> 00:25:26.149 align:start position:0% single day. These are not influential people<00:25:23.840> in<00:25:24.159> the<00:25:24.320> space.<00:25:25.039> They're<00:25:25.279> just<00:25:25.679> not. 00:25:26.149 --> 00:25:26.159 align:start position:0% people in the space. They're just not. 00:25:26.159 --> 00:25:27.750 align:start position:0% people in the space. They're just not. And<00:25:26.320> I<00:25:26.480> know<00:25:26.559> I'm<00:25:26.799> getting<00:25:26.960> worked<00:25:27.279> up<00:25:27.440> over 00:25:27.750 --> 00:25:27.760 align:start position:0% And I know I'm getting worked up over 00:25:27.760 --> 00:25:29.750 align:start position:0% And I know I'm getting worked up over something<00:25:28.080> that's<00:25:28.400> probably<00:25:28.799> designed<00:25:29.279> to 00:25:29.750 --> 00:25:29.760 align:start position:0% something that's probably designed to 00:25:29.760 --> 00:25:31.430 align:start position:0% something that's probably designed to work<00:25:30.080> people<00:25:30.400> up,<00:25:30.720> right?<00:25:30.960> Like<00:25:31.120> Time 00:25:31.430 --> 00:25:31.440 align:start position:0% work people up, right? Like Time 00:25:31.440 --> 00:25:33.750 align:start position:0% work people up, right? Like Time magazine<00:25:32.000> is<00:25:32.320> probably<00:25:32.720> purposely<00:25:33.360> rage 00:25:33.750 --> 00:25:33.760 align:start position:0% magazine is probably purposely rage 00:25:33.760 --> 00:25:35.830 align:start position:0% magazine is probably purposely rage baiting<00:25:34.080> us<00:25:34.559> knowing<00:25:34.880> that<00:25:35.120> this<00:25:35.360> is<00:25:35.600> an 00:25:35.830 --> 00:25:35.840 align:start position:0% baiting us knowing that this is an 00:25:35.840 --> 00:25:37.990 align:start position:0% baiting us knowing that this is an incomplete<00:25:36.559> list<00:25:37.039> and<00:25:37.360> like<00:25:37.520> names<00:25:37.840> like 00:25:37.990 --> 00:25:38.000 align:start position:0% incomplete list and like names like 00:25:38.000 --> 00:25:40.710 align:start position:0% incomplete list and like names like Paris<00:25:38.400> Hilton<00:25:38.799> are<00:25:39.039> on<00:25:39.279> it<00:25:39.600> to<00:25:40.000> get<00:25:40.320> people<00:25:40.559> to 00:25:40.710 --> 00:25:40.720 align:start position:0% Paris Hilton are on it to get people to 00:25:40.720 --> 00:25:42.549 align:start position:0% Paris Hilton are on it to get people to go,<00:25:40.880> "What<00:25:41.120> the<00:25:41.279> hell<00:25:41.440> is<00:25:41.600> Paris<00:25:41.840> Hilton<00:25:42.320> doing 00:25:42.549 --> 00:25:42.559 align:start position:0% go, "What the hell is Paris Hilton doing 00:25:42.559 --> 00:25:44.710 align:start position:0% go, "What the hell is Paris Hilton doing on<00:25:42.799> this<00:25:42.960> list?"<00:25:43.440> and<00:25:43.679> get<00:25:43.919> people<00:25:44.080> like<00:25:44.320> me 00:25:44.710 --> 00:25:44.720 align:start position:0% on this list?" and get people like me 00:25:44.720 --> 00:25:47.590 align:start position:0% on this list?" and get people like me and<00:25:45.039> other<00:25:46.000> like<00:25:46.320> people<00:25:46.640> on<00:25:46.960> social<00:25:47.200> media 00:25:47.590 --> 00:25:47.600 align:start position:0% and other like people on social media 00:25:47.600 --> 00:25:49.590 align:start position:0% and other like people on social media talking<00:25:47.840> about<00:25:48.080> how<00:25:48.240> bad<00:25:48.480> this<00:25:48.720> list<00:25:48.960> is<00:25:49.360> just 00:25:49.590 --> 00:25:49.600 align:start position:0% talking about how bad this list is just 00:25:49.600 --> 00:25:51.430 align:start position:0% talking about how bad this list is just because<00:25:49.760> it<00:25:50.000> drives<00:25:50.240> more<00:25:50.480> eyeballs<00:25:50.880> to<00:25:51.120> time. 00:25:51.430 --> 00:25:51.440 align:start position:0% because it drives more eyeballs to time. 00:25:51.440 --> 00:25:53.029 align:start position:0% because it drives more eyeballs to time. And<00:25:51.600> I<00:25:51.760> played<00:25:52.000> right<00:25:52.240> into<00:25:52.400> it.<00:25:52.640> But<00:25:52.799> okay, 00:25:53.029 --> 00:25:53.039 align:start position:0% And I played right into it. But okay, 00:25:53.039 --> 00:25:55.029 align:start position:0% And I played right into it. But okay, I'm<00:25:53.200> done<00:25:53.440> ranting.<00:25:54.000> I<00:25:54.240> just<00:25:54.400> think<00:25:54.559> this<00:25:54.799> list 00:25:55.029 --> 00:25:55.039 align:start position:0% I'm done ranting. I just think this list 00:25:55.039 --> 00:25:56.870 align:start position:0% I'm done ranting. I just think this list is<00:25:55.279> absolutely<00:25:55.760> ridiculous.<00:25:56.320> Let's<00:25:56.559> end<00:25:56.799> with 00:25:56.870 --> 00:25:56.880 align:start position:0% is absolutely ridiculous. Let's end with 00:25:56.880 --> 00:25:59.430 align:start position:0% is absolutely ridiculous. Let's end with a<00:25:57.039> cool<00:25:57.279> robot.<00:25:57.760> So,<00:25:58.080> Skilled<00:25:58.400> AI<00:25:58.799> introduced 00:25:59.430 --> 00:25:59.440 align:start position:0% a cool robot. So, Skilled AI introduced 00:25:59.440 --> 00:26:01.830 align:start position:0% a cool robot. So, Skilled AI introduced S1,<00:26:00.159> which<00:26:00.400> is<00:26:00.480> a<00:26:00.720> new<00:26:00.880> foundation<00:26:01.360> model<00:26:01.600> for 00:26:01.830 --> 00:26:01.840 align:start position:0% S1, which is a new foundation model for 00:26:01.840 --> 00:26:03.909 align:start position:0% S1, which is a new foundation model for robots.<00:26:02.400> It<00:26:02.559> can<00:26:02.640> be<00:26:02.799> taught<00:26:03.039> 10-minute<00:26:03.679> long 00:26:03.909 --> 00:26:03.919 align:start position:0% robots. It can be taught 10-minute long 00:26:03.919 --> 00:26:06.630 align:start position:0% robots. It can be taught 10-minute long tasks<00:26:04.640> that<00:26:04.799> it<00:26:05.039> has<00:26:05.200> never<00:26:05.520> seen<00:26:05.840> before<00:26:06.320> from 00:26:06.630 --> 00:26:06.640 align:start position:0% tasks that it has never seen before from 00:26:06.640 --> 00:26:09.430 align:start position:0% tasks that it has never seen before from just<00:26:06.960> one<00:26:07.600> video<00:26:08.159> prompt<00:26:08.720> without<00:26:09.120> any 00:26:09.430 --> 00:26:09.440 align:start position:0% just one video prompt without any 00:26:09.440 --> 00:26:10.950 align:start position:0% just one video prompt without any fine-tuning.<00:26:10.080> So,<00:26:10.240> in<00:26:10.400> this<00:26:10.559> example,<00:26:10.799> you 00:26:10.950 --> 00:26:10.960 align:start position:0% fine-tuning. So, in this example, you 00:26:10.960 --> 00:26:12.310 align:start position:0% fine-tuning. So, in this example, you can<00:26:11.039> see<00:26:11.200> them<00:26:11.360> wearing<00:26:11.600> like<00:26:11.760> little<00:26:12.000> wrist 00:26:12.310 --> 00:26:12.320 align:start position:0% can see them wearing like little wrist 00:26:12.320 --> 00:26:14.230 align:start position:0% can see them wearing like little wrist things<00:26:12.640> with<00:26:12.880> cameras<00:26:13.200> on<00:26:13.360> it<00:26:13.679> doing<00:26:14.000> the 00:26:14.230 --> 00:26:14.240 align:start position:0% things with cameras on it doing the 00:26:14.240 --> 00:26:16.310 align:start position:0% things with cameras on it doing the task.<00:26:14.799> And<00:26:14.960> then<00:26:15.200> when<00:26:15.440> they're<00:26:15.679> done<00:26:16.000> doing 00:26:16.310 --> 00:26:16.320 align:start position:0% task. And then when they're done doing 00:26:16.320 --> 00:26:18.789 align:start position:0% task. And then when they're done doing the<00:26:16.559> task,<00:26:17.039> the<00:26:17.279> robots<00:26:17.760> know<00:26:18.000> how<00:26:18.159> to<00:26:18.400> operate 00:26:18.789 --> 00:26:18.799 align:start position:0% the task, the robots know how to operate 00:26:18.799 --> 00:26:21.269 align:start position:0% the task, the robots know how to operate their<00:26:19.279> hands<00:26:20.000> and<00:26:20.320> recreate<00:26:20.720> the<00:26:20.960> task 00:26:21.269 --> 00:26:21.279 align:start position:0% their hands and recreate the task 00:26:21.279 --> 00:26:22.870 align:start position:0% their hands and recreate the task because<00:26:21.520> they<00:26:21.760> can<00:26:21.919> watch<00:26:22.159> the<00:26:22.400> cameras, 00:26:22.870 --> 00:26:22.880 align:start position:0% because they can watch the cameras, 00:26:22.880 --> 00:26:24.549 align:start position:0% because they can watch the cameras, right?<00:26:23.120> There's<00:26:23.200> a<00:26:23.360> camera<00:26:23.600> on<00:26:23.760> each<00:26:24.000> wrist 00:26:24.549 --> 00:26:24.559 align:start position:0% right? There's a camera on each wrist 00:26:24.559 --> 00:26:27.669 align:start position:0% right? There's a camera on each wrist and<00:26:25.039> there's<00:26:25.520> two<00:26:25.919> robot<00:26:26.320> arms<00:26:26.799> and<00:26:27.039> now<00:26:27.360> based 00:26:27.669 --> 00:26:27.679 align:start position:0% and there's two robot arms and now based 00:26:27.679 --> 00:26:29.669 align:start position:0% and there's two robot arms and now based on<00:26:27.840> what<00:26:28.080> they<00:26:28.320> saw<00:26:28.559> from<00:26:28.720> the<00:26:28.960> cameras,<00:26:29.520> they 00:26:29.669 --> 00:26:29.679 align:start position:0% on what they saw from the cameras, they 00:26:29.679 --> 00:26:31.430 align:start position:0% on what they saw from the cameras, they could<00:26:29.840> now<00:26:30.080> do<00:26:30.240> that.<00:26:30.559> That's<00:26:30.720> pretty<00:26:30.960> cool.<00:26:31.200> I 00:26:31.430 --> 00:26:31.440 align:start position:0% could now do that. That's pretty cool. I 00:26:31.440 --> 00:26:33.269 align:start position:0% could now do that. That's pretty cool. I love<00:26:31.600> seeing<00:26:31.840> advancements<00:26:32.320> in<00:26:32.640> robotics 00:26:33.269 --> 00:26:33.279 align:start position:0% love seeing advancements in robotics 00:26:33.279 --> 00:26:34.710 align:start position:0% love seeing advancements in robotics and,<00:26:33.679> you<00:26:33.840> know,<00:26:34.000> making<00:26:34.159> it<00:26:34.320> easier<00:26:34.559> and 00:26:34.710 --> 00:26:34.720 align:start position:0% and, you know, making it easier and 00:26:34.720 --> 00:26:36.950 align:start position:0% and, you know, making it easier and easier<00:26:35.039> to<00:26:35.200> train<00:26:35.440> robots.<00:26:36.080> So,<00:26:36.400> yeah,<00:26:36.720> this 00:26:36.950 --> 00:26:36.960 align:start position:0% easier to train robots. So, yeah, this 00:26:36.960 --> 00:26:38.310 align:start position:0% easier to train robots. So, yeah, this one's<00:26:37.279> pretty<00:26:37.520> awesome.<00:26:37.840> Oh,<00:26:38.000> and<00:26:38.159> by<00:26:38.240> the 00:26:38.310 --> 00:26:38.320 align:start position:0% one's pretty awesome. Oh, and by the 00:26:38.320 --> 00:26:39.510 align:start position:0% one's pretty awesome. Oh, and by the way,<00:26:38.480> if<00:26:38.640> you<00:26:38.720> haven't<00:26:38.880> watched<00:26:39.120> some<00:26:39.279> of<00:26:39.360> the 00:26:39.510 --> 00:26:39.520 align:start position:0% way, if you haven't watched some of the 00:26:39.520 --> 00:26:41.590 align:start position:0% way, if you haven't watched some of the videos<00:26:39.840> from<00:26:40.080> the<00:26:40.320> World<00:26:40.640> Humanoid<00:26:41.279> Robot 00:26:41.590 --> 00:26:41.600 align:start position:0% videos from the World Humanoid Robot 00:26:41.600 --> 00:26:43.110 align:start position:0% videos from the World Humanoid Robot Games,<00:26:42.240> you<00:26:42.400> should<00:26:42.480> definitely<00:26:42.799> look<00:26:42.960> them 00:26:43.110 --> 00:26:43.120 align:start position:0% Games, you should definitely look them 00:26:43.120 --> 00:26:44.630 align:start position:0% Games, you should definitely look them up.<00:26:43.360> They're<00:26:43.600> kind<00:26:43.760> of<00:26:43.919> awesome.<00:26:44.320> And<00:26:44.480> that's 00:26:44.630 --> 00:26:44.640 align:start position:0% up. They're kind of awesome. And that's 00:26:44.640 --> 00:26:46.230 align:start position:0% up. They're kind of awesome. And that's what<00:26:44.799> I<00:26:44.880> got<00:26:45.039> for<00:26:45.120> you<00:26:45.279> today.<00:26:45.600> Now,<00:26:45.840> before<00:26:46.080> I 00:26:46.230 --> 00:26:46.240 align:start position:0% what I got for you today. Now, before I 00:26:46.240 --> 00:26:48.470 align:start position:0% what I got for you today. Now, before I sign<00:26:46.480> off,<00:26:46.880> this<00:26:47.039> week<00:26:47.440> was<00:26:47.679> a<00:26:48.000> really<00:26:48.240> big 00:26:48.470 --> 00:26:48.480 align:start position:0% sign off, this week was a really big 00:26:48.480 --> 00:26:50.470 align:start position:0% sign off, this week was a really big milestone<00:26:49.039> for<00:26:49.279> me<00:26:49.600> personally<00:26:50.000> as<00:26:50.240> well. 00:26:50.470 --> 00:26:50.480 align:start position:0% milestone for me personally as well. 00:26:50.480 --> 00:26:51.830 align:start position:0% milestone for me personally as well. This<00:26:50.640> was<00:26:50.720> the<00:26:50.880> week<00:26:50.960> that<00:26:51.120> I<00:26:51.360> actually<00:26:51.520> passed 00:26:51.830 --> 00:26:51.840 align:start position:0% This was the week that I actually passed 00:26:51.840 --> 00:26:54.230 align:start position:0% This was the week that I actually passed a<00:26:52.000> million<00:26:52.320> subscribers<00:26:52.880> on<00:26:53.279> YouTube,<00:26:53.840> and<00:26:54.000> I 00:26:54.230 --> 00:26:54.240 align:start position:0% a million subscribers on YouTube, and I 00:26:54.240 --> 00:26:56.310 align:start position:0% a million subscribers on YouTube, and I can't<00:26:54.559> thank<00:26:54.799> you<00:26:55.120> enough<00:26:55.440> for<00:26:55.760> being<00:26:56.000> a<00:26:56.240> part 00:26:56.310 --> 00:26:56.320 align:start position:0% can't thank you enough for being a part 00:26:56.320 --> 00:26:57.990 align:start position:0% can't thank you enough for being a part of<00:26:56.480> that.<00:26:56.720> Everybody<00:26:57.039> who<00:26:57.279> watches<00:26:57.600> these 00:26:57.990 --> 00:26:58.000 align:start position:0% of that. Everybody who watches these 00:26:58.000 --> 00:26:59.990 align:start position:0% of that. Everybody who watches these videos,<00:26:58.400> has<00:26:58.640> hit<00:26:58.880> the<00:26:59.120> subscribe<00:26:59.600> button, 00:26:59.990 --> 00:27:00.000 align:start position:0% videos, has hit the subscribe button, 00:27:00.000 --> 00:27:01.750 align:start position:0% videos, has hit the subscribe button, who<00:27:00.159> has<00:27:00.320> liked<00:27:00.640> the<00:27:00.880> videos,<00:27:01.200> which<00:27:01.440> has 00:27:01.750 --> 00:27:01.760 align:start position:0% who has liked the videos, which has 00:27:01.760 --> 00:27:03.110 align:start position:0% who has liked the videos, which has helped<00:27:02.000> me<00:27:02.159> get<00:27:02.320> more<00:27:02.559> reach<00:27:02.799> on<00:27:02.960> these 00:27:03.110 --> 00:27:03.120 align:start position:0% helped me get more reach on these 00:27:03.120 --> 00:27:05.110 align:start position:0% helped me get more reach on these videos.<00:27:03.440> I<00:27:03.679> appreciate<00:27:04.080> you<00:27:04.480> more<00:27:04.720> than<00:27:04.960> you 00:27:05.110 --> 00:27:05.120 align:start position:0% videos. I appreciate you more than you 00:27:05.120 --> 00:27:07.269 align:start position:0% videos. I appreciate you more than you know.<00:27:05.520> It<00:27:05.760> has<00:27:05.919> been<00:27:06.080> an<00:27:06.320> awesome<00:27:06.640> ride<00:27:07.039> and 00:27:07.269 --> 00:27:07.279 align:start position:0% know. It has been an awesome ride and 00:27:07.279 --> 00:27:09.510 align:start position:0% know. It has been an awesome ride and I'm<00:27:07.520> excited<00:27:07.760> to<00:27:08.000> keep<00:27:08.159> on<00:27:08.400> going<00:27:08.799> and<00:27:09.200> seeing 00:27:09.510 --> 00:27:09.520 align:start position:0% I'm excited to keep on going and seeing 00:27:09.520 --> 00:27:11.510 align:start position:0% I'm excited to keep on going and seeing how<00:27:09.679> big<00:27:09.919> this<00:27:10.240> thing<00:27:10.480> could<00:27:10.720> get<00:27:10.960> and<00:27:11.279> how 00:27:11.510 --> 00:27:11.520 align:start position:0% how big this thing could get and how 00:27:11.520 --> 00:27:13.510 align:start position:0% how big this thing could get and how much<00:27:11.679> more<00:27:12.080> helpful<00:27:12.480> I<00:27:12.640> could<00:27:12.880> try<00:27:13.039> to<00:27:13.279> make 00:27:13.510 --> 00:27:13.520 align:start position:0% much more helpful I could try to make 00:27:13.520 --> 00:27:15.830 align:start position:0% much more helpful I could try to make these<00:27:13.840> videos<00:27:14.159> as<00:27:14.320> I<00:27:14.559> go.<00:27:14.799> It's<00:27:14.960> my<00:27:15.200> goal<00:27:15.520> every 00:27:15.830 --> 00:27:15.840 align:start position:0% these videos as I go. It's my goal every 00:27:15.840 --> 00:27:18.630 align:start position:0% these videos as I go. It's my goal every week<00:27:16.240> to<00:27:16.799> drink<00:27:17.120> from<00:27:17.279> the<00:27:17.440> fire<00:27:17.679> hose<00:27:18.240> and 00:27:18.630 --> 00:27:18.640 align:start position:0% week to drink from the fire hose and 00:27:18.640 --> 00:27:20.789 align:start position:0% week to drink from the fire hose and keep<00:27:18.799> up<00:27:19.039> with<00:27:19.200> all<00:27:19.440> the<00:27:19.679> AI<00:27:20.080> news.<00:27:20.480> I'm<00:27:20.640> not 00:27:20.789 --> 00:27:20.799 align:start position:0% keep up with all the AI news. I'm not 00:27:20.799 --> 00:27:22.549 align:start position:0% keep up with all the AI news. I'm not going<00:27:20.880> to<00:27:21.039> try<00:27:21.200> to<00:27:21.520> pretend<00:27:21.840> that<00:27:22.240> everything 00:27:22.549 --> 00:27:22.559 align:start position:0% going to try to pretend that everything 00:27:22.559 --> 00:27:24.230 align:start position:0% going to try to pretend that everything is<00:27:22.799> the<00:27:23.039> biggest<00:27:23.360> deal<00:27:23.600> that's<00:27:23.919> ever 00:27:24.230 --> 00:27:24.240 align:start position:0% is the biggest deal that's ever 00:27:24.240 --> 00:27:25.830 align:start position:0% is the biggest deal that's ever happened.<00:27:24.880> I'm<00:27:25.039> just<00:27:25.200> going<00:27:25.279> to<00:27:25.360> share<00:27:25.600> my 00:27:25.830 --> 00:27:25.840 align:start position:0% happened. I'm just going to share my 00:27:25.840 --> 00:27:27.990 align:start position:0% happened. I'm just going to share my thoughts<00:27:26.320> as<00:27:26.559> they<00:27:26.799> come<00:27:26.960> out<00:27:27.200> about<00:27:27.520> the<00:27:27.760> news 00:27:27.990 --> 00:27:28.000 align:start position:0% thoughts as they come out about the news 00:27:28.000 --> 00:27:29.590 align:start position:0% thoughts as they come out about the news that<00:27:28.159> I<00:27:28.320> think<00:27:28.480> is<00:27:28.640> the<00:27:28.880> most<00:27:29.039> important<00:27:29.360> to 00:27:29.590 --> 00:27:29.600 align:start position:0% that I think is the most important to 00:27:29.600 --> 00:27:31.669 align:start position:0% that I think is the most important to the<00:27:29.760> most<00:27:30.000> amount<00:27:30.320> of<00:27:30.559> people.<00:27:31.039> And<00:27:31.200> if<00:27:31.440> that's 00:27:31.669 --> 00:27:31.679 align:start position:0% the most amount of people. And if that's 00:27:31.679 --> 00:27:33.430 align:start position:0% the most amount of people. And if that's something<00:27:31.919> that's<00:27:32.240> interesting<00:27:32.799> to<00:27:33.039> you, 00:27:33.430 --> 00:27:33.440 align:start position:0% something that's interesting to you, 00:27:33.440 --> 00:27:35.269 align:start position:0% something that's interesting to you, maybe<00:27:33.679> consider<00:27:34.080> liking<00:27:34.400> this<00:27:34.559> video.<00:27:34.880> And<00:27:35.120> if 00:27:35.269 --> 00:27:35.279 align:start position:0% maybe consider liking this video. And if 00:27:35.279 --> 00:27:36.710 align:start position:0% maybe consider liking this video. And if you<00:27:35.360> haven't<00:27:35.600> already,<00:27:35.919> subscribe<00:27:36.320> to<00:27:36.480> this 00:27:36.710 --> 00:27:36.720 align:start position:0% you haven't already, subscribe to this 00:27:36.720 --> 00:27:38.470 align:start position:0% you haven't already, subscribe to this channel.<00:27:37.200> A<00:27:37.440> million<00:27:37.600> of<00:27:37.760> you<00:27:37.919> have<00:27:38.159> already 00:27:38.470 --> 00:27:38.480 align:start position:0% channel. A million of you have already 00:27:38.480 --> 00:27:40.870 align:start position:0% channel. A million of you have already done<00:27:38.640> it.<00:27:38.960> And<00:27:39.200> again,<00:27:39.760> thank<00:27:40.000> you<00:27:40.159> so<00:27:40.400> much.<00:27:40.720> I 00:27:40.870 --> 00:27:40.880 align:start position:0% done it. And again, thank you so much. I 00:27:40.880 --> 00:27:42.630 align:start position:0% done it. And again, thank you so much. I do<00:27:41.039> record<00:27:41.360> these<00:27:41.600> videos<00:27:41.840> on<00:27:42.080> Thursdays<00:27:42.480> and 00:27:42.630 --> 00:27:42.640 align:start position:0% do record these videos on Thursdays and 00:27:42.640 --> 00:27:44.149 align:start position:0% do record these videos on Thursdays and publish<00:27:42.880> them<00:27:43.039> on<00:27:43.200> Friday.<00:27:43.520> So,<00:27:43.679> if<00:27:43.840> anything 00:27:44.149 --> 00:27:44.159 align:start position:0% publish them on Friday. So, if anything 00:27:44.159 --> 00:27:46.310 align:start position:0% publish them on Friday. So, if anything came<00:27:44.320> out<00:27:44.559> sort<00:27:44.720> of<00:27:44.799> late<00:27:45.120> Thursday<00:27:45.679> evening 00:27:46.310 --> 00:27:46.320 align:start position:0% came out sort of late Thursday evening 00:27:46.320 --> 00:27:48.789 align:start position:0% came out sort of late Thursday evening or<00:27:46.559> on<00:27:46.880> Friday,<00:27:47.440> it'll<00:27:47.840> usually<00:27:48.240> make<00:27:48.400> it<00:27:48.559> into 00:27:48.789 --> 00:27:48.799 align:start position:0% or on Friday, it'll usually make it into 00:27:48.799 --> 00:27:50.950 align:start position:0% or on Friday, it'll usually make it into next<00:27:49.120> Friday's<00:27:49.760> video.<00:27:50.240> But<00:27:50.400> again,<00:27:50.640> I'll<00:27:50.880> do 00:27:50.950 --> 00:27:50.960 align:start position:0% next Friday's video. But again, I'll do 00:27:50.960 --> 00:27:53.269 align:start position:0% next Friday's video. But again, I'll do my<00:27:51.200> best<00:27:51.360> to<00:27:51.760> keep<00:27:51.919> you<00:27:52.159> looped<00:27:52.559> in<00:27:52.880> and 00:27:53.269 --> 00:27:53.279 align:start position:0% my best to keep you looped in and 00:27:53.279 --> 00:27:54.710 align:start position:0% my best to keep you looped in and hopefully<00:27:53.679> make<00:27:53.760> you<00:27:54.000> feel<00:27:54.159> like<00:27:54.320> you<00:27:54.559> don't 00:27:54.710 --> 00:27:54.720 align:start position:0% hopefully make you feel like you don't 00:27:54.720 --> 00:27:56.070 align:start position:0% hopefully make you feel like you don't have<00:27:54.799> to<00:27:54.880> keep<00:27:55.039> up<00:27:55.200> with<00:27:55.360> it<00:27:55.440> on<00:27:55.600> a<00:27:55.760> daily 00:27:56.070 --> 00:27:56.080 align:start position:0% have to keep up with it on a daily 00:27:56.080 --> 00:27:57.990 align:start position:0% have to keep up with it on a daily basis.<00:27:56.480> I<00:27:56.720> got<00:27:56.880> a<00:27:57.039> lot<00:27:57.120> of<00:27:57.279> cool<00:27:57.520> thank<00:27:57.760> yous 00:27:57.990 --> 00:27:58.000 align:start position:0% basis. I got a lot of cool thank yous 00:27:58.000 --> 00:27:59.830 align:start position:0% basis. I got a lot of cool thank yous and<00:27:58.240> shout<00:27:58.480> outs<00:27:58.720> from<00:27:58.960> a<00:27:59.279> lot<00:27:59.360> of<00:27:59.520> different 00:27:59.830 --> 00:27:59.840 align:start position:0% and shout outs from a lot of different 00:27:59.840 --> 00:28:01.909 align:start position:0% and shout outs from a lot of different people<00:28:00.320> over<00:28:00.559> the<00:28:00.799> last<00:28:00.960> few<00:28:01.200> days<00:28:01.440> as<00:28:01.679> I 00:28:01.909 --> 00:28:01.919 align:start position:0% people over the last few days as I 00:28:01.919 --> 00:28:03.750 align:start position:0% people over the last few days as I crossed<00:28:02.159> that<00:28:02.399> million<00:28:03.120> subscriber 00:28:03.750 --> 00:28:03.760 align:start position:0% crossed that million subscriber 00:28:03.760 --> 00:28:06.630 align:start position:0% crossed that million subscriber milestone.<00:28:04.559> And<00:28:04.799> so<00:28:05.039> to<00:28:05.360> wrap<00:28:05.600> this<00:28:05.919> video<00:28:06.240> up, 00:28:06.630 --> 00:28:06.640 align:start position:0% milestone. And so to wrap this video up, 00:28:06.640 --> 00:28:08.230 align:start position:0% milestone. And so to wrap this video up, I<00:28:06.799> thought<00:28:06.880> it<00:28:07.120> would<00:28:07.279> only<00:28:07.600> be<00:28:07.760> appropriate 00:28:08.230 --> 00:28:08.240 align:start position:0% I thought it would only be appropriate 00:28:08.240 --> 00:28:10.549 align:start position:0% I thought it would only be appropriate to<00:28:08.720> share<00:28:08.960> a<00:28:09.279> few<00:28:09.440> of<00:28:09.600> those<00:28:09.840> messages<00:28:10.240> that 00:28:10.549 --> 00:28:10.559 align:start position:0% to share a few of those messages that 00:28:10.559 --> 00:28:12.710 align:start position:0% to share a few of those messages that people<00:28:10.960> sent<00:28:11.279> to<00:28:11.440> me<00:28:11.760> just<00:28:12.000> because<00:28:12.399> I<00:28:12.640> think 00:28:12.710 --> 00:28:12.720 align:start position:0% people sent to me just because I think 00:28:12.720 --> 00:28:14.310 align:start position:0% people sent to me just because I think it's<00:28:12.960> pretty<00:28:13.120> cool<00:28:13.360> and<00:28:13.600> like<00:28:13.840> I'm<00:28:14.080> very 00:28:14.310 --> 00:28:14.320 align:start position:0% it's pretty cool and like I'm very 00:28:14.320 --> 00:28:15.830 align:start position:0% it's pretty cool and like I'm very grateful<00:28:14.720> that<00:28:14.960> people<00:28:15.200> took<00:28:15.440> the<00:28:15.600> time<00:28:15.760> out 00:28:15.830 --> 00:28:15.840 align:start position:0% grateful that people took the time out 00:28:15.840 --> 00:28:17.830 align:start position:0% grateful that people took the time out of<00:28:15.919> their<00:28:16.159> day<00:28:16.320> to<00:28:16.960> send<00:28:17.200> me<00:28:17.360> some<00:28:17.520> of<00:28:17.600> these 00:28:17.830 --> 00:28:17.840 align:start position:0% of their day to send me some of these 00:28:17.840 --> 00:28:19.430 align:start position:0% of their day to send me some of these messages.<00:28:18.399> So,<00:28:18.640> thank<00:28:18.720> you<00:28:18.880> so<00:28:19.120> much<00:28:19.200> for 00:28:19.430 --> 00:28:19.440 align:start position:0% messages. So, thank you so much for 00:28:19.440 --> 00:28:21.430 align:start position:0% messages. So, thank you so much for tuning<00:28:19.760> in.<00:28:20.159> I<00:28:20.399> really<00:28:20.640> really<00:28:20.960> appreciate 00:28:21.430 --> 00:28:21.440 align:start position:0% tuning in. I really really appreciate 00:28:21.440 --> 00:28:23.510 align:start position:0% tuning in. I really really appreciate you.<00:28:21.919> It's<00:28:22.159> been<00:28:22.320> so<00:28:22.559> much<00:28:22.640> fun<00:28:22.880> nerding<00:28:23.360> out 00:28:23.510 --> 00:28:23.520 align:start position:0% you. It's been so much fun nerding out 00:28:23.520 --> 00:28:25.990 align:start position:0% you. It's been so much fun nerding out over<00:28:23.760> the<00:28:24.000> last<00:28:24.399> 17<00:28:24.880> years,<00:28:25.120> but<00:28:25.360> really<00:28:25.760> five 00:28:25.990 --> 00:28:26.000 align:start position:0% over the last 17 years, but really five 00:28:26.000 --> 00:28:28.389 align:start position:0% over the last 17 years, but really five and<00:28:26.080> a<00:28:26.159> half<00:28:26.480> years<00:28:26.720> about<00:28:26.960> AI.<00:28:27.600> And<00:28:28.000> uh<00:28:28.159> I'm 00:28:28.389 --> 00:28:28.399 align:start position:0% and a half years about AI. And uh I'm 00:28:28.399 --> 00:28:29.909 align:start position:0% and a half years about AI. And uh I'm going<00:28:28.480> to<00:28:28.559> keep<00:28:28.720> on<00:28:28.960> going<00:28:29.200> with<00:28:29.360> this.<00:28:29.679> Thank 00:28:29.909 --> 00:28:29.919 align:start position:0% going to keep on going with this. Thank 00:28:29.919 --> 00:28:31.269 align:start position:0% going to keep on going with this. Thank you<00:28:30.000> again<00:28:30.240> for<00:28:30.399> tuning<00:28:30.640> in.<00:28:30.880> I<00:28:31.120> really, 00:28:31.269 --> 00:28:31.279 align:start position:0% you again for tuning in. I really, 00:28:31.279 --> 00:28:33.110 align:start position:0% you again for tuning in. I really, really<00:28:31.520> appreciate<00:28:31.840> you.<00:28:32.320> And<00:28:32.640> hopefully 00:28:33.110 --> 00:28:33.120 align:start position:0% really appreciate you. And hopefully 00:28:33.120 --> 00:28:34.149 align:start position:0% really appreciate you. And hopefully I'll<00:28:33.360> see<00:28:33.440> you<00:28:33.440> in<00:28:33.600> the<00:28:33.679> next<00:28:33.760> one. 00:28:34.149 --> 00:28:34.159 align:start position:0% I'll see you in the next one. 00:28:34.159 --> 00:28:35.510 align:start position:0% I'll see you in the next one. >> Congratulations<00:28:34.880> on<00:28:35.039> a<00:28:35.279> million 00:28:35.510 --> 00:28:35.520 align:start position:0% >> Congratulations on a million 00:28:35.520 --> 00:28:36.230 align:start position:0% >> Congratulations on a million subscribers. 00:28:36.230 --> 00:28:36.240 align:start position:0% subscribers. 00:28:36.240 --> 00:28:39.269 align:start position:0% subscribers. >> Congratulations<00:28:37.279> on<00:28:37.760> a<00:28:38.000> million<00:28:38.399> on<00:28:38.640> YouTube. 00:28:39.269 --> 00:28:39.279 align:start position:0% >> Congratulations on a million on YouTube. 00:28:39.279 --> 00:28:40.789 align:start position:0% >> Congratulations on a million on YouTube. That<00:28:39.520> is<00:28:39.840> amazing. 00:28:40.789 --> 00:28:40.799 align:start position:0% That is amazing. 00:28:40.799 --> 00:28:42.230 align:start position:0% That is amazing. >> Congrats,<00:28:41.200> buddy.<00:28:41.520> Well<00:28:41.760> earned. 00:28:42.230 --> 00:28:42.240 align:start position:0% >> Congrats, buddy. Well earned. 00:28:42.240 --> 00:28:44.149 align:start position:0% >> Congrats, buddy. Well earned. >> Congrats<00:28:42.640> on<00:28:42.799> 1<00:28:43.039> million<00:28:43.360> subscribers. 00:28:44.149 --> 00:28:44.159 align:start position:0% >> Congrats on 1 million subscribers. 00:28:44.159 --> 00:28:45.590 align:start position:0% >> Congrats on 1 million subscribers. >> Congratulations<00:28:44.880> on<00:28:45.039> the<00:28:45.279> million 00:28:45.590 --> 00:28:45.600 align:start position:0% >> Congratulations on the million 00:28:45.600 --> 00:28:46.549 align:start position:0% >> Congratulations on the million subscribers. 00:28:46.549 --> 00:28:46.559 align:start position:0% subscribers. 00:28:46.559 --> 00:28:48.549 align:start position:0% subscribers. >> Congratulations<00:28:47.279> on<00:28:47.600> the<00:28:47.840> 1<00:28:48.080> million 00:28:48.549 --> 00:28:48.559 align:start position:0% >> Congratulations on the 1 million 00:28:48.559 --> 00:28:49.190 align:start position:0% >> Congratulations on the 1 million subscribers. 00:28:49.190 --> 00:28:49.200 align:start position:0% subscribers. 00:28:49.200 --> 00:28:51.430 align:start position:0% subscribers. >> Matt,<00:28:49.520> congrats<00:28:49.840> on<00:28:50.000> 1<00:28:50.240> million<00:28:50.559> subscribers. 00:28:51.430 --> 00:28:51.440 align:start position:0% >> Matt, congrats on 1 million subscribers. 00:28:51.440 --> 00:28:53.430 align:start position:0% >> Matt, congrats on 1 million subscribers. This<00:28:51.679> is<00:28:51.919> such<00:28:52.080> a<00:28:52.320> big<00:28:52.480> milestone<00:28:52.960> and<00:28:53.279> so 00:28:53.430 --> 00:28:53.440 align:start position:0% This is such a big milestone and so 00:28:53.440 --> 00:28:54.310 align:start position:0% This is such a big milestone and so welld<00:28:53.679> deserved. 00:28:54.310 --> 00:28:54.320 align:start position:0% welld deserved. 00:28:54.320 --> 00:28:56.149 align:start position:0% welld deserved. >> Congrats<00:28:54.720> on<00:28:54.960> reaching<00:28:55.360> 1<00:28:55.600> million. 00:28:56.149 --> 00:28:56.159 align:start position:0% >> Congrats on reaching 1 million. 00:28:56.159 --> 00:28:58.630 align:start position:0% >> Congrats on reaching 1 million. >> Very<00:28:56.480> happy<00:28:56.720> for<00:28:56.880> you<00:28:57.200> and<00:28:57.679> uh<00:28:57.840> onwards<00:28:58.399> and 00:28:58.630 --> 00:28:58.640 align:start position:0% >> Very happy for you and uh onwards and 00:28:58.640 --> 00:28:59.750 align:start position:0% >> Very happy for you and uh onwards and upwards.<00:28:59.200> Let's<00:28:59.440> do<00:28:59.520> it. 00:28:59.750 --> 00:28:59.760 align:start position:0% upwards. Let's do it. 00:28:59.760 --> 00:29:01.269 align:start position:0% upwards. Let's do it. >> I<00:28:59.919> wanted<00:29:00.159> to<00:29:00.320> wish<00:29:00.480> you<00:29:00.640> a<00:29:00.960> huge 00:29:01.269 --> 00:29:01.279 align:start position:0% >> I wanted to wish you a huge 00:29:01.279 --> 00:29:03.909 align:start position:0% >> I wanted to wish you a huge congratulations<00:29:02.240> on<00:29:02.559> reaching<00:29:02.960> those<00:29:03.440> seven 00:29:03.909 --> 00:29:03.919 align:start position:0% congratulations on reaching those seven 00:29:03.919 --> 00:29:04.470 align:start position:0% congratulations on reaching those seven digits. 00:29:04.470 --> 00:29:04.480 align:start position:0% digits. 00:29:04.480 --> 00:29:06.710 align:start position:0% digits. >> I<00:29:04.720> wish<00:29:04.799> you<00:29:04.960> way<00:29:05.200> more<00:29:05.440> success<00:29:06.320> than<00:29:06.559> you 00:29:06.710 --> 00:29:06.720 align:start position:0% >> I wish you way more success than you 00:29:06.720 --> 00:29:09.830 align:start position:0% >> I wish you way more success than you could<00:29:06.960> ever<00:29:07.279> imagine<00:29:08.000> and<00:29:08.240> I<00:29:08.640> hope<00:29:09.200> that<00:29:09.600> this 00:29:09.830 --> 00:29:09.840 align:start position:0% could ever imagine and I hope that this 00:29:09.840 --> 00:29:11.909 align:start position:0% could ever imagine and I hope that this is<00:29:10.000> just<00:29:10.159> the<00:29:10.399> beginning<00:29:10.960> of<00:29:11.200> your<00:29:11.440> journey. 00:29:11.909 --> 00:29:11.919 align:start position:0% is just the beginning of your journey. 00:29:11.919 --> 00:29:13.269 align:start position:0% is just the beginning of your journey. >> Just<00:29:12.080> wanted<00:29:12.240> to<00:29:12.399> wish<00:29:12.559> you<00:29:12.640> a<00:29:12.799> heartfelt 00:29:13.269 --> 00:29:13.279 align:start position:0% >> Just wanted to wish you a heartfelt 00:29:13.279 --> 00:29:15.029 align:start position:0% >> Just wanted to wish you a heartfelt congratulations<00:29:13.919> on<00:29:14.159> reaching<00:29:14.559> 1<00:29:14.720> million 00:29:15.029 --> 00:29:15.039 align:start position:0% congratulations on reaching 1 million 00:29:15.039 --> 00:29:16.470 align:start position:0% congratulations on reaching 1 million subscribers.<00:29:15.679> Big<00:29:15.919> boy. 00:29:16.470 --> 00:29:16.480 align:start position:0% subscribers. Big boy. 00:29:16.480 --> 00:29:18.630 align:start position:0% subscribers. Big boy. >> Congrats. 00:29:18.630 --> 00:29:18.640 align:start position:0% >> Congrats. 00:29:18.640 --> 00:29:20.549 align:start position:0% >> Congrats. Congrats 00:29:20.549 --> 00:29:20.559 align:start position:0% Congrats 00:29:20.559 --> 00:29:23.590 align:start position:0% Congrats on<00:29:20.880> 1<00:29:21.120> million<00:29:21.679> subscribers. 00:29:23.590 --> 00:29:23.600 align:start position:0% on 1 million subscribers. 00:29:23.600 --> 00:29:27.080 align:start position:0% on 1 million subscribers. >> We<00:29:23.840> love<00:29:24.080> you.