WEBVTT Kind: captions Language: en 00:00:04.540 --> 00:00:09.750 align:start position:0% hi<00:00:05.140> everyone<00:00:05.430> I'm<00:00:07.050> Oscar<00:00:08.400> welcome<00:00:09.400> political 00:00:09.750 --> 00:00:09.760 align:start position:0% hi everyone I'm Oscar welcome political 00:00:09.760 --> 00:00:12.390 align:start position:0% hi everyone I'm Oscar welcome political research<00:00:09.969> at<00:00:10.150> status 00:00:12.390 --> 00:00:12.400 align:start position:0% research at status 00:00:12.400 --> 00:00:14.459 align:start position:0% research at status I'm<00:00:12.789> Dina<00:00:13.180> also<00:00:13.480> work<00:00:13.600> on<00:00:13.690> protocol<00:00:14.110> research 00:00:14.459 --> 00:00:14.469 align:start position:0% I'm Dina also work on protocol research 00:00:14.469 --> 00:00:16.710 align:start position:0% I'm Dina also work on protocol research at<00:00:14.590> status<00:00:15.090> today<00:00:16.090> we're<00:00:16.330> gonna<00:00:16.420> talk<00:00:16.539> to<00:00:16.660> you 00:00:16.710 --> 00:00:16.720 align:start position:0% at status today we're gonna talk to you 00:00:16.720 --> 00:00:21.749 align:start position:0% at status today we're gonna talk to you about<00:00:16.780> vac<00:00:17.199> PDP<00:00:19.410> so<00:00:20.410> vac<00:00:21.220> is<00:00:21.369> family<00:00:21.670> of 00:00:21.749 --> 00:00:21.759 align:start position:0% about vac PDP so vac is family of 00:00:21.759 --> 00:00:23.999 align:start position:0% about vac PDP so vac is family of protocols<00:00:21.970> for<00:00:22.480> developing<00:00:22.900> secure<00:00:23.380> private 00:00:23.999 --> 00:00:24.009 align:start position:0% protocols for developing secure private 00:00:24.009 --> 00:00:27.259 align:start position:0% protocols for developing secure private and<00:00:24.279> sensitive<00:00:24.609> resistant<00:00:25.269> p2p<00:00:25.570> solutions 00:00:27.259 --> 00:00:27.269 align:start position:0% and sensitive resistant p2p solutions 00:00:27.269 --> 00:00:29.460 align:start position:0% and sensitive resistant p2p solutions what<00:00:28.269> that<00:00:28.390> means<00:00:28.570> in<00:00:28.720> practice<00:00:29.140> for<00:00:29.259> us<00:00:29.349> the 00:00:29.460 --> 00:00:29.470 align:start position:0% what that means in practice for us the 00:00:29.470 --> 00:00:31.650 align:start position:0% what that means in practice for us the status<00:00:29.710> right<00:00:30.160> now<00:00:30.369> is<00:00:30.669> essentially<00:00:31.329> secure 00:00:31.650 --> 00:00:31.660 align:start position:0% status right now is essentially secure 00:00:31.660 --> 00:00:35.400 align:start position:0% status right now is essentially secure messaging<00:00:33.750> when<00:00:34.750> people<00:00:34.990> talk<00:00:35.079> about<00:00:35.110> secure 00:00:35.400 --> 00:00:35.410 align:start position:0% messaging when people talk about secure 00:00:35.410 --> 00:00:37.650 align:start position:0% messaging when people talk about secure messaging<00:00:35.800> usually<00:00:36.280> focus<00:00:37.120> on<00:00:37.149> sort<00:00:37.300> of<00:00:37.390> enter 00:00:37.650 --> 00:00:37.660 align:start position:0% messaging usually focus on sort of enter 00:00:37.660 --> 00:00:40.380 align:start position:0% messaging usually focus on sort of enter an<00:00:37.719> encryption<00:00:38.050> forward<00:00:38.860> secrecy<00:00:39.390> avoiding 00:00:40.380 --> 00:00:40.390 align:start position:0% an encryption forward secrecy avoiding 00:00:40.390 --> 00:00:44.010 align:start position:0% an encryption forward secrecy avoiding Manimal<00:00:41.020> attacks<00:00:41.320> and<00:00:41.559> so<00:00:41.649> on<00:00:42.750> but<00:00:43.750> as<00:00:43.870> other 00:00:44.010 --> 00:00:44.020 align:start position:0% Manimal attacks and so on but as other 00:00:44.020 --> 00:00:46.080 align:start position:0% Manimal attacks and so on but as other security<00:00:44.440> properties<00:00:44.829> such<00:00:45.219> as<00:00:45.250> privacy<00:00:45.910> and 00:00:46.080 --> 00:00:46.090 align:start position:0% security properties such as privacy and 00:00:46.090 --> 00:00:48.599 align:start position:0% security properties such as privacy and protecting<00:00:46.750> sort<00:00:46.960> of<00:00:47.050> metadata<00:00:47.920> as<00:00:48.219> well<00:00:48.489> as 00:00:48.599 --> 00:00:48.609 align:start position:0% protecting sort of metadata as well as 00:00:48.609 --> 00:00:51.660 align:start position:0% protecting sort of metadata as well as sensitive<00:00:48.940> persistence<00:00:49.420> and<00:00:50.190> all<00:00:51.190> together 00:00:51.660 --> 00:00:51.670 align:start position:0% sensitive persistence and all together 00:00:51.670 --> 00:00:56.400 align:start position:0% sensitive persistence and all together these<00:00:52.390> sort<00:00:52.660> of<00:00:52.719> properties<00:00:55.109> help<00:00:56.109> you 00:00:56.400 --> 00:00:56.410 align:start position:0% these sort of properties help you 00:00:56.410 --> 00:00:58.139 align:start position:0% these sort of properties help you protect<00:00:57.039> against<00:00:57.489> various<00:00:57.730> types<00:00:57.879> of<00:00:57.969> threat 00:00:58.139 --> 00:00:58.149 align:start position:0% protect against various types of threat 00:00:58.149 --> 00:00:59.310 align:start position:0% protect against various types of threat models<00:00:58.480> that<00:00:58.750> we<00:00:58.809> see<00:00:58.929> around<00:00:58.989> the<00:00:59.109> world 00:00:59.310 --> 00:00:59.320 align:start position:0% models that we see around the world 00:00:59.320 --> 00:01:01.349 align:start position:0% models that we see around the world today<00:00:59.440> as<00:01:00.129> well<00:01:00.340> as<00:01:00.429> for<00:01:00.609> certain<00:01:00.940> high-risk 00:01:01.349 --> 00:01:01.359 align:start position:0% today as well as for certain high-risk 00:01:01.359 --> 00:01:06.660 align:start position:0% today as well as for certain high-risk individuals<00:01:04.800> so<00:01:05.800> one<00:01:05.920> way<00:01:06.040> of<00:01:06.130> looking<00:01:06.490> at<00:01:06.580> the 00:01:06.660 --> 00:01:06.670 align:start position:0% individuals so one way of looking at the 00:01:06.670 --> 00:01:09.660 align:start position:0% individuals so one way of looking at the problem<00:01:07.030> of<00:01:07.150> sort<00:01:07.900> of<00:01:07.960> secure<00:01:08.410> messaging<00:01:08.770> is 00:01:09.660 --> 00:01:09.670 align:start position:0% problem of sort of secure messaging is 00:01:09.670 --> 00:01:13.200 align:start position:0% problem of sort of secure messaging is in<00:01:10.420> terms<00:01:10.600> of<00:01:10.750> a<00:01:10.870> messaging<00:01:11.770> stack<00:01:12.090> we're<00:01:13.090> sort 00:01:13.200 --> 00:01:13.210 align:start position:0% in terms of a messaging stack we're sort 00:01:13.210 --> 00:01:14.940 align:start position:0% in terms of a messaging stack we're sort of<00:01:13.240> each<00:01:13.480> layer<00:01:13.750> is<00:01:14.020> roughly<00:01:14.320> orthogonal<00:01:14.860> to 00:01:14.940 --> 00:01:14.950 align:start position:0% of each layer is roughly orthogonal to 00:01:14.950 --> 00:01:17.100 align:start position:0% of each layer is roughly orthogonal to the<00:01:15.010> other<00:01:15.100> layers<00:01:15.480> so<00:01:16.480> starting<00:01:16.780> at<00:01:16.870> the<00:01:16.900> very 00:01:17.100 --> 00:01:17.110 align:start position:0% the other layers so starting at the very 00:01:17.110 --> 00:01:19.200 align:start position:0% the other layers so starting at the very top<00:01:17.290> you<00:01:17.890> have<00:01:17.980> sort<00:01:18.130> of<00:01:18.190> end-user<00:01:18.460> semantics 00:01:19.200 --> 00:01:19.210 align:start position:0% top you have sort of end-user semantics 00:01:19.210 --> 00:01:22.740 align:start position:0% top you have sort of end-user semantics let's<00:01:19.600> you're<00:01:20.190> it's<00:01:21.190> some<00:01:21.640> private<00:01:22.000> sort<00:01:22.690> of 00:01:22.740 --> 00:01:22.750 align:start position:0% let's you're it's some private sort of 00:01:22.750 --> 00:01:24.300 align:start position:0% let's you're it's some private sort of encrypted<00:01:23.110> group<00:01:23.260> chat<00:01:23.470> or<00:01:23.740> maybe<00:01:24.010> some 00:01:24.300 --> 00:01:24.310 align:start position:0% encrypted group chat or maybe some 00:01:24.310 --> 00:01:26.670 align:start position:0% encrypted group chat or maybe some public<00:01:25.140> forum<00:01:26.140> with<00:01:26.290> some<00:01:26.410> moderation 00:01:26.670 --> 00:01:26.680 align:start position:0% public forum with some moderation 00:01:26.680 --> 00:01:28.920 align:start position:0% public forum with some moderation mechanism<00:01:27.220> then<00:01:28.120> below<00:01:28.330> that<00:01:28.360> you<00:01:28.570> have<00:01:28.780> sort 00:01:28.920 --> 00:01:28.930 align:start position:0% mechanism then below that you have sort 00:01:28.930 --> 00:01:30.990 align:start position:0% mechanism then below that you have sort of<00:01:29.020> data<00:01:29.470> consistency<00:01:29.980> data<00:01:30.280> Sinclair<00:01:30.670> which 00:01:30.990 --> 00:01:31.000 align:start position:0% of data consistency data Sinclair which 00:01:31.000 --> 00:01:32.760 align:start position:0% of data consistency data Sinclair which is<00:01:31.120> sourced<00:01:31.420> at<00:01:31.570> sort<00:01:31.810> of<00:01:31.840> all<00:01:32.140> the<00:01:32.350> nodes<00:01:32.500> have 00:01:32.760 --> 00:01:32.770 align:start position:0% is sourced at sort of all the nodes have 00:01:32.770 --> 00:01:35.700 align:start position:0% is sourced at sort of all the nodes have sort<00:01:33.520> of<00:01:33.550> right<00:01:34.240> idea<00:01:34.570> for<00:01:34.780> the<00:01:34.840> state<00:01:35.050> of<00:01:35.260> some 00:01:35.700 --> 00:01:35.710 align:start position:0% sort of right idea for the state of some 00:01:35.710 --> 00:01:39.240 align:start position:0% sort of right idea for the state of some context<00:01:36.220> or<00:01:36.340> conversation<00:01:36.820> is<00:01:37.770> and<00:01:38.770> below 00:01:39.240 --> 00:01:39.250 align:start position:0% context or conversation is and below 00:01:39.250 --> 00:01:40.410 align:start position:0% context or conversation is and below that<00:01:39.280> you<00:01:39.460> have<00:01:39.670> sort<00:01:39.940> of<00:01:40.000> your<00:01:40.180> secure 00:01:40.410 --> 00:01:40.420 align:start position:0% that you have sort of your secure 00:01:40.420 --> 00:01:43.050 align:start position:0% that you have sort of your secure transport<00:01:41.100> which<00:01:42.100> gives<00:01:42.580> you<00:01:42.670> probably<00:01:42.910> is<00:01:43.000> a 00:01:43.050 --> 00:01:43.060 align:start position:0% transport which gives you probably is a 00:01:43.060 --> 00:01:44.880 align:start position:0% transport which gives you probably is a confidentiality<00:01:43.480> forward<00:01:44.260> secrecy<00:01:44.440> and<00:01:44.770> so 00:01:44.880 --> 00:01:44.890 align:start position:0% confidentiality forward secrecy and so 00:01:44.890 --> 00:01:47.220 align:start position:0% confidentiality forward secrecy and so on<00:01:45.180> and<00:01:46.180> right<00:01:46.390> now<00:01:46.510> we<00:01:46.570> use<00:01:46.630> double<00:01:46.900> register 00:01:47.220 --> 00:01:47.230 align:start position:0% on and right now we use double register 00:01:47.230 --> 00:01:49.140 align:start position:0% on and right now we use double register for<00:01:47.320> that<00:01:47.350> status<00:01:47.680> but<00:01:48.160> it's<00:01:48.280> others<00:01:48.490> like<00:01:48.730> mrs 00:01:49.140 --> 00:01:49.150 align:start position:0% for that status but it's others like mrs 00:01:49.150 --> 00:01:51.750 align:start position:0% for that status but it's others like mrs lacy<00:01:49.270> security<00:01:50.220> below<00:01:51.220> that<00:01:51.370> you<00:01:51.490> sort<00:01:51.730> of 00:01:51.750 --> 00:01:51.760 align:start position:0% lacy security below that you sort of 00:01:51.760 --> 00:01:53.370 align:start position:0% lacy security below that you sort of have<00:01:51.910> the<00:01:52.090> metadata<00:01:52.540> protection<00:01:52.960> layer<00:01:53.080> where 00:01:53.370 --> 00:01:53.380 align:start position:0% have the metadata protection layer where 00:01:53.380 --> 00:01:55.800 align:start position:0% have the metadata protection layer where right<00:01:53.500> now<00:01:53.650> we<00:01:53.710> use<00:01:53.890> whispered<00:01:54.820> sellers<00:01:55.090> but 00:01:55.800 --> 00:01:55.810 align:start position:0% right now we use whispered sellers but 00:01:55.810 --> 00:01:58.530 align:start position:0% right now we use whispered sellers but so<00:01:55.960> solder<00:01:56.230> so<00:01:56.410> just<00:01:56.620> like<00:01:56.740> pcs<00:01:57.520> and<00:01:57.790> tor<00:01:58.270> mix 00:01:58.530 --> 00:01:58.540 align:start position:0% so solder so just like pcs and tor mix 00:01:58.540 --> 00:02:01.710 align:start position:0% so solder so just like pcs and tor mix nets<00:01:58.780> that<00:01:59.040> kind<00:02:00.040> of<00:02:00.130> different<00:02:00.970> but<00:02:01.270> but<00:02:01.540> they 00:02:01.710 --> 00:02:01.720 align:start position:0% nets that kind of different but but they 00:02:01.720 --> 00:02:04.680 align:start position:0% nets that kind of different but but they they<00:02:02.140> share<00:02:03.070> some<00:02:03.370> common<00:02:03.400> design<00:02:04.240> goals<00:02:04.450> and 00:02:04.680 --> 00:02:04.690 align:start position:0% they share some common design goals and 00:02:04.690 --> 00:02:05.820 align:start position:0% they share some common design goals and they<00:02:04.750> have<00:02:04.870> various<00:02:05.140> properties<00:02:05.530> against 00:02:05.820 --> 00:02:05.830 align:start position:0% they have various properties against 00:02:05.830 --> 00:02:08.520 align:start position:0% they have various properties against very<00:02:06.010> types<00:02:06.220> of<00:02:06.390> fret<00:02:07.390> walls<00:02:07.600> and<00:02:08.259> below<00:02:08.500> that 00:02:08.520 --> 00:02:08.530 align:start position:0% very types of fret walls and below that 00:02:08.530 --> 00:02:10.650 align:start position:0% very types of fret walls and below that you<00:02:08.739> have<00:02:08.770> sort<00:02:09.009> of<00:02:09.039> the<00:02:09.280> overlay<00:02:09.819> network 00:02:10.650 --> 00:02:10.660 align:start position:0% you have sort of the overlay network 00:02:10.660 --> 00:02:13.020 align:start position:0% you have sort of the overlay network overlay<00:02:11.110> routing<00:02:11.470> for<00:02:11.800> natural<00:02:12.459> and<00:02:12.909> so 00:02:13.020 --> 00:02:13.030 align:start position:0% overlay routing for natural and so 00:02:13.030 --> 00:02:14.910 align:start position:0% overlay routing for natural and so abstracting<00:02:13.540> awaited<00:02:13.810> actual<00:02:14.140> transports 00:02:14.910 --> 00:02:14.920 align:start position:0% abstracting awaited actual transports 00:02:14.920 --> 00:02:17.910 align:start position:0% abstracting awaited actual transports like<00:02:15.040> TCP<00:02:15.430> UDP<00:02:15.549> and<00:02:15.909> so<00:02:16.030> on 00:02:17.910 --> 00:02:17.920 align:start position:0% like TCP UDP and so on 00:02:17.920 --> 00:02:20.010 align:start position:0% like TCP UDP and so on and<00:02:18.010> this<00:02:18.819> layer<00:02:19.090> sort<00:02:19.330> of<00:02:19.390> helps<00:02:19.630> a<00:02:19.720> lot<00:02:19.810> when 00:02:20.010 --> 00:02:20.020 align:start position:0% and this layer sort of helps a lot when 00:02:20.020 --> 00:02:21.630 align:start position:0% and this layer sort of helps a lot when it<00:02:20.110> comes<00:02:20.140> to<00:02:20.380> sense<00:02:20.650> of<00:02:20.770> resistance<00:02:21.010> because 00:02:21.630 --> 00:02:21.640 align:start position:0% it comes to sense of resistance because 00:02:21.640 --> 00:02:24.180 align:start position:0% it comes to sense of resistance because this<00:02:21.880> is<00:02:22.000> where<00:02:22.239> use<00:02:22.870> of<00:02:23.020> God<00:02:23.230> against<00:02:23.650> various 00:02:24.180 --> 00:02:24.190 align:start position:0% this is where use of God against various 00:02:24.190 --> 00:02:26.790 align:start position:0% this is where use of God against various types<00:02:24.370> of<00:02:24.489> traffic<00:02:24.670> filtering<00:02:25.209> and<00:02:25.390> so<00:02:25.780> on<00:02:25.900> and 00:02:26.790 --> 00:02:26.800 align:start position:0% types of traffic filtering and so on and 00:02:26.800 --> 00:02:28.830 align:start position:0% types of traffic filtering and so on and it's<00:02:26.950> a<00:02:27.010> kind<00:02:27.220> of<00:02:27.370> somewhat<00:02:28.300> the<00:02:28.390> focal<00:02:28.630> piece 00:02:28.830 --> 00:02:28.840 align:start position:0% it's a kind of somewhat the focal piece 00:02:28.840 --> 00:02:30.420 align:start position:0% it's a kind of somewhat the focal piece that<00:02:29.050> you<00:02:29.260> also<00:02:29.380> have<00:02:29.620> trust<00:02:29.980> establishment 00:02:30.420 --> 00:02:30.430 align:start position:0% that you also have trust establishment 00:02:30.430 --> 00:02:31.350 align:start position:0% that you also have trust establishment which<00:02:30.730> is<00:02:30.849> sort<00:02:31.030> of<00:02:31.090> how<00:02:31.180> you<00:02:31.239> establish 00:02:31.350 --> 00:02:31.360 align:start position:0% which is sort of how you establish 00:02:31.360 --> 00:02:33.570 align:start position:0% which is sort of how you establish end-to-end<00:02:31.959> trust<00:02:32.230> with<00:02:32.920> its<00:02:33.069> various<00:02:33.250> models 00:02:33.570 --> 00:02:33.580 align:start position:0% end-to-end trust with its various models 00:02:33.580 --> 00:02:36.540 align:start position:0% end-to-end trust with its various models like<00:02:33.700> trust<00:02:34.330> first<00:02:34.600> use<00:02:35.040> and<00:02:36.040> web<00:02:36.280> of<00:02:36.310> trust 00:02:36.540 --> 00:02:36.550 align:start position:0% like trust first use and web of trust 00:02:36.550 --> 00:02:41.699 align:start position:0% like trust first use and web of trust like<00:02:36.819> PGP<00:02:37.239> and<00:02:37.390> key<00:02:37.510> based<00:02:37.720> and<00:02:37.989> so<00:02:38.050> on<00:02:40.709> talking 00:02:41.699 --> 00:02:41.709 align:start position:0% like PGP and key based and so on talking 00:02:41.709 --> 00:02:43.110 align:start position:0% like PGP and key based and so on talking briefly<00:02:41.860> about<00:02:41.920> some<00:02:42.370> design<00:02:42.640> goals<00:02:42.850> we<00:02:43.000> have 00:02:43.110 --> 00:02:43.120 align:start position:0% briefly about some design goals we have 00:02:43.120 --> 00:02:44.370 align:start position:0% briefly about some design goals we have it<00:02:43.209> vac<00:02:43.390> so<00:02:43.660> we<00:02:43.780> were<00:02:43.930> trying<00:02:44.110> to<00:02:44.230> sort<00:02:44.350> of 00:02:44.370 --> 00:02:44.380 align:start position:0% it vac so we were trying to sort of 00:02:44.380 --> 00:02:46.290 align:start position:0% it vac so we were trying to sort of create<00:02:44.830> these<00:02:45.010> these<00:02:45.459> interfaces<00:02:45.970> at<00:02:46.180> each 00:02:46.290 --> 00:02:46.300 align:start position:0% create these these interfaces at each 00:02:46.300 --> 00:02:49.890 align:start position:0% create these these interfaces at each layer<00:02:46.860> where<00:02:47.860> that<00:02:48.849> allows<00:02:49.090> for<00:02:49.330> existing<00:02:49.840> in 00:02:49.890 --> 00:02:49.900 align:start position:0% layer where that allows for existing in 00:02:49.900 --> 00:02:52.520 align:start position:0% layer where that allows for existing in new<00:02:49.989> protocols<00:02:50.470> at<00:02:51.220> each<00:02:51.370> layer<00:02:51.550> of<00:02:51.610> the<00:02:51.670> stack 00:02:52.520 --> 00:02:52.530 align:start position:0% new protocols at each layer of the stack 00:02:52.530 --> 00:02:54.570 align:start position:0% new protocols at each layer of the stack we<00:02:53.530> don't<00:02:53.680> want<00:02:53.830> to<00:02:53.890> reinvent<00:02:54.069> the<00:02:54.280> wheel<00:02:54.310> here 00:02:54.570 --> 00:02:54.580 align:start position:0% we don't want to reinvent the wheel here 00:02:54.580 --> 00:02:55.979 align:start position:0% we don't want to reinvent the wheel here because<00:02:54.819> there's<00:02:54.940> a<00:02:54.970> lot<00:02:55.060> of<00:02:55.180> protocols<00:02:55.900> and 00:02:55.979 --> 00:02:55.989 align:start position:0% because there's a lot of protocols and 00:02:55.989 --> 00:02:57.180 align:start position:0% because there's a lot of protocols and components<00:02:56.470> that<00:02:56.560> are<00:02:56.739> being<00:02:56.860> developed<00:02:57.160> for 00:02:57.180 --> 00:02:57.190 align:start position:0% components that are being developed for 00:02:57.190 --> 00:02:59.190 align:start position:0% components that are being developed for people<00:02:57.549> at<00:02:58.000> this<00:02:58.120> conference<00:02:58.299> as<00:02:58.870> well<00:02:59.110> as 00:02:59.190 --> 00:02:59.200 align:start position:0% people at this conference as well as 00:02:59.200 --> 00:03:01.140 align:start position:0% people at this conference as well as sort<00:02:59.319> of<00:02:59.350> in<00:02:59.560> adjacent<00:03:00.040> ecosystems<00:03:00.910> and 00:03:01.140 --> 00:03:01.150 align:start position:0% sort of in adjacent ecosystems and 00:03:01.150 --> 00:03:03.150 align:start position:0% sort of in adjacent ecosystems and communities<00:03:01.290> that<00:03:02.290> also<00:03:02.560> solve<00:03:02.890> all<00:03:02.980> the 00:03:03.150 --> 00:03:03.160 align:start position:0% communities that also solve all the 00:03:03.160 --> 00:03:04.710 align:start position:0% communities that also solve all the problems<00:03:03.489> it's<00:03:03.880> more<00:03:04.060> about<00:03:04.239> sort<00:03:04.390> of<00:03:04.450> define 00:03:04.710 --> 00:03:04.720 align:start position:0% problems it's more about sort of define 00:03:04.720 --> 00:03:07.380 align:start position:0% problems it's more about sort of define these<00:03:04.810> interfaces<00:03:05.380> and<00:03:05.530> then<00:03:06.100> allowing<00:03:06.700> these 00:03:07.380 --> 00:03:07.390 align:start position:0% these interfaces and then allowing these 00:03:07.390 --> 00:03:09.350 align:start position:0% these interfaces and then allowing these very<00:03:07.630> several<00:03:07.870> protocols<00:03:08.140> to<00:03:08.709> work<00:03:08.830> together 00:03:09.350 --> 00:03:09.360 align:start position:0% very several protocols to work together 00:03:09.360 --> 00:03:11.729 align:start position:0% very several protocols to work together we<00:03:10.360> very<00:03:10.569> much<00:03:10.720> sort<00:03:10.870> of<00:03:10.930> take<00:03:11.200> the<00:03:11.410> design 00:03:11.729 --> 00:03:11.739 align:start position:0% we very much sort of take the design 00:03:11.739 --> 00:03:13.320 align:start position:0% we very much sort of take the design philosophy<00:03:12.130> from<00:03:12.280> products<00:03:12.730> like<00:03:12.819> lead<00:03:13.000> PTP 00:03:13.320 --> 00:03:13.330 align:start position:0% philosophy from products like lead PTP 00:03:13.330 --> 00:03:16.470 align:start position:0% philosophy from products like lead PTP and<00:03:13.510> substrate<00:03:13.930> in<00:03:14.280> instead<00:03:15.280> of<00:03:15.480> enabling 00:03:16.470 --> 00:03:16.480 align:start position:0% and substrate in instead of enabling 00:03:16.480 --> 00:03:18.479 align:start position:0% and substrate in instead of enabling that<00:03:16.630> and<00:03:16.989> having<00:03:17.230> kind<00:03:17.739> of<00:03:17.860> a<00:03:18.010> protocol 00:03:18.479 --> 00:03:18.489 align:start position:0% that and having kind of a protocol 00:03:18.489 --> 00:03:20.220 align:start position:0% that and having kind of a protocol selection<00:03:18.880> that<00:03:19.060> depends<00:03:19.390> on<00:03:19.569> your<00:03:20.019> specific 00:03:20.220 --> 00:03:20.230 align:start position:0% selection that depends on your specific 00:03:20.230 --> 00:03:22.140 align:start position:0% selection that depends on your specific design<00:03:20.709> goals<00:03:20.950> so<00:03:21.489> I'd<00:03:21.580> say<00:03:21.700> you're<00:03:21.819> extremely 00:03:22.140 --> 00:03:22.150 align:start position:0% design goals so I'd say you're extremely 00:03:22.150 --> 00:03:23.789 align:start position:0% design goals so I'd say you're extremely sort<00:03:22.359> of<00:03:22.420> privacy<00:03:22.930> conscious<00:03:23.109> then<00:03:23.560> you<00:03:23.650> might 00:03:23.789 --> 00:03:23.799 align:start position:0% sort of privacy conscious then you might 00:03:23.799 --> 00:03:26.160 align:start position:0% sort of privacy conscious then you might want<00:03:23.980> to<00:03:24.040> use<00:03:24.130> the<00:03:24.250> mix<00:03:24.459> net<00:03:24.870> such<00:03:25.870> as<00:03:25.989> one 00:03:26.160 --> 00:03:26.170 align:start position:0% want to use the mix net such as one 00:03:26.170 --> 00:03:27.990 align:start position:0% want to use the mix net such as one developed<00:03:26.680> by<00:03:26.739> NIMH<00:03:26.980> but<00:03:27.670> if<00:03:27.820> you<00:03:27.910> have 00:03:27.990 --> 00:03:28.000 align:start position:0% developed by NIMH but if you have 00:03:28.000 --> 00:03:30.060 align:start position:0% developed by NIMH but if you have different<00:03:28.359> of<00:03:28.570> constraints<00:03:29.049> maybe<00:03:29.620> use<00:03:29.859> of 00:03:30.060 --> 00:03:30.070 align:start position:0% different of constraints maybe use of 00:03:30.070 --> 00:03:32.490 align:start position:0% different of constraints maybe use of care<00:03:30.820> a<00:03:30.850> lot<00:03:30.940> about<00:03:31.000> bandwidth<00:03:31.540> or<00:03:31.720> or<00:03:32.049> or 00:03:32.490 --> 00:03:32.500 align:start position:0% care a lot about bandwidth or or or 00:03:32.500 --> 00:03:34.949 align:start position:0% care a lot about bandwidth or or or latency<00:03:32.920> or<00:03:33.370> sense<00:03:34.180> of<00:03:34.299> residence<00:03:34.660> then<00:03:34.840> you 00:03:34.949 --> 00:03:34.959 align:start position:0% latency or sense of residence then you 00:03:34.959 --> 00:03:36.420 align:start position:0% latency or sense of residence then you might<00:03:35.109> want<00:03:35.320> to<00:03:35.410> have<00:03:35.530> a<00:03:35.560> different<00:03:35.859> choice<00:03:36.130> at 00:03:36.420 --> 00:03:36.430 align:start position:0% might want to have a different choice at 00:03:36.430 --> 00:03:41.069 align:start position:0% might want to have a different choice at that<00:03:36.579> specific<00:03:37.060> layer<00:03:39.630> another<00:03:40.630> design<00:03:40.870> goal 00:03:41.069 --> 00:03:41.079 align:start position:0% that specific layer another design goal 00:03:41.079 --> 00:03:45.349 align:start position:0% that specific layer another design goal is<00:03:41.230> in<00:03:41.350> terms<00:03:41.560> of<00:03:41.799> better<00:03:42.489> specifications<00:03:43.239> and 00:03:45.349 --> 00:03:45.359 align:start position:0% is in terms of better specifications and 00:03:45.359 --> 00:03:47.759 align:start position:0% is in terms of better specifications and for<00:03:46.359> status<00:03:46.750> we<00:03:46.930> started<00:03:47.290> off<00:03:47.380> with<00:03:47.530> this<00:03:47.650> or 00:03:47.759 --> 00:03:47.769 align:start position:0% for status we started off with this or 00:03:47.769 --> 00:03:50.729 align:start position:0% for status we started off with this or ad<00:03:47.920> hoc<00:03:47.950> protocol<00:03:48.609> defining<00:03:49.239> the<00:03:49.329> app<00:03:49.450> and<00:03:50.320> now 00:03:50.729 --> 00:03:50.739 align:start position:0% ad hoc protocol defining the app and now 00:03:50.739 --> 00:03:52.470 align:start position:0% ad hoc protocol defining the app and now we're<00:03:50.859> sort<00:03:51.010> of<00:03:51.040> moving<00:03:51.459> to<00:03:51.820> the<00:03:51.970> more<00:03:52.299> other 00:03:52.470 --> 00:03:52.480 align:start position:0% we're sort of moving to the more other 00:03:52.480 --> 00:03:54.810 align:start position:0% we're sort of moving to the more other extreme<00:03:52.840> where<00:03:53.049> we<00:03:53.140> serve<00:03:53.670> look<00:03:54.670> at<00:03:54.760> a 00:03:54.810 --> 00:03:54.820 align:start position:0% extreme where we serve look at a 00:03:54.820 --> 00:03:56.520 align:start position:0% extreme where we serve look at a protocol<00:03:55.180> as<00:03:55.390> its<00:03:55.570> as<00:03:55.750> an<00:03:55.930> animal<00:03:56.260> in<00:03:56.350> its<00:03:56.470> own 00:03:56.520 --> 00:03:56.530 align:start position:0% protocol as its as an animal in its own 00:03:56.530 --> 00:03:58.800 align:start position:0% protocol as its as an animal in its own right<00:03:56.739> and<00:03:57.239> sort<00:03:58.239> of<00:03:58.299> trying<00:03:58.540> to<00:03:58.600> make<00:03:58.780> it 00:03:58.800 --> 00:03:58.810 align:start position:0% right and sort of trying to make it 00:03:58.810 --> 00:04:00.960 align:start position:0% right and sort of trying to make it maximum<00:03:59.140> a<00:03:59.200> useful<00:03:59.470> for<00:03:59.739> force<00:04:00.130> of<00:04:00.280> other<00:04:00.670> Pods 00:04:00.960 --> 00:04:00.970 align:start position:0% maximum a useful for force of other Pods 00:04:00.970 --> 00:04:02.699 align:start position:0% maximum a useful for force of other Pods as<00:04:01.150> well<00:04:01.329> and<00:04:01.540> it's<00:04:02.049> also<00:04:02.140> include<00:04:02.470> sort<00:04:02.650> of 00:04:02.699 --> 00:04:02.709 align:start position:0% as well and it's also include sort of 00:04:02.709 --> 00:04:04.140 align:start position:0% as well and it's also include sort of making<00:04:02.920> more<00:04:03.130> rigorous<00:04:03.400> analysis<00:04:03.760> of<00:04:03.970> the 00:04:04.140 --> 00:04:04.150 align:start position:0% making more rigorous analysis of the 00:04:04.150 --> 00:04:06.360 align:start position:0% making more rigorous analysis of the exact<00:04:04.420> Kent<00:04:04.720> he's<00:04:04.870> in<00:04:05.079> behaviors<00:04:05.650> of<00:04:05.890> these 00:04:06.360 --> 00:04:06.370 align:start position:0% exact Kent he's in behaviors of these 00:04:06.370 --> 00:04:10.440 align:start position:0% exact Kent he's in behaviors of these protocols<00:04:08.609> another<00:04:09.609> sign<00:04:09.790> goes<00:04:09.940> in<00:04:10.090> terms<00:04:10.269> of 00:04:10.440 --> 00:04:10.450 align:start position:0% protocols another sign goes in terms of 00:04:10.450 --> 00:04:12.780 align:start position:0% protocols another sign goes in terms of sort<00:04:10.780> of<00:04:10.810> pro<00:04:11.739> in<00:04:11.859> the<00:04:11.950> tools<00:04:12.130> to<00:04:12.370> do<00:04:12.519> sort<00:04:12.760> of 00:04:12.780 --> 00:04:12.790 align:start position:0% sort of pro in the tools to do sort of 00:04:12.790 --> 00:04:14.910 align:start position:0% sort of pro in the tools to do sort of simulation<00:04:13.180> testing<00:04:13.510> in<00:04:13.750> beaufort<00:04:14.470> scale<00:04:14.590> and 00:04:14.910 --> 00:04:14.920 align:start position:0% simulation testing in beaufort scale and 00:04:14.920 --> 00:04:17.099 align:start position:0% simulation testing in beaufort scale and for<00:04:15.100> adverse<00:04:15.539> environments<00:04:16.539> and<00:04:16.720> this<00:04:16.810> is<00:04:16.900> for 00:04:17.099 --> 00:04:17.109 align:start position:0% for adverse environments and this is for 00:04:17.109 --> 00:04:19.830 align:start position:0% for adverse environments and this is for things<00:04:17.260> like<00:04:17.459> white<00:04:18.459> lock<00:04:18.729> and<00:04:19.060> Jepson 00:04:19.830 --> 00:04:19.840 align:start position:0% things like white lock and Jepson 00:04:19.840 --> 00:04:22.050 align:start position:0% things like white lock and Jepson simulation<00:04:20.229> framework<00:04:20.530> and<00:04:20.680> so<00:04:20.739> on<00:04:20.940> to<00:04:21.940> make 00:04:22.050 --> 00:04:22.060 align:start position:0% simulation framework and so on to make 00:04:22.060 --> 00:04:23.250 align:start position:0% simulation framework and so on to make sure<00:04:22.240> that<00:04:22.360> the<00:04:22.539> design<00:04:22.810> actually<00:04:22.960> makes 00:04:23.250 --> 00:04:23.260 align:start position:0% sure that the design actually makes 00:04:23.260 --> 00:04:25.740 align:start position:0% sure that the design actually makes sense<00:04:23.410> and<00:04:23.680> will<00:04:23.830> scale<00:04:24.100> to<00:04:24.130> the<00:04:24.570> to<00:04:25.570> sort<00:04:25.720> of 00:04:25.740 --> 00:04:25.750 align:start position:0% sense and will scale to the to sort of 00:04:25.750 --> 00:04:27.719 align:start position:0% sense and will scale to the to sort of have<00:04:26.590> the<00:04:26.740> properties<00:04:27.070> that<00:04:27.099> we<00:04:27.250> want<00:04:27.490> at 00:04:27.719 --> 00:04:27.729 align:start position:0% have the properties that we want at 00:04:27.729 --> 00:04:30.899 align:start position:0% have the properties that we want at scale<00:04:27.970> so<00:04:28.690> it<00:04:28.750> doesn't<00:04:29.020> sort<00:04:29.169> of 00:04:30.899 --> 00:04:30.909 align:start position:0% scale so it doesn't sort of 00:04:30.909 --> 00:04:32.639 align:start position:0% scale so it doesn't sort of full<00:04:31.749> under<00:04:31.990> which<00:04:32.110> is<00:04:32.199> what<00:04:32.319> we<00:04:32.409> were<00:04:32.469> seeing 00:04:32.639 --> 00:04:32.649 align:start position:0% full under which is what we were seeing 00:04:32.649 --> 00:04:34.679 align:start position:0% full under which is what we were seeing with<00:04:32.830> with<00:04:33.159> some<00:04:33.669> of<00:04:33.789> the<00:04:33.879> stuff<00:04:34.029> we<00:04:34.419> had<00:04:34.569> in 00:04:34.679 --> 00:04:34.689 align:start position:0% with with some of the stuff we had in 00:04:34.689 --> 00:04:37.609 align:start position:0% with with some of the stuff we had in production<00:04:35.050> with<00:04:35.169> whisper<00:04:35.469> for<00:04:35.589> example 00:04:37.609 --> 00:04:37.619 align:start position:0% production with whisper for example 00:04:37.619 --> 00:04:40.679 align:start position:0% production with whisper for example another<00:04:38.619> big<00:04:38.830> one<00:04:39.069> is<00:04:39.369> in<00:04:39.520> terms<00:04:39.669> of<00:04:39.939> mostly 00:04:40.679 --> 00:04:40.689 align:start position:0% another big one is in terms of mostly 00:04:40.689 --> 00:04:42.989 align:start position:0% another big one is in terms of mostly offline<00:04:41.020> so<00:04:41.740> when<00:04:42.580> it<00:04:42.669> comes<00:04:42.789> to<00:04:42.879> key 00:04:42.989 --> 00:04:42.999 align:start position:0% offline so when it comes to key 00:04:42.999 --> 00:04:45.389 align:start position:0% offline so when it comes to key messaging<00:04:43.360> and<00:04:43.479> so<00:04:43.599> on<00:04:43.719> often<00:04:44.379> users<00:04:44.979> are<00:04:45.189> sort 00:04:45.389 --> 00:04:45.399 align:start position:0% messaging and so on often users are sort 00:04:45.399 --> 00:04:47.100 align:start position:0% messaging and so on often users are sort of<00:04:45.459> mobile<00:04:45.819> phones<00:04:46.059> and<00:04:46.240> usually<00:04:46.809> this<00:04:46.959> is 00:04:47.100 --> 00:04:47.110 align:start position:0% of mobile phones and usually this is 00:04:47.110 --> 00:04:48.989 align:start position:0% of mobile phones and usually this is sort<00:04:47.289> of<00:04:47.349> an<00:04:47.469> afterthought<00:04:47.889> and<00:04:48.129> this<00:04:48.789> leads 00:04:48.989 --> 00:04:48.999 align:start position:0% sort of an afterthought and this leads 00:04:48.999 --> 00:04:51.449 align:start position:0% sort of an afterthought and this leads to<00:04:49.270> people<00:04:49.830> accessing<00:04:50.830> the<00:04:51.009> network<00:04:51.039> through 00:04:51.449 --> 00:04:51.459 align:start position:0% to people accessing the network through 00:04:51.459 --> 00:04:53.459 align:start position:0% to people accessing the network through gateways<00:04:51.849> and<00:04:52.029> so<00:04:52.119> on<00:04:52.240> and<00:04:52.569> we<00:04:53.050> want<00:04:53.229> to<00:04:53.289> sort 00:04:53.459 --> 00:04:53.469 align:start position:0% gateways and so on and we want to sort 00:04:53.469 --> 00:04:55.549 align:start position:0% gateways and so on and we want to sort of<00:04:53.499> think<00:04:53.679> about<00:04:53.800> this<00:04:54.009> from<00:04:54.099> the<00:04:54.189> get-go 00:04:55.549 --> 00:04:55.559 align:start position:0% of think about this from the get-go 00:04:55.559 --> 00:04:57.629 align:start position:0% of think about this from the get-go because<00:04:56.559> what<00:04:56.830> makes<00:04:57.009> mobile<00:04:57.309> phones<00:04:57.490> bit 00:04:57.629 --> 00:04:57.639 align:start position:0% because what makes mobile phones bit 00:04:57.639 --> 00:04:59.519 align:start position:0% because what makes mobile phones bit special<00:04:57.999> is<00:04:58.149> that<00:04:58.479> for<00:04:58.809> example<00:04:58.959> I<00:04:59.199> guess<00:04:59.379> you 00:04:59.519 --> 00:04:59.529 align:start position:0% special is that for example I guess you 00:04:59.529 --> 00:05:02.070 align:start position:0% special is that for example I guess you can't<00:04:59.740> have<00:05:00.360> back<00:05:01.360> from<00:05:01.509> execution<00:05:01.899> is<00:05:01.959> very 00:05:02.070 --> 00:05:02.080 align:start position:0% can't have back from execution is very 00:05:02.080 --> 00:05:03.480 align:start position:0% can't have back from execution is very limited<00:05:02.469> on<00:05:02.619> Android<00:05:03.009> it's<00:05:03.159> raining<00:05:03.429> a 00:05:03.480 --> 00:05:03.490 align:start position:0% limited on Android it's raining a 00:05:03.490 --> 00:05:05.009 align:start position:0% limited on Android it's raining a battery<00:05:03.789> so<00:05:04.300> you<00:05:04.360> got<00:05:04.479> to<00:05:04.539> think<00:05:04.689> about<00:05:04.779> these 00:05:05.009 --> 00:05:05.019 align:start position:0% battery so you got to think about these 00:05:05.019 --> 00:05:06.600 align:start position:0% battery so you got to think about these things<00:05:05.080> and<00:05:05.439> how<00:05:05.559> he<00:05:05.619> actually<00:05:06.039> sort<00:05:06.580> of 00:05:06.600 --> 00:05:06.610 align:start position:0% things and how he actually sort of 00:05:06.610 --> 00:05:08.129 align:start position:0% things and how he actually sort of natively<00:05:06.939> connect<00:05:07.269> to<00:05:07.360> a<00:05:07.389> network<00:05:07.539> and<00:05:07.899> and 00:05:08.129 --> 00:05:08.139 align:start position:0% natively connect to a network and and 00:05:08.139 --> 00:05:09.839 align:start position:0% natively connect to a network and and make<00:05:08.649> sure<00:05:08.800> things<00:05:09.039> work<00:05:09.249> properly<00:05:09.490> with 00:05:09.839 --> 00:05:09.849 align:start position:0% make sure things work properly with 00:05:09.849 --> 00:05:14.639 align:start position:0% make sure things work properly with recent<00:05:10.569> stick<00:05:10.749> to<00:05:10.839> devices<00:05:12.990> and<00:05:13.990> finally<00:05:14.469> sort 00:05:14.639 --> 00:05:14.649 align:start position:0% recent stick to devices and finally sort 00:05:14.649 --> 00:05:18.179 align:start position:0% recent stick to devices and finally sort of<00:05:14.800> a<00:05:15.099> lot<00:05:15.999> of<00:05:16.029> people<00:05:16.809> use<00:05:17.679> things<00:05:18.009> like 00:05:18.179 --> 00:05:18.189 align:start position:0% of a lot of people use things like 00:05:18.189 --> 00:05:19.769 align:start position:0% of a lot of people use things like what's<00:05:18.369> happened<00:05:18.729> and<00:05:18.879> telegram<00:05:19.479> and<00:05:19.599> so<00:05:19.719> on 00:05:19.769 --> 00:05:19.779 align:start position:0% what's happened and telegram and so on 00:05:19.779 --> 00:05:21.540 align:start position:0% what's happened and telegram and so on and<00:05:19.990> we<00:05:20.080> do<00:05:20.199> it<00:05:20.259> internally<00:05:20.589> it<00:05:21.009> steps<00:05:21.279> as<00:05:21.429> well 00:05:21.540 --> 00:05:21.550 align:start position:0% and we do it internally it steps as well 00:05:21.550 --> 00:05:26.249 align:start position:0% and we do it internally it steps as well and<00:05:21.789> and<00:05:24.269> like<00:05:25.269> people<00:05:25.539> aren't<00:05:25.719> gonna<00:05:25.869> use<00:05:26.050> use 00:05:26.249 --> 00:05:26.259 align:start position:0% and and like people aren't gonna use use 00:05:26.259 --> 00:05:27.269 align:start position:0% and and like people aren't gonna use use not<00:05:26.439> only<00:05:26.619> on<00:05:26.769> this<00:05:26.889> that<00:05:27.069> you<00:05:27.159> actually 00:05:27.269 --> 00:05:27.279 align:start position:0% not only on this that you actually 00:05:27.279 --> 00:05:30.059 align:start position:0% not only on this that you actually enable<00:05:27.669> Nixon<00:05:28.059> to<00:05:28.119> use<00:05:28.240> experience<00:05:28.569> so<00:05:29.379> that's 00:05:30.059 --> 00:05:30.069 align:start position:0% enable Nixon to use experience so that's 00:05:30.069 --> 00:05:31.379 align:start position:0% enable Nixon to use experience so that's something<00:05:30.369> you<00:05:30.550> have<00:05:30.729> to<00:05:30.879> so<00:05:30.999> if<00:05:31.089> you<00:05:31.119> have<00:05:31.269> to 00:05:31.379 --> 00:05:31.389 align:start position:0% something you have to so if you have to 00:05:31.389 --> 00:05:33.629 align:start position:0% something you have to so if you have to make<00:05:32.259> sure<00:05:32.409> it<00:05:32.529> is<00:05:32.679> support<00:05:33.039> to<00:05:33.129> user<00:05:33.279> stories 00:05:33.629 --> 00:05:33.639 align:start position:0% make sure it is support to user stories 00:05:33.639 --> 00:05:35.519 align:start position:0% make sure it is support to user stories for<00:05:33.999> the<00:05:34.119> end<00:05:34.240> users<00:05:34.599> therefore<00:05:35.409> people 00:05:35.519 --> 00:05:35.529 align:start position:0% for the end users therefore people 00:05:35.529 --> 00:05:38.730 align:start position:0% for the end users therefore people actually<00:05:35.860> use<00:05:35.979> this<00:05:36.069> kind<00:05:36.189> of<00:05:36.279> stuff<00:05:37.740> with 00:05:38.730 --> 00:05:38.740 align:start position:0% actually use this kind of stuff with 00:05:38.740 --> 00:05:40.199 align:start position:0% actually use this kind of stuff with that<00:05:38.919> theme<00:05:39.579> we'll<00:05:39.699> talk<00:05:39.819> a<00:05:39.849> bit<00:05:39.999> about<00:05:40.029> our 00:05:40.199 --> 00:05:40.209 align:start position:0% that theme we'll talk a bit about our 00:05:40.209 --> 00:05:44.519 align:start position:0% that theme we'll talk a bit about our date<00:05:40.899> Sinclair<00:05:41.969> yeah<00:05:42.969> so<00:05:43.360> what<00:05:43.959> we<00:05:44.079> started 00:05:44.519 --> 00:05:44.529 align:start position:0% date Sinclair yeah so what we started 00:05:44.529 --> 00:05:46.559 align:start position:0% date Sinclair yeah so what we started off<00:05:44.649> with<00:05:44.860> that<00:05:44.919> status<00:05:45.490> is<00:05:45.699> a<00:05:45.819> very<00:05:46.209> naive 00:05:46.559 --> 00:05:46.569 align:start position:0% off with that status is a very naive 00:05:46.569 --> 00:05:49.889 align:start position:0% off with that status is a very naive whisper<00:05:47.319> transport<00:05:48.159> and<00:05:48.509> whisper<00:05:49.509> comes<00:05:49.719> with 00:05:49.889 --> 00:05:49.899 align:start position:0% whisper transport and whisper comes with 00:05:49.899 --> 00:05:51.600 align:start position:0% whisper transport and whisper comes with what<00:05:50.139> various<00:05:50.589> issues<00:05:50.740> in<00:05:51.189> the<00:05:51.279> way<00:05:51.399> that 00:05:51.600 --> 00:05:51.610 align:start position:0% what various issues in the way that 00:05:51.610 --> 00:05:53.369 align:start position:0% what various issues in the way that messages<00:05:52.089> are<00:05:52.240> sent<00:05:52.449> they<00:05:52.689> expire<00:05:53.110> at<00:05:53.289> a 00:05:53.369 --> 00:05:53.379 align:start position:0% messages are sent they expire at a 00:05:53.379 --> 00:05:56.790 align:start position:0% messages are sent they expire at a certain<00:05:53.709> point<00:05:53.919> so<00:05:54.459> we<00:05:54.729> need<00:05:54.879> to<00:05:54.999> go<00:05:55.149> to<00:05:55.800> save 00:05:56.790 --> 00:05:56.800 align:start position:0% certain point so we need to go to save 00:05:56.800 --> 00:05:58.529 align:start position:0% certain point so we need to go to save these<00:05:56.949> messages<00:05:57.399> on<00:05:57.490> a<00:05:57.519> mail<00:05:57.759> server<00:05:58.089> so<00:05:58.360> that 00:05:58.529 --> 00:05:58.539 align:start position:0% these messages on a mail server so that 00:05:58.539 --> 00:06:00.989 align:start position:0% these messages on a mail server so that with<00:05:58.779> mostly<00:05:59.079> offline<00:05:59.439> devices<00:05:59.979> a<00:06:00.249> message 00:06:00.989 --> 00:06:00.999 align:start position:0% with mostly offline devices a message 00:06:00.999 --> 00:06:05.790 align:start position:0% with mostly offline devices a message actually<00:06:01.539> reaches<00:06:02.050> its<00:06:02.879> destination<00:06:03.879> user<00:06:04.809> so 00:06:05.790 --> 00:06:05.800 align:start position:0% actually reaches its destination user so 00:06:05.800 --> 00:06:07.649 align:start position:0% actually reaches its destination user so to<00:06:05.860> solve<00:06:06.729> for<00:06:06.939> that<00:06:06.999> what<00:06:07.179> we<00:06:07.209> did<00:06:07.419> is<00:06:07.539> we 00:06:07.649 --> 00:06:07.659 align:start position:0% to solve for that what we did is we 00:06:07.659 --> 00:06:09.779 align:start position:0% to solve for that what we did is we built<00:06:07.809> a<00:06:07.959> Data<00:06:08.409> Sync<00:06:08.649> protocol<00:06:09.129> on<00:06:09.399> top<00:06:09.610> of 00:06:09.779 --> 00:06:09.789 align:start position:0% built a Data Sync protocol on top of 00:06:09.789 --> 00:06:12.569 align:start position:0% built a Data Sync protocol on top of whisper<00:06:10.149> to<00:06:10.749> already<00:06:11.289> add<00:06:11.679> more<00:06:12.039> reliability 00:06:12.569 --> 00:06:12.579 align:start position:0% whisper to already add more reliability 00:06:12.579 --> 00:06:15.350 align:start position:0% whisper to already add more reliability guarantees<00:06:13.240> to<00:06:14.199> the<00:06:14.229> lower<00:06:14.499> whisper 00:06:15.350 --> 00:06:15.360 align:start position:0% guarantees to the lower whisper 00:06:15.360 --> 00:06:19.799 align:start position:0% guarantees to the lower whisper transport<00:06:16.360> layer<00:06:16.979> is<00:06:18.449> this<00:06:19.449> a<00:06:19.509> general 00:06:19.799 --> 00:06:19.809 align:start position:0% transport layer is this a general 00:06:19.809 --> 00:06:21.779 align:start position:0% transport layer is this a general problem<00:06:20.259> in<00:06:20.319> peer-to-peer<00:06:20.769> systems<00:06:21.490> when<00:06:21.669> you 00:06:21.779 --> 00:06:21.789 align:start position:0% problem in peer-to-peer systems when you 00:06:21.789 --> 00:06:23.759 align:start position:0% problem in peer-to-peer systems when you have<00:06:21.909> unreliable<00:06:22.509> transports<00:06:23.169> where<00:06:23.619> you 00:06:23.759 --> 00:06:23.769 align:start position:0% have unreliable transports where you 00:06:23.769 --> 00:06:25.829 align:start position:0% have unreliable transports where you need<00:06:23.919> to<00:06:24.099> add<00:06:24.279> some<00:06:24.729> form<00:06:25.089> of<00:06:25.240> synchronization 00:06:25.829 --> 00:06:25.839 align:start position:0% need to add some form of synchronization 00:06:25.839 --> 00:06:29.489 align:start position:0% need to add some form of synchronization protocol<00:06:26.589> on<00:06:26.860> top<00:06:27.519> of<00:06:27.639> it<00:06:27.789> to<00:06:28.569> ensure<00:06:28.599> that<00:06:29.050> we 00:06:29.489 --> 00:06:29.499 align:start position:0% protocol on top of it to ensure that we 00:06:29.499 --> 00:06:32.279 align:start position:0% protocol on top of it to ensure that we have<00:06:29.709> these<00:06:30.089> availability<00:06:31.089> guarantees<00:06:31.289> which 00:06:32.279 --> 00:06:32.289 align:start position:0% have these availability guarantees which 00:06:32.289 --> 00:06:35.179 align:start position:0% have these availability guarantees which are<00:06:32.740> usually<00:06:32.949> only<00:06:33.759> achievable<00:06:34.269> through 00:06:35.179 --> 00:06:35.189 align:start position:0% are usually only achievable through 00:06:35.189 --> 00:06:38.459 align:start position:0% are usually only achievable through centralized<00:06:36.189> servers<00:06:37.079> so<00:06:38.079> how<00:06:38.169> does<00:06:38.349> this 00:06:38.459 --> 00:06:38.469 align:start position:0% centralized servers so how does this 00:06:38.469 --> 00:06:42.629 align:start position:0% centralized servers so how does this look<00:06:38.679> it's<00:06:39.519> a<00:06:39.729> very<00:06:40.169> tcp<00:06:41.169> like<00:06:41.459> inspired 00:06:42.629 --> 00:06:42.639 align:start position:0% look it's a very tcp like inspired 00:06:42.639 --> 00:06:44.410 align:start position:0% look it's a very tcp like inspired protocol 00:06:44.410 --> 00:06:44.420 align:start position:0% protocol 00:06:44.420 --> 00:06:47.440 align:start position:0% protocol that<00:06:44.720> we<00:06:45.290> now<00:06:45.980> split<00:06:46.640> up<00:06:46.790> the<00:06:46.940> way<00:06:47.030> we<00:06:47.060> send<00:06:47.360> a 00:06:47.440 --> 00:06:47.450 align:start position:0% that we now split up the way we send a 00:06:47.450 --> 00:06:49.330 align:start position:0% that we now split up the way we send a message<00:06:47.480> into<00:06:47.990> multiple<00:06:48.380> steps<00:06:48.500> what<00:06:49.220> we 00:06:49.330 --> 00:06:49.340 align:start position:0% message into multiple steps what we 00:06:49.340 --> 00:06:51.940 align:start position:0% message into multiple steps what we initially<00:06:49.550> do<00:06:49.880> is<00:06:50.000> we<00:06:50.150> offer<00:06:50.360> a<00:06:50.870> message<00:06:51.410> to<00:06:51.920> a 00:06:51.940 --> 00:06:51.950 align:start position:0% initially do is we offer a message to a 00:06:51.950 --> 00:06:54.490 align:start position:0% initially do is we offer a message to a specific<00:06:52.580> user<00:06:53.000> so<00:06:53.300> Alice<00:06:53.690> would<00:06:53.870> offer<00:06:54.110> a 00:06:54.490 --> 00:06:54.500 align:start position:0% specific user so Alice would offer a 00:06:54.500 --> 00:06:59.830 align:start position:0% specific user so Alice would offer a payload<00:06:55.780> to<00:06:56.780> Bob<00:06:57.230> and<00:06:57.560> then<00:06:58.550> once<00:06:58.880> Bob<00:06:59.660> has 00:06:59.830 --> 00:06:59.840 align:start position:0% payload to Bob and then once Bob has 00:06:59.840 --> 00:07:02.230 align:start position:0% payload to Bob and then once Bob has received<00:07:00.380> that<00:07:00.620> message<00:07:01.130> of<00:07:01.550> the<00:07:01.700> offer<00:07:01.820> he 00:07:02.230 --> 00:07:02.240 align:start position:0% received that message of the offer he 00:07:02.240 --> 00:07:04.690 align:start position:0% received that message of the offer he will<00:07:02.360> request<00:07:02.720> it<00:07:02.900> from<00:07:02.930> Alice<00:07:03.490> Alice<00:07:04.490> then 00:07:04.690 --> 00:07:04.700 align:start position:0% will request it from Alice Alice then 00:07:04.700 --> 00:07:08.650 align:start position:0% will request it from Alice Alice then sends<00:07:05.090> that<00:07:05.150> message<00:07:05.360> and<00:07:06.170> Bob<00:07:06.830> then<00:07:07.660> returns 00:07:08.650 --> 00:07:08.660 align:start position:0% sends that message and Bob then returns 00:07:08.660 --> 00:07:10.660 align:start position:0% sends that message and Bob then returns an<00:07:09.080> ACK<00:07:09.410> saying<00:07:09.980> that<00:07:10.130> I<00:07:10.160> received<00:07:10.550> this 00:07:10.660 --> 00:07:10.670 align:start position:0% an ACK saying that I received this 00:07:10.670 --> 00:07:13.150 align:start position:0% an ACK saying that I received this message<00:07:11.060> with<00:07:11.750> the<00:07:11.870> each<00:07:12.350> of<00:07:12.680> these<00:07:12.830> steps 00:07:13.150 --> 00:07:13.160 align:start position:0% message with the each of these steps 00:07:13.160 --> 00:07:16.270 align:start position:0% message with the each of these steps what<00:07:13.490> happens<00:07:13.940> is<00:07:14.360> things<00:07:15.290> are<00:07:15.440> retransmitted 00:07:16.270 --> 00:07:16.280 align:start position:0% what happens is things are retransmitted 00:07:16.280 --> 00:07:18.550 align:start position:0% what happens is things are retransmitted so<00:07:16.820> if<00:07:16.970> Bob<00:07:17.210> is<00:07:17.330> offline<00:07:17.840> when<00:07:18.110> alice<00:07:18.410> is 00:07:18.550 --> 00:07:18.560 align:start position:0% so if Bob is offline when alice is 00:07:18.560 --> 00:07:20.130 align:start position:0% so if Bob is offline when alice is sending<00:07:18.590> an<00:07:18.950> offer<00:07:19.130> Alice<00:07:19.850> will 00:07:20.130 --> 00:07:20.140 align:start position:0% sending an offer Alice will 00:07:20.140 --> 00:07:22.720 align:start position:0% sending an offer Alice will exponentially<00:07:21.140> try<00:07:21.590> and<00:07:21.800> offer<00:07:21.920> that<00:07:22.250> message 00:07:22.720 --> 00:07:22.730 align:start position:0% exponentially try and offer that message 00:07:22.730 --> 00:07:25.510 align:start position:0% exponentially try and offer that message again<00:07:23.360> and<00:07:23.600> again<00:07:23.960> up<00:07:24.440> until<00:07:24.860> it<00:07:25.010> receives<00:07:25.160> a 00:07:25.510 --> 00:07:25.520 align:start position:0% again and again up until it receives a 00:07:25.520 --> 00:07:28.930 align:start position:0% again and again up until it receives a request<00:07:25.880> from<00:07:26.060> bulb<00:07:26.360> and<00:07:27.130> that<00:07:28.130> continues<00:07:28.670> for 00:07:28.930 --> 00:07:28.940 align:start position:0% request from bulb and that continues for 00:07:28.940 --> 00:07:31.360 align:start position:0% request from bulb and that continues for every<00:07:29.150> stage<00:07:29.420> so<00:07:30.020> we<00:07:30.230> we<00:07:30.560> know<00:07:30.800> that<00:07:31.130> this 00:07:31.360 --> 00:07:31.370 align:start position:0% every stage so we we know that this 00:07:31.370 --> 00:07:33.610 align:start position:0% every stage so we we know that this entire<00:07:31.640> process<00:07:31.910> has<00:07:32.240> happened<00:07:32.780> and<00:07:33.320> that<00:07:33.560> a 00:07:33.610 --> 00:07:33.620 align:start position:0% entire process has happened and that a 00:07:33.620 --> 00:07:35.170 align:start position:0% entire process has happened and that a message<00:07:34.040> is<00:07:34.160> transported<00:07:34.850> in<00:07:34.940> the<00:07:34.970> end 00:07:35.170 --> 00:07:35.180 align:start position:0% message is transported in the end 00:07:35.180 --> 00:07:37.270 align:start position:0% message is transported in the end successfully<00:07:35.360> because<00:07:36.290> we've<00:07:36.440> retransmitted 00:07:37.270 --> 00:07:37.280 align:start position:0% successfully because we've retransmitted 00:07:37.280 --> 00:07:41.200 align:start position:0% successfully because we've retransmitted it<00:07:37.370> up<00:07:37.550> until<00:07:37.880> the<00:07:37.970> next<00:07:38.150> step<00:07:39.910> that's<00:07:40.910> how<00:07:41.150> the 00:07:41.200 --> 00:07:41.210 align:start position:0% it up until the next step that's how the 00:07:41.210 --> 00:07:42.550 align:start position:0% it up until the next step that's how the interactive<00:07:41.840> mode<00:07:41.990> works<00:07:42.140> that's<00:07:42.410> like<00:07:42.530> a 00:07:42.550 --> 00:07:42.560 align:start position:0% interactive mode works that's like a 00:07:42.560 --> 00:07:46.780 align:start position:0% interactive mode works that's like a very<00:07:43.210> bandwidth<00:07:44.210> high<00:07:45.460> version<00:07:46.460> of<00:07:46.700> the 00:07:46.780 --> 00:07:46.790 align:start position:0% very bandwidth high version of the 00:07:46.790 --> 00:07:49.240 align:start position:0% very bandwidth high version of the protocol<00:07:47.240> what<00:07:47.960> we<00:07:48.080> also<00:07:48.230> have<00:07:48.350> is<00:07:48.710> the<00:07:49.010> batch 00:07:49.240 --> 00:07:49.250 align:start position:0% protocol what we also have is the batch 00:07:49.250 --> 00:07:51.280 align:start position:0% protocol what we also have is the batch data<00:07:49.640> sync<00:07:49.910> mode<00:07:50.120> so<00:07:50.420> here<00:07:50.630> we<00:07:50.720> don't<00:07:50.870> have<00:07:51.020> any 00:07:51.280 --> 00:07:51.290 align:start position:0% data sync mode so here we don't have any 00:07:51.290 --> 00:07:53.440 align:start position:0% data sync mode so here we don't have any offers<00:07:51.740> we<00:07:51.860> don't<00:07:52.040> have<00:07:52.160> any<00:07:52.310> requests<00:07:52.910> what 00:07:53.440 --> 00:07:53.450 align:start position:0% offers we don't have any requests what 00:07:53.450 --> 00:07:56.230 align:start position:0% offers we don't have any requests what we<00:07:53.600> do<00:07:53.750> here<00:07:54.050> is<00:07:54.170> we<00:07:54.200> simply<00:07:54.940> repeatedly<00:07:55.940> send 00:07:56.230 --> 00:07:56.240 align:start position:0% we do here is we simply repeatedly send 00:07:56.240 --> 00:07:59.580 align:start position:0% we do here is we simply repeatedly send the<00:07:56.390> message<00:07:56.690> payload<00:07:57.170> up<00:07:57.380> until<00:07:57.920> we<00:07:58.790> have 00:07:59.580 --> 00:07:59.590 align:start position:0% the message payload up until we have 00:07:59.590 --> 00:08:02.320 align:start position:0% the message payload up until we have received<00:08:00.590> X<00:08:00.830> this<00:08:01.340> is<00:08:01.490> sorry<00:08:01.970> this<00:08:02.030> is<00:08:02.270> the 00:08:02.320 --> 00:08:02.330 align:start position:0% received X this is sorry this is the 00:08:02.330 --> 00:08:03.550 align:start position:0% received X this is sorry this is the bandwidth<00:08:02.780> high<00:08:02.960> one<00:08:03.170> the<00:08:03.260> other<00:08:03.380> one<00:08:03.530> just 00:08:03.550 --> 00:08:03.560 align:start position:0% bandwidth high one the other one just 00:08:03.560 --> 00:08:05.530 align:start position:0% bandwidth high one the other one just has<00:08:03.830> a<00:08:04.100> higher<00:08:04.400> latency<00:08:04.670> up<00:08:05.090> until<00:08:05.390> you've 00:08:05.530 --> 00:08:05.540 align:start position:0% has a higher latency up until you've 00:08:05.540 --> 00:08:06.970 align:start position:0% has a higher latency up until you've received<00:08:06.080> the<00:08:06.200> actual<00:08:06.500> message<00:08:06.650> because 00:08:06.970 --> 00:08:06.980 align:start position:0% received the actual message because 00:08:06.980 --> 00:08:10.660 align:start position:0% received the actual message because there's<00:08:07.160> multiple<00:08:07.550> steps<00:08:08.030> in<00:08:08.210> between<00:08:09.670> this 00:08:10.660 --> 00:08:10.670 align:start position:0% there's multiple steps in between this 00:08:10.670 --> 00:08:13.030 align:start position:0% there's multiple steps in between this still<00:08:11.000> has<00:08:11.240> certain<00:08:11.900> problems<00:08:12.200> because<00:08:12.800> it 00:08:13.030 --> 00:08:13.040 align:start position:0% still has certain problems because it 00:08:13.040 --> 00:08:15.580 align:start position:0% still has certain problems because it requires<00:08:13.430> us<00:08:13.730> to<00:08:13.760> keep<00:08:14.410> forwarding<00:08:15.410> these 00:08:15.580 --> 00:08:15.590 align:start position:0% requires us to keep forwarding these 00:08:15.590 --> 00:08:18.580 align:start position:0% requires us to keep forwarding these messages<00:08:16.130> repeatedly<00:08:16.730> so<00:08:17.390> one<00:08:18.110> way<00:08:18.290> we<00:08:18.320> can 00:08:18.580 --> 00:08:18.590 align:start position:0% messages repeatedly so one way we can 00:08:18.590 --> 00:08:20.380 align:start position:0% messages repeatedly so one way we can solve<00:08:18.800> for<00:08:18.920> that<00:08:19.070> is<00:08:19.280> we<00:08:19.400> can<00:08:19.550> add<00:08:19.790> a<00:08:19.850> remote 00:08:20.380 --> 00:08:20.390 align:start position:0% solve for that is we can add a remote 00:08:20.390 --> 00:08:23.410 align:start position:0% solve for that is we can add a remote log<00:08:20.690> on<00:08:20.960> top<00:08:21.470> of<00:08:21.620> the<00:08:21.770> protocol<00:08:22.250> which<00:08:22.730> Oscar 00:08:23.410 --> 00:08:23.420 align:start position:0% log on top of the protocol which Oscar 00:08:23.420 --> 00:08:27.070 align:start position:0% log on top of the protocol which Oscar will<00:08:23.570> talk<00:08:23.750> about<00:08:25.060> yep<00:08:26.060> so<00:08:26.420> so<00:08:26.690> the<00:08:26.750> idea<00:08:26.810> with 00:08:27.070 --> 00:08:27.080 align:start position:0% will talk about yep so so the idea with 00:08:27.080 --> 00:08:28.450 align:start position:0% will talk about yep so so the idea with the<00:08:27.140> remote<00:08:27.350> log<00:08:27.500> is<00:08:27.590> very<00:08:27.770> straightforward 00:08:28.450 --> 00:08:28.460 align:start position:0% the remote log is very straightforward 00:08:28.460 --> 00:08:31.480 align:start position:0% the remote log is very straightforward you<00:08:29.030> centrally<00:08:29.540> have<00:08:29.720> a<00:08:30.040> local<00:08:31.040> log<00:08:31.190> where<00:08:31.400> you 00:08:31.480 --> 00:08:31.490 align:start position:0% you centrally have a local log where you 00:08:31.490 --> 00:08:32.950 align:start position:0% you centrally have a local log where you sort<00:08:31.670> of<00:08:31.700> have<00:08:32.150> you<00:08:32.270> messages<00:08:32.600> on<00:08:32.750> a<00:08:32.780> local 00:08:32.950 --> 00:08:32.960 align:start position:0% sort of have you messages on a local 00:08:32.960 --> 00:08:34.240 align:start position:0% sort of have you messages on a local machine<00:08:32.990> and<00:08:33.350> then<00:08:33.440> you<00:08:33.500> replicate<00:08:33.710> it<00:08:34.070> on 00:08:34.240 --> 00:08:34.250 align:start position:0% machine and then you replicate it on 00:08:34.250 --> 00:08:38.260 align:start position:0% machine and then you replicate it on some<00:08:34.580> decent-size<00:08:35.360> file<00:08:35.630> storage<00:08:36.220> and<00:08:37.270> that 00:08:38.260 --> 00:08:38.270 align:start position:0% some decent-size file storage and that 00:08:38.270 --> 00:08:40.300 align:start position:0% some decent-size file storage and that acts<00:08:38.479> as<00:08:38.630> kind<00:08:38.780> of<00:08:38.930> highly<00:08:39.650> available<00:08:39.770> caching 00:08:40.300 --> 00:08:40.310 align:start position:0% acts as kind of highly available caching 00:08:40.310 --> 00:08:43.900 align:start position:0% acts as kind of highly available caching layer<00:08:41.680> so<00:08:42.680> what<00:08:43.310> you<00:08:43.400> have<00:08:43.580> is<00:08:43.760> you<00:08:43.880> have 00:08:43.900 --> 00:08:43.910 align:start position:0% layer so what you have is you have 00:08:43.910 --> 00:08:46.150 align:start position:0% layer so what you have is you have exactly<00:08:44.330> two<00:08:44.570> two<00:08:44.870> new<00:08:45.530> components<00:08:46.040> you<00:08:46.130> have 00:08:46.150 --> 00:08:46.160 align:start position:0% exactly two two new components you have 00:08:46.160 --> 00:08:49.660 align:start position:0% exactly two two new components you have a<00:08:46.250> cache<00:08:46.490> and<00:08:46.730> then<00:08:46.940> name<00:08:47.660> system<00:08:48.340> the<00:08:49.340> cast<00:08:49.550> is 00:08:49.660 --> 00:08:49.670 align:start position:0% a cache and then name system the cast is 00:08:49.670 --> 00:08:53.050 align:start position:0% a cache and then name system the cast is contestable<00:08:50.330> storage<00:08:50.690> and<00:08:51.550> essentially<00:08:52.550> you 00:08:53.050 --> 00:08:53.060 align:start position:0% contestable storage and essentially you 00:08:53.060 --> 00:08:56.380 align:start position:0% contestable storage and essentially you you<00:08:54.040> you<00:08:55.040> upload<00:08:55.340> some<00:08:55.460> content<00:08:55.910> and<00:08:56.120> then<00:08:56.240> you 00:08:56.380 --> 00:08:56.390 align:start position:0% you you upload some content and then you 00:08:56.390 --> 00:08:58.269 align:start position:0% you you upload some content and then you address<00:08:56.570> it<00:08:56.690> by<00:08:56.870> sort<00:08:57.140> of<00:08:57.170> its<00:08:57.350> content<00:08:57.740> hash 00:08:58.269 --> 00:08:58.279 align:start position:0% address it by sort of its content hash 00:08:58.279 --> 00:09:00.879 align:start position:0% address it by sort of its content hash mutable<00:08:58.610> store<00:08:58.990> and<00:08:59.990> the<00:09:00.079> name<00:09:00.259> system<00:09:00.649> that's 00:09:00.879 --> 00:09:00.889 align:start position:0% mutable store and the name system that's 00:09:00.889 --> 00:09:03.999 align:start position:0% mutable store and the name system that's something<00:09:01.220> like<00:09:01.430> DNS<00:09:01.999> or<00:09:02.269> ENS<00:09:03.139> or<00:09:03.470> swamp<00:09:03.800> feeds 00:09:03.999 --> 00:09:04.009 align:start position:0% something like DNS or ENS or swamp feeds 00:09:04.009 --> 00:09:07.210 align:start position:0% something like DNS or ENS or swamp feeds or<00:09:04.249> IP<00:09:05.029> NS<00:09:05.300> in<00:09:05.600> the<00:09:05.779> IP<00:09:05.990> FS<00:09:06.230> world<00:09:06.439> and<00:09:06.620> it 00:09:07.210 --> 00:09:07.220 align:start position:0% or IP NS in the IP FS world and it 00:09:07.220 --> 00:09:08.470 align:start position:0% or IP NS in the IP FS world and it essentially<00:09:07.579> gives<00:09:07.730> you<00:09:07.910> some<00:09:08.089> location 00:09:08.470 --> 00:09:08.480 align:start position:0% essentially gives you some location 00:09:08.480 --> 00:09:12.189 align:start position:0% essentially gives you some location addressing<00:09:08.930> or<00:09:09.110> mutable<00:09:09.620> references<00:09:10.689> so<00:09:11.689> when 00:09:12.189 --> 00:09:12.199 align:start position:0% addressing or mutable references so when 00:09:12.199 --> 00:09:12.730 align:start position:0% addressing or mutable references so when Alice 00:09:12.730 --> 00:09:12.740 align:start position:0% Alice 00:09:12.740 --> 00:09:16.239 align:start position:0% Alice so<00:09:13.459> they<00:09:14.449> upload<00:09:14.959> something<00:09:15.259> to<00:09:15.499> the<00:09:15.769> cast<00:09:15.980> and 00:09:16.239 --> 00:09:16.249 align:start position:0% so they upload something to the cast and 00:09:16.249 --> 00:09:17.710 align:start position:0% so they upload something to the cast and they<00:09:16.309> get<00:09:16.459> back<00:09:16.639> to<00:09:16.790> address<00:09:16.970> for<00:09:17.149> it<00:09:17.240> and<00:09:17.389> then 00:09:17.710 --> 00:09:17.720 align:start position:0% they get back to address for it and then 00:09:17.720 --> 00:09:19.629 align:start position:0% they get back to address for it and then the<00:09:17.839> update<00:09:17.959> stuff<00:09:18.379> they<00:09:18.589> they<00:09:18.829> the<00:09:19.490> name 00:09:19.629 --> 00:09:19.639 align:start position:0% the update stuff they they the name 00:09:19.639 --> 00:09:22.929 align:start position:0% the update stuff they they the name system<00:09:20.170> and<00:09:21.170> then<00:09:21.829> when<00:09:22.279> when<00:09:22.550> Bob<00:09:22.730> comes 00:09:22.929 --> 00:09:22.939 align:start position:0% system and then when when Bob comes 00:09:22.939 --> 00:09:24.730 align:start position:0% system and then when when Bob comes online<00:09:23.089> when<00:09:23.569> it<00:09:23.600> notes<00:09:23.809> comes<00:09:23.990> online<00:09:24.110> and 00:09:24.730 --> 00:09:24.740 align:start position:0% online when it notes comes online and 00:09:24.740 --> 00:09:26.860 align:start position:0% online when it notes comes online and they<00:09:24.920> know<00:09:25.160> about<00:09:25.339> sort<00:09:25.730> of<00:09:25.819> this<00:09:26.269> this<00:09:26.329> kind 00:09:26.860 --> 00:09:26.870 align:start position:0% they know about sort of this this kind 00:09:26.870 --> 00:09:28.600 align:start position:0% they know about sort of this this kind of<00:09:26.899> conversation<00:09:27.529> or<00:09:27.680> do<00:09:27.829> this<00:09:27.949> sync<00:09:28.370> scope 00:09:28.600 --> 00:09:28.610 align:start position:0% of conversation or do this sync scope 00:09:28.610 --> 00:09:30.369 align:start position:0% of conversation or do this sync scope between<00:09:29.059> Alice<00:09:29.329> and<00:09:29.360> Bob<00:09:29.480> they<00:09:29.990> have<00:09:30.079> a<00:09:30.139> fixed 00:09:30.369 --> 00:09:30.379 align:start position:0% between Alice and Bob they have a fixed 00:09:30.379 --> 00:09:31.780 align:start position:0% between Alice and Bob they have a fixed point<00:09:30.529> they<00:09:30.769> know<00:09:30.949> that<00:09:31.100> it<00:09:31.220> can<00:09:31.370> look<00:09:31.519> at<00:09:31.699> the 00:09:31.780 --> 00:09:31.790 align:start position:0% point they know that it can look at the 00:09:31.790 --> 00:09:34.569 align:start position:0% point they know that it can look at the name<00:09:31.939> system<00:09:32.920> even<00:09:33.920> with<00:09:34.009> Alice<00:09:34.399> being 00:09:34.569 --> 00:09:34.579 align:start position:0% name system even with Alice being 00:09:34.579 --> 00:09:37.090 align:start position:0% name system even with Alice being offline<00:09:34.850> so<00:09:35.839> they<00:09:36.139> check<00:09:36.470> the<00:09:36.589> name<00:09:36.709> system 00:09:37.090 --> 00:09:37.100 align:start position:0% offline so they check the name system 00:09:37.100 --> 00:09:39.160 align:start position:0% offline so they check the name system and<00:09:37.819> they<00:09:38.240> see<00:09:38.449> what<00:09:38.600> message<00:09:38.899> they've<00:09:39.050> been 00:09:39.160 --> 00:09:39.170 align:start position:0% and they see what message they've been 00:09:39.170 --> 00:09:41.319 align:start position:0% and they see what message they've been missing<00:09:39.350> and<00:09:39.620> then<00:09:40.249> it<00:09:40.399> can<00:09:40.459> go<00:09:40.639> to<00:09:40.699> the<00:09:40.939> to<00:09:41.240> the 00:09:41.319 --> 00:09:41.329 align:start position:0% missing and then it can go to the to the 00:09:41.329 --> 00:09:43.900 align:start position:0% missing and then it can go to the to the cast<00:09:41.569> and<00:09:41.809> and<00:09:42.079> get<00:09:42.259> those<00:09:42.579> without<00:09:43.579> Alice 00:09:43.900 --> 00:09:43.910 align:start position:0% cast and and get those without Alice 00:09:43.910 --> 00:09:46.809 align:start position:0% cast and and get those without Alice being<00:09:44.089> online<00:09:44.980> in<00:09:45.980> terms<00:09:46.129> of<00:09:46.309> data<00:09:46.490> format 00:09:46.809 --> 00:09:46.819 align:start position:0% being online in terms of data format 00:09:46.819 --> 00:09:48.910 align:start position:0% being online in terms of data format it's<00:09:46.970> it's<00:09:47.199> very<00:09:48.199> straightforward<00:09:48.410> it's 00:09:48.910 --> 00:09:48.920 align:start position:0% it's it's very straightforward it's 00:09:48.920 --> 00:09:51.400 align:start position:0% it's it's very straightforward it's essentially<00:09:49.249> a<00:09:49.309> mapping<00:09:49.699> and<00:09:50.449> it's<00:09:51.230> just 00:09:51.400 --> 00:09:51.410 align:start position:0% essentially a mapping and it's just 00:09:51.410 --> 00:09:53.920 align:start position:0% essentially a mapping and it's just mapping<00:09:51.769> from<00:09:52.040> sort<00:09:52.279> of<00:09:52.339> the<00:09:52.399> native<00:09:52.930> methods 00:09:53.920 --> 00:09:53.930 align:start position:0% mapping from sort of the native methods 00:09:53.930 --> 00:09:55.059 align:start position:0% mapping from sort of the native methods identifier<00:09:54.319> which<00:09:54.559> is<00:09:54.680> sort<00:09:54.829> of<00:09:54.860> what's 00:09:55.059 --> 00:09:55.069 align:start position:0% identifier which is sort of what's 00:09:55.069 --> 00:09:57.639 align:start position:0% identifier which is sort of what's determined<00:09:55.879> by<00:09:55.970> the<00:09:56.029> upper<00:09:56.269> layers<00:09:56.449> to<00:09:56.990> this 00:09:57.639 --> 00:09:57.649 align:start position:0% determined by the upper layers to this 00:09:57.649 --> 00:10:02.319 align:start position:0% determined by the upper layers to this sort<00:09:57.829> of<00:09:58.059> address<00:09:59.059> at<00:09:59.629> there<00:09:59.930> at<00:10:00.110> the<00:10:00.230> Cass<00:10:01.329> and 00:10:02.319 --> 00:10:02.329 align:start position:0% sort of address at there at the Cass and 00:10:02.329 --> 00:10:04.480 align:start position:0% sort of address at there at the Cass and then<00:10:03.259> there's<00:10:03.529> all<00:10:03.649> sort<00:10:03.800> of<00:10:03.860> an<00:10:04.009> address<00:10:04.160> to 00:10:04.480 --> 00:10:04.490 align:start position:0% then there's all sort of an address to 00:10:04.490 --> 00:10:05.949 align:start position:0% then there's all sort of an address to the<00:10:04.790> next<00:10:05.089> page<00:10:05.269> so<00:10:05.480> you<00:10:05.540> essentially<00:10:05.779> have 00:10:05.949 --> 00:10:05.959 align:start position:0% the next page so you essentially have 00:10:05.959 --> 00:10:08.290 align:start position:0% the next page so you essentially have these<00:10:06.110> pages<00:10:06.559> with<00:10:07.129> logs<00:10:07.579> because<00:10:08.059> if<00:10:08.240> you 00:10:08.290 --> 00:10:08.300 align:start position:0% these pages with logs because if you 00:10:08.300 --> 00:10:10.210 align:start position:0% these pages with logs because if you have<00:10:08.389> a<00:10:08.420> lot<00:10:08.540> of<00:10:08.569> sort<00:10:08.809> of<00:10:08.839> misses<00:10:09.139> you<00:10:09.740> you 00:10:10.210 --> 00:10:10.220 align:start position:0% have a lot of sort of misses you you 00:10:10.220 --> 00:10:12.790 align:start position:0% have a lot of sort of misses you you want<00:10:10.519> to<00:10:10.579> split<00:10:10.730> it<00:10:10.819> apart<00:10:11.379> and<00:10:12.379> that's<00:10:12.649> an 00:10:12.790 --> 00:10:12.800 align:start position:0% want to split it apart and that's an 00:10:12.800 --> 00:10:14.619 align:start position:0% want to split it apart and that's an alternative<00:10:13.279> you<00:10:13.459> can<00:10:13.550> also<00:10:13.699> embed<00:10:13.939> this<00:10:14.449> sort 00:10:14.619 --> 00:10:14.629 align:start position:0% alternative you can also embed this sort 00:10:14.629 --> 00:10:17.670 align:start position:0% alternative you can also embed this sort of<00:10:14.720> actual<00:10:15.459> wire<00:10:16.459> payload<00:10:16.910> encrypted<00:10:17.389> content 00:10:17.670 --> 00:10:17.680 align:start position:0% of actual wire payload encrypted content 00:10:17.680 --> 00:10:20.889 align:start position:0% of actual wire payload encrypted content in<00:10:18.680> the<00:10:18.829> name<00:10:18.949> system<00:10:19.250> as<00:10:19.309> well<00:10:19.540> and<00:10:20.540> this<00:10:20.720> is 00:10:20.889 --> 00:10:20.899 align:start position:0% in the name system as well and this is 00:10:20.899 --> 00:10:22.569 align:start position:0% in the name system as well and this is just<00:10:21.259> kind<00:10:21.350> of<00:10:21.559> a<00:10:21.620> trade<00:10:21.860> off<00:10:21.889> in<00:10:22.220> terms<00:10:22.370> of 00:10:22.569 --> 00:10:22.579 align:start position:0% just kind of a trade off in terms of 00:10:22.579 --> 00:10:24.280 align:start position:0% just kind of a trade off in terms of what<00:10:22.730> the<00:10:22.879> name<00:10:23.059> system<00:10:23.240> specific<00:10:24.110> name 00:10:24.280 --> 00:10:24.290 align:start position:0% what the name system specific name 00:10:24.290 --> 00:10:28.809 align:start position:0% what the name system specific name system<00:10:24.879> supports<00:10:26.350> so<00:10:27.350> it<00:10:28.309> could<00:10:28.550> be<00:10:28.579> a<00:10:28.639> very 00:10:28.809 --> 00:10:28.819 align:start position:0% system supports so it could be a very 00:10:28.819 --> 00:10:29.920 align:start position:0% system supports so it could be a very small<00:10:28.910> one<00:10:29.209> in<00:10:29.360> which<00:10:29.480> case<00:10:29.660> you<00:10:29.779> can't 00:10:29.920 --> 00:10:29.930 align:start position:0% small one in which case you can't 00:10:29.930 --> 00:10:32.590 align:start position:0% small one in which case you can't actually<00:10:30.079> embedded<00:10:30.470> content<00:10:30.879> and<00:10:31.879> then<00:10:32.300> the 00:10:32.590 --> 00:10:32.600 align:start position:0% actually embedded content and then the 00:10:32.600 --> 00:10:33.840 align:start position:0% actually embedded content and then the trade<00:10:32.809> office<00:10:33.079> if<00:10:33.230> you<00:10:33.319> want<00:10:33.439> to<00:10:33.559> sort<00:10:33.709> of 00:10:33.840 --> 00:10:33.850 align:start position:0% trade office if you want to sort of 00:10:33.850 --> 00:10:35.980 align:start position:0% trade office if you want to sort of traverse<00:10:34.850> the<00:10:35.029> linked<00:10:35.240> list<00:10:35.269> and<00:10:35.569> to<00:10:35.779> go<00:10:35.959> to 00:10:35.980 --> 00:10:35.990 align:start position:0% traverse the linked list and to go to 00:10:35.990 --> 00:10:39.460 align:start position:0% traverse the linked list and to go to the<00:10:36.230> cast<00:10:36.620> multiple<00:10:37.040> times<00:10:37.220> and<00:10:37.399> so<00:10:37.490> on<00:10:38.470> this 00:10:39.460 --> 00:10:39.470 align:start position:0% the cast multiple times and so on this 00:10:39.470 --> 00:10:42.040 align:start position:0% the cast multiple times and so on this is<00:10:39.529> sort<00:10:39.769> of<00:10:39.800> a<00:10:39.860> very<00:10:40.569> general<00:10:41.569> design<00:10:41.839> so<00:10:41.959> it 00:10:42.040 --> 00:10:42.050 align:start position:0% is sort of a very general design so it 00:10:42.050 --> 00:10:44.139 align:start position:0% is sort of a very general design so it works<00:10:42.259> it<00:10:42.529> works<00:10:42.889> swarm<00:10:43.399> it<00:10:43.610> works<00:10:43.790> with<00:10:43.970> I 00:10:44.139 --> 00:10:44.149 align:start position:0% works it works swarm it works with I 00:10:44.149 --> 00:10:45.999 align:start position:0% works it works swarm it works with I profess<00:10:44.509> and<00:10:44.720> also<00:10:45.319> works<00:10:45.589> sort<00:10:45.740> of<00:10:45.829> if<00:10:45.949> you 00:10:45.999 --> 00:10:46.009 align:start position:0% profess and also works sort of if you 00:10:46.009 --> 00:10:47.860 align:start position:0% profess and also works sort of if you want<00:10:46.129> to<00:10:46.189> have<00:10:46.279> it<00:10:46.399> on<00:10:46.459> a<00:10:46.550> USB<00:10:46.850> Drive<00:10:46.970> to<00:10:47.420> the 00:10:47.860 --> 00:10:47.870 align:start position:0% want to have it on a USB Drive to the 00:10:47.870 --> 00:10:49.780 align:start position:0% want to have it on a USB Drive to the backups<00:10:48.290> or<00:10:48.559> any<00:10:48.769> others<00:10:49.040> of<00:10:49.220> similar<00:10:49.429> thing 00:10:49.780 --> 00:10:49.790 align:start position:0% backups or any others of similar thing 00:10:49.790 --> 00:10:52.629 align:start position:0% backups or any others of similar thing that<00:10:49.939> implements<00:10:50.360> these<00:10:50.600> interfaces<00:10:51.639> in 00:10:52.629 --> 00:10:52.639 align:start position:0% that implements these interfaces in 00:10:52.639 --> 00:10:54.400 align:start position:0% that implements these interfaces in terms<00:10:52.850> of<00:10:52.939> privacy<00:10:53.179> properties<00:10:53.629> there's<00:10:54.079> this 00:10:54.400 --> 00:10:54.410 align:start position:0% terms of privacy properties there's this 00:10:54.410 --> 00:10:55.660 align:start position:0% terms of privacy properties there's this very<00:10:54.649> much<00:10:54.800> depends<00:10:55.189> on<00:10:55.309> the<00:10:55.519> underlying 00:10:55.660 --> 00:10:55.670 align:start position:0% very much depends on the underlying 00:10:55.670 --> 00:10:58.600 align:start position:0% very much depends on the underlying casts<00:10:56.629> so<00:10:57.110> if<00:10:57.470> you<00:10:57.860> have<00:10:57.949> for<00:10:58.069> example<00:10:58.129> a<00:10:58.370> mixed 00:10:58.600 --> 00:10:58.610 align:start position:0% casts so if you have for example a mixed 00:10:58.610 --> 00:11:02.559 align:start position:0% casts so if you have for example a mixed in<00:10:58.699> it<00:10:58.759> and<00:10:58.999> you<00:10:59.120> do<00:11:00.279> posts<00:11:01.279> or<00:11:01.490> gets<00:11:02.120> through 00:11:02.559 --> 00:11:02.569 align:start position:0% in it and you do posts or gets through 00:11:02.569 --> 00:11:04.809 align:start position:0% in it and you do posts or gets through the<00:11:02.689> mix<00:11:02.870> net<00:11:03.079> then<00:11:03.980> you<00:11:04.100> actually<00:11:04.339> get<00:11:04.550> send 00:11:04.809 --> 00:11:04.819 align:start position:0% the mix net then you actually get send 00:11:04.819 --> 00:11:07.299 align:start position:0% the mix net then you actually get send and<00:11:04.970> receive<00:11:05.209> anonymity<00:11:05.569> that<00:11:05.689> way<00:11:06.160> you<00:11:07.160> can 00:11:07.299 --> 00:11:07.309 align:start position:0% and receive anonymity that way you can 00:11:07.309 --> 00:11:08.799 align:start position:0% and receive anonymity that way you can also<00:11:07.429> do<00:11:07.639> other<00:11:07.939> things<00:11:08.240> like<00:11:08.480> you<00:11:08.600> can 00:11:08.799 --> 00:11:08.809 align:start position:0% also do other things like you can 00:11:08.809 --> 00:11:10.929 align:start position:0% also do other things like you can ratchet<00:11:09.110> the<00:11:09.769> name<00:11:10.160> system<00:11:10.309> so<00:11:10.610> you<00:11:10.699> change 00:11:10.929 --> 00:11:10.939 align:start position:0% ratchet the name system so you change 00:11:10.939 --> 00:11:12.220 align:start position:0% ratchet the name system so you change the<00:11:11.120> location<00:11:11.209> of<00:11:11.660> it 00:11:12.220 --> 00:11:12.230 align:start position:0% the location of it 00:11:12.230 --> 00:11:15.280 align:start position:0% the location of it kind<00:11:12.589> of<00:11:12.680> like<00:11:13.010> how<00:11:13.279> you<00:11:13.610> do<00:11:13.730> ratcheting<00:11:14.209> in<00:11:14.420> so 00:11:15.280 --> 00:11:15.290 align:start position:0% kind of like how you do ratcheting in so 00:11:15.290 --> 00:11:19.810 align:start position:0% kind of like how you do ratcheting in so forward<00:11:15.620> secrecy<00:11:15.769> schemes<00:11:16.190> and<00:11:16.370> so<00:11:16.459> on<00:11:18.820> Dean 00:11:19.810 --> 00:11:19.820 align:start position:0% forward secrecy schemes and so on Dean 00:11:19.820 --> 00:11:21.100 align:start position:0% forward secrecy schemes and so on Dean will<00:11:19.940> talk<00:11:20.060> a<00:11:20.089> bit<00:11:20.209> about<00:11:20.240> how<00:11:20.750> we<00:11:20.810> achieve 00:11:21.100 --> 00:11:21.110 align:start position:0% will talk a bit about how we achieve 00:11:21.110 --> 00:11:22.870 align:start position:0% will talk a bit about how we achieve certain<00:11:21.560> cuz<00:11:21.709> this<00:11:21.860> is<00:11:21.980> e<00:11:22.100> Kennedy's<00:11:22.579> with<00:11:22.790> the 00:11:22.870 --> 00:11:22.880 align:start position:0% certain cuz this is e Kennedy's with the 00:11:22.880 --> 00:11:26.079 align:start position:0% certain cuz this is e Kennedy's with the metadata<00:11:23.149> format<00:11:23.649> yeah<00:11:24.649> so<00:11:25.100> a<00:11:25.130> problem<00:11:25.610> of<00:11:25.850> all 00:11:26.079 --> 00:11:26.089 align:start position:0% metadata format yeah so a problem of all 00:11:26.089 --> 00:11:28.420 align:start position:0% metadata format yeah so a problem of all this<00:11:26.240> messaging<00:11:26.720> stuff<00:11:26.959> is<00:11:27.170> that<00:11:27.430> messages 00:11:28.420 --> 00:11:28.430 align:start position:0% this messaging stuff is that messages 00:11:28.430 --> 00:11:30.790 align:start position:0% this messaging stuff is that messages are<00:11:28.550> usually<00:11:28.850> related<00:11:29.329> and<00:11:29.540> so<00:11:29.870> we<00:11:30.050> need<00:11:30.199> some 00:11:30.790 --> 00:11:30.800 align:start position:0% are usually related and so we need some 00:11:30.800 --> 00:11:32.769 align:start position:0% are usually related and so we need some way<00:11:30.980> to<00:11:31.010> provide<00:11:31.730> some<00:11:32.000> form<00:11:32.149> of<00:11:32.269> consistency 00:11:32.769 --> 00:11:32.779 align:start position:0% way to provide some form of consistency 00:11:32.779 --> 00:11:35.199 align:start position:0% way to provide some form of consistency to<00:11:32.930> these<00:11:33.199> messages<00:11:33.699> so<00:11:34.699> we<00:11:34.820> need<00:11:34.940> to<00:11:35.029> be<00:11:35.120> able 00:11:35.199 --> 00:11:35.209 align:start position:0% to these messages so we need to be able 00:11:35.209 --> 00:11:37.300 align:start position:0% to these messages so we need to be able to<00:11:35.329> provide<00:11:35.779> ordering<00:11:36.380> amongst<00:11:37.070> various 00:11:37.300 --> 00:11:37.310 align:start position:0% to provide ordering amongst various 00:11:37.310 --> 00:11:40.150 align:start position:0% to provide ordering amongst various messages<00:11:37.850> not<00:11:38.149> only<00:11:38.389> a<00:11:38.990> linear<00:11:39.709> ordering 00:11:40.150 --> 00:11:40.160 align:start position:0% messages not only a linear ordering 00:11:40.160 --> 00:11:41.949 align:start position:0% messages not only a linear ordering through<00:11:40.459> my<00:11:40.610> messages<00:11:41.060> but<00:11:41.360> we<00:11:41.600> want<00:11:41.779> some 00:11:41.949 --> 00:11:41.959 align:start position:0% through my messages but we want some 00:11:41.959 --> 00:11:44.350 align:start position:0% through my messages but we want some kind<00:11:42.170> of<00:11:42.230> dag<00:11:42.529> if<00:11:42.860> I'm<00:11:43.339> in<00:11:43.519> a<00:11:43.610> conversation 00:11:44.350 --> 00:11:44.360 align:start position:0% kind of dag if I'm in a conversation 00:11:44.360 --> 00:11:46.509 align:start position:0% kind of dag if I'm in a conversation where<00:11:44.570> messages<00:11:45.320> are<00:11:45.529> linked<00:11:45.829> to<00:11:45.949> each<00:11:45.980> other 00:11:46.509 --> 00:11:46.519 align:start position:0% where messages are linked to each other 00:11:46.519 --> 00:11:48.759 align:start position:0% where messages are linked to each other to<00:11:46.820> show<00:11:47.029> what<00:11:47.060> is<00:11:47.420> the<00:11:47.540> what<00:11:47.959> message<00:11:48.290> depends 00:11:48.759 --> 00:11:48.769 align:start position:0% to show what is the what message depends 00:11:48.769 --> 00:11:51.610 align:start position:0% to show what is the what message depends on<00:11:48.920> what<00:11:49.130> message<00:11:49.839> so<00:11:50.839> here<00:11:51.320> we<00:11:51.410> have<00:11:51.529> an 00:11:51.610 --> 00:11:51.620 align:start position:0% on what message so here we have an 00:11:51.620 --> 00:11:54.759 align:start position:0% on what message so here we have an example<00:11:51.949> of<00:11:52.130> this<00:11:52.279> dag<00:11:52.579> where<00:11:53.120> what<00:11:54.079> we<00:11:54.529> want 00:11:54.759 --> 00:11:54.769 align:start position:0% example of this dag where what we want 00:11:54.769 --> 00:11:58.329 align:start position:0% example of this dag where what we want is<00:11:54.980> we<00:11:55.160> want<00:11:55.240> linear<00:11:56.470> lists<00:11:57.470> of<00:11:57.709> messages 00:11:58.329 --> 00:11:58.339 align:start position:0% is we want linear lists of messages 00:11:58.339 --> 00:12:00.310 align:start position:0% is we want linear lists of messages saying<00:11:58.639> I<00:11:58.880> sent<00:11:59.149> this<00:11:59.240> message<00:11:59.449> before<00:11:59.810> this 00:12:00.310 --> 00:12:00.320 align:start position:0% saying I sent this message before this 00:12:00.320 --> 00:12:01.210 align:start position:0% saying I sent this message before this is<00:12:00.440> the<00:12:00.589> next<00:12:00.860> message 00:12:01.210 --> 00:12:01.220 align:start position:0% is the next message 00:12:01.220 --> 00:12:03.639 align:start position:0% is the next message and<00:12:01.370> I<00:12:01.639> keep<00:12:01.850> linking<00:12:02.360> the<00:12:03.019> previous<00:12:03.470> message 00:12:03.639 --> 00:12:03.649 align:start position:0% and I keep linking the previous message 00:12:03.649 --> 00:12:05.740 align:start position:0% and I keep linking the previous message that<00:12:03.980> I<00:12:04.010> sent<00:12:04.339> but<00:12:05.029> what<00:12:05.180> we<00:12:05.300> then<00:12:05.420> also<00:12:05.570> start 00:12:05.740 --> 00:12:05.750 align:start position:0% that I sent but what we then also start 00:12:05.750 --> 00:12:08.319 align:start position:0% that I sent but what we then also start doing<00:12:06.260> is<00:12:06.380> we<00:12:06.500> start<00:12:06.800> linking<00:12:07.250> messages<00:12:08.180> that 00:12:08.319 --> 00:12:08.329 align:start position:0% doing is we start linking messages that 00:12:08.329 --> 00:12:10.389 align:start position:0% doing is we start linking messages that other<00:12:08.480> people<00:12:08.839> have<00:12:08.959> sent<00:12:09.230> me<00:12:09.290> so<00:12:09.740> I<00:12:09.769> start 00:12:10.389 --> 00:12:10.399 align:start position:0% other people have sent me so I start 00:12:10.399 --> 00:12:13.000 align:start position:0% other people have sent me so I start linking<00:12:10.760> the<00:12:11.209> last<00:12:11.449> seen<00:12:11.779> message<00:12:12.230> that<00:12:12.889> I've 00:12:13.000 --> 00:12:13.010 align:start position:0% linking the last seen message that I've 00:12:13.010 --> 00:12:16.090 align:start position:0% linking the last seen message that I've received<00:12:13.190> into<00:12:14.290> the<00:12:15.290> next<00:12:15.589> message<00:12:15.860> that<00:12:16.010> I'm 00:12:16.090 --> 00:12:16.100 align:start position:0% received into the next message that I'm 00:12:16.100 --> 00:12:19.000 align:start position:0% received into the next message that I'm gonna<00:12:16.190> send<00:12:16.990> and<00:12:17.990> additionally<00:12:18.620> what<00:12:18.769> we<00:12:18.890> can 00:12:19.000 --> 00:12:19.010 align:start position:0% gonna send and additionally what we can 00:12:19.010 --> 00:12:20.500 align:start position:0% gonna send and additionally what we can start<00:12:19.250> linking<00:12:19.550> in<00:12:19.670> is<00:12:19.790> we<00:12:19.910> can<00:12:20.029> start<00:12:20.209> linking 00:12:20.500 --> 00:12:20.510 align:start position:0% start linking in is we can start linking 00:12:20.510 --> 00:12:22.780 align:start position:0% start linking in is we can start linking in<00:12:20.630> things<00:12:20.839> like<00:12:20.930> remote<00:12:21.290> log<00:12:21.529> information<00:12:21.860> so 00:12:22.780 --> 00:12:22.790 align:start position:0% in things like remote log information so 00:12:22.790 --> 00:12:24.639 align:start position:0% in things like remote log information so that<00:12:22.820> when<00:12:23.420> we<00:12:23.630> go<00:12:23.810> to<00:12:23.839> this<00:12:24.079> log<00:12:24.350> we<00:12:24.529> know 00:12:24.639 --> 00:12:24.649 align:start position:0% that when we go to this log we know 00:12:24.649 --> 00:12:27.310 align:start position:0% that when we go to this log we know exactly<00:12:25.339> what<00:12:25.670> position<00:12:26.240> a<00:12:26.420> message<00:12:27.110> is 00:12:27.310 --> 00:12:27.320 align:start position:0% exactly what position a message is 00:12:27.320 --> 00:12:29.319 align:start position:0% exactly what position a message is placed<00:12:27.620> that<00:12:27.800> in<00:12:28.010> this<00:12:28.250> remote<00:12:28.490> log<00:12:28.760> so<00:12:29.300> that 00:12:29.319 --> 00:12:29.329 align:start position:0% placed that in this remote log so that 00:12:29.329 --> 00:12:31.030 align:start position:0% placed that in this remote log so that if<00:12:29.600> I've<00:12:29.779> missed<00:12:30.079> let's<00:12:30.440> say<00:12:30.589> 10<00:12:30.829> messages 00:12:31.030 --> 00:12:31.040 align:start position:0% if I've missed let's say 10 messages 00:12:31.040 --> 00:12:33.160 align:start position:0% if I've missed let's say 10 messages before<00:12:31.610> my<00:12:31.730> last<00:12:31.880> message<00:12:32.329> I<00:12:32.510> know<00:12:32.810> exactly 00:12:33.160 --> 00:12:33.170 align:start position:0% before my last message I know exactly 00:12:33.170 --> 00:12:35.790 align:start position:0% before my last message I know exactly which<00:12:33.470> page<00:12:33.829> to<00:12:33.860> go<00:12:34.190> to<00:12:34.250> and<00:12:34.610> from<00:12:35.180> which 00:12:35.790 --> 00:12:35.800 align:start position:0% which page to go to and from which 00:12:35.800 --> 00:12:38.199 align:start position:0% which page to go to and from which message<00:12:36.800> number<00:12:37.070> to<00:12:37.490> which<00:12:37.670> message<00:12:38.029> number 00:12:38.199 --> 00:12:38.209 align:start position:0% message number to which message number 00:12:38.209 --> 00:12:40.870 align:start position:0% message number to which message number to<00:12:38.839> sync<00:12:39.079> and<00:12:39.890> the<00:12:40.190> way<00:12:40.279> we<00:12:40.430> do<00:12:40.550> this<00:12:40.670> is 00:12:40.870 --> 00:12:40.880 align:start position:0% to sync and the way we do this is 00:12:40.880 --> 00:12:43.150 align:start position:0% to sync and the way we do this is relatively<00:12:41.269> easy<00:12:41.390> right<00:12:41.839> now<00:12:41.870> we<00:12:42.260> just<00:12:42.440> add<00:12:42.860> a 00:12:43.150 --> 00:12:43.160 align:start position:0% relatively easy right now we just add a 00:12:43.160 --> 00:12:45.819 align:start position:0% relatively easy right now we just add a protocol<00:12:43.820> buffer<00:12:44.149> essentially<00:12:44.660> to<00:12:45.380> the 00:12:45.819 --> 00:12:45.829 align:start position:0% protocol buffer essentially to the 00:12:45.829 --> 00:12:48.699 align:start position:0% protocol buffer essentially to the message<00:12:46.220> as<00:12:46.579> a<00:12:46.850> header<00:12:47.180> where<00:12:47.930> we<00:12:48.110> have<00:12:48.320> a 00:12:48.699 --> 00:12:48.709 align:start position:0% message as a header where we have a 00:12:48.709 --> 00:12:51.310 align:start position:0% message as a header where we have a repeated<00:12:49.339> byte<00:12:50.240> array<00:12:50.480> of<00:12:50.600> parents<00:12:51.050> which<00:12:51.199> is 00:12:51.310 --> 00:12:51.320 align:start position:0% repeated byte array of parents which is 00:12:51.320 --> 00:12:54.730 align:start position:0% repeated byte array of parents which is just<00:12:51.529> the<00:12:51.680> parent<00:12:52.250> IDs<00:12:52.579> of<00:12:52.899> messages<00:12:53.899> so<00:12:54.589> that 00:12:54.730 --> 00:12:54.740 align:start position:0% just the parent IDs of messages so that 00:12:54.740 --> 00:12:57.100 align:start position:0% just the parent IDs of messages so that would<00:12:54.890> be<00:12:55.010> like<00:12:55.190> messages<00:12:56.000> that<00:12:56.360> have<00:12:56.480> been<00:12:56.510> in 00:12:57.100 --> 00:12:57.110 align:start position:0% would be like messages that have been in 00:12:57.110 --> 00:12:59.710 align:start position:0% would be like messages that have been in this<00:12:57.529> group<00:12:57.769> context<00:12:58.430> before<00:12:58.819> my<00:12:59.329> message 00:12:59.710 --> 00:12:59.720 align:start position:0% this group context before my message 00:12:59.720 --> 00:13:01.720 align:start position:0% this group context before my message this<00:12:59.899> can<00:13:00.050> be<00:13:00.140> messages<00:13:00.589> I've<00:13:00.709> received<00:13:01.100> or 00:13:01.720 --> 00:13:01.730 align:start position:0% this can be messages I've received or 00:13:01.730 --> 00:13:03.790 align:start position:0% this can be messages I've received or messages<00:13:02.149> I've<00:13:02.300> sent<00:13:02.569> then<00:13:03.230> the<00:13:03.380> sequence 00:13:03.790 --> 00:13:03.800 align:start position:0% messages I've sent then the sequence 00:13:03.800 --> 00:13:05.590 align:start position:0% messages I've sent then the sequence number<00:13:04.160> that<00:13:04.399> is<00:13:04.490> the<00:13:04.610> one<00:13:04.760> which<00:13:04.910> relates<00:13:05.329> to 00:13:05.590 --> 00:13:05.600 align:start position:0% number that is the one which relates to 00:13:05.600 --> 00:13:09.370 align:start position:0% number that is the one which relates to the<00:13:06.230> actual<00:13:07.089> number<00:13:08.089> we're<00:13:08.240> seeing<00:13:08.600> on<00:13:08.930> the 00:13:09.370 --> 00:13:09.380 align:start position:0% the actual number we're seeing on the 00:13:09.380 --> 00:13:11.410 align:start position:0% the actual number we're seeing on the remote<00:13:09.680> log<00:13:09.920> and<00:13:10.250> then<00:13:10.790> we<00:13:10.880> have<00:13:11.029> something 00:13:11.410 --> 00:13:11.420 align:start position:0% remote log and then we have something 00:13:11.420 --> 00:13:13.480 align:start position:0% remote log and then we have something like<00:13:11.630> previous<00:13:12.380> message<00:13:12.860> which<00:13:13.040> is<00:13:13.160> my<00:13:13.310> last 00:13:13.480 --> 00:13:13.490 align:start position:0% like previous message which is my last 00:13:13.490 --> 00:13:15.699 align:start position:0% like previous message which is my last sent<00:13:13.790> message<00:13:14.149> and<00:13:14.779> additionally<00:13:15.410> we<00:13:15.589> also 00:13:15.699 --> 00:13:15.709 align:start position:0% sent message and additionally we also 00:13:15.709 --> 00:13:20.259 align:start position:0% sent message and additionally we also add<00:13:16.100> a<00:13:16.459> boolean<00:13:17.649> to<00:13:19.029> indicate<00:13:20.029> whether<00:13:20.180> a 00:13:20.259 --> 00:13:20.269 align:start position:0% add a boolean to indicate whether a 00:13:20.269 --> 00:13:22.540 align:start position:0% add a boolean to indicate whether a message<00:13:20.510> is<00:13:20.959> required<00:13:21.529> to<00:13:21.649> be<00:13:21.769> act<00:13:21.980> or<00:13:22.190> not<00:13:22.250> and 00:13:22.540 --> 00:13:22.550 align:start position:0% message is required to be act or not and 00:13:22.550 --> 00:13:24.850 align:start position:0% message is required to be act or not and this<00:13:23.120> is<00:13:23.360> important<00:13:23.899> for<00:13:23.959> things<00:13:24.319> like<00:13:24.560> user 00:13:24.850 --> 00:13:24.860 align:start position:0% this is important for things like user 00:13:24.860 --> 00:13:25.960 align:start position:0% this is important for things like user typing<00:13:25.279> notification 00:13:25.960 --> 00:13:25.970 align:start position:0% typing notification 00:13:25.970 --> 00:13:28.720 align:start position:0% typing notification or<00:13:26.240> that<00:13:26.360> a<00:13:26.389> user<00:13:26.660> came<00:13:26.930> online<00:13:27.550> those<00:13:28.550> are 00:13:28.720 --> 00:13:28.730 align:start position:0% or that a user came online those are 00:13:28.730 --> 00:13:31.540 align:start position:0% or that a user came online those are things<00:13:29.660> that<00:13:29.779> we<00:13:30.079> don't<00:13:30.199> need<00:13:30.379> to<00:13:30.439> really<00:13:31.160> be 00:13:31.540 --> 00:13:31.550 align:start position:0% things that we don't need to really be 00:13:31.550 --> 00:13:33.340 align:start position:0% things that we don't need to really be consistent<00:13:32.209> about<00:13:32.420> because<00:13:32.660> if<00:13:32.839> that<00:13:33.079> message 00:13:33.340 --> 00:13:33.350 align:start position:0% consistent about because if that message 00:13:33.350 --> 00:13:35.019 align:start position:0% consistent about because if that message gets<00:13:33.649> dropped<00:13:33.980> I<00:13:34.220> don't<00:13:34.370> really<00:13:34.490> care<00:13:34.730> I'm<00:13:34.879> not 00:13:35.019 --> 00:13:35.029 align:start position:0% gets dropped I don't really care I'm not 00:13:35.029 --> 00:13:36.670 align:start position:0% gets dropped I don't really care I'm not going<00:13:35.149> to<00:13:35.209> retransmit<00:13:35.509> that<00:13:35.959> those<00:13:36.439> are<00:13:36.589> like 00:13:36.670 --> 00:13:36.680 align:start position:0% going to retransmit that those are like 00:13:36.680 --> 00:13:38.590 align:start position:0% going to retransmit that those are like one-time<00:13:37.129> notifications<00:13:37.939> that<00:13:38.209> I'm<00:13:38.329> just 00:13:38.590 --> 00:13:38.600 align:start position:0% one-time notifications that I'm just 00:13:38.600 --> 00:13:40.749 align:start position:0% one-time notifications that I'm just gonna<00:13:38.720> send<00:13:39.050> out<00:13:39.199> and<00:13:39.439> if<00:13:39.560> if<00:13:39.980> it's<00:13:40.339> received 00:13:40.749 --> 00:13:40.759 align:start position:0% gonna send out and if if it's received 00:13:40.759 --> 00:13:43.030 align:start position:0% gonna send out and if if it's received that's<00:13:41.540> good<00:13:41.779> if<00:13:41.930> it's<00:13:42.079> not<00:13:42.230> received<00:13:42.680> I<00:13:42.889> don't 00:13:43.030 --> 00:13:43.040 align:start position:0% that's good if it's not received I don't 00:13:43.040 --> 00:13:44.619 align:start position:0% that's good if it's not received I don't really<00:13:43.189> care<00:13:43.430> because<00:13:43.550> it's<00:13:43.790> not<00:13:43.970> important 00:13:44.619 --> 00:13:44.629 align:start position:0% really care because it's not important 00:13:44.629 --> 00:13:47.470 align:start position:0% really care because it's not important to<00:13:45.110> the<00:13:45.230> actual<00:13:45.589> in<00:13:45.920> a<00:13:46.519> chat<00:13:46.970> context 00:13:47.470 --> 00:13:47.480 align:start position:0% to the actual in a chat context 00:13:47.480 --> 00:13:52.449 align:start position:0% to the actual in a chat context conversation<00:13:48.139> that<00:13:48.350> is<00:13:48.500> occurring<00:13:51.189> cool<00:13:52.189> so 00:13:52.449 --> 00:13:52.459 align:start position:0% conversation that is occurring cool so 00:13:52.459 --> 00:13:54.819 align:start position:0% conversation that is occurring cool so in<00:13:52.730> terms<00:13:52.939> of<00:13:53.319> problems<00:13:54.319> and<00:13:54.560> rough 00:13:54.819 --> 00:13:54.829 align:start position:0% in terms of problems and rough 00:13:54.829 --> 00:13:57.850 align:start position:0% in terms of problems and rough priorities<00:13:55.250> as<00:13:55.759> next<00:13:56.209> steps<00:13:56.300> so<00:13:57.139> our<00:13:57.560> initial 00:13:57.850 --> 00:13:57.860 align:start position:0% priorities as next steps so our initial 00:13:57.860 --> 00:13:59.319 align:start position:0% priorities as next steps so our initial focus<00:13:57.920> being<00:13:58.189> on<00:13:58.250> data<00:13:58.430> sync<00:13:58.730> there's<00:13:59.180> still 00:13:59.319 --> 00:13:59.329 align:start position:0% focus being on data sync there's still 00:13:59.329 --> 00:14:00.939 align:start position:0% focus being on data sync there's still some<00:13:59.480> things<00:13:59.629> we<00:13:59.839> have<00:13:59.870> to<00:13:59.990> improve<00:14:00.680> it 00:14:00.939 --> 00:14:00.949 align:start position:0% some things we have to improve it 00:14:00.949 --> 00:14:03.220 align:start position:0% some things we have to improve it specifically<00:14:01.730> in<00:14:01.850> terms<00:14:01.910> of<00:14:02.149> scalability<00:14:02.930> in 00:14:03.220 --> 00:14:03.230 align:start position:0% specifically in terms of scalability in 00:14:03.230 --> 00:14:05.259 align:start position:0% specifically in terms of scalability in semantics<00:14:03.680> for<00:14:03.949> sort<00:14:04.279> of<00:14:04.339> large<00:14:04.519> in<00:14:04.850> context 00:14:05.259 --> 00:14:05.269 align:start position:0% semantics for sort of large in context 00:14:05.269 --> 00:14:07.360 align:start position:0% semantics for sort of large in context so<00:14:05.509> many<00:14:06.019> imagine<00:14:06.439> if<00:14:06.529> you're<00:14:06.649> a<00:14:06.680> group<00:14:06.860> with<00:14:07.100> a 00:14:07.360 --> 00:14:07.370 align:start position:0% so many imagine if you're a group with a 00:14:07.370 --> 00:14:09.160 align:start position:0% so many imagine if you're a group with a faster<00:14:07.819> participants<00:14:08.360> you<00:14:08.720> want<00:14:08.899> to<00:14:08.959> reduce 00:14:09.160 --> 00:14:09.170 align:start position:0% faster participants you want to reduce 00:14:09.170 --> 00:14:11.199 align:start position:0% faster participants you want to reduce sort<00:14:09.410> of<00:14:09.500> the<00:14:10.339> chatter<00:14:10.579> and<00:14:10.759> sort<00:14:11.060> of<00:14:11.120> have 00:14:11.199 --> 00:14:11.209 align:start position:0% sort of the chatter and sort of have 00:14:11.209 --> 00:14:13.629 align:start position:0% sort of the chatter and sort of have efficient<00:14:11.600> joining<00:14:11.959> of<00:14:12.050> logs<00:14:12.589> so<00:14:13.040> you<00:14:13.459> don't 00:14:13.629 --> 00:14:13.639 align:start position:0% efficient joining of logs so you don't 00:14:13.639 --> 00:14:18.220 align:start position:0% efficient joining of logs so you don't overwhelmed<00:14:14.509> network<00:14:16.750> another<00:14:17.750> big<00:14:17.959> three 00:14:18.220 --> 00:14:18.230 align:start position:0% overwhelmed network another big three 00:14:18.230 --> 00:14:19.210 align:start position:0% overwhelmed network another big three priorities<00:14:18.620> in<00:14:18.709> terms<00:14:18.860> of<00:14:19.009> a<00:14:19.040> better 00:14:19.210 --> 00:14:19.220 align:start position:0% priorities in terms of a better 00:14:19.220 --> 00:14:22.269 align:start position:0% priorities in terms of a better transport<00:14:19.730> so<00:14:20.300> currently<00:14:20.569> we<00:14:20.750> use<00:14:21.279> whisper 00:14:22.269 --> 00:14:22.279 align:start position:0% transport so currently we use whisper 00:14:22.279 --> 00:14:23.769 align:start position:0% transport so currently we use whisper and<00:14:22.519> it<00:14:22.670> sort<00:14:22.879> of<00:14:22.910> has<00:14:23.060> a<00:14:23.089> lot<00:14:23.269> of<00:14:23.329> issues<00:14:23.480> when 00:14:23.769 --> 00:14:23.779 align:start position:0% and it sort of has a lot of issues when 00:14:23.779 --> 00:14:25.569 align:start position:0% and it sort of has a lot of issues when it<00:14:23.870> comes<00:14:23.990> to<00:14:24.110> scalability<00:14:24.680> and<00:14:24.920> it's<00:14:25.430> using 00:14:25.569 --> 00:14:25.579 align:start position:0% it comes to scalability and it's using 00:14:25.579 --> 00:14:27.939 align:start position:0% it comes to scalability and it's using proof-of-work<00:14:26.060> for<00:14:26.449> spam<00:14:26.990> resistance<00:14:27.410> what 00:14:27.939 --> 00:14:27.949 align:start position:0% proof-of-work for spam resistance what 00:14:27.949 --> 00:14:30.340 align:start position:0% proof-of-work for spam resistance what is<00:14:27.980> not<00:14:28.189> great<00:14:28.430> for<00:14:28.639> heterogeneous<00:14:29.350> devices 00:14:30.340 --> 00:14:30.350 align:start position:0% is not great for heterogeneous devices 00:14:30.350 --> 00:14:33.460 align:start position:0% is not great for heterogeneous devices or<00:14:30.620> nodes<00:14:30.829> because<00:14:31.389> your<00:14:32.389> phone<00:14:32.750> can<00:14:33.110> easily 00:14:33.460 --> 00:14:33.470 align:start position:0% or nodes because your phone can easily 00:14:33.470 --> 00:14:34.840 align:start position:0% or nodes because your phone can easily be<00:14:33.559> overwhelmed<00:14:33.769> by<00:14:34.009> someone<00:14:34.370> speeding<00:14:34.579> up<00:14:34.730> an 00:14:34.840 --> 00:14:34.850 align:start position:0% be overwhelmed by someone speeding up an 00:14:34.850 --> 00:14:37.480 align:start position:0% be overwhelmed by someone speeding up an EWS<00:14:35.300> node<00:14:35.509> and<00:14:35.750> it's<00:14:36.709> also<00:14:36.829> not<00:14:36.949> incentivized 00:14:37.480 --> 00:14:37.490 align:start position:0% EWS node and it's also not incentivized 00:14:37.490 --> 00:14:39.340 align:start position:0% EWS node and it's also not incentivized there's<00:14:37.730> no<00:14:37.850> reason<00:14:38.329> to<00:14:38.540> to<00:14:38.870> actually<00:14:39.170> run 00:14:39.340 --> 00:14:39.350 align:start position:0% there's no reason to to actually run 00:14:39.350 --> 00:14:40.569 align:start position:0% there's no reason to to actually run their<00:14:39.529> whisper<00:14:39.740> node<00:14:39.920> and<00:14:40.160> it<00:14:40.370> sort<00:14:40.550> of 00:14:40.569 --> 00:14:40.579 align:start position:0% their whisper node and it sort of 00:14:40.579 --> 00:14:43.030 align:start position:0% their whisper node and it sort of doesn't<00:14:40.879> map<00:14:41.059> cleanly<00:14:41.839> to<00:14:41.870> the<00:14:42.559> counting<00:14:42.949> of 00:14:43.030 --> 00:14:43.040 align:start position:0% doesn't map cleanly to the counting of 00:14:43.040 --> 00:14:44.829 align:start position:0% doesn't map cleanly to the counting of the<00:14:43.189> resources<00:14:43.670> that<00:14:43.790> you're<00:14:43.939> actually<00:14:44.120> sort 00:14:44.829 --> 00:14:44.839 align:start position:0% the resources that you're actually sort 00:14:44.839 --> 00:14:46.929 align:start position:0% the resources that you're actually sort of<00:14:44.870> consuming<00:14:45.350> and<00:14:45.470> so<00:14:45.559> on<00:14:45.680> so<00:14:46.550> that's<00:14:46.610> sort<00:14:46.910> of 00:14:46.929 --> 00:14:46.939 align:start position:0% of consuming and so on so that's sort of 00:14:46.939 --> 00:14:48.579 align:start position:0% of consuming and so on so that's sort of in<00:14:47.089> in<00:14:47.209> looking<00:14:47.689> at<00:14:47.899> various<00:14:48.170> alternatives 00:14:48.579 --> 00:14:48.589 align:start position:0% in in looking at various alternatives 00:14:48.589 --> 00:14:50.049 align:start position:0% in in looking at various alternatives and<00:14:48.800> it's<00:14:48.920> very<00:14:49.129> early<00:14:49.370> in<00:14:49.610> recent<00:14:49.910> stage 00:14:50.049 --> 00:14:50.059 align:start position:0% and it's very early in recent stage 00:14:50.059 --> 00:14:51.490 align:start position:0% and it's very early in recent stage right<00:14:50.269> now 00:14:51.490 --> 00:14:51.500 align:start position:0% right now 00:14:51.500 --> 00:14:53.710 align:start position:0% right now and<00:14:51.800> related<00:14:52.639> to<00:14:52.850> that<00:14:52.910> is<00:14:53.149> also<00:14:53.360> that<00:14:53.509> this 00:14:53.710 --> 00:14:53.720 align:start position:0% and related to that is also that this 00:14:53.720 --> 00:14:57.009 align:start position:0% and related to that is also that this sort<00:14:53.899> of<00:14:53.930> concept<00:14:54.139> of<00:14:54.379> adaptive<00:14:54.740> nodes<00:14:56.019> right 00:14:57.009 --> 00:14:57.019 align:start position:0% sort of concept of adaptive nodes right 00:14:57.019 --> 00:14:58.929 align:start position:0% sort of concept of adaptive nodes right now<00:14:57.170> you<00:14:57.230> have<00:14:57.439> generally<00:14:58.309> speaking<00:14:58.550> so<00:14:58.819> if 00:14:58.929 --> 00:14:58.939 align:start position:0% now you have generally speaking so if 00:14:58.939 --> 00:15:00.699 align:start position:0% now you have generally speaking so if this<00:14:59.120> this<00:14:59.899> thing<00:15:00.139> where<00:15:00.290> you<00:15:00.410> have<00:15:00.500> full 00:15:00.699 --> 00:15:00.709 align:start position:0% this this thing where you have full 00:15:00.709 --> 00:15:02.110 align:start position:0% this this thing where you have full nodes<00:15:00.920> that<00:15:01.160> are<00:15:01.279> participating<00:15:01.610> fully<00:15:02.000> in 00:15:02.110 --> 00:15:02.120 align:start position:0% nodes that are participating fully in 00:15:02.120 --> 00:15:03.910 align:start position:0% nodes that are participating fully in network<00:15:02.480> and<00:15:02.689> then<00:15:03.019> you<00:15:03.110> have<00:15:03.230> light<00:15:03.410> notes<00:15:03.680> or 00:15:03.910 --> 00:15:03.920 align:start position:0% network and then you have light notes or 00:15:03.920 --> 00:15:05.980 align:start position:0% network and then you have light notes or even<00:15:04.730> sort<00:15:04.850> of<00:15:04.910> gateways<00:15:05.300> that<00:15:05.720> are<00:15:05.809> kind<00:15:05.959> of 00:15:05.980 --> 00:15:05.990 align:start position:0% even sort of gateways that are kind of 00:15:05.990 --> 00:15:07.689 align:start position:0% even sort of gateways that are kind of like<00:15:06.050> leeches<00:15:06.410> and<00:15:06.860> and<00:15:07.220> you<00:15:07.279> know<00:15:07.399> don't 00:15:07.689 --> 00:15:07.699 align:start position:0% like leeches and and you know don't 00:15:07.699 --> 00:15:09.910 align:start position:0% like leeches and and you know don't actually<00:15:07.819> contribute<00:15:08.209> to<00:15:08.449> the<00:15:08.600> network<00:15:09.259> and 00:15:09.910 --> 00:15:09.920 align:start position:0% actually contribute to the network and 00:15:09.920 --> 00:15:12.309 align:start position:0% actually contribute to the network and we<00:15:09.980> think<00:15:10.160> this<00:15:10.220> is<00:15:10.339> a<00:15:10.370> bit<00:15:10.459> backwards<00:15:11.319> because 00:15:12.309 --> 00:15:12.319 align:start position:0% we think this is a bit backwards because 00:15:12.319 --> 00:15:14.170 align:start position:0% we think this is a bit backwards because if<00:15:12.529> you<00:15:12.589> look<00:15:12.709> at<00:15:12.800> sort<00:15:12.889> of<00:15:12.980> more<00:15:13.610> successful 00:15:14.170 --> 00:15:14.180 align:start position:0% if you look at sort of more successful 00:15:14.180 --> 00:15:17.439 align:start position:0% if you look at sort of more successful like<00:15:14.870> peer<00:15:15.529> to<00:15:15.649> peer<00:15:15.800> a<00:15:16.189> bit<00:15:16.699> torrent<00:15:16.939> as<00:15:17.329> an 00:15:17.439 --> 00:15:17.449 align:start position:0% like peer to peer a bit torrent as an 00:15:17.449 --> 00:15:18.699 align:start position:0% like peer to peer a bit torrent as an example<00:15:17.809> as<00:15:17.870> one<00:15:18.199> of<00:15:18.259> the<00:15:18.410> most<00:15:18.559> successful 00:15:18.699 --> 00:15:18.709 align:start position:0% example as one of the most successful 00:15:18.709 --> 00:15:21.009 align:start position:0% example as one of the most successful sort<00:15:19.220> of<00:15:19.279> peer<00:15:19.490> to<00:15:19.550> peer<00:15:19.639> deployments<00:15:20.149> you 00:15:21.009 --> 00:15:21.019 align:start position:0% sort of peer to peer deployments you 00:15:21.019 --> 00:15:22.960 align:start position:0% sort of peer to peer deployments you actually<00:15:21.680> always<00:15:21.920> everyone's<00:15:22.730> contributing 00:15:22.960 --> 00:15:22.970 align:start position:0% actually always everyone's contributing 00:15:22.970 --> 00:15:24.699 align:start position:0% actually always everyone's contributing to<00:15:23.540> the<00:15:23.629> network<00:15:23.959> and<00:15:24.079> health<00:15:24.230> of<00:15:24.319> a<00:15:24.410> network 00:15:24.699 --> 00:15:24.709 align:start position:0% to the network and health of a network 00:15:24.709 --> 00:15:27.429 align:start position:0% to the network and health of a network that's<00:15:25.069> a<00:15:25.220> very<00:15:25.370> nice<00:15:25.490> property<00:15:25.759> and<00:15:26.439> not 00:15:27.429 --> 00:15:27.439 align:start position:0% that's a very nice property and not 00:15:27.439 --> 00:15:29.079 align:start position:0% that's a very nice property and not everyone<00:15:27.800> will<00:15:27.949> all<00:15:28.160> nodes<00:15:28.519> will<00:15:28.670> be<00:15:28.790> able<00:15:28.910> to 00:15:29.079 --> 00:15:29.089 align:start position:0% everyone will all nodes will be able to 00:15:29.089 --> 00:15:31.179 align:start position:0% everyone will all nodes will be able to contribute<00:15:29.329> equally<00:15:29.720> but<00:15:30.230> you<00:15:30.829> sort<00:15:31.009> of<00:15:31.040> have 00:15:31.179 --> 00:15:31.189 align:start position:0% contribute equally but you sort of have 00:15:31.189 --> 00:15:33.970 align:start position:0% contribute equally but you sort of have the<00:15:31.309> option<00:15:31.639> to<00:15:31.759> do<00:15:31.850> that<00:15:32.680> and<00:15:33.680> it's<00:15:33.860> something 00:15:33.970 --> 00:15:33.980 align:start position:0% the option to do that and it's something 00:15:33.980 --> 00:15:35.590 align:start position:0% the option to do that and it's something that<00:15:34.189> swarm<00:15:34.519> is<00:15:34.639> also<00:15:34.880> working<00:15:35.059> on<00:15:35.269> this<00:15:35.449> sort 00:15:35.590 --> 00:15:35.600 align:start position:0% that swarm is also working on this sort 00:15:35.600 --> 00:15:37.419 align:start position:0% that swarm is also working on this sort of<00:15:35.630> idea<00:15:35.839> and<00:15:36.199> like<00:15:36.529> you<00:15:36.769> can<00:15:36.889> imagine<00:15:37.040> that<00:15:37.309> if 00:15:37.419 --> 00:15:37.429 align:start position:0% of idea and like you can imagine that if 00:15:37.429 --> 00:15:39.120 align:start position:0% of idea and like you can imagine that if you<00:15:37.519> have<00:15:37.639> a<00:15:37.670> mobile<00:15:38.120> phone<00:15:38.389> with 00:15:39.120 --> 00:15:39.130 align:start position:0% you have a mobile phone with 00:15:39.130 --> 00:15:41.920 align:start position:0% you have a mobile phone with limited<00:15:40.130> data<00:15:40.280> plan<00:15:40.520> you<00:15:40.940> probably<00:15:41.420> aren't 00:15:41.920 --> 00:15:41.930 align:start position:0% limited data plan you probably aren't 00:15:41.930 --> 00:15:44.410 align:start position:0% limited data plan you probably aren't gonna<00:15:42.440> contribute<00:15:43.310> a<00:15:43.340> network<00:15:43.700> so<00:15:44.150> you<00:15:44.210> might 00:15:44.410 --> 00:15:44.420 align:start position:0% gonna contribute a network so you might 00:15:44.420 --> 00:15:46.540 align:start position:0% gonna contribute a network so you might pay<00:15:44.600> for<00:15:44.630> through<00:15:44.930> some<00:15:45.080> other<00:15:45.200> means<00:15:45.550> but 00:15:46.540 --> 00:15:46.550 align:start position:0% pay for through some other means but 00:15:46.550 --> 00:15:49.750 align:start position:0% pay for through some other means but let's<00:15:47.090> say<00:15:47.240> that<00:15:47.270> you<00:15:47.450> you<00:15:48.050> have<00:15:48.290> a<00:15:48.610> you<00:15:49.610> come 00:15:49.750 --> 00:15:49.760 align:start position:0% let's say that you you have a you come 00:15:49.760 --> 00:15:51.490 align:start position:0% let's say that you you have a you come home<00:15:49.910> and<00:15:50.120> then<00:15:50.240> you<00:15:50.390> sort<00:15:50.570> of<00:15:50.630> plug<00:15:50.900> in<00:15:51.050> you 00:15:51.490 --> 00:15:51.500 align:start position:0% home and then you sort of plug in you 00:15:51.500 --> 00:15:53.080 align:start position:0% home and then you sort of plug in you use<00:15:51.710> Wi-Fi<00:15:52.010> and<00:15:52.400> you<00:15:52.460> plug<00:15:52.670> it<00:15:52.790> in<00:15:52.880> for 00:15:53.080 --> 00:15:53.090 align:start position:0% use Wi-Fi and you plug it in for 00:15:53.090 --> 00:15:54.730 align:start position:0% use Wi-Fi and you plug it in for charging<00:15:53.480> then<00:15:53.990> you<00:15:54.200> can<00:15:54.350> sort<00:15:54.470> of<00:15:54.500> start<00:15:54.590> to 00:15:54.730 --> 00:15:54.740 align:start position:0% charging then you can sort of start to 00:15:54.740 --> 00:15:56.590 align:start position:0% charging then you can sort of start to use<00:15:54.950> that<00:15:55.160> for<00:15:55.310> relaying<00:15:55.610> a<00:15:55.730> messages<00:15:56.090> or<00:15:56.450> if 00:15:56.590 --> 00:15:56.600 align:start position:0% use that for relaying a messages or if 00:15:56.600 --> 00:15:57.760 align:start position:0% use that for relaying a messages or if you<00:15:56.690> have<00:15:56.810> an<00:15:56.900> old<00:15:57.050> laptop<00:15:57.290> laying<00:15:57.680> around 00:15:57.760 --> 00:15:57.770 align:start position:0% you have an old laptop laying around 00:15:57.770 --> 00:15:59.190 align:start position:0% you have an old laptop laying around then<00:15:58.070> you<00:15:58.130> can<00:15:58.280> use<00:15:58.400> that<00:15:58.550> sort<00:15:58.760> of<00:15:58.820> store 00:15:59.190 --> 00:15:59.200 align:start position:0% then you can use that sort of store 00:15:59.200 --> 00:16:01.150 align:start position:0% then you can use that sort of store messages<00:16:00.200> and<00:16:00.350> help<00:16:00.500> the<00:16:00.590> network<00:16:00.830> that<00:16:00.980> way 00:16:01.150 --> 00:16:01.160 align:start position:0% messages and help the network that way 00:16:01.160 --> 00:16:03.610 align:start position:0% messages and help the network that way this<00:16:01.940> idea<00:16:02.210> for<00:16:02.450> creating<00:16:02.810> continuum<00:16:03.350> between 00:16:03.610 --> 00:16:03.620 align:start position:0% this idea for creating continuum between 00:16:03.620 --> 00:16:05.530 align:start position:0% this idea for creating continuum between sort<00:16:04.040> of<00:16:04.100> light<00:16:04.310> notes<00:16:04.550> and<00:16:04.730> full<00:16:04.910> notes<00:16:05.150> where 00:16:05.530 --> 00:16:05.540 align:start position:0% sort of light notes and full notes where 00:16:05.540 --> 00:16:07.420 align:start position:0% sort of light notes and full notes where you<00:16:05.840> sort<00:16:05.990> of<00:16:06.020> have<00:16:06.200> some<00:16:06.560> capabilities<00:16:07.220> and 00:16:07.420 --> 00:16:07.430 align:start position:0% you sort of have some capabilities and 00:16:07.430 --> 00:16:09.220 align:start position:0% you sort of have some capabilities and you<00:16:07.550> try<00:16:07.760> to<00:16:07.790> contribute<00:16:08.420> that<00:16:08.570> to<00:16:08.840> the 00:16:09.220 --> 00:16:09.230 align:start position:0% you try to contribute that to the 00:16:09.230 --> 00:16:10.630 align:start position:0% you try to contribute that to the network<00:16:09.590> sort<00:16:10.190> of<00:16:10.250> make<00:16:10.400> the<00:16:10.490> network 00:16:10.630 --> 00:16:10.640 align:start position:0% network sort of make the network 00:16:10.640 --> 00:16:13.320 align:start position:0% network sort of make the network stronger<00:16:11.120> we<00:16:12.110> think<00:16:12.320> this<00:16:12.470> does<00:16:12.770> some<00:16:12.950> sort<00:16:13.160> of 00:16:13.320 --> 00:16:13.330 align:start position:0% stronger we think this does some sort of 00:16:13.330 --> 00:16:15.610 align:start position:0% stronger we think this does some sort of something<00:16:14.330> we'll<00:16:14.570> look<00:16:14.930> into<00:16:15.200> him<00:16:15.320> we<00:16:15.410> would 00:16:15.610 --> 00:16:15.620 align:start position:0% something we'll look into him we would 00:16:15.620 --> 00:16:17.680 align:start position:0% something we'll look into him we would love<00:16:15.740> it<00:16:15.890> if<00:16:15.980> more<00:16:16.160> people<00:16:16.280> also<00:16:17.240> so<00:16:17.330> thinking 00:16:17.680 --> 00:16:17.690 align:start position:0% love it if more people also so thinking 00:16:17.690 --> 00:16:19.350 align:start position:0% love it if more people also so thinking in<00:16:17.750> these<00:16:17.840> terms<00:16:17.900> because<00:16:18.320> it<00:16:18.950> sort<00:16:19.220> of 00:16:19.350 --> 00:16:19.360 align:start position:0% in these terms because it sort of 00:16:19.360 --> 00:16:21.580 align:start position:0% in these terms because it sort of creates<00:16:20.360> for<00:16:20.540> a<00:16:20.570> better<00:16:20.720> network<00:16:20.930> in<00:16:21.230> general 00:16:21.580 --> 00:16:21.590 align:start position:0% creates for a better network in general 00:16:21.590 --> 00:16:23.260 align:start position:0% creates for a better network in general and<00:16:21.770> it<00:16:22.040> sort<00:16:22.220> of<00:16:22.250> also<00:16:22.430> more<00:16:22.730> in<00:16:22.940> line<00:16:23.120> with 00:16:23.260 --> 00:16:23.270 align:start position:0% and it sort of also more in line with 00:16:23.270 --> 00:16:25.180 align:start position:0% and it sort of also more in line with how<00:16:23.420> we<00:16:23.480> generate<00:16:24.350> sort<00:16:24.560> of<00:16:24.620> see<00:16:24.740> successful 00:16:25.180 --> 00:16:25.190 align:start position:0% how we generate sort of see successful 00:16:25.190 --> 00:16:27.460 align:start position:0% how we generate sort of see successful societies<00:16:25.790> and<00:16:26.000> systems<00:16:26.510> where<00:16:26.720> all<00:16:27.140> nodes 00:16:27.460 --> 00:16:27.470 align:start position:0% societies and systems where all nodes 00:16:27.470 --> 00:16:31.500 align:start position:0% societies and systems where all nodes contribute<00:16:27.920> to<00:16:28.010> the<00:16:28.070> extent<00:16:28.310> that<00:16:28.570> they<00:16:29.570> can 00:16:31.500 --> 00:16:31.510 align:start position:0% contribute to the extent that they can 00:16:31.510 --> 00:16:37.060 align:start position:0% contribute to the extent that they can so<00:16:32.830> yeah<00:16:33.830> that's<00:16:34.100> it<00:16:34.190> for<00:16:34.820> us<00:16:35.470> are<00:16:36.470> there<00:16:36.770> any 00:16:37.060 --> 00:16:37.070 align:start position:0% so yeah that's it for us are there any 00:16:37.070 --> 00:16:38.860 align:start position:0% so yeah that's it for us are there any questions<00:16:37.330> yeah<00:16:38.330> and<00:16:38.420> you<00:16:38.480> can<00:16:38.600> check<00:16:38.720> out 00:16:38.860 --> 00:16:38.870 align:start position:0% questions yeah and you can check out 00:16:38.870 --> 00:16:41.110 align:start position:0% questions yeah and you can check out these<00:16:39.160> websites<00:16:40.160> where<00:16:40.490> we<00:16:40.820> have<00:16:40.940> some 00:16:41.110 --> 00:16:41.120 align:start position:0% these websites where we have some 00:16:41.120 --> 00:16:43.000 align:start position:0% these websites where we have some research<00:16:41.330> logs<00:16:41.630> you<00:16:41.960> can<00:16:41.990> read<00:16:42.260> more<00:16:42.470> detail 00:16:43.000 --> 00:16:43.010 align:start position:0% research logs you can read more detail 00:16:43.010 --> 00:16:45.430 align:start position:0% research logs you can read more detail about<00:16:43.100> data<00:16:43.670> sink<00:16:43.970> remote<00:16:44.540> log<00:16:44.720> and<00:16:45.020> the 00:16:45.430 --> 00:16:45.440 align:start position:0% about data sink remote log and the 00:16:45.440 --> 00:16:47.140 align:start position:0% about data sink remote log and the general<00:16:45.710> stack<00:16:45.920> we<00:16:46.850> also<00:16:46.970> have 00:16:47.140 --> 00:16:47.150 align:start position:0% general stack we also have 00:16:47.150 --> 00:16:49.690 align:start position:0% general stack we also have specifications<00:16:47.660> and<00:16:48.650> yeah<00:16:49.370> feel<00:16:49.550> free<00:16:49.580> to 00:16:49.690 --> 00:16:49.700 align:start position:0% specifications and yeah feel free to 00:16:49.700 --> 00:17:03.090 align:start position:0% specifications and yeah feel free to reach<00:16:49.910> has<00:16:50.060> a<00:16:50.090> Twitter 00:17:03.090 --> 00:17:03.100 align:start position:0% 00:17:03.100 --> 00:17:06.600 align:start position:0% yes<00:17:03.220> a<00:17:03.490> drawer<00:17:04.260> there<00:17:05.260> is<00:17:05.440> a<00:17:05.650> for<00:17:06.190> invidious 00:17:06.600 --> 00:17:06.610 align:start position:0% yes a drawer there is a for invidious 00:17:06.610 --> 00:17:08.520 align:start position:0% yes a drawer there is a for invidious that<00:17:07.060> they're<00:17:07.210> solely<00:17:07.390> spec<00:17:07.750> and<00:17:08.080> it's<00:17:08.350> also 00:17:08.520 --> 00:17:08.530 align:start position:0% that they're solely spec and it's also 00:17:08.530 --> 00:17:10.020 align:start position:0% that they're solely spec and it's also in<00:17:08.710> there<00:17:08.890> its<00:17:09.190> status<00:17:09.520> version<00:17:09.760> one<00:17:09.880> app 00:17:10.020 --> 00:17:10.030 align:start position:0% in there its status version one app 00:17:10.030 --> 00:17:13.200 align:start position:0% in there its status version one app remote<00:17:11.020> remote<00:17:11.920> log<00:17:12.220> disrespect<00:17:12.730> improve 00:17:13.200 --> 00:17:13.210 align:start position:0% remote remote log disrespect improve 00:17:13.210 --> 00:17:16.140 align:start position:0% remote remote log disrespect improve concept<00:17:13.690> it's<00:17:13.840> still<00:17:14.260> not<00:17:14.440> deployed<00:17:14.770> in<00:17:15.150> ends 00:17:16.140 --> 00:17:16.150 align:start position:0% concept it's still not deployed in ends 00:17:16.150 --> 00:17:17.940 align:start position:0% concept it's still not deployed in ends of<00:17:16.300> the<00:17:16.420> app<00:17:16.510> and<00:17:16.810> then<00:17:17.140> the<00:17:17.260> other<00:17:17.380> other 00:17:17.940 --> 00:17:17.950 align:start position:0% of the app and then the other other 00:17:17.950 --> 00:17:19.650 align:start position:0% of the app and then the other other serve<00:17:18.310> products<00:17:18.700> are<00:17:18.820> still<00:17:19.180> serving<00:17:19.480> in 00:17:19.650 --> 00:17:19.660 align:start position:0% serve products are still serving in 00:17:19.660 --> 00:17:23.130 align:start position:0% serve products are still serving in various<00:17:20.350> research<00:17:20.680> data's<00:17:21.100> oh<00:17:22.050> and<00:17:23.050> the 00:17:23.130 --> 00:17:23.140 align:start position:0% various research data's oh and the 00:17:23.140 --> 00:17:25.740 align:start position:0% various research data's oh and the metadata<00:17:23.500> format<00:17:23.680> is<00:17:23.920> in<00:17:24.820> spec<00:17:25.210> and<00:17:25.510> proof<00:17:25.630> of 00:17:25.740 --> 00:17:25.750 align:start position:0% metadata format is in spec and proof of 00:17:25.750 --> 00:17:40.370 align:start position:0% metadata format is in spec and proof of concept<00:17:25.990> States<00:17:26.170> but<00:17:26.380> not<00:17:26.530> yet<00:17:26.800> in<00:17:26.830> in<00:17:27.460> app 00:17:40.370 --> 00:17:40.380 align:start position:0% 00:17:40.380 --> 00:17:45.300 align:start position:0% there<00:17:41.380> is<00:17:41.410> some<00:17:43.920> not<00:17:44.920> going<00:17:45.070> to<00:17:45.130> promise 00:17:45.300 --> 00:17:45.310 align:start position:0% there is some not going to promise 00:17:45.310 --> 00:17:46.710 align:start position:0% there is some not going to promise anything<00:17:45.550> because<00:17:45.790> that's<00:17:45.910> also<00:17:46.150> it's<00:17:46.420> a<00:17:46.540> free 00:17:46.710 --> 00:17:46.720 align:start position:0% anything because that's also it's a free 00:17:46.720 --> 00:17:48.150 align:start position:0% anything because that's also it's a free system<00:17:46.870> interesting<00:17:47.440> ideas<00:17:47.710> when<00:17:47.890> it<00:17:48.010> comes 00:17:48.150 --> 00:17:48.160 align:start position:0% system interesting ideas when it comes 00:17:48.160 --> 00:17:50.580 align:start position:0% system interesting ideas when it comes to<00:17:48.370> using<00:17:48.810> senior<00:17:49.810> knowledge<00:17:49.990> proofs<00:17:50.260> and<00:17:50.440> so 00:17:50.580 --> 00:17:50.590 align:start position:0% to using senior knowledge proofs and so 00:17:50.590 --> 00:17:52.320 align:start position:0% to using senior knowledge proofs and so on<00:17:50.710> where<00:17:50.920> you<00:17:51.040> can<00:17:51.220> sort<00:17:51.310> of<00:17:51.430> limit<00:17:52.060> it<00:17:52.180> that 00:17:52.320 --> 00:17:52.330 align:start position:0% on where you can sort of limit it that 00:17:52.330 --> 00:17:55.560 align:start position:0% on where you can sort of limit it that way<00:17:52.510> but<00:17:53.200> it's<00:17:53.680> it's<00:17:54.010> too<00:17:54.280> early<00:17:54.310> to<00:17:54.730> tell<00:17:54.970> if 00:17:55.560 --> 00:17:55.570 align:start position:0% way but it's it's too early to tell if 00:17:55.570 --> 00:17:57.240 align:start position:0% way but it's it's too early to tell if those<00:17:55.960> things<00:17:56.290> are<00:17:56.470> actually<00:17:56.650> will<00:17:56.980> actually 00:17:57.240 --> 00:17:57.250 align:start position:0% those things are actually will actually 00:17:57.250 --> 00:17:59.310 align:start position:0% those things are actually will actually work<00:17:57.310> out<00:17:57.460> so<00:17:57.610> we<00:17:57.670> still<00:17:57.850> need<00:17:58.060> to<00:17:58.210> yeah 00:17:59.310 --> 00:17:59.320 align:start position:0% work out so we still need to yeah 00:17:59.320 --> 00:18:00.870 align:start position:0% work out so we still need to yeah spend<00:17:59.680> more<00:17:59.830> time<00:17:59.890> on<00:18:00.130> that<00:18:00.280> essentially<00:18:00.700> I 00:18:00.870 --> 00:18:00.880 align:start position:0% spend more time on that essentially I 00:18:00.880 --> 00:18:02.310 align:start position:0% spend more time on that essentially I would<00:18:01.360> also<00:18:01.570> point<00:18:01.750> that<00:18:01.930> that<00:18:02.050> that's<00:18:02.230> a 00:18:02.310 --> 00:18:02.320 align:start position:0% would also point that that that's a 00:18:02.320 --> 00:18:04.410 align:start position:0% would also point that that that's a specific<00:18:02.770> thing<00:18:03.100> for<00:18:03.520> multi<00:18:03.880> cost<00:18:04.030> networks 00:18:04.410 --> 00:18:04.420 align:start position:0% specific thing for multi cost networks 00:18:04.420 --> 00:18:06.000 align:start position:0% specific thing for multi cost networks as<00:18:04.630> well<00:18:04.930> where<00:18:05.560> you<00:18:05.590> serve<00:18:05.800> have<00:18:05.920> this 00:18:06.000 --> 00:18:06.010 align:start position:0% as well where you serve have this 00:18:06.010 --> 00:18:08.820 align:start position:0% as well where you serve have this implication<00:18:06.430> factor<00:18:07.420> so<00:18:07.930> for<00:18:08.350> other<00:18:08.470> types<00:18:08.740> of 00:18:08.820 --> 00:18:08.830 align:start position:0% implication factor so for other types of 00:18:08.830 --> 00:18:10.980 align:start position:0% implication factor so for other types of networks<00:18:09.190> that<00:18:09.280> that<00:18:09.790> might<00:18:09.970> not<00:18:10.150> be<00:18:10.180> as<00:18:10.780> big 00:18:10.980 --> 00:18:10.990 align:start position:0% networks that that might not be as big 00:18:10.990 --> 00:18:16.050 align:start position:0% networks that that might not be as big of<00:18:11.020> a<00:18:11.140> problem<00:18:11.340> but<00:18:12.340> yeah<00:18:14.790> any<00:18:15.790> other 00:18:16.050 --> 00:18:16.060 align:start position:0% of a problem but yeah any other 00:18:16.060 --> 00:18:21.820 align:start position:0% of a problem but yeah any other questions<00:18:18.870> all<00:18:19.870> right<00:18:19.960> cool<00:18:20.320> thanks 00:18:21.820 --> 00:18:21.830 align:start position:0% questions all right cool thanks 00:18:21.830 --> 00:18:32.710 align:start position:0% questions all right cool thanks [Applause] 00:18:32.710 --> 00:18:32.720 align:start position:0% 00:18:32.720 --> 00:18:34.780 align:start position:0% you