WEBVTT Kind: captions Language: en 00:00:01.070 --> 00:00:12.480 align:start position:0% [Applause] 00:00:12.480 --> 00:00:12.490 align:start position:0% 00:00:12.490 --> 00:00:15.509 align:start position:0% it's<00:00:12.940> to<00:00:13.900> be<00:00:14.219> lost 00:00:15.509 --> 00:00:15.519 align:start position:0% it's to be lost 00:00:15.519 --> 00:00:18.810 align:start position:0% it's to be lost DEFCON<00:00:15.879> say<00:00:16.150> DEFCON<00:00:16.480> 4<00:00:16.779> Mike<00:00:17.050> and<00:00:17.259> I<00:00:17.369> were<00:00:18.369> just 00:00:18.810 --> 00:00:18.820 align:start position:0% DEFCON say DEFCON 4 Mike and I were just 00:00:18.820 --> 00:00:21.029 align:start position:0% DEFCON say DEFCON 4 Mike and I were just roaming<00:00:19.060> around<00:00:19.410> we<00:00:20.410> didn't<00:00:20.740> actually<00:00:20.829> have 00:00:21.029 --> 00:00:21.039 align:start position:0% roaming around we didn't actually have 00:00:21.039 --> 00:00:23.880 align:start position:0% roaming around we didn't actually have an<00:00:21.220> official<00:00:21.520> talk<00:00:21.730> but<00:00:22.449> it<00:00:22.869> was<00:00:22.989> super<00:00:23.680> funny 00:00:23.880 --> 00:00:23.890 align:start position:0% an official talk but it was super funny 00:00:23.890 --> 00:00:25.050 align:start position:0% an official talk but it was super funny because<00:00:24.070> everybody<00:00:24.489> was<00:00:24.640> talking<00:00:24.699> about<00:00:24.910> it 00:00:25.050 --> 00:00:25.060 align:start position:0% because everybody was talking about it 00:00:25.060 --> 00:00:26.519 align:start position:0% because everybody was talking about it and<00:00:25.239> to<00:00:25.329> be<00:00:25.449> it<00:00:25.539> was<00:00:25.630> around<00:00:25.840> the<00:00:26.020> same<00:00:26.050> time 00:00:26.519 --> 00:00:26.529 align:start position:0% and to be it was around the same time 00:00:26.529 --> 00:00:29.819 align:start position:0% and to be it was around the same time that<00:00:26.590> each<00:00:27.219> do<00:00:27.550> was<00:00:27.820> to<00:00:28.750> be<00:00:28.899> to<00:00:29.110> adopt<00:00:29.349> and<00:00:29.710> so 00:00:29.819 --> 00:00:29.829 align:start position:0% that each do was to be to adopt and so 00:00:29.829 --> 00:00:32.609 align:start position:0% that each do was to be to adopt and so on<00:00:30.009> so<00:00:30.460> those<00:00:30.610> are<00:00:30.759> Molly<00:00:30.939> bus<00:00:31.300> and<00:00:31.660> we<00:00:32.349> ended 00:00:32.609 --> 00:00:32.619 align:start position:0% on so those are Molly bus and we ended 00:00:32.619 --> 00:00:34.200 align:start position:0% on so those are Molly bus and we ended up<00:00:32.680> realizing<00:00:32.860> that<00:00:33.520> you<00:00:33.760> know<00:00:33.790> people 00:00:34.200 --> 00:00:34.210 align:start position:0% up realizing that you know people 00:00:34.210 --> 00:00:35.819 align:start position:0% up realizing that you know people actually<00:00:34.480> wanted<00:00:34.870> heard<00:00:35.050> about<00:00:35.320> it<00:00:35.500> with<00:00:35.590> you 00:00:35.819 --> 00:00:35.829 align:start position:0% actually wanted heard about it with you 00:00:35.829 --> 00:00:37.740 align:start position:0% actually wanted heard about it with you people<00:00:36.039> want<00:00:36.399> to<00:00:36.489> you<00:00:36.789> know<00:00:36.910> up<00:00:37.180> there<00:00:37.360> their 00:00:37.740 --> 00:00:37.750 align:start position:0% people want to you know up there their 00:00:37.750 --> 00:00:39.510 align:start position:0% people want to you know up there their skills<00:00:38.050> and<00:00:38.379> understand<00:00:38.980> what<00:00:39.190> this<00:00:39.280> thing<00:00:39.340> is 00:00:39.510 --> 00:00:39.520 align:start position:0% skills and understand what this thing is 00:00:39.520 --> 00:00:40.020 align:start position:0% skills and understand what this thing is all<00:00:39.730> about 00:00:40.020 --> 00:00:40.030 align:start position:0% all about 00:00:40.030 --> 00:00:41.639 align:start position:0% all about so<00:00:40.450> we<00:00:40.570> can't<00:00:40.719> leave<00:00:40.809> him<00:00:40.899> for<00:00:41.140> you<00:00:41.230> -<00:00:41.289> nothing 00:00:41.639 --> 00:00:41.649 align:start position:0% so we can't leave him for you - nothing 00:00:41.649 --> 00:00:44.779 align:start position:0% so we can't leave him for you - nothing like<00:00:41.829> a<00:00:41.980> subversive<00:00:42.399> workshop<00:00:43.329> on<00:00:44.050> velocity 00:00:44.779 --> 00:00:44.789 align:start position:0% like a subversive workshop on velocity 00:00:44.789 --> 00:00:48.090 align:start position:0% like a subversive workshop on velocity very<00:00:45.789> very<00:00:46.239> impromptu<00:00:46.589> relegated<00:00:47.589> over<00:00:47.949> to 00:00:48.090 --> 00:00:48.100 align:start position:0% very very impromptu relegated over to 00:00:48.100 --> 00:00:50.250 align:start position:0% very very impromptu relegated over to the<00:00:48.159> ground<00:00:48.399> a<00:00:48.550> very<00:00:48.760> small<00:00:48.969> organized<00:00:49.449> we<00:00:50.109> had 00:00:50.250 --> 00:00:50.260 align:start position:0% the ground a very small organized we had 00:00:50.260 --> 00:00:52.500 align:start position:0% the ground a very small organized we had a<00:00:50.289> turnout<00:00:50.620> of<00:00:50.949> my<00:00:51.339> heathered<00:00:51.670> of<00:00:51.789> 40<00:00:52.089> to<00:00:52.210> 50 00:00:52.500 --> 00:00:52.510 align:start position:0% a turnout of my heathered of 40 to 50 00:00:52.510 --> 00:00:54.599 align:start position:0% a turnout of my heathered of 40 to 50 people<00:00:52.809> in<00:00:53.019> a<00:00:53.109> tiny<00:00:53.350> room<00:00:53.530> where<00:00:53.949> we<00:00:54.069> had<00:00:54.219> to<00:00:54.339> we 00:00:54.599 --> 00:00:54.609 align:start position:0% people in a tiny room where we had to we 00:00:54.609 --> 00:00:55.889 align:start position:0% people in a tiny room where we had to we had<00:00:54.670> to<00:00:54.879> like<00:00:55.030> move<00:00:55.300> all<00:00:55.629> the<00:00:55.749> furniture 00:00:55.889 --> 00:00:55.899 align:start position:0% had to like move all the furniture 00:00:55.899 --> 00:00:58.139 align:start position:0% had to like move all the furniture around<00:00:56.260> -<00:00:56.769> and<00:00:57.010> sit<00:00:57.460> on<00:00:57.489> the<00:00:57.670> ground<00:00:57.850> so<00:00:58.089> it 00:00:58.139 --> 00:00:58.149 align:start position:0% around - and sit on the ground so it 00:00:58.149 --> 00:00:59.369 align:start position:0% around - and sit on the ground so it felt<00:00:58.359> like<00:00:58.479> you<00:00:58.659> know<00:00:58.780> the<00:00:58.929> start<00:00:59.229> of 00:00:59.369 --> 00:00:59.379 align:start position:0% felt like you know the start of 00:00:59.379 --> 00:01:01.439 align:start position:0% felt like you know the start of something<00:00:59.589> very<00:00:59.949> special<00:01:00.339> in<00:01:00.940> this<00:01:01.059> variance 00:01:01.439 --> 00:01:01.449 align:start position:0% something very special in this variance 00:01:01.449 --> 00:01:03.509 align:start position:0% something very special in this variance between<00:01:01.600> the<00:01:01.839> theory<00:01:02.079> of<00:01:02.199> and<00:01:02.889> they<00:01:03.280> need<00:01:03.429> to 00:01:03.509 --> 00:01:03.519 align:start position:0% between the theory of and they need to 00:01:03.519 --> 00:01:07.230 align:start position:0% between the theory of and they need to be<00:01:03.670> and<00:01:04.510> that<00:01:05.470> we<00:01:06.400> actually<00:01:06.550> have<00:01:06.880> official 00:01:07.230 --> 00:01:07.240 align:start position:0% be and that we actually have official 00:01:07.240 --> 00:01:09.840 align:start position:0% be and that we actually have official sessions<00:01:07.600> this<00:01:07.750> done<00:01:08.010> so<00:01:09.010> so<00:01:09.430> it's<00:01:09.549> great<00:01:09.729> we 00:01:09.840 --> 00:01:09.850 align:start position:0% sessions this done so so it's great we 00:01:09.850 --> 00:01:12.930 align:start position:0% sessions this done so so it's great we have<00:01:10.000> this<00:01:10.840> is<00:01:11.020> one<00:01:11.290> of<00:01:11.470> two<00:01:11.650> sessions<00:01:11.890> that<00:01:12.670> we 00:01:12.930 --> 00:01:12.940 align:start position:0% have this is one of two sessions that we 00:01:12.940 --> 00:01:15.510 align:start position:0% have this is one of two sessions that we are<00:01:13.150> running<00:01:13.450> here<00:01:13.780> in<00:01:13.870> depth<00:01:14.050> on<00:01:14.200> what<00:01:14.950> I'm 00:01:15.510 --> 00:01:15.520 align:start position:0% are running here in depth on what I'm 00:01:15.520 --> 00:01:17.640 align:start position:0% are running here in depth on what I'm going<00:01:15.700> to<00:01:15.730> talk<00:01:15.910> about<00:01:15.940> is<00:01:16.600> what<00:01:17.230> what<00:01:17.560> has 00:01:17.640 --> 00:01:17.650 align:start position:0% going to talk about is what what has 00:01:17.650 --> 00:01:19.590 align:start position:0% going to talk about is what what has been<00:01:17.800> up<00:01:17.980> and<00:01:18.250> they<00:01:18.670> be<00:01:18.760> to<00:01:18.880> be<00:01:18.970> project<00:01:19.180> over 00:01:19.590 --> 00:01:19.600 align:start position:0% been up and they be to be project over 00:01:19.600 --> 00:01:21.120 align:start position:0% been up and they be to be project over the<00:01:19.630> last<00:01:19.750> few<00:01:20.020> months<00:01:20.080> and<00:01:20.620> what's<00:01:20.920> coming 00:01:21.120 --> 00:01:21.130 align:start position:0% the last few months and what's coming 00:01:21.130 --> 00:01:23.040 align:start position:0% the last few months and what's coming next<00:01:21.340> a<00:01:21.670> lot<00:01:21.940> of<00:01:22.150> super<00:01:22.480> exciting<00:01:22.870> stuff 00:01:23.040 --> 00:01:23.050 align:start position:0% next a lot of super exciting stuff 00:01:23.050 --> 00:01:25.860 align:start position:0% next a lot of super exciting stuff coming<00:01:23.080> up<00:01:23.440> next<00:01:23.650> so<00:01:24.250> I<00:01:24.970> have<00:01:25.360> a<00:01:25.390> lot<00:01:25.600> of<00:01:25.630> ground 00:01:25.860 --> 00:01:25.870 align:start position:0% coming up next so I have a lot of ground 00:01:25.870 --> 00:01:26.310 align:start position:0% coming up next so I have a lot of ground to<00:01:26.050> cover 00:01:26.310 --> 00:01:26.320 align:start position:0% to cover 00:01:26.320 --> 00:01:28.410 align:start position:0% to cover I'm<00:01:26.500> gonna<00:01:26.680> go<00:01:26.830> super<00:01:27.040> super<00:01:27.370> quickly<00:01:27.760> I<00:01:28.090> don't 00:01:28.410 --> 00:01:28.420 align:start position:0% I'm gonna go super super quickly I don't 00:01:28.420 --> 00:01:28.850 align:start position:0% I'm gonna go super super quickly I don't even 00:01:28.850 --> 00:01:28.860 align:start position:0% even 00:01:28.860 --> 00:01:32.420 align:start position:0% even again<00:01:29.280> we<00:01:29.940> done<00:01:30.120> this<00:01:30.360> in<00:01:31.260> time<00:01:31.560> but<00:01:31.920> if<00:01:32.250> I 00:01:32.420 --> 00:01:32.430 align:start position:0% again we done this in time but if I 00:01:32.430 --> 00:01:34.850 align:start position:0% again we done this in time but if I don't<00:01:32.700> come<00:01:33.060> feel<00:01:33.300> come<00:01:33.780> come<00:01:34.500> talk<00:01:34.710> to<00:01:34.740> me 00:01:34.850 --> 00:01:34.860 align:start position:0% don't come feel come come talk to me 00:01:34.860 --> 00:01:36.320 align:start position:0% don't come feel come come talk to me come<00:01:35.190> find<00:01:35.340> me<00:01:35.460> I'm<00:01:35.640> going<00:01:35.820> to<00:01:35.880> be<00:01:35.940> I'm<00:01:36.270> going 00:01:36.320 --> 00:01:36.330 align:start position:0% come find me I'm going to be I'm going 00:01:36.330 --> 00:01:38.420 align:start position:0% come find me I'm going to be I'm going to<00:01:36.510> be<00:01:36.570> your<00:01:36.720> owns<00:01:36.930> the<00:01:37.500> second<00:01:37.920> talk<00:01:38.130> can<00:01:38.310> we 00:01:38.420 --> 00:01:38.430 align:start position:0% to be your owns the second talk can we 00:01:38.430 --> 00:01:40.940 align:start position:0% to be your owns the second talk can we go<00:01:38.520> we<00:01:38.730> have<00:01:38.910> a<00:01:38.940> pentacle<00:01:39.780> is<00:01:39.960> about<00:01:40.530> gossip 00:01:40.940 --> 00:01:40.950 align:start position:0% go we have a pentacle is about gossip 00:01:40.950 --> 00:01:41.570 align:start position:0% go we have a pentacle is about gossip sir 00:01:41.570 --> 00:01:41.580 align:start position:0% sir 00:01:41.580 --> 00:01:43.700 align:start position:0% sir so<00:01:42.000> a<00:01:42.030> lot<00:01:42.390> of<00:01:42.420> people<00:01:42.540> gossip<00:01:43.020> service<00:01:43.350> is<00:01:43.590> an 00:01:43.700 --> 00:01:43.710 align:start position:0% so a lot of people gossip service is an 00:01:43.710 --> 00:01:44.780 align:start position:0% so a lot of people gossip service is an important<00:01:44.130> protocol<00:01:44.490> that<00:01:44.670> is<00:01:44.760> being 00:01:44.780 --> 00:01:44.790 align:start position:0% important protocol that is being 00:01:44.790 --> 00:01:47.870 align:start position:0% important protocol that is being conducted<00:01:45.060> at<00:01:45.420> the<00:01:45.530> need<00:01:46.530> to<00:01:46.800> project<00:01:47.040> and<00:01:47.520> a 00:01:47.870 --> 00:01:47.880 align:start position:0% conducted at the need to project and a 00:01:47.880 --> 00:01:49.160 align:start position:0% conducted at the need to project and a lot<00:01:48.030> of<00:01:48.120> people<00:01:48.300> have<00:01:48.420> shown<00:01:48.479> interest<00:01:48.840> so<00:01:49.080> we 00:01:49.160 --> 00:01:49.170 align:start position:0% lot of people have shown interest so we 00:01:49.170 --> 00:01:50.570 align:start position:0% lot of people have shown interest so we decided<00:01:49.470> to<00:01:49.560> do<00:01:49.740> kind<00:01:49.920> of<00:01:50.010> like<00:01:50.070> a<00:01:50.160> deep<00:01:50.400> dive 00:01:50.570 --> 00:01:50.580 align:start position:0% decided to do kind of like a deep dive 00:01:50.580 --> 00:01:53.300 align:start position:0% decided to do kind of like a deep dive in<00:01:50.790> concept<00:01:51.150> of<00:01:51.440> stuff<00:01:52.440> that's<00:01:52.680> happening<00:01:53.040> on 00:01:53.300 --> 00:01:53.310 align:start position:0% in concept of stuff that's happening on 00:01:53.310 --> 00:01:57.380 align:start position:0% in concept of stuff that's happening on Wednesday<00:01:53.840> moon<00:01:54.840> beat<00:01:55.050> 10<00:01:55.620> and<00:01:56.580> your<00:01:57.030> collagen 00:01:57.380 --> 00:01:57.390 align:start position:0% Wednesday moon beat 10 and your collagen 00:01:57.390 --> 00:02:00.380 align:start position:0% Wednesday moon beat 10 and your collagen Sunstein<00:01:57.930> the<00:01:58.170> scientists<00:01:59.010> for<00:01:59.100> now<00:01:59.220> just<00:02:00.090> get 00:02:00.380 --> 00:02:00.390 align:start position:0% Sunstein the scientists for now just get 00:02:00.390 --> 00:02:00.890 align:start position:0% Sunstein the scientists for now just get started 00:02:00.890 --> 00:02:00.900 align:start position:0% started 00:02:00.900 --> 00:02:03.890 align:start position:0% started so<00:02:01.140> I<00:02:01.170> see<00:02:01.470> a<00:02:01.860> lot<00:02:02.190> of<00:02:02.640> idiot<00:02:03.240> business<00:02:03.600> here<00:02:03.869> so 00:02:03.890 --> 00:02:03.900 align:start position:0% so I see a lot of idiot business here so 00:02:03.900 --> 00:02:05.840 align:start position:0% so I see a lot of idiot business here so it<00:02:04.140> was<00:02:04.259> actually<00:02:04.410> user<00:02:04.890> rational<00:02:05.460> so<00:02:05.729> it's 00:02:05.840 --> 00:02:05.850 align:start position:0% it was actually user rational so it's 00:02:05.850 --> 00:02:07.640 align:start position:0% it was actually user rational so it's actually<00:02:05.970> a<00:02:06.119> user<00:02:06.450> of<00:02:06.869> it<00:02:07.140> needs<00:02:07.320> to<00:02:07.380> be<00:02:07.440> right 00:02:07.640 --> 00:02:07.650 align:start position:0% actually a user of it needs to be right 00:02:07.650 --> 00:02:10.880 align:start position:0% actually a user of it needs to be right now<00:02:07.890> okay<00:02:08.850> that's<00:02:09.390> pretty<00:02:09.630> cool<00:02:09.869> that's<00:02:10.530> good 00:02:10.880 --> 00:02:10.890 align:start position:0% now okay that's pretty cool that's good 00:02:10.890 --> 00:02:13.820 align:start position:0% now okay that's pretty cool that's good who<00:02:11.040> contributes<00:02:11.520> to<00:02:11.640> gonna<00:02:11.760> be<00:02:11.880> to<00:02:11.970> be<00:02:12.830> nice 00:02:13.820 --> 00:02:13.830 align:start position:0% who contributes to gonna be to be nice 00:02:13.830 --> 00:02:18.740 align:start position:0% who contributes to gonna be to be nice okay<00:02:14.340> we've<00:02:15.150> got<00:02:17.390> activities<00:02:18.390> be<00:02:18.540> that's 00:02:18.740 --> 00:02:18.750 align:start position:0% okay we've got activities be that's 00:02:18.750 --> 00:02:21.710 align:start position:0% okay we've got activities be that's awesome<00:02:19.110> cool<00:02:19.800> so<00:02:20.580> let's<00:02:20.610> get<00:02:20.880> started<00:02:21.270> as<00:02:21.660> I 00:02:21.710 --> 00:02:21.720 align:start position:0% awesome cool so let's get started as I 00:02:21.720 --> 00:02:22.940 align:start position:0% awesome cool so let's get started as I said<00:02:21.959> we<00:02:22.080> have<00:02:22.260> a<00:02:22.290> lot<00:02:22.530> of<00:02:22.560> ground<00:02:22.770> to<00:02:22.920> cover 00:02:22.940 --> 00:02:22.950 align:start position:0% said we have a lot of ground to cover 00:02:22.950 --> 00:02:26.300 align:start position:0% said we have a lot of ground to cover very<00:02:23.459> little<00:02:23.730> time<00:02:23.940> and<00:02:24.920> what<00:02:25.920> I<00:02:25.950> want<00:02:26.190> to<00:02:26.250> go 00:02:26.300 --> 00:02:26.310 align:start position:0% very little time and what I want to go 00:02:26.310 --> 00:02:29.390 align:start position:0% very little time and what I want to go through<00:02:26.640> today<00:02:27.420> so<00:02:27.810> who<00:02:28.170> was<00:02:28.290> actually<00:02:28.650> well 00:02:29.390 --> 00:02:29.400 align:start position:0% through today so who was actually well 00:02:29.400 --> 00:02:31.580 align:start position:0% through today so who was actually well who's<00:02:29.910> actually<00:02:30.090> pretty<00:02:30.600> familiar<00:02:30.840> living<00:02:31.500> to 00:02:31.580 --> 00:02:31.590 align:start position:0% who's actually pretty familiar living to 00:02:31.590 --> 00:02:34.550 align:start position:0% who's actually pretty familiar living to be<00:02:31.739> we<00:02:32.520> just<00:02:32.730> say<00:02:32.880> like<00:02:33.180> who's<00:02:33.750> applying<00:02:34.290> then 00:02:34.550 --> 00:02:34.560 align:start position:0% be we just say like who's applying then 00:02:34.560 --> 00:02:37.400 align:start position:0% be we just say like who's applying then they<00:02:34.650> need<00:02:34.799> to<00:02:34.830> be<00:02:34.980> more<00:02:35.130> is<00:02:35.370> okay<00:02:36.360> five<00:02:37.200> and 00:02:37.400 --> 00:02:37.410 align:start position:0% they need to be more is okay five and 00:02:37.410 --> 00:02:40.070 align:start position:0% they need to be more is okay five and above<00:02:37.470> well<00:02:38.160> so<00:02:38.910> I<00:02:38.940> think<00:02:39.090> the<00:02:39.330> one<00:02:39.540> on<00:02:39.660> one<00:02:39.840> and 00:02:40.070 --> 00:02:40.080 align:start position:0% above well so I think the one on one and 00:02:40.080 --> 00:02:41.539 align:start position:0% above well so I think the one on one and the<00:02:40.230> one<00:02:40.380> on<00:02:40.410> one<00:02:40.620> is<00:02:40.739> going<00:02:40.920> to<00:02:40.980> be<00:02:41.070> it's<00:02:41.400> going 00:02:41.539 --> 00:02:41.549 align:start position:0% the one on one is going to be it's going 00:02:41.549 --> 00:02:45.050 align:start position:0% the one on one is going to be it's going to<00:02:41.610> be<00:02:41.790> important<00:02:42.570> to<00:02:42.690> go<00:02:42.870> through<00:02:43.489> today<00:02:44.489> then 00:02:45.050 --> 00:02:45.060 align:start position:0% to be important to go through today then 00:02:45.060 --> 00:02:46.250 align:start position:0% to be important to go through today then I'm<00:02:45.180> going<00:02:45.330> to<00:02:45.360> I'm<00:02:45.690> going<00:02:45.750> to<00:02:45.930> talk<00:02:46.140> about 00:02:46.250 --> 00:02:46.260 align:start position:0% I'm going to I'm going to talk about 00:02:46.260 --> 00:02:48.050 align:start position:0% I'm going to I'm going to talk about what<00:02:46.769> we've<00:02:46.920> shed<00:02:47.250> in<00:02:47.519> the<00:02:47.610> last<00:02:47.760> few<00:02:47.910> months 00:02:48.050 --> 00:02:48.060 align:start position:0% what we've shed in the last few months 00:02:48.060 --> 00:02:50.530 align:start position:0% what we've shed in the last few months and<00:02:48.330> won't<00:02:48.540> be<00:02:48.690> actually<00:02:49.290> building<00:02:49.680> and 00:02:50.530 --> 00:02:50.540 align:start position:0% and won't be actually building and 00:02:50.540 --> 00:02:54.869 align:start position:0% and won't be actually building and a<00:02:50.569> few<00:02:51.319> months<00:02:51.620> so<00:02:52.370> so<00:02:53.299> yeah<00:02:53.450> cool<00:02:53.870> so<00:02:54.049> that's 00:02:54.869 --> 00:02:54.879 align:start position:0% a few months so so yeah cool so that's 00:02:54.879 --> 00:02:56.740 align:start position:0% a few months so so yeah cool so that's little<00:02:55.879> insurance<00:02:56.150> for<00:02:56.269> their<00:02:56.359> beauty<00:02:56.540> so 00:02:56.740 --> 00:02:56.750 align:start position:0% little insurance for their beauty so 00:02:56.750 --> 00:02:57.819 align:start position:0% little insurance for their beauty so it'll<00:02:56.930> be<00:02:57.019> to<00:02:57.140> me<00:02:57.230> it's<00:02:57.439> a<00:02:57.560> modular 00:02:57.819 --> 00:02:57.829 align:start position:0% it'll be to me it's a modular 00:02:57.829 --> 00:03:00.880 align:start position:0% it'll be to me it's a modular peer-to-peer<00:02:58.310> networking<00:02:58.939> stack<00:02:59.299> it<00:02:59.510> is<00:03:00.170> I'd 00:03:00.880 --> 00:03:00.890 align:start position:0% peer-to-peer networking stack it is I'd 00:03:00.890 --> 00:03:02.970 align:start position:0% peer-to-peer networking stack it is I'd like<00:03:01.280> to<00:03:01.430> follow<00:03:01.579> that<00:03:01.819> later<00:03:02.030> it's 00:03:02.970 --> 00:03:02.980 align:start position:0% like to follow that later it's 00:03:02.980 --> 00:03:05.470 align:start position:0% like to follow that later it's decentralized<00:03:03.980> buffers<00:03:04.519> because<00:03:05.180> it 00:03:05.470 --> 00:03:05.480 align:start position:0% decentralized buffers because it 00:03:05.480 --> 00:03:08.050 align:start position:0% decentralized buffers because it basically<00:03:05.659> is<00:03:06.230> so<00:03:07.099> if<00:03:07.310> you<00:03:07.640> realize 00:03:08.050 --> 00:03:08.060 align:start position:0% basically is so if you realize 00:03:08.060 --> 00:03:09.099 align:start position:0% basically is so if you realize everything<00:03:08.299> that<00:03:08.540> we<00:03:08.629> will<00:03:08.780> take<00:03:08.959> care 00:03:09.099 --> 00:03:09.109 align:start position:0% everything that we will take care 00:03:09.109 --> 00:03:10.300 align:start position:0% everything that we will take care everything<00:03:09.319> that's<00:03:09.620> getting<00:03:09.859> built<00:03:10.069> in<00:03:10.220> this 00:03:10.300 --> 00:03:10.310 align:start position:0% everything that's getting built in this 00:03:10.310 --> 00:03:12.039 align:start position:0% everything that's getting built in this conference<00:03:10.640> my<00:03:10.939> team's<00:03:11.180> attending<00:03:11.959> this 00:03:12.039 --> 00:03:12.049 align:start position:0% conference my team's attending this 00:03:12.049 --> 00:03:14.559 align:start position:0% conference my team's attending this conference<00:03:12.260> and<00:03:12.620> so<00:03:12.709> on<00:03:12.879> rests<00:03:13.879> on<00:03:14.120> top<00:03:14.359> of 00:03:14.559 --> 00:03:14.569 align:start position:0% conference and so on rests on top of 00:03:14.569 --> 00:03:16.720 align:start position:0% conference and so on rests on top of unstoppable<00:03:15.230> networks<00:03:15.560> if<00:03:15.709> we<00:03:15.859> don't<00:03:16.129> have<00:03:16.459> a 00:03:16.720 --> 00:03:16.730 align:start position:0% unstoppable networks if we don't have a 00:03:16.730 --> 00:03:19.509 align:start position:0% unstoppable networks if we don't have a good<00:03:17.180> peer-to-peer<00:03:17.590> rock-solid<00:03:18.590> networking 00:03:19.509 --> 00:03:19.519 align:start position:0% good peer-to-peer rock-solid networking 00:03:19.519 --> 00:03:21.129 align:start position:0% good peer-to-peer rock-solid networking foundations<00:03:20.030> we<00:03:20.180> have<00:03:20.359> nothing<00:03:20.900> right 00:03:21.129 --> 00:03:21.139 align:start position:0% foundations we have nothing right 00:03:21.139 --> 00:03:22.960 align:start position:0% foundations we have nothing right because<00:03:21.439> the<00:03:21.980> very<00:03:22.219> nature<00:03:22.489> of<00:03:22.639> everything 00:03:22.960 --> 00:03:22.970 align:start position:0% because the very nature of everything 00:03:22.970 --> 00:03:24.490 align:start position:0% because the very nature of everything that<00:03:23.150> we<00:03:23.269> building<00:03:23.569> is<00:03:23.689> decentralized<00:03:24.019> and 00:03:24.490 --> 00:03:24.500 align:start position:0% that we building is decentralized and 00:03:24.500 --> 00:03:26.470 align:start position:0% that we building is decentralized and decentralized<00:03:25.040> means<00:03:25.280> that<00:03:25.549> different<00:03:25.909> nodes 00:03:26.470 --> 00:03:26.480 align:start position:0% decentralized means that different nodes 00:03:26.480 --> 00:03:28.030 align:start position:0% decentralized means that different nodes around<00:03:26.599> the<00:03:26.810> world<00:03:27.049> without<00:03:27.500> knowing<00:03:27.799> each 00:03:28.030 --> 00:03:28.040 align:start position:0% around the world without knowing each 00:03:28.040 --> 00:03:29.589 align:start position:0% around the world without knowing each other<00:03:28.220> and<00:03:28.310> can<00:03:28.519> operate<00:03:28.669> across<00:03:29.090> this<00:03:29.389> have 00:03:29.589 --> 00:03:29.599 align:start position:0% other and can operate across this have 00:03:29.599 --> 00:03:31.330 align:start position:0% other and can operate across this have protocols<00:03:30.109> and<00:03:30.349> across<00:03:30.530> the<00:03:30.680> seven<00:03:30.950> processes 00:03:31.330 --> 00:03:31.340 align:start position:0% protocols and across the seven processes 00:03:31.340 --> 00:03:34.780 align:start position:0% protocols and across the seven processes so<00:03:32.530> the<00:03:33.530> entities<00:03:33.799> and<00:03:34.099> logic<00:03:34.310> appears<00:03:34.669> with 00:03:34.780 --> 00:03:34.790 align:start position:0% so the entities and logic appears with 00:03:34.790 --> 00:03:36.309 align:start position:0% so the entities and logic appears with your<00:03:34.909> networking<00:03:35.389> stack<00:03:35.629> which<00:03:36.290> is 00:03:36.309 --> 00:03:36.319 align:start position:0% your networking stack which is 00:03:36.319 --> 00:03:39.280 align:start position:0% your networking stack which is essentially<00:03:37.129> a<00:03:37.280> composable<00:03:37.970> it's<00:03:38.540> a<00:03:38.810> multiple 00:03:39.280 --> 00:03:39.290 align:start position:0% essentially a composable it's a multiple 00:03:39.290 --> 00:03:40.809 align:start position:0% essentially a composable it's a multiple set<00:03:39.470> of<00:03:39.590> building<00:03:39.889> blocks<00:03:39.919> to<00:03:40.189> assemble<00:03:40.609> a 00:03:40.809 --> 00:03:40.819 align:start position:0% set of building blocks to assemble a 00:03:40.819 --> 00:03:43.330 align:start position:0% set of building blocks to assemble a future-proof<00:03:41.769> peer-to-peer<00:03:42.769> networking 00:03:43.330 --> 00:03:43.340 align:start position:0% future-proof peer-to-peer networking 00:03:43.340 --> 00:03:46.659 align:start position:0% future-proof peer-to-peer networking layer<00:03:43.609> runs<00:03:44.239> on<00:03:44.599> many<00:03:45.409> runtimes<00:03:45.980> server 00:03:46.659 --> 00:03:46.669 align:start position:0% layer runs on many runtimes server 00:03:46.669 --> 00:03:50.289 align:start position:0% layer runs on many runtimes server browser<00:03:47.230> then<00:03:48.230> in<00:03:48.500> experiments<00:03:49.430> in<00:03:49.700> mobile 00:03:50.289 --> 00:03:50.299 align:start position:0% browser then in experiments in mobile 00:03:50.299 --> 00:03:52.119 align:start position:0% browser then in experiments in mobile environments<00:03:50.750> as<00:03:50.840> well<00:03:50.870> and<00:03:51.260> soon<00:03:51.560> as<00:03:51.829> a<00:03:51.859> team 00:03:52.119 --> 00:03:52.129 align:start position:0% environments as well and soon as a team 00:03:52.129 --> 00:03:53.949 align:start position:0% environments as well and soon as a team that's<00:03:52.340> working<00:03:52.519> on<00:03:52.970> making<00:03:53.540> it<00:03:53.659> needs<00:03:53.810> to<00:03:53.870> be 00:03:53.949 --> 00:03:53.959 align:start position:0% that's working on making it needs to be 00:03:53.959 --> 00:03:55.770 align:start position:0% that's working on making it needs to be around<00:03:54.169> nice<00:03:54.379> and<00:03:54.409> young<00:03:54.650> embedded<00:03:55.040> devices 00:03:55.770 --> 00:03:55.780 align:start position:0% around nice and young embedded devices 00:03:55.780 --> 00:03:58.990 align:start position:0% around nice and young embedded devices it<00:03:56.780> originated<00:03:57.440> in<00:03:57.709> the<00:03:57.889> IDF<00:03:58.250> s<00:03:58.370> project<00:03:58.790> and 00:03:58.990 --> 00:03:59.000 align:start position:0% it originated in the IDF s project and 00:03:59.000 --> 00:04:01.270 align:start position:0% it originated in the IDF s project and it's<00:03:59.840> right<00:04:00.139> now<00:04:00.349> implemented<00:04:01.069> across 00:04:01.270 --> 00:04:01.280 align:start position:0% it's right now implemented across 00:04:01.280 --> 00:04:03.250 align:start position:0% it's right now implemented across segments<00:04:01.729> of<00:04:01.819> America<00:04:02.359> so<00:04:02.510> differently<00:04:02.959> at 00:04:03.250 --> 00:04:03.260 align:start position:0% segments of America so differently at 00:04:03.260 --> 00:04:04.420 align:start position:0% segments of America so differently at different<00:04:03.319> levels<00:04:03.799> of<00:04:03.889> maturity 00:04:04.420 --> 00:04:04.430 align:start position:0% different levels of maturity 00:04:04.430 --> 00:04:06.759 align:start position:0% different levels of maturity this<00:04:04.849> is<00:04:04.970> bustling<00:04:05.389> across<00:04:05.769> cross-border 00:04:06.759 --> 00:04:06.769 align:start position:0% this is bustling across cross-border 00:04:06.769 --> 00:04:10.719 align:start position:0% this is bustling across cross-border community<00:04:07.569> initially<00:04:08.569> it<00:04:08.690> was<00:04:08.840> created<00:04:09.409> by<00:04:09.739> IP 00:04:10.719 --> 00:04:10.729 align:start position:0% community initially it was created by IP 00:04:10.729 --> 00:04:13.000 align:start position:0% community initially it was created by IP elaborate<00:04:11.329> upon<00:04:11.419> us<00:04:11.720> and<00:04:11.989> is<00:04:12.260> chewing<00:04:12.590> it<00:04:12.859> back 00:04:13.000 --> 00:04:13.010 align:start position:0% elaborate upon us and is chewing it back 00:04:13.010 --> 00:04:15.369 align:start position:0% elaborate upon us and is chewing it back roads<00:04:13.250> were<00:04:13.400> nuts<00:04:13.609> but<00:04:13.940> by<00:04:14.449> no<00:04:14.510> means<00:04:14.720> does 00:04:15.369 --> 00:04:15.379 align:start position:0% roads were nuts but by no means does 00:04:15.379 --> 00:04:18.189 align:start position:0% roads were nuts but by no means does protocol<00:04:15.829> now<00:04:16.010> own<00:04:16.549> the<00:04:17.329> community<00:04:17.930> whether 00:04:18.189 --> 00:04:18.199 align:start position:0% protocol now own the community whether 00:04:18.199 --> 00:04:20.569 align:start position:0% protocol now own the community whether at<00:04:19.070> this<00:04:19.190> point<00:04:19.699> in<00:04:19.880> time 00:04:20.569 --> 00:04:20.579 align:start position:0% at this point in time 00:04:20.579 --> 00:04:23.119 align:start position:0% at this point in time it's<00:04:21.359> become<00:04:21.690> a<00:04:21.720> public<00:04:22.169> rather<00:04:22.740> than<00:04:22.949> seeing 00:04:23.119 --> 00:04:23.129 align:start position:0% it's become a public rather than seeing 00:04:23.129 --> 00:04:25.330 align:start position:0% it's become a public rather than seeing the<00:04:23.280> content<00:04:23.639> all<00:04:23.789> across<00:04:24.090> the<00:04:24.300> VMS<00:04:24.870> system 00:04:25.330 --> 00:04:25.340 align:start position:0% the content all across the VMS system 00:04:25.340 --> 00:04:27.439 align:start position:0% the content all across the VMS system it's<00:04:26.340> licensed<00:04:26.699> currently<00:04:27.030> licensed 00:04:27.439 --> 00:04:27.449 align:start position:0% it's licensed currently licensed 00:04:27.449 --> 00:04:29.629 align:start position:0% it's licensed currently licensed officially<00:04:27.930> under<00:04:28.169> the<00:04:28.289> MIT<00:04:28.590> stack<00:04:29.039> but<00:04:29.310> soon 00:04:29.629 --> 00:04:29.639 align:start position:0% officially under the MIT stack but soon 00:04:29.639 --> 00:04:30.950 align:start position:0% officially under the MIT stack but soon we're<00:04:29.789> going<00:04:29.909> to<00:04:29.970> be<00:04:30.030> transitioning<00:04:30.419> under 00:04:30.950 --> 00:04:30.960 align:start position:0% we're going to be transitioning under 00:04:30.960 --> 00:04:32.749 align:start position:0% we're going to be transitioning under the<00:04:31.020> MIT<00:04:31.319> license<00:04:31.800> so<00:04:32.280> we're<00:04:32.490> going<00:04:32.610> to<00:04:32.699> be 00:04:32.749 --> 00:04:32.759 align:start position:0% the MIT license so we're going to be 00:04:32.759 --> 00:04:34.249 align:start position:0% the MIT license so we're going to be transitioning<00:04:33.389> this<00:04:33.599> to<00:04:33.750> the<00:04:33.840> permissive 00:04:34.249 --> 00:04:34.259 align:start position:0% transitioning this to the permissive 00:04:34.259 --> 00:04:35.839 align:start position:0% transitioning this to the permissive license<00:04:34.620> tag<00:04:34.770> which<00:04:34.979> gives<00:04:35.460> you<00:04:35.610> even<00:04:35.669> more 00:04:35.839 --> 00:04:35.849 align:start position:0% license tag which gives you even more 00:04:35.849 --> 00:04:41.149 align:start position:0% license tag which gives you even more parent<00:04:36.330> ease<00:04:36.449> in<00:04:37.020> terms<00:04:37.349> of<00:04:37.620> us<00:04:38.370> being<00:04:39.620> able<00:04:40.620> to 00:04:41.149 --> 00:04:41.159 align:start position:0% parent ease in terms of us being able to 00:04:41.159 --> 00:04:45.999 align:start position:0% parent ease in terms of us being able to hold<00:04:41.550> any<00:04:41.819> rights<00:04:42.150> at<00:04:42.270> all<00:04:42.620> over<00:04:43.620> it<00:04:43.770> to<00:04:43.949> be<00:04:44.330> so 00:04:45.999 --> 00:04:46.009 align:start position:0% hold any rights at all over it to be so 00:04:46.009 --> 00:04:49.640 align:start position:0% hold any rights at all over it to be so what<00:04:47.009> does<00:04:47.190> certainly<00:04:47.699> to<00:04:47.819> be<00:04:47.909> really<00:04:48.650> hinges 00:04:49.640 --> 00:04:49.650 align:start position:0% what does certainly to be really hinges 00:04:49.650 --> 00:04:51.559 align:start position:0% what does certainly to be really hinges on<00:04:49.680> this<00:04:50.069> concept<00:04:50.520> of<00:04:50.699> decentralized<00:04:51.389> process 00:04:51.559 --> 00:04:51.569 align:start position:0% on this concept of decentralized process 00:04:51.569 --> 00:04:53.480 align:start position:0% on this concept of decentralized process address<00:04:52.050> once<00:04:52.530> the<00:04:52.740> second<00:04:53.069> task<00:04:53.159> force<00:04:53.400> is 00:04:53.480 --> 00:04:53.490 align:start position:0% address once the second task force is 00:04:53.490 --> 00:04:55.640 align:start position:0% address once the second task force is addressing<00:04:53.879> the<00:04:54.509> grand<00:04:54.870> vision<00:04:55.110> of<00:04:55.440> their 00:04:55.640 --> 00:04:55.650 align:start position:0% addressing the grand vision of their 00:04:55.650 --> 00:04:58.339 align:start position:0% addressing the grand vision of their little<00:04:55.800> being<00:04:56.099> is<00:04:56.520> to<00:04:56.879> is<00:04:57.180> to<00:04:57.810> provide<00:04:58.169> the 00:04:58.339 --> 00:04:58.349 align:start position:0% little being is to is to provide the 00:04:58.349 --> 00:05:00.709 align:start position:0% little being is to is to provide the ability<00:04:58.740> to<00:04:58.770> locate<00:04:59.280> connect<00:04:59.819> authenticate 00:05:00.709 --> 00:05:00.719 align:start position:0% ability to locate connect authenticate 00:05:00.719 --> 00:05:02.839 align:start position:0% ability to locate connect authenticate negotiate<00:05:01.199> and<00:05:01.379> interact<00:05:01.740> sufficiently<00:05:02.219> with 00:05:02.839 --> 00:05:02.849 align:start position:0% negotiate and interact sufficiently with 00:05:02.849 --> 00:05:04.159 align:start position:0% negotiate and interact sufficiently with processes<00:05:03.419> around<00:05:03.539> the<00:05:03.810> world<00:05:03.990> no<00:05:04.139> matter 00:05:04.159 --> 00:05:04.169 align:start position:0% processes around the world no matter 00:05:04.169 --> 00:05:06.830 align:start position:0% processes around the world no matter where<00:05:04.740> they<00:05:04.949> are<00:05:04.979> no<00:05:05.370> matter<00:05:05.550> what<00:05:06.330> transfers 00:05:06.830 --> 00:05:06.840 align:start position:0% where they are no matter what transfers 00:05:06.840 --> 00:05:08.749 align:start position:0% where they are no matter what transfers are<00:05:06.990> using<00:05:07.319> no<00:05:07.560> matter<00:05:07.770> what<00:05:08.129> runtimes<00:05:08.580> them 00:05:08.749 --> 00:05:08.759 align:start position:0% are using no matter what runtimes them 00:05:08.759 --> 00:05:11.899 align:start position:0% are using no matter what runtimes them using<00:05:09.030> as<00:05:09.210> long<00:05:09.479> as<00:05:10.159> their<00:05:11.159> identity<00:05:11.729> is 00:05:11.899 --> 00:05:11.909 align:start position:0% using as long as their identity is 00:05:11.909 --> 00:05:14.390 align:start position:0% using as long as their identity is cryptographically<00:05:12.599> derived<00:05:13.229> from<00:05:13.800> sorry 00:05:14.390 --> 00:05:14.400 align:start position:0% cryptographically derived from sorry 00:05:14.400 --> 00:05:16.100 align:start position:0% cryptographically derived from sorry their<00:05:14.580> identities<00:05:15.240> cryptographic<00:05:15.629> a<00:05:16.050> to 00:05:16.100 --> 00:05:16.110 align:start position:0% their identities cryptographic a to 00:05:16.110 --> 00:05:18.709 align:start position:0% their identities cryptographic a to derive<00:05:16.620> from<00:05:16.650> the<00:05:16.860> public<00:05:17.280> key<00:05:17.400> and<00:05:17.719> letting 00:05:18.709 --> 00:05:18.719 align:start position:0% derive from the public key and letting 00:05:18.719 --> 00:05:20.149 align:start position:0% derive from the public key and letting to<00:05:18.840> be<00:05:18.930> a<00:05:18.960> really<00:05:19.259> strives<00:05:19.590> to<00:05:19.770> make<00:05:19.949> this 00:05:20.149 --> 00:05:20.159 align:start position:0% to be a really strives to make this 00:05:20.159 --> 00:05:22.100 align:start position:0% to be a really strives to make this happen<00:05:20.400> in<00:05:20.610> a<00:05:20.669> scene<00:05:20.909> this<00:05:21.060> matter<00:05:21.330> by<00:05:21.659> taking 00:05:22.100 --> 00:05:22.110 align:start position:0% happen in a scene this matter by taking 00:05:22.110 --> 00:05:24.860 align:start position:0% happen in a scene this matter by taking care<00:05:22.319> of<00:05:22.349> not<00:05:23.250> traversal<00:05:23.849> really<00:05:24.479> after 00:05:24.860 --> 00:05:24.870 align:start position:0% care of not traversal really after 00:05:24.870 --> 00:05:26.510 align:start position:0% care of not traversal really after switching<00:05:25.259> and<00:05:25.620> a<00:05:25.650> few<00:05:25.800> other<00:05:25.979> things<00:05:26.069> that<00:05:26.370> I 00:05:26.510 --> 00:05:26.520 align:start position:0% switching and a few other things that I 00:05:26.520 --> 00:05:28.129 align:start position:0% switching and a few other things that I wanted<00:05:26.969> to<00:05:27.029> make<00:05:27.300> sure<00:05:27.330> that<00:05:27.539> different 00:05:28.129 --> 00:05:28.139 align:start position:0% wanted to make sure that different 00:05:28.139 --> 00:05:29.749 align:start position:0% wanted to make sure that different processes<00:05:28.560> that<00:05:28.680> are<00:05:28.800> running<00:05:28.979> anywhere<00:05:29.699> in 00:05:29.749 --> 00:05:29.759 align:start position:0% processes that are running anywhere in 00:05:29.759 --> 00:05:32.809 align:start position:0% processes that are running anywhere in the<00:05:29.849> world<00:05:30.060> can<00:05:30.360> find<00:05:30.599> other<00:05:31.590> processes<00:05:32.130> in 00:05:32.809 --> 00:05:32.819 align:start position:0% the world can find other processes in 00:05:32.819 --> 00:05:35.059 align:start position:0% the world can find other processes in this<00:05:33.150> global<00:05:33.630> in<00:05:33.719> this<00:05:34.319> global<00:05:34.620> fabric<00:05:34.919> that 00:05:35.059 --> 00:05:35.069 align:start position:0% this global in this global fabric that 00:05:35.069 --> 00:05:36.559 align:start position:0% this global in this global fabric that is<00:05:35.190> the<00:05:35.310> internet<00:05:35.729> and<00:05:35.849> interact<00:05:36.300> with<00:05:36.449> each 00:05:36.559 --> 00:05:36.569 align:start position:0% is the internet and interact with each 00:05:36.569 --> 00:05:37.040 align:start position:0% is the internet and interact with each other 00:05:37.040 --> 00:05:37.050 align:start position:0% other 00:05:37.050 --> 00:05:40.040 align:start position:0% other even<00:05:37.860> as<00:05:37.949> those<00:05:38.099> processes<00:05:38.729> relocate<00:05:39.630> Rome 00:05:40.040 --> 00:05:40.050 align:start position:0% even as those processes relocate Rome 00:05:40.050 --> 00:05:41.779 align:start position:0% even as those processes relocate Rome evolve<00:05:40.650> mutate<00:05:41.130> over<00:05:41.370> time 00:05:41.779 --> 00:05:41.789 align:start position:0% evolve mutate over time 00:05:41.789 --> 00:05:43.820 align:start position:0% evolve mutate over time right<00:05:42.060> choice<00:05:42.270> this<00:05:42.750> is<00:05:42.900> the<00:05:43.440> concept<00:05:43.770> of 00:05:43.820 --> 00:05:43.830 align:start position:0% right choice this is the concept of 00:05:43.830 --> 00:05:45.709 align:start position:0% right choice this is the concept of process<00:05:44.009> addressing<00:05:44.610> is<00:05:44.789> community<00:05:45.479> just 00:05:45.709 --> 00:05:45.719 align:start position:0% process addressing is community just 00:05:45.719 --> 00:05:47.809 align:start position:0% process addressing is community just supposed<00:05:46.020> to<00:05:46.139> endpoint<00:05:47.099> addressing<00:05:47.550> which 00:05:47.809 --> 00:05:47.819 align:start position:0% supposed to endpoint addressing which 00:05:47.819 --> 00:05:50.629 align:start position:0% supposed to endpoint addressing which relies<00:05:48.210> on<00:05:48.479> having<00:05:49.020> a<00:05:49.440> on<00:05:49.919> targeting<00:05:50.580> a 00:05:50.629 --> 00:05:50.639 align:start position:0% relies on having a on targeting a 00:05:50.639 --> 00:05:52.670 align:start position:0% relies on having a on targeting a process<00:05:50.969> by<00:05:51.240> when<00:05:51.870> they<00:05:52.050> are<00:05:52.080> in<00:05:52.349> the<00:05:52.469> walked 00:05:52.670 --> 00:05:52.680 align:start position:0% process by when they are in the walked 00:05:52.680 --> 00:05:55.930 align:start position:0% process by when they are in the walked by<00:05:52.889> an<00:05:53.039> IP<00:05:53.190> address<00:05:53.340> right<00:05:54.240> so<00:05:54.779> it<00:05:54.960> may<00:05:55.050> be 00:05:55.930 --> 00:05:55.940 align:start position:0% by an IP address right so it may be 00:05:55.940 --> 00:05:58.570 align:start position:0% by an IP address right so it may be is<00:05:56.750> a<00:05:57.230> sack<00:05:57.620> of<00:05:57.650> the<00:05:57.860> possible<00:05:58.340> building 00:05:58.570 --> 00:05:58.580 align:start position:0% is a sack of the possible building 00:05:58.580 --> 00:05:59.950 align:start position:0% is a sack of the possible building blocks<00:05:58.940> and<00:05:59.180> these<00:05:59.330> building<00:05:59.660> Lots<00:05:59.840> I 00:05:59.950 --> 00:05:59.960 align:start position:0% blocks and these building Lots I 00:05:59.960 --> 00:06:01.420 align:start position:0% blocks and these building Lots I transfer<00:06:00.410> its<00:06:00.560> multiplex<00:06:01.040> a<00:06:01.160> circular 00:06:01.420 --> 00:06:01.430 align:start position:0% transfer its multiplex a circular 00:06:01.430 --> 00:06:03.190 align:start position:0% transfer its multiplex a circular channel<00:06:01.820> leaves<00:06:02.030> its<00:06:02.180> memory<00:06:02.480> pops<00:06:02.810> up<00:06:02.990> at 00:06:03.190 --> 00:06:03.200 align:start position:0% channel leaves its memory pops up at 00:06:03.200 --> 00:06:05.500 align:start position:0% channel leaves its memory pops up at rehearsal<00:06:03.320> and<00:06:03.950> several<00:06:04.940> other<00:06:05.060> things<00:06:05.150> that 00:06:05.500 --> 00:06:05.510 align:start position:0% rehearsal and several other things that 00:06:05.510 --> 00:06:07.450 align:start position:0% rehearsal and several other things that I've<00:06:05.600> got<00:06:05.720> even<00:06:05.930> mentioned<00:06:06.290> here<00:06:06.530> so<00:06:07.280> they 00:06:07.450 --> 00:06:07.460 align:start position:0% I've got even mentioned here so they 00:06:07.460 --> 00:06:09.070 align:start position:0% I've got even mentioned here so they know<00:06:07.520> they're<00:06:07.910> going<00:06:08.000> to<00:06:08.120> be<00:06:08.210> as<00:06:08.360> a<00:06:08.390> toolbox<00:06:08.870> to 00:06:09.070 --> 00:06:09.080 align:start position:0% know they're going to be as a toolbox to 00:06:09.080 --> 00:06:11.770 align:start position:0% know they're going to be as a toolbox to assemble<00:06:09.500> the<00:06:09.680> network<00:06:10.010> in<00:06:10.130> the<00:06:10.280> year<00:06:10.460> of<00:06:11.330> a 00:06:11.770 --> 00:06:11.780 align:start position:0% assemble the network in the year of a 00:06:11.780 --> 00:06:13.780 align:start position:0% assemble the network in the year of a decent<00:06:12.260> mass<00:06:12.500> spec<00:06:12.740> work<00:06:12.920> from<00:06:13.460> compostable 00:06:13.780 --> 00:06:13.790 align:start position:0% decent mass spec work from compostable 00:06:13.790 --> 00:06:15.220 align:start position:0% decent mass spec work from compostable means<00:06:14.090> it's<00:06:14.330> kinda<00:06:14.540> like<00:06:14.660> the<00:06:14.780> other<00:06:14.900> angle 00:06:15.220 --> 00:06:15.230 align:start position:0% means it's kinda like the other angle 00:06:15.230 --> 00:06:17.110 align:start position:0% means it's kinda like the other angle puzzle<00:06:15.500> right<00:06:15.920> these<00:06:16.520> are<00:06:16.550> the<00:06:16.700> mints<00:06:16.910> is<00:06:16.970> not 00:06:17.110 --> 00:06:17.120 align:start position:0% puzzle right these are the mints is not 00:06:17.120 --> 00:06:19.450 align:start position:0% puzzle right these are the mints is not into<00:06:17.360> each<00:06:17.510> other<00:06:17.660> by<00:06:18.140> abstractions<00:06:18.890> and<00:06:19.160> each 00:06:19.450 --> 00:06:19.460 align:start position:0% into each other by abstractions and each 00:06:19.460 --> 00:06:20.800 align:start position:0% into each other by abstractions and each of<00:06:19.640> these<00:06:19.730> sentiments<00:06:20.030> can<00:06:20.360> have<00:06:20.510> multiple 00:06:20.800 --> 00:06:20.810 align:start position:0% of these sentiments can have multiple 00:06:20.810 --> 00:06:23.260 align:start position:0% of these sentiments can have multiple bangin<00:06:21.380> augmentation<00:06:21.860> so<00:06:22.010> for<00:06:22.160> example<00:06:22.610> we 00:06:23.260 --> 00:06:23.270 align:start position:0% bangin augmentation so for example we 00:06:23.270 --> 00:06:25.480 align:start position:0% bangin augmentation so for example we have<00:06:23.420> ones<00:06:23.600> about<00:06:23.780> transforming<00:06:24.260> CCP<00:06:24.830> quick 00:06:25.480 --> 00:06:25.490 align:start position:0% have ones about transforming CCP quick 00:06:25.490 --> 00:06:28.030 align:start position:0% have ones about transforming CCP quick there<00:06:26.360> is<00:06:26.450> room<00:06:26.690> to<00:06:26.720> transfer<00:06:27.170> Axl<00:06:27.560> I'm<00:06:27.680> coming 00:06:28.030 --> 00:06:28.040 align:start position:0% there is room to transfer Axl I'm coming 00:06:28.040 --> 00:06:31.240 align:start position:0% there is room to transfer Axl I'm coming that<00:06:28.820> we're<00:06:29.390> working<00:06:29.480> on<00:06:29.810> UDP<00:06:30.230> so<00:06:30.650> there's<00:06:31.190> a 00:06:31.240 --> 00:06:31.250 align:start position:0% that we're working on UDP so there's a 00:06:31.250 --> 00:06:33.370 align:start position:0% that we're working on UDP so there's a number<00:06:31.370> of<00:06:31.790> vacuum<00:06:32.540> orientations<00:06:33.170> to<00:06:33.290> each 00:06:33.370 --> 00:06:33.380 align:start position:0% number of vacuum orientations to each 00:06:33.380 --> 00:06:36.160 align:start position:0% number of vacuum orientations to each other<00:06:33.560> pieces<00:06:34.340> so<00:06:34.700> that's<00:06:35.420> nothing<00:06:35.930> like<00:06:36.080> what 00:06:36.160 --> 00:06:36.170 align:start position:0% other pieces so that's nothing like what 00:06:36.170 --> 00:06:37.990 align:start position:0% other pieces so that's nothing like what I<00:06:36.470> have<00:06:36.710> I<00:06:36.920> have<00:06:37.100> very<00:06:37.280> little<00:06:37.460> time<00:06:37.700> so<00:06:37.760> this 00:06:37.990 --> 00:06:38.000 align:start position:0% I have I have very little time so this 00:06:38.000 --> 00:06:39.970 align:start position:0% I have I have very little time so this is<00:06:38.090> what<00:06:38.240> I<00:06:38.270> have<00:06:38.420> for<00:06:38.660> an<00:06:39.020> intro<00:06:39.320> and<00:06:39.560> now 00:06:39.970 --> 00:06:39.980 align:start position:0% is what I have for an intro and now 00:06:39.980 --> 00:06:41.950 align:start position:0% is what I have for an intro and now we're<00:06:40.100> gonna<00:06:40.190> talk<00:06:40.400> about<00:06:40.580> what<00:06:40.820> we<00:06:40.910> said<00:06:41.180> in 00:06:41.950 --> 00:06:41.960 align:start position:0% we're gonna talk about what we said in 00:06:41.960 --> 00:06:43.690 align:start position:0% we're gonna talk about what we said in the<00:06:42.020> last<00:06:42.140> the<00:06:42.620> last<00:06:42.830> few<00:06:43.070> months<00:06:43.280> and<00:06:43.430> this<00:06:43.580> is 00:06:43.690 --> 00:06:43.700 align:start position:0% the last the last few months and this is 00:06:43.700 --> 00:06:46.750 align:start position:0% the last the last few months and this is super<00:06:44.090> exciting<00:06:44.240> so<00:06:45.200> we<00:06:45.680> have<00:06:45.920> certainly<00:06:46.610> to 00:06:46.750 --> 00:06:46.760 align:start position:0% super exciting so we have certainly to 00:06:46.760 --> 00:06:49.630 align:start position:0% super exciting so we have certainly to be<00:06:46.910> has<00:06:47.630> seven<00:06:48.350> needs<00:06:48.680> of<00:06:48.860> the<00:06:48.950> presentations 00:06:49.630 --> 00:06:49.640 align:start position:0% be has seven needs of the presentations 00:06:49.640 --> 00:06:52.210 align:start position:0% be has seven needs of the presentations which<00:06:50.420> are<00:06:50.810> not<00:06:51.050> shipped<00:06:51.380> the<00:06:51.770> shipping 00:06:52.210 --> 00:06:52.220 align:start position:0% which are not shipped the shipping 00:06:52.220 --> 00:06:54.520 align:start position:0% which are not shipped the shipping that's<00:06:52.370> right<00:06:53.210> nothing<00:06:53.810> is<00:06:53.930> ever<00:06:54.080> done<00:06:54.320> at 00:06:54.520 --> 00:06:54.530 align:start position:0% that's right nothing is ever done at 00:06:54.530 --> 00:06:56.890 align:start position:0% that's right nothing is ever done at this<00:06:54.620> world<00:06:54.920> right<00:06:55.280> what's<00:06:56.180> cool<00:06:56.450> about<00:06:56.480> this 00:06:56.890 --> 00:06:56.900 align:start position:0% this world right what's cool about this 00:06:56.900 --> 00:06:58.120 align:start position:0% this world right what's cool about this is<00:06:56.960> that<00:06:57.140> each<00:06:57.530> community<00:06:57.800> each 00:06:58.120 --> 00:06:58.130 align:start position:0% is that each community each 00:06:58.130 --> 00:07:00.700 align:start position:0% is that each community each implementation<00:06:59.120> really<00:06:59.720> is<00:07:00.080> fact<00:07:00.440> and 00:07:00.700 --> 00:07:00.710 align:start position:0% implementation really is fact and 00:07:00.710 --> 00:07:02.950 align:start position:0% implementation really is fact and supported<00:07:01.220> by<00:07:01.370> a<00:07:01.550> different<00:07:02.300> provider 00:07:02.950 --> 00:07:02.960 align:start position:0% supported by a different provider 00:07:02.960 --> 00:07:05.260 align:start position:0% supported by a different provider different<00:07:03.740> community<00:07:04.250> a<00:07:04.280> different<00:07:04.880> team<00:07:05.060> in 00:07:05.260 --> 00:07:05.270 align:start position:0% different community a different team in 00:07:05.270 --> 00:07:07.180 align:start position:0% different community a different team in the<00:07:05.450> united<00:07:05.720> system<00:07:06.050> and<00:07:06.500> these<00:07:06.710> teams<00:07:07.010> are 00:07:07.180 --> 00:07:07.190 align:start position:0% the united system and these teams are 00:07:07.190 --> 00:07:09.730 align:start position:0% the united system and these teams are actually<00:07:07.340> working<00:07:08.120> okay<00:07:08.990> we're<00:07:09.320> gonna<00:07:09.560> tell 00:07:09.730 --> 00:07:09.740 align:start position:0% actually working okay we're gonna tell 00:07:09.740 --> 00:07:11.860 align:start position:0% actually working okay we're gonna tell me<00:07:09.860> here<00:07:10.010> so<00:07:10.250> we're<00:07:10.400> calling<00:07:10.580> okay<00:07:11.360> grace<00:07:11.540> max 00:07:11.860 --> 00:07:11.870 align:start position:0% me here so we're calling okay grace max 00:07:11.870 --> 00:07:14.290 align:start position:0% me here so we're calling okay grace max stages<00:07:12.830> over<00:07:13.040> there<00:07:13.190> summarizing<00:07:13.850> the<00:07:14.030> movie 00:07:14.290 --> 00:07:14.300 align:start position:0% stages over there summarizing the movie 00:07:14.300 --> 00:07:17.560 align:start position:0% stages over there summarizing the movie to<00:07:14.419> be<00:07:14.450> we've<00:07:15.200> got<00:07:15.550> the<00:07:16.550> single<00:07:17.090> frame<00:07:17.300> team 00:07:17.560 --> 00:07:17.570 align:start position:0% to be we've got the single frame team 00:07:17.570 --> 00:07:18.600 align:start position:0% to be we've got the single frame team over<00:07:17.780> there<00:07:17.960> that 00:07:18.600 --> 00:07:18.610 align:start position:0% over there that 00:07:18.610 --> 00:07:20.850 align:start position:0% over there that impressively<00:07:19.449> to<00:07:19.629> beat<00:07:19.810> that's<00:07:20.050> working<00:07:20.680> with 00:07:20.850 --> 00:07:20.860 align:start position:0% impressively to beat that's working with 00:07:20.860 --> 00:07:23.850 align:start position:0% impressively to beat that's working with the<00:07:21.580> weapon<00:07:21.879> foundation<00:07:22.500> trusted<00:07:23.500> me<00:07:23.590> to<00:07:23.710> be 00:07:23.850 --> 00:07:23.860 align:start position:0% the weapon foundation trusted me to be 00:07:23.860 --> 00:07:25.890 align:start position:0% the weapon foundation trusted me to be do<00:07:24.340> we<00:07:24.430> have<00:07:24.580> because<00:07:25.090> I<00:07:25.150> think<00:07:25.210> we<00:07:25.449> have<00:07:25.479> a 00:07:25.890 --> 00:07:25.900 align:start position:0% do we have because I think we have a 00:07:25.900 --> 00:07:27.089 align:start position:0% do we have because I think we have a Java<00:07:26.259> team<00:07:26.590> around 00:07:27.089 --> 00:07:27.099 align:start position:0% Java team around 00:07:27.099 --> 00:07:29.399 align:start position:0% Java team around well<00:07:27.639> we've<00:07:27.789> got<00:07:28.000> go<00:07:28.270> into<00:07:28.750> and<00:07:28.960> some<00:07:29.139> in<00:07:29.259> there 00:07:29.399 --> 00:07:29.409 align:start position:0% well we've got go into and some in there 00:07:29.409 --> 00:07:32.189 align:start position:0% well we've got go into and some in there this<00:07:29.650> is<00:07:29.740> pretty<00:07:29.889> cool<00:07:30.810> so<00:07:31.810> what's<00:07:31.960> good<00:07:32.110> about 00:07:32.189 --> 00:07:32.199 align:start position:0% this is pretty cool so what's good about 00:07:32.199 --> 00:07:33.600 align:start position:0% this is pretty cool so what's good about this<00:07:32.469> is<00:07:32.530> that<00:07:32.650> although<00:07:33.310> these 00:07:33.600 --> 00:07:33.610 align:start position:0% this is that although these 00:07:33.610 --> 00:07:35.070 align:start position:0% this is that although these implementations<00:07:34.270> actually<00:07:34.539> deployed<00:07:34.810> with<00:07:34.990> a 00:07:35.070 --> 00:07:35.080 align:start position:0% implementations actually deployed with a 00:07:35.080 --> 00:07:36.480 align:start position:0% implementations actually deployed with a lady<00:07:35.259> to<00:07:35.409> be<00:07:35.469> specifications<00:07:36.189> so<00:07:36.310> they're 00:07:36.480 --> 00:07:36.490 align:start position:0% lady to be specifications so they're 00:07:36.490 --> 00:07:38.550 align:start position:0% lady to be specifications so they're interoperable<00:07:37.030> with<00:07:37.090> one<00:07:37.930> another<00:07:38.229> they<00:07:38.530> are 00:07:38.550 --> 00:07:38.560 align:start position:0% interoperable with one another they are 00:07:38.560 --> 00:07:40.950 align:start position:0% interoperable with one another they are at<00:07:39.460> different<00:07:39.669> levels<00:07:39.879> of<00:07:40.150> maturity<00:07:40.330> so<00:07:40.840> the 00:07:40.950 --> 00:07:40.960 align:start position:0% at different levels of maturity so the 00:07:40.960 --> 00:07:42.990 align:start position:0% at different levels of maturity so the three<00:07:41.349> most<00:07:41.710> mature<00:07:42.009> works<00:07:42.400> that<00:07:42.580> we<00:07:42.669> consider 00:07:42.990 --> 00:07:43.000 align:start position:0% three most mature works that we consider 00:07:43.000 --> 00:07:46.740 align:start position:0% three most mature works that we consider are<00:07:43.120> Jas<00:07:43.930> go<00:07:44.259> and<00:07:44.560> Russ<00:07:44.770> and<00:07:45.069> pilot<00:07:45.939> to<00:07:46.120> be<00:07:46.240> JVM 00:07:46.740 --> 00:07:46.750 align:start position:0% are Jas go and Russ and pilot to be JVM 00:07:46.750 --> 00:07:50.159 align:start position:0% are Jas go and Russ and pilot to be JVM and<00:07:47.080> nib<00:07:47.530> are<00:07:47.830> mostly<00:07:48.669> driven<00:07:49.030> by<00:07:49.210> the<00:07:49.569> theory 00:07:50.159 --> 00:07:50.169 align:start position:0% and nib are mostly driven by the theory 00:07:50.169 --> 00:07:53.100 align:start position:0% and nib are mostly driven by the theory to<00:07:50.500> project<00:07:50.979> and<00:07:51.729> CBD<00:07:52.090> that<00:07:52.330> to<00:07:52.689> be<00:07:52.810> it<00:07:52.960> is 00:07:53.100 --> 00:07:53.110 align:start position:0% to project and CBD that to be it is 00:07:53.110 --> 00:07:55.080 align:start position:0% to project and CBD that to be it is driven<00:07:53.349> by<00:07:53.529> the<00:07:53.650> bulk<00:07:53.949> of<00:07:54.009> our<00:07:54.159> project<00:07:54.520> so 00:07:55.080 --> 00:07:55.090 align:start position:0% driven by the bulk of our project so 00:07:55.090 --> 00:07:57.629 align:start position:0% driven by the bulk of our project so this<00:07:55.360> is<00:07:55.479> prequel<00:07:55.870> and<00:07:56.219> most<00:07:57.219> great<00:07:57.430> about 00:07:57.629 --> 00:07:57.639 align:start position:0% this is prequel and most great about 00:07:57.639 --> 00:07:59.279 align:start position:0% this is prequel and most great about this<00:07:57.819> is<00:07:58.000> that<00:07:58.029> YouTube's<00:07:58.509> going<00:07:58.629> to<00:07:58.840> jump<00:07:59.080> in 00:07:59.279 --> 00:07:59.289 align:start position:0% this is that YouTube's going to jump in 00:07:59.289 --> 00:08:01.980 align:start position:0% this is that YouTube's going to jump in a<00:07:59.319> way<00:07:59.590> also<00:08:00.000> targets<00:08:01.000> specialized 00:08:01.980 --> 00:08:01.990 align:start position:0% a way also targets specialized 00:08:01.990 --> 00:08:04.350 align:start position:0% a way also targets specialized environments<00:08:02.710> right<00:08:02.979> so<00:08:03.310> in<00:08:03.909> the<00:08:04.120> case<00:08:04.330> of 00:08:04.350 --> 00:08:04.360 align:start position:0% environments right so in the case of 00:08:04.360 --> 00:08:06.480 align:start position:0% environments right so in the case of nineveh<00:08:05.020> to<00:08:05.229> be<00:08:05.409> they<00:08:05.740> are<00:08:05.889> making<00:08:06.189> a<00:08:06.370> strong 00:08:06.480 --> 00:08:06.490 align:start position:0% nineveh to be they are making a strong 00:08:06.490 --> 00:08:08.100 align:start position:0% nineveh to be they are making a strong effort<00:08:06.610> to<00:08:07.120> target<00:08:07.330> embedded<00:08:07.960> and 00:08:08.100 --> 00:08:08.110 align:start position:0% effort to target embedded and 00:08:08.110 --> 00:08:09.899 align:start position:0% effort to target embedded and constrained<00:08:08.469> devices<00:08:08.770> right<00:08:09.279> in<00:08:09.460> the<00:08:09.550> case<00:08:09.699> of 00:08:09.899 --> 00:08:09.909 align:start position:0% constrained devices right in the case of 00:08:09.909 --> 00:08:11.550 align:start position:0% constrained devices right in the case of JVM<00:08:10.360> they<00:08:10.509> need<00:08:10.629> to<00:08:10.719> be<00:08:10.840> right<00:08:11.110> now<00:08:11.139> with<00:08:11.469> the 00:08:11.550 --> 00:08:11.560 align:start position:0% JVM they need to be right now with the 00:08:11.560 --> 00:08:14.670 align:start position:0% JVM they need to be right now with the current<00:08:11.740> version<00:08:12.060> it<00:08:13.060> is<00:08:13.689> a<00:08:13.719> java<00:08:14.139> proposition 00:08:14.670 --> 00:08:14.680 align:start position:0% current version it is a java proposition 00:08:14.680 --> 00:08:16.920 align:start position:0% current version it is a java proposition but<00:08:14.800> in<00:08:14.919> the<00:08:15.039> next<00:08:15.340> Gration<00:08:15.789> it<00:08:16.000> would<00:08:16.120> be<00:08:16.270> very 00:08:16.920 --> 00:08:16.930 align:start position:0% but in the next Gration it would be very 00:08:16.930 --> 00:08:18.749 align:start position:0% but in the next Gration it would be very here<00:08:17.379> to<00:08:17.560> load<00:08:17.680> time<00:08:17.919> during<00:08:18.189> the<00:08:18.340> strong 00:08:18.749 --> 00:08:18.759 align:start position:0% here to load time during the strong 00:08:18.759 --> 00:08:20.909 align:start position:0% here to load time during the strong alright<00:08:19.060> so<00:08:19.240> this<00:08:19.330> is<00:08:19.509> uh<00:08:19.539> this<00:08:19.900> is<00:08:20.139> you<00:08:20.830> know 00:08:20.909 --> 00:08:20.919 align:start position:0% alright so this is uh this is you know 00:08:20.919 --> 00:08:23.279 align:start position:0% alright so this is uh this is you know this<00:08:21.219> is<00:08:21.279> brief<00:08:21.520> I'm<00:08:22.000> very<00:08:22.180> happy<00:08:22.389> rise<00:08:22.599> okay 00:08:23.279 --> 00:08:23.289 align:start position:0% this is brief I'm very happy rise okay 00:08:23.289 --> 00:08:26.850 align:start position:0% this is brief I'm very happy rise okay so<00:08:23.379> in<00:08:23.919> terms<00:08:24.159> of<00:08:24.370> adoption<00:08:25.240> the<00:08:25.960> adoption<00:08:26.560> of 00:08:26.850 --> 00:08:26.860 align:start position:0% so in terms of adoption the adoption of 00:08:26.860 --> 00:08:28.350 align:start position:0% so in terms of adoption the adoption of they<00:08:27.099> need<00:08:27.250> to<00:08:27.310> be<00:08:27.430> over<00:08:27.669> the<00:08:27.759> last<00:08:27.940> few<00:08:28.150> miles 00:08:28.350 --> 00:08:28.360 align:start position:0% they need to be over the last few miles 00:08:28.360 --> 00:08:31.110 align:start position:0% they need to be over the last few miles us<00:08:28.629> so<00:08:29.259> I<00:08:29.310> anticipate 00:08:31.110 --> 00:08:31.120 align:start position:0% us so I anticipate 00:08:31.120 --> 00:08:32.969 align:start position:0% us so I anticipate gonna<00:08:31.479> make<00:08:31.659> a<00:08:31.690> network<00:08:32.019> network<00:08:32.469> effects 00:08:32.969 --> 00:08:32.979 align:start position:0% gonna make a network network effects 00:08:32.979 --> 00:08:35.279 align:start position:0% gonna make a network network effects it's<00:08:33.190> been<00:08:33.310> amazing<00:08:33.550> so<00:08:34.180> what's<00:08:35.050> cool<00:08:35.229> about 00:08:35.279 --> 00:08:35.289 align:start position:0% it's been amazing so what's cool about 00:08:35.289 --> 00:08:37.469 align:start position:0% it's been amazing so what's cool about so<00:08:35.709> here<00:08:35.979> you<00:08:36.159> gonna<00:08:36.370> if<00:08:36.550> you're<00:08:37.180> not<00:08:37.300> doing 00:08:37.469 --> 00:08:37.479 align:start position:0% so here you gonna if you're not doing 00:08:37.479 --> 00:08:40.290 align:start position:0% so here you gonna if you're not doing something<00:08:38.159> worth<00:08:39.159> mentioning<00:08:39.729> of<00:08:40.120> course 00:08:40.290 --> 00:08:40.300 align:start position:0% something worth mentioning of course 00:08:40.300 --> 00:08:42.760 align:start position:0% something worth mentioning of course well<00:08:40.510> kind<00:08:40.690> of<00:08:40.719> a<00:08:40.930> theory<00:08:41.199> and<00:08:41.349> why<00:08:41.500> would<00:08:41.740> I<00:08:41.829> be 00:08:42.760 --> 00:08:42.770 align:start position:0% well kind of a theory and why would I be 00:08:42.770 --> 00:08:44.530 align:start position:0% well kind of a theory and why would I be they're<00:08:43.100> kind<00:08:43.280> of<00:08:43.340> like<00:08:43.400> the<00:08:43.670> top<00:08:44.120> ones<00:08:44.360> over 00:08:44.530 --> 00:08:44.540 align:start position:0% they're kind of like the top ones over 00:08:44.540 --> 00:08:46.240 align:start position:0% they're kind of like the top ones over there<00:08:44.690> and<00:08:44.990> that<00:08:45.110> there<00:08:45.290> is<00:08:45.380> zero<00:08:45.980> expense 00:08:46.240 --> 00:08:46.250 align:start position:0% there and that there is zero expense 00:08:46.250 --> 00:08:47.830 align:start position:0% there and that there is zero expense during<00:08:46.370> the<00:08:46.580> bottles<00:08:47.000> and<00:08:47.150> stuff<00:08:47.360> will<00:08:47.750> be 00:08:47.830 --> 00:08:47.840 align:start position:0% during the bottles and stuff will be 00:08:47.840 --> 00:08:49.510 align:start position:0% during the bottles and stuff will be retired<00:08:48.170> they<00:08:48.320> have<00:08:48.410> created<00:08:48.590> nothing<00:08:49.340> in 00:08:49.510 --> 00:08:49.520 align:start position:0% retired they have created nothing in 00:08:49.520 --> 00:08:51.130 align:start position:0% retired they have created nothing in transport<00:08:49.970> from<00:08:50.090> the<00:08:50.150> b2b<00:08:50.450> and<00:08:50.660> that's<00:08:50.930> what's 00:08:51.130 --> 00:08:51.140 align:start position:0% transport from the b2b and that's what's 00:08:51.140 --> 00:08:53.920 align:start position:0% transport from the b2b and that's what's cool<00:08:51.440> about<00:08:51.500> all<00:08:52.310> this<00:08:53.000> fraction<00:08:53.390> and<00:08:53.480> having 00:08:53.920 --> 00:08:53.930 align:start position:0% cool about all this fraction and having 00:08:53.930 --> 00:08:55.840 align:start position:0% cool about all this fraction and having me<00:08:54.140> basically<00:08:55.040> having<00:08:55.430> a<00:08:55.520> bunch<00:08:55.730> of 00:08:55.840 --> 00:08:55.850 align:start position:0% me basically having a bunch of 00:08:55.850 --> 00:08:59.590 align:start position:0% me basically having a bunch of communities<00:08:56.890> that<00:08:57.890> when<00:08:58.370> you<00:08:58.490> look<00:08:58.700> at<00:08:59.240> how 00:08:59.590 --> 00:08:59.600 align:start position:0% communities that when you look at how 00:08:59.600 --> 00:09:01.000 align:start position:0% communities that when you look at how they<00:08:59.780> would<00:08:59.900> have<00:09:00.020> build<00:09:00.230> their<00:09:00.530> networking 00:09:01.000 --> 00:09:01.010 align:start position:0% they would have build their networking 00:09:01.010 --> 00:09:03.640 align:start position:0% they would have build their networking layers<00:09:01.340> from<00:09:01.790> scratch<00:09:02.180> they<00:09:02.870> would<00:09:03.050> have<00:09:03.140> they 00:09:03.640 --> 00:09:03.650 align:start position:0% layers from scratch they would have they 00:09:03.650 --> 00:09:05.380 align:start position:0% layers from scratch they would have they would<00:09:03.680> have<00:09:03.830> looked<00:09:04.190> a<00:09:04.490> lot<00:09:04.760> of<00:09:04.940> like<00:09:05.090> one 00:09:05.380 --> 00:09:05.390 align:start position:0% would have looked a lot of like one 00:09:05.390 --> 00:09:07.210 align:start position:0% would have looked a lot of like one another<00:09:05.690> right<00:09:06.020> because<00:09:06.350> this<00:09:06.470> they<00:09:06.950> don't 00:09:07.210 --> 00:09:07.220 align:start position:0% another right because this they don't 00:09:07.220 --> 00:09:08.850 align:start position:0% another right because this they don't share<00:09:07.430> the<00:09:07.520> same<00:09:07.580> assets<00:09:08.210> right<00:09:08.420> so 00:09:08.850 --> 00:09:08.860 align:start position:0% share the same assets right so 00:09:08.860 --> 00:09:11.080 align:start position:0% share the same assets right so connectivity<00:09:09.860> addressing<00:09:10.430> video<00:09:10.730> discovery 00:09:11.080 --> 00:09:11.090 align:start position:0% connectivity addressing video discovery 00:09:11.090 --> 00:09:13.450 align:start position:0% connectivity addressing video discovery NAT<00:09:11.480> traversal<00:09:11.620> these<00:09:12.620> are<00:09:12.800> things<00:09:13.070> that<00:09:13.250> a 00:09:13.450 --> 00:09:13.460 align:start position:0% NAT traversal these are things that a 00:09:13.460 --> 00:09:15.040 align:start position:0% NAT traversal these are things that a comment<00:09:13.730> across<00:09:14.030> state<00:09:14.270> across<00:09:14.690> the<00:09:14.750> arrow 00:09:15.040 --> 00:09:15.050 align:start position:0% comment across state across the arrow 00:09:15.050 --> 00:09:17.140 align:start position:0% comment across state across the arrow system<00:09:15.530> right<00:09:15.770> so<00:09:16.280> there's<00:09:16.430> no<00:09:16.550> point<00:09:16.700> we<00:09:16.910> can 00:09:17.140 --> 00:09:17.150 align:start position:0% system right so there's no point we can 00:09:17.150 --> 00:09:18.460 align:start position:0% system right so there's no point we can take<00:09:17.300> the<00:09:17.390> wheel<00:09:17.540> and<00:09:17.750> at<00:09:18.050> each<00:09:18.200> of<00:09:18.380> these 00:09:18.460 --> 00:09:18.470 align:start position:0% take the wheel and at each of these 00:09:18.470 --> 00:09:19.660 align:start position:0% take the wheel and at each of these projects<00:09:18.920> and<00:09:19.070> what's<00:09:19.190> cool<00:09:19.340> is<00:09:19.370> that 00:09:19.660 --> 00:09:19.670 align:start position:0% projects and what's cool is that 00:09:19.670 --> 00:09:20.860 align:start position:0% projects and what's cool is that well<00:09:20.000> these<00:09:20.210> projects<00:09:20.570> are<00:09:20.750> now 00:09:20.860 --> 00:09:20.870 align:start position:0% well these projects are now 00:09:20.870 --> 00:09:22.120 align:start position:0% well these projects are now collaborating<00:09:21.140> with<00:09:21.620> the<00:09:21.680> lipids<00:09:21.950> of<00:09:22.010> the 00:09:22.120 --> 00:09:22.130 align:start position:0% collaborating with the lipids of the 00:09:22.130 --> 00:09:25.990 align:start position:0% collaborating with the lipids of the open<00:09:22.400> community<00:09:22.760> to<00:09:24.070> do<00:09:25.070> all<00:09:25.250> the<00:09:25.400> brains<00:09:25.640> and 00:09:25.990 --> 00:09:26.000 align:start position:0% open community to do all the brains and 00:09:26.000 --> 00:09:27.630 align:start position:0% open community to do all the brains and the<00:09:26.240> hands<00:09:26.510> to<00:09:26.780> build<00:09:26.930> a<00:09:27.110> rock-solid 00:09:27.630 --> 00:09:27.640 align:start position:0% the hands to build a rock-solid 00:09:27.640 --> 00:09:30.820 align:start position:0% the hands to build a rock-solid networking<00:09:28.640> foundation<00:09:29.150> and<00:09:29.620> what's<00:09:30.620> great 00:09:30.820 --> 00:09:30.830 align:start position:0% networking foundation and what's great 00:09:30.830 --> 00:09:32.710 align:start position:0% networking foundation and what's great is<00:09:30.980> that<00:09:31.010> most<00:09:31.970> of<00:09:32.090> these<00:09:32.210> planets<00:09:32.450> are 00:09:32.710 --> 00:09:32.720 align:start position:0% is that most of these planets are 00:09:32.720 --> 00:09:34.930 align:start position:0% is that most of these planets are actually<00:09:32.780> contributing<00:09:33.200> activity<00:09:33.890> to<00:09:34.070> so<00:09:34.880> I'm 00:09:34.930 --> 00:09:34.940 align:start position:0% actually contributing activity to so I'm 00:09:34.940 --> 00:09:36.280 align:start position:0% actually contributing activity to so I'm not<00:09:35.090> just<00:09:35.150> using<00:09:35.570> the<00:09:35.690> technology<00:09:36.170> that 00:09:36.280 --> 00:09:36.290 align:start position:0% not just using the technology that 00:09:36.290 --> 00:09:40.030 align:start position:0% not just using the technology that actually<00:09:36.470> introduced<00:09:37.040> a<00:09:37.900> few<00:09:38.900> weeks<00:09:39.470> ago<00:09:39.650> we 00:09:40.030 --> 00:09:40.040 align:start position:0% actually introduced a few weeks ago we 00:09:40.040 --> 00:09:43.630 align:start position:0% actually introduced a few weeks ago we also<00:09:40.190> saw<00:09:40.490> the<00:09:40.910> 7-way<00:09:41.720> Interop<00:09:42.620> lid<00:09:43.190> off<00:09:43.400> of 00:09:43.630 --> 00:09:43.640 align:start position:0% also saw the 7-way Interop lid off of 00:09:43.640 --> 00:09:47.410 align:start position:0% also saw the 7-way Interop lid off of the<00:09:44.180> earth<00:09:44.900> 2.0<00:09:45.620> project<00:09:46.580> so<00:09:47.120> a<00:09:47.150> bunch<00:09:47.330> of 00:09:47.410 --> 00:09:47.420 align:start position:0% the earth 2.0 project so a bunch of 00:09:47.420 --> 00:09:49.270 align:start position:0% the earth 2.0 project so a bunch of teams<00:09:47.660> actually<00:09:48.080> lock<00:09:48.230> themselves<00:09:48.410> up<00:09:48.770> in<00:09:49.070> a 00:09:49.270 --> 00:09:49.280 align:start position:0% teams actually lock themselves up in a 00:09:49.280 --> 00:09:52.300 align:start position:0% teams actually lock themselves up in a few<00:09:49.430> comments<00:09:49.790> in<00:09:49.880> Canada<00:09:50.300> and<00:09:50.860> came<00:09:51.860> up<00:09:52.070> with 00:09:52.300 --> 00:09:52.310 align:start position:0% few comments in Canada and came up with 00:09:52.310 --> 00:09:57.130 align:start position:0% few comments in Canada and came up with a<00:09:54.190> network<00:09:55.190> of<00:09:55.550> a<00:09:56.120> living<00:09:56.750> to<00:09:56.840> be<00:09:56.930> based 00:09:57.130 --> 00:09:57.140 align:start position:0% a network of a living to be based 00:09:57.140 --> 00:10:00.580 align:start position:0% a network of a living to be based network<00:09:57.530> of<00:09:57.710> all<00:09:58.070> sending<00:09:58.970> of<00:09:59.360> seven-<00:10:00.350> built 00:10:00.580 --> 00:10:00.590 align:start position:0% network of all sending of seven- built 00:10:00.590 --> 00:10:01.840 align:start position:0% network of all sending of seven- built of<00:10:00.740> different<00:10:01.010> 9<00:10:01.100> inches<00:10:01.340> interactive 00:10:01.840 --> 00:10:01.850 align:start position:0% of different 9 inches interactive 00:10:01.850 --> 00:10:02.470 align:start position:0% of different 9 inches interactive environment 00:10:02.470 --> 00:10:02.480 align:start position:0% environment 00:10:02.480 --> 00:10:04.780 align:start position:0% environment and<00:10:02.570> the<00:10:02.660> president<00:10:03.230> this<00:10:03.320> is<00:10:03.470> nt<00:10:04.130> that<00:10:04.250> was 00:10:04.780 --> 00:10:04.790 align:start position:0% and the president this is nt that was 00:10:04.790 --> 00:10:06.730 align:start position:0% and the president this is nt that was super<00:10:05.329> copyright<00:10:05.779> might<00:10:06.260> tell<00:10:06.500> you're<00:10:06.709> a 00:10:06.730 --> 00:10:06.740 align:start position:0% super copyright might tell you're a 00:10:06.740 --> 00:10:09.569 align:start position:0% super copyright might tell you're a whole<00:10:07.040> other<00:10:07.160> person<00:10:07.519> in<00:10:08.180> this<00:10:08.269> room<00:10:08.449> mmm<00:10:08.810> yeah 00:10:09.569 --> 00:10:09.579 align:start position:0% whole other person in this room mmm yeah 00:10:09.579 --> 00:10:10.810 align:start position:0% whole other person in this room mmm yeah cool 00:10:10.810 --> 00:10:10.820 align:start position:0% cool 00:10:10.820 --> 00:10:13.870 align:start position:0% cool so<00:10:10.970> a<00:10:11.329> few<00:10:11.860> weeks<00:10:12.860> ago<00:10:13.010> we<00:10:13.430> also<00:10:13.550> launched 00:10:13.870 --> 00:10:13.880 align:start position:0% so a few weeks ago we also launched 00:10:13.880 --> 00:10:18.009 align:start position:0% so a few weeks ago we also launched deference<00:10:14.420> and<00:10:14.720> we<00:10:15.649> made<00:10:16.310> so<00:10:17.269> that<00:10:17.300> friends<00:10:17.839> is 00:10:18.009 --> 00:10:18.019 align:start position:0% deference and we made so that friends is 00:10:18.019 --> 00:10:20.590 align:start position:0% deference and we made so that friends is a<00:10:18.529> the<00:10:19.190> place<00:10:19.399> we're<00:10:19.699> going<00:10:19.910> to<00:10:19.970> be<00:10:20.120> publishing 00:10:20.590 --> 00:10:20.600 align:start position:0% a the place we're going to be publishing 00:10:20.600 --> 00:10:22.720 align:start position:0% a the place we're going to be publishing and<00:10:21.380> you<00:10:21.440> can<00:10:21.589> where<00:10:22.310> we're<00:10:22.430> going<00:10:22.579> to<00:10:22.639> be 00:10:22.720 --> 00:10:22.730 align:start position:0% and you can where we're going to be 00:10:22.730 --> 00:10:25.210 align:start position:0% and you can where we're going to be publishing<00:10:22.880> work<00:10:23.360> that<00:10:23.779> we<00:10:24.170> we<00:10:24.680> would<00:10:24.829> like<00:10:25.070> to 00:10:25.210 --> 00:10:25.220 align:start position:0% publishing work that we we would like to 00:10:25.220 --> 00:10:26.710 align:start position:0% publishing work that we we would like to get<00:10:25.370> done<00:10:25.430> but<00:10:25.910> it's<00:10:26.029> also<00:10:26.180> a<00:10:26.300> collaborative 00:10:26.710 --> 00:10:26.720 align:start position:0% get done but it's also a collaborative 00:10:26.720 --> 00:10:28.389 align:start position:0% get done but it's also a collaborative space<00:10:27.110> for<00:10:27.470> different<00:10:27.769> projects<00:10:28.100> across<00:10:28.279> the 00:10:28.389 --> 00:10:28.399 align:start position:0% space for different projects across the 00:10:28.399 --> 00:10:32.439 align:start position:0% space for different projects across the ecosystem<00:10:29.209> to<00:10:29.899> publish<00:10:31.060> items<00:10:32.060> that<00:10:32.240> I<00:10:32.329> would 00:10:32.439 --> 00:10:32.449 align:start position:0% ecosystem to publish items that I would 00:10:32.449 --> 00:10:35.710 align:start position:0% ecosystem to publish items that I would like<00:10:32.630> to<00:10:33.740> and<00:10:33.769> they'd<00:10:34.130> be<00:10:34.250> to<00:10:34.370> me<00:10:34.490> and<00:10:35.420> go 00:10:35.710 --> 00:10:35.720 align:start position:0% like to and they'd be to me and go 00:10:35.720 --> 00:10:37.509 align:start position:0% like to and they'd be to me and go Funko<00:10:36.110> sites<00:10:36.350> and<00:10:36.529> some<00:10:36.709> more<00:10:36.949> funds<00:10:37.190> together 00:10:37.509 --> 00:10:37.519 align:start position:0% Funko sites and some more funds together 00:10:37.519 --> 00:10:40.030 align:start position:0% Funko sites and some more funds together to<00:10:37.820> make<00:10:38.000> sure<00:10:38.510> that<00:10:38.720> those<00:10:38.870> happen<00:10:39.320> and<00:10:39.470> at 00:10:40.030 --> 00:10:40.040 align:start position:0% to make sure that those happen and at 00:10:40.040 --> 00:10:41.710 align:start position:0% to make sure that those happen and at one<00:10:40.250> point<00:10:40.279> we're<00:10:40.910> speaking<00:10:41.089> as<00:10:41.329> well<00:10:41.510> with<00:10:41.690> a 00:10:41.710 --> 00:10:41.720 align:start position:0% one point we're speaking as well with a 00:10:41.720 --> 00:10:45.160 align:start position:0% one point we're speaking as well with a few<00:10:41.870> teams<00:10:42.170> that<00:10:42.290> are<00:10:43.060> gonna<00:10:44.060> help<00:10:44.600> us<00:10:44.839> fund 00:10:45.160 --> 00:10:45.170 align:start position:0% few teams that are gonna help us fund 00:10:45.170 --> 00:10:48.819 align:start position:0% few teams that are gonna help us fund much<00:10:45.500> of<00:10:45.649> this<00:10:45.769> work<00:10:46.010> I<00:10:46.220> had<00:10:46.370> eyes<00:10:47.300> and<00:10:47.720> a<00:10:48.380> few 00:10:48.819 --> 00:10:48.829 align:start position:0% much of this work I had eyes and a few 00:10:48.829 --> 00:10:52.810 align:start position:0% much of this work I had eyes and a few other<00:10:48.980> things<00:10:49.070> we<00:10:49.279> also<00:10:50.110> avoided<00:10:51.110> a<00:10:51.620> bunch<00:10:52.610> of 00:10:52.810 --> 00:10:52.820 align:start position:0% other things we also avoided a bunch of 00:10:52.820 --> 00:10:55.449 align:start position:0% other things we also avoided a bunch of a<00:10:53.240> bunch<00:10:53.600> of<00:10:53.899> bounties<00:10:54.260> that<00:10:54.290> year<00:10:54.589> in<00:10:54.800> it<00:10:54.949> and 00:10:55.449 --> 00:10:55.459 align:start position:0% a bunch of bounties that year in it and 00:10:55.459 --> 00:10:58.470 align:start position:0% a bunch of bounties that year in it and that<00:10:55.550> was<00:10:55.670> huge<00:10:55.820> huge<00:10:56.449> hugely<00:10:57.019> successful 00:10:58.470 --> 00:10:58.480 align:start position:0% that was huge huge hugely successful 00:10:58.480 --> 00:11:01.900 align:start position:0% that was huge huge hugely successful we've<00:10:59.480> also<00:10:59.660> shown<00:10:59.810> a<00:11:00.079> sense<00:11:00.740> thanks<00:11:01.160> this<00:11:01.730> has 00:11:01.900 --> 00:11:01.910 align:start position:0% we've also shown a sense thanks this has 00:11:01.910 --> 00:11:03.550 align:start position:0% we've also shown a sense thanks this has been<00:11:02.120> a<00:11:02.149> long-standing<00:11:02.540> issue<00:11:03.079> for<00:11:03.470> the 00:11:03.550 --> 00:11:03.560 align:start position:0% been a long-standing issue for the 00:11:03.560 --> 00:11:05.620 align:start position:0% been a long-standing issue for the defeat<00:11:03.800> of<00:11:03.829> you<00:11:04.070> project<00:11:04.519> thanks<00:11:05.420> to 00:11:05.620 --> 00:11:05.630 align:start position:0% defeat of you project thanks to 00:11:05.630 --> 00:11:07.990 align:start position:0% defeat of you project thanks to everybody<00:11:06.320> who<00:11:06.620> stopped<00:11:06.860> by<00:11:06.889> us<00:11:07.250> during<00:11:07.880> the 00:11:07.990 --> 00:11:08.000 align:start position:0% everybody who stopped by us during the 00:11:08.000 --> 00:11:09.639 align:start position:0% everybody who stopped by us during the dark<00:11:08.240> times<00:11:08.449> well<00:11:08.779> we<00:11:09.079> didn't<00:11:09.319> have<00:11:09.440> good 00:11:09.639 --> 00:11:09.649 align:start position:0% dark times well we didn't have good 00:11:09.649 --> 00:11:11.199 align:start position:0% dark times well we didn't have good conceptual<00:11:10.010> thoughts<00:11:10.339> we<00:11:10.610> now<00:11:10.819> have<00:11:11.089> an 00:11:11.199 --> 00:11:11.209 align:start position:0% conceptual thoughts we now have an 00:11:11.209 --> 00:11:13.629 align:start position:0% conceptual thoughts we now have an amazing<00:11:11.860> thing<00:11:12.860> that<00:11:12.889> we<00:11:13.010> to<00:11:13.160> be<00:11:13.310> though<00:11:13.430> our 00:11:13.629 --> 00:11:13.639 align:start position:0% amazing thing that we to be though our 00:11:13.639 --> 00:11:16.900 align:start position:0% amazing thing that we to be though our website<00:11:14.180> were<00:11:15.110> engaged<00:11:16.010> in<00:11:16.160> a<00:11:16.220> full<00:11:16.459> specs<00:11:16.730> we 00:11:16.900 --> 00:11:16.910 align:start position:0% website were engaged in a full specs we 00:11:16.910 --> 00:11:19.059 align:start position:0% website were engaged in a full specs we write<00:11:17.120> to<00:11:17.269> make<00:11:17.420> sure<00:11:17.569> that<00:11:17.810> the<00:11:17.990> sex<00:11:18.740> actually 00:11:19.059 --> 00:11:19.069 align:start position:0% write to make sure that the sex actually 00:11:19.069 --> 00:11:20.199 align:start position:0% write to make sure that the sex actually matched<00:11:19.370> and<00:11:19.730> they're<00:11:19.850> agreeable 00:11:20.199 --> 00:11:20.209 align:start position:0% matched and they're agreeable 00:11:20.209 --> 00:11:22.780 align:start position:0% matched and they're agreeable implementations<00:11:21.079> we've<00:11:22.069> created<00:11:22.279> a<00:11:22.550> specs 00:11:22.780 --> 00:11:22.790 align:start position:0% implementations we've created a specs 00:11:22.790 --> 00:11:24.670 align:start position:0% implementations we've created a specs maturity<00:11:23.269> cycle<00:11:23.420> we're<00:11:23.959> defining<00:11:24.170> an<00:11:24.410> IRC 00:11:24.670 --> 00:11:24.680 align:start position:0% maturity cycle we're defining an IRC 00:11:24.680 --> 00:11:26.680 align:start position:0% maturity cycle we're defining an IRC process<00:11:25.160> and<00:11:25.310> we're<00:11:25.430> maturing<00:11:25.880> and<00:11:26.180> a<00:11:26.240> lot<00:11:26.389> in 00:11:26.680 --> 00:11:26.690 align:start position:0% process and we're maturing and a lot in 00:11:26.690 --> 00:11:29.170 align:start position:0% process and we're maturing and a lot in terms<00:11:26.870> of<00:11:27.220> you<00:11:28.220> know<00:11:28.250> things<00:11:28.670> that<00:11:28.760> are<00:11:28.880> just 00:11:29.170 --> 00:11:29.180 align:start position:0% terms of you know things that are just 00:11:29.180 --> 00:11:31.960 align:start position:0% terms of you know things that are just not<00:11:29.300> cool<00:11:29.630> right<00:11:30.560> so<00:11:30.620> he<00:11:30.860> says<00:11:31.069> Morgan's<00:11:31.670> in 00:11:31.960 --> 00:11:31.970 align:start position:0% not cool right so he says Morgan's in 00:11:31.970 --> 00:11:37.840 align:start position:0% not cool right so he says Morgan's in apartments 00:11:37.840 --> 00:11:37.850 align:start position:0% 00:11:37.850 --> 00:11:40.480 align:start position:0% we've<00:11:38.570> lost<00:11:38.870> the<00:11:39.620> discussion<00:11:40.040> forums<00:11:40.310> as<00:11:40.460> well 00:11:40.480 --> 00:11:40.490 align:start position:0% we've lost the discussion forums as well 00:11:40.490 --> 00:11:42.070 align:start position:0% we've lost the discussion forums as well so<00:11:40.790> you've<00:11:40.910> got<00:11:41.090> this<00:11:41.330> custom<00:11:41.720> that<00:11:41.840> we<00:11:41.870> could 00:11:42.070 --> 00:11:42.080 align:start position:0% so you've got this custom that we could 00:11:42.080 --> 00:11:44.830 align:start position:0% so you've got this custom that we could be<00:11:42.140> done<00:11:42.320> I<00:11:42.410> know<00:11:42.470> so<00:11:42.920> if<00:11:43.640> you<00:11:43.910> have<00:11:44.210> any<00:11:44.450> usage 00:11:44.830 --> 00:11:44.840 align:start position:0% be done I know so if you have any usage 00:11:44.840 --> 00:11:46.150 align:start position:0% be done I know so if you have any usage questions<00:11:45.320> if<00:11:45.530> you<00:11:45.620> want<00:11:45.800> to<00:11:45.860> start<00:11:46.010> a 00:11:46.150 --> 00:11:46.160 align:start position:0% questions if you want to start a 00:11:46.160 --> 00:11:48.160 align:start position:0% questions if you want to start a discussion<00:11:46.190> about<00:11:46.910> things<00:11:47.690> that<00:11:47.930> I'm<00:11:48.050> not 00:11:48.160 --> 00:11:48.170 align:start position:0% discussion about things that I'm not 00:11:48.170 --> 00:11:50.530 align:start position:0% discussion about things that I'm not necessarily<00:11:48.410> bugs<00:11:49.250> or<00:11:49.730> change<00:11:50.000> requests<00:11:50.420> and 00:11:50.530 --> 00:11:50.540 align:start position:0% necessarily bugs or change requests and 00:11:50.540 --> 00:11:52.030 align:start position:0% necessarily bugs or change requests and so<00:11:50.660> on<00:11:50.810> and<00:11:50.990> code<00:11:51.140> this<00:11:51.320> is<00:11:51.470> the<00:11:51.500> place<00:11:51.770> to<00:11:51.920> go 00:11:52.030 --> 00:11:52.040 align:start position:0% so on and code this is the place to go 00:11:52.040 --> 00:11:54.880 align:start position:0% so on and code this is the place to go and<00:11:52.070> I'm<00:11:52.280> really<00:11:52.490> good<00:11:52.670> health<00:11:52.910> and<00:11:53.150> we<00:11:54.140> share 00:11:54.880 --> 00:11:54.890 align:start position:0% and I'm really good health and we share 00:11:54.890 --> 00:11:56.830 align:start position:0% and I'm really good health and we share too<00:11:55.070> much<00:11:55.100> features<00:11:55.700> as<00:11:55.850> well<00:11:56.030> right<00:11:56.330> so<00:11:56.360> this 00:11:56.830 --> 00:11:56.840 align:start position:0% too much features as well right so this 00:11:56.840 --> 00:11:58.510 align:start position:0% too much features as well right so this is<00:11:56.900> just<00:11:57.050> the<00:11:57.530> list<00:11:57.740> of<00:11:57.920> the<00:11:58.040> ones<00:11:58.220> that<00:11:58.400> came 00:11:58.510 --> 00:11:58.520 align:start position:0% is just the list of the ones that came 00:11:58.520 --> 00:12:00.370 align:start position:0% is just the list of the ones that came to<00:11:58.700> mind<00:11:58.880> we've<00:11:59.210> got<00:11:59.420> what<00:11:59.660> tonight<00:11:59.990> want<00:12:00.290> to 00:12:00.370 --> 00:12:00.380 align:start position:0% to mind we've got what tonight want to 00:12:00.380 --> 00:12:03.490 align:start position:0% to mind we've got what tonight want to read<00:12:00.560> a<00:12:00.970> recreated<00:12:01.970> a<00:12:02.300> automated<00:12:03.050> experiment 00:12:03.490 --> 00:12:03.500 align:start position:0% read a recreated a automated experiment 00:12:03.500 --> 00:12:04.570 align:start position:0% read a recreated a automated experiment so<00:12:03.590> we<00:12:03.740> don't<00:12:04.040> you<00:12:04.190> know<00:12:04.280> to<00:12:04.430> really 00:12:04.570 --> 00:12:04.580 align:start position:0% so we don't you know to really 00:12:04.580 --> 00:12:06.490 align:start position:0% so we don't you know to really experiment<00:12:04.940> and<00:12:05.240> my<00:12:05.330> BFS<00:12:05.690> got<00:12:05.960> married<00:12:06.290> a 00:12:06.490 --> 00:12:06.500 align:start position:0% experiment and my BFS got married a 00:12:06.500 --> 00:12:09.360 align:start position:0% experiment and my BFS got married a bunch<00:12:06.920> of<00:12:06.980> memories<00:12:07.280> from<00:12:07.430> that<00:12:07.780> ts1<00:12:08.780> going<00:12:09.110> to 00:12:09.360 --> 00:12:09.370 align:start position:0% bunch of memories from that ts1 going to 00:12:09.370 --> 00:12:11.680 align:start position:0% bunch of memories from that ts1 going to experimentation<00:12:10.370> going<00:12:10.640> to<00:12:10.880> be<00:12:10.970> to<00:12:11.090> be<00:12:11.240> print 00:12:11.680 --> 00:12:11.690 align:start position:0% experimentation going to be to be print 00:12:11.690 --> 00:12:13.750 align:start position:0% experimentation going to be to be print transported<00:12:12.290> with<00:12:12.470> drive<00:12:12.650> 22<00:12:13.040> really<00:12:13.370> support 00:12:13.750 --> 00:12:13.760 align:start position:0% transported with drive 22 really support 00:12:13.760 --> 00:12:15.610 align:start position:0% transported with drive 22 really support way<00:12:14.330> variety<00:12:14.630> scenario<00:12:15.050> transport<00:12:15.470> with 00:12:15.610 --> 00:12:15.620 align:start position:0% way variety scenario transport with 00:12:15.620 --> 00:12:17.830 align:start position:0% way variety scenario transport with worship<00:12:15.890> which<00:12:16.070> was<00:12:16.280> actually<00:12:16.660> promoted<00:12:17.660> and 00:12:17.830 --> 00:12:17.840 align:start position:0% worship which was actually promoted and 00:12:17.840 --> 00:12:21.070 align:start position:0% worship which was actually promoted and created<00:12:18.320> by<00:12:18.350> the<00:12:19.040> fortes<00:12:19.600> 0x 00:12:21.070 --> 00:12:21.080 align:start position:0% created by the fortes 0x 00:12:21.080 --> 00:12:23.680 align:start position:0% created by the fortes 0x I<00:12:21.110> think<00:12:21.770> the<00:12:21.830> here<00:12:22.270> brought<00:12:23.270> the<00:12:23.480> problem 00:12:23.680 --> 00:12:23.690 align:start position:0% I think the here brought the problem 00:12:23.690 --> 00:12:26.050 align:start position:0% I think the here brought the problem piece<00:12:23.990> wasn't<00:12:24.620> employment<00:12:25.130> so<00:12:25.520> presently 00:12:26.050 --> 00:12:26.060 align:start position:0% piece wasn't employment so presently 00:12:26.060 --> 00:12:27.640 align:start position:0% piece wasn't employment so presently schools<00:12:26.390> and<00:12:26.570> departments<00:12:26.660> of<00:12:27.140> rustic<00:12:27.500> need 00:12:27.640 --> 00:12:27.650 align:start position:0% schools and departments of rustic need 00:12:27.650 --> 00:12:29.620 align:start position:0% schools and departments of rustic need to<00:12:27.710> be<00:12:27.830> included<00:12:28.160> with<00:12:28.400> me<00:12:28.550> as<00:12:28.790> well<00:12:29.000> with<00:12:29.600> a 00:12:29.620 --> 00:12:29.630 align:start position:0% to be included with me as well with a 00:12:29.630 --> 00:12:31.330 align:start position:0% to be included with me as well with a lot<00:12:29.840> of<00:12:29.870> support<00:12:30.080> from<00:12:30.320> the<00:12:30.470> 0x<00:12:30.830> guys<00:12:31.040> what<00:12:31.280> I 00:12:31.330 --> 00:12:31.340 align:start position:0% lot of support from the 0x guys what I 00:12:31.340 --> 00:12:34.480 align:start position:0% lot of support from the 0x guys what I see<00:12:31.520> in<00:12:31.580> the<00:12:31.670> room<00:12:31.790> as<00:12:31.940> well<00:12:32.980> great<00:12:33.980> concepts 00:12:34.480 --> 00:12:34.490 align:start position:0% see in the room as well great concepts 00:12:34.490 --> 00:12:37.330 align:start position:0% see in the room as well great concepts of<00:12:34.610> support<00:12:35.230> that<00:12:36.230> was<00:12:36.410> created<00:12:36.800> by<00:12:36.830> by<00:12:37.280> the 00:12:37.330 --> 00:12:37.340 align:start position:0% of support that was created by by the 00:12:37.340 --> 00:12:40.870 align:start position:0% of support that was created by by the guys<00:12:37.550> at<00:12:37.580> Sigma<00:12:37.940> brain<00:12:38.270> a<00:12:38.510> rest<00:12:39.310> so<00:12:40.310> taking<00:12:40.790> the 00:12:40.870 --> 00:12:40.880 align:start position:0% guys at Sigma brain a rest so taking the 00:12:40.880 --> 00:12:42.580 align:start position:0% guys at Sigma brain a rest so taking the reference<00:12:41.210> teacher<00:12:41.690> home<00:12:41.930> ability<00:12:42.350> to<00:12:42.470> be 00:12:42.580 --> 00:12:42.590 align:start position:0% reference teacher home ability to be 00:12:42.590 --> 00:12:45.850 align:start position:0% reference teacher home ability to be imported<00:12:43.040> over<00:12:43.370> to<00:12:43.490> Russ<00:12:43.700> as<00:12:44.660> well<00:12:45.050> as<00:12:45.410> the 00:12:45.850 --> 00:12:45.860 align:start position:0% imported over to Russ as well as the 00:12:45.860 --> 00:12:48.610 align:start position:0% imported over to Russ as well as the guys<00:12:46.040> from<00:12:46.250> Trinity<00:12:46.580> who<00:12:47.090> did<00:12:47.720> the<00:12:47.840> work<00:12:48.050> for<00:12:48.350> a 00:12:48.610 --> 00:12:48.620 align:start position:0% guys from Trinity who did the work for a 00:12:48.620 --> 00:12:50.740 align:start position:0% guys from Trinity who did the work for a JSA<00:12:49.130> before<00:12:49.490> AJ<00:12:49.640> SNP<00:12:50.000> to<00:12:50.060> be<00:12:50.210> and<00:12:50.510> there<00:12:50.630> are 00:12:50.740 --> 00:12:50.750 align:start position:0% JSA before AJ SNP to be and there are 00:12:50.750 --> 00:12:52.960 align:start position:0% JSA before AJ SNP to be and there are the<00:12:50.930> bank<00:12:51.110> amazing 00:12:52.960 --> 00:12:52.970 align:start position:0% the bank amazing 00:12:52.970 --> 00:12:54.520 align:start position:0% the bank amazing we<00:12:53.570> also<00:12:53.750> should<00:12:53.960> know<00:12:54.110> that<00:12:54.230> we<00:12:54.320> to<00:12:54.440> be 00:12:54.520 --> 00:12:54.530 align:start position:0% we also should know that we to be 00:12:54.530 --> 00:12:56.230 align:start position:0% we also should know that we to be teaming<00:12:54.890> we<00:12:55.520> have<00:12:55.700> three<00:12:55.850> facts<00:12:56.120> with<00:12:56.210> the 00:12:56.230 --> 00:12:56.240 align:start position:0% teaming we have three facts with the 00:12:56.240 --> 00:12:57.850 align:start position:0% teaming we have three facts with the insta-fix<00:12:56.510> is<00:12:56.870> going<00:12:57.050> to<00:12:57.140> be<00:12:57.260> 2<00:12:57.380> p.m.<00:12:57.710> and 00:12:57.850 --> 00:12:57.860 align:start position:0% insta-fix is going to be 2 p.m. and 00:12:57.860 --> 00:13:01.270 align:start position:0% insta-fix is going to be 2 p.m. and adopted<00:12:58.250> go<00:12:58.400> bond<00:12:58.810> there<00:12:59.810> is<00:12:59.960> a<00:13:00.320> up-and-coming 00:13:01.270 --> 00:13:01.280 align:start position:0% adopted go bond there is a up-and-coming 00:13:01.280 --> 00:13:02.800 align:start position:0% adopted go bond there is a up-and-coming Bluetooth<00:13:01.730> transport<00:13:02.270> that<00:13:02.480> has<00:13:02.630> been 00:13:02.800 --> 00:13:02.810 align:start position:0% Bluetooth transport that has been 00:13:02.810 --> 00:13:06.280 align:start position:0% Bluetooth transport that has been created<00:13:03.020> by<00:13:03.410> a<00:13:03.740> team<00:13:04.220> of<00:13:05.210> French<00:13:05.780> Jean<00:13:06.020> that's 00:13:06.280 --> 00:13:06.290 align:start position:0% created by a team of French Jean that's 00:13:06.290 --> 00:13:08.290 align:start position:0% created by a team of French Jean that's one<00:13:06.500> of<00:13:06.560> our<00:13:06.710> team<00:13:06.920> who<00:13:07.190> are<00:13:07.610> building<00:13:07.940> a 00:13:08.290 --> 00:13:08.300 align:start position:0% one of our team who are building a 00:13:08.300 --> 00:13:11.170 align:start position:0% one of our team who are building a decentralized<00:13:08.960> peer-to-peer<00:13:10.090> often<00:13:11.090> I'm 00:13:11.170 --> 00:13:11.180 align:start position:0% decentralized peer-to-peer often I'm 00:13:11.180 --> 00:13:14.440 align:start position:0% decentralized peer-to-peer often I'm first<00:13:11.660> message<00:13:12.440> on<00:13:12.590> vacation<00:13:13.100> they<00:13:14.030> called 00:13:14.440 --> 00:13:14.450 align:start position:0% first message on vacation they called 00:13:14.450 --> 00:13:17.350 align:start position:0% first message on vacation they called running<00:13:14.779> on<00:13:15.050> going<00:13:15.380> to<00:13:15.589> be<00:13:15.740> shipped<00:13:16.550> in<00:13:16.730> in<00:13:17.029> iOS 00:13:17.350 --> 00:13:17.360 align:start position:0% running on going to be shipped in in iOS 00:13:17.360 --> 00:13:22.600 align:start position:0% running on going to be shipped in in iOS and<00:13:17.810> of<00:13:18.620> course<00:13:18.860> we've<00:13:19.600> done<00:13:20.600> like<00:13:21.200> we've<00:13:21.800> done 00:13:22.600 --> 00:13:22.610 align:start position:0% and of course we've done like we've done 00:13:22.610 --> 00:13:24.280 align:start position:0% and of course we've done like we've done any<00:13:22.790> stability<00:13:23.000> before<00:13:23.630> the<00:13:23.750> spaces<00:13:24.110> across 00:13:24.280 --> 00:13:24.290 align:start position:0% any stability before the spaces across 00:13:24.290 --> 00:13:27.490 align:start position:0% any stability before the spaces across the<00:13:24.470> pond<00:13:24.620> so<00:13:25.550> that<00:13:25.730> is<00:13:26.000> what<00:13:26.779> we've<00:13:26.930> shared<00:13:27.230> so 00:13:27.490 --> 00:13:27.500 align:start position:0% the pond so that is what we've shared so 00:13:27.500 --> 00:13:29.230 align:start position:0% the pond so that is what we've shared so far<00:13:27.529> in<00:13:28.010> the<00:13:28.130> last<00:13:28.250> few<00:13:28.490> months<00:13:28.880> the<00:13:29.029> things 00:13:29.230 --> 00:13:29.240 align:start position:0% far in the last few months the things 00:13:29.240 --> 00:13:31.000 align:start position:0% far in the last few months the things that<00:13:29.389> actually<00:13:29.660> came<00:13:30.050> to<00:13:30.200> mind<00:13:30.410> that<00:13:30.500> been<00:13:30.800> a 00:13:31.000 --> 00:13:31.010 align:start position:0% that actually came to mind that been a 00:13:31.010 --> 00:13:33.360 align:start position:0% that actually came to mind that been a lot<00:13:31.250> more<00:13:31.399> things<00:13:31.699> that<00:13:31.970> come<00:13:32.329> to<00:13:32.480> mind<00:13:32.660> so 00:13:33.360 --> 00:13:33.370 align:start position:0% lot more things that come to mind so 00:13:33.370 --> 00:13:36.250 align:start position:0% lot more things that come to mind so sorry<00:13:34.370> if<00:13:34.490> I<00:13:34.579> didn't<00:13:34.790> mention<00:13:34.880> some<00:13:35.269> that<00:13:35.990> you 00:13:36.250 --> 00:13:36.260 align:start position:0% sorry if I didn't mention some that you 00:13:36.260 --> 00:13:38.650 align:start position:0% sorry if I didn't mention some that you think<00:13:36.500> Iranians<00:13:37.490> and<00:13:37.820> I<00:13:37.970> okay<00:13:38.180> talk<00:13:38.420> about 00:13:38.650 --> 00:13:38.660 align:start position:0% think Iranians and I okay talk about 00:13:38.660 --> 00:13:41.110 align:start position:0% think Iranians and I okay talk about what<00:13:39.139> we<00:13:39.320> were<00:13:39.800> eating<00:13:39.829> on<00:13:40.220> and<00:13:40.430> what's<00:13:40.730> on<00:13:41.029> the 00:13:41.110 --> 00:13:41.120 align:start position:0% what we were eating on and what's on the 00:13:41.120 --> 00:13:42.579 align:start position:0% what we were eating on and what's on the roadmap<00:13:41.329> for<00:13:41.720> the<00:13:41.779> few<00:13:41.990> more<00:13:42.139> for<00:13:42.290> the<00:13:42.380> next 00:13:42.579 --> 00:13:42.589 align:start position:0% roadmap for the few more for the next 00:13:42.589 --> 00:13:45.189 align:start position:0% roadmap for the few more for the next few<00:13:42.709> months<00:13:42.860> so<00:13:43.360> number<00:13:44.360> one<00:13:44.660> I<00:13:44.959> would<00:13:45.110> say 00:13:45.189 --> 00:13:45.199 align:start position:0% few months so number one I would say 00:13:45.199 --> 00:13:47.710 align:start position:0% few months so number one I would say number<00:13:45.500> one<00:13:45.740> priority<00:13:46.310> not<00:13:47.149> just<00:13:47.209> for<00:13:47.570> us<00:13:47.600> but 00:13:47.710 --> 00:13:47.720 align:start position:0% number one priority not just for us but 00:13:47.720 --> 00:13:50.319 align:start position:0% number one priority not just for us but for<00:13:48.199> a<00:13:48.440> lot<00:13:48.800> of<00:13:48.829> projects<00:13:49.370> and<00:13:49.610> a<00:13:49.850> lot<00:13:50.029> of<00:13:50.120> teams 00:13:50.319 --> 00:13:50.329 align:start position:0% for a lot of projects and a lot of teams 00:13:50.329 --> 00:13:52.569 align:start position:0% for a lot of projects and a lot of teams across<00:13:50.570> the<00:13:50.660> board<00:13:51.019> it's<00:13:51.620> testing<00:13:52.220> that<00:13:52.339> scale 00:13:52.569 --> 00:13:52.579 align:start position:0% across the board it's testing that scale 00:13:52.579 --> 00:13:55.600 align:start position:0% across the board it's testing that scale and<00:13:52.820> this<00:13:53.269> is<00:13:53.420> a<00:13:53.560> recurring<00:13:54.560> topic 00:13:55.600 --> 00:13:55.610 align:start position:0% and this is a recurring topic 00:13:55.610 --> 00:13:59.379 align:start position:0% and this is a recurring topic whenever<00:13:56.060> I<00:13:56.120> speak<00:13:56.329> to<00:13:56.480> a<00:13:56.510> team<00:13:57.010> we<00:13:58.389> like 00:13:59.379 --> 00:13:59.389 align:start position:0% whenever I speak to a team we like 00:13:59.389 --> 00:14:00.879 align:start position:0% whenever I speak to a team we like pretty<00:13:59.660> confused<00:14:00.110> that<00:14:00.230> they<00:14:00.350> don't<00:14:00.560> like 00:14:00.879 --> 00:14:00.889 align:start position:0% pretty confused that they don't like 00:14:00.889 --> 00:14:03.069 align:start position:0% pretty confused that they don't like they've<00:14:01.519> always<00:14:01.699> asked<00:14:01.970> about<00:14:02.089> hey<00:14:02.420> I'm<00:14:02.720> kinda 00:14:03.069 --> 00:14:03.079 align:start position:0% they've always asked about hey I'm kinda 00:14:03.079 --> 00:14:04.000 align:start position:0% they've always asked about hey I'm kinda testing<00:14:03.380> might<00:14:03.500> be<00:14:03.620> if<00:14:03.680> that's<00:14:03.829> how<00:14:03.949> you 00:14:04.000 --> 00:14:04.010 align:start position:0% testing might be if that's how you 00:14:04.010 --> 00:14:05.530 align:start position:0% testing might be if that's how you tested<00:14:04.370> maybe<00:14:04.550> to<00:14:04.699> be<00:14:04.820> it's<00:14:04.970> here<00:14:05.180> whether 00:14:05.530 --> 00:14:05.540 align:start position:0% tested maybe to be it's here whether 00:14:05.540 --> 00:14:07.240 align:start position:0% tested maybe to be it's here whether than<00:14:05.750> what<00:14:06.019> other<00:14:06.199> techniques<00:14:06.560> and<00:14:06.800> so<00:14:06.949> on 00:14:07.240 --> 00:14:07.250 align:start position:0% than what other techniques and so on 00:14:07.250 --> 00:14:09.189 align:start position:0% than what other techniques and so on so<00:14:07.579> whatever<00:14:07.730> actually<00:14:08.180> this<00:14:08.720> has<00:14:08.870> become<00:14:09.050> a 00:14:09.189 --> 00:14:09.199 align:start position:0% so whatever actually this has become a 00:14:09.199 --> 00:14:11.199 align:start position:0% so whatever actually this has become a bottleneck<00:14:09.410> for<00:14:09.860> us<00:14:10.010> we<00:14:10.790> want<00:14:11.000> to<00:14:11.060> make<00:14:11.180> sure 00:14:11.199 --> 00:14:11.209 align:start position:0% bottleneck for us we want to make sure 00:14:11.209 --> 00:14:13.360 align:start position:0% bottleneck for us we want to make sure that<00:14:11.600> every<00:14:11.959> single<00:14:12.079> release<00:14:12.529> ability<00:14:13.100> to<00:14:13.220> be 00:14:13.360 --> 00:14:13.370 align:start position:0% that every single release ability to be 00:14:13.370 --> 00:14:16.660 align:start position:0% that every single release ability to be an<00:14:13.579> IB<00:14:13.880> FS<00:14:14.149> and<00:14:14.740> other<00:14:15.740> projects<00:14:16.279> that<00:14:16.339> we<00:14:16.430> put 00:14:16.660 --> 00:14:16.670 align:start position:0% an IB FS and other projects that we put 00:14:16.670 --> 00:14:21.150 align:start position:0% an IB FS and other projects that we put out<00:14:16.820> there<00:14:16.870> is<00:14:17.870> well<00:14:19.209> so<00:14:20.209> that<00:14:20.600> the 00:14:21.150 --> 00:14:21.160 align:start position:0% out there is well so that the 00:14:21.160 --> 00:14:23.560 align:start position:0% out there is well so that the improvements<00:14:22.160> or<00:14:22.399> the<00:14:22.730> deterioration<00:14:23.360> of 00:14:23.560 --> 00:14:23.570 align:start position:0% improvements or the deterioration of 00:14:23.570 --> 00:14:25.810 align:start position:0% improvements or the deterioration of each<00:14:24.079> release<00:14:24.380> and<00:14:24.620> each<00:14:24.740> commit<00:14:25.130> this<00:14:25.490> well 00:14:25.810 --> 00:14:25.820 align:start position:0% each release and each commit this well 00:14:25.820 --> 00:14:28.090 align:start position:0% each release and each commit this well quantified<00:14:26.360> and<00:14:26.510> for<00:14:27.260> that<00:14:27.380> we<00:14:27.680> need<00:14:27.709> a 00:14:28.090 --> 00:14:28.100 align:start position:0% quantified and for that we need a 00:14:28.100 --> 00:14:30.370 align:start position:0% quantified and for that we need a platform<00:14:28.839> which<00:14:29.839> we're<00:14:30.019> calling<00:14:30.260> the 00:14:30.370 --> 00:14:30.380 align:start position:0% platform which we're calling the 00:14:30.380 --> 00:14:33.960 align:start position:0% platform which we're calling the interplanetary<00:14:30.740> test<00:14:31.339> ground<00:14:31.519> to<00:14:32.240> be<00:14:32.870> able<00:14:32.959> to 00:14:33.960 --> 00:14:33.970 align:start position:0% interplanetary test ground to be able to 00:14:33.970 --> 00:14:36.579 align:start position:0% interplanetary test ground to be able to create<00:14:34.970> distributed<00:14:35.839> that<00:14:35.959> record<00:14:36.260> usable 00:14:36.579 --> 00:14:36.589 align:start position:0% create distributed that record usable 00:14:36.589 --> 00:14:40.150 align:start position:0% create distributed that record usable teste<00:14:36.860> that<00:14:36.980> hits<00:14:37.600> magnitudes<00:14:38.600> of<00:14:39.160> 100,000 00:14:40.150 --> 00:14:40.160 align:start position:0% teste that hits magnitudes of 100,000 00:14:40.160 --> 00:14:42.819 align:start position:0% teste that hits magnitudes of 100,000 volts<00:14:40.279> right<00:14:41.060> what<00:14:41.990> simulated<00:14:42.500> network 00:14:42.819 --> 00:14:42.829 align:start position:0% volts right what simulated network 00:14:42.829 --> 00:14:45.970 align:start position:0% volts right what simulated network conditions<00:14:43.269> so<00:14:44.500> this<00:14:45.500> is<00:14:45.620> going<00:14:45.800> to<00:14:45.860> be<00:14:45.920> a 00:14:45.970 --> 00:14:45.980 align:start position:0% conditions so this is going to be a 00:14:45.980 --> 00:14:48.069 align:start position:0% conditions so this is going to be a platform<00:14:46.459> that<00:14:46.640> is<00:14:46.699> currently<00:14:47.360> in 00:14:48.069 --> 00:14:48.079 align:start position:0% platform that is currently in 00:14:48.079 --> 00:14:50.620 align:start position:0% platform that is currently in development<00:14:48.760> we<00:14:49.760> have<00:14:49.790> architected<00:14:50.540> this 00:14:50.620 --> 00:14:50.630 align:start position:0% development we have architected this 00:14:50.630 --> 00:14:54.449 align:start position:0% development we have architected this platform<00:14:50.870> it<00:14:51.740> is<00:14:51.880> racing<00:14:52.880> towards<00:14:53.269> it<00:14:53.420> and 00:14:54.449 --> 00:14:54.459 align:start position:0% platform it is racing towards it and 00:14:54.459 --> 00:14:56.710 align:start position:0% platform it is racing towards it and what<00:14:55.459> we<00:14:55.579> want<00:14:55.760> to<00:14:55.820> make<00:14:55.910> sure<00:14:55.970> it<00:14:56.329> is<00:14:56.510> that 00:14:56.710 --> 00:14:56.720 align:start position:0% what we want to make sure it is that 00:14:56.720 --> 00:14:58.569 align:start position:0% what we want to make sure it is that it's<00:14:56.930> tightly<00:14:57.140> tightly<00:14:57.529> integrated<00:14:58.100> with<00:14:58.250> the 00:14:58.569 --> 00:14:58.579 align:start position:0% it's tightly tightly integrated with the 00:14:58.579 --> 00:15:01.569 align:start position:0% it's tightly tightly integrated with the engineering<00:14:59.000> lifecycle<00:14:59.300> so<00:14:59.870> basically<00:15:00.769> since 00:15:01.569 --> 00:15:01.579 align:start position:0% engineering lifecycle so basically since 00:15:01.579 --> 00:15:03.220 align:start position:0% engineering lifecycle so basically since no<00:15:01.790> use<00:15:02.029> and<00:15:02.269> having<00:15:02.510> a<00:15:02.569> platform<00:15:02.990> where<00:15:03.140> you 00:15:03.220 --> 00:15:03.230 align:start position:0% no use and having a platform where you 00:15:03.230 --> 00:15:05.170 align:start position:0% no use and having a platform where you have<00:15:03.680> to<00:15:03.890> where<00:15:04.399> you<00:15:04.490> have<00:15:04.640> to<00:15:04.790> do<00:15:04.940> things 00:15:05.170 --> 00:15:05.180 align:start position:0% have to where you have to do things 00:15:05.180 --> 00:15:07.300 align:start position:0% have to where you have to do things manually<00:15:05.540> every<00:15:05.870> single<00:15:06.170> time<00:15:06.350> right<00:15:06.620> so<00:15:06.829> we 00:15:07.300 --> 00:15:07.310 align:start position:0% manually every single time right so we 00:15:07.310 --> 00:15:09.730 align:start position:0% manually every single time right so we want<00:15:07.550> for<00:15:07.819> every<00:15:08.089> single<00:15:08.329> commit<00:15:08.630> of<00:15:08.870> living 00:15:09.730 --> 00:15:09.740 align:start position:0% want for every single commit of living 00:15:09.740 --> 00:15:12.519 align:start position:0% want for every single commit of living to<00:15:09.829> be<00:15:09.980> and<00:15:10.250> IVFs<00:15:10.819> to<00:15:11.180> be<00:15:11.690> subjected<00:15:12.350> to<00:15:12.380> a 00:15:12.519 --> 00:15:12.529 align:start position:0% to be and IVFs to be subjected to a 00:15:12.529 --> 00:15:14.559 align:start position:0% to be and IVFs to be subjected to a battery<00:15:12.740> of<00:15:13.069> tests<00:15:13.550> all<00:15:13.910> different<00:15:14.389> parts 00:15:14.559 --> 00:15:14.569 align:start position:0% battery of tests all different parts 00:15:14.569 --> 00:15:16.689 align:start position:0% battery of tests all different parts right<00:15:14.930> so<00:15:15.139> comparative<00:15:15.860> testing<00:15:16.220> how<00:15:16.459> does 00:15:16.689 --> 00:15:16.699 align:start position:0% right so comparative testing how does 00:15:16.699 --> 00:15:20.980 align:start position:0% right so comparative testing how does this<00:15:16.970> really<00:15:17.660> cause<00:15:17.930> us<00:15:18.139> this<00:15:18.410> limit<00:15:19.990> compared 00:15:20.980 --> 00:15:20.990 align:start position:0% this really cause us this limit compared 00:15:20.990 --> 00:15:22.930 align:start position:0% this really cause us this limit compared to<00:15:21.230> a<00:15:21.260> previous<00:15:21.829> commit<00:15:22.130> or<00:15:22.339> to<00:15:22.459> a<00:15:22.490> previous 00:15:22.930 --> 00:15:22.940 align:start position:0% to a previous commit or to a previous 00:15:22.940 --> 00:15:25.960 align:start position:0% to a previous commit or to a previous branch<00:15:23.180> of<00:15:23.449> the<00:15:23.600> hub<00:15:23.899> of<00:15:23.930> this<00:15:24.290> er<00:15:24.970> deteriorate 00:15:25.960 --> 00:15:25.970 align:start position:0% branch of the hub of this er deteriorate 00:15:25.970 --> 00:15:28.509 align:start position:0% branch of the hub of this er deteriorate or<00:15:26.180> improve<00:15:26.690> the<00:15:26.899> status<00:15:27.140> school<00:15:27.500> in<00:15:27.800> terms<00:15:28.279> of 00:15:28.509 --> 00:15:28.519 align:start position:0% or improve the status school in terms of 00:15:28.519 --> 00:15:29.920 align:start position:0% or improve the status school in terms of how<00:15:28.940> my<00:15:29.149> own<00:15:29.360> behaves 00:15:29.920 --> 00:15:29.930 align:start position:0% how my own behaves 00:15:29.930 --> 00:15:31.809 align:start position:0% how my own behaves what<00:15:30.290> about<00:15:30.380> runtime<00:15:30.740> characteristics<00:15:31.610> and 00:15:31.809 --> 00:15:31.819 align:start position:0% what about runtime characteristics and 00:15:31.819 --> 00:15:34.809 align:start position:0% what about runtime characteristics and also<00:15:32.060> in<00:15:32.329> terms<00:15:32.540> of<00:15:32.870> emergence<00:15:33.819> network 00:15:34.809 --> 00:15:34.819 align:start position:0% also in terms of emergence network 00:15:34.819 --> 00:15:37.389 align:start position:0% also in terms of emergence network behavior<00:15:35.329> as<00:15:35.540> a<00:15:35.569> result<00:15:35.810> of<00:15:36.199> deploying<00:15:36.980> that 00:15:37.389 --> 00:15:37.399 align:start position:0% behavior as a result of deploying that 00:15:37.399 --> 00:15:40.470 align:start position:0% behavior as a result of deploying that PR<00:15:37.760> in<00:15:38.060> the<00:15:38.240> net<00:15:38.420> rank<00:15:38.660> of<00:15:38.930> 10<00:15:39.470> al<00:15:39.709> feels 00:15:40.470 --> 00:15:40.480 align:start position:0% PR in the net rank of 10 al feels 00:15:40.480 --> 00:15:42.819 align:start position:0% PR in the net rank of 10 al feels $100,000<00:15:41.480> right<00:15:41.690> we<00:15:42.079> want<00:15:42.260> to<00:15:42.319> be<00:15:42.410> able<00:15:42.500> to<00:15:42.680> do 00:15:42.819 --> 00:15:42.829 align:start position:0% $100,000 right we want to be able to do 00:15:42.829 --> 00:15:44.860 align:start position:0% $100,000 right we want to be able to do things<00:15:43.100> like<00:15:43.329> tails<00:15:44.329> testing 00:15:44.860 --> 00:15:44.870 align:start position:0% things like tails testing 00:15:44.870 --> 00:15:46.720 align:start position:0% things like tails testing interoperability<00:15:45.620> testing<00:15:46.040> so<00:15:46.430> being<00:15:46.640> able 00:15:46.720 --> 00:15:46.730 align:start position:0% interoperability testing so being able 00:15:46.730 --> 00:15:50.290 align:start position:0% interoperability testing so being able to<00:15:46.910> take<00:15:47.600> for<00:15:47.779> example<00:15:47.870> a<00:15:49.300> particular 00:15:50.290 --> 00:15:50.300 align:start position:0% to take for example a particular 00:15:50.300 --> 00:15:53.230 align:start position:0% to take for example a particular proportion<00:15:51.260> of<00:15:51.680> nodes<00:15:51.980> and<00:15:52.279> running<00:15:52.760> IP 00:15:53.230 --> 00:15:53.240 align:start position:0% proportion of nodes and running IP 00:15:53.240 --> 00:15:55.179 align:start position:0% proportion of nodes and running IP offense<00:15:53.689> whether<00:15:53.930> it<00:15:54.050> be<00:15:54.140> to<00:15:54.290> be<00:15:54.470> version 00:15:55.179 --> 00:15:55.189 align:start position:0% offense whether it be to be version 00:15:55.189 --> 00:15:57.280 align:start position:0% offense whether it be to be version whatever<00:15:55.550> 30<00:15:56.329> percent<00:15:56.779> that<00:15:56.930> I'm<00:15:57.050> running 00:15:57.280 --> 00:15:57.290 align:start position:0% whatever 30 percent that I'm running 00:15:57.290 --> 00:15:58.929 align:start position:0% whatever 30 percent that I'm running this<00:15:57.439> version<00:15:57.680> 20<00:15:58.189> percent<00:15:58.459> that<00:15:58.579> are<00:15:58.640> running 00:15:58.929 --> 00:15:58.939 align:start position:0% this version 20 percent that are running 00:15:58.939 --> 00:16:00.340 align:start position:0% this version 20 percent that are running this<00:15:59.060> version<00:15:59.540> and<00:15:59.720> 10<00:15:59.870> percent<00:15:59.990> that<00:16:00.230> are 00:16:00.340 --> 00:16:00.350 align:start position:0% this version and 10 percent that are 00:16:00.350 --> 00:16:03.309 align:start position:0% this version and 10 percent that are running<00:16:00.649> another<00:16:01.310> version<00:16:01.550> and<00:16:02.319> understand 00:16:03.309 --> 00:16:03.319 align:start position:0% running another version and understand 00:16:03.319 --> 00:16:05.439 align:start position:0% running another version and understand how<00:16:03.649> that<00:16:03.920> combination<00:16:04.250> actually<00:16:05.000> plays<00:16:05.240> out 00:16:05.439 --> 00:16:05.449 align:start position:0% how that combination actually plays out 00:16:05.449 --> 00:16:08.050 align:start position:0% how that combination actually plays out in<00:16:05.750> terms<00:16:05.779> of<00:16:06.250> the<00:16:07.250> in<00:16:07.339> terms<00:16:07.370> of<00:16:07.670> performance 00:16:08.050 --> 00:16:08.060 align:start position:0% in terms of the in terms of performance 00:16:08.060 --> 00:16:10.929 align:start position:0% in terms of the in terms of performance this<00:16:08.269> is<00:16:08.329> what<00:16:09.279> what<00:16:10.279> the<00:16:10.370> architecture<00:16:10.760> is 00:16:10.929 --> 00:16:10.939 align:start position:0% this is what what the architecture is 00:16:10.939 --> 00:16:13.329 align:start position:0% this is what what the architecture is looking<00:16:11.240> like<00:16:11.420> if<00:16:12.140> you<00:16:12.290> want<00:16:12.470> to<00:16:12.589> follow<00:16:13.100> this 00:16:13.329 --> 00:16:13.339 align:start position:0% looking like if you want to follow this 00:16:13.339 --> 00:16:14.710 align:start position:0% looking like if you want to follow this effort<00:16:13.699> if<00:16:13.939> you<00:16:14.029> want<00:16:14.209> to<00:16:14.300> track<00:16:14.510> what<00:16:14.689> we 00:16:14.710 --> 00:16:14.720 align:start position:0% effort if you want to track what we 00:16:14.720 --> 00:16:16.569 align:start position:0% effort if you want to track what we doing<00:16:15.079> make<00:16:15.709> sure<00:16:15.740> that<00:16:16.069> you<00:16:16.189> watch<00:16:16.399> this 00:16:16.569 --> 00:16:16.579 align:start position:0% doing make sure that you watch this 00:16:16.579 --> 00:16:19.150 align:start position:0% doing make sure that you watch this right<00:16:16.790> I<00:16:17.029> be<00:16:17.269> FSS<00:16:17.720> farms<00:16:18.019> it<00:16:18.410> is<00:16:18.529> right<00:16:18.709> now<00:16:18.860> me 00:16:19.150 --> 00:16:19.160 align:start position:0% right I be FSS farms it is right now me 00:16:19.160 --> 00:16:19.830 align:start position:0% right I be FSS farms it is right now me of<00:16:19.490> the 00:16:19.830 --> 00:16:19.840 align:start position:0% of the 00:16:19.840 --> 00:16:21.300 align:start position:0% of the it<00:16:20.020> has<00:16:20.170> spread<00:16:20.440> that<00:16:20.620> it's<00:16:20.890> probably<00:16:21.070> going 00:16:21.300 --> 00:16:21.310 align:start position:0% it has spread that it's probably going 00:16:21.310 --> 00:16:23.700 align:start position:0% it has spread that it's probably going to<00:16:21.370> be<00:16:21.490> moved<00:16:22.180> to<00:16:22.390> the<00:16:22.870> nippy<00:16:23.140> to<00:16:23.260> be<00:16:23.380> umbrella 00:16:23.700 --> 00:16:23.710 align:start position:0% to be moved to the nippy to be umbrella 00:16:23.710 --> 00:16:26.280 align:start position:0% to be moved to the nippy to be umbrella at<00:16:23.920> one<00:16:24.160> point<00:16:24.340> because<00:16:24.550> it's<00:16:24.850> a<00:16:25.480> bit<00:16:25.660> it's<00:16:25.960> way 00:16:26.280 --> 00:16:26.290 align:start position:0% at one point because it's a bit it's way 00:16:26.290 --> 00:16:28.950 align:start position:0% at one point because it's a bit it's way lowering<00:16:26.680> the<00:16:26.800> stack<00:16:27.010> when<00:16:27.190> IVFs<00:16:27.670> or<00:16:27.970> even<00:16:28.900> a 00:16:28.950 --> 00:16:28.960 align:start position:0% lowering the stack when IVFs or even a 00:16:28.960 --> 00:16:31.830 align:start position:0% lowering the stack when IVFs or even a separate<00:16:29.260> top<00:16:29.470> level<00:16:29.740> project<00:16:30.660> another<00:16:31.660> thing 00:16:31.830 --> 00:16:31.840 align:start position:0% separate top level project another thing 00:16:31.840 --> 00:16:34.110 align:start position:0% separate top level project another thing that<00:16:31.960> I'm<00:16:32.050> super<00:16:32.470> excited<00:16:32.560> about<00:16:33.120> working 00:16:34.110 --> 00:16:34.120 align:start position:0% that I'm super excited about working 00:16:34.120 --> 00:16:38.370 align:start position:0% that I'm super excited about working actively<00:16:34.540> on<00:16:34.720> is<00:16:35.290> instrumentation<00:16:36.070> so<00:16:36.850> a<00:16:37.390> lot 00:16:38.370 --> 00:16:38.380 align:start position:0% actively on is instrumentation so a lot 00:16:38.380 --> 00:16:39.870 align:start position:0% actively on is instrumentation so a lot of<00:16:38.500> teams<00:16:38.770> of<00:16:38.980> hostas<00:16:39.400> for<00:16:39.670> meThe 00:16:39.870 --> 00:16:39.880 align:start position:0% of teams of hostas for meThe 00:16:39.880 --> 00:16:41.550 align:start position:0% of teams of hostas for meThe observability<00:16:40.690> and<00:16:40.839> essentially<00:16:41.380> the 00:16:41.550 --> 00:16:41.560 align:start position:0% observability and essentially the 00:16:41.560 --> 00:16:43.470 align:start position:0% observability and essentially the capabilities<00:16:42.250> of<00:16:42.279> X<00:16:42.520> rating<00:16:42.850> to<00:16:42.970> one<00:16:43.270> the 00:16:43.470 --> 00:16:43.480 align:start position:0% capabilities of X rating to one the 00:16:43.480 --> 00:16:46.050 align:start position:0% capabilities of X rating to one the living<00:16:43.990> to<00:16:44.080> be<00:16:44.200> sad<00:16:44.500> this<00:16:44.980> precisely<00:16:45.430> doing<00:16:45.910> in 00:16:46.050 --> 00:16:46.060 align:start position:0% living to be sad this precisely doing in 00:16:46.060 --> 00:16:49.620 align:start position:0% living to be sad this precisely doing in the<00:16:46.120> phenotypes<00:16:46.660> so<00:16:47.380> we<00:16:47.500> currently<00:16:48.270> run<00:16:49.270> work 00:16:49.620 --> 00:16:49.630 align:start position:0% the phenotypes so we currently run work 00:16:49.630 --> 00:16:52.820 align:start position:0% the phenotypes so we currently run work by<00:16:50.140> taking<00:16:50.350> a<00:16:50.620> data<00:16:50.890> first<00:16:51.220> approach<00:16:51.700> right<00:16:52.330> so 00:16:52.820 --> 00:16:52.830 align:start position:0% by taking a data first approach right so 00:16:52.830 --> 00:16:55.500 align:start position:0% by taking a data first approach right so yeah<00:16:53.830> it<00:16:53.980> would<00:16:54.070> be<00:16:54.220> awesome<00:16:54.250> to<00:16:54.790> create<00:16:55.180> ad 00:16:55.500 --> 00:16:55.510 align:start position:0% yeah it would be awesome to create ad 00:16:55.510 --> 00:16:57.150 align:start position:0% yeah it would be awesome to create ad hoc<00:16:55.779> realizations<00:16:56.560> about<00:16:56.620> things<00:16:56.950> that<00:16:57.010> I 00:16:57.150 --> 00:16:57.160 align:start position:0% hoc realizations about things that I 00:16:57.160 --> 00:16:59.490 align:start position:0% hoc realizations about things that I have<00:16:57.279> a<00:16:57.310> let<00:16:57.700> me<00:16:57.790> to<00:16:57.910> be<00:16:58.029> really<00:16:58.900> the<00:16:59.020> scalable 00:16:59.490 --> 00:16:59.500 align:start position:0% have a let me to be really the scalable 00:16:59.500 --> 00:17:02.970 align:start position:0% have a let me to be really the scalable way<00:16:59.680> to<00:17:00.160> build<00:17:00.430> this<00:17:00.550> is<00:17:00.850> to<00:17:01.260> tap<00:17:02.260> into<00:17:02.800> the 00:17:02.970 --> 00:17:02.980 align:start position:0% way to build this is to tap into the 00:17:02.980 --> 00:17:05.490 align:start position:0% way to build this is to tap into the inner<00:17:03.190> guts<00:17:03.550> of<00:17:03.850> the<00:17:03.970> b2b<00:17:04.360> and<00:17:04.540> expose<00:17:05.170> a 00:17:05.490 --> 00:17:05.500 align:start position:0% inner guts of the b2b and expose a 00:17:05.500 --> 00:17:08.340 align:start position:0% inner guts of the b2b and expose a firehose<00:17:06.010> of<00:17:06.250> instrumentation<00:17:07.240> data<00:17:07.600> by<00:17:08.319> a 00:17:08.340 --> 00:17:08.350 align:start position:0% firehose of instrumentation data by a 00:17:08.350 --> 00:17:10.230 align:start position:0% firehose of instrumentation data by a standard<00:17:09.069> protocol<00:17:09.520> such<00:17:09.790> that<00:17:10.000> any 00:17:10.230 --> 00:17:10.240 align:start position:0% standard protocol such that any 00:17:10.240 --> 00:17:12.750 align:start position:0% standard protocol such that any implementation<00:17:10.510> of<00:17:11.020> the<00:17:11.170> b2b<00:17:11.439> by<00:17:12.130> adopting<00:17:12.490> a 00:17:12.750 --> 00:17:12.760 align:start position:0% implementation of the b2b by adopting a 00:17:12.760 --> 00:17:15.090 align:start position:0% implementation of the b2b by adopting a standard<00:17:13.120> protocol<00:17:13.510> will<00:17:13.959> render<00:17:14.380> itself<00:17:14.740> to 00:17:15.090 --> 00:17:15.100 align:start position:0% standard protocol will render itself to 00:17:15.100 --> 00:17:19.040 align:start position:0% standard protocol will render itself to be<00:17:15.730> visualized<00:17:16.600> and<00:17:16.930> being<00:17:17.230> inspected<00:17:17.589> by<00:17:18.220> a 00:17:19.040 --> 00:17:19.050 align:start position:0% be visualized and being inspected by a 00:17:19.050 --> 00:17:21.990 align:start position:0% be visualized and being inspected by a Holland<00:17:20.050> report<00:17:20.380> right<00:17:20.860> so<00:17:21.250> the<00:17:21.339> next<00:17:21.550> set<00:17:21.790> so 00:17:21.990 --> 00:17:22.000 align:start position:0% Holland report right so the next set so 00:17:22.000 --> 00:17:23.670 align:start position:0% Holland report right so the next set so we're<00:17:22.240> focusing<00:17:22.569> on<00:17:22.720> building<00:17:22.900> a<00:17:23.140> fire<00:17:23.380> hose 00:17:23.670 --> 00:17:23.680 align:start position:0% we're focusing on building a fire hose 00:17:23.680 --> 00:17:25.199 align:start position:0% we're focusing on building a fire hose of<00:17:24.010> introspection<00:17:24.310> protocol<00:17:24.970> that<00:17:25.089> we 00:17:25.199 --> 00:17:25.209 align:start position:0% of introspection protocol that we 00:17:25.209 --> 00:17:27.480 align:start position:0% of introspection protocol that we drafting<00:17:25.689> and<00:17:26.530> the<00:17:26.679> next<00:17:26.920> time<00:17:27.010> is<00:17:27.160> to<00:17:27.280> create 00:17:27.480 --> 00:17:27.490 align:start position:0% drafting and the next time is to create 00:17:27.490 --> 00:17:29.070 align:start position:0% drafting and the next time is to create a<00:17:27.520> binding<00:17:27.910> framework<00:17:28.300> that<00:17:28.480> consumes<00:17:28.870> that 00:17:29.070 --> 00:17:29.080 align:start position:0% a binding framework that consumes that 00:17:29.080 --> 00:17:32.340 align:start position:0% a binding framework that consumes that data<00:17:29.290> in<00:17:29.980> a<00:17:30.040> browser<00:17:30.400> creates<00:17:31.240> us<00:17:31.480> essentially 00:17:32.340 --> 00:17:32.350 align:start position:0% data in a browser creates us essentially 00:17:32.350 --> 00:17:34.260 align:start position:0% data in a browser creates us essentially a<00:17:32.500> reactive<00:17:33.010> State<00:17:33.250> repository<00:17:33.490> on<00:17:34.120> the 00:17:34.260 --> 00:17:34.270 align:start position:0% a reactive State repository on the 00:17:34.270 --> 00:17:38.850 align:start position:0% a reactive State repository on the browser<00:17:34.800> that<00:17:36.240> react<00:17:37.240> T<00:17:38.110> three<00:17:38.350> different 00:17:38.850 --> 00:17:38.860 align:start position:0% browser that react T three different 00:17:38.860 --> 00:17:40.680 align:start position:0% browser that react T three different driven<00:17:39.220> visualizations<00:17:39.700> can<00:17:40.150> subscribe<00:17:40.660> to 00:17:40.680 --> 00:17:40.690 align:start position:0% driven visualizations can subscribe to 00:17:40.690 --> 00:17:43.980 align:start position:0% driven visualizations can subscribe to and<00:17:41.520> visualize<00:17:42.520> data<00:17:42.880> whether<00:17:43.630> it's<00:17:43.870> a 00:17:43.980 --> 00:17:43.990 align:start position:0% and visualize data whether it's a 00:17:43.990 --> 00:17:49.260 align:start position:0% and visualize data whether it's a recording<00:17:44.530> of<00:17:44.650> a<00:17:44.770> slice<00:17:45.040> of<00:17:45.070> time<00:17:45.460> and<00:17:47.429> we<00:17:48.429> want 00:17:49.260 --> 00:17:49.270 align:start position:0% recording of a slice of time and we want 00:17:49.270 --> 00:17:50.970 align:start position:0% recording of a slice of time and we want to<00:17:49.450> get<00:17:49.870> people<00:17:49.990> the<00:17:50.290> ability<00:17:50.380> to<00:17:50.740> move 00:17:50.970 --> 00:17:50.980 align:start position:0% to get people the ability to move 00:17:50.980 --> 00:17:53.400 align:start position:0% to get people the ability to move backwards<00:17:51.730> towards<00:17:52.330> in<00:17:52.810> time<00:17:52.990> so<00:17:53.140> that<00:17:53.170> you 00:17:53.400 --> 00:17:53.410 align:start position:0% backwards towards in time so that you 00:17:53.410 --> 00:17:55.020 align:start position:0% backwards towards in time so that you can<00:17:53.440> if<00:17:53.950> you<00:17:54.070> want<00:17:54.190> to<00:17:54.310> do<00:17:54.460> that<00:17:54.670> particular 00:17:55.020 --> 00:17:55.030 align:start position:0% can if you want to do that particular 00:17:55.030 --> 00:17:56.669 align:start position:0% can if you want to do that particular situation<00:17:55.210> you<00:17:55.690> can<00:17:55.840> start<00:17:56.080> up<00:17:56.200> a<00:17:56.260> recording 00:17:56.669 --> 00:17:56.679 align:start position:0% situation you can start up a recording 00:17:56.679 --> 00:17:58.830 align:start position:0% situation you can start up a recording take<00:17:57.280> the<00:17:57.400> dough<00:17:57.610> and<00:17:57.820> then<00:17:58.090> go<00:17:58.270> at<00:17:58.390> it<00:17:58.510> into 00:17:58.830 --> 00:17:58.840 align:start position:0% take the dough and then go at it into 00:17:58.840 --> 00:18:00.750 align:start position:0% take the dough and then go at it into the<00:17:58.960> browser<00:17:59.170> and<00:17:59.500> visualize<00:17:59.980> and<00:18:00.550> move 00:18:00.750 --> 00:18:00.760 align:start position:0% the browser and visualize and move 00:18:00.760 --> 00:18:03.450 align:start position:0% the browser and visualize and move through<00:18:01.270> time<00:18:01.540> as<00:18:01.840> well<00:18:02.470> as<00:18:02.679> watching<00:18:03.280> the 00:18:03.450 --> 00:18:03.460 align:start position:0% through time as well as watching the 00:18:03.460 --> 00:18:05.210 align:start position:0% through time as well as watching the activity<00:18:03.970> open 00:18:05.210 --> 00:18:05.220 align:start position:0% activity open 00:18:05.220 --> 00:18:08.280 align:start position:0% activity open so<00:18:06.220> see<00:18:06.790> how<00:18:06.880> my<00:18:07.000> panties<00:18:07.570> a<00:18:07.600> browser<00:18:07.900> library 00:18:08.280 --> 00:18:08.290 align:start position:0% so see how my panties a browser library 00:18:08.290 --> 00:18:10.520 align:start position:0% so see how my panties a browser library for<00:18:08.440> developers<00:18:08.890> to<00:18:08.920> to<00:18:09.460> enclose<00:18:09.730> reusable 00:18:10.520 --> 00:18:10.530 align:start position:0% for developers to to enclose reusable 00:18:10.530 --> 00:18:13.470 align:start position:0% for developers to to enclose reusable visualization<00:18:11.530> sent<00:18:11.890> reads<00:18:12.760> any<00:18:13.000> hope<00:18:13.240> that 00:18:13.470 --> 00:18:13.480 align:start position:0% visualization sent reads any hope that 00:18:13.480 --> 00:18:15.960 align:start position:0% visualization sent reads any hope that this<00:18:14.200> will<00:18:14.350> kick-start<00:18:14.650> a<00:18:15.190> counselor<00:18:15.730> of 00:18:15.960 --> 00:18:15.970 align:start position:0% this will kick-start a counselor of 00:18:15.970 --> 00:18:18.330 align:start position:0% this will kick-start a counselor of reusable<00:18:16.510> visualizations<00:18:17.470> of<00:18:17.740> concentrate 00:18:18.330 --> 00:18:18.340 align:start position:0% reusable visualizations of concentrate 00:18:18.340 --> 00:18:20.750 align:start position:0% reusable visualizations of concentrate that<00:18:18.460> are<00:18:18.610> compatible<00:18:18.820> with<00:18:19.150> all<00:18:19.450> negative<00:18:19.929> B 00:18:20.750 --> 00:18:20.760 align:start position:0% that are compatible with all negative B 00:18:20.760 --> 00:18:22.830 align:start position:0% that are compatible with all negative B implementations<00:18:21.760> and<00:18:21.970> by<00:18:22.450> the<00:18:22.510> way<00:18:22.660> this 00:18:22.830 --> 00:18:22.840 align:start position:0% implementations and by the way this 00:18:22.840 --> 00:18:24.750 align:start position:0% implementations and by the way this project<00:18:23.020> is<00:18:23.350> codenamed<00:18:23.590> phantom<00:18:24.309> dreads 00:18:24.750 --> 00:18:24.760 align:start position:0% project is codenamed phantom dreads 00:18:24.760 --> 00:18:27.630 align:start position:0% project is codenamed phantom dreads so<00:18:24.940> if<00:18:25.540> you<00:18:25.720> see<00:18:25.990> if<00:18:26.380> you<00:18:26.530> see<00:18:26.710> those<00:18:26.950> terms<00:18:27.220> now 00:18:27.630 --> 00:18:27.640 align:start position:0% so if you see if you see those terms now 00:18:27.640 --> 00:18:29.490 align:start position:0% so if you see if you see those terms now you<00:18:27.700> know<00:18:27.940> what<00:18:28.360> what<00:18:28.929> it's<00:18:29.050> about 00:18:29.490 --> 00:18:29.500 align:start position:0% you know what what it's about 00:18:29.500 --> 00:18:31.770 align:start position:0% you know what what it's about okay<00:18:30.370> so<00:18:30.429> a<00:18:30.610> few<00:18:31.059> other<00:18:31.240> things<00:18:31.270> that<00:18:31.450> we<00:18:31.660> do 00:18:31.770 --> 00:18:31.780 align:start position:0% okay so a few other things that we do 00:18:31.780 --> 00:18:33.299 align:start position:0% okay so a few other things that we do that<00:18:32.200> we're<00:18:32.559> going<00:18:32.650> to<00:18:32.710> be<00:18:32.800> working<00:18:32.950> on<00:18:33.280> that 00:18:33.299 --> 00:18:33.309 align:start position:0% that we're going to be working on that 00:18:33.309 --> 00:18:34.950 align:start position:0% that we're going to be working on that we're<00:18:33.550> actually<00:18:33.700> working<00:18:34.030> on<00:18:34.330> our<00:18:34.630> message 00:18:34.950 --> 00:18:34.960 align:start position:0% we're actually working on our message 00:18:34.960 --> 00:18:38.510 align:start position:0% we're actually working on our message orientation<00:18:35.590> so<00:18:36.179> this<00:18:37.179> is<00:18:37.330> saying<00:18:37.510> a 00:18:38.510 --> 00:18:38.520 align:start position:0% orientation so this is saying a 00:18:38.520 --> 00:18:40.710 align:start position:0% orientation so this is saying a long-standing<00:18:39.520> missing<00:18:40.179> future<00:18:40.450> and<00:18:40.570> maybe 00:18:40.710 --> 00:18:40.720 align:start position:0% long-standing missing future and maybe 00:18:40.720 --> 00:18:45.030 align:start position:0% long-standing missing future and maybe to<00:18:40.900> be<00:18:42.570> so<00:18:43.570> this<00:18:43.900> so<00:18:44.290> where<00:18:44.650> it's<00:18:44.770> haven't 00:18:45.030 --> 00:18:45.040 align:start position:0% to be so this so where it's haven't 00:18:45.040 --> 00:18:47.240 align:start position:0% to be so this so where it's haven't written<00:18:45.190> to<00:18:45.460> be<00:18:45.580> to<00:18:45.700> become<00:18:45.850> an<00:18:46.090> entry<00:18:46.330> point 00:18:47.240 --> 00:18:47.250 align:start position:0% written to be to become an entry point 00:18:47.250 --> 00:18:49.830 align:start position:0% written to be to become an entry point so<00:18:48.250> for<00:18:48.550> the<00:18:48.670> newbies<00:18:49.030> and<00:18:49.420> if<00:18:49.540> you're<00:18:49.660> going 00:18:49.830 --> 00:18:49.840 align:start position:0% so for the newbies and if you're going 00:18:49.840 --> 00:18:51.240 align:start position:0% so for the newbies and if you're going to<00:18:49.929> become<00:18:50.110> a<00:18:50.170> factory<00:18:50.530> of<00:18:50.650> stats<00:18:50.860> from<00:18:51.040> which 00:18:51.240 --> 00:18:51.250 align:start position:0% to become a factory of stats from which 00:18:51.250 --> 00:18:52.470 align:start position:0% to become a factory of stats from which you'll<00:18:51.400> be<00:18:51.429> able<00:18:51.610> to<00:18:51.880> create<00:18:52.090> different<00:18:52.210> kinds 00:18:52.470 --> 00:18:52.480 align:start position:0% you'll be able to create different kinds 00:18:52.480 --> 00:18:54.660 align:start position:0% you'll be able to create different kinds of<00:18:52.630> hosts<00:18:53.050> we're<00:18:53.590> working<00:18:53.920> on<00:18:54.070> not<00:18:54.429> a<00:18:54.460> whole 00:18:54.660 --> 00:18:54.670 align:start position:0% of hosts we're working on not a whole 00:18:54.670 --> 00:18:56.700 align:start position:0% of hosts we're working on not a whole bunch<00:18:54.910> in<00:18:55.030> indirect<00:18:55.480> connection<00:18:55.840> upgrade<00:18:56.200> so 00:18:56.700 --> 00:18:56.710 align:start position:0% bunch in indirect connection upgrade so 00:18:56.710 --> 00:18:59.190 align:start position:0% bunch in indirect connection upgrade so we<00:18:56.890> already<00:18:57.130> have<00:18:57.340> you<00:18:57.520> VIP<00:18:57.880> and<00:18:58.330> not<00:18:58.510> PMP<00:18:58.900> port 00:18:59.190 --> 00:18:59.200 align:start position:0% we already have you VIP and not PMP port 00:18:59.200 --> 00:19:03.060 align:start position:0% we already have you VIP and not PMP port support<00:18:59.530> or<00:19:00.280> its<00:19:00.429> opening<00:19:00.880> support<00:19:01.210> but<00:19:02.070> and 00:19:03.060 --> 00:19:03.070 align:start position:0% support or its opening support but and 00:19:03.070 --> 00:19:04.350 align:start position:0% support or its opening support but and we<00:19:03.190> have<00:19:03.340> people<00:19:03.580> to<00:19:03.700> read<00:19:03.880> a<00:19:04.000> note<00:19:04.210> about 00:19:04.350 --> 00:19:04.360 align:start position:0% we have people to read a note about 00:19:04.360 --> 00:19:06.180 align:start position:0% we have people to read a note about subsistence<00:19:05.020> that<00:19:05.170> I<00:19:05.200> capable<00:19:05.679> of<00:19:05.770> sensing<00:19:05.980> if 00:19:06.180 --> 00:19:06.190 align:start position:0% subsistence that I capable of sensing if 00:19:06.190 --> 00:19:07.520 align:start position:0% subsistence that I capable of sensing if you're<00:19:06.309> running<00:19:06.580> behind<00:19:06.670> it<00:19:07.030> now 00:19:07.520 --> 00:19:07.530 align:start position:0% you're running behind it now 00:19:07.530 --> 00:19:09.410 align:start position:0% you're running behind it now that's<00:19:07.800> the<00:19:08.040> starting<00:19:08.730> of<00:19:08.850> a<00:19:08.940> connection<00:19:09.300> with 00:19:09.410 --> 00:19:09.420 align:start position:0% that's the starting of a connection with 00:19:09.420 --> 00:19:11.990 align:start position:0% that's the starting of a connection with everyday<00:19:09.690> advertising<00:19:10.530> those<00:19:10.980> addresses<00:19:11.520> so 00:19:11.990 --> 00:19:12.000 align:start position:0% everyday advertising those addresses so 00:19:12.000 --> 00:19:13.250 align:start position:0% everyday advertising those addresses so the<00:19:12.090> rest<00:19:12.240> of<00:19:12.390> the<00:19:12.510> world<00:19:12.690> so<00:19:12.900> that<00:19:12.930> you<00:19:13.140> can 00:19:13.250 --> 00:19:13.260 align:start position:0% the rest of the world so that you can 00:19:13.260 --> 00:19:14.690 align:start position:0% the rest of the world so that you can receive<00:19:13.500> inbound<00:19:13.890> connections<00:19:14.040> for<00:19:14.460> that<00:19:14.580> is 00:19:14.690 --> 00:19:14.700 align:start position:0% receive inbound connections for that is 00:19:14.700 --> 00:19:16.940 align:start position:0% receive inbound connections for that is super<00:19:15.030> inefficient<00:19:15.270> and<00:19:15.810> what<00:19:16.470> we<00:19:16.560> need<00:19:16.680> to<00:19:16.830> do 00:19:16.940 --> 00:19:16.950 align:start position:0% super inefficient and what we need to do 00:19:16.950 --> 00:19:19.430 align:start position:0% super inefficient and what we need to do is<00:19:17.220> move<00:19:17.730> to<00:19:18.000> a<00:19:18.210> place<00:19:18.390> where<00:19:18.720> we<00:19:18.810> use<00:19:18.960> that 00:19:19.430 --> 00:19:19.440 align:start position:0% is move to a place where we use that 00:19:19.440 --> 00:19:20.930 align:start position:0% is move to a place where we use that Renate<00:19:19.920> connection<00:19:20.310> as<00:19:20.430> an<00:19:20.550> embryonic 00:19:20.930 --> 00:19:20.940 align:start position:0% Renate connection as an embryonic 00:19:20.940 --> 00:19:23.510 align:start position:0% Renate connection as an embryonic connection<00:19:21.480> to<00:19:21.660> do<00:19:21.810> signaling<00:19:22.680> between<00:19:23.340> the 00:19:23.510 --> 00:19:23.520 align:start position:0% connection to do signaling between the 00:19:23.520 --> 00:19:26.540 align:start position:0% connection to do signaling between the between<00:19:24.000> the<00:19:24.210> two<00:19:24.390> between<00:19:24.750> various<00:19:25.680> peers<00:19:25.950> to 00:19:26.540 --> 00:19:26.550 align:start position:0% between the two between various peers to 00:19:26.550 --> 00:19:28.400 align:start position:0% between the two between various peers to start<00:19:27.090> to<00:19:27.450> initiate<00:19:27.630> a<00:19:27.900> whole<00:19:28.140> punching 00:19:28.400 --> 00:19:28.410 align:start position:0% start to initiate a whole punching 00:19:28.410 --> 00:19:30.200 align:start position:0% start to initiate a whole punching procedure<00:19:28.770> and<00:19:29.130> hopefully<00:19:29.580> be<00:19:29.700> able<00:19:29.820> to<00:19:29.970> hold 00:19:30.200 --> 00:19:30.210 align:start position:0% procedure and hopefully be able to hold 00:19:30.210 --> 00:19:33.590 align:start position:0% procedure and hopefully be able to hold much<00:19:30.390> right<00:19:31.850> we're<00:19:32.850> gonna<00:19:32.940> be<00:19:33.120> working<00:19:33.450> on 00:19:33.590 --> 00:19:33.600 align:start position:0% much right we're gonna be working on 00:19:33.600 --> 00:19:35.660 align:start position:0% much right we're gonna be working on robust<00:19:34.020> pervasive<00:19:34.590> in<00:19:35.100> some<00:19:35.250> points<00:19:35.460> as<00:19:35.520> well 00:19:35.660 --> 00:19:35.670 align:start position:0% robust pervasive in some points as well 00:19:35.670 --> 00:19:37.010 align:start position:0% robust pervasive in some points as well but<00:19:35.910> t<00:19:36.060> I<00:19:36.090> don't<00:19:36.300> want<00:19:36.510> waiting<00:19:36.690> to<00:19:36.780> me<00:19:36.870> and 00:19:37.010 --> 00:19:37.020 align:start position:0% but t I don't want waiting to me and 00:19:37.020 --> 00:19:38.480 align:start position:0% but t I don't want waiting to me and this<00:19:37.140> is<00:19:37.260> important<00:19:37.710> because<00:19:37.890> this 00:19:38.480 --> 00:19:38.490 align:start position:0% this is important because this 00:19:38.490 --> 00:19:40.220 align:start position:0% this is important because this combination<00:19:39.090> of<00:19:39.210> protocols<00:19:39.660> is<00:19:39.780> what's<00:19:39.990> used 00:19:40.220 --> 00:19:40.230 align:start position:0% combination of protocols is what's used 00:19:40.230 --> 00:19:44.120 align:start position:0% combination of protocols is what's used in<00:19:40.350> HTTP<00:19:40.890> 3<00:19:41.790> as<00:19:41.910> well<00:19:42.150> and<00:19:42.990> if<00:19:43.170> we<00:19:43.350> made<00:19:43.800> Libby 00:19:44.120 --> 00:19:44.130 align:start position:0% in HTTP 3 as well and if we made Libby 00:19:44.130 --> 00:19:45.980 align:start position:0% in HTTP 3 as well and if we made Libby to<00:19:44.190> be<00:19:44.310> run<00:19:44.550> on<00:19:44.730> port<00:19:44.910> for<00:19:45.150> free<00:19:45.480> this<00:19:45.750> means 00:19:45.980 --> 00:19:45.990 align:start position:0% to be run on port for free this means 00:19:45.990 --> 00:19:49.100 align:start position:0% to be run on port for free this means that<00:19:46.340> we<00:19:47.340> basically<00:19:47.550> have<00:19:48.120> a<00:19:48.420> high<00:19:48.690> chance<00:19:48.930> of 00:19:49.100 --> 00:19:49.110 align:start position:0% that we basically have a high chance of 00:19:49.110 --> 00:19:50.720 align:start position:0% that we basically have a high chance of being<00:19:49.260> a<00:19:49.410> lot<00:19:49.560> more<00:19:49.590> sensitive<00:19:50.070> persistence 00:19:50.720 --> 00:19:50.730 align:start position:0% being a lot more sensitive persistence 00:19:50.730 --> 00:19:54.260 align:start position:0% being a lot more sensitive persistence the<00:19:51.630> other<00:19:51.780> system<00:19:52.140> that<00:19:52.170> we<00:19:52.440> are<00:19:52.670> pleased<00:19:53.670> of 00:19:54.260 --> 00:19:54.270 align:start position:0% the other system that we are pleased of 00:19:54.270 --> 00:19:55.460 align:start position:0% the other system that we are pleased of people<00:19:54.540> the<00:19:54.600> things<00:19:54.810> that<00:19:54.930> we're<00:19:55.050> working<00:19:55.350> on 00:19:55.460 --> 00:19:55.470 align:start position:0% people the things that we're working on 00:19:55.470 --> 00:19:57.350 align:start position:0% people the things that we're working on negotiation<00:19:56.250> principled<00:19:56.610> negotiation<00:19:56.640> one 00:19:57.350 --> 00:19:57.360 align:start position:0% negotiation principled negotiation one 00:19:57.360 --> 00:19:58.790 align:start position:0% negotiation principled negotiation one go<00:19:57.510> too<00:19:57.660> deep<00:19:57.810> into<00:19:57.990> this<00:19:58.140> a<00:19:58.290> very<00:19:58.590> similar 00:19:58.790 --> 00:19:58.800 align:start position:0% go too deep into this a very similar 00:19:58.800 --> 00:20:01.160 align:start position:0% go too deep into this a very similar type<00:19:59.060> so<00:20:00.060> once<00:20:00.270> it's<00:20:00.420> like<00:20:00.510> to<00:20:00.690> point<00:20:00.810> out<00:20:00.990> if 00:20:01.160 --> 00:20:01.170 align:start position:0% type so once it's like to point out if 00:20:01.170 --> 00:20:04.090 align:start position:0% type so once it's like to point out if you<00:20:01.260> hear<00:20:01.440> this<00:20:01.730> this<00:20:02.730> a<00:20:03.060> bunch<00:20:03.330> of<00:20:03.450> features 00:20:04.090 --> 00:20:04.100 align:start position:0% you hear this this a bunch of features 00:20:04.100 --> 00:20:07.550 align:start position:0% you hear this this a bunch of features that<00:20:05.510> necessary<00:20:06.510> for<00:20:06.750> you<00:20:06.870> to<00:20:06.960> point<00:20:07.350> O<00:20:07.410> as 00:20:07.550 --> 00:20:07.560 align:start position:0% that necessary for you to point O as 00:20:07.560 --> 00:20:09.320 align:start position:0% that necessary for you to point O as well<00:20:07.770> so<00:20:08.010> they're<00:20:08.280> super<00:20:08.640> high<00:20:08.850> priority<00:20:09.300> for 00:20:09.320 --> 00:20:09.330 align:start position:0% well so they're super high priority for 00:20:09.330 --> 00:20:11.840 align:start position:0% well so they're super high priority for us<00:20:09.540> we<00:20:10.260> are<00:20:10.380> creating<00:20:10.740> music<00:20:10.890> uhm<00:20:11.490> let's<00:20:11.700> do 00:20:11.840 --> 00:20:11.850 align:start position:0% us we are creating music uhm let's do 00:20:11.850 --> 00:20:13.850 align:start position:0% us we are creating music uhm let's do that's<00:20:12.030> 1.3<00:20:12.420> and<00:20:12.660> noise<00:20:12.840> tension<00:20:13.350> suicide 00:20:13.850 --> 00:20:13.860 align:start position:0% that's 1.3 and noise tension suicide 00:20:13.860 --> 00:20:15.110 align:start position:0% that's 1.3 and noise tension suicide shakes<00:20:14.070> is<00:20:14.190> going<00:20:14.370> to<00:20:14.430> be<00:20:14.490> using<00:20:14.670> my<00:20:14.940> spy 00:20:15.110 --> 00:20:15.120 align:start position:0% shakes is going to be using my spy 00:20:15.120 --> 00:20:18.230 align:start position:0% shakes is going to be using my spy planes<00:20:15.890> which<00:20:16.890> uses<00:20:17.400> a<00:20:17.610> combination<00:20:17.880> of 00:20:18.230 --> 00:20:18.240 align:start position:0% planes which uses a combination of 00:20:18.240 --> 00:20:20.000 align:start position:0% planes which uses a combination of optimistic<00:20:18.780> scenarios<00:20:19.380> with<00:20:19.560> a<00:20:19.800> graceful 00:20:20.000 --> 00:20:20.010 align:start position:0% optimistic scenarios with a graceful 00:20:20.010 --> 00:20:20.860 align:start position:0% optimistic scenarios with a graceful fallbacks 00:20:20.860 --> 00:20:20.870 align:start position:0% fallbacks 00:20:20.870 --> 00:20:24.020 align:start position:0% fallbacks when<00:20:21.870> the<00:20:22.170> keys<00:20:22.320> not<00:20:22.640> one<00:20:23.640> that<00:20:23.730> you<00:20:23.850> have<00:20:24.000> to 00:20:24.020 --> 00:20:24.030 align:start position:0% when the keys not one that you have to 00:20:24.030 --> 00:20:26.240 align:start position:0% when the keys not one that you have to rotate<00:20:24.180> it<00:20:24.420> on<00:20:24.540> the<00:20:24.690> other<00:20:24.870> end<00:20:25.130> we're<00:20:26.130> going 00:20:26.240 --> 00:20:26.250 align:start position:0% rotate it on the other end we're going 00:20:26.250 --> 00:20:29.270 align:start position:0% rotate it on the other end we're going to<00:20:26.310> be<00:20:26.370> working<00:20:27.330> on<00:20:27.600> TLS<00:20:27.990> one<00:20:28.710> way<00:20:28.860> we<00:20:29.040> own 00:20:29.270 --> 00:20:29.280 align:start position:0% to be working on TLS one way we own 00:20:29.280 --> 00:20:31.010 align:start position:0% to be working on TLS one way we own languages<00:20:29.760> we<00:20:30.030> currently<00:20:30.270> have<00:20:30.570> support<00:20:30.900> for 00:20:31.010 --> 00:20:31.020 align:start position:0% languages we currently have support for 00:20:31.020 --> 00:20:33.290 align:start position:0% languages we currently have support for go<00:20:31.200> away<00:20:31.500> there<00:20:31.710> are<00:20:31.800> some<00:20:31.980> roadblocks<00:20:32.160> in<00:20:32.760> JSF 00:20:33.290 --> 00:20:33.300 align:start position:0% go away there are some roadblocks in JSF 00:20:33.300 --> 00:20:35.240 align:start position:0% go away there are some roadblocks in JSF rust<00:20:33.540> so<00:20:33.870> we're<00:20:34.080> going<00:20:34.170> to<00:20:34.230> be<00:20:34.380> searching 00:20:35.240 --> 00:20:35.250 align:start position:0% rust so we're going to be searching 00:20:35.250 --> 00:20:37.640 align:start position:0% rust so we're going to be searching through<00:20:35.550> those<00:20:35.790> and<00:20:36.060> more<00:20:36.930> and<00:20:37.500> basically 00:20:37.640 --> 00:20:37.650 align:start position:0% through those and more and basically 00:20:37.650 --> 00:20:40.220 align:start position:0% through those and more and basically yeah<00:20:38.640> so<00:20:38.970> a<00:20:39.000> few<00:20:39.360> more<00:20:39.480> things<00:20:39.690> here<00:20:39.870> to 00:20:40.220 --> 00:20:40.230 align:start position:0% yeah so a few more things here to 00:20:40.230 --> 00:20:41.810 align:start position:0% yeah so a few more things here to mention<00:20:40.590> like<00:20:40.770> with<00:20:40.920> specific<00:20:41.310> improvements 00:20:41.810 --> 00:20:41.820 align:start position:0% mention like with specific improvements 00:20:41.820 --> 00:20:44.120 align:start position:0% mention like with specific improvements a<00:20:41.850> majority<00:20:42.390> pops<00:20:42.780> up<00:20:42.960> ecolution<00:20:43.050> so<00:20:43.860> make 00:20:44.120 --> 00:20:44.130 align:start position:0% a majority pops up ecolution so make 00:20:44.130 --> 00:20:45.380 align:start position:0% a majority pops up ecolution so make sure<00:20:44.160> that<00:20:44.460> you<00:20:44.550> come<00:20:44.790> to<00:20:44.970> the<00:20:45.060> concepts 00:20:45.380 --> 00:20:45.390 align:start position:0% sure that you come to the concepts 00:20:45.390 --> 00:20:48.720 align:start position:0% sure that you come to the concepts obsession<00:20:45.960> on<00:20:46.140> 1c<00:20:47.030> which<00:20:48.030> is<00:20:48.180> a 00:20:48.720 --> 00:20:48.730 align:start position:0% obsession on 1c which is a 00:20:48.730 --> 00:20:53.790 align:start position:0% obsession on 1c which is a to<00:20:49.050> 255<00:20:50.050> room<00:20:50.470> being<00:20:50.800> beaten<00:20:52.560> because<00:20:53.560> we're 00:20:53.790 --> 00:20:53.800 align:start position:0% to 255 room being beaten because we're 00:20:53.800 --> 00:20:55.230 align:start position:0% to 255 room being beaten because we're going<00:20:53.950> to<00:20:54.040> be<00:20:54.130> we're<00:20:54.760> going<00:20:54.790> to<00:20:54.940> be<00:20:55.000> talking 00:20:55.230 --> 00:20:55.240 align:start position:0% going to be we're going to be talking 00:20:55.240 --> 00:20:56.730 align:start position:0% going to be we're going to be talking about<00:20:55.420> some<00:20:55.720> of<00:20:55.840> the<00:20:55.930> things<00:20:56.080> that<00:20:56.200> are<00:20:56.410> coming 00:20:56.730 --> 00:20:56.740 align:start position:0% about some of the things that are coming 00:20:56.740 --> 00:21:00.120 align:start position:0% about some of the things that are coming down<00:20:57.550> the<00:20:57.670> pike<00:20:57.850> in<00:20:58.450> terms<00:20:58.720> of<00:20:58.930> where<00:20:59.680> this<00:20:59.950> is 00:21:00.120 --> 00:21:00.130 align:start position:0% down the pike in terms of where this is 00:21:00.130 --> 00:21:01.370 align:start position:0% down the pike in terms of where this is heading 00:21:01.370 --> 00:21:01.380 align:start position:0% heading 00:21:01.380 --> 00:21:02.940 align:start position:0% heading we're<00:21:02.380> going<00:21:02.530> to<00:21:02.590> be<00:21:02.650> talking<00:21:02.830> about 00:21:02.940 --> 00:21:02.950 align:start position:0% we're going to be talking about 00:21:02.950 --> 00:21:04.770 align:start position:0% we're going to be talking about something<00:21:03.310> like<00:21:03.430> this<00:21:03.820> up<00:21:04.030> which<00:21:04.540> is<00:21:04.660> the 00:21:04.770 --> 00:21:04.780 align:start position:0% something like this up which is the 00:21:04.780 --> 00:21:07.260 align:start position:0% something like this up which is the future<00:21:05.140> generation<00:21:05.830> of<00:21:05.890> us<00:21:06.070> it's<00:21:06.250> time<00:21:06.370> for 00:21:07.260 --> 00:21:07.270 align:start position:0% future generation of us it's time for 00:21:07.270 --> 00:21:09.870 align:start position:0% future generation of us it's time for evolution<00:21:07.930> so<00:21:08.200> hardening<00:21:08.680> the<00:21:08.830> DHD<00:21:09.130> which<00:21:09.730> is 00:21:09.870 --> 00:21:09.880 align:start position:0% evolution so hardening the DHD which is 00:21:09.880 --> 00:21:13.140 align:start position:0% evolution so hardening the DHD which is principal<00:21:10.810> thing<00:21:11.260> right<00:21:11.440> now<00:21:11.620> for<00:21:11.830> us<00:21:12.150> and 00:21:13.140 --> 00:21:13.150 align:start position:0% principal thing right now for us and 00:21:13.150 --> 00:21:16.260 align:start position:0% principal thing right now for us and this<00:21:13.630> is<00:21:13.840> dependent<00:21:14.290> on<00:21:14.320> the<00:21:14.470> test<00:21:14.740> round<00:21:15.270> we 00:21:16.260 --> 00:21:16.270 align:start position:0% this is dependent on the test round we 00:21:16.270 --> 00:21:19.770 align:start position:0% this is dependent on the test round we are<00:21:16.480> aiming<00:21:16.720> to<00:21:17.670> to<00:21:18.670> get<00:21:19.060> even<00:21:19.330> better<00:21:19.480> specs 00:21:19.770 --> 00:21:19.780 align:start position:0% are aiming to to get even better specs 00:21:19.780 --> 00:21:22.080 align:start position:0% are aiming to to get even better specs so<00:21:20.050> we're<00:21:20.260> aiming<00:21:20.350> for<00:21:20.560> 100<00:21:21.220> percent<00:21:21.520> accurate 00:21:22.080 --> 00:21:22.090 align:start position:0% so we're aiming for 100 percent accurate 00:21:22.090 --> 00:21:25.470 align:start position:0% so we're aiming for 100 percent accurate respect<00:21:22.540> and<00:21:22.870> as<00:21:23.440> a<00:21:23.880> contributor<00:21:24.880> and<00:21:25.240> this 00:21:25.470 --> 00:21:25.480 align:start position:0% respect and as a contributor and this 00:21:25.480 --> 00:21:27.870 align:start position:0% respect and as a contributor and this this<00:21:26.380> disappear<00:21:27.160> that's<00:21:27.280> working<00:21:27.610> actively 00:21:27.870 --> 00:21:27.880 align:start position:0% this disappear that's working actively 00:21:27.880 --> 00:21:31.140 align:start position:0% this disappear that's working actively on<00:21:28.030> this<00:21:28.330> other<00:21:29.320> topics<00:21:29.800> CTA<00:21:30.130> CTA<00:21:30.460> on<00:21:31.000> your 00:21:31.140 --> 00:21:31.150 align:start position:0% on this other topics CTA CTA on your 00:21:31.150 --> 00:21:32.730 align:start position:0% on this other topics CTA CTA on your broadening<00:21:31.570> reputation<00:21:32.140> on<00:21:32.290> different<00:21:32.590> these 00:21:32.730 --> 00:21:32.740 align:start position:0% broadening reputation on different these 00:21:32.740 --> 00:21:34.800 align:start position:0% broadening reputation on different these updates<00:21:33.100> that<00:21:33.400> are<00:21:33.430> ideas<00:21:34.360> that<00:21:34.570> we're 00:21:34.800 --> 00:21:34.810 align:start position:0% updates that are ideas that we're 00:21:34.810 --> 00:21:38.010 align:start position:0% updates that are ideas that we're developing<00:21:35.710> had<00:21:36.310> said<00:21:36.670> when<00:21:37.120> we<00:21:37.330> hope<00:21:37.540> to<00:21:37.720> not 00:21:38.010 --> 00:21:38.020 align:start position:0% developing had said when we hope to not 00:21:38.020 --> 00:21:40.320 align:start position:0% developing had said when we hope to not shot<00:21:38.200> over<00:21:38.440> the<00:21:38.530> next<00:21:38.710> few<00:21:38.860> months<00:21:39.330> also 00:21:40.320 --> 00:21:40.330 align:start position:0% shot over the next few months also 00:21:40.330 --> 00:21:42.210 align:start position:0% shot over the next few months also wanted<00:21:40.540> to<00:21:40.600> do<00:21:40.690> a<00:21:40.720> showcase<00:21:41.200> West<00:21:41.830> what<00:21:42.190> I 00:21:42.210 --> 00:21:42.220 align:start position:0% wanted to do a showcase West what I 00:21:42.220 --> 00:21:44.130 align:start position:0% wanted to do a showcase West what I talked<00:21:42.490> about<00:21:42.700> that<00:21:42.820> year<00:21:43.120> the<00:21:43.750> groups<00:21:44.020> of 00:21:44.130 --> 00:21:44.140 align:start position:0% talked about that year the groups of 00:21:44.140 --> 00:21:46.110 align:start position:0% talked about that year the groups of transport<00:21:44.740> and<00:21:45.010> go<00:21:45.220> to<00:21:45.280> a<00:21:45.370> p2p<00:21:45.610> which<00:21:45.910> was 00:21:46.110 --> 00:21:46.120 align:start position:0% transport and go to a p2p which was 00:21:46.120 --> 00:21:49.790 align:start position:0% transport and go to a p2p which was developed<00:21:46.990> by<00:21:47.200> /<00:21:47.830> Franklin<00:21:48.100> /<00:21:48.310> FG<00:21:48.520> burnsy 00:21:49.790 --> 00:21:49.800 align:start position:0% developed by / Franklin / FG burnsy 00:21:49.800 --> 00:21:51.900 align:start position:0% developed by / Franklin / FG burnsy unfortunately<00:21:50.800> it<00:21:51.130> is<00:21:51.340> still<00:21:51.640> the<00:21:51.790> most 00:21:51.900 --> 00:21:51.910 align:start position:0% unfortunately it is still the most 00:21:51.910 --> 00:21:56.040 align:start position:0% unfortunately it is still the most racially<00:21:52.480> content<00:21:52.900> boy<00:21:53.020> week<00:21:53.440> on<00:21:54.330> you<00:21:55.360> this 00:21:56.040 --> 00:21:56.050 align:start position:0% racially content boy week on you this 00:21:56.050 --> 00:21:57.780 align:start position:0% racially content boy week on you this relaxes<00:21:56.320> public<00:21:56.890> access<00:21:57.160> to<00:21:57.310> the<00:21:57.400> code<00:21:57.550> but 00:21:57.780 --> 00:21:57.790 align:start position:0% relaxes public access to the code but 00:21:57.790 --> 00:22:00.290 align:start position:0% relaxes public access to the code but that<00:21:58.360> will<00:21:58.540> change<00:21:58.570> hopefully<00:21:59.440> shortly<00:21:59.740> and 00:22:00.290 --> 00:22:00.300 align:start position:0% that will change hopefully shortly and 00:22:00.300 --> 00:22:02.600 align:start position:0% that will change hopefully shortly and that's<00:22:01.300> pretty<00:22:01.420> much<00:22:01.540> all<00:22:01.960> I<00:22:02.140> have<00:22:02.320> for<00:22:02.440> today 00:22:02.600 --> 00:22:02.610 align:start position:0% that's pretty much all I have for today 00:22:02.610 --> 00:22:06.060 align:start position:0% that's pretty much all I have for today so<00:22:03.610> that<00:22:04.270> was<00:22:04.360> super<00:22:04.600> rushed<00:22:05.020> a<00:22:05.650> lot<00:22:05.950> of 00:22:06.060 --> 00:22:06.070 align:start position:0% so that was super rushed a lot of 00:22:06.070 --> 00:22:09.360 align:start position:0% so that was super rushed a lot of content<00:22:06.430> to<00:22:06.550> share<00:22:07.080> and<00:22:08.080> if<00:22:08.860> you<00:22:09.010> have<00:22:09.160> any 00:22:09.360 --> 00:22:09.370 align:start position:0% content to share and if you have any 00:22:09.370 --> 00:22:12.810 align:start position:0% content to share and if you have any questions<00:22:09.760> make<00:22:10.090> sure<00:22:10.150> to<00:22:10.410> to<00:22:11.410> hit<00:22:11.650> me<00:22:11.860> - 00:22:12.810 --> 00:22:12.820 align:start position:0% questions make sure to to hit me - 00:22:12.820 --> 00:22:15.390 align:start position:0% questions make sure to to hit me - Tiffany<00:22:13.330> I'm<00:22:13.660> gonna<00:22:13.840> be<00:22:13.990> rolling<00:22:14.380> around<00:22:14.500> make 00:22:15.390 --> 00:22:15.400 align:start position:0% Tiffany I'm gonna be rolling around make 00:22:15.400 --> 00:22:18.060 align:start position:0% Tiffany I'm gonna be rolling around make sure<00:22:15.550> we<00:22:15.820> come<00:22:16.000> to<00:22:16.120> the<00:22:16.210> next<00:22:16.480> session<00:22:16.660> that<00:22:17.560> we 00:22:18.060 --> 00:22:18.070 align:start position:0% sure we come to the next session that we 00:22:18.070 --> 00:22:20.720 align:start position:0% sure we come to the next session that we have<00:22:18.310> got<00:22:18.940> go<00:22:19.210> stem<00:22:19.390> cell<00:22:19.600> which<00:22:19.810> is<00:22:19.960> tomorrow 00:22:20.720 --> 00:22:20.730 align:start position:0% have got go stem cell which is tomorrow 00:22:20.730 --> 00:22:25.200 align:start position:0% have got go stem cell which is tomorrow at<00:22:21.730> 2:55<00:22:22.660> and<00:22:22.690> room<00:22:23.170> b10<00:22:23.800> and<00:22:24.100> make<00:22:24.340> sure<00:22:24.550> if 00:22:25.200 --> 00:22:25.210 align:start position:0% at 2:55 and room b10 and make sure if 00:22:25.210 --> 00:22:26.130 align:start position:0% at 2:55 and room b10 and make sure if you<00:22:25.300> are<00:22:25.330> excited<00:22:25.690> about 00:22:26.130 --> 00:22:26.140 align:start position:0% you are excited about 00:22:26.140 --> 00:22:28.680 align:start position:0% you are excited about like<00:22:26.920> we<00:22:27.100> are<00:22:27.340> and<00:22:27.820> a<00:22:28.030> lot<00:22:28.150> of<00:22:28.179> people<00:22:28.510> in<00:22:28.570> this 00:22:28.680 --> 00:22:28.690 align:start position:0% like we are and a lot of people in this 00:22:28.690 --> 00:22:31.799 align:start position:0% like we are and a lot of people in this room<00:22:28.870> are<00:22:29.110> make<00:22:29.710> sure<00:22:29.830> to<00:22:30.010> get<00:22:30.130> involved<00:22:30.640> -<00:22:30.910> the 00:22:31.799 --> 00:22:31.809 align:start position:0% room are make sure to get involved - the 00:22:31.809 --> 00:22:34.289 align:start position:0% room are make sure to get involved - the future<00:22:32.140> integrates<00:22:32.740> into<00:22:32.860> the<00:22:33.040> specs<00:22:33.309> by 00:22:34.289 --> 00:22:34.299 align:start position:0% future integrates into the specs by 00:22:34.299 --> 00:22:36.380 align:start position:0% future integrates into the specs by having<00:22:34.660> a<00:22:34.750> meeting<00:22:34.990> or<00:22:35.530> meeting<00:22:35.980> things 00:22:36.380 --> 00:22:36.390 align:start position:0% having a meeting or meeting things 00:22:36.390 --> 00:22:40.110 align:start position:0% having a meeting or meeting things looking<00:22:37.390> at<00:22:37.480> the<00:22:37.570> Deaf<00:22:37.750> Branson<00:22:38.230> and<00:22:38.670> and<00:22:39.670> a 00:22:40.110 --> 00:22:40.120 align:start position:0% looking at the Deaf Branson and and a 00:22:40.120 --> 00:22:43.740 align:start position:0% looking at the Deaf Branson and and a taking<00:22:41.110> on<00:22:41.260> some<00:22:41.410> of<00:22:41.500> that<00:22:41.650> work<00:22:41.890> and<00:22:42.510> if<00:22:43.510> you 00:22:43.740 --> 00:22:43.750 align:start position:0% taking on some of that work and if you 00:22:43.750 --> 00:22:46.110 align:start position:0% taking on some of that work and if you just<00:22:44.020> want<00:22:44.200> to<00:22:44.230> contribute<00:22:44.500> it<00:22:44.799> you<00:22:45.130> know<00:22:45.250> on 00:22:46.110 --> 00:22:46.120 align:start position:0% just want to contribute it you know on 00:22:46.120 --> 00:22:47.520 align:start position:0% just want to contribute it you know on particular<00:22:46.570> things<00:22:46.600> then<00:22:47.110> make<00:22:47.410> sure<00:22:47.440> to 00:22:47.520 --> 00:22:47.530 align:start position:0% particular things then make sure to 00:22:47.530 --> 00:22:49.890 align:start position:0% particular things then make sure to watch<00:22:47.830> the<00:22:47.980> project<00:22:48.340> records<00:22:48.690> those<00:22:49.690> have<00:22:49.840> a 00:22:49.890 --> 00:22:49.900 align:start position:0% watch the project records those have a 00:22:49.900 --> 00:22:51.510 align:start position:0% watch the project records those have a contact<00:22:50.230> details<00:22:50.559> if<00:22:50.770> you're<00:22:50.890> going<00:22:51.040> to<00:22:51.309> find 00:22:51.510 --> 00:22:51.520 align:start position:0% contact details if you're going to find 00:22:51.520 --> 00:22:53.280 align:start position:0% contact details if you're going to find you<00:22:51.670> around<00:22:51.760> and<00:22:52.179> you<00:22:52.510> want<00:22:52.600> to<00:22:52.750> fund<00:22:52.929> a<00:22:53.020> b2b 00:22:53.280 --> 00:22:53.290 align:start position:0% you around and you want to fund a b2b 00:22:53.290 --> 00:22:58.630 align:start position:0% you around and you want to fund a b2b make<00:22:53.799> sure<00:22:53.920> to<00:22:54.070> pick<00:22:54.190> me<00:22:54.340> on<00:22:54.460> those<00:22:54.549> networks 00:22:58.630 --> 00:22:58.640 align:start position:0% 00:22:58.640 --> 00:23:05.050 align:start position:0% [Applause]