WEBVTT Kind: captions Language: en 00:00:01.070 --> 00:00:20.920 align:start position:0% [Applause] 00:00:20.920 --> 00:00:20.930 align:start position:0% 00:00:20.930 --> 00:00:24.830 align:start position:0% that's<00:00:22.760> okay<00:00:23.760> so<00:00:23.820> we<00:00:24.119> know<00:00:24.300> that<00:00:24.330> dear 00:00:24.830 --> 00:00:24.840 align:start position:0% that's okay so we know that dear 00:00:24.840 --> 00:00:28.130 align:start position:0% that's okay so we know that dear listener<00:00:25.290> terms<00:00:25.700> it's<00:00:26.700> a<00:00:26.910> stream<00:00:27.570> of 00:00:28.130 --> 00:00:28.140 align:start position:0% listener terms it's a stream of 00:00:28.140 --> 00:00:32.300 align:start position:0% listener terms it's a stream of privileged<00:00:29.689> senior<00:00:30.689> German<00:00:30.900> ignition<00:00:31.470> and 00:00:32.300 --> 00:00:32.310 align:start position:0% privileged senior German ignition and 00:00:32.310 --> 00:00:35.270 align:start position:0% privileged senior German ignition and something<00:00:32.910> that<00:00:33.600> is<00:00:33.780> quite<00:00:33.960> choose<00:00:34.280> to 00:00:35.270 --> 00:00:35.280 align:start position:0% something that is quite choose to 00:00:35.280 --> 00:00:38.210 align:start position:0% something that is quite choose to because<00:00:36.270> of<00:00:36.570> specific<00:00:37.079> formatting<00:00:37.680> which<00:00:38.010> is 00:00:38.210 --> 00:00:38.220 align:start position:0% because of specific formatting which is 00:00:38.220 --> 00:00:41.990 align:start position:0% because of specific formatting which is can<00:00:38.910> be<00:00:38.940> aggregated<00:00:40.130> means<00:00:41.130> that<00:00:41.340> pushing 00:00:41.990 --> 00:00:42.000 align:start position:0% can be aggregated means that pushing 00:00:42.000 --> 00:00:51.050 align:start position:0% can be aggregated means that pushing your<00:00:42.120> Charles<00:00:44.960> 1000<00:00:45.960> signatures<00:00:50.060> initial 00:00:51.050 --> 00:00:51.060 align:start position:0% your Charles 1000 signatures initial 00:00:51.060 --> 00:00:53.300 align:start position:0% your Charles 1000 signatures initial cousin<00:00:51.840> all<00:00:51.990> back<00:00:52.170> the<00:00:52.590> vilification<00:00:53.220> this 00:00:53.300 --> 00:00:53.310 align:start position:0% cousin all back the vilification this 00:00:53.310 --> 00:00:55.660 align:start position:0% cousin all back the vilification this party<00:00:53.670> this<00:00:54.090> refugees<00:00:54.690> that<00:00:54.810> comes<00:00:55.020> towards 00:00:55.660 --> 00:00:55.670 align:start position:0% party this refugees that comes towards 00:00:55.670 --> 00:01:01.670 align:start position:0% party this refugees that comes towards sometimes<00:00:58.160> issues<00:00:59.390> so<00:01:00.410> Commission<00:01:01.410> is<00:01:01.530> home 00:01:01.670 --> 00:01:01.680 align:start position:0% sometimes issues so Commission is home 00:01:01.680 --> 00:01:04.189 align:start position:0% sometimes issues so Commission is home to<00:01:01.920> and<00:01:02.250> I<00:01:02.630> simplified<00:01:03.630> a<00:01:03.660> little<00:01:03.780> the<00:01:04.080> way 00:01:04.189 --> 00:01:04.199 align:start position:0% to and I simplified a little the way 00:01:04.199 --> 00:01:06.469 align:start position:0% to and I simplified a little the way truth<00:01:04.470> in<00:01:04.619> the<00:01:04.710> term<00:01:04.860> to<00:01:05.159> the<00:01:05.640> vandegraaff<00:01:06.060> say 00:01:06.469 --> 00:01:06.479 align:start position:0% truth in the term to the vandegraaff say 00:01:06.479 --> 00:01:08.840 align:start position:0% truth in the term to the vandegraaff say sorry<00:01:06.750> other<00:01:07.350> stations<00:01:07.829> but<00:01:08.490> thousand 00:01:08.840 --> 00:01:08.850 align:start position:0% sorry other stations but thousand 00:01:08.850 --> 00:01:10.789 align:start position:0% sorry other stations but thousand already<00:01:09.000> the<00:01:09.299> dolls<00:01:09.509> beside<00:01:10.290> thousand<00:01:10.710> of 00:01:10.789 --> 00:01:10.799 align:start position:0% already the dolls beside thousand of 00:01:10.799 --> 00:01:14.540 align:start position:0% already the dolls beside thousand of other<00:01:10.950> stations<00:01:11.400> but<00:01:12.500> when<00:01:13.500> you<00:01:13.800> intersect<00:01:14.370> us 00:01:14.540 --> 00:01:14.550 align:start position:0% other stations but when you intersect us 00:01:14.550 --> 00:01:15.980 align:start position:0% other stations but when you intersect us at<00:01:14.760> the<00:01:14.850> stations<00:01:15.360> when<00:01:15.510> you<00:01:15.600> receive<00:01:15.870> in<00:01:15.960> your 00:01:15.980 --> 00:01:15.990 align:start position:0% at the stations when you receive in your 00:01:15.990 --> 00:01:18.890 align:start position:0% at the stations when you receive in your garage<00:01:16.170> you<00:01:16.560> won't<00:01:16.890> have<00:01:17.130> each<00:01:17.580> side<00:01:17.900> always 00:01:18.890 --> 00:01:18.900 align:start position:0% garage you won't have each side always 00:01:18.900 --> 00:01:21.290 align:start position:0% garage you won't have each side always in<00:01:19.200> each<00:01:19.290> other<00:01:19.500> properly<00:01:20.370> you<00:01:20.880> would<00:01:20.970> get 00:01:21.290 --> 00:01:21.300 align:start position:0% in each other properly you would get 00:01:21.300 --> 00:01:26.600 align:start position:0% in each other properly you would get reverse<00:01:22.080> initiatives<00:01:22.530> because<00:01:24.920> someone<00:01:25.920> with 00:01:26.600 --> 00:01:26.610 align:start position:0% reverse initiatives because someone with 00:01:26.610 --> 00:01:28.969 align:start position:0% reverse initiatives because someone with I<00:01:26.790> met<00:01:26.970> them<00:01:27.300> how<00:01:27.900> much<00:01:28.229> will<00:01:28.440> happen<00:01:28.620> the 00:01:28.969 --> 00:01:28.979 align:start position:0% I met them how much will happen the 00:01:28.979 --> 00:01:32.930 align:start position:0% I met them how much will happen the blood<00:01:29.250> is<00:01:29.610> an<00:01:30.170> analytic<00:01:31.170> signature<00:01:31.680> and<00:01:31.950> so<00:01:32.850> it 00:01:32.930 --> 00:01:32.940 align:start position:0% blood is an analytic signature and so it 00:01:32.940 --> 00:01:37.730 align:start position:0% blood is an analytic signature and so it means<00:01:33.150> that<00:01:33.650> much<00:01:34.650> smaller<00:01:35.630> even<00:01:36.630> wonder<00:01:37.350> is<00:01:37.620> a 00:01:37.730 --> 00:01:37.740 align:start position:0% means that much smaller even wonder is a 00:01:37.740 --> 00:01:40.210 align:start position:0% means that much smaller even wonder is a nice<00:01:37.890> low<00:01:38.150> setting 00:01:40.210 --> 00:01:40.220 align:start position:0% nice low setting 00:01:40.220 --> 00:01:47.860 align:start position:0% nice low setting so<00:01:40.430> if<00:01:40.670> I<00:01:40.850> can<00:01:44.620> multitask<00:01:45.620> on<00:01:46.420> what<00:01:47.420> it<00:01:47.570> means 00:01:47.860 --> 00:01:47.870 align:start position:0% so if I can multitask on what it means 00:01:47.870 --> 00:01:52.480 align:start position:0% so if I can multitask on what it means forget<00:01:49.750> an<00:01:50.750> ignition<00:01:51.080> is<00:01:51.440> most<00:01:51.620> primitive<00:01:51.800> and 00:01:52.480 --> 00:01:52.490 align:start position:0% forget an ignition is most primitive and 00:01:52.490 --> 00:01:54.070 align:start position:0% forget an ignition is most primitive and the<00:01:52.640> specific<00:01:53.090> which<00:01:53.240> means<00:01:53.570> that<00:01:53.780> returned 00:01:54.070 --> 00:01:54.080 align:start position:0% the specific which means that returned 00:01:54.080 --> 00:01:56.680 align:start position:0% the specific which means that returned owner<00:01:54.260> to<00:01:54.410> train<00:01:54.620> the<00:01:54.740> order<00:01:54.980> okay<00:01:55.690> that's 00:01:56.680 --> 00:01:56.690 align:start position:0% owner to train the order okay that's 00:01:56.690 --> 00:01:58.870 align:start position:0% owner to train the order okay that's kinda<00:01:57.170> for<00:01:57.350> modernization<00:01:57.740> we<00:01:58.160> can<00:01:58.370> have<00:01:58.550> one 00:01:58.870 --> 00:01:58.880 align:start position:0% kinda for modernization we can have one 00:01:58.880 --> 00:02:01.090 align:start position:0% kinda for modernization we can have one set<00:01:59.090> of<00:01:59.240> signature<00:01:59.690> argued<00:02:00.290> by<00:02:00.590> someone 00:02:01.090 --> 00:02:01.100 align:start position:0% set of signature argued by someone 00:02:01.100 --> 00:02:03.190 align:start position:0% set of signature argued by someone another<00:02:01.490> set<00:02:01.730> I<00:02:02.030> will<00:02:02.480> get<00:02:02.750> it<00:02:02.870> by<00:02:02.960> someone 00:02:03.190 --> 00:02:03.200 align:start position:0% another set I will get it by someone 00:02:03.200 --> 00:02:06.840 align:start position:0% another set I will get it by someone else<00:02:03.470> a<00:02:03.740> very<00:02:04.160> vintage<00:02:04.570> this<00:02:05.570> going<00:02:06.170> I<00:02:06.290> get 00:02:06.840 --> 00:02:06.850 align:start position:0% else a very vintage this going I get 00:02:06.850 --> 00:02:10.210 align:start position:0% else a very vintage this going I get producer<00:02:07.850> and<00:02:08.479> your<00:02:08.720> mother<00:02:09.259> you're<00:02:10.009> done 00:02:10.210 --> 00:02:10.220 align:start position:0% producer and your mother you're done 00:02:10.220 --> 00:02:12.699 align:start position:0% producer and your mother you're done except<00:02:10.729> that<00:02:10.850> we<00:02:11.180> small<00:02:11.480> parts<00:02:11.840> which<00:02:11.990> means 00:02:12.699 --> 00:02:12.709 align:start position:0% except that we small parts which means 00:02:12.709 --> 00:02:15.850 align:start position:0% except that we small parts which means we've<00:02:13.459> actually<00:02:13.760> to<00:02:14.180> set<00:02:14.420> the<00:02:15.320> same<00:02:15.530> signature 00:02:15.850 --> 00:02:15.860 align:start position:0% we've actually to set the same signature 00:02:15.860 --> 00:02:18.790 align:start position:0% we've actually to set the same signature when<00:02:16.430> you<00:02:16.520> aggregate<00:02:16.900> we<00:02:17.900> will<00:02:18.020> add<00:02:18.140> something 00:02:18.790 --> 00:02:18.800 align:start position:0% when you aggregate we will add something 00:02:18.800 --> 00:02:20.680 align:start position:0% when you aggregate we will add something back<00:02:19.070> which<00:02:19.340> is<00:02:19.459> basically<00:02:19.790> Pleistocene<00:02:20.600> your 00:02:20.680 --> 00:02:20.690 align:start position:0% back which is basically Pleistocene your 00:02:20.690 --> 00:02:23.620 align:start position:0% back which is basically Pleistocene your job<00:02:20.930> which<00:02:21.500> is<00:02:21.680> it<00:02:22.490> isn't<00:02:22.640> really<00:02:23.000> right<00:02:23.180> so<00:02:23.420> if 00:02:23.620 --> 00:02:23.630 align:start position:0% job which is it isn't really right so if 00:02:23.630 --> 00:02:26.050 align:start position:0% job which is it isn't really right so if we<00:02:23.750> simplify<00:02:24.080> when<00:02:24.890> you<00:02:25.040> ever<00:02:25.280> get<00:02:25.550> in<00:02:25.850> the 00:02:26.050 --> 00:02:26.060 align:start position:0% we simplify when you ever get in the 00:02:26.060 --> 00:02:28.510 align:start position:0% we simplify when you ever get in the scene<00:02:26.270> details<00:02:26.390> you'd<00:02:27.320> report<00:02:27.650> when<00:02:28.220> they<00:02:28.340> get 00:02:28.510 --> 00:02:28.520 align:start position:0% scene details you'd report when they get 00:02:28.520 --> 00:02:36.730 align:start position:0% scene details you'd report when they get twice<00:02:28.850> per<00:02:29.120> section 00:02:36.730 --> 00:02:36.740 align:start position:0% 00:02:36.740 --> 00:02:39.940 align:start position:0% be<00:02:37.280> the<00:02:37.700> fact<00:02:37.970> that<00:02:38.210> because<00:02:38.960> I<00:02:39.170> give<00:02:39.350> them<00:02:39.560> is 00:02:39.940 --> 00:02:39.950 align:start position:0% be the fact that because I give them is 00:02:39.950 --> 00:02:42.850 align:start position:0% be the fact that because I give them is that<00:02:40.720> they<00:02:41.720> have<00:02:41.750> application<00:02:42.590> for<00:02:42.770> the 00:02:42.850 --> 00:02:42.860 align:start position:0% that they have application for the 00:02:42.860 --> 00:02:46.980 align:start position:0% that they have application for the control<00:02:43.250> just<00:02:43.850> use<00:02:44.060> one<00:02:44.480> of<00:02:44.510> them<00:02:45.520> and<00:02:46.520> then 00:02:46.980 --> 00:02:46.990 align:start position:0% control just use one of them and then 00:02:46.990 --> 00:02:51.580 align:start position:0% control just use one of them and then its<00:02:47.990> importance<00:02:48.500> but<00:02:48.940> dozens<00:02:49.940> of<00:02:50.590> addiction 00:02:51.580 --> 00:02:51.590 align:start position:0% its importance but dozens of addiction 00:02:51.590 --> 00:02:53.050 align:start position:0% its importance but dozens of addiction public<00:02:51.890> art<00:02:52.070> but<00:02:52.250> then<00:02:52.370> an<00:02:52.460> event<00:02:52.610> is 00:02:53.050 --> 00:02:53.060 align:start position:0% public art but then an event is 00:02:53.060 --> 00:02:55.240 align:start position:0% public art but then an event is Byzantine<00:02:53.600> jolly<00:02:54.080> well<00:02:54.260> fantastic<00:02:54.740> some<00:02:55.130> of 00:02:55.240 --> 00:02:55.250 align:start position:0% Byzantine jolly well fantastic some of 00:02:55.250 --> 00:03:02.290 align:start position:0% Byzantine jolly well fantastic some of them<00:02:56.110> some<00:02:57.110> of<00:02:57.200> us<00:02:58.420> about<00:02:59.420> nervousness<00:03:00.170> so<00:03:01.300> if 00:03:02.290 --> 00:03:02.300 align:start position:0% them some of us about nervousness so if 00:03:02.300 --> 00:03:05.530 align:start position:0% them some of us about nervousness so if I<00:03:02.480> ask<00:03:02.810> what<00:03:03.470> hundred<00:03:03.890> is<00:03:03.950> about<00:03:04.220> we<00:03:05.120> can<00:03:05.330> guess 00:03:05.530 --> 00:03:05.540 align:start position:0% I ask what hundred is about we can guess 00:03:05.540 --> 00:03:10.080 align:start position:0% I ask what hundred is about we can guess that<00:03:06.640> it's<00:03:07.640> a<00:03:07.760> gating<00:03:08.120> via<00:03:08.300> the<00:03:08.390> signature 00:03:10.080 --> 00:03:10.090 align:start position:0% that it's a gating via the signature 00:03:10.090 --> 00:03:13.840 align:start position:0% that it's a gating via the signature being<00:03:11.090> fast<00:03:11.390> and<00:03:11.750> we<00:03:12.710> say<00:03:12.890> fast<00:03:13.160> it's<00:03:13.400> possible 00:03:13.840 --> 00:03:13.850 align:start position:0% being fast and we say fast it's possible 00:03:13.850 --> 00:03:18.340 align:start position:0% being fast and we say fast it's possible signatures<00:03:14.270> ability<00:03:14.870> in<00:03:15.440> seconds<00:03:15.920> I<00:03:17.350> can't 00:03:18.340 --> 00:03:18.350 align:start position:0% signatures ability in seconds I can't 00:03:18.350 --> 00:03:19.750 align:start position:0% signatures ability in seconds I can't internal<00:03:18.740> so<00:03:19.010> you're<00:03:19.160> going<00:03:19.340> to<00:03:19.430> aggregate 00:03:19.750 --> 00:03:19.760 align:start position:0% internal so you're going to aggregate 00:03:19.760 --> 00:03:21.880 align:start position:0% internal so you're going to aggregate between<00:03:20.360> thousands<00:03:20.720> of<00:03:20.810> notes<00:03:21.020> and<00:03:21.290> some<00:03:21.770> of 00:03:21.880 --> 00:03:21.890 align:start position:0% between thousands of notes and some of 00:03:21.890 --> 00:03:25.540 align:start position:0% between thousands of notes and some of its<00:03:22.040> notes<00:03:22.310> we'll<00:03:22.940> try<00:03:23.270> to<00:03:24.170> cut<00:03:24.890> down<00:03:25.040> by<00:03:25.520> the 00:03:25.540 --> 00:03:25.550 align:start position:0% its notes we'll try to cut down by the 00:03:25.550 --> 00:03:31.000 align:start position:0% its notes we'll try to cut down by the minute<00:03:27.490> we<00:03:28.490> can<00:03:28.640> do<00:03:28.760> whatever<00:03:28.880> levels<00:03:29.390> and<00:03:30.350> in 00:03:31.000 --> 00:03:31.010 align:start position:0% minute we can do whatever levels and in 00:03:31.010 --> 00:03:33.220 align:start position:0% minute we can do whatever levels and in your<00:03:31.190> life<00:03:31.370> which<00:03:31.610> we<00:03:31.790> have<00:03:31.910> a<00:03:32.060> family<00:03:32.510> not 00:03:33.220 --> 00:03:33.230 align:start position:0% your life which we have a family not 00:03:33.230 --> 00:03:38.650 align:start position:0% your life which we have a family not without<00:03:33.560> us<00:03:33.770> that 00:03:38.650 --> 00:03:38.660 align:start position:0% 00:03:38.660 --> 00:03:42.970 align:start position:0% a<00:03:38.690> lot<00:03:39.500> of<00:03:39.650> diversity<00:03:40.190> I<00:03:40.790> buy<00:03:41.570> this<00:03:41.630> but<00:03:42.560> in<00:03:42.860> a 00:03:42.970 --> 00:03:42.980 align:start position:0% a lot of diversity I buy this but in a 00:03:42.980 --> 00:03:46.840 align:start position:0% a lot of diversity I buy this but in a network<00:03:44.740> you<00:03:45.740> will<00:03:45.890> have<00:03:46.040> thousands<00:03:46.550> of<00:03:46.580> nodes 00:03:46.840 --> 00:03:46.850 align:start position:0% network you will have thousands of nodes 00:03:46.850 --> 00:03:48.580 align:start position:0% network you will have thousands of nodes with<00:03:47.270> different<00:03:47.630> capacity<00:03:48.110> some<00:03:48.350> of<00:03:48.470> them 00:03:48.580 --> 00:03:48.590 align:start position:0% with different capacity some of them 00:03:48.590 --> 00:03:54.460 align:start position:0% with different capacity some of them very<00:03:48.770> fast<00:03:48.980> of<00:03:49.430> their<00:03:49.610> slope<00:03:52.300> as<00:03:53.300> it<00:03:53.450> is<00:03:53.600> some 00:03:54.460 --> 00:03:54.470 align:start position:0% very fast of their slope as it is some 00:03:54.470 --> 00:03:55.570 align:start position:0% very fast of their slope as it is some of<00:03:54.590> them<00:03:54.770> will<00:03:55.010> be<00:03:55.130> when<00:03:55.370> we're 00:03:55.570 --> 00:03:55.580 align:start position:0% of them will be when we're 00:03:55.580 --> 00:03:57.630 align:start position:0% of them will be when we're interconnected<00:03:55.880> there<00:03:56.660> will<00:03:56.780> be<00:03:56.810> some<00:03:57.200> are 00:03:57.630 --> 00:03:57.640 align:start position:0% interconnected there will be some are 00:03:57.640 --> 00:04:00.460 align:start position:0% interconnected there will be some are lots<00:03:58.640> of<00:03:58.910> course<00:03:59.210> under<00:03:59.540> penalty<00:03:59.750> twice<00:04:00.200> and 00:04:00.460 --> 00:04:00.470 align:start position:0% lots of course under penalty twice and 00:04:00.470 --> 00:04:08.010 align:start position:0% lots of course under penalty twice and that<00:04:00.560> will<00:04:00.800> be<00:04:00.920> somewhere<00:04:01.220> else 00:04:08.010 --> 00:04:08.020 align:start position:0% 00:04:08.020 --> 00:04:11.980 align:start position:0% what<00:04:09.020> does<00:04:09.140> it<00:04:09.260> return<00:04:09.710> a<00:04:10.240> possible<00:04:11.240> plan<00:04:11.510> to 00:04:11.980 --> 00:04:11.990 align:start position:0% what does it return a possible plan to 00:04:11.990 --> 00:04:15.370 align:start position:0% what does it return a possible plan to use<00:04:12.140> and<00:04:12.380> improve<00:04:13.040> in<00:04:13.280> this<00:04:13.400> one<00:04:14.110> if<00:04:15.110> you<00:04:15.230> look 00:04:15.370 --> 00:04:15.380 align:start position:0% use and improve in this one if you look 00:04:15.380 --> 00:04:20.800 align:start position:0% use and improve in this one if you look at<00:04:15.740> a<00:04:16.100> specific<00:04:16.280> issue<00:04:18.070> we<00:04:19.070> took<00:04:19.630> what<00:04:20.630> we<00:04:20.780> had 00:04:20.800 --> 00:04:20.810 align:start position:0% at a specific issue we took what we had 00:04:20.810 --> 00:04:25.090 align:start position:0% at a specific issue we took what we had is<00:04:21.200> basically<00:04:22.870> in<00:04:23.870> the<00:04:23.990> south<00:04:24.260> we<00:04:24.710> target 00:04:25.090 --> 00:04:25.100 align:start position:0% is basically in the south we target 00:04:25.100 --> 00:04:35.710 align:start position:0% is basically in the south we target community<00:04:25.730> size<00:04:29.560> so<00:04:32.980> quickly<00:04:34.450> nobody<00:04:35.450> tells 00:04:35.710 --> 00:04:35.720 align:start position:0% community size so quickly nobody tells 00:04:35.720 --> 00:04:38.140 align:start position:0% community size so quickly nobody tells of<00:04:35.870> the<00:04:35.960> size<00:04:36.200> the<00:04:36.800> committee<00:04:37.220> in<00:04:37.970> this 00:04:38.140 --> 00:04:38.150 align:start position:0% of the size the committee in this 00:04:38.150 --> 00:04:41.500 align:start position:0% of the size the committee in this wonderfully<00:04:38.810> visited<00:04:39.320> one<00:04:40.040> one<00:04:41.000> second<00:04:41.390> over 00:04:41.500 --> 00:04:41.510 align:start position:0% wonderfully visited one one second over 00:04:41.510 --> 00:04:47.620 align:start position:0% wonderfully visited one one second over time<00:04:41.950> as<00:04:42.950> well<00:04:45.670> become<00:04:46.670> centimeters<00:04:47.390> of 00:04:47.620 --> 00:04:47.630 align:start position:0% time as well become centimeters of 00:04:47.630 --> 00:04:51.120 align:start position:0% time as well become centimeters of Earth's<00:04:48.190> vision<00:04:49.190> is<00:04:49.280> what<00:04:49.490> you<00:04:49.700> I<00:04:49.990> forget 00:04:51.120 --> 00:04:51.130 align:start position:0% Earth's vision is what you I forget 00:04:51.130 --> 00:04:54.580 align:start position:0% Earth's vision is what you I forget comma<00:04:52.130> become<00:04:52.460> shy<00:04:52.670> and<00:04:53.000> at<00:04:53.390> this<00:04:53.540> point<00:04:53.750> what 00:04:54.580 --> 00:04:54.590 align:start position:0% comma become shy and at this point what 00:04:54.590 --> 00:04:57.100 align:start position:0% comma become shy and at this point what you<00:04:55.580> both<00:04:55.730> will<00:04:55.970> harvest<00:04:56.300> accepting<00:04:56.930> a 00:04:57.100 --> 00:04:57.110 align:start position:0% you both will harvest accepting a 00:04:57.110 --> 00:04:59.860 align:start position:0% you both will harvest accepting a picture<00:04:58.040> of<00:04:58.460> a<00:04:58.580> super<00:04:58.820> what<00:04:59.030> you<00:04:59.300> think<00:04:59.540> is 00:04:59.860 --> 00:04:59.870 align:start position:0% picture of a super what you think is 00:04:59.870 --> 00:05:03.880 align:start position:0% picture of a super what you think is let's<00:05:00.530> select<00:05:00.830> a<00:05:01.160> subset<00:05:02.000> of<00:05:02.450> a<00:05:03.290> node<00:05:03.470> from<00:05:03.710> the 00:05:03.880 --> 00:05:03.890 align:start position:0% let's select a subset of a node from the 00:05:03.890 --> 00:05:07.570 align:start position:0% let's select a subset of a node from the committee's<00:05:04.660> 16<00:05:05.770> unless<00:05:06.770> as<00:05:07.100> well 00:05:07.570 --> 00:05:07.580 align:start position:0% committee's 16 unless as well 00:05:07.580 --> 00:05:10.000 align:start position:0% committee's 16 unless as well variation<00:05:08.300> forward<00:05:08.930> become<00:05:09.170> show<00:05:09.350> and<00:05:09.800> we 00:05:10.000 --> 00:05:10.010 align:start position:0% variation forward become show and we 00:05:10.010 --> 00:05:11.740 align:start position:0% variation forward become show and we have<00:05:10.220> despite<00:05:10.820> an<00:05:10.970> education<00:05:11.450> different 00:05:11.740 --> 00:05:11.750 align:start position:0% have despite an education different 00:05:11.750 --> 00:05:14.830 align:start position:0% have despite an education different 16000 00:05:14.830 --> 00:05:14.840 align:start position:0% 00:05:14.840 --> 00:05:17.409 align:start position:0% how<00:05:15.380> do<00:05:15.440> you<00:05:15.530> miss<00:05:15.800> to<00:05:15.919> be<00:05:16.040> fast<00:05:16.250> because<00:05:16.419> the 00:05:17.409 --> 00:05:17.419 align:start position:0% how do you miss to be fast because the 00:05:17.419 --> 00:05:19.540 align:start position:0% how do you miss to be fast because the land<00:05:17.690> is<00:05:17.870> if<00:05:18.169> you<00:05:18.260> can<00:05:18.440> be<00:05:18.560> very<00:05:18.770> fast<00:05:19.040> about 00:05:19.540 --> 00:05:19.550 align:start position:0% land is if you can be very fast about 00:05:19.550 --> 00:05:21.040 align:start position:0% land is if you can be very fast about one<00:05:19.730> or<00:05:19.910> two<00:05:19.940> seconds<00:05:20.389> pounds<00:05:20.750> for<00:05:21.020> a 00:05:21.040 --> 00:05:21.050 align:start position:0% one or two seconds pounds for a 00:05:21.050 --> 00:05:23.260 align:start position:0% one or two seconds pounds for a traditional<00:05:21.260> leopard<00:05:21.680> it<00:05:22.340> means<00:05:22.580> that<00:05:22.790> in<00:05:23.090> two 00:05:23.260 --> 00:05:23.270 align:start position:0% traditional leopard it means that in two 00:05:23.270 --> 00:05:28.330 align:start position:0% traditional leopard it means that in two gloves<00:05:23.480> to<00:05:23.840> petrify<00:05:24.169> deity<00:05:26.950> so<00:05:27.950> that's<00:05:28.130> what 00:05:28.330 --> 00:05:28.340 align:start position:0% gloves to petrify deity so that's what 00:05:28.340 --> 00:05:32.140 align:start position:0% gloves to petrify deity so that's what what<00:05:28.520> to<00:05:28.669> do<00:05:28.850> and<00:05:29.419> we<00:05:29.630> set<00:05:30.550> some<00:05:31.550> taxes<00:05:31.850> to<00:05:32.000> them 00:05:32.140 --> 00:05:32.150 align:start position:0% what to do and we set some taxes to them 00:05:32.150 --> 00:05:35.200 align:start position:0% what to do and we set some taxes to them whatever<00:05:32.870> so<00:05:33.290> about<00:05:33.560> us<00:05:34.070> so<00:05:34.850> when<00:05:35.030> you<00:05:35.120> have 00:05:35.200 --> 00:05:35.210 align:start position:0% whatever so about us so when you have 00:05:35.210 --> 00:05:37.360 align:start position:0% whatever so about us so when you have such<00:05:35.419> a<00:05:35.450> problem<00:05:35.750> as<00:05:36.410> if<00:05:36.620> you<00:05:36.770> looking<00:05:37.220> at 00:05:37.360 --> 00:05:37.370 align:start position:0% such a problem as if you looking at 00:05:37.370 --> 00:05:38.110 align:start position:0% such a problem as if you looking at competitively 00:05:38.110 --> 00:05:38.120 align:start position:0% competitively 00:05:38.120 --> 00:05:40.390 align:start position:0% competitively through<00:05:38.660> the<00:05:38.900> time<00:05:39.110> complexity<00:05:39.530> and<00:05:39.889> message 00:05:40.390 --> 00:05:40.400 align:start position:0% through the time complexity and message 00:05:40.400 --> 00:05:43.450 align:start position:0% through the time complexity and message complexity<00:05:41.230> annual<00:05:42.230> is<00:05:42.320> not<00:05:42.590> porous<00:05:43.070> and 00:05:43.450 --> 00:05:43.460 align:start position:0% complexity annual is not porous and 00:05:43.460 --> 00:05:45.790 align:start position:0% complexity annual is not porous and decided<00:05:43.940> you<00:05:43.970> can<00:05:44.240> learn<00:05:44.419> more<00:05:44.660> for<00:05:44.840> me<00:05:45.080> on 00:05:45.790 --> 00:05:45.800 align:start position:0% decided you can learn more for me on 00:05:45.800 --> 00:05:49.150 align:start position:0% decided you can learn more for me on this<00:05:46.010> size<00:05:46.250> of<00:05:46.610> his<00:05:46.760> money<00:05:46.970> okay<00:05:47.900> and<00:05:48.260> we'll 00:05:49.150 --> 00:05:49.160 align:start position:0% this size of his money okay and we'll 00:05:49.160 --> 00:05:52.270 align:start position:0% this size of his money okay and we'll see<00:05:49.340> that<00:05:49.370> some<00:05:49.580> particles<00:05:49.910> as<00:05:50.870> the<00:05:51.560> initials 00:05:52.270 --> 00:05:52.280 align:start position:0% see that some particles as the initials 00:05:52.280 --> 00:05:53.740 align:start position:0% see that some particles as the initials are<00:05:52.400> quite<00:05:52.610> easy<00:05:52.639> to<00:05:52.910> aggregate<00:05:53.240> it's<00:05:53.600> very 00:05:53.740 --> 00:05:53.750 align:start position:0% are quite easy to aggregate it's very 00:05:53.750 --> 00:05:55.000 align:start position:0% are quite easy to aggregate it's very very<00:05:53.990> nice 00:05:55.000 --> 00:05:55.010 align:start position:0% very nice 00:05:55.010 --> 00:05:59.290 align:start position:0% very nice so<00:05:56.260> time<00:05:57.260> complexity<00:05:57.710> is<00:05:57.889> easy<00:05:58.220> to<00:05:58.430> get<00:05:58.610> our 00:05:59.290 --> 00:05:59.300 align:start position:0% so time complexity is easy to get our 00:05:59.300 --> 00:06:09.640 align:start position:0% so time complexity is easy to get our message<00:06:05.919> so<00:06:06.940> thanks<00:06:08.080> just<00:06:09.080> a<00:06:09.200> simple<00:06:09.380> this 00:06:09.640 --> 00:06:09.650 align:start position:0% message so thanks just a simple this 00:06:09.650 --> 00:06:12.040 align:start position:0% message so thanks just a simple this evening<00:06:09.919> solution<00:06:10.310> by<00:06:10.820> simple<00:06:11.180> visiting<00:06:11.660> I'll 00:06:12.040 --> 00:06:12.050 align:start position:0% evening solution by simple visiting I'll 00:06:12.050 --> 00:06:16.060 align:start position:0% evening solution by simple visiting I'll tell<00:06:12.290> you<00:06:12.410> just<00:06:13.479> the<00:06:14.479> fruit<00:06:14.780> busy<00:06:15.169> pursuing 00:06:16.060 --> 00:06:16.070 align:start position:0% tell you just the fruit busy pursuing 00:06:16.070 --> 00:06:18.719 align:start position:0% tell you just the fruit busy pursuing stuff<00:06:16.460> not<00:06:17.030> just<00:06:17.240> sending<00:06:17.540> your<00:06:17.690> signature 00:06:18.719 --> 00:06:18.729 align:start position:0% stuff not just sending your signature 00:06:18.729 --> 00:06:28.960 align:start position:0% stuff not just sending your signature everybody<00:06:19.729> does<00:06:19.880> that<00:06:20.060> and<00:06:20.330> so<00:06:27.760> and<00:06:28.760> it's<00:06:28.880> not 00:06:28.960 --> 00:06:28.970 align:start position:0% everybody does that and so and it's not 00:06:28.970 --> 00:06:32.590 align:start position:0% everybody does that and so and it's not absolutely<00:06:29.600> bad<00:06:31.000> you<00:06:32.000> will<00:06:32.120> have<00:06:32.240> this<00:06:32.390> time 00:06:32.590 --> 00:06:32.600 align:start position:0% absolutely bad you will have this time 00:06:32.600 --> 00:06:36.340 align:start position:0% absolutely bad you will have this time complexity<00:06:33.020> and<00:06:34.060> basically<00:06:35.060> because<00:06:35.360> such<00:06:36.229> a 00:06:36.340 --> 00:06:36.350 align:start position:0% complexity and basically because such a 00:06:36.350 --> 00:06:38.350 align:start position:0% complexity and basically because such a fraternity<00:06:36.740> 12<00:06:37.039> and<00:06:37.280> you<00:06:37.340> expect<00:06:37.700> us<00:06:37.850> at<00:06:38.180> some 00:06:38.350 --> 00:06:38.360 align:start position:0% fraternity 12 and you expect us at some 00:06:38.360 --> 00:06:40.510 align:start position:0% fraternity 12 and you expect us at some definitions<00:06:38.539> overtime<00:06:39.289> capacity<00:06:39.440> is<00:06:39.919> good 00:06:40.510 --> 00:06:40.520 align:start position:0% definitions overtime capacity is good 00:06:40.520 --> 00:06:43.510 align:start position:0% definitions overtime capacity is good enjoy<00:06:40.850> and<00:06:41.390> the<00:06:42.020> message<00:06:42.289> complexity<00:06:42.740> do<00:06:43.100> all 00:06:43.510 --> 00:06:43.520 align:start position:0% enjoy and the message complexity do all 00:06:43.520 --> 00:06:45.909 align:start position:0% enjoy and the message complexity do all the<00:06:43.760> nodes<00:06:44.000> in<00:06:44.150> the<00:06:44.210> network<00:06:44.560> won't<00:06:45.560> assign 00:06:45.909 --> 00:06:45.919 align:start position:0% the nodes in the network won't assign 00:06:45.919 --> 00:06:47.700 align:start position:0% the nodes in the network won't assign once<00:06:46.190> accomplished 00:06:47.700 --> 00:06:47.710 align:start position:0% once accomplished 00:06:47.710 --> 00:06:51.770 align:start position:0% once accomplished Nichelle's<00:06:48.280> between<00:06:49.060> the<00:06:49.300> ends<00:06:49.539> well<00:06:50.220> minimum 00:06:51.770 --> 00:06:51.780 align:start position:0% Nichelle's between the ends well minimum 00:06:51.780 --> 00:06:54.300 align:start position:0% Nichelle's between the ends well minimum we<00:06:52.780> were<00:06:52.900> rooting<00:06:53.110> for<00:06:53.410> the<00:06:53.530> quality<00:06:53.979> that<00:06:54.009> we 00:06:54.300 --> 00:06:54.310 align:start position:0% we were rooting for the quality that we 00:06:54.310 --> 00:06:59.790 align:start position:0% we were rooting for the quality that we probably<00:06:54.630> can<00:06:55.630> extend<00:06:55.960> to<00:06:56.380> but<00:06:58.800> intonations 00:06:59.790 --> 00:06:59.800 align:start position:0% probably can extend to but intonations 00:06:59.800 --> 00:07:05.219 align:start position:0% probably can extend to but intonations of<00:07:01.050> alcohol<00:07:02.050> sweat<00:07:02.470> is<00:07:02.880> weapon<00:07:03.880> and<00:07:04.389> aggregate 00:07:05.219 --> 00:07:05.229 align:start position:0% of alcohol sweat is weapon and aggregate 00:07:05.229 --> 00:07:06.719 align:start position:0% of alcohol sweat is weapon and aggregate with<00:07:05.440> you<00:07:05.560> for<00:07:05.889> some<00:07:06.009> of<00:07:06.100> us<00:07:06.160> it's<00:07:06.610> a 00:07:06.719 --> 00:07:06.729 align:start position:0% with you for some of us it's a 00:07:06.729 --> 00:07:10.159 align:start position:0% with you for some of us it's a fixed-size 00:07:10.159 --> 00:07:10.169 align:start position:0% 00:07:10.169 --> 00:07:21.770 align:start position:0% which<00:07:11.169> is<00:07:17.729> a<00:07:18.729> vintage<00:07:19.199> 80s<00:07:20.310> which<00:07:21.310> is 00:07:21.770 --> 00:07:21.780 align:start position:0% which is a vintage 80s which is 00:07:21.780 --> 00:07:26.670 align:start position:0% which is a vintage 80s which is especially<00:07:24.360> the<00:07:25.360> current<00:07:25.750> survey<00:07:25.990> that<00:07:26.349> slow 00:07:26.670 --> 00:07:26.680 align:start position:0% especially the current survey that slow 00:07:26.680 --> 00:07:34.920 align:start position:0% especially the current survey that slow but<00:07:27.340> is<00:07:27.580> to<00:07:28.030> travel<00:07:32.280> with<00:07:33.280> like<00:07:33.550> this<00:07:33.729> so<00:07:34.090> of 00:07:34.920 --> 00:07:34.930 align:start position:0% but is to travel with like this so of 00:07:34.930 --> 00:07:37.830 align:start position:0% but is to travel with like this so of the<00:07:35.139> DS<00:07:35.500> issues<00:07:35.830> twin<00:07:36.070> cities<00:07:36.389> and<00:07:37.389> some<00:07:37.660> so 00:07:37.830 --> 00:07:37.840 align:start position:0% the DS issues twin cities and some so 00:07:37.840 --> 00:07:39.210 align:start position:0% the DS issues twin cities and some so what<00:07:37.960> we<00:07:38.080> find<00:07:38.289> the<00:07:38.470> beginning<00:07:38.590> is<00:07:38.949> active 00:07:39.210 --> 00:07:39.220 align:start position:0% what we find the beginning is active 00:07:39.220 --> 00:07:41.730 align:start position:0% what we find the beginning is active then<00:07:39.400> we<00:07:39.580> continue<00:07:40.479> on<00:07:40.930> the<00:07:41.020> recipe<00:07:41.380> network 00:07:41.730 --> 00:07:41.740 align:start position:0% then we continue on the recipe network 00:07:41.740 --> 00:07:43.950 align:start position:0% then we continue on the recipe network but<00:07:42.460> can<00:07:42.759> be<00:07:42.910> kind<00:07:43.120> of<00:07:43.210> confessing<00:07:43.720> things 00:07:43.950 --> 00:07:43.960 align:start position:0% but can be kind of confessing things 00:07:43.960 --> 00:07:46.589 align:start position:0% but can be kind of confessing things like<00:07:44.770> if<00:07:45.099> we<00:07:45.220> can<00:07:45.400> aggregate<00:07:45.729> so<00:07:46.389> as<00:07:46.570> a 00:07:46.589 --> 00:07:46.599 align:start position:0% like if we can aggregate so as a 00:07:46.599 --> 00:07:50.219 align:start position:0% like if we can aggregate so as a receiver<00:07:47.440> signature<00:07:47.860> becoming<00:07:48.280> a<00:07:48.490> get<00:07:49.229> we 00:07:50.219 --> 00:07:50.229 align:start position:0% receiver signature becoming a get we 00:07:50.229 --> 00:07:51.600 align:start position:0% receiver signature becoming a get we will<00:07:50.380> and<00:07:50.740> instead<00:07:51.009> of<00:07:51.099> sending<00:07:51.310> our 00:07:51.600 --> 00:07:51.610 align:start position:0% will and instead of sending our 00:07:51.610 --> 00:07:54.649 align:start position:0% will and instead of sending our solutions<00:07:52.120> will<00:07:52.630> send<00:07:52.900> some<00:07:53.020> a<00:07:53.139> high<00:07:53.289> negative 00:07:54.649 --> 00:07:54.659 align:start position:0% solutions will send some a high negative 00:07:54.659 --> 00:07:57.689 align:start position:0% solutions will send some a high negative it<00:07:55.659> in<00:07:55.810> hyper<00:07:56.020> to<00:07:56.289> verify<00:07:56.650> this<00:07:57.190> part<00:07:57.460> because 00:07:57.689 --> 00:07:57.699 align:start position:0% it in hyper to verify this part because 00:07:57.699 --> 00:07:59.490 align:start position:0% it in hyper to verify this part because if<00:07:57.820> someone's<00:07:58.180> and<00:07:58.449> to<00:07:58.539> a<00:07:58.570> back<00:07:58.780> to<00:07:58.930> nature<00:07:59.110> and 00:07:59.490 --> 00:07:59.500 align:start position:0% if someone's and to a back to nature and 00:07:59.500 --> 00:08:02.370 align:start position:0% if someone's and to a back to nature and we<00:08:00.130> get<00:08:00.460> without<00:08:00.729> verification<00:08:01.199> when<00:08:02.199> your 00:08:02.370 --> 00:08:02.380 align:start position:0% we get without verification when your 00:08:02.380 --> 00:08:06.089 align:start position:0% we get without verification when your whole<00:08:02.530> thr<00:08:02.979> will<00:08:03.130> be<00:08:03.220> bad<00:08:04.320> too<00:08:05.349> when<00:08:05.740> you<00:08:05.860> stop 00:08:06.089 --> 00:08:06.099 align:start position:0% whole thr will be bad too when you stop 00:08:06.099 --> 00:08:07.290 align:start position:0% whole thr will be bad too when you stop to<00:08:06.190> do<00:08:06.310> this<00:08:06.430> you<00:08:06.610> have<00:08:06.639> to<00:08:06.729> make 00:08:07.290 --> 00:08:07.300 align:start position:0% to do this you have to make 00:08:07.300 --> 00:08:11.760 align:start position:0% to do this you have to make a<00:08:08.010> variation<00:08:09.010> that<00:08:09.040> you<00:08:09.190> receive<00:08:09.990> and<00:08:10.990> the<00:08:11.020> men 00:08:11.760 --> 00:08:11.770 align:start position:0% a variation that you receive and the men 00:08:11.770 --> 00:08:13.440 align:start position:0% a variation that you receive and the men will<00:08:11.980> not<00:08:12.280> work<00:08:12.490> on<00:08:12.610> that<00:08:12.790> because<00:08:13.060> different 00:08:13.440 --> 00:08:13.450 align:start position:0% will not work on that because different 00:08:13.450 --> 00:08:16.200 align:start position:0% will not work on that because different sending<00:08:13.810> something<00:08:14.020> integrity<00:08:14.980> and<00:08:15.820> someone 00:08:16.200 --> 00:08:16.210 align:start position:0% sending something integrity and someone 00:08:16.210 --> 00:08:19.650 align:start position:0% sending something integrity and someone else<00:08:16.390> as<00:08:16.630> I<00:08:16.750> created<00:08:17.020> and<00:08:17.380> it<00:08:17.590> allowed<00:08:18.660> your 00:08:19.650 --> 00:08:19.660 align:start position:0% else as I created and it allowed your 00:08:19.660 --> 00:08:25.080 align:start position:0% else as I created and it allowed your debt<00:08:19.840> coming<00:08:20.470> in<00:08:20.920> on<00:08:21.370> a<00:08:21.940> new<00:08:22.060> service<00:08:22.800> so<00:08:24.090> what 00:08:25.080 --> 00:08:25.090 align:start position:0% debt coming in on a new service so what 00:08:25.090 --> 00:08:26.850 align:start position:0% debt coming in on a new service so what we<00:08:25.240> did<00:08:25.360> at<00:08:25.420> this<00:08:25.600> one's<00:08:25.810> okay<00:08:25.990> actually<00:08:26.530> we 00:08:26.850 --> 00:08:26.860 align:start position:0% we did at this one's okay actually we 00:08:26.860 --> 00:08:30.240 align:start position:0% we did at this one's okay actually we know<00:08:27.040> all<00:08:27.310> the<00:08:27.790> signups<00:08:28.350> also<00:08:29.350> nominees<00:08:29.980> this 00:08:30.240 --> 00:08:30.250 align:start position:0% know all the signups also nominees this 00:08:30.250 --> 00:08:33.420 align:start position:0% know all the signups also nominees this committee<00:08:30.670> so<00:08:30.940> we<00:08:31.840> can<00:08:32.170> give<00:08:32.590> our<00:08:32.710> body<00:08:33.040> just 00:08:33.420 --> 00:08:33.430 align:start position:0% committee so we can give our body just 00:08:33.430 --> 00:08:35.490 align:start position:0% committee so we can give our body just by<00:08:34.150> using<00:08:34.390> the<00:08:34.660> public<00:08:34.810> key<00:08:34.990> that<00:08:35.140> we<00:08:35.380> know 00:08:35.490 --> 00:08:35.500 align:start position:0% by using the public key that we know 00:08:35.500 --> 00:08:38.700 align:start position:0% by using the public key that we know which<00:08:35.740> is<00:08:35.860> so<00:08:36.040> based<00:08:36.280> on<00:08:36.490> the<00:08:36.640> position<00:08:37.120> in<00:08:37.710> the 00:08:38.700 --> 00:08:38.710 align:start position:0% which is so based on the position in the 00:08:38.710 --> 00:08:41.970 align:start position:0% which is so based on the position in the power<00:08:39.420> will<00:08:40.420> be<00:08:40.570> the<00:08:40.750> light<00:08:40.930> so<00:08:41.650> we<00:08:41.680> know<00:08:41.950> that 00:08:41.970 --> 00:08:41.980 align:start position:0% power will be the light so we know that 00:08:41.980 --> 00:08:46.740 align:start position:0% power will be the light so we know that but<00:08:42.460> now<00:08:42.730> a<00:08:42.760> set<00:08:43.180> of<00:08:43.210> notes<00:08:43.600> with<00:08:44.200> no<00:08:44.350> cones<00:08:45.750> so 00:08:46.740 --> 00:08:46.750 align:start position:0% but now a set of notes with no cones so 00:08:46.750 --> 00:08:48.890 align:start position:0% but now a set of notes with no cones so there<00:08:46.990> is<00:08:47.500> a<00:08:47.530> component<00:08:47.860> that's<00:08:48.070> eight<00:08:48.580> notes 00:08:48.890 --> 00:08:48.900 align:start position:0% there is a component that's eight notes 00:08:48.900 --> 00:08:51.060 align:start position:0% there is a component that's eight notes is<00:08:49.900> 0<00:08:50.080> 1<00:08:50.380> and<00:08:50.680> so<00:08:50.740> on 00:08:51.060 --> 00:08:51.070 align:start position:0% is 0 1 and so on 00:08:51.070 --> 00:08:53.100 align:start position:0% is 0 1 and so on and<00:08:51.400> we<00:08:51.550> are<00:08:51.610> kind<00:08:52.090> of<00:08:52.210> organizing<00:08:52.870> where<00:08:52.990> my 00:08:53.100 --> 00:08:53.110 align:start position:0% and we are kind of organizing where my 00:08:53.110 --> 00:08:55.110 align:start position:0% and we are kind of organizing where my conditional<00:08:53.590> my<00:08:53.710> syndicate<00:08:53.980> when<00:08:54.640> not<00:08:54.790> 0<00:08:55.090> we 00:08:55.110 --> 00:08:55.120 align:start position:0% conditional my syndicate when not 0 we 00:08:55.120 --> 00:08:57.420 align:start position:0% conditional my syndicate when not 0 we aggregate<00:08:55.780> the<00:08:55.840> signature<00:08:56.380> on<00:08:56.590> that<00:08:56.620> one<00:08:56.920> and 00:08:57.420 --> 00:08:57.430 align:start position:0% aggregate the signature on that one and 00:08:57.430 --> 00:08:58.710 align:start position:0% aggregate the signature on that one and that's<00:08:57.640> it<00:08:57.760> so<00:08:58.000> if<00:08:58.180> you<00:08:58.300> miss<00:08:58.450> you<00:08:58.600> the 00:08:58.710 --> 00:08:58.720 align:start position:0% that's it so if you miss you the 00:08:58.720 --> 00:09:01.230 align:start position:0% that's it so if you miss you the solution<00:08:59.140> for<00:08:59.290> not<00:08:59.410> one<00:08:59.590> attacker<00:09:00.430> gets<00:09:00.670> is 00:09:01.230 --> 00:09:01.240 align:start position:0% solution for not one attacker gets is 00:09:01.240 --> 00:09:05.700 align:start position:0% solution for not one attacker gets is not<00:09:01.480> quite<00:09:02.470> by<00:09:03.210> cell<00:09:04.210> phone<00:09:04.420> to<00:09:04.750> actually<00:09:05.350> run 00:09:05.700 --> 00:09:05.710 align:start position:0% not quite by cell phone to actually run 00:09:05.710 --> 00:09:08.550 align:start position:0% not quite by cell phone to actually run five<00:09:06.070> exam<00:09:06.430> and<00:09:06.850> you<00:09:07.690> can<00:09:07.900> move<00:09:08.080> on<00:09:08.230> to<00:09:08.260> a<00:09:08.410> next 00:09:08.550 --> 00:09:08.560 align:start position:0% five exam and you can move on to a next 00:09:08.560 --> 00:09:11.790 align:start position:0% five exam and you can move on to a next event<00:09:08.920> additional<00:09:09.280> activity<00:09:09.910> -<00:09:10.810> and<00:09:11.530> now<00:09:11.740> we 00:09:11.790 --> 00:09:11.800 align:start position:0% event additional activity - and now we 00:09:11.800 --> 00:09:15.330 align:start position:0% event additional activity - and now we receive<00:09:12.280> two<00:09:12.460> and<00:09:12.580> three<00:09:12.760> I<00:09:13.390> think<00:09:13.750> it<00:09:14.220> so<00:09:15.220> much 00:09:15.330 --> 00:09:15.340 align:start position:0% receive two and three I think it so much 00:09:15.340 --> 00:09:20.220 align:start position:0% receive two and three I think it so much you're<00:09:15.490> spotted<00:09:15.790> you<00:09:16.590> it's<00:09:17.590> it's<00:09:18.370> nice<00:09:19.230> it's 00:09:20.220 --> 00:09:20.230 align:start position:0% you're spotted you it's it's nice it's 00:09:20.230 --> 00:09:25.050 align:start position:0% you're spotted you it's it's nice it's nice<00:09:20.440> but<00:09:21.780> good<00:09:22.780> points<00:09:23.140> among<00:09:23.830> us<00:09:24.340> or<00:09:24.910> less 00:09:25.050 --> 00:09:25.060 align:start position:0% nice but good points among us or less 00:09:25.060 --> 00:09:28.980 align:start position:0% nice but good points among us or less difficult<00:09:25.330> the<00:09:25.960> last<00:09:27.780> possibilities<00:09:28.780> time 00:09:28.980 --> 00:09:28.990 align:start position:0% difficult the last possibilities time 00:09:28.990 --> 00:09:31.210 align:start position:0% difficult the last possibilities time again<00:09:29.230> busy<00:09:29.440> to<00:09:29.590> actually<00:09:29.890> receive 00:09:31.210 --> 00:09:31.220 align:start position:0% again busy to actually receive 00:09:31.220 --> 00:09:33.920 align:start position:0% again busy to actually receive two<00:09:32.220> things<00:09:32.459> can<00:09:33.089> we<00:09:33.240> wait<00:09:33.390> a<00:09:33.420> little<00:09:33.600> bit 00:09:33.920 --> 00:09:33.930 align:start position:0% two things can we wait a little bit 00:09:33.930 --> 00:09:38.780 align:start position:0% two things can we wait a little bit longer<00:09:33.990> and<00:09:34.649> so<00:09:35.160> you<00:09:35.370> can<00:09:35.490> do<00:09:35.610> things<00:09:35.760> but<00:09:37.790> you 00:09:38.780 --> 00:09:38.790 align:start position:0% longer and so you can do things but you 00:09:38.790 --> 00:09:41.980 align:start position:0% longer and so you can do things but you feel<00:09:39.029> relieved<00:09:39.690> at<00:09:39.839> least<00:09:40.019> nothing<00:09:40.170> to<00:09:40.440> fight 00:09:41.980 --> 00:09:41.990 align:start position:0% feel relieved at least nothing to fight 00:09:41.990 --> 00:09:45.980 align:start position:0% feel relieved at least nothing to fight so<00:09:42.990> you<00:09:43.050> need<00:09:43.230> to<00:09:43.350> do<00:09:43.470> something<00:09:43.769> better<00:09:44.990> at 00:09:45.980 --> 00:09:45.990 align:start position:0% so you need to do something better at 00:09:45.990 --> 00:09:51.579 align:start position:0% so you need to do something better at this<00:09:46.200> part<00:09:46.700> we<00:09:47.700> produce<00:09:48.570> a<00:09:49.019> set<00:09:49.740> of<00:09:49.890> techniques 00:09:51.579 --> 00:09:51.589 align:start position:0% this part we produce a set of techniques 00:09:51.589 --> 00:10:00.500 align:start position:0% this part we produce a set of techniques so<00:09:53.180> actually<00:09:54.180> because<00:09:55.050> someone<00:09:56.029> wants<00:09:59.390> a<00:10:00.390> to 00:10:00.500 --> 00:10:00.510 align:start position:0% so actually because someone wants a to 00:10:00.510 --> 00:10:02.780 align:start position:0% so actually because someone wants a to be<00:10:00.600> symmetrical<00:10:01.260> okay<00:10:01.620> you<00:10:01.769> practice<00:10:02.399> you 00:10:02.780 --> 00:10:02.790 align:start position:0% be symmetrical okay you practice you 00:10:02.790 --> 00:10:04.460 align:start position:0% be symmetrical okay you practice you know<00:10:02.940> what<00:10:03.120> we're<00:10:03.269> not<00:10:03.420> a<00:10:03.450> baby<00:10:03.839> any<00:10:04.079> ideas 00:10:04.460 --> 00:10:04.470 align:start position:0% know what we're not a baby any ideas 00:10:04.470 --> 00:10:07.160 align:start position:0% know what we're not a baby any ideas anything<00:10:04.829> instead<00:10:05.700> of<00:10:05.970> kind<00:10:06.450> of<00:10:06.570> open<00:10:07.140> that 00:10:07.160 --> 00:10:07.170 align:start position:0% anything instead of kind of open that 00:10:07.170 --> 00:10:09.500 align:start position:0% anything instead of kind of open that you<00:10:08.130> will<00:10:08.279> get<00:10:08.459> the<00:10:08.579> signature<00:10:08.940> from<00:10:09.000> water<00:10:09.329> to 00:10:09.500 --> 00:10:09.510 align:start position:0% you will get the signature from water to 00:10:09.510 --> 00:10:11.360 align:start position:0% you will get the signature from water to parts<00:10:09.779> of<00:10:09.930> us<00:10:10.079> organizing<00:10:10.680> things<00:10:10.800> and<00:10:11.070> zero 00:10:11.360 --> 00:10:11.370 align:start position:0% parts of us organizing things and zero 00:10:11.370 --> 00:10:13.639 align:start position:0% parts of us organizing things and zero is<00:10:11.700> going<00:10:11.910> to<00:10:12.060> send<00:10:12.480> in<00:10:12.720> signatures<00:10:13.260> to<00:10:13.440> mind 00:10:13.639 --> 00:10:13.649 align:start position:0% is going to send in signatures to mind 00:10:13.649 --> 00:10:16.550 align:start position:0% is going to send in signatures to mind because<00:10:13.829> you<00:10:14.070> know<00:10:14.820> as<00:10:15.149> one<00:10:15.570> with<00:10:16.140> entities 00:10:16.550 --> 00:10:16.560 align:start position:0% because you know as one with entities 00:10:16.560 --> 00:10:18.860 align:start position:0% because you know as one with entities but<00:10:17.550> this<00:10:17.700> one<00:10:17.850> has<00:10:17.970> the<00:10:18.000> time<00:10:18.240> the<00:10:18.390> first<00:10:18.570> form 00:10:18.860 --> 00:10:18.870 align:start position:0% but this one has the time the first form 00:10:18.870 --> 00:10:22.009 align:start position:0% but this one has the time the first form Australia<00:10:19.550> and<00:10:20.550> disabilities<00:10:21.420> you<00:10:21.540> will<00:10:21.720> send 00:10:22.009 --> 00:10:22.019 align:start position:0% Australia and disabilities you will send 00:10:22.019 --> 00:10:27.949 align:start position:0% Australia and disabilities you will send in<00:10:22.500> signatures<00:10:23.010> to<00:10:23.130> 1<00:10:23.310> 1<00:10:23.790> to<00:10:23.820> 0<00:10:25.760> okay<00:10:26.760> and<00:10:27.029> then 00:10:27.949 --> 00:10:27.959 align:start position:0% in signatures to 1 1 to 0 okay and then 00:10:27.959 --> 00:10:30.050 align:start position:0% in signatures to 1 1 to 0 okay and then we<00:10:28.110> can<00:10:28.290> aggregate<00:10:28.670> so<00:10:29.670> it's<00:10:29.790> like<00:10:29.910> negative 00:10:30.050 --> 00:10:30.060 align:start position:0% we can aggregate so it's like negative 00:10:30.060 --> 00:10:33.259 align:start position:0% we can aggregate so it's like negative and<00:10:30.510> it<00:10:30.779> means<00:10:30.990> that<00:10:31.260> at<00:10:31.500> the<00:10:31.890> next<00:10:32.190> level<00:10:32.399> when 00:10:33.259 --> 00:10:33.269 align:start position:0% and it means that at the next level when 00:10:33.269 --> 00:10:35.630 align:start position:0% and it means that at the next level when 0<00:10:33.630> and<00:10:33.870> 1<00:10:34.110> we<00:10:34.350> accelerate<00:10:35.130> immediate 00:10:35.630 --> 00:10:35.640 align:start position:0% 0 and 1 we accelerate immediate 00:10:35.640 --> 00:10:38.120 align:start position:0% 0 and 1 we accelerate immediate signature<00:10:36.149> is<00:10:36.420> what<00:10:36.690> will<00:10:36.930> the<00:10:37.529> aggregation 00:10:38.120 --> 00:10:38.130 align:start position:0% signature is what will the aggregation 00:10:38.130 --> 00:10:42.530 align:start position:0% signature is what will the aggregation is<00:10:38.279> for<00:10:39.060> me<00:10:39.180> succeeded<00:10:39.690> because<00:10:41.360> such<00:10:42.360> way 00:10:42.530 --> 00:10:42.540 align:start position:0% is for me succeeded because such way 00:10:42.540 --> 00:10:46.069 align:start position:0% is for me succeeded because such way lenders<00:10:42.899> know<00:10:43.250> by<00:10:44.250> diffusion<00:10:44.910> and<00:10:45.390> then<00:10:45.959> you 00:10:46.069 --> 00:10:46.079 align:start position:0% lenders know by diffusion and then you 00:10:46.079 --> 00:10:47.120 align:start position:0% lenders know by diffusion and then you go<00:10:46.230> through<00:10:46.410> an<00:10:46.500> experience 00:10:47.120 --> 00:10:47.130 align:start position:0% go through an experience 00:10:47.130 --> 00:10:51.290 align:start position:0% go through an experience and<00:10:47.880> so<00:10:48.149> on<00:10:48.269> and<00:10:48.420> so<00:10:48.570> on<00:10:48.600> so<00:10:49.410> easy<00:10:50.310> to<00:10:50.550> block<00:10:51.029> an 00:10:51.290 --> 00:10:51.300 align:start position:0% and so on and so on so easy to block an 00:10:51.300 --> 00:10:56.710 align:start position:0% and so on and so on so easy to block an event<00:10:51.660> which<00:10:52.260> is<00:10:52.410> good<00:10:52.589> for 00:10:56.710 --> 00:10:56.720 align:start position:0% 00:10:56.720 --> 00:10:59.380 align:start position:0% if<00:10:57.230> one<00:10:57.410> knot<00:10:57.560> is<00:10:57.680> now<00:10:57.860> secure<00:10:58.700> please<00:10:59.030> lament 00:10:59.380 --> 00:10:59.390 align:start position:0% if one knot is now secure please lament 00:10:59.390 --> 00:11:02.440 align:start position:0% if one knot is now secure please lament by<00:10:59.720> traditional<00:11:00.260> and<00:11:01.220> then<00:11:01.850> we<00:11:01.970> aggregate 00:11:02.440 --> 00:11:02.450 align:start position:0% by traditional and then we aggregate 00:11:02.450 --> 00:11:05.820 align:start position:0% by traditional and then we aggregate with<00:11:02.920> 1250<00:11:03.920> and<00:11:04.670> that's<00:11:04.910> it 00:11:05.820 --> 00:11:05.830 align:start position:0% with 1250 and that's it 00:11:05.830 --> 00:11:09.310 align:start position:0% with 1250 and that's it see<00:11:06.830> it's<00:11:07.010> and<00:11:07.190> if<00:11:07.420> not<00:11:08.420> loves<00:11:08.720> that<00:11:08.960> one<00:11:09.080> is 00:11:09.310 --> 00:11:09.320 align:start position:0% see it's and if not loves that one is 00:11:09.320 --> 00:11:14.880 align:start position:0% see it's and if not loves that one is for<00:11:09.530> something<00:11:10.630> nothing<00:11:11.630> will<00:11:11.900> happen 00:11:14.880 --> 00:11:14.890 align:start position:0% 00:11:14.890 --> 00:11:18.430 align:start position:0% because<00:11:15.890> still<00:11:16.310> a<00:11:16.910> little<00:11:17.390> bit<00:11:17.540> issue<00:11:17.720> when<00:11:18.410> I 00:11:18.430 --> 00:11:18.440 align:start position:0% because still a little bit issue when I 00:11:18.440 --> 00:11:20.890 align:start position:0% because still a little bit issue when I say<00:11:18.710> how<00:11:19.490> do<00:11:19.550> I<00:11:19.760> know<00:11:19.910> what<00:11:20.060> what<00:11:20.300> the<00:11:20.390> sound<00:11:20.750> we 00:11:20.890 --> 00:11:20.900 align:start position:0% say how do I know what what the sound we 00:11:20.900 --> 00:11:26.110 align:start position:0% say how do I know what what the sound we have<00:11:21.050> to<00:11:21.170> wait<00:11:21.320> for<00:11:21.530> now<00:11:24.490> by<00:11:25.490> definition<00:11:25.700> in 00:11:26.110 --> 00:11:26.120 align:start position:0% have to wait for now by definition in 00:11:26.120 --> 00:11:27.760 align:start position:0% have to wait for now by definition in the<00:11:26.210> disability<00:11:26.420> system<00:11:26.780> I<00:11:27.110> can<00:11:27.260> see<00:11:27.440> the<00:11:27.560> time 00:11:27.760 --> 00:11:27.770 align:start position:0% the disability system I can see the time 00:11:27.770 --> 00:11:29.830 align:start position:0% the disability system I can see the time will<00:11:28.220> receive<00:11:28.550> anything<00:11:28.850> or<00:11:29.240> what<00:11:29.420> does<00:11:29.690> not 00:11:29.830 --> 00:11:29.840 align:start position:0% will receive anything or what does not 00:11:29.840 --> 00:11:32.770 align:start position:0% will receive anything or what does not behind<00:11:30.200> us<00:11:30.410> I<00:11:30.620> hope<00:11:31.520> not<00:11:31.670> true<00:11:31.880> and<00:11:32.390> it's<00:11:32.600> what 00:11:32.770 --> 00:11:32.780 align:start position:0% behind us I hope not true and it's what 00:11:32.780 --> 00:11:34.630 align:start position:0% behind us I hope not true and it's what because<00:11:33.140> it's<00:11:33.320> vital<00:11:33.710> to<00:11:33.740> context<00:11:34.220> they<00:11:34.430> can 00:11:34.630 --> 00:11:34.640 align:start position:0% because it's vital to context they can 00:11:34.640 --> 00:11:37.150 align:start position:0% because it's vital to context they can pretend<00:11:34.940> to<00:11:35.000> be<00:11:35.090> very<00:11:36.050> develop<00:11:36.500> concern<00:11:36.950> and 00:11:37.150 --> 00:11:37.160 align:start position:0% pretend to be very develop concern and 00:11:37.160 --> 00:11:38.680 align:start position:0% pretend to be very develop concern and producing<00:11:37.520> a<00:11:37.640> show<00:11:37.670> of<00:11:38.150> confidence<00:11:38.330> in 00:11:38.680 --> 00:11:38.690 align:start position:0% producing a show of confidence in 00:11:38.690 --> 00:11:39.370 align:start position:0% producing a show of confidence in yourself 00:11:39.370 --> 00:11:39.380 align:start position:0% yourself 00:11:39.380 --> 00:11:44.260 align:start position:0% yourself whatever<00:11:40.310> okay<00:11:40.880> so<00:11:41.650> the<00:11:42.650> way<00:11:42.770> we<00:11:42.920> do<00:11:43.040> at<00:11:43.270> first 00:11:44.260 --> 00:11:44.270 align:start position:0% whatever okay so the way we do at first 00:11:44.270 --> 00:11:46.060 align:start position:0% whatever okay so the way we do at first with<00:11:44.450> visual<00:11:44.810> information<00:11:45.040> we're<00:11:46.040> not 00:11:46.060 --> 00:11:46.070 align:start position:0% with visual information we're not 00:11:46.070 --> 00:11:48.430 align:start position:0% with visual information we're not proving<00:11:46.640> someone<00:11:47.600> to<00:11:47.690> send<00:11:47.870> us<00:11:47.990> something<00:11:48.200> we 00:11:48.430 --> 00:11:48.440 align:start position:0% proving someone to send us something we 00:11:48.440 --> 00:11:50.110 align:start position:0% proving someone to send us something we just<00:11:48.620> serve<00:11:48.770> the<00:11:48.920> image<00:11:49.220> of<00:11:49.490> yourself 00:11:50.110 --> 00:11:50.120 align:start position:0% just serve the image of yourself 00:11:50.120 --> 00:11:53.680 align:start position:0% just serve the image of yourself I<00:11:50.240> get<00:11:50.570> it<00:11:52.070> and<00:11:52.340> sing<00:11:52.580> out<00:11:52.730> everything 00:11:53.680 --> 00:11:53.690 align:start position:0% I get it and sing out everything 00:11:53.690 --> 00:11:56.100 align:start position:0% I get it and sing out everything happened<00:11:53.960> in<00:11:54.080> Paris<00:11:54.350> so<00:11:54.590> we're<00:11:54.770> not<00:11:54.860> waiting 00:11:56.100 --> 00:11:56.110 align:start position:0% happened in Paris so we're not waiting 00:11:56.110 --> 00:11:59.590 align:start position:0% happened in Paris so we're not waiting for<00:11:57.110> a<00:11:57.350> nun<00:11:57.530> cellphone<00:11:58.100> that<00:11:58.580> one<00:11:58.820> of<00:11:59.300> an 00:11:59.590 --> 00:11:59.600 align:start position:0% for a nun cellphone that one of an 00:11:59.600 --> 00:12:01.270 align:start position:0% for a nun cellphone that one of an operating<00:11:59.930> from<00:12:00.170> a<00:12:00.230> signature<00:12:00.560> for<00:12:00.860> not<00:12:01.040> one 00:12:01.270 --> 00:12:01.280 align:start position:0% operating from a signature for not one 00:12:01.280 --> 00:12:04.480 align:start position:0% operating from a signature for not one to<00:12:01.910> stop<00:12:02.480> the<00:12:02.660> others<00:12:02.840> so<00:12:03.590> zero<00:12:03.980> at<00:12:04.340> the 00:12:04.480 --> 00:12:04.490 align:start position:0% to stop the others so zero at the 00:12:04.490 --> 00:12:06.250 align:start position:0% to stop the others so zero at the beginning<00:12:04.610> is<00:12:05.030> going<00:12:05.270> to<00:12:05.390> communicate<00:12:05.720> with 00:12:06.250 --> 00:12:06.260 align:start position:0% beginning is going to communicate with 00:12:06.260 --> 00:12:10.030 align:start position:0% beginning is going to communicate with not<00:12:06.410> one<00:12:06.620> but<00:12:06.830> as<00:12:07.310> well<00:12:07.520> even<00:12:07.820> a<00:12:08.860> 200-person 00:12:10.030 --> 00:12:10.040 align:start position:0% not one but as well even a 200-person 00:12:10.040 --> 00:12:12.340 align:start position:0% not one but as well even a 200-person response<00:12:10.400> it<00:12:11.240> isn't<00:12:11.510> a<00:12:11.660> machine<00:12:11.840> yourself 00:12:12.340 --> 00:12:12.350 align:start position:0% response it isn't a machine yourself 00:12:12.350 --> 00:12:14.530 align:start position:0% response it isn't a machine yourself from<00:12:12.530> one<00:12:12.710> and<00:12:13.070> in<00:12:13.640> this<00:12:13.730> case<00:12:13.970> in<00:12:14.090> the<00:12:14.360> right 00:12:14.530 --> 00:12:14.540 align:start position:0% from one and in this case in the right 00:12:14.540 --> 00:12:18.130 align:start position:0% from one and in this case in the right but<00:12:15.170> if<00:12:15.320> I<00:12:15.440> get<00:12:15.500> it<00:12:15.710> starts<00:12:16.100> so<00:12:16.960> 0<00:12:17.960> would 00:12:18.130 --> 00:12:18.140 align:start position:0% but if I get it starts so 0 would 00:12:18.140 --> 00:12:21.040 align:start position:0% but if I get it starts so 0 would subject<00:12:18.410> you<00:12:19.070> can<00:12:19.220> I<00:12:19.280> forget<00:12:19.640> my<00:12:19.820> signature<00:12:20.330> so 00:12:21.040 --> 00:12:21.050 align:start position:0% subject you can I forget my signature so 00:12:21.050 --> 00:12:23.650 align:start position:0% subject you can I forget my signature so at<00:12:21.320> this<00:12:21.440> point<00:12:21.650> maybe<00:12:21.920> two<00:12:22.580> will<00:12:22.850> add<00:12:23.090> zero<00:12:23.600> to 00:12:23.650 --> 00:12:23.660 align:start position:0% at this point maybe two will add zero to 00:12:23.660 --> 00:12:27.550 align:start position:0% at this point maybe two will add zero to three<00:12:24.220> and<00:12:25.220> if<00:12:25.640> we<00:12:26.540> look<00:12:26.660> at<00:12:26.780> good<00:12:26.960> of<00:12:27.140> deliver 00:12:27.550 --> 00:12:27.560 align:start position:0% three and if we look at good of deliver 00:12:27.560 --> 00:12:28.990 align:start position:0% three and if we look at good of deliver something<00:12:27.770> we<00:12:28.100> start<00:12:28.340> to<00:12:28.430> be<00:12:28.520> that<00:12:28.700> we<00:12:28.820> can 00:12:28.990 --> 00:12:29.000 align:start position:0% something we start to be that we can 00:12:29.000 --> 00:12:36.300 align:start position:0% something we start to be that we can then<00:12:29.180> develop<00:12:29.480> advanced 00:12:36.300 --> 00:12:36.310 align:start position:0% 00:12:36.310 --> 00:12:37.769 align:start position:0% so<00:12:36.939> Jen<00:12:37.149> will<00:12:37.300> come<00:12:37.480> to<00:12:37.569> find 00:12:37.769 --> 00:12:37.779 align:start position:0% so Jen will come to find 00:12:37.779 --> 00:12:40.319 align:start position:0% so Jen will come to find miscommunication<00:12:38.589> Oregon<00:12:39.009> place<00:12:39.310> and<00:12:40.120> power 00:12:40.319 --> 00:12:40.329 align:start position:0% miscommunication Oregon place and power 00:12:40.329 --> 00:12:42.269 align:start position:0% miscommunication Oregon place and power button<00:12:40.810> a<00:12:40.899> little<00:12:41.079> bit<00:12:41.259> so<00:12:41.410> it's<00:12:41.560> organized<00:12:41.980> to 00:12:42.269 --> 00:12:42.279 align:start position:0% button a little bit so it's organized to 00:12:42.279 --> 00:12:43.530 align:start position:0% button a little bit so it's organized to communicate<00:12:42.730> with<00:12:42.910> everybody 00:12:43.530 --> 00:12:43.540 align:start position:0% communicate with everybody 00:12:43.540 --> 00:12:46.619 align:start position:0% communicate with everybody we<00:12:43.749> got<00:12:43.899> rating<00:12:44.259> which<00:12:45.189> is<00:12:45.490> obviously<00:12:46.420> an 00:12:46.619 --> 00:12:46.629 align:start position:0% we got rating which is obviously an 00:12:46.629 --> 00:12:48.499 align:start position:0% we got rating which is obviously an issue<00:12:46.749> is<00:12:47.019> you<00:12:47.110> have<00:12:47.230> thousands<00:12:47.649> of<00:12:47.829> knots 00:12:48.499 --> 00:12:48.509 align:start position:0% issue is you have thousands of knots 00:12:48.509 --> 00:12:51.119 align:start position:0% issue is you have thousands of knots because<00:12:49.509> what<00:12:50.230> I'm<00:12:50.350> saying<00:12:50.379> is<00:12:50.680> our<00:12:50.860> best 00:12:51.119 --> 00:12:51.129 align:start position:0% because what I'm saying is our best 00:12:51.129 --> 00:12:55.379 align:start position:0% because what I'm saying is our best communicate<00:12:51.759> with<00:12:51.910> everybody<00:12:52.920> right<00:12:53.920> but<00:12:54.790> if 00:12:55.379 --> 00:12:55.389 align:start position:0% communicate with everybody right but if 00:12:55.389 --> 00:12:57.179 align:start position:0% communicate with everybody right but if I<00:12:55.509> don't<00:12:55.689> want<00:12:55.870> to<00:12:55.930> keep<00:12:56.110> a<00:12:56.259> network<00:12:56.589> a<00:12:56.740> other 00:12:57.179 --> 00:12:57.189 align:start position:0% I don't want to keep a network a other 00:12:57.189 --> 00:12:59.489 align:start position:0% I don't want to keep a network a other nice<00:12:57.339> conservator<00:12:57.910> at<00:12:58.389> the<00:12:58.779> white<00:12:58.930> box 00:12:59.489 --> 00:12:59.499 align:start position:0% nice conservator at the white box 00:12:59.499 --> 00:13:02.720 align:start position:0% nice conservator at the white box we<00:13:00.069> basically<00:13:00.819> a<00:13:01.300> dissemination<00:13:01.809> biologist 00:13:02.720 --> 00:13:02.730 align:start position:0% we basically a dissemination biologist 00:13:02.730 --> 00:13:05.340 align:start position:0% we basically a dissemination biologist concerning<00:13:03.730> seconds<00:13:04.149> and<00:13:04.480> then<00:13:04.959> we<00:13:05.050> charge<00:13:05.170> a 00:13:05.340 --> 00:13:05.350 align:start position:0% concerning seconds and then we charge a 00:13:05.350 --> 00:13:07.379 align:start position:0% concerning seconds and then we charge a secondary<00:13:05.829> contact<00:13:06.040> and<00:13:06.579> assertiveness<00:13:06.999> and 00:13:07.379 --> 00:13:07.389 align:start position:0% secondary contact and assertiveness and 00:13:07.389 --> 00:13:09.179 align:start position:0% secondary contact and assertiveness and we<00:13:07.990> progress<00:13:08.199> in<00:13:08.589> the<00:13:08.709> others 00:13:09.179 --> 00:13:09.189 align:start position:0% we progress in the others 00:13:09.189 --> 00:13:11.720 align:start position:0% we progress in the others so<00:13:09.670> for<00:13:09.879> this<00:13:09.999> calendar<00:13:10.300> contacts<00:13:10.809> per<00:13:11.110> unit 00:13:11.720 --> 00:13:11.730 align:start position:0% so for this calendar contacts per unit 00:13:11.730 --> 00:13:16.920 align:start position:0% so for this calendar contacts per unit installed<00:13:12.730> and<00:13:14.490> serviced<00:13:15.490> just<00:13:16.360> matter<00:13:16.629> to 00:13:16.920 --> 00:13:16.930 align:start position:0% installed and serviced just matter to 00:13:16.930 --> 00:13:24.499 align:start position:0% installed and serviced just matter to force<00:13:17.170> it<00:13:17.350> will<00:13:17.529> which<00:13:18.129> put<00:13:18.370> pressure<00:13:18.399> on<00:13:19.139> just 00:13:24.499 --> 00:13:24.509 align:start position:0% 00:13:24.509 --> 00:13:28.069 align:start position:0% so<00:13:25.509> is<00:13:25.779> that<00:13:25.990> has<00:13:26.410> a<00:13:26.439> suction<00:13:26.800> task<00:13:27.249> of 00:13:28.069 --> 00:13:28.079 align:start position:0% so is that has a suction task of 00:13:28.079 --> 00:13:34.889 align:start position:0% so is that has a suction task of horribles<00:13:29.790> here<00:13:31.139> yes<00:13:33.089> yes<00:13:34.089> we<00:13:34.300> knew<00:13:34.480> the 00:13:34.889 --> 00:13:34.899 align:start position:0% horribles here yes yes we knew the 00:13:34.899 --> 00:13:36.749 align:start position:0% horribles here yes yes we knew the difference<00:13:35.139> between<00:13:35.769> the<00:13:35.889> publicity<00:13:36.220> now 00:13:36.749 --> 00:13:36.759 align:start position:0% difference between the publicity now 00:13:36.759 --> 00:13:38.910 align:start position:0% difference between the publicity now this<00:13:36.970> one<00:13:37.120> is<00:13:37.300> miss<00:13:37.449> one<00:13:37.600> remote<00:13:37.930> management<00:13:38.379> I 00:13:38.910 --> 00:13:38.920 align:start position:0% this one is miss one remote management I 00:13:38.920 --> 00:13:40.949 align:start position:0% this one is miss one remote management I will<00:13:39.819> have<00:13:39.910> a<00:13:39.970> lot<00:13:40.120> of<00:13:40.149> slides<00:13:40.360> at<00:13:40.629> the<00:13:40.660> end<00:13:40.779> of 00:13:40.949 --> 00:13:40.959 align:start position:0% will have a lot of slides at the end of 00:13:40.959 --> 00:13:42.449 align:start position:0% will have a lot of slides at the end of the<00:13:41.050> fact<00:13:41.259> that<00:13:41.319> you<00:13:41.500> move<00:13:41.680> and<00:13:41.829> so<00:13:42.009> you<00:13:42.339> know 00:13:42.449 --> 00:13:42.459 align:start position:0% the fact that you move and so you know 00:13:42.459 --> 00:13:45.629 align:start position:0% the fact that you move and so you know you<00:13:42.730> know<00:13:42.910> this<00:13:43.209> is<00:13:43.569> high<00:13:43.750> to<00:13:43.809> us<00:13:44.139> so<00:13:45.129> you<00:13:45.189> know 00:13:45.629 --> 00:13:45.639 align:start position:0% you know this is high to us so you know 00:13:45.639 --> 00:13:46.759 align:start position:0% you know this is high to us so you know other<00:13:45.910> ways 00:13:46.759 --> 00:13:46.769 align:start position:0% other ways 00:13:46.769 --> 00:13:53.000 align:start position:0% other ways so<00:13:47.769> in<00:13:48.189> the<00:13:48.309> time<00:13:48.519> removalist<00:13:49.269> of<00:13:50.399> opportunity 00:13:53.000 --> 00:13:53.010 align:start position:0% so in the time removalist of opportunity 00:13:53.010 --> 00:13:59.600 align:start position:0% so in the time removalist of opportunity in<00:13:53.930> fact<00:13:54.930> as<00:13:55.459> an<00:13:56.459> indication<00:13:56.940> of<00:13:58.010> so<00:13:59.010> the<00:13:59.430> way 00:13:59.600 --> 00:13:59.610 align:start position:0% in fact as an indication of so the way 00:13:59.610 --> 00:14:03.800 align:start position:0% in fact as an indication of so the way the<00:14:00.209> world<00:14:00.690> is<00:14:01.130> at<00:14:02.130> the<00:14:02.370> beginning<00:14:02.810> when 00:14:03.800 --> 00:14:03.810 align:start position:0% the world is at the beginning when 00:14:03.810 --> 00:14:05.600 align:start position:0% the world is at the beginning when you're<00:14:03.959> a<00:14:04.230> member<00:14:04.380> of<00:14:04.560> a<00:14:04.740> committee<00:14:04.949> you<00:14:05.399> say 00:14:05.600 --> 00:14:05.610 align:start position:0% you're a member of a committee you say 00:14:05.610 --> 00:14:07.699 align:start position:0% you're a member of a committee you say oh<00:14:05.760> actually<00:14:06.029> as<00:14:06.449> an<00:14:06.600> aggregate<00:14:06.959> I<00:14:07.320> will<00:14:07.470> speak 00:14:07.699 --> 00:14:07.709 align:start position:0% oh actually as an aggregate I will speak 00:14:07.709 --> 00:14:11.050 align:start position:0% oh actually as an aggregate I will speak at<00:14:08.610> a<00:14:08.880> service<00:14:09.209> and<00:14:09.750> then<00:14:10.199> you're<00:14:10.410> not<00:14:10.529> doing 00:14:11.050 --> 00:14:11.060 align:start position:0% at a service and then you're not doing 00:14:11.060 --> 00:14:14.180 align:start position:0% at a service and then you're not doing the<00:14:12.060> sipping<00:14:12.449> connection<00:14:13.079> will<00:14:13.949> drain<00:14:14.160> the 00:14:14.180 --> 00:14:14.190 align:start position:0% the sipping connection will drain the 00:14:14.190 --> 00:14:17.030 align:start position:0% the sipping connection will drain the dark<00:14:14.519> TCP<00:14:15.120> connections<00:14:15.540> will<00:14:15.720> repeatedly<00:14:16.139> but 00:14:17.030 --> 00:14:17.040 align:start position:0% dark TCP connections will repeatedly but 00:14:17.040 --> 00:14:19.519 align:start position:0% dark TCP connections will repeatedly but a<00:14:17.660> really<00:14:18.660> nice<00:14:18.750> edge<00:14:18.959> of<00:14:19.139> a<00:14:19.199> quick<00:14:19.380> message 00:14:19.519 --> 00:14:19.529 align:start position:0% a really nice edge of a quick message 00:14:19.529 --> 00:14:24.259 align:start position:0% a really nice edge of a quick message but<00:14:19.920> really<00:14:20.130> which<00:14:20.250> white<00:14:20.459> 300<00:14:21.089> I<00:14:23.120> will<00:14:24.120> have<00:14:24.209> a 00:14:24.259 --> 00:14:24.269 align:start position:0% but really which white 300 I will have a 00:14:24.269 --> 00:14:25.850 align:start position:0% but really which white 300 I will have a lot<00:14:24.420> of<00:14:24.449> spice<00:14:24.750> in<00:14:24.899> this<00:14:24.990> but<00:14:25.170> you<00:14:25.410> understood 00:14:25.850 --> 00:14:25.860 align:start position:0% lot of spice in this but you understood 00:14:25.860 --> 00:14:29.689 align:start position:0% lot of spice in this but you understood partly<00:14:26.959> basically<00:14:27.959> you're<00:14:28.139> doing<00:14:28.519> if<00:14:29.519> I 00:14:29.689 --> 00:14:29.699 align:start position:0% partly basically you're doing if I 00:14:29.699 --> 00:14:32.139 align:start position:0% partly basically you're doing if I simplified<00:14:30.209> of<00:14:30.420> something<00:14:30.779> or<00:14:30.930> UDP<00:14:31.230> in<00:14:31.649> search 00:14:32.139 --> 00:14:32.149 align:start position:0% simplified of something or UDP in search 00:14:32.149 --> 00:14:35.060 align:start position:0% simplified of something or UDP in search so<00:14:33.149> you<00:14:33.209> know<00:14:33.810> that<00:14:34.110> you<00:14:34.230> to<00:14:34.350> be<00:14:34.470> address<00:14:34.829> of 00:14:35.060 --> 00:14:35.070 align:start position:0% so you know that you to be address of 00:14:35.070 --> 00:14:36.860 align:start position:0% so you know that you to be address of this<00:14:35.220> world<00:14:35.459> and<00:14:35.699> this<00:14:35.940> one<00:14:36.060> is<00:14:36.300> one<00:14:36.449> the 00:14:36.860 --> 00:14:36.870 align:start position:0% this world and this one is one the 00:14:36.870 --> 00:14:39.740 align:start position:0% this world and this one is one the probability<00:14:37.170> of<00:14:37.560> asset<00:14:37.829> unknown<00:14:38.329> to<00:14:39.329> hope<00:14:39.510> is 00:14:39.740 --> 00:14:39.750 align:start position:0% probability of asset unknown to hope is 00:14:39.750 --> 00:14:50.990 align:start position:0% probability of asset unknown to hope is sending<00:14:40.139> a<00:14:40.230> message<00:14:40.260> targeted<00:14:41.100> with<00:14:43.610> food 00:14:50.990 --> 00:14:51.000 align:start position:0% 00:14:51.000 --> 00:14:54.920 align:start position:0% I<00:14:51.029> will<00:14:52.370> so<00:14:53.370> different<00:14:53.759> let's<00:14:54.000> basically<00:14:54.839> we 00:14:54.920 --> 00:14:54.930 align:start position:0% I will so different let's basically we 00:14:54.930 --> 00:14:58.220 align:start position:0% I will so different let's basically we will<00:14:55.050> have<00:14:56.089> originated<00:14:57.089> at<00:14:57.509> each<00:14:57.750> step<00:14:57.959> for 00:14:58.220 --> 00:14:58.230 align:start position:0% will have originated at each step for 00:14:58.230 --> 00:15:00.079 align:start position:0% will have originated at each step for sending<00:14:58.500> you<00:14:58.560> know<00:14:58.680> gay<00:14:58.829> messages<00:14:59.310> now<00:14:59.759> we 00:15:00.079 --> 00:15:00.089 align:start position:0% sending you know gay messages now we 00:15:00.089 --> 00:15:05.569 align:start position:0% sending you know gay messages now we have<00:15:00.600> some<00:15:00.779> slides<00:15:02.120> so<00:15:03.120> actually<00:15:04.050> as<00:15:04.649> well<00:15:04.829> so 00:15:05.569 --> 00:15:05.579 align:start position:0% have some slides so actually as well so 00:15:05.579 --> 00:15:07.309 align:start position:0% have some slides so actually as well so who<00:15:05.790> parties<00:15:06.209> like<00:15:06.360> Alba<00:15:06.810> you<00:15:06.899> know<00:15:07.110> that 00:15:07.309 --> 00:15:07.319 align:start position:0% who parties like Alba you know that 00:15:07.319 --> 00:15:10.280 align:start position:0% who parties like Alba you know that you're<00:15:07.529> looking<00:15:07.800> all<00:15:08.160> right<00:15:08.930> all<00:15:09.930> the<00:15:10.079> notes 00:15:10.280 --> 00:15:10.290 align:start position:0% you're looking all right all the notes 00:15:10.290 --> 00:15:13.639 align:start position:0% you're looking all right all the notes but<00:15:10.769> it's<00:15:10.949> going<00:15:11.100> to<00:15:11.220> finish<00:15:12.230> some<00:15:13.230> mats<00:15:13.439> and 00:15:13.639 --> 00:15:13.649 align:start position:0% but it's going to finish some mats and 00:15:13.649 --> 00:15:19.340 align:start position:0% but it's going to finish some mats and that's<00:15:16.879> awesome<00:15:17.879> but<00:15:18.209> you<00:15:18.329> need<00:15:18.480> to<00:15:18.569> send<00:15:18.810> drug 00:15:19.340 --> 00:15:19.350 align:start position:0% that's awesome but you need to send drug 00:15:19.350 --> 00:15:25.090 align:start position:0% that's awesome but you need to send drug a<00:15:19.470> massage<00:15:20.360> too<00:15:21.360> which<00:15:23.360> is<00:15:24.360> just<00:15:24.569> follow<00:15:24.839> stuff 00:15:25.090 --> 00:15:25.100 align:start position:0% a massage too which is just follow stuff 00:15:25.100 --> 00:15:27.650 align:start position:0% a massage too which is just follow stuff for<00:15:26.100> mathematical<00:15:26.670> point<00:15:26.879> of<00:15:26.970> view<00:15:27.029> is<00:15:27.389> based 00:15:27.650 --> 00:15:27.660 align:start position:0% for mathematical point of view is based 00:15:27.660 --> 00:15:30.410 align:start position:0% for mathematical point of view is based on<00:15:27.959> consultation<00:15:28.889> ability<00:15:29.730> to<00:15:29.910> be<00:15:30.060> shown<00:15:30.269> at 00:15:30.410 --> 00:15:30.420 align:start position:0% on consultation ability to be shown at 00:15:30.420 --> 00:15:33.079 align:start position:0% on consultation ability to be shown at unit<00:15:30.689> either<00:15:30.899> a<00:15:31.319> set<00:15:31.889> of<00:15:32.040> nodes<00:15:32.310> at<00:15:32.579> Apogee 00:15:33.079 --> 00:15:33.089 align:start position:0% unit either a set of nodes at Apogee 00:15:33.089 --> 00:15:57.319 align:start position:0% unit either a set of nodes at Apogee the<00:15:33.389> question<00:15:33.839> is<00:15:53.509> what<00:15:54.509> is<00:15:55.399> the<00:15:56.399> point<00:15:56.579> is<00:15:56.819> we 00:15:57.319 --> 00:15:57.329 align:start position:0% the question is what is the point is we 00:15:57.329 --> 00:16:03.879 align:start position:0% the question is what is the point is we said<00:16:00.110> we<00:16:01.110> want<00:16:01.379> things<00:16:01.769> to<00:16:02.730> support<00:16:03.120> very 00:16:03.879 --> 00:16:03.889 align:start position:0% said we want things to support very 00:16:03.889 --> 00:16:06.259 align:start position:0% said we want things to support very different<00:16:04.889> angle<00:16:05.220> to<00:16:05.459> someone's<00:16:05.970> can<00:16:06.149> be 00:16:06.259 --> 00:16:06.269 align:start position:0% different angle to someone's can be 00:16:06.269 --> 00:16:08.660 align:start position:0% different angle to someone's can be useful<00:16:06.720> and<00:16:07.230> we<00:16:07.439> said<00:16:07.649> that<00:16:07.829> would<00:16:07.980> be<00:16:08.040> less<00:16:08.339> in 00:16:08.660 --> 00:16:08.670 align:start position:0% useful and we said that would be less in 00:16:08.670 --> 00:16:09.980 align:start position:0% useful and we said that would be less in each<00:16:08.850> of<00:16:09.029> their<00:16:09.149> application<00:16:09.569> was<00:16:09.600> very 00:16:09.980 --> 00:16:09.990 align:start position:0% each of their application was very 00:16:09.990 --> 00:16:13.069 align:start position:0% each of their application was very expensive<00:16:10.439> and<00:16:11.370> we<00:16:11.430> said<00:16:11.730> as<00:16:11.939> well<00:16:12.149> but<00:16:12.389> when<00:16:12.839> I 00:16:13.069 --> 00:16:13.079 align:start position:0% expensive and we said as well but when I 00:16:13.079 --> 00:16:16.100 align:start position:0% expensive and we said as well but when I get<00:16:13.410> you<00:16:13.559> need<00:16:13.680> to<00:16:13.800> check<00:16:14.069> that<00:16:15.019> it's<00:16:16.019> correct 00:16:16.100 --> 00:16:16.110 align:start position:0% get you need to check that it's correct 00:16:16.110 --> 00:16:18.319 align:start position:0% get you need to check that it's correct if<00:16:16.680> not<00:16:16.889> you're<00:16:17.040> just<00:16:17.069> going<00:16:17.370> to<00:16:17.399> get<00:16:17.699> a<00:16:17.970> mess 00:16:18.319 --> 00:16:18.329 align:start position:0% if not you're just going to get a mess 00:16:18.329 --> 00:16:21.079 align:start position:0% if not you're just going to get a mess so<00:16:19.079> because<00:16:20.009> of<00:16:20.160> this<00:16:20.309> I'm<00:16:20.610> not<00:16:20.819> who<00:16:21.059> people 00:16:21.079 --> 00:16:21.089 align:start position:0% so because of this I'm not who people 00:16:21.089 --> 00:16:24.650 align:start position:0% so because of this I'm not who people captured<00:16:22.079> the<00:16:22.559> no<00:16:22.680> verification 00:16:24.650 --> 00:16:24.660 align:start position:0% captured the no verification 00:16:24.660 --> 00:16:30.269 align:start position:0% captured the no verification and<00:16:25.660> the<00:16:26.050> net<00:16:27.929> site<00:16:28.929> signature<00:16:29.800> that<00:16:30.009> on<00:16:30.160> the 00:16:30.269 --> 00:16:30.279 align:start position:0% and the net site signature that on the 00:16:30.279 --> 00:16:32.669 align:start position:0% and the net site signature that on the day<00:16:30.429> of<00:16:30.459> testing<00:16:30.999> one<00:16:31.540> that's<00:16:31.959> um<00:16:32.110> I<00:16:32.230> bigots<00:16:32.559> in 00:16:32.669 --> 00:16:32.679 align:start position:0% day of testing one that's um I bigots in 00:16:32.679 --> 00:16:36.299 align:start position:0% day of testing one that's um I bigots in itself<00:16:32.980> a<00:16:33.189> little<00:16:33.550> bit<00:16:33.939> didn't<00:16:34.509> we<00:16:34.540> see<00:16:34.749> me<00:16:35.309> so 00:16:36.299 --> 00:16:36.309 align:start position:0% itself a little bit didn't we see me so 00:16:36.309 --> 00:16:37.769 align:start position:0% itself a little bit didn't we see me so because<00:16:36.550> of<00:16:36.670> interest<00:16:37.089> I<00:16:37.269> was<00:16:37.389> going<00:16:37.689> the 00:16:37.769 --> 00:16:37.779 align:start position:0% because of interest I was going the 00:16:37.779 --> 00:16:39.569 align:start position:0% because of interest I was going the technologies<00:16:38.379> how<00:16:38.529> much<00:16:38.769> time<00:16:39.009> keep<00:16:39.220> moving 00:16:39.569 --> 00:16:39.579 align:start position:0% technologies how much time keep moving 00:16:39.579 --> 00:16:41.910 align:start position:0% technologies how much time keep moving them<00:16:39.759> over<00:16:40.029> seen<00:16:40.929> each<00:16:41.019> other<00:16:41.259> but<00:16:41.619> they<00:16:41.769> are 00:16:41.910 --> 00:16:41.920 align:start position:0% them over seen each other but they are 00:16:41.920 --> 00:16:46.619 align:start position:0% them over seen each other but they are indeed<00:16:43.529> so<00:16:44.529> we've<00:16:44.679> got<00:16:44.829> a<00:16:44.860> scope<00:16:45.509> when<00:16:46.509> you 00:16:46.619 --> 00:16:46.629 align:start position:0% indeed so we've got a scope when you 00:16:46.629 --> 00:16:48.419 align:start position:0% indeed so we've got a scope when you have<00:16:46.749> a<00:16:46.779> scope<00:16:47.139> in<00:16:47.410> the<00:16:47.470> Byzantine<00:16:47.949> context 00:16:48.419 --> 00:16:48.429 align:start position:0% have a scope in the Byzantine context 00:16:48.429 --> 00:16:51.210 align:start position:0% have a scope in the Byzantine context you<00:16:49.239> can<00:16:49.389> imagine<00:16:49.929> to<00:16:50.049> know<00:16:50.230> them<00:16:50.499> and<00:16:50.739> also 00:16:51.210 --> 00:16:51.220 align:start position:0% you can imagine to know them and also 00:16:51.220 --> 00:16:53.999 align:start position:0% you can imagine to know them and also wanting<00:16:51.610> each<00:16:51.759> other<00:16:52.059> verify<00:16:52.480> these<00:16:53.009> actually 00:16:53.999 --> 00:16:54.009 align:start position:0% wanting each other verify these actually 00:16:54.009 --> 00:16:56.039 align:start position:0% wanting each other verify these actually these<00:16:54.129> neutrals<00:16:54.759> it's<00:16:55.059> invalid<00:16:55.420> so<00:16:55.839> you<00:16:55.929> will 00:16:56.039 --> 00:16:56.049 align:start position:0% these neutrals it's invalid so you will 00:16:56.049 --> 00:16:57.650 align:start position:0% these neutrals it's invalid so you will have<00:16:56.170> wasted<00:16:56.350> five<00:16:56.769> milliseconds<00:16:57.040> of 00:16:57.650 --> 00:16:57.660 align:start position:0% have wasted five milliseconds of 00:16:57.660 --> 00:17:03.869 align:start position:0% have wasted five milliseconds of communication<00:16:58.660> time<00:16:58.839> which<00:16:59.079> regulars<00:16:59.619> and<00:17:02.879> ID 00:17:03.869 --> 00:17:03.879 align:start position:0% communication time which regulars and ID 00:17:03.879 --> 00:17:08.269 align:start position:0% communication time which regulars and ID there<00:17:04.779> is<00:17:05.020> to<00:17:05.199> have<00:17:05.350> a<00:17:05.679> walking<00:17:06.360> of<00:17:07.360> the<00:17:07.779> notes 00:17:08.269 --> 00:17:08.279 align:start position:0% there is to have a walking of the notes 00:17:08.279 --> 00:17:10.829 align:start position:0% there is to have a walking of the notes before<00:17:09.279> almost<00:17:09.610> us<00:17:09.880> to<00:17:10.120> say<00:17:10.270> okay<00:17:10.539> at<00:17:10.720> this 00:17:10.829 --> 00:17:10.839 align:start position:0% before almost us to say okay at this 00:17:10.839 --> 00:17:12.419 align:start position:0% before almost us to say okay at this point<00:17:10.899> we<00:17:11.289> should<00:17:11.319> be<00:17:11.620> contacted<00:17:12.100> by<00:17:12.130> those 00:17:12.419 --> 00:17:12.429 align:start position:0% point we should be contacted by those 00:17:12.429 --> 00:17:16.889 align:start position:0% point we should be contacted by those notes<00:17:13.649> we've<00:17:14.649> got<00:17:14.829> a<00:17:14.860> window<00:17:15.279> that<00:17:15.760> six<00:17:16.089> Morris 00:17:16.889 --> 00:17:16.899 align:start position:0% notes we've got a window that six Morris 00:17:16.899 --> 00:17:18.659 align:start position:0% notes we've got a window that six Morris project<00:17:17.289> so<00:17:17.409> we're<00:17:17.559> looking<00:17:17.770> to<00:17:17.799> easily<00:17:18.309> into 00:17:18.659 --> 00:17:18.669 align:start position:0% project so we're looking to easily into 00:17:18.669 --> 00:17:27.110 align:start position:0% project so we're looking to easily into each<00:17:18.760> window<00:17:20.549> inside<00:17:21.549> this<00:17:25.529> window<00:17:26.529> size 00:17:27.110 --> 00:17:27.120 align:start position:0% each window inside this window size 00:17:27.120 --> 00:17:29.610 align:start position:0% each window inside this window size difficult<00:17:28.120> if<00:17:28.329> we<00:17:28.539> see<00:17:28.840> that<00:17:28.960> some<00:17:29.139> signature 00:17:29.610 --> 00:17:29.620 align:start position:0% difficult if we see that some signature 00:17:29.620 --> 00:17:31.769 align:start position:0% difficult if we see that some signature are<00:17:29.740> failing<00:17:30.010> we<00:17:30.399> say<00:17:30.610> home<00:17:30.820> someone<00:17:31.539> is 00:17:31.769 --> 00:17:31.779 align:start position:0% are failing we say home someone is 00:17:31.779 --> 00:17:36.840 align:start position:0% are failing we say home someone is likely<00:17:32.020> to<00:17:32.279> reverse<00:17:33.279> the<00:17:34.210> cycle<00:17:35.700> and<00:17:36.700> that's 00:17:36.840 --> 00:17:36.850 align:start position:0% likely to reverse the cycle and that's 00:17:36.850 --> 00:17:39.440 align:start position:0% likely to reverse the cycle and that's basically<00:17:37.389> the<00:17:37.510> main<00:17:37.659> mechanisms<00:17:38.559> for<00:17:38.740> under 00:17:39.440 --> 00:17:39.450 align:start position:0% basically the main mechanisms for under 00:17:39.450 --> 00:17:42.120 align:start position:0% basically the main mechanisms for under this<00:17:40.450> fact<00:17:40.899> that<00:17:40.990> reproductive<00:17:41.470> an<00:17:41.799> unsightly 00:17:42.120 --> 00:17:42.130 align:start position:0% this fact that reproductive an unsightly 00:17:42.130 --> 00:17:45.480 align:start position:0% this fact that reproductive an unsightly because<00:17:42.639> a<00:17:42.669> tree<00:17:43.000> based<00:17:43.289> organization<00:17:44.289> so<00:17:44.500> we 00:17:45.480 --> 00:17:45.490 align:start position:0% because a tree based organization so we 00:17:45.490 --> 00:17:49.649 align:start position:0% because a tree based organization so we have<00:17:46.980> a<00:17:47.980> musician<00:17:48.429> we<00:17:49.029> do<00:17:49.179> verify<00:17:49.600> this 00:17:49.649 --> 00:17:49.659 align:start position:0% have a musician we do verify this 00:17:49.659 --> 00:17:51.289 align:start position:0% have a musician we do verify this miniature 00:17:51.289 --> 00:17:51.299 align:start position:0% miniature 00:17:51.299 --> 00:17:56.810 align:start position:0% miniature channel<00:17:52.299> thickness<00:17:54.990> let's<00:17:55.990> go 00:17:56.810 --> 00:17:56.820 align:start position:0% channel thickness let's go 00:17:56.820 --> 00:18:09.560 align:start position:0% channel thickness let's go now<00:17:59.190> if<00:18:00.190> we<00:18:00.340> take<00:18:00.490> this<00:18:05.789> so<00:18:06.789> we<00:18:07.470> jump<00:18:08.470> in<00:18:08.679> Amazon 00:18:09.560 --> 00:18:09.570 align:start position:0% now if we take this so we jump in Amazon 00:18:09.570 --> 00:18:12.000 align:start position:0% now if we take this so we jump in Amazon so<00:18:10.570> some<00:18:10.779> of<00:18:10.809> them<00:18:11.049> you<00:18:11.350> can<00:18:11.529> see<00:18:11.710> that<00:18:11.740> it's 00:18:12.000 --> 00:18:12.010 align:start position:0% so some of them you can see that it's 00:18:12.010 --> 00:18:15.419 align:start position:0% so some of them you can see that it's quite<00:18:12.130> fast<00:18:13.200> to<00:18:14.200> the<00:18:14.500> bill<00:18:14.710> at<00:18:14.950> least<00:18:14.980> well 00:18:15.419 --> 00:18:15.429 align:start position:0% quite fast to the bill at least well 00:18:15.429 --> 00:18:17.700 align:start position:0% quite fast to the bill at least well maybe<00:18:15.639> seconds<00:18:16.059> but<00:18:16.779> if<00:18:16.960> you<00:18:17.049> have<00:18:17.169> to<00:18:17.320> go<00:18:17.440> for 00:18:17.700 --> 00:18:17.710 align:start position:0% maybe seconds but if you have to go for 00:18:17.710 --> 00:18:20.430 align:start position:0% maybe seconds but if you have to go for multi<00:18:18.370> tools<00:18:18.700> in<00:18:19.000> there<00:18:19.210> it's<00:18:19.929> about<00:18:20.260> an 00:18:20.430 --> 00:18:20.440 align:start position:0% multi tools in there it's about an 00:18:20.440 --> 00:18:23.760 align:start position:0% multi tools in there it's about an eighty<00:18:20.649> coincidence<00:18:22.260> and<00:18:23.260> so<00:18:23.500> we<00:18:23.620> do<00:18:23.740> this 00:18:23.760 --> 00:18:23.770 align:start position:0% eighty coincidence and so we do this 00:18:23.770 --> 00:18:28.590 align:start position:0% eighty coincidence and so we do this term<00:18:24.639> returns<00:18:25.000> we<00:18:25.899> used<00:18:26.139> the<00:18:27.100> small<00:18:27.250> notes<00:18:27.610> on 00:18:28.590 --> 00:18:28.600 align:start position:0% term returns we used the small notes on 00:18:28.600 --> 00:18:36.240 align:start position:0% term returns we used the small notes on Amazon<00:18:29.080> so<00:18:29.380> it's<00:18:32.610> and<00:18:33.610> we<00:18:33.850> could<00:18:34.260> we<00:18:35.260> wanted<00:18:36.010> to 00:18:36.240 --> 00:18:36.250 align:start position:0% Amazon so it's and we could we wanted to 00:18:36.250 --> 00:18:40.039 align:start position:0% Amazon so it's and we could we wanted to thousand<00:18:36.610> of<00:18:36.700> them<00:18:37.139> through<00:18:38.139> notes<00:18:38.350> on<00:18:39.190> each 00:18:40.039 --> 00:18:40.049 align:start position:0% thousand of them through notes on each 00:18:40.049 --> 00:18:42.720 align:start position:0% thousand of them through notes on each three<00:18:41.049> hundred<00:18:41.470> girls<00:18:41.740> engaged<00:18:42.010> Amazon 00:18:42.720 --> 00:18:42.730 align:start position:0% three hundred girls engaged Amazon 00:18:42.730 --> 00:18:44.879 align:start position:0% three hundred girls engaged Amazon because<00:18:43.240> we<00:18:43.570> visited<00:18:44.020> to<00:18:44.139> process<00:18:44.500> on<00:18:44.830> a 00:18:44.879 --> 00:18:44.889 align:start position:0% because we visited to process on a 00:18:44.889 --> 00:18:47.399 align:start position:0% because we visited to process on a misapplication<00:18:45.250> of<00:18:45.639> so<00:18:46.570> obviously<00:18:47.139> when<00:18:47.320> you 00:18:47.399 --> 00:18:47.409 align:start position:0% misapplication of so obviously when you 00:18:47.409 --> 00:18:50.070 align:start position:0% misapplication of so obviously when you do<00:18:47.529> matter<00:18:47.710> fighting<00:18:48.190> overseas<00:18:48.630> because<00:18:49.630> you 00:18:50.070 --> 00:18:50.080 align:start position:0% do matter fighting overseas because you 00:18:50.080 --> 00:18:51.570 align:start position:0% do matter fighting overseas because you were<00:18:50.200> single<00:18:50.500> top<00:18:50.679> of<00:18:50.860> sharp<00:18:51.159> and<00:18:51.250> when<00:18:51.460> they 00:18:51.570 --> 00:18:51.580 align:start position:0% were single top of sharp and when they 00:18:51.580 --> 00:18:54.120 align:start position:0% were single top of sharp and when they define<00:18:51.880> use<00:18:52.090> in<00:18:52.270> each<00:18:52.360> answer<00:18:52.830> what<00:18:53.830> is<00:18:53.860> the 00:18:54.120 --> 00:18:54.130 align:start position:0% define use in each answer what is the 00:18:54.130 --> 00:18:57.000 align:start position:0% define use in each answer what is the final<00:18:54.429> yoga<00:18:54.820> one<00:18:54.970> is<00:18:55.090> waiting<00:18:55.240> for<00:18:55.539> us<00:18:55.809> so<00:18:56.529> we 00:18:57.000 --> 00:18:57.010 align:start position:0% final yoga one is waiting for us so we 00:18:57.010 --> 00:19:00.539 align:start position:0% final yoga one is waiting for us so we consider<00:18:57.760> matted<00:18:58.059> sumo<00:18:58.360> critical<00:18:59.549> context 00:19:00.539 --> 00:19:00.549 align:start position:0% consider matted sumo critical context 00:19:00.549 --> 00:19:03.510 align:start position:0% consider matted sumo critical context and<00:19:00.760> only<00:19:01.149> one<00:19:01.710> whatever<00:19:02.710> being<00:19:03.010> magical 00:19:03.510 --> 00:19:03.520 align:start position:0% and only one whatever being magical 00:19:03.520 --> 00:19:07.250 align:start position:0% and only one whatever being magical Patel<00:19:03.880> using<00:19:04.360> too 00:19:07.250 --> 00:19:07.260 align:start position:0% 00:19:07.260 --> 00:19:11.720 align:start position:0% and<00:19:07.980> on<00:19:08.100> this<00:19:08.250> we<00:19:09.240> compare<00:19:09.630> with<00:19:10.460> okay<00:19:11.460> so<00:19:11.490> I 00:19:11.720 --> 00:19:11.730 align:start position:0% and on this we compare with okay so I 00:19:11.730 --> 00:19:13.820 align:start position:0% and on this we compare with okay so I will<00:19:11.850> just<00:19:12.000> send<00:19:12.210> the<00:19:12.330> signature<00:19:12.809> element 00:19:13.820 --> 00:19:13.830 align:start position:0% will just send the signature element 00:19:13.830 --> 00:19:16.970 align:start position:0% will just send the signature element I<00:19:14.120> mean<00:19:15.120> basically<00:19:15.750> what<00:19:16.020> was<00:19:16.200> expected<00:19:16.470> is<00:19:16.799> a 00:19:16.970 --> 00:19:16.980 align:start position:0% I mean basically what was expected is a 00:19:16.980 --> 00:19:21.710 align:start position:0% I mean basically what was expected is a lot<00:19:17.160> of<00:19:17.309> data<00:19:19.340> a<00:19:20.340> lot<00:19:20.880> of<00:19:20.940> time<00:19:21.240> because<00:19:21.450> it 00:19:21.710 --> 00:19:21.720 align:start position:0% lot of data a lot of time because it 00:19:21.720 --> 00:19:25.870 align:start position:0% lot of data a lot of time because it started<00:19:22.020> mr.<00:19:22.410> Dickinson<00:19:22.980> compared<00:19:23.970> to<00:19:24.240> under 00:19:25.870 --> 00:19:25.880 align:start position:0% started mr. Dickinson compared to under 00:19:25.880 --> 00:19:33.110 align:start position:0% started mr. Dickinson compared to under which<00:19:26.880> which<00:19:27.090> is<00:19:28.400> Father<00:19:29.400> Knows<00:19:31.850> night<00:19:32.850> night 00:19:33.110 --> 00:19:33.120 align:start position:0% which which is Father Knows night night 00:19:33.120 --> 00:19:41.120 align:start position:0% which which is Father Knows night night wasn't<00:19:33.450> a<00:19:37.160> cell<00:19:38.160> phone<00:19:38.460> as<00:19:39.390> well<00:19:39.600> I<00:19:39.929> also<00:19:40.770> did 00:19:41.120 --> 00:19:41.130 align:start position:0% wasn't a cell phone as well I also did 00:19:41.130 --> 00:19:42.020 align:start position:0% wasn't a cell phone as well I also did not<00:19:41.309> answer 00:19:42.020 --> 00:19:42.030 align:start position:0% not answer 00:19:42.030 --> 00:19:45.080 align:start position:0% not answer just<00:19:42.870> you<00:19:43.169> know<00:19:43.260> maximum<00:19:43.500> detection<00:19:43.880> for<00:19:44.880> well 00:19:45.080 --> 00:19:45.090 align:start position:0% just you know maximum detection for well 00:19:45.090 --> 00:19:45.880 align:start position:0% just you know maximum detection for well buddy 00:19:45.880 --> 00:19:45.890 align:start position:0% buddy 00:19:45.890 --> 00:19:47.390 align:start position:0% buddy seven<00:19:46.890> minutes 00:19:47.390 --> 00:19:47.400 align:start position:0% seven minutes 00:19:47.400 --> 00:19:55.960 align:start position:0% seven minutes [Music] 00:19:55.960 --> 00:19:55.970 align:start position:0% 00:19:55.970 --> 00:19:58.690 align:start position:0% and<00:19:56.570> we<00:19:56.960> try<00:19:57.230> them<00:19:57.650> as<00:19:57.770> long<00:19:57.920> if<00:19:58.190> some<00:19:58.490> notes 00:19:58.690 --> 00:19:58.700 align:start position:0% and we try them as long if some notes 00:19:58.700 --> 00:20:01.720 align:start position:0% and we try them as long if some notes are<00:19:58.910> not<00:19:59.060> responding<00:19:59.570> and<00:20:00.410> so<00:20:00.800> it<00:20:00.980> compared 00:20:01.720 --> 00:20:01.730 align:start position:0% are not responding and so it compared 00:20:01.730 --> 00:20:04.360 align:start position:0% are not responding and so it compared the<00:20:01.850> time<00:20:02.230> to<00:20:03.230> which<00:20:03.410> agreements 00:20:04.360 --> 00:20:04.370 align:start position:0% the time to which agreements 00:20:04.370 --> 00:20:06.550 align:start position:0% the time to which agreements depending<00:20:04.970> on<00:20:05.090> our<00:20:05.300> MIDI<00:20:05.540> notes<00:20:05.840> are 00:20:06.550 --> 00:20:06.560 align:start position:0% depending on our MIDI notes are 00:20:06.560 --> 00:20:09.450 align:start position:0% depending on our MIDI notes are available<00:20:06.740> so<00:20:07.280> if<00:20:07.430> you<00:20:07.520> try<00:20:07.760> to<00:20:08.090> which 00:20:09.450 --> 00:20:09.460 align:start position:0% available so if you try to which 00:20:09.460 --> 00:20:10.600 align:start position:0% available so if you try to which fifty-fifty 00:20:10.600 --> 00:20:10.610 align:start position:0% fifty-fifty 00:20:10.610 --> 00:20:12.490 align:start position:0% fifty-fifty what<00:20:10.730> was<00:20:10.910> the<00:20:11.030> pressure<00:20:11.270> on<00:20:11.420> quite<00:20:11.930> open<00:20:12.380> note 00:20:12.490 --> 00:20:12.500 align:start position:0% what was the pressure on quite open note 00:20:12.500 --> 00:20:15.640 align:start position:0% what was the pressure on quite open note are<00:20:12.650> very<00:20:12.860> obviously<00:20:13.370> my<00:20:13.670> plastic<00:20:14.120> all<00:20:15.080> six<00:20:15.380> on 00:20:15.640 --> 00:20:15.650 align:start position:0% are very obviously my plastic all six on 00:20:15.650 --> 00:20:18.220 align:start position:0% are very obviously my plastic all six on one<00:20:15.830> milliseconds<00:20:16.810> it's<00:20:17.810> getting<00:20:18.080> a<00:20:18.140> little 00:20:18.220 --> 00:20:18.230 align:start position:0% one milliseconds it's getting a little 00:20:18.230 --> 00:20:20.890 align:start position:0% one milliseconds it's getting a little explorers<00:20:19.150> and<00:20:20.150> missing<00:20:20.420> some<00:20:20.600> not<00:20:20.750> be 00:20:20.890 --> 00:20:20.900 align:start position:0% explorers and missing some not be 00:20:20.900 --> 00:20:22.800 align:start position:0% explorers and missing some not be visited<00:20:21.470> this<00:20:21.590> much<00:20:21.800> more<00:20:22.040> polka<00:20:22.340> dots 00:20:22.800 --> 00:20:22.810 align:start position:0% visited this much more polka dots 00:20:22.810 --> 00:20:30.190 align:start position:0% visited this much more polka dots oneself<00:20:23.870> I<00:20:23.990> know<00:20:24.170> along<00:20:25.150> some<00:20:26.150> ways<00:20:29.020> so<00:20:30.020> we 00:20:30.190 --> 00:20:30.200 align:start position:0% oneself I know along some ways so we 00:20:30.200 --> 00:20:35.470 align:start position:0% oneself I know along some ways so we tried<00:20:30.500> uncie<00:20:31.070> relations<00:20:32.890> more<00:20:34.210> things<00:20:35.210> like 00:20:35.470 --> 00:20:35.480 align:start position:0% tried uncie relations more things like 00:20:35.480 --> 00:20:38.890 align:start position:0% tried uncie relations more things like attacks<00:20:36.110> so<00:20:36.980> for<00:20:37.190> example<00:20:37.550> this<00:20:37.700> one<00:20:37.940> is<00:20:38.300> the 00:20:38.890 --> 00:20:38.900 align:start position:0% attacks so for example this one is the 00:20:38.900 --> 00:20:43.590 align:start position:0% attacks so for example this one is the case<00:20:39.140> of<00:20:39.440> this<00:20:40.190> I<00:20:40.550> can<00:20:40.850> see<00:20:41.000> not<00:20:41.150> sending<00:20:41.720> you 00:20:43.590 --> 00:20:43.600 align:start position:0% case of this I can see not sending you 00:20:43.600 --> 00:20:46.780 align:start position:0% case of this I can see not sending you try<00:20:44.600> to<00:20:44.660> argue<00:20:45.560> project<00:20:46.100> with<00:20:46.370> this<00:20:46.490> in<00:20:46.700> a 00:20:46.780 --> 00:20:46.790 align:start position:0% try to argue project with this in a 00:20:46.790 --> 00:20:49.480 align:start position:0% try to argue project with this in a chair<00:20:47.030> with<00:20:47.210> 90%<00:20:48.110> open<00:20:48.650> nose<00:20:48.800> begins<00:20:49.040> by 00:20:49.480 --> 00:20:49.490 align:start position:0% chair with 90% open nose begins by 00:20:49.490 --> 00:20:51.850 align:start position:0% chair with 90% open nose begins by hunting<00:20:49.880> to<00:20:50.300> find<00:20:50.330> out<00:20:50.690> it's<00:20:51.350> a<00:20:51.440> little<00:20:51.560> bit 00:20:51.850 --> 00:20:51.860 align:start position:0% hunting to find out it's a little bit 00:20:51.860 --> 00:20:53.950 align:start position:0% hunting to find out it's a little bit scary<00:20:52.130> so<00:20:52.640> it's<00:20:52.790> still<00:20:53.000> about<00:20:53.180> 10<00:20:53.420> seconds<00:20:53.810> in 00:20:53.950 --> 00:20:53.960 align:start position:0% scary so it's still about 10 seconds in 00:20:53.960 --> 00:20:58.090 align:start position:0% scary so it's still about 10 seconds in this<00:20:54.110> context<00:20:54.470> which<00:20:55.400> is<00:20:55.430> visually<00:20:56.830> of<00:20:57.830> course 00:20:58.090 --> 00:20:58.100 align:start position:0% this context which is visually of course 00:20:58.100 --> 00:20:59.800 align:start position:0% this context which is visually of course in<00:20:58.220> this<00:20:58.310> context<00:20:58.670> you<00:20:58.730> just<00:20:58.910> open<00:20:59.240> 10% 00:20:59.800 --> 00:20:59.810 align:start position:0% in this context you just open 10% 00:20:59.810 --> 00:21:07.000 align:start position:0% in this context you just open 10% questions<00:21:02.290> so<00:21:03.290> let's<00:21:05.050> now<00:21:06.050> the<00:21:06.560> point<00:21:06.920> that 00:21:07.000 --> 00:21:07.010 align:start position:0% questions so let's now the point that 00:21:07.010 --> 00:21:08.830 align:start position:0% questions so let's now the point that you<00:21:07.130> are<00:21:07.220> mentioning<00:21:07.370> the<00:21:08.060> fact<00:21:08.270> that<00:21:08.450> since 00:21:08.830 --> 00:21:08.840 align:start position:0% you are mentioning the fact that since 00:21:08.840 --> 00:21:10.760 align:start position:0% you are mentioning the fact that since the<00:21:08.990> dye<00:21:09.140> penetrant 00:21:10.760 --> 00:21:10.770 align:start position:0% the dye penetrant 00:21:10.770 --> 00:21:14.790 align:start position:0% the dye penetrant interesting<00:21:11.770> part<00:21:13.080> which<00:21:14.080> means<00:21:14.350> that<00:21:14.620> the 00:21:14.790 --> 00:21:14.800 align:start position:0% interesting part which means that the 00:21:14.800 --> 00:21:18.140 align:start position:0% interesting part which means that the other<00:21:14.950> hypothesis<00:21:15.730> or<00:21:16.030> introducing<00:21:16.810> Network 00:21:18.140 --> 00:21:18.150 align:start position:0% other hypothesis or introducing Network 00:21:18.150 --> 00:21:24.660 align:start position:0% other hypothesis or introducing Network you<00:21:20.190> actually<00:21:21.270> can<00:21:22.270> get<00:21:22.510> access<00:21:22.810> to<00:21:22.990> them<00:21:23.670> well 00:21:24.660 --> 00:21:24.670 align:start position:0% you actually can get access to them well 00:21:24.670 --> 00:21:26.130 align:start position:0% you actually can get access to them well it's<00:21:24.880> a<00:21:24.940> little-bitty<00:21:25.180> that<00:21:25.540> we<00:21:25.630> can<00:21:25.780> pretend 00:21:26.130 --> 00:21:26.140 align:start position:0% it's a little-bitty that we can pretend 00:21:26.140 --> 00:21:28.230 align:start position:0% it's a little-bitty that we can pretend that<00:21:26.350> you're<00:21:27.340> cooler<00:21:27.700> than<00:21:27.820> a<00:21:28.030> chocolate 00:21:28.230 --> 00:21:28.240 align:start position:0% that you're cooler than a chocolate 00:21:28.240 --> 00:21:30.510 align:start position:0% that you're cooler than a chocolate ignore<00:21:28.870> that<00:21:29.080> you<00:21:29.230> actually<00:21:29.530> participate<00:21:29.710> in 00:21:30.510 --> 00:21:30.520 align:start position:0% ignore that you actually participate in 00:21:30.520 --> 00:21:32.490 align:start position:0% ignore that you actually participate in certain<00:21:30.760> so<00:21:31.000> like<00:21:31.180> it's<00:21:31.600> quite<00:21:31.810> easy<00:21:31.960> to<00:21:32.110> find 00:21:32.490 --> 00:21:32.500 align:start position:0% certain so like it's quite easy to find 00:21:32.500 --> 00:21:35.190 align:start position:0% certain so like it's quite easy to find user<00:21:32.980> actually<00:21:33.640> only<00:21:33.910> disappear<00:21:34.360> network<00:21:34.660> but 00:21:35.190 --> 00:21:35.200 align:start position:0% user actually only disappear network but 00:21:35.200 --> 00:21:37.050 align:start position:0% user actually only disappear network but it's<00:21:35.410> a<00:21:35.500> little<00:21:35.620> bit<00:21:35.860> even<00:21:36.160> while<00:21:36.820> they<00:21:37.030> are 00:21:37.050 --> 00:21:37.060 align:start position:0% it's a little bit even while they are 00:21:37.060 --> 00:21:40.530 align:start position:0% it's a little bit even while they are it's<00:21:37.330> not<00:21:37.510> even<00:21:37.720> authority<00:21:38.230> it<00:21:38.740> started<00:21:39.670> so<00:21:40.270> a 00:21:40.530 --> 00:21:40.540 align:start position:0% it's not even authority it started so a 00:21:40.540 --> 00:21:46.280 align:start position:0% it's not even authority it started so a lot<00:21:41.200> of<00:21:41.230> points<00:21:41.680> on<00:21:41.740> this<00:21:42.180> and<00:21:43.180> five<00:21:43.450> of<00:21:43.600> us 00:21:46.280 --> 00:21:46.290 align:start position:0% 00:21:46.290 --> 00:21:49.980 align:start position:0% there's<00:21:47.290> a<00:21:47.410> key<00:21:47.980> part<00:21:48.280> which<00:21:48.990> literally 00:21:49.980 --> 00:21:49.990 align:start position:0% there's a key part which literally 00:21:49.990 --> 00:21:51.720 align:start position:0% there's a key part which literally investing<00:21:50.620> and<00:21:50.800> then<00:21:50.950> that<00:21:51.130> the<00:21:51.430> fact<00:21:51.670> that 00:21:51.720 --> 00:21:51.730 align:start position:0% investing and then that the fact that 00:21:51.730 --> 00:21:53.190 align:start position:0% investing and then that the fact that you're<00:21:51.910> pushing<00:21:52.090> the<00:21:52.270> information<00:21:52.840> and<00:21:53.080> we 00:21:53.190 --> 00:21:53.200 align:start position:0% you're pushing the information and we 00:21:53.200 --> 00:21:53.930 align:start position:0% you're pushing the information and we don't<00:21:53.350> request 00:21:53.930 --> 00:21:53.940 align:start position:0% don't request 00:21:53.940 --> 00:21:59.760 align:start position:0% don't request okay<00:21:54.940> so<00:21:55.740> you<00:21:56.740> have<00:21:57.070> to<00:21:57.190> also<00:21:57.930> participate<00:21:58.930> or 00:21:59.760 --> 00:21:59.770 align:start position:0% okay so you have to also participate or 00:21:59.770 --> 00:22:02.940 align:start position:0% okay so you have to also participate or something<00:22:00.070> just<00:22:00.250> pushing<00:22:00.730> things<00:22:01.950> which 00:22:02.940 --> 00:22:02.950 align:start position:0% something just pushing things which 00:22:02.950 --> 00:22:06.990 align:start position:0% something just pushing things which means<00:22:03.160> that<00:22:04.500> if<00:22:05.500> we<00:22:05.680> manage<00:22:06.010> to<00:22:06.040> have<00:22:06.250> a<00:22:06.610> single 00:22:06.990 --> 00:22:07.000 align:start position:0% means that if we manage to have a single 00:22:07.000 --> 00:22:10.950 align:start position:0% means that if we manage to have a single packet<00:22:07.330> people<00:22:07.630> sounds<00:22:07.870> will<00:22:08.680> happen<00:22:09.840> so<00:22:10.840> we 00:22:10.950 --> 00:22:10.960 align:start position:0% packet people sounds will happen so we 00:22:10.960 --> 00:22:16.710 align:start position:0% packet people sounds will happen so we think<00:22:11.140> that<00:22:11.290> because<00:22:11.560> of<00:22:11.770> this<00:22:15.300> is<00:22:16.300> super 00:22:16.710 --> 00:22:16.720 align:start position:0% think that because of this is super 00:22:16.720 --> 00:22:20.700 align:start position:0% think that because of this is super super<00:22:16.870> theory<00:22:17.410> but<00:22:18.540> it<00:22:19.540> requires<00:22:19.930> some<00:22:20.110> some 00:22:20.700 --> 00:22:20.710 align:start position:0% super theory but it requires some some 00:22:20.710 --> 00:22:23.960 align:start position:0% super theory but it requires some some other<00:22:20.950> person 00:22:23.960 --> 00:22:23.970 align:start position:0% 00:22:23.970 --> 00:22:27.440 align:start position:0% the<00:22:24.480> question<00:22:24.810> of<00:22:24.930> anonymity<00:22:26.180> we<00:22:27.180> know<00:22:27.330> we 00:22:27.440 --> 00:22:27.450 align:start position:0% the question of anonymity we know we 00:22:27.450 --> 00:22:29.060 align:start position:0% the question of anonymity we know we want<00:22:27.540> to<00:22:27.720> be<00:22:27.810> told<00:22:27.990> you<00:22:28.290> know<00:22:28.410> the<00:22:28.530> IP<00:22:28.680> address 00:22:29.060 --> 00:22:29.070 align:start position:0% want to be told you know the IP address 00:22:29.070 --> 00:22:30.740 align:start position:0% want to be told you know the IP address and<00:22:29.340> we<00:22:29.400> know<00:22:29.520> that<00:22:29.700> words<00:22:30.000> because<00:22:30.570> they're 00:22:30.740 --> 00:22:30.750 align:start position:0% and we know that words because they're 00:22:30.750 --> 00:22:32.450 align:start position:0% and we know that words because they're stickers<00:22:31.020> so<00:22:31.440> we<00:22:31.560> can<00:22:31.800> be<00:22:31.920> really<00:22:32.160> high<00:22:32.400> - 00:22:32.450 --> 00:22:32.460 align:start position:0% stickers so we can be really high - 00:22:32.460 --> 00:22:35.090 align:start position:0% stickers so we can be really high - unless<00:22:32.760> forints<00:22:33.630> that's<00:22:34.290> that<00:22:34.470> expensive 00:22:35.090 --> 00:22:35.100 align:start position:0% unless forints that's that expensive 00:22:35.100 --> 00:22:38.150 align:start position:0% unless forints that's that expensive that<00:22:36.110> it's<00:22:37.110> much<00:22:37.260> about<00:22:37.470> the<00:22:37.650> tone<00:22:37.830> phone<00:22:38.040> yet 00:22:38.150 --> 00:22:38.160 align:start position:0% that it's much about the tone phone yet 00:22:38.160 --> 00:22:39.920 align:start position:0% that it's much about the tone phone yet but<00:22:38.370> even<00:22:38.670> with<00:22:38.850> this<00:22:38.970> network<00:22:39.390> it<00:22:39.900> can 00:22:39.920 --> 00:22:39.930 align:start position:0% but even with this network it can 00:22:39.930 --> 00:22:41.600 align:start position:0% but even with this network it can actually<00:22:40.290> guess<00:22:40.680> who<00:22:41.010> is<00:22:41.160> who 00:22:41.600 --> 00:22:41.610 align:start position:0% actually guess who is who 00:22:41.610 --> 00:22:43.970 align:start position:0% actually guess who is who because<00:22:42.120> and<00:22:42.990> in<00:22:43.110> the<00:22:43.230> house<00:22:43.410> we<00:22:43.650> move<00:22:43.830> from 00:22:43.970 --> 00:22:43.980 align:start position:0% because and in the house we move from 00:22:43.980 --> 00:22:45.860 align:start position:0% because and in the house we move from one<00:22:44.070> period<00:22:44.340> to<00:22:44.610> another<00:22:44.730> so<00:22:45.450> you<00:22:45.480> just<00:22:45.720> have 00:22:45.860 --> 00:22:45.870 align:start position:0% one period to another so you just have 00:22:45.870 --> 00:22:48.260 align:start position:0% one period to another so you just have to<00:22:45.900> follow<00:22:46.220> which<00:22:47.220> i<00:22:47.520> paralyzed<00:22:47.940> having 00:22:48.260 --> 00:22:48.270 align:start position:0% to follow which i paralyzed having 00:22:48.270 --> 00:22:52.040 align:start position:0% to follow which i paralyzed having infinity<00:22:48.960> look<00:22:49.680> at<00:22:49.950> what<00:22:50.550> our<00:22:51.050> wallets 00:22:52.040 --> 00:22:52.050 align:start position:0% infinity look at what our wallets 00:22:52.050 --> 00:22:54.140 align:start position:0% infinity look at what our wallets because<00:22:52.410> represent<00:22:53.070> to<00:22:53.130> be<00:22:53.250> considered<00:22:53.760> a<00:22:53.910> now 00:22:54.140 --> 00:22:54.150 align:start position:0% because represent to be considered a now 00:22:54.150 --> 00:22:56.660 align:start position:0% because represent to be considered a now after<00:22:54.630> one<00:22:55.140> or<00:22:55.170> two<00:22:55.470> will<00:22:56.040> be<00:22:56.070> quite<00:22:56.340> travel 00:22:56.660 --> 00:22:56.670 align:start position:0% after one or two will be quite travel 00:22:56.670 --> 00:22:59.570 align:start position:0% after one or two will be quite travel and<00:22:57.000> welcome<00:22:57.450> and<00:22:57.600> yes<00:22:57.810> right<00:22:58.020> so<00:22:58.370> its<00:22:59.370> own 00:22:59.570 --> 00:22:59.580 align:start position:0% and welcome and yes right so its own 00:22:59.580 --> 00:23:02.930 align:start position:0% and welcome and yes right so its own version<00:22:59.970> but<00:23:00.420> it's<00:23:00.630> not<00:23:00.840> too<00:23:01.530> specific<00:23:01.800> and<00:23:02.760> we 00:23:02.930 --> 00:23:02.940 align:start position:0% version but it's not too specific and we 00:23:02.940 --> 00:23:07.310 align:start position:0% version but it's not too specific and we can<00:23:03.120> actually<00:23:03.330> I<00:23:03.830> will<00:23:04.830> mr.<00:23:05.670> proposal<00:23:06.270> to<00:23:06.600> a 00:23:07.310 --> 00:23:07.320 align:start position:0% can actually I will mr. proposal to a 00:23:07.320 --> 00:23:10.610 align:start position:0% can actually I will mr. proposal to a few<00:23:07.920> weeks<00:23:08.010> ago<00:23:08.250> to<00:23:09.090> be<00:23:09.240> misled<00:23:09.720> by<00:23:09.750> adding<00:23:10.440> up 00:23:10.610 --> 00:23:10.620 align:start position:0% few weeks ago to be misled by adding up 00:23:10.620 --> 00:23:15.740 align:start position:0% few weeks ago to be misled by adding up a<00:23:12.500> certain<00:23:13.500> the<00:23:13.740> middle<00:23:14.070> and<00:23:14.460> set<00:23:14.910> allows<00:23:15.480> us 00:23:15.740 --> 00:23:15.750 align:start position:0% a certain the middle and set allows us 00:23:15.750 --> 00:23:20.360 align:start position:0% a certain the middle and set allows us to<00:23:16.560> say<00:23:17.550> ok<00:23:17.790> you<00:23:18.000> will<00:23:18.210> mourn<00:23:18.510> as<00:23:19.020> a<00:23:19.590> validator 00:23:20.360 --> 00:23:20.370 align:start position:0% to say ok you will mourn as a validator 00:23:20.370 --> 00:23:25.220 align:start position:0% to say ok you will mourn as a validator but<00:23:20.880> report<00:23:21.270> know<00:23:21.450> which<00:23:22.790> valedictorian<00:23:24.230> so 00:23:25.220 --> 00:23:25.230 align:start position:0% but report know which valedictorian so 00:23:25.230 --> 00:23:27.890 align:start position:0% but report know which valedictorian so it's<00:23:25.350> basically<00:23:25.680> basically<00:23:26.150> playing<00:23:27.150> with<00:23:27.510> a 00:23:27.890 --> 00:23:27.900 align:start position:0% it's basically basically playing with a 00:23:27.900 --> 00:23:30.350 align:start position:0% it's basically basically playing with a look<00:23:28.350> at<00:23:28.470> the<00:23:28.590> home<00:23:28.740> is<00:23:28.860> that<00:23:29.040> they<00:23:29.400> override 00:23:30.350 --> 00:23:30.360 align:start position:0% look at the home is that they override 00:23:30.360 --> 00:23:32.690 align:start position:0% look at the home is that they override no<00:23:30.570> one<00:23:30.840> private<00:23:31.770> keys<00:23:32.070> but<00:23:32.220> I<00:23:32.370> will<00:23:32.520> tell<00:23:32.640> you 00:23:32.690 --> 00:23:32.700 align:start position:0% no one private keys but I will tell you 00:23:32.700 --> 00:23:35.750 align:start position:0% no one private keys but I will tell you going<00:23:32.970> on<00:23:33.180> but<00:23:33.840> I<00:23:34.140> can't<00:23:34.560> be<00:23:34.710> spiteful<00:23:35.010> inside 00:23:35.750 --> 00:23:35.760 align:start position:0% going on but I can't be spiteful inside 00:23:35.760 --> 00:23:38.540 align:start position:0% going on but I can't be spiteful inside ok<00:23:36.330> so<00:23:37.110> that<00:23:37.260> was<00:23:37.470> before<00:23:37.740> and<00:23:38.130> learning<00:23:38.400> with 00:23:38.540 --> 00:23:38.550 align:start position:0% ok so that was before and learning with 00:23:38.550 --> 00:23:42.950 align:start position:0% ok so that was before and learning with other<00:23:38.790> civilians<00:23:39.300> during<00:23:39.930> the<00:23:40.200> ground<00:23:41.960> and 00:23:42.950 --> 00:23:42.960 align:start position:0% other civilians during the ground and 00:23:42.960 --> 00:23:46.010 align:start position:0% other civilians during the ground and then<00:23:43.170> if<00:23:43.560> the<00:23:43.770> issues<00:23:44.160> is<00:23:44.670> IP<00:23:44.970> address<00:23:45.780> stuff 00:23:46.010 --> 00:23:46.020 align:start position:0% then if the issues is IP address stuff 00:23:46.020 --> 00:23:49.850 align:start position:0% then if the issues is IP address stuff and<00:23:46.440> I<00:23:46.980> don't<00:23:47.460> think<00:23:47.700> as<00:23:47.790> in<00:23:48.120> right<00:23:48.360> now<00:23:48.860> it's 00:23:49.850 --> 00:23:49.860 align:start position:0% and I don't think as in right now it's 00:23:49.860 --> 00:23:52.550 align:start position:0% and I don't think as in right now it's worth<00:23:50.070> how<00:23:50.370> to<00:23:50.430> either<00:23:50.760> actual<00:23:51.240> eyes<00:23:51.450> well<00:23:52.440> no 00:23:52.550 --> 00:23:52.560 align:start position:0% worth how to either actual eyes well no 00:23:52.560 --> 00:23:54.290 align:start position:0% worth how to either actual eyes well no solutions<00:23:53.100> and<00:23:53.460> in<00:23:53.580> the<00:23:53.670> like<00:23:53.850> whatever 00:23:54.290 --> 00:23:54.300 align:start position:0% solutions and in the like whatever 00:23:54.300 --> 00:23:57.680 align:start position:0% solutions and in the like whatever vector<00:23:55.070> the<00:23:56.070> problem<00:23:56.520> in<00:23:57.000> this<00:23:57.270> is<00:23:57.330> whatever 00:23:57.680 --> 00:23:57.690 align:start position:0% vector the problem in this is whatever 00:23:57.690 --> 00:23:59.450 align:start position:0% vector the problem in this is whatever it's<00:23:58.290> going<00:23:58.470> to<00:23:58.530> be<00:23:58.620> marked<00:23:58.980> and<00:23:59.100> safe<00:23:59.280> because 00:23:59.450 --> 00:23:59.460 align:start position:0% it's going to be marked and safe because 00:23:59.460 --> 00:24:01.150 align:start position:0% it's going to be marked and safe because times<00:23:59.970> I<00:24:00.330> mean 00:24:01.150 --> 00:24:01.160 align:start position:0% times I mean 00:24:01.160 --> 00:24:05.830 align:start position:0% times I mean setting<00:24:01.730> groups<00:24:02.360> in<00:24:03.110> the<00:24:03.260> know<00:24:04.060> so<00:24:05.060> we<00:24:05.630> talk 00:24:05.830 --> 00:24:05.840 align:start position:0% setting groups in the know so we talk 00:24:05.840 --> 00:24:09.840 align:start position:0% setting groups in the know so we talk money<00:24:06.020> twice<00:24:06.320> because<00:24:07.480> this<00:24:08.480> we<00:24:08.660> might<00:24:08.960> talk 00:24:09.840 --> 00:24:09.850 align:start position:0% money twice because this we might talk 00:24:09.850 --> 00:24:13.630 align:start position:0% money twice because this we might talk but<00:24:10.900> we<00:24:11.900> tried<00:24:12.230> in<00:24:12.590> this<00:24:12.710> unit<00:24:13.100> of<00:24:13.250> meter 00:24:13.630 --> 00:24:13.640 align:start position:0% but we tried in this unit of meter 00:24:13.640 --> 00:24:15.820 align:start position:0% but we tried in this unit of meter participants<00:24:14.420> leave<00:24:14.600> some<00:24:14.900> notes<00:24:14.930> particular 00:24:15.820 --> 00:24:15.830 align:start position:0% participants leave some notes particular 00:24:15.830 --> 00:24:18.850 align:start position:0% participants leave some notes particular set<00:24:15.950> of<00:24:15.980> results<00:24:16.340> are<00:24:16.730> behind<00:24:17.600> this<00:24:18.260> potential 00:24:18.850 --> 00:24:18.860 align:start position:0% set of results are behind this potential 00:24:18.860 --> 00:24:22.300 align:start position:0% set of results are behind this potential one<00:24:19.130> second<00:24:19.460> and<00:24:19.760> what<00:24:20.120> we<00:24:20.270> see<00:24:20.480> this<00:24:21.310> will 00:24:22.300 --> 00:24:22.310 align:start position:0% one second and what we see this will 00:24:22.310 --> 00:24:24.910 align:start position:0% one second and what we see this will steam<00:24:22.520> Academy<00:24:22.760> and<00:24:23.300> mr.<00:24:23.630> business<00:24:24.230> which 00:24:24.910 --> 00:24:24.920 align:start position:0% steam Academy and mr. business which 00:24:24.920 --> 00:24:26.700 align:start position:0% steam Academy and mr. business which went<00:24:25.130> for<00:24:25.310> some<00:24:25.520> from<00:24:25.670> inspector 00:24:26.700 --> 00:24:26.710 align:start position:0% went for some from inspector 00:24:26.710 --> 00:24:33.040 align:start position:0% went for some from inspector what's<00:24:27.710> a<00:24:27.830> solution<00:24:29.230> ultra<00:24:30.230> John<00:24:31.210> the<00:24:32.210> idea<00:24:32.600> is 00:24:33.040 --> 00:24:33.050 align:start position:0% what's a solution ultra John the idea is 00:24:33.050 --> 00:24:35.740 align:start position:0% what's a solution ultra John the idea is you<00:24:33.560> can<00:24:33.590> very<00:24:34.370> quickly<00:24:34.520> we<00:24:35.000> can<00:24:35.150> finally 00:24:35.740 --> 00:24:35.750 align:start position:0% you can very quickly we can finally 00:24:35.750 --> 00:24:38.560 align:start position:0% you can very quickly we can finally develop<00:24:36.200> Italy<00:24:36.700> in<00:24:37.700> our<00:24:37.880> opinion<00:24:38.300> it's 00:24:38.560 --> 00:24:38.570 align:start position:0% develop Italy in our opinion it's 00:24:38.570 --> 00:24:41.160 align:start position:0% develop Italy in our opinion it's something<00:24:39.320> with<00:24:39.590> three<00:24:39.950> different 00:24:41.160 --> 00:24:41.170 align:start position:0% something with three different 00:24:41.170 --> 00:24:45.000 align:start position:0% something with three different components<00:24:43.120> 25,000<00:24:44.120> people<00:24:44.300> in<00:24:44.720> charge 00:24:45.000 --> 00:24:45.010 align:start position:0% components 25,000 people in charge 00:24:45.010 --> 00:24:49.420 align:start position:0% components 25,000 people in charge validation<00:24:46.510> in<00:24:47.510> charge<00:24:47.780> of<00:24:48.020> I<00:24:48.260> mean<00:24:48.860> people 00:24:49.420 --> 00:24:49.430 align:start position:0% validation in charge of I mean people 00:24:49.430 --> 00:24:50.670 align:start position:0% validation in charge of I mean people are<00:24:49.520> community 00:24:50.670 --> 00:24:50.680 align:start position:0% are community 00:24:50.680 --> 00:24:54.640 align:start position:0% are community we<00:24:51.680> don't<00:24:51.860> know<00:24:52.010> your<00:24:52.420> purity<00:24:53.420> and<00:24:54.380> there's 00:24:54.640 --> 00:24:54.650 align:start position:0% we don't know your purity and there's 00:24:54.650 --> 00:24:57.490 align:start position:0% we don't know your purity and there's Network<00:24:55.100> anonymity<00:24:55.490> which<00:24:56.420> is<00:24:56.660> the<00:24:57.140> unitary 00:24:57.490 --> 00:24:57.500 align:start position:0% Network anonymity which is the unitary 00:24:57.500 --> 00:25:02.260 align:start position:0% Network anonymity which is the unitary system<00:24:58.280> but<00:24:59.230> not<00:25:00.230> exactly<00:25:00.710> but<00:25:01.490> to<00:25:01.940> be<00:25:02.090> done 00:25:02.260 --> 00:25:02.270 align:start position:0% system but not exactly but to be done 00:25:02.270 --> 00:25:07.900 align:start position:0% system but not exactly but to be done anyway<00:25:03.100> in<00:25:04.300> the<00:25:05.300> possible<00:25:05.990> position<00:25:06.730> we<00:25:07.730> put 00:25:07.900 --> 00:25:07.910 align:start position:0% anyway in the possible position we put 00:25:07.910 --> 00:25:11.380 align:start position:0% anyway in the possible position we put the<00:25:08.030> pepper<00:25:09.340> what<00:25:10.340> we<00:25:10.520> use<00:25:10.670> for<00:25:11.000> vector 00:25:11.380 --> 00:25:11.390 align:start position:0% the pepper what we use for vector 00:25:11.390 --> 00:25:14.680 align:start position:0% the pepper what we use for vector notation<00:25:11.540> is<00:25:12.290> available<00:25:12.950> and<00:25:13.820> what<00:25:14.330> we<00:25:14.540> use 00:25:14.680 --> 00:25:14.690 align:start position:0% notation is available and what we use 00:25:14.690 --> 00:25:25.629 align:start position:0% notation is available and what we use for<00:25:14.720> my<00:25:14.960> situation 00:25:25.629 --> 00:25:25.639 align:start position:0% 00:25:25.639 --> 00:25:33.739 align:start position:0% let's<00:25:26.639> take<00:25:26.789> a<00:25:26.850> question<00:25:27.179> or<00:25:27.269> do<00:25:32.450> on<00:25:33.450> which 00:25:33.739 --> 00:25:33.749 align:start position:0% let's take a question or do on which 00:25:33.749 --> 00:25:39.590 align:start position:0% let's take a question or do on which part 00:25:39.590 --> 00:25:39.600 align:start position:0% 00:25:39.600 --> 00:25:42.440 align:start position:0% so<00:25:40.019> actually<00:25:40.500> it's<00:25:40.919> Philippi<00:25:41.250> preserved<00:25:41.580> at 00:25:42.440 --> 00:25:42.450 align:start position:0% so actually it's Philippi preserved at 00:25:42.450 --> 00:25:45.139 align:start position:0% so actually it's Philippi preserved at it<00:25:42.799> but<00:25:43.799> after<00:25:44.190> his<00:25:44.309> client<00:25:44.730> is<00:25:44.850> going<00:25:45.029> to 00:25:45.139 --> 00:25:45.149 align:start position:0% it but after his client is going to 00:25:45.149 --> 00:25:47.480 align:start position:0% it but after his client is going to intimate<00:25:45.450> it<00:25:45.570> has<00:25:46.409> been<00:25:46.919> waiting<00:25:47.220> to<00:25:47.370> be 00:25:47.480 --> 00:25:47.490 align:start position:0% intimate it has been waiting to be 00:25:47.490 --> 00:25:51.200 align:start position:0% intimate it has been waiting to be implemented<00:25:47.669> is<00:25:48.539> by<00:25:49.760> creating<00:25:50.760> on<00:25:51.179> the 00:25:51.200 --> 00:25:51.210 align:start position:0% implemented is by creating on the 00:25:51.210 --> 00:25:56.570 align:start position:0% implemented is by creating on the separate<00:25:51.779> one<00:25:52.049> part<00:25:53.029> process<00:25:54.110> some<00:25:55.580> things 00:25:56.570 --> 00:25:56.580 align:start position:0% separate one part process some things 00:25:56.580 --> 00:26:11.750 align:start position:0% separate one part process some things package<00:26:02.090> you<00:26:03.090> will<00:26:03.210> have<00:26:03.419> one<00:26:04.049> under<00:26:04.710> process 00:26:11.750 --> 00:26:11.760 align:start position:0% 00:26:11.760 --> 00:26:14.340 align:start position:0% by<00:26:12.760> different<00:26:13.150> varieties<00:26:13.750> but<00:26:13.930> somewhat 00:26:14.340 --> 00:26:14.350 align:start position:0% by different varieties but somewhat 00:26:14.350 --> 00:26:17.160 align:start position:0% by different varieties but somewhat disorganized<00:26:15.070> so<00:26:16.030> the<00:26:16.330> fact<00:26:16.570> that<00:26:16.630> it'll<00:26:16.960> work 00:26:17.160 --> 00:26:17.170 align:start position:0% disorganized so the fact that it'll work 00:26:17.170 --> 00:26:21.440 align:start position:0% disorganized so the fact that it'll work with<00:26:17.830> no<00:26:18.280> computers<00:26:18.790> and<00:26:19.560> decentralisation 00:26:21.440 --> 00:26:21.450 align:start position:0% with no computers and decentralisation 00:26:21.450 --> 00:26:24.030 align:start position:0% with no computers and decentralisation we<00:26:22.450> looked<00:26:22.660> into<00:26:22.840> and<00:26:23.170> ignore<00:26:23.500> that<00:26:23.530> we<00:26:23.830> will 00:26:24.030 --> 00:26:24.040 align:start position:0% we looked into and ignore that we will 00:26:24.040 --> 00:26:26.070 align:start position:0% we looked into and ignore that we will create<00:26:24.250> an<00:26:24.430> additional<00:26:24.610> 4,000<00:26:25.510> signature<00:26:25.870> for 00:26:26.070 --> 00:26:26.080 align:start position:0% create an additional 4,000 signature for 00:26:26.080 --> 00:26:27.990 align:start position:0% create an additional 4,000 signature for you 00:26:27.990 --> 00:26:28.000 align:start position:0% you 00:26:28.000 --> 00:26:29.880 align:start position:0% you so<00:26:28.360> what<00:26:28.540> let's<00:26:28.780> the<00:26:28.870> main<00:26:29.140> thing<00:26:29.470> that<00:26:29.500> is 00:26:29.880 --> 00:26:29.890 align:start position:0% so what let's the main thing that is 00:26:29.890 --> 00:26:33.930 align:start position:0% so what let's the main thing that is menu 00:26:33.930 --> 00:26:33.940 align:start position:0% 00:26:33.940 --> 00:26:52.870 align:start position:0% [Music] 00:26:52.870 --> 00:26:52.880 align:start position:0% 00:26:52.880 --> 00:26:57.980 align:start position:0% but<00:26:53.880> we<00:26:54.210> shuffle<00:26:54.900> them<00:26:56.300> using<00:26:57.300> them<00:26:57.480> in<00:26:57.810> each 00:26:57.980 --> 00:26:57.990 align:start position:0% but we shuffle them using them in each 00:26:57.990 --> 00:27:03.130 align:start position:0% but we shuffle them using them in each element<00:26:58.320> exactly<00:26:59.310> we<00:26:59.400> need<00:26:59.520> to<00:26:59.610> suffer<00:26:59.790> that 00:27:03.130 --> 00:27:03.140 align:start position:0% 00:27:03.140 --> 00:27:07.930 align:start position:0% point<00:27:04.140> as<00:27:04.320> well<00:27:04.500> yes<00:27:04.710> we<00:27:05.550> rely<00:27:05.970> on<00:27:06.350> ourselves 00:27:07.930 --> 00:27:07.940 align:start position:0% point as well yes we rely on ourselves 00:27:07.940 --> 00:27:12.230 align:start position:0% point as well yes we rely on ourselves or<00:27:08.940> soft<00:27:09.180> ominous<00:27:09.560> news<00:27:10.560> which<00:27:11.460> is<00:27:11.670> I<00:27:11.880> haven't 00:27:12.230 --> 00:27:12.240 align:start position:0% or soft ominous news which is I haven't 00:27:12.240 --> 00:27:14.080 align:start position:0% or soft ominous news which is I haven't to<00:27:12.300> take<00:27:12.480> this<00:27:12.570> because<00:27:12.900> it's<00:27:13.080> not 00:27:14.080 --> 00:27:14.090 align:start position:0% to take this because it's not 00:27:14.090 --> 00:27:19.640 align:start position:0% to take this because it's not communities<00:27:16.100> in<00:27:17.100> the<00:27:17.220> future<00:27:17.370> what<00:27:17.760> is<00:27:18.650> too 00:27:19.640 --> 00:27:19.650 align:start position:0% communities in the future what is too 00:27:19.650 --> 00:27:24.530 align:start position:0% communities in the future what is too much<00:27:19.800> of<00:27:19.950> other<00:27:20.130> mess<00:27:20.660> is<00:27:21.660> part<00:27:21.900> it's<00:27:23.540> because 00:27:24.530 --> 00:27:24.540 align:start position:0% much of other mess is part it's because 00:27:24.540 --> 00:27:27.380 align:start position:0% much of other mess is part it's because the<00:27:25.380> world<00:27:25.590> if<00:27:25.800> you<00:27:25.920> can<00:27:26.190> if<00:27:26.580> you<00:27:26.760> don't 00:27:27.380 --> 00:27:27.390 align:start position:0% the world if you can if you don't 00:27:27.390 --> 00:27:29.060 align:start position:0% the world if you can if you don't important<00:27:27.900> s<00:27:28.080> it<00:27:28.260> means<00:27:28.440> that<00:27:28.530> we<00:27:28.650> can<00:27:28.800> choose 00:27:29.060 --> 00:27:29.070 align:start position:0% important s it means that we can choose 00:27:29.070 --> 00:27:31.910 align:start position:0% important s it means that we can choose your<00:27:29.190> position<00:27:29.640> which<00:27:29.880> we<00:27:30.710> as<00:27:31.710> white 00:27:31.910 --> 00:27:31.920 align:start position:0% your position which we as white 00:27:31.920 --> 00:27:33.680 align:start position:0% your position which we as white Americans<00:27:32.100> say<00:27:32.490> oh<00:27:32.520> I<00:27:32.610> don't<00:27:32.820> like<00:27:33.060> this<00:27:33.450> guy 00:27:33.680 --> 00:27:33.690 align:start position:0% Americans say oh I don't like this guy 00:27:33.690 --> 00:27:36.380 align:start position:0% Americans say oh I don't like this guy well<00:27:33.900> so<00:27:34.200> all<00:27:34.710> my<00:27:34.950> by<00:27:35.070> 1902<00:27:35.550> connects<00:27:36.060> to<00:27:36.180> him 00:27:36.380 --> 00:27:36.390 align:start position:0% well so all my by 1902 connects to him 00:27:36.390 --> 00:27:38.960 align:start position:0% well so all my by 1902 connects to him and<00:27:36.690> with<00:27:36.870> perfect<00:27:37.620> perspective<00:27:38.460> ammunition 00:27:38.960 --> 00:27:38.970 align:start position:0% and with perfect perspective ammunition 00:27:38.970 --> 00:27:47.330 align:start position:0% and with perfect perspective ammunition will<00:27:39.840> become<00:27:40.230> 2<00:27:40.440> or<00:27:40.650> whatever<00:27:45.200> so<00:27:46.250> there's<00:27:47.250> a 00:27:47.330 --> 00:27:47.340 align:start position:0% will become 2 or whatever so there's a 00:27:47.340 --> 00:27:49.940 align:start position:0% will become 2 or whatever so there's a dependency<00:27:47.940> analysis<00:27:48.650> incontinence<00:27:49.650> and 00:27:49.940 --> 00:27:49.950 align:start position:0% dependency analysis incontinence and 00:27:49.950 --> 00:27:55.420 align:start position:0% dependency analysis incontinence and ensure<00:27:50.340> that<00:27:50.460> your<00:27:50.790> life<00:27:50.970> and<00:27:51.270> so<00:27:51.630> much 00:27:55.420 --> 00:27:55.430 align:start position:0% 00:27:55.430 --> 00:27:57.499 align:start position:0% [Music] 00:27:57.499 --> 00:27:57.509 align:start position:0% [Music] 00:27:57.509 --> 00:28:03.210 align:start position:0% [Music] what<00:27:58.509> defense<00:27:59.289> against<00:27:59.590> the<00:28:00.539> Phillies 00:28:03.210 --> 00:28:03.220 align:start position:0% what defense against the Phillies 00:28:03.220 --> 00:28:26.070 align:start position:0% what defense against the Phillies so<00:28:03.700> we<00:28:03.820> reconsider<00:28:04.769> petition 00:28:26.070 --> 00:28:26.080 align:start position:0% 00:28:26.080 --> 00:28:35.770 align:start position:0% soonish<00:28:27.080> ball 00:28:35.770 --> 00:28:35.780 align:start position:0% 00:28:35.780 --> 00:28:40.240 align:start position:0% [Applause]