WEBVTT Kind: captions Language: en 00:00:14.079 --> 00:00:16.870 align:start position:0% I'm<00:00:15.079> the<00:00:15.289> total<00:00:15.440> my<00:00:15.589> talk<00:00:15.769> was<00:00:15.950> scalable 00:00:16.870 --> 00:00:16.880 align:start position:0% I'm the total my talk was scalable 00:00:16.880 --> 00:00:19.780 align:start position:0% I'm the total my talk was scalable secure<00:00:17.090> scuttlebutt<00:00:18.280> my<00:00:19.280> name<00:00:19.430> and<00:00:19.580> my<00:00:19.670> name 00:00:19.780 --> 00:00:19.790 align:start position:0% secure scuttlebutt my name and my name 00:00:19.790 --> 00:00:22.030 align:start position:0% secure scuttlebutt my name and my name is<00:00:19.850> Dominic<00:00:20.090> tower<00:00:20.300> um<00:00:20.600> so<00:00:21.350> what<00:00:21.920> is 00:00:22.030 --> 00:00:22.040 align:start position:0% is Dominic tower um so what is 00:00:22.040 --> 00:00:25.420 align:start position:0% is Dominic tower um so what is scuttlebutt<00:00:22.400> scuttlebutt<00:00:23.320> the<00:00:24.320> -<00:00:24.620> so-so 00:00:25.420 --> 00:00:25.430 align:start position:0% scuttlebutt scuttlebutt the - so-so 00:00:25.430 --> 00:00:27.970 align:start position:0% scuttlebutt scuttlebutt the - so-so scuttlebutt<00:00:26.390> is<00:00:26.450> a<00:00:26.570> nautical<00:00:26.900> term<00:00:27.440> for 00:00:27.970 --> 00:00:27.980 align:start position:0% scuttlebutt is a nautical term for 00:00:27.980 --> 00:00:31.660 align:start position:0% scuttlebutt is a nautical term for gossip<00:00:28.370> a<00:00:28.540> but<00:00:29.540> there's<00:00:30.080> a<00:00:30.140> barrel<00:00:30.620> that<00:00:31.400> water 00:00:31.660 --> 00:00:31.670 align:start position:0% gossip a but there's a barrel that water 00:00:31.670 --> 00:00:34.000 align:start position:0% gossip a but there's a barrel that water is<00:00:31.880> stored<00:00:32.090> and<00:00:32.480> scuttle<00:00:33.020> is<00:00:33.230> to<00:00:33.590> open<00:00:33.770> the 00:00:34.000 --> 00:00:34.010 align:start position:0% is stored and scuttle is to open the 00:00:34.010 --> 00:00:36.310 align:start position:0% is stored and scuttle is to open the barrel<00:00:34.370> so<00:00:35.030> it's<00:00:35.390> to<00:00:35.510> make<00:00:35.630> a<00:00:35.660> hole<00:00:35.840> in<00:00:35.990> it<00:00:36.110> so 00:00:36.310 --> 00:00:36.320 align:start position:0% barrel so it's to make a hole in it so 00:00:36.320 --> 00:00:38.020 align:start position:0% barrel so it's to make a hole in it so this<00:00:36.530> why<00:00:36.710> scuttle<00:00:37.100> is<00:00:37.250> also<00:00:37.520> distinct<00:00:37.790> ership 00:00:38.020 --> 00:00:38.030 align:start position:0% this why scuttle is also distinct ership 00:00:38.030 --> 00:00:46.150 align:start position:0% this why scuttle is also distinct ership because<00:00:38.570> you<00:00:38.660> open<00:00:38.990> the<00:00:39.110> dish<00:00:39.530> up<00:00:39.710> so<00:00:43.840> the<00:00:45.160> yeah 00:00:46.150 --> 00:00:46.160 align:start position:0% because you open the dish up so the yeah 00:00:46.160 --> 00:00:48.310 align:start position:0% because you open the dish up so the yeah so<00:00:46.399> this<00:00:46.760> means<00:00:46.940> gossip<00:00:47.300> for<00:00:47.600> pirates<00:00:48.230> and 00:00:48.310 --> 00:00:48.320 align:start position:0% so this means gossip for pirates and 00:00:48.320 --> 00:00:51.280 align:start position:0% so this means gossip for pirates and stuff<00:00:48.470> like<00:00:48.590> this<00:00:48.680> so<00:00:49.160> and<00:00:49.970> that<00:00:50.720> I<00:00:51.050> got<00:00:51.170> the 00:00:51.280 --> 00:00:51.290 align:start position:0% stuff like this so and that I got the 00:00:51.290 --> 00:00:56.229 align:start position:0% stuff like this so and that I got the term<00:00:51.500> from<00:00:52.010> a<00:00:53.620> part<00:00:54.620> of<00:00:54.710> the<00:00:54.980> Amazon<00:00:55.239> paper 00:00:56.229 --> 00:00:56.239 align:start position:0% term from a part of the Amazon paper 00:00:56.239 --> 00:00:58.150 align:start position:0% term from a part of the Amazon paper there<00:00:56.540> was<00:00:56.630> a<00:00:56.690> it<00:00:57.380> was<00:00:57.530> on<00:00:57.590> paper<00:00:57.739> called<00:00:57.980> flow 00:00:58.150 --> 00:00:58.160 align:start position:0% there was a it was on paper called flow 00:00:58.160 --> 00:01:00.100 align:start position:0% there was a it was on paper called flow control<00:00:58.550> for<00:00:58.670> anti<00:00:58.880> entropy<00:00:59.239> projects<00:00:59.840> it's 00:01:00.100 --> 00:01:00.110 align:start position:0% control for anti entropy projects it's 00:01:00.110 --> 00:01:02.650 align:start position:0% control for anti entropy projects it's like<00:01:00.260> for<00:01:00.739> anti<00:01:00.980> in<00:01:01.130> entropy<00:01:01.670> protocols 00:01:02.650 --> 00:01:02.660 align:start position:0% like for anti in entropy protocols 00:01:02.660 --> 00:01:04.860 align:start position:0% like for anti in entropy protocols so<00:01:02.930> it's<00:01:03.050> eventually<00:01:03.410> consistent<00:01:03.820> gossip 00:01:04.860 --> 00:01:04.870 align:start position:0% so it's eventually consistent gossip 00:01:04.870 --> 00:01:06.640 align:start position:0% so it's eventually consistent gossip protocol<00:01:05.870> that's<00:01:06.110> used<00:01:06.200> to<00:01:06.409> a<00:01:06.470> thorough 00:01:06.640 --> 00:01:06.650 align:start position:0% protocol that's used to a thorough 00:01:06.650 --> 00:01:11.080 align:start position:0% protocol that's used to a thorough trusted<00:01:07.100> system<00:01:07.900> and<00:01:08.900> then<00:01:09.290> I<00:01:09.620> made<00:01:10.520> secure 00:01:11.080 --> 00:01:11.090 align:start position:0% trusted system and then I made secure 00:01:11.090 --> 00:01:13.300 align:start position:0% trusted system and then I made secure scuttlebutt<00:01:11.600> which<00:01:12.170> took<00:01:12.470> the<00:01:12.620> same<00:01:12.770> idea<00:01:12.890> and 00:01:13.300 --> 00:01:13.310 align:start position:0% scuttlebutt which took the same idea and 00:01:13.310 --> 00:01:17.649 align:start position:0% scuttlebutt which took the same idea and then<00:01:13.760> added<00:01:14.030> security<00:01:14.390> so<00:01:15.220> the<00:01:16.220> peer<00:01:16.520> that<00:01:17.270> ID 00:01:17.649 --> 00:01:17.659 align:start position:0% then added security so the peer that ID 00:01:17.659 --> 00:01:20.469 align:start position:0% then added security so the peer that ID of<00:01:17.900> the<00:01:18.020> peer<00:01:18.229> is<00:01:18.440> the<00:01:18.710> of<00:01:19.430> is<00:01:19.850> its<00:01:20.000> public<00:01:20.330> key 00:01:20.469 --> 00:01:20.479 align:start position:0% of the peer is the of is its public key 00:01:20.479 --> 00:01:23.200 align:start position:0% of the peer is the of is its public key the<00:01:21.290> data<00:01:21.500> model<00:01:21.830> is<00:01:22.010> just<00:01:22.340> append-only<00:01:22.700> logs 00:01:23.200 --> 00:01:23.210 align:start position:0% the data model is just append-only logs 00:01:23.210 --> 00:01:26.590 align:start position:0% the data model is just append-only logs where<00:01:24.140> each<00:01:24.400> peer<00:01:25.400> appeals<00:01:26.060> to<00:01:26.270> it<00:01:26.330> has<00:01:26.450> its 00:01:26.590 --> 00:01:26.600 align:start position:0% where each peer appeals to it has its 00:01:26.600 --> 00:01:29.830 align:start position:0% where each peer appeals to it has its own<00:01:26.780> personal<00:01:27.229> log<00:01:27.409> that<00:01:27.650> signed<00:01:28.630> peers<00:01:29.630> can 00:01:29.830 --> 00:01:29.840 align:start position:0% own personal log that signed peers can 00:01:29.840 --> 00:01:31.810 align:start position:0% own personal log that signed peers can relay<00:01:30.200> other<00:01:30.500> messages<00:01:31.010> but<00:01:31.340> they<00:01:31.369> can't 00:01:31.810 --> 00:01:31.820 align:start position:0% relay other messages but they can't 00:01:31.820 --> 00:01:34.719 align:start position:0% relay other messages but they can't insert<00:01:32.540> modify<00:01:33.110> or<00:01:33.439> reorder<00:01:33.799> messages 00:01:34.719 --> 00:01:34.729 align:start position:0% insert modify or reorder messages 00:01:34.729 --> 00:01:36.820 align:start position:0% insert modify or reorder messages because<00:01:35.450> the<00:01:35.930> signatures<00:01:36.350> would<00:01:36.500> then<00:01:36.680> be 00:01:36.820 --> 00:01:36.830 align:start position:0% because the signatures would then be 00:01:36.830 --> 00:01:42.550 align:start position:0% because the signatures would then be invalid<00:01:37.250> so<00:01:39.700> this<00:01:40.700> gives<00:01:41.210> you<00:01:41.390> like<00:01:41.840> a<00:01:41.869> really 00:01:42.550 --> 00:01:42.560 align:start position:0% invalid so this gives you like a really 00:01:42.560 --> 00:01:44.289 align:start position:0% invalid so this gives you like a really simple<00:01:42.680> data<00:01:43.010> model<00:01:43.100> they<00:01:43.760> can<00:01:43.909> use<00:01:44.270> to 00:01:44.289 --> 00:01:44.299 align:start position:0% simple data model they can use to 00:01:44.299 --> 00:01:46.480 align:start position:0% simple data model they can use to represent<00:01:44.780> a<00:01:45.080> bunch<00:01:45.380> of<00:01:45.560> stuff<00:01:45.770> but<00:01:45.799> it's<00:01:46.130> and 00:01:46.480 --> 00:01:46.490 align:start position:0% represent a bunch of stuff but it's and 00:01:46.490 --> 00:01:49.420 align:start position:0% represent a bunch of stuff but it's and it's<00:01:46.850> completely<00:01:47.210> like<00:01:47.600> free<00:01:48.049> to<00:01:49.009> run<00:01:49.159> like 00:01:49.420 --> 00:01:49.430 align:start position:0% it's completely like free to run like 00:01:49.430 --> 00:01:51.999 align:start position:0% it's completely like free to run like signatures<00:01:50.000> you<00:01:50.840> can<00:01:50.869> make<00:01:51.170> 12<00:01:51.560> you<00:01:51.920> know 00:01:51.999 --> 00:01:52.009 align:start position:0% signatures you can make 12 you know 00:01:52.009 --> 00:01:53.679 align:start position:0% signatures you can make 12 you know thousands<00:01:52.400> of<00:01:52.460> signatures<00:01:52.580> a<00:01:52.850> second<00:01:53.270> on<00:01:53.479> an 00:01:53.679 --> 00:01:53.689 align:start position:0% thousands of signatures a second on an 00:01:53.689 --> 00:01:55.719 align:start position:0% thousands of signatures a second on an ordinary<00:01:53.960> laptop<00:01:54.170> you<00:01:54.830> can<00:01:55.009> the<00:01:55.490> current 00:01:55.719 --> 00:01:55.729 align:start position:0% ordinary laptop you can the current 00:01:55.729 --> 00:01:58.359 align:start position:0% ordinary laptop you can the current implementation<00:01:55.970> can<00:01:56.659> receive<00:01:57.560> like<00:01:58.009> two 00:01:58.359 --> 00:01:58.369 align:start position:0% implementation can receive like two 00:01:58.369 --> 00:02:01.899 align:start position:0% implementation can receive like two thousand<00:01:58.790> messages<00:01:58.880> a<00:01:59.180> second<00:02:00.520> and<00:02:01.520> validate 00:02:01.899 --> 00:02:01.909 align:start position:0% thousand messages a second and validate 00:02:01.909 --> 00:02:04.649 align:start position:0% thousand messages a second and validate them<00:02:02.090> like<00:02:02.270> it's<00:02:02.450> it's<00:02:02.869> very<00:02:03.140> like<00:02:03.680> it's<00:02:04.310> not 00:02:04.649 --> 00:02:04.659 align:start position:0% them like it's it's very like it's not 00:02:04.659 --> 00:02:07.090 align:start position:0% them like it's it's very like it's not it<00:02:05.659> avoids<00:02:05.960> all<00:02:06.200> kinds<00:02:06.470> of<00:02:06.500> bottlenecks<00:02:06.920> that 00:02:07.090 --> 00:02:07.100 align:start position:0% it avoids all kinds of bottlenecks that 00:02:07.100 --> 00:02:08.589 align:start position:0% it avoids all kinds of bottlenecks that you<00:02:07.159> do<00:02:07.310> if<00:02:07.490> you<00:02:07.579> have<00:02:07.729> a<00:02:07.759> get<00:02:08.239> if<00:02:08.329> you<00:02:08.450> have<00:02:08.569> a 00:02:08.589 --> 00:02:08.599 align:start position:0% you do if you have a get if you have a 00:02:08.599 --> 00:02:13.990 align:start position:0% you do if you have a get if you have a consensus<00:02:09.049> layer<00:02:10.959> so<00:02:11.959> this<00:02:12.340> then<00:02:13.340> there's<00:02:13.940> a 00:02:13.990 --> 00:02:14.000 align:start position:0% consensus layer so this then there's a 00:02:14.000 --> 00:02:14.260 align:start position:0% consensus layer so this then there's a few 00:02:14.260 --> 00:02:14.270 align:start position:0% few 00:02:14.270 --> 00:02:17.890 align:start position:0% few it<00:02:14.720> Maps<00:02:14.990> quite<00:02:15.350> closely<00:02:15.590> to<00:02:16.240> social<00:02:17.240> media 00:02:17.890 --> 00:02:17.900 align:start position:0% it Maps quite closely to social media 00:02:17.900 --> 00:02:21.580 align:start position:0% it Maps quite closely to social media kind<00:02:18.350> of<00:02:18.470> models<00:02:18.710> like<00:02:20.230> Twitter<00:02:21.230> and<00:02:21.470> whatnot 00:02:21.580 --> 00:02:21.590 align:start position:0% kind of models like Twitter and whatnot 00:02:21.590 --> 00:02:24.280 align:start position:0% kind of models like Twitter and whatnot because<00:02:21.980> you<00:02:22.130> you<00:02:22.580> follow<00:02:22.940> the<00:02:23.660> feeds<00:02:23.960> that 00:02:24.280 --> 00:02:24.290 align:start position:0% because you you follow the feeds that 00:02:24.290 --> 00:02:26.890 align:start position:0% because you you follow the feeds that you<00:02:24.350> want<00:02:24.620> to<00:02:24.710> replicate<00:02:25.160> and<00:02:25.370> this<00:02:26.000> solves<00:02:26.840> a 00:02:26.890 --> 00:02:26.900 align:start position:0% you want to replicate and this solves a 00:02:26.900 --> 00:02:28.540 align:start position:0% you want to replicate and this solves a whole<00:02:27.020> bunch<00:02:27.170> of<00:02:27.230> neat<00:02:27.470> problems<00:02:27.860> so<00:02:28.070> this 00:02:28.540 --> 00:02:28.550 align:start position:0% whole bunch of neat problems so this 00:02:28.550 --> 00:02:31.090 align:start position:0% whole bunch of neat problems so this solves<00:02:28.790> civil<00:02:29.630> attack<00:02:29.900> because<00:02:30.290> the<00:02:30.500> human<00:02:30.800> it 00:02:31.090 --> 00:02:31.100 align:start position:0% solves civil attack because the human it 00:02:31.100 --> 00:02:32.590 align:start position:0% solves civil attack because the human it bubbles<00:02:31.610> up<00:02:31.670> to<00:02:31.760> the<00:02:31.880> human<00:02:32.150> layer<00:02:32.270> and<00:02:32.510> then 00:02:32.590 --> 00:02:32.600 align:start position:0% bubbles up to the human layer and then 00:02:32.600 --> 00:02:34.870 align:start position:0% bubbles up to the human layer and then they<00:02:32.690> just<00:02:32.840> unfollow<00:02:33.260> the<00:02:34.010> nose<00:02:34.490> they<00:02:34.700> don't 00:02:34.870 --> 00:02:34.880 align:start position:0% they just unfollow the nose they don't 00:02:34.880 --> 00:02:36.880 align:start position:0% they just unfollow the nose they don't want<00:02:35.000> to<00:02:35.120> talk<00:02:35.300> to<00:02:35.440> or<00:02:36.440> don't<00:02:36.590> want<00:02:36.650> to<00:02:36.740> hear 00:02:36.880 --> 00:02:36.890 align:start position:0% want to talk to or don't want to hear 00:02:36.890 --> 00:02:39.760 align:start position:0% want to talk to or don't want to hear from<00:02:37.060> it<00:02:38.060> also<00:02:38.180> provides<00:02:38.600> discovery<00:02:39.440> so 00:02:39.760 --> 00:02:39.770 align:start position:0% from it also provides discovery so 00:02:39.770 --> 00:02:43.120 align:start position:0% from it also provides discovery so writing<00:02:40.520> a<00:02:40.870> crappy<00:02:41.870> peer-to-peer<00:02:42.130> Google 00:02:43.120 --> 00:02:43.130 align:start position:0% writing a crappy peer-to-peer Google 00:02:43.130 --> 00:02:45.670 align:start position:0% writing a crappy peer-to-peer Google would<00:02:43.490> be<00:02:43.730> really<00:02:44.300> really<00:02:44.330> hard<00:02:44.660> but<00:02:45.380> writing 00:02:45.670 --> 00:02:45.680 align:start position:0% would be really really hard but writing 00:02:45.680 --> 00:02:48.720 align:start position:0% would be really really hard but writing a<00:02:46.270> crappy<00:02:47.270> peer-to-peer<00:02:47.450> social<00:02:48.170> network 00:02:48.720 --> 00:02:48.730 align:start position:0% a crappy peer-to-peer social network 00:02:48.730 --> 00:02:51.220 align:start position:0% a crappy peer-to-peer social network actually<00:02:49.730> can<00:02:50.300> still<00:02:50.510> be<00:02:50.600> really<00:02:50.750> awesome<00:02:50.990> if 00:02:51.220 --> 00:02:51.230 align:start position:0% actually can still be really awesome if 00:02:51.230 --> 00:02:53.470 align:start position:0% actually can still be really awesome if there<00:02:51.410> are<00:02:51.470> awesome<00:02:51.710> people<00:02:51.740> on<00:02:52.190> it<00:02:52.520> and<00:02:53.390> you 00:02:53.470 --> 00:02:53.480 align:start position:0% there are awesome people on it and you 00:02:53.480 --> 00:02:55.090 align:start position:0% there are awesome people on it and you can<00:02:53.780> still<00:02:53.990> discover<00:02:54.170> new<00:02:54.470> things<00:02:54.710> so<00:02:54.890> it's<00:02:55.040> a 00:02:55.090 --> 00:02:55.100 align:start position:0% can still discover new things so it's a 00:02:55.100 --> 00:02:56.950 align:start position:0% can still discover new things so it's a way<00:02:55.220> of<00:02:55.430> like<00:02:55.700> discovering<00:02:56.510> things<00:02:56.690> in<00:02:56.870> a 00:02:56.950 --> 00:02:56.960 align:start position:0% way of like discovering things in a 00:02:56.960 --> 00:02:58.780 align:start position:0% way of like discovering things in a decent<00:02:57.230> surance<00:02:57.590> new<00:02:57.680> decentralized<00:02:58.160> way<00:02:58.310> and 00:02:58.780 --> 00:02:58.790 align:start position:0% decent surance new decentralized way and 00:02:58.790 --> 00:03:00.850 align:start position:0% decent surance new decentralized way and then<00:02:59.750> because<00:02:59.990> it<00:03:00.110> replicates<00:03:00.560> misses<00:03:00.830> just 00:03:00.850 --> 00:03:00.860 align:start position:0% then because it replicates misses just 00:03:00.860 --> 00:03:03.670 align:start position:0% then because it replicates misses just an<00:03:01.100> order<00:03:01.780> it's<00:03:02.780> easy<00:03:03.080> to<00:03:03.290> think<00:03:03.410> about 00:03:03.670 --> 00:03:03.680 align:start position:0% an order it's easy to think about 00:03:03.680 --> 00:03:04.930 align:start position:0% an order it's easy to think about building<00:03:03.950> a<00:03:04.070> database<00:03:04.340> on<00:03:04.580> top<00:03:04.700> of<00:03:04.820> this 00:03:04.930 --> 00:03:04.940 align:start position:0% building a database on top of this 00:03:04.940 --> 00:03:08.020 align:start position:0% building a database on top of this because<00:03:05.120> the<00:03:05.680> things<00:03:06.680> happen<00:03:07.040> you<00:03:07.730> receive 00:03:08.020 --> 00:03:08.030 align:start position:0% because the things happen you receive 00:03:08.030 --> 00:03:09.100 align:start position:0% because the things happen you receive things<00:03:08.270> in<00:03:08.390> the<00:03:08.480> same<00:03:08.630> order<00:03:08.840> that<00:03:08.870> they 00:03:09.100 --> 00:03:09.110 align:start position:0% things in the same order that they 00:03:09.110 --> 00:03:12.820 align:start position:0% things in the same order that they happened<00:03:09.550> so<00:03:10.550> that<00:03:10.990> was<00:03:11.990> secure<00:03:12.350> Scott<00:03:12.590> Oberg 00:03:12.820 --> 00:03:12.830 align:start position:0% happened so that was secure Scott Oberg 00:03:12.830 --> 00:03:15.460 align:start position:0% happened so that was secure Scott Oberg and<00:03:13.070> then<00:03:13.700> my<00:03:14.270> recent<00:03:14.630> work<00:03:14.720> has<00:03:14.750> been<00:03:15.140> to<00:03:15.320> make 00:03:15.460 --> 00:03:15.470 align:start position:0% and then my recent work has been to make 00:03:15.470 --> 00:03:17.920 align:start position:0% and then my recent work has been to make it<00:03:15.500> much<00:03:15.980> much<00:03:16.220> more<00:03:16.430> scalable<00:03:16.670> so<00:03:17.420> scalable 00:03:17.920 --> 00:03:17.930 align:start position:0% it much much more scalable so scalable 00:03:17.930 --> 00:03:19.630 align:start position:0% it much much more scalable so scalable secure<00:03:18.110> scuttlebutt<00:03:18.770> is<00:03:18.950> the<00:03:19.280> same<00:03:19.460> thing 00:03:19.630 --> 00:03:19.640 align:start position:0% secure scuttlebutt is the same thing 00:03:19.640 --> 00:03:21.760 align:start position:0% secure scuttlebutt is the same thing again<00:03:19.910> but<00:03:20.090> optimized<00:03:20.930> for<00:03:21.140> bandwidth<00:03:21.530> and 00:03:21.760 --> 00:03:21.770 align:start position:0% again but optimized for bandwidth and 00:03:21.770 --> 00:03:25.690 align:start position:0% again but optimized for bandwidth and latency<00:03:23.020> so<00:03:24.020> the<00:03:24.200> the<00:03:24.800> big<00:03:24.980> deal<00:03:25.220> here<00:03:25.490> is<00:03:25.670> that 00:03:25.690 --> 00:03:25.700 align:start position:0% latency so the the big deal here is that 00:03:25.700 --> 00:03:28.030 align:start position:0% latency so the the big deal here is that the<00:03:25.970> overhead<00:03:26.420> the<00:03:26.930> networking<00:03:27.320> over<00:03:27.560> here<00:03:27.740> is 00:03:28.030 --> 00:03:28.040 align:start position:0% the overhead the networking over here is 00:03:28.040 --> 00:03:30.760 align:start position:0% the overhead the networking over here is proportional<00:03:28.910> to<00:03:29.180> the<00:03:29.510> feeds<00:03:29.780> updated<00:03:30.560> and 00:03:30.760 --> 00:03:30.770 align:start position:0% proportional to the feeds updated and 00:03:30.770 --> 00:03:36.340 align:start position:0% proportional to the feeds updated and I'll<00:03:31.580> explain<00:03:31.970> why<00:03:32.270> that's<00:03:32.420> important<00:03:32.960> so<00:03:35.350> so 00:03:36.340 --> 00:03:36.350 align:start position:0% I'll explain why that's important so so 00:03:36.350 --> 00:03:38.680 align:start position:0% I'll explain why that's important so so part<00:03:36.590> one<00:03:36.710> is<00:03:37.240> optimizing<00:03:38.240> the<00:03:38.420> network 00:03:38.680 --> 00:03:38.690 align:start position:0% part one is optimizing the network 00:03:38.690 --> 00:03:45.850 align:start position:0% part one is optimizing the network topology<00:03:39.400> so<00:03:40.400> the<00:03:42.190> the<00:03:43.840> like<00:03:44.840> simplest<00:03:45.290> most 00:03:45.850 --> 00:03:45.860 align:start position:0% topology so the the like simplest most 00:03:45.860 --> 00:03:47.800 align:start position:0% topology so the the like simplest most naive<00:03:46.130> design<00:03:46.490> would<00:03:46.820> be<00:03:46.880> just<00:03:47.360> to<00:03:47.480> connect<00:03:47.720> to 00:03:47.800 --> 00:03:47.810 align:start position:0% naive design would be just to connect to 00:03:47.810 --> 00:03:50.050 align:start position:0% naive design would be just to connect to everyone<00:03:48.310> and<00:03:49.310> I<00:03:49.370> have<00:03:49.520> really<00:03:49.910> cool 00:03:50.050 --> 00:03:50.060 align:start position:0% everyone and I have really cool 00:03:50.060 --> 00:03:51.930 align:start position:0% everyone and I have really cool animation<00:03:50.630> of<00:03:50.750> this<00:03:50.900> that<00:03:51.140> you<00:03:51.230> can't<00:03:51.470> see<00:03:51.710> but 00:03:51.930 --> 00:03:51.940 align:start position:0% animation of this that you can't see but 00:03:51.940 --> 00:03:55.360 align:start position:0% animation of this that you can't see but perhaps<00:03:52.940> I'll<00:03:53.090> just<00:03:53.120> like<00:03:53.510> I<00:03:53.870> don't<00:03:54.710> know<00:03:54.770> can 00:03:55.360 --> 00:03:55.370 align:start position:0% perhaps I'll just like I don't know can 00:03:55.370 --> 00:03:57.190 align:start position:0% perhaps I'll just like I don't know can see<00:03:55.610> you<00:03:55.730> wanna<00:03:55.880> see<00:03:56.030> something<00:03:56.990> kind<00:03:57.110> of 00:03:57.190 --> 00:03:57.200 align:start position:0% see you wanna see something kind of 00:03:57.200 --> 00:04:01.630 align:start position:0% see you wanna see something kind of happening<00:03:57.500> yeah<00:03:59.110> so<00:04:00.110> this<00:04:00.950> of<00:04:01.100> course<00:04:01.130> is<00:04:01.310> like 00:04:01.630 --> 00:04:01.640 align:start position:0% happening yeah so this of course is like 00:04:01.640 --> 00:04:03.940 align:start position:0% happening yeah so this of course is like inherently<00:04:02.000> centralized<00:04:02.930> it<00:04:03.200> goes<00:04:03.620> out<00:04:03.770> from 00:04:03.940 --> 00:04:03.950 align:start position:0% inherently centralized it goes out from 00:04:03.950 --> 00:04:04.960 align:start position:0% inherently centralized it goes out from one<00:04:04.070> point<00:04:04.280> but<00:04:04.520> it's<00:04:04.640> actually<00:04:04.910> really 00:04:04.960 --> 00:04:04.970 align:start position:0% one point but it's actually really 00:04:04.970 --> 00:04:09.390 align:start position:0% one point but it's actually really efficient<00:04:05.540> because<00:04:06.260> each<00:04:07.120> message<00:04:08.120> is 00:04:09.390 --> 00:04:09.400 align:start position:0% efficient because each message is 00:04:09.400 --> 00:04:12.970 align:start position:0% efficient because each message is transmitted<00:04:10.400> exactly<00:04:10.820> once<00:04:11.030> to<00:04:11.740> to<00:04:12.740> every 00:04:12.970 --> 00:04:12.980 align:start position:0% transmitted exactly once to to every 00:04:12.980 --> 00:04:15.400 align:start position:0% transmitted exactly once to to every node<00:04:13.160> so<00:04:13.490> the<00:04:14.090> amount<00:04:14.900> of<00:04:14.990> people<00:04:15.290> that 00:04:15.400 --> 00:04:15.410 align:start position:0% node so the amount of people that 00:04:15.410 --> 00:04:17.170 align:start position:0% node so the amount of people that receive<00:04:15.770> messages<00:04:16.160> is<00:04:16.280> exactly<00:04:16.640> the<00:04:16.820> same<00:04:17.000> as 00:04:17.170 --> 00:04:17.180 align:start position:0% receive messages is exactly the same as 00:04:17.180 --> 00:04:18.370 align:start position:0% receive messages is exactly the same as the<00:04:17.299> amount<00:04:17.420> of<00:04:17.570> messages<00:04:17.750> that<00:04:18.020> need<00:04:18.140> to<00:04:18.290> be 00:04:18.370 --> 00:04:18.380 align:start position:0% the amount of messages that need to be 00:04:18.380 --> 00:04:21.940 align:start position:0% the amount of messages that need to be their<00:04:18.799> assent<00:04:19.250> and<00:04:20.140> but<00:04:21.140> the<00:04:21.230> problem<00:04:21.500> is<00:04:21.620> this 00:04:21.940 --> 00:04:21.950 align:start position:0% their assent and but the problem is this 00:04:21.950 --> 00:04:23.380 align:start position:0% their assent and but the problem is this means<00:04:22.160> that<00:04:22.400> actually<00:04:22.550> there's<00:04:23.000> one<00:04:23.030> node 00:04:23.380 --> 00:04:23.390 align:start position:0% means that actually there's one node 00:04:23.390 --> 00:04:24.880 align:start position:0% means that actually there's one node that<00:04:23.540> does<00:04:23.690> all<00:04:23.870> the<00:04:24.050> work<00:04:24.080> and<00:04:24.500> all<00:04:24.650> the<00:04:24.740> other 00:04:24.880 --> 00:04:24.890 align:start position:0% that does all the work and all the other 00:04:24.890 --> 00:04:27.130 align:start position:0% that does all the work and all the other nodes<00:04:25.040> do<00:04:25.280> nearly<00:04:25.460> no<00:04:25.669> work<00:04:25.880> and<00:04:26.150> then<00:04:26.810> you 00:04:27.130 --> 00:04:27.140 align:start position:0% nodes do nearly no work and then you 00:04:27.140 --> 00:04:27.580 align:start position:0% nodes do nearly no work and then you know 00:04:27.580 --> 00:04:27.590 align:start position:0% know 00:04:27.590 --> 00:04:29.590 align:start position:0% know that's<00:04:28.010> you<00:04:28.639> know<00:04:28.760> you<00:04:28.940> know<00:04:29.060> about<00:04:29.180> you<00:04:29.480> know 00:04:29.590 --> 00:04:29.600 align:start position:0% that's you know you know about you know 00:04:29.600 --> 00:04:31.510 align:start position:0% that's you know you know about you know about<00:04:29.780> why<00:04:29.900> centralization<00:04:30.620> is<00:04:30.710> bad<00:04:30.889> so 00:04:31.510 --> 00:04:31.520 align:start position:0% about why centralization is bad so 00:04:31.520 --> 00:04:33.159 align:start position:0% about why centralization is bad so another<00:04:32.090> solution<00:04:32.270> is<00:04:32.690> you<00:04:32.840> just<00:04:33.020> have<00:04:33.139> a 00:04:33.159 --> 00:04:33.169 align:start position:0% another solution is you just have a 00:04:33.169 --> 00:04:35.560 align:start position:0% another solution is you just have a random<00:04:33.440> Network<00:04:33.950> just<00:04:34.490> peers<00:04:34.730> every<00:04:35.330> peer 00:04:35.560 --> 00:04:35.570 align:start position:0% random Network just peers every peer 00:04:35.570 --> 00:04:36.790 align:start position:0% random Network just peers every peer connects<00:04:36.020> to<00:04:36.139> a<00:04:36.169> couple<00:04:36.410> of<00:04:36.470> other<00:04:36.620> random 00:04:36.790 --> 00:04:36.800 align:start position:0% connects to a couple of other random 00:04:36.800 --> 00:04:39.760 align:start position:0% connects to a couple of other random nodes<00:04:37.160> and<00:04:38.050> it's<00:04:39.050> really<00:04:39.290> easy<00:04:39.440> to<00:04:39.530> make<00:04:39.650> a 00:04:39.760 --> 00:04:39.770 align:start position:0% nodes and it's really easy to make a 00:04:39.770 --> 00:04:41.890 align:start position:0% nodes and it's really easy to make a fully<00:04:40.070> connected<00:04:40.460> Network<00:04:40.520> like<00:04:40.970> this<00:04:41.000> like 00:04:41.890 --> 00:04:41.900 align:start position:0% fully connected Network like this like 00:04:41.900 --> 00:04:44.590 align:start position:0% fully connected Network like this like if<00:04:42.050> you<00:04:42.200> connect<00:04:42.590> to<00:04:42.860> more<00:04:43.040> than<00:04:43.190> two<00:04:43.610> peers<00:04:43.910> to 00:04:44.590 --> 00:04:44.600 align:start position:0% if you connect to more than two peers to 00:04:44.600 --> 00:04:46.210 align:start position:0% if you connect to more than two peers to other<00:04:44.810> peers<00:04:45.020> the<00:04:45.590> chance<00:04:45.860> of<00:04:46.040> being 00:04:46.210 --> 00:04:46.220 align:start position:0% other peers the chance of being 00:04:46.220 --> 00:04:48.700 align:start position:0% other peers the chance of being completely<00:04:46.669> connected<00:04:46.910> is<00:04:47.270> like<00:04:47.480> at<00:04:48.169> as<00:04:48.560> the 00:04:48.700 --> 00:04:48.710 align:start position:0% completely connected is like at as the 00:04:48.710 --> 00:04:50.980 align:start position:0% completely connected is like at as the network<00:04:48.919> gets<00:04:49.070> bigger<00:04:49.280> increases<00:04:50.120> so<00:04:50.419> once 00:04:50.980 --> 00:04:50.990 align:start position:0% network gets bigger increases so once 00:04:50.990 --> 00:04:52.540 align:start position:0% network gets bigger increases so once you're<00:04:51.110> past<00:04:51.260> oh<00:04:51.590> it's<00:04:51.980> like<00:04:52.100> the<00:04:52.190> chance<00:04:52.400> of 00:04:52.540 --> 00:04:52.550 align:start position:0% you're past oh it's like the chance of 00:04:52.550 --> 00:04:54.640 align:start position:0% you're past oh it's like the chance of being<00:04:52.700> fully<00:04:53.300> connected<00:04:53.630> this<00:04:53.750> like<00:04:53.960> pretty 00:04:54.640 --> 00:04:54.650 align:start position:0% being fully connected this like pretty 00:04:54.650 --> 00:04:57.820 align:start position:0% being fully connected this like pretty much<00:04:54.860> certain<00:04:55.070> and<00:04:56.200> but<00:04:57.200> the<00:04:57.320> problem<00:04:57.590> is<00:04:57.680> that 00:04:57.820 --> 00:04:57.830 align:start position:0% much certain and but the problem is that 00:04:57.830 --> 00:05:00.310 align:start position:0% much certain and but the problem is that it's<00:04:57.980> a<00:04:58.070> trade-off<00:04:58.370> between<00:04:59.200> bandwidth<00:05:00.200> and 00:05:00.310 --> 00:05:00.320 align:start position:0% it's a trade-off between bandwidth and 00:05:00.320 --> 00:05:01.600 align:start position:0% it's a trade-off between bandwidth and latency<00:05:00.440> depending<00:05:00.830> on<00:05:01.100> how<00:05:01.220> many<00:05:01.400> extra 00:05:01.600 --> 00:05:01.610 align:start position:0% latency depending on how many extra 00:05:01.610 --> 00:05:03.190 align:start position:0% latency depending on how many extra connections<00:05:02.090> you<00:05:02.210> have<00:05:02.240> so<00:05:02.900> I<00:05:02.930> have<00:05:03.050> another 00:05:03.190 --> 00:05:03.200 align:start position:0% connections you have so I have another 00:05:03.200 --> 00:05:09.070 align:start position:0% connections you have so I have another animation<00:05:03.979> here<00:05:04.340> so<00:05:07.330> it's<00:05:08.330> like<00:05:08.510> looks<00:05:08.900> like<00:05:08.960> a 00:05:09.070 --> 00:05:09.080 align:start position:0% animation here so it's like looks like a 00:05:09.080 --> 00:05:11.920 align:start position:0% animation here so it's like looks like a noisy<00:05:09.620> noisy<00:05:10.340> mess<00:05:10.520> and<00:05:10.820> then<00:05:11.150> you<00:05:11.510> might<00:05:11.660> say 00:05:11.920 --> 00:05:11.930 align:start position:0% noisy noisy mess and then you might say 00:05:11.930 --> 00:05:14.670 align:start position:0% noisy noisy mess and then you might say some<00:05:12.229> like<00:05:12.440> read<00:05:13.180> that<00:05:14.180> all<00:05:14.300> the<00:05:14.450> read 00:05:14.670 --> 00:05:14.680 align:start position:0% some like read that all the read 00:05:14.680 --> 00:05:16.600 align:start position:0% some like read that all the read messages<00:05:15.680> that<00:05:15.800> are<00:05:15.889> flying<00:05:16.010> around<00:05:16.100> those 00:05:16.600 --> 00:05:16.610 align:start position:0% messages that are flying around those 00:05:16.610 --> 00:05:19.659 align:start position:0% messages that are flying around those are<00:05:16.760> the<00:05:16.850> extra<00:05:17.300> redundant<00:05:17.840> messages<00:05:18.290> and<00:05:18.669> if 00:05:19.659 --> 00:05:19.669 align:start position:0% are the extra redundant messages and if 00:05:19.669 --> 00:05:21.580 align:start position:0% are the extra redundant messages and if you<00:05:20.150> have<00:05:20.360> like<00:05:20.630> I<00:05:20.840> think<00:05:21.020> this<00:05:21.110> one<00:05:21.260> has<00:05:21.410> like 00:05:21.580 --> 00:05:21.590 align:start position:0% you have like I think this one has like 00:05:21.590 --> 00:05:24.250 align:start position:0% you have like I think this one has like five<00:05:22.400> connections<00:05:22.760> or<00:05:23.180> something<00:05:23.479> I've<00:05:24.020> got<00:05:24.229> a 00:05:24.250 --> 00:05:24.260 align:start position:0% five connections or something I've got a 00:05:24.260 --> 00:05:27.100 align:start position:0% five connections or something I've got a little<00:05:24.350> table<00:05:24.560> here<00:05:25.450> yeah<00:05:26.450> so<00:05:26.630> once<00:05:26.870> you<00:05:26.990> have 00:05:27.100 --> 00:05:27.110 align:start position:0% little table here yeah so once you have 00:05:27.110 --> 00:05:30.430 align:start position:0% little table here yeah so once you have like<00:05:27.320> five<00:05:27.590> connections<00:05:28.280> per<00:05:29.240> pair<00:05:30.229> things 00:05:30.430 --> 00:05:30.440 align:start position:0% like five connections per pair things 00:05:30.440 --> 00:05:33.219 align:start position:0% like five connections per pair things then<00:05:30.650> you're<00:05:30.770> getting<00:05:30.919> like<00:05:31.220> 10<00:05:31.789> times<00:05:32.229> extra 00:05:33.219 --> 00:05:33.229 align:start position:0% then you're getting like 10 times extra 00:05:33.229 --> 00:05:34.840 align:start position:0% then you're getting like 10 times extra redundant<00:05:33.680> messages<00:05:34.100> that<00:05:34.280> you<00:05:34.430> don't<00:05:34.610> need 00:05:34.840 --> 00:05:34.850 align:start position:0% redundant messages that you don't need 00:05:34.850 --> 00:05:36.700 align:start position:0% redundant messages that you don't need to<00:05:35.510> see<00:05:35.630> well<00:05:35.840> you<00:05:35.930> kind<00:05:36.080> of<00:05:36.140> need<00:05:36.320> to<00:05:36.350> seem<00:05:36.620> to 00:05:36.700 --> 00:05:36.710 align:start position:0% to see well you kind of need to seem to 00:05:36.710 --> 00:05:38.440 align:start position:0% to see well you kind of need to seem to make<00:05:36.830> sure<00:05:37.010> they<00:05:37.100> all<00:05:37.130> arrive<00:05:37.729> but<00:05:38.000> you've 00:05:38.440 --> 00:05:38.450 align:start position:0% make sure they all arrive but you've 00:05:38.450 --> 00:05:39.880 align:start position:0% make sure they all arrive but you've seen<00:05:38.630> ten<00:05:38.840> times<00:05:39.020> as<00:05:39.140> much<00:05:39.260> as<00:05:39.440> you<00:05:39.530> needed<00:05:39.680> to 00:05:39.880 --> 00:05:39.890 align:start position:0% seen ten times as much as you needed to 00:05:39.890 --> 00:05:43.990 align:start position:0% seen ten times as much as you needed to but<00:05:40.160> it's<00:05:40.280> super<00:05:40.580> robust<00:05:42.430> they're<00:05:43.430> simple<00:05:43.760> and 00:05:43.990 --> 00:05:44.000 align:start position:0% but it's super robust they're simple and 00:05:44.000 --> 00:05:45.820 align:start position:0% but it's super robust they're simple and it's<00:05:44.360> the<00:05:44.539> in<00:05:44.660> it's<00:05:44.810> super<00:05:45.080> simple<00:05:45.620> to 00:05:45.820 --> 00:05:45.830 align:start position:0% it's the in it's super simple to 00:05:45.830 --> 00:05:48.790 align:start position:0% it's the in it's super simple to implement<00:05:45.979> as<00:05:46.280> well<00:05:46.430> the<00:05:46.940> role<00:05:47.150> is<00:05:47.300> just<00:05:47.800> seen 00:05:48.790 --> 00:05:48.800 align:start position:0% implement as well the role is just seen 00:05:48.800 --> 00:05:50.830 align:start position:0% implement as well the role is just seen two<00:05:48.919> new<00:05:49.070> messages<00:05:49.220> to<00:05:49.850> everyone<00:05:50.270> that<00:05:50.539> didn't 00:05:50.830 --> 00:05:50.840 align:start position:0% two new messages to everyone that didn't 00:05:50.840 --> 00:05:54.460 align:start position:0% two new messages to everyone that didn't send<00:05:51.050> it<00:05:51.140> to<00:05:51.260> you<00:05:52.270> which<00:05:53.270> is<00:05:53.630> also<00:05:53.930> being<00:05:54.080> don't 00:05:54.460 --> 00:05:54.470 align:start position:0% send it to you which is also being don't 00:05:54.470 --> 00:05:56.140 align:start position:0% send it to you which is also being don't receive<00:05:54.890> messages<00:05:55.310> who<00:05:55.430> really<00:05:55.669> know<00:05:55.789> so<00:05:55.970> just 00:05:56.140 --> 00:05:56.150 align:start position:0% receive messages who really know so just 00:05:56.150 --> 00:05:57.730 align:start position:0% receive messages who really know so just your<00:05:56.450> super<00:05:56.539> message<00:05:56.930> check<00:05:57.380> if<00:05:57.500> you<00:05:57.620> already 00:05:57.730 --> 00:05:57.740 align:start position:0% your super message check if you already 00:05:57.740 --> 00:05:59.830 align:start position:0% your super message check if you already know<00:05:58.010> about<00:05:58.039> this<00:05:58.340> message<00:05:58.700> and<00:05:58.910> if<00:05:59.270> not<00:05:59.419> send 00:05:59.830 --> 00:05:59.840 align:start position:0% know about this message and if not send 00:05:59.840 --> 00:06:01.000 align:start position:0% know about this message and if not send it<00:05:59.930> to<00:05:59.990> everyone<00:06:00.169> that<00:06:00.410> you're<00:06:00.530> connected<00:06:00.889> to 00:06:01.000 --> 00:06:01.010 align:start position:0% it to everyone that you're connected to 00:06:01.010 --> 00:06:02.590 align:start position:0% it to everyone that you're connected to and<00:06:01.280> then<00:06:01.700> that<00:06:01.820> will<00:06:01.970> flood<00:06:02.389> the<00:06:02.419> whole 00:06:02.590 --> 00:06:02.600 align:start position:0% and then that will flood the whole 00:06:02.600 --> 00:06:05.890 align:start position:0% and then that will flood the whole network<00:06:03.130> pretty<00:06:04.130> efficient<00:06:04.430> I<00:06:04.669> like<00:06:04.940> very 00:06:05.890 --> 00:06:05.900 align:start position:0% network pretty efficient I like very 00:06:05.900 --> 00:06:08.290 align:start position:0% network pretty efficient I like very robustly<00:06:06.440> like<00:06:06.800> if<00:06:06.950> some<00:06:07.130> nodes<00:06:07.340> get<00:06:08.090> taken 00:06:08.290 --> 00:06:08.300 align:start position:0% robustly like if some nodes get taken 00:06:08.300 --> 00:06:10.270 align:start position:0% robustly like if some nodes get taken out<00:06:08.539> it'll<00:06:09.169> just<00:06:09.200> be<00:06:09.410> routed<00:06:10.070> around 00:06:10.270 --> 00:06:10.280 align:start position:0% out it'll just be routed around 00:06:10.280 --> 00:06:13.870 align:start position:0% out it'll just be routed around otherwise<00:06:10.900> so<00:06:12.250> there's<00:06:13.250> only<00:06:13.400> like<00:06:13.639> a<00:06:13.669> couple 00:06:13.870 --> 00:06:13.880 align:start position:0% otherwise so there's only like a couple 00:06:13.880 --> 00:06:16.750 align:start position:0% otherwise so there's only like a couple of<00:06:14.060> cases<00:06:14.240> we<00:06:14.510> need<00:06:14.750> to<00:06:14.960> handle<00:06:15.800> think<00:06:16.430> of<00:06:16.520> here 00:06:16.750 --> 00:06:16.760 align:start position:0% of cases we need to handle think of here 00:06:16.760 --> 00:06:19.150 align:start position:0% of cases we need to handle think of here is<00:06:16.850> like<00:06:17.260> one<00:06:18.260> peer<00:06:18.500> sends<00:06:18.800> it<00:06:18.889> to<00:06:18.979> another 00:06:19.150 --> 00:06:19.160 align:start position:0% is like one peer sends it to another 00:06:19.160 --> 00:06:21.640 align:start position:0% is like one peer sends it to another peer<00:06:19.460> or<00:06:19.760> the<00:06:20.570> second<00:06:20.870> peer<00:06:21.020> sends<00:06:21.380> it<00:06:21.470> to<00:06:21.560> the 00:06:21.640 --> 00:06:21.650 align:start position:0% peer or the second peer sends it to the 00:06:21.650 --> 00:06:23.770 align:start position:0% peer or the second peer sends it to the first<00:06:21.770> peer<00:06:22.039> and<00:06:22.370> the<00:06:23.180> other<00:06:23.330> thing<00:06:23.510> that<00:06:23.539> can 00:06:23.770 --> 00:06:23.780 align:start position:0% first peer and the other thing that can 00:06:23.780 --> 00:06:25.450 align:start position:0% first peer and the other thing that can happen<00:06:23.900> is<00:06:24.229> they<00:06:24.500> both<00:06:24.710> send<00:06:25.070> it<00:06:25.220> to<00:06:25.310> each 00:06:25.450 --> 00:06:25.460 align:start position:0% happen is they both send it to each 00:06:25.460 --> 00:06:28.690 align:start position:0% happen is they both send it to each other<00:06:25.669> where<00:06:26.570> there<00:06:27.530> are<00:06:27.680> two<00:06:27.830> paths<00:06:28.310> for<00:06:28.580> that 00:06:28.690 --> 00:06:28.700 align:start position:0% other where there are two paths for that 00:06:28.700 --> 00:06:31.000 align:start position:0% other where there are two paths for that message<00:06:28.970> to<00:06:29.180> get<00:06:29.300> to<00:06:29.630> to<00:06:30.050> Alice<00:06:30.350> and<00:06:30.560> to<00:06:30.800> Bob 00:06:31.000 --> 00:06:31.010 align:start position:0% message to get to to Alice and to Bob 00:06:31.010 --> 00:06:33.700 align:start position:0% message to get to to Alice and to Bob and<00:06:31.340> they<00:06:32.030> both<00:06:32.210> received<00:06:32.660> it<00:06:32.900> in<00:06:33.050> a<00:06:33.260> within 00:06:33.700 --> 00:06:33.710 align:start position:0% and they both received it in a within 00:06:33.710 --> 00:06:36.930 align:start position:0% and they both received it in a within the<00:06:33.979> time<00:06:34.190> that<00:06:34.789> it<00:06:34.910> takes<00:06:35.060> to<00:06:35.300> see<00:06:35.960> to<00:06:36.409> send 00:06:36.930 --> 00:06:36.940 align:start position:0% the time that it takes to see to send 00:06:36.940 --> 00:06:41.080 align:start position:0% the time that it takes to see to send one<00:06:37.940> message<00:06:39.039> that's<00:06:40.039> the<00:06:40.370> that's<00:06:40.700> the<00:06:40.789> only 00:06:41.080 --> 00:06:41.090 align:start position:0% one message that's the that's the only 00:06:41.090 --> 00:06:41.410 align:start position:0% one message that's the that's the only case 00:06:41.410 --> 00:06:41.420 align:start position:0% case 00:06:41.420 --> 00:06:45.130 align:start position:0% case where<00:06:41.750> you<00:06:42.440> get<00:06:42.680> both<00:06:43.550> peers<00:06:44.080> passing<00:06:45.080> the 00:06:45.130 --> 00:06:45.140 align:start position:0% where you get both peers passing the 00:06:45.140 --> 00:06:47.350 align:start position:0% where you get both peers passing the message<00:06:45.640> well<00:06:46.640> you'll<00:06:46.760> get<00:06:46.850> where<00:06:47.090> you<00:06:47.180> get<00:06:47.330> a 00:06:47.350 --> 00:06:47.360 align:start position:0% message well you'll get where you get a 00:06:47.360 --> 00:06:50.050 align:start position:0% message well you'll get where you get a redundant<00:06:47.720> connection<00:06:48.220> and<00:06:49.220> the<00:06:49.670> bandwidth 00:06:50.050 --> 00:06:50.060 align:start position:0% redundant connection and the bandwidth 00:06:50.060 --> 00:06:52.270 align:start position:0% redundant connection and the bandwidth complexity<00:06:50.720> is<00:06:50.870> like<00:06:51.080> it's<00:06:51.620> proportional<00:06:52.130> to 00:06:52.270 --> 00:06:52.280 align:start position:0% complexity is like it's proportional to 00:06:52.280 --> 00:06:54.760 align:start position:0% complexity is like it's proportional to the<00:06:52.370> messages<00:06:53.170> times<00:06:54.170> the<00:06:54.410> spanning 00:06:54.760 --> 00:06:54.770 align:start position:0% the messages times the spanning 00:06:54.770 --> 00:06:58.750 align:start position:0% the messages times the spanning connections<00:06:55.870> plus<00:06:56.870> twice<00:06:57.500> the<00:06:58.250> redundant 00:06:58.750 --> 00:06:58.760 align:start position:0% connections plus twice the redundant 00:06:58.760 --> 00:07:00.610 align:start position:0% connections plus twice the redundant connections<00:06:59.360> because<00:06:59.930> each<00:07:00.170> redundant 00:07:00.610 --> 00:07:00.620 align:start position:0% connections because each redundant 00:07:00.620 --> 00:07:02.770 align:start position:0% connections because each redundant connection<00:07:01.070> gets<00:07:01.760> two<00:07:02.030> messages<00:07:02.480> sent<00:07:02.660> on 00:07:02.770 --> 00:07:02.780 align:start position:0% connection gets two messages sent on 00:07:02.780 --> 00:07:04.540 align:start position:0% connection gets two messages sent on earth<00:07:02.960> so<00:07:03.320> the<00:07:03.680> redundant<00:07:04.040> connections<00:07:04.220> are 00:07:04.540 --> 00:07:04.550 align:start position:0% earth so the redundant connections are 00:07:04.550 --> 00:07:05.860 align:start position:0% earth so the redundant connections are like<00:07:04.670> much<00:07:04.910> more<00:07:05.120> expensive<00:07:05.330> than<00:07:05.720> the 00:07:05.860 --> 00:07:05.870 align:start position:0% like much more expensive than the 00:07:05.870 --> 00:07:09.250 align:start position:0% like much more expensive than the minimal<00:07:06.620> set<00:07:06.800> of<00:07:06.830> spanning<00:07:07.250> connections<00:07:08.260> and 00:07:09.250 --> 00:07:09.260 align:start position:0% minimal set of spanning connections and 00:07:09.260 --> 00:07:11.380 align:start position:0% minimal set of spanning connections and once<00:07:09.740> you've<00:07:09.860> got<00:07:10.010> 10<00:07:10.220> when<00:07:10.550> you've<00:07:10.970> got<00:07:11.120> 10 00:07:11.380 --> 00:07:11.390 align:start position:0% once you've got 10 when you've got 10 00:07:11.390 --> 00:07:15.360 align:start position:0% once you've got 10 when you've got 10 connections<00:07:11.930> to<00:07:12.170> appear<00:07:13.210> you<00:07:14.210> have<00:07:14.390> like<00:07:14.540> 95% 00:07:15.360 --> 00:07:15.370 align:start position:0% connections to appear you have like 95% 00:07:15.370 --> 00:07:19.240 align:start position:0% connections to appear you have like 95% redundant<00:07:16.370> messages<00:07:17.150> so<00:07:17.990> it<00:07:18.620> means<00:07:18.800> if<00:07:18.980> we<00:07:19.070> can 00:07:19.240 --> 00:07:19.250 align:start position:0% redundant messages so it means if we can 00:07:19.250 --> 00:07:21.550 align:start position:0% redundant messages so it means if we can get<00:07:19.370> rid<00:07:19.460> of<00:07:19.550> the<00:07:19.640> drownded<00:07:19.940> messages<00:07:20.360> week<00:07:21.170> we 00:07:21.550 --> 00:07:21.560 align:start position:0% get rid of the drownded messages week we 00:07:21.560 --> 00:07:27.580 align:start position:0% get rid of the drownded messages week we can<00:07:22.930> we<00:07:23.930> can<00:07:24.080> just<00:07:24.110> transmit<00:07:24.680> one<00:07:25.210> message<00:07:26.590> one 00:07:27.580 --> 00:07:27.590 align:start position:0% can we can just transmit one message one 00:07:27.590 --> 00:07:31.420 align:start position:0% can we can just transmit one message one one<00:07:28.160> message<00:07:28.460> per<00:07:28.520> pair<00:07:28.900> which<00:07:29.900> is<00:07:30.050> optimal<00:07:30.770> so 00:07:31.420 --> 00:07:31.430 align:start position:0% one message per pair which is optimal so 00:07:31.430 --> 00:07:33.970 align:start position:0% one message per pair which is optimal so the<00:07:32.390> better<00:07:32.810> solution<00:07:33.110> is<00:07:33.230> a<00:07:33.260> spanning<00:07:33.950> tree 00:07:33.970 --> 00:07:33.980 align:start position:0% the better solution is a spanning tree 00:07:33.980 --> 00:07:36.310 align:start position:0% the better solution is a spanning tree network<00:07:34.880> so<00:07:35.270> spanning<00:07:35.630> tree<00:07:35.780> is<00:07:35.930> like<00:07:36.080> we<00:07:36.200> get 00:07:36.310 --> 00:07:36.320 align:start position:0% network so spanning tree is like we get 00:07:36.320 --> 00:07:39.040 align:start position:0% network so spanning tree is like we get a<00:07:36.380> graph<00:07:36.890> and<00:07:37.160> we<00:07:37.640> just<00:07:37.940> only<00:07:38.780> have<00:07:38.930> the 00:07:39.040 --> 00:07:39.050 align:start position:0% a graph and we just only have the 00:07:39.050 --> 00:07:40.480 align:start position:0% a graph and we just only have the connections<00:07:39.380> we<00:07:39.500> need<00:07:39.740> to<00:07:39.950> reach<00:07:40.100> all<00:07:40.250> of<00:07:40.280> the 00:07:40.480 --> 00:07:40.490 align:start position:0% connections we need to reach all of the 00:07:40.490 --> 00:07:45.040 align:start position:0% connections we need to reach all of the nodes<00:07:42.130> so<00:07:43.130> we<00:07:43.280> can<00:07:43.460> take<00:07:44.300> the<00:07:44.690> flood<00:07:44.930> and 00:07:45.040 --> 00:07:45.050 align:start position:0% nodes so we can take the flood and 00:07:45.050 --> 00:07:46.840 align:start position:0% nodes so we can take the flood and gossip<00:07:45.410> and<00:07:45.590> we<00:07:45.740> can<00:07:45.890> build<00:07:46.130> use<00:07:46.490> that<00:07:46.670> to 00:07:46.840 --> 00:07:46.850 align:start position:0% gossip and we can build use that to 00:07:46.850 --> 00:07:48.520 align:start position:0% gossip and we can build use that to build<00:07:47.030> a<00:07:47.330> spanning<00:07:47.750> network<00:07:48.050> spanning 00:07:48.520 --> 00:07:48.530 align:start position:0% build a spanning network spanning 00:07:48.530 --> 00:07:50.920 align:start position:0% build a spanning network spanning network<00:07:48.860> in<00:07:48.980> a<00:07:49.070> decentralized<00:07:49.310> way<00:07:49.730> by<00:07:50.570> just 00:07:50.920 --> 00:07:50.930 align:start position:0% network in a decentralized way by just 00:07:50.930 --> 00:07:53.080 align:start position:0% network in a decentralized way by just whenever<00:07:51.740> you<00:07:51.980> receive<00:07:52.310> a<00:07:52.370> duplicate<00:07:52.790> message 00:07:53.080 --> 00:07:53.090 align:start position:0% whenever you receive a duplicate message 00:07:53.090 --> 00:07:55.090 align:start position:0% whenever you receive a duplicate message you<00:07:53.210> just<00:07:53.240> say<00:07:53.480> you<00:07:53.660> just<00:07:53.830> deactivate<00:07:54.830> that 00:07:55.090 --> 00:07:55.100 align:start position:0% you just say you just deactivate that 00:07:55.100 --> 00:07:55.660 align:start position:0% you just say you just deactivate that connection 00:07:55.660 --> 00:07:55.670 align:start position:0% connection 00:07:55.670 --> 00:07:57.340 align:start position:0% connection I<00:07:55.880> didn't<00:07:56.330> say<00:07:56.390> disconnect<00:07:56.870> and<00:07:57.080> I'll<00:07:57.200> come 00:07:57.340 --> 00:07:57.350 align:start position:0% I didn't say disconnect and I'll come 00:07:57.350 --> 00:07:59.140 align:start position:0% I didn't say disconnect and I'll come back<00:07:57.470> to<00:07:57.860> that<00:07:57.890> in<00:07:58.580> a<00:07:58.700> bit<00:07:58.730> so<00:07:58.940> you<00:07:58.970> just 00:07:59.140 --> 00:07:59.150 align:start position:0% back to that in a bit so you just 00:07:59.150 --> 00:08:02.710 align:start position:0% back to that in a bit so you just deactivate<00:07:59.660> that<00:08:00.190> so<00:08:01.190> now<00:08:02.030> you're<00:08:02.510> sending 00:08:02.710 --> 00:08:02.720 align:start position:0% deactivate that so now you're sending 00:08:02.720 --> 00:08:08.800 align:start position:0% deactivate that so now you're sending like<00:08:03.140> just<00:08:04.100> the<00:08:04.220> number<00:08:04.430> of<00:08:04.520> messages<00:08:07.810> the 00:08:08.800 --> 00:08:08.810 align:start position:0% like just the number of messages the 00:08:08.810 --> 00:08:09.970 align:start position:0% like just the number of messages the only<00:08:09.020> problem<00:08:09.290> is<00:08:09.320> that<00:08:09.380> trees<00:08:09.740> are<00:08:09.860> really 00:08:09.970 --> 00:08:09.980 align:start position:0% only problem is that trees are really 00:08:09.980 --> 00:08:13.720 align:start position:0% only problem is that trees are really fragile<00:08:10.840> so<00:08:11.840> it's<00:08:12.430> because<00:08:13.430> now<00:08:13.550> you've 00:08:13.720 --> 00:08:13.730 align:start position:0% fragile so it's because now you've 00:08:13.730 --> 00:08:15.130 align:start position:0% fragile so it's because now you've basically<00:08:13.940> just<00:08:14.210> added<00:08:14.690> a<00:08:14.750> whole<00:08:14.840> bunch<00:08:15.050> of 00:08:15.130 --> 00:08:15.140 align:start position:0% basically just added a whole bunch of 00:08:15.140 --> 00:08:16.840 align:start position:0% basically just added a whole bunch of single<00:08:15.740> you've<00:08:16.010> made<00:08:16.190> every<00:08:16.490> single<00:08:16.730> node 00:08:16.840 --> 00:08:16.850 align:start position:0% single you've made every single node 00:08:16.850 --> 00:08:18.510 align:start position:0% single you've made every single node into<00:08:17.090> a<00:08:17.120> central<00:08:17.510> point<00:08:17.840> of<00:08:17.990> failure<00:08:18.140> so 00:08:18.510 --> 00:08:18.520 align:start position:0% into a central point of failure so 00:08:18.520 --> 00:08:21.760 align:start position:0% into a central point of failure so there's<00:08:19.520> one<00:08:19.730> path<00:08:19.970> between<00:08:20.480> any<00:08:20.840> two<00:08:21.590> random 00:08:21.760 --> 00:08:21.770 align:start position:0% there's one path between any two random 00:08:21.770 --> 00:08:24.700 align:start position:0% there's one path between any two random nodes<00:08:22.070> and<00:08:22.340> if<00:08:23.150> any<00:08:23.300> of<00:08:23.450> the<00:08:23.630> nodes<00:08:24.050> in<00:08:24.410> that 00:08:24.700 --> 00:08:24.710 align:start position:0% nodes and if any of the nodes in that 00:08:24.710 --> 00:08:28.690 align:start position:0% nodes and if any of the nodes in that thing<00:08:25.190> fail<00:08:25.460> then<00:08:26.090> the<00:08:27.250> end<00:08:28.250> those<00:08:28.340> messages 00:08:28.690 --> 00:08:28.700 align:start position:0% thing fail then the end those messages 00:08:28.700 --> 00:08:35.020 align:start position:0% thing fail then the end those messages won't<00:08:28.970> get<00:08:29.090> through<00:08:29.270> so<00:08:30.340> the<00:08:33.550> yes<00:08:34.550> so<00:08:34.729> it's<00:08:34.880> odd 00:08:35.020 --> 00:08:35.030 align:start position:0% won't get through so the yes so it's odd 00:08:35.030 --> 00:08:38.850 align:start position:0% won't get through so the yes so it's odd bandwidth<00:08:35.479> optimal<00:08:35.900> but<00:08:36.080> it's<00:08:36.229> not<00:08:36.440> robust 00:08:38.850 --> 00:08:38.860 align:start position:0% bandwidth optimal but it's not robust 00:08:38.860 --> 00:08:41.290 align:start position:0% bandwidth optimal but it's not robust but<00:08:39.860> then<00:08:40.040> there's<00:08:40.280> this<00:08:40.430> paper<00:08:40.760> I<00:08:40.850> discovered 00:08:41.290 --> 00:08:41.300 align:start position:0% but then there's this paper I discovered 00:08:41.300 --> 00:08:43.390 align:start position:0% but then there's this paper I discovered a<00:08:41.360> while<00:08:41.479> ago<00:08:41.660> called<00:08:42.020> epidemic<00:08:42.920> broadcast 00:08:43.390 --> 00:08:43.400 align:start position:0% a while ago called epidemic broadcast 00:08:43.400 --> 00:08:46.120 align:start position:0% a while ago called epidemic broadcast trees<00:08:43.700> and<00:08:43.970> this<00:08:44.380> combines<00:08:45.380> the<00:08:45.590> best<00:08:45.770> parts 00:08:46.120 --> 00:08:46.130 align:start position:0% trees and this combines the best parts 00:08:46.130 --> 00:08:48.880 align:start position:0% trees and this combines the best parts of<00:08:46.280> both<00:08:46.460> flood<00:08:46.760> and<00:08:46.910> gossip<00:08:47.240> and<00:08:47.890> spanning 00:08:48.880 --> 00:08:48.890 align:start position:0% of both flood and gossip and spanning 00:08:48.890 --> 00:08:53.890 align:start position:0% of both flood and gossip and spanning trees<00:08:49.100> so<00:08:51.550> how<00:08:52.550> it<00:08:52.610> works<00:08:52.940> basically<00:08:53.240> as<00:08:53.720> you 00:08:53.890 --> 00:08:53.900 align:start position:0% trees so how it works basically as you 00:08:53.900 --> 00:08:54.770 align:start position:0% trees so how it works basically as you have 00:08:54.770 --> 00:08:54.780 align:start position:0% have 00:08:54.780 --> 00:08:56.660 align:start position:0% have connections<00:08:55.440> are<00:08:55.740> in<00:08:55.920> two<00:08:56.100> modes<00:08:56.280> there's 00:08:56.660 --> 00:08:56.670 align:start position:0% connections are in two modes there's 00:08:56.670 --> 00:09:00.590 align:start position:0% connections are in two modes there's eager<00:08:57.030> and<00:08:57.270> there's<00:08:57.720> lazy<00:08:57.990> and<00:08:58.910> so<00:08:59.910> the<00:09:00.420> lays 00:09:00.590 --> 00:09:00.600 align:start position:0% eager and there's lazy and so the lays 00:09:00.600 --> 00:09:03.500 align:start position:0% eager and there's lazy and so the lays it<00:09:00.840> the<00:09:00.960> redundant<00:09:01.920> connections<00:09:02.850> get<00:09:03.330> put 00:09:03.500 --> 00:09:03.510 align:start position:0% it the redundant connections get put 00:09:03.510 --> 00:09:08.840 align:start position:0% it the redundant connections get put into<00:09:03.660> lazy<00:09:03.960> mode<00:09:04.260> so<00:09:04.890> in<00:09:06.680> eager<00:09:07.680> mode<00:09:07.890> when<00:09:08.730> you 00:09:08.840 --> 00:09:08.850 align:start position:0% into lazy mode so in eager mode when you 00:09:08.850 --> 00:09:10.160 align:start position:0% into lazy mode so in eager mode when you receive<00:09:09.120> message<00:09:09.450> you<00:09:09.630> transmit<00:09:10.050> it 00:09:10.160 --> 00:09:10.170 align:start position:0% receive message you transmit it 00:09:10.170 --> 00:09:12.410 align:start position:0% receive message you transmit it immediately<00:09:10.590> and<00:09:11.010> when<00:09:11.610> a<00:09:11.820> connection<00:09:12.060> is<00:09:12.270> in 00:09:12.410 --> 00:09:12.420 align:start position:0% immediately and when a connection is in 00:09:12.420 --> 00:09:14.990 align:start position:0% immediately and when a connection is in lazy<00:09:12.660> mode<00:09:12.960> when<00:09:13.920> you<00:09:14.010> receive<00:09:14.280> a<00:09:14.310> message<00:09:14.490> you 00:09:14.990 --> 00:09:15.000 align:start position:0% lazy mode when you receive a message you 00:09:15.000 --> 00:09:17.030 align:start position:0% lazy mode when you receive a message you just<00:09:15.210> seemed<00:09:15.420> a<00:09:15.480> really<00:09:15.690> short<00:09:15.870> note<00:09:16.260> that<00:09:16.920> you 00:09:17.030 --> 00:09:17.040 align:start position:0% just seemed a really short note that you 00:09:17.040 --> 00:09:20.210 align:start position:0% just seemed a really short note that you know<00:09:17.220> about<00:09:17.490> this<00:09:17.670> new<00:09:17.850> message<00:09:18.150> now<00:09:18.390> so<00:09:19.220> all 00:09:20.210 --> 00:09:20.220 align:start position:0% know about this new message now so all 00:09:20.220 --> 00:09:22.010 align:start position:0% know about this new message now so all of<00:09:20.460> the<00:09:20.580> main<00:09:20.760> all<00:09:21.150> of<00:09:21.330> the<00:09:21.480> spanning 00:09:22.010 --> 00:09:22.020 align:start position:0% of the main all of the spanning 00:09:22.020 --> 00:09:24.050 align:start position:0% of the main all of the spanning connections<00:09:22.410> get<00:09:22.980> the<00:09:23.130> whole<00:09:23.280> message<00:09:23.610> sent 00:09:24.050 --> 00:09:24.060 align:start position:0% connections get the whole message sent 00:09:24.060 --> 00:09:26.270 align:start position:0% connections get the whole message sent across<00:09:24.270> so<00:09:24.690> that's<00:09:25.170> that<00:09:25.590> lets<00:09:25.800> the<00:09:25.980> message 00:09:26.270 --> 00:09:26.280 align:start position:0% across so that's that lets the message 00:09:26.280 --> 00:09:29.450 align:start position:0% across so that's that lets the message propagate<00:09:26.700> as<00:09:26.880> fast<00:09:27.600> as<00:09:27.780> it<00:09:27.900> can<00:09:28.050> and<00:09:28.320> then<00:09:28.460> the 00:09:29.450 --> 00:09:29.460 align:start position:0% propagate as fast as it can and then the 00:09:29.460 --> 00:09:31.610 align:start position:0% propagate as fast as it can and then the message<00:09:30.300> the<00:09:30.660> redundant<00:09:31.140> connections<00:09:31.290> they 00:09:31.610 --> 00:09:31.620 align:start position:0% message the redundant connections they 00:09:31.620 --> 00:09:34.160 align:start position:0% message the redundant connections they just<00:09:31.800> have<00:09:31.890> a<00:09:31.920> very<00:09:32.550> short<00:09:32.840> message<00:09:33.840> being 00:09:34.160 --> 00:09:34.170 align:start position:0% just have a very short message being 00:09:34.170 --> 00:09:38.060 align:start position:0% just have a very short message being sent<00:09:34.230> across<00:09:34.530> so<00:09:34.830> it<00:09:35.130> might<00:09:35.520> only<00:09:35.790> be<00:09:36.440> so<00:09:37.440> in 00:09:38.060 --> 00:09:38.070 align:start position:0% sent across so it might only be so in 00:09:38.070 --> 00:09:40.190 align:start position:0% sent across so it might only be so in the<00:09:38.490> current<00:09:38.790> implementation<00:09:38.940> of<00:09:39.600> secure 00:09:40.190 --> 00:09:40.200 align:start position:0% the current implementation of secure 00:09:40.200 --> 00:09:46.580 align:start position:0% the current implementation of secure scuttlebutt<00:09:43.850> and<00:09:44.850> the<00:09:45.540> average<00:09:45.870> message<00:09:46.350> size 00:09:46.580 --> 00:09:46.590 align:start position:0% scuttlebutt and the average message size 00:09:46.590 --> 00:09:48.860 align:start position:0% scuttlebutt and the average message size is<00:09:46.830> like<00:09:46.980> 700<00:09:47.370> bytes<00:09:47.730> and<00:09:48.060> it<00:09:48.270> can<00:09:48.420> be<00:09:48.570> could<00:09:48.780> we 00:09:48.860 --> 00:09:48.870 align:start position:0% is like 700 bytes and it can be could we 00:09:48.870 --> 00:09:52.280 align:start position:0% is like 700 bytes and it can be could we go<00:09:48.990> up<00:09:49.050> to<00:09:49.230> 8<00:09:49.500> kilobytes<00:09:49.950> but<00:09:50.700> the<00:09:51.240> note<00:09:51.810> would 00:09:52.280 --> 00:09:52.290 align:start position:0% go up to 8 kilobytes but the note would 00:09:52.290 --> 00:09:55.220 align:start position:0% go up to 8 kilobytes but the note would only<00:09:52.440> be<00:09:52.770> like<00:09:53.460> 80<00:09:53.850> bytes<00:09:54.090> I<00:09:54.450> think<00:09:54.750> and<00:09:54.900> that 00:09:55.220 --> 00:09:55.230 align:start position:0% only be like 80 bytes I think and that 00:09:55.230 --> 00:09:57.020 align:start position:0% only be like 80 bytes I think and that could<00:09:55.410> be<00:09:55.530> like<00:09:55.770> binary<00:09:56.010> optimize<00:09:56.580> down<00:09:56.850> to 00:09:57.020 --> 00:09:57.030 align:start position:0% could be like binary optimize down to 00:09:57.030 --> 00:10:01.790 align:start position:0% could be like binary optimize down to probably<00:09:57.480> less<00:09:57.840> than<00:09:57.870> 10<00:09:59.510> so<00:10:00.510> the<00:10:01.140> redundant 00:10:01.790 --> 00:10:01.800 align:start position:0% probably less than 10 so the redundant 00:10:01.800 --> 00:10:03.829 align:start position:0% probably less than 10 so the redundant connections<00:10:01.980> still<00:10:02.400> exist<00:10:02.820> but<00:10:03.360> you<00:10:03.660> just 00:10:03.829 --> 00:10:03.839 align:start position:0% connections still exist but you just 00:10:03.839 --> 00:10:06.520 align:start position:0% connections still exist but you just seem<00:10:03.990> to<00:10:04.080> Whaley<00:10:04.350> a<00:10:04.380> starter<00:10:04.710> on<00:10:04.860> them<00:10:05.010> and 00:10:06.520 --> 00:10:06.530 align:start position:0% seem to Whaley a starter on them and 00:10:06.530 --> 00:10:11.060 align:start position:0% seem to Whaley a starter on them and then<00:10:07.530> um<00:10:08.510> they<00:10:09.510> also<00:10:09.720> the<00:10:10.110> robustness<00:10:10.740> still 00:10:11.060 --> 00:10:11.070 align:start position:0% then um they also the robustness still 00:10:11.070 --> 00:10:16.100 align:start position:0% then um they also the robustness still exists<00:10:11.520> because<00:10:12.620> when<00:10:13.620> a<00:10:14.339> message<00:10:15.270> when<00:10:15.480> so 00:10:16.100 --> 00:10:16.110 align:start position:0% exists because when a message when so 00:10:16.110 --> 00:10:19.010 align:start position:0% exists because when a message when so when<00:10:16.530> you<00:10:16.620> receive<00:10:16.800> a<00:10:17.580> message<00:10:17.910> for<00:10:18.750> the<00:10:18.839> first 00:10:19.010 --> 00:10:19.020 align:start position:0% when you receive a message for the first 00:10:19.020 --> 00:10:21.200 align:start position:0% when you receive a message for the first time<00:10:19.170> you<00:10:19.320> like<00:10:19.589> rebroadcast<00:10:20.339> and<00:10:20.550> so<00:10:20.700> on<00:10:20.790> but 00:10:21.200 --> 00:10:21.210 align:start position:0% time you like rebroadcast and so on but 00:10:21.210 --> 00:10:23.180 align:start position:0% time you like rebroadcast and so on but if<00:10:21.330> you<00:10:21.480> receive<00:10:21.780> a<00:10:21.810> note<00:10:22.110> about<00:10:22.770> a<00:10:22.800> message 00:10:23.180 --> 00:10:23.190 align:start position:0% if you receive a note about a message 00:10:23.190 --> 00:10:24.920 align:start position:0% if you receive a note about a message that<00:10:23.400> you<00:10:23.490> haven't<00:10:23.940> that<00:10:24.480> you<00:10:24.540> don't<00:10:24.780> know 00:10:24.920 --> 00:10:24.930 align:start position:0% that you haven't that you don't know 00:10:24.930 --> 00:10:27.650 align:start position:0% that you haven't that you don't know about<00:10:25.080> you<00:10:25.380> then<00:10:26.220> you've<00:10:27.030> seen<00:10:27.210> dammit<00:10:27.450> you 00:10:27.650 --> 00:10:27.660 align:start position:0% about you then you've seen dammit you 00:10:27.660 --> 00:10:33.190 align:start position:0% about you then you've seen dammit you send<00:10:27.900> a<00:10:27.930> request<00:10:27.960> back<00:10:28.560> to<00:10:28.920> that<00:10:30.890> back<00:10:31.890> to<00:10:32.100> that 00:10:33.190 --> 00:10:33.200 align:start position:0% send a request back to that back to that 00:10:33.200 --> 00:10:35.960 align:start position:0% send a request back to that back to that back<00:10:34.200> back<00:10:34.410> to<00:10:34.530> that<00:10:34.650> peer<00:10:34.920> asking<00:10:35.640> them<00:10:35.790> to 00:10:35.960 --> 00:10:35.970 align:start position:0% back back to that peer asking them to 00:10:35.970 --> 00:10:37.910 align:start position:0% back back to that peer asking them to turn<00:10:36.270> back<00:10:36.540> into<00:10:36.780> eager<00:10:37.230> mode<00:10:37.410> and<00:10:37.680> then 00:10:37.910 --> 00:10:37.920 align:start position:0% turn back into eager mode and then 00:10:37.920 --> 00:10:39.079 align:start position:0% turn back into eager mode and then they'll<00:10:38.070> send<00:10:38.190> you<00:10:38.310> the<00:10:38.430> whole<00:10:38.580> message<00:10:38.730> and 00:10:39.079 --> 00:10:39.089 align:start position:0% they'll send you the whole message and 00:10:39.089 --> 00:10:42.050 align:start position:0% they'll send you the whole message and now<00:10:39.330> the<00:10:39.390> network<00:10:39.600> is<00:10:39.870> repaired<00:10:40.230> so<00:10:40.880> as<00:10:41.880> the 00:10:42.050 --> 00:10:42.060 align:start position:0% now the network is repaired so as the 00:10:42.060 --> 00:10:47.000 align:start position:0% now the network is repaired so as the best<00:10:42.210> of<00:10:42.300> both<00:10:42.390> worlds<00:10:45.650> yeah<00:10:46.650> and<00:10:46.860> then 00:10:47.000 --> 00:10:47.010 align:start position:0% best of both worlds yeah and then 00:10:47.010 --> 00:10:52.190 align:start position:0% best of both worlds yeah and then there's<00:10:47.310> only<00:10:47.460> a<00:10:49.490> small<00:10:50.490> amount<00:10:51.060> of<00:10:51.200> state 00:10:52.190 --> 00:10:52.200 align:start position:0% there's only a small amount of state 00:10:52.200 --> 00:10:55.520 align:start position:0% there's only a small amount of state that<00:10:52.560> you<00:10:52.710> need<00:10:52.920> to<00:10:53.480> keep<00:10:54.480> track<00:10:54.690> of<00:10:54.750> up<00:10:55.200> here 00:10:55.520 --> 00:10:55.530 align:start position:0% that you need to keep track of up here 00:10:55.530 --> 00:10:58.610 align:start position:0% that you need to keep track of up here for<00:10:55.980> per<00:10:56.310> feed<00:10:56.550> you<00:10:56.790> just<00:10:57.030> need<00:10:57.180> the<00:10:57.360> ID<00:10:57.930> the 00:10:58.610 --> 00:10:58.620 align:start position:0% for per feed you just need the ID the 00:10:58.620 --> 00:11:00.140 align:start position:0% for per feed you just need the ID the local<00:10:58.920> sequence<00:10:59.190> number<00:10:59.730> of<00:10:59.760> the<00:10:59.880> remote 00:11:00.140 --> 00:11:00.150 align:start position:0% local sequence number of the remote 00:11:00.150 --> 00:11:03.650 align:start position:0% local sequence number of the remote Cygnus<00:11:00.540> number<00:11:00.900> the<00:11:01.970> local<00:11:02.970> request<00:11:03.390> the 00:11:03.650 --> 00:11:03.660 align:start position:0% Cygnus number the local request the 00:11:03.660 --> 00:11:05.840 align:start position:0% Cygnus number the local request the remote<00:11:03.959> request<00:11:04.290> and<00:11:04.589> the<00:11:05.010> local<00:11:05.580> and<00:11:05.670> remote 00:11:05.840 --> 00:11:05.850 align:start position:0% remote request and the local and remote 00:11:05.850 --> 00:11:08.040 align:start position:0% remote request and the local and remote modes<00:11:06.480> so<00:11:06.839> that's<00:11:07.020> only 00:11:08.040 --> 00:11:08.050 align:start position:0% modes so that's only 00:11:08.050 --> 00:11:10.020 align:start position:0% modes so that's only debts<00:11:09.040> you<00:11:09.220> know<00:11:09.310> if<00:11:09.370> we're<00:11:09.520> under<00:11:09.850> like 00:11:10.020 --> 00:11:10.030 align:start position:0% debts you know if we're under like 00:11:10.030 --> 00:11:11.610 align:start position:0% debts you know if we're under like depending<00:11:10.480> on<00:11:10.600> how<00:11:10.750> long<00:11:10.990> that<00:11:11.050> idea 00:11:11.610 --> 00:11:11.620 align:start position:0% depending on how long that idea 00:11:11.620 --> 00:11:14.820 align:start position:0% depending on how long that idea Stringer's<00:11:12.420> would<00:11:13.420> talk<00:11:13.720> about<00:11:13.750> like<00:11:13.960> just 00:11:14.820 --> 00:11:14.830 align:start position:0% Stringer's would talk about like just 00:11:14.830 --> 00:11:24.030 align:start position:0% Stringer's would talk about like just like<00:11:15.490> tens<00:11:15.760> of<00:11:15.940> bytes<00:11:16.770> I'm<00:11:18.000> debt<00:11:19.000> is<00:11:22.410> okay<00:11:23.410> so 00:11:24.030 --> 00:11:24.040 align:start position:0% like tens of bytes I'm debt is okay so 00:11:24.040 --> 00:11:27.690 align:start position:0% like tens of bytes I'm debt is okay so then<00:11:24.880> the<00:11:25.270> other<00:11:25.740> so<00:11:26.740> they<00:11:27.160> talked<00:11:27.370> up<00:11:27.490> that's 00:11:27.690 --> 00:11:27.700 align:start position:0% then the other so they talked up that's 00:11:27.700 --> 00:11:30.570 align:start position:0% then the other so they talked up that's all<00:11:28.030> about<00:11:28.240> optimizing<00:11:28.690> the<00:11:28.900> network<00:11:29.230> so<00:11:29.950> the 00:11:30.570 --> 00:11:30.580 align:start position:0% all about optimizing the network so the 00:11:30.580 --> 00:11:32.820 align:start position:0% all about optimizing the network so the second<00:11:30.880> part<00:11:31.000> is<00:11:31.260> optimizing<00:11:32.260> the<00:11:32.440> handshakes 00:11:32.820 --> 00:11:32.830 align:start position:0% second part is optimizing the handshakes 00:11:32.830 --> 00:11:37.410 align:start position:0% second part is optimizing the handshakes so<00:11:33.490> secure<00:11:34.000> scuttlebutt<00:11:34.420> had<00:11:35.260> this<00:11:36.420> so 00:11:37.410 --> 00:11:37.420 align:start position:0% so secure scuttlebutt had this so 00:11:37.420 --> 00:11:40.770 align:start position:0% so secure scuttlebutt had this so original<00:11:38.050> scuttlebutt<00:11:38.610> had<00:11:39.610> this<00:11:39.780> thing 00:11:40.770 --> 00:11:40.780 align:start position:0% original scuttlebutt had this thing 00:11:40.780 --> 00:11:43.170 align:start position:0% original scuttlebutt had this thing called<00:11:40.810> a<00:11:41.050> victor<00:11:41.410> clog<00:11:41.700> so<00:11:42.700> a<00:11:42.730> victor<00:11:43.000> clock 00:11:43.170 --> 00:11:43.180 align:start position:0% called a victor clog so a victor clock 00:11:43.180 --> 00:11:46.220 align:start position:0% called a victor clog so a victor clock is<00:11:43.420> just<00:11:43.480> like<00:11:43.930> a<00:11:43.960> list<00:11:44.320> of<00:11:44.560> all<00:11:45.250> of<00:11:45.280> the<00:11:45.610> things 00:11:46.220 --> 00:11:46.230 align:start position:0% is just like a list of all of the things 00:11:46.230 --> 00:11:48.960 align:start position:0% is just like a list of all of the things so<00:11:47.230> pure<00:11:47.560> so<00:11:47.890> you<00:11:48.160> have<00:11:48.340> a<00:11:48.370> whole<00:11:48.490> bunch<00:11:48.640> of<00:11:48.700> a 00:11:48.960 --> 00:11:48.970 align:start position:0% so pure so you have a whole bunch of a 00:11:48.970 --> 00:11:50.250 align:start position:0% so pure so you have a whole bunch of a whole<00:11:49.060> bunch<00:11:49.150> of<00:11:49.300> friends<00:11:49.510> and<00:11:49.690> when<00:11:50.170> two 00:11:50.250 --> 00:11:50.260 align:start position:0% whole bunch of friends and when two 00:11:50.260 --> 00:11:52.110 align:start position:0% whole bunch of friends and when two friends<00:11:50.290> bump<00:11:50.650> into<00:11:50.860> each<00:11:50.890> other<00:11:51.070> they<00:11:51.670> say<00:11:51.910> I 00:11:52.110 --> 00:11:52.120 align:start position:0% friends bump into each other they say I 00:11:52.120 --> 00:11:53.880 align:start position:0% friends bump into each other they say I win<00:11:52.330> did<00:11:52.450> you<00:11:52.510> last<00:11:52.750> hear<00:11:52.990> from<00:11:53.170> Bob<00:11:53.380> I<00:11:53.650> heard 00:11:53.880 --> 00:11:53.890 align:start position:0% win did you last hear from Bob I heard 00:11:53.890 --> 00:11:56.100 align:start position:0% win did you last hear from Bob I heard from<00:11:54.040> Bob<00:11:54.250> on<00:11:54.550> Tuesday<00:11:55.510> when<00:11:55.720> did<00:11:55.870> you<00:11:55.990> last 00:11:56.100 --> 00:11:56.110 align:start position:0% from Bob on Tuesday when did you last 00:11:56.110 --> 00:11:58.170 align:start position:0% from Bob on Tuesday when did you last hear<00:11:56.530> from<00:11:56.950> Ellis<00:11:57.250> I<00:11:57.370> heard<00:11:57.520> from<00:11:57.790> Ellis<00:11:58.030> on 00:11:58.170 --> 00:11:58.180 align:start position:0% hear from Ellis I heard from Ellis on 00:11:58.180 --> 00:12:02.880 align:start position:0% hear from Ellis I heard from Ellis on Monday<00:11:58.450> and<00:11:58.690> if<00:11:59.500> I<00:12:00.190> say<00:12:00.820> that<00:12:01.060> I<00:12:01.120> saw<00:12:01.990> Alice<00:12:02.710> on 00:12:02.880 --> 00:12:02.890 align:start position:0% Monday and if I say that I saw Alice on 00:12:02.890 --> 00:12:05.310 align:start position:0% Monday and if I say that I saw Alice on Monday<00:12:03.520> and<00:12:03.790> you<00:12:03.820> saw<00:12:04.060> her<00:12:04.210> on<00:12:04.330> Sunday<00:12:04.570> then<00:12:05.200> I 00:12:05.310 --> 00:12:05.320 align:start position:0% Monday and you saw her on Sunday then I 00:12:05.320 --> 00:12:07.230 align:start position:0% Monday and you saw her on Sunday then I can<00:12:05.530> then<00:12:06.010> I<00:12:06.100> know<00:12:06.160> I<00:12:06.310> just<00:12:06.670> need<00:12:06.820> to<00:12:06.910> send<00:12:07.090> you 00:12:07.230 --> 00:12:07.240 align:start position:0% can then I know I just need to send you 00:12:07.240 --> 00:12:11.670 align:start position:0% can then I know I just need to send you the<00:12:07.890> messages<00:12:08.890> from<00:12:09.100> Monday<00:12:10.050> what<00:12:11.050> from<00:12:11.290> after 00:12:11.670 --> 00:12:11.680 align:start position:0% the messages from Monday what from after 00:12:11.680 --> 00:12:13.860 align:start position:0% the messages from Monday what from after Sunday<00:12:11.980> so<00:12:12.040> it<00:12:12.790> means<00:12:13.210> we<00:12:13.360> just<00:12:13.390> exchanged 00:12:13.860 --> 00:12:13.870 align:start position:0% Sunday so it means we just exchanged 00:12:13.870 --> 00:12:17.760 align:start position:0% Sunday so it means we just exchanged this<00:12:13.990> one<00:12:14.170> thing<00:12:14.380> and<00:12:16.140> then<00:12:17.140> I<00:12:17.260> just<00:12:17.500> know 00:12:17.760 --> 00:12:17.770 align:start position:0% this one thing and then I just know 00:12:17.770 --> 00:12:20.030 align:start position:0% this one thing and then I just know immediately<00:12:18.010> what<00:12:18.430> you<00:12:18.550> don't<00:12:18.730> have<00:12:18.910> and<00:12:19.120> by 00:12:20.030 --> 00:12:20.040 align:start position:0% immediately what you don't have and by 00:12:20.040 --> 00:12:21.870 align:start position:0% immediately what you don't have and by arranging<00:12:21.040> the<00:12:21.100> message<00:12:21.370> isn't<00:12:21.610> alone<00:12:21.790> in 00:12:21.870 --> 00:12:21.880 align:start position:0% arranging the message isn't alone in 00:12:21.880 --> 00:12:23.760 align:start position:0% arranging the message isn't alone in your<00:12:21.910> audio<00:12:22.330> order<00:12:22.990> it<00:12:23.170> makes<00:12:23.410> that 00:12:23.760 --> 00:12:23.770 align:start position:0% your audio order it makes that 00:12:23.770 --> 00:12:26.370 align:start position:0% your audio order it makes that comparison<00:12:24.430> like<00:12:24.520> completely<00:12:24.970> simple<00:12:25.300> if<00:12:26.200> you 00:12:26.370 --> 00:12:26.380 align:start position:0% comparison like completely simple if you 00:12:26.380 --> 00:12:29.010 align:start position:0% comparison like completely simple if you have<00:12:26.590> like<00:12:26.980> more<00:12:27.160> complicated<00:12:27.760> orderings<00:12:28.630> and 00:12:29.010 --> 00:12:29.020 align:start position:0% have like more complicated orderings and 00:12:29.020 --> 00:12:30.360 align:start position:0% have like more complicated orderings and they<00:12:29.410> if<00:12:29.470> you<00:12:29.560> have<00:12:29.770> some<00:12:29.950> kind<00:12:30.100> of<00:12:30.130> common 00:12:30.360 --> 00:12:30.370 align:start position:0% they if you have some kind of common 00:12:30.370 --> 00:12:31.560 align:start position:0% they if you have some kind of common more<00:12:30.460> complicated<00:12:30.910> structure<00:12:31.180> it<00:12:31.300> becomes 00:12:31.560 --> 00:12:31.570 align:start position:0% more complicated structure it becomes 00:12:31.570 --> 00:12:34.650 align:start position:0% more complicated structure it becomes much<00:12:31.720> much<00:12:31.930> more<00:12:32.170> difficult<00:12:32.560> to<00:12:33.070> do<00:12:33.730> a<00:12:33.760> remote 00:12:34.650 --> 00:12:34.660 align:start position:0% much much more difficult to do a remote 00:12:34.660 --> 00:12:36.270 align:start position:0% much much more difficult to do a remote set<00:12:35.110> comparison<00:12:35.620> but<00:12:35.740> if<00:12:35.860> you<00:12:35.950> may<00:12:36.070> have<00:12:36.100> it 00:12:36.270 --> 00:12:36.280 align:start position:0% set comparison but if you may have it 00:12:36.280 --> 00:12:38.280 align:start position:0% set comparison but if you may have it alone<00:12:36.490> your<00:12:36.670> order<00:12:36.910> it's<00:12:37.330> like<00:12:37.540> did<00:12:37.690> simple<00:12:38.020> so 00:12:38.280 --> 00:12:38.290 align:start position:0% alone your order it's like did simple so 00:12:38.290 --> 00:12:41.850 align:start position:0% alone your order it's like did simple so just<00:12:38.560> like<00:12:40.170> compromise<00:12:41.170> towards<00:12:41.710> the 00:12:41.850 --> 00:12:41.860 align:start position:0% just like compromise towards the 00:12:41.860 --> 00:12:43.860 align:start position:0% just like compromise towards the simplest<00:12:42.160> structure<00:12:42.490> that's<00:12:42.670> easier<00:12:42.970> to<00:12:43.060> be 00:12:43.860 --> 00:12:43.870 align:start position:0% simplest structure that's easier to be 00:12:43.870 --> 00:12:48.540 align:start position:0% simplest structure that's easier to be optimal<00:12:44.230> about<00:12:46.800> so<00:12:47.800> that<00:12:47.980> but<00:12:48.280> that<00:12:48.400> has<00:12:48.520> a 00:12:48.540 --> 00:12:48.550 align:start position:0% optimal about so that but that has a 00:12:48.550 --> 00:12:51.000 align:start position:0% optimal about so that but that has a problem<00:12:48.820> and<00:12:49.090> that<00:12:49.180> if<00:12:49.780> you're<00:12:50.350> having<00:12:50.560> like 00:12:51.000 --> 00:12:51.010 align:start position:0% problem and that if you're having like 00:12:51.010 --> 00:12:52.560 align:start position:0% problem and that if you're having like the<00:12:51.190> original<00:12:51.580> paper<00:12:51.760> that<00:12:51.880> describes<00:12:52.360> this 00:12:52.560 --> 00:12:52.570 align:start position:0% the original paper that describes this 00:12:52.570 --> 00:12:54.240 align:start position:0% the original paper that describes this said<00:12:52.840> that<00:12:52.870> they're<00:12:53.230> probably<00:12:53.380> you<00:12:53.890> know<00:12:53.980> it 00:12:54.240 --> 00:12:54.250 align:start position:0% said that they're probably you know it 00:12:54.250 --> 00:12:56.730 align:start position:0% said that they're probably you know it was<00:12:54.400> designed<00:12:54.700> for<00:12:54.880> used<00:12:55.300> for<00:12:55.840> one<00:12:56.320> cluster 00:12:56.730 --> 00:12:56.740 align:start position:0% was designed for used for one cluster 00:12:56.740 --> 00:12:58.530 align:start position:0% was designed for used for one cluster within<00:12:56.920> a<00:12:57.130> data<00:12:57.310> center<00:12:57.640> so<00:12:58.150> when<00:12:58.330> you'd<00:12:58.420> have 00:12:58.530 --> 00:12:58.540 align:start position:0% within a data center so when you'd have 00:12:58.540 --> 00:13:00.930 align:start position:0% within a data center so when you'd have like<00:12:58.690> a<00:12:58.720> dynamo<00:12:59.380> DB<00:12:59.710> instance<00:12:59.860> that<00:13:00.250> they<00:13:00.760> said 00:13:00.930 --> 00:13:00.940 align:start position:0% like a dynamo DB instance that they said 00:13:00.940 --> 00:13:04.050 align:start position:0% like a dynamo DB instance that they said might<00:13:01.090> have<00:13:01.270> like<00:13:01.420> 300<00:13:01.750> nodes<00:13:02.170> which<00:13:02.950> is<00:13:03.490> maybe 00:13:04.050 --> 00:13:04.060 align:start position:0% might have like 300 nodes which is maybe 00:13:04.060 --> 00:13:06.900 align:start position:0% might have like 300 nodes which is maybe a<00:13:04.180> lot<00:13:04.450> for<00:13:04.780> one<00:13:05.160> you<00:13:06.160> know<00:13:06.190> cluster<00:13:06.580> and<00:13:06.700> a<00:13:06.760> dot 00:13:06.900 --> 00:13:06.910 align:start position:0% a lot for one you know cluster and a dot 00:13:06.910 --> 00:13:08.460 align:start position:0% a lot for one you know cluster and a dot and<00:13:07.060> a<00:13:07.150> data<00:13:07.330> center<00:13:07.600> but<00:13:07.720> there's<00:13:08.140> not<00:13:08.290> a<00:13:08.320> lot 00:13:08.460 --> 00:13:08.470 align:start position:0% and a data center but there's not a lot 00:13:08.470 --> 00:13:09.930 align:start position:0% and a data center but there's not a lot for<00:13:08.500> a<00:13:08.680> peer-to-peer<00:13:08.860> network<00:13:08.890> we<00:13:09.700> want<00:13:09.880> to 00:13:09.930 --> 00:13:09.940 align:start position:0% for a peer-to-peer network we want to 00:13:09.940 --> 00:13:12.630 align:start position:0% for a peer-to-peer network we want to have<00:13:10.030> thousands<00:13:10.480> and<00:13:10.570> thousands<00:13:10.960> of<00:13:11.020> nodes<00:13:11.640> so 00:13:12.630 --> 00:13:12.640 align:start position:0% have thousands and thousands of nodes so 00:13:12.640 --> 00:13:14.730 align:start position:0% have thousands and thousands of nodes so if<00:13:13.150> you<00:13:13.480> have<00:13:13.600> thousands<00:13:13.960> of<00:13:14.080> thousands<00:13:14.440> nodes 00:13:14.730 --> 00:13:14.740 align:start position:0% if you have thousands of thousands nodes 00:13:14.740 --> 00:13:16.380 align:start position:0% if you have thousands of thousands nodes then<00:13:14.950> just<00:13:15.190> sending<00:13:15.490> the<00:13:15.580> victor<00:13:15.880> clock<00:13:16.150> like 00:13:16.380 --> 00:13:16.390 align:start position:0% then just sending the victor clock like 00:13:16.390 --> 00:13:18.960 align:start position:0% then just sending the victor clock like really<00:13:16.660> adds<00:13:16.840> up<00:13:17.370> because<00:13:18.370> you<00:13:18.550> might<00:13:18.700> it 00:13:18.960 --> 00:13:18.970 align:start position:0% really adds up because you might it 00:13:18.970 --> 00:13:20.490 align:start position:0% really adds up because you might it might<00:13:19.150> just<00:13:19.300> be<00:13:19.420> like<00:13:19.540> a<00:13:19.720> public<00:13:20.050> key<00:13:20.230> in<00:13:20.410> a 00:13:20.490 --> 00:13:20.500 align:start position:0% might just be like a public key in a 00:13:20.500 --> 00:13:21.510 align:start position:0% might just be like a public key in a sequence<00:13:20.860> number 00:13:21.510 --> 00:13:21.520 align:start position:0% sequence number 00:13:21.520 --> 00:13:23.520 align:start position:0% sequence number so<00:13:21.640> there<00:13:21.790> might<00:13:21.940> be<00:13:21.970> like<00:13:22.330> 80<00:13:22.810> bytes<00:13:23.050> but<00:13:23.380> then 00:13:23.520 --> 00:13:23.530 align:start position:0% so there might be like 80 bytes but then 00:13:23.530 --> 00:13:25.380 align:start position:0% so there might be like 80 bytes but then if<00:13:23.650> you're<00:13:23.830> sending<00:13:24.070> this<00:13:24.310> for<00:13:24.580> like<00:13:24.820> 3000 00:13:25.380 --> 00:13:25.390 align:start position:0% if you're sending this for like 3000 00:13:25.390 --> 00:13:29.130 align:start position:0% if you're sending this for like 3000 people<00:13:26.040> that<00:13:27.040> is<00:13:27.430> like<00:13:27.730> into<00:13:28.390> like<00:13:28.570> hundreds 00:13:29.130 --> 00:13:29.140 align:start position:0% people that is like into like hundreds 00:13:29.140 --> 00:13:31.320 align:start position:0% people that is like into like hundreds of<00:13:29.200> kilobytes<00:13:29.470> so<00:13:30.370> that<00:13:30.790> means<00:13:30.940> like<00:13:31.120> each 00:13:31.320 --> 00:13:31.330 align:start position:0% of kilobytes so that means like each 00:13:31.330 --> 00:13:33.000 align:start position:0% of kilobytes so that means like each time<00:13:31.390> you<00:13:31.870> can<00:13:32.020> answer<00:13:32.230> you've<00:13:32.500> seen<00:13:32.680> you 00:13:33.000 --> 00:13:33.010 align:start position:0% time you can answer you've seen you 00:13:33.010 --> 00:13:34.350 align:start position:0% time you can answer you've seen you might<00:13:33.160> send<00:13:33.430> like<00:13:33.580> half<00:13:33.730> a<00:13:33.820> megabyte<00:13:34.180> of<00:13:34.240> data 00:13:34.350 --> 00:13:34.360 align:start position:0% might send like half a megabyte of data 00:13:34.360 --> 00:13:38.730 align:start position:0% might send like half a megabyte of data both<00:13:35.170> ways<00:13:35.640> and<00:13:36.640> if<00:13:37.120> you<00:13:37.630> can<00:13:37.870> reconnect<00:13:38.410> and 00:13:38.730 --> 00:13:38.740 align:start position:0% both ways and if you can reconnect and 00:13:38.740 --> 00:13:40.320 align:start position:0% both ways and if you can reconnect and reconnect<00:13:39.190> you<00:13:39.400> could<00:13:39.550> be<00:13:39.700> sending<00:13:39.910> like<00:13:40.090> tens 00:13:40.320 --> 00:13:40.330 align:start position:0% reconnect you could be sending like tens 00:13:40.330 --> 00:13:42.480 align:start position:0% reconnect you could be sending like tens of<00:13:40.510> megabytes<00:13:40.750> a<00:13:41.020> day<00:13:41.200> just<00:13:42.160> to<00:13:42.250> keep<00:13:42.280> the 00:13:42.480 --> 00:13:42.490 align:start position:0% of megabytes a day just to keep the 00:13:42.490 --> 00:13:44.610 align:start position:0% of megabytes a day just to keep the network<00:13:42.670> alive<00:13:43.540> like<00:13:43.780> even<00:13:43.990> if<00:13:44.080> no<00:13:44.200> messages 00:13:44.610 --> 00:13:44.620 align:start position:0% network alive like even if no messages 00:13:44.620 --> 00:13:46.560 align:start position:0% network alive like even if no messages are<00:13:44.800> being<00:13:44.950> sent<00:13:45.190> so<00:13:45.610> that's<00:13:46.090> not<00:13:46.300> really 00:13:46.560 --> 00:13:46.570 align:start position:0% are being sent so that's not really 00:13:46.570 --> 00:13:49.890 align:start position:0% are being sent so that's not really that's<00:13:46.960> not<00:13:47.110> very<00:13:47.350> good<00:13:47.470> at<00:13:47.560> all<00:13:48.030> but<00:13:49.030> one<00:13:49.870> of 00:13:49.890 --> 00:13:49.900 align:start position:0% that's not very good at all but one of 00:13:49.900 --> 00:13:51.420 align:start position:0% that's not very good at all but one of the<00:13:50.080> other<00:13:50.110> secure<00:13:51.100> scuttlebutt 00:13:51.420 --> 00:13:51.430 align:start position:0% the other secure scuttlebutt 00:13:51.430 --> 00:13:54.660 align:start position:0% the other secure scuttlebutt contributors<00:13:52.110> are<00:13:53.110> cell<00:13:53.590> shelves<00:13:54.250> Lin<00:13:54.520> who 00:13:54.660 --> 00:13:54.670 align:start position:0% contributors are cell shelves Lin who 00:13:54.670 --> 00:13:58.980 align:start position:0% contributors are cell shelves Lin who came<00:13:55.270> up<00:13:55.390> with<00:13:55.480> this<00:13:56.050> idea<00:13:56.230> to<00:13:57.450> skip<00:13:58.450> some 00:13:58.980 --> 00:13:58.990 align:start position:0% came up with this idea to skip some 00:13:58.990 --> 00:14:01.340 align:start position:0% came up with this idea to skip some requests<00:13:59.530> so<00:13:59.890> what<00:14:00.490> you<00:14:00.580> do<00:14:00.820> is<00:14:01.000> you<00:14:01.150> just 00:14:01.340 --> 00:14:01.350 align:start position:0% requests so what you do is you just 00:14:01.350 --> 00:14:03.900 align:start position:0% requests so what you do is you just remember<00:14:02.350> the<00:14:02.740> victor<00:14:03.130> clock<00:14:03.340> that<00:14:03.610> the<00:14:03.730> other 00:14:03.900 --> 00:14:03.910 align:start position:0% remember the victor clock that the other 00:14:03.910 --> 00:14:07.050 align:start position:0% remember the victor clock that the other person<00:14:04.270> sent<00:14:04.510> to<00:14:04.600> you<00:14:04.690> and<00:14:05.130> then<00:14:06.130> compare<00:14:06.730> your 00:14:07.050 --> 00:14:07.060 align:start position:0% person sent to you and then compare your 00:14:07.060 --> 00:14:10.980 align:start position:0% person sent to you and then compare your new<00:14:08.050> victor<00:14:09.040> clock<00:14:09.250> to<00:14:09.640> the<00:14:09.790> stored<00:14:10.090> one<00:14:10.330> for 00:14:10.980 --> 00:14:10.990 align:start position:0% new victor clock to the stored one for 00:14:10.990 --> 00:14:13.350 align:start position:0% new victor clock to the stored one for that<00:14:11.110> peer<00:14:11.380> and<00:14:11.620> then<00:14:12.310> just<00:14:12.640> don't<00:14:13.030> mention 00:14:13.350 --> 00:14:13.360 align:start position:0% that peer and then just don't mention 00:14:13.360 --> 00:14:15.630 align:start position:0% that peer and then just don't mention all<00:14:13.750> the<00:14:13.900> things<00:14:14.080> that<00:14:14.230> haven't<00:14:14.470> changed<00:14:14.640> so 00:14:15.630 --> 00:14:15.640 align:start position:0% all the things that haven't changed so 00:14:15.640 --> 00:14:20.160 align:start position:0% all the things that haven't changed so if<00:14:16.480> I<00:14:17.310> if<00:14:18.310> we<00:14:18.340> meet<00:14:18.640> on<00:14:18.850> Sunday<00:14:19.630> and<00:14:19.900> we 00:14:20.160 --> 00:14:20.170 align:start position:0% if I if we meet on Sunday and we 00:14:20.170 --> 00:14:23.880 align:start position:0% if I if we meet on Sunday and we exchange<00:14:20.650> news<00:14:20.920> about<00:14:21.220> Carol<00:14:22.120> and<00:14:22.620> then<00:14:23.620> we 00:14:23.880 --> 00:14:23.890 align:start position:0% exchange news about Carol and then we 00:14:23.890 --> 00:14:25.860 align:start position:0% exchange news about Carol and then we meet<00:14:24.070> each<00:14:24.250> other<00:14:24.460> again<00:14:24.550> on<00:14:24.940> Wednesday<00:14:25.450> and 00:14:25.860 --> 00:14:25.870 align:start position:0% meet each other again on Wednesday and 00:14:25.870 --> 00:14:27.750 align:start position:0% meet each other again on Wednesday and neither<00:14:26.140> of<00:14:26.320> us<00:14:26.350> will<00:14:26.680> have<00:14:26.890> talked<00:14:27.160> to<00:14:27.430> Carol 00:14:27.750 --> 00:14:27.760 align:start position:0% neither of us will have talked to Carol 00:14:27.760 --> 00:14:29.640 align:start position:0% neither of us will have talked to Carol since<00:14:28.120> then<00:14:28.330> then<00:14:29.080> we<00:14:29.230> just<00:14:29.350> don't<00:14:29.530> mention 00:14:29.640 --> 00:14:29.650 align:start position:0% since then then we just don't mention 00:14:29.650 --> 00:14:32.880 align:start position:0% since then then we just don't mention Carol<00:14:30.640> and<00:14:30.990> because<00:14:31.990> we<00:14:32.110> know<00:14:32.230> that<00:14:32.260> if<00:14:32.530> so<00:14:32.740> if 00:14:32.880 --> 00:14:32.890 align:start position:0% Carol and because we know that if so if 00:14:32.890 --> 00:14:34.890 align:start position:0% Carol and because we know that if so if the<00:14:33.010> other<00:14:33.070> person<00:14:33.400> did<00:14:33.700> they<00:14:34.540> would<00:14:34.720> mention 00:14:34.890 --> 00:14:34.900 align:start position:0% the other person did they would mention 00:14:34.900 --> 00:14:37.590 align:start position:0% the other person did they would mention her<00:14:35.110> so<00:14:36.100> that<00:14:36.670> means<00:14:36.880> that<00:14:37.090> you<00:14:37.210> can<00:14:37.390> just 00:14:37.590 --> 00:14:37.600 align:start position:0% her so that means that you can just 00:14:37.600 --> 00:14:40.710 align:start position:0% her so that means that you can just leave<00:14:38.050> out<00:14:38.350> most<00:14:39.280> of<00:14:39.520> the<00:14:39.700> victor<00:14:40.000> clog<00:14:40.240> and 00:14:40.710 --> 00:14:40.720 align:start position:0% leave out most of the victor clog and 00:14:40.720 --> 00:14:42.360 align:start position:0% leave out most of the victor clog and you<00:14:41.320> just<00:14:41.470> don't<00:14:41.590> mention<00:14:41.830> most<00:14:42.100> of<00:14:42.310> the 00:14:42.360 --> 00:14:42.370 align:start position:0% you just don't mention most of the 00:14:42.370 --> 00:14:43.830 align:start position:0% you just don't mention most of the things<00:14:42.550> that<00:14:42.730> have<00:14:42.850> changed<00:14:42.880> that<00:14:43.240> all<00:14:43.660> the 00:14:43.830 --> 00:14:43.840 align:start position:0% things that have changed that all the 00:14:43.840 --> 00:14:45.060 align:start position:0% things that have changed that all the things<00:14:44.020> that<00:14:44.110> you<00:14:44.260> think<00:14:44.470> probably<00:14:44.860> haven't 00:14:45.060 --> 00:14:45.070 align:start position:0% things that you think probably haven't 00:14:45.070 --> 00:14:47.790 align:start position:0% things that you think probably haven't changed<00:14:45.370> and<00:14:45.580> then<00:14:46.420> if<00:14:46.540> you<00:14:46.690> find<00:14:46.900> out<00:14:47.140> if<00:14:47.410> some 00:14:47.790 --> 00:14:47.800 align:start position:0% changed and then if you find out if some 00:14:47.800 --> 00:14:49.620 align:start position:0% changed and then if you find out if some fella<00:14:48.130> person<00:14:48.430> does<00:14:48.610> mention<00:14:48.850> it<00:14:49.090> then<00:14:49.480> you 00:14:49.620 --> 00:14:49.630 align:start position:0% fella person does mention it then you 00:14:49.630 --> 00:14:53.820 align:start position:0% fella person does mention it then you just<00:14:49.840> reply<00:14:50.170> with<00:14:50.590> like<00:14:51.000> your<00:14:52.000> partial<00:14:52.830> figure 00:14:53.820 --> 00:14:53.830 align:start position:0% just reply with like your partial figure 00:14:53.830 --> 00:14:56.360 align:start position:0% just reply with like your partial figure clock<00:14:54.070> of<00:14:54.220> the<00:14:54.340> things<00:14:54.520> that<00:14:54.760> that<00:14:55.480> didn't 00:14:56.360 --> 00:14:56.370 align:start position:0% clock of the things that that didn't 00:14:56.370 --> 00:15:08.960 align:start position:0% clock of the things that that didn't didn't<00:14:57.370> change<00:15:00.420> yep<00:15:01.450> so<00:15:01.690> I<00:15:01.720> had 00:15:08.960 --> 00:15:08.970 align:start position:0% 00:15:08.970 --> 00:15:11.820 align:start position:0% yeah<00:15:09.970> yeah<00:15:10.420> this<00:15:10.630> is<00:15:10.690> this<00:15:11.050> is<00:15:11.110> this<00:15:11.470> is<00:15:11.620> really 00:15:11.820 --> 00:15:11.830 align:start position:0% yeah yeah this is this is this is really 00:15:11.830 --> 00:15:13.500 align:start position:0% yeah yeah this is this is this is really important<00:15:12.100> because<00:15:12.160> when<00:15:12.970> when<00:15:13.300> you<00:15:13.360> have 00:15:13.500 --> 00:15:13.510 align:start position:0% important because when when you have 00:15:13.510 --> 00:15:16.800 align:start position:0% important because when when you have like<00:15:13.720> a<00:15:13.930> people<00:15:14.500> using<00:15:15.150> uni<00:15:16.150> pretty<00:15:16.450> much<00:15:16.630> any 00:15:16.800 --> 00:15:16.810 align:start position:0% like a people using uni pretty much any 00:15:16.810 --> 00:15:19.410 align:start position:0% like a people using uni pretty much any kind<00:15:17.020> of<00:15:17.080> application<00:15:17.590> you<00:15:17.880> power<00:15:18.880> laws<00:15:19.180> are 00:15:19.410 --> 00:15:19.420 align:start position:0% kind of application you power laws are 00:15:19.420 --> 00:15:21.540 align:start position:0% kind of application you power laws are really<00:15:19.540> typical<00:15:20.530> so<00:15:20.710> you're<00:15:20.890> really<00:15:21.220> likely 00:15:21.540 --> 00:15:21.550 align:start position:0% really typical so you're really likely 00:15:21.550 --> 00:15:23.760 align:start position:0% really typical so you're really likely to<00:15:21.670> have<00:15:21.850> some<00:15:22.390> users<00:15:22.630> that<00:15:22.960> are<00:15:23.110> like<00:15:23.320> really 00:15:23.760 --> 00:15:23.770 align:start position:0% to have some users that are like really 00:15:23.770 --> 00:15:28.800 align:start position:0% to have some users that are like really active<00:15:25.770> you<00:15:26.770> know<00:15:26.830> use<00:15:27.760> every<00:15:28.090> day<00:15:28.210> or<00:15:28.450> posting 00:15:28.800 --> 00:15:28.810 align:start position:0% active you know use every day or posting 00:15:28.810 --> 00:15:31.440 align:start position:0% active you know use every day or posting you<00:15:28.960> know<00:15:29.350> constantly<00:15:29.800> you<00:15:30.760> have<00:15:30.940> like<00:15:31.180> some 00:15:31.440 --> 00:15:31.450 align:start position:0% you know constantly you have like some 00:15:31.450 --> 00:15:34.110 align:start position:0% you know constantly you have like some users<00:15:32.080> that<00:15:32.110> are<00:15:32.350> like<00:15:32.500> daily<00:15:33.250> a<00:15:33.490> fair<00:15:34.030> amount 00:15:34.110 --> 00:15:34.120 align:start position:0% users that are like daily a fair amount 00:15:34.120 --> 00:15:36.240 align:start position:0% users that are like daily a fair amount of<00:15:34.420> light<00:15:34.630> moderate<00:15:35.050> users<00:15:35.560> and<00:15:35.770> then<00:15:36.010> like 00:15:36.240 --> 00:15:36.250 align:start position:0% of light moderate users and then like 00:15:36.250 --> 00:15:38.430 align:start position:0% of light moderate users and then like heaps<00:15:36.760> and<00:15:37.000> heaps<00:15:37.090> of<00:15:37.360> like<00:15:37.600> people<00:15:38.110> that<00:15:38.290> only 00:15:38.430 --> 00:15:38.440 align:start position:0% heaps and heaps of like people that only 00:15:38.440 --> 00:15:39.930 align:start position:0% heaps and heaps of like people that only use<00:15:38.620> it<00:15:38.740> occasionally<00:15:38.980> or<00:15:39.400> even<00:15:39.580> signed<00:15:39.820> up 00:15:39.930 --> 00:15:39.940 align:start position:0% use it occasionally or even signed up 00:15:39.940 --> 00:15:42.630 align:start position:0% use it occasionally or even signed up and<00:15:40.090> never<00:15:40.240> used<00:15:40.420> it<00:15:40.600> again<00:15:41.320> and<00:15:41.680> you<00:15:42.460> don't 00:15:42.630 --> 00:15:42.640 align:start position:0% and never used it again and you don't 00:15:42.640 --> 00:15:44.400 align:start position:0% and never used it again and you don't want<00:15:42.790> to<00:15:42.850> be<00:15:42.970> wasting<00:15:43.270> bandwidth<00:15:43.630> on<00:15:43.990> people 00:15:44.400 --> 00:15:44.410 align:start position:0% want to be wasting bandwidth on people 00:15:44.410 --> 00:15:45.990 align:start position:0% want to be wasting bandwidth on people they<00:15:44.530> haven't<00:15:44.710> done<00:15:44.860> anything<00:15:44.920> in<00:15:45.490> a<00:15:45.580> while<00:15:45.760> so 00:15:45.990 --> 00:15:46.000 align:start position:0% they haven't done anything in a while so 00:15:46.000 --> 00:15:48.630 align:start position:0% they haven't done anything in a while so this<00:15:46.510> this<00:15:47.350> simple<00:15:47.530> technique<00:15:48.220> allows<00:15:48.430> you<00:15:48.460> to 00:15:48.630 --> 00:15:48.640 align:start position:0% this this simple technique allows you to 00:15:48.640 --> 00:15:51.930 align:start position:0% this this simple technique allows you to completely<00:15:48.970> cut<00:15:49.180> out<00:15:49.350> all<00:15:50.350> of<00:15:50.410> that<00:15:50.530> stuff<00:15:51.280> and 00:15:51.930 --> 00:15:51.940 align:start position:0% completely cut out all of that stuff and 00:15:51.940 --> 00:15:54.630 align:start position:0% completely cut out all of that stuff and that<00:15:52.450> basically<00:15:52.810> gives<00:15:52.900> you<00:15:53.170> an<00:15:53.290> end<00:15:53.620> so<00:15:54.190> basic 00:15:54.630 --> 00:15:54.640 align:start position:0% that basically gives you an end so basic 00:15:54.640 --> 00:15:56.880 align:start position:0% that basically gives you an end so basic basic<00:15:55.360> skill<00:15:55.540> about<00:15:55.750> the<00:15:55.900> message<00:15:56.500> over<00:15:56.680> here 00:15:56.880 --> 00:15:56.890 align:start position:0% basic skill about the message over here 00:15:56.890 --> 00:15:59.070 align:start position:0% basic skill about the message over here per<00:15:57.160> connection<00:15:57.490> was<00:15:58.270> like<00:15:58.450> the<00:15:58.600> messages 00:15:59.070 --> 00:15:59.080 align:start position:0% per connection was like the messages 00:15:59.080 --> 00:16:03.060 align:start position:0% per connection was like the messages plus<00:15:59.590> the<00:16:00.400> feeds<00:16:00.670> and<00:16:01.230> if<00:16:02.230> no<00:16:02.470> messages<00:16:02.890> have 00:16:03.060 --> 00:16:03.070 align:start position:0% plus the feeds and if no messages have 00:16:03.070 --> 00:16:04.530 align:start position:0% plus the feeds and if no messages have changed<00:16:03.400> the<00:16:03.520> messages<00:16:03.880> might<00:16:04.030> be<00:16:04.150> 0<00:16:04.360> but 00:16:04.530 --> 00:16:04.540 align:start position:0% changed the messages might be 0 but 00:16:04.540 --> 00:16:06.420 align:start position:0% changed the messages might be 0 but feeds<00:16:04.780> could<00:16:05.020> be<00:16:05.110> thousands<00:16:05.530> but<00:16:06.160> secure 00:16:06.420 --> 00:16:06.430 align:start position:0% feeds could be thousands but secure 00:16:06.430 --> 00:16:08.910 align:start position:0% feeds could be thousands but secure scuttlebutt<00:16:06.820> is<00:16:07.030> messages<00:16:07.660> plus<00:16:08.320> updated 00:16:08.910 --> 00:16:08.920 align:start position:0% scuttlebutt is messages plus updated 00:16:08.920 --> 00:16:11.280 align:start position:0% scuttlebutt is messages plus updated feeds<00:16:09.160> an<00:16:09.700> updated<00:16:10.570> feeds<00:16:10.750> could<00:16:10.990> be<00:16:11.110> much 00:16:11.280 --> 00:16:11.290 align:start position:0% feeds an updated feeds could be much 00:16:11.290 --> 00:16:13.470 align:start position:0% feeds an updated feeds could be much much<00:16:11.470> smaller<00:16:11.530> number<00:16:12.130> usually<00:16:13.000> it<00:16:13.090> would<00:16:13.330> be 00:16:13.470 --> 00:16:13.480 align:start position:0% much smaller number usually it would be 00:16:13.480 --> 00:16:14.940 align:start position:0% much smaller number usually it would be like<00:16:13.660> if<00:16:13.750> you<00:16:13.780> reconnect<00:16:14.290> frequent<00:16:14.620> like 00:16:14.940 --> 00:16:14.950 align:start position:0% like if you reconnect frequent like 00:16:14.950 --> 00:16:16.710 align:start position:0% like if you reconnect frequent like frequently<00:16:15.460> number<00:16:16.150> could<00:16:16.270> be<00:16:16.330> like<00:16:16.540> will<00:16:16.690> be 00:16:16.710 --> 00:16:16.720 align:start position:0% frequently number could be like will be 00:16:16.720 --> 00:16:20.610 align:start position:0% frequently number could be like will be close<00:16:16.960> to<00:16:16.990> 0<00:16:17.350> if<00:16:18.340> you<00:16:19.150> reconnect<00:16:19.690> months<00:16:20.410> later 00:16:20.610 --> 00:16:20.620 align:start position:0% close to 0 if you reconnect months later 00:16:20.620 --> 00:16:24.630 align:start position:0% close to 0 if you reconnect months later it<00:16:20.890> will<00:16:21.040> just<00:16:21.220> be<00:16:21.460> you<00:16:22.330> might<00:16:22.480> get<00:16:23.640> individual 00:16:24.630 --> 00:16:24.640 align:start position:0% it will just be you might get individual 00:16:24.640 --> 00:16:26.940 align:start position:0% it will just be you might get individual users<00:16:24.880> might<00:16:25.030> have<00:16:25.180> posted<00:16:25.770> hundreds<00:16:26.770> of 00:16:26.940 --> 00:16:26.950 align:start position:0% users might have posted hundreds of 00:16:26.950 --> 00:16:29.850 align:start position:0% users might have posted hundreds of messages<00:16:27.760> but<00:16:27.970> over<00:16:28.540> here<00:16:28.690> is<00:16:28.960> just<00:16:29.230> one<00:16:29.470> for 00:16:29.850 --> 00:16:29.860 align:start position:0% messages but over here is just one for 00:16:29.860 --> 00:16:33.180 align:start position:0% messages but over here is just one for that<00:16:29.950> updated<00:16:30.310> fade<00:16:31.980> which<00:16:32.980> makes 00:16:33.180 --> 00:16:33.190 align:start position:0% that updated fade which makes 00:16:33.190 --> 00:16:35.280 align:start position:0% that updated fade which makes reconnections<00:16:33.850> very<00:16:34.060> cheap<00:16:34.240> and<00:16:34.510> the<00:16:35.140> only 00:16:35.280 --> 00:16:35.290 align:start position:0% reconnections very cheap and the only 00:16:35.290 --> 00:16:37.920 align:start position:0% reconnections very cheap and the only time<00:16:35.470> you<00:16:35.650> have<00:16:35.770> to<00:16:35.890> pay<00:16:36.040> the<00:16:36.190> whole<00:16:36.750> send<00:16:37.750> all 00:16:37.920 --> 00:16:37.930 align:start position:0% time you have to pay the whole send all 00:16:37.930 --> 00:16:41.970 align:start position:0% time you have to pay the whole send all of<00:16:37.960> the<00:16:38.230> feeds<00:16:38.470> as<00:16:38.770> when<00:16:39.220> you<00:16:39.880> have<00:16:39.910> a<00:16:40.890> when<00:16:41.890> you 00:16:41.970 --> 00:16:41.980 align:start position:0% of the feeds as when you have a when you 00:16:41.980 --> 00:16:46.490 align:start position:0% of the feeds as when you have a when you win<00:16:42.400> the<00:16:42.580> first<00:16:42.910> time<00:16:43.090> that<00:16:43.270> to<00:16:43.360> peers<00:16:43.600> connect 00:16:46.490 --> 00:16:46.500 align:start position:0% 00:16:46.500 --> 00:16:48.930 align:start position:0% yes<00:16:47.500> this<00:16:47.650> for<00:16:47.860> good<00:16:47.980> and<00:16:48.100> the<00:16:48.280> light<00:16:48.460> and<00:16:48.820> the 00:16:48.930 --> 00:16:48.940 align:start position:0% yes this for good and the light and the 00:16:48.940 --> 00:16:53.220 align:start position:0% yes this for good and the light and the latency<00:16:49.830> complexity<00:16:50.830> is<00:16:51.040> just<00:16:51.960> you<00:16:52.960> can 00:16:53.220 --> 00:16:53.230 align:start position:0% latency complexity is just you can 00:16:53.230 --> 00:16:54.960 align:start position:0% latency complexity is just you can you're<00:16:53.560> replicating<00:16:53.770> in<00:16:54.130> either<00:16:54.250> one<00:16:54.490> or<00:16:54.520> two 00:16:54.960 --> 00:16:54.970 align:start position:0% you're replicating in either one or two 00:16:54.970 --> 00:16:57.210 align:start position:0% you're replicating in either one or two round<00:16:55.210> trips<00:16:55.480> so<00:16:56.200> one<00:16:56.380> round<00:16:56.590> trip<00:16:56.740> if<00:16:57.040> you've 00:16:57.210 --> 00:16:57.220 align:start position:0% round trips so one round trip if you've 00:16:57.220 --> 00:16:59.300 align:start position:0% round trips so one round trip if you've seen<00:16:57.580> if<00:16:57.880> you've<00:16:58.060> sent<00:16:58.270> the<00:16:58.360> whole<00:16:58.510> clock<00:16:58.780> and 00:16:59.300 --> 00:16:59.310 align:start position:0% seen if you've sent the whole clock and 00:16:59.310 --> 00:17:02.130 align:start position:0% seen if you've sent the whole clock and they<00:17:00.310> then<00:17:00.610> seen<00:17:00.820> the<00:17:00.910> messages<00:17:01.270> but<00:17:01.840> if<00:17:01.960> they 00:17:02.130 --> 00:17:02.140 align:start position:0% they then seen the messages but if they 00:17:02.140 --> 00:17:04.350 align:start position:0% they then seen the messages but if they send<00:17:02.410> a<00:17:02.500> putt<00:17:02.710> if<00:17:03.010> they<00:17:03.190> or<00:17:03.490> if<00:17:03.730> they<00:17:03.850> don't<00:17:04.089> or 00:17:04.350 --> 00:17:04.360 align:start position:0% send a putt if they or if they don't or 00:17:04.360 --> 00:17:05.790 align:start position:0% send a putt if they or if they don't or if<00:17:04.660> the<00:17:04.870> messages<00:17:05.290> that<00:17:05.350> you<00:17:05.530> haven't 00:17:05.790 --> 00:17:05.800 align:start position:0% if the messages that you haven't 00:17:05.800 --> 00:17:07.770 align:start position:0% if the messages that you haven't mentioned<00:17:05.949> haven't<00:17:06.400> updated<00:17:06.520> then<00:17:07.390> it's<00:17:07.600> one 00:17:07.770 --> 00:17:07.780 align:start position:0% mentioned haven't updated then it's one 00:17:07.780 --> 00:17:10.890 align:start position:0% mentioned haven't updated then it's one round<00:17:07.930> trip<00:17:08.110> and<00:17:08.439> if<00:17:09.339> you<00:17:09.760> send<00:17:10.449> a<00:17:10.569> message 00:17:10.890 --> 00:17:10.900 align:start position:0% round trip and if you send a message 00:17:10.900 --> 00:17:12.840 align:start position:0% round trip and if you send a message have<00:17:11.589> you<00:17:11.680> seen<00:17:11.920> a<00:17:11.949> partial<00:17:12.250> victory<00:17:12.370> if<00:17:12.760> they 00:17:12.840 --> 00:17:12.850 align:start position:0% have you seen a partial victory if they 00:17:12.850 --> 00:17:14.069 align:start position:0% have you seen a partial victory if they send<00:17:13.060> a<00:17:13.089> partial<00:17:13.390> victor<00:17:13.600> clock<00:17:13.780> and<00:17:13.930> then<00:17:14.020> you 00:17:14.069 --> 00:17:14.079 align:start position:0% send a partial victor clock and then you 00:17:14.079 --> 00:17:15.390 align:start position:0% send a partial victor clock and then you have<00:17:14.199> to<00:17:14.319> have<00:17:14.410> seen<00:17:14.530> one<00:17:14.650> back<00:17:14.829> you<00:17:15.040> know<00:17:15.310> it's 00:17:15.390 --> 00:17:15.400 align:start position:0% have to have seen one back you know it's 00:17:15.400 --> 00:17:20.340 align:start position:0% have to have seen one back you know it's two<00:17:15.550> round<00:17:15.760> trips<00:17:16.199> but<00:17:17.199> my<00:17:19.260> back 00:17:20.340 --> 00:17:20.350 align:start position:0% two round trips but my back 00:17:20.350 --> 00:17:24.720 align:start position:0% two round trips but my back since<00:17:21.120> now<00:17:22.120> basically<00:17:22.360> improvising<00:17:23.520> so<00:17:24.520> like 00:17:24.720 --> 00:17:24.730 align:start position:0% since now basically improvising so like 00:17:24.730 --> 00:17:26.939 align:start position:0% since now basically improvising so like I<00:17:24.939> became<00:17:25.780> interest<00:17:26.230> in<00:17:26.319> this<00:17:26.439> because<00:17:26.620> I<00:17:26.799> was 00:17:26.939 --> 00:17:26.949 align:start position:0% I became interest in this because I was 00:17:26.949 --> 00:17:28.260 align:start position:0% I became interest in this because I was living<00:17:27.309> on<00:17:27.520> a<00:17:27.549> sailboat 00:17:28.260 --> 00:17:28.270 align:start position:0% living on a sailboat 00:17:28.270 --> 00:17:31.080 align:start position:0% living on a sailboat in<00:17:28.569> New<00:17:28.809> Zealand<00:17:28.840> and<00:17:29.380> I<00:17:29.980> was<00:17:30.490> used<00:17:30.730> to<00:17:30.850> like 00:17:31.080 --> 00:17:31.090 align:start position:0% in New Zealand and I was used to like 00:17:31.090 --> 00:17:34.080 align:start position:0% in New Zealand and I was used to like like<00:17:31.750> my<00:17:32.410> normal<00:17:32.830> thing<00:17:33.160> was<00:17:33.490> not<00:17:33.640> having<00:17:33.820> very 00:17:34.080 --> 00:17:34.090 align:start position:0% like my normal thing was not having very 00:17:34.090 --> 00:17:35.880 align:start position:0% like my normal thing was not having very good<00:17:34.120> Anson<00:17:34.510> it<00:17:34.630> at<00:17:34.809> the<00:17:34.900> time<00:17:35.080> when<00:17:35.679> I<00:17:35.710> first 00:17:35.880 --> 00:17:35.890 align:start position:0% good Anson it at the time when I first 00:17:35.890 --> 00:17:37.140 align:start position:0% good Anson it at the time when I first became<00:17:36.070> interested<00:17:36.280> this<00:17:36.580> I<00:17:36.760> didn't<00:17:37.059> actually 00:17:37.140 --> 00:17:37.150 align:start position:0% became interested this I didn't actually 00:17:37.150 --> 00:17:40.039 align:start position:0% became interested this I didn't actually have<00:17:37.360> any<00:17:37.480> any<00:17:37.840> aunts<00:17:38.080> name<00:17:38.230> of<00:17:38.289> my<00:17:38.410> boat<00:17:38.530> and<00:17:38.830> I 00:17:40.039 --> 00:17:40.049 align:start position:0% have any any aunts name of my boat and I 00:17:40.049 --> 00:17:43.620 align:start position:0% have any any aunts name of my boat and I was<00:17:41.049> like<00:17:41.289> why<00:17:41.440> can't<00:17:41.710> that<00:17:42.070> be<00:17:42.210> like<00:17:43.210> why<00:17:43.450> does 00:17:43.620 --> 00:17:43.630 align:start position:0% was like why can't that be like why does 00:17:43.630 --> 00:17:45.390 align:start position:0% was like why can't that be like why does that<00:17:43.660> mean<00:17:43.990> that<00:17:44.230> I<00:17:44.470> can't<00:17:44.830> use<00:17:45.010> my<00:17:45.160> computer 00:17:45.390 --> 00:17:45.400 align:start position:0% that mean that I can't use my computer 00:17:45.400 --> 00:17:47.070 align:start position:0% that mean that I can't use my computer you<00:17:46.030> should<00:17:46.059> be<00:17:46.270> a<00:17:46.330> user<00:17:46.570> view<00:17:46.720> of<00:17:46.780> computer<00:17:47.049> I 00:17:47.070 --> 00:17:47.080 align:start position:0% you should be a user view of computer I 00:17:47.080 --> 00:17:49.140 align:start position:0% you should be a user view of computer I also<00:17:47.200> grew<00:17:47.440> up<00:17:47.530> on<00:17:47.620> a<00:17:47.679> farm<00:17:47.860> in<00:17:48.190> New<00:17:48.610> Zealand<00:17:48.970> we 00:17:49.140 --> 00:17:49.150 align:start position:0% also grew up on a farm in New Zealand we 00:17:49.150 --> 00:17:51.299 align:start position:0% also grew up on a farm in New Zealand we are<00:17:49.240> the<00:17:49.330> best<00:17:49.660> internet<00:17:50.140> we<00:17:50.260> have<00:17:50.289> we<00:17:50.559> had<00:17:50.740> was 00:17:51.299 --> 00:17:51.309 align:start position:0% are the best internet we have we had was 00:17:51.309 --> 00:17:52.919 align:start position:0% are the best internet we have we had was like<00:17:51.549> a<00:17:51.610> satellite<00:17:51.940> and<00:17:52.210> snare<00:17:52.419> that<00:17:52.450> had<00:17:52.750> like 00:17:52.919 --> 00:17:52.929 align:start position:0% like a satellite and snare that had like 00:17:52.929 --> 00:17:57.810 align:start position:0% like a satellite and snare that had like a<00:17:53.169> one-second<00:17:54.159> round<00:17:54.669> trip<00:17:56.429> which<00:17:57.429> is<00:17:57.610> like 00:17:57.810 --> 00:17:57.820 align:start position:0% a one-second round trip which is like 00:17:57.820 --> 00:17:59.100 align:start position:0% a one-second round trip which is like you<00:17:58.059> know<00:17:58.150> it<00:17:58.360> shouldn't<00:17:58.630> really<00:17:58.690> take<00:17:58.929> that 00:17:59.100 --> 00:17:59.110 align:start position:0% you know it shouldn't really take that 00:17:59.110 --> 00:18:01.169 align:start position:0% you know it shouldn't really take that by<00:17:59.260> that<00:17:59.740> long<00:17:59.950> that<00:18:00.280> long<00:18:00.490> for<00:18:00.700> light<00:18:00.850> to 00:18:01.169 --> 00:18:01.179 align:start position:0% by that long that long for light to 00:18:01.179 --> 00:18:05.490 align:start position:0% by that long that long for light to travel<00:18:01.210> but<00:18:01.840> it<00:18:02.350> has<00:18:02.850> like<00:18:03.850> I<00:18:04.059> don't<00:18:04.150> know<00:18:04.500> lots 00:18:05.490 --> 00:18:05.500 align:start position:0% travel but it has like I don't know lots 00:18:05.500 --> 00:18:07.169 align:start position:0% travel but it has like I don't know lots of<00:18:05.620> switching<00:18:06.429> packets<00:18:06.789> and<00:18:06.909> that's<00:18:07.030> that 00:18:07.169 --> 00:18:07.179 align:start position:0% of switching packets and that's that 00:18:07.179 --> 00:18:09.630 align:start position:0% of switching packets and that's that other<00:18:07.240> stuff<00:18:07.419> so<00:18:08.020> I<00:18:08.350> was<00:18:09.159> really<00:18:09.400> determined 00:18:09.630 --> 00:18:09.640 align:start position:0% other stuff so I was really determined 00:18:09.640 --> 00:18:14.850 align:start position:0% other stuff so I was really determined to<00:18:11.400> like<00:18:12.400> latency<00:18:13.179> is<00:18:13.419> really<00:18:13.929> a<00:18:14.049> killer<00:18:14.260> like 00:18:14.850 --> 00:18:14.860 align:start position:0% to like latency is really a killer like 00:18:14.860 --> 00:18:17.340 align:start position:0% to like latency is really a killer like if<00:18:15.039> you<00:18:15.220> and<00:18:15.730> if<00:18:16.090> you<00:18:16.480> live<00:18:16.659> in<00:18:16.780> like<00:18:16.929> a<00:18:16.960> fancy 00:18:17.340 --> 00:18:17.350 align:start position:0% if you and if you live in like a fancy 00:18:17.350 --> 00:18:19.440 align:start position:0% if you and if you live in like a fancy place<00:18:17.679> that<00:18:18.280> has<00:18:18.460> fiber<00:18:18.789> and<00:18:19.120> that<00:18:19.210> sort<00:18:19.419> of 00:18:19.440 --> 00:18:19.450 align:start position:0% place that has fiber and that sort of 00:18:19.450 --> 00:18:21.870 align:start position:0% place that has fiber and that sort of stuff<00:18:19.630> then<00:18:19.780> latency<00:18:20.230> you<00:18:20.740> might<00:18:20.950> not<00:18:21.700> better 00:18:21.870 --> 00:18:21.880 align:start position:0% stuff then latency you might not better 00:18:21.880 --> 00:18:23.130 align:start position:0% stuff then latency you might not better notice<00:18:22.240> it<00:18:22.390> and<00:18:22.510> a<00:18:22.570> couple<00:18:22.750> of<00:18:22.870> each<00:18:22.990> two 00:18:23.130 --> 00:18:23.140 align:start position:0% notice it and a couple of each two 00:18:23.140 --> 00:18:25.320 align:start position:0% notice it and a couple of each two round-trips<00:18:23.559> might<00:18:24.250> not<00:18:24.370> be<00:18:24.460> there<00:18:24.610> bad<00:18:24.820> but 00:18:25.320 --> 00:18:25.330 align:start position:0% round-trips might not be there bad but 00:18:25.330 --> 00:18:27.840 align:start position:0% round-trips might not be there bad but when<00:18:25.960> latency<00:18:26.470> gets<00:18:26.710> bad<00:18:26.950> it<00:18:27.190> gets<00:18:27.309> really<00:18:27.580> bad 00:18:27.840 --> 00:18:27.850 align:start position:0% when latency gets bad it gets really bad 00:18:27.850 --> 00:18:30.390 align:start position:0% when latency gets bad it gets really bad and<00:18:28.120> if<00:18:28.270> you<00:18:28.390> have<00:18:28.570> a<00:18:28.960> design<00:18:29.860> with<00:18:30.220> that 00:18:30.390 --> 00:18:30.400 align:start position:0% and if you have a design with that 00:18:30.400 --> 00:18:32.430 align:start position:0% and if you have a design with that scenes<00:18:31.059> a<00:18:31.270> lot<00:18:31.539> of<00:18:31.690> packets<00:18:31.929> back<00:18:32.110> and<00:18:32.260> forth 00:18:32.430 --> 00:18:32.440 align:start position:0% scenes a lot of packets back and forth 00:18:32.440 --> 00:18:33.870 align:start position:0% scenes a lot of packets back and forth then<00:18:32.679> it's<00:18:32.860> going<00:18:32.980> to<00:18:33.039> be<00:18:33.130> really<00:18:33.520> really 00:18:33.870 --> 00:18:33.880 align:start position:0% then it's going to be really really 00:18:33.880 --> 00:18:36.000 align:start position:0% then it's going to be really really painful<00:18:34.059> to<00:18:34.360> use<00:18:34.510> in<00:18:34.630> that<00:18:34.659> situation<00:18:35.320> so<00:18:35.860> it's 00:18:36.000 --> 00:18:36.010 align:start position:0% painful to use in that situation so it's 00:18:36.010 --> 00:18:38.250 align:start position:0% painful to use in that situation so it's determined<00:18:36.580> to<00:18:36.909> have<00:18:37.150> like<00:18:37.630> a<00:18:37.659> constant 00:18:38.250 --> 00:18:38.260 align:start position:0% determined to have like a constant 00:18:38.260 --> 00:18:41.460 align:start position:0% determined to have like a constant number<00:18:38.409> of<00:18:38.770> round<00:18:39.100> rubs<00:18:39.659> so<00:18:40.659> one<00:18:41.020> or<00:18:41.140> two<00:18:41.169> round 00:18:41.460 --> 00:18:41.470 align:start position:0% number of round rubs so one or two round 00:18:41.470 --> 00:18:43.590 align:start position:0% number of round rubs so one or two round trips<00:18:41.740> I<00:18:41.980> think<00:18:42.250> is<00:18:42.400> like<00:18:42.700> about<00:18:43.000> how<00:18:43.179> much<00:18:43.360> you 00:18:43.590 --> 00:18:43.600 align:start position:0% trips I think is like about how much you 00:18:43.600 --> 00:18:45.870 align:start position:0% trips I think is like about how much you can<00:18:43.780> I<00:18:44.440> can<00:18:44.770> tolerate<00:18:44.919> for<00:18:45.460> a<00:18:45.490> replication 00:18:45.870 --> 00:18:45.880 align:start position:0% can I can tolerate for a replication 00:18:45.880 --> 00:18:51.240 align:start position:0% can I can tolerate for a replication protocol<00:18:47.400> logarithmic<00:18:48.400> round<00:18:49.030> trips<00:18:49.299> not<00:18:50.250> not 00:18:51.240 --> 00:18:51.250 align:start position:0% protocol logarithmic round trips not not 00:18:51.250 --> 00:18:52.860 align:start position:0% protocol logarithmic round trips not not acceptable<00:18:51.669> it's<00:18:52.299> going<00:18:52.480> to<00:18:52.539> be<00:18:52.659> really 00:18:52.860 --> 00:18:52.870 align:start position:0% acceptable it's going to be really 00:18:52.870 --> 00:19:02.100 align:start position:0% acceptable it's going to be really painful<00:18:53.370> in<00:18:54.370> in<00:18:54.850> many<00:18:55.510> cases<00:18:57.630> so<00:19:00.150> the<00:19:01.150> part 00:19:02.100 --> 00:19:02.110 align:start position:0% painful in in many cases so the part 00:19:02.110 --> 00:19:05.039 align:start position:0% painful in in many cases so the part three<00:19:02.470> is<00:19:03.510> simply<00:19:04.510> they've<00:19:04.750> arrived 00:19:05.039 --> 00:19:05.049 align:start position:0% three is simply they've arrived 00:19:05.049 --> 00:19:08.130 align:start position:0% three is simply they've arrived comparison<00:19:05.980> to<00:19:06.100> ipfs<00:19:06.610> I<00:19:06.909> was<00:19:07.390> sure<00:19:07.780> people 00:19:08.130 --> 00:19:08.140 align:start position:0% comparison to ipfs I was sure people 00:19:08.140 --> 00:19:12.510 align:start position:0% comparison to ipfs I was sure people would<00:19:08.320> ask<00:19:08.530> about<00:19:09.220> this<00:19:09.669> so<00:19:11.520> secure 00:19:12.510 --> 00:19:12.520 align:start position:0% would ask about this so secure 00:19:12.520 --> 00:19:14.669 align:start position:0% would ask about this so secure scuttlebutt<00:19:12.909> basically<00:19:13.600> optimizes<00:19:14.260> for<00:19:14.440> the 00:19:14.669 --> 00:19:14.679 align:start position:0% scuttlebutt basically optimizes for the 00:19:14.679 --> 00:19:18.950 align:start position:0% scuttlebutt basically optimizes for the worst<00:19:15.370> case<00:19:15.730> and<00:19:16.120> secure<00:19:16.510> in<00:19:16.690> IP<00:19:17.679> FES<00:19:17.950> so 00:19:18.950 --> 00:19:18.960 align:start position:0% worst case and secure in IP FES so 00:19:18.960 --> 00:19:21.149 align:start position:0% worst case and secure in IP FES so secure<00:19:19.960> scuttlebutt<00:19:20.350> is<00:19:20.409> designed<00:19:20.890> for<00:19:21.010> like 00:19:21.149 --> 00:19:21.159 align:start position:0% secure scuttlebutt is designed for like 00:19:21.159 --> 00:19:23.399 align:start position:0% secure scuttlebutt is designed for like long<00:19:21.429> append-only<00:19:22.000> chains<00:19:22.480> and<00:19:22.780> this<00:19:23.260> would 00:19:23.399 --> 00:19:23.409 align:start position:0% long append-only chains and this would 00:19:23.409 --> 00:19:26.340 align:start position:0% long append-only chains and this would be<00:19:23.590> like<00:19:23.620> the<00:19:24.039> pathological<00:19:24.700> case<00:19:25.059> and<00:19:25.330> yes<00:19:26.140> so 00:19:26.340 --> 00:19:26.350 align:start position:0% be like the pathological case and yes so 00:19:26.350 --> 00:19:28.020 align:start position:0% be like the pathological case and yes so they're<00:19:26.830> trying<00:19:27.010> to<00:19:27.039> completely<00:19:27.549> completely 00:19:28.020 --> 00:19:28.030 align:start position:0% they're trying to completely completely 00:19:28.030 --> 00:19:31.590 align:start position:0% they're trying to completely completely opposite<00:19:28.659> things<00:19:29.790> but<00:19:30.790> similar<00:19:31.390> and<00:19:31.570> that 00:19:31.590 --> 00:19:31.600 align:start position:0% opposite things but similar and that 00:19:31.600 --> 00:19:33.080 align:start position:0% opposite things but similar and that they<00:19:32.049> both<00:19:32.200> replicate<00:19:32.710> data 00:19:33.080 --> 00:19:33.090 align:start position:0% they both replicate data 00:19:33.090 --> 00:19:35.600 align:start position:0% they both replicate data without<00:19:33.539> global<00:19:34.200> consistency<00:19:34.470> so<00:19:35.399> they're 00:19:35.600 --> 00:19:35.610 align:start position:0% without global consistency so they're 00:19:35.610 --> 00:19:37.940 align:start position:0% without global consistency so they're kind<00:19:35.789> of<00:19:35.850> like<00:19:35.970> an<00:19:36.240> infrastructural<00:19:36.929> role<00:19:37.259> for 00:19:37.940 --> 00:19:37.950 align:start position:0% kind of like an infrastructural role for 00:19:37.950 --> 00:19:40.430 align:start position:0% kind of like an infrastructural role for if<00:19:38.399> you're<00:19:38.580> building<00:19:38.759> like<00:19:39.210> other<00:19:39.509> p2p<00:19:40.230> apps 00:19:40.430 --> 00:19:40.440 align:start position:0% if you're building like other p2p apps 00:19:40.440 --> 00:19:43.279 align:start position:0% if you're building like other p2p apps and<00:19:40.710> so<00:19:40.830> on<00:19:40.950> so<00:19:41.549> neither<00:19:42.240> again<00:19:42.749> neither<00:19:43.110> have 00:19:43.279 --> 00:19:43.289 align:start position:0% and so on so neither again neither have 00:19:43.289 --> 00:19:45.739 align:start position:0% and so on so neither again neither have any<00:19:43.499> like<00:19:43.919> cryptocurrency<00:19:44.730> or<00:19:45.149> thing<00:19:45.360> like<00:19:45.389> to 00:19:45.739 --> 00:19:45.749 align:start position:0% any like cryptocurrency or thing like to 00:19:45.749 --> 00:19:49.039 align:start position:0% any like cryptocurrency or thing like to directly<00:19:46.470> built<00:19:46.710> into<00:19:46.950> it<00:19:47.070> but<00:19:47.779> if<00:19:48.779> you're 00:19:49.039 --> 00:19:49.049 align:start position:0% directly built into it but if you're 00:19:49.049 --> 00:19:51.440 align:start position:0% directly built into it but if you're building<00:19:49.230> stuff<00:19:49.529> like<00:19:49.679> that<00:19:49.830> you<00:19:50.009> could<00:19:50.450> move 00:19:51.440 --> 00:19:51.450 align:start position:0% building stuff like that you could move 00:19:51.450 --> 00:19:54.799 align:start position:0% building stuff like that you could move your<00:19:51.659> data<00:19:51.870> around<00:19:52.169> using<00:19:52.679> a<00:19:53.450> combination<00:19:54.450> of 00:19:54.799 --> 00:19:54.809 align:start position:0% your data around using a combination of 00:19:54.809 --> 00:19:58.999 align:start position:0% your data around using a combination of these<00:19:54.929> things<00:19:57.139> secure<00:19:58.139> scuttlebutt<00:19:58.559> streams 00:19:58.999 --> 00:19:59.009 align:start position:0% these things secure scuttlebutt streams 00:19:59.009 --> 00:20:03.499 align:start position:0% these things secure scuttlebutt streams updates<00:19:59.909> in<00:20:00.240> order<00:20:00.809> to<00:20:01.230> feed<00:20:01.470> and<00:20:01.769> ipfs<00:20:02.669> has<00:20:03.480> a 00:20:03.499 --> 00:20:03.509 align:start position:0% updates in order to feed and ipfs has a 00:20:03.509 --> 00:20:05.509 align:start position:0% updates in order to feed and ipfs has a pointer<00:20:03.929> to<00:20:03.960> the<00:20:04.139> latest<00:20:04.409> message<00:20:04.740> and<00:20:04.980> works 00:20:05.509 --> 00:20:05.519 align:start position:0% pointer to the latest message and works 00:20:05.519 --> 00:20:06.919 align:start position:0% pointer to the latest message and works back<00:20:05.789> and<00:20:06.210> if<00:20:06.330> you<00:20:06.389> want<00:20:06.539> to<00:20:06.629> have<00:20:06.809> it 00:20:06.919 --> 00:20:06.929 align:start position:0% back and if you want to have it 00:20:06.929 --> 00:20:09.109 align:start position:0% back and if you want to have it relatively<00:20:07.649> efficient<00:20:08.129> you'd<00:20:08.340> have<00:20:08.850> some 00:20:09.109 --> 00:20:09.119 align:start position:0% relatively efficient you'd have some 00:20:09.119 --> 00:20:10.820 align:start position:0% relatively efficient you'd have some kind<00:20:09.299> of<00:20:09.389> tree<00:20:09.690> or<00:20:09.990> some<00:20:10.169> sort<00:20:10.379> of<00:20:10.409> directory 00:20:10.820 --> 00:20:10.830 align:start position:0% kind of tree or some sort of directory 00:20:10.830 --> 00:20:12.379 align:start position:0% kind of tree or some sort of directory you<00:20:11.070> find<00:20:11.309> the<00:20:11.399> things<00:20:11.610> will<00:20:11.850> just<00:20:11.879> not<00:20:12.119> have 00:20:12.379 --> 00:20:12.389 align:start position:0% you find the things will just not have 00:20:12.389 --> 00:20:14.419 align:start position:0% you find the things will just not have very<00:20:12.899> deep<00:20:13.259> structures<00:20:13.860> have<00:20:14.009> relatively 00:20:14.419 --> 00:20:14.429 align:start position:0% very deep structures have relatively 00:20:14.429 --> 00:20:18.859 align:start position:0% very deep structures have relatively shallow<00:20:14.639> ones<00:20:16.399> so<00:20:17.399> IPS<00:20:18.360> is<00:20:18.480> probably<00:20:18.690> better 00:20:18.859 --> 00:20:18.869 align:start position:0% shallow ones so IPS is probably better 00:20:18.869 --> 00:20:20.869 align:start position:0% shallow ones so IPS is probably better for<00:20:18.929> like<00:20:19.230> arbitrary<00:20:19.769> partial<00:20:20.429> data<00:20:20.549> sets 00:20:20.869 --> 00:20:20.879 align:start position:0% for like arbitrary partial data sets 00:20:20.879 --> 00:20:24.619 align:start position:0% for like arbitrary partial data sets like<00:20:21.090> wiki's<00:20:21.570> and<00:20:22.669> sort<00:20:23.669> of<00:20:23.730> static<00:20:24.389> sites 00:20:24.619 --> 00:20:24.629 align:start position:0% like wiki's and sort of static sites 00:20:24.629 --> 00:20:29.480 align:start position:0% like wiki's and sort of static sites such<00:20:24.899> things<00:20:25.169> all<00:20:25.409> like<00:20:27.830> directories<00:20:28.830> of<00:20:29.100> data 00:20:29.480 --> 00:20:29.490 align:start position:0% such things all like directories of data 00:20:29.490 --> 00:20:30.499 align:start position:0% such things all like directories of data and<00:20:29.759> that<00:20:29.820> sort<00:20:30.059> of<00:20:30.090> stuff 00:20:30.499 --> 00:20:30.509 align:start position:0% and that sort of stuff 00:20:30.509 --> 00:20:33.259 align:start position:0% and that sort of stuff whereas<00:20:30.960> SSB<00:20:31.710> is<00:20:31.919> designed<00:20:32.340> specifically<00:20:33.090> for 00:20:33.259 --> 00:20:33.269 align:start position:0% whereas SSB is designed specifically for 00:20:33.269 --> 00:20:35.720 align:start position:0% whereas SSB is designed specifically for like<00:20:34.169> social<00:20:34.619> applications<00:20:35.220> or<00:20:35.429> social 00:20:35.720 --> 00:20:35.730 align:start position:0% like social applications or social 00:20:35.730 --> 00:20:37.190 align:start position:0% like social applications or social applications<00:20:36.240> with<00:20:36.389> something<00:20:36.749> strapped<00:20:37.049> on 00:20:37.190 --> 00:20:37.200 align:start position:0% applications with something strapped on 00:20:37.200 --> 00:20:40.399 align:start position:0% applications with something strapped on the<00:20:37.320> side<00:20:38.299> so<00:20:39.299> secure<00:20:39.990> scuttlebutt<00:20:40.350> is 00:20:40.399 --> 00:20:40.409 align:start position:0% the side so secure scuttlebutt is 00:20:40.409 --> 00:20:42.859 align:start position:0% the side so secure scuttlebutt is basically<00:20:40.799> a<00:20:40.889> graph<00:20:41.070> database<00:20:41.249> and<00:20:41.759> IFIF<00:20:42.720> this 00:20:42.859 --> 00:20:42.869 align:start position:0% basically a graph database and IFIF this 00:20:42.869 --> 00:20:48.830 align:start position:0% basically a graph database and IFIF this is<00:20:43.230> file<00:20:43.529> system<00:20:45.799> yep<00:20:46.799> okay<00:20:47.429> that<00:20:48.389> took<00:20:48.659> this 00:20:48.830 --> 00:20:48.840 align:start position:0% is file system yep okay that took this 00:20:48.840 --> 00:20:50.359 align:start position:0% is file system yep okay that took this long<00:20:49.110> because<00:20:49.350> I<00:20:49.649> didn't<00:20:49.950> get<00:20:50.070> to<00:20:50.159> show<00:20:50.340> you 00:20:50.359 --> 00:20:50.369 align:start position:0% long because I didn't get to show you 00:20:50.369 --> 00:20:58.090 align:start position:0% long because I didn't get to show you the<00:20:50.789> animation<00:20:51.720> stuff<00:20:52.230> but<00:20:52.940> I'm<00:20:54.919> that's<00:20:55.919> it 00:20:58.090 --> 00:20:58.100 align:start position:0% 00:20:58.100 --> 00:21:01.580 align:start position:0% okay<00:20:59.100> um<00:20:59.340> if<00:21:00.090> you'd<00:21:00.450> like<00:21:00.629> to<00:21:00.899> if<00:21:01.169> you'd<00:21:01.409> like 00:21:01.580 --> 00:21:01.590 align:start position:0% okay um if you'd like to if you'd like 00:21:01.590 --> 00:21:05.029 align:start position:0% okay um if you'd like to if you'd like to<00:21:01.769> learn<00:21:02.429> more<00:21:03.320> you<00:21:04.320> can<00:21:04.350> go<00:21:04.470> to<00:21:04.649> a 00:21:05.029 --> 00:21:05.039 align:start position:0% to learn more you can go to a 00:21:05.039 --> 00:21:10.239 align:start position:0% to learn more you can go to a scuttlebutt<00:21:05.399> don't<00:21:06.119> NZ<00:21:06.889> that's<00:21:07.889> to<00:21:08.100> tease<00:21:08.309> and 00:21:10.239 --> 00:21:10.249 align:start position:0% scuttlebutt don't NZ that's to tease and 00:21:10.249 --> 00:21:13.460 align:start position:0% scuttlebutt don't NZ that's to tease and github.com<00:21:11.249> slash<00:21:11.909> uses<00:21:12.240> bc<00:21:12.629> /<00:21:12.840> patchwork 00:21:13.460 --> 00:21:13.470 align:start position:0% github.com slash uses bc / patchwork 00:21:13.470 --> 00:21:16.909 align:start position:0% github.com slash uses bc / patchwork there's<00:21:13.740> like<00:21:13.919> a<00:21:13.950> UI<00:21:14.940> for<00:21:15.090> like<00:21:15.539> a<00:21:15.570> real<00:21:15.919> real 00:21:16.909 --> 00:21:16.919 align:start position:0% there's like a UI for like a real real 00:21:16.919 --> 00:21:18.710 align:start position:0% there's like a UI for like a real real working<00:21:17.490> application<00:21:17.759> that<00:21:18.330> you<00:21:18.450> can<00:21:18.600> use 00:21:18.710 --> 00:21:18.720 align:start position:0% working application that you can use 00:21:18.720 --> 00:21:22.850 align:start position:0% working application that you can use today<00:21:19.100> and<00:21:20.690> if<00:21:21.690> you<00:21:22.200> go<00:21:22.350> on<00:21:22.499> that<00:21:22.590> you'll<00:21:22.740> meet 00:21:22.850 --> 00:21:22.860 align:start position:0% today and if you go on that you'll meet 00:21:22.860 --> 00:21:25.190 align:start position:0% today and if you go on that you'll meet lots<00:21:23.009> of<00:21:23.129> love<00:21:23.669> lots<00:21:23.879> of<00:21:24.179> load<00:21:24.360> lots<00:21:24.840> of<00:21:24.990> lovely 00:21:25.190 --> 00:21:25.200 align:start position:0% lots of love lots of load lots of lovely 00:21:25.200 --> 00:21:27.529 align:start position:0% lots of love lots of load lots of lovely people<00:21:25.590> that<00:21:25.710> will<00:21:25.830> tell<00:21:25.950> you<00:21:26.039> all<00:21:26.159> about<00:21:26.539> how 00:21:27.529 --> 00:21:27.539 align:start position:0% people that will tell you all about how 00:21:27.539 --> 00:21:29.720 align:start position:0% people that will tell you all about how things<00:21:27.749> work<00:21:28.129> fortunately<00:21:29.129> yeah<00:21:29.309> so<00:21:29.580> the 00:21:29.720 --> 00:21:29.730 align:start position:0% things work fortunately yeah so the 00:21:29.730 --> 00:21:33.850 align:start position:0% things work fortunately yeah so the slice<00:21:29.879> doesn't<00:21:30.179> work 00:21:33.850 --> 00:21:33.860 align:start position:0% 00:21:33.860 --> 00:21:35.930 align:start position:0% I've<00:21:34.860> got<00:21:35.039> about<00:21:35.249> eight<00:21:35.490> minutes<00:21:35.639> see<00:21:35.820> any 00:21:35.930 --> 00:21:35.940 align:start position:0% I've got about eight minutes see any 00:21:35.940 --> 00:21:43.140 align:start position:0% I've got about eight minutes see any questions<00:21:36.269> or<00:21:36.480> heckling<00:21:37.440> or<00:21:37.679> anything 00:21:43.140 --> 00:21:43.150 align:start position:0% 00:21:43.150 --> 00:21:50.190 align:start position:0% scuttlebutt<00:21:43.660> ends<00:21:44.290> it<00:21:45.270> yep<00:21:48.510> go<00:21:49.510> thank<00:21:50.170> you 00:21:50.190 --> 00:21:50.200 align:start position:0% scuttlebutt ends it yep go thank you 00:21:50.200 --> 00:21:51.920 align:start position:0% scuttlebutt ends it yep go thank you very<00:21:50.380> much 00:21:51.920 --> 00:21:51.930 align:start position:0% very much 00:21:51.930 --> 00:21:54.930 align:start position:0% very much [Applause] 00:21:54.930 --> 00:21:54.940 align:start position:0% [Applause] 00:21:54.940 --> 00:22:01.329 align:start position:0% [Applause] [Music]