WEBVTT Kind: captions Language: en 00:00:00.000 --> 00:00:18.820 align:start position:0% I 00:00:18.820 --> 00:00:18.830 align:start position:0% 00:00:18.830 --> 00:00:23.060 align:start position:0% and<00:00:20.480> my<00:00:21.480> name<00:00:21.630> is<00:00:21.750> also<00:00:22.050> xik<00:00:22.439> as<00:00:22.590> most<00:00:22.800> people 00:00:23.060 --> 00:00:23.070 align:start position:0% and my name is also xik as most people 00:00:23.070 --> 00:00:25.609 align:start position:0% and my name is also xik as most people know<00:00:23.099> me<00:00:23.220> on<00:00:23.580> github<00:00:23.910> so<00:00:24.900> I'm<00:00:25.140> going<00:00:25.320> to<00:00:25.529> talk 00:00:25.609 --> 00:00:25.619 align:start position:0% know me on github so I'm going to talk 00:00:25.619 --> 00:00:28.310 align:start position:0% know me on github so I'm going to talk about<00:00:25.770> mango<00:00:26.220> which<00:00:27.119> is<00:00:27.360> making<00:00:27.570> it<00:00:27.960> fully 00:00:28.310 --> 00:00:28.320 align:start position:0% about mango which is making it fully 00:00:28.320 --> 00:00:30.230 align:start position:0% about mango which is making it fully decentralized<00:00:28.710> and<00:00:29.189> what<00:00:29.669> does<00:00:29.789> that<00:00:29.820> means 00:00:30.230 --> 00:00:30.240 align:start position:0% decentralized and what does that means 00:00:30.240 --> 00:00:34.700 align:start position:0% decentralized and what does that means it<00:00:30.539> puts<00:00:31.230> get<00:00:32.030> repositories<00:00:33.030> onto<00:00:33.989> athyrium 00:00:34.700 --> 00:00:34.710 align:start position:0% it puts get repositories onto athyrium 00:00:34.710 --> 00:00:38.330 align:start position:0% it puts get repositories onto athyrium swarm<00:00:35.579> and<00:00:35.850> I<00:00:35.970> PFS<00:00:36.510> I<00:00:36.950> just<00:00:37.950> a<00:00:38.010> quick<00:00:38.190> note 00:00:38.330 --> 00:00:38.340 align:start position:0% swarm and I PFS I just a quick note 00:00:38.340 --> 00:00:40.490 align:start position:0% swarm and I PFS I just a quick note about<00:00:38.399> what<00:00:38.700> get<00:00:38.969> is<00:00:39.120> get<00:00:39.809> is<00:00:40.020> a<00:00:40.050> version 00:00:40.490 --> 00:00:40.500 align:start position:0% about what get is get is a version 00:00:40.500 --> 00:00:44.080 align:start position:0% about what get is get is a version control<00:00:40.680> software<00:00:41.489> where<00:00:42.480> most<00:00:42.960> developers 00:00:44.080 --> 00:00:44.090 align:start position:0% control software where most developers 00:00:44.090 --> 00:00:46.610 align:start position:0% control software where most developers keep<00:00:45.090> their<00:00:45.300> source<00:00:45.570> code<00:00:45.840> and<00:00:46.050> they<00:00:46.440> make 00:00:46.610 --> 00:00:46.620 align:start position:0% keep their source code and they make 00:00:46.620 --> 00:00:48.470 align:start position:0% keep their source code and they make changes<00:00:46.950> to<00:00:47.010> the<00:00:47.190> source<00:00:47.430> code<00:00:47.670> other<00:00:48.120> people 00:00:48.470 --> 00:00:48.480 align:start position:0% changes to the source code other people 00:00:48.480 --> 00:00:50.060 align:start position:0% changes to the source code other people can<00:00:48.600> track<00:00:48.840> these<00:00:48.990> changes<00:00:49.440> and<00:00:49.470> contribute 00:00:50.060 --> 00:00:50.070 align:start position:0% can track these changes and contribute 00:00:50.070 --> 00:00:53.330 align:start position:0% can track these changes and contribute changes<00:00:50.930> so<00:00:51.930> the<00:00:52.020> first<00:00:52.170> thing<00:00:52.380> is<00:00:52.740> about<00:00:53.010> get 00:00:53.330 --> 00:00:53.340 align:start position:0% changes so the first thing is about get 00:00:53.340 --> 00:00:55.730 align:start position:0% changes so the first thing is about get as<00:00:53.610> it<00:00:53.820> was<00:00:53.940> created<00:00:54.180> roughly<00:00:54.840> ten<00:00:55.260> years<00:00:55.500> ago 00:00:55.730 --> 00:00:55.740 align:start position:0% as it was created roughly ten years ago 00:00:55.740 --> 00:00:58.490 align:start position:0% as it was created roughly ten years ago and<00:00:55.980> it<00:00:56.850> was<00:00:57.000> created<00:00:57.480> with<00:00:57.660> decentralization 00:00:58.490 --> 00:00:58.500 align:start position:0% and it was created with decentralization 00:00:58.500 --> 00:01:01.760 align:start position:0% and it was created with decentralization and<00:00:58.940> distributed<00:00:59.940> systems<00:01:00.360> in<00:01:00.510> mind<00:01:01.020> however 00:01:01.760 --> 00:01:01.770 align:start position:0% and distributed systems in mind however 00:01:01.770 --> 00:01:04.759 align:start position:0% and distributed systems in mind however ten<00:01:02.730> years<00:01:02.970> ago<00:01:03.270> decentralized<00:01:04.170> systems 00:01:04.759 --> 00:01:04.769 align:start position:0% ten years ago decentralized systems 00:01:04.769 --> 00:01:07.490 align:start position:0% ten years ago decentralized systems weren't<00:01:05.040> ready<00:01:05.720> so<00:01:06.720> you<00:01:06.990> couldn't<00:01:07.259> do<00:01:07.380> this 00:01:07.490 --> 00:01:07.500 align:start position:0% weren't ready so you couldn't do this 00:01:07.500 --> 00:01:10.300 align:start position:0% weren't ready so you couldn't do this you<00:01:07.740> had<00:01:07.979> to<00:01:08.250> use<00:01:08.729> a<00:01:08.759> central<00:01:09.329> part<00:01:09.570> to<00:01:09.990> get 00:01:10.300 --> 00:01:10.310 align:start position:0% you had to use a central part to get 00:01:10.310 --> 00:01:13.310 align:start position:0% you had to use a central part to get however<00:01:11.310> today<00:01:11.540> we<00:01:12.540> have<00:01:12.810> decentralized 00:01:13.310 --> 00:01:13.320 align:start position:0% however today we have decentralized 00:01:13.320 --> 00:01:17.030 align:start position:0% however today we have decentralized systems<00:01:13.979> in<00:01:14.189> place<00:01:14.250> the<00:01:15.149> etherium<00:01:15.720> I<00:01:15.930> PFS<00:01:16.799> and 00:01:17.030 --> 00:01:17.040 align:start position:0% systems in place the etherium I PFS and 00:01:17.040 --> 00:01:19.760 align:start position:0% systems in place the etherium I PFS and swarm<00:01:17.280> so<00:01:18.060> this<00:01:18.299> is<00:01:18.450> the<00:01:18.570> time<00:01:18.840> to<00:01:19.530> accomplish 00:01:19.760 --> 00:01:19.770 align:start position:0% swarm so this is the time to accomplish 00:01:19.770 --> 00:01:23.569 align:start position:0% swarm so this is the time to accomplish the<00:01:20.219> goal<00:01:20.399> of<00:01:20.670> get<00:01:21.649> the<00:01:22.649> first<00:01:22.859> thing<00:01:23.069> is<00:01:23.280> why 00:01:23.569 --> 00:01:23.579 align:start position:0% the goal of get the first thing is why 00:01:23.579 --> 00:01:26.989 align:start position:0% the goal of get the first thing is why do<00:01:23.639> I<00:01:23.850> care<00:01:24.119> about<00:01:24.240> mango<00:01:24.719> and<00:01:25.579> what<00:01:26.579> do<00:01:26.700> I<00:01:26.759> care 00:01:26.989 --> 00:01:26.999 align:start position:0% do I care about mango and what do I care 00:01:26.999 --> 00:01:29.599 align:start position:0% do I care about mango and what do I care of<00:01:27.060> it<00:01:27.210> sorry<00:01:28.049> why<00:01:28.530> do<00:01:28.590> I<00:01:28.710> care<00:01:28.950> about<00:01:29.069> mango 00:01:29.599 --> 00:01:29.609 align:start position:0% of it sorry why do I care about mango 00:01:29.609 --> 00:01:32.419 align:start position:0% of it sorry why do I care about mango and<00:01:29.990> why<00:01:30.990> you<00:01:31.049> should<00:01:31.229> also<00:01:31.560> care<00:01:31.920> about<00:01:31.950> mango 00:01:32.419 --> 00:01:32.429 align:start position:0% and why you should also care about mango 00:01:32.429 --> 00:01:34.789 align:start position:0% and why you should also care about mango there<00:01:33.240> a<00:01:33.270> couple<00:01:33.389> of<00:01:33.539> reasons<00:01:33.770> you<00:01:34.770> don't 00:01:34.789 --> 00:01:34.799 align:start position:0% there a couple of reasons you don't 00:01:34.799 --> 00:01:36.260 align:start position:0% there a couple of reasons you don't really<00:01:35.069> want<00:01:35.280> to<00:01:35.340> trust<00:01:35.639> the<00:01:35.850> central 00:01:36.260 --> 00:01:36.270 align:start position:0% really want to trust the central 00:01:36.270 --> 00:01:38.899 align:start position:0% really want to trust the central repository<00:01:36.469> with<00:01:37.469> all<00:01:37.679> your<00:01:37.829> data<00:01:38.039> they<00:01:38.729> could 00:01:38.899 --> 00:01:38.909 align:start position:0% repository with all your data they could 00:01:38.909 --> 00:01:41.120 align:start position:0% repository with all your data they could take<00:01:39.090> it<00:01:39.119> down<00:01:39.450> and<00:01:40.139> you<00:01:40.200> want<00:01:40.530> more<00:01:40.740> security 00:01:41.120 --> 00:01:41.130 align:start position:0% take it down and you want more security 00:01:41.130 --> 00:01:43.849 align:start position:0% take it down and you want more security than<00:01:41.310> that<00:01:41.659> this<00:01:42.659> is<00:01:42.719> a<00:01:42.749> very<00:01:42.780> important<00:01:43.529> fact 00:01:43.849 --> 00:01:43.859 align:start position:0% than that this is a very important fact 00:01:43.859 --> 00:01:47.539 align:start position:0% than that this is a very important fact that<00:01:44.609> you<00:01:45.029> get<00:01:45.389> by<00:01:45.659> default<00:01:46.170> if<00:01:46.409> you<00:01:46.920> use<00:01:47.100> mango 00:01:47.539 --> 00:01:47.549 align:start position:0% that you get by default if you use mango 00:01:47.549 --> 00:01:50.090 align:start position:0% that you get by default if you use mango you<00:01:48.119> get<00:01:48.299> proof<00:01:48.539> of<00:01:48.689> existence<00:01:48.840> of<00:01:49.560> your<00:01:49.829> code 00:01:50.090 --> 00:01:50.100 align:start position:0% you get proof of existence of your code 00:01:50.100 --> 00:01:52.849 align:start position:0% you get proof of existence of your code so<00:01:50.789> whenever<00:01:50.969> you<00:01:51.270> push<00:01:51.600> your<00:01:52.139> changes<00:01:52.709> or 00:01:52.849 --> 00:01:52.859 align:start position:0% so whenever you push your changes or 00:01:52.859 --> 00:01:57.050 align:start position:0% so whenever you push your changes or your<00:01:52.979> code<00:01:53.219> is<00:01:54.619> a<00:01:55.619> better<00:01:55.859> name<00:01:56.039> so<00:01:56.579> whenever 00:01:57.050 --> 00:01:57.060 align:start position:0% your code is a better name so whenever 00:01:57.060 --> 00:02:00.620 align:start position:0% your code is a better name so whenever you<00:01:57.270> push<00:01:57.479> changes<00:01:57.869> to<00:01:58.020> your<00:01:58.139> code<00:01:58.439> and<00:01:59.630> it 00:02:00.620 --> 00:02:00.630 align:start position:0% you push changes to your code and it 00:02:00.630 --> 00:02:01.910 align:start position:0% you push changes to your code and it will<00:02:00.689> be<00:02:00.959> stored<00:02:01.229> on<00:02:01.319> the<00:02:01.380> block<00:02:01.560> chain<00:02:01.590> as 00:02:01.910 --> 00:02:01.920 align:start position:0% will be stored on the block chain as 00:02:01.920 --> 00:02:04.249 align:start position:0% will be stored on the block chain as well<00:02:01.950> and<00:02:02.450> because<00:02:03.450> of<00:02:03.479> that<00:02:03.630> you<00:02:03.810> get<00:02:04.079> the 00:02:04.249 --> 00:02:04.259 align:start position:0% well and because of that you get the 00:02:04.259 --> 00:02:06.620 align:start position:0% well and because of that you get the timestamp<00:02:05.240> according<00:02:06.240> to<00:02:06.270> the<00:02:06.420> block<00:02:06.599> chain 00:02:06.620 --> 00:02:06.630 align:start position:0% timestamp according to the block chain 00:02:06.630 --> 00:02:09.710 align:start position:0% timestamp according to the block chain and<00:02:07.109> you<00:02:07.529> can<00:02:07.770> prove<00:02:08.130> that<00:02:08.160> your<00:02:08.759> code<00:02:09.179> with 00:02:09.710 --> 00:02:09.720 align:start position:0% and you can prove that your code with 00:02:09.720 --> 00:02:12.680 align:start position:0% and you can prove that your code with all<00:02:09.959> its<00:02:10.140> content<00:02:10.709> existed<00:02:11.700> at<00:02:11.880> that<00:02:11.940> point<00:02:12.510> of 00:02:12.680 --> 00:02:12.690 align:start position:0% all its content existed at that point of 00:02:12.690 --> 00:02:15.559 align:start position:0% all its content existed at that point of time<00:02:13.430> you<00:02:14.430> can<00:02:14.640> see<00:02:14.760> that's<00:02:14.940> very<00:02:15.090> important 00:02:15.559 --> 00:02:15.569 align:start position:0% time you can see that's very important 00:02:15.569 --> 00:02:17.540 align:start position:0% time you can see that's very important because<00:02:15.630> you<00:02:15.959> can<00:02:16.110> prove<00:02:16.380> in<00:02:16.800> case<00:02:17.069> of<00:02:17.250> legal 00:02:17.540 --> 00:02:17.550 align:start position:0% because you can prove in case of legal 00:02:17.550 --> 00:02:19.070 align:start position:0% because you can prove in case of legal issues<00:02:17.640> that<00:02:18.420> you<00:02:18.569> were<00:02:18.660> the<00:02:18.720> first 00:02:19.070 --> 00:02:19.080 align:start position:0% issues that you were the first 00:02:19.080 --> 00:02:21.380 align:start position:0% issues that you were the first implementing<00:02:19.920> that<00:02:20.099> and<00:02:20.310> you<00:02:20.760> have<00:02:21.000> the<00:02:21.150> prior 00:02:21.380 --> 00:02:21.390 align:start position:0% implementing that and you have the prior 00:02:21.390 --> 00:02:23.330 align:start position:0% implementing that and you have the prior art<00:02:21.540> and<00:02:22.110> that's<00:02:22.650> really<00:02:22.769> important<00:02:23.159> in<00:02:23.250> the 00:02:23.330 --> 00:02:23.340 align:start position:0% art and that's really important in the 00:02:23.340 --> 00:02:26.860 align:start position:0% art and that's really important in the open<00:02:23.579> source<00:02:23.730> software<00:02:23.970> and<00:02:24.739> I<00:02:25.739> don't<00:02:25.950> really 00:02:26.860 --> 00:02:26.870 align:start position:0% open source software and I don't really 00:02:26.870 --> 00:02:29.170 align:start position:0% open source software and I don't really used<00:02:27.110> for<00:02:27.409> mango<00:02:27.709> which<00:02:27.920> get<00:02:28.519> cannot<00:02:28.970> really 00:02:29.170 --> 00:02:29.180 align:start position:0% used for mango which get cannot really 00:02:29.180 --> 00:02:32.229 align:start position:0% used for mango which get cannot really do<00:02:29.450> is<00:02:29.690> storing<00:02:30.290> large<00:02:30.500> pies<00:02:30.860> so<00:02:31.819> get<00:02:32.030> just 00:02:32.229 --> 00:02:32.239 align:start position:0% do is storing large pies so get just 00:02:32.239 --> 00:02:34.089 align:start position:0% do is storing large pies so get just towards<00:02:32.510> large<00:02:32.720> files<00:02:33.080> as<00:02:33.319> a<00:02:33.560> single<00:02:33.950> block 00:02:34.089 --> 00:02:34.099 align:start position:0% towards large files as a single block 00:02:34.099 --> 00:02:36.699 align:start position:0% towards large files as a single block and<00:02:34.430> whenever<00:02:35.330> other<00:02:35.569> people<00:02:35.989> copy<00:02:36.200> your<00:02:36.470> gate 00:02:36.699 --> 00:02:36.709 align:start position:0% and whenever other people copy your gate 00:02:36.709 --> 00:02:38.440 align:start position:0% and whenever other people copy your gate or<00:02:36.920> they<00:02:37.099> make<00:02:37.280> changes<00:02:37.760> to<00:02:37.819> that<00:02:38.000> or<00:02:38.330> they 00:02:38.440 --> 00:02:38.450 align:start position:0% or they make changes to that or they 00:02:38.450 --> 00:02:40.030 align:start position:0% or they make changes to that or they store<00:02:38.690> other<00:02:38.840> files<00:02:38.930> or<00:02:39.470> they<00:02:39.590> change<00:02:39.890> the 00:02:40.030 --> 00:02:40.040 align:start position:0% store other files or they change the 00:02:40.040 --> 00:02:43.000 align:start position:0% store other files or they change the file<00:02:40.280> it<00:02:40.549> will<00:02:41.239> be<00:02:41.420> a<00:02:41.450> brand-new<00:02:41.750> entire<00:02:42.680> blob 00:02:43.000 --> 00:02:43.010 align:start position:0% file it will be a brand-new entire blob 00:02:43.010 --> 00:02:44.920 align:start position:0% file it will be a brand-new entire blob so<00:02:43.819> if<00:02:43.879> you<00:02:43.970> have<00:02:44.060> a<00:02:44.090> file<00:02:44.360> of<00:02:44.510> like<00:02:44.720> 10 00:02:44.920 --> 00:02:44.930 align:start position:0% so if you have a file of like 10 00:02:44.930 --> 00:02:47.020 align:start position:0% so if you have a file of like 10 megabytes<00:02:45.379> which<00:02:45.799> is<00:02:46.010> the<00:02:46.190> solidity<00:02:46.549> compiler 00:02:47.020 --> 00:02:47.030 align:start position:0% megabytes which is the solidity compiler 00:02:47.030 --> 00:02:49.839 align:start position:0% megabytes which is the solidity compiler for<00:02:47.959> every<00:02:48.349> new<00:02:48.590> compiler<00:02:48.920> version<00:02:49.129> you<00:02:49.640> have 00:02:49.839 --> 00:02:49.849 align:start position:0% for every new compiler version you have 00:02:49.849 --> 00:02:52.149 align:start position:0% for every new compiler version you have the<00:02:50.000> full<00:02:50.209> file<00:02:50.560> currently<00:02:51.560> the<00:02:51.769> solidity 00:02:52.149 --> 00:02:52.159 align:start position:0% the full file currently the solidity 00:02:52.159 --> 00:02:54.819 align:start position:0% the full file currently the solidity repository<00:02:52.909> is<00:02:53.150> roughly<00:02:53.959> 100<00:02:54.260> megabytes<00:02:54.680> in 00:02:54.819 --> 00:02:54.829 align:start position:0% repository is roughly 100 megabytes in 00:02:54.829 --> 00:02:58.660 align:start position:0% repository is roughly 100 megabytes in yet<00:02:55.069> just<00:02:55.970> for<00:02:56.120> the<00:02:56.209> compiler<00:02:56.540> versions<00:02:57.670> which 00:02:58.660 --> 00:02:58.670 align:start position:0% yet just for the compiler versions which 00:02:58.670 --> 00:03:01.210 align:start position:0% yet just for the compiler versions which using<00:02:59.120> IP<00:02:59.299> FS<00:02:59.660> or<00:02:59.840> sworn<00:03:00.200> you<00:03:00.950> have 00:03:01.210 --> 00:03:01.220 align:start position:0% using IP FS or sworn you have 00:03:01.220 --> 00:03:04.720 align:start position:0% using IP FS or sworn you have deduplication<00:03:02.030> and<00:03:03.129> whenever<00:03:04.129> you<00:03:04.459> store 00:03:04.720 --> 00:03:04.730 align:start position:0% deduplication and whenever you store 00:03:04.730 --> 00:03:07.809 align:start position:0% deduplication and whenever you store these<00:03:04.849> files<00:03:05.180> and<00:03:05.420> use<00:03:06.260> it<00:03:06.410> a<00:03:06.500> mango<00:03:06.829> only<00:03:07.700> the 00:03:07.809 --> 00:03:07.819 align:start position:0% these files and use it a mango only the 00:03:07.819 --> 00:03:09.759 align:start position:0% these files and use it a mango only the differences<00:03:08.299> are<00:03:08.329> stored<00:03:08.780> this<00:03:09.440> is<00:03:09.590> something 00:03:09.759 --> 00:03:09.769 align:start position:0% differences are stored this is something 00:03:09.769 --> 00:03:12.789 align:start position:0% differences are stored this is something many<00:03:10.160> people<00:03:10.280> don't<00:03:10.609> know<00:03:10.730> but<00:03:10.970> get<00:03:11.209> and<00:03:11.799> the 00:03:12.789 --> 00:03:12.799 align:start position:0% many people don't know but get and the 00:03:12.799 --> 00:03:15.369 align:start position:0% many people don't know but get and the last<00:03:13.010> really<00:03:13.220> important<00:03:13.609> point<00:03:13.790> is<00:03:14.030> it<00:03:14.930> here 00:03:15.369 --> 00:03:15.379 align:start position:0% last really important point is it here 00:03:15.379 --> 00:03:18.099 align:start position:0% last really important point is it here iam<00:03:15.620> as<00:03:15.799> a<00:03:16.609> cause<00:03:16.970> is<00:03:17.239> building<00:03:17.690> decentralized 00:03:18.099 --> 00:03:18.109 align:start position:0% iam as a cause is building decentralized 00:03:18.109 --> 00:03:20.770 align:start position:0% iam as a cause is building decentralized systems<00:03:18.700> the<00:03:19.700> whole<00:03:19.879> source<00:03:20.209> code<00:03:20.480> of<00:03:20.599> this 00:03:20.770 --> 00:03:20.780 align:start position:0% systems the whole source code of this 00:03:20.780 --> 00:03:22.839 align:start position:0% systems the whole source code of this cost<00:03:21.019> should<00:03:21.290> be<00:03:21.349> of<00:03:21.650> label<00:03:22.040> two<00:03:22.280> distinct 00:03:22.839 --> 00:03:22.849 align:start position:0% cost should be of label two distinct 00:03:22.849 --> 00:03:33.250 align:start position:0% cost should be of label two distinct rely<00:03:23.000> systems<00:03:30.609> the<00:03:31.609> last<00:03:31.760> photo<00:03:31.940> so<00:03:32.840> what<00:03:33.139> is 00:03:33.250 --> 00:03:33.260 align:start position:0% rely systems the last photo so what is 00:03:33.260 --> 00:03:35.379 align:start position:0% rely systems the last photo so what is get<00:03:33.440> itself<00:03:33.739> get<00:03:34.190> is<00:03:34.400> a<00:03:34.430> content<00:03:35.060> addressable 00:03:35.379 --> 00:03:35.389 align:start position:0% get itself get is a content addressable 00:03:35.389 --> 00:03:38.650 align:start position:0% get itself get is a content addressable file<00:03:35.989> system<00:03:36.410> what<00:03:37.190> is<00:03:37.310> form<00:03:37.579> it<00:03:37.760> is<00:03:38.299> the<00:03:38.450> same 00:03:38.650 --> 00:03:38.660 align:start position:0% file system what is form it is the same 00:03:38.660 --> 00:03:42.610 align:start position:0% file system what is form it is the same what<00:03:39.590> is<00:03:39.709> I<00:03:39.739> PFS<00:03:40.340> it<00:03:40.579> is<00:03:41.209> the<00:03:41.359> same<00:03:41.599> there's<00:03:42.560> a 00:03:42.610 --> 00:03:42.620 align:start position:0% what is I PFS it is the same there's a 00:03:42.620 --> 00:03:44.500 align:start position:0% what is I PFS it is the same there's a tiny<00:03:42.799> bit<00:03:43.010> of<00:03:43.099> difference<00:03:43.280> though<00:03:43.669> it<00:03:44.299> is 00:03:44.500 --> 00:03:44.510 align:start position:0% tiny bit of difference though it is 00:03:44.510 --> 00:03:46.900 align:start position:0% tiny bit of difference though it is working<00:03:44.930> on<00:03:45.139> your<00:03:45.290> local<00:03:45.650> system<00:03:45.859> what<00:03:46.760> other 00:03:46.900 --> 00:03:46.910 align:start position:0% working on your local system what other 00:03:46.910 --> 00:03:48.610 align:start position:0% working on your local system what other two<00:03:47.239> are<00:03:47.510> working<00:03:47.780> in<00:03:48.139> a<00:03:48.260> global 00:03:48.610 --> 00:03:48.620 align:start position:0% two are working in a global 00:03:48.620 --> 00:03:51.400 align:start position:0% two are working in a global decentralized<00:03:49.129> way<00:03:49.629> so<00:03:50.629> you<00:03:50.690> see<00:03:50.900> it<00:03:51.079> makes 00:03:51.400 --> 00:03:51.410 align:start position:0% decentralized way so you see it makes 00:03:51.410 --> 00:03:53.949 align:start position:0% decentralized way so you see it makes sense<00:03:51.709> to<00:03:51.950> move<00:03:52.190> your<00:03:52.430> git<00:03:52.669> repos<00:03:53.090> to<00:03:53.840> either 00:03:53.949 --> 00:03:53.959 align:start position:0% sense to move your git repos to either 00:03:53.959 --> 00:03:58.720 align:start position:0% sense to move your git repos to either swarm<00:03:54.500> or<00:03:55.010> I<00:03:55.099> BFS<00:03:56.980> that<00:03:57.980> this<00:03:58.370> is<00:03:58.519> something 00:03:58.720 --> 00:03:58.730 align:start position:0% swarm or I BFS that this is something 00:03:58.730 --> 00:04:00.580 align:start position:0% swarm or I BFS that this is something many<00:03:58.940> people<00:03:59.030> have<00:03:59.329> seen<00:03:59.540> you<00:03:59.810> know<00:04:00.109> get<00:04:00.319> looks 00:04:00.580 --> 00:04:00.590 align:start position:0% many people have seen you know get looks 00:04:00.590 --> 00:04:03.400 align:start position:0% many people have seen you know get looks fairly<00:04:01.099> complicated<00:04:01.840> people<00:04:02.840> mostly<00:04:02.989> know<00:04:03.169> a 00:04:03.400 --> 00:04:03.410 align:start position:0% fairly complicated people mostly know a 00:04:03.410 --> 00:04:05.890 align:start position:0% fairly complicated people mostly know a few<00:04:03.799> commands<00:04:04.549> and<00:04:04.849> they<00:04:04.940> get<00:04:05.150> afraid<00:04:05.510> they 00:04:05.890 --> 00:04:05.900 align:start position:0% few commands and they get afraid they 00:04:05.900 --> 00:04:07.479 align:start position:0% few commands and they get afraid they delete<00:04:06.169> stuff<00:04:06.470> and<00:04:06.739> they<00:04:06.829> start<00:04:07.069> from<00:04:07.250> scratch 00:04:07.479 --> 00:04:07.489 align:start position:0% delete stuff and they start from scratch 00:04:07.489 --> 00:04:11.229 align:start position:0% delete stuff and they start from scratch I<00:04:07.940> can<00:04:08.780> assure<00:04:08.870> you<00:04:09.019> a<00:04:09.169> few<00:04:09.500> tricks<00:04:09.919> or<00:04:10.280> you 00:04:11.229 --> 00:04:11.239 align:start position:0% I can assure you a few tricks or you 00:04:11.239 --> 00:04:12.550 align:start position:0% I can assure you a few tricks or you know<00:04:11.329> just<00:04:11.389> try<00:04:11.629> to<00:04:11.690> explain<00:04:11.989> how<00:04:12.230> it<00:04:12.530> works 00:04:12.550 --> 00:04:12.560 align:start position:0% know just try to explain how it works 00:04:12.560 --> 00:04:14.650 align:start position:0% know just try to explain how it works internally<00:04:13.160> and<00:04:13.430> that<00:04:13.849> will<00:04:14.000> help<00:04:14.180> you<00:04:14.389> to 00:04:14.650 --> 00:04:14.660 align:start position:0% internally and that will help you to 00:04:14.660 --> 00:04:18.490 align:start position:0% internally and that will help you to understand<00:04:15.379> how<00:04:15.560> mango<00:04:16.220> works<00:04:17.169> and<00:04:18.169> don't<00:04:18.410> be 00:04:18.490 --> 00:04:18.500 align:start position:0% understand how mango works and don't be 00:04:18.500 --> 00:04:20.979 align:start position:0% understand how mango works and don't be afraid<00:04:18.530> it<00:04:18.949> won't<00:04:19.130> be<00:04:19.250> long<00:04:19.690> so<00:04:20.690> you<00:04:20.750> get 00:04:20.979 --> 00:04:20.989 align:start position:0% afraid it won't be long so you get 00:04:20.989 --> 00:04:23.350 align:start position:0% afraid it won't be long so you get everything<00:04:21.349> is<00:04:21.590> an<00:04:21.769> object<00:04:21.859> and<00:04:22.400> every<00:04:23.210> object 00:04:23.350 --> 00:04:23.360 align:start position:0% everything is an object and every object 00:04:23.360 --> 00:04:25.900 align:start position:0% everything is an object and every object has<00:04:23.690> an<00:04:23.900> identifier<00:04:24.500> that<00:04:24.800> this<00:04:25.340> identifier 00:04:25.900 --> 00:04:25.910 align:start position:0% has an identifier that this identifier 00:04:25.910 --> 00:04:28.990 align:start position:0% has an identifier that this identifier is<00:04:26.150> a<00:04:26.180> sha-1<00:04:26.510> hash<00:04:27.280> so<00:04:28.280> in<00:04:28.370> this<00:04:28.460> example<00:04:28.639> the 00:04:28.990 --> 00:04:29.000 align:start position:0% is a sha-1 hash so in this example the 00:04:29.000 --> 00:04:31.029 align:start position:0% is a sha-1 hash so in this example the first<00:04:29.270> one<00:04:29.449> example<00:04:29.780> I'm<00:04:30.260> just<00:04:30.800> putting 00:04:31.029 --> 00:04:31.039 align:start position:0% first one example I'm just putting 00:04:31.039 --> 00:04:34.210 align:start position:0% first one example I'm just putting putting<00:04:31.610> some<00:04:32.030> data<00:04:32.330> in<00:04:32.720> to<00:04:33.169> get<00:04:33.380> and<00:04:33.680> you<00:04:34.010> get 00:04:34.210 --> 00:04:34.220 align:start position:0% putting some data in to get and you get 00:04:34.220 --> 00:04:36.520 align:start position:0% putting some data in to get and you get back<00:04:34.430> the<00:04:34.550> identifier<00:04:35.060> and<00:04:35.750> of<00:04:36.140> course<00:04:36.169> once 00:04:36.520 --> 00:04:36.530 align:start position:0% back the identifier and of course once 00:04:36.530 --> 00:04:38.830 align:start position:0% back the identifier and of course once you<00:04:36.650> notice<00:04:36.800> identifier<00:04:37.550> you<00:04:38.150> can<00:04:38.390> print<00:04:38.719> the 00:04:38.830 --> 00:04:38.840 align:start position:0% you notice identifier you can print the 00:04:38.840 --> 00:04:40.119 align:start position:0% you notice identifier you can print the details 00:04:40.119 --> 00:04:40.129 align:start position:0% details 00:04:40.129 --> 00:04:42.279 align:start position:0% details so<00:04:40.249> there<00:04:40.759> I<00:04:40.789> just<00:04:40.969> loaded<00:04:41.419> a<00:04:41.629> file<00:04:41.869> which<00:04:42.139> at 00:04:42.279 --> 00:04:42.289 align:start position:0% so there I just loaded a file which at 00:04:42.289 --> 00:04:43.749 align:start position:0% so there I just loaded a file which at the<00:04:42.379> content<00:04:42.739> hello<00:04:42.979> material<00:04:43.459> hello 00:04:43.749 --> 00:04:43.759 align:start position:0% the content hello material hello 00:04:43.759 --> 00:04:47.320 align:start position:0% the content hello material hello Shanghai<00:04:44.149> on<00:04:45.129> the<00:04:46.129> file<00:04:46.429> system<00:04:46.610> all<00:04:47.029> these 00:04:47.320 --> 00:04:47.330 align:start position:0% Shanghai on the file system all these 00:04:47.330 --> 00:04:49.839 align:start position:0% Shanghai on the file system all these data<00:04:47.779> blobs<00:04:48.080> are<00:04:48.319> stalled<00:04:48.889> stored<00:04:49.580> in<00:04:49.789> a 00:04:49.839 --> 00:04:49.849 align:start position:0% data blobs are stalled stored in a 00:04:49.849 --> 00:04:53.139 align:start position:0% data blobs are stalled stored in a compressed<00:04:50.179> form<00:04:51.189> ok<00:04:52.189> so<00:04:52.249> now<00:04:52.550> I<00:04:52.699> have<00:04:52.729> data 00:04:53.139 --> 00:04:53.149 align:start position:0% compressed form ok so now I have data 00:04:53.149 --> 00:04:55.359 align:start position:0% compressed form ok so now I have data and<00:04:53.389> get<00:04:53.569> and<00:04:54.259> the<00:04:54.319> second<00:04:54.709> thing<00:04:54.739> I<00:04:54.949> need<00:04:55.159> is 00:04:55.359 --> 00:04:55.369 align:start position:0% and get and the second thing I need is 00:04:55.369 --> 00:04:58.089 align:start position:0% and get and the second thing I need is the<00:04:55.729> file<00:04:55.969> name<00:04:56.119> for<00:04:56.839> that<00:04:56.869> data<00:04:57.259> and<00:04:57.559> probably 00:04:58.089 --> 00:04:58.099 align:start position:0% the file name for that data and probably 00:04:58.099 --> 00:05:00.339 align:start position:0% the file name for that data and probably permissions<00:04:58.580> in<00:04:58.759> some<00:04:58.909> other<00:04:58.999> details<00:04:59.449> so<00:05:00.229> the 00:05:00.339 --> 00:05:00.349 align:start position:0% permissions in some other details so the 00:05:00.349 --> 00:05:02.559 align:start position:0% permissions in some other details so the second<00:05:00.679> object<00:05:00.860> think<00:05:01.249> it<00:05:01.429> is<00:05:01.909> called<00:05:02.239> trees 00:05:02.559 --> 00:05:02.569 align:start position:0% second object think it is called trees 00:05:02.569 --> 00:05:06.129 align:start position:0% second object think it is called trees and<00:05:03.669> creating<00:05:04.669> a<00:05:04.699> new<00:05:04.849> tree<00:05:05.029> is<00:05:05.149> simple<00:05:05.509> use 00:05:06.129 --> 00:05:06.139 align:start position:0% and creating a new tree is simple use 00:05:06.139 --> 00:05:09.699 align:start position:0% and creating a new tree is simple use the<00:05:06.439> identifier<00:05:07.339> of<00:05:07.369> the<00:05:07.759> data<00:05:07.999> and<00:05:08.330> you<00:05:09.019> set 00:05:09.699 --> 00:05:09.709 align:start position:0% the identifier of the data and you set 00:05:09.709 --> 00:05:12.219 align:start position:0% the identifier of the data and you set the<00:05:09.860> file<00:05:10.069> name<00:05:10.279> next<00:05:10.519> to<00:05:10.610> it<00:05:10.699> and<00:05:10.899> as<00:05:11.899> you<00:05:12.019> see 00:05:12.219 --> 00:05:12.229 align:start position:0% the file name next to it and as you see 00:05:12.229 --> 00:05:14.619 align:start position:0% the file name next to it and as you see printing<00:05:12.800> this<00:05:13.369> object<00:05:14.029> works<00:05:14.269> the<00:05:14.389> same<00:05:14.419> way 00:05:14.619 --> 00:05:14.629 align:start position:0% printing this object works the same way 00:05:14.629 --> 00:05:17.829 align:start position:0% printing this object works the same way as<00:05:14.959> previously<00:05:15.819> ok<00:05:16.819> at<00:05:16.909> this<00:05:17.059> stage<00:05:17.269> I<00:05:17.479> know 00:05:17.829 --> 00:05:17.839 align:start position:0% as previously ok at this stage I know 00:05:17.839 --> 00:05:19.659 align:start position:0% as previously ok at this stage I know what<00:05:18.110> my<00:05:18.259> data<00:05:18.469> is<00:05:18.709> I<00:05:18.860> know<00:05:18.919> what<00:05:19.189> the<00:05:19.279> fine<00:05:19.490> aim 00:05:19.659 --> 00:05:19.669 align:start position:0% what my data is I know what the fine aim 00:05:19.669 --> 00:05:22.689 align:start position:0% what my data is I know what the fine aim is<00:05:19.819> but<00:05:20.749> I<00:05:20.779> don't<00:05:21.110> know<00:05:21.289> who<00:05:22.069> created<00:05:22.669> that 00:05:22.689 --> 00:05:22.699 align:start position:0% is but I don't know who created that 00:05:22.699 --> 00:05:25.299 align:start position:0% is but I don't know who created that file<00:05:23.059> and<00:05:23.300> when<00:05:23.779> it<00:05:23.899> was<00:05:24.050> created<00:05:24.199> a<00:05:24.679> white<00:05:25.099> was 00:05:25.299 --> 00:05:25.309 align:start position:0% file and when it was created a white was 00:05:25.309 --> 00:05:27.969 align:start position:0% file and when it was created a white was created<00:05:25.789> so<00:05:26.599> the<00:05:26.719> third<00:05:26.869> object<00:05:27.110> we<00:05:27.529> have<00:05:27.709> is 00:05:27.969 --> 00:05:27.979 align:start position:0% created so the third object we have is 00:05:27.979 --> 00:05:31.359 align:start position:0% created so the third object we have is called<00:05:28.580> the<00:05:28.699> comet<00:05:29.029> and<00:05:29.839> it's<00:05:30.740> another<00:05:30.949> simple 00:05:31.359 --> 00:05:31.369 align:start position:0% called the comet and it's another simple 00:05:31.369 --> 00:05:33.129 align:start position:0% called the comet and it's another simple command<00:05:31.669> which<00:05:32.269> you<00:05:32.389> can<00:05:32.539> use<00:05:32.569> and<00:05:32.899> you<00:05:32.990> get 00:05:33.129 --> 00:05:33.139 align:start position:0% command which you can use and you get 00:05:33.139 --> 00:05:36.850 align:start position:0% command which you can use and you get back<00:05:33.409> another<00:05:34.369> simple<00:05:34.699> hash<00:05:35.709> similar<00:05:36.709> to 00:05:36.850 --> 00:05:36.860 align:start position:0% back another simple hash similar to 00:05:36.860 --> 00:05:39.279 align:start position:0% back another simple hash similar to before<00:05:37.099> you<00:05:37.610> can<00:05:37.759> print<00:05:37.969> that<00:05:38.089> hash<00:05:38.329> and<00:05:38.569> you 00:05:39.279 --> 00:05:39.289 align:start position:0% before you can print that hash and you 00:05:39.289 --> 00:05:40.989 align:start position:0% before you can print that hash and you get<00:05:39.559> the<00:05:39.679> familiar<00:05:40.129> display<00:05:40.550> which<00:05:40.819> you 00:05:40.989 --> 00:05:40.999 align:start position:0% get the familiar display which you 00:05:40.999 --> 00:05:43.629 align:start position:0% get the familiar display which you already<00:05:41.179> see<00:05:41.629> in<00:05:41.869> get<00:05:42.079> logs<00:05:42.459> so<00:05:43.459> I'm<00:05:43.519> not 00:05:43.629 --> 00:05:43.639 align:start position:0% already see in get logs so I'm not 00:05:43.639 --> 00:05:45.009 align:start position:0% already see in get logs so I'm not seeing<00:05:43.939> all<00:05:44.119> of<00:05:44.149> you<00:05:44.269> should<00:05:44.419> use<00:05:44.749> these 00:05:45.009 --> 00:05:45.019 align:start position:0% seeing all of you should use these 00:05:45.019 --> 00:05:47.199 align:start position:0% seeing all of you should use these comments<00:05:45.469> to<00:05:45.619> manage<00:05:46.099> get<00:05:46.309> because<00:05:46.939> you<00:05:47.089> do 00:05:47.199 --> 00:05:47.209 align:start position:0% comments to manage get because you do 00:05:47.209 --> 00:05:49.029 align:start position:0% comments to manage get because you do have<00:05:47.240> the<00:05:47.509> higher<00:05:47.689> level<00:05:48.050> systems<00:05:48.589> to<00:05:48.740> do<00:05:48.829> that 00:05:49.029 --> 00:05:49.039 align:start position:0% have the higher level systems to do that 00:05:49.039 --> 00:05:51.759 align:start position:0% have the higher level systems to do that but<00:05:49.699> because<00:05:49.939> of<00:05:49.969> these<00:05:50.240> three<00:05:50.629> objects<00:05:51.199> you 00:05:51.759 --> 00:05:51.769 align:start position:0% but because of these three objects you 00:05:51.769 --> 00:05:55.089 align:start position:0% but because of these three objects you can<00:05:51.919> represent<00:05:52.309> get<00:05:52.639> in<00:05:52.849> a<00:05:52.999> tree<00:05:53.269> and<00:05:53.919> the<00:05:54.919> leaf 00:05:55.089 --> 00:05:55.099 align:start position:0% can represent get in a tree and the leaf 00:05:55.099 --> 00:05:58.509 align:start position:0% can represent get in a tree and the leaf nodes<00:05:55.129> in<00:05:55.669> ingots<00:05:56.149> are<00:05:56.449> the<00:05:56.689> data<00:05:56.869> blobs<00:05:57.519> then 00:05:58.509 --> 00:05:58.519 align:start position:0% nodes in ingots are the data blobs then 00:05:58.519 --> 00:06:00.129 align:start position:0% nodes in ingots are the data blobs then you<00:05:58.639> associate<00:05:59.059> those<00:05:59.209> data<00:05:59.449> blobs<00:05:59.779> with<00:06:00.110> a 00:06:00.129 --> 00:06:00.139 align:start position:0% you associate those data blobs with a 00:06:00.139 --> 00:06:02.850 align:start position:0% you associate those data blobs with a fine<00:06:00.529> name<00:06:00.740> and<00:06:00.919> finally<00:06:01.399> with<00:06:01.519> the<00:06:01.610> comet<00:06:01.969> and 00:06:02.850 --> 00:06:02.860 align:start position:0% fine name and finally with the comet and 00:06:02.860 --> 00:06:04.869 align:start position:0% fine name and finally with the comet and subsequent<00:06:03.860> comets<00:06:04.159> can<00:06:04.279> refer<00:06:04.550> to<00:06:04.699> previous 00:06:04.869 --> 00:06:04.879 align:start position:0% subsequent comets can refer to previous 00:06:04.879 --> 00:06:07.629 align:start position:0% subsequent comets can refer to previous comments<00:06:05.419> etc<00:06:05.509> and<00:06:06.079> you<00:06:06.919> see<00:06:07.069> the<00:06:07.219> tree<00:06:07.429> is 00:06:07.629 --> 00:06:07.639 align:start position:0% comments etc and you see the tree is 00:06:07.639 --> 00:06:10.029 align:start position:0% comments etc and you see the tree is just<00:06:07.909> a<00:06:07.999> flat<00:06:08.179> structure<00:06:08.689> if<00:06:08.929> you<00:06:09.589> want<00:06:09.829> to 00:06:10.029 --> 00:06:10.039 align:start position:0% just a flat structure if you want to 00:06:10.039 --> 00:06:11.889 align:start position:0% just a flat structure if you want to have<00:06:10.219> multiple<00:06:10.519> directories<00:06:11.119> you<00:06:11.509> can<00:06:11.689> just 00:06:11.889 --> 00:06:11.899 align:start position:0% have multiple directories you can just 00:06:11.899 --> 00:06:14.889 align:start position:0% have multiple directories you can just change<00:06:12.139> trees<00:06:12.740> together<00:06:13.449> when<00:06:14.449> you<00:06:14.569> create<00:06:14.749> a 00:06:14.889 --> 00:06:14.899 align:start position:0% change trees together when you create a 00:06:14.899 --> 00:06:17.049 align:start position:0% change trees together when you create a merge<00:06:15.169> or<00:06:15.409> a<00:06:15.439> pull<00:06:15.679> request<00:06:16.059> multiple 00:06:17.049 --> 00:06:17.059 align:start position:0% merge or a pull request multiple 00:06:17.059 --> 00:06:19.239 align:start position:0% merge or a pull request multiple comments<00:06:17.269> will<00:06:17.599> be<00:06:17.629> referenced<00:06:18.319> in<00:06:18.439> the<00:06:18.979> next 00:06:19.239 --> 00:06:19.249 align:start position:0% comments will be referenced in the next 00:06:19.249 --> 00:06:22.059 align:start position:0% comments will be referenced in the next comment<00:06:19.659> ok<00:06:20.659> so<00:06:20.719> that<00:06:21.019> was<00:06:21.050> the<00:06:21.379> hard<00:06:21.649> part<00:06:21.709> a 00:06:22.059 --> 00:06:22.069 align:start position:0% comment ok so that was the hard part a 00:06:22.069 --> 00:06:23.859 align:start position:0% comment ok so that was the hard part a little<00:06:22.579> bit<00:06:22.669> what<00:06:23.029> kind<00:06:23.209> of<00:06:23.269> objects<00:06:23.749> we 00:06:23.859 --> 00:06:23.869 align:start position:0% little bit what kind of objects we 00:06:23.869 --> 00:06:26.019 align:start position:0% little bit what kind of objects we haven't<00:06:24.110> yet<00:06:24.229> but<00:06:25.069> you<00:06:25.189> can<00:06:25.219> see<00:06:25.579> we<00:06:25.729> have<00:06:25.759> all 00:06:26.019 --> 00:06:26.029 align:start position:0% haven't yet but you can see we have all 00:06:26.029 --> 00:06:28.569 align:start position:0% haven't yet but you can see we have all these<00:06:26.209> simple<00:06:26.719> bits<00:06:27.019> of<00:06:27.229> data<00:06:27.559> and<00:06:27.949> for<00:06:28.550> a 00:06:28.569 --> 00:06:28.579 align:start position:0% these simple bits of data and for a 00:06:28.579 --> 00:06:30.549 align:start position:0% these simple bits of data and for a single<00:06:28.939> comment<00:06:29.179> and<00:06:29.479> actual<00:06:29.809> you<00:06:30.529> know 00:06:30.549 --> 00:06:30.559 align:start position:0% single comment and actual you know 00:06:30.559 --> 00:06:32.290 align:start position:0% single comment and actual you know high-level<00:06:31.069> commitment<00:06:31.519> you<00:06:31.610> put<00:06:31.639> files<00:06:32.029> into 00:06:32.290 --> 00:06:32.300 align:start position:0% high-level commitment you put files into 00:06:32.300 --> 00:06:35.049 align:start position:0% high-level commitment you put files into your<00:06:32.509> git<00:06:32.719> repo<00:06:33.259> you<00:06:33.860> have<00:06:34.069> at<00:06:34.189> least<00:06:34.369> four 00:06:35.049 --> 00:06:35.059 align:start position:0% your git repo you have at least four 00:06:35.059 --> 00:06:39.339 align:start position:0% your git repo you have at least four five<00:06:35.509> objects<00:06:37.539> so<00:06:38.539> my<00:06:38.689> first<00:06:38.899> implementation 00:06:39.339 --> 00:06:39.349 align:start position:0% five objects so my first implementation 00:06:39.349 --> 00:06:41.469 align:start position:0% five objects so my first implementation of<00:06:39.619> mango<00:06:40.069> was<00:06:40.729> just<00:06:40.879> building<00:06:41.059> all<00:06:41.329> these 00:06:41.469 --> 00:06:41.479 align:start position:0% of mango was just building all these 00:06:41.479 --> 00:06:45.669 align:start position:0% of mango was just building all these objects<00:06:43.300> putting<00:06:44.300> all<00:06:44.449> these<00:06:44.569> objects<00:06:45.019> into 00:06:45.669 --> 00:06:45.679 align:start position:0% objects putting all these objects into 00:06:45.679 --> 00:06:48.879 align:start position:0% objects putting all these objects into any<00:06:45.889> theorem<00:06:46.159> contract<00:06:46.659> that<00:06:47.659> works<00:06:47.899> but 00:06:48.879 --> 00:06:48.889 align:start position:0% any theorem contract that works but 00:06:48.889 --> 00:06:51.100 align:start position:0% any theorem contract that works but probably<00:06:49.159> it's<00:06:49.279> not<00:06:49.399> very<00:06:49.519> useful<00:06:49.729> and<00:06:50.089> for<00:06:51.050> a 00:06:51.100 --> 00:06:51.110 align:start position:0% probably it's not very useful and for a 00:06:51.110 --> 00:06:53.890 align:start position:0% probably it's not very useful and for a simple<00:06:51.559> repo<00:06:51.860> of<00:06:52.069> a<00:06:52.550> couple<00:06:52.819> of<00:06:52.879> files<00:06:53.180> we 00:06:53.890 --> 00:06:53.900 align:start position:0% simple repo of a couple of files we 00:06:53.900 --> 00:06:55.780 align:start position:0% simple repo of a couple of files we just<00:06:54.590> a<00:06:54.650> hello<00:06:54.800> world<00:06:54.889> in<00:06:55.160> them<00:06:55.340> it<00:06:55.759> takes 00:06:55.780 --> 00:06:55.790 align:start position:0% just a hello world in them it takes 00:06:55.790 --> 00:06:59.020 align:start position:0% just a hello world in them it takes roughly<00:06:56.120> 50<00:06:56.570> million<00:06:56.840> gas<00:06:57.400> like<00:06:58.400> developers 00:06:59.020 --> 00:06:59.030 align:start position:0% roughly 50 million gas like developers 00:06:59.030 --> 00:07:01.030 align:start position:0% roughly 50 million gas like developers earn<00:06:59.270> a<00:06:59.300> lot<00:06:59.540> but<00:06:59.960> probably<00:07:00.259> they<00:07:00.590> don't<00:07:00.889> have 00:07:01.030 --> 00:07:01.040 align:start position:0% earn a lot but probably they don't have 00:07:01.040 --> 00:07:03.279 align:start position:0% earn a lot but probably they don't have enough<00:07:01.220> money<00:07:01.460> to<00:07:01.699> keep<00:07:02.300> up<00:07:02.539> with<00:07:02.570> typos 00:07:03.279 --> 00:07:03.289 align:start position:0% enough money to keep up with typos 00:07:03.289 --> 00:07:05.439 align:start position:0% enough money to keep up with typos changes<00:07:03.830> and<00:07:04.340> pushing<00:07:04.669> attempt<00:07:04.910> to<00:07:05.030> an<00:07:05.090> atrium 00:07:05.439 --> 00:07:05.449 align:start position:0% changes and pushing attempt to an atrium 00:07:05.449 --> 00:07:08.730 align:start position:0% changes and pushing attempt to an atrium contract<00:07:06.280> so<00:07:07.280> better<00:07:07.520> implementation<00:07:08.120> is 00:07:08.730 --> 00:07:08.740 align:start position:0% contract so better implementation is 00:07:08.740 --> 00:07:11.260 align:start position:0% contract so better implementation is realizing<00:07:09.740> the<00:07:09.830> fact<00:07:10.070> that<00:07:10.160> we<00:07:10.340> can<00:07:10.490> use<00:07:10.520> IVFs 00:07:11.260 --> 00:07:11.270 align:start position:0% realizing the fact that we can use IVFs 00:07:11.270 --> 00:07:15.430 align:start position:0% realizing the fact that we can use IVFs and<00:07:11.570> swarm<00:07:12.490> so<00:07:13.490> this<00:07:14.270> is<00:07:14.330> what<00:07:14.449> I<00:07:14.479> did<00:07:14.660> and<00:07:14.840> I 00:07:15.430 --> 00:07:15.440 align:start position:0% and swarm so this is what I did and I 00:07:15.440 --> 00:07:18.010 align:start position:0% and swarm so this is what I did and I put<00:07:15.680> all<00:07:15.919> these<00:07:16.280> objects<00:07:16.820> into<00:07:17.570> IP<00:07:17.720> offense 00:07:18.010 --> 00:07:18.020 align:start position:0% put all these objects into IP offense 00:07:18.020 --> 00:07:21.159 align:start position:0% put all these objects into IP offense and<00:07:18.139> swarm<00:07:18.440> but<00:07:19.160> as<00:07:19.280> I've<00:07:19.430> mentioned<00:07:19.780> get<00:07:20.780> uses 00:07:21.159 --> 00:07:21.169 align:start position:0% and swarm but as I've mentioned get uses 00:07:21.169 --> 00:07:23.830 align:start position:0% and swarm but as I've mentioned get uses sha-1<00:07:21.710> heshes<00:07:22.280> and<00:07:22.520> probably<00:07:23.449> all<00:07:23.600> of<00:07:23.630> you 00:07:23.830 --> 00:07:23.840 align:start position:0% sha-1 heshes and probably all of you 00:07:23.840 --> 00:07:26.529 align:start position:0% sha-1 heshes and probably all of you know<00:07:23.990> that<00:07:24.229> I<00:07:24.380> PFS<00:07:24.800> doesn't<00:07:25.310> so<00:07:25.699> shavon<00:07:26.300> isn't 00:07:26.529 --> 00:07:26.539 align:start position:0% know that I PFS doesn't so shavon isn't 00:07:26.539 --> 00:07:30.010 align:start position:0% know that I PFS doesn't so shavon isn't really<00:07:26.690> good<00:07:26.840> anymore<00:07:27.880> we<00:07:28.880> could<00:07:29.090> change<00:07:29.389> get 00:07:30.010 --> 00:07:30.020 align:start position:0% really good anymore we could change get 00:07:30.020 --> 00:07:32.950 align:start position:0% really good anymore we could change get do<00:07:30.590> not<00:07:30.740> use<00:07:30.949> shavon<00:07:31.400> but<00:07:32.210> unfortunately<00:07:32.810> it's 00:07:32.950 --> 00:07:32.960 align:start position:0% do not use shavon but unfortunately it's 00:07:32.960 --> 00:07:34.840 align:start position:0% do not use shavon but unfortunately it's really<00:07:33.139> tied<00:07:33.380> in<00:07:33.680> which<00:07:33.889> have<00:07:34.130> one<00:07:34.310> and<00:07:34.490> we 00:07:34.840 --> 00:07:34.850 align:start position:0% really tied in which have one and we 00:07:34.850 --> 00:07:37.240 align:start position:0% really tied in which have one and we want<00:07:35.000> to<00:07:35.210> keep<00:07:35.419> a<00:07:35.750> backwards<00:07:36.620> compatibility 00:07:37.240 --> 00:07:37.250 align:start position:0% want to keep a backwards compatibility 00:07:37.250 --> 00:07:39.279 align:start position:0% want to keep a backwards compatibility with<00:07:37.280> every<00:07:37.850> tool<00:07:38.000> you<00:07:38.060> have<00:07:38.240> today<00:07:38.510> as<00:07:39.050> well 00:07:39.279 --> 00:07:39.289 align:start position:0% with every tool you have today as well 00:07:39.289 --> 00:07:42.250 align:start position:0% with every tool you have today as well as<00:07:39.580> solutions<00:07:40.580> like<00:07:40.699> github<00:07:40.970> so<00:07:41.900> we<00:07:42.020> cannot 00:07:42.250 --> 00:07:42.260 align:start position:0% as solutions like github so we cannot 00:07:42.260 --> 00:07:44.950 align:start position:0% as solutions like github so we cannot change<00:07:42.320> that<00:07:42.910> well<00:07:43.910> a<00:07:43.940> simple<00:07:44.330> solution<00:07:44.419> is<00:07:44.780> to 00:07:44.950 --> 00:07:44.960 align:start position:0% change that well a simple solution is to 00:07:44.960 --> 00:07:50.010 align:start position:0% change that well a simple solution is to map<00:07:45.169> I<00:07:45.490> PFS<00:07:46.490> identifiers<00:07:47.479> to<00:07:47.930> get<00:07:48.710> identifiers 00:07:50.010 --> 00:07:50.020 align:start position:0% map I PFS identifiers to get identifiers 00:07:50.020 --> 00:07:53.230 align:start position:0% map I PFS identifiers to get identifiers so<00:07:51.020> what<00:07:51.139> this<00:07:51.229> means<00:07:51.470> is<00:07:51.770> I<00:07:52.070> push<00:07:52.759> every 00:07:53.230 --> 00:07:53.240 align:start position:0% so what this means is I push every 00:07:53.240 --> 00:07:56.499 align:start position:0% so what this means is I push every single<00:07:53.570> object<00:07:53.720> to<00:07:54.530> I<00:07:54.560> PFS<00:07:55.090> then<00:07:56.090> i<00:07:56.180> create<00:07:56.240> a 00:07:56.499 --> 00:07:56.509 align:start position:0% single object to I PFS then i create a 00:07:56.509 --> 00:07:58.990 align:start position:0% single object to I PFS then i create a snapshot<00:07:56.630> file<00:07:57.199> of<00:07:57.410> the<00:07:58.010> mapping<00:07:58.370> of<00:07:58.550> these 00:07:58.990 --> 00:07:59.000 align:start position:0% snapshot file of the mapping of these 00:07:59.000 --> 00:08:02.350 align:start position:0% snapshot file of the mapping of these identifiers<00:07:59.630> and<00:07:59.930> i<00:08:00.470> push<00:08:00.770> this<00:08:01.550> snapshot<00:08:01.820> 52 00:08:02.350 --> 00:08:02.360 align:start position:0% identifiers and i push this snapshot 52 00:08:02.360 --> 00:08:05.140 align:start position:0% identifiers and i push this snapshot 52 I<00:08:02.389> PFS<00:08:02.870> as<00:08:03.020> well<00:08:03.460> okay<00:08:04.460> so<00:08:04.520> why<00:08:04.699> do<00:08:04.760> you<00:08:04.849> need<00:08:04.910> it 00:08:05.140 --> 00:08:05.150 align:start position:0% I PFS as well okay so why do you need it 00:08:05.150 --> 00:08:07.120 align:start position:0% I PFS as well okay so why do you need it here<00:08:05.330> IAM<00:08:05.449> right<00:08:05.960> well<00:08:06.620> you<00:08:06.800> don't<00:08:06.919> actually 00:08:07.120 --> 00:08:07.130 align:start position:0% here IAM right well you don't actually 00:08:07.130 --> 00:08:09.899 align:start position:0% here IAM right well you don't actually need<00:08:07.340> a<00:08:07.520> theorem<00:08:07.910> at<00:08:08.630> least<00:08:08.840> to<00:08:08.960> this<00:08:09.050> level 00:08:09.899 --> 00:08:09.909 align:start position:0% need a theorem at least to this level 00:08:09.909 --> 00:08:12.760 align:start position:0% need a theorem at least to this level when<00:08:10.909> you<00:08:11.030> push<00:08:11.300> all<00:08:11.599> your<00:08:11.630> content<00:08:12.080> to<00:08:12.260> I<00:08:12.289> PFS 00:08:12.760 --> 00:08:12.770 align:start position:0% when you push all your content to I PFS 00:08:12.770 --> 00:08:15.000 align:start position:0% when you push all your content to I PFS you<00:08:13.039> get<00:08:13.250> this<00:08:13.400> top-level<00:08:13.669> snapshot<00:08:14.300> file<00:08:14.539> and 00:08:15.000 --> 00:08:15.010 align:start position:0% you get this top-level snapshot file and 00:08:15.010 --> 00:08:18.339 align:start position:0% you get this top-level snapshot file and you<00:08:16.010> can<00:08:16.039> give<00:08:16.340> this<00:08:16.580> snapshot<00:08:17.050> identifier<00:08:18.050> to 00:08:18.339 --> 00:08:18.349 align:start position:0% you can give this snapshot identifier to 00:08:18.349 --> 00:08:20.200 align:start position:0% you can give this snapshot identifier to anyone<00:08:18.800> you<00:08:19.280> want<00:08:19.430> to<00:08:19.490> give<00:08:19.580> your<00:08:19.669> coat<00:08:19.970> too 00:08:20.200 --> 00:08:20.210 align:start position:0% anyone you want to give your coat too 00:08:20.210 --> 00:08:22.589 align:start position:0% anyone you want to give your coat too they<00:08:20.780> can<00:08:20.960> download<00:08:21.289> your<00:08:21.440> code<00:08:21.650> that<00:08:21.949> way 00:08:22.589 --> 00:08:22.599 align:start position:0% they can download your code that way 00:08:22.599 --> 00:08:25.779 align:start position:0% they can download your code that way however<00:08:23.599> if<00:08:23.930> they<00:08:24.440> make<00:08:24.650> changes<00:08:25.130> or<00:08:25.310> you<00:08:25.400> make 00:08:25.779 --> 00:08:25.789 align:start position:0% however if they make changes or you make 00:08:25.789 --> 00:08:27.939 align:start position:0% however if they make changes or you make changes<00:08:26.000> you're<00:08:26.810> going<00:08:26.990> to<00:08:27.080> get<00:08:27.199> a<00:08:27.440> new 00:08:27.939 --> 00:08:27.949 align:start position:0% changes you're going to get a new 00:08:27.949 --> 00:08:30.610 align:start position:0% changes you're going to get a new snapshot<00:08:28.280> identifier<00:08:29.060> so<00:08:29.960> then<00:08:30.110> you<00:08:30.260> have<00:08:30.500> to 00:08:30.610 --> 00:08:30.620 align:start position:0% snapshot identifier so then you have to 00:08:30.620 --> 00:08:33.070 align:start position:0% snapshot identifier so then you have to give<00:08:30.770> that<00:08:31.120> identify<00:08:32.120> to<00:08:32.180> them<00:08:32.450> they<00:08:32.900> make 00:08:33.070 --> 00:08:33.080 align:start position:0% give that identify to them they make 00:08:33.080 --> 00:08:35.079 align:start position:0% give that identify to them they make changes<00:08:33.500> they<00:08:33.890> give<00:08:34.039> a<00:08:34.070> new<00:08:34.279> one<00:08:34.459> you<00:08:34.909> make 00:08:35.079 --> 00:08:35.089 align:start position:0% changes they give a new one you make 00:08:35.089 --> 00:08:37.540 align:start position:0% changes they give a new one you make changes<00:08:35.240> give<00:08:36.110> a<00:08:36.140> new<00:08:36.320> one<00:08:36.469> it's<00:08:37.159> not<00:08:37.370> really 00:08:37.540 --> 00:08:37.550 align:start position:0% changes give a new one it's not really 00:08:37.550 --> 00:08:40.240 align:start position:0% changes give a new one it's not really practical<00:08:38.320> so<00:08:39.320> this<00:08:39.500> is<00:08:39.529> where<00:08:39.800> a<00:08:39.950> theorem 00:08:40.240 --> 00:08:40.250 align:start position:0% practical so this is where a theorem 00:08:40.250 --> 00:08:42.820 align:start position:0% practical so this is where a theorem comes<00:08:40.490> into<00:08:40.820> play<00:08:41.390> and<00:08:41.599> it<00:08:41.750> makes<00:08:42.020> this<00:08:42.589> a 00:08:42.820 --> 00:08:42.830 align:start position:0% comes into play and it makes this a 00:08:42.830 --> 00:08:48.269 align:start position:0% comes into play and it makes this a practical<00:08:43.310> solution<00:08:44.560> so<00:08:45.560> at<00:08:46.220> every<00:08:46.970> gate<00:08:47.300> push 00:08:48.269 --> 00:08:48.279 align:start position:0% practical solution so at every gate push 00:08:48.279 --> 00:08:51.730 align:start position:0% practical solution so at every gate push they<00:08:49.279> push<00:08:49.310> to<00:08:49.790> details<00:08:50.209> into<00:08:50.510> a<00:08:51.350> mango 00:08:51.730 --> 00:08:51.740 align:start position:0% they push to details into a mango 00:08:51.740 --> 00:08:53.920 align:start position:0% they push to details into a mango contract<00:08:52.220> which<00:08:52.760> is<00:08:52.970> what<00:08:53.510> was<00:08:53.660> the<00:08:53.750> latest 00:08:53.920 --> 00:08:53.930 align:start position:0% contract which is what was the latest 00:08:53.930 --> 00:08:56.860 align:start position:0% contract which is what was the latest comet<00:08:54.440> which<00:08:55.010> is<00:08:55.220> the<00:08:55.580> gate<00:08:55.760> identifier<00:08:56.630> and 00:08:56.860 --> 00:08:56.870 align:start position:0% comet which is the gate identifier and 00:08:56.870 --> 00:09:00.280 align:start position:0% comet which is the gate identifier and the<00:08:57.800> location<00:08:58.250> of<00:08:58.310> this<00:08:58.520> snapshot<00:08:59.120> pie<00:08:59.510> and 00:09:00.280 --> 00:09:00.290 align:start position:0% the location of this snapshot pie and 00:09:00.290 --> 00:09:02.380 align:start position:0% the location of this snapshot pie and today<00:09:00.950> it<00:09:01.040> is<00:09:01.220> cost<00:09:01.459> hundred<00:09:01.820> forty<00:09:02.089> thousand 00:09:02.380 --> 00:09:02.390 align:start position:0% today it is cost hundred forty thousand 00:09:02.390 --> 00:09:04.660 align:start position:0% today it is cost hundred forty thousand gas<00:09:02.570> which<00:09:03.170> is<00:09:03.200> a<00:09:03.350> big<00:09:03.620> difference<00:09:03.890> 250 00:09:04.660 --> 00:09:04.670 align:start position:0% gas which is a big difference 250 00:09:04.670 --> 00:09:07.540 align:start position:0% gas which is a big difference 250 million<00:09:04.850> and<00:09:05.440> this<00:09:06.440> contract<00:09:06.829> isn't<00:09:06.950> optic 00:09:07.540 --> 00:09:07.550 align:start position:0% million and this contract isn't optic 00:09:07.550 --> 00:09:11.800 align:start position:0% million and this contract isn't optic so<00:09:08.120> this<00:09:08.300> could<00:09:08.450> even<00:09:08.570> go<00:09:09.080> for<00:09:09.290> the<00:09:09.470> deck<00:09:10.810> so 00:09:11.800 --> 00:09:11.810 align:start position:0% so this could even go for the deck so 00:09:11.810 --> 00:09:14.230 align:start position:0% so this could even go for the deck so what<00:09:12.230> is<00:09:12.260> mango<00:09:12.830> and<00:09:13.070> mango<00:09:13.370> is<00:09:13.490> actually<00:09:14.000> a 00:09:14.230 --> 00:09:14.240 align:start position:0% what is mango and mango is actually a 00:09:14.240 --> 00:09:16.240 align:start position:0% what is mango and mango is actually a couple<00:09:14.510> of<00:09:14.690> things<00:09:14.899> it<00:09:15.800> defines<00:09:16.130> the 00:09:16.240 --> 00:09:16.250 align:start position:0% couple of things it defines the 00:09:16.250 --> 00:09:19.630 align:start position:0% couple of things it defines the semantics<00:09:16.850> had<00:09:17.480> to<00:09:17.660> store<00:09:17.990> get<00:09:18.230> objects<00:09:18.860> in<00:09:19.010> I 00:09:19.630 --> 00:09:19.640 align:start position:0% semantics had to store get objects in I 00:09:19.640 --> 00:09:23.050 align:start position:0% semantics had to store get objects in I PFS<00:09:20.060> or<00:09:20.269> swarm<00:09:20.570> it<00:09:21.350> also<00:09:22.220> defines<00:09:22.459> a<00:09:22.700> contract 00:09:23.050 --> 00:09:23.060 align:start position:0% PFS or swarm it also defines a contract 00:09:23.060 --> 00:09:26.800 align:start position:0% PFS or swarm it also defines a contract interface<00:09:23.860> for<00:09:24.860> itanium<00:09:25.250> it<00:09:26.149> gives<00:09:26.480> you<00:09:26.660> an 00:09:26.800 --> 00:09:26.810 align:start position:0% interface for itanium it gives you an 00:09:26.810 --> 00:09:28.870 align:start position:0% interface for itanium it gives you an implementation<00:09:27.260> for<00:09:27.740> the<00:09:27.829> get<00:09:27.980> back<00:09:28.190> end<00:09:28.399> in 00:09:28.870 --> 00:09:28.880 align:start position:0% implementation for the get back end in 00:09:28.880 --> 00:09:31.810 align:start position:0% implementation for the get back end in able<00:09:29.209> to<00:09:29.589> communicate<00:09:30.589> with<00:09:30.980> each<00:09:31.190> here<00:09:31.670> iam 00:09:31.810 --> 00:09:31.820 align:start position:0% able to communicate with each here iam 00:09:31.820 --> 00:09:35.590 align:start position:0% able to communicate with each here iam and<00:09:32.029> I<00:09:32.510> BFS<00:09:32.959> and<00:09:33.430> it<00:09:34.430> also<00:09:34.579> gives<00:09:34.700> you<00:09:34.940> admin 00:09:35.590 --> 00:09:35.600 align:start position:0% and I BFS and it also gives you admin 00:09:35.600 --> 00:09:42.370 align:start position:0% and I BFS and it also gives you admin tools<00:09:35.870> to<00:09:36.860> create<00:09:37.040> repos<00:09:39.850> so<00:09:40.850> every<00:09:41.360> git<00:09:41.690> repo 00:09:42.370 --> 00:09:42.380 align:start position:0% tools to create repos so every git repo 00:09:42.380 --> 00:09:45.310 align:start position:0% tools to create repos so every git repo has<00:09:42.890> its<00:09:43.070> own<00:09:43.250> contract<00:09:43.850> there's<00:09:44.750> no<00:09:44.930> point 00:09:45.310 --> 00:09:45.320 align:start position:0% has its own contract there's no point 00:09:45.320 --> 00:09:47.050 align:start position:0% has its own contract there's no point making<00:09:45.620> this<00:09:45.950> complex<00:09:46.370> and<00:09:46.610> having<00:09:46.910> a 00:09:47.050 --> 00:09:47.060 align:start position:0% making this complex and having a 00:09:47.060 --> 00:09:49.269 align:start position:0% making this complex and having a contract<00:09:47.839> for<00:09:48.260> a<00:09:48.320> number<00:09:48.589> of<00:09:48.680> repositories 00:09:49.269 --> 00:09:49.279 align:start position:0% contract for a number of repositories 00:09:49.279 --> 00:09:51.819 align:start position:0% contract for a number of repositories this<00:09:49.790> has<00:09:50.029> to<00:09:50.209> be<00:09:50.300> simple<00:09:50.720> and<00:09:50.899> you<00:09:51.709> know 00:09:51.819 --> 00:09:51.829 align:start position:0% this has to be simple and you know 00:09:51.829 --> 00:09:55.240 align:start position:0% this has to be simple and you know secure<00:09:52.550> as<00:09:52.670> it<00:09:52.700> can<00:09:53.260> so<00:09:54.260> what<00:09:54.470> the<00:09:54.680> etherium 00:09:55.240 --> 00:09:55.250 align:start position:0% secure as it can so what the etherium 00:09:55.250 --> 00:09:58.509 align:start position:0% secure as it can so what the etherium does<00:09:55.459> on<00:09:55.670> top<00:09:55.820> of<00:09:55.970> this<00:09:56.149> it<00:09:56.390> can<00:09:57.250> manage<00:09:58.250> access 00:09:58.509 --> 00:09:58.519 align:start position:0% does on top of this it can manage access 00:09:58.519 --> 00:10:00.579 align:start position:0% does on top of this it can manage access control<00:09:59.120> and<00:09:59.390> you're<00:10:00.140> also<00:10:00.320> free<00:10:00.500> to 00:10:00.579 --> 00:10:00.589 align:start position:0% control and you're also free to 00:10:00.589 --> 00:10:02.170 align:start position:0% control and you're also free to implement<00:10:01.010> whatever<00:10:01.220> else<00:10:01.550> you<00:10:01.700> want<00:10:01.730> add 00:10:02.170 --> 00:10:02.180 align:start position:0% implement whatever else you want add 00:10:02.180 --> 00:10:04.960 align:start position:0% implement whatever else you want add there's<00:10:03.110> just<00:10:03.320> a<00:10:03.380> repo<00:10:03.680> interface<00:10:04.130> you<00:10:04.820> have 00:10:04.960 --> 00:10:04.970 align:start position:0% there's just a repo interface you have 00:10:04.970 --> 00:10:07.000 align:start position:0% there's just a repo interface you have to<00:10:05.089> conform<00:10:05.420> to<00:10:05.660> but<00:10:06.140> in<00:10:06.230> if<00:10:06.350> anything<00:10:06.829> else 00:10:07.000 --> 00:10:07.010 align:start position:0% to conform to but in if anything else 00:10:07.010 --> 00:10:11.319 align:start position:0% to conform to but in if anything else you<00:10:07.130> do<00:10:07.279> is<00:10:07.490> up<00:10:07.550> to<00:10:07.790> you<00:10:08.680> m<00:10:10.000> for<00:10:11.000> the<00:10:11.029> actual 00:10:11.319 --> 00:10:11.329 align:start position:0% you do is up to you m for the actual 00:10:11.329 --> 00:10:13.780 align:start position:0% you do is up to you m for the actual repo<00:10:11.630> contract<00:10:12.110> which<00:10:12.740> uses<00:10:13.339> hundred<00:10:13.579> forty 00:10:13.780 --> 00:10:13.790 align:start position:0% repo contract which uses hundred forty 00:10:13.790 --> 00:10:15.550 align:start position:0% repo contract which uses hundred forty thousand<00:10:14.060> gasps<00:10:14.209> there's<00:10:14.959> an<00:10:15.110> implementation 00:10:15.550 --> 00:10:15.560 align:start position:0% thousand gasps there's an implementation 00:10:15.560 --> 00:10:21.010 align:start position:0% thousand gasps there's an implementation in<00:10:16.010> the<00:10:16.279> mango<00:10:16.790> admin<00:10:17.209> tool<00:10:18.110> chain<00:10:19.600> is<00:10:20.600> it<00:10:20.839> this 00:10:21.010 --> 00:10:21.020 align:start position:0% in the mango admin tool chain is it this 00:10:21.020 --> 00:10:22.420 align:start position:0% in the mango admin tool chain is it this is<00:10:21.170> an<00:10:21.230> actual<00:10:21.350> example<00:10:21.529> how<00:10:21.890> to<00:10:21.950> use<00:10:22.160> the<00:10:22.250> tool 00:10:22.420 --> 00:10:22.430 align:start position:0% is an actual example how to use the tool 00:10:22.430 --> 00:10:24.490 align:start position:0% is an actual example how to use the tool chain<00:10:22.670> and<00:10:22.880> once<00:10:23.690> you<00:10:23.779> install<00:10:23.959> it<00:10:24.079> you<00:10:24.320> can 00:10:24.490 --> 00:10:24.500 align:start position:0% chain and once you install it you can 00:10:24.500 --> 00:10:27.100 align:start position:0% chain and once you install it you can create<00:10:25.010> repos<00:10:25.640> this<00:10:26.270> of<00:10:26.480> course<00:10:26.540> will<00:10:26.930> need 00:10:27.100 --> 00:10:27.110 align:start position:0% create repos this of course will need 00:10:27.110 --> 00:10:30.850 align:start position:0% create repos this of course will need access<00:10:27.320> to<00:10:27.560> an<00:10:28.070> idiom<00:10:28.850> RPC<00:10:29.390> node<00:10:29.660> as<00:10:29.930> well<00:10:30.770> as 00:10:30.850 --> 00:10:30.860 align:start position:0% access to an idiom RPC node as well as 00:10:30.860 --> 00:10:33.639 align:start position:0% access to an idiom RPC node as well as to<00:10:30.980> I<00:10:31.040> PFS<00:10:31.430> or<00:10:31.640> swarm<00:10:32.000> so<00:10:32.870> once<00:10:33.050> you<00:10:33.170> create<00:10:33.470> it 00:10:33.639 --> 00:10:33.649 align:start position:0% to I PFS or swarm so once you create it 00:10:33.649 --> 00:10:35.740 align:start position:0% to I PFS or swarm so once you create it you<00:10:33.800> get<00:10:33.950> any<00:10:34.190> tea<00:10:34.339> room<00:10:34.520> address<00:10:34.880> and<00:10:35.120> that's 00:10:35.740 --> 00:10:35.750 align:start position:0% you get any tea room address and that's 00:10:35.750 --> 00:10:38.530 align:start position:0% you get any tea room address and that's the<00:10:35.839> address<00:10:36.079> of<00:10:36.320> your<00:10:36.589> repo<00:10:37.300> then<00:10:38.300> you<00:10:38.390> can 00:10:38.530 --> 00:10:38.540 align:start position:0% the address of your repo then you can 00:10:38.540 --> 00:10:40.300 align:start position:0% the address of your repo then you can create<00:10:38.779> new<00:10:38.810> users<00:10:39.320> you<00:10:39.529> can<00:10:39.649> delete<00:10:39.860> users 00:10:40.300 --> 00:10:40.310 align:start position:0% create new users you can delete users 00:10:40.310 --> 00:10:42.460 align:start position:0% create new users you can delete users you<00:10:40.579> can<00:10:40.640> set<00:10:40.940> administration<00:10:41.600> rights<00:10:41.839> and<00:10:42.290> a 00:10:42.460 --> 00:10:42.470 align:start position:0% you can set administration rights and a 00:10:42.470 --> 00:10:44.650 align:start position:0% you can set administration rights and a couple<00:10:42.649> of<00:10:42.770> other<00:10:42.890> things<00:10:43.540> okay<00:10:44.540> at<00:10:44.600> this 00:10:44.650 --> 00:10:44.660 align:start position:0% couple of other things okay at this 00:10:44.660 --> 00:10:47.740 align:start position:0% couple of other things okay at this stage<00:10:45.020> you<00:10:45.290> have<00:10:45.709> your<00:10:46.100> repository<00:10:46.790> so<00:10:47.600> the 00:10:47.740 --> 00:10:47.750 align:start position:0% stage you have your repository so the 00:10:47.750 --> 00:10:50.579 align:start position:0% stage you have your repository so the next<00:10:47.899> thing<00:10:48.050> is<00:10:48.230> to<00:10:48.440> upload<00:10:49.040> data<00:10:49.279> into<00:10:49.730> it 00:10:50.579 --> 00:10:50.589 align:start position:0% next thing is to upload data into it 00:10:50.589 --> 00:10:53.560 align:start position:0% next thing is to upload data into it assuming<00:10:51.589> you<00:10:51.620> have<00:10:51.920> your<00:10:52.130> repo<00:10:52.459> already<00:10:52.760> you 00:10:53.560 --> 00:10:53.570 align:start position:0% assuming you have your repo already you 00:10:53.570 --> 00:10:55.930 align:start position:0% assuming you have your repo already you just<00:10:53.839> have<00:10:54.020> to<00:10:54.050> set<00:10:54.529> up<00:10:54.649> the<00:10:54.800> endpoint<00:10:55.310> which 00:10:55.930 --> 00:10:55.940 align:start position:0% just have to set up the endpoint which 00:10:55.940 --> 00:10:58.480 align:start position:0% just have to set up the endpoint which is<00:10:56.149> your<00:10:56.540> contract<00:10:57.050> address<00:10:57.410> and<00:10:58.220> you<00:10:58.459> can 00:10:58.480 --> 00:10:58.490 align:start position:0% is your contract address and you can 00:10:58.490 --> 00:11:02.139 align:start position:0% is your contract address and you can push<00:10:58.910> data<00:10:59.720> into<00:11:00.680> this<00:11:00.829> repo<00:11:01.279> let's<00:11:02.000> mention 00:11:02.139 --> 00:11:02.149 align:start position:0% push data into this repo let's mention 00:11:02.149 --> 00:11:04.090 align:start position:0% push data into this repo let's mention before<00:11:02.390> we<00:11:02.779> don't<00:11:03.260> really<00:11:03.380> store<00:11:03.620> the<00:11:03.709> data<00:11:03.829> in 00:11:04.090 --> 00:11:04.100 align:start position:0% before we don't really store the data in 00:11:04.100 --> 00:11:06.699 align:start position:0% before we don't really store the data in the<00:11:04.190> repo<00:11:04.490> but<00:11:05.089> we<00:11:05.209> need<00:11:05.360> to<00:11:05.449> update<00:11:05.709> the 00:11:06.699 --> 00:11:06.709 align:start position:0% the repo but we need to update the 00:11:06.709 --> 00:11:10.540 align:start position:0% the repo but we need to update the references<00:11:07.279> in<00:11:07.490> your<00:11:07.940> repo<00:11:09.160> okay<00:11:10.160> now<00:11:10.490> you 00:11:10.540 --> 00:11:10.550 align:start position:0% references in your repo okay now you 00:11:10.550 --> 00:11:14.680 align:start position:0% references in your repo okay now you have<00:11:11.000> all<00:11:11.240> your<00:11:11.630> content<00:11:12.019> a<00:11:12.310> decentralized<00:11:13.690> so 00:11:14.680 --> 00:11:14.690 align:start position:0% have all your content a decentralized so 00:11:14.690 --> 00:11:15.850 align:start position:0% have all your content a decentralized so it's<00:11:14.810> time<00:11:14.959> to<00:11:14.990> share<00:11:15.350> it<00:11:15.470> with<00:11:15.589> your<00:11:15.709> friends 00:11:15.850 --> 00:11:15.860 align:start position:0% it's time to share it with your friends 00:11:15.860 --> 00:11:18.610 align:start position:0% it's time to share it with your friends and<00:11:16.160> they<00:11:16.790> can<00:11:16.970> download<00:11:17.300> it<00:11:17.329> as<00:11:17.570> well 00:11:18.610 --> 00:11:18.620 align:start position:0% and they can download it as well 00:11:18.620 --> 00:11:21.100 align:start position:0% and they can download it as well since<00:11:19.580> you<00:11:19.790> are<00:11:19.820> able<00:11:20.120> to<00:11:20.420> create<00:11:20.630> multiple 00:11:21.100 --> 00:11:21.110 align:start position:0% since you are able to create multiple 00:11:21.110 --> 00:11:23.410 align:start position:0% since you are able to create multiple accounts<00:11:21.710> in<00:11:21.980> your<00:11:22.130> repo<00:11:22.490> contract<00:11:22.970> your 00:11:23.410 --> 00:11:23.420 align:start position:0% accounts in your repo contract your 00:11:23.420 --> 00:11:25.780 align:start position:0% accounts in your repo contract your friends<00:11:23.720> are<00:11:23.810> able<00:11:24.080> to<00:11:24.230> push<00:11:24.500> changes<00:11:25.490> to<00:11:25.670> your 00:11:25.780 --> 00:11:25.790 align:start position:0% friends are able to push changes to your 00:11:25.790 --> 00:11:31.300 align:start position:0% friends are able to push changes to your repo<00:11:26.120> at<00:11:26.570> the<00:11:26.720> same<00:11:26.900> time<00:11:29.830> while<00:11:30.830> you<00:11:31.190> know 00:11:31.300 --> 00:11:31.310 align:start position:0% repo at the same time while you know 00:11:31.310 --> 00:11:33.730 align:start position:0% repo at the same time while you know contract<00:11:31.700> addresses<00:11:32.090> work<00:11:32.300> I<00:11:32.540> think<00:11:32.990> there 00:11:33.730 --> 00:11:33.740 align:start position:0% contract addresses work I think there 00:11:33.740 --> 00:11:35.290 align:start position:0% contract addresses work I think there will<00:11:33.830> be<00:11:33.890> a<00:11:34.010> better<00:11:34.160> way<00:11:34.340> to<00:11:34.370> do<00:11:34.610> that<00:11:34.730> and<00:11:34.910> I 00:11:35.290 --> 00:11:35.300 align:start position:0% will be a better way to do that and I 00:11:35.300 --> 00:11:37.180 align:start position:0% will be a better way to do that and I hope<00:11:35.540> ens<00:11:35.960> or<00:11:36.140> a<00:11:36.170> similar<00:11:36.470> system<00:11:36.650> will<00:11:36.920> come 00:11:37.180 --> 00:11:37.190 align:start position:0% hope ens or a similar system will come 00:11:37.190 --> 00:11:39.250 align:start position:0% hope ens or a similar system will come along<00:11:37.430> soon<00:11:37.490> and<00:11:38.120> you<00:11:38.510> will<00:11:38.660> have<00:11:38.810> symbolic 00:11:39.250 --> 00:11:39.260 align:start position:0% along soon and you will have symbolic 00:11:39.260 --> 00:11:42.220 align:start position:0% along soon and you will have symbolic names<00:11:39.650> for<00:11:40.250> your<00:11:40.280> repos<00:11:40.790> such<00:11:41.600> as<00:11:41.810> solidity 00:11:42.220 --> 00:11:42.230 align:start position:0% names for your repos such as solidity 00:11:42.230 --> 00:11:45.180 align:start position:0% names for your repos such as solidity that<00:11:42.500> etherium<00:11:43.070> that<00:11:43.250> mango<00:11:43.640> the<00:11:43.670> thief<00:11:44.030> I 00:11:45.180 --> 00:11:45.190 align:start position:0% that etherium that mango the thief I 00:11:45.190 --> 00:11:47.380 align:start position:0% that etherium that mango the thief I still<00:11:46.190> need<00:11:46.340> to<00:11:46.370> convince<00:11:46.610> the<00:11:46.730> guys<00:11:46.910> to 00:11:47.380 --> 00:11:47.390 align:start position:0% still need to convince the guys to 00:11:47.390 --> 00:11:50.260 align:start position:0% still need to convince the guys to register<00:11:47.900> five<00:11:48.200> letter<00:11:48.860> names<00:11:49.400> in<00:11:49.640> eve<00:11:49.790> but 00:11:50.260 --> 00:11:50.270 align:start position:0% register five letter names in eve but 00:11:50.270 --> 00:11:53.980 align:start position:0% register five letter names in eve but hopefully<00:11:50.960> that<00:11:51.110> works<00:11:52.450> so<00:11:53.450> where<00:11:53.660> are<00:11:53.810> we 00:11:53.980 --> 00:11:53.990 align:start position:0% hopefully that works so where are we 00:11:53.990 --> 00:11:56.590 align:start position:0% hopefully that works so where are we with<00:11:54.140> mango<00:11:54.560> is<00:11:55.310> it<00:11:55.430> a<00:11:55.460> replacement<00:11:56.030> yet<00:11:56.180> of 00:11:56.590 --> 00:11:56.600 align:start position:0% with mango is it a replacement yet of 00:11:56.600 --> 00:12:00.190 align:start position:0% with mango is it a replacement yet of course<00:11:57.020> well<00:11:57.980> not<00:11:58.220> entirely<00:11:58.610> but<00:11:59.240> there's 00:12:00.190 --> 00:12:00.200 align:start position:0% course well not entirely but there's 00:12:00.200 --> 00:12:01.990 align:start position:0% course well not entirely but there's certain<00:12:00.560> use<00:12:00.710> cases<00:12:00.830> it's<00:12:01.460> already<00:12:01.700> capable 00:12:01.990 --> 00:12:02.000 align:start position:0% certain use cases it's already capable 00:12:02.000 --> 00:12:05.350 align:start position:0% certain use cases it's already capable off<00:12:02.360> I<00:12:03.040> would<00:12:04.040> suggest<00:12:04.250> that<00:12:04.640> you<00:12:04.880> use<00:12:04.910> your 00:12:05.350 --> 00:12:05.360 align:start position:0% off I would suggest that you use your 00:12:05.360 --> 00:12:07.360 align:start position:0% off I would suggest that you use your tools<00:12:05.900> you're<00:12:06.200> familiar<00:12:06.440> with<00:12:06.710> today<00:12:06.950> and 00:12:07.360 --> 00:12:07.370 align:start position:0% tools you're familiar with today and 00:12:07.370 --> 00:12:09.300 align:start position:0% tools you're familiar with today and your<00:12:07.850> services<00:12:08.330> you're<00:12:08.480> familiar<00:12:08.660> with<00:12:08.870> today 00:12:09.300 --> 00:12:09.310 align:start position:0% your services you're familiar with today 00:12:09.310 --> 00:12:11.800 align:start position:0% your services you're familiar with today but<00:12:10.310> once<00:12:10.580> you<00:12:10.820> have<00:12:11.060> a<00:12:11.090> version<00:12:11.540> of<00:12:11.630> your 00:12:11.800 --> 00:12:11.810 align:start position:0% but once you have a version of your 00:12:11.810 --> 00:12:14.470 align:start position:0% but once you have a version of your software<00:12:12.290> or<00:12:12.500> release<00:12:13.280> you<00:12:13.880> want<00:12:14.030> to<00:12:14.090> persist 00:12:14.470 --> 00:12:14.480 align:start position:0% software or release you want to persist 00:12:14.480 --> 00:12:17.680 align:start position:0% software or release you want to persist for<00:12:14.810> and<00:12:15.050> an<00:12:15.500> indefinite<00:12:16.160> length<00:12:16.310> of<00:12:16.550> time<00:12:16.820> you 00:12:17.680 --> 00:12:17.690 align:start position:0% for and an indefinite length of time you 00:12:17.690 --> 00:12:20.200 align:start position:0% for and an indefinite length of time you could<00:12:17.840> use<00:12:18.080> mango<00:12:18.590> and<00:12:18.800> you<00:12:18.980> could<00:12:19.130> push<00:12:19.430> that 00:12:20.200 --> 00:12:20.210 align:start position:0% could use mango and you could push that 00:12:20.210 --> 00:12:23.110 align:start position:0% could use mango and you could push that certain<00:12:21.050> chainset<00:12:21.740> the<00:12:22.190> certain<00:12:22.550> version<00:12:22.940> of 00:12:23.110 --> 00:12:23.120 align:start position:0% certain chainset the certain version of 00:12:23.120 --> 00:12:26.380 align:start position:0% certain chainset the certain version of your<00:12:23.540> software<00:12:24.020> to<00:12:24.140> mango<00:12:25.060> but<00:12:26.060> this<00:12:26.180> should 00:12:26.380 --> 00:12:26.390 align:start position:0% your software to mango but this should 00:12:26.390 --> 00:12:28.540 align:start position:0% your software to mango but this should change<00:12:26.690> in<00:12:26.900> the<00:12:26.990> future<00:12:27.200> so<00:12:27.980> we<00:12:28.130> have<00:12:28.370> to 00:12:28.540 --> 00:12:28.550 align:start position:0% change in the future so we have to 00:12:28.550 --> 00:12:30.370 align:start position:0% change in the future so we have to improve<00:12:28.730> mango<00:12:29.390> and<00:12:29.570> we<00:12:29.960> have<00:12:30.140> to<00:12:30.260> improve 00:12:30.370 --> 00:12:30.380 align:start position:0% improve mango and we have to improve 00:12:30.380 --> 00:12:33.310 align:start position:0% improve mango and we have to improve tools<00:12:30.950> to<00:12:31.610> provide<00:12:31.910> full<00:12:32.300> replacement<00:12:32.540> full 00:12:33.310 --> 00:12:33.320 align:start position:0% tools to provide full replacement full 00:12:33.320 --> 00:12:38.440 align:start position:0% tools to provide full replacement full decent<00:12:33.680> replacement<00:12:34.240> to<00:12:36.250> social<00:12:37.250> coding<00:12:37.670> so 00:12:38.440 --> 00:12:38.450 align:start position:0% decent replacement to social coding so 00:12:38.450 --> 00:12:39.930 align:start position:0% decent replacement to social coding so the<00:12:38.570> first<00:12:38.750> thing<00:12:38.840> we<00:12:39.050> have<00:12:39.080> to<00:12:39.200> do<00:12:39.410> here<00:12:39.470> is 00:12:39.930 --> 00:12:39.940 align:start position:0% the first thing we have to do here is 00:12:39.940 --> 00:12:42.880 align:start position:0% the first thing we have to do here is which<00:12:40.940> is<00:12:40.970> a<00:12:41.090> tiny<00:12:41.390> thing<00:12:41.540> you<00:12:42.380> know<00:12:42.500> with<00:12:42.680> each 00:12:42.880 --> 00:12:42.890 align:start position:0% which is a tiny thing you know with each 00:12:42.890 --> 00:12:45.400 align:start position:0% which is a tiny thing you know with each releasing<00:12:43.520> it<00:12:43.700> you<00:12:43.880> can<00:12:44.030> only<00:12:44.180> set<00:12:44.840> a<00:12:45.020> version 00:12:45.400 --> 00:12:45.410 align:start position:0% releasing it you can only set a version 00:12:45.410 --> 00:12:48.040 align:start position:0% releasing it you can only set a version number<00:12:45.730> we<00:12:46.730> would<00:12:46.910> be<00:12:47.060> rakul<00:12:47.480> to<00:12:47.600> also<00:12:47.810> set 00:12:48.040 --> 00:12:48.050 align:start position:0% number we would be rakul to also set 00:12:48.050 --> 00:12:50.980 align:start position:0% number we would be rakul to also set release<00:12:48.500> notes<00:12:48.800> what<00:12:49.610> that<00:12:50.060> version<00:12:50.270> includes 00:12:50.980 --> 00:12:50.990 align:start position:0% release notes what that version includes 00:12:50.990 --> 00:12:53.410 align:start position:0% release notes what that version includes so<00:12:51.890> that's<00:12:52.070> actually<00:12:52.220> possible<00:12:52.550> with<00:12:52.970> it<00:12:53.210> add 00:12:53.410 --> 00:12:53.420 align:start position:0% so that's actually possible with it add 00:12:53.420 --> 00:12:56.530 align:start position:0% so that's actually possible with it add this<00:12:54.020> feature<00:12:54.290> called<00:12:54.650> get<00:12:54.890> note<00:12:55.240> which<00:12:56.240> you 00:12:56.530 --> 00:12:56.540 align:start position:0% this feature called get note which you 00:12:56.540 --> 00:12:59.550 align:start position:0% this feature called get note which you can<00:12:56.690> use<00:12:56.720> to<00:12:56.900> put<00:12:57.260> notes<00:12:58.100> next<00:12:58.520> to<00:12:58.670> any<00:12:58.940> object 00:12:59.550 --> 00:12:59.560 align:start position:0% can use to put notes next to any object 00:12:59.560 --> 00:13:02.080 align:start position:0% can use to put notes next to any object it's<00:13:00.560> kind<00:13:00.770> of<00:13:00.830> hard<00:13:00.980> to<00:13:01.040> use<00:13:01.280> so<00:13:01.490> this<00:13:01.700> has<00:13:01.940> to 00:13:02.080 --> 00:13:02.090 align:start position:0% it's kind of hard to use so this has to 00:13:02.090 --> 00:13:06.340 align:start position:0% it's kind of hard to use so this has to be<00:13:02.210> improved<00:13:02.950> the<00:13:03.950> second<00:13:04.310> big<00:13:04.400> thing<00:13:04.640> is<00:13:05.350> to 00:13:06.340 --> 00:13:06.350 align:start position:0% be improved the second big thing is to 00:13:06.350 --> 00:13:08.940 align:start position:0% be improved the second big thing is to have<00:13:06.530> issue<00:13:06.800> tracking<00:13:07.220> we<00:13:07.700> didn't<00:13:07.940> get<00:13:08.090> and 00:13:08.940 --> 00:13:08.950 align:start position:0% have issue tracking we didn't get and 00:13:08.950 --> 00:13:11.230 align:start position:0% have issue tracking we didn't get and google<00:13:09.950> has<00:13:10.070> a<00:13:10.100> project<00:13:10.520> to<00:13:10.610> do<00:13:10.730> that<00:13:10.880> with<00:13:11.060> get 00:13:11.230 --> 00:13:11.240 align:start position:0% google has a project to do that with get 00:13:11.240 --> 00:13:13.330 align:start position:0% google has a project to do that with get notes<00:13:11.450> but<00:13:12.020> it's<00:13:12.170> a<00:13:12.230> bit<00:13:12.350> clumsy<00:13:12.590> so<00:13:12.950> there's 00:13:13.330 --> 00:13:13.340 align:start position:0% notes but it's a bit clumsy so there's 00:13:13.340 --> 00:13:16.260 align:start position:0% notes but it's a bit clumsy so there's still<00:13:13.430> room<00:13:13.760> of<00:13:14.060> room<00:13:14.840> for<00:13:15.020> improvement<00:13:15.050> here 00:13:16.260 --> 00:13:16.270 align:start position:0% still room of room for improvement here 00:13:16.270 --> 00:13:19.840 align:start position:0% still room of room for improvement here the<00:13:17.270> really<00:13:17.780> big<00:13:17.900> work<00:13:18.170> here<00:13:18.560> is<00:13:18.740> a<00:13:18.850> supporting 00:13:19.840 --> 00:13:19.850 align:start position:0% the really big work here is a supporting 00:13:19.850 --> 00:13:22.810 align:start position:0% the really big work here is a supporting pull<00:13:20.030> request<00:13:20.360> or<00:13:20.630> merge<00:13:20.870> request<00:13:21.260> and<00:13:21.820> as 00:13:22.810 --> 00:13:22.820 align:start position:0% pull request or merge request and as 00:13:22.820 --> 00:13:25.420 align:start position:0% pull request or merge request and as well<00:13:23.300> as<00:13:23.330> like<00:13:23.540> github<00:13:23.690> start<00:13:24.200> forking<00:13:24.650> so<00:13:25.340> if 00:13:25.420 --> 00:13:25.430 align:start position:0% well as like github start forking so if 00:13:25.430 --> 00:13:27.190 align:start position:0% well as like github start forking so if anyone<00:13:25.910> has<00:13:25.940> good<00:13:26.270> ideas<00:13:26.390> had<00:13:26.840> to<00:13:26.990> do<00:13:27.080> it 00:13:27.190 --> 00:13:27.200 align:start position:0% anyone has good ideas had to do it 00:13:27.200 --> 00:13:29.740 align:start position:0% anyone has good ideas had to do it please<00:13:27.830> talk<00:13:28.010> to<00:13:28.190> me<00:13:28.220> or<00:13:28.760> anyone<00:13:29.060> involved<00:13:29.540> is 00:13:29.740 --> 00:13:29.750 align:start position:0% please talk to me or anyone involved is 00:13:29.750 --> 00:13:31.410 align:start position:0% please talk to me or anyone involved is improving<00:13:30.230> yet 00:13:31.410 --> 00:13:31.420 align:start position:0% improving yet 00:13:31.420 --> 00:13:34.010 align:start position:0% improving yet and<00:13:31.540> of<00:13:31.780> course<00:13:31.840> we<00:13:32.560> need<00:13:32.710> user-friendly 00:13:34.010 --> 00:13:34.020 align:start position:0% and of course we need user-friendly 00:13:34.020 --> 00:13:37.740 align:start position:0% and of course we need user-friendly front<00:13:35.020> end<00:13:35.230> is<00:13:35.850> yeah<00:13:36.850> people<00:13:37.210> some<00:13:37.450> people<00:13:37.480> are 00:13:37.740 --> 00:13:37.750 align:start position:0% front end is yeah people some people are 00:13:37.750 --> 00:13:40.260 align:start position:0% front end is yeah people some people are happy<00:13:37.990> to<00:13:38.110> use<00:13:38.260> the<00:13:38.500> comment<00:13:39.220> line<00:13:39.370> but<00:13:39.940> others 00:13:40.260 --> 00:13:40.270 align:start position:0% happy to use the comment line but others 00:13:40.270 --> 00:13:41.970 align:start position:0% happy to use the comment line but others would<00:13:40.510> be<00:13:40.690> much<00:13:40.900> more<00:13:40.930> happy<00:13:41.350> to<00:13:41.500> have<00:13:41.680> a<00:13:41.710> nice 00:13:41.970 --> 00:13:41.980 align:start position:0% would be much more happy to have a nice 00:13:41.980 --> 00:13:45.540 align:start position:0% would be much more happy to have a nice web<00:13:42.250> prompting<00:13:42.640> to<00:13:42.790> create<00:13:43.290> manage<00:13:44.290> and<00:13:44.550> view 00:13:45.540 --> 00:13:45.550 align:start position:0% web prompting to create manage and view 00:13:45.550 --> 00:13:49.350 align:start position:0% web prompting to create manage and view and<00:13:45.910> interact<00:13:46.060> with<00:13:46.480> all<00:13:46.600> these<00:13:46.750> repos<00:13:48.360> one 00:13:49.350 --> 00:13:49.360 align:start position:0% and interact with all these repos one 00:13:49.360 --> 00:13:51.000 align:start position:0% and interact with all these repos one important<00:13:49.720> aspect<00:13:49.840> there<00:13:50.200> with<00:13:50.410> improving 00:13:51.000 --> 00:13:51.010 align:start position:0% important aspect there with improving 00:13:51.010 --> 00:13:53.280 align:start position:0% important aspect there with improving the<00:13:51.970> issue<00:13:52.180> tracking<00:13:52.600> and<00:13:52.960> the<00:13:53.050> pull<00:13:53.200> request 00:13:53.280 --> 00:13:53.290 align:start position:0% the issue tracking and the pull request 00:13:53.290 --> 00:13:56.220 align:start position:0% the issue tracking and the pull request would<00:13:53.740> get<00:13:53.980> this<00:13:54.730> wouldn't<00:13:55.120> be<00:13:55.300> only<00:13:55.690> for 00:13:56.220 --> 00:13:56.230 align:start position:0% would get this wouldn't be only for 00:13:56.230 --> 00:13:58.140 align:start position:0% would get this wouldn't be only for mango<00:13:56.620> if<00:13:56.830> you<00:13:57.460> have<00:13:57.550> all<00:13:57.670> these<00:13:57.850> things 00:13:58.140 --> 00:13:58.150 align:start position:0% mango if you have all these things 00:13:58.150 --> 00:14:00.510 align:start position:0% mango if you have all these things waiting<00:13:58.600> it<00:13:58.750> itself<00:13:59.140> no<00:13:59.950> matter<00:13:59.980> where<00:14:00.490> you 00:14:00.510 --> 00:14:00.520 align:start position:0% waiting it itself no matter where you 00:14:00.520 --> 00:14:02.820 align:start position:0% waiting it itself no matter where you take<00:14:00.850> your<00:14:00.910> repository<00:14:01.750> or<00:14:01.960> your<00:14:02.560> data 00:14:02.820 --> 00:14:02.830 align:start position:0% take your repository or your data 00:14:02.830 --> 00:14:04.470 align:start position:0% take your repository or your data including<00:14:03.400> your<00:14:03.550> issues<00:14:03.970> and<00:14:04.210> your<00:14:04.330> pull 00:14:04.470 --> 00:14:04.480 align:start position:0% including your issues and your pull 00:14:04.480 --> 00:14:07.950 align:start position:0% including your issues and your pull request<00:14:04.620> will<00:14:05.620> stay<00:14:05.830> with<00:14:06.010> you<00:14:06.250> and<00:14:06.930> I<00:14:07.930> hope 00:14:07.950 --> 00:14:07.960 align:start position:0% request will stay with you and I hope 00:14:07.960 --> 00:14:10.710 align:start position:0% request will stay with you and I hope actually<00:14:08.650> github<00:14:09.070> and<00:14:09.250> get<00:14:09.850> lab<00:14:10.120> and<00:14:10.360> other 00:14:10.710 --> 00:14:10.720 align:start position:0% actually github and get lab and other 00:14:10.720 --> 00:14:13.050 align:start position:0% actually github and get lab and other bigger<00:14:11.020> companies<00:14:11.530> using<00:14:11.800> it<00:14:12.100> would<00:14:12.790> be<00:14:12.940> able 00:14:13.050 --> 00:14:13.060 align:start position:0% bigger companies using it would be able 00:14:13.060 --> 00:14:15.480 align:start position:0% bigger companies using it would be able to<00:14:13.300> support<00:14:13.690> some<00:14:13.930> of<00:14:14.050> these<00:14:14.170> features<00:14:14.740> so<00:14:15.400> you 00:14:15.480 --> 00:14:15.490 align:start position:0% to support some of these features so you 00:14:15.490 --> 00:14:17.640 align:start position:0% to support some of these features so you could<00:14:15.610> freely<00:14:15.880> move<00:14:16.180> between<00:14:16.570> mango<00:14:17.110> and<00:14:17.350> the 00:14:17.640 --> 00:14:17.650 align:start position:0% could freely move between mango and the 00:14:17.650 --> 00:14:20.760 align:start position:0% could freely move between mango and the decentralized<00:14:18.240> the<00:14:19.240> website<00:14:19.660> or<00:14:20.320> additional 00:14:20.760 --> 00:14:20.770 align:start position:0% decentralized the website or additional 00:14:20.770 --> 00:14:23.340 align:start position:0% decentralized the website or additional eyes<00:14:20.920> up<00:14:21.420> and<00:14:22.420> between<00:14:22.660> these<00:14:22.870> services 00:14:23.340 --> 00:14:23.350 align:start position:0% eyes up and between these services 00:14:23.350 --> 00:14:27.180 align:start position:0% eyes up and between these services without<00:14:23.860> any<00:14:24.190> hassle<00:14:25.590> well<00:14:26.590> thank<00:14:27.010> you<00:14:27.130> for 00:14:27.180 --> 00:14:27.190 align:start position:0% without any hassle well thank you for 00:14:27.190 --> 00:14:28.800 align:start position:0% without any hassle well thank you for listening<00:14:27.400> I<00:14:27.850> think<00:14:28.360> now<00:14:28.450> it's<00:14:28.570> the<00:14:28.630> time<00:14:28.750> to 00:14:28.800 --> 00:14:28.810 align:start position:0% listening I think now it's the time to 00:14:28.810 --> 00:14:30.570 align:start position:0% listening I think now it's the time to check<00:14:29.050> out<00:14:29.200> mango<00:14:29.560> and<00:14:29.770> actually<00:14:30.310> no<00:14:30.430> one 00:14:30.570 --> 00:14:30.580 align:start position:0% check out mango and actually no one 00:14:30.580 --> 00:14:32.640 align:start position:0% check out mango and actually no one believes<00:14:30.820> this<00:14:31.000> but<00:14:31.210> it<00:14:31.300> works<00:14:31.570> already<00:14:31.960> so 00:14:32.640 --> 00:14:32.650 align:start position:0% believes this but it works already so 00:14:32.650 --> 00:14:36.420 align:start position:0% believes this but it works already so you<00:14:32.710> could<00:14:33.070> try<00:14:33.220> it<00:14:33.280> out<00:14:33.460> and<00:14:34.300> thank<00:14:34.570> you<00:14:35.430> thank 00:14:36.420 --> 00:14:36.430 align:start position:0% you could try it out and thank you thank 00:14:36.430 --> 00:14:40.170 align:start position:0% you could try it out and thank you thank you<00:14:36.490> Alex 00:14:40.170 --> 00:14:40.180 align:start position:0% 00:14:40.180 --> 00:14:42.240 align:start position:0% you