WEBVTT Kind: captions Language: en 00:00:01.070 --> 00:00:10.430 align:start position:0% [Applause] 00:00:10.430 --> 00:00:10.440 align:start position:0% 00:00:10.440 --> 00:00:13.039 align:start position:0% the<00:00:11.440> technical<00:00:12.160> for<00:00:12.610> the<00:00:12.700> free<00:00:12.910> stuff 00:00:13.039 --> 00:00:13.049 align:start position:0% the technical for the free stuff 00:00:13.049 --> 00:00:15.780 align:start position:0% the technical for the free stuff technical<00:00:14.049> kinda<00:00:14.620> like<00:00:14.799> advanced<00:00:15.219> talking 00:00:15.780 --> 00:00:15.790 align:start position:0% technical kinda like advanced talking 00:00:15.790 --> 00:00:17.310 align:start position:0% technical kinda like advanced talking awesome<00:00:16.119> stuff<00:00:16.299> there's<00:00:16.869> been<00:00:17.020> a<00:00:17.050> lot<00:00:17.290> of 00:00:17.310 --> 00:00:17.320 align:start position:0% awesome stuff there's been a lot of 00:00:17.320 --> 00:00:21.929 align:start position:0% awesome stuff there's been a lot of interest<00:00:17.760> agnostic<00:00:18.760> so<00:00:20.099> the<00:00:21.099> D<00:00:21.279> people<00:00:21.610> signed 00:00:21.929 --> 00:00:21.939 align:start position:0% interest agnostic so the D people signed 00:00:21.939 --> 00:00:24.450 align:start position:0% interest agnostic so the D people signed up<00:00:22.060> for<00:00:22.210> this<00:00:22.360> particular<00:00:22.630> talk<00:00:22.990> I'd<00:00:23.230> I<00:00:23.529> don't 00:00:24.450 --> 00:00:24.460 align:start position:0% up for this particular talk I'd I don't 00:00:24.460 --> 00:00:25.800 align:start position:0% up for this particular talk I'd I don't think<00:00:24.670> everybody<00:00:24.910> will<00:00:25.180> fit<00:00:25.420> in<00:00:25.509> this<00:00:25.630> work 00:00:25.800 --> 00:00:25.810 align:start position:0% think everybody will fit in this work 00:00:25.810 --> 00:00:27.750 align:start position:0% think everybody will fit in this work you<00:00:25.900> have<00:00:25.930> to<00:00:26.109> happen<00:00:26.260> to<00:00:26.470> show<00:00:26.619> up<00:00:26.800> but<00:00:27.670> you 00:00:27.750 --> 00:00:27.760 align:start position:0% you have to happen to show up but you 00:00:27.760 --> 00:00:29.040 align:start position:0% you have to happen to show up but you know<00:00:27.820> we<00:00:27.940> have<00:00:28.060> very<00:00:28.090> little<00:00:28.390> time<00:00:28.690> and<00:00:28.869> a<00:00:28.930> lot 00:00:29.040 --> 00:00:29.050 align:start position:0% know we have very little time and a lot 00:00:29.050 --> 00:00:30.390 align:start position:0% know we have very little time and a lot of<00:00:29.199> ground<00:00:29.439> to<00:00:29.560> cover<00:00:29.590> so<00:00:29.830> I'm<00:00:30.039> gonna<00:00:30.220> get 00:00:30.390 --> 00:00:30.400 align:start position:0% of ground to cover so I'm gonna get 00:00:30.400 --> 00:00:32.970 align:start position:0% of ground to cover so I'm gonna get started<00:00:30.580> on<00:00:30.840> the<00:00:31.840> undetected<00:00:32.379> for<00:00:32.590> it<00:00:32.710> than<00:00:32.860> it 00:00:32.970 --> 00:00:32.980 align:start position:0% started on the undetected for it than it 00:00:32.980 --> 00:00:34.799 align:start position:0% started on the undetected for it than it be<00:00:33.040> to<00:00:33.129> be<00:00:33.280> project<00:00:33.460> properly<00:00:34.150> what<00:00:34.360> apps<00:00:34.540> and 00:00:34.799 --> 00:00:34.809 align:start position:0% be to be project properly what apps and 00:00:34.809 --> 00:00:36.780 align:start position:0% be to be project properly what apps and this<00:00:35.739> is<00:00:35.890> what<00:00:36.040> we're<00:00:36.280> going<00:00:36.370> to<00:00:36.430> be<00:00:36.580> talking 00:00:36.780 --> 00:00:36.790 align:start position:0% this is what we're going to be talking 00:00:36.790 --> 00:00:38.759 align:start position:0% this is what we're going to be talking about<00:00:36.940> and<00:00:37.269> missed<00:00:37.420> it<00:00:37.540> by<00:00:37.690> yourself<00:00:38.410> so 00:00:38.759 --> 00:00:38.769 align:start position:0% about and missed it by yourself so 00:00:38.769 --> 00:00:41.430 align:start position:0% about and missed it by yourself so positive<00:00:39.760> is<00:00:39.970> a<00:00:40.030> scalable<00:00:40.720> instant<00:00:41.260> and 00:00:41.430 --> 00:00:41.440 align:start position:0% positive is a scalable instant and 00:00:41.440 --> 00:00:42.870 align:start position:0% positive is a scalable instant and extensible<00:00:41.949> peer-to-peer<00:00:42.219> gossiping 00:00:42.870 --> 00:00:42.880 align:start position:0% extensible peer-to-peer gossiping 00:00:42.880 --> 00:00:46.200 align:start position:0% extensible peer-to-peer gossiping protocol<00:00:43.540> and<00:00:44.500> over<00:00:45.130> agenda<00:00:45.520> for<00:00:45.640> today<00:00:45.880> is 00:00:46.200 --> 00:00:46.210 align:start position:0% protocol and over agenda for today is 00:00:46.210 --> 00:00:48.119 align:start position:0% protocol and over agenda for today is first<00:00:46.480> of<00:00:46.600> all<00:00:46.780> I<00:00:47.079> want<00:00:47.559> to<00:00:47.590> make<00:00:47.649> sure<00:00:47.739> that<00:00:48.040> we 00:00:48.119 --> 00:00:48.129 align:start position:0% first of all I want to make sure that we 00:00:48.129 --> 00:00:50.040 align:start position:0% first of all I want to make sure that we all<00:00:48.250> have<00:00:48.489> had<00:00:48.940> like<00:00:49.180> a<00:00:49.210> comedy<00:00:49.540> based<00:00:49.750> night 00:00:50.040 --> 00:00:50.050 align:start position:0% all have had like a comedy based night 00:00:50.050 --> 00:00:52.709 align:start position:0% all have had like a comedy based night to<00:00:50.800> talk<00:00:50.920> about<00:00:51.070> these<00:00:51.309> technical<00:00:52.300> concepts 00:00:52.709 --> 00:00:52.719 align:start position:0% to talk about these technical concepts 00:00:52.719 --> 00:00:54.090 align:start position:0% to talk about these technical concepts so<00:00:52.989> I'm<00:00:53.290> gonna<00:00:53.469> do<00:00:53.649> a<00:00:53.680> very<00:00:53.829> quick 00:00:54.090 --> 00:00:54.100 align:start position:0% so I'm gonna do a very quick 00:00:54.100 --> 00:00:56.279 align:start position:0% so I'm gonna do a very quick introduction<00:00:54.460> to<00:00:54.670> beer<00:00:54.940> beer<00:00:55.420> to<00:00:55.570> beer<00:00:55.780> pub 00:00:56.279 --> 00:00:56.289 align:start position:0% introduction to beer beer to beer pub 00:00:56.289 --> 00:00:58.350 align:start position:0% introduction to beer beer to beer pub sup<00:00:56.469> who<00:00:56.680> here<00:00:56.920> is<00:00:56.980> familiar<00:00:57.100> with<00:00:57.399> with<00:00:58.239> these 00:00:58.350 --> 00:00:58.360 align:start position:0% sup who here is familiar with with these 00:00:58.360 --> 00:01:00.810 align:start position:0% sup who here is familiar with with these concepts<00:00:58.809> like<00:00:59.110> maybe<00:00:59.469> a<00:00:59.620> 5<00:01:00.070> and<00:01:00.280> above<00:01:00.340> in 00:01:00.810 --> 00:01:00.820 align:start position:0% concepts like maybe a 5 and above in 00:01:00.820 --> 00:01:03.060 align:start position:0% concepts like maybe a 5 and above in this<00:01:01.629> game<00:01:01.780> over<00:01:01.930> 10<00:01:02.079> fantastic<00:01:02.710> ok<00:01:02.860> so<00:01:02.920> now 00:01:03.060 --> 00:01:03.070 align:start position:0% this game over 10 fantastic ok so now 00:01:03.070 --> 00:01:04.590 align:start position:0% this game over 10 fantastic ok so now I'm<00:01:03.160> gonna<00:01:03.309> move<00:01:04.089> through<00:01:04.300> this<00:01:04.390> pretty 00:01:04.590 --> 00:01:04.600 align:start position:0% I'm gonna move through this pretty 00:01:04.600 --> 00:01:07.440 align:start position:0% I'm gonna move through this pretty quickly<00:01:05.490> then<00:01:06.490> we're<00:01:06.610> gonna<00:01:06.700> talk<00:01:06.940> about<00:01:06.970> what 00:01:07.440 --> 00:01:07.450 align:start position:0% quickly then we're gonna talk about what 00:01:07.450 --> 00:01:08.850 align:start position:0% quickly then we're gonna talk about what is<00:01:07.570> cost<00:01:07.780> observe<00:01:08.110> we're<00:01:08.259> gonna<00:01:08.380> talk<00:01:08.680> about 00:01:08.850 --> 00:01:08.860 align:start position:0% is cost observe we're gonna talk about 00:01:08.860 --> 00:01:11.760 align:start position:0% is cost observe we're gonna talk about how<00:01:09.520> the<00:01:09.580> system<00:01:09.880> operates<00:01:10.210> and<00:01:11.080> what's<00:01:11.619> up 00:01:11.760 --> 00:01:11.770 align:start position:0% how the system operates and what's up 00:01:11.770 --> 00:01:13.920 align:start position:0% how the system operates and what's up next<00:01:12.190> because<00:01:13.000> as<00:01:13.240> you'll<00:01:13.390> see<00:01:13.539> in<00:01:13.660> gossip 00:01:13.920 --> 00:01:13.930 align:start position:0% next because as you'll see in gossip 00:01:13.930 --> 00:01:20.090 align:start position:0% next because as you'll see in gossip serve<00:01:14.140> is<00:01:14.350> a<00:01:16.650> stepping<00:01:17.650> stone<00:01:17.920> in<00:01:18.400> a<00:01:18.970> road<00:01:19.330> map 00:01:20.090 --> 00:01:20.100 align:start position:0% serve is a stepping stone in a road map 00:01:20.100 --> 00:01:24.380 align:start position:0% serve is a stepping stone in a road map improves<00:01:21.100> a<00:01:21.430> lot<00:01:21.850> of<00:01:21.939> functionality<00:01:22.330> that's 00:01:24.380 --> 00:01:24.390 align:start position:0% improves a lot of functionality that's 00:01:24.390 --> 00:01:33.670 align:start position:0% improves a lot of functionality that's let's<00:01:25.200> gonna<00:01:25.320> get<00:01:25.500> the<00:01:25.590> future<00:01:25.800> so<00:01:32.570> alright 00:01:33.670 --> 00:01:33.680 align:start position:0% let's gonna get the future so alright 00:01:33.680 --> 00:01:36.740 align:start position:0% let's gonna get the future so alright what<00:01:34.680> is<00:01:34.770> pop<00:01:34.980> ups<00:01:35.370> up<00:01:35.610> is<00:01:35.820> a<00:01:36.240> message<00:01:36.510> oriented 00:01:36.740 --> 00:01:36.750 align:start position:0% what is pop ups up is a message oriented 00:01:36.750 --> 00:01:38.390 align:start position:0% what is pop ups up is a message oriented communication<00:01:37.470> pack<00:01:37.650> right<00:01:38.010> this<00:01:38.220> isn't 00:01:38.390 --> 00:01:38.400 align:start position:0% communication pack right this isn't 00:01:38.400 --> 00:01:41.120 align:start position:0% communication pack right this isn't stock<00:01:38.700> on<00:01:38.910> trust<00:01:39.180> with<00:01:39.570> stream<00:01:40.500> orientation 00:01:41.120 --> 00:01:41.130 align:start position:0% stock on trust with stream orientation 00:01:41.130 --> 00:01:42.860 align:start position:0% stock on trust with stream orientation so<00:01:41.310> here<00:01:41.640> we're<00:01:41.790> not<00:01:41.940> interested<00:01:42.600> in<00:01:42.810> what 00:01:42.860 --> 00:01:42.870 align:start position:0% so here we're not interested in what 00:01:42.870 --> 00:01:44.270 align:start position:0% so here we're not interested in what pops<00:01:43.200> up<00:01:43.410> we're<00:01:43.560> know<00:01:43.680> many<00:01:43.890> interesting 00:01:44.270 --> 00:01:44.280 align:start position:0% pops up we're know many interesting 00:01:44.280 --> 00:01:46.460 align:start position:0% pops up we're know many interesting sending<00:01:44.640> transactional<00:01:45.540> messages<00:01:46.020> and<00:01:46.230> small 00:01:46.460 --> 00:01:46.470 align:start position:0% sending transactional messages and small 00:01:46.470 --> 00:01:48.950 align:start position:0% sending transactional messages and small units<00:01:46.860> that<00:01:47.520> are<00:01:47.730> actually<00:01:48.240> messages<00:01:48.660> and<00:01:48.840> not 00:01:48.950 --> 00:01:48.960 align:start position:0% units that are actually messages and not 00:01:48.960 --> 00:01:51.590 align:start position:0% units that are actually messages and not streams<00:01:49.290> right<00:01:49.590> over<00:01:49.920> the<00:01:50.010> wire<00:01:50.190> between<00:01:50.850> a 00:01:51.590 --> 00:01:51.600 align:start position:0% streams right over the wire between a 00:01:51.600 --> 00:01:55.220 align:start position:0% streams right over the wire between a bunch<00:01:52.050> of<00:01:52.230> peers<00:01:52.590> that<00:01:53.330> are<00:01:54.330> not<00:01:54.690> necessarily 00:01:55.220 --> 00:01:55.230 align:start position:0% bunch of peers that are not necessarily 00:01:55.230 --> 00:01:57.020 align:start position:0% bunch of peers that are not necessarily talking<00:01:55.380> to<00:01:55.710> each<00:01:55.830> other<00:01:56.070> so<00:01:56.430> the<00:01:56.520> interaction 00:01:57.020 --> 00:01:57.030 align:start position:0% talking to each other so the interaction 00:01:57.030 --> 00:01:58.970 align:start position:0% talking to each other so the interaction model<00:01:57.060> of<00:01:57.420> pops<00:01:57.660> up<00:01:57.870> is<00:01:58.050> end<00:01:58.440> to<00:01:58.650> end<00:01:58.800> this 00:01:58.970 --> 00:01:58.980 align:start position:0% model of pops up is end to end this 00:01:58.980 --> 00:02:01.100 align:start position:0% model of pops up is end to end this means<00:01:59.220> that<00:01:59.430> NP<00:02:00.360> r--'s<00:02:00.420> are<00:02:00.750> publishing 00:02:01.100 --> 00:02:01.110 align:start position:0% means that NP r--'s are publishing 00:02:01.110 --> 00:02:03.670 align:start position:0% means that NP r--'s are publishing messages<00:02:01.650> about<00:02:02.280> a<00:02:02.340> particular<00:02:02.760> subject<00:02:03.270> and 00:02:03.670 --> 00:02:03.680 align:start position:0% messages about a particular subject and 00:02:03.680 --> 00:02:06.650 align:start position:0% messages about a particular subject and a<00:02:04.680> lot<00:02:05.250> of<00:02:05.370> other<00:02:05.520> peers<00:02:05.820> in<00:02:06.060> the<00:02:06.150> network<00:02:06.180> are 00:02:06.650 --> 00:02:06.660 align:start position:0% a lot of other peers in the network are 00:02:06.660 --> 00:02:09.260 align:start position:0% a lot of other peers in the network are interested<00:02:07.200> in<00:02:07.320> consuming<00:02:08.149> messages<00:02:09.149> from 00:02:09.260 --> 00:02:09.270 align:start position:0% interested in consuming messages from 00:02:09.270 --> 00:02:11.180 align:start position:0% interested in consuming messages from that<00:02:09.330> from<00:02:09.750> that<00:02:09.780> particular<00:02:10.110> subject<00:02:10.470> wait 00:02:11.180 --> 00:02:11.190 align:start position:0% that from that particular subject wait 00:02:11.190 --> 00:02:13.220 align:start position:0% that from that particular subject wait this<00:02:11.430> is<00:02:11.550> as<00:02:11.730> I<00:02:11.760> said<00:02:11.850> in<00:02:12.120> contrast<00:02:12.540> to<00:02:12.600> our<00:02:12.930> PCR 00:02:13.220 --> 00:02:13.230 align:start position:0% this is as I said in contrast to our PCR 00:02:13.230 --> 00:02:15.590 align:start position:0% this is as I said in contrast to our PCR reply<00:02:13.620> with<00:02:14.220> western<00:02:14.520> pop<00:02:14.730> patterns<00:02:15.120> which 00:02:15.590 --> 00:02:15.600 align:start position:0% reply with western pop patterns which 00:02:15.600 --> 00:02:18.620 align:start position:0% reply with western pop patterns which are<00:02:15.750> mostly<00:02:16.140> one-to-one<00:02:17.070> no<00:02:17.970> buffs<00:02:18.510> up 00:02:18.620 --> 00:02:18.630 align:start position:0% are mostly one-to-one no buffs up 00:02:18.630 --> 00:02:20.030 align:start position:0% are mostly one-to-one no buffs up communication<00:02:19.230> is<00:02:19.380> a<00:02:19.410> synchronous<00:02:19.890> and 00:02:20.030 --> 00:02:20.040 align:start position:0% communication is a synchronous and 00:02:20.040 --> 00:02:21.890 align:start position:0% communication is a synchronous and decoupled<00:02:20.550> in<00:02:20.670> nature<00:02:21.000> right<00:02:21.270> this<00:02:21.720> means 00:02:21.890 --> 00:02:21.900 align:start position:0% decoupled in nature right this means 00:02:21.900 --> 00:02:24.050 align:start position:0% decoupled in nature right this means that<00:02:22.110> whenever<00:02:22.320> I<00:02:22.500> send<00:02:22.860> a<00:02:23.100> message<00:02:23.700> as<00:02:24.000> a 00:02:24.050 --> 00:02:24.060 align:start position:0% that whenever I send a message as a 00:02:24.060 --> 00:02:26.360 align:start position:0% that whenever I send a message as a producer<00:02:24.420> I<00:02:24.810> have<00:02:25.260> no<00:02:25.410> guarantee<00:02:25.560> for<00:02:25.890> us<00:02:26.220> to 00:02:26.360 --> 00:02:26.370 align:start position:0% producer I have no guarantee for us to 00:02:26.370 --> 00:02:28.670 align:start position:0% producer I have no guarantee for us to vol<00:02:26.550> when<00:02:27.180> who<00:02:27.690> is<00:02:27.900> actually<00:02:28.230> going<00:02:28.590> to 00:02:28.670 --> 00:02:28.680 align:start position:0% vol when who is actually going to 00:02:28.680 --> 00:02:30.620 align:start position:0% vol when who is actually going to receive<00:02:28.980> that<00:02:29.040> message<00:02:29.310> because<00:02:30.300> we<00:02:30.450> don't 00:02:30.620 --> 00:02:30.630 align:start position:0% receive that message because we don't 00:02:30.630 --> 00:02:32.900 align:start position:0% receive that message because we don't have<00:02:30.690> peers<00:02:31.560> don't<00:02:31.860> have<00:02:32.130> a<00:02:32.160> complete<00:02:32.610> view<00:02:32.640> of 00:02:32.900 --> 00:02:32.910 align:start position:0% have peers don't have a complete view of 00:02:32.910 --> 00:02:35.510 align:start position:0% have peers don't have a complete view of the<00:02:33.270> network<00:02:33.570> and<00:02:33.810> a<00:02:34.170> complete<00:02:34.500> view<00:02:34.800> of<00:02:34.860> the 00:02:35.510 --> 00:02:35.520 align:start position:0% the network and a complete view of the 00:02:35.520 --> 00:02:38.690 align:start position:0% the network and a complete view of the subscription<00:02:36.209> state<00:02:36.530> and<00:02:37.530> it's<00:02:37.890> also<00:02:38.070> it's 00:02:38.690 --> 00:02:38.700 align:start position:0% subscription state and it's also it's 00:02:38.700 --> 00:02:40.790 align:start position:0% subscription state and it's also it's also<00:02:38.850> a<00:02:39.030> synchronous<00:02:39.570> because<00:02:39.780> there<00:02:40.500> is<00:02:40.620> no 00:02:40.790 --> 00:02:40.800 align:start position:0% also a synchronous because there is no 00:02:40.800 --> 00:02:43.880 align:start position:0% also a synchronous because there is no time<00:02:41.160> dependency<00:02:42.060> I<00:02:42.330> have<00:02:43.140> received<00:02:43.770> no 00:02:43.880 --> 00:02:43.890 align:start position:0% time dependency I have received no 00:02:43.890 --> 00:02:46.790 align:start position:0% time dependency I have received no explicit<00:02:44.760> confirmation<00:02:45.450> from<00:02:45.930> any<00:02:46.140> peer<00:02:46.410> that 00:02:46.790 --> 00:02:46.800 align:start position:0% explicit confirmation from any peer that 00:02:46.800 --> 00:02:48.770 align:start position:0% explicit confirmation from any peer that they've<00:02:46.980> actually<00:02:47.130> received<00:02:47.640> my<00:02:47.760> message 00:02:48.770 --> 00:02:48.780 align:start position:0% they've actually received my message 00:02:48.780 --> 00:02:51.110 align:start position:0% they've actually received my message processes<00:02:49.620> act<00:02:49.920> as<00:02:50.250> publishers<00:02:50.880> and 00:02:51.110 --> 00:02:51.120 align:start position:0% processes act as publishers and 00:02:51.120 --> 00:02:52.790 align:start position:0% processes act as publishers and consumers<00:02:51.540> of<00:02:51.690> messages<00:02:52.110> and<00:02:52.320> then<00:02:52.440> the<00:02:52.560> peer 00:02:52.790 --> 00:02:52.800 align:start position:0% consumers of messages and then the peer 00:02:52.800 --> 00:02:54.350 align:start position:0% consumers of messages and then the peer to<00:02:52.950> peer<00:02:53.040> network<00:02:53.220> this<00:02:53.790> is<00:02:53.850> important 00:02:54.350 --> 00:02:54.360 align:start position:0% to peer network this is important 00:02:54.360 --> 00:02:55.850 align:start position:0% to peer network this is important because<00:02:54.480> the<00:02:54.690> process<00:02:55.050> can<00:02:55.320> act<00:02:55.470> as<00:02:55.680> both 00:02:55.850 --> 00:02:55.860 align:start position:0% because the process can act as both 00:02:55.860 --> 00:02:58.670 align:start position:0% because the process can act as both things<00:02:56.220> and<00:02:56.970> they<00:02:57.420> congregated<00:02:57.660> on<00:02:58.200> topics<00:02:58.590> of 00:02:58.670 --> 00:02:58.680 align:start position:0% things and they congregated on topics of 00:02:58.680 --> 00:03:00.920 align:start position:0% things and they congregated on topics of interest<00:02:58.800> now<00:02:59.700> pub<00:03:00.330> cell<00:03:00.510> is<00:03:00.600> implying 00:03:00.920 --> 00:03:00.930 align:start position:0% interest now pub cell is implying 00:03:00.930 --> 00:03:02.770 align:start position:0% interest now pub cell is implying popular<00:03:01.560> and<00:03:01.739> then<00:03:01.860> in<00:03:02.040> enterprise<00:03:02.459> software 00:03:02.770 --> 00:03:02.780 align:start position:0% popular and then in enterprise software 00:03:02.780 --> 00:03:06.410 align:start position:0% popular and then in enterprise software and<00:03:04.010> if<00:03:05.010> you've<00:03:05.160> heard<00:03:05.430> of<00:03:05.640> products<00:03:06.180> and 00:03:06.410 --> 00:03:06.420 align:start position:0% and if you've heard of products and 00:03:06.420 --> 00:03:08.449 align:start position:0% and if you've heard of products and projects<00:03:06.780> like<00:03:06.840> about<00:03:07.170> Apache<00:03:07.680> ActiveMQ 00:03:08.449 --> 00:03:08.459 align:start position:0% projects like about Apache ActiveMQ 00:03:08.459 --> 00:03:11.120 align:start position:0% projects like about Apache ActiveMQ Kalka<00:03:09.150> RabbitMQ<00:03:09.780> then<00:03:10.380> that's<00:03:10.590> it<00:03:10.800> but<00:03:11.010> in 00:03:11.120 --> 00:03:11.130 align:start position:0% Kalka RabbitMQ then that's it but in 00:03:11.130 --> 00:03:13.850 align:start position:0% Kalka RabbitMQ then that's it but in those<00:03:11.660> contexts<00:03:12.660> is<00:03:12.810> usually<00:03:13.350> being 00:03:13.850 --> 00:03:13.860 align:start position:0% those contexts is usually being 00:03:13.860 --> 00:03:16.160 align:start position:0% those contexts is usually being centralized<00:03:14.430> around<00:03:14.610> brokers<00:03:15.480> in<00:03:15.780> private 00:03:16.160 --> 00:03:16.170 align:start position:0% centralized around brokers in private 00:03:16.170 --> 00:03:18.140 align:start position:0% centralized around brokers in private networks<00:03:16.530> and<00:03:16.830> it's<00:03:17.070> tough<00:03:17.250> you<00:03:17.370> know<00:03:17.430> these 00:03:18.140 --> 00:03:18.150 align:start position:0% networks and it's tough you know these 00:03:18.150 --> 00:03:19.740 align:start position:0% networks and it's tough you know these approaches<00:03:18.750> and<00:03:18.900> also<00:03:19.110> to<00:03:19.170> both 00:03:19.740 --> 00:03:19.750 align:start position:0% approaches and also to both 00:03:19.750 --> 00:03:21.750 align:start position:0% approaches and also to both for<00:03:19.900> public<00:03:20.200> message<00:03:20.470> markets<00:03:20.860> so<00:03:21.460> what<00:03:21.640> is 00:03:21.750 --> 00:03:21.760 align:start position:0% for public message markets so what is 00:03:21.760 --> 00:03:23.730 align:start position:0% for public message markets so what is decentralized<00:03:22.120> appear<00:03:23.020> to<00:03:23.170> be<00:03:23.290> your<00:03:23.380> website 00:03:23.730 --> 00:03:23.740 align:start position:0% decentralized appear to be your website 00:03:23.740 --> 00:03:26.310 align:start position:0% decentralized appear to be your website first<00:03:24.070> of<00:03:24.220> all<00:03:24.340> it's<00:03:24.670> broken<00:03:25.060> s<00:03:25.210> it<00:03:25.900> means<00:03:26.140> that 00:03:26.310 --> 00:03:26.320 align:start position:0% first of all it's broken s it means that 00:03:26.320 --> 00:03:27.870 align:start position:0% first of all it's broken s it means that we<00:03:26.440> have<00:03:26.470> no<00:03:26.740> central<00:03:27.070> authorities<00:03:27.550> to<00:03:27.760> keep 00:03:27.870 --> 00:03:27.880 align:start position:0% we have no central authorities to keep 00:03:27.880 --> 00:03:30.120 align:start position:0% we have no central authorities to keep track<00:03:28.150> of<00:03:28.300> subscribers<00:03:28.780> publishers<00:03:29.680> topics 00:03:30.120 --> 00:03:30.130 align:start position:0% track of subscribers publishers topics 00:03:30.130 --> 00:03:33.780 align:start position:0% track of subscribers publishers topics it's<00:03:30.970> self<00:03:31.300> recognizing<00:03:32.370> whatever<00:03:33.370> we<00:03:33.580> deal 00:03:33.780 --> 00:03:33.790 align:start position:0% it's self recognizing whatever we deal 00:03:33.790 --> 00:03:35.460 align:start position:0% it's self recognizing whatever we deal with<00:03:33.820> peer-to-peer<00:03:34.390> networks<00:03:35.020> we<00:03:35.200> have<00:03:35.260> to 00:03:35.460 --> 00:03:35.470 align:start position:0% with peer-to-peer networks we have to 00:03:35.470 --> 00:03:38.040 align:start position:0% with peer-to-peer networks we have to mob<00:03:35.620> uterine<00:03:36.100> right<00:03:36.490> and<00:03:36.700> peer<00:03:37.240> and<00:03:37.450> networks 00:03:38.040 --> 00:03:38.050 align:start position:0% mob uterine right and peer and networks 00:03:38.050 --> 00:03:41.780 align:start position:0% mob uterine right and peer and networks can<00:03:38.320> rotate<00:03:38.890> in<00:03:39.459> presence<00:03:39.910> very<00:03:40.690> rapidly<00:03:41.230> so 00:03:41.780 --> 00:03:41.790 align:start position:0% can rotate in presence very rapidly so 00:03:41.790 --> 00:03:44.370 align:start position:0% can rotate in presence very rapidly so there<00:03:42.790> is<00:03:42.910> no<00:03:43.030> global<00:03:43.270> knowledge<00:03:43.690> there<00:03:44.050> is<00:03:44.200> no 00:03:44.370 --> 00:03:44.380 align:start position:0% there is no global knowledge there is no 00:03:44.380 --> 00:03:46.080 align:start position:0% there is no global knowledge there is no single<00:03:44.709> peer<00:03:44.950> that<00:03:45.100> is<00:03:45.160> an<00:03:45.340> authority<00:03:45.820> that 00:03:46.080 --> 00:03:46.090 align:start position:0% single peer that is an authority that 00:03:46.090 --> 00:03:48.270 align:start position:0% single peer that is an authority that has<00:03:46.270> a<00:03:46.300> review<00:03:46.900> of<00:03:47.200> the<00:03:47.350> network<00:03:47.680> and<00:03:47.920> the 00:03:48.270 --> 00:03:48.280 align:start position:0% has a review of the network and the 00:03:48.280 --> 00:03:50.130 align:start position:0% has a review of the network and the network<00:03:48.310> behavior<00:03:49.060> actually<00:03:49.330> emerges<00:03:49.990> from 00:03:50.130 --> 00:03:50.140 align:start position:0% network behavior actually emerges from 00:03:50.140 --> 00:03:52.410 align:start position:0% network behavior actually emerges from small<00:03:50.530> tiny<00:03:50.950> local<00:03:51.310> decisions<00:03:51.910> that<00:03:52.180> peers 00:03:52.410 --> 00:03:52.420 align:start position:0% small tiny local decisions that peers 00:03:52.420 --> 00:03:54.840 align:start position:0% small tiny local decisions that peers are<00:03:52.600> taking<00:03:52.870> another<00:03:53.110> right<00:03:53.709> so<00:03:54.459> here<00:03:54.640> to 00:03:54.840 --> 00:03:54.850 align:start position:0% are taking another right so here to 00:03:54.850 --> 00:03:57.210 align:start position:0% are taking another right so here to pierre<00:03:55.120> pops<00:03:55.420> up<00:03:55.600> is<00:03:55.750> usually<00:03:56.200> constructed<00:03:56.830> as 00:03:57.210 --> 00:03:57.220 align:start position:0% pierre pops up is usually constructed as 00:03:57.220 --> 00:03:59.449 align:start position:0% pierre pops up is usually constructed as an<00:03:57.430> opening<00:03:57.820> network<00:03:58.150> with<00:03:58.720> peers 00:03:59.449 --> 00:03:59.459 align:start position:0% an opening network with peers 00:03:59.459 --> 00:04:01.260 align:start position:0% an opening network with peers collaborating<00:04:00.459> to<00:04:00.670> ensure<00:04:00.910> message 00:04:01.260 --> 00:04:01.270 align:start position:0% collaborating to ensure message 00:04:01.270 --> 00:04:03.990 align:start position:0% collaborating to ensure message deliverability<00:04:01.810> ok<00:04:02.470> and<00:04:02.680> when<00:04:03.580> we<00:04:03.790> say 00:04:03.990 --> 00:04:04.000 align:start position:0% deliverability ok and when we say 00:04:04.000 --> 00:04:06.420 align:start position:0% deliverability ok and when we say overlay<00:04:04.959> there's<00:04:05.290> usually<00:04:05.410> an<00:04:05.830> undulating 00:04:06.420 --> 00:04:06.430 align:start position:0% overlay there's usually an undulating 00:04:06.430 --> 00:04:10.560 align:start position:0% overlay there's usually an undulating right<00:04:06.700> so<00:04:07.180> it's<00:04:07.330> another<00:04:08.260> name<00:04:08.530> network<00:04:09.570> that 00:04:10.560 --> 00:04:10.570 align:start position:0% right so it's another name network that 00:04:10.570 --> 00:04:12.420 align:start position:0% right so it's another name network that actually<00:04:11.110> make<00:04:11.290> sure<00:04:11.470> that<00:04:11.680> messages<00:04:12.190> and 00:04:12.420 --> 00:04:12.430 align:start position:0% actually make sure that messages and 00:04:12.430 --> 00:04:14.780 align:start position:0% actually make sure that messages and traffic<00:04:12.820> gets<00:04:13.000> routed<00:04:13.209> and<00:04:13.570> usually 00:04:14.780 --> 00:04:14.790 align:start position:0% traffic gets routed and usually 00:04:14.790 --> 00:04:18.180 align:start position:0% traffic gets routed and usually algorithms<00:04:15.790> will<00:04:16.329> assume<00:04:16.630> that<00:04:16.799> the<00:04:17.799> underlay 00:04:18.180 --> 00:04:18.190 align:start position:0% algorithms will assume that the underlay 00:04:18.190 --> 00:04:21.150 align:start position:0% algorithms will assume that the underlay is<00:04:18.400> well<00:04:18.880> connected<00:04:19.290> so<00:04:20.290> this<00:04:20.739> means<00:04:20.950> that<00:04:21.010> I 00:04:21.150 --> 00:04:21.160 align:start position:0% is well connected so this means that I 00:04:21.160 --> 00:04:23.700 align:start position:0% is well connected so this means that I can<00:04:21.370> always<00:04:21.640> find<00:04:21.880> a<00:04:22.030> path<00:04:22.240> from<00:04:22.450> A<00:04:22.720> to<00:04:22.990> B<00:04:23.110> and 00:04:23.700 --> 00:04:23.710 align:start position:0% can always find a path from A to B and 00:04:23.710 --> 00:04:27.300 align:start position:0% can always find a path from A to B and if<00:04:23.860> I<00:04:23.979> can't<00:04:24.220> that's<00:04:24.430> a<00:04:24.520> component<00:04:25.680> so<00:04:26.680> just<00:04:27.160> to 00:04:27.300 --> 00:04:27.310 align:start position:0% if I can't that's a component so just to 00:04:27.310 --> 00:04:29.790 align:start position:0% if I can't that's a component so just to set<00:04:27.729> a<00:04:27.790> base<00:04:28.000> value<00:04:28.030> for<00:04:28.870> terminology<00:04:29.560> in<00:04:29.710> a 00:04:29.790 --> 00:04:29.800 align:start position:0% set a base value for terminology in a 00:04:29.800 --> 00:04:32.070 align:start position:0% set a base value for terminology in a topic<00:04:30.070> is<00:04:30.460> a<00:04:30.520> subject<00:04:31.150> on<00:04:31.300> which<00:04:31.479> appears 00:04:32.070 --> 00:04:32.080 align:start position:0% topic is a subject on which appears 00:04:32.080 --> 00:04:33.960 align:start position:0% topic is a subject on which appears congregate<00:04:32.620> and<00:04:32.919> the<00:04:33.220> image<00:04:33.550> and<00:04:33.729> receive 00:04:33.960 --> 00:04:33.970 align:start position:0% congregate and the image and receive 00:04:33.970 --> 00:04:36.030 align:start position:0% congregate and the image and receive messages<00:04:34.440> subscription<00:04:35.440> is<00:04:35.560> the<00:04:35.680> act<00:04:35.860> of 00:04:36.030 --> 00:04:36.040 align:start position:0% messages subscription is the act of 00:04:36.040 --> 00:04:37.469 align:start position:0% messages subscription is the act of expressing<00:04:36.370> interest<00:04:36.850> on<00:04:37.180> a<00:04:37.210> particular 00:04:37.469 --> 00:04:37.479 align:start position:0% expressing interest on a particular 00:04:37.479 --> 00:04:39.780 align:start position:0% expressing interest on a particular topic<00:04:37.979> publishing<00:04:38.979> is<00:04:39.070> the<00:04:39.190> act<00:04:39.340> of<00:04:39.460> creating 00:04:39.780 --> 00:04:39.790 align:start position:0% topic publishing is the act of creating 00:04:39.790 --> 00:04:41.400 align:start position:0% topic publishing is the act of creating a<00:04:39.940> message<00:04:40.270> and<00:04:40.570> pushing<00:04:40.870> it<00:04:40.960> out<00:04:41.110> to<00:04:41.140> the 00:04:41.400 --> 00:04:41.410 align:start position:0% a message and pushing it out to the 00:04:41.410 --> 00:04:43.530 align:start position:0% a message and pushing it out to the network<00:04:41.740> for<00:04:42.400> winning<00:04:42.729> is<00:04:42.850> the<00:04:42.880> apt<00:04:43.210> of 00:04:43.530 --> 00:04:43.540 align:start position:0% network for winning is the apt of 00:04:43.540 --> 00:04:45.600 align:start position:0% network for winning is the apt of propagating<00:04:44.140> a<00:04:44.380> message<00:04:44.740> to<00:04:44.979> other<00:04:45.160> peers<00:04:45.460> and 00:04:45.600 --> 00:04:45.610 align:start position:0% propagating a message to other peers and 00:04:45.610 --> 00:04:48.090 align:start position:0% propagating a message to other peers and the<00:04:45.700> topic<00:04:46.030> and<00:04:46.350> Fabian<00:04:47.350> discovery<00:04:47.830> is 00:04:48.090 --> 00:04:48.100 align:start position:0% the topic and Fabian discovery is 00:04:48.100 --> 00:04:49.980 align:start position:0% the topic and Fabian discovery is something<00:04:48.460> I<00:04:48.550> talk<00:04:48.729> about<00:04:48.760> in<00:04:49.090> the<00:04:49.150> same<00:04:49.300> so 00:04:49.980 --> 00:04:49.990 align:start position:0% something I talk about in the same so 00:04:49.990 --> 00:04:52.409 align:start position:0% something I talk about in the same so the<00:04:50.470> desirable<00:04:51.220> properties<00:04:51.280> in<00:04:52.000> peer-to-peer 00:04:52.409 --> 00:04:52.419 align:start position:0% the desirable properties in peer-to-peer 00:04:52.419 --> 00:04:55.040 align:start position:0% the desirable properties in peer-to-peer pops<00:04:52.960> up<00:04:53.140> our<00:04:53.320> reliability<00:04:53.890> Brazilians 00:04:55.040 --> 00:04:55.050 align:start position:0% pops up our reliability Brazilians 00:04:55.050 --> 00:04:57.780 align:start position:0% pops up our reliability Brazilians effect<00:04:56.050> efficient<00:04:56.530> dissemination<00:04:57.160> altruism 00:04:57.780 --> 00:04:57.790 align:start position:0% effect efficient dissemination altruism 00:04:57.790 --> 00:05:00.180 align:start position:0% effect efficient dissemination altruism free<00:04:58.150> routing<00:04:58.600> this<00:04:58.840> means<00:04:59.050> that<00:04:59.290> only<00:04:59.770> those 00:05:00.180 --> 00:05:00.190 align:start position:0% free routing this means that only those 00:05:00.190 --> 00:05:02.790 align:start position:0% free routing this means that only those peers<00:05:00.610> that<00:05:00.880> are<00:05:00.940> actually<00:05:01.590> participating<00:05:02.590> in 00:05:02.790 --> 00:05:02.800 align:start position:0% peers that are actually participating in 00:05:02.800 --> 00:05:06.990 align:start position:0% peers that are actually participating in one<00:05:03.160> in<00:05:03.400> a<00:05:03.760> particular<00:05:04.060> topic<00:05:04.419> will<00:05:06.000> will 00:05:06.990 --> 00:05:07.000 align:start position:0% one in a particular topic will will 00:05:07.000 --> 00:05:08.340 align:start position:0% one in a particular topic will will actually<00:05:07.030> contribute<00:05:07.600> to<00:05:07.780> for<00:05:08.080> reading<00:05:08.320> that 00:05:08.340 --> 00:05:08.350 align:start position:0% actually contribute to for reading that 00:05:08.350 --> 00:05:09.810 align:start position:0% actually contribute to for reading that topic<00:05:08.830> and<00:05:09.010> we're<00:05:09.160> not<00:05:09.250> burning<00:05:09.490> and 00:05:09.810 --> 00:05:09.820 align:start position:0% topic and we're not burning and 00:05:09.820 --> 00:05:11.159 align:start position:0% topic and we're not burning and burdening<00:05:10.240> the<00:05:10.419> rest<00:05:10.630> of<00:05:10.750> the<00:05:10.840> peers<00:05:11.020> of<00:05:11.140> the 00:05:11.159 --> 00:05:11.169 align:start position:0% burdening the rest of the peers of the 00:05:11.169 --> 00:05:12.659 align:start position:0% burdening the rest of the peers of the network<00:05:11.530> that<00:05:11.740> are<00:05:11.830> not<00:05:11.979> invested<00:05:12.490> in<00:05:12.550> a 00:05:12.659 --> 00:05:12.669 align:start position:0% network that are not invested in a 00:05:12.669 --> 00:05:14.780 align:start position:0% network that are not invested in a particular<00:05:12.790> topic<00:05:13.390> and<00:05:13.510> disseminating<00:05:14.140> that 00:05:14.780 --> 00:05:14.790 align:start position:0% particular topic and disseminating that 00:05:14.790 --> 00:05:17.940 align:start position:0% particular topic and disseminating that it<00:05:15.790> has<00:05:15.970> to<00:05:16.150> be<00:05:16.270> scalable<00:05:16.570> across<00:05:17.229> various 00:05:17.940 --> 00:05:17.950 align:start position:0% it has to be scalable across various 00:05:17.950 --> 00:05:20.610 align:start position:0% it has to be scalable across various axes<00:05:18.340> and<00:05:18.640> so<00:05:19.090> we<00:05:19.570> learn<00:05:19.750> about<00:05:19.780> number<00:05:20.590> of 00:05:20.610 --> 00:05:20.620 align:start position:0% axes and so we learn about number of 00:05:20.620 --> 00:05:22.380 align:start position:0% axes and so we learn about number of nodes<00:05:20.890> number<00:05:21.430> of<00:05:21.550> domains<00:05:21.910> messages 00:05:22.380 --> 00:05:22.390 align:start position:0% nodes number of domains messages 00:05:22.390 --> 00:05:24.240 align:start position:0% nodes number of domains messages subscriptions<00:05:22.930> subscribers<00:05:23.530> all<00:05:23.950> of<00:05:24.100> these 00:05:24.240 --> 00:05:24.250 align:start position:0% subscriptions subscribers all of these 00:05:24.250 --> 00:05:26.460 align:start position:0% subscriptions subscribers all of these are<00:05:24.400> different<00:05:24.520> axes<00:05:25.000> for<00:05:25.660> scalability 00:05:26.460 --> 00:05:26.470 align:start position:0% are different axes for scalability 00:05:26.470 --> 00:05:28.910 align:start position:0% are different axes for scalability there<00:05:27.460> has<00:05:27.550> to<00:05:27.580> be<00:05:27.729> a<00:05:27.820> law<00:05:28.030> where<00:05:28.300> we<00:05:28.360> have<00:05:28.570> four 00:05:28.910 --> 00:05:28.920 align:start position:0% there has to be a law where we have four 00:05:28.920 --> 00:05:32.900 align:start position:0% there has to be a law where we have four sssay<00:05:29.760> as<00:05:30.000> I<00:05:30.060> say<00:05:30.410> we<00:05:31.410> are<00:05:31.740> relying<00:05:32.190> on<00:05:32.400> peers 00:05:32.900 --> 00:05:32.910 align:start position:0% sssay as I say we are relying on peers 00:05:32.910 --> 00:05:35.420 align:start position:0% sssay as I say we are relying on peers making<00:05:33.390> little<00:05:33.840> decisions<00:05:34.290> so<00:05:34.710> that<00:05:34.740> messages 00:05:35.420 --> 00:05:35.430 align:start position:0% making little decisions so that messages 00:05:35.430 --> 00:05:38.120 align:start position:0% making little decisions so that messages are<00:05:35.610> greatly<00:05:35.970> routed<00:05:36.480> in<00:05:36.630> the<00:05:36.750> network<00:05:37.130> and 00:05:38.120 --> 00:05:38.130 align:start position:0% are greatly routed in the network and 00:05:38.130 --> 00:05:39.770 align:start position:0% are greatly routed in the network and ideally<00:05:38.580> what<00:05:38.850> not<00:05:39.030> a<00:05:39.060> protocol<00:05:39.540> that<00:05:39.660> is 00:05:39.770 --> 00:05:39.780 align:start position:0% ideally what not a protocol that is 00:05:39.780 --> 00:05:41.960 align:start position:0% ideally what not a protocol that is simple<00:05:40.140> and<00:05:40.170> easy<00:05:40.410> to<00:05:40.620> understand<00:05:41.070> so<00:05:41.400> we'll 00:05:41.960 --> 00:05:41.970 align:start position:0% simple and easy to understand so we'll 00:05:41.970 --> 00:05:43.490 align:start position:0% simple and easy to understand so we'll see<00:05:42.120> if<00:05:42.180> we've<00:05:42.360> actually<00:05:42.690> managed<00:05:43.170> to<00:05:43.230> do<00:05:43.380> this 00:05:43.490 --> 00:05:43.500 align:start position:0% see if we've actually managed to do this 00:05:43.500 --> 00:05:45.740 align:start position:0% see if we've actually managed to do this one<00:05:43.680> gossip<00:05:43.980> session<00:05:44.160> at<00:05:44.340> them<00:05:44.490> all<00:05:45.330> right<00:05:45.450> so 00:05:45.740 --> 00:05:45.750 align:start position:0% one gossip session at them all right so 00:05:45.750 --> 00:05:48.110 align:start position:0% one gossip session at them all right so what<00:05:45.990> does<00:05:46.080> gossip<00:05:46.470> so<00:05:46.620> the<00:05:47.550> key<00:05:47.700> elements<00:05:48.060> of 00:05:48.110 --> 00:05:48.120 align:start position:0% what does gossip so the key elements of 00:05:48.120 --> 00:05:49.790 align:start position:0% what does gossip so the key elements of gossip<00:05:48.480> serve<00:05:48.660> is<00:05:48.840> that<00:05:49.020> first<00:05:49.350> of<00:05:49.470> all<00:05:49.590> is<00:05:49.770> a 00:05:49.790 --> 00:05:49.800 align:start position:0% gossip serve is that first of all is a 00:05:49.800 --> 00:05:52.070 align:start position:0% gossip serve is that first of all is a scalable<00:05:50.340> and<00:05:50.580> extensible<00:05:51.090> pops<00:05:51.360> up<00:05:51.510> so 00:05:52.070 --> 00:05:52.080 align:start position:0% scalable and extensible pops up so 00:05:52.080 --> 00:05:54.740 align:start position:0% scalable and extensible pops up so concepts<00:05:52.830> on<00:05:52.980> in<00:05:53.190> itself<00:05:53.760> is<00:05:54.000> not<00:05:54.540> necessarily 00:05:54.740 --> 00:05:54.750 align:start position:0% concepts on in itself is not necessarily 00:05:54.750 --> 00:05:58.280 align:start position:0% concepts on in itself is not necessarily intended<00:05:55.620> to<00:05:55.980> be<00:05:56.190> the<00:05:56.580> final<00:05:57.240> usage<00:05:57.960> of<00:05:58.200> a 00:05:58.280 --> 00:05:58.290 align:start position:0% intended to be the final usage of a 00:05:58.290 --> 00:05:59.570 align:start position:0% intended to be the final usage of a peer-to-peer<00:05:58.530> protocol<00:05:59.190> for<00:05:59.370> peer-to-peer 00:05:59.570 --> 00:05:59.580 align:start position:0% peer-to-peer protocol for peer-to-peer 00:05:59.580 --> 00:06:01.910 align:start position:0% peer-to-peer protocol for peer-to-peer support<00:06:00.210> well<00:06:00.600> it<00:06:00.750> is<00:06:00.870> a<00:06:00.900> protocol<00:06:01.380> on<00:06:01.530> top<00:06:01.770> of 00:06:01.910 --> 00:06:01.920 align:start position:0% support well it is a protocol on top of 00:06:01.920 --> 00:06:05.060 align:start position:0% support well it is a protocol on top of which<00:06:02.190> we<00:06:02.850> can<00:06:03.090> overlay<00:06:03.680> different<00:06:04.680> routers 00:06:05.060 --> 00:06:05.070 align:start position:0% which we can overlay different routers 00:06:05.070 --> 00:06:08.480 align:start position:0% which we can overlay different routers to<00:06:05.550> take<00:06:06.180> different<00:06:06.420> decisions<00:06:07.020> and<00:06:07.830> pops<00:06:08.280> up 00:06:08.480 --> 00:06:08.490 align:start position:0% to take different decisions and pops up 00:06:08.490 --> 00:06:10.310 align:start position:0% to take different decisions and pops up entry<00:06:08.970> and<00:06:09.210> gossip<00:06:09.540> some<00:06:09.720> actually<00:06:10.020> provides 00:06:10.310 --> 00:06:10.320 align:start position:0% entry and gossip some actually provides 00:06:10.320 --> 00:06:13.340 align:start position:0% entry and gossip some actually provides the<00:06:10.410> primitives<00:06:11.040> to<00:06:12.030> make<00:06:12.180> sure<00:06:12.390> that<00:06:12.750> first 00:06:13.340 --> 00:06:13.350 align:start position:0% the primitives to make sure that first 00:06:13.350 --> 00:06:15.170 align:start position:0% the primitives to make sure that first of<00:06:13.500> all<00:06:13.620> messages<00:06:13.950> are<00:06:14.310> into<00:06:14.610> the<00:06:14.730> grade<00:06:14.910> and 00:06:15.170 --> 00:06:15.180 align:start position:0% of all messages are into the grade and 00:06:15.180 --> 00:06:17.090 align:start position:0% of all messages are into the grade and second<00:06:15.600> that's<00:06:15.750> enough<00:06:16.140> gossip<00:06:16.560> mentally 00:06:17.090 --> 00:06:17.100 align:start position:0% second that's enough gossip mentally 00:06:17.100 --> 00:06:18.790 align:start position:0% second that's enough gossip mentally test<00:06:17.370> circulating<00:06:17.790> on<00:06:18.000> the<00:06:18.090> network<00:06:18.390> so<00:06:18.570> that 00:06:18.790 --> 00:06:18.800 align:start position:0% test circulating on the network so that 00:06:18.800 --> 00:06:21.680 align:start position:0% test circulating on the network so that different<00:06:19.800> and<00:06:20.100> alternative<00:06:20.610> decisions<00:06:21.510> can 00:06:21.680 --> 00:06:21.690 align:start position:0% different and alternative decisions can 00:06:21.690 --> 00:06:23.990 align:start position:0% different and alternative decisions can be<00:06:21.720> taken<00:06:21.840> on<00:06:22.320> the<00:06:22.410> way<00:06:22.560> it<00:06:23.160> was<00:06:23.280> ambition<00:06:23.760> and 00:06:23.990 --> 00:06:24.000 align:start position:0% be taken on the way it was ambition and 00:06:24.000 --> 00:06:26.230 align:start position:0% be taken on the way it was ambition and specified<00:06:24.750> initially<00:06:25.200> by<00:06:25.350> a<00:06:25.380> developer 00:06:26.230 --> 00:06:26.240 align:start position:0% specified initially by a developer 00:06:26.240 --> 00:06:28.850 align:start position:0% specified initially by a developer called<00:06:27.240> be<00:06:27.510> so<00:06:27.690> he's<00:06:27.990> a<00:06:28.290> millipedes<00:06:28.710> of<00:06:28.800> the 00:06:28.850 --> 00:06:28.860 align:start position:0% called be so he's a millipedes of the 00:06:28.860 --> 00:06:30.710 align:start position:0% called be so he's a millipedes of the quarantine<00:06:29.160> and<00:06:29.490> as<00:06:29.970> I<00:06:30.060> said<00:06:30.120> it<00:06:30.330> provides<00:06:30.600> a 00:06:30.710 --> 00:06:30.720 align:start position:0% quarantine and as I said it provides a 00:06:30.720 --> 00:06:32.540 align:start position:0% quarantine and as I said it provides a base<00:06:30.900> layer<00:06:31.140> and<00:06:31.560> primitives<00:06:32.250> to<00:06:32.310> build 00:06:32.540 --> 00:06:32.550 align:start position:0% base layer and primitives to build 00:06:32.550 --> 00:06:34.400 align:start position:0% base layer and primitives to build adaptive<00:06:32.790> self<00:06:33.450> optimizing<00:06:33.600> routing 00:06:34.400 --> 00:06:34.410 align:start position:0% adaptive self optimizing routing 00:06:34.410 --> 00:06:36.590 align:start position:0% adaptive self optimizing routing algorithms<00:06:34.950> capable<00:06:35.790> of<00:06:35.940> repair<00:06:36.300> and 00:06:36.590 --> 00:06:36.600 align:start position:0% algorithms capable of repair and 00:06:36.600 --> 00:06:37.850 align:start position:0% algorithms capable of repair and rearrangements<00:06:37.290> on<00:06:37.380> the<00:06:37.440> network<00:06:37.710> to<00:06:37.830> the 00:06:37.850 --> 00:06:37.860 align:start position:0% rearrangements on the network to the 00:06:37.860 --> 00:06:40.880 align:start position:0% rearrangements on the network to the presence<00:06:38.250> of<00:06:38.340> churn<00:06:38.640> and<00:06:39.000> so<00:06:39.120> on<00:06:39.240> so<00:06:40.200> the<00:06:40.650> key 00:06:40.880 --> 00:06:40.890 align:start position:0% presence of churn and so on so the key 00:06:40.890 --> 00:06:42.500 align:start position:0% presence of churn and so on so the key aspect<00:06:41.340> of<00:06:41.430> concepts<00:06:41.820> up<00:06:42.000> is<00:06:42.180> that<00:06:42.360> it 00:06:42.500 --> 00:06:42.510 align:start position:0% aspect of concepts up is that it 00:06:42.510 --> 00:06:45.680 align:start position:0% aspect of concepts up is that it combines<00:06:42.930> stable<00:06:43.920> reciprocal<00:06:44.610> Misha's<00:06:45.000> with 00:06:45.680 --> 00:06:45.690 align:start position:0% combines stable reciprocal Misha's with 00:06:45.690 --> 00:06:47.570 align:start position:0% combines stable reciprocal Misha's with gossip<00:06:46.080> about<00:06:46.230> message<00:06:46.710> flow<00:06:46.890> metadata<00:06:47.310> would 00:06:47.570 --> 00:06:47.580 align:start position:0% gossip about message flow metadata would 00:06:47.580 --> 00:06:48.920 align:start position:0% gossip about message flow metadata would dig<00:06:47.700> into<00:06:47.820> this<00:06:48.000> in<00:06:48.150> a<00:06:48.210> second<00:06:48.540> and<00:06:48.750> this 00:06:48.920 --> 00:06:48.930 align:start position:0% dig into this in a second and this 00:06:48.930 --> 00:06:51.140 align:start position:0% dig into this in a second and this exceeds<00:06:49.260> a<00:06:49.500> protocol<00:06:49.980> that<00:06:50.250> we<00:06:50.760> had<00:06:50.940> in<00:06:51.060> the 00:06:51.140 --> 00:06:51.150 align:start position:0% exceeds a protocol that we had in the 00:06:51.150 --> 00:06:52.430 align:start position:0% exceeds a protocol that we had in the living<00:06:51.240> to<00:06:51.450> be<00:06:51.570> stab<00:06:51.840> which<00:06:52.080> is<00:06:52.230> called 00:06:52.430 --> 00:06:52.440 align:start position:0% living to be stab which is called 00:06:52.440 --> 00:06:54.980 align:start position:0% living to be stab which is called flutter<00:06:52.710> and<00:06:53.160> it's<00:06:53.400> the<00:06:54.150> basically<00:06:54.780> the 00:06:54.980 --> 00:06:54.990 align:start position:0% flutter and it's the basically the 00:06:54.990 --> 00:06:57.860 align:start position:0% flutter and it's the basically the dumbest<00:06:55.260> protocol<00:06:55.680> in<00:06:56.460> terms<00:06:56.820> of<00:06:57.090> views<00:06:57.750> of 00:06:57.860 --> 00:06:57.870 align:start position:0% dumbest protocol in terms of views of 00:06:57.870 --> 00:06:59.930 align:start position:0% dumbest protocol in terms of views of your<00:06:58.050> pops<00:06:58.260> up<00:06:58.440> you<00:06:58.860> disseminated<00:06:59.610> a<00:06:59.640> message 00:06:59.930 --> 00:06:59.940 align:start position:0% your pops up you disseminated a message 00:06:59.940 --> 00:07:01.520 align:start position:0% your pops up you disseminated a message to<00:07:00.150> every<00:07:00.420> period<00:07:00.840> that<00:07:01.020> you<00:07:01.110> connected<00:07:01.470> to 00:07:01.520 --> 00:07:01.530 align:start position:0% to every period that you connected to 00:07:01.530 --> 00:07:03.200 align:start position:0% to every period that you connected to that<00:07:01.830> universe<00:07:02.160> and<00:07:02.310> customer<00:07:02.700> time<00:07:02.910> right 00:07:03.200 --> 00:07:03.210 align:start position:0% that universe and customer time right 00:07:03.210 --> 00:07:05.180 align:start position:0% that universe and customer time right which<00:07:03.690> has<00:07:03.900> which<00:07:04.470> is<00:07:04.500> creating<00:07:04.920> thickness 00:07:05.180 --> 00:07:05.190 align:start position:0% which has which is creating thickness 00:07:05.190 --> 00:07:07.340 align:start position:0% which has which is creating thickness its<00:07:05.370> proboscis<00:07:05.730> with<00:07:06.090> Zambia<00:07:06.390> then<00:07:06.690> you<00:07:07.230> know 00:07:07.340 --> 00:07:07.350 align:start position:0% its proboscis with Zambia then you know 00:07:07.350 --> 00:07:09.350 align:start position:0% its proboscis with Zambia then you know you<00:07:07.560> can<00:07:07.830> take<00:07:08.160> minimal<00:07:08.670> needs<00:07:08.880> and<00:07:09.030> teapots 00:07:09.350 --> 00:07:09.360 align:start position:0% you can take minimal needs and teapots 00:07:09.360 --> 00:07:11.240 align:start position:0% you can take minimal needs and teapots because<00:07:09.750> you<00:07:10.380> just<00:07:10.590> push<00:07:10.740> that<00:07:10.770> message<00:07:11.130> out 00:07:11.240 --> 00:07:11.250 align:start position:0% because you just push that message out 00:07:11.250 --> 00:07:15.620 align:start position:0% because you just push that message out and<00:07:11.580> well<00:07:12.360> those<00:07:13.080> beers<00:07:13.350> that<00:07:13.560> are<00:07:14.390> are<00:07:15.390> close 00:07:15.620 --> 00:07:15.630 align:start position:0% and well those beers that are are close 00:07:15.630 --> 00:07:16.540 align:start position:0% and well those beers that are are close closely 00:07:16.540 --> 00:07:16.550 align:start position:0% closely 00:07:16.550 --> 00:07:18.460 align:start position:0% closely and<00:07:17.120> have<00:07:17.330> a<00:07:17.360> pass<00:07:17.660> thing<00:07:17.840> with<00:07:17.990> you<00:07:18.110> what<00:07:18.320> was 00:07:18.460 --> 00:07:18.470 align:start position:0% and have a pass thing with you what was 00:07:18.470 --> 00:07:19.870 align:start position:0% and have a pass thing with you what was he<00:07:18.590> the<00:07:18.680> first<00:07:18.710> but<00:07:19.100> it<00:07:19.190> also<00:07:19.340> creates<00:07:19.730> a<00:07:19.850> lot 00:07:19.870 --> 00:07:19.880 align:start position:0% he the first but it also creates a lot 00:07:19.880 --> 00:07:22.180 align:start position:0% he the first but it also creates a lot of<00:07:20.240> write<00:07:20.600> amplification<00:07:21.020> and<00:07:21.590> it<00:07:22.100> basically 00:07:22.180 --> 00:07:22.190 align:start position:0% of write amplification and it basically 00:07:22.190 --> 00:07:25.330 align:start position:0% of write amplification and it basically plops<00:07:22.760> clogs<00:07:23.210> up<00:07:23.420> the<00:07:23.690> bandwidth<00:07:24.350> is<00:07:25.040> you 00:07:25.330 --> 00:07:25.340 align:start position:0% plops clogs up the bandwidth is you 00:07:25.340 --> 00:07:26.710 align:start position:0% plops clogs up the bandwidth is you creating<00:07:25.760> a<00:07:25.820> lot<00:07:25.970> of<00:07:26.090> duplication<00:07:26.480> of<00:07:26.660> the 00:07:26.710 --> 00:07:26.720 align:start position:0% creating a lot of duplication of the 00:07:26.720 --> 00:07:29.170 align:start position:0% creating a lot of duplication of the network<00:07:27.080> as<00:07:27.740> I<00:07:27.800> said<00:07:28.100> bas<00:07:28.400> observe<00:07:28.760> is<00:07:28.970> the 00:07:29.170 --> 00:07:29.180 align:start position:0% network as I said bas observe is the 00:07:29.180 --> 00:07:30.970 align:start position:0% network as I said bas observe is the stepping<00:07:29.450> stone<00:07:29.810> towards<00:07:30.230> the<00:07:30.350> grand<00:07:30.740> mission 00:07:30.970 --> 00:07:30.980 align:start position:0% stepping stone towards the grand mission 00:07:30.980 --> 00:07:34.300 align:start position:0% stepping stone towards the grand mission of<00:07:31.490> episode<00:07:32.270> which<00:07:32.720> is<00:07:32.750> I'll<00:07:33.710> introduce<00:07:33.980> it<00:07:34.250> a 00:07:34.300 --> 00:07:34.310 align:start position:0% of episode which is I'll introduce it a 00:07:34.310 --> 00:07:37.600 align:start position:0% of episode which is I'll introduce it a bit<00:07:34.490> later<00:07:34.670> basically<00:07:35.450> come<00:07:36.050> talk<00:07:36.370> on<00:07:37.370> God's 00:07:37.600 --> 00:07:37.610 align:start position:0% bit later basically come talk on God's 00:07:37.610 --> 00:07:41.010 align:start position:0% bit later basically come talk on God's ideas<00:07:38.240> from<00:07:38.420> plum<00:07:38.660> tree<00:07:38.870> hi<00:07:39.380> Barney<00:07:39.740> on<00:07:39.860> August 00:07:41.010 --> 00:07:41.020 align:start position:0% ideas from plum tree hi Barney on August 00:07:41.020 --> 00:07:43.780 align:start position:0% ideas from plum tree hi Barney on August morning<00:07:42.020> the<00:07:42.320> steepness<00:07:42.620> of<00:07:43.040> gossip<00:07:43.430> sub<00:07:43.610> is 00:07:43.780 --> 00:07:43.790 align:start position:0% morning the steepness of gossip sub is 00:07:43.790 --> 00:07:46.000 align:start position:0% morning the steepness of gossip sub is currently<00:07:44.270> off<00:07:44.600> right<00:07:45.290> and<00:07:45.530> this<00:07:45.680> is<00:07:45.830> very 00:07:46.000 --> 00:07:46.010 align:start position:0% currently off right and this is very 00:07:46.010 --> 00:07:49.240 align:start position:0% currently off right and this is very important<00:07:46.430> for<00:07:46.580> people<00:07:46.640> to<00:07:47.440> understand<00:07:48.440> it<00:07:48.620> is 00:07:49.240 --> 00:07:49.250 align:start position:0% important for people to understand it is 00:07:49.250 --> 00:07:51.490 align:start position:0% important for people to understand it is a<00:07:49.780> protocol<00:07:50.780> that<00:07:50.840> we're<00:07:51.200> gonna<00:07:51.290> continue 00:07:51.490 --> 00:07:51.500 align:start position:0% a protocol that we're gonna continue 00:07:51.500 --> 00:07:54.340 align:start position:0% a protocol that we're gonna continue iterating<00:07:52.040> on<00:07:52.550> over<00:07:53.300> and<00:07:53.480> over<00:07:53.690> again<00:07:53.810> and<00:07:54.200> as 00:07:54.340 --> 00:07:54.350 align:start position:0% iterating on over and over again and as 00:07:54.350 --> 00:07:56.020 align:start position:0% iterating on over and over again and as I<00:07:54.470> said<00:07:54.620> it's<00:07:54.830> a<00:07:54.890> stepping<00:07:55.160> stone<00:07:55.520> towards 00:07:56.020 --> 00:07:56.030 align:start position:0% I said it's a stepping stone towards 00:07:56.030 --> 00:08:00.400 align:start position:0% I said it's a stepping stone towards this<00:07:56.270> more<00:07:56.810> stable<00:07:57.320> and<00:07:57.580> feature<00:07:59.410> feature 00:08:00.400 --> 00:08:00.410 align:start position:0% this more stable and feature feature 00:08:00.410 --> 00:08:02.470 align:start position:0% this more stable and feature feature movie<00:08:00.710> protocol<00:08:01.130> called<00:08:01.400> episode<00:08:02.180> there<00:08:02.360> are 00:08:02.470 --> 00:08:02.480 align:start position:0% movie protocol called episode there are 00:08:02.480 --> 00:08:05.740 align:start position:0% movie protocol called episode there are three<00:08:02.720> implementations<00:08:03.470> there<00:08:04.250> is<00:08:04.750> reference 00:08:05.740 --> 00:08:05.750 align:start position:0% three implementations there is reference 00:08:05.750 --> 00:08:07.990 align:start position:0% three implementations there is reference implementation<00:08:06.350> and<00:08:06.500> go<00:08:06.650> but<00:08:07.370> they<00:08:07.850> need<00:08:07.970> to 00:08:07.990 --> 00:08:08.000 align:start position:0% implementation and go but they need to 00:08:08.000 --> 00:08:10.060 align:start position:0% implementation and go but they need to be<00:08:08.090> important<00:08:08.450> to<00:08:08.480> be<00:08:08.570> produced<00:08:08.930> there<00:08:09.590> is<00:08:09.800> a 00:08:10.060 --> 00:08:10.070 align:start position:0% be important to be produced there is a 00:08:10.070 --> 00:08:11.920 align:start position:0% be important to be produced there is a implementation<00:08:10.970> by<00:08:11.090> the<00:08:11.150> Sigma<00:08:11.450> Prime<00:08:11.720> guys 00:08:11.920 --> 00:08:11.930 align:start position:0% implementation by the Sigma Prime guys 00:08:11.930 --> 00:08:13.240 align:start position:0% implementation by the Sigma Prime guys who<00:08:12.200> are<00:08:12.290> just<00:08:12.530> here<00:08:12.680> raise<00:08:12.890> your<00:08:12.920> hands 00:08:13.240 --> 00:08:13.250 align:start position:0% who are just here raise your hands 00:08:13.250 --> 00:08:16.660 align:start position:0% who are just here raise your hands please<00:08:13.340> get<00:08:14.150> some<00:08:14.300> credit<00:08:14.770> fantastic<00:08:15.770> it's 00:08:16.660 --> 00:08:16.670 align:start position:0% please get some credit fantastic it's 00:08:16.670 --> 00:08:18.640 align:start position:0% please get some credit fantastic it's going<00:08:16.910> to<00:08:17.000> be<00:08:17.060> sitting<00:08:17.240> in<00:08:17.420> a<00:08:17.840> fork<00:08:18.080> and<00:08:18.320> I 00:08:18.640 --> 00:08:18.650 align:start position:0% going to be sitting in a fork and I 00:08:18.650 --> 00:08:20.980 align:start position:0% going to be sitting in a fork and I don't<00:08:18.830> have<00:08:18.950> the<00:08:19.040> chain<00:08:19.220> same<00:08:19.400> guys<00:08:19.610> here<00:08:20.180> I 00:08:20.980 --> 00:08:20.990 align:start position:0% don't have the chain same guys here I 00:08:20.990 --> 00:08:22.960 align:start position:0% don't have the chain same guys here I don't<00:08:21.710> think<00:08:21.860> they<00:08:21.950> are<00:08:22.070> but<00:08:22.340> they<00:08:22.610> also 00:08:22.960 --> 00:08:22.970 align:start position:0% don't think they are but they also 00:08:22.970 --> 00:08:24.970 align:start position:0% don't think they are but they also contribute<00:08:23.630> to<00:08:23.660> and<00:08:24.050> they<00:08:24.440> created<00:08:24.830> a 00:08:24.970 --> 00:08:24.980 align:start position:0% contribute to and they created a 00:08:24.980 --> 00:08:28.180 align:start position:0% contribute to and they created a concepts<00:08:25.340> of<00:08:25.460> implementation<00:08:26.030> James<00:08:26.950> cool<00:08:27.950> so 00:08:28.180 --> 00:08:28.190 align:start position:0% concepts of implementation James cool so 00:08:28.190 --> 00:08:29.100 align:start position:0% concepts of implementation James cool so how<00:08:28.490> does<00:08:28.550> it<00:08:28.700> work 00:08:29.100 --> 00:08:29.110 align:start position:0% how does it work 00:08:29.110 --> 00:08:31.540 align:start position:0% how does it work I'm<00:08:30.110> gonna<00:08:30.290> go<00:08:30.500> through<00:08:30.770> differently<00:08:31.250> years 00:08:31.540 --> 00:08:31.550 align:start position:0% I'm gonna go through differently years 00:08:31.550 --> 00:08:36.310 align:start position:0% I'm gonna go through differently years of<00:08:32.330> the<00:08:32.750> protocol<00:08:33.620> together<00:08:33.980> I<00:08:34.100> do<00:08:34.250> a<00:08:34.700> wall<00:08:35.320> so 00:08:36.310 --> 00:08:36.320 align:start position:0% of the protocol together I do a wall so 00:08:36.320 --> 00:08:38.230 align:start position:0% of the protocol together I do a wall so the<00:08:36.410> first<00:08:36.650> thing<00:08:36.830> that<00:08:37.430> you<00:08:37.670> need<00:08:38.210> to 00:08:38.230 --> 00:08:38.240 align:start position:0% the first thing that you need to 00:08:38.240 --> 00:08:40.300 align:start position:0% the first thing that you need to understand<00:08:38.840> is<00:08:39.110> that<00:08:39.170> Glossop<00:08:39.650> stuff<00:08:39.830> isn't 00:08:40.300 --> 00:08:40.310 align:start position:0% understand is that Glossop stuff isn't 00:08:40.310 --> 00:08:42.760 align:start position:0% understand is that Glossop stuff isn't actually<00:08:40.790> a<00:08:41.000> hybrid<00:08:41.870> of<00:08:42.020> two<00:08:42.200> different 00:08:42.760 --> 00:08:42.770 align:start position:0% actually a hybrid of two different 00:08:42.770 --> 00:08:45.640 align:start position:0% actually a hybrid of two different networks<00:08:42.860> right<00:08:43.730> that<00:08:44.420> are<00:08:44.690> on<00:08:45.290> the<00:08:45.500> same 00:08:45.640 --> 00:08:45.650 align:start position:0% networks right that are on the same 00:08:45.650 --> 00:08:48.040 align:start position:0% networks right that are on the same notable<00:08:46.130> that<00:08:46.460> are<00:08:46.640> on<00:08:47.180> the<00:08:47.450> same<00:08:47.600> underneath 00:08:48.040 --> 00:08:48.050 align:start position:0% notable that are on the same underneath 00:08:48.050 --> 00:08:51.220 align:start position:0% notable that are on the same underneath there<00:08:48.530> is<00:08:48.620> a<00:08:48.650> full<00:08:49.010> message<00:08:49.220> network<00:08:49.990> porn<00:08:50.990> bar 00:08:51.220 --> 00:08:51.230 align:start position:0% there is a full message network porn bar 00:08:51.230 --> 00:08:53.050 align:start position:0% there is a full message network porn bar reciprocal<00:08:51.800> links<00:08:52.160> through<00:08:52.430> which<00:08:52.580> messages 00:08:53.050 --> 00:08:53.060 align:start position:0% reciprocal links through which messages 00:08:53.060 --> 00:08:55.780 align:start position:0% reciprocal links through which messages are<00:08:53.210> forwarded<00:08:53.630> and<00:08:53.840> this<00:08:54.020> is<00:08:54.520> for<00:08:55.520> superable 00:08:55.780 --> 00:08:55.790 align:start position:0% are forwarded and this is for superable 00:08:55.790 --> 00:08:57.880 align:start position:0% are forwarded and this is for superable expect<00:08:56.210> to<00:08:56.390> keep<00:08:56.570> the<00:08:56.960> word<00:08:57.170> reciprocal<00:08:57.770> is 00:08:57.880 --> 00:08:57.890 align:start position:0% expect to keep the word reciprocal is 00:08:57.890 --> 00:09:00.250 align:start position:0% expect to keep the word reciprocal is very<00:08:58.070> important<00:08:58.550> because<00:08:58.790> this<00:08:59.780> is<00:08:59.840> supposed 00:09:00.250 --> 00:09:00.260 align:start position:0% very important because this is supposed 00:09:00.260 --> 00:09:03.460 align:start position:0% very important because this is supposed to<00:09:00.320> be<00:09:00.470> a<00:09:00.680> stable<00:09:00.980> mesh<00:09:01.750> where<00:09:02.750> peers<00:09:03.200> are 00:09:03.460 --> 00:09:03.470 align:start position:0% to be a stable mesh where peers are 00:09:03.470 --> 00:09:06.070 align:start position:0% to be a stable mesh where peers are actually<00:09:04.270> exchanging<00:09:05.270> messages<00:09:05.420> with<00:09:05.900> one 00:09:06.070 --> 00:09:06.080 align:start position:0% actually exchanging messages with one 00:09:06.080 --> 00:09:09.760 align:start position:0% actually exchanging messages with one another<00:09:06.380> so<00:09:06.740> if<00:09:07.010> I<00:09:07.310> if<00:09:07.730> I'm<00:09:08.270> puree<00:09:08.570> and<00:09:09.140> there 00:09:09.760 --> 00:09:09.770 align:start position:0% another so if I if I'm puree and there 00:09:09.770 --> 00:09:12.220 align:start position:0% another so if I if I'm puree and there is<00:09:09.890> interacting<00:09:10.730> with<00:09:10.760> peer<00:09:11.060> be<00:09:11.240> in<00:09:11.510> a<00:09:12.020> topic 00:09:12.220 --> 00:09:12.230 align:start position:0% is interacting with peer be in a topic 00:09:12.230 --> 00:09:14.110 align:start position:0% is interacting with peer be in a topic these<00:09:12.860> two<00:09:13.070> peers<00:09:13.340> will<00:09:13.640> actually<00:09:14.000> be 00:09:14.110 --> 00:09:14.120 align:start position:0% these two peers will actually be 00:09:14.120 --> 00:09:15.910 align:start position:0% these two peers will actually be exchanging<00:09:14.630> messages<00:09:14.750> with<00:09:15.170> one<00:09:15.380> another<00:09:15.680> in 00:09:15.910 --> 00:09:15.920 align:start position:0% exchanging messages with one another in 00:09:15.920 --> 00:09:18.250 align:start position:0% exchanging messages with one another in system<00:09:16.250> and<00:09:16.460> then<00:09:17.120> there<00:09:17.240> is<00:09:17.330> a<00:09:17.360> metadata<00:09:17.810> on<00:09:18.170> a 00:09:18.250 --> 00:09:18.260 align:start position:0% system and then there is a metadata on a 00:09:18.260 --> 00:09:20.050 align:start position:0% system and then there is a metadata on a network<00:09:18.470> that<00:09:18.650> carries<00:09:19.040> gossips<00:09:19.460> about<00:09:19.670> which 00:09:20.050 --> 00:09:20.060 align:start position:0% network that carries gossips about which 00:09:20.060 --> 00:09:23.410 align:start position:0% network that carries gossips about which peers<00:09:20.410> what<00:09:21.410> peers<00:09:21.650> have<00:09:21.800> actually<00:09:22.130> seen<00:09:22.420> so 00:09:23.410 --> 00:09:23.420 align:start position:0% peers what peers have actually seen so 00:09:23.420 --> 00:09:25.270 align:start position:0% peers what peers have actually seen so as<00:09:23.780> I<00:09:23.870> said<00:09:24.050> the<00:09:24.140> full<00:09:24.320> message<00:09:24.500> network 00:09:25.270 --> 00:09:25.280 align:start position:0% as I said the full message network 00:09:25.280 --> 00:09:28.470 align:start position:0% as I said the full message network recall<00:09:25.880> that<00:09:25.970> mesh<00:09:26.330> is<00:09:26.570> a<00:09:27.200> sparsely<00:09:27.740> connected 00:09:28.470 --> 00:09:28.480 align:start position:0% recall that mesh is a sparsely connected 00:09:28.480 --> 00:09:31.090 align:start position:0% recall that mesh is a sparsely connected network<00:09:29.480> or<00:09:29.720> reciprocal<00:09:30.590> links<00:09:30.920> between 00:09:31.090 --> 00:09:31.100 align:start position:0% network or reciprocal links between 00:09:31.100 --> 00:09:33.430 align:start position:0% network or reciprocal links between peers<00:09:31.640> that<00:09:32.120> are<00:09:32.240> actively<00:09:32.660> consuming<00:09:33.320> and 00:09:33.430 --> 00:09:33.440 align:start position:0% peers that are actively consuming and 00:09:33.440 --> 00:09:35.380 align:start position:0% peers that are actively consuming and interesting<00:09:34.010> and<00:09:34.250> therefore<00:09:34.790> forwarding<00:09:35.210> a 00:09:35.380 --> 00:09:35.390 align:start position:0% interesting and therefore forwarding a 00:09:35.390 --> 00:09:37.840 align:start position:0% interesting and therefore forwarding a particular<00:09:36.050> topic<00:09:36.560> the<00:09:37.100> construction<00:09:37.640> of<00:09:37.700> the 00:09:37.840 --> 00:09:37.850 align:start position:0% particular topic the construction of the 00:09:37.850 --> 00:09:40.270 align:start position:0% particular topic the construction of the mesh<00:09:38.000> is<00:09:38.150> actually<00:09:38.480> randomized<00:09:38.990> and<00:09:39.350> is<00:09:39.470> self 00:09:40.270 --> 00:09:40.280 align:start position:0% mesh is actually randomized and is self 00:09:40.280 --> 00:09:42.310 align:start position:0% mesh is actually randomized and is self step<00:09:40.550> stabilizing<00:09:41.330> because<00:09:41.600> it<00:09:41.720> has<00:09:41.840> a<00:09:41.870> number 00:09:42.310 --> 00:09:42.320 align:start position:0% step stabilizing because it has a number 00:09:42.320 --> 00:09:44.650 align:start position:0% step stabilizing because it has a number of<00:09:42.590> stabilizing<00:09:43.250> from<00:09:43.550> its<00:09:44.000> particularly<00:09:44.510> the 00:09:44.650 --> 00:09:44.660 align:start position:0% of stabilizing from its particularly the 00:09:44.660 --> 00:09:48.610 align:start position:0% of stabilizing from its particularly the new<00:09:44.780> so<00:09:45.260> peers<00:09:45.920> will<00:09:46.690> are<00:09:47.690> configured<00:09:48.290> the 00:09:48.610 --> 00:09:48.620 align:start position:0% new so peers will are configured the 00:09:48.620 --> 00:09:50.470 align:start position:0% new so peers will are configured the mesh<00:09:48.770> is<00:09:48.890> configured<00:09:49.370> with<00:09:49.490> a<00:09:49.850> target<00:09:50.210> degree 00:09:50.470 --> 00:09:50.480 align:start position:0% mesh is configured with a target degree 00:09:50.480 --> 00:09:53.560 align:start position:0% mesh is configured with a target degree which<00:09:50.840> 1946<00:09:51.770> there<00:09:52.610> is<00:09:52.760> a<00:09:52.790> high<00:09:53.120> and<00:09:53.540> low 00:09:53.560 --> 00:09:53.570 align:start position:0% which 1946 there is a high and low 00:09:53.570 --> 00:09:56.110 align:start position:0% which 1946 there is a high and low watermark<00:09:54.050> which<00:09:54.770> by<00:09:55.070> default<00:09:55.130> is<00:09:55.550> four<00:09:55.880> and 00:09:56.110 --> 00:09:56.120 align:start position:0% watermark which by default is four and 00:09:56.120 --> 00:09:59.350 align:start position:0% watermark which by default is four and twelve<00:09:56.420> and<00:09:56.660> peers<00:09:57.440> will<00:09:57.680> strive<00:09:58.070> to<00:09:58.940> maintain 00:09:59.350 --> 00:09:59.360 align:start position:0% twelve and peers will strive to maintain 00:09:59.360 --> 00:10:03.060 align:start position:0% twelve and peers will strive to maintain the<00:10:00.350> connectedness<00:10:00.890> for<00:10:01.610> a<00:10:01.640> particular<00:10:01.940> topic 00:10:03.060 --> 00:10:03.070 align:start position:0% the connectedness for a particular topic 00:10:03.070 --> 00:10:06.850 align:start position:0% the connectedness for a particular topic at<00:10:04.270> an<00:10:05.270> optimal<00:10:05.720> level<00:10:05.750> of<00:10:06.050> six<00:10:06.350> taking 00:10:06.850 --> 00:10:06.860 align:start position:0% at an optimal level of six taking 00:10:06.860 --> 00:10:08.980 align:start position:0% at an optimal level of six taking compensating<00:10:07.550> action<00:10:07.940> whenever<00:10:08.480> it<00:10:08.840> goes 00:10:08.980 --> 00:10:08.990 align:start position:0% compensating action whenever it goes 00:10:08.990 --> 00:10:12.040 align:start position:0% compensating action whenever it goes above<00:10:09.950> below<00:10:10.460> the<00:10:10.760> low-water<00:10:11.330> mark<00:10:11.480> on<00:10:11.810> or 00:10:12.040 --> 00:10:12.050 align:start position:0% above below the low-water mark on or 00:10:12.050 --> 00:10:14.500 align:start position:0% above below the low-water mark on or above<00:10:12.740> the<00:10:12.800> high-water<00:10:13.130> line<00:10:13.460> this<00:10:13.760> is<00:10:13.820> how<00:10:14.360> we 00:10:14.500 --> 00:10:14.510 align:start position:0% above the high-water line this is how we 00:10:14.510 --> 00:10:17.920 align:start position:0% above the high-water line this is how we keep<00:10:14.690> that<00:10:14.930> that<00:10:15.700> that<00:10:16.700> leeway<00:10:17.150> to<00:10:17.630> avoid 00:10:17.920 --> 00:10:17.930 align:start position:0% keep that that that leeway to avoid 00:10:17.930 --> 00:10:21.550 align:start position:0% keep that that that leeway to avoid drastic<00:10:18.500> you<00:10:18.770> know<00:10:20.050> down<00:10:21.050> cutting<00:10:21.470> a 00:10:21.550 --> 00:10:21.560 align:start position:0% drastic you know down cutting a 00:10:21.560 --> 00:10:24.760 align:start position:0% drastic you know down cutting a numbering<00:10:21.890> anything<00:10:22.690> this<00:10:23.690> is<00:10:23.870> so<00:10:24.560> stable 00:10:24.760 --> 00:10:24.770 align:start position:0% numbering anything this is so stable 00:10:24.770 --> 00:10:26.920 align:start position:0% numbering anything this is so stable mesh<00:10:25.070> is<00:10:25.220> complemented<00:10:25.820> by<00:10:25.850> a<00:10:26.270> metadata 00:10:26.920 --> 00:10:26.930 align:start position:0% mesh is complemented by a metadata 00:10:26.930 --> 00:10:28.600 align:start position:0% mesh is complemented by a metadata linear<00:10:27.350> network<00:10:27.710> which<00:10:27.920> is<00:10:28.040> a<00:10:28.070> densely 00:10:28.600 --> 00:10:28.610 align:start position:0% linear network which is a densely 00:10:28.610 --> 00:10:31.650 align:start position:0% linear network which is a densely connected<00:10:28.820> network<00:10:29.480> that<00:10:30.110> augments<00:10:30.650> the<00:10:31.040> mesh 00:10:31.650 --> 00:10:31.660 align:start position:0% connected network that augments the mesh 00:10:31.660 --> 00:10:34.660 align:start position:0% connected network that augments the mesh with<00:10:32.660> gossip<00:10:33.380> propagation<00:10:34.160> about<00:10:34.460> which 00:10:34.660 --> 00:10:34.670 align:start position:0% with gossip propagation about which 00:10:34.670 --> 00:10:37.210 align:start position:0% with gossip propagation about which messages<00:10:35.150> are<00:10:35.360> actually<00:10:35.510> living<00:10:35.900> so<00:10:36.860> this 00:10:37.210 --> 00:10:37.220 align:start position:0% messages are actually living so this 00:10:37.220 --> 00:10:38.980 align:start position:0% messages are actually living so this enables<00:10:37.460> routing<00:10:37.970> decisions<00:10:38.420> to<00:10:38.570> be<00:10:38.660> made<00:10:38.690> if 00:10:38.980 --> 00:10:38.990 align:start position:0% enables routing decisions to be made if 00:10:38.990 --> 00:10:42.640 align:start position:0% enables routing decisions to be made if I<00:10:39.530> have<00:10:39.740> so<00:10:40.280> the<00:10:40.430> easy<00:10:41.390> way<00:10:41.630> to<00:10:41.660> put<00:10:41.930> this<00:10:42.080> is<00:10:42.290> in 00:10:42.640 --> 00:10:42.650 align:start position:0% I have so the easy way to put this is in 00:10:42.650 --> 00:10:46.090 align:start position:0% I have so the easy way to put this is in a<00:10:43.010> particular<00:10:43.130> topic<00:10:43.610> if<00:10:44.000> I<00:10:44.450> have<00:10:44.770> fifty<00:10:45.770> peers 00:10:46.090 --> 00:10:46.100 align:start position:0% a particular topic if I have fifty peers 00:10:46.100 --> 00:10:47.950 align:start position:0% a particular topic if I have fifty peers that<00:10:46.460> are<00:10:46.520> interested<00:10:47.150> that<00:10:47.180> are<00:10:47.450> consuming 00:10:47.950 --> 00:10:47.960 align:start position:0% that are interested that are consuming 00:10:47.960 --> 00:10:50.200 align:start position:0% that are interested that are consuming so<00:10:48.200> fifty<00:10:48.590> neighbors<00:10:48.920> of<00:10:49.100> fifteen<00:10:49.790> neighbors 00:10:50.200 --> 00:10:50.210 align:start position:0% so fifty neighbors of fifteen neighbors 00:10:50.210 --> 00:10:52.200 align:start position:0% so fifty neighbors of fifteen neighbors of<00:10:50.360> mine<00:10:50.540> are<00:10:51.410> interested 00:10:52.200 --> 00:10:52.210 align:start position:0% of mine are interested 00:10:52.210 --> 00:10:58.590 align:start position:0% of mine are interested in<00:10:52.600> a<00:10:53.020> particular<00:10:53.380> topic<00:10:56.279> six<00:10:57.279> right<00:10:58.180> in 00:10:58.590 --> 00:10:58.600 align:start position:0% in a particular topic six right in 00:10:58.600 --> 00:11:01.680 align:start position:0% in a particular topic six right in theory<00:10:59.080> based<00:10:59.890> on<00:11:00.040> the<00:11:00.220> one<00:11:00.760> on<00:11:01.089> the<00:11:01.270> stable 00:11:01.680 --> 00:11:01.690 align:start position:0% theory based on the one on the stable 00:11:01.690 --> 00:11:05.130 align:start position:0% theory based on the one on the stable mesh<00:11:01.899> the<00:11:02.800> remaining<00:11:03.550> so<00:11:04.330> the<00:11:04.450> remaining<00:11:04.930> nine 00:11:05.130 --> 00:11:05.140 align:start position:0% mesh the remaining so the remaining nine 00:11:05.140 --> 00:11:07.470 align:start position:0% mesh the remaining so the remaining nine will<00:11:05.529> turn<00:11:05.740> into<00:11:05.920> the<00:11:06.070> gossip<00:11:06.250> years<00:11:06.790> so<00:11:07.450> I 00:11:07.470 --> 00:11:07.480 align:start position:0% will turn into the gossip years so I 00:11:07.480 --> 00:11:09.269 align:start position:0% will turn into the gossip years so I would<00:11:07.779> not<00:11:07.960> exchange<00:11:08.200> messages<00:11:08.649> with<00:11:09.100> them 00:11:09.269 --> 00:11:09.279 align:start position:0% would not exchange messages with them 00:11:09.279 --> 00:11:11.730 align:start position:0% would not exchange messages with them but<00:11:09.820> I<00:11:09.850> will<00:11:10.089> I<00:11:10.540> will<00:11:10.779> collaborate<00:11:11.200> with<00:11:11.440> I'm 00:11:11.730 --> 00:11:11.740 align:start position:0% but I will I will collaborate with I'm 00:11:11.740 --> 00:11:13.440 align:start position:0% but I will I will collaborate with I'm telling<00:11:12.070> them<00:11:12.190> more<00:11:12.399> messages<00:11:12.880> I've<00:11:13.149> seen 00:11:13.440 --> 00:11:13.450 align:start position:0% telling them more messages I've seen 00:11:13.450 --> 00:11:15.449 align:start position:0% telling them more messages I've seen without<00:11:14.320> pushing<00:11:14.589> actually<00:11:15.100> without 00:11:15.449 --> 00:11:15.459 align:start position:0% without pushing actually without 00:11:15.459 --> 00:11:17.519 align:start position:0% without pushing actually without actually<00:11:15.790> she<00:11:16.029> has<00:11:16.180> adjusted<00:11:16.600> well<00:11:16.930> we'll<00:11:17.440> go 00:11:17.519 --> 00:11:17.529 align:start position:0% actually she has adjusted well we'll go 00:11:17.529 --> 00:11:21.660 align:start position:0% actually she has adjusted well we'll go through<00:11:17.709> this<00:11:17.800> is<00:11:18.990> so<00:11:20.160> how<00:11:21.160> does<00:11:21.220> copping 00:11:21.660 --> 00:11:21.670 align:start position:0% through this is so how does copping 00:11:21.670 --> 00:11:24.389 align:start position:0% through this is so how does copping membership<00:11:22.120> work<00:11:22.330> as<00:11:22.570> I<00:11:22.630> said<00:11:22.990> appear<00:11:23.980> can<00:11:24.370> be 00:11:24.389 --> 00:11:24.399 align:start position:0% membership work as I said appear can be 00:11:24.399 --> 00:11:27.320 align:start position:0% membership work as I said appear can be subscribed<00:11:25.149> and<00:11:25.420> the<00:11:25.839> emitting<00:11:26.320> messages<00:11:26.980> on 00:11:27.320 --> 00:11:27.330 align:start position:0% subscribed and the emitting messages on 00:11:27.330 --> 00:11:31.560 align:start position:0% subscribed and the emitting messages on various<00:11:28.330> topics<00:11:28.480> at<00:11:28.959> wise<00:11:29.260> so<00:11:30.420> appears<00:11:31.420> can 00:11:31.560 --> 00:11:31.570 align:start position:0% various topics at wise so appears can 00:11:31.570 --> 00:11:33.180 align:start position:0% various topics at wise so appears can participate<00:11:31.839> in<00:11:32.080> many<00:11:32.350> topics<00:11:32.830> either<00:11:33.100> a 00:11:33.180 --> 00:11:33.190 align:start position:0% participate in many topics either a 00:11:33.190 --> 00:11:35.579 align:start position:0% participate in many topics either a subscribers<00:11:33.940> publishers<00:11:34.510> applause<00:11:34.839> and 00:11:35.579 --> 00:11:35.589 align:start position:0% subscribers publishers applause and 00:11:35.589 --> 00:11:38.820 align:start position:0% subscribers publishers applause and peers<00:11:35.920> review<00:11:36.670> of<00:11:37.300> all<00:11:37.830> neighbor 00:11:38.820 --> 00:11:38.830 align:start position:0% peers review of all neighbor 00:11:38.830 --> 00:11:40.470 align:start position:0% peers review of all neighbor subscriptions<00:11:39.520> whether<00:11:39.820> they<00:11:40.029> overlap<00:11:40.450> with 00:11:40.470 --> 00:11:40.480 align:start position:0% subscriptions whether they overlap with 00:11:40.480 --> 00:11:43.350 align:start position:0% subscriptions whether they overlap with ours<00:11:40.899> or<00:11:41.200> not<00:11:41.470> so<00:11:41.800> if<00:11:42.490> also<00:11:42.850> subscribe<00:11:43.330> to 00:11:43.350 --> 00:11:43.360 align:start position:0% ours or not so if also subscribe to 00:11:43.360 --> 00:11:45.990 align:start position:0% ours or not so if also subscribe to Tommy<00:11:43.660> Kay<00:11:43.930> and<00:11:44.230> another<00:11:45.130> period<00:11:45.459> subscribe 00:11:45.990 --> 00:11:46.000 align:start position:0% Tommy Kay and another period subscribe 00:11:46.000 --> 00:11:47.639 align:start position:0% Tommy Kay and another period subscribe to<00:11:46.120> Tommy<00:11:46.300> C<00:11:46.570> but<00:11:46.779> I'm<00:11:46.870> not<00:11:46.990> interested<00:11:47.290> in<00:11:47.560> the 00:11:47.639 --> 00:11:47.649 align:start position:0% to Tommy C but I'm not interested in the 00:11:47.649 --> 00:11:49.680 align:start position:0% to Tommy C but I'm not interested in the see<00:11:47.830> I<00:11:48.010> was<00:11:48.370> still<00:11:48.640> note<00:11:48.910> that<00:11:49.149> the<00:11:49.270> other<00:11:49.390> peer 00:11:49.680 --> 00:11:49.690 align:start position:0% see I was still note that the other peer 00:11:49.690 --> 00:11:53.490 align:start position:0% see I was still note that the other peer subscribe<00:11:50.110> to<00:11:50.260> talkin<00:11:50.589> see<00:11:52.200> subscribers<00:11:53.200> is<00:11:53.440> a 00:11:53.490 --> 00:11:53.500 align:start position:0% subscribe to talkin see subscribers is a 00:11:53.500 --> 00:11:55.500 align:start position:0% subscribe to talkin see subscribers is a Santoni<00:11:54.010> engage<00:11:54.399> in<00:11:54.580> message<00:11:54.910> propagation 00:11:55.500 --> 00:11:55.510 align:start position:0% Santoni engage in message propagation 00:11:55.510 --> 00:11:58.710 align:start position:0% Santoni engage in message propagation and<00:11:55.839> gossip<00:11:56.410> or<00:11:56.589> personal<00:11:57.010> topics<00:11:57.400> so<00:11:57.720> abalone 00:11:58.710 --> 00:11:58.720 align:start position:0% and gossip or personal topics so abalone 00:11:58.720 --> 00:12:00.240 align:start position:0% and gossip or personal topics so abalone is<00:11:58.839> actually<00:11:59.170> participate<00:11:59.709> and<00:11:59.860> this<00:11:59.920> is<00:12:00.070> one 00:12:00.240 --> 00:12:00.250 align:start position:0% is actually participate and this is one 00:12:00.250 --> 00:12:02.130 align:start position:0% is actually participate and this is one of<00:12:00.279> the<00:12:00.459> key<00:12:00.640> properties<00:12:00.850> of<00:12:01.330> if<00:12:01.540> you<00:12:01.690> remember 00:12:02.130 --> 00:12:02.140 align:start position:0% of the key properties of if you remember 00:12:02.140 --> 00:12:05.400 align:start position:0% of the key properties of if you remember that<00:12:02.740> a<00:12:02.770> desirable<00:12:03.430> and<00:12:03.580> pub/sub<00:12:04.270> systems<00:12:04.720> and 00:12:05.400 --> 00:12:05.410 align:start position:0% that a desirable and pub/sub systems and 00:12:05.410 --> 00:12:07.380 align:start position:0% that a desirable and pub/sub systems and gears<00:12:05.770> revolves<00:12:06.220> up<00:12:06.339> systems<00:12:06.730> which<00:12:06.970> is<00:12:07.180> a 00:12:07.380 --> 00:12:07.390 align:start position:0% gears revolves up systems which is a 00:12:07.390 --> 00:12:09.600 align:start position:0% gears revolves up systems which is a only<00:12:08.020> those<00:12:08.260> peers<00:12:08.589> that<00:12:08.740> I<00:12:08.770> invested<00:12:09.339> in<00:12:09.459> and 00:12:09.600 --> 00:12:09.610 align:start position:0% only those peers that I invested in and 00:12:09.610 --> 00:12:12.850 align:start position:0% only those peers that I invested in and always<00:12:09.760> should<00:12:10.089> be<00:12:10.410> making<00:12:11.410> memory<00:12:11.740> too 00:12:12.850 --> 00:12:12.860 align:start position:0% always should be making memory too 00:12:12.860 --> 00:12:15.780 align:start position:0% always should be making memory too so<00:12:13.460> that<00:12:13.640> to<00:12:14.060> lhasa<00:12:14.350> self-satisfied 00:12:15.780 --> 00:12:15.790 align:start position:0% so that to lhasa self-satisfied 00:12:15.790 --> 00:12:18.310 align:start position:0% so that to lhasa self-satisfied so<00:12:16.790> we<00:12:17.060> have<00:12:17.210> a<00:12:17.240> concept<00:12:17.750> that's<00:12:18.080> called 00:12:18.310 --> 00:12:18.320 align:start position:0% so we have a concept that's called 00:12:18.320 --> 00:12:20.410 align:start position:0% so we have a concept that's called subscription<00:12:18.830> beginning<00:12:19.300> which<00:12:20.300> is 00:12:20.410 --> 00:12:20.420 align:start position:0% subscription beginning which is 00:12:20.420 --> 00:12:22.870 align:start position:0% subscription beginning which is basically<00:12:20.780> on<00:12:20.960> every<00:12:21.440> new<00:12:21.740> connection<00:12:22.250> beers 00:12:22.870 --> 00:12:22.880 align:start position:0% basically on every new connection beers 00:12:22.880 --> 00:12:24.670 align:start position:0% basically on every new connection beers will<00:12:23.240> exchange<00:12:23.690> the<00:12:24.110> topics<00:12:24.440> that<00:12:24.560> they 00:12:24.670 --> 00:12:24.680 align:start position:0% will exchange the topics that they 00:12:24.680 --> 00:12:29.140 align:start position:0% will exchange the topics that they subscribe<00:12:25.070> to<00:12:25.100> and<00:12:25.550> as<00:12:26.800> the<00:12:27.800> application<00:12:28.790> that 00:12:29.140 --> 00:12:29.150 align:start position:0% subscribe to and as the application that 00:12:29.150 --> 00:12:31.750 align:start position:0% subscribe to and as the application that is<00:12:29.240> using<00:12:29.540> the<00:12:29.630> livery<00:12:29.930> to<00:12:30.050> be<00:12:30.200> stack<00:12:30.500> joins<00:12:31.400> or 00:12:31.750 --> 00:12:31.760 align:start position:0% is using the livery to be stack joins or 00:12:31.760 --> 00:12:34.780 align:start position:0% is using the livery to be stack joins or leaves<00:12:32.090> topics<00:12:32.750> there<00:12:33.500> will<00:12:33.710> send<00:12:34.100> updates<00:12:34.310> to 00:12:34.780 --> 00:12:34.790 align:start position:0% leaves topics there will send updates to 00:12:34.790 --> 00:12:38.440 align:start position:0% leaves topics there will send updates to all<00:12:35.000> over<00:12:35.300> here<00:12:35.570> so<00:12:35.870> as<00:12:36.200> i<00:12:37.330> participating<00:12:38.330> as 00:12:38.440 --> 00:12:38.450 align:start position:0% all over here so as i participating as 00:12:38.450 --> 00:12:39.790 align:start position:0% all over here so as i participating as i've<00:12:38.570> become<00:12:38.840> a<00:12:38.900> participant<00:12:39.440> in<00:12:39.560> that<00:12:39.680> new 00:12:39.790 --> 00:12:39.800 align:start position:0% i've become a participant in that new 00:12:39.800 --> 00:12:40.930 align:start position:0% i've become a participant in that new topic 00:12:40.930 --> 00:12:40.940 align:start position:0% topic 00:12:40.940 --> 00:12:43.300 align:start position:0% topic i<00:12:40.970> will<00:12:41.540> send<00:12:41.960> an<00:12:42.080> update<00:12:42.380> to<00:12:42.560> to<00:12:42.920> all<00:12:43.100> of<00:12:43.220> the 00:12:43.300 --> 00:12:43.310 align:start position:0% i will send an update to to all of the 00:12:43.310 --> 00:12:45.430 align:start position:0% i will send an update to to all of the penis<00:12:43.640> now<00:12:44.420> we<00:12:44.780> don't<00:12:44.870> want<00:12:45.050> to<00:12:45.110> be<00:12:45.200> very 00:12:45.430 --> 00:12:45.440 align:start position:0% penis now we don't want to be very 00:12:45.440 --> 00:12:47.800 align:start position:0% penis now we don't want to be very chatty<00:12:45.800> so<00:12:46.460> we<00:12:47.090> have<00:12:47.240> introduced<00:12:47.630> the<00:12:47.780> concept 00:12:47.800 --> 00:12:47.810 align:start position:0% chatty so we have introduced the concept 00:12:47.810 --> 00:12:51.000 align:start position:0% chatty so we have introduced the concept of<00:12:48.320> piggybacking<00:12:48.830> right<00:12:49.520> so<00:12:49.730> this<00:12:49.820> means<00:12:50.060> that 00:12:51.000 --> 00:12:51.010 align:start position:0% of piggybacking right so this means that 00:12:51.010 --> 00:12:56.560 align:start position:0% of piggybacking right so this means that we<00:12:52.010> will<00:12:52.160> try<00:12:52.520> to<00:12:53.170> coalesce<00:12:55.570> Octane's 00:12:56.560 --> 00:12:56.570 align:start position:0% we will try to coalesce Octane's 00:12:56.570 --> 00:12:59.620 align:start position:0% we will try to coalesce Octane's metadata<00:12:57.350> updates<00:12:57.740> to<00:12:57.950> peers<00:12:58.250> on<00:12:59.000> top<00:12:59.390> of 00:12:59.620 --> 00:12:59.630 align:start position:0% metadata updates to peers on top of 00:12:59.630 --> 00:13:01.930 align:start position:0% metadata updates to peers on top of messages<00:13:00.530> that<00:13:00.770> we<00:13:00.950> anyway<00:13:01.370> need<00:13:01.580> to<00:13:01.730> send 00:13:01.930 --> 00:13:01.940 align:start position:0% messages that we anyway need to send 00:13:01.940 --> 00:13:04.420 align:start position:0% messages that we anyway need to send them<00:13:02.090> right<00:13:02.930> such<00:13:03.170> as<00:13:03.200> graphs<00:13:03.620> and<00:13:03.950> things<00:13:04.010> and 00:13:04.420 --> 00:13:04.430 align:start position:0% them right such as graphs and things and 00:13:04.430 --> 00:13:06.580 align:start position:0% them right such as graphs and things and so<00:13:04.580> on<00:13:04.610> as<00:13:04.850> we<00:13:05.030> can<00:13:05.690> that's<00:13:05.870> kind<00:13:06.110> of<00:13:06.200> beginning 00:13:06.580 --> 00:13:06.590 align:start position:0% so on as we can that's kind of beginning 00:13:06.590 --> 00:13:09.790 align:start position:0% so on as we can that's kind of beginning enables<00:13:07.460> us<00:13:07.580> to<00:13:07.870> create<00:13:08.870> an<00:13:09.170> about<00:13:09.320> metadata 00:13:09.790 --> 00:13:09.800 align:start position:0% enables us to create an about metadata 00:13:09.800 --> 00:13:13.030 align:start position:0% enables us to create an about metadata flows<00:13:10.220> and<00:13:10.490> to<00:13:10.990> and<00:13:11.990> to<00:13:12.140> do<00:13:12.260> also<00:13:12.410> pheromone 00:13:13.030 --> 00:13:13.040 align:start position:0% flows and to and to do also pheromone 00:13:13.040 --> 00:13:15.240 align:start position:0% flows and to and to do also pheromone topics<00:13:13.370> anything<00:13:13.670> which<00:13:13.790> is<00:13:13.910> possible<00:13:14.690> father 00:13:15.240 --> 00:13:15.250 align:start position:0% topics anything which is possible father 00:13:15.250 --> 00:13:20.170 align:start position:0% topics anything which is possible father explained<00:13:16.250> assessing<00:13:17.260> so<00:13:18.260> this<00:13:18.890> with<00:13:19.790> regards 00:13:20.170 --> 00:13:20.180 align:start position:0% explained assessing so this with regards 00:13:20.180 --> 00:13:22.000 align:start position:0% explained assessing so this with regards to<00:13:20.210> topic<00:13:20.570> membership<00:13:21.020> there<00:13:21.230> is<00:13:21.380> two<00:13:21.830> key 00:13:22.000 --> 00:13:22.010 align:start position:0% to topic membership there is two key 00:13:22.010 --> 00:13:24.730 align:start position:0% to topic membership there is two key concepts<00:13:22.430> to<00:13:22.640> to<00:13:23.210> to<00:13:23.900> understand<00:13:24.350> here<00:13:24.530> there 00:13:24.730 --> 00:13:24.740 align:start position:0% concepts to to to understand here there 00:13:24.740 --> 00:13:26.740 align:start position:0% concepts to to to understand here there is<00:13:24.830> the<00:13:24.920> concept<00:13:25.190> of<00:13:25.340> rotting<00:13:25.910> improved<00:13:26.480> i 00:13:26.740 --> 00:13:26.750 align:start position:0% is the concept of rotting improved i 00:13:26.750 --> 00:13:30.970 align:start position:0% is the concept of rotting improved i said<00:13:27.470> that<00:13:28.480> the<00:13:29.480> stable<00:13:30.140> mesh<00:13:30.320> is<00:13:30.530> actually<00:13:30.950> a 00:13:30.970 --> 00:13:30.980 align:start position:0% said that the stable mesh is actually a 00:13:30.980 --> 00:13:34.150 align:start position:0% said that the stable mesh is actually a separate<00:13:31.370> editing<00:13:31.760> mesh<00:13:32.200> and<00:13:33.200> the<00:13:33.710> and<00:13:33.950> these 00:13:34.150 --> 00:13:34.160 align:start position:0% separate editing mesh and the and these 00:13:34.160 --> 00:13:36.150 align:start position:0% separate editing mesh and the and these two<00:13:34.370> messages<00:13:34.760> are<00:13:34.940> key<00:13:35.120> to<00:13:35.330> really 00:13:36.150 --> 00:13:36.160 align:start position:0% two messages are key to really 00:13:36.160 --> 00:13:38.699 align:start position:0% two messages are key to really to<00:13:36.490> regulate<00:13:36.880> average<00:13:37.269> so<00:13:37.839> a<00:13:37.870> broath<00:13:38.259> control 00:13:38.699 --> 00:13:38.709 align:start position:0% to regulate average so a broath control 00:13:38.709 --> 00:13:40.819 align:start position:0% to regulate average so a broath control messages<00:13:39.190> brought<00:13:40.120> them<00:13:40.300> to<00:13:40.420> a<00:13:40.449> message 00:13:40.819 --> 00:13:40.829 align:start position:0% messages brought them to a message 00:13:40.829 --> 00:13:44.819 align:start position:0% messages brought them to a message proposes<00:13:41.829> a<00:13:41.860> two-way<00:13:42.959> full<00:13:43.959> message<00:13:44.170> stable 00:13:44.819 --> 00:13:44.829 align:start position:0% proposes a two-way full message stable 00:13:44.829 --> 00:13:45.720 align:start position:0% proposes a two-way full message stable link<00:13:45.040> will<00:13:45.190> appear 00:13:45.720 --> 00:13:45.730 align:start position:0% link will appear 00:13:45.730 --> 00:13:48.059 align:start position:0% link will appear so<00:13:45.880> it<00:13:46.089> basically<00:13:46.209> when<00:13:47.050> s1<00:13:47.199> appear<00:13:47.709> sends<00:13:48.009> a 00:13:48.059 --> 00:13:48.069 align:start position:0% so it basically when s1 appear sends a 00:13:48.069 --> 00:13:49.949 align:start position:0% so it basically when s1 appear sends a graph<00:13:48.279> to<00:13:48.459> another<00:13:48.759> here<00:13:49.089> is<00:13:49.240> basically 00:13:49.949 --> 00:13:49.959 align:start position:0% graph to another here is basically 00:13:49.959 --> 00:13:52.800 align:start position:0% graph to another here is basically telling<00:13:50.470> it<00:13:50.709> hey<00:13:50.920> I<00:13:51.250> want<00:13:51.819> to<00:13:51.850> be<00:13:52.000> part<00:13:52.269> of<00:13:52.540> your 00:13:52.800 --> 00:13:52.810 align:start position:0% telling it hey I want to be part of your 00:13:52.810 --> 00:13:55.740 align:start position:0% telling it hey I want to be part of your reciprocal<00:13:53.440> national<00:13:53.920> this<00:13:54.009> time<00:13:54.310> hey<00:13:55.300> this 00:13:55.740 --> 00:13:55.750 align:start position:0% reciprocal national this time hey this 00:13:55.750 --> 00:13:57.150 align:start position:0% reciprocal national this time hey this means<00:13:55.899> that<00:13:56.110> I'm<00:13:56.259> gonna<00:13:56.410> send<00:13:56.649> your<00:13:56.769> messages 00:13:57.150 --> 00:13:57.160 align:start position:0% means that I'm gonna send your messages 00:13:57.160 --> 00:13:59.009 align:start position:0% means that I'm gonna send your messages and<00:13:57.430> you<00:13:57.610> promised<00:13:58.000> to<00:13:58.149> send<00:13:58.329> messages<00:13:58.839> as 00:13:59.009 --> 00:13:59.019 align:start position:0% and you promised to send messages as 00:13:59.019 --> 00:14:01.290 align:start position:0% and you promised to send messages as well<00:13:59.199> right<00:14:00.009> now<00:14:00.550> the<00:14:00.610> other<00:14:00.850> peer<00:14:01.120> can 00:14:01.290 --> 00:14:01.300 align:start position:0% well right now the other peer can 00:14:01.300 --> 00:14:03.329 align:start position:0% well right now the other peer can protect<00:14:01.720> that<00:14:01.870> because<00:14:02.529> they<00:14:02.740> are<00:14:02.800> ready<00:14:03.069> to 00:14:03.329 --> 00:14:03.339 align:start position:0% protect that because they are ready to 00:14:03.339 --> 00:14:05.850 align:start position:0% protect that because they are ready to be<00:14:03.819> on<00:14:03.850> their<00:14:04.480> target<00:14:04.899> degree<00:14:05.170> right<00:14:05.470> and<00:14:05.680> if 00:14:05.850 --> 00:14:05.860 align:start position:0% be on their target degree right and if 00:14:05.860 --> 00:14:09.030 align:start position:0% be on their target degree right and if they're<00:14:06.009> rejected<00:14:06.839> they<00:14:07.839> send<00:14:08.319> McAfee 00:14:09.030 --> 00:14:09.040 align:start position:0% they're rejected they send McAfee 00:14:09.040 --> 00:14:13.019 align:start position:0% they're rejected they send McAfee however<00:14:09.660> the<00:14:10.660> other<00:14:10.870> peer<00:14:11.110> knows<00:14:11.519> that<00:14:12.519> I'm 00:14:13.019 --> 00:14:13.029 align:start position:0% however the other peer knows that I'm 00:14:13.029 --> 00:14:14.939 align:start position:0% however the other peer knows that I'm interested<00:14:13.569> in<00:14:13.690> that<00:14:13.839> topic<00:14:14.019> right<00:14:14.440> because 00:14:14.939 --> 00:14:14.949 align:start position:0% interested in that topic right because 00:14:14.949 --> 00:14:16.949 align:start position:0% interested in that topic right because I've<00:14:15.250> weakened<00:14:16.120> a<00:14:16.209> subscription<00:14:16.779> to<00:14:16.810> that 00:14:16.949 --> 00:14:16.959 align:start position:0% I've weakened a subscription to that 00:14:16.959 --> 00:14:17.610 align:start position:0% I've weakened a subscription to that topic 00:14:17.610 --> 00:14:17.620 align:start position:0% topic 00:14:17.620 --> 00:14:19.590 align:start position:0% topic therefore<00:14:18.220> their<00:14:18.430> even<00:14:18.850> though<00:14:19.000> I'm<00:14:19.120> not<00:14:19.329> part 00:14:19.590 --> 00:14:19.600 align:start position:0% therefore their even though I'm not part 00:14:19.600 --> 00:14:21.629 align:start position:0% therefore their even though I'm not part of<00:14:19.690> this<00:14:19.839> table<00:14:20.079> -<00:14:20.380> that<00:14:21.160> will<00:14:21.279> send<00:14:21.519> me 00:14:21.629 --> 00:14:21.639 align:start position:0% of this table - that will send me 00:14:21.639 --> 00:14:24.870 align:start position:0% of this table - that will send me metadata<00:14:22.149> right<00:14:22.930> so<00:14:23.680> this<00:14:23.829> is<00:14:23.889> where<00:14:24.190> the<00:14:24.699> yes 00:14:24.870 --> 00:14:24.880 align:start position:0% metadata right so this is where the yes 00:14:24.880 --> 00:14:27.509 align:start position:0% metadata right so this is where the yes these<00:14:25.480> two<00:14:25.720> network<00:14:26.350> started<00:14:26.829> making<00:14:27.250> sense 00:14:27.509 --> 00:14:27.519 align:start position:0% these two network started making sense 00:14:27.519 --> 00:14:29.460 align:start position:0% these two network started making sense right<00:14:27.759> now 00:14:29.460 --> 00:14:29.470 align:start position:0% right now 00:14:29.470 --> 00:14:31.829 align:start position:0% right now a<00:14:30.069> prune<00:14:30.459> control<00:14:30.819> message<00:14:31.120> dissolves<00:14:31.750> a 00:14:31.829 --> 00:14:31.839 align:start position:0% a prune control message dissolves a 00:14:31.839 --> 00:14:33.930 align:start position:0% a prune control message dissolves a two-way<00:14:32.139> message<00:14:32.500> a<00:14:32.769> two-way<00:14:33.160> stable<00:14:33.610> stable 00:14:33.930 --> 00:14:33.940 align:start position:0% two-way message a two-way stable stable 00:14:33.940 --> 00:14:36.420 align:start position:0% two-way message a two-way stable stable mesh<00:14:34.240> stable<00:14:34.930> between<00:14:35.500> two<00:14:35.649> peers<00:14:35.949> and<00:14:36.220> this 00:14:36.420 --> 00:14:36.430 align:start position:0% mesh stable between two peers and this 00:14:36.430 --> 00:14:39.540 align:start position:0% mesh stable between two peers and this could<00:14:36.579> be<00:14:37.019> in<00:14:38.019> this<00:14:38.440> can<00:14:38.589> be<00:14:38.709> sentence<00:14:39.130> one<00:14:39.399> to 00:14:39.540 --> 00:14:39.550 align:start position:0% could be in this can be sentence one to 00:14:39.550 --> 00:14:41.280 align:start position:0% could be in this can be sentence one to the<00:14:39.730> response<00:14:40.209> or<00:14:40.360> rather<00:14:40.630> we<00:14:40.870> want<00:14:40.990> to<00:14:41.110> reject 00:14:41.280 --> 00:14:41.290 align:start position:0% the response or rather we want to reject 00:14:41.290 --> 00:14:47.380 align:start position:0% the response or rather we want to reject or<00:14:42.420> if<00:14:43.420> I'm<00:14:43.750> done<00:14:43.990> regulating<00:14:44.620> my<00:14:44.769> my<00:14:45.130> degrees 00:14:47.380 --> 00:14:47.390 align:start position:0% or if I'm done regulating my my degrees 00:14:47.390 --> 00:14:50.079 align:start position:0% or if I'm done regulating my my degrees now<00:14:47.930> one<00:14:48.560> key<00:14:48.709> another<00:14:49.040> key<00:14:49.220> aspect<00:14:49.339> to<00:14:49.790> to 00:14:50.079 --> 00:14:50.089 align:start position:0% now one key another key aspect to to 00:14:50.089 --> 00:14:52.720 align:start position:0% now one key another key aspect to to understand<00:14:50.480> is<00:14:50.630> that<00:14:50.660> by<00:14:51.019> itself<00:14:51.890> the<00:14:52.459> steps 00:14:52.720 --> 00:14:52.730 align:start position:0% understand is that by itself the steps 00:14:52.730 --> 00:14:54.100 align:start position:0% understand is that by itself the steps up<00:14:52.880> right<00:14:53.089> now<00:14:53.240> does<00:14:53.510> not<00:14:53.540> include<00:14:53.930> a 00:14:54.100 --> 00:14:54.110 align:start position:0% up right now does not include a 00:14:54.110 --> 00:14:56.500 align:start position:0% up right now does not include a mechanism<00:14:54.470> for<00:14:54.620> you<00:14:54.950> this<00:14:55.100> country<00:14:55.430> right<00:14:55.820> so 00:14:56.500 --> 00:14:56.510 align:start position:0% mechanism for you this country right so 00:14:56.510 --> 00:14:59.170 align:start position:0% mechanism for you this country right so if<00:14:57.079> we<00:14:57.470> want<00:14:57.709> to<00:14:57.860> whenever<00:14:58.579> we<00:14:58.880> want<00:14:59.120> to 00:14:59.170 --> 00:14:59.180 align:start position:0% if we want to whenever we want to 00:14:59.180 --> 00:15:00.940 align:start position:0% if we want to whenever we want to subscribe<00:14:59.360> to<00:14:59.630> a<00:14:59.750> topic<00:15:00.110> we<00:15:00.260> need<00:15:00.290> to<00:15:00.560> find<00:15:00.769> a 00:15:00.940 --> 00:15:00.950 align:start position:0% subscribe to a topic we need to find a 00:15:00.950 --> 00:15:02.680 align:start position:0% subscribe to a topic we need to find a set<00:15:01.130> of<00:15:01.160> peers<00:15:01.519> that<00:15:01.610> have<00:15:01.850> already<00:15:02.029> subscribe 00:15:02.680 --> 00:15:02.690 align:start position:0% set of peers that have already subscribe 00:15:02.690 --> 00:15:04.389 align:start position:0% set of peers that have already subscribe to<00:15:02.810> that<00:15:02.930> time<00:15:03.140> and<00:15:03.440> this<00:15:04.130> and<00:15:04.339> the 00:15:04.389 --> 00:15:04.399 align:start position:0% to that time and this and the 00:15:04.399 --> 00:15:06.370 align:start position:0% to that time and this and the specification<00:15:05.029> is<00:15:05.120> called<00:15:05.329> ambient<00:15:05.870> appear 00:15:06.370 --> 00:15:06.380 align:start position:0% specification is called ambient appear 00:15:06.380 --> 00:15:08.699 align:start position:0% specification is called ambient appear in<00:15:06.470> this<00:15:06.560> country<00:15:06.920> right<00:15:07.100> we<00:15:07.610> rely<00:15:08.120> on 00:15:08.699 --> 00:15:08.709 align:start position:0% in this country right we rely on 00:15:08.709 --> 00:15:10.720 align:start position:0% in this country right we rely on computers<00:15:09.709> every<00:15:09.950> mechanism<00:15:10.490> which<00:15:10.700> is 00:15:10.720 --> 00:15:10.730 align:start position:0% computers every mechanism which is 00:15:10.730 --> 00:15:13.720 align:start position:0% computers every mechanism which is present<00:15:11.269> in<00:15:11.450> the<00:15:11.570> audience<00:15:11.660> right<00:15:12.579> this<00:15:13.579> is 00:15:13.720 --> 00:15:13.730 align:start position:0% present in the audience right this is 00:15:13.730 --> 00:15:16.600 align:start position:0% present in the audience right this is gonna<00:15:13.850> change<00:15:14.089> as<00:15:14.750> we<00:15:14.990> go<00:15:15.110> forward<00:15:15.350> where<00:15:16.070> the 00:15:16.600 --> 00:15:16.610 align:start position:0% gonna change as we go forward where the 00:15:16.610 --> 00:15:19.480 align:start position:0% gonna change as we go forward where the start<00:15:16.850> be<00:15:16.970> OPR<00:15:17.329> to<00:15:18.110> add<00:15:18.410> active<00:15:19.070> appeared<00:15:19.370> in 00:15:19.480 --> 00:15:19.490 align:start position:0% start be OPR to add active appeared in 00:15:19.490 --> 00:15:21.670 align:start position:0% start be OPR to add active appeared in Discovery<00:15:19.910> so<00:15:20.089> that<00:15:20.240> whatever<00:15:20.420> you<00:15:21.230> the 00:15:21.670 --> 00:15:21.680 align:start position:0% Discovery so that whatever you the 00:15:21.680 --> 00:15:23.829 align:start position:0% Discovery so that whatever you the application<00:15:22.070> subscribes<00:15:22.760> through<00:15:23.000> a<00:15:23.269> topic 00:15:23.829 --> 00:15:23.839 align:start position:0% application subscribes through a topic 00:15:23.839 --> 00:15:26.829 align:start position:0% application subscribes through a topic there<00:15:24.709> will<00:15:24.860> be<00:15:24.890> a<00:15:25.120> pops<00:15:26.120> up<00:15:26.269> will<00:15:26.390> actually<00:15:26.690> to 00:15:26.829 --> 00:15:26.839 align:start position:0% there will be a pops up will actually to 00:15:26.839 --> 00:15:28.960 align:start position:0% there will be a pops up will actually to become<00:15:27.079> of<00:15:27.769> peers<00:15:28.070> and<00:15:28.130> that<00:15:28.339> topic<00:15:28.550> for<00:15:28.820> them 00:15:28.960 --> 00:15:28.970 align:start position:0% become of peers and that topic for them 00:15:28.970 --> 00:15:31.329 align:start position:0% become of peers and that topic for them and<00:15:29.750> for<00:15:29.959> the<00:15:30.050> application<00:15:30.560> and<00:15:30.860> we<00:15:31.220> also 00:15:31.329 --> 00:15:31.339 align:start position:0% and for the application and we also 00:15:31.339 --> 00:15:32.740 align:start position:0% and for the application and we also found<00:15:31.579> an<00:15:31.760> introducing<00:15:32.269> something<00:15:32.450> that<00:15:32.660> we 00:15:32.740 --> 00:15:32.750 align:start position:0% found an introducing something that we 00:15:32.750 --> 00:15:35.259 align:start position:0% found an introducing something that we call<00:15:32.959> on<00:15:33.230> connectors<00:15:33.680> have<00:15:34.060> various<00:15:35.060> terms 00:15:35.259 --> 00:15:35.269 align:start position:0% call on connectors have various terms 00:15:35.269 --> 00:15:38.620 align:start position:0% call on connectors have various terms let's<00:15:36.170> talk<00:15:36.260> about<00:15:36.350> message<00:15:36.769> flow<00:15:37.329> when<00:15:38.329> a 00:15:38.620 --> 00:15:38.630 align:start position:0% let's talk about message flow when a 00:15:38.630 --> 00:15:41.680 align:start position:0% let's talk about message flow when a peer<00:15:39.560> wants<00:15:40.130> to<00:15:40.220> send<00:15:40.399> a<00:15:40.519> message<00:15:40.850> as<00:15:41.630> a 00:15:41.680 --> 00:15:41.690 align:start position:0% peer wants to send a message as a 00:15:41.690 --> 00:15:43.630 align:start position:0% peer wants to send a message as a message<00:15:42.140> source<00:15:42.320> they<00:15:43.040> just<00:15:43.279> push<00:15:43.490> the 00:15:43.630 --> 00:15:43.640 align:start position:0% message source they just push the 00:15:43.640 --> 00:15:46.210 align:start position:0% message source they just push the message<00:15:43.970> to<00:15:44.209> a<00:15:44.240> walls<00:15:44.510> table<00:15:44.899> to<00:15:45.350> 12<00:15:45.860> peers<00:15:46.070> in 00:15:46.210 --> 00:15:46.220 align:start position:0% message to a walls table to 12 peers in 00:15:46.220 --> 00:15:48.009 align:start position:0% message to a walls table to 12 peers in the<00:15:46.310> rationalization<00:15:47.089> area<00:15:47.600> right 00:15:48.009 --> 00:15:48.019 align:start position:0% the rationalization area right 00:15:48.019 --> 00:15:51.759 align:start position:0% the rationalization area right superstone<00:15:49.000> now<00:15:50.000> peers<00:15:50.810> that<00:15:51.260> received<00:15:51.620> that 00:15:51.759 --> 00:15:51.769 align:start position:0% superstone now peers that received that 00:15:51.769 --> 00:15:53.769 align:start position:0% superstone now peers that received that message<00:15:51.980> are<00:15:52.399> actually<00:15:52.850> message<00:15:53.149> from<00:15:53.300> so 00:15:53.769 --> 00:15:53.779 align:start position:0% message are actually message from so 00:15:53.779 --> 00:15:56.470 align:start position:0% message are actually message from so whenever<00:15:54.440> they<00:15:55.070> received<00:15:55.430> that<00:15:55.490> message<00:15:55.790> that 00:15:56.470 --> 00:15:56.480 align:start position:0% whenever they received that message that 00:15:56.480 --> 00:15:59.170 align:start position:0% whenever they received that message that will<00:15:56.660> forward<00:15:57.110> that<00:15:57.199> message<00:15:57.740> to<00:15:58.370> all<00:15:58.670> other 00:15:59.170 --> 00:15:59.180 align:start position:0% will forward that message to all other 00:15:59.180 --> 00:16:01.240 align:start position:0% will forward that message to all other peers<00:15:59.570> that<00:15:59.660> are<00:15:59.839> part<00:16:00.350> of<00:16:00.470> that<00:16:00.529> much<00:16:00.860> of<00:16:01.160> that 00:16:01.240 --> 00:16:01.250 align:start position:0% peers that are part of that much of that 00:16:01.250 --> 00:16:03.880 align:start position:0% peers that are part of that much of that of<00:16:01.670> that<00:16:01.850> view<00:16:02.029> of<00:16:02.089> the<00:16:02.300> network<00:16:02.480> right<00:16:02.870> and<00:16:03.230> we 00:16:03.880 --> 00:16:03.890 align:start position:0% of that view of the network right and we 00:16:03.890 --> 00:16:05.500 align:start position:0% of that view of the network right and we follow<00:16:04.160> here<00:16:04.459> is<00:16:04.579> to<00:16:04.730> interpret<00:16:04.910> silence 00:16:05.500 --> 00:16:05.510 align:start position:0% follow here is to interpret silence 00:16:05.510 --> 00:16:06.610 align:start position:0% follow here is to interpret silence because<00:16:05.779> we<00:16:05.899> don't<00:16:06.110> want<00:16:06.230> to<00:16:06.260> send<00:16:06.500> the 00:16:06.610 --> 00:16:06.620 align:start position:0% because we don't want to send the 00:16:06.620 --> 00:16:11.299 align:start position:0% because we don't want to send the message<00:16:06.649> back<00:16:07.070> and<00:16:07.100> forward<00:16:07.579> back 00:16:11.299 --> 00:16:11.309 align:start position:0% 00:16:11.309 --> 00:16:13.459 align:start position:0% now<00:16:11.909> we<00:16:11.969> can<00:16:12.239> also<00:16:12.389> publish<00:16:12.719> messages<00:16:13.349> on 00:16:13.459 --> 00:16:13.469 align:start position:0% now we can also publish messages on 00:16:13.469 --> 00:16:15.619 align:start position:0% now we can also publish messages on topics<00:16:13.829> that<00:16:13.859> we<00:16:14.039> don't<00:16:14.219> subscribe<00:16:14.399> to<00:16:14.629> right 00:16:15.619 --> 00:16:15.629 align:start position:0% topics that we don't subscribe to right 00:16:15.629 --> 00:16:17.749 align:start position:0% topics that we don't subscribe to right and<00:16:15.749> this<00:16:16.229> is<00:16:16.409> interesting<00:16:16.889> for<00:16:17.159> things<00:16:17.519> time 00:16:17.749 --> 00:16:17.759 align:start position:0% and this is interesting for things time 00:16:17.759 --> 00:16:19.129 align:start position:0% and this is interesting for things time for<00:16:17.939> example<00:16:18.059> at<00:16:18.419> Vienna<00:16:18.689> as<00:16:18.869> the 00:16:19.129 --> 00:16:19.139 align:start position:0% for example at Vienna as the 00:16:19.139 --> 00:16:21.229 align:start position:0% for example at Vienna as the interplanetary<00:16:19.769> naming<00:16:20.429> service<00:16:20.789> would<00:16:20.939> want 00:16:21.229 --> 00:16:21.239 align:start position:0% interplanetary naming service would want 00:16:21.239 --> 00:16:24.439 align:start position:0% interplanetary naming service would want to<00:16:21.329> send<00:16:21.479> updates<00:16:21.659> from<00:16:22.789> whatever<00:16:23.789> in<00:16:24.239> name 00:16:24.439 --> 00:16:24.449 align:start position:0% to send updates from whatever in name 00:16:24.449 --> 00:16:27.079 align:start position:0% to send updates from whatever in name they're<00:16:24.869> mapping<00:16:25.019> over<00:16:25.229> name<00:16:25.529> changes<00:16:26.159> to<00:16:26.399> a 00:16:27.079 --> 00:16:27.089 align:start position:0% they're mapping over name changes to a 00:16:27.089 --> 00:16:29.239 align:start position:0% they're mapping over name changes to a different<00:16:27.779> aperture<00:16:28.109> for<00:16:28.199> example<00:16:28.649> right<00:16:28.979> so 00:16:29.239 --> 00:16:29.249 align:start position:0% different aperture for example right so 00:16:29.249 --> 00:16:31.399 align:start position:0% different aperture for example right so you<00:16:29.849> don't<00:16:30.029> necessarily<00:16:30.149> the<00:16:30.659> peer<00:16:31.019> that's 00:16:31.399 --> 00:16:31.409 align:start position:0% you don't necessarily the peer that's 00:16:31.409 --> 00:16:35.059 align:start position:0% you don't necessarily the peer that's watching<00:16:32.119> for<00:16:33.119> example<00:16:33.449> the<00:16:33.509> DNS<00:16:33.959> server<00:16:34.169> DNS 00:16:35.059 --> 00:16:35.069 align:start position:0% watching for example the DNS server DNS 00:16:35.069 --> 00:16:37.189 align:start position:0% watching for example the DNS server DNS name<00:16:35.249> server<00:16:35.579> somewhere<00:16:35.789> and<00:16:36.269> then<00:16:36.629> noticing 00:16:37.189 --> 00:16:37.199 align:start position:0% name server somewhere and then noticing 00:16:37.199 --> 00:16:39.469 align:start position:0% name server somewhere and then noticing this<00:16:37.349> change<00:16:37.589> doesn't<00:16:38.339> message<00:16:38.849> simply<00:16:39.179> set 00:16:39.469 --> 00:16:39.479 align:start position:0% this change doesn't message simply set 00:16:39.479 --> 00:16:41.269 align:start position:0% this change doesn't message simply set the<00:16:39.569> necessary<00:16:39.689> need<00:16:40.199> want<00:16:40.649> to<00:16:40.799> be<00:16:40.919> subscribe 00:16:41.269 --> 00:16:41.279 align:start position:0% the necessary need want to be subscribe 00:16:41.279 --> 00:16:42.829 align:start position:0% the necessary need want to be subscribe to<00:16:41.399> these<00:16:41.519> comments<00:16:41.939> right<00:16:42.119> as<00:16:42.689> the 00:16:42.829 --> 00:16:42.839 align:start position:0% to these comments right as the 00:16:42.839 --> 00:16:44.179 align:start position:0% to these comments right as the possibility<00:16:43.469> of<00:16:43.679> sending<00:16:43.889> those<00:16:44.099> messages 00:16:44.179 --> 00:16:44.189 align:start position:0% possibility of sending those messages 00:16:44.189 --> 00:16:46.759 align:start position:0% possibility of sending those messages and<00:16:44.759> when<00:16:44.879> we<00:16:44.969> do<00:16:45.119> that<00:16:45.299> we<00:16:45.839> basically<00:16:46.049> already 00:16:46.759 --> 00:16:46.769 align:start position:0% and when we do that we basically already 00:16:46.769 --> 00:16:48.799 align:start position:0% and when we do that we basically already remember<00:16:47.429> that<00:16:47.639> we<00:16:47.729> keep<00:16:47.879> in<00:16:48.059> track<00:16:48.179> of<00:16:48.539> what 00:16:48.799 --> 00:16:48.809 align:start position:0% remember that we keep in track of what 00:16:48.809 --> 00:16:50.899 align:start position:0% remember that we keep in track of what appears<00:16:49.289> are<00:16:49.499> actually<00:16:49.799> subscribe<00:16:50.189> to<00:16:50.369> the 00:16:50.899 --> 00:16:50.909 align:start position:0% appears are actually subscribe to the 00:16:50.909 --> 00:16:53.329 align:start position:0% appears are actually subscribe to the network<00:16:51.209> we're<00:16:51.959> not<00:16:52.139> for<00:16:52.349> forming<00:16:52.949> stable 00:16:53.329 --> 00:16:53.339 align:start position:0% network we're not for forming stable 00:16:53.339 --> 00:16:54.979 align:start position:0% network we're not for forming stable messages<00:16:53.669> for<00:16:53.789> them<00:16:53.939> but<00:16:54.179> we<00:16:54.299> keep<00:16:54.449> in<00:16:54.629> trouble 00:16:54.979 --> 00:16:54.989 align:start position:0% messages for them but we keep in trouble 00:16:54.989 --> 00:16:57.679 align:start position:0% messages for them but we keep in trouble so<00:16:55.379> if<00:16:56.009> the<00:16:56.219> local<00:16:56.399> application<00:16:57.239> tries<00:16:57.509> to 00:16:57.679 --> 00:16:57.689 align:start position:0% so if the local application tries to 00:16:57.689 --> 00:16:59.329 align:start position:0% so if the local application tries to send<00:16:57.839> that<00:16:58.019> message<00:16:58.169> we<00:16:58.769> will<00:16:58.949> immediately 00:16:59.329 --> 00:16:59.339 align:start position:0% send that message we will immediately 00:16:59.339 --> 00:17:01.939 align:start position:0% send that message we will immediately form<00:16:59.909> what<00:17:00.119> we<00:17:00.239> call<00:17:00.449> the<00:17:00.539> final<00:17:00.779> group<00:17:01.079> from 00:17:01.939 --> 00:17:01.949 align:start position:0% form what we call the final group from 00:17:01.949 --> 00:17:03.229 align:start position:0% form what we call the final group from those<00:17:02.159> years<00:17:02.489> that<00:17:02.609> we<00:17:02.669> know<00:17:02.939> already 00:17:03.229 --> 00:17:03.239 align:start position:0% those years that we know already 00:17:03.239 --> 00:17:05.509 align:start position:0% those years that we know already subscribe<00:17:03.869> to<00:17:03.899> that<00:17:04.110> oh<00:17:04.169> right<00:17:04.829> and<00:17:05.039> this<00:17:05.399> is 00:17:05.509 --> 00:17:05.519 align:start position:0% subscribe to that oh right and this is 00:17:05.519 --> 00:17:07.759 align:start position:0% subscribe to that oh right and this is gonna<00:17:05.669> be<00:17:05.759> an<00:17:05.970> ephemeral<00:17:06.389> nation<00:17:06.720> so<00:17:07.049> once<00:17:07.620> we 00:17:07.759 --> 00:17:07.769 align:start position:0% gonna be an ephemeral nation so once we 00:17:07.769 --> 00:17:08.449 align:start position:0% gonna be an ephemeral nation so once we form<00:17:07.919> that<00:17:08.100> group 00:17:08.449 --> 00:17:08.459 align:start position:0% form that group 00:17:08.459 --> 00:17:10.309 align:start position:0% form that group we<00:17:08.669> push<00:17:08.879> out<00:17:09.000> the<00:17:09.120> message<00:17:09.449> those<00:17:09.750> peers<00:17:10.049> we 00:17:10.309 --> 00:17:10.319 align:start position:0% we push out the message those peers we 00:17:10.319 --> 00:17:12.649 align:start position:0% we push out the message those peers we know<00:17:10.589> are<00:17:11.100> already<00:17:11.459> part<00:17:12.000> of<00:17:12.149> the<00:17:12.269> mansion 00:17:12.649 --> 00:17:12.659 align:start position:0% know are already part of the mansion 00:17:12.659 --> 00:17:15.429 align:start position:0% know are already part of the mansion therefore<00:17:13.350> they<00:17:13.500> will<00:17:13.769> forward<00:17:14.189> that<00:17:14.370> message 00:17:15.429 --> 00:17:15.439 align:start position:0% therefore they will forward that message 00:17:15.439 --> 00:17:17.509 align:start position:0% therefore they will forward that message internally<00:17:16.439> because<00:17:16.829> the<00:17:17.100> message<00:17:17.369> has 00:17:17.509 --> 00:17:17.519 align:start position:0% internally because the message has 00:17:17.519 --> 00:17:19.369 align:start position:0% internally because the message has arrived<00:17:17.879> inside<00:17:18.449> the<00:17:18.629> mesh<00:17:18.779> for<00:17:18.929> the<00:17:18.990> topic 00:17:19.369 --> 00:17:19.379 align:start position:0% arrived inside the mesh for the topic 00:17:19.379 --> 00:17:24.889 align:start position:0% arrived inside the mesh for the topic and<00:17:20.329> after<00:17:21.329> two<00:17:21.480> minutes<00:17:21.629> we<00:17:22.429> just<00:17:23.429> dis 00:17:24.889 --> 00:17:24.899 align:start position:0% and after two minutes we just dis 00:17:24.899 --> 00:17:27.529 align:start position:0% and after two minutes we just dis it<00:17:25.409> was<00:17:25.529> just<00:17:25.740> an<00:17:25.860> informal<00:17:26.039> sense<00:17:26.459> so<00:17:26.759> we 00:17:27.529 --> 00:17:27.539 align:start position:0% it was just an informal sense so we 00:17:27.539 --> 00:17:28.940 align:start position:0% it was just an informal sense so we don't<00:17:27.689> want<00:17:27.809> to<00:17:27.869> keep<00:17:28.019> it<00:17:28.139> at<00:17:28.259> all<00:17:28.409> for<00:17:28.740> too 00:17:28.940 --> 00:17:28.950 align:start position:0% don't want to keep it at all for too 00:17:28.950 --> 00:17:30.289 align:start position:0% don't want to keep it at all for too long<00:17:29.129> because<00:17:29.399> that<00:17:29.639> would<00:17:29.759> be<00:17:29.879> everything<00:17:30.179> to 00:17:30.289 --> 00:17:30.299 align:start position:0% long because that would be everything to 00:17:30.299 --> 00:17:33.830 align:start position:0% long because that would be everything to stay<00:17:30.600> that<00:17:30.659> way<00:17:32.000> we<00:17:33.000> also<00:17:33.149> have<00:17:33.330> a<00:17:33.419> concept<00:17:33.690> of 00:17:33.830 --> 00:17:33.840 align:start position:0% stay that way we also have a concept of 00:17:33.840 --> 00:17:36.350 align:start position:0% stay that way we also have a concept of topic<00:17:34.169> validators<00:17:34.740> and<00:17:35.340> perception<00:17:36.059> nature 00:17:36.350 --> 00:17:36.360 align:start position:0% topic validators and perception nature 00:17:36.360 --> 00:17:38.869 align:start position:0% topic validators and perception nature is<00:17:36.509> so<00:17:37.309> we<00:17:38.309> can 00:17:38.869 --> 00:17:38.879 align:start position:0% is so we can 00:17:38.879 --> 00:17:41.060 align:start position:0% is so we can so<00:17:39.389> when<00:17:39.570> appear<00:17:39.960> when<00:17:40.200> an<00:17:40.320> application<00:17:40.649> sends 00:17:41.060 --> 00:17:41.070 align:start position:0% so when appear when an application sends 00:17:41.070 --> 00:17:43.580 align:start position:0% so when appear when an application sends a<00:17:41.129> message<00:17:41.460> sorry<00:17:42.360> the<00:17:42.960> application<00:17:43.409> can 00:17:43.580 --> 00:17:43.590 align:start position:0% a message sorry the application can 00:17:43.590 --> 00:17:46.190 align:start position:0% a message sorry the application can configure<00:17:44.009> can<00:17:44.460> attach<00:17:45.200> predicate 00:17:46.190 --> 00:17:46.200 align:start position:0% configure can attach predicate 00:17:46.200 --> 00:17:48.019 align:start position:0% configure can attach predicate validation<00:17:46.799> predicates<00:17:47.250> to<00:17:47.309> topics<00:17:47.730> right 00:17:48.019 --> 00:17:48.029 align:start position:0% validation predicates to topics right 00:17:48.029 --> 00:17:50.139 align:start position:0% validation predicates to topics right and<00:17:48.269> even<00:17:48.539> 2.0<00:17:48.990> for<00:17:49.139> example<00:17:49.470> is<00:17:49.559> using<00:17:49.860> this 00:17:50.139 --> 00:17:50.149 align:start position:0% and even 2.0 for example is using this 00:17:50.149 --> 00:17:52.409 align:start position:0% and even 2.0 for example is using this for<00:17:51.149> validating 00:17:52.409 --> 00:17:52.419 align:start position:0% for validating 00:17:52.419 --> 00:17:54.450 align:start position:0% for validating signatures<00:17:52.869> in<00:17:53.139> adults<00:17:54.100> that<00:17:54.190> are<00:17:54.279> getting 00:17:54.450 --> 00:17:54.460 align:start position:0% signatures in adults that are getting 00:17:54.460 --> 00:17:58.229 align:start position:0% signatures in adults that are getting propagated<00:17:54.759> inside<00:17:56.549> so<00:17:57.549> when<00:17:57.820> a<00:17:57.850> message<00:17:58.149> is 00:17:58.229 --> 00:17:58.239 align:start position:0% propagated inside so when a message is 00:17:58.239 --> 00:18:00.180 align:start position:0% propagated inside so when a message is publish<00:17:58.600> globally<00:17:59.230> or<00:17:59.470> before<00:17:59.799> boarding<00:18:00.129> a 00:18:00.180 --> 00:18:00.190 align:start position:0% publish globally or before boarding a 00:18:00.190 --> 00:18:02.340 align:start position:0% publish globally or before boarding a message<00:18:00.519> this<00:18:00.850> predicate<00:18:01.119> will<00:18:01.389> be<00:18:01.509> caught<00:18:01.720> if 00:18:02.340 --> 00:18:02.350 align:start position:0% message this predicate will be caught if 00:18:02.350 --> 00:18:03.930 align:start position:0% message this predicate will be caught if it<00:18:02.559> succeeds<00:18:02.950> then<00:18:03.249> the<00:18:03.340> message<00:18:03.669> will 00:18:03.930 --> 00:18:03.940 align:start position:0% it succeeds then the message will 00:18:03.940 --> 00:18:05.310 align:start position:0% it succeeds then the message will continue<00:18:04.509> dissemination 00:18:05.310 --> 00:18:05.320 align:start position:0% continue dissemination 00:18:05.320 --> 00:18:07.710 align:start position:0% continue dissemination otherwise<00:18:05.710> it<00:18:06.100> will<00:18:06.220> just<00:18:06.279> be<00:18:06.519> dropped<00:18:07.299> we 00:18:07.710 --> 00:18:07.720 align:start position:0% otherwise it will just be dropped we 00:18:07.720 --> 00:18:08.940 align:start position:0% otherwise it will just be dropped we have<00:18:07.869> the<00:18:07.989> concept<00:18:08.350> of<00:18:08.440> the<00:18:08.529> single<00:18:08.799> a 00:18:08.940 --> 00:18:08.950 align:start position:0% have the concept of the single a 00:18:08.950 --> 00:18:10.979 align:start position:0% have the concept of the single a synchronous<00:18:09.340> validators<00:18:09.909> for<00:18:10.720> a<00:18:10.749> heavy 00:18:10.979 --> 00:18:10.989 align:start position:0% synchronous validators for a heavy 00:18:10.989 --> 00:18:13.529 align:start position:0% synchronous validators for a heavy robotic<00:18:11.499> and<00:18:11.859> gossip<00:18:12.759> self<00:18:12.999> can<00:18:13.210> also<00:18:13.330> be 00:18:13.529 --> 00:18:13.539 align:start position:0% robotic and gossip self can also be 00:18:13.539 --> 00:18:15.950 align:start position:0% robotic and gossip self can also be configured<00:18:13.720> to<00:18:14.049> sign<00:18:14.350> our<00:18:14.769> messages<00:18:15.460> in<00:18:15.609> tune 00:18:15.950 --> 00:18:15.960 align:start position:0% configured to sign our messages in tune 00:18:15.960 --> 00:18:18.720 align:start position:0% configured to sign our messages in tune and<00:18:16.960> to<00:18:17.139> strictly<00:18:17.470> validate<00:18:18.159> having 00:18:18.720 --> 00:18:18.730 align:start position:0% and to strictly validate having 00:18:18.730 --> 00:18:21.960 align:start position:0% and to strictly validate having signatures<00:18:19.210> as<00:18:19.330> well<00:18:20.429> now<00:18:21.429> how<00:18:21.789> do<00:18:21.850> we 00:18:21.960 --> 00:18:21.970 align:start position:0% signatures as well now how do we 00:18:21.970 --> 00:18:26.369 align:start position:0% signatures as well now how do we regulate<00:18:22.659> the<00:18:23.499> mesh<00:18:23.710> this<00:18:24.700> a<00:18:25.200> concept<00:18:26.200> called 00:18:26.369 --> 00:18:26.379 align:start position:0% regulate the mesh this a concept called 00:18:26.379 --> 00:18:29.099 align:start position:0% regulate the mesh this a concept called heavy<00:18:26.679> quote<00:18:27.489> by<00:18:27.669> default<00:18:28.029> happens<00:18:28.389> every 00:18:29.099 --> 00:18:29.109 align:start position:0% heavy quote by default happens every 00:18:29.109 --> 00:18:30.930 align:start position:0% heavy quote by default happens every second<00:18:29.379> business<00:18:29.590> very<00:18:30.070> popular<00:18:30.429> concept<00:18:30.700> and 00:18:30.930 --> 00:18:30.940 align:start position:0% second business very popular concept and 00:18:30.940 --> 00:18:33.299 align:start position:0% second business very popular concept and distributed<00:18:31.450> systems<00:18:31.830> and<00:18:32.830> this<00:18:32.980> basically 00:18:33.299 --> 00:18:33.309 align:start position:0% distributed systems and this basically 00:18:33.309 --> 00:18:35.220 align:start position:0% distributed systems and this basically performs<00:18:33.820> mesh<00:18:34.179> and<00:18:34.480> gossip<00:18:34.779> meats<00:18:34.960> and<00:18:35.080> its 00:18:35.220 --> 00:18:35.230 align:start position:0% performs mesh and gossip meats and its 00:18:35.230 --> 00:18:36.989 align:start position:0% performs mesh and gossip meats and its functions<00:18:35.590> right<00:18:36.070> there's<00:18:36.609> three<00:18:36.759> things 00:18:36.989 --> 00:18:36.999 align:start position:0% functions right there's three things 00:18:36.999 --> 00:18:39.869 align:start position:0% functions right there's three things that<00:18:37.119> happen<00:18:37.480> we<00:18:38.019> regulate<00:18:38.529> the<00:18:39.279> mesh<00:18:39.460> degree 00:18:39.869 --> 00:18:39.879 align:start position:0% that happen we regulate the mesh degree 00:18:39.879 --> 00:18:42.060 align:start position:0% that happen we regulate the mesh degree for<00:18:40.119> every<00:18:40.299> topic<00:18:40.480> we<00:18:40.960> met<00:18:41.259> gossip<00:18:41.710> and<00:18:41.950> we 00:18:42.060 --> 00:18:42.070 align:start position:0% for every topic we met gossip and we 00:18:42.070 --> 00:18:44.580 align:start position:0% for every topic we met gossip and we slide<00:18:42.309> the<00:18:42.429> message<00:18:42.730> functions<00:18:43.320> so<00:18:44.320> this<00:18:44.470> is 00:18:44.580 --> 00:18:44.590 align:start position:0% slide the message functions so this is 00:18:44.590 --> 00:18:46.470 align:start position:0% slide the message functions so this is kind<00:18:44.980> of<00:18:45.039> like<00:18:45.129> how<00:18:45.369> degree<00:18:45.940> recognition 00:18:46.470 --> 00:18:46.480 align:start position:0% kind of like how degree recognition 00:18:46.480 --> 00:18:48.810 align:start position:0% kind of like how degree recognition works<00:18:46.629> as<00:18:46.929> already<00:18:47.440> explained<00:18:47.950> it<00:18:48.129> if<00:18:48.549> we're 00:18:48.810 --> 00:18:48.820 align:start position:0% works as already explained it if we're 00:18:48.820 --> 00:18:52.109 align:start position:0% works as already explained it if we're below<00:18:49.299> a<00:18:50.019> certain<00:18:50.739> threshold<00:18:51.009> we<00:18:51.669> will<00:18:51.820> try<00:18:52.090> to 00:18:52.109 --> 00:18:52.119 align:start position:0% below a certain threshold we will try to 00:18:52.119 --> 00:18:55.049 align:start position:0% below a certain threshold we will try to add<00:18:52.570> peers<00:18:53.230> to<00:18:53.919> the<00:18:54.070> mesh<00:18:54.340> for<00:18:54.759> that<00:18:54.909> matter 00:18:55.049 --> 00:18:55.059 align:start position:0% add peers to the mesh for that matter 00:18:55.059 --> 00:18:57.599 align:start position:0% add peers to the mesh for that matter forum<00:18:55.629> so<00:18:55.960> for<00:18:56.590> that<00:18:56.679> particular<00:18:56.950> topic<00:18:57.249> if 00:18:57.599 --> 00:18:57.609 align:start position:0% forum so for that particular topic if 00:18:57.609 --> 00:19:00.060 align:start position:0% forum so for that particular topic if we're<00:18:57.789> above<00:18:58.179> a<00:18:58.539> certain<00:18:58.989> threshold<00:18:59.169> then<00:18:59.710> we 00:19:00.060 --> 00:19:00.070 align:start position:0% we're above a certain threshold then we 00:19:00.070 --> 00:19:02.970 align:start position:0% we're above a certain threshold then we will<00:19:00.340> try<00:19:00.519> what<00:19:00.879> we'll<00:19:01.029> cream<00:19:01.679> here<00:19:02.679> is<00:19:02.799> from 00:19:02.970 --> 00:19:02.980 align:start position:0% will try what we'll cream here is from 00:19:02.980 --> 00:19:06.570 align:start position:0% will try what we'll cream here is from that<00:19:03.159> topic<00:19:03.809> to<00:19:04.809> try<00:19:05.019> to<00:19:05.080> keep<00:19:05.379> the<00:19:05.980> degree<00:19:06.340> at 00:19:06.570 --> 00:19:06.580 align:start position:0% that topic to try to keep the degree at 00:19:06.580 --> 00:19:10.739 align:start position:0% that topic to try to keep the degree at a<00:19:06.999> stable<00:19:07.570> constant<00:19:09.059> to<00:19:10.059> be<00:19:10.149> able<00:19:10.269> to<00:19:10.480> do<00:19:10.570> this 00:19:10.739 --> 00:19:10.749 align:start position:0% a stable constant to be able to do this 00:19:10.749 --> 00:19:12.629 align:start position:0% a stable constant to be able to do this we<00:19:10.989> keep<00:19:11.169> a<00:19:11.289> bunch<00:19:11.470> of<00:19:11.590> local<00:19:11.950> states<00:19:12.220> and 00:19:12.629 --> 00:19:12.639 align:start position:0% we keep a bunch of local states and 00:19:12.639 --> 00:19:14.669 align:start position:0% we keep a bunch of local states and topics<00:19:12.909> that<00:19:13.059> I<00:19:13.090> subscribe<00:19:13.570> to<00:19:13.629> topics<00:19:14.529> that<00:19:14.649> I 00:19:14.669 --> 00:19:14.679 align:start position:0% topics that I subscribe to topics that I 00:19:14.679 --> 00:19:16.680 align:start position:0% topics that I subscribe to topics that I recently<00:19:14.950> sent<00:19:15.369> a<00:19:15.519> message<00:19:15.850> to<00:19:15.879> this<00:19:16.419> is<00:19:16.570> the 00:19:16.680 --> 00:19:16.690 align:start position:0% recently sent a message to this is the 00:19:16.690 --> 00:19:18.690 align:start position:0% recently sent a message to this is the fountain<00:19:17.080> rumors<00:19:17.499> appears<00:19:18.399> that<00:19:18.549> we 00:19:18.690 --> 00:19:18.700 align:start position:0% fountain rumors appears that we 00:19:18.700 --> 00:19:21.479 align:start position:0% fountain rumors appears that we currently<00:19:18.879> connected<00:19:19.480> to<00:19:19.649> and<00:19:20.649> what<00:19:21.190> kind<00:19:21.399> of 00:19:21.479 --> 00:19:21.489 align:start position:0% currently connected to and what kind of 00:19:21.489 --> 00:19:23.020 align:start position:0% currently connected to and what kind of links<00:19:21.759> we<00:19:21.879> maintain 00:19:23.020 --> 00:19:23.030 align:start position:0% links we maintain 00:19:23.030 --> 00:19:25.400 align:start position:0% links we maintain fluorinated<00:19:24.030> message<00:19:24.300> detailing<00:19:24.810> or<00:19:25.020> a<00:19:25.200> fan 00:19:25.400 --> 00:19:25.410 align:start position:0% fluorinated message detailing or a fan 00:19:25.410 --> 00:19:27.710 align:start position:0% fluorinated message detailing or a fan of<00:19:25.560> peers<00:19:25.860> and<00:19:26.220> what<00:19:27.090> messages<00:19:27.450> were<00:19:27.630> you 00:19:27.710 --> 00:19:27.720 align:start position:0% of peers and what messages were you 00:19:27.720 --> 00:19:29.990 align:start position:0% of peers and what messages were you recently<00:19:27.990> seen<00:19:28.410> why<00:19:28.980> is<00:19:29.040> this<00:19:29.310> important 00:19:29.990 --> 00:19:30.000 align:start position:0% recently seen why is this important 00:19:30.000 --> 00:19:33.080 align:start position:0% recently seen why is this important this<00:19:30.540> is<00:19:30.690> this<00:19:30.810> last<00:19:31.050> bit<00:19:31.550> because<00:19:32.550> we<00:19:32.820> send 00:19:33.080 --> 00:19:33.090 align:start position:0% this is this last bit because we send 00:19:33.090 --> 00:19:35.510 align:start position:0% this is this last bit because we send both<00:19:33.690> so<00:19:34.440> this<00:19:34.590> is<00:19:34.740> part<00:19:35.100> of<00:19:35.130> the<00:19:35.220> gossip 00:19:35.510 --> 00:19:35.520 align:start position:0% both so this is part of the gossip 00:19:35.520 --> 00:19:38.000 align:start position:0% both so this is part of the gossip content<00:19:35.880> so<00:19:36.060> for<00:19:36.240> every<00:19:36.570> single<00:19:36.600> year<00:19:37.020> that<00:19:37.800> we 00:19:38.000 --> 00:19:38.010 align:start position:0% content so for every single year that we 00:19:38.010 --> 00:19:39.550 align:start position:0% content so for every single year that we know<00:19:38.190> is<00:19:38.310> interested<00:19:38.760> in<00:19:38.850> a<00:19:38.970> particular<00:19:39.090> topic 00:19:39.550 --> 00:19:39.560 align:start position:0% know is interested in a particular topic 00:19:39.560 --> 00:19:44.060 align:start position:0% know is interested in a particular topic that<00:19:40.560> is<00:19:41.490> not<00:19:41.760> part<00:19:42.090> of<00:19:42.300> our<00:19:42.510> stable<00:19:43.080> mesh<00:19:43.260> we 00:19:44.060 --> 00:19:44.070 align:start position:0% that is not part of our stable mesh we 00:19:44.070 --> 00:19:46.250 align:start position:0% that is not part of our stable mesh we will<00:19:44.310> collaborate<00:19:44.640> in<00:19:45.060> the<00:19:45.150> network<00:19:45.570> bye<00:19:45.810> bye 00:19:46.250 --> 00:19:46.260 align:start position:0% will collaborate in the network bye bye 00:19:46.260 --> 00:19:48.770 align:start position:0% will collaborate in the network bye bye gossiping<00:19:46.830> gossiping<00:19:47.730> what<00:19:48.120> messages<00:19:48.540> we've 00:19:48.770 --> 00:19:48.780 align:start position:0% gossiping gossiping what messages we've 00:19:48.780 --> 00:19:51.080 align:start position:0% gossiping gossiping what messages we've seen<00:19:49.200> in<00:19:49.500> a<00:19:49.650> particular<00:19:49.950> time<00:19:50.250> so<00:19:50.550> we<00:19:50.700> don't 00:19:51.080 --> 00:19:51.090 align:start position:0% seen in a particular time so we don't 00:19:51.090 --> 00:19:54.050 align:start position:0% seen in a particular time so we don't send<00:19:51.750> the<00:19:51.930> message<00:19:52.320> to<00:19:52.530> them<00:19:52.680> but<00:19:53.550> what<00:19:53.730> we<00:19:53.910> do 00:19:54.050 --> 00:19:54.060 align:start position:0% send the message to them but what we do 00:19:54.060 --> 00:19:56.660 align:start position:0% send the message to them but what we do is<00:19:54.090> with<00:19:54.630> every<00:19:55.020> tick<00:19:55.260> and<00:19:55.530> every<00:19:56.250> heartbeat 00:19:56.660 --> 00:19:56.670 align:start position:0% is with every tick and every heartbeat 00:19:56.670 --> 00:20:00.860 align:start position:0% is with every tick and every heartbeat we<00:19:57.540> will<00:19:58.580> when<00:19:59.580> the<00:19:59.700> message<00:20:00.030> we<00:20:00.480> keep<00:20:00.660> in<00:20:00.780> your 00:20:00.860 --> 00:20:00.870 align:start position:0% we will when the message we keep in your 00:20:00.870 --> 00:20:02.630 align:start position:0% we will when the message we keep in your message<00:20:01.200> cache<00:20:01.470> and<00:20:01.800> we<00:20:01.830> keep<00:20:02.070> it<00:20:02.250> under<00:20:02.400> like 00:20:02.630 --> 00:20:02.640 align:start position:0% message cache and we keep it under like 00:20:02.640 --> 00:20:04.340 align:start position:0% message cache and we keep it under like a<00:20:02.670> sliding<00:20:03.210> window<00:20:03.240> our<00:20:03.690> messages<00:20:04.080> that<00:20:04.230> we've 00:20:04.340 --> 00:20:04.350 align:start position:0% a sliding window our messages that we've 00:20:04.350 --> 00:20:06.530 align:start position:0% a sliding window our messages that we've seen<00:20:04.590> in<00:20:04.920> the<00:20:05.010> last<00:20:05.040> 30<00:20:05.880> seconds<00:20:06.330> 2<00:20:06.510> minutes 00:20:06.530 --> 00:20:06.540 align:start position:0% seen in the last 30 seconds 2 minutes 00:20:06.540 --> 00:20:09.440 align:start position:0% seen in the last 30 seconds 2 minutes this<00:20:07.020> is<00:20:07.080> configurable<00:20:07.790> we<00:20:08.790> will<00:20:08.970> send<00:20:09.240> them<00:20:09.360> a 00:20:09.440 --> 00:20:09.450 align:start position:0% this is configurable we will send them a 00:20:09.450 --> 00:20:11.750 align:start position:0% this is configurable we will send them a list<00:20:09.660> of<00:20:09.780> all<00:20:10.140> the<00:20:10.320> message<00:20:10.860> of<00:20:11.040> the<00:20:11.250> IDS<00:20:11.640> of 00:20:11.750 --> 00:20:11.760 align:start position:0% list of all the message of the IDS of 00:20:11.760 --> 00:20:13.910 align:start position:0% list of all the message of the IDS of the<00:20:11.820> messages<00:20:12.270> that<00:20:12.300> we've<00:20:12.570> seen<00:20:12.780> right<00:20:13.740> and 00:20:13.910 --> 00:20:13.920 align:start position:0% the messages that we've seen right and 00:20:13.920 --> 00:20:17.510 align:start position:0% the messages that we've seen right and this<00:20:14.670> usually<00:20:15.450> happens<00:20:15.900> as<00:20:16.470> well<00:20:16.710> we<00:20:17.250> try<00:20:17.460> to 00:20:17.510 --> 00:20:17.520 align:start position:0% this usually happens as well we try to 00:20:17.520 --> 00:20:19.190 align:start position:0% this usually happens as well we try to make<00:20:17.760> it<00:20:17.790> back<00:20:18.030> this<00:20:18.270> because<00:20:18.540> we<00:20:18.690> want<00:20:18.870> to<00:20:18.960> we 00:20:19.190 --> 00:20:19.200 align:start position:0% make it back this because we want to we 00:20:19.200 --> 00:20:22.130 align:start position:0% make it back this because we want to we don't<00:20:19.230> want<00:20:19.410> to<00:20:19.560> create<00:20:19.910> excess<00:20:21.140> excess 00:20:22.130 --> 00:20:22.140 align:start position:0% don't want to create excess excess 00:20:22.140 --> 00:20:23.810 align:start position:0% don't want to create excess excess overhead<00:20:22.770> in<00:20:22.950> the<00:20:23.040> network<00:20:23.340> that's<00:20:23.580> and<00:20:23.730> then 00:20:23.810 --> 00:20:23.820 align:start position:0% overhead in the network that's and then 00:20:23.820 --> 00:20:25.610 align:start position:0% overhead in the network that's and then that's<00:20:23.970> meant<00:20:24.150> to<00:20:24.180> date<00:20:24.360> around<00:20:24.570> every<00:20:25.470> time 00:20:25.610 --> 00:20:25.620 align:start position:0% that's meant to date around every time 00:20:25.620 --> 00:20:27.050 align:start position:0% that's meant to date around every time that<00:20:25.740> we<00:20:25.860> see<00:20:26.010> a<00:20:26.040> message<00:20:26.250> so<00:20:26.430> we<00:20:26.550> try<00:20:26.730> to<00:20:26.760> make 00:20:27.050 --> 00:20:27.060 align:start position:0% that we see a message so we try to make 00:20:27.060 --> 00:20:28.430 align:start position:0% that we see a message so we try to make it<00:20:27.180> back<00:20:27.300> if<00:20:27.570> we<00:20:27.600> have<00:20:27.870> a<00:20:27.900> message<00:20:28.110> to<00:20:28.260> send 00:20:28.430 --> 00:20:28.440 align:start position:0% it back if we have a message to send 00:20:28.440 --> 00:20:29.960 align:start position:0% it back if we have a message to send them<00:20:28.740> any<00:20:28.890> way<00:20:29.070> than<00:20:29.280> we<00:20:29.370> try<00:20:29.580> to<00:20:29.640> think<00:20:29.850> it 00:20:29.960 --> 00:20:29.970 align:start position:0% them any way than we try to think it 00:20:29.970 --> 00:20:33.440 align:start position:0% them any way than we try to think it back<00:20:30.150> these<00:20:31.110> control<00:20:31.470> messages<00:20:32.060> now<00:20:33.060> if<00:20:33.330> a 00:20:33.440 --> 00:20:33.450 align:start position:0% back these control messages now if a 00:20:33.450 --> 00:20:36.740 align:start position:0% back these control messages now if a peer<00:20:34.670> spots<00:20:35.670> a<00:20:35.790> message<00:20:36.150> that<00:20:36.390> they<00:20:36.510> haven't 00:20:36.740 --> 00:20:36.750 align:start position:0% peer spots a message that they haven't 00:20:36.750 --> 00:20:40.070 align:start position:0% peer spots a message that they haven't seen<00:20:37.070> right<00:20:38.070> they<00:20:38.700> can<00:20:38.910> ask<00:20:39.270> for<00:20:39.660> that<00:20:39.780> message 00:20:40.070 --> 00:20:40.080 align:start position:0% seen right they can ask for that message 00:20:40.080 --> 00:20:43.400 align:start position:0% seen right they can ask for that message they<00:20:40.410> can<00:20:40.530> pull<00:20:40.830> that<00:20:41.010> message<00:20:41.460> by<00:20:42.230> sending<00:20:43.230> an 00:20:43.400 --> 00:20:43.410 align:start position:0% they can pull that message by sending an 00:20:43.410 --> 00:20:46.370 align:start position:0% they can pull that message by sending an I<00:20:43.830> want<00:20:44.250> control<00:20:44.670> message<00:20:45.030> so<00:20:45.330> in<00:20:45.600> that<00:20:45.810> I<00:20:46.020> want 00:20:46.370 --> 00:20:46.380 align:start position:0% I want control message so in that I want 00:20:46.380 --> 00:20:48.470 align:start position:0% I want control message so in that I want a<00:20:46.440> control<00:20:46.680> message<00:20:46.920> that<00:20:47.730> would<00:20:47.910> be<00:20:48.030> listing 00:20:48.470 --> 00:20:48.480 align:start position:0% a control message that would be listing 00:20:48.480 --> 00:20:50.660 align:start position:0% a control message that would be listing the<00:20:48.510> messages<00:20:49.200> that<00:20:49.560> they<00:20:49.860> want<00:20:50.130> us<00:20:50.310> to<00:20:50.340> push 00:20:50.660 --> 00:20:50.670 align:start position:0% the messages that they want us to push 00:20:50.670 --> 00:20:53.330 align:start position:0% the messages that they want us to push to<00:20:50.880> them<00:20:51.090> right<00:20:51.570> why<00:20:52.200> is<00:20:52.260> this<00:20:52.500> important<00:20:53.040> this 00:20:53.330 --> 00:20:53.340 align:start position:0% to them right why is this important this 00:20:53.340 --> 00:20:55.490 align:start position:0% to them right why is this important this is<00:20:53.520> important<00:20:54.030> because<00:20:54.180> it<00:20:54.990> allows<00:20:55.020> us<00:20:55.320> to 00:20:55.490 --> 00:20:55.500 align:start position:0% is important because it allows us to 00:20:55.500 --> 00:20:57.290 align:start position:0% is important because it allows us to take<00:20:55.770> routing<00:20:56.130> decision<00:20:56.550> so<00:20:56.670> I'm<00:20:56.790> at<00:20:57.000> in<00:20:57.180> the 00:20:57.290 --> 00:20:57.300 align:start position:0% take routing decision so I'm at in the 00:20:57.300 --> 00:20:58.850 align:start position:0% take routing decision so I'm at in the case<00:20:57.510> where<00:20:57.780> you<00:20:57.870> have<00:20:57.900> a<00:20:58.110> stable<00:20:58.380> mission 00:20:58.850 --> 00:20:58.860 align:start position:0% case where you have a stable mission 00:20:58.860 --> 00:21:01.040 align:start position:0% case where you have a stable mission right<00:20:59.430> you're<00:20:59.910> in<00:20:59.940> the<00:21:00.060> topic<00:21:00.390> you<00:21:00.870> have<00:21:00.900> a 00:21:01.040 --> 00:21:01.050 align:start position:0% right you're in the topic you have a 00:21:01.050 --> 00:21:03.350 align:start position:0% right you're in the topic you have a bunch<00:21:01.260> of<00:21:01.380> peers<00:21:01.740> that<00:21:02.010> are<00:21:02.490> sending<00:21:03.240> you 00:21:03.350 --> 00:21:03.360 align:start position:0% bunch of peers that are sending you 00:21:03.360 --> 00:21:06.680 align:start position:0% bunch of peers that are sending you messages<00:21:03.480> and<00:21:04.490> another<00:21:05.490> of<00:21:05.580> the<00:21:05.670> year<00:21:05.880> which 00:21:06.680 --> 00:21:06.690 align:start position:0% messages and another of the year which 00:21:06.690 --> 00:21:08.630 align:start position:0% messages and another of the year which is<00:21:06.720> gossiping<00:21:07.230> with<00:21:07.260> you<00:21:07.560> tells<00:21:08.250> you<00:21:08.400> about<00:21:08.520> a 00:21:08.630 --> 00:21:08.640 align:start position:0% is gossiping with you tells you about a 00:21:08.640 --> 00:21:10.010 align:start position:0% is gossiping with you tells you about a message<00:21:09.030> that<00:21:09.390> you<00:21:09.480> have 00:21:10.010 --> 00:21:10.020 align:start position:0% message that you have 00:21:10.020 --> 00:21:13.550 align:start position:0% message that you have yeah<00:21:10.760> this<00:21:11.760> means<00:21:12.000> that<00:21:12.180> your<00:21:12.450> that<00:21:12.780> that 00:21:13.550 --> 00:21:13.560 align:start position:0% yeah this means that your that that 00:21:13.560 --> 00:21:15.740 align:start position:0% yeah this means that your that that deliverability<00:21:14.250> to<00:21:14.640> ability<00:21:15.000> is<00:21:15.120> not<00:21:15.270> 100% 00:21:15.740 --> 00:21:15.750 align:start position:0% deliverability to ability is not 100% 00:21:15.750 --> 00:21:19.010 align:start position:0% deliverability to ability is not 100% right<00:21:16.650> because<00:21:16.950> in<00:21:17.160> your<00:21:17.430> in<00:21:17.700> your<00:21:17.730> mesh<00:21:18.060> you 00:21:19.010 --> 00:21:19.020 align:start position:0% right because in your in your mesh you 00:21:19.020 --> 00:21:20.930 align:start position:0% right because in your in your mesh you haven't<00:21:19.440> received<00:21:19.740> that<00:21:19.770> message<00:21:20.040> yet<00:21:20.490> right 00:21:20.930 --> 00:21:20.940 align:start position:0% haven't received that message yet right 00:21:20.940 --> 00:21:24.800 align:start position:0% haven't received that message yet right so<00:21:21.150> you<00:21:21.600> can<00:21:22.050> use<00:21:22.620> that<00:21:23.250> as<00:21:23.640> a<00:21:23.670> sign<00:21:24.090> as<00:21:24.420> a<00:21:24.450> hint 00:21:24.800 --> 00:21:24.810 align:start position:0% so you can use that as a sign as a hint 00:21:24.810 --> 00:21:27.620 align:start position:0% so you can use that as a sign as a hint to<00:21:24.930> try<00:21:25.560> to<00:21:25.620> repair<00:21:26.040> that<00:21:26.220> pathology<00:21:26.760> right<00:21:27.360> by 00:21:27.620 --> 00:21:27.630 align:start position:0% to try to repair that pathology right by 00:21:27.630 --> 00:21:29.990 align:start position:0% to try to repair that pathology right by pruning<00:21:28.470> peers<00:21:29.070> that<00:21:29.310> you<00:21:29.430> believe<00:21:29.760> are 00:21:29.990 --> 00:21:30.000 align:start position:0% pruning peers that you believe are 00:21:30.000 --> 00:21:32.840 align:start position:0% pruning peers that you believe are unhealthy<00:21:30.510> and<00:21:30.890> grafting<00:21:31.890> with<00:21:32.070> peers<00:21:32.430> would 00:21:32.840 --> 00:21:32.850 align:start position:0% unhealthy and grafting with peers would 00:21:32.850 --> 00:21:34.640 align:start position:0% unhealthy and grafting with peers would appear<00:21:33.240> that<00:21:33.270> sends<00:21:33.720> a<00:21:33.810> message<00:21:33.840> who<00:21:34.380> probably 00:21:34.640 --> 00:21:34.650 align:start position:0% appear that sends a message who probably 00:21:34.650 --> 00:21:36.650 align:start position:0% appear that sends a message who probably has<00:21:35.070> a<00:21:35.100> better<00:21:35.340> route<00:21:35.610> to<00:21:35.910> the<00:21:36.120> restaurant 00:21:36.650 --> 00:21:36.660 align:start position:0% has a better route to the restaurant 00:21:36.660 --> 00:21:39.080 align:start position:0% has a better route to the restaurant manage<00:21:36.810> their<00:21:37.020> memory<00:21:37.320> okay<00:21:38.190> you<00:21:38.910> have<00:21:39.060> one 00:21:39.080 --> 00:21:39.090 align:start position:0% manage their memory okay you have one 00:21:39.090 --> 00:21:42.050 align:start position:0% manage their memory okay you have one baby<00:21:39.560> okay<00:21:40.730> fantastic 00:21:42.050 --> 00:21:42.060 align:start position:0% baby okay fantastic 00:21:42.060 --> 00:21:46.160 align:start position:0% baby okay fantastic I<00:21:42.290> think<00:21:43.290> um<00:21:43.410> one's<00:21:43.650> done<00:21:44.180> so<00:21:45.180> so<00:21:45.780> yeah<00:21:45.900> this<00:21:46.020> is 00:21:46.160 --> 00:21:46.170 align:start position:0% I think um one's done so so yeah this is 00:21:46.170 --> 00:21:48.680 align:start position:0% I think um one's done so so yeah this is kind<00:21:46.380> of<00:21:46.440> like<00:21:46.560> a<00:21:47.070> bit<00:21:47.430> of<00:21:47.460> a<00:21:48.090> schematic<00:21:48.390> view 00:21:48.680 --> 00:21:48.690 align:start position:0% kind of like a bit of a schematic view 00:21:48.690 --> 00:21:51.230 align:start position:0% kind of like a bit of a schematic view of<00:21:48.840> why<00:21:49.410> oh<00:21:49.440> by<00:21:49.710> the<00:21:49.740> way<00:21:49.890> all<00:21:50.340> of<00:21:50.370> this<00:21:50.670> all<00:21:51.180> of 00:21:51.230 --> 00:21:51.240 align:start position:0% of why oh by the way all of this all of 00:21:51.240 --> 00:21:53.810 align:start position:0% of why oh by the way all of this all of these<00:21:51.570> images<00:21:52.020> and<00:21:52.200> so<00:21:52.380> on<00:21:52.560> you<00:21:53.340> can<00:21:53.370> find<00:21:53.670> them 00:21:53.810 --> 00:21:53.820 align:start position:0% these images and so on you can find them 00:21:53.820 --> 00:21:56.360 align:start position:0% these images and so on you can find them on<00:21:53.940> the<00:21:53.970> web<00:21:54.210> so<00:21:54.390> don't<00:21:54.420> worry<00:21:54.840> I<00:21:55.530> just<00:21:55.980> read 00:21:56.360 --> 00:21:56.370 align:start position:0% on the web so don't worry I just read 00:21:56.370 --> 00:21:58.760 align:start position:0% on the web so don't worry I just read you<00:21:56.430> are<00:21:56.580> there<00:21:56.840> now<00:21:57.840> I<00:21:57.870> just<00:21:58.230> want<00:21:58.560> to<00:21:58.620> talk 00:21:58.760 --> 00:21:58.770 align:start position:0% you are there now I just want to talk 00:21:58.770 --> 00:22:01.850 align:start position:0% you are there now I just want to talk quickly<00:21:58.800> about<00:21:59.130> what's<00:21:59.700> next<00:21:59.990> for<00:22:00.990> a<00:22:01.560> gossip 00:22:01.850 --> 00:22:01.860 align:start position:0% quickly about what's next for a gossip 00:22:01.860 --> 00:22:04.730 align:start position:0% quickly about what's next for a gossip zone<00:22:02.040> first<00:22:02.850> of<00:22:03.000> all<00:22:03.210> we<00:22:04.020> want<00:22:04.200> to<00:22:04.290> formalize 00:22:04.730 --> 00:22:04.740 align:start position:0% zone first of all we want to formalize 00:22:04.740 --> 00:22:07.880 align:start position:0% zone first of all we want to formalize concepts<00:22:05.190> of<00:22:05.340> into<00:22:05.640> an<00:22:05.730> academic<00:22:06.180> paper<00:22:06.890> we 00:22:07.880 --> 00:22:07.890 align:start position:0% concepts of into an academic paper we 00:22:07.890 --> 00:22:09.290 align:start position:0% concepts of into an academic paper we want<00:22:08.100> to<00:22:08.160> harden<00:22:08.580> the<00:22:08.940> reference 00:22:09.290 --> 00:22:09.300 align:start position:0% want to harden the reference 00:22:09.300 --> 00:22:12.650 align:start position:0% want to harden the reference implementation<00:22:09.480> and<00:22:10.410> go<00:22:11.030> to<00:22:12.030> the<00:22:12.120> rep<00:22:12.300> is<00:22:12.510> to 00:22:12.650 --> 00:22:12.660 align:start position:0% implementation and go to the rep is to 00:22:12.660 --> 00:22:14.810 align:start position:0% implementation and go to the rep is to enable<00:22:12.900> plugable<00:22:13.500> Rogers<00:22:13.920> this<00:22:14.220> is<00:22:14.400> for<00:22:14.700> us 00:22:14.810 --> 00:22:14.820 align:start position:0% enable plugable Rogers this is for us 00:22:14.820 --> 00:22:16.280 align:start position:0% enable plugable Rogers this is for us very<00:22:15.030> very<00:22:15.360> important<00:22:15.810> for<00:22:15.900> the<00:22:15.990> mission<00:22:16.230> of 00:22:16.280 --> 00:22:16.290 align:start position:0% very very important for the mission of 00:22:16.290 --> 00:22:18.350 align:start position:0% very very important for the mission of gossips<00:22:16.680> of<00:22:16.800> itself<00:22:17.100> and<00:22:17.700> for<00:22:18.120> organizing 00:22:18.350 --> 00:22:18.360 align:start position:0% gossips of itself and for organizing 00:22:18.360 --> 00:22:20.120 align:start position:0% gossips of itself and for organizing blossom<00:22:18.780> time<00:22:18.990> into<00:22:19.170> an<00:22:19.260> academic<00:22:19.410> paper<00:22:19.830> is 00:22:20.120 --> 00:22:20.130 align:start position:0% blossom time into an academic paper is 00:22:20.130 --> 00:22:22.820 align:start position:0% blossom time into an academic paper is gonna<00:22:20.340> be<00:22:21.030> also<00:22:21.300> a<00:22:21.480> robust<00:22:21.900> step<00:22:22.170> in<00:22:22.410> allowing 00:22:22.820 --> 00:22:22.830 align:start position:0% gonna be also a robust step in allowing 00:22:22.830 --> 00:22:26.080 align:start position:0% gonna be also a robust step in allowing other<00:22:23.430> downstream<00:22:23.910> projects<00:22:24.510> to<00:22:24.660> actually 00:22:26.080 --> 00:22:26.090 align:start position:0% other downstream projects to actually 00:22:26.090 --> 00:22:28.970 align:start position:0% other downstream projects to actually build<00:22:27.090> on<00:22:27.360> top<00:22:27.510> of<00:22:27.570> that<00:22:27.720> and<00:22:28.140> then<00:22:28.410> I<00:22:28.500> say<00:22:28.740> and 00:22:28.970 --> 00:22:28.980 align:start position:0% build on top of that and then I say and 00:22:28.980 --> 00:22:30.650 align:start position:0% build on top of that and then I say and to<00:22:29.100> get<00:22:29.250> all<00:22:29.490> this<00:22:29.730> work<00:22:29.910> through<00:22:30.210> peer<00:22:30.630> review 00:22:30.650 --> 00:22:30.660 align:start position:0% to get all this work through peer review 00:22:30.660 --> 00:22:32.240 align:start position:0% to get all this work through peer review because<00:22:31.260> it's<00:22:31.590> essentially<00:22:31.920> a<00:22:32.070> new 00:22:32.240 --> 00:22:32.250 align:start position:0% because it's essentially a new 00:22:32.250 --> 00:22:34.090 align:start position:0% because it's essentially a new contribution<00:22:32.820> to 00:22:34.090 --> 00:22:34.100 align:start position:0% contribution to 00:22:34.100 --> 00:22:36.080 align:start position:0% contribution to we<00:22:35.100> want<00:22:35.280> to<00:22:35.340> enter<00:22:35.430> great<00:22:35.670> discovery 00:22:36.080 --> 00:22:36.090 align:start position:0% we want to enter great discovery 00:22:36.090 --> 00:22:37.720 align:start position:0% we want to enter great discovery mechanisms<00:22:36.660> and<00:22:36.900> there<00:22:37.110> are<00:22:37.290> various 00:22:37.720 --> 00:22:37.730 align:start position:0% mechanisms and there are various 00:22:37.730 --> 00:22:40.600 align:start position:0% mechanisms and there are various benchmarking<00:22:38.730> efforts<00:22:38.850> underway<00:22:39.300> underway 00:22:40.600 --> 00:22:40.610 align:start position:0% benchmarking efforts underway underway 00:22:40.610 --> 00:22:44.720 align:start position:0% benchmarking efforts underway underway important<00:22:41.610> aspect<00:22:42.000> is<00:22:42.210> said<00:22:43.340> gossip<00:22:44.340> site<00:22:44.550> is 00:22:44.720 --> 00:22:44.730 align:start position:0% important aspect is said gossip site is 00:22:44.730 --> 00:22:47.090 align:start position:0% important aspect is said gossip site is not<00:22:44.970> the<00:22:45.120> final<00:22:45.480> destination<00:22:45.710> and<00:22:46.710> gossip 00:22:47.090 --> 00:22:47.100 align:start position:0% not the final destination and gossip 00:22:47.100 --> 00:22:50.180 align:start position:0% not the final destination and gossip itself<00:22:47.400> is<00:22:47.610> a<00:22:48.000> step<00:22:48.540> along<00:22:48.780> the<00:22:49.020> way<00:22:49.190> really 00:22:50.180 --> 00:22:50.190 align:start position:0% itself is a step along the way really 00:22:50.190 --> 00:22:53.240 align:start position:0% itself is a step along the way really the<00:22:50.460> key<00:22:50.670> aspect<00:22:51.090> here<00:22:51.300> is<00:22:51.590> and<00:22:52.590> what<00:22:52.890> we<00:22:53.040> want 00:22:53.240 --> 00:22:53.250 align:start position:0% the key aspect here is and what we want 00:22:53.250 --> 00:22:55.280 align:start position:0% the key aspect here is and what we want to<00:22:53.310> get<00:22:53.400> to<00:22:53.610> is<00:22:53.850> a<00:22:54.180> protocol<00:22:54.690> that<00:22:54.750> we<00:22:54.960> call<00:22:55.170> it 00:22:55.280 --> 00:22:55.290 align:start position:0% to get to is a protocol that we call it 00:22:55.290 --> 00:22:59.870 align:start position:0% to get to is a protocol that we call it X<00:22:55.530> which<00:22:56.430> is<00:22:56.580> a<00:22:56.610> combination<00:22:57.210> of<00:22:57.360> Gumtree<00:22:58.880> high 00:22:59.870 --> 00:22:59.880 align:start position:0% X which is a combination of Gumtree high 00:22:59.880 --> 00:23:01.700 align:start position:0% X which is a combination of Gumtree high Parkview<00:23:00.360> for<00:23:00.570> membership<00:23:00.930> maintenance<00:23:01.470> and 00:23:01.700 --> 00:23:01.710 align:start position:0% Parkview for membership maintenance and 00:23:01.710 --> 00:23:04.210 align:start position:0% Parkview for membership maintenance and low<00:23:01.860> cost<00:23:02.130> for<00:23:02.370> the<00:23:02.550> personality<00:23:02.900> awareness 00:23:04.210 --> 00:23:04.220 align:start position:0% low cost for the personality awareness 00:23:04.220 --> 00:23:07.910 align:start position:0% low cost for the personality awareness machine<00:23:05.220> and<00:23:05.610> so<00:23:05.760> on<00:23:06.080> and<00:23:07.080> this<00:23:07.290> was<00:23:07.440> a<00:23:07.470> Daoist 00:23:07.910 --> 00:23:07.920 align:start position:0% machine and so on and this was a Daoist 00:23:07.920 --> 00:23:10.640 align:start position:0% machine and so on and this was a Daoist accession<00:23:08.430> to<00:23:08.910> model<00:23:09.570> the<00:23:10.080> kind<00:23:10.350> of<00:23:10.500> behavior 00:23:10.640 --> 00:23:10.650 align:start position:0% accession to model the kind of behavior 00:23:10.650 --> 00:23:15.200 align:start position:0% accession to model the kind of behavior that<00:23:11.010> are<00:23:11.190> described<00:23:11.610> so<00:23:12.000> if<00:23:12.480> we<00:23:13.130> so<00:23:14.210> with 00:23:15.200 --> 00:23:15.210 align:start position:0% that are described so if we so with 00:23:15.210 --> 00:23:17.780 align:start position:0% that are described so if we so with episode<00:23:15.630> we'll<00:23:15.870> be<00:23:15.900> able<00:23:16.080> to<00:23:16.260> build<00:23:16.790> dynamic 00:23:17.780 --> 00:23:17.790 align:start position:0% episode we'll be able to build dynamic 00:23:17.790 --> 00:23:21.920 align:start position:0% episode we'll be able to build dynamic dissemination<00:23:18.780> tricks<00:23:19.340> that<00:23:20.340> are<00:23:20.930> mutating 00:23:21.920 --> 00:23:21.930 align:start position:0% dissemination tricks that are mutating 00:23:21.930 --> 00:23:23.870 align:start position:0% dissemination tricks that are mutating and<00:23:22.230> that<00:23:22.440> are<00:23:22.530> adapting<00:23:23.160> to<00:23:23.340> the<00:23:23.430> conditions 00:23:23.870 --> 00:23:23.880 align:start position:0% and that are adapting to the conditions 00:23:23.880 --> 00:23:26.090 align:start position:0% and that are adapting to the conditions of<00:23:24.030> the<00:23:24.150> network<00:23:24.540> by<00:23:25.080> keeping<00:23:25.440> track<00:23:25.710> of<00:23:25.920> the 00:23:26.090 --> 00:23:26.100 align:start position:0% of the network by keeping track of the 00:23:26.100 --> 00:23:27.380 align:start position:0% of the network by keeping track of the peers<00:23:26.310> that<00:23:26.400> are<00:23:26.550> better<00:23:26.730> connected<00:23:27.240> to<00:23:27.270> the 00:23:27.380 --> 00:23:27.390 align:start position:0% peers that are better connected to the 00:23:27.390 --> 00:23:29.060 align:start position:0% peers that are better connected to the network<00:23:27.660> and<00:23:27.930> as<00:23:28.110> one<00:23:28.260> of<00:23:28.290> those<00:23:28.440> peers<00:23:28.740> that 00:23:29.060 --> 00:23:29.070 align:start position:0% network and as one of those peers that 00:23:29.070 --> 00:23:31.250 align:start position:0% network and as one of those peers that happen<00:23:29.730> to<00:23:29.880> present<00:23:30.240> mythology's<00:23:30.900> rivers 00:23:31.250 --> 00:23:31.260 align:start position:0% happen to present mythology's rivers 00:23:31.260 --> 00:23:34.130 align:start position:0% happen to present mythology's rivers right<00:23:31.740> so<00:23:32.160> whenever<00:23:32.340> we<00:23:32.670> find<00:23:32.910> messages<00:23:33.630> that 00:23:34.130 --> 00:23:34.140 align:start position:0% right so whenever we find messages that 00:23:34.140 --> 00:23:36.860 align:start position:0% right so whenever we find messages that we<00:23:34.230> haven't<00:23:34.530> seen<00:23:34.770> that<00:23:35.070> article<00:23:36.000> said<00:23:36.180> that<00:23:36.480> I 00:23:36.860 --> 00:23:36.870 align:start position:0% we haven't seen that article said that I 00:23:36.870 --> 00:23:39.020 align:start position:0% we haven't seen that article said that I mean<00:23:37.110> coming<00:23:37.320> also<00:23:37.530> from<00:23:37.680> another<00:23:38.100> peer<00:23:38.340> we 00:23:39.020 --> 00:23:39.030 align:start position:0% mean coming also from another peer we 00:23:39.030 --> 00:23:41.480 align:start position:0% mean coming also from another peer we can<00:23:39.270> rebalance<00:23:39.990> the<00:23:40.350> tree<00:23:40.560> and<00:23:40.890> make<00:23:41.340> sure 00:23:41.480 --> 00:23:41.490 align:start position:0% can rebalance the tree and make sure 00:23:41.490 --> 00:23:43.550 align:start position:0% can rebalance the tree and make sure that<00:23:41.700> we<00:23:41.850> always<00:23:42.060> have<00:23:42.420> a<00:23:42.450> good<00:23:43.020> connection<00:23:43.290> to 00:23:43.550 --> 00:23:43.560 align:start position:0% that we always have a good connection to 00:23:43.560 --> 00:23:46.070 align:start position:0% that we always have a good connection to them<00:23:43.830> right<00:23:44.250> we<00:23:44.700> want<00:23:44.910> to<00:23:45.060> so<00:23:45.570> this<00:23:45.660> is<00:23:45.720> what<00:23:45.960> we 00:23:46.070 --> 00:23:46.080 align:start position:0% them right we want to so this is what we 00:23:46.080 --> 00:23:48.050 align:start position:0% them right we want to so this is what we also<00:23:46.200> call<00:23:46.500> this<00:23:46.650> healthy<00:23:46.920> little<00:23:47.130> mesh<00:23:47.310> we 00:23:48.050 --> 00:23:48.060 align:start position:0% also call this healthy little mesh we 00:23:48.060 --> 00:23:51.230 align:start position:0% also call this healthy little mesh we want<00:23:48.300> to<00:23:48.980> introduce<00:23:49.980> adaptive<00:23:50.580> cash<00:23:50.820> flows 00:23:51.230 --> 00:23:51.240 align:start position:0% want to introduce adaptive cash flows 00:23:51.240 --> 00:23:53.390 align:start position:0% want to introduce adaptive cash flows and<00:23:51.570> things<00:23:52.500> like<00:23:52.680> collaborative<00:23:53.100> and 00:23:53.390 --> 00:23:53.400 align:start position:0% and things like collaborative and 00:23:53.400 --> 00:23:53.970 align:start position:0% and things like collaborative and passive 00:23:53.970 --> 00:23:53.980 align:start position:0% passive 00:23:53.980 --> 00:23:55.710 align:start position:0% passive Bishop<00:23:54.460> you<00:23:54.610> so<00:23:54.910> something<00:23:55.240> that's<00:23:55.270> that's 00:23:55.710 --> 00:23:55.720 align:start position:0% Bishop you so something that's that's 00:23:55.720 --> 00:23:59.340 align:start position:0% Bishop you so something that's that's key<00:23:56.020> here<00:23:56.260> is<00:23:56.559> the<00:23:57.549> ability<00:23:58.059> to<00:23:58.750> send 00:23:59.340 --> 00:23:59.350 align:start position:0% key here is the ability to send 00:23:59.350 --> 00:24:01.590 align:start position:0% key here is the ability to send advisories<00:23:59.919> over<00:24:00.220> the<00:24:00.309> network<00:24:00.520> of<00:24:00.910> what 00:24:01.590 --> 00:24:01.600 align:start position:0% advisories over the network of what 00:24:01.600 --> 00:24:03.510 align:start position:0% advisories over the network of what peers<00:24:01.870> are<00:24:02.110> available<00:24:02.590> at<00:24:02.710> which<00:24:02.890> time<00:24:03.130> so 00:24:03.510 --> 00:24:03.520 align:start position:0% peers are available at which time so 00:24:03.520 --> 00:24:08.070 align:start position:0% peers are available at which time so ideally<00:24:04.299> you<00:24:04.900> want<00:24:05.140> to<00:24:05.700> use<00:24:06.700> a<00:24:07.080> ambience 00:24:08.070 --> 00:24:08.080 align:start position:0% ideally you want to use a ambience 00:24:08.080 --> 00:24:10.260 align:start position:0% ideally you want to use a ambience discovery<00:24:08.650> mechanism<00:24:09.190> like<00:24:09.400> the<00:24:09.610> teach<00:24:09.790> D<00:24:10.059> for 00:24:10.260 --> 00:24:10.270 align:start position:0% discovery mechanism like the teach D for 00:24:10.270 --> 00:24:13.049 align:start position:0% discovery mechanism like the teach D for example<00:24:10.299> to<00:24:10.870> find<00:24:11.110> a<00:24:11.410> seat<00:24:11.830> a<00:24:12.220> limited<00:24:12.910> number 00:24:13.049 --> 00:24:13.059 align:start position:0% example to find a seat a limited number 00:24:13.059 --> 00:24:16.860 align:start position:0% example to find a seat a limited number of<00:24:13.480> peers<00:24:14.309> accesses<00:24:15.309> to<00:24:15.669> bind<00:24:16.120> to<00:24:16.330> that<00:24:16.480> topic 00:24:16.860 --> 00:24:16.870 align:start position:0% of peers accesses to bind to that topic 00:24:16.870 --> 00:24:21.570 align:start position:0% of peers accesses to bind to that topic and<00:24:17.320> once<00:24:18.040> you<00:24:18.549> have<00:24:18.960> those<00:24:19.960> those<00:24:20.650> few<00:24:21.250> peers 00:24:21.570 --> 00:24:21.580 align:start position:0% and once you have those those few peers 00:24:21.580 --> 00:24:23.460 align:start position:0% and once you have those those few peers which<00:24:21.880> are<00:24:22.330> probably<00:24:22.570> overloaded<00:24:23.320> because 00:24:23.460 --> 00:24:23.470 align:start position:0% which are probably overloaded because 00:24:23.470 --> 00:24:25.470 align:start position:0% which are probably overloaded because they're<00:24:23.770> being<00:24:23.980> advertised<00:24:24.520> right<00:24:24.850> if<00:24:25.299> you 00:24:25.470 --> 00:24:25.480 align:start position:0% they're being advertised right if you 00:24:25.480 --> 00:24:28.770 align:start position:0% they're being advertised right if you want<00:24:25.780> to<00:24:26.370> inquire<00:24:27.370> them<00:24:27.760> for<00:24:28.000> other<00:24:28.270> members 00:24:28.770 --> 00:24:28.780 align:start position:0% want to inquire them for other members 00:24:28.780 --> 00:24:30.570 align:start position:0% want to inquire them for other members that<00:24:29.260> they<00:24:29.410> know<00:24:29.559> about<00:24:29.710> information<00:24:30.040> you 00:24:30.570 --> 00:24:30.580 align:start position:0% that they know about information you 00:24:30.580 --> 00:24:33.539 align:start position:0% that they know about information you want<00:24:30.820> you<00:24:31.059> want<00:24:31.510> to<00:24:31.630> create<00:24:32.049> gossip<00:24:32.590> not<00:24:33.250> just 00:24:33.539 --> 00:24:33.549 align:start position:0% want you want to create gossip not just 00:24:33.549 --> 00:24:35.130 align:start position:0% want you want to create gossip not just about<00:24:33.760> the<00:24:33.910> messages<00:24:34.390> that<00:24:34.419> are<00:24:34.690> available 00:24:35.130 --> 00:24:35.140 align:start position:0% about the messages that are available 00:24:35.140 --> 00:24:37.409 align:start position:0% about the messages that are available but<00:24:35.320> about<00:24:35.559> what<00:24:35.860> peers<00:24:36.309> are<00:24:36.640> present<00:24:37.120> at<00:24:37.240> that 00:24:37.409 --> 00:24:37.419 align:start position:0% but about what peers are present at that 00:24:37.419 --> 00:24:39.570 align:start position:0% but about what peers are present at that in<00:24:37.690> that<00:24:37.720> time<00:24:38.080> right<00:24:38.830> so<00:24:39.010> this<00:24:39.130> is<00:24:39.190> something 00:24:39.570 --> 00:24:39.580 align:start position:0% in that time right so this is something 00:24:39.580 --> 00:24:41.430 align:start position:0% in that time right so this is something that<00:24:39.610> is<00:24:40.330> going<00:24:40.540> to<00:24:40.600> be<00:24:40.720> that's<00:24:41.110> going<00:24:41.260> to<00:24:41.380> be 00:24:41.430 --> 00:24:41.440 align:start position:0% that is going to be that's going to be 00:24:41.440 --> 00:24:44.159 align:start position:0% that is going to be that's going to be that's<00:24:42.070> coming<00:24:42.370> down<00:24:42.460> the<00:24:42.520> pike<00:24:43.020> it's<00:24:44.020> also 00:24:44.159 --> 00:24:44.169 align:start position:0% that's coming down the pike it's also 00:24:44.169 --> 00:24:47.640 align:start position:0% that's coming down the pike it's also has<00:24:44.620> some<00:24:44.799> notions<00:24:45.100> of<00:24:45.220> appearance<00:24:46.020> also<00:24:47.020> as<00:24:47.590> I 00:24:47.640 --> 00:24:47.650 align:start position:0% has some notions of appearance also as I 00:24:47.650 --> 00:24:51.180 align:start position:0% has some notions of appearance also as I said<00:24:48.100> all<00:24:48.429> of<00:24:48.640> these<00:24:48.820> time<00:24:49.120> cards<00:24:49.710> and<00:24:50.710> these 00:24:51.180 --> 00:24:51.190 align:start position:0% said all of these time cards and these 00:24:51.190 --> 00:24:52.860 align:start position:0% said all of these time cards and these schematics<00:24:51.429> which<00:24:52.059> I<00:24:52.150> previewed<00:24:52.419> eyes<00:24:52.570> and 00:24:52.860 --> 00:24:52.870 align:start position:0% schematics which I previewed eyes and 00:24:52.870 --> 00:24:55.049 align:start position:0% schematics which I previewed eyes and very<00:24:52.929> beautiful<00:24:53.169> they<00:24:54.130> are<00:24:54.160> available<00:24:54.760> under 00:24:55.049 --> 00:24:55.059 align:start position:0% very beautiful they are available under 00:24:55.059 --> 00:24:58.650 align:start position:0% very beautiful they are available under the<00:24:55.330> docs<00:24:55.510> website<00:24:56.220> so<00:24:57.220> make<00:24:57.910> sure<00:24:57.940> that<00:24:58.419> you 00:24:58.650 --> 00:24:58.660 align:start position:0% the docs website so make sure that you 00:24:58.660 --> 00:25:01.470 align:start position:0% the docs website so make sure that you check<00:24:58.929> out<00:24:59.110> the<00:24:59.260> new<00:24:59.500> snazzy<00:25:00.160> docs<00:25:00.520> for<00:25:00.850> gossip 00:25:01.470 --> 00:25:01.480 align:start position:0% check out the new snazzy docs for gossip 00:25:01.480 --> 00:25:03.810 align:start position:0% check out the new snazzy docs for gossip stuff<00:25:01.660> which<00:25:02.049> we<00:25:02.260> just<00:25:02.440> released<00:25:02.610> one<00:25:03.610> week 00:25:03.810 --> 00:25:03.820 align:start position:0% stuff which we just released one week 00:25:03.820 --> 00:25:11.150 align:start position:0% stuff which we just released one week ago<00:25:04.350> just<00:25:05.350> in<00:25:05.470> time<00:25:05.590> for<00:25:05.650> that 00:25:11.150 --> 00:25:11.160 align:start position:0% 00:25:11.160 --> 00:25:17.500 align:start position:0% [Applause]