WEBVTT Kind: captions Language: en 00:00:01.070 --> 00:00:11.299 align:start position:0% [Applause] 00:00:11.299 --> 00:00:11.309 align:start position:0% 00:00:11.309 --> 00:00:14.490 align:start position:0% my<00:00:12.309> name<00:00:12.459> is<00:00:12.610> jangan<00:00:12.969> kau<00:00:13.240> kini<00:00:13.599> and<00:00:13.839> they'll 00:00:14.490 --> 00:00:14.500 align:start position:0% my name is jangan kau kini and they'll 00:00:14.500 --> 00:00:18.480 align:start position:0% my name is jangan kau kini and they'll be<00:00:14.740> the<00:00:15.219> same<00:00:15.250> plentiful<00:00:16.080> interest<00:00:17.340> in<00:00:18.340> this 00:00:18.480 --> 00:00:18.490 align:start position:0% be the same plentiful interest in this 00:00:18.490 --> 00:00:20.370 align:start position:0% be the same plentiful interest in this presentation<00:00:18.880> I'll<00:00:19.360> talk<00:00:19.630> about<00:00:19.720> how<00:00:20.349> we 00:00:20.370 --> 00:00:20.380 align:start position:0% presentation I'll talk about how we 00:00:20.380 --> 00:00:22.710 align:start position:0% presentation I'll talk about how we extended<00:00:21.070> the<00:00:21.400> history<00:00:21.970> of<00:00:22.090> soccer<00:00:22.480> and 00:00:22.710 --> 00:00:22.720 align:start position:0% extended the history of soccer and 00:00:22.720 --> 00:00:32.510 align:start position:0% extended the history of soccer and tension<00:00:23.169> bonus<00:00:23.520> infinity<00:00:29.879> okay 00:00:32.510 --> 00:00:32.520 align:start position:0% tension bonus infinity okay 00:00:32.520 --> 00:00:36.900 align:start position:0% tension bonus infinity okay October<00:00:33.520> 1st<00:00:33.969> is<00:00:34.180> about<00:00:34.660> Twiggy's<00:00:35.730> police' 00:00:36.900 --> 00:00:36.910 align:start position:0% October 1st is about Twiggy's police' 00:00:36.910 --> 00:00:39.630 align:start position:0% October 1st is about Twiggy's police' content<00:00:37.600> platform<00:00:38.110> built<00:00:38.530> by<00:00:38.770> graphics<00:00:39.399> a 00:00:39.630 --> 00:00:39.640 align:start position:0% content platform built by graphics a 00:00:39.640 --> 00:00:43.310 align:start position:0% content platform built by graphics a crab<00:00:40.329> legs<00:00:40.539> with<00:00:41.219> clutches<00:00:42.219> of<00:00:42.339> material 00:00:43.310 --> 00:00:43.320 align:start position:0% crab legs with clutches of material 00:00:43.320 --> 00:00:48.000 align:start position:0% crab legs with clutches of material which<00:00:44.320> is<00:00:44.699> Korea's<00:00:45.809> largest<00:00:46.809> mobile<00:00:46.989> platform 00:00:48.000 --> 00:00:48.010 align:start position:0% which is Korea's largest mobile platform 00:00:48.010 --> 00:00:51.479 align:start position:0% which is Korea's largest mobile platform I<00:00:48.510> thought<00:00:49.510> Augustana<00:00:50.260> vertical<00:00:50.769> service<00:00:51.129> and 00:00:51.479 --> 00:00:51.489 align:start position:0% I thought Augustana vertical service and 00:00:51.489 --> 00:00:54.479 align:start position:0% I thought Augustana vertical service and this<00:00:52.269> is<00:00:52.420> wrong<00:00:53.260> messenger<00:00:53.620> service<00:00:54.010> in<00:00:54.280> South 00:00:54.479 --> 00:00:54.489 align:start position:0% this is wrong messenger service in South 00:00:54.489 --> 00:00:58.500 align:start position:0% this is wrong messenger service in South Korea<00:00:54.879> it<00:00:55.510> has<00:00:55.719> more<00:00:56.559> than<00:00:56.620> 96%<00:00:57.249> of<00:00:57.699> user 00:00:58.500 --> 00:00:58.510 align:start position:0% Korea it has more than 96% of user 00:00:58.510 --> 00:01:01.349 align:start position:0% Korea it has more than 96% of user penetration<00:00:59.199> so<00:00:59.679> this<00:00:59.829> is<00:00:59.979> therapy<00:01:00.399> services 00:01:01.349 --> 00:01:01.359 align:start position:0% penetration so this is therapy services 00:01:01.359 --> 00:01:05.009 align:start position:0% penetration so this is therapy services the<00:01:01.569> program<00:01:02.370> and<00:01:03.370> an<00:01:03.850> finish<00:01:04.239> from<00:01:04.600> from 00:01:05.009 --> 00:01:05.019 align:start position:0% the program and an finish from from 00:01:05.019 --> 00:01:07.350 align:start position:0% the program and an finish from from coffee<00:01:05.409> theory<00:01:05.710> on<00:01:05.860> so<00:01:06.130> this<00:01:06.640> is<00:01:06.790> if<00:01:07.180> they 00:01:07.350 --> 00:01:07.360 align:start position:0% coffee theory on so this is if they 00:01:07.360 --> 00:01:10.430 align:start position:0% coffee theory on so this is if they embraced<00:01:07.659> the<00:01:07.870> project<00:01:08.400> we<00:01:09.400> launched<00:01:09.729> lately 00:01:10.430 --> 00:01:10.440 align:start position:0% embraced the project we launched lately 00:01:10.440 --> 00:01:14.430 align:start position:0% embraced the project we launched lately until<00:01:11.440> this<00:01:11.590> year<00:01:12.750> as<00:01:13.750> you<00:01:13.810> can<00:01:14.050> see<00:01:14.200> on<00:01:14.290> the 00:01:14.430 --> 00:01:14.440 align:start position:0% until this year as you can see on the 00:01:14.440 --> 00:01:16.530 align:start position:0% until this year as you can see on the left<00:01:14.680> hand<00:01:14.770> side<00:01:15.070> v<00:01:15.850> is<00:01:15.970> an<00:01:16.150> open<00:01:16.420> source 00:01:16.530 --> 00:01:16.540 align:start position:0% left hand side v is an open source 00:01:16.540 --> 00:01:19.710 align:start position:0% left hand side v is an open source project<00:01:17.500> so<00:01:17.830> we<00:01:18.070> can<00:01:18.340> check<00:01:18.910> out<00:01:19.090> a<00:01:19.330> source 00:01:19.710 --> 00:01:19.720 align:start position:0% project so we can check out a source 00:01:19.720 --> 00:01:24.690 align:start position:0% project so we can check out a source code<00:01:19.900> with<00:01:20.440> BL<00:01:21.300> Sokka<00:01:22.300> Katara<00:01:22.540> and<00:01:23.320> we<00:01:24.310> can<00:01:24.490> get 00:01:24.690 --> 00:01:24.700 align:start position:0% code with BL Sokka Katara and we can get 00:01:24.700 --> 00:01:27.900 align:start position:0% code with BL Sokka Katara and we can get some<00:01:24.910> competitions<00:01:25.870> about<00:01:26.650> Clinton<00:01:27.070> we<00:01:27.790> are 00:01:27.900 --> 00:01:27.910 align:start position:0% some competitions about Clinton we are 00:01:27.910 --> 00:01:32.940 align:start position:0% some competitions about Clinton we are wasting<00:01:28.900> our<00:01:29.230> time<00:01:31.080> we<00:01:32.080> are<00:01:32.230> to<00:01:32.470> support 00:01:32.940 --> 00:01:32.950 align:start position:0% wasting our time we are to support 00:01:32.950 --> 00:01:35.700 align:start position:0% wasting our time we are to support enterprise<00:01:33.880> rail<00:01:34.180> services<00:01:34.720> as<00:01:34.960> a<00:01:35.140> coach<00:01:35.530> and 00:01:35.700 --> 00:01:35.710 align:start position:0% enterprise rail services as a coach and 00:01:35.710 --> 00:01:38.400 align:start position:0% enterprise rail services as a coach and platform<00:01:36.220> the<00:01:36.970> dispersion<00:01:37.330> feature<00:01:37.660> talk 00:01:38.400 --> 00:01:38.410 align:start position:0% platform the dispersion feature talk 00:01:38.410 --> 00:01:42.350 align:start position:0% platform the dispersion feature talk about<00:01:39.240> biology 00:01:42.350 --> 00:01:42.360 align:start position:0% 00:01:42.360 --> 00:01:46.020 align:start position:0% so<00:01:43.360> to<00:01:43.630> summarize<00:01:44.230> of<00:01:44.530> limitations<00:01:45.250> first<00:01:45.760> and 00:01:46.020 --> 00:01:46.030 align:start position:0% so to summarize of limitations first and 00:01:46.030 --> 00:01:49.380 align:start position:0% so to summarize of limitations first and foremost<00:01:46.660> one<00:01:46.870> is<00:01:47.050> a<00:01:47.290> little<00:01:47.440> cranky<00:01:48.240> now<00:01:49.240> in 00:01:49.380 --> 00:01:49.390 align:start position:0% foremost one is a little cranky now in 00:01:49.390 --> 00:01:52.830 align:start position:0% foremost one is a little cranky now in fatal<00:01:49.720> keep<00:01:50.410> air<00:01:50.680> in<00:01:50.950> Athenian<00:01:51.520> the<00:01:52.480> three 00:01:52.830 --> 00:01:52.840 align:start position:0% fatal keep air in Athenian the three 00:01:52.840 --> 00:01:55.140 align:start position:0% fatal keep air in Athenian the three male<00:01:53.110> stays<00:01:53.350> to<00:01:53.530> turn<00:01:53.740> so<00:01:54.370> if<00:01:54.700> you<00:01:54.820> click<00:01:55.000> on 00:01:55.140 --> 00:01:55.150 align:start position:0% male stays to turn so if you click on 00:01:55.150 --> 00:01:58.260 align:start position:0% male stays to turn so if you click on the<00:01:55.330> key<00:01:55.480> pair<00:01:55.780> it<00:01:56.140> means<00:01:56.440> you<00:01:56.920> create<00:01:57.190> a<00:01:57.430> dream 00:01:58.260 --> 00:01:58.270 align:start position:0% the key pair it means you create a dream 00:01:58.270 --> 00:02:01.960 align:start position:0% the key pair it means you create a dream account<00:01:59.550> so<00:02:00.550> what<00:02:00.700> if<00:02:00.820> you're<00:02:00.970> a<00:02:01.000> perky 00:02:01.960 --> 00:02:01.970 align:start position:0% account so what if you're a perky 00:02:01.970 --> 00:02:05.890 align:start position:0% account so what if you're a perky excellent<00:02:02.780> on<00:02:03.550> what<00:02:04.550> you<00:02:04.760> can<00:02:05.000> do<00:02:05.180> these<00:02:05.420> to 00:02:05.890 --> 00:02:05.900 align:start position:0% excellent on what you can do these to 00:02:05.900 --> 00:02:09.370 align:start position:0% excellent on what you can do these to create<00:02:06.200> another<00:02:06.650> account<00:02:07.150> but<00:02:08.150> we<00:02:08.380> interest 00:02:09.370 --> 00:02:09.380 align:start position:0% create another account but we interest 00:02:09.380 --> 00:02:12.220 align:start position:0% create another account but we interest more<00:02:09.680> additional<00:02:10.640> problems<00:02:11.060> so<00:02:11.930> you<00:02:11.960> should 00:02:12.220 --> 00:02:12.230 align:start position:0% more additional problems so you should 00:02:12.230 --> 00:02:15.370 align:start position:0% more additional problems so you should tell<00:02:12.650> the<00:02:13.040> address<00:02:13.250> to<00:02:14.180> your<00:02:14.330> friend<00:02:14.720> to<00:02:15.230> make 00:02:15.370 --> 00:02:15.380 align:start position:0% tell the address to your friend to make 00:02:15.380 --> 00:02:17.650 align:start position:0% tell the address to your friend to make sure<00:02:15.560> they're<00:02:16.000> toast<00:02:17.000> your<00:02:17.150> friend<00:02:17.420> to<00:02:17.630> the 00:02:17.650 --> 00:02:17.660 align:start position:0% sure they're toast your friend to the 00:02:17.660 --> 00:02:20.890 align:start position:0% sure they're toast your friend to the same<00:02:17.990> but<00:02:18.920> with<00:02:19.070> their<00:02:19.310> to<00:02:19.520> the<00:02:20.330> old<00:02:20.480> madness 00:02:20.890 --> 00:02:20.900 align:start position:0% same but with their to the old madness 00:02:20.900 --> 00:02:24.390 align:start position:0% same but with their to the old madness in<00:02:21.800> any<00:02:22.040> shop<00:02:22.190> you<00:02:23.180> should<00:02:23.210> transfer<00:02:23.660> your 00:02:24.390 --> 00:02:24.400 align:start position:0% in any shop you should transfer your 00:02:24.400 --> 00:02:27.580 align:start position:0% in any shop you should transfer your necessity<00:02:25.400> all<00:02:25.670> the<00:02:25.940> nurses<00:02:26.300> to<00:02:26.780> to<00:02:27.350> a<00:02:27.380> new 00:02:27.580 --> 00:02:27.590 align:start position:0% necessity all the nurses to to a new 00:02:27.590 --> 00:02:29.920 align:start position:0% necessity all the nurses to to a new notice<00:02:27.860> if<00:02:28.370> you<00:02:28.550> use<00:02:28.730> any<00:02:29.030> disinterest 00:02:29.920 --> 00:02:29.930 align:start position:0% notice if you use any disinterest 00:02:29.930 --> 00:02:33.910 align:start position:0% notice if you use any disinterest applications<00:02:31.240> if<00:02:32.240> you<00:02:32.390> goes<00:02:32.570> to<00:02:32.870> expose<00:02:33.800> your 00:02:33.910 --> 00:02:33.920 align:start position:0% applications if you goes to expose your 00:02:33.920 --> 00:02:35.740 align:start position:0% applications if you goes to expose your credit<00:02:34.340> here<00:02:34.550> accidentally<00:02:35.180> Mustang<00:02:35.600> game 00:02:35.740 --> 00:02:35.750 align:start position:0% credit here accidentally Mustang game 00:02:35.750 --> 00:02:38.190 align:start position:0% credit here accidentally Mustang game you<00:02:36.080> should<00:02:36.290> follow<00:02:36.500> this<00:02:36.800> process<00:02:37.220> to<00:02:37.640> me 00:02:38.190 --> 00:02:38.200 align:start position:0% you should follow this process to me 00:02:38.200 --> 00:02:42.010 align:start position:0% you should follow this process to me this<00:02:39.200> is<00:02:39.320> very<00:02:39.730> inconvenient<00:02:40.730> and<00:02:41.120> unexpected 00:02:42.010 --> 00:02:42.020 align:start position:0% this is very inconvenient and unexpected 00:02:42.020 --> 00:02:46.090 align:start position:0% this is very inconvenient and unexpected pleasure<00:02:42.310> experiences<00:02:44.080> let's<00:02:45.080> compare<00:02:45.830> to 00:02:46.090 --> 00:02:46.100 align:start position:0% pleasure experiences let's compare to 00:02:46.100 --> 00:02:50.200 align:start position:0% pleasure experiences let's compare to the<00:02:46.460> pickle<00:02:47.180> car<00:02:48.070> if<00:02:49.070> you<00:02:49.190> click<00:02:49.370> on<00:02:49.520> if<00:02:50.000> your 00:02:50.200 --> 00:02:50.210 align:start position:0% the pickle car if you click on if your 00:02:50.210 --> 00:02:52.060 align:start position:0% the pickle car if you click on if your email<00:02:50.390> address<00:02:50.570> there's<00:02:51.140> a<00:02:51.230> bank<00:02:51.800> account 00:02:52.060 --> 00:02:52.070 align:start position:0% email address there's a bank account 00:02:52.070 --> 00:02:55.570 align:start position:0% email address there's a bank account number<00:02:52.450> also<00:02:53.450> technically<00:02:54.580> different 00:02:55.570 --> 00:02:55.580 align:start position:0% number also technically different 00:02:55.580 --> 00:02:57.430 align:start position:0% number also technically different private<00:02:56.090> key<00:02:56.240> as<00:02:56.540> the<00:02:56.570> password<00:02:56.810> of<00:02:57.410> your 00:02:57.430 --> 00:02:57.440 align:start position:0% private key as the password of your 00:02:57.440 --> 00:03:01.270 align:start position:0% private key as the password of your paper<00:02:58.190> found<00:02:58.720> but<00:02:59.720> if<00:02:59.810> you<00:03:00.080> expose<00:03:01.070> your 00:03:01.270 --> 00:03:01.280 align:start position:0% paper found but if you expose your 00:03:01.280 --> 00:03:03.940 align:start position:0% paper found but if you expose your password<00:03:02.050> what<00:03:03.050> do<00:03:03.170> you<00:03:03.260> need<00:03:03.410> to<00:03:03.620> do<00:03:03.800> these 00:03:03.940 --> 00:03:03.950 align:start position:0% password what do you need to do these 00:03:03.950 --> 00:03:05.890 align:start position:0% password what do you need to do these are<00:03:04.310> just<00:03:04.610> change<00:03:04.880> your<00:03:04.970> password<00:03:05.390> use<00:03:05.780> only 00:03:05.890 --> 00:03:05.900 align:start position:0% are just change your password use only 00:03:05.900 --> 00:03:06.760 align:start position:0% are just change your password use only two<00:03:06.230> three 00:03:06.760 --> 00:03:06.770 align:start position:0% two three 00:03:06.770 --> 00:03:10.479 align:start position:0% two three thank<00:03:07.700> you<00:03:07.790> pal<00:03:08.800> so<00:03:09.800> this<00:03:10.100> limiter 00:03:10.479 --> 00:03:10.489 align:start position:0% thank you pal so this limiter 00:03:10.489 --> 00:03:13.260 align:start position:0% thank you pal so this limiter practically 00:03:13.260 --> 00:03:13.270 align:start position:0% 00:03:13.270 --> 00:03:17.560 align:start position:0% is<00:03:14.270> a<00:03:14.300> little<00:03:14.570> imitation<00:03:14.870> the<00:03:16.360> second<00:03:17.360> thing 00:03:17.560 --> 00:03:17.570 align:start position:0% is a little imitation the second thing 00:03:17.570 --> 00:03:21.070 align:start position:0% is a little imitation the second thing is<00:03:18.110> legal<00:03:19.010> artistic<00:03:19.459> movements<00:03:19.840> if<00:03:20.840> you 00:03:21.070 --> 00:03:21.080 align:start position:0% is legal artistic movements if you 00:03:21.080 --> 00:03:24.190 align:start position:0% is legal artistic movements if you confuse<00:03:21.830> your<00:03:21.970> account<00:03:22.970> security<00:03:23.300> you<00:03:24.170> should 00:03:24.190 --> 00:03:24.200 align:start position:0% confuse your account security you should 00:03:24.200 --> 00:03:27.160 align:start position:0% confuse your account security you should you<00:03:24.620> can<00:03:24.739> use<00:03:24.950> our<00:03:25.190> participants<00:03:25.820> but<00:03:26.570> one 00:03:27.160 --> 00:03:27.170 align:start position:0% you can use our participants but one 00:03:27.170 --> 00:03:29.010 align:start position:0% you can use our participants but one interview<00:03:27.650> you<00:03:27.950> cannot<00:03:28.220> use<00:03:28.430> vertice 00:03:29.010 --> 00:03:29.020 align:start position:0% interview you cannot use vertice 00:03:29.020 --> 00:03:31.300 align:start position:0% interview you cannot use vertice economically<00:03:30.020> understand<00:03:30.530> you<00:03:31.280> should 00:03:31.300 --> 00:03:31.310 align:start position:0% economically understand you should 00:03:31.310 --> 00:03:34.090 align:start position:0% economically understand you should create<00:03:31.820> what<00:03:32.300> you<00:03:32.420> see<00:03:32.600> it's<00:03:33.230> not<00:03:33.410> country<00:03:33.830> and 00:03:34.090 --> 00:03:34.100 align:start position:0% create what you see it's not country and 00:03:34.100 --> 00:03:37.270 align:start position:0% create what you see it's not country and you<00:03:34.640> should<00:03:35.000> know<00:03:35.209> how<00:03:35.239> to<00:03:35.540> use<00:03:35.920> so<00:03:36.920> this<00:03:37.070> way 00:03:37.270 --> 00:03:37.280 align:start position:0% you should know how to use so this way 00:03:37.280 --> 00:03:40.210 align:start position:0% you should know how to use so this way this<00:03:37.880> is<00:03:38.000> very<00:03:38.209> inconvenient<00:03:38.900> so<00:03:39.650> we<00:03:39.860> should 00:03:40.210 --> 00:03:40.220 align:start position:0% this is very inconvenient so we should 00:03:40.220 --> 00:03:42.850 align:start position:0% this is very inconvenient so we should be<00:03:40.340> very<00:03:40.519> if<00:03:40.790> we<00:03:40.959> have<00:03:41.959> brother<00:03:42.530> see<00:03:42.739> my 00:03:42.850 --> 00:03:42.860 align:start position:0% be very if we have brother see my 00:03:42.860 --> 00:03:45.040 align:start position:0% be very if we have brother see my husband 00:03:45.040 --> 00:03:45.050 align:start position:0% husband 00:03:45.050 --> 00:03:49.330 align:start position:0% husband and<00:03:46.050> third<00:03:46.230> one<00:03:46.470> is<00:03:46.500> in<00:03:47.040> terms<00:03:47.280> of<00:03:47.400> something 00:03:49.330 --> 00:03:49.340 align:start position:0% and third one is in terms of something 00:03:49.340 --> 00:03:52.309 align:start position:0% and third one is in terms of something find<00:03:50.340> information<00:03:50.970> for<00:03:51.240> our<00:03:51.660> consent 00:03:52.309 --> 00:03:52.319 align:start position:0% find information for our consent 00:03:52.319 --> 00:03:55.000 align:start position:0% find information for our consent traditions<00:03:52.830> so<00:03:53.400> it<00:03:53.670> is<00:03:53.760> very<00:03:54.000> hard<00:03:54.209> to<00:03:54.300> extend 00:03:55.000 --> 00:03:55.010 align:start position:0% traditions so it is very hard to extend 00:03:55.010 --> 00:04:00.340 align:start position:0% traditions so it is very hard to extend deformities<00:03:56.840> and<00:03:57.840> first<00:03:58.470> one<00:03:58.620> is<00:03:58.800> you<00:03:59.490> should 00:04:00.340 --> 00:04:00.350 align:start position:0% deformities and first one is you should 00:04:00.350 --> 00:04:03.410 align:start position:0% deformities and first one is you should there's<00:04:01.350> no<00:04:01.590> attention<00:04:02.220> time<00:04:02.550> so<00:04:03.060> you<00:04:03.390> should 00:04:03.410 --> 00:04:03.420 align:start position:0% there's no attention time so you should 00:04:03.420 --> 00:04:06.140 align:start position:0% there's no attention time so you should that<00:04:04.080> there's<00:04:04.350> some<00:04:04.520> necessary<00:04:05.520> field<00:04:05.970> should 00:04:06.140 --> 00:04:06.150 align:start position:0% that there's some necessary field should 00:04:06.150 --> 00:04:08.809 align:start position:0% that there's some necessary field should be<00:04:06.209> included<00:04:06.720> in<00:04:06.900> the<00:04:07.130> tradition<00:04:08.130> presenter 00:04:08.809 --> 00:04:08.819 align:start position:0% be included in the tradition presenter 00:04:08.819 --> 00:04:12.830 align:start position:0% be included in the tradition presenter think<00:04:09.239> of<00:04:09.360> a<00:04:09.510> parrot<00:04:10.200> iceberg<00:04:11.270> if<00:04:12.270> you<00:04:12.450> just 00:04:12.830 --> 00:04:12.840 align:start position:0% think of a parrot iceberg if you just 00:04:12.840 --> 00:04:15.380 align:start position:0% think of a parrot iceberg if you just rebellion<00:04:13.380> listen<00:04:14.310> to<00:04:14.400> some<00:04:14.550> ether<00:04:14.730> to<00:04:15.120> your 00:04:15.380 --> 00:04:15.390 align:start position:0% rebellion listen to some ether to your 00:04:15.390 --> 00:04:18.650 align:start position:0% rebellion listen to some ether to your friends<00:04:16.400> you<00:04:17.400> don't<00:04:17.820> need<00:04:17.940> to<00:04:18.060> set<00:04:18.269> party 00:04:18.650 --> 00:04:18.660 align:start position:0% friends you don't need to set party 00:04:18.660 --> 00:04:20.930 align:start position:0% friends you don't need to set party appeal<00:04:18.989> but<00:04:19.440> it<00:04:19.590> should<00:04:19.739> be<00:04:19.859> always<00:04:20.220> because 00:04:20.930 --> 00:04:20.940 align:start position:0% appeal but it should be always because 00:04:20.940 --> 00:04:23.810 align:start position:0% appeal but it should be always because there's<00:04:21.180> a<00:04:21.390> silver<00:04:21.630> finish<00:04:22.200> the<00:04:22.410> floor<00:04:22.820> and 00:04:23.810 --> 00:04:23.820 align:start position:0% there's a silver finish the floor and 00:04:23.820 --> 00:04:27.050 align:start position:0% there's a silver finish the floor and there's<00:04:24.770> no<00:04:25.770> affiliate<00:04:26.250> fee<00:04:26.550> generation 00:04:27.050 --> 00:04:27.060 align:start position:0% there's no affiliate fee generation 00:04:27.060 --> 00:04:31.010 align:start position:0% there's no affiliate fee generation mechanism<00:04:28.910> affiliation<00:04:29.910> means<00:04:30.120> there<00:04:30.360> are<00:04:30.660> we 00:04:31.010 --> 00:04:31.020 align:start position:0% mechanism affiliation means there are we 00:04:31.020 --> 00:04:34.010 align:start position:0% mechanism affiliation means there are we can<00:04:31.050> gain<00:04:31.790> recently<00:04:32.790> instead<00:04:33.390> of<00:04:33.540> a<00:04:33.570> standard 00:04:34.010 --> 00:04:34.020 align:start position:0% can gain recently instead of a standard 00:04:34.020 --> 00:04:37.400 align:start position:0% can gain recently instead of a standard there's<00:04:34.740> no<00:04:34.950> such<00:04:35.520> thing<00:04:36.120> is<00:04:36.660> implemented<00:04:37.229> on 00:04:37.400 --> 00:04:37.410 align:start position:0% there's no such thing is implemented on 00:04:37.410 --> 00:04:42.500 align:start position:0% there's no such thing is implemented on a<00:04:37.680> do<00:04:38.840> so<00:04:39.840> I<00:04:39.960> say<00:04:40.229> think<00:04:40.590> about<00:04:41.090> these<00:04:42.090> are 00:04:42.500 --> 00:04:42.510 align:start position:0% a do so I say think about these are 00:04:42.510 --> 00:04:45.680 align:start position:0% a do so I say think about these are senior<00:04:42.870> engineers<00:04:43.370> first<00:04:44.370> ones<00:04:44.580> what<00:04:44.880> if<00:04:45.060> you 00:04:45.680 --> 00:04:45.690 align:start position:0% senior engineers first ones what if you 00:04:45.690 --> 00:04:48.909 align:start position:0% senior engineers first ones what if you as<00:04:45.990> a<00:04:46.050> user<00:04:46.830> should<00:04:47.280> pay<00:04:47.850> whenever<00:04:48.210> you<00:04:48.510> trees 00:04:48.909 --> 00:04:48.919 align:start position:0% as a user should pay whenever you trees 00:04:48.919 --> 00:04:53.230 align:start position:0% as a user should pay whenever you trees this<00:04:49.919> is<00:04:49.979> very<00:04:50.310> uncommon<00:04:50.729> but<00:04:51.200> one<00:04:52.220> older 00:04:53.230 --> 00:04:53.240 align:start position:0% this is very uncommon but one older 00:04:53.240 --> 00:04:55.760 align:start position:0% this is very uncommon but one older decentralized<00:04:54.240> application<00:04:54.870> requires<00:04:55.380> you 00:04:55.760 --> 00:04:55.770 align:start position:0% decentralized application requires you 00:04:55.770 --> 00:05:00.920 align:start position:0% decentralized application requires you to<00:04:55.830> paste<00:04:56.220> on<00:04:58.160> 22nd<00:04:59.160> is<00:04:59.340> it<00:04:59.610> one<00:04:59.850> of<00:04:59.880> you<00:05:00.150> as<00:05:00.510> a 00:05:00.920 --> 00:05:00.930 align:start position:0% to paste on 22nd is it one of you as a 00:05:00.930 --> 00:05:04.580 align:start position:0% to paste on 22nd is it one of you as a software<00:05:01.789> first<00:05:02.789> if<00:05:03.030> a<00:05:03.210> developer<00:05:03.600> want<00:05:04.440> to 00:05:04.580 --> 00:05:04.590 align:start position:0% software first if a developer want to 00:05:04.590 --> 00:05:07.340 align:start position:0% software first if a developer want to give<00:05:04.800> users<00:05:05.070> free<00:05:05.880> trial<00:05:06.210> period<00:05:06.450> this<00:05:07.200> is 00:05:07.340 --> 00:05:07.350 align:start position:0% give users free trial period this is 00:05:07.350 --> 00:05:11.120 align:start position:0% give users free trial period this is very<00:05:07.560> common<00:05:08.010> service<00:05:08.370> our<00:05:09.380> synthesis<00:05:10.380> but<00:05:10.650> it 00:05:11.120 --> 00:05:11.130 align:start position:0% very common service our synthesis but it 00:05:11.130 --> 00:05:13.620 align:start position:0% very common service our synthesis but it is<00:05:11.370> not<00:05:11.550> possible 00:05:13.620 --> 00:05:13.630 align:start position:0% is not possible 00:05:13.630 --> 00:05:16.500 align:start position:0% is not possible so<00:05:14.290> you<00:05:14.740> feel<00:05:14.920> provided<00:05:15.550> English<00:05:15.880> mechanism 00:05:16.500 --> 00:05:16.510 align:start position:0% so you feel provided English mechanism 00:05:16.510 --> 00:05:19.380 align:start position:0% so you feel provided English mechanism of<00:05:16.990> the<00:05:17.110> plant<00:05:17.320> another<00:05:17.590> those<00:05:18.460> seniors<00:05:19.150> will 00:05:19.380 --> 00:05:19.390 align:start position:0% of the plant another those seniors will 00:05:19.390 --> 00:05:25.170 align:start position:0% of the plant another those seniors will be<00:05:19.420> solved<00:05:20.110> very<00:05:20.350> easily<00:05:23.580> let's<00:05:24.580> talk<00:05:25.060> about 00:05:25.170 --> 00:05:25.180 align:start position:0% be solved very easily let's talk about 00:05:25.180 --> 00:05:28.020 align:start position:0% be solved very easily let's talk about what<00:05:25.750> we<00:05:25.930> are<00:05:26.200> designing<00:05:27.190> the<00:05:27.340> features<00:05:27.820> of 00:05:28.020 --> 00:05:28.030 align:start position:0% what we are designing the features of 00:05:28.030 --> 00:05:34.590 align:start position:0% what we are designing the features of theta<00:05:30.990> first<00:05:31.990> we<00:05:32.350> are<00:05:33.210> providing<00:05:34.210> a<00:05:34.240> friend 00:05:34.590 --> 00:05:34.600 align:start position:0% theta first we are providing a friend 00:05:34.600 --> 00:05:37.080 align:start position:0% theta first we are providing a friend key<00:05:34.870> to<00:05:35.620> do<00:05:35.770> this<00:05:35.920> we<00:05:36.130> can<00:05:36.310> change<00:05:36.340> your<00:05:36.790> friend 00:05:37.080 --> 00:05:37.090 align:start position:0% key to do this we can change your friend 00:05:37.090 --> 00:05:39.390 align:start position:0% key to do this we can change your friend key<00:05:37.330> if<00:05:37.540> you<00:05:37.720> expose<00:05:38.380> bureaucratically<00:05:39.130> once 00:05:39.390 --> 00:05:39.400 align:start position:0% key if you expose bureaucratically once 00:05:39.400 --> 00:05:44.510 align:start position:0% key if you expose bureaucratically once then<00:05:40.060> you<00:05:40.240> can<00:05:40.620> use<00:05:41.620> your<00:05:41.860> account<00:05:42.700> number 00:05:44.510 --> 00:05:44.520 align:start position:0% then you can use your account number 00:05:44.520 --> 00:05:48.210 align:start position:0% then you can use your account number continuously<00:05:45.690> and<00:05:46.740> also<00:05:47.740> we<00:05:47.860> stop<00:05:48.070> we're 00:05:48.210 --> 00:05:48.220 align:start position:0% continuously and also we stop we're 00:05:48.220 --> 00:05:49.680 align:start position:0% continuously and also we stop we're about<00:05:48.400> to<00:05:48.580> finally<00:05:49.000> kill<00:05:49.300> the<00:05:49.480> planet 00:05:49.680 --> 00:05:49.690 align:start position:0% about to finally kill the planet 00:05:49.690 --> 00:05:51.510 align:start position:0% about to finally kill the planet understood<00:05:50.290> you<00:05:50.530> don't<00:05:50.710> need<00:05:50.830> to<00:05:51.010> know<00:05:51.190> how<00:05:51.490> to 00:05:51.510 --> 00:05:51.520 align:start position:0% understood you don't need to know how to 00:05:51.520 --> 00:05:55.140 align:start position:0% understood you don't need to know how to create<00:05:52.330> how<00:05:52.990> to<00:05:53.050> use<00:05:53.380> a<00:05:53.710> smart<00:05:54.160> country<00:05:54.340> order 00:05:55.140 --> 00:05:55.150 align:start position:0% create how to use a smart country order 00:05:55.150 --> 00:05:58.740 align:start position:0% create how to use a smart country order for<00:05:55.630> the<00:05:55.720> Sigma<00:05:55.990> cancer<00:05:56.940> and<00:05:57.940> also<00:05:58.120> be<00:05:58.300> pounded 00:05:58.740 --> 00:05:58.750 align:start position:0% for the Sigma cancer and also be pounded 00:05:58.750 --> 00:06:00.540 align:start position:0% for the Sigma cancer and also be pounded out<00:05:58.960> there<00:05:59.260> are<00:05:59.380> several<00:05:59.590> doors<00:06:00.190> in<00:06:00.310> a<00:06:00.400> knock 00:06:00.540 --> 00:06:00.550 align:start position:0% out there are several doors in a knock 00:06:00.550 --> 00:06:03.330 align:start position:0% out there are several doors in a knock loud<00:06:00.790> when<00:06:01.480> a<00:06:01.510> desire<00:06:01.900> is<00:06:02.230> account<00:06:02.710> model<00:06:02.950> so 00:06:03.330 --> 00:06:03.340 align:start position:0% loud when a desire is account model so 00:06:03.340 --> 00:06:06.750 align:start position:0% loud when a desire is account model so we<00:06:03.910> can<00:06:04.150> assign<00:06:04.930> separately<00:06:05.500> you<00:06:06.370> can<00:06:06.520> assign 00:06:06.750 --> 00:06:06.760 align:start position:0% we can assign separately you can assign 00:06:06.760 --> 00:06:08.460 align:start position:0% we can assign separately you can assign keys<00:06:07.060> to<00:06:07.690> each<00:06:08.020> other 00:06:08.460 --> 00:06:08.470 align:start position:0% keys to each other 00:06:08.470 --> 00:06:12.210 align:start position:0% keys to each other and<00:06:08.680> you<00:06:08.770> can<00:06:09.180> comfort<00:06:10.180> to<00:06:11.080> your<00:06:11.230> fans<00:06:11.530> more 00:06:12.210 --> 00:06:12.220 align:start position:0% and you can comfort to your fans more 00:06:12.220 --> 00:06:15.810 align:start position:0% and you can comfort to your fans more specifically<00:06:13.320> and<00:06:14.320> we<00:06:14.590> talked<00:06:14.860> about<00:06:15.430> change 00:06:15.810 --> 00:06:15.820 align:start position:0% specifically and we talked about change 00:06:15.820 --> 00:06:20.070 align:start position:0% specifically and we talked about change the<00:06:15.940> model<00:06:16.270> you<00:06:17.200> can<00:06:17.730> really<00:06:18.750> provide<00:06:19.750> thirty 00:06:20.070 --> 00:06:20.080 align:start position:0% the model you can really provide thirty 00:06:20.080 --> 00:06:23.250 align:start position:0% the model you can really provide thirty potential<00:06:20.560> types<00:06:20.800> so<00:06:21.430> there<00:06:22.050> we<00:06:23.050> can<00:06:23.230> easily 00:06:23.250 --> 00:06:23.260 align:start position:0% potential types so there we can easily 00:06:23.260 --> 00:06:26.370 align:start position:0% potential types so there we can easily extend<00:06:24.180> any<00:06:25.180> features<00:06:25.570> of<00:06:25.810> the<00:06:25.900> change<00:06:26.080> type 00:06:26.370 --> 00:06:26.380 align:start position:0% extend any features of the change type 00:06:26.380 --> 00:06:28.260 align:start position:0% extend any features of the change type or<00:06:26.950> so<00:06:27.100> you<00:06:27.190> can<00:06:27.340> ignore<00:06:27.550> some<00:06:27.910> unnecessary 00:06:28.260 --> 00:06:28.270 align:start position:0% or so you can ignore some unnecessary 00:06:28.270 --> 00:06:30.930 align:start position:0% or so you can ignore some unnecessary periods<00:06:28.930> and<00:06:29.800> also<00:06:30.040> we<00:06:30.280> provide<00:06:30.430> ventilation 00:06:30.930 --> 00:06:30.940 align:start position:0% periods and also we provide ventilation 00:06:30.940 --> 00:06:35.970 align:start position:0% periods and also we provide ventilation a<00:06:31.390> custom<00:06:31.720> of<00:06:32.220> trenchant<00:06:33.220> woman<00:06:34.440> but<00:06:35.440> want<00:06:35.680> in 00:06:35.970 --> 00:06:35.980 align:start position:0% a custom of trenchant woman but want in 00:06:35.980 --> 00:06:38.790 align:start position:0% a custom of trenchant woman but want in our<00:06:36.480> society<00:06:37.480> that<00:06:37.690> we<00:06:37.990> preserve 00:06:38.790 --> 00:06:38.800 align:start position:0% our society that we preserve 00:06:38.800 --> 00:06:42.270 align:start position:0% our society that we preserve community<00:06:39.700> will<00:06:40.030> be<00:06:40.180> thin<00:06:40.440> which<00:06:41.440> means<00:06:41.770> it's 00:06:42.270 --> 00:06:42.280 align:start position:0% community will be thin which means it's 00:06:42.280 --> 00:06:44.520 align:start position:0% community will be thin which means it's in<00:06:42.460> traditions<00:06:43.060> and<00:06:43.300> they<00:06:43.420> still<00:06:43.690> on<00:06:43.960> Satan 00:06:44.520 --> 00:06:44.530 align:start position:0% in traditions and they still on Satan 00:06:44.530 --> 00:06:49.890 align:start position:0% in traditions and they still on Satan without<00:06:45.010> and<00:06:47.550> so<00:06:48.550> for<00:06:48.820> those<00:06:48.970> extinctions<00:06:49.660> we 00:06:49.890 --> 00:06:49.900 align:start position:0% without and so for those extinctions we 00:06:49.900 --> 00:06:52.140 align:start position:0% without and so for those extinctions we use<00:06:50.470> some<00:06:50.800> techniques<00:06:51.190> first<00:06:51.760> on<00:06:52.000> his 00:06:52.140 --> 00:06:52.150 align:start position:0% use some techniques first on his 00:06:52.150 --> 00:06:54.570 align:start position:0% use some techniques first on his interest<00:06:52.780> time<00:06:52.990> so<00:06:53.380> we<00:06:53.620> designed<00:06:53.980> three<00:06:54.340> the 00:06:54.570 --> 00:06:54.580 align:start position:0% interest time so we designed three the 00:06:54.580 --> 00:06:59.680 align:start position:0% interest time so we designed three the structures<00:06:55.090> account<00:06:55.840> of<00:06:56.260> a<00:06:56.440> key<00:06:56.740> transition 00:06:59.680 --> 00:06:59.690 align:start position:0% structures account of a key transition 00:06:59.690 --> 00:07:02.710 align:start position:0% structures account of a key transition there<00:07:00.320> are<00:07:00.410> structures<00:07:00.890> we<00:07:01.520> have<00:07:01.880> tried 00:07:02.710 --> 00:07:02.720 align:start position:0% there are structures we have tried 00:07:02.720 --> 00:07:05.380 align:start position:0% there are structures we have tried information<00:07:03.320> and<00:07:04.010> we<00:07:04.640> used<00:07:04.910> public 00:07:05.380 --> 00:07:05.390 align:start position:0% information and we used public 00:07:05.390 --> 00:07:06.270 align:start position:0% information and we used public appearances 00:07:06.270 --> 00:07:06.280 align:start position:0% appearances 00:07:06.280 --> 00:07:11.050 align:start position:0% appearances so<00:07:07.280> in<00:07:07.460> code<00:07:07.730> athina<00:07:08.360> at<00:07:08.900> first<00:07:09.230> then<00:07:10.060> the 00:07:11.050 --> 00:07:11.060 align:start position:0% so in code athina at first then the 00:07:11.060 --> 00:07:15.580 align:start position:0% so in code athina at first then the movie<00:07:11.870> data<00:07:12.110> with<00:07:12.740> simply<00:07:13.700> us<00:07:13.910> again<00:07:14.300> we<00:07:14.590> find 00:07:15.580 --> 00:07:15.590 align:start position:0% movie data with simply us again we find 00:07:15.590 --> 00:07:17.950 align:start position:0% movie data with simply us again we find information<00:07:16.090> so<00:07:17.090> when<00:07:17.270> we<00:07:17.420> think<00:07:17.570> of<00:07:17.720> this 00:07:17.950 --> 00:07:17.960 align:start position:0% information so when we think of this 00:07:17.960 --> 00:07:20.110 align:start position:0% information so when we think of this minute<00:07:18.710> about<00:07:18.950> this<00:07:19.160> matter<00:07:19.430> of<00:07:19.790> the 00:07:20.110 --> 00:07:20.120 align:start position:0% minute about this matter of the 00:07:20.120 --> 00:07:22.630 align:start position:0% minute about this matter of the structure<00:07:20.900> the<00:07:21.260> first<00:07:21.500> equal<00:07:22.400> time 00:07:22.630 --> 00:07:22.640 align:start position:0% structure the first equal time 00:07:22.640 --> 00:07:25.690 align:start position:0% structure the first equal time information<00:07:23.330> and<00:07:23.510> then<00:07:24.050> mythical<00:07:24.860> was<00:07:25.490> some 00:07:25.690 --> 00:07:25.700 align:start position:0% information and then mythical was some 00:07:25.700 --> 00:07:30.730 align:start position:0% information and then mythical was some game<00:07:25.910> face<00:07:26.750> on<00:07:26.780> the<00:07:26.990> file<00:07:27.230> information<00:07:29.740> so 00:07:30.730 --> 00:07:30.740 align:start position:0% game face on the file information so 00:07:30.740 --> 00:07:36.580 align:start position:0% game face on the file information so let's<00:07:30.770> talk<00:07:31.190> about<00:07:31.310> a<00:07:31.640> more<00:07:34.960> an<00:07:35.960> interpreters 00:07:36.580 --> 00:07:36.590 align:start position:0% let's talk about a more an interpreters 00:07:36.590 --> 00:07:39.190 align:start position:0% let's talk about a more an interpreters a<00:07:36.860> single<00:07:37.250> account<00:07:37.580> type<00:07:37.940> here<00:07:38.450> so<00:07:38.840> there's<00:07:39.140> no 00:07:39.190 --> 00:07:39.200 align:start position:0% a single account type here so there's no 00:07:39.200 --> 00:07:43.510 align:start position:0% a single account type here so there's no flight<00:07:39.530> information<00:07:40.270> and<00:07:41.380> VM<00:07:42.380> we<00:07:42.950> can<00:07:43.130> see<00:07:43.280> we 00:07:43.510 --> 00:07:43.520 align:start position:0% flight information and VM we can see we 00:07:43.520 --> 00:07:47.530 align:start position:0% flight information and VM we can see we have<00:07:43.640> four<00:07:43.880> finish<00:07:44.600> here<00:07:44.840> but<00:07:45.500> history<00:07:46.040> has<00:07:46.540> it 00:07:47.530 --> 00:07:47.540 align:start position:0% have four finish here but history has it 00:07:47.540 --> 00:07:52.020 align:start position:0% have four finish here but history has it distinguishes<00:07:48.110> two<00:07:48.440> types<00:07:50.110> smart<00:07:51.110> culture 00:07:52.020 --> 00:07:52.030 align:start position:0% distinguishes two types smart culture 00:07:52.030 --> 00:07:56.260 align:start position:0% distinguishes two types smart culture becomes<00:07:53.030> an<00:07:53.920> Estonian<00:07:54.920> doctrines<00:07:55.340> or<00:07:55.670> a 00:07:56.260 --> 00:07:56.270 align:start position:0% becomes an Estonian doctrines or a 00:07:56.270 --> 00:07:59.140 align:start position:0% becomes an Estonian doctrines or a domain<00:07:56.560> but<00:07:57.560> as<00:07:58.130> of<00:07:58.310> September<00:07:58.820> of<00:07:58.850> this<00:07:59.090> year 00:07:59.140 --> 00:07:59.150 align:start position:0% domain but as of September of this year 00:07:59.150 --> 00:08:03.550 align:start position:0% domain but as of September of this year we<00:07:59.630> found<00:07:59.840> more<00:08:00.830> than<00:08:00.980> 8%<00:08:01.640> of<00:08:02.270> the<00:08:03.170> thermal 00:08:03.550 --> 00:08:03.560 align:start position:0% we found more than 8% of the thermal 00:08:03.560 --> 00:08:08.170 align:start position:0% we found more than 8% of the thermal transfer<00:08:04.630> awaits<00:08:06.160> in<00:08:07.160> eh<00:08:07.520> there's<00:08:07.850> no 00:08:08.170 --> 00:08:08.180 align:start position:0% transfer awaits in eh there's no 00:08:08.180 --> 00:08:10.630 align:start position:0% transfer awaits in eh there's no information<00:08:08.720> occurred<00:08:09.380> for<00:08:09.680> a<00:08:09.710> routine 00:08:10.630 --> 00:08:10.640 align:start position:0% information occurred for a routine 00:08:10.640 --> 00:08:14.530 align:start position:0% information occurred for a routine voltage<00:08:11.150> so<00:08:11.690> for<00:08:12.680> anyways<00:08:13.010> these<00:08:13.520> are<00:08:13.580> search 00:08:14.530 --> 00:08:14.540 align:start position:0% voltage so for anyways these are search 00:08:14.540 --> 00:08:18.850 align:start position:0% voltage so for anyways these are search warrant<00:08:16.060> so<00:08:17.060> to<00:08:17.120> evoke<00:08:17.720> this<00:08:17.900> kind<00:08:18.170> of<00:08:18.260> surge 00:08:18.850 --> 00:08:18.860 align:start position:0% warrant so to evoke this kind of surge 00:08:18.860 --> 00:08:25.930 align:start position:0% warrant so to evoke this kind of surge over<00:08:19.010> here<00:08:19.340> we<00:08:22.060> design<00:08:23.060> a<00:08:23.360> model<00:08:24.350> in<00:08:24.560> the<00:08:24.940> top 00:08:25.930 --> 00:08:25.940 align:start position:0% over here we design a model in the top 00:08:25.940 --> 00:08:30.130 align:start position:0% over here we design a model in the top five<00:08:26.240> so<00:08:26.600> we<00:08:27.260> have<00:08:27.440> to<00:08:27.680> contrast<00:08:28.280> here<00:08:28.670> and<00:08:29.600> you 00:08:30.130 --> 00:08:30.140 align:start position:0% five so we have to contrast here and you 00:08:30.140 --> 00:08:32.380 align:start position:0% five so we have to contrast here and you can<00:08:30.320> see<00:08:30.500> the<00:08:30.680> new<00:08:30.830> way<00:08:31.010> there's<00:08:31.370> no<00:08:31.550> routine 00:08:32.380 --> 00:08:32.390 align:start position:0% can see the new way there's no routine 00:08:32.390 --> 00:08:35.770 align:start position:0% can see the new way there's no routine called<00:08:32.690> nest<00:08:32.930> build<00:08:33.320> so<00:08:33.950> you<00:08:34.070> can<00:08:34.280> just<00:08:34.780> search 00:08:35.770 --> 00:08:35.780 align:start position:0% called nest build so you can just search 00:08:35.780 --> 00:08:38.920 align:start position:0% called nest build so you can just search tossed<00:08:36.550> in<00:08:37.550> additionally<00:08:38.060> we<00:08:38.300> have<00:08:38.540> a<00:08:38.720> key 00:08:38.920 --> 00:08:38.930 align:start position:0% tossed in additionally we have a key 00:08:38.930 --> 00:08:42.100 align:start position:0% tossed in additionally we have a key field<00:08:39.169> which<00:08:39.620> is<00:08:39.919> here<00:08:40.160> and<00:08:40.479> this<00:08:41.479> account<00:08:41.840> key 00:08:42.100 --> 00:08:42.110 align:start position:0% field which is here and this account key 00:08:42.110 --> 00:08:46.600 align:start position:0% field which is here and this account key field<00:08:42.380> also<00:08:43.310> have<00:08:43.900> five<00:08:44.900> information<00:08:45.470> so<00:08:46.100> he 00:08:46.600 --> 00:08:46.610 align:start position:0% field also have five information so he 00:08:46.610 --> 00:08:48.150 align:start position:0% field also have five information so he field<00:08:46.820> can<00:08:47.060> be<00:08:47.090> configured 00:08:48.150 --> 00:08:48.160 align:start position:0% field can be configured 00:08:48.160 --> 00:08:52.530 align:start position:0% field can be configured one<00:08:48.450> of<00:08:49.450> those<00:08:49.750> four<00:08:50.080> times<00:08:51.060> let's<00:08:52.060> get<00:08:52.300> last 00:08:52.530 --> 00:08:52.540 align:start position:0% one of those four times let's get last 00:08:52.540 --> 00:08:55.890 align:start position:0% one of those four times let's get last is<00:08:52.900> what's<00:08:53.890> Malaya<00:08:54.250> III<00:08:55.120> thought<00:08:55.450> we<00:08:55.690> said<00:08:55.870> no 00:08:55.890 --> 00:08:55.900 align:start position:0% is what's Malaya III thought we said no 00:08:55.900 --> 00:08:58.920 align:start position:0% is what's Malaya III thought we said no key<00:08:56.320> this<00:08:56.710> is<00:08:56.860> provided<00:08:57.280> for<00:08:57.430> our<00:08:57.930> comparative 00:08:58.920 --> 00:08:58.930 align:start position:0% key this is provided for our comparative 00:08:58.930 --> 00:09:03.360 align:start position:0% key this is provided for our comparative it<00:08:59.230> with<00:08:59.440> you<00:09:00.240> and<00:09:01.240> also<00:09:01.420> consent<00:09:01.930> our<00:09:02.370> pollen 00:09:03.360 --> 00:09:03.370 align:start position:0% it with you and also consent our pollen 00:09:03.370 --> 00:09:06.090 align:start position:0% it with you and also consent our pollen kita<00:09:03.760> kita<00:09:03.910> in<00:09:04.660> this<00:09:04.870> case<00:09:05.080> traditions<00:09:05.950> of 00:09:06.090 --> 00:09:06.100 align:start position:0% kita kita in this case traditions of 00:09:06.100 --> 00:09:10.620 align:start position:0% kita kita in this case traditions of discipline<00:09:06.820> can<00:09:07.720> decide<00:09:08.110> by<00:09:08.520> dr.<00:09:09.520> McKee<00:09:09.820> that 00:09:10.620 --> 00:09:10.630 align:start position:0% discipline can decide by dr. McKee that 00:09:10.630 --> 00:09:13.700 align:start position:0% discipline can decide by dr. McKee that first<00:09:10.870> must<00:09:11.170> is<00:09:11.410> apology<00:09:12.190> to<00:09:12.640> can<00:09:12.940> change<00:09:13.270> any 00:09:13.700 --> 00:09:13.710 align:start position:0% first must is apology to can change any 00:09:13.710 --> 00:09:17.330 align:start position:0% first must is apology to can change any his<00:09:14.850> artists<00:09:15.850> too<00:09:16.120> perfect 00:09:17.330 --> 00:09:17.340 align:start position:0% his artists too perfect 00:09:17.340 --> 00:09:21.660 align:start position:0% his artists too perfect so<00:09:18.630> we<00:09:19.630> provide<00:09:20.050> participant<00:09:20.770> another<00:09:21.220> plan<00:09:21.550> a 00:09:21.660 --> 00:09:21.670 align:start position:0% so we provide participant another plan a 00:09:21.670 --> 00:09:24.060 align:start position:0% so we provide participant another plan a misstep<00:09:21.970> so<00:09:22.360> we<00:09:22.810> can<00:09:22.990> say<00:09:23.170> multiple<00:09:23.680> public 00:09:24.060 --> 00:09:24.070 align:start position:0% misstep so we can say multiple public 00:09:24.070 --> 00:09:28.890 align:start position:0% misstep so we can say multiple public his<00:09:24.250> into<00:09:24.850> discreetly<00:09:26.850> to<00:09:27.850> respond<00:09:28.240> to 00:09:28.890 --> 00:09:28.900 align:start position:0% his into discreetly to respond to 00:09:28.900 --> 00:09:32.130 align:start position:0% his into discreetly to respond to comedies<00:09:29.290> workers<00:09:30.070> keys<00:09:30.370> we<00:09:31.150> have<00:09:31.360> found 00:09:32.130 --> 00:09:32.140 align:start position:0% comedies workers keys we have found 00:09:32.140 --> 00:09:33.120 align:start position:0% comedies workers keys we have found three<00:09:32.590> doors 00:09:33.120 --> 00:09:33.130 align:start position:0% three doors 00:09:33.130 --> 00:09:35.850 align:start position:0% three doors first<00:09:33.760> one<00:09:33.970> is<00:09:34.090> transition<00:09:34.870> the<00:09:35.320> second<00:09:35.650> one 00:09:35.850 --> 00:09:35.860 align:start position:0% first one is transition the second one 00:09:35.860 --> 00:09:40.050 align:start position:0% first one is transition the second one for<00:09:36.280> cantata<00:09:36.850> and<00:09:37.000> the<00:09:37.420> last<00:09:37.600> one<00:09:37.780> he<00:09:38.560> pay<00:09:39.060> his 00:09:40.050 --> 00:09:40.060 align:start position:0% for cantata and the last one he pay his 00:09:40.060 --> 00:09:42.510 align:start position:0% for cantata and the last one he pay his for<00:09:40.420> a<00:09:40.630> tradition<00:09:41.140> historic<00:09:42.040> traditional 00:09:42.510 --> 00:09:42.520 align:start position:0% for a tradition historic traditional 00:09:42.520 --> 00:09:47.120 align:start position:0% for a tradition historic traditional role<00:09:42.910> are<00:09:43.480> used<00:09:43.810> to<00:09:44.790> whisper<00:09:45.790> on<00:09:46.240> very 00:09:47.120 --> 00:09:47.130 align:start position:0% role are used to whisper on very 00:09:47.130 --> 00:09:49.950 align:start position:0% role are used to whisper on very desperate<00:09:48.130> ethically<00:09:48.640> and<00:09:49.000> smart<00:09:49.630> cuts<00:09:49.840> of 00:09:49.950 --> 00:09:49.960 align:start position:0% desperate ethically and smart cuts of 00:09:49.960 --> 00:09:53.580 align:start position:0% desperate ethically and smart cuts of execution<00:09:51.060> and<00:09:52.060> his<00:09:52.420> pearly<00:09:52.960> account<00:09:53.440> of 00:09:53.580 --> 00:09:53.590 align:start position:0% execution and his pearly account of 00:09:53.590 --> 00:09:57.500 align:start position:0% execution and his pearly account of interest<00:09:54.340> is<00:09:54.910> to<00:09:55.300> update<00:09:55.480> our<00:09:56.250> assumption<00:09:57.250> and 00:09:57.500 --> 00:09:57.510 align:start position:0% interest is to update our assumption and 00:09:57.510 --> 00:10:03.350 align:start position:0% interest is to update our assumption and the<00:09:58.510> last<00:09:58.720> one<00:09:59.220> peeping<00:10:00.220> a<00:10:00.340> role<00:10:00.550> is<00:10:00.900> used<00:10:01.900> to 00:10:03.350 --> 00:10:03.360 align:start position:0% the last one peeping a role is used to 00:10:03.360 --> 00:10:06.180 align:start position:0% the last one peeping a role is used to change<00:10:04.360> a<00:10:04.450> fee-only<00:10:04.660> so<00:10:05.260> if<00:10:05.530> we<00:10:05.650> have<00:10:05.830> only 00:10:06.180 --> 00:10:06.190 align:start position:0% change a fee-only so if we have only 00:10:06.190 --> 00:10:08.250 align:start position:0% change a fee-only so if we have only kissed<00:10:06.520> or<00:10:06.850> at<00:10:07.030> least<00:10:07.270> even<00:10:07.480> keep<00:10:07.960> in<00:10:08.170> your 00:10:08.250 --> 00:10:08.260 align:start position:0% kissed or at least even keep in your 00:10:08.260 --> 00:10:12.690 align:start position:0% kissed or at least even keep in your role<00:10:08.500> and<00:10:09.100> you<00:10:09.550> just<00:10:09.850> realize<00:10:10.390> that<00:10:10.420> you<00:10:11.700> can 00:10:12.690 --> 00:10:12.700 align:start position:0% role and you just realize that you can 00:10:12.700 --> 00:10:16.350 align:start position:0% role and you just realize that you can pay<00:10:13.450> transfer<00:10:14.020> only<00:10:14.170> if<00:10:14.890> you<00:10:15.070> have<00:10:15.310> chest<00:10:16.150> for 00:10:16.350 --> 00:10:16.360 align:start position:0% pay transfer only if you have chest for 00:10:16.360 --> 00:10:19.020 align:start position:0% pay transfer only if you have chest for a<00:10:16.390> value<00:10:16.660> and<00:10:17.380> you<00:10:17.440> need<00:10:17.800> to<00:10:18.010> know<00:10:18.310> that<00:10:18.610> you 00:10:19.020 --> 00:10:19.030 align:start position:0% a value and you need to know that you 00:10:19.030 --> 00:10:26.440 align:start position:0% a value and you need to know that you have<00:10:19.240> a<00:10:19.570> kiss<00:10:19.870> for<00:10:20.550> 21<00:10:22.620> let's<00:10:23.620> talk<00:10:23.770> about 00:10:26.440 --> 00:10:26.450 align:start position:0% 00:10:26.450 --> 00:10:29.069 align:start position:0% a<00:10:26.480> third<00:10:26.990> to<00:10:27.200> the<00:10:27.529> accountant<00:10:27.980> water 00:10:29.069 --> 00:10:29.079 align:start position:0% a third to the accountant water 00:10:29.079 --> 00:10:32.190 align:start position:0% a third to the accountant water interview<00:10:30.079> doesn't<00:10:30.500> have<00:10:30.680> tight<00:10:31.040> information 00:10:32.190 --> 00:10:32.200 align:start position:0% interview doesn't have tight information 00:10:32.200 --> 00:10:35.440 align:start position:0% interview doesn't have tight information changement<00:10:33.200> changement<00:10:33.820> but<00:10:34.820> intense<00:10:35.240> three 00:10:35.440 --> 00:10:35.450 align:start position:0% changement changement but intense three 00:10:35.450 --> 00:10:37.300 align:start position:0% changement changement but intense three functions<00:10:36.050> their<00:10:36.529> transfer<00:10:36.950> is 00:10:37.300 --> 00:10:37.310 align:start position:0% functions their transfer is 00:10:37.310 --> 00:10:39.190 align:start position:0% functions their transfer is mathematically<00:10:37.970> plain<00:10:38.240> there's<00:10:38.750> not<00:10:39.019> much 00:10:39.190 --> 00:10:39.200 align:start position:0% mathematically plain there's not much 00:10:39.200 --> 00:10:44.379 align:start position:0% mathematically plain there's not much execution<00:10:42.100> interpreting<00:10:43.209> transaction<00:10:44.209> be 00:10:44.379 --> 00:10:44.389 align:start position:0% execution interpreting transaction be 00:10:44.389 --> 00:10:48.009 align:start position:0% execution interpreting transaction be interest<00:10:45.320> or<00:10:45.649> war<00:10:46.579> feelers<00:10:46.970> from<00:10:47.600> sonia 00:10:48.009 --> 00:10:48.019 align:start position:0% interest or war feelers from sonia 00:10:48.019 --> 00:10:51.189 align:start position:0% interest or war feelers from sonia sender<00:10:48.500> address<00:10:48.820> this<00:10:49.820> is<00:10:50.029> a<00:10:50.060> recovered<00:10:51.050> to 00:10:51.189 --> 00:10:51.199 align:start position:0% sender address this is a recovered to 00:10:51.199 --> 00:10:54.490 align:start position:0% sender address this is a recovered to attitude<00:10:52.010> change<00:10:52.940> repaired<00:10:53.389> key<00:10:53.720> so<00:10:54.290> we 00:10:54.490 --> 00:10:54.500 align:start position:0% attitude change repaired key so we 00:10:54.500 --> 00:10:56.800 align:start position:0% attitude change repaired key so we should<00:10:54.709> explicitly<00:10:55.100> specify<00:10:55.880> the<00:10:56.420> standard 00:10:56.800 --> 00:10:56.810 align:start position:0% should explicitly specify the standard 00:10:56.810 --> 00:11:03.250 align:start position:0% should explicitly specify the standard errors<00:10:59.290> that<00:11:00.290> we<00:11:00.529> provide<00:11:00.980> but<00:11:01.670> see<00:11:02.630> mechanism 00:11:03.250 --> 00:11:03.260 align:start position:0% errors that we provide but see mechanism 00:11:03.260 --> 00:11:05.620 align:start position:0% errors that we provide but see mechanism the<00:11:03.769> sender's<00:11:04.100> features<00:11:04.519> can<00:11:04.790> add<00:11:05.000> body 00:11:05.620 --> 00:11:05.630 align:start position:0% the sender's features can add body 00:11:05.630 --> 00:11:09.699 align:start position:0% the sender's features can add body procedures<00:11:07.060> and<00:11:08.060> also<00:11:08.300> be<00:11:08.480> payer<00:11:08.959> addressed 00:11:09.699 --> 00:11:09.709 align:start position:0% procedures and also be payer addressed 00:11:09.709 --> 00:11:12.250 align:start position:0% procedures and also be payer addressed and<00:11:09.889> we<00:11:10.070> pay<00:11:10.220> interest<00:11:10.670> are<00:11:11.110> related<00:11:12.110> to 00:11:12.250 --> 00:11:12.260 align:start position:0% and we pay interest are related to 00:11:12.260 --> 00:11:14.740 align:start position:0% and we pay interest are related to finish<00:11:13.190> McMaster<00:11:13.730> but<00:11:14.300> they<00:11:14.480> are<00:11:14.600> not 00:11:14.740 --> 00:11:14.750 align:start position:0% finish McMaster but they are not 00:11:14.750 --> 00:11:18.550 align:start position:0% finish McMaster but they are not occurred<00:11:15.110> for<00:11:15.380> water<00:11:15.589> change<00:11:15.920> types<00:11:17.410> which<00:11:18.410> is 00:11:18.550 --> 00:11:18.560 align:start position:0% occurred for water change types which is 00:11:18.560 --> 00:11:20.800 align:start position:0% occurred for water change types which is that<00:11:18.740> shows<00:11:19.010> the<00:11:19.310> theorem<00:11:19.880> which 00:11:20.800 --> 00:11:20.810 align:start position:0% that shows the theorem which 00:11:20.810 --> 00:11:22.960 align:start position:0% that shows the theorem which interpretation<00:11:21.260> mechanism<00:11:21.889> as<00:11:22.459> you<00:11:22.610> can<00:11:22.790> see 00:11:22.960 --> 00:11:22.970 align:start position:0% interpretation mechanism as you can see 00:11:22.970 --> 00:11:24.879 align:start position:0% interpretation mechanism as you can see we<00:11:23.510> can<00:11:23.660> get<00:11:23.839> our<00:11:24.019> signatures<00:11:24.470> from<00:11:24.649> the 00:11:24.879 --> 00:11:24.889 align:start position:0% we can get our signatures from the 00:11:24.889 --> 00:11:26.470 align:start position:0% we can get our signatures from the transition<00:11:25.430> and<00:11:25.610> then<00:11:25.850> take<00:11:26.120> the<00:11:26.240> apology 00:11:26.470 --> 00:11:26.480 align:start position:0% transition and then take the apology 00:11:26.480 --> 00:11:28.990 align:start position:0% transition and then take the apology from<00:11:26.779> the<00:11:27.139> sketcher<00:11:27.680> and<00:11:27.860> we<00:11:28.579> can<00:11:28.730> get<00:11:28.880> the 00:11:28.990 --> 00:11:29.000 align:start position:0% from the sketcher and we can get the 00:11:29.000 --> 00:11:33.310 align:start position:0% from the sketcher and we can get the progress<00:11:29.420> from<00:11:30.079> the<00:11:30.380> policy<00:11:31.720> but<00:11:32.720> in<00:11:32.899> Clayton 00:11:33.310 --> 00:11:33.320 align:start position:0% progress from the policy but in Clayton 00:11:33.320 --> 00:11:36.310 align:start position:0% progress from the policy but in Clayton we<00:11:33.500> are<00:11:33.860> change<00:11:34.250> it<00:11:34.600> accountant<00:11:35.600> organization 00:11:36.310 --> 00:11:36.320 align:start position:0% we are change it accountant organization 00:11:36.320 --> 00:11:39.579 align:start position:0% we are change it accountant organization motor<00:11:36.560> we<00:11:37.070> should<00:11:37.339> some<00:11:37.820> work<00:11:38.410> attested<00:11:39.410> to 00:11:39.579 --> 00:11:39.589 align:start position:0% motor we should some work attested to 00:11:39.589 --> 00:11:42.790 align:start position:0% motor we should some work attested to verify<00:11:40.190> the<00:11:40.250> tradition<00:11:41.320> so<00:11:42.320> for<00:11:42.680> the 00:11:42.790 --> 00:11:42.800 align:start position:0% verify the tradition so for the 00:11:42.800 --> 00:11:45.250 align:start position:0% verify the tradition so for the determines<00:11:43.459> winter<00:11:43.730> shots<00:11:44.000> we<00:11:44.600> can<00:11:44.810> use<00:11:45.019> the 00:11:45.250 --> 00:11:45.260 align:start position:0% determines winter shots we can use the 00:11:45.260 --> 00:11:47.800 align:start position:0% determines winter shots we can use the same<00:11:45.589> mechanism<00:11:45.740> but<00:11:46.310> for<00:11:46.670> other<00:11:46.820> newly 00:11:47.800 --> 00:11:47.810 align:start position:0% same mechanism but for other newly 00:11:47.810 --> 00:11:50.920 align:start position:0% same mechanism but for other newly introduced<00:11:48.350> engine<00:11:49.279> clanks<00:11:49.610> we<00:11:50.240> can<00:11:50.449> follow 00:11:50.920 --> 00:11:50.930 align:start position:0% introduced engine clanks we can follow 00:11:50.930 --> 00:11:54.370 align:start position:0% introduced engine clanks we can follow the<00:11:51.110> but<00:11:51.740> against<00:11:51.980> time<00:11:52.630> so<00:11:53.630> it<00:11:53.810> is<00:11:54.079> a<00:11:54.110> feature 00:11:54.370 --> 00:11:54.380 align:start position:0% the but against time so it is a feature 00:11:54.380 --> 00:11:56.680 align:start position:0% the but against time so it is a feature from<00:11:54.920> the<00:11:55.130> transition<00:11:55.640> and<00:11:55.850> we<00:11:56.269> can<00:11:56.449> get<00:11:56.660> a 00:11:56.680 --> 00:11:56.690 align:start position:0% from the transition and we can get a 00:11:56.690 --> 00:11:59.079 align:start position:0% from the transition and we can get a public<00:11:57.110> key<00:11:57.260> of<00:11:57.470> a<00:11:57.560> switch<00:11:57.829> so<00:11:58.550> we<00:11:58.790> can<00:11:58.940> get 00:11:59.079 --> 00:11:59.089 align:start position:0% public key of a switch so we can get 00:11:59.089 --> 00:11:59.680 align:start position:0% public key of a switch so we can get funky 00:11:59.680 --> 00:11:59.690 align:start position:0% funky 00:11:59.690 --> 00:12:03.040 align:start position:0% funky that's<00:12:00.410> time<00:12:00.680> and<00:12:01.010> we<00:12:01.970> can<00:12:02.180> get<00:12:02.329> account<00:12:02.779> key 00:12:03.040 --> 00:12:03.050 align:start position:0% that's time and we can get account key 00:12:03.050 --> 00:12:06.130 align:start position:0% that's time and we can get account key from<00:12:03.380> the<00:12:04.329> sender<00:12:05.329> members<00:12:05.660> of<00:12:05.930> the 00:12:06.130 --> 00:12:06.140 align:start position:0% from the sender members of the 00:12:06.140 --> 00:12:10.360 align:start position:0% from the sender members of the transition<00:12:06.709> so<00:12:07.279> we<00:12:07.610> get<00:12:08.000> to<00:12:08.709> public<00:12:09.709> keys<00:12:09.949> and 00:12:10.360 --> 00:12:10.370 align:start position:0% transition so we get to public keys and 00:12:10.370 --> 00:12:13.750 align:start position:0% transition so we get to public keys and if<00:12:11.029> you<00:12:11.120> compare<00:12:11.420> both<00:12:11.720> the<00:12:11.750> keys<00:12:12.579> if<00:12:13.579> they 00:12:13.750 --> 00:12:13.760 align:start position:0% if you compare both the keys if they 00:12:13.760 --> 00:12:16.809 align:start position:0% if you compare both the keys if they match<00:12:14.029> then<00:12:14.540> you<00:12:14.720> can<00:12:14.930> say<00:12:15.079> here<00:12:15.370> this<00:12:16.370> is<00:12:16.430> very 00:12:16.809 --> 00:12:16.819 align:start position:0% match then you can say here this is very 00:12:16.819 --> 00:12:19.030 align:start position:0% match then you can say here this is very citation<00:12:17.390> if<00:12:17.930> they<00:12:18.110> are<00:12:18.199> not<00:12:18.350> mentioned<00:12:18.769> and 00:12:19.030 --> 00:12:19.040 align:start position:0% citation if they are not mentioned and 00:12:19.040 --> 00:12:24.680 align:start position:0% citation if they are not mentioned and can<00:12:19.730> say<00:12:19.940> that<00:12:20.120> the<00:12:20.990> tradition<00:12:21.410> is<00:12:21.529> in<00:12:21.800> them 00:12:24.680 --> 00:12:24.690 align:start position:0% 00:12:24.690 --> 00:12:27.420 align:start position:0% dispatcher<00:12:25.690> was<00:12:26.020> two<00:12:26.320> examples<00:12:26.890> of<00:12:27.160> our 00:12:27.420 --> 00:12:27.430 align:start position:0% dispatcher was two examples of our 00:12:27.430 --> 00:12:31.530 align:start position:0% dispatcher was two examples of our generation<00:12:28.420> ties<00:12:29.400> left<00:12:30.400> on<00:12:30.610> them<00:12:30.970> for<00:12:31.210> grabs 00:12:31.530 --> 00:12:31.540 align:start position:0% generation ties left on them for grabs 00:12:31.540 --> 00:12:33.360 align:start position:0% generation ties left on them for grabs on<00:12:31.690> shows<00:12:32.020> are<00:12:32.290> very<00:12:32.320> inspiring<00:12:32.740> right 00:12:33.360 --> 00:12:33.370 align:start position:0% on shows are very inspiring right 00:12:33.370 --> 00:12:38.190 align:start position:0% on shows are very inspiring right pontius<00:12:33.779> easily<00:12:34.779> will<00:12:35.350> transfer<00:12:37.200> the 00:12:38.190 --> 00:12:38.200 align:start position:0% pontius easily will transfer the 00:12:38.200 --> 00:12:40.440 align:start position:0% pontius easily will transfer the transports<00:12:38.770> petition<00:12:39.279> was<00:12:39.450> interrogation 00:12:40.440 --> 00:12:40.450 align:start position:0% transports petition was interrogation 00:12:40.450 --> 00:12:45.510 align:start position:0% transports petition was interrogation mechanism<00:12:40.930> so<00:12:42.120> it<00:12:43.120> was<00:12:43.270> not<00:12:43.450> have<00:12:43.660> to<00:12:44.140> have<00:12:44.520> he 00:12:45.510 --> 00:12:45.520 align:start position:0% mechanism so it was not have to have he 00:12:45.520 --> 00:12:48.660 align:start position:0% mechanism so it was not have to have he player<00:12:45.760> Atlas<00:12:46.180> NP<00:12:46.600> players<00:12:46.870> Rangers<00:12:47.430> so<00:12:48.430> when 00:12:48.660 --> 00:12:48.670 align:start position:0% player Atlas NP players Rangers so when 00:12:48.670 --> 00:12:51.630 align:start position:0% player Atlas NP players Rangers so when we<00:12:48.850> still<00:12:49.210> public<00:12:49.720> transport<00:12:50.080> transition<00:12:50.640> to 00:12:51.630 --> 00:12:51.640 align:start position:0% we still public transport transition to 00:12:51.640 --> 00:12:54.240 align:start position:0% we still public transport transition to therapy<00:12:52.120> really<00:12:52.720> charged<00:12:53.230> by<00:12:53.440> asserted<00:12:54.220> to 00:12:54.240 --> 00:12:54.250 align:start position:0% therapy really charged by asserted to 00:12:54.250 --> 00:12:57.480 align:start position:0% therapy really charged by asserted to sender<00:12:55.029> Everest<00:12:55.420> and<00:12:55.600> the<00:12:56.560> amount<00:12:56.950> of<00:12:57.040> tokens 00:12:57.480 --> 00:12:57.490 align:start position:0% sender Everest and the amount of tokens 00:12:57.490 --> 00:12:59.640 align:start position:0% sender Everest and the amount of tokens will<00:12:58.330> be<00:12:58.450> transferred<00:12:58.870> from<00:12:59.080> sender<00:12:59.500> address 00:12:59.640 --> 00:12:59.650 align:start position:0% will be transferred from sender address 00:12:59.650 --> 00:13:03.510 align:start position:0% will be transferred from sender address to<00:13:00.520> the<00:13:00.940> subpoena<00:13:01.360> and<00:13:02.130> many<00:13:03.130> skilled 00:13:03.510 --> 00:13:03.520 align:start position:0% to the subpoena and many skilled 00:13:03.520 --> 00:13:06.690 align:start position:0% to the subpoena and many skilled affinity<00:13:04.089> benefits<00:13:04.900> per<00:13:05.160> the<00:13:06.160> attention<00:13:06.550> fee 00:13:06.690 --> 00:13:06.700 align:start position:0% affinity benefits per the attention fee 00:13:06.700 --> 00:13:11.970 align:start position:0% affinity benefits per the attention fee will<00:13:07.390> be<00:13:07.680> charged<00:13:08.680> to<00:13:08.830> the<00:13:08.980> people<00:13:09.850> and<00:13:10.980> the 00:13:11.970 --> 00:13:11.980 align:start position:0% will be charged to the people and the 00:13:11.980 --> 00:13:13.650 align:start position:0% will be charged to the people and the amount<00:13:12.130> of<00:13:12.339> tokens<00:13:12.730> will<00:13:13.150> be<00:13:13.240> transferred 00:13:13.650 --> 00:13:13.660 align:start position:0% amount of tokens will be transferred 00:13:13.660 --> 00:13:18.210 align:start position:0% amount of tokens will be transferred from<00:13:13.810> the<00:13:13.900> sender<00:13:14.320> endless<00:13:14.650> to<00:13:15.250> disappear<00:13:17.220> and 00:13:18.210 --> 00:13:18.220 align:start position:0% from the sender endless to disappear and 00:13:18.220 --> 00:13:21.510 align:start position:0% from the sender endless to disappear and distractions<00:13:19.120> some<00:13:19.960> of<00:13:20.080> our<00:13:20.520> Clinton 00:13:21.510 --> 00:13:21.520 align:start position:0% distractions some of our Clinton 00:13:21.520 --> 00:13:25.079 align:start position:0% distractions some of our Clinton changing<00:13:21.880> tribes<00:13:22.680> settled<00:13:23.680> from<00:13:24.040> shows<00:13:24.370> page 00:13:25.079 --> 00:13:25.089 align:start position:0% changing tribes settled from shows page 00:13:25.089 --> 00:13:27.420 align:start position:0% changing tribes settled from shows page refreshes<00:13:25.420> types<00:13:25.779> which<00:13:26.200> has<00:13:26.410> no<00:13:26.650> affiliation 00:13:27.420 --> 00:13:27.430 align:start position:0% refreshes types which has no affiliation 00:13:27.430 --> 00:13:30.720 align:start position:0% refreshes types which has no affiliation both<00:13:28.240> conscious<00:13:28.780> the<00:13:29.620> delegation<00:13:30.310> changing 00:13:30.720 --> 00:13:30.730 align:start position:0% both conscious the delegation changing 00:13:30.730 --> 00:13:34.440 align:start position:0% both conscious the delegation changing types<00:13:31.560> which<00:13:33.000> provides<00:13:34.000> middle-aged 00:13:34.440 --> 00:13:34.450 align:start position:0% types which provides middle-aged 00:13:34.450 --> 00:13:38.940 align:start position:0% types which provides middle-aged attachment<00:13:35.140> and<00:13:36.070> issue<00:13:36.490> loss<00:13:36.880> use<00:13:37.950> different 00:13:38.940 --> 00:13:38.950 align:start position:0% attachment and issue loss use different 00:13:38.950 --> 00:13:39.840 align:start position:0% attachment and issue loss use different functionalities 00:13:39.840 --> 00:13:39.850 align:start position:0% functionalities 00:13:39.850 --> 00:13:43.050 align:start position:0% functionalities first<00:13:40.780> on<00:13:40.960> is<00:13:41.110> the<00:13:41.440> explanation<00:13:42.160> this<00:13:42.910> is 00:13:43.050 --> 00:13:43.060 align:start position:0% first on is the explanation this is 00:13:43.060 --> 00:13:45.270 align:start position:0% first on is the explanation this is provide<00:13:43.450> for<00:13:43.750> comparative<00:13:44.410> so<00:13:45.010> whole 00:13:45.270 --> 00:13:45.280 align:start position:0% provide for comparative so whole 00:13:45.280 --> 00:13:47.550 align:start position:0% provide for comparative so whole internal<00:13:45.730> transitions<00:13:46.300> will<00:13:46.570> be<00:13:46.750> bent<00:13:46.990> to<00:13:47.170> his 00:13:47.550 --> 00:13:47.560 align:start position:0% internal transitions will be bent to his 00:13:47.560 --> 00:13:52.190 align:start position:0% internal transitions will be bent to his worst<00:13:48.250> finish<00:13:49.710> and<00:13:50.710> those<00:13:51.010> functions<00:13:51.790> are 00:13:52.190 --> 00:13:52.200 align:start position:0% worst finish and those functions are 00:13:52.200 --> 00:13:56.160 align:start position:0% worst finish and those functions are also<00:13:53.200> provided<00:13:53.740> in<00:13:54.720> internal<00:13:55.720> thought<00:13:55.990> we 00:13:56.160 --> 00:13:56.170 align:start position:0% also provided in internal thought we 00:13:56.170 --> 00:13:59.130 align:start position:0% also provided in internal thought we separate<00:13:57.070> attention<00:13:57.460> spice<00:13:57.690> and<00:13:58.690> we<00:13:58.930> also 00:13:59.130 --> 00:13:59.140 align:start position:0% separate attention spice and we also 00:13:59.140 --> 00:14:01.440 align:start position:0% separate attention spice and we also have<00:13:59.530> two<00:13:59.740> functions<00:14:00.370> such<00:14:00.550> as<00:14:00.580> of<00:14:00.940> Qaddafi 00:14:01.440 --> 00:14:01.450 align:start position:0% have two functions such as of Qaddafi 00:14:01.450 --> 00:14:04.200 align:start position:0% have two functions such as of Qaddafi and<00:14:01.690> so<00:14:01.930> on<00:14:02.200> so<00:14:02.860> if<00:14:03.070> you're<00:14:03.220> not<00:14:03.339> work<00:14:03.670> if 00:14:04.200 --> 00:14:04.210 align:start position:0% and so on so if you're not work if 00:14:04.210 --> 00:14:07.170 align:start position:0% and so on so if you're not work if you're<00:14:04.330> interested<00:14:04.900> in<00:14:05.530> the<00:14:06.010> origin<00:14:06.070> price<00:14:06.580> we 00:14:07.170 --> 00:14:07.180 align:start position:0% you're interested in the origin price we 00:14:07.180 --> 00:14:08.970 align:start position:0% you're interested in the origin price we can<00:14:07.360> find<00:14:07.570> more<00:14:07.900> informations<00:14:08.560> in<00:14:08.770> our 00:14:08.970 --> 00:14:08.980 align:start position:0% can find more informations in our 00:14:08.980 --> 00:14:13.490 align:start position:0% can find more informations in our documentation<00:14:09.850> site<00:14:12.120> let's<00:14:13.120> talk<00:14:13.300> about 00:14:13.490 --> 00:14:13.500 align:start position:0% documentation site let's talk about 00:14:13.500 --> 00:14:17.340 align:start position:0% documentation site let's talk about provenance<00:14:15.420> in<00:14:16.420> this<00:14:16.570> chart<00:14:16.810> on<00:14:17.020> the<00:14:17.140> next 00:14:17.340 --> 00:14:17.350 align:start position:0% provenance in this chart on the next 00:14:17.350 --> 00:14:18.960 align:start position:0% provenance in this chart on the next date<00:14:17.470> these<00:14:17.650> issues 00:14:18.960 --> 00:14:18.970 align:start position:0% date these issues 00:14:18.970 --> 00:14:22.090 align:start position:0% date these issues Bogey's<00:14:19.990> built-in<00:14:20.990> super<00:14:21.080> smart<00:14:21.800> content 00:14:22.090 --> 00:14:22.100 align:start position:0% Bogey's built-in super smart content 00:14:22.100 --> 00:14:24.540 align:start position:0% Bogey's built-in super smart content deploying<00:14:22.580> and<00:14:23.150> smart<00:14:23.420> object<00:14:23.750> excision<00:14:24.320> and 00:14:24.540 --> 00:14:24.550 align:start position:0% deploying and smart object excision and 00:14:24.550 --> 00:14:27.100 align:start position:0% deploying and smart object excision and the<00:14:25.550> y-axis<00:14:26.000> shows<00:14:26.030> a<00:14:26.600> little<00:14:26.960> team 00:14:27.100 --> 00:14:27.110 align:start position:0% the y-axis shows a little team 00:14:27.110 --> 00:14:31.330 align:start position:0% the y-axis shows a little team exhibition<00:14:27.680> fight<00:14:27.860> over<00:14:28.400> legacy<00:14:29.980> as<00:14:30.980> you<00:14:31.160> can 00:14:31.330 --> 00:14:31.340 align:start position:0% exhibition fight over legacy as you can 00:14:31.340 --> 00:14:35.680 align:start position:0% exhibition fight over legacy as you can see<00:14:32.050> our<00:14:33.050> new<00:14:33.410> patient<00:14:33.830> ID<00:14:34.450> performs<00:14:35.450> well 00:14:35.680 --> 00:14:35.690 align:start position:0% see our new patient ID performs well 00:14:35.690 --> 00:14:38.110 align:start position:0% see our new patient ID performs well slightly<00:14:36.260> slower<00:14:36.560> than<00:14:36.590> the<00:14:37.130> legacy<00:14:37.580> image 00:14:38.110 --> 00:14:38.120 align:start position:0% slightly slower than the legacy image 00:14:38.120 --> 00:14:43.150 align:start position:0% slightly slower than the legacy image after<00:14:38.540> conviction<00:14:39.080> less<00:14:39.920> than<00:14:40.190> 10%<00:14:42.040> this<00:14:43.040> is 00:14:43.150 --> 00:14:43.160 align:start position:0% after conviction less than 10% this is 00:14:43.160 --> 00:14:45.210 align:start position:0% after conviction less than 10% this is due<00:14:43.340> to<00:14:43.370> the<00:14:43.640> doubling<00:14:44.300> coding<00:14:44.780> and 00:14:45.210 --> 00:14:45.220 align:start position:0% due to the doubling coding and 00:14:45.220 --> 00:14:49.090 align:start position:0% due to the doubling coding and rehabilitation<00:14:46.330> but<00:14:47.330> we<00:14:47.900> have<00:14:48.080> more<00:14:48.440> benefits 00:14:49.090 --> 00:14:49.100 align:start position:0% rehabilitation but we have more benefits 00:14:49.100 --> 00:14:51.370 align:start position:0% rehabilitation but we have more benefits from<00:14:49.970> something<00:14:50.360> is<00:14:50.450> visibility 00:14:51.370 --> 00:14:51.380 align:start position:0% from something is visibility 00:14:51.380 --> 00:14:55.030 align:start position:0% from something is visibility Esmond<00:14:51.830> which<00:14:52.550> means<00:14:52.820> we<00:14:52.970> provide<00:14:53.920> change<00:14:54.920> of 00:14:55.030 --> 00:14:55.040 align:start position:0% Esmond which means we provide change of 00:14:55.040 --> 00:14:57.010 align:start position:0% Esmond which means we provide change of Bernanke<00:14:55.550> and<00:14:55.880> bhakti<00:14:56.180> see<00:14:56.330> my<00:14:56.480> pencil<00:14:56.810> and 00:14:57.010 --> 00:14:57.020 align:start position:0% Bernanke and bhakti see my pencil and 00:14:57.020 --> 00:14:57.880 align:start position:0% Bernanke and bhakti see my pencil and reversed<00:14:57.440> key 00:14:57.880 --> 00:14:57.890 align:start position:0% reversed key 00:14:57.890 --> 00:15:03.370 align:start position:0% reversed key so<00:14:58.420> today<00:14:59.420> Washburn<00:14:59.990> visuality<00:15:00.980> ESMA<00:15:01.490> and<00:15:02.380> due 00:15:03.370 --> 00:15:03.380 align:start position:0% so today Washburn visuality ESMA and due 00:15:03.380 --> 00:15:07.240 align:start position:0% so today Washburn visuality ESMA and due to<00:15:03.500> the<00:15:04.360> time<00:15:05.360> information<00:15:06.020> we<00:15:06.500> can<00:15:06.680> Hospital 00:15:07.240 --> 00:15:07.250 align:start position:0% to the time information we can Hospital 00:15:07.250 --> 00:15:12.430 align:start position:0% to the time information we can Hospital on<00:15:07.670> disparities<00:15:08.150> so<00:15:08.690> if<00:15:09.320> we<00:15:09.410> had<00:15:09.590> more<00:15:11.440> planks 00:15:12.430 --> 00:15:12.440 align:start position:0% on disparities so if we had more planks 00:15:12.440 --> 00:15:14.980 align:start position:0% on disparities so if we had more planks for<00:15:12.710> functions<00:15:13.310> required<00:15:13.820> in<00:15:13.940> the<00:15:14.030> future<00:15:14.390> we 00:15:14.980 --> 00:15:14.990 align:start position:0% for functions required in the future we 00:15:14.990 --> 00:15:17.310 align:start position:0% for functions required in the future we can<00:15:15.140> easily<00:15:15.560> implement<00:15:16.190> those<00:15:16.550> family<00:15:16.970> crest 00:15:17.310 --> 00:15:17.320 align:start position:0% can easily implement those family crest 00:15:17.320 --> 00:15:20.920 align:start position:0% can easily implement those family crest without<00:15:18.320> curry<00:15:18.890> in<00:15:19.490> the<00:15:19.640> airsoft<00:15:19.880> world<00:15:20.030> and 00:15:20.920 --> 00:15:20.930 align:start position:0% without curry in the airsoft world and 00:15:20.930 --> 00:15:24.910 align:start position:0% without curry in the airsoft world and we<00:15:21.050> also<00:15:21.230> got<00:15:21.800> our<00:15:22.100> search<00:15:22.370> position<00:15:23.860> as<00:15:24.860> a 00:15:24.910 --> 00:15:24.920 align:start position:0% we also got our search position as a 00:15:24.920 --> 00:15:28.180 align:start position:0% we also got our search position as a family<00:15:25.460> data<00:15:25.700> data<00:15:26.000> we<00:15:26.530> as<00:15:27.530> of<00:15:27.680> September<00:15:28.040> this 00:15:28.180 --> 00:15:28.190 align:start position:0% family data data we as of September this 00:15:28.190 --> 00:15:31.060 align:start position:0% family data data we as of September this year<00:15:28.250> we<00:15:28.880> found<00:15:29.090> that<00:15:29.300> there<00:15:29.660> are<00:15:29.710> 75<00:15:30.710> billion 00:15:31.060 --> 00:15:31.070 align:start position:0% year we found that there are 75 billion 00:15:31.070 --> 00:15:34.990 align:start position:0% year we found that there are 75 billion users<00:15:31.660> billion<00:15:32.660> neurons<00:15:32.990> in<00:15:33.410> this<00:15:33.800> area<00:15:34.100> so<00:15:34.700> if 00:15:34.990 --> 00:15:35.000 align:start position:0% users billion neurons in this area so if 00:15:35.000 --> 00:15:37.990 align:start position:0% users billion neurons in this area so if we<00:15:35.150> have<00:15:35.330> five<00:15:35.960> information<00:15:36.560> internet<00:15:37.250> then 00:15:37.990 --> 00:15:38.000 align:start position:0% we have five information internet then 00:15:38.000 --> 00:15:41.530 align:start position:0% we have five information internet then we<00:15:38.330> get<00:15:38.840> one<00:15:39.170> type<00:15:39.710> of<00:15:39.890> red<00:15:40.130> purple<00:15:40.790> advance 00:15:41.530 --> 00:15:41.540 align:start position:0% we get one type of red purple advance 00:15:41.540 --> 00:15:46.120 align:start position:0% we get one type of red purple advance this<00:15:42.440> case<00:15:42.740> are<00:15:43.010> sent<00:15:43.250> five<00:15:43.460> megabytes<00:15:44.450> but<00:15:45.130> we 00:15:46.120 --> 00:15:46.130 align:start position:0% this case are sent five megabytes but we 00:15:46.130 --> 00:15:49.780 align:start position:0% this case are sent five megabytes but we can<00:15:46.430> reduce<00:15:47.350> 64<00:15:48.350> bytes<00:15:48.590> for<00:15:49.010> us 00:15:49.780 --> 00:15:49.790 align:start position:0% can reduce 64 bytes for us 00:15:49.790 --> 00:15:53.080 align:start position:0% can reduce 64 bytes for us as<00:15:50.030> you<00:15:50.210> can<00:15:50.360> see<00:15:50.570> Weald<00:15:51.850> routine<00:15:52.850> routine 00:15:53.080 --> 00:15:53.090 align:start position:0% as you can see Weald routine routine 00:15:53.090 --> 00:15:55.810 align:start position:0% as you can see Weald routine routine cottage<00:15:53.930> for<00:15:54.470> those<00:15:54.650> are<00:15:54.950> fixed<00:15:55.550> up 00:15:55.810 --> 00:15:55.820 align:start position:0% cottage for those are fixed up 00:15:55.820 --> 00:16:02.140 align:start position:0% cottage for those are fixed up Pittsburgh<00:15:56.780> parts<00:15:57.730> if<00:15:58.730> we<00:16:00.130> assume<00:16:01.130> that<00:16:01.160> US 00:16:02.140 --> 00:16:02.150 align:start position:0% Pittsburgh parts if we assume that US 00:16:02.150 --> 00:16:05.620 align:start position:0% Pittsburgh parts if we assume that US states<00:16:02.480> of<00:16:02.690> a<00:16:02.870> percent<00:16:03.350> of<00:16:03.530> total<00:16:03.910> income<00:16:04.910> then 00:16:05.620 --> 00:16:05.630 align:start position:0% states of a percent of total income then 00:16:05.630 --> 00:16:10.750 align:start position:0% states of a percent of total income then we<00:16:05.780> can<00:16:05.990> reduce<00:16:07.090> 3.8<00:16:08.090> device<00:16:08.630> rosters<00:16:09.590> post<00:16:09.920> it 00:16:10.750 --> 00:16:10.760 align:start position:0% we can reduce 3.8 device rosters post it 00:16:10.760 --> 00:16:13.450 align:start position:0% we can reduce 3.8 device rosters post it is<00:16:10.910> obvious<00:16:11.720> we<00:16:12.080> can<00:16:12.350> get<00:16:12.560> massive<00:16:12.950> masters 00:16:13.450 --> 00:16:13.460 align:start position:0% is obvious we can get massive masters 00:16:13.460 --> 00:16:17.860 align:start position:0% is obvious we can get massive masters position<00:16:15.970> so<00:16:16.970> let's<00:16:17.270> summarize<00:16:17.510> my 00:16:17.860 --> 00:16:17.870 align:start position:0% position so let's summarize my 00:16:17.870 --> 00:16:21.160 align:start position:0% position so let's summarize my presentation<00:16:18.850> we<00:16:19.850> found<00:16:20.120> several<00:16:20.600> solid 00:16:21.160 --> 00:16:21.170 align:start position:0% presentation we found several solid 00:16:21.170 --> 00:16:23.960 align:start position:0% presentation we found several solid limitations<00:16:22.270> such<00:16:23.270> as 00:16:23.960 --> 00:16:23.970 align:start position:0% limitations such as 00:16:23.970 --> 00:16:27.410 align:start position:0% limitations such as a<00:16:24.470> little<00:16:25.470> panicky<00:16:26.070> and<00:16:26.400> the<00:16:26.670> robot<00:16:26.970> ASIMO<00:16:27.210> has 00:16:27.410 --> 00:16:27.420 align:start position:0% a little panicky and the robot ASIMO has 00:16:27.420 --> 00:16:32.420 align:start position:0% a little panicky and the robot ASIMO has menthol<00:16:27.900> and<00:16:28.940> we<00:16:30.080> find<00:16:31.080> solutions<00:16:31.430> by 00:16:32.420 --> 00:16:32.430 align:start position:0% menthol and we find solutions by 00:16:32.430 --> 00:16:35.000 align:start position:0% menthol and we find solutions by extending<00:16:33.180> across<00:16:33.960> modern<00:16:34.410> and<00:16:34.830> traditional 00:16:35.000 --> 00:16:35.010 align:start position:0% extending across modern and traditional 00:16:35.010 --> 00:16:39.920 align:start position:0% extending across modern and traditional more<00:16:37.040> also<00:16:38.040> to<00:16:38.670> to<00:16:38.820> change<00:16:39.120> of<00:16:39.330> this<00:16:39.510> and 00:16:39.920 --> 00:16:39.930 align:start position:0% more also to to change of this and 00:16:39.930 --> 00:16:42.650 align:start position:0% more also to to change of this and mothers<00:16:40.350> we<00:16:40.950> should<00:16:41.220> change<00:16:41.670> the<00:16:42.000> treatment 00:16:42.650 --> 00:16:42.660 align:start position:0% mothers we should change the treatment 00:16:42.660 --> 00:16:45.410 align:start position:0% mothers we should change the treatment Fishman<00:16:43.590> with<00:16:43.860> chief<00:16:44.040> our<00:16:44.280> sleds<00:16:44.670> be<00:16:44.880> overhead 00:16:45.410 --> 00:16:45.420 align:start position:0% Fishman with chief our sleds be overhead 00:16:45.420 --> 00:16:49.960 align:start position:0% Fishman with chief our sleds be overhead compared<00:16:45.960> to<00:16:46.080> Eternity<00:16:47.060> but<00:16:48.060> we<00:16:48.210> get<00:16:48.360> trailer 00:16:49.960 --> 00:16:49.970 align:start position:0% compared to Eternity but we get trailer 00:16:49.970 --> 00:16:53.360 align:start position:0% compared to Eternity but we get trailer there's<00:16:50.970> essentially<00:16:51.660> the<00:16:52.590> illusion<00:16:52.890> of<00:16:52.980> mass 00:16:53.360 --> 00:16:53.370 align:start position:0% there's essentially the illusion of mass 00:16:53.370 --> 00:16:56.530 align:start position:0% there's essentially the illusion of mass delusion<00:16:53.610> but<00:16:54.390> we<00:16:54.570> can<00:16:54.840> get<00:16:55.050> more<00:16:55.260> penalties 00:16:56.530 --> 00:16:56.540 align:start position:0% delusion but we can get more penalties 00:16:56.540 --> 00:17:00.260 align:start position:0% delusion but we can get more penalties intro<00:16:57.540> is<00:16:57.870> adenosine<00:16:58.560> extensibility<00:16:59.400> and<00:17:00.180> we 00:17:00.260 --> 00:17:00.270 align:start position:0% intro is adenosine extensibility and we 00:17:00.270 --> 00:17:04.490 align:start position:0% intro is adenosine extensibility and we also<00:17:00.390> reduce<00:17:00.930> search<00:17:01.590> cost<00:17:03.020> so<00:17:04.020> I<00:17:04.050> hope<00:17:04.470> that 00:17:04.490 --> 00:17:04.500 align:start position:0% also reduce search cost so I hope that 00:17:04.500 --> 00:17:09.290 align:start position:0% also reduce search cost so I hope that this<00:17:05.329> distinction<00:17:06.329> at<00:17:06.720> least<00:17:06.930> do<00:17:07.970> motors<00:17:08.970> can 00:17:09.290 --> 00:17:09.300 align:start position:0% this distinction at least do motors can 00:17:09.300 --> 00:17:11.290 align:start position:0% this distinction at least do motors can be<00:17:09.360> applicable<00:17:09.930> to<00:17:10.079> other<00:17:10.470> different 00:17:11.290 --> 00:17:11.300 align:start position:0% be applicable to other different 00:17:11.300 --> 00:17:17.270 align:start position:0% be applicable to other different approaches<00:17:12.300> for<00:17:12.329> sale<00:17:13.050> staff<00:17:16.070> okay 00:17:17.270 --> 00:17:17.280 align:start position:0% approaches for sale staff okay 00:17:17.280 --> 00:17:22.100 align:start position:0% approaches for sale staff okay we<00:17:17.940> always<00:17:18.360> welcome<00:17:18.900> to<00:17:19.940> contribute<00:17:20.940> our<00:17:21.120> open 00:17:22.100 --> 00:17:22.110 align:start position:0% we always welcome to contribute our open 00:17:22.110 --> 00:17:23.810 align:start position:0% we always welcome to contribute our open source<00:17:22.290> project<00:17:22.680> waiting<00:17:23.070> as<00:17:23.370> you<00:17:23.520> can<00:17:23.699> see 00:17:23.810 --> 00:17:23.820 align:start position:0% source project waiting as you can see 00:17:23.820 --> 00:17:25.579 align:start position:0% source project waiting as you can see over<00:17:23.940> the<00:17:24.390> kitchen<00:17:24.540> table<00:17:24.839> our<00:17:25.020> sauce<00:17:25.260> going 00:17:25.579 --> 00:17:25.589 align:start position:0% over the kitchen table our sauce going 00:17:25.589 --> 00:17:28.270 align:start position:0% over the kitchen table our sauce going to<00:17:25.680> it<00:17:25.829> aside<00:17:26.160> and<00:17:26.699> cannot<00:17:27.390> find<00:17:27.690> some<00:17:28.020> more 00:17:28.270 --> 00:17:28.280 align:start position:0% to it aside and cannot find some more 00:17:28.280 --> 00:17:30.440 align:start position:0% to it aside and cannot find some more information<00:17:29.280> about<00:17:29.430> Clinton<00:17:30.030> in<00:17:30.270> the 00:17:30.440 --> 00:17:30.450 align:start position:0% information about Clinton in the 00:17:30.450 --> 00:17:33.050 align:start position:0% information about Clinton in the documentation<00:17:30.870> site<00:17:31.310> and<00:17:32.310> you<00:17:32.490> can<00:17:32.550> see<00:17:32.760> the 00:17:33.050 --> 00:17:33.060 align:start position:0% documentation site and you can see the 00:17:33.060 --> 00:17:35.450 align:start position:0% documentation site and you can see the right<00:17:33.210> hand<00:17:33.390> side<00:17:33.600> there's<00:17:33.900> a<00:17:33.990> cure<00:17:34.320> for<00:17:34.460> what 00:17:35.450 --> 00:17:35.460 align:start position:0% right hand side there's a cure for what 00:17:35.460 --> 00:17:38.630 align:start position:0% right hand side there's a cure for what is<00:17:35.730> what<00:17:36.000> the<00:17:36.630> user<00:17:36.960> should<00:17:37.130> wear<00:17:38.130> to<00:17:38.370> a<00:17:38.400> fish 00:17:38.630 --> 00:17:38.640 align:start position:0% is what the user should wear to a fish 00:17:38.640 --> 00:17:42.110 align:start position:0% is what the user should wear to a fish dip<00:17:38.850> in<00:17:39.690> the<00:17:39.810> last<00:17:39.960> slide<00:17:40.230> you<00:17:41.160> can<00:17:41.340> find<00:17:41.610> my 00:17:42.110 --> 00:17:42.120 align:start position:0% dip in the last slide you can find my 00:17:42.120 --> 00:17:44.900 align:start position:0% dip in the last slide you can find my email<00:17:42.390> address<00:17:42.930> to<00:17:43.170> film<00:17:43.380> any<00:17:43.560> more<00:17:44.370> questions 00:17:44.900 --> 00:17:44.910 align:start position:0% email address to film any more questions 00:17:44.910 --> 00:17:49.130 align:start position:0% email address to film any more questions and<00:17:45.540> please<00:17:45.930> ask<00:17:46.740> me<00:17:47.100> yes<00:17:47.730> mister<00:17:48.390> even 00:17:49.130 --> 00:17:49.140 align:start position:0% and please ask me yes mister even 00:17:49.140 --> 00:17:51.160 align:start position:0% and please ask me yes mister even madness 00:17:51.160 --> 00:17:51.170 align:start position:0% madness 00:17:51.170 --> 00:17:55.270 align:start position:0% madness this<00:17:51.530> is<00:17:53.350> another<00:17:54.350> thing<00:17:54.560> I'll<00:17:54.770> talk<00:17:54.980> about<00:17:55.100> is 00:17:55.270 --> 00:17:55.280 align:start position:0% this is another thing I'll talk about is 00:17:55.280 --> 00:17:59.020 align:start position:0% this is another thing I'll talk about is that<00:17:55.520> there's<00:17:56.000> some<00:17:56.240> 20<00:17:57.200> stickers<00:17:57.560> and<00:17:58.030> pegs 00:17:59.020 --> 00:17:59.030 align:start position:0% that there's some 20 stickers and pegs 00:17:59.030 --> 00:18:02.710 align:start position:0% that there's some 20 stickers and pegs just<00:17:59.360> in<00:18:00.350> front<00:18:00.590> of<00:18:00.740> the<00:18:00.950> entry<00:18:01.700> you<00:18:02.240> can<00:18:02.270> be 00:18:02.710 --> 00:18:02.720 align:start position:0% just in front of the entry you can be 00:18:02.720 --> 00:18:06.540 align:start position:0% just in front of the entry you can be interesting<00:18:03.290> in<00:18:03.380> that<00:18:03.410> you<00:18:03.560> can<00:18:03.770> take<00:18:03.800> some 00:18:06.540 --> 00:18:06.550 align:start position:0% interesting in that you can take some 00:18:06.550 --> 00:18:10.580 align:start position:0% interesting in that you can take some medication 00:18:10.580 --> 00:18:10.590 align:start position:0% 00:18:10.590 --> 00:18:16.980 align:start position:0% [Applause]