WEBVTT Kind: captions Language: en 00:00:00.060 --> 00:00:01.790 align:start position:0% and<00:00:00.240> today<00:00:00.840> I<00:00:00.900> want<00:00:01.079> to<00:00:01.140> talk<00:00:01.290> about<00:00:01.439> browser 00:00:01.790 --> 00:00:01.800 align:start position:0% and today I want to talk about browser 00:00:01.800 --> 00:00:04.730 align:start position:0% and today I want to talk about browser 3.0<00:00:02.550> how<00:00:02.790> to<00:00:02.850> build<00:00:03.149> secure<00:00:03.870> secure<00:00:04.230> web<00:00:04.529> 3 00:00:04.730 --> 00:00:04.740 align:start position:0% 3.0 how to build secure secure web 3 00:00:04.740 --> 00:00:06.740 align:start position:0% 3.0 how to build secure secure web 3 clients<00:00:05.220> and<00:00:05.520> I<00:00:05.910> would<00:00:06.029> like<00:00:06.180> to<00:00:06.330> start<00:00:06.569> with 00:00:06.740 --> 00:00:06.750 align:start position:0% clients and I would like to start with 00:00:06.750 --> 00:00:10.759 align:start position:0% clients and I would like to start with this<00:00:07.040> quote<00:00:08.929> there<00:00:09.929> are<00:00:09.960> two<00:00:10.200> ages<00:00:10.500> of<00:00:10.650> the 00:00:10.759 --> 00:00:10.769 align:start position:0% this quote there are two ages of the 00:00:10.769 --> 00:00:15.289 align:start position:0% this quote there are two ages of the internet<00:00:11.160> before<00:00:11.610> mosaic<00:00:12.210> and<00:00:12.420> after<00:00:14.299> the 00:00:15.289 --> 00:00:15.299 align:start position:0% internet before mosaic and after the 00:00:15.299 --> 00:00:17.210 align:start position:0% internet before mosaic and after the combination<00:00:15.870> of<00:00:15.960> protocols<00:00:16.560> with<00:00:16.920> a<00:00:16.949> browser 00:00:17.210 --> 00:00:17.220 align:start position:0% combination of protocols with a browser 00:00:17.220 --> 00:00:19.730 align:start position:0% combination of protocols with a browser which<00:00:18.000> provided<00:00:18.390> a<00:00:18.539> great<00:00:18.690> interface<00:00:19.020> proved 00:00:19.730 --> 00:00:19.740 align:start position:0% which provided a great interface proved 00:00:19.740 --> 00:00:22.880 align:start position:0% which provided a great interface proved explosive<00:00:20.400> in<00:00:20.609> 24<00:00:21.570> months<00:00:21.900> the<00:00:22.080> web<00:00:22.560> has<00:00:22.740> gone 00:00:22.880 --> 00:00:22.890 align:start position:0% explosive in 24 months the web has gone 00:00:22.890 --> 00:00:24.679 align:start position:0% explosive in 24 months the web has gone from<00:00:23.070> being<00:00:23.279> unknown<00:00:23.699> to<00:00:24.269> absolutely 00:00:24.679 --> 00:00:24.689 align:start position:0% from being unknown to absolutely 00:00:24.689 --> 00:00:27.439 align:start position:0% from being unknown to absolutely ubiquitous<00:00:25.050> and<00:00:25.609> I<00:00:26.609> like<00:00:26.849> this<00:00:27.000> quote<00:00:27.210> because 00:00:27.439 --> 00:00:27.449 align:start position:0% ubiquitous and I like this quote because 00:00:27.449 --> 00:00:28.849 align:start position:0% ubiquitous and I like this quote because I<00:00:27.630> think<00:00:27.779> it's<00:00:28.050> important<00:00:28.590> to<00:00:28.650> remind 00:00:28.849 --> 00:00:28.859 align:start position:0% I think it's important to remind 00:00:28.859 --> 00:00:30.950 align:start position:0% I think it's important to remind ourselves<00:00:29.070> that<00:00:29.460> the<00:00:30.119> Internet<00:00:30.480> is<00:00:30.510> not<00:00:30.779> so 00:00:30.950 --> 00:00:30.960 align:start position:0% ourselves that the Internet is not so 00:00:30.960 --> 00:00:33.950 align:start position:0% ourselves that the Internet is not so old<00:00:31.109> and<00:00:31.410> less<00:00:32.099> than<00:00:32.250> 25<00:00:32.700> years<00:00:32.850> ago<00:00:33.000> no<00:00:33.840> one 00:00:33.950 --> 00:00:33.960 align:start position:0% old and less than 25 years ago no one 00:00:33.960 --> 00:00:35.569 align:start position:0% old and less than 25 years ago no one was<00:00:34.110> really<00:00:34.350> talking<00:00:34.530> about<00:00:34.739> the<00:00:34.980> latest<00:00:35.160> web 00:00:35.569 --> 00:00:35.579 align:start position:0% was really talking about the latest web 00:00:35.579 --> 00:00:37.270 align:start position:0% was really talking about the latest web development<00:00:36.000> framework<00:00:36.480> trends 00:00:37.270 --> 00:00:37.280 align:start position:0% development framework trends 00:00:37.280 --> 00:00:40.010 align:start position:0% development framework trends no<00:00:38.280> one<00:00:38.399> was<00:00:38.550> sharing<00:00:39.030> stuff<00:00:39.270> on<00:00:39.450> social<00:00:39.660> media 00:00:40.010 --> 00:00:40.020 align:start position:0% no one was sharing stuff on social media 00:00:40.020 --> 00:00:42.139 align:start position:0% no one was sharing stuff on social media because<00:00:41.010> the<00:00:41.129> internet<00:00:41.399> didn't<00:00:41.640> really<00:00:41.820> exist 00:00:42.139 --> 00:00:42.149 align:start position:0% because the internet didn't really exist 00:00:42.149 --> 00:00:44.270 align:start position:0% because the internet didn't really exist and<00:00:42.930> people<00:00:43.110> were<00:00:43.320> more<00:00:43.500> concerned<00:00:43.950> about 00:00:44.270 --> 00:00:44.280 align:start position:0% and people were more concerned about 00:00:44.280 --> 00:00:46.610 align:start position:0% and people were more concerned about like<00:00:44.910> infrastructure<00:00:45.690> things<00:00:45.899> and<00:00:46.140> protocols 00:00:46.610 --> 00:00:46.620 align:start position:0% like infrastructure things and protocols 00:00:46.620 --> 00:00:49.639 align:start position:0% like infrastructure things and protocols and<00:00:46.829> how<00:00:46.890> to<00:00:47.010> scare<00:00:47.879> this<00:00:48.120> thing<00:00:48.809> and<00:00:49.020> only<00:00:49.620> a 00:00:49.639 --> 00:00:49.649 align:start position:0% and how to scare this thing and only a 00:00:49.649 --> 00:00:51.799 align:start position:0% and how to scare this thing and only a very<00:00:49.980> small<00:00:50.700> group<00:00:50.850> of<00:00:51.000> people<00:00:51.210> actually<00:00:51.480> had 00:00:51.799 --> 00:00:51.809 align:start position:0% very small group of people actually had 00:00:51.809 --> 00:00:54.110 align:start position:0% very small group of people actually had the<00:00:52.050> the<00:00:52.530> knowledge<00:00:52.739> and<00:00:53.070> the<00:00:53.190> tools<00:00:53.370> the 00:00:54.110 --> 00:00:54.120 align:start position:0% the the knowledge and the tools the 00:00:54.120 --> 00:00:56.479 align:start position:0% the the knowledge and the tools the money<00:00:54.329> the<00:00:54.570> resources<00:00:54.719> in<00:00:55.199> general<00:00:55.230> to<00:00:55.860> access 00:00:56.479 --> 00:00:56.489 align:start position:0% money the resources in general to access 00:00:56.489 --> 00:00:59.689 align:start position:0% money the resources in general to access the<00:00:56.640> Internet<00:00:57.829> so<00:00:58.829> it<00:00:58.920> was<00:00:59.039> very<00:00:59.250> similar<00:00:59.520> to 00:00:59.689 --> 00:00:59.699 align:start position:0% the Internet so it was very similar to 00:00:59.699 --> 00:01:02.720 align:start position:0% the Internet so it was very similar to what<00:00:59.820> we<00:01:00.059> have<00:01:00.149> with<00:01:00.329> if<00:01:00.660> you<00:01:00.840> know<00:01:01.609> but<00:01:02.609> then 00:01:02.720 --> 00:01:02.730 align:start position:0% what we have with if you know but then 00:01:02.730 --> 00:01:05.240 align:start position:0% what we have with if you know but then something<00:01:03.180> something<00:01:03.960> happened<00:01:04.080> the<00:01:05.010> browser 00:01:05.240 --> 00:01:05.250 align:start position:0% something something happened the browser 00:01:05.250 --> 00:01:07.399 align:start position:0% something something happened the browser was<00:01:05.519> introduced<00:01:06.030> and<00:01:06.299> now<00:01:06.840> people<00:01:07.229> actually 00:01:07.399 --> 00:01:07.409 align:start position:0% was introduced and now people actually 00:01:07.409 --> 00:01:10.490 align:start position:0% was introduced and now people actually could<00:01:07.860> access<00:01:08.580> the<00:01:08.729> internet<00:01:09.150> and<00:01:09.360> then<00:01:10.320> mass 00:01:10.490 --> 00:01:10.500 align:start position:0% could access the internet and then mass 00:01:10.500 --> 00:01:12.200 align:start position:0% could access the internet and then mass adoption<00:01:10.740> started<00:01:11.340> and<00:01:11.490> we<00:01:11.909> will<00:01:12.000> probably 00:01:12.200 --> 00:01:12.210 align:start position:0% adoption started and we will probably 00:01:12.210 --> 00:01:15.350 align:start position:0% adoption started and we will probably see<00:01:12.960> this<00:01:13.159> once<00:01:14.159> the<00:01:14.369> scalability<00:01:15.060> and 00:01:15.350 --> 00:01:15.360 align:start position:0% see this once the scalability and 00:01:15.360 --> 00:01:17.780 align:start position:0% see this once the scalability and protocol<00:01:15.869> problems<00:01:16.350> are<00:01:16.530> solved<00:01:16.890> and<00:01:17.130> that 00:01:17.780 --> 00:01:17.790 align:start position:0% protocol problems are solved and that 00:01:17.790 --> 00:01:19.370 align:start position:0% protocol problems are solved and that there's<00:01:18.150> some<00:01:18.360> kind<00:01:18.570> of<00:01:18.630> message<00:01:18.960> option<00:01:19.229> for 00:01:19.370 --> 00:01:19.380 align:start position:0% there's some kind of message option for 00:01:19.380 --> 00:01:22.100 align:start position:0% there's some kind of message option for a<00:01:19.409> theme<00:01:19.619> as<00:01:19.830> well<00:01:19.979> and<00:01:20.220> then<00:01:20.640> some<00:01:20.909> some<00:01:21.659> funny 00:01:22.100 --> 00:01:22.110 align:start position:0% a theme as well and then some some funny 00:01:22.110 --> 00:01:23.840 align:start position:0% a theme as well and then some some funny funny<00:01:22.590> things<00:01:22.860> can<00:01:23.100> happen<00:01:23.220> and<00:01:23.430> I<00:01:23.580> want<00:01:23.729> to 00:01:23.840 --> 00:01:23.850 align:start position:0% funny things can happen and I want to 00:01:23.850 --> 00:01:26.480 align:start position:0% funny things can happen and I want to show<00:01:24.030> you<00:01:24.090> how<00:01:24.299> this<00:01:24.420> looks<00:01:24.479> like<00:01:25.250> so<00:01:26.250> we<00:01:26.400> are 00:01:26.480 --> 00:01:26.490 align:start position:0% show you how this looks like so we are 00:01:26.490 --> 00:01:29.960 align:start position:0% show you how this looks like so we are in<00:01:26.549> the<00:01:26.640> year<00:01:26.820> 1994<00:01:27.680> its<00:01:28.680> December<00:01:29.009> 1994<00:01:29.729> and 00:01:29.960 --> 00:01:29.970 align:start position:0% in the year 1994 its December 1994 and 00:01:29.970 --> 00:01:32.679 align:start position:0% in the year 1994 its December 1994 and Netscape<00:01:30.180> Navigator<00:01:30.329> 1.0<00:01:31.320> was<00:01:31.470> released<00:01:31.500> and 00:01:32.679 --> 00:01:32.689 align:start position:0% Netscape Navigator 1.0 was released and 00:01:32.689 --> 00:01:35.030 align:start position:0% Netscape Navigator 1.0 was released and suddenly<00:01:33.689> it<00:01:33.930> is<00:01:34.140> easy<00:01:34.409> to<00:01:34.650> access<00:01:34.920> the 00:01:35.030 --> 00:01:35.040 align:start position:0% suddenly it is easy to access the 00:01:35.040 --> 00:01:36.859 align:start position:0% suddenly it is easy to access the Internet<00:01:35.430> and<00:01:35.610> then<00:01:35.909> this<00:01:36.030> happens<00:01:36.420> everyone 00:01:36.859 --> 00:01:36.869 align:start position:0% Internet and then this happens everyone 00:01:36.869 --> 00:01:38.870 align:start position:0% Internet and then this happens everyone wants<00:01:37.079> to<00:01:37.140> go<00:01:37.320> online<00:01:37.500> everyone<00:01:38.189> wants<00:01:38.850> to 00:01:38.870 --> 00:01:38.880 align:start position:0% wants to go online everyone wants to 00:01:38.880 --> 00:01:41.210 align:start position:0% wants to go online everyone wants to experience<00:01:39.390> this<00:01:39.689> thing<00:01:40.200> before<00:01:40.560> we<00:01:40.590> had<00:01:40.799> TV 00:01:41.210 --> 00:01:41.220 align:start position:0% experience this thing before we had TV 00:01:41.220 --> 00:01:42.859 align:start position:0% experience this thing before we had TV shows<00:01:41.460> that<00:01:41.970> would<00:01:42.150> make<00:01:42.299> fun<00:01:42.570> of<00:01:42.630> the 00:01:42.859 --> 00:01:42.869 align:start position:0% shows that would make fun of the 00:01:42.869 --> 00:01:44.270 align:start position:0% shows that would make fun of the internet<00:01:43.259> that<00:01:43.409> would<00:01:43.500> laugh<00:01:43.740> about<00:01:43.920> it<00:01:44.220> and 00:01:44.270 --> 00:01:44.280 align:start position:0% internet that would laugh about it and 00:01:44.280 --> 00:01:47.359 align:start position:0% internet that would laugh about it and suddenly<00:01:44.759> it<00:01:45.090> is<00:01:45.210> a<00:01:45.240> thing<00:01:45.570> and<00:01:46.369> someone 00:01:47.359 --> 00:01:47.369 align:start position:0% suddenly it is a thing and someone 00:01:47.369 --> 00:01:48.920 align:start position:0% suddenly it is a thing and someone noticed<00:01:47.700> this<00:01:47.909> and<00:01:48.180> then<00:01:48.540> someone<00:01:48.810> is 00:01:48.920 --> 00:01:48.930 align:start position:0% noticed this and then someone is 00:01:48.930 --> 00:01:51.440 align:start position:0% noticed this and then someone is Microsoft<00:01:49.759> and<00:01:50.759> when<00:01:50.880> they<00:01:51.000> saw<00:01:51.240> what 00:01:51.440 --> 00:01:51.450 align:start position:0% Microsoft and when they saw what 00:01:51.450 --> 00:01:53.450 align:start position:0% Microsoft and when they saw what happened<00:01:51.810> they<00:01:52.110> got<00:01:52.259> really<00:01:52.409> scared<00:01:52.770> because 00:01:53.450 --> 00:01:53.460 align:start position:0% happened they got really scared because 00:01:53.460 --> 00:01:55.249 align:start position:0% happened they got really scared because they<00:01:53.790> were<00:01:53.850> really<00:01:54.119> the<00:01:54.270> dominant<00:01:54.840> force<00:01:55.079> they 00:01:55.249 --> 00:01:55.259 align:start position:0% they were really the dominant force they 00:01:55.259 --> 00:01:56.630 align:start position:0% they were really the dominant force they were<00:01:55.380> completely<00:01:55.770> completely<00:01:56.130> owning<00:01:56.399> the 00:01:56.630 --> 00:01:56.640 align:start position:0% were completely completely owning the 00:01:56.640 --> 00:02:00.469 align:start position:0% were completely completely owning the home<00:01:56.850> computer<00:01:57.060> market<00:01:58.250> and<00:01:59.250> this<00:01:59.820> was<00:02:00.000> a<00:02:00.030> big 00:02:00.469 --> 00:02:00.479 align:start position:0% home computer market and this was a big 00:02:00.479 --> 00:02:03.980 align:start position:0% home computer market and this was a big shock<00:02:00.509> for<00:02:00.869> them<00:02:01.049> so<00:02:01.950> in<00:02:02.159> July<00:02:02.360> 1995<00:02:03.360> they 00:02:03.980 --> 00:02:03.990 align:start position:0% shock for them so in July 1995 they 00:02:03.990 --> 00:02:05.959 align:start position:0% shock for them so in July 1995 they released<00:02:04.020> Windows<00:02:04.860> 95<00:02:05.250> and<00:02:05.729> it<00:02:05.820> came 00:02:05.959 --> 00:02:05.969 align:start position:0% released Windows 95 and it came 00:02:05.969 --> 00:02:08.359 align:start position:0% released Windows 95 and it came pre-installed<00:02:06.689> with<00:02:07.320> Internet<00:02:07.710> Explorer<00:02:08.099> as 00:02:08.359 --> 00:02:08.369 align:start position:0% pre-installed with Internet Explorer as 00:02:08.369 --> 00:02:11.449 align:start position:0% pre-installed with Internet Explorer as the<00:02:08.670> default<00:02:09.000> browser<00:02:09.090> and<00:02:10.190> some<00:02:11.190> of<00:02:11.370> you 00:02:11.449 --> 00:02:11.459 align:start position:0% the default browser and some of you 00:02:11.459 --> 00:02:12.979 align:start position:0% the default browser and some of you might<00:02:11.640> say<00:02:11.879> hey<00:02:12.000> that's<00:02:12.209> good<00:02:12.420> that's<00:02:12.810> some 00:02:12.979 --> 00:02:12.989 align:start position:0% might say hey that's good that's some 00:02:12.989 --> 00:02:14.589 align:start position:0% might say hey that's good that's some horrific<00:02:13.170> on 00:02:14.589 --> 00:02:14.599 align:start position:0% horrific on 00:02:14.599 --> 00:02:16.760 align:start position:0% horrific on but<00:02:15.599> it<00:02:15.690> was<00:02:15.810> pretty<00:02:15.989> much<00:02:16.080> illegal<00:02:16.620> and 00:02:16.760 --> 00:02:16.770 align:start position:0% but it was pretty much illegal and 00:02:16.770 --> 00:02:19.460 align:start position:0% but it was pretty much illegal and recall<00:02:17.370> this<00:02:17.550> browser<00:02:17.849> was<00:02:18.150> 1.0<00:02:18.810> and<00:02:19.080> it's<00:02:19.319> not 00:02:19.460 --> 00:02:19.470 align:start position:0% recall this browser was 1.0 and it's not 00:02:19.470 --> 00:02:21.860 align:start position:0% recall this browser was 1.0 and it's not called<00:02:19.950> the<00:02:20.250> browser<00:02:20.520> disagreement<00:02:21.510> of<00:02:21.599> fight 00:02:21.860 --> 00:02:21.870 align:start position:0% called the browser disagreement of fight 00:02:21.870 --> 00:02:24.530 align:start position:0% called the browser disagreement of fight no<00:02:22.470> it's<00:02:22.620> called<00:02:22.800> browser<00:02:23.040> Wars<00:02:23.370> because<00:02:24.300> a 00:02:24.530 --> 00:02:24.540 align:start position:0% no it's called browser Wars because a 00:02:24.540 --> 00:02:26.690 align:start position:0% no it's called browser Wars because a big<00:02:24.900> corporation<00:02:25.380> used<00:02:25.860> all<00:02:26.130> the<00:02:26.250> energy<00:02:26.670> and 00:02:26.690 --> 00:02:26.700 align:start position:0% big corporation used all the energy and 00:02:26.700 --> 00:02:28.940 align:start position:0% big corporation used all the energy and all<00:02:27.030> available<00:02:27.239> resources<00:02:27.720> to<00:02:28.560> destroy<00:02:28.920> a 00:02:28.940 --> 00:02:28.950 align:start position:0% all available resources to destroy a 00:02:28.950 --> 00:02:31.220 align:start position:0% all available resources to destroy a potential<00:02:29.550> threat<00:02:29.790> the<00:02:30.750> internet<00:02:31.080> was 00:02:31.220 --> 00:02:31.230 align:start position:0% potential threat the internet was 00:02:31.230 --> 00:02:33.170 align:start position:0% potential threat the internet was becoming<00:02:31.380> a<00:02:31.739> thing<00:02:31.920> browsers<00:02:32.340> became<00:02:32.790> too<00:02:33.000> big 00:02:33.170 --> 00:02:33.180 align:start position:0% becoming a thing browsers became too big 00:02:33.180 --> 00:02:35.420 align:start position:0% becoming a thing browsers became too big so<00:02:33.780> they<00:02:33.810> were<00:02:33.989> going<00:02:34.349> after<00:02:34.560> developers<00:02:35.310> on 00:02:35.420 --> 00:02:35.430 align:start position:0% so they were going after developers on 00:02:35.430 --> 00:02:37.550 align:start position:0% so they were going after developers on an<00:02:35.550> individual<00:02:36.060> basis<00:02:36.480> they<00:02:36.870> tried<00:02:37.200> to<00:02:37.230> sue 00:02:37.550 --> 00:02:37.560 align:start position:0% an individual basis they tried to sue 00:02:37.560 --> 00:02:41.180 align:start position:0% an individual basis they tried to sue them<00:02:37.970> individually<00:02:39.500> this<00:02:40.500> ended<00:02:40.920> with<00:02:41.069> an 00:02:41.180 --> 00:02:41.190 align:start position:0% them individually this ended with an 00:02:41.190 --> 00:02:43.220 align:start position:0% them individually this ended with an antitrust<00:02:41.489> lawsuit<00:02:41.819> United<00:02:42.540> States<00:02:42.810> vs 00:02:43.220 --> 00:02:43.230 align:start position:0% antitrust lawsuit United States vs 00:02:43.230 --> 00:02:46.130 align:start position:0% antitrust lawsuit United States vs Microsoft<00:02:44.120> they<00:02:45.120> got<00:02:45.300> charged<00:02:45.630> with<00:02:45.690> a<00:02:45.810> legal 00:02:46.130 --> 00:02:46.140 align:start position:0% Microsoft they got charged with a legal 00:02:46.140 --> 00:02:47.509 align:start position:0% Microsoft they got charged with a legal tying<00:02:46.350> of<00:02:46.500> Internet<00:02:46.890> Explorer<00:02:47.220> to<00:02:47.400> the 00:02:47.509 --> 00:02:47.519 align:start position:0% tying of Internet Explorer to the 00:02:47.519 --> 00:02:49.820 align:start position:0% tying of Internet Explorer to the Windows<00:02:47.760> operating<00:02:47.940> system<00:02:48.630> and<00:02:48.810> they<00:02:49.590> had<00:02:49.709> to 00:02:49.820 --> 00:02:49.830 align:start position:0% Windows operating system and they had to 00:02:49.830 --> 00:02:51.890 align:start position:0% Windows operating system and they had to pay<00:02:49.980> hundreds<00:02:50.340> of<00:02:50.430> millions<00:02:50.790> and<00:02:51.030> this<00:02:51.569> is<00:02:51.720> not 00:02:51.890 --> 00:02:51.900 align:start position:0% pay hundreds of millions and this is not 00:02:51.900 --> 00:02:55.100 align:start position:0% pay hundreds of millions and this is not super<00:02:52.440> interesting<00:02:53.010> the<00:02:54.000> interesting<00:02:54.900> part 00:02:55.100 --> 00:02:55.110 align:start position:0% super interesting the interesting part 00:02:55.110 --> 00:02:56.680 align:start position:0% super interesting the interesting part is<00:02:55.230> really<00:02:55.410> this<00:02:55.620> someone<00:02:56.400> tried<00:02:56.640> to 00:02:56.680 --> 00:02:56.690 align:start position:0% is really this someone tried to 00:02:56.690 --> 00:02:59.539 align:start position:0% is really this someone tried to monopolize<00:02:57.690> and<00:02:57.989> gain<00:02:58.200> platform<00:02:58.680> power<00:02:58.860> over 00:02:59.539 --> 00:02:59.549 align:start position:0% monopolize and gain platform power over 00:02:59.549 --> 00:03:01.550 align:start position:0% monopolize and gain platform power over something<00:02:59.940> that<00:02:59.970> is<00:03:00.269> decentralized<00:03:00.930> the 00:03:01.550 --> 00:03:01.560 align:start position:0% something that is decentralized the 00:03:01.560 --> 00:03:06.350 align:start position:0% something that is decentralized the internet<00:03:04.130> and<00:03:05.130> this<00:03:05.430> concept<00:03:05.819> of<00:03:05.970> platform 00:03:06.350 --> 00:03:06.360 align:start position:0% internet and this concept of platform 00:03:06.360 --> 00:03:07.370 align:start position:0% internet and this concept of platform power<00:03:06.569> is<00:03:06.690> something<00:03:06.870> that<00:03:07.110> I<00:03:07.140> want<00:03:07.319> to 00:03:07.370 --> 00:03:07.380 align:start position:0% power is something that I want to 00:03:07.380 --> 00:03:10.640 align:start position:0% power is something that I want to emphasize<00:03:07.860> it<00:03:08.519> means<00:03:08.790> pretty<00:03:09.000> much<00:03:09.090> that<00:03:09.650> the 00:03:10.640 --> 00:03:10.650 align:start position:0% emphasize it means pretty much that the 00:03:10.650 --> 00:03:12.530 align:start position:0% emphasize it means pretty much that the browser's<00:03:11.099> are<00:03:11.220> not<00:03:11.400> just<00:03:11.670> the<00:03:11.849> clients<00:03:12.390> that 00:03:12.530 --> 00:03:12.540 align:start position:0% browser's are not just the clients that 00:03:12.540 --> 00:03:14.660 align:start position:0% browser's are not just the clients that represent<00:03:13.049> the<00:03:13.140> infrastructure<00:03:13.680> but<00:03:14.220> clients 00:03:14.660 --> 00:03:14.670 align:start position:0% represent the infrastructure but clients 00:03:14.670 --> 00:03:15.770 align:start position:0% represent the infrastructure but clients actually<00:03:14.819> have<00:03:15.120> the<00:03:15.269> power<00:03:15.420> to<00:03:15.599> dictate 00:03:15.770 --> 00:03:15.780 align:start position:0% actually have the power to dictate 00:03:15.780 --> 00:03:18.229 align:start position:0% actually have the power to dictate dictate<00:03:16.530> the<00:03:16.980> underlying<00:03:17.430> infrastructure 00:03:18.229 --> 00:03:18.239 align:start position:0% dictate the underlying infrastructure 00:03:18.239 --> 00:03:20.780 align:start position:0% dictate the underlying infrastructure and<00:03:18.420> protocols<00:03:18.870> and<00:03:19.220> they<00:03:20.220> create<00:03:20.489> blocking 00:03:20.780 --> 00:03:20.790 align:start position:0% and protocols and they create blocking 00:03:20.790 --> 00:03:22.759 align:start position:0% and protocols and they create blocking effects<00:03:21.299> and<00:03:21.450> they<00:03:21.840> can<00:03:22.049> they<00:03:22.590> can<00:03:22.739> be 00:03:22.759 --> 00:03:22.769 align:start position:0% effects and they can they can be 00:03:22.769 --> 00:03:24.440 align:start position:0% effects and they can they can be gatekeepers<00:03:23.430> that<00:03:23.459> control<00:03:24.000> who<00:03:24.180> should<00:03:24.359> have 00:03:24.440 --> 00:03:24.450 align:start position:0% gatekeepers that control who should have 00:03:24.450 --> 00:03:28.069 align:start position:0% gatekeepers that control who should have access<00:03:24.660> and<00:03:25.049> what<00:03:25.530> kind<00:03:25.769> of<00:03:25.890> access<00:03:26.250> and<00:03:26.930> if<00:03:27.930> we 00:03:28.069 --> 00:03:28.079 align:start position:0% access and what kind of access and if we 00:03:28.079 --> 00:03:30.289 align:start position:0% access and what kind of access and if we see<00:03:28.260> it<00:03:28.320> we<00:03:28.470> see<00:03:28.709> this<00:03:28.829> even<00:03:28.980> today<00:03:29.299> when 00:03:30.289 --> 00:03:30.299 align:start position:0% see it we see this even today when 00:03:30.299 --> 00:03:32.360 align:start position:0% see it we see this even today when Google<00:03:30.690> is<00:03:30.780> willing<00:03:31.109> to<00:03:31.140> pay<00:03:31.440> 12<00:03:31.980> billion 00:03:32.360 --> 00:03:32.370 align:start position:0% Google is willing to pay 12 billion 00:03:32.370 --> 00:03:35.660 align:start position:0% Google is willing to pay 12 billion dollars<00:03:32.549> a<00:03:33.120> year<00:03:33.709> to<00:03:34.709> Apple<00:03:35.069> just<00:03:35.280> to<00:03:35.459> remain 00:03:35.660 --> 00:03:35.670 align:start position:0% dollars a year to Apple just to remain 00:03:35.670 --> 00:03:38.770 align:start position:0% dollars a year to Apple just to remain the<00:03:35.880> default<00:03:36.209> search<00:03:36.420> in<00:03:36.569> Safari<00:03:36.930> browser<00:03:37.700> so 00:03:38.770 --> 00:03:38.780 align:start position:0% the default search in Safari browser so 00:03:38.780 --> 00:03:41.360 align:start position:0% the default search in Safari browser so browsers<00:03:39.780> are<00:03:39.930> still<00:03:40.109> a<00:03:40.140> very<00:03:40.440> interesting 00:03:41.360 --> 00:03:41.370 align:start position:0% browsers are still a very interesting 00:03:41.370 --> 00:03:43.370 align:start position:0% browsers are still a very interesting and<00:03:41.700> lucrative<00:03:41.940> target<00:03:42.569> for<00:03:43.260> big 00:03:43.370 --> 00:03:43.380 align:start position:0% and lucrative target for big 00:03:43.380 --> 00:03:45.289 align:start position:0% and lucrative target for big corporations<00:03:44.040> and<00:03:44.250> they<00:03:44.549> really<00:03:44.910> want<00:03:45.060> to<00:03:45.150> own 00:03:45.289 --> 00:03:45.299 align:start position:0% corporations and they really want to own 00:03:45.299 --> 00:03:47.569 align:start position:0% corporations and they really want to own this<00:03:45.569> this<00:03:45.810> space<00:03:46.139> and<00:03:46.350> control<00:03:46.739> it<00:03:46.889> as<00:03:47.370> much 00:03:47.569 --> 00:03:47.579 align:start position:0% this this space and control it as much 00:03:47.579 --> 00:03:50.559 align:start position:0% this this space and control it as much as<00:03:47.730> possible<00:03:48.620> but<00:03:49.620> this<00:03:49.739> is<00:03:49.799> not<00:03:50.040> what<00:03:50.190> we<00:03:50.310> want 00:03:50.559 --> 00:03:50.569 align:start position:0% as possible but this is not what we want 00:03:50.569 --> 00:03:54.349 align:start position:0% as possible but this is not what we want we<00:03:51.569> want<00:03:51.600> our<00:03:51.959> tools<00:03:52.260> and<00:03:52.470> clients<00:03:52.859> to<00:03:52.920> be<00:03:53.359> open 00:03:54.349 --> 00:03:54.359 align:start position:0% we want our tools and clients to be open 00:03:54.359 --> 00:03:56.330 align:start position:0% we want our tools and clients to be open and<00:03:54.480> free<00:03:54.660> as<00:03:54.870> much<00:03:55.079> as<00:03:55.230> possible<00:03:55.410> we<00:03:56.220> want 00:03:56.330 --> 00:03:56.340 align:start position:0% and free as much as possible we want 00:03:56.340 --> 00:03:58.309 align:start position:0% and free as much as possible we want them<00:03:56.549> to<00:03:56.700> be<00:03:56.819> an<00:03:56.940> extension<00:03:57.540> to<00:03:57.840> the<00:03:57.930> regular 00:03:58.309 --> 00:03:58.319 align:start position:0% them to be an extension to the regular 00:03:58.319 --> 00:04:00.500 align:start position:0% them to be an extension to the regular web<00:03:58.500> but<00:03:59.280> they<00:03:59.639> should<00:03:59.819> have<00:03:59.850> the<00:04:00.120> full<00:04:00.299> access 00:04:00.500 --> 00:04:00.510 align:start position:0% web but they should have the full access 00:04:00.510 --> 00:04:02.180 align:start position:0% web but they should have the full access to<00:04:00.690> the<00:04:00.900> Ethier<00:04:01.230> Network<00:04:01.650> and<00:04:01.829> all<00:04:01.980> the 00:04:02.180 --> 00:04:02.190 align:start position:0% to the Ethier Network and all the 00:04:02.190 --> 00:04:03.860 align:start position:0% to the Ethier Network and all the benefits<00:04:02.310> that<00:04:02.760> come<00:04:02.970> with<00:04:03.000> it<00:04:03.269> such<00:04:03.840> as 00:04:03.860 --> 00:04:03.870 align:start position:0% benefits that come with it such as 00:04:03.870 --> 00:04:05.900 align:start position:0% benefits that come with it such as computational<00:04:04.769> power<00:04:04.920> smart<00:04:05.340> contracts 00:04:05.900 --> 00:04:05.910 align:start position:0% computational power smart contracts 00:04:05.910 --> 00:04:09.379 align:start position:0% computational power smart contracts cryptographic<00:04:06.980> security<00:04:08.060> safe<00:04:09.060> sovereign 00:04:09.379 --> 00:04:09.389 align:start position:0% cryptographic security safe sovereign 00:04:09.389 --> 00:04:11.569 align:start position:0% cryptographic security safe sovereign identity<00:04:10.040> decentralized<00:04:11.040> storage<00:04:11.370> and 00:04:11.569 --> 00:04:11.579 align:start position:0% identity decentralized storage and 00:04:11.579 --> 00:04:14.840 align:start position:0% identity decentralized storage and crypto<00:04:11.819> payments<00:04:12.319> and<00:04:13.319> we<00:04:13.470> can<00:04:13.680> call<00:04:13.920> chorused 00:04:14.840 --> 00:04:14.850 align:start position:0% crypto payments and we can call chorused 00:04:14.850 --> 00:04:18.529 align:start position:0% crypto payments and we can call chorused where<00:04:15.090> the<00:04:15.209> browser<00:04:15.359> 3.0<00:04:16.940> unfortunately<00:04:17.940> this 00:04:18.529 --> 00:04:18.539 align:start position:0% where the browser 3.0 unfortunately this 00:04:18.539 --> 00:04:21.050 align:start position:0% where the browser 3.0 unfortunately this too<00:04:18.750> doesn't<00:04:18.930> exist<00:04:19.320> yet<00:04:19.560> and<00:04:20.400> someone<00:04:20.760> needs 00:04:21.050 --> 00:04:21.060 align:start position:0% too doesn't exist yet and someone needs 00:04:21.060 --> 00:04:24.260 align:start position:0% too doesn't exist yet and someone needs to<00:04:21.180> build<00:04:21.299> it<00:04:21.510> so<00:04:21.900> let's<00:04:22.080> build<00:04:22.169> a<00:04:22.260> browser<00:04:23.270> but 00:04:24.260 --> 00:04:24.270 align:start position:0% to build it so let's build a browser but 00:04:24.270 --> 00:04:26.149 align:start position:0% to build it so let's build a browser but before<00:04:24.630> we<00:04:24.780> are<00:04:24.930> reinventing<00:04:25.530> the<00:04:25.800> wheel<00:04:25.919> we 00:04:26.149 --> 00:04:26.159 align:start position:0% before we are reinventing the wheel we 00:04:26.159 --> 00:04:27.110 align:start position:0% before we are reinventing the wheel we should<00:04:26.340> just<00:04:26.490> shake 00:04:27.110 --> 00:04:27.120 align:start position:0% should just shake 00:04:27.120 --> 00:04:29.150 align:start position:0% should just shake this<00:04:27.540> would<00:04:27.720> be<00:04:27.870> and<00:04:28.050> there's<00:04:28.470> chromium<00:04:28.949> the 00:04:29.150 --> 00:04:29.160 align:start position:0% this would be and there's chromium the 00:04:29.160 --> 00:04:31.460 align:start position:0% this would be and there's chromium the open-source<00:04:29.669> project<00:04:30.660> for<00:04:31.080> Google<00:04:31.350> Chrome 00:04:31.460 --> 00:04:31.470 align:start position:0% open-source project for Google Chrome 00:04:31.470 --> 00:04:34.129 align:start position:0% open-source project for Google Chrome and<00:04:31.830> this<00:04:32.729> project<00:04:33.060> has<00:04:33.180> 20<00:04:33.540> million<00:04:33.720> lines<00:04:33.990> of 00:04:34.129 --> 00:04:34.139 align:start position:0% and this project has 20 million lines of 00:04:34.139 --> 00:04:37.219 align:start position:0% and this project has 20 million lines of code<00:04:34.199> it<00:04:35.070> takes<00:04:35.310> around<00:04:35.550> six<00:04:36.479> thousand<00:04:36.930> person 00:04:37.219 --> 00:04:37.229 align:start position:0% code it takes around six thousand person 00:04:37.229 --> 00:04:40.150 align:start position:0% code it takes around six thousand person years<00:04:37.470> to<00:04:37.620> build<00:04:37.970> the<00:04:38.970> estimated<00:04:39.449> costs<00:04:39.750> are 00:04:40.150 --> 00:04:40.160 align:start position:0% years to build the estimated costs are 00:04:40.160 --> 00:04:43.280 align:start position:0% years to build the estimated costs are 320<00:04:41.160> million<00:04:41.310> US<00:04:41.639> dollars<00:04:41.690> 35<00:04:42.690> programming 00:04:43.280 --> 00:04:43.290 align:start position:0% 320 million US dollars 35 programming 00:04:43.290 --> 00:04:45.439 align:start position:0% 320 million US dollars 35 programming languages<00:04:43.710> are<00:04:43.830> used<00:04:44.010> in<00:04:44.130> this<00:04:44.220> project<00:04:44.460> more 00:04:45.439 --> 00:04:45.449 align:start position:0% languages are used in this project more 00:04:45.449 --> 00:04:46.939 align:start position:0% languages are used in this project more than<00:04:45.570> 50<00:04:45.870> engineers<00:04:46.020> are<00:04:46.470> working<00:04:46.500> on<00:04:46.830> it 00:04:46.939 --> 00:04:46.949 align:start position:0% than 50 engineers are working on it 00:04:46.949 --> 00:04:49.850 align:start position:0% than 50 engineers are working on it full-time<00:04:47.690> more<00:04:48.690> than<00:04:48.840> 60<00:04:49.169> gigabytes<00:04:49.560> of<00:04:49.650> RAM 00:04:49.850 --> 00:04:49.860 align:start position:0% full-time more than 60 gigabytes of RAM 00:04:49.860 --> 00:04:51.409 align:start position:0% full-time more than 60 gigabytes of RAM are<00:04:49.979> highly<00:04:50.250> recommended<00:04:50.760> to<00:04:50.790> build<00:04:51.030> it<00:04:51.210> and 00:04:51.409 --> 00:04:51.419 align:start position:0% are highly recommended to build it and 00:04:51.419 --> 00:04:53.560 align:start position:0% are highly recommended to build it and it<00:04:51.720> takes<00:04:51.900> roughly<00:04:52.080> 24<00:04:52.620> hours<00:04:52.860> on<00:04:53.010> my<00:04:53.130> machine 00:04:53.560 --> 00:04:53.570 align:start position:0% it takes roughly 24 hours on my machine 00:04:53.570 --> 00:04:56.900 align:start position:0% it takes roughly 24 hours on my machine so<00:04:54.570> that<00:04:55.410> is<00:04:55.530> not<00:04:55.889> an<00:04:56.040> option<00:04:56.340> for<00:04:56.370> us<00:04:56.550> we<00:04:56.760> don't 00:04:56.900 --> 00:04:56.910 align:start position:0% so that is not an option for us we don't 00:04:56.910 --> 00:05:00.500 align:start position:0% so that is not an option for us we don't have<00:04:57.030> these<00:04:57.210> resources<00:04:59.300> but<00:05:00.300> there<00:05:00.449> are 00:05:00.500 --> 00:05:00.510 align:start position:0% have these resources but there are 00:05:00.510 --> 00:05:02.029 align:start position:0% have these resources but there are certain<00:05:00.780> frameworks<00:05:01.169> that<00:05:01.289> can<00:05:01.410> help<00:05:01.680> us<00:05:01.860> with 00:05:02.029 --> 00:05:02.039 align:start position:0% certain frameworks that can help us with 00:05:02.039 --> 00:05:04.610 align:start position:0% certain frameworks that can help us with it<00:05:02.070> and<00:05:02.430> one<00:05:02.639> of<00:05:02.669> them<00:05:02.910> is<00:05:03.030> electron<00:05:03.479> so<00:05:04.470> what 00:05:04.610 --> 00:05:04.620 align:start position:0% it and one of them is electron so what 00:05:04.620 --> 00:05:06.710 align:start position:0% it and one of them is electron so what is<00:05:04.710> electron<00:05:05.160> electron<00:05:05.669> already<00:05:06.360> comes<00:05:06.600> with 00:05:06.710 --> 00:05:06.720 align:start position:0% is electron electron already comes with 00:05:06.720 --> 00:05:10.129 align:start position:0% is electron electron already comes with chromium<00:05:07.080> pre-built<00:05:07.740> pre<00:05:07.979> bundled<00:05:08.449> it<00:05:09.449> has<00:05:09.660> no 00:05:10.129 --> 00:05:10.139 align:start position:0% chromium pre-built pre bundled it has no 00:05:10.139 --> 00:05:13.670 align:start position:0% chromium pre-built pre bundled it has no js'<00:05:10.520> integration<00:05:11.520> to<00:05:12.210> customize<00:05:13.020> the<00:05:13.410> the 00:05:13.670 --> 00:05:13.680 align:start position:0% js' integration to customize the the 00:05:13.680 --> 00:05:16.550 align:start position:0% js' integration to customize the the browser<00:05:14.310> behavior<00:05:14.880> and<00:05:15.810> it<00:05:15.930> also<00:05:16.110> has<00:05:16.380> native 00:05:16.550 --> 00:05:16.560 align:start position:0% browser behavior and it also has native 00:05:16.560 --> 00:05:19.100 align:start position:0% browser behavior and it also has native api's<00:05:17.160> so<00:05:17.850> that<00:05:18.240> it<00:05:18.360> runs<00:05:18.479> on<00:05:18.690> all<00:05:18.900> major 00:05:19.100 --> 00:05:19.110 align:start position:0% api's so that it runs on all major 00:05:19.110 --> 00:05:21.110 align:start position:0% api's so that it runs on all major operating<00:05:19.260> systems<00:05:19.710> it<00:05:20.610> looks<00:05:20.850> really 00:05:21.110 --> 00:05:21.120 align:start position:0% operating systems it looks really 00:05:21.120 --> 00:05:21.800 align:start position:0% operating systems it looks really promising 00:05:21.800 --> 00:05:21.810 align:start position:0% promising 00:05:21.810 --> 00:05:23.330 align:start position:0% promising it<00:05:22.080> looks<00:05:22.229> like<00:05:22.380> a<00:05:22.410> really<00:05:22.710> good<00:05:22.830> tool<00:05:23.039> that<00:05:23.070> we 00:05:23.330 --> 00:05:23.340 align:start position:0% it looks like a really good tool that we 00:05:23.340 --> 00:05:25.159 align:start position:0% it looks like a really good tool that we can<00:05:23.490> use<00:05:23.639> and<00:05:23.850> many<00:05:24.090> many<00:05:24.389> applications<00:05:24.600> are 00:05:25.159 --> 00:05:25.169 align:start position:0% can use and many many applications are 00:05:25.169 --> 00:05:27.230 align:start position:0% can use and many many applications are already<00:05:25.440> using<00:05:25.620> it<00:05:25.830> and<00:05:26.010> it's<00:05:26.669> becoming<00:05:27.030> a 00:05:27.230 --> 00:05:27.240 align:start position:0% already using it and it's becoming a 00:05:27.240 --> 00:05:29.360 align:start position:0% already using it and it's becoming a really<00:05:27.510> big<00:05:27.750> thing<00:05:27.930> and<00:05:28.169> we<00:05:28.620> see<00:05:28.830> this<00:05:29.010> for 00:05:29.360 --> 00:05:29.370 align:start position:0% really big thing and we see this for 00:05:29.370 --> 00:05:30.439 align:start position:0% really big thing and we see this for classical<00:05:29.880> and<00:05:30.000> developer<00:05:30.419> tools 00:05:30.439 --> 00:05:30.449 align:start position:0% classical and developer tools 00:05:30.449 --> 00:05:32.839 align:start position:0% classical and developer tools productivity<00:05:31.349> but<00:05:31.710> also<00:05:31.770> a<00:05:32.099> lot<00:05:32.310> of<00:05:32.430> trips<00:05:32.669> or 00:05:32.839 --> 00:05:32.849 align:start position:0% productivity but also a lot of trips or 00:05:32.849 --> 00:05:34.790 align:start position:0% productivity but also a lot of trips or applications<00:05:33.810> that<00:05:33.870> are<00:05:34.080> already<00:05:34.110> using 00:05:34.790 --> 00:05:34.800 align:start position:0% applications that are already using 00:05:34.800 --> 00:05:41.240 align:start position:0% applications that are already using electron<00:05:36.229> and<00:05:37.229> I<00:05:38.160> want<00:05:38.370> to<00:05:38.460> focus<00:05:38.639> on<00:05:40.220> before<00:05:41.220> I 00:05:41.240 --> 00:05:41.250 align:start position:0% electron and I want to focus on before I 00:05:41.250 --> 00:05:43.279 align:start position:0% electron and I want to focus on before I go<00:05:41.550> to<00:05:41.610> this<00:05:41.820> slide<00:05:42.360> I<00:05:42.419> should<00:05:42.780> I<00:05:42.900> should<00:05:43.139> say 00:05:43.279 --> 00:05:43.289 align:start position:0% go to this slide I should I should say 00:05:43.289 --> 00:05:46.670 align:start position:0% go to this slide I should I should say this<00:05:43.440> is<00:05:43.500> a<00:05:43.620> security<00:05:44.039> talk<00:05:45.380> this<00:05:46.380> was<00:05:46.560> the 00:05:46.670 --> 00:05:46.680 align:start position:0% this is a security talk this was the 00:05:46.680 --> 00:05:47.990 align:start position:0% this is a security talk this was the first<00:05:46.889> part<00:05:47.099> and<00:05:47.340> I<00:05:47.460> really<00:05:47.669> wanted<00:05:47.880> to 00:05:47.990 --> 00:05:48.000 align:start position:0% first part and I really wanted to 00:05:48.000 --> 00:05:49.310 align:start position:0% first part and I really wanted to emphasize<00:05:48.120> why<00:05:48.539> we<00:05:48.690> want<00:05:48.870> to<00:05:48.960> build<00:05:49.080> this 00:05:49.310 --> 00:05:49.320 align:start position:0% emphasize why we want to build this 00:05:49.320 --> 00:05:52.580 align:start position:0% emphasize why we want to build this browser<00:05:49.580> but<00:05:50.580> I<00:05:50.849> think<00:05:51.240> now<00:05:51.960> it's<00:05:52.139> becoming<00:05:52.440> a 00:05:52.580 --> 00:05:52.590 align:start position:0% browser but I think now it's becoming a 00:05:52.590 --> 00:05:54.170 align:start position:0% browser but I think now it's becoming a little<00:05:52.650> bit<00:05:52.770> more<00:05:52.979> technical<00:05:53.160> but<00:05:53.460> if<00:05:53.729> one<00:05:54.030> of 00:05:54.170 --> 00:05:54.180 align:start position:0% little bit more technical but if one of 00:05:54.180 --> 00:05:55.879 align:start position:0% little bit more technical but if one of you<00:05:54.360> and<00:05:54.539> the<00:05:54.599> audience<00:05:54.720> just<00:05:55.080> recognizes<00:05:55.740> one 00:05:55.879 --> 00:05:55.889 align:start position:0% you and the audience just recognizes one 00:05:55.889 --> 00:05:58.760 align:start position:0% you and the audience just recognizes one of<00:05:56.039> these<00:05:56.539> icons<00:05:57.539> here<00:05:57.630> or<00:05:58.110> you<00:05:58.320> may<00:05:58.440> be<00:05:58.470> using 00:05:58.760 --> 00:05:58.770 align:start position:0% of these icons here or you may be using 00:05:58.770 --> 00:06:01.040 align:start position:0% of these icons here or you may be using one<00:05:59.070> of<00:05:59.099> these<00:05:59.280> products<00:05:59.910> on<00:06:00.180> your<00:06:00.570> computer 00:06:01.040 --> 00:06:01.050 align:start position:0% one of these products on your computer 00:06:01.050 --> 00:06:03.740 align:start position:0% one of these products on your computer that's<00:06:01.580> also<00:06:02.580> ask<00:06:02.729> your<00:06:03.000> private<00:06:03.389> keys<00:06:03.570> or 00:06:03.740 --> 00:06:03.750 align:start position:0% that's also ask your private keys or 00:06:03.750 --> 00:06:05.570 align:start position:0% that's also ask your private keys or some<00:06:03.900> funds<00:06:04.139> on<00:06:04.289> it<00:06:04.440> then<00:06:04.889> I<00:06:04.919> think<00:06:05.220> the<00:06:05.340> next 00:06:05.570 --> 00:06:05.580 align:start position:0% some funds on it then I think the next 00:06:05.580 --> 00:06:07.310 align:start position:0% some funds on it then I think the next part<00:06:05.760> which<00:06:05.910> is<00:06:05.940> more<00:06:06.180> technical<00:06:06.690> technical 00:06:07.310 --> 00:06:07.320 align:start position:0% part which is more technical technical 00:06:07.320 --> 00:06:10.029 align:start position:0% part which is more technical technical could<00:06:07.620> still<00:06:07.860> be<00:06:07.979> interesting<00:06:08.400> for<00:06:08.550> you<00:06:08.669> I 00:06:10.029 --> 00:06:10.039 align:start position:0% could still be interesting for you I 00:06:10.039 --> 00:06:12.980 align:start position:0% could still be interesting for you I want<00:06:11.039> to<00:06:11.099> focus<00:06:11.280> on<00:06:11.639> these<00:06:11.789> web<00:06:12.389> 3<00:06:12.570> clients 00:06:12.980 --> 00:06:12.990 align:start position:0% want to focus on these web 3 clients 00:06:12.990 --> 00:06:15.350 align:start position:0% want to focus on these web 3 clients which<00:06:13.260> can<00:06:13.470> be<00:06:13.590> considered<00:06:14.010> a<00:06:14.099> subset<00:06:14.520> of<00:06:14.580> the 00:06:15.350 --> 00:06:15.360 align:start position:0% which can be considered a subset of the 00:06:15.360 --> 00:06:18.920 align:start position:0% which can be considered a subset of the browser<00:06:15.630> 3.0<00:06:16.340> so<00:06:17.340> these<00:06:17.550> are<00:06:17.729> clients<00:06:18.479> that 00:06:18.920 --> 00:06:18.930 align:start position:0% browser 3.0 so these are clients that 00:06:18.930 --> 00:06:21.379 align:start position:0% browser 3.0 so these are clients that have<00:06:19.260> access<00:06:19.949> to<00:06:20.070> the<00:06:20.190> ethion<00:06:20.550> network<00:06:20.910> but 00:06:21.379 --> 00:06:21.389 align:start position:0% have access to the ethion network but 00:06:21.389 --> 00:06:23.930 align:start position:0% have access to the ethion network but they<00:06:21.510> can<00:06:21.660> also<00:06:21.840> host<00:06:22.169> EPS<00:06:22.940> decentralized 00:06:23.930 --> 00:06:23.940 align:start position:0% they can also host EPS decentralized 00:06:23.940 --> 00:06:26.089 align:start position:0% they can also host EPS decentralized apps<00:06:24.240> and<00:06:24.479> they<00:06:25.020> provide<00:06:25.349> an<00:06:25.470> interface<00:06:25.740> so 00:06:26.089 --> 00:06:26.099 align:start position:0% apps and they provide an interface so 00:06:26.099 --> 00:06:27.890 align:start position:0% apps and they provide an interface so that<00:06:26.280> these<00:06:26.490> apps<00:06:26.760> can<00:06:26.910> actually<00:06:27.570> interact 00:06:27.890 --> 00:06:27.900 align:start position:0% that these apps can actually interact 00:06:27.900 --> 00:06:30.290 align:start position:0% that these apps can actually interact with<00:06:28.080> the<00:06:28.260> network<00:06:28.380> and<00:06:28.740> the<00:06:29.280> most<00:06:29.430> prominent 00:06:30.290 --> 00:06:30.300 align:start position:0% with the network and the most prominent 00:06:30.300 --> 00:06:32.330 align:start position:0% with the network and the most prominent ones<00:06:30.479> are<00:06:30.630> probably<00:06:30.900> madam<00:06:31.229> as<00:06:31.380> brave<00:06:31.770> then<00:06:32.190> if 00:06:32.330 --> 00:06:32.340 align:start position:0% ones are probably madam as brave then if 00:06:32.340 --> 00:06:34.670 align:start position:0% ones are probably madam as brave then if you<00:06:32.550> missed<00:06:32.880> and<00:06:33.120> the<00:06:33.570> parent<00:06:33.870> parity<00:06:34.320> client 00:06:34.670 --> 00:06:34.680 align:start position:0% you missed and the parent parity client 00:06:34.680 --> 00:06:38.270 align:start position:0% you missed and the parent parity client and<00:06:36.200> this<00:06:37.200> is<00:06:37.349> the<00:06:37.500> approach<00:06:37.830> that<00:06:37.860> these 00:06:38.270 --> 00:06:38.280 align:start position:0% and this is the approach that these 00:06:38.280 --> 00:06:40.940 align:start position:0% and this is the approach that these projects<00:06:38.880> took<00:06:39.360> so<00:06:40.020> meta<00:06:40.200> mask<00:06:40.440> is<00:06:40.620> really 00:06:40.940 --> 00:06:40.950 align:start position:0% projects took so meta mask is really 00:06:40.950 --> 00:06:43.370 align:start position:0% projects took so meta mask is really convenient<00:06:41.250> and<00:06:41.580> it's<00:06:41.760> a<00:06:41.880> great<00:06:42.030> tool<00:06:42.320> it's<00:06:43.320> a 00:06:43.370 --> 00:06:43.380 align:start position:0% convenient and it's a great tool it's a 00:06:43.380 --> 00:06:45.350 align:start position:0% convenient and it's a great tool it's a Chrome<00:06:43.560> extension<00:06:43.590> then<00:06:44.310> brave<00:06:44.520> was<00:06:45.090> built<00:06:45.300> on 00:06:45.350 --> 00:06:45.360 align:start position:0% Chrome extension then brave was built on 00:06:45.360 --> 00:06:47.180 align:start position:0% Chrome extension then brave was built on electron<00:06:45.870> if<00:06:46.020> you<00:06:46.140> missed<00:06:46.380> build<00:06:46.680> on<00:06:46.770> electron 00:06:47.180 --> 00:06:47.190 align:start position:0% electron if you missed build on electron 00:06:47.190 --> 00:06:50.150 align:start position:0% electron if you missed build on electron and<00:06:47.400> parity<00:06:47.730> had<00:06:48.330> a<00:06:48.360> UI<00:06:49.350> that<00:06:49.620> was<00:06:49.800> built<00:06:50.010> on 00:06:50.150 --> 00:06:50.160 align:start position:0% and parity had a UI that was built on 00:06:50.160 --> 00:06:51.620 align:start position:0% and parity had a UI that was built on electron<00:06:50.700> and<00:06:50.850> now<00:06:50.910> they<00:06:51.060> have<00:06:51.150> a<00:06:51.180> wallet<00:06:51.540> that 00:06:51.620 --> 00:06:51.630 align:start position:0% electron and now they have a wallet that 00:06:51.630 --> 00:06:55.190 align:start position:0% electron and now they have a wallet that is<00:06:51.750> built<00:06:51.930> with<00:06:52.050> electron<00:06:52.500> and<00:06:53.630> brave<00:06:54.630> were 00:06:55.190 --> 00:06:55.200 align:start position:0% is built with electron and brave were 00:06:55.200 --> 00:06:57.170 align:start position:0% is built with electron and brave were probably<00:06:55.440> the<00:06:55.680> first<00:06:55.710> that<00:06:56.310> recognized<00:06:56.820> that 00:06:57.170 --> 00:06:57.180 align:start position:0% probably the first that recognized that 00:06:57.180 --> 00:06:59.330 align:start position:0% probably the first that recognized that electron<00:06:57.600> is<00:06:57.690> not<00:06:57.930> the<00:06:58.050> best<00:06:58.200> tool<00:06:58.500> to<00:06:58.740> build 00:06:59.330 --> 00:06:59.340 align:start position:0% electron is not the best tool to build 00:06:59.340 --> 00:07:01.010 align:start position:0% electron is not the best tool to build these<00:06:59.460> kind<00:06:59.790> of<00:06:59.970> browser<00:07:00.300> browser<00:07:00.570> logic 00:07:01.010 --> 00:07:01.020 align:start position:0% these kind of browser browser logic 00:07:01.020 --> 00:07:02.870 align:start position:0% these kind of browser browser logic applications<00:07:01.650> and<00:07:01.860> then<00:07:02.400> they<00:07:02.520> forked 00:07:02.870 --> 00:07:02.880 align:start position:0% applications and then they forked 00:07:02.880 --> 00:07:06.380 align:start position:0% applications and then they forked electron<00:07:04.190> to<00:07:05.190> fix<00:07:05.430> some<00:07:05.640> of<00:07:05.670> the<00:07:05.910> security 00:07:06.380 --> 00:07:06.390 align:start position:0% electron to fix some of the security 00:07:06.390 --> 00:07:08.540 align:start position:0% electron to fix some of the security problems<00:07:06.810> and<00:07:06.990> they<00:07:07.320> call<00:07:07.500> it<00:07:07.650> moon<00:07:07.890> and<00:07:08.160> then 00:07:08.540 --> 00:07:08.550 align:start position:0% problems and they call it moon and then 00:07:08.550 --> 00:07:10.130 align:start position:0% problems and they call it moon and then they<00:07:08.640> realized<00:07:09.000> this<00:07:09.360> will<00:07:09.540> also<00:07:09.810> not<00:07:09.930> help 00:07:10.130 --> 00:07:10.140 align:start position:0% they realized this will also not help 00:07:10.140 --> 00:07:12.410 align:start position:0% they realized this will also not help and<00:07:10.380> now<00:07:10.500> they<00:07:10.650> going<00:07:10.920> completely<00:07:11.130> away<00:07:11.520> to 00:07:12.410 --> 00:07:12.420 align:start position:0% and now they going completely away to 00:07:12.420 --> 00:07:14.840 align:start position:0% and now they going completely away to something<00:07:12.720> that<00:07:12.750> is<00:07:12.990> closer<00:07:13.260> to<00:07:13.410> chromium<00:07:13.850> and 00:07:14.840 --> 00:07:14.850 align:start position:0% something that is closer to chromium and 00:07:14.850 --> 00:07:17.210 align:start position:0% something that is closer to chromium and the<00:07:15.180> if<00:07:15.330> you<00:07:15.450> miss<00:07:15.690> team<00:07:15.960> also<00:07:16.770> realized<00:07:17.130> that 00:07:17.210 --> 00:07:17.220 align:start position:0% the if you miss team also realized that 00:07:17.220 --> 00:07:18.500 align:start position:0% the if you miss team also realized that electron<00:07:17.670> might<00:07:17.820> not<00:07:18.000> be<00:07:18.150> the<00:07:18.270> best<00:07:18.360> choice 00:07:18.500 --> 00:07:18.510 align:start position:0% electron might not be the best choice 00:07:18.510 --> 00:07:20.630 align:start position:0% electron might not be the best choice and<00:07:18.930> we<00:07:19.380> have<00:07:19.410> an<00:07:19.650> internal<00:07:20.070> project<00:07:20.250> called 00:07:20.630 --> 00:07:20.640 align:start position:0% and we have an internal project called 00:07:20.640 --> 00:07:22.100 align:start position:0% and we have an internal project called Tao<00:07:20.820> and<00:07:21.000> I<00:07:21.090> will<00:07:21.270> talk<00:07:21.780> a<00:07:21.810> little<00:07:21.900> bit<00:07:22.080> more 00:07:22.100 --> 00:07:22.110 align:start position:0% Tao and I will talk a little bit more 00:07:22.110 --> 00:07:25.000 align:start position:0% Tao and I will talk a little bit more about<00:07:22.410> this<00:07:22.620> in<00:07:22.860> a<00:07:22.950> second<00:07:23.310> and<00:07:23.490> that<00:07:24.240> tries<00:07:24.480> to 00:07:25.000 --> 00:07:25.010 align:start position:0% about this in a second and that tries to 00:07:25.010 --> 00:07:29.360 align:start position:0% about this in a second and that tries to fix<00:07:26.010> all<00:07:26.250> these<00:07:26.400> security<00:07:26.880> problems<00:07:28.370> but 00:07:29.360 --> 00:07:29.370 align:start position:0% fix all these security problems but 00:07:29.370 --> 00:07:31.280 align:start position:0% fix all these security problems but before<00:07:29.670> I<00:07:29.700> talk<00:07:29.790> more<00:07:30.090> about<00:07:30.150> electron<00:07:30.750> why 00:07:31.280 --> 00:07:31.290 align:start position:0% before I talk more about electron why 00:07:31.290 --> 00:07:33.470 align:start position:0% before I talk more about electron why it's<00:07:31.470> not<00:07:31.590> just<00:07:31.830> every<00:07:32.130> electron<00:07:33.000> is<00:07:33.120> not<00:07:33.300> such 00:07:33.470 --> 00:07:33.480 align:start position:0% it's not just every electron is not such 00:07:33.480 --> 00:07:35.210 align:start position:0% it's not just every electron is not such a<00:07:33.510> great<00:07:33.750> option<00:07:34.050> why<00:07:34.590> it's<00:07:34.680> not<00:07:34.770> everyone 00:07:35.210 --> 00:07:35.220 align:start position:0% a great option why it's not everyone 00:07:35.220 --> 00:07:37.160 align:start position:0% a great option why it's not everyone just<00:07:35.460> building<00:07:35.790> a<00:07:35.880> Chrome<00:07:36.060> extension<00:07:36.570> and<00:07:36.720> I 00:07:37.160 --> 00:07:37.170 align:start position:0% just building a Chrome extension and I 00:07:37.170 --> 00:07:38.720 align:start position:0% just building a Chrome extension and I really<00:07:37.410> wanted<00:07:37.650> to<00:07:37.710> motivate<00:07:38.310> this<00:07:38.430> with<00:07:38.640> the 00:07:38.720 --> 00:07:38.730 align:start position:0% really wanted to motivate this with the 00:07:38.730 --> 00:07:41.300 align:start position:0% really wanted to motivate this with the first<00:07:38.940> couple<00:07:39.330> of<00:07:39.390> slides<00:07:39.570> and<00:07:40.100> that<00:07:41.100> we<00:07:41.190> need 00:07:41.300 --> 00:07:41.310 align:start position:0% first couple of slides and that we need 00:07:41.310 --> 00:07:44.030 align:start position:0% first couple of slides and that we need some<00:07:41.460> kind<00:07:41.640> of<00:07:41.730> diversity<00:07:42.240> and<00:07:42.710> that<00:07:43.710> platform 00:07:44.030 --> 00:07:44.040 align:start position:0% some kind of diversity and that platform 00:07:44.040 --> 00:07:46.730 align:start position:0% some kind of diversity and that platform power<00:07:44.430> is<00:07:44.550> a<00:07:44.580> big<00:07:44.850> problem<00:07:45.060> and<00:07:45.530> besides<00:07:46.530> this 00:07:46.730 --> 00:07:46.740 align:start position:0% power is a big problem and besides this 00:07:46.740 --> 00:07:48.260 align:start position:0% power is a big problem and besides this being<00:07:47.130> a<00:07:47.190> browser<00:07:47.370> plugin<00:07:47.760> has<00:07:48.000> more 00:07:48.260 --> 00:07:48.270 align:start position:0% being a browser plugin has more 00:07:48.270 --> 00:07:52.490 align:start position:0% being a browser plugin has more limitations<00:07:49.820> limited<00:07:50.820> API<00:07:51.120> X<00:07:51.390> is<00:07:51.630> not<00:07:52.200> running 00:07:52.490 --> 00:07:52.500 align:start position:0% limitations limited API X is not running 00:07:52.500 --> 00:07:54.230 align:start position:0% limitations limited API X is not running in<00:07:52.620> chromium<00:07:52.860> forks<00:07:53.280> without<00:07:53.520> extension<00:07:54.000> API 00:07:54.230 --> 00:07:54.240 align:start position:0% in chromium forks without extension API 00:07:54.240 --> 00:07:56.810 align:start position:0% in chromium forks without extension API such<00:07:54.390> as<00:07:54.780> electron<00:07:55.200> it's<00:07:55.710> perceived<00:07:56.220> and<00:07:56.550> a 00:07:56.810 --> 00:07:56.820 align:start position:0% such as electron it's perceived and a 00:07:56.820 --> 00:07:59.990 align:start position:0% such as electron it's perceived and a type<00:07:57.600> of<00:07:57.750> coupled<00:07:58.440> to<00:07:58.590> the<00:07:58.770> Chrome<00:07:59.190> Firefox<00:07:59.460> or 00:07:59.990 --> 00:08:00.000 align:start position:0% type of coupled to the Chrome Firefox or 00:08:00.000 --> 00:08:01.640 align:start position:0% type of coupled to the Chrome Firefox or whatever<00:08:00.270> the<00:08:00.510> hosting<00:08:00.810> application<00:08:01.320> is<00:08:01.440> and 00:08:01.640 --> 00:08:01.650 align:start position:0% whatever the hosting application is and 00:08:01.650 --> 00:08:04.190 align:start position:0% whatever the hosting application is and it<00:08:02.580> has<00:08:02.670> no<00:08:02.880> platform<00:08:03.240> ownership<00:08:03.630> which<00:08:04.050> is 00:08:04.190 --> 00:08:04.200 align:start position:0% it has no platform ownership which is 00:08:04.200 --> 00:08:06.170 align:start position:0% it has no platform ownership which is probably<00:08:04.530> probably<00:08:05.070> the<00:08:05.490> biggest<00:08:05.820> problem 00:08:06.170 --> 00:08:06.180 align:start position:0% probably probably the biggest problem 00:08:06.180 --> 00:08:09.050 align:start position:0% probably probably the biggest problem because<00:08:06.380> then<00:08:07.380> this<00:08:07.560> can<00:08:07.770> happen<00:08:08.060> someone 00:08:09.050 --> 00:08:09.060 align:start position:0% because then this can happen someone 00:08:09.060 --> 00:08:10.910 align:start position:0% because then this can happen someone decides<00:08:09.630> for<00:08:09.930> you<00:08:10.080> that<00:08:10.350> your<00:08:10.470> extension 00:08:10.910 --> 00:08:10.920 align:start position:0% decides for you that your extension 00:08:10.920 --> 00:08:12.620 align:start position:0% decides for you that your extension should<00:08:11.040> not<00:08:11.220> exist<00:08:11.640> anymore<00:08:11.940> should<00:08:12.390> not<00:08:12.540> be 00:08:12.620 --> 00:08:12.630 align:start position:0% should not exist anymore should not be 00:08:12.630 --> 00:08:14.510 align:start position:0% should not exist anymore should not be available<00:08:12.840> anymore<00:08:13.290> and<00:08:13.560> this<00:08:13.890> happened<00:08:14.250> and 00:08:14.510 --> 00:08:14.520 align:start position:0% available anymore and this happened and 00:08:14.520 --> 00:08:16.460 align:start position:0% available anymore and this happened and the<00:08:15.150> Mirrormask<00:08:15.360> extension<00:08:16.050> was<00:08:16.170> removed 00:08:16.460 --> 00:08:16.470 align:start position:0% the Mirrormask extension was removed 00:08:16.470 --> 00:08:17.990 align:start position:0% the Mirrormask extension was removed from<00:08:16.560> the<00:08:16.650> store<00:08:17.010> for<00:08:17.250> a<00:08:17.280> couple<00:08:17.550> of<00:08:17.580> days<00:08:17.820> and 00:08:17.990 --> 00:08:18.000 align:start position:0% from the store for a couple of days and 00:08:18.000 --> 00:08:19.880 align:start position:0% from the store for a couple of days and they<00:08:18.120> are<00:08:18.150> more<00:08:18.360> crypto<00:08:18.720> extensions<00:08:19.260> that<00:08:19.710> got 00:08:19.880 --> 00:08:19.890 align:start position:0% they are more crypto extensions that got 00:08:19.890 --> 00:08:23.150 align:start position:0% they are more crypto extensions that got completely<00:08:20.280> banned<00:08:20.580> from<00:08:20.730> the<00:08:20.880> store<00:08:22.160> well 00:08:23.150 --> 00:08:23.160 align:start position:0% completely banned from the store well 00:08:23.160 --> 00:08:24.710 align:start position:0% completely banned from the store well this<00:08:23.280> happens<00:08:23.640> someone<00:08:23.880> decides<00:08:24.240> that<00:08:24.510> all 00:08:24.710 --> 00:08:24.720 align:start position:0% this happens someone decides that all 00:08:24.720 --> 00:08:26.210 align:start position:0% this happens someone decides that all applications<00:08:25.170> should<00:08:25.470> not<00:08:25.650> exist<00:08:25.920> anymore 00:08:26.210 --> 00:08:26.220 align:start position:0% applications should not exist anymore 00:08:26.220 --> 00:08:28.490 align:start position:0% applications should not exist anymore and<00:08:26.460> this<00:08:26.820> also<00:08:27.000> happened<00:08:27.480> and<00:08:27.690> there<00:08:28.470> was 00:08:28.490 --> 00:08:28.500 align:start position:0% and this also happened and there was 00:08:28.500 --> 00:08:30.530 align:start position:0% and this also happened and there was something<00:08:28.920> called<00:08:29.130> Chrome<00:08:29.430> apps<00:08:29.670> and<00:08:29.910> they 00:08:30.530 --> 00:08:30.540 align:start position:0% something called Chrome apps and they 00:08:30.540 --> 00:08:31.850 align:start position:0% something called Chrome apps and they got<00:08:30.720> pretty<00:08:30.870> much<00:08:31.020> killed<00:08:31.350> within<00:08:31.530> the<00:08:31.710> last 00:08:31.850 --> 00:08:31.860 align:start position:0% got pretty much killed within the last 00:08:31.860 --> 00:08:35.870 align:start position:0% got pretty much killed within the last two<00:08:32.010> years<00:08:32.360> all<00:08:33.360> of<00:08:33.540> them<00:08:34.400> okay<00:08:35.400> now<00:08:35.580> I<00:08:35.610> want<00:08:35.790> to 00:08:35.870 --> 00:08:35.880 align:start position:0% two years all of them okay now I want to 00:08:35.880 --> 00:08:37.550 align:start position:0% two years all of them okay now I want to focus<00:08:36.060> a<00:08:36.330> little<00:08:36.420> bit<00:08:36.570> more<00:08:36.750> on<00:08:37.020> electron 00:08:37.550 --> 00:08:37.560 align:start position:0% focus a little bit more on electron 00:08:37.560 --> 00:08:40.310 align:start position:0% focus a little bit more on electron security<00:08:38.060> and<00:08:39.060> there<00:08:39.510> are<00:08:39.599> a<00:08:39.630> couple<00:08:39.780> of<00:08:40.080> ways 00:08:40.310 --> 00:08:40.320 align:start position:0% security and there are a couple of ways 00:08:40.320 --> 00:08:42.140 align:start position:0% security and there are a couple of ways how<00:08:40.349> to<00:08:40.590> build<00:08:40.919> an<00:08:41.160> electronic<00:08:42.000> application 00:08:42.140 --> 00:08:42.150 align:start position:0% how to build an electronic application 00:08:42.150 --> 00:08:44.390 align:start position:0% how to build an electronic application there<00:08:42.810> is<00:08:42.840> a<00:08:42.900> good<00:08:43.110> way<00:08:43.290> where<00:08:43.950> you<00:08:44.040> actually 00:08:44.390 --> 00:08:44.400 align:start position:0% there is a good way where you actually 00:08:44.400 --> 00:08:45.950 align:start position:0% there is a good way where you actually build<00:08:44.880> a<00:08:45.000> user<00:08:45.150> interface<00:08:45.630> with<00:08:45.810> web 00:08:45.950 --> 00:08:45.960 align:start position:0% build a user interface with web 00:08:45.960 --> 00:08:47.630 align:start position:0% build a user interface with web technologies<00:08:46.530> which<00:08:46.950> is<00:08:47.100> what<00:08:47.250> you<00:08:47.340> want<00:08:47.520> or 00:08:47.630 --> 00:08:47.640 align:start position:0% technologies which is what you want or 00:08:47.640 --> 00:08:49.070 align:start position:0% technologies which is what you want or you<00:08:47.730> build<00:08:47.940> your<00:08:48.030> your<00:08:48.510> DEP<00:08:48.720> with<00:08:48.930> web 00:08:49.070 --> 00:08:49.080 align:start position:0% you build your your DEP with web 00:08:49.080 --> 00:08:51.110 align:start position:0% you build your your DEP with web technologies<00:08:49.650> and<00:08:49.920> then<00:08:50.100> you<00:08:50.700> need<00:08:50.880> to<00:08:50.970> make 00:08:51.110 --> 00:08:51.120 align:start position:0% technologies and then you need to make 00:08:51.120 --> 00:08:53.400 align:start position:0% technologies and then you need to make some<00:08:51.360> like<00:08:51.870> extensions<00:08:52.620> to<00:08:52.830> the<00:08:52.980> to<00:08:53.190> the 00:08:53.400 --> 00:08:53.410 align:start position:0% some like extensions to the to the 00:08:53.410 --> 00:08:54.809 align:start position:0% some like extensions to the to the the<00:08:53.680> stuff<00:08:53.980> that<00:08:54.009> the<00:08:54.279> browser<00:08:54.310> does<00:08:54.790> not 00:08:54.809 --> 00:08:54.819 align:start position:0% the stuff that the browser does not 00:08:54.819 --> 00:08:57.449 align:start position:0% the stuff that the browser does not offer<00:08:55.600> you<00:08:55.930> a<00:08:55.959> regular<00:08:56.620> browser<00:08:56.769> so<00:08:57.399> you 00:08:57.449 --> 00:08:57.459 align:start position:0% offer you a regular browser so you 00:08:57.459 --> 00:09:00.720 align:start position:0% offer you a regular browser so you design<00:08:57.879> an<00:08:58.029> API<00:08:58.300> for<00:08:58.389> this<00:08:58.750> and<00:08:58.990> then<00:08:59.560> may<00:09:00.519> need 00:09:00.720 --> 00:09:00.730 align:start position:0% design an API for this and then may need 00:09:00.730 --> 00:09:02.670 align:start position:0% design an API for this and then may need more<00:09:00.879> access<00:09:01.060> to<00:09:01.240> the<00:09:01.420> operating<00:09:01.839> system<00:09:02.199> you 00:09:02.670 --> 00:09:02.680 align:start position:0% more access to the operating system you 00:09:02.680 --> 00:09:04.769 align:start position:0% more access to the operating system you write<00:09:02.860> the<00:09:02.980> application<00:09:03.100> logic<00:09:03.730> that<00:09:04.089> is<00:09:04.240> that 00:09:04.769 --> 00:09:04.779 align:start position:0% write the application logic that is that 00:09:04.779 --> 00:09:07.379 align:start position:0% write the application logic that is that is<00:09:04.899> running<00:09:05.350> in<00:09:05.560> a<00:09:05.620> separate<00:09:05.920> process<00:09:06.399> and<00:09:06.940> you 00:09:07.379 --> 00:09:07.389 align:start position:0% is running in a separate process and you 00:09:07.389 --> 00:09:09.449 align:start position:0% is running in a separate process and you have<00:09:07.509> some<00:09:07.750> kind<00:09:07.930> of<00:09:08.139> messaging<00:09:08.920> mechanism 00:09:09.449 --> 00:09:09.459 align:start position:0% have some kind of messaging mechanism 00:09:09.459 --> 00:09:11.100 align:start position:0% have some kind of messaging mechanism that<00:09:09.579> is<00:09:09.730> whitelist<00:09:10.209> whitelisting<00:09:10.810> certain 00:09:11.100 --> 00:09:11.110 align:start position:0% that is whitelist whitelisting certain 00:09:11.110 --> 00:09:12.960 align:start position:0% that is whitelist whitelisting certain messages<00:09:11.500> between<00:09:12.189> these<00:09:12.370> two<00:09:12.579> processes 00:09:12.960 --> 00:09:12.970 align:start position:0% messages between these two processes 00:09:12.970 --> 00:09:15.780 align:start position:0% messages between these two processes that's<00:09:13.779> good<00:09:14.500> but<00:09:14.920> it's<00:09:15.009> also<00:09:15.220> harder<00:09:15.639> to 00:09:15.780 --> 00:09:15.790 align:start position:0% that's good but it's also harder to 00:09:15.790 --> 00:09:18.059 align:start position:0% that's good but it's also harder to build<00:09:15.939> and<00:09:16.379> you<00:09:17.379> can<00:09:17.529> also<00:09:17.680> do<00:09:17.860> this<00:09:18.009> with 00:09:18.059 --> 00:09:18.069 align:start position:0% build and you can also do this with 00:09:18.069 --> 00:09:19.860 align:start position:0% build and you can also do this with electron<00:09:18.610> you<00:09:18.639> can<00:09:18.939> build<00:09:19.360> the<00:09:19.509> whole<00:09:19.660> your 00:09:19.860 --> 00:09:19.870 align:start position:0% electron you can build the whole your 00:09:19.870 --> 00:09:21.900 align:start position:0% electron you can build the whole your user<00:09:20.199> interface<00:09:20.379> code<00:09:20.949> that<00:09:21.459> is<00:09:21.579> running<00:09:21.759> in 00:09:21.900 --> 00:09:21.910 align:start position:0% user interface code that is running in 00:09:21.910 --> 00:09:23.970 align:start position:0% user interface code that is running in the<00:09:22.029> browser<00:09:22.259> then<00:09:23.259> you<00:09:23.379> don't<00:09:23.589> really<00:09:23.769> need 00:09:23.970 --> 00:09:23.980 align:start position:0% the browser then you don't really need 00:09:23.980 --> 00:09:25.699 align:start position:0% the browser then you don't really need an<00:09:24.160> API<00:09:24.459> and<00:09:24.759> you<00:09:24.819> can<00:09:24.970> just<00:09:25.209> write<00:09:25.389> your<00:09:25.540> whole 00:09:25.699 --> 00:09:25.709 align:start position:0% an API and you can just write your whole 00:09:25.709 --> 00:09:28.170 align:start position:0% an API and you can just write your whole application<00:09:26.709> code<00:09:26.920> that<00:09:27.399> is<00:09:27.519> also<00:09:27.850> running<00:09:28.000> in 00:09:28.170 --> 00:09:28.180 align:start position:0% application code that is also running in 00:09:28.180 --> 00:09:30.480 align:start position:0% application code that is also running in the<00:09:28.300> in<00:09:28.449> the<00:09:28.540> browser<00:09:28.720> window<00:09:28.959> and<00:09:29.290> that's<00:09:29.740> for 00:09:30.480 --> 00:09:30.490 align:start position:0% the in the browser window and that's for 00:09:30.490 --> 00:09:32.550 align:start position:0% the in the browser window and that's for most<00:09:30.730> applications<00:09:30.970> a<00:09:31.540> really<00:09:31.750> bad<00:09:31.930> idea<00:09:31.959> and 00:09:32.550 --> 00:09:32.560 align:start position:0% most applications a really bad idea and 00:09:32.560 --> 00:09:35.069 align:start position:0% most applications a really bad idea and this<00:09:33.490> is<00:09:33.550> possible<00:09:34.269> because<00:09:34.389> of<00:09:34.600> a<00:09:34.870> feature 00:09:35.069 --> 00:09:35.079 align:start position:0% this is possible because of a feature 00:09:35.079 --> 00:09:37.079 align:start position:0% this is possible because of a feature one<00:09:35.769> of<00:09:35.860> the<00:09:35.980> core<00:09:36.189> features<00:09:36.310> of<00:09:36.639> electron 00:09:37.079 --> 00:09:37.089 align:start position:0% one of the core features of electron 00:09:37.089 --> 00:09:40.050 align:start position:0% one of the core features of electron which<00:09:37.600> is<00:09:37.750> called<00:09:37.959> node<00:09:38.170> integration<00:09:38.879> so<00:09:39.879> node 00:09:40.050 --> 00:09:40.060 align:start position:0% which is called node integration so node 00:09:40.060 --> 00:09:43.110 align:start position:0% which is called node integration so node integration<00:09:40.720> allows<00:09:41.500> you<00:09:41.889> to<00:09:42.250> access<00:09:42.550> all<00:09:42.759> the 00:09:43.110 --> 00:09:43.120 align:start position:0% integration allows you to access all the 00:09:43.120 --> 00:09:45.569 align:start position:0% integration allows you to access all the node<00:09:43.300> Rhea's<00:09:43.750> api's<00:09:44.350> from<00:09:45.189> within<00:09:45.370> the 00:09:45.569 --> 00:09:45.579 align:start position:0% node Rhea's api's from within the 00:09:45.579 --> 00:09:47.819 align:start position:0% node Rhea's api's from within the browser<00:09:45.759> window<00:09:46.209> you<00:09:46.389> don't<00:09:47.350> need<00:09:47.680> the 00:09:47.819 --> 00:09:47.829 align:start position:0% browser window you don't need the 00:09:47.829 --> 00:09:50.069 align:start position:0% browser window you don't need the separation<00:09:48.459> of<00:09:48.519> these<00:09:49.149> processes<00:09:49.629> anymore 00:09:50.069 --> 00:09:50.079 align:start position:0% separation of these processes anymore 00:09:50.079 --> 00:09:52.290 align:start position:0% separation of these processes anymore you<00:09:50.680> can<00:09:50.920> do<00:09:51.189> really<00:09:51.519> crazy<00:09:51.670> stuff<00:09:52.029> you<00:09:52.089> can 00:09:52.290 --> 00:09:52.300 align:start position:0% you can do really crazy stuff you can 00:09:52.300 --> 00:09:53.999 align:start position:0% you can do really crazy stuff you can accept<00:09:52.540> the<00:09:52.660> filesystem<00:09:52.870> just<00:09:53.500> from<00:09:53.740> a 00:09:53.999 --> 00:09:54.009 align:start position:0% accept the filesystem just from a 00:09:54.009 --> 00:09:57.480 align:start position:0% accept the filesystem just from a regular<00:09:54.579> web<00:09:54.730> page<00:09:55.949> this<00:09:56.949> is<00:09:57.069> possible 00:09:57.480 --> 00:09:57.490 align:start position:0% regular web page this is possible 00:09:57.490 --> 00:10:01.439 align:start position:0% regular web page this is possible especially<00:09:57.819> because<00:09:59.550> the<00:10:00.550> electron<00:10:00.939> project 00:10:01.439 --> 00:10:01.449 align:start position:0% especially because the electron project 00:10:01.449 --> 00:10:02.819 align:start position:0% especially because the electron project removes<00:10:01.870> the<00:10:01.990> sandbox<00:10:02.380> from<00:10:02.529> the<00:10:02.649> browser 00:10:02.819 --> 00:10:02.829 align:start position:0% removes the sandbox from the browser 00:10:02.829 --> 00:10:04.800 align:start position:0% removes the sandbox from the browser which<00:10:03.040> is<00:10:03.069> one<00:10:03.310> of<00:10:03.430> the<00:10:03.550> core<00:10:03.819> security 00:10:04.800 --> 00:10:04.810 align:start position:0% which is one of the core security 00:10:04.810 --> 00:10:11.929 align:start position:0% which is one of the core security mechanisms<00:10:06.630> so<00:10:07.740> that's<00:10:08.740> really<00:10:08.920> bad<00:10:09.189> and<00:10:10.860> it 00:10:11.929 --> 00:10:11.939 align:start position:0% mechanisms so that's really bad and it 00:10:11.939 --> 00:10:14.490 align:start position:0% mechanisms so that's really bad and it opens<00:10:12.939> a<00:10:13.060> really<00:10:13.300> large<00:10:13.540> attack<00:10:13.959> surface<00:10:14.350> for 00:10:14.490 --> 00:10:14.500 align:start position:0% opens a really large attack surface for 00:10:14.500 --> 00:10:15.870 align:start position:0% opens a really large attack surface for these<00:10:14.620> applications<00:10:15.279> and<00:10:15.459> we<00:10:15.579> should<00:10:15.759> be 00:10:15.870 --> 00:10:15.880 align:start position:0% these applications and we should be 00:10:15.880 --> 00:10:19.050 align:start position:0% these applications and we should be aware<00:10:16.000> of<00:10:16.209> this<00:10:16.509> and<00:10:16.769> there's<00:10:17.850> there's<00:10:18.850> our 00:10:19.050 --> 00:10:19.060 align:start position:0% aware of this and there's there's our 00:10:19.060 --> 00:10:21.090 align:start position:0% aware of this and there's there's our application<00:10:19.720> code<00:10:19.750> but<00:10:20.319> this<00:10:20.439> is<00:10:20.620> only<00:10:20.800> at<00:10:21.069> the 00:10:21.090 --> 00:10:21.100 align:start position:0% application code but this is only at the 00:10:21.100 --> 00:10:24.030 align:start position:0% application code but this is only at the top<00:10:21.430> our<00:10:22.120> application<00:10:22.870> has<00:10:23.050> its<00:10:23.860> own 00:10:24.030 --> 00:10:24.040 align:start position:0% top our application has its own 00:10:24.040 --> 00:10:26.189 align:start position:0% top our application has its own dependencies<00:10:24.579> to<00:10:24.639> NPM<00:10:25.120> or<00:10:25.269> yours<00:10:25.480> then<00:10:26.050> it's 00:10:26.189 --> 00:10:26.199 align:start position:0% dependencies to NPM or yours then it's 00:10:26.199 --> 00:10:27.780 align:start position:0% dependencies to NPM or yours then it's running<00:10:26.500> in<00:10:26.620> the<00:10:26.709> electron<00:10:27.130> framework<00:10:27.579> and 00:10:27.780 --> 00:10:27.790 align:start position:0% running in the electron framework and 00:10:27.790 --> 00:10:29.400 align:start position:0% running in the electron framework and the<00:10:28.209> electron<00:10:28.540> framework<00:10:28.870> has<00:10:28.990> dependencies 00:10:29.400 --> 00:10:29.410 align:start position:0% the electron framework has dependencies 00:10:29.410 --> 00:10:32.550 align:start position:0% the electron framework has dependencies to<00:10:29.800> chromium<00:10:30.220> nodejs<00:10:31.029> v<00:10:31.509> ID<00:10:31.660> and<00:10:31.990> some 00:10:32.550 --> 00:10:32.560 align:start position:0% to chromium nodejs v ID and some 00:10:32.560 --> 00:10:37.620 align:start position:0% to chromium nodejs v ID and some lower-level<00:10:34.110> api's<00:10:35.110> and<00:10:36.240> we<00:10:37.240> need<00:10:37.389> to<00:10:37.509> be 00:10:37.620 --> 00:10:37.630 align:start position:0% lower-level api's and we need to be 00:10:37.630 --> 00:10:39.870 align:start position:0% lower-level api's and we need to be aware<00:10:37.870> of<00:10:37.930> the<00:10:38.199> fact<00:10:38.410> that<00:10:38.550> every<00:10:39.550> single 00:10:39.870 --> 00:10:39.880 align:start position:0% aware of the fact that every single 00:10:39.880 --> 00:10:41.790 align:start position:0% aware of the fact that every single layer<00:10:40.029> can<00:10:40.480> be<00:10:40.600> attacked<00:10:40.930> and<00:10:41.170> was<00:10:41.410> attacked 00:10:41.790 --> 00:10:41.800 align:start position:0% layer can be attacked and was attacked 00:10:41.800 --> 00:10:44.309 align:start position:0% layer can be attacked and was attacked so<00:10:42.160> far<00:10:42.399> so<00:10:43.000> we<00:10:43.149> saw<00:10:43.329> on<00:10:43.600> an<00:10:43.750> infrastructure 00:10:44.309 --> 00:10:44.319 align:start position:0% so far so we saw on an infrastructure 00:10:44.319 --> 00:10:47.040 align:start position:0% so far so we saw on an infrastructure level<00:10:44.620> there<00:10:45.220> was<00:10:45.309> a<00:10:45.370> DNA<00:10:45.610> attack<00:10:46.149> against<00:10:46.899> my 00:10:47.040 --> 00:10:47.050 align:start position:0% level there was a DNA attack against my 00:10:47.050 --> 00:10:49.559 align:start position:0% level there was a DNA attack against my ether<00:10:47.319> wallet<00:10:47.620> then<00:10:48.399> for<00:10:48.670> electron<00:10:49.149> we've 00:10:49.559 --> 00:10:49.569 align:start position:0% ether wallet then for electron we've 00:10:49.569 --> 00:10:51.420 align:start position:0% ether wallet then for electron we've seen<00:10:49.779> a<00:10:49.809> bunch<00:10:50.019> of<00:10:50.199> node<00:10:50.889> integration 00:10:51.420 --> 00:10:51.430 align:start position:0% seen a bunch of node integration 00:10:51.430 --> 00:10:53.369 align:start position:0% seen a bunch of node integration bypasses<00:10:52.000> so<00:10:52.449> you<00:10:52.509> can<00:10:52.720> actually<00:10:52.870> turn<00:10:53.230> the 00:10:53.369 --> 00:10:53.379 align:start position:0% bypasses so you can actually turn the 00:10:53.379 --> 00:10:55.679 align:start position:0% bypasses so you can actually turn the node<00:10:53.529> integration<00:10:54.160> off<00:10:54.339> for<00:10:55.120> these<00:10:55.240> browser 00:10:55.679 --> 00:10:55.689 align:start position:0% node integration off for these browser 00:10:55.689 --> 00:10:57.990 align:start position:0% node integration off for these browser windows<00:10:56.139> but<00:10:56.410> then<00:10:56.559> we've<00:10:56.740> seen<00:10:56.949> cases<00:10:57.160> where 00:10:57.990 --> 00:10:58.000 align:start position:0% windows but then we've seen cases where 00:10:58.000 --> 00:10:59.639 align:start position:0% windows but then we've seen cases where an<00:10:58.149> application<00:10:58.600> that<00:10:58.870> was<00:10:59.050> running<00:10:59.259> in<00:10:59.589> the 00:10:59.639 --> 00:10:59.649 align:start position:0% an application that was running in the 00:10:59.649 --> 00:11:01.470 align:start position:0% an application that was running in the browser<00:10:59.920> window<00:11:00.250> could<00:11:00.790> turn<00:11:00.970> it<00:11:01.089> on<00:11:01.209> again 00:11:01.470 --> 00:11:01.480 align:start position:0% browser window could turn it on again 00:11:01.480 --> 00:11:03.240 align:start position:0% browser window could turn it on again which<00:11:01.660> completely<00:11:02.110> defeats<00:11:02.529> the<00:11:02.769> purpose<00:11:02.889> of 00:11:03.240 --> 00:11:03.250 align:start position:0% which completely defeats the purpose of 00:11:03.250 --> 00:11:05.790 align:start position:0% which completely defeats the purpose of it<00:11:03.540> and<00:11:04.540> if<00:11:04.750> this<00:11:04.899> was<00:11:05.079> not<00:11:05.230> working<00:11:05.439> they<00:11:05.680> will 00:11:05.790 --> 00:11:05.800 align:start position:0% it and if this was not working they will 00:11:05.800 --> 00:11:07.020 align:start position:0% it and if this was not working they will just<00:11:05.980> create<00:11:06.160> a<00:11:06.250> new<00:11:06.430> window 00:11:07.020 --> 00:11:07.030 align:start position:0% just create a new window 00:11:07.030 --> 00:11:08.790 align:start position:0% just create a new window that<00:11:07.150> had<00:11:07.300> note<00:11:07.480> integration<00:11:08.050> on<00:11:08.200> and<00:11:08.680> they 00:11:08.790 --> 00:11:08.800 align:start position:0% that had note integration on and they 00:11:08.800 --> 00:11:10.560 align:start position:0% that had note integration on and they would<00:11:08.950> load<00:11:09.130> itself<00:11:09.520> there<00:11:09.850> themselves<00:11:10.060> into 00:11:10.560 --> 00:11:10.570 align:start position:0% would load itself there themselves into 00:11:10.570 --> 00:11:13.050 align:start position:0% would load itself there themselves into the<00:11:10.660> new<00:11:10.780> window<00:11:11.080> and<00:11:11.290> then<00:11:12.220> they<00:11:12.370> get<00:11:12.520> full 00:11:13.050 --> 00:11:13.060 align:start position:0% the new window and then they get full 00:11:13.060 --> 00:11:15.240 align:start position:0% the new window and then they get full access<00:11:13.210> to<00:11:13.570> the<00:11:13.660> operating<00:11:13.930> system<00:11:14.110> and<00:11:14.710> it's 00:11:15.240 --> 00:11:15.250 align:start position:0% access to the operating system and it's 00:11:15.250 --> 00:11:17.280 align:start position:0% access to the operating system and it's this<00:11:15.790> is<00:11:15.970> the<00:11:16.120> security<00:11:16.630> nightmare<00:11:16.780> and<00:11:17.170> then 00:11:17.280 --> 00:11:17.290 align:start position:0% this is the security nightmare and then 00:11:17.290 --> 00:11:19.110 align:start position:0% this is the security nightmare and then they<00:11:17.410> have<00:11:17.530> full<00:11:17.740> access<00:11:17.890> to<00:11:18.100> all<00:11:18.220> your<00:11:18.400> keys 00:11:19.110 --> 00:11:19.120 align:start position:0% they have full access to all your keys 00:11:19.120 --> 00:11:21.210 align:start position:0% they have full access to all your keys and<00:11:19.390> files<00:11:19.660> and<00:11:20.080> whatever<00:11:20.620> you<00:11:20.830> store<00:11:21.040> on<00:11:21.070> your 00:11:21.210 --> 00:11:21.220 align:start position:0% and files and whatever you store on your 00:11:21.220 --> 00:11:24.150 align:start position:0% and files and whatever you store on your computer<00:11:21.610> on<00:11:22.540> the<00:11:23.170> dependency<00:11:23.740> level<00:11:24.040> we've 00:11:24.150 --> 00:11:24.160 align:start position:0% computer on the dependency level we've 00:11:24.160 --> 00:11:26.550 align:start position:0% computer on the dependency level we've seen<00:11:24.400> NPM<00:11:24.910> modules<00:11:25.840> being<00:11:26.110> hacked 00:11:26.550 --> 00:11:26.560 align:start position:0% seen NPM modules being hacked 00:11:26.560 --> 00:11:29.630 align:start position:0% seen NPM modules being hacked so<00:11:27.010> someone<00:11:27.820> created<00:11:28.150> an<00:11:28.270> NPM<00:11:28.660> module<00:11:28.990> and 00:11:29.630 --> 00:11:29.640 align:start position:0% so someone created an NPM module and 00:11:29.640 --> 00:11:31.680 align:start position:0% so someone created an NPM module and they<00:11:30.640> did<00:11:30.820> not<00:11:30.940> really<00:11:31.210> protect<00:11:31.540> their 00:11:31.680 --> 00:11:31.690 align:start position:0% they did not really protect their 00:11:31.690 --> 00:11:33.720 align:start position:0% they did not really protect their account<00:11:31.990> someone<00:11:32.350> was<00:11:32.530> able<00:11:32.860> to<00:11:32.890> hack<00:11:33.550> into 00:11:33.720 --> 00:11:33.730 align:start position:0% account someone was able to hack into 00:11:33.730 --> 00:11:36.540 align:start position:0% account someone was able to hack into this<00:11:33.970> account<00:11:34.390> they<00:11:34.930> modify<00:11:35.440> the<00:11:35.920> the<00:11:35.950> module 00:11:36.540 --> 00:11:36.550 align:start position:0% this account they modify the the module 00:11:36.550 --> 00:11:38.070 align:start position:0% this account they modify the the module code<00:11:36.790> and<00:11:37.030> then<00:11:37.420> this<00:11:37.600> module<00:11:37.930> is<00:11:38.050> a 00:11:38.070 --> 00:11:38.080 align:start position:0% code and then this module is a 00:11:38.080 --> 00:11:39.930 align:start position:0% code and then this module is a dependency<00:11:38.590> of<00:11:38.680> millions<00:11:39.040> of<00:11:39.160> other<00:11:39.370> projects 00:11:39.930 --> 00:11:39.940 align:start position:0% dependency of millions of other projects 00:11:39.940 --> 00:11:42.060 align:start position:0% dependency of millions of other projects and<00:11:40.090> they<00:11:40.300> can<00:11:40.480> infect<00:11:40.870> in<00:11:41.140> fact<00:11:41.620> millions<00:11:41.830> of 00:11:42.060 --> 00:11:42.070 align:start position:0% and they can infect in fact millions of 00:11:42.070 --> 00:11:45.000 align:start position:0% and they can infect in fact millions of other<00:11:42.220> of<00:11:42.340> projects<00:11:43.050> on<00:11:44.050> the<00:11:44.290> application 00:11:45.000 --> 00:11:45.010 align:start position:0% other of projects on the application 00:11:45.010 --> 00:11:47.280 align:start position:0% other of projects on the application level<00:11:45.400> we<00:11:45.700> see<00:11:45.910> a<00:11:45.940> bunch<00:11:46.210> of<00:11:46.450> cross-site 00:11:47.280 --> 00:11:47.290 align:start position:0% level we see a bunch of cross-site 00:11:47.290 --> 00:11:48.780 align:start position:0% level we see a bunch of cross-site scripting<00:11:47.680> attacks<00:11:48.040> which<00:11:48.250> is<00:11:48.370> probably<00:11:48.640> the 00:11:48.780 --> 00:11:48.790 align:start position:0% scripting attacks which is probably the 00:11:48.790 --> 00:11:50.580 align:start position:0% scripting attacks which is probably the the<00:11:49.360> most<00:11:49.540> dominant<00:11:49.960> thread<00:11:50.260> they<00:11:50.470> are 00:11:50.580 --> 00:11:50.590 align:start position:0% the most dominant thread they are 00:11:50.590 --> 00:11:52.620 align:start position:0% the most dominant thread they are especially<00:11:51.340> don't<00:11:51.880> cross-site<00:11:52.210> scripting 00:11:52.620 --> 00:11:52.630 align:start position:0% especially don't cross-site scripting 00:11:52.630 --> 00:11:57.510 align:start position:0% especially don't cross-site scripting for<00:11:52.810> electronics<00:11:55.470> another<00:11:56.470> big<00:11:56.770> really<00:11:57.310> big 00:11:57.510 --> 00:11:57.520 align:start position:0% for electronics another big really big 00:11:57.520 --> 00:12:00.180 align:start position:0% for electronics another big really big thing<00:11:57.730> for<00:11:57.760> us<00:11:58.020> updates<00:11:59.020> that<00:11:59.590> are<00:11:59.620> security 00:12:00.180 --> 00:12:00.190 align:start position:0% thing for us updates that are security 00:12:00.190 --> 00:12:02.520 align:start position:0% thing for us updates that are security critical<00:12:00.400> and<00:12:00.790> I<00:12:00.850> want<00:12:01.000> to<00:12:01.090> show<00:12:01.240> you<00:12:01.300> why 00:12:02.520 --> 00:12:02.530 align:start position:0% critical and I want to show you why 00:12:02.530 --> 00:12:06.060 align:start position:0% critical and I want to show you why so<00:12:02.950> for<00:12:03.250> with<00:12:03.910> mists<00:12:04.150> for<00:12:04.330> example<00:12:04.780> in<00:12:05.650> version 00:12:06.060 --> 00:12:06.070 align:start position:0% so for with mists for example in version 00:12:06.070 --> 00:12:08.760 align:start position:0% so for with mists for example in version 10<00:12:06.640> 10<00:12:07.390> we<00:12:07.540> have<00:12:07.660> dependency<00:12:08.440> two-electron 00:12:08.760 --> 00:12:08.770 align:start position:0% 10 10 we have dependency two-electron 00:12:08.770 --> 00:12:11.670 align:start position:0% 10 10 we have dependency two-electron 1.8<00:12:09.490> in<00:12:10.090> version<00:12:10.690> 11<00:12:10.780> we<00:12:11.080> have<00:12:11.140> a<00:12:11.230> dependency 00:12:11.670 --> 00:12:11.680 align:start position:0% 1.8 in version 11 we have a dependency 00:12:11.680 --> 00:12:15.180 align:start position:0% 1.8 in version 11 we have a dependency two-electron<00:12:11.980> -<00:12:12.420> so<00:12:13.420> I<00:12:13.450> I<00:12:13.870> said<00:12:14.830> it<00:12:14.920> before 00:12:15.180 --> 00:12:15.190 align:start position:0% two-electron - so I I said it before 00:12:15.190 --> 00:12:17.490 align:start position:0% two-electron - so I I said it before electron<00:12:16.090> has<00:12:16.210> its<00:12:16.360> own<00:12:16.510> set<00:12:16.750> of<00:12:16.780> dependencies 00:12:17.490 --> 00:12:17.500 align:start position:0% electron has its own set of dependencies 00:12:17.500 --> 00:12:19.980 align:start position:0% electron has its own set of dependencies so<00:12:17.710> electron<00:12:18.340> 1.48<00:12:19.210> for<00:12:19.480> example<00:12:19.840> has<00:12:19.930> a 00:12:19.980 --> 00:12:19.990 align:start position:0% so electron 1.48 for example has a 00:12:19.990 --> 00:12:23.820 align:start position:0% so electron 1.48 for example has a dependency<00:12:20.500> to<00:12:20.650> chromium<00:12:20.920> 59<00:12:21.520> then<00:12:22.270> node<00:12:22.830> 88.2 00:12:23.820 --> 00:12:23.830 align:start position:0% dependency to chromium 59 then node 88.2 00:12:23.830 --> 00:12:26.700 align:start position:0% dependency to chromium 59 then node 88.2 and<00:12:24.130> v8<00:12:24.370> 5.9<00:12:25.060> and<00:12:25.330> electron<00:12:26.230> two<00:12:26.440> has<00:12:26.680> a 00:12:26.700 --> 00:12:26.710 align:start position:0% and v8 5.9 and electron two has a 00:12:26.710 --> 00:12:29.880 align:start position:0% and v8 5.9 and electron two has a dependency<00:12:27.400> to<00:12:27.520> chromium<00:12:27.760> 61<00:12:28.420> node<00:12:28.990> 8.9<00:12:29.650> and 00:12:29.880 --> 00:12:29.890 align:start position:0% dependency to chromium 61 node 8.9 and 00:12:29.890 --> 00:12:32.250 align:start position:0% dependency to chromium 61 node 8.9 and v8<00:12:30.100> 6.1<00:12:30.730> and<00:12:30.910> the<00:12:31.270> latest<00:12:31.570> version<00:12:31.960> is<00:12:32.140> for 00:12:32.250 --> 00:12:32.260 align:start position:0% v8 6.1 and the latest version is for 00:12:32.260 --> 00:12:35.070 align:start position:0% v8 6.1 and the latest version is for chromium<00:12:32.560> 71<00:12:33.250> for<00:12:33.760> note<00:12:33.910> it's<00:12:34.090> 11<00:12:34.480> and<00:12:34.570> for<00:12:34.780> v8 00:12:35.070 --> 00:12:35.080 align:start position:0% chromium 71 for note it's 11 and for v8 00:12:35.080 --> 00:12:37.350 align:start position:0% chromium 71 for note it's 11 and for v8 and<00:12:35.230> 7<00:12:35.560> and<00:12:36.430> you<00:12:36.580> don't<00:12:36.730> have<00:12:36.850> to<00:12:37.000> remember<00:12:37.210> all 00:12:37.350 --> 00:12:37.360 align:start position:0% and 7 and you don't have to remember all 00:12:37.360 --> 00:12:39.300 align:start position:0% and 7 and you don't have to remember all these<00:12:37.630> numbers<00:12:37.990> I<00:12:38.170> will<00:12:38.680> break<00:12:38.830> it<00:12:38.980> down<00:12:39.070> for 00:12:39.300 --> 00:12:39.310 align:start position:0% these numbers I will break it down for 00:12:39.310 --> 00:12:43.350 align:start position:0% these numbers I will break it down for you<00:12:39.520> the<00:12:40.270> latest<00:12:40.450> version<00:12:41.050> is<00:12:41.470> 71<00:12:42.340> the<00:12:42.940> version 00:12:43.350 --> 00:12:43.360 align:start position:0% you the latest version is 71 the version 00:12:43.360 --> 00:12:45.600 align:start position:0% you the latest version is 71 the version that<00:12:43.720> is<00:12:43.840> used<00:12:44.140> as<00:12:44.440> a<00:12:44.500> dependency<00:12:45.010> of<00:12:45.310> our 00:12:45.600 --> 00:12:45.610 align:start position:0% that is used as a dependency of our 00:12:45.610 --> 00:12:48.930 align:start position:0% that is used as a dependency of our electron<00:12:46.090> dependency<00:12:46.540> a<00:12:46.570> 61<00:12:47.460> that's<00:12:48.460> a<00:12:48.670> 10 00:12:48.930 --> 00:12:48.940 align:start position:0% electron dependency a 61 that's a 10 00:12:48.940 --> 00:12:50.790 align:start position:0% electron dependency a 61 that's a 10 version<00:12:49.120> difference<00:12:49.680> chromium<00:12:50.680> has<00:12:50.740> a 00:12:50.790 --> 00:12:50.800 align:start position:0% version difference chromium has a 00:12:50.800 --> 00:12:53.130 align:start position:0% version difference chromium has a release<00:12:51.280> cycle<00:12:51.460> of<00:12:51.670> 6<00:12:51.910> weeks<00:12:52.150> that's<00:12:52.600> a<00:12:52.750> 60 00:12:53.130 --> 00:12:53.140 align:start position:0% release cycle of 6 weeks that's a 60 00:12:53.140 --> 00:12:55.500 align:start position:0% release cycle of 6 weeks that's a 60 week<00:12:53.290> difference<00:12:53.710> in<00:12:53.920> Petra's<00:12:54.670> security 00:12:55.500 --> 00:12:55.510 align:start position:0% week difference in Petra's security 00:12:55.510 --> 00:12:57.690 align:start position:0% week difference in Petra's security updates<00:12:55.900> bug<00:12:56.350> fixes<00:12:56.860> more<00:12:57.280> than<00:12:57.430> a<00:12:57.460> year 00:12:57.690 --> 00:12:57.700 align:start position:0% updates bug fixes more than a year 00:12:57.700 --> 00:13:00.120 align:start position:0% updates bug fixes more than a year outdated<00:12:58.240> and<00:12:58.660> it's<00:12:59.170> even<00:12:59.380> worse<00:12:59.530> because<00:12:59.830> we 00:13:00.120 --> 00:13:00.130 align:start position:0% outdated and it's even worse because we 00:13:00.130 --> 00:13:02.820 align:start position:0% outdated and it's even worse because we get<00:13:00.250> this<00:13:00.510> the<00:13:01.510> responsible<00:13:02.320> is<00:13:02.410> closed<00:13:02.620> our 00:13:02.820 --> 00:13:02.830 align:start position:0% get this the responsible is closed our 00:13:02.830 --> 00:13:06.390 align:start position:0% get this the responsible is closed our timeline<00:13:03.310> for<00:13:04.290> v8<00:13:05.290> bucks<00:13:05.560> for<00:13:05.770> example<00:13:06.160> is<00:13:06.220> not 00:13:06.390 --> 00:13:06.400 align:start position:0% timeline for v8 bucks for example is not 00:13:06.400 --> 00:13:08.700 align:start position:0% timeline for v8 bucks for example is not one<00:13:06.670> year<00:13:06.880> it's<00:13:07.090> a<00:13:07.210> couple<00:13:07.480> of<00:13:07.570> weeks<00:13:07.810> so<00:13:08.590> we 00:13:08.700 --> 00:13:08.710 align:start position:0% one year it's a couple of weeks so we 00:13:08.710 --> 00:13:12.240 align:start position:0% one year it's a couple of weeks so we have<00:13:08.890> documented<00:13:09.880> exploits<00:13:10.330> such<00:13:11.200> as<00:13:11.410> this<00:13:11.620> s 00:13:12.240 --> 00:13:12.250 align:start position:0% have documented exploits such as this s 00:13:12.250 --> 00:13:15.120 align:start position:0% have documented exploits such as this s this<00:13:12.550> v8<00:13:13.090> integer<00:13:13.600> overflow<00:13:14.020> and<00:13:14.800> you<00:13:14.950> can 00:13:15.120 --> 00:13:15.130 align:start position:0% this v8 integer overflow and you can 00:13:15.130 --> 00:13:17.760 align:start position:0% this v8 integer overflow and you can find<00:13:15.340> it<00:13:15.430> online<00:13:15.580> this<00:13:16.450> is<00:13:16.810> a<00:13:16.930> is<00:13:17.290> an<00:13:17.440> attack 00:13:17.760 --> 00:13:17.770 align:start position:0% find it online this is a is an attack 00:13:17.770 --> 00:13:20.040 align:start position:0% find it online this is a is an attack that<00:13:17.800> works<00:13:18.190> in<00:13:18.370> old<00:13:18.550> outdated<00:13:18.850> browsers<00:13:19.570> it 00:13:20.040 --> 00:13:20.050 align:start position:0% that works in old outdated browsers it 00:13:20.050 --> 00:13:20.970 align:start position:0% that works in old outdated browsers it also<00:13:20.260> works<00:13:20.530> for<00:13:20.710> every 00:13:20.970 --> 00:13:20.980 align:start position:0% also works for every 00:13:20.980 --> 00:13:23.160 align:start position:0% also works for every electronic<00:13:21.490> that<00:13:21.880> is<00:13:22.060> still<00:13:22.269> on<00:13:22.420> 1.8<00:13:22.990> for 00:13:23.160 --> 00:13:23.170 align:start position:0% electronic that is still on 1.8 for 00:13:23.170 --> 00:13:27.750 align:start position:0% electronic that is still on 1.8 for example<00:13:25.740> another<00:13:26.740> big<00:13:27.160> problem 00:13:27.750 --> 00:13:27.760 align:start position:0% example another big problem 00:13:27.760 --> 00:13:29.970 align:start position:0% example another big problem who<00:13:28.540> is<00:13:28.690> reinstalling<00:13:29.230> their<00:13:29.470> browser<00:13:29.680> when 00:13:29.970 --> 00:13:29.980 align:start position:0% who is reinstalling their browser when 00:13:29.980 --> 00:13:33.090 align:start position:0% who is reinstalling their browser when they<00:13:30.130> want<00:13:30.279> to<00:13:30.399> refresh<00:13:30.730> a<00:13:30.790> web<00:13:31.029> page<00:13:31.209> I<00:13:32.100> hope 00:13:33.090 --> 00:13:33.100 align:start position:0% they want to refresh a web page I hope 00:13:33.100 --> 00:13:34.980 align:start position:0% they want to refresh a web page I hope no<00:13:33.310> one<00:13:33.490> does<00:13:33.699> this<00:13:33.910> because<00:13:34.300> this<00:13:34.660> is<00:13:34.720> what 00:13:34.980 --> 00:13:34.990 align:start position:0% no one does this because this is what 00:13:34.990 --> 00:13:37.590 align:start position:0% no one does this because this is what crazy<00:13:35.440> people<00:13:35.680> do<00:13:35.949> but<00:13:36.579> this<00:13:36.730> is<00:13:36.940> our<00:13:37.149> update 00:13:37.590 --> 00:13:37.600 align:start position:0% crazy people do but this is our update 00:13:37.600 --> 00:13:39.000 align:start position:0% crazy people do but this is our update model<00:13:37.930> right<00:13:38.019> now<00:13:38.170> with<00:13:38.350> all<00:13:38.380> the<00:13:38.649> electron 00:13:39.000 --> 00:13:39.010 align:start position:0% model right now with all the electron 00:13:39.010 --> 00:13:41.250 align:start position:0% model right now with all the electron apps<00:13:39.220> so<00:13:39.820> in<00:13:39.970> order<00:13:40.120> to<00:13:40.360> push<00:13:40.570> a<00:13:40.600> very<00:13:40.899> very 00:13:41.250 --> 00:13:41.260 align:start position:0% apps so in order to push a very very 00:13:41.260 --> 00:13:43.290 align:start position:0% apps so in order to push a very very simple<00:13:41.589> change<00:13:41.889> to<00:13:41.949> the<00:13:42.160> user<00:13:42.339> interface<00:13:42.790> we 00:13:43.290 --> 00:13:43.300 align:start position:0% simple change to the user interface we 00:13:43.300 --> 00:13:44.879 align:start position:0% simple change to the user interface we would<00:13:43.449> have<00:13:43.630> to<00:13:43.779> go<00:13:43.930> through<00:13:44.680> the<00:13:44.769> whole 00:13:44.879 --> 00:13:44.889 align:start position:0% would have to go through the whole 00:13:44.889 --> 00:13:46.800 align:start position:0% would have to go through the whole process<00:13:45.130> or<00:13:45.399> process<00:13:45.940> of<00:13:46.000> reinstalling<00:13:46.540> all 00:13:46.800 --> 00:13:46.810 align:start position:0% process or process of reinstalling all 00:13:46.810 --> 00:13:48.329 align:start position:0% process or process of reinstalling all the<00:13:46.930> binaries<00:13:47.290> that<00:13:47.320> come<00:13:47.649> with<00:13:47.769> it<00:13:47.860> which 00:13:48.329 --> 00:13:48.339 align:start position:0% the binaries that come with it which 00:13:48.339 --> 00:13:51.569 align:start position:0% the binaries that come with it which gives<00:13:48.490> you<00:13:48.670> a<00:13:48.699> sec<00:13:48.940> 60<00:13:49.389> megabyte<00:13:49.839> update<00:13:50.579> you 00:13:51.569 --> 00:13:51.579 align:start position:0% gives you a sec 60 megabyte update you 00:13:51.579 --> 00:13:53.730 align:start position:0% gives you a sec 60 megabyte update you need<00:13:51.730> to<00:13:51.880> download<00:13:52.269> a<00:13:52.420> new<00:13:52.540> installer<00:13:53.440> and 00:13:53.730 --> 00:13:53.740 align:start position:0% need to download a new installer and 00:13:53.740 --> 00:13:55.230 align:start position:0% need to download a new installer and then<00:13:53.920> run<00:13:54.100> through<00:13:54.250> the<00:13:54.310> whole<00:13:54.670> process<00:13:54.940> of 00:13:55.230 --> 00:13:55.240 align:start position:0% then run through the whole process of 00:13:55.240 --> 00:13:57.960 align:start position:0% then run through the whole process of updating<00:13:55.540> a<00:13:55.839> new<00:13:55.959> browser<00:13:56.230> basically<00:13:56.970> just 00:13:57.960 --> 00:13:57.970 align:start position:0% updating a new browser basically just 00:13:57.970 --> 00:14:00.900 align:start position:0% updating a new browser basically just for<00:13:58.209> very<00:13:58.810> small<00:13:58.959> changes<00:13:59.470> so<00:14:00.310> we<00:14:00.430> saw<00:14:00.610> these 00:14:00.900 --> 00:14:00.910 align:start position:0% for very small changes so we saw these 00:14:00.910 --> 00:14:03.470 align:start position:0% for very small changes so we saw these problems<00:14:01.389> and<00:14:02.260> we<00:14:02.350> wanted<00:14:02.620> to<00:14:02.709> fix<00:14:02.889> them<00:14:03.160> and 00:14:03.470 --> 00:14:03.480 align:start position:0% problems and we wanted to fix them and 00:14:03.480 --> 00:14:05.939 align:start position:0% problems and we wanted to fix them and we<00:14:04.480> did<00:14:04.630> this<00:14:04.779> with<00:14:04.839> our<00:14:05.139> internal<00:14:05.470> project 00:14:05.939 --> 00:14:05.949 align:start position:0% we did this with our internal project 00:14:05.949 --> 00:14:09.300 align:start position:0% we did this with our internal project called<00:14:06.100> tau<00:14:06.870> so<00:14:07.870> what<00:14:07.990> is<00:14:08.079> tau<00:14:08.290> tau<00:14:08.620> is<00:14:08.800> also 00:14:09.300 --> 00:14:09.310 align:start position:0% called tau so what is tau tau is also 00:14:09.310 --> 00:14:10.980 align:start position:0% called tau so what is tau tau is also chromium<00:14:09.699> it's<00:14:09.850> not<00:14:10.000> yes<00:14:10.269> it<00:14:10.540> has<00:14:10.779> native 00:14:10.980 --> 00:14:10.990 align:start position:0% chromium it's not yes it has native 00:14:10.990 --> 00:14:13.860 align:start position:0% chromium it's not yes it has native api's<00:14:11.699> but<00:14:12.699> we're<00:14:12.850> doing<00:14:13.000> a<00:14:13.269> bunch<00:14:13.540> of<00:14:13.660> things 00:14:13.860 --> 00:14:13.870 align:start position:0% api's but we're doing a bunch of things 00:14:13.870 --> 00:14:15.750 align:start position:0% api's but we're doing a bunch of things in<00:14:14.170> a<00:14:14.230> different<00:14:14.350> way<00:14:14.709> so<00:14:14.920> for<00:14:15.399> example 00:14:15.750 --> 00:14:15.760 align:start position:0% in a different way so for example 00:14:15.760 --> 00:14:17.460 align:start position:0% in a different way so for example there's<00:14:15.940> no<00:14:16.089> node.js<00:14:16.360> integration<00:14:17.139> anymore 00:14:17.460 --> 00:14:17.470 align:start position:0% there's no node.js integration anymore 00:14:17.470 --> 00:14:19.379 align:start position:0% there's no node.js integration anymore we<00:14:18.160> are<00:14:18.190> also<00:14:18.370> not<00:14:18.610> using<00:14:18.850> the<00:14:19.149> chromium 00:14:19.379 --> 00:14:19.389 align:start position:0% we are also not using the chromium 00:14:19.389 --> 00:14:22.170 align:start position:0% we are also not using the chromium content<00:14:20.010> that<00:14:21.010> is<00:14:21.130> used<00:14:21.310> in<00:14:21.550> electron<00:14:22.029> but 00:14:22.170 --> 00:14:22.180 align:start position:0% content that is used in electron but 00:14:22.180 --> 00:14:25.199 align:start position:0% content that is used in electron but we're<00:14:22.329> using<00:14:22.449> CF<00:14:23.019> and<00:14:23.290> CF<00:14:24.010> is<00:14:24.250> maintained<00:14:25.120> by 00:14:25.199 --> 00:14:25.209 align:start position:0% we're using CF and CF is maintained by 00:14:25.209 --> 00:14:26.730 align:start position:0% we're using CF and CF is maintained by Spotify<00:14:25.690> and<00:14:25.839> they're<00:14:25.959> doing<00:14:26.110> a<00:14:26.260> really<00:14:26.290> great 00:14:26.730 --> 00:14:26.740 align:start position:0% Spotify and they're doing a really great 00:14:26.740 --> 00:14:28.949 align:start position:0% Spotify and they're doing a really great job<00:14:26.949> in<00:14:27.160> providing<00:14:27.819> really<00:14:28.180> recent<00:14:28.569> updates 00:14:28.949 --> 00:14:28.959 align:start position:0% job in providing really recent updates 00:14:28.959 --> 00:14:32.670 align:start position:0% job in providing really recent updates for<00:14:29.649> the<00:14:29.860> chromium<00:14:30.130> v8<00:14:30.699> and<00:14:30.940> Noem<00:14:31.779> chromium 00:14:32.670 --> 00:14:32.680 align:start position:0% for the chromium v8 and Noem chromium 00:14:32.680 --> 00:14:35.850 align:start position:0% for the chromium v8 and Noem chromium and<00:14:32.800> v8<00:14:33.040> dependencies<00:14:33.610> for<00:14:33.760> the<00:14:33.819> browser<00:14:34.860> we 00:14:35.850 --> 00:14:35.860 align:start position:0% and v8 dependencies for the browser we 00:14:35.860 --> 00:14:39.030 align:start position:0% and v8 dependencies for the browser we also<00:14:36.180> have<00:14:37.180> the<00:14:37.660> advantage<00:14:37.959> that<00:14:38.319> chromium 00:14:39.030 --> 00:14:39.040 align:start position:0% also have the advantage that chromium 00:14:39.040 --> 00:14:41.129 align:start position:0% also have the advantage that chromium embedded<00:14:39.490> framework<00:14:39.819> allows<00:14:40.060> us<00:14:40.269> to<00:14:40.660> enable<00:14:40.899> a 00:14:41.129 --> 00:14:41.139 align:start position:0% embedded framework allows us to enable a 00:14:41.139 --> 00:14:43.800 align:start position:0% embedded framework allows us to enable a full<00:14:41.350> sandbox<00:14:41.800> and<00:14:42.389> for<00:14:43.389> the<00:14:43.480> back-end 00:14:43.800 --> 00:14:43.810 align:start position:0% full sandbox and for the back-end 00:14:43.810 --> 00:14:46.530 align:start position:0% full sandbox and for the back-end process<00:14:44.220> we<00:14:45.220> can<00:14:45.399> use<00:14:45.519> whatever<00:14:45.850> we<00:14:46.029> want<00:14:46.240> so 00:14:46.530 --> 00:14:46.540 align:start position:0% process we can use whatever we want so 00:14:46.540 --> 00:14:48.449 align:start position:0% process we can use whatever we want so we<00:14:46.660> can<00:14:46.839> update<00:14:47.019> to<00:14:47.290> the<00:14:47.410> latest<00:14:47.440> v8<00:14:48.010> version 00:14:48.449 --> 00:14:48.459 align:start position:0% we can update to the latest v8 version 00:14:48.459 --> 00:14:50.699 align:start position:0% we can update to the latest v8 version which<00:14:48.970> which<00:14:49.180> is<00:14:49.209> version<00:14:49.510> 7<00:14:49.990> and<00:14:50.170> we<00:14:50.560> can 00:14:50.699 --> 00:14:50.709 align:start position:0% which which is version 7 and we can 00:14:50.709 --> 00:14:52.230 align:start position:0% which which is version 7 and we can update<00:14:50.889> to<00:14:51.100> the<00:14:51.190> latest<00:14:51.220> node.js<00:14:51.670> which<00:14:51.940> is 00:14:52.230 --> 00:14:52.240 align:start position:0% update to the latest node.js which is 00:14:52.240 --> 00:14:54.870 align:start position:0% update to the latest node.js which is version<00:14:52.630> 11<00:14:53.019> and<00:14:53.199> then<00:14:54.100> we<00:14:54.130> get<00:14:54.399> this<00:14:54.610> nice 00:14:54.870 --> 00:14:54.880 align:start position:0% version 11 and then we get this nice 00:14:54.880 --> 00:14:58.710 align:start position:0% version 11 and then we get this nice benefits<00:14:55.779> so<00:14:56.410> the<00:14:57.130> 8<00:14:57.250> version<00:14:57.459> 7<00:14:57.880> was<00:14:58.180> released 00:14:58.710 --> 00:14:58.720 align:start position:0% benefits so the 8 version 7 was released 00:14:58.720 --> 00:15:00.660 align:start position:0% benefits so the 8 version 7 was released two<00:14:58.870> weeks<00:14:58.899> ago<00:14:59.319> and<00:14:59.620> it<00:14:59.949> comes<00:15:00.130> with<00:15:00.220> web 00:15:00.660 --> 00:15:00.670 align:start position:0% two weeks ago and it comes with web 00:15:00.670 --> 00:15:03.240 align:start position:0% two weeks ago and it comes with web assembly<00:15:01.120> support<00:15:01.510> for<00:15:01.630> 4<00:15:01.990> threads<00:15:02.250> and 00:15:03.240 --> 00:15:03.250 align:start position:0% assembly support for 4 threads and 00:15:03.250 --> 00:15:04.410 align:start position:0% assembly support for 4 threads and that's<00:15:03.430> pretty<00:15:03.610> cool<00:15:03.819> if<00:15:03.970> you<00:15:04.000> think<00:15:04.300> about 00:15:04.410 --> 00:15:04.420 align:start position:0% that's pretty cool if you think about 00:15:04.420 --> 00:15:06.120 align:start position:0% that's pretty cool if you think about all<00:15:04.839> the<00:15:05.199> stuff<00:15:05.230> that<00:15:05.470> we<00:15:05.769> have<00:15:05.889> on<00:15:06.010> our 00:15:06.120 --> 00:15:06.130 align:start position:0% all the stuff that we have on our 00:15:06.130 --> 00:15:08.670 align:start position:0% all the stuff that we have on our roadmap<00:15:06.459> for<00:15:07.029> it<00:15:07.540> wasn't<00:15:07.899> for<00:15:08.079> example<00:15:08.529> that 00:15:08.670 --> 00:15:08.680 align:start position:0% roadmap for it wasn't for example that 00:15:08.680 --> 00:15:10.199 align:start position:0% roadmap for it wasn't for example that rely<00:15:08.949> on<00:15:08.980> newer<00:15:09.490> features<00:15:09.910> that<00:15:10.029> are<00:15:10.180> not 00:15:10.199 --> 00:15:10.209 align:start position:0% rely on newer features that are not 00:15:10.209 --> 00:15:14.309 align:start position:0% rely on newer features that are not available<00:15:10.360> in<00:15:10.899> all<00:15:11.050> browsers<00:15:11.500> yet<00:15:13.170> we<00:15:14.170> also 00:15:14.309 --> 00:15:14.319 align:start position:0% available in all browsers yet we also 00:15:14.319 --> 00:15:16.379 align:start position:0% available in all browsers yet we also have<00:15:14.529> these<00:15:14.680> advantages<00:15:15.610> because<00:15:15.790> we<00:15:16.060> get<00:15:16.149> all 00:15:16.379 --> 00:15:16.389 align:start position:0% have these advantages because we get all 00:15:16.389 --> 00:15:18.870 align:start position:0% have these advantages because we get all the<00:15:16.569> benefits<00:15:16.990> all<00:15:17.290> the<00:15:17.680> changes<00:15:18.190> to<00:15:18.339> no<00:15:18.490> js' 00:15:18.870 --> 00:15:18.880 align:start position:0% the benefits all the changes to no js' 00:15:18.880 --> 00:15:20.610 align:start position:0% the benefits all the changes to no js' all<00:15:19.120> these<00:15:19.300> like<00:15:19.750> bug<00:15:19.959> fixes<00:15:20.470> and 00:15:20.610 --> 00:15:20.620 align:start position:0% all these like bug fixes and 00:15:20.620 --> 00:15:22.050 align:start position:0% all these like bug fixes and improvements<00:15:20.709> to<00:15:21.130> the<00:15:21.339> crypto<00:15:21.639> API<00:15:21.670> for 00:15:22.050 --> 00:15:22.060 align:start position:0% improvements to the crypto API for 00:15:22.060 --> 00:15:24.030 align:start position:0% improvements to the crypto API for example<00:15:22.240> and<00:15:22.779> many<00:15:23.230> of<00:15:23.440> the<00:15:23.620> crypto 00:15:24.030 --> 00:15:24.040 align:start position:0% example and many of the crypto 00:15:24.040 --> 00:15:26.970 align:start position:0% example and many of the crypto algorithms<00:15:24.579> that<00:15:25.269> we<00:15:25.449> need<00:15:25.660> to<00:15:26.380> achieve<00:15:26.529> our 00:15:26.970 --> 00:15:26.980 align:start position:0% algorithms that we need to achieve our 00:15:26.980 --> 00:15:30.300 align:start position:0% algorithms that we need to achieve our goals<00:15:27.279> with<00:15:27.639> a<00:15:27.880> theorem<00:15:28.800> getting<00:15:29.800> implemented 00:15:30.300 --> 00:15:30.310 align:start position:0% goals with a theorem getting implemented 00:15:30.310 --> 00:15:32.009 align:start position:0% goals with a theorem getting implemented are<00:15:30.430> already<00:15:30.939> implemented<00:15:31.540> in<00:15:31.630> your<00:15:31.660> note 00:15:32.009 --> 00:15:32.019 align:start position:0% are already implemented in your note 00:15:32.019 --> 00:15:34.560 align:start position:0% are already implemented in your note versions<00:15:32.410> so<00:15:32.769> that's<00:15:33.000> that<00:15:34.000> that's<00:15:34.240> a 00:15:34.560 --> 00:15:34.570 align:start position:0% versions so that's that that's a 00:15:34.570 --> 00:15:37.500 align:start position:0% versions so that's that that's a have<00:15:34.690> benefit<00:15:35.110> as<00:15:35.230> well<00:15:35.850> so<00:15:36.850> who's<00:15:37.000> using<00:15:37.180> Tao 00:15:37.500 --> 00:15:37.510 align:start position:0% have benefit as well so who's using Tao 00:15:37.510 --> 00:15:41.250 align:start position:0% have benefit as well so who's using Tao pretty<00:15:38.320> much<00:15:38.440> no<00:15:38.620> one<00:15:38.740> is<00:15:38.860> using<00:15:39.010> this<00:15:40.260> except 00:15:41.250 --> 00:15:41.260 align:start position:0% pretty much no one is using this except 00:15:41.260 --> 00:15:43.460 align:start position:0% pretty much no one is using this except maybe<00:15:41.440> our<00:15:41.860> little<00:15:42.430> like<00:15:42.970> proof-of-concept 00:15:43.460 --> 00:15:43.470 align:start position:0% maybe our little like proof-of-concept 00:15:43.470 --> 00:15:46.350 align:start position:0% maybe our little like proof-of-concept project<00:15:44.470> and<00:15:44.890> that's<00:15:45.220> a<00:15:45.370> good<00:15:45.520> thing<00:15:45.580> because 00:15:46.350 --> 00:15:46.360 align:start position:0% project and that's a good thing because 00:15:46.360 --> 00:15:48.570 align:start position:0% project and that's a good thing because electron<00:15:47.170> is<00:15:47.380> a<00:15:47.560> one-size-fits-all<00:15:48.070> solution 00:15:48.570 --> 00:15:48.580 align:start position:0% electron is a one-size-fits-all solution 00:15:48.580 --> 00:15:50.640 align:start position:0% electron is a one-size-fits-all solution and<00:15:49.300> you<00:15:49.660> have<00:15:49.750> to<00:15:49.840> think<00:15:50.050> about<00:15:50.200> it<00:15:50.470> they're 00:15:50.640 --> 00:15:50.650 align:start position:0% and you have to think about it they're 00:15:50.650 --> 00:15:52.560 align:start position:0% and you have to think about it they're going<00:15:50.890> through<00:15:51.070> the<00:15:51.220> full<00:15:51.670> bureaucracy 00:15:52.560 --> 00:15:52.570 align:start position:0% going through the full bureaucracy 00:15:52.570 --> 00:15:54.690 align:start position:0% going through the full bureaucracy the<00:15:52.870> full<00:15:53.590> backporting<00:15:54.280> they<00:15:54.400> need<00:15:54.610> to 00:15:54.690 --> 00:15:54.700 align:start position:0% the full backporting they need to 00:15:54.700 --> 00:15:56.490 align:start position:0% the full backporting they need to coordinate<00:15:55.210> with<00:15:55.300> Microsoft<00:15:55.930> with<00:15:56.110> get<00:15:56.320> up 00:15:56.490 --> 00:15:56.500 align:start position:0% coordinate with Microsoft with get up 00:15:56.500 --> 00:15:58.620 align:start position:0% coordinate with Microsoft with get up with<00:15:56.710> slag<00:15:57.190> and<00:15:57.430> all<00:15:57.880> the<00:15:58.030> other<00:15:58.180> applications 00:15:58.620 --> 00:15:58.630 align:start position:0% with slag and all the other applications 00:15:58.630 --> 00:16:01.140 align:start position:0% with slag and all the other applications that<00:15:58.990> we<00:15:59.080> just<00:15:59.260> saw<00:15:59.500> when<00:16:00.310> they<00:16:00.460> want<00:16:00.670> to<00:16:00.850> make 00:16:01.140 --> 00:16:01.150 align:start position:0% that we just saw when they want to make 00:16:01.150 --> 00:16:02.850 align:start position:0% that we just saw when they want to make a<00:16:01.210> breaking<00:16:01.630> change<00:16:01.960> it<00:16:02.230> will<00:16:02.440> take<00:16:02.620> forever 00:16:02.850 --> 00:16:02.860 align:start position:0% a breaking change it will take forever 00:16:02.860 --> 00:16:05.250 align:start position:0% a breaking change it will take forever just<00:16:03.280> because<00:16:03.670> they<00:16:04.300> need<00:16:04.480> to<00:16:04.600> coordinate<00:16:04.840> it 00:16:05.250 --> 00:16:05.260 align:start position:0% just because they need to coordinate it 00:16:05.260 --> 00:16:07.860 align:start position:0% just because they need to coordinate it very<00:16:05.860> well<00:16:06.100> they<00:16:06.700> cannot<00:16:06.970> just<00:16:07.240> break<00:16:07.600> all 00:16:07.860 --> 00:16:07.870 align:start position:0% very well they cannot just break all 00:16:07.870 --> 00:16:09.960 align:start position:0% very well they cannot just break all these<00:16:08.020> applications<00:16:08.260> and<00:16:08.920> we<00:16:09.760> have<00:16:09.850> the 00:16:09.960 --> 00:16:09.970 align:start position:0% these applications and we have the 00:16:09.970 --> 00:16:12.180 align:start position:0% these applications and we have the benefit<00:16:10.390> that<00:16:10.420> we<00:16:10.570> can<00:16:10.840> actually<00:16:11.470> we<00:16:12.040> can 00:16:12.180 --> 00:16:12.190 align:start position:0% benefit that we can actually we can 00:16:12.190 --> 00:16:15.510 align:start position:0% benefit that we can actually we can break<00:16:12.400> things<00:16:12.670> we<00:16:12.820> can<00:16:12.970> move<00:16:13.120> first<00:16:14.100> so<00:16:15.100> it's<00:16:15.460> a 00:16:15.510 --> 00:16:15.520 align:start position:0% break things we can move first so it's a 00:16:15.520 --> 00:16:17.430 align:start position:0% break things we can move first so it's a really<00:16:15.670> small<00:16:15.940> project<00:16:16.660> so<00:16:16.840> far<00:16:17.050> I<00:16:17.080> think<00:16:17.230> it's 00:16:17.430 --> 00:16:17.440 align:start position:0% really small project so far I think it's 00:16:17.440 --> 00:16:20.760 align:start position:0% really small project so far I think it's extremely<00:16:17.860> promising<00:16:19.170> it's<00:16:20.170> not<00:16:20.380> meant 00:16:20.760 --> 00:16:20.770 align:start position:0% extremely promising it's not meant 00:16:20.770 --> 00:16:22.860 align:start position:0% extremely promising it's not meant really<00:16:21.220> for<00:16:21.490> the<00:16:21.550> mainstream<00:16:21.790> but<00:16:22.150> I<00:16:22.210> think 00:16:22.860 --> 00:16:22.870 align:start position:0% really for the mainstream but I think 00:16:22.870 --> 00:16:25.260 align:start position:0% really for the mainstream but I think it's<00:16:23.020> it's<00:16:23.530> good<00:16:23.800> that<00:16:24.010> that<00:16:24.400> we<00:16:24.850> that<00:16:25.120> we're 00:16:25.260 --> 00:16:25.270 align:start position:0% it's it's good that that we that we're 00:16:25.270 --> 00:16:26.640 align:start position:0% it's it's good that that we that we're bringing<00:16:25.450> out<00:16:25.690> this<00:16:25.900> message<00:16:26.110> now<00:16:26.260> that<00:16:26.560> it 00:16:26.640 --> 00:16:26.650 align:start position:0% bringing out this message now that it 00:16:26.650 --> 00:16:29.550 align:start position:0% bringing out this message now that it exists<00:16:27.100> and<00:16:27.280> it<00:16:28.060> already<00:16:28.270> has<00:16:28.570> pre-built 00:16:29.550 --> 00:16:29.560 align:start position:0% exists and it already has pre-built 00:16:29.560 --> 00:16:31.260 align:start position:0% exists and it already has pre-built binaries<00:16:29.980> so<00:16:30.010> you<00:16:30.220> can<00:16:30.460> actually<00:16:30.670> test<00:16:31.060> it<00:16:31.120> out 00:16:31.260 --> 00:16:31.270 align:start position:0% binaries so you can actually test it out 00:16:31.270 --> 00:16:33.240 align:start position:0% binaries so you can actually test it out it<00:16:31.510> the<00:16:31.720> pre-built<00:16:32.200> binaries<00:16:32.590> are<00:16:32.740> working<00:16:33.040> on 00:16:33.240 --> 00:16:33.250 align:start position:0% it the pre-built binaries are working on 00:16:33.250 --> 00:16:35.190 align:start position:0% it the pre-built binaries are working on Mac<00:16:33.880> and<00:16:34.060> Windows<00:16:34.180> so<00:16:34.510> far<00:16:34.690> they're<00:16:34.870> they<00:16:35.170> are 00:16:35.190 --> 00:16:35.200 align:start position:0% Mac and Windows so far they're they are 00:16:35.200 --> 00:16:36.690 align:start position:0% Mac and Windows so far they're they are known<00:16:35.410> for<00:16:35.440> for<00:16:35.860> Linux<00:16:36.130> but<00:16:36.310> we<00:16:36.400> will<00:16:36.520> probably 00:16:36.690 --> 00:16:36.700 align:start position:0% known for for Linux but we will probably 00:16:36.700 --> 00:16:39.750 align:start position:0% known for for Linux but we will probably provide<00:16:37.270> them<00:16:37.480> within<00:16:37.630> the<00:16:37.840> next<00:16:37.870> weeks<00:16:38.760> and 00:16:39.750 --> 00:16:39.760 align:start position:0% provide them within the next weeks and 00:16:39.760 --> 00:16:41.820 align:start position:0% provide them within the next weeks and this<00:16:40.000> is<00:16:40.060> how<00:16:40.270> it<00:16:40.360> looks<00:16:40.540> like<00:16:40.600> you<00:16:41.500> won't<00:16:41.680> see 00:16:41.820 --> 00:16:41.830 align:start position:0% this is how it looks like you won't see 00:16:41.830 --> 00:16:43.470 align:start position:0% this is how it looks like you won't see a<00:16:41.860> difference<00:16:42.250> to<00:16:42.430> a<00:16:42.460> regular<00:16:42.790> Chrome<00:16:43.060> browser 00:16:43.470 --> 00:16:43.480 align:start position:0% a difference to a regular Chrome browser 00:16:43.480 --> 00:16:45.570 align:start position:0% a difference to a regular Chrome browser or<00:16:43.630> electron<00:16:44.020> application<00:16:44.590> you<00:16:45.220> will<00:16:45.370> see 00:16:45.570 --> 00:16:45.580 align:start position:0% or electron application you will see 00:16:45.580 --> 00:16:47.550 align:start position:0% or electron application you will see this<00:16:46.090> is<00:16:46.240> our<00:16:46.360> new<00:16:46.570> mist<00:16:46.810> UI<00:16:46.960> react 00:16:47.550 --> 00:16:47.560 align:start position:0% this is our new mist UI react 00:16:47.560 --> 00:16:50.040 align:start position:0% this is our new mist UI react running<00:16:48.010> in<00:16:48.130> one<00:16:48.250> of<00:16:48.370> the<00:16:48.490> tower<00:16:48.670> windows<00:16:49.050> so 00:16:50.040 --> 00:16:50.050 align:start position:0% running in one of the tower windows so 00:16:50.050 --> 00:16:52.140 align:start position:0% running in one of the tower windows so it's<00:16:50.230> it's<00:16:51.010> a<00:16:51.130> browser<00:16:51.310> window<00:16:51.580> and<00:16:51.880> we<00:16:52.000> can 00:16:52.140 --> 00:16:52.150 align:start position:0% it's it's a browser window and we can 00:16:52.150 --> 00:16:53.940 align:start position:0% it's it's a browser window and we can control<00:16:52.510> and<00:16:52.750> customize<00:16:52.930> it<00:16:53.410> and<00:16:53.530> we<00:16:53.650> can<00:16:53.800> run 00:16:53.940 --> 00:16:53.950 align:start position:0% control and customize it and we can run 00:16:53.950 --> 00:16:55.830 align:start position:0% control and customize it and we can run application<00:16:54.580> code<00:16:54.730> and<00:16:54.910> it<00:16:55.270> has<00:16:55.450> all<00:16:55.690> the 00:16:55.830 --> 00:16:55.840 align:start position:0% application code and it has all the 00:16:55.840 --> 00:16:56.970 align:start position:0% application code and it has all the updates<00:16:56.170> that<00:16:56.290> we<00:16:56.470> need<00:16:56.650> and<00:16:56.860> all<00:16:56.920> the 00:16:56.970 --> 00:16:56.980 align:start position:0% updates that we need and all the 00:16:56.980 --> 00:16:59.610 align:start position:0% updates that we need and all the benefits<00:16:57.190> that<00:16:57.520> we<00:16:57.700> want<00:16:57.880> and<00:16:58.330> we<00:16:59.320> also 00:16:59.610 --> 00:16:59.620 align:start position:0% benefits that we want and we also 00:16:59.620 --> 00:17:01.890 align:start position:0% benefits that we want and we also introduced<00:17:00.160> this<00:17:00.340> new<00:17:00.550> update<00:17:00.880> mechanism<00:17:01.450> to 00:17:01.890 --> 00:17:01.900 align:start position:0% introduced this new update mechanism to 00:17:01.900 --> 00:17:03.660 align:start position:0% introduced this new update mechanism to avoid<00:17:02.020> this<00:17:02.470> these<00:17:02.710> painful<00:17:03.010> long<00:17:03.400> release 00:17:03.660 --> 00:17:03.670 align:start position:0% avoid this these painful long release 00:17:03.670 --> 00:17:06.300 align:start position:0% avoid this these painful long release cycles<00:17:04.150> where<00:17:05.140> we<00:17:05.260> actually<00:17:05.620> split<00:17:05.890> our 00:17:06.300 --> 00:17:06.310 align:start position:0% cycles where we actually split our 00:17:06.310 --> 00:17:08.819 align:start position:0% cycles where we actually split our application<00:17:07.240> into<00:17:07.449> multiple<00:17:07.930> multiple<00:17:08.560> paths 00:17:08.819 --> 00:17:08.829 align:start position:0% application into multiple multiple paths 00:17:08.829 --> 00:17:10.860 align:start position:0% application into multiple multiple paths so<00:17:09.370> the<00:17:09.459> user<00:17:09.610> interface<00:17:10.270> is<00:17:10.420> updated 00:17:10.860 --> 00:17:10.870 align:start position:0% so the user interface is updated 00:17:10.870 --> 00:17:13.020 align:start position:0% so the user interface is updated separately<00:17:11.410> and<00:17:11.860> then<00:17:12.459> we<00:17:12.610> have<00:17:12.699> something 00:17:13.020 --> 00:17:13.030 align:start position:0% separately and then we have something 00:17:13.030 --> 00:17:14.280 align:start position:0% separately and then we have something that<00:17:13.150> we<00:17:13.240> call<00:17:13.420> the<00:17:13.449> shell<00:17:13.810> or<00:17:14.020> the<00:17:14.110> browser 00:17:14.280 --> 00:17:14.290 align:start position:0% that we call the shell or the browser 00:17:14.290 --> 00:17:16.949 align:start position:0% that we call the shell or the browser window<00:17:14.740> and<00:17:14.920> this<00:17:15.730> becomes<00:17:16.089> interchangeable 00:17:16.949 --> 00:17:16.959 align:start position:0% window and this becomes interchangeable 00:17:16.959 --> 00:17:19.590 align:start position:0% window and this becomes interchangeable so<00:17:17.079> we<00:17:17.170> can<00:17:17.380> switch<00:17:17.650> between<00:17:18.070> electron<00:17:18.760> or<00:17:19.270> tau 00:17:19.590 --> 00:17:19.600 align:start position:0% so we can switch between electron or tau 00:17:19.600 --> 00:17:22.650 align:start position:0% so we can switch between electron or tau as<00:17:19.900> long<00:17:20.620> as<00:17:20.800> we<00:17:20.949> have<00:17:21.070> an<00:17:21.220> API<00:17:21.520> that<00:17:22.329> the<00:17:22.480> user 00:17:22.650 --> 00:17:22.660 align:start position:0% as long as we have an API that the user 00:17:22.660 --> 00:17:24.480 align:start position:0% as long as we have an API that the user interface<00:17:23.230> communicates<00:17:23.920> with<00:17:24.070> and<00:17:24.370> our 00:17:24.480 --> 00:17:24.490 align:start position:0% interface communicates with and our 00:17:24.490 --> 00:17:26.520 align:start position:0% interface communicates with and our application<00:17:24.699> logic<00:17:25.180> communicates<00:17:25.900> with<00:17:26.079> we 00:17:26.520 --> 00:17:26.530 align:start position:0% application logic communicates with we 00:17:26.530 --> 00:17:28.590 align:start position:0% application logic communicates with we can<00:17:26.740> run<00:17:26.949> updates<00:17:27.250> pretty<00:17:27.850> much<00:17:27.970> every<00:17:28.300> day<00:17:28.449> or 00:17:28.590 --> 00:17:28.600 align:start position:0% can run updates pretty much every day or 00:17:28.600 --> 00:17:31.670 align:start position:0% can run updates pretty much every day or every<00:17:28.720> week<00:17:28.990> have<00:17:29.280> for<00:17:30.280> all<00:17:30.430> these<00:17:30.580> parts<00:17:30.970> and 00:17:31.670 --> 00:17:31.680 align:start position:0% every week have for all these parts and 00:17:31.680 --> 00:17:33.990 align:start position:0% every week have for all these parts and this<00:17:32.680> is<00:17:32.800> the<00:17:33.040> what<00:17:33.280> we<00:17:33.400> call<00:17:33.580> the<00:17:33.610> app<00:17:33.790> shell 00:17:33.990 --> 00:17:34.000 align:start position:0% this is the what we call the app shell 00:17:34.000 --> 00:17:35.670 align:start position:0% this is the what we call the app shell model<00:17:34.300> and<00:17:34.420> there<00:17:34.570> will<00:17:34.660> probably<00:17:34.690> be<00:17:35.140> a<00:17:35.320> blog 00:17:35.670 --> 00:17:35.680 align:start position:0% model and there will probably be a blog 00:17:35.680 --> 00:17:40.640 align:start position:0% model and there will probably be a blog post<00:17:35.920> following<00:17:36.280> on<00:17:36.970> our<00:17:37.680> on<00:17:38.680> our<00:17:39.400> medium<00:17:39.730> blog 00:17:40.640 --> 00:17:40.650 align:start position:0% post following on our on our medium blog 00:17:40.650 --> 00:17:43.830 align:start position:0% post following on our on our medium blog we<00:17:41.650> also<00:17:41.770> have<00:17:41.980> a<00:17:42.040> bunch<00:17:42.250> of<00:17:42.660> modules<00:17:43.660> and 00:17:43.830 --> 00:17:43.840 align:start position:0% we also have a bunch of modules and 00:17:43.840 --> 00:17:45.360 align:start position:0% we also have a bunch of modules and reference<00:17:44.260> implementations<00:17:45.070> if<00:17:45.220> you're 00:17:45.360 --> 00:17:45.370 align:start position:0% reference implementations if you're 00:17:45.370 --> 00:17:47.160 align:start position:0% reference implementations if you're interested<00:17:45.790> to<00:17:45.880> check<00:17:45.910> it<00:17:46.240> out<00:17:46.360> there 00:17:47.160 --> 00:17:47.170 align:start position:0% interested to check it out there 00:17:47.170 --> 00:17:49.050 align:start position:0% interested to check it out there the<00:17:47.740> mist<00:17:47.920> UI<00:17:48.040> react<00:17:48.370> project<00:17:48.790> that<00:17:48.940> is 00:17:49.050 --> 00:17:49.060 align:start position:0% the mist UI react project that is 00:17:49.060 --> 00:17:52.170 align:start position:0% the mist UI react project that is working<00:17:49.780> in<00:17:49.900> Tao<00:17:50.140> and<00:17:50.440> an<00:17:50.650> electron<00:17:51.130> was<00:17:51.910> just 00:17:52.170 --> 00:17:52.180 align:start position:0% working in Tao and an electron was just 00:17:52.180 --> 00:17:56.010 align:start position:0% working in Tao and an electron was just recently<00:17:52.390> adopted<00:17:52.810> by<00:17:53.080> the<00:17:53.140> etherium<00:17:55.020> if 00:17:56.010 --> 00:17:56.020 align:start position:0% recently adopted by the etherium if 00:17:56.020 --> 00:17:58.140 align:start position:0% recently adopted by the etherium if human<00:17:56.410> getup<00:17:56.620> repository<00:17:57.340> and<00:17:57.550> then<00:17:57.910> there's 00:17:58.140 --> 00:17:58.150 align:start position:0% human getup repository and then there's 00:17:58.150 --> 00:17:59.970 align:start position:0% human getup repository and then there's create<00:17:58.450> direct<00:17:58.690> create<00:17:59.320> react<00:17:59.770> app 00:17:59.970 --> 00:17:59.980 align:start position:0% create direct create react app 00:17:59.980 --> 00:18:02.160 align:start position:0% create direct create react app extensions<00:18:00.610> which<00:18:01.090> turns<00:18:01.360> every<00:18:01.720> react<00:18:02.020> app 00:18:02.160 --> 00:18:02.170 align:start position:0% extensions which turns every react app 00:18:02.170 --> 00:18:04.890 align:start position:0% extensions which turns every react app into<00:18:02.500> an<00:18:02.650> electron<00:18:03.130> towel<00:18:03.490> container<00:18:03.940> as<00:18:04.330> you 00:18:04.890 --> 00:18:04.900 align:start position:0% into an electron towel container as you 00:18:04.900 --> 00:18:06.870 align:start position:0% into an electron towel container as you can<00:18:05.050> call<00:18:05.290> it<00:18:05.440> then<00:18:05.950> there's<00:18:06.160> an<00:18:06.310> update<00:18:06.640> that 00:18:06.870 --> 00:18:06.880 align:start position:0% can call it then there's an update that 00:18:06.880 --> 00:18:08.670 align:start position:0% can call it then there's an update that does<00:18:07.030> hot<00:18:07.270> updating<00:18:07.810> for<00:18:08.020> these<00:18:08.140> containers 00:18:08.670 --> 00:18:08.680 align:start position:0% does hot updating for these containers 00:18:08.680 --> 00:18:10.920 align:start position:0% does hot updating for these containers for<00:18:08.890> electron<00:18:09.280> or<00:18:09.400> Tao<00:18:09.550> apps<00:18:09.790> and<00:18:10.030> then<00:18:10.780> we 00:18:10.920 --> 00:18:10.930 align:start position:0% for electron or Tao apps and then we 00:18:10.930 --> 00:18:12.750 align:start position:0% for electron or Tao apps and then we have<00:18:11.080> a<00:18:11.110> reference<00:18:11.410> implementation<00:18:11.740> for<00:18:12.370> the 00:18:12.750 --> 00:18:12.760 align:start position:0% have a reference implementation for the 00:18:12.760 --> 00:18:14.640 align:start position:0% have a reference implementation for the electron<00:18:13.360> shell<00:18:13.570> and<00:18:13.750> the<00:18:13.840> tour<00:18:14.020> shell<00:18:14.260> that 00:18:14.640 --> 00:18:14.650 align:start position:0% electron shell and the tour shell that 00:18:14.650 --> 00:18:17.330 align:start position:0% electron shell and the tour shell that can<00:18:14.830> actually<00:18:14.980> host<00:18:15.340> one<00:18:15.940> of<00:18:15.970> these<00:18:16.240> electron 00:18:17.330 --> 00:18:17.340 align:start position:0% can actually host one of these electron 00:18:17.340 --> 00:18:21.480 align:start position:0% can actually host one of these electron react<00:18:18.340> apps<00:18:18.610> for<00:18:18.820> electron<00:18:19.210> water<00:18:19.360> and<00:18:20.490> that's 00:18:21.480 --> 00:18:21.490 align:start position:0% react apps for electron water and that's 00:18:21.490 --> 00:18:21.840 align:start position:0% react apps for electron water and that's it 00:18:21.840 --> 00:18:21.850 align:start position:0% it 00:18:21.850 --> 00:18:24.110 align:start position:0% it and<00:18:22.480> if<00:18:23.020> you're<00:18:23.140> interested<00:18:23.500> in<00:18:23.620> any<00:18:23.740> of<00:18:23.830> this 00:18:24.110 --> 00:18:24.120 align:start position:0% and if you're interested in any of this 00:18:24.120 --> 00:18:28.200 align:start position:0% and if you're interested in any of this you<00:18:25.120> can<00:18:25.270> come<00:18:25.480> talk<00:18:25.690> to<00:18:25.750> me<00:18:26.610> or<00:18:27.610> you<00:18:27.790> can<00:18:27.970> just 00:18:28.200 --> 00:18:28.210 align:start position:0% you can come talk to me or you can just 00:18:28.210 --> 00:18:30.870 align:start position:0% you can come talk to me or you can just reach<00:18:28.360> out<00:18:28.540> via<00:18:28.600> my<00:18:29.140> github<00:18:29.830> or<00:18:30.250> my<00:18:30.610> mail 00:18:30.870 --> 00:18:30.880 align:start position:0% reach out via my github or my mail 00:18:30.880 --> 00:18:36.470 align:start position:0% reach out via my github or my mail thanks 00:18:36.470 --> 00:18:36.480 align:start position:0% 00:18:36.480 --> 00:18:38.910 align:start position:0% my<00:18:37.480> thoughts<00:18:37.690> about<00:18:37.900> note<00:18:38.080> WebKit<00:18:38.440> yeah<00:18:38.680> I 00:18:38.910 --> 00:18:38.920 align:start position:0% my thoughts about note WebKit yeah I 00:18:38.920 --> 00:18:41.730 align:start position:0% my thoughts about note WebKit yeah I think<00:18:39.310> one<00:18:39.580> of<00:18:39.610> the<00:18:39.940> of<00:18:40.240> the<00:18:40.450> cool<00:18:40.660> benefits<00:18:41.560> of 00:18:41.730 --> 00:18:41.740 align:start position:0% think one of the of the cool benefits of 00:18:41.740 --> 00:18:43.950 align:start position:0% think one of the of the cool benefits of electron<00:18:42.130> is<00:18:42.250> the<00:18:42.520> the<00:18:42.760> community<00:18:43.240> so<00:18:43.630> I<00:18:43.660> I 00:18:43.950 --> 00:18:43.960 align:start position:0% electron is the the community so I I 00:18:43.960 --> 00:18:45.840 align:start position:0% electron is the the community so I I said<00:18:44.110> it's<00:18:44.410> a<00:18:44.560> disadvantage<00:18:44.830> it<00:18:45.310> can<00:18:45.490> also<00:18:45.670> be 00:18:45.840 --> 00:18:45.850 align:start position:0% said it's a disadvantage it can also be 00:18:45.850 --> 00:18:47.460 align:start position:0% said it's a disadvantage it can also be considered<00:18:46.120> as<00:18:46.360> an<00:18:46.480> advantage<00:18:46.900> because<00:18:47.290> you 00:18:47.460 --> 00:18:47.470 align:start position:0% considered as an advantage because you 00:18:47.470 --> 00:18:49.560 align:start position:0% considered as an advantage because you actually<00:18:47.710> have<00:18:48.280> this<00:18:48.490> like<00:18:48.790> large<00:18:49.060> community 00:18:49.560 --> 00:18:49.570 align:start position:0% actually have this like large community 00:18:49.570 --> 00:18:50.850 align:start position:0% actually have this like large community and<00:18:49.660> we<00:18:49.720> have<00:18:49.810> the<00:18:49.900> same<00:18:50.080> forum<00:18:50.470> you<00:18:50.590> see<00:18:50.740> the 00:18:50.850 --> 00:18:50.860 align:start position:0% and we have the same forum you see the 00:18:50.860 --> 00:18:52.740 align:start position:0% and we have the same forum you see the benefits<00:18:51.280> of<00:18:51.400> many<00:18:51.610> projects<00:18:52.120> already<00:18:52.300> using 00:18:52.740 --> 00:18:52.750 align:start position:0% benefits of many projects already using 00:18:52.750 --> 00:18:54.690 align:start position:0% benefits of many projects already using these<00:18:52.870> technologies<00:18:53.200> you<00:18:53.890> get<00:18:54.070> already<00:18:54.430> tools 00:18:54.690 --> 00:18:54.700 align:start position:0% these technologies you get already tools 00:18:54.700 --> 00:18:56.970 align:start position:0% these technologies you get already tools for<00:18:55.060> black<00:18:55.420> building<00:18:55.690> update<00:18:56.200> and<00:18:56.680> update 00:18:56.970 --> 00:18:56.980 align:start position:0% for black building update and update 00:18:56.980 --> 00:19:00.990 align:start position:0% for black building update and update mechanisms<00:18:57.870> signing<00:18:58.870> applications<00:19:00.000> or 00:19:00.990 --> 00:19:01.000 align:start position:0% mechanisms signing applications or 00:19:01.000 --> 00:19:03.300 align:start position:0% mechanisms signing applications or creating<00:19:01.360> installers<00:19:01.870> and<00:19:02.110> I<00:19:02.470> think<00:19:02.710> this<00:19:02.830> the 00:19:03.300 --> 00:19:03.310 align:start position:0% creating installers and I think this the 00:19:03.310 --> 00:19:04.830 align:start position:0% creating installers and I think this the whole<00:19:03.460> ecosystem<00:19:03.730> for<00:19:04.180> electron<00:19:04.510> is<00:19:04.630> just 00:19:04.830 --> 00:19:04.840 align:start position:0% whole ecosystem for electron is just 00:19:04.840 --> 00:19:06.690 align:start position:0% whole ecosystem for electron is just better<00:19:05.290> than<00:19:05.530> for<00:19:05.770> node<00:19:05.920> then<00:19:06.310> for<00:19:06.520> node 00:19:06.690 --> 00:19:06.700 align:start position:0% better than for node then for node 00:19:06.700 --> 00:19:09.150 align:start position:0% better than for node then for node WebKit<00:19:07.180> but<00:19:07.990> I<00:19:08.020> think<00:19:08.260> node<00:19:08.380> WebKit<00:19:08.740> is<00:19:08.770> a<00:19:08.890> cool 00:19:09.150 --> 00:19:09.160 align:start position:0% WebKit but I think node WebKit is a cool 00:19:09.160 --> 00:19:12.540 align:start position:0% WebKit but I think node WebKit is a cool project<00:19:09.340> and<00:19:09.870> it<00:19:10.870> it<00:19:11.320> also<00:19:11.530> goes<00:19:12.100> in<00:19:12.280> a<00:19:12.370> very 00:19:12.540 --> 00:19:12.550 align:start position:0% project and it it also goes in a very 00:19:12.550 --> 00:19:14.910 align:start position:0% project and it it also goes in a very similar<00:19:12.760> direction<00:19:13.300> so<00:19:13.510> yeah<00:19:13.990> so<00:19:14.620> you<00:19:14.680> said 00:19:14.910 --> 00:19:14.920 align:start position:0% similar direction so yeah so you said 00:19:14.920 --> 00:19:18.420 align:start position:0% similar direction so yeah so you said that<00:19:15.130> Tao<00:19:15.970> is<00:19:16.000> kind<00:19:16.600> of<00:19:16.660> like<00:19:16.900> in<00:19:17.080> a<00:19:17.400> kind<00:19:18.400> of 00:19:18.420 --> 00:19:18.430 align:start position:0% that Tao is kind of like in a kind of 00:19:18.430 --> 00:19:20.640 align:start position:0% that Tao is kind of like in a kind of beta<00:19:18.670> sandbox<00:19:19.390> development<00:19:20.080> and<00:19:20.380> you're<00:19:20.500> not 00:19:20.640 --> 00:19:20.650 align:start position:0% beta sandbox development and you're not 00:19:20.650 --> 00:19:22.800 align:start position:0% beta sandbox development and you're not really<00:19:20.890> saying<00:19:21.550> hey<00:19:21.760> let's<00:19:22.030> start<00:19:22.210> using<00:19:22.480> Tao 00:19:22.800 --> 00:19:22.810 align:start position:0% really saying hey let's start using Tao 00:19:22.810 --> 00:19:24.540 align:start position:0% really saying hey let's start using Tao at<00:19:23.320> what<00:19:23.440> point<00:19:23.710> should<00:19:23.830> those<00:19:24.250> other 00:19:24.540 --> 00:19:24.550 align:start position:0% at what point should those other 00:19:24.550 --> 00:19:26.760 align:start position:0% at what point should those other applications<00:19:24.880> start<00:19:25.630> using<00:19:26.200> Tao<00:19:26.530> and 00:19:26.760 --> 00:19:26.770 align:start position:0% applications start using Tao and 00:19:26.770 --> 00:19:28.920 align:start position:0% applications start using Tao and integrating<00:19:27.310> that<00:19:27.480> yeah<00:19:28.480> that's<00:19:28.750> a<00:19:28.840> good 00:19:28.920 --> 00:19:28.930 align:start position:0% integrating that yeah that's a good 00:19:28.930 --> 00:19:31.200 align:start position:0% integrating that yeah that's a good question<00:19:29.080> there<00:19:29.830> was<00:19:29.920> no<00:19:30.130> like<00:19:30.520> real<00:19:30.730> roadmap 00:19:31.200 --> 00:19:31.210 align:start position:0% question there was no like real roadmap 00:19:31.210 --> 00:19:33.690 align:start position:0% question there was no like real roadmap there<00:19:31.480> was<00:19:31.600> never<00:19:31.900> the<00:19:32.110> idea<00:19:32.440> that<00:19:32.710> this<00:19:33.220> could 00:19:33.690 --> 00:19:33.700 align:start position:0% there was never the idea that this could 00:19:33.700 --> 00:19:35.310 align:start position:0% there was never the idea that this could become<00:19:33.880> something<00:19:34.390> really<00:19:34.630> big<00:19:34.810> and<00:19:34.870> I<00:19:35.110> think 00:19:35.310 --> 00:19:35.320 align:start position:0% become something really big and I think 00:19:35.320 --> 00:19:37.080 align:start position:0% become something really big and I think that<00:19:35.470> it<00:19:35.890> was<00:19:36.040> also<00:19:36.280> not<00:19:36.430> the<00:19:36.520> intention<00:19:36.850> to 00:19:37.080 --> 00:19:37.090 align:start position:0% that it was also not the intention to 00:19:37.090 --> 00:19:39.030 align:start position:0% that it was also not the intention to make<00:19:37.270> it<00:19:37.450> a<00:19:37.570> competitor<00:19:38.170> to<00:19:38.320> electron<00:19:38.740> for 00:19:39.030 --> 00:19:39.040 align:start position:0% make it a competitor to electron for 00:19:39.040 --> 00:19:41.520 align:start position:0% make it a competitor to electron for example<00:19:39.070> and<00:19:39.780> we<00:19:40.780> started<00:19:41.050> with<00:19:41.170> a<00:19:41.200> proof<00:19:41.440> of 00:19:41.520 --> 00:19:41.530 align:start position:0% example and we started with a proof of 00:19:41.530 --> 00:19:43.290 align:start position:0% example and we started with a proof of concept<00:19:41.710> the<00:19:42.100> proof<00:19:42.280> of<00:19:42.400> concept<00:19:42.550> look<00:19:43.000> really 00:19:43.290 --> 00:19:43.300 align:start position:0% concept the proof of concept look really 00:19:43.300 --> 00:19:44.970 align:start position:0% concept the proof of concept look really promising<00:19:43.780> and<00:19:43.960> now<00:19:44.290> we're<00:19:44.440> seeing<00:19:44.590> like<00:19:44.800> all 00:19:44.970 --> 00:19:44.980 align:start position:0% promising and now we're seeing like all 00:19:44.980 --> 00:19:47.280 align:start position:0% promising and now we're seeing like all these<00:19:45.150> additional<00:19:46.150> benefits<00:19:46.630> and<00:19:46.930> and 00:19:47.280 --> 00:19:47.290 align:start position:0% these additional benefits and and 00:19:47.290 --> 00:19:49.140 align:start position:0% these additional benefits and and possibilities<00:19:48.040> how<00:19:48.190> it<00:19:48.310> could<00:19:48.490> integrate 00:19:49.140 --> 00:19:49.150 align:start position:0% possibilities how it could integrate 00:19:49.150 --> 00:19:50.700 align:start position:0% possibilities how it could integrate with<00:19:49.480> other<00:19:49.660> aphelion<00:19:50.140> projects<00:19:50.560> such<00:19:50.680> as 00:19:50.700 --> 00:19:50.710 align:start position:0% with other aphelion projects such as 00:19:50.710 --> 00:19:53.100 align:start position:0% with other aphelion projects such as remakes<00:19:51.400> or<00:19:51.700> the<00:19:51.880> the<00:19:52.150> holy<00:19:52.330> was<00:19:52.690> enough<00:19:52.930> for 00:19:53.100 --> 00:19:53.110 align:start position:0% remakes or the the holy was enough for 00:19:53.110 --> 00:19:56.130 align:start position:0% remakes or the the holy was enough for efforts<00:19:53.710> and<00:19:53.980> swarm<00:19:54.580> and<00:19:54.820> I<00:19:55.360> think<00:19:55.570> yeah<00:19:56.110> I 00:19:56.130 --> 00:19:56.140 align:start position:0% efforts and swarm and I think yeah I 00:19:56.140 --> 00:19:58.180 align:start position:0% efforts and swarm and I think yeah I think<00:19:56.260> it<00:19:56.500> looks<00:19:56.650> really<00:19:56.860> promising<00:19:57.010> and 00:19:58.180 --> 00:19:58.190 align:start position:0% think it looks really promising and 00:19:58.190 --> 00:19:59.769 align:start position:0% think it looks really promising and we<00:19:58.279> will<00:19:58.399> probably<00:19:58.549> focus<00:19:59.149> all<00:19:59.360> of<00:19:59.389> our<00:19:59.600> energy 00:19:59.769 --> 00:19:59.779 align:start position:0% we will probably focus all of our energy 00:19:59.779 --> 00:20:02.680 align:start position:0% we will probably focus all of our energy to<00:20:00.200> make<00:20:00.350> it<00:20:00.379> the<00:20:01.039> perfect<00:20:01.610> fit<00:20:01.909> for<00:20:02.149> these 00:20:02.680 --> 00:20:02.690 align:start position:0% to make it the perfect fit for these 00:20:02.690 --> 00:20:04.570 align:start position:0% to make it the perfect fit for these applications<00:20:02.899> and<00:20:03.559> not<00:20:03.740> any<00:20:03.919> other<00:20:04.190> like 00:20:04.570 --> 00:20:04.580 align:start position:0% applications and not any other like 00:20:04.580 --> 00:20:06.039 align:start position:0% applications and not any other like mainstream<00:20:05.000> applications<00:20:05.600> they<00:20:05.750> should 00:20:06.039 --> 00:20:06.049 align:start position:0% mainstream applications they should 00:20:06.049 --> 00:20:08.220 align:start position:0% mainstream applications they should probably<00:20:06.230> try<00:20:06.529> to<00:20:06.649> use<00:20:06.950> electron<00:20:07.460> and<00:20:07.610> just 00:20:08.220 --> 00:20:08.230 align:start position:0% probably try to use electron and just 00:20:08.230 --> 00:20:10.330 align:start position:0% probably try to use electron and just put<00:20:09.230> some<00:20:09.379> pressure<00:20:09.500> on<00:20:09.679> them<00:20:09.860> so<00:20:10.039> that<00:20:10.190> they 00:20:10.330 --> 00:20:10.340 align:start position:0% put some pressure on them so that they 00:20:10.340 --> 00:20:14.200 align:start position:0% put some pressure on them so that they they<00:20:10.669> fix<00:20:11.029> their<00:20:11.980> about<00:20:13.029> security<00:20:14.029> of 00:20:14.200 --> 00:20:14.210 align:start position:0% they fix their about security of 00:20:14.210 --> 00:20:17.519 align:start position:0% they fix their about security of you<00:20:14.419> perform<00:20:14.809> any<00:20:14.929> security<00:20:15.889> I<00:20:15.980> Tonto<00:20:16.549> and 00:20:17.519 --> 00:20:17.529 align:start position:0% you perform any security I Tonto and 00:20:17.529 --> 00:20:21.190 align:start position:0% you perform any security I Tonto and second<00:20:18.529> question<00:20:18.919> have<00:20:19.730> you<00:20:19.759> put<00:20:20.090> into<00:20:20.779> the 00:20:21.190 --> 00:20:21.200 align:start position:0% second question have you put into the 00:20:21.200 --> 00:20:23.590 align:start position:0% second question have you put into the like<00:20:21.889> continuous<00:20:22.490> integration<00:20:22.850> filling 00:20:23.590 --> 00:20:23.600 align:start position:0% like continuous integration filling 00:20:23.600 --> 00:20:26.200 align:start position:0% like continuous integration filling systems<00:20:24.019> that<00:20:24.200> have<00:20:24.320> been<00:20:24.350> built<00:20:25.070> by<00:20:25.210> Martine 00:20:26.200 --> 00:20:26.210 align:start position:0% systems that have been built by Martine 00:20:26.210 --> 00:20:30.639 align:start position:0% systems that have been built by Martine and<00:20:26.860> indeed<00:20:27.860> oh<00:20:28.240> the<00:20:29.240> answer<00:20:29.629> is<00:20:29.659> no<00:20:30.259> and<00:20:30.500> no 00:20:30.639 --> 00:20:30.649 align:start position:0% and indeed oh the answer is no and no 00:20:30.649 --> 00:20:32.649 align:start position:0% and indeed oh the answer is no and no Soto<00:20:31.190> is<00:20:31.399> not<00:20:31.610> was<00:20:31.850> not<00:20:32.029> going<00:20:32.330> through<00:20:32.629> a 00:20:32.649 --> 00:20:32.659 align:start position:0% Soto is not was not going through a 00:20:32.659 --> 00:20:35.320 align:start position:0% Soto is not was not going through a security<00:20:33.049> audit<00:20:33.350> and<00:20:33.679> missed<00:20:34.460> of<00:20:34.669> course<00:20:34.909> was 00:20:35.320 --> 00:20:35.330 align:start position:0% security audit and missed of course was 00:20:35.330 --> 00:20:38.740 align:start position:0% security audit and missed of course was going<00:20:35.600> through<00:20:35.779> a<00:20:35.899> very<00:20:37.299> very<00:20:38.299> complete 00:20:38.740 --> 00:20:38.750 align:start position:0% going through a very very complete 00:20:38.750 --> 00:20:40.210 align:start position:0% going through a very very complete security<00:20:39.080> audit<00:20:39.620> we<00:20:39.740> learned<00:20:39.919> a<00:20:40.039> lot<00:20:40.159> from 00:20:40.210 --> 00:20:40.220 align:start position:0% security audit we learned a lot from 00:20:40.220 --> 00:20:42.759 align:start position:0% security audit we learned a lot from from<00:20:40.970> these<00:20:41.120> lessons<00:20:41.419> and<00:20:41.929> from<00:20:42.289> this<00:20:42.440> audit 00:20:42.759 --> 00:20:42.769 align:start position:0% from these lessons and from this audit 00:20:42.769 --> 00:20:45.249 align:start position:0% from these lessons and from this audit and<00:20:42.950> we<00:20:43.250> try<00:20:43.490> to<00:20:43.549> incorporate<00:20:43.940> all<00:20:44.419> the<00:20:44.659> these 00:20:45.249 --> 00:20:45.259 align:start position:0% and we try to incorporate all the these 00:20:45.259 --> 00:20:48.279 align:start position:0% and we try to incorporate all the these things<00:20:45.710> that<00:20:45.889> we<00:20:46.039> learned<00:20:46.250> into<00:20:46.820> tau<00:20:47.000> but<00:20:47.629> it 00:20:48.279 --> 00:20:48.289 align:start position:0% things that we learned into tau but it 00:20:48.289 --> 00:20:49.480 align:start position:0% things that we learned into tau but it is<00:20:48.440> not<00:20:48.590> in<00:20:48.710> this<00:20:48.830> stage<00:20:49.039> where<00:20:49.250> we<00:20:49.340> would 00:20:49.480 --> 00:20:49.490 align:start position:0% is not in this stage where we would 00:20:49.490 --> 00:20:51.700 align:start position:0% is not in this stage where we would perform<00:20:49.700> a<00:20:49.909> security<00:20:50.330> audit<00:20:50.600> on<00:20:50.720> it<00:20:50.870> and<00:20:51.049> the 00:20:51.700 --> 00:20:51.710 align:start position:0% perform a security audit on it and the 00:20:51.710 --> 00:20:53.710 align:start position:0% perform a security audit on it and the other<00:20:51.830> thing<00:20:52.279> is<00:20:52.399> the<00:20:52.940> other<00:20:53.059> question<00:20:53.269> was<00:20:53.539> if 00:20:53.710 --> 00:20:53.720 align:start position:0% other thing is the other question was if 00:20:53.720 --> 00:20:55.240 align:start position:0% other thing is the other question was if we<00:20:53.840> have<00:20:53.929> integrated<00:20:54.470> into<00:20:54.710> any<00:20:54.830> kind<00:20:55.129> of 00:20:55.240 --> 00:20:55.250 align:start position:0% we have integrated into any kind of 00:20:55.250 --> 00:20:57.279 align:start position:0% we have integrated into any kind of continuous<00:20:55.759> integration<00:20:56.029> or<00:20:56.389> continuous 00:20:57.279 --> 00:20:57.289 align:start position:0% continuous integration or continuous 00:20:57.289 --> 00:20:59.200 align:start position:0% continuous integration or continuous delivery<00:20:57.409> mechanism<00:20:58.190> and<00:20:58.340> the<00:20:58.669> answer<00:20:58.940> is<00:20:59.000> no 00:20:59.200 --> 00:20:59.210 align:start position:0% delivery mechanism and the answer is no 00:20:59.210 --> 00:21:01.749 align:start position:0% delivery mechanism and the answer is no because<00:20:59.360> we<00:20:59.750> are<00:20:59.779> and<00:21:00.139> this<00:21:00.830> was<00:21:01.009> on<00:21:01.429> one<00:21:01.490> of 00:21:01.749 --> 00:21:01.759 align:start position:0% because we are and this was on one of 00:21:01.759 --> 00:21:03.490 align:start position:0% because we are and this was on one of these<00:21:01.940> slides<00:21:02.330> I've<00:21:02.629> mentioned<00:21:03.230> it<00:21:03.289> really 00:21:03.490 --> 00:21:03.500 align:start position:0% these slides I've mentioned it really 00:21:03.500 --> 00:21:05.110 align:start position:0% these slides I've mentioned it really briefly<00:21:03.799> we<00:21:04.009> are<00:21:04.129> rolling<00:21:04.519> out<00:21:04.639> our<00:21:04.879> own 00:21:05.110 --> 00:21:05.120 align:start position:0% briefly we are rolling out our own 00:21:05.120 --> 00:21:06.879 align:start position:0% briefly we are rolling out our own mechanism<00:21:06.019> for<00:21:06.139> this<00:21:06.259> pretty<00:21:06.500> much<00:21:06.649> where<00:21:06.860> we 00:21:06.879 --> 00:21:06.889 align:start position:0% mechanism for this pretty much where we 00:21:06.889 --> 00:21:09.129 align:start position:0% mechanism for this pretty much where we have<00:21:07.100> these<00:21:07.250> reactive<00:21:07.850> containers<00:21:08.570> and<00:21:08.750> we're 00:21:09.129 --> 00:21:09.139 align:start position:0% have these reactive containers and we're 00:21:09.139 --> 00:21:11.139 align:start position:0% have these reactive containers and we're also<00:21:09.259> thinking<00:21:09.529> about<00:21:10.009> stuff<00:21:10.730> like<00:21:10.909> how<00:21:11.090> to 00:21:11.139 --> 00:21:11.149 align:start position:0% also thinking about stuff like how to 00:21:11.149 --> 00:21:12.999 align:start position:0% also thinking about stuff like how to properly<00:21:11.659> sign<00:21:12.049> these<00:21:12.320> containers<00:21:12.860> and 00:21:12.999 --> 00:21:13.009 align:start position:0% properly sign these containers and 00:21:13.009 --> 00:21:15.039 align:start position:0% properly sign these containers and modules<00:21:13.340> because<00:21:13.460> and<00:21:13.940> this<00:21:14.600> is<00:21:14.659> something 00:21:15.039 --> 00:21:15.049 align:start position:0% modules because and this is something 00:21:15.049 --> 00:21:16.299 align:start position:0% modules because and this is something that<00:21:15.200> we're<00:21:15.350> really<00:21:15.379> missing<00:21:15.710> in<00:21:16.039> the<00:21:16.129> whole 00:21:16.299 --> 00:21:16.309 align:start position:0% that we're really missing in the whole 00:21:16.309 --> 00:21:19.419 align:start position:0% that we're really missing in the whole note<00:21:17.000> reyes<00:21:17.529> ecosystem<00:21:18.529> you<00:21:19.070> can<00:21:19.250> actually 00:21:19.419 --> 00:21:19.429 align:start position:0% note reyes ecosystem you can actually 00:21:19.429 --> 00:21:21.549 align:start position:0% note reyes ecosystem you can actually put<00:21:19.759> check<00:21:20.000> sums<00:21:20.269> on<00:21:20.509> stuff<00:21:20.840> but<00:21:21.080> they<00:21:21.200> are<00:21:21.289> the 00:21:21.549 --> 00:21:21.559 align:start position:0% put check sums on stuff but they are the 00:21:21.559 --> 00:21:23.499 align:start position:0% put check sums on stuff but they are the these<00:21:21.889> these<00:21:22.250> modules<00:21:22.639> are<00:21:22.730> not<00:21:22.850> never<00:21:23.120> really 00:21:23.499 --> 00:21:23.509 align:start position:0% these these modules are not never really 00:21:23.509 --> 00:21:25.450 align:start position:0% these these modules are not never really signed<00:21:23.840> and<00:21:24.169> we<00:21:24.470> have<00:21:24.559> these<00:21:24.740> advantages<00:21:25.340> we 00:21:25.450 --> 00:21:25.460 align:start position:0% signed and we have these advantages we 00:21:25.460 --> 00:21:26.919 align:start position:0% signed and we have these advantages we know<00:21:25.580> how<00:21:25.789> to<00:21:25.850> do<00:21:26.059> it<00:21:26.179> and<00:21:26.330> we<00:21:26.419> could 00:21:26.919 --> 00:21:26.929 align:start position:0% know how to do it and we could 00:21:26.929 --> 00:21:28.629 align:start position:0% know how to do it and we could potentially<00:21:27.350> incorporate<00:21:28.190> it<00:21:28.340> in<00:21:28.460> our<00:21:28.610> own 00:21:28.629 --> 00:21:28.639 align:start position:0% potentially incorporate it in our own 00:21:28.639 --> 00:21:32.289 align:start position:0% potentially incorporate it in our own mechanism<00:21:29.269> okay<00:21:29.659> thank<00:21:29.990> you<00:21:30.159> so<00:21:31.159> that<00:21:32.000> style 00:21:32.289 --> 00:21:32.299 align:start position:0% mechanism okay thank you so that style 00:21:32.299 --> 00:21:34.389 align:start position:0% mechanism okay thank you so that style has<00:21:32.480> like<00:21:32.720> an<00:21:32.870> in<00:21:33.019> will<00:21:33.200> like<00:21:33.769> kind<00:21:34.070> of<00:21:34.250> some 00:21:34.389 --> 00:21:34.399 align:start position:0% has like an in will like kind of some 00:21:34.399 --> 00:21:38.860 align:start position:0% has like an in will like kind of some sort<00:21:36.309> the<00:21:37.309> principle<00:21:37.820> would<00:21:37.940> be<00:21:38.059> the<00:21:38.210> same<00:21:38.509> as 00:21:38.860 --> 00:21:38.870 align:start position:0% sort the principle would be the same as 00:21:38.870 --> 00:21:42.700 align:start position:0% sort the principle would be the same as for<00:21:39.009> mist<00:21:40.009> so<00:21:40.429> we<00:21:40.549> will<00:21:40.700> try<00:21:41.389> to<00:21:41.509> interact<00:21:42.500> with 00:21:42.700 --> 00:21:42.710 align:start position:0% for mist so we will try to interact with 00:21:42.710 --> 00:21:44.950 align:start position:0% for mist so we will try to interact with Goethe<00:21:43.279> room<00:21:43.639> for<00:21:43.820> example<00:21:43.970> or<00:21:44.299> with<00:21:44.450> parity 00:21:44.950 --> 00:21:44.960 align:start position:0% Goethe room for example or with parity 00:21:44.960 --> 00:21:46.810 align:start position:0% Goethe room for example or with parity with<00:21:45.110> some<00:21:45.440> external<00:21:45.860> client<00:21:46.399> that<00:21:46.580> we<00:21:46.700> would 00:21:46.810 --> 00:21:46.820 align:start position:0% with some external client that we would 00:21:46.820 --> 00:21:48.970 align:start position:0% with some external client that we would download<00:21:47.240> and<00:21:47.389> try<00:21:47.539> to<00:21:47.600> update<00:21:48.049> through<00:21:48.830> our 00:21:48.970 --> 00:21:48.980 align:start position:0% download and try to update through our 00:21:48.980 --> 00:21:51.490 align:start position:0% download and try to update through our update<00:21:49.279> mechanism<00:21:49.460> they<00:21:50.240> are<00:21:50.330> of<00:21:50.450> course<00:21:50.659> yes 00:21:51.490 --> 00:21:51.500 align:start position:0% update mechanism they are of course yes 00:21:51.500 --> 00:21:54.009 align:start position:0% update mechanism they are of course yes of<00:21:51.679> course<00:21:51.950> a<00:21:52.039> potential<00:21:52.610> we<00:21:53.330> saw<00:21:53.779> a<00:21:53.809> lot<00:21:53.990> of 00:21:54.009 --> 00:21:54.019 align:start position:0% of course a potential we saw a lot of 00:21:54.019 --> 00:21:57.639 align:start position:0% of course a potential we saw a lot of him<00:21:54.289> like<00:21:55.009> development<00:21:55.809> for<00:21:56.809> the<00:21:56.899> ethion<00:21:57.289> Jas 00:21:57.639 --> 00:21:57.649 align:start position:0% him like development for the ethion Jas 00:21:57.649 --> 00:21:59.799 align:start position:0% him like development for the ethion Jas project<00:21:58.250> and<00:21:58.429> there<00:21:58.940> could<00:21:59.120> be<00:21:59.149> the<00:21:59.509> the 00:21:59.799 --> 00:21:59.809 align:start position:0% project and there could be the the 00:21:59.809 --> 00:22:02.200 align:start position:0% project and there could be the the option<00:22:00.169> to<00:22:00.320> try<00:22:00.559> all<00:22:00.830> these<00:22:01.100> like<00:22:01.610> JavaScript 00:22:02.200 --> 00:22:02.210 align:start position:0% option to try all these like JavaScript 00:22:02.210 --> 00:22:03.999 align:start position:0% option to try all these like JavaScript libraries<00:22:02.870> to<00:22:03.049> make<00:22:03.080> it<00:22:03.379> more<00:22:03.500> like<00:22:03.679> a<00:22:03.710> full 00:22:03.999 --> 00:22:04.009 align:start position:0% libraries to make it more like a full 00:22:04.009 --> 00:22:07.090 align:start position:0% libraries to make it more like a full client<00:22:04.279> at<00:22:04.639> some<00:22:04.909> point<00:22:05.210> but<00:22:05.779> so<00:22:06.710> far<00:22:06.919> there 00:22:07.090 --> 00:22:07.100 align:start position:0% client at some point but so far there 00:22:07.100 --> 00:22:08.919 align:start position:0% client at some point but so far there are<00:22:07.129> no<00:22:07.220> plans<00:22:07.610> to<00:22:07.759> turn<00:22:08.179> it<00:22:08.360> into<00:22:08.509> a<00:22:08.659> light 00:22:08.919 --> 00:22:08.929 align:start position:0% are no plans to turn it into a light 00:22:08.929 --> 00:22:11.440 align:start position:0% are no plans to turn it into a light client<00:22:09.350> full<00:22:09.470> client<00:22:09.740> whatever 00:22:11.440 --> 00:22:11.450 align:start position:0% client full client whatever 00:22:11.450 --> 00:22:13.880 align:start position:0% client full client whatever okay<00:22:12.450> so<00:22:12.510> you<00:22:12.690> mentioned<00:22:13.140> the<00:22:13.290> update<00:22:13.740> process 00:22:13.880 --> 00:22:13.890 align:start position:0% okay so you mentioned the update process 00:22:13.890 --> 00:22:17.960 align:start position:0% okay so you mentioned the update process of<00:22:14.370> tower<00:22:14.580> vs.<00:22:16.070> electron-electron<00:22:17.070> obviously 00:22:17.960 --> 00:22:17.970 align:start position:0% of tower vs. electron-electron obviously 00:22:17.970 --> 00:22:19.460 align:start position:0% of tower vs. electron-electron obviously is<00:22:18.240> you<00:22:18.600> got<00:22:18.720> to<00:22:18.810> download<00:22:19.050> the<00:22:19.140> whole<00:22:19.260> app 00:22:19.460 --> 00:22:19.470 align:start position:0% is you got to download the whole app 00:22:19.470 --> 00:22:21.470 align:start position:0% is you got to download the whole app even<00:22:20.280> if<00:22:20.370> there<00:22:20.520> was<00:22:20.610> a<00:22:20.640> minor<00:22:20.850> change<00:22:21.180> on<00:22:21.390> the 00:22:21.470 --> 00:22:21.480 align:start position:0% even if there was a minor change on the 00:22:21.480 --> 00:22:24.050 align:start position:0% even if there was a minor change on the App<00:22:21.630> 60<00:22:22.470> megabytes<00:22:22.710> whatnot 00:22:24.050 --> 00:22:24.060 align:start position:0% App 60 megabytes whatnot 00:22:24.060 --> 00:22:26.000 align:start position:0% App 60 megabytes whatnot I<00:22:24.090> quite<00:22:24.570> didn't<00:22:24.870> get<00:22:25.050> the<00:22:25.170> update<00:22:25.440> process<00:22:25.890> of 00:22:26.000 --> 00:22:26.010 align:start position:0% I quite didn't get the update process of 00:22:26.010 --> 00:22:28.280 align:start position:0% I quite didn't get the update process of tau<00:22:26.220> as<00:22:26.550> in<00:22:26.790> like<00:22:27.000> if<00:22:27.240> I<00:22:27.360> want<00:22:27.540> to<00:22:27.630> update<00:22:27.780> some 00:22:28.280 --> 00:22:28.290 align:start position:0% tau as in like if I want to update some 00:22:28.290 --> 00:22:30.380 align:start position:0% tau as in like if I want to update some HTML<00:22:28.470> or<00:22:28.890> CSS<00:22:28.920> or<00:22:29.580> something<00:22:29.910> along<00:22:30.030> the<00:22:30.150> lines 00:22:30.380 --> 00:22:30.390 align:start position:0% HTML or CSS or something along the lines 00:22:30.390 --> 00:22:34.100 align:start position:0% HTML or CSS or something along the lines do<00:22:31.170> you<00:22:31.230> download<00:22:31.650> a<00:22:31.830> smaller<00:22:32.190> copy<00:22:32.550> of<00:22:33.110> the 00:22:34.100 --> 00:22:34.110 align:start position:0% do you download a smaller copy of the 00:22:34.110 --> 00:22:37.610 align:start position:0% do you download a smaller copy of the app<00:22:34.260> or<00:22:34.590> or<00:22:35.550> how<00:22:36.480> does<00:22:36.630> it<00:22:36.660> work<00:22:36.780> so<00:22:37.080> like<00:22:37.320> let's 00:22:37.610 --> 00:22:37.620 align:start position:0% app or or how does it work so like let's 00:22:37.620 --> 00:22:39.230 align:start position:0% app or or how does it work so like let's say<00:22:37.740> the<00:22:37.860> whole<00:22:37.980> app<00:22:38.220> is<00:22:38.430> like<00:22:38.610> still<00:22:38.910> 60 00:22:39.230 --> 00:22:39.240 align:start position:0% say the whole app is like still 60 00:22:39.240 --> 00:22:40.970 align:start position:0% say the whole app is like still 60 megabytes<00:22:39.420> right<00:22:39.660> yeah<00:22:40.170> and<00:22:40.410> then<00:22:40.770> you<00:22:40.830> want 00:22:40.970 --> 00:22:40.980 align:start position:0% megabytes right yeah and then you want 00:22:40.980 --> 00:22:42.890 align:start position:0% megabytes right yeah and then you want to<00:22:41.040> update<00:22:41.130> smaller<00:22:41.520> processes<00:22:42.090> how<00:22:42.690> do<00:22:42.750> you 00:22:42.890 --> 00:22:42.900 align:start position:0% to update smaller processes how do you 00:22:42.900 --> 00:22:45.290 align:start position:0% to update smaller processes how do you go<00:22:43.050> about<00:22:43.140> doing<00:22:43.500> that<00:22:43.620> yeah<00:22:44.100> so<00:22:44.340> the<00:22:44.520> the<00:22:44.850> user 00:22:45.290 --> 00:22:45.300 align:start position:0% go about doing that yeah so the the user 00:22:45.300 --> 00:22:47.270 align:start position:0% go about doing that yeah so the the user interface<00:22:45.690> this<00:22:45.930> yellow<00:22:46.200> box<00:22:46.470> is<00:22:46.740> packaged 00:22:47.270 --> 00:22:47.280 align:start position:0% interface this yellow box is packaged 00:22:47.280 --> 00:22:51.620 align:start position:0% interface this yellow box is packaged separately<00:22:48.020> and<00:22:49.020> then<00:22:49.440> we<00:22:49.590> have<00:22:49.740> a<00:22:50.700> frame<00:22:51.420> for 00:22:51.620 --> 00:22:51.630 align:start position:0% separately and then we have a frame for 00:22:51.630 --> 00:22:53.270 align:start position:0% separately and then we have a frame for this<00:22:51.780> which<00:22:52.020> is<00:22:52.050> the<00:22:52.170> browser<00:22:52.440> frame<00:22:52.770> that 00:22:53.270 --> 00:22:53.280 align:start position:0% this which is the browser frame that 00:22:53.280 --> 00:22:55.580 align:start position:0% this which is the browser frame that includes<00:22:54.030> the<00:22:54.180> update<00:22:54.480> mechanism<00:22:54.630> and<00:22:55.230> it 00:22:55.580 --> 00:22:55.590 align:start position:0% includes the update mechanism and it 00:22:55.590 --> 00:22:57.110 align:start position:0% includes the update mechanism and it will<00:22:55.800> actually<00:22:55.950> check<00:22:56.400> for<00:22:56.580> newer<00:22:56.700> versions 00:22:57.110 --> 00:22:57.120 align:start position:0% will actually check for newer versions 00:22:57.120 --> 00:22:58.580 align:start position:0% will actually check for newer versions of<00:22:57.240> this<00:22:57.330> UI<00:22:57.570> it's<00:22:57.810> pretty<00:22:57.990> much<00:22:58.080> like<00:22:58.140> a<00:22:58.320> hot 00:22:58.580 --> 00:22:58.590 align:start position:0% of this UI it's pretty much like a hot 00:22:58.590 --> 00:23:00.920 align:start position:0% of this UI it's pretty much like a hot hot<00:22:58.830> updating<00:22:59.490> mechanism<00:23:00.060> for<00:23:00.330> electron<00:23:00.720> apps 00:23:00.920 --> 00:23:00.930 align:start position:0% hot updating mechanism for electron apps 00:23:00.930 --> 00:23:03.770 align:start position:0% hot updating mechanism for electron apps only<00:23:01.740> that<00:23:02.070> you<00:23:02.160> don't<00:23:02.340> have<00:23:02.490> to<00:23:02.640> press<00:23:02.850> f5<00:23:03.270> but 00:23:03.770 --> 00:23:03.780 align:start position:0% only that you don't have to press f5 but 00:23:03.780 --> 00:23:05.210 align:start position:0% only that you don't have to press f5 but someone<00:23:04.020> else<00:23:04.200> will<00:23:04.350> do<00:23:04.440> it<00:23:04.470> for<00:23:04.680> you<00:23:04.830> and<00:23:04.980> they 00:23:05.210 --> 00:23:05.220 align:start position:0% someone else will do it for you and they 00:23:05.220 --> 00:23:07.820 align:start position:0% someone else will do it for you and they will<00:23:05.340> check<00:23:05.610> our<00:23:06.510> github<00:23:06.870> releases<00:23:07.380> page<00:23:07.590> for 00:23:07.820 --> 00:23:07.830 align:start position:0% will check our github releases page for 00:23:07.830 --> 00:23:10.940 align:start position:0% will check our github releases page for new<00:23:07.950> updates<00:23:08.340> and<00:23:08.970> we<00:23:09.930> also<00:23:10.080> provide<00:23:10.620> like<00:23:10.800> all 00:23:10.940 --> 00:23:10.950 align:start position:0% new updates and we also provide like all 00:23:10.950 --> 00:23:12.950 align:start position:0% new updates and we also provide like all the<00:23:11.070> tools<00:23:11.280> to<00:23:11.400> publish<00:23:12.000> these<00:23:12.150> updates<00:23:12.600> they 00:23:12.950 --> 00:23:12.960 align:start position:0% the tools to publish these updates they 00:23:12.960 --> 00:23:14.480 align:start position:0% the tools to publish these updates they include<00:23:13.440> check<00:23:13.650> sums<00:23:13.920> they<00:23:14.130> include 00:23:14.480 --> 00:23:14.490 align:start position:0% include check sums they include 00:23:14.490 --> 00:23:16.850 align:start position:0% include check sums they include versioning<00:23:15.480> a<00:23:15.720> channel<00:23:16.380> if<00:23:16.500> it's<00:23:16.650> better 00:23:16.850 --> 00:23:16.860 align:start position:0% versioning a channel if it's better 00:23:16.860 --> 00:23:19.730 align:start position:0% versioning a channel if it's better release<00:23:17.220> we<00:23:17.850> can<00:23:18.000> even<00:23:18.300> make<00:23:18.600> staged<00:23:19.230> rollouts 00:23:19.730 --> 00:23:19.740 align:start position:0% release we can even make staged rollouts 00:23:19.740 --> 00:23:21.530 align:start position:0% release we can even make staged rollouts so<00:23:20.070> we<00:23:20.160> can<00:23:20.340> say<00:23:20.610> it's<00:23:20.820> something<00:23:21.210> like<00:23:21.300> 10% 00:23:21.530 --> 00:23:21.540 align:start position:0% so we can say it's something like 10% 00:23:21.540 --> 00:23:26.840 align:start position:0% so we can say it's something like 10% should<00:23:21.990> update<00:23:22.140> now<00:23:22.640> and<00:23:23.640> then<00:23:25.040> the<00:23:26.040> the<00:23:26.580> shell 00:23:26.840 --> 00:23:26.850 align:start position:0% should update now and then the the shell 00:23:26.850 --> 00:23:29.060 align:start position:0% should update now and then the the shell will<00:23:27.210> update<00:23:27.360> this<00:23:27.600> new<00:23:27.840> like<00:23:28.350> packages<00:23:28.860> these 00:23:29.060 --> 00:23:29.070 align:start position:0% will update this new like packages these 00:23:29.070 --> 00:23:38.120 align:start position:0% will update this new like packages these containers<00:23:29.610> and<00:23:29.790> run<00:23:29.940> them 00:23:38.120 --> 00:23:38.130 align:start position:0% 00:23:38.130 --> 00:23:40.190 align:start position:0% you