WEBVTT Kind: captions Language: en 00:00:01.070 --> 00:00:10.570 align:start position:0% [Applause] 00:00:10.570 --> 00:00:10.580 align:start position:0% 00:00:10.580 --> 00:00:15.160 align:start position:0% hello<00:00:11.610> it's<00:00:12.570> like<00:00:12.780> Rockley<00:00:13.320> 9:15 00:00:15.160 --> 00:00:15.170 align:start position:0% hello it's like Rockley 9:15 00:00:15.170 --> 00:00:17.779 align:start position:0% hello it's like Rockley 9:15 everybody's<00:00:16.170> here<00:00:16.379> have<00:00:16.619> which<00:00:17.250> is<00:00:17.369> amazing 00:00:17.779 --> 00:00:17.789 align:start position:0% everybody's here have which is amazing 00:00:17.789 --> 00:00:19.249 align:start position:0% everybody's here have which is amazing thank<00:00:18.000> you<00:00:18.119> so<00:00:18.270> much<00:00:18.480> we<00:00:18.779> really<00:00:18.810> didn't 00:00:19.249 --> 00:00:19.259 align:start position:0% thank you so much we really didn't 00:00:19.259 --> 00:00:21.800 align:start position:0% thank you so much we really didn't expect<00:00:19.320> everybody<00:00:20.009> showing<00:00:20.189> them<00:00:20.369> time<00:00:20.810> that 00:00:21.800 --> 00:00:21.810 align:start position:0% expect everybody showing them time that 00:00:21.810 --> 00:00:23.900 align:start position:0% expect everybody showing them time that shown<00:00:22.259> that<00:00:22.500> you're<00:00:22.680> either<00:00:22.800> jet<00:00:23.279> lagged<00:00:23.580> the 00:00:23.900 --> 00:00:23.910 align:start position:0% shown that you're either jet lagged the 00:00:23.910 --> 00:00:26.089 align:start position:0% shown that you're either jet lagged the right<00:00:24.180> way<00:00:24.450> or<00:00:24.750> that<00:00:25.079> you<00:00:25.200> really<00:00:25.410> care<00:00:25.650> either 00:00:26.089 --> 00:00:26.099 align:start position:0% right way or that you really care either 00:00:26.099 --> 00:00:29.320 align:start position:0% right way or that you really care either way<00:00:26.550> it's<00:00:27.240> really<00:00:27.539> really<00:00:27.750> good 00:00:29.320 --> 00:00:29.330 align:start position:0% way it's really really good 00:00:29.330 --> 00:00:31.640 align:start position:0% way it's really really good let's<00:00:30.330> walk<00:00:30.539> through<00:00:30.570> the<00:00:30.840> day<00:00:31.019> very<00:00:31.380> very 00:00:31.640 --> 00:00:31.650 align:start position:0% let's walk through the day very very 00:00:31.650 --> 00:00:32.509 align:start position:0% let's walk through the day very very briefly 00:00:32.509 --> 00:00:32.519 align:start position:0% briefly 00:00:32.519 --> 00:00:34.910 align:start position:0% briefly like<00:00:33.210> right<00:00:33.660> now<00:00:33.690> 15<00:00:34.260> minutes<00:00:34.559> of<00:00:34.710> just 00:00:34.910 --> 00:00:34.920 align:start position:0% like right now 15 minutes of just 00:00:34.920 --> 00:00:36.890 align:start position:0% like right now 15 minutes of just welcoming<00:00:35.370> wards<00:00:35.820> and<00:00:36.000> like<00:00:36.150> shortly<00:00:36.600> throws 00:00:36.890 --> 00:00:36.900 align:start position:0% welcoming wards and like shortly throws 00:00:36.900 --> 00:00:38.900 align:start position:0% welcoming wards and like shortly throws like<00:00:37.080> everybody<00:00:37.589> will<00:00:37.739> say<00:00:37.920> roughly<00:00:38.370> 102<00:00:38.879> Oh 00:00:38.900 --> 00:00:38.910 align:start position:0% like everybody will say roughly 102 Oh 00:00:38.910 --> 00:00:41.090 align:start position:0% like everybody will say roughly 102 Oh sentences<00:00:39.420> like<00:00:39.540> we<00:00:39.900> were<00:00:40.080> like<00:00:40.379> why<00:00:40.739> you<00:00:40.800> care 00:00:41.090 --> 00:00:41.100 align:start position:0% sentences like we were like why you care 00:00:41.100 --> 00:00:43.160 align:start position:0% sentences like we were like why you care about<00:00:41.280> p2p<00:00:41.879> or<00:00:42.180> or<00:00:42.360> maybe<00:00:42.570> you<00:00:42.720> don't<00:00:42.870> major 00:00:43.160 --> 00:00:43.170 align:start position:0% about p2p or or maybe you don't major 00:00:43.170 --> 00:00:45.170 align:start position:0% about p2p or or maybe you don't major you're<00:00:43.530> just<00:00:43.799> like<00:00:44.040> suppose<00:00:44.430> it's<00:00:44.610> about<00:00:44.879> like 00:00:45.170 --> 00:00:45.180 align:start position:0% you're just like suppose it's about like 00:00:45.180 --> 00:00:47.299 align:start position:0% you're just like suppose it's about like that's<00:00:45.659> also<00:00:45.900> unacceptable<00:00:46.650> as<00:00:46.799> scientists 00:00:47.299 --> 00:00:47.309 align:start position:0% that's also unacceptable as scientists 00:00:47.309 --> 00:00:50.240 align:start position:0% that's also unacceptable as scientists you<00:00:47.519> know<00:00:47.580> you<00:00:48.210> do<00:00:48.360> you<00:00:48.540> and<00:00:49.019> and<00:00:49.830> then<00:00:49.979> we<00:00:50.159> have 00:00:50.240 --> 00:00:50.250 align:start position:0% you know you do you and and then we have 00:00:50.250 --> 00:00:51.950 align:start position:0% you know you do you and and then we have project<00:00:50.670> presentations<00:00:51.299> and<00:00:51.479> discussion 00:00:51.950 --> 00:00:51.960 align:start position:0% project presentations and discussion 00:00:51.960 --> 00:00:53.869 align:start position:0% project presentations and discussion vlogs<00:00:52.199> in<00:00:52.440> the<00:00:52.559> project<00:00:52.979> presentations<00:00:53.580> like 00:00:53.869 --> 00:00:53.879 align:start position:0% vlogs in the project presentations like 00:00:53.879 --> 00:00:55.640 align:start position:0% vlogs in the project presentations like we<00:00:54.089> tried<00:00:54.330> to<00:00:54.479> squeeze<00:00:54.720> in<00:00:54.900> as<00:00:55.080> many<00:00:55.379> as<00:00:55.530> we 00:00:55.640 --> 00:00:55.650 align:start position:0% we tried to squeeze in as many as we 00:00:55.650 --> 00:00:58.039 align:start position:0% we tried to squeeze in as many as we could<00:00:55.830> so<00:00:56.129> like<00:00:56.339> we're<00:00:56.909> kind<00:00:57.180> of<00:00:57.299> gonna<00:00:57.420> be<00:00:57.629> my 00:00:58.039 --> 00:00:58.049 align:start position:0% could so like we're kind of gonna be my 00:00:58.049 --> 00:00:59.990 align:start position:0% could so like we're kind of gonna be my new<00:00:58.170> here<00:00:58.500> my<00:00:58.860> new<00:00:58.920> is<00:00:59.070> amazing<00:00:59.489> he's<00:00:59.670> part<00:00:59.909> of 00:00:59.990 --> 00:01:00.000 align:start position:0% new here my new is amazing he's part of 00:01:00.000 --> 00:01:02.090 align:start position:0% new here my new is amazing he's part of the<00:01:00.119> DEF<00:01:00.299> CON<00:01:00.449> staff<00:01:00.750> and<00:01:01.019> like<00:01:01.199> he's<00:01:01.470> gonna<00:01:01.949> be 00:01:02.090 --> 00:01:02.100 align:start position:0% the DEF CON staff and like he's gonna be 00:01:02.100 --> 00:01:04.640 align:start position:0% the DEF CON staff and like he's gonna be keeping<00:01:02.430> the<00:01:02.519> time<00:01:02.760> he<00:01:03.390> prepared<00:01:03.809> everything 00:01:04.640 --> 00:01:04.650 align:start position:0% keeping the time he prepared everything 00:01:04.650 --> 00:01:06.770 align:start position:0% keeping the time he prepared everything he's<00:01:05.100> also<00:01:05.430> he<00:01:05.670> also<00:01:05.700> prefers<00:01:06.210> the<00:01:06.330> cards<00:01:06.659> that 00:01:06.770 --> 00:01:06.780 align:start position:0% he's also he also prefers the cards that 00:01:06.780 --> 00:01:08.539 align:start position:0% he's also he also prefers the cards that showing<00:01:07.530> you<00:01:07.650> when<00:01:07.799> you're<00:01:07.920> out<00:01:08.130> of<00:01:08.159> time 00:01:08.539 --> 00:01:08.549 align:start position:0% showing you when you're out of time 00:01:08.549 --> 00:01:10.310 align:start position:0% showing you when you're out of time because<00:01:08.850> I<00:01:08.909> think<00:01:08.970> like<00:01:09.270> about<00:01:09.689> half<00:01:09.960> of<00:01:09.990> the 00:01:10.310 --> 00:01:10.320 align:start position:0% because I think like about half of the 00:01:10.320 --> 00:01:12.050 align:start position:0% because I think like about half of the room<00:01:10.439> are<00:01:10.560> speakers<00:01:10.979> right<00:01:11.340> so<00:01:11.610> like<00:01:11.850> you<00:01:12.030> know 00:01:12.050 --> 00:01:12.060 align:start position:0% room are speakers right so like you know 00:01:12.060 --> 00:01:14.179 align:start position:0% room are speakers right so like you know pay<00:01:12.659> attention<00:01:13.080> to<00:01:13.170> what<00:01:13.320> multis<00:01:13.710> showing<00:01:14.009> you 00:01:14.179 --> 00:01:14.189 align:start position:0% pay attention to what multis showing you 00:01:14.189 --> 00:01:16.639 align:start position:0% pay attention to what multis showing you we<00:01:15.000> know<00:01:15.149> that<00:01:15.390> these<00:01:15.570> are<00:01:15.719> short<00:01:16.079> time<00:01:16.350> slots 00:01:16.639 --> 00:01:16.649 align:start position:0% we know that these are short time slots 00:01:16.649 --> 00:01:18.169 align:start position:0% we know that these are short time slots and<00:01:16.859> it's<00:01:17.009> impossible<00:01:17.250> to<00:01:17.549> cover<00:01:17.850> everything 00:01:18.169 --> 00:01:18.179 align:start position:0% and it's impossible to cover everything 00:01:18.179 --> 00:01:20.149 align:start position:0% and it's impossible to cover everything in<00:01:18.390> such<00:01:18.659> a<00:01:18.689> short<00:01:18.960> amount<00:01:19.020> of<00:01:19.259> time<00:01:19.350> but<00:01:19.979> it's 00:01:20.149 --> 00:01:20.159 align:start position:0% in such a short amount of time but it's 00:01:20.159 --> 00:01:22.310 align:start position:0% in such a short amount of time but it's more<00:01:20.340> of<00:01:20.460> like<00:01:20.670> hey<00:01:21.090> we're<00:01:21.390> like<00:01:21.570> galvanizing 00:01:22.310 --> 00:01:22.320 align:start position:0% more of like hey we're like galvanizing 00:01:22.320 --> 00:01:24.020 align:start position:0% more of like hey we're like galvanizing the<00:01:22.439> community<00:01:22.920> now<00:01:23.070> and<00:01:23.399> like<00:01:23.549> starting<00:01:23.969> a 00:01:24.020 --> 00:01:24.030 align:start position:0% the community now and like starting a 00:01:24.030 --> 00:01:25.340 align:start position:0% the community now and like starting a thing<00:01:24.240> that<00:01:24.479> we're<00:01:24.630> going<00:01:24.719> to<00:01:24.810> be<00:01:24.869> doing<00:01:24.990> for 00:01:25.340 --> 00:01:25.350 align:start position:0% thing that we're going to be doing for 00:01:25.350 --> 00:01:27.050 align:start position:0% thing that we're going to be doing for at<00:01:25.469> least<00:01:25.649> three<00:01:25.979> months<00:01:26.130> together<00:01:26.579> working 00:01:27.050 --> 00:01:27.060 align:start position:0% at least three months together working 00:01:27.060 --> 00:01:29.090 align:start position:0% at least three months together working on<00:01:27.149> mapping<00:01:27.479> of<00:01:27.659> the<00:01:27.749> p2p<00:01:28.049> ecosystem<00:01:28.710> solving 00:01:29.090 --> 00:01:29.100 align:start position:0% on mapping of the p2p ecosystem solving 00:01:29.100 --> 00:01:31.760 align:start position:0% on mapping of the p2p ecosystem solving challenges<00:01:29.549> together<00:01:29.820> and<00:01:30.499> you<00:01:31.499> know<00:01:31.619> and 00:01:31.760 --> 00:01:31.770 align:start position:0% challenges together and you know and 00:01:31.770 --> 00:01:33.440 align:start position:0% challenges together and you know and things<00:01:31.979> like<00:01:32.130> that<00:01:32.189> so<00:01:32.369> basically<00:01:32.999> this<00:01:33.390> is 00:01:33.440 --> 00:01:33.450 align:start position:0% things like that so basically this is 00:01:33.450 --> 00:01:35.209 align:start position:0% things like that so basically this is more<00:01:33.869> of<00:01:33.960> like<00:01:33.990> boys<00:01:34.380> who<00:01:34.740> what<00:01:34.979> are<00:01:35.130> you 00:01:35.209 --> 00:01:35.219 align:start position:0% more of like boys who what are you 00:01:35.219 --> 00:01:36.770 align:start position:0% more of like boys who what are you working<00:01:35.579> on<00:01:35.670> what<00:01:35.909> are<00:01:35.969> the<00:01:36.240> challenges<00:01:36.749> and 00:01:36.770 --> 00:01:36.780 align:start position:0% working on what are the challenges and 00:01:36.780 --> 00:01:38.539 align:start position:0% working on what are the challenges and like<00:01:37.170> let's<00:01:37.560> work<00:01:37.770> on<00:01:37.950> a<00:01:38.009> common<00:01:38.189> vision<00:01:38.429> for 00:01:38.539 --> 00:01:38.549 align:start position:0% like let's work on a common vision for 00:01:38.549 --> 00:01:40.580 align:start position:0% like let's work on a common vision for solving<00:01:39.030> them<00:01:39.179> we<00:01:39.780> have<00:01:39.899> -<00:01:40.109> for<00:01:40.319> the<00:01:40.439> call 00:01:40.580 --> 00:01:40.590 align:start position:0% solving them we have - for the call 00:01:40.590 --> 00:01:41.090 align:start position:0% solving them we have - for the call today 00:01:41.090 --> 00:01:41.100 align:start position:0% today 00:01:41.100 --> 00:01:43.730 align:start position:0% today Carrie<00:01:41.520> sighs<00:01:41.729> here<00:01:42.090> we<00:01:42.689> have<00:01:43.170> Demetrius 00:01:43.730 --> 00:01:43.740 align:start position:0% Carrie sighs here we have Demetrius 00:01:43.740 --> 00:01:46.580 align:start position:0% Carrie sighs here we have Demetrius enthroned<00:01:44.189> stages<00:01:44.640> we<00:01:45.179> have<00:01:45.229> September<00:01:46.229> to 00:01:46.580 --> 00:01:46.590 align:start position:0% enthroned stages we have September to 00:01:46.590 --> 00:01:49.550 align:start position:0% enthroned stages we have September to give<00:01:46.740> out<00:01:46.859> reputation<00:01:47.299> in<00:01:48.299> p2p<00:01:48.659> networks<00:01:49.049> we 00:01:49.550 --> 00:01:49.560 align:start position:0% give out reputation in p2p networks we 00:01:49.560 --> 00:01:52.309 align:start position:0% give out reputation in p2p networks we have<00:01:49.590> three<00:01:49.890> trade<00:01:50.159> showing<00:01:50.640> wireline<00:01:51.319> we 00:01:52.309 --> 00:01:52.319 align:start position:0% have three trade showing wireline we 00:01:52.319 --> 00:01:54.639 align:start position:0% have three trade showing wireline we have<00:01:52.560> Deb<00:01:53.280> Russian<00:01:53.639> with<00:01:53.729> Altea 00:01:54.639 --> 00:01:54.649 align:start position:0% have Deb Russian with Altea 00:01:54.649 --> 00:01:56.749 align:start position:0% have Deb Russian with Altea very<00:01:55.649> all<00:01:55.740> showing<00:01:55.979> talking<00:01:56.609> about 00:01:56.749 --> 00:01:56.759 align:start position:0% very all showing talking about 00:01:56.759 --> 00:01:58.700 align:start position:0% very all showing talking about redundancy<00:01:57.329> in<00:01:57.389> p2p<00:01:57.749> systems<00:01:58.079> I<00:01:58.319> don't<00:01:58.499> think 00:01:58.700 --> 00:01:58.710 align:start position:0% redundancy in p2p systems I don't think 00:01:58.710 --> 00:02:00.580 align:start position:0% redundancy in p2p systems I don't think she's<00:01:58.859> here<00:01:59.039> yet<00:01:59.100> but<00:01:59.429> she's<00:01:59.609> not<00:01:59.700> arrived<00:01:59.999> sir 00:02:00.580 --> 00:02:00.590 align:start position:0% she's here yet but she's not arrived sir 00:02:00.590 --> 00:02:02.300 align:start position:0% she's here yet but she's not arrived sir Antoine<00:02:01.590> is<00:02:01.619> gonna<00:02:01.889> be<00:02:01.950> talking<00:02:02.100> about 00:02:02.300 --> 00:02:02.310 align:start position:0% Antoine is gonna be talking about 00:02:02.310 --> 00:02:04.749 align:start position:0% Antoine is gonna be talking about testing<00:02:02.700> networks<00:02:03.060> with<00:02:03.270> with<00:02:03.810> Wyatt<00:02:04.049> block 00:02:04.749 --> 00:02:04.759 align:start position:0% testing networks with with Wyatt block 00:02:04.759 --> 00:02:07.429 align:start position:0% testing networks with with Wyatt block Matthew<00:02:05.759> sleepers<00:02:06.119> in<00:02:06.329> a<00:02:06.420> give<00:02:06.719> overview<00:02:07.350> of 00:02:07.429 --> 00:02:07.439 align:start position:0% Matthew sleepers in a give overview of 00:02:07.439 --> 00:02:10.130 align:start position:0% Matthew sleepers in a give overview of SSB<00:02:07.829> jaya<00:02:08.640> promises<00:02:09.149> we<00:02:09.330> wanted<00:02:09.869> to<00:02:09.959> be<00:02:10.110> here 00:02:10.130 --> 00:02:10.140 align:start position:0% SSB jaya promises we wanted to be here 00:02:10.140 --> 00:02:11.270 align:start position:0% SSB jaya promises we wanted to be here but<00:02:10.470> I<00:02:10.530> think<00:02:10.770> she 00:02:11.270 --> 00:02:11.280 align:start position:0% but I think she 00:02:11.280 --> 00:02:14.090 align:start position:0% but I think she small<00:02:11.970> accidents<00:02:12.540> last<00:02:12.780> minute<00:02:13.200> so<00:02:13.470> she<00:02:13.860> won't 00:02:14.090 --> 00:02:14.100 align:start position:0% small accidents last minute so she won't 00:02:14.100 --> 00:02:15.680 align:start position:0% small accidents last minute so she won't make<00:02:14.280> it<00:02:14.460> this<00:02:14.580> time 00:02:15.680 --> 00:02:15.690 align:start position:0% make it this time 00:02:15.690 --> 00:02:17.510 align:start position:0% make it this time phonemic<00:02:16.260> we'll<00:02:16.620> talk<00:02:16.800> about<00:02:17.010> al-qaeda's 00:02:17.510 --> 00:02:17.520 align:start position:0% phonemic we'll talk about al-qaeda's 00:02:17.520 --> 00:02:20.090 align:start position:0% phonemic we'll talk about al-qaeda's need<00:02:17.730> for<00:02:17.910> a<00:02:17.940> p2p<00:02:18.530> Mike<00:02:19.530> and<00:02:19.710> Molly<00:02:19.890> from 00:02:20.090 --> 00:02:20.100 align:start position:0% need for a p2p Mike and Molly from 00:02:20.100 --> 00:02:21.950 align:start position:0% need for a p2p Mike and Molly from protocol<00:02:20.430> lapse<00:02:20.640> will<00:02:20.880> will<00:02:21.210> cover<00:02:21.510> lifting 00:02:21.950 --> 00:02:21.960 align:start position:0% protocol lapse will will cover lifting 00:02:21.960 --> 00:02:24.200 align:start position:0% protocol lapse will will cover lifting to<00:02:22.050> be<00:02:22.170> entire<00:02:22.590> many<00:02:22.860> ipfs<00:02:23.550> and<00:02:23.820> I<00:02:23.850> know<00:02:23.910> there 00:02:24.200 --> 00:02:24.210 align:start position:0% to be entire many ipfs and I know there 00:02:24.210 --> 00:02:25.550 align:start position:0% to be entire many ipfs and I know there are<00:02:24.270> like<00:02:24.390> couple<00:02:24.720> of<00:02:24.810> people<00:02:24.990> that<00:02:25.140> email 00:02:25.550 --> 00:02:25.560 align:start position:0% are like couple of people that email 00:02:25.560 --> 00:02:27.710 align:start position:0% are like couple of people that email last<00:02:25.770> minute<00:02:26.190> and<00:02:26.400> like<00:02:26.670> what<00:02:26.940> to<00:02:27.090> do<00:02:27.420> a<00:02:27.450> shirt 00:02:27.710 --> 00:02:27.720 align:start position:0% last minute and like what to do a shirt 00:02:27.720 --> 00:02:29.810 align:start position:0% last minute and like what to do a shirt like<00:02:27.750> to<00:02:28.050> talk<00:02:28.320> like<00:02:28.920> we<00:02:29.160> should<00:02:29.430> have<00:02:29.610> time 00:02:29.810 --> 00:02:29.820 align:start position:0% like to talk like we should have time 00:02:29.820 --> 00:02:31.340 align:start position:0% like to talk like we should have time for<00:02:29.850> that<00:02:30.240> like<00:02:30.450> five<00:02:30.690> or<00:02:30.870> ten<00:02:31.050> minutes 00:02:31.340 --> 00:02:31.350 align:start position:0% for that like five or ten minutes 00:02:31.350 --> 00:02:32.900 align:start position:0% for that like five or ten minutes depending<00:02:31.470> on<00:02:31.740> how<00:02:31.800> many<00:02:32.010> of<00:02:32.310> you<00:02:32.550> are<00:02:32.700> here 00:02:32.900 --> 00:02:32.910 align:start position:0% depending on how many of you are here 00:02:32.910 --> 00:02:35.570 align:start position:0% depending on how many of you are here please<00:02:33.420> raise<00:02:33.630> your<00:02:33.660> heads<00:02:34.100> okay<00:02:35.100> a<00:02:35.370> piece 00:02:35.570 --> 00:02:35.580 align:start position:0% please raise your heads okay a piece 00:02:35.580 --> 00:02:37.400 align:start position:0% please raise your heads okay a piece here<00:02:35.910> that's<00:02:36.300> perfect<00:02:36.600> and<00:02:36.990> I<00:02:37.080> know<00:02:37.110> that 00:02:37.400 --> 00:02:37.410 align:start position:0% here that's perfect and I know that 00:02:37.410 --> 00:02:38.930 align:start position:0% here that's perfect and I know that there's<00:02:37.680> two<00:02:37.890> people<00:02:38.160> that<00:02:38.430> are<00:02:38.610> gonna<00:02:38.730> arrive 00:02:38.930 --> 00:02:38.940 align:start position:0% there's two people that are gonna arrive 00:02:38.940 --> 00:02:41.600 align:start position:0% there's two people that are gonna arrive soon<00:02:39.300> so<00:02:39.810> like<00:02:39.990> like<00:02:40.680> if<00:02:40.920> we<00:02:41.100> if<00:02:41.280> we<00:02:41.310> stay<00:02:41.580> on 00:02:41.600 --> 00:02:41.610 align:start position:0% soon so like like if we if we stay on 00:02:41.610 --> 00:02:43.310 align:start position:0% soon so like like if we if we stay on schedule<00:02:41.850> like<00:02:42.600> we're<00:02:42.780> going<00:02:42.959> to<00:02:42.990> be<00:02:43.080> able<00:02:43.170> to 00:02:43.310 --> 00:02:43.320 align:start position:0% schedule like we're going to be able to 00:02:43.320 --> 00:02:44.750 align:start position:0% schedule like we're going to be able to talk<00:02:43.500> about<00:02:43.590> all<00:02:43.980> of<00:02:44.010> this<00:02:44.250> we're<00:02:44.520> just<00:02:44.640> going 00:02:44.750 --> 00:02:44.760 align:start position:0% talk about all of this we're just going 00:02:44.760 --> 00:02:46.970 align:start position:0% talk about all of this we're just going to<00:02:44.790> be<00:02:44.880> variable<00:02:45.270> and<00:02:46.200> then<00:02:46.470> this<00:02:46.620> fashion 00:02:46.970 --> 00:02:46.980 align:start position:0% to be variable and then this fashion 00:02:46.980 --> 00:02:48.530 align:start position:0% to be variable and then this fashion looks<00:02:47.220> we<00:02:47.459> have<00:02:47.550> like<00:02:47.760> you<00:02:47.970> know<00:02:48.060> a<00:02:48.180> bunch<00:02:48.420> of 00:02:48.530 --> 00:02:48.540 align:start position:0% looks we have like you know a bunch of 00:02:48.540 --> 00:02:50.030 align:start position:0% looks we have like you know a bunch of people<00:02:48.600> we're<00:02:49.290> going<00:02:49.410> to<00:02:49.470> be<00:02:49.530> taking<00:02:49.830> notes 00:02:50.030 --> 00:02:50.040 align:start position:0% people we're going to be taking notes 00:02:50.040 --> 00:02:51.560 align:start position:0% people we're going to be taking notes during<00:02:50.310> the<00:02:50.610> during<00:02:50.970> hearing<00:02:51.450> care 00:02:51.560 --> 00:02:51.570 align:start position:0% during the during hearing care 00:02:51.570 --> 00:02:53.270 align:start position:0% during the during hearing care presentations<00:02:52.140> and<00:02:52.320> like<00:02:52.530> it<00:02:52.770> will<00:02:52.950> be<00:02:53.040> great 00:02:53.270 --> 00:02:53.280 align:start position:0% presentations and like it will be great 00:02:53.280 --> 00:02:55.520 align:start position:0% presentations and like it will be great for<00:02:53.459> you<00:02:53.610> if<00:02:54.150> you're<00:02:54.630> presenting<00:02:54.870> you<00:02:55.230> also 00:02:55.520 --> 00:02:55.530 align:start position:0% for you if you're presenting you also 00:02:55.530 --> 00:02:57.320 align:start position:0% for you if you're presenting you also briefly<00:02:55.950> mentioned<00:02:56.040> like<00:02:56.670> what<00:02:57.030> do<00:02:57.239> you<00:02:57.270> think 00:02:57.320 --> 00:02:57.330 align:start position:0% briefly mentioned like what do you think 00:02:57.330 --> 00:02:59.150 align:start position:0% briefly mentioned like what do you think the<00:02:57.600> biggest<00:02:57.840> challenges<00:02:58.230> are<00:02:58.440> for<00:02:58.709> us<00:02:58.800> to<00:02:58.980> put 00:02:59.150 --> 00:02:59.160 align:start position:0% the biggest challenges are for us to put 00:02:59.160 --> 00:03:01.699 align:start position:0% the biggest challenges are for us to put this<00:02:59.280> forward<00:02:59.580> and<00:03:00.080> would<00:03:01.080> definitely<00:03:01.590> be 00:03:01.699 --> 00:03:01.709 align:start position:0% this forward and would definitely be 00:03:01.709 --> 00:03:03.380 align:start position:0% this forward and would definitely be great<00:03:01.950> to<00:03:02.100> map<00:03:02.250> this<00:03:02.400> out<00:03:02.550> in<00:03:02.820> the<00:03:02.910> discussion 00:03:03.380 --> 00:03:03.390 align:start position:0% great to map this out in the discussion 00:03:03.390 --> 00:03:04.910 align:start position:0% great to map this out in the discussion part<00:03:03.570> like<00:03:03.840> what<00:03:04.020> the<00:03:04.140> challenges<00:03:04.500> are<00:03:04.680> and 00:03:04.910 --> 00:03:04.920 align:start position:0% part like what the challenges are and 00:03:04.920 --> 00:03:06.560 align:start position:0% part like what the challenges are and what<00:03:05.340> the<00:03:05.459> action<00:03:05.790> blocks<00:03:06.030> we<00:03:06.330> have<00:03:06.360> some 00:03:06.560 --> 00:03:06.570 align:start position:0% what the action blocks we have some 00:03:06.570 --> 00:03:08.240 align:start position:0% what the action blocks we have some ideas<00:03:06.930> about<00:03:07.170> that<00:03:07.440> we've<00:03:07.709> been<00:03:07.830> working<00:03:08.010> on 00:03:08.240 --> 00:03:08.250 align:start position:0% ideas about that we've been working on 00:03:08.250 --> 00:03:10.790 align:start position:0% ideas about that we've been working on something<00:03:08.520> we<00:03:08.880> all<00:03:09.030> need<00:03:09.180> to<00:03:09.209> do<00:03:09.570> on<00:03:09.870> that<00:03:10.110> like 00:03:10.790 --> 00:03:10.800 align:start position:0% something we all need to do on that like 00:03:10.800 --> 00:03:13.310 align:start position:0% something we all need to do on that like before<00:03:11.070> we<00:03:11.459> start<00:03:11.760> so<00:03:11.970> you<00:03:12.600> know<00:03:12.750> we<00:03:12.959> really 00:03:13.310 --> 00:03:13.320 align:start position:0% before we start so you know we really 00:03:13.320 --> 00:03:15.080 align:start position:0% before we start so you know we really have<00:03:13.440> high<00:03:13.709> hopes<00:03:13.920> for<00:03:14.100> the<00:03:14.489> discussion<00:03:14.940> part 00:03:15.080 --> 00:03:15.090 align:start position:0% have high hopes for the discussion part 00:03:15.090 --> 00:03:18.020 align:start position:0% have high hopes for the discussion part but<00:03:15.810> to<00:03:15.870> keep<00:03:16.140> things<00:03:16.200> off<00:03:16.650> we<00:03:17.100> have<00:03:17.250> one's<00:03:17.940> own 00:03:18.020 --> 00:03:18.030 align:start position:0% but to keep things off we have one's own 00:03:18.030 --> 00:03:20.210 align:start position:0% but to keep things off we have one's own exterior<00:03:18.720> too<00:03:18.900> like<00:03:19.110> probably<00:03:19.680> remind 00:03:20.210 --> 00:03:20.220 align:start position:0% exterior too like probably remind 00:03:20.220 --> 00:03:23.479 align:start position:0% exterior too like probably remind everybody<00:03:20.459> why<00:03:20.880> this<00:03:20.940> matters<00:03:21.470> and<00:03:22.470> also<00:03:22.920> well 00:03:23.479 --> 00:03:23.489 align:start position:0% everybody why this matters and also well 00:03:23.489 --> 00:03:25.130 align:start position:0% everybody why this matters and also well I<00:03:23.519> would<00:03:24.150> actually<00:03:24.269> actually<00:03:24.510> do<00:03:24.720> kind<00:03:24.930> of<00:03:25.019> a 00:03:25.130 --> 00:03:25.140 align:start position:0% I would actually actually do kind of a 00:03:25.140 --> 00:03:29.420 align:start position:0% I would actually actually do kind of a kind<00:03:25.380> of<00:03:25.470> a<00:03:25.560> brief<00:03:25.769> introduction<00:03:26.280> of<00:03:28.100> the<00:03:29.100> idea 00:03:29.420 --> 00:03:29.430 align:start position:0% kind of a brief introduction of the idea 00:03:29.430 --> 00:03:31.490 align:start position:0% kind of a brief introduction of the idea of<00:03:29.640> p2p<00:03:29.940> and<00:03:30.269> maybe<00:03:30.480> maybe<00:03:31.019> a<00:03:31.110> better<00:03:31.320> way<00:03:31.470> to 00:03:31.490 --> 00:03:31.500 align:start position:0% of p2p and maybe maybe a better way to 00:03:31.500 --> 00:03:32.960 align:start position:0% of p2p and maybe maybe a better way to do<00:03:31.799> this<00:03:31.830> I<00:03:32.010> was<00:03:32.100> think<00:03:32.220> about<00:03:32.250> this<00:03:32.430> when<00:03:32.580> you 00:03:32.960 --> 00:03:32.970 align:start position:0% do this I was think about this when you 00:03:32.970 --> 00:03:34.580 align:start position:0% do this I was think about this when you mention<00:03:33.269> it<00:03:33.360> I<00:03:33.540> would<00:03:34.080> like<00:03:34.260> to<00:03:34.380> kind<00:03:34.500> of 00:03:34.580 --> 00:03:34.590 align:start position:0% mention it I would like to kind of 00:03:34.590 --> 00:03:35.990 align:start position:0% mention it I would like to kind of understand<00:03:35.040> what<00:03:35.190> everybody<00:03:35.519> thinks<00:03:35.850> that 00:03:35.990 --> 00:03:36.000 align:start position:0% understand what everybody thinks that 00:03:36.000 --> 00:03:38.360 align:start position:0% understand what everybody thinks that term<00:03:36.510> means<00:03:36.870> what<00:03:37.560> is<00:03:37.650> it<00:03:37.769> what<00:03:38.010> does<00:03:38.070> it<00:03:38.190> mean 00:03:38.360 --> 00:03:38.370 align:start position:0% term means what is it what does it mean 00:03:38.370 --> 00:03:39.090 align:start position:0% term means what is it what does it mean for<00:03:38.610> everybody 00:03:39.090 --> 00:03:39.100 align:start position:0% for everybody 00:03:39.100 --> 00:03:41.490 align:start position:0% for everybody it's<00:03:39.220> here<00:03:39.460> because<00:03:40.360> we<00:03:40.930> have<00:03:41.050> a<00:03:41.080> pretty 00:03:41.490 --> 00:03:41.500 align:start position:0% it's here because we have a pretty 00:03:41.500 --> 00:03:43.470 align:start position:0% it's here because we have a pretty diverse<00:03:41.680> range<00:03:42.190> of<00:03:42.370> projects<00:03:42.910> doing<00:03:43.090> a<00:03:43.270> lot<00:03:43.390> of 00:03:43.470 --> 00:03:43.480 align:start position:0% diverse range of projects doing a lot of 00:03:43.480 --> 00:03:45.930 align:start position:0% diverse range of projects doing a lot of different<00:03:43.750> stuff<00:03:43.990> in<00:03:44.320> it<00:03:44.440> you<00:03:44.710> know<00:03:45.580> I<00:03:45.820> think 00:03:45.930 --> 00:03:45.940 align:start position:0% different stuff in it you know I think 00:03:45.940 --> 00:03:48.030 align:start position:0% different stuff in it you know I think there<00:03:46.210> is<00:03:46.300> a<00:03:46.330> common<00:03:46.600> cause<00:03:46.960> here<00:03:47.380> and<00:03:47.620> maybe 00:03:48.030 --> 00:03:48.040 align:start position:0% there is a common cause here and maybe 00:03:48.040 --> 00:03:49.590 align:start position:0% there is a common cause here and maybe the<00:03:48.160> reason<00:03:48.310> this<00:03:48.550> room<00:03:48.760> is<00:03:48.880> kind<00:03:49.120> of<00:03:49.180> distinct 00:03:49.590 --> 00:03:49.600 align:start position:0% the reason this room is kind of distinct 00:03:49.600 --> 00:03:51.270 align:start position:0% the reason this room is kind of distinct is<00:03:49.810> because<00:03:50.110> in<00:03:50.290> some<00:03:50.500> respects<00:03:50.890> some<00:03:51.010> of<00:03:51.160> the 00:03:51.270 --> 00:03:51.280 align:start position:0% is because in some respects some of the 00:03:51.280 --> 00:03:52.860 align:start position:0% is because in some respects some of the people<00:03:51.520> here<00:03:51.760> are<00:03:51.910> working<00:03:52.030> on<00:03:52.300> things<00:03:52.510> that 00:03:52.860 --> 00:03:52.870 align:start position:0% people here are working on things that 00:03:52.870 --> 00:03:55.410 align:start position:0% people here are working on things that can<00:03:53.770> work<00:03:53.890> in<00:03:53.950> conjunction<00:03:54.220> with<00:03:54.580> a<00:03:54.730> theory<00:03:55.030> or 00:03:55.410 --> 00:03:55.420 align:start position:0% can work in conjunction with a theory or 00:03:55.420 --> 00:03:57.930 align:start position:0% can work in conjunction with a theory or quite<00:03:55.780> separate<00:03:56.170> from<00:03:56.200> it<00:03:56.530> or<00:03:57.310> the<00:03:57.460> projects 00:03:57.930 --> 00:03:57.940 align:start position:0% quite separate from it or the projects 00:03:57.940 --> 00:04:01.470 align:start position:0% quite separate from it or the projects like<00:03:58.090> that<00:03:58.680> so<00:03:59.790> maybe<00:04:00.790> instead<00:04:01.000> of<00:04:01.300> giving 00:04:01.470 --> 00:04:01.480 align:start position:0% like that so maybe instead of giving 00:04:01.480 --> 00:04:03.570 align:start position:0% like that so maybe instead of giving kind<00:04:01.720> of<00:04:01.780> introduction<00:04:02.140> that's<00:04:02.500> stating<00:04:03.490> what 00:04:03.570 --> 00:04:03.580 align:start position:0% kind of introduction that's stating what 00:04:03.580 --> 00:04:05.190 align:start position:0% kind of introduction that's stating what PD<00:04:03.820> is<00:04:04.060> I'd<00:04:04.240> like<00:04:04.300> to<00:04:04.450> hear<00:04:04.540> from<00:04:04.660> you<00:04:04.810> guys<00:04:04.960> in 00:04:05.190 --> 00:04:05.200 align:start position:0% PD is I'd like to hear from you guys in 00:04:05.200 --> 00:04:07.650 align:start position:0% PD is I'd like to hear from you guys in here<00:04:05.350> what<00:04:05.560> you<00:04:05.590> think<00:04:05.890> it<00:04:05.980> is<00:04:06.420> I'm<00:04:07.420> going<00:04:07.600> to 00:04:07.650 --> 00:04:07.660 align:start position:0% here what you think it is I'm going to 00:04:07.660 --> 00:04:09.210 align:start position:0% here what you think it is I'm going to I've<00:04:07.750> been<00:04:07.810> working<00:04:08.170> with<00:04:08.200> a<00:04:08.470> lot<00:04:08.680> of<00:04:08.710> projects 00:04:09.210 --> 00:04:09.220 align:start position:0% I've been working with a lot of projects 00:04:09.220 --> 00:04:10.740 align:start position:0% I've been working with a lot of projects in<00:04:09.250> this<00:04:09.370> space<00:04:09.640> currently<00:04:10.270> we<00:04:10.420> have<00:04:10.450> a<00:04:10.540> wire 00:04:10.740 --> 00:04:10.750 align:start position:0% in this space currently we have a wire 00:04:10.750 --> 00:04:15.480 align:start position:0% in this space currently we have a wire line<00:04:11.160> and<00:04:12.160> for<00:04:12.880> me<00:04:12.970> a<00:04:13.000> p2p<00:04:13.420> is<00:04:13.930> about<00:04:14.400> you<00:04:15.400> know 00:04:15.480 --> 00:04:15.490 align:start position:0% line and for me a p2p is about you know 00:04:15.490 --> 00:04:16.860 align:start position:0% line and for me a p2p is about you know kind<00:04:15.640> of<00:04:15.730> a<00:04:15.850> kind<00:04:16.120> of<00:04:16.150> a<00:04:16.270> way<00:04:16.420> to<00:04:16.480> get 00:04:16.860 --> 00:04:16.870 align:start position:0% kind of a kind of a way to get 00:04:16.870 --> 00:04:19.110 align:start position:0% kind of a kind of a way to get sovereignty<00:04:17.410> over<00:04:17.739> over<00:04:18.610> the<00:04:18.850> sort<00:04:19.090> of 00:04:19.110 --> 00:04:19.120 align:start position:0% sovereignty over over the sort of 00:04:19.120 --> 00:04:20.420 align:start position:0% sovereignty over over the sort of digital<00:04:19.270> world<00:04:19.600> that<00:04:19.690> we're<00:04:19.870> creating 00:04:20.420 --> 00:04:20.430 align:start position:0% digital world that we're creating 00:04:20.430 --> 00:04:22.350 align:start position:0% digital world that we're creating anywhere<00:04:21.430> we<00:04:21.640> don't<00:04:21.790> have<00:04:22.030> a<00:04:22.060> lot<00:04:22.330> of 00:04:22.350 --> 00:04:22.360 align:start position:0% anywhere we don't have a lot of 00:04:22.360 --> 00:04:24.690 align:start position:0% anywhere we don't have a lot of intermediates<00:04:22.900> or<00:04:23.200> any<00:04:23.380> impossible<00:04:24.040> you<00:04:24.490> can 00:04:24.690 --> 00:04:24.700 align:start position:0% intermediates or any impossible you can 00:04:24.700 --> 00:04:25.770 align:start position:0% intermediates or any impossible you can just<00:04:24.850> directly<00:04:25.150> connect<00:04:25.420> with<00:04:25.510> the<00:04:25.570> things 00:04:25.770 --> 00:04:25.780 align:start position:0% just directly connect with the things 00:04:25.780 --> 00:04:28.140 align:start position:0% just directly connect with the things that<00:04:25.870> we<00:04:26.080> care<00:04:26.560> about<00:04:26.620> so<00:04:27.070> where<00:04:27.790> would<00:04:27.850> I<00:04:27.940> move 00:04:28.140 --> 00:04:28.150 align:start position:0% that we care about so where would I move 00:04:28.150 --> 00:04:30.780 align:start position:0% that we care about so where would I move from<00:04:28.210> here<00:04:28.420> one<00:04:28.660> direction<00:04:29.520> how<00:04:30.520> would<00:04:30.610> you 00:04:30.780 --> 00:04:30.790 align:start position:0% from here one direction how would you 00:04:30.790 --> 00:04:32.420 align:start position:0% from here one direction how would you sir 00:04:32.420 --> 00:04:32.430 align:start position:0% sir 00:04:32.430 --> 00:04:35.719 align:start position:0% sir just<00:04:32.610> myself<00:04:32.850> and<00:04:33.150> saying<00:04:33.389> okay<00:04:33.930> with<00:04:34.050> you<00:04:34.729> and 00:04:35.719 --> 00:04:35.729 align:start position:0% just myself and saying okay with you and 00:04:35.729 --> 00:04:40.249 align:start position:0% just myself and saying okay with you and peer-to-peer<00:04:36.620> you<00:04:37.729> say<00:04:38.990> whatever<00:04:39.990> you<00:04:40.169> like 00:04:40.249 --> 00:04:40.259 align:start position:0% peer-to-peer you say whatever you like 00:04:40.259 --> 00:04:45.620 align:start position:0% peer-to-peer you say whatever you like to<00:04:42.620> our<00:04:43.620> device<00:04:43.979> and<00:04:44.370> being<00:04:45.180> able<00:04:45.300> to<00:04:45.419> talk 00:04:45.620 --> 00:04:45.630 align:start position:0% to our device and being able to talk 00:04:45.630 --> 00:04:47.510 align:start position:0% to our device and being able to talk directly<00:04:46.050> with<00:04:46.139> each<00:04:46.410> other<00:04:46.650> and<00:04:46.949> figuring 00:04:47.510 --> 00:04:47.520 align:start position:0% directly with each other and figuring 00:04:47.520 --> 00:04:52.390 align:start position:0% directly with each other and figuring out<00:04:49.400> that<00:04:50.400> having<00:04:50.669> some<00:04:50.940> utility<00:04:51.419> for<00:04:51.660> us 00:04:52.390 --> 00:04:52.400 align:start position:0% out that having some utility for us 00:04:52.400 --> 00:04:54.080 align:start position:0% out that having some utility for us what's<00:04:53.400> the<00:04:53.490> project<00:04:53.639> through<00:04:53.880> orientation 00:04:54.080 --> 00:04:54.090 align:start position:0% what's the project through orientation 00:04:54.090 --> 00:04:59.350 align:start position:0% what's the project through orientation and<00:04:54.720> coordination<00:04:55.580> through<00:04:56.580> boxes<00:04:57.000> coming 00:04:59.350 --> 00:04:59.360 align:start position:0% 00:04:59.360 --> 00:05:02.869 align:start position:0% remember<00:05:00.360> Texas<00:05:01.039> organizers<00:05:02.039> identity<00:05:02.580> and 00:05:02.869 --> 00:05:02.879 align:start position:0% remember Texas organizers identity and 00:05:02.879 --> 00:05:07.159 align:start position:0% remember Texas organizers identity and pitch<00:05:03.629> me<00:05:03.779> in<00:05:03.840> Texas<00:05:04.069> audiences<00:05:05.069> for<00:05:05.849> pizza<00:05:06.300> so 00:05:07.159 --> 00:05:07.169 align:start position:0% pitch me in Texas audiences for pizza so 00:05:07.169 --> 00:05:21.350 align:start position:0% pitch me in Texas audiences for pizza so much<00:05:17.060> here<00:05:19.340> it's<00:05:20.340> like<00:05:20.490> BitTorrent<00:05:21.240> and 00:05:21.350 --> 00:05:21.360 align:start position:0% much here it's like BitTorrent and 00:05:21.360 --> 00:05:35.640 align:start position:0% much here it's like BitTorrent and Napster<00:05:21.779> but<00:05:22.080> like<00:05:22.370> next<00:05:23.370> phase 00:05:35.640 --> 00:05:35.650 align:start position:0% 00:05:35.650 --> 00:05:40.650 align:start position:0% I<00:05:36.600> think<00:05:37.600> of<00:05:37.720> hey<00:05:38.290> Felix<00:05:38.860> I<00:05:39.220> worked<00:05:39.850> on<00:05:39.970> deputy 00:05:40.650 --> 00:05:40.660 align:start position:0% I think of hey Felix I worked on deputy 00:05:40.660 --> 00:05:47.300 align:start position:0% I think of hey Felix I worked on deputy for<00:05:40.930> yet<00:05:44.010> mate<00:05:45.010> Green<00:05:45.250> I<00:05:45.520> work<00:05:45.820> on<00:05:46.060> lived<00:05:46.570> to<00:05:46.750> be 00:05:47.300 --> 00:05:47.310 align:start position:0% for yet mate Green I work on lived to be 00:05:47.310 --> 00:05:49.740 align:start position:0% for yet mate Green I work on lived to be status<00:05:48.310> and 00:05:49.740 --> 00:05:49.750 align:start position:0% status and 00:05:49.750 --> 00:05:51.750 align:start position:0% status and beer<00:05:50.260> is<00:05:50.410> anything<00:05:51.190> just<00:05:51.400> sort<00:05:51.550> of<00:05:51.610> the 00:05:51.750 --> 00:05:51.760 align:start position:0% beer is anything just sort of the 00:05:51.760 --> 00:05:57.630 align:start position:0% beer is anything just sort of the centralized<00:05:52.210> infrastructure<00:05:55.680> and<00:05:56.680> working 00:05:57.630 --> 00:05:57.640 align:start position:0% centralized infrastructure and working 00:05:57.640 --> 00:06:27.170 align:start position:0% centralized infrastructure and working on<00:05:57.760> that<00:05:57.880> identity<00:05:58.660> that<00:05:59.620> IT<00:06:00.520> projects<00:06:00.880> so 00:06:27.170 --> 00:06:27.180 align:start position:0% 00:06:27.180 --> 00:06:35.000 align:start position:0% research<00:06:28.180> per<00:06:28.480> Connie<00:06:28.840> just<00:06:29.800> exploring<00:06:31.290> no 00:06:35.000 --> 00:06:35.010 align:start position:0% 00:06:35.010 --> 00:06:37.830 align:start position:0% algorithm<00:06:36.010> founders<00:06:36.670> of<00:06:36.880> the<00:06:37.000> context<00:06:37.510> are 00:06:37.830 --> 00:06:37.840 align:start position:0% algorithm founders of the context are 00:06:37.840 --> 00:06:39.910 align:start position:0% algorithm founders of the context are interested<00:06:38.410> in 00:06:39.910 --> 00:06:39.920 align:start position:0% interested in 00:06:39.920 --> 00:06:48.410 align:start position:0% interested in -<00:06:46.070> something<00:06:47.070> like<00:06:47.250> hope<00:06:47.640> it<00:06:47.790> was<00:06:47.910> hard<00:06:48.150> what 00:06:48.410 --> 00:06:48.420 align:start position:0% - something like hope it was hard what 00:06:48.420 --> 00:06:59.620 align:start position:0% - something like hope it was hard what for 00:06:59.620 --> 00:06:59.630 align:start position:0% 00:06:59.630 --> 00:07:06.320 align:start position:0% really 00:07:06.320 --> 00:07:06.330 align:start position:0% 00:07:06.330 --> 00:07:12.730 align:start position:0% we<00:07:07.590> think<00:07:08.590> software 00:07:12.730 --> 00:07:12.740 align:start position:0% 00:07:12.740 --> 00:07:16.370 align:start position:0% Hey 00:07:16.370 --> 00:07:16.380 align:start position:0% 00:07:16.380 --> 00:07:18.350 align:start position:0% Gerard<00:07:17.070> link<00:07:17.340> that<00:07:17.580> I<00:07:17.640> have<00:07:17.670> is<00:07:17.910> a<00:07:17.940> company 00:07:18.350 --> 00:07:18.360 align:start position:0% Gerard link that I have is a company 00:07:18.360 --> 00:07:19.490 align:start position:0% Gerard link that I have is a company over<00:07:18.570> a<00:07:18.660> block<00:07:18.900> we<00:07:19.170> were<00:07:19.290> building 00:07:19.490 --> 00:07:19.500 align:start position:0% over a block we were building 00:07:19.500 --> 00:07:34.320 align:start position:0% over a block we were building decentralize<00:07:20.400> get<00:07:20.850> out<00:07:20.970> the<00:07:21.210> place 00:07:34.320 --> 00:07:34.330 align:start position:0% 00:07:34.330 --> 00:07:36.000 align:start position:0% Engineering 00:07:36.000 --> 00:07:36.010 align:start position:0% Engineering 00:07:36.010 --> 00:07:39.020 align:start position:0% Engineering [Music] 00:07:39.020 --> 00:07:39.030 align:start position:0% [Music] 00:07:39.030 --> 00:07:42.860 align:start position:0% [Music] I<00:07:39.060> am<00:07:39.840> prem<00:07:40.080> KO<00:07:40.290> I'm<00:07:40.500> the<00:07:40.710> researcher<00:07:41.370> it<00:07:41.910> I'm 00:07:42.860 --> 00:07:42.870 align:start position:0% I am prem KO I'm the researcher it I'm 00:07:42.870 --> 00:07:45.800 align:start position:0% I am prem KO I'm the researcher it I'm Renko<00:07:43.680> I'm<00:07:43.860> a<00:07:43.980> researcher<00:07:44.520> of<00:07:44.550> zero<00:07:45.210> X<00:07:45.420> and 00:07:45.800 --> 00:07:45.810 align:start position:0% Renko I'm a researcher of zero X and 00:07:45.810 --> 00:07:48.500 align:start position:0% Renko I'm a researcher of zero X and looking<00:07:46.680> into<00:07:47.010> decentralized<00:07:48.000> the<00:07:48.210> chains 00:07:48.500 --> 00:07:48.510 align:start position:0% looking into decentralized the chains 00:07:48.510 --> 00:07:50.960 align:start position:0% looking into decentralized the chains and<00:07:48.840> nearly<00:07:49.110> beers<00:07:49.460> importance<00:07:50.460> of<00:07:50.580> Roswell's 00:07:50.960 --> 00:07:50.970 align:start position:0% and nearly beers importance of Roswell's 00:07:50.970 --> 00:07:57.900 align:start position:0% and nearly beers importance of Roswell's permissionless<00:07:51.780> and<00:07:52.290> inherently<00:07:52.890> Brazilian 00:07:57.900 --> 00:07:57.910 align:start position:0% 00:07:57.910 --> 00:08:02.730 align:start position:0% [Music] 00:08:02.730 --> 00:08:02.740 align:start position:0% 00:08:02.740 --> 00:08:06.020 align:start position:0% I<00:08:02.770> am<00:08:03.460> draw 00:08:06.020 --> 00:08:06.030 align:start position:0% 00:08:06.030 --> 00:08:09.380 align:start position:0% stand<00:08:06.660> up<00:08:06.990> so<00:08:07.560> we<00:08:07.680> can<00:08:07.830> see<00:08:08.010> you<00:08:08.220> I<00:08:08.430> have<00:08:09.060> Chuck 00:08:09.380 --> 00:08:09.390 align:start position:0% stand up so we can see you I have Chuck 00:08:09.390 --> 00:08:12.890 align:start position:0% stand up so we can see you I have Chuck I<00:08:09.800> stay<00:08:10.800> aside<00:08:11.280> when<00:08:11.820> you<00:08:11.940> work<00:08:12.090> on<00:08:12.270> a<00:08:12.540> small 00:08:12.890 --> 00:08:12.900 align:start position:0% I stay aside when you work on a small 00:08:12.900 --> 00:08:16.760 align:start position:0% I stay aside when you work on a small country<00:08:13.110> packages<00:08:13.740> but<00:08:14.660> disappear<00:08:15.660> this 00:08:16.760 --> 00:08:16.770 align:start position:0% country packages but disappear this 00:08:16.770 --> 00:08:35.430 align:start position:0% country packages but disappear this I 00:08:35.430 --> 00:08:35.440 align:start position:0% 00:08:35.440 --> 00:08:45.040 align:start position:0% [Music] 00:08:45.040 --> 00:08:45.050 align:start position:0% 00:08:45.050 --> 00:08:50.220 align:start position:0% [Music] 00:08:50.220 --> 00:08:50.230 align:start position:0% 00:08:50.230 --> 00:08:57.970 align:start position:0% so<00:08:51.230> they<00:08:51.500> can<00:08:51.860> accommodate<00:08:52.480> up 00:08:57.970 --> 00:08:57.980 align:start position:0% 00:08:57.980 --> 00:09:05.510 align:start position:0% I'm<00:08:58.490> Danny<00:08:58.790> from<00:08:58.910> box 00:09:05.510 --> 00:09:05.520 align:start position:0% 00:09:05.520 --> 00:09:11.310 align:start position:0% your<00:09:06.520> voice 00:09:11.310 --> 00:09:11.320 align:start position:0% 00:09:11.320 --> 00:09:18.699 align:start position:0% by<00:09:11.860> researcher 00:09:18.699 --> 00:09:18.709 align:start position:0% 00:09:18.709 --> 00:09:23.869 align:start position:0% stop 00:09:23.869 --> 00:09:23.879 align:start position:0% 00:09:23.879 --> 00:09:27.420 align:start position:0% I'm<00:09:24.879> Matt<00:09:25.180> I'm<00:09:25.480> from<00:09:25.809> pinata<00:09:26.290> to<00:09:26.680> do<00:09:26.829> idea 00:09:27.420 --> 00:09:27.430 align:start position:0% I'm Matt I'm from pinata to do idea 00:09:27.430 --> 00:09:30.449 align:start position:0% I'm Matt I'm from pinata to do idea testing<00:09:27.639> for<00:09:28.059> structuring<00:09:28.449> services<00:09:29.199> and<00:09:29.980> I'm 00:09:30.449 --> 00:09:30.459 align:start position:0% testing for structuring services and I'm 00:09:30.459 --> 00:09:32.160 align:start position:0% testing for structuring services and I'm here<00:09:30.490> to<00:09:31.209> see<00:09:31.389> kind<00:09:31.660> of<00:09:31.720> what<00:09:31.779> everybody<00:09:32.110> else 00:09:32.160 --> 00:09:32.170 align:start position:0% here to see kind of what everybody else 00:09:32.170 --> 00:09:43.740 align:start position:0% here to see kind of what everybody else is<00:09:39.839> here<00:09:40.839> apparently 00:09:43.740 --> 00:09:43.750 align:start position:0% 00:09:43.750 --> 00:09:47.610 align:start position:0% episode<00:09:44.500> Megan<00:09:45.279> X<00:09:45.430> 2005<00:09:46.120> 70%<00:09:46.990> of<00:09:47.199> the<00:09:47.319> internet 00:09:47.610 --> 00:09:47.620 align:start position:0% episode Megan X 2005 70% of the internet 00:09:47.620 --> 00:09:50.869 align:start position:0% episode Megan X 2005 70% of the internet was<00:09:47.920> peer-to-peer<00:09:48.189> and<00:09:49.029> I<00:09:49.209> was<00:09:49.389> like<00:09:49.540> 95% 00:09:50.869 --> 00:09:50.879 align:start position:0% was peer-to-peer and I was like 95% 00:09:50.879 --> 00:09:53.790 align:start position:0% was peer-to-peer and I was like 95% centralized<00:09:51.879> and<00:09:52.209> obviously<00:09:52.800> something 00:09:53.790 --> 00:09:53.800 align:start position:0% centralized and obviously something 00:09:53.800 --> 00:09:57.990 align:start position:0% centralized and obviously something changed<00:09:54.160> narratives<00:09:54.639> are<00:09:54.850> pack<00:09:55.149> animals 00:09:57.990 --> 00:09:58.000 align:start position:0% 00:09:58.000 --> 00:10:01.060 align:start position:0% [Music] 00:10:01.060 --> 00:10:01.070 align:start position:0% [Music] 00:10:01.070 --> 00:10:03.610 align:start position:0% [Music] Michael<00:10:01.640> also<00:10:01.990> like<00:10:02.990> Danny<00:10:03.200> from<00:10:03.410> three 00:10:03.610 --> 00:10:03.620 align:start position:0% Michael also like Danny from three 00:10:03.620 --> 00:10:14.560 align:start position:0% Michael also like Danny from three points<00:10:03.920> for<00:10:04.100> economists<00:10:04.490> repeated<00:10:04.910> data 00:10:14.560 --> 00:10:14.570 align:start position:0% 00:10:14.570 --> 00:10:19.550 align:start position:0% occasionally<00:10:16.880> some<00:10:17.880> developments<00:10:18.720> of<00:10:19.050> the 00:10:19.550 --> 00:10:19.560 align:start position:0% occasionally some developments of the 00:10:19.560 --> 00:10:23.990 align:start position:0% occasionally some developments of the different<00:10:19.950> body<00:10:20.130> of<00:10:20.279> the<00:10:20.430> system<00:10:22.430> yes<00:10:23.460> Chen 00:10:23.990 --> 00:10:24.000 align:start position:0% different body of the system yes Chen 00:10:24.000 --> 00:10:26.810 align:start position:0% different body of the system yes Chen security<00:10:24.570> must<00:10:25.080> be<00:10:25.290> interested<00:10:25.800> in 00:10:26.810 --> 00:10:26.820 align:start position:0% security must be interested in 00:10:26.820 --> 00:10:42.190 align:start position:0% security must be interested in attack<00:10:28.910> like 00:10:42.190 --> 00:10:42.200 align:start position:0% 00:10:42.200 --> 00:10:46.760 align:start position:0% I 00:10:46.760 --> 00:10:46.770 align:start position:0% 00:10:46.770 --> 00:10:50.070 align:start position:0% [Music] 00:10:50.070 --> 00:10:50.080 align:start position:0% 00:10:50.080 --> 00:10:55.670 align:start position:0% you<00:10:50.830> guys<00:10:50.980> need 00:10:55.670 --> 00:10:55.680 align:start position:0% 00:10:55.680 --> 00:10:59.639 align:start position:0% I'm<00:10:56.279> Bernardo<00:10:56.790> I<00:10:56.970> work<00:10:57.180> for<00:10:57.389> request<00:10:57.749> Network 00:10:59.639 --> 00:10:59.649 align:start position:0% I'm Bernardo I work for request Network 00:10:59.649 --> 00:11:05.160 align:start position:0% I'm Bernardo I work for request Network to<00:11:00.009> connect<00:11:00.579> our<00:11:00.759> notes<00:11:03.629> you<00:11:04.629> know<00:11:04.689> what<00:11:05.019> you 00:11:05.160 --> 00:11:05.170 align:start position:0% to connect our notes you know what you 00:11:05.170 --> 00:11:10.519 align:start position:0% to connect our notes you know what you both<00:11:05.410> up 00:11:10.519 --> 00:11:10.529 align:start position:0% 00:11:10.529 --> 00:11:14.089 align:start position:0% ah<00:11:11.059> hi<00:11:12.059> i'm<00:11:12.209> mike<00:11:12.479> elder<00:11:12.719> i'm<00:11:13.229> from<00:11:13.559> protocol 00:11:14.089 --> 00:11:14.099 align:start position:0% ah hi i'm mike elder i'm from protocol 00:11:14.099 --> 00:11:16.189 align:start position:0% ah hi i'm mike elder i'm from protocol labs<00:11:14.489> I<00:11:14.699> work<00:11:14.879> on<00:11:15.029> the<00:11:15.149> LinkedIn<00:11:15.479> in<00:11:15.719> project 00:11:16.189 --> 00:11:16.199 align:start position:0% labs I work on the LinkedIn in project 00:11:16.199 --> 00:11:18.699 align:start position:0% labs I work on the LinkedIn in project and<00:11:16.619> for<00:11:17.369> me<00:11:17.489> peer<00:11:17.699> to<00:11:17.819> peer<00:11:17.999> is<00:11:18.119> about 00:11:18.699 --> 00:11:18.709 align:start position:0% and for me peer to peer is about 00:11:18.709 --> 00:11:21.559 align:start position:0% and for me peer to peer is about eliminating<00:11:19.709> centralized<00:11:20.669> control<00:11:21.119> points 00:11:21.559 --> 00:11:21.569 align:start position:0% eliminating centralized control points 00:11:21.569 --> 00:11:24.319 align:start position:0% eliminating centralized control points in<00:11:21.809> network<00:11:22.469> so<00:11:22.739> that<00:11:22.769> you<00:11:23.039> have<00:11:23.219> no<00:11:24.089> single 00:11:24.319 --> 00:11:24.329 align:start position:0% in network so that you have no single 00:11:24.329 --> 00:11:27.799 align:start position:0% in network so that you have no single theories<00:11:24.779> more<00:11:24.989> powerful<00:11:26.419> by<00:11:27.419> the<00:11:27.449> way<00:11:27.599> we 00:11:27.799 --> 00:11:27.809 align:start position:0% theories more powerful by the way we 00:11:27.809 --> 00:11:35.079 align:start position:0% theories more powerful by the way we miss<00:11:32.839> you<00:11:33.839> guys<00:11:33.959> what<00:11:34.199> I<00:11:34.229> think<00:11:34.499> I<00:11:34.529> want<00:11:34.709> of 00:11:35.079 --> 00:11:35.089 align:start position:0% miss you guys what I think I want of 00:11:35.089 --> 00:11:37.129 align:start position:0% miss you guys what I think I want of course<00:11:36.089> is<00:11:36.239> just<00:11:36.329> basically<00:11:36.719> an<00:11:36.839> introduction 00:11:37.129 --> 00:11:37.139 align:start position:0% course is just basically an introduction 00:11:37.139 --> 00:11:39.349 align:start position:0% course is just basically an introduction and<00:11:37.409> also<00:11:37.499> like<00:11:37.889> what<00:11:38.519> I'm<00:11:38.939> interested<00:11:39.149> in 00:11:39.349 --> 00:11:39.359 align:start position:0% and also like what I'm interested in 00:11:39.359 --> 00:11:44.980 align:start position:0% and also like what I'm interested in what<00:11:39.719> is<00:11:40.879> so 00:11:44.980 --> 00:11:44.990 align:start position:0% 00:11:44.990 --> 00:11:47.170 align:start position:0% oh<00:11:45.020> hi<00:11:45.529> Molly<00:11:45.890> I<00:11:46.040> work<00:11:46.250> on<00:11:46.339> my<00:11:46.459> peoples<00:11:46.790> project 00:11:47.170 --> 00:11:47.180 align:start position:0% oh hi Molly I work on my peoples project 00:11:47.180 --> 00:11:51.670 align:start position:0% oh hi Molly I work on my peoples project man<00:11:47.470> each<00:11:48.470> key<00:11:48.920> to<00:11:49.310> me<00:11:49.520> is<00:11:49.790> about<00:11:50.630> making<00:11:51.440> a 00:11:51.670 --> 00:11:51.680 align:start position:0% man each key to me is about making a 00:11:51.680 --> 00:11:53.680 align:start position:0% man each key to me is about making a more<00:11:51.860> resilient<00:11:52.459> network<00:11:53.120> that<00:11:53.420> was<00:11:53.480> not 00:11:53.680 --> 00:11:53.690 align:start position:0% more resilient network that was not 00:11:53.690 --> 00:11:55.930 align:start position:0% more resilient network that was not connected<00:11:54.140> through<00:11:54.320> so<00:11:54.740> that<00:11:54.920> no<00:11:55.760> matter 00:11:55.930 --> 00:11:55.940 align:start position:0% connected through so that no matter 00:11:55.940 --> 00:11:57.639 align:start position:0% connected through so that no matter where<00:11:56.209> we<00:11:56.240> are<00:11:56.420> or<00:11:56.570> how<00:11:57.020> many<00:11:57.200> people<00:11:57.560> get 00:11:57.639 --> 00:11:57.649 align:start position:0% where we are or how many people get 00:11:57.649 --> 00:11:59.500 align:start position:0% where we are or how many people get together<00:11:57.830> we<00:11:58.250> can<00:11:58.430> still<00:11:58.730> make<00:11:59.060> use<00:11:59.209> of<00:11:59.240> the 00:11:59.500 --> 00:11:59.510 align:start position:0% together we can still make use of the 00:11:59.510 --> 00:12:01.180 align:start position:0% together we can still make use of the tools<00:11:59.630> we<00:11:59.959> really<00:12:00.320> care<00:12:00.500> about 00:12:01.180 --> 00:12:01.190 align:start position:0% tools we really care about 00:12:01.190 --> 00:12:03.000 align:start position:0% tools we really care about [Music] 00:12:03.000 --> 00:12:03.010 align:start position:0% [Music] 00:12:03.010 --> 00:12:05.920 align:start position:0% [Music] hey<00:12:04.010> Brian<00:12:04.310> so<00:12:04.790> tell<00:12:05.029> us<00:12:05.060> who<00:12:05.300> you<00:12:05.420> are<00:12:05.450> what 00:12:05.920 --> 00:12:05.930 align:start position:0% hey Brian so tell us who you are what 00:12:05.930 --> 00:12:16.540 align:start position:0% hey Brian so tell us who you are what will<00:12:06.260> teach<00:12:06.470> me<00:12:10.330> sorry<00:12:11.620> said<00:12:12.620> again<00:12:15.070> and<00:12:16.070> won't 00:12:16.540 --> 00:12:16.550 align:start position:0% will teach me sorry said again and won't 00:12:16.550 --> 00:12:28.150 align:start position:0% will teach me sorry said again and won't be<00:12:16.700> the<00:12:16.790> B's<00:12:16.970> dude 00:12:28.150 --> 00:12:28.160 align:start position:0% 00:12:28.160 --> 00:12:36.230 align:start position:0% hi<00:12:29.160> I'm<00:12:29.370> Eric<00:12:34.250> maybe<00:12:35.250> have<00:12:35.430> useful<00:12:35.640> definition 00:12:36.230 --> 00:12:36.240 align:start position:0% hi I'm Eric maybe have useful definition 00:12:36.240 --> 00:12:37.280 align:start position:0% hi I'm Eric maybe have useful definition because<00:12:36.420> I'm<00:12:36.540> worried<00:12:36.750> about 00:12:37.280 --> 00:12:37.290 align:start position:0% because I'm worried about 00:12:37.290 --> 00:12:40.660 align:start position:0% because I'm worried about data<00:12:37.889> structures<00:12:38.220> that<00:12:38.670> playing<00:12:39.029> welcome<00:12:39.269> to 00:12:40.660 --> 00:12:40.670 align:start position:0% data structures that playing welcome to 00:12:40.670 --> 00:12:47.610 align:start position:0% data structures that playing welcome to networking<00:12:41.180> y'all<00:12:41.750> can<00:12:41.990> figure<00:12:42.140> out 00:12:47.610 --> 00:12:47.620 align:start position:0% 00:12:47.620 --> 00:12:50.490 align:start position:0% all<00:12:48.070> right<00:12:48.390> she's<00:12:49.390> just<00:12:49.420> hiding<00:12:49.870> and<00:12:50.350> it's 00:12:50.490 --> 00:12:50.500 align:start position:0% all right she's just hiding and it's 00:12:50.500 --> 00:12:53.160 align:start position:0% all right she's just hiding and it's fair<00:12:51.040> enough<00:12:51.280> I'm<00:12:51.970> merging<00:12:52.450> us<00:12:52.660> with<00:12:52.810> Hispanic 00:12:53.160 --> 00:12:53.170 align:start position:0% fair enough I'm merging us with Hispanic 00:12:53.170 --> 00:12:57.450 align:start position:0% fair enough I'm merging us with Hispanic labs<00:12:53.440> and<00:12:54.360> p2p<00:12:55.360> well<00:12:56.080> there's<00:12:57.070> something<00:12:57.340> that 00:12:57.450 --> 00:12:57.460 align:start position:0% labs and p2p well there's something that 00:12:57.460 --> 00:13:03.390 align:start position:0% labs and p2p well there's something that shouldn't<00:12:57.670> be<00:12:57.730> anyone 00:13:03.390 --> 00:13:03.400 align:start position:0% 00:13:03.400 --> 00:13:07.000 align:start position:0% hello<00:13:04.430> I'm<00:13:04.700> happy<00:13:05.180> home<00:13:05.420> by<00:13:06.170> working<00:13:06.770> on 00:13:07.000 --> 00:13:07.010 align:start position:0% hello I'm happy home by working on 00:13:07.010 --> 00:13:10.480 align:start position:0% hello I'm happy home by working on company<00:13:07.910> Network<00:13:08.510> Japan<00:13:08.870> and<00:13:09.290> my<00:13:09.740> develop 00:13:10.480 --> 00:13:10.490 align:start position:0% company Network Japan and my develop 00:13:10.490 --> 00:13:13.380 align:start position:0% company Network Japan and my develop software<00:13:11.060> for<00:13:11.180> Andrew<00:13:11.810> artists<00:13:12.170> using 00:13:13.380 --> 00:13:13.390 align:start position:0% software for Andrew artists using 00:13:13.390 --> 00:13:18.910 align:start position:0% software for Andrew artists using distributed<00:13:15.130> ledger<00:13:16.130> system<00:13:16.520> and<00:13:17.890> interfere 00:13:18.910 --> 00:13:18.920 align:start position:0% distributed ledger system and interfere 00:13:18.920 --> 00:13:20.410 align:start position:0% distributed ledger system and interfere I<00:13:19.070> like<00:13:19.370> interfere 00:13:20.410 --> 00:13:20.420 align:start position:0% I like interfere 00:13:20.420 --> 00:13:24.340 align:start position:0% I like interfere girls<00:13:21.170> get<00:13:21.800> beer<00:13:22.040> system<00:13:22.220> is<00:13:22.580> more<00:13:23.350> natural 00:13:24.340 --> 00:13:24.350 align:start position:0% girls get beer system is more natural 00:13:24.350 --> 00:13:30.280 align:start position:0% girls get beer system is more natural for<00:13:24.770> me<00:13:24.910> thank<00:13:25.910> you<00:13:27.250> and<00:13:28.510> when<00:13:29.510> intercept<00:13:29.990> I 00:13:30.280 --> 00:13:30.290 align:start position:0% for me thank you and when intercept I 00:13:30.290 --> 00:13:36.310 align:start position:0% for me thank you and when intercept I work<00:13:30.980> on<00:13:31.190> cell 00:13:36.310 --> 00:13:36.320 align:start position:0% 00:13:36.320 --> 00:13:39.650 align:start position:0% [Music] 00:13:39.650 --> 00:13:39.660 align:start position:0% 00:13:39.660 --> 00:14:00.450 align:start position:0% it's<00:13:40.660> best<00:13:40.899> that<00:13:40.959> I<00:13:41.350> work<00:13:41.740> in 00:14:00.450 --> 00:14:00.460 align:start position:0% 00:14:00.460 --> 00:14:02.500 align:start position:0% [Music] 00:14:02.500 --> 00:14:02.510 align:start position:0% [Music] 00:14:02.510 --> 00:14:05.240 align:start position:0% [Music] taras<00:14:03.510> broidy's<00:14:03.690> Matthew<00:14:04.290> life's<00:14:04.530> working<00:14:05.130> am 00:14:05.240 --> 00:14:05.250 align:start position:0% taras broidy's Matthew life's working am 00:14:05.250 --> 00:14:10.100 align:start position:0% taras broidy's Matthew life's working am using<00:14:05.460> a<00:14:05.910> new<00:14:06.510> party<00:14:07.050> to<00:14:07.230> client<00:14:07.680> and 00:14:10.100 --> 00:14:10.110 align:start position:0% 00:14:10.110 --> 00:14:12.710 align:start position:0% and<00:14:10.610> occasion<00:14:11.610> for<00:14:11.940> each<00:14:12.120> other<00:14:12.300> with<00:14:12.600> all 00:14:12.710 --> 00:14:12.720 align:start position:0% and occasion for each other with all 00:14:12.720 --> 00:14:18.750 align:start position:0% and occasion for each other with all essential<00:14:13.260> ice 00:14:18.750 --> 00:14:18.760 align:start position:0% 00:14:18.760 --> 00:14:21.600 align:start position:0% I'm<00:14:19.209> Abby<00:14:19.630> I<00:14:19.930> worked<00:14:20.230> with<00:14:20.470> radical<00:14:21.160> and<00:14:21.370> iOS 00:14:21.600 --> 00:14:21.610 align:start position:0% I'm Abby I worked with radical and iOS 00:14:21.610 --> 00:14:25.290 align:start position:0% I'm Abby I worked with radical and iOS Queen<00:14:21.940> which<00:14:22.180> are<00:14:22.360> both<00:14:23.290> building<00:14:24.300> such 00:14:25.290 --> 00:14:25.300 align:start position:0% Queen which are both building such 00:14:25.300 --> 00:14:28.170 align:start position:0% Queen which are both building such alliance<00:14:25.750> alternative<00:14:26.290> to<00:14:26.410> get<00:14:26.880> here<00:14:27.880> to<00:14:27.970> here 00:14:28.170 --> 00:14:28.180 align:start position:0% alliance alternative to get here to here 00:14:28.180 --> 00:14:34.590 align:start position:0% alliance alternative to get here to here at<00:14:28.300> code<00:14:28.600> collaboration<00:14:29.579> and<00:14:30.579> not<00:14:31.300> say<00:14:31.779> no<00:14:31.990> to 00:14:34.590 --> 00:14:34.600 align:start position:0% 00:14:34.600 --> 00:14:37.640 align:start position:0% the<00:14:34.960> deep<00:14:35.140> platform<00:14:35.760> and 00:14:37.640 --> 00:14:37.650 align:start position:0% the deep platform and 00:14:37.650 --> 00:14:39.210 align:start position:0% the deep platform and [Music] 00:14:39.210 --> 00:14:39.220 align:start position:0% [Music] 00:14:39.220 --> 00:14:43.080 align:start position:0% [Music] I'm<00:14:39.610> Dean<00:14:39.910> I'm<00:14:40.330> a<00:14:40.360> researcher<00:14:41.080> I<00:14:41.890> think<00:14:42.670> PP<00:14:43.000> is 00:14:43.080 --> 00:14:43.090 align:start position:0% I'm Dean I'm a researcher I think PP is 00:14:43.090 --> 00:14:44.730 align:start position:0% I'm Dean I'm a researcher I think PP is about<00:14:43.300> creating<00:14:43.660> more<00:14:43.780> accessible<00:14:44.350> networks 00:14:44.730 --> 00:14:44.740 align:start position:0% about creating more accessible networks 00:14:44.740 --> 00:14:48.110 align:start position:0% about creating more accessible networks and<00:14:45.160> so<00:14:45.430> that's<00:14:45.640> what<00:14:46.000> I<00:14:46.240> mainly 00:14:48.110 --> 00:14:48.120 align:start position:0% and so that's what I mainly 00:14:48.120 --> 00:14:53.090 align:start position:0% and so that's what I mainly it<00:14:48.420> easy<00:14:48.689> to<00:14:48.959> use<00:14:49.139> more<00:14:49.559> accessible 00:14:53.090 --> 00:14:53.100 align:start position:0% 00:14:53.100 --> 00:14:55.930 align:start position:0% good<00:14:53.880> morning<00:14:54.150> everyone<00:14:54.450> I'm<00:14:55.140> our<00:14:55.440> own 00:14:55.930 --> 00:14:55.940 align:start position:0% good morning everyone I'm our own 00:14:55.940 --> 00:15:01.960 align:start position:0% good morning everyone I'm our own project<00:14:56.940> two<00:14:57.030> technologies<00:14:57.600> so<00:14:58.080> BtoB<00:14:59.040> us 00:15:01.960 --> 00:15:01.970 align:start position:0% 00:15:01.970 --> 00:15:05.840 align:start position:0% community<00:15:03.320> communications<00:15:04.320> and<00:15:04.920> they<00:15:05.070> try<00:15:05.790> to 00:15:05.840 --> 00:15:05.850 align:start position:0% community communications and they try to 00:15:05.850 --> 00:15:07.760 align:start position:0% community communications and they try to concentrate<00:15:06.330> and<00:15:06.630> explore<00:15:07.050> more<00:15:07.290> about<00:15:07.350> how 00:15:07.760 --> 00:15:07.770 align:start position:0% concentrate and explore more about how 00:15:07.770 --> 00:15:16.710 align:start position:0% concentrate and explore more about how data<00:15:08.190> can<00:15:08.370> be<00:15:09.710> saved<00:15:10.710> forever<00:15:11.480> without<00:15:12.480> loss 00:15:16.710 --> 00:15:16.720 align:start position:0% 00:15:16.720 --> 00:15:18.220 align:start position:0% [Music] 00:15:18.220 --> 00:15:18.230 align:start position:0% [Music] 00:15:18.230 --> 00:15:20.010 align:start position:0% [Music] the<00:15:18.440> box 00:15:20.010 --> 00:15:20.020 align:start position:0% the box 00:15:20.020 --> 00:15:26.780 align:start position:0% the box for<00:15:20.529> me<00:15:21.459> TV<00:15:23.220> committee<00:15:24.220> to<00:15:24.339> be<00:15:24.520> is<00:15:24.580> a<00:15:24.990> waterway 00:15:26.780 --> 00:15:26.790 align:start position:0% for me TV committee to be is a waterway 00:15:26.790 --> 00:15:31.260 align:start position:0% for me TV committee to be is a waterway identity<00:15:27.810> identity<00:15:28.810> you<00:15:29.709> know<00:15:29.800> the<00:15:30.670> freedom 00:15:31.260 --> 00:15:31.270 align:start position:0% identity identity you know the freedom 00:15:31.270 --> 00:15:33.830 align:start position:0% identity identity you know the freedom from<00:15:32.110> our<00:15:32.380> eyes 00:15:33.830 --> 00:15:33.840 align:start position:0% from our eyes 00:15:33.840 --> 00:15:37.390 align:start position:0% from our eyes [Music] 00:15:37.390 --> 00:15:37.400 align:start position:0% [Music] 00:15:37.400 --> 00:15:39.760 align:start position:0% [Music] hi<00:15:37.910> everybody<00:15:38.270> name<00:15:38.900> is<00:15:38.990> Antoine<00:15:39.380> from<00:15:39.620> wet 00:15:39.760 --> 00:15:39.770 align:start position:0% hi everybody name is Antoine from wet 00:15:39.770 --> 00:15:42.400 align:start position:0% hi everybody name is Antoine from wet look<00:15:39.950> I<00:15:40.610> talk<00:15:41.450> to<00:15:41.570> look<00:15:41.690> at<00:15:41.810> the<00:15:41.870> bug<00:15:42.020> go<00:15:42.200> to 00:15:42.400 --> 00:15:42.410 align:start position:0% look I talk to look at the bug go to 00:15:42.410 --> 00:15:45.940 align:start position:0% look I talk to look at the bug go to this<00:15:42.530> point<00:15:42.710> so<00:15:43.840> me<00:15:44.840> because<00:15:45.260> period<00:15:45.710> the 00:15:45.940 --> 00:15:45.950 align:start position:0% this point so me because period the 00:15:45.950 --> 00:15:51.820 align:start position:0% this point so me because period the future<00:15:46.720> specifications<00:15:47.720> now<00:15:47.900> rules<00:15:48.680> away<00:15:50.830> so 00:15:51.820 --> 00:15:51.830 align:start position:0% future specifications now rules away so 00:15:51.830 --> 00:15:54.070 align:start position:0% future specifications now rules away so willing<00:15:52.130> to<00:15:52.160> see<00:15:52.370> more<00:15:52.520> more<00:15:52.730> that<00:15:53.080> we 00:15:54.070 --> 00:15:54.080 align:start position:0% willing to see more more that we 00:15:54.080 --> 00:15:55.870 align:start position:0% willing to see more more that we specialize<00:15:54.530> in<00:15:54.560> testing<00:15:55.310> those<00:15:55.460> things<00:15:55.700> and 00:15:55.870 --> 00:15:55.880 align:start position:0% specialize in testing those things and 00:15:55.880 --> 00:15:58.530 align:start position:0% specialize in testing those things and bringing<00:15:56.060> them<00:15:56.180> as<00:15:56.420> much<00:15:56.570> as<00:15:56.720> possible 00:15:58.530 --> 00:15:58.540 align:start position:0% bringing them as much as possible 00:15:58.540 --> 00:16:01.190 align:start position:0% bringing them as much as possible [Music] 00:16:01.190 --> 00:16:01.200 align:start position:0% [Music] 00:16:01.200 --> 00:16:03.920 align:start position:0% [Music] I'm<00:16:01.589> Renee<00:16:01.860> and<00:16:02.010> we'll<00:16:02.220> solve<00:16:02.430> o'clock<00:16:02.930> I'm 00:16:03.920 --> 00:16:03.930 align:start position:0% I'm Renee and we'll solve o'clock I'm 00:16:03.930 --> 00:16:04.519 align:start position:0% I'm Renee and we'll solve o'clock I'm here<00:16:04.200> because 00:16:04.519 --> 00:16:04.529 align:start position:0% here because 00:16:04.529 --> 00:16:09.090 align:start position:0% here because networking<00:16:05.100> touches<00:16:05.459> our<00:16:05.610> program<00:16:06.000> work 00:16:09.090 --> 00:16:09.100 align:start position:0% 00:16:09.100 --> 00:16:12.850 align:start position:0% I<00:16:10.100> work<00:16:10.640> with<00:16:10.850> that<00:16:11.089> wire<00:16:11.360> line<00:16:11.570> and<00:16:12.529> I<00:16:12.649> like<00:16:12.830> a 00:16:12.850 --> 00:16:12.860 align:start position:0% I work with that wire line and I like a 00:16:12.860 --> 00:16:15.960 align:start position:0% I work with that wire line and I like a PCP<00:16:13.190> because<00:16:13.550> of<00:16:13.640> its<00:16:13.790> permissionless<00:16:14.330> nature 00:16:15.960 --> 00:16:15.970 align:start position:0% PCP because of its permissionless nature 00:16:15.970 --> 00:16:20.260 align:start position:0% PCP because of its permissionless nature okay<00:16:18.040> everyone<00:16:19.040> my<00:16:19.490> name<00:16:19.610> is<00:16:19.670> Matthew<00:16:19.970> slipper 00:16:20.260 --> 00:16:20.270 align:start position:0% okay everyone my name is Matthew slipper 00:16:20.270 --> 00:16:23.079 align:start position:0% okay everyone my name is Matthew slipper I<00:16:20.450> founded<00:16:20.810> a<00:16:20.899> company<00:16:21.020> called<00:16:21.260> kyojin<00:16:22.130> and<00:16:22.279> we 00:16:23.079 --> 00:16:23.089 align:start position:0% I founded a company called kyojin and we 00:16:23.089 --> 00:16:24.970 align:start position:0% I founded a company called kyojin and we help<00:16:23.300> other<00:16:23.660> companies<00:16:23.899> build<00:16:24.350> protocols<00:16:24.800> and 00:16:24.970 --> 00:16:24.980 align:start position:0% help other companies build protocols and 00:16:24.980 --> 00:16:28.840 align:start position:0% help other companies build protocols and apps<00:16:25.130> and<00:16:25.399> I<00:16:26.360> think<00:16:26.899> that's<00:16:27.140> this<00:16:27.320> is<00:16:27.860> the<00:16:28.010> fear 00:16:28.840 --> 00:16:28.850 align:start position:0% apps and I think that's this is the fear 00:16:28.850 --> 00:16:30.160 align:start position:0% apps and I think that's this is the fear that<00:16:29.089> I<00:16:29.270> was<00:16:29.360> thinking<00:16:29.480> about<00:16:29.660> it<00:16:29.959> see 00:16:30.160 --> 00:16:30.170 align:start position:0% that I was thinking about it see 00:16:30.170 --> 00:16:31.690 align:start position:0% that I was thinking about it see peer-to-peer<00:16:30.709> is<00:16:30.950> important<00:16:31.339> because<00:16:31.430> it's 00:16:31.690 --> 00:16:31.700 align:start position:0% peer-to-peer is important because it's 00:16:31.700 --> 00:16:33.699 align:start position:0% peer-to-peer is important because it's the<00:16:31.790> substrate<00:16:32.420> that<00:16:32.750> allows<00:16:33.020> you<00:16:33.230> to<00:16:33.320> build<00:16:33.470> a 00:16:33.699 --> 00:16:33.709 align:start position:0% the substrate that allows you to build a 00:16:33.709 --> 00:16:35.620 align:start position:0% the substrate that allows you to build a credibly<00:16:33.980> decentralized<00:16:34.550> applications<00:16:34.730> you 00:16:35.620 --> 00:16:35.630 align:start position:0% credibly decentralized applications you 00:16:35.630 --> 00:16:36.670 align:start position:0% credibly decentralized applications you can't<00:16:35.810> have<00:16:35.930> one<00:16:36.080> without<00:16:36.170> the<00:16:36.350> other<00:16:36.470> and 00:16:36.670 --> 00:16:36.680 align:start position:0% can't have one without the other and 00:16:36.680 --> 00:16:41.910 align:start position:0% can't have one without the other and here<00:16:37.310> we<00:16:37.370> are<00:16:37.399> to<00:16:37.580> build<00:16:37.730> a<00:16:37.880> great<00:16:38.089> foundation 00:16:41.910 --> 00:16:41.920 align:start position:0% 00:16:41.920 --> 00:16:43.150 align:start position:0% joon-ha 00:16:43.150 --> 00:16:43.160 align:start position:0% joon-ha 00:16:43.160 --> 00:16:47.980 align:start position:0% joon-ha yeah<00:16:43.459> I'm<00:16:43.670> Julian<00:16:44.600> I<00:16:45.970> think<00:16:46.970> open<00:16:47.330> foundation 00:16:47.980 --> 00:16:47.990 align:start position:0% yeah I'm Julian I think open foundation 00:16:47.990 --> 00:16:53.560 align:start position:0% yeah I'm Julian I think open foundation and<00:16:48.920> I<00:16:49.839> think<00:16:50.839> that<00:16:51.020> for<00:16:51.649> me<00:16:51.800> p2p<00:16:52.279> is<00:16:52.910> important 00:16:53.560 --> 00:16:53.570 align:start position:0% and I think that for me p2p is important 00:16:53.570 --> 00:16:56.400 align:start position:0% and I think that for me p2p is important because<00:16:53.750> that's<00:16:54.230> something<00:16:54.649> that<00:16:55.279> enables 00:16:56.400 --> 00:16:56.410 align:start position:0% because that's something that enables 00:16:56.410 --> 00:16:59.829 align:start position:0% because that's something that enables emergence<00:16:57.410> of<00:16:57.709> complex<00:16:58.399> systems<00:16:59.209> in<00:16:59.779> a 00:16:59.829 --> 00:16:59.839 align:start position:0% emergence of complex systems in a 00:16:59.839 --> 00:17:05.590 align:start position:0% emergence of complex systems in a bottom-up<00:17:00.700> way<00:17:03.010> exponential<00:17:04.010> way<00:17:04.510> with<00:17:05.510> the 00:17:05.590 --> 00:17:05.600 align:start position:0% bottom-up way exponential way with the 00:17:05.600 --> 00:17:09.850 align:start position:0% bottom-up way exponential way with the explanation<00:17:06.020> of<00:17:06.050> growth<00:17:08.500> hi<00:17:09.500> I'm<00:17:09.650> rich 00:17:09.850 --> 00:17:09.860 align:start position:0% explanation of growth hi I'm rich 00:17:09.860 --> 00:17:12.400 align:start position:0% explanation of growth hi I'm rich burdened<00:17:10.490> I<00:17:10.579> work<00:17:10.790> for<00:17:11.059> a<00:17:11.089> while<00:17:11.300> ein<00:17:11.569> I'm 00:17:12.400 --> 00:17:12.410 align:start position:0% burdened I work for a while ein I'm 00:17:12.410 --> 00:17:14.590 align:start position:0% burdened I work for a while ein I'm interested<00:17:12.860> in<00:17:12.920> p2p<00:17:13.459> because<00:17:13.910> the<00:17:14.240> internet 00:17:14.590 --> 00:17:14.600 align:start position:0% interested in p2p because the internet 00:17:14.600 --> 00:17:17.199 align:start position:0% interested in p2p because the internet was<00:17:14.630> originally<00:17:15.110> designed<00:17:15.260> to<00:17:15.589> be<00:17:16.280> tolerant 00:17:17.199 --> 00:17:17.209 align:start position:0% was originally designed to be tolerant 00:17:17.209 --> 00:17:20.290 align:start position:0% was originally designed to be tolerant to<00:17:17.480> a<00:17:17.510> catastrophic<00:17:18.459> nuclear<00:17:19.459> attack<00:17:19.970> and 00:17:20.290 --> 00:17:20.300 align:start position:0% to a catastrophic nuclear attack and 00:17:20.300 --> 00:17:22.329 align:start position:0% to a catastrophic nuclear attack and still<00:17:20.540> operate<00:17:21.020> I<00:17:21.290> think<00:17:21.829> we<00:17:21.920> still<00:17:22.100> have<00:17:22.160> some 00:17:22.329 --> 00:17:22.339 align:start position:0% still operate I think we still have some 00:17:22.339 --> 00:17:25.210 align:start position:0% still operate I think we still have some extent<00:17:22.880> existential<00:17:23.630> risks<00:17:24.050> today<00:17:24.410> that<00:17:25.100> we 00:17:25.210 --> 00:17:25.220 align:start position:0% extent existential risks today that we 00:17:25.220 --> 00:17:27.309 align:start position:0% extent existential risks today that we need<00:17:25.339> to<00:17:25.459> guard<00:17:25.640> against<00:17:26.179> and<00:17:26.360> I<00:17:26.420> think<00:17:26.660> Peter 00:17:27.309 --> 00:17:27.319 align:start position:0% need to guard against and I think Peter 00:17:27.319 --> 00:17:29.020 align:start position:0% need to guard against and I think Peter B<00:17:27.500> is<00:17:27.679> a<00:17:27.709> way<00:17:28.100> of<00:17:28.220> getting<00:17:28.490> back<00:17:28.520> to<00:17:28.940> the 00:17:29.020 --> 00:17:29.030 align:start position:0% B is a way of getting back to the 00:17:29.030 --> 00:17:33.430 align:start position:0% B is a way of getting back to the original<00:17:29.059> origins<00:17:29.900> of<00:17:30.110> the<00:17:30.230> Internet 00:17:33.430 --> 00:17:33.440 align:start position:0% 00:17:33.440 --> 00:17:37.100 align:start position:0% hi<00:17:34.440> I'm<00:17:34.860> Ashwin<00:17:35.159> work<00:17:35.639> for<00:17:35.820> wireline<00:17:36.179> and<00:17:36.389> for 00:17:37.100 --> 00:17:37.110 align:start position:0% hi I'm Ashwin work for wireline and for 00:17:37.110 --> 00:17:38.869 align:start position:0% hi I'm Ashwin work for wireline and for me<00:17:37.230> we<00:17:37.440> do<00:17:37.559> be<00:17:37.710> is<00:17:37.860> about<00:17:38.070> sort<00:17:38.340> of<00:17:38.399> replicating 00:17:38.869 --> 00:17:38.879 align:start position:0% me we do be is about sort of replicating 00:17:38.879 --> 00:17:40.070 align:start position:0% me we do be is about sort of replicating what<00:17:39.090> happens<00:17:39.360> in<00:17:39.480> the<00:17:39.539> real<00:17:39.659> world 00:17:40.070 --> 00:17:40.080 align:start position:0% what happens in the real world 00:17:40.080 --> 00:17:41.899 align:start position:0% what happens in the real world just<00:17:40.230> taking<00:17:40.500> it<00:17:40.590> online<00:17:40.740> all<00:17:41.070> your<00:17:41.399> kudos<00:17:41.789> all 00:17:41.899 --> 00:17:41.909 align:start position:0% just taking it online all your kudos all 00:17:41.909 --> 00:17:43.070 align:start position:0% just taking it online all your kudos all your<00:17:42.059> connections<00:17:42.269> in<00:17:42.600> the<00:17:42.690> real<00:17:42.840> world 00:17:43.070 --> 00:17:43.080 align:start position:0% your connections in the real world 00:17:43.080 --> 00:17:44.840 align:start position:0% your connections in the real world thinking<00:17:43.710> them<00:17:43.919> online<00:17:44.039> and<00:17:44.279> just<00:17:44.549> dealing 00:17:44.840 --> 00:17:44.850 align:start position:0% thinking them online and just dealing 00:17:44.850 --> 00:17:48.220 align:start position:0% thinking them online and just dealing with<00:17:44.970> you<00:17:45.240> know<00:17:45.299> people<00:17:45.899> directly<00:17:46.279> thank<00:17:47.279> you 00:17:48.220 --> 00:17:48.230 align:start position:0% with you know people directly thank you 00:17:48.230 --> 00:17:52.730 align:start position:0% with you know people directly thank you hi<00:17:49.230> Manuel<00:17:50.129> and<00:17:50.850> I'm<00:17:51.750> basically<00:17:52.139> working<00:17:52.350> on<00:17:52.649> a 00:17:52.730 --> 00:17:52.740 align:start position:0% hi Manuel and I'm basically working on a 00:17:52.740 --> 00:17:54.980 align:start position:0% hi Manuel and I'm basically working on a collective<00:17:53.279> venture<00:17:53.610> builder<00:17:54.000> so<00:17:54.720> we're 00:17:54.980 --> 00:17:54.990 align:start position:0% collective venture builder so we're 00:17:54.990 --> 00:17:58.129 align:start position:0% collective venture builder so we're trying<00:17:55.259> to<00:17:55.620> be<00:17:56.580> like<00:17:56.820> rocket<00:17:57.480> internet<00:17:57.750> but 00:17:58.129 --> 00:17:58.139 align:start position:0% trying to be like rocket internet but 00:17:58.139 --> 00:18:00.289 align:start position:0% trying to be like rocket internet but with<00:17:58.799> peers<00:17:59.100> that<00:17:59.279> are<00:17:59.399> building<00:17:59.759> stuff<00:18:00.029> and 00:18:00.289 --> 00:18:00.299 align:start position:0% with peers that are building stuff and 00:18:00.299 --> 00:18:03.519 align:start position:0% with peers that are building stuff and not<00:18:01.110> only<00:18:01.230> developers<00:18:02.190> but<00:18:02.370> also<00:18:02.490> my<00:18:02.879> tears 00:18:03.519 --> 00:18:03.529 align:start position:0% not only developers but also my tears 00:18:03.529 --> 00:18:07.789 align:start position:0% not only developers but also my tears operations<00:18:04.529> guys<00:18:04.830> finance<00:18:05.789> financial<00:18:06.799> help 00:18:07.789 --> 00:18:07.799 align:start position:0% operations guys finance financial help 00:18:07.799 --> 00:18:10.159 align:start position:0% operations guys finance financial help that<00:18:07.860> any<00:18:08.309> project<00:18:08.610> needs<00:18:08.940> and<00:18:09.210> we<00:18:09.990> just 00:18:10.159 --> 00:18:10.169 align:start position:0% that any project needs and we just 00:18:10.169 --> 00:18:12.200 align:start position:0% that any project needs and we just connect<00:18:10.440> all<00:18:10.590> these<00:18:10.679> tools<00:18:10.919> and<00:18:11.190> bring<00:18:11.429> people 00:18:12.200 --> 00:18:12.210 align:start position:0% connect all these tools and bring people 00:18:12.210 --> 00:18:14.360 align:start position:0% connect all these tools and bring people together<00:18:12.620> what<00:18:13.620> we<00:18:13.769> do<00:18:13.830> we<00:18:13.950> do 00:18:14.360 --> 00:18:14.370 align:start position:0% together what we do we do 00:18:14.370 --> 00:18:19.190 align:start position:0% together what we do we do well<00:18:15.980> something<00:18:16.980> April's<00:18:17.370> us<00:18:17.549> to<00:18:18.049> work<00:18:19.049> with 00:18:19.190 --> 00:18:19.200 align:start position:0% well something April's us to work with 00:18:19.200 --> 00:18:26.360 align:start position:0% well something April's us to work with that<00:18:19.409> somewhere<00:18:20.070> in<00:18:20.159> the<00:18:20.250> middle 00:18:26.360 --> 00:18:26.370 align:start position:0% 00:18:26.370 --> 00:18:29.250 align:start position:0% yes<00:18:27.780> who<00:18:28.780> are<00:18:28.900> you 00:18:29.250 --> 00:18:29.260 align:start position:0% yes who are you 00:18:29.260 --> 00:18:33.800 align:start position:0% yes who are you oh<00:18:29.290> hello<00:18:30.130> why<00:18:30.280> do<00:18:30.340> you<00:18:30.460> do<00:18:30.640> this 00:18:33.800 --> 00:18:33.810 align:start position:0% 00:18:33.810 --> 00:18:39.060 align:start position:0% hi<00:18:34.810> I'm<00:18:34.930> Frankie<00:18:35.380> I<00:18:35.590> work<00:18:36.340> on<00:18:36.520> madam<00:18:36.760> ask<00:18:38.070> what 00:18:39.060 --> 00:18:39.070 align:start position:0% hi I'm Frankie I work on madam ask what 00:18:39.070 --> 00:18:40.410 align:start position:0% hi I'm Frankie I work on madam ask what what<00:18:39.520> was<00:18:39.640> the<00:18:39.670> question<00:18:39.970> what<00:18:40.330> is 00:18:40.410 --> 00:18:40.420 align:start position:0% what was the question what is 00:18:40.420 --> 00:18:45.330 align:start position:0% what was the question what is peer-to-peer<00:18:40.600> to<00:18:40.900> me<00:18:41.020> yeah<00:18:43.860> I'm<00:18:44.860> just<00:18:45.040> here<00:18:45.190> to 00:18:45.330 --> 00:18:45.340 align:start position:0% peer-to-peer to me yeah I'm just here to 00:18:45.340 --> 00:18:48.160 align:start position:0% peer-to-peer to me yeah I'm just here to help<00:18:45.430> everyone<00:18:45.940> out<00:18:46.000> you<00:18:46.390> know 00:18:48.160 --> 00:18:48.170 align:start position:0% help everyone out you know 00:18:48.170 --> 00:19:04.630 align:start position:0% help everyone out you know [Music] 00:19:04.630 --> 00:19:04.640 align:start position:0% 00:19:04.640 --> 00:19:07.910 align:start position:0% so<00:19:05.640> I<00:19:06.059> think<00:19:06.600> that's<00:19:06.720> about<00:19:06.840> as<00:19:07.260> good<00:19:07.470> of<00:19:07.800> an 00:19:07.910 --> 00:19:07.920 align:start position:0% so I think that's about as good of an 00:19:07.920 --> 00:19:09.560 align:start position:0% so I think that's about as good of an interim<00:19:08.340> generally<00:19:08.700> speaking<00:19:08.970> it<00:19:09.270> appears 00:19:09.560 --> 00:19:09.570 align:start position:0% interim generally speaking it appears 00:19:09.570 --> 00:19:11.120 align:start position:0% interim generally speaking it appears one<00:19:09.720> can<00:19:09.870> hope<00:19:09.990> to<00:19:10.110> give<00:19:10.260> because<00:19:10.440> this<00:19:10.710> covers 00:19:11.120 --> 00:19:11.130 align:start position:0% one can hope to give because this covers 00:19:11.130 --> 00:19:16.370 align:start position:0% one can hope to give because this covers the<00:19:11.520> philosophical<00:19:12.680> the<00:19:13.680> social<00:19:15.110> but<00:19:16.110> there's 00:19:16.370 --> 00:19:16.380 align:start position:0% the philosophical the social but there's 00:19:16.380 --> 00:19:18.500 align:start position:0% the philosophical the social but there's one<00:19:16.559> more<00:19:16.710> person<00:19:17.030> perhaps<00:19:18.030> you'll<00:19:18.270> have<00:19:18.300> the 00:19:18.500 --> 00:19:18.510 align:start position:0% one more person perhaps you'll have the 00:19:18.510 --> 00:19:22.970 align:start position:0% one more person perhaps you'll have the size<00:19:20.480> so<00:19:21.480> the<00:19:21.660> question<00:19:22.110> is<00:19:22.290> what's<00:19:22.620> your<00:19:22.680> name 00:19:22.970 --> 00:19:22.980 align:start position:0% size so the question is what's your name 00:19:22.980 --> 00:19:24.440 align:start position:0% size so the question is what's your name what<00:19:23.190> you're<00:19:23.340> working<00:19:23.640> on<00:19:23.760> and<00:19:23.970> what<00:19:24.090> they<00:19:24.240> can 00:19:24.440 --> 00:19:24.450 align:start position:0% what you're working on and what they can 00:19:24.450 --> 00:19:26.120 align:start position:0% what you're working on and what they can be<00:19:24.570> we're<00:19:25.260> just<00:19:25.410> finishing<00:19:25.650> around<00:19:25.920> the 00:19:26.120 --> 00:19:26.130 align:start position:0% be we're just finishing around the 00:19:26.130 --> 00:19:48.830 align:start position:0% be we're just finishing around the future<00:19:37.370> what<00:19:38.370> is<00:19:46.309> cool<00:19:47.309> when<00:19:48.000> the<00:19:48.179> finals<00:19:48.600> work 00:19:48.830 --> 00:19:48.840 align:start position:0% future what is cool when the finals work 00:19:48.840 --> 00:19:50.480 align:start position:0% future what is cool when the finals work final<00:19:49.320> worth<00:19:49.470> now<00:19:49.679> that's<00:19:49.860> about<00:19:49.980> it<00:19:50.220> I<00:19:50.250> mean 00:19:50.480 --> 00:19:50.490 align:start position:0% final worth now that's about it I mean 00:19:50.490 --> 00:19:52.370 align:start position:0% final worth now that's about it I mean like<00:19:50.700> it's<00:19:50.940> a<00:19:51.030> quite<00:19:51.270> a<00:19:51.300> diverse<00:19:51.690> topic<00:19:52.140> and 00:19:52.370 --> 00:19:52.380 align:start position:0% like it's a quite a diverse topic and 00:19:52.380 --> 00:19:53.780 align:start position:0% like it's a quite a diverse topic and sounds<00:19:52.830> like<00:19:52.920> we<00:19:53.010> have<00:19:53.160> a<00:19:53.190> number<00:19:53.370> of<00:19:53.490> people 00:19:53.780 --> 00:19:53.790 align:start position:0% sounds like we have a number of people 00:19:53.790 --> 00:19:57.200 align:start position:0% sounds like we have a number of people here<00:19:53.970> who<00:19:54.179> are<00:19:55.490> but<00:19:56.490> the<00:19:56.580> right<00:19:56.760> people<00:19:56.910> to 00:19:57.200 --> 00:19:57.210 align:start position:0% here who are but the right people to 00:19:57.210 --> 00:19:58.700 align:start position:0% here who are but the right people to help<00:19:57.390> us<00:19:57.510> come<00:19:57.840> up<00:19:57.900> with<00:19:57.960> a<00:19:58.140> definition<00:19:58.380> of 00:19:58.700 --> 00:19:58.710 align:start position:0% help us come up with a definition of 00:19:58.710 --> 00:20:09.890 align:start position:0% help us come up with a definition of what<00:19:58.770> this<00:19:59.010> thing<00:19:59.070> is<00:20:03.080> gonna<00:20:04.080> go<00:20:05.300> first<00:20:08.900> okay 00:20:09.890 --> 00:20:09.900 align:start position:0% what this thing is gonna go first okay 00:20:09.900 --> 00:20:18.430 align:start position:0% what this thing is gonna go first okay so<00:20:10.730> we<00:20:11.730> heard<00:20:11.940> that 00:20:18.430 --> 00:20:18.440 align:start position:0% 00:20:18.440 --> 00:20:20.630 align:start position:0% it's<00:20:19.440> a<00:20:19.500> community<00:20:19.890> during<00:20:20.130> project<00:20:20.490> for 00:20:20.630 --> 00:20:20.640 align:start position:0% it's a community during project for 00:20:20.640 --> 00:20:22.430 align:start position:0% it's a community during project for secure<00:20:20.940> real<00:20:21.059> times<00:20:21.330> distributed<00:20:21.929> data<00:20:22.140> sync 00:20:22.430 --> 00:20:22.440 align:start position:0% secure real times distributed data sync 00:20:22.440 --> 00:20:24.200 align:start position:0% secure real times distributed data sync that's<00:20:22.830> like<00:20:22.980> a<00:20:23.250> nice<00:20:23.760> way<00:20:23.970> to<00:20:24.000> say 00:20:24.200 --> 00:20:24.210 align:start position:0% that's like a nice way to say 00:20:24.210 --> 00:20:27.169 align:start position:0% that's like a nice way to say peer-to-peer<00:20:24.450> but<00:20:25.140> yeah<00:20:25.500> so<00:20:26.429> it's<00:20:26.460> a<00:20:27.030> pretty 00:20:27.169 --> 00:20:27.179 align:start position:0% peer-to-peer but yeah so it's a pretty 00:20:27.179 --> 00:20:30.529 align:start position:0% peer-to-peer but yeah so it's a pretty clear<00:20:27.330> critical<00:20:27.690> a<00:20:28.520> little<00:20:29.520> bit<00:20:29.640> about<00:20:29.730> me<00:20:29.970> I 00:20:30.529 --> 00:20:30.539 align:start position:0% clear critical a little bit about me I 00:20:30.539 --> 00:20:32.840 align:start position:0% clear critical a little bit about me I worked<00:20:31.470> at<00:20:31.679> Google<00:20:31.919> and<00:20:32.280> they<00:20:32.340> were<00:20:32.400> close<00:20:32.669> to 00:20:32.840 --> 00:20:32.850 align:start position:0% worked at Google and they were close to 00:20:32.850 --> 00:20:35.810 align:start position:0% worked at Google and they were close to canvas<00:20:33.450> I<00:20:33.740> found<00:20:34.740> pandas<00:20:35.190> for<00:20:35.309> a<00:20:35.340> little<00:20:35.490> bit 00:20:35.810 --> 00:20:35.820 align:start position:0% canvas I found pandas for a little bit 00:20:35.820 --> 00:20:38.539 align:start position:0% canvas I found pandas for a little bit sold<00:20:36.450> that<00:20:36.630> companies<00:20:37.140> in<00:20:37.380> that<00:20:37.559> era<00:20:37.740> but<00:20:38.070> I 00:20:38.539 --> 00:20:38.549 align:start position:0% sold that companies in that era but I 00:20:38.549 --> 00:20:39.890 align:start position:0% sold that companies in that era but I could<00:20:38.760> like<00:20:38.970> deal<00:20:39.270> with<00:20:39.510> like<00:20:39.690> large 00:20:39.890 --> 00:20:39.900 align:start position:0% could like deal with like large 00:20:39.900 --> 00:20:41.600 align:start position:0% could like deal with like large companies<00:20:40.320> so<00:20:40.559> I<00:20:40.620> just<00:20:40.799> always<00:20:41.039> was<00:20:41.309> doing 00:20:41.600 --> 00:20:41.610 align:start position:0% companies so I just always was doing 00:20:41.610 --> 00:20:45.740 align:start position:0% companies so I just always was doing like<00:20:41.789> small<00:20:42.090> projects<00:20:43.640> I<00:20:44.640> also<00:20:45.450> worked<00:20:45.690> in 00:20:45.740 --> 00:20:45.750 align:start position:0% like small projects I also worked in 00:20:45.750 --> 00:20:49.310 align:start position:0% like small projects I also worked in anaconda<00:20:47.450> so<00:20:48.450> I<00:20:48.480> came<00:20:48.570> from<00:20:48.780> like<00:20:48.960> a<00:20:48.990> science 00:20:49.310 --> 00:20:49.320 align:start position:0% anaconda so I came from like a science 00:20:49.320 --> 00:20:50.270 align:start position:0% anaconda so I came from like a science background<00:20:49.470> right<00:20:49.890> and<00:20:50.010> I<00:20:50.070> was<00:20:50.159> doing 00:20:50.270 --> 00:20:50.280 align:start position:0% background right and I was doing 00:20:50.280 --> 00:20:53.149 align:start position:0% background right and I was doing research<00:20:50.520> and<00:20:51.450> science<00:20:52.169> is<00:20:52.289> messed<00:20:52.530> up<00:20:52.710> so<00:20:52.980> at 00:20:53.149 --> 00:20:53.159 align:start position:0% research and science is messed up so at 00:20:53.159 --> 00:20:55.760 align:start position:0% research and science is messed up so at this<00:20:53.280> time<00:20:53.549> when<00:20:53.850> I<00:20:53.940> was<00:20:54.120> talking<00:20:54.330> about<00:20:54.770> - 00:20:55.760 --> 00:20:55.770 align:start position:0% this time when I was talking about - 00:20:55.770 --> 00:20:59.330 align:start position:0% this time when I was talking about - okay<00:20:56.010> everyone<00:20:56.850> is<00:20:56.940> talking<00:20:57.120> about<00:20:58.070> that<00:20:59.070> half 00:20:59.330 --> 00:20:59.340 align:start position:0% okay everyone is talking about that half 00:20:59.340 --> 00:21:00.860 align:start position:0% okay everyone is talking about that half of<00:20:59.490> published<00:20:59.880> research<00:21:00.210> could<00:21:00.539> not<00:21:00.600> be 00:21:00.860 --> 00:21:00.870 align:start position:0% of published research could not be 00:21:00.870 --> 00:21:03.200 align:start position:0% of published research could not be replicated<00:21:01.070> like<00:21:02.070> the<00:21:02.309> data<00:21:02.549> was<00:21:02.880> just<00:21:02.970> like 00:21:03.200 --> 00:21:03.210 align:start position:0% replicated like the data was just like 00:21:03.210 --> 00:21:05.029 align:start position:0% replicated like the data was just like locked<00:21:03.600> up<00:21:03.780> in<00:21:03.900> silos<00:21:04.409> it<00:21:04.770> was<00:21:04.890> like 00:21:05.029 --> 00:21:05.039 align:start position:0% locked up in silos it was like 00:21:05.039 --> 00:21:07.190 align:start position:0% locked up in silos it was like completely<00:21:05.400> gone<00:21:05.640> link<00:21:06.539> route<00:21:06.780> was<00:21:06.960> an<00:21:07.049> issue 00:21:07.190 --> 00:21:07.200 align:start position:0% completely gone link route was an issue 00:21:07.200 --> 00:21:09.320 align:start position:0% completely gone link route was an issue so<00:21:07.950> scientists<00:21:08.610> are<00:21:08.669> still<00:21:08.940> talking<00:21:09.210> about 00:21:09.320 --> 00:21:09.330 align:start position:0% so scientists are still talking about 00:21:09.330 --> 00:21:11.420 align:start position:0% so scientists are still talking about this<00:21:09.539> problem<00:21:10.020> is<00:21:10.260> still<00:21:10.500> not<00:21:10.559> really<00:21:10.830> solved 00:21:11.420 --> 00:21:11.430 align:start position:0% this problem is still not really solved 00:21:11.430 --> 00:21:12.909 align:start position:0% this problem is still not really solved [Music] 00:21:12.909 --> 00:21:12.919 align:start position:0% [Music] 00:21:12.919 --> 00:21:16.700 align:start position:0% [Music] so<00:21:13.919> we<00:21:14.039> were<00:21:14.159> talking<00:21:14.309> at<00:21:14.820> this<00:21:14.940> time<00:21:15.179> in<00:21:15.720> 2013 00:21:16.700 --> 00:21:16.710 align:start position:0% so we were talking at this time in 2013 00:21:16.710 --> 00:21:19.669 align:start position:0% so we were talking at this time in 2013 how<00:21:16.860> do<00:21:16.919> we<00:21:16.980> replicate<00:21:17.159> research<00:21:18.530> and<00:21:19.530> then 00:21:19.669 --> 00:21:19.679 align:start position:0% how do we replicate research and then 00:21:19.679 --> 00:21:20.990 align:start position:0% how do we replicate research and then the<00:21:19.740> credit<00:21:19.860> extrapolate<00:21:20.490> on<00:21:20.580> that<00:21:20.760> problem 00:21:20.990 --> 00:21:21.000 align:start position:0% the credit extrapolate on that problem 00:21:21.000 --> 00:21:22.549 align:start position:0% the credit extrapolate on that problem and<00:21:21.270> talked<00:21:21.510> about<00:21:21.630> how<00:21:21.870> to<00:21:21.929> collaborate<00:21:22.440> on 00:21:22.549 --> 00:21:22.559 align:start position:0% and talked about how to collaborate on 00:21:22.559 --> 00:21:24.110 align:start position:0% and talked about how to collaborate on data<00:21:22.830> analysis<00:21:23.400> because<00:21:23.669> that's<00:21:23.850> all<00:21:24.000> we're 00:21:24.110 --> 00:21:24.120 align:start position:0% data analysis because that's all we're 00:21:24.120 --> 00:21:27.649 align:start position:0% data analysis because that's all we're really<00:21:24.150> talking<00:21:24.419> about<00:21:24.659> right<00:21:26.030> so<00:21:27.030> it's<00:21:27.600> a 00:21:27.649 --> 00:21:27.659 align:start position:0% really talking about right so it's a 00:21:27.659 --> 00:21:29.510 align:start position:0% really talking about right so it's a terrible<00:21:28.080> they<00:21:28.470> still<00:21:28.710> do<00:21:28.860> this<00:21:29.010> like<00:21:29.309> if 00:21:29.510 --> 00:21:29.520 align:start position:0% terrible they still do this like if 00:21:29.520 --> 00:21:32.330 align:start position:0% terrible they still do this like if you're<00:21:29.700> having<00:21:30.000> a<00:21:30.539> server<00:21:30.840> and<00:21:31.559> you<00:21:32.010> share 00:21:32.330 --> 00:21:32.340 align:start position:0% you're having a server and you share 00:21:32.340 --> 00:21:33.919 align:start position:0% you're having a server and you share that<00:21:32.370> server<00:21:32.850> with<00:21:33.059> a<00:21:33.090> bunch<00:21:33.240> of<00:21:33.330> people<00:21:33.630> you 00:21:33.919 --> 00:21:33.929 align:start position:0% that server with a bunch of people you 00:21:33.929 --> 00:21:36.409 align:start position:0% that server with a bunch of people you know<00:21:34.590> bad<00:21:34.770> things<00:21:35.039> happen<00:21:35.429> so<00:21:35.880> they<00:21:36.059> started 00:21:36.409 --> 00:21:36.419 align:start position:0% know bad things happen so they started 00:21:36.419 --> 00:21:39.649 align:start position:0% know bad things happen so they started using<00:21:36.570> like<00:21:36.960> git<00:21:37.230> or<00:21:37.470> email<00:21:38.100> or<00:21:38.370> arcing<00:21:38.850> as 00:21:39.649 --> 00:21:39.659 align:start position:0% using like git or email or arcing as 00:21:39.659 --> 00:21:41.899 align:start position:0% using like git or email or arcing as three<00:21:39.990> Dropbox<00:21:40.500> but<00:21:41.130> all<00:21:41.250> these<00:21:41.460> have<00:21:41.700> their 00:21:41.899 --> 00:21:41.909 align:start position:0% three Dropbox but all these have their 00:21:41.909 --> 00:21:43.310 align:start position:0% three Dropbox but all these have their own<00:21:41.970> issues<00:21:42.179> we're<00:21:42.570> trying<00:21:42.780> to<00:21:42.840> claw<00:21:43.020> grown<00:21:43.230> up 00:21:43.310 --> 00:21:43.320 align:start position:0% own issues we're trying to claw grown up 00:21:43.320 --> 00:21:45.130 align:start position:0% own issues we're trying to claw grown up in<00:21:43.470> analysis 00:21:45.130 --> 00:21:45.140 align:start position:0% in analysis 00:21:45.140 --> 00:21:49.580 align:start position:0% in analysis so<00:21:46.140> I<00:21:46.740> found<00:21:47.340> this<00:21:47.490> guy<00:21:47.730> in<00:21:48.390> 2014<00:21:49.140> this<00:21:49.290> is<00:21:49.380> max 00:21:49.580 --> 00:21:49.590 align:start position:0% so I found this guy in 2014 this is max 00:21:49.590 --> 00:21:51.650 align:start position:0% so I found this guy in 2014 this is max often<00:21:49.980> and<00:21:50.640> he<00:21:50.790> was<00:21:50.880> talking<00:21:51.090> about<00:21:51.270> let's<00:21:51.450> do 00:21:51.650 --> 00:21:51.660 align:start position:0% often and he was talking about let's do 00:21:51.660 --> 00:21:53.930 align:start position:0% often and he was talking about let's do for<00:21:52.380> data<00:21:52.560> what<00:21:52.860> get<00:21:53.130> could<00:21:53.370> do<00:21:53.490> for<00:21:53.730> source 00:21:53.930 --> 00:21:53.940 align:start position:0% for data what get could do for source 00:21:53.940 --> 00:21:56.380 align:start position:0% for data what get could do for source code<00:21:54.410> like<00:21:55.410> this<00:21:55.500> is<00:21:55.620> your<00:21:55.770> little<00:21:56.010> idea 00:21:56.380 --> 00:21:56.390 align:start position:0% code like this is your little idea 00:21:56.390 --> 00:21:58.820 align:start position:0% code like this is your little idea definitely<00:21:57.390> do<00:21:57.510> this<00:21:57.630> because<00:21:58.200> git<00:21:58.500> was<00:21:58.650> just 00:21:58.820 --> 00:21:58.830 align:start position:0% definitely do this because git was just 00:21:58.830 --> 00:22:00.320 align:start position:0% definitely do this because git was just not<00:21:58.950> working<00:21:59.100> it<00:21:59.400> I<00:21:59.640> don't<00:21:59.820> even<00:21:59.850> try<00:22:00.060> to<00:22:00.120> put<00:22:00.300> a 00:22:00.320 --> 00:22:00.330 align:start position:0% not working it I don't even try to put a 00:22:00.330 --> 00:22:02.330 align:start position:0% not working it I don't even try to put a terabyte<00:22:00.780> in<00:22:00.960> to<00:22:01.050> get<00:22:01.230> maybe<00:22:01.590> falls<00:22:01.890> over 00:22:02.330 --> 00:22:02.340 align:start position:0% terabyte in to get maybe falls over 00:22:02.340 --> 00:22:05.570 align:start position:0% terabyte in to get maybe falls over so<00:22:03.320> also<00:22:04.320> working<00:22:04.590> with<00:22:04.650> me<00:22:04.860> is<00:22:05.100> this<00:22:05.340> at<00:22:05.520> this 00:22:05.570 --> 00:22:05.580 align:start position:0% so also working with me is this at this 00:22:05.580 --> 00:22:08.090 align:start position:0% so also working with me is this at this time<00:22:05.640> and<00:22:06.470> there<00:22:07.470> are<00:22:07.530> other<00:22:07.680> people<00:22:07.800> talking 00:22:08.090 --> 00:22:08.100 align:start position:0% time and there are other people talking 00:22:08.100 --> 00:22:09.770 align:start position:0% time and there are other people talking about<00:22:08.310> this<00:22:08.460> to<00:22:08.640> look<00:22:08.820> at<00:22:08.940> this<00:22:09.030> is<00:22:09.180> wants<00:22:09.630> on 00:22:09.770 --> 00:22:09.780 align:start position:0% about this to look at this is wants on 00:22:09.780 --> 00:22:13.490 align:start position:0% about this to look at this is wants on this<00:22:09.960> computer<00:22:10.320> panel<00:22:12.050> this<00:22:13.050> is<00:22:13.110> me<00:22:13.320> they're 00:22:13.490 --> 00:22:13.500 align:start position:0% this computer panel this is me they're 00:22:13.500 --> 00:22:14.630 align:start position:0% this computer panel this is me they're all<00:22:13.620> just<00:22:13.740> kind<00:22:13.950> of<00:22:13.980> hanging<00:22:14.280> out<00:22:14.310> in<00:22:14.520> an 00:22:14.630 --> 00:22:14.640 align:start position:0% all just kind of hanging out in an 00:22:14.640 --> 00:22:18.080 align:start position:0% all just kind of hanging out in an archive<00:22:15.000> for<00:22:15.150> years<00:22:15.360> ago<00:22:16.580> but<00:22:17.580> you<00:22:17.910> may<00:22:18.030> see 00:22:18.080 --> 00:22:18.090 align:start position:0% archive for years ago but you may see 00:22:18.090 --> 00:22:19.550 align:start position:0% archive for years ago but you may see the<00:22:18.330> start<00:22:18.540> an<00:22:18.600> organization<00:22:18.750> called<00:22:19.320> that 00:22:19.550 --> 00:22:19.560 align:start position:0% the start an organization called that 00:22:19.560 --> 00:22:21.830 align:start position:0% the start an organization called that and<00:22:19.890> it<00:22:20.010> was<00:22:20.130> focused<00:22:20.430> on<00:22:20.820> how<00:22:21.120> we<00:22:21.180> saw<00:22:21.780> the 00:22:21.830 --> 00:22:21.840 align:start position:0% and it was focused on how we saw the 00:22:21.840 --> 00:22:24.680 align:start position:0% and it was focused on how we saw the scientific<00:22:22.530> problem<00:22:22.950> of<00:22:23.580> sharing<00:22:24.180> data<00:22:24.210> sets 00:22:24.680 --> 00:22:24.690 align:start position:0% scientific problem of sharing data sets 00:22:24.690 --> 00:22:26.180 align:start position:0% scientific problem of sharing data sets that<00:22:24.810> people<00:22:25.230> still<00:22:25.440> haven't<00:22:25.650> be<00:22:25.830> able<00:22:26.040> to 00:22:26.180 --> 00:22:26.190 align:start position:0% that people still haven't be able to 00:22:26.190 --> 00:22:28.520 align:start position:0% that people still haven't be able to really<00:22:26.760> solve<00:22:27.000> and<00:22:27.750> we<00:22:27.840> were<00:22:27.960> we<00:22:28.320> weren't<00:22:28.440> a 00:22:28.520 --> 00:22:28.530 align:start position:0% really solve and we were we weren't a 00:22:28.530 --> 00:22:30.620 align:start position:0% really solve and we were we weren't a company<00:22:28.920> this<00:22:29.160> time<00:22:29.400> so<00:22:29.640> he<00:22:29.730> got<00:22:29.880> nonprofit 00:22:30.620 --> 00:22:30.630 align:start position:0% company this time so he got nonprofit 00:22:30.630 --> 00:22:33.920 align:start position:0% company this time so he got nonprofit funding<00:22:32.060> so<00:22:33.060> what<00:22:33.210> everyone's<00:22:33.660> talking<00:22:33.720> on 00:22:33.920 --> 00:22:33.930 align:start position:0% funding so what everyone's talking on 00:22:33.930 --> 00:22:36.320 align:start position:0% funding so what everyone's talking on science<00:22:34.350> the<00:22:34.650> same<00:22:35.610> time<00:22:35.880> there's<00:22:36.210> like 00:22:36.320 --> 00:22:36.330 align:start position:0% science the same time there's like 00:22:36.330 --> 00:22:37.610 align:start position:0% science the same time there's like revolutions<00:22:36.900> happening<00:22:37.200> on<00:22:37.320> the<00:22:37.410> world 00:22:37.610 --> 00:22:37.620 align:start position:0% revolutions happening on the world 00:22:37.620 --> 00:22:40.550 align:start position:0% revolutions happening on the world that's<00:22:37.830> part<00:22:38.010> of<00:22:38.070> Occupy<00:22:38.280> movement<00:22:38.850> we<00:22:39.810> you 00:22:40.550 --> 00:22:40.560 align:start position:0% that's part of Occupy movement we you 00:22:40.560 --> 00:22:42.110 align:start position:0% that's part of Occupy movement we you know<00:22:40.680> we're<00:22:40.860> watching<00:22:41.250> as<00:22:41.430> the<00:22:41.760> world<00:22:41.940> was 00:22:42.110 --> 00:22:42.120 align:start position:0% know we're watching as the world was 00:22:42.120 --> 00:22:45.430 align:start position:0% know we're watching as the world was going<00:22:42.360> into<00:22:43.220> basically<00:22:44.220> chaos<00:22:44.670> because 00:22:45.430 --> 00:22:45.440 align:start position:0% going into basically chaos because 00:22:45.440 --> 00:22:47.300 align:start position:0% going into basically chaos because governments<00:22:46.440> had<00:22:46.530> shut<00:22:46.710> down<00:22:46.740> the<00:22:46.890> internet 00:22:47.300 --> 00:22:47.310 align:start position:0% governments had shut down the internet 00:22:47.310 --> 00:22:48.680 align:start position:0% governments had shut down the internet and<00:22:47.520> then<00:22:47.610> people<00:22:47.820> go<00:22:48.030> to<00:22:48.090> the<00:22:48.240> streets<00:22:48.570> and 00:22:48.680 --> 00:22:48.690 align:start position:0% and then people go to the streets and 00:22:48.690 --> 00:22:50.150 align:start position:0% and then people go to the streets and became<00:22:49.470> really<00:22:49.620> clear<00:22:49.830> that<00:22:49.890> peer-to-peer 00:22:50.150 --> 00:22:50.160 align:start position:0% became really clear that peer-to-peer 00:22:50.160 --> 00:22:51.470 align:start position:0% became really clear that peer-to-peer can<00:22:50.580> be<00:22:50.670> used<00:22:50.850> for<00:22:51.090> more<00:22:51.270> than<00:22:51.330> just 00:22:51.470 --> 00:22:51.480 align:start position:0% can be used for more than just 00:22:51.480 --> 00:22:53.420 align:start position:0% can be used for more than just scientific<00:22:52.050> data<00:22:52.350> sharing<00:22:52.590> and<00:22:53.220> we<00:22:53.310> got 00:22:53.420 --> 00:22:53.430 align:start position:0% scientific data sharing and we got 00:22:53.430 --> 00:22:54.560 align:start position:0% scientific data sharing and we got really<00:22:53.610> excited<00:22:53.970> about<00:22:54.060> the<00:22:54.330> idea<00:22:54.540> of 00:22:54.560 --> 00:22:54.570 align:start position:0% really excited about the idea of 00:22:54.570 --> 00:22:56.900 align:start position:0% really excited about the idea of building<00:22:54.930> applications<00:22:55.920> on<00:22:56.520> top 00:22:56.900 --> 00:22:56.910 align:start position:0% building applications on top 00:22:56.910 --> 00:23:01.130 align:start position:0% building applications on top this<00:22:58.400> so<00:22:59.400> you<00:22:59.640> took<00:22:59.790> BitTorrent<00:23:00.690> as<00:23:00.840> one<00:23:01.110> of 00:23:01.130 --> 00:23:01.140 align:start position:0% this so you took BitTorrent as one of 00:23:01.140 --> 00:23:03.710 align:start position:0% this so you took BitTorrent as one of our<00:23:01.290> main<00:23:01.700> inspirations<00:23:02.700> actually<00:23:03.510> use<00:23:03.630> the 00:23:03.710 --> 00:23:03.720 align:start position:0% our main inspirations actually use the 00:23:03.720 --> 00:23:05.210 align:start position:0% our main inspirations actually use the BitTorrent<00:23:03.870> DHT<00:23:04.470> for<00:23:04.680> a<00:23:04.710> little<00:23:04.860> while<00:23:04.980> in<00:23:05.190> the 00:23:05.210 --> 00:23:05.220 align:start position:0% BitTorrent DHT for a little while in the 00:23:05.220 --> 00:23:08.900 align:start position:0% BitTorrent DHT for a little while in the beginning<00:23:06.860> so<00:23:07.860> there's<00:23:08.040> some<00:23:08.430> problems<00:23:08.790> with 00:23:08.900 --> 00:23:08.910 align:start position:0% beginning so there's some problems with 00:23:08.910 --> 00:23:10.640 align:start position:0% beginning so there's some problems with BitTorrent<00:23:09.450> it<00:23:09.810> only<00:23:09.990> works<00:23:10.200> for<00:23:10.350> static 00:23:10.640 --> 00:23:10.650 align:start position:0% BitTorrent it only works for static 00:23:10.650 --> 00:23:13.070 align:start position:0% BitTorrent it only works for static files<00:23:10.860> and<00:23:11.670> create<00:23:11.820> skills<00:23:12.180> really<00:23:12.630> poorly<00:23:12.960> on 00:23:13.070 --> 00:23:13.080 align:start position:0% files and create skills really poorly on 00:23:13.080 --> 00:23:15.470 align:start position:0% files and create skills really poorly on really<00:23:13.350> big<00:23:13.440> datasets<00:23:13.710> and<00:23:14.190> it's<00:23:15.030> really<00:23:15.300> easy 00:23:15.470 --> 00:23:15.480 align:start position:0% really big datasets and it's really easy 00:23:15.480 --> 00:23:17.120 align:start position:0% really big datasets and it's really easy to<00:23:15.600> eat<00:23:15.840> straw<00:23:16.140> and<00:23:16.590> find<00:23:16.830> out<00:23:16.950> what<00:23:17.040> people 00:23:17.120 --> 00:23:17.130 align:start position:0% to eat straw and find out what people 00:23:17.130 --> 00:23:19.340 align:start position:0% to eat straw and find out what people are<00:23:17.280> sharing<00:23:17.780> so<00:23:18.780> we<00:23:18.840> wanted<00:23:18.990> to<00:23:19.050> solve<00:23:19.230> these 00:23:19.340 --> 00:23:19.350 align:start position:0% are sharing so we wanted to solve these 00:23:19.350 --> 00:23:23.660 align:start position:0% are sharing so we wanted to solve these problems<00:23:20.120> so<00:23:21.120> our<00:23:21.450> goals<00:23:21.660> are<00:23:22.370> it's<00:23:23.370> easy<00:23:23.520> to 00:23:23.660 --> 00:23:23.670 align:start position:0% problems so our goals are it's easy to 00:23:23.670 --> 00:23:25.400 align:start position:0% problems so our goals are it's easy to use<00:23:23.820> and<00:23:24.360> it<00:23:24.480> was<00:23:24.570> an<00:23:24.630> alternative<00:23:24.750> to<00:23:25.080> Dropbox 00:23:25.400 --> 00:23:25.410 align:start position:0% use and it was an alternative to Dropbox 00:23:25.410 --> 00:23:29.720 align:start position:0% use and it was an alternative to Dropbox and<00:23:27.500> we<00:23:28.500> wanted<00:23:28.710> to<00:23:28.800> be<00:23:28.860> dynamic<00:23:29.100> in<00:23:29.400> real<00:23:29.520> time 00:23:29.720 --> 00:23:29.730 align:start position:0% and we wanted to be dynamic in real time 00:23:29.730 --> 00:23:32.420 align:start position:0% and we wanted to be dynamic in real time data<00:23:30.260> built<00:23:31.260> for<00:23:31.440> modern<00:23:31.680> scientific<00:23:32.100> connect 00:23:32.420 --> 00:23:32.430 align:start position:0% data built for modern scientific connect 00:23:32.430 --> 00:23:34.700 align:start position:0% data built for modern scientific connect with<00:23:32.610> these<00:23:32.730> cases<00:23:32.970> and<00:23:33.480> always<00:23:34.170> be<00:23:34.290> faster 00:23:34.700 --> 00:23:34.710 align:start position:0% with these cases and always be faster 00:23:34.710 --> 00:23:38.870 align:start position:0% with these cases and always be faster and<00:23:35.100> note<00:23:35.820> eavesdroppers<00:23:37.550> so<00:23:38.550> you<00:23:38.610> take<00:23:38.760> this 00:23:38.870 --> 00:23:38.880 align:start position:0% and note eavesdroppers so you take this 00:23:38.880 --> 00:23:41.170 align:start position:0% and note eavesdroppers so you take this encrypting<00:23:39.420> ultimately<00:23:39.750> secured<00:23:40.200> that<00:23:40.380> link 00:23:41.170 --> 00:23:41.180 align:start position:0% encrypting ultimately secured that link 00:23:41.180 --> 00:23:43.730 align:start position:0% encrypting ultimately secured that link and<00:23:42.180> it<00:23:42.300> never<00:23:42.450> changes<00:23:42.930> even<00:23:43.260> as<00:23:43.350> the<00:23:43.440> data<00:23:43.620> is 00:23:43.730 --> 00:23:43.740 align:start position:0% and it never changes even as the data is 00:23:43.740 --> 00:23:47.690 align:start position:0% and it never changes even as the data is updated<00:23:45.890> so<00:23:46.890> how<00:23:47.010> do<00:23:47.070> you<00:23:47.130> do<00:23:47.250> this<00:23:47.370> you<00:23:47.520> build 00:23:47.690 --> 00:23:47.700 align:start position:0% updated so how do you do this you build 00:23:47.700 --> 00:23:50.900 align:start position:0% updated so how do you do this you build it<00:23:47.790> on<00:23:47.880> top<00:23:48.090> of<00:23:48.210> a<00:23:48.300> log<00:23:48.480> right<00:23:49.760> depend<00:23:50.760> only 00:23:50.900 --> 00:23:50.910 align:start position:0% it on top of a log right depend only 00:23:50.910 --> 00:23:53.450 align:start position:0% it on top of a log right depend only loves<00:23:51.120> I<00:23:51.510> have<00:23:51.720> to<00:23:51.840> go<00:23:51.930> to<00:23:52.050> this<00:23:52.250> but<00:23:53.250> how<00:23:53.400> can 00:23:53.450 --> 00:23:53.460 align:start position:0% loves I have to go to this but how can 00:23:53.460 --> 00:23:56.870 align:start position:0% loves I have to go to this but how can we<00:23:53.700> share<00:23:53.970> append-only<00:23:54.300> logs<00:23:54.720> right<00:23:55.880> Merkle 00:23:56.870 --> 00:23:56.880 align:start position:0% we share append-only logs right Merkle 00:23:56.880 --> 00:23:59.060 align:start position:0% we share append-only logs right Merkle trees<00:23:57.140> I'm<00:23:58.140> not<00:23:58.380> that's<00:23:58.560> I<00:23:58.680> want<00:23:58.740> Angela 00:23:59.060 --> 00:23:59.070 align:start position:0% trees I'm not that's I want Angela 00:23:59.070 --> 00:24:03.410 align:start position:0% trees I'm not that's I want Angela Merkel<00:23:59.340> just<00:23:59.550> like<00:23:59.640> arbitrate<00:24:02.210> so<00:24:03.210> this<00:24:03.330> is 00:24:03.410 --> 00:24:03.420 align:start position:0% Merkel just like arbitrate so this is 00:24:03.420 --> 00:24:04.250 align:start position:0% Merkel just like arbitrate so this is what<00:24:03.570> I'm<00:24:03.780> not<00:24:03.900> going<00:24:04.020> to<00:24:04.110> talk<00:24:04.200> about 00:24:04.250 --> 00:24:04.260 align:start position:0% what I'm not going to talk about 00:24:04.260 --> 00:24:06.470 align:start position:0% what I'm not going to talk about garbages<00:24:04.830> work<00:24:05.010> because<00:24:05.250> kind<00:24:05.700> of<00:24:05.790> 15<00:24:06.390> minutes 00:24:06.470 --> 00:24:06.480 align:start position:0% garbages work because kind of 15 minutes 00:24:06.480 --> 00:24:12.440 align:start position:0% garbages work because kind of 15 minutes but<00:24:07.140> get<00:24:07.460> okay<00:24:08.460> this<00:24:10.940> so<00:24:11.940> wanted<00:24:12.240> to<00:24:12.300> really 00:24:12.440 --> 00:24:12.450 align:start position:0% but get okay this so wanted to really 00:24:12.450 --> 00:24:14.660 align:start position:0% but get okay this so wanted to really talk<00:24:12.660> about<00:24:12.740> real-time<00:24:13.740> distributed<00:24:14.550> data 00:24:14.660 --> 00:24:14.670 align:start position:0% talk about real-time distributed data 00:24:14.670 --> 00:24:16.720 align:start position:0% talk about real-time distributed data sync<00:24:14.910> though<00:24:15.060> and<00:24:15.240> get<00:24:15.390> isn't<00:24:15.780> great<00:24:15.960> at<00:24:16.110> that 00:24:16.720 --> 00:24:16.730 align:start position:0% sync though and get isn't great at that 00:24:16.730 --> 00:24:20.000 align:start position:0% sync though and get isn't great at that so<00:24:17.730> how<00:24:17.850> do<00:24:17.910> you<00:24:17.970> do<00:24:18.120> real-time<00:24:18.920> that's<00:24:19.920> what 00:24:20.000 --> 00:24:20.010 align:start position:0% so how do you do real-time that's what 00:24:20.010 --> 00:24:23.100 align:start position:0% so how do you do real-time that's what you<00:24:20.070> need<00:24:20.220> to<00:24:20.250> build<00:24:20.430> applications 00:24:23.100 --> 00:24:23.110 align:start position:0% 00:24:23.110 --> 00:24:24.690 align:start position:0% so<00:24:23.620> every<00:24:23.769> time<00:24:23.919> we've<00:24:24.070> been<00:24:24.159> data<00:24:24.429> the<00:24:24.580> group 00:24:24.690 --> 00:24:24.700 align:start position:0% so every time we've been data the group 00:24:24.700 --> 00:24:27.240 align:start position:0% so every time we've been data the group has<00:24:24.850> changes<00:24:25.299> and<00:24:25.510> this<00:24:25.630> is<00:24:25.809> the<00:24:26.559> issue<00:24:26.679> with 00:24:27.240 --> 00:24:27.250 align:start position:0% has changes and this is the issue with 00:24:27.250 --> 00:24:30.000 align:start position:0% has changes and this is the issue with real-time<00:24:27.429> data<00:24:28.169> so<00:24:29.169> we<00:24:29.500> brought<00:24:29.649> it<00:24:29.769> up<00:24:29.919> to 00:24:30.000 --> 00:24:30.010 align:start position:0% real-time data so we brought it up to 00:24:30.010 --> 00:24:32.250 align:start position:0% real-time data so we brought it up to you<00:24:30.070> to<00:24:30.220> crypto<00:24:30.789> to<00:24:30.940> the<00:24:31.029> rescue<00:24:31.360> generate<00:24:32.230> a 00:24:32.250 --> 00:24:32.260 align:start position:0% you to crypto to the rescue generate a 00:24:32.260 --> 00:24:36.750 align:start position:0% you to crypto to the rescue generate a key<00:24:32.590> pair<00:24:32.830> a<00:24:33.100> public<00:24:33.580> key<00:24:33.760> and<00:24:33.789> secret<00:24:34.120> key<00:24:35.760> so 00:24:36.750 --> 00:24:36.760 align:start position:0% key pair a public key and secret key so 00:24:36.760 --> 00:24:38.190 align:start position:0% key pair a public key and secret key so say<00:24:36.909> someone<00:24:37.240> trusts<00:24:37.630> the<00:24:37.720> public<00:24:38.019> key<00:24:38.169> that 00:24:38.190 --> 00:24:38.200 align:start position:0% say someone trusts the public key that 00:24:38.200 --> 00:24:39.230 align:start position:0% say someone trusts the public key that I'm<00:24:38.440> sharing<00:24:38.590> you 00:24:39.230 --> 00:24:39.240 align:start position:0% I'm sharing you 00:24:39.240 --> 00:24:43.200 align:start position:0% I'm sharing you so<00:24:40.240> I<00:24:40.269> assign<00:24:40.570> the<00:24:40.690> group<00:24:40.720> of<00:24:41.380> a<00:24:41.830> of<00:24:42.640> the<00:24:42.909> rehash 00:24:43.200 --> 00:24:43.210 align:start position:0% so I assign the group of a of the rehash 00:24:43.210 --> 00:24:45.659 align:start position:0% so I assign the group of a of the rehash with<00:24:43.510> my<00:24:43.630> secret<00:24:43.899> key<00:24:44.019> and<00:24:44.289> then<00:24:45.279> as<00:24:45.399> I<00:24:45.519> add 00:24:45.659 --> 00:24:45.669 align:start position:0% with my secret key and then as I add 00:24:45.669 --> 00:24:50.250 align:start position:0% with my secret key and then as I add data<00:24:45.970> we<00:24:46.419> sign<00:24:46.659> the<00:24:46.809> new<00:24:46.960> group<00:24:48.029> right<00:24:49.140> so<00:24:50.140> then 00:24:50.250 --> 00:24:50.260 align:start position:0% data we sign the new group right so then 00:24:50.260 --> 00:24:53.279 align:start position:0% data we sign the new group right so then Bob<00:24:50.470> can<00:24:50.830> use<00:24:51.399> this<00:24:51.669> public<00:24:51.909> key<00:24:52.090> to<00:24:52.539> verify 00:24:53.279 --> 00:24:53.289 align:start position:0% Bob can use this public key to verify 00:24:53.289 --> 00:24:56.730 align:start position:0% Bob can use this public key to verify through<00:24:53.649> hash<00:24:53.919> signatures<00:24:54.340> over<00:24:54.490> time<00:24:55.740> this 00:24:56.730 --> 00:24:56.740 align:start position:0% through hash signatures over time this 00:24:56.740 --> 00:24:59.549 align:start position:0% through hash signatures over time this is<00:24:56.889> how<00:24:57.010> that<00:24:57.070> works<00:24:57.279> this<00:24:58.149> is<00:24:58.330> the<00:24:58.659> basic 00:24:59.549 --> 00:24:59.559 align:start position:0% is how that works this is the basic 00:24:59.559 --> 00:25:00.930 align:start position:0% is how that works this is the basic building<00:24:59.679> block<00:25:00.070> of<00:25:00.250> data<00:25:00.370> file<00:25:00.639> type<00:25:00.789> report 00:25:00.930 --> 00:25:00.940 align:start position:0% building block of data file type report 00:25:00.940 --> 00:25:02.580 align:start position:0% building block of data file type report which<00:25:01.750> took<00:25:01.899> about<00:25:02.110> four<00:25:02.320> years<00:25:02.440> of 00:25:02.580 --> 00:25:02.590 align:start position:0% which took about four years of 00:25:02.590 --> 00:25:04.139 align:start position:0% which took about four years of development<00:25:02.710> like<00:25:03.340> with<00:25:03.519> your<00:25:03.669> like<00:25:03.730> multiple 00:25:04.139 --> 00:25:04.149 align:start position:0% development like with your like multiple 00:25:04.149 --> 00:25:09.269 align:start position:0% development like with your like multiple cycles<00:25:04.559> of<00:25:05.559> development<00:25:07.470> and<00:25:08.470> this<00:25:08.649> is<00:25:08.830> hyper 00:25:09.269 --> 00:25:09.279 align:start position:0% cycles of development and this is hyper 00:25:09.279 --> 00:25:12.210 align:start position:0% cycles of development and this is hyper core<00:25:09.580> hyper<00:25:10.299> log<00:25:10.570> mr.<00:25:11.350> hyper<00:25:11.620> core<00:25:11.860> and<00:25:12.070> hyper 00:25:12.210 --> 00:25:12.220 align:start position:0% core hyper log mr. hyper core and hyper 00:25:12.220 --> 00:25:14.970 align:start position:0% core hyper log mr. hyper core and hyper ghor<00:25:12.370> protocol<00:25:12.960> so<00:25:13.960> what<00:25:14.289> people<00:25:14.440> be<00:25:14.679> doing<00:25:14.799> to 00:25:14.970 --> 00:25:14.980 align:start position:0% ghor protocol so what people be doing to 00:25:14.980 --> 00:25:16.440 align:start position:0% ghor protocol so what people be doing to build<00:25:15.130> applications<00:25:15.279> on<00:25:15.820> top<00:25:16.029> of<00:25:16.149> it<00:25:16.240> you<00:25:16.330> had 00:25:16.440 --> 00:25:16.450 align:start position:0% build applications on top of it you had 00:25:16.450 --> 00:25:20.310 align:start position:0% build applications on top of it you had some<00:25:16.630> storage<00:25:17.019> like<00:25:17.320> file<00:25:17.590> system<00:25:18.100> or<00:25:18.690> s3<00:25:19.690> or 00:25:20.310 --> 00:25:20.320 align:start position:0% some storage like file system or s3 or 00:25:20.320 --> 00:25:24.299 align:start position:0% some storage like file system or s3 or maybe<00:25:20.620> browser<00:25:21.070> cache<00:25:23.010> generating<00:25:24.010> index 00:25:24.299 --> 00:25:24.309 align:start position:0% maybe browser cache generating index 00:25:24.309 --> 00:25:27.419 align:start position:0% maybe browser cache generating index over<00:25:24.730> the<00:25:24.940> data<00:25:25.380> so<00:25:26.380> say<00:25:26.740> you<00:25:26.799> want<00:25:26.889> to<00:25:27.130> fetch 00:25:27.419 --> 00:25:27.429 align:start position:0% over the data so say you want to fetch 00:25:27.429 --> 00:25:29.879 align:start position:0% over the data so say you want to fetch or<00:25:27.909> query<00:25:28.240> that<00:25:28.419> data<00:25:28.630> in<00:25:28.720> some<00:25:28.960> way<00:25:29.139> as<00:25:29.679> it's 00:25:29.879 --> 00:25:29.889 align:start position:0% or query that data in some way as it's 00:25:29.889 --> 00:25:31.759 align:start position:0% or query that data in some way as it's coming<00:25:30.070> in<00:25:30.279> you<00:25:30.460> you<00:25:30.669> create<00:25:30.909> indexes<00:25:31.269> over<00:25:31.419> it 00:25:31.759 --> 00:25:31.769 align:start position:0% coming in you you create indexes over it 00:25:31.769 --> 00:25:34.590 align:start position:0% coming in you you create indexes over it and<00:25:32.769> that's<00:25:32.950> really<00:25:33.220> a<00:25:33.519> database<00:25:34.029> right<00:25:34.419> so 00:25:34.590 --> 00:25:34.600 align:start position:0% and that's really a database right so 00:25:34.600 --> 00:25:35.970 align:start position:0% and that's really a database right so then<00:25:34.750> people<00:25:34.929> can<00:25:35.139> start<00:25:35.380> creating 00:25:35.970 --> 00:25:35.980 align:start position:0% then people can start creating 00:25:35.980 --> 00:25:39.600 align:start position:0% then people can start creating applications<00:25:36.899> then<00:25:37.899> you<00:25:37.990> have<00:25:38.110> a<00:25:38.139> network<00:25:38.610> so 00:25:39.600 --> 00:25:39.610 align:start position:0% applications then you have a network so 00:25:39.610 --> 00:25:42.720 align:start position:0% applications then you have a network so everything<00:25:40.000> is<00:25:40.120> built<00:25:40.360> in<00:25:40.659> a<00:25:40.809> modular<00:25:40.990> way<00:25:41.730> we 00:25:42.720 --> 00:25:42.730 align:start position:0% everything is built in a modular way we 00:25:42.730 --> 00:25:44.310 align:start position:0% everything is built in a modular way we don't<00:25:42.850> say<00:25:43.269> that<00:25:43.480> you<00:25:43.539> have<00:25:43.690> to<00:25:43.809> use<00:25:43.929> any<00:25:44.110> sort 00:25:44.310 --> 00:25:44.320 align:start position:0% don't say that you have to use any sort 00:25:44.320 --> 00:25:45.720 align:start position:0% don't say that you have to use any sort of<00:25:44.440> networking<00:25:44.860> protocol 00:25:45.720 --> 00:25:45.730 align:start position:0% of networking protocol 00:25:45.730 --> 00:25:49.440 align:start position:0% of networking protocol you<00:25:46.419> just<00:25:46.600> have<00:25:46.750> to<00:25:47.190> somehow<00:25:48.190> replicate<00:25:49.000> pipe 00:25:49.440 --> 00:25:49.450 align:start position:0% you just have to somehow replicate pipe 00:25:49.450 --> 00:25:51.810 align:start position:0% you just have to somehow replicate pipe type<00:25:49.720> of<00:25:49.870> data<00:25:50.049> in<00:25:50.260> to<00:25:51.159> the<00:25:51.279> network<00:25:51.549> and<00:25:51.700> then 00:25:51.810 --> 00:25:51.820 align:start position:0% type of data in to the network and then 00:25:51.820 --> 00:25:53.539 align:start position:0% type of data in to the network and then get<00:25:51.940> it<00:25:52.059> out<00:25:52.120> on<00:25:52.179> the<00:25:52.330> other<00:25:52.360> side<00:25:52.510> so 00:25:53.539 --> 00:25:53.549 align:start position:0% get it out on the other side so 00:25:53.549 --> 00:26:01.159 align:start position:0% get it out on the other side so we<00:25:53.700> use<00:25:53.999> WebRTC<00:25:55.820> they<00:25:56.820> use<00:25:57.259> UTP<00:25:59.749> empty<00:26:00.749> NS<00:26:00.960> to 00:26:01.159 --> 00:26:01.169 align:start position:0% we use WebRTC they use UTP empty NS to 00:26:01.169 --> 00:26:04.820 align:start position:0% we use WebRTC they use UTP empty NS to find<00:26:01.350> Pierce<00:26:01.649> is<00:26:02.100> DHT<00:26:03.499> it's<00:26:04.499> very<00:26:04.679> modular 00:26:04.820 --> 00:26:04.830 align:start position:0% find Pierce is DHT it's very modular 00:26:04.830 --> 00:26:06.560 align:start position:0% find Pierce is DHT it's very modular people<00:26:05.580> kind<00:26:05.759> of<00:26:05.789> put<00:26:05.850> things<00:26:06.210> together<00:26:06.360> I 00:26:06.560 --> 00:26:06.570 align:start position:0% people kind of put things together I 00:26:06.570 --> 00:26:09.970 align:start position:0% people kind of put things together I think<00:26:07.879> so<00:26:08.879> this<00:26:09.029> is<00:26:09.179> the<00:26:09.269> foundational 00:26:09.970 --> 00:26:09.980 align:start position:0% think so this is the foundational 00:26:09.980 --> 00:26:12.409 align:start position:0% think so this is the foundational building<00:26:10.980> blocks<00:26:11.190> of<00:26:11.489> our<00:26:11.759> my<00:26:11.970> paper<00:26:12.239> which 00:26:12.409 --> 00:26:12.419 align:start position:0% building blocks of our my paper which 00:26:12.419 --> 00:26:16.279 align:start position:0% building blocks of our my paper which came<00:26:12.600> out<00:26:12.720> in<00:26:13.789> 2017<00:26:14.929> it's<00:26:15.929> part<00:26:16.169> of<00:26:16.200> the 00:26:16.279 --> 00:26:16.289 align:start position:0% came out in 2017 it's part of the 00:26:16.289 --> 00:26:17.899 align:start position:0% came out in 2017 it's part of the nonprofit<00:26:16.470> called<00:26:17.159> the<00:26:17.249> hood<00:26:17.399> for<00:26:17.549> science 00:26:17.899 --> 00:26:17.909 align:start position:0% nonprofit called the hood for science 00:26:17.909 --> 00:26:21.619 align:start position:0% nonprofit called the hood for science which<00:26:18.149> means<00:26:18.389> fact<00:26:18.539> I<00:26:18.690> found<00:26:18.899> it<00:26:20.389> so<00:26:21.389> now<00:26:21.480> we're 00:26:21.619 --> 00:26:21.629 align:start position:0% which means fact I found it so now we're 00:26:21.629 --> 00:26:24.139 align:start position:0% which means fact I found it so now we're never<00:26:21.720> like<00:26:21.929> 7,000<00:26:22.649> downloads<00:26:22.739> a<00:26:23.039> week<00:26:23.190> on<00:26:23.700> NPM 00:26:24.139 --> 00:26:24.149 align:start position:0% never like 7,000 downloads a week on NPM 00:26:24.149 --> 00:26:26.810 align:start position:0% never like 7,000 downloads a week on NPM derp<00:26:24.749> all<00:26:24.840> the<00:26:24.929> modules<00:26:25.080> and<00:26:26.009> about<00:26:26.639> like 00:26:26.810 --> 00:26:26.820 align:start position:0% derp all the modules and about like 00:26:26.820 --> 00:26:28.759 align:start position:0% derp all the modules and about like 1,500<00:26:27.419> dependent<00:26:27.749> projects<00:26:28.169> that<00:26:28.559> we<00:26:28.649> know 00:26:28.759 --> 00:26:28.769 align:start position:0% 1,500 dependent projects that we know 00:26:28.769 --> 00:26:31.669 align:start position:0% 1,500 dependent projects that we know how<00:26:28.859> to<00:26:28.919> play<00:26:29.039> through<00:26:30.139> you<00:26:31.139> know<00:26:31.259> internet 00:26:31.669 --> 00:26:31.679 align:start position:0% how to play through you know internet 00:26:31.679 --> 00:26:36.440 align:start position:0% how to play through you know internet scraping<00:26:34.190> create<00:26:35.190> our<00:26:35.309> own<00:26:35.340> dog<00:26:35.580> food<00:26:35.609> also<00:26:36.119> so 00:26:36.440 --> 00:26:36.450 align:start position:0% scraping create our own dog food also so 00:26:36.450 --> 00:26:39.049 align:start position:0% scraping create our own dog food also so I<00:26:37.039> went<00:26:38.039> often<00:26:38.460> for<00:26:38.700> a<00:26:38.759> couple<00:26:38.999> years 00:26:39.049 --> 00:26:39.059 align:start position:0% I went often for a couple years 00:26:39.059 --> 00:26:43.489 align:start position:0% I went often for a couple years contracted<00:26:40.019> with<00:26:40.169> a<00:26:40.590> couple<00:26:41.009> places<00:26:42.499> Matthias 00:26:43.489 --> 00:26:43.499 align:start position:0% contracted with a couple places Matthias 00:26:43.499 --> 00:26:47.930 align:start position:0% contracted with a couple places Matthias and<00:26:43.619> Max<00:26:43.859> as<00:26:44.039> well<00:26:44.600> and<00:26:46.820> started<00:26:47.820> building 00:26:47.930 --> 00:26:47.940 align:start position:0% and Max as well and started building 00:26:47.940 --> 00:26:51.259 align:start position:0% and Max as well and started building applications<00:26:48.570> on<00:26:48.690> top<00:26:48.720> of<00:26:48.989> this<00:26:49.970> and<00:26:50.970> we<00:26:51.059> start 00:26:51.259 --> 00:26:51.269 align:start position:0% applications on top of this and we start 00:26:51.269 --> 00:26:52.549 align:start position:0% applications on top of this and we start anticipating<00:26:51.480> in<00:26:51.869> the<00:26:51.929> community<00:26:52.320> start 00:26:52.549 --> 00:26:52.559 align:start position:0% anticipating in the community start 00:26:52.559 --> 00:26:56.899 align:start position:0% anticipating in the community start community<00:26:52.919> grew<00:26:53.879> over<00:26:54.720> time<00:26:55.519> so<00:26:56.519> building<00:26:56.789> you 00:26:56.899 --> 00:26:56.909 align:start position:0% community grew over time so building you 00:26:56.909 --> 00:26:58.970 align:start position:0% community grew over time so building you user<00:26:57.119> interfaces<00:26:57.749> on<00:26:57.929> top<00:26:58.109> of<00:26:58.230> the<00:26:58.350> stuff 00:26:58.970 --> 00:26:58.980 align:start position:0% user interfaces on top of the stuff 00:26:58.980 --> 00:27:01.639 align:start position:0% user interfaces on top of the stuff one<00:26:59.940> of<00:27:00.029> the<00:27:00.090> biggest<00:27:00.539> purse<00:27:01.109> user<00:27:01.320> interface' 00:27:01.639 --> 00:27:01.649 align:start position:0% one of the biggest purse user interface' 00:27:01.649 --> 00:27:03.909 align:start position:0% one of the biggest purse user interface' speaker<00:27:02.039> browser<00:27:02.249> which<00:27:02.999> is<00:27:03.029> a<00:27:03.179> web<00:27:03.389> browser 00:27:03.909 --> 00:27:03.919 align:start position:0% speaker browser which is a web browser 00:27:03.919 --> 00:27:09.470 align:start position:0% speaker browser which is a web browser they<00:27:04.919> uses<00:27:05.249> debt<00:27:05.489> to<00:27:05.879> send<00:27:06.299> data<00:27:06.480> around 00:27:09.470 --> 00:27:09.480 align:start position:0% 00:27:09.480 --> 00:27:12.019 align:start position:0% there's<00:27:10.260> also<00:27:10.440> another<00:27:10.649> big<00:27:11.010> one<00:27:11.190> that<00:27:11.760> I<00:27:11.789> got 00:27:12.019 --> 00:27:12.029 align:start position:0% there's also another big one that I got 00:27:12.029 --> 00:27:13.480 align:start position:0% there's also another big one that I got personally<00:27:12.510> involved<00:27:12.690> in<00:27:12.870> called<00:27:13.139> that<00:27:13.289> bale 00:27:13.480 --> 00:27:13.490 align:start position:0% personally involved in called that bale 00:27:13.490 --> 00:27:17.000 align:start position:0% personally involved in called that bale which<00:27:14.490> is<00:27:14.580> a<00:27:14.610> collaborative<00:27:15.059> map<00:27:15.330> editor<00:27:16.010> to 00:27:17.000 --> 00:27:17.010 align:start position:0% which is a collaborative map editor to 00:27:17.010 --> 00:27:18.830 align:start position:0% which is a collaborative map editor to take<00:27:17.190> the<00:27:17.279> OpenStreetMap<00:27:17.700> interface<00:27:18.299> put<00:27:18.750> in 00:27:18.830 --> 00:27:18.840 align:start position:0% take the OpenStreetMap interface put in 00:27:18.840 --> 00:27:21.860 align:start position:0% take the OpenStreetMap interface put in a<00:27:18.929> desktop<00:27:19.289> app<00:27:19.470> and<00:27:20.010> put<00:27:20.870> peer-to-peer 00:27:21.860 --> 00:27:21.870 align:start position:0% a desktop app and put peer-to-peer 00:27:21.870 --> 00:27:25.970 align:start position:0% a desktop app and put peer-to-peer back-end<00:27:22.409> ready<00:27:23.750> we<00:27:24.750> work<00:27:24.899> with<00:27:25.080> monitors<00:27:25.799> and 00:27:25.970 --> 00:27:25.980 align:start position:0% back-end ready we work with monitors and 00:27:25.980 --> 00:27:30.379 align:start position:0% back-end ready we work with monitors and Peru<00:27:26.250> and<00:27:26.580> Ecuador<00:27:27.149> and<00:27:28.080> Guiana<00:27:28.700> to<00:27:29.700> map<00:27:30.179> their 00:27:30.379 --> 00:27:30.389 align:start position:0% Peru and Ecuador and Guiana to map their 00:27:30.389 --> 00:27:32.480 align:start position:0% Peru and Ecuador and Guiana to map their territories<00:27:30.929> there's<00:27:31.679> also<00:27:31.830> a<00:27:31.980> mobile<00:27:32.220> app 00:27:32.480 --> 00:27:32.490 align:start position:0% territories there's also a mobile app 00:27:32.490 --> 00:27:36.620 align:start position:0% territories there's also a mobile app that<00:27:32.789> uses<00:27:33.419> that<00:27:33.779> using<00:27:34.559> node.js<00:27:34.830> mobile<00:27:35.630> so 00:27:36.620 --> 00:27:36.630 align:start position:0% that uses that using node.js mobile so 00:27:36.630 --> 00:27:38.810 align:start position:0% that uses that using node.js mobile so they<00:27:36.779> connect<00:27:37.169> they<00:27:37.649> take<00:27:38.100> pictures<00:27:38.460> of 00:27:38.810 --> 00:27:38.820 align:start position:0% they connect they take pictures of 00:27:38.820 --> 00:27:41.450 align:start position:0% they connect they take pictures of forest<00:27:39.330> and<00:27:39.740> oil<00:27:40.740> spills<00:27:40.860> that<00:27:41.159> are<00:27:41.309> happening 00:27:41.450 --> 00:27:41.460 align:start position:0% forest and oil spills that are happening 00:27:41.460 --> 00:27:44.659 align:start position:0% forest and oil spills that are happening and<00:27:42.000> they<00:27:42.330> put<00:27:42.510> them<00:27:42.630> on<00:27:42.750> a<00:27:42.809> map<00:27:43.460> and<00:27:44.460> together 00:27:44.659 --> 00:27:44.669 align:start position:0% and they put them on a map and together 00:27:44.669 --> 00:27:46.250 align:start position:0% and they put them on a map and together they<00:27:44.970> collaborate<00:27:45.510> with<00:27:45.630> the<00:27:45.720> community<00:27:45.750> so 00:27:46.250 --> 00:27:46.260 align:start position:0% they collaborate with the community so 00:27:46.260 --> 00:27:47.480 align:start position:0% they collaborate with the community so everything<00:27:46.590> has<00:27:46.710> to<00:27:46.799> be<00:27:46.889> offline<00:27:47.250> we're 00:27:47.480 --> 00:27:47.490 align:start position:0% everything has to be offline we're 00:27:47.490 --> 00:27:50.509 align:start position:0% everything has to be offline we're talking<00:27:47.700> like<00:27:47.789> six<00:27:48.179> hours<00:27:48.360> in<00:27:48.720> canoe<00:27:49.519> they 00:27:50.509 --> 00:27:50.519 align:start position:0% talking like six hours in canoe they 00:27:50.519 --> 00:27:52.039 align:start position:0% talking like six hours in canoe they can't<00:27:50.850> have<00:27:51.090> access<00:27:51.240> a<00:27:51.539> minute<00:27:51.809> there<00:27:51.929> I'm 00:27:52.039 --> 00:27:52.049 align:start position:0% can't have access a minute there I'm 00:27:52.049 --> 00:27:54.320 align:start position:0% can't have access a minute there I'm accessing<00:27:52.350> it<00:27:52.710> and<00:27:52.980> then<00:27:53.789> they<00:27:53.880> create<00:27:54.120> maps 00:27:54.320 --> 00:27:54.330 align:start position:0% accessing it and then they create maps 00:27:54.330 --> 00:27:56.930 align:start position:0% accessing it and then they create maps and<00:27:54.570> sent<00:27:54.750> them<00:27:54.840> out<00:27:54.929> offline<00:27:55.320> and<00:27:55.789> they<00:27:56.789> use 00:27:56.930 --> 00:27:56.940 align:start position:0% and sent them out offline and they use 00:27:56.940 --> 00:27:59.259 align:start position:0% and sent them out offline and they use them<00:27:57.210> in<00:27:57.419> campaigns<00:27:58.139> and<00:27:58.529> in<00:27:58.740> legal<00:27:58.860> defense 00:27:59.259 --> 00:27:59.269 align:start position:0% them in campaigns and in legal defense 00:27:59.269 --> 00:28:02.120 align:start position:0% them in campaigns and in legal defense they<00:28:00.269> recently<00:28:00.690> won<00:28:00.899> an<00:28:01.169> amazing<00:28:01.620> campaign<00:28:01.980> in 00:28:02.120 --> 00:28:02.130 align:start position:0% they recently won an amazing campaign in 00:28:02.130 --> 00:28:04.669 align:start position:0% they recently won an amazing campaign in Ecuador<00:28:02.519> and<00:28:02.850> protected<00:28:03.539> a<00:28:03.870> lot<00:28:04.230> of<00:28:04.289> millions 00:28:04.669 --> 00:28:04.679 align:start position:0% Ecuador and protected a lot of millions 00:28:04.679 --> 00:28:07.039 align:start position:0% Ecuador and protected a lot of millions of<00:28:04.769> acres<00:28:04.919> of<00:28:05.370> pristine<00:28:05.850> rainforest<00:28:06.149> using 00:28:07.039 --> 00:28:07.049 align:start position:0% of acres of pristine rainforest using 00:28:07.049 --> 00:28:12.409 align:start position:0% of acres of pristine rainforest using the<00:28:07.110> technology<00:28:10.100> pure<00:28:11.100> Maps<00:28:11.279> is<00:28:11.429> another<00:28:11.669> one 00:28:12.409 --> 00:28:12.419 align:start position:0% the technology pure Maps is another one 00:28:12.419 --> 00:28:14.149 align:start position:0% the technology pure Maps is another one but<00:28:12.630> this<00:28:12.720> is<00:28:12.779> not<00:28:13.350> about<00:28:13.440> local<00:28:14.010> and 00:28:14.149 --> 00:28:14.159 align:start position:0% but this is not about local and 00:28:14.159 --> 00:28:16.190 align:start position:0% but this is not about local and collaborative<00:28:14.820> editing<00:28:15.600> it's<00:28:15.870> about<00:28:15.960> taking 00:28:16.190 --> 00:28:16.200 align:start position:0% collaborative editing it's about taking 00:28:16.200 --> 00:28:18.169 align:start position:0% collaborative editing it's about taking OpenStreetMap<00:28:16.980> pickles<00:28:17.340> OpenStreetMap<00:28:18.029> and 00:28:18.169 --> 00:28:18.179 align:start position:0% OpenStreetMap pickles OpenStreetMap and 00:28:18.179 --> 00:28:19.759 align:start position:0% OpenStreetMap pickles OpenStreetMap and distributing<00:28:18.510> it<00:28:18.779> across<00:28:19.019> the<00:28:19.529> internet 00:28:19.759 --> 00:28:19.769 align:start position:0% distributing it across the internet 00:28:19.769 --> 00:28:21.769 align:start position:0% distributing it across the internet really<00:28:20.429> literally<00:28:20.909> taking<00:28:21.299> the<00:28:21.360> principles 00:28:21.769 --> 00:28:21.779 align:start position:0% really literally taking the principles 00:28:21.779 --> 00:28:23.299 align:start position:0% really literally taking the principles of<00:28:21.899> BitTorrent<00:28:22.110> and<00:28:22.500> study<00:28:22.740> at<00:28:22.860> home<00:28:23.039> and 00:28:23.299 --> 00:28:23.309 align:start position:0% of BitTorrent and study at home and 00:28:23.309 --> 00:28:26.210 align:start position:0% of BitTorrent and study at home and applying<00:28:23.580> them<00:28:23.760> to<00:28:23.820> OpenStreetMap<00:28:24.630> and<00:28:25.220> and 00:28:26.210 --> 00:28:26.220 align:start position:0% applying them to OpenStreetMap and and 00:28:26.220 --> 00:28:27.950 align:start position:0% applying them to OpenStreetMap and and there's<00:28:26.429> they're<00:28:26.730> actively<00:28:27.570> working<00:28:27.809> on 00:28:27.950 --> 00:28:27.960 align:start position:0% there's they're actively working on 00:28:27.960 --> 00:28:29.269 align:start position:0% there's they're actively working on stuff<00:28:28.200> it's<00:28:28.350> really<00:28:28.529> amazing<00:28:28.679> if<00:28:28.980> you<00:28:29.039> want<00:28:29.220> to 00:28:29.269 --> 00:28:29.279 align:start position:0% stuff it's really amazing if you want to 00:28:29.279 --> 00:28:32.810 align:start position:0% stuff it's really amazing if you want to watch<00:28:29.370> them<00:28:30.980> the<00:28:31.980> two<00:28:32.159> more<00:28:32.340> care<00:28:32.519> social 00:28:32.810 --> 00:28:32.820 align:start position:0% watch them the two more care social 00:28:32.820 --> 00:28:34.310 align:start position:0% watch them the two more care social media<00:28:33.029> so<00:28:33.210> there's<00:28:33.330> a<00:28:33.450> chat<00:28:33.659> app<00:28:33.840> built<00:28:34.139> on 00:28:34.310 --> 00:28:34.320 align:start position:0% media so there's a chat app built on 00:28:34.320 --> 00:28:37.190 align:start position:0% media so there's a chat app built on this<00:28:34.440> called<00:28:34.740> cabal<00:28:36.049> there's<00:28:37.049> a 00:28:37.190 --> 00:28:37.200 align:start position:0% this called cabal there's a 00:28:37.200 --> 00:28:38.840 align:start position:0% this called cabal there's a collaborative<00:28:37.620> workspaces<00:28:38.070> called<00:28:38.429> pushpin 00:28:38.840 --> 00:28:38.850 align:start position:0% collaborative workspaces called pushpin 00:28:38.850 --> 00:28:40.490 align:start position:0% collaborative workspaces called pushpin these<00:28:39.360> are<00:28:39.450> all<00:28:39.510> desktop<00:28:39.870> apps<00:28:40.080> by<00:28:40.320> the<00:28:40.380> way 00:28:40.490 --> 00:28:40.500 align:start position:0% these are all desktop apps by the way 00:28:40.500 --> 00:28:44.350 align:start position:0% these are all desktop apps by the way and<00:28:40.710> then<00:28:41.490> mobile<00:28:41.789> apps 00:28:44.350 --> 00:28:44.360 align:start position:0% 00:28:44.360 --> 00:28:47.330 align:start position:0% there's<00:28:45.360> a<00:28:45.450> scientific<00:28:45.810> data<00:28:46.110> network<00:28:46.440> so<00:28:46.980> dry 00:28:47.330 --> 00:28:47.340 align:start position:0% there's a scientific data network so dry 00:28:47.340 --> 00:28:49.250 align:start position:0% there's a scientific data network so dry adamant<00:28:47.760> Californians<00:28:48.360> internal<00:28:48.570> library<00:28:48.900> is 00:28:49.250 --> 00:28:49.260 align:start position:0% adamant Californians internal library is 00:28:49.260 --> 00:28:50.570 align:start position:0% adamant Californians internal library is collaborating<00:28:49.710> with<00:28:49.800> the<00:28:50.010> University<00:28:50.520> of 00:28:50.570 --> 00:28:50.580 align:start position:0% collaborating with the University of 00:28:50.580 --> 00:28:52.430 align:start position:0% collaborating with the University of California<00:28:51.090> to<00:28:51.300> distribute<00:28:51.990> data<00:28:52.170> sets 00:28:52.430 --> 00:28:52.440 align:start position:0% California to distribute data sets 00:28:52.440 --> 00:28:56.120 align:start position:0% California to distribute data sets across<00:28:53.040> they<00:28:53.880> are<00:28:54.000> data<00:28:54.210> centers<00:28:55.070> with<00:28:56.070> a 00:28:56.120 --> 00:28:56.130 align:start position:0% across they are data centers with a 00:28:56.130 --> 00:28:57.410 align:start position:0% across they are data centers with a cooperative<00:28:56.490> posting<00:28:56.790> network<00:28:57.030> called<00:28:57.240> Co 00:28:57.410 --> 00:28:57.420 align:start position:0% cooperative posting network called Co 00:28:57.420 --> 00:29:00.020 align:start position:0% cooperative posting network called Co box<00:28:57.630> they're<00:28:58.290> actually<00:28:58.560> pretty<00:28:58.770> new<00:28:59.030> and 00:29:00.020 --> 00:29:00.030 align:start position:0% box they're actually pretty new and 00:29:00.030 --> 00:29:01.460 align:start position:0% box they're actually pretty new and they've<00:29:00.150> done<00:29:00.300> a<00:29:00.360> lot<00:29:00.720> of<00:29:00.750> amazing<00:29:01.020> work<00:29:01.350> in 00:29:01.460 --> 00:29:01.470 align:start position:0% they've done a lot of amazing work in 00:29:01.470 --> 00:29:03.260 align:start position:0% they've done a lot of amazing work in the<00:29:01.530> past<00:29:01.740> three<00:29:01.980> months<00:29:02.010> it's<00:29:02.370> like<00:29:02.460> wild 00:29:03.260 --> 00:29:03.270 align:start position:0% the past three months it's like wild 00:29:03.270 --> 00:29:04.970 align:start position:0% the past three months it's like wild watch<00:29:03.540> them<00:29:03.750> live<00:29:03.900> on<00:29:04.260> github<00:29:04.650> so<00:29:04.710> you<00:29:04.860> should 00:29:04.970 --> 00:29:04.980 align:start position:0% watch them live on github so you should 00:29:04.980 --> 00:29:07.220 align:start position:0% watch them live on github so you should totally<00:29:05.160> check<00:29:05.280> them<00:29:05.550> out<00:29:05.640> they're<00:29:06.270> doing<00:29:07.170> a 00:29:07.220 --> 00:29:07.230 align:start position:0% totally check them out they're doing a 00:29:07.230 --> 00:29:09.560 align:start position:0% totally check them out they're doing a lot<00:29:07.320> of<00:29:07.380> like<00:29:07.820> multiple<00:29:08.820> writers<00:29:09.030> and<00:29:09.420> like 00:29:09.560 --> 00:29:09.570 align:start position:0% lot of like multiple writers and like 00:29:09.570 --> 00:29:11.780 align:start position:0% lot of like multiple writers and like preserve<00:29:10.350> resolving<00:29:10.920> conflicts<00:29:11.490> and<00:29:11.580> stuff 00:29:11.780 --> 00:29:11.790 align:start position:0% preserve resolving conflicts and stuff 00:29:11.790 --> 00:29:14.240 align:start position:0% preserve resolving conflicts and stuff and<00:29:12.000> Klaus<00:29:12.210> is<00:29:12.420> Simmons<00:29:12.750> for<00:29:12.870> the<00:29:12.930> book<00:29:13.250> ara 00:29:14.240 --> 00:29:14.250 align:start position:0% and Klaus is Simmons for the book ara 00:29:14.250 --> 00:29:17.150 align:start position:0% and Klaus is Simmons for the book ara it's<00:29:14.700> a<00:29:14.760> constant<00:29:15.090> record<00:29:15.360> network<00:29:16.160> they've 00:29:17.150 --> 00:29:17.160 align:start position:0% it's a constant record network they've 00:29:17.160 --> 00:29:18.740 align:start position:0% it's a constant record network they've also<00:29:17.340> put<00:29:17.580> on<00:29:17.670> much<00:29:17.820> ss1<00:29:18.210> github 00:29:18.740 --> 00:29:18.750 align:start position:0% also put on much ss1 github 00:29:18.750 --> 00:29:21.440 align:start position:0% also put on much ss1 github they're<00:29:19.470> more<00:29:19.890> aetherium<00:29:20.310> focused<00:29:20.640> so<00:29:21.180> and 00:29:21.440 --> 00:29:21.450 align:start position:0% they're more aetherium focused so and 00:29:21.450 --> 00:29:23.810 align:start position:0% they're more aetherium focused so and then<00:29:21.990> wireline<00:29:22.410> n'yar<00:29:22.860> from<00:29:23.040> later<00:29:23.310> today 00:29:23.810 --> 00:29:23.820 align:start position:0% then wireline n'yar from later today 00:29:23.820 --> 00:29:25.970 align:start position:0% then wireline n'yar from later today that's<00:29:24.360> pretty<00:29:24.720> new<00:29:24.900> as<00:29:25.050> well<00:29:25.170> as<00:29:25.350> mail<00:29:25.620> simple 00:29:25.970 --> 00:29:25.980 align:start position:0% that's pretty new as well as mail simple 00:29:25.980 --> 00:29:32.120 align:start position:0% that's pretty new as well as mail simple stuff<00:29:29.300> yeah<00:29:30.300> so<00:29:30.540> people<00:29:31.320> are<00:29:31.410> using<00:29:31.620> the<00:29:31.860> stack 00:29:32.120 --> 00:29:32.130 align:start position:0% stuff yeah so people are using the stack 00:29:32.130 --> 00:29:34.160 align:start position:0% stuff yeah so people are using the stack right<00:29:32.400> now<00:29:32.580> to<00:29:32.640> build<00:29:33.030> stuff<00:29:33.240> the<00:29:33.750> problem 00:29:34.160 --> 00:29:34.170 align:start position:0% right now to build stuff the problem 00:29:34.170 --> 00:29:35.630 align:start position:0% right now to build stuff the problem that<00:29:34.260> we're<00:29:34.410> seeing<00:29:34.440> now<00:29:34.860> and<00:29:35.070> you<00:29:35.310> know<00:29:35.430> where 00:29:35.630 --> 00:29:35.640 align:start position:0% that we're seeing now and you know where 00:29:35.640 --> 00:29:37.670 align:start position:0% that we're seeing now and you know where are<00:29:35.700> we<00:29:35.790> going<00:29:36.090> with<00:29:36.750> from<00:29:37.170> now<00:29:37.200> so<00:29:37.470> I<00:29:37.500> have 00:29:37.670 --> 00:29:37.680 align:start position:0% are we going with from now so I have 00:29:37.680 --> 00:29:39.440 align:start position:0% are we going with from now so I have this<00:29:37.770> amazing<00:29:37.980> set<00:29:38.670> of<00:29:38.700> apps<00:29:38.940> and<00:29:39.120> people<00:29:39.390> are 00:29:39.440 --> 00:29:39.450 align:start position:0% this amazing set of apps and people are 00:29:39.450 --> 00:29:41.090 align:start position:0% this amazing set of apps and people are using<00:29:39.630> it's<00:29:40.260> distributed<00:29:40.890> in<00:29:41.040> the 00:29:41.090 --> 00:29:41.100 align:start position:0% using it's distributed in the 00:29:41.100 --> 00:29:42.440 align:start position:0% using it's distributed in the centralized<00:29:41.580> organization<00:29:41.760> and<00:29:42.300> there's 00:29:42.440 --> 00:29:42.450 align:start position:0% centralized organization and there's 00:29:42.450 --> 00:29:45.050 align:start position:0% centralized organization and there's like<00:29:42.630> no<00:29:43.590> central<00:29:44.160> control<00:29:44.190> of<00:29:44.640> what<00:29:44.820> we<00:29:44.910> will 00:29:45.050 --> 00:29:45.060 align:start position:0% like no central control of what we will 00:29:45.060 --> 00:29:47.630 align:start position:0% like no central control of what we will build<00:29:45.380> the<00:29:46.380> issue<00:29:46.530> though<00:29:47.010> that<00:29:47.040> we're<00:29:47.460> trying 00:29:47.630 --> 00:29:47.640 align:start position:0% build the issue though that we're trying 00:29:47.640 --> 00:29:50.270 align:start position:0% build the issue though that we're trying to<00:29:47.790> put<00:29:47.910> this<00:29:48.030> on<00:29:48.180> now<00:29:48.240> is<00:29:48.570> how<00:29:49.260> how<00:29:49.770> you<00:29:49.830> can 00:29:50.270 --> 00:29:50.280 align:start position:0% to put this on now is how how you can 00:29:50.280 --> 00:29:52.880 align:start position:0% to put this on now is how how you can make<00:29:50.460> this<00:29:50.820> these<00:29:51.720> three<00:29:51.990> parts<00:29:52.350> a<00:29:52.440> lot<00:29:52.560> easier 00:29:52.880 --> 00:29:52.890 align:start position:0% make this these three parts a lot easier 00:29:52.890 --> 00:29:54.050 align:start position:0% make this these three parts a lot easier to<00:29:52.950> work<00:29:53.040> with<00:29:53.100> because<00:29:53.430> right<00:29:53.730> now<00:29:53.850> when<00:29:53.970> you 00:29:54.050 --> 00:29:54.060 align:start position:0% to work with because right now when you 00:29:54.060 --> 00:29:56.300 align:start position:0% to work with because right now when you come<00:29:54.240> in<00:29:54.420> and<00:29:54.600> you<00:29:54.690> try<00:29:54.870> and<00:29:54.960> build<00:29:55.260> an<00:29:55.440> app<00:29:55.620> you 00:29:56.300 --> 00:29:56.310 align:start position:0% come in and you try and build an app you 00:29:56.310 --> 00:29:57.530 align:start position:0% come in and you try and build an app you would<00:29:56.430> kind<00:29:56.670> of<00:29:56.700> have<00:29:56.760> to<00:29:56.970> build<00:29:57.270> your<00:29:57.480> own 00:29:57.530 --> 00:29:57.540 align:start position:0% would kind of have to build your own 00:29:57.540 --> 00:29:59.630 align:start position:0% would kind of have to build your own database<00:29:58.020> from<00:29:58.230> scratch<00:29:58.560> every<00:29:58.860> time<00:29:59.100> which 00:29:59.630 --> 00:29:59.640 align:start position:0% database from scratch every time which 00:29:59.640 --> 00:30:02.900 align:start position:0% database from scratch every time which is<00:30:00.560> well<00:30:01.560> it's<00:30:01.860> like<00:30:02.040> I'm<00:30:02.250> probably<00:30:02.520> sure<00:30:02.700> if 00:30:02.900 --> 00:30:02.910 align:start position:0% is well it's like I'm probably sure if 00:30:02.910 --> 00:30:04.310 align:start position:0% is well it's like I'm probably sure if some<00:30:03.090> of<00:30:03.210> you<00:30:03.300> in<00:30:03.510> the<00:30:03.570> room<00:30:03.600> to<00:30:03.810> do<00:30:03.960> it<00:30:04.080> but 00:30:04.310 --> 00:30:04.320 align:start position:0% some of you in the room to do it but 00:30:04.320 --> 00:30:05.960 align:start position:0% some of you in the room to do it but like<00:30:04.560> someone<00:30:04.860> who<00:30:05.220> wants<00:30:05.430> it<00:30:05.490> just<00:30:05.640> build<00:30:05.850> an 00:30:05.960 --> 00:30:05.970 align:start position:0% like someone who wants it just build an 00:30:05.970 --> 00:30:08.090 align:start position:0% like someone who wants it just build an app<00:30:06.150> Platzer<00:30:06.930> raise<00:30:07.110> a<00:30:07.140> lot<00:30:07.320> of<00:30:07.350> money<00:30:07.440> hire 00:30:08.090 --> 00:30:08.100 align:start position:0% app Platzer raise a lot of money hire 00:30:08.100 --> 00:30:09.440 align:start position:0% app Platzer raise a lot of money hire some<00:30:08.430> distribute<00:30:08.820> engine<00:30:09.150> software 00:30:09.440 --> 00:30:09.450 align:start position:0% some distribute engine software 00:30:09.450 --> 00:30:12.160 align:start position:0% some distribute engine software engineers<00:30:09.960> it's<00:30:10.230> like<00:30:10.380> it's<00:30:11.370> a<00:30:11.430> huge<00:30:11.640> task 00:30:12.160 --> 00:30:12.170 align:start position:0% engineers it's like it's a huge task 00:30:12.170 --> 00:30:14.300 align:start position:0% engineers it's like it's a huge task it's<00:30:13.170> very<00:30:13.320> complicated<00:30:13.620> and<00:30:13.920> things<00:30:14.100> break 00:30:14.300 --> 00:30:14.310 align:start position:0% it's very complicated and things break 00:30:14.310 --> 00:30:17.240 align:start position:0% it's very complicated and things break so<00:30:15.470> what<00:30:16.470> are<00:30:16.530> we<00:30:16.620> going<00:30:16.740> to<00:30:16.800> do<00:30:16.950> to<00:30:17.010> try<00:30:17.100> and 00:30:17.240 --> 00:30:17.250 align:start position:0% so what are we going to do to try and 00:30:17.250 --> 00:30:19.640 align:start position:0% so what are we going to do to try and fix<00:30:17.430> up<00:30:17.990> create<00:30:18.990> a<00:30:19.020> software<00:30:19.380> development 00:30:19.640 --> 00:30:19.650 align:start position:0% fix up create a software development 00:30:19.650 --> 00:30:20.760 align:start position:0% fix up create a software development toolkit<00:30:20.040> hot 00:30:20.760 --> 00:30:20.770 align:start position:0% toolkit hot 00:30:20.770 --> 00:30:23.580 align:start position:0% toolkit hot so<00:30:21.340> people<00:30:21.640> can<00:30:21.910> get<00:30:22.600> started<00:30:23.050> quickly<00:30:23.170> and 00:30:23.580 --> 00:30:23.590 align:start position:0% so people can get started quickly and 00:30:23.590 --> 00:30:27.660 align:start position:0% so people can get started quickly and prototype<00:30:24.429> do<00:30:25.210> very<00:30:25.420> rapid<00:30:25.780> prototypes<00:30:26.670> and 00:30:27.660 --> 00:30:27.670 align:start position:0% prototype do very rapid prototypes and 00:30:27.670 --> 00:30:28.740 align:start position:0% prototype do very rapid prototypes and then<00:30:27.730> if<00:30:27.970> they<00:30:28.090> want<00:30:28.120> to<00:30:28.360> have<00:30:28.480> a<00:30:28.510> lot<00:30:28.660> of 00:30:28.740 --> 00:30:28.750 align:start position:0% then if they want to have a lot of 00:30:28.750 --> 00:30:30.240 align:start position:0% then if they want to have a lot of customization<00:30:29.110> they<00:30:29.530> can<00:30:29.679> start<00:30:29.890> going<00:30:29.980> under 00:30:30.240 --> 00:30:30.250 align:start position:0% customization they can start going under 00:30:30.250 --> 00:30:34.080 align:start position:0% customization they can start going under the<00:30:30.340> head<00:30:30.490> after<00:30:30.610> that<00:30:32.610> also<00:30:33.610> helps<00:30:33.820> if<00:30:33.940> you 00:30:34.080 --> 00:30:34.090 align:start position:0% the head after that also helps if you 00:30:34.090 --> 00:30:36.360 align:start position:0% the head after that also helps if you have<00:30:34.210> like<00:30:34.450> major<00:30:34.990> bumps<00:30:35.410> or<00:30:35.650> big<00:30:35.950> things<00:30:36.250> that 00:30:36.360 --> 00:30:36.370 align:start position:0% have like major bumps or big things that 00:30:36.370 --> 00:30:37.830 align:start position:0% have like major bumps or big things that happen<00:30:36.610> underneath<00:30:36.820> the<00:30:37.030> hood<00:30:37.150> you<00:30:37.660> know<00:30:37.690> if 00:30:37.830 --> 00:30:37.840 align:start position:0% happen underneath the hood you know if 00:30:37.840 --> 00:30:38.730 align:start position:0% happen underneath the hood you know if they<00:30:37.900> change<00:30:38.140> your<00:30:38.290> entire<00:30:38.530> application 00:30:38.730 --> 00:30:38.740 align:start position:0% they change your entire application 00:30:38.740 --> 00:30:43.799 align:start position:0% they change your entire application because<00:30:39.400> an<00:30:39.520> API<00:30:39.820> down<00:30:40.150> the<00:30:40.690> snap<00:30:40.900> changed<00:30:42.809> so 00:30:43.799 --> 00:30:43.809 align:start position:0% because an API down the snap changed so 00:30:43.809 --> 00:30:45.990 align:start position:0% because an API down the snap changed so I<00:30:44.110> was<00:30:44.620> using<00:30:44.800> the<00:30:45.070> non<00:30:45.250> names<00:30:45.490> but<00:30:45.670> here's<00:30:45.880> the 00:30:45.990 --> 00:30:46.000 align:start position:0% I was using the non names but here's the 00:30:46.000 --> 00:30:47.940 align:start position:0% I was using the non names but here's the actual<00:30:46.300> names<00:30:46.600> of<00:30:46.780> these<00:30:46.870> signs<00:30:47.170> on<00:30:47.470> github 00:30:47.940 --> 00:30:47.950 align:start position:0% actual names of these signs on github 00:30:47.950 --> 00:30:49.169 align:start position:0% actual names of these signs on github you<00:30:48.160> wanted<00:30:48.580> to<00:30:48.640> check<00:30:48.760> it<00:30:48.880> out 00:30:49.169 --> 00:30:49.179 align:start position:0% you wanted to check it out 00:30:49.179 --> 00:30:51.480 align:start position:0% you wanted to check it out hyper<00:30:49.450> core<00:30:49.690> protocol<00:30:50.110> pipe<00:30:50.440> report<00:30:50.830> we're 00:30:51.480 --> 00:30:51.490 align:start position:0% hyper core protocol pipe report we're 00:30:51.490 --> 00:30:55.530 align:start position:0% hyper core protocol pipe report we're coming<00:30:51.760> out<00:30:51.820> with<00:30:51.880> these<00:30:52.179> new<00:30:53.309> modules<00:30:54.540> this 00:30:55.530 --> 00:30:55.540 align:start position:0% coming out with these new modules this 00:30:55.540 --> 00:31:00.990 align:start position:0% coming out with these new modules this year<00:30:56.520> hyper<00:30:57.520> tribe<00:30:57.790> pepper<00:30:58.420> salon<00:30:58.750> and<00:31:00.000> this 00:31:00.990 --> 00:31:01.000 align:start position:0% year hyper tribe pepper salon and this 00:31:01.000 --> 00:31:02.460 align:start position:0% year hyper tribe pepper salon and this is<00:31:01.179> going<00:31:01.300> to<00:31:01.360> be<00:31:01.420> part<00:31:01.660> of<00:31:01.750> what<00:31:01.929> we<00:31:02.020> call<00:31:02.200> that 00:31:02.460 --> 00:31:02.470 align:start position:0% is going to be part of what we call that 00:31:02.470 --> 00:31:05.700 align:start position:0% is going to be part of what we call that 2.0<00:31:02.950> so<00:31:03.730> this<00:31:03.880> will<00:31:04.030> be<00:31:04.120> this<00:31:04.960> already<00:31:05.559> these 00:31:05.700 --> 00:31:05.710 align:start position:0% 2.0 so this will be this already these 00:31:05.710 --> 00:31:07.620 align:start position:0% 2.0 so this will be this already these models<00:31:06.040> exist<00:31:06.190> but<00:31:06.580> we're<00:31:07.059> not<00:31:07.150> putting<00:31:07.390> them 00:31:07.620 --> 00:31:07.630 align:start position:0% models exist but we're not putting them 00:31:07.630 --> 00:31:09.330 align:start position:0% models exist but we're not putting them into<00:31:07.840> a<00:31:07.990> cohesive<00:31:08.290> package<00:31:08.559> till<00:31:08.950> early<00:31:09.190> next 00:31:09.330 --> 00:31:09.340 align:start position:0% into a cohesive package till early next 00:31:09.340 --> 00:31:15.299 align:start position:0% into a cohesive package till early next year<00:31:11.250> so<00:31:12.250> how<00:31:12.910> much<00:31:13.030> money<00:31:13.300> do<00:31:13.860> you<00:31:14.860> think<00:31:15.130> that 00:31:15.299 --> 00:31:15.309 align:start position:0% year so how much money do you think that 00:31:15.309 --> 00:31:17.640 align:start position:0% year so how much money do you think that we've<00:31:15.460> spent<00:31:15.790> at<00:31:16.420> the<00:31:16.570> death<00:31:16.720> foundation<00:31:17.200> no<00:31:17.530> I 00:31:17.640 --> 00:31:17.650 align:start position:0% we've spent at the death foundation no I 00:31:17.650 --> 00:31:29.040 align:start position:0% we've spent at the death foundation no I can't 00:31:29.040 --> 00:31:29.050 align:start position:0% 00:31:29.050 --> 00:31:37.000 align:start position:0% yeah<00:31:30.050> 1.6<00:31:30.590> million<00:31:30.770> since<00:31:31.100> 2003<00:31:31.670> 13<00:31:34.840> so<00:31:36.010> the 00:31:37.000 --> 00:31:37.010 align:start position:0% yeah 1.6 million since 2003 13 so the 00:31:37.010 --> 00:31:38.460 align:start position:0% yeah 1.6 million since 2003 13 so the that<00:31:37.160> foundation<00:31:37.670> is<00:31:37.820> us-based<00:31:38.180> nonprofit 00:31:38.460 --> 00:31:38.470 align:start position:0% that foundation is us-based nonprofit 00:31:38.470 --> 00:31:42.610 align:start position:0% that foundation is us-based nonprofit started<00:31:39.470> 2013<00:31:40.460> but<00:31:40.610> formalized<00:31:40.970> in<00:31:41.120> 2017<00:31:41.870> when 00:31:42.610 --> 00:31:42.620 align:start position:0% started 2013 but formalized in 2017 when 00:31:42.620 --> 00:31:44.220 align:start position:0% started 2013 but formalized in 2017 when would<00:31:42.770> 6<00:31:42.950> million<00:31:43.310> over<00:31:43.490> the<00:31:43.520> past<00:31:43.580> six<00:31:44.000> years 00:31:44.220 --> 00:31:44.230 align:start position:0% would 6 million over the past six years 00:31:44.230 --> 00:31:46.210 align:start position:0% would 6 million over the past six years mostly<00:31:45.230> funded<00:31:45.440> by<00:31:45.530> the<00:31:45.650> night<00:31:45.860> in<00:31:45.950> the<00:31:46.010> Sun 00:31:46.210 --> 00:31:46.220 align:start position:0% mostly funded by the night in the Sun 00:31:46.220 --> 00:31:47.800 align:start position:0% mostly funded by the night in the Sun foundation<00:31:46.760> although<00:31:47.150> in<00:31:47.270> the<00:31:47.360> past<00:31:47.600> year 00:31:47.800 --> 00:31:47.810 align:start position:0% foundation although in the past year 00:31:47.810 --> 00:31:49.240 align:start position:0% foundation although in the past year we've<00:31:47.930> gotten<00:31:48.200> a<00:31:48.260> lot<00:31:48.380> of<00:31:48.440> individual<00:31:49.100> and 00:31:49.240 --> 00:31:49.250 align:start position:0% we've gotten a lot of individual and 00:31:49.250 --> 00:31:52.600 align:start position:0% we've gotten a lot of individual and organizational<00:31:49.880> contributions<00:31:51.370> our<00:31:52.370> current 00:31:52.600 --> 00:31:52.610 align:start position:0% organizational contributions our current 00:31:52.610 --> 00:31:55.930 align:start position:0% organizational contributions our current operating<00:31:52.880> budget<00:31:53.150> is<00:31:53.240> $300,000<00:31:54.850> we<00:31:55.850> have 00:31:55.930 --> 00:31:55.940 align:start position:0% operating budget is $300,000 we have 00:31:55.940 --> 00:31:57.130 align:start position:0% operating budget is $300,000 we have like<00:31:56.090> forty<00:31:56.390> thousand<00:31:56.720> left<00:31:56.810> in<00:31:56.930> the<00:31:56.990> bank 00:31:57.130 --> 00:31:57.140 align:start position:0% like forty thousand left in the bank 00:31:57.140 --> 00:31:59.890 align:start position:0% like forty thousand left in the bank right<00:31:57.380> now<00:31:57.530> this<00:31:58.460> is<00:31:58.640> like<00:31:58.790> classic<00:31:59.450> non 00:31:59.890 --> 00:31:59.900 align:start position:0% right now this is like classic non 00:31:59.900 --> 00:32:02.920 align:start position:0% right now this is like classic non profit<00:32:00.290> like<00:32:00.650> always<00:32:01.160> writing<00:32:01.550> grants<00:32:01.930> always 00:32:02.920 --> 00:32:02.930 align:start position:0% profit like always writing grants always 00:32:02.930 --> 00:32:05.350 align:start position:0% profit like always writing grants always like<00:32:03.170> getting<00:32:03.590> people<00:32:03.860> involved<00:32:04.430> in<00:32:04.580> getting 00:32:05.350 --> 00:32:05.360 align:start position:0% like getting people involved in getting 00:32:05.360 --> 00:32:08.260 align:start position:0% like getting people involved in getting donations<00:32:06.370> so<00:32:07.370> how<00:32:07.490> do<00:32:07.550> we<00:32:07.670> do<00:32:07.820> this<00:32:08.000> well<00:32:08.180> it's 00:32:08.260 --> 00:32:08.270 align:start position:0% donations so how do we do this well it's 00:32:08.270 --> 00:32:10.180 align:start position:0% donations so how do we do this well it's community<00:32:09.230> right<00:32:09.470> it's<00:32:09.680> not<00:32:09.770> about<00:32:09.830> the<00:32:10.100> money 00:32:10.180 --> 00:32:10.190 align:start position:0% community right it's not about the money 00:32:10.190 --> 00:32:12.040 align:start position:0% community right it's not about the money it's<00:32:10.340> about<00:32:10.520> people<00:32:11.000> caring<00:32:11.210> about<00:32:11.360> this<00:32:11.690> and 00:32:12.040 --> 00:32:12.050 align:start position:0% it's about people caring about this and 00:32:12.050 --> 00:32:15.100 align:start position:0% it's about people caring about this and contributing<00:32:12.680> time<00:32:13.330> so<00:32:14.330> our<00:32:14.360> values<00:32:14.990> our 00:32:15.100 --> 00:32:15.110 align:start position:0% contributing time so our values our 00:32:15.110 --> 00:32:17.650 align:start position:0% contributing time so our values our community<00:32:15.500> first<00:32:15.910> transparently<00:32:16.910> funded<00:32:17.300> and 00:32:17.650 --> 00:32:17.660 align:start position:0% community first transparently funded and 00:32:17.660 --> 00:32:18.850 align:start position:0% community first transparently funded and I<00:32:17.750> have<00:32:17.840> open<00:32:18.110> governance<00:32:18.380> so<00:32:18.650> we<00:32:18.740> have<00:32:18.830> a 00:32:18.850 --> 00:32:18.860 align:start position:0% I have open governance so we have a 00:32:18.860 --> 00:32:22.010 align:start position:0% I have open governance so we have a series<00:32:19.040> of<00:32:19.190> working<00:32:19.520> group<00:32:19.730> so<00:32:19.760> you<00:32:19.910> can 00:32:22.010 --> 00:32:22.020 align:start position:0% series of working group so you can 00:32:22.020 --> 00:32:24.510 align:start position:0% series of working group so you can it<00:32:23.020> all<00:32:23.140> comes<00:32:23.320> down<00:32:23.410> to<00:32:23.530> making<00:32:24.130> good 00:32:24.510 --> 00:32:24.520 align:start position:0% it all comes down to making good 00:32:24.520 --> 00:32:27.420 align:start position:0% it all comes down to making good software<00:32:25.450> and<00:32:25.780> giving<00:32:26.650> it<00:32:26.740> away<00:32:26.830> for<00:32:26.920> free<00:32:27.100> and 00:32:27.420 --> 00:32:27.430 align:start position:0% software and giving it away for free and 00:32:27.430 --> 00:32:30.450 align:start position:0% software and giving it away for free and that<00:32:27.930> Network<00:32:28.930> effect<00:32:29.350> of<00:32:29.800> that<00:32:30.070> good 00:32:30.450 --> 00:32:30.460 align:start position:0% that Network effect of that good 00:32:30.460 --> 00:32:32.220 align:start position:0% that Network effect of that good software<00:32:30.910> and<00:32:31.000> people<00:32:31.270> care<00:32:31.510> about<00:32:31.750> the 00:32:32.220 --> 00:32:32.230 align:start position:0% software and people care about the 00:32:32.230 --> 00:32:34.050 align:start position:0% software and people care about the scientific<00:32:32.770> values<00:32:33.070> of<00:32:33.190> that<00:32:33.310> software<00:32:33.640> the 00:32:34.050 --> 00:32:34.060 align:start position:0% scientific values of that software the 00:32:34.060 --> 00:32:35.820 align:start position:0% scientific values of that software the computer<00:32:34.450> scientist<00:32:35.020> that<00:32:35.230> software<00:32:35.500> is<00:32:35.680> like 00:32:35.820 --> 00:32:35.830 align:start position:0% computer scientist that software is like 00:32:35.830 --> 00:32:39.030 align:start position:0% computer scientist that software is like it's<00:32:36.010> people<00:32:36.160> excited<00:32:37.260> and<00:32:38.260> together<00:32:38.650> we<00:32:38.860> can 00:32:39.030 --> 00:32:39.040 align:start position:0% it's people excited and together we can 00:32:39.040 --> 00:32:43.050 align:start position:0% it's people excited and together we can build<00:32:39.550> this<00:32:40.060> amazing<00:32:41.070> applications<00:32:42.070> and<00:32:42.430> work 00:32:43.050 --> 00:32:43.060 align:start position:0% build this amazing applications and work 00:32:43.060 --> 00:32:44.370 align:start position:0% build this amazing applications and work together<00:32:43.210> so<00:32:43.600> that's<00:32:43.750> kind<00:32:43.930> of<00:32:43.960> the<00:32:44.080> vision 00:32:44.370 --> 00:32:44.380 align:start position:0% together so that's kind of the vision 00:32:44.380 --> 00:32:47.850 align:start position:0% together so that's kind of the vision for<00:32:44.530> our<00:32:44.590> future<00:32:46.440> so<00:32:47.440> as<00:32:47.470> we<00:32:47.620> go<00:32:47.740> from 00:32:47.850 --> 00:32:47.860 align:start position:0% for our future so as we go from 00:32:47.860 --> 00:32:50.820 align:start position:0% for our future so as we go from networking<00:32:48.600> to<00:32:49.600> collaboration<00:32:50.320> this<00:32:50.470> is<00:32:50.620> kind 00:32:50.820 --> 00:32:50.830 align:start position:0% networking to collaboration this is kind 00:32:50.830 --> 00:32:53.070 align:start position:0% networking to collaboration this is kind of<00:32:50.890> our<00:32:51.460> focus<00:32:52.030> for<00:32:52.240> the<00:32:52.360> next<00:32:52.450> year<00:32:52.780> is<00:32:52.930> how 00:32:53.070 --> 00:32:53.080 align:start position:0% of our focus for the next year is how 00:32:53.080 --> 00:32:55.500 align:start position:0% of our focus for the next year is how can<00:32:53.290> we<00:32:53.320> get<00:32:53.770> developers<00:32:54.310> from<00:32:55.000> networking 00:32:55.500 --> 00:32:55.510 align:start position:0% can we get developers from networking 00:32:55.510 --> 00:32:57.510 align:start position:0% can we get developers from networking and<00:32:56.020> I<00:32:56.050> don't<00:32:56.320> mean<00:32:56.440> like<00:32:56.560> peer<00:32:57.400> to<00:32:57.460> peer 00:32:57.510 --> 00:32:57.520 align:start position:0% and I don't mean like peer to peer 00:32:57.520 --> 00:32:58.830 align:start position:0% and I don't mean like peer to peer networking<00:32:57.940> by<00:32:58.120> the<00:32:58.180> way<00:32:58.300> and<00:32:58.630> had<00:32:58.810> a 00:32:58.830 --> 00:32:58.840 align:start position:0% networking by the way and had a 00:32:58.840 --> 00:33:01.770 align:start position:0% networking by the way and had a conference<00:32:59.170> networking<00:33:00.060> to<00:33:01.060> cooperation<00:33:01.630> for 00:33:01.770 --> 00:33:01.780 align:start position:0% conference networking to cooperation for 00:33:01.780 --> 00:33:05.630 align:start position:0% conference networking to cooperation for coordination<00:33:02.080> coalition<00:33:02.680> and<00:33:02.770> collaboration 00:33:05.630 --> 00:33:05.640 align:start position:0% 00:33:05.640 --> 00:33:08.820 align:start position:0% so<00:33:06.640> our<00:33:06.910> plan<00:33:07.150> over<00:33:07.960> the<00:33:08.020> next<00:33:08.230> few<00:33:08.500> months<00:33:08.650> to 00:33:08.820 --> 00:33:08.830 align:start position:0% so our plan over the next few months to 00:33:08.830 --> 00:33:10.710 align:start position:0% so our plan over the next few months to the<00:33:09.010> build<00:33:09.160> a<00:33:09.250> membership<00:33:09.610> model<00:33:09.760> and<00:33:10.240> next 00:33:10.710 --> 00:33:10.720 align:start position:0% the build a membership model and next 00:33:10.720 --> 00:33:12.570 align:start position:0% the build a membership model and next year<00:33:10.810> have<00:33:10.930> to<00:33:11.020> move<00:33:11.140> an<00:33:11.320> event<00:33:11.560> and<00:33:11.770> start<00:33:12.550> a 00:33:12.570 --> 00:33:12.580 align:start position:0% year have to move an event and start a 00:33:12.580 --> 00:33:16.170 align:start position:0% year have to move an event and start a community<00:33:12.790> grants<00:33:13.240> program<00:33:13.600> and<00:33:15.150> you<00:33:16.150> know 00:33:16.170 --> 00:33:16.180 align:start position:0% community grants program and you know 00:33:16.180 --> 00:33:17.220 align:start position:0% community grants program and you know people<00:33:16.360> say<00:33:16.570> we're<00:33:16.720> standing<00:33:17.050> on<00:33:17.170> the 00:33:17.220 --> 00:33:17.230 align:start position:0% people say we're standing on the 00:33:17.230 --> 00:33:19.680 align:start position:0% people say we're standing on the shoulders<00:33:17.530> of<00:33:17.560> giants<00:33:17.940> I'd<00:33:18.940> say<00:33:19.150> like<00:33:19.330> we 00:33:19.680 --> 00:33:19.690 align:start position:0% shoulders of giants I'd say like we 00:33:19.690 --> 00:33:21.120 align:start position:0% shoulders of giants I'd say like we invite<00:33:19.960> the<00:33:20.080> giants<00:33:20.470> and<00:33:20.620> come<00:33:20.800> sit<00:33:20.980> at<00:33:21.070> the 00:33:21.120 --> 00:33:21.130 align:start position:0% invite the giants and come sit at the 00:33:21.130 --> 00:33:29.840 align:start position:0% invite the giants and come sit at the table 00:33:29.840 --> 00:33:29.850 align:start position:0% 00:33:29.850 --> 00:33:32.490 align:start position:0% questions<00:33:30.850> questions<00:33:31.059> we<00:33:31.960> have<00:33:32.080> we<00:33:32.200> have<00:33:32.320> time 00:33:32.490 --> 00:33:32.500 align:start position:0% questions questions we have we have time 00:33:32.500 --> 00:33:36.419 align:start position:0% questions questions we have we have time for<00:33:32.529> two<00:33:32.860> questions<00:33:34.769> he<00:33:35.769> took<00:33:35.950> aim<00:33:36.129> there<00:33:36.370> are 00:33:36.419 --> 00:33:36.429 align:start position:0% for two questions he took aim there are 00:33:36.429 --> 00:33:38.730 align:start position:0% for two questions he took aim there are no<00:33:36.519> question<00:33:36.879> I'll<00:33:37.029> even<00:33:37.240> ask<00:33:37.450> one<00:33:37.809> quick<00:33:38.049> link 00:33:38.730 --> 00:33:38.740 align:start position:0% no question I'll even ask one quick link 00:33:38.740 --> 00:33:40.049 align:start position:0% no question I'll even ask one quick link when<00:33:38.860> you<00:33:38.889> receive<00:33:39.279> the<00:33:39.370> grants<00:33:39.639> from<00:33:39.970> the 00:33:40.049 --> 00:33:40.059 align:start position:0% when you receive the grants from the 00:33:40.059 --> 00:33:44.940 align:start position:0% when you receive the grants from the Foundation's<00:33:40.629> what<00:33:40.929> was<00:33:41.139> the<00:33:41.799> start<00:33:43.950> they're 00:33:44.940 --> 00:33:44.950 align:start position:0% Foundation's what was the start they're 00:33:44.950 --> 00:33:46.680 align:start position:0% Foundation's what was the start they're interested<00:33:45.309> because<00:33:45.399> of<00:33:45.639> scientific<00:33:46.059> itching 00:33:46.680 --> 00:33:46.690 align:start position:0% interested because of scientific itching 00:33:46.690 --> 00:33:49.740 align:start position:0% interested because of scientific itching so<00:33:47.409> most<00:33:47.830> of<00:33:48.039> I<00:33:48.309> think<00:33:48.639> like<00:33:48.850> 1.3<00:33:49.330> million<00:33:49.539> of 00:33:49.740 --> 00:33:49.750 align:start position:0% so most of I think like 1.3 million of 00:33:49.750 --> 00:33:56.149 align:start position:0% so most of I think like 1.3 million of that<00:33:49.779> money<00:33:49.960> came<00:33:50.350> from<00:33:50.730> scientific<00:33:51.730> ditch 00:33:56.149 --> 00:33:56.159 align:start position:0% 00:33:56.159 --> 00:33:58.049 align:start position:0% there's<00:33:57.159> a<00:33:57.190> lot<00:33:57.309> of<00:33:57.399> money<00:33:57.549> in<00:33:57.789> the 00:33:58.049 --> 00:33:58.059 align:start position:0% there's a lot of money in the 00:33:58.059 --> 00:33:59.399 align:start position:0% there's a lot of money in the reproducible<00:33:58.600> research<00:33:58.659> case<00:33:59.080> that<00:33:59.289> are 00:33:59.399 --> 00:33:59.409 align:start position:0% reproducible research case that are 00:33:59.409 --> 00:34:07.640 align:start position:0% reproducible research case that are still<00:33:59.590> going<00:33:59.740> after<00:33:59.950> grants<00:34:00.309> in<00:34:00.700> that<00:34:00.909> space 00:34:07.640 --> 00:34:07.650 align:start position:0% 00:34:07.650 --> 00:34:10.619 align:start position:0% in<00:34:08.060> brain 00:34:10.619 --> 00:34:10.629 align:start position:0% in brain 00:34:10.629 --> 00:34:14.309 align:start position:0% in brain they<00:34:11.289> found<00:34:11.529> us<00:34:12.569> they're<00:34:13.569> using<00:34:13.839> them<00:34:14.019> open 00:34:14.309 --> 00:34:14.319 align:start position:0% they found us they're using them open 00:34:14.319 --> 00:34:15.450 align:start position:0% they found us they're using them open source<00:34:14.499> modules<00:34:14.889> and<00:34:15.039> they're<00:34:15.159> contributing 00:34:15.450 --> 00:34:15.460 align:start position:0% source modules and they're contributing 00:34:15.460 --> 00:34:17.249 align:start position:0% source modules and they're contributing to<00:34:15.729> the<00:34:15.940> code<00:34:16.149> it's<00:34:16.359> all<00:34:16.509> open<00:34:17.109> source 00:34:17.249 --> 00:34:17.259 align:start position:0% to the code it's all open source 00:34:17.259 --> 00:34:21.389 align:start position:0% to the code it's all open source community<00:34:18.869> so<00:34:19.869> we<00:34:19.929> have<00:34:20.919> given<00:34:21.190> them<00:34:21.249> any 00:34:21.389 --> 00:34:21.399 align:start position:0% community so we have given them any 00:34:21.399 --> 00:34:25.319 align:start position:0% community so we have given them any money<00:34:22.919> that's<00:34:23.919> just<00:34:24.279> they<00:34:24.639> found<00:34:24.940> us 00:34:25.319 --> 00:34:25.329 align:start position:0% money that's just they found us 00:34:25.329 --> 00:34:28.559 align:start position:0% money that's just they found us conferences<00:34:26.009> yeah<00:34:27.269> that's<00:34:28.269> it 00:34:28.559 --> 00:34:28.569 align:start position:0% conferences yeah that's it 00:34:28.569 --> 00:34:34.919 align:start position:0% conferences yeah that's it yeah<00:34:29.259> thank<00:34:30.039> you<00:34:30.129> guys<00:34:32.220> so<00:34:33.220> I'm<00:34:34.179> between<00:34:34.720> an 00:34:34.919 --> 00:34:34.929 align:start position:0% yeah thank you guys so I'm between an 00:34:34.929 --> 00:34:39.719 align:start position:0% yeah thank you guys so I'm between an origin<00:34:35.319> of<00:34:35.649> its<00:34:35.979> status<00:34:38.279> this<00:34:39.279> song<00:34:39.489> is<00:34:39.609> going 00:34:39.719 --> 00:34:39.729 align:start position:0% origin of its status this song is going 00:34:39.729 --> 00:34:44.909 align:start position:0% origin of its status this song is going to<00:34:39.789> be<00:34:39.909> mostly<00:34:40.659> permanent<00:34:41.579> people<00:34:43.829> need<00:34:44.829> to 00:34:44.909 --> 00:34:44.919 align:start position:0% to be mostly permanent people need to 00:34:44.919 --> 00:34:47.249 align:start position:0% to be mostly permanent people need to hear<00:34:45.099> from<00:34:45.279> the<00:34:45.429> front<00:34:45.789> of<00:34:46.259> resource 00:34:47.249 --> 00:34:47.259 align:start position:0% hear from the front of resource 00:34:47.259 --> 00:34:52.680 align:start position:0% hear from the front of resource constrained<00:34:47.649> devices<00:34:50.999> so<00:34:51.999> sentence<00:34:52.359> is<00:34:52.509> a 00:34:52.680 --> 00:34:52.690 align:start position:0% constrained devices so sentence is a 00:34:52.690 --> 00:34:56.969 align:start position:0% constrained devices so sentence is a company<00:34:53.319> that<00:34:54.599> primarily<00:34:55.619> works<00:34:56.619> on<00:34:56.950> a 00:34:56.969 --> 00:34:56.979 align:start position:0% company that primarily works on a 00:34:56.979 --> 00:35:01.970 align:start position:0% company that primarily works on a distributed<00:34:58.229> chat<00:34:59.309> like<00:35:00.309> application 00:35:01.970 --> 00:35:01.980 align:start position:0% distributed chat like application 00:35:01.980 --> 00:35:05.600 align:start position:0% distributed chat like application which<00:35:02.359> targets<00:35:03.359> phones 00:35:05.600 --> 00:35:05.610 align:start position:0% which targets phones 00:35:05.610 --> 00:35:07.930 align:start position:0% which targets phones it's<00:35:06.150> currently<00:35:06.510> heavily<00:35:07.110> multi-building 00:35:07.930 --> 00:35:07.940 align:start position:0% it's currently heavily multi-building 00:35:07.940 --> 00:35:10.359 align:start position:0% it's currently heavily multi-building flies<00:35:08.940> forward 00:35:10.359 --> 00:35:10.369 align:start position:0% flies forward 00:35:10.369 --> 00:35:18.130 align:start position:0% flies forward with<00:35:11.150> its<00:35:11.869> major<00:35:12.079> focus<00:35:12.499> being<00:35:12.880> that<00:35:16.809> we<00:35:17.809> help 00:35:18.130 --> 00:35:18.140 align:start position:0% with its major focus being that we help 00:35:18.140 --> 00:35:22.420 align:start position:0% with its major focus being that we help define<00:35:18.440> the<00:35:18.910> 2.93<00:35:19.910> inspect<00:35:21.039> and<00:35:22.039> there's<00:35:22.279> also 00:35:22.420 --> 00:35:22.430 align:start position:0% define the 2.93 inspect and there's also 00:35:22.430 --> 00:35:24.640 align:start position:0% define the 2.93 inspect and there's also that<00:35:23.329> pursuit<00:35:23.690> of<00:35:23.809> something<00:35:24.229> called<00:35:24.440> what 00:35:24.640 --> 00:35:24.650 align:start position:0% that pursuit of something called what 00:35:24.650 --> 00:35:27.219 align:start position:0% that pursuit of something called what about<00:35:25.249> he<00:35:25.579> could<00:35:25.729> be<00:35:25.849> which<00:35:26.029> is<00:35:26.210> the<00:35:26.420> tool<00:35:27.049> in 00:35:27.219 --> 00:35:27.229 align:start position:0% about he could be which is the tool in 00:35:27.229 --> 00:35:30.160 align:start position:0% about he could be which is the tool in to<00:35:27.380> build<00:35:27.589> to<00:35:28.249> get<00:35:28.430> to<00:35:28.519> build<00:35:28.729> the<00:35:29.479> p2p 00:35:30.160 --> 00:35:30.170 align:start position:0% to build to get to build the p2p 00:35:30.170 --> 00:35:37.210 align:start position:0% to build to get to build the p2p solutions<00:35:30.789> like<00:35:32.079> application<00:35:33.079> level 00:35:37.210 --> 00:35:37.220 align:start position:0% 00:35:37.220 --> 00:35:44.010 align:start position:0% so<00:35:38.650> how<00:35:39.650> does<00:35:41.170> statuses 00:35:44.010 --> 00:35:44.020 align:start position:0% so how does statuses 00:35:44.020 --> 00:35:48.130 align:start position:0% so how does statuses it's<00:35:45.020> a<00:35:45.700> distributed<00:35:46.700> chat<00:35:47.270> application<00:35:47.839> and 00:35:48.130 --> 00:35:48.140 align:start position:0% it's a distributed chat application and 00:35:48.140 --> 00:35:52.210 align:start position:0% it's a distributed chat application and it<00:35:48.560> was<00:35:49.369> robust<00:35:50.000> peer-to-peer<00:35:51.220> stacking 00:35:52.210 --> 00:35:52.220 align:start position:0% it was robust peer-to-peer stacking 00:35:52.220 --> 00:35:59.800 align:start position:0% it was robust peer-to-peer stacking order<00:35:52.430> to<00:35:52.640> will<00:35:53.300> feel<00:35:53.450> it's<00:35:53.630> from<00:35:57.760> the<00:35:58.810> weepy 00:35:59.800 --> 00:35:59.810 align:start position:0% order to will feel it's from the weepy 00:35:59.810 --> 00:36:03.900 align:start position:0% order to will feel it's from the weepy to<00:35:59.960> be<00:36:00.140> is<00:36:01.599> no<00:36:02.599> no<00:36:02.660> sorry 00:36:03.900 --> 00:36:03.910 align:start position:0% to be is no no sorry 00:36:03.910 --> 00:36:07.210 align:start position:0% to be is no no sorry the<00:36:04.910> problem<00:36:05.450> is<00:36:05.540> that<00:36:05.569> the<00:36:05.930> current<00:36:06.220> atrium 00:36:07.210 --> 00:36:07.220 align:start position:0% the problem is that the current atrium 00:36:07.220 --> 00:36:10.030 align:start position:0% the problem is that the current atrium solutions<00:36:08.210> peer-to-peer<00:36:09.140> solutions<00:36:09.710> are<00:36:09.920> not 00:36:10.030 --> 00:36:10.040 align:start position:0% solutions peer-to-peer solutions are not 00:36:10.040 --> 00:36:15.540 align:start position:0% solutions peer-to-peer solutions are not necessarily<00:36:12.430> didn't<00:36:13.430> necessarily<00:36:13.520> feed<00:36:13.970> the 00:36:15.540 --> 00:36:15.550 align:start position:0% necessarily didn't necessarily feed the 00:36:15.550 --> 00:36:19.599 align:start position:0% necessarily didn't necessarily feed the status<00:36:16.550> require<00:36:16.849> separately<00:36:17.359> so<00:36:18.190> we<00:36:19.190> are 00:36:19.599 --> 00:36:19.609 align:start position:0% status require separately so we are 00:36:19.609 --> 00:36:23.740 align:start position:0% status require separately so we are going<00:36:20.000> we<00:36:20.390> need<00:36:21.170> to<00:36:21.410> be<00:36:21.560> which<00:36:22.400> is<00:36:22.700> a<00:36:23.210> wide 00:36:23.740 --> 00:36:23.750 align:start position:0% going we need to be which is a wide 00:36:23.750 --> 00:36:26.380 align:start position:0% going we need to be which is a wide alert<00:36:24.050> actually<00:36:24.829> in<00:36:25.040> swapped<00:36:25.400> components<00:36:26.270> in 00:36:26.380 --> 00:36:26.390 align:start position:0% alert actually in swapped components in 00:36:26.390 --> 00:36:31.450 align:start position:0% alert actually in swapped components in and<00:36:26.510> out<00:36:26.890> it's<00:36:27.940> a<00:36:28.940> transfer<00:36:29.780> support<00:36:30.339> you<00:36:31.339> can 00:36:31.450 --> 00:36:31.460 align:start position:0% and out it's a transfer support you can 00:36:31.460 --> 00:36:41.290 align:start position:0% and out it's a transfer support you can use<00:36:31.640> this<00:36:31.880> B<00:36:32.180> is<00:36:32.480> the<00:36:33.460> new<00:36:34.460> base 00:36:41.290 --> 00:36:41.300 align:start position:0% 00:36:41.300 --> 00:36:43.420 align:start position:0% oh<00:36:41.380> there's<00:36:42.380> so<00:36:42.650> many<00:36:42.710> men<00:36:42.980> in<00:36:43.010> the<00:36:43.280> wheel 00:36:43.420 --> 00:36:43.430 align:start position:0% oh there's so many men in the wheel 00:36:43.430 --> 00:36:46.480 align:start position:0% oh there's so many men in the wheel oftentimes<00:36:44.240> when<00:36:44.450> you're<00:36:44.630> building<00:36:45.400> cured<00:36:46.400> of 00:36:46.480 --> 00:36:46.490 align:start position:0% oftentimes when you're building cured of 00:36:46.490 --> 00:36:48.430 align:start position:0% oftentimes when you're building cured of your<00:36:46.520> application<00:36:47.150> you<00:36:47.510> tend<00:36:47.780> to<00:36:47.869> sort<00:36:48.319> of 00:36:48.430 --> 00:36:48.440 align:start position:0% your application you tend to sort of 00:36:48.440 --> 00:36:50.620 align:start position:0% your application you tend to sort of build<00:36:49.099> up<00:36:49.280> your<00:36:49.430> career<00:36:49.550> start<00:36:49.940> from<00:36:50.390> scratch 00:36:50.620 --> 00:36:50.630 align:start position:0% build up your career start from scratch 00:36:50.630 --> 00:36:55.480 align:start position:0% build up your career start from scratch it's<00:36:51.559> probably<00:36:51.859> not<00:36:51.950> a<00:36:52.010> good<00:36:52.160> idea<00:36:52.270> so<00:36:54.490> and 00:36:55.480 --> 00:36:55.490 align:start position:0% it's probably not a good idea so and 00:36:55.490 --> 00:36:57.700 align:start position:0% it's probably not a good idea so and there's<00:36:56.150> also<00:36:56.329> lots<00:36:56.540> of<00:36:56.690> buying<00:36:56.990> from<00:36:57.380> from 00:36:57.700 --> 00:36:57.710 align:start position:0% there's also lots of buying from from 00:36:57.710 --> 00:37:01.210 align:start position:0% there's also lots of buying from from other<00:36:57.859> projects<00:36:58.280> again<00:36:58.520> itself<00:36:59.950> hold<00:37:00.950> it<00:37:01.069> up 00:37:01.210 --> 00:37:01.220 align:start position:0% other projects again itself hold it up 00:37:01.220 --> 00:37:03.910 align:start position:0% other projects again itself hold it up and<00:37:01.460> the<00:37:02.270> five<00:37:02.480> point<00:37:02.750> which<00:37:02.930> is<00:37:03.109> from 00:37:03.910 --> 00:37:03.920 align:start position:0% and the five point which is from 00:37:03.920 --> 00:37:09.470 align:start position:0% and the five point which is from Langston<00:37:05.230> regional<00:37:06.230> creator 00:37:09.470 --> 00:37:09.480 align:start position:0% 00:37:09.480 --> 00:37:12.390 align:start position:0% so<00:37:10.480> our<00:37:11.170> implementation<00:37:11.890> of<00:37:11.980> the<00:37:12.040> big<00:37:12.190> build 00:37:12.390 --> 00:37:12.400 align:start position:0% so our implementation of the big build 00:37:12.400 --> 00:37:15.000 align:start position:0% so our implementation of the big build using<00:37:13.119> something<00:37:13.599> called<00:37:13.720> name<00:37:14.109> rather<00:37:14.890> than 00:37:15.000 --> 00:37:15.010 align:start position:0% using something called name rather than 00:37:15.010 --> 00:37:16.740 align:start position:0% using something called name rather than that<00:37:15.220> which<00:37:15.400> just<00:37:15.730> want<00:37:15.970> to<00:37:16.030> give<00:37:16.150> us<00:37:16.240> a<00:37:16.359> little 00:37:16.740 --> 00:37:16.750 align:start position:0% that which just want to give us a little 00:37:16.750 --> 00:37:19.040 align:start position:0% that which just want to give us a little bit<00:37:16.930> of<00:37:17.020> props<00:37:17.260> instead<00:37:17.859> of<00:37:17.950> making<00:37:18.160> language 00:37:19.040 --> 00:37:19.050 align:start position:0% bit of props instead of making language 00:37:19.050 --> 00:37:20.849 align:start position:0% bit of props instead of making language haven't<00:37:20.050> sinned 00:37:20.849 --> 00:37:20.859 align:start position:0% haven't sinned 00:37:20.859 --> 00:37:24.960 align:start position:0% haven't sinned try<00:37:21.819> it<00:37:21.880> out<00:37:22.000> it's<00:37:22.390> super<00:37:22.839> fast<00:37:23.309> it's<00:37:24.309> got<00:37:24.460> mega 00:37:24.960 --> 00:37:24.970 align:start position:0% try it out it's super fast it's got mega 00:37:24.970 --> 00:37:28.200 align:start position:0% try it out it's super fast it's got mega browser<00:37:25.210> support<00:37:25.720> and<00:37:26.200> it<00:37:27.160> is<00:37:27.220> they<00:37:27.970> call<00:37:28.119> it 00:37:28.200 --> 00:37:28.210 align:start position:0% browser support and it is they call it 00:37:28.210 --> 00:37:33.599 align:start position:0% browser support and it is they call it super<00:37:28.450> productive<00:37:28.750> but<00:37:31.410> and<00:37:32.410> it<00:37:32.770> also<00:37:32.950> just 00:37:33.599 --> 00:37:33.609 align:start position:0% super productive but and it also just 00:37:33.609 --> 00:37:36.329 align:start position:0% super productive but and it also just got<00:37:33.849> version<00:37:34.240> one<00:37:34.420> took<00:37:35.290> a<00:37:35.349> while<00:37:35.589> but<00:37:35.800> it's 00:37:36.329 --> 00:37:36.339 align:start position:0% got version one took a while but it's 00:37:36.339 --> 00:37:41.010 align:start position:0% got version one took a while but it's here<00:37:37.980> so<00:37:38.980> I<00:37:39.450> want<00:37:40.450> to<00:37:40.510> talk<00:37:40.660> about<00:37:40.780> the 00:37:41.010 --> 00:37:41.020 align:start position:0% here so I want to talk about the 00:37:41.020 --> 00:37:44.730 align:start position:0% here so I want to talk about the challenges<00:37:41.559> so<00:37:41.589> both<00:37:42.520> feet<00:37:43.270> I'm<00:37:44.200> sorry 00:37:44.730 --> 00:37:44.740 align:start position:0% challenges so both feet I'm sorry 00:37:44.740 --> 00:37:49.069 align:start position:0% challenges so both feet I'm sorry peer<00:37:45.609> to<00:37:45.700> peer<00:37:45.819> in<00:37:45.940> general<00:37:46.470> and<00:37:47.730> those<00:37:48.730> arts 00:37:49.069 --> 00:37:49.079 align:start position:0% peer to peer in general and those arts 00:37:49.079 --> 00:37:52.650 align:start position:0% peer to peer in general and those arts scalability<00:37:50.790> so<00:37:51.790> maintain<00:37:52.300> stable 00:37:52.650 --> 00:37:52.660 align:start position:0% scalability so maintain stable 00:37:52.660 --> 00:37:54.900 align:start position:0% scalability so maintain stable connections<00:37:53.170> on<00:37:53.470> in<00:37:53.829> terms<00:37:54.369> of<00:37:54.460> your<00:37:54.609> networks 00:37:54.900 --> 00:37:54.910 align:start position:0% connections on in terms of your networks 00:37:54.910 --> 00:37:57.950 align:start position:0% connections on in terms of your networks it's<00:37:55.150> very<00:37:55.660> challenging<00:37:56.430> that's<00:37:57.430> one<00:37:57.640> of<00:37:57.730> the 00:37:57.950 --> 00:37:57.960 align:start position:0% it's very challenging that's one of the 00:37:57.960 --> 00:38:02.790 align:start position:0% it's very challenging that's one of the biggest<00:37:58.960> major<00:37:59.170> issues<00:38:00.000> scale<00:38:01.000> in<00:38:01.800> hardware 00:38:02.790 --> 00:38:02.800 align:start position:0% biggest major issues scale in hardware 00:38:02.800 --> 00:38:06.210 align:start position:0% biggest major issues scale in hardware being<00:38:02.980> very<00:38:03.190> diverse<00:38:03.579> you<00:38:04.500> can<00:38:05.500> find<00:38:05.859> them<00:38:06.069> a 00:38:06.210 --> 00:38:06.220 align:start position:0% being very diverse you can find them a 00:38:06.220 --> 00:38:07.859 align:start position:0% being very diverse you can find them a few<00:38:06.339> servers<00:38:06.700> or<00:38:07.030> you<00:38:07.150> could<00:38:07.329> be<00:38:07.450> running<00:38:07.750> it 00:38:07.859 --> 00:38:07.869 align:start position:0% few servers or you could be running it 00:38:07.869 --> 00:38:10.980 align:start position:0% few servers or you could be running it on<00:38:08.109> a<00:38:08.380> browser<00:38:08.710> or<00:38:09.250> on<00:38:09.309> your<00:38:09.790> phone<00:38:10.000> so<00:38:10.359> I'm<00:38:10.839> not 00:38:10.980 --> 00:38:10.990 align:start position:0% on a browser or on your phone so I'm not 00:38:10.990 --> 00:38:13.660 align:start position:0% on a browser or on your phone so I'm not convenient<00:38:11.470> you<00:38:12.069> have<00:38:12.250> to<00:38:12.369> go<00:38:12.490> for<00:38:12.730> that 00:38:13.660 --> 00:38:13.670 align:start position:0% convenient you have to go for that 00:38:13.670 --> 00:38:15.700 align:start position:0% convenient you have to go for that this<00:38:13.940> coming<00:38:14.180> of<00:38:14.450> this<00:38:14.660> also<00:38:14.840> a<00:38:15.080> problem 00:38:15.700 --> 00:38:15.710 align:start position:0% this coming of this also a problem 00:38:15.710 --> 00:38:17.320 align:start position:0% this coming of this also a problem there's<00:38:16.340> different<00:38:16.640> solutions<00:38:17.030> for<00:38:17.090> dad 00:38:17.320 --> 00:38:17.330 align:start position:0% there's different solutions for dad 00:38:17.330 --> 00:38:23.170 align:start position:0% there's different solutions for dad there's<00:38:18.400> heaps<00:38:19.400> T<00:38:19.640> residues<00:38:20.500> etc<00:38:21.640> but<00:38:22.640> out<00:38:23.120> of 00:38:23.170 --> 00:38:23.180 align:start position:0% there's heaps T residues etc but out of 00:38:23.180 --> 00:38:28.630 align:start position:0% there's heaps T residues etc but out of those<00:38:23.390> is<00:38:24.320> the<00:38:24.620> only<00:38:25.000> sort<00:38:26.000> of<00:38:27.640> discovery 00:38:28.630 --> 00:38:28.640 align:start position:0% those is the only sort of discovery 00:38:28.640 --> 00:38:33.700 align:start position:0% those is the only sort of discovery mechanism<00:38:29.480> and<00:38:31.000> it<00:38:32.000> is<00:38:32.420> relatively<00:38:33.350> easy<00:38:33.440> to 00:38:33.700 --> 00:38:33.710 align:start position:0% mechanism and it is relatively easy to 00:38:33.710 --> 00:38:34.600 align:start position:0% mechanism and it is relatively easy to Samaritans 00:38:34.600 --> 00:38:34.610 align:start position:0% Samaritans 00:38:34.610 --> 00:38:36.970 align:start position:0% Samaritans although<00:38:35.030> there<00:38:35.210> are<00:38:35.240> ways<00:38:35.750> of<00:38:36.380> going<00:38:36.860> about 00:38:36.970 --> 00:38:36.980 align:start position:0% although there are ways of going about 00:38:36.980 --> 00:38:37.800 align:start position:0% although there are ways of going about it 00:38:37.800 --> 00:38:37.810 align:start position:0% it 00:38:37.810 --> 00:38:40.180 align:start position:0% it g'day<00:38:38.810> Emily<00:38:38.990> a<00:38:39.020> house<00:38:39.230> and<00:38:39.590> fiscally<00:38:40.010> only 00:38:40.180 --> 00:38:40.190 align:start position:0% g'day Emily a house and fiscally only 00:38:40.190 --> 00:38:42.870 align:start position:0% g'day Emily a house and fiscally only entity<00:38:40.580> providing<00:38:41.210> some<00:38:41.650> workarounds<00:38:42.650> or 00:38:42.870 --> 00:38:42.880 align:start position:0% entity providing some workarounds or 00:38:42.880 --> 00:38:44.950 align:start position:0% entity providing some workarounds or solutions<00:38:43.880> when<00:38:44.060> you<00:38:44.150> get<00:38:44.300> to<00:38:44.480> mitigate<00:38:44.810> the 00:38:44.950 --> 00:38:44.960 align:start position:0% solutions when you get to mitigate the 00:38:44.960 --> 00:38:46.300 align:start position:0% solutions when you get to mitigate the seasons 00:38:46.300 --> 00:38:46.310 align:start position:0% seasons 00:38:46.310 --> 00:38:54.780 align:start position:0% seasons that's<00:38:47.000> our<00:38:47.300> problem<00:38:47.720> a<00:38:48.050> problem<00:38:49.010> as<00:38:49.130> well<00:38:53.230> the 00:38:54.780 --> 00:38:54.790 align:start position:0% that's our problem a problem as well the 00:38:54.790 --> 00:38:59.329 align:start position:0% that's our problem a problem as well the what<00:38:55.790> else 00:38:59.329 --> 00:38:59.339 align:start position:0% 00:38:59.339 --> 00:39:02.469 align:start position:0% yep<00:38:59.909> bandit<00:39:00.329> defended<00:39:01.019> it's<00:39:01.169> a<00:39:01.229> big<00:39:01.409> one 00:39:02.469 --> 00:39:02.479 align:start position:0% yep bandit defended it's a big one 00:39:02.479 --> 00:39:05.029 align:start position:0% yep bandit defended it's a big one usually<00:39:03.479> in<00:39:03.630> intronetworks<00:39:04.409> there's<00:39:04.799> a<00:39:04.890> lot 00:39:05.029 --> 00:39:05.039 align:start position:0% usually in intronetworks there's a lot 00:39:05.039 --> 00:39:11.800 align:start position:0% usually in intronetworks there's a lot of<00:39:05.189> traffic<00:39:05.909> and<00:39:06.799> discovery<00:39:07.799> and 00:39:11.800 --> 00:39:11.810 align:start position:0% 00:39:11.810 --> 00:39:16.960 align:start position:0% and<00:39:12.230> then<00:39:12.380> privacy<00:39:12.980> and<00:39:13.070> anonymity<00:39:15.700> you<00:39:16.700> can 00:39:16.960 --> 00:39:16.970 align:start position:0% and then privacy and anonymity you can 00:39:16.970 --> 00:39:19.180 align:start position:0% and then privacy and anonymity you can build<00:39:17.270> that<00:39:17.900> you<00:39:18.080> can<00:39:18.260> encrypt<00:39:18.530> data<00:39:18.650> and 00:39:19.180 --> 00:39:19.190 align:start position:0% build that you can encrypt data and 00:39:19.190 --> 00:39:24.010 align:start position:0% build that you can encrypt data and prevent<00:39:20.150> from<00:39:20.750> it<00:39:20.900> being<00:39:22.690> inspected<00:39:23.690> and 00:39:24.010 --> 00:39:24.020 align:start position:0% prevent from it being inspected and 00:39:24.020 --> 00:39:25.480 align:start position:0% prevent from it being inspected and things<00:39:24.170> like<00:39:24.290> that<00:39:24.350> is<00:39:24.740> still<00:39:24.920> weak<00:39:25.100> a<00:39:25.190> lot<00:39:25.340> of 00:39:25.480 --> 00:39:25.490 align:start position:0% things like that is still weak a lot of 00:39:25.490 --> 00:39:28.990 align:start position:0% things like that is still weak a lot of metadata<00:39:25.970> and<00:39:26.560> usually<00:39:27.560> or<00:39:28.190> sometimes<00:39:28.670> that's 00:39:28.990 --> 00:39:29.000 align:start position:0% metadata and usually or sometimes that's 00:39:29.000 --> 00:39:34.270 align:start position:0% metadata and usually or sometimes that's enough<00:39:29.300> to<00:39:29.540> basically<00:39:31.840> to<00:39:32.840> invalidate<00:39:33.560> every 00:39:34.270 --> 00:39:34.280 align:start position:0% enough to basically to invalidate every 00:39:34.280 --> 00:39:40.330 align:start position:0% enough to basically to invalidate every other<00:39:34.780> security<00:39:35.780> measures<00:39:36.220> happily<00:39:38.710> and<00:39:39.710> then 00:39:40.330 --> 00:39:40.340 align:start position:0% other security measures happily and then 00:39:40.340 --> 00:39:44.500 align:start position:0% other security measures happily and then in<00:39:41.180> order<00:39:41.420> to<00:39:42.370> support<00:39:43.370> the<00:39:43.640> work<00:39:43.880> to<00:39:44.120> run<00:39:44.330> a 00:39:44.500 --> 00:39:44.510 align:start position:0% in order to support the work to run a 00:39:44.510 --> 00:39:46.720 align:start position:0% in order to support the work to run a large<00:39:44.750> computer<00:39:45.590> during<00:39:45.800> a<00:39:45.950> break<00:39:46.160> you<00:39:46.580> need 00:39:46.720 --> 00:39:46.730 align:start position:0% large computer during a break you need 00:39:46.730 --> 00:39:48.940 align:start position:0% large computer during a break you need some<00:39:46.910> sort<00:39:47.060> of<00:39:47.180> incentive<00:39:47.720> Asia<00:39:47.900> I<00:39:48.290> think 00:39:48.940 --> 00:39:48.950 align:start position:0% some sort of incentive Asia I think 00:39:48.950 --> 00:39:51.820 align:start position:0% some sort of incentive Asia I think that's<00:39:49.360> the<00:39:50.360> thing<00:39:50.390> we<00:39:50.720> haven't<00:39:50.900> really<00:39:51.110> saw 00:39:51.820 --> 00:39:51.830 align:start position:0% that's the thing we haven't really saw 00:39:51.830 --> 00:39:55.450 align:start position:0% that's the thing we haven't really saw yet 00:39:55.450 --> 00:39:55.460 align:start position:0% 00:39:55.460 --> 00:39:59.350 align:start position:0% [Music] 00:39:59.350 --> 00:39:59.360 align:start position:0% 00:39:59.360 --> 00:40:03.970 align:start position:0% so<00:40:00.700> this<00:40:01.700> is<00:40:01.940> some<00:40:02.810> solutions<00:40:03.350> to<00:40:03.680> some<00:40:03.950> of 00:40:03.970 --> 00:40:03.980 align:start position:0% so this is some solutions to some of 00:40:03.980 --> 00:40:07.420 align:start position:0% so this is some solutions to some of this<00:40:04.130> problems<00:40:05.200> that<00:40:06.200> I<00:40:06.290> just<00:40:07.070> want<00:40:07.250> to<00:40:07.310> bring 00:40:07.420 --> 00:40:07.430 align:start position:0% this problems that I just want to bring 00:40:07.430 --> 00:40:12.530 align:start position:0% this problems that I just want to bring it<00:40:07.490> up<00:40:07.640> and<00:40:07.790> bring<00:40:08.000> them<00:40:08.120> on<00:40:08.210> there<00:40:08.390> obviously 00:40:12.530 --> 00:40:12.540 align:start position:0% 00:40:12.540 --> 00:40:15.680 align:start position:0% the<00:40:13.490> tree<00:40:14.490> gets<00:40:14.730> to<00:40:14.849> build<00:40:15.000> clients<00:40:15.510> that 00:40:15.680 --> 00:40:15.690 align:start position:0% the tree gets to build clients that 00:40:15.690 --> 00:40:17.329 align:start position:0% the tree gets to build clients that always<00:40:16.349> contribute<00:40:16.829> something<00:40:17.010> to<00:40:17.130> the 00:40:17.329 --> 00:40:17.339 align:start position:0% always contribute something to the 00:40:17.339 --> 00:40:20.390 align:start position:0% always contribute something to the networks<00:40:17.670> there's<00:40:17.940> this<00:40:18.359> idea<00:40:18.570> of<00:40:18.859> my<00:40:19.859> clients 00:40:20.390 --> 00:40:20.400 align:start position:0% networks there's this idea of my clients 00:40:20.400 --> 00:40:25.069 align:start position:0% networks there's this idea of my clients and<00:40:21.079> Realtors<00:40:22.079> and<00:40:22.820> usually<00:40:23.820> that<00:40:24.480> implies 00:40:25.069 --> 00:40:25.079 align:start position:0% and Realtors and usually that implies 00:40:25.079 --> 00:40:28.460 align:start position:0% and Realtors and usually that implies that<00:40:25.109> the<00:40:25.589> client<00:40:26.040> is<00:40:26.220> basically<00:40:27.290> the<00:40:28.290> most 00:40:28.460 --> 00:40:28.470 align:start position:0% that the client is basically the most 00:40:28.470 --> 00:40:32.270 align:start position:0% that the client is basically the most cases<00:40:28.730> leaches<00:40:29.730> data<00:40:30.030> from<00:40:30.359> other<00:40:31.280> bigger 00:40:32.270 --> 00:40:32.280 align:start position:0% cases leaches data from other bigger 00:40:32.280 --> 00:40:34.069 align:start position:0% cases leaches data from other bigger notes<00:40:32.490> in<00:40:32.670> an<00:40:32.790> effort<00:40:33.060> or<00:40:33.300> more<00:40:33.510> powerful 00:40:34.069 --> 00:40:34.079 align:start position:0% notes in an effort or more powerful 00:40:34.079 --> 00:40:35.930 align:start position:0% notes in an effort or more powerful notes<00:40:34.260> and<00:40:34.440> they're<00:40:34.619> usually<00:40:35.520> that<00:40:35.910> doesn't 00:40:35.930 --> 00:40:35.940 align:start position:0% notes and they're usually that doesn't 00:40:35.940 --> 00:40:38.240 align:start position:0% notes and they're usually that doesn't speak<00:40:36.390> scale<00:40:36.750> very<00:40:36.990> well<00:40:37.170> does<00:40:37.500> he<00:40:37.530> have<00:40:37.619> to 00:40:38.240 --> 00:40:38.250 align:start position:0% speak scale very well does he have to 00:40:38.250 --> 00:40:41.390 align:start position:0% speak scale very well does he have to end<00:40:38.579> up<00:40:38.700> with<00:40:38.820> a<00:40:38.880> lot<00:40:39.089> more<00:40:39.800> like<00:40:40.800> lines<00:40:41.099> in<00:40:41.310> the 00:40:41.390 --> 00:40:41.400 align:start position:0% end up with a lot more like lines in the 00:40:41.400 --> 00:40:43.099 align:start position:0% end up with a lot more like lines in the never<00:40:41.579> again<00:40:41.910> than<00:40:42.210> full<00:40:42.420> clients<00:40:42.869> and 00:40:43.099 --> 00:40:43.109 align:start position:0% never again than full clients and 00:40:43.109 --> 00:40:44.990 align:start position:0% never again than full clients and they're<00:40:44.070> only<00:40:44.190> attendant 00:40:44.990 --> 00:40:45.000 align:start position:0% they're only attendant 00:40:45.000 --> 00:40:47.680 align:start position:0% they're only attendant it's<00:40:45.780> very<00:40:45.990> hard<00:40:46.170> to<00:40:46.290> scale<00:40:46.380> during<00:40:46.920> effort<00:40:47.250> so 00:40:47.680 --> 00:40:47.690 align:start position:0% it's very hard to scale during effort so 00:40:47.690 --> 00:40:51.849 align:start position:0% it's very hard to scale during effort so one<00:40:48.690> of<00:40:48.810> those<00:40:48.900> things<00:40:49.109> that<00:40:49.410> I<00:40:49.680> believe<00:40:50.550> that 00:40:51.849 --> 00:40:51.859 align:start position:0% one of those things that I believe that 00:40:51.859 --> 00:40:55.099 align:start position:0% one of those things that I believe that should<00:40:52.859> that<00:40:53.359> peer-to-peer<00:40:54.359> network<00:40:54.869> should 00:40:55.099 --> 00:40:55.109 align:start position:0% should that peer-to-peer network should 00:40:55.109 --> 00:40:57.890 align:start position:0% should that peer-to-peer network should have<00:40:55.320> is<00:40:55.589> the<00:40:56.369> ability<00:40:56.550> of<00:40:56.880> beauty<00:40:57.540> line<00:40:57.720> that 00:40:57.890 --> 00:40:57.900 align:start position:0% have is the ability of beauty line that 00:40:57.900 --> 00:40:59.839 align:start position:0% have is the ability of beauty line that every<00:40:58.079> single<00:40:58.230> resources<00:40:58.829> available<00:40:59.250> to<00:40:59.310> hear 00:40:59.839 --> 00:40:59.849 align:start position:0% every single resources available to hear 00:40:59.849 --> 00:41:03.920 align:start position:0% every single resources available to hear a<00:41:00.089> light<00:41:00.270> client<00:41:00.720> and<00:41:01.579> you<00:41:02.579> can<00:41:02.730> steal<00:41:03.119> serve 00:41:03.920 --> 00:41:03.930 align:start position:0% a light client and you can steal serve 00:41:03.930 --> 00:41:06.560 align:start position:0% a light client and you can steal serve some<00:41:03.960> chunks<00:41:04.680> of<00:41:04.800> data<00:41:04.950> to<00:41:05.339> other<00:41:06.030> peers<00:41:06.300> in<00:41:06.480> a 00:41:06.560 --> 00:41:06.570 align:start position:0% some chunks of data to other peers in a 00:41:06.570 --> 00:41:07.730 align:start position:0% some chunks of data to other peers in a network<00:41:06.869> if<00:41:07.020> we're<00:41:07.170> talking<00:41:07.260> about<00:41:07.410> data 00:41:07.730 --> 00:41:07.740 align:start position:0% network if we're talking about data 00:41:07.740 --> 00:41:10.550 align:start position:0% network if we're talking about data specificity<00:41:08.660> and<00:41:09.660> the<00:41:09.720> probably<00:41:10.290> should<00:41:10.410> do 00:41:10.550 --> 00:41:10.560 align:start position:0% specificity and the probably should do 00:41:10.560 --> 00:41:11.210 align:start position:0% specificity and the probably should do that 00:41:11.210 --> 00:41:11.220 align:start position:0% that 00:41:11.220 --> 00:41:15.859 align:start position:0% that it's<00:41:11.340> gonna<00:41:11.460> help<00:41:12.300> scale<00:41:12.930> them<00:41:14.390> and<00:41:15.390> we<00:41:15.660> also 00:41:15.859 --> 00:41:15.869 align:start position:0% it's gonna help scale them and we also 00:41:15.869 --> 00:41:20.349 align:start position:0% it's gonna help scale them and we also wish<00:41:16.440> it<00:41:16.590> also<00:41:16.800> sold<00:41:17.130> the<00:41:18.290> patientís 00:41:20.349 --> 00:41:20.359 align:start position:0% wish it also sold the patientís 00:41:20.359 --> 00:41:23.440 align:start position:0% wish it also sold the patientís there<00:41:21.359> are<00:41:21.450> several<00:41:21.630> projects<00:41:22.140> but<00:41:22.430> and 00:41:23.440 --> 00:41:23.450 align:start position:0% there are several projects but and 00:41:23.450 --> 00:41:26.180 align:start position:0% there are several projects but and obviously<00:41:24.450> this<00:41:24.840> two<00:41:25.050> things<00:41:25.290> are<00:41:25.500> not<00:41:25.650> too 00:41:26.180 --> 00:41:26.190 align:start position:0% obviously this two things are not too 00:41:26.190 --> 00:41:41.630 align:start position:0% obviously this two things are not too exclusive<00:41:26.430> there<00:41:26.910> every<00:41:27.840> weekend 00:41:41.630 --> 00:41:41.640 align:start position:0% 00:41:41.640 --> 00:41:43.890 align:start position:0% yeah<00:41:42.640> that<00:41:42.880> looks<00:41:43.030> other<00:41:43.210> time<00:41:43.540> which<00:41:43.780> is 00:41:43.890 --> 00:41:43.900 align:start position:0% yeah that looks other time which is 00:41:43.900 --> 00:41:46.590 align:start position:0% yeah that looks other time which is great<00:41:44.050> we're<00:41:44.500> back<00:41:44.680> on<00:41:44.800> track<00:41:44.950> now<00:41:45.250> and<00:41:45.600> my 00:41:46.590 --> 00:41:46.600 align:start position:0% great we're back on track now and my 00:41:46.600 --> 00:41:48.360 align:start position:0% great we're back on track now and my question<00:41:47.110> is<00:41:47.140> from<00:41:47.350> the<00:41:47.500> room<00:41:47.680> there<00:41:47.980> already 00:41:48.360 --> 00:41:48.370 align:start position:0% question is from the room there already 00:41:48.370 --> 00:41:55.910 align:start position:0% question is from the room there already I<00:41:51.570> like<00:41:52.570> that<00:41:52.720> something<00:41:52.990> so 00:41:55.910 --> 00:41:55.920 align:start position:0% 00:41:55.920 --> 00:41:58.069 align:start position:0% satis<00:41:56.880> is<00:41:57.000> one<00:41:57.150> of<00:41:57.240> these<00:41:57.390> one<00:41:57.960> of<00:41:57.990> these 00:41:58.069 --> 00:41:58.079 align:start position:0% satis is one of these one of these 00:41:58.079 --> 00:42:00.799 align:start position:0% satis is one of these one of these projects<00:41:58.680> which<00:41:58.829> basically<00:41:59.220> kind<00:42:00.150> of<00:42:00.240> good 00:42:00.799 --> 00:42:00.809 align:start position:0% projects which basically kind of good 00:42:00.809 --> 00:42:04.970 align:start position:0% projects which basically kind of good men<00:42:00.990> estimated<00:42:01.859> 1/2<00:42:02.339> as<00:42:02.519> a<00:42:02.549> result<00:42:03.000> I<00:42:03.980> guess 00:42:04.970 --> 00:42:04.980 align:start position:0% men estimated 1/2 as a result I guess 00:42:04.980 --> 00:42:08.620 align:start position:0% men estimated 1/2 as a result I guess you<00:42:05.130> could<00:42:05.250> say<00:42:05.539> the<00:42:06.539> original<00:42:06.869> problem 00:42:08.620 --> 00:42:08.630 align:start position:0% you could say the original problem 00:42:08.630 --> 00:42:15.020 align:start position:0% you could say the original problem [Music] 00:42:15.020 --> 00:42:15.030 align:start position:0% 00:42:15.030 --> 00:42:17.690 align:start position:0% are<00:42:15.540> you<00:42:15.720> looking<00:42:15.900> at<00:42:16.170> statuses<00:42:16.860> and<00:42:17.490> its 00:42:17.690 --> 00:42:17.700 align:start position:0% are you looking at statuses and its 00:42:17.700 --> 00:42:20.270 align:start position:0% are you looking at statuses and its current<00:42:18.030> development<00:42:18.510> is<00:42:18.570> a<00:42:18.660> way<00:42:18.840> to<00:42:19.190> sort<00:42:20.190> of 00:42:20.270 --> 00:42:20.280 align:start position:0% current development is a way to sort of 00:42:20.280 --> 00:42:22.280 align:start position:0% current development is a way to sort of match<00:42:20.550> that<00:42:20.790> whole<00:42:21.000> thing<00:42:21.150> is<00:42:21.330> it<00:42:21.510> is<00:42:21.900> it<00:42:22.050> it's 00:42:22.280 --> 00:42:22.290 align:start position:0% match that whole thing is it is it it's 00:42:22.290 --> 00:42:30.680 align:start position:0% match that whole thing is it is it it's not<00:42:22.470> explicitly<00:42:25.220> yeah<00:42:27.050> so<00:42:29.240> it's<00:42:30.240> basically 00:42:30.680 --> 00:42:30.690 align:start position:0% not explicitly yeah so it's basically 00:42:30.690 --> 00:42:41.020 align:start position:0% not explicitly yeah so it's basically trying<00:42:31.080> to<00:42:31.200> conceal<00:42:31.590> the<00:42:39.200> like<00:42:40.200> in 00:42:41.020 --> 00:42:41.030 align:start position:0% trying to conceal the like in 00:42:41.030 --> 00:42:49.010 align:start position:0% trying to conceal the like in scalability<00:42:42.030> or<00:42:45.590> okay<00:42:46.590> so<00:42:47.520> yeah<00:42:47.750> status<00:42:48.750> is 00:42:49.010 --> 00:42:49.020 align:start position:0% scalability or okay so yeah status is 00:42:49.020 --> 00:42:52.370 align:start position:0% scalability or okay so yeah status is basically<00:42:49.380> trying<00:42:49.740> to<00:42:50.930> help<00:42:51.930> those 00:42:52.370 --> 00:42:52.380 align:start position:0% basically trying to help those 00:42:52.380 --> 00:42:55.220 align:start position:0% basically trying to help those scalability<00:42:53.280> issues<00:42:53.640> that<00:42:54.300> get<00:42:54.660> run<00:42:54.930> into 00:42:55.220 --> 00:42:55.230 align:start position:0% scalability issues that get run into 00:42:55.230 --> 00:42:59.060 align:start position:0% scalability issues that get run into trying<00:42:55.560> to<00:42:55.830> sort<00:42:56.550> of<00:42:56.640> build<00:42:57.330> its<00:42:57.990> its<00:42:58.410> WeChat 00:42:59.060 --> 00:42:59.070 align:start position:0% trying to sort of build its its WeChat 00:42:59.070 --> 00:43:03.020 align:start position:0% trying to sort of build its its WeChat like<00:42:59.760> application<00:43:00.650> and<00:43:01.650> yeah<00:43:02.400> now<00:43:02.820> it's 00:43:03.020 --> 00:43:03.030 align:start position:0% like application and yeah now it's 00:43:03.030 --> 00:43:08.990 align:start position:0% like application and yeah now it's pushing<00:43:03.690> forward<00:43:07.370> was<00:43:08.370> that<00:43:08.520> the<00:43:08.580> question 00:43:08.990 --> 00:43:09.000 align:start position:0% pushing forward was that the question 00:43:09.000 --> 00:43:17.270 align:start position:0% pushing forward was that the question I<00:43:09.030> was<00:43:09.990> asking 00:43:17.270 --> 00:43:17.280 align:start position:0% 00:43:17.280 --> 00:43:53.370 align:start position:0% [Music] 00:43:53.370 --> 00:43:53.380 align:start position:0% 00:43:53.380 --> 00:43:56.080 align:start position:0% my<00:43:54.380> name<00:43:54.530> is<00:43:54.650> September<00:43:55.280> and<00:43:55.520> I<00:43:55.580> work<00:43:55.880> on<00:43:56.030> the 00:43:56.080 --> 00:43:56.090 align:start position:0% my name is September and I work on the 00:43:56.090 --> 00:43:59.650 align:start position:0% my name is September and I work on the cellar<00:43:56.540> protocol<00:43:58.030> today<00:43:59.030> I'm<00:43:59.300> going<00:43:59.510> to<00:43:59.570> be 00:43:59.650 --> 00:43:59.660 align:start position:0% cellar protocol today I'm going to be 00:43:59.660 --> 00:44:02.410 align:start position:0% cellar protocol today I'm going to be talking<00:43:59.930> about<00:44:00.230> I<00:44:00.890> can<00:44:01.220> trust<00:44:01.430> which<00:44:01.760> is<00:44:01.790> a 00:44:02.410 --> 00:44:02.420 align:start position:0% talking about I can trust which is a 00:44:02.420 --> 00:44:06.970 align:start position:0% talking about I can trust which is a protocol<00:44:03.110> that<00:44:03.520> I<00:44:04.520> wrote<00:44:05.180> back<00:44:05.630> in<00:44:05.660> 2002<00:44:06.650> with 00:44:06.970 --> 00:44:06.980 align:start position:0% protocol that I wrote back in 2002 with 00:44:06.980 --> 00:44:09.190 align:start position:0% protocol that I wrote back in 2002 with a<00:44:07.010> couple<00:44:07.400> colonies<00:44:07.760> of<00:44:07.940> my<00:44:08.150> mario<00:44:08.990> schlosser 00:44:09.190 --> 00:44:09.200 align:start position:0% a couple colonies of my mario schlosser 00:44:09.200 --> 00:44:12.730 align:start position:0% a couple colonies of my mario schlosser and<00:44:09.680> Hector<00:44:09.920> Garcia<00:44:10.250> both<00:44:11.170> and<00:44:12.170> I<00:44:12.440> could<00:44:12.590> trust 00:44:12.730 --> 00:44:12.740 align:start position:0% and Hector Garcia both and I could trust 00:44:12.740 --> 00:44:14.200 align:start position:0% and Hector Garcia both and I could trust is<00:44:12.890> all<00:44:12.980> about<00:44:13.190> trust<00:44:13.430> and<00:44:13.550> reputation<00:44:13.820> in 00:44:14.200 --> 00:44:14.210 align:start position:0% is all about trust and reputation in 00:44:14.210 --> 00:44:16.450 align:start position:0% is all about trust and reputation in peer-to-peer<00:44:14.450> networks<00:44:15.070> and<00:44:16.070> I<00:44:16.130> want<00:44:16.280> to<00:44:16.340> talk 00:44:16.450 --> 00:44:16.460 align:start position:0% peer-to-peer networks and I want to talk 00:44:16.460 --> 00:44:20.920 align:start position:0% peer-to-peer networks and I want to talk about<00:44:16.580> it<00:44:16.790> today<00:44:16.880> because<00:44:19.210> at<00:44:20.210> the<00:44:20.360> time<00:44:20.630> we 00:44:20.920 --> 00:44:20.930 align:start position:0% about it today because at the time we 00:44:20.930 --> 00:44:24.010 align:start position:0% about it today because at the time we worked<00:44:21.230> we<00:44:21.590> were<00:44:21.800> thinking<00:44:22.130> that<00:44:22.930> there<00:44:23.930> was 00:44:24.010 --> 00:44:24.020 align:start position:0% worked we were thinking that there was 00:44:24.020 --> 00:44:27.550 align:start position:0% worked we were thinking that there was going<00:44:24.230> to<00:44:24.320> be<00:44:24.380> whoa<00:44:25.900> I'm<00:44:26.900> gonna<00:44:27.080> walk<00:44:27.350> through 00:44:27.550 --> 00:44:27.560 align:start position:0% going to be whoa I'm gonna walk through 00:44:27.560 --> 00:44:30.610 align:start position:0% going to be whoa I'm gonna walk through basically<00:44:27.950> the<00:44:29.020> context<00:44:30.020> where<00:44:30.350> I<00:44:30.380> didn't 00:44:30.610 --> 00:44:30.620 align:start position:0% basically the context where I didn't 00:44:30.620 --> 00:44:32.710 align:start position:0% basically the context where I didn't trust<00:44:30.770> when<00:44:31.010> I<00:44:31.040> wrote<00:44:31.280> it<00:44:31.450> then<00:44:32.450> I'm<00:44:32.570> gonna 00:44:32.710 --> 00:44:32.720 align:start position:0% trust when I wrote it then I'm gonna 00:44:32.720 --> 00:44:34.660 align:start position:0% trust when I wrote it then I'm gonna walk<00:44:32.900> through<00:44:33.080> the<00:44:33.200> protocol<00:44:33.560> itself<00:44:33.710> then 00:44:34.660 --> 00:44:34.670 align:start position:0% walk through the protocol itself then 00:44:34.670 --> 00:44:37.030 align:start position:0% walk through the protocol itself then I'm<00:44:34.790> gonna<00:44:34.910> walk<00:44:35.090> through<00:44:35.390> why<00:44:35.600> is<00:44:36.530> relevant 00:44:37.030 --> 00:44:37.040 align:start position:0% I'm gonna walk through why is relevant 00:44:37.040 --> 00:44:39.100 align:start position:0% I'm gonna walk through why is relevant today<00:44:37.360> and<00:44:38.360> then<00:44:38.540> I'm<00:44:38.630> going<00:44:38.810> to<00:44:38.840> talk<00:44:38.960> about 00:44:39.100 --> 00:44:39.110 align:start position:0% today and then I'm going to talk about 00:44:39.110 --> 00:44:40.980 align:start position:0% today and then I'm going to talk about some<00:44:39.350> interesting<00:44:39.710> research<00:44:39.860> that<00:44:40.400> we<00:44:40.520> can<00:44:40.640> do 00:44:40.980 --> 00:44:40.990 align:start position:0% some interesting research that we can do 00:44:40.990 --> 00:44:44.490 align:start position:0% some interesting research that we can do going<00:44:41.800> forward<00:44:42.359> that's<00:44:43.359> a<00:44:43.510> lot<00:44:43.690> just<00:44:44.260> a<00:44:44.320> little 00:44:44.490 --> 00:44:44.500 align:start position:0% going forward that's a lot just a little 00:44:44.500 --> 00:44:45.780 align:start position:0% going forward that's a lot just a little bit<00:44:44.589> of<00:44:44.680> time<00:44:44.859> so<00:44:45.070> I'll<00:44:45.160> just<00:44:45.250> grab<00:44:45.460> it<00:44:45.550> jump 00:44:45.780 --> 00:44:45.790 align:start position:0% bit of time so I'll just grab it jump 00:44:45.790 --> 00:44:50.339 align:start position:0% bit of time so I'll just grab it jump right<00:44:45.940> in<00:44:46.119> so<00:44:46.440> we<00:44:47.440> started<00:44:47.859> to<00:44:48.839> the<00:44:49.839> context<00:44:50.230> in 00:44:50.339 --> 00:44:50.349 align:start position:0% right in so we started to the context in 00:44:50.349 --> 00:44:52.250 align:start position:0% right in so we started to the context in which<00:44:50.380> we<00:44:50.500> thought<00:44:51.190> about<00:44:51.310> I<00:44:51.430> can<00:44:51.670> trust<00:44:51.849> was 00:44:52.250 --> 00:44:52.260 align:start position:0% which we thought about I can trust was 00:44:52.260 --> 00:44:55.349 align:start position:0% which we thought about I can trust was back<00:44:53.260> in<00:44:53.410> 2002<00:44:54.190> peer-to-peer<00:44:54.880> file-sharing 00:44:55.349 --> 00:44:55.359 align:start position:0% back in 2002 peer-to-peer file-sharing 00:44:55.359 --> 00:44:58.410 align:start position:0% back in 2002 peer-to-peer file-sharing networks<00:44:56.080> we're<00:44:56.260> getting<00:44:56.530> popular<00:44:57.150> and<00:44:58.150> at 00:44:58.410 --> 00:44:58.420 align:start position:0% networks we're getting popular and at 00:44:58.420 --> 00:45:00.900 align:start position:0% networks we're getting popular and at the<00:44:58.540> time<00:44:58.830> the<00:44:59.830> record<00:44:59.950> industry<00:45:00.490> saw<00:45:00.700> this 00:45:00.900 --> 00:45:00.910 align:start position:0% the time the record industry saw this 00:45:00.910 --> 00:45:02.430 align:start position:0% the time the record industry saw this and<00:45:01.150> started<00:45:01.510> flooding<00:45:01.869> the<00:45:02.200> peer-to-peer 00:45:02.430 --> 00:45:02.440 align:start position:0% and started flooding the peer-to-peer 00:45:02.440 --> 00:45:05.640 align:start position:0% and started flooding the peer-to-peer file-sharing<00:45:02.950> networks<00:45:03.609> with<00:45:04.140> bogus<00:45:05.140> copies 00:45:05.640 --> 00:45:05.650 align:start position:0% file-sharing networks with bogus copies 00:45:05.650 --> 00:45:08.700 align:start position:0% file-sharing networks with bogus copies of<00:45:06.240> music<00:45:07.240> so<00:45:07.450> someone<00:45:07.780> with<00:45:07.930> search<00:45:08.109> for<00:45:08.440> say 00:45:08.700 --> 00:45:08.710 align:start position:0% of music so someone with search for say 00:45:08.710 --> 00:45:11.190 align:start position:0% of music so someone with search for say an<00:45:09.040> anime<00:45:09.520> 8<00:45:09.640> Mile<00:45:09.820> Road<00:45:09.849> and<00:45:10.390> then<00:45:10.960> you<00:45:11.080> get 00:45:11.190 --> 00:45:11.200 align:start position:0% an anime 8 Mile Road and then you get 00:45:11.200 --> 00:45:15.329 align:start position:0% an anime 8 Mile Road and then you get 500<00:45:11.800> razones<00:45:12.130> latter<00:45:12.970> ok<00:45:13.720> you<00:45:14.589> get<00:45:14.770> 500 00:45:15.329 --> 00:45:15.339 align:start position:0% 500 razones latter ok you get 500 00:45:15.339 --> 00:45:20.310 align:start position:0% 500 razones latter ok you get 500 results<00:45:17.339> 400<00:45:18.339> of<00:45:18.700> which<00:45:18.880> were<00:45:19.320> inauthentic 00:45:20.310 --> 00:45:20.320 align:start position:0% results 400 of which were inauthentic 00:45:20.320 --> 00:45:23.190 align:start position:0% results 400 of which were inauthentic copies<00:45:20.740> of<00:45:20.980> the<00:45:21.099> song<00:45:21.780> and<00:45:22.780> so<00:45:22.930> the<00:45:23.050> way<00:45:23.170> that 00:45:23.190 --> 00:45:23.200 align:start position:0% copies of the song and so the way that 00:45:23.200 --> 00:45:24.450 align:start position:0% copies of the song and so the way that they<00:45:23.440> would<00:45:23.560> do<00:45:23.680> that<00:45:23.830> as<00:45:23.980> they<00:45:24.099> would<00:45:24.280> come 00:45:24.450 --> 00:45:24.460 align:start position:0% they would do that as they would come 00:45:24.460 --> 00:45:26.130 align:start position:0% they would do that as they would come into<00:45:24.640> the<00:45:24.820> network<00:45:25.119> with<00:45:25.359> with<00:45:26.020> an 00:45:26.130 --> 00:45:26.140 align:start position:0% into the network with with an 00:45:26.140 --> 00:45:27.810 align:start position:0% into the network with with an adversarial<00:45:26.770> node<00:45:27.040> and<00:45:27.339> start<00:45:27.550> spreading 00:45:27.810 --> 00:45:27.820 align:start position:0% adversarial node and start spreading 00:45:27.820 --> 00:45:30.930 align:start position:0% adversarial node and start spreading that<00:45:28.510> information<00:45:29.170> on<00:45:29.290> the<00:45:29.380> network<00:45:29.580> and<00:45:30.580> we 00:45:30.930 --> 00:45:30.940 align:start position:0% that information on the network and we 00:45:30.940 --> 00:45:35.280 align:start position:0% that information on the network and we saw<00:45:31.119> that<00:45:31.150> at<00:45:31.420> the<00:45:31.510> time<00:45:31.750> and<00:45:32.200> and<00:45:34.140> while<00:45:35.140> it 00:45:35.280 --> 00:45:35.290 align:start position:0% saw that at the time and and while it 00:45:35.290 --> 00:45:37.560 align:start position:0% saw that at the time and and while it was<00:45:35.440> the<00:45:36.070> application<00:45:36.670> itself<00:45:36.940> was<00:45:37.150> somewhat 00:45:37.560 --> 00:45:37.570 align:start position:0% was the application itself was somewhat 00:45:37.570 --> 00:45:39.000 align:start position:0% was the application itself was somewhat interesting<00:45:38.050> what<00:45:38.170> was<00:45:38.320> more<00:45:38.440> interesting<00:45:38.500> to 00:45:39.000 --> 00:45:39.010 align:start position:0% interesting what was more interesting to 00:45:39.010 --> 00:45:42.900 align:start position:0% interesting what was more interesting to us<00:45:39.280> was<00:45:40.060> that<00:45:40.420> we<00:45:40.780> saw<00:45:41.080> at<00:45:41.230> the<00:45:41.260> time<00:45:41.530> them<00:45:41.910> we 00:45:42.900 --> 00:45:42.910 align:start position:0% us was that we saw at the time them we 00:45:42.910 --> 00:45:44.430 align:start position:0% us was that we saw at the time them we felt<00:45:43.150> like<00:45:43.210> peer-to-peer<00:45:43.720> networks<00:45:44.290> would 00:45:44.430 --> 00:45:44.440 align:start position:0% felt like peer-to-peer networks would 00:45:44.440 --> 00:45:46.410 align:start position:0% felt like peer-to-peer networks would start<00:45:44.740> to<00:45:44.830> get<00:45:44.920> very<00:45:45.190> popular<00:45:45.700> and<00:45:45.910> this 00:45:46.410 --> 00:45:46.420 align:start position:0% start to get very popular and this 00:45:46.420 --> 00:45:48.810 align:start position:0% start to get very popular and this problem<00:45:47.020> was<00:45:47.589> not<00:45:47.770> a<00:45:47.800> problem<00:45:48.070> that<00:45:48.430> was<00:45:48.550> just 00:45:48.810 --> 00:45:48.820 align:start position:0% problem was not a problem that was just 00:45:48.820 --> 00:45:50.730 align:start position:0% problem was not a problem that was just about<00:45:49.030> file-sharing<00:45:49.839> this<00:45:50.109> would<00:45:50.260> come<00:45:50.440> up<00:45:50.560> in 00:45:50.730 --> 00:45:50.740 align:start position:0% about file-sharing this would come up in 00:45:50.740 --> 00:45:53.250 align:start position:0% about file-sharing this would come up in lots<00:45:51.670> of<00:45:51.880> different<00:45:51.940> scenarios<00:45:52.750> and<00:45:52.780> we<00:45:53.109> would 00:45:53.250 --> 00:45:53.260 align:start position:0% lots of different scenarios and we would 00:45:53.260 --> 00:45:55.620 align:start position:0% lots of different scenarios and we would want<00:45:53.470> to<00:45:53.589> have<00:45:53.770> a<00:45:53.800> situation<00:45:54.430> in<00:45:54.940> peer-to-peer 00:45:55.620 --> 00:45:55.630 align:start position:0% want to have a situation in peer-to-peer 00:45:55.630 --> 00:46:00.930 align:start position:0% want to have a situation in peer-to-peer and<00:45:56.140> networks<00:45:56.589> in<00:45:57.130> which<00:45:58.410> nodes<00:45:59.940> adversarial 00:46:00.930 --> 00:46:00.940 align:start position:0% and networks in which nodes adversarial 00:46:00.940 --> 00:46:04.620 align:start position:0% and networks in which nodes adversarial nodes<00:46:01.150> could<00:46:01.330> be<00:46:01.570> identified<00:46:02.280> and<00:46:03.630> people 00:46:04.620 --> 00:46:04.630 align:start position:0% nodes could be identified and people 00:46:04.630 --> 00:46:09.420 align:start position:0% nodes could be identified and people could<00:46:04.900> be<00:46:04.930> for<00:46:06.540> good<00:46:07.650> good<00:46:08.650> acting<00:46:09.040> nodes<00:46:09.250> can 00:46:09.420 --> 00:46:09.430 align:start position:0% could be for good good acting nodes can 00:46:09.430 --> 00:46:14.100 align:start position:0% could be for good good acting nodes can be<00:46:09.580> prevented<00:46:10.030> from<00:46:10.890> interacting 00:46:14.100 --> 00:46:14.110 align:start position:0% 00:46:14.110 --> 00:46:16.230 align:start position:0% and<00:46:15.070> so<00:46:15.250> there's<00:46:15.430> a<00:46:15.520> couple<00:46:15.670> of<00:46:15.880> ways<00:46:16.000> of 00:46:16.230 --> 00:46:16.240 align:start position:0% and so there's a couple of ways of 00:46:16.240 --> 00:46:17.430 align:start position:0% and so there's a couple of ways of thinking<00:46:16.270> about<00:46:16.600> doing<00:46:16.870> that<00:46:17.080> I<00:46:17.140> mean<00:46:17.350> the 00:46:17.430 --> 00:46:17.440 align:start position:0% thinking about doing that I mean the 00:46:17.440 --> 00:46:20.850 align:start position:0% thinking about doing that I mean the first<00:46:17.680> is<00:46:17.860> you<00:46:17.980> can<00:46:18.010> imagine<00:46:18.900> just<00:46:19.900> having<00:46:20.620> a 00:46:20.850 --> 00:46:20.860 align:start position:0% first is you can imagine just having a 00:46:20.860 --> 00:46:23.360 align:start position:0% first is you can imagine just having a proof<00:46:21.130> a<00:46:21.730> cryptographic<00:46:22.450> proof<00:46:22.960> that<00:46:23.110> this 00:46:23.360 --> 00:46:23.370 align:start position:0% proof a cryptographic proof that this 00:46:23.370 --> 00:46:27.030 align:start position:0% proof a cryptographic proof that this file<00:46:24.370> is<00:46:24.700> the<00:46:25.210> right<00:46:25.630> file<00:46:25.900> like<00:46:26.140> this<00:46:26.320> song<00:46:26.710> is 00:46:27.030 --> 00:46:27.040 align:start position:0% file is the right file like this song is 00:46:27.040 --> 00:46:31.830 align:start position:0% file is the right file like this song is actually<00:46:30.120> in<00:46:31.120> a<00:46:31.210> lot<00:46:31.330> of<00:46:31.360> cases<00:46:31.600> that's 00:46:31.830 --> 00:46:31.840 align:start position:0% actually in a lot of cases that's 00:46:31.840 --> 00:46:34.050 align:start position:0% actually in a lot of cases that's difficult<00:46:32.050> to<00:46:32.320> do<00:46:32.470> I<00:46:32.500> mean<00:46:32.740> in<00:46:32.860> the<00:46:32.950> case<00:46:32.980> of<00:46:33.340> in 00:46:34.050 --> 00:46:34.060 align:start position:0% difficult to do I mean in the case of in 00:46:34.060 --> 00:46:35.910 align:start position:0% difficult to do I mean in the case of in that<00:46:34.270> case<00:46:34.480> it<00:46:35.080> would<00:46:35.230> be<00:46:35.260> difficult<00:46:35.710> to<00:46:35.800> do 00:46:35.910 --> 00:46:35.920 align:start position:0% that case it would be difficult to do 00:46:35.920 --> 00:46:38.550 align:start position:0% that case it would be difficult to do without<00:46:36.190> say<00:46:37.150> a<00:46:37.330> central<00:46:37.690> authority<00:46:37.840> actually 00:46:38.550 --> 00:46:38.560 align:start position:0% without say a central authority actually 00:46:38.560 --> 00:46:41.400 align:start position:0% without say a central authority actually having<00:46:38.920> to<00:46:39.040> copy<00:46:39.310> a<00:46:39.700> song<00:46:39.970> and<00:46:40.300> that's<00:46:41.260> not 00:46:41.400 --> 00:46:41.410 align:start position:0% having to copy a song and that's not 00:46:41.410 --> 00:46:43.230 align:start position:0% having to copy a song and that's not possible<00:46:41.650> and<00:46:41.980> so<00:46:42.220> the<00:46:42.730> first<00:46:43.000> thing<00:46:43.150> we 00:46:43.230 --> 00:46:43.240 align:start position:0% possible and so the first thing we 00:46:43.240 --> 00:46:45.660 align:start position:0% possible and so the first thing we choose<00:46:43.450> to<00:46:43.570> chose<00:46:43.930> to<00:46:44.080> take<00:46:44.260> was<00:46:44.950> to<00:46:45.280> assign<00:46:45.640> a 00:46:45.660 --> 00:46:45.670 align:start position:0% choose to chose to take was to assign a 00:46:45.670 --> 00:46:48.480 align:start position:0% choose to chose to take was to assign a trust<00:46:46.090> score<00:46:46.480> to<00:46:47.080> every<00:46:47.380> peer<00:46:47.800> in<00:46:48.040> the<00:46:48.160> network 00:46:48.480 --> 00:46:48.490 align:start position:0% trust score to every peer in the network 00:46:48.490 --> 00:46:51.330 align:start position:0% trust score to every peer in the network so<00:46:48.790> for<00:46:49.240> example<00:46:49.690> if<00:46:49.840> if<00:46:50.350> this<00:46:50.770> peer<00:46:51.100> was 00:46:51.330 --> 00:46:51.340 align:start position:0% so for example if if this peer was 00:46:51.340 --> 00:46:53.330 align:start position:0% so for example if if this peer was choosing<00:46:51.790> to<00:46:51.820> download<00:46:52.270> files<00:46:52.450> from<00:46:52.660> either 00:46:53.330 --> 00:46:53.340 align:start position:0% choosing to download files from either 00:46:53.340 --> 00:46:55.980 align:start position:0% choosing to download files from either that<00:46:54.340> geared<00:46:54.700> up<00:46:54.880> here<00:46:55.150> it<00:46:55.240> looks<00:46:55.480> at<00:46:55.630> the<00:46:55.750> pier 00:46:55.980 --> 00:46:55.990 align:start position:0% that geared up here it looks at the pier 00:46:55.990 --> 00:46:58.320 align:start position:0% that geared up here it looks at the pier where<00:46:56.140> that<00:46:56.290> a<00:46:56.320> trust<00:46:56.560> 4.9<00:46:57.340> and<00:46:57.790> chooses<00:46:58.300> to 00:46:58.320 --> 00:46:58.330 align:start position:0% where that a trust 4.9 and chooses to 00:46:58.330 --> 00:47:01.920 align:start position:0% where that a trust 4.9 and chooses to download<00:46:58.780> the<00:46:58.900> file<00:46:59.110> from<00:46:59.320> that<00:46:59.410> gear<00:47:00.570> that<00:47:01.570> I 00:47:01.920 --> 00:47:01.930 align:start position:0% download the file from that gear that I 00:47:01.930 --> 00:47:03.780 align:start position:0% download the file from that gear that I mean<00:47:02.110> it's<00:47:02.800> straightforward<00:47:03.070> but<00:47:03.550> the<00:47:03.580> big 00:47:03.780 --> 00:47:03.790 align:start position:0% mean it's straightforward but the big 00:47:03.790 --> 00:47:06.330 align:start position:0% mean it's straightforward but the big question<00:47:03.910> is<00:47:04.300> how<00:47:04.690> do<00:47:04.750> we<00:47:04.900> come<00:47:05.230> up<00:47:05.260> with<00:47:06.070> that 00:47:06.330 --> 00:47:06.340 align:start position:0% question is how do we come up with that 00:47:06.340 --> 00:47:08.670 align:start position:0% question is how do we come up with that score<00:47:06.760> and<00:47:07.360> I'm<00:47:07.630> going<00:47:07.870> to<00:47:07.960> talk<00:47:08.230> about<00:47:08.380> three 00:47:08.670 --> 00:47:08.680 align:start position:0% score and I'm going to talk about three 00:47:08.680 --> 00:47:10.680 align:start position:0% score and I'm going to talk about three approaches<00:47:09.160> each<00:47:09.370> of<00:47:09.610> which<00:47:09.790> building<00:47:10.150> on<00:47:10.270> top 00:47:10.680 --> 00:47:10.690 align:start position:0% approaches each of which building on top 00:47:10.690 --> 00:47:11.430 align:start position:0% approaches each of which building on top of<00:47:10.810> one<00:47:10.990> another 00:47:11.430 --> 00:47:11.440 align:start position:0% of one another 00:47:11.440 --> 00:47:13.940 align:start position:0% of one another culminating<00:47:12.010> in<00:47:12.430> the<00:47:12.520> eigen<00:47:12.820> trust<00:47:13.000> approach 00:47:13.940 --> 00:47:13.950 align:start position:0% culminating in the eigen trust approach 00:47:13.950 --> 00:47:16.740 align:start position:0% culminating in the eigen trust approach so<00:47:14.950> the<00:47:14.980> first<00:47:15.340> is<00:47:15.520> just<00:47:15.760> using<00:47:15.940> past<00:47:16.300> history 00:47:16.740 --> 00:47:16.750 align:start position:0% so the first is just using past history 00:47:16.750 --> 00:47:18.660 align:start position:0% so the first is just using past history and<00:47:17.620> so<00:47:17.830> the<00:47:18.010> idea<00:47:18.250> is<00:47:18.400> that<00:47:18.430> you<00:47:18.640> have 00:47:18.660 --> 00:47:18.670 align:start position:0% and so the idea is that you have 00:47:18.670 --> 00:47:20.640 align:start position:0% and so the idea is that you have interactions<00:47:19.390> with<00:47:19.480> a<00:47:19.600> peer<00:47:19.960> and<00:47:20.140> if<00:47:20.530> the 00:47:20.640 --> 00:47:20.650 align:start position:0% interactions with a peer and if the 00:47:20.650 --> 00:47:22.860 align:start position:0% interactions with a peer and if the interactions<00:47:21.190> are<00:47:21.280> positive<00:47:21.790> the<00:47:22.000> scores<00:47:22.330> go 00:47:22.860 --> 00:47:22.870 align:start position:0% interactions are positive the scores go 00:47:22.870 --> 00:47:25.320 align:start position:0% interactions are positive the scores go up<00:47:22.900> and<00:47:23.440> if<00:47:24.130> the<00:47:24.280> interactions<00:47:24.850> are<00:47:24.940> negative 00:47:25.320 --> 00:47:25.330 align:start position:0% up and if the interactions are negative 00:47:25.330 --> 00:47:28.500 align:start position:0% up and if the interactions are negative the<00:47:26.140> scores<00:47:26.410> go<00:47:26.560> down<00:47:26.850> and<00:47:27.850> that's<00:47:28.150> a<00:47:28.300> pretty 00:47:28.500 --> 00:47:28.510 align:start position:0% the scores go down and that's a pretty 00:47:28.510 --> 00:47:30.270 align:start position:0% the scores go down and that's a pretty straightforward<00:47:28.780> way<00:47:29.200> that's<00:47:29.440> how<00:47:29.560> we<00:47:29.620> we 00:47:30.270 --> 00:47:30.280 align:start position:0% straightforward way that's how we we 00:47:30.280 --> 00:47:34.320 align:start position:0% straightforward way that's how we we interact<00:47:30.640> in<00:47:30.790> real<00:47:30.970> life<00:47:31.320> and<00:47:32.610> so<00:47:33.610> so<00:47:34.060> we<00:47:34.210> can 00:47:34.320 --> 00:47:34.330 align:start position:0% interact in real life and so so we can 00:47:34.330 --> 00:47:36.150 align:start position:0% interact in real life and so so we can mathematize<00:47:34.810> that<00:47:35.050> by<00:47:35.170> creating<00:47:35.560> a<00:47:35.620> vector<00:47:36.010> of 00:47:36.150 --> 00:47:36.160 align:start position:0% mathematize that by creating a vector of 00:47:36.160 --> 00:47:39.390 align:start position:0% mathematize that by creating a vector of peers<00:47:36.970> we'll<00:47:37.270> call<00:47:37.630> this<00:47:37.900> peer<00:47:38.380> peer<00:47:38.770> I<00:47:38.830> and 00:47:39.390 --> 00:47:39.400 align:start position:0% peers we'll call this peer peer I and 00:47:39.400 --> 00:47:42.840 align:start position:0% peers we'll call this peer peer I and then<00:47:39.970> therefore<00:47:40.450> this<00:47:41.230> this<00:47:41.560> trust<00:47:42.460> vector 00:47:42.840 --> 00:47:42.850 align:start position:0% then therefore this this trust vector 00:47:42.850 --> 00:47:46.680 align:start position:0% then therefore this this trust vector would<00:47:43.000> be<00:47:43.060> CI<00:47:43.480> the<00:47:44.380> vector<00:47:45.220> of<00:47:45.420> opinions<00:47:46.420> that 00:47:46.680 --> 00:47:46.690 align:start position:0% would be CI the vector of opinions that 00:47:46.690 --> 00:47:49.140 align:start position:0% would be CI the vector of opinions that this<00:47:46.930> PRI<00:47:47.320> has<00:47:47.740> of<00:47:48.130> the<00:47:48.430> other<00:47:48.610> peers<00:47:48.910> on<00:47:49.090> the 00:47:49.140 --> 00:47:49.150 align:start position:0% this PRI has of the other peers on the 00:47:49.150 --> 00:47:51.810 align:start position:0% this PRI has of the other peers on the network<00:47:49.920> now<00:47:50.920> the<00:47:50.980> problem<00:47:51.370> with<00:47:51.430> this<00:47:51.610> is 00:47:51.810 --> 00:47:51.820 align:start position:0% network now the problem with this is 00:47:51.820 --> 00:47:54.640 align:start position:0% network now the problem with this is that<00:47:52.530> you<00:47:53.530> only<00:47:53.770> have 00:47:54.640 --> 00:47:54.650 align:start position:0% that you only have 00:47:54.650 --> 00:47:56.620 align:start position:0% that you only have with<00:47:55.039> a<00:47:55.069> small<00:47:55.460> number<00:47:55.700> of<00:47:55.849> peers<00:47:56.329> on<00:47:56.509> the 00:47:56.620 --> 00:47:56.630 align:start position:0% with a small number of peers on the 00:47:56.630 --> 00:47:58.329 align:start position:0% with a small number of peers on the network<00:47:56.960> but<00:47:57.380> there's<00:47:57.559> a<00:47:57.650> lot<00:47:57.859> of<00:47:58.009> peers<00:47:58.220> on 00:47:58.329 --> 00:47:58.339 align:start position:0% network but there's a lot of peers on 00:47:58.339 --> 00:48:00.460 align:start position:0% network but there's a lot of peers on the<00:47:58.369> network<00:47:58.789> and<00:47:59.569> so<00:47:59.779> you<00:47:59.839> don't<00:48:00.019> have<00:48:00.140> enough 00:48:00.460 --> 00:48:00.470 align:start position:0% the network and so you don't have enough 00:48:00.470 --> 00:48:04.509 align:start position:0% the network and so you don't have enough coverage<00:48:00.890> with<00:48:01.490> just<00:48:01.730> past<00:48:02.329> history<00:48:03.400> so<00:48:04.400> the 00:48:04.509 --> 00:48:04.519 align:start position:0% coverage with just past history so the 00:48:04.519 --> 00:48:07.690 align:start position:0% coverage with just past history so the natural<00:48:04.670> thing<00:48:04.910> to<00:48:05.059> do<00:48:05.359> is<00:48:05.690> to<00:48:06.220> ask<00:48:07.220> friends 00:48:07.690 --> 00:48:07.700 align:start position:0% natural thing to do is to ask friends 00:48:07.700 --> 00:48:10.809 align:start position:0% natural thing to do is to ask friends ask<00:48:08.150> a<00:48:08.599> friend<00:48:08.990> of<00:48:09.200> a<00:48:09.289> friend<00:48:09.400> this<00:48:10.400> is<00:48:10.609> also 00:48:10.809 --> 00:48:10.819 align:start position:0% ask a friend of a friend this is also 00:48:10.819 --> 00:48:12.309 align:start position:0% ask a friend of a friend this is also what<00:48:11.150> we<00:48:11.180> do<00:48:11.420> in<00:48:11.539> real<00:48:11.660> life<00:48:11.720> when<00:48:12.049> we<00:48:12.140> don't 00:48:12.309 --> 00:48:12.319 align:start position:0% what we do in real life when we don't 00:48:12.319 --> 00:48:14.109 align:start position:0% what we do in real life when we don't have<00:48:12.410> enough<00:48:12.499> coverage<00:48:12.829> and<00:48:13.430> we<00:48:13.940> can 00:48:14.109 --> 00:48:14.119 align:start position:0% have enough coverage and we can 00:48:14.119 --> 00:48:16.180 align:start position:0% have enough coverage and we can mathematize<00:48:14.599> it<00:48:14.839> pretty<00:48:15.559> straightforwardly 00:48:16.180 --> 00:48:16.190 align:start position:0% mathematize it pretty straightforwardly 00:48:16.190 --> 00:48:17.620 align:start position:0% mathematize it pretty straightforwardly so<00:48:16.309> we<00:48:16.460> ask<00:48:16.819> a<00:48:17.089> friend 00:48:17.620 --> 00:48:17.630 align:start position:0% so we ask a friend 00:48:17.630 --> 00:48:20.319 align:start position:0% so we ask a friend what<00:48:18.259> they<00:48:18.410> think<00:48:18.470> about<00:48:18.769> their<00:48:19.069> friends<00:48:19.490> and 00:48:20.319 --> 00:48:20.329 align:start position:0% what they think about their friends and 00:48:20.329 --> 00:48:23.140 align:start position:0% what they think about their friends and we<00:48:20.869> wait<00:48:21.349> their<00:48:22.069> opinion<00:48:22.490> of<00:48:22.609> their<00:48:22.730> friends 00:48:23.140 --> 00:48:23.150 align:start position:0% we wait their opinion of their friends 00:48:23.150 --> 00:48:26.789 align:start position:0% we wait their opinion of their friends by<00:48:23.749> how<00:48:23.930> much<00:48:24.079> we<00:48:24.259> trust<00:48:24.499> them<00:48:25.089> so<00:48:26.089> this<00:48:26.240> is<00:48:26.390> CI 00:48:26.789 --> 00:48:26.799 align:start position:0% by how much we trust them so this is CI 00:48:26.799 --> 00:48:30.849 align:start position:0% by how much we trust them so this is CI the<00:48:27.799> opinion<00:48:28.190> vector<00:48:28.490> of<00:48:28.609> PRI<00:48:28.940> and<00:48:29.480> this<00:48:30.170> is<00:48:30.349> CJ 00:48:30.849 --> 00:48:30.859 align:start position:0% the opinion vector of PRI and this is CJ 00:48:30.859 --> 00:48:35.380 align:start position:0% the opinion vector of PRI and this is CJ the<00:48:31.099> opinion<00:48:31.460> vector<00:48:31.759> of<00:48:31.880> this<00:48:31.999> peer<00:48:34.059> and<00:48:35.059> if 00:48:35.380 --> 00:48:35.390 align:start position:0% the opinion vector of this peer and if 00:48:35.390 --> 00:48:37.329 align:start position:0% the opinion vector of this peer and if we<00:48:35.480> want<00:48:35.660> to<00:48:35.720> put<00:48:35.900> it<00:48:36.019> in<00:48:36.170> if<00:48:36.859> we<00:48:37.009> want<00:48:37.099> to<00:48:37.190> put 00:48:37.329 --> 00:48:37.339 align:start position:0% we want to put it in if we want to put 00:48:37.339 --> 00:48:39.039 align:start position:0% we want to put it in if we want to put in<00:48:37.430> a<00:48:37.490> matrix<00:48:37.640> form<00:48:37.880> we<00:48:38.180> say<00:48:38.359> okay<00:48:38.599> well<00:48:38.779> let's 00:48:39.039 --> 00:48:39.049 align:start position:0% in a matrix form we say okay well let's 00:48:39.049 --> 00:48:42.309 align:start position:0% in a matrix form we say okay well let's ask<00:48:39.259> our<00:48:40.069> friends<00:48:40.400> J<00:48:40.869> what<00:48:41.869> they<00:48:42.019> think<00:48:42.230> of 00:48:42.309 --> 00:48:42.319 align:start position:0% ask our friends J what they think of 00:48:42.319 --> 00:48:45.099 align:start position:0% ask our friends J what they think of peer<00:48:42.619> k<00:48:42.859> and<00:48:43.460> wait<00:48:44.269> what<00:48:44.480> they<00:48:44.569> think<00:48:44.779> of<00:48:44.869> your 00:48:45.099 --> 00:48:45.109 align:start position:0% peer k and wait what they think of your 00:48:45.109 --> 00:48:52.269 align:start position:0% peer k and wait what they think of your k<00:48:45.609> by<00:48:46.609> how<00:48:46.759> much<00:48:46.910> you<00:48:47.059> trust<00:48:50.529> in<00:48:51.529> matrix<00:48:51.859> forms 00:48:52.269 --> 00:48:52.279 align:start position:0% k by how much you trust in matrix forms 00:48:52.279 --> 00:48:53.739 align:start position:0% k by how much you trust in matrix forms and<00:48:52.490> look<00:48:52.670> something<00:48:52.999> like<00:48:53.029> this<00:48:53.299> so<00:48:53.480> this<00:48:53.509> is 00:48:53.739 --> 00:48:53.749 align:start position:0% and look something like this so this is 00:48:53.749 --> 00:48:55.930 align:start position:0% and look something like this so this is I<00:48:53.900> called<00:48:54.140> the<00:48:54.230> ask<00:48:54.440> a<00:48:54.619> friend<00:48:54.740> operator<00:48:55.309> that 00:48:55.930 --> 00:48:55.940 align:start position:0% I called the ask a friend operator that 00:48:55.940 --> 00:48:58.180 align:start position:0% I called the ask a friend operator that you<00:48:56.059> have<00:48:56.299> a<00:48:56.329> matrix<00:48:56.930> C<00:48:57.410> transpose<00:48:57.920> C 00:48:58.180 --> 00:48:58.190 align:start position:0% you have a matrix C transpose C 00:48:58.190 --> 00:49:00.910 align:start position:0% you have a matrix C transpose C transpose<00:48:58.819> which<00:48:59.509> is<00:48:59.720> the<00:49:00.019> list<00:49:00.259> of<00:49:00.380> opinions 00:49:00.910 --> 00:49:00.920 align:start position:0% transpose which is the list of opinions 00:49:00.920 --> 00:49:03.099 align:start position:0% transpose which is the list of opinions of<00:49:01.069> everybody<00:49:01.549> it's<00:49:01.789> the<00:49:01.940> network<00:49:02.150> graphic<00:49:02.779> of 00:49:03.099 --> 00:49:03.109 align:start position:0% of everybody it's the network graphic of 00:49:03.109 --> 00:49:04.809 align:start position:0% of everybody it's the network graphic of all<00:49:03.440> of<00:49:03.619> the<00:49:03.710> opinions<00:49:03.920> of<00:49:04.190> everybody<00:49:04.609> on<00:49:04.730> the 00:49:04.809 --> 00:49:04.819 align:start position:0% all of the opinions of everybody on the 00:49:04.819 --> 00:49:07.870 align:start position:0% all of the opinions of everybody on the network<00:49:05.089> and<00:49:05.599> then<00:49:05.869> you<00:49:06.079> just<00:49:06.349> multiply<00:49:06.559> it<00:49:06.920> by 00:49:07.870 --> 00:49:07.880 align:start position:0% network and then you just multiply it by 00:49:07.880 --> 00:49:10.299 align:start position:0% network and then you just multiply it by your<00:49:08.089> own<00:49:08.299> opinion<00:49:08.779> and<00:49:09.019> you<00:49:09.710> basically<00:49:10.069> take 00:49:10.299 --> 00:49:10.309 align:start position:0% your own opinion and you basically take 00:49:10.309 --> 00:49:13.600 align:start position:0% your own opinion and you basically take one<00:49:10.640> hop<00:49:10.880> out 00:49:13.600 --> 00:49:13.610 align:start position:0% 00:49:13.610 --> 00:49:16.240 align:start position:0% the<00:49:14.060> problem<00:49:14.420> with<00:49:14.570> this<00:49:14.720> is<00:49:15.650> twofold<00:49:16.100> you 00:49:16.240 --> 00:49:16.250 align:start position:0% the problem with this is twofold you 00:49:16.250 --> 00:49:18.160 align:start position:0% the problem with this is twofold you either<00:49:16.460> have<00:49:16.670> a<00:49:16.700> lot<00:49:16.940> of<00:49:16.970> friends<00:49:17.390> who<00:49:17.990> have<00:49:18.140> a 00:49:18.160 --> 00:49:18.170 align:start position:0% either have a lot of friends who have a 00:49:18.170 --> 00:49:20.080 align:start position:0% either have a lot of friends who have a lot<00:49:18.380> of<00:49:18.470> friends<00:49:18.830> and<00:49:19.340> then<00:49:19.580> you<00:49:19.610> get<00:49:19.820> good 00:49:20.080 --> 00:49:20.090 align:start position:0% lot of friends and then you get good 00:49:20.090 --> 00:49:22.180 align:start position:0% lot of friends and then you get good coverage<00:49:20.300> but<00:49:21.170> you<00:49:21.290> have<00:49:21.470> to<00:49:21.590> do<00:49:21.710> a<00:49:21.740> fair 00:49:22.180 --> 00:49:22.190 align:start position:0% coverage but you have to do a fair 00:49:22.190 --> 00:49:26.770 align:start position:0% coverage but you have to do a fair amount<00:49:22.310> of<00:49:22.760> computation<00:49:23.750> and<00:49:23.870> storage<00:49:24.880> or<00:49:25.880> you 00:49:26.770 --> 00:49:26.780 align:start position:0% amount of computation and storage or you 00:49:26.780 --> 00:49:28.570 align:start position:0% amount of computation and storage or you don't<00:49:26.960> have<00:49:27.080> a<00:49:27.110> lot<00:49:27.320> of<00:49:27.350> friends<00:49:27.740> we<00:49:28.400> don't 00:49:28.570 --> 00:49:28.580 align:start position:0% don't have a lot of friends we don't 00:49:28.580 --> 00:49:30.880 align:start position:0% don't have a lot of friends we don't have<00:49:28.730> a<00:49:28.760> lot<00:49:28.940> of<00:49:28.970> friends<00:49:29.330> and<00:49:29.600> then<00:49:30.380> you<00:49:30.620> don't 00:49:30.880 --> 00:49:30.890 align:start position:0% have a lot of friends and then you don't 00:49:30.890 --> 00:49:32.500 align:start position:0% have a lot of friends and then you don't have<00:49:31.010> to<00:49:31.100> do<00:49:31.190> a<00:49:31.220> lot<00:49:31.400> of<00:49:31.430> trust<00:49:31.730> you<00:49:32.210> don't<00:49:32.300> have 00:49:32.500 --> 00:49:32.510 align:start position:0% have to do a lot of trust you don't have 00:49:32.510 --> 00:49:33.600 align:start position:0% have to do a lot of trust you don't have to<00:49:32.600> do<00:49:32.690> a<00:49:32.720> lot<00:49:32.840> of<00:49:32.930> computation<00:49:33.170> and<00:49:33.500> storage 00:49:33.600 --> 00:49:33.610 align:start position:0% to do a lot of computation and storage 00:49:33.610 --> 00:49:36.550 align:start position:0% to do a lot of computation and storage but<00:49:34.610> you<00:49:34.820> do<00:49:35.090> end<00:49:35.390> up<00:49:35.510> having<00:49:35.570> the<00:49:36.530> same 00:49:36.550 --> 00:49:36.560 align:start position:0% but you do end up having the same 00:49:36.560 --> 00:49:37.840 align:start position:0% but you do end up having the same problem<00:49:37.040> that<00:49:37.130> you<00:49:37.220> had<00:49:37.340> in<00:49:37.430> the<00:49:37.460> first<00:49:37.520> place 00:49:37.840 --> 00:49:37.850 align:start position:0% problem that you had in the first place 00:49:37.850 --> 00:49:39.910 align:start position:0% problem that you had in the first place like<00:49:38.000> you<00:49:38.120> don't<00:49:38.270> have<00:49:38.360> enough<00:49:38.570> memory<00:49:38.920> so 00:49:39.910 --> 00:49:39.920 align:start position:0% like you don't have enough memory so 00:49:39.920 --> 00:49:42.580 align:start position:0% like you don't have enough memory so what<00:49:40.100> we<00:49:40.190> really<00:49:40.580> want<00:49:40.790> is<00:49:41.060> we<00:49:41.390> want<00:49:41.420> lots<00:49:42.410> of 00:49:42.580 --> 00:49:42.590 align:start position:0% what we really want is we want lots of 00:49:42.590 --> 00:49:48.160 align:start position:0% what we really want is we want lots of coverage<00:49:42.920> and<00:49:43.310> low<00:49:43.790> complication<00:49:46.150> so<00:49:47.150> one<00:49:47.960> way 00:49:48.160 --> 00:49:48.170 align:start position:0% coverage and low complication so one way 00:49:48.170 --> 00:49:51.220 align:start position:0% coverage and low complication so one way to<00:49:48.530> get<00:49:49.280> lots<00:49:49.580> of<00:49:49.760> coverage<00:49:50.150> is<00:49:50.630> just<00:49:50.690> to<00:49:50.990> keep 00:49:51.220 --> 00:49:51.230 align:start position:0% to get lots of coverage is just to keep 00:49:51.230 --> 00:49:53.050 align:start position:0% to get lots of coverage is just to keep asking<00:49:51.440> friends<00:49:51.890> so<00:49:52.130> you<00:49:52.220> start<00:49:52.550> to<00:49:52.580> ask<00:49:52.880> your 00:49:53.050 --> 00:49:53.060 align:start position:0% asking friends so you start to ask your 00:49:53.060 --> 00:49:57.810 align:start position:0% asking friends so you start to ask your friends<00:49:55.180> and<00:49:56.180> then<00:49:56.360> you<00:49:56.570> ask<00:49:56.780> their<00:49:57.050> friends 00:49:57.810 --> 00:49:57.820 align:start position:0% friends and then you ask their friends 00:49:57.820 --> 00:50:00.100 align:start position:0% friends and then you ask their friends and<00:49:58.820> so<00:49:59.000> you<00:49:59.060> just<00:49:59.270> apply<00:49:59.390> the<00:49:59.570> ask<00:49:59.810> to<00:50:00.020> the 00:50:00.100 --> 00:50:00.110 align:start position:0% and so you just apply the ask to the 00:50:00.110 --> 00:50:03.820 align:start position:0% and so you just apply the ask to the friend<00:50:00.320> operator<00:50:00.680> again<00:50:02.320> and<00:50:03.320> then<00:50:03.500> you<00:50:03.620> keep 00:50:03.820 --> 00:50:03.830 align:start position:0% friend operator again and then you keep 00:50:03.830 --> 00:50:05.500 align:start position:0% friend operator again and then you keep asking<00:50:04.250> until<00:50:04.340> the<00:50:04.610> cows<00:50:04.790> come<00:50:04.820> on<00:50:05.240> them<00:50:05.330> so 00:50:05.500 --> 00:50:05.510 align:start position:0% asking until the cows come on them so 00:50:05.510 --> 00:50:08.830 align:start position:0% asking until the cows come on them so you<00:50:06.200> have<00:50:06.230> the<00:50:06.470> trust<00:50:06.650> vector<00:50:07.100> is<00:50:07.370> equal<00:50:07.730> to<00:50:08.120> C 00:50:08.830 --> 00:50:08.840 align:start position:0% you have the trust vector is equal to C 00:50:08.840 --> 00:50:12.580 align:start position:0% you have the trust vector is equal to C T<00:50:09.080> to<00:50:09.260> the<00:50:09.380> N<00:50:09.590> kind<00:50:10.370> of<00:50:10.490> CI<00:50:11.320> and<00:50:12.320> there's<00:50:12.530> a 00:50:12.580 --> 00:50:12.590 align:start position:0% T to the N kind of CI and there's a 00:50:12.590 --> 00:50:14.830 align:start position:0% T to the N kind of CI and there's a great<00:50:12.920> benefit<00:50:13.910> to<00:50:14.030> this<00:50:14.150> and<00:50:14.330> it's<00:50:14.450> not<00:50:14.600> just 00:50:14.830 --> 00:50:14.840 align:start position:0% great benefit to this and it's not just 00:50:14.840 --> 00:50:18.070 align:start position:0% great benefit to this and it's not just the<00:50:14.930> cows<00:50:15.170> is<00:50:15.590> that<00:50:16.220> this<00:50:17.090> trust<00:50:17.420> vector<00:50:17.810> when 00:50:18.070 --> 00:50:18.080 align:start position:0% the cows is that this trust vector when 00:50:18.080 --> 00:50:19.810 align:start position:0% the cows is that this trust vector when you<00:50:18.170> compute<00:50:18.530> it<00:50:18.590> in<00:50:18.710> this<00:50:18.860> way<00:50:19.070> actually 00:50:19.810 --> 00:50:19.820 align:start position:0% you compute it in this way actually 00:50:19.820 --> 00:50:23.740 align:start position:0% you compute it in this way actually converges<00:50:20.690> to<00:50:20.990> the<00:50:21.650> same<00:50:21.950> thing<00:50:22.550> for<00:50:23.330> every 00:50:23.740 --> 00:50:23.750 align:start position:0% converges to the same thing for every 00:50:23.750 --> 00:50:25.930 align:start position:0% converges to the same thing for every peer<00:50:23.960> on<00:50:24.200> the<00:50:24.320> network<00:50:24.650> so<00:50:25.340> what<00:50:25.520> we've<00:50:25.700> done 00:50:25.930 --> 00:50:25.940 align:start position:0% peer on the network so what we've done 00:50:25.940 --> 00:50:30.010 align:start position:0% peer on the network so what we've done by<00:50:26.180> asking<00:50:26.420> friends<00:50:26.990> ad<00:50:27.620> infinitum<00:50:28.520> is<00:50:29.240> that 00:50:30.010 --> 00:50:30.020 align:start position:0% by asking friends ad infinitum is that 00:50:30.020 --> 00:50:31.840 align:start position:0% by asking friends ad infinitum is that we've<00:50:30.170> actually<00:50:30.380> computed<00:50:31.040> a<00:50:31.100> global<00:50:31.580> trust 00:50:31.840 --> 00:50:31.850 align:start position:0% we've actually computed a global trust 00:50:31.850 --> 00:50:34.390 align:start position:0% we've actually computed a global trust vector<00:50:32.240> for<00:50:32.480> the<00:50:32.600> entire<00:50:32.900> network<00:50:33.170> and<00:50:33.680> so 00:50:34.390 --> 00:50:34.400 align:start position:0% vector for the entire network and so 00:50:34.400 --> 00:50:37.060 align:start position:0% vector for the entire network and so therefore<00:50:34.640> you<00:50:35.480> each<00:50:35.900> peer<00:50:36.290> can<00:50:36.530> collaborate 00:50:37.060 --> 00:50:37.070 align:start position:0% therefore you each peer can collaborate 00:50:37.070 --> 00:50:39.730 align:start position:0% therefore you each peer can collaborate in<00:50:37.310> the<00:50:37.640> storage<00:50:38.090> and<00:50:38.240> computation<00:50:38.540> of<00:50:39.080> a 00:50:39.730 --> 00:50:39.740 align:start position:0% in the storage and computation of a 00:50:39.740 --> 00:50:42.490 align:start position:0% in the storage and computation of a single<00:50:40.220> trust<00:50:40.520> value<00:50:40.790> for<00:50:41.300> each<00:50:41.450> person<00:50:41.990> so<00:50:42.470> a 00:50:42.490 --> 00:50:42.500 align:start position:0% single trust value for each person so a 00:50:42.500 --> 00:50:45.060 align:start position:0% single trust value for each person so a single<00:50:42.770> stress<00:50:43.130> vector<00:50:43.490> for<00:50:43.730> them 00:50:45.060 --> 00:50:45.070 align:start position:0% single stress vector for them 00:50:45.070 --> 00:50:46.590 align:start position:0% single stress vector for them [Music] 00:50:46.590 --> 00:50:46.600 align:start position:0% [Music] 00:50:46.600 --> 00:50:49.590 align:start position:0% [Music] and<00:50:46.960> the<00:50:47.920> way<00:50:48.040> that<00:50:48.220> the<00:50:48.850> way<00:50:48.970> that<00:50:49.150> works<00:50:49.420> like 00:50:49.590 --> 00:50:49.600 align:start position:0% and the way that the way that works like 00:50:49.600 --> 00:50:52.530 align:start position:0% and the way that the way that works like the<00:50:50.020> way<00:50:50.140> that<00:50:50.490> we<00:50:51.490> initialize<00:50:52.150> a<00:50:52.180> trust 00:50:52.530 --> 00:50:52.540 align:start position:0% the way that we initialize a trust 00:50:52.540 --> 00:50:58.080 align:start position:0% the way that we initialize a trust vector<00:50:52.900> to<00:50:53.620> any<00:50:54.930> any<00:50:56.010> any<00:50:57.010> vector<00:50:57.430> let's<00:50:57.850> just 00:50:58.080 --> 00:50:58.090 align:start position:0% vector to any any any vector let's just 00:50:58.090 --> 00:51:01.110 align:start position:0% vector to any any any vector let's just start<00:50:58.510> with<00:50:58.660> the<00:50:58.780> uniform<00:50:59.200> mentor<00:50:59.910> and<00:51:00.910> then 00:51:01.110 --> 00:51:01.120 align:start position:0% start with the uniform mentor and then 00:51:01.120 --> 00:51:03.510 align:start position:0% start with the uniform mentor and then we<00:51:01.270> just<00:51:01.450> keep<00:51:01.660> repeating<00:51:02.070> applying<00:51:03.070> the<00:51:03.310> ask 00:51:03.510 --> 00:51:03.520 align:start position:0% we just keep repeating applying the ask 00:51:03.520 --> 00:51:07.380 align:start position:0% we just keep repeating applying the ask a<00:51:03.760> friend<00:51:03.940> operator<00:51:04.870> to<00:51:05.590> this<00:51:06.160> iteration<00:51:06.670> and 00:51:07.380 --> 00:51:07.390 align:start position:0% a friend operator to this iteration and 00:51:07.390 --> 00:51:08.790 align:start position:0% a friend operator to this iteration and you<00:51:07.540> keep<00:51:07.720> asking<00:51:07.930> and<00:51:08.260> eventually<00:51:08.680> I'll 00:51:08.790 --> 00:51:08.800 align:start position:0% you keep asking and eventually I'll 00:51:08.800 --> 00:51:11.460 align:start position:0% you keep asking and eventually I'll converge<00:51:09.250> and<00:51:09.730> look<00:51:10.330> what<00:51:10.750> it<00:51:10.900> will<00:51:11.050> converge 00:51:11.460 --> 00:51:11.470 align:start position:0% converge and look what it will converge 00:51:11.470 --> 00:51:14.640 align:start position:0% converge and look what it will converge to<00:51:11.500> is<00:51:12.310> the<00:51:12.820> principal<00:51:13.330> eigenvector<00:51:13.480> of<00:51:14.140> that 00:51:14.640 --> 00:51:14.650 align:start position:0% to is the principal eigenvector of that 00:51:14.650 --> 00:51:16.530 align:start position:0% to is the principal eigenvector of that trust<00:51:15.040> matrix<00:51:15.640> the<00:51:15.910> in<00:51:16.090> principal 00:51:16.530 --> 00:51:16.540 align:start position:0% trust matrix the in principal 00:51:16.540 --> 00:51:18.840 align:start position:0% trust matrix the in principal eigenvector<00:51:16.690> of<00:51:17.320> the<00:51:17.470> matrix<00:51:17.920> that<00:51:18.370> represent 00:51:18.840 --> 00:51:18.850 align:start position:0% eigenvector of the matrix that represent 00:51:18.850 --> 00:51:22.350 align:start position:0% eigenvector of the matrix that represent the<00:51:18.970> opinions<00:51:19.060> of<00:51:19.480> everybody<00:51:20.820> everybody<00:51:21.820> in 00:51:22.350 --> 00:51:22.360 align:start position:0% the opinions of everybody everybody in 00:51:22.360 --> 00:51:27.870 align:start position:0% the opinions of everybody everybody in the<00:51:22.540> network<00:51:24.390> so<00:51:25.390> this<00:51:25.570> is<00:51:25.780> nice<00:51:26.170> and<00:51:26.730> if<00:51:27.730> we 00:51:27.870 --> 00:51:27.880 align:start position:0% the network so this is nice and if we 00:51:27.880 --> 00:51:29.340 align:start position:0% the network so this is nice and if we have<00:51:28.060> a<00:51:28.090> centralized<00:51:28.600> system<00:51:28.750> or<00:51:29.020> even<00:51:29.050> if<00:51:29.320> we 00:51:29.340 --> 00:51:29.350 align:start position:0% have a centralized system or even if we 00:51:29.350 --> 00:51:30.900 align:start position:0% have a centralized system or even if we had<00:51:29.530> a<00:51:29.560> block<00:51:29.770> chain<00:51:30.070> this<00:51:30.580> would<00:51:30.820> be 00:51:30.900 --> 00:51:30.910 align:start position:0% had a block chain this would be 00:51:30.910 --> 00:51:34.590 align:start position:0% had a block chain this would be sufficient<00:51:31.450> we<00:51:32.410> could<00:51:32.650> just<00:51:32.980> take<00:51:33.790> the<00:51:34.090> we 00:51:34.590 --> 00:51:34.600 align:start position:0% sufficient we could just take the we 00:51:34.600 --> 00:51:36.030 align:start position:0% sufficient we could just take the we could<00:51:34.780> just<00:51:34.930> take<00:51:35.140> the<00:51:35.290> opinions<00:51:35.680> and<00:51:35.860> have<00:51:35.980> a 00:51:36.030 --> 00:51:36.040 align:start position:0% could just take the opinions and have a 00:51:36.040 --> 00:51:38.910 align:start position:0% could just take the opinions and have a centralized<00:51:37.200> computer<00:51:38.200> or<00:51:38.440> lots<00:51:38.740> of 00:51:38.910 --> 00:51:38.920 align:start position:0% centralized computer or lots of 00:51:38.920 --> 00:51:41.700 align:start position:0% centralized computer or lots of computers<00:51:39.550> operating<00:51:40.090> in<00:51:40.210> consensus<00:51:40.810> compute 00:51:41.700 --> 00:51:41.710 align:start position:0% computers operating in consensus compute 00:51:41.710 --> 00:51:44.790 align:start position:0% computers operating in consensus compute this<00:51:41.890> computation<00:51:43.080> but<00:51:44.080> we<00:51:44.260> can<00:51:44.410> take<00:51:44.620> it<00:51:44.770> one 00:51:44.790 --> 00:51:44.800 align:start position:0% this computation but we can take it one 00:51:44.800 --> 00:51:45.630 align:start position:0% this computation but we can take it one step<00:51:45.130> further 00:51:45.630 --> 00:51:45.640 align:start position:0% step further 00:51:45.640 --> 00:51:48.240 align:start position:0% step further because<00:51:46.420> in<00:51:46.990> a<00:51:47.110> true<00:51:47.380> peer-to-peer<00:51:47.680> network 00:51:48.240 --> 00:51:48.250 align:start position:0% because in a true peer-to-peer network 00:51:48.250 --> 00:51:51.000 align:start position:0% because in a true peer-to-peer network you<00:51:48.400> won't<00:51:48.610> have<00:51:48.790> any<00:51:49.240> single<00:51:49.990> machine<00:51:50.470> and 00:51:51.000 --> 00:51:51.010 align:start position:0% you won't have any single machine and 00:51:51.010 --> 00:51:53.660 align:start position:0% you won't have any single machine and you<00:51:51.070> single<00:51:51.400> node<00:51:51.580> storing<00:51:52.450> the<00:51:52.630> whole<00:51:52.870> matrix 00:51:53.660 --> 00:51:53.670 align:start position:0% you single node storing the whole matrix 00:51:53.670 --> 00:51:57.120 align:start position:0% you single node storing the whole matrix or<00:51:54.780> even<00:51:55.780> is<00:51:55.990> storing<00:51:56.320> the<00:51:56.470> whole<00:51:56.620> matrix<00:51:56.740> or 00:51:57.120 --> 00:51:57.130 align:start position:0% or even is storing the whole matrix or 00:51:57.130 --> 00:51:59.100 align:start position:0% or even is storing the whole matrix or being<00:51:57.370> able<00:51:57.490> to<00:51:57.640> compute<00:51:58.090> the<00:51:58.360> whole<00:51:58.600> and 00:51:59.100 --> 00:51:59.110 align:start position:0% being able to compute the whole and 00:51:59.110 --> 00:52:00.990 align:start position:0% being able to compute the whole and supplying 00:52:00.990 --> 00:52:01.000 align:start position:0% supplying 00:52:01.000 --> 00:52:03.180 align:start position:0% supplying in<00:52:01.300> fact<00:52:01.570> what<00:52:01.810> you<00:52:01.930> have<00:52:02.200> is<00:52:02.530> you<00:52:03.160> have 00:52:03.180 --> 00:52:03.190 align:start position:0% in fact what you have is you have 00:52:03.190 --> 00:52:08.359 align:start position:0% in fact what you have is you have basically<00:52:03.880> each<00:52:04.330> node<00:52:05.400> storing<00:52:06.400> is<00:52:06.609> own<00:52:07.000> row 00:52:08.359 --> 00:52:08.369 align:start position:0% basically each node storing is own row 00:52:08.369 --> 00:52:12.420 align:start position:0% basically each node storing is own row its<00:52:09.369> own<00:52:09.730> basically<00:52:10.540> his<00:52:10.690> own<00:52:11.220> opinions<00:52:12.220> of 00:52:12.420 --> 00:52:12.430 align:start position:0% its own basically his own opinions of 00:52:12.430 --> 00:52:16.230 align:start position:0% its own basically his own opinions of other<00:52:12.730> people<00:52:13.260> and<00:52:14.260> so<00:52:14.440> how<00:52:14.800> do<00:52:14.859> we<00:52:15.040> compute<00:52:15.460> a 00:52:16.230 --> 00:52:16.240 align:start position:0% other people and so how do we compute a 00:52:16.240 --> 00:52:18.150 align:start position:0% other people and so how do we compute a principal<00:52:17.080> eigenvector<00:52:17.230> when<00:52:17.890> you<00:52:17.980> don't 00:52:18.150 --> 00:52:18.160 align:start position:0% principal eigenvector when you don't 00:52:18.160 --> 00:52:20.130 align:start position:0% principal eigenvector when you don't have<00:52:18.430> any<00:52:18.550> machine<00:52:18.940> that<00:52:19.390> knows<00:52:19.780> the<00:52:19.960> whole 00:52:20.130 --> 00:52:20.140 align:start position:0% have any machine that knows the whole 00:52:20.140 --> 00:52:22.920 align:start position:0% have any machine that knows the whole dangerous<00:52:20.910> well<00:52:21.910> one<00:52:22.090> way<00:52:22.240> we<00:52:22.390> can<00:52:22.510> do<00:52:22.630> this<00:52:22.810> is 00:52:22.920 --> 00:52:22.930 align:start position:0% dangerous well one way we can do this is 00:52:22.930 --> 00:52:26.060 align:start position:0% dangerous well one way we can do this is we<00:52:23.050> can<00:52:23.230> recognize<00:52:23.740> that<00:52:24.310> we<00:52:24.790> can<00:52:24.970> take<00:52:25.210> this 00:52:26.060 --> 00:52:26.070 align:start position:0% we can recognize that we can take this 00:52:26.070 --> 00:52:30.990 align:start position:0% we can recognize that we can take this matrix<00:52:27.070> computation<00:52:27.430> and<00:52:28.500> actually<00:52:29.820> break<00:52:30.820> it 00:52:30.990 --> 00:52:31.000 align:start position:0% matrix computation and actually break it 00:52:31.000 --> 00:52:33.720 align:start position:0% matrix computation and actually break it down<00:52:31.150> into<00:52:31.540> a<00:52:31.750> single<00:52:32.440> element<00:52:32.859> conversation 00:52:33.720 --> 00:52:33.730 align:start position:0% down into a single element conversation 00:52:33.730 --> 00:52:38.010 align:start position:0% down into a single element conversation by<00:52:34.420> saying<00:52:34.810> that<00:52:36.030> this<00:52:37.030> element<00:52:37.420> the<00:52:37.750> ti 00:52:38.010 --> 00:52:38.020 align:start position:0% by saying that this element the ti 00:52:38.020 --> 00:52:42.060 align:start position:0% by saying that this element the ti element<00:52:38.770> is<00:52:39.060> actually<00:52:40.060> equal<00:52:40.390> to<00:52:40.710> this<00:52:41.710> row 00:52:42.060 --> 00:52:42.070 align:start position:0% element is actually equal to this row 00:52:42.070 --> 00:52:47.099 align:start position:0% element is actually equal to this row times<00:52:42.490> this<00:52:42.760> column<00:52:43.440> and<00:52:44.940> to<00:52:45.940> be<00:52:46.570> a<00:52:46.599> little<00:52:46.990> bit 00:52:47.099 --> 00:52:47.109 align:start position:0% times this column and to be a little bit 00:52:47.109 --> 00:52:49.620 align:start position:0% times this column and to be a little bit less<00:52:47.290> abstract<00:52:47.590> about<00:52:48.130> it<00:52:48.369> what<00:52:49.060> it<00:52:49.180> means<00:52:49.359> is 00:52:49.620 --> 00:52:49.630 align:start position:0% less abstract about it what it means is 00:52:49.630 --> 00:52:53.130 align:start position:0% less abstract about it what it means is that<00:52:49.950> the<00:52:50.950> trust<00:52:51.310> my<00:52:51.880> own<00:52:51.910> trust<00:52:52.540> score<00:52:52.869> at<00:52:53.020> any 00:52:53.130 --> 00:52:53.140 align:start position:0% that the trust my own trust score at any 00:52:53.140 --> 00:52:58.320 align:start position:0% that the trust my own trust score at any given<00:52:53.530> time<00:52:53.830> is<00:52:55.080> the<00:52:56.080> the<00:52:57.119> opinions<00:52:58.119> that 00:52:58.320 --> 00:52:58.330 align:start position:0% given time is the the opinions that 00:52:58.330 --> 00:53:01.650 align:start position:0% given time is the the opinions that people<00:52:58.690> have<00:52:58.900> of<00:52:59.170> me<00:52:59.550> weighted<00:53:00.550> by<00:53:00.790> their 00:53:01.650 --> 00:53:01.660 align:start position:0% people have of me weighted by their 00:53:01.660 --> 00:53:03.780 align:start position:0% people have of me weighted by their trust<00:53:02.170> scores<00:53:02.530> the<00:53:02.800> trust<00:53:03.010> scores<00:53:03.220> of<00:53:03.400> people 00:53:03.780 --> 00:53:03.790 align:start position:0% trust scores the trust scores of people 00:53:03.790 --> 00:53:05.180 align:start position:0% trust scores the trust scores of people who<00:53:03.910> have 00:53:05.180 --> 00:53:05.190 align:start position:0% who have 00:53:05.190 --> 00:53:07.519 align:start position:0% who have and<00:53:05.700> so<00:53:05.880> in<00:53:06.059> that<00:53:06.240> case<00:53:06.450> everybody<00:53:07.200> can 00:53:07.519 --> 00:53:07.529 align:start position:0% and so in that case everybody can 00:53:07.529 --> 00:53:10.789 align:start position:0% and so in that case everybody can compute<00:53:08.039> their<00:53:09.029> own<00:53:09.210> truss<00:53:09.539> core<00:53:09.809> at<00:53:10.289> any<00:53:10.529> time 00:53:10.789 --> 00:53:10.799 align:start position:0% compute their own truss core at any time 00:53:10.799 --> 00:53:15.079 align:start position:0% compute their own truss core at any time was<00:53:11.400> they<00:53:11.549> just<00:53:11.789> know<00:53:11.940> those<00:53:12.150> two<00:53:12.359> things<00:53:14.089> so 00:53:15.079 --> 00:53:15.089 align:start position:0% was they just know those two things so 00:53:15.089 --> 00:53:18.109 align:start position:0% was they just know those two things so you<00:53:15.509> end<00:53:15.690> up<00:53:15.779> having<00:53:15.839> a<00:53:17.119> pretty 00:53:18.109 --> 00:53:18.119 align:start position:0% you end up having a pretty 00:53:18.119 --> 00:53:23.960 align:start position:0% you end up having a pretty straightforward<00:53:20.720> protocol<00:53:21.720> were<00:53:21.869> you<00:53:22.970> for 00:53:23.960 --> 00:53:23.970 align:start position:0% straightforward protocol were you for 00:53:23.970 --> 00:53:26.420 align:start position:0% straightforward protocol were you for each<00:53:24.269> year<00:53:24.839> you<00:53:25.109> compute<00:53:25.680> your<00:53:25.920> friend<00:53:26.190> trust 00:53:26.420 --> 00:53:26.430 align:start position:0% each year you compute your friend trust 00:53:26.430 --> 00:53:29.900 align:start position:0% each year you compute your friend trust value<00:53:26.789> by<00:53:27.509> taking<00:53:27.950> the<00:53:28.950> present<00:53:29.490> trust<00:53:29.730> about 00:53:29.900 --> 00:53:29.910 align:start position:0% value by taking the present trust about 00:53:29.910 --> 00:53:32.329 align:start position:0% value by taking the present trust about the<00:53:29.970> present<00:53:30.599> people<00:53:31.410> who<00:53:31.500> have<00:53:31.680> opinions<00:53:32.190> of 00:53:32.329 --> 00:53:32.339 align:start position:0% the present people who have opinions of 00:53:32.339 --> 00:53:35.299 align:start position:0% the present people who have opinions of you<00:53:32.490> their<00:53:33.059> opinions<00:53:33.509> of<00:53:33.630> you<00:53:33.829> times<00:53:34.829> their 00:53:35.299 --> 00:53:35.309 align:start position:0% you their opinions of you times their 00:53:35.309 --> 00:53:37.940 align:start position:0% you their opinions of you times their current<00:53:35.339> trust<00:53:35.940> values<00:53:36.559> then<00:53:37.559> once<00:53:37.829> you 00:53:37.940 --> 00:53:37.950 align:start position:0% current trust values then once you 00:53:37.950 --> 00:53:40.039 align:start position:0% current trust values then once you compute<00:53:38.430> your<00:53:38.460> current<00:53:38.789> trust<00:53:39.029> scores<00:53:39.269> you 00:53:40.039 --> 00:53:40.049 align:start position:0% compute your current trust scores you 00:53:40.049 --> 00:53:43.970 align:start position:0% compute your current trust scores you send<00:53:40.440> your<00:53:41.160> trust<00:53:41.460> fund<00:53:41.700> and<00:53:42.509> the<00:53:43.440> opinions 00:53:43.970 --> 00:53:43.980 align:start position:0% send your trust fund and the opinions 00:53:43.980 --> 00:53:46.460 align:start position:0% send your trust fund and the opinions that<00:53:44.400> you<00:53:44.519> have<00:53:44.730> of<00:53:45.119> other<00:53:45.329> people<00:53:45.750> to<00:53:46.289> them 00:53:46.460 --> 00:53:46.470 align:start position:0% that you have of other people to them 00:53:46.470 --> 00:53:49.039 align:start position:0% that you have of other people to them and<00:53:46.769> then<00:53:47.579> they<00:53:47.849> aggregate<00:53:48.539> those<00:53:48.779> that 00:53:49.039 --> 00:53:49.049 align:start position:0% and then they aggregate those that 00:53:49.049 --> 00:53:51.620 align:start position:0% and then they aggregate those that compute<00:53:49.470> their<00:53:49.650> trust<00:53:49.950> score<00:53:50.190> and<00:53:50.880> then<00:53:51.509> you 00:53:51.620 --> 00:53:51.630 align:start position:0% compute their trust score and then you 00:53:51.630 --> 00:53:54.079 align:start position:0% compute their trust score and then you wait<00:53:51.839> until<00:53:52.289> it<00:53:52.859> goes<00:53:53.069> around<00:53:53.339> and<00:53:53.700> they<00:53:53.849> send 00:53:54.079 --> 00:53:54.089 align:start position:0% wait until it goes around and they send 00:53:54.089 --> 00:53:56.150 align:start position:0% wait until it goes around and they send it<00:53:54.210> back<00:53:54.359> to<00:53:54.509> you<00:53:54.599> and<00:53:54.869> that<00:53:55.319> iteration<00:53:55.740> keeps 00:53:56.150 --> 00:53:56.160 align:start position:0% it back to you and that iteration keeps 00:53:56.160 --> 00:53:57.769 align:start position:0% it back to you and that iteration keeps happening<00:53:56.369> over<00:53:56.789> the<00:53:57.059> course<00:53:57.089> of<00:53:57.359> the<00:53:57.480> network 00:53:57.769 --> 00:53:57.779 align:start position:0% happening over the course of the network 00:53:57.779 --> 00:54:00.650 align:start position:0% happening over the course of the network and<00:53:58.200> that<00:53:58.289> way<00:53:58.710> lots<00:53:59.460> of<00:53:59.640> peers<00:54:00.000> all<00:54:00.269> over<00:54:00.539> the 00:54:00.650 --> 00:54:00.660 align:start position:0% and that way lots of peers all over the 00:54:00.660 --> 00:54:03.019 align:start position:0% and that way lots of peers all over the network<00:54:00.839> end<00:54:01.259> up<00:54:01.410> collaboratively<00:54:02.400> computing 00:54:03.019 --> 00:54:03.029 align:start position:0% network end up collaboratively computing 00:54:03.029 --> 00:54:05.210 align:start position:0% network end up collaboratively computing the<00:54:03.599> principal<00:54:04.019> eigenvector<00:54:04.170> of<00:54:04.650> a<00:54:04.890> matrix 00:54:05.210 --> 00:54:05.220 align:start position:0% the principal eigenvector of a matrix 00:54:05.220 --> 00:54:08.349 align:start position:0% the principal eigenvector of a matrix that<00:54:05.309> none<00:54:05.640> of<00:54:05.759> them<00:54:05.910> knows<00:54:06.180> the<00:54:06.480> whole<00:54:06.660> matrix 00:54:08.349 --> 00:54:08.359 align:start position:0% that none of them knows the whole matrix 00:54:08.359 --> 00:54:12.010 align:start position:0% that none of them knows the whole matrix so 00:54:12.010 --> 00:54:12.020 align:start position:0% 00:54:12.020 --> 00:54:15.400 align:start position:0% when<00:54:12.619> we<00:54:12.880> would<00:54:13.880> be<00:54:14.030> when<00:54:14.900> we<00:54:15.020> wrote<00:54:15.140> this<00:54:15.290> in 00:54:15.400 --> 00:54:15.410 align:start position:0% when we would be when we wrote this in 00:54:15.410 --> 00:54:17.740 align:start position:0% when we would be when we wrote this in 2002<00:54:15.890> is<00:54:16.010> really<00:54:16.220> you<00:54:16.430> know<00:54:16.550> like<00:54:17.450> there's 00:54:17.740 --> 00:54:17.750 align:start position:0% 2002 is really you know like there's 00:54:17.750 --> 00:54:19.060 align:start position:0% 2002 is really you know like there's going<00:54:17.900> to<00:54:17.990> be<00:54:18.050> lots<00:54:18.530> and<00:54:18.800> lots<00:54:18.980> of 00:54:19.060 --> 00:54:19.070 align:start position:0% going to be lots and lots of 00:54:19.070 --> 00:54:20.590 align:start position:0% going to be lots and lots of peer-to-peer<00:54:19.340> application<00:54:20.060> just<00:54:20.180> right 00:54:20.590 --> 00:54:20.600 align:start position:0% peer-to-peer application just right 00:54:20.600 --> 00:54:28.120 align:start position:0% peer-to-peer application just right around<00:54:20.810> the<00:54:20.990> corner<00:54:21.350> but<00:54:25.060> now<00:54:26.060> is<00:54:26.570> the<00:54:27.530> time<00:54:27.710> I 00:54:28.120 --> 00:54:28.130 align:start position:0% around the corner but now is the time I 00:54:28.130 --> 00:54:32.530 align:start position:0% around the corner but now is the time I mean<00:54:28.690> I'm<00:54:29.740> seeing<00:54:30.740> that<00:54:31.160> there's<00:54:32.119> lots<00:54:32.420> and 00:54:32.530 --> 00:54:32.540 align:start position:0% mean I'm seeing that there's lots and 00:54:32.540 --> 00:54:34.090 align:start position:0% mean I'm seeing that there's lots and lots<00:54:32.750> of<00:54:32.840> peer-to-peer<00:54:33.080> applications<00:54:33.410> right 00:54:34.090 --> 00:54:34.100 align:start position:0% lots of peer-to-peer applications right 00:54:34.100 --> 00:54:36.070 align:start position:0% lots of peer-to-peer applications right around<00:54:34.280> the<00:54:34.430> corner<00:54:34.820> and<00:54:35.270> I'm<00:54:35.540> seeing<00:54:35.810> that 00:54:36.070 --> 00:54:36.080 align:start position:0% around the corner and I'm seeing that 00:54:36.080 --> 00:54:38.770 align:start position:0% around the corner and I'm seeing that those<00:54:36.380> peer-to-peer<00:54:37.040> applications<00:54:37.780> will 00:54:38.770 --> 00:54:38.780 align:start position:0% those peer-to-peer applications will 00:54:38.780 --> 00:54:43.600 align:start position:0% those peer-to-peer applications will need<00:54:39.080> notions<00:54:39.680> like<00:54:41.890> reputation<00:54:42.890> identity 00:54:43.600 --> 00:54:43.610 align:start position:0% need notions like reputation identity 00:54:43.610 --> 00:54:46.060 align:start position:0% need notions like reputation identity the<00:54:43.880> ability<00:54:44.330> to<00:54:44.360> identify<00:54:45.290> in<00:54:45.830> a 00:54:46.060 --> 00:54:46.070 align:start position:0% the ability to identify in a 00:54:46.070 --> 00:54:50.470 align:start position:0% the ability to identify in a decentralized<00:54:46.400> way<00:54:48.850> adversarial<00:54:49.850> nodes<00:54:50.119> and 00:54:50.470 --> 00:54:50.480 align:start position:0% decentralized way adversarial nodes and 00:54:50.480 --> 00:54:52.840 align:start position:0% decentralized way adversarial nodes and in<00:54:50.780> a<00:54:50.900> decentralized<00:54:51.530> way<00:54:51.619> be<00:54:52.280> able<00:54:52.490> to<00:54:52.610> self 00:54:52.840 --> 00:54:52.850 align:start position:0% in a decentralized way be able to self 00:54:52.850 --> 00:54:55.270 align:start position:0% in a decentralized way be able to self organize<00:54:53.090> to<00:54:53.660> avoid<00:54:53.990> those<00:54:54.200> out<00:54:54.350> adversaries 00:54:55.270 --> 00:54:55.280 align:start position:0% organize to avoid those out adversaries 00:54:55.280 --> 00:54:59.020 align:start position:0% organize to avoid those out adversaries and<00:54:56.560> and<00:54:57.560> the<00:54:58.130> exciting<00:54:58.490> thing<00:54:58.580> this<00:54:58.820> is<00:54:59.000> not 00:54:59.020 --> 00:54:59.030 align:start position:0% and and the exciting thing this is not 00:54:59.030 --> 00:55:03.609 align:start position:0% and and the exciting thing this is not really<00:54:59.810> about<00:55:00.580> music<00:55:01.580> sharing<00:55:02.000> I<00:55:02.210> mean<00:55:03.110> you 00:55:03.609 --> 00:55:03.619 align:start position:0% really about music sharing I mean you 00:55:03.619 --> 00:55:05.470 align:start position:0% really about music sharing I mean you take<00:55:03.860> a<00:55:03.920> look<00:55:04.190> at<00:55:04.369> lots<00:55:04.760> of<00:55:04.910> different<00:55:04.970> graphs 00:55:05.470 --> 00:55:05.480 align:start position:0% take a look at lots of different graphs 00:55:05.480 --> 00:55:07.960 align:start position:0% take a look at lots of different graphs and<00:55:05.750> you<00:55:06.020> can<00:55:06.200> imagine<00:55:06.440> lots<00:55:07.280> of<00:55:07.490> different 00:55:07.960 --> 00:55:07.970 align:start position:0% and you can imagine lots of different 00:55:07.970 --> 00:55:09.460 align:start position:0% and you can imagine lots of different computations<00:55:08.600> that<00:55:08.660> can<00:55:08.960> be<00:55:09.080> did<00:55:09.260> trust 00:55:09.460 --> 00:55:09.470 align:start position:0% computations that can be did trust 00:55:09.470 --> 00:55:10.930 align:start position:0% computations that can be did trust computations<00:55:10.070> that<00:55:10.130> can<00:55:10.369> be<00:55:10.460> done<00:55:10.610> among 00:55:10.930 --> 00:55:10.940 align:start position:0% computations that can be done among 00:55:10.940 --> 00:55:13.930 align:start position:0% computations that can be done among those<00:55:11.150> graphs<00:55:11.800> so<00:55:12.800> for<00:55:13.100> example<00:55:13.520> I<00:55:13.580> mean<00:55:13.760> one 00:55:13.930 --> 00:55:13.940 align:start position:0% those graphs so for example I mean one 00:55:13.940 --> 00:55:17.020 align:start position:0% those graphs so for example I mean one thing<00:55:14.150> that<00:55:14.800> I'm<00:55:15.800> very<00:55:16.100> interested<00:55:16.340> in<00:55:16.730> is 00:55:17.020 --> 00:55:17.030 align:start position:0% thing that I'm very interested in is 00:55:17.030 --> 00:55:21.430 align:start position:0% thing that I'm very interested in is active<00:55:17.810> stations<00:55:18.170> and<00:55:19.810> by<00:55:20.810> and<00:55:21.020> large<00:55:21.080> I<00:55:21.410> mean 00:55:21.430 --> 00:55:21.440 align:start position:0% active stations and by and large I mean 00:55:21.440 --> 00:55:23.740 align:start position:0% active stations and by and large I mean people<00:55:21.859> think<00:55:22.040> about<00:55:22.190> identity<00:55:22.760> computation 00:55:23.740 --> 00:55:23.750 align:start position:0% people think about identity computation 00:55:23.750 --> 00:55:24.420 align:start position:0% people think about identity computation in<00:55:23.930> the<00:55:24.050> front 00:55:24.420 --> 00:55:24.430 align:start position:0% in the front 00:55:24.430 --> 00:55:27.000 align:start position:0% in the front Matis<00:55:24.850> access<00:55:25.360> station<00:55:25.720> so<00:55:26.020> people<00:55:26.830> will 00:55:27.000 --> 00:55:27.010 align:start position:0% Matis access station so people will 00:55:27.010 --> 00:55:29.610 align:start position:0% Matis access station so people will attest<00:55:27.660> like<00:55:28.660> I<00:55:28.810> will<00:55:28.990> plant<00:55:29.200> that<00:55:29.380> I<00:55:29.410> have<00:55:29.590> a 00:55:29.610 --> 00:55:29.620 align:start position:0% attest like I will plant that I have a 00:55:29.620 --> 00:55:32.730 align:start position:0% attest like I will plant that I have a certain<00:55:29.830> property<00:55:30.220> and<00:55:31.260> other<00:55:32.260> people<00:55:32.620> will 00:55:32.730 --> 00:55:32.740 align:start position:0% certain property and other people will 00:55:32.740 --> 00:55:36.270 align:start position:0% certain property and other people will attest<00:55:33.100> that<00:55:34.060> I<00:55:34.330> have<00:55:34.510> that<00:55:34.660> problem<00:55:35.160> but<00:55:36.160> the 00:55:36.270 --> 00:55:36.280 align:start position:0% attest that I have that problem but the 00:55:36.280 --> 00:55:39.720 align:start position:0% attest that I have that problem but the problem<00:55:36.430> with<00:55:37.330> that<00:55:37.360> is<00:55:37.750> well<00:55:38.260> I<00:55:38.590> mean<00:55:39.040> who 00:55:39.720 --> 00:55:39.730 align:start position:0% problem with that is well I mean who 00:55:39.730 --> 00:55:42.210 align:start position:0% problem with that is well I mean who knows<00:55:39.970> these<00:55:40.690> other<00:55:40.810> people<00:55:41.200> who<00:55:41.380> are<00:55:41.860> or 00:55:42.210 --> 00:55:42.220 align:start position:0% knows these other people who are or 00:55:42.220 --> 00:55:43.890 align:start position:0% knows these other people who are or attesting<00:55:42.820> that<00:55:43.000> I<00:55:43.030> have<00:55:43.210> this<00:55:43.360> property<00:55:43.720> and 00:55:43.890 --> 00:55:43.900 align:start position:0% attesting that I have this property and 00:55:43.900 --> 00:55:45.420 align:start position:0% attesting that I have this property and in<00:55:43.960> fact<00:55:44.110> I<00:55:44.260> can<00:55:44.440> make<00:55:44.560> five<00:55:44.740> hundred<00:55:44.770> civils 00:55:45.420 --> 00:55:45.430 align:start position:0% in fact I can make five hundred civils 00:55:45.430 --> 00:55:48.710 align:start position:0% in fact I can make five hundred civils but<00:55:45.910> all<00:55:46.030> the<00:55:46.150> tests<00:55:46.510> that<00:55:46.620> my<00:55:47.620> name<00:55:47.800> is<00:55:47.920> John 00:55:48.710 --> 00:55:48.720 align:start position:0% but all the tests that my name is John 00:55:48.720 --> 00:55:50.910 align:start position:0% but all the tests that my name is John wait<00:55:49.720> a<00:55:49.870> second 00:55:50.910 --> 00:55:50.920 align:start position:0% wait a second 00:55:50.920 --> 00:55:54.540 align:start position:0% wait a second and<00:55:51.310> so<00:55:52.150> though<00:55:52.810> but<00:55:53.290> if<00:55:53.440> we<00:55:53.650> wait 00:55:54.540 --> 00:55:54.550 align:start position:0% and so though but if we wait 00:55:54.550 --> 00:55:59.820 align:start position:0% and so though but if we wait attestations<00:55:55.300> by<00:55:56.640> a<00:55:57.640> trust<00:55:58.330> score<00:55:58.690> then<00:55:59.560> all 00:55:59.820 --> 00:55:59.830 align:start position:0% attestations by a trust score then all 00:55:59.830 --> 00:56:02.370 align:start position:0% attestations by a trust score then all of<00:55:59.860> a<00:56:00.040> sudden<00:56:00.070> we<00:56:00.580> have<00:56:00.850> a<00:56:01.300> test<00:56:01.840> issues<00:56:02.140> that 00:56:02.370 --> 00:56:02.380 align:start position:0% of a sudden we have a test issues that 00:56:02.380 --> 00:56:04.650 align:start position:0% of a sudden we have a test issues that are<00:56:02.500> much<00:56:02.650> more<00:56:02.830> justifiable<00:56:03.540> similarly<00:56:04.540> if 00:56:04.650 --> 00:56:04.660 align:start position:0% are much more justifiable similarly if 00:56:04.660 --> 00:56:06.390 align:start position:0% are much more justifiable similarly if you<00:56:04.780> imagine<00:56:05.020> kind<00:56:05.350> of<00:56:05.500> a<00:56:05.620> decentralized 00:56:06.390 --> 00:56:06.400 align:start position:0% you imagine kind of a decentralized 00:56:06.400 --> 00:56:08.850 align:start position:0% you imagine kind of a decentralized finance<00:56:06.820> application<00:56:07.450> you<00:56:08.380> can<00:56:08.560> take<00:56:08.740> the 00:56:08.850 --> 00:56:08.860 align:start position:0% finance application you can take the 00:56:08.860 --> 00:56:11.670 align:start position:0% finance application you can take the graph<00:56:09.100> of<00:56:09.370> loan<00:56:09.970> repayments<00:56:10.390> and<00:56:10.900> then 00:56:11.670 --> 00:56:11.680 align:start position:0% graph of loan repayments and then 00:56:11.680 --> 00:56:14.530 align:start position:0% graph of loan repayments and then compute<00:56:12.130> a<00:56:12.190> credit<00:56:12.490> score<00:56:12.610> in<00:56:13.330> a<00:56:13.480> similar<00:56:13.870> way 00:56:14.530 --> 00:56:14.540 align:start position:0% compute a credit score in a similar way 00:56:14.540 --> 00:56:19.060 align:start position:0% compute a credit score in a similar way in<00:56:14.780> a<00:56:14.840> decentralized<00:56:15.350> way<00:56:17.440> another<00:56:18.440> another 00:56:19.060 --> 00:56:19.070 align:start position:0% in a decentralized way another another 00:56:19.070 --> 00:56:20.850 align:start position:0% in a decentralized way another another application<00:56:19.460> that<00:56:19.760> I<00:56:19.790> really<00:56:20.090> like<00:56:20.270> is 00:56:20.850 --> 00:56:20.860 align:start position:0% application that I really like is 00:56:20.860 --> 00:56:22.960 align:start position:0% application that I really like is actually<00:56:21.860> I<00:56:22.070> have<00:56:22.190> two<00:56:22.370> minutes<00:56:22.550> left<00:56:22.670> and<00:56:22.910> I 00:56:22.960 --> 00:56:22.970 align:start position:0% actually I have two minutes left and I 00:56:22.970 --> 00:56:25.240 align:start position:0% actually I have two minutes left and I wanna<00:56:23.210> I<00:56:23.510> want<00:56:24.080> to<00:56:24.140> move<00:56:24.260> on<00:56:24.350> to<00:56:24.500> questions<00:56:24.620> so 00:56:25.240 --> 00:56:25.250 align:start position:0% wanna I want to move on to questions so 00:56:25.250 --> 00:56:28.930 align:start position:0% wanna I want to move on to questions so let<00:56:25.730> me<00:56:25.820> just<00:56:26.350> so<00:56:27.350> so<00:56:27.890> to<00:56:28.250> me<00:56:28.400> this<00:56:28.550> is<00:56:28.610> a<00:56:28.730> very 00:56:28.930 --> 00:56:28.940 align:start position:0% let me just so so to me this is a very 00:56:28.940 --> 00:56:30.910 align:start position:0% let me just so so to me this is a very exciting<00:56:29.330> time<00:56:29.660> before<00:56:30.050> trust<00:56:30.350> computation 00:56:30.910 --> 00:56:30.920 align:start position:0% exciting time before trust computation 00:56:30.920 --> 00:56:32.680 align:start position:0% exciting time before trust computation their<00:56:31.070> point<00:56:31.280> of<00:56:31.310> view<00:56:31.460> networks<00:56:31.910> and<00:56:32.420> I<00:56:32.480> think 00:56:32.680 --> 00:56:32.690 align:start position:0% their point of view networks and I think 00:56:32.690 --> 00:56:33.520 align:start position:0% their point of view networks and I think there's<00:56:32.840> a<00:56:32.930> lot<00:56:33.110> of<00:56:33.140> really<00:56:33.410> interesting 00:56:33.520 --> 00:56:33.530 align:start position:0% there's a lot of really interesting 00:56:33.530 --> 00:56:35.530 align:start position:0% there's a lot of really interesting research<00:56:34.160> opportunities<00:56:34.880> and<00:56:35.120> this<00:56:35.240> is<00:56:35.390> one 00:56:35.530 --> 00:56:35.540 align:start position:0% research opportunities and this is one 00:56:35.540 --> 00:56:36.610 align:start position:0% research opportunities and this is one of<00:56:35.660> the<00:56:35.780> things<00:56:35.960> that<00:56:36.110> I'm<00:56:36.200> excited<00:56:36.320> about 00:56:36.610 --> 00:56:36.620 align:start position:0% of the things that I'm excited about 00:56:36.620 --> 00:56:39.730 align:start position:0% of the things that I'm excited about area<00:56:37.010> of<00:56:37.100> the<00:56:37.160> community<00:56:37.640> I<00:56:37.850> think<00:56:38.470> is<00:56:39.470> really 00:56:39.730 --> 00:56:39.740 align:start position:0% area of the community I think is really 00:56:39.740 --> 00:56:42.660 align:start position:0% area of the community I think is really interesting<00:56:39.890> in<00:56:40.640> the<00:56:40.940> current<00:56:41.270> context<00:56:41.780> to 00:56:42.660 --> 00:56:42.670 align:start position:0% interesting in the current context to 00:56:42.670 --> 00:56:45.850 align:start position:0% interesting in the current context to compute<00:56:43.670> these<00:56:44.120> trust<00:56:44.450> computations<00:56:45.080> without 00:56:45.850 --> 00:56:45.860 align:start position:0% compute these trust computations without 00:56:45.860 --> 00:56:48.970 align:start position:0% compute these trust computations without anybody<00:56:46.400> knowing<00:56:46.700> your<00:56:47.600> opinion<00:56:48.020> of<00:56:48.140> them<00:56:48.290> and 00:56:48.970 --> 00:56:48.980 align:start position:0% anybody knowing your opinion of them and 00:56:48.980 --> 00:56:52.540 align:start position:0% anybody knowing your opinion of them and so<00:56:49.160> that's<00:56:49.310> one<00:56:50.740> one<00:56:51.740> interesting<00:56:52.220> area<00:56:52.490> of 00:56:52.540 --> 00:56:52.550 align:start position:0% so that's one one interesting area of 00:56:52.550 --> 00:56:57.010 align:start position:0% so that's one one interesting area of research<00:56:52.850> a<00:56:53.300> second<00:56:54.080> is<00:56:55.570> we<00:56:56.570> can<00:56:56.750> imagine 00:56:57.010 --> 00:56:57.020 align:start position:0% research a second is we can imagine 00:56:57.020 --> 00:56:59.440 align:start position:0% research a second is we can imagine tweaking<00:56:57.860> the<00:56:58.160> trust<00:56:58.430> computations<00:56:59.090> so<00:56:59.270> that 00:56:59.440 --> 00:56:59.450 align:start position:0% tweaking the trust computations so that 00:56:59.450 --> 00:57:01.900 align:start position:0% tweaking the trust computations so that different<00:56:59.840> people's<00:57:00.170> preferences<00:57:00.910> actually 00:57:01.900 --> 00:57:01.910 align:start position:0% different people's preferences actually 00:57:01.910 --> 00:57:04.990 align:start position:0% different people's preferences actually make<00:57:02.810> for<00:57:03.080> different<00:57:03.590> levels<00:57:03.770> of<00:57:04.070> trust<00:57:04.370> so<00:57:04.850> we 00:57:04.990 --> 00:57:05.000 align:start position:0% make for different levels of trust so we 00:57:05.000 --> 00:57:06.790 align:start position:0% make for different levels of trust so we actually<00:57:05.180> go<00:57:05.450> back<00:57:05.690> to<00:57:05.720> rather<00:57:06.110> than<00:57:06.320> a<00:57:06.350> single 00:57:06.790 --> 00:57:06.800 align:start position:0% actually go back to rather than a single 00:57:06.800 --> 00:57:10.570 align:start position:0% actually go back to rather than a single trust<00:57:07.040> vector<00:57:07.370> multiple<00:57:08.240> transfers<00:57:09.430> and<00:57:10.430> then 00:57:10.570 --> 00:57:10.580 align:start position:0% trust vector multiple transfers and then 00:57:10.580 --> 00:57:12.670 align:start position:0% trust vector multiple transfers and then finally<00:57:10.970> we<00:57:11.660> can<00:57:11.780> look<00:57:11.960> at<00:57:12.080> dyadic<00:57:12.380> graph 00:57:12.670 --> 00:57:12.680 align:start position:0% finally we can look at dyadic graph 00:57:12.680 --> 00:57:14.020 align:start position:0% finally we can look at dyadic graph structures<00:57:13.130> for<00:57:13.340> example<00:57:13.370> if<00:57:13.790> you<00:57:13.880> have 00:57:14.020 --> 00:57:14.030 align:start position:0% structures for example if you have 00:57:14.030 --> 00:57:15.970 align:start position:0% structures for example if you have buyers<00:57:14.330> and<00:57:14.690> sellers<00:57:15.080> or<00:57:15.260> two<00:57:15.410> different<00:57:15.770> kind 00:57:15.970 --> 00:57:15.980 align:start position:0% buyers and sellers or two different kind 00:57:15.980 --> 00:57:17.200 align:start position:0% buyers and sellers or two different kind of<00:57:16.070> people<00:57:16.370> who<00:57:16.460> interact<00:57:16.730> with<00:57:16.970> one<00:57:17.180> another 00:57:17.200 --> 00:57:17.210 align:start position:0% of people who interact with one another 00:57:17.210 --> 00:57:21.040 align:start position:0% of people who interact with one another but<00:57:18.020> not<00:57:18.200> with<00:57:18.500> with<00:57:18.830> one<00:57:19.070> another<00:57:19.390> and<00:57:20.390> those 00:57:21.040 --> 00:57:21.050 align:start position:0% but not with with one another and those 00:57:21.050 --> 00:57:22.750 align:start position:0% but not with with one another and those will<00:57:21.290> lead<00:57:21.470> to<00:57:21.620> trust<00:57:21.860> computations<00:57:22.520> that<00:57:22.610> are 00:57:22.750 --> 00:57:22.760 align:start position:0% will lead to trust computations that are 00:57:22.760 --> 00:57:25.090 align:start position:0% will lead to trust computations that are more<00:57:23.030> around<00:57:23.330> the<00:57:23.570> see<00:57:23.840> evaluative<00:57:24.470> singular 00:57:25.090 --> 00:57:25.100 align:start position:0% more around the see evaluative singular 00:57:25.100 --> 00:57:27.220 align:start position:0% more around the see evaluative singular value<00:57:25.370> decomposition<00:57:25.400> rather<00:57:26.360> than<00:57:27.110> the 00:57:27.220 --> 00:57:27.230 align:start position:0% value decomposition rather than the 00:57:27.230 --> 00:57:30.190 align:start position:0% value decomposition rather than the eigenvector<00:57:27.770> calculation<00:57:28.750> so<00:57:29.750> that's<00:57:29.930> all 00:57:30.190 --> 00:57:30.200 align:start position:0% eigenvector calculation so that's all 00:57:30.200 --> 00:57:39.310 align:start position:0% eigenvector calculation so that's all thank<00:57:30.620> you<00:57:30.740> all<00:57:30.950> very<00:57:30.980> much 00:57:39.310 --> 00:57:39.320 align:start position:0% 00:57:39.320 --> 00:57:50.120 align:start position:0% questions<00:57:40.320> people<00:57:41.310> question<00:57:44.960> yes<00:57:48.950> yeah<00:57:49.950> I 00:57:50.120 --> 00:57:50.130 align:start position:0% questions people question yes yeah I 00:57:50.130 --> 00:57:55.579 align:start position:0% questions people question yes yeah I mean<00:57:50.310> so<00:57:50.790> so<00:57:51.380> absolutely<00:57:52.820> I<00:57:54.109> mean<00:57:55.109> the<00:57:55.320> way 00:57:55.579 --> 00:57:55.589 align:start position:0% mean so so absolutely I mean the way 00:57:55.589 --> 00:57:59.270 align:start position:0% mean so so absolutely I mean the way that<00:57:55.619> I<00:57:55.800> see<00:57:56.010> PageRank<00:57:57.000> is<00:57:57.329> as<00:57:57.690> an<00:57:58.290> example<00:57:59.160> of 00:57:59.270 --> 00:57:59.280 align:start position:0% that I see PageRank is as an example of 00:57:59.280 --> 00:58:00.859 align:start position:0% that I see PageRank is as an example of trust<00:57:59.490> computations<00:58:00.089> and<00:58:00.329> so<00:58:00.540> yes<00:58:00.720> absolutely 00:58:00.859 --> 00:58:00.869 align:start position:0% trust computations and so yes absolutely 00:58:00.869 --> 00:58:02.870 align:start position:0% trust computations and so yes absolutely I<00:58:01.290> think<00:58:01.500> it'll<00:58:01.770> be<00:58:01.890> really<00:58:01.920> valuable<00:58:02.369> in<00:58:02.790> the 00:58:02.870 --> 00:58:02.880 align:start position:0% I think it'll be really valuable in the 00:58:02.880 --> 00:58:13.069 align:start position:0% I think it'll be really valuable in the context<00:58:03.660> of<00:58:03.750> history<00:58:09.230> I'm<00:58:10.230> sorry<00:58:11.030> yeah<00:58:12.030> yeah 00:58:13.069 --> 00:58:13.079 align:start position:0% context of history I'm sorry yeah yeah 00:58:13.079 --> 00:58:15.440 align:start position:0% context of history I'm sorry yeah yeah so<00:58:13.470> basically<00:58:13.890> kind<00:58:14.190> of<00:58:14.310> if<00:58:14.880> the<00:58:15.089> message 00:58:15.440 --> 00:58:15.450 align:start position:0% so basically kind of if the message 00:58:15.450 --> 00:58:20.560 align:start position:0% so basically kind of if the message complexity<00:58:15.960> is<00:58:17.210> the<00:58:18.210> is<00:58:18.720> linear<00:58:19.470> to<00:58:19.890> the<00:58:19.920> norm 00:58:20.560 --> 00:58:20.570 align:start position:0% complexity is the is linear to the norm 00:58:20.570 --> 00:58:23.540 align:start position:0% complexity is the is linear to the norm nodes<00:58:21.570> of<00:58:21.780> the<00:58:21.869> network<00:58:21.900> and<00:58:22.829> the<00:58:22.890> reason<00:58:23.339> why 00:58:23.540 --> 00:58:23.550 align:start position:0% nodes of the network and the reason why 00:58:23.550 --> 00:58:28.579 align:start position:0% nodes of the network and the reason why is<00:58:23.940> because<00:58:24.859> each<00:58:25.859> peer<00:58:26.339> only<00:58:26.849> has<00:58:27.089> a<00:58:27.599> certain 00:58:28.579 --> 00:58:28.589 align:start position:0% is because each peer only has a certain 00:58:28.589 --> 00:58:30.290 align:start position:0% is because each peer only has a certain number<00:58:28.710> appears<00:58:29.190> that<00:58:29.400> they<00:58:29.550> interact<00:58:29.910> like 00:58:30.290 --> 00:58:30.300 align:start position:0% number appears that they interact like 00:58:30.300 --> 00:58:32.420 align:start position:0% number appears that they interact like say<00:58:30.510> ten<00:58:31.320> or<00:58:31.349> something<00:58:31.740> like<00:58:31.829> that 00:58:32.420 --> 00:58:32.430 align:start position:0% say ten or something like that 00:58:32.430 --> 00:58:36.800 align:start position:0% say ten or something like that rather<00:58:32.940> than<00:58:33.270> every<00:58:34.109> peer<00:58:35.599> every<00:58:36.599> peer 00:58:36.800 --> 00:58:36.810 align:start position:0% rather than every peer every peer 00:58:36.810 --> 00:58:38.569 align:start position:0% rather than every peer every peer interacting<00:58:37.320> with<00:58:37.440> every<00:58:37.710> other<00:58:38.099> peer<00:58:38.430> in 00:58:38.569 --> 00:58:38.579 align:start position:0% interacting with every other peer in 00:58:38.579 --> 00:58:43.200 align:start position:0% interacting with every other peer in that<00:58:38.730> case<00:58:38.910> it<00:58:39.089> would<00:58:39.180> be<00:58:39.210> nice<00:58:39.599> right 00:58:43.200 --> 00:58:43.210 align:start position:0% 00:58:43.210 --> 00:58:45.090 align:start position:0% that's<00:58:43.810> right<00:58:43.930> exactly<00:58:44.110> yeah<00:58:44.800> and<00:58:44.920> that 00:58:45.090 --> 00:58:45.100 align:start position:0% that's right exactly yeah and that 00:58:45.100 --> 00:58:49.080 align:start position:0% that's right exactly yeah and that testing<00:58:45.550> yes<00:58:46.120> it<00:58:46.510> is<00:58:46.750> a<00:58:46.780> paltry<00:58:47.410> make<00:58:47.950> of<00:58:48.190> you 00:58:49.080 --> 00:58:49.090 align:start position:0% testing yes it is a paltry make of you 00:58:49.090 --> 00:58:51.120 align:start position:0% testing yes it is a paltry make of you generally<00:58:49.600> I'm<00:58:50.320> somebody's<00:58:50.650> a<00:58:50.710> good<00:58:50.830> Pilate 00:58:51.120 --> 00:58:51.130 align:start position:0% generally I'm somebody's a good Pilate 00:58:51.130 --> 00:58:53.580 align:start position:0% generally I'm somebody's a good Pilate algorri<00:58:51.670> is<00:58:52.450> it<00:58:52.570> a<00:58:52.630> flighting<00:58:52.930> algorithm<00:58:53.320> yeah 00:58:53.580 --> 00:58:53.590 align:start position:0% algorri is it a flighting algorithm yeah 00:58:53.590 --> 00:58:56.910 align:start position:0% algorri is it a flighting algorithm yeah where<00:58:54.070> Palomas<00:58:54.910> is<00:58:55.150> our<00:58:55.300> printable<00:58:55.870> no<00:58:56.620> no<00:58:56.800> are 00:58:56.910 --> 00:58:56.920 align:start position:0% where Palomas is our printable no no are 00:58:56.920 --> 00:58:58.650 align:start position:0% where Palomas is our printable no no are you<00:58:57.070> you<00:58:57.340> can<00:58:57.520> actually<00:58:57.820> send<00:58:58.090> the<00:58:58.240> note<00:58:58.420> as 00:58:58.650 --> 00:58:58.660 align:start position:0% you you can actually send the note as 00:58:58.660 --> 00:59:00.690 align:start position:0% you you can actually send the note as you<00:58:58.690> can<00:58:58.960> send<00:58:59.140> the<00:58:59.230> message<00:58:59.320> only<00:58:59.680> to<00:59:00.100> the 00:59:00.690 --> 00:59:00.700 align:start position:0% you can send the message only to the 00:59:00.700 --> 00:59:02.100 align:start position:0% you can send the message only to the person<00:59:00.850> who<00:59:01.120> needs<00:59:01.270> to<00:59:01.450> get<00:59:01.570> the<00:59:01.690> message<00:59:01.990> and 00:59:02.100 --> 00:59:02.110 align:start position:0% person who needs to get the message and 00:59:02.110 --> 00:59:12.420 align:start position:0% person who needs to get the message and you<00:59:02.170> know<00:59:02.320> who<00:59:02.470> that<00:59:02.500> is<00:59:02.650> because<00:59:03.130> the 00:59:12.420 --> 00:59:12.430 align:start position:0% 00:59:12.430 --> 00:59:14.789 align:start position:0% I<00:59:12.460> mean<00:59:13.150> you<00:59:13.299> can<00:59:13.480> run<00:59:13.750> I<00:59:14.140> can<00:59:14.200> trust<00:59:14.559> in<00:59:14.710> the 00:59:14.789 --> 00:59:14.799 align:start position:0% I mean you can run I can trust in the 00:59:14.799 --> 00:59:16.799 align:start position:0% I mean you can run I can trust in the same<00:59:14.950> way<00:59:15.069> you<00:59:15.130> front<00:59:15.520> page<00:59:15.670> rank<00:59:15.940> with<00:59:16.390> just<00:59:16.690> a 00:59:16.799 --> 00:59:16.809 align:start position:0% same way you front page rank with just a 00:59:16.809 --> 00:59:19.500 align:start position:0% same way you front page rank with just a few<00:59:17.200> notes<00:59:17.440> I<00:59:17.890> think<00:59:18.160> the<00:59:18.520> important<00:59:19.000> thing<00:59:19.240> is 00:59:19.500 --> 00:59:19.510 align:start position:0% few notes I think the important thing is 00:59:19.510 --> 00:59:23.640 align:start position:0% few notes I think the important thing is you<00:59:20.470> want<00:59:21.190> to<00:59:21.250> make<00:59:21.400> sure<00:59:21.460> that<00:59:22.059> there<00:59:22.480> is<00:59:22.900> the 00:59:23.640 --> 00:59:23.650 align:start position:0% you want to make sure that there is the 00:59:23.650 --> 00:59:26.670 align:start position:0% you want to make sure that there is the number<00:59:24.069> of<00:59:24.309> adversarial<00:59:25.180> node<00:59:25.480> so<00:59:26.170> it's<00:59:26.529> not 00:59:26.670 --> 00:59:26.680 align:start position:0% number of adversarial node so it's not 00:59:26.680 --> 00:59:30.120 align:start position:0% number of adversarial node so it's not the<00:59:26.829> majority<00:59:27.960> are<00:59:28.960> you<00:59:29.140> trust<00:59:29.500> how<00:59:29.950> do<00:59:30.010> you 00:59:30.120 --> 00:59:30.130 align:start position:0% the majority are you trust how do you 00:59:30.130 --> 00:59:31.579 align:start position:0% the majority are you trust how do you trust<00:59:30.309> the 00:59:31.579 --> 00:59:31.589 align:start position:0% trust the 00:59:31.589 --> 00:59:33.799 align:start position:0% trust the plus<00:59:32.160> support<00:59:32.309> line<00:59:32.640> you're<00:59:32.880> appearing<00:59:33.209> near 00:59:33.799 --> 00:59:33.809 align:start position:0% plus support line you're appearing near 00:59:33.809 --> 00:59:34.670 align:start position:0% plus support line you're appearing near neighbors<00:59:34.109> good<00:59:34.289> news 00:59:34.670 --> 00:59:34.680 align:start position:0% neighbors good news 00:59:34.680 --> 00:59:36.650 align:start position:0% neighbors good news yeah<00:59:34.859> that's<00:59:35.519> great<00:59:35.699> that's<00:59:36.059> a<00:59:36.209> new<00:59:36.329> camera<00:59:36.630> I 00:59:36.650 --> 00:59:36.660 align:start position:0% yeah that's great that's a new camera I 00:59:36.660 --> 00:59:37.849 align:start position:0% yeah that's great that's a new camera I didn't<00:59:36.900> have<00:59:36.989> time<00:59:37.109> to<00:59:37.259> talk<00:59:37.380> about<00:59:37.529> it<00:59:37.739> today 00:59:37.849 --> 00:59:37.859 align:start position:0% didn't have time to talk about it today 00:59:37.859 --> 00:59:41.569 align:start position:0% didn't have time to talk about it today you<00:59:38.640> you<00:59:39.449> don't<00:59:39.719> in<00:59:39.930> this<00:59:40.170> so<00:59:40.709> what<00:59:40.979> what<00:59:41.430> we 00:59:41.569 --> 00:59:41.579 align:start position:0% you you don't in this so what what we 00:59:41.579 --> 00:59:43.759 align:start position:0% you you don't in this so what what we did<00:59:41.759> we<00:59:41.969> can<00:59:42.089> is<00:59:42.209> distributed<00:59:42.719> hash<00:59:42.839> tables<00:59:43.289> to 00:59:43.759 --> 00:59:43.769 align:start position:0% did we can is distributed hash tables to 00:59:43.769 --> 00:59:46.039 align:start position:0% did we can is distributed hash tables to have<00:59:43.979> a<00:59:44.009> score<00:59:44.400> manager<00:59:44.849> and<00:59:45.630> that<00:59:45.779> store 00:59:46.039 --> 00:59:46.049 align:start position:0% have a score manager and that store 00:59:46.049 --> 00:59:48.410 align:start position:0% have a score manager and that store manager<00:59:46.529> ISM<00:59:46.829> and<00:59:47.039> actually<00:59:47.849> it's<00:59:47.969> three 00:59:48.410 --> 00:59:48.420 align:start position:0% manager ISM and actually it's three 00:59:48.420 --> 00:59:51.979 align:start position:0% manager ISM and actually it's three score<00:59:48.779> managers<00:59:49.199> in<00:59:49.380> a<00:59:49.439> boat<00:59:49.789> and<00:59:50.789> that<00:59:51.150> that 00:59:51.979 --> 00:59:51.989 align:start position:0% score managers in a boat and that that 00:59:51.989 --> 00:59:58.390 align:start position:0% score managers in a boat and that that make<00:59:52.829> sure<00:59:53.039> that<00:59:53.219> those<00:59:53.699> are<00:59:53.939> trustworthy 00:59:58.390 --> 00:59:58.400 align:start position:0% 00:59:58.400 --> 01:00:04.009 align:start position:0% yeah<00:59:59.400> yeah<01:00:01.939> so<01:00:02.939> basically<01:00:03.359> and<01:00:03.749> this<01:00:03.900> is 01:00:04.009 --> 01:00:04.019 align:start position:0% yeah yeah so basically and this is 01:00:04.019 --> 01:00:05.390 align:start position:0% yeah yeah so basically and this is something<01:00:04.199> that<01:00:04.319> I<01:00:04.469> also<01:00:04.589> did<01:00:04.799> gets<01:00:05.069> you<01:00:05.189> into 01:00:05.390 --> 01:00:05.400 align:start position:0% something that I also did gets you into 01:00:05.400 --> 01:00:11.569 align:start position:0% something that I also did gets you into this<01:00:05.459> mock<01:00:09.380> what<01:00:10.380> we<01:00:10.499> have<01:00:10.739> to<01:00:10.920> do<01:00:11.099> is<01:00:11.219> we<01:00:11.369> have 01:00:11.569 --> 01:00:11.579 align:start position:0% this mock what we have to do is we have 01:00:11.579 --> 01:00:14.120 align:start position:0% this mock what we have to do is we have to<01:00:11.609> add<01:00:11.939> a<01:00:12.209> regularization<01:00:12.660> parameter<01:00:13.229> so 01:00:14.120 --> 01:00:14.130 align:start position:0% to add a regularization parameter so 01:00:14.130 --> 01:00:15.650 align:start position:0% to add a regularization parameter so right<01:00:14.369> now<01:00:14.519> what<01:00:14.759> could<01:00:14.999> happen<01:00:15.420> is<01:00:15.479> there 01:00:15.650 --> 01:00:15.660 align:start position:0% right now what could happen is there 01:00:15.660 --> 01:00:18.199 align:start position:0% right now what could happen is there could<01:00:15.809> be<01:00:15.839> a<01:00:15.959> click<01:00:16.259> and<01:00:17.189> that<01:00:17.249> clicked<01:00:17.759> you 01:00:18.199 --> 01:00:18.209 align:start position:0% could be a click and that clicked you 01:00:18.209 --> 01:00:20.329 align:start position:0% could be a click and that clicked you just<01:00:18.420> basically<01:00:18.539> end<01:00:18.959> up<01:00:19.140> never<01:00:19.829> converging 01:00:20.329 --> 01:00:20.339 align:start position:0% just basically end up never converging 01:00:20.339 --> 01:00:21.529 align:start position:0% just basically end up never converging because<01:00:20.549> you<01:00:20.640> never<01:00:20.729> get<01:00:20.939> out<01:00:20.999> of<01:00:21.119> that<01:00:21.239> click 01:00:21.529 --> 01:00:21.539 align:start position:0% because you never get out of that click 01:00:21.539 --> 01:00:24.890 align:start position:0% because you never get out of that click and<01:00:22.079> so<01:00:22.410> basically<01:00:22.829> what<01:00:23.069> we<01:00:23.219> have<01:00:23.249> is<01:00:23.819> in<01:00:24.420> page 01:00:24.890 --> 01:00:24.900 align:start position:0% and so basically what we have is in page 01:00:24.900 --> 01:00:27.880 align:start position:0% and so basically what we have is in page rank<01:00:24.930> what<01:00:25.319> they<01:00:25.439> do<01:00:25.499> is<01:00:25.739> they<01:00:25.890> say<01:00:26.099> you<01:00:27.059> know 01:00:27.880 --> 01:00:27.890 align:start position:0% rank what they do is they say you know 01:00:27.890 --> 01:00:30.859 align:start position:0% rank what they do is they say you know so<01:00:28.890> the<01:00:29.519> way<01:00:29.609> that<01:00:29.640> all<01:00:29.910> offering<01:00:30.509> that<01:00:30.689> is 01:00:30.859 --> 01:00:30.869 align:start position:0% so the way that all offering that is 01:00:30.869 --> 01:00:32.390 align:start position:0% so the way that all offering that is there's<01:00:31.439> a<01:00:31.529> probabilistic<01:00:32.069> interpretation 01:00:32.390 --> 01:00:32.400 align:start position:0% there's a probabilistic interpretation 01:00:32.400 --> 01:00:33.949 align:start position:0% there's a probabilistic interpretation of<01:00:33.119> this<01:00:33.269> the<01:00:33.449> problem<01:00:33.660> is<01:00:33.869> the 01:00:33.949 --> 01:00:33.959 align:start position:0% of this the problem is the 01:00:33.959 --> 01:00:36.049 align:start position:0% of this the problem is the interpretation<01:00:34.890> is<01:00:35.099> that<01:00:35.130> you're<01:00:35.430> jumping 01:00:36.049 --> 01:00:36.059 align:start position:0% interpretation is that you're jumping 01:00:36.059 --> 01:00:39.499 align:start position:0% interpretation is that you're jumping around<01:00:36.329> from<01:00:36.749> node<01:00:37.140> to<01:00:37.349> node<01:00:38.509> following 01:00:39.499 --> 01:00:39.509 align:start position:0% around from node to node following 01:00:39.509 --> 01:00:41.779 align:start position:0% around from node to node following people's<01:00:40.229> local<01:00:40.619> trust<01:00:40.920> of<01:00:41.099> one<01:00:41.279> another<01:00:41.609> and 01:00:41.779 --> 01:00:41.789 align:start position:0% people's local trust of one another and 01:00:41.789 --> 01:00:44.839 align:start position:0% people's local trust of one another and then<01:00:42.390> after<01:00:42.959> a<01:00:42.989> long<01:00:43.289> period<01:00:43.799> of<01:00:43.859> time<01:00:44.160> your 01:00:44.839 --> 01:00:44.849 align:start position:0% then after a long period of time your 01:00:44.849 --> 01:00:47.359 align:start position:0% then after a long period of time your likelihood<01:00:45.209> of<01:00:45.390> being<01:00:45.689> at<01:00:46.079> a<01:00:46.109> node<01:00:46.469> that<01:00:46.769> is 01:00:47.359 --> 01:00:47.369 align:start position:0% likelihood of being at a node that is 01:00:47.369 --> 01:00:50.479 align:start position:0% likelihood of being at a node that is the<01:00:47.519> IB<01:00:47.670> trust<01:00:47.999> for<01:00:48.239> that<01:00:48.949> now<01:00:49.949> in<01:00:50.189> order<01:00:50.369> to 01:00:50.479 --> 01:00:50.489 align:start position:0% the IB trust for that now in order to 01:00:50.489 --> 01:00:52.429 align:start position:0% the IB trust for that now in order to make<01:00:50.670> that<01:00:50.819> work<01:00:50.880> you<01:00:51.630> can't<01:00:51.839> get<01:00:51.989> stuck<01:00:52.229> in<01:00:52.349> it 01:00:52.429 --> 01:00:52.439 align:start position:0% make that work you can't get stuck in it 01:00:52.439 --> 01:00:54.140 align:start position:0% make that work you can't get stuck in it away<01:00:52.650> so<01:00:53.249> you<01:00:53.309> have<01:00:53.609> to<01:00:53.729> have<01:00:53.880> some 01:00:54.140 --> 01:00:54.150 align:start position:0% away so you have to have some 01:00:54.150 --> 01:00:56.059 align:start position:0% away so you have to have some probability<01:00:54.779> of<01:00:54.929> jumping<01:00:55.259> to<01:00:55.410> a<01:00:55.439> random<01:00:55.949> note 01:00:56.059 --> 01:00:56.069 align:start position:0% probability of jumping to a random note 01:00:56.069 --> 01:00:58.099 align:start position:0% probability of jumping to a random note and<01:00:56.670> once<01:00:56.969> you<01:00:57.119> have<01:00:57.299> that<01:00:57.539> regularization 01:00:58.099 --> 01:00:58.109 align:start position:0% and once you have that regularization 01:00:58.109 --> 01:01:01.939 align:start position:0% and once you have that regularization parameter<01:00:58.559> as<01:00:59.189> a<01:01:00.650> convergence<01:01:01.650> is<01:01:01.739> quite 01:01:01.939 --> 01:01:01.949 align:start position:0% parameter as a convergence is quite 01:01:01.949 --> 01:01:02.670 align:start position:0% parameter as a convergence is quite quite<01:01:02.189> fine 01:01:02.670 --> 01:01:02.680 align:start position:0% quite fine 01:01:02.680 --> 01:01:04.200 align:start position:0% quite fine and<01:01:02.770> it<01:01:02.890> depends<01:01:03.250> on<01:01:03.340> what<01:01:03.550> that<01:01:03.760> probability 01:01:04.200 --> 01:01:04.210 align:start position:0% and it depends on what that probability 01:01:04.210 --> 01:01:09.870 align:start position:0% and it depends on what that probability is<01:01:04.480> you<01:01:05.140> can<01:01:05.260> actually<01:01:05.560> tweak<01:01:05.800> the<01:01:05.950> different 01:01:09.870 --> 01:01:09.880 align:start position:0% 01:01:09.880 --> 01:01:36.099 align:start position:0% you<01:01:10.880> know<01:01:33.219> next<01:01:34.219> half<01:01:34.579> dead<01:01:35.059> rat<01:01:35.329> from<01:01:35.569> Altea 01:01:36.099 --> 01:01:36.109 align:start position:0% you know next half dead rat from Altea 01:01:36.109 --> 01:01:38.380 align:start position:0% you know next half dead rat from Altea and<01:01:36.529> there's<01:01:36.739> IP<01:01:36.979> address<01:01:37.489> on<01:01:37.640> the<01:01:37.670> board<01:01:37.999> so<01:01:38.359> I 01:01:38.380 --> 01:01:38.390 align:start position:0% and there's IP address on the board so I 01:01:38.390 --> 01:01:42.670 align:start position:0% and there's IP address on the board so I guess<01:01:38.809> level<01:01:39.529> another<01:01:39.799> yeah<01:01:40.599> so<01:01:41.599> here<01:01:42.109> is<01:01:42.380> the 01:01:42.670 --> 01:01:42.680 align:start position:0% guess level another yeah so here is the 01:01:42.680 --> 01:01:44.680 align:start position:0% guess level another yeah so here is the there's<01:01:43.489> a<01:01:43.579> fee<01:01:43.729> amount<01:01:44.029> of<01:01:44.180> the<01:01:44.329> five 01:01:44.680 --> 01:01:44.690 align:start position:0% there's a fee amount of the five 01:01:44.690 --> 01:01:47.349 align:start position:0% there's a fee amount of the five gigahertz<01:01:44.989> in<01:01:45.289> the<01:01:45.380> 2.4<01:01:45.999> and<01:01:46.999> you're<01:01:47.150> welcome 01:01:47.349 --> 01:01:47.359 align:start position:0% gigahertz in the 2.4 and you're welcome 01:01:47.359 --> 01:01:49.809 align:start position:0% gigahertz in the 2.4 and you're welcome to<01:01:47.569> log<01:01:48.079> in<01:01:48.229> to<01:01:48.259> enforce<01:01:48.709> them<01:01:48.890> so<01:01:49.069> internet 01:01:49.809 --> 01:01:49.819 align:start position:0% to log in to enforce them so internet 01:01:49.819 --> 01:01:52.479 align:start position:0% to log in to enforce them so internet connected<01:01:50.269> to<01:01:50.479> it<01:01:50.630> but<01:01:50.869> you<01:01:51.859> can<01:01:52.069> go<01:01:52.279> to<01:01:52.369> the 01:01:52.479 --> 01:01:52.489 align:start position:0% connected to it but you can go to the 01:01:52.489 --> 01:01:54.849 align:start position:0% connected to it but you can go to the dashboard<01:01:52.670> and<01:01:53.390> see<01:01:53.749> the<01:01:53.900> the<01:01:53.930> interface<01:01:54.619> that 01:01:54.849 --> 01:01:54.859 align:start position:0% dashboard and see the the interface that 01:01:54.859 --> 01:02:00.310 align:start position:0% dashboard and see the the interface that are<01:01:55.039> in<01:01:55.519> users<01:01:55.969> see<01:01:56.420> with<01:01:56.660> a 01:02:00.310 --> 01:02:00.320 align:start position:0% 01:02:00.320 --> 01:02:08.860 align:start position:0% [Music] 01:02:08.860 --> 01:02:08.870 align:start position:0% 01:02:08.870 --> 01:02:14.030 align:start position:0% okay<01:02:11.840> hi<01:02:12.840> I'm<01:02:12.870> Debra<01:02:13.530> I'm<01:02:13.680> one<01:02:13.830> of<01:02:13.950> the 01:02:14.030 --> 01:02:14.040 align:start position:0% okay hi I'm Debra I'm one of the 01:02:14.040 --> 01:02:17.600 align:start position:0% okay hi I'm Debra I'm one of the cofounders<01:02:14.370> of<01:02:14.930> TN<01:02:15.930> and<01:02:16.260> I'm<01:02:17.160> really<01:02:17.370> excited 01:02:17.600 --> 01:02:17.610 align:start position:0% cofounders of TN and I'm really excited 01:02:17.610 --> 01:02:19.070 align:start position:0% cofounders of TN and I'm really excited to<01:02:17.850> share<01:02:17.970> a<01:02:18.030> little<01:02:18.210> bit<01:02:18.300> about<01:02:18.420> how<01:02:18.750> it<01:02:18.870> works 01:02:19.070 --> 01:02:19.080 align:start position:0% to share a little bit about how it works 01:02:19.080 --> 01:02:21.680 align:start position:0% to share a little bit about how it works today<01:02:19.650> and<01:02:20.010> then<01:02:20.130> I'll<01:02:20.400> be<01:02:20.670> sharing<01:02:21.300> more 01:02:21.680 --> 01:02:21.690 align:start position:0% today and then I'll be sharing more 01:02:21.690 --> 01:02:24.050 align:start position:0% today and then I'll be sharing more about<01:02:21.900> our<01:02:22.170> experiences<01:02:23.160> working<01:02:23.760> on<01:02:23.970> the 01:02:24.050 --> 01:02:24.060 align:start position:0% about our experiences working on the 01:02:24.060 --> 01:02:26.240 align:start position:0% about our experiences working on the ground<01:02:24.180> in<01:02:24.360> my<01:02:24.570> community<01:02:25.530> setting<01:02:25.920> up<01:02:26.010> one<01:02:26.160> of 01:02:26.240 --> 01:02:26.250 align:start position:0% ground in my community setting up one of 01:02:26.250 --> 01:02:27.680 align:start position:0% ground in my community setting up one of these<01:02:26.340> decentralized<01:02:27.000> internet<01:02:27.330> service 01:02:27.680 --> 01:02:27.690 align:start position:0% these decentralized internet service 01:02:27.690 --> 01:02:33.100 align:start position:0% these decentralized internet service providers<01:02:28.200> on<01:02:28.500> Thursday<01:02:29.570> Wow 01:02:33.100 --> 01:02:33.110 align:start position:0% 01:02:33.110 --> 01:02:44.420 align:start position:0% so<01:02:34.280> Athena<01:02:35.280> is<01:02:41.030> so<01:02:42.030> Athena<01:02:42.480> is<01:02:42.870> a<01:02:43.430> software 01:02:44.420 --> 01:02:44.430 align:start position:0% so Athena is so Athena is a software 01:02:44.430 --> 01:02:47.240 align:start position:0% so Athena is so Athena is a software that<01:02:44.460> runs<01:02:45.030> on<01:02:45.510> readily<01:02:46.260> available<01:02:46.380> consumer 01:02:47.240 --> 01:02:47.250 align:start position:0% that runs on readily available consumer 01:02:47.250 --> 01:02:49.940 align:start position:0% that runs on readily available consumer routers<01:02:47.610> like<01:02:48.210> the<01:02:48.300> one<01:02:48.450> we<01:02:48.540> have<01:02:48.690> here<01:02:48.950> that 01:02:49.940 --> 01:02:49.950 align:start position:0% routers like the one we have here that 01:02:49.950 --> 01:02:52.970 align:start position:0% routers like the one we have here that allows<01:02:50.220> people<01:02:50.550> to<01:02:51.320> set<01:02:52.320> up<01:02:52.350> centralized 01:02:52.970 --> 01:02:52.980 align:start position:0% allows people to set up centralized 01:02:52.980 --> 01:02:54.470 align:start position:0% allows people to set up centralized Internet<01:02:53.370> service<01:02:53.700> providers<01:02:54.150> in<01:02:54.390> their 01:02:54.470 --> 01:02:54.480 align:start position:0% Internet service providers in their 01:02:54.480 --> 01:02:59.000 align:start position:0% Internet service providers in their community<01:02:56.060> because<01:02:57.060> the<01:02:57.630> routers<01:02:58.230> hate<01:02:58.800> each 01:02:59.000 --> 01:02:59.010 align:start position:0% community because the routers hate each 01:02:59.010 --> 01:03:01.810 align:start position:0% community because the routers hate each other<01:02:59.220> for<01:02:59.490> bandwidth<01:02:59.880> so<01:03:00.330> this<01:03:00.750> lets 01:03:01.810 --> 01:03:01.820 align:start position:0% other for bandwidth so this lets 01:03:01.820 --> 01:03:04.040 align:start position:0% other for bandwidth so this lets homeowners<01:03:02.820> and<01:03:02.970> business<01:03:03.240> owners<01:03:03.360> host<01:03:03.810> some 01:03:04.040 --> 01:03:04.050 align:start position:0% homeowners and business owners host some 01:03:04.050 --> 01:03:07.100 align:start position:0% homeowners and business owners host some of<01:03:04.080> this<01:03:04.260> long-range<01:03:05.300> Wi-Fi<01:03:06.300> hardware<01:03:06.780> and 01:03:07.100 --> 01:03:07.110 align:start position:0% of this long-range Wi-Fi hardware and 01:03:07.110 --> 01:03:09.740 align:start position:0% of this long-range Wi-Fi hardware and earn<01:03:07.230> money<01:03:07.500> automatically<01:03:08.250> for<01:03:08.490> doing<01:03:08.730> so<01:03:08.940> so 01:03:09.740 --> 01:03:09.750 align:start position:0% earn money automatically for doing so so 01:03:09.750 --> 01:03:14.090 align:start position:0% earn money automatically for doing so so that<01:03:09.960> instead<01:03:10.380> of<01:03:10.760> one<01:03:11.760> is<01:03:12.150> he<01:03:12.450> running<01:03:13.380> all<01:03:13.950> of 01:03:14.090 --> 01:03:14.100 align:start position:0% that instead of one is he running all of 01:03:14.100 --> 01:03:15.620 align:start position:0% that instead of one is he running all of the<01:03:14.190> infrastructure<01:03:14.640> and<01:03:14.910> owning<01:03:15.270> all<01:03:15.390> of<01:03:15.540> the 01:03:15.620 --> 01:03:15.630 align:start position:0% the infrastructure and owning all of the 01:03:15.630 --> 01:03:17.030 align:start position:0% the infrastructure and owning all of the different<01:03:15.900> pieces<01:03:16.080> of<01:03:16.230> the<01:03:16.410> network<01:03:16.770> and 01:03:17.030 --> 01:03:17.040 align:start position:0% different pieces of the network and 01:03:17.040 --> 01:03:18.950 align:start position:0% different pieces of the network and extracting<01:03:17.490> all<01:03:17.610> about<01:03:17.820> profit<01:03:18.270> many 01:03:18.950 --> 01:03:18.960 align:start position:0% extracting all about profit many 01:03:18.960 --> 01:03:21.290 align:start position:0% extracting all about profit many different<01:03:19.350> people<01:03:19.650> can<01:03:19.860> get<01:03:20.460> all<01:03:20.760> these<01:03:20.940> and 01:03:21.290 --> 01:03:21.300 align:start position:0% different people can get all these and 01:03:21.300 --> 01:03:24.650 align:start position:0% different people can get all these and and<01:03:21.900> earn<01:03:22.080> money<01:03:22.230> and<01:03:23.120> all<01:03:24.120> these<01:03:24.240> does<01:03:24.480> this 01:03:24.650 --> 01:03:24.660 align:start position:0% and earn money and all these does this 01:03:24.660 --> 01:03:26.110 align:start position:0% and earn money and all these does this by<01:03:24.900> using 01:03:26.110 --> 01:03:26.120 align:start position:0% by using 01:03:26.120 --> 01:03:28.720 align:start position:0% by using price<01:03:26.900> aware<01:03:27.380> version<01:03:27.920> of<01:03:28.100> the<01:03:28.190> Bible<01:03:28.580> in<01:03:28.640> this 01:03:28.720 --> 01:03:28.730 align:start position:0% price aware version of the Bible in this 01:03:28.730 --> 01:03:31.810 align:start position:0% price aware version of the Bible in this protocol<01:03:29.150> to<01:03:29.570> select<01:03:30.230> routes<01:03:30.520> so<01:03:31.520> what<01:03:31.700> this 01:03:31.810 --> 01:03:31.820 align:start position:0% protocol to select routes so what this 01:03:31.820 --> 01:03:35.380 align:start position:0% protocol to select routes so what this means<01:03:31.880> is<01:03:32.570> that<01:03:32.930> instead<01:03:33.560> of<01:03:33.940> only<01:03:34.940> selecting 01:03:35.380 --> 01:03:35.390 align:start position:0% means is that instead of only selecting 01:03:35.390 --> 01:03:37.390 align:start position:0% means is that instead of only selecting routes<01:03:35.600> by<01:03:35.840> the<01:03:35.900> best<01:03:36.110> around<01:03:36.380> trip<01:03:36.710> time<01:03:36.980> as 01:03:37.390 --> 01:03:37.400 align:start position:0% routes by the best around trip time as 01:03:37.400 --> 01:03:38.950 align:start position:0% routes by the best around trip time as we<01:03:37.580> would<01:03:37.730> see<01:03:37.880> in<01:03:37.940> the<01:03:37.970> local<01:03:38.330> match<01:03:38.480> protocol 01:03:38.950 --> 01:03:38.960 align:start position:0% we would see in the local match protocol 01:03:38.960 --> 01:03:41.710 align:start position:0% we would see in the local match protocol this<01:03:39.620> also<01:03:40.010> takes<01:03:40.310> the<01:03:40.640> price<01:03:41.240> into 01:03:41.710 --> 01:03:41.720 align:start position:0% this also takes the price into 01:03:41.720 --> 01:03:44.590 align:start position:0% this also takes the price into consideration<01:03:42.410> as<01:03:42.530> well<01:03:43.060> so<01:03:44.060> that<01:03:44.330> it's<01:03:44.450> been 01:03:44.590 --> 01:03:44.600 align:start position:0% consideration as well so that it's been 01:03:44.600 --> 01:03:46.330 align:start position:0% consideration as well so that it's been automatically<01:03:45.320> on<01:03:45.470> a<01:03:45.560> second-by-second 01:03:46.330 --> 01:03:46.340 align:start position:0% automatically on a second-by-second 01:03:46.340 --> 01:03:50.290 align:start position:0% automatically on a second-by-second basis<01:03:46.730> select<01:03:47.540> the<01:03:48.700> level<01:03:49.700> in<01:03:49.790> the<01:03:49.910> best<01:03:50.090> route 01:03:50.290 --> 01:03:50.300 align:start position:0% basis select the level in the best route 01:03:50.300 --> 01:03:52.210 align:start position:0% basis select the level in the best route but<01:03:50.810> the<01:03:50.900> least<01:03:51.110> expensive<01:03:51.590> sort<01:03:51.860> of<01:03:51.920> adding 01:03:52.210 --> 01:03:52.220 align:start position:0% but the least expensive sort of adding 01:03:52.220 --> 01:03:56.690 align:start position:0% but the least expensive sort of adding in<01:03:52.310> that<01:03:52.400> audition<01:03:53.740> and 01:03:56.690 --> 01:03:56.700 align:start position:0% in that audition and 01:03:56.700 --> 01:03:59.660 align:start position:0% in that audition and it's<01:03:57.540> also<01:03:57.780> like<01:03:58.260> a<01:03:58.290> prepaid<01:03:58.770> system<01:03:59.220> right<01:03:59.430> so 01:03:59.660 --> 01:03:59.670 align:start position:0% it's also like a prepaid system right so 01:03:59.670 --> 01:04:01.339 align:start position:0% it's also like a prepaid system right so essentially<01:04:00.240> you<01:04:00.329> load<01:04:00.569> your<01:04:00.599> router<01:04:00.900> roll<01:04:01.140> it 01:04:01.339 --> 01:04:01.349 align:start position:0% essentially you load your router roll it 01:04:01.349 --> 01:04:04.700 align:start position:0% essentially you load your router roll it up<01:04:01.470> with<01:04:01.770> aetherium<01:04:02.490> or<01:04:03.119> X<01:04:03.299> I<01:04:03.540> or<01:04:04.319> recently 01:04:04.700 --> 01:04:04.710 align:start position:0% up with aetherium or X I or recently 01:04:04.710 --> 01:04:08.210 align:start position:0% up with aetherium or X I or recently we've<01:04:04.980> added<01:04:05.190> in<01:04:05.460> a<01:04:05.609> bridge<01:04:05.970> so<01:04:06.750> that<01:04:07.220> it's 01:04:08.210 --> 01:04:08.220 align:start position:0% we've added in a bridge so that it's 01:04:08.220 --> 01:04:09.710 align:start position:0% we've added in a bridge so that it's easy<01:04:08.490> to<01:04:08.730> get<01:04:08.849> a<01:04:08.880> theorem<01:04:09.270> that<01:04:09.299> you<01:04:09.420> can<01:04:09.599> get 01:04:09.710 --> 01:04:09.720 align:start position:0% easy to get a theorem that you can get 01:04:09.720 --> 01:04:11.930 align:start position:0% easy to get a theorem that you can get from<01:04:09.869> point<01:04:09.900> A<01:04:10.290> B's<01:04:10.470> you<01:04:11.430> can<01:04:11.579> send<01:04:11.790> out<01:04:11.880> to 01:04:11.930 --> 01:04:11.940 align:start position:0% from point A B's you can send out to 01:04:11.940 --> 01:04:13.910 align:start position:0% from point A B's you can send out to your<01:04:12.119> honor<01:04:12.270> wallet<01:04:12.780> and<01:04:13.260> that<01:04:13.619> it<01:04:13.829> will 01:04:13.910 --> 01:04:13.920 align:start position:0% your honor wallet and that it will 01:04:13.920 --> 01:04:16.849 align:start position:0% your honor wallet and that it will bridging<01:04:14.460> the<01:04:14.549> music<01:04:15.000> unit<01:04:15.450> spot<01:04:15.690> to<01:04:15.990> a<01:04:16.260> design 01:04:16.849 --> 01:04:16.859 align:start position:0% bridging the music unit spot to a design 01:04:16.859 --> 01:04:18.829 align:start position:0% bridging the music unit spot to a design you'd<01:04:17.010> be<01:04:17.099> a<01:04:17.130> single<01:04:17.490> currency<01:04:17.790> to<01:04:18.599> know<01:04:18.720> how 01:04:18.829 --> 01:04:18.839 align:start position:0% you'd be a single currency to know how 01:04:18.839 --> 01:04:20.660 align:start position:0% you'd be a single currency to know how those<01:04:19.020> price<01:04:19.230> fluctuations<01:04:19.890> that<01:04:20.010> aetherium 01:04:20.660 --> 01:04:20.670 align:start position:0% those price fluctuations that aetherium 01:04:20.670 --> 01:04:22.700 align:start position:0% those price fluctuations that aetherium has<01:04:20.849> for<01:04:21.150> and<01:04:21.750> users<01:04:22.109> just<01:04:22.260> trying<01:04:22.500> to<01:04:22.559> pay<01:04:22.680> for 01:04:22.700 --> 01:04:22.710 align:start position:0% has for and users just trying to pay for 01:04:22.710 --> 01:04:28.390 align:start position:0% has for and users just trying to pay for Internet 01:04:28.390 --> 01:04:28.400 align:start position:0% 01:04:28.400 --> 01:04:31.140 align:start position:0% [Music] 01:04:31.140 --> 01:04:31.150 align:start position:0% [Music] 01:04:31.150 --> 01:04:33.390 align:start position:0% [Music] okay<01:04:31.660> so<01:04:31.720> what<01:04:32.109> this<01:04:32.289> what<01:04:32.680> this<01:04:32.859> does<01:04:33.099> and<01:04:33.309> we 01:04:33.390 --> 01:04:33.400 align:start position:0% okay so what this what this does and we 01:04:33.400 --> 01:04:35.789 align:start position:0% okay so what this what this does and we have<01:04:33.839> lots<01:04:34.839> of<01:04:34.960> different<01:04:35.079> people<01:04:35.410> learning 01:04:35.789 --> 01:04:35.799 align:start position:0% have lots of different people learning 01:04:35.799 --> 01:04:38.579 align:start position:0% have lots of different people learning infrastructure<01:04:36.809> is<01:04:37.809> that<01:04:38.079> a<01:04:38.109> case<01:04:38.410> on 01:04:38.579 --> 01:04:38.589 align:start position:0% infrastructure is that a case on 01:04:38.589 --> 01:04:40.620 align:start position:0% infrastructure is that a case on automatically<01:04:39.160> competitive<01:04:39.910> bandwidth 01:04:40.620 --> 01:04:40.630 align:start position:0% automatically competitive bandwidth 01:04:40.630 --> 01:04:42.509 align:start position:0% automatically competitive bandwidth marketplace<01:04:41.140> so<01:04:41.559> this<01:04:42.099> is<01:04:42.249> sort<01:04:42.369> of<01:04:42.430> the 01:04:42.509 --> 01:04:42.519 align:start position:0% marketplace so this is sort of the 01:04:42.519 --> 01:04:43.980 align:start position:0% marketplace so this is sort of the picture<01:04:42.789> what<01:04:42.940> we<01:04:43.059> have<01:04:43.210> with<01:04:43.390> the<01:04:43.539> the 01:04:43.980 --> 01:04:43.990 align:start position:0% picture what we have with the the 01:04:43.990 --> 01:04:45.739 align:start position:0% picture what we have with the the internet<01:04:44.319> currently<01:04:44.769> right<01:04:45.009> you<01:04:45.220> you<01:04:45.430> get<01:04:45.609> a 01:04:45.739 --> 01:04:45.749 align:start position:0% internet currently right you you get a 01:04:45.749 --> 01:04:48.359 align:start position:0% internet currently right you you get a an<01:04:46.749> Internet<01:04:47.200> service<01:04:47.349> monthly<01:04:47.769> subscription 01:04:48.359 --> 01:04:48.369 align:start position:0% an Internet service monthly subscription 01:04:48.369 --> 01:04:50.430 align:start position:0% an Internet service monthly subscription and<01:04:48.640> they<01:04:49.240> bring<01:04:49.420> in<01:04:49.509> a<01:04:49.569> specific<01:04:49.749> hardware 01:04:50.430 --> 01:04:50.440 align:start position:0% and they bring in a specific hardware 01:04:50.440 --> 01:04:54.620 align:start position:0% and they bring in a specific hardware and<01:04:50.859> it's<01:04:50.980> very<01:04:51.130> siloed<01:04:52.319> but<01:04:53.319> with<01:04:53.920> Althea 01:04:54.620 --> 01:04:54.630 align:start position:0% and it's very siloed but with Althea 01:04:54.630 --> 01:05:01.349 align:start position:0% and it's very siloed but with Althea what<01:04:55.630> if<01:04:55.809> you<01:04:56.740> can<01:04:57.119> automatically<01:04:58.650> compete<01:05:00.359> if 01:05:01.349 --> 01:05:01.359 align:start position:0% what if you can automatically compete if 01:05:01.359 --> 01:05:03.210 align:start position:0% what if you can automatically compete if your<01:05:01.539> service<01:05:01.809> provider<01:05:02.109> on<01:05:02.529> like<01:05:02.799> a<01:05:02.829> second 01:05:03.210 --> 01:05:03.220 align:start position:0% your service provider on like a second 01:05:03.220 --> 01:05:05.430 align:start position:0% your service provider on like a second my<01:05:03.279> second<01:05:03.670> basis<01:05:04.150> if<01:05:04.660> your<01:05:04.869> router<01:05:05.019> was<01:05:05.319> too 01:05:05.430 --> 01:05:05.440 align:start position:0% my second basis if your router was too 01:05:05.440 --> 01:05:08.220 align:start position:0% my second basis if your router was too may<01:05:05.559> not<01:05:05.740> work<01:05:05.920> for<01:05:05.950> you<01:05:06.249> so<01:05:07.210> as<01:05:07.900> we<01:05:08.079> build 01:05:08.220 --> 01:05:08.230 align:start position:0% may not work for you so as we build 01:05:08.230 --> 01:05:09.630 align:start position:0% may not work for you so as we build these<01:05:08.410> networks<01:05:08.589> and<01:05:09.009> different<01:05:09.099> people<01:05:09.400> on 01:05:09.630 --> 01:05:09.640 align:start position:0% these networks and different people on 01:05:09.640 --> 01:05:14.099 align:start position:0% these networks and different people on hardware<01:05:10.210> the<01:05:11.140> the<01:05:11.499> links<01:05:12.180> will<01:05:13.180> will<01:05:13.749> select 01:05:14.099 --> 01:05:14.109 align:start position:0% hardware the the links will will select 01:05:14.109 --> 01:05:19.920 align:start position:0% hardware the the links will will select the<01:05:14.200> path<01:05:14.380> Ralph 01:05:19.920 --> 01:05:19.930 align:start position:0% 01:05:19.930 --> 01:05:23.339 align:start position:0% so<01:05:20.910> this<01:05:21.910> is<01:05:22.089> a<01:05:22.119> this<01:05:22.390> is<01:05:22.450> a<01:05:22.569> map<01:05:22.779> of<01:05:22.809> one<01:05:23.109> of<01:05:23.230> our 01:05:23.339 --> 01:05:23.349 align:start position:0% so this is a this is a map of one of our 01:05:23.349 --> 01:05:26.460 align:start position:0% so this is a this is a map of one of our this<01:05:24.099> thing<01:05:24.160> that<01:05:24.460> works<01:05:24.700> in<01:05:25.140> Oregon<01:05:26.140> this<01:05:26.319> is 01:05:26.460 --> 01:05:26.470 align:start position:0% this thing that works in Oregon this is 01:05:26.470 --> 01:05:27.690 align:start position:0% this thing that works in Oregon this is actually<01:05:26.799> working<01:05:26.950> promise 01:05:27.690 --> 01:05:27.700 align:start position:0% actually working promise 01:05:27.700 --> 01:05:29.819 align:start position:0% actually working promise we're<01:05:27.970> all<01:05:28.029> community<01:05:28.630> here<01:05:28.839> and<01:05:29.319> you<01:05:29.500> can<01:05:29.650> see 01:05:29.819 --> 01:05:29.829 align:start position:0% we're all community here and you can see 01:05:29.829 --> 01:05:31.470 align:start position:0% we're all community here and you can see this<01:05:29.980> sort<01:05:30.160> of<01:05:30.279> distributed<01:05:30.789> nature<01:05:31.000> that<01:05:31.329> we 01:05:31.470 --> 01:05:31.480 align:start position:0% this sort of distributed nature that we 01:05:31.480 --> 01:05:33.329 align:start position:0% this sort of distributed nature that we have<01:05:32.079> here<01:05:32.500> each<01:05:32.650> of<01:05:32.829> these<01:05:32.920> different<01:05:33.130> things 01:05:33.329 --> 01:05:33.339 align:start position:0% have here each of these different things 01:05:33.339 --> 01:05:36.029 align:start position:0% have here each of these different things are<01:05:33.670> what<01:05:33.880> we<01:05:34.000> call<01:05:34.210> them<01:05:34.359> relay<01:05:34.770> and<01:05:35.770> so 01:05:36.029 --> 01:05:36.039 align:start position:0% are what we call them relay and so 01:05:36.039 --> 01:05:38.510 align:start position:0% are what we call them relay and so that's<01:05:36.220> at<01:05:36.369> home<01:05:36.520> or<01:05:36.880> a<01:05:36.910> business<01:05:37.299> person<01:05:37.809> or 01:05:38.510 --> 01:05:38.520 align:start position:0% that's at home or a business person or 01:05:38.520 --> 01:05:42.329 align:start position:0% that's at home or a business person or you<01:05:39.520> know<01:05:39.640> a<01:05:39.970> farm<01:05:40.900> in<01:05:41.170> this<01:05:41.289> case<01:05:41.500> that<01:05:42.220> is 01:05:42.329 --> 01:05:42.339 align:start position:0% you know a farm in this case that is 01:05:42.339 --> 01:05:44.279 align:start position:0% you know a farm in this case that is hosting<01:05:42.670> some<01:05:42.849> hardware<01:05:43.180> and<01:05:43.450> getting 01:05:44.279 --> 01:05:44.289 align:start position:0% hosting some hardware and getting 01:05:44.289 --> 01:05:45.870 align:start position:0% hosting some hardware and getting painted<01:05:44.589> on<01:05:44.680> there<01:05:44.859> but<01:05:45.099> further<01:05:45.339> further 01:05:45.870 --> 01:05:45.880 align:start position:0% painted on there but further further 01:05:45.880 --> 01:05:48.720 align:start position:0% painted on there but further further routers<01:05:46.240> do<01:05:46.480> that<01:05:46.829> and<01:05:47.829> so<01:05:48.250> you<01:05:48.309> can<01:05:48.460> see<01:05:48.609> we 01:05:48.720 --> 01:05:48.730 align:start position:0% routers do that and so you can see we 01:05:48.730 --> 01:05:51.539 align:start position:0% routers do that and so you can see we even<01:05:48.880> have<01:05:49.059> some<01:05:49.210> really<01:05:49.390> dynamic<01:05:49.660> leaks<01:05:50.549> that 01:05:51.539 --> 01:05:51.549 align:start position:0% even have some really dynamic leaks that 01:05:51.549 --> 01:05:53.730 align:start position:0% even have some really dynamic leaks that this<01:05:52.150> is<01:05:52.270> that<01:05:52.390> way<01:05:52.569> in<01:05:52.630> the<01:05:52.779> valley<01:05:52.990> there<01:05:53.349> and 01:05:53.730 --> 01:05:53.740 align:start position:0% this is that way in the valley there and 01:05:53.740 --> 01:05:56.670 align:start position:0% this is that way in the valley there and then<01:05:54.240> routes<01:05:55.240> to<01:05:55.539> a<01:05:55.569> person<01:05:56.170> up<01:05:56.260> on<01:05:56.380> the<01:05:56.470> hill 01:05:56.670 --> 01:05:56.680 align:start position:0% then routes to a person up on the hill 01:05:56.680 --> 01:05:59.390 align:start position:0% then routes to a person up on the hill and<01:05:57.010> then<01:05:57.910> from<01:05:58.180> that<01:05:58.210> person<01:05:58.660> on<01:05:58.750> the<01:05:58.809> hill 01:05:59.390 --> 01:05:59.400 align:start position:0% and then from that person on the hill 01:05:59.400 --> 01:06:01.980 align:start position:0% and then from that person on the hill all<01:06:00.400> the<01:06:00.460> way<01:06:00.670> out<01:06:00.819> to<01:06:00.940> the<01:06:01.089> river<01:06:01.510> and<01:06:01.750> the 01:06:01.980 --> 01:06:01.990 align:start position:0% all the way out to the river and the 01:06:01.990 --> 01:06:03.299 align:start position:0% all the way out to the river and the reason<01:06:02.260> why<01:06:02.349> we<01:06:02.500> did<01:06:02.650> this<01:06:02.770> instead<01:06:03.010> of<01:06:03.130> going 01:06:03.299 --> 01:06:03.309 align:start position:0% reason why we did this instead of going 01:06:03.309 --> 01:06:04.380 align:start position:0% reason why we did this instead of going straight<01:06:03.460> is<01:06:03.849> because<01:06:04.119> there's<01:06:04.240> actually 01:06:04.380 --> 01:06:04.390 align:start position:0% straight is because there's actually 01:06:04.390 --> 01:06:06.089 align:start position:0% straight is because there's actually geographical<01:06:05.170> challenges<01:06:05.289> to<01:06:05.740> that<01:06:05.770> this 01:06:06.089 --> 01:06:06.099 align:start position:0% geographical challenges to that this 01:06:06.099 --> 01:06:09.059 align:start position:0% geographical challenges to that this sort<01:06:06.309> of<01:06:06.630> interoperable<01:06:07.630> kind<01:06:08.170> of<01:06:08.260> agile 01:06:09.059 --> 01:06:09.069 align:start position:0% sort of interoperable kind of agile 01:06:09.069 --> 01:06:11.789 align:start position:0% sort of interoperable kind of agile configuration<01:06:09.789> lets<01:06:09.970> us<01:06:10.089> do<01:06:10.270> as<01:06:10.510> well<01:06:10.799> and 01:06:11.789 --> 01:06:11.799 align:start position:0% configuration lets us do as well and 01:06:11.799 --> 01:06:13.200 align:start position:0% configuration lets us do as well and then<01:06:11.950> we'll<01:06:12.099> be<01:06:12.190> adding<01:06:12.339> in<01:06:12.579> the<01:06:12.670> worth<01:06:12.849> more 01:06:13.200 --> 01:06:13.210 align:start position:0% then we'll be adding in the worth more 01:06:13.210 --> 01:06:15.210 align:start position:0% then we'll be adding in the worth more redundancy<01:06:13.960> and<01:06:14.170> links<01:06:14.470> as<01:06:14.619> the<01:06:14.710> network<01:06:14.980> sort 01:06:15.210 --> 01:06:15.220 align:start position:0% redundancy and links as the network sort 01:06:15.220 --> 01:06:18.260 align:start position:0% redundancy and links as the network sort of<01:06:15.279> gross 01:06:18.260 --> 01:06:18.270 align:start position:0% 01:06:18.270 --> 01:06:21.059 align:start position:0% another<01:06:19.270> thing<01:06:19.510> about<01:06:19.539> Alethea<01:06:20.020> is<01:06:20.109> that<01:06:20.529> all 01:06:21.059 --> 01:06:21.069 align:start position:0% another thing about Alethea is that all 01:06:21.069 --> 01:06:22.799 align:start position:0% another thing about Alethea is that all of<01:06:21.250> the<01:06:21.490> all<01:06:22.059> of<01:06:22.089> these<01:06:22.329> interconnections 01:06:22.799 --> 01:06:22.809 align:start position:0% of the all of these interconnections 01:06:22.809 --> 01:06:24.870 align:start position:0% of the all of these interconnections between<01:06:23.020> and<01:06:23.410> homeowners<01:06:23.859> are<01:06:24.039> subject<01:06:24.609> using 01:06:24.870 --> 01:06:24.880 align:start position:0% between and homeowners are subject using 01:06:24.880 --> 01:06:28.559 align:start position:0% between and homeowners are subject using wire<01:06:25.089> art<01:06:25.589> and<01:06:26.589> that<01:06:26.859> is<01:06:27.279> then<01:06:27.849> decrypted<01:06:28.390> at 01:06:28.559 --> 01:06:28.569 align:start position:0% wire art and that is then decrypted at 01:06:28.569 --> 01:06:31.170 align:start position:0% wire art and that is then decrypted at the<01:06:28.779> exit<01:06:29.680> what<01:06:30.130> we<01:06:30.250> call<01:06:30.430> an<01:06:30.520> exit<01:06:30.849> node<01:06:30.880> which 01:06:31.170 --> 01:06:31.180 align:start position:0% the exit what we call an exit node which 01:06:31.180 --> 01:06:33.890 align:start position:0% the exit what we call an exit node which is<01:06:31.329> just<01:06:31.510> like<01:06:31.930> a<01:06:31.960> VPN<01:06:32.410> server 01:06:33.890 --> 01:06:33.900 align:start position:0% is just like a VPN server 01:06:33.900 --> 01:06:38.380 align:start position:0% is just like a VPN server Center<01:06:34.589> and<01:06:34.920> this<01:06:35.309> also<01:06:35.609> allows<01:06:36.150> for<01:06:36.720> us<01:06:37.559> to 01:06:38.380 --> 01:06:38.390 align:start position:0% Center and this also allows for us to 01:06:38.390 --> 01:06:41.510 align:start position:0% Center and this also allows for us to verify<01:06:39.390> that<01:06:39.809> the<01:06:40.230> that<01:06:40.680> the<01:06:40.799> cost<01:06:41.069> that<01:06:41.400> each 01:06:41.510 --> 01:06:41.520 align:start position:0% verify that the that the cost that each 01:06:41.520 --> 01:06:43.819 align:start position:0% verify that the that the cost that each link<01:06:41.730> is<01:06:42.000> reporting<01:06:42.779> and<01:06:43.109> the<01:06:43.289> round-trip 01:06:43.819 --> 01:06:43.829 align:start position:0% link is reporting and the round-trip 01:06:43.829 --> 01:06:46.940 align:start position:0% link is reporting and the round-trip time<01:06:44.039> is<01:06:44.960> verified<01:06:45.960> instead<01:06:46.710> of<01:06:46.799> them<01:06:46.920> just 01:06:46.940 --> 01:06:46.950 align:start position:0% time is verified instead of them just 01:06:46.950 --> 01:06:50.180 align:start position:0% time is verified instead of them just sort<01:06:47.279> of<01:06:47.809> potentially<01:06:49.099> misrepresenting<01:06:50.099> a 01:06:50.180 --> 01:06:50.190 align:start position:0% sort of potentially misrepresenting a 01:06:50.190 --> 01:06:54.210 align:start position:0% sort of potentially misrepresenting a fact 01:06:54.210 --> 01:06:54.220 align:start position:0% 01:06:54.220 --> 01:06:55.360 align:start position:0% [Music] 01:06:55.360 --> 01:06:55.370 align:start position:0% [Music] 01:06:55.370 --> 01:06:57.580 align:start position:0% [Music] so<01:06:55.940> here's<01:06:56.240> one<01:06:56.360> of<01:06:56.390> our<01:06:56.480> relays<01:06:56.840> so<01:06:57.200> this<01:06:57.410> is 01:06:57.580 --> 01:06:57.590 align:start position:0% so here's one of our relays so this is 01:06:57.590 --> 01:07:00.850 align:start position:0% so here's one of our relays so this is actually<01:06:58.010> that<01:06:58.130> farm<01:06:58.460> on<01:06:58.730> the<01:06:59.530> in<01:07:00.530> the<01:07:00.680> valley 01:07:00.850 --> 01:07:00.860 align:start position:0% actually that farm on the in the valley 01:07:00.860 --> 01:07:02.290 align:start position:0% actually that farm on the in the valley there<01:07:01.220> and<01:07:01.370> then<01:07:01.460> that<01:07:01.610> correct<01:07:01.970> meaning 01:07:02.290 --> 01:07:02.300 align:start position:0% there and then that correct meaning 01:07:02.300 --> 01:07:04.210 align:start position:0% there and then that correct meaning green<01:07:02.870> connection<01:07:03.170> so<01:07:03.590> what<01:07:03.740> we<01:07:03.830> can<01:07:03.950> see<01:07:04.100> is 01:07:04.210 --> 01:07:04.220 align:start position:0% green connection so what we can see is 01:07:04.220 --> 01:07:06.790 align:start position:0% green connection so what we can see is be<01:07:04.400> havin<01:07:04.670> a<01:07:04.730> ton<01:07:04.970> of<01:07:05.000> coming<01:07:05.330> into<01:07:05.480> the<01:07:05.800> that 01:07:06.790 --> 01:07:06.800 align:start position:0% be havin a ton of coming into the that 01:07:06.800 --> 01:07:09.760 align:start position:0% be havin a ton of coming into the that it's<01:07:06.950> receiving<01:07:07.280> signal<01:07:07.730> from<01:07:08.420> a<01:07:08.780> and 01:07:09.760 --> 01:07:09.770 align:start position:0% it's receiving signal from a and 01:07:09.770 --> 01:07:11.290 align:start position:0% it's receiving signal from a and actually<01:07:09.890> this<01:07:10.130> is<01:07:10.280> from<01:07:10.430> like<01:07:10.730> a<01:07:10.760> wholesale 01:07:11.290 --> 01:07:11.300 align:start position:0% actually this is from like a wholesale 01:07:11.300 --> 01:07:14.530 align:start position:0% actually this is from like a wholesale fiber<01:07:11.600> not<01:07:12.110> call<01:07:12.350> and<01:07:12.860> then<01:07:13.070> she's<01:07:13.340> hitting<01:07:14.330> an 01:07:14.530 --> 01:07:14.540 align:start position:0% fiber not call and then she's hitting an 01:07:14.540 --> 01:07:15.940 align:start position:0% fiber not call and then she's hitting an incoming<01:07:14.960> connection<01:07:15.410> and<01:07:15.560> then<01:07:15.650> the<01:07:15.740> two 01:07:15.940 --> 01:07:15.950 align:start position:0% incoming connection and then the two 01:07:15.950 --> 01:07:18.400 align:start position:0% incoming connection and then the two smaller<01:07:16.340> antennas<01:07:17.060> are<01:07:17.240> connecting<01:07:18.140> up<01:07:18.260> her 01:07:18.400 --> 01:07:18.410 align:start position:0% smaller antennas are connecting up her 01:07:18.410 --> 01:07:23.590 align:start position:0% smaller antennas are connecting up her nearby<01:07:18.770> neighbors<01:07:19.160> and<01:07:20.680> those<01:07:21.680> three<01:07:22.600> third 01:07:23.590 --> 01:07:23.600 align:start position:0% nearby neighbors and those three third 01:07:23.600 --> 01:07:25.180 align:start position:0% nearby neighbors and those three third net<01:07:23.720> cables<01:07:24.110> are<01:07:24.230> then<01:07:24.410> routed<01:07:24.560> to<01:07:24.920> her 01:07:25.180 --> 01:07:25.190 align:start position:0% net cables are then routed to her 01:07:25.190 --> 01:07:28.180 align:start position:0% net cables are then routed to her consumer<01:07:26.060> router<01:07:26.510> in<01:07:26.780> her<01:07:26.870> home<01:07:27.170> which<01:07:27.980> does 01:07:28.180 --> 01:07:28.190 align:start position:0% consumer router in her home which does 01:07:28.190 --> 01:07:30.910 align:start position:0% consumer router in her home which does all<01:07:28.370> of<01:07:28.400> that<01:07:28.520> filling<01:07:29.440> automatic<01:07:30.440> agency 01:07:30.910 --> 01:07:30.920 align:start position:0% all of that filling automatic agency 01:07:30.920 --> 01:07:32.680 align:start position:0% all of that filling automatic agency this<01:07:31.040> is<01:07:31.100> her<01:07:31.340> either<01:07:31.520> scan<01:07:31.880> of<01:07:32.060> money<01:07:32.240> put<01:07:32.480> in 01:07:32.680 --> 01:07:32.690 align:start position:0% this is her either scan of money put in 01:07:32.690 --> 01:07:34.510 align:start position:0% this is her either scan of money put in and<01:07:32.840> out<01:07:32.930> and<01:07:33.110> suddenly<01:07:33.440> they're<01:07:34.160> in<01:07:34.430> the 01:07:34.510 --> 01:07:34.520 align:start position:0% and out and suddenly they're in the 01:07:34.520 --> 01:07:38.200 align:start position:0% and out and suddenly they're in the Miriam<01:07:34.880> and<01:07:36.400> it<01:07:37.400> also<01:07:37.550> handles<01:07:37.820> all<01:07:38.060> their 01:07:38.200 --> 01:07:38.210 align:start position:0% Miriam and it also handles all their 01:07:38.210 --> 01:07:39.850 align:start position:0% Miriam and it also handles all their routing<01:07:38.540> and<01:07:38.720> then<01:07:38.900> it<01:07:39.050> provides<01:07:39.200> for<01:07:39.620> her 01:07:39.850 --> 01:07:39.860 align:start position:0% routing and then it provides for her 01:07:39.860 --> 01:07:44.440 align:start position:0% routing and then it provides for her home<01:07:40.100> her<01:07:40.640> home<01:07:40.850> Wi-Fi<01:07:41.240> so<01:07:41.570> for<01:07:41.780> her<01:07:41.990> she<01:07:43.450> she 01:07:44.440 --> 01:07:44.450 align:start position:0% home her home Wi-Fi so for her she she 01:07:44.450 --> 01:07:46.150 align:start position:0% home her home Wi-Fi so for her she she just<01:07:44.480> gets<01:07:44.780> it<01:07:44.900> or<01:07:45.080> not<01:07:45.200> and<01:07:45.500> actually<01:07:45.770> gets 01:07:46.150 --> 01:07:46.160 align:start position:0% just gets it or not and actually gets 01:07:46.160 --> 01:07:49.120 align:start position:0% just gets it or not and actually gets extra<01:07:46.790> money<01:07:46.970> that<01:07:47.060> she<01:07:47.360> Nina<01:07:47.590> that<01:07:48.590> about<01:07:49.100> a 01:07:49.120 --> 01:07:49.130 align:start position:0% extra money that she Nina that about a 01:07:49.130 --> 01:07:50.680 align:start position:0% extra money that she Nina that about a hundred<01:07:49.460> dollars<01:07:49.580> every<01:07:49.940> couple<01:07:50.330> of<01:07:50.450> months 01:07:50.680 --> 01:07:50.690 align:start position:0% hundred dollars every couple of months 01:07:50.690 --> 01:07:52.300 align:start position:0% hundred dollars every couple of months from<01:07:50.810> about<01:07:51.110> six<01:07:51.350> connects<01:07:51.710> attic<01:07:51.920> science 01:07:52.300 --> 01:07:52.310 align:start position:0% from about six connects attic science 01:07:52.310 --> 01:07:55.030 align:start position:0% from about six connects attic science that<01:07:52.940> she<01:07:53.270> should<01:07:53.840> use<01:07:54.110> as<01:07:54.260> point<01:07:54.470> basis<01:07:54.860> and 01:07:55.030 --> 01:07:55.040 align:start position:0% that she should use as point basis and 01:07:55.040 --> 01:07:57.190 align:start position:0% that she should use as point basis and extinguish<01:07:55.490> not<01:07:55.640> to<01:07:55.790> extract<01:07:56.180> that<01:07:56.330> to<01:07:56.900> be<01:07:57.080> on 01:07:57.190 --> 01:07:57.200 align:start position:0% extinguish not to extract that to be on 01:07:57.200 --> 01:07:59.940 align:start position:0% extinguish not to extract that to be on instead<01:07:58.070> of<01:07:58.190> the<01:07:58.640> other<01:07:58.730> way<01:07:58.910> around 01:07:59.940 --> 01:07:59.950 align:start position:0% instead of the other way around 01:07:59.950 --> 01:08:02.820 align:start position:0% instead of the other way around just<01:08:00.550> pretty<01:08:00.700> ball<01:08:00.910> and<01:08:01.780> then<01:08:01.960> she<01:08:02.170> also<01:08:02.410> we 01:08:02.820 --> 01:08:02.830 align:start position:0% just pretty ball and then she also we 01:08:02.830 --> 01:08:04.170 align:start position:0% just pretty ball and then she also we have<01:08:02.950> this<01:08:03.040> sort<01:08:03.160> of<01:08:03.250> bio<01:08:03.400> oil<01:08:03.520> drill<01:08:03.880> so 01:08:04.170 --> 01:08:04.180 align:start position:0% have this sort of bio oil drill so 01:08:04.180 --> 01:08:05.370 align:start position:0% have this sort of bio oil drill so she'll<01:08:04.420> go<01:08:04.540> and<01:08:04.690> talk<01:08:04.810> to<01:08:04.930> our<01:08:04.960> neighbors<01:08:05.350> and 01:08:05.370 --> 01:08:05.380 align:start position:0% she'll go and talk to our neighbors and 01:08:05.380 --> 01:08:07.560 align:start position:0% she'll go and talk to our neighbors and try<01:08:05.680> to<01:08:05.740> get<01:08:05.890> more<01:08:06.010> people<01:08:06.130> connected<01:08:06.670> we 01:08:07.560 --> 01:08:07.570 align:start position:0% try to get more people connected we 01:08:07.570 --> 01:08:09.750 align:start position:0% try to get more people connected we should<01:08:07.750> have<01:08:07.900> one<01:08:08.080> relay<01:08:08.410> that<01:08:08.620> will<01:08:09.490> take<01:08:09.730> a 01:08:09.750 --> 01:08:09.760 align:start position:0% should have one relay that will take a 01:08:09.760 --> 01:08:11.580 align:start position:0% should have one relay that will take a bottle<01:08:09.970> align<01:08:10.240> those<01:08:10.540> neighbors<01:08:10.900> and<01:08:11.230> see<01:08:11.530> if 01:08:11.580 --> 01:08:11.590 align:start position:0% bottle align those neighbors and see if 01:08:11.590 --> 01:08:14.550 align:start position:0% bottle align those neighbors and see if we<01:08:11.710> can<01:08:12.480> get<01:08:13.480> the<01:08:13.720> kids<01:08:13.900> and<01:08:14.020> connected<01:08:14.410> to<01:08:14.470> the 01:08:14.550 --> 01:08:14.560 align:start position:0% we can get the kids and connected to the 01:08:14.560 --> 01:08:16.470 align:start position:0% we can get the kids and connected to the internet<01:08:14.920> so<01:08:15.100> you<01:08:15.190> can<01:08:15.370> see<01:08:15.490> it<01:08:15.610> as<01:08:15.760> I<01:08:16.030> sort<01:08:16.420> of 01:08:16.470 --> 01:08:16.480 align:start position:0% internet so you can see it as I sort of 01:08:16.480 --> 01:08:19.260 align:start position:0% internet so you can see it as I sort of like<01:08:16.660> incentive<01:08:17.200> for<01:08:17.650> for<01:08:18.400> viral<01:08:18.850> growth<01:08:18.970> as 01:08:19.260 --> 01:08:19.270 align:start position:0% like incentive for for viral growth as 01:08:19.270 --> 01:08:21.630 align:start position:0% like incentive for for viral growth as well<01:08:19.530> and<01:08:20.530> there's<01:08:20.710> always<01:08:20.890> that<01:08:21.100> incentive 01:08:21.630 --> 01:08:21.640 align:start position:0% well and there's always that incentive 01:08:21.640 --> 01:08:24.030 align:start position:0% well and there's always that incentive because<01:08:22.150> it<01:08:22.300> is<01:08:22.420> sort<01:08:22.570> of<01:08:22.630> meter<01:08:22.900> that<01:08:23.500> we<01:08:23.740> want 01:08:24.030 --> 01:08:24.040 align:start position:0% because it is sort of meter that we want 01:08:24.040 --> 01:08:27.090 align:start position:0% because it is sort of meter that we want to<01:08:24.220> add<01:08:24.400> in<01:08:24.700> more<01:08:25.260> more<01:08:26.260> bandwidth<01:08:26.740> better 01:08:27.090 --> 01:08:27.100 align:start position:0% to add in more more bandwidth better 01:08:27.100 --> 01:08:31.180 align:start position:0% to add in more more bandwidth better service<01:08:27.460> for<01:08:27.490> folks 01:08:31.180 --> 01:08:31.190 align:start position:0% 01:08:31.190 --> 01:08:34.120 align:start position:0% so<01:08:31.670> we<01:08:31.850> do<01:08:32.000> realize<01:08:32.390> though<01:08:32.660> that<01:08:32.930> even<01:08:33.530> as 01:08:34.120 --> 01:08:34.130 align:start position:0% so we do realize though that even as 01:08:34.130 --> 01:08:36.280 align:start position:0% so we do realize though that even as permissionless<01:08:34.790> and<01:08:35.150> us<01:08:35.390> automatic<01:08:35.990> as<01:08:36.140> we 01:08:36.280 --> 01:08:36.290 align:start position:0% permissionless and us automatic as we 01:08:36.290 --> 01:08:37.720 align:start position:0% permissionless and us automatic as we would<01:08:36.410> like<01:08:36.590> these<01:08:36.740> two<01:08:36.890> things<01:08:37.070> to<01:08:37.250> be<01:08:37.460> there 01:08:37.720 --> 01:08:37.730 align:start position:0% would like these two things to be there 01:08:37.730 --> 01:08:39.870 align:start position:0% would like these two things to be there still<01:08:38.000> is<01:08:38.210> some<01:08:38.540> friction<01:08:38.750> with<01:08:39.200> the<01:08:39.230> hardware 01:08:39.870 --> 01:08:39.880 align:start position:0% still is some friction with the hardware 01:08:39.880 --> 01:08:44.140 align:start position:0% still is some friction with the hardware the<01:08:40.880> radio<01:08:41.180> hardware<01:08:41.860> and<01:08:42.860> outreach<01:08:43.550> part<01:08:44.030> of 01:08:44.140 --> 01:08:44.150 align:start position:0% the radio hardware and outreach part of 01:08:44.150 --> 01:08:47.770 align:start position:0% the radio hardware and outreach part of it<01:08:44.300> so<01:08:44.660> we<01:08:45.350> have<01:08:45.650> another<01:08:46.310> incentive<01:08:46.850> for<01:08:47.540> what 01:08:47.770 --> 01:08:47.780 align:start position:0% it so we have another incentive for what 01:08:47.780 --> 01:08:50.140 align:start position:0% it so we have another incentive for what we<01:08:47.900> call<01:08:48.050> organizers<01:08:48.740> which<01:08:49.370> is<01:08:49.550> typically 01:08:50.140 --> 01:08:50.150 align:start position:0% we call organizers which is typically 01:08:50.150 --> 01:08:52.240 align:start position:0% we call organizers which is typically like<01:08:50.330> a<01:08:50.390> business<01:08:50.870> or<01:08:51.380> in<01:08:51.500> the<01:08:51.560> case<01:08:51.800> of<01:08:51.830> that 01:08:52.240 --> 01:08:52.250 align:start position:0% like a business or in the case of that 01:08:52.250 --> 01:08:56.010 align:start position:0% like a business or in the case of that rural<01:08:52.670> network<01:08:53.180> of<01:08:53.300> it's<01:08:53.810> a<01:08:53.900> cooperative<01:08:54.470> or 01:08:56.010 --> 01:08:56.020 align:start position:0% rural network of it's a cooperative or 01:08:56.020 --> 01:08:58.240 align:start position:0% rural network of it's a cooperative or sometimes<01:08:57.020> it's<01:08:57.140> a<01:08:57.200> nonprofit<01:08:57.530> as<01:08:57.890> well<01:08:58.070> so 01:08:58.240 --> 01:08:58.250 align:start position:0% sometimes it's a nonprofit as well so 01:08:58.250 --> 01:08:59.470 align:start position:0% sometimes it's a nonprofit as well so it's<01:08:58.340> kind<01:08:58.550> of<01:08:58.580> different<01:08:58.880> legal<01:08:59.120> structures 01:08:59.470 --> 01:08:59.480 align:start position:0% it's kind of different legal structures 01:08:59.480 --> 01:09:02.410 align:start position:0% it's kind of different legal structures but<01:08:59.810> this<01:08:59.990> sort<01:09:00.170> of<01:09:00.290> entity<01:09:01.210> provides<01:09:02.210> for<01:09:02.360> the 01:09:02.410 --> 01:09:02.420 align:start position:0% but this sort of entity provides for the 01:09:02.420 --> 01:09:03.700 align:start position:0% but this sort of entity provides for the customer<01:09:02.750> service<01:09:03.080> that<01:09:03.200> things<01:09:03.410> go<01:09:03.530> wrong 01:09:03.700 --> 01:09:03.710 align:start position:0% customer service that things go wrong 01:09:03.710 --> 01:09:06.490 align:start position:0% customer service that things go wrong helps<01:09:04.460> solve<01:09:05.150> people<01:09:05.450> in<01:09:05.540> many<01:09:05.660> cases<01:09:06.110> and 01:09:06.490 --> 01:09:06.500 align:start position:0% helps solve people in many cases and 01:09:06.500 --> 01:09:08.710 align:start position:0% helps solve people in many cases and kind<01:09:07.460> of<01:09:07.520> helps<01:09:07.760> curate<01:09:08.120> the<01:09:08.240> network<01:09:08.570> as<01:09:08.690> it 01:09:08.710 --> 01:09:08.720 align:start position:0% kind of helps curate the network as it 01:09:08.720 --> 01:09:12.280 align:start position:0% kind of helps curate the network as it grows<01:09:08.960> and<01:09:09.410> they<01:09:10.480> and<01:09:11.480> they<01:09:11.780> earn<01:09:11.960> a<01:09:12.050> monthly 01:09:12.280 --> 01:09:12.290 align:start position:0% grows and they and they earn a monthly 01:09:12.290 --> 01:09:16.080 align:start position:0% grows and they and they earn a monthly for<01:09:12.560> way<01:09:12.680> this<01:09:12.830> description<01:09:13.690> but<01:09:14.690> for<01:09:14.960> the<01:09:15.050> in 01:09:16.080 --> 01:09:16.090 align:start position:0% for way this description but for the in 01:09:16.090 --> 01:09:19.150 align:start position:0% for way this description but for the in users<01:09:17.090> and<01:09:17.360> subscribers<01:09:17.680> we<01:09:18.680> simply<01:09:18.980> load 01:09:19.150 --> 01:09:19.160 align:start position:0% users and subscribers we simply load 01:09:19.160 --> 01:09:20.950 align:start position:0% users and subscribers we simply load their<01:09:19.340> router<01:09:19.520> up<01:09:19.760> with<01:09:19.940> aetherium<01:09:20.420> or<01:09:20.570> X<01:09:20.720> die 01:09:20.950 --> 01:09:20.960 align:start position:0% their router up with aetherium or X die 01:09:20.960 --> 01:09:25.210 align:start position:0% their router up with aetherium or X die and<01:09:21.470> then<01:09:22.780> it's<01:09:23.780> rather<01:09:24.110> automatically<01:09:24.920> to 01:09:25.210 --> 01:09:25.220 align:start position:0% and then it's rather automatically to 01:09:25.220 --> 01:09:26.860 align:start position:0% and then it's rather automatically to the<01:09:25.490> people<01:09:25.850> who<01:09:26.030> are<01:09:26.180> forwarding<01:09:26.540> them<01:09:26.660> bound 01:09:26.860 --> 01:09:26.870 align:start position:0% the people who are forwarding them bound 01:09:26.870 --> 01:09:28.870 align:start position:0% the people who are forwarding them bound with<01:09:27.110> or<01:09:27.350> in<01:09:27.800> a<01:09:27.890> pro-rated<01:09:28.220> way<01:09:28.520> for<01:09:28.820> the 01:09:28.870 --> 01:09:28.880 align:start position:0% with or in a pro-rated way for the 01:09:28.880 --> 01:09:30.520 align:start position:0% with or in a pro-rated way for the monthly<01:09:29.180> subscription<01:09:29.690> fee<01:09:29.840> the<01:09:30.050> organizers 01:09:30.520 --> 01:09:30.530 align:start position:0% monthly subscription fee the organizers 01:09:30.530 --> 01:09:32.139 align:start position:0% monthly subscription fee the organizers address 01:09:32.139 --> 01:09:32.149 align:start position:0% address 01:09:32.149 --> 01:09:34.620 align:start position:0% address [Music] 01:09:34.620 --> 01:09:34.630 align:start position:0% [Music] 01:09:34.630 --> 01:09:36.240 align:start position:0% [Music] and<01:09:35.500> so<01:09:35.620> this<01:09:35.770> is<01:09:35.890> sort<01:09:35.980> of<01:09:36.100> our<01:09:36.190> next 01:09:36.240 --> 01:09:36.250 align:start position:0% and so this is sort of our next 01:09:36.250 --> 01:09:38.370 align:start position:0% and so this is sort of our next iteration<01:09:36.910> of<01:09:36.970> the<01:09:37.060> project<01:09:37.480> we<01:09:37.630> have<01:09:38.020> the 01:09:38.370 --> 01:09:38.380 align:start position:0% iteration of the project we have the 01:09:38.380 --> 01:09:41.940 align:start position:0% iteration of the project we have the pilot<01:09:38.740> program<01:09:39.520> and<01:09:40.230> and<01:09:41.230> now<01:09:41.500> we're<01:09:41.680> helping 01:09:41.940 --> 01:09:41.950 align:start position:0% pilot program and and now we're helping 01:09:41.950 --> 01:09:43.440 align:start position:0% pilot program and and now we're helping other<01:09:42.130> folks<01:09:42.340> get<01:09:42.820> started<01:09:43.120> with<01:09:43.210> their<01:09:43.330> own 01:09:43.440 --> 01:09:43.450 align:start position:0% other folks get started with their own 01:09:43.450 --> 01:09:47.490 align:start position:0% other folks get started with their own networks<01:09:44.490> so<01:09:45.490> these<01:09:45.850> these<01:09:46.780> are<01:09:46.840> what<01:09:47.380> we<01:09:47.470> call 01:09:47.490 --> 01:09:47.500 align:start position:0% networks so these these are what we call 01:09:47.500 --> 01:09:50.970 align:start position:0% networks so these these are what we call Thea<01:09:47.920> feds<01:09:48.250> and<01:09:49.170> essentially<01:09:50.170> it's<01:09:50.650> just<01:09:50.710> sort 01:09:50.970 --> 01:09:50.980 align:start position:0% Thea feds and essentially it's just sort 01:09:50.980 --> 01:09:52.740 align:start position:0% Thea feds and essentially it's just sort of<01:09:51.010> a<01:09:51.100> set<01:09:51.310> of<01:09:51.580> marketing<01:09:52.300> and 01:09:52.740 --> 01:09:52.750 align:start position:0% of a set of marketing and 01:09:52.750 --> 01:09:56.340 align:start position:0% of a set of marketing and pre-registration<01:09:53.740> page<01:09:54.430> so<01:09:54.850> that<01:09:55.350> organizers 01:09:56.340 --> 01:09:56.350 align:start position:0% pre-registration page so that organizers 01:09:56.350 --> 01:09:58.830 align:start position:0% pre-registration page so that organizers have<01:09:56.530> time<01:09:56.740> and<01:09:57.150> kind<01:09:58.150> of<01:09:58.210> front-load<01:09:58.660> the 01:09:58.830 --> 01:09:58.840 align:start position:0% have time and kind of front-load the 01:09:58.840 --> 01:10:00.870 align:start position:0% have time and kind of front-load the user<01:09:59.380> acquisition<01:09:59.680> so<01:10:00.310> when<01:10:00.520> they're<01:10:00.700> ready 01:10:00.870 --> 01:10:00.880 align:start position:0% user acquisition so when they're ready 01:10:00.880 --> 01:10:03.270 align:start position:0% user acquisition so when they're ready to<01:10:01.060> build<01:10:01.510> out<01:10:01.720> that<01:10:01.750> sort<01:10:02.230> of<01:10:02.290> initial<01:10:02.530> fiber 01:10:03.270 --> 01:10:03.280 align:start position:0% to build out that sort of initial fiber 01:10:03.280 --> 01:10:05.760 align:start position:0% to build out that sort of initial fiber backhaul<01:10:03.790> and<01:10:04.720> get<01:10:04.870> that<01:10:04.960> network<01:10:05.290> anchor 01:10:05.760 --> 01:10:05.770 align:start position:0% backhaul and get that network anchor 01:10:05.770 --> 01:10:08.250 align:start position:0% backhaul and get that network anchor then<01:10:06.400> they<01:10:06.880> have<01:10:07.090> all<01:10:07.330> of<01:10:07.510> their<01:10:07.690> you<01:10:08.230> know 01:10:08.250 --> 01:10:08.260 align:start position:0% then they have all of their you know 01:10:08.260 --> 01:10:10.230 align:start position:0% then they have all of their you know user<01:10:08.530> acquisition<01:10:08.740> and<01:10:09.490> marketing<01:10:09.940> or 01:10:10.230 --> 01:10:10.240 align:start position:0% user acquisition and marketing or 01:10:10.240 --> 01:10:12.510 align:start position:0% user acquisition and marketing or whatever<01:10:10.330> already<01:10:10.870> in<01:10:11.020> place<01:10:11.200> and<01:10:12.190> so<01:10:12.280> we<01:10:12.310> have 01:10:12.510 --> 01:10:12.520 align:start position:0% whatever already in place and so we have 01:10:12.520 --> 01:10:14.640 align:start position:0% whatever already in place and so we have a<01:10:12.550> few<01:10:12.760> folks<01:10:12.970> we<01:10:13.270> have<01:10:13.360> a<01:10:13.390> couple<01:10:13.750> of<01:10:13.900> members 01:10:14.640 --> 01:10:14.650 align:start position:0% a few folks we have a couple of members 01:10:14.650 --> 01:10:16.440 align:start position:0% a few folks we have a couple of members starting<01:10:15.130> in<01:10:15.220> the<01:10:15.280> United<01:10:15.370> States<01:10:15.850> and<01:10:16.180> one<01:10:16.300> in 01:10:16.440 --> 01:10:16.450 align:start position:0% starting in the United States and one in 01:10:16.450 --> 01:10:18.090 align:start position:0% starting in the United States and one in Nigeria<01:10:16.900> here<01:10:17.110> in<01:10:17.170> the<01:10:17.230> next<01:10:17.410> few<01:10:17.590> months<01:10:17.770> and 01:10:18.090 --> 01:10:18.100 align:start position:0% Nigeria here in the next few months and 01:10:18.100 --> 01:10:19.560 align:start position:0% Nigeria here in the next few months and then<01:10:18.220> about<01:10:18.340> another<01:10:18.400> ten<01:10:18.850> networks<01:10:19.270> that<01:10:19.540> are 01:10:19.560 --> 01:10:19.570 align:start position:0% then about another ten networks that are 01:10:19.570 --> 01:10:24.010 align:start position:0% then about another ten networks that are working<01:10:20.350> on<01:10:21.240> starting<01:10:22.240> up 01:10:24.010 --> 01:10:24.020 align:start position:0% working on starting up 01:10:24.020 --> 01:10:29.399 align:start position:0% working on starting up 20 01:10:29.399 --> 01:10:29.409 align:start position:0% 01:10:29.409 --> 01:10:31.260 align:start position:0% I'm<01:10:29.920> just<01:10:30.130> to<01:10:30.219> kind<01:10:30.429> of<01:10:30.489> recap<01:10:30.670> and<01:10:31.090> then<01:10:31.179> I 01:10:31.260 --> 01:10:31.270 align:start position:0% I'm just to kind of recap and then I 01:10:31.270 --> 01:10:32.820 align:start position:0% I'm just to kind of recap and then I think<01:10:31.420> there's<01:10:31.659> some<01:10:31.810> time<01:10:31.989> for<01:10:32.139> questions 01:10:32.820 --> 01:10:32.830 align:start position:0% think there's some time for questions 01:10:32.830 --> 01:10:36.570 align:start position:0% think there's some time for questions yeah<01:10:33.190> well<01:10:34.060> so<01:10:34.960> kind<01:10:35.889> of<01:10:35.920> the<01:10:36.040> benefits<01:10:36.460> of 01:10:36.570 --> 01:10:36.580 align:start position:0% yeah well so kind of the benefits of 01:10:36.580 --> 01:10:38.220 align:start position:0% yeah well so kind of the benefits of course<01:10:36.790> is<01:10:36.909> that<01:10:37.000> it's<01:10:37.120> owned<01:10:37.330> and<01:10:37.810> run<01:10:38.020> by<01:10:38.080> the 01:10:38.220 --> 01:10:38.230 align:start position:0% course is that it's owned and run by the 01:10:38.230 --> 01:10:41.129 align:start position:0% course is that it's owned and run by the community<01:10:38.800> that<01:10:39.010> it's<01:10:39.190> serving<01:10:39.460> and<01:10:39.850> I<01:10:40.780> think 01:10:41.129 --> 01:10:41.139 align:start position:0% community that it's serving and I think 01:10:41.139 --> 01:10:43.410 align:start position:0% community that it's serving and I think we<01:10:41.260> think<01:10:42.010> the<01:10:42.070> another<01:10:42.280> benefit<01:10:42.760> of<01:10:42.790> a<01:10:43.030> kind 01:10:43.410 --> 01:10:43.420 align:start position:0% we think the another benefit of a kind 01:10:43.420 --> 01:10:44.939 align:start position:0% we think the another benefit of a kind of<01:10:43.540> any<01:10:43.719> peer-to-peer<01:10:43.989> system<01:10:44.590> is<01:10:44.710> that<01:10:44.830> the 01:10:44.939 --> 01:10:44.949 align:start position:0% of any peer-to-peer system is that the 01:10:44.949 --> 01:10:47.430 align:start position:0% of any peer-to-peer system is that the money<01:10:45.610> stays<01:10:45.969> within<01:10:46.300> the<01:10:46.420> economic<01:10:46.690> system 01:10:47.430 --> 01:10:47.440 align:start position:0% money stays within the economic system 01:10:47.440 --> 01:10:51.330 align:start position:0% money stays within the economic system that<01:10:47.469> it<01:10:48.090> that<01:10:49.090> is<01:10:49.270> serving<01:10:50.139> so<01:10:50.889> instead<01:10:51.280> of 01:10:51.330 --> 01:10:51.340 align:start position:0% that it that is serving so instead of 01:10:51.340 --> 01:10:53.640 align:start position:0% that it that is serving so instead of the<01:10:51.790> many<01:10:52.179> telecoms<01:10:52.750> where<01:10:53.050> it's<01:10:53.139> distracting 01:10:53.640 --> 01:10:53.650 align:start position:0% the many telecoms where it's distracting 01:10:53.650 --> 01:10:54.930 align:start position:0% the many telecoms where it's distracting walls<01:10:53.860> was<01:10:54.130> to<01:10:54.219> have<01:10:54.310> these<01:10:54.460> developing 01:10:54.930 --> 01:10:54.940 align:start position:0% walls was to have these developing 01:10:54.940 --> 01:10:56.550 align:start position:0% walls was to have these developing countries<01:10:55.000> right<01:10:55.600> where<01:10:55.750> we<01:10:55.840> have<01:10:56.020> foreign 01:10:56.550 --> 01:10:56.560 align:start position:0% countries right where we have foreign 01:10:56.560 --> 01:10:58.229 align:start position:0% countries right where we have foreign companies<01:10:56.949> coming<01:10:57.190> in<01:10:57.429> and<01:10:57.639> distracting<01:10:58.090> all 01:10:58.229 --> 01:10:58.239 align:start position:0% companies coming in and distracting all 01:10:58.239 --> 01:11:01.590 align:start position:0% companies coming in and distracting all this<01:10:58.420> that<01:10:59.250> community's<01:11:00.250> able<01:11:00.610> to<01:11:00.790> reap<01:11:01.449> the 01:11:01.590 --> 01:11:01.600 align:start position:0% this that community's able to reap the 01:11:01.600 --> 01:11:04.860 align:start position:0% this that community's able to reap the economic<01:11:01.630> benefits<01:11:02.940> and<01:11:03.940> again<01:11:04.480> that's<01:11:04.810> that 01:11:04.860 --> 01:11:04.870 align:start position:0% economic benefits and again that's that 01:11:04.870 --> 01:11:07.530 align:start position:0% economic benefits and again that's that also<01:11:05.230> that<01:11:05.380> built<01:11:05.710> in<01:11:05.860> competition<01:11:06.540> where 01:11:07.530 --> 01:11:07.540 align:start position:0% also that built in competition where 01:11:07.540 --> 01:11:10.919 align:start position:0% also that built in competition where your<01:11:08.080> router<01:11:08.409> is<01:11:08.710> is<01:11:08.889> basically<01:11:09.449> choosing<01:11:10.449> the 01:11:10.919 --> 01:11:10.929 align:start position:0% your router is is basically choosing the 01:11:10.929 --> 01:11:14.729 align:start position:0% your router is is basically choosing the most<01:11:11.139> competitive<01:11:11.440> link<01:11:13.020> it's<01:11:14.020> a<01:11:14.290> sustainable 01:11:14.729 --> 01:11:14.739 align:start position:0% most competitive link it's a sustainable 01:11:14.739 --> 01:11:16.890 align:start position:0% most competitive link it's a sustainable way<01:11:15.100> because<01:11:15.760> of<01:11:15.850> the<01:11:15.940> incentivize<01:11:16.389> links<01:11:16.780> we 01:11:16.890 --> 01:11:16.900 align:start position:0% way because of the incentivize links we 01:11:16.900 --> 01:11:21.689 align:start position:0% way because of the incentivize links we see<01:11:17.110> the<01:11:17.260> network<01:11:17.850> factors<01:11:18.850> well<01:11:20.699> neighbors 01:11:21.689 --> 01:11:21.699 align:start position:0% see the network factors well neighbors 01:11:21.699 --> 01:11:23.160 align:start position:0% see the network factors well neighbors hanging<01:11:22.000> neighbors<01:11:22.270> for<01:11:22.449> bandwidth<01:11:22.840> which<01:11:23.139> is 01:11:23.160 --> 01:11:23.170 align:start position:0% hanging neighbors for bandwidth which is 01:11:23.170 --> 01:11:32.459 align:start position:0% hanging neighbors for bandwidth which is like<01:11:23.530> very<01:11:23.770> poor<01:11:24.400> p2p<01:11:25.270> great<01:11:26.940> and<01:11:28.080> yes<01:11:29.080> so<01:11:31.469> so 01:11:32.459 --> 01:11:32.469 align:start position:0% like very poor p2p great and yes so so 01:11:32.469 --> 01:11:39.459 align:start position:0% like very poor p2p great and yes so so do<01:11:32.530> you<01:11:32.679> have<01:11:32.770> any<01:11:32.980> questions 01:11:39.459 --> 01:11:39.469 align:start position:0% 01:11:39.469 --> 01:11:44.209 align:start position:0% what's<01:11:40.469> the<01:11:40.650> cost<01:11:40.980> I<01:11:41.340> guess<01:11:43.010> put<01:11:44.010> that 01:11:44.209 --> 01:11:44.219 align:start position:0% what's the cost I guess put that 01:11:44.219 --> 01:11:46.879 align:start position:0% what's the cost I guess put that infrastructure<01:11:44.730> in<01:11:44.940> place<01:11:45.210> is<01:11:45.710> obviously<01:11:46.710> an 01:11:46.879 --> 01:11:46.889 align:start position:0% infrastructure in place is obviously an 01:11:46.889 --> 01:11:48.890 align:start position:0% infrastructure in place is obviously an all<01:11:47.070> Hardware<01:11:47.580> and<01:11:47.940> I<01:11:48.030> guess<01:11:48.300> to<01:11:48.449> create<01:11:48.750> a 01:11:48.890 --> 01:11:48.900 align:start position:0% all Hardware and I guess to create a 01:11:48.900 --> 01:11:52.100 align:start position:0% all Hardware and I guess to create a relay<01:11:49.460> to<01:11:50.460> install<01:11:51.210> that<01:11:51.389> with<01:11:51.630> what's<01:11:51.960> the 01:11:52.100 --> 01:11:52.110 align:start position:0% relay to install that with what's the 01:11:52.110 --> 01:11:54.620 align:start position:0% relay to install that with what's the cost<01:11:52.340> associated<01:11:53.340> with<01:11:53.699> that<01:11:54.000> he<01:11:54.480> has<01:11:54.599> a 01:11:54.620 --> 01:11:54.630 align:start position:0% cost associated with that he has a 01:11:54.630 --> 01:11:56.479 align:start position:0% cost associated with that he has a really<01:11:54.900> good<01:11:55.110> question<01:11:55.260> and<01:11:55.679> if<01:11:55.770> we<01:11:55.920> that<01:11:56.219> that 01:11:56.479 --> 01:11:56.489 align:start position:0% really good question and if we that that 01:11:56.489 --> 01:11:58.070 align:start position:0% really good question and if we that that relay<01:11:56.820> in<01:11:56.940> the<01:11:57.030> picture<01:11:57.330> there<01:11:57.510> has<01:11:57.780> about 01:11:58.070 --> 01:11:58.080 align:start position:0% relay in the picture there has about 01:11:58.080 --> 01:12:00.979 align:start position:0% relay in the picture there has about four<01:11:58.320> hundred<01:11:58.440> dollars<01:11:59.219> for<01:12:00.030> each<01:12:00.540> of<01:12:00.840> the 01:12:00.979 --> 01:12:00.989 align:start position:0% four hundred dollars for each of the 01:12:00.989 --> 01:12:04.160 align:start position:0% four hundred dollars for each of the outgoing<01:12:01.860> antennas<01:12:02.520> and<01:12:02.790> then<01:12:03.030> about<01:12:03.300> three 01:12:04.160 --> 01:12:04.170 align:start position:0% outgoing antennas and then about three 01:12:04.170 --> 01:12:05.899 align:start position:0% outgoing antennas and then about three hundred<01:12:04.530> for<01:12:04.739> the<01:12:04.860> incumbents<01:12:05.610> on<01:12:05.730> it<01:12:05.849> so 01:12:05.899 --> 01:12:05.909 align:start position:0% hundred for the incumbents on it so 01:12:05.909 --> 01:12:07.250 align:start position:0% hundred for the incumbents on it so that's<01:12:06.060> actually<01:12:06.119> a<01:12:06.300> little<01:12:06.449> bit<01:12:06.599> more<01:12:06.780> robust 01:12:07.250 --> 01:12:07.260 align:start position:0% that's actually a little bit more robust 01:12:07.260 --> 01:12:09.020 align:start position:0% that's actually a little bit more robust than<01:12:07.409> some<01:12:07.619> of<01:12:07.739> the<01:12:07.860> relays<01:12:08.190> I<01:12:08.460> would<01:12:08.940> say 01:12:09.020 --> 01:12:09.030 align:start position:0% than some of the relays I would say 01:12:09.030 --> 01:12:10.580 align:start position:0% than some of the relays I would say you're<01:12:09.179> probably<01:12:09.360> gonna<01:12:09.540> be<01:12:09.630> up<01:12:09.659> to<01:12:09.929> 500<01:12:10.469> and 01:12:10.580 --> 01:12:10.590 align:start position:0% you're probably gonna be up to 500 and 01:12:10.590 --> 01:12:12.530 align:start position:0% you're probably gonna be up to 500 and then<01:12:10.710> and<01:12:11.369> a<01:12:11.460> thousand<01:12:11.820> dollars<01:12:12.119> depending<01:12:12.239> on 01:12:12.530 --> 01:12:12.540 align:start position:0% then and a thousand dollars depending on 01:12:12.540 --> 01:12:14.720 align:start position:0% then and a thousand dollars depending on how<01:12:12.690> how<01:12:13.080> many<01:12:13.170> people<01:12:13.590> it's<01:12:13.710> gonna<01:12:13.830> serve<01:12:14.099> and 01:12:14.720 --> 01:12:14.730 align:start position:0% how how many people it's gonna serve and 01:12:14.730 --> 01:12:17.600 align:start position:0% how how many people it's gonna serve and then<01:12:14.849> what<01:12:15.000> the<01:12:15.179> routers<01:12:16.190> is<01:12:17.190> it<01:12:17.429> like<01:12:17.580> a 01:12:17.600 --> 01:12:17.610 align:start position:0% then what the routers is it like a 01:12:17.610 --> 01:12:19.160 align:start position:0% then what the routers is it like a specific<01:12:18.119> router<01:12:18.330> that<01:12:18.570> you<01:12:18.630> have<01:12:18.840> to<01:12:19.020> do 01:12:19.160 --> 01:12:19.170 align:start position:0% specific router that you have to do 01:12:19.170 --> 01:12:21.680 align:start position:0% specific router that you have to do their<01:12:19.440> communication<01:12:20.400> routers<01:12:21.060> like<01:12:21.480> that 01:12:21.680 --> 01:12:21.690 align:start position:0% their communication routers like that 01:12:21.690 --> 01:12:25.700 align:start position:0% their communication routers like that you<01:12:21.810> can<01:12:21.989> get<01:12:23.150> specific<01:12:24.150> so<01:12:25.020> we<01:12:25.290> do<01:12:25.530> have 01:12:25.700 --> 01:12:25.710 align:start position:0% you can get specific so we do have 01:12:25.710 --> 01:12:27.620 align:start position:0% you can get specific so we do have supported<01:12:26.190> models<01:12:26.520> in<01:12:26.580> its<01:12:26.730> open<01:12:27.090> work<01:12:27.300> based 01:12:27.620 --> 01:12:27.630 align:start position:0% supported models in its open work based 01:12:27.630 --> 01:12:31.459 align:start position:0% supported models in its open work based our<01:12:28.560> open<01:12:28.830> wrt<01:12:29.159> and<01:12:29.820> these<01:12:30.420> are<01:12:30.690> consumer 01:12:31.459 --> 01:12:31.469 align:start position:0% our open wrt and these are consumer 01:12:31.469 --> 01:12:34.280 align:start position:0% our open wrt and these are consumer routers<01:12:31.980> that<01:12:32.010> you<01:12:32.460> can<01:12:32.639> get<01:12:32.820> from<01:12:33.000> Amazon<01:12:33.449> and 01:12:34.280 --> 01:12:34.290 align:start position:0% routers that you can get from Amazon and 01:12:34.290 --> 01:12:35.870 align:start position:0% routers that you can get from Amazon and we<01:12:34.590> have<01:12:34.710> about<01:12:34.800> three<01:12:35.070> or<01:12:35.099> four<01:12:35.369> supported 01:12:35.870 --> 01:12:35.880 align:start position:0% we have about three or four supported 01:12:35.880 --> 01:12:37.560 align:start position:0% we have about three or four supported models 01:12:37.560 --> 01:12:37.570 align:start position:0% models 01:12:37.570 --> 01:12:55.450 align:start position:0% models [Music] 01:12:55.450 --> 01:12:55.460 align:start position:0% 01:12:55.460 --> 01:12:58.490 align:start position:0% yes<01:12:56.460> it's<01:12:57.119> not<01:12:57.300> a<01:12:57.330> single<01:12:57.810> radio<01:12:58.080> of<01:12:58.320> match 01:12:58.490 --> 01:12:58.500 align:start position:0% yes it's not a single radio of match 01:12:58.500 --> 01:13:00.200 align:start position:0% yes it's not a single radio of match that<01:12:58.710> you<01:12:58.800> saw<01:12:59.010> everything<01:12:59.369> appointed<01:12:59.880> coming 01:13:00.200 --> 01:13:00.210 align:start position:0% that you saw everything appointed coming 01:13:00.210 --> 01:13:02.030 align:start position:0% that you saw everything appointed coming in<01:13:00.449> the<01:13:00.510> radio<01:13:00.810> and<01:13:01.110> without<01:13:01.440> boys<01:13:01.619> we<01:13:01.949> have 01:13:02.030 --> 01:13:02.040 align:start position:0% in the radio and without boys we have 01:13:02.040 --> 01:13:04.220 align:start position:0% in the radio and without boys we have combined<01:13:02.489> reciting<01:13:03.000> drives<01:13:03.330> percent<01:13:03.810> packet 01:13:04.220 --> 01:13:04.230 align:start position:0% combined reciting drives percent packet 01:13:04.230 --> 01:13:07.640 align:start position:0% combined reciting drives percent packet loss<01:13:04.409> her<01:13:04.849> performance<01:13:05.849> offered<01:13:06.449> with<01:13:07.199> links 01:13:07.640 --> 01:13:07.650 align:start position:0% loss her performance offered with links 01:13:07.650 --> 01:13:09.080 align:start position:0% loss her performance offered with links so<01:13:08.159> the<01:13:08.250> one<01:13:08.400> that<01:13:08.520> was<01:13:08.639> like<01:13:08.760> two<01:13:08.909> or<01:13:09.060> three 01:13:09.080 --> 01:13:09.090 align:start position:0% so the one that was like two or three 01:13:09.090 --> 01:13:10.850 align:start position:0% so the one that was like two or three team<01:13:09.449> you<01:13:09.750> know<01:13:09.840> we're<01:13:10.080> still<01:13:10.290> seeing<01:13:10.530> 50 01:13:10.850 --> 01:13:10.860 align:start position:0% team you know we're still seeing 50 01:13:10.860 --> 01:13:15.500 align:start position:0% team you know we're still seeing 50 megabits<01:13:11.340> per<01:13:11.400> second 01:13:15.500 --> 01:13:15.510 align:start position:0% 01:13:15.510 --> 01:13:17.660 align:start position:0% cuz<01:13:16.080> it<01:13:16.230> does<01:13:16.470> the<01:13:16.650> like<01:13:16.950> infrastructure<01:13:17.430> for 01:13:17.660 --> 01:13:17.670 align:start position:0% cuz it does the like infrastructure for 01:13:17.670 --> 01:13:19.430 align:start position:0% cuz it does the like infrastructure for breakdown<01:13:18.120> or<01:13:18.360> like<01:13:18.480> people<01:13:18.810> throw<01:13:18.989> a<01:13:19.020> parrot 01:13:19.430 --> 01:13:19.440 align:start position:0% breakdown or like people throw a parrot 01:13:19.440 --> 01:13:23.240 align:start position:0% breakdown or like people throw a parrot like<01:13:19.650> how<01:13:20.430> does<01:13:20.489> that<01:13:20.700> work<01:13:21.360> yeah<01:13:22.290> so<01:13:22.860> this<01:13:23.130> is 01:13:23.240 --> 01:13:23.250 align:start position:0% like how does that work yeah so this is 01:13:23.250 --> 01:13:24.890 align:start position:0% like how does that work yeah so this is why<01:13:23.340> we<01:13:23.489> have<01:13:23.640> you<01:13:24.090> know<01:13:24.210> the<01:13:24.330> concept<01:13:24.660> of<01:13:24.780> the 01:13:24.890 --> 01:13:24.900 align:start position:0% why we have you know the concept of the 01:13:24.900 --> 01:13:26.210 align:start position:0% why we have you know the concept of the organizer<01:13:25.350> right<01:13:25.650> now<01:13:25.830> they're<01:13:26.040> kind<01:13:26.070> of 01:13:26.210 --> 01:13:26.220 align:start position:0% organizer right now they're kind of 01:13:26.220 --> 01:13:28.040 align:start position:0% organizer right now they're kind of prosecutor<01:13:26.700> a<01:13:26.730> but<01:13:27.120> unfortunately<01:13:27.660> the<01:13:27.780> radio 01:13:28.040 --> 01:13:28.050 align:start position:0% prosecutor a but unfortunately the radio 01:13:28.050 --> 01:13:29.870 align:start position:0% prosecutor a but unfortunately the radio hardware<01:13:28.470> is<01:13:28.680> it<01:13:28.890> completely<01:13:29.610> in<01:13:29.790> a 01:13:29.870 --> 01:13:29.880 align:start position:0% hardware is it completely in a 01:13:29.880 --> 01:13:31.190 align:start position:0% hardware is it completely in a permission<01:13:30.180> the<01:13:30.420> state<01:13:30.660> where<01:13:30.840> people<01:13:30.960> can 01:13:31.190 --> 01:13:31.200 align:start position:0% permission the state where people can 01:13:31.200 --> 01:13:32.479 align:start position:0% permission the state where people can just<01:13:31.230> leave<01:13:31.500> and<01:13:31.650> pop<01:13:31.800> them<01:13:31.980> off<01:13:32.130> and<01:13:32.400> they 01:13:32.479 --> 01:13:32.489 align:start position:0% just leave and pop them off and they 01:13:32.489 --> 01:13:34.220 align:start position:0% just leave and pop them off and they just<01:13:32.520> work<01:13:33.030> and<01:13:33.180> everything<01:13:33.510> doesn't<01:13:33.989> even 01:13:34.220 --> 01:13:34.230 align:start position:0% just work and everything doesn't even 01:13:34.230 --> 01:13:36.710 align:start position:0% just work and everything doesn't even configure<01:13:34.680> we're<01:13:35.520> excited<01:13:35.850> about<01:13:36.000> what<01:13:36.239> some 01:13:36.710 --> 01:13:36.720 align:start position:0% configure we're excited about what some 01:13:36.720 --> 01:13:38.000 align:start position:0% configure we're excited about what some some<01:13:37.200> of<01:13:37.260> the<01:13:37.320> things<01:13:37.350> that<01:13:37.560> are<01:13:37.650> coming<01:13:37.739> with 01:13:38.000 --> 01:13:38.010 align:start position:0% some of the things that are coming with 01:13:38.010 --> 01:13:39.860 align:start position:0% some of the things that are coming with the<01:13:38.130> informing<01:13:38.580> radio<01:13:38.880> so<01:13:39.210> that<01:13:39.239> there's<01:13:39.600> less 01:13:39.860 --> 01:13:39.870 align:start position:0% the informing radio so that there's less 01:13:39.870 --> 01:13:43.460 align:start position:0% the informing radio so that there's less of<01:13:39.900> the<01:13:40.710> aiming<01:13:41.550> and<01:13:41.970> kind<01:13:42.780> of<01:13:42.870> maintenance 01:13:43.460 --> 01:13:43.470 align:start position:0% of the aiming and kind of maintenance 01:13:43.470 --> 01:13:45.860 align:start position:0% of the aiming and kind of maintenance but<01:13:44.220> yeah<01:13:44.520> all<01:13:44.790> right<01:13:44.940> now<01:13:44.970> the<01:13:45.120> organizers<01:13:45.750> do 01:13:45.860 --> 01:13:45.870 align:start position:0% but yeah all right now the organizers do 01:13:45.870 --> 01:13:49.670 align:start position:0% but yeah all right now the organizers do that<01:13:46.020> well<01:13:46.230> when<01:13:46.350> they<01:13:46.470> get<01:13:46.590> painting<01:13:46.950> with<01:13:48.680> um 01:13:49.670 --> 01:13:49.680 align:start position:0% that well when they get painting with um 01:13:49.680 --> 01:13:51.890 align:start position:0% that well when they get painting with um comfort<01:13:50.040> than<01:13:50.250> the<01:13:50.340> issues<01:13:50.790> will<01:13:51.150> the<01:13:51.360> service 01:13:51.890 --> 01:13:51.900 align:start position:0% comfort than the issues will the service 01:13:51.900 --> 01:13:55.180 align:start position:0% comfort than the issues will the service providers<01:13:52.410> I<01:13:52.730> expect<01:13:53.730> that<01:13:53.910> that<01:13:54.120> might<01:13:54.420> be 01:13:55.180 --> 01:13:55.190 align:start position:0% providers I expect that that might be 01:13:55.190 --> 01:13:57.770 align:start position:0% providers I expect that that might be perfect<01:13:56.190> mission<01:13:56.340> to<01:13:56.700> resell<01:13:57.120> your<01:13:57.480> fans 01:13:57.770 --> 01:13:57.780 align:start position:0% perfect mission to resell your fans 01:13:57.780 --> 01:14:00.710 align:start position:0% perfect mission to resell your fans which<01:13:58.050> to<01:13:58.230> either<01:13:58.350> exam<01:13:59.239> well<01:14:00.239> we<01:14:00.360> do<01:14:00.540> use<01:14:00.690> a 01:14:00.710 --> 01:14:00.720 align:start position:0% which to either exam well we do use a 01:14:00.720 --> 01:14:03.320 align:start position:0% which to either exam well we do use a whole<01:14:00.989> cell<01:14:01.200> connection<01:14:01.739> so<01:14:02.040> we<01:14:02.790> are<01:14:03.090> just 01:14:03.320 --> 01:14:03.330 align:start position:0% whole cell connection so we are just 01:14:03.330 --> 01:14:04.550 align:start position:0% whole cell connection so we are just operating<01:14:03.570> as<01:14:03.840> an<01:14:03.989> Internet<01:14:04.440> service 01:14:04.550 --> 01:14:04.560 align:start position:0% operating as an Internet service 01:14:04.560 --> 01:14:06.260 align:start position:0% operating as an Internet service provider<01:14:05.010> at<01:14:05.220> some<01:14:05.460> point<01:14:05.820> in<01:14:06.000> the<01:14:06.090> network 01:14:06.260 --> 01:14:06.270 align:start position:0% provider at some point in the network 01:14:06.270 --> 01:14:08.810 align:start position:0% provider at some point in the network order<01:14:06.930> gateway<01:14:07.380> however<01:14:08.280> what's<01:14:08.550> been<01:14:08.700> really 01:14:08.810 --> 01:14:08.820 align:start position:0% order gateway however what's been really 01:14:08.820 --> 01:14:10.640 align:start position:0% order gateway however what's been really interesting<01:14:09.390> is<01:14:09.480> that<01:14:09.510> some<01:14:09.840> people<01:14:10.200> some<01:14:10.590> of 01:14:10.640 --> 01:14:10.650 align:start position:0% interesting is that some people some of 01:14:10.650 --> 01:14:11.990 align:start position:0% interesting is that some people some of the<01:14:10.770> Internet<01:14:11.040> service<01:14:11.340> providers<01:14:11.790> have 01:14:11.990 --> 01:14:12.000 align:start position:0% the Internet service providers have 01:14:12.000 --> 01:14:14.750 align:start position:0% the Internet service providers have actually<01:14:12.739> at<01:14:13.739> first<01:14:14.010> been<01:14:14.190> really<01:14:14.460> business 01:14:14.750 --> 01:14:14.760 align:start position:0% actually at first been really business 01:14:14.760 --> 01:14:16.820 align:start position:0% actually at first been really business in<01:14:14.910> it<01:14:15.030> and<01:14:15.210> then<01:14:15.510> thought<01:14:16.350> this<01:14:16.620> might<01:14:16.770> be 01:14:16.820 --> 01:14:16.830 align:start position:0% in it and then thought this might be 01:14:16.830 --> 01:14:18.350 align:start position:0% in it and then thought this might be actually<01:14:17.160> a<01:14:17.280> pretty<01:14:17.489> cool<01:14:17.670> idea<01:14:17.730> so<01:14:18.239> I<01:14:18.270> think 01:14:18.350 --> 01:14:18.360 align:start position:0% actually a pretty cool idea so I think 01:14:18.360 --> 01:14:19.790 align:start position:0% actually a pretty cool idea so I think we'll<01:14:18.570> see<01:14:18.720> how<01:14:18.750> these<01:14:18.960> networks<01:14:19.350> growing<01:14:19.739> to 01:14:19.790 --> 01:14:19.800 align:start position:0% we'll see how these networks growing to 01:14:19.800 --> 01:14:21.440 align:start position:0% we'll see how these networks growing to stop<01:14:20.010> the<01:14:20.160> space<01:14:20.400> they're<01:14:20.760> gonna<01:14:20.850> come<01:14:21.090> up<01:14:21.120> for 01:14:21.440 --> 01:14:21.450 align:start position:0% stop the space they're gonna come up for 01:14:21.450 --> 01:14:23.450 align:start position:0% stop the space they're gonna come up for this<01:14:21.600> out<01:14:21.750> the<01:14:21.900> other<01:14:21.930> gateways<01:14:22.650> like<01:14:23.250> what 01:14:23.450 --> 01:14:23.460 align:start position:0% this out the other gateways like what 01:14:23.460 --> 01:14:25.310 align:start position:0% this out the other gateways like what are<01:14:23.610> the<01:14:23.790> reasons<01:14:24.180> for<01:14:24.239> that<01:14:24.480> you<01:14:24.720> think<01:14:25.170> this 01:14:25.310 --> 01:14:25.320 align:start position:0% are the reasons for that you think this 01:14:25.320 --> 01:14:30.800 align:start position:0% are the reasons for that you think this is<01:14:25.470> like<01:14:28.640> why<01:14:29.640> do<01:14:29.700> you<01:14:29.850> think<01:14:30.090> they<01:14:30.300> would<01:14:30.780> be 01:14:30.800 --> 01:14:30.810 align:start position:0% is like why do you think they would be 01:14:30.810 --> 01:14:35.090 align:start position:0% is like why do you think they would be killed<01:14:31.650> bad<01:14:33.230> um<01:14:34.230> well<01:14:34.650> I<01:14:34.680> think<01:14:34.800> there's 01:14:35.090 --> 01:14:35.100 align:start position:0% killed bad um well I think there's 01:14:35.100 --> 01:14:39.460 align:start position:0% killed bad um well I think there's always<01:14:35.250> legacy<01:14:35.970> resistance<01:14:36.870> to<01:14:36.960> change<01:14:37.550> but<01:14:38.550> I 01:14:39.460 --> 01:14:39.470 align:start position:0% always legacy resistance to change but I 01:14:39.470 --> 01:14:42.399 align:start position:0% always legacy resistance to change but I think<01:14:40.470> I<01:14:40.560> think<01:14:40.770> as<01:14:40.890> time<01:14:41.280> goes<01:14:41.489> on<01:14:41.580> that 01:14:42.399 --> 01:14:42.409 align:start position:0% think I think as time goes on that 01:14:42.409 --> 01:14:43.510 align:start position:0% think I think as time goes on that they'll<01:14:42.530> see<01:14:42.679> the<01:14:42.770> market<01:14:43.040> potential<01:14:43.280> that's 01:14:43.510 --> 01:14:43.520 align:start position:0% they'll see the market potential that's 01:14:43.520 --> 01:14:45.580 align:start position:0% they'll see the market potential that's less<01:14:43.790> lost<01:14:44.030> give<01:14:44.810> a<01:14:44.900> plaintiff<01:14:45.290> and<01:14:45.350> I<01:14:45.469> ask 01:14:45.580 --> 01:14:45.590 align:start position:0% less lost give a plaintiff and I ask 01:14:45.590 --> 01:14:49.720 align:start position:0% less lost give a plaintiff and I ask advise<01:14:46.010> you<01:14:47.860> to<01:14:48.860> agree<01:14:49.070> we<01:14:49.250> would<01:14:49.520> hope<01:14:49.670> that 01:14:49.720 --> 01:14:49.730 align:start position:0% advise you to agree we would hope that 01:14:49.730 --> 01:14:52.870 align:start position:0% advise you to agree we would hope that they<01:14:49.909> would<01:14:49.940> just<01:14:50.120> run<01:14:50.239> the<01:14:51.310> okay<01:14:52.310> how<01:14:52.699> do<01:14:52.760> you 01:14:52.870 --> 01:14:52.880 align:start position:0% they would just run the okay how do you 01:14:52.880 --> 01:14:54.580 align:start position:0% they would just run the okay how do you sustain<01:14:53.150> your<01:14:53.570> work<01:14:53.840> because<01:14:54.230> you<01:14:54.320> said<01:14:54.500> an 01:14:54.580 --> 01:14:54.590 align:start position:0% sustain your work because you said an 01:14:54.590 --> 01:14:56.830 align:start position:0% sustain your work because you said an adult<01:14:54.889> extract<01:14:55.340> value<01:14:55.730> from<01:14:55.880> this<01:14:56.239> community 01:14:56.830 --> 01:14:56.840 align:start position:0% adult extract value from this community 01:14:56.840 --> 01:14:59.070 align:start position:0% adult extract value from this community that<01:14:57.020> also<01:14:57.320> start<01:14:57.590> the<01:14:57.739> caduceus<01:14:58.219> than<01:14:58.429> your 01:14:59.070 --> 01:14:59.080 align:start position:0% that also start the caduceus than your 01:14:59.080 --> 01:15:02.410 align:start position:0% that also start the caduceus than your yeah<01:15:00.080> so<01:15:01.060> we're<01:15:02.060> working 01:15:02.410 --> 01:15:02.420 align:start position:0% yeah so we're working 01:15:02.420 --> 01:15:06.729 align:start position:0% yeah so we're working we're<01:15:02.540> building<01:15:02.690> a<01:15:04.570> cosmos<01:15:05.570> for<01:15:05.719> change<01:15:06.020> so 01:15:06.729 --> 01:15:06.739 align:start position:0% we're building a cosmos for change so 01:15:06.739 --> 01:15:08.709 align:start position:0% we're building a cosmos for change so that<01:15:06.770> people<01:15:07.460> will<01:15:07.550> pay<01:15:07.730> with<01:15:07.880> the<01:15:08.030> period<01:15:08.449> and 01:15:08.709 --> 01:15:08.719 align:start position:0% that people will pay with the period and 01:15:08.719 --> 01:15:11.410 align:start position:0% that people will pay with the period and then<01:15:08.870> it<01:15:08.900> will<01:15:09.440> fetch<01:15:10.429> to<01:15:10.670> our<01:15:10.760> token<01:15:11.120> so<01:15:11.360> no 01:15:11.410 --> 01:15:11.420 align:start position:0% then it will fetch to our token so no 01:15:11.420 --> 01:15:14.860 align:start position:0% then it will fetch to our token so no seven<01:15:11.840> areas<01:15:12.699> minor<01:15:13.699> five<01:15:14.389> percent<01:15:14.719> of<01:15:14.810> the 01:15:14.860 --> 01:15:14.870 align:start position:0% seven areas minor five percent of the 01:15:14.870 --> 01:15:16.780 align:start position:0% seven areas minor five percent of the transaction<01:15:15.350> easier<01:15:15.739> to<01:15:15.949> get<01:15:16.070> token<01:15:16.280> holders 01:15:16.780 --> 01:15:16.790 align:start position:0% transaction easier to get token holders 01:15:16.790 --> 01:15:18.850 align:start position:0% transaction easier to get token holders actually<01:15:17.179> well<01:15:17.360> so<01:15:17.630> for<01:15:18.110> end-users<01:15:18.380> they'll 01:15:18.850 --> 01:15:18.860 align:start position:0% actually well so for end-users they'll 01:15:18.860 --> 01:15:21.220 align:start position:0% actually well so for end-users they'll still<01:15:19.130> have<01:15:19.489> the<01:15:19.969> same<01:15:20.179> process<01:15:20.480> of<01:15:20.900> buying 01:15:21.220 --> 01:15:21.230 align:start position:0% still have the same process of buying 01:15:21.230 --> 01:15:25.240 align:start position:0% still have the same process of buying ethan<01:15:21.739> routers<01:15:22.580> but<01:15:23.270> then<01:15:23.630> our<01:15:24.350> companies 01:15:25.240 --> 01:15:25.250 align:start position:0% ethan routers but then our companies 01:15:25.250 --> 01:15:43.000 align:start position:0% ethan routers but then our companies actually<01:15:40.600> yeah<01:15:41.600> this<01:15:41.810> dog<01:15:42.230> is<01:15:42.440> savvy<01:15:42.830> team 01:15:43.000 --> 01:15:43.010 align:start position:0% actually yeah this dog is savvy team 01:15:43.010 --> 01:15:44.620 align:start position:0% actually yeah this dog is savvy team provides<01:15:43.400> because<01:15:43.790> i<01:15:43.850> was<01:15:44.150> invited 01:15:44.620 --> 01:15:44.630 align:start position:0% provides because i was invited 01:15:44.630 --> 01:15:47.530 align:start position:0% provides because i was invited yesterday<01:15:45.080> fat<01:15:45.260> i<01:15:45.409> i'm<01:15:45.650> given<01:15:46.070> a<01:15:46.190> longer<01:15:47.060> stop 01:15:47.530 --> 01:15:47.540 align:start position:0% yesterday fat i i'm given a longer stop 01:15:47.540 --> 01:15:50.879 align:start position:0% yesterday fat i i'm given a longer stop at<01:15:47.840> working<01:15:48.290> swans<01:15:49.130> recognition<01:15:49.969> a<01:15:50.090> soprano 01:15:50.879 --> 01:15:50.889 align:start position:0% at working swans recognition a soprano 01:15:50.889 --> 01:15:56.160 align:start position:0% at working swans recognition a soprano so<01:15:51.889> little<01:15:52.820> bit<01:15:52.940> about<01:15:53.210> me<01:15:54.040> Tirion 01:15:56.160 --> 01:15:56.170 align:start position:0% so little bit about me Tirion 01:15:56.170 --> 01:15:59.580 align:start position:0% so little bit about me Tirion Athene<01:15:57.100> I<01:15:57.220> was<01:15:57.430> doing<01:15:58.150> research<01:15:58.300> on<01:15:58.810> the 01:15:59.580 --> 01:15:59.590 align:start position:0% Athene I was doing research on the 01:15:59.590 --> 01:16:03.600 align:start position:0% Athene I was doing research on the racial<01:15:59.800> codes<01:16:00.540> for<01:16:01.540> cloud<01:16:02.020> storage<01:16:02.320> and<01:16:03.100> we 01:16:03.600 --> 01:16:03.610 align:start position:0% racial codes for cloud storage and we 01:16:03.610 --> 01:16:06.120 align:start position:0% racial codes for cloud storage and we have<01:16:03.730> to<01:16:03.850> be<01:16:03.970> a<01:16:04.000> systems<01:16:04.570> I<01:16:04.840> did<01:16:05.410> my<01:16:05.620> PhD<01:16:05.680> in 01:16:06.120 --> 01:16:06.130 align:start position:0% have to be a systems I did my PhD in 01:16:06.130 --> 01:16:08.970 align:start position:0% have to be a systems I did my PhD in Switzerland<01:16:06.850> I<01:16:07.060> also<01:16:07.300> I<01:16:07.540> did<01:16:07.810> disorder<01:16:08.770> center 01:16:08.970 --> 01:16:08.980 align:start position:0% Switzerland I also I did disorder center 01:16:08.980 --> 01:16:15.410 align:start position:0% Switzerland I also I did disorder center at<01:16:09.370> UC<01:16:10.180> Santa<01:16:10.450> Cruz<01:16:11.640> since<01:16:12.640> during<01:16:13.510> my<01:16:13.810> PhD<01:16:14.020> I 01:16:15.410 --> 01:16:15.420 align:start position:0% at UC Santa Cruz since during my PhD I 01:16:15.420 --> 01:16:19.290 align:start position:0% at UC Santa Cruz since during my PhD I produced<01:16:16.420> the<01:16:16.630> alfonseca<01:16:17.500> macros<01:16:18.040> and<01:16:18.430> the 01:16:19.290 --> 01:16:19.300 align:start position:0% produced the alfonseca macros and the 01:16:19.300 --> 01:16:21.180 align:start position:0% produced the alfonseca macros and the since<01:16:19.570> last<01:16:19.870> year<01:16:20.140> I<01:16:20.350> started<01:16:20.500> collaborating 01:16:21.180 --> 01:16:21.190 align:start position:0% since last year I started collaborating 01:16:21.190 --> 01:16:23.910 align:start position:0% since last year I started collaborating with<01:16:21.730> the<01:16:21.880> people<01:16:22.180> from<01:16:22.390> the<01:16:22.570> fever<01:16:22.780> swamp<01:16:23.170> to 01:16:23.910 --> 01:16:23.920 align:start position:0% with the people from the fever swamp to 01:16:23.920 --> 01:16:26.190 align:start position:0% with the people from the fever swamp to see<01:16:24.160> if<01:16:24.280> we<01:16:24.400> can<01:16:24.520> implement<01:16:24.850> this<01:16:25.210> coach<01:16:25.720> in 01:16:26.190 --> 01:16:26.200 align:start position:0% see if we can implement this coach in 01:16:26.200 --> 01:16:30.380 align:start position:0% see if we can implement this coach in Swan<01:16:26.680> to<01:16:26.950> make<01:16:27.130> the<01:16:27.340> Swan<01:16:27.910> more<01:16:28.210> robust<01:16:28.630> and 01:16:30.380 --> 01:16:30.390 align:start position:0% Swan to make the Swan more robust and 01:16:30.390 --> 01:16:33.360 align:start position:0% Swan to make the Swan more robust and since<01:16:31.390> this<01:16:31.600> year<01:16:31.960> I<01:16:32.230> joined<01:16:32.320> the<01:16:32.800> BB<01:16:33.070> change 01:16:33.360 --> 01:16:33.370 align:start position:0% since this year I joined the BB change 01:16:33.370 --> 01:16:35.670 align:start position:0% since this year I joined the BB change Norwegian<01:16:34.210> project<01:16:34.660> at<01:16:34.780> University<01:16:35.320> of<01:16:35.380> Festa 01:16:35.670 --> 01:16:35.680 align:start position:0% Norwegian project at University of Festa 01:16:35.680 --> 01:16:39.450 align:start position:0% Norwegian project at University of Festa Wonga<01:16:36.070> which<01:16:36.730> aims<01:16:37.240> to<01:16:37.680> develop<01:16:38.680> disease 01:16:39.450 --> 01:16:39.460 align:start position:0% Wonga which aims to develop disease 01:16:39.460 --> 01:16:43.050 align:start position:0% Wonga which aims to develop disease assist<01:16:39.940> them<01:16:40.120> to<01:16:40.230> verify<01:16:41.230> documents<01:16:42.190> and<01:16:42.370> the 01:16:43.050 --> 01:16:43.060 align:start position:0% assist them to verify documents and the 01:16:43.060 --> 01:16:45.960 align:start position:0% assist them to verify documents and the first<01:16:43.420> use<01:16:43.630> case<01:16:43.750> is<01:16:44.140> like<01:16:44.350> diploma<01:16:44.830> so<01:16:45.220> so<01:16:45.550> so 01:16:45.960 --> 01:16:45.970 align:start position:0% first use case is like diploma so so so 01:16:45.970 --> 01:16:48.120 align:start position:0% first use case is like diploma so so so we<01:16:46.120> can<01:16:46.330> have<01:16:46.540> the<01:16:46.720> digital<01:16:47.170> diploma<01:16:47.560> verified 01:16:48.120 --> 01:16:48.130 align:start position:0% we can have the digital diploma verified 01:16:48.130 --> 01:16:50.310 align:start position:0% we can have the digital diploma verified that<01:16:48.310> this<01:16:48.490> is<01:16:48.670> a<01:16:48.790> real<01:16:49.120> drama<01:16:49.720> and<01:16:49.990> all<01:16:50.110> the 01:16:50.310 --> 01:16:50.320 align:start position:0% that this is a real drama and all the 01:16:50.320 --> 01:16:54.930 align:start position:0% that this is a real drama and all the process<01:16:51.570> the<01:16:52.570> process<01:16:52.960> of<01:16:53.200> the<01:16:53.350> student<01:16:53.940> I'm 01:16:54.930 --> 01:16:54.940 align:start position:0% process the process of the student I'm 01:16:54.940 --> 01:16:57.180 align:start position:0% process the process of the student I'm for<01:16:55.240> supervising<01:16:55.690> the<01:16:55.960> work<01:16:56.350> of<01:16:56.560> these<01:16:56.950> two 01:16:57.180 --> 01:16:57.190 align:start position:0% for supervising the work of these two 01:16:57.190 --> 01:16:59.610 align:start position:0% for supervising the work of these two students<01:16:57.670> were<01:16:58.180> seeing<01:16:58.540> who<01:16:58.780> is<01:16:58.900> working<01:16:59.320> on 01:16:59.610 --> 01:16:59.620 align:start position:0% students were seeing who is working on 01:16:59.620 --> 01:17:01.110 align:start position:0% students were seeing who is working on the<01:16:59.770> actuary<01:17:00.160> and<01:17:00.310> the<01:17:00.400> implementation<01:17:01.030> of 01:17:01.110 --> 01:17:01.120 align:start position:0% the actuary and the implementation of 01:17:01.120 --> 01:17:04.800 align:start position:0% the actuary and the implementation of autonomy<01:17:01.630> calcium<01:17:02.020> swab<01:17:02.290> so<01:17:03.100> he<01:17:03.490> is<01:17:03.690> here<01:17:04.690> a 01:17:04.800 --> 01:17:04.810 align:start position:0% autonomy calcium swab so he is here a 01:17:04.810 --> 01:17:06.540 align:start position:0% autonomy calcium swab so he is here a second<01:17:05.260> comes<01:17:05.500> he<01:17:05.680> will<01:17:05.800> be<01:17:05.950> talking<01:17:06.220> with<01:17:06.400> me 01:17:06.540 --> 01:17:06.550 align:start position:0% second comes he will be talking with me 01:17:06.550 --> 01:17:07.800 align:start position:0% second comes he will be talking with me is<01:17:07.150> optimal 01:17:07.800 --> 01:17:07.810 align:start position:0% is optimal 01:17:07.810 --> 01:17:09.840 align:start position:0% is optimal another<01:17:08.440> your<01:17:08.710> who<01:17:08.920> is<01:17:08.950> focused<01:17:09.280> on<01:17:09.490> the<01:17:09.640> part 01:17:09.840 --> 01:17:09.850 align:start position:0% another your who is focused on the part 01:17:09.850 --> 01:17:13.550 align:start position:0% another your who is focused on the part of<01:17:09.940> their<01:17:10.120> contract<01:17:10.690> and<01:17:10.960> verification<01:17:11.760> so 01:17:13.550 --> 01:17:13.560 align:start position:0% of their contract and verification so 01:17:13.560 --> 01:17:17.250 align:start position:0% of their contract and verification so this<01:17:14.560> is<01:17:14.710> very<01:17:15.010> very<01:17:15.330> short<01:17:16.330> idea<01:17:16.840> of<01:17:17.050> what<01:17:17.230> I 01:17:17.250 --> 01:17:17.260 align:start position:0% this is very very short idea of what I 01:17:17.260 --> 01:17:22.479 align:start position:0% this is very very short idea of what I am<01:17:17.440> working<01:17:17.650> on<01:17:17.980> that<01:17:18.310> you<01:17:18.340> can<01:17:19.200> get<01:17:20.200> more<01:17:20.500> info 01:17:22.479 --> 01:17:22.489 align:start position:0% am working on that you can get more info 01:17:22.489 --> 01:17:26.110 align:start position:0% am working on that you can get more info so<01:17:22.970> basically<01:17:23.630> the<01:17:24.590> main<01:17:25.190> method<01:17:25.760> of<01:17:25.940> them 01:17:26.110 --> 01:17:26.120 align:start position:0% so basically the main method of them 01:17:26.120 --> 01:17:29.530 align:start position:0% so basically the main method of them simple<01:17:26.900> way<01:17:27.110> of<01:17:27.140> getting<01:17:28.300> redundancies<01:17:29.300> just 01:17:29.530 --> 01:17:29.540 align:start position:0% simple way of getting redundancies just 01:17:29.540 --> 01:17:32.680 align:start position:0% simple way of getting redundancies just copied<01:17:29.870> your<01:17:29.989> MacDonald<01:17:30.560> and<01:17:31.250> this<01:17:31.489> is<01:17:31.700> this 01:17:32.680 --> 01:17:32.690 align:start position:0% copied your MacDonald and this is this 01:17:32.690 --> 01:17:36.570 align:start position:0% copied your MacDonald and this is this is<01:17:32.900> a<01:17:33.160> very<01:17:34.160> popular<01:17:34.850> and<01:17:35.390> easy<01:17:35.540> way<01:17:35.780> of<01:17:35.810> just 01:17:36.570 --> 01:17:36.580 align:start position:0% is a very popular and easy way of just 01:17:36.580 --> 01:17:39.130 align:start position:0% is a very popular and easy way of just keep<01:17:37.580> replicating<01:17:37.820> data<01:17:38.420> so<01:17:38.810> this<01:17:38.989> is 01:17:39.130 --> 01:17:39.140 align:start position:0% keep replicating data so this is 01:17:39.140 --> 01:17:41.020 align:start position:0% keep replicating data so this is basically<01:17:39.500> the<01:17:39.739> man<01:17:39.950> from<01:17:40.190> behind<01:17:40.580> this<01:17:40.760> is 01:17:41.020 --> 01:17:41.030 align:start position:0% basically the man from behind this is 01:17:41.030 --> 01:17:41.950 align:start position:0% basically the man from behind this is the<01:17:41.239> more<01:17:41.480> the<01:17:41.630> better 01:17:41.950 --> 01:17:41.960 align:start position:0% the more the better 01:17:41.960 --> 01:17:44.020 align:start position:0% the more the better which<01:17:42.200> do<01:17:42.320> you<01:17:42.410> have<01:17:42.590> more<01:17:42.920> more<01:17:43.340> replicas<01:17:44.000> you 01:17:44.020 --> 01:17:44.030 align:start position:0% which do you have more more replicas you 01:17:44.030 --> 01:17:46.870 align:start position:0% which do you have more more replicas you can<01:17:44.480> tolerate<01:17:44.660> more<01:17:44.930> crazy<01:17:45.470> machines<01:17:45.950> if<01:17:46.190> the 01:17:46.870 --> 01:17:46.880 align:start position:0% can tolerate more crazy machines if the 01:17:46.880 --> 01:17:49.000 align:start position:0% can tolerate more crazy machines if the network<01:17:47.060> is<01:17:47.390> not<01:17:47.450> good<01:17:47.840> the<01:17:48.080> nodes<01:17:48.320> disappear 01:17:49.000 --> 01:17:49.010 align:start position:0% network is not good the nodes disappear 01:17:49.010 --> 01:17:51.430 align:start position:0% network is not good the nodes disappear so<01:17:49.340> you<01:17:49.370> can<01:17:49.790> still<01:17:50.030> save<01:17:50.690> your<01:17:50.840> data<01:17:51.050> recover 01:17:51.430 --> 01:17:51.440 align:start position:0% so you can still save your data recover 01:17:51.440 --> 01:17:54.490 align:start position:0% so you can still save your data recover your<01:17:51.650> file<01:17:51.920> but<01:17:52.700> this<01:17:53.090> has<01:17:53.500> disadvantage 01:17:54.490 --> 01:17:54.500 align:start position:0% your file but this has disadvantage 01:17:54.500 --> 01:17:58.630 align:start position:0% your file but this has disadvantage which<01:17:54.710> is<01:17:54.890> the<01:17:55.130> space<01:17:55.520> overhead<01:17:56.739> then<01:17:57.739> we<01:17:58.430> have 01:17:58.630 --> 01:17:58.640 align:start position:0% which is the space overhead then we have 01:17:58.640 --> 01:18:01.660 align:start position:0% which is the space overhead then we have another<01:17:59.060> approach<01:17:59.720> to<01:18:00.130> achieve<01:18:01.130> redundancy 01:18:01.660 --> 01:18:01.670 align:start position:0% another approach to achieve redundancy 01:18:01.670 --> 01:18:03.880 align:start position:0% another approach to achieve redundancy which<01:18:01.940> is<01:18:02.090> with<01:18:02.630> your<01:18:02.750> racial<01:18:02.960> coding<01:18:03.350> spacing 01:18:03.880 --> 01:18:03.890 align:start position:0% which is with your racial coding spacing 01:18:03.890 --> 01:18:06.160 align:start position:0% which is with your racial coding spacing the<01:18:04.010> MDS<01:18:04.489> codes<01:18:04.850> or<01:18:05.150> read<01:18:05.390> sort<01:18:05.660> of<01:18:05.720> accounts 01:18:06.160 --> 01:18:06.170 align:start position:0% the MDS codes or read sort of accounts 01:18:06.170 --> 01:18:09.400 align:start position:0% the MDS codes or read sort of accounts which<01:18:06.890> have<01:18:07.250> the<01:18:08.060> mantra<01:18:08.510> behind<01:18:08.870> that<01:18:09.050> is<01:18:09.200> the 01:18:09.400 --> 01:18:09.410 align:start position:0% which have the mantra behind that is the 01:18:09.410 --> 01:18:11.320 align:start position:0% which have the mantra behind that is the less<01:18:09.770> the<01:18:09.950> better<01:18:10.100> because<01:18:10.460> you<01:18:10.760> want<01:18:10.940> to<01:18:11.000> save 01:18:11.320 --> 01:18:11.330 align:start position:0% less the better because you want to save 01:18:11.330 --> 01:18:16.479 align:start position:0% less the better because you want to save a<01:18:11.360> space<01:18:11.870> and<01:18:12.410> buy<01:18:13.450> it<01:18:14.620> here<01:18:15.620> a<01:18:15.770> circle<01:18:16.190> in<01:18:16.310> your 01:18:16.479 --> 01:18:16.489 align:start position:0% a space and buy it here a circle in your 01:18:16.489 --> 01:18:18.910 align:start position:0% a space and buy it here a circle in your data<01:18:16.730> but<01:18:17.030> basically<01:18:17.480> you<01:18:17.720> you<01:18:18.110> do<01:18:18.350> is<01:18:18.590> like 01:18:18.910 --> 01:18:18.920 align:start position:0% data but basically you you do is like 01:18:18.920 --> 01:18:21.550 align:start position:0% data but basically you you do is like served<01:18:19.790> in<01:18:19.940> your<01:18:20.060> file<01:18:20.420> and<01:18:20.660> then<01:18:20.840> creating 01:18:21.550 --> 01:18:21.560 align:start position:0% served in your file and then creating 01:18:21.560 --> 01:18:25.330 align:start position:0% served in your file and then creating some<01:18:21.770> extra<01:18:22.340> blocks<01:18:22.610> but<01:18:23.330> now<01:18:23.540> you<01:18:24.080> use<01:18:24.650> less 01:18:25.330 --> 01:18:25.340 align:start position:0% some extra blocks but now you use less 01:18:25.340 --> 01:18:27.940 align:start position:0% some extra blocks but now you use less space<01:18:25.760> of<01:18:26.060> a<01:18:26.150> fat<01:18:26.420> but<01:18:27.140> the<01:18:27.260> problem<01:18:27.680> with<01:18:27.800> is 01:18:27.940 --> 01:18:27.950 align:start position:0% space of a fat but the problem with is 01:18:27.950 --> 01:18:30.880 align:start position:0% space of a fat but the problem with is with<01:18:28.400> this<01:18:28.550> method<01:18:29.030> is<01:18:29.180> that<01:18:29.450> man<01:18:30.140> Dana's<01:18:30.650> is 01:18:30.880 --> 01:18:30.890 align:start position:0% with this method is that man Dana's is 01:18:30.890 --> 01:18:33.340 align:start position:0% with this method is that man Dana's is very<01:18:31.250> hard<01:18:31.550> and<01:18:31.760> many<01:18:32.150> peer-to-peer<01:18:32.510> systems 01:18:33.340 --> 01:18:33.350 align:start position:0% very hard and many peer-to-peer systems 01:18:33.350 --> 01:18:35.740 align:start position:0% very hard and many peer-to-peer systems failed<01:18:33.770> because<01:18:34.160> of<01:18:34.370> this<01:18:34.730> in<01:18:35.300> the<01:18:35.420> sense<01:18:35.570> of 01:18:35.740 --> 01:18:35.750 align:start position:0% failed because of this in the sense of 01:18:35.750 --> 01:18:38.940 align:start position:0% failed because of this in the sense of faith<01:18:36.110> pay<01:18:36.440> to<01:18:36.610> protect<01:18:37.610> the<01:18:37.760> data<01:18:37.930> because 01:18:38.940 --> 01:18:38.950 align:start position:0% faith pay to protect the data because 01:18:38.950 --> 01:18:42.280 align:start position:0% faith pay to protect the data because you<01:18:39.950> can<01:18:40.190> you<01:18:40.460> can<01:18:40.730> create<01:18:41.450> this<01:18:41.720> redundancy 01:18:42.280 --> 01:18:42.290 align:start position:0% you can you can create this redundancy 01:18:42.290 --> 01:18:44.650 align:start position:0% you can you can create this redundancy at<01:18:42.440> the<01:18:42.530> very<01:18:42.710> beginning<01:18:42.950> but<01:18:43.400> then<01:18:43.730> it's<01:18:44.390> very 01:18:44.650 --> 01:18:44.660 align:start position:0% at the very beginning but then it's very 01:18:44.660 --> 01:18:46.690 align:start position:0% at the very beginning but then it's very common<01:18:45.170> thing<01:18:45.380> to<01:18:45.560> keep<01:18:45.890> well<01:18:46.250> when<01:18:46.520> they 01:18:46.690 --> 01:18:46.700 align:start position:0% common thing to keep well when they 01:18:46.700 --> 01:18:49.300 align:start position:0% common thing to keep well when they noticed<01:18:47.180> are<01:18:47.360> disappearing<01:18:47.810> when<01:18:48.710> when<01:18:49.160> there 01:18:49.300 --> 01:18:49.310 align:start position:0% noticed are disappearing when when there 01:18:49.310 --> 01:18:50.500 align:start position:0% noticed are disappearing when when there is<01:18:49.489> a<01:18:49.520> failure 01:18:50.500 --> 01:18:50.510 align:start position:0% is a failure 01:18:50.510 --> 01:18:53.050 align:start position:0% is a failure Devon<01:18:51.230> Tanous<01:18:51.650> takes<01:18:51.950> a<01:18:52.160> lot<01:18:52.310> of<01:18:52.340> anguish<01:18:52.730> and 01:18:53.050 --> 01:18:53.060 align:start position:0% Devon Tanous takes a lot of anguish and 01:18:53.060 --> 01:18:55.660 align:start position:0% Devon Tanous takes a lot of anguish and you<01:18:53.239> and<01:18:53.540> also<01:18:53.810> it<01:18:54.230> requires<01:18:54.440> that<01:18:55.160> many<01:18:55.430> other 01:18:55.660 --> 01:18:55.670 align:start position:0% you and also it requires that many other 01:18:55.670 --> 01:18:58.330 align:start position:0% you and also it requires that many other nodes<01:18:56.060> are<01:18:56.750> available<01:18:57.530> when<01:18:57.770> you<01:18:57.920> need<01:18:58.070> to<01:18:58.190> do 01:18:58.330 --> 01:18:58.340 align:start position:0% nodes are available when you need to do 01:18:58.340 --> 01:19:01.750 align:start position:0% nodes are available when you need to do the<01:18:58.489> repair<01:18:59.320> so<01:19:00.320> I'm<01:19:00.650> working<01:19:01.280> that's<01:19:01.520> what<01:19:01.730> I 01:19:01.750 --> 01:19:01.760 align:start position:0% the repair so I'm working that's what I 01:19:01.760 --> 01:19:04.540 align:start position:0% the repair so I'm working that's what I developed<01:19:02.330> in<01:19:02.480> my<01:19:02.720> PhD<01:19:02.960> on<01:19:03.470> Allen<01:19:04.100> recommend 01:19:04.540 --> 01:19:04.550 align:start position:0% developed in my PhD on Allen recommend 01:19:04.550 --> 01:19:06.670 align:start position:0% developed in my PhD on Allen recommend course<01:19:04.790> or<01:19:05.030> in<01:19:05.210> tournament<01:19:05.660> cause<01:19:05.810> the<01:19:06.440> idea 01:19:06.670 --> 01:19:06.680 align:start position:0% course or in tournament cause the idea 01:19:06.680 --> 01:19:08.590 align:start position:0% course or in tournament cause the idea of<01:19:06.800> entanglement<01:19:07.250> course<01:19:07.610> is<01:19:07.850> that<01:19:08.030> each<01:19:08.300> time 01:19:08.590 --> 01:19:08.600 align:start position:0% of entanglement course is that each time 01:19:08.600 --> 01:19:12.640 align:start position:0% of entanglement course is that each time you<01:19:08.630> add<01:19:08.960> a<01:19:08.989> file<01:19:09.890> to<01:19:09.920> the<01:19:10.340> system<01:19:10.820> you<01:19:11.650> again 01:19:12.640 --> 01:19:12.650 align:start position:0% you add a file to the system you again 01:19:12.650 --> 01:19:14.440 align:start position:0% you add a file to the system you again you<01:19:12.860> charge<01:19:13.220> the<01:19:13.430> data<01:19:13.700> so<01:19:13.880> you<01:19:13.940> have<01:19:14.210> like 01:19:14.440 --> 01:19:14.450 align:start position:0% you charge the data so you have like 01:19:14.450 --> 01:19:16.910 align:start position:0% you charge the data so you have like blocks<01:19:14.810> of<01:19:15.140> of<01:19:15.380> these<01:19:15.680> rights<01:19:15.950> and 01:19:16.910 --> 01:19:16.920 align:start position:0% blocks of of these rights and 01:19:16.920 --> 01:19:19.220 align:start position:0% blocks of of these rights and you<01:19:16.980> exert<01:19:17.610> these<01:19:17.850> blocks<01:19:18.179> with<01:19:18.570> other<01:19:18.810> blocks 01:19:19.220 --> 01:19:19.230 align:start position:0% you exert these blocks with other blocks 01:19:19.230 --> 01:19:21.229 align:start position:0% you exert these blocks with other blocks that<01:19:19.350> are<01:19:19.410> in<01:19:19.650> the<01:19:19.770> system<01:19:19.980> creating<01:19:20.760> a<01:19:20.850> bottom 01:19:21.229 --> 01:19:21.239 align:start position:0% that are in the system creating a bottom 01:19:21.239 --> 01:19:23.660 align:start position:0% that are in the system creating a bottom creating<01:19:21.780> like<01:19:21.980> multiple<01:19:22.980> chains<01:19:23.340> of 01:19:23.660 --> 01:19:23.670 align:start position:0% creating like multiple chains of 01:19:23.670 --> 01:19:26.630 align:start position:0% creating like multiple chains of real-time<01:19:24.390> data<01:19:24.630> and<01:19:25.350> this<01:19:26.010> chase<01:19:26.340> are 01:19:26.630 --> 01:19:26.640 align:start position:0% real-time data and this chase are 01:19:26.640 --> 01:19:29.630 align:start position:0% real-time data and this chase are intertwined<01:19:27.210> together<01:19:27.920> creating<01:19:28.920> a<01:19:29.040> larger 01:19:29.630 --> 01:19:29.640 align:start position:0% intertwined together creating a larger 01:19:29.640 --> 01:19:31.939 align:start position:0% intertwined together creating a larger structure<01:19:30.060> of<01:19:30.330> a<01:19:30.449> conical<01:19:30.870> lattice<01:19:31.230> where 01:19:31.939 --> 01:19:31.949 align:start position:0% structure of a conical lattice where 01:19:31.949 --> 01:19:35.120 align:start position:0% structure of a conical lattice where this<01:19:32.190> lot<01:19:32.489> is<01:19:32.699> what<01:19:33.060> creates<01:19:33.750> many<01:19:34.620> different 01:19:35.120 --> 01:19:35.130 align:start position:0% this lot is what creates many different 01:19:35.130 --> 01:19:37.220 align:start position:0% this lot is what creates many different ways<01:19:35.370> many<01:19:35.699> different<01:19:36.239> paths<01:19:36.449> where<01:19:36.780> you<01:19:37.020> can 01:19:37.220 --> 01:19:37.230 align:start position:0% ways many different paths where you can 01:19:37.230 --> 01:19:40.310 align:start position:0% ways many different paths where you can recover<01:19:37.620> this<01:19:37.920> data<01:19:38.250> and<01:19:39.090> by<01:19:39.449> doing<01:19:39.719> this<01:19:39.989> in<01:19:40.230> a 01:19:40.310 --> 01:19:40.320 align:start position:0% recover this data and by doing this in a 01:19:40.320 --> 01:19:42.770 align:start position:0% recover this data and by doing this in a very<01:19:40.710> efficient<01:19:41.160> way<01:19:41.190> that<01:19:41.670> and<01:19:41.850> so<01:19:42.239> every 01:19:42.770 --> 01:19:42.780 align:start position:0% very efficient way that and so every 01:19:42.780 --> 01:19:44.689 align:start position:0% very efficient way that and so every time<01:19:42.870> you<01:19:43.170> have<01:19:43.410> a<01:19:43.440> failure<01:19:43.800> a<01:19:43.949> single<01:19:44.370> failure 01:19:44.689 --> 01:19:44.699 align:start position:0% time you have a failure a single failure 01:19:44.699 --> 01:19:47.090 align:start position:0% time you have a failure a single failure you<01:19:44.910> only<01:19:45.150> need<01:19:45.420> two<01:19:46.020> blocks<01:19:46.320> to<01:19:46.590> recover<01:19:46.949> the 01:19:47.090 --> 01:19:47.100 align:start position:0% you only need two blocks to recover the 01:19:47.100 --> 01:19:51.350 align:start position:0% you only need two blocks to recover the data<01:19:47.280> and<01:19:47.730> then<01:19:48.090> you<01:19:48.210> can<01:19:48.480> do<01:19:49.699> the<01:19:50.699> repairs<01:19:51.120> in 01:19:51.350 --> 01:19:51.360 align:start position:0% data and then you can do the repairs in 01:19:51.360 --> 01:19:53.330 align:start position:0% data and then you can do the repairs in parallel<01:19:51.840> because<01:19:52.020> this<01:19:52.410> lattice<01:19:52.920> you<01:19:53.160> can 01:19:53.330 --> 01:19:53.340 align:start position:0% parallel because this lattice you can 01:19:53.340 --> 01:19:55.100 align:start position:0% parallel because this lattice you can you<01:19:53.520> can<01:19:53.670> do<01:19:53.760> some<01:19:53.969> repairs<01:19:54.360> and<01:19:54.630> repair<01:19:54.929> some 01:19:55.100 --> 01:19:55.110 align:start position:0% you can do some repairs and repair some 01:19:55.110 --> 01:19:56.540 align:start position:0% you can do some repairs and repair some blocks<01:19:55.320> that<01:19:55.469> are<01:19:55.620> missing<01:19:55.800> here<01:19:56.160> or<01:19:56.370> some 01:19:56.540 --> 01:19:56.550 align:start position:0% blocks that are missing here or some 01:19:56.550 --> 01:19:58.010 align:start position:0% blocks that are missing here or some some<01:19:56.850> blocks<01:19:57.030> that<01:19:57.150> are<01:19:57.300> missing<01:19:57.540> here<01:19:57.750> always 01:19:58.010 --> 01:19:58.020 align:start position:0% some blocks that are missing here always 01:19:58.020 --> 01:20:01.010 align:start position:0% some blocks that are missing here always by<01:19:58.350> reading<01:19:59.280> two<01:19:59.429> blocks<01:19:59.699> and<01:19:59.969> only<01:20:00.239> doing<01:20:00.840> X 01:20:01.010 --> 01:20:01.020 align:start position:0% by reading two blocks and only doing X 01:20:01.020 --> 01:20:06.709 align:start position:0% by reading two blocks and only doing X or<01:20:01.290> that's<01:20:01.679> also<01:20:04.310> mentioned<01:20:05.310> these<01:20:06.150> codes<01:20:06.480> are 01:20:06.709 --> 01:20:06.719 align:start position:0% or that's also mentioned these codes are 01:20:06.719 --> 01:20:09.110 align:start position:0% or that's also mentioned these codes are normally<01:20:07.320> the<01:20:07.560> aromatic<01:20:08.070> suffix<01:20:08.550> girls<01:20:08.940> are 01:20:09.110 --> 01:20:09.120 align:start position:0% normally the aromatic suffix girls are 01:20:09.120 --> 01:20:11.000 align:start position:0% normally the aromatic suffix girls are are<01:20:09.330> based<01:20:09.570> on<01:20:09.840> karma<01:20:10.260> fields<01:20:10.650> which<01:20:10.830> is<01:20:10.980> a 01:20:11.000 --> 01:20:11.010 align:start position:0% are based on karma fields which is a 01:20:11.010 --> 01:20:13.070 align:start position:0% are based on karma fields which is a little<01:20:11.370> complicated<01:20:11.580> so<01:20:11.850> so<01:20:12.480> to<01:20:12.540> make<01:20:12.750> it<01:20:12.780> more 01:20:13.070 --> 01:20:13.080 align:start position:0% little complicated so so to make it more 01:20:13.080 --> 01:20:14.750 align:start position:0% little complicated so so to make it more efficient<01:20:13.560> you<01:20:13.650> have<01:20:13.830> to<01:20:13.949> have<01:20:14.100> a<01:20:14.130> team<01:20:14.520> say 01:20:14.750 --> 01:20:14.760 align:start position:0% efficient you have to have a team say 01:20:14.760 --> 01:20:16.820 align:start position:0% efficient you have to have a team say show<01:20:15.090> some<01:20:15.360> some<01:20:15.660> of<01:20:15.840> the<01:20:15.960> incisions<01:20:16.410> are<01:20:16.530> so 01:20:16.820 --> 01:20:16.830 align:start position:0% show some some of the incisions are so 01:20:16.830 --> 01:20:20.600 align:start position:0% show some some of the incisions are so that<01:20:17.040> their<01:20:17.550> patterns<01:20:18.090> become<01:20:18.330> the<01:20:18.660> center<01:20:19.610> so 01:20:20.600 --> 01:20:20.610 align:start position:0% that their patterns become the center so 01:20:20.610 --> 01:20:22.580 align:start position:0% that their patterns become the center so this<01:20:20.790> this<01:20:21.120> was<01:20:21.390> a<01:20:21.420> very<01:20:21.810> simple<01:20:22.230> to<01:20:22.350> implement 01:20:22.580 --> 01:20:22.590 align:start position:0% this this was a very simple to implement 01:20:22.590 --> 01:20:27.290 align:start position:0% this this was a very simple to implement and<01:20:24.080> facilitate<01:20:25.080> their<01:20:26.070> repairs<01:20:26.699> and<01:20:26.969> the 01:20:27.290 --> 01:20:27.300 align:start position:0% and facilitate their repairs and the 01:20:27.300 --> 01:20:29.689 align:start position:0% and facilitate their repairs and the space<01:20:27.570> requirements<01:20:28.140> and<01:20:28.500> also<01:20:29.160> can<01:20:29.400> generate 01:20:29.689 --> 01:20:29.699 align:start position:0% space requirements and also can generate 01:20:29.699 --> 01:20:32.689 align:start position:0% space requirements and also can generate a<01:20:30.120> lot<01:20:30.660> of<01:20:30.719> other<01:20:31.080> failures<01:20:31.650> and<01:20:31.949> we<01:20:32.219> show<01:20:32.489> that 01:20:32.689 --> 01:20:32.699 align:start position:0% a lot of other failures and we show that 01:20:32.699 --> 01:20:34.970 align:start position:0% a lot of other failures and we show that instant<01:20:33.120> assistance<01:20:33.570> is<01:20:34.050> superior<01:20:34.469> than 01:20:34.970 --> 01:20:34.980 align:start position:0% instant assistance is superior than 01:20:34.980 --> 01:20:38.870 align:start position:0% instant assistance is superior than average<01:20:35.610> Salomon<01:20:36.380> so<01:20:37.380> you<01:20:38.219> will<01:20:38.400> get<01:20:38.580> worried 01:20:38.870 --> 01:20:38.880 align:start position:0% average Salomon so you will get worried 01:20:38.880 --> 01:20:41.360 align:start position:0% average Salomon so you will get worried for<01:20:39.239> this<01:20:40.080> afternoon<01:20:40.620> if<01:20:40.830> you<01:20:40.980> want<01:20:41.219> you<01:20:41.340> have 01:20:41.360 --> 01:20:41.370 align:start position:0% for this afternoon if you want you have 01:20:41.370 --> 01:20:44.080 align:start position:0% for this afternoon if you want you have to<01:20:41.820> swamp<01:20:42.449> recap<01:20:42.810> such<01:20:43.020> as<01:20:43.199> will<01:20:43.410> mr.<01:20:43.560> about 01:20:44.080 --> 01:20:44.090 align:start position:0% to swamp recap such as will mr. about 01:20:44.090 --> 01:20:47.209 align:start position:0% to swamp recap such as will mr. about former<01:20:45.090> cadet<01:20:45.300> autonomous<01:20:46.140> and<01:20:46.530> though<01:20:46.890> you 01:20:47.209 --> 01:20:47.219 align:start position:0% former cadet autonomous and though you 01:20:47.219 --> 01:20:50.810 align:start position:0% former cadet autonomous and though you can<01:20:47.400> also<01:20:47.810> read<01:20:48.810> the<01:20:48.840> last<01:20:49.500> paper<01:20:49.830> to<01:20:50.610> publish 01:20:50.810 --> 01:20:50.820 align:start position:0% can also read the last paper to publish 01:20:50.820 --> 01:20:55.820 align:start position:0% can also read the last paper to publish the<01:20:51.120> PSN<01:20:51.660> and<01:20:52.969> then<01:20:53.969> I<01:20:54.469> want<01:20:55.469> to<01:20:55.590> mention 01:20:55.820 --> 01:20:55.830 align:start position:0% the PSN and then I want to mention 01:20:55.830 --> 01:21:00.410 align:start position:0% the PSN and then I want to mention something<01:20:56.900> I'm<01:20:57.900> working<01:20:58.679> on<01:20:59.130> the<01:20:59.429> and<01:21:00.000> a 01:21:00.410 --> 01:21:00.420 align:start position:0% something I'm working on the and a 01:21:00.420 --> 01:21:03.229 align:start position:0% something I'm working on the and a proposal<01:21:00.840> a<01:21:01.110> workshop<01:21:01.530> proposal<01:21:02.190> to<01:21:02.850> submit 01:21:03.229 --> 01:21:03.239 align:start position:0% proposal a workshop proposal to submit 01:21:03.239 --> 01:21:07.700 align:start position:0% proposal a workshop proposal to submit to<01:21:03.420> a<01:21:03.449> very<01:21:04.100> top<01:21:05.100> confer<01:21:05.460> upon<01:21:05.550> systems<01:21:06.710> this 01:21:07.700 --> 01:21:07.710 align:start position:0% to a very top confer upon systems this 01:21:07.710 --> 01:21:11.270 align:start position:0% to a very top confer upon systems this conference<01:21:09.170> Swiss<01:21:10.170> about<01:21:10.440> systems<01:21:10.949> but<01:21:11.100> in 01:21:11.270 --> 01:21:11.280 align:start position:0% conference Swiss about systems but in 01:21:11.280 --> 01:21:13.130 align:start position:0% conference Swiss about systems but in Sheridan<01:21:11.880> I'd<01:21:12.120> noticed<01:21:12.510> that<01:21:12.719> there's<01:21:12.960> a<01:21:13.110> lot 01:21:13.130 --> 01:21:13.140 align:start position:0% Sheridan I'd noticed that there's a lot 01:21:13.140 --> 01:21:16.580 align:start position:0% Sheridan I'd noticed that there's a lot of<01:21:13.320> focus<01:21:13.620> on<01:21:13.949> centralized<01:21:14.850> systems<01:21:15.360> but<01:21:16.110> it's 01:21:16.580 --> 01:21:16.590 align:start position:0% of focus on centralized systems but it's 01:21:16.590 --> 01:21:19.570 align:start position:0% of focus on centralized systems but it's a<01:21:16.739> system<01:21:16.890> conference<01:21:17.520> so<01:21:17.790> I<01:21:18.090> would<01:21:18.929> like<01:21:19.080> to 01:21:19.570 --> 01:21:19.580 align:start position:0% a system conference so I would like to 01:21:19.580 --> 01:21:22.450 align:start position:0% a system conference so I would like to discuss<01:21:20.580> more<01:21:20.940> all<01:21:21.300> these<01:21:21.719> top 01:21:22.450 --> 01:21:22.460 align:start position:0% discuss more all these top 01:21:22.460 --> 01:21:25.040 align:start position:0% discuss more all these top personalized<01:21:23.460> in<01:21:24.000> also<01:21:24.510> in<01:21:24.600> the<01:21:24.690> academic 01:21:25.040 --> 01:21:25.050 align:start position:0% personalized in also in the academic 01:21:25.050 --> 01:21:27.110 align:start position:0% personalized in also in the academic environment<01:21:25.200> why<01:21:25.890> because<01:21:26.370> you<01:21:26.790> know<01:21:26.910> in<01:21:27.090> the 01:21:27.110 --> 01:21:27.120 align:start position:0% environment why because you know in the 01:21:27.120 --> 01:21:29.690 align:start position:0% environment why because you know in the to<01:21:27.420> sauce<01:21:27.630> it<01:21:27.930> could<01:21:27.960> be<01:21:28.200> between<01:21:28.550> $2,000<01:21:29.550> and 01:21:29.690 --> 01:21:29.700 align:start position:0% to sauce it could be between $2,000 and 01:21:29.700 --> 01:21:32.840 align:start position:0% to sauce it could be between $2,000 and this<01:21:30.270> is<01:21:30.420> all<01:21:30.570> sonic<01:21:30.780> man<01:21:31.340> there<01:21:32.340> was<01:21:32.430> a<01:21:32.580> lot<01:21:32.610> of 01:21:32.840 --> 01:21:32.850 align:start position:0% this is all sonic man there was a lot of 01:21:32.850 --> 01:21:34.880 align:start position:0% this is all sonic man there was a lot of research<01:21:33.360> and<01:21:33.480> there<01:21:33.630> was<01:21:33.750> very<01:21:34.080> very<01:21:34.470> serious 01:21:34.880 --> 01:21:34.890 align:start position:0% research and there was very very serious 01:21:34.890 --> 01:21:37.340 align:start position:0% research and there was very very serious research<01:21:35.070> of<01:21:35.430> European<01:21:35.940> systems<01:21:36.330> but<01:21:36.900> on<01:21:37.110> how 01:21:37.340 --> 01:21:37.350 align:start position:0% research of European systems but on how 01:21:37.350 --> 01:21:41.390 align:start position:0% research of European systems but on how this<01:21:39.410> disappear<01:21:40.410> immediately<01:21:40.739> change<01:21:41.310> the 01:21:41.390 --> 01:21:41.400 align:start position:0% this disappear immediately change the 01:21:41.400 --> 01:21:44.060 align:start position:0% this disappear immediately change the name<01:21:41.730> that<01:21:42.239> was<01:21:42.450> not<01:21:42.660> cool<01:21:43.110> to<01:21:43.650> talk<01:21:43.920> about 01:21:44.060 --> 01:21:44.070 align:start position:0% name that was not cool to talk about 01:21:44.070 --> 01:21:45.920 align:start position:0% name that was not cool to talk about peer<01:21:44.400> to<01:21:44.550> peer<01:21:44.730> because<01:21:45.090> it<01:21:45.239> was<01:21:45.360> a<01:21:45.390> city<01:21:45.780> with 01:21:45.920 --> 01:21:45.930 align:start position:0% peer to peer because it was a city with 01:21:45.930 --> 01:21:49.729 align:start position:0% peer to peer because it was a city with with<01:21:46.850> illegal<01:21:47.850> networks<01:21:48.450> or<01:21:48.810> elegant<01:21:49.440> allowed 01:21:49.729 --> 01:21:49.739 align:start position:0% with illegal networks or elegant allowed 01:21:49.739 --> 01:21:52.880 align:start position:0% with illegal networks or elegant allowed to<01:21:50.190> the<01:21:50.310> lasso<01:21:50.790> and<01:21:50.970> and<01:21:51.660> then<01:21:51.840> I<01:21:52.140> mean<01:21:52.680> there's 01:21:52.880 --> 01:21:52.890 align:start position:0% to the lasso and and then I mean there's 01:21:52.890 --> 01:21:54.830 align:start position:0% to the lasso and and then I mean there's a<01:21:52.980> steel<01:21:53.340> research<01:21:53.730> of<01:21:53.940> course<01:21:54.120> in<01:21:54.390> Europe<01:21:54.510> er 01:21:54.830 --> 01:21:54.840 align:start position:0% a steel research of course in Europe er 01:21:54.840 --> 01:21:57.590 align:start position:0% a steel research of course in Europe er in<01:21:54.960> the<01:21:55.080> academia<01:21:55.470> but<01:21:56.000> and<01:21:57.000> it<01:21:57.180> also<01:21:57.360> takes 01:21:57.590 --> 01:21:57.600 align:start position:0% in the academia but and it also takes 01:21:57.600 --> 01:22:01.640 align:start position:0% in the academia but and it also takes different<01:21:58.050> names<01:21:58.489> but<01:21:59.489> not<01:22:00.480> as<01:22:00.720> much<01:22:01.080> as<01:22:01.350> I 01:22:01.640 --> 01:22:01.650 align:start position:0% different names but not as much as I 01:22:01.650 --> 01:22:04.250 align:start position:0% different names but not as much as I would<01:22:01.860> like<01:22:02.100> to<01:22:02.310> at<01:22:02.430> listen<01:22:02.820> and<01:22:03.480> also<01:22:03.900> we<01:22:04.050> have 01:22:04.250 --> 01:22:04.260 align:start position:0% would like to at listen and also we have 01:22:04.260 --> 01:22:06.290 align:start position:0% would like to at listen and also we have the<01:22:04.350> problem<01:22:04.830> probably<01:22:05.100> researchers<01:22:05.940> that<01:22:06.090> we 01:22:06.290 --> 01:22:06.300 align:start position:0% the problem probably researchers that we 01:22:06.300 --> 01:22:08.180 align:start position:0% the problem probably researchers that we are<01:22:06.450> interested<01:22:06.960> in<01:22:07.080> to<01:22:07.230> in<01:22:07.350> search<01:22:07.680> of<01:22:07.710> these 01:22:08.180 --> 01:22:08.190 align:start position:0% are interested in to in search of these 01:22:08.190 --> 01:22:10.580 align:start position:0% are interested in to in search of these different<01:22:08.850> systems<01:22:09.000> it's<01:22:09.690> very<01:22:10.020> hard<01:22:10.230> to<01:22:10.320> I 01:22:10.580 --> 01:22:10.590 align:start position:0% different systems it's very hard to I 01:22:10.590 --> 01:22:12.260 align:start position:0% different systems it's very hard to I had<01:22:10.830> to<01:22:10.860> attend<01:22:11.400> this<01:22:11.550> kind<01:22:11.730> of<01:22:11.850> conference 01:22:12.260 --> 01:22:12.270 align:start position:0% had to attend this kind of conference 01:22:12.270 --> 01:22:13.729 align:start position:0% had to attend this kind of conference because<01:22:12.660> they<01:22:12.780> are<01:22:12.870> developing<01:22:13.320> conference 01:22:13.729 --> 01:22:13.739 align:start position:0% because they are developing conference 01:22:13.739 --> 01:22:17.060 align:start position:0% because they are developing conference and<01:22:13.920> when<01:22:14.040> you<01:22:14.130> have<01:22:14.360> funding<01:22:15.360> it's<01:22:16.170> only<01:22:16.410> for 01:22:17.060 --> 01:22:17.070 align:start position:0% and when you have funding it's only for 01:22:17.070 --> 01:22:18.740 align:start position:0% and when you have funding it's only for academic<01:22:17.760> conference<01:22:18.150> because<01:22:18.300> we<01:22:18.510> need<01:22:18.660> to 01:22:18.740 --> 01:22:18.750 align:start position:0% academic conference because we need to 01:22:18.750 --> 01:22:23.600 align:start position:0% academic conference because we need to publish<01:22:19.220> so<01:22:20.220> it's<01:22:20.420> my<01:22:21.420> aim<01:22:21.600> is<01:22:21.840> like<01:22:22.080> to<01:22:22.470> to<01:22:23.280> mix 01:22:23.600 --> 01:22:23.610 align:start position:0% publish so it's my aim is like to to mix 01:22:23.610 --> 01:22:26.840 align:start position:0% publish so it's my aim is like to to mix but<01:22:23.970> both<01:22:24.360> communities<01:22:25.020> to<01:22:25.380> buy<01:22:26.070> in<01:22:26.670> this 01:22:26.840 --> 01:22:26.850 align:start position:0% but both communities to buy in this 01:22:26.850 --> 01:22:29.180 align:start position:0% but both communities to buy in this workshop<01:22:27.390> where<01:22:27.630> the<01:22:28.620> purpose<01:22:28.920> of<01:22:29.040> this 01:22:29.180 --> 01:22:29.190 align:start position:0% workshop where the purpose of this 01:22:29.190 --> 01:22:31.040 align:start position:0% workshop where the purpose of this workshop<01:22:29.460> is<01:22:29.820> to<01:22:30.000> have<01:22:30.180> some<01:22:30.390> keynote 01:22:31.040 --> 01:22:31.050 align:start position:0% workshop is to have some keynote 01:22:31.050 --> 01:22:33.170 align:start position:0% workshop is to have some keynote speakers<01:22:31.620> from<01:22:31.860> fraud<01:22:32.280> academic<01:22:32.790> units<01:22:33.090> a 01:22:33.170 --> 01:22:33.180 align:start position:0% speakers from fraud academic units a 01:22:33.180 --> 01:22:34.940 align:start position:0% speakers from fraud academic units a speaker<01:22:33.420> from<01:22:33.630> the<01:22:33.750> decentralized<01:22:34.200> community 01:22:34.940 --> 01:22:34.950 align:start position:0% speaker from the decentralized community 01:22:34.950 --> 01:22:37.940 align:start position:0% speaker from the decentralized community also<01:22:35.700> have<01:22:35.940> son<01:22:36.239> for<01:22:36.630> I<01:22:36.989> know<01:22:37.050> that<01:22:37.440> this<01:22:37.710> and 01:22:37.940 --> 01:22:37.950 align:start position:0% also have son for I know that this and 01:22:37.950 --> 01:22:39.830 align:start position:0% also have son for I know that this and that<01:22:38.030> people<01:22:39.030> from<01:22:39.150> the<01:22:39.270> community<01:22:39.660> they 01:22:39.830 --> 01:22:39.840 align:start position:0% that people from the community they 01:22:39.840 --> 01:22:42.260 align:start position:0% that people from the community they don't<01:22:39.950> polish<01:22:40.950> the<01:22:41.310> dog<01:22:41.489> have<01:22:41.640> the<01:22:41.880> time<01:22:42.090> to 01:22:42.260 --> 01:22:42.270 align:start position:0% don't polish the dog have the time to 01:22:42.270 --> 01:22:44.590 align:start position:0% don't polish the dog have the time to publish<01:22:42.450> an<01:22:42.720> academic<01:22:43.140> paper<01:22:43.320> but<01:22:43.770> but<01:22:44.130> it 01:22:44.590 --> 01:22:44.600 align:start position:0% publish an academic paper but but it 01:22:44.600 --> 01:22:47.840 align:start position:0% publish an academic paper but but it will<01:22:45.600> be<01:22:45.780> very<01:22:46.020> nice<01:22:46.230> to<01:22:46.290> have<01:22:46.739> demos<01:22:47.190> to<01:22:47.670> have 01:22:47.840 --> 01:22:47.850 align:start position:0% will be very nice to have demos to have 01:22:47.850 --> 01:22:49.540 align:start position:0% will be very nice to have demos to have posters<01:22:48.360> from<01:22:48.720> the 01:22:49.540 --> 01:22:49.550 align:start position:0% posters from the 01:22:49.550 --> 01:22:52.970 align:start position:0% posters from the community<01:22:50.550> so<01:22:51.270> to<01:22:51.330> show<01:22:51.780> the<01:22:52.110> students<01:22:52.710> what 01:22:52.970 --> 01:22:52.980 align:start position:0% community so to show the students what 01:22:52.980 --> 01:22:55.370 align:start position:0% community so to show the students what interesting<01:22:53.670> things<01:22:54.000> or<01:22:54.240> what<01:22:54.570> what<01:22:54.990> what 01:22:55.370 --> 01:22:55.380 align:start position:0% interesting things or what what what 01:22:55.380 --> 01:22:57.590 align:start position:0% interesting things or what what what problems<01:22:55.950> can<01:22:56.160> can<01:22:56.580> be<01:22:56.610> good<01:22:56.940> for<01:22:57.210> research 01:22:57.590 --> 01:22:57.600 align:start position:0% problems can can be good for research 01:22:57.600 --> 01:23:00.770 align:start position:0% problems can can be good for research and<01:22:58.140> also<01:22:58.950> to<01:22:59.130> contact<01:23:00.000> each<01:23:00.330> other<01:23:00.540> to 01:23:00.770 --> 01:23:00.780 align:start position:0% and also to contact each other to 01:23:00.780 --> 01:23:03.440 align:start position:0% and also to contact each other to continue<01:23:01.260> to<01:23:01.470> to<01:23:02.340> have<01:23:02.490> the<01:23:02.640> contact<01:23:03.030> of<01:23:03.150> the 01:23:03.440 --> 01:23:03.450 align:start position:0% continue to to have the contact of the 01:23:03.450 --> 01:23:06.140 align:start position:0% continue to to have the contact of the students<01:23:03.810> with<01:23:04.020> with<01:23:04.640> the<01:23:05.640> savannahs 01:23:06.140 --> 01:23:06.150 align:start position:0% students with with the savannahs 01:23:06.150 --> 01:23:10.190 align:start position:0% students with with the savannahs community<01:23:06.690> and<01:23:07.190> and<01:23:08.190> also<01:23:08.550> to<01:23:08.820> have<01:23:09.090> a<01:23:09.150> plan<01:23:09.420> so 01:23:10.190 --> 01:23:10.200 align:start position:0% community and and also to have a plan so 01:23:10.200 --> 01:23:13.820 align:start position:0% community and and also to have a plan so I<01:23:10.530> just<01:23:11.160> started<01:23:11.640> my<01:23:11.870> associate<01:23:12.870> professor 01:23:13.820 --> 01:23:13.830 align:start position:0% I just started my associate professor 01:23:13.830 --> 01:23:16.340 align:start position:0% I just started my associate professor position<01:23:14.310> so<01:23:14.460> I<01:23:14.490> still<01:23:15.000> don't<01:23:15.270> have<01:23:15.450> them<01:23:15.690> much 01:23:16.340 --> 01:23:16.350 align:start position:0% position so I still don't have them much 01:23:16.350 --> 01:23:19.910 align:start position:0% position so I still don't have them much fun<01:23:16.760> but<01:23:17.760> so<01:23:18.540> I<01:23:18.570> need<01:23:18.840> much<01:23:19.080> more<01:23:19.350> help<01:23:19.410> than 01:23:19.910 --> 01:23:19.920 align:start position:0% fun but so I need much more help than 01:23:19.920 --> 01:23:23.540 align:start position:0% fun but so I need much more help than that<01:23:19.980> what<01:23:20.850> I<01:23:20.970> can<01:23:21.180> provide<01:23:21.800> but<01:23:22.800> if<01:23:23.010> somebody 01:23:23.540 --> 01:23:23.550 align:start position:0% that what I can provide but if somebody 01:23:23.550 --> 01:23:28.820 align:start position:0% that what I can provide but if somebody is<01:23:23.670> interested<01:23:23.880> or<01:23:24.590> or<01:23:25.640> or<01:23:26.640> no<01:23:27.200> have<01:23:28.200> contacts 01:23:28.820 --> 01:23:28.830 align:start position:0% is interested or or or no have contacts 01:23:28.830 --> 01:23:30.140 align:start position:0% is interested or or or no have contacts with<01:23:28.920> other<01:23:29.220> people<01:23:29.700> that<01:23:29.820> could<01:23:30.090> be 01:23:30.140 --> 01:23:30.150 align:start position:0% with other people that could be 01:23:30.150 --> 01:23:33.380 align:start position:0% with other people that could be interested<01:23:30.680> in<01:23:31.680> participated<01:23:32.610> in<01:23:32.760> this 01:23:33.380 --> 01:23:33.390 align:start position:0% interested in participated in this 01:23:33.390 --> 01:23:35.480 align:start position:0% interested in participated in this we<01:23:33.690> need<01:23:33.810> to<01:23:33.930> submit<01:23:34.200> a<01:23:34.260> proposal<01:23:34.680> at<01:23:35.100> the 01:23:35.480 --> 01:23:35.490 align:start position:0% we need to submit a proposal at the 01:23:35.490 --> 01:23:38.240 align:start position:0% we need to submit a proposal at the beginning<01:23:36.150> of<01:23:36.300> you<01:23:36.540> November<01:23:37.020> I<01:23:37.050> think<01:23:37.250> and 01:23:38.240 --> 01:23:38.250 align:start position:0% beginning of you November I think and 01:23:38.250 --> 01:23:40.400 align:start position:0% beginning of you November I think and the<01:23:38.460> workshop<01:23:38.880> will<01:23:39.090> be<01:23:39.270> in<01:23:39.480> April<01:23:39.660> increased 01:23:40.400 --> 01:23:40.410 align:start position:0% the workshop will be in April increased 01:23:40.410 --> 01:24:06.330 align:start position:0% the workshop will be in April increased in<01:23:40.740> the<01:23:41.390> doctor<01:23:42.830> conferences<01:23:43.830> so<01:23:44.310> that's<01:23:44.760> all 01:24:06.330 --> 01:24:06.340 align:start position:0% 01:24:06.340 --> 01:24:14.230 align:start position:0% which<01:24:07.340> course<01:24:08.330> is<01:24:08.630> like<01:24:09.850> patents<01:24:11.620> and<01:24:13.240> and 01:24:14.230 --> 01:24:14.240 align:start position:0% which course is like patents and and 01:24:14.240 --> 01:24:17.850 align:start position:0% which course is like patents and and also<01:24:14.900> in<01:24:15.740> some<01:24:16.040> cases<01:24:16.250> emits<01:24:16.700> I<01:24:16.820> don't<01:24:17.090> have 01:24:17.850 --> 01:24:17.860 align:start position:0% also in some cases emits I don't have 01:24:17.860 --> 01:24:21.550 align:start position:0% also in some cases emits I don't have comparison<01:24:19.630> in<01:24:20.630> the<01:24:20.720> papers<01:24:21.080> with<01:24:21.290> food 01:24:21.550 --> 01:24:21.560 align:start position:0% comparison in the papers with food 01:24:21.560 --> 01:24:23.980 align:start position:0% comparison in the papers with food workers<01:24:21.980> we<01:24:22.370> have<01:24:22.400> comparisons<01:24:23.390> with<01:24:23.660> others 01:24:23.980 --> 01:24:23.990 align:start position:0% workers we have comparisons with others 01:24:23.990 --> 01:24:30.070 align:start position:0% workers we have comparisons with others like<01:24:24.670> with<01:24:26.380> low<01:24:27.380> locality<01:24:27.980> codes<01:24:28.540> with<01:24:29.540> Prince 01:24:30.070 --> 01:24:30.080 align:start position:0% like with low locality codes with Prince 01:24:30.080 --> 01:24:33.730 align:start position:0% like with low locality codes with Prince aluminium<01:24:30.980> also<01:24:31.430> now<01:24:31.580> working<01:24:32.360> on<01:24:32.780> the<01:24:32.960> on<01:24:33.680> a 01:24:33.730 --> 01:24:33.740 align:start position:0% aluminium also now working on the on a 01:24:33.740 --> 01:24:38.200 align:start position:0% aluminium also now working on the on a system<01:24:34.250> that<01:24:34.780> will<01:24:35.780> be<01:24:36.190> useful<01:24:37.190> for<01:24:37.220> anyone<01:24:38.000> to 01:24:38.200 --> 01:24:38.210 align:start position:0% system that will be useful for anyone to 01:24:38.210 --> 01:24:41.380 align:start position:0% system that will be useful for anyone to compare<01:24:38.600> my<01:24:39.020> goals<01:24:39.320> with<01:24:39.830> others<01:24:40.220> so<01:24:40.850> you<01:24:41.240> can 01:24:41.380 --> 01:24:41.390 align:start position:0% compare my goals with others so you can 01:24:41.390 --> 01:24:44.050 align:start position:0% compare my goals with others so you can implemented<01:24:41.990> workouts<01:24:42.410> there<01:24:42.710> but<01:24:43.640> I<01:24:43.670> don't 01:24:44.050 --> 01:24:44.060 align:start position:0% implemented workouts there but I don't 01:24:44.060 --> 01:24:51.750 align:start position:0% implemented workouts there but I don't have<01:24:44.210> measurements<01:24:44.900> of<01:24:45.050> two<01:24:45.320> rotors 01:24:51.750 --> 01:24:51.760 align:start position:0% 01:24:51.760 --> 01:24:57.630 align:start position:0% thank<01:24:52.390> you<01:24:52.480> so<01:24:52.630> much<01:24:55.800> everyone<01:24:56.800> my<01:24:57.489> name<01:24:57.610> is 01:24:57.630 --> 01:24:57.640 align:start position:0% thank you so much everyone my name is 01:24:57.640 --> 01:24:59.430 align:start position:0% thank you so much everyone my name is Fatma<01:24:57.850> slipper<01:24:58.120> I'm<01:24:58.300> the<01:24:58.420> CTO<01:24:58.570> co-founder<01:24:59.410> of 01:24:59.430 --> 01:24:59.440 align:start position:0% Fatma slipper I'm the CTO co-founder of 01:24:59.440 --> 01:25:01.350 align:start position:0% Fatma slipper I'm the CTO co-founder of Killian<01:24:59.860> those<01:25:00.489> of<01:25:00.640> you<01:25:00.760> who<01:25:00.910> don't<01:25:01.090> know<01:25:01.120> what 01:25:01.350 --> 01:25:01.360 align:start position:0% Killian those of you who don't know what 01:25:01.360 --> 01:25:03.540 align:start position:0% Killian those of you who don't know what we<01:25:01.510> do<01:25:01.660> or<01:25:01.840> we<01:25:01.989> are<01:25:02.140> we're<01:25:02.950> a<01:25:02.980> blockchain 01:25:03.540 --> 01:25:03.550 align:start position:0% we do or we are we're a blockchain 01:25:03.550 --> 01:25:05.670 align:start position:0% we do or we are we're a blockchain needed<01:25:03.970> a<01:25:04.030> software<01:25:04.480> consultancy<01:25:04.930> in<01:25:05.170> foolish 01:25:05.670 --> 01:25:05.680 align:start position:0% needed a software consultancy in foolish 01:25:05.680 --> 01:25:08.610 align:start position:0% needed a software consultancy in foolish these<01:25:06.430> a<01:25:07.000> bunch<01:25:07.600> of<01:25:07.720> notable<01:25:08.290> folks<01:25:08.440> in<01:25:08.560> the 01:25:08.610 --> 01:25:08.620 align:start position:0% these a bunch of notable folks in the 01:25:08.620 --> 01:25:10.560 align:start position:0% these a bunch of notable folks in the space<01:25:08.830> business<01:25:09.040> pop<01:25:09.430> see<01:25:09.580> why<01:25:09.760> we<01:25:10.450> did 01:25:10.560 --> 01:25:10.570 align:start position:0% space business pop see why we did 01:25:10.570 --> 01:25:13.110 align:start position:0% space business pop see why we did mathematics<01:25:11.170> do<01:25:11.260> you<01:25:11.380> I<01:25:11.440> also<01:25:12.040> have<01:25:12.340> a<01:25:12.370> grant 01:25:13.110 --> 01:25:13.120 align:start position:0% mathematics do you I also have a grant 01:25:13.120 --> 01:25:15.479 align:start position:0% mathematics do you I also have a grant and<01:25:13.450> we<01:25:13.510> rented<01:25:14.230> an<01:25:14.410> audited<01:25:14.710> dr.<01:25:15.310> penny 01:25:15.479 --> 01:25:15.489 align:start position:0% and we rented an audited dr. penny 01:25:15.489 --> 01:25:18.540 align:start position:0% and we rented an audited dr. penny plasma<01:25:15.940> MVP<01:25:16.980> bunch<01:25:17.980> of<01:25:18.070> other<01:25:18.160> stuff<01:25:18.370> you<01:25:18.489> can 01:25:18.540 --> 01:25:18.550 align:start position:0% plasma MVP bunch of other stuff you can 01:25:18.550 --> 01:25:20.040 align:start position:0% plasma MVP bunch of other stuff you can talk<01:25:18.820> to<01:25:18.940> me<01:25:19.030> about<01:25:19.180> that<01:25:19.360> later<01:25:19.600> because 01:25:20.040 --> 01:25:20.050 align:start position:0% talk to me about that later because 01:25:20.050 --> 01:25:22.140 align:start position:0% talk to me about that later because today's<01:25:20.620> talk<01:25:21.010> isn't<01:25:21.220> really<01:25:21.760> about<01:25:21.850> what 01:25:22.140 --> 01:25:22.150 align:start position:0% today's talk isn't really about what 01:25:22.150 --> 01:25:23.490 align:start position:0% today's talk isn't really about what keoki<01:25:22.510> knows<01:25:22.690> about<01:25:22.989> something<01:25:23.350> that's 01:25:23.490 --> 01:25:23.500 align:start position:0% keoki knows about something that's 01:25:23.500 --> 01:25:25.680 align:start position:0% keoki knows about something that's important<01:25:23.920> to<01:25:23.950> me<01:25:24.010> and<01:25:24.430> that's<01:25:25.180> peer-to-peer 01:25:25.680 --> 01:25:25.690 align:start position:0% important to me and that's peer-to-peer 01:25:25.690 --> 01:25:29.160 align:start position:0% important to me and that's peer-to-peer decentralized<01:25:26.620> social<01:25:27.370> networking<01:25:27.940> so<01:25:28.840> I'm 01:25:29.160 --> 01:25:29.170 align:start position:0% decentralized social networking so I'm 01:25:29.170 --> 01:25:30.210 align:start position:0% decentralized social networking so I'm gonna<01:25:29.320> kick<01:25:29.470> things<01:25:29.650> off<01:25:29.770> with<01:25:29.830> a<01:25:29.980> little<01:25:30.010> bit 01:25:30.210 --> 01:25:30.220 align:start position:0% gonna kick things off with a little bit 01:25:30.220 --> 01:25:32.430 align:start position:0% gonna kick things off with a little bit of<01:25:30.310> a<01:25:30.370> story<01:25:30.640> so<01:25:30.850> there<01:25:31.000> were<01:25:31.060> two<01:25:31.440> most 01:25:32.430 --> 01:25:32.440 align:start position:0% of a story so there were two most 01:25:32.440 --> 01:25:34.800 align:start position:0% of a story so there were two most memorable<01:25:33.040> moments<01:25:33.489> growing<01:25:33.790> up<01:25:33.940> that<01:25:34.450> I<01:25:34.480> had 01:25:34.800 --> 01:25:34.810 align:start position:0% memorable moments growing up that I had 01:25:34.810 --> 01:25:36.360 align:start position:0% memorable moments growing up that I had when<01:25:34.989> I<01:25:35.050> interacted<01:25:35.560> with<01:25:35.650> the<01:25:35.770> technology 01:25:36.360 --> 01:25:36.370 align:start position:0% when I interacted with the technology 01:25:36.370 --> 01:25:38.910 align:start position:0% when I interacted with the technology and<01:25:36.730> the<01:25:37.330> first<01:25:37.600> was<01:25:37.870> when<01:25:38.050> my<01:25:38.320> level<01:25:38.770> nine 01:25:38.910 --> 01:25:38.920 align:start position:0% and the first was when my level nine 01:25:38.920 --> 01:25:41.729 align:start position:0% and the first was when my level nine dwarf<01:25:39.370> hunter<01:25:39.760> first<01:25:40.390> walked<01:25:40.840> into<01:25:41.050> Ironforge 01:25:41.729 --> 01:25:41.739 align:start position:0% dwarf hunter first walked into Ironforge 01:25:41.739 --> 01:25:43.710 align:start position:0% dwarf hunter first walked into Ironforge and<01:25:42.070> saw<01:25:42.489> the<01:25:42.550> dude<01:25:42.790> with<01:25:42.940> the<01:25:42.970> glowy<01:25:43.210> sword 01:25:43.710 --> 01:25:43.720 align:start position:0% and saw the dude with the glowy sword 01:25:43.720 --> 01:25:45.900 align:start position:0% and saw the dude with the glowy sword the<01:25:44.590> second<01:25:44.980> was<01:25:45.190> when<01:25:45.310> I<01:25:45.370> signed<01:25:45.700> up<01:25:45.880> for 01:25:45.900 --> 01:25:45.910 align:start position:0% the second was when I signed up for 01:25:45.910 --> 01:25:48.270 align:start position:0% the second was when I signed up for Facebook<01:25:46.540> the<01:25:47.440> reason<01:25:47.739> these<01:25:47.830> two<01:25:48.010> things 01:25:48.270 --> 01:25:48.280 align:start position:0% Facebook the reason these two things 01:25:48.280 --> 01:25:50.010 align:start position:0% Facebook the reason these two things were<01:25:48.460> so<01:25:48.610> memorable<01:25:49.210> and<01:25:49.360> important<01:25:49.810> to<01:25:49.870> me 01:25:50.010 --> 01:25:50.020 align:start position:0% were so memorable and important to me 01:25:50.020 --> 01:25:52.410 align:start position:0% were so memorable and important to me was<01:25:50.260> that<01:25:50.290> it<01:25:50.830> was<01:25:50.950> the<01:25:50.980> first<01:25:51.280> time<01:25:51.580> in<01:25:51.970> my 01:25:52.410 --> 01:25:52.420 align:start position:0% was that it was the first time in my 01:25:52.420 --> 01:25:53.970 align:start position:0% was that it was the first time in my life<01:25:52.840> that<01:25:53.110> had<01:25:53.200> actually<01:25:53.500> seen<01:25:53.710> technology 01:25:53.970 --> 01:25:53.980 align:start position:0% life that had actually seen technology 01:25:53.980 --> 01:25:57.240 align:start position:0% life that had actually seen technology be<01:25:54.520> used<01:25:54.760> to<01:25:55.120> connect<01:25:55.660> people<01:25:55.989> in<01:25:56.739> the<01:25:56.890> case<01:25:57.070> of 01:25:57.240 --> 01:25:57.250 align:start position:0% be used to connect people in the case of 01:25:57.250 --> 01:25:59.130 align:start position:0% be used to connect people in the case of World<01:25:57.400> of<01:25:57.489> Warcraft<01:25:57.610> it<01:25:58.120> was<01:25:58.330> here's<01:25:58.989> these 01:25:59.130 --> 01:25:59.140 align:start position:0% World of Warcraft it was here's these 01:25:59.140 --> 01:26:01.050 align:start position:0% World of Warcraft it was here's these people<01:25:59.500> that<01:25:59.739> are<01:25:59.860> immersed<01:26:00.340> within<01:26:00.640> and 01:26:01.050 --> 01:26:01.060 align:start position:0% people that are immersed within and 01:26:01.060 --> 01:26:03.330 align:start position:0% people that are immersed within and changing<01:26:01.870> this<01:26:02.050> incredible<01:26:02.590> fantasy<01:26:03.070> world 01:26:03.330 --> 01:26:03.340 align:start position:0% changing this incredible fantasy world 01:26:03.340 --> 01:26:05.250 align:start position:0% changing this incredible fantasy world and<01:26:03.610> the<01:26:04.030> second<01:26:04.390> one<01:26:04.480> on<01:26:04.630> Facebook<01:26:05.050> was 01:26:05.250 --> 01:26:05.260 align:start position:0% and the second one on Facebook was 01:26:05.260 --> 01:26:07.110 align:start position:0% and the second one on Facebook was here's<01:26:05.650> all<01:26:05.830> these<01:26:06.010> people<01:26:06.430> you<01:26:06.760> know<01:26:06.880> maybe 01:26:07.110 --> 01:26:07.120 align:start position:0% here's all these people you know maybe 01:26:07.120 --> 01:26:08.580 align:start position:0% here's all these people you know maybe folks<01:26:07.420> from<01:26:07.570> the<01:26:07.720> weird<01:26:07.930> private<01:26:08.290> school<01:26:08.470> I 01:26:08.580 --> 01:26:08.590 align:start position:0% folks from the weird private school I 01:26:08.590 --> 01:26:10.170 align:start position:0% folks from the weird private school I went<01:26:08.770> to<01:26:08.890> when<01:26:09.040> I<01:26:09.100> was<01:26:09.190> younger<01:26:09.430> that<01:26:09.580> I<01:26:09.850> hadn't 01:26:10.170 --> 01:26:10.180 align:start position:0% went to when I was younger that I hadn't 01:26:10.180 --> 01:26:11.010 align:start position:0% went to when I was younger that I hadn't talked<01:26:10.300> to<01:26:10.480> in<01:26:10.600> years 01:26:11.010 --> 01:26:11.020 align:start position:0% talked to in years 01:26:11.020 --> 01:26:14.070 align:start position:0% talked to in years maybe<01:26:11.650> folks<01:26:11.980> from<01:26:12.250> the<01:26:12.540> you<01:26:13.540> know<01:26:13.660> there<01:26:13.989> was 01:26:14.070 --> 01:26:14.080 align:start position:0% maybe folks from the you know there was 01:26:14.080 --> 01:26:15.630 align:start position:0% maybe folks from the you know there was a<01:26:14.110> whole<01:26:14.290> film<01:26:14.560> group<01:26:14.890> just<01:26:15.220> called<01:26:15.430> the 01:26:15.630 --> 01:26:15.640 align:start position:0% a whole film group just called the 01:26:15.640 --> 01:26:17.490 align:start position:0% a whole film group just called the slipper<01:26:15.880> clan<01:26:16.239> so<01:26:16.540> it<01:26:16.600> was<01:26:16.690> other<01:26:16.900> people<01:26:17.290> with 01:26:17.490 --> 01:26:17.500 align:start position:0% slipper clan so it was other people with 01:26:17.500 --> 01:26:20.040 align:start position:0% slipper clan so it was other people with my<01:26:18.160> same<01:26:18.520> weird<01:26:18.910> last<01:26:19.180> name<01:26:19.450> and<01:26:19.690> we<01:26:19.810> could<01:26:19.930> all 01:26:20.040 --> 01:26:20.050 align:start position:0% my same weird last name and we could all 01:26:20.050 --> 01:26:22.170 align:start position:0% my same weird last name and we could all get<01:26:20.620> together<01:26:20.800> and<01:26:21.100> like<01:26:21.460> talk<01:26:21.760> about<01:26:22.030> what 01:26:22.170 --> 01:26:22.180 align:start position:0% get together and like talk about what 01:26:22.180 --> 01:26:25.920 align:start position:0% get together and like talk about what it's<01:26:22.300> like<01:26:22.360> to<01:26:22.510> have<01:26:22.750> a<01:26:22.780> weird<01:26:23.080> last<01:26:23.260> name<01:26:24.930> one 01:26:25.920 --> 01:26:25.930 align:start position:0% it's like to have a weird last name one 01:26:25.930 --> 01:26:27.150 align:start position:0% it's like to have a weird last name one of<01:26:25.960> them<01:26:26.050> was<01:26:26.200> a<01:26:26.230> member<01:26:26.590> of<01:26:26.680> the<01:26:26.770> Australian 01:26:27.150 --> 01:26:27.160 align:start position:0% of them was a member of the Australian 01:26:27.160 --> 01:26:30.080 align:start position:0% of them was a member of the Australian Parliament 01:26:30.080 --> 01:26:30.090 align:start position:0% 01:26:30.090 --> 01:26:33.110 align:start position:0% so<01:26:30.720> I'm<01:26:30.870> gonna<01:26:31.020> bring<01:26:31.170> this<01:26:31.350> up<01:26:31.500> well<01:26:31.830> SSB<01:26:32.790> is 01:26:33.110 --> 01:26:33.120 align:start position:0% so I'm gonna bring this up well SSB is 01:26:33.120 --> 01:26:35.510 align:start position:0% so I'm gonna bring this up well SSB is one<01:26:33.450> just<01:26:33.690> a<01:26:33.780> protocol<01:26:34.290> it's<01:26:34.800> a<01:26:35.160> set<01:26:35.430> of 01:26:35.510 --> 01:26:35.520 align:start position:0% one just a protocol it's a set of 01:26:35.520 --> 01:26:36.710 align:start position:0% one just a protocol it's a set of applications<01:26:35.640> that<01:26:36.270> let<01:26:36.390> you<01:26:36.540> build 01:26:36.710 --> 01:26:36.720 align:start position:0% applications that let you build 01:26:36.720 --> 01:26:38.900 align:start position:0% applications that let you build decentralized<01:26:37.050> social<01:26:37.680> networking<01:26:38.220> so<01:26:38.850> I've 01:26:38.900 --> 01:26:38.910 align:start position:0% decentralized social networking so I've 01:26:38.910 --> 01:26:39.860 align:start position:0% decentralized social networking so I've got<01:26:39.030> a<01:26:39.060> bunch<01:26:39.240> of<01:26:39.300> slides<01:26:39.480> in<01:26:39.630> here<01:26:39.720> on<01:26:39.780> the 01:26:39.860 --> 01:26:39.870 align:start position:0% got a bunch of slides in here on the 01:26:39.870 --> 01:26:41.510 align:start position:0% got a bunch of slides in here on the talk<01:26:40.050> about<01:26:40.290> like<01:26:40.500> you<01:26:40.920> know<01:26:41.040> how<01:26:41.220> it<01:26:41.340> works 01:26:41.510 --> 01:26:41.520 align:start position:0% talk about like you know how it works 01:26:41.520 --> 01:26:43.160 align:start position:0% talk about like you know how it works and<01:26:41.760> things<01:26:41.970> like<01:26:42.090> that<01:26:42.300> and<01:26:42.480> we'll<01:26:42.600> get<01:26:42.930> there 01:26:43.160 --> 01:26:43.170 align:start position:0% and things like that and we'll get there 01:26:43.170 --> 01:26:44.480 align:start position:0% and things like that and we'll get there but<01:26:43.380> like<01:26:43.470> the<01:26:43.590> first<01:26:43.740> thing<01:26:43.920> I<01:26:44.010> want<01:26:44.190> to<01:26:44.220> do<01:26:44.340> is 01:26:44.480 --> 01:26:44.490 align:start position:0% but like the first thing I want to do is 01:26:44.490 --> 01:26:46.550 align:start position:0% but like the first thing I want to do is just<01:26:44.670> like<01:26:44.850> show<01:26:45.180> you<01:26:45.240> who<01:26:45.570> has<01:26:45.780> this<01:26:45.930> people 01:26:46.550 --> 01:26:46.560 align:start position:0% just like show you who has this people 01:26:46.560 --> 01:26:52.570 align:start position:0% just like show you who has this people so<01:26:47.070> let<01:26:47.550> me<01:26:48.200> X<01:26:49.200> out<01:26:49.530> of<01:26:49.650> this<01:26:50.510> and<01:26:51.510> come<01:26:51.930> in<01:26:52.080> here 01:26:52.570 --> 01:26:52.580 align:start position:0% so let me X out of this and come in here 01:26:52.580 --> 01:26:56.210 align:start position:0% so let me X out of this and come in here and<01:26:53.580> drag<01:26:53.970> it<01:26:54.120> over<01:26:54.240> here<01:26:54.420> and<01:26:54.870> that's<01:26:55.770> go<01:26:55.980> like 01:26:56.210 --> 01:26:56.220 align:start position:0% and drag it over here and that's go like 01:26:56.220 --> 01:27:02.180 align:start position:0% and drag it over here and that's go like this<01:26:58.730> so<01:26:59.730> this<01:27:00.000> is<01:27:00.060> patchwork<01:27:00.710> patchwork<01:27:01.710> is<01:27:02.160> a 01:27:02.180 --> 01:27:02.190 align:start position:0% this so this is patchwork patchwork is a 01:27:02.190 --> 01:27:04.160 align:start position:0% this so this is patchwork patchwork is a client<01:27:02.580> application<01:27:02.760> that<01:27:03.570> talks<01:27:03.900> to<01:27:04.020> the 01:27:04.160 --> 01:27:04.170 align:start position:0% client application that talks to the 01:27:04.170 --> 01:27:07.550 align:start position:0% client application that talks to the wider<01:27:04.740> SSB<01:27:05.310> number<01:27:05.700> and<01:27:06.090> the<01:27:06.720> resolution<01:27:07.440> was 01:27:07.550 --> 01:27:07.560 align:start position:0% wider SSB number and the resolution was 01:27:07.560 --> 01:27:09.440 align:start position:0% wider SSB number and the resolution was kind<01:27:07.860> of<01:27:07.950> screwed<01:27:08.250> up<01:27:08.340> so<01:27:08.730> it<01:27:08.880> can't<01:27:09.240> actually 01:27:09.440 --> 01:27:09.450 align:start position:0% kind of screwed up so it can't actually 01:27:09.450 --> 01:27:18.929 align:start position:0% kind of screwed up so it can't actually see<01:27:09.870> the<01:27:10.050> channels<01:27:10.410> on<01:27:10.530> this<01:27:13.640> when<01:27:14.640> we<01:27:14.700> do<01:27:14.820> that 01:27:18.929 --> 01:27:18.939 align:start position:0% 01:27:18.939 --> 01:27:22.509 align:start position:0% councillor<01:27:19.939> shine<01:27:20.179> on<01:27:20.389> the<01:27:20.509> right<01:27:21.369> all<01:27:22.369> right 01:27:22.509 --> 01:27:22.519 align:start position:0% councillor shine on the right all right 01:27:22.519 --> 01:27:25.059 align:start position:0% councillor shine on the right all right well<01:27:22.729> I'll<01:27:23.449> wing<01:27:23.659> it<01:27:23.689> guys<01:27:23.929> homing<01:27:24.379> so<01:27:24.739> anyway 01:27:25.059 --> 01:27:25.069 align:start position:0% well I'll wing it guys homing so anyway 01:27:25.069 --> 01:27:26.619 align:start position:0% well I'll wing it guys homing so anyway what<01:27:25.189> you're<01:27:25.309> seeing<01:27:25.489> is<01:27:25.729> Patrick<01:27:26.149> mr.<01:27:26.449> Klein 01:27:26.619 --> 01:27:26.629 align:start position:0% what you're seeing is Patrick mr. Klein 01:27:26.629 --> 01:27:28.029 align:start position:0% what you're seeing is Patrick mr. Klein that<01:27:26.779> connects<01:27:27.079> to<01:27:27.169> the<01:27:27.259> larger<01:27:27.619> assets<01:27:27.919> we 01:27:28.029 --> 01:27:28.039 align:start position:0% that connects to the larger assets we 01:27:28.039 --> 01:27:30.069 align:start position:0% that connects to the larger assets we network<01:27:28.369> so<01:27:28.999> I'm<01:27:29.089> most<01:27:29.269> important<01:27:29.659> to<01:27:29.719> know<01:27:29.839> is 01:27:30.069 --> 01:27:30.079 align:start position:0% network so I'm most important to know is 01:27:30.079 --> 01:27:31.539 align:start position:0% network so I'm most important to know is that<01:27:30.109> you<01:27:30.319> know<01:27:30.409> if<01:27:30.589> I<01:27:30.709> Mouse<01:27:30.919> appear<01:27:31.309> you'll 01:27:31.539 --> 01:27:31.549 align:start position:0% that you know if I Mouse appear you'll 01:27:31.549 --> 01:27:34.209 align:start position:0% that you know if I Mouse appear you'll see<01:27:31.669> that<01:27:31.789> my<01:27:31.909> Wi-Fi<01:27:32.329> is<01:27:32.389> off<01:27:32.749> so<01:27:33.739> everything 01:27:34.209 --> 01:27:34.219 align:start position:0% see that my Wi-Fi is off so everything 01:27:34.219 --> 01:27:35.589 align:start position:0% see that my Wi-Fi is off so everything that<01:27:34.249> I'm<01:27:34.519> currently<01:27:34.699> interacting<01:27:35.299> with<01:27:35.449> on 01:27:35.589 --> 01:27:35.599 align:start position:0% that I'm currently interacting with on 01:27:35.599 --> 01:27:37.569 align:start position:0% that I'm currently interacting with on the<01:27:35.719> screen<01:27:36.019> is<01:27:36.199> local<01:27:36.619> on<01:27:36.979> my<01:27:37.129> computer<01:27:37.549> that 01:27:37.569 --> 01:27:37.579 align:start position:0% the screen is local on my computer that 01:27:37.579 --> 01:27:38.979 align:start position:0% the screen is local on my computer that I've<01:27:37.849> synced<01:27:38.179> from<01:27:38.299> a<01:27:38.449> network<01:27:38.779> of 01:27:38.979 --> 01:27:38.989 align:start position:0% I've synced from a network of 01:27:38.989 --> 01:27:40.959 align:start position:0% I've synced from a network of decentralized<01:27:39.679> peers<01:27:40.009> all<01:27:40.369> around<01:27:40.639> the<01:27:40.759> world 01:27:40.959 --> 01:27:40.969 align:start position:0% decentralized peers all around the world 01:27:40.969 --> 01:27:43.089 align:start position:0% decentralized peers all around the world if<01:27:41.839> I<01:27:41.929> were<01:27:42.049> to<01:27:42.169> go<01:27:42.289> here<01:27:42.589> and<01:27:42.739> let's<01:27:42.889> take<01:27:43.039> a 01:27:43.089 --> 01:27:43.099 align:start position:0% if I were to go here and let's take a 01:27:43.099 --> 01:27:46.539 align:start position:0% if I were to go here and let's take a look<01:27:43.339> at<01:27:43.459> what<01:27:45.189> people<01:27:46.189> are<01:27:46.279> talking<01:27:46.399> about 01:27:46.539 --> 01:27:46.549 align:start position:0% look at what people are talking about 01:27:46.549 --> 01:27:52.629 align:start position:0% look at what people are talking about the<01:27:46.789> closure<01:27:47.059> closure<01:27:47.959> channel<01:27:50.049> well<01:27:51.639> I'm 01:27:52.629 --> 01:27:52.639 align:start position:0% the closure closure channel well I'm 01:27:52.639 --> 01:27:55.329 align:start position:0% the closure closure channel well I'm just<01:27:52.729> gonna<01:27:52.849> scroll<01:27:53.299> here<01:27:53.889> you<01:27:54.889> can<01:27:55.039> see<01:27:55.219> that 01:27:55.329 --> 01:27:55.339 align:start position:0% just gonna scroll here you can see that 01:27:55.339 --> 01:27:57.819 align:start position:0% just gonna scroll here you can see that we<01:27:55.459> have<01:27:55.549> a<01:27:55.609> sort<01:27:55.819> of<01:27:55.849> very<01:27:56.089> typical<01:27:56.829> social 01:27:57.819 --> 01:27:57.829 align:start position:0% we have a sort of very typical social 01:27:57.829 --> 01:28:00.309 align:start position:0% we have a sort of very typical social feed<01:27:58.249> here<01:27:58.519> but<01:27:58.819> the<01:27:58.939> difference<01:27:59.359> is<01:27:59.599> no<01:28:00.139> one 01:28:00.309 --> 01:28:00.319 align:start position:0% feed here but the difference is no one 01:28:00.319 --> 01:28:02.439 align:start position:0% feed here but the difference is no one is<01:28:00.409> actually<01:28:00.619> posting<01:28:01.279> the<01:28:01.399> speed<01:28:01.669> it's<01:28:02.239> all 01:28:02.439 --> 01:28:02.449 align:start position:0% is actually posting the speed it's all 01:28:02.449 --> 01:28:04.689 align:start position:0% is actually posting the speed it's all local<01:28:02.899> and<01:28:03.229> I'm<01:28:03.469> replicating<01:28:03.769> it<01:28:04.309> from<01:28:04.519> other 01:28:04.689 --> 01:28:04.699 align:start position:0% local and I'm replicating it from other 01:28:04.699 --> 01:28:07.149 align:start position:0% local and I'm replicating it from other people<01:28:05.089> out<01:28:05.629> in<01:28:05.779> the<01:28:05.869> ether<01:28:06.019> as<01:28:06.559> it<01:28:06.769> were<01:28:06.889> and 01:28:07.149 --> 01:28:07.159 align:start position:0% people out in the ether as it were and 01:28:07.159 --> 01:28:08.679 align:start position:0% people out in the ether as it were and no<01:28:07.399> one<01:28:07.549> can<01:28:07.699> take<01:28:07.879> these<01:28:08.119> away<01:28:08.269> from<01:28:08.599> me 01:28:08.679 --> 01:28:08.689 align:start position:0% no one can take these away from me 01:28:08.689 --> 01:28:10.659 align:start position:0% no one can take these away from me there's<01:28:09.199> no<01:28:09.379> product<01:28:09.829> guy<01:28:10.309> whose 01:28:10.659 --> 01:28:10.669 align:start position:0% there's no product guy whose 01:28:10.669 --> 01:28:12.729 align:start position:0% there's no product guy whose responsibility<01:28:11.599> it<01:28:11.719> is<01:28:11.839> to<01:28:12.079> drive<01:28:12.529> engagement 01:28:12.729 --> 01:28:12.739 align:start position:0% responsibility it is to drive engagement 01:28:12.739 --> 01:28:14.709 align:start position:0% responsibility it is to drive engagement eyeballs<01:28:13.489> to<01:28:13.699> this<01:28:13.849> that's<01:28:14.149> going<01:28:14.329> to<01:28:14.389> say<01:28:14.569> I'm 01:28:14.709 --> 01:28:14.719 align:start position:0% eyeballs to this that's going to say I'm 01:28:14.719 --> 01:28:17.439 align:start position:0% eyeballs to this that's going to say I'm not<01:28:14.839> allowed<01:28:15.079> to<01:28:15.109> talk<01:28:15.409> about<01:28:15.559> X<01:28:15.919> Y<01:28:16.099> &<01:28:16.279> Z<01:28:16.449> the 01:28:17.439 --> 01:28:17.449 align:start position:0% not allowed to talk about X Y & Z the 01:28:17.449 --> 01:28:19.209 align:start position:0% not allowed to talk about X Y & Z the only<01:28:17.839> person<01:28:18.229> that<01:28:18.259> has<01:28:18.379> any<01:28:18.679> control<01:28:18.949> over 01:28:19.209 --> 01:28:19.219 align:start position:0% only person that has any control over 01:28:19.219 --> 01:28:21.219 align:start position:0% only person that has any control over what<01:28:19.789> content<01:28:20.479> goes<01:28:20.539> in<01:28:20.689> there<01:28:21.019> and<01:28:21.169> the 01:28:21.219 --> 01:28:21.229 align:start position:0% what content goes in there and the 01:28:21.229 --> 01:28:24.429 align:start position:0% what content goes in there and the people<01:28:21.349> who<01:28:21.649> are<01:28:21.769> posting<01:28:22.009> it<01:28:22.399> and<01:28:22.609> me<01:28:23.449> the<01:28:24.289> guy 01:28:24.429 --> 01:28:24.439 align:start position:0% people who are posting it and me the guy 01:28:24.439 --> 01:28:26.319 align:start position:0% people who are posting it and me the guy who's<01:28:24.679> viewing<01:28:24.919> it<01:28:25.129> and<01:28:25.309> so<01:28:25.729> it<01:28:25.849> changes<01:28:25.879> the 01:28:26.319 --> 01:28:26.329 align:start position:0% who's viewing it and so it changes the 01:28:26.329 --> 01:28:28.809 align:start position:0% who's viewing it and so it changes the web<01:28:26.479> from<01:28:26.689> this<01:28:26.869> paradigm<01:28:27.379> where<01:28:27.889> we<01:28:28.399> go<01:28:28.609> and 01:28:28.809 --> 01:28:28.819 align:start position:0% web from this paradigm where we go and 01:28:28.819 --> 01:28:31.059 align:start position:0% web from this paradigm where we go and post<01:28:29.029> stuff<01:28:29.449> on<01:28:29.629> to<01:28:29.809> some<01:28:30.019> platform<01:28:30.529> somewhere 01:28:31.059 --> 01:28:31.069 align:start position:0% post stuff on to some platform somewhere 01:28:31.069 --> 01:28:33.189 align:start position:0% post stuff on to some platform somewhere and<01:28:31.309> some<01:28:31.519> other<01:28:31.819> product<01:28:32.299> guy<01:28:32.419> decides<01:28:32.869> where 01:28:33.189 --> 01:28:33.199 align:start position:0% and some other product guy decides where 01:28:33.199 --> 01:28:34.629 align:start position:0% and some other product guy decides where that's<01:28:33.469> going<01:28:33.679> to<01:28:33.769> be<01:28:33.859> rendered<01:28:34.249> and<01:28:34.399> somehow 01:28:34.629 --> 01:28:34.639 align:start position:0% that's going to be rendered and somehow 01:28:34.639 --> 01:28:36.939 align:start position:0% that's going to be rendered and somehow the<01:28:34.819> rhythmically<01:28:35.419> design<01:28:35.779> queue<01:28:36.259> of<01:28:36.439> posts 01:28:36.939 --> 01:28:36.949 align:start position:0% the rhythmically design queue of posts 01:28:36.949 --> 01:28:40.299 align:start position:0% the rhythmically design queue of posts instead<01:28:37.639> I'm<01:28:38.479> creating<01:28:38.899> a<01:28:38.989> viewer<01:28:39.349> onto<01:28:40.189> the 01:28:40.299 --> 01:28:40.309 align:start position:0% instead I'm creating a viewer onto the 01:28:40.309 --> 01:28:42.489 align:start position:0% instead I'm creating a viewer onto the web<01:28:40.489> now<01:28:41.059> lets<01:28:41.269> me<01:28:41.509> see<01:28:41.779> the<01:28:41.899> web<01:28:42.109> the<01:28:42.349> way<01:28:42.469> I 01:28:42.489 --> 01:28:42.499 align:start position:0% web now lets me see the web the way I 01:28:42.499 --> 01:28:45.159 align:start position:0% web now lets me see the web the way I care<01:28:43.099> about<01:28:43.369> and<01:28:43.519> the<01:28:44.269> things<01:28:44.449> that<01:28:44.599> I<01:28:44.839> care 01:28:45.159 --> 01:28:45.169 align:start position:0% care about and the things that I care 01:28:45.169 --> 01:28:47.459 align:start position:0% care about and the things that I care about<01:28:45.469> forever<01:28:46.099> and<01:28:46.489> no<01:28:46.669> one<01:28:46.819> can<01:28:46.969> take 01:28:47.459 --> 01:28:47.469 align:start position:0% about forever and no one can take 01:28:47.469 --> 01:28:50.010 align:start position:0% about forever and no one can take so<01:28:48.310> you<01:28:48.760> know<01:28:48.850> if<01:28:49.120> you<01:28:49.360> guys<01:28:49.449> want<01:28:49.780> to<01:28:49.870> download 01:28:50.010 --> 01:28:50.020 align:start position:0% so you know if you guys want to download 01:28:50.020 --> 01:28:51.840 align:start position:0% so you know if you guys want to download it<01:28:50.290> yourself<01:28:50.380> and<01:28:50.830> take<01:28:51.070> a<01:28:51.100> look<01:28:51.340> at<01:28:51.460> it<01:28:51.699> it's 01:28:51.840 --> 01:28:51.850 align:start position:0% it yourself and take a look at it it's 01:28:51.850 --> 01:28:53.820 align:start position:0% it yourself and take a look at it it's relatively<01:28:52.239> straightforward<01:28:52.600> but<01:28:53.170> you<01:28:53.770> know 01:28:53.820 --> 01:28:53.830 align:start position:0% relatively straightforward but you know 01:28:53.830 --> 01:28:56.189 align:start position:0% relatively straightforward but you know you've<01:28:54.010> probably<01:28:54.130> seen<01:28:54.699> this<01:28:55.090> type<01:28:55.810> of<01:28:55.840> UI 01:28:56.189 --> 01:28:56.199 align:start position:0% you've probably seen this type of UI 01:28:56.199 --> 01:29:00.300 align:start position:0% you've probably seen this type of UI before<01:28:57.540> but<01:28:58.540> that's<01:28:59.050> why<01:28:59.650> I<01:28:59.680> think<01:28:59.890> this<01:29:00.160> is 01:29:00.300 --> 01:29:00.310 align:start position:0% before but that's why I think this is 01:29:00.310 --> 01:29:02.280 align:start position:0% before but that's why I think this is important<01:29:00.820> and<01:29:01.000> why<01:29:01.270> I<01:29:01.300> care<01:29:01.630> about<01:29:01.870> it<01:29:02.020> and 01:29:02.280 --> 01:29:02.290 align:start position:0% important and why I care about it and 01:29:02.290 --> 01:29:05.189 align:start position:0% important and why I care about it and what<01:29:02.920> the<01:29:03.100> end<01:29:03.280> result<01:29:03.760> is<01:29:03.969> of<01:29:04.360> the<01:29:04.780> technical 01:29:05.189 --> 01:29:05.199 align:start position:0% what the end result is of the technical 01:29:05.199 --> 01:29:06.479 align:start position:0% what the end result is of the technical protocol<01:29:05.620> that<01:29:05.800> I'm<01:29:05.860> going<01:29:05.980> to<01:29:06.010> be<01:29:06.100> giving<01:29:06.219> you 01:29:06.479 --> 01:29:06.489 align:start position:0% protocol that I'm going to be giving you 01:29:06.489 --> 01:29:09.870 align:start position:0% protocol that I'm going to be giving you an<01:29:06.610> overview<01:29:06.699> of<01:29:07.090> next<01:29:08.020> so<01:29:08.680> anything<01:29:09.580> you<01:29:09.730> guys 01:29:09.870 --> 01:29:09.880 align:start position:0% an overview of next so anything you guys 01:29:09.880 --> 01:29:11.970 align:start position:0% an overview of next so anything you guys want<01:29:10.239> me<01:29:10.360> to<01:29:10.449> cover<01:29:10.930> against<01:29:11.410> quite<01:29:11.710> launch 01:29:11.970 --> 01:29:11.980 align:start position:0% want me to cover against quite launch 01:29:11.980 --> 01:29:14.550 align:start position:0% want me to cover against quite launch into<01:29:12.250> how<01:29:12.340> it<01:29:12.489> all<01:29:12.610> works<01:29:13.080> all<01:29:14.080> right<01:29:14.140> cool 01:29:14.550 --> 01:29:14.560 align:start position:0% into how it all works all right cool 01:29:14.560 --> 01:29:23.370 align:start position:0% into how it all works all right cool let's<01:29:15.520> go<01:29:15.640> back<01:29:15.820> to<01:29:16.230> mr.<01:29:17.230> PowerPoint<01:29:17.890> here 01:29:23.370 --> 01:29:23.380 align:start position:0% 01:29:23.380 --> 01:29:27.930 align:start position:0% like<01:29:23.530> this<01:29:25.770> who<01:29:26.770> said<01:29:26.950> that<01:29:27.040> I<01:29:27.310> all<01:29:27.790> their 01:29:27.930 --> 01:29:27.940 align:start position:0% like this who said that I all their 01:29:27.940 --> 01:29:29.490 align:start position:0% like this who said that I all their alternate<01:29:28.390> user<01:29:28.660> interfaces 01:29:29.490 --> 01:29:29.500 align:start position:0% alternate user interfaces 01:29:29.500 --> 01:29:31.380 align:start position:0% alternate user interfaces oh<01:29:29.530> yeah<01:29:29.830> there's<01:29:30.220> lots<01:29:30.340> okay<01:29:30.790> so<01:29:31.090> there<01:29:31.360> is 01:29:31.380 --> 01:29:31.390 align:start position:0% oh yeah there's lots okay so there is 01:29:31.390 --> 01:29:33.720 align:start position:0% oh yeah there's lots okay so there is patch<01:29:31.690> Bay<01:29:31.990> there's<01:29:32.530> a<01:29:32.560> whole<01:29:32.710> bunch<01:29:32.830> of<01:29:33.040> CLI 01:29:33.720 --> 01:29:33.730 align:start position:0% patch Bay there's a whole bunch of CLI 01:29:33.730 --> 01:29:35.250 align:start position:0% patch Bay there's a whole bunch of CLI based<01:29:34.000> ones<01:29:34.270> there's<01:29:34.570> always<01:29:34.690> two<01:29:34.840> us<01:29:34.930> are<01:29:35.050> you 01:29:35.250 --> 01:29:35.260 align:start position:0% based ones there's always two us are you 01:29:35.260 --> 01:29:37.680 align:start position:0% based ones there's always two us are you that's<01:29:36.010> patchwork<01:29:36.580> I<01:29:36.850> like<01:29:37.510> patchwork 01:29:37.680 --> 01:29:37.690 align:start position:0% that's patchwork I like patchwork 01:29:37.690 --> 01:29:40.040 align:start position:0% that's patchwork I like patchwork because<01:29:38.260> it's<01:29:38.410> a<01:29:38.500> little<01:29:38.620> bit<01:29:38.800> more<01:29:39.520> polish 01:29:40.040 --> 01:29:40.050 align:start position:0% because it's a little bit more polish 01:29:40.050 --> 01:29:42.120 align:start position:0% because it's a little bit more polish yeah<01:29:41.050> yeah<01:29:41.230> I<01:29:41.260> write<01:29:41.470> in<01:29:41.590> the<01:29:41.650> nice<01:29:41.770> patchwork 01:29:42.120 --> 01:29:42.130 align:start position:0% yeah yeah I write in the nice patchwork 01:29:42.130 --> 01:29:43.410 align:start position:0% yeah yeah I write in the nice patchwork but<01:29:42.280> it's<01:29:42.460> dis<01:29:42.670> one<01:29:42.850> the<01:29:43.000> one<01:29:43.150> you<01:29:43.390> are 01:29:43.410 --> 01:29:43.420 align:start position:0% but it's dis one the one you are 01:29:43.420 --> 01:29:45.990 align:start position:0% but it's dis one the one you are personnel<01:29:44.080> using<01:29:44.260> the<01:29:44.380> day-to-day<01:29:44.700> okay<01:29:45.700> yeah 01:29:45.990 --> 01:29:46.000 align:start position:0% personnel using the day-to-day okay yeah 01:29:46.000 --> 01:29:47.250 align:start position:0% personnel using the day-to-day okay yeah I<01:29:46.090> don't<01:29:46.240> wanna<01:29:46.360> tell<01:29:46.480> you<01:29:46.510> my<01:29:46.690> account<01:29:47.050> Issa 01:29:47.250 --> 01:29:47.260 align:start position:0% I don't wanna tell you my account Issa 01:29:47.260 --> 01:29:48.600 align:start position:0% I don't wanna tell you my account Issa is<01:29:47.470> one<01:29:47.620> of<01:29:47.710> the<01:29:47.770> fun<01:29:47.950> parts<01:29:47.980> is<01:29:48.370> that<01:29:48.400> it's 01:29:48.600 --> 01:29:48.610 align:start position:0% is one of the fun parts is that it's 01:29:48.610 --> 01:29:51.110 align:start position:0% is one of the fun parts is that it's like<01:29:48.760> actually<01:29:49.240> pseudo<01:29:49.540> anonymous<01:29:49.780> and<01:29:50.740> so<01:29:50.950> uh 01:29:51.110 --> 01:29:51.120 align:start position:0% like actually pseudo anonymous and so uh 01:29:51.120 --> 01:29:55.200 align:start position:0% like actually pseudo anonymous and so uh yeah<01:29:52.120> sorry<01:29:52.420> about<01:29:52.450> that<01:29:52.600> but<01:29:53.500> okay<01:29:54.070> so<01:29:54.910> this 01:29:55.200 --> 01:29:55.210 align:start position:0% yeah sorry about that but okay so this 01:29:55.210 --> 01:29:56.760 align:start position:0% yeah sorry about that but okay so this is<01:29:55.360> how<01:29:55.480> secure<01:29:55.780> scuttlebutt<01:29:56.140> defines<01:29:56.470> itself 01:29:56.760 --> 01:29:56.770 align:start position:0% is how secure scuttlebutt defines itself 01:29:56.770 --> 01:29:58.170 align:start position:0% is how secure scuttlebutt defines itself as<01:29:56.920> a<01:29:56.980> protocol<01:29:57.370> so<01:29:57.580> it's<01:29:57.730> a<01:29:57.760> family<01:29:57.940> of 01:29:58.170 --> 01:29:58.180 align:start position:0% as a protocol so it's a family of 01:29:58.180 --> 01:29:59.910 align:start position:0% as a protocol so it's a family of protocols<01:29:58.390> from<01:29:58.840> the<01:29:58.990> security<01:29:59.470> naration<01:29:59.680> and 01:29:59.910 --> 01:29:59.920 align:start position:0% protocols from the security naration and 01:29:59.920 --> 01:30:01.560 align:start position:0% protocols from the security naration and replication<01:30:00.460> of<01:30:00.550> append-only<01:30:00.850> data<01:30:01.300> means 01:30:01.560 --> 01:30:01.570 align:start position:0% replication of append-only data means 01:30:01.570 --> 01:30:03.390 align:start position:0% replication of append-only data means you're<01:30:02.230> gonna<01:30:02.320> see<01:30:02.530> a<01:30:02.560> lot<01:30:02.740> of<01:30:02.770> local<01:30:03.160> office 01:30:03.390 --> 01:30:03.400 align:start position:0% you're gonna see a lot of local office 01:30:03.400 --> 01:30:05.220 align:start position:0% you're gonna see a lot of local office and<01:30:03.550> parallels<01:30:03.970> between<01:30:04.060> this<01:30:04.390> and<01:30:04.750> you<01:30:05.140> know 01:30:05.220 --> 01:30:05.230 align:start position:0% and parallels between this and you know 01:30:05.230 --> 01:30:06.660 align:start position:0% and parallels between this and you know what<01:30:05.350> was<01:30:05.440> discussed<01:30:05.800> during<01:30:05.920> death<01:30:06.310> because 01:30:06.660 --> 01:30:06.670 align:start position:0% what was discussed during death because 01:30:06.670 --> 01:30:08.610 align:start position:0% what was discussed during death because it's<01:30:06.790> a<01:30:06.820> very<01:30:07.030> similar<01:30:07.360> idea<01:30:07.540> you<01:30:08.350> take<01:30:08.500> an 01:30:08.610 --> 01:30:08.620 align:start position:0% it's a very similar idea you take an 01:30:08.620 --> 01:30:10.050 align:start position:0% it's a very similar idea you take an append-only<01:30:08.890> feet<01:30:09.340> of<01:30:09.460> the<01:30:09.520> content<01:30:09.910> you 01:30:10.050 --> 01:30:10.060 align:start position:0% append-only feet of the content you 01:30:10.060 --> 01:30:11.790 align:start position:0% append-only feet of the content you replicated<01:30:10.780> to<01:30:10.900> a<01:30:10.930> bunch<01:30:11.200> of<01:30:11.290> other<01:30:11.530> people 01:30:11.790 --> 01:30:11.800 align:start position:0% replicated to a bunch of other people 01:30:11.800 --> 01:30:14.160 align:start position:0% replicated to a bunch of other people and<01:30:12.130> then<01:30:12.550> you<01:30:12.790> allow<01:30:13.060> client<01:30:13.570> applications 01:30:14.160 --> 01:30:14.170 align:start position:0% and then you allow client applications 01:30:14.170 --> 01:30:16.500 align:start position:0% and then you allow client applications databases<01:30:14.950> etc<01:30:15.070> to<01:30:15.550> be<01:30:15.640> built<01:30:15.850> on<01:30:15.970> top<01:30:16.030> of<01:30:16.240> it 01:30:16.500 --> 01:30:16.510 align:start position:0% databases etc to be built on top of it 01:30:16.510 --> 01:30:18.420 align:start position:0% databases etc to be built on top of it and<01:30:16.990> then<01:30:17.170> allow<01:30:17.380> people<01:30:17.590> to<01:30:17.710> index<01:30:18.190> and 01:30:18.420 --> 01:30:18.430 align:start position:0% and then allow people to index and 01:30:18.430 --> 01:30:20.310 align:start position:0% and then allow people to index and display<01:30:18.820> the<01:30:18.970> data<01:30:19.000> in<01:30:19.270> a<01:30:19.450> meaningful<01:30:19.780> way<01:30:19.900> and 01:30:20.310 --> 01:30:20.320 align:start position:0% display the data in a meaningful way and 01:30:20.320 --> 01:30:23.040 align:start position:0% display the data in a meaningful way and when<01:30:21.100> I<01:30:21.130> say<01:30:21.340> it's<01:30:21.460> a<01:30:21.520> family<01:30:21.700> protocols<01:30:22.450> also 01:30:23.040 --> 01:30:23.050 align:start position:0% when I say it's a family protocols also 01:30:23.050 --> 01:30:24.330 align:start position:0% when I say it's a family protocols also very<01:30:23.230> similar<01:30:23.530> to<01:30:23.650> doubt<01:30:23.830> they're<01:30:24.040> designed 01:30:24.330 --> 01:30:24.340 align:start position:0% very similar to doubt they're designed 01:30:24.340 --> 01:30:26.100 align:start position:0% very similar to doubt they're designed to<01:30:24.430> be<01:30:24.490> motto<01:30:24.820> am<01:30:25.270> I<01:30:25.390> already<01:30:25.510> known<01:30:25.810> at<01:30:25.960> three 01:30:26.100 --> 01:30:26.110 align:start position:0% to be motto am I already known at three 01:30:26.110 --> 01:30:28.800 align:start position:0% to be motto am I already known at three minutes<01:30:26.230> Jesus 01:30:28.800 --> 01:30:28.810 align:start position:0% minutes Jesus 01:30:28.810 --> 01:30:31.410 align:start position:0% so<01:30:29.530> yeah<01:30:30.400> they<01:30:30.520> say<01:30:30.880> it's<01:30:31.000> a<01:30:31.030> family<01:30:31.360> of 01:30:31.410 --> 01:30:31.420 align:start position:0% so yeah they say it's a family of 01:30:31.420 --> 01:30:32.610 align:start position:0% so yeah they say it's a family of protocols<01:30:31.630> that<01:30:31.990> they're<01:30:32.140> designed<01:30:32.440> to<01:30:32.530> be 01:30:32.610 --> 01:30:32.620 align:start position:0% protocols that they're designed to be 01:30:32.620 --> 01:30:34.200 align:start position:0% protocols that they're designed to be modular<01:30:32.770> it<01:30:33.190> makes<01:30:33.370> it<01:30:33.460> a<01:30:33.520> match<01:30:33.700> so<01:30:34.120> they 01:30:34.200 --> 01:30:34.210 align:start position:0% modular it makes it a match so they 01:30:34.210 --> 01:30:38.190 align:start position:0% modular it makes it a match so they already<01:30:34.390> know<01:30:34.810> here<01:30:35.710> we<01:30:35.770> go<01:30:36.210> the<01:30:37.210> SSB<01:30:37.750> family 01:30:38.190 --> 01:30:38.200 align:start position:0% already know here we go the SSB family 01:30:38.200 --> 01:30:40.020 align:start position:0% already know here we go the SSB family consists<01:30:38.710> basically<01:30:38.740> of<01:30:39.190> these<01:30:39.430> layers<01:30:39.670> at 01:30:40.020 --> 01:30:40.030 align:start position:0% consists basically of these layers at 01:30:40.030 --> 01:30:41.490 align:start position:0% consists basically of these layers at the<01:30:40.090> bottom<01:30:40.180> layer<01:30:40.600> you<01:30:40.780> have<01:30:40.810> a<01:30:40.960> set<01:30:41.200> of<01:30:41.230> keys 01:30:41.490 --> 01:30:41.500 align:start position:0% the bottom layer you have a set of keys 01:30:41.500 --> 01:30:43.110 align:start position:0% the bottom layer you have a set of keys so<01:30:41.800> a<01:30:41.830> key<01:30:42.070> pair<01:30:42.310> that's<01:30:42.580> used<01:30:42.790> for<01:30:43.000> user 01:30:43.110 --> 01:30:43.120 align:start position:0% so a key pair that's used for user 01:30:43.120 --> 01:30:45.570 align:start position:0% so a key pair that's used for user identity<01:30:43.810> there's<01:30:44.290> no<01:30:44.470> canonical<01:30:45.130> naming<01:30:45.460> on 01:30:45.570 --> 01:30:45.580 align:start position:0% identity there's no canonical naming on 01:30:45.580 --> 01:30:47.430 align:start position:0% identity there's no canonical naming on SSB<01:30:46.030> so<01:30:46.270> you<01:30:46.330> name<01:30:46.630> yourself<01:30:46.810> and<01:30:47.290> other 01:30:47.430 --> 01:30:47.440 align:start position:0% SSB so you name yourself and other 01:30:47.440 --> 01:30:49.020 align:start position:0% SSB so you name yourself and other people<01:30:47.530> decide<01:30:47.950> what<01:30:48.370> name<01:30:48.580> they<01:30:48.790> are<01:30:48.820> going 01:30:49.020 --> 01:30:49.030 align:start position:0% people decide what name they are going 01:30:49.030 --> 01:30:51.360 align:start position:0% people decide what name they are going to<01:30:49.210> use<01:30:49.360> to<01:30:49.510> describe<01:30:49.780> you<01:30:50.050> that<01:30:50.350> have<01:30:51.220> your 01:30:51.360 --> 01:30:51.370 align:start position:0% to use to describe you that have your 01:30:51.370 --> 01:30:53.070 align:start position:0% to use to describe you that have your feeds<01:30:51.610> drug<01:30:51.970> the<01:30:52.060> append<01:30:52.360> only<01:30:52.480> feeds<01:30:52.870> as<01:30:52.960> we 01:30:53.070 --> 01:30:53.080 align:start position:0% feeds drug the append only feeds as we 01:30:53.080 --> 01:30:55.020 align:start position:0% feeds drug the append only feeds as we mentioned<01:30:53.410> earlier<01:30:53.710> a<01:30:53.980> secret<01:30:54.760> handshake 01:30:55.020 --> 01:30:55.030 align:start position:0% mentioned earlier a secret handshake 01:30:55.030 --> 01:30:57.150 align:start position:0% mentioned earlier a secret handshake which<01:30:55.570> is<01:30:55.690> how<01:30:55.810> peers<01:30:56.140> talk<01:30:56.500> to<01:30:56.740> one<01:30:56.890> another 01:30:57.150 --> 01:30:57.160 align:start position:0% which is how peers talk to one another 01:30:57.160 --> 01:30:59.310 align:start position:0% which is how peers talk to one another we<01:30:57.370> identify<01:30:58.060> one<01:30:58.330> another<01:30:58.570> and<01:30:58.840> it<01:30:58.990> grabs<01:30:59.230> a 01:30:59.310 --> 01:30:59.320 align:start position:0% we identify one another and it grabs a 01:30:59.320 --> 01:31:01.070 align:start position:0% we identify one another and it grabs a traffic<01:30:59.710> between<01:30:59.890> one<01:31:00.370> another 01:31:01.070 --> 01:31:01.080 align:start position:0% traffic between one another 01:31:01.080 --> 01:31:03.240 align:start position:0% traffic between one another probably<01:31:02.080> I'll<01:31:02.290> get<01:31:02.410> into<01:31:02.500> in<01:31:02.650> a<01:31:02.710> second<01:31:03.070> and 01:31:03.240 --> 01:31:03.250 align:start position:0% probably I'll get into in a second and 01:31:03.250 --> 01:31:04.770 align:start position:0% probably I'll get into in a second and applications<01:31:03.880> which<01:31:04.120> is<01:31:04.150> something<01:31:04.540> that<01:31:04.660> you 01:31:04.770 --> 01:31:04.780 align:start position:0% applications which is something that you 01:31:04.780 --> 01:31:06.960 align:start position:0% applications which is something that you are<01:31:04.810> in<01:31:05.080> the<01:31:05.170> sauce<01:31:05.440> so<01:31:05.710> Koch<01:31:05.920> work<01:31:06.220> is<01:31:06.820> an 01:31:06.960 --> 01:31:06.970 align:start position:0% are in the sauce so Koch work is an 01:31:06.970 --> 01:31:08.310 align:start position:0% are in the sauce so Koch work is an application 01:31:08.310 --> 01:31:08.320 align:start position:0% application 01:31:08.320 --> 01:31:11.140 align:start position:0% application this<01:31:09.320> example<01:31:09.710> what<01:31:09.920> a<01:31:09.950> key<01:31:10.130> looks<01:31:10.400> like<01:31:10.580> so<01:31:11.060> in 01:31:11.140 --> 01:31:11.150 align:start position:0% this example what a key looks like so in 01:31:11.150 --> 01:31:12.550 align:start position:0% this example what a key looks like so in this<01:31:11.240> case<01:31:11.480> soap<01:31:11.780> dog<01:31:11.990> the<01:31:12.200> guy<01:31:12.320> who<01:31:12.380> was 01:31:12.550 --> 01:31:12.560 align:start position:0% this case soap dog the guy who was 01:31:12.560 --> 01:31:14.740 align:start position:0% this case soap dog the guy who was talking<01:31:12.770> about<01:31:13.010> the<01:31:13.370> go<01:31:13.670> back<01:31:13.910> up<01:31:14.120> tool<01:31:14.300> this 01:31:14.740 --> 01:31:14.750 align:start position:0% talking about the go back up tool this 01:31:14.750 --> 01:31:17.110 align:start position:0% talking about the go back up tool this is<01:31:14.900> his<01:31:15.080> key<01:31:15.400> anytime<01:31:16.400> you<01:31:16.550> see<01:31:16.730> a<01:31:16.760> feed<01:31:17.090> that 01:31:17.110 --> 01:31:17.120 align:start position:0% is his key anytime you see a feed that 01:31:17.120 --> 01:31:19.780 align:start position:0% is his key anytime you see a feed that has<01:31:17.420> messages<01:31:17.900> signed<01:31:18.170> by<01:31:18.440> this<01:31:18.500> key<01:31:19.220> you<01:31:19.520> know 01:31:19.780 --> 01:31:19.790 align:start position:0% has messages signed by this key you know 01:31:19.790 --> 01:31:21.550 align:start position:0% has messages signed by this key you know it<01:31:19.910> belongs<01:31:20.210> to<01:31:20.390> sub<01:31:20.600> dog<01:31:20.810> but<01:31:21.110> sub<01:31:21.350> dog 01:31:21.550 --> 01:31:21.560 align:start position:0% it belongs to sub dog but sub dog 01:31:21.560 --> 01:31:23.560 align:start position:0% it belongs to sub dog but sub dog doesn't<01:31:21.890> actually<01:31:22.190> own<01:31:22.490> that<01:31:22.520> I<01:31:23.090> have<01:31:23.210> decided 01:31:23.560 --> 01:31:23.570 align:start position:0% doesn't actually own that I have decided 01:31:23.570 --> 01:31:25.120 align:start position:0% doesn't actually own that I have decided to<01:31:23.720> accept<01:31:24.170> the<01:31:24.260> fact<01:31:24.560> that<01:31:24.650> he's<01:31:24.860> called 01:31:25.120 --> 01:31:25.130 align:start position:0% to accept the fact that he's called 01:31:25.130 --> 01:31:28.510 align:start position:0% to accept the fact that he's called himself<01:31:25.310> back<01:31:25.640> on<01:31:26.000> SSP<01:31:27.070> this<01:31:28.070> is<01:31:28.190> kind<01:31:28.370> of<01:31:28.400> what 01:31:28.510 --> 01:31:28.520 align:start position:0% himself back on SSP this is kind of what 01:31:28.520 --> 01:31:30.250 align:start position:0% himself back on SSP this is kind of what feed<01:31:28.730> looks<01:31:28.880> like<01:31:29.120> just<01:31:29.870> like<01:31:29.900> a<01:31:30.020> blockchain 01:31:30.250 --> 01:31:30.260 align:start position:0% feed looks like just like a blockchain 01:31:30.260 --> 01:31:32.380 align:start position:0% feed looks like just like a blockchain this<01:31:30.590> content<01:31:31.130> hash<01:31:31.340> linked<01:31:31.760> so<01:31:32.180> this 01:31:32.380 --> 01:31:32.390 align:start position:0% this content hash linked so this 01:31:32.390 --> 01:31:35.860 align:start position:0% this content hash linked so this previous<01:31:33.550> here<01:31:34.550> is<01:31:35.060> the<01:31:35.330> hash<01:31:35.510> of<01:31:35.750> this 01:31:35.860 --> 01:31:35.870 align:start position:0% previous here is the hash of this 01:31:35.870 --> 01:31:37.870 align:start position:0% previous here is the hash of this definer<01:31:36.230> message<01:31:36.560> before<01:31:36.740> this<01:31:37.580> is<01:31:37.730> how 01:31:37.870 --> 01:31:37.880 align:start position:0% definer message before this is how 01:31:37.880 --> 01:31:40.660 align:start position:0% definer message before this is how you're<01:31:38.110> providing<01:31:39.110> authenticity<01:31:39.950> to<01:31:40.580> the 01:31:40.660 --> 01:31:40.670 align:start position:0% you're providing authenticity to the 01:31:40.670 --> 01:31:42.790 align:start position:0% you're providing authenticity to the messages<01:31:41.060> as<01:31:41.180> they<01:31:41.210> get<01:31:41.450> replicated<01:31:42.080> people 01:31:42.790 --> 01:31:42.800 align:start position:0% messages as they get replicated people 01:31:42.800 --> 01:31:44.260 align:start position:0% messages as they get replicated people would<01:31:42.950> need<01:31:43.130> my<01:31:43.400> key<01:31:43.700> and<01:31:43.910> they<01:31:44.000> would<01:31:44.120> need 01:31:44.260 --> 01:31:44.270 align:start position:0% would need my key and they would need 01:31:44.270 --> 01:31:45.730 align:start position:0% would need my key and they would need all<01:31:44.540> of<01:31:44.570> my<01:31:44.720> messages<01:31:45.170> going<01:31:45.440> all<01:31:45.620> the<01:31:45.710> way 01:31:45.730 --> 01:31:45.740 align:start position:0% all of my messages going all the way 01:31:45.740 --> 01:31:47.860 align:start position:0% all of my messages going all the way back<01:31:45.830> to<01:31:46.190> sort<01:31:46.430> of<01:31:46.460> Genesis<01:31:47.180> message<01:31:47.600> if<01:31:47.750> they 01:31:47.860 --> 01:31:47.870 align:start position:0% back to sort of Genesis message if they 01:31:47.870 --> 01:31:51.190 align:start position:0% back to sort of Genesis message if they wanted<01:31:48.170> to<01:31:48.460> Forge<01:31:49.690> anything<01:31:50.690> that<01:31:50.840> I'm<01:31:50.930> trying 01:31:51.190 --> 01:31:51.200 align:start position:0% wanted to Forge anything that I'm trying 01:31:51.200 --> 01:31:57.430 align:start position:0% wanted to Forge anything that I'm trying to<01:31:51.320> say<01:31:51.500> unless<01:31:51.860> is<01:31:52.010> B<01:31:53.770> so<01:31:56.320> there's<01:31:57.320> also 01:31:57.430 --> 01:31:57.440 align:start position:0% to say unless is B so there's also 01:31:57.440 --> 01:31:59.350 align:start position:0% to say unless is B so there's also probably<01:31:57.800> no<01:31:58.070> networking<01:31:58.640> that's<01:31:58.970> included 01:31:59.350 --> 01:31:59.360 align:start position:0% probably no networking that's included 01:31:59.360 --> 01:32:00.790 align:start position:0% probably no networking that's included in<01:31:59.480> the<01:31:59.540> secret<01:31:59.840> handshake<01:31:59.990> now<01:32:00.530> I'm<01:32:00.680> not 01:32:00.790 --> 01:32:00.800 align:start position:0% in the secret handshake now I'm not 01:32:00.800 --> 01:32:01.960 align:start position:0% in the secret handshake now I'm not going<01:32:00.920> to<01:32:00.980> go<01:32:01.190> into<01:32:01.370> the<01:32:01.460> details<01:32:01.790> of<01:32:01.910> that 01:32:01.960 --> 01:32:01.970 align:start position:0% going to go into the details of that 01:32:01.970 --> 01:32:03.610 align:start position:0% going to go into the details of that because<01:32:02.180> it's<01:32:02.450> not<01:32:02.720> enough<01:32:02.960> time<01:32:03.140> but<01:32:03.410> if<01:32:03.500> you 01:32:03.610 --> 01:32:03.620 align:start position:0% because it's not enough time but if you 01:32:03.620 --> 01:32:05.410 align:start position:0% because it's not enough time but if you imagine<01:32:03.800> a<01:32:04.070> TLS<01:32:04.460> handshake<01:32:04.490> between<01:32:05.060> two 01:32:05.410 --> 01:32:05.420 align:start position:0% imagine a TLS handshake between two 01:32:05.420 --> 01:32:08.740 align:start position:0% imagine a TLS handshake between two peers<01:32:05.720> where<01:32:06.020> the<01:32:06.200> identity<01:32:07.190> is<01:32:07.910> the<01:32:08.420> key<01:32:08.600> that 01:32:08.740 --> 01:32:08.750 align:start position:0% peers where the identity is the key that 01:32:08.750 --> 01:32:11.110 align:start position:0% peers where the identity is the key that I<01:32:08.840> both<01:32:09.230> recently<01:32:09.830> discussed<01:32:10.160> that's<01:32:10.910> the<01:32:11.030> way 01:32:11.110 --> 01:32:11.120 align:start position:0% I both recently discussed that's the way 01:32:11.120 --> 01:32:14.530 align:start position:0% I both recently discussed that's the way the<01:32:11.240> secret<01:32:11.450> handshake<01:32:11.870> works<01:32:13.180> now<01:32:14.180> we<01:32:14.240> get<01:32:14.420> to 01:32:14.530 --> 01:32:14.540 align:start position:0% the secret handshake works now we get to 01:32:14.540 --> 01:32:16.120 align:start position:0% the secret handshake works now we get to some<01:32:14.690> of<01:32:14.720> the<01:32:14.840> interesting<01:32:15.170> stuff<01:32:15.350> so<01:32:15.740> peer 01:32:16.120 --> 01:32:16.130 align:start position:0% some of the interesting stuff so peer 01:32:16.130 --> 01:32:18.490 align:start position:0% some of the interesting stuff so peer discovery<01:32:16.610> you<01:32:17.030> can<01:32:17.210> pull<01:32:17.780> stuff<01:32:17.990> in<01:32:18.200> over<01:32:18.470> a 01:32:18.490 --> 01:32:18.500 align:start position:0% discovery you can pull stuff in over a 01:32:18.500 --> 01:32:20.200 align:start position:0% discovery you can pull stuff in over a local<01:32:18.800> network<01:32:18.890> so<01:32:19.310> that's<01:32:19.400> Bluetooth<01:32:19.910> Wi-Fi 01:32:20.200 --> 01:32:20.210 align:start position:0% local network so that's Bluetooth Wi-Fi 01:32:20.210 --> 01:32:22.480 align:start position:0% local network so that's Bluetooth Wi-Fi whatever<01:32:20.750> else<01:32:20.960> the<01:32:21.440> guy<01:32:21.560> who's<01:32:21.740> grounded<01:32:21.860> SSP 01:32:22.480 --> 01:32:22.490 align:start position:0% whatever else the guy who's grounded SSP 01:32:22.490 --> 01:32:23.860 align:start position:0% whatever else the guy who's grounded SSP actually<01:32:22.850> lives<01:32:23.060> on<01:32:23.180> a<01:32:23.210> boat<01:32:23.300> and<01:32:23.720> when<01:32:23.810> he 01:32:23.860 --> 01:32:23.870 align:start position:0% actually lives on a boat and when he 01:32:23.870 --> 01:32:26.140 align:start position:0% actually lives on a boat and when he gets<01:32:24.050> back<01:32:24.260> onto<01:32:24.470> Shore<01:32:24.830> he<01:32:25.670> connects<01:32:26.000> to<01:32:26.060> a 01:32:26.140 --> 01:32:26.150 align:start position:0% gets back onto Shore he connects to a 01:32:26.150 --> 01:32:27.790 align:start position:0% gets back onto Shore he connects to a local<01:32:26.480> Wi-Fi<01:32:26.630> instincts<01:32:27.260> all<01:32:27.380> of<01:32:27.470> this<01:32:27.560> stuff 01:32:27.790 --> 01:32:27.800 align:start position:0% local Wi-Fi instincts all of this stuff 01:32:27.800 --> 01:32:30.550 align:start position:0% local Wi-Fi instincts all of this stuff you<01:32:28.760> can<01:32:28.850> also<01:32:28.970> use<01:32:29.150> an<01:32:29.270> invite<01:32:29.510> coded<01:32:29.900> message 01:32:30.550 --> 01:32:30.560 align:start position:0% you can also use an invite coded message 01:32:30.560 --> 01:32:32.800 align:start position:0% you can also use an invite coded message and<01:32:31.070> pubs<01:32:31.610> are<01:32:31.700> important<01:32:32.150> because<01:32:32.330> following 01:32:32.800 --> 01:32:32.810 align:start position:0% and pubs are important because following 01:32:32.810 --> 01:32:34.750 align:start position:0% and pubs are important because following has<01:32:33.260> meaning<01:32:33.530> this<01:32:33.830> is<01:32:33.980> there's<01:32:34.370> one<01:32:34.430> thing 01:32:34.750 --> 01:32:34.760 align:start position:0% has meaning this is there's one thing 01:32:34.760 --> 01:32:36.250 align:start position:0% has meaning this is there's one thing that<01:32:34.820> I<01:32:35.000> want<01:32:35.180> you<01:32:35.270> to<01:32:35.300> take<01:32:35.540> away<01:32:35.690> from<01:32:35.840> this 01:32:36.250 --> 01:32:36.260 align:start position:0% that I want you to take away from this 01:32:36.260 --> 01:32:38.920 align:start position:0% that I want you to take away from this sort<01:32:36.530> of<01:32:36.560> talk<01:32:37.130> about<01:32:37.190> SSB<01:32:37.850> is<01:32:38.120> that<01:32:38.300> SSP<01:32:38.750> has 01:32:38.920 --> 01:32:38.930 align:start position:0% sort of talk about SSB is that SSP has 01:32:38.930 --> 01:32:41.740 align:start position:0% sort of talk about SSB is that SSP has baked<01:32:39.230> the<01:32:39.410> concept<01:32:39.890> to<01:32:40.040> play<01:32:40.220> the<01:32:41.210> social 01:32:41.740 --> 01:32:41.750 align:start position:0% baked the concept to play the social 01:32:41.750 --> 01:32:44.200 align:start position:0% baked the concept to play the social interactions<01:32:42.380> between<01:32:42.530> people<01:32:43.000> into<01:32:44.000> the 01:32:44.200 --> 01:32:44.210 align:start position:0% interactions between people into the 01:32:44.210 --> 01:32:46.360 align:start position:0% interactions between people into the protocol<01:32:44.690> and<01:32:45.500> the<01:32:45.560> way<01:32:45.650> it<01:32:45.770> does<01:32:45.950> that<01:32:45.980> is 01:32:46.360 --> 01:32:46.370 align:start position:0% protocol and the way it does that is 01:32:46.370 --> 01:32:49.089 align:start position:0% protocol and the way it does that is with<01:32:46.520> the<01:32:46.610> pub<01:32:47.020> and 01:32:49.089 --> 01:32:49.099 align:start position:0% with the pub and 01:32:49.099 --> 01:32:52.089 align:start position:0% with the pub and you<01:32:49.639> when<01:32:50.300> you<01:32:50.389> sign<01:32:50.630> up<01:32:50.659> for<01:32:51.079> bug<01:32:51.349> you<01:32:51.949> now 01:32:52.089 --> 01:32:52.099 align:start position:0% you when you sign up for bug you now 01:32:52.099 --> 01:32:53.740 align:start position:0% you when you sign up for bug you now have<01:32:52.280> a<01:32:52.310> pub<01:32:52.550> in<01:32:52.670> the<01:32:52.760> hub<01:32:52.909> follows<01:32:53.300> you<01:32:53.480> the 01:32:53.740 --> 01:32:53.750 align:start position:0% have a pub in the hub follows you the 01:32:53.750 --> 01:32:55.359 align:start position:0% have a pub in the hub follows you the pub<01:32:53.929> will<01:32:54.079> be<01:32:54.170> replicating<01:32:54.800> your<01:32:55.040> feed 01:32:55.359 --> 01:32:55.369 align:start position:0% pub will be replicating your feed 01:32:55.369 --> 01:32:56.950 align:start position:0% pub will be replicating your feed messages<01:32:55.849> to<01:32:56.030> existing<01:32:56.480> users<01:32:56.750> on<01:32:56.869> the 01:32:56.950 --> 01:32:56.960 align:start position:0% messages to existing users on the 01:32:56.960 --> 01:32:58.899 align:start position:0% messages to existing users on the network<01:32:56.989> when<01:32:57.920> you<01:32:58.040> saw<01:32:58.219> the<01:32:58.280> demo<01:32:58.550> apps 01:32:58.899 --> 01:32:58.909 align:start position:0% network when you saw the demo apps 01:32:58.909 --> 01:33:00.729 align:start position:0% network when you saw the demo apps coming<01:32:59.270> from<01:32:59.540> me<01:32:59.719> connecting<01:33:00.170> to<01:33:00.320> a<01:33:00.349> pub<01:33:00.590> and 01:33:00.729 --> 01:33:00.739 align:start position:0% coming from me connecting to a pub and 01:33:00.739 --> 01:33:02.260 align:start position:0% coming from me connecting to a pub and the<01:33:00.829> pub<01:33:01.040> giving<01:33:01.369> me<01:33:01.489> everybody<01:33:01.940> else's 01:33:02.260 --> 01:33:02.270 align:start position:0% the pub giving me everybody else's 01:33:02.270 --> 01:33:04.600 align:start position:0% the pub giving me everybody else's messages<01:33:02.690> and<01:33:02.869> me<01:33:02.960> cashing<01:33:03.380> them<01:33:03.530> locally<01:33:03.889> so 01:33:04.600 --> 01:33:04.610 align:start position:0% messages and me cashing them locally so 01:33:04.610 --> 01:33:06.370 align:start position:0% messages and me cashing them locally so you<01:33:04.670> end<01:33:04.880> up<01:33:05.030> the<01:33:05.659> system<01:33:06.020> that<01:33:06.139> looks<01:33:06.290> a 01:33:06.370 --> 01:33:06.380 align:start position:0% you end up the system that looks a 01:33:06.380 --> 01:33:07.629 align:start position:0% you end up the system that looks a little<01:33:06.500> bit<01:33:06.650> like<01:33:06.800> this<01:33:06.980> I<01:33:07.190> took<01:33:07.340> this<01:33:07.460> from 01:33:07.629 --> 01:33:07.639 align:start position:0% little bit like this I took this from 01:33:07.639 --> 01:33:10.780 align:start position:0% little bit like this I took this from the<01:33:07.730> SSP<01:33:08.210> website<01:33:09.250> basically<01:33:10.250> you<01:33:10.639> have<01:33:10.760> a 01:33:10.780 --> 01:33:10.790 align:start position:0% the SSP website basically you have a 01:33:10.790 --> 01:33:12.790 align:start position:0% the SSP website basically you have a user<01:33:11.090> and<01:33:11.480> you<01:33:11.869> are<01:33:11.989> seeing<01:33:12.230> messages<01:33:12.650> that 01:33:12.790 --> 01:33:12.800 align:start position:0% user and you are seeing messages that 01:33:12.800 --> 01:33:16.060 align:start position:0% user and you are seeing messages that are<01:33:12.889> n<01:33:13.070> hops<01:33:13.369> away<01:33:13.610> from<01:33:14.000> you<01:33:14.090> this<01:33:15.050> is<01:33:15.260> kind<01:33:15.980> of 01:33:16.060 --> 01:33:16.070 align:start position:0% are n hops away from you this is kind of 01:33:16.070 --> 01:33:17.950 align:start position:0% are n hops away from you this is kind of interesting<01:33:16.219> because<01:33:16.880> it<01:33:17.179> means<01:33:17.300> that<01:33:17.599> how 01:33:17.950 --> 01:33:17.960 align:start position:0% interesting because it means that how 01:33:17.960 --> 01:33:19.629 align:start position:0% interesting because it means that how many<01:33:18.020> of<01:33:18.230> you<01:33:18.409> have<01:33:18.679> gone<01:33:18.889> on<01:33:19.070> Twitter<01:33:19.340> and 01:33:19.629 --> 01:33:19.639 align:start position:0% many of you have gone on Twitter and 01:33:19.639 --> 01:33:21.310 align:start position:0% many of you have gone on Twitter and like<01:33:19.820> to<01:33:19.940> spin<01:33:20.150> bombarded<01:33:20.599> with<01:33:20.659> trolls<01:33:21.020> or 01:33:21.310 --> 01:33:21.320 align:start position:0% like to spin bombarded with trolls or 01:33:21.320 --> 01:33:22.959 align:start position:0% like to spin bombarded with trolls or people<01:33:21.560> you<01:33:21.679> don't<01:33:21.800> like<01:33:21.949> and<01:33:22.460> sort<01:33:22.670> of<01:33:22.760> things 01:33:22.959 --> 01:33:22.969 align:start position:0% people you don't like and sort of things 01:33:22.969 --> 01:33:25.810 align:start position:0% people you don't like and sort of things like<01:33:23.060> that<01:33:23.230> sort<01:33:24.230> of<01:33:24.290> see<01:33:24.500> some<01:33:24.800> nods<01:33:25.520> and 01:33:25.810 --> 01:33:25.820 align:start position:0% like that sort of see some nods and 01:33:25.820 --> 01:33:27.580 align:start position:0% like that sort of see some nods and things<01:33:25.969> along<01:33:26.090> those<01:33:26.360> lines<01:33:26.510> on<01:33:26.900> SSP<01:33:27.320> when<01:33:27.500> you 01:33:27.580 --> 01:33:27.590 align:start position:0% things along those lines on SSP when you 01:33:27.590 --> 01:33:29.050 align:start position:0% things along those lines on SSP when you block<01:33:27.829> someone<01:33:27.860> as<01:33:28.400> a<01:33:28.429> protocol<01:33:28.790> level 01:33:29.050 --> 01:33:29.060 align:start position:0% block someone as a protocol level 01:33:29.060 --> 01:33:31.060 align:start position:0% block someone as a protocol level meaning<01:33:29.360> your<01:33:30.050> client<01:33:30.469> will<01:33:30.590> refuse<01:33:31.040> to 01:33:31.060 --> 01:33:31.070 align:start position:0% meaning your client will refuse to 01:33:31.070 --> 01:33:33.189 align:start position:0% meaning your client will refuse to replicate<01:33:31.670> any<01:33:31.909> messages<01:33:32.480> that<01:33:32.540> come<01:33:32.929> from 01:33:33.189 --> 01:33:33.199 align:start position:0% replicate any messages that come from 01:33:33.199 --> 01:33:35.859 align:start position:0% replicate any messages that come from the<01:33:33.380> blocked<01:33:33.619> identity<01:33:34.130> oh<01:33:34.480> I'm<01:33:35.480> out<01:33:35.599> of<01:33:35.659> time 01:33:35.859 --> 01:33:35.869 align:start position:0% the blocked identity oh I'm out of time 01:33:35.869 --> 01:33:37.450 align:start position:0% the blocked identity oh I'm out of time can<01:33:36.110> I<01:33:36.170> go<01:33:36.290> over<01:33:36.349> for<01:33:36.710> 30<01:33:36.829> seconds<01:33:37.190> yeah<01:33:37.400> you 01:33:37.450 --> 01:33:37.460 align:start position:0% can I go over for 30 seconds yeah you 01:33:37.460 --> 01:33:39.010 align:start position:0% can I go over for 30 seconds yeah you should<01:33:37.880> you<01:33:38.030> should<01:33:38.060> and<01:33:38.389> thank<01:33:38.599> you<01:33:38.690> so<01:33:38.840> much 01:33:39.010 --> 01:33:39.020 align:start position:0% should you should and thank you so much 01:33:39.020 --> 01:33:41.620 align:start position:0% should you should and thank you so much for<01:33:39.199> doing<01:33:39.380> that<01:33:39.560> person<01:33:40.130> from<01:33:40.369> SSB<01:33:40.969> did<01:33:41.360> was 01:33:41.620 --> 01:33:41.630 align:start position:0% for doing that person from SSB did was 01:33:41.630 --> 01:33:43.810 align:start position:0% for doing that person from SSB did was not<01:33:41.869> able<01:33:42.079> to<01:33:42.199> come<01:33:42.409> to<01:33:42.469> Def<01:33:42.800> Con<01:33:43.010> last<01:33:43.040> seconds 01:33:43.810 --> 01:33:43.820 align:start position:0% not able to come to Def Con last seconds 01:33:43.820 --> 01:33:46.240 align:start position:0% not able to come to Def Con last seconds and<01:33:44.000> in<01:33:44.179> math<01:33:44.420> math<01:33:44.840> it's<01:33:45.079> like<01:33:45.139> nice<01:33:45.920> enough 01:33:46.240 --> 01:33:46.250 align:start position:0% and in math math it's like nice enough 01:33:46.250 --> 01:33:48.069 align:start position:0% and in math math it's like nice enough to<01:33:46.400> fill<01:33:46.610> in<01:33:46.760> and<01:33:47.000> the<01:33:47.239> brave<01:33:47.420> enough<01:33:47.690> to<01:33:47.750> fill 01:33:48.069 --> 01:33:48.079 align:start position:0% to fill in and the brave enough to fill 01:33:48.079 --> 01:33:50.350 align:start position:0% to fill in and the brave enough to fill in<01:33:48.230> like<01:33:48.409> on<01:33:48.650> a<01:33:48.679> very<01:33:48.949> short<01:33:49.010> notice<01:33:49.489> and<01:33:50.060> some 01:33:50.350 --> 01:33:50.360 align:start position:0% in like on a very short notice and some 01:33:50.360 --> 01:33:52.930 align:start position:0% in like on a very short notice and some are<01:33:50.480> SSB<01:33:50.960> so<01:33:51.199> yeah<01:33:51.440> yeah<01:33:51.800> yeah<01:33:52.040> Simon<01:33:52.730> by<01:33:52.880> the 01:33:52.930 --> 01:33:52.940 align:start position:0% are SSB so yeah yeah yeah Simon by the 01:33:52.940 --> 01:33:56.280 align:start position:0% are SSB so yeah yeah yeah Simon by the way<01:33:53.090> seven<01:33:53.570> seconds 01:33:56.280 --> 01:33:56.290 align:start position:0% 01:33:56.290 --> 01:33:59.200 align:start position:0% I'm<01:33:57.290> a<01:33:57.380> fan<01:33:57.590> of<01:33:57.620> SSB<01:33:58.010> I'm<01:33:58.370> not<01:33:58.730> a<01:33:58.760> core 01:33:59.200 --> 01:33:59.210 align:start position:0% I'm a fan of SSB I'm not a core 01:33:59.210 --> 01:34:01.120 align:start position:0% I'm a fan of SSB I'm not a core developer<01:33:59.300> but<01:34:00.020> I<01:34:00.260> just<01:34:00.470> think<01:34:00.620> it's<01:34:00.770> super 01:34:01.120 --> 01:34:01.130 align:start position:0% developer but I just think it's super 01:34:01.130 --> 01:34:02.560 align:start position:0% developer but I just think it's super dope<01:34:01.370> and<01:34:01.640> so<01:34:01.790> I<01:34:01.820> was<01:34:02.030> really<01:34:02.270> happy<01:34:02.450> to 01:34:02.560 --> 01:34:02.570 align:start position:0% dope and so I was really happy to 01:34:02.570 --> 01:34:03.940 align:start position:0% dope and so I was really happy to actually<01:34:02.810> be<01:34:03.080> able<01:34:03.140> to<01:34:03.320> share<01:34:03.530> with<01:34:03.650> everybody 01:34:03.940 --> 01:34:03.950 align:start position:0% actually be able to share with everybody 01:34:03.950 --> 01:34:06.520 align:start position:0% actually be able to share with everybody anyway<01:34:04.790> so<01:34:05.000> flocking<01:34:05.600> has<01:34:05.750> meaning<01:34:05.960> following 01:34:06.520 --> 01:34:06.530 align:start position:0% anyway so flocking has meaning following 01:34:06.530 --> 01:34:07.960 align:start position:0% anyway so flocking has meaning following this<01:34:06.650> meeting<01:34:06.830> you<01:34:07.130> see<01:34:07.340> the<01:34:07.520> things<01:34:07.760> that 01:34:07.960 --> 01:34:07.970 align:start position:0% this meeting you see the things that 01:34:07.970 --> 01:34:10.090 align:start position:0% this meeting you see the things that your<01:34:08.150> social<01:34:08.510> graph<01:34:08.750> wants<01:34:09.680> you<01:34:09.770> to<01:34:09.890> see 01:34:10.090 --> 01:34:10.100 align:start position:0% your social graph wants you to see 01:34:10.100 --> 01:34:11.770 align:start position:0% your social graph wants you to see because<01:34:10.400> they're<01:34:10.760> likely<01:34:11.120> to<01:34:11.150> be<01:34:11.360> like<01:34:11.540> you 01:34:11.770 --> 01:34:11.780 align:start position:0% because they're likely to be like you 01:34:11.780 --> 01:34:13.330 align:start position:0% because they're likely to be like you and<01:34:11.990> follow<01:34:12.230> people<01:34:12.470> that<01:34:12.770> are<01:34:12.860> more<01:34:12.950> likely 01:34:13.330 --> 01:34:13.340 align:start position:0% and follow people that are more likely 01:34:13.340 --> 01:34:15.670 align:start position:0% and follow people that are more likely to<01:34:13.430> be<01:34:13.520> interesting<01:34:14.120> to<01:34:14.690> you<01:34:14.900> and<01:34:15.380> blocking 01:34:15.670 --> 01:34:15.680 align:start position:0% to be interesting to you and blocking 01:34:15.680 --> 01:34:19.000 align:start position:0% to be interesting to you and blocking the<01:34:16.010> same<01:34:16.340> way<01:34:16.550> so<01:34:17.330> I<01:34:17.690> think<01:34:18.470> that's<01:34:18.710> the<01:34:18.800> speed 01:34:19.000 --> 01:34:19.010 align:start position:0% the same way so I think that's the speed 01:34:19.010 --> 01:34:20.380 align:start position:0% the same way so I think that's the speed is<01:34:19.130> the<01:34:19.160> potential<01:34:19.700> to<01:34:19.790> change<01:34:19.850> the<01:34:20.150> way<01:34:20.240> we 01:34:20.380 --> 01:34:20.390 align:start position:0% is the potential to change the way we 01:34:20.390 --> 01:34:22.480 align:start position:0% is the potential to change the way we think<01:34:20.420> about<01:34:20.750> social<01:34:21.380> networking<01:34:21.860> as<01:34:22.160> well<01:34:22.190> as 01:34:22.480 --> 01:34:22.490 align:start position:0% think about social networking as well as 01:34:22.490 --> 01:34:24.070 align:start position:0% think about social networking as well as just<01:34:22.760> social<01:34:23.150> content<01:34:23.540> on<01:34:23.690> the<01:34:23.780> web<01:34:23.930> in 01:34:24.070 --> 01:34:24.080 align:start position:0% just social content on the web in 01:34:24.080 --> 01:34:26.350 align:start position:0% just social content on the web in general<01:34:24.440> I<01:34:24.680> think<01:34:25.250> it's<01:34:25.370> definitely<01:34:25.640> worthy 01:34:26.350 --> 01:34:26.360 align:start position:0% general I think it's definitely worthy 01:34:26.360 --> 01:34:28.930 align:start position:0% general I think it's definitely worthy of<01:34:26.690> your<01:34:27.110> time<01:34:27.320> to<01:34:27.470> check<01:34:27.650> it<01:34:27.830> out<01:34:27.920> because<01:34:28.550> if 01:34:28.930 --> 01:34:28.940 align:start position:0% of your time to check it out because if 01:34:28.940 --> 01:34:30.250 align:start position:0% of your time to check it out because if there's<01:34:29.150> one<01:34:29.360> thing<01:34:29.570> that's<01:34:29.720> going<01:34:30.020> to<01:34:30.110> help 01:34:30.250 --> 01:34:30.260 align:start position:0% there's one thing that's going to help 01:34:30.260 --> 01:34:33.070 align:start position:0% there's one thing that's going to help and<01:34:30.560> the<01:34:31.070> stigma<01:34:31.490> of<01:34:31.870> decentralized<01:34:32.870> social 01:34:33.070 --> 01:34:33.080 align:start position:0% and the stigma of decentralized social 01:34:33.080 --> 01:34:35.320 align:start position:0% and the stigma of decentralized social networking<01:34:33.560> doesn't<01:34:33.890> work<01:34:34.100> it's<01:34:34.760> actually 01:34:35.320 --> 01:34:35.330 align:start position:0% networking doesn't work it's actually 01:34:35.330 --> 01:34:37.180 align:start position:0% networking doesn't work it's actually having<01:34:35.870> content<01:34:36.260> on<01:34:36.410> there<01:34:36.590> and<01:34:36.710> your<01:34:36.860> friends 01:34:37.180 --> 01:34:37.190 align:start position:0% having content on there and your friends 01:34:37.190 --> 01:34:39.220 align:start position:0% having content on there and your friends on<01:34:37.340> there<01:34:37.630> because<01:34:38.630> that's<01:34:38.750> the<01:34:38.870> number<01:34:39.110> one 01:34:39.220 --> 01:34:39.230 align:start position:0% on there because that's the number one 01:34:39.230 --> 01:34:40.720 align:start position:0% on there because that's the number one objection<01:34:39.650> that<01:34:39.740> people<01:34:39.770> have<01:34:40.160> to<01:34:40.370> any<01:34:40.460> piece 01:34:40.720 --> 01:34:40.730 align:start position:0% objection that people have to any piece 01:34:40.730 --> 01:34:42.460 align:start position:0% objection that people have to any piece exactly<01:34:41.210> and<01:34:41.660> you<01:34:41.750> should<01:34:41.870> talk<01:34:41.990> to<01:34:42.050> Frankie 01:34:42.460 --> 01:34:42.470 align:start position:0% exactly and you should talk to Frankie 01:34:42.470 --> 01:34:45.990 align:start position:0% exactly and you should talk to Frankie about<01:34:42.530> SSB<01:34:43.010> too<01:34:43.220> she<01:34:43.720> actually<01:34:44.720> works<01:34:45.110> on 01:34:45.990 --> 01:34:46.000 align:start position:0% about SSB too she actually works on 01:34:46.000 --> 01:34:48.430 align:start position:0% about SSB too she actually works on that's<01:34:47.000> all<01:34:47.120> the<01:34:47.180> time<01:34:47.360> I<01:34:47.450> got<01:34:47.570> identify 01:34:48.430 --> 01:34:48.440 align:start position:0% that's all the time I got identify 01:34:48.440 --> 01:34:55.580 align:start position:0% that's all the time I got identify yourself 01:34:55.580 --> 01:34:55.590 align:start position:0% 01:34:55.590 --> 01:34:57.690 align:start position:0% thanks<01:34:56.590> everyone<01:34:57.010> oh<01:34:57.160> this<01:34:57.370> is<01:34:57.490> gonna<01:34:57.610> be 01:34:57.690 --> 01:34:57.700 align:start position:0% thanks everyone oh this is gonna be 01:34:57.700 --> 01:34:59.580 align:start position:0% thanks everyone oh this is gonna be really<01:34:58.030> exciting<01:34:58.780> because<01:34:58.930> I'm<01:34:59.200> we're<01:34:59.440> all 01:34:59.580 --> 01:34:59.590 align:start position:0% really exciting because I'm we're all 01:34:59.590 --> 01:35:01.560 align:start position:0% really exciting because I'm we're all used<01:34:59.770> to<01:34:59.890> demos<01:35:00.340> failing<01:35:00.850> well<01:35:01.030> haven't<01:35:01.420> seen 01:35:01.560 --> 01:35:01.570 align:start position:0% used to demos failing well haven't seen 01:35:01.570 --> 01:35:04.170 align:start position:0% used to demos failing well haven't seen the<01:35:01.690> kind<01:35:01.840> of<01:35:01.930> catastrophic<01:35:02.320> failure<01:35:03.180> scaling 01:35:04.170 --> 01:35:04.180 align:start position:0% the kind of catastrophic failure scaling 01:35:04.180 --> 01:35:06.690 align:start position:0% the kind of catastrophic failure scaling all<01:35:04.330> morning<01:35:04.690> so<01:35:05.380> it'd<01:35:05.920> be<01:35:06.040> good<01:35:06.220> to<01:35:06.280> get<01:35:06.580> this 01:35:06.690 --> 01:35:06.700 align:start position:0% all morning so it'd be good to get this 01:35:06.700 --> 01:35:08.220 align:start position:0% all morning so it'd be good to get this out<01:35:06.880> of<01:35:06.910> the<01:35:07.030> way<01:35:07.210> now<01:35:07.450> I'm<01:35:07.840> gonna<01:35:07.990> do<01:35:08.200> a 01:35:08.220 --> 01:35:08.230 align:start position:0% out of the way now I'm gonna do a 01:35:08.230 --> 01:35:11.490 align:start position:0% out of the way now I'm gonna do a mainstage<01:35:09.220> talk<01:35:09.520> on<01:35:09.880> and<01:35:10.540> I'll<01:35:11.200> go<01:35:11.350> quickly 01:35:11.490 --> 01:35:11.500 align:start position:0% mainstage talk on and I'll go quickly 01:35:11.500 --> 01:35:13.980 align:start position:0% mainstage talk on and I'll go quickly through<01:35:11.680> a<01:35:11.890> couple<01:35:12.040> of<01:35:12.190> things<01:35:12.370> so<01:35:12.670> I'm<01:35:13.270> -<01:35:13.660> rich 01:35:13.980 --> 01:35:13.990 align:start position:0% through a couple of things so I'm - rich 01:35:13.990 --> 01:35:15.090 align:start position:0% through a couple of things so I'm - rich Gordon<01:35:14.320> I<01:35:14.380> work<01:35:14.560> on<01:35:14.680> a<01:35:14.740> project<01:35:14.770> called 01:35:15.090 --> 01:35:15.100 align:start position:0% Gordon I work on a project called 01:35:15.100 --> 01:35:16.860 align:start position:0% Gordon I work on a project called wireline<01:35:15.670> we're<01:35:16.000> building<01:35:16.300> a<01:35:16.390> new<01:35:16.420> kind<01:35:16.750> of 01:35:16.860 --> 01:35:16.870 align:start position:0% wireline we're building a new kind of 01:35:16.870 --> 01:35:18.750 align:start position:0% wireline we're building a new kind of peer-to-peer<01:35:17.200> network<01:35:18.010> and<01:35:18.550> they're<01:35:18.640> gonna 01:35:18.750 --> 01:35:18.760 align:start position:0% peer-to-peer network and they're gonna 01:35:18.760 --> 01:35:21.630 align:start position:0% peer-to-peer network and they're gonna demonstrate<01:35:19.000> today<01:35:20.010> quickly<01:35:21.010> how<01:35:21.340> we<01:35:21.400> can 01:35:21.630 --> 01:35:21.640 align:start position:0% demonstrate today quickly how we can 01:35:21.640 --> 01:35:24.090 align:start position:0% demonstrate today quickly how we can build<01:35:21.790> applications<01:35:22.120> that<01:35:22.900> might<01:35:23.620> enable<01:35:23.860> us 01:35:24.090 --> 01:35:24.100 align:start position:0% build applications that might enable us 01:35:24.100 --> 01:35:25.620 align:start position:0% build applications that might enable us to<01:35:24.130> stop<01:35:24.460> using<01:35:24.640> things<01:35:24.940> like<01:35:25.150> Google<01:35:25.480> Docs 01:35:25.620 --> 01:35:25.630 align:start position:0% to stop using things like Google Docs 01:35:25.630 --> 01:35:28.440 align:start position:0% to stop using things like Google Docs and<01:35:25.990> I<01:35:26.320> was<01:35:26.770> involved<01:35:27.100> in<01:35:27.370> group<01:35:27.580> building 01:35:28.440 --> 01:35:28.450 align:start position:0% and I was involved in group building 01:35:28.450 --> 01:35:30.570 align:start position:0% and I was involved in group building technologies<01:35:28.990> that<01:35:29.110> Google<01:35:29.380> Docs<01:35:29.530> Google<01:35:29.830> I'm 01:35:30.570 --> 01:35:30.580 align:start position:0% technologies that Google Docs Google I'm 01:35:30.580 --> 01:35:31.680 align:start position:0% technologies that Google Docs Google I'm going<01:35:30.790> to<01:35:30.850> go<01:35:30.910> through<01:35:31.120> all<01:35:31.150> these<01:35:31.360> slides 01:35:31.680 --> 01:35:31.690 align:start position:0% going to go through all these slides 01:35:31.690 --> 01:35:35.790 align:start position:0% going to go through all these slides just<01:35:32.020> quickly<01:35:34.260> building<01:35:35.260> that's<01:35:35.440> it's<01:35:35.740> hard 01:35:35.790 --> 01:35:35.800 align:start position:0% just quickly building that's it's hard 01:35:35.800 --> 01:35:37.620 align:start position:0% just quickly building that's it's hard building<01:35:36.430> apps<01:35:36.640> of<01:35:36.820> internet<01:35:37.210> scale<01:35:37.480> is 01:35:37.620 --> 01:35:37.630 align:start position:0% building apps of internet scale is 01:35:37.630 --> 01:35:39.270 align:start position:0% building apps of internet scale is really<01:35:37.930> hard<01:35:38.140> and<01:35:38.320> building<01:35:38.590> decentralized 01:35:39.270 --> 01:35:39.280 align:start position:0% really hard and building decentralized 01:35:39.280 --> 01:35:42.150 align:start position:0% really hard and building decentralized apps<01:35:39.520> it's<01:35:40.420> much<01:35:40.810> much<01:35:41.080> more<01:35:41.140> difficult<01:35:41.950> so<01:35:42.130> I 01:35:42.150 --> 01:35:42.160 align:start position:0% apps it's much much more difficult so I 01:35:42.160 --> 01:35:44.640 align:start position:0% apps it's much much more difficult so I thought<01:35:42.640> just<01:35:43.330> as<01:35:43.480> a<01:35:43.510> start<01:35:43.900> we<01:35:44.200> do<01:35:44.350> a<01:35:44.380> thought 01:35:44.640 --> 01:35:44.650 align:start position:0% thought just as a start we do a thought 01:35:44.650 --> 01:35:46.290 align:start position:0% thought just as a start we do a thought experiment<01:35:45.010> about<01:35:45.370> the<01:35:45.760> kinds<01:35:46.210> of 01:35:46.290 --> 01:35:46.300 align:start position:0% experiment about the kinds of 01:35:46.300 --> 01:35:48.240 align:start position:0% experiment about the kinds of technologies<01:35:46.930> we're<01:35:47.110> going<01:35:47.230> to<01:35:47.290> need<01:35:47.470> in 01:35:48.240 --> 01:35:48.250 align:start position:0% technologies we're going to need in 01:35:48.250 --> 01:35:50.010 align:start position:0% technologies we're going to need in order<01:35:48.460> to<01:35:48.610> rebuild<01:35:49.030> with<01:35:49.360> internet<01:35:49.840> scale 01:35:50.010 --> 01:35:50.020 align:start position:0% order to rebuild with internet scale 01:35:50.020 --> 01:35:52.740 align:start position:0% order to rebuild with internet scale applications<01:35:50.650> so<01:35:51.190> we<01:35:51.940> need<01:35:52.120> new<01:35:52.450> kinds<01:35:52.690> of 01:35:52.740 --> 01:35:52.750 align:start position:0% applications so we need new kinds of 01:35:52.750 --> 01:35:55.160 align:start position:0% applications so we need new kinds of networks<01:35:53.160> data<01:35:54.160> is<01:35:54.400> probably<01:35:54.610> the<01:35:54.730> most 01:35:55.160 --> 01:35:55.170 align:start position:0% networks data is probably the most 01:35:55.170 --> 01:35:58.220 align:start position:0% networks data is probably the most important<01:35:56.170> and<01:35:56.320> difficult<01:35:56.500> thing<01:35:56.980> to<01:35:57.130> solve 01:35:58.220 --> 01:35:58.230 align:start position:0% important and difficult thing to solve 01:35:58.230 --> 01:36:01.470 align:start position:0% important and difficult thing to solve where<01:35:59.230> do<01:35:59.320> we<01:35:59.440> run<01:35:59.980> long-running<01:36:00.550> favor 01:36:01.470 --> 01:36:01.480 align:start position:0% where do we run long-running favor 01:36:01.480 --> 01:36:03.720 align:start position:0% where do we run long-running favor intense<01:36:01.870> computations<01:36:02.710> and<01:36:03.100> how<01:36:03.430> do<01:36:03.490> we<01:36:03.610> deal 01:36:03.720 --> 01:36:03.730 align:start position:0% intense computations and how do we deal 01:36:03.730 --> 01:36:05.130 align:start position:0% intense computations and how do we deal with<01:36:03.760> identity<01:36:04.270> so<01:36:04.570> quickly<01:36:04.900> going<01:36:05.050> through 01:36:05.130 --> 01:36:05.140 align:start position:0% with identity so quickly going through 01:36:05.140 --> 01:36:08.250 align:start position:0% with identity so quickly going through these<01:36:05.640> if<01:36:06.640> we<01:36:06.700> were<01:36:07.060> running<01:36:07.510> Google<01:36:08.050> Docs 01:36:08.250 --> 01:36:08.260 align:start position:0% these if we were running Google Docs 01:36:08.260 --> 01:36:11.100 align:start position:0% these if we were running Google Docs here<01:36:08.620> today<01:36:08.940> all<01:36:09.940> of<01:36:09.970> our<01:36:10.210> keystrokes<01:36:10.780> would 01:36:11.100 --> 01:36:11.110 align:start position:0% here today all of our keystrokes would 01:36:11.110 --> 01:36:12.510 align:start position:0% here today all of our keystrokes would be<01:36:11.260> going<01:36:11.410> through<01:36:11.650> a<01:36:11.680> server<01:36:11.980> in<01:36:12.130> Mountain 01:36:12.510 --> 01:36:12.520 align:start position:0% be going through a server in Mountain 01:36:12.520 --> 01:36:13.290 align:start position:0% be going through a server in Mountain View<01:36:12.580> California 01:36:13.290 --> 01:36:13.300 align:start position:0% View California 01:36:13.300 --> 01:36:15.780 align:start position:0% View California or<01:36:13.480> perhaps<01:36:13.630> Tokyo<01:36:14.140> they're<01:36:14.980> not<01:36:15.190> and<01:36:15.700> if 01:36:15.780 --> 01:36:15.790 align:start position:0% or perhaps Tokyo they're not and if 01:36:15.790 --> 01:36:16.500 align:start position:0% or perhaps Tokyo they're not and if they're<01:36:15.970> going<01:36:16.120> to<01:36:16.180> be<01:36:16.270> going<01:36:16.390> through 01:36:16.500 --> 01:36:16.510 align:start position:0% they're going to be going through 01:36:16.510 --> 01:36:19.020 align:start position:0% they're going to be going through infrastructure<01:36:17.320> across<01:36:17.950> the<01:36:18.070> internet<01:36:18.640> and 01:36:19.020 --> 01:36:19.030 align:start position:0% infrastructure across the internet and 01:36:19.030 --> 01:36:22.680 align:start position:0% infrastructure across the internet and this<01:36:19.210> makes<01:36:19.480> absolutely<01:36:20.140> no<01:36:20.290> sense<01:36:20.520> so<01:36:21.690> we're 01:36:22.680 --> 01:36:22.690 align:start position:0% this makes absolutely no sense so we're 01:36:22.690 --> 01:36:23.880 align:start position:0% this makes absolutely no sense so we're starting<01:36:22.840> to<01:36:23.080> have<01:36:23.170> different<01:36:23.590> kinds<01:36:23.830> of 01:36:23.880 --> 01:36:23.890 align:start position:0% starting to have different kinds of 01:36:23.890 --> 01:36:25.620 align:start position:0% starting to have different kinds of technologies<01:36:24.490> for<01:36:24.760> peer-to-peer<01:36:24.970> we've<01:36:25.480> got 01:36:25.620 --> 01:36:25.630 align:start position:0% technologies for peer-to-peer we've got 01:36:25.630 --> 01:36:28.770 align:start position:0% technologies for peer-to-peer we've got the<01:36:25.750> BJP<01:36:26.290> with<01:36:26.500> WebRTC<01:36:27.360> there's<01:36:28.360> still<01:36:28.540> a<01:36:28.570> big 01:36:28.770 --> 01:36:28.780 align:start position:0% the BJP with WebRTC there's still a big 01:36:28.780 --> 01:36:30.360 align:start position:0% the BJP with WebRTC there's still a big chat<01:36:29.050> challenge<01:36:29.590> getting<01:36:29.950> this<01:36:30.040> towards 01:36:30.360 --> 01:36:30.370 align:start position:0% chat challenge getting this towards 01:36:30.370 --> 01:36:33.810 align:start position:0% chat challenge getting this towards seamlessly<01:36:30.940> in<01:36:31.030> the<01:36:31.060> browser<01:36:31.360> so<01:36:32.400> we<01:36:33.400> need<01:36:33.550> at 01:36:33.810 --> 01:36:33.820 align:start position:0% seamlessly in the browser so we need at 01:36:33.820 --> 01:36:35.520 align:start position:0% seamlessly in the browser so we need at least<01:36:33.880> additional<01:36:34.870> infrastructure<01:36:35.290> like 01:36:35.520 --> 01:36:35.530 align:start position:0% least additional infrastructure like 01:36:35.530 --> 01:36:36.950 align:start position:0% least additional infrastructure like stun<01:36:35.860> and<01:36:36.220> turns 01:36:36.950 --> 01:36:36.960 align:start position:0% stun and turns 01:36:36.960 --> 01:36:38.450 align:start position:0% stun and turns did<01:36:37.200> not<01:36:37.320> traversal<01:36:38.010> and<01:36:38.100> to<01:36:38.190> do<01:36:38.310> with 01:36:38.450 --> 01:36:38.460 align:start position:0% did not traversal and to do with 01:36:38.460 --> 01:36:41.060 align:start position:0% did not traversal and to do with firewalls<01:36:38.990> but<01:36:39.990> we<01:36:40.080> also<01:36:40.230> need<01:36:40.440> the<01:36:40.470> HDS<01:36:40.920> and 01:36:41.060 --> 01:36:41.070 align:start position:0% firewalls but we also need the HDS and 01:36:41.070 --> 01:36:42.380 align:start position:0% firewalls but we also need the HDS and signal<01:36:41.370> service<01:36:41.550> and<01:36:41.880> the<01:36:41.940> different<01:36:42.210> peers 01:36:42.380 --> 01:36:42.390 align:start position:0% signal service and the different peers 01:36:42.390 --> 01:36:44.180 align:start position:0% signal service and the different peers can<01:36:42.600> find<01:36:42.900> each<01:36:43.050> other<01:36:43.320> we<01:36:43.740> need<01:36:43.830> to<01:36:43.950> do<01:36:44.070> this 01:36:44.180 --> 01:36:44.190 align:start position:0% can find each other we need to do this 01:36:44.190 --> 01:36:46.220 align:start position:0% can find each other we need to do this in<01:36:44.370> a<01:36:44.430> way<01:36:44.580> that<01:36:44.610> doesn't<01:36:45.360> reduce<01:36:45.930> any 01:36:46.220 --> 01:36:46.230 align:start position:0% in a way that doesn't reduce any 01:36:46.230 --> 01:36:48.650 align:start position:0% in a way that doesn't reduce any centralized<01:36:46.710> dependencies<01:36:47.340> if<01:36:48.270> we<01:36:48.510> were 01:36:48.650 --> 01:36:48.660 align:start position:0% centralized dependencies if we were 01:36:48.660 --> 01:36:50.450 align:start position:0% centralized dependencies if we were building<01:36:49.140> on<01:36:49.260> the<01:36:49.380> cloud<01:36:49.590> today<01:36:49.890> we've<01:36:50.340> got 01:36:50.450 --> 01:36:50.460 align:start position:0% building on the cloud today we've got 01:36:50.460 --> 01:36:53.020 align:start position:0% building on the cloud today we've got dozens<01:36:51.270> of<01:36:51.510> different<01:36:51.660> databases<01:36:52.230> managers 01:36:53.020 --> 01:36:53.030 align:start position:0% dozens of different databases managers 01:36:53.030 --> 01:36:57.560 align:start position:0% dozens of different databases managers MongoDB<01:36:54.530> DynamoDB<01:36:55.530> Google<01:36:55.980> cloud<01:36:56.220> of<01:36:56.700> big 01:36:57.560 --> 01:36:57.570 align:start position:0% MongoDB DynamoDB Google cloud of big 01:36:57.570 --> 01:37:00.500 align:start position:0% MongoDB DynamoDB Google cloud of big table<01:36:58.020> s3<01:36:58.790> but<01:36:59.790> we<01:36:59.880> have<01:36:59.970> to<01:37:00.060> give<01:37:00.210> up<01:37:00.330> all<01:37:00.450> of 01:37:00.500 --> 01:37:00.510 align:start position:0% table s3 but we have to give up all of 01:37:00.510 --> 01:37:01.670 align:start position:0% table s3 but we have to give up all of that<01:37:00.720> if<01:37:00.810> we're<01:37:00.930> going<01:37:01.020> to<01:37:01.080> build<01:37:01.230> this<01:37:01.470> on<01:37:01.620> a 01:37:01.670 --> 01:37:01.680 align:start position:0% that if we're going to build this on a 01:37:01.680 --> 01:37:03.290 align:start position:0% that if we're going to build this on a peer-to-peer<01:37:01.920> network<01:37:01.950> and<01:37:02.760> we've<01:37:02.880> got<01:37:03.060> now 01:37:03.290 --> 01:37:03.300 align:start position:0% peer-to-peer network and we've got now 01:37:03.300 --> 01:37:06.710 align:start position:0% peer-to-peer network and we've got now you<01:37:03.630> know<01:37:04.290> starting<01:37:04.830> ten<01:37:05.610> years<01:37:05.820> ago<01:37:06.060> maybe 01:37:06.710 --> 01:37:06.720 align:start position:0% you know starting ten years ago maybe 01:37:06.720 --> 01:37:10.580 align:start position:0% you know starting ten years ago maybe before<01:37:07.080> that<01:37:07.320> victim<01:37:08.390> demonstrated<01:37:09.590> stable 01:37:10.580 --> 01:37:10.590 align:start position:0% before that victim demonstrated stable 01:37:10.590 --> 01:37:12.470 align:start position:0% before that victim demonstrated stable file<01:37:11.130> exchange<01:37:11.640> will<01:37:12.210> that<01:37:12.330> require 01:37:12.470 --> 01:37:12.480 align:start position:0% file exchange will that require 01:37:12.480 --> 01:37:15.560 align:start position:0% file exchange will that require decentralized<01:37:13.260> index<01:37:14.060> and<01:37:15.060> now<01:37:15.240> we're<01:37:15.420> moving 01:37:15.560 --> 01:37:15.570 align:start position:0% decentralized index and now we're moving 01:37:15.570 --> 01:37:18.290 align:start position:0% decentralized index and now we're moving rapidly<01:37:15.930> towards<01:37:16.740> okay<01:37:17.490> the<01:37:17.550> peer<01:37:17.820> protocols 01:37:18.290 --> 01:37:18.300 align:start position:0% rapidly towards okay the peer protocols 01:37:18.300 --> 01:37:20.870 align:start position:0% rapidly towards okay the peer protocols like<01:37:18.510> that<01:37:18.810> and<01:37:19.170> secure<01:37:19.530> scuttlebutt<01:37:20.160> to<01:37:20.730> give 01:37:20.870 --> 01:37:20.880 align:start position:0% like that and secure scuttlebutt to give 01:37:20.880 --> 01:37:22.580 align:start position:0% like that and secure scuttlebutt to give us<01:37:21.000> access<01:37:21.180> to<01:37:21.360> real-time<01:37:21.690> date<01:37:22.170> so<01:37:22.350> they<01:37:22.470> can 01:37:22.580 --> 01:37:22.590 align:start position:0% us access to real-time date so they can 01:37:22.590 --> 01:37:24.770 align:start position:0% us access to real-time date so they can be<01:37:22.680> securely<01:37:23.070> exchanged<01:37:23.760> but<01:37:24.300> we<01:37:24.420> still<01:37:24.600> have 01:37:24.770 --> 01:37:24.780 align:start position:0% be securely exchanged but we still have 01:37:24.780 --> 01:37:26.900 align:start position:0% be securely exchanged but we still have a<01:37:24.810> fundamental<01:37:25.440> problem<01:37:25.650> which<01:37:25.950> is<01:37:26.130> if<01:37:26.520> we've 01:37:26.900 --> 01:37:26.910 align:start position:0% a fundamental problem which is if we've 01:37:26.910 --> 01:37:28.790 align:start position:0% a fundamental problem which is if we've got<01:37:27.060> concurrency<01:37:27.840> we've<01:37:28.230> got<01:37:28.350> multiple 01:37:28.790 --> 01:37:28.800 align:start position:0% got concurrency we've got multiple 01:37:28.800 --> 01:37:30.380 align:start position:0% got concurrency we've got multiple people<01:37:28.920> editing<01:37:29.220> the<01:37:29.640> same<01:37:29.820> document<01:37:29.880> at<01:37:30.330> the 01:37:30.380 --> 01:37:30.390 align:start position:0% people editing the same document at the 01:37:30.390 --> 01:37:33.170 align:start position:0% people editing the same document at the same<01:37:30.450> time<01:37:30.900> how<01:37:31.470> do<01:37:31.530> we<01:37:31.740> merge<01:37:32.220> the<01:37:32.250> data<01:37:32.760> so 01:37:33.170 --> 01:37:33.180 align:start position:0% same time how do we merge the data so 01:37:33.180 --> 01:37:36.129 align:start position:0% same time how do we merge the data so that<01:37:33.210> we've<01:37:34.140> got<01:37:34.260> a<01:37:34.290> consistent<01:37:34.860> view<01:37:35.010> of 01:37:36.129 --> 01:37:36.139 align:start position:0% that we've got a consistent view of 01:37:36.139 --> 01:37:38.169 align:start position:0% that we've got a consistent view of the<01:37:36.679> way<01:37:36.770> Google<01:37:37.100> does<01:37:37.130> this<01:37:37.460> pioneer 01:37:38.169 --> 01:37:38.179 align:start position:0% the way Google does this pioneer 01:37:38.179 --> 01:37:39.750 align:start position:0% the way Google does this pioneer technology<01:37:38.750> called<01:37:38.929> operational 01:37:39.750 --> 01:37:39.760 align:start position:0% technology called operational 01:37:39.760 --> 01:37:47.260 align:start position:0% technology called operational transformations<01:37:42.940> thank<01:37:43.940> you<01:37:44.090> I'll<01:37:44.300> try<01:37:46.239> okay 01:37:47.260 --> 01:37:47.270 align:start position:0% transformations thank you I'll try okay 01:37:47.270 --> 01:37:52.240 align:start position:0% transformations thank you I'll try okay apologies<01:37:48.050> sir<01:37:48.080> one<01:37:48.409> at<01:37:48.500> the<01:37:48.560> front<01:37:51.219> good 01:37:52.240 --> 01:37:52.250 align:start position:0% apologies sir one at the front good 01:37:52.250 --> 01:37:53.919 align:start position:0% apologies sir one at the front good Google<01:37:52.699> pioneer<01:37:53.179> the<01:37:53.239> technology<01:37:53.719> little 01:37:53.919 --> 01:37:53.929 align:start position:0% Google pioneer the technology little 01:37:53.929 --> 01:37:56.140 align:start position:0% Google pioneer the technology little operational<01:37:54.590> transformations<01:37:55.250> ot<01:37:55.760> and<01:37:56.030> this 01:37:56.140 --> 01:37:56.150 align:start position:0% operational transformations ot and this 01:37:56.150 --> 01:37:58.180 align:start position:0% operational transformations ot and this is<01:37:56.270> actually<01:37:56.570> from<01:37:56.750> a<01:37:56.840> project<01:37:57.320> some<01:37:57.860> might 01:37:58.180 --> 01:37:58.190 align:start position:0% is actually from a project some might 01:37:58.190 --> 01:38:00.910 align:start position:0% is actually from a project some might remember<01:37:58.460> called<01:37:58.760> Google<01:37:59.060> Wave<01:37:59.350> ot<01:38:00.350> is<01:38:00.679> an 01:38:00.910 --> 01:38:00.920 align:start position:0% remember called Google Wave ot is an 01:38:00.920 --> 01:38:03.100 align:start position:0% remember called Google Wave ot is an eventual<01:38:01.219> consistency<01:38:01.600> protocol<01:38:02.600> that 01:38:03.100 --> 01:38:03.110 align:start position:0% eventual consistency protocol that 01:38:03.110 --> 01:38:05.020 align:start position:0% eventual consistency protocol that requires<01:38:03.409> a<01:38:03.530> centralized<01:38:04.040> server<01:38:04.310> where 01:38:05.020 --> 01:38:05.030 align:start position:0% requires a centralized server where 01:38:05.030 --> 01:38:07.180 align:start position:0% requires a centralized server where essentially<01:38:05.389> instead<01:38:05.719> of<01:38:06.010> obviously<01:38:07.010> we 01:38:07.180 --> 01:38:07.190 align:start position:0% essentially instead of obviously we 01:38:07.190 --> 01:38:08.530 align:start position:0% essentially instead of obviously we don't<01:38:07.369> send<01:38:07.639> the<01:38:07.730> whole<01:38:07.880> document<01:38:08.300> to<01:38:08.449> the 01:38:08.530 --> 01:38:08.540 align:start position:0% don't send the whole document to the 01:38:08.540 --> 01:38:10.209 align:start position:0% don't send the whole document to the server<01:38:08.780> becoming<01:38:09.170> edison<01:38:09.590> we<01:38:09.739> send<01:38:10.010> a 01:38:10.209 --> 01:38:10.219 align:start position:0% server becoming edison we send a 01:38:10.219 --> 01:38:13.750 align:start position:0% server becoming edison we send a mutation<01:38:10.880> and<01:38:11.750> what<01:38:11.900> OT<01:38:12.260> does<01:38:12.530> is<01:38:13.159> a<01:38:13.219> lecture 01:38:13.750 --> 01:38:13.760 align:start position:0% mutation and what OT does is a lecture 01:38:13.760 --> 01:38:16.540 align:start position:0% mutation and what OT does is a lecture that<01:38:14.030> the<01:38:14.239> server<01:38:14.690> is<01:38:14.989> able<01:38:15.560> to<01:38:15.830> rewrite<01:38:16.489> that 01:38:16.540 --> 01:38:16.550 align:start position:0% that the server is able to rewrite that 01:38:16.550 --> 01:38:18.879 align:start position:0% that the server is able to rewrite that mutation<01:38:17.360> so<01:38:17.900> it<01:38:17.989> can<01:38:18.139> be<01:38:18.560> applied 01:38:18.879 --> 01:38:18.889 align:start position:0% mutation so it can be applied 01:38:18.889 --> 01:38:21.790 align:start position:0% mutation so it can be applied commutatively<01:38:19.850> in<01:38:20.239> any<01:38:20.480> order<01:38:20.900> and<01:38:21.170> that 01:38:21.790 --> 01:38:21.800 align:start position:0% commutatively in any order and that 01:38:21.800 --> 01:38:22.629 align:start position:0% commutatively in any order and that means<01:38:22.010> we<01:38:22.100> can<01:38:22.219> have<01:38:22.250> lots<01:38:22.460> of<01:38:22.550> different 01:38:22.629 --> 01:38:22.639 align:start position:0% means we can have lots of different 01:38:22.639 --> 01:38:25.209 align:start position:0% means we can have lots of different peers<01:38:23.000> somewhere<01:38:23.389> across<01:38:23.780> the<01:38:23.900> network<01:38:24.350> some 01:38:25.209 --> 01:38:25.219 align:start position:0% peers somewhere across the network some 01:38:25.219 --> 01:38:28.750 align:start position:0% peers somewhere across the network some online<01:38:25.610> some<01:38:25.909> offline<01:38:27.040> keeping<01:38:28.040> a<01:38:28.130> local<01:38:28.520> log 01:38:28.750 --> 01:38:28.760 align:start position:0% online some offline keeping a local log 01:38:28.760 --> 01:38:30.939 align:start position:0% online some offline keeping a local log of<01:38:28.940> all<01:38:29.060> of<01:38:29.179> the<01:38:29.270> mutations<01:38:29.810> and<01:38:30.199> then<01:38:30.619> at<01:38:30.770> some 01:38:30.939 --> 01:38:30.949 align:start position:0% of all of the mutations and then at some 01:38:30.949 --> 01:38:32.500 align:start position:0% of all of the mutations and then at some point<01:38:31.010> they<01:38:31.340> can<01:38:31.520> push<01:38:31.730> those<01:38:31.969> to<01:38:32.119> the<01:38:32.210> server 01:38:32.500 --> 01:38:32.510 align:start position:0% point they can push those to the server 01:38:32.510 --> 01:38:34.629 align:start position:0% point they can push those to the server and<01:38:32.690> the<01:38:32.780> server<01:38:32.810> will<01:38:33.139> reconcile<01:38:33.920> them<01:38:34.159> kind 01:38:34.629 --> 01:38:34.639 align:start position:0% and the server will reconcile them kind 01:38:34.639 --> 01:38:37.300 align:start position:0% and the server will reconcile them kind of<01:38:34.699> like<01:38:34.820> a<01:38:34.850> dynamic<01:38:35.150> get<01:38:35.780> but<01:38:36.679> since<01:38:36.920> I<01:38:37.040> said 01:38:37.300 --> 01:38:37.310 align:start position:0% of like a dynamic get but since I said 01:38:37.310 --> 01:38:38.620 align:start position:0% of like a dynamic get but since I said so<01:38:37.699> how<01:38:37.730> do<01:38:37.909> we<01:38:38.030> do<01:38:38.150> that<01:38:38.300> in<01:38:38.449> peer-to-peer 01:38:38.620 --> 01:38:38.630 align:start position:0% so how do we do that in peer-to-peer 01:38:38.630 --> 01:38:40.959 align:start position:0% so how do we do that in peer-to-peer network<01:38:39.230> well<01:38:39.440> there<01:38:39.590> are<01:38:39.710> new<01:38:39.969> technologies 01:38:40.959 --> 01:38:40.969 align:start position:0% network well there are new technologies 01:38:40.969 --> 01:38:43.540 align:start position:0% network well there are new technologies called<01:38:41.750> conflict<01:38:42.199> free<01:38:42.650> replicated<01:38:43.429> data 01:38:43.540 --> 01:38:43.550 align:start position:0% called conflict free replicated data 01:38:43.550 --> 01:38:45.310 align:start position:0% called conflict free replicated data types<01:38:43.940> and<01:38:44.210> trouble<01:38:44.600> saying<01:38:44.810> that<01:38:44.960> sometimes 01:38:45.310 --> 01:38:45.320 align:start position:0% types and trouble saying that sometimes 01:38:45.320 --> 01:38:48.070 align:start position:0% types and trouble saying that sometimes CID<01:38:46.070> T's<01:38:46.310> which<01:38:47.150> enable<01:38:47.570> these<01:38:47.659> kinds<01:38:47.989> of 01:38:48.070 --> 01:38:48.080 align:start position:0% CID T's which enable these kinds of 01:38:48.080 --> 01:38:49.899 align:start position:0% CID T's which enable these kinds of algorithms<01:38:48.320> to<01:38:48.590> work<01:38:48.860> in<01:38:49.130> peers<01:38:49.520> but<01:38:49.790> they 01:38:49.899 --> 01:38:49.909 align:start position:0% algorithms to work in peers but they 01:38:49.909 --> 01:38:51.149 align:start position:0% algorithms to work in peers but they have<01:38:50.090> some<01:38:50.300> challenges 01:38:51.149 --> 01:38:51.159 align:start position:0% have some challenges 01:38:51.159 --> 01:38:54.629 align:start position:0% have some challenges there's<01:38:52.389> scalability<01:38:53.389> problems<01:38:53.869> and 01:38:54.629 --> 01:38:54.639 align:start position:0% there's scalability problems and 01:38:54.639 --> 01:38:56.800 align:start position:0% there's scalability problems and security<01:38:55.639> issues<01:38:55.969> and<01:38:56.150> so<01:38:56.300> there's<01:38:56.480> still<01:38:56.750> a 01:38:56.800 --> 01:38:56.810 align:start position:0% security issues and so there's still a 01:38:56.810 --> 01:38:59.919 align:start position:0% security issues and so there's still a lot<01:38:57.020> to<01:38:57.199> solve<01:38:57.469> there<01:38:58.600> you<01:38:59.600> said<01:38:59.750> to<01:38:59.840> us 01:38:59.919 --> 01:38:59.929 align:start position:0% lot to solve there you said to us 01:38:59.929 --> 01:39:01.209 align:start position:0% lot to solve there you said to us compute<01:39:00.260> everything's<01:39:00.739> happening<01:39:01.040> in<01:39:01.159> the 01:39:01.209 --> 01:39:01.219 align:start position:0% compute everything's happening in the 01:39:01.219 --> 01:39:05.649 align:start position:0% compute everything's happening in the cloud<01:39:01.429> today<01:39:02.020> as<01:39:03.020> a<01:39:03.350> obviously<01:39:04.340> for<01:39:04.670> problems 01:39:05.649 --> 01:39:05.659 align:start position:0% cloud today as a obviously for problems 01:39:05.659 --> 01:39:07.689 align:start position:0% cloud today as a obviously for problems we<01:39:05.929> have<01:39:06.080> where<01:39:06.320> we<01:39:06.409> need<01:39:06.560> global<01:39:07.010> consensus 01:39:07.689 --> 01:39:07.699 align:start position:0% we have where we need global consensus 01:39:07.699 --> 01:39:09.790 align:start position:0% we have where we need global consensus we're<01:39:07.850> gonna<01:39:07.969> use<01:39:08.150> blob<01:39:08.389> trains<01:39:08.719> but<01:39:09.619> that's 01:39:09.790 --> 01:39:09.800 align:start position:0% we're gonna use blob trains but that's 01:39:09.800 --> 01:39:11.410 align:start position:0% we're gonna use blob trains but that's not<01:39:09.920> a<01:39:09.949> proper<01:39:10.310> appropriate<01:39:10.820> for<01:39:11.300> all 01:39:11.410 --> 01:39:11.420 align:start position:0% not a proper appropriate for all 01:39:11.420 --> 01:39:14.260 align:start position:0% not a proper appropriate for all computers<01:39:12.170> cases<01:39:12.619> I<01:39:12.800> mean<01:39:13.219> even<01:39:13.520> given<01:39:14.060> layer 01:39:14.260 --> 01:39:14.270 align:start position:0% computers cases I mean even given layer 01:39:14.270 --> 01:39:16.350 align:start position:0% computers cases I mean even given layer 2<01:39:14.540> solutions<01:39:15.290> that<01:39:15.530> we're<01:39:15.619> developing<01:39:15.800> right 01:39:16.350 --> 01:39:16.360 align:start position:0% 2 solutions that we're developing right 01:39:16.360 --> 01:39:18.180 align:start position:0% 2 solutions that we're developing right so<01:39:16.930> as<01:39:16.990> a<01:39:17.080> general<01:39:17.410> principle<01:39:17.590> of 01:39:18.180 --> 01:39:18.190 align:start position:0% so as a general principle of 01:39:18.190 --> 01:39:20.280 align:start position:0% so as a general principle of decentralized<01:39:18.910> compute<01:39:19.510> we<01:39:19.660> want<01:39:19.840> to<01:39:19.900> move<01:39:20.050> as 01:39:20.280 --> 01:39:20.290 align:start position:0% decentralized compute we want to move as 01:39:20.290 --> 01:39:23.100 align:start position:0% decentralized compute we want to move as much<01:39:20.590> as<01:39:20.860> possible<01:39:21.130> to<01:39:21.580> the<01:39:21.700> edges<01:39:22.180> that<01:39:22.420> means 01:39:23.100 --> 01:39:23.110 align:start position:0% much as possible to the edges that means 01:39:23.110 --> 01:39:24.960 align:start position:0% much as possible to the edges that means of<01:39:23.290> doing<01:39:23.560> more<01:39:23.710> work<01:39:23.920> in<01:39:24.190> the<01:39:24.370> browser<01:39:24.580> that 01:39:24.960 --> 01:39:24.970 align:start position:0% of doing more work in the browser that 01:39:24.970 --> 01:39:27.030 align:start position:0% of doing more work in the browser that they're<01:39:25.780> going<01:39:25.870> to<01:39:25.930> be<01:39:26.050> many<01:39:26.230> use<01:39:26.440> cases<01:39:26.710> where 01:39:27.030 --> 01:39:27.040 align:start position:0% they're going to be many use cases where 01:39:27.040 --> 01:39:28.860 align:start position:0% they're going to be many use cases where we<01:39:27.190> want<01:39:27.370> long<01:39:27.610> running<01:39:28.060> processes<01:39:28.540> doing 01:39:28.860 --> 01:39:28.870 align:start position:0% we want long running processes doing 01:39:28.870 --> 01:39:31.350 align:start position:0% we want long running processes doing compute<01:39:29.380> intense<01:39:29.830> things<01:39:30.370> for<01:39:30.970> example<01:39:31.300> if 01:39:31.350 --> 01:39:31.360 align:start position:0% compute intense things for example if 01:39:31.360 --> 01:39:33.150 align:start position:0% compute intense things for example if you<01:39:31.450> wanted<01:39:31.720> something<01:39:31.990> to<01:39:32.200> index<01:39:32.680> all<01:39:33.010> in 01:39:33.150 --> 01:39:33.160 align:start position:0% you wanted something to index all in 01:39:33.160 --> 01:39:35.250 align:start position:0% you wanted something to index all in your<01:39:33.310> document<01:39:33.790> so<01:39:33.910> you<01:39:33.970> search<01:39:34.420> them<01:39:34.690> you 01:39:35.250 --> 01:39:35.260 align:start position:0% your document so you search them you 01:39:35.260 --> 01:39:37.740 align:start position:0% your document so you search them you need<01:39:35.470> some<01:39:35.740> other<01:39:35.860> kind<01:39:36.010> of<01:39:36.400> system<01:39:36.910> and<01:39:37.120> we're 01:39:37.740 --> 01:39:37.750 align:start position:0% need some other kind of system and we're 01:39:37.750 --> 01:39:40.560 align:start position:0% need some other kind of system and we're taking<01:39:38.080> a<01:39:38.170> cue<01:39:38.410> from<01:39:38.650> Google<01:39:39.430> app<01:39:39.610> from<01:39:39.910> Amazon 01:39:40.560 --> 01:39:40.570 align:start position:0% taking a cue from Google app from Amazon 01:39:40.570 --> 01:39:42.030 align:start position:0% taking a cue from Google app from Amazon lounder<01:39:40.960> and<01:39:41.140> Google<01:39:41.350> Cloud<01:39:41.440> functions 01:39:42.030 --> 01:39:42.040 align:start position:0% lounder and Google Cloud functions 01:39:42.040 --> 01:39:44.160 align:start position:0% lounder and Google Cloud functions they're<01:39:42.640> very<01:39:42.820> scalable<01:39:43.390> technologies<01:39:43.960> to 01:39:44.160 --> 01:39:44.170 align:start position:0% they're very scalable technologies to 01:39:44.170 --> 01:39:46.170 align:start position:0% they're very scalable technologies to probably<01:39:44.590> make<01:39:44.830> those<01:39:45.040> run<01:39:45.400> more 01:39:46.170 --> 01:39:46.180 align:start position:0% probably make those run more 01:39:46.180 --> 01:39:49.890 align:start position:0% probably make those run more peer-to-peer<01:39:46.950> network<01:39:47.970> and<01:39:48.970> in<01:39:49.090> a<01:39:49.180> secure<01:39:49.630> way 01:39:49.890 --> 01:39:49.900 align:start position:0% peer-to-peer network and in a secure way 01:39:49.900 --> 01:39:54.630 align:start position:0% peer-to-peer network and in a secure way and<01:39:50.530> then<01:39:50.800> finally<01:39:51.840> identity<01:39:53.430> there<01:39:54.430> are<01:39:54.490> many 01:39:54.630 --> 01:39:54.640 align:start position:0% and then finally identity there are many 01:39:54.640 --> 01:39:56.490 align:start position:0% and then finally identity there are many cases<01:39:54.820> we<01:39:55.150> want<01:39:55.360> to<01:39:55.420> be<01:39:55.510> an<01:39:55.600> anonymous<01:39:56.020> but 01:39:56.490 --> 01:39:56.500 align:start position:0% cases we want to be an anonymous but 01:39:56.500 --> 01:39:58.080 align:start position:0% cases we want to be an anonymous but we're<01:39:56.710> social<01:39:57.160> beings<01:39:57.220> so<01:39:57.790> how<01:39:57.910> do<01:39:57.970> we 01:39:58.080 --> 01:39:58.090 align:start position:0% we're social beings so how do we 01:39:58.090 --> 01:40:00.450 align:start position:0% we're social beings so how do we represent<01:39:58.240> identity<01:39:58.990> for<01:39:59.170> us<01:39:59.350> and<01:39:59.740> for<01:40:00.400> the 01:40:00.450 --> 01:40:00.460 align:start position:0% represent identity for us and for the 01:40:00.460 --> 01:40:03.270 align:start position:0% represent identity for us and for the systems<01:40:00.850> that<01:40:00.940> we<01:40:01.120> interact<01:40:01.480> with<01:40:02.190> but<01:40:03.190> we 01:40:03.270 --> 01:40:03.280 align:start position:0% systems that we interact with but we 01:40:03.280 --> 01:40:05.340 align:start position:0% systems that we interact with but we have<01:40:03.400> single<01:40:03.580> sign-on<01:40:03.970> today<01:40:04.390> but<01:40:05.080> that's<01:40:05.260> a 01:40:05.340 --> 01:40:05.350 align:start position:0% have single sign-on today but that's a 01:40:05.350 --> 01:40:06.960 align:start position:0% have single sign-on today but that's a terrible<01:40:05.530> thing<01:40:05.740> and<01:40:05.950> that's<01:40:06.310> the<01:40:06.550> central 01:40:06.960 --> 01:40:06.970 align:start position:0% terrible thing and that's the central 01:40:06.970 --> 01:40:09.450 align:start position:0% terrible thing and that's the central authority<01:40:07.840> track<01:40:08.560> everything<01:40:09.040> that<01:40:09.190> we<01:40:09.280> do 01:40:09.450 --> 01:40:09.460 align:start position:0% authority track everything that we do 01:40:09.460 --> 01:40:12.360 align:start position:0% authority track everything that we do we've<01:40:10.330> got<01:40:10.360> new<01:40:10.690> w3c<01:40:11.350> standards<01:40:11.770> who<01:40:11.920> are<01:40:12.010> self 01:40:12.360 --> 01:40:12.370 align:start position:0% we've got new w3c standards who are self 01:40:12.370 --> 01:40:14.250 align:start position:0% we've got new w3c standards who are self sovereign<01:40:12.880> identity<01:40:13.540> where<01:40:13.720> we<01:40:13.840> can<01:40:14.020> create 01:40:14.250 --> 01:40:14.260 align:start position:0% sovereign identity where we can create 01:40:14.260 --> 01:40:16.560 align:start position:0% sovereign identity where we can create up<01:40:14.440> multiple<01:40:15.010> identities<01:40:15.430> that<01:40:15.970> we<01:40:16.150> control 01:40:16.560 --> 01:40:16.570 align:start position:0% up multiple identities that we control 01:40:16.570 --> 01:40:19.190 align:start position:0% up multiple identities that we control the<01:40:16.780> private<01:40:17.380> key<01:40:17.500> pairs<01:40:17.800> and<01:40:18.640> we<01:40:18.760> have 01:40:19.190 --> 01:40:19.200 align:start position:0% the private key pairs and we have 01:40:19.200 --> 01:40:21.120 align:start position:0% the private key pairs and we have verifiable<01:40:20.200> credentials<01:40:20.740> where<01:40:20.890> we<01:40:20.980> can 01:40:21.120 --> 01:40:21.130 align:start position:0% verifiable credentials where we can 01:40:21.130 --> 01:40:23.760 align:start position:0% verifiable credentials where we can exchange<01:40:21.330> signed<01:40:22.330> proofs<01:40:22.840> to<01:40:23.230> give<01:40:23.680> each 01:40:23.760 --> 01:40:23.770 align:start position:0% exchange signed proofs to give each 01:40:23.770 --> 01:40:26.640 align:start position:0% exchange signed proofs to give each other<01:40:23.920> access<01:40:24.790> to<01:40:25.000> different<01:40:25.270> resources<01:40:25.650> so 01:40:26.640 --> 01:40:26.650 align:start position:0% other access to different resources so 01:40:26.650 --> 01:40:29.580 align:start position:0% other access to different resources so um<01:40:27.300> what<01:40:28.300> we<01:40:28.450> are<01:40:28.510> focusing<01:40:29.110> on<01:40:29.260> is<01:40:29.380> building 01:40:29.580 --> 01:40:29.590 align:start position:0% um what we are focusing on is building 01:40:29.590 --> 01:40:32.070 align:start position:0% um what we are focusing on is building this<01:40:29.890> missing<01:40:30.520> peer-to-peer<01:40:30.970> network<01:40:31.720> that 01:40:32.070 --> 01:40:32.080 align:start position:0% this missing peer-to-peer network that 01:40:32.080 --> 01:40:34.080 align:start position:0% this missing peer-to-peer network that joins<01:40:32.950> together<01:40:33.370> the<01:40:33.520> existing<01:40:33.850> cloud 01:40:34.080 --> 01:40:34.090 align:start position:0% joins together the existing cloud 01:40:34.090 --> 01:40:35.880 align:start position:0% joins together the existing cloud technologies<01:40:34.840> with<01:40:35.080> the<01:40:35.110> emergent<01:40:35.650> and<01:40:35.710> what 01:40:35.880 --> 01:40:35.890 align:start position:0% technologies with the emergent and what 01:40:35.890 --> 01:40:37.740 align:start position:0% technologies with the emergent and what train<01:40:36.220> these<01:40:36.730> centralized<01:40:37.180> technologies 01:40:37.740 --> 01:40:37.750 align:start position:0% train these centralized technologies 01:40:37.750 --> 01:40:39.210 align:start position:0% train these centralized technologies because<01:40:38.380> we<01:40:38.530> think<01:40:38.650> there's<01:40:38.830> gonna<01:40:38.920> be<01:40:39.100> on 01:40:39.210 --> 01:40:39.220 align:start position:0% because we think there's gonna be on 01:40:39.220 --> 01:40:41.160 align:start position:0% because we think there's gonna be on that<01:40:39.760> the<01:40:39.910> web<01:40:40.060> will<01:40:40.270> evolve<01:40:40.450> into<01:40:40.690> a<01:40:40.870> hybrid 01:40:41.160 --> 01:40:41.170 align:start position:0% that the web will evolve into a hybrid 01:40:41.170 --> 01:40:44.040 align:start position:0% that the web will evolve into a hybrid of<01:40:41.680> different<01:40:42.280> decentralized<01:40:42.820> systems<01:40:43.210> so 01:40:44.040 --> 01:40:44.050 align:start position:0% of different decentralized systems so 01:40:44.050 --> 01:40:47.880 align:start position:0% of different decentralized systems so can<01:40:45.010> I<01:40:45.070> do<01:40:45.130> a<01:40:45.220> time<01:40:45.520> check<01:40:45.960> yeah<01:40:46.960> six<01:40:47.470> minutes 01:40:47.880 --> 01:40:47.890 align:start position:0% can I do a time check yeah six minutes 01:40:47.890 --> 01:40:48.660 align:start position:0% can I do a time check yeah six minutes okay<01:40:48.130> great 01:40:48.660 --> 01:40:48.670 align:start position:0% okay great 01:40:48.670 --> 01:40:53.430 align:start position:0% okay great so<01:40:49.200> in<01:40:51.270> eight<01:40:52.270> minutes<01:40:52.510> I'm<01:40:52.930> going<01:40:53.050> to<01:40:53.110> rebuild 01:40:53.430 --> 01:40:53.440 align:start position:0% so in eight minutes I'm going to rebuild 01:40:53.440 --> 01:40:56.260 align:start position:0% so in eight minutes I'm going to rebuild googled 01:40:56.260 --> 01:40:56.270 align:start position:0% 01:40:56.270 --> 01:41:00.740 align:start position:0% well<01:40:57.270> we'll<01:40:57.599> see<01:40:57.840> how<01:40:58.020> far<01:40:58.260> we<01:40:58.409> get<01:40:59.239> so<01:41:00.239> I'm 01:41:00.740 --> 01:41:00.750 align:start position:0% well we'll see how far we get so I'm 01:41:00.750 --> 01:41:02.689 align:start position:0% well we'll see how far we get so I'm showing<01:41:01.260> these<01:41:01.530> slides<01:41:01.889> on<01:41:02.190> an<01:41:02.310> app<01:41:02.460> that 01:41:02.689 --> 01:41:02.699 align:start position:0% showing these slides on an app that 01:41:02.699 --> 01:41:04.430 align:start position:0% showing these slides on an app that we've<01:41:02.880> built<01:41:03.119> on<01:41:03.449> our<01:41:03.510> platform<01:41:04.170> called 01:41:04.430 --> 01:41:04.440 align:start position:0% we've built on our platform called 01:41:04.440 --> 01:41:09.350 align:start position:0% we've built on our platform called Launchpad<01:41:05.040> and<01:41:05.250> here<01:41:05.909> it<01:41:06.000> is<01:41:06.060> here<01:41:08.270> Lord 01:41:09.350 --> 01:41:09.360 align:start position:0% Launchpad and here it is here Lord 01:41:09.360 --> 01:41:12.560 align:start position:0% Launchpad and here it is here Lord Launchpad<01:41:09.840> is<01:41:09.900> a<01:41:10.199> is<01:41:10.469> both<01:41:11.239> what<01:41:12.239> would<01:41:12.420> be 01:41:12.560 --> 01:41:12.570 align:start position:0% Launchpad is a is both what would be 01:41:12.570 --> 01:41:15.050 align:start position:0% Launchpad is a is both what would be called<01:41:12.810> today<01:41:13.170> an<01:41:13.349> app<01:41:13.560> store<01:41:13.770> although<01:41:14.579> it's 01:41:15.050 --> 01:41:15.060 align:start position:0% called today an app store although it's 01:41:15.060 --> 01:41:17.510 align:start position:0% called today an app store although it's a<01:41:15.210> actually<01:41:15.659> permissionless<01:41:16.199> blockchain<01:41:16.920> for 01:41:17.510 --> 01:41:17.520 align:start position:0% a actually permissionless blockchain for 01:41:17.520 --> 01:41:19.660 align:start position:0% a actually permissionless blockchain for any<01:41:17.699> developer<01:41:18.030> can<01:41:18.270> freely<01:41:18.690> publish<01:41:19.199> their 01:41:19.660 --> 01:41:19.670 align:start position:0% any developer can freely publish their 01:41:19.670 --> 01:41:23.089 align:start position:0% any developer can freely publish their applications<01:41:20.670> onto<01:41:21.030> this<01:41:21.570> block<01:41:22.560> chain<01:41:22.860> and 01:41:23.089 --> 01:41:23.099 align:start position:0% applications onto this block chain and 01:41:23.099 --> 01:41:26.080 align:start position:0% applications onto this block chain and so<01:41:23.790> Launchpad<01:41:24.540> shows<01:41:24.989> those<01:41:25.260> applications 01:41:26.080 --> 01:41:26.090 align:start position:0% so Launchpad shows those applications 01:41:26.090 --> 01:41:28.850 align:start position:0% so Launchpad shows those applications and<01:41:27.090> then<01:41:27.210> I<01:41:27.270> can<01:41:27.449> sort<01:41:28.020> of<01:41:28.050> create<01:41:28.199> one<01:41:28.619> and 01:41:28.850 --> 01:41:28.860 align:start position:0% and then I can sort of create one and 01:41:28.860 --> 01:41:31.280 align:start position:0% and then I can sort of create one and add<01:41:29.460> it<01:41:29.610> to<01:41:29.639> what<01:41:29.969> we<01:41:30.090> call<01:41:30.270> a<01:41:30.300> party<01:41:30.750> so 01:41:31.280 --> 01:41:31.290 align:start position:0% add it to what we call a party so 01:41:31.290 --> 01:41:34.129 align:start position:0% add it to what we call a party so parties<01:41:31.739> are<01:41:31.889> like<01:41:32.099> lightweight<01:41:33.139> replicated 01:41:34.129 --> 01:41:34.139 align:start position:0% parties are like lightweight replicated 01:41:34.139 --> 01:41:36.770 align:start position:0% parties are like lightweight replicated database<01:41:35.010> that<01:41:35.610> is<01:41:35.730> constructed<01:41:36.389> from<01:41:36.510> that 01:41:36.770 --> 01:41:36.780 align:start position:0% database that is constructed from that 01:41:36.780 --> 01:41:39.620 align:start position:0% database that is constructed from that fields<01:41:37.260> and<01:41:37.500> the<01:41:37.860> user<01:41:38.070> CID<01:41:38.550> tees<01:41:38.880> to<01:41:39.150> create<01:41:39.420> a 01:41:39.620 --> 01:41:39.630 align:start position:0% fields and the user CID tees to create a 01:41:39.630 --> 01:41:42.830 align:start position:0% fields and the user CID tees to create a consistent<01:41:40.020> global<01:41:40.860> view<01:41:41.460> about<01:41:42.360> all<01:41:42.630> of<01:41:42.750> the 01:41:42.830 --> 01:41:42.840 align:start position:0% consistent global view about all of the 01:41:42.840 --> 01:41:45.470 align:start position:0% consistent global view about all of the participants<01:41:43.469> of<01:41:43.590> a<01:41:43.860> particular<01:41:44.360> set<01:41:45.360> of<01:41:45.389> data 01:41:45.470 --> 01:41:45.480 align:start position:0% participants of a particular set of data 01:41:45.480 --> 01:41:47.330 align:start position:0% participants of a particular set of data so<01:41:45.869> we've<01:41:45.989> got<01:41:46.110> very<01:41:46.320> simple<01:41:46.710> spreadsheet 01:41:47.330 --> 01:41:47.340 align:start position:0% so we've got very simple spreadsheet 01:41:47.340 --> 01:41:49.240 align:start position:0% so we've got very simple spreadsheet starting<01:41:48.119> to<01:41:48.179> work<01:41:48.329> with<01:41:48.360> third-party 01:41:49.240 --> 01:41:49.250 align:start position:0% starting to work with third-party 01:41:49.250 --> 01:41:51.200 align:start position:0% starting to work with third-party developers<01:41:50.250> to<01:41:50.400> build<01:41:50.550> out<01:41:50.730> some<01:41:50.760> of<01:41:51.090> these 01:41:51.200 --> 01:41:51.210 align:start position:0% developers to build out some of these 01:41:51.210 --> 01:41:53.569 align:start position:0% developers to build out some of these applications<01:41:52.070> we've<01:41:53.070> got<01:41:53.219> a<01:41:53.250> very<01:41:53.400> simple 01:41:53.569 --> 01:41:53.579 align:start position:0% applications we've got a very simple 01:41:53.579 --> 01:41:58.069 align:start position:0% applications we've got a very simple calendar<01:41:54.239> and<01:41:54.570> that's<01:41:55.560> a<01:41:56.119> document<01:41:57.119> now<01:41:57.810> one 01:41:58.069 --> 01:41:58.079 align:start position:0% calendar and that's a document now one 01:41:58.079 --> 01:41:59.479 align:start position:0% calendar and that's a document now one of<01:41:58.110> the<01:41:58.349> things<01:41:58.619> that<01:41:58.860> fell<01:41:59.070> are<01:41:59.219> still<01:41:59.340> about 01:41:59.479 --> 01:41:59.489 align:start position:0% of the things that fell are still about 01:41:59.489 --> 01:42:01.790 align:start position:0% of the things that fell are still about resilience<01:42:00.000> earlier<01:42:00.420> so<01:42:00.719> we've<01:42:00.869> got<01:42:01.079> some 01:42:01.790 --> 01:42:01.800 align:start position:0% resilience earlier so we've got some 01:42:01.800 --> 01:42:05.540 align:start position:0% resilience earlier so we've got some Wi-Fi<01:42:02.429> resilient<01:42:03.060> issues<01:42:03.739> let's<01:42:04.739> see<01:42:04.949> how<01:42:05.190> far 01:42:05.540 --> 01:42:05.550 align:start position:0% Wi-Fi resilient issues let's see how far 01:42:05.550 --> 01:42:09.589 align:start position:0% Wi-Fi resilient issues let's see how far I<01:42:05.579> can<01:42:05.699> get<01:42:05.880> here<01:42:06.239> so<01:42:06.889> this<01:42:07.889> is<01:42:08.099> me<01:42:08.340> here<01:42:08.849> typing 01:42:09.589 --> 01:42:09.599 align:start position:0% I can get here so this is me here typing 01:42:09.599 --> 01:42:13.939 align:start position:0% I can get here so this is me here typing in<01:42:09.719> this<01:42:09.869> text<01:42:10.230> editor 01:42:13.939 --> 01:42:13.949 align:start position:0% 01:42:13.949 --> 01:42:18.529 align:start position:0% so<01:42:14.639> far<01:42:15.090> and<01:42:15.599> then<01:42:16.110> over<01:42:16.739> here<01:42:17.239> in<01:42:18.239> another 01:42:18.529 --> 01:42:18.539 align:start position:0% so far and then over here in another 01:42:18.539 --> 01:42:21.350 align:start position:0% so far and then over here in another browser<01:42:18.809> incidence<01:42:19.729> which<01:42:20.729> will<01:42:20.940> pretentious 01:42:21.350 --> 01:42:21.360 align:start position:0% browser incidence which will pretentious 01:42:21.360 --> 01:42:23.149 align:start position:0% browser incidence which will pretentious somebody<01:42:21.749> else<01:42:21.929> not<01:42:22.650> me 01:42:23.149 --> 01:42:23.159 align:start position:0% somebody else not me 01:42:23.159 --> 01:42:26.089 align:start position:0% somebody else not me so<01:42:23.459> I<01:42:23.489> call<01:42:23.699> that<01:42:23.729> non<01:42:24.059> trench<01:42:24.360> up<01:42:24.690> here<01:42:25.099> I'm 01:42:26.089 --> 01:42:26.099 align:start position:0% so I call that non trench up here I'm 01:42:26.099 --> 01:42:28.850 align:start position:0% so I call that non trench up here I'm gonna<01:42:26.309> send<01:42:26.639> an<01:42:26.880> invite<01:42:27.590> which<01:42:28.590> you<01:42:28.769> would 01:42:28.850 --> 01:42:28.860 align:start position:0% gonna send an invite which you would 01:42:28.860 --> 01:42:31.100 align:start position:0% gonna send an invite which you would send<01:42:29.099> out<01:42:29.249> of<01:42:29.400> band<01:42:29.670> or<01:42:30.090> once<01:42:30.570> you<01:42:30.719> get<01:42:30.869> to<01:42:30.989> know 01:42:31.100 --> 01:42:31.110 align:start position:0% send out of band or once you get to know 01:42:31.110 --> 01:42:33.680 align:start position:0% send out of band or once you get to know somebody<01:42:31.409> you<01:42:31.590> can<01:42:31.920> now<01:42:32.159> use<01:42:32.940> an<01:42:33.119> address<01:42:33.300> book 01:42:33.680 --> 01:42:33.690 align:start position:0% somebody you can now use an address book 01:42:33.690 --> 01:42:37.100 align:start position:0% somebody you can now use an address book and<01:42:34.579> hopefully<01:42:35.579> these<01:42:35.999> two<01:42:36.300> clients<01:42:36.929> will 01:42:37.100 --> 01:42:37.110 align:start position:0% and hopefully these two clients will 01:42:37.110 --> 01:42:39.109 align:start position:0% and hopefully these two clients will discover<01:42:37.590> each<01:42:37.769> other 01:42:39.109 --> 01:42:39.119 align:start position:0% discover each other 01:42:39.119 --> 01:42:41.449 align:start position:0% discover each other I'll<01:42:39.690> move<01:42:39.959> this<01:42:40.199> one<01:42:40.440> over<01:42:40.469> here<01:42:41.010> and<01:42:41.159> close 01:42:41.449 --> 01:42:41.459 align:start position:0% I'll move this one over here and close 01:42:41.459 --> 01:42:48.189 align:start position:0% I'll move this one over here and close that<01:42:41.789> off<01:42:46.249> yeah 01:42:48.189 --> 01:42:48.199 align:start position:0% that off yeah 01:42:48.199 --> 01:42:50.930 align:start position:0% that off yeah and<01:42:49.199> so<01:42:49.320> these<01:42:49.440> are<01:42:49.499> two<01:42:49.619> peers<01:42:50.099> on<01:42:50.459> the<01:42:50.519> same 01:42:50.930 --> 01:42:50.940 align:start position:0% and so these are two peers on the same 01:42:50.940 --> 01:42:55.370 align:start position:0% and so these are two peers on the same network<01:42:51.479> did<01:42:52.469> it<01:42:52.559> work<01:42:52.769> yeah<01:42:52.979> okay<01:42:54.199> and<01:42:55.199> we're 01:42:55.370 --> 01:42:55.380 align:start position:0% network did it work yeah okay and we're 01:42:55.380 --> 01:43:03.349 align:start position:0% network did it work yeah okay and we're going<01:42:55.530> to<01:42:55.590> the<01:42:55.709> same<01:42:55.889> document 01:43:03.349 --> 01:43:03.359 align:start position:0% 01:43:03.359 --> 01:43:06.589 align:start position:0% well<01:43:03.899> okay<01:43:04.309> you<01:43:05.309> can<01:43:05.459> see<01:43:05.669> the<01:43:05.820> if<01:43:06.300> I<01:43:06.419> go<01:43:06.570> over 01:43:06.589 --> 01:43:06.599 align:start position:0% well okay you can see the if I go over 01:43:06.599 --> 01:43:09.500 align:start position:0% well okay you can see the if I go over here<01:43:06.809> quickly<01:43:07.699> you<01:43:08.699> should<01:43:08.969> be<01:43:09.089> able<01:43:09.149> to<01:43:09.300> see 01:43:09.500 --> 01:43:09.510 align:start position:0% here quickly you should be able to see 01:43:09.510 --> 01:43:11.569 align:start position:0% here quickly you should be able to see me<01:43:10.109> typing<01:43:10.289> over<01:43:10.589> that<01:43:10.800> so<01:43:10.979> what's<01:43:11.129> happening 01:43:11.569 --> 01:43:11.579 align:start position:0% me typing over that so what's happening 01:43:11.579 --> 01:43:14.209 align:start position:0% me typing over that so what's happening here<01:43:11.820> two<01:43:12.089> clients<01:43:12.739> swarming<01:43:13.739> with<01:43:13.769> the<01:43:14.010> same 01:43:14.209 --> 01:43:14.219 align:start position:0% here two clients swarming with the same 01:43:14.219 --> 01:43:17.409 align:start position:0% here two clients swarming with the same discovery<01:43:14.609> key<01:43:14.999> on<01:43:15.659> the<01:43:15.809> same<01:43:16.019> local<01:43:16.649> network 01:43:17.409 --> 01:43:17.419 align:start position:0% discovery key on the same local network 01:43:17.419 --> 01:43:19.790 align:start position:0% discovery key on the same local network this<01:43:18.419> will<01:43:18.599> happen<01:43:18.749> across<01:43:19.050> the<01:43:19.169> internet<01:43:19.679> if 01:43:19.790 --> 01:43:19.800 align:start position:0% this will happen across the internet if 01:43:19.800 --> 01:43:22.849 align:start position:0% this will happen across the internet if we<01:43:20.249> had<01:43:20.399> our<01:43:20.939> Wi-Fi<01:43:21.269> working<01:43:21.559> and<01:43:22.559> then<01:43:22.739> the 01:43:22.849 --> 01:43:22.859 align:start position:0% we had our Wi-Fi working and then the 01:43:22.859 --> 01:43:24.649 align:start position:0% we had our Wi-Fi working and then the the<01:43:23.129> mutations<01:43:23.760> are<01:43:23.849> getting<01:43:24.089> exchanged<01:43:24.570> in 01:43:24.649 --> 01:43:24.659 align:start position:0% the mutations are getting exchanged in 01:43:24.659 --> 01:43:30.229 align:start position:0% the mutations are getting exchanged in real<01:43:24.899> time<01:43:25.079> so<01:43:25.760> we'll<01:43:26.760> go<01:43:26.909> from<01:43:27.300> this<01:43:27.689> into<01:43:29.239> I'm 01:43:30.229 --> 01:43:30.239 align:start position:0% real time so we'll go from this into I'm 01:43:30.239 --> 01:43:33.679 align:start position:0% real time so we'll go from this into I'm gonna<01:43:30.419> try<01:43:30.719> to<01:43:30.780> build<01:43:31.139> an<01:43:31.499> app<01:43:31.709> now<01:43:32.099> and<01:43:32.689> remain 01:43:33.679 --> 01:43:33.689 align:start position:0% gonna try to build an app now and remain 01:43:33.689 --> 01:43:37.639 align:start position:0% gonna try to build an app now and remain five<01:43:34.079> minutes<01:43:34.699> see<01:43:35.699> a<01:43:35.729> father<01:43:35.999> yet<01:43:36.329> so<01:43:37.019> it's 01:43:37.639 --> 01:43:37.649 align:start position:0% five minutes see a father yet so it's 01:43:37.649 --> 01:43:41.659 align:start position:0% five minutes see a father yet so it's check<01:43:38.449> we've<01:43:39.449> got<01:43:39.599> an<01:43:39.689> SDK<01:43:40.229> called<01:43:40.709> the<01:43:40.800> ys<01:43:41.189> tli 01:43:41.659 --> 01:43:41.669 align:start position:0% check we've got an SDK called the ys tli 01:43:41.669 --> 01:43:43.489 align:start position:0% check we've got an SDK called the ys tli that<01:43:42.269> the<01:43:42.359> first<01:43:42.629> thing<01:43:42.719> I'm<01:43:42.869> going<01:43:42.899> to<01:43:43.079> do<01:43:43.260> is 01:43:43.489 --> 01:43:43.499 align:start position:0% that the first thing I'm going to do is 01:43:43.499 --> 01:43:46.849 align:start position:0% that the first thing I'm going to do is build<01:43:43.889> a<01:43:44.280> new<01:43:44.789> pad<01:43:45.599> we<01:43:45.869> call<01:43:46.109> these<01:43:46.260> US 01:43:46.849 --> 01:43:46.859 align:start position:0% build a new pad we call these US 01:43:46.859 --> 01:43:50.839 align:start position:0% build a new pad we call these US components<01:43:47.550> pads<01:43:47.989> so<01:43:48.989> I'll<01:43:49.589> use<01:43:50.070> an<01:43:50.369> incessant 01:43:50.839 --> 01:43:50.849 align:start position:0% components pads so I'll use an incessant 01:43:50.849 --> 01:43:53.810 align:start position:0% components pads so I'll use an incessant and<01:43:51.059> a<01:43:51.119> fork<01:43:51.389> an<01:43:51.599> existing<01:43:52.379> github<01:43:53.249> repo<01:43:53.669> that 01:43:53.810 --> 01:43:53.820 align:start position:0% and a fork an existing github repo that 01:43:53.820 --> 01:43:56.060 align:start position:0% and a fork an existing github repo that has<01:43:53.999> my<01:43:54.179> starting<01:43:54.570> point<01:43:54.809> me<01:43:55.050> so<01:43:55.409> why<01:43:55.679> I've<01:43:55.829> had 01:43:56.060 --> 01:43:56.070 align:start position:0% has my starting point me so why I've had 01:43:56.070 --> 01:43:58.459 align:start position:0% has my starting point me so why I've had to<01:43:56.129> create<01:43:56.459> and<01:43:57.239> then<01:43:57.359> I<01:43:57.479> call<01:43:57.780> the<01:43:58.229> name<01:43:58.349> of 01:43:58.459 --> 01:43:58.469 align:start position:0% to create and then I call the name of 01:43:58.469 --> 01:44:02.000 align:start position:0% to create and then I call the name of the<01:43:58.559> template<01:43:59.039> and<01:43:59.339> now<01:44:00.269> if<01:44:01.169> I<01:44:01.289> go<01:44:01.439> into<01:44:01.589> demo 01:44:02.000 --> 01:44:02.010 align:start position:0% the template and now if I go into demo 01:44:02.010 --> 01:44:04.849 align:start position:0% the template and now if I go into demo pad<01:44:02.570> we're<01:44:03.570> gonna<01:44:03.749> code<01:44:04.139> here 01:44:04.849 --> 01:44:04.859 align:start position:0% pad we're gonna code here 01:44:04.859 --> 01:44:18.180 align:start position:0% pad we're gonna code here I'll<01:44:05.849> see<01:44:06.329> hopefully<01:44:07.159> that 01:44:18.180 --> 01:44:18.190 align:start position:0% 01:44:18.190 --> 01:44:23.830 align:start position:0% it's<01:44:19.190> just<01:44:19.520> waking<01:44:20.090> up<01:44:20.180> okay<01:44:20.900> here<01:44:21.380> we<01:44:21.440> go 01:44:23.830 --> 01:44:23.840 align:start position:0% 01:44:23.840 --> 01:45:05.580 align:start position:0% [Music] 01:45:05.580 --> 01:45:05.590 align:start position:0% 01:45:05.590 --> 01:45:07.720 align:start position:0% all<01:45:06.590> right<01:45:06.740> just<01:45:07.400> try 01:45:07.720 --> 01:45:07.730 align:start position:0% all right just try 01:45:07.730 --> 01:45:11.830 align:start position:0% all right just try thank<01:45:08.180> you<01:45:08.360> this<01:45:10.030> they<01:45:11.030> say<01:45:11.240> backs<01:45:11.510> are<01:45:11.720> more 01:45:11.830 --> 01:45:11.840 align:start position:0% thank you this they say backs are more 01:45:11.840 --> 01:45:20.770 align:start position:0% thank you this they say backs are more reliable<01:45:12.170> I<01:45:12.470> don't<01:45:12.650> know<01:45:19.150> we<01:45:20.150> need<01:45:20.330> we<01:45:20.510> need<01:45:20.540> a 01:45:20.770 --> 01:45:20.780 align:start position:0% reliable I don't know we need we need a 01:45:20.780 --> 01:45:23.230 align:start position:0% reliable I don't know we need we need a keyboard 01:45:23.230 --> 01:45:23.240 align:start position:0% 01:45:23.240 --> 01:45:27.250 align:start position:0% I<01:45:23.500> think<01:45:24.500> you<01:45:24.590> have<01:45:24.770> that<01:45:24.800> much<01:45:25.010> stuff<01:45:26.260> let's 01:45:27.250 --> 01:45:27.260 align:start position:0% I think you have that much stuff let's 01:45:27.260 --> 01:45:29.170 align:start position:0% I think you have that much stuff let's know<01:45:27.860> that<01:45:28.010> we<01:45:28.100> commute<01:45:28.460> he<01:45:28.700> doesn't<01:45:28.970> have<01:45:29.090> to 01:45:29.170 --> 01:45:29.180 align:start position:0% know that we commute he doesn't have to 01:45:29.180 --> 01:45:31.930 align:start position:0% know that we commute he doesn't have to stop<01:45:29.780> there<01:45:29.810> so<01:45:30.230> I<01:45:30.260> don't<01:45:30.530> know<01:45:30.760> okay<01:45:31.790> I'm 01:45:31.930 --> 01:45:31.940 align:start position:0% stop there so I don't know okay I'm 01:45:31.940 --> 01:45:34.360 align:start position:0% stop there so I don't know okay I'm worried<01:45:32.690> tight<01:45:32.990> without<01:45:33.260> let's<01:45:33.920> do<01:45:34.070> it<01:45:34.160> life 01:45:34.360 --> 01:45:34.370 align:start position:0% worried tight without let's do it life 01:45:34.370 --> 01:45:46.590 align:start position:0% worried tight without let's do it life I'm<01:45:34.730> gonna<01:45:34.940> do<01:45:37.300> I'm<01:45:38.300> referring<01:45:38.690> to<01:45:38.750> that<01:45:38.870> book 01:45:46.590 --> 01:45:46.600 align:start position:0% 01:45:46.600 --> 01:45:55.750 align:start position:0% yes<01:45:47.600> Jay 01:45:55.750 --> 01:45:55.760 align:start position:0% 01:45:55.760 --> 01:45:58.160 align:start position:0% so<01:45:56.760> this<01:45:56.910> is<01:45:57.060> why<01:45:57.180> we're<01:45:57.300> gonna<01:45:57.390> stop<01:45:57.720> building 01:45:58.160 --> 01:45:58.170 align:start position:0% so this is why we're gonna stop building 01:45:58.170 --> 01:46:00.980 align:start position:0% so this is why we're gonna stop building apps<01:45:59.070> and<01:45:59.310> electron<01:45:59.730> and<01:46:00.030> start<01:46:00.240> using<01:46:00.360> the 01:46:00.980 --> 01:46:00.990 align:start position:0% apps and electron and start using the 01:46:00.990 --> 01:46:09.160 align:start position:0% apps and electron and start using the press<01:46:02.150> okay<01:46:03.150> okay<01:46:03.750> can<01:46:04.170> I<01:46:04.320> have<01:46:04.350> another<01:46:04.940> yes<01:46:07.310> I 01:46:09.160 --> 01:46:09.170 align:start position:0% press okay okay can I have another yes I 01:46:09.170 --> 01:46:12.040 align:start position:0% press okay okay can I have another yes I was<01:46:10.170> gonna<01:46:10.380> say<01:46:10.680> when<01:46:10.950> I<01:46:10.980> was<01:46:11.280> a<01:46:11.340> kid 01:46:12.040 --> 01:46:12.050 align:start position:0% was gonna say when I was a kid 01:46:12.050 --> 01:46:15.710 align:start position:0% was gonna say when I was a kid Microsoft<01:46:13.050> was<01:46:13.400> treated<01:46:14.400> as<01:46:14.520> the<01:46:14.760> enemy<01:46:15.330> in 01:46:15.710 --> 01:46:15.720 align:start position:0% Microsoft was treated as the enemy in 01:46:15.720 --> 01:46:19.400 align:start position:0% Microsoft was treated as the enemy in the<01:46:15.870> real<01:46:16.050> sort<01:46:16.500> of<01:46:16.530> worst<01:46:17.520> contender<01:46:18.180> oh<01:46:18.570> that 01:46:19.400 --> 01:46:19.410 align:start position:0% the real sort of worst contender oh that 01:46:19.410 --> 01:46:20.930 align:start position:0% the real sort of worst contender oh that kind<01:46:19.590> of<01:46:19.680> repeat<01:46:19.980> rehabilitate<01:46:20.670> themselves 01:46:20.930 --> 01:46:20.940 align:start position:0% kind of repeat rehabilitate themselves 01:46:20.940 --> 01:46:23.870 align:start position:0% kind of repeat rehabilitate themselves but<01:46:21.630> going<01:46:21.870> back<01:46:22.080> on<01:46:22.260> that<01:46:22.290> that<01:46:22.590> guess<01:46:23.550> code 01:46:23.870 --> 01:46:23.880 align:start position:0% but going back on that that guess code 01:46:23.880 --> 01:46:29.120 align:start position:0% but going back on that that guess code this<01:46:24.210> is<01:46:24.510> pretty<01:46:24.690> good<01:46:24.930> okay<01:46:25.920> so<01:46:27.200> look<01:46:28.200> bad<01:46:28.410> and 01:46:29.120 --> 01:46:29.130 align:start position:0% this is pretty good okay so look bad and 01:46:29.130 --> 01:46:30.920 align:start position:0% this is pretty good okay so look bad and what<01:46:29.370> we<01:46:29.490> have<01:46:29.670> here<01:46:29.910> is<01:46:30.030> this<01:46:30.150> template<01:46:30.630> pad 01:46:30.920 --> 01:46:30.930 align:start position:0% what we have here is this template pad 01:46:30.930 --> 01:46:34.190 align:start position:0% what we have here is this template pad and<01:46:31.110> what<01:46:31.200> I'm<01:46:31.290> going<01:46:31.410> to<01:46:31.500> do<01:46:31.740> is<01:46:32.670> go<01:46:33.510> into<01:46:33.990> the 01:46:34.190 --> 01:46:34.200 align:start position:0% and what I'm going to do is go into the 01:46:34.200 --> 01:46:36.410 align:start position:0% and what I'm going to do is go into the terminal<01:46:34.470> here<01:46:35.040> and<01:46:35.250> say<01:46:35.850> first<01:46:36.180> thing<01:46:36.270> root 01:46:36.410 --> 01:46:36.420 align:start position:0% terminal here and say first thing root 01:46:36.420 --> 01:46:37.970 align:start position:0% terminal here and say first thing root is<01:46:36.570> register<01:46:37.050> the<01:46:37.140> time<01:46:37.350> of<01:46:37.530> the<01:46:37.590> block<01:46:37.740> trace 01:46:37.970 --> 01:46:37.980 align:start position:0% is register the time of the block trace 01:46:37.980 --> 01:46:43.120 align:start position:0% is register the time of the block trace and<01:46:38.220> what<01:46:38.400> part<01:46:39.000> of<01:46:39.120> the<01:46:39.240> register<01:46:39.860> register 01:46:43.120 --> 01:46:43.130 align:start position:0% 01:46:43.130 --> 01:46:51.590 align:start position:0% okay<01:46:44.130> and<01:46:44.370> then<01:46:44.490> yarn<01:46:44.700> pills<01:46:50.210> with<01:46:51.210> the<01:46:51.330> Kratz 01:46:51.590 --> 01:46:51.600 align:start position:0% okay and then yarn pills with the Kratz 01:46:51.600 --> 01:46:55.280 align:start position:0% okay and then yarn pills with the Kratz permission<01:46:52.610> okay<01:46:53.610> so<01:46:54.270> what<01:46:55.050> should<01:46:55.080> happen 01:46:55.280 --> 01:46:55.290 align:start position:0% permission okay so what should happen 01:46:55.290 --> 01:46:58.070 align:start position:0% permission okay so what should happen now<01:46:55.740> is<01:46:56.100> that<01:46:56.160> we're<01:46:57.060> running<01:46:57.180> the<01:46:57.780> launchpad 01:46:58.070 --> 01:46:58.080 align:start position:0% now is that we're running the launchpad 01:46:58.080 --> 01:47:01.250 align:start position:0% now is that we're running the launchpad in<01:46:58.470> dev<01:46:58.740> mode<01:46:58.950> and<01:46:59.310> so<01:46:59.520> this<01:46:59.760> this<01:47:00.060> template<01:47:00.990> is 01:47:01.250 --> 01:47:01.260 align:start position:0% in dev mode and so this this template is 01:47:01.260 --> 01:47:03.380 align:start position:0% in dev mode and so this this template is a<01:47:01.290> simple<01:47:01.770> tasks<01:47:02.160> app<01:47:02.370> if<01:47:03.000> I<01:47:03.090> create<01:47:03.330> a<01:47:03.360> new 01:47:03.380 --> 01:47:03.390 align:start position:0% a simple tasks app if I create a new 01:47:03.390 --> 01:47:05.420 align:start position:0% a simple tasks app if I create a new instance<01:47:03.810> of<01:47:04.020> that<01:47:04.080> inside<01:47:04.650> this<01:47:04.770> party<01:47:05.280> which 01:47:05.420 --> 01:47:05.430 align:start position:0% instance of that inside this party which 01:47:05.430 --> 01:47:07.790 align:start position:0% instance of that inside this party which is<01:47:05.460> this<01:47:05.730> spiritual<01:47:06.090> database<01:47:06.480> I<01:47:06.810> can<01:47:07.320> now<01:47:07.470> I 01:47:07.790 --> 01:47:07.800 align:start position:0% is this spiritual database I can now I 01:47:07.800 --> 01:47:09.260 align:start position:0% is this spiritual database I can now I usually<01:47:08.430> type<01:47:08.610> things<01:47:08.910> a<01:47:09.000> little<01:47:09.060> bit<01:47:09.210> more 01:47:09.260 --> 01:47:09.270 align:start position:0% usually type things a little bit more 01:47:09.270 --> 01:47:11.480 align:start position:0% usually type things a little bit more thoughtfulness<01:47:09.780> but<01:47:10.020> given<01:47:10.500> the<01:47:10.560> time<01:47:10.740> I<01:47:11.010> can 01:47:11.480 --> 01:47:11.490 align:start position:0% thoughtfulness but given the time I can 01:47:11.490 --> 01:47:13.610 align:start position:0% thoughtfulness but given the time I can now<01:47:11.640> see<01:47:12.570> that<01:47:12.720> we've<01:47:12.840> got<01:47:12.960> this<01:47:13.050> very<01:47:13.170> simple 01:47:13.610 --> 01:47:13.620 align:start position:0% now see that we've got this very simple 01:47:13.620 --> 01:47:15.860 align:start position:0% now see that we've got this very simple task<01:47:13.860> list<01:47:14.160> if<01:47:14.790> I<01:47:15.030> go<01:47:15.210> over<01:47:15.450> to<01:47:15.480> the<01:47:15.720> other 01:47:15.860 --> 01:47:15.870 align:start position:0% task list if I go over to the other 01:47:15.870 --> 01:47:19.180 align:start position:0% task list if I go over to the other browser<01:47:16.230> instance<01:47:16.860> over<01:47:17.070> here 01:47:19.180 --> 01:47:19.190 align:start position:0% browser instance over here 01:47:19.190 --> 01:47:23.070 align:start position:0% browser instance over here suppose<01:47:19.969> that<01:47:20.000> should<01:47:20.480> open<01:47:20.630> up<01:47:20.840> again<01:47:21.070> here 01:47:23.070 --> 01:47:23.080 align:start position:0% suppose that should open up again here 01:47:23.080 --> 01:47:26.500 align:start position:0% suppose that should open up again here there's<01:47:24.080> my<01:47:24.739> task<01:47:25.100> lesson<01:47:25.969> I<01:47:26.030> check<01:47:26.330> some 01:47:26.500 --> 01:47:26.510 align:start position:0% there's my task lesson I check some 01:47:26.510 --> 01:47:28.420 align:start position:0% there's my task lesson I check some things<01:47:26.540> up<01:47:26.900> so<01:47:27.350> automatically<01:47:28.010> out<01:47:28.250> of<01:47:28.340> the 01:47:28.420 --> 01:47:28.430 align:start position:0% things up so automatically out of the 01:47:28.430 --> 01:47:30.220 align:start position:0% things up so automatically out of the box<01:47:28.670> it's<01:47:28.910> collaborative<01:47:29.330> so<01:47:29.750> let's<01:47:29.900> let's 01:47:30.220 --> 01:47:30.230 align:start position:0% box it's collaborative so let's let's 01:47:30.230 --> 01:47:31.420 align:start position:0% box it's collaborative so let's let's change<01:47:30.560> that<01:47:30.800> alert 01:47:31.420 --> 01:47:31.430 align:start position:0% change that alert 01:47:31.430 --> 01:47:34.000 align:start position:0% change that alert I'm<01:47:31.670> going<01:47:32.330> to<01:47:32.510> now<01:47:32.719> close<01:47:33.230> that<01:47:33.350> happened 01:47:34.000 --> 01:47:34.010 align:start position:0% I'm going to now close that happened 01:47:34.010 --> 01:47:35.439 align:start position:0% I'm going to now close that happened since<01:47:34.850> we're<01:47:35.030> in<01:47:35.090> Japan 01:47:35.439 --> 01:47:35.449 align:start position:0% since we're in Japan 01:47:35.449 --> 01:47:39.640 align:start position:0% since we're in Japan I'm<01:47:35.660> gonna<01:47:35.780> build<01:47:35.989> shogi<01:47:36.500> yeah<01:47:36.880> so<01:47:38.500> show<01:47:39.500> his 01:47:39.640 --> 01:47:39.650 align:start position:0% I'm gonna build shogi yeah so show his 01:47:39.650 --> 01:47:42.760 align:start position:0% I'm gonna build shogi yeah so show his Japanese<01:47:40.130> chess<01:47:40.489> I<01:47:40.790> did<01:47:41.660> this<01:47:41.780> really<01:47:42.380> quick 01:47:42.760 --> 01:47:42.770 align:start position:0% Japanese chess I did this really quick 01:47:42.770 --> 01:47:46.330 align:start position:0% Japanese chess I did this really quick so<01:47:43.510> edit<01:47:44.510> this<01:47:44.660> task<01:47:45.230> list<01:47:45.560> and<01:47:45.770> I've<01:47:46.160> got<01:47:46.310> a 01:47:46.330 --> 01:47:46.340 align:start position:0% so edit this task list and I've got a 01:47:46.340 --> 01:47:47.680 align:start position:0% so edit this task list and I've got a couple<01:47:46.580> of<01:47:46.670> these<01:47:46.820> things<01:47:47.120> couple<01:47:47.510> of<01:47:47.570> the 01:47:47.680 --> 01:47:47.690 align:start position:0% couple of these things couple of the 01:47:47.690 --> 01:47:50.290 align:start position:0% couple of these things couple of the import<01:47:48.020> statements<01:47:48.560> already<01:47:48.830> ready<01:47:49.300> we're 01:47:50.290 --> 01:47:50.300 align:start position:0% import statements already ready we're 01:47:50.300 --> 01:47:51.880 align:start position:0% import statements already ready we're gonna<01:47:50.360> change<01:47:50.690> the<01:47:50.930> entire<01:47:51.199> render<01:47:51.680> function 01:47:51.880 --> 01:47:51.890 align:start position:0% gonna change the entire render function 01:47:51.890 --> 01:47:55.479 align:start position:0% gonna change the entire render function if<01:47:52.219> those<01:47:52.430> things<01:47:52.760> only<01:47:53.000> act<01:47:54.310> we're<01:47:55.310> going<01:47:55.430> to 01:47:55.479 --> 01:47:55.489 align:start position:0% if those things only act we're going to 01:47:55.489 --> 01:47:57.700 align:start position:0% if those things only act we're going to render<01:47:55.670> this<01:47:55.880> Shoei<01:47:56.270> board<01:47:56.630> using<01:47:57.620> your 01:47:57.700 --> 01:47:57.710 align:start position:0% render this Shoei board using your 01:47:57.710 --> 01:48:07.060 align:start position:0% render this Shoei board using your current<01:47:57.890> game<01:47:58.280> state<01:48:04.270> and<01:48:05.410> let's<01:48:06.410> just<01:48:06.620> try<01:48:06.890> it 01:48:07.060 --> 01:48:07.070 align:start position:0% current game state and let's just try it 01:48:07.070 --> 01:48:09.070 align:start position:0% current game state and let's just try it and<01:48:07.219> then<01:48:07.430> inside<01:48:08.000> deaths<01:48:08.330> I'm<01:48:08.600> gonna<01:48:08.780> change 01:48:09.070 --> 01:48:09.080 align:start position:0% and then inside deaths I'm gonna change 01:48:09.080 --> 01:48:13.689 align:start position:0% and then inside deaths I'm gonna change the<01:48:09.469> icon<01:48:10.010> somebody<01:48:10.730> give<01:48:10.850> me<01:48:10.880> a<01:48:11.000> car<01:48:12.699> black 01:48:13.689 --> 01:48:13.699 align:start position:0% the icon somebody give me a car black 01:48:13.699 --> 01:48:18.860 align:start position:0% the icon somebody give me a car black could<01:48:13.850> be<01:48:13.910> a<01:48:14.030> plan<01:48:14.300> amendment<01:48:16.150> shogi 01:48:18.860 --> 01:48:18.870 align:start position:0% could be a plan amendment shogi 01:48:18.870 --> 01:48:24.390 align:start position:0% could be a plan amendment shogi say<01:48:19.870> it<01:48:19.990> and<01:48:20.710> let's<01:48:21.700> see<01:48:21.910> so<01:48:23.070> it<01:48:24.070> should<01:48:24.310> get 01:48:24.390 --> 01:48:24.400 align:start position:0% say it and let's see so it should get 01:48:24.400 --> 01:48:25.590 align:start position:0% say it and let's see so it should get the<01:48:24.580> changes<01:48:24.910> should<01:48:25.060> get<01:48:25.240> picked<01:48:25.480> up 01:48:25.590 --> 01:48:25.600 align:start position:0% the changes should get picked up 01:48:25.600 --> 01:48:28.200 align:start position:0% the changes should get picked up automatically<01:48:26.230> and<01:48:26.910> we're<01:48:27.910> going<01:48:28.060> to<01:48:28.090> show 01:48:28.200 --> 01:48:28.210 align:start position:0% automatically and we're going to show 01:48:28.210 --> 01:48:30.420 align:start position:0% automatically and we're going to show you<01:48:28.270> what<01:48:28.480> in<01:48:28.630> green<01:48:28.900> I<01:48:29.200> know<01:48:29.980> if<01:48:30.040> we<01:48:30.160> create<01:48:30.400> a 01:48:30.420 --> 01:48:30.430 align:start position:0% you what in green I know if we create a 01:48:30.430 --> 01:48:32.550 align:start position:0% you what in green I know if we create a new<01:48:30.550> instance<01:48:30.700> of<01:48:31.060> that<01:48:31.090> we've<01:48:31.720> got<01:48:31.870> somewhat 01:48:32.550 --> 01:48:32.560 align:start position:0% new instance of that we've got somewhat 01:48:32.560 --> 01:48:35.430 align:start position:0% new instance of that we've got somewhat of<01:48:32.860> a<01:48:33.190> show<01:48:33.640> you<01:48:33.670> what<01:48:34.000> this<01:48:34.330> is<01:48:34.390> here<01:48:34.780> right<01:48:35.410> I 01:48:35.430 --> 01:48:35.440 align:start position:0% of a show you what this is here right I 01:48:35.440 --> 01:48:37.620 align:start position:0% of a show you what this is here right I can<01:48:35.680> I<01:48:35.890> can<01:48:36.160> move<01:48:36.370> pieces<01:48:36.850> here<01:48:37.330> but<01:48:37.540> obviously 01:48:37.620 --> 01:48:37.630 align:start position:0% can I can move pieces here but obviously 01:48:37.630 --> 01:48:39.510 align:start position:0% can I can move pieces here but obviously probably<01:48:38.110> to<01:48:38.170> refresh<01:48:38.590> the<01:48:38.770> screen<01:48:39.010> we're 01:48:39.510 --> 01:48:39.520 align:start position:0% probably to refresh the screen we're 01:48:39.520 --> 01:48:41.280 align:start position:0% probably to refresh the screen we're gonna<01:48:39.640> lose<01:48:39.820> all<01:48:39.940> of<01:48:39.970> the<01:48:40.120> stain<01:48:40.360> so<01:48:41.050> the<01:48:41.140> next 01:48:41.280 --> 01:48:41.290 align:start position:0% gonna lose all of the stain so the next 01:48:41.290 --> 01:48:43.370 align:start position:0% gonna lose all of the stain so the next thing<01:48:41.440> I'm<01:48:41.560> going<01:48:41.620> to<01:48:41.770> do<01:48:42.010> is<01:48:42.340> go<01:48:42.670> in<01:48:42.820> here<01:48:43.150> and 01:48:43.370 --> 01:48:43.380 align:start position:0% thing I'm going to do is go in here and 01:48:43.380 --> 01:48:47.040 align:start position:0% thing I'm going to do is go in here and add<01:48:44.380> a<01:48:44.440> add<01:48:45.070> a<01:48:45.130> little<01:48:45.370> parameter<01:48:45.880> here<01:48:46.450> for 01:48:47.040 --> 01:48:47.050 align:start position:0% add a add a little parameter here for 01:48:47.050 --> 01:48:50.070 align:start position:0% add a add a little parameter here for the<01:48:47.290> drop<01:48:47.860> and<01:48:48.430> then<01:48:48.850> add<01:48:49.030> a<01:48:49.060> front<01:48:49.570> end<01:48:49.840> to 01:48:50.070 --> 01:48:50.080 align:start position:0% the drop and then add a front end to 01:48:50.080 --> 01:48:54.210 align:start position:0% the drop and then add a front end to that<01:48:50.200> effect<01:48:51.780> handle<01:48:52.780> drop<01:48:52.990> so<01:48:53.830> I'm<01:48:53.980> going<01:48:54.130> to 01:48:54.210 --> 01:48:54.220 align:start position:0% that effect handle drop so I'm going to 01:48:54.220 --> 01:48:56.100 align:start position:0% that effect handle drop so I'm going to get<01:48:54.310> the<01:48:54.430> events<01:48:54.910> that<01:48:55.360> were<01:48:55.540> published<01:48:55.990> by 01:48:56.100 --> 01:48:56.110 align:start position:0% get the events that were published by 01:48:56.110 --> 01:48:58.560 align:start position:0% get the events that were published by that<01:48:56.320> we<01:48:56.530> are<01:48:56.650> control<01:48:57.210> validate<01:48:58.210> that's<01:48:58.450> a 01:48:58.560 --> 01:48:58.570 align:start position:0% that we are control validate that's a 01:48:58.570 --> 01:49:00.990 align:start position:0% that we are control validate that's a reasonable<01:48:59.020> move<01:48:59.230> and<01:48:59.620> then<01:48:59.980> I'm<01:49:00.700> going<01:49:00.910> to 01:49:00.990 --> 01:49:01.000 align:start position:0% reasonable move and then I'm going to 01:49:01.000 --> 01:49:03.690 align:start position:0% reasonable move and then I'm going to append<01:49:01.450> that<01:49:01.630> to<01:49:02.050> a<01:49:02.440> law<01:49:02.650> we're<01:49:03.340> using<01:49:03.490> these 01:49:03.690 --> 01:49:03.700 align:start position:0% append that to a law we're using these 01:49:03.700 --> 01:49:05.790 align:start position:0% append that to a law we're using these higher-order<01:49:04.260> components<01:49:05.260> which<01:49:05.440> are<01:49:05.560> right 01:49:05.790 --> 01:49:05.800 align:start position:0% higher-order components which are right 01:49:05.800 --> 01:49:06.660 align:start position:0% higher-order components which are right it's<01:49:05.980> part<01:49:06.160> of<01:49:06.190> a<01:49:06.250> react 01:49:06.660 --> 01:49:06.670 align:start position:0% it's part of a react 01:49:06.670 --> 01:49:08.970 align:start position:0% it's part of a react idiom<01:49:07.030> it's<01:49:07.540> going<01:49:07.690> to<01:49:07.750> inject<01:49:08.170> the<01:49:08.500> database 01:49:08.970 --> 01:49:08.980 align:start position:0% idiom it's going to inject the database 01:49:08.980 --> 01:49:11.700 align:start position:0% idiom it's going to inject the database from<01:49:09.220> this<01:49:09.340> party<01:49:09.760> into<01:49:10.390> the<01:49:10.480> control<01:49:10.870> give<01:49:11.590> me 01:49:11.700 --> 01:49:11.710 align:start position:0% from this party into the control give me 01:49:11.710 --> 01:49:13.740 align:start position:0% from this party into the control give me this<01:49:11.860> view<01:49:12.340> object<01:49:12.790> that<01:49:13.060> I<01:49:13.180> can<01:49:13.330> then<01:49:13.450> append 01:49:13.740 --> 01:49:13.750 align:start position:0% this view object that I can then append 01:49:13.750 --> 01:49:18.390 align:start position:0% this view object that I can then append changes<01:49:14.260> to<01:49:14.470> and<01:49:15.280> then<01:49:15.930> in<01:49:16.930> order<01:49:17.170> to<01:49:17.370> process 01:49:18.390 --> 01:49:18.400 align:start position:0% changes to and then in order to process 01:49:18.400 --> 01:49:21.570 align:start position:0% changes to and then in order to process inbound<01:49:18.880> changes<01:49:19.420> from<01:49:19.690> other<01:49:20.020> players<01:49:20.590> I'm 01:49:21.570 --> 01:49:21.580 align:start position:0% inbound changes from other players I'm 01:49:21.580 --> 01:49:27.300 align:start position:0% inbound changes from other players I'm going<01:49:22.000> to<01:49:23.670> get<01:49:24.670> the<01:49:25.420> log<01:49:25.990> view<01:49:26.260> go<01:49:27.040> through 01:49:27.300 --> 01:49:27.310 align:start position:0% going to get the log view go through 01:49:27.310 --> 01:49:28.710 align:start position:0% going to get the log view go through each<01:49:27.400> of<01:49:27.580> the<01:49:27.730> messages<01:49:27.940> which<01:49:28.450> are<01:49:28.540> just 01:49:28.710 --> 01:49:28.720 align:start position:0% each of the messages which are just 01:49:28.720 --> 01:49:30.600 align:start position:0% each of the messages which are just mutations<01:49:29.200> process<01:49:29.800> them<01:49:29.980> against<01:49:30.340> the<01:49:30.460> local 01:49:30.600 --> 01:49:30.610 align:start position:0% mutations process them against the local 01:49:30.610 --> 01:49:32.550 align:start position:0% mutations process them against the local state<01:49:31.000> machine<01:49:31.390> which<01:49:31.540> is<01:49:31.690> this<01:49:31.780> show<01:49:32.380> you 01:49:32.550 --> 01:49:32.560 align:start position:0% state machine which is this show you 01:49:32.560 --> 01:49:34.620 align:start position:0% state machine which is this show you third<01:49:32.740> fun<01:49:32.950> show<01:49:33.160> the<01:49:33.340> object<01:49:33.730> and<01:49:33.940> then 01:49:34.620 --> 01:49:34.630 align:start position:0% third fun show the object and then 01:49:34.630 --> 01:49:37.080 align:start position:0% third fun show the object and then return<01:49:35.260> that<01:49:35.290> as<01:49:35.560> a<01:49:35.590> state<01:49:35.920> object<01:49:36.340> so<01:49:36.850> let's 01:49:37.080 --> 01:49:37.090 align:start position:0% return that as a state object so let's 01:49:37.090 --> 01:49:41.260 align:start position:0% return that as a state object so let's see<01:49:37.210> if<01:49:37.270> that<01:49:37.300> picks<01:49:37.660> up<01:49:37.900> here<01:49:38.350> now<01:49:38.980> if<01:49:39.220> I<01:49:39.400> make 01:49:41.260 --> 01:49:41.270 align:start position:0% see if that picks up here now if I make 01:49:41.270 --> 01:49:45.040 align:start position:0% see if that picks up here now if I make it<01:49:41.660> should<01:49:41.960> stick<01:49:42.969> so<01:49:43.969> why<01:49:44.510> don't<01:49:44.690> you<01:49:44.780> just 01:49:45.040 --> 01:49:45.050 align:start position:0% it should stick so why don't you just 01:49:45.050 --> 01:49:47.430 align:start position:0% it should stick so why don't you just finish<01:49:45.290> off<01:49:45.469> this<01:49:45.650> part<01:49:46.040> is<01:49:46.370> we<01:49:46.580> can<01:49:46.699> go<01:49:46.850> into 01:49:47.430 --> 01:49:47.440 align:start position:0% finish off this part is we can go into 01:49:47.440 --> 01:49:51.250 align:start position:0% finish off this part is we can go into the<01:49:49.030> chat<01:49:50.030> application<01:49:50.719> which<01:49:50.870> is<01:49:51.020> another 01:49:51.250 --> 01:49:51.260 align:start position:0% the chat application which is another 01:49:51.260 --> 01:49:55.450 align:start position:0% the chat application which is another app<01:49:51.590> here<01:49:53.230> great<01:49:54.230> a<01:49:54.260> chat<01:49:54.560> room<01:49:54.830> and<01:49:54.980> I<01:49:55.100> can<01:49:55.250> say 01:49:55.450 --> 01:49:55.460 align:start position:0% app here great a chat room and I can say 01:49:55.460 --> 01:50:02.189 align:start position:0% app here great a chat room and I can say hey<01:49:57.340> not<01:49:58.340> rich 01:50:02.189 --> 01:50:02.199 align:start position:0% 01:50:02.199 --> 01:50:04.740 align:start position:0% surely<01:50:02.890> if<01:50:03.550> I<01:50:03.699> go<01:50:03.850> over<01:50:04.060> here<01:50:04.090> and<01:50:04.239> then<01:50:04.480> press 01:50:04.740 --> 01:50:04.750 align:start position:0% surely if I go over here and then press 01:50:04.750 --> 01:50:07.110 align:start position:0% surely if I go over here and then press ENTER<01:50:05.050> if<01:50:05.770> they<01:50:05.890> go<01:50:06.040> over<01:50:06.219> here<01:50:06.400> into<01:50:06.610> the<01:50:06.850> chat 01:50:07.110 --> 01:50:07.120 align:start position:0% ENTER if they go over here into the chat 01:50:07.120 --> 01:50:09.030 align:start position:0% ENTER if they go over here into the chat app<01:50:07.330> which<01:50:07.540> is<01:50:07.660> just<01:50:07.870> shown<01:50:08.080> up<01:50:08.260> magically<01:50:08.800> I 01:50:09.030 --> 01:50:09.040 align:start position:0% app which is just shown up magically I 01:50:09.040 --> 01:50:12.030 align:start position:0% app which is just shown up magically I can<01:50:09.670> see<01:50:09.910> that<01:50:10.179> I've<01:50:10.690> got<01:50:10.750> that<01:50:11.080> link<01:50:11.290> and<01:50:11.830> if<01:50:11.920> I 01:50:12.030 --> 01:50:12.040 align:start position:0% can see that I've got that link and if I 01:50:12.040 --> 01:50:13.830 align:start position:0% can see that I've got that link and if I can<01:50:12.190> click<01:50:12.429> on<01:50:12.460> here<01:50:12.940> they<01:50:13.390> go<01:50:13.510> straight<01:50:13.719> into 01:50:13.830 --> 01:50:13.840 align:start position:0% can click on here they go straight into 01:50:13.840 --> 01:50:14.610 align:start position:0% can click on here they go straight into the<01:50:13.960> show<01:50:14.110> me<01:50:14.170> game 01:50:14.610 --> 01:50:14.620 align:start position:0% the show me game 01:50:14.620 --> 01:50:16.890 align:start position:0% the show me game and<01:50:14.920> so<01:50:15.070> now<01:50:15.190> not<01:50:16.000> Ritchie<01:50:16.239> is<01:50:16.480> playing<01:50:16.750> the 01:50:16.890 --> 01:50:16.900 align:start position:0% and so now not Ritchie is playing the 01:50:16.900 --> 01:50:20.910 align:start position:0% and so now not Ritchie is playing the first<01:50:17.140> move<01:50:17.380> and<01:50:17.620> then<01:50:17.949> like<01:50:18.640> here<01:50:19.650> rich<01:50:20.650> here 01:50:20.910 --> 01:50:20.920 align:start position:0% first move and then like here rich here 01:50:20.920 --> 01:50:23.400 align:start position:0% first move and then like here rich here is<01:50:21.010> playing<01:50:21.219> the<01:50:21.370> second<01:50:21.760> move<01:50:21.910> and<01:50:22.360> then<01:50:22.540> you 01:50:23.400 --> 01:50:23.410 align:start position:0% is playing the second move and then you 01:50:23.410 --> 01:50:25.290 align:start position:0% is playing the second move and then you can<01:50:23.590> see<01:50:23.800> that<01:50:24.040> everything's<01:50:24.730> working<01:50:24.790> right 01:50:25.290 --> 01:50:25.300 align:start position:0% can see that everything's working right 01:50:25.300 --> 01:50:29.130 align:start position:0% can see that everything's working right so<01:50:25.449> automatic<01:50:26.260> no<01:50:27.330> 10-millimeter<01:50:28.330> woman<01:50:28.840> okay 01:50:29.130 --> 01:50:29.140 align:start position:0% so automatic no 10-millimeter woman okay 01:50:29.140 --> 01:50:35.180 align:start position:0% so automatic no 10-millimeter woman okay woman<01:50:29.560> right<01:50:30.160> let's<01:50:30.850> build<01:50:31.120> an<01:50:31.300> AI<01:50:31.570> to<01:50:31.750> play 01:50:35.180 --> 01:50:35.190 align:start position:0% 01:50:35.190 --> 01:50:38.880 align:start position:0% all<01:50:36.190> right<01:50:37.440> boss 01:50:38.880 --> 01:50:38.890 align:start position:0% all right boss 01:50:38.890 --> 01:51:03.510 align:start position:0% all right boss creates<01:50:40.530> see<01:50:41.530> the<01:50:41.739> demo<01:50:57.960> going<01:50:58.960> to<01:50:59.140> be<01:50:59.320> I<01:51:02.520> equal 01:51:03.510 --> 01:51:03.520 align:start position:0% creates see the demo going to be I equal 01:51:03.520 --> 01:51:04.260 align:start position:0% creates see the demo going to be I equal Fraser 01:51:04.260 --> 01:51:04.270 align:start position:0% Fraser 01:51:04.270 --> 01:51:07.140 align:start position:0% Fraser it's<01:51:04.840> because<01:51:05.170> you<01:51:05.350> trying<01:51:05.830> to<01:51:05.890> open 01:51:07.140 --> 01:51:07.150 align:start position:0% it's because you trying to open 01:51:07.150 --> 01:51:18.180 align:start position:0% it's because you trying to open yeah<01:51:08.150> I'm<01:51:08.210> gonna<01:51:10.720> kill<01:51:11.720> it 01:51:18.180 --> 01:51:18.190 align:start position:0% 01:51:18.190 --> 01:51:22.360 align:start position:0% okay<01:51:19.190> alright<01:51:19.640> so<01:51:19.880> let's<01:51:20.060> see<01:51:20.270> yeah<01:51:21.100> this<01:51:22.100> will 01:51:22.360 --> 01:51:22.370 align:start position:0% okay alright so let's see yeah this will 01:51:22.370 --> 01:51:38.760 align:start position:0% okay alright so let's see yeah this will be<01:51:35.920> can<01:51:36.920> I<01:51:37.040> get<01:51:37.220> from<01:51:37.430> the<01:51:37.550> crowd<01:51:37.670> two<01:51:38.030> minutes 01:51:38.760 --> 01:51:38.770 align:start position:0% be can I get from the crowd two minutes 01:51:38.770 --> 01:51:42.550 align:start position:0% be can I get from the crowd two minutes we<01:51:39.770> take<01:51:39.950> your<01:51:40.010> folks<01:51:40.690> now<01:51:41.690> these<01:51:41.870> the<01:51:42.170> next 01:51:42.550 --> 01:51:42.560 align:start position:0% we take your folks now these the next 01:51:42.560 --> 01:51:45.430 align:start position:0% we take your folks now these the next speaker<01:51:42.890> alright<01:51:43.130> so<01:51:43.250> next<01:51:43.370> speaker<01:51:44.350> do<01:51:45.350> they 01:51:45.430 --> 01:51:45.440 align:start position:0% speaker alright so next speaker do they 01:51:45.440 --> 01:51:47.050 align:start position:0% speaker alright so next speaker do they feel<01:51:45.590> anything<01:51:45.950> at<01:51:46.250> this<01:51:46.370> point<01:51:46.430> we're<01:51:46.790> super 01:51:47.050 --> 01:51:47.060 align:start position:0% feel anything at this point we're super 01:51:47.060 --> 01:51:50.010 align:start position:0% feel anything at this point we're super curious 01:51:50.010 --> 01:51:50.020 align:start position:0% 01:51:50.020 --> 01:51:51.580 align:start position:0% okay<01:51:51.020> here<01:51:51.290> we<01:51:51.320> go 01:51:51.580 --> 01:51:51.590 align:start position:0% okay here we go 01:51:51.590 --> 01:51:59.170 align:start position:0% okay here we go all<01:51:51.860> right<01:51:52.070> so<01:51:53.020> let's<01:51:54.020> see<01:51:54.350> fine<01:51:57.850> yeah<01:51:58.850> that's 01:51:59.170 --> 01:51:59.180 align:start position:0% all right so let's see fine yeah that's 01:51:59.180 --> 01:52:03.190 align:start position:0% all right so let's see fine yeah that's great<01:51:59.990> so<01:52:00.470> we've<01:52:01.400> got<01:52:01.670> the<01:52:02.240> body<01:52:02.450> on<01:52:02.690> I'm<01:52:03.050> gonna 01:52:03.190 --> 01:52:03.200 align:start position:0% great so we've got the body on I'm gonna 01:52:03.200 --> 01:52:04.930 align:start position:0% great so we've got the body on I'm gonna chain<01:52:03.500> citizen<01:52:03.950> that's<01:52:04.280> a<01:52:04.430> configuration 01:52:04.930 --> 01:52:04.940 align:start position:0% chain citizen that's a configuration 01:52:04.940 --> 01:52:06.880 align:start position:0% chain citizen that's a configuration file<01:52:05.270> I'm<01:52:05.330> gonna<01:52:05.480> change<01:52:05.750> that<01:52:05.930> to<01:52:05.990> show<01:52:06.830> you 01:52:06.880 --> 01:52:06.890 align:start position:0% file I'm gonna change that to show you 01:52:06.890 --> 01:52:09.040 align:start position:0% file I'm gonna change that to show you one<01:52:07.270> I'm<01:52:08.270> gonna<01:52:08.390> change<01:52:08.600> the<01:52:08.690> name<01:52:08.750> of<01:52:08.870> the 01:52:09.040 --> 01:52:09.050 align:start position:0% one I'm gonna change the name of the 01:52:09.050 --> 01:52:10.480 align:start position:0% one I'm gonna change the name of the view<01:52:09.230> which<01:52:09.380> is<01:52:09.530> the<01:52:09.650> virtual<01:52:10.040> I'm<01:52:10.190> gonna<01:52:10.340> send 01:52:10.480 --> 01:52:10.490 align:start position:0% view which is the virtual I'm gonna send 01:52:10.490 --> 01:52:12.880 align:start position:0% view which is the virtual I'm gonna send you<01:52:10.580> to<01:52:10.670> the<01:52:10.850> name<01:52:10.940> of<01:52:10.970> the<01:52:11.240> box<01:52:11.870> to<01:52:12.170> show 01:52:12.880 --> 01:52:12.890 align:start position:0% you to the name of the box to show 01:52:12.890 --> 01:52:15.790 align:start position:0% you to the name of the box to show deport<01:52:13.550> in<01:52:14.540> deaths<01:52:14.930> I'm<01:52:15.230> going<01:52:15.380> to<01:52:15.440> change<01:52:15.650> the 01:52:15.790 --> 01:52:15.800 align:start position:0% deport in deaths I'm going to change the 01:52:15.800 --> 01:52:18.040 align:start position:0% deport in deaths I'm going to change the view<01:52:16.070> to<01:52:16.100> the<01:52:16.400> same<01:52:16.640> database<01:52:16.910> name<01:52:17.720> that<01:52:17.930> we 01:52:18.040 --> 01:52:18.050 align:start position:0% view to the same database name that we 01:52:18.050 --> 01:52:19.149 align:start position:0% view to the same database name that we chose<01:52:18.320> yeah 01:52:19.149 --> 01:52:19.159 align:start position:0% chose yeah 01:52:19.159 --> 01:52:22.169 align:start position:0% chose yeah and<01:52:19.400> then<01:52:19.580> inside<01:52:19.909> applause<01:52:20.330> I'm<01:52:21.110> going<01:52:21.409> to 01:52:22.169 --> 01:52:22.179 align:start position:0% and then inside applause I'm going to 01:52:22.179 --> 01:52:26.459 align:start position:0% and then inside applause I'm going to same<01:52:23.179> standard<01:52:23.900> library<01:52:24.260> beast<01:52:24.469> earlier<01:52:24.920> and 01:52:26.459 --> 01:52:26.469 align:start position:0% same standard library beast earlier and 01:52:26.469 --> 01:52:30.070 align:start position:0% same standard library beast earlier and walks<01:52:28.090> processed<01:52:29.090> the<01:52:29.239> log<01:52:29.449> so<01:52:29.750> that's<01:52:29.929> the 01:52:30.070 --> 01:52:30.080 align:start position:0% walks processed the log so that's the 01:52:30.080 --> 01:52:31.720 align:start position:0% walks processed the log so that's the inbound<01:52:30.500> law<01:52:30.770> we<01:52:30.920> get<01:52:31.040> this<01:52:31.310> is<01:52:31.460> a<01:52:31.489> lambda 01:52:31.720 --> 01:52:31.730 align:start position:0% inbound law we get this is a lambda 01:52:31.730 --> 01:52:33.189 align:start position:0% inbound law we get this is a lambda function<01:52:31.909> gets<01:52:32.420> called<01:52:32.540> whenever<01:52:33.050> this 01:52:33.189 --> 01:52:33.199 align:start position:0% function gets called whenever this 01:52:33.199 --> 01:52:35.290 align:start position:0% function gets called whenever this irritation<01:52:33.739> on<01:52:33.830> the<01:52:33.889> feed<01:52:34.159> and<01:52:34.909> I'll<01:52:35.030> skip 01:52:35.290 --> 01:52:35.300 align:start position:0% irritation on the feed and I'll skip 01:52:35.300 --> 01:52:37.899 align:start position:0% irritation on the feed and I'll skip ahead<01:52:35.449> now<01:52:35.659> and<01:52:36.170> we'll<01:52:36.320> say<01:52:36.500> boss<01:52:36.800> a<01:52:37.159> pen<01:52:37.699> move 01:52:37.899 --> 01:52:37.909 align:start position:0% ahead now and we'll say boss a pen move 01:52:37.909 --> 01:52:40.270 align:start position:0% ahead now and we'll say boss a pen move so<01:52:38.150> well<01:52:38.300> we'll<01:52:38.900> get<01:52:38.989> the<01:52:39.170> set<01:52:39.440> of<01:52:39.590> valid<01:52:39.889> moves 01:52:40.270 --> 01:52:40.280 align:start position:0% so well we'll get the set of valid moves 01:52:40.280 --> 01:52:42.250 align:start position:0% so well we'll get the set of valid moves shown<01:52:40.610> the<01:52:40.730> standard<01:52:41.090> library<01:52:41.510> and<01:52:41.690> then 01:52:42.250 --> 01:52:42.260 align:start position:0% shown the standard library and then 01:52:42.260 --> 01:52:43.540 align:start position:0% shown the standard library and then we're<01:52:42.469> gonna<01:52:42.560> do<01:52:42.679> this<01:52:42.770> really<01:52:42.949> smart<01:52:43.340> thing 01:52:43.540 --> 01:52:43.550 align:start position:0% we're gonna do this really smart thing 01:52:43.550 --> 01:52:44.740 align:start position:0% we're gonna do this really smart thing where<01:52:43.730> we're<01:52:43.820> just<01:52:43.850> gonna<01:52:44.000> pick<01:52:44.330> and<01:52:44.540> move<01:52:44.659> a 01:52:44.740 --> 01:52:44.750 align:start position:0% where we're just gonna pick and move a 01:52:44.750 --> 01:52:54.250 align:start position:0% where we're just gonna pick and move a random<01:52:45.199> and<01:52:45.440> append<01:52:45.739> it<01:52:45.920> to<01:52:45.949> the<01:52:46.100> feet<01:52:46.400> so<01:52:53.260> in 01:52:54.250 --> 01:52:54.260 align:start position:0% random and append it to the feet so in 01:52:54.260 --> 01:52:57.070 align:start position:0% random and append it to the feet so in the<01:52:54.500> terminal<01:52:54.980> we're<01:52:55.159> gonna<01:52:55.250> say<01:52:55.489> quiet<01:52:56.080> walk 01:52:57.070 --> 01:52:57.080 align:start position:0% the terminal we're gonna say quiet walk 01:52:57.080 --> 01:53:02.559 align:start position:0% the terminal we're gonna say quiet walk register 01:53:02.559 --> 01:53:02.569 align:start position:0% 01:53:02.569 --> 01:53:05.580 align:start position:0% and<01:53:02.809> the<01:53:03.079> wire 01:53:05.580 --> 01:53:05.590 align:start position:0% and the wire 01:53:05.590 --> 01:53:08.430 align:start position:0% and the wire that's<01:53:06.490> right<01:53:07.390> so<01:53:07.630> I'm<01:53:07.690> running<01:53:07.840> the<01:53:08.020> bot<01:53:08.230> now 01:53:08.430 --> 01:53:08.440 align:start position:0% that's right so I'm running the bot now 01:53:08.440 --> 01:53:11.100 align:start position:0% that's right so I'm running the bot now in<01:53:08.740> its<01:53:08.890> death<01:53:09.160> mode<01:53:09.670> and<01:53:10.150> it's<01:53:10.300> debug<01:53:10.630> mode<01:53:10.900> on 01:53:11.100 --> 01:53:11.110 align:start position:0% in its death mode and it's debug mode on 01:53:11.110 --> 01:53:15.180 align:start position:0% in its death mode and it's debug mode on this<01:53:11.200> local<01:53:11.470> machine<01:53:11.890> so<01:53:13.290> bots<01:53:14.290> are<01:53:14.620> humans 01:53:15.180 --> 01:53:15.190 align:start position:0% this local machine so bots are humans 01:53:15.190 --> 01:53:17.280 align:start position:0% this local machine so bots are humans too<01:53:15.280> and<01:53:15.910> so<01:53:16.270> I<01:53:16.300> should<01:53:16.450> be<01:53:16.690> able<01:53:16.780> to<01:53:16.930> if<01:53:17.200> I 01:53:17.280 --> 01:53:17.290 align:start position:0% too and so I should be able to if I 01:53:17.290 --> 01:53:22.830 align:start position:0% too and so I should be able to if I click<01:53:17.500> on<01:53:17.590> here<01:53:17.650> I'm<01:53:18.130> going<01:53:18.490> to<01:53:18.730> I<01:53:21.690> think<01:53:22.690> this 01:53:22.830 --> 01:53:22.840 align:start position:0% click on here I'm going to I think this 01:53:22.840 --> 01:53:27.450 align:start position:0% click on here I'm going to I think this is<01:53:22.960> where<01:53:23.200> we<01:53:23.350> actually<01:53:23.380> do<01:53:23.920> give<01:53:24.640> up<01:53:26.460> what 01:53:27.450 --> 01:53:27.460 align:start position:0% is where we actually do give up what 01:53:27.460 --> 01:53:32.490 align:start position:0% is where we actually do give up what would<01:53:27.670> happen<01:53:28.150> is<01:53:29.430> so<01:53:30.430> what<01:53:30.850> what<01:53:31.090> what<01:53:32.020> what 01:53:32.490 --> 01:53:32.500 align:start position:0% would happen is so what what what what 01:53:32.500 --> 01:53:34.230 align:start position:0% would happen is so what what what what would<01:53:32.680> happen<01:53:33.070> here<01:53:33.310> is<01:53:33.460> that<01:53:33.490> publishing<01:53:34.150> the 01:53:34.230 --> 01:53:34.240 align:start position:0% would happen here is that publishing the 01:53:34.240 --> 01:53:35.970 align:start position:0% would happen here is that publishing the metadata<01:53:34.660> of<01:53:34.810> the<01:53:34.930> plot<01:53:35.230> to<01:53:35.560> the<01:53:35.680> local 01:53:35.970 --> 01:53:35.980 align:start position:0% metadata of the plot to the local 01:53:35.980 --> 01:53:37.980 align:start position:0% metadata of the plot to the local blockchain<01:53:36.430> I<01:53:36.700> can<01:53:37.090> then<01:53:37.210> discover<01:53:37.750> it<01:53:37.960> by 01:53:37.980 --> 01:53:37.990 align:start position:0% blockchain I can then discover it by 01:53:37.990 --> 01:53:41.310 align:start position:0% blockchain I can then discover it by clearing<01:53:38.620> the<01:53:38.650> chain<01:53:39.010> from<01:53:39.310> the<01:53:39.400> browser<01:53:40.320> send 01:53:41.310 --> 01:53:41.320 align:start position:0% clearing the chain from the browser send 01:53:41.320 --> 01:53:43.440 align:start position:0% clearing the chain from the browser send the<01:53:41.410> signal<01:53:41.830> of<01:53:41.980> discovery<01:53:42.790> key<01:53:42.970> to<01:53:43.150> the<01:53:43.240> bots 01:53:43.440 --> 01:53:43.450 align:start position:0% the signal of discovery key to the bots 01:53:43.450 --> 01:53:45.990 align:start position:0% the signal of discovery key to the bots in<01:53:43.660> swarms<01:53:43.990> that<01:53:44.350> joins<01:53:44.650> the<01:53:44.920> party<01:53:45.130> and<01:53:45.610> then 01:53:45.990 --> 01:53:46.000 align:start position:0% in swarms that joins the party and then 01:53:46.000 --> 01:53:49.590 align:start position:0% in swarms that joins the party and then it<01:53:46.120> gets<01:53:46.240> all<01:53:46.450> of<01:53:46.510> the<01:53:46.660> mutations<01:53:47.370> and<01:53:48.600> we 01:53:49.590 --> 01:53:49.600 align:start position:0% it gets all of the mutations and we 01:53:49.600 --> 01:53:52.010 align:start position:0% it gets all of the mutations and we would<01:53:49.780> be<01:53:49.900> able<01:53:50.020> to<01:53:50.170> play<01:53:50.410> in<01:53:51.040> this<01:53:51.340> case 01:53:52.010 --> 01:53:52.020 align:start position:0% would be able to play in this case 01:53:52.020 --> 01:54:01.470 align:start position:0% would be able to play in this case unless<01:53:54.750> okay 01:54:01.470 --> 01:54:01.480 align:start position:0% 01:54:01.480 --> 01:54:04.480 align:start position:0% since<01:54:02.480> we<01:54:02.660> since<01:54:03.050> you<01:54:03.260> are<01:54:03.440> so<01:54:03.740> generous<01:54:04.160> and 01:54:04.480 --> 01:54:04.490 align:start position:0% since we since you are so generous and 01:54:04.490 --> 01:54:07.090 align:start position:0% since we since you are so generous and we<01:54:04.670> got<01:54:04.820> this<01:54:04.940> small<01:54:05.090> let's<01:54:05.630> just<01:54:05.840> try<01:54:06.020> the<01:54:06.100> one 01:54:07.090 --> 01:54:07.100 align:start position:0% we got this small let's just try the one 01:54:07.100 --> 01:54:12.880 align:start position:0% we got this small let's just try the one at<01:54:07.130> fault<01:54:07.250> register<01:54:08.620> long<01:54:09.620> dong<01:54:09.860> Qiang<01:54:11.890> okay 01:54:12.880 --> 01:54:12.890 align:start position:0% at fault register long dong Qiang okay 01:54:12.890 --> 01:54:14.830 align:start position:0% at fault register long dong Qiang okay so<01:54:12.950> we've<01:54:13.370> seen<01:54:13.490> that's<01:54:14.300> more<01:54:14.630> promising 01:54:14.830 --> 01:54:14.840 align:start position:0% so we've seen that's more promising 01:54:14.840 --> 01:54:18.490 align:start position:0% so we've seen that's more promising while<01:54:16.180> okay<01:54:17.180> the<01:54:17.330> block<01:54:17.600> times<01:54:17.930> about<01:54:18.230> five 01:54:18.490 --> 01:54:18.500 align:start position:0% while okay the block times about five 01:54:18.500 --> 01:54:21.610 align:start position:0% while okay the block times about five seconds<01:54:18.980> so<01:54:19.070> now<01:54:19.430> if<01:54:19.580> we<01:54:19.640> clear<01:54:20.120> these<01:54:20.620> she's 01:54:21.610 --> 01:54:21.620 align:start position:0% seconds so now if we clear these she's 01:54:21.620 --> 01:54:24.400 align:start position:0% seconds so now if we clear these she's setting<01:54:22.010> listen<01:54:22.630> tell<01:54:23.630> me<01:54:23.660> the<01:54:23.840> settings 01:54:24.400 --> 01:54:24.410 align:start position:0% setting listen tell me the settings 01:54:24.410 --> 01:54:26.710 align:start position:0% setting listen tell me the settings ladies<01:54:25.130> me<01:54:25.370> yeah<01:54:25.940> wait<01:54:26.210> wait<01:54:26.390> you<01:54:26.480> said<01:54:26.630> that 01:54:26.710 --> 01:54:26.720 align:start position:0% ladies me yeah wait wait you said that 01:54:26.720 --> 01:54:34.630 align:start position:0% ladies me yeah wait wait you said that beautiful<01:54:27.140> one 01:54:34.630 --> 01:54:34.640 align:start position:0% 01:54:34.640 --> 01:54:40.990 align:start position:0% this<01:54:35.030> is<01:54:35.180> exciting<01:54:35.719> oh<01:54:38.140> right<01:54:39.140> okay<01:54:40.000> surprise 01:54:40.990 --> 01:54:41.000 align:start position:0% this is exciting oh right okay surprise 01:54:41.000 --> 01:54:45.270 align:start position:0% this is exciting oh right okay surprise them<01:54:41.710> okay<01:54:42.710> so<01:54:42.770> let's<01:54:43.760> create<01:54:43.969> a<01:54:44.060> new<01:54:44.090> game<01:54:44.420> and 01:54:45.270 --> 01:54:45.280 align:start position:0% them okay so let's create a new game and 01:54:45.280 --> 01:54:47.920 align:start position:0% them okay so let's create a new game and we're<01:54:46.280> going<01:54:46.460> to<01:54:46.520> members<01:54:46.880> well<01:54:47.239> we<01:54:47.630> can<01:54:47.810> now 01:54:47.920 --> 01:54:47.930 align:start position:0% we're going to members well we can now 01:54:47.930 --> 01:54:51.550 align:start position:0% we're going to members well we can now see<01:54:48.140> shogi<01:54:48.560> bar<01:54:48.770> on<01:54:49.040> the<01:54:49.880> registry<01:54:50.360> show<01:54:51.320> you 01:54:51.550 --> 01:54:51.560 align:start position:0% see shogi bar on the registry show you 01:54:51.560 --> 01:54:56.110 align:start position:0% see shogi bar on the registry show you Bob<01:54:51.770> I<01:54:52.100> was<01:54:52.460> joining<01:54:52.969> the<01:54:53.000> party<01:54:54.820> if<01:54:55.820> I<01:54:55.940> click 01:54:56.110 --> 01:54:56.120 align:start position:0% Bob I was joining the party if I click 01:54:56.120 --> 01:54:58.390 align:start position:0% Bob I was joining the party if I click on<01:54:56.210> the<01:54:56.330> debug<01:54:56.480> panel<01:54:56.840> here<01:54:57.140> and<01:54:57.440> see<01:54:57.680> the 01:54:58.390 --> 01:54:58.400 align:start position:0% on the debug panel here and see the 01:54:58.400 --> 01:55:01.120 align:start position:0% on the debug panel here and see the different<01:54:59.469> members<01:55:00.469> of<01:55:00.620> the<01:55:00.770> swarm 01:55:01.120 --> 01:55:01.130 align:start position:0% different members of the swarm 01:55:01.130 --> 01:55:05.200 align:start position:0% different members of the swarm eventually<01:55:02.090> now<01:55:02.930> if<01:55:03.020> I<01:55:03.110> make<01:55:03.260> a<01:55:03.290> move<01:55:04.060> for<01:55:05.060> us 01:55:05.200 --> 01:55:05.210 align:start position:0% eventually now if I make a move for us 01:55:05.210 --> 01:55:11.880 align:start position:0% eventually now if I make a move for us or<01:55:05.360> what<01:55:05.480> happened 01:55:11.880 --> 01:55:11.890 align:start position:0% 01:55:11.890 --> 01:55:28.980 align:start position:0% oh<01:55:17.970> it's<01:55:18.970> unhappy<01:55:26.700> okay<01:55:27.700> so<01:55:27.880> that's<01:55:28.690> my<01:55:28.810> name 01:55:28.980 --> 01:55:28.990 align:start position:0% oh it's unhappy okay so that's my name 01:55:28.990 --> 01:55:33.270 align:start position:0% oh it's unhappy okay so that's my name I'm<01:55:29.710> French<01:55:30.040> so<01:55:30.130> the<01:55:30.490> exit<01:55:31.090> is<01:55:31.240> warranted<01:55:32.280> do 01:55:33.270 --> 01:55:33.280 align:start position:0% I'm French so the exit is warranted do 01:55:33.280 --> 01:55:34.010 align:start position:0% I'm French so the exit is warranted do anything<01:55:33.610> about<01:55:33.700> it 01:55:34.010 --> 01:55:34.020 align:start position:0% anything about it 01:55:34.020 --> 01:55:37.980 align:start position:0% anything about it 24<01:55:35.020> years<01:55:35.230> sorry<01:55:36.150> if<01:55:37.150> you<01:55:37.330> don't<01:55:37.540> want<01:55:37.690> if<01:55:37.870> I 01:55:37.980 --> 01:55:37.990 align:start position:0% 24 years sorry if you don't want if I 01:55:37.990 --> 01:55:39.480 align:start position:0% 24 years sorry if you don't want if I say<01:55:38.290> I'll<01:55:38.830> be<01:55:38.980> good 01:55:39.480 --> 01:55:39.490 align:start position:0% say I'll be good 01:55:39.490 --> 01:55:41.130 align:start position:0% say I'll be good understand<01:55:39.940> myself<01:55:40.090> but<01:55:40.540> you<01:55:40.720> can<01:55:40.840> ask<01:55:40.990> me 01:55:41.130 --> 01:55:41.140 align:start position:0% understand myself but you can ask me 01:55:41.140 --> 01:55:45.440 align:start position:0% understand myself but you can ask me questions<01:55:42.270> let's<01:55:43.270> go<01:55:43.420> go 01:55:45.440 --> 01:55:45.450 align:start position:0% questions let's go go 01:55:45.450 --> 01:55:47.790 align:start position:0% questions let's go go so<01:55:46.450> here's<01:55:47.110> what<01:55:47.230> I'm<01:55:47.290> going<01:55:47.440> to<01:55:47.500> talk<01:55:47.740> about 01:55:47.790 --> 01:55:47.800 align:start position:0% so here's what I'm going to talk about 01:55:47.800 --> 01:55:49.740 align:start position:0% so here's what I'm going to talk about the<01:55:48.340> other<01:55:48.580> side<01:55:48.880> of<01:55:49.000> the<01:55:49.090> equation<01:55:49.330> so 01:55:49.740 --> 01:55:49.750 align:start position:0% the other side of the equation so 01:55:49.750 --> 01:55:51.420 align:start position:0% the other side of the equation so everybody<01:55:50.230> hear<01:55:50.440> stuff<01:55:50.680> give<01:55:50.860> up<01:55:50.980> new 01:55:51.420 --> 01:55:51.430 align:start position:0% everybody hear stuff give up new 01:55:51.430 --> 01:55:53.580 align:start position:0% everybody hear stuff give up new innovative<01:55:51.910> ways<01:55:52.150> of<01:55:52.420> doing<01:55:52.570> but<01:55:52.870> chain<01:55:53.170> also 01:55:53.580 --> 01:55:53.590 align:start position:0% innovative ways of doing but chain also 01:55:53.590 --> 01:55:56.220 align:start position:0% innovative ways of doing but chain also few<01:55:53.890> puzzles<01:55:54.040> come<01:55:54.490> together<01:55:54.640> I<01:55:55.150> need<01:55:55.960> to<01:55:56.080> tell 01:55:56.220 --> 01:55:56.230 align:start position:0% few puzzles come together I need to tell 01:55:56.230 --> 01:55:58.650 align:start position:0% few puzzles come together I need to tell you<01:55:56.320> about<01:55:56.410> the<01:55:56.710> risky<01:55:57.070> side<01:55:57.310> of<01:55:58.120> what<01:55:58.540> you 01:55:58.650 --> 01:55:58.660 align:start position:0% you about the risky side of what you 01:55:58.660 --> 01:56:01.020 align:start position:0% you about the risky side of what you guys<01:55:58.810> do<01:55:59.020> which<01:55:59.170> is<01:55:59.380> natural<01:56:00.100> desti<01:56:00.550> you're 01:56:01.020 --> 01:56:01.030 align:start position:0% guys do which is natural desti you're 01:56:01.030 --> 01:56:05.220 align:start position:0% guys do which is natural desti you're lucky<01:56:01.420> right<01:56:01.810> so<01:56:02.140> the<01:56:02.770> issue<01:56:02.950> here<01:56:03.160> is<01:56:03.370> that<01:56:04.230> we 01:56:05.220 --> 01:56:05.230 align:start position:0% lucky right so the issue here is that we 01:56:05.230 --> 01:56:07.500 align:start position:0% lucky right so the issue here is that we are<01:56:05.890> not<01:56:06.010> creating<01:56:06.190> too<01:56:06.730> much<01:56:06.880> pains<01:56:07.210> for 01:56:07.500 --> 01:56:07.510 align:start position:0% are not creating too much pains for 01:56:07.510 --> 01:56:09.570 align:start position:0% are not creating too much pains for people<01:56:07.810> who<01:56:07.900> want<01:56:08.110> to<01:56:08.140> make<01:56:08.620> sure<01:56:08.680> and<01:56:09.310> things 01:56:09.570 --> 01:56:09.580 align:start position:0% people who want to make sure and things 01:56:09.580 --> 01:56:11.550 align:start position:0% people who want to make sure and things that<01:56:09.640> you<01:56:09.820> work<01:56:10.060> as<01:56:10.300> they<01:56:10.570> should<01:56:10.840> right<01:56:11.260> so 01:56:11.550 --> 01:56:11.560 align:start position:0% that you work as they should right so 01:56:11.560 --> 01:56:17.460 align:start position:0% that you work as they should right so that's<01:56:12.370> the<01:56:12.640> old<01:56:12.760> wall<01:56:15.780> you<01:56:16.780> know<01:56:16.900> reading 01:56:17.460 --> 01:56:17.470 align:start position:0% that's the old wall you know reading 01:56:17.470 --> 01:56:19.040 align:start position:0% that's the old wall you know reading reading<01:56:17.680> reading<01:56:17.980> complaints 01:56:19.040 --> 01:56:19.050 align:start position:0% reading reading complaints 01:56:19.050 --> 01:56:22.220 align:start position:0% reading reading complaints much<01:56:19.170> that<01:56:19.710> simple<01:56:20.550> communities<01:56:21.179> cluster<01:56:21.570> you 01:56:22.220 --> 01:56:22.230 align:start position:0% much that simple communities cluster you 01:56:22.230 --> 01:56:24.260 align:start position:0% much that simple communities cluster you know<01:56:22.380> you<01:56:22.889> know<01:56:22.980> convenience<01:56:23.460> like<01:56:23.730> lemons 01:56:24.260 --> 01:56:24.270 align:start position:0% know you know convenience like lemons 01:56:24.270 --> 01:56:28.790 align:start position:0% know you know convenience like lemons instance<01:56:25.610> spray<01:56:26.610> flexible<01:56:27.230> be<01:56:28.230> asynchronous 01:56:28.790 --> 01:56:28.800 align:start position:0% instance spray flexible be asynchronous 01:56:28.800 --> 01:56:31.700 align:start position:0% instance spray flexible be asynchronous mister<01:56:29.219> time<01:56:29.659> lots<01:56:30.659> of<01:56:30.750> web<01:56:30.989> series<01:56:31.260> this<01:56:31.500> week 01:56:31.700 --> 01:56:31.710 align:start position:0% mister time lots of web series this week 01:56:31.710 --> 01:56:33.770 align:start position:0% mister time lots of web series this week software<01:56:32.130> is<01:56:32.280> not<01:56:32.670> pretty<01:56:33.119> well<01:56:33.360> test<01:56:33.599> it's 01:56:33.770 --> 01:56:33.780 align:start position:0% software is not pretty well test it's 01:56:33.780 --> 01:56:35.959 align:start position:0% software is not pretty well test it's pretty<01:56:34.020> hard<01:56:34.260> to<01:56:34.320> test<01:56:34.559> at<01:56:34.739> scale<01:56:35.010> any<01:56:35.790> which 01:56:35.959 --> 01:56:35.969 align:start position:0% pretty hard to test at scale any which 01:56:35.969 --> 01:56:38.180 align:start position:0% pretty hard to test at scale any which test<01:56:36.300> things<01:56:36.540> me<01:56:36.869> into<01:56:37.170> just<01:56:37.349> this<01:56:37.559> like<01:56:37.889> just 01:56:38.180 --> 01:56:38.190 align:start position:0% test things me into just this like just 01:56:38.190 --> 01:56:41.060 align:start position:0% test things me into just this like just go<01:56:38.489> for<01:56:38.670> test<01:56:38.849> net<01:56:39.059> try<01:56:39.960> for<01:56:40.230> 50<01:56:40.469> weeks 01:56:41.060 --> 01:56:41.070 align:start position:0% go for test net try for 50 weeks 01:56:41.070 --> 01:56:44.450 align:start position:0% go for test net try for 50 weeks see<01:56:41.489> if<01:56:41.550> things<01:56:41.730> stick<01:56:42.500> spine<01:56:43.500> up<01:56:43.679> the<01:56:43.920> handle 01:56:44.450 --> 01:56:44.460 align:start position:0% see if things stick spine up the handle 01:56:44.460 --> 01:56:48.379 align:start position:0% see if things stick spine up the handle and<01:56:45.409> it's<01:56:46.409> a<01:56:46.500> new<01:56:46.679> stack<01:56:47.010> a<01:56:47.250> new<01:56:47.550> stack<01:56:47.820> we<01:56:48.210> will 01:56:48.379 --> 01:56:48.389 align:start position:0% and it's a new stack a new stack we will 01:56:48.389 --> 01:56:49.540 align:start position:0% and it's a new stack a new stack we will need<01:56:48.570> to<01:56:48.690> start<01:56:48.750> from<01:56:49.079> scratch<01:56:49.320> again 01:56:49.540 --> 01:56:49.550 align:start position:0% need to start from scratch again 01:56:49.550 --> 01:56:51.890 align:start position:0% need to start from scratch again creating<01:56:50.550> new<01:56:50.699> testing<01:56:51.090> tools<01:56:51.420> a<01:56:51.510> specific 01:56:51.890 --> 01:56:51.900 align:start position:0% creating new testing tools a specific 01:56:51.900 --> 01:56:57.640 align:start position:0% creating new testing tools a specific level<01:56:52.050> of<01:56:52.199> change<01:56:55.400> if<01:56:56.400> you<01:56:56.579> recommends 01:56:57.640 --> 01:56:57.650 align:start position:0% level of change if you recommends 01:56:57.650 --> 01:57:02.930 align:start position:0% level of change if you recommends networks<01:56:58.650> this<01:56:59.309> one<01:56:59.489> here<01:56:59.809> we<01:57:00.809> have<01:57:01.940> almost 01:57:02.930 --> 01:57:02.940 align:start position:0% networks this one here we have almost 01:57:02.940 --> 01:57:06.020 align:start position:0% networks this one here we have almost critical<01:57:03.630> asynchronous<01:57:04.590> not<01:57:05.400> always<01:57:05.670> final 01:57:06.020 --> 01:57:06.030 align:start position:0% critical asynchronous not always final 01:57:06.030 --> 01:57:09.129 align:start position:0% critical asynchronous not always final even<01:57:06.599> fidelity<01:57:07.170> itself<01:57:07.500> is<01:57:07.679> fun<01:57:07.980> to<01:57:08.099> test 01:57:09.129 --> 01:57:09.139 align:start position:0% even fidelity itself is fun to test 01:57:09.139 --> 01:57:11.899 align:start position:0% even fidelity itself is fun to test there's<01:57:10.139> reorder<01:57:10.650> chains<01:57:10.980> that's<01:57:11.489> something 01:57:11.899 --> 01:57:11.909 align:start position:0% there's reorder chains that's something 01:57:11.909 --> 01:57:14.450 align:start position:0% there's reorder chains that's something you<01:57:12.179> need<01:57:12.300> to<01:57:12.449> be<01:57:12.540> prepared<01:57:12.900> for<01:57:12.989> any<01:57:13.530> quiz<01:57:13.800> so 01:57:14.450 --> 01:57:14.460 align:start position:0% you need to be prepared for any quiz so 01:57:14.460 --> 01:57:15.770 align:start position:0% you need to be prepared for any quiz so you<01:57:14.639> don't<01:57:14.820> have<01:57:14.940> like<01:57:15.000> the<01:57:15.389> instance 01:57:15.770 --> 01:57:15.780 align:start position:0% you don't have like the instance 01:57:15.780 --> 01:57:18.049 align:start position:0% you don't have like the instance information<01:57:16.469> something<01:57:16.800> you<01:57:17.369> know<01:57:17.460> hours<01:57:17.849> to 01:57:18.049 --> 01:57:18.059 align:start position:0% information something you know hours to 01:57:18.059 --> 01:57:21.830 align:start position:0% information something you know hours to actually<01:57:18.300> test<01:57:18.510> available<01:57:19.079> network<01:57:20.809> we<01:57:21.809> can 01:57:21.830 --> 01:57:21.840 align:start position:0% actually test available network we can 01:57:21.840 --> 01:57:23.780 align:start position:0% actually test available network we can now<01:57:22.199> see<01:57:22.440> that<01:57:22.469> between<01:57:22.770> proof-of-work<01:57:23.280> for 01:57:23.780 --> 01:57:23.790 align:start position:0% now see that between proof-of-work for 01:57:23.790 --> 01:57:26.799 align:start position:0% now see that between proof-of-work for state<01:57:24.000> trade-offs<01:57:24.980> performance<01:57:25.980> three 01:57:26.799 --> 01:57:26.809 align:start position:0% state trade-offs performance three 01:57:26.809 --> 01:57:28.020 align:start position:0% state trade-offs performance three incision 01:57:28.020 --> 01:57:28.030 align:start position:0% incision 01:57:28.030 --> 01:57:30.180 align:start position:0% incision since<01:57:28.210> approaches<01:57:28.870> so<01:57:29.530> we<01:57:29.680> see<01:57:29.830> all<01:57:29.890> sorts<01:57:30.070> of 01:57:30.180 --> 01:57:30.190 align:start position:0% since approaches so we see all sorts of 01:57:30.190 --> 01:57:32.040 align:start position:0% since approaches so we see all sorts of different<01:57:30.400> ways<01:57:30.670> this<01:57:31.210> playing<01:57:31.870> out<01:57:31.990> of 01:57:32.040 --> 01:57:32.050 align:start position:0% different ways this playing out of 01:57:32.050 --> 01:57:35.640 align:start position:0% different ways this playing out of investing<01:57:32.770> and<01:57:33.450> it's<01:57:34.450> just<01:57:34.630> not<01:57:35.350> the<01:57:35.500> blood 01:57:35.640 --> 01:57:35.650 align:start position:0% investing and it's just not the blood 01:57:35.650 --> 01:57:37.290 align:start position:0% investing and it's just not the blood seems<01:57:35.830> like<01:57:35.980> everything<01:57:36.490> built<01:57:36.700> on<01:57:36.880> top<01:57:37.030> of<01:57:37.090> it 01:57:37.290 --> 01:57:37.300 align:start position:0% seems like everything built on top of it 01:57:37.300 --> 01:57:40.320 align:start position:0% seems like everything built on top of it starts<01:57:37.660> to<01:57:38.050> it's<01:57:38.260> great<01:57:38.440> to<01:57:39.060> civilization 01:57:40.320 --> 01:57:40.330 align:start position:0% starts to it's great to civilization 01:57:40.330 --> 01:57:42.450 align:start position:0% starts to it's great to civilization you're<01:57:40.630> at<01:57:40.750> Norco<01:57:41.140> we<01:57:41.260> have<01:57:41.350> a<01:57:41.410> breach<01:57:41.980> all<01:57:42.370> of 01:57:42.450 --> 01:57:42.460 align:start position:0% you're at Norco we have a breach all of 01:57:42.460 --> 01:57:43.950 align:start position:0% you're at Norco we have a breach all of a<01:57:42.520> sudden<01:57:42.550> have<01:57:43.150> things<01:57:43.420> you<01:57:43.510> could<01:57:43.660> take<01:57:43.810> for 01:57:43.950 --> 01:57:43.960 align:start position:0% a sudden have things you could take for 01:57:43.960 --> 01:57:45.990 align:start position:0% a sudden have things you could take for granted<01:57:44.140> start<01:57:44.770> to<01:57:45.010> misbehave 01:57:45.990 --> 01:57:46.000 align:start position:0% granted start to misbehave 01:57:46.000 --> 01:57:50.490 align:start position:0% granted start to misbehave Unwin<01:57:47.430> and<01:57:48.430> that's<01:57:49.300> you<01:57:50.230> know<01:57:50.260> thick 01:57:50.490 --> 01:57:50.500 align:start position:0% Unwin and that's you know thick 01:57:50.500 --> 01:57:53.910 align:start position:0% Unwin and that's you know thick victories<01:57:50.950> so<01:57:51.400> we'll<01:57:52.060> talk<01:57:52.210> about<01:57:52.360> that<01:57:52.920> if 01:57:53.910 --> 01:57:53.920 align:start position:0% victories so we'll talk about that if 01:57:53.920 --> 01:57:58.520 align:start position:0% victories so we'll talk about that if you<01:57:54.100> want<01:57:54.250> to<01:57:54.340> learn<01:57:54.430> more<01:57:54.640> real<01:57:54.820> we<01:57:55.180> also<01:57:55.300> have 01:57:58.520 --> 01:57:58.530 align:start position:0% 01:57:58.530 --> 01:58:01.350 align:start position:0% we<01:57:59.530> also<01:57:59.560> have<01:57:59.890> new<01:58:00.640> metrics<01:58:00.970> to<01:58:01.030> capture 01:58:01.350 --> 01:58:01.360 align:start position:0% we also have new metrics to capture 01:58:01.360 --> 01:58:04.380 align:start position:0% we also have new metrics to capture before<01:58:02.050> you<01:58:02.320> just<01:58:02.530> be<01:58:02.650> like<01:58:03.030> what's<01:58:04.030> a<01:58:04.090> delay 01:58:04.380 --> 01:58:04.390 align:start position:0% before you just be like what's a delay 01:58:04.390 --> 01:58:08.580 align:start position:0% before you just be like what's a delay how<01:58:04.810> much<01:58:05.250> do<01:58:06.250> you<01:58:06.490> replace<01:58:06.760> to<01:58:06.940> buy<01:58:07.530> now<01:58:08.530> we 01:58:08.580 --> 01:58:08.590 align:start position:0% how much do you replace to buy now we 01:58:08.590 --> 01:58:10.440 align:start position:0% how much do you replace to buy now we have<01:58:08.860> all<01:58:09.520> sorts<01:58:09.700> of<01:58:09.820> fees<01:58:09.970> we<01:58:10.120> want<01:58:10.330> to 01:58:10.440 --> 01:58:10.450 align:start position:0% have all sorts of fees we want to 01:58:10.450 --> 01:58:12.450 align:start position:0% have all sorts of fees we want to capture<01:58:10.660> which<01:58:11.350> are<01:58:11.530> more<01:58:11.680> critical<01:58:11.980> to<01:58:12.220> the 01:58:12.450 --> 01:58:12.460 align:start position:0% capture which are more critical to the 01:58:12.460 --> 01:58:14.400 align:start position:0% capture which are more critical to the purpose<01:58:12.820> of<01:58:12.970> the<01:58:13.060> network<01:58:13.450> in<01:58:13.720> top<01:58:14.200> of<01:58:14.230> that 01:58:14.400 --> 01:58:14.410 align:start position:0% purpose of the network in top of that 01:58:14.410 --> 01:58:16.680 align:start position:0% purpose of the network in top of that approaching<01:58:14.980> specific<01:58:15.460> so<01:58:16.150> if<01:58:16.210> we<01:58:16.330> failure 01:58:16.680 --> 01:58:16.690 align:start position:0% approaching specific so if we failure 01:58:16.690 --> 01:58:18.960 align:start position:0% approaching specific so if we failure out<01:58:16.870> there<01:58:17.140> some<01:58:18.070> of<01:58:18.190> what<01:58:18.430> we<01:58:18.580> have<01:58:18.610> to 01:58:18.960 --> 01:58:18.970 align:start position:0% out there some of what we have to 01:58:18.970 --> 01:58:20.880 align:start position:0% out there some of what we have to capture<01:58:19.480> for<01:58:19.720> every<01:58:20.080> love<01:58:20.290> for<01:58:20.530> every<01:58:20.740> child 01:58:20.880 --> 01:58:20.890 align:start position:0% capture for every love for every child 01:58:20.890 --> 01:58:23.160 align:start position:0% capture for every love for every child actually<01:58:21.100> the<01:58:21.850> size<01:58:22.060> to<01:58:22.540> get<01:58:22.630> the<01:58:22.750> center<01:58:23.050> of 01:58:23.160 --> 01:58:23.170 align:start position:0% actually the size to get the center of 01:58:23.170 --> 01:58:24.840 align:start position:0% actually the size to get the center of zooming<01:58:23.410> we<01:58:24.100> have<01:58:24.190> to<01:58:24.310> get<01:58:24.430> all<01:58:24.550> the<01:58:24.670> time 01:58:24.840 --> 01:58:24.850 align:start position:0% zooming we have to get all the time 01:58:24.850 --> 01:58:27.570 align:start position:0% zooming we have to get all the time sensors<01:58:25.330> to<01:58:25.450> compute<01:58:25.810> the<01:58:26.050> median<01:58:26.950> time<01:58:27.310> and 01:58:27.570 --> 01:58:27.580 align:start position:0% sensors to compute the median time and 01:58:27.580 --> 01:58:29.520 align:start position:0% sensors to compute the median time and average<01:58:27.670> time<01:58:28.060> we<01:58:28.990> have<01:58:29.140> all<01:58:29.290> the<01:58:29.380> information 01:58:29.520 --> 01:58:29.530 align:start position:0% average time we have all the information 01:58:29.530 --> 01:58:32.880 align:start position:0% average time we have all the information on<01:58:29.890> the<01:58:30.010> blog's<01:58:30.540> also<01:58:31.540> like<01:58:31.690> traditional<01:58:32.230> one 01:58:32.880 --> 01:58:32.890 align:start position:0% on the blog's also like traditional one 01:58:32.890 --> 01:58:38.280 align:start position:0% on the blog's also like traditional one also<01:58:33.250> emphasized<01:58:33.880> collection<01:58:34.750> exercise<01:58:37.290> most 01:58:38.280 --> 01:58:38.290 align:start position:0% also emphasized collection exercise most 01:58:38.290 --> 01:58:39.540 align:start position:0% also emphasized collection exercise most efficient<01:58:38.560> time<01:58:38.800> it's<01:58:39.100> gonna<01:58:39.250> be<01:58:39.370> tricky 01:58:39.540 --> 01:58:39.550 align:start position:0% efficient time it's gonna be tricky 01:58:39.550 --> 01:58:41.160 align:start position:0% efficient time it's gonna be tricky especially<01:58:39.760> when<01:58:40.360> we<01:58:40.450> start<01:58:40.540> doing<01:58:40.750> double 01:58:41.160 --> 01:58:41.170 align:start position:0% especially when we start doing double 01:58:41.170 --> 01:58:44.700 align:start position:0% especially when we start doing double engine<01:58:41.260> testing<01:58:42.030> and<01:58:43.080> the<01:58:44.080> head<01:58:44.500> of<01:58:44.620> an 01:58:44.700 --> 01:58:44.710 align:start position:0% engine testing and the head of an 01:58:44.710 --> 01:58:46.740 align:start position:0% engine testing and the head of an addition<01:58:45.070> doesn't<01:58:45.430> kind<01:58:45.610> of<01:58:45.760> fighting<01:58:46.630> with 01:58:46.740 --> 01:58:46.750 align:start position:0% addition doesn't kind of fighting with 01:58:46.750 --> 01:58:48.900 align:start position:0% addition doesn't kind of fighting with your<01:58:47.110> attention<01:58:47.560> terrific<01:58:48.160> troops<01:58:48.460> that 01:58:48.900 --> 01:58:48.910 align:start position:0% your attention terrific troops that 01:58:48.910 --> 01:58:53.010 align:start position:0% your attention terrific troops that you're<01:58:49.240> getting<01:58:49.390> the<01:58:49.570> right<01:58:49.600> headers<01:58:51.810> but<01:58:52.810> not 01:58:53.010 --> 01:58:53.020 align:start position:0% you're getting the right headers but not 01:58:53.020 --> 01:58:54.840 align:start position:0% you're getting the right headers but not least<01:58:53.260> this<01:58:53.740> is<01:58:53.920> something<01:58:54.220> that<01:58:54.250> because 01:58:54.840 --> 01:58:54.850 align:start position:0% least this is something that because 01:58:54.850 --> 01:58:57.210 align:start position:0% least this is something that because recently<01:58:55.150> the<01:58:55.570> m48<01:58:56.200> to<01:58:56.500> ensure<01:58:56.800> that<01:58:56.830> we<01:58:57.100> get 01:58:57.210 --> 01:58:57.220 align:start position:0% recently the m48 to ensure that we get 01:58:57.220 --> 01:58:58.950 align:start position:0% recently the m48 to ensure that we get like<01:58:57.460> a<01:58:57.670> good<01:58:58.000> operation<01:58:58.390> instead<01:58:58.810> of 01:58:58.950 --> 01:58:58.960 align:start position:0% like a good operation instead of 01:58:58.960 --> 01:59:04.260 align:start position:0% like a good operation instead of returning<01:58:59.170> a<01:58:59.350> favor<01:59:01.980> so<01:59:02.980> for<01:59:03.430> that<01:59:03.520> we<01:59:03.700> just 01:59:04.260 --> 01:59:04.270 align:start position:0% returning a favor so for that we just 01:59:04.270 --> 01:59:07.290 align:start position:0% returning a favor so for that we just choose<01:59:04.890> an<01:59:05.890> open<01:59:06.130> source<01:59:06.310> project<01:59:06.520> which<01:59:07.150> is 01:59:07.290 --> 01:59:07.300 align:start position:0% choose an open source project which is 01:59:07.300 --> 01:59:11.010 align:start position:0% choose an open source project which is also<01:59:07.450> complementing<01:59:08.170> back<01:59:08.320> tools<01:59:09.690> all<01:59:10.690> sorts 01:59:11.010 --> 01:59:11.020 align:start position:0% also complementing back tools all sorts 01:59:11.020 --> 01:59:14.460 align:start position:0% also complementing back tools all sorts of<01:59:11.110> data<01:59:11.290> extraction<01:59:11.680> and<01:59:12.630> analysis<01:59:13.630> so 01:59:14.460 --> 01:59:14.470 align:start position:0% of data extraction and analysis so 01:59:14.470 --> 01:59:17.340 align:start position:0% of data extraction and analysis so Genesis<01:59:14.860> allows<01:59:15.070> you<01:59:15.310> to<01:59:15.490> run<01:59:15.670> anybody<01:59:16.350> you 01:59:17.340 --> 01:59:17.350 align:start position:0% Genesis allows you to run anybody you 01:59:17.350 --> 01:59:19.080 align:start position:0% Genesis allows you to run anybody you know<01:59:17.530> agnostic<01:59:18.130> environment<01:59:18.640> where<01:59:18.820> you<01:59:18.910> can 01:59:19.080 --> 01:59:19.090 align:start position:0% know agnostic environment where you can 01:59:19.090 --> 01:59:21.570 align:start position:0% know agnostic environment where you can actually<01:59:19.360> control<01:59:19.870> every<01:59:20.500> aspect<01:59:20.650> of<01:59:21.220> your 01:59:21.570 --> 01:59:21.580 align:start position:0% actually control every aspect of your 01:59:21.580 --> 01:59:24.420 align:start position:0% actually control every aspect of your blood<01:59:21.970> chain<01:59:22.150> from<01:59:22.450> the<01:59:23.380> tiny<01:59:23.620> wants<01:59:24.070> to<01:59:24.310> have 01:59:24.420 --> 01:59:24.430 align:start position:0% blood chain from the tiny wants to have 01:59:24.430 --> 01:59:28.200 align:start position:0% blood chain from the tiny wants to have between<01:59:24.640> the<01:59:24.910> four<01:59:25.180> nodes<01:59:26.550> that<01:59:27.550> meet<01:59:27.760> you<01:59:28.060> can 01:59:28.200 --> 01:59:28.210 align:start position:0% between the four nodes that meet you can 01:59:28.210 --> 01:59:30.930 align:start position:0% between the four nodes that meet you can have<01:59:28.390> some<01:59:28.870> class<01:59:29.280> you<01:59:30.280> can<01:59:30.460> do<01:59:30.640> all 01:59:30.930 --> 01:59:30.940 align:start position:0% have some class you can do all 01:59:30.940 --> 01:59:33.420 align:start position:0% have some class you can do all sorts<01:59:31.180> of<01:59:31.240> tests<01:59:32.110> which<01:59:32.320> are<01:59:32.530> famous 01:59:33.420 --> 01:59:33.430 align:start position:0% sorts of tests which are famous 01:59:33.430 --> 01:59:36.540 align:start position:0% sorts of tests which are famous torturing<01:59:34.000> any<01:59:34.120> blocks<01:59:34.360> out<01:59:34.540> there<01:59:35.340> this<01:59:36.340> is<01:59:36.490> a 01:59:36.540 --> 01:59:36.550 align:start position:0% torturing any blocks out there this is a 01:59:36.550 --> 01:59:38.310 align:start position:0% torturing any blocks out there this is a great<01:59:36.700> doctor<01:59:37.000> chamber<01:59:37.480> it's<01:59:37.900> out<01:59:38.050> there<01:59:38.200> in 01:59:38.310 --> 01:59:38.320 align:start position:0% great doctor chamber it's out there in 01:59:38.320 --> 01:59:41.910 align:start position:0% great doctor chamber it's out there in the<01:59:38.710> web<01:59:38.860> you<01:59:39.490> feel<01:59:39.670> like 01:59:41.910 --> 01:59:41.920 align:start position:0% 01:59:41.920 --> 01:59:44.160 align:start position:0% and<01:59:42.250> on<01:59:42.790> top<01:59:42.940> of<01:59:43.000> that<01:59:43.120> so<01:59:43.390> we<01:59:43.570> plug<01:59:43.810> them<01:59:43.989> into 01:59:44.160 --> 01:59:44.170 align:start position:0% and on top of that so we plug them into 01:59:44.170 --> 01:59:46.800 align:start position:0% and on top of that so we plug them into our<01:59:44.620> platform<01:59:44.950> which<01:59:45.340> allows<01:59:45.810> authority 01:59:46.800 --> 01:59:46.810 align:start position:0% our platform which allows authority 01:59:46.810 --> 01:59:48.630 align:start position:0% our platform which allows authority comments<01:59:47.260> other<01:59:47.830> source<01:59:48.070> of<01:59:48.160> data<01:59:48.310> tends 01:59:48.630 --> 01:59:48.640 align:start position:0% comments other source of data tends 01:59:48.640 --> 01:59:50.760 align:start position:0% comments other source of data tends towards<01:59:48.970> his<01:59:49.180> feet<01:59:49.420> to<01:59:49.570> develop<01:59:49.900> chamber<01:59:50.350> you 01:59:50.760 --> 01:59:50.770 align:start position:0% towards his feet to develop chamber you 01:59:50.770 --> 01:59:53.700 align:start position:0% towards his feet to develop chamber you can<01:59:50.800> read<01:59:51.310> all<01:59:51.430> the<01:59:51.550> logs<01:59:51.730> of<01:59:52.540> data<01:59:52.750> make<01:59:53.440> sense 01:59:53.700 --> 01:59:53.710 align:start position:0% can read all the logs of data make sense 01:59:53.710 --> 01:59:55.560 align:start position:0% can read all the logs of data make sense of<01:59:53.860> it<01:59:54.010> if<01:59:54.640> they're<01:59:54.850> that<01:59:55.030> between<01:59:55.300> different 01:59:55.560 --> 01:59:55.570 align:start position:0% of it if they're that between different 01:59:55.570 --> 01:59:55.890 align:start position:0% of it if they're that between different runs 01:59:55.890 --> 01:59:55.900 align:start position:0% runs 01:59:55.900 --> 01:59:57.150 align:start position:0% runs we'll<01:59:56.050> have<01:59:56.170> that<01:59:56.260> between<01:59:56.530> blockchains 01:59:57.150 --> 01:59:57.160 align:start position:0% we'll have that between blockchains 01:59:57.160 --> 02:00:03.810 align:start position:0% we'll have that between blockchains pickles<01:59:58.210> solid<01:59:58.810> pencil<02:00:02.100> so<02:00:03.100> tuck<02:00:03.460> those<02:00:03.580> two 02:00:03.810 --> 02:00:03.820 align:start position:0% pickles solid pencil so tuck those two 02:00:03.820 --> 02:00:07.560 align:start position:0% pickles solid pencil so tuck those two sweets<02:00:04.650> we<02:00:05.650> start<02:00:05.950> very<02:00:06.010> small<02:00:06.640> we<02:00:07.210> just<02:00:07.420> want 02:00:07.560 --> 02:00:07.570 align:start position:0% sweets we start very small we just want 02:00:07.570 --> 02:00:09.270 align:start position:0% sweets we start very small we just want to<02:00:07.630> make<02:00:07.720> sure<02:00:07.750> you<02:00:08.260> know<02:00:08.350> works<02:00:08.739> just<02:00:09.040> on 02:00:09.270 --> 02:00:09.280 align:start position:0% to make sure you know works just on 02:00:09.280 --> 02:00:10.920 align:start position:0% to make sure you know works just on obstruct<02:00:09.940> justice<02:00:10.000> with<02:00:10.450> work<02:00:10.660> on<02:00:10.780> your 02:00:10.920 --> 02:00:10.930 align:start position:0% obstruct justice with work on your 02:00:10.930 --> 02:00:15.540 align:start position:0% obstruct justice with work on your machine<02:00:11.230> so<02:00:12.690> nice<02:00:13.690> and<02:00:13.930> even<02:00:14.170> then<02:00:14.830> start 02:00:15.540 --> 02:00:15.550 align:start position:0% machine so nice and even then start 02:00:15.550 --> 02:00:17.760 align:start position:0% machine so nice and even then start doing<02:00:15.760> it<02:00:15.880> for<02:00:16.030> testing<02:00:16.180> so<02:00:16.420> we<02:00:16.710> know<02:00:17.710> the 02:00:17.760 --> 02:00:17.770 align:start position:0% doing it for testing so we know the 02:00:17.770 --> 02:00:20.670 align:start position:0% doing it for testing so we know the parts<02:00:18.250> will<02:00:18.910> be<02:00:18.940> juice<02:00:19.270> event<02:00:19.600> we<02:00:19.720> we<02:00:20.290> make<02:00:20.470> you 02:00:20.670 --> 02:00:20.680 align:start position:0% parts will be juice event we we make you 02:00:20.680 --> 02:00:23.100 align:start position:0% parts will be juice event we we make you know<02:00:20.830> those<02:00:20.950> messages<02:00:21.250> CT<02:00:22.210> to<02:00:22.330> be<02:00:22.450> personality 02:00:23.100 --> 02:00:23.110 align:start position:0% know those messages CT to be personality 02:00:23.110 --> 02:00:25.110 align:start position:0% know those messages CT to be personality with<02:00:23.860> little<02:00:24.070> bit<02:00:24.190> of<02:00:24.220> that<02:00:24.430> testing<02:00:24.880> how<02:00:25.000> much 02:00:25.110 --> 02:00:25.120 align:start position:0% with little bit of that testing how much 02:00:25.120 --> 02:00:29.930 align:start position:0% with little bit of that testing how much tend<02:00:25.360> to<02:00:25.420> stick<02:00:25.690> to<02:00:25.810> stick<02:00:25.960> it<02:00:26.110> out 02:00:29.930 --> 02:00:29.940 align:start position:0% 02:00:29.940 --> 02:00:32.950 align:start position:0% we<02:00:30.810> do<02:00:30.930> some<02:00:31.110> opportunity<02:00:31.980> testing<02:00:32.340> so<02:00:32.550> it's 02:00:32.950 --> 02:00:32.960 align:start position:0% we do some opportunity testing so it's 02:00:32.960 --> 02:00:35.360 align:start position:0% we do some opportunity testing so it's getting<02:00:33.960> to<02:00:34.080> work<02:00:34.200> which<02:00:34.470> that<02:00:34.680> version<02:00:34.860> party 02:00:35.360 --> 02:00:35.370 align:start position:0% getting to work which that version party 02:00:35.370 --> 02:00:38.390 align:start position:0% getting to work which that version party I<02:00:35.580> was<02:00:36.060> indicating<02:00:36.270> exactly<02:00:36.990> the<02:00:37.080> same<02:00:37.260> way<02:00:37.410> we 02:00:38.390 --> 02:00:38.400 align:start position:0% I was indicating exactly the same way we 02:00:38.400 --> 02:00:39.890 align:start position:0% I was indicating exactly the same way we should<02:00:38.430> start<02:00:38.790> testing<02:00:39.300> all<02:00:39.420> the<02:00:39.510> UPS<02:00:39.690> codes 02:00:39.890 --> 02:00:39.900 align:start position:0% should start testing all the UPS codes 02:00:39.900 --> 02:00:43.010 align:start position:0% should start testing all the UPS codes did<02:00:40.170> we<02:00:40.290> see<02:00:40.500> that<02:00:40.620> the<02:00:40.770> extra<02:00:41.100> behavior<02:00:41.520> 77<02:00:42.360> we 02:00:43.010 --> 02:00:43.020 align:start position:0% did we see that the extra behavior 77 we 02:00:43.020 --> 02:00:44.540 align:start position:0% did we see that the extra behavior 77 we don't<02:00:43.170> have<02:00:43.290> a<02:00:43.320> refill<02:00:43.680> that's<02:00:43.920> negative<02:00:44.310> to 02:00:44.540 --> 02:00:44.550 align:start position:0% don't have a refill that's negative to 02:00:44.550 --> 02:00:46.860 align:start position:0% don't have a refill that's negative to the<02:00:44.640> positive<02:00:44.670> stuff<02:00:45.360> things 02:00:46.860 --> 02:00:46.870 align:start position:0% the positive stuff things 02:00:46.870 --> 02:00:48.419 align:start position:0% the positive stuff things you're<02:00:47.290> some<02:00:47.440> secret<02:00:47.890> testing<02:00:48.219> and<02:00:48.370> things 02:00:48.419 --> 02:00:48.429 align:start position:0% you're some secret testing and things 02:00:48.429 --> 02:00:50.220 align:start position:0% you're some secret testing and things someone<02:00:48.820> mentioned<02:00:49.150> earlier<02:00:49.270> keeps<02:00:49.929> attacked 02:00:50.220 --> 02:00:50.230 align:start position:0% someone mentioned earlier keeps attacked 02:00:50.230 --> 02:00:52.950 align:start position:0% someone mentioned earlier keeps attacked that's<02:00:50.940> bread<02:00:51.940> and<02:00:52.060> butter<02:00:52.239> for<02:00:52.449> us<02:00:52.540> we<02:00:52.840> like 02:00:52.950 --> 02:00:52.960 align:start position:0% that's bread and butter for us we like 02:00:52.960 --> 02:00:55.979 align:start position:0% that's bread and butter for us we like to<02:00:52.989> do<02:00:53.199> that<02:00:53.350> double<02:00:54.040> spins<02:00:54.630> between<02:00:55.630> two 02:00:55.979 --> 02:00:55.989 align:start position:0% to do that double spins between two 02:00:55.989 --> 02:00:57.540 align:start position:0% to do that double spins between two hijacks<02:00:56.440> and<02:00:56.590> those<02:00:56.739> I<02:00:56.949> mean<02:00:57.070> a<02:00:57.130> man<02:00:57.250> is<02:00:57.340> very 02:00:57.540 --> 02:00:57.550 align:start position:0% hijacks and those I mean a man is very 02:00:57.550 --> 02:01:01.169 align:start position:0% hijacks and those I mean a man is very bitter<02:00:57.880> things<02:00:59.520> little<02:01:00.520> testing<02:01:00.850> with<02:01:01.030> just 02:01:01.169 --> 02:01:01.179 align:start position:0% bitter things little testing with just 02:01:01.179 --> 02:01:03.990 align:start position:0% bitter things little testing with just one<02:01:01.600> milk<02:01:01.810> skin<02:01:02.110> to<02:01:02.230> get<02:01:02.380> completely<02:01:03.000> lost 02:01:03.990 --> 02:01:04.000 align:start position:0% one milk skin to get completely lost 02:01:04.000 --> 02:01:05.880 align:start position:0% one milk skin to get completely lost like<02:01:04.239> thousand<02:01:04.630> three<02:01:04.750> collections<02:01:04.960> a<02:01:05.320> second 02:01:05.880 --> 02:01:05.890 align:start position:0% like thousand three collections a second 02:01:05.890 --> 02:01:08.180 align:start position:0% like thousand three collections a second for<02:01:06.370> five<02:01:06.550> minutes<02:01:06.880> big<02:01:07.330> thing<02:01:07.600> even<02:01:07.929> night 02:01:08.180 --> 02:01:08.190 align:start position:0% for five minutes big thing even night 02:01:08.190 --> 02:01:10.320 align:start position:0% for five minutes big thing even night recovered<02:01:09.190> from<02:01:09.280> that<02:01:09.370> when<02:01:09.909> we<02:01:10.030> do<02:01:10.150> this 02:01:10.320 --> 02:01:10.330 align:start position:0% recovered from that when we do this 02:01:10.330 --> 02:01:12.270 align:start position:0% recovered from that when we do this bridge<02:01:10.570> testing<02:01:11.020> everybody<02:01:11.679> just<02:01:11.920> dispatched 02:01:12.270 --> 02:01:12.280 align:start position:0% bridge testing everybody just dispatched 02:01:12.280 --> 02:01:14.340 align:start position:0% bridge testing everybody just dispatched for<02:01:12.969> five<02:01:13.150> minutes<02:01:13.390> and<02:01:13.630> look<02:01:13.810> at<02:01:13.960> the<02:01:14.050> result 02:01:14.340 --> 02:01:14.350 align:start position:0% for five minutes and look at the result 02:01:14.350 --> 02:01:18.419 align:start position:0% for five minutes and look at the result of<02:01:14.500> the<02:01:14.620> the<02:01:15.400> damage<02:01:16.739> upon<02:01:17.739> such<02:01:17.920> testing<02:01:18.280> is 02:01:18.419 --> 02:01:18.429 align:start position:0% of the the damage upon such testing is 02:01:18.429 --> 02:01:20.010 align:start position:0% of the the damage upon such testing is like<02:01:18.550> we<02:01:18.699> do<02:01:18.850> at<02:01:18.969> all<02:01:19.270> we're<02:01:19.719> doing<02:01:19.900> this 02:01:20.010 --> 02:01:20.020 align:start position:0% like we do at all we're doing this 02:01:20.020 --> 02:01:23.419 align:start position:0% like we do at all we're doing this receive<02:01:20.350> to<02:01:20.530> talk<02:01:21.100> about<02:01:21.219> that<02:01:21.690> we'll<02:01:22.690> do 02:01:23.419 --> 02:01:23.429 align:start position:0% receive to talk about that we'll do 02:01:23.429 --> 02:01:26.910 align:start position:0% receive to talk about that we'll do testing<02:01:24.429> where<02:01:24.610> we'll<02:01:25.320> take<02:01:26.320> the<02:01:26.440> note<02:01:26.620> state 02:01:26.910 --> 02:01:26.920 align:start position:0% testing where we'll take the note state 02:01:26.920 --> 02:01:29.010 align:start position:0% testing where we'll take the note state will<02:01:27.460> get<02:01:27.640> your<02:01:27.850> point<02:01:28.060> to<02:01:28.300> transition<02:01:28.840> to<02:01:28.870> the 02:01:29.010 --> 02:01:29.020 align:start position:0% will get your point to transition to the 02:01:29.020 --> 02:01:30.510 align:start position:0% will get your point to transition to the next<02:01:29.230> block<02:01:29.530> and<02:01:29.860> we'll<02:01:30.010> make<02:01:30.159> sure<02:01:30.190> that's 02:01:30.510 --> 02:01:30.520 align:start position:0% next block and we'll make sure that's 02:01:30.520 --> 02:01:32.490 align:start position:0% next block and we'll make sure that's able<02:01:31.030> to<02:01:31.179> get<02:01:31.360> to<02:01:31.540> the<02:01:31.659> exact<02:01:31.960> same<02:01:32.080> result<02:01:32.409> is 02:01:32.490 --> 02:01:32.500 align:start position:0% able to get to the exact same result is 02:01:32.500 --> 02:01:35.040 align:start position:0% able to get to the exact same result is expected<02:01:32.949> as<02:01:33.730> long<02:01:33.880> as<02:01:33.969> we<02:01:34.090> can<02:01:34.270> determine<02:01:34.360> all 02:01:35.040 --> 02:01:35.050 align:start position:0% expected as long as we can determine all 02:01:35.050 --> 02:01:37.890 align:start position:0% expected as long as we can determine all the<02:01:35.380> stuff<02:01:35.650> that's<02:01:35.770> outside<02:01:36.010> of<02:01:36.659> like<02:01:37.659> the 02:01:37.890 --> 02:01:37.900 align:start position:0% the stuff that's outside of like the 02:01:37.900 --> 02:01:40.080 align:start position:0% the stuff that's outside of like the term<02:01:38.380> test<02:01:38.650> the<02:01:38.860> market<02:01:39.159> leaders<02:01:39.520> all<02:01:39.969> the 02:01:40.080 --> 02:01:40.090 align:start position:0% term test the market leaders all the 02:01:40.090 --> 02:01:48.060 align:start position:0% term test the market leaders all the space<02:01:40.330> we<02:01:40.600> can<02:01:40.810> actually<02:01:40.929> do<02:01:41.230> this<02:01:46.140> so<02:01:47.140> this 02:01:48.060 --> 02:01:48.070 align:start position:0% space we can actually do this so this 02:01:48.070 --> 02:01:49.950 align:start position:0% space we can actually do this so this kid<02:01:48.310> listen<02:01:48.670> gates<02:01:48.880> right<02:01:49.210> so<02:01:49.480> you're<02:01:49.929> a 02:01:49.950 --> 02:01:49.960 align:start position:0% kid listen gates right so you're a 02:01:49.960 --> 02:01:52.500 align:start position:0% kid listen gates right so you're a talker<02:01:50.380> you<02:01:50.590> want<02:01:50.920> to<02:01:51.159> use<02:01:51.340> some<02:01:52.090> level<02:01:52.449> of 02:01:52.500 --> 02:01:52.510 align:start position:0% talker you want to use some level of 02:01:52.510 --> 02:01:53.490 align:start position:0% talker you want to use some level of testing<02:01:52.840> to<02:01:52.989> make<02:01:53.110> sure<02:01:53.170> you're<02:01:53.380> both 02:01:53.490 --> 02:01:53.500 align:start position:0% testing to make sure you're both 02:01:53.500 --> 02:01:56.160 align:start position:0% testing to make sure you're both entering<02:01:53.890> work<02:01:54.540> we<02:01:55.540> can<02:01:55.690> give<02:01:55.840> you<02:01:55.960> a<02:01:55.989> month 02:01:56.160 --> 02:01:56.170 align:start position:0% entering work we can give you a month 02:01:56.170 --> 02:01:57.450 align:start position:0% entering work we can give you a month and<02:01:56.350> distant<02:01:56.710> you're<02:01:57.040> going<02:01:57.190> to<02:01:57.250> take<02:01:57.340> your 02:01:57.450 --> 02:01:57.460 align:start position:0% and distant you're going to take your 02:01:57.460 --> 02:02:01.919 align:start position:0% and distant you're going to take your fancy<02:01:57.909> words<02:01:59.699> now<02:02:00.699> you'd<02:02:01.480> like<02:02:01.510> to<02:02:01.750> make<02:02:01.900> sure 02:02:01.919 --> 02:02:01.929 align:start position:0% fancy words now you'd like to make sure 02:02:01.929 --> 02:02:03.720 align:start position:0% fancy words now you'd like to make sure that<02:02:02.050> actually<02:02:02.469> works<02:02:02.739> is<02:02:03.040> another<02:02:03.370> client 02:02:03.720 --> 02:02:03.730 align:start position:0% that actually works is another client 02:02:03.730 --> 02:02:05.490 align:start position:0% that actually works is another client that<02:02:03.790> you<02:02:03.969> don't<02:02:04.510> control<02:02:04.870> that<02:02:05.199> you<02:02:05.469> have 02:02:05.490 --> 02:02:05.500 align:start position:0% that you don't control that you have 02:02:05.500 --> 02:02:07.680 align:start position:0% that you don't control that you have Miller<02:02:05.860> hear<02:02:06.040> about<02:02:06.219> that's<02:02:07.210> a<02:02:07.330> big<02:02:07.480> step 02:02:07.680 --> 02:02:07.690 align:start position:0% Miller hear about that's a big step 02:02:07.690 --> 02:02:09.959 align:start position:0% Miller hear about that's a big step right<02:02:07.900> so<02:02:08.290> it<02:02:08.409> started<02:02:08.679> working<02:02:09.340> this<02:02:09.460> point 02:02:09.959 --> 02:02:09.969 align:start position:0% right so it started working this point 02:02:09.969 --> 02:02:11.399 align:start position:0% right so it started working this point intensities<02:02:10.630> you<02:02:10.840> don't<02:02:11.020> really<02:02:11.170> know<02:02:11.290> how 02:02:11.399 --> 02:02:11.409 align:start position:0% intensities you don't really know how 02:02:11.409 --> 02:02:13.350 align:start position:0% intensities you don't really know how they<02:02:11.500> work<02:02:11.710> Laxmi<02:02:12.640> sure<02:02:12.760> can't<02:02:12.969> write<02:02:13.150> lots 02:02:13.350 --> 02:02:13.360 align:start position:0% they work Laxmi sure can't write lots 02:02:13.360 --> 02:02:17.490 align:start position:0% they work Laxmi sure can't write lots the<02:02:13.510> right<02:02:13.690> time<02:02:14.730> now<02:02:15.810> you<02:02:16.810> can<02:02:16.960> also<02:02:17.170> try<02:02:17.440> this 02:02:17.490 --> 02:02:17.500 align:start position:0% the right time now you can also try this 02:02:17.500 --> 02:02:27.620 align:start position:0% the right time now you can also try this by<02:02:18.040> checking<02:02:18.610> the<02:02:18.880> new<02:02:19.000> version<02:02:19.360> of<02:02:19.390> the<02:02:19.929> time 02:02:27.620 --> 02:02:27.630 align:start position:0% 02:02:27.630 --> 02:02:30.870 align:start position:0% so<02:02:28.630> you<02:02:28.690> can<02:02:28.870> hear<02:02:29.409> is<02:02:29.560> it<02:02:29.710> outside<02:02:30.310> you<02:02:30.730> can 02:02:30.870 --> 02:02:30.880 align:start position:0% so you can hear is it outside you can 02:02:30.880 --> 02:02:32.490 align:start position:0% so you can hear is it outside you can start<02:02:31.330> doing<02:02:31.570> all<02:02:31.840> sorts<02:02:32.050> of<02:02:32.080> things<02:02:32.140> it 02:02:32.490 --> 02:02:32.500 align:start position:0% start doing all sorts of things it 02:02:32.500 --> 02:02:33.570 align:start position:0% start doing all sorts of things it becomes<02:02:32.800> interviewer 02:02:33.570 --> 02:02:33.580 align:start position:0% becomes interviewer 02:02:33.580 --> 02:02:38.520 align:start position:0% becomes interviewer privates<02:02:34.030> Roxton<02:02:34.480> and<02:02:36.780> applications<02:02:37.780> on<02:02:37.900> that 02:02:38.520 --> 02:02:38.530 align:start position:0% privates Roxton and applications on that 02:02:38.530 --> 02:02:39.959 align:start position:0% privates Roxton and applications on that you<02:02:38.800> reserve<02:02:39.100> to<02:02:39.250> your<02:02:39.370> stuff<02:02:39.550> so<02:02:39.670> you<02:02:39.790> think 02:02:39.959 --> 02:02:39.969 align:start position:0% you reserve to your stuff so you think 02:02:39.969 --> 02:02:42.720 align:start position:0% you reserve to your stuff so you think you<02:02:40.090> see<02:02:40.270> the<02:02:40.390> speaker<02:02:41.310> that<02:02:42.310> works<02:02:42.550> for<02:02:42.640> me 02:02:42.720 --> 02:02:42.730 align:start position:0% you see the speaker that works for me 02:02:42.730 --> 02:02:45.209 align:start position:0% you see the speaker that works for me well<02:02:42.909> iam<02:02:43.510> before<02:02:44.050> on<02:02:44.140> as<02:02:44.290> well 02:02:45.209 --> 02:02:45.219 align:start position:0% well iam before on as well 02:02:45.219 --> 02:02:47.370 align:start position:0% well iam before on as well holder<02:02:45.790> like<02:02:46.030> you<02:02:46.360> know<02:02:46.449> permission<02:02:46.989> networks 02:02:47.370 --> 02:02:47.380 align:start position:0% holder like you know permission networks 02:02:47.380 --> 02:02:56.010 align:start position:0% holder like you know permission networks much<02:02:47.860> more<02:02:48.070> fun<02:02:54.239> yeah<02:02:55.239> we<02:02:55.420> also<02:02:55.600> have<02:02:55.840> these 02:02:56.010 --> 02:02:56.020 align:start position:0% much more fun yeah we also have these 02:02:56.020 --> 02:02:58.350 align:start position:0% much more fun yeah we also have these stress<02:02:56.980> testing<02:02:57.400> like<02:02:57.699> once<02:02:58.060> a<02:02:58.179> week 02:02:58.350 --> 02:02:58.360 align:start position:0% stress testing like once a week 02:02:58.360 --> 02:03:00.240 align:start position:0% stress testing like once a week in<02:02:58.659> on<02:02:58.810> Saturday<02:02:59.230> to<02:02:59.290> just<02:02:59.590> deploy<02:02:59.860> your<02:03:00.100> feet 02:03:00.240 --> 02:03:00.250 align:start position:0% in on Saturday to just deploy your feet 02:03:00.250 --> 02:03:01.830 align:start position:0% in on Saturday to just deploy your feet and<02:03:00.429> then<02:03:00.580> do<02:03:00.760> your<02:03:01.090> smashing<02:03:01.510> it<02:03:01.630> work 02:03:01.830 --> 02:03:01.840 align:start position:0% and then do your smashing it work 02:03:01.840 --> 02:03:03.479 align:start position:0% and then do your smashing it work although<02:03:02.230> we<02:03:02.380> didn't<02:03:02.679> even<02:03:03.100> signal<02:03:03.250> to 02:03:03.479 --> 02:03:03.489 align:start position:0% although we didn't even signal to 02:03:03.489 --> 02:03:05.729 align:start position:0% although we didn't even signal to sustained<02:03:03.880> effort<02:03:04.690> and<02:03:05.199> you<02:03:05.320> can<02:03:05.469> compare 02:03:05.729 --> 02:03:05.739 align:start position:0% sustained effort and you can compare 02:03:05.739 --> 02:03:07.020 align:start position:0% sustained effort and you can compare results<02:03:05.889> with<02:03:06.250> time<02:03:06.400> to<02:03:06.580> make<02:03:06.699> sure<02:03:06.730> that 02:03:07.020 --> 02:03:07.030 align:start position:0% results with time to make sure that 02:03:07.030 --> 02:03:08.610 align:start position:0% results with time to make sure that you're<02:03:07.210> getting<02:03:07.300> better<02:03:07.600> performance<02:03:08.139> as<02:03:08.440> you 02:03:08.610 --> 02:03:08.620 align:start position:0% you're getting better performance as you 02:03:08.620 --> 02:03:12.479 align:start position:0% you're getting better performance as you please<02:03:09.870> so<02:03:10.870> just<02:03:11.080> couple<02:03:11.380> samples<02:03:11.860> for<02:03:12.310> what 02:03:12.479 --> 02:03:12.489 align:start position:0% please so just couple samples for what 02:03:12.489 --> 02:03:14.220 align:start position:0% please so just couple samples for what we<02:03:12.610> do<02:03:12.760> so<02:03:13.000> we<02:03:13.030> do<02:03:13.210> let<02:03:13.360> them<02:03:13.480> see<02:03:13.600> testing<02:03:13.960> very 02:03:14.220 --> 02:03:14.230 align:start position:0% we do so we do let them see testing very 02:03:14.230 --> 02:03:17.310 align:start position:0% we do so we do let them see testing very easily<02:03:14.320> that's<02:03:14.710> monitoring<02:03:15.310> these<02:03:15.880> tests<02:03:16.389> we 02:03:17.310 --> 02:03:17.320 align:start position:0% easily that's monitoring these tests we 02:03:17.320 --> 02:03:19.020 align:start position:0% easily that's monitoring these tests we take<02:03:17.530> your<02:03:17.650> network<02:03:18.010> you<02:03:18.159> start<02:03:18.400> pushing<02:03:18.670> the 02:03:19.020 --> 02:03:19.030 align:start position:0% take your network you start pushing the 02:03:19.030 --> 02:03:20.919 align:start position:0% take your network you start pushing the notes<02:03:19.239> apart<02:03:19.630> and<02:03:19.929> seeing<02:03:20.260> this 02:03:20.919 --> 02:03:20.929 align:start position:0% notes apart and seeing this 02:03:20.929 --> 02:03:23.890 align:start position:0% notes apart and seeing this to<02:03:21.110> communicate<02:03:21.530> we<02:03:22.489> can<02:03:22.640> even<02:03:22.850> like<02:03:23.300> do<02:03:23.690> some 02:03:23.890 --> 02:03:23.900 align:start position:0% to communicate we can even like do some 02:03:23.900 --> 02:03:25.660 align:start position:0% to communicate we can even like do some geographical<02:03:24.469> replication<02:03:24.980> so<02:03:25.190> if<02:03:25.400> you<02:03:25.520> had<02:03:25.640> a 02:03:25.660 --> 02:03:25.670 align:start position:0% geographical replication so if you had a 02:03:25.670 --> 02:03:27.430 align:start position:0% geographical replication so if you had a note<02:03:25.909> in<02:03:26.239> New<02:03:26.360> York<02:03:26.600> in<02:03:26.780> a<02:03:26.870> building<02:03:27.140> talk<02:03:27.320> to 02:03:27.430 --> 02:03:27.440 align:start position:0% note in New York in a building talk to 02:03:27.440 --> 02:03:29.709 align:start position:0% note in New York in a building talk to you<02:03:27.530> know<02:03:28.280> here's<02:03:28.670> an<02:03:28.820> identity<02:03:29.179> we<02:03:29.330> get<02:03:29.480> into 02:03:29.709 --> 02:03:29.719 align:start position:0% you know here's an identity we get into 02:03:29.719 --> 02:03:31.360 align:start position:0% you know here's an identity we get into those<02:03:29.929> two<02:03:30.080> locations<02:03:30.590> immediately<02:03:31.190> make 02:03:31.360 --> 02:03:31.370 align:start position:0% those two locations immediately make 02:03:31.370 --> 02:03:32.560 align:start position:0% those two locations immediately make sure<02:03:31.520> it<02:03:31.610> is<02:03:31.699> syllable<02:03:32.060> to<02:03:32.150> communicate 02:03:32.560 --> 02:03:32.570 align:start position:0% sure it is syllable to communicate 02:03:32.570 --> 02:03:36.250 align:start position:0% sure it is syllable to communicate properly<02:03:32.780> under<02:03:33.679> something<02:03:33.920> but<02:03:34.190> fine 02:03:36.250 --> 02:03:36.260 align:start position:0% properly under something but fine 02:03:36.260 --> 02:03:39.700 align:start position:0% properly under something but fine we<02:03:37.040> have<02:03:37.219> also<02:03:38.020> started<02:03:39.020> my<02:03:39.199> favorite<02:03:39.530> this 02:03:39.700 --> 02:03:39.710 align:start position:0% we have also started my favorite this 02:03:39.710 --> 02:03:42.459 align:start position:0% we have also started my favorite this one<02:03:39.830> we<02:03:40.610> take<02:03:40.820> a<02:03:41.060> nice<02:03:41.390> definite<02:03:41.840> we're<02:03:42.260> ready 02:03:42.459 --> 02:03:42.469 align:start position:0% one we take a nice definite we're ready 02:03:42.469 --> 02:03:44.919 align:start position:0% one we take a nice definite we're ready to<02:03:42.650> to<02:03:42.890> wait<02:03:43.610> five<02:03:43.820> minutes<02:03:44.000> bring<02:03:44.750> them 02:03:44.919 --> 02:03:44.929 align:start position:0% to to wait five minutes bring them 02:03:44.929 --> 02:03:47.020 align:start position:0% to to wait five minutes bring them together<02:03:45.110> so<02:03:45.980> what<02:03:46.460> are<02:03:46.520> we<02:03:46.610> going<02:03:46.760> to<02:03:46.820> see 02:03:47.020 --> 02:03:47.030 align:start position:0% together so what are we going to see 02:03:47.030 --> 02:03:48.850 align:start position:0% together so what are we going to see some<02:03:47.239> networks<02:03:47.630> some<02:03:48.050> protocol<02:03:48.409> will<02:03:48.590> be<02:03:48.710> able 02:03:48.850 --> 02:03:48.860 align:start position:0% some networks some protocol will be able 02:03:48.860 --> 02:03:51.220 align:start position:0% some networks some protocol will be able to<02:03:49.010> know<02:03:49.130> how<02:03:49.159> to<02:03:49.310> consensus<02:03:50.000> for<02:03:50.270> example<02:03:50.690> for 02:03:51.220 --> 02:03:51.230 align:start position:0% to know how to consensus for example for 02:03:51.230 --> 02:03:53.260 align:start position:0% to know how to consensus for example for the<02:03:51.290> five<02:03:51.440> minutes<02:03:51.770> because<02:03:52.100> they<02:03:52.429> come<02:03:52.699> get 02:03:53.260 --> 02:03:53.270 align:start position:0% the five minutes because they come get 02:03:53.270 --> 02:03:55.450 align:start position:0% the five minutes because they come get to<02:03:53.420> consistently<02:03:53.960> one<02:03:54.110> but<02:03:54.890> if<02:03:55.159> you<02:03:55.250> have<02:03:55.340> to 02:03:55.450 --> 02:03:55.460 align:start position:0% to consistently one but if you have to 02:03:55.460 --> 02:03:56.950 align:start position:0% to consistently one but if you have to work<02:03:55.790> for<02:03:55.969> example<02:03:56.330> you<02:03:56.390> start<02:03:56.600> having<02:03:56.719> to 02:03:56.950 --> 02:03:56.960 align:start position:0% work for example you start having to 02:03:56.960 --> 02:03:59.200 align:start position:0% work for example you start having to change<02:03:57.199> the<02:03:57.590> content<02:03:57.770> of<02:03:57.980> each<02:03:58.070> other<02:03:58.280> now<02:03:59.120> if 02:03:59.200 --> 02:03:59.210 align:start position:0% change the content of each other now if 02:03:59.210 --> 02:04:00.880 align:start position:0% change the content of each other now if you<02:03:59.330> bring<02:03:59.449> them<02:03:59.659> back<02:03:59.719> together<02:03:59.989> the 02:04:00.880 --> 02:04:00.890 align:start position:0% you bring them back together the 02:04:00.890 --> 02:04:02.439 align:start position:0% you bring them back together the beginning<02:04:01.219> you<02:04:01.460> have<02:04:01.670> to<02:04:01.909> give<02:04:02.060> them<02:04:02.210> some 02:04:02.439 --> 02:04:02.449 align:start position:0% beginning you have to give them some 02:04:02.449 --> 02:04:04.419 align:start position:0% beginning you have to give them some time<02:04:02.630> and<02:04:02.810> eventually<02:04:03.260> into<02:04:03.590> some<02:04:03.679> consensus 02:04:04.419 --> 02:04:04.429 align:start position:0% time and eventually into some consensus 02:04:04.429 --> 02:04:08.500 align:start position:0% time and eventually into some consensus reach<02:04:04.699> back<02:04:06.400> some<02:04:07.400> margins<02:04:08.150> don't<02:04:08.360> actually 02:04:08.500 --> 02:04:08.510 align:start position:0% reach back some margins don't actually 02:04:08.510 --> 02:04:10.550 align:start position:0% reach back some margins don't actually support<02:04:08.750> that<02:04:09.080> paper 02:04:10.550 --> 02:04:10.560 align:start position:0% support that paper 02:04:10.560 --> 02:04:12.440 align:start position:0% support that paper and<02:04:10.890> this<02:04:11.100> is<02:04:11.250> what<02:04:11.580> you've<02:04:11.700> done<02:04:11.850> recently<02:04:12.090> to 02:04:12.440 --> 02:04:12.450 align:start position:0% and this is what you've done recently to 02:04:12.450 --> 02:04:15.470 align:start position:0% and this is what you've done recently to interrupt<02:04:12.950> so<02:04:13.950> big<02:04:14.550> seven<02:04:14.880> different<02:04:14.970> clients 02:04:15.470 --> 02:04:15.480 align:start position:0% interrupt so big seven different clients 02:04:15.480 --> 02:04:18.710 align:start position:0% interrupt so big seven different clients then<02:04:16.350> a<02:04:16.890> farmer<02:04:17.400> of<02:04:17.460> your<02:04:17.580> soup<02:04:17.910> of<02:04:18.300> a<02:04:18.390> destined 02:04:18.710 --> 02:04:18.720 align:start position:0% then a farmer of your soup of a destined 02:04:18.720 --> 02:04:20.300 align:start position:0% then a farmer of your soup of a destined end<02:04:18.840> and<02:04:19.080> make<02:04:19.530> sure<02:04:19.650> is<02:04:19.710> able<02:04:19.980> to<02:04:20.070> come<02:04:20.220> to 02:04:20.300 --> 02:04:20.310 align:start position:0% end and make sure is able to come to 02:04:20.310 --> 02:04:22.190 align:start position:0% end and make sure is able to come to consensus<02:04:20.850> right<02:04:21.300> so<02:04:21.570> he's<02:04:21.750> innocent<02:04:21.960> of 02:04:22.190 --> 02:04:22.200 align:start position:0% consensus right so he's innocent of 02:04:22.200 --> 02:04:24.080 align:start position:0% consensus right so he's innocent of figuration<02:04:22.710> files<02:04:22.950> knowing<02:04:23.880> about<02:04:23.970> each 02:04:24.080 --> 02:04:24.090 align:start position:0% figuration files knowing about each 02:04:24.090 --> 02:04:24.650 align:start position:0% figuration files knowing about each other 02:04:24.650 --> 02:04:24.660 align:start position:0% other 02:04:24.660 --> 02:04:26.870 align:start position:0% other this<02:04:25.050> is<02:04:25.230> had<02:04:25.380> fun<02:04:26.040> a<02:04:26.070> bit<02:04:26.190> of<02:04:26.310> a<02:04:26.400> challenge<02:04:26.580> of 02:04:26.870 --> 02:04:26.880 align:start position:0% this is had fun a bit of a challenge of 02:04:26.880 --> 02:04:28.040 align:start position:0% this is had fun a bit of a challenge of the<02:04:26.970> column<02:04:27.270> where<02:04:27.420> they<02:04:27.540> need<02:04:27.690> to<02:04:27.810> credit 02:04:28.040 --> 02:04:28.050 align:start position:0% the column where they need to credit 02:04:28.050 --> 02:04:30.290 align:start position:0% the column where they need to credit date<02:04:28.290> sometime<02:04:28.710> get<02:04:29.010> the<02:04:29.100> right<02:04:29.250> blogs<02:04:29.550> or 02:04:30.290 --> 02:04:30.300 align:start position:0% date sometime get the right blogs or 02:04:30.300 --> 02:04:32.150 align:start position:0% date sometime get the right blogs or post<02:04:30.540> boxes<02:04:30.840> right<02:04:31.320> it's<02:04:31.530> a<02:04:31.620> dining<02:04:32.040> with 02:04:32.150 --> 02:04:32.160 align:start position:0% post boxes right it's a dining with 02:04:32.160 --> 02:04:35.000 align:start position:0% post boxes right it's a dining with those<02:04:32.310> things<02:04:32.930> and<02:04:33.930> this<02:04:34.440> is<02:04:34.620> something<02:04:34.890> we 02:04:35.000 --> 02:04:35.010 align:start position:0% those things and this is something we 02:04:35.010 --> 02:04:37.280 align:start position:0% those things and this is something we need<02:04:35.130> for<02:04:35.370> for<02:04:35.700> find<02:04:35.910> where<02:04:36.210> they<02:04:36.930> wanted<02:04:37.200> to 02:04:37.280 --> 02:04:37.290 align:start position:0% need for for find where they wanted to 02:04:37.290 --> 02:04:39.230 align:start position:0% need for for find where they wanted to distant<02:04:37.590> name<02:04:37.740> key<02:04:37.920> and<02:04:38.130> then<02:04:38.550> we<02:04:38.640> test<02:04:39.000> it<02:04:39.120> in 02:04:39.230 --> 02:04:39.240 align:start position:0% distant name key and then we test it in 02:04:39.240 --> 02:04:41.210 align:start position:0% distant name key and then we test it in the<02:04:39.300> safe<02:04:39.570> manner<02:04:39.990> so<02:04:40.680> that<02:04:40.830> you<02:04:40.950> could<02:04:41.130> get 02:04:41.210 --> 02:04:41.220 align:start position:0% the safe manner so that you could get 02:04:41.220 --> 02:04:43.700 align:start position:0% the safe manner so that you could get four<02:04:41.580> digit<02:04:41.910> results<02:04:42.330> that<02:04:42.930> there<02:04:43.320> if<02:04:43.470> he 02:04:43.700 --> 02:04:43.710 align:start position:0% four digit results that there if he 02:04:43.710 --> 02:04:45.470 align:start position:0% four digit results that there if he wasn't<02:04:43.980> week<02:04:44.100> to<02:04:44.250> break<02:04:44.400> the<02:04:44.640> maintenance<02:04:45.090> so 02:04:45.470 --> 02:04:45.480 align:start position:0% wasn't week to break the maintenance so 02:04:45.480 --> 02:04:52.730 align:start position:0% wasn't week to break the maintenance so we<02:04:45.930> to<02:04:46.110> domain<02:04:46.470> that<02:04:51.020> we<02:04:52.020> change<02:04:52.290> the<02:04:52.380> plan<02:04:52.560> to 02:04:52.730 --> 02:04:52.740 align:start position:0% we to domain that we change the plan to 02:04:52.740 --> 02:04:54.200 align:start position:0% we to domain that we change the plan to be<02:04:52.830> so<02:04:52.980> slightly<02:04:53.220> to<02:04:53.550> allow<02:04:53.640> larger 02:04:54.200 --> 02:04:54.210 align:start position:0% be so slightly to allow larger 02:04:54.210 --> 02:04:58.340 align:start position:0% be so slightly to allow larger collections<02:04:54.720> and<02:04:55.640> that<02:04:56.640> gave<02:04:57.210> us<02:04:57.420> the<02:04:57.720> actual 02:04:58.340 --> 02:04:58.350 align:start position:0% collections and that gave us the actual 02:04:58.350 --> 02:05:00.080 align:start position:0% collections and that gave us the actual results<02:04:59.040> in<02:04:59.160> terms<02:04:59.340> of<02:04:59.430> analytics<02:04:59.640> and<02:04:59.970> we 02:05:00.080 --> 02:05:00.090 align:start position:0% results in terms of analytics and we 02:05:00.090 --> 02:05:01.940 align:start position:0% results in terms of analytics and we could<02:05:00.240> see<02:05:00.390> the<02:05:00.660> uncle<02:05:01.020> rate<02:05:01.140> was<02:05:01.410> breathing 02:05:01.940 --> 02:05:01.950 align:start position:0% could see the uncle rate was breathing 02:05:01.950 --> 02:05:06.810 align:start position:0% could see the uncle rate was breathing good<02:05:02.160> of<02:05:02.310> that<02:05:02.340> material<02:05:02.910> to<02:05:03.510> system 02:05:06.810 --> 02:05:06.820 align:start position:0% 02:05:06.820 --> 02:05:10.110 align:start position:0% he<02:05:06.910> pushes<02:05:08.190> what<02:05:09.190> sort<02:05:09.370> of<02:05:09.430> scale<02:05:09.730> you<02:05:09.970> guys 02:05:10.110 --> 02:05:10.120 align:start position:0% he pushes what sort of scale you guys 02:05:10.120 --> 02:05:16.350 align:start position:0% he pushes what sort of scale you guys that<02:05:10.590> tests<02:05:14.400> soul<02:05:15.400> artists<02:05:15.850> are<02:05:15.910> reproducible 02:05:16.350 --> 02:05:16.360 align:start position:0% that tests soul artists are reproducible 02:05:16.360 --> 02:05:19.110 align:start position:0% that tests soul artists are reproducible that's<02:05:16.660> enough<02:05:17.140> yeah<02:05:17.830> we<02:05:18.250> run<02:05:18.490> this<02:05:18.670> interview 02:05:19.110 --> 02:05:19.120 align:start position:0% that's enough yeah we run this interview 02:05:19.120 --> 02:05:20.580 align:start position:0% that's enough yeah we run this interview and<02:05:19.270> then<02:05:19.360> close<02:05:19.540> the<02:05:19.690> ramen<02:05:20.020> so<02:05:20.200> we<02:05:20.320> can<02:05:20.470> make 02:05:20.580 --> 02:05:20.590 align:start position:0% and then close the ramen so we can make 02:05:20.590 --> 02:05:21.900 align:start position:0% and then close the ramen so we can make sure<02:05:20.620> that<02:05:20.770> you<02:05:21.010> get<02:05:21.130> the<02:05:21.280> same<02:05:21.460> results<02:05:21.820> at<02:05:21.880> a 02:05:21.900 --> 02:05:21.910 align:start position:0% sure that you get the same results at a 02:05:21.910 --> 02:05:24.210 align:start position:0% sure that you get the same results at a time<02:05:22.120> we<02:05:22.690> can<02:05:22.840> do<02:05:23.020> up<02:05:23.290> to<02:05:23.320> 100<02:05:23.740> notes<02:05:23.920> right<02:05:24.100> now 02:05:24.210 --> 02:05:24.220 align:start position:0% time we can do up to 100 notes right now 02:05:24.220 --> 02:05:26.760 align:start position:0% time we can do up to 100 notes right now we're<02:05:24.880> trying<02:05:25.090> to<02:05:25.270> go<02:05:25.390> much<02:05:25.900> bigger<02:05:26.140> but 02:05:26.760 --> 02:05:26.770 align:start position:0% we're trying to go much bigger but 02:05:26.770 --> 02:05:28.320 align:start position:0% we're trying to go much bigger but frankly<02:05:27.220> what<02:05:27.400> I've<02:05:27.520> seen<02:05:27.640> in<02:05:27.760> that<02:05:27.880> 30<02:05:28.090> notes 02:05:28.320 --> 02:05:28.330 align:start position:0% frankly what I've seen in that 30 notes 02:05:28.330 --> 02:05:30.090 align:start position:0% frankly what I've seen in that 30 notes I<02:05:28.630> already<02:05:29.050> know<02:05:29.170> that<02:05:29.200> you<02:05:29.560> can<02:05:29.680> really<02:05:29.890> mess 02:05:30.090 --> 02:05:30.100 align:start position:0% I already know that you can really mess 02:05:30.100 --> 02:05:35.880 align:start position:0% I already know that you can really mess with<02:05:30.370> my<02:05:30.430> stuff<02:05:30.490> so<02:05:33.510> I<02:05:34.510> was<02:05:34.810> wondering<02:05:35.260> can<02:05:35.800> you 02:05:35.880 --> 02:05:35.890 align:start position:0% with my stuff so I was wondering can you 02:05:35.890 --> 02:05:48.630 align:start position:0% with my stuff so I was wondering can you do<02:05:36.700> some<02:05:36.940> tests<02:05:37.180> on<02:05:37.390> we<02:05:38.260> cannot<02:05:38.500> look<02:05:38.650> like<02:05:47.640> yes 02:05:48.630 --> 02:05:48.640 align:start position:0% do some tests on we cannot look like yes 02:05:48.640 --> 02:05:50.460 align:start position:0% do some tests on we cannot look like yes so<02:05:48.760> we<02:05:48.850> can<02:05:48.880> really<02:05:49.240> it's<02:05:49.690> really<02:05:49.870> very<02:05:50.290> much 02:05:50.460 --> 02:05:50.470 align:start position:0% so we can really it's really very much 02:05:50.470 --> 02:05:52.080 align:start position:0% so we can really it's really very much for<02:05:50.680> picketing<02:05:50.980> and<02:05:51.220> running<02:05:51.460> that<02:05:51.670> completes 02:05:52.080 --> 02:05:52.090 align:start position:0% for picketing and running that completes 02:05:52.090 --> 02:05:54.210 align:start position:0% for picketing and running that completes doesn't<02:05:52.780> it<02:05:52.870> so<02:05:53.380> you<02:05:53.440> thinking<02:05:53.800> very<02:05:54.130> much 02:05:54.210 --> 02:05:54.220 align:start position:0% doesn't it so you thinking very much 02:05:54.220 --> 02:05:57.000 align:start position:0% doesn't it so you thinking very much employs<02:05:54.700> contracts<02:05:55.420> on<02:05:55.570> it<02:05:55.720> we<02:05:56.620> have<02:05:56.800> some 02:05:57.000 --> 02:05:57.010 align:start position:0% employs contracts on it we have some 02:05:57.010 --> 02:05:58.470 align:start position:0% employs contracts on it we have some test<02:05:57.220> that<02:05:57.370> involves<02:05:57.610> my<02:05:57.910> contracts<02:05:58.330> we 02:05:58.470 --> 02:05:58.480 align:start position:0% test that involves my contracts we 02:05:58.480 --> 02:06:01.920 align:start position:0% test that involves my contracts we collectively<02:05:58.960> try<02:05:59.320> to<02:05:59.380> reduce<02:05:59.710> them<02:06:00.270> even<02:06:01.270> use 02:06:01.920 --> 02:06:01.930 align:start position:0% collectively try to reduce them even use 02:06:01.930 --> 02:06:04.440 align:start position:0% collectively try to reduce them even use the<02:06:02.260> infrastructure<02:06:02.890> elements<02:06:03.130> that<02:06:04.120> are 02:06:04.440 --> 02:06:04.450 align:start position:0% the infrastructure elements that are 02:06:04.450 --> 02:06:06.300 align:start position:0% the infrastructure elements that are injured<02:06:04.690> article<02:06:05.080> which<02:06:05.590> we<02:06:05.830> will<02:06:05.920> be<02:06:06.040> able<02:06:06.130> to 02:06:06.300 --> 02:06:06.310 align:start position:0% injured article which we will be able to 02:06:06.310 --> 02:06:08.850 align:start position:0% injured article which we will be able to run<02:06:06.400> to<02:06:06.640> test<02:06:06.850> destitute<02:06:07.600> certain<02:06:07.990> breach<02:06:08.200> and 02:06:08.850 --> 02:06:08.860 align:start position:0% run to test destitute certain breach and 02:06:08.860 --> 02:06:10.650 align:start position:0% run to test destitute certain breach and then<02:06:09.100> we<02:06:09.160> can<02:06:09.310> actually<02:06:09.430> do<02:06:09.910> also<02:06:10.210> saw<02:06:10.360> flight 02:06:10.650 --> 02:06:10.660 align:start position:0% then we can actually do also saw flight 02:06:10.660 --> 02:06:13.320 align:start position:0% then we can actually do also saw flight but<02:06:11.050> it's<02:06:11.170> just<02:06:11.260> easier<02:06:11.770> to<02:06:11.920> see<02:06:12.330> full 02:06:13.320 --> 02:06:13.330 align:start position:0% but it's just easier to see full 02:06:13.330 --> 02:06:17.360 align:start position:0% but it's just easier to see full coverage<02:06:13.660> intercept 02:06:17.360 --> 02:06:17.370 align:start position:0% 02:06:17.370 --> 02:06:20.520 align:start position:0% we're<02:06:18.370> Network<02:06:18.640> dinners<02:06:18.940> so<02:06:19.360> we<02:06:19.960> always<02:06:20.230> end 02:06:20.520 --> 02:06:20.530 align:start position:0% we're Network dinners so we always end 02:06:20.530 --> 02:06:23.490 align:start position:0% we're Network dinners so we always end up<02:06:20.620> like<02:06:20.830> me<02:06:20.980> back<02:06:21.219> down<02:06:21.460> the<02:06:22.500> powerful 02:06:23.490 --> 02:06:23.500 align:start position:0% up like me back down the powerful 02:06:23.500 --> 02:06:26.550 align:start position:0% up like me back down the powerful Network<02:06:24.250> first<02:06:24.550> and<02:06:25.060> we're<02:06:25.270> doing<02:06:25.570> yes<02:06:25.960> do<02:06:26.469> you 02:06:26.550 --> 02:06:26.560 align:start position:0% Network first and we're doing yes do you 02:06:26.560 --> 02:06:30.090 align:start position:0% Network first and we're doing yes do you have<02:06:26.710> like<02:06:26.980> I<02:06:28.050> don't<02:06:29.050> know<02:06:29.440> we<02:06:29.560> wait<02:06:29.739> for<02:06:29.890> about 02:06:30.090 --> 02:06:30.100 align:start position:0% have like I don't know we wait for about 02:06:30.100 --> 02:06:33.180 align:start position:0% have like I don't know we wait for about that<02:06:30.219> success<02:06:30.790> I<02:06:31.000> just<02:06:31.180> think<02:06:31.540> like<02:06:31.630> I<02:06:32.130> go<02:06:33.130> to 02:06:33.180 --> 02:06:33.190 align:start position:0% that success I just think like I go to 02:06:33.190 --> 02:06:35.850 align:start position:0% that success I just think like I go to your<02:06:33.460> blog<02:06:33.730> and<02:06:33.790> then<02:06:34.120> I<02:06:34.270> like<02:06:34.480> I<02:06:34.510> have<02:06:34.860> very 02:06:35.850 --> 02:06:35.860 align:start position:0% your blog and then I like I have very 02:06:35.860 --> 02:06:38.000 align:start position:0% your blog and then I like I have very some<02:06:36.040> of<02:06:36.160> my<02:06:36.340> things<02:06:36.850> with<02:06:37.120> like<02:06:37.330> started 02:06:38.000 --> 02:06:38.010 align:start position:0% some of my things with like started 02:06:38.010 --> 02:06:39.630 align:start position:0% some of my things with like started coming<02:06:39.010> around 02:06:39.630 --> 02:06:39.640 align:start position:0% coming around 02:06:39.640 --> 02:06:41.550 align:start position:0% coming around that's<02:06:39.880> different<02:06:40.090> becoming<02:06:40.540> so<02:06:40.780> yeah<02:06:41.530> I 02:06:41.550 --> 02:06:41.560 align:start position:0% that's different becoming so yeah I 02:06:41.560 --> 02:06:43.440 align:start position:0% that's different becoming so yeah I would<02:06:42.400> like<02:06:42.550> to<02:06:42.580> be<02:06:42.790> able<02:06:42.850> to<02:06:43.030> have<02:06:43.239> public 02:06:43.440 --> 02:06:43.450 align:start position:0% would like to be able to have public 02:06:43.450 --> 02:06:46.380 align:start position:0% would like to be able to have public datasets<02:06:43.860> so<02:06:44.860> not<02:06:45.040> just<02:06:45.219> results<02:06:45.730> right<02:06:46.150> the 02:06:46.380 --> 02:06:46.390 align:start position:0% datasets so not just results right the 02:06:46.390 --> 02:06:48.360 align:start position:0% datasets so not just results right the lecture<02:06:46.690> giving<02:06:47.050> you<02:06:47.140> the<02:06:47.590> whole<02:06:47.800> data<02:06:48.070> set<02:06:48.219> of 02:06:48.360 --> 02:06:48.370 align:start position:0% lecture giving you the whole data set of 02:06:48.370 --> 02:06:50.520 align:start position:0% lecture giving you the whole data set of everything<02:06:48.760> going<02:06:48.880> on<02:06:49.210> about<02:06:49.540> investment<02:06:50.170> and 02:06:50.520 --> 02:06:50.530 align:start position:0% everything going on about investment and 02:06:50.530 --> 02:06:52.950 align:start position:0% everything going on about investment and make<02:06:50.890> that<02:06:51.070> public<02:06:51.250> visibility<02:06:52.180> to<02:06:52.600> our<02:06:52.660> users 02:06:52.950 --> 02:06:52.960 align:start position:0% make that public visibility to our users 02:06:52.960 --> 02:06:55.170 align:start position:0% make that public visibility to our users to<02:06:52.989> the<02:06:53.380> public<02:06:53.710> platforms<02:06:54.370> people<02:06:54.820> down<02:06:55.030> low 02:06:55.170 --> 02:06:55.180 align:start position:0% to the public platforms people down low 02:06:55.180 --> 02:06:59.130 align:start position:0% to the public platforms people down low like<02:06:55.450> 1.5<02:06:56.320> gigabytes<02:06:56.830> of<02:06:56.920> blogs<02:06:57.160> and<02:06:58.140> number 02:06:59.130 --> 02:06:59.140 align:start position:0% like 1.5 gigabytes of blogs and number 02:06:59.140 --> 02:07:06.420 align:start position:0% like 1.5 gigabytes of blogs and number crunching<02:07:03.900> even<02:07:04.900> like<02:07:05.410> you<02:07:05.860> don't<02:07:06.040> work<02:07:06.190> press 02:07:06.420 --> 02:07:06.430 align:start position:0% crunching even like you don't work press 02:07:06.430 --> 02:07:10.229 align:start position:0% crunching even like you don't work press this<02:07:07.320> to<02:07:08.320> do<02:07:08.410> blood<02:07:08.560> testing<02:07:08.890> in<02:07:09.120> tomorrow<02:07:10.120> so 02:07:10.229 --> 02:07:10.239 align:start position:0% this to do blood testing in tomorrow so 02:07:10.239 --> 02:07:14.070 align:start position:0% this to do blood testing in tomorrow so I<02:07:10.930> do<02:07:11.350> know<02:07:11.760> what<02:07:12.760> the<02:07:12.820> doctor<02:07:13.180> ordered<02:07:13.540> back 02:07:14.070 --> 02:07:14.080 align:start position:0% I do know what the doctor ordered back 02:07:14.080 --> 02:07:19.080 align:start position:0% I do know what the doctor ordered back to<02:07:14.140> dysfunction<02:07:16.650> days<02:07:17.650> where<02:07:18.370> we<02:07:18.610> spent<02:07:18.940> quite 02:07:19.080 --> 02:07:19.090 align:start position:0% to dysfunction days where we spent quite 02:07:19.090 --> 02:07:20.310 align:start position:0% to dysfunction days where we spent quite a<02:07:19.150> bit<02:07:19.180> of<02:07:19.360> time<02:07:19.570> actually<02:07:19.719> we<02:07:19.989> do<02:07:20.080> a<02:07:20.110> lot<02:07:20.290> of 02:07:20.310 --> 02:07:20.320 align:start position:0% a bit of time actually we do a lot of 02:07:20.320 --> 02:07:22.440 align:start position:0% a bit of time actually we do a lot of discoveries<02:07:20.890> of<02:07:21.040> clients<02:07:21.370> because<02:07:21.940> it's<02:07:22.360> a 02:07:22.440 --> 02:07:22.450 align:start position:0% discoveries of clients because it's a 02:07:22.450 --> 02:07:25.100 align:start position:0% discoveries of clients because it's a very<02:07:23.260> fancy<02:07:23.500> so<02:07:23.680> important 02:07:25.100 --> 02:07:25.110 align:start position:0% very fancy so important 02:07:25.110 --> 02:07:26.570 align:start position:0% very fancy so important and<02:07:25.200> bunches<02:07:25.530> of<02:07:25.710> these<02:07:25.860> different<02:07:26.310> portals 02:07:26.570 --> 02:07:26.580 align:start position:0% and bunches of these different portals 02:07:26.580 --> 02:07:28.610 align:start position:0% and bunches of these different portals different<02:07:27.570> approaches<02:07:28.020> permission 02:07:28.610 --> 02:07:28.620 align:start position:0% different approaches permission 02:07:28.620 --> 02:07:31.550 align:start position:0% different approaches permission regulation<02:07:29.280> all<02:07:29.910> those<02:07:30.060> fees<02:07:30.270> so<02:07:30.930> we<02:07:31.170> end<02:07:31.410> up 02:07:31.550 --> 02:07:31.560 align:start position:0% regulation all those fees so we end up 02:07:31.560 --> 02:07:33.620 align:start position:0% regulation all those fees so we end up like<02:07:31.830> Lowell<02:07:32.070> is<02:07:32.220> having<02:07:32.580> a<02:07:32.700> collaborative 02:07:33.620 --> 02:07:33.630 align:start position:0% like Lowell is having a collaborative 02:07:33.630 --> 02:07:35.600 align:start position:0% like Lowell is having a collaborative discussion<02:07:34.230> about<02:07:34.680> the<02:07:34.860> right<02:07:35.040> metrics<02:07:35.460> know 02:07:35.600 --> 02:07:35.610 align:start position:0% discussion about the right metrics know 02:07:35.610 --> 02:07:38.240 align:start position:0% discussion about the right metrics know and<02:07:35.790> being<02:07:36.000> able<02:07:36.150> to<02:07:36.300> test<02:07:36.570> for<02:07:36.630> so<02:07:37.620> you<02:07:38.160> know 02:07:38.240 --> 02:07:38.250 align:start position:0% and being able to test for so you know 02:07:38.250 --> 02:07:40.040 align:start position:0% and being able to test for so you know initially<02:07:38.760> when<02:07:39.030> we<02:07:39.270> study<02:07:39.510> about<02:07:39.600> people 02:07:40.040 --> 02:07:40.050 align:start position:0% initially when we study about people 02:07:40.050 --> 02:07:43.640 align:start position:0% initially when we study about people just<02:07:40.200> yes<02:07:40.920> just<02:07:41.550> get<02:07:42.120> like<02:07:42.270> a<02:07:42.330> bras<02:07:43.200> for<02:07:43.500> boot 02:07:43.640 --> 02:07:43.650 align:start position:0% just yes just get like a bras for boot 02:07:43.650 --> 02:07:44.570 align:start position:0% just yes just get like a bras for boot of<02:07:43.830> the<02:07:43.860> platform 02:07:44.570 --> 02:07:44.580 align:start position:0% of the platform 02:07:44.580 --> 02:07:50.110 align:start position:0% of the platform I<02:07:44.610> think<02:07:45.180> he's<02:07:45.270> changing<02:07:45.660> a<02:07:45.750> lot<02:07:45.870> more<02:07:46.080> now<02:07:46.230> I 02:07:50.110 --> 02:07:50.120 align:start position:0% 02:07:50.120 --> 02:07:52.580 align:start position:0% hope<02:07:51.120> you<02:07:51.240> can<02:07:51.420> stay<02:07:51.720> for<02:07:51.780> the<02:07:52.110> discussion 02:07:52.580 --> 02:07:52.590 align:start position:0% hope you can stay for the discussion 02:07:52.590 --> 02:07:57.170 align:start position:0% hope you can stay for the discussion part<02:07:52.860> because<02:07:54.260> actually<02:07:55.260> plot<02:07:55.610> yeah<02:07:56.610> we're 02:07:57.170 --> 02:07:57.180 align:start position:0% part because actually plot yeah we're 02:07:57.180 --> 02:08:02.330 align:start position:0% part because actually plot yeah we're going<02:07:57.330> to<02:07:57.420> you<02:07:57.510> guys<02:07:58.100> I'm<02:07:59.100> sorry<02:07:59.370> sir<02:07:59.670> so<02:08:01.340> we 02:08:02.330 --> 02:08:02.340 align:start position:0% going to you guys I'm sorry sir so we 02:08:02.340 --> 02:08:06.170 align:start position:0% going to you guys I'm sorry sir so we really<02:08:03.120> decided<02:08:04.020> to<02:08:04.230> see<02:08:04.410> those<02:08:04.970> summaries<02:08:05.970> on 02:08:06.170 --> 02:08:06.180 align:start position:0% really decided to see those summaries on 02:08:06.180 --> 02:08:20.630 align:start position:0% really decided to see those summaries on I<02:08:17.720> hate<02:08:18.720> my<02:08:18.930> name<02:08:19.110> is<02:08:19.200> Mike<02:08:19.440> gelser<02:08:19.890> I'm<02:08:20.430> from 02:08:20.630 --> 02:08:20.640 align:start position:0% I hate my name is Mike gelser I'm from 02:08:20.640 --> 02:08:22.460 align:start position:0% I hate my name is Mike gelser I'm from the<02:08:20.760> Olympia<02:08:21.090> peat<02:08:21.330> project<02:08:21.870> I<02:08:22.110> work<02:08:22.290> at 02:08:22.460 --> 02:08:22.470 align:start position:0% the Olympia peat project I work at 02:08:22.470 --> 02:08:24.590 align:start position:0% the Olympia peat project I work at protocol<02:08:22.950> labs<02:08:23.190> were<02:08:23.580> one<02:08:24.240> of<02:08:24.270> the<02:08:24.480> sponsors 02:08:24.590 --> 02:08:24.600 align:start position:0% protocol labs were one of the sponsors 02:08:24.600 --> 02:08:27.440 align:start position:0% protocol labs were one of the sponsors of<02:08:24.990> looking<02:08:25.410> to<02:08:25.500> be<02:08:25.730> here's<02:08:26.730> my<02:08:26.970> partner<02:08:27.210> in 02:08:27.440 --> 02:08:27.450 align:start position:0% of looking to be here's my partner in 02:08:27.450 --> 02:08:29.840 align:start position:0% of looking to be here's my partner in crime<02:08:28.190> rollerblading<02:08:29.190> say<02:08:29.430> on<02:08:29.580> the<02:08:29.670> floor 02:08:29.840 --> 02:08:29.850 align:start position:0% crime rollerblading say on the floor 02:08:29.850 --> 02:08:32.540 align:start position:0% crime rollerblading say on the floor there<02:08:30.090> so<02:08:31.050> then<02:08:31.290> so<02:08:31.740> what<02:08:31.890> we<02:08:32.040> have<02:08:32.220> planned 02:08:32.540 --> 02:08:32.550 align:start position:0% there so then so what we have planned 02:08:32.550 --> 02:08:34.580 align:start position:0% there so then so what we have planned for<02:08:32.730> you<02:08:32.940> here<02:08:33.180> at<02:08:33.300> Def<02:08:33.480> Con<02:08:33.510> this<02:08:34.080> week<02:08:34.290> is<02:08:34.560> a 02:08:34.580 --> 02:08:34.590 align:start position:0% for you here at Def Con this week is a 02:08:34.590 --> 02:08:36.980 align:start position:0% for you here at Def Con this week is a kind<02:08:35.070> of<02:08:35.100> escalating<02:08:35.640> series<02:08:35.850> of<02:08:36.120> talks<02:08:36.330> this 02:08:36.980 --> 02:08:36.990 align:start position:0% kind of escalating series of talks this 02:08:36.990 --> 02:08:38.930 align:start position:0% kind of escalating series of talks this 10-minute<02:08:37.320> intro<02:08:37.980> is<02:08:38.280> going<02:08:38.520> to<02:08:38.610> talk<02:08:38.790> about 02:08:38.930 --> 02:08:38.940 align:start position:0% 10-minute intro is going to talk about 02:08:38.940 --> 02:08:41.480 align:start position:0% 10-minute intro is going to talk about what<02:08:39.240> Olympia<02:08:39.630> Diaz<02:08:40.020> what's<02:08:40.680> coming<02:08:41.070> next<02:08:41.250> in 02:08:41.480 --> 02:08:41.490 align:start position:0% what Olympia Diaz what's coming next in 02:08:41.490 --> 02:08:45.140 align:start position:0% what Olympia Diaz what's coming next in the<02:08:41.580> project<02:08:41.990> then<02:08:42.990> in<02:08:43.500> what<02:08:44.280> is<02:08:44.370> the<02:08:44.490> two 02:08:45.140 --> 02:08:45.150 align:start position:0% the project then in what is the two 02:08:45.150 --> 02:08:48.110 align:start position:0% the project then in what is the two hours<02:08:45.480> from<02:08:45.690> now<02:08:45.900> I<02:08:45.930> think<02:08:46.080> and<02:08:46.440> Rudy<02:08:46.890> roll<02:08:47.850> is 02:08:48.110 --> 02:08:48.120 align:start position:0% hours from now I think and Rudy roll is 02:08:48.120 --> 02:08:51.980 align:start position:0% hours from now I think and Rudy roll is going<02:08:48.330> to<02:08:48.420> give<02:08:48.570> his<02:08:49.140> talk<02:08:49.410> on<02:08:50.210> 101<02:08:51.210> of<02:08:51.570> to<02:08:51.780> talk 02:08:51.980 --> 02:08:51.990 align:start position:0% going to give his talk on 101 of to talk 02:08:51.990 --> 02:08:55.040 align:start position:0% going to give his talk on 101 of to talk some<02:08:52.260> blue<02:08:52.410> P<02:08:52.560> defeat<02:08:52.830> that<02:08:53.340> will<02:08:53.780> take<02:08:54.780> it<02:08:54.930> up 02:08:55.040 --> 02:08:55.050 align:start position:0% some blue P defeat that will take it up 02:08:55.050 --> 02:08:56.510 align:start position:0% some blue P defeat that will take it up a<02:08:55.080> level<02:08:55.200> so<02:08:55.680> some<02:08:55.920> of<02:08:55.950> you<02:08:56.190> I<02:08:56.250> know<02:08:56.370> are 02:08:56.510 --> 02:08:56.520 align:start position:0% a level so some of you I know are 02:08:56.520 --> 02:08:58.760 align:start position:0% a level so some of you I know are experts<02:08:57.030> on<02:08:57.120> Limpy<02:08:57.450> to<02:08:57.540> be<02:08:57.720> some<02:08:58.350> of<02:08:58.470> you<02:08:58.590> have 02:08:58.760 --> 02:08:58.770 align:start position:0% experts on Limpy to be some of you have 02:08:58.770 --> 02:09:00.760 align:start position:0% experts on Limpy to be some of you have never<02:08:59.310> heard<02:08:59.580> of<02:08:59.640> it<02:08:59.730> before<02:08:59.910> that's<02:09:00.390> fine 02:09:00.760 --> 02:09:00.770 align:start position:0% never heard of it before that's fine 02:09:00.770 --> 02:09:02.990 align:start position:0% never heard of it before that's fine we're<02:09:01.770> gonna<02:09:01.890> take<02:09:02.100> it<02:09:02.220> up<02:09:02.280> a<02:09:02.430> level<02:09:02.460> in<02:09:02.850> two 02:09:02.990 --> 02:09:03.000 align:start position:0% we're gonna take it up a level in two 02:09:03.000 --> 02:09:04.490 align:start position:0% we're gonna take it up a level in two hours<02:09:03.330> and<02:09:03.540> Rudy 02:09:04.490 --> 02:09:04.500 align:start position:0% hours and Rudy 02:09:04.500 --> 02:09:06.740 align:start position:0% hours and Rudy Royals<02:09:05.160> going<02:09:05.340> to<02:09:05.430> give<02:09:05.550> his<02:09:06.090> introductory 02:09:06.740 --> 02:09:06.750 align:start position:0% Royals going to give his introductory 02:09:06.750 --> 02:09:08.630 align:start position:0% Royals going to give his introductory talk<02:09:07.140> on<02:09:07.320> Limpy<02:09:07.590> defeat<02:09:07.890> and<02:09:08.280> then<02:09:08.460> tomorrow 02:09:08.630 --> 02:09:08.640 align:start position:0% talk on Limpy defeat and then tomorrow 02:09:08.640 --> 02:09:11.000 align:start position:0% talk on Limpy defeat and then tomorrow we're<02:09:09.150> going<02:09:09.300> to<02:09:09.360> go<02:09:09.570> roll<02:09:10.470> is<02:09:10.590> going<02:09:10.740> to<02:09:10.830> give 02:09:11.000 --> 02:09:11.010 align:start position:0% we're going to go roll is going to give 02:09:11.010 --> 02:09:13.400 align:start position:0% we're going to go roll is going to give a<02:09:11.040> second<02:09:11.550> talk<02:09:11.730> which<02:09:12.300> could<02:09:12.540> dive<02:09:12.750> deep<02:09:13.140> into 02:09:13.400 --> 02:09:13.410 align:start position:0% a second talk which could dive deep into 02:09:13.410 --> 02:09:16.490 align:start position:0% a second talk which could dive deep into one<02:09:13.710> aspect<02:09:14.220> of<02:09:14.340> loopy<02:09:14.700> to<02:09:14.760> be<02:09:15.000> that<02:09:15.510> is<02:09:15.780> of 02:09:16.490 --> 02:09:16.500 align:start position:0% one aspect of loopy to be that is of 02:09:16.500 --> 02:09:18.740 align:start position:0% one aspect of loopy to be that is of interest<02:09:16.710> I<02:09:17.070> think<02:09:17.100> to<02:09:17.640> the<02:09:18.180> etherium<02:09:18.600> to 02:09:18.740 --> 02:09:18.750 align:start position:0% interest I think to the etherium to 02:09:18.750 --> 02:09:21.680 align:start position:0% interest I think to the etherium to community<02:09:19.260> especially<02:09:19.470> which<02:09:20.010> is<02:09:20.450> gossip<02:09:21.450> sub 02:09:21.680 --> 02:09:21.690 align:start position:0% community especially which is gossip sub 02:09:21.690 --> 02:09:25.430 align:start position:0% community especially which is gossip sub and<02:09:22.080> so<02:09:22.590> digging<02:09:23.190> digging<02:09:23.640> deep<02:09:24.420> into<02:09:24.660> that<02:09:24.960> so 02:09:25.430 --> 02:09:25.440 align:start position:0% and so digging digging deep into that so 02:09:25.440 --> 02:09:28.250 align:start position:0% and so digging digging deep into that so that's<02:09:26.100> kind<02:09:26.280> of<02:09:26.340> our<02:09:26.490> plan<02:09:26.760> for<02:09:27.090> Def<02:09:27.300> Con 02:09:28.250 --> 02:09:28.260 align:start position:0% that's kind of our plan for Def Con 02:09:28.260 --> 02:09:30.290 align:start position:0% that's kind of our plan for Def Con if<02:09:28.560> you<02:09:28.739> have<02:09:28.920> no<02:09:29.130> idea<02:09:29.520> what<02:09:29.730> lifting<02:09:30.090> if<02:09:30.180> he 02:09:30.290 --> 02:09:30.300 align:start position:0% if you have no idea what lifting if he 02:09:30.300 --> 02:09:33.110 align:start position:0% if you have no idea what lifting if he is<02:09:30.480> let<02:09:31.110> me<02:09:31.140> start<02:09:31.500> out<02:09:31.620> looking<02:09:32.460> feet<02:09:32.850> we're 02:09:33.110 --> 02:09:33.120 align:start position:0% is let me start out looking feet we're 02:09:33.120 --> 02:09:36.350 align:start position:0% is let me start out looking feet we're out<02:09:33.210> of<02:09:33.239> the<02:09:33.510> ipfs<02:09:34.170> project<02:09:34.770> ipfs<02:09:35.670> is<02:09:36.000> a 02:09:36.350 --> 02:09:36.360 align:start position:0% out of the ipfs project ipfs is a 02:09:36.360 --> 02:09:38.540 align:start position:0% out of the ipfs project ipfs is a project<02:09:36.780> that<02:09:37.080> actually<02:09:37.920> I<02:09:37.980> think<02:09:38.070> there<02:09:38.460> are 02:09:38.540 --> 02:09:38.550 align:start position:0% project that actually I think there are 02:09:38.550 --> 02:09:39.500 align:start position:0% project that actually I think there are out<02:09:38.670> of<02:09:38.700> quarter<02:09:39.000> you're<02:09:39.150> going<02:09:39.270> to<02:09:39.330> hear 02:09:39.500 --> 02:09:39.510 align:start position:0% out of quarter you're going to hear 02:09:39.510 --> 02:09:42.260 align:start position:0% out of quarter you're going to hear about<02:09:39.600> this<02:09:39.950> in<02:09:40.950> a<02:09:41.160> few<02:09:41.340> minutes<02:09:41.640> so<02:09:41.820> I<02:09:41.850> won't 02:09:42.260 --> 02:09:42.270 align:start position:0% about this in a few minutes so I won't 02:09:42.270 --> 02:09:44.450 align:start position:0% about this in a few minutes so I won't give<02:09:42.480> it<02:09:42.600> away<02:09:42.630> but<02:09:42.810> it's<02:09:43.710> a<02:09:43.860> project<02:09:44.250> to<02:09:44.340> build 02:09:44.450 --> 02:09:44.460 align:start position:0% give it away but it's a project to build 02:09:44.460 --> 02:09:47.690 align:start position:0% give it away but it's a project to build a<02:09:44.670> globally<02:09:45.180> or<02:09:45.480> are<02:09:46.350> even<02:09:46.700> cosmically 02:09:47.690 --> 02:09:47.700 align:start position:0% a globally or are even cosmically 02:09:47.700 --> 02:09:51.590 align:start position:0% a globally or are even cosmically distributed<02:09:48.360> file<02:09:49.200> system<02:09:49.680> based<02:09:50.130> on<02:09:50.600> content 02:09:51.590 --> 02:09:51.600 align:start position:0% distributed file system based on content 02:09:51.600 --> 02:09:54.770 align:start position:0% distributed file system based on content addressable<02:09:53.239> content<02:09:54.239> content 02:09:54.770 --> 02:09:54.780 align:start position:0% addressable content content 02:09:54.780 --> 02:09:59.750 align:start position:0% addressable content content accessibility<02:09:55.080> and<02:09:56.040> so<02:09:57.230> let<02:09:58.230> p2p<02:09:58.680> was<02:09:59.430> the 02:09:59.750 --> 02:09:59.760 align:start position:0% accessibility and so let p2p was the 02:09:59.760 --> 02:10:03.560 align:start position:0% accessibility and so let p2p was the networking<02:10:00.270> layer<02:10:00.480> and<02:10:01.020> ipfs<02:10:01.560> and<02:10:01.920> what<02:10:02.570> the 02:10:03.560 --> 02:10:03.570 align:start position:0% networking layer and ipfs and what the 02:10:03.570 --> 02:10:05.810 align:start position:0% networking layer and ipfs and what the builders<02:10:04.380> who<02:10:04.530> I<02:10:04.620> think<02:10:04.830> has<02:10:04.980> realized<02:10:05.460> as 02:10:05.810 --> 02:10:05.820 align:start position:0% builders who I think has realized as 02:10:05.820 --> 02:10:08.479 align:start position:0% builders who I think has realized as they<02:10:06.330> were<02:10:06.780> building<02:10:07.170> idea<02:10:07.500> test<02:10:07.739> was<02:10:08.250> that 02:10:08.479 --> 02:10:08.489 align:start position:0% they were building idea test was that 02:10:08.489 --> 02:10:11.330 align:start position:0% they were building idea test was that hey<02:10:08.670> we<02:10:09.270> could<02:10:09.450> factor<02:10:09.660> out<02:10:09.900> this<02:10:10.340> networking 02:10:11.330 --> 02:10:11.340 align:start position:0% hey we could factor out this networking 02:10:11.340 --> 02:10:13.490 align:start position:0% hey we could factor out this networking layer<02:10:11.489> it<02:10:11.850> could<02:10:11.970> be<02:10:12.090> useful<02:10:12.239> for<02:10:12.510> other<02:10:13.110> D 02:10:13.490 --> 02:10:13.500 align:start position:0% layer it could be useful for other D 02:10:13.500 --> 02:10:16.070 align:start position:0% layer it could be useful for other D apps<02:10:13.710> or<02:10:14.100> anybody<02:10:15.030> who<02:10:15.239> want<02:10:15.420> to<02:10:15.480> build<02:10:15.840> a 02:10:16.070 --> 02:10:16.080 align:start position:0% apps or anybody who want to build a 02:10:16.080 --> 02:10:20.900 align:start position:0% apps or anybody who want to build a peer-to-peer<02:10:16.320> system<02:10:16.980> and<02:10:17.730> so<02:10:19.070> today<02:10:20.070> Lib<02:10:20.489> p2p 02:10:20.900 --> 02:10:20.910 align:start position:0% peer-to-peer system and so today Lib p2p 02:10:20.910 --> 02:10:23.540 align:start position:0% peer-to-peer system and so today Lib p2p is<02:10:21.120> its<02:10:21.330> own<02:10:21.510> standalone<02:10:22.110> library<02:10:22.860> its<02:10:23.400> own 02:10:23.540 --> 02:10:23.550 align:start position:0% is its own standalone library its own 02:10:23.550 --> 02:10:25.580 align:start position:0% is its own standalone library its own standalone<02:10:23.940> project<02:10:24.780> it<02:10:25.020> has<02:10:25.320> the 02:10:25.580 --> 02:10:25.590 align:start position:0% standalone project it has the 02:10:25.590 --> 02:10:27.440 align:start position:0% standalone project it has the implementations<02:10:26.190> in<02:10:26.340> multiple<02:10:26.790> languages<02:10:27.120> as 02:10:27.440 --> 02:10:27.450 align:start position:0% implementations in multiple languages as 02:10:27.450 --> 02:10:28.820 align:start position:0% implementations in multiple languages as we'll<02:10:27.600> see<02:10:27.750> in<02:10:27.840> a<02:10:27.900> minute<02:10:28.050> is<02:10:28.350> the 02:10:28.820 --> 02:10:28.830 align:start position:0% we'll see in a minute is the 02:10:28.830 --> 02:10:31.700 align:start position:0% we'll see in a minute is the foundational<02:10:29.520> layer<02:10:29.730> for<02:10:30.320> many<02:10:31.320> different 02:10:31.700 --> 02:10:31.710 align:start position:0% foundational layer for many different 02:10:31.710 --> 02:10:34.100 align:start position:0% foundational layer for many different projects<02:10:32.130> before<02:10:32.340> ipfs<02:10:33.120> obviously<02:10:33.750> those<02:10:34.080> are 02:10:34.100 --> 02:10:34.110 align:start position:0% projects before ipfs obviously those are 02:10:34.110 --> 02:10:37.280 align:start position:0% projects before ipfs obviously those are came<02:10:34.410> from<02:10:34.650> for<02:10:35.340> aetherium<02:10:35.640> 2.0<02:10:36.510> that's<02:10:37.110> what 02:10:37.280 --> 02:10:37.290 align:start position:0% came from for aetherium 2.0 that's what 02:10:37.290 --> 02:10:38.540 align:start position:0% came from for aetherium 2.0 that's what you're<02:10:37.410> going<02:10:37.500> to<02:10:37.590> hear<02:10:37.770> a<02:10:37.800> lot<02:10:38.070> about<02:10:38.340> this 02:10:38.540 --> 02:10:38.550 align:start position:0% you're going to hear a lot about this 02:10:38.550 --> 02:10:41.630 align:start position:0% you're going to hear a lot about this week<02:10:38.850> here<02:10:39.750> at<02:10:39.840> Def<02:10:40.020> Con<02:10:40.050> and<02:10:40.470> then<02:10:40.620> the<02:10:40.950> sort 02:10:41.630 --> 02:10:41.640 align:start position:0% week here at Def Con and then the sort 02:10:41.640 --> 02:10:43.760 align:start position:0% week here at Def Con and then the sort of<02:10:41.700> main<02:10:41.850> source<02:10:42.120> of<02:10:42.210> interest<02:10:42.570> at<02:10:42.720> this<02:10:42.870> at 02:10:43.760 --> 02:10:43.770 align:start position:0% of main source of interest at this at 02:10:43.770 --> 02:10:45.920 align:start position:0% of main source of interest at this at this<02:10:43.980> event<02:10:44.310> and<02:10:44.520> then<02:10:44.880> for<02:10:45.480> many<02:10:45.600> more 02:10:45.920 --> 02:10:45.930 align:start position:0% this event and then for many more 02:10:45.930 --> 02:10:47.900 align:start position:0% this event and then for many more projects<02:10:46.470> I<02:10:46.710> don't<02:10:47.250> have<02:10:47.340> time<02:10:47.520> to<02:10:47.730> go<02:10:47.850> through 02:10:47.900 --> 02:10:47.910 align:start position:0% projects I don't have time to go through 02:10:47.910 --> 02:10:50.780 align:start position:0% projects I don't have time to go through them<02:10:48.270> all<02:10:48.420> but<02:10:48.900> this<02:10:49.080> is<02:10:49.260> a<02:10:49.290> rough<02:10:50.070> list<02:10:50.340> of 02:10:50.780 --> 02:10:50.790 align:start position:0% them all but this is a rough list of 02:10:50.790 --> 02:10:53.540 align:start position:0% them all but this is a rough list of many<02:10:51.450> of<02:10:51.630> the<02:10:51.690> projects<02:10:52.080> that<02:10:52.230> are<02:10:52.320> using<02:10:52.860> lit 02:10:53.540 --> 02:10:53.550 align:start position:0% many of the projects that are using lit 02:10:53.550 --> 02:10:58.310 align:start position:0% many of the projects that are using lit p2p<02:10:54.000> today<02:10:56.450> okay<02:10:57.480> let<02:10:57.750> me<02:10:57.840> just<02:10:58.050> explain 02:10:58.310 --> 02:10:58.320 align:start position:0% p2p today okay let me just explain 02:10:58.320 --> 02:11:02.150 align:start position:0% p2p today okay let me just explain really<02:10:58.680> briefly<02:10:59.040> what<02:10:59.310> lit<02:10:59.520> Fifi<02:10:59.880> is<02:11:01.010> like<02:11:02.010> I 02:11:02.150 --> 02:11:02.160 align:start position:0% really briefly what lit Fifi is like I 02:11:02.160 --> 02:11:04.010 align:start position:0% really briefly what lit Fifi is like I said<02:11:02.370> it's<02:11:02.580> a<02:11:02.700> foundational<02:11:03.390> layer<02:11:03.570> to<02:11:03.840> build 02:11:04.010 --> 02:11:04.020 align:start position:0% said it's a foundational layer to build 02:11:04.020 --> 02:11:07.070 align:start position:0% said it's a foundational layer to build peer-to-peer<02:11:04.500> networks<02:11:05.340> not<02:11:06.080> build 02:11:07.070 --> 02:11:07.080 align:start position:0% peer-to-peer networks not build 02:11:07.080 --> 02:11:09.170 align:start position:0% peer-to-peer networks not build peer-to-peer<02:11:07.380> applications<02:11:07.830> where<02:11:08.760> you<02:11:08.970> need 02:11:09.170 --> 02:11:09.180 align:start position:0% peer-to-peer applications where you need 02:11:09.180 --> 02:11:11.510 align:start position:0% peer-to-peer applications where you need an<02:11:09.300> underlying<02:11:09.840> pure<02:11:10.560> peer<02:11:10.830> networking<02:11:11.190> layer 02:11:11.510 --> 02:11:11.520 align:start position:0% an underlying pure peer networking layer 02:11:11.520 --> 02:11:13.670 align:start position:0% an underlying pure peer networking layer and<02:11:12.060> so<02:11:12.420> we<02:11:12.930> have<02:11:13.140> the<02:11:13.290> different 02:11:13.670 --> 02:11:13.680 align:start position:0% and so we have the different 02:11:13.680 --> 02:11:15.410 align:start position:0% and so we have the different abstractions<02:11:13.860> that<02:11:14.730> provide<02:11:15.090> you<02:11:15.239> with 02:11:15.410 --> 02:11:15.420 align:start position:0% abstractions that provide you with 02:11:15.420 --> 02:11:16.490 align:start position:0% abstractions that provide you with different<02:11:15.600> functionality 02:11:16.490 --> 02:11:16.500 align:start position:0% different functionality 02:11:16.500 --> 02:11:19.460 align:start position:0% different functionality that<02:11:16.590> you<02:11:16.710> will<02:11:16.830> need<02:11:17.040> to<02:11:17.760> build<02:11:18.390> one<02:11:19.170> of<02:11:19.320> these 02:11:19.460 --> 02:11:19.470 align:start position:0% that you will need to build one of these 02:11:19.470 --> 02:11:20.990 align:start position:0% that you will need to build one of these types<02:11:19.740> of<02:11:19.890> applications<02:11:20.550> so<02:11:20.790> an<02:11:20.910> example 02:11:20.990 --> 02:11:21.000 align:start position:0% types of applications so an example 02:11:21.000 --> 02:11:23.810 align:start position:0% types of applications so an example would<02:11:21.540> be<02:11:21.600> transport<02:11:22.560> a<02:11:22.860> transport<02:11:23.580> could<02:11:23.730> be 02:11:23.810 --> 02:11:23.820 align:start position:0% would be transport a transport could be 02:11:23.820 --> 02:11:26.630 align:start position:0% would be transport a transport could be something<02:11:24.150> like<02:11:24.330> a<02:11:24.360> TC<02:11:24.750> TC<02:11:25.440> P<02:11:25.740> it<02:11:26.370> could<02:11:26.550> be 02:11:26.630 --> 02:11:26.640 align:start position:0% something like a TC TC P it could be 02:11:26.640 --> 02:11:28.640 align:start position:0% something like a TC TC P it could be something<02:11:26.910> like<02:11:26.940> UDP<02:11:27.540> it<02:11:28.110> could<02:11:28.260> be<02:11:28.320> something 02:11:28.640 --> 02:11:28.650 align:start position:0% something like UDP it could be something 02:11:28.650 --> 02:11:31.910 align:start position:0% something like UDP it could be something like<02:11:29.150> radio<02:11:30.150> ham<02:11:30.450> radio<02:11:30.840> it<02:11:31.470> could<02:11:31.590> be<02:11:31.710> a<02:11:31.740> lot 02:11:31.910 --> 02:11:31.920 align:start position:0% like radio ham radio it could be a lot 02:11:31.920 --> 02:11:32.810 align:start position:0% like radio ham radio it could be a lot of<02:11:31.950> different<02:11:32.130> things 02:11:32.810 --> 02:11:32.820 align:start position:0% of different things 02:11:32.820 --> 02:11:35.840 align:start position:0% of different things it<02:11:33.150> moves<02:11:33.480> packets<02:11:34.080> from<02:11:34.200> one<02:11:34.670> place<02:11:35.670> to 02:11:35.840 --> 02:11:35.850 align:start position:0% it moves packets from one place to 02:11:35.850 --> 02:11:38.390 align:start position:0% it moves packets from one place to another<02:11:36.230> we<02:11:37.230> then<02:11:37.410> have<02:11:37.620> these<02:11:37.800> notions<02:11:38.100> of 02:11:38.390 --> 02:11:38.400 align:start position:0% another we then have these notions of 02:11:38.400 --> 02:11:40.610 align:start position:0% another we then have these notions of crypto<02:11:38.760> channels<02:11:39.270> and<02:11:39.510> stream<02:11:39.840> multiplexers 02:11:40.610 --> 02:11:40.620 align:start position:0% crypto channels and stream multiplexers 02:11:40.620 --> 02:11:42.380 align:start position:0% crypto channels and stream multiplexers I<02:11:40.830> won't<02:11:41.190> go<02:11:41.310> into<02:11:41.460> the<02:11:41.670> details<02:11:42.060> of<02:11:42.180> these 02:11:42.380 --> 02:11:42.390 align:start position:0% I won't go into the details of these 02:11:42.390 --> 02:11:44.270 align:start position:0% I won't go into the details of these right<02:11:42.630> now<02:11:42.660> but<02:11:43.020> the<02:11:43.110> basic<02:11:43.410> idea<02:11:43.740> is<02:11:44.010> that 02:11:44.270 --> 02:11:44.280 align:start position:0% right now but the basic idea is that 02:11:44.280 --> 02:11:47.150 align:start position:0% right now but the basic idea is that inlet<02:11:45.060> p2p<02:11:45.480> you<02:11:45.930> establish<02:11:46.500> some<02:11:46.740> type<02:11:46.950> of<02:11:46.980> a 02:11:47.150 --> 02:11:47.160 align:start position:0% inlet p2p you establish some type of a 02:11:47.160 --> 02:11:49.580 align:start position:0% inlet p2p you establish some type of a connection<02:11:47.670> over<02:11:47.760> a<02:11:48.000> transport<02:11:48.630> and<02:11:49.410> then 02:11:49.580 --> 02:11:49.590 align:start position:0% connection over a transport and then 02:11:49.590 --> 02:11:50.720 align:start position:0% connection over a transport and then once<02:11:49.860> you<02:11:50.010> have<02:11:50.190> that<02:11:50.250> connection 02:11:50.720 --> 02:11:50.730 align:start position:0% once you have that connection 02:11:50.730 --> 02:11:52.820 align:start position:0% once you have that connection established<02:11:51.420> of<02:11:52.110> course<02:11:52.410> you<02:11:52.560> want 02:11:52.820 --> 02:11:52.830 align:start position:0% established of course you want 02:11:52.830 --> 02:11:55.400 align:start position:0% established of course you want encryption<02:11:53.460> you<02:11:54.060> want<02:11:54.300> authentication<02:11:55.170> and 02:11:55.400 --> 02:11:55.410 align:start position:0% encryption you want authentication and 02:11:55.410 --> 02:11:59.060 align:start position:0% encryption you want authentication and you<02:11:55.830> want<02:11:56.600> you've<02:11:57.600> got<02:11:57.750> the<02:11:57.900> ability<02:11:58.290> to<02:11:58.320> send 02:11:59.060 --> 02:11:59.070 align:start position:0% you want you've got the ability to send 02:11:59.070 --> 02:12:02.390 align:start position:0% you want you've got the ability to send multiple<02:11:59.370> streams<02:12:00.090> data<02:12:01.080> streams<02:12:01.470> over<02:12:01.950> that 02:12:02.390 --> 02:12:02.400 align:start position:0% multiple streams data streams over that 02:12:02.400 --> 02:12:03.950 align:start position:0% multiple streams data streams over that connection<02:12:02.760> at<02:12:03.000> the<02:12:03.120> same<02:12:03.300> time<02:12:03.600> and<02:12:03.870> that's 02:12:03.950 --> 02:12:03.960 align:start position:0% connection at the same time and that's 02:12:03.960 --> 02:12:06.950 align:start position:0% connection at the same time and that's what<02:12:04.230> extreme<02:12:04.860> multiplexing<02:12:05.580> is<02:12:05.730> about<02:12:05.970> of 02:12:06.950 --> 02:12:06.960 align:start position:0% what extreme multiplexing is about of 02:12:06.960 --> 02:12:10.280 align:start position:0% what extreme multiplexing is about of course<02:12:07.260> like<02:12:07.920> any<02:12:08.130> peer-to-peer<02:12:08.520> system<02:12:09.290> like 02:12:10.280 --> 02:12:10.290 align:start position:0% course like any peer-to-peer system like 02:12:10.290 --> 02:12:11.270 align:start position:0% course like any peer-to-peer system like some<02:12:10.440> of<02:12:10.560> the<02:12:10.620> ones<02:12:10.800> you've<02:12:10.950> heard<02:12:11.160> about 02:12:11.270 --> 02:12:11.280 align:start position:0% some of the ones you've heard about 02:12:11.280 --> 02:12:14.150 align:start position:0% some of the ones you've heard about earlier<02:12:11.850> today<02:12:12.090> or<02:12:12.690> some<02:12:13.440> of<02:12:13.530> the<02:12:13.680> older<02:12:13.710> ones 02:12:14.150 --> 02:12:14.160 align:start position:0% earlier today or some of the older ones 02:12:14.160 --> 02:12:17.660 align:start position:0% earlier today or some of the older ones like<02:12:14.820> BitTorrent<02:12:15.330> and<02:12:15.930> so<02:12:16.200> forth<02:12:16.410> you<02:12:17.370> need<02:12:17.640> a 02:12:17.660 --> 02:12:17.670 align:start position:0% like BitTorrent and so forth you need a 02:12:17.670 --> 02:12:19.760 align:start position:0% like BitTorrent and so forth you need a way<02:12:17.970> to<02:12:18.000> discover<02:12:18.630> other<02:12:18.840> beers<02:12:19.350> so<02:12:19.650> we 02:12:19.760 --> 02:12:19.770 align:start position:0% way to discover other beers so we 02:12:19.770 --> 02:12:22.490 align:start position:0% way to discover other beers so we provide<02:12:20.160> pure<02:12:20.430> discovery<02:12:21.140> we<02:12:22.140> provide 02:12:22.490 --> 02:12:22.500 align:start position:0% provide pure discovery we provide 02:12:22.500 --> 02:12:24.410 align:start position:0% provide pure discovery we provide several<02:12:22.830> mechanisms<02:12:23.160> to<02:12:23.730> do<02:12:23.880> that<02:12:24.060> you<02:12:24.270> can 02:12:24.410 --> 02:12:24.420 align:start position:0% several mechanisms to do that you can 02:12:24.420 --> 02:12:26.450 align:start position:0% several mechanisms to do that you can discover<02:12:24.780> peers<02:12:25.170> on<02:12:25.410> your<02:12:25.860> local<02:12:26.280> network 02:12:26.450 --> 02:12:26.460 align:start position:0% discover peers on your local network 02:12:26.460 --> 02:12:29.930 align:start position:0% discover peers on your local network through<02:12:27.500> mdns<02:12:28.500> you<02:12:28.830> can<02:12:28.980> also<02:12:29.130> discover<02:12:29.460> peers 02:12:29.930 --> 02:12:29.940 align:start position:0% through mdns you can also discover peers 02:12:29.940 --> 02:12:32.510 align:start position:0% through mdns you can also discover peers on<02:12:30.150> a<02:12:30.180> global<02:12:30.690> network<02:12:31.050> through<02:12:31.830> a 02:12:32.510 --> 02:12:32.520 align:start position:0% on a global network through a 02:12:32.520 --> 02:12:37.160 align:start position:0% on a global network through a distributed<02:12:33.330> hash<02:12:33.480> table<02:12:34.100> which<02:12:35.100> is<02:12:35.580> a<02:12:36.210> I 02:12:37.160 --> 02:12:37.170 align:start position:0% distributed hash table which is a I 02:12:37.170 --> 02:12:39.320 align:start position:0% distributed hash table which is a I think<02:12:37.620> we've<02:12:37.860> actually<02:12:38.340> heard<02:12:38.610> about<02:12:38.760> these<02:12:38.970> a 02:12:39.320 --> 02:12:39.330 align:start position:0% think we've actually heard about these a 02:12:39.330 --> 02:12:42.350 align:start position:0% think we've actually heard about these a little<02:12:39.600> bit<02:12:39.930> this<02:12:40.020> morning<02:12:40.080> so<02:12:40.610> but<02:12:41.610> it<02:12:42.150> is<02:12:42.330> a 02:12:42.350 --> 02:12:42.360 align:start position:0% little bit this morning so but it is a 02:12:42.360 --> 02:12:44.950 align:start position:0% little bit this morning so but it is a the<02:12:42.990> most<02:12:43.200> common<02:12:43.530> data<02:12:43.710> structure<02:12:44.070> for 02:12:44.950 --> 02:12:44.960 align:start position:0% the most common data structure for 02:12:44.960 --> 02:12:49.100 align:start position:0% the most common data structure for finding<02:12:46.340> content<02:12:47.340> on<02:12:47.610> a<02:12:48.110> globally 02:12:49.100 --> 02:12:49.110 align:start position:0% finding content on a globally 02:12:49.110 --> 02:12:51.470 align:start position:0% finding content on a globally distributed<02:12:49.700> peer-to-peer<02:12:50.700> network<02:12:51.270> that 02:12:51.470 --> 02:12:51.480 align:start position:0% distributed peer-to-peer network that 02:12:51.480 --> 02:12:53.990 align:start position:0% distributed peer-to-peer network that doesn't<02:12:51.780> have<02:12:51.900> any<02:12:52.050> centralized<02:12:53.000> lookup 02:12:53.990 --> 02:12:54.000 align:start position:0% doesn't have any centralized lookup 02:12:54.000 --> 02:12:55.730 align:start position:0% doesn't have any centralized lookup point<02:12:54.300> the<02:12:54.510> way<02:12:54.660> that<02:12:54.960> the<02:12:55.260> central 02:12:55.730 --> 02:12:55.740 align:start position:0% point the way that the central 02:12:55.740 --> 02:12:59.120 align:start position:0% point the way that the central centralized<02:12:56.460> applications<02:12:57.030> do<02:12:58.130> nationalism 02:12:59.120 --> 02:12:59.130 align:start position:0% centralized applications do nationalism 02:12:59.130 --> 02:13:01.370 align:start position:0% centralized applications do nationalism is<02:12:59.340> another<02:12:59.640> big<02:12:59.850> issue<02:12:59.880> many<02:13:00.810> users<02:13:01.200> are 02:13:01.370 --> 02:13:01.380 align:start position:0% is another big issue many users are 02:13:01.380 --> 02:13:05.450 align:start position:0% is another big issue many users are behind<02:13:01.770> Nats<02:13:02.810> they<02:13:03.810> either<02:13:04.500> don't<02:13:05.130> know<02:13:05.250> how 02:13:05.450 --> 02:13:05.460 align:start position:0% behind Nats they either don't know how 02:13:05.460 --> 02:13:08.000 align:start position:0% behind Nats they either don't know how to<02:13:05.520> or<02:13:05.970> don't<02:13:06.750> want<02:13:06.900> to<02:13:06.990> go<02:13:07.110> to<02:13:07.170> the<02:13:07.440> trouble<02:13:07.680> of 02:13:08.000 --> 02:13:08.010 align:start position:0% to or don't want to go to the trouble of 02:13:08.010 --> 02:13:11.990 align:start position:0% to or don't want to go to the trouble of opening<02:13:08.720> ports<02:13:09.720> on<02:13:09.900> their<02:13:10.050> routers<02:13:10.440> so<02:13:11.000> we 02:13:11.990 --> 02:13:12.000 align:start position:0% opening ports on their routers so we 02:13:12.000 --> 02:13:14.680 align:start position:0% opening ports on their routers so we have<02:13:12.210> logic<02:13:12.960> in<02:13:13.080> Limpy<02:13:13.440> P<02:13:13.680> to<02:13:13.890> help<02:13:14.100> with 02:13:14.680 --> 02:13:14.690 align:start position:0% have logic in Limpy P to help with 02:13:14.690 --> 02:13:16.500 align:start position:0% have logic in Limpy P to help with traversing<02:13:15.690> Nats<02:13:15.900> and 02:13:16.500 --> 02:13:16.510 align:start position:0% traversing Nats and 02:13:16.510 --> 02:13:18.990 align:start position:0% traversing Nats and getting<02:13:16.900> the<02:13:17.830> actual<02:13:18.190> machine<02:13:18.370> they<02:13:18.790> have<02:13:18.880> to 02:13:18.990 --> 02:13:19.000 align:start position:0% getting the actual machine they have to 02:13:19.000 --> 02:13:22.500 align:start position:0% getting the actual machine they have to appear<02:13:19.420> to<02:13:20.380> appear<02:13:20.830> as<02:13:20.950> if<02:13:21.100> it<02:13:21.310> has<02:13:21.550> it's<02:13:22.330> on 02:13:22.500 --> 02:13:22.510 align:start position:0% appear to appear as if it has it's on 02:13:22.510 --> 02:13:26.250 align:start position:0% appear to appear as if it has it's on the<02:13:22.690> public<02:13:22.990> internet<02:13:25.080> publish/subscribe<02:13:26.080> is 02:13:26.250 --> 02:13:26.260 align:start position:0% the public internet publish/subscribe is 02:13:26.260 --> 02:13:27.960 align:start position:0% the public internet publish/subscribe is a<02:13:26.290> whole<02:13:26.530> topic<02:13:26.920> in<02:13:27.190> and<02:13:27.310> of<02:13:27.370> itself<02:13:27.700> but 02:13:27.960 --> 02:13:27.970 align:start position:0% a whole topic in and of itself but 02:13:27.970 --> 02:13:30.330 align:start position:0% a whole topic in and of itself but basically<02:13:28.420> once<02:13:29.320> you<02:13:29.500> have<02:13:29.710> a<02:13:29.740> set<02:13:30.010> of<02:13:30.100> peers 02:13:30.330 --> 02:13:30.340 align:start position:0% basically once you have a set of peers 02:13:30.340 --> 02:13:32.280 align:start position:0% basically once you have a set of peers connected<02:13:30.820> to<02:13:30.940> each<02:13:31.060> other<02:13:31.270> you<02:13:31.900> want<02:13:32.080> to<02:13:32.200> be 02:13:32.280 --> 02:13:32.290 align:start position:0% connected to each other you want to be 02:13:32.290 --> 02:13:34.920 align:start position:0% connected to each other you want to be able<02:13:32.350> to<02:13:33.090> you<02:13:34.090> want<02:13:34.300> to<02:13:34.390> enable<02:13:34.600> them<02:13:34.870> to 02:13:34.920 --> 02:13:34.930 align:start position:0% able to you want to enable them to 02:13:34.930 --> 02:13:36.420 align:start position:0% able to you want to enable them to communicate<02:13:35.350> with<02:13:35.530> each<02:13:35.740> other<02:13:35.950> in<02:13:36.130> one<02:13:36.310> of 02:13:36.420 --> 02:13:36.430 align:start position:0% communicate with each other in one of 02:13:36.430 --> 02:13:38.930 align:start position:0% communicate with each other in one of the<02:13:36.520> ways<02:13:36.810> one<02:13:37.810> of<02:13:37.870> the<02:13:37.960> most<02:13:38.050> common 02:13:38.930 --> 02:13:38.940 align:start position:0% the ways one of the most common 02:13:38.940 --> 02:13:41.550 align:start position:0% the ways one of the most common communications<02:13:39.940> paradigms<02:13:40.750> in<02:13:41.050> distributed 02:13:41.550 --> 02:13:41.560 align:start position:0% communications paradigms in distributed 02:13:41.560 --> 02:13:44.130 align:start position:0% communications paradigms in distributed systems<02:13:41.920> is<02:13:42.300> publish/subscribe<02:13:43.300> so<02:13:43.900> we<02:13:43.990> have 02:13:44.130 --> 02:13:44.140 align:start position:0% systems is publish/subscribe so we have 02:13:44.140 --> 02:13:45.660 align:start position:0% systems is publish/subscribe so we have several<02:13:44.380> mechanisms<02:13:44.710> for<02:13:45.280> a<02:13:45.340> published 02:13:45.660 --> 02:13:45.670 align:start position:0% several mechanisms for a published 02:13:45.670 --> 02:13:49.080 align:start position:0% several mechanisms for a published publish/subscribe<02:13:46.860> and<02:13:47.860> one<02:13:48.760> of<02:13:48.880> those 02:13:49.080 --> 02:13:49.090 align:start position:0% publish/subscribe and one of those 02:13:49.090 --> 02:13:52.080 align:start position:0% publish/subscribe and one of those gossips<02:13:49.720> of<02:13:49.900> is<02:13:50.110> it's<02:13:50.380> the<02:13:50.590> most<02:13:50.770> oh<02:13:51.400> the<02:13:51.970> most 02:13:52.080 --> 02:13:52.090 align:start position:0% gossips of is it's the most oh the most 02:13:52.090 --> 02:13:54.300 align:start position:0% gossips of is it's the most oh the most efficient<02:13:52.540> one<02:13:52.660> we<02:13:52.780> have<02:13:52.960> right<02:13:52.990> now<02:13:53.350> that's 02:13:54.300 --> 02:13:54.310 align:start position:0% efficient one we have right now that's 02:13:54.310 --> 02:13:56.580 align:start position:0% efficient one we have right now that's the<02:13:54.460> one<02:13:54.670> that<02:13:54.970> Raul<02:13:55.960> is<02:13:56.170> going<02:13:56.320> to<02:13:56.410> give<02:13:56.500> a 02:13:56.580 --> 02:13:56.590 align:start position:0% the one that Raul is going to give a 02:13:56.590 --> 02:14:00.840 align:start position:0% the one that Raul is going to give a deep<02:13:56.770> dive<02:13:56.950> on<02:13:57.190> in<02:13:57.640> tomorrow<02:13:59.190> so<02:14:00.190> you<02:14:00.670> should 02:14:00.840 --> 02:14:00.850 align:start position:0% deep dive on in tomorrow so you should 02:14:00.850 --> 02:14:04.230 align:start position:0% deep dive on in tomorrow so you should come<02:14:01.030> to<02:14:01.210> that<02:14:01.240> and<02:14:02.070> lastly<02:14:03.070> were<02:14:03.400> in<02:14:04.060> the 02:14:04.230 --> 02:14:04.240 align:start position:0% come to that and lastly were in the 02:14:04.240 --> 02:14:06.540 align:start position:0% come to that and lastly were in the final<02:14:04.540> stages<02:14:04.780> of<02:14:04.960> security<02:14:05.650> auditing<02:14:06.070> Lupita 02:14:06.540 --> 02:14:06.550 align:start position:0% final stages of security auditing Lupita 02:14:06.550 --> 02:14:09.120 align:start position:0% final stages of security auditing Lupita Pete<02:14:06.820> so<02:14:07.390> it<02:14:07.720> should<02:14:07.930> be<02:14:08.110> I<02:14:08.410> believe<02:14:08.920> it'll<02:14:09.010> be 02:14:09.120 --> 02:14:09.130 align:start position:0% Pete so it should be I believe it'll be 02:14:09.130 --> 02:14:11.430 align:start position:0% Pete so it should be I believe it'll be one<02:14:09.280> of<02:14:09.370> the<02:14:09.430> few<02:14:09.640> peer-to-peer<02:14:10.440> foundational 02:14:11.430 --> 02:14:11.440 align:start position:0% one of the few peer-to-peer foundational 02:14:11.440 --> 02:14:14.430 align:start position:0% one of the few peer-to-peer foundational layers<02:14:11.650> the<02:14:12.640> lilly<02:14:13.030> open<02:14:13.420> source<02:14:13.630> that<02:14:14.200> has<02:14:14.410> a 02:14:14.430 --> 02:14:14.440 align:start position:0% layers the lilly open source that has a 02:14:14.440 --> 02:14:16.680 align:start position:0% layers the lilly open source that has a public<02:14:14.980> security<02:14:15.340> audit<02:14:16.030> and<02:14:16.210> you<02:14:16.240> can<02:14:16.480> see 02:14:16.680 --> 02:14:16.690 align:start position:0% public security audit and you can see 02:14:16.690 --> 02:14:19.050 align:start position:0% public security audit and you can see where<02:14:17.290> our<02:14:17.740> vulnerabilities<02:14:18.490> are<02:14:18.670> what<02:14:18.940> we've 02:14:19.050 --> 02:14:19.060 align:start position:0% where our vulnerabilities are what we've 02:14:19.060 --> 02:14:22.650 align:start position:0% where our vulnerabilities are what we've done<02:14:19.210> about<02:14:19.360> them<02:14:19.830> as<02:14:20.830> some<02:14:21.310> i<02:14:21.700> think<02:14:22.030> is<02:14:22.300> f1 02:14:22.650 --> 02:14:22.660 align:start position:0% done about them as some i think is f1 02:14:22.660 --> 02:14:24.840 align:start position:0% done about them as some i think is f1 and<02:14:23.020> maybe<02:14:23.770> some<02:14:23.980> others<02:14:24.220> have<02:14:24.430> mentioned 02:14:24.840 --> 02:14:24.850 align:start position:0% and maybe some others have mentioned 02:14:24.850 --> 02:14:27.150 align:start position:0% and maybe some others have mentioned there<02:14:25.720> are<02:14:25.750> some<02:14:25.900> generic<02:14:26.410> attacks<02:14:26.770> against 02:14:27.150 --> 02:14:27.160 align:start position:0% there are some generic attacks against 02:14:27.160 --> 02:14:28.620 align:start position:0% there are some generic attacks against peer-to-peer<02:14:27.370> networks<02:14:27.880> that<02:14:28.030> are<02:14:28.060> very<02:14:28.360> very 02:14:28.620 --> 02:14:28.630 align:start position:0% peer-to-peer networks that are very very 02:14:28.630 --> 02:14:31.110 align:start position:0% peer-to-peer networks that are very very hard<02:14:28.840> to<02:14:29.530> mitigate<02:14:30.160> against<02:14:30.430> in<02:14:30.640> the<02:14:30.790> general 02:14:31.110 --> 02:14:31.120 align:start position:0% hard to mitigate against in the general 02:14:31.120 --> 02:14:34.530 align:start position:0% hard to mitigate against in the general case<02:14:31.420> like<02:14:32.260> eclipse<02:14:32.500> attacks<02:14:33.210> civil<02:14:34.210> attacks 02:14:34.530 --> 02:14:34.540 align:start position:0% case like eclipse attacks civil attacks 02:14:34.540 --> 02:14:37.290 align:start position:0% case like eclipse attacks civil attacks things<02:14:34.930> like<02:14:35.080> this<02:14:35.260> so<02:14:35.890> there's<02:14:36.370> a<02:14:36.460> kind<02:14:37.150> of<02:14:37.210> a 02:14:37.290 --> 02:14:37.300 align:start position:0% things like this so there's a kind of a 02:14:37.300 --> 02:14:41.100 align:start position:0% things like this so there's a kind of a mix<02:14:37.510> of<02:14:37.780> attacks<02:14:38.230> that<02:14:38.530> are<02:14:39.070> very<02:14:39.790> hard<02:14:40.090> in<02:14:40.930> the 02:14:41.100 --> 02:14:41.110 align:start position:0% mix of attacks that are very hard in the 02:14:41.110 --> 02:14:43.080 align:start position:0% mix of attacks that are very hard in the general<02:14:41.410> case<02:14:41.620> to<02:14:41.950> mitigate<02:14:42.490> against<02:14:42.910> and 02:14:43.080 --> 02:14:43.090 align:start position:0% general case to mitigate against and 02:14:43.090 --> 02:14:46.410 align:start position:0% general case to mitigate against and then<02:14:43.260> all<02:14:44.260> the<02:14:44.470> way<02:14:44.590> to<02:14:44.620> specific<02:14:45.610> codes<02:14:45.820> bugs 02:14:46.410 --> 02:14:46.420 align:start position:0% then all the way to specific codes bugs 02:14:46.420 --> 02:14:49.950 align:start position:0% then all the way to specific codes bugs in<02:14:46.600> our<02:14:46.780> code<02:14:47.080> that<02:14:47.350> we<02:14:47.530> have<02:14:48.150> patched<02:14:49.150> or<02:14:49.690> will 02:14:49.950 --> 02:14:49.960 align:start position:0% in our code that we have patched or will 02:14:49.960 --> 02:14:52.310 align:start position:0% in our code that we have patched or will patch<02:14:50.170> the<02:14:50.800> tongue<02:14:51.100> we<02:14:51.220> publish<02:14:51.850> the<02:14:51.970> report 02:14:52.310 --> 02:14:52.320 align:start position:0% patch the tongue we publish the report 02:14:52.320 --> 02:14:57.000 align:start position:0% patch the tongue we publish the report that's<02:14:53.320> coming<02:14:53.470> later<02:14:53.860> this<02:14:53.950> year<02:14:54.520> oh<02:14:55.680> yeah<02:14:56.680> so 02:14:57.000 --> 02:14:57.010 align:start position:0% that's coming later this year oh yeah so 02:14:57.010 --> 02:14:59.130 align:start position:0% that's coming later this year oh yeah so so<02:14:57.580> in<02:14:57.730> a<02:14:57.850> sense<02:14:58.090> we<02:14:58.330> like<02:14:58.510> to<02:14:58.630> describe<02:14:58.780> the 02:14:59.130 --> 02:14:59.140 align:start position:0% so in a sense we like to describe the 02:14:59.140 --> 02:15:01.530 align:start position:0% so in a sense we like to describe the PDB<02:14:59.530> as<02:14:59.620> a<02:14:59.650> modular<02:15:00.250> extensible<02:15:01.240> peer-to-peer 02:15:01.530 --> 02:15:01.540 align:start position:0% PDB as a modular extensible peer-to-peer 02:15:01.540 --> 02:15:04.640 align:start position:0% PDB as a modular extensible peer-to-peer networking<02:15:02.140> stack 02:15:04.640 --> 02:15:04.650 align:start position:0% 02:15:04.650 --> 02:15:07.000 align:start position:0% I<02:15:04.730> mentioned<02:15:05.730> earlier<02:15:06.090> that<02:15:06.150> we<02:15:06.480> have 02:15:07.000 --> 02:15:07.010 align:start position:0% I mentioned earlier that we have 02:15:07.010 --> 02:15:09.380 align:start position:0% I mentioned earlier that we have implementations<02:15:08.010> of<02:15:08.130> limb<02:15:08.340> p2p<02:15:08.730> in<02:15:08.910> multiple 02:15:09.380 --> 02:15:09.390 align:start position:0% implementations of limb p2p in multiple 02:15:09.390 --> 02:15:11.930 align:start position:0% implementations of limb p2p in multiple different<02:15:09.540> programming<02:15:10.140> languages<02:15:10.560> so<02:15:11.340> this 02:15:11.930 --> 02:15:11.940 align:start position:0% different programming languages so this 02:15:11.940 --> 02:15:13.430 align:start position:0% different programming languages so this came<02:15:12.150> about<02:15:12.360> largely<02:15:12.600> because<02:15:13.170> of<02:15:13.200> the 02:15:13.430 --> 02:15:13.440 align:start position:0% came about largely because of the 02:15:13.440 --> 02:15:17.990 align:start position:0% came about largely because of the etherium<02:15:13.860> 2.0<02:15:15.350> project<02:15:16.350> and<02:15:16.620> one<02:15:17.310> slip<02:15:17.580> p2p 02:15:17.990 --> 02:15:18.000 align:start position:0% etherium 2.0 project and one slip p2p 02:15:18.000 --> 02:15:20.180 align:start position:0% etherium 2.0 project and one slip p2p got<02:15:18.210> locked<02:15:18.480> into<02:15:18.690> the<02:15:18.930> specification<02:15:19.320> for 02:15:20.180 --> 02:15:20.190 align:start position:0% got locked into the specification for 02:15:20.190 --> 02:15:23.360 align:start position:0% got locked into the specification for how<02:15:21.080> aetherium<02:15:22.080> 2.0<02:15:22.590> nodes<02:15:22.860> are<02:15:23.070> going<02:15:23.250> to 02:15:23.360 --> 02:15:23.370 align:start position:0% how aetherium 2.0 nodes are going to 02:15:23.370 --> 02:15:25.550 align:start position:0% how aetherium 2.0 nodes are going to communicate<02:15:23.910> then<02:15:24.480> we<02:15:25.200> had<02:15:25.320> a<02:15:25.350> situation 02:15:25.550 --> 02:15:25.560 align:start position:0% communicate then we had a situation 02:15:25.560 --> 02:15:28.760 align:start position:0% communicate then we had a situation where<02:15:26.160> a<02:15:26.460> theory<02:15:26.970> of<02:15:27.030> 2.0<02:15:27.570> wanted<02:15:28.110> nodes<02:15:28.410> in 02:15:28.760 --> 02:15:28.770 align:start position:0% where a theory of 2.0 wanted nodes in 02:15:28.770 --> 02:15:31.430 align:start position:0% where a theory of 2.0 wanted nodes in many<02:15:29.040> different<02:15:29.310> programming<02:15:29.880> languages<02:15:30.480> and 02:15:31.430 --> 02:15:31.440 align:start position:0% many different programming languages and 02:15:31.440 --> 02:15:33.890 align:start position:0% many different programming languages and that<02:15:32.400> meant<02:15:32.730> that<02:15:32.790> we<02:15:33.000> needed<02:15:33.300> to<02:15:33.450> have<02:15:33.600> limb 02:15:33.890 --> 02:15:33.900 align:start position:0% that meant that we needed to have limb 02:15:33.900 --> 02:15:35.720 align:start position:0% that meant that we needed to have limb p2p<02:15:34.350> implementations<02:15:35.190> in<02:15:35.400> many<02:15:35.550> different 02:15:35.720 --> 02:15:35.730 align:start position:0% p2p implementations in many different 02:15:35.730 --> 02:15:38.600 align:start position:0% p2p implementations in many different programming<02:15:36.240> languages<02:15:36.600> and<02:15:37.140> so<02:15:37.740> some<02:15:38.310> of<02:15:38.460> the 02:15:38.600 --> 02:15:38.610 align:start position:0% programming languages and so some of the 02:15:38.610 --> 02:15:40.580 align:start position:0% programming languages and so some of the people<02:15:39.150> who<02:15:39.420> some<02:15:39.810> of<02:15:39.840> the<02:15:39.960> authors<02:15:40.290> of<02:15:40.320> those 02:15:40.580 --> 02:15:40.590 align:start position:0% people who some of the authors of those 02:15:40.590 --> 02:15:43.430 align:start position:0% people who some of the authors of those are<02:15:40.770> in<02:15:40.860> this<02:15:40.980> room<02:15:41.390> some<02:15:42.390> of<02:15:42.450> those<02:15:42.660> are<02:15:42.840> some 02:15:43.430 --> 02:15:43.440 align:start position:0% are in this room some of those are some 02:15:43.440 --> 02:15:46.460 align:start position:0% are in this room some of those are some of<02:15:43.590> the<02:15:43.680> more<02:15:43.860> advanced<02:15:44.280> folks<02:15:44.840> I<02:15:45.840> think 02:15:46.460 --> 02:15:46.470 align:start position:0% of the more advanced folks I think 02:15:46.470 --> 02:15:47.750 align:start position:0% of the more advanced folks I think probably<02:15:46.680> all<02:15:46.950> of<02:15:46.980> them<02:15:47.250> are<02:15:47.460> at<02:15:47.580> this 02:15:47.750 --> 02:15:47.760 align:start position:0% probably all of them are at this 02:15:47.760 --> 02:15:49.610 align:start position:0% probably all of them are at this conference<02:15:47.970> somewhere<02:15:48.870> so<02:15:49.050> you<02:15:49.080> can 02:15:49.610 --> 02:15:49.620 align:start position:0% conference somewhere so you can 02:15:49.620 --> 02:15:51.590 align:start position:0% conference somewhere so you can certainly<02:15:49.950> feel<02:15:50.550> have<02:15:50.730> opportunities<02:15:51.360> to<02:15:51.390> run 02:15:51.590 --> 02:15:51.600 align:start position:0% certainly feel have opportunities to run 02:15:51.600 --> 02:15:55.070 align:start position:0% certainly feel have opportunities to run into<02:15:51.900> them<02:15:52.050> but<02:15:52.380> in<02:15:53.340> the<02:15:53.490> beginning<02:15:53.790> was<02:15:54.750> jazz 02:15:55.070 --> 02:15:55.080 align:start position:0% into them but in the beginning was jazz 02:15:55.080 --> 02:15:57.260 align:start position:0% into them but in the beginning was jazz flip<02:15:55.410> p2p<02:15:55.830> and<02:15:56.010> go<02:15:56.220> lucky<02:15:56.610> to<02:15:56.700> be<02:15:56.850> those<02:15:57.090> are 02:15:57.260 --> 02:15:57.270 align:start position:0% flip p2p and go lucky to be those are 02:15:57.270 --> 02:16:00.200 align:start position:0% flip p2p and go lucky to be those are the<02:15:57.360> first<02:15:57.540> two<02:15:57.720> implementations<02:15:58.760> rust<02:15:59.760> that 02:16:00.200 --> 02:16:00.210 align:start position:0% the first two implementations rust that 02:16:00.210 --> 02:16:01.640 align:start position:0% the first two implementations rust that came<02:16:00.450> along<02:16:00.690> that<02:16:00.750> was<02:16:01.020> developed<02:16:01.500> by<02:16:01.620> the 02:16:01.640 --> 02:16:01.650 align:start position:0% came along that was developed by the 02:16:01.650 --> 02:16:04.730 align:start position:0% came along that was developed by the folks<02:16:01.920> of<02:16:02.100> Paradis<02:16:02.520> and<02:16:03.150> then<02:16:03.750> since<02:16:04.560> then 02:16:04.730 --> 02:16:04.740 align:start position:0% folks of Paradis and then since then 02:16:04.740 --> 02:16:06.170 align:start position:0% folks of Paradis and then since then we've<02:16:04.920> had<02:16:04.950> four<02:16:05.520> new<02:16:05.760> language 02:16:06.170 --> 02:16:06.180 align:start position:0% we've had four new language 02:16:06.180 --> 02:16:09.740 align:start position:0% we've had four new language implementations<02:16:06.960> of<02:16:07.110> Lippe<02:16:07.410> 2p<02:16:07.680> and<02:16:08.750> we're 02:16:09.740 --> 02:16:09.750 align:start position:0% implementations of Lippe 2p and we're 02:16:09.750 --> 02:16:12.220 align:start position:0% implementations of Lippe 2p and we're really<02:16:09.930> excited<02:16:10.140> to<02:16:10.710> have<02:16:10.740> so<02:16:11.250> many<02:16:11.430> different 02:16:12.220 --> 02:16:12.230 align:start position:0% really excited to have so many different 02:16:12.230 --> 02:16:14.630 align:start position:0% really excited to have so many different interoperable<02:16:13.230> programming<02:16:13.800> languages<02:16:14.310> all 02:16:14.630 --> 02:16:14.640 align:start position:0% interoperable programming languages all 02:16:14.640 --> 02:16:17.500 align:start position:0% interoperable programming languages all implementing<02:16:15.480> the<02:16:15.600> same<02:16:15.840> live<02:16:16.560> p2p 02:16:17.500 --> 02:16:17.510 align:start position:0% implementing the same live p2p 02:16:17.510 --> 02:16:21.280 align:start position:0% implementing the same live p2p specifications<02:16:18.510> I<02:16:19.400> have<02:16:20.400> a<02:16:20.460> little<02:16:20.700> bit<02:16:20.850> here 02:16:21.280 --> 02:16:21.290 align:start position:0% specifications I have a little bit here 02:16:21.290 --> 02:16:24.910 align:start position:0% specifications I have a little bit here it's<02:16:22.290> give<02:16:22.440> them<02:16:22.530> through<02:16:22.740> this<02:16:22.950> but<02:16:23.280> just<02:16:23.630> the 02:16:24.910 --> 02:16:24.920 align:start position:0% it's give them through this but just the 02:16:24.920 --> 02:16:27.350 align:start position:0% it's give them through this but just the kind<02:16:25.920> of<02:16:25.950> the<02:16:26.040> most<02:16:26.220> mature<02:16:26.430> implementations 02:16:27.350 --> 02:16:27.360 align:start position:0% kind of the most mature implementations 02:16:27.360 --> 02:16:30.290 align:start position:0% kind of the most mature implementations right<02:16:27.600> now<02:16:27.810> rjs<02:16:28.770> go<02:16:29.430> and<02:16:29.610> rust<02:16:29.850> they<02:16:30.090> have<02:16:30.210> the 02:16:30.290 --> 02:16:30.300 align:start position:0% right now rjs go and rust they have the 02:16:30.300 --> 02:16:33.260 align:start position:0% right now rjs go and rust they have the most<02:16:30.510> features<02:16:30.980> we<02:16:31.980> often<02:16:32.340> treat<02:16:32.580> goes<02:16:32.880> sort 02:16:33.260 --> 02:16:33.270 align:start position:0% most features we often treat goes sort 02:16:33.270 --> 02:16:35.300 align:start position:0% most features we often treat goes sort of<02:16:33.330> the<02:16:33.450> reference<02:16:33.990> implementation<02:16:34.310> we're 02:16:35.300 --> 02:16:35.310 align:start position:0% of the reference implementation we're 02:16:35.310 --> 02:16:37.190 align:start position:0% of the reference implementation we're trying<02:16:35.490> to<02:16:35.550> move<02:16:35.730> away<02:16:35.910> from<02:16:36.090> that<02:16:36.390> and<02:16:36.929> toward 02:16:37.190 --> 02:16:37.200 align:start position:0% trying to move away from that and toward 02:16:37.200 --> 02:16:40.340 align:start position:0% trying to move away from that and toward a<02:16:37.320> model<02:16:37.500> where<02:16:37.980> limb<02:16:38.550> p2p<02:16:39.000> is<02:16:39.030> spec<02:16:39.510> first<02:16:39.870> so 02:16:40.340 --> 02:16:40.350 align:start position:0% a model where limb p2p is spec first so 02:16:40.350 --> 02:16:43.669 align:start position:0% a model where limb p2p is spec first so lip<02:16:40.860> AP<02:16:41.219> itself<02:16:41.580> would<02:16:42.240> really<02:16:42.510> be<02:16:42.840> a<02:16:43.080> specimen 02:16:43.669 --> 02:16:43.679 align:start position:0% lip AP itself would really be a specimen 02:16:43.679 --> 02:16:46.340 align:start position:0% lip AP itself would really be a specimen not<02:16:43.890> a<02:16:43.920> not<02:16:44.429> a<02:16:44.730> library<02:16:45.300> but<02:16:45.750> a<02:16:45.780> specification 02:16:46.340 --> 02:16:46.350 align:start position:0% not a not a library but a specification 02:16:46.350 --> 02:16:50.030 align:start position:0% not a not a library but a specification for<02:16:46.800> creating<02:16:47.400> a<02:16:47.700> library<02:16:48.030> in<02:16:48.900> a<02:16:49.170> language<02:16:49.740> or 02:16:50.030 --> 02:16:50.040 align:start position:0% for creating a library in a language or 02:16:50.040 --> 02:16:52.419 align:start position:0% for creating a library in a language or on<02:16:50.250> any<02:16:50.550> device<02:16:51.000> or<02:16:51.240> platform<02:16:51.390> that<02:16:51.870> you<02:16:51.960> want 02:16:52.419 --> 02:16:52.429 align:start position:0% on any device or platform that you want 02:16:52.429 --> 02:16:55.940 align:start position:0% on any device or platform that you want to<02:16:53.429> implement<02:16:54.140> peer-to-peer<02:16:55.140> functionality 02:16:55.940 --> 02:16:55.950 align:start position:0% to implement peer-to-peer functionality 02:16:55.950 --> 02:16:57.500 align:start position:0% to implement peer-to-peer functionality and<02:16:56.280> then<02:16:56.670> these<02:16:56.880> are<02:16:56.940> some<02:16:57.060> of<02:16:57.300> the<02:16:57.390> new 02:16:57.500 --> 02:16:57.510 align:start position:0% and then these are some of the new 02:16:57.510 --> 02:16:58.009 align:start position:0% and then these are some of the new relying 02:16:58.009 --> 02:16:58.019 align:start position:0% relying 02:16:58.019 --> 02:17:00.620 align:start position:0% relying as<02:16:58.139> I<02:16:58.710> showed<02:16:59.519> this<02:16:59.729> on<02:16:59.909> the<02:17:00.000> previous<02:17:00.359> slide 02:17:00.620 --> 02:17:00.630 align:start position:0% as I showed this on the previous slide 02:17:00.630 --> 02:17:03.830 align:start position:0% as I showed this on the previous slide but<02:17:01.439> they're<02:17:02.099> they're<02:17:02.699> coming<02:17:03.090> along 02:17:03.830 --> 02:17:03.840 align:start position:0% but they're they're coming along 02:17:03.840 --> 02:17:06.469 align:start position:0% but they're they're coming along each<02:17:04.170> one<02:17:04.500> is<02:17:04.710> releasing<02:17:05.069> on<02:17:05.369> its<02:17:05.550> own<02:17:05.729> early 02:17:06.469 --> 02:17:06.479 align:start position:0% each one is releasing on its own early 02:17:06.479 --> 02:17:10.879 align:start position:0% each one is releasing on its own early cycle<02:17:06.779> and<02:17:08.239> and<02:17:09.239> they're<02:17:09.840> all<02:17:09.989> making<02:17:10.590> good 02:17:10.879 --> 02:17:10.889 align:start position:0% cycle and and they're all making good 02:17:10.889 --> 02:17:13.549 align:start position:0% cycle and and they're all making good progress<02:17:11.840> now<02:17:12.840> I<02:17:12.869> just<02:17:12.989> want<02:17:13.289> to<02:17:13.319> talk<02:17:13.469> a 02:17:13.549 --> 02:17:13.559 align:start position:0% progress now I just want to talk a 02:17:13.559 --> 02:17:15.500 align:start position:0% progress now I just want to talk a little<02:17:13.739> bit<02:17:13.889> about<02:17:13.920> what's<02:17:14.639> coming<02:17:14.849> next<02:17:15.059> in 02:17:15.500 --> 02:17:15.510 align:start position:0% little bit about what's coming next in 02:17:15.510 --> 02:17:18.080 align:start position:0% little bit about what's coming next in Limpy<02:17:15.989> tepee<02:17:16.260> we<02:17:17.099> have<02:17:17.250> a<02:17:17.279> lot<02:17:17.519> of<02:17:17.550> things<02:17:17.880> that 02:17:18.080 --> 02:17:18.090 align:start position:0% Limpy tepee we have a lot of things that 02:17:18.090 --> 02:17:19.509 align:start position:0% Limpy tepee we have a lot of things that we're<02:17:18.210> working<02:17:18.239> on<02:17:18.599> in<02:17:18.750> the<02:17:18.840> project 02:17:19.509 --> 02:17:19.519 align:start position:0% we're working on in the project 02:17:19.519 --> 02:17:23.269 align:start position:0% we're working on in the project so<02:17:20.519> I<02:17:20.819> mentioned<02:17:21.319> the<02:17:22.319> new<02:17:22.469> languages<02:17:22.949> are<02:17:23.159> at 02:17:23.269 --> 02:17:23.279 align:start position:0% so I mentioned the new languages are at 02:17:23.279 --> 02:17:26.059 align:start position:0% so I mentioned the new languages are at varying<02:17:23.609> levels<02:17:23.670> of<02:17:24.090> maturity<02:17:24.800> we<02:17:25.800> had<02:17:25.949> to 02:17:26.059 --> 02:17:26.069 align:start position:0% varying levels of maturity we had to 02:17:26.069 --> 02:17:28.160 align:start position:0% varying levels of maturity we had to mean<02:17:26.219> a<02:17:26.250> minimum<02:17:26.760> or<02:17:26.939> sorry<02:17:27.359> the<02:17:27.569> implementers 02:17:28.160 --> 02:17:28.170 align:start position:0% mean a minimum or sorry the implementers 02:17:28.170 --> 02:17:31.729 align:start position:0% mean a minimum or sorry the implementers of<02:17:28.460> each<02:17:29.460> language<02:17:29.849> had<02:17:30.510> to<02:17:30.659> meet<02:17:30.899> a<02:17:31.229> minimum 02:17:31.729 --> 02:17:31.739 align:start position:0% of each language had to meet a minimum 02:17:31.739 --> 02:17:34.419 align:start position:0% of each language had to meet a minimum set<02:17:32.279> of<02:17:32.369> requirements<02:17:32.760> okay<02:17:33.389> one<02:17:33.569> minute 02:17:34.419 --> 02:17:34.429 align:start position:0% set of requirements okay one minute 02:17:34.429 --> 02:17:37.219 align:start position:0% set of requirements okay one minute minimum<02:17:35.429> set<02:17:35.579> of<02:17:35.639> requirements<02:17:36.000> for<02:17:36.449> each<02:17:36.599> 2.0 02:17:37.219 --> 02:17:37.229 align:start position:0% minimum set of requirements for each 2.0 02:17:37.229 --> 02:17:39.319 align:start position:0% minimum set of requirements for each 2.0 now<02:17:37.260> we're<02:17:37.710> trying<02:17:37.949> to<02:17:38.039> build<02:17:38.189> up<02:17:38.519> on<02:17:38.849> top<02:17:39.000> of 02:17:39.319 --> 02:17:39.329 align:start position:0% now we're trying to build up on top of 02:17:39.329 --> 02:17:43.189 align:start position:0% now we're trying to build up on top of that<02:17:39.510> and<02:17:39.869> enhance<02:17:40.139> that<02:17:41.210> testing<02:17:42.210> and<02:17:42.449> a 02:17:43.189 --> 02:17:43.199 align:start position:0% that and enhance that testing and a 02:17:43.199 --> 02:17:45.080 align:start position:0% that and enhance that testing and a visualization<02:17:44.069> of<02:17:44.219> distributed<02:17:44.729> systems<02:17:45.000> is 02:17:45.080 --> 02:17:45.090 align:start position:0% visualization of distributed systems is 02:17:45.090 --> 02:17:47.719 align:start position:0% visualization of distributed systems is a<02:17:45.119> really<02:17:45.630> really<02:17:45.750> hard<02:17:45.929> problem<02:17:46.429> it<02:17:47.429> doesn't 02:17:47.719 --> 02:17:47.729 align:start position:0% a really really hard problem it doesn't 02:17:47.729 --> 02:17:48.859 align:start position:0% a really really hard problem it doesn't matter<02:17:47.880> whether<02:17:48.119> they're<02:17:48.359> create<02:17:48.569> a<02:17:48.599> peer<02:17:48.840> or 02:17:48.859 --> 02:17:48.869 align:start position:0% matter whether they're create a peer or 02:17:48.869 --> 02:17:51.139 align:start position:0% matter whether they're create a peer or or<02:17:49.170> or<02:17:49.529> or<02:17:49.800> centralized<02:17:50.309> it's<02:17:50.639> still<02:17:50.880> a<02:17:50.909> hard 02:17:51.139 --> 02:17:51.149 align:start position:0% or or or centralized it's still a hard 02:17:51.149 --> 02:17:53.000 align:start position:0% or or or centralized it's still a hard problem<02:17:51.359> but<02:17:51.899> it's<02:17:52.050> particularly<02:17:52.469> hard<02:17:52.829> at 02:17:53.000 --> 02:17:53.010 align:start position:0% problem but it's particularly hard at 02:17:53.010 --> 02:17:55.639 align:start position:0% problem but it's particularly hard at your<02:17:53.159> computer<02:17:53.550> so<02:17:54.119> both<02:17:54.750> it's<02:17:54.929> 2<02:17:55.050> &<02:17:55.170> 4<02:17:55.349> there 02:17:55.639 --> 02:17:55.649 align:start position:0% your computer so both it's 2 & 4 there 02:17:55.649 --> 02:17:57.379 align:start position:0% your computer so both it's 2 & 4 there what<02:17:56.069> we're<02:17:56.189> focusing<02:17:56.639> on<02:17:56.789> in<02:17:57.000> terms<02:17:57.210> of 02:17:57.379 --> 02:17:57.389 align:start position:0% what we're focusing on in terms of 02:17:57.389 --> 02:18:00.799 align:start position:0% what we're focusing on in terms of trying<02:17:57.659> to<02:17:57.779> make<02:17:58.019> the<02:17:58.260> system<02:17:59.010> less<02:17:59.340> okay<02:17:59.809> spec 02:18:00.799 --> 02:18:00.809 align:start position:0% trying to make the system less okay spec 02:18:00.809 --> 02:18:02.479 align:start position:0% trying to make the system less okay spec first<02:18:01.109> I<02:18:01.319> mentioned<02:18:01.739> we<02:18:01.979> also<02:18:02.159> want<02:18:02.429> to 02:18:02.479 --> 02:18:02.489 align:start position:0% first I mentioned we also want to 02:18:02.489 --> 02:18:04.759 align:start position:0% first I mentioned we also want to improve<02:18:02.609> documentation<02:18:03.119> and<02:18:04.019> we<02:18:04.590> have<02:18:04.739> a 02:18:04.759 --> 02:18:04.769 align:start position:0% improve documentation and we have a 02:18:04.769 --> 02:18:07.219 align:start position:0% improve documentation and we have a variety<02:18:05.159> of<02:18:05.399> features<02:18:05.699> that<02:18:05.909> we<02:18:06.779> want<02:18:06.989> to<02:18:07.050> add 02:18:07.219 --> 02:18:07.229 align:start position:0% variety of features that we want to add 02:18:07.229 --> 02:18:09.620 align:start position:0% variety of features that we want to add I<02:18:07.590> will<02:18:08.279> not<02:18:08.579> go<02:18:08.729> into<02:18:08.849> but<02:18:09.149> I<02:18:09.179> think<02:18:09.449> you'll 02:18:09.620 --> 02:18:09.630 align:start position:0% I will not go into but I think you'll 02:18:09.630 --> 02:18:12.469 align:start position:0% I will not go into but I think you'll hear<02:18:09.840> more<02:18:10.170> about<02:18:10.229> that<02:18:10.469> from<02:18:10.679> role<02:18:11.279> so<02:18:12.239> here 02:18:12.469 --> 02:18:12.479 align:start position:0% hear more about that from role so here 02:18:12.479 --> 02:18:14.059 align:start position:0% hear more about that from role so here are<02:18:12.569> the<02:18:12.689> two<02:18:12.869> talks<02:18:13.109> I<02:18:13.319> mentioned<02:18:13.769> this<02:18:13.889> is 02:18:14.059 --> 02:18:14.069 align:start position:0% are the two talks I mentioned this is 02:18:14.069 --> 02:18:16.819 align:start position:0% are the two talks I mentioned this is the<02:18:14.250> my<02:18:14.399> plug<02:18:14.639> for<02:18:14.939> roles<02:18:15.599> to<02:18:15.840> talks<02:18:16.139> one<02:18:16.710> of 02:18:16.819 --> 02:18:16.829 align:start position:0% the my plug for roles to talks one of 02:18:16.829 --> 02:18:18.469 align:start position:0% the my plug for roles to talks one of them<02:18:16.949> is<02:18:17.069> coming<02:18:17.250> up<02:18:17.429> in<02:18:17.579> two<02:18:17.699> hours<02:18:17.729> you 02:18:18.469 --> 02:18:18.479 align:start position:0% them is coming up in two hours you 02:18:18.479 --> 02:18:20.259 align:start position:0% them is coming up in two hours you should<02:18:18.510> absolutely<02:18:18.899> go<02:18:19.260> to<02:18:19.289> it<02:18:19.559> it's<02:18:19.769> indeed 02:18:20.259 --> 02:18:20.269 align:start position:0% should absolutely go to it it's indeed 02:18:20.269 --> 02:18:23.689 align:start position:0% should absolutely go to it it's indeed it's<02:18:21.269> and<02:18:22.229> then<02:18:22.559> the<02:18:22.679> second<02:18:23.039> one<02:18:23.309> the<02:18:23.519> more 02:18:23.689 --> 02:18:23.699 align:start position:0% it's and then the second one the more 02:18:23.699 --> 02:18:25.639 align:start position:0% it's and then the second one the more advanced<02:18:24.000> one<02:18:24.300> that<02:18:24.449> focuses<02:18:24.840> on<02:18:24.960> gossip<02:18:25.409> sub 02:18:25.639 --> 02:18:25.649 align:start position:0% advanced one that focuses on gossip sub 02:18:25.649 --> 02:18:31.459 align:start position:0% advanced one that focuses on gossip sub will<02:18:26.219> be<02:18:26.489> tomorrow<02:18:27.359> at<02:18:28.219> 1455<02:18:29.250> in<02:18:29.609> v10<02:18:30.469> check 02:18:31.459 --> 02:18:31.469 align:start position:0% will be tomorrow at 1455 in v10 check 02:18:31.469 --> 02:18:33.349 align:start position:0% will be tomorrow at 1455 in v10 check the<02:18:31.649> schedule<02:18:32.010> this<02:18:32.670> is<02:18:32.729> from<02:18:33.029> the<02:18:33.119> official 02:18:33.349 --> 02:18:33.359 align:start position:0% the schedule this is from the official 02:18:33.359 --> 02:18:35.569 align:start position:0% the schedule this is from the official DEFCON<02:18:34.139> scheduled<02:18:34.559> but<02:18:34.769> if<02:18:34.889> design<02:18:35.189> changes 02:18:35.569 --> 02:18:35.579 align:start position:0% DEFCON scheduled but if design changes 02:18:35.579 --> 02:18:44.260 align:start position:0% DEFCON scheduled but if design changes will<02:18:36.239> be<02:18:36.359> on<02:18:36.479> there<02:18:36.659> Wow<02:18:36.779> all<02:18:37.409> right 02:18:44.260 --> 02:18:44.270 align:start position:0% 02:18:44.270 --> 02:18:46.600 align:start position:0% as<02:18:44.690> their<02:18:44.870> question<02:18:45.230> time<02:18:45.410> worship<02:18:45.710> is<02:18:46.160> just 02:18:46.600 --> 02:18:46.610 align:start position:0% as their question time worship is just 02:18:46.610 --> 02:18:47.590 align:start position:0% as their question time worship is just delicious 02:18:47.590 --> 02:18:47.600 align:start position:0% delicious 02:18:47.600 --> 02:18:50.410 align:start position:0% delicious okay<02:18:48.080> ghetto<02:18:48.890> so<02:18:49.280> do<02:18:49.490> you<02:18:49.550> think<02:18:49.580> the<02:18:50.150> other 02:18:50.410 --> 02:18:50.420 align:start position:0% okay ghetto so do you think the other 02:18:50.420 --> 02:18:52.210 align:start position:0% okay ghetto so do you think the other pyramid<02:18:50.810> not<02:18:50.900> even<02:18:51.170> sees<02:18:51.320> that<02:18:51.500> you<02:18:51.650> want<02:18:52.040> to 02:18:52.210 --> 02:18:52.220 align:start position:0% pyramid not even sees that you want to 02:18:52.220 --> 02:18:55.120 align:start position:0% pyramid not even sees that you want to be<02:18:52.910> oh<02:18:53.090> yes<02:18:53.570> we're<02:18:53.870> this<02:18:54.320> is<02:18:54.380> a<02:18:54.500> subject<02:18:54.830> we're 02:18:55.120 --> 02:18:55.130 align:start position:0% be oh yes we're this is a subject we're 02:18:55.130 --> 02:18:59.490 align:start position:0% be oh yes we're this is a subject we're very<02:18:55.310> interested<02:18:55.580> in<02:18:55.940> an<02:18:56.480> anonymous<02:18:56.840> DST 02:18:59.490 --> 02:18:59.500 align:start position:0% very interested in an anonymous DST 02:18:59.500 --> 02:19:03.940 align:start position:0% very interested in an anonymous DST privacy<02:19:00.500> issues<02:19:00.890> yes<02:19:01.730> sir<02:19:01.970> I<02:19:02.900> wouldn't<02:19:03.800> say 02:19:03.940 --> 02:19:03.950 align:start position:0% privacy issues yes sir I wouldn't say 02:19:03.950 --> 02:19:06.280 align:start position:0% privacy issues yes sir I wouldn't say that<02:19:04.100> we've<02:19:04.220> solved<02:19:04.670> it<02:19:04.760> yet<02:19:05.000> it's<02:19:05.360> uh<02:19:05.480> it's<02:19:06.170> a 02:19:06.280 --> 02:19:06.290 align:start position:0% that we've solved it yet it's uh it's a 02:19:06.290 --> 02:19:08.820 align:start position:0% that we've solved it yet it's uh it's a subject<02:19:06.650> of<02:19:06.740> interest<02:19:07.240> so<02:19:08.240> there's<02:19:08.480> a 02:19:08.820 --> 02:19:08.830 align:start position:0% subject of interest so there's a 02:19:08.830 --> 02:19:14.350 align:start position:0% subject of interest so there's a proposal<02:19:11.260> and<02:19:12.260> it's<02:19:13.160> basically<02:19:13.790> using<02:19:14.240> my 02:19:14.350 --> 02:19:14.360 align:start position:0% proposal and it's basically using my 02:19:14.360 --> 02:19:17.170 align:start position:0% proposal and it's basically using my morality<02:19:14.720> to<02:19:14.870> climb<02:19:15.110> on<02:19:15.500> the<02:19:15.560> TCP<02:19:16.010> layer<02:19:16.040> yes<02:19:17.000> I 02:19:17.170 --> 02:19:17.180 align:start position:0% morality to climb on the TCP layer yes I 02:19:17.180 --> 02:19:19.990 align:start position:0% morality to climb on the TCP layer yes I have<02:19:17.420> seen<02:19:17.630> this<02:19:17.810> of<02:19:18.050> a<02:19:18.500> new<02:19:18.680> space<02:19:19.010> well<02:19:19.610> yeah 02:19:19.990 --> 02:19:20.000 align:start position:0% have seen this of a new space well yeah 02:19:20.000 --> 02:19:22.510 align:start position:0% have seen this of a new space well yeah yeah<02:19:20.800> there<02:19:21.800> are<02:19:21.890> a<02:19:21.920> lot<02:19:22.100> of<02:19:22.130> different 02:19:22.510 --> 02:19:22.520 align:start position:0% yeah there are a lot of different 02:19:22.520 --> 02:19:24.130 align:start position:0% yeah there are a lot of different approaches<02:19:22.850> to<02:19:22.940> to<02:19:23.300> achieve<02:19:23.570> this<02:19:23.720> end<02:19:23.900> yeah 02:19:24.130 --> 02:19:24.140 align:start position:0% approaches to to achieve this end yeah 02:19:24.140 --> 02:19:40.870 align:start position:0% approaches to to achieve this end yeah we<02:19:24.770> would<02:19:24.920> like<02:19:25.070> this<02:19:35.020> are<02:19:38.980> either<02:19:39.980> broken<02:19:40.610> or 02:19:40.870 --> 02:19:40.880 align:start position:0% we would like this are either broken or 02:19:40.880 --> 02:19:43.240 align:start position:0% we would like this are either broken or easily<02:19:41.390> as<02:19:41.480> I<02:19:41.600> go<02:19:41.810> by<02:19:41.960> even<02:19:42.560> moderate<02:19:43.010> in<02:19:43.100> size 02:19:43.240 --> 02:19:43.250 align:start position:0% easily as I go by even moderate in size 02:19:43.250 --> 02:19:45.850 align:start position:0% easily as I go by even moderate in size nation<02:19:43.640> states<02:19:43.820> so<02:19:44.660> not<02:19:44.810> actually<02:19:45.080> there<02:19:45.350> so 02:19:45.850 --> 02:19:45.860 align:start position:0% nation states so not actually there so 02:19:45.860 --> 02:19:47.800 align:start position:0% nation states so not actually there so Billy's<02:19:46.160> building<02:19:46.850> must<02:19:47.030> work<02:19:47.180> those<02:19:47.390> systems 02:19:47.800 --> 02:19:47.810 align:start position:0% Billy's building must work those systems 02:19:47.810 --> 02:19:49.900 align:start position:0% Billy's building must work those systems are<02:19:47.960> deep<02:19:48.140> those<02:19:48.350> right<02:19:48.590> Mountain<02:19:49.010> foreign 02:19:49.900 --> 02:19:49.910 align:start position:0% are deep those right Mountain foreign 02:19:49.910 --> 02:19:54.131 align:start position:0% are deep those right Mountain foreign fighters<02:19:50.240> helping 02:19:54.131 --> 02:19:54.141 align:start position:0% 02:19:54.141 --> 02:19:57.791 align:start position:0% but<02:19:55.070> for<02:19:55.190> now<02:19:55.280> like<02:19:56.500> because<02:19:57.500> the<02:19:57.591> thing<02:19:57.771> is 02:19:57.791 --> 02:19:57.801 align:start position:0% but for now like because the thing is 02:19:57.801 --> 02:19:59.650 align:start position:0% but for now like because the thing is you<02:19:58.490> gotta<02:19:58.670> you<02:19:59.030> gotta<02:19:59.181> figure<02:19:59.330> out<02:19:59.450> which 02:19:59.650 --> 02:19:59.660 align:start position:0% you gotta you gotta figure out which 02:19:59.660 --> 02:20:01.270 align:start position:0% you gotta you gotta figure out which Frenchman<02:20:00.110> can<02:20:00.200> use<02:20:00.351> let's<02:20:00.681> manage<02:20:00.950> making<02:20:01.250> a 02:20:01.270 --> 02:20:01.280 align:start position:0% Frenchman can use let's manage making a 02:20:01.280 --> 02:20:05.200 align:start position:0% Frenchman can use let's manage making a privacy<02:20:01.641> or<02:20:01.730> a<02:20:01.761> that<02:20:03.160> but<02:20:04.160> you<02:20:04.670> in<02:20:04.761> a<02:20:04.790> fuse<02:20:05.000> or 02:20:05.200 --> 02:20:05.210 align:start position:0% privacy or a that but you in a fuse or 02:20:05.210 --> 02:20:09.791 align:start position:0% privacy or a that but you in a fuse or be<02:20:05.931> aware<02:20:06.110> look<02:20:06.351> like<02:20:06.471> probably<02:20:08.681> thank<02:20:09.681> you 02:20:09.791 --> 02:20:09.801 align:start position:0% be aware look like probably thank you 02:20:09.801 --> 02:20:11.501 align:start position:0% be aware look like probably thank you yeah<02:20:10.551> I<02:20:10.580> think<02:20:10.761> that's<02:20:10.971> a<02:20:11.061> really<02:20:11.271> good<02:20:11.360> at 02:20:11.501 --> 02:20:11.511 align:start position:0% yeah I think that's a really good at 02:20:11.511 --> 02:20:14.910 align:start position:0% yeah I think that's a really good at demo<02:20:11.690> okay<02:20:12.110> thank<02:20:12.351> you<02:20:12.410> for<02:20:12.500> your<02:20:12.620> time 02:20:14.910 --> 02:20:14.920 align:start position:0% 02:20:14.920 --> 02:20:17.740 align:start position:0% everybody<02:20:15.920> I'm<02:20:16.400> Molly<02:20:16.670> I'm<02:20:16.940> the<02:20:17.120> best<02:20:17.450> project 02:20:17.740 --> 02:20:17.750 align:start position:0% everybody I'm Molly I'm the best project 02:20:17.750 --> 02:20:19.180 align:start position:0% everybody I'm Molly I'm the best project week<02:20:17.900> and<02:20:18.380> I've<02:20:18.471> been<02:20:18.591> talking<02:20:18.801> to<02:20:18.860> a<02:20:18.920> little 02:20:19.180 --> 02:20:19.190 align:start position:0% week and I've been talking to a little 02:20:19.190 --> 02:20:20.770 align:start position:0% week and I've been talking to a little bit<02:20:19.311> about<02:20:19.490> ecosystem<02:20:20.061> growth<02:20:20.271> and<02:20:20.420> an<02:20:20.480> option 02:20:20.770 --> 02:20:20.780 align:start position:0% bit about ecosystem growth and an option 02:20:20.780 --> 02:20:22.570 align:start position:0% bit about ecosystem growth and an option my<02:20:21.261> slides<02:20:21.500> are<02:20:21.681> definitely<02:20:22.101> longer<02:20:22.341> than 02:20:22.570 --> 02:20:22.580 align:start position:0% my slides are definitely longer than 02:20:22.580 --> 02:20:24.280 align:start position:0% my slides are definitely longer than Mike's<02:20:22.790> so<02:20:23.091> I'm<02:20:23.181> gonna<02:20:23.271> go<02:20:23.420> real<02:20:23.721> fast<02:20:23.931> through 02:20:24.280 --> 02:20:24.290 align:start position:0% Mike's so I'm gonna go real fast through 02:20:24.290 --> 02:20:25.751 align:start position:0% Mike's so I'm gonna go real fast through some<02:20:24.500> of<02:20:24.620> these<02:20:24.740> examples<02:20:24.801> to<02:20:25.400> try<02:20:25.521> and<02:20:25.641> get 02:20:25.751 --> 02:20:25.761 align:start position:0% some of these examples to try and get 02:20:25.761 --> 02:20:28.030 align:start position:0% some of these examples to try and get this<02:20:25.851> up<02:20:26.000> but<02:20:26.570> if<02:20:26.780> I<02:20:26.900> don't<02:20:27.170> come<02:20:27.681> back<02:20:27.830> to<02:20:27.950> me 02:20:28.030 --> 02:20:28.040 align:start position:0% this up but if I don't come back to me 02:20:28.040 --> 02:20:29.200 align:start position:0% this up but if I don't come back to me afterward<02:20:28.341> for<02:20:28.521> where<02:20:28.761> we're<02:20:28.910> heading<02:20:29.181> next 02:20:29.200 --> 02:20:29.210 align:start position:0% afterward for where we're heading next 02:20:29.210 --> 02:20:30.970 align:start position:0% afterward for where we're heading next that's<02:20:29.900> the<02:20:30.021> part<02:20:30.230> that<02:20:30.261> moment<02:20:30.561> that<02:20:30.650> missing 02:20:30.970 --> 02:20:30.980 align:start position:0% that's the part that moment that missing 02:20:30.980 --> 02:20:33.100 align:start position:0% that's the part that moment that missing if<02:20:31.130> I<02:20:31.280> haven't<02:20:31.431> gonna<02:20:31.610> cut<02:20:31.790> off<02:20:31.880> so<02:20:32.420> feel<02:20:33.080> free 02:20:33.100 --> 02:20:33.110 align:start position:0% if I haven't gonna cut off so feel free 02:20:33.110 --> 02:20:36.761 align:start position:0% if I haven't gonna cut off so feel free to<02:20:33.230> chat<02:20:33.380> to<02:20:33.500> me<02:20:33.940> quickly<02:20:34.940> what<02:20:35.721> is<02:20:35.841> ipfs<02:20:36.380> it's 02:20:36.761 --> 02:20:36.771 align:start position:0% to chat to me quickly what is ipfs it's 02:20:36.771 --> 02:20:38.711 align:start position:0% to chat to me quickly what is ipfs it's aiming<02:20:37.311> to<02:20:37.431> make<02:20:37.460> the<02:20:37.670> web<02:20:37.790> work<02:20:37.971> here<02:20:38.420> to<02:20:38.540> here 02:20:38.711 --> 02:20:38.721 align:start position:0% aiming to make the web work here to here 02:20:38.721 --> 02:20:40.480 align:start position:0% aiming to make the web work here to here so<02:20:38.870> instead<02:20:39.320> of<02:20:39.440> HTTP<02:20:39.920> you<02:20:40.040> are<02:20:40.160> all<02:20:40.280> talking 02:20:40.480 --> 02:20:40.490 align:start position:0% so instead of HTTP you are all talking 02:20:40.490 --> 02:20:42.520 align:start position:0% so instead of HTTP you are all talking to<02:20:40.610> a<02:20:40.670> central<02:20:40.940> server<02:20:41.030> or<02:20:41.721> connecting 02:20:42.520 --> 02:20:42.530 align:start position:0% to a central server or connecting 02:20:42.530 --> 02:20:43.870 align:start position:0% to a central server or connecting between<02:20:42.681> all<02:20:43.160> of<02:20:43.190> the<02:20:43.400> different<02:20:43.431> notes<02:20:43.761> in 02:20:43.870 --> 02:20:43.880 align:start position:0% between all of the different notes in 02:20:43.880 --> 02:20:45.940 align:start position:0% between all of the different notes in the<02:20:43.971> network<02:20:44.210> directly<02:20:44.511> and<02:20:45.290> and<02:20:45.620> it's<02:20:45.830> going 02:20:45.940 --> 02:20:45.950 align:start position:0% the network directly and and it's going 02:20:45.950 --> 02:20:47.230 align:start position:0% the network directly and and it's going from<02:20:46.070> something<02:20:46.400> like<02:20:46.551> location<02:20:46.971> with 02:20:47.230 --> 02:20:47.240 align:start position:0% from something like location with 02:20:47.240 --> 02:20:48.700 align:start position:0% from something like location with addressing<02:20:47.630> where<02:20:47.960> you're<02:20:48.051> going<02:20:48.230> to<02:20:48.351> the 02:20:48.700 --> 02:20:48.710 align:start position:0% addressing where you're going to the 02:20:48.710 --> 02:20:51.430 align:start position:0% addressing where you're going to the example.com<02:20:49.221> to<02:20:49.971> contents<02:20:50.811> addressing<02:20:51.230> where 02:20:51.430 --> 02:20:51.440 align:start position:0% example.com to contents addressing where 02:20:51.440 --> 02:20:52.690 align:start position:0% example.com to contents addressing where you're<02:20:51.530> finding<02:20:51.681> content<02:20:52.160> like<02:20:52.250> what<02:20:52.460> it<02:20:52.580> is 02:20:52.690 --> 02:20:52.700 align:start position:0% you're finding content like what it is 02:20:52.700 --> 02:20:56.440 align:start position:0% you're finding content like what it is not<02:20:53.091> whose<02:20:53.330> hooks<02:20:53.511> together<02:20:55.000> any<02:20:56.000> of<02:20:56.120> us<02:20:56.210> aims 02:20:56.440 --> 02:20:56.450 align:start position:0% not whose hooks together any of us aims 02:20:56.450 --> 02:20:57.881 align:start position:0% not whose hooks together any of us aims to<02:20:56.601> solve<02:20:56.780> a<02:20:57.080> whole<02:20:57.351> ton<02:20:57.561> of<02:20:57.591> different 02:20:57.881 --> 02:20:57.891 align:start position:0% to solve a whole ton of different 02:20:57.891 --> 02:21:00.251 align:start position:0% to solve a whole ton of different problems<02:20:58.280> around<02:20:59.181> public<02:20:59.990> with<02:21:00.141> the 02:21:00.251 --> 02:21:00.261 align:start position:0% problems around public with the 02:21:00.261 --> 02:21:01.990 align:start position:0% problems around public with the inefficiencies<02:21:00.500> of<02:21:00.591> all<02:21:01.250> trying<02:21:01.610> to<02:21:01.641> download 02:21:01.990 --> 02:21:02.000 align:start position:0% inefficiencies of all trying to download 02:21:02.000 --> 02:21:03.551 align:start position:0% inefficiencies of all trying to download the<02:21:02.120> same<02:21:02.271> video<02:21:02.511> at<02:21:02.811> the<02:21:02.900> same<02:21:03.080> room<02:21:03.290> at<02:21:03.380> once 02:21:03.551 --> 02:21:03.561 align:start position:0% the same video at the same room at once 02:21:03.561 --> 02:21:06.131 align:start position:0% the same video at the same room at once to<02:21:04.190> break<02:21:04.610> links<02:21:04.971> to<02:21:05.301> about<02:21:05.450> security<02:21:05.841> models 02:21:06.131 --> 02:21:06.141 align:start position:0% to break links to about security models 02:21:06.141 --> 02:21:09.370 align:start position:0% to break links to about security models to<02:21:06.681> censorship<02:21:07.040> resistance<02:21:07.610> and<02:21:08.450> we're<02:21:08.900> we're 02:21:09.370 --> 02:21:09.380 align:start position:0% to censorship resistance and we're we're 02:21:09.380 --> 02:21:11.200 align:start position:0% to censorship resistance and we're we're in<02:21:09.561> different<02:21:09.920> stages<02:21:10.221> of<02:21:10.521> completion<02:21:10.880> on 02:21:11.200 --> 02:21:11.210 align:start position:0% in different stages of completion on 02:21:11.210 --> 02:21:13.001 align:start position:0% in different stages of completion on various<02:21:11.750> ones<02:21:11.960> of<02:21:12.080> these<02:21:12.170> I<02:21:12.351> think<02:21:12.561> censorship 02:21:13.001 --> 02:21:13.011 align:start position:0% various ones of these I think censorship 02:21:13.011 --> 02:21:14.560 align:start position:0% various ones of these I think censorship is<02:21:13.130> actually<02:21:13.460> an<02:21:13.700> area<02:21:14.091> where<02:21:14.271> I<02:21:14.301> think<02:21:14.360> this 02:21:14.560 --> 02:21:14.570 align:start position:0% is actually an area where I think this 02:21:14.570 --> 02:21:16.120 align:start position:0% is actually an area where I think this has<02:21:14.690> been<02:21:14.721> used<02:21:15.021> pretty<02:21:15.500> effectively<02:21:15.950> in 02:21:16.120 --> 02:21:16.130 align:start position:0% has been used pretty effectively in 02:21:16.130 --> 02:21:20.261 align:start position:0% has been used pretty effectively in things<02:21:16.400> like<02:21:16.660> the<02:21:17.830> the<02:21:18.830> work<02:21:19.521> in<02:21:19.700> Catalunya 02:21:20.261 --> 02:21:20.271 align:start position:0% things like the the work in Catalunya 02:21:20.271 --> 02:21:22.541 align:start position:0% things like the the work in Catalunya where<02:21:20.780> they<02:21:20.900> were<02:21:20.990> using<02:21:21.170> IDs<02:21:21.710> to<02:21:21.920> put<02:21:22.190> up<02:21:22.311> the 02:21:22.541 --> 02:21:22.551 align:start position:0% where they were using IDs to put up the 02:21:22.551 --> 02:21:24.421 align:start position:0% where they were using IDs to put up the various<02:21:23.330> polling<02:21:23.721> location 02:21:24.421 --> 02:21:24.431 align:start position:0% various polling location 02:21:24.431 --> 02:21:26.520 align:start position:0% various polling location where<02:21:24.551> people<02:21:24.700> go<02:21:25.061> in<02:21:25.240> and<02:21:25.511> vote<02:21:25.780> about 02:21:26.520 --> 02:21:26.530 align:start position:0% where people go in and vote about 02:21:26.530 --> 02:21:27.480 align:start position:0% where people go in and vote about whether<02:21:26.681> or<02:21:26.920> not<02:21:26.980> they<02:21:27.131> wanted<02:21:27.341> to<02:21:27.400> be<02:21:27.460> a 02:21:27.480 --> 02:21:27.490 align:start position:0% whether or not they wanted to be a 02:21:27.490 --> 02:21:29.400 align:start position:0% whether or not they wanted to be a dependent<02:21:27.780> but<02:21:28.780> hitting<02:21:28.900> a<02:21:29.021> number<02:21:29.200> of<02:21:29.290> these 02:21:29.400 --> 02:21:29.410 align:start position:0% dependent but hitting a number of these 02:21:29.410 --> 02:21:30.900 align:start position:0% dependent but hitting a number of these areas<02:21:29.681> we<02:21:29.801> still<02:21:29.950> have<02:21:30.040> a<02:21:30.070> lot<02:21:30.280> of<02:21:30.311> work<02:21:30.551> to<02:21:30.820> get 02:21:30.900 --> 02:21:30.910 align:start position:0% areas we still have a lot of work to get 02:21:30.910 --> 02:21:34.980 align:start position:0% areas we still have a lot of work to get to<02:21:30.971> our<02:21:31.181> end<02:21:31.330> goal<02:21:33.150> as<02:21:34.150> mine<02:21:34.450> was<02:21:34.601> mentioning 02:21:34.980 --> 02:21:34.990 align:start position:0% to our end goal as mine was mentioning 02:21:34.990 --> 02:21:36.810 align:start position:0% to our end goal as mine was mentioning IP<02:21:35.261> MSE<02:21:35.681> is<02:21:35.740> just<02:21:35.920> kind<02:21:36.070> of<02:21:36.101> one<02:21:36.400> component 02:21:36.810 --> 02:21:36.820 align:start position:0% IP MSE is just kind of one component 02:21:36.820 --> 02:21:38.820 align:start position:0% IP MSE is just kind of one component we've<02:21:37.120> done<02:21:37.330> a<02:21:37.511> lot<02:21:37.690> of<02:21:37.841> work<02:21:38.051> to<02:21:38.230> factor<02:21:38.681> out 02:21:38.820 --> 02:21:38.830 align:start position:0% we've done a lot of work to factor out 02:21:38.830 --> 02:21:40.621 align:start position:0% we've done a lot of work to factor out the<02:21:39.011> different<02:21:39.341> pieces<02:21:39.610> of<02:21:39.761> IQ<02:21:40.210> recipe<02:21:40.540> you 02:21:40.621 --> 02:21:40.631 align:start position:0% the different pieces of IQ recipe you 02:21:40.631 --> 02:21:42.331 align:start position:0% the different pieces of IQ recipe you could<02:21:40.750> use<02:21:40.931> them<02:21:41.170> independently<02:21:42.040> they've 02:21:42.331 --> 02:21:42.341 align:start position:0% could use them independently they've 02:21:42.341 --> 02:21:44.041 align:start position:0% could use them independently they've grown<02:21:42.761> and<02:21:43.030> taken<02:21:43.301> on<02:21:43.420> their<02:21:43.601> own 02:21:44.041 --> 02:21:44.051 align:start position:0% grown and taken on their own 02:21:44.051 --> 02:21:46.291 align:start position:0% grown and taken on their own open-source<02:21:44.471> projects<02:21:45.131> so<02:21:45.311> the<02:21:45.761> PDP<02:21:46.061> is<02:21:46.150> one 02:21:46.291 --> 02:21:46.301 align:start position:0% open-source projects so the PDP is one 02:21:46.301 --> 02:21:47.671 align:start position:0% open-source projects so the PDP is one of<02:21:46.391> those<02:21:46.540> but<02:21:46.780> there's<02:21:46.931> also<02:21:47.051> a<02:21:47.141> multi-format 02:21:47.671 --> 02:21:47.681 align:start position:0% of those but there's also a multi-format 02:21:47.681 --> 02:21:49.501 align:start position:0% of those but there's also a multi-format and<02:21:48.101> i<02:21:48.160> Kildee<02:21:48.610> if<02:21:49.061> you<02:21:49.150> want<02:21:49.271> to<02:21:49.330> talk<02:21:49.420> about 02:21:49.501 --> 02:21:49.511 align:start position:0% and i Kildee if you want to talk about 02:21:49.511 --> 02:21:51.900 align:start position:0% and i Kildee if you want to talk about IW<02:21:49.960> go<02:21:50.051> talk<02:21:50.230> to<02:21:50.261> Derek<02:21:50.591> is<02:21:51.040> or<02:21:51.341> your<02:21:51.551> master 02:21:51.900 --> 02:21:51.910 align:start position:0% IW go talk to Derek is or your master 02:21:51.910 --> 02:21:54.450 align:start position:0% IW go talk to Derek is or your master about<02:21:52.120> everything<02:21:52.631> linked<02:21:53.530> to<02:21:53.710> data<02:21:53.830> related 02:21:54.450 --> 02:21:54.460 align:start position:0% about everything linked to data related 02:21:54.460 --> 02:21:57.541 align:start position:0% about everything linked to data related about<02:21:54.820> schemas<02:21:55.500> but<02:21:56.500> we<02:21:56.740> kind<02:21:57.011> of<02:21:57.070> sit<02:21:57.250> on<02:21:57.400> top 02:21:57.541 --> 02:21:57.551 align:start position:0% about schemas but we kind of sit on top 02:21:57.551 --> 02:21:59.581 align:start position:0% about schemas but we kind of sit on top of<02:21:57.730> this<02:21:58.000> amazing<02:21:58.210> staff<02:21:58.660> and<02:21:58.870> get<02:21:58.990> to<02:21:59.110> utilize 02:21:59.581 --> 02:21:59.591 align:start position:0% of this amazing staff and get to utilize 02:21:59.591 --> 02:22:01.020 align:start position:0% of this amazing staff and get to utilize all<02:21:59.891> of<02:21:59.920> the<02:22:00.160> wonderful<02:22:00.311> components<02:22:00.940> that 02:22:01.020 --> 02:22:01.030 align:start position:0% all of the wonderful components that 02:22:01.030 --> 02:22:02.160 align:start position:0% all of the wonderful components that folks<02:22:01.210> like<02:22:01.301> let<02:22:01.511> me<02:22:01.601> be<02:22:01.750> and<02:22:01.870> I<02:22:01.900> feel<02:22:02.051> like 02:22:02.160 --> 02:22:02.170 align:start position:0% folks like let me be and I feel like 02:22:02.170 --> 02:22:05.610 align:start position:0% folks like let me be and I feel like everything<02:22:02.471> on<02:22:03.480> Ibanez<02:22:04.480> is<02:22:04.960> a<02:22:05.051> super<02:22:05.440> huge 02:22:05.610 --> 02:22:05.620 align:start position:0% everything on Ibanez is a super huge 02:22:05.620 --> 02:22:07.081 align:start position:0% everything on Ibanez is a super huge community<02:22:05.950> there's<02:22:06.341> four<02:22:06.670> thousand 02:22:07.081 --> 02:22:07.091 align:start position:0% community there's four thousand 02:22:07.091 --> 02:22:08.610 align:start position:0% community there's four thousand contributors<02:22:07.511> around<02:22:07.870> the<02:22:07.990> world<02:22:08.170> we 02:22:08.610 --> 02:22:08.620 align:start position:0% contributors around the world we 02:22:08.620 --> 02:22:10.470 align:start position:0% contributors around the world we actually<02:22:08.860> just<02:22:09.040> had<02:22:09.280> our<02:22:09.311> first<02:22:09.730> meetup 02:22:10.470 --> 02:22:10.480 align:start position:0% actually just had our first meetup 02:22:10.480 --> 02:22:12.270 align:start position:0% actually just had our first meetup in<02:22:10.631> Japan<02:22:11.021> yesterday<02:22:11.710> which<02:22:11.980> was<02:22:12.131> super 02:22:12.270 --> 02:22:12.280 align:start position:0% in Japan yesterday which was super 02:22:12.280 --> 02:22:14.190 align:start position:0% in Japan yesterday which was super awesome<02:22:12.490> great<02:22:12.910> to<02:22:13.030> eat<02:22:13.150> this<02:22:13.330> slice<02:22:13.900> of<02:22:13.960> the 02:22:14.190 --> 02:22:14.200 align:start position:0% awesome great to eat this slice of the 02:22:14.200 --> 02:22:15.600 align:start position:0% awesome great to eat this slice of the community<02:22:14.650> have<02:22:15.101> been<02:22:15.131> a<02:22:15.311> lot<02:22:15.431> of<02:22:15.460> other 02:22:15.600 --> 02:22:15.610 align:start position:0% community have been a lot of other 02:22:15.610 --> 02:22:17.791 align:start position:0% community have been a lot of other people<02:22:15.910> from<02:22:16.120> Hong<02:22:16.750> Kong<02:22:17.021> and<02:22:17.320> trying<02:22:17.561> to<02:22:17.620> also 02:22:17.791 --> 02:22:17.801 align:start position:0% people from Hong Kong and trying to also 02:22:17.801 --> 02:22:21.270 align:start position:0% people from Hong Kong and trying to also be<02:22:18.011> a<02:22:18.040> participate<02:22:18.551> in<02:22:18.761> that<02:22:19.740> okay<02:22:20.740> I<02:22:20.950> don't 02:22:21.270 --> 02:22:21.280 align:start position:0% be a participate in that okay I don't 02:22:21.280 --> 02:22:22.591 align:start position:0% be a participate in that okay I don't learn<02:22:21.460> for<02:22:21.580> today<02:22:21.730> gonna<02:22:22.000> talk<02:22:22.181> a<02:22:22.210> little<02:22:22.450> bit 02:22:22.591 --> 02:22:22.601 align:start position:0% learn for today gonna talk a little bit 02:22:22.601 --> 02:22:23.910 align:start position:0% learn for today gonna talk a little bit about<02:22:22.631> the<02:22:22.811> growth<02:22:23.051> we've<02:22:23.261> been<02:22:23.410> seeing<02:22:23.591> and 02:22:23.910 --> 02:22:23.920 align:start position:0% about the growth we've been seeing and 02:22:23.920 --> 02:22:25.171 align:start position:0% about the growth we've been seeing and some<02:22:24.101> cool<02:22:24.460> new<02:22:24.580> projects<02:22:24.971> that<02:22:25.091> are<02:22:25.150> being 02:22:25.171 --> 02:22:25.181 align:start position:0% some cool new projects that are being 02:22:25.181 --> 02:22:27.060 align:start position:0% some cool new projects that are being built<02:22:25.420> behind<02:22:25.601> EFS<02:22:26.051> and<02:22:26.381> then<02:22:26.771> hopefully 02:22:27.060 --> 02:22:27.070 align:start position:0% built behind EFS and then hopefully 02:22:27.070 --> 02:22:28.680 align:start position:0% built behind EFS and then hopefully phone<02:22:27.460> gets<02:22:27.670> time<02:22:27.790> to<02:22:27.820> it<02:22:28.061> I<02:22:28.240> can<02:22:28.540> talk<02:22:28.660> a 02:22:28.680 --> 02:22:28.690 align:start position:0% phone gets time to it I can talk a 02:22:28.690 --> 02:22:30.211 align:start position:0% phone gets time to it I can talk a little<02:22:28.960> bit<02:22:29.141> about<02:22:29.170> the<02:22:29.410> future<02:22:29.561> and<02:22:29.860> the<02:22:29.950> cool 02:22:30.211 --> 02:22:30.221 align:start position:0% little bit about the future and the cool 02:22:30.221 --> 02:22:31.831 align:start position:0% little bit about the future and the cool stuff<02:22:30.370> that<02:22:30.431> we<02:22:30.670> we've<02:22:31.150> done<02:22:31.330> this<02:22:31.420> past<02:22:31.631> year 02:22:31.831 --> 02:22:31.841 align:start position:0% stuff that we we've done this past year 02:22:31.841 --> 02:22:34.921 align:start position:0% stuff that we we've done this past year and<02:22:31.960> what<02:22:32.051> we<02:22:32.080> see<02:22:32.290> going<02:22:32.410> forward<02:22:33.811> from<02:22:34.811> a 02:22:34.921 --> 02:22:34.931 align:start position:0% and what we see going forward from a 02:22:34.931 --> 02:22:36.810 align:start position:0% and what we see going forward from a growth<02:22:35.080> perspective<02:22:35.110> we<02:22:35.830> saw<02:22:36.011> huge<02:22:36.551> growth 02:22:36.810 --> 02:22:36.820 align:start position:0% growth perspective we saw huge growth 02:22:36.820 --> 02:22:40.200 align:start position:0% growth perspective we saw huge growth this<02:22:37.360> year<02:22:37.420> we<02:22:38.170> saw<02:22:38.290> a<02:22:38.320> 30x<02:22:38.830> increase<02:22:39.370> in<02:22:39.641> nodes 02:22:40.200 --> 02:22:40.210 align:start position:0% this year we saw a 30x increase in nodes 02:22:40.210 --> 02:22:42.600 align:start position:0% this year we saw a 30x increase in nodes connected<02:22:40.631> to<02:22:40.690> the<02:22:40.780> network<02:22:40.960> in<02:22:41.410> q2<02:22:42.011> so<02:22:42.490> now 02:22:42.600 --> 02:22:42.610 align:start position:0% connected to the network in q2 so now 02:22:42.610 --> 02:22:44.131 align:start position:0% connected to the network in q2 so now we're<02:22:42.761> up<02:22:42.820> to<02:22:42.881> hundreds<02:22:43.540> of<02:22:43.631> thousands<02:22:44.051> of 02:22:44.131 --> 02:22:44.141 align:start position:0% we're up to hundreds of thousands of 02:22:44.141 --> 02:22:46.291 align:start position:0% we're up to hundreds of thousands of nodes<02:22:44.381> accessing<02:22:45.101> itams<02:22:45.370> every<02:22:45.881> single<02:22:46.150> day 02:22:46.291 --> 02:22:46.301 align:start position:0% nodes accessing itams every single day 02:22:46.301 --> 02:22:50.100 align:start position:0% nodes accessing itams every single day super<02:22:47.290> cool<02:22:47.500> super<02:22:48.011> exciting<02:22:48.551> also<02:22:49.301> a<02:22:49.330> lot<02:22:50.021> of 02:22:50.100 --> 02:22:50.110 align:start position:0% super cool super exciting also a lot of 02:22:50.110 --> 02:22:51.780 align:start position:0% super cool super exciting also a lot of performance<02:22:50.620> and<02:22:50.860> scaling<02:22:51.400> related 02:22:51.780 --> 02:22:51.790 align:start position:0% performance and scaling related 02:22:51.790 --> 02:22:53.280 align:start position:0% performance and scaling related challenges<02:22:51.971> that<02:22:52.330> come<02:22:52.480> out<02:22:52.601> of<02:22:52.721> that<02:22:52.841> as<02:22:53.080> you 02:22:53.280 --> 02:22:53.290 align:start position:0% challenges that come out of that as you 02:22:53.290 --> 02:22:55.890 align:start position:0% challenges that come out of that as you probably<02:22:53.681> expect<02:22:54.101> some<02:22:54.670> definitely<02:22:55.360> new 02:22:55.890 --> 02:22:55.900 align:start position:0% probably expect some definitely new 02:22:55.900 --> 02:22:57.600 align:start position:0% probably expect some definitely new challenges<02:22:56.500> for<02:22:56.530> us<02:22:56.740> in<02:22:57.011> terms<02:22:57.190> of<02:22:57.341> being<02:22:57.460> able 02:22:57.600 --> 02:22:57.610 align:start position:0% challenges for us in terms of being able 02:22:57.610 --> 02:23:01.440 align:start position:0% challenges for us in terms of being able to<02:22:58.290> spin<02:22:59.290> up<02:22:59.440> test<02:22:59.891> nets<02:23:00.131> that<02:23:00.311> can<02:23:00.610> validate 02:23:01.440 --> 02:23:01.450 align:start position:0% to spin up test nets that can validate 02:23:01.450 --> 02:23:03.211 align:start position:0% to spin up test nets that can validate the<02:23:01.690> new<02:23:01.990> releases<02:23:02.320> of<02:23:02.471> IQs<02:23:02.771> are<02:23:03.011> gonna<02:23:03.131> be 02:23:03.211 --> 02:23:03.221 align:start position:0% the new releases of IQs are gonna be 02:23:03.221 --> 02:23:05.131 align:start position:0% the new releases of IQs are gonna be able<02:23:03.280> to<02:23:03.400> handle<02:23:03.641> that<02:23:03.940> sort<02:23:04.271> of<02:23:04.360> load<02:23:04.631> on<02:23:05.080> a 02:23:05.131 --> 02:23:05.141 align:start position:0% able to handle that sort of load on a 02:23:05.141 --> 02:23:06.870 align:start position:0% able to handle that sort of load on a day<02:23:05.320> to<02:23:05.381> day<02:23:05.471> basis 02:23:06.870 --> 02:23:06.880 align:start position:0% day to day basis 02:23:06.880 --> 02:23:10.180 align:start position:0% day to day basis the<02:23:07.880> IMS<02:23:08.510> HTTP<02:23:09.020> gateway<02:23:09.380> that<02:23:09.560> we<02:23:09.710> run<02:23:09.860> there's 02:23:10.180 --> 02:23:10.190 align:start position:0% the IMS HTTP gateway that we run there's 02:23:10.190 --> 02:23:11.740 align:start position:0% the IMS HTTP gateway that we run there's a<02:23:10.220> lot<02:23:10.520> of<02:23:10.640> different<02:23:10.880> gateways<02:23:11.030> but<02:23:11.390> one<02:23:11.660> in 02:23:11.740 --> 02:23:11.750 align:start position:0% a lot of different gateways but one in 02:23:11.750 --> 02:23:13.740 align:start position:0% a lot of different gateways but one in particular<02:23:11.870> that<02:23:12.200> we're<02:23:12.800> running<02:23:12.920> is<02:23:13.190> seeing 02:23:13.740 --> 02:23:13.750 align:start position:0% particular that we're running is seeing 02:23:13.750 --> 02:23:17.440 align:start position:0% particular that we're running is seeing 300<02:23:14.750> million<02:23:15.140> requests<02:23:15.500> per<02:23:15.560> day<02:23:15.710> from<02:23:16.460> very 02:23:17.440 --> 02:23:17.450 align:start position:0% 300 million requests per day from very 02:23:17.450 --> 02:23:19.660 align:start position:0% 300 million requests per day from very accessing<02:23:17.900> about<02:23:18.080> one<02:23:18.290> terabyte<02:23:18.770> of<02:23:18.830> data<02:23:19.100> so 02:23:19.660 --> 02:23:19.670 align:start position:0% accessing about one terabyte of data so 02:23:19.670 --> 02:23:21.280 align:start position:0% accessing about one terabyte of data so that's<02:23:20.000> just<02:23:20.150> one<02:23:20.510> slice<02:23:20.810> that<02:23:20.990> people<02:23:21.170> who 02:23:21.280 --> 02:23:21.290 align:start position:0% that's just one slice that people who 02:23:21.290 --> 02:23:23.590 align:start position:0% that's just one slice that people who are<02:23:21.380> currently<02:23:21.770> using<02:23:21.940> HTTP<02:23:22.940> trying<02:23:23.390> to<02:23:23.479> get 02:23:23.590 --> 02:23:23.600 align:start position:0% are currently using HTTP trying to get 02:23:23.600 --> 02:23:26.140 align:start position:0% are currently using HTTP trying to get content<02:23:23.900> on<02:23:24.050> my<02:23:24.140> ipfs<02:23:24.500> network<02:23:24.800> and<02:23:25.150> they're 02:23:26.140 --> 02:23:26.150 align:start position:0% content on my ipfs network and they're 02:23:26.150 --> 02:23:27.400 align:start position:0% content on my ipfs network and they're getting<02:23:26.240> a<02:23:26.390> lot<02:23:26.510> of<02:23:26.630> content<02:23:26.930> there's<02:23:27.229> a<02:23:27.290> lot 02:23:27.400 --> 02:23:27.410 align:start position:0% getting a lot of content there's a lot 02:23:27.410 --> 02:23:28.510 align:start position:0% getting a lot of content there's a lot of<02:23:27.470> people<02:23:27.710> trying<02:23:27.890> to<02:23:28.040> utilize<02:23:28.220> this 02:23:28.510 --> 02:23:28.520 align:start position:0% of people trying to utilize this 02:23:28.520 --> 02:23:30.010 align:start position:0% of people trying to utilize this infrastructure<02:23:29.060> that's<02:23:29.240> another<02:23:29.660> thing<02:23:29.960> that 02:23:30.010 --> 02:23:30.020 align:start position:0% infrastructure that's another thing that 02:23:30.020 --> 02:23:32.350 align:start position:0% infrastructure that's another thing that we<02:23:30.350> support<02:23:30.800> and<02:23:31.040> have<02:23:31.820> to<02:23:31.940> make<02:23:32.090> sure<02:23:32.210> it's 02:23:32.350 --> 02:23:32.360 align:start position:0% we support and have to make sure it's 02:23:32.360 --> 02:23:34.060 align:start position:0% we support and have to make sure it's performant<02:23:32.870> and<02:23:32.990> we're<02:23:33.110> trying<02:23:33.320> to<02:23:33.440> reach<02:23:33.590> all 02:23:34.060 --> 02:23:34.070 align:start position:0% performant and we're trying to reach all 02:23:34.070 --> 02:23:37.990 align:start position:0% performant and we're trying to reach all of<02:23:34.310> these<02:23:34.430> new<02:23:34.550> people<02:23:34.670> gets<02:23:34.970> you<02:23:36.610> the<02:23:37.610> number 02:23:37.990 --> 02:23:38.000 align:start position:0% of these new people gets you the number 02:23:38.000 --> 02:23:39.640 align:start position:0% of these new people gets you the number of<02:23:38.030> people<02:23:38.210> who<02:23:38.420> are<02:23:38.450> building<02:23:38.750> on<02:23:39.020> top<02:23:39.290> of<02:23:39.350> IP 02:23:39.640 --> 02:23:39.650 align:start position:0% of people who are building on top of IP 02:23:39.650 --> 02:23:41.820 align:start position:0% of people who are building on top of IP FS<02:23:39.979> and<02:23:40.190> building<02:23:40.490> new<02:23:40.610> types<02:23:40.940> of<02:23:41.240> data 02:23:41.820 --> 02:23:41.830 align:start position:0% FS and building new types of data 02:23:41.830 --> 02:23:44.520 align:start position:0% FS and building new types of data related<02:23:42.830> out<02:23:42.950> with<02:23:43.100> you<02:23:43.220> to<02:23:43.430> social<02:23:43.880> media 02:23:44.520 --> 02:23:44.530 align:start position:0% related out with you to social media 02:23:44.530 --> 02:23:47.530 align:start position:0% related out with you to social media marketplaces<02:23:45.550> content<02:23:46.550> things<02:23:46.760> things<02:23:47.450> in 02:23:47.530 --> 02:23:47.540 align:start position:0% marketplaces content things things in 02:23:47.540 --> 02:23:49.420 align:start position:0% marketplaces content things things in the<02:23:47.630> finance<02:23:48.020> space<02:23:48.320> governance<02:23:49.130> really 02:23:49.420 --> 02:23:49.430 align:start position:0% the finance space governance really 02:23:49.430 --> 02:23:51.100 align:start position:0% the finance space governance really there's<02:23:49.940> a<02:23:50.000> ton<02:23:50.300> of<02:23:50.330> new<02:23:50.630> things<02:23:50.900> that<02:23:51.080> are 02:23:51.100 --> 02:23:51.110 align:start position:0% there's a ton of new things that are 02:23:51.110 --> 02:23:52.810 align:start position:0% there's a ton of new things that are happening<02:23:51.200> and<02:23:51.740> something<02:23:52.280> that's<02:23:52.550> really 02:23:52.810 --> 02:23:52.820 align:start position:0% happening and something that's really 02:23:52.820 --> 02:23:54.760 align:start position:0% happening and something that's really exciting<02:23:52.940> is<02:23:53.510> that<02:23:53.570> now<02:23:54.229> some<02:23:54.440> of<02:23:54.470> them<02:23:54.620> are 02:23:54.760 --> 02:23:54.770 align:start position:0% exciting is that now some of them are 02:23:54.770 --> 02:23:56.710 align:start position:0% exciting is that now some of them are reaching<02:23:55.160> millions<02:23:55.460> of<02:23:56.030> monthly<02:23:56.360> active 02:23:56.710 --> 02:23:56.720 align:start position:0% reaching millions of monthly active 02:23:56.720 --> 02:23:58.450 align:start position:0% reaching millions of monthly active users<02:23:56.750> so<02:23:57.350> we<02:23:57.440> have<02:23:57.530> multiple<02:23:58.010> apps<02:23:58.190> they're 02:23:58.450 --> 02:23:58.460 align:start position:0% users so we have multiple apps they're 02:23:58.460 --> 02:24:00.280 align:start position:0% users so we have multiple apps they're all<02:23:58.640> in<02:23:58.910> the<02:23:59.360> millions<02:23:59.690> of<02:23:59.780> monthly<02:23:59.960> active 02:24:00.280 --> 02:24:00.290 align:start position:0% all in the millions of monthly active 02:24:00.290 --> 02:24:02.650 align:start position:0% all in the millions of monthly active users<02:24:00.320> space<02:24:00.860> which<02:24:01.820> means<02:24:02.210> there's<02:24:02.510> some 02:24:02.650 --> 02:24:02.660 align:start position:0% users space which means there's some 02:24:02.660 --> 02:24:05.140 align:start position:0% users space which means there's some really<02:24:03.110> exciting<02:24:03.410> in<02:24:03.770> the<02:24:04.340> use<02:24:04.490> cases<02:24:04.760> you 02:24:05.140 --> 02:24:05.150 align:start position:0% really exciting in the use cases you 02:24:05.150 --> 02:24:06.160 align:start position:0% really exciting in the use cases you need<02:24:05.270> to<02:24:05.420> make<02:24:05.540> sure<02:24:05.570> we're<02:24:05.840> supporting 02:24:06.160 --> 02:24:06.170 align:start position:0% need to make sure we're supporting 02:24:06.170 --> 02:24:08.200 align:start position:0% need to make sure we're supporting people<02:24:06.500> who<02:24:06.650> are<02:24:06.800> utilizing<02:24:07.010> ipfs<02:24:07.820> for<02:24:08.060> kind 02:24:08.200 --> 02:24:08.210 align:start position:0% people who are utilizing ipfs for kind 02:24:08.210 --> 02:24:12.730 align:start position:0% people who are utilizing ipfs for kind of<02:24:08.300> their<02:24:08.840> normal<02:24:09.229> browsing<02:24:09.979> needs<02:24:10.190> for<02:24:11.740> PSL 02:24:12.730 --> 02:24:12.740 align:start position:0% of their normal browsing needs for PSL 02:24:12.740 --> 02:24:14.650 align:start position:0% of their normal browsing needs for PSL content<02:24:13.220> or<02:24:13.400> videos<02:24:13.820> or<02:24:14.150> other<02:24:14.360> things<02:24:14.570> like 02:24:14.650 --> 02:24:14.660 align:start position:0% content or videos or other things like 02:24:14.660 --> 02:24:14.950 align:start position:0% content or videos or other things like that 02:24:14.950 --> 02:24:14.960 align:start position:0% that 02:24:14.960 --> 02:24:17.140 align:start position:0% that that's<02:24:15.830> an<02:24:15.950> increased<02:24:16.310> scale<02:24:16.670> that<02:24:16.850> we<02:24:17.030> need 02:24:17.140 --> 02:24:17.150 align:start position:0% that's an increased scale that we need 02:24:17.150 --> 02:24:18.670 align:start position:0% that's an increased scale that we need to<02:24:17.240> make<02:24:17.390> sure<02:24:17.510> we're<02:24:17.660> supporting<02:24:17.750> as<02:24:18.410> it's 02:24:18.670 --> 02:24:18.680 align:start position:0% to make sure we're supporting as it's 02:24:18.680 --> 02:24:20.050 align:start position:0% to make sure we're supporting as it's sort<02:24:18.860> of<02:24:18.890> follow<02:24:19.130> that<02:24:19.310> people<02:24:19.520> build<02:24:19.700> on<02:24:19.850> top 02:24:20.050 --> 02:24:20.060 align:start position:0% sort of follow that people build on top 02:24:20.060 --> 02:24:22.570 align:start position:0% sort of follow that people build on top of<02:24:21.220> all<02:24:22.220> right 02:24:22.570 --> 02:24:22.580 align:start position:0% of all right 02:24:22.580 --> 02:24:24.460 align:start position:0% of all right talking<02:24:22.880> about<02:24:23.090> new<02:24:23.360> new<02:24:23.840> projects<02:24:24.260> so<02:24:24.350> what 02:24:24.460 --> 02:24:24.470 align:start position:0% talking about new new projects so what 02:24:24.470 --> 02:24:27.430 align:start position:0% talking about new new projects so what are<02:24:24.590> some<02:24:24.620> of<02:24:24.800> these<02:24:25.450> three<02:24:26.450> three<02:24:26.990> categories 02:24:27.430 --> 02:24:27.440 align:start position:0% are some of these three three categories 02:24:27.440 --> 02:24:29.350 align:start position:0% are some of these three three categories I'll<02:24:27.560> touch<02:24:27.740> on<02:24:27.890> I<02:24:28.160> mean<02:24:28.460> the<02:24:28.850> last<02:24:29.000> time<02:24:29.120> we're 02:24:29.350 --> 02:24:29.360 align:start position:0% I'll touch on I mean the last time we're 02:24:29.360 --> 02:24:31.270 align:start position:0% I'll touch on I mean the last time we're going<02:24:29.479> to<02:24:29.540> say<02:24:29.660> grab<02:24:30.440> that<02:24:30.590> in<02:24:30.680> February<02:24:30.890> but 02:24:31.270 --> 02:24:31.280 align:start position:0% going to say grab that in February but 02:24:31.280 --> 02:24:33.340 align:start position:0% going to say grab that in February but mobile<02:24:31.790> was<02:24:32.240> a<02:24:32.270> new<02:24:32.450> thing<02:24:32.479> this<02:24:32.810> year<02:24:32.870> where 02:24:33.340 --> 02:24:33.350 align:start position:0% mobile was a new thing this year where 02:24:33.350 --> 02:24:35.650 align:start position:0% mobile was a new thing this year where new<02:24:34.010> mobile<02:24:34.729> apps<02:24:34.910> are<02:24:35.090> being<02:24:35.210> built<02:24:35.420> on<02:24:35.540> top 02:24:35.650 --> 02:24:35.660 align:start position:0% new mobile apps are being built on top 02:24:35.660 --> 02:24:37.390 align:start position:0% new mobile apps are being built on top of<02:24:35.720> NTFS<02:24:36.170> we<02:24:36.650> didn't<02:24:36.830> expect<02:24:37.040> this<02:24:37.190> to<02:24:37.250> happen 02:24:37.390 --> 02:24:37.400 align:start position:0% of NTFS we didn't expect this to happen 02:24:37.400 --> 02:24:38.080 align:start position:0% of NTFS we didn't expect this to happen so<02:24:37.760> quickly 02:24:38.080 --> 02:24:38.090 align:start position:0% so quickly 02:24:38.090 --> 02:24:41.020 align:start position:0% so quickly I<02:24:38.479> actually<02:24:38.990> think<02:24:39.290> like<02:24:39.560> it's<02:24:40.280> hard<02:24:40.610> to<02:24:40.880> get 02:24:41.020 --> 02:24:41.030 align:start position:0% I actually think like it's hard to get 02:24:41.030 --> 02:24:42.670 align:start position:0% I actually think like it's hard to get one<02:24:41.330> of<02:24:41.420> these<02:24:41.570> nodes<02:24:41.780> running<02:24:42.320> on<02:24:42.470> a<02:24:42.500> mobile 02:24:42.670 --> 02:24:42.680 align:start position:0% one of these nodes running on a mobile 02:24:42.680 --> 02:24:44.350 align:start position:0% one of these nodes running on a mobile device<02:24:43.040> where<02:24:43.280> you<02:24:43.310> have<02:24:43.370> like<02:24:43.790> pretty 02:24:44.350 --> 02:24:44.360 align:start position:0% device where you have like pretty 02:24:44.360 --> 02:24:46.870 align:start position:0% device where you have like pretty significant<02:24:45.490> environments<02:24:46.490> in<02:24:46.610> terms<02:24:46.760> of 02:24:46.870 --> 02:24:46.880 align:start position:0% significant environments in terms of 02:24:46.880 --> 02:24:49.180 align:start position:0% significant environments in terms of like<02:24:47.030> not<02:24:47.300> draining<02:24:47.600> battery<02:24:47.930> how<02:24:48.380> how<02:24:48.830> much 02:24:49.180 --> 02:24:49.190 align:start position:0% like not draining battery how how much 02:24:49.190 --> 02:24:50.200 align:start position:0% like not draining battery how how much you<02:24:49.310> can<02:24:49.430> actually<02:24:49.700> run<02:24:49.880> in<02:24:50.000> the 02:24:50.200 --> 02:24:50.210 align:start position:0% you can actually run in the 02:24:50.210 --> 02:24:52.420 align:start position:0% you can actually run in the around<02:24:50.510> all<02:24:51.020> of<02:24:51.170> those<02:24:51.260> things<02:24:51.500> but<02:24:51.770> the<02:24:52.250> folks 02:24:52.420 --> 02:24:52.430 align:start position:0% around all of those things but the folks 02:24:52.430 --> 02:24:54.070 align:start position:0% around all of those things but the folks at<02:24:52.550> textile<02:24:52.910> have<02:24:53.090> done<02:24:53.180> a<02:24:53.210> ton<02:24:53.540> of<02:24:53.570> work<02:24:53.690> to 02:24:54.070 --> 02:24:54.080 align:start position:0% at textile have done a ton of work to 02:24:54.080 --> 02:24:55.420 align:start position:0% at textile have done a ton of work to make<02:24:54.410> this<02:24:54.560> actually<02:24:54.890> really<02:24:55.010> easy<02:24:55.130> and 02:24:55.420 --> 02:24:55.430 align:start position:0% make this actually really easy and 02:24:55.430 --> 02:24:57.340 align:start position:0% make this actually really easy and accessible<02:24:55.720> there's<02:24:56.720> also<02:24:56.840> a<02:24:56.930> lot<02:24:57.140> of<02:24:57.200> stuff 02:24:57.340 --> 02:24:57.350 align:start position:0% accessible there's also a lot of stuff 02:24:57.350 --> 02:24:59.380 align:start position:0% accessible there's also a lot of stuff happening<02:24:57.680> in<02:24:57.800> identity<02:24:58.490> space<02:24:58.640> people<02:24:59.060> build 02:24:59.380 --> 02:24:59.390 align:start position:0% happening in identity space people build 02:24:59.390 --> 02:25:01.660 align:start position:0% happening in identity space people build in<02:24:59.540> a<02:24:59.600> cup<02:24:59.750> of<02:24:59.870> IP<02:25:00.020> Avesta<02:25:00.650> to<02:25:01.250> support 02:25:01.660 --> 02:25:01.670 align:start position:0% in a cup of IP Avesta to support 02:25:01.670 --> 02:25:03.610 align:start position:0% in a cup of IP Avesta to support variation<02:25:02.060> custom<02:25:02.390> identity<02:25:02.750> work<02:25:02.900> and 02:25:03.610 --> 02:25:03.620 align:start position:0% variation custom identity work and 02:25:03.620 --> 02:25:05.170 align:start position:0% variation custom identity work and apparently<02:25:03.830> other<02:25:04.160> really<02:25:04.580> cool<02:25:04.790> projects 02:25:05.170 --> 02:25:05.180 align:start position:0% apparently other really cool projects 02:25:05.180 --> 02:25:06.460 align:start position:0% apparently other really cool projects that<02:25:05.300> Braddock<02:25:05.540> will<02:25:05.690> and<02:25:05.870> a<02:25:05.900> couple<02:25:06.290> of 02:25:06.460 --> 02:25:06.470 align:start position:0% that Braddock will and a couple of 02:25:06.470 --> 02:25:08.320 align:start position:0% that Braddock will and a couple of others<02:25:06.680> I'll<02:25:06.860> mention<02:25:07.010> that<02:25:07.820> are<02:25:07.940> building<02:25:08.210> on 02:25:08.320 --> 02:25:08.330 align:start position:0% others I'll mention that are building on 02:25:08.330 --> 02:25:11.380 align:start position:0% others I'll mention that are building on top<02:25:08.390> of<02:25:08.450> my<02:25:08.600> advancement<02:25:09.080> cool<02:25:09.229> new<02:25:09.320> ways<02:25:10.270> as<02:25:11.270> I 02:25:11.380 --> 02:25:11.390 align:start position:0% top of my advancement cool new ways as I 02:25:11.390 --> 02:25:12.850 align:start position:0% top of my advancement cool new ways as I mentioned<02:25:11.720> textile<02:25:12.050> they're<02:25:12.290> building<02:25:12.650> a 02:25:12.850 --> 02:25:12.860 align:start position:0% mentioned textile they're building a 02:25:12.860 --> 02:25:14.890 align:start position:0% mentioned textile they're building a number<02:25:13.280> of<02:25:13.400> SDKs<02:25:13.820> they<02:25:14.000> have<02:25:14.150> an<02:25:14.240> iOS<02:25:14.420> and 02:25:14.890 --> 02:25:14.900 align:start position:0% number of SDKs they have an iOS and 02:25:14.900 --> 02:25:17.440 align:start position:0% number of SDKs they have an iOS and Android<02:25:15.020> SDK<02:25:15.979> right<02:25:16.220> now<02:25:16.400> for<02:25:16.940> building<02:25:17.330> on 02:25:17.440 --> 02:25:17.450 align:start position:0% Android SDK right now for building on 02:25:17.450 --> 02:25:20.230 align:start position:0% Android SDK right now for building on top<02:25:17.660> of<02:25:17.720> IP<02:25:18.110> FS<02:25:18.440> to<02:25:18.770> make<02:25:19.190> mobile<02:25:19.520> apps<02:25:19.670> that 02:25:20.230 --> 02:25:20.240 align:start position:0% top of IP FS to make mobile apps that 02:25:20.240 --> 02:25:21.640 align:start position:0% top of IP FS to make mobile apps that you<02:25:20.390> can<02:25:20.420> also<02:25:20.630> do<02:25:20.840> web<02:25:20.990> apps<02:25:21.170> and<02:25:21.470> build 02:25:21.640 --> 02:25:21.650 align:start position:0% you can also do web apps and build 02:25:21.650 --> 02:25:23.230 align:start position:0% you can also do web apps and build things<02:25:21.800> on<02:25:21.950> top<02:25:22.100> of<02:25:22.160> their<02:25:22.370> network<02:25:22.670> of<02:25:22.820> cafes 02:25:23.230 --> 02:25:23.240 align:start position:0% things on top of their network of cafes 02:25:23.240 --> 02:25:24.969 align:start position:0% things on top of their network of cafes their<02:25:23.720> documentation<02:25:24.290> is<02:25:24.380> beautiful 02:25:24.969 --> 02:25:24.979 align:start position:0% their documentation is beautiful 02:25:24.979 --> 02:25:26.350 align:start position:0% their documentation is beautiful I<02:25:25.010> highly<02:25:25.400> recommend<02:25:25.430> checking<02:25:25.790> it<02:25:26.060> out<02:25:26.150> it's 02:25:26.350 --> 02:25:26.360 align:start position:0% I highly recommend checking it out it's 02:25:26.360 --> 02:25:27.880 align:start position:0% I highly recommend checking it out it's a<02:25:26.450> great<02:25:26.660> way<02:25:26.780> to<02:25:26.810> get<02:25:27.020> started<02:25:27.200> on<02:25:27.470> top<02:25:27.650> of<02:25:27.770> IP 02:25:27.880 --> 02:25:27.890 align:start position:0% a great way to get started on top of IP 02:25:27.890 --> 02:25:29.969 align:start position:0% a great way to get started on top of IP FS<02:25:28.190> they<02:25:28.340> make<02:25:28.490> it<02:25:28.580> really<02:25:28.790> really<02:25:28.820> easy 02:25:29.969 --> 02:25:29.979 align:start position:0% FS they make it really really easy 02:25:29.979 --> 02:25:32.350 align:start position:0% FS they make it really really easy another<02:25:30.979> example<02:25:31.100> is<02:25:31.490> even<02:25:31.729> this<02:25:32.150> is<02:25:32.330> the 02:25:32.350 --> 02:25:32.360 align:start position:0% another example is even this is the 02:25:32.360 --> 02:25:35.740 align:start position:0% another example is even this is the mobile<02:25:32.690> app<02:25:32.930> that<02:25:32.960> the<02:25:33.470> open<02:25:33.860> Bazaar<02:25:34.630> which<02:25:35.630> is 02:25:35.740 --> 02:25:35.750 align:start position:0% mobile app that the open Bazaar which is 02:25:35.750 --> 02:25:37.900 align:start position:0% mobile app that the open Bazaar which is a<02:25:36.010> marketplace<02:25:37.010> for<02:25:37.250> buying<02:25:37.550> and<02:25:37.790> selling 02:25:37.900 --> 02:25:37.910 align:start position:0% a marketplace for buying and selling 02:25:37.910 --> 02:25:39.640 align:start position:0% a marketplace for buying and selling goods<02:25:38.300> on<02:25:38.660> top<02:25:38.870> of<02:25:38.990> that<02:25:39.080> if<02:25:39.260> it's<02:25:39.380> network 02:25:39.640 --> 02:25:39.650 align:start position:0% goods on top of that if it's network 02:25:39.650 --> 02:25:42.700 align:start position:0% goods on top of that if it's network it's<02:25:39.830> fully<02:25:40.270> here<02:25:41.270> and<02:25:42.080> they<02:25:42.320> have<02:25:42.440> a<02:25:42.470> really 02:25:42.700 --> 02:25:42.710 align:start position:0% it's fully here and they have a really 02:25:42.710 --> 02:25:45.160 align:start position:0% it's fully here and they have a really slick<02:25:43.190> new<02:25:43.430> mobile<02:25:43.760> app<02:25:43.880> built<02:25:44.150> on<02:25:44.330> top<02:25:44.510> of<02:25:44.570> I 02:25:45.160 --> 02:25:45.170 align:start position:0% slick new mobile app built on top of I 02:25:45.170 --> 02:25:46.620 align:start position:0% slick new mobile app built on top of I think<02:25:45.470> both<02:25:45.650> for<02:25:45.680> Android<02:25:46.040> and<02:25:46.250> for<02:25:46.310> iOS 02:25:46.620 --> 02:25:46.630 align:start position:0% think both for Android and for iOS 02:25:46.630 --> 02:25:48.640 align:start position:0% think both for Android and for iOS building<02:25:47.630> I<02:25:47.690> might<02:25:47.810> invest<02:25:48.110> that<02:25:48.229> you<02:25:48.320> can<02:25:48.500> use 02:25:48.640 --> 02:25:48.650 align:start position:0% building I might invest that you can use 02:25:48.650 --> 02:25:51.040 align:start position:0% building I might invest that you can use highly<02:25:49.340> recommend<02:25:49.700> it<02:25:49.790> it's<02:25:50.000> like<02:25:50.479> beautiful 02:25:51.040 --> 02:25:51.050 align:start position:0% highly recommend it it's like beautiful 02:25:51.050 --> 02:25:52.690 align:start position:0% highly recommend it it's like beautiful thanks<02:25:51.890> for<02:25:51.979> them<02:25:52.100> thank<02:25:52.280> you<02:25:52.310> they<02:25:52.460> move<02:25:52.640> a 02:25:52.690 --> 02:25:52.700 align:start position:0% thanks for them thank you they move a 02:25:52.700 --> 02:25:55.150 align:start position:0% thanks for them thank you they move a lot<02:25:52.850> I<02:25:52.880> would<02:25:53.120> say<02:25:53.710> and<02:25:54.710> then<02:25:54.920> there's<02:25:55.040> also 02:25:55.150 --> 02:25:55.160 align:start position:0% lot I would say and then there's also 02:25:55.160 --> 02:25:57.550 align:start position:0% lot I would say and then there's also birdie<02:25:55.460> this<02:25:55.670> is<02:25:55.850> still<02:25:56.300> in<02:25:56.540> the<02:25:56.720> works<02:25:56.960> still 02:25:57.550 --> 02:25:57.560 align:start position:0% birdie this is still in the works still 02:25:57.560 --> 02:25:59.200 align:start position:0% birdie this is still in the works still a<02:25:57.590> work<02:25:57.770> in<02:25:57.860> progress<02:25:57.920> but<02:25:58.430> they<02:25:58.580> made<02:25:58.790> a<02:25:59.000> new 02:25:59.200 --> 02:25:59.210 align:start position:0% a work in progress but they made a new 02:25:59.210 --> 02:26:01.510 align:start position:0% a work in progress but they made a new awesome<02:25:59.540> Bluetooth<02:26:00.440> transport<02:26:00.979> for<02:26:01.160> the<02:26:01.250> p2p 02:26:01.510 --> 02:26:01.520 align:start position:0% awesome Bluetooth transport for the p2p 02:26:01.520 --> 02:26:03.340 align:start position:0% awesome Bluetooth transport for the p2p which<02:26:01.940> is<02:26:02.090> super<02:26:02.450> cool<02:26:02.690> so<02:26:02.960> you<02:26:03.050> can<02:26:03.170> actually 02:26:03.340 --> 02:26:03.350 align:start position:0% which is super cool so you can actually 02:26:03.350 --> 02:26:05.950 align:start position:0% which is super cool so you can actually do<02:26:03.710> fully<02:26:04.310> end-to-end<02:26:04.940> encrypted<02:26:05.270> offline 02:26:05.950 --> 02:26:05.960 align:start position:0% do fully end-to-end encrypted offline 02:26:05.960 --> 02:26:08.530 align:start position:0% do fully end-to-end encrypted offline mobile<02:26:06.770> chat<02:26:06.979> so<02:26:07.490> just<02:26:07.760> here<02:26:08.090> with<02:26:08.240> the<02:26:08.300> people 02:26:08.530 --> 02:26:08.540 align:start position:0% mobile chat so just here with the people 02:26:08.540 --> 02:26:09.880 align:start position:0% mobile chat so just here with the people next<02:26:08.660> to<02:26:08.840> you<02:26:08.930> and<02:26:08.990> then<02:26:09.320> you're<02:26:09.410> able<02:26:09.470> to<02:26:09.620> sign 02:26:09.880 --> 02:26:09.890 align:start position:0% next to you and then you're able to sign 02:26:09.890 --> 02:26:11.860 align:start position:0% next to you and then you're able to sign messages<02:26:10.400> back<02:26:10.610> and<02:26:10.640> forth<02:26:10.820> no<02:26:11.510> internet 02:26:11.860 --> 02:26:11.870 align:start position:0% messages back and forth no internet 02:26:11.870 --> 02:26:14.469 align:start position:0% messages back and forth no internet connection<02:26:12.290> and<02:26:12.350> no<02:26:12.470> anything<02:26:13.000> I<02:26:14.000> was<02:26:14.210> also<02:26:14.450> I 02:26:14.469 --> 02:26:14.479 align:start position:0% connection and no anything I was also I 02:26:14.479 --> 02:26:15.910 align:start position:0% connection and no anything I was also I think<02:26:14.600> I<02:26:14.720> would<02:26:14.870> if<02:26:15.110> I<02:26:15.200> confess<02:26:15.470> camp<02:26:15.740> and 02:26:15.910 --> 02:26:15.920 align:start position:0% think I would if I confess camp and 02:26:15.920 --> 02:26:17.830 align:start position:0% think I would if I confess camp and we're<02:26:16.610> continuing<02:26:17.270> to<02:26:17.300> push<02:26:17.479> on<02:26:17.600> them<02:26:17.690> they're 02:26:17.830 --> 02:26:17.840 align:start position:0% we're continuing to push on them they're 02:26:17.840 --> 02:26:19.300 align:start position:0% we're continuing to push on them they're planning<02:26:18.080> to<02:26:18.110> make<02:26:18.290> it<02:26:18.440> a<02:26:18.590> fully<02:26:18.979> open<02:26:19.160> source 02:26:19.300 --> 02:26:19.310 align:start position:0% planning to make it a fully open source 02:26:19.310 --> 02:26:21.190 align:start position:0% planning to make it a fully open source but<02:26:19.790> I<02:26:19.850> don't<02:26:20.000> think<02:26:20.150> it's<02:26:20.240> quite 02:26:21.190 --> 02:26:21.200 align:start position:0% but I don't think it's quite 02:26:21.200 --> 02:26:23.980 align:start position:0% but I don't think it's quite yeah<02:26:21.460> it's<02:26:22.460> something<02:26:22.580> to<02:26:22.729> watch<02:26:22.820> out<02:26:23.000> for<02:26:23.030> on 02:26:23.980 --> 02:26:23.990 align:start position:0% yeah it's something to watch out for on 02:26:23.990 --> 02:26:25.600 align:start position:0% yeah it's something to watch out for on the<02:26:24.140> identity<02:26:24.439> sighs<02:26:24.770> you<02:26:25.010> ports<02:26:25.280> been<02:26:25.430> around 02:26:25.600 --> 02:26:25.610 align:start position:0% the identity sighs you ports been around 02:26:25.610 --> 02:26:27.400 align:start position:0% the identity sighs you ports been around for<02:26:25.760> a<02:26:25.790> while<02:26:25.850> they<02:26:26.300> build<02:26:26.420> on<02:26:26.600> top<02:26:26.689> of<02:26:26.750> a<02:26:26.990> PMS 02:26:27.400 --> 02:26:27.410 align:start position:0% for a while they build on top of a PMS 02:26:27.410 --> 02:26:30.160 align:start position:0% for a while they build on top of a PMS for<02:26:27.770> looking<02:26:28.310> up<02:26:28.370> identity<02:26:28.880> documents<02:26:29.479> and 02:26:30.160 --> 02:26:30.170 align:start position:0% for looking up identity documents and 02:26:30.170 --> 02:26:32.200 align:start position:0% for looking up identity documents and there's<02:26:30.350> also<02:26:30.439> now<02:26:30.650> free<02:26:31.280> box<02:26:31.490> which<02:26:31.790> is<02:26:31.939> super 02:26:32.200 --> 02:26:32.210 align:start position:0% there's also now free box which is super 02:26:32.210 --> 02:26:34.060 align:start position:0% there's also now free box which is super cool<02:26:32.479> and<02:26:32.510> they're<02:26:32.720> doing<02:26:32.930> kind<02:26:33.110> of<02:26:33.200> user<02:26:33.710> app 02:26:34.060 --> 02:26:34.070 align:start position:0% cool and they're doing kind of user app 02:26:34.070 --> 02:26:36.700 align:start position:0% cool and they're doing kind of user app profile<02:26:34.640> data<02:26:35.270> stores<02:26:35.600> on<02:26:35.960> top<02:26:36.110> of<02:26:36.229> IP<02:26:36.350> address 02:26:36.700 --> 02:26:36.710 align:start position:0% profile data stores on top of IP address 02:26:36.710 --> 02:26:39.130 align:start position:0% profile data stores on top of IP address use<02:26:37.220> a<02:26:37.370> Normandy<02:26:37.820> B<02:26:37.939> so<02:26:38.780> that's<02:26:38.930> kind<02:26:39.110> of 02:26:39.130 --> 02:26:39.140 align:start position:0% use a Normandy B so that's kind of 02:26:39.140 --> 02:26:42.070 align:start position:0% use a Normandy B so that's kind of another<02:26:39.670> database<02:26:40.670> style<02:26:41.120> tool<02:26:41.420> on<02:26:41.660> top<02:26:41.689> of<02:26:41.960> IP 02:26:42.070 --> 02:26:42.080 align:start position:0% another database style tool on top of IP 02:26:42.080 --> 02:26:45.700 align:start position:0% another database style tool on top of IP MS<02:26:42.410> that<02:26:43.040> lets<02:26:43.189> you<02:26:43.360> store<02:26:44.360> data<02:26:44.420> and<02:26:44.960> this<02:26:45.590> is 02:26:45.700 --> 02:26:45.710 align:start position:0% MS that lets you store data and this is 02:26:45.710 --> 02:26:47.170 align:start position:0% MS that lets you store data and this is super<02:26:45.920> cool<02:26:46.070> I<02:26:46.340> think<02:26:46.700> some<02:26:46.820> of<02:26:46.850> those<02:26:46.970> guys 02:26:47.170 --> 02:26:47.180 align:start position:0% super cool I think some of those guys 02:26:47.180 --> 02:26:51.400 align:start position:0% super cool I think some of those guys are<02:26:47.300> an<02:26:47.360> audience<02:26:47.689> up<02:26:47.870> go<02:26:48.410> chat<02:26:48.590> with<02:26:48.620> Mark<02:26:50.410> and 02:26:51.400 --> 02:26:51.410 align:start position:0% are an audience up go chat with Mark and 02:26:51.410 --> 02:26:53.050 align:start position:0% are an audience up go chat with Mark and then<02:26:51.590> finally<02:26:51.890> there's<02:26:52.189> the<02:26:52.520> Identity 02:26:53.050 --> 02:26:53.060 align:start position:0% then finally there's the Identity 02:26:53.060 --> 02:26:54.820 align:start position:0% then finally there's the Identity Manager<02:26:53.420> this<02:26:53.630> is<02:26:53.780> kind<02:26:53.960> of<02:26:53.990> a<02:26:54.110> spec<02:26:54.470> and<02:26:54.650> they 02:26:54.820 --> 02:26:54.830 align:start position:0% Manager this is kind of a spec and they 02:26:54.830 --> 02:26:56.679 align:start position:0% Manager this is kind of a spec and they also<02:26:54.950> built<02:26:55.220> a<02:26:55.340> proof<02:26:55.610> of<02:26:55.760> concept<02:26:56.030> of<02:26:56.510> it 02:26:56.679 --> 02:26:56.689 align:start position:0% also built a proof of concept of it 02:26:56.689 --> 02:26:58.540 align:start position:0% also built a proof of concept of it working<02:26:57.050> in<02:26:57.170> practice<02:26:57.290> this<02:26:57.890> is<02:26:58.070> trying<02:26:58.340> to<02:26:58.460> do 02:26:58.540 --> 02:26:58.550 align:start position:0% working in practice this is trying to do 02:26:58.550 --> 02:27:01.750 align:start position:0% working in practice this is trying to do this<02:26:59.420> is<02:26:59.570> trying<02:26:59.780> to<02:26:59.900> do<02:27:00.020> and<02:27:00.430> so<02:27:01.430> that<02:27:01.550> you<02:27:01.610> can 02:27:01.750 --> 02:27:01.760 align:start position:0% this is trying to do and so that you can 02:27:01.760 --> 02:27:03.520 align:start position:0% this is trying to do and so that you can log<02:27:01.970> in<02:27:02.150> with<02:27:02.180> many<02:27:02.600> different<02:27:02.930> identity 02:27:03.520 --> 02:27:03.530 align:start position:0% log in with many different identity 02:27:03.530 --> 02:27:05.230 align:start position:0% log in with many different identity types<02:27:03.770> say<02:27:04.100> you<02:27:04.160> have<02:27:04.370> three<02:27:04.670> box<02:27:04.850> identity 02:27:05.230 --> 02:27:05.240 align:start position:0% types say you have three box identity 02:27:05.240 --> 02:27:07.300 align:start position:0% types say you have three box identity and<02:27:05.510> you<02:27:05.780> poured<02:27:05.990> a<02:27:06.050> movie<02:27:06.380> and<02:27:06.650> the<02:27:06.740> IPS 02:27:07.300 --> 02:27:07.310 align:start position:0% and you poured a movie and the IPS 02:27:07.310 --> 02:27:09.790 align:start position:0% and you poured a movie and the IPS identity<02:27:07.790> of<02:27:08.120> the<02:27:08.240> some<02:27:09.050> other<02:27:09.260> somewhere 02:27:09.790 --> 02:27:09.800 align:start position:0% identity of the some other somewhere 02:27:09.800 --> 02:27:12.070 align:start position:0% identity of the some other somewhere identity<02:27:10.520> you<02:27:10.939> can<02:27:10.970> use<02:27:11.330> all<02:27:11.750> of<02:27:11.780> these<02:27:12.020> things 02:27:12.070 --> 02:27:12.080 align:start position:0% identity you can use all of these things 02:27:12.080 --> 02:27:14.290 align:start position:0% identity you can use all of these things in<02:27:12.530> one<02:27:12.740> identity<02:27:13.340> wallet<02:27:13.700> so<02:27:13.850> you<02:27:13.910> can<02:27:13.970> pick 02:27:14.290 --> 02:27:14.300 align:start position:0% in one identity wallet so you can pick 02:27:14.300 --> 02:27:15.790 align:start position:0% in one identity wallet so you can pick which<02:27:14.570> I<02:27:14.750> guess<02:27:14.900> it<02:27:15.050> you<02:27:15.229> want<02:27:15.410> to<02:27:15.470> use<02:27:15.620> in 02:27:15.790 --> 02:27:15.800 align:start position:0% which I guess it you want to use in 02:27:15.800 --> 02:27:17.560 align:start position:0% which I guess it you want to use in which<02:27:15.920> different<02:27:16.189> application<02:27:16.640> it<02:27:17.300> still 02:27:17.560 --> 02:27:17.570 align:start position:0% which different application it still 02:27:17.570 --> 02:27:18.900 align:start position:0% which different application it still this<02:27:17.780> is<02:27:17.930> just<02:27:18.110> a<02:27:18.260> proof<02:27:18.500> of<02:27:18.650> concept 02:27:18.900 --> 02:27:18.910 align:start position:0% this is just a proof of concept 02:27:18.910 --> 02:27:20.860 align:start position:0% this is just a proof of concept implementing<02:27:19.910> the<02:27:20.180> spec<02:27:20.450> that<02:27:20.630> they've 02:27:20.860 --> 02:27:20.870 align:start position:0% implementing the spec that they've 02:27:20.870 --> 02:27:22.929 align:start position:0% implementing the spec that they've designed<02:27:21.140> but<02:27:21.770> super<02:27:22.189> exciting<02:27:22.550> stuff<02:27:22.729> all 02:27:22.929 --> 02:27:22.939 align:start position:0% designed but super exciting stuff all 02:27:22.939 --> 02:27:25.960 align:start position:0% designed but super exciting stuff all those<02:27:23.150> on<02:27:23.300> top<02:27:23.390> of<02:27:23.540> the<02:27:23.660> IDs<02:27:23.960> and<02:27:24.970> super 02:27:25.960 --> 02:27:25.970 align:start position:0% those on top of the IDs and super 02:27:25.970 --> 02:27:27.100 align:start position:0% those on top of the IDs and super interested<02:27:26.300> in<02:27:26.420> collaborating<02:27:26.600> with<02:27:26.960> more 02:27:27.100 --> 02:27:27.110 align:start position:0% interested in collaborating with more 02:27:27.110 --> 02:27:29.440 align:start position:0% interested in collaborating with more people<02:27:27.410> to<02:27:27.530> utilize<02:27:27.680> in<02:27:28.640> real<02:27:29.060> world<02:27:29.270> use 02:27:29.440 --> 02:27:29.450 align:start position:0% people to utilize in real world use 02:27:29.450 --> 02:27:33.580 align:start position:0% people to utilize in real world use cases<02:27:31.330> my<02:27:32.330> locks<02:27:32.540> image<02:27:32.750> it's<02:27:33.140> just<02:27:33.320> there's 02:27:33.580 --> 02:27:33.590 align:start position:0% cases my locks image it's just there's 02:27:33.590 --> 02:27:34.900 align:start position:0% cases my locks image it's just there's so<02:27:33.710> many<02:27:33.800> more<02:27:33.979> things<02:27:34.189> here<02:27:34.460> but<02:27:34.610> I<02:27:34.700> want<02:27:34.850> to 02:27:34.900 --> 02:27:34.910 align:start position:0% so many more things here but I want to 02:27:34.910 --> 02:27:36.100 align:start position:0% so many more things here but I want to call<02:27:35.030> it<02:27:35.060> three<02:27:35.450> just<02:27:35.689> cuz<02:27:35.810> I<02:27:35.840> think<02:27:35.930> that 02:27:36.100 --> 02:27:36.110 align:start position:0% call it three just cuz I think that 02:27:36.110 --> 02:27:38.110 align:start position:0% call it three just cuz I think that super<02:27:36.350> cool<02:27:36.560> there's<02:27:37.040> matters<02:27:37.460> news<02:27:37.729> which<02:27:38.090> is 02:27:38.110 --> 02:27:38.120 align:start position:0% super cool there's matters news which is 02:27:38.120 --> 02:27:42.400 align:start position:0% super cool there's matters news which is doing<02:27:38.570> an<02:27:38.900> a<02:27:39.820> Chinese<02:27:40.820> kind<02:27:41.720> of<02:27:41.810> new<02:27:41.960> sharing 02:27:42.400 --> 02:27:42.410 align:start position:0% doing an a Chinese kind of new sharing 02:27:42.410 --> 02:27:44.290 align:start position:0% doing an a Chinese kind of new sharing application<02:27:42.890> so<02:27:43.130> that<02:27:43.250> you<02:27:43.550> as<02:27:43.729> a<02:27:43.760> person 02:27:44.290 --> 02:27:44.300 align:start position:0% application so that you as a person 02:27:44.300 --> 02:27:46.300 align:start position:0% application so that you as a person who's<02:27:44.600> writing<02:27:44.840> the<02:27:45.140> content<02:27:45.710> contribute<02:27:46.250> to 02:27:46.300 --> 02:27:46.310 align:start position:0% who's writing the content contribute to 02:27:46.310 --> 02:27:47.740 align:start position:0% who's writing the content contribute to this<02:27:46.370> website<02:27:46.700> you<02:27:47.060> really<02:27:47.300> own<02:27:47.450> your<02:27:47.479> data 02:27:47.740 --> 02:27:47.750 align:start position:0% this website you really own your data 02:27:47.750 --> 02:27:50.050 align:start position:0% this website you really own your data it's<02:27:48.050> kind<02:27:48.229> of<02:27:48.260> like<02:27:48.380> medium<02:27:49.100> but<02:27:49.400> you<02:27:49.790> can 02:27:50.050 --> 02:27:50.060 align:start position:0% it's kind of like medium but you can 02:27:50.060 --> 02:27:51.700 align:start position:0% it's kind of like medium but you can actually<02:27:50.240> pick<02:27:50.810> up<02:27:50.900> all<02:27:51.050> your<02:27:51.170> data<02:27:51.290> and<02:27:51.439> go 02:27:51.700 --> 02:27:51.710 align:start position:0% actually pick up all your data and go 02:27:51.710 --> 02:27:54.040 align:start position:0% actually pick up all your data and go and<02:27:51.979> take<02:27:52.130> this<02:27:52.250> full<02:27:52.490> site<02:27:52.670> with<02:27:52.820> you<02:27:53.050> it's 02:27:54.040 --> 02:27:54.050 align:start position:0% and take this full site with you it's 02:27:54.050 --> 02:27:55.750 align:start position:0% and take this full site with you it's radical<02:27:54.590> I<02:27:54.680> think<02:27:54.860> someone<02:27:55.100> from<02:27:55.189> radicals<02:27:55.670> in 02:27:55.750 --> 02:27:55.760 align:start position:0% radical I think someone from radicals in 02:27:55.760 --> 02:27:57.310 align:start position:0% radical I think someone from radicals in there<02:27:55.850> right<02:27:56.030> yeah<02:27:56.510> go<02:27:56.900> chat<02:27:57.080> with<02:27:57.110> her<02:27:57.290> about 02:27:57.310 --> 02:27:57.320 align:start position:0% there right yeah go chat with her about 02:27:57.320 --> 02:27:59.080 align:start position:0% there right yeah go chat with her about radical<02:27:57.920> probably<02:27:58.220> super<02:27:58.490> cool<02:27:58.700> she's<02:27:58.970> gonna 02:27:59.080 --> 02:27:59.090 align:start position:0% radical probably super cool she's gonna 02:27:59.090 --> 02:28:00.160 align:start position:0% radical probably super cool she's gonna know<02:27:59.240> about<02:27:59.330> a<02:27:59.420> lightning<02:27:59.630> strike<02:27:59.930> on<02:27:59.990> this 02:28:00.160 --> 02:28:00.170 align:start position:0% know about a lightning strike on this 02:28:00.170 --> 02:28:03.429 align:start position:0% know about a lightning strike on this awesome<02:28:01.130> even<02:28:01.700> better<02:28:01.850> you<02:28:02.780> can<02:28:02.810> hear<02:28:03.320> more 02:28:03.429 --> 02:28:03.439 align:start position:0% awesome even better you can hear more 02:28:03.439 --> 02:28:05.110 align:start position:0% awesome even better you can hear more about<02:28:03.530> this<02:28:03.710> in<02:28:03.830> a<02:28:03.860> second<02:28:04.250> and<02:28:04.550> finally<02:28:04.910> I'm 02:28:05.110 --> 02:28:05.120 align:start position:0% about this in a second and finally I'm 02:28:05.120 --> 02:28:07.210 align:start position:0% about this in a second and finally I'm also<02:28:05.750> an<02:28:05.960> identity<02:28:06.110> space<02:28:06.500> Microsoft<02:28:07.130> just 02:28:07.210 --> 02:28:07.220 align:start position:0% also an identity space Microsoft just 02:28:07.220 --> 02:28:10.410 align:start position:0% also an identity space Microsoft just watch<02:28:07.880> this<02:28:08.180> yet<02:28:08.810> even<02:28:08.930> thing<02:28:09.170> called<02:28:09.320> an<02:28:09.380> ion 02:28:10.410 --> 02:28:10.420 align:start position:0% watch this yet even thing called an ion 02:28:10.420 --> 02:28:14.590 align:start position:0% watch this yet even thing called an ion okay<02:28:11.470> quickly<02:28:12.970> in<02:28:13.970> my<02:28:14.060> last<02:28:14.270> three<02:28:14.479> minutes 02:28:14.590 --> 02:28:14.600 align:start position:0% okay quickly in my last three minutes 02:28:14.600 --> 02:28:16.929 align:start position:0% okay quickly in my last three minutes accessing<02:28:15.439> IVFs<02:28:15.800> has<02:28:16.010> also<02:28:16.250> gotten<02:28:16.670> a<02:28:16.790> lot 02:28:16.929 --> 02:28:16.939 align:start position:0% accessing IVFs has also gotten a lot 02:28:16.939 --> 02:28:19.840 align:start position:0% accessing IVFs has also gotten a lot easier<02:28:17.380> desktop<02:28:18.380> and<02:28:18.590> what<02:28:18.680> UI<02:28:18.890> are<02:28:19.250> too<02:28:19.490> kind 02:28:19.840 --> 02:28:19.850 align:start position:0% easier desktop and what UI are too kind 02:28:19.850 --> 02:28:22.900 align:start position:0% easier desktop and what UI are too kind of<02:28:20.000> and<02:28:20.180> user<02:28:20.750> tools<02:28:21.200> that<02:28:21.560> we<02:28:22.400> created<02:28:22.700> in<02:28:22.880> the 02:28:22.900 --> 02:28:22.910 align:start position:0% of and user tools that we created in the 02:28:22.910 --> 02:28:23.439 align:start position:0% of and user tools that we created in the project 02:28:23.439 --> 02:28:23.449 align:start position:0% project 02:28:23.449 --> 02:28:25.840 align:start position:0% project to<02:28:23.569> make<02:28:24.169> it<02:28:24.289> easy<02:28:24.499> to<02:28:24.770> access<02:28:25.100> and<02:28:25.459> run<02:28:25.549> an<02:28:25.699> IP 02:28:25.840 --> 02:28:25.850 align:start position:0% to make it easy to access and run an IP 02:28:25.850 --> 02:28:27.340 align:start position:0% to make it easy to access and run an IP let's<02:28:26.089> note<02:28:26.239> highly<02:28:26.899> recommend<02:28:27.259> getting 02:28:27.340 --> 02:28:27.350 align:start position:0% let's note highly recommend getting 02:28:27.350 --> 02:28:28.869 align:start position:0% let's note highly recommend getting started<02:28:27.799> with<02:28:27.919> desktop<02:28:28.249> if<02:28:28.579> you<02:28:28.669> don't 02:28:28.869 --> 02:28:28.879 align:start position:0% started with desktop if you don't 02:28:28.879 --> 02:28:30.219 align:start position:0% started with desktop if you don't currently<02:28:29.119> around<02:28:29.419> an<02:28:29.629> IT<02:28:29.749> investment<02:28:30.140> it's 02:28:30.219 --> 02:28:30.229 align:start position:0% currently around an IT investment it's 02:28:30.229 --> 02:28:32.170 align:start position:0% currently around an IT investment it's really<02:28:30.439> easy<02:28:30.649> you<02:28:30.979> can<02:28:31.279> add<02:28:31.399> IPS<02:28:31.819> to<02:28:31.909> your<02:28:31.999> tool 02:28:32.170 --> 02:28:32.180 align:start position:0% really easy you can add IPS to your tool 02:28:32.180 --> 02:28:36.099 align:start position:0% really easy you can add IPS to your tool team<02:28:32.419> you<02:28:32.959> have<02:28:33.140> a<02:28:33.169> persistent<02:28:34.209> like<02:28:35.209> widget 02:28:36.099 --> 02:28:36.109 align:start position:0% team you have a persistent like widget 02:28:36.109 --> 02:28:38.349 align:start position:0% team you have a persistent like widget in<02:28:36.289> your<02:28:36.499> address<02:28:37.249> book<02:28:37.430> earlier<02:28:37.759> whatever 02:28:38.349 --> 02:28:38.359 align:start position:0% in your address book earlier whatever 02:28:38.359 --> 02:28:40.119 align:start position:0% in your address book earlier whatever top<02:28:38.930> bar<02:28:39.140> that<02:28:39.439> you're<02:28:39.499> going<02:28:39.649> to<02:28:39.709> play<02:28:39.919> with 02:28:40.119 --> 02:28:40.129 align:start position:0% top bar that you're going to play with 02:28:40.129 --> 02:28:41.649 align:start position:0% top bar that you're going to play with and<02:28:40.520> you<02:28:40.640> also<02:28:40.850> get<02:28:41.029> all<02:28:41.149> these<02:28:41.329> beautiful 02:28:41.649 --> 02:28:41.659 align:start position:0% and you also get all these beautiful 02:28:41.659 --> 02:28:43.269 align:start position:0% and you also get all these beautiful visualizations<02:28:42.079> at<02:28:42.619> the<02:28:42.709> files<02:28:43.009> you're 02:28:43.269 --> 02:28:43.279 align:start position:0% visualizations at the files you're 02:28:43.279 --> 02:28:44.829 align:start position:0% visualizations at the files you're pinning<02:28:43.520> and<02:28:43.819> what<02:28:43.909> nodes<02:28:44.299> you're<02:28:44.390> connected 02:28:44.829 --> 02:28:44.839 align:start position:0% pinning and what nodes you're connected 02:28:44.839 --> 02:28:47.439 align:start position:0% pinning and what nodes you're connected to<02:28:45.020> and<02:28:45.259> all<02:28:45.319> this<02:28:45.439> other<02:28:45.619> exciting<02:28:45.890> stuff<02:28:46.449> you 02:28:47.439 --> 02:28:47.449 align:start position:0% to and all this other exciting stuff you 02:28:47.449 --> 02:28:49.510 align:start position:0% to and all this other exciting stuff you could<02:28:47.629> run<02:28:47.930> it<02:28:48.049> you're<02:28:48.709> connecting<02:28:49.069> with<02:28:49.159> IBM 02:28:49.510 --> 02:28:49.520 align:start position:0% could run it you're connecting with IBM 02:28:49.520 --> 02:28:51.279 align:start position:0% could run it you're connecting with IBM s<02:28:49.609> companion<02:28:50.180> which<02:28:50.629> is<02:28:50.779> a<02:28:50.959> browser<02:28:51.169> extension 02:28:51.279 --> 02:28:51.289 align:start position:0% s companion which is a browser extension 02:28:51.289 --> 02:28:53.559 align:start position:0% s companion which is a browser extension we've<02:28:51.890> created<02:28:52.129> for<02:28:52.310> Chrome<02:28:52.699> and<02:28:52.729> for<02:28:53.180> Firefox 02:28:53.559 --> 02:28:53.569 align:start position:0% we've created for Chrome and for Firefox 02:28:53.569 --> 02:28:56.529 align:start position:0% we've created for Chrome and for Firefox which<02:28:54.020> now<02:28:54.199> has<02:28:54.409> 20<02:28:54.770> 20<02:28:55.459> K<02:28:55.640> people<02:28:56.149> using<02:28:56.449> it 02:28:56.529 --> 02:28:56.539 align:start position:0% which now has 20 20 K people using it 02:28:56.539 --> 02:28:57.760 align:start position:0% which now has 20 20 K people using it super<02:28:57.199> exciting 02:28:57.760 --> 02:28:57.770 align:start position:0% super exciting 02:28:57.770 --> 02:29:00.130 align:start position:0% super exciting speaking<02:28:58.549> of<02:28:58.699> companion<02:28:59.239> it's<02:28:59.539> also<02:28:59.779> now 02:29:00.130 --> 02:29:00.140 align:start position:0% speaking of companion it's also now 02:29:00.140 --> 02:29:02.139 align:start position:0% speaking of companion it's also now integrated<02:29:00.799> with<02:29:00.829> braid<02:29:01.219> directly<02:29:01.819> so<02:29:02.119> that 02:29:02.139 --> 02:29:02.149 align:start position:0% integrated with braid directly so that 02:29:02.149 --> 02:29:04.119 align:start position:0% integrated with braid directly so that you<02:29:02.299> can<02:29:02.479> just<02:29:02.659> install<02:29:03.079> brave<02:29:03.289> go<02:29:03.829> to<02:29:03.890> your 02:29:04.119 --> 02:29:04.129 align:start position:0% you can just install brave go to your 02:29:04.129 --> 02:29:06.789 align:start position:0% you can just install brave go to your like<02:29:04.399> little<02:29:04.879> settings<02:29:05.239> area<02:29:05.449> and<02:29:05.779> I<02:29:06.379> think 02:29:06.789 --> 02:29:06.799 align:start position:0% like little settings area and I think 02:29:06.799 --> 02:29:09.369 align:start position:0% like little settings area and I think this<02:29:06.979> companion<02:29:07.459> is<02:29:07.609> default<02:29:08.149> can't<02:29:09.140> really 02:29:09.369 --> 02:29:09.379 align:start position:0% this companion is default can't really 02:29:09.379 --> 02:29:11.109 align:start position:0% this companion is default can't really see<02:29:09.499> it<02:29:09.589> this<02:29:09.739> time<02:29:09.919> in<02:29:10.189> Java<02:29:10.399> but<02:29:10.549> you're<02:29:10.999> just 02:29:11.109 --> 02:29:11.119 align:start position:0% see it this time in Java but you're just 02:29:11.119 --> 02:29:12.880 align:start position:0% see it this time in Java but you're just toggle<02:29:11.449> that<02:29:11.539> button<02:29:11.839> you<02:29:12.229> get<02:29:12.319> a<02:29:12.379> companion 02:29:12.880 --> 02:29:12.890 align:start position:0% toggle that button you get a companion 02:29:12.890 --> 02:29:14.649 align:start position:0% toggle that button you get a companion at<02:29:13.069> it<02:29:13.219> and<02:29:13.399> it<02:29:13.489> also<02:29:13.669> gets<02:29:13.879> access<02:29:14.390> to<02:29:14.509> things 02:29:14.649 --> 02:29:14.659 align:start position:0% at it and it also gets access to things 02:29:14.659 --> 02:29:16.359 align:start position:0% at it and it also gets access to things like<02:29:14.779> the<02:29:14.959> chrome<02:29:15.140> sockets<02:29:15.529> API<02:29:15.829> so<02:29:16.129> if<02:29:16.189> you<02:29:16.279> do 02:29:16.359 --> 02:29:16.369 align:start position:0% like the chrome sockets API so if you do 02:29:16.369 --> 02:29:18.130 align:start position:0% like the chrome sockets API so if you do some<02:29:16.549> really<02:29:16.729> cool<02:29:16.969> stuff<02:29:17.029> so<02:29:17.479> expect<02:29:18.079> more 02:29:18.130 --> 02:29:18.140 align:start position:0% some really cool stuff so expect more 02:29:18.140 --> 02:29:20.380 align:start position:0% some really cool stuff so expect more more<02:29:18.949> exciting<02:29:19.399> news<02:29:19.549> to<02:29:19.729> come<02:29:19.909> there<02:29:20.089> but 02:29:20.380 --> 02:29:20.390 align:start position:0% more exciting news to come there but 02:29:20.390 --> 02:29:22.599 align:start position:0% more exciting news to come there but it's<02:29:21.049> it's<02:29:21.439> letting<02:29:21.739> setting<02:29:22.189> you<02:29:22.279> up<02:29:22.310> where 02:29:22.599 --> 02:29:22.609 align:start position:0% it's it's letting setting you up where 02:29:22.609 --> 02:29:24.429 align:start position:0% it's it's letting setting you up where you<02:29:22.729> can<02:29:22.909> do<02:29:23.060> kind<02:29:23.270> of<02:29:23.359> mdns<02:29:23.779> connections<02:29:24.229> to 02:29:24.429 --> 02:29:24.439 align:start position:0% you can do kind of mdns connections to 02:29:24.439 --> 02:29:26.349 align:start position:0% you can do kind of mdns connections to many<02:29:24.589> people<02:29:24.859> in<02:29:24.919> a<02:29:24.979> room<02:29:25.159> over<02:29:25.819> brave<02:29:26.060> and 02:29:26.349 --> 02:29:26.359 align:start position:0% many people in a room over brave and 02:29:26.359 --> 02:29:28.630 align:start position:0% many people in a room over brave and directly<02:29:26.659> share<02:29:27.140> with<02:29:27.259> each<02:29:27.379> other<02:29:27.640> they're 02:29:28.630 --> 02:29:28.640 align:start position:0% directly share with each other they're 02:29:28.640 --> 02:29:30.639 align:start position:0% directly share with each other they're also<02:29:28.759> working<02:29:28.999> on<02:29:29.239> adding<02:29:29.419> some<02:29:29.509> nice<02:29:29.779> IP<02:29:30.350> best 02:29:30.639 --> 02:29:30.649 align:start position:0% also working on adding some nice IP best 02:29:30.649 --> 02:29:32.439 align:start position:0% also working on adding some nice IP best colon<02:29:30.979> slash<02:29:31.129> slash<02:29:31.310> so<02:29:31.939> that<02:29:32.060> you<02:29:32.119> know<02:29:32.270> when 02:29:32.439 --> 02:29:32.449 align:start position:0% colon slash slash so that you know when 02:29:32.449 --> 02:29:33.819 align:start position:0% colon slash slash so that you know when you're<02:29:32.539> accessing<02:29:32.810> it<02:29:33.049> might<02:29:33.140> be<02:29:33.229> FS<02:29:33.439> URL 02:29:33.819 --> 02:29:33.829 align:start position:0% you're accessing it might be FS URL 02:29:33.829 --> 02:29:36.159 align:start position:0% you're accessing it might be FS URL directly<02:29:34.489> within<02:29:34.909> the<02:29:35.060> browser<02:29:35.180> itself<02:29:35.600> and 02:29:36.159 --> 02:29:36.169 align:start position:0% directly within the browser itself and 02:29:36.169 --> 02:29:38.859 align:start position:0% directly within the browser itself and leading<02:29:36.560> the<02:29:36.649> charge<02:29:37.149> opera<02:29:38.149> is<02:29:38.329> also<02:29:38.659> working 02:29:38.859 --> 02:29:38.869 align:start position:0% leading the charge opera is also working 02:29:38.869 --> 02:29:41.800 align:start position:0% leading the charge opera is also working on<02:29:39.489> IQs<02:29:40.489> and<02:29:40.669> the<02:29:40.789> NS<02:29:41.060> support<02:29:41.419> they<02:29:41.569> announced 02:29:41.800 --> 02:29:41.810 align:start position:0% on IQs and the NS support they announced 02:29:41.810 --> 02:29:45.609 align:start position:0% on IQs and the NS support they announced this<02:29:42.020> back<02:29:42.409> in<02:29:42.999> April<02:29:43.999> mini<02:29:44.209> team<02:29:45.049> something 02:29:45.609 --> 02:29:45.619 align:start position:0% this back in April mini team something 02:29:45.619 --> 02:29:46.059 align:start position:0% this back in April mini team something like<02:29:45.739> that 02:29:46.059 --> 02:29:46.069 align:start position:0% like that 02:29:46.069 --> 02:29:49.179 align:start position:0% like that the<02:29:46.819> aim<02:29:47.060> hopefully<02:29:47.959> is<02:29:48.140> that<02:29:48.169> have<02:29:48.469> support 02:29:49.179 --> 02:29:49.189 align:start position:0% the aim hopefully is that have support 02:29:49.189 --> 02:29:52.239 align:start position:0% the aim hopefully is that have support in<02:29:49.939> the<02:29:50.119> end<02:29:50.209> road<02:29:50.449> I<02:29:50.719> ended<02:29:51.199> here<02:29:51.439> and<02:29:51.649> then 02:29:52.239 --> 02:29:52.249 align:start position:0% in the end road I ended here and then 02:29:52.249 --> 02:29:53.469 align:start position:0% in the end road I ended here and then Firefox<02:29:52.669> we've<02:29:52.789> been<02:29:52.909> working<02:29:53.119> on<02:29:53.180> that<02:29:53.209> for<02:29:53.329> a 02:29:53.469 --> 02:29:53.479 align:start position:0% Firefox we've been working on that for a 02:29:53.479 --> 02:29:55.929 align:start position:0% Firefox we've been working on that for a long<02:29:53.600> time<02:29:53.810> they<02:29:54.319> added<02:29:54.850> support<02:29:55.850> for 02:29:55.929 --> 02:29:55.939 align:start position:0% long time they added support for 02:29:55.939 --> 02:29:57.249 align:start position:0% long time they added support for decentralized<02:29:56.329> protocol<02:29:56.749> handlers<02:29:57.079> in 02:29:57.249 --> 02:29:57.259 align:start position:0% decentralized protocol handlers in 02:29:57.259 --> 02:29:59.979 align:start position:0% decentralized protocol handlers in Firefox<02:29:57.619> 59<02:29:58.039> and<02:29:58.339> Lib<02:29:59.119> D<02:29:59.270> web<02:29:59.449> which<02:29:59.689> is<02:29:59.839> that 02:29:59.979 --> 02:29:59.989 align:start position:0% Firefox 59 and Lib D web which is that 02:29:59.989 --> 02:30:02.529 align:start position:0% Firefox 59 and Lib D web which is that kind<02:30:00.289> of<02:30:00.350> generalized<02:30:01.339> supports<02:30:01.909> many<02:30:02.209> many 02:30:02.529 --> 02:30:02.539 align:start position:0% kind of generalized supports many many 02:30:02.539 --> 02:30:05.319 align:start position:0% kind of generalized supports many many different<02:30:02.930> web<02:30:03.499> handlers<02:30:04.009> is<02:30:04.699> currently 02:30:05.319 --> 02:30:05.329 align:start position:0% different web handlers is currently 02:30:05.329 --> 02:30:06.819 align:start position:0% different web handlers is currently working<02:30:05.600> on<02:30:05.899> being<02:30:06.079> integrated<02:30:06.409> into<02:30:06.739> the 02:30:06.819 --> 02:30:06.829 align:start position:0% working on being integrated into the 02:30:06.829 --> 02:30:10.389 align:start position:0% working on being integrated into the Gecko<02:30:07.069> browser<02:30:07.279> engine<02:30:08.649> there's<02:30:09.649> also<02:30:10.009> really 02:30:10.389 --> 02:30:10.399 align:start position:0% Gecko browser engine there's also really 02:30:10.399 --> 02:30:11.290 align:start position:0% Gecko browser engine there's also really exciting<02:30:10.759> stuff<02:30:10.879> happen 02:30:11.290 --> 02:30:11.300 align:start position:0% exciting stuff happen 02:30:11.300 --> 02:30:12.519 align:start position:0% exciting stuff happen in<02:30:11.359> the<02:30:11.479> gateways<02:30:11.840> and<02:30:12.020> pinning<02:30:12.319> space 02:30:12.519 --> 02:30:12.529 align:start position:0% in the gateways and pinning space 02:30:12.529 --> 02:30:14.740 align:start position:0% in the gateways and pinning space there's<02:30:12.829> a<02:30:12.920> ton<02:30:13.159> of<02:30:13.189> computing<02:30:13.699> services<02:30:14.149> not 02:30:14.740 --> 02:30:14.750 align:start position:0% there's a ton of computing services not 02:30:14.750 --> 02:30:16.899 align:start position:0% there's a ton of computing services not over<02:30:15.109> somewhere<02:30:15.619> in<02:30:15.710> here<02:30:15.859> from<02:30:16.100> pinata<02:30:16.399> and 02:30:16.899 --> 02:30:16.909 align:start position:0% over somewhere in here from pinata and 02:30:16.909 --> 02:30:37.559 align:start position:0% over somewhere in here from pinata and that's<02:30:17.899> where<02:30:18.020> anyways<02:30:18.289> and<02:30:18.859> as<02:30:19.789> I<02:30:20.000> expected 02:30:37.559 --> 02:30:37.569 align:start position:0% 02:30:37.569 --> 02:30:40.660 align:start position:0% there's<02:30:38.569> a<02:30:38.659> lot<02:30:38.810> of<02:30:38.930> stuff<02:30:39.109> next<02:30:39.439> I<02:30:39.649> think<02:30:40.520> a 02:30:40.660 --> 02:30:40.670 align:start position:0% there's a lot of stuff next I think a 02:30:40.670 --> 02:30:43.120 align:start position:0% there's a lot of stuff next I think a big<02:30:40.819> focus<02:30:41.000> I'll<02:30:41.329> skip<02:30:42.050> to<02:30:42.079> that<02:30:42.289> slide<02:30:42.590> it's 02:30:43.120 --> 02:30:43.130 align:start position:0% big focus I'll skip to that slide it's 02:30:43.130 --> 02:30:49.120 align:start position:0% big focus I'll skip to that slide it's effective<02:30:43.670> a<02:30:46.869> big<02:30:47.869> focus<02:30:48.170> is<02:30:48.350> testing<02:30:48.770> and<02:30:48.949> so 02:30:49.120 --> 02:30:49.130 align:start position:0% effective a big focus is testing and so 02:30:49.130 --> 02:30:51.670 align:start position:0% effective a big focus is testing and so we<02:30:49.760> should<02:30:49.939> chat<02:30:50.119> later<02:30:50.329> but<02:30:50.689> one<02:30:51.529> of<02:30:51.560> the 02:30:51.670 --> 02:30:51.680 align:start position:0% we should chat later but one of the 02:30:51.680 --> 02:30:52.689 align:start position:0% we should chat later but one of the areas<02:30:51.710> were<02:30:52.039> working<02:30:52.279> on<02:30:52.399> right<02:30:52.430> now<02:30:52.550> two 02:30:52.689 --> 02:30:52.699 align:start position:0% areas were working on right now two 02:30:52.699 --> 02:30:54.939 align:start position:0% areas were working on right now two simplest<02:30:53.239> application<02:30:53.869> it's<02:30:54.350> very<02:30:54.619> hard<02:30:54.859> to 02:30:54.939 --> 02:30:54.949 align:start position:0% simplest application it's very hard to 02:30:54.949 --> 02:30:56.500 align:start position:0% simplest application it's very hard to test<02:30:55.159> we<02:30:55.789> want<02:30:55.939> to<02:30:56.000> be<02:30:56.060> able<02:30:56.119> to<02:30:56.210> spend<02:30:56.420> up 02:30:56.500 --> 02:30:56.510 align:start position:0% test we want to be able to spend up 02:30:56.510 --> 02:30:59.830 align:start position:0% test we want to be able to spend up 10,000<02:30:57.229> nodes<02:30:57.590> in<02:30:58.069> a<02:30:58.970> network<02:30:59.029> be<02:30:59.510> able<02:30:59.689> to 02:30:59.830 --> 02:30:59.840 align:start position:0% 10,000 nodes in a network be able to 02:30:59.840 --> 02:31:01.809 align:start position:0% 10,000 nodes in a network be able to emulate<02:31:00.829> having<02:31:01.100> some<02:31:01.310> of<02:31:01.399> them<02:31:01.550> hidden 02:31:01.809 --> 02:31:01.819 align:start position:0% emulate having some of them hidden 02:31:01.819 --> 02:31:04.660 align:start position:0% emulate having some of them hidden behind<02:31:01.970> apps<02:31:02.500> run<02:31:03.500> a<02:31:03.529> series<02:31:04.010> of<02:31:04.159> test<02:31:04.460> cases 02:31:04.660 --> 02:31:04.670 align:start position:0% behind apps run a series of test cases 02:31:04.670 --> 02:31:07.330 align:start position:0% behind apps run a series of test cases back<02:31:04.970> and<02:31:05.149> forth<02:31:05.329> and<02:31:06.079> try<02:31:06.409> and<02:31:06.560> validate<02:31:06.949> that 02:31:07.330 --> 02:31:07.340 align:start position:0% back and forth and try and validate that 02:31:07.340 --> 02:31:09.279 align:start position:0% back and forth and try and validate that the<02:31:07.939> hundreds<02:31:08.329> of<02:31:08.420> thousands<02:31:08.899> of<02:31:08.960> musics 02:31:09.279 --> 02:31:09.289 align:start position:0% the hundreds of thousands of musics 02:31:09.289 --> 02:31:10.689 align:start position:0% the hundreds of thousands of musics connected<02:31:09.619> to<02:31:09.680> that<02:31:09.770> because<02:31:09.949> network<02:31:10.369> are 02:31:10.689 --> 02:31:10.699 align:start position:0% connected to that because network are 02:31:10.699 --> 02:31:12.370 align:start position:0% connected to that because network are going<02:31:10.939> to<02:31:11.000> be<02:31:11.090> very<02:31:11.329> happy<02:31:11.600> the<02:31:12.020> next<02:31:12.229> time 02:31:12.370 --> 02:31:12.380 align:start position:0% going to be very happy the next time 02:31:12.380 --> 02:31:15.309 align:start position:0% going to be very happy the next time that<02:31:12.560> we<02:31:12.649> want<02:31:13.369> to<02:31:13.699> go<02:31:13.819> ipfs<02:31:14.239> code<02:31:14.449> op<02:31:14.569> 5.0<02:31:15.050> and 02:31:15.309 --> 02:31:15.319 align:start position:0% that we want to go ipfs code op 5.0 and 02:31:15.319 --> 02:31:16.870 align:start position:0% that we want to go ipfs code op 5.0 and it<02:31:15.409> doesn't<02:31:15.649> have<02:31:15.800> any<02:31:15.949> issues<02:31:16.159> about<02:31:16.609> to<02:31:16.760> that 02:31:16.870 --> 02:31:16.880 align:start position:0% it doesn't have any issues about to that 02:31:16.880 --> 02:31:19.059 align:start position:0% it doesn't have any issues about to that especially<02:31:17.600> since<02:31:18.020> that<02:31:18.079> contains<02:31:18.590> a<02:31:18.739> number 02:31:19.059 --> 02:31:19.069 align:start position:0% especially since that contains a number 02:31:19.069 --> 02:31:20.830 align:start position:0% especially since that contains a number of<02:31:19.250> changes<02:31:19.520> to<02:31:19.819> the<02:31:19.909> DHT<02:31:20.149> to<02:31:20.390> make<02:31:20.600> it<02:31:20.720> way 02:31:20.830 --> 02:31:20.840 align:start position:0% of changes to the DHT to make it way 02:31:20.840 --> 02:31:22.840 align:start position:0% of changes to the DHT to make it way more<02:31:20.869> performant<02:31:21.470> resilient<02:31:21.920> those<02:31:22.460> are<02:31:22.609> hard 02:31:22.840 --> 02:31:22.850 align:start position:0% more performant resilient those are hard 02:31:22.850 --> 02:31:24.099 align:start position:0% more performant resilient those are hard to<02:31:22.880> test<02:31:23.119> and<02:31:23.359> we<02:31:23.420> need<02:31:23.539> to<02:31:23.630> validate<02:31:23.810> that 02:31:24.099 --> 02:31:24.109 align:start position:0% to test and we need to validate that 02:31:24.109 --> 02:31:26.349 align:start position:0% to test and we need to validate that they<02:31:24.229> rather<02:31:24.380> worker<02:31:24.739> really<02:31:25.180> thank<02:31:26.180> you<02:31:26.239> so 02:31:26.349 --> 02:31:26.359 align:start position:0% they rather worker really thank you so 02:31:26.359 --> 02:31:36.310 align:start position:0% they rather worker really thank you so much 02:31:36.310 --> 02:31:36.320 align:start position:0% 02:31:36.320 --> 02:31:44.461 align:start position:0% the<02:31:40.761> key<02:31:41.761> to<02:31:41.911> kiss<02:31:42.091> that 02:31:44.461 --> 02:31:44.471 align:start position:0% 02:31:44.471 --> 02:31:49.841 align:start position:0% so<02:31:45.671> before<02:31:46.671> I<02:31:47.501> have<02:31:48.501> a<02:31:48.530> very<02:31:48.860> short<02:31:48.950> overview 02:31:49.841 --> 02:31:49.851 align:start position:0% so before I have a very short overview 02:31:49.851 --> 02:31:53.140 align:start position:0% so before I have a very short overview ultimately<02:31:50.841> but<02:31:51.341> basically<02:31:52.341> consists<02:31:52.971> of 02:31:53.140 --> 02:31:53.150 align:start position:0% ultimately but basically consists of 02:31:53.150 --> 02:31:55.321 align:start position:0% ultimately but basically consists of these<02:31:53.661> multiple<02:31:54.110> chains<02:31:54.381> that<02:31:54.771> because 02:31:55.321 --> 02:31:55.331 align:start position:0% these multiple chains that because 02:31:55.331 --> 02:31:57.611 align:start position:0% these multiple chains that because apparently<02:31:56.331> it's<02:31:56.661> short<02:31:56.931> for<02:31:56.990> parallel 02:31:57.611 --> 02:31:57.621 align:start position:0% apparently it's short for parallel 02:31:57.621 --> 02:31:59.831 align:start position:0% apparently it's short for parallel chains<02:31:57.891> these<02:31:58.730> are<02:31:58.791> connected<02:31:59.391> together 02:31:59.831 --> 02:31:59.841 align:start position:0% chains these are connected together 02:31:59.841 --> 02:32:06.631 align:start position:0% chains these are connected together through<02:32:00.591> a<02:32:00.650> million<02:32:01.610> chain<02:32:01.911> which<02:32:02.181> basically 02:32:06.631 --> 02:32:06.641 align:start position:0% 02:32:06.641 --> 02:32:10.600 align:start position:0% these<02:32:07.641> pallets<02:32:08.331> are<02:32:08.570> connected<02:32:09.171> together<02:32:10.070> to 02:32:10.600 --> 02:32:10.610 align:start position:0% these pallets are connected together to 02:32:10.610 --> 02:32:14.890 align:start position:0% these pallets are connected together to a<02:32:10.791> relay<02:32:11.240> chain<02:32:11.541> which<02:32:12.081> is<02:32:12.261> securing<02:32:13.751> we<02:32:14.751> have 02:32:14.890 --> 02:32:14.900 align:start position:0% a relay chain which is securing we have 02:32:14.900 --> 02:32:17.230 align:start position:0% a relay chain which is securing we have a<02:32:14.931> set<02:32:15.171> of<02:32:15.291> validators<02:32:16.011> that<02:32:16.400> are<02:32:16.700> securing 02:32:17.230 --> 02:32:17.240 align:start position:0% a set of validators that are securing 02:32:17.240 --> 02:32:19.480 align:start position:0% a set of validators that are securing and<02:32:17.391> a<02:32:17.570> chain<02:32:17.900> and<02:32:18.141> we<02:32:18.650> divided<02:32:19.011> them<02:32:19.251> into 02:32:19.480 --> 02:32:19.490 align:start position:0% and a chain and we divided them into 02:32:19.490 --> 02:32:22.060 align:start position:0% and a chain and we divided them into disjoint<02:32:19.811> subsets<02:32:20.811> that<02:32:21.051> are<02:32:21.440> assigned<02:32:21.831> to 02:32:22.060 --> 02:32:22.070 align:start position:0% disjoint subsets that are assigned to 02:32:22.070 --> 02:32:25.211 align:start position:0% disjoint subsets that are assigned to each<02:32:22.431> one<02:32:22.671> of<02:32:22.700> its<02:32:23.061> energy<02:32:23.721> so<02:32:24.230> here<02:32:24.471> you<02:32:25.041> have 02:32:25.211 --> 02:32:25.221 align:start position:0% each one of its energy so here you have 02:32:25.221 --> 02:32:28.781 align:start position:0% each one of its energy so here you have the<02:32:25.400> tire<02:32:25.610> chain<02:32:25.940> e<02:32:26.211> you<02:32:27.051> have<02:32:27.351> error<02:32:27.980> tree 02:32:28.781 --> 02:32:28.791 align:start position:0% the tire chain e you have error tree 02:32:28.791 --> 02:32:32.600 align:start position:0% the tire chain e you have error tree when<02:32:29.541> there's<02:32:30.110> another<02:32:30.351> side<02:32:30.650> to<02:32:30.681> this 02:32:32.600 --> 02:32:32.610 align:start position:0% when there's another side to this 02:32:32.610 --> 02:32:35.180 align:start position:0% when there's another side to this you<02:32:32.910> have<02:32:33.210> the<02:32:33.750> small<02:32:33.900> collectors<02:32:34.710> you<02:32:35.011> that 02:32:35.180 --> 02:32:35.190 align:start position:0% you have the small collectors you that 02:32:35.190 --> 02:32:38.060 align:start position:0% you have the small collectors you that are<02:32:35.341> producing<02:32:35.851> the<02:32:35.910> parity<02:32:36.480> laws<02:32:36.780> so<02:32:37.620> how<02:32:37.891> it 02:32:38.060 --> 02:32:38.070 align:start position:0% are producing the parity laws so how it 02:32:38.070 --> 02:32:42.081 align:start position:0% are producing the parity laws so how it works<02:32:38.101> is<02:32:38.490> that<02:32:39.110> users<02:32:40.400> submit<02:32:41.400> transactions 02:32:42.081 --> 02:32:42.091 align:start position:0% works is that users submit transactions 02:32:42.091 --> 02:32:44.320 align:start position:0% works is that users submit transactions to<02:32:42.271> these<02:32:42.450> encouraging<02:32:43.080> these<02:32:43.650> collectors 02:32:44.320 --> 02:32:44.330 align:start position:0% to these encouraging these collectors 02:32:44.330 --> 02:32:47.120 align:start position:0% to these encouraging these collectors produce<02:32:45.330> the<02:32:45.721> block<02:32:45.960> here<02:32:46.380> for<02:32:46.740> the<02:32:46.830> Karachi 02:32:47.120 --> 02:32:47.130 align:start position:0% produce the block here for the Karachi 02:32:47.130 --> 02:32:51.261 align:start position:0% produce the block here for the Karachi the<02:32:48.061> meditators<02:32:48.750> here<02:32:49.641> validate<02:32:50.641> these<02:32:50.940> dogs 02:32:51.261 --> 02:32:51.271 align:start position:0% the meditators here validate these dogs 02:32:51.271 --> 02:32:53.480 align:start position:0% the meditators here validate these dogs send<02:32:51.931> them<02:32:52.051> to<02:32:52.200> the<02:32:52.320> reader<02:32:52.591> chain<02:32:52.830> and<02:32:53.311> then 02:32:53.480 --> 02:32:53.490 align:start position:0% send them to the reader chain and then 02:32:53.490 --> 02:32:56.120 align:start position:0% send them to the reader chain and then you<02:32:54.091> have<02:32:54.360> shared<02:32:54.931> security<02:32:55.261> for<02:32:55.801> all<02:32:55.980> these 02:32:56.120 --> 02:32:56.130 align:start position:0% you have shared security for all these 02:32:56.130 --> 02:33:00.711 align:start position:0% you have shared security for all these tire<02:32:56.370> chains<02:32:57.110> chains<02:32:58.551> now<02:32:59.551> the<02:33:00.120> networking 02:33:00.711 --> 02:33:00.721 align:start position:0% tire chains chains now the networking 02:33:00.721 --> 02:33:03.350 align:start position:0% tire chains chains now the networking that<02:33:00.780> we<02:33:01.021> use<02:33:01.200> here<02:33:01.440> is<02:33:01.980> the<02:33:02.880> usual<02:33:03.210> custom 02:33:03.350 --> 02:33:03.360 align:start position:0% that we use here is the usual custom 02:33:03.360 --> 02:33:05.211 align:start position:0% that we use here is the usual custom thing<02:33:03.721> that<02:33:03.900> is<02:33:04.051> used<02:33:04.290> it<02:33:04.500> was<02:33:04.650> of<02:33:04.801> the<02:33:04.891> network 02:33:05.211 --> 02:33:05.221 align:start position:0% thing that is used it was of the network 02:33:05.221 --> 02:33:09.620 align:start position:0% thing that is used it was of the network you<02:33:05.400> skip<02:33:05.700> to<02:33:05.910> to<02:33:06.511> be<02:33:07.490> here<02:33:08.490> these<02:33:09.000> collectors 02:33:09.620 --> 02:33:09.630 align:start position:0% you skip to to be here these collectors 02:33:09.630 --> 02:33:13.490 align:start position:0% you skip to to be here these collectors basically<02:33:10.351> I<02:33:10.710> wanted<02:33:11.630> this<02:33:12.630> merchant<02:33:13.290> block 02:33:13.490 --> 02:33:13.500 align:start position:0% basically I wanted this merchant block 02:33:13.500 --> 02:33:16.280 align:start position:0% basically I wanted this merchant block so<02:33:13.771> that<02:33:13.801> our<02:33:14.551> children<02:33:14.730> it<02:33:15.150> enters<02:33:15.480> and<02:33:16.051> then 02:33:16.280 --> 02:33:16.290 align:start position:0% so that our children it enters and then 02:33:16.290 --> 02:33:18.831 align:start position:0% so that our children it enters and then they<02:33:16.620> accept<02:33:17.101> the<02:33:17.250> summaries<02:33:17.700> to<02:33:17.730> them<02:33:18.091> the 02:33:18.831 --> 02:33:18.841 align:start position:0% they accept the summaries to them the 02:33:18.841 --> 02:33:20.730 align:start position:0% they accept the summaries to them the set<02:33:19.080> of<02:33:19.200> all<02:33:19.410> validators 02:33:20.730 --> 02:33:20.740 align:start position:0% set of all validators 02:33:20.740 --> 02:33:22.800 align:start position:0% set of all validators produce<02:33:21.040> the<02:33:21.340> relation<02:33:21.850> blocks<02:33:22.090> again 02:33:22.800 --> 02:33:22.810 align:start position:0% produce the relation blocks again 02:33:22.810 --> 02:33:25.020 align:start position:0% produce the relation blocks again everything<02:33:23.260> is<02:33:23.350> constant<02:33:23.800> however<02:33:24.070> there<02:33:24.880> are 02:33:25.020 --> 02:33:25.030 align:start position:0% everything is constant however there are 02:33:25.030 --> 02:33:27.570 align:start position:0% everything is constant however there are couple<02:33:25.360> of<02:33:25.390> problems<02:33:26.040> that<02:33:27.040> have<02:33:27.370> occurred 02:33:27.570 --> 02:33:27.580 align:start position:0% couple of problems that have occurred 02:33:27.580 --> 02:33:31.680 align:start position:0% couple of problems that have occurred that<02:33:28.390> we<02:33:28.540> have<02:33:28.780> noticed<02:33:29.560> with<02:33:30.479> using<02:33:31.479> just 02:33:31.680 --> 02:33:31.690 align:start position:0% that we have noticed with using just 02:33:31.690 --> 02:33:34.340 align:start position:0% that we have noticed with using just gossiping<02:33:32.290> and 02:33:34.340 --> 02:33:34.350 align:start position:0% gossiping and 02:33:34.350 --> 02:33:38.430 align:start position:0% gossiping and so<02:33:35.350> one<02:33:35.560> of<02:33:35.590> the<02:33:35.800> problems<02:33:36.190> is<02:33:36.460> that<02:33:37.440> because 02:33:38.430 --> 02:33:38.440 align:start position:0% so one of the problems is that because 02:33:38.440 --> 02:33:40.830 align:start position:0% so one of the problems is that because we<02:33:38.590> have<02:33:38.800> this<02:33:39.010> sort<02:33:39.220> of<02:33:39.400> charting<02:33:39.940> or<02:33:40.180> this 02:33:40.830 --> 02:33:40.840 align:start position:0% we have this sort of charting or this 02:33:40.840 --> 02:33:45.510 align:start position:0% we have this sort of charting or this basically<02:33:41.580> number<02:33:42.580> of<02:33:42.700> step<02:33:43.000> of<02:33:43.210> of<02:33:43.870> chains<02:33:44.520> we 02:33:45.510 --> 02:33:45.520 align:start position:0% basically number of step of of chains we 02:33:45.520 --> 02:33:48.120 align:start position:0% basically number of step of of chains we don't<02:33:45.729> have<02:33:46.000> this<02:33:46.240> pool<02:33:46.630> of<02:33:46.890> validators<02:33:47.890> that 02:33:48.120 --> 02:33:48.130 align:start position:0% don't have this pool of validators that 02:33:48.130 --> 02:33:51.150 align:start position:0% don't have this pool of validators that are<02:33:48.990> securing<02:33:49.990> the<02:33:50.080> whole<02:33:50.260> chain<02:33:50.530> but<02:33:50.740> we<02:33:50.920> have 02:33:51.150 --> 02:33:51.160 align:start position:0% are securing the whole chain but we have 02:33:51.160 --> 02:33:53.490 align:start position:0% are securing the whole chain but we have to<02:33:51.310> also<02:33:51.490> assign<02:33:51.940> them<02:33:52.240> to<02:33:52.840> pilot<02:33:53.260> chains 02:33:53.490 --> 02:33:53.500 align:start position:0% to also assign them to pilot chains 02:33:53.500 --> 02:33:57.830 align:start position:0% to also assign them to pilot chains these<02:33:53.979> are<02:33:54.220> these<02:33:55.229> substances<02:33:56.229> for<02:33:57.130> helium 02:33:57.830 --> 02:33:57.840 align:start position:0% these are these substances for helium 02:33:57.840 --> 02:34:00.810 align:start position:0% these are these substances for helium 2.0<02:33:58.840> that<02:33:59.020> would<02:33:59.170> be<02:33:59.260> the<02:33:59.380> same<02:33:59.560> case<02:33:59.800> now<02:34:00.460> here 02:34:00.810 --> 02:34:00.820 align:start position:0% 2.0 that would be the same case now here 02:34:00.820 --> 02:34:02.460 align:start position:0% 2.0 that would be the same case now here your<02:34:01.090> attack<02:34:01.510> surface<02:34:01.690> is<02:34:02.080> going<02:34:02.260> to<02:34:02.350> be 02:34:02.460 --> 02:34:02.470 align:start position:0% your attack surface is going to be 02:34:02.470 --> 02:34:05.730 align:start position:0% your attack surface is going to be wastewater<02:34:03.280> for<02:34:04.030> adversary'<02:34:04.660> that<02:34:05.350> then<02:34:05.590> you 02:34:05.730 --> 02:34:05.740 align:start position:0% wastewater for adversary' that then you 02:34:05.740 --> 02:34:08.520 align:start position:0% wastewater for adversary' that then you have<02:34:06.040> a<02:34:06.340> huge<02:34:06.790> central<02:34:07.180> validators<02:34:07.780> so<02:34:08.320> this 02:34:08.520 --> 02:34:08.530 align:start position:0% have a huge central validators so this 02:34:08.530 --> 02:34:12.750 align:start position:0% have a huge central validators so this is<02:34:08.710> assumed<02:34:09.870> attacker<02:34:10.870> wants<02:34:11.170> to<02:34:11.380> attack<02:34:11.760> make 02:34:12.750 --> 02:34:12.760 align:start position:0% is assumed attacker wants to attack make 02:34:12.760 --> 02:34:15.390 align:start position:0% is assumed attacker wants to attack make an<02:34:12.910> ellipse<02:34:13.210> attack<02:34:13.600> on<02:34:13.960> the<02:34:14.260> helium<02:34:14.530> or<02:34:14.950> argon 02:34:15.390 --> 02:34:15.400 align:start position:0% an ellipse attack on the helium or argon 02:34:15.400 --> 02:34:18.180 align:start position:0% an ellipse attack on the helium or argon polka<02:34:15.790> dot<02:34:15.970> and<02:34:16.540> we<02:34:16.750> did<02:34:16.900> if<02:34:17.650> we<02:34:17.680> didn't<02:34:18.040> have 02:34:18.180 --> 02:34:18.190 align:start position:0% polka dot and we did if we didn't have 02:34:18.190 --> 02:34:22.140 align:start position:0% polka dot and we did if we didn't have any<02:34:18.400> packages<02:34:18.910> he<02:34:19.450> would<02:34:19.600> need<02:34:19.810> to<02:34:19.840> attack<02:34:21.150> one 02:34:22.140 --> 02:34:22.150 align:start position:0% any packages he would need to attack one 02:34:22.150 --> 02:34:23.790 align:start position:0% any packages he would need to attack one of<02:34:22.180> these<02:34:22.450> alligators<02:34:23.020> but<02:34:23.320> he<02:34:23.440> would<02:34:23.590> not<02:34:23.740> be 02:34:23.790 --> 02:34:23.800 align:start position:0% of these alligators but he would not be 02:34:23.800 --> 02:34:26.100 align:start position:0% of these alligators but he would not be able<02:34:24.190> to<02:34:24.430> do<02:34:24.940> much<02:34:25.150> harm<02:34:25.360> at<02:34:25.720> the<02:34:25.810> attack 02:34:26.100 --> 02:34:26.110 align:start position:0% able to do much harm at the attack 02:34:26.110 --> 02:34:28.200 align:start position:0% able to do much harm at the attack surfaces<02:34:26.560> I<02:34:26.710> take<02:34:26.920> however<02:34:27.520> many<02:34:27.940> from 02:34:28.200 --> 02:34:28.210 align:start position:0% surfaces I take however many from 02:34:28.210 --> 02:34:31.240 align:start position:0% surfaces I take however many from sharding<02:34:28.750> awarded<02:34:29.590> the<02:34:29.830> case<02:34:30.010> of<02:34:30.160> Aden 02:34:31.240 --> 02:34:31.250 align:start position:0% sharding awarded the case of Aden 02:34:31.250 --> 02:34:33.460 align:start position:0% sharding awarded the case of Aden these<02:34:31.370> marriages<02:34:31.729> the<02:34:32.450> attack<02:34:32.779> surface<02:34:32.989> gets 02:34:33.460 --> 02:34:33.470 align:start position:0% these marriages the attack surface gets 02:34:33.470 --> 02:34:36.099 align:start position:0% these marriages the attack surface gets very<02:34:33.710> small<02:34:34.010> so<02:34:34.550> if<02:34:34.670> the<02:34:34.790> adversary's<02:34:35.120> flips 02:34:36.099 --> 02:34:36.109 align:start position:0% very small so if the adversary's flips 02:34:36.109 --> 02:34:36.940 align:start position:0% very small so if the adversary's flips in<02:34:36.260> history 02:34:36.940 --> 02:34:36.950 align:start position:0% in history 02:34:36.950 --> 02:34:38.910 align:start position:0% in history Paddy's<02:34:37.489> acres<02:34:37.850> is<02:34:38.210> going<02:34:38.540> to<02:34:38.720> basically 02:34:38.910 --> 02:34:38.920 align:start position:0% Paddy's acres is going to basically 02:34:38.920 --> 02:34:41.679 align:start position:0% Paddy's acres is going to basically compromising<02:34:39.920> the<02:34:40.460> validators<02:34:41.000> are<02:34:41.149> going<02:34:41.479> to 02:34:41.679 --> 02:34:41.689 align:start position:0% compromising the validators are going to 02:34:41.689 --> 02:34:45.550 align:start position:0% compromising the validators are going to say<02:34:42.500> we<02:34:43.370> have<02:34:43.580> a<02:34:43.609> fallback<02:34:44.029> which<02:34:44.569> are<02:34:44.840> which 02:34:45.550 --> 02:34:45.560 align:start position:0% say we have a fallback which are which 02:34:45.560 --> 02:34:47.889 align:start position:0% say we have a fallback which are which we<02:34:45.739> called<02:34:46.010> fishermen<02:34:46.550> they<02:34:47.120> should<02:34:47.359> notice 02:34:47.889 --> 02:34:47.899 align:start position:0% we called fishermen they should notice 02:34:47.899 --> 02:34:50.410 align:start position:0% we called fishermen they should notice any<02:34:48.200> wrongdoing<02:34:48.500> of<02:34:49.040> these<02:34:49.189> three<02:34:49.399> people<02:34:49.819> or 02:34:50.410 --> 02:34:50.420 align:start position:0% any wrongdoing of these three people or 02:34:50.420 --> 02:34:52.479 align:start position:0% any wrongdoing of these three people or disregarded<02:34:51.020> answers<02:34:51.350> however<02:34:52.069> it<02:34:52.279> would<02:34:52.460> be 02:34:52.479 --> 02:34:52.489 align:start position:0% disregarded answers however it would be 02:34:52.489 --> 02:34:54.210 align:start position:0% disregarded answers however it would be good<02:34:52.880> to<02:34:53.120> have<02:34:53.270> some<02:34:53.540> sort<02:34:53.779> of<02:34:53.870> network 02:34:54.210 --> 02:34:54.220 align:start position:0% good to have some sort of network 02:34:54.220 --> 02:34:57.389 align:start position:0% good to have some sort of network eclipsing<02:34:55.220> this<02:34:55.399> is<02:34:55.910> also<02:34:56.239> very<02:34:56.540> difficult 02:34:57.389 --> 02:34:57.399 align:start position:0% eclipsing this is also very difficult 02:34:57.399 --> 02:35:01.450 align:start position:0% eclipsing this is also very difficult so<02:34:58.399> basically<02:34:58.790> security<02:34:59.540> and<02:34:59.920> the<02:35:00.920> networking 02:35:01.450 --> 02:35:01.460 align:start position:0% so basically security and the networking 02:35:01.460 --> 02:35:03.160 align:start position:0% so basically security and the networking against<02:35:01.760> it<02:35:01.910> its<02:35:02.060> attack<02:35:02.390> is<02:35:02.569> one<02:35:02.750> of<02:35:02.870> the<02:35:02.989> big 02:35:03.160 --> 02:35:03.170 align:start position:0% against it its attack is one of the big 02:35:03.170 --> 02:35:05.800 align:start position:0% against it its attack is one of the big and<02:35:03.620> our<02:35:04.069> priorities<02:35:04.609> for<02:35:04.760> us<02:35:04.880> another 02:35:05.800 --> 02:35:05.810 align:start position:0% and our priorities for us another 02:35:05.810 --> 02:35:10.500 align:start position:0% and our priorities for us another problem<02:35:06.620> that<02:35:06.649> we<02:35:06.979> have<02:35:07.220> is<02:35:07.520> clear<02:35:07.970> discovery 02:35:10.500 --> 02:35:10.510 align:start position:0% 02:35:10.510 --> 02:35:13.450 align:start position:0% all<02:35:11.510> of<02:35:11.660> these<02:35:11.870> chains<02:35:12.529> are<02:35:12.800> going<02:35:13.040> to<02:35:13.160> be<02:35:13.310> in<02:35:13.399> a 02:35:13.450 --> 02:35:13.460 align:start position:0% all of these chains are going to be in a 02:35:13.460 --> 02:35:16.059 align:start position:0% all of these chains are going to be in a big<02:35:13.670> condemn<02:35:14.090> via<02:35:14.300> Network<02:35:14.779> but<02:35:15.439> the<02:35:15.620> problem 02:35:16.059 --> 02:35:16.069 align:start position:0% big condemn via Network but the problem 02:35:16.069 --> 02:35:17.979 align:start position:0% big condemn via Network but the problem that<02:35:16.279> occurs<02:35:16.970> from<02:35:17.210> us<02:35:17.390> is<02:35:17.569> that<02:35:17.750> these 02:35:17.979 --> 02:35:17.989 align:start position:0% that occurs from us is that these 02:35:17.989 --> 02:35:21.490 align:start position:0% that occurs from us is that these meditators<02:35:18.800> are<02:35:19.010> not<02:35:19.279> set<02:35:19.760> aside<02:35:20.660> to<02:35:21.140> entire 02:35:21.490 --> 02:35:21.500 align:start position:0% meditators are not set aside to entire 02:35:21.500 --> 02:35:24.480 align:start position:0% meditators are not set aside to entire chain<02:35:21.890> and<02:35:22.189> stay<02:35:22.460> right<02:35:23.270> there<02:35:23.330> forever 02:35:24.480 --> 02:35:24.490 align:start position:0% chain and stay right there forever 02:35:24.490 --> 02:35:26.100 align:start position:0% chain and stay right there forever and<02:35:24.610> will<02:35:24.791> be<02:35:24.911> connected<02:35:25.391> to<02:35:25.421> this<02:35:25.601> collectors 02:35:26.100 --> 02:35:26.110 align:start position:0% and will be connected to this collectors 02:35:26.110 --> 02:35:28.770 align:start position:0% and will be connected to this collectors but<02:35:26.650> we<02:35:26.801> got<02:35:27.011> it<02:35:27.221> and<02:35:27.761> the<02:35:27.911> reason<02:35:28.240> for<02:35:28.271> that<02:35:28.450> is 02:35:28.770 --> 02:35:28.780 align:start position:0% but we got it and the reason for that is 02:35:28.780 --> 02:35:31.560 align:start position:0% but we got it and the reason for that is that<02:35:28.811> if<02:35:29.501> a<02:35:30.131> random<02:35:30.551> assignment<02:35:31.030> at<02:35:31.360> some 02:35:31.560 --> 02:35:31.570 align:start position:0% that if a random assignment at some 02:35:31.570 --> 02:35:34.251 align:start position:0% that if a random assignment at some point<02:35:31.860> three<02:35:32.860> validators<02:35:33.490> found<02:35:33.730> malicious 02:35:34.251 --> 02:35:34.261 align:start position:0% point three validators found malicious 02:35:34.261 --> 02:35:37.261 align:start position:0% point three validators found malicious they<02:35:35.261> don't<02:35:35.530> keep<02:35:35.801> to<02:35:36.070> compromise<02:35:36.881> this 02:35:37.261 --> 02:35:37.271 align:start position:0% they don't keep to compromise this 02:35:37.271 --> 02:35:39.810 align:start position:0% they don't keep to compromise this inspire<02:35:38.021> chains<02:35:38.351> forever<02:35:38.621> but<02:35:39.431> this<02:35:39.581> patch<02:35:39.791> is 02:35:39.810 --> 02:35:39.820 align:start position:0% inspire chains forever but this patch is 02:35:39.820 --> 02:35:41.791 align:start position:0% inspire chains forever but this patch is going<02:35:40.240> to<02:35:40.331> have<02:35:40.480> some<02:35:40.690> challenge<02:35:41.141> fighter<02:35:41.530> the 02:35:41.791 --> 02:35:41.801 align:start position:0% going to have some challenge fighter the 02:35:41.801 --> 02:35:44.041 align:start position:0% going to have some challenge fighter the shuffling<02:35:42.221> of<02:35:42.400> the<02:35:42.431> panels<02:35:43.091> however<02:35:43.661> when<02:35:43.961> you 02:35:44.041 --> 02:35:44.051 align:start position:0% shuffling of the panels however when you 02:35:44.051 --> 02:35:45.841 align:start position:0% shuffling of the panels however when you change<02:35:44.381> the<02:35:44.501> agitator<02:35:44.740> for<02:35:45.280> example<02:35:45.610> if<02:35:45.730> this 02:35:45.841 --> 02:35:45.851 align:start position:0% change the agitator for example if this 02:35:45.851 --> 02:35:47.911 align:start position:0% change the agitator for example if this validators<02:35:46.450> right<02:35:46.661> now<02:35:46.871> it<02:35:47.320> decides<02:35:47.711> to 02:35:47.911 --> 02:35:47.921 align:start position:0% validators right now it decides to 02:35:47.921 --> 02:35:50.220 align:start position:0% validators right now it decides to create<02:35:48.131> a<02:35:48.641> the<02:35:49.211> later<02:35:49.421> on<02:35:49.690> is<02:35:49.811> going<02:35:50.051> to<02:35:50.141> be 02:35:50.220 --> 02:35:50.230 align:start position:0% create a the later on is going to be 02:35:50.230 --> 02:35:52.711 align:start position:0% create a the later on is going to be assigned<02:35:50.591> to<02:35:50.711> eat<02:35:50.980> the<02:35:51.161> question<02:35:51.581> is<02:35:51.700> how<02:35:52.030> this 02:35:52.711 --> 02:35:52.721 align:start position:0% assigned to eat the question is how this 02:35:52.721 --> 02:35:54.301 align:start position:0% assigned to eat the question is how this disguise<02:35:53.110> difficult<02:35:53.561> to<02:35:53.681> find<02:35:53.980> the<02:35:54.161> new 02:35:54.301 --> 02:35:54.311 align:start position:0% disguise difficult to find the new 02:35:54.311 --> 02:35:56.190 align:start position:0% disguise difficult to find the new collectors<02:35:54.851> in<02:35:55.360> the<02:35:55.511> new<02:35:55.661> pattern<02:35:56.081> the 02:35:56.190 --> 02:35:56.200 align:start position:0% collectors in the new pattern the 02:35:56.200 --> 02:35:57.591 align:start position:0% collectors in the new pattern the prepare<02:35:56.621> discovery<02:35:57.011> becomes<02:35:57.341> very 02:35:57.591 --> 02:35:57.601 align:start position:0% prepare discovery becomes very 02:35:57.601 --> 02:36:05.301 align:start position:0% prepare discovery becomes very complicated<02:35:58.601> and<02:35:58.990> we<02:35:59.591> still<02:35:59.831> are<02:36:00.011> working<02:36:00.041> on 02:36:05.301 --> 02:36:05.311 align:start position:0% 02:36:05.311 --> 02:36:09.091 align:start position:0% having<02:36:06.311> basically<02:36:06.820> this<02:36:07.631> charted<02:36:08.411> system<02:36:08.860> and 02:36:09.091 --> 02:36:09.101 align:start position:0% having basically this charted system and 02:36:09.101 --> 02:36:10.651 align:start position:0% having basically this charted system and also<02:36:09.251> having<02:36:09.730> this<02:36:09.851> rotation<02:36:10.421> of<02:36:10.541> the 02:36:10.651 --> 02:36:10.661 align:start position:0% also having this rotation of the 02:36:10.661 --> 02:36:15.421 align:start position:0% also having this rotation of the validators<02:36:13.320> the<02:36:14.320> second<02:36:14.740> problem<02:36:14.950> that<02:36:15.131> we 02:36:15.421 --> 02:36:15.431 align:start position:0% validators the second problem that we 02:36:15.431 --> 02:36:18.720 align:start position:0% validators the second problem that we have<02:36:15.671> is<02:36:15.911> that<02:36:16.331> a<02:36:17.291> lot<02:36:17.831> of<02:36:17.860> times<02:36:18.221> we<02:36:18.400> have<02:36:18.581> to 02:36:18.720 --> 02:36:18.730 align:start position:0% have is that a lot of times we have to 02:36:18.730 --> 02:36:20.791 align:start position:0% have is that a lot of times we have to communicate<02:36:18.940> things<02:36:19.541> that<02:36:19.871> don't<02:36:20.230> have<02:36:20.501> to<02:36:20.650> go 02:36:20.791 --> 02:36:20.801 align:start position:0% communicate things that don't have to go 02:36:20.801 --> 02:36:24.211 align:start position:0% communicate things that don't have to go to<02:36:20.860> everyone<02:36:21.371> so<02:36:22.030> it's<02:36:22.271> not<02:36:22.391> like<02:36:22.661> in<02:36:23.221> nearly 02:36:24.211 --> 02:36:24.221 align:start position:0% to everyone so it's not like in nearly 02:36:24.221 --> 02:36:25.591 align:start position:0% to everyone so it's not like in nearly oh<02:36:24.251> man<02:36:24.490> you<02:36:24.610> have<02:36:24.791> a<02:36:24.820> block<02:36:25.121> and<02:36:25.271> you<02:36:25.331> have<02:36:25.480> to 02:36:25.591 --> 02:36:25.601 align:start position:0% oh man you have a block and you have to 02:36:25.601 --> 02:36:27.511 align:start position:0% oh man you have a block and you have to send<02:36:25.751> it<02:36:25.900> to<02:36:26.261> all<02:36:26.440> of<02:36:26.591> the<02:36:26.711> notes<02:36:26.950> but<02:36:27.161> you<02:36:27.311> have 02:36:27.511 --> 02:36:27.521 align:start position:0% send it to all of the notes but you have 02:36:27.521 --> 02:36:30.001 align:start position:0% send it to all of the notes but you have sometimes<02:36:28.421> you<02:36:28.961> have<02:36:29.141> to<02:36:29.291> we<02:36:29.501> have<02:36:29.530> to<02:36:29.681> set 02:36:30.001 --> 02:36:30.011 align:start position:0% sometimes you have to we have to set 02:36:30.011 --> 02:36:31.831 align:start position:0% sometimes you have to we have to set things<02:36:30.280> that<02:36:30.551> are<02:36:30.700> going<02:36:30.971> to<02:36:31.150> a<02:36:31.181> specific 02:36:31.831 --> 02:36:31.841 align:start position:0% things that are going to a specific 02:36:31.841 --> 02:36:34.680 align:start position:0% things that are going to a specific validator<02:36:32.381> in<02:36:33.041> that<02:36:33.251> case<02:36:33.521> gossiping<02:36:34.150> becomes 02:36:34.680 --> 02:36:34.690 align:start position:0% validator in that case gossiping becomes 02:36:34.690 --> 02:36:37.140 align:start position:0% validator in that case gossiping becomes very<02:36:35.200> inefficient<02:36:35.921> you<02:36:36.461> don't<02:36:36.671> need<02:36:36.820> to<02:36:36.940> cause 02:36:37.140 --> 02:36:37.150 align:start position:0% very inefficient you don't need to cause 02:36:37.150 --> 02:36:38.970 align:start position:0% very inefficient you don't need to cause if<02:36:37.331> something<02:36:37.780> that<02:36:37.811> I<02:36:38.051> need<02:36:38.230> to<02:36:38.261> send<02:36:38.591> to<02:36:38.681> one 02:36:38.970 --> 02:36:38.980 align:start position:0% if something that I need to send to one 02:36:38.980 --> 02:36:41.341 align:start position:0% if something that I need to send to one specific<02:36:39.280> person<02:36:39.820> to<02:36:40.450> the<02:36:40.570> whole<02:36:40.751> network<02:36:40.931> and 02:36:41.341 --> 02:36:41.351 align:start position:0% specific person to the whole network and 02:36:41.351 --> 02:36:43.291 align:start position:0% specific person to the whole network and assuming<02:36:42.161> and 02:36:43.291 --> 02:36:43.301 align:start position:0% assuming and 02:36:43.301 --> 02:36:45.211 align:start position:0% assuming and since<02:36:43.450> we<02:36:43.601> have<02:36:43.811> a<02:36:44.021> large<02:36:44.230> amount<02:36:44.591> of<02:36:44.681> data 02:36:45.211 --> 02:36:45.221 align:start position:0% since we have a large amount of data 02:36:45.221 --> 02:36:47.461 align:start position:0% since we have a large amount of data this<02:36:45.551> becomes<02:36:45.910> inefficient<02:36:46.391> very<02:36:46.811> very<02:36:47.021> fancy 02:36:47.461 --> 02:36:47.471 align:start position:0% this becomes inefficient very very fancy 02:36:47.471 --> 02:36:50.701 align:start position:0% this becomes inefficient very very fancy so<02:36:48.070> using<02:36:49.061> Pacific<02:36:49.660> for<02:36:49.900> a<02:36:49.931> lot<02:36:50.110> of<02:36:50.261> parts<02:36:50.591> of 02:36:50.701 --> 02:36:50.711 align:start position:0% so using Pacific for a lot of parts of 02:36:50.711 --> 02:36:56.631 align:start position:0% so using Pacific for a lot of parts of the<02:36:50.801> protocol<02:36:51.251> becomes<02:36:51.671> not<02:36:52.030> very<02:36:52.601> suitable 02:36:56.631 --> 02:36:56.641 align:start position:0% 02:36:56.641 --> 02:36:59.251 align:start position:0% yet<02:36:57.641> so<02:36:57.820> what<02:36:57.940> we<02:36:58.120> are<02:36:58.240> looking<02:36:58.870> into<02:36:59.080> right 02:36:59.251 --> 02:36:59.261 align:start position:0% yet so what we are looking into right 02:36:59.261 --> 02:37:01.261 align:start position:0% yet so what we are looking into right now<02:36:59.320> is<02:36:59.471> some<02:36:59.830> sort<02:37:00.070> for<02:37:00.251> alternative<02:37:00.851> routing 02:37:01.261 --> 02:37:01.271 align:start position:0% now is some sort for alternative routing 02:37:01.271 --> 02:37:03.991 align:start position:0% now is some sort for alternative routing that<02:37:01.811> would<02:37:02.021> be<02:37:02.200> more<02:37:02.440> directed<02:37:03.160> so<02:37:03.551> basically 02:37:03.991 --> 02:37:04.001 align:start position:0% that would be more directed so basically 02:37:04.001 --> 02:37:07.280 align:start position:0% that would be more directed so basically if<02:37:04.570> you<02:37:04.631> want<02:37:04.811> to<02:37:05.141> send<02:37:05.410> to<02:37:05.591> some<02:37:06.240> validator 02:37:07.280 --> 02:37:07.290 align:start position:0% if you want to send to some validator 02:37:07.290 --> 02:37:10.610 align:start position:0% if you want to send to some validator and<02:37:08.290> energy<02:37:08.711> coded<02:37:09.131> piece<02:37:09.341> that<02:37:09.851> we<02:37:10.030> are<02:37:10.120> using 02:37:10.610 --> 02:37:10.620 align:start position:0% and energy coded piece that we are using 02:37:10.620 --> 02:37:12.930 align:start position:0% and energy coded piece that we are using you<02:37:11.620> don't<02:37:11.801> have<02:37:11.950> to<02:37:12.131> gossip<02:37:12.311> it<02:37:12.580> to<02:37:12.671> the<02:37:12.790> whole 02:37:12.930 --> 02:37:12.940 align:start position:0% you don't have to gossip it to the whole 02:37:12.940 --> 02:37:15.060 align:start position:0% you don't have to gossip it to the whole network<02:37:13.091> but<02:37:13.811> you<02:37:13.841> want<02:37:14.200> to<02:37:14.320> find<02:37:14.620> that<02:37:14.801> very 02:37:15.060 --> 02:37:15.070 align:start position:0% network but you want to find that very 02:37:15.070 --> 02:37:16.951 align:start position:0% network but you want to find that very different<02:37:15.280> address<02:37:15.820> and<02:37:16.030> you<02:37:16.330> don't<02:37:16.540> directly 02:37:16.951 --> 02:37:16.961 align:start position:0% different address and you don't directly 02:37:16.961 --> 02:37:17.671 align:start position:0% different address and you don't directly send<02:37:17.230> it<02:37:17.320> there 02:37:17.671 --> 02:37:17.681 align:start position:0% send it there 02:37:17.681 --> 02:37:20.310 align:start position:0% send it there however<02:37:18.190> there<02:37:18.370> are<02:37:18.780> problems<02:37:19.780> there<02:37:19.870> too<02:37:20.021> we 02:37:20.310 --> 02:37:20.320 align:start position:0% however there are problems there too we 02:37:20.320 --> 02:37:24.001 align:start position:0% however there are problems there too we wanted<02:37:20.681> to<02:37:20.771> be<02:37:20.891> reliable<02:37:21.461> because<02:37:22.181> a<02:37:22.980> lot<02:37:23.980> of 02:37:24.001 --> 02:37:24.011 align:start position:0% wanted to be reliable because a lot of 02:37:24.011 --> 02:37:26.581 align:start position:0% wanted to be reliable because a lot of the<02:37:24.370> security<02:37:24.971> of<02:37:25.001> the<02:37:25.091> system<02:37:25.360> relies<02:37:25.990> on<02:37:26.021> T's 02:37:26.581 --> 02:37:26.591 align:start position:0% the security of the system relies on T's 02:37:26.591 --> 02:37:32.220 align:start position:0% the security of the system relies on T's and<02:37:27.370> data<02:37:27.610> to<02:37:27.940> be<02:37:28.620> successfully<02:37:29.620> received<02:37:31.230> so 02:37:32.220 --> 02:37:32.230 align:start position:0% and data to be successfully received so 02:37:32.230 --> 02:37:36.240 align:start position:0% and data to be successfully received so these<02:37:32.381> are<02:37:32.561> the<02:37:32.801> main<02:37:33.641> networking<02:37:34.271> challenges 02:37:36.240 --> 02:37:36.250 align:start position:0% these are the main networking challenges 02:37:36.250 --> 02:37:39.469 align:start position:0% these are the main networking challenges the<02:37:36.490> short 02:37:39.469 --> 02:37:39.479 align:start position:0% 02:37:39.479 --> 02:37:44.000 align:start position:0% you<02:37:39.720> if<02:37:40.710> you<02:37:40.800> have<02:37:40.979> any<02:37:41.159> questions<02:37:41.869> -<02:37:43.010> what's 02:37:44.000 --> 02:37:44.010 align:start position:0% you if you have any questions - what's 02:37:44.010 --> 02:37:45.649 align:start position:0% you if you have any questions - what's your<02:37:44.159> current<02:37:44.399> thinking<02:37:44.729> around<02:37:45.359> how<02:37:45.600> to 02:37:45.649 --> 02:37:45.659 align:start position:0% your current thinking around how to 02:37:45.659 --> 02:37:50.290 align:start position:0% your current thinking around how to solve<02:37:45.960> these<02:37:46.590> are<02:37:46.800> how<02:37:46.920> to<02:37:46.979> do<02:37:47.279> propulsive 02:37:50.290 --> 02:37:50.300 align:start position:0% 02:37:50.300 --> 02:37:52.410 align:start position:0% mortgage<02:37:51.300> one<02:37:51.510> piece 02:37:52.410 --> 02:37:52.420 align:start position:0% mortgage one piece 02:37:52.420 --> 02:37:55.750 align:start position:0% mortgage one piece I<02:37:52.530> guess<02:37:53.530> number<02:37:53.740> two 02:37:55.750 --> 02:37:55.760 align:start position:0% I guess number two 02:37:55.760 --> 02:37:58.550 align:start position:0% I guess number two but<02:37:56.760> we<02:37:56.880> are<02:37:57.000> trying<02:37:57.360> to<02:37:57.450> do<02:37:57.660> right<02:37:57.810> now<02:37:57.840> sorted 02:37:58.550 --> 02:37:58.560 align:start position:0% but we are trying to do right now sorted 02:37:58.560 --> 02:38:00.380 align:start position:0% but we are trying to do right now sorted by<02:37:58.979> vector<02:37:59.340> routing<02:37:59.430> so<02:37:59.940> they<02:38:00.060> are<02:38:00.120> looking 02:38:00.380 --> 02:38:00.390 align:start position:0% by vector routing so they are looking 02:38:00.390 --> 02:38:02.960 align:start position:0% by vector routing so they are looking into<02:38:00.540> policies<02:38:01.290> that<02:38:01.530> this<02:38:02.100> is<02:38:02.400> this<02:38:02.700> nose 02:38:02.960 --> 02:38:02.970 align:start position:0% into policies that this is this nose 02:38:02.970 --> 02:38:05.540 align:start position:0% into policies that this is this nose could<02:38:03.270> have<02:38:03.510> together<02:38:03.720> and<02:38:04.560> look<02:38:04.740> into<02:38:04.979> a<02:38:05.160> car 02:38:05.540 --> 02:38:05.550 align:start position:0% could have together and look into a car 02:38:05.550 --> 02:38:07.040 align:start position:0% could have together and look into a car type<02:38:05.760> of<02:38:05.940> gravity<02:38:06.300> strategies<02:38:06.780> which<02:38:07.020> will 02:38:07.040 --> 02:38:07.050 align:start position:0% type of gravity strategies which will 02:38:07.050 --> 02:38:09.200 align:start position:0% type of gravity strategies which will apply<02:38:07.410> to<02:38:07.560> these<02:38:07.830> operations<02:38:08.160> we<02:38:08.970> are<02:38:09.060> not 02:38:09.200 --> 02:38:09.210 align:start position:0% apply to these operations we are not 02:38:09.210 --> 02:38:12.800 align:start position:0% apply to these operations we are not going<02:38:09.420> to<02:38:09.979> be<02:38:10.979> reduced<02:38:11.370> in<02:38:11.490> therefore<02:38:12.030> part<02:38:12.630> of 02:38:12.800 --> 02:38:12.810 align:start position:0% going to be reduced in therefore part of 02:38:12.810 --> 02:38:14.719 align:start position:0% going to be reduced in therefore part of the<02:38:12.960> protocol<02:38:13.380> but<02:38:13.920> for<02:38:14.100> the<02:38:14.190> part<02:38:14.430> that<02:38:14.490> we 02:38:14.719 --> 02:38:14.729 align:start position:0% the protocol but for the part that we 02:38:14.729 --> 02:38:16.880 align:start position:0% the protocol but for the part that we are<02:38:14.760> not<02:38:14.940> going<02:38:15.210> to<02:38:15.300> send<02:38:15.660> a<02:38:16.020> specific<02:38:16.590> ADA<02:38:16.740> to 02:38:16.880 --> 02:38:16.890 align:start position:0% are not going to send a specific ADA to 02:38:16.890 --> 02:38:18.830 align:start position:0% are not going to send a specific ADA to everyone<02:38:17.430> but<02:38:17.670> to<02:38:17.729> specific<02:38:18.360> validators 02:38:18.830 --> 02:38:18.840 align:start position:0% everyone but to specific validators 02:38:18.840 --> 02:38:21.800 align:start position:0% everyone but to specific validators therefore<02:38:19.229> to<02:38:19.350> do<02:38:19.500> something<02:38:20.660> there<02:38:21.660> are<02:38:21.720> a 02:38:21.800 --> 02:38:21.810 align:start position:0% therefore to do something there are a 02:38:21.810 --> 02:38:25.250 align:start position:0% therefore to do something there are a couple<02:38:21.930> of<02:38:22.460> topologies<02:38:23.460> I<02:38:23.900> mean<02:38:24.900> the<02:38:24.990> easiest 02:38:25.250 --> 02:38:25.260 align:start position:0% couple of topologies I mean the easiest 02:38:25.260 --> 02:38:26.780 align:start position:0% couple of topologies I mean the easiest would<02:38:25.470> be<02:38:25.560> just<02:38:25.800> products<02:38:26.160> to<02:38:26.250> everyone<02:38:26.640> - 02:38:26.780 --> 02:38:26.790 align:start position:0% would be just products to everyone - 02:38:26.790 --> 02:38:28.880 align:start position:0% would be just products to everyone - however<02:38:26.970> if<02:38:27.240> you<02:38:27.330> have<02:38:27.479> a<02:38:27.510> larger<02:38:27.930> center 02:38:28.880 --> 02:38:28.890 align:start position:0% however if you have a larger center 02:38:28.890 --> 02:38:31.219 align:start position:0% however if you have a larger center console<02:38:29.390> they<02:38:30.390> all<02:38:30.540> have<02:38:30.660> two<02:38:30.810> polishes<02:38:31.200> that 02:38:31.219 --> 02:38:31.229 align:start position:0% console they all have two polishes that 02:38:31.229 --> 02:38:37.660 align:start position:0% console they all have two polishes that are<02:38:31.350> a<02:38:31.560> bit<02:38:31.770> more 02:38:37.660 --> 02:38:37.670 align:start position:0% 02:38:37.670 --> 02:38:44.840 align:start position:0% [Music] 02:38:44.840 --> 02:38:44.850 align:start position:0% [Music] 02:38:44.850 --> 02:38:50.120 align:start position:0% [Music] in<02:38:45.850> fact<02:38:46.060> or<02:38:46.750> theoretical<02:38:48.120> discovery 02:38:50.120 --> 02:38:50.130 align:start position:0% in fact or theoretical discovery 02:38:50.130 --> 02:38:53.269 align:start position:0% in fact or theoretical discovery discovery<02:38:51.130> defy<02:38:51.760> that<02:38:51.970> you<02:38:52.090> can<02:38:52.390> look<02:38:52.569> at<02:38:52.720> it 02:38:53.269 --> 02:38:53.279 align:start position:0% discovery defy that you can look at it 02:38:53.279 --> 02:38:57.750 align:start position:0% discovery defy that you can look at it oh<02:38:55.140> do<02:38:56.140> I<02:38:56.199> need<02:38:56.229> to<02:38:56.500> define<02:38:56.770> them<02:38:57.040> I<02:38:57.340> don't<02:38:57.640> know 02:38:57.750 --> 02:38:57.760 align:start position:0% oh do I need to define them I don't know 02:38:57.760 --> 02:38:58.889 align:start position:0% oh do I need to define them I don't know okay 02:38:58.889 --> 02:38:58.899 align:start position:0% okay 02:38:58.899 --> 02:39:00.900 align:start position:0% okay whatever<02:38:59.229> look<02:38:59.410> into<02:38:59.710> it<02:38:59.859> and<02:39:00.250> I'll<02:39:00.580> ask<02:39:00.760> you 02:39:00.900 --> 02:39:00.910 align:start position:0% whatever look into it and I'll ask you 02:39:00.910 --> 02:39:04.410 align:start position:0% whatever look into it and I'll ask you later<02:39:01.300> oh<02:39:01.949> thanks<02:39:02.949> money<02:39:03.819> getting<02:39:04.029> calls<02:39:04.270> for 02:39:04.410 --> 02:39:04.420 align:start position:0% later oh thanks money getting calls for 02:39:04.420 --> 02:39:06.269 align:start position:0% later oh thanks money getting calls for this<02:39:04.540> mission<02:39:04.750> your<02:39:05.470> twice<02:39:05.500> enough<02:39:05.979> to<02:39:06.100> get 02:39:06.269 --> 02:39:06.279 align:start position:0% this mission your twice enough to get 02:39:06.279 --> 02:39:14.519 align:start position:0% this mission your twice enough to get any<02:39:06.699> attention<02:39:06.850> that's<02:39:07.540> the<02:39:07.779> person<02:39:13.529> simply 02:39:14.519 --> 02:39:14.529 align:start position:0% any attention that's the person simply 02:39:14.529 --> 02:39:16.559 align:start position:0% any attention that's the person simply psychometric<02:39:15.460> foundation<02:39:15.939> before<02:39:16.060> to<02:39:16.390> learn 02:39:16.559 --> 02:39:16.569 align:start position:0% psychometric foundation before to learn 02:39:16.569 --> 02:39:17.300 align:start position:0% psychometric foundation before to learn whisper 02:39:17.300 --> 02:39:17.310 align:start position:0% whisper 02:39:17.310 --> 02:39:19.910 align:start position:0% whisper [Music] 02:39:19.910 --> 02:39:19.920 align:start position:0% [Music] 02:39:19.920 --> 02:39:22.820 align:start position:0% [Music] I<02:39:20.540> think<02:39:21.540> it's<02:39:21.659> like<02:39:21.810> a<02:39:21.989> year<02:39:22.229> ago<02:39:22.290> it<02:39:22.649> was 02:39:22.820 --> 02:39:22.830 align:start position:0% I think it's like a year ago it was 02:39:22.830 --> 02:39:25.519 align:start position:0% I think it's like a year ago it was announced<02:39:23.069> in<02:39:23.310> detail<02:39:23.880> and<02:39:24.390> so<02:39:24.689> we<02:39:25.260> have<02:39:25.500> a 02:39:25.519 --> 02:39:25.529 align:start position:0% announced in detail and so we have a 02:39:25.529 --> 02:39:28.309 align:start position:0% announced in detail and so we have a project<02:39:25.830> that<02:39:26.460> we<02:39:27.210> are<02:39:27.330> working<02:39:27.479> on<02:39:27.899> that<02:39:28.050> is 02:39:28.309 --> 02:39:28.319 align:start position:0% project that we are working on that is 02:39:28.319 --> 02:39:32.559 align:start position:0% project that we are working on that is implemented<02:39:29.330> is<02:39:30.330> privacy-preserving 02:39:32.559 --> 02:39:32.569 align:start position:0% implemented is privacy-preserving 02:39:32.569 --> 02:39:34.470 align:start position:0% implemented is privacy-preserving messaging 02:39:34.470 --> 02:39:34.480 align:start position:0% messaging 02:39:34.480 --> 02:39:36.810 align:start position:0% messaging and<02:39:34.570> they<02:39:35.050> are<02:39:35.110> looking<02:39:35.440> to<02:39:35.650> respond<02:39:36.370> to<02:39:36.550> it<02:39:36.670> as 02:39:36.810 --> 02:39:36.820 align:start position:0% and they are looking to respond to it as 02:39:36.820 --> 02:39:39.739 align:start position:0% and they are looking to respond to it as a<02:39:36.851> collaboration<02:39:37.360> with<02:39:37.601> staples<02:39:38.110> and 02:39:39.739 --> 02:39:39.749 align:start position:0% a collaboration with staples and 02:39:39.749 --> 02:39:43.609 align:start position:0% a collaboration with staples and but<02:39:40.649> that's<02:39:40.829> in<02:39:41.189> Paris<02:39:41.609> that<02:39:42.140> okay<02:39:43.140> okay<02:39:43.319> yes 02:39:43.609 --> 02:39:43.619 align:start position:0% but that's in Paris that okay okay yes 02:39:43.619 --> 02:39:52.200 align:start position:0% but that's in Paris that okay okay yes that<02:39:44.430> was<02:39:45.060> bad 02:39:52.200 --> 02:39:52.210 align:start position:0% 02:39:52.210 --> 02:39:56.769 align:start position:0% okay 02:39:56.769 --> 02:39:56.779 align:start position:0% 02:39:56.779 --> 02:40:06.309 align:start position:0% thank<02:39:57.350> you<02:39:57.560> Thank<02:39:57.979> You<02:40:04.060> radical<02:40:05.060> of<02:40:05.299> a<02:40:06.020> network 02:40:06.309 --> 02:40:06.319 align:start position:0% thank you Thank You radical of a network 02:40:06.319 --> 02:40:09.159 align:start position:0% thank you Thank You radical of a network for<02:40:06.529> code<02:40:06.680> collaboration<02:40:07.810> we've<02:40:08.810> launched 02:40:09.159 --> 02:40:09.169 align:start position:0% for code collaboration we've launched 02:40:09.169 --> 02:40:11.380 align:start position:0% for code collaboration we've launched radical<02:40:09.499> last<02:40:09.680> year<02:40:09.859> it's<02:40:10.100> built<02:40:10.339> as<02:40:10.729> a<02:40:10.760> Pico 02:40:11.380 --> 02:40:11.390 align:start position:0% radical last year it's built as a Pico 02:40:11.390 --> 02:40:13.590 align:start position:0% radical last year it's built as a Pico collaboration<02:40:11.899> staff<02:40:12.199> that's<02:40:12.529> built<02:40:12.739> on<02:40:12.859> ipfs 02:40:13.590 --> 02:40:13.600 align:start position:0% collaboration staff that's built on ipfs 02:40:13.600 --> 02:40:16.059 align:start position:0% collaboration staff that's built on ipfs and<02:40:14.600> we<02:40:15.049> started<02:40:15.289> the<02:40:15.409> project<02:40:15.560> with<02:40:15.799> at<02:40:15.949> least 02:40:16.059 --> 02:40:16.069 align:start position:0% and we started the project with at least 02:40:16.069 --> 02:40:19.029 align:start position:0% and we started the project with at least that<02:40:16.310> code<02:40:16.489> collaboration<02:40:17.209> and<02:40:18.039> centralized 02:40:19.029 --> 02:40:19.039 align:start position:0% that code collaboration and centralized 02:40:19.039 --> 02:40:22.000 align:start position:0% that code collaboration and centralized to<02:40:19.249> one<02:40:19.459> platform<02:40:19.699> is<02:40:20.119> to<02:40:20.449> go<02:40:21.409> collaborations 02:40:22.000 --> 02:40:22.010 align:start position:0% to one platform is to go collaborations 02:40:22.010 --> 02:40:23.739 align:start position:0% to one platform is to go collaborations to<02:40:22.189> critical<02:40:22.609> to<02:40:22.760> be<02:40:22.850> centralized<02:40:23.270> to<02:40:23.600> one 02:40:23.739 --> 02:40:23.749 align:start position:0% to critical to be centralized to one 02:40:23.749 --> 02:40:26.199 align:start position:0% to critical to be centralized to one platform<02:40:23.989> that<02:40:24.709> is<02:40:25.100> expressed<02:40:25.549> in<02:40:25.760> this<02:40:25.939> tweet 02:40:26.199 --> 02:40:26.209 align:start position:0% platform that is expressed in this tweet 02:40:26.209 --> 02:40:28.319 align:start position:0% platform that is expressed in this tweet that<02:40:26.419> I<02:40:26.930> included<02:40:27.289> in<02:40:27.439> my<02:40:27.470> presentation 02:40:28.319 --> 02:40:28.329 align:start position:0% that I included in my presentation 02:40:28.329 --> 02:40:30.880 align:start position:0% that I included in my presentation specifically<02:40:29.329> having<02:40:30.079> all<02:40:30.319> free<02:40:30.560> and<02:40:30.680> open 02:40:30.880 --> 02:40:30.890 align:start position:0% specifically having all free and open 02:40:30.890 --> 02:40:32.260 align:start position:0% specifically having all free and open source<02:40:31.010> software<02:40:31.100> which<02:40:31.609> is<02:40:31.729> like<02:40:31.850> critical 02:40:32.260 --> 02:40:32.270 align:start position:0% source software which is like critical 02:40:32.270 --> 02:40:33.880 align:start position:0% source software which is like critical to<02:40:32.510> all<02:40:32.749> of<02:40:32.899> the<02:40:33.079> functioning<02:40:33.499> technical 02:40:33.880 --> 02:40:33.890 align:start position:0% to all of the functioning technical 02:40:33.890 --> 02:40:37.420 align:start position:0% to all of the functioning technical infrastructure<02:40:34.329> in<02:40:35.329> globally<02:40:36.229> right<02:40:36.470> now<02:40:36.649> so 02:40:37.420 --> 02:40:37.430 align:start position:0% infrastructure in globally right now so 02:40:37.430 --> 02:40:39.429 align:start position:0% infrastructure in globally right now so we<02:40:37.909> were<02:40:37.999> inspired<02:40:38.119> by<02:40:38.439> existing 02:40:39.429 --> 02:40:39.439 align:start position:0% we were inspired by existing 02:40:39.439 --> 02:40:41.079 align:start position:0% we were inspired by existing decentralized<02:40:40.069> protocols<02:40:40.430> networks<02:40:40.789> like<02:40:41.029> I 02:40:41.079 --> 02:40:41.089 align:start position:0% decentralized protocols networks like I 02:40:41.089 --> 02:40:44.380 align:start position:0% decentralized protocols networks like I speak<02:40:41.539> that<02:40:41.989> everybody<02:40:42.529> who's<02:40:42.709> here<02:40:43.390> speaking 02:40:44.380 --> 02:40:44.390 align:start position:0% speak that everybody who's here speaking 02:40:44.390 --> 02:40:46.179 align:start position:0% speak that everybody who's here speaking today<02:40:44.629> and<02:40:44.869> we<02:40:45.169> try<02:40:45.379> to<02:40:45.439> learn<02:40:45.709> from<02:40:45.770> other 02:40:46.179 --> 02:40:46.189 align:start position:0% today and we try to learn from other 02:40:46.189 --> 02:40:49.329 align:start position:0% today and we try to learn from other previous<02:40:46.640> attempts<02:40:47.060> like<02:40:47.499> in<02:40:48.499> SSP<02:40:48.979> and<02:40:49.159> get 02:40:49.329 --> 02:40:49.339 align:start position:0% previous attempts like in SSP and get 02:40:49.339 --> 02:40:51.309 align:start position:0% previous attempts like in SSP and get torrent<02:40:49.789> so<02:40:50.390> the<02:40:50.510> current<02:40:50.659> state<02:40:50.869> of<02:40:50.930> radical 02:40:51.309 --> 02:40:51.319 align:start position:0% torrent so the current state of radical 02:40:51.319 --> 02:40:53.590 align:start position:0% torrent so the current state of radical is<02:40:51.560> basically<02:40:52.159> a<02:40:52.249> secure<02:40:52.669> and<02:40:52.789> offline<02:40:53.180> first 02:40:53.590 --> 02:40:53.600 align:start position:0% is basically a secure and offline first 02:40:53.600 --> 02:40:56.469 align:start position:0% is basically a secure and offline first in<02:40:54.260> terminal<02:40:54.739> native<02:40:55.209> alternative<02:40:56.209> to 02:40:56.469 --> 02:40:56.479 align:start position:0% in terminal native alternative to 02:40:56.479 --> 02:40:57.729 align:start position:0% in terminal native alternative to centralize<02:40:56.869> the<02:40:56.989> code<02:40:57.140> of<02:40:57.260> collaboration 02:40:57.729 --> 02:40:57.739 align:start position:0% centralize the code of collaboration 02:40:57.739 --> 02:40:59.679 align:start position:0% centralize the code of collaboration it's<02:40:58.220> super<02:40:58.640> cool<02:40:58.819> it<02:40:59.060> increased<02:40:59.479> with 02:40:59.679 --> 02:40:59.689 align:start position:0% it's super cool it increased with 02:40:59.689 --> 02:41:01.689 align:start position:0% it's super cool it increased with distributed<02:41:00.260> version<02:41:00.709> control<02:41:00.919> systems<02:41:01.609> like 02:41:01.689 --> 02:41:01.699 align:start position:0% distributed version control systems like 02:41:01.699 --> 02:41:04.710 align:start position:0% distributed version control systems like get<02:41:01.999> includes<02:41:02.839> a<02:41:02.899> high<02:41:03.049> level<02:41:03.260> language<02:41:03.829> for 02:41:04.710 --> 02:41:04.720 align:start position:0% get includes a high level language for 02:41:04.720 --> 02:41:07.719 align:start position:0% get includes a high level language for reprogram<02:41:05.720> level<02:41:06.079> of<02:41:06.169> semantics<02:41:06.799> you'd<02:41:07.579> be 02:41:07.719 --> 02:41:07.729 align:start position:0% reprogram level of semantics you'd be 02:41:07.729 --> 02:41:09.159 align:start position:0% reprogram level of semantics you'd be network<02:41:08.029> for<02:41:08.239> sharing<02:41:08.270> application<02:41:08.959> states 02:41:09.159 --> 02:41:09.169 align:start position:0% network for sharing application states 02:41:09.169 --> 02:41:11.139 align:start position:0% network for sharing application states to<02:41:09.319> this<02:41:09.470> super-awesome<02:41:10.039> replicated<02:41:10.939> state 02:41:11.139 --> 02:41:11.149 align:start position:0% to this super-awesome replicated state 02:41:11.149 --> 02:41:13.630 align:start position:0% to this super-awesome replicated state machine<02:41:11.449> language<02:41:11.979> inflexible<02:41:12.979> c'mon<02:41:13.310> who's 02:41:13.630 --> 02:41:13.640 align:start position:0% machine language inflexible c'mon who's 02:41:13.640 --> 02:41:15.130 align:start position:0% machine language inflexible c'mon who's command-line<02:41:14.089> tools<02:41:14.419> so<02:41:14.539> basically<02:41:14.899> makes 02:41:15.130 --> 02:41:15.140 align:start position:0% command-line tools so basically makes 02:41:15.140 --> 02:41:18.010 align:start position:0% command-line tools so basically makes code<02:41:15.409> collaboration<02:41:16.039> of<02:41:16.129> primitive<02:41:16.459> and<02:41:17.359> is 02:41:18.010 --> 02:41:18.020 align:start position:0% code collaboration of primitive and is 02:41:18.020 --> 02:41:19.149 align:start position:0% code collaboration of primitive and is building<02:41:18.379> an<02:41:18.470> entirely<02:41:18.739> peer-to-peer 02:41:19.149 --> 02:41:19.159 align:start position:0% building an entirely peer-to-peer 02:41:19.159 --> 02:41:21.699 align:start position:0% building an entirely peer-to-peer developer<02:41:20.289> experience<02:41:21.289> that<02:41:21.409> a<02:41:21.439> Kurtz 02:41:21.699 --> 02:41:21.709 align:start position:0% developer experience that a Kurtz 02:41:21.709 --> 02:41:24.250 align:start position:0% developer experience that a Kurtz experimented<02:41:22.600> experimentation<02:41:23.600> about<02:41:24.109> how 02:41:24.250 --> 02:41:24.260 align:start position:0% experimented experimentation about how 02:41:24.260 --> 02:41:27.250 align:start position:0% experimented experimentation about how we<02:41:24.919> work<02:41:25.159> and<02:41:25.699> develop<02:41:25.999> together<02:41:26.299> but<02:41:27.140> what 02:41:27.250 --> 02:41:27.260 align:start position:0% we work and develop together but what 02:41:27.260 --> 02:41:29.079 align:start position:0% we work and develop together but what I'm<02:41:27.350> here<02:41:27.529> to<02:41:27.619> talk<02:41:27.739> about<02:41:27.799> in<02:41:28.189> the<02:41:28.549> last<02:41:28.819> three 02:41:29.079 --> 02:41:29.089 align:start position:0% I'm here to talk about in the last three 02:41:29.089 --> 02:41:30.849 align:start position:0% I'm here to talk about in the last three minutes<02:41:29.209> of<02:41:29.479> my<02:41:29.659> talk<02:41:29.839> is<02:41:30.319> how<02:41:30.589> the<02:41:30.649> code 02:41:30.849 --> 02:41:30.859 align:start position:0% minutes of my talk is how the code 02:41:30.859 --> 02:41:32.071 align:start position:0% minutes of my talk is how the code collaboration<02:41:31.430> is<02:41:31.520> more<02:41:31.699> than<02:41:31.789> just 02:41:32.071 --> 02:41:32.081 align:start position:0% collaboration is more than just 02:41:32.081 --> 02:41:34.951 align:start position:0% collaboration is more than just and<02:41:32.471> what<02:41:32.681> works<02:41:33.001> exploring<02:41:34.001> beyond 02:41:34.951 --> 02:41:34.961 align:start position:0% and what works exploring beyond 02:41:34.961 --> 02:41:36.421 align:start position:0% and what works exploring beyond peer-to-peer<02:41:35.320> post<02:41:35.711> collaboration<02:41:36.221> at 02:41:36.421 --> 02:41:36.431 align:start position:0% peer-to-peer post collaboration at 02:41:36.431 --> 02:41:40.111 align:start position:0% peer-to-peer post collaboration at radical<02:41:36.911> so<02:41:37.871> I<02:41:38.341> think<02:41:39.341> it<02:41:39.671> kind<02:41:39.820> of<02:41:39.940> is 02:41:40.111 --> 02:41:40.121 align:start position:0% radical so I think it kind of is 02:41:40.121 --> 02:41:43.021 align:start position:0% radical so I think it kind of is embodied<02:41:40.631> in<02:41:40.721> this<02:41:40.841> tweet<02:41:41.141> like<02:41:42.101> you<02:41:42.940> know 02:41:43.021 --> 02:41:43.031 align:start position:0% embodied in this tweet like you know 02:41:43.031 --> 02:41:44.371 align:start position:0% embodied in this tweet like you know code<02:41:43.301> collaboration<02:41:43.811> is<02:41:43.900> more<02:41:44.081> than<02:41:44.201> code 02:41:44.371 --> 02:41:44.381 align:start position:0% code collaboration is more than code 02:41:44.381 --> 02:41:46.111 align:start position:0% code collaboration is more than code network<02:41:44.741> effects<02:41:45.161> are<02:41:45.400> a<02:41:45.431> thing<02:41:45.791> there's<02:41:46.061> a 02:41:46.111 --> 02:41:46.121 align:start position:0% network effects are a thing there's a 02:41:46.121 --> 02:41:48.271 align:start position:0% network effects are a thing there's a reason<02:41:46.421> why<02:41:46.511> most<02:41:46.751> code<02:41:47.021> collab<02:41:47.650> is<02:41:47.681> done<02:41:48.011> on 02:41:48.271 --> 02:41:48.281 align:start position:0% reason why most code collab is done on 02:41:48.281 --> 02:41:51.211 align:start position:0% reason why most code collab is done on github<02:41:48.701> right<02:41:49.091> now<02:41:49.711> and<02:41:50.711> I<02:41:50.771> had<02:41:50.921> a<02:41:50.951> really 02:41:51.211 --> 02:41:51.221 align:start position:0% github right now and I had a really 02:41:51.221 --> 02:41:54.661 align:start position:0% github right now and I had a really funny<02:41:51.521> slide<02:41:51.820> here<02:41:52.091> that<02:41:52.471> says<02:41:53.471> this<02:41:53.741> peer 02:41:54.661 --> 02:41:54.671 align:start position:0% funny slide here that says this peer 02:41:54.671 --> 02:41:56.071 align:start position:0% funny slide here that says this peer here<02:41:54.881> and<02:41:55.001> watching<02:41:55.331> kind<02:41:55.601> of<02:41:55.661> had<02:41:55.781> this<02:41:55.931> like 02:41:56.071 --> 02:41:56.081 align:start position:0% here and watching kind of had this like 02:41:56.081 --> 02:41:59.970 align:start position:0% here and watching kind of had this like awkward<02:41:56.320> relationship<02:41:57.301> but<02:41:58.301> we<02:41:59.051> think<02:41:59.440> and<02:41:59.801> at 02:41:59.970 --> 02:41:59.980 align:start position:0% awkward relationship but we think and at 02:41:59.980 --> 02:42:01.711 align:start position:0% awkward relationship but we think and at radical<02:42:00.371> we<02:42:00.491> are<02:42:00.581> exploring<02:42:00.971> how<02:42:01.121> blockchain 02:42:01.711 --> 02:42:01.721 align:start position:0% radical we are exploring how blockchain 02:42:01.721 --> 02:42:04.560 align:start position:0% radical we are exploring how blockchain can<02:42:01.751> be<02:42:02.081> code<02:42:02.471> collaboration<02:42:03.311> trans<02:42:04.121> dental 02:42:04.560 --> 02:42:04.570 align:start position:0% can be code collaboration trans dental 02:42:04.570 --> 02:42:07.621 align:start position:0% can be code collaboration trans dental experience<02:42:05.400> because<02:42:06.400> we<02:42:06.551> think<02:42:06.761> that<02:42:06.881> Foss<02:42:07.271> is 02:42:07.621 --> 02:42:07.631 align:start position:0% experience because we think that Foss is 02:42:07.631 --> 02:42:10.411 align:start position:0% experience because we think that Foss is a<02:42:07.900> really<02:42:08.291> great<02:42:08.381> design<02:42:08.771> space<02:42:09.041> for<02:42:09.911> adapted 02:42:10.411 --> 02:42:10.421 align:start position:0% a really great design space for adapted 02:42:10.421 --> 02:42:12.481 align:start position:0% a really great design space for adapted formation<02:42:10.931> I<02:42:11.141> mean<02:42:11.891> it's<02:42:12.011> really<02:42:12.190> common 02:42:12.481 --> 02:42:12.491 align:start position:0% formation I mean it's really common 02:42:12.491 --> 02:42:15.151 align:start position:0% formation I mean it's really common based<02:42:12.730> peer<02:42:12.971> production<02:42:13.181> at<02:42:13.661> its<02:42:13.690> core<02:42:14.110> and<02:42:14.980> so 02:42:15.151 --> 02:42:15.161 align:start position:0% based peer production at its core and so 02:42:15.161 --> 02:42:16.531 align:start position:0% based peer production at its core and so we<02:42:15.281> want<02:42:15.491> to<02:42:15.521> experiment<02:42:15.791> with<02:42:16.001> distributing 02:42:16.531 --> 02:42:16.541 align:start position:0% we want to experiment with distributing 02:42:16.541 --> 02:42:17.850 align:start position:0% we want to experiment with distributing rotation<02:42:16.931> collective<02:42:17.261> ownership<02:42:17.381> and 02:42:17.850 --> 02:42:17.860 align:start position:0% rotation collective ownership and 02:42:17.860 --> 02:42:20.551 align:start position:0% rotation collective ownership and community<02:42:18.400> stewardship<02:42:19.091> of<02:42:19.271> value<02:42:19.601> I'm<02:42:20.051> so 02:42:20.551 --> 02:42:20.561 align:start position:0% community stewardship of value I'm so 02:42:20.561 --> 02:42:22.531 align:start position:0% community stewardship of value I'm so secure<02:42:21.190> an<02:42:21.311> offline<02:42:21.610> first<02:42:21.820> is<02:42:22.061> peer<02:42:22.271> to<02:42:22.301> peer 02:42:22.531 --> 02:42:22.541 align:start position:0% secure an offline first is peer to peer 02:42:22.541 --> 02:42:24.361 align:start position:0% secure an offline first is peer to peer that's<02:42:22.900> what<02:42:23.141> we<02:42:23.320> built<02:42:23.471> the<02:42:23.951> radical<02:42:24.281> step 02:42:24.361 --> 02:42:24.371 align:start position:0% that's what we built the radical step 02:42:24.371 --> 02:42:26.191 align:start position:0% that's what we built the radical step but<02:42:25.001> now<02:42:25.121> we're<02:42:25.271> exploring<02:42:25.570> what<02:42:25.751> it<02:42:25.871> is<02:42:25.991> to 02:42:26.191 --> 02:42:26.201 align:start position:0% but now we're exploring what it is to 02:42:26.201 --> 02:42:27.901 align:start position:0% but now we're exploring what it is to have<02:42:26.230> a<02:42:26.351> community<02:42:26.621> owned<02:42:27.070> encrypted<02:42:27.581> native 02:42:27.901 --> 02:42:27.911 align:start position:0% have a community owned encrypted native 02:42:27.911 --> 02:42:30.421 align:start position:0% have a community owned encrypted native peer<02:42:28.480> to<02:42:28.541> peer<02:42:28.661> collaboration<02:42:29.201> effort<02:42:30.041> with 02:42:30.421 --> 02:42:30.431 align:start position:0% peer to peer collaboration effort with 02:42:30.431 --> 02:42:32.821 align:start position:0% peer to peer collaboration effort with watching<02:42:30.881> so<02:42:31.121> watching<02:42:31.391> as<02:42:31.811> a<02:42:32.110> bunch<02:42:32.681> of 02:42:32.821 --> 02:42:32.831 align:start position:0% watching so watching as a bunch of 02:42:32.831 --> 02:42:34.680 align:start position:0% watching so watching as a bunch of things<02:42:33.070> that<02:42:33.311> I<02:42:33.400> cannot<02:42:33.761> talk<02:42:34.091> about<02:42:34.391> in<02:42:34.570> this 02:42:34.680 --> 02:42:34.690 align:start position:0% things that I cannot talk about in this 02:42:34.690 --> 02:42:36.691 align:start position:0% things that I cannot talk about in this one<02:42:34.871> talk<02:42:35.081> so<02:42:35.291> please<02:42:35.320> come<02:42:35.951> talk<02:42:36.161> to<02:42:36.221> me<02:42:36.311> after 02:42:36.691 --> 02:42:36.701 align:start position:0% one talk so please come talk to me after 02:42:36.701 --> 02:42:38.850 align:start position:0% one talk so please come talk to me after about<02:42:36.820> all<02:42:37.061> of<02:42:37.181> this<02:42:37.271> but<02:42:37.991> for<02:42:38.141> example<02:42:38.531> one 02:42:38.850 --> 02:42:38.860 align:start position:0% about all of this but for example one 02:42:38.860 --> 02:42:40.411 align:start position:0% about all of this but for example one hit<02:42:39.041> ko<02:42:39.190> collaboration<02:42:39.820> beat<02:42:40.001> is<02:42:40.181> we<02:42:40.331> have 02:42:40.411 --> 02:42:40.421 align:start position:0% hit ko collaboration beat is we have 02:42:40.421 --> 02:42:42.180 align:start position:0% hit ko collaboration beat is we have verified<02:42:40.811> wallet<02:42:41.141> set<02:42:41.381> I<02:42:41.411> love<02:42:41.681> direct 02:42:42.180 --> 02:42:42.190 align:start position:0% verified wallet set I love direct 02:42:42.190 --> 02:42:44.331 align:start position:0% verified wallet set I love direct peer-to-peer<02:42:42.400> code<02:42:43.360> blogger<02:42:43.631> ocean 02:42:44.331 --> 02:42:44.341 align:start position:0% peer-to-peer code blogger ocean 02:42:44.341 --> 02:42:46.350 align:start position:0% peer-to-peer code blogger ocean ecosystem<02:42:45.341> stewardship<02:42:45.851> through<02:42:46.061> block 02:42:46.350 --> 02:42:46.360 align:start position:0% ecosystem stewardship through block 02:42:46.360 --> 02:42:48.691 align:start position:0% ecosystem stewardship through block Awards<02:42:46.781> inflation<02:42:47.351> funding<02:42:47.471> what<02:42:48.371> if<02:42:48.461> we<02:42:48.551> had 02:42:48.691 --> 02:42:48.701 align:start position:0% Awards inflation funding what if we had 02:42:48.701 --> 02:42:50.251 align:start position:0% Awards inflation funding what if we had a<02:42:48.881> chair<02:42:49.061> a<02:42:49.091> teacher<02:42:49.360> dependency<02:42:49.871> graphing 02:42:50.251 --> 02:42:50.261 align:start position:0% a chair a teacher dependency graphing 02:42:50.261 --> 02:42:51.541 align:start position:0% a chair a teacher dependency graphing between<02:42:50.561> projects<02:42:50.921> maintainer<02:42:51.251> xand 02:42:51.541 --> 02:42:51.551 align:start position:0% between projects maintainer xand 02:42:51.551 --> 02:42:53.371 align:start position:0% between projects maintainer xand communities<02:42:51.971> so<02:42:52.511> we<02:42:52.541> can<02:42:52.721> understand<02:42:53.141> how<02:42:53.320> we 02:42:53.371 --> 02:42:53.381 align:start position:0% communities so we can understand how we 02:42:53.381 --> 02:42:55.591 align:start position:0% communities so we can understand how we distribute<02:42:53.681> value<02:42:54.190> from<02:42:54.521> a<02:42:54.761> system<02:42:55.391> so<02:42:55.511> we 02:42:55.591 --> 02:42:55.601 align:start position:0% distribute value from a system so we 02:42:55.601 --> 02:42:56.611 align:start position:0% distribute value from a system so we don't<02:42:55.631> have<02:42:55.811> to<02:42:55.900> rely<02:42:56.051> on<02:42:56.171> building<02:42:56.591> a 02:42:56.611 --> 02:42:56.621 align:start position:0% don't have to rely on building a 02:42:56.621 --> 02:42:58.350 align:start position:0% don't have to rely on building a business<02:42:56.891> model<02:42:57.041> for<02:42:57.251> Foss<02:42:57.851> and<02:42:57.881> make<02:42:58.271> an 02:42:58.350 --> 02:42:58.360 align:start position:0% business model for Foss and make an 02:42:58.360 --> 02:42:59.640 align:start position:0% business model for Foss and make an instead<02:42:58.661> created<02:42:58.961> a<02:42:58.991> sustainable<02:42:59.171> economy 02:42:59.640 --> 02:42:59.650 align:start position:0% instead created a sustainable economy 02:42:59.650 --> 02:43:01.921 align:start position:0% instead created a sustainable economy under<02:43:00.281> free<02:43:00.851> and<02:43:00.940> open-source<02:43:01.211> software<02:43:01.391> and 02:43:01.921 --> 02:43:01.931 align:start position:0% under free and open-source software and 02:43:01.931 --> 02:43:03.481 align:start position:0% under free and open-source software and also<02:43:02.471> what<02:43:02.681> if<02:43:02.771> you<02:43:02.831> had<02:43:02.921> a<02:43:02.980> global<02:43:03.281> project 02:43:03.481 --> 02:43:03.491 align:start position:0% also what if you had a global project 02:43:03.491 --> 02:43:05.970 align:start position:0% also what if you had a global project registry<02:43:04.061> of<02:43:04.091> foster<02:43:04.690> projects<02:43:05.110> allowing 02:43:05.970 --> 02:43:05.980 align:start position:0% registry of foster projects allowing 02:43:05.980 --> 02:43:08.251 align:start position:0% registry of foster projects allowing global<02:43:06.431> canonicity<02:43:06.820> and<02:43:07.241> discoverability<02:43:07.781> so 02:43:08.251 --> 02:43:08.261 align:start position:0% global canonicity and discoverability so 02:43:08.261 --> 02:43:10.140 align:start position:0% global canonicity and discoverability so those<02:43:08.440> Network<02:43:08.741> effects<02:43:09.101> that<02:43:09.551> make<02:43:09.761> it<02:43:10.001> come 02:43:10.140 --> 02:43:10.150 align:start position:0% those Network effects that make it come 02:43:10.150 --> 02:43:12.211 align:start position:0% those Network effects that make it come so<02:43:10.301> great<02:43:10.570> with<02:43:11.201> us<02:43:11.320> also<02:43:11.561> add<02:43:11.891> a<02:43:11.921> really 02:43:12.211 --> 02:43:12.221 align:start position:0% so great with us also add a really 02:43:12.221 --> 02:43:14.191 align:start position:0% so great with us also add a really awesome<02:43:12.431> security<02:43:12.971> layer<02:43:13.150> that<02:43:13.421> audible<02:43:14.110> and 02:43:14.191 --> 02:43:14.201 align:start position:0% awesome security layer that audible and 02:43:14.201 --> 02:43:15.871 align:start position:0% awesome security layer that audible and temporary<02:43:14.591> project<02:43:15.041> histories<02:43:15.431> kind<02:43:15.641> of<02:43:15.730> up 02:43:15.871 --> 02:43:15.881 align:start position:0% temporary project histories kind of up 02:43:15.881 --> 02:43:17.671 align:start position:0% temporary project histories kind of up the<02:43:16.061> security<02:43:16.360> that<02:43:16.721> we<02:43:16.841> can<02:43:16.991> have<02:43:17.171> on<02:43:17.440> any 02:43:17.671 --> 02:43:17.681 align:start position:0% the security that we can have on any 02:43:17.681 --> 02:43:20.161 align:start position:0% the security that we can have on any centralized<02:43:18.491> platform<02:43:18.701> so<02:43:19.121> all<02:43:19.271> this<02:43:19.690> is 02:43:20.161 --> 02:43:20.171 align:start position:0% centralized platform so all this is 02:43:20.171 --> 02:43:22.231 align:start position:0% centralized platform so all this is really<02:43:20.471> really<02:43:20.801> cool<02:43:20.980> and<02:43:21.820> we're<02:43:22.001> exploring 02:43:22.231 --> 02:43:22.241 align:start position:0% really really cool and we're exploring 02:43:22.241 --> 02:43:25.350 align:start position:0% really really cool and we're exploring it<02:43:22.570> at<02:43:22.721> radical<02:43:23.251> and<02:43:24.251> really<02:43:24.551> we<02:43:24.881> really<02:43:24.911> think 02:43:25.350 --> 02:43:25.360 align:start position:0% it at radical and really we really think 02:43:25.360 --> 02:43:27.781 align:start position:0% it at radical and really we really think that<02:43:25.421> code<02:43:25.721> collaboration<02:43:26.381> will<02:43:26.671> bring<02:43:27.671> about 02:43:27.781 --> 02:43:27.791 align:start position:0% that code collaboration will bring about 02:43:27.791 --> 02:43:29.611 align:start position:0% that code collaboration will bring about our<02:43:28.121> new<02:43:28.360> vision<02:43:28.631> of<02:43:28.931> what<02:43:29.201> is<02:43:29.320> free<02:43:29.501> and<02:43:29.591> open 02:43:29.611 --> 02:43:29.621 align:start position:0% our new vision of what is free and open 02:43:29.621 --> 02:43:31.621 align:start position:0% our new vision of what is free and open source<02:43:29.831> sustainability<02:43:30.551> mine<02:43:31.360> Abel 02:43:31.621 --> 02:43:31.631 align:start position:0% source sustainability mine Abel 02:43:31.631 --> 02:43:33.751 align:start position:0% source sustainability mine Abel trustless<02:43:32.141> workflows<02:43:32.650> or<02:43:32.860> LaValley<02:43:33.341> exchange 02:43:33.751 --> 02:43:33.761 align:start position:0% trustless workflows or LaValley exchange 02:43:33.761 --> 02:43:36.180 align:start position:0% trustless workflows or LaValley exchange and<02:43:34.001> global<02:43:34.421> canonicity<02:43:34.751> and<02:43:35.741> those<02:43:35.860> network 02:43:36.180 --> 02:43:36.190 align:start position:0% and global canonicity and those network 02:43:36.190 --> 02:43:39.871 align:start position:0% and global canonicity and those network effects<02:43:36.581> that<02:43:36.911> people<02:43:37.331> think<02:43:37.871> is<02:43:38.051> only<02:43:38.881> you 02:43:39.871 --> 02:43:39.881 align:start position:0% effects that people think is only you 02:43:39.881 --> 02:43:42.600 align:start position:0% effects that people think is only you know<02:43:39.911> prone<02:43:40.271> to<02:43:40.541> github<02:43:41.021> so<02:43:41.351> cool<02:43:41.980> come<02:43:42.371> find 02:43:42.600 --> 02:43:42.610 align:start position:0% know prone to github so cool come find 02:43:42.610 --> 02:43:45.301 align:start position:0% know prone to github so cool come find me<02:43:42.730> my<02:43:43.121> name's<02:43:43.301> Abby<02:43:43.511> I'm<02:43:44.051> on<02:43:44.230> Twitter<02:43:44.501> I<02:43:44.831> have 02:43:45.301 --> 02:43:45.311 align:start position:0% me my name's Abby I'm on Twitter I have 02:43:45.311 --> 02:43:47.191 align:start position:0% me my name's Abby I'm on Twitter I have a<02:43:45.341> tick<02:43:45.581> home<02:43:45.761> we're<02:43:46.271> not<02:43:46.391> doing<02:43:46.570> a<02:43:46.631> talk<02:43:46.811> but 02:43:47.191 --> 02:43:47.201 align:start position:0% a tick home we're not doing a talk but 02:43:47.201 --> 02:43:48.901 align:start position:0% a tick home we're not doing a talk but I'll<02:43:47.351> be<02:43:47.471> around<02:43:47.501> so<02:43:47.951> please<02:43:48.371> come<02:43:48.581> talk<02:43:48.730> to<02:43:48.791> me 02:43:48.901 --> 02:43:48.911 align:start position:0% I'll be around so please come talk to me 02:43:48.911 --> 02:43:50.341 align:start position:0% I'll be around so please come talk to me we're<02:43:49.271> going<02:43:49.360> to<02:43:49.421> be<02:43:49.511> building<02:43:49.661> this<02:43:49.871> really 02:43:50.341 --> 02:43:50.351 align:start position:0% we're going to be building this really 02:43:50.351 --> 02:43:50.911 align:start position:0% we're going to be building this really soon 02:43:50.911 --> 02:43:50.921 align:start position:0% soon 02:43:50.921 --> 02:44:04.951 align:start position:0% soon so<02:43:51.251> I'd<02:43:51.371> love<02:43:51.491> to<02:44:02.730> yeah<02:44:03.730> so<02:44:04.091> I'm<02:44:04.331> hosting<02:44:04.811> a 02:44:04.951 --> 02:44:04.961 align:start position:0% so I'd love to yeah so I'm hosting a 02:44:04.961 --> 02:44:06.631 align:start position:0% so I'd love to yeah so I'm hosting a workshop<02:44:05.110> personally<02:44:05.650> on<02:44:05.860> that's<02:44:06.461> called 02:44:06.631 --> 02:44:06.641 align:start position:0% workshop personally on that's called 02:44:06.641 --> 02:44:09.091 align:start position:0% workshop personally on that's called beyond<02:44:06.911> aus<02:44:07.121> that's<02:44:07.511> actually<02:44:07.871> in<02:44:08.051> this<02:44:08.921> is 02:44:09.091 --> 02:44:09.101 align:start position:0% beyond aus that's actually in this is 02:44:09.101 --> 02:44:10.651 align:start position:0% beyond aus that's actually in this is like<02:44:09.251> what<02:44:09.461> it's<02:44:09.581> about<02:44:09.641> that's<02:44:09.940> really<02:44:10.391> great 02:44:10.651 --> 02:44:10.661 align:start position:0% like what it's about that's really great 02:44:10.661 --> 02:44:12.541 align:start position:0% like what it's about that's really great that<02:44:10.871> this<02:44:10.991> is<02:44:11.110> learning<02:44:11.381> here<02:44:11.531> in<02:44:11.591> our<02:44:12.221> shop 02:44:12.541 --> 02:44:12.551 align:start position:0% that this is learning here in our shop 02:44:12.551 --> 02:44:15.600 align:start position:0% that this is learning here in our shop tomorrow<02:44:12.940> at<02:44:13.421> 3:30<02:44:13.991> where<02:44:14.531> we're<02:44:15.011> going<02:44:15.131> to<02:44:15.221> be 02:44:15.600 --> 02:44:15.610 align:start position:0% tomorrow at 3:30 where we're going to be 02:44:15.610 --> 02:44:17.310 align:start position:0% tomorrow at 3:30 where we're going to be diving<02:44:15.820> into<02:44:16.211> like<02:44:16.421> doubts<02:44:16.661> as<02:44:16.931> a<02:44:16.961> design 02:44:17.310 --> 02:44:17.320 align:start position:0% diving into like doubts as a design 02:44:17.320 --> 02:44:19.591 align:start position:0% diving into like doubts as a design space<02:44:17.501> for<02:44:17.831> experimentation<02:44:18.421> so<02:44:19.421> would<02:44:19.570> love 02:44:19.591 --> 02:44:19.601 align:start position:0% space for experimentation so would love 02:44:19.601 --> 02:44:22.051 align:start position:0% space for experimentation so would love to<02:44:19.900> have<02:44:20.021> you<02:44:20.110> guys<02:44:20.141> all<02:44:20.531> here<02:44:20.801> it's<02:44:21.761> on<02:44:21.911> my 02:44:22.051 --> 02:44:22.061 align:start position:0% to have you guys all here it's on my 02:44:22.061 --> 02:44:30.870 align:start position:0% to have you guys all here it's on my Twitter<02:44:22.301> I've<02:44:22.570> been<02:44:22.931> posting<02:44:23.711> about<02:44:23.951> it 02:44:30.870 --> 02:44:30.880 align:start position:0% 02:44:30.880 --> 02:44:33.630 align:start position:0% everyone<02:44:31.930> Michael<02:44:32.930> for<02:44:33.080> three<02:44:33.290> bucks 02:44:33.630 --> 02:44:33.640 align:start position:0% everyone Michael for three bucks 02:44:33.640 --> 02:44:35.740 align:start position:0% everyone Michael for three bucks four-minute<02:44:34.640> lightning<02:44:34.970> talk<02:44:35.149> is<02:44:35.330> too<02:44:35.540> fast 02:44:35.740 --> 02:44:35.750 align:start position:0% four-minute lightning talk is too fast 02:44:35.750 --> 02:44:38.109 align:start position:0% four-minute lightning talk is too fast to<02:44:35.930> cover<02:44:36.109> everything<02:44:36.439> but<02:44:36.920> we'll<02:44:37.819> touch<02:44:38.000> on 02:44:38.109 --> 02:44:38.119 align:start position:0% to cover everything but we'll touch on 02:44:38.119 --> 02:44:39.969 align:start position:0% to cover everything but we'll touch on the<02:44:38.239> important<02:44:38.600> things<02:44:38.630> cool 02:44:39.969 --> 02:44:39.979 align:start position:0% the important things cool 02:44:39.979 --> 02:44:43.090 align:start position:0% the important things cool so<02:44:40.369> as<02:44:40.850> the<02:44:41.810> ipfs<02:44:42.290> team<02:44:42.470> mentioned<02:44:42.800> three 02:44:43.090 --> 02:44:43.100 align:start position:0% so as the ipfs team mentioned three 02:44:43.100 --> 02:44:45.760 align:start position:0% so as the ipfs team mentioned three boxes<02:44:43.460> building<02:44:44.020> identity<02:44:45.020> and<02:44:45.140> data<02:44:45.260> tooling 02:44:45.760 --> 02:44:45.770 align:start position:0% boxes building identity and data tooling 02:44:45.770 --> 02:44:48.070 align:start position:0% boxes building identity and data tooling for<02:44:45.800> me<02:44:46.069> to<02:44:46.159> be<02:44:46.279> apps<02:44:46.460> and<02:44:46.790> really<02:44:47.180> some<02:44:47.930> of<02:44:47.960> the 02:44:48.070 --> 02:44:48.080 align:start position:0% for me to be apps and really some of the 02:44:48.080 --> 02:44:49.450 align:start position:0% for me to be apps and really some of the needs<02:44:48.260> we<02:44:48.439> address<02:44:48.680> in<02:44:48.800> the<02:44:48.859> market<02:44:49.159> were<02:44:49.310> like 02:44:49.450 --> 02:44:49.460 align:start position:0% needs we address in the market were like 02:44:49.460 --> 02:44:52.599 align:start position:0% needs we address in the market were like how<02:44:50.149> do<02:44:50.210> we<02:44:50.479> bring<02:44:50.779> p2p<02:44:51.770> systems<02:44:52.220> to 02:44:52.599 --> 02:44:52.609 align:start position:0% how do we bring p2p systems to 02:44:52.609 --> 02:44:54.760 align:start position:0% how do we bring p2p systems to blockchain<02:44:53.479> users<02:44:53.840> and<02:44:53.989> developers<02:44:54.170> and<02:44:54.619> let 02:44:54.760 --> 02:44:54.770 align:start position:0% blockchain users and developers and let 02:44:54.770 --> 02:44:56.469 align:start position:0% blockchain users and developers and let them<02:44:55.010> together<02:44:55.609> to<02:44:55.939> create<02:44:55.970> a<02:44:56.239> better 02:44:56.469 --> 02:44:56.479 align:start position:0% them together to create a better 02:44:56.479 --> 02:44:59.889 align:start position:0% them together to create a better application<02:44:57.580> I'll<02:44:58.580> skip<02:44:58.850> this<02:44:59.029> and<02:44:59.449> so<02:44:59.659> yeah 02:44:59.889 --> 02:44:59.899 align:start position:0% application I'll skip this and so yeah 02:44:59.899 --> 02:45:01.599 align:start position:0% application I'll skip this and so yeah we've<02:45:00.319> built<02:45:00.529> a<02:45:00.649> framework<02:45:00.890> and<02:45:01.310> really<02:45:01.520> at 02:45:01.599 --> 02:45:01.609 align:start position:0% we've built a framework and really at 02:45:01.609 --> 02:45:04.269 align:start position:0% we've built a framework and really at the<02:45:01.699> core<02:45:01.880> of<02:45:01.939> three<02:45:02.210> boxes<02:45:02.859> and<02:45:03.859> identity 02:45:04.269 --> 02:45:04.279 align:start position:0% the core of three boxes and identity 02:45:04.279 --> 02:45:07.179 align:start position:0% the core of three boxes and identity protocol<02:45:04.729> and<02:45:05.720> developer<02:45:06.260> tool<02:45:06.439> so<02:45:06.859> these<02:45:06.979> two 02:45:07.179 --> 02:45:07.189 align:start position:0% protocol and developer tool so these two 02:45:07.189 --> 02:45:09.280 align:start position:0% protocol and developer tool so these two components<02:45:07.489> together<02:45:07.790> allow<02:45:08.330> us<02:45:08.840> to<02:45:08.989> connect 02:45:09.280 --> 02:45:09.290 align:start position:0% components together allow us to connect 02:45:09.290 --> 02:45:11.559 align:start position:0% components together allow us to connect to<02:45:09.380> my<02:45:09.800> PFS<02:45:09.949> storage<02:45:10.580> that<02:45:10.850> lives<02:45:11.029> on<02:45:11.149> top<02:45:11.300> of 02:45:11.559 --> 02:45:11.569 align:start position:0% to my PFS storage that lives on top of 02:45:11.569 --> 02:45:14.710 align:start position:0% to my PFS storage that lives on top of or<02:45:12.260> below<02:45:12.560> distributed<02:45:13.310> databases<02:45:13.729> and 02:45:14.710 --> 02:45:14.720 align:start position:0% or below distributed databases and 02:45:14.720 --> 02:45:16.179 align:start position:0% or below distributed databases and connect<02:45:14.989> those<02:45:15.109> to<02:45:15.409> the<02:45:15.560> clock<02:45:15.770> Jimmy<02:45:16.040> Mullins 02:45:16.179 --> 02:45:16.189 align:start position:0% connect those to the clock Jimmy Mullins 02:45:16.189 --> 02:45:18.820 align:start position:0% connect those to the clock Jimmy Mullins and<02:45:16.670> so<02:45:16.970> really<02:45:17.810> we<02:45:18.170> looked<02:45:18.380> up<02:45:18.470> the<02:45:18.500> needs<02:45:18.739> of 02:45:18.820 --> 02:45:18.830 align:start position:0% and so really we looked up the needs of 02:45:18.830 --> 02:45:21.460 align:start position:0% and so really we looked up the needs of DAP<02:45:19.040> devs<02:45:19.340> to<02:45:19.520> start<02:45:19.729> building<02:45:20.109> and<02:45:21.109> people 02:45:21.460 --> 02:45:21.470 align:start position:0% DAP devs to start building and people 02:45:21.470 --> 02:45:23.979 align:start position:0% DAP devs to start building and people really<02:45:21.939> that<02:45:22.939> want<02:45:23.180> to<02:45:23.239> implement<02:45:23.569> a<02:45:23.630> service 02:45:23.979 --> 02:45:23.989 align:start position:0% really that want to implement a service 02:45:23.989 --> 02:45:26.679 align:start position:0% really that want to implement a service p2p<02:45:24.319> architecture<02:45:24.949> really<02:45:25.880> also<02:45:26.330> just<02:45:26.540> want 02:45:26.679 --> 02:45:26.689 align:start position:0% p2p architecture really also just want 02:45:26.689 --> 02:45:28.780 align:start position:0% p2p architecture really also just want to<02:45:26.750> build<02:45:26.930> useful<02:45:27.140> engaging<02:45:27.680> apps<02:45:27.979> because 02:45:28.780 --> 02:45:28.790 align:start position:0% to build useful engaging apps because 02:45:28.790 --> 02:45:31.389 align:start position:0% to build useful engaging apps because they<02:45:28.880> still<02:45:29.090> need<02:45:29.239> users<02:45:29.600> and<02:45:30.050> so<02:45:30.649> on<02:45:31.220> the 02:45:31.389 --> 02:45:31.399 align:start position:0% they still need users and so on the 02:45:31.399 --> 02:45:33.189 align:start position:0% they still need users and so on the other<02:45:31.520> side<02:45:31.760> of<02:45:31.909> that<02:45:32.029> looking<02:45:32.810> at<02:45:32.960> the<02:45:33.050> needs 02:45:33.189 --> 02:45:33.199 align:start position:0% other side of that looking at the needs 02:45:33.199 --> 02:45:34.540 align:start position:0% other side of that looking at the needs of<02:45:33.290> users<02:45:33.500> they<02:45:33.830> really<02:45:34.040> don't<02:45:34.130> care<02:45:34.399> about 02:45:34.540 --> 02:45:34.550 align:start position:0% of users they really don't care about 02:45:34.550 --> 02:45:37.479 align:start position:0% of users they really don't care about the<02:45:34.790> tech<02:45:35.350> just<02:45:36.350> sort<02:45:36.560> of<02:45:36.619> what<02:45:37.069> they<02:45:37.189> can<02:45:37.250> do 02:45:37.479 --> 02:45:37.489 align:start position:0% the tech just sort of what they can do 02:45:37.489 --> 02:45:40.740 align:start position:0% the tech just sort of what they can do with<02:45:37.609> it<02:45:37.729> and<02:45:37.909> so<02:45:39.100> we<02:45:40.100> built<02:45:40.340> this<02:45:40.430> framework 02:45:40.740 --> 02:45:40.750 align:start position:0% with it and so we built this framework 02:45:40.750 --> 02:45:43.059 align:start position:0% with it and so we built this framework but<02:45:41.750> more<02:45:42.199> importantly<02:45:42.590> let's<02:45:42.830> talk<02:45:42.949> about 02:45:43.059 --> 02:45:43.069 align:start position:0% but more importantly let's talk about 02:45:43.069 --> 02:45:45.460 align:start position:0% but more importantly let's talk about this<02:45:43.310> cool<02:45:44.149> so<02:45:44.300> the<02:45:44.420> decentralized<02:45:45.020> identity 02:45:45.460 --> 02:45:45.470 align:start position:0% this cool so the decentralized identity 02:45:45.470 --> 02:45:47.950 align:start position:0% this cool so the decentralized identity stack<02:45:45.850> really<02:45:46.850> what<02:45:47.090> we<02:45:47.210> wanted<02:45:47.449> to<02:45:47.569> do<02:45:47.750> is 02:45:47.950 --> 02:45:47.960 align:start position:0% stack really what we wanted to do is 02:45:47.960 --> 02:45:50.170 align:start position:0% stack really what we wanted to do is utilize<02:45:48.350> the<02:45:48.800> existing<02:45:49.100> wallets<02:45:49.819> that<02:45:49.939> people 02:45:50.170 --> 02:45:50.180 align:start position:0% utilize the existing wallets that people 02:45:50.180 --> 02:45:51.790 align:start position:0% utilize the existing wallets that people already<02:45:50.390> have<02:45:50.720> it's<02:45:51.170> like<02:45:51.229> if<02:45:51.409> you<02:45:51.470> have<02:45:51.590> meta 02:45:51.790 --> 02:45:51.800 align:start position:0% already have it's like if you have meta 02:45:51.800 --> 02:45:53.011 align:start position:0% already have it's like if you have meta master 02:45:53.011 --> 02:45:53.021 align:start position:0% master 02:45:53.021 --> 02:45:56.280 align:start position:0% master wallets<02:45:53.620> how<02:45:54.490> can<02:45:54.700> we<02:45:54.820> let<02:45:55.000> those<02:45:55.240> connect<02:45:56.170> it 02:45:56.280 --> 02:45:56.290 align:start position:0% wallets how can we let those connect it 02:45:56.290 --> 02:45:58.290 align:start position:0% wallets how can we let those connect it to<02:45:56.440> a<02:45:56.471> control<02:45:56.860> user<02:45:57.160> data<02:45:57.400> that's<02:45:57.760> stored<02:45:57.851> on 02:45:58.290 --> 02:45:58.300 align:start position:0% to a control user data that's stored on 02:45:58.300 --> 02:46:00.240 align:start position:0% to a control user data that's stored on the<02:45:58.450> distributed<02:45:58.900> weapon<02:45:59.200> so<02:45:59.410> our<02:46:00.010> first 02:46:00.240 --> 02:46:00.250 align:start position:0% the distributed weapon so our first 02:46:00.250 --> 02:46:02.160 align:start position:0% the distributed weapon so our first implementation<02:46:00.521> is<02:46:01.061> or<02:46:01.690> meant<02:46:01.900> to<02:46:02.021> be 02:46:02.160 --> 02:46:02.170 align:start position:0% implementation is or meant to be 02:46:02.170 --> 02:46:05.430 align:start position:0% implementation is or meant to be instances<02:46:02.710> that<02:46:03.130> are<02:46:03.190> manifest<02:46:03.990> but<02:46:04.990> really 02:46:05.430 --> 02:46:05.440 align:start position:0% instances that are manifest but really 02:46:05.440 --> 02:46:07.620 align:start position:0% instances that are manifest but really we<02:46:05.771> can<02:46:05.891> abstract<02:46:06.250> these<02:46:06.580> and<02:46:06.820> sort<02:46:06.910> of<02:46:07.030> let 02:46:07.620 --> 02:46:07.630 align:start position:0% we can abstract these and sort of let 02:46:07.630 --> 02:46:09.511 align:start position:0% we can abstract these and sort of let users<02:46:07.900> control<02:46:08.351> and<02:46:08.561> connect<02:46:08.830> to<02:46:08.891> many 02:46:09.511 --> 02:46:09.521 align:start position:0% users control and connect to many 02:46:09.521 --> 02:46:11.100 align:start position:0% users control and connect to many different<02:46:09.670> databases<02:46:10.240> that<02:46:10.420> are<02:46:10.480> sort<02:46:10.840> of<02:46:10.900> on 02:46:11.100 --> 02:46:11.110 align:start position:0% different databases that are sort of on 02:46:11.110 --> 02:46:13.440 align:start position:0% different databases that are sort of on different<02:46:11.500> storage<02:46:11.740> systems<02:46:12.221> and<02:46:12.880> so<02:46:13.030> here<02:46:13.271> we 02:46:13.440 --> 02:46:13.450 align:start position:0% different storage systems and so here we 02:46:13.450 --> 02:46:16.680 align:start position:0% different storage systems and so here we design<02:46:13.750> this<02:46:13.900> protocol<02:46:14.351> 3<02:46:14.860> ID<02:46:15.330> which<02:46:16.330> really 02:46:16.680 --> 02:46:16.690 align:start position:0% design this protocol 3 ID which really 02:46:16.690 --> 02:46:18.870 align:start position:0% design this protocol 3 ID which really an<02:46:17.110> enable<02:46:17.710> system<02:46:18.101> so<02:46:18.221> it's<02:46:18.370> like<02:46:18.490> an<02:46:18.580> access 02:46:18.870 --> 02:46:18.880 align:start position:0% an enable system so it's like an access 02:46:18.880 --> 02:46:20.700 align:start position:0% an enable system so it's like an access control<02:46:19.090> encryption<02:46:19.900> data<02:46:20.230> authentication 02:46:20.700 --> 02:46:20.710 align:start position:0% control encryption data authentication 02:46:20.710 --> 02:46:23.250 align:start position:0% control encryption data authentication protocol<02:46:21.460> that<02:46:22.000> allows<02:46:22.150> many<02:46:22.780> different 02:46:23.250 --> 02:46:23.260 align:start position:0% protocol that allows many different 02:46:23.260 --> 02:46:26.220 align:start position:0% protocol that allows many different accounts<02:46:24.190> and<02:46:24.280> keys<02:46:24.550> to<02:46:24.971> connect<02:46:25.840> to<02:46:25.990> the<02:46:26.080> same 02:46:26.220 --> 02:46:26.230 align:start position:0% accounts and keys to connect to the same 02:46:26.230 --> 02:46:29.100 align:start position:0% accounts and keys to connect to the same ID<02:46:26.471> which<02:46:27.370> is<02:46:27.610> actually<02:46:28.240> what<02:46:28.450> authorizes 02:46:29.100 --> 02:46:29.110 align:start position:0% ID which is actually what authorizes 02:46:29.110 --> 02:46:32.220 align:start position:0% ID which is actually what authorizes data<02:46:29.380> on<02:46:29.620> the<02:46:29.860> systems<02:46:30.721> and<02:46:31.721> so<02:46:31.900> all<02:46:32.080> the<02:46:32.200> other 02:46:32.220 --> 02:46:32.230 align:start position:0% data on the systems and so all the other 02:46:32.230 --> 02:46:35.220 align:start position:0% data on the systems and so all the other stuff<02:46:32.530> we've<02:46:32.710> built<02:46:33.010> we<02:46:33.221> have<02:46:33.340> SDKs<02:46:34.090> so<02:46:34.840> if 02:46:35.220 --> 02:46:35.230 align:start position:0% stuff we've built we have SDKs so if 02:46:35.230 --> 02:46:36.990 align:start position:0% stuff we've built we have SDKs so if you're<02:46:35.410> an<02:46:35.500> app<02:46:35.620> developer<02:46:35.650> you<02:46:36.460> can<02:46:36.730> use<02:46:36.851> the 02:46:36.990 --> 02:46:37.000 align:start position:0% you're an app developer you can use the 02:46:37.000 --> 02:46:40.200 align:start position:0% you're an app developer you can use the Box<02:46:37.240> SDK<02:46:37.780> to<02:46:38.500> do<02:46:38.650> all<02:46:38.891> these<02:46:39.190> things<02:46:39.250> so<02:46:39.971> it 02:46:40.200 --> 02:46:40.210 align:start position:0% Box SDK to do all these things so it 02:46:40.210 --> 02:46:42.750 align:start position:0% Box SDK to do all these things so it makes<02:46:40.391> identity<02:46:40.931> easy<02:46:41.170> authentication<02:46:41.760> user 02:46:42.750 --> 02:46:42.760 align:start position:0% makes identity easy authentication user 02:46:42.760 --> 02:46:45.140 align:start position:0% makes identity easy authentication user profiles<02:46:43.330> for<02:46:43.630> social<02:46:44.050> interactions 02:46:45.140 --> 02:46:45.150 align:start position:0% profiles for social interactions 02:46:45.150 --> 02:46:47.761 align:start position:0% profiles for social interactions generalized<02:46:46.150> storage<02:46:46.601> for<02:46:46.900> our<02:46:47.050> content 02:46:47.761 --> 02:46:47.771 align:start position:0% generalized storage for our content 02:46:47.771 --> 02:46:52.261 align:start position:0% generalized storage for our content specific<02:46:48.160> data<02:46:48.370> and<02:46:49.740> messaging<02:46:50.740> and<02:46:51.090> to<02:46:52.090> make 02:46:52.261 --> 02:46:52.271 align:start position:0% specific data and messaging and to make 02:46:52.271 --> 02:46:55.440 align:start position:0% specific data and messaging and to make it<02:46:52.300> even<02:46:52.570> easier<02:46:52.891> if<02:46:53.891> you're<02:46:54.101> lazy<02:46:54.311> we<02:46:54.910> have<02:46:55.150> a 02:46:55.440 --> 02:46:55.450 align:start position:0% it even easier if you're lazy we have a 02:46:55.450 --> 02:46:57.270 align:start position:0% it even easier if you're lazy we have a hub<02:46:55.960> which<02:46:56.230> is<02:46:56.351> already<02:46:56.561> an<02:46:56.891> out-of-the-box 02:46:57.270 --> 02:46:57.280 align:start position:0% hub which is already an out-of-the-box 02:46:57.280 --> 02:46:59.730 align:start position:0% hub which is already an out-of-the-box profile<02:46:57.790> application<02:46:58.410> profile<02:46:59.410> numbers 02:46:59.730 --> 02:46:59.740 align:start position:0% profile application profile numbers 02:46:59.740 --> 02:47:01.470 align:start position:0% profile application profile numbers which<02:46:59.950> is<02:47:00.040> a<02:47:00.101> drop<02:47:00.311> in<02:47:00.340> component<02:47:01.030> that<02:47:01.210> is 02:47:01.470 --> 02:47:01.480 align:start position:0% which is a drop in component that is 02:47:01.480 --> 02:47:02.820 align:start position:0% which is a drop in component that is like<02:47:01.690> Twitter<02:47:01.960> when<02:47:02.141> you<02:47:02.230> hover<02:47:02.351> over<02:47:02.471> name 02:47:02.820 --> 02:47:02.830 align:start position:0% like Twitter when you hover over name 02:47:02.830 --> 02:47:04.520 align:start position:0% like Twitter when you hover over name you<02:47:03.190> get<02:47:03.311> the<02:47:03.400> social<02:47:03.730> profile<02:47:04.061> and<02:47:04.240> vote 02:47:04.520 --> 02:47:04.530 align:start position:0% you get the social profile and vote 02:47:04.530 --> 02:47:06.841 align:start position:0% you get the social profile and vote comments<02:47:05.530> rejecting<02:47:05.920> demo<02:47:06.280> was<02:47:06.610> just<02:47:06.760> the 02:47:06.841 --> 02:47:06.851 align:start position:0% comments rejecting demo was just the 02:47:06.851 --> 02:47:08.580 align:start position:0% comments rejecting demo was just the commenting<02:47:07.360> plugin<02:47:07.721> kind<02:47:07.960> of<02:47:08.021> like<02:47:08.141> discussed 02:47:08.580 --> 02:47:08.590 align:start position:0% commenting plugin kind of like discussed 02:47:08.590 --> 02:47:11.250 align:start position:0% commenting plugin kind of like discussed but<02:47:09.070> built<02:47:09.311> on<02:47:09.460> the<02:47:09.580> sentiment<02:47:09.971> systems<02:47:10.360> and 02:47:11.250 --> 02:47:11.260 align:start position:0% but built on the sentiment systems and 02:47:11.260 --> 02:47:13.200 align:start position:0% but built on the sentiment systems and chat<02:47:11.530> box<02:47:11.771> there's<02:47:12.010> a<02:47:12.130> little<02:47:12.400> tool<02:47:12.610> box<02:47:12.880> for 02:47:13.200 --> 02:47:13.210 align:start position:0% chat box there's a little tool box for 02:47:13.210 --> 02:47:15.450 align:start position:0% chat box there's a little tool box for the<02:47:13.271> corner<02:47:13.590> and<02:47:14.590> identity<02:47:15.101> wallet<02:47:15.370> is 02:47:15.450 --> 02:47:15.460 align:start position:0% the corner and identity wallet is 02:47:15.460 --> 02:47:16.650 align:start position:0% the corner and identity wallet is actually<02:47:15.790> what<02:47:15.940> wallet<02:47:16.210> developers 02:47:16.650 --> 02:47:16.660 align:start position:0% actually what wallet developers 02:47:16.660 --> 02:47:18.961 align:start position:0% actually what wallet developers implement<02:47:16.840> to<02:47:17.681> add<02:47:17.860> three<02:47:18.160> ID<02:47:18.340> to<02:47:18.851> their 02:47:18.961 --> 02:47:18.971 align:start position:0% implement to add three ID to their 02:47:18.971 --> 02:47:20.280 align:start position:0% implement to add three ID to their system<02:47:19.391> and<02:47:19.570> kind<02:47:19.660> of<02:47:19.750> like<02:47:19.870> ties<02:47:20.080> it<02:47:20.230> all 02:47:20.280 --> 02:47:20.290 align:start position:0% system and kind of like ties it all 02:47:20.290 --> 02:47:22.910 align:start position:0% system and kind of like ties it all together<02:47:20.971> we<02:47:21.971> just<02:47:22.000> talked<02:47:22.271> about<02:47:22.300> this 02:47:22.910 --> 02:47:22.920 align:start position:0% together we just talked about this 02:47:22.920 --> 02:47:25.350 align:start position:0% together we just talked about this agenda<02:47:23.920> new<02:47:24.101> all<02:47:24.221> SDKs<02:47:24.700> like<02:47:24.910> why<02:47:25.090> would<02:47:25.330> you 02:47:25.350 --> 02:47:25.360 align:start position:0% agenda new all SDKs like why would you 02:47:25.360 --> 02:47:27.450 align:start position:0% agenda new all SDKs like why would you do<02:47:25.630> this<02:47:25.660> this<02:47:26.530> is<02:47:26.650> actually<02:47:26.920> what<02:47:27.010> implements 02:47:27.450 --> 02:47:27.460 align:start position:0% do this this is actually what implements 02:47:27.460 --> 02:47:30.150 align:start position:0% do this this is actually what implements three<02:47:27.641> ID<02:47:27.820> kind<02:47:28.601> of<02:47:28.660> like<02:47:28.840> web<02:47:29.710> through<02:47:29.920> junior 02:47:30.150 --> 02:47:30.160 align:start position:0% three ID kind of like web through junior 02:47:30.160 --> 02:47:32.131 align:start position:0% three ID kind of like web through junior ethers<02:47:30.550> dance<02:47:30.790> does<02:47:31.120> for<02:47:31.480> the<02:47:31.750> etherium 02:47:32.131 --> 02:47:32.141 align:start position:0% ethers dance does for the etherium 02:47:32.141 --> 02:47:34.500 align:start position:0% ethers dance does for the etherium protocol<02:47:32.590> identity<02:47:33.400> wallet<02:47:33.670> does<02:47:33.940> for<02:47:34.271> three 02:47:34.500 --> 02:47:34.510 align:start position:0% protocol identity wallet does for three 02:47:34.510 --> 02:47:37.110 align:start position:0% protocol identity wallet does for three ID<02:47:34.660> so<02:47:35.290> it<02:47:35.320> sort<02:47:35.590> of<02:47:35.650> works<02:47:35.860> the<02:47:36.010> same<02:47:36.160> way 02:47:37.110 --> 02:47:37.120 align:start position:0% ID so it sort of works the same way 02:47:37.120 --> 02:47:38.091 align:start position:0% ID so it sort of works the same way it's 02:47:38.091 --> 02:47:38.101 align:start position:0% it's 02:47:38.101 --> 02:47:41.060 align:start position:0% it's with<02:47:38.670> existing<02:47:38.940> keys<02:47:39.590> it<02:47:40.590> works<02:47:40.830> in<02:47:41.040> different 02:47:41.060 --> 02:47:41.070 align:start position:0% with existing keys it works in different 02:47:41.070 --> 02:47:43.990 align:start position:0% with existing keys it works in different contexts<02:47:41.880> react<02:47:42.181> native<02:47:42.360> nodejs 02:47:43.990 --> 02:47:44.000 align:start position:0% contexts react native nodejs 02:47:44.000 --> 02:47:46.341 align:start position:0% contexts react native nodejs can<02:47:45.000> support<02:47:45.240> different<02:47:45.450> transports<02:47:46.110> between 02:47:46.341 --> 02:47:46.351 align:start position:0% can support different transports between 02:47:46.351 --> 02:47:48.020 align:start position:0% can support different transports between wallets<02:47:46.681> and<02:47:46.771> apps<02:47:46.950> like<02:47:47.190> wallet<02:47:47.460> connect<02:47:47.761> or 02:47:48.020 --> 02:47:48.030 align:start position:0% wallets and apps like wallet connect or 02:47:48.030 --> 02:47:51.261 align:start position:0% wallets and apps like wallet connect or directly<02:47:48.330> in<02:47:48.450> the<02:47:48.511> browser<02:47:49.641> yeah<02:47:50.670> and<02:47:50.910> it's 02:47:51.261 --> 02:47:51.271 align:start position:0% directly in the browser yeah and it's 02:47:51.271 --> 02:47:54.711 align:start position:0% directly in the browser yeah and it's more<02:47:51.450> secure<02:47:51.811> for<02:47:52.051> signing<02:47:52.410> keys<02:47:52.700> cool<02:47:53.721> so 02:47:54.711 --> 02:47:54.721 align:start position:0% more secure for signing keys cool so 02:47:54.721 --> 02:47:55.881 align:start position:0% more secure for signing keys cool so here's<02:47:54.900> how<02:47:55.021> you<02:47:55.080> can<02:47:55.200> build<02:47:55.290> app<02:47:55.530> so<02:47:55.681> three 02:47:55.881 --> 02:47:55.891 align:start position:0% here's how you can build app so three 02:47:55.891 --> 02:47:56.930 align:start position:0% here's how you can build app so three locks<02:47:56.101> there's<02:47:56.280> really<02:47:56.400> like<02:47:56.610> three 02:47:56.930 --> 02:47:56.940 align:start position:0% locks there's really like three 02:47:56.940 --> 02:47:59.240 align:start position:0% locks there's really like three different<02:47:57.271> models<02:47:57.420> so<02:47:58.351> if<02:47:58.740> your<02:47:58.860> app<02:47:59.011> has<02:47:59.040> a 02:47:59.240 --> 02:47:59.250 align:start position:0% different models so if your app has a 02:47:59.250 --> 02:48:00.110 align:start position:0% different models so if your app has a built-in<02:47:59.670> wallet 02:48:00.110 --> 02:48:00.120 align:start position:0% built-in wallet 02:48:00.120 --> 02:48:01.850 align:start position:0% built-in wallet so<02:48:00.420> it's<02:48:00.601> either<02:48:00.780> self-contained<02:48:01.380> mobile<02:48:01.650> app 02:48:01.850 --> 02:48:01.860 align:start position:0% so it's either self-contained mobile app 02:48:01.860 --> 02:48:04.671 align:start position:0% so it's either self-contained mobile app or<02:48:02.601> if<02:48:03.601> you're<02:48:03.840> obviously<02:48:03.931> posting<02:48:04.440> it<02:48:04.530> for 02:48:04.671 --> 02:48:04.681 align:start position:0% or if you're obviously posting it for 02:48:04.681 --> 02:48:05.961 align:start position:0% or if you're obviously posting it for your<02:48:04.771> users<02:48:05.070> you<02:48:05.250> can<02:48:05.370> do<02:48:05.490> something<02:48:05.820> like 02:48:05.961 --> 02:48:05.971 align:start position:0% your users you can do something like 02:48:05.971 --> 02:48:08.631 align:start position:0% your users you can do something like this<02:48:06.290> where<02:48:07.290> you<02:48:07.471> implement<02:48:07.920> identity<02:48:08.400> wallet 02:48:08.631 --> 02:48:08.641 align:start position:0% this where you implement identity wallet 02:48:08.641 --> 02:48:11.150 align:start position:0% this where you implement identity wallet and<02:48:08.761> three<02:48:09.061> March<02:48:09.271> to<02:48:09.450> s<02:48:09.590> if<02:48:10.590> it<02:48:10.740> runs<02:48:10.920> in<02:48:11.101> a 02:48:11.150 --> 02:48:11.160 align:start position:0% and three March to s if it runs in a 02:48:11.160 --> 02:48:13.400 align:start position:0% and three March to s if it runs in a browser<02:48:11.280> and<02:48:11.820> the<02:48:12.420> browser<02:48:12.450> is<02:48:12.870> facilitating 02:48:13.400 --> 02:48:13.410 align:start position:0% browser and the browser is facilitating 02:48:13.410 --> 02:48:14.961 align:start position:0% browser and the browser is facilitating the<02:48:13.471> communication<02:48:13.620> such<02:48:14.280> as<02:48:14.311> they<02:48:14.610> can<02:48:14.790> meta 02:48:14.961 --> 02:48:14.971 align:start position:0% the communication such as they can meta 02:48:14.971 --> 02:48:17.421 align:start position:0% the communication such as they can meta mask<02:48:15.240> it's<02:48:16.230> also<02:48:16.351> running<02:48:16.650> that<02:48:16.891> meta<02:48:17.221> mask 02:48:17.421 --> 02:48:17.431 align:start position:0% mask it's also running that meta mask 02:48:17.431 --> 02:48:19.761 align:start position:0% mask it's also running that meta mask would<02:48:17.610> implement<02:48:17.880> any<02:48:18.330> wallet<02:48:18.511> SDK<02:48:18.990> you<02:48:19.620> would 02:48:19.761 --> 02:48:19.771 align:start position:0% would implement any wallet SDK you would 02:48:19.771 --> 02:48:21.830 align:start position:0% would implement any wallet SDK you would pass<02:48:19.950> the<02:48:20.160> provider<02:48:20.551> to<02:48:21.330> the<02:48:21.360> app<02:48:21.601> that's 02:48:21.830 --> 02:48:21.840 align:start position:0% pass the provider to the app that's 02:48:21.840 --> 02:48:25.160 align:start position:0% pass the provider to the app that's integrated<02:48:22.500> with<02:48:22.650> free<02:48:22.980> box<02:48:23.190> tasks<02:48:23.790> and<02:48:24.750> also 02:48:25.160 --> 02:48:25.170 align:start position:0% integrated with free box tasks and also 02:48:25.170 --> 02:48:27.110 align:start position:0% integrated with free box tasks and also external<02:48:25.891> wallet<02:48:26.190> so<02:48:26.370> this<02:48:26.521> is<02:48:26.641> like<02:48:26.790> a<02:48:26.820> mobile 02:48:27.110 --> 02:48:27.120 align:start position:0% external wallet so this is like a mobile 02:48:27.120 --> 02:48:28.970 align:start position:0% external wallet so this is like a mobile wallet<02:48:27.450> that<02:48:28.080> uses<02:48:28.351> wallet<02:48:28.620> and<02:48:28.771> I'm<02:48:28.860> sure 02:48:28.970 --> 02:48:28.980 align:start position:0% wallet that uses wallet and I'm sure 02:48:28.980 --> 02:48:30.501 align:start position:0% wallet that uses wallet and I'm sure some<02:48:29.160> other<02:48:29.311> transport<02:48:29.940> to<02:48:30.090> connect<02:48:30.330> to<02:48:30.450> an 02:48:30.501 --> 02:48:30.511 align:start position:0% some other transport to connect to an 02:48:30.511 --> 02:48:33.291 align:start position:0% some other transport to connect to an application<02:48:31.610> yeah<02:48:32.610> here's<02:48:32.910> some<02:48:32.971> plugins 02:48:33.291 --> 02:48:33.301 align:start position:0% application yeah here's some plugins 02:48:33.301 --> 02:48:36.950 align:start position:0% application yeah here's some plugins will<02:48:34.230> make<02:48:34.771> it<02:48:34.891> really<02:48:35.040> easy<02:48:35.130> to<02:48:35.460> build<02:48:35.960> and 02:48:36.950 --> 02:48:36.960 align:start position:0% will make it really easy to build and 02:48:36.960 --> 02:48:38.751 align:start position:0% will make it really easy to build and that's<02:48:37.351> probably<02:48:37.801> all<02:48:37.950> we<02:48:38.130> have<02:48:38.280> you<02:48:38.551> can<02:48:38.670> make 02:48:38.751 --> 02:48:38.761 align:start position:0% that's probably all we have you can make 02:48:38.761 --> 02:48:43.609 align:start position:0% that's probably all we have you can make a<02:48:38.790> profile<02:48:39.240> thanks 02:48:43.609 --> 02:48:43.619 align:start position:0% 02:48:43.619 --> 02:48:47.399 align:start position:0% okay<02:48:44.669> so<02:48:45.669> I'm<02:48:46.089> actually<02:48:46.299> proposing<02:48:47.199> something 02:48:47.399 --> 02:48:47.409 align:start position:0% okay so I'm actually proposing something 02:48:47.409 --> 02:48:50.219 align:start position:0% okay so I'm actually proposing something but<02:48:47.859> I'm<02:48:48.159> basically<02:48:48.819> a<02:48:49.119> collection<02:48:49.569> of<02:48:49.899> do<02:48:50.079> to 02:48:50.219 --> 02:48:50.229 align:start position:0% but I'm basically a collection of do to 02:48:50.229 --> 02:48:51.869 align:start position:0% but I'm basically a collection of do to prisoner<02:48:50.709> since<02:48:51.069> it<02:48:51.279> ever<02:48:51.429> going<02:48:51.579> to<02:48:51.669> share 02:48:51.869 --> 02:48:51.879 align:start position:0% prisoner since it ever going to share 02:48:51.879 --> 02:48:54.449 align:start position:0% prisoner since it ever going to share what<02:48:52.119> propose<02:48:52.419> oh<02:48:52.600> that<02:48:52.869> is<02:48:53.109> pure<02:48:53.529> long<02:48:53.739> finger 02:48:54.449 --> 02:48:54.459 align:start position:0% what propose oh that is pure long finger 02:48:54.459 --> 02:48:56.999 align:start position:0% what propose oh that is pure long finger brother<02:48:54.819> Research<02:48:55.479> Board<02:48:55.659> which<02:48:56.469> is<02:48:56.499> someone 02:48:56.999 --> 02:48:57.009 align:start position:0% brother Research Board which is someone 02:48:57.009 --> 02:48:58.709 align:start position:0% brother Research Board which is someone close<02:48:57.429> to<02:48:57.759> have<02:48:57.969> the<02:48:58.060> humming<02:48:58.299> browning<02:48:58.629> on 02:48:58.709 --> 02:48:58.719 align:start position:0% close to have the humming browning on 02:48:58.719 --> 02:49:01.050 align:start position:0% close to have the humming browning on your<02:48:58.839> theory<02:48:58.989> it's<02:48:59.469> not<02:48:59.589> a<02:48:59.829> so<02:49:00.129> so<02:49:00.879> Who 02:49:01.050 --> 02:49:01.060 align:start position:0% your theory it's not a so so Who 02:49:01.060 --> 02:49:03.059 align:start position:0% your theory it's not a so so Who am<02:49:01.119> I<02:49:01.299> the<02:49:01.600> gym<02:49:01.810> I'm<02:49:02.049> jutsu<02:49:02.439> from<02:49:02.619> Taiwan 02:49:03.059 --> 02:49:03.069 align:start position:0% am I the gym I'm jutsu from Taiwan 02:49:03.069 --> 02:49:05.579 align:start position:0% am I the gym I'm jutsu from Taiwan Taipei<02:49:03.279> I'm<02:49:03.579> a<02:49:03.850> Washington<02:49:04.749> TLT<02:49:05.199> researcher 02:49:05.579 --> 02:49:05.589 align:start position:0% Taipei I'm a Washington TLT researcher 02:49:05.589 --> 02:49:09.869 align:start position:0% Taipei I'm a Washington TLT researcher and<02:49:06.629> so<02:49:07.629> I<02:49:08.020> basically<02:49:08.859> do<02:49:09.310> a<02:49:09.339> bunch<02:49:09.789> of 02:49:09.869 --> 02:49:09.879 align:start position:0% and so I basically do a bunch of 02:49:09.879 --> 02:49:11.550 align:start position:0% and so I basically do a bunch of different<02:49:10.329> different<02:49:11.289> researchers 02:49:11.550 --> 02:49:11.560 align:start position:0% different different researchers 02:49:11.560 --> 02:49:13.349 align:start position:0% different different researchers including<02:49:12.189> comes<02:49:12.369> in<02:49:12.489> support<02:49:12.789> of<02:49:12.819> ghosts<02:49:12.999> and 02:49:13.349 --> 02:49:13.359 align:start position:0% including comes in support of ghosts and 02:49:13.359 --> 02:49:15.389 align:start position:0% including comes in support of ghosts and unfortunately<02:49:14.350> one<02:49:14.619> of<02:49:14.739> my<02:49:14.889> article<02:49:15.310> is 02:49:15.389 --> 02:49:15.399 align:start position:0% unfortunately one of my article is 02:49:15.399 --> 02:49:17.819 align:start position:0% unfortunately one of my article is twitted<02:49:15.759> by<02:49:15.879> Potomac<02:49:16.449> like<02:49:16.719> one<02:49:17.079> week<02:49:17.199> ago<02:49:17.350> and 02:49:17.819 --> 02:49:17.829 align:start position:0% twitted by Potomac like one week ago and 02:49:17.829 --> 02:49:20.969 align:start position:0% twitted by Potomac like one week ago and just<02:49:18.039> to<02:49:18.100> talk<02:49:18.279> about<02:49:18.429> Casper<02:49:18.879> MFG<02:49:19.979> explainer 02:49:20.969 --> 02:49:20.979 align:start position:0% just to talk about Casper MFG explainer 02:49:20.979 --> 02:49:26.340 align:start position:0% just to talk about Casper MFG explainer so<02:49:21.819> speed<02:49:22.119> also<02:49:22.589> so<02:49:23.589> and<02:49:24.100> today<02:49:25.060> so<02:49:25.810> yesterday 02:49:26.340 --> 02:49:26.350 align:start position:0% so speed also so and today so yesterday 02:49:26.350 --> 02:49:28.019 align:start position:0% so speed also so and today so yesterday I<02:49:26.560> just<02:49:26.619> published<02:49:27.100> the<02:49:27.249> article<02:49:27.279> that<02:49:27.789> talked 02:49:28.019 --> 02:49:28.029 align:start position:0% I just published the article that talked 02:49:28.029 --> 02:49:29.519 align:start position:0% I just published the article that talked about<02:49:28.060> privacy<02:49:28.659> function<02:49:29.079> and<02:49:29.199> I'm<02:49:29.259> kind<02:49:29.469> of 02:49:29.519 --> 02:49:29.529 align:start position:0% about privacy function and I'm kind of 02:49:29.529 --> 02:49:32.039 align:start position:0% about privacy function and I'm kind of routing<02:49:29.739> such<02:49:30.039> Adam<02:49:30.249> Koch<02:49:30.520> to<02:49:30.819> avail<02:49:31.479> about<02:49:31.749> it 02:49:32.039 --> 02:49:32.049 align:start position:0% routing such Adam Koch to avail about it 02:49:32.049 --> 02:49:36.209 align:start position:0% routing such Adam Koch to avail about it so<02:49:33.039> I<02:49:33.069> big<02:49:33.549> cared<02:49:33.759> about<02:49:33.879> privacy<02:49:34.479> analogy<02:49:35.289> so 02:49:36.209 --> 02:49:36.219 align:start position:0% so I big cared about privacy analogy so 02:49:36.219 --> 02:49:38.309 align:start position:0% so I big cared about privacy analogy so people<02:49:36.699> sometimes<02:49:37.179> confuse<02:49:37.539> about<02:49:37.989> these<02:49:38.139> two 02:49:38.309 --> 02:49:38.319 align:start position:0% people sometimes confuse about these two 02:49:38.319 --> 02:49:40.609 align:start position:0% people sometimes confuse about these two ideas<02:49:38.499> its<02:49:39.069> privacy<02:49:39.489> is<02:49:39.879> something<02:49:40.060> that 02:49:40.609 --> 02:49:40.619 align:start position:0% ideas its privacy is something that 02:49:40.619 --> 02:49:42.989 align:start position:0% ideas its privacy is something that people<02:49:41.619> know<02:49:41.889> where<02:49:42.069> you<02:49:42.189> are<02:49:42.219> but<02:49:42.579> then<02:49:42.789> don't 02:49:42.989 --> 02:49:42.999 align:start position:0% people know where you are but then don't 02:49:42.999 --> 02:49:44.699 align:start position:0% people know where you are but then don't know<02:49:43.089> what<02:49:43.239> to<02:49:43.299> do<02:49:43.479> what<02:49:43.779> they're<02:49:43.869> doing<02:49:43.899> but 02:49:44.699 --> 02:49:44.709 align:start position:0% know what to do what they're doing but 02:49:44.709 --> 02:49:46.349 align:start position:0% know what to do what they're doing but but<02:49:45.369> not<02:49:45.520> know<02:49:45.699> this<02:49:45.759> isn't<02:49:46.029> the<02:49:46.060> other<02:49:46.209> way 02:49:46.349 --> 02:49:46.359 align:start position:0% but not know this isn't the other way 02:49:46.359 --> 02:49:48.269 align:start position:0% but not know this isn't the other way around<02:49:46.419> this<02:49:46.719> it's<02:49:47.259> like<02:49:47.409> people<02:49:47.649> don't<02:49:48.069> know 02:49:48.269 --> 02:49:48.279 align:start position:0% around this it's like people don't know 02:49:48.279 --> 02:49:50.429 align:start position:0% around this it's like people don't know anymore<02:49:48.489> but<02:49:48.969> they<02:49:49.509> know<02:49:49.659> what<02:49:50.020> you're<02:49:50.169> doing 02:49:50.429 --> 02:49:50.439 align:start position:0% anymore but they know what you're doing 02:49:50.439 --> 02:49:54.599 align:start position:0% anymore but they know what you're doing so<02:49:50.619> I<02:49:51.399> mean<02:49:51.879> I<02:49:51.909> don't<02:49:52.270> even<02:49:52.449> see<02:49:52.689> his<02:49:52.899> wad<02:49:53.609> I'm 02:49:54.599 --> 02:49:54.609 align:start position:0% so I mean I don't even see his wad I'm 02:49:54.609 --> 02:49:56.639 align:start position:0% so I mean I don't even see his wad I'm gonna<02:49:55.089> do<02:49:55.270> this<02:49:55.479> one 02:49:56.639 --> 02:49:56.649 align:start position:0% gonna do this one 02:49:56.649 --> 02:50:00.040 align:start position:0% gonna do this one so<02:49:57.649> it's<02:49:58.340> actually<02:49:58.579> has<02:49:59.569> something<02:49:59.749> to<02:49:59.869> do 02:50:00.040 --> 02:50:00.050 align:start position:0% so it's actually has something to do 02:50:00.050 --> 02:50:02.410 align:start position:0% so it's actually has something to do with<02:50:00.199> it<02:50:00.380> being<02:50:00.590> like<02:50:00.800> lime<02:50:01.039> because<02:50:01.420> it's 02:50:02.410 --> 02:50:02.420 align:start position:0% with it being like lime because it's 02:50:02.420 --> 02:50:04.029 align:start position:0% with it being like lime because it's pretty<02:50:02.569> critical<02:50:02.840> to<02:50:03.170> charting<02:50:03.560> right<02:50:03.890> the 02:50:04.029 --> 02:50:04.039 align:start position:0% pretty critical to charting right the 02:50:04.039 --> 02:50:05.529 align:start position:0% pretty critical to charting right the Charlie<02:50:04.399> you<02:50:04.520> don't<02:50:04.640> want<02:50:04.850> any<02:50:05.029> node<02:50:05.270> to<02:50:05.479> store 02:50:05.529 --> 02:50:05.539 align:start position:0% Charlie you don't want any node to store 02:50:05.539 --> 02:50:07.540 align:start position:0% Charlie you don't want any node to store order<02:50:05.930> data<02:50:06.109> so<02:50:06.439> we<02:50:06.619> have<02:50:06.859> to<02:50:07.039> explain<02:50:07.310> to<02:50:07.369> them 02:50:07.540 --> 02:50:07.550 align:start position:0% order data so we have to explain to them 02:50:07.550 --> 02:50:09.460 align:start position:0% order data so we have to explain to them they'll<02:50:07.699> into<02:50:07.999> two<02:50:08.180> ropes<02:50:08.510> one<02:50:09.079> is<02:50:09.199> the<02:50:09.289> Pony 02:50:09.460 --> 02:50:09.470 align:start position:0% they'll into two ropes one is the Pony 02:50:09.470 --> 02:50:12.460 align:start position:0% they'll into two ropes one is the Pony Express<02:50:09.999> process<02:50:10.999> and<02:50:11.149> store<02:50:11.329> data<02:50:11.749> and<02:50:12.380> the 02:50:12.460 --> 02:50:12.470 align:start position:0% Express process and store data and the 02:50:12.470 --> 02:50:15.040 align:start position:0% Express process and store data and the other<02:50:12.499> one<02:50:13.130> is<02:50:13.249> like<02:50:13.399> climb<02:50:13.699> but<02:50:14.239> the<02:50:14.659> problem 02:50:15.040 --> 02:50:15.050 align:start position:0% other one is like climb but the problem 02:50:15.050 --> 02:50:16.870 align:start position:0% other one is like climb but the problem is<02:50:15.140> how<02:50:15.319> can<02:50:15.350> you<02:50:15.649> prove<02:50:15.920> that<02:50:15.979> data<02:50:16.460> is 02:50:16.870 --> 02:50:16.880 align:start position:0% is how can you prove that data is 02:50:16.880 --> 02:50:17.710 align:start position:0% is how can you prove that data is available 02:50:17.710 --> 02:50:17.720 align:start position:0% available 02:50:17.720 --> 02:50:21.309 align:start position:0% available on<02:50:17.869> a<02:50:18.079> cool<02:50:18.289> note<02:50:18.499> right<02:50:18.829> so<02:50:19.220> the<02:50:20.020> so<02:50:21.020> what<02:50:21.229> if 02:50:21.309 --> 02:50:21.319 align:start position:0% on a cool note right so the so what if 02:50:21.319 --> 02:50:25.149 align:start position:0% on a cool note right so the so what if solution<02:50:21.770> is<02:50:21.920> to<02:50:22.100> put<02:50:22.369> the<02:50:22.569> troops<02:50:23.569> and<02:50:24.159> and 02:50:25.149 --> 02:50:25.159 align:start position:0% solution is to put the troops and and 02:50:25.159 --> 02:50:27.040 align:start position:0% solution is to put the troops and and and<02:50:25.489> and<02:50:25.939> the<02:50:26.180> didn't<02:50:26.479> know<02:50:26.630> who's<02:50:26.930> supposed 02:50:27.040 --> 02:50:27.050 align:start position:0% and and the didn't know who's supposed 02:50:27.050 --> 02:50:29.950 align:start position:0% and and the didn't know who's supposed to<02:50:27.380> do<02:50:27.499> that<02:50:27.680> on<02:50:28.069> a<02:50:28.130> smoker<02:50:28.460> track<02:50:28.789> and<02:50:29.149> so<02:50:29.779> that 02:50:29.950 --> 02:50:29.960 align:start position:0% to do that on a smoker track and so that 02:50:29.960 --> 02:50:31.779 align:start position:0% to do that on a smoker track and so that the<02:50:30.170> third<02:50:30.350> party<02:50:30.649> can<02:50:30.859> just<02:50:31.159> access<02:50:31.369> the 02:50:31.779 --> 02:50:31.789 align:start position:0% the third party can just access the 02:50:31.789 --> 02:50:34.149 align:start position:0% the third party can just access the smoke<02:50:32.060> might<02:50:32.180> read<02:50:32.359> ham<02:50:32.590> senators<02:50:33.590> action<02:50:33.949> and 02:50:34.149 --> 02:50:34.159 align:start position:0% smoke might read ham senators action and 02:50:34.159 --> 02:50:37.569 align:start position:0% smoke might read ham senators action and then<02:50:34.720> for<02:50:35.720> attention<02:50:36.020> to<02:50:36.109> data<02:50:36.590> ability<02:50:37.010> right 02:50:37.569 --> 02:50:37.579 align:start position:0% then for attention to data ability right 02:50:37.579 --> 02:50:41.290 align:start position:0% then for attention to data ability right so<02:50:38.890> but<02:50:39.890> but<02:50:40.189> that's<02:50:40.340> a<02:50:40.460> problem<02:50:40.670> so<02:50:41.119> the 02:50:41.290 --> 02:50:41.300 align:start position:0% so but but that's a problem so the 02:50:41.300 --> 02:50:45.849 align:start position:0% so but but that's a problem so the solutions<02:50:41.720> that<02:50:43.749> the<02:50:44.749> problem<02:50:45.050> is<02:50:45.109> that<02:50:45.289> the 02:50:45.849 --> 02:50:45.859 align:start position:0% solutions that the problem is that the 02:50:45.859 --> 02:50:47.889 align:start position:0% solutions that the problem is that the full<02:50:46.100> nail<02:50:46.279> probably<02:50:46.789> can<02:50:46.999> just<02:50:47.180> a<02:50:47.270> sensor<02:50:47.659> the 02:50:47.889 --> 02:50:47.899 align:start position:0% full nail probably can just a sensor the 02:50:47.899 --> 02:50:49.389 align:start position:0% full nail probably can just a sensor the electron<02:50:48.289> so<02:50:48.529> this<02:50:48.680> little<02:50:48.920> solution<02:50:49.279> to<02:50:49.369> that 02:50:49.389 --> 02:50:49.399 align:start position:0% electron so this little solution to that 02:50:49.399 --> 02:50:52.450 align:start position:0% electron so this little solution to that is<02:50:49.760> is<02:50:50.270> to<02:50:50.479> make<02:50:50.630> the<02:50:50.749> client<02:50:51.260> anonymous<02:50:51.920> thank 02:50:52.450 --> 02:50:52.460 align:start position:0% is is to make the client anonymous thank 02:50:52.460 --> 02:50:55.779 align:start position:0% is is to make the client anonymous thank you<02:50:52.609> and<02:50:53.359> so<02:50:53.989> this<02:50:54.800> game<02:50:55.039> is<02:50:55.069> to<02:50:55.340> use<02:50:55.520> the<02:50:55.670> iron 02:50:55.779 --> 02:50:55.789 align:start position:0% you and so this game is to use the iron 02:50:55.789 --> 02:50:58.479 align:start position:0% you and so this game is to use the iron rally<02:50:56.090> so<02:50:57.020> this<02:50:57.409> is<02:50:57.560> how<02:50:57.649> the<02:50:57.710> right<02:50:58.130> user<02:50:58.340> can 02:50:58.479 --> 02:50:58.489 align:start position:0% rally so this is how the right user can 02:50:58.489 --> 02:51:00.929 align:start position:0% rally so this is how the right user can construct<02:50:58.909> so<02:50:59.210> basically<02:50:59.689> you<02:51:00.109> have<02:51:00.590> to 02:51:00.929 --> 02:51:00.939 align:start position:0% construct so basically you have to 02:51:00.939 --> 02:51:05.170 align:start position:0% construct so basically you have to choose<02:51:01.939> the<02:51:01.970> fool<02:51:02.739> the<02:51:03.739> field<02:51:03.949> hops<02:51:04.220> right<02:51:04.550> so 02:51:05.170 --> 02:51:05.180 align:start position:0% choose the fool the field hops right so 02:51:05.180 --> 02:51:08.380 align:start position:0% choose the fool the field hops right so these<02:51:05.359> are<02:51:05.539> basically<02:51:05.899> the<02:51:06.050> EEPROM<02:51:06.499> notes<02:51:07.390> so 02:51:08.380 --> 02:51:08.390 align:start position:0% these are basically the EEPROM notes so 02:51:08.390 --> 02:51:10.809 align:start position:0% these are basically the EEPROM notes so you<02:51:08.449> have<02:51:08.689> to<02:51:08.840> like<02:51:09.050> contract<02:51:09.890> this<02:51:10.039> circuit 02:51:10.809 --> 02:51:10.819 align:start position:0% you have to like contract this circuit 02:51:10.819 --> 02:51:11.500 align:start position:0% you have to like contract this circuit one<02:51:10.970> by<02:51:11.090> one 02:51:11.500 --> 02:51:11.510 align:start position:0% one by one 02:51:11.510 --> 02:51:14.290 align:start position:0% one by one and<02:51:11.859> this<02:51:12.859> what<02:51:13.100> what's<02:51:13.399> specialty<02:51:13.880> here<02:51:14.060> is 02:51:14.290 --> 02:51:14.300 align:start position:0% and this what what's specialty here is 02:51:14.300 --> 02:51:17.710 align:start position:0% and this what what's specialty here is that<02:51:14.479> it's<02:51:14.869> not<02:51:15.020> just<02:51:16.149> these<02:51:17.149> two<02:51:17.359> notes<02:51:17.630> are 02:51:17.710 --> 02:51:17.720 align:start position:0% that it's not just these two notes are 02:51:17.720 --> 02:51:19.719 align:start position:0% that it's not just these two notes are not<02:51:17.869> just<02:51:18.079> in<02:51:18.229> two<02:51:18.439> keys<02:51:18.680> but<02:51:19.279> they're 02:51:19.719 --> 02:51:19.729 align:start position:0% not just in two keys but they're 02:51:19.729 --> 02:51:21.460 align:start position:0% not just in two keys but they're actually<02:51:19.970> using<02:51:20.420> some<02:51:20.600> three<02:51:21.050> or<02:51:21.109> five<02:51:21.350> of 02:51:21.460 --> 02:51:21.470 align:start position:0% actually using some three or five of 02:51:21.470 --> 02:51:23.649 align:start position:0% actually using some three or five of rhythm<02:51:21.739> functions<02:51:22.130> to<02:51:22.609> generate<02:51:23.329> it<02:51:23.510> written 02:51:23.649 --> 02:51:23.659 align:start position:0% rhythm functions to generate it written 02:51:23.659 --> 02:51:26.590 align:start position:0% rhythm functions to generate it written over<02:51:23.810> here<02:51:23.930> and<02:51:24.680> then<02:51:24.829> so<02:51:25.279> they're<02:51:26.239> not<02:51:26.420> really 02:51:26.590 --> 02:51:26.600 align:start position:0% over here and then so they're not really 02:51:26.600 --> 02:51:28.750 align:start position:0% over here and then so they're not really operate<02:51:27.079> so<02:51:27.499> that<02:51:27.529> the<02:51:28.159> bread<02:51:28.369> number<02:51:28.640> is 02:51:28.750 --> 02:51:28.760 align:start position:0% operate so that the bread number is 02:51:28.760 --> 02:51:31.479 align:start position:0% operate so that the bread number is unpredictable<02:51:29.180> to<02:51:29.600> the<02:51:29.689> next<02:51:29.930> relay<02:51:30.199> so<02:51:30.680> they 02:51:31.479 --> 02:51:31.489 align:start position:0% unpredictable to the next relay so they 02:51:31.489 --> 02:51:33.849 align:start position:0% unpredictable to the next relay so they each<02:51:31.850> gain<02:51:32.090> over<02:51:32.239> 800<02:51:32.749> number<02:51:33.020> at<02:51:33.380> a<02:51:33.560> time 02:51:33.849 --> 02:51:33.859 align:start position:0% each gain over 800 number at a time 02:51:33.859 --> 02:51:36.399 align:start position:0% each gain over 800 number at a time and<02:51:34.039> finally<02:51:34.460> Bureau<02:51:34.640> circuit<02:51:35.029> so<02:51:35.630> that<02:51:36.079> is<02:51:36.260> it 02:51:36.399 --> 02:51:36.409 align:start position:0% and finally Bureau circuit so that is it 02:51:36.409 --> 02:51:39.099 align:start position:0% and finally Bureau circuit so that is it no<02:51:36.560> it's<02:51:36.829> actually<02:51:36.979> it's<02:51:37.310> anonymous<02:51:37.520> to<02:51:38.109> basic 02:51:39.099 --> 02:51:39.109 align:start position:0% no it's actually it's anonymous to basic 02:51:39.109 --> 02:51:41.590 align:start position:0% no it's actually it's anonymous to basic to<02:51:39.229> anyone<02:51:39.590> right<02:51:40.039> so<02:51:40.520> this<02:51:40.909> is<02:51:40.970> for<02:51:41.210> nope<02:51:41.390> so 02:51:41.590 --> 02:51:41.600 align:start position:0% to anyone right so this is for nope so 02:51:41.600 --> 02:51:43.840 align:start position:0% to anyone right so this is for nope so the<02:51:42.050> opponent<02:51:42.350> doesn't<02:51:42.470> know<02:51:42.680> who<02:51:43.130> is<02:51:43.579> their 02:51:43.840 --> 02:51:43.850 align:start position:0% the opponent doesn't know who is their 02:51:43.850 --> 02:51:46.239 align:start position:0% the opponent doesn't know who is their true<02:51:44.180> unlike<02:51:45.020> like<02:51:45.199> yours<02:51:45.439> so<02:51:45.739> that<02:51:46.100> basically 02:51:46.239 --> 02:51:46.249 align:start position:0% true unlike like yours so that basically 02:51:46.249 --> 02:51:48.790 align:start position:0% true unlike like yours so that basically protect<02:51:46.819> this<02:51:47.390> is<02:51:47.539> our<02:51:47.659> ship<02:51:47.810> attack<02:51:48.050> right 02:51:48.790 --> 02:51:48.800 align:start position:0% protect this is our ship attack right 02:51:48.800 --> 02:51:49.330 align:start position:0% protect this is our ship attack right that's<02:51:49.039> it 02:51:49.330 --> 02:51:49.340 align:start position:0% that's it 02:51:49.340 --> 02:51:53.399 align:start position:0% that's it so<02:51:49.489> I<02:51:49.520> hope<02:51:50.079> this<02:51:51.079> really<02:51:51.380> pretty<02:51:51.939> quick 02:51:53.399 --> 02:51:53.409 align:start position:0% so I hope this really pretty quick 02:51:53.409 --> 02:51:54.960 align:start position:0% so I hope this really pretty quick introduction 02:51:54.960 --> 02:51:54.970 align:start position:0% introduction 02:51:54.970 --> 02:51:57.660 align:start position:0% introduction and<02:51:55.090> happy<02:51:55.569> to<02:51:55.720> dig<02:51:56.260> more<02:51:56.410> into<02:51:56.529> this<02:51:57.279> concept 02:51:57.660 --> 02:51:57.670 align:start position:0% and happy to dig more into this concept 02:51:57.670 --> 02:52:06.360 align:start position:0% and happy to dig more into this concept thank<02:51:57.819> you<02:52:03.270> hi<02:52:04.270> I'm<02:52:04.720> Alex<02:52:05.170> Brown<02:52:05.439> and<02:52:05.920> I<02:52:06.189> work 02:52:06.360 --> 02:52:06.370 align:start position:0% thank you hi I'm Alex Brown and I work 02:52:06.370 --> 02:52:09.090 align:start position:0% thank you hi I'm Alex Brown and I work in<02:52:06.580> the<02:52:06.729> CRX<02:52:07.149> I'm<02:52:07.989> here<02:52:08.319> to<02:52:08.500> talk<02:52:08.649> about<02:52:08.890> how<02:52:09.040> we 02:52:09.090 --> 02:52:09.100 align:start position:0% in the CRX I'm here to talk about how we 02:52:09.100 --> 02:52:12.450 align:start position:0% in the CRX I'm here to talk about how we used<02:52:09.430> the<02:52:09.729> tippy<02:52:10.149> and<02:52:10.180> webassembly<02:52:11.170> to<02:52:11.770> enable 02:52:12.450 --> 02:52:12.460 align:start position:0% used the tippy and webassembly to enable 02:52:12.460 --> 02:52:17.219 align:start position:0% used the tippy and webassembly to enable peer-to-peer<02:52:12.819> training<02:52:13.330> in<02:52:13.750> the<02:52:13.810> browser<02:52:16.229> 0x 02:52:17.219 --> 02:52:17.229 align:start position:0% peer-to-peer training in the browser 0x 02:52:17.229 --> 02:52:19.469 align:start position:0% peer-to-peer training in the browser 0x is<02:52:17.500> a<02:52:17.560> protocol<02:52:18.399> for<02:52:18.460> a<02:52:18.790> decentralized 02:52:19.469 --> 02:52:19.479 align:start position:0% is a protocol for a decentralized 02:52:19.479 --> 02:52:22.139 align:start position:0% is a protocol for a decentralized exchange<02:52:19.630> that<02:52:20.260> anybody<02:52:20.770> can<02:52:20.890> use<02:52:21.100> to<02:52:21.640> trade 02:52:22.139 --> 02:52:22.149 align:start position:0% exchange that anybody can use to trade 02:52:22.149 --> 02:52:25.170 align:start position:0% exchange that anybody can use to trade digital<02:52:22.569> assets<02:52:23.020> including<02:52:23.830> a<02:52:23.859> or<02:52:24.160> C<02:52:24.340> 20<02:52:24.670> or<02:52:24.970> C 02:52:25.170 --> 02:52:25.180 align:start position:0% digital assets including a or C 20 or C 02:52:25.180 --> 02:52:27.960 align:start position:0% digital assets including a or C 20 or C 721<02:52:25.950> your<02:52:26.950> transitional<02:52:27.399> assets<02:52:27.790> with 02:52:27.960 --> 02:52:27.970 align:start position:0% 721 your transitional assets with 02:52:27.970 --> 02:52:33.349 align:start position:0% 721 your transitional assets with anybody<02:52:28.359> in<02:52:28.479> the<02:52:28.510> world<02:52:29.040> to<02:52:30.040> trust<02:52:30.310> this<02:52:30.399> way 02:52:33.349 --> 02:52:33.359 align:start position:0% 02:52:33.359 --> 02:52:37.200 align:start position:0% 0x<02:52:34.359> protocol<02:52:34.930> features<02:52:35.470> an<02:52:36.340> off<02:52:36.520> chain<02:52:36.819> relay 02:52:37.200 --> 02:52:37.210 align:start position:0% 0x protocol features an off chain relay 02:52:37.210 --> 02:52:39.719 align:start position:0% 0x protocol features an off chain relay and<02:52:37.510> on<02:52:37.689> chain<02:52:37.989> settlement<02:52:38.529> so<02:52:39.340> what<02:52:39.609> that 02:52:39.719 --> 02:52:39.729 align:start position:0% and on chain settlement so what that 02:52:39.729 --> 02:52:42.450 align:start position:0% and on chain settlement so what that means<02:52:39.939> is<02:52:40.090> that<02:52:40.120> you<02:52:40.330> share<02:52:40.660> orders<02:52:41.310> offers<02:52:42.310> to 02:52:42.450 --> 02:52:42.460 align:start position:0% means is that you share orders offers to 02:52:42.460 --> 02:52:43.530 align:start position:0% means is that you share orders offers to buy<02:52:42.609> or<02:52:42.670> sell<02:52:42.970> samatha 02:52:43.530 --> 02:52:43.540 align:start position:0% buy or sell samatha 02:52:43.540 --> 02:52:46.349 align:start position:0% buy or sell samatha with<02:52:44.350> people<02:52:44.830> and<02:52:45.340> have<02:52:45.460> an<02:52:45.580> off<02:52:45.760> chain<02:52:46.060> and 02:52:46.349 --> 02:52:46.359 align:start position:0% with people and have an off chain and 02:52:46.359 --> 02:52:48.479 align:start position:0% with people and have an off chain and then<02:52:47.260> when<02:52:47.439> it<02:52:47.529> comes<02:52:47.620> time<02:52:47.800> to<02:52:47.950> settle<02:52:48.340> the 02:52:48.479 --> 02:52:48.489 align:start position:0% then when it comes time to settle the 02:52:48.489 --> 02:52:50.040 align:start position:0% then when it comes time to settle the orders<02:52:48.760> you<02:52:48.850> go<02:52:49.029> on<02:52:49.270> chain<02:52:49.569> and<02:52:49.750> use<02:52:49.840> smart 02:52:50.040 --> 02:52:50.050 align:start position:0% orders you go on chain and use smart 02:52:50.050 --> 02:52:52.020 align:start position:0% orders you go on chain and use smart contracts<02:52:50.590> to<02:52:50.680> do<02:52:50.800> entrusted<02:52:51.220> sub 02:52:52.020 --> 02:52:52.030 align:start position:0% contracts to do entrusted sub 02:52:52.030 --> 02:52:54.511 align:start position:0% contracts to do entrusted sub [Music] 02:52:54.511 --> 02:52:54.521 align:start position:0% [Music] 02:52:54.521 --> 02:52:58.140 align:start position:0% [Music] Xerox<02:52:55.210> mesh<02:52:55.721> is<02:52:56.110> a<02:52:56.200> way<02:52:56.561> to<02:52:56.620> exchange<02:52:57.400> orders 02:52:58.140 --> 02:52:58.150 align:start position:0% Xerox mesh is a way to exchange orders 02:52:58.150 --> 02:53:00.690 align:start position:0% Xerox mesh is a way to exchange orders and<02:52:58.480> it<02:52:58.870> totally<02:52:59.320> decentralized<02:53:00.221> appear<02:53:00.610> to 02:53:00.690 --> 02:53:00.700 align:start position:0% and it totally decentralized appear to 02:53:00.700 --> 02:53:02.970 align:start position:0% and it totally decentralized appear to appear<02:53:00.851> fashion<02:53:01.271> it<02:53:02.170> allows<02:53:02.410> users<02:53:02.830> to<02:53:02.860> share 02:53:02.970 --> 02:53:02.980 align:start position:0% appear fashion it allows users to share 02:53:02.980 --> 02:53:04.620 align:start position:0% appear fashion it allows users to share what<02:53:03.431> air<02:53:03.550> is<02:53:03.641> directly<02:53:04.061> with<02:53:04.300> each<02:53:04.420> other 02:53:04.620 --> 02:53:04.630 align:start position:0% what air is directly with each other 02:53:04.630 --> 02:53:07.711 align:start position:0% what air is directly with each other using<02:53:04.931> computer<02:53:05.471> network<02:53:05.800> as<02:53:06.521> opposed<02:53:06.910> to<02:53:07.090> the 02:53:07.711 --> 02:53:07.721 align:start position:0% using computer network as opposed to the 02:53:07.721 --> 02:53:09.211 align:start position:0% using computer network as opposed to the alternatives<02:53:08.260> day<02:53:08.440> which<02:53:08.650> is<02:53:08.771> using<02:53:09.070> a 02:53:09.211 --> 02:53:09.221 align:start position:0% alternatives day which is using a 02:53:09.221 --> 02:53:11.640 align:start position:0% alternatives day which is using a centralized<02:53:09.760> service<02:53:09.971> to<02:53:10.480> collect<02:53:11.290> orders 02:53:11.640 --> 02:53:11.650 align:start position:0% centralized service to collect orders 02:53:11.650 --> 02:53:18.030 align:start position:0% centralized service to collect orders and<02:53:11.920> I<02:53:12.101> create<02:53:12.340> a<02:53:12.370> field<02:53:16.500> Xerox<02:53:17.500> masters<02:53:17.860> grid 02:53:18.030 --> 02:53:18.040 align:start position:0% and I create a field Xerox masters grid 02:53:18.040 --> 02:53:20.870 align:start position:0% and I create a field Xerox masters grid didn't<02:53:18.280> go<02:53:18.400> and<02:53:19.181> we<02:53:19.420> decided<02:53:19.840> to<02:53:19.960> use 02:53:20.870 --> 02:53:20.880 align:start position:0% didn't go and we decided to use 02:53:20.880 --> 02:53:23.430 align:start position:0% didn't go and we decided to use webassembly<02:53:21.880> which<02:53:22.271> allows<02:53:22.540> us<02:53:22.750> to<02:53:22.780> have<02:53:22.931> an 02:53:23.430 --> 02:53:23.440 align:start position:0% webassembly which allows us to have an 02:53:23.440 --> 02:53:25.110 align:start position:0% webassembly which allows us to have an isomorphic<02:53:24.040> average<02:53:24.610> intern<02:53:24.851> in<02:53:24.971> one 02:53:25.110 --> 02:53:25.120 align:start position:0% isomorphic average intern in one 02:53:25.120 --> 02:53:27.990 align:start position:0% isomorphic average intern in one language<02:53:25.380> we<02:53:26.380> can<02:53:26.530> compile<02:53:26.891> 0x<02:53:27.340> mesh<02:53:27.580> to<02:53:27.790> run 02:53:27.990 --> 02:53:28.000 align:start position:0% language we can compile 0x mesh to run 02:53:28.000 --> 02:53:30.720 align:start position:0% language we can compile 0x mesh to run in<02:53:28.210> the<02:53:28.330> browser<02:53:28.510> or<02:53:29.200> sera<02:53:29.650> as<02:53:30.070> a<02:53:30.340> standalone 02:53:30.720 --> 02:53:30.730 align:start position:0% in the browser or sera as a standalone 02:53:30.730 --> 02:53:34.620 align:start position:0% in the browser or sera as a standalone node<02:53:31.090> or<02:53:32.021> annika<02:53:32.320> back<02:53:32.590> insert<02:53:33.300> other<02:53:34.300> couple 02:53:34.620 --> 02:53:34.630 align:start position:0% node or annika back insert other couple 02:53:34.630 --> 02:53:36.421 align:start position:0% node or annika back insert other couple reasons<02:53:34.750> for<02:53:34.990> this<02:53:35.110> we<02:53:35.410> think<02:53:35.530> they<02:53:35.710> go<02:53:35.980> the<02:53:36.101> PP 02:53:36.421 --> 02:53:36.431 align:start position:0% reasons for this we think they go the PP 02:53:36.431 --> 02:53:38.370 align:start position:0% reasons for this we think they go the PP is<02:53:36.580> the<02:53:36.940> original<02:53:37.540> implementation<02:53:37.660> would<02:53:38.260> be 02:53:38.370 --> 02:53:38.380 align:start position:0% is the original implementation would be 02:53:38.380 --> 02:53:40.500 align:start position:0% is the original implementation would be to<02:53:38.471> be<02:53:38.590> as<02:53:38.800> a<02:53:38.830> lot<02:53:39.010> more<02:53:39.130> active<02:53:39.460> also<02:53:40.181> some 02:53:40.500 --> 02:53:40.510 align:start position:0% to be as a lot more active also some 02:53:40.510 --> 02:53:42.091 align:start position:0% to be as a lot more active also some smaller<02:53:40.811> factors<02:53:41.290> are<02:53:41.440> more<02:53:41.590> familiar<02:53:41.740> with 02:53:42.091 --> 02:53:42.101 align:start position:0% smaller factors are more familiar with 02:53:42.101 --> 02:53:44.211 align:start position:0% smaller factors are more familiar with language<02:53:42.851> get<02:53:43.660> better<02:53:43.840> performance 02:53:44.211 --> 02:53:44.221 align:start position:0% language get better performance 02:53:44.221 --> 02:53:46.320 align:start position:0% language get better performance characteristics<02:53:45.221> or<02:53:45.700> a<02:53:45.760> million<02:53:46.181> better 02:53:46.320 --> 02:53:46.330 align:start position:0% characteristics or a million better 02:53:46.330 --> 02:53:51.360 align:start position:0% characteristics or a million better tools<02:53:49.080> the<02:53:50.080> cool<02:53:50.260> thing<02:53:50.410> is<02:53:50.471> that<02:53:50.650> most<02:53:50.830> Lipke 02:53:51.360 --> 02:53:51.370 align:start position:0% tools the cool thing is that most Lipke 02:53:51.370 --> 02:53:53.700 align:start position:0% tools the cool thing is that most Lipke to<02:53:51.460> be<02:53:51.580> components<02:53:52.210> were<02:53:52.960> crowned<02:53:53.351> on<02:53:53.440> the<02:53:53.500> box 02:53:53.700 --> 02:53:53.710 align:start position:0% to be components were crowned on the box 02:53:53.710 --> 02:53:55.410 align:start position:0% to be components were crowned on the box everything<02:53:54.400> that<02:53:54.580> wasn't<02:53:54.730> here<02:53:55.000> from<02:53:55.210> piles 02:53:55.410 --> 02:53:55.420 align:start position:0% everything that wasn't here from piles 02:53:55.420 --> 02:53:57.240 align:start position:0% everything that wasn't here from piles to<02:53:55.601> webassembly<02:53:55.960> works<02:53:56.891> in<02:53:57.040> the<02:53:57.101> browser 02:53:57.240 --> 02:53:57.250 align:start position:0% to webassembly works in the browser 02:53:57.250 --> 02:53:58.801 align:start position:0% to webassembly works in the browser right<02:53:57.670> away<02:53:57.940> without<02:53:58.120> any<02:53:58.480> additional 02:53:58.801 --> 02:53:58.811 align:start position:0% right away without any additional 02:53:58.811 --> 02:54:00.961 align:start position:0% right away without any additional changes<02:53:59.070> within<02:54:00.070> within<02:54:00.280> th<02:54:00.460> to<02:54:00.670> you<02:54:00.760> for 02:54:00.961 --> 02:54:00.971 align:start position:0% changes within within th to you for 02:54:00.971 --> 02:54:03.540 align:start position:0% changes within within th to you for discovery<02:54:01.540> things<02:54:02.230> like<02:54:02.380> Auto<02:54:02.561> dadada<02:54:03.160> relay 02:54:03.540 --> 02:54:03.550 align:start position:0% discovery things like Auto dadada relay 02:54:03.550 --> 02:54:06.650 align:start position:0% discovery things like Auto dadada relay and<02:54:03.910> gossips<02:54:04.630> a<02:54:04.750> number<02:54:05.260> of<02:54:05.320> other<02:54:05.440> things 02:54:06.650 --> 02:54:06.660 align:start position:0% and gossips a number of other things 02:54:06.660 --> 02:54:09.240 align:start position:0% and gossips a number of other things there<02:54:07.660> really<02:54:07.780> only<02:54:07.931> two<02:54:08.320> components<02:54:08.980> that<02:54:09.010> we 02:54:09.240 --> 02:54:09.250 align:start position:0% there really only two components that we 02:54:09.250 --> 02:54:11.729 align:start position:0% there really only two components that we needed<02:54:09.431> to<02:54:09.550> make<02:54:10.061> modifications<02:54:10.360> for<02:54:10.931> door 02:54:11.729 --> 02:54:11.739 align:start position:0% needed to make modifications for door 02:54:11.739 --> 02:54:14.010 align:start position:0% needed to make modifications for door Houser<02:54:12.189> the<02:54:12.909> first<02:54:13.149> of<02:54:13.299> the<02:54:13.390> transport<02:54:13.989> layer 02:54:14.010 --> 02:54:14.020 align:start position:0% Houser the first of the transport layer 02:54:14.020 --> 02:54:17.760 align:start position:0% Houser the first of the transport layer so<02:54:14.529> let<02:54:14.739> me<02:54:14.829> -<02:54:14.919> Pia<02:54:15.069> Transport<02:54:15.729> is<02:54:16.770> networking 02:54:17.760 --> 02:54:17.770 align:start position:0% so let me - Pia Transport is networking 02:54:17.770 --> 02:54:19.710 align:start position:0% so let me - Pia Transport is networking TCP<02:54:18.310> or<02:54:18.489> WebSockets<02:54:19.149> that<02:54:19.359> allows<02:54:19.509> you<02:54:19.689> to 02:54:19.710 --> 02:54:19.720 align:start position:0% TCP or WebSockets that allows you to 02:54:19.720 --> 02:54:21.989 align:start position:0% TCP or WebSockets that allows you to send<02:54:19.959> messages<02:54:20.020> with<02:54:20.499> their<02:54:20.619> peers<02:54:20.879> so<02:54:21.879> what 02:54:21.989 --> 02:54:21.999 align:start position:0% send messages with their peers so what 02:54:21.999 --> 02:54:23.249 align:start position:0% send messages with their peers so what we've<02:54:22.089> done<02:54:22.239> is<02:54:22.299> we<02:54:22.539> wrote<02:54:22.749> webassembly 02:54:23.249 --> 02:54:23.259 align:start position:0% we've done is we wrote webassembly 02:54:23.259 --> 02:54:25.409 align:start position:0% we've done is we wrote webassembly bindings<02:54:23.890> for<02:54:24.189> the<02:54:24.399> WebSocket<02:54:24.850> transport<02:54:25.299> and 02:54:25.409 --> 02:54:25.419 align:start position:0% bindings for the WebSocket transport and 02:54:25.419 --> 02:54:27.779 align:start position:0% bindings for the WebSocket transport and the<02:54:25.479> p2p<02:54:25.770> that's<02:54:26.770> already<02:54:26.919> done<02:54:27.129> there's<02:54:27.459> a<02:54:27.520> PR 02:54:27.779 --> 02:54:27.789 align:start position:0% the p2p that's already done there's a PR 02:54:27.789 --> 02:54:29.880 align:start position:0% the p2p that's already done there's a PR the<02:54:28.449> dopin<02:54:28.749> we're<02:54:28.930> going<02:54:29.319> to<02:54:29.409> be<02:54:29.470> marriage<02:54:29.739> off 02:54:29.880 --> 02:54:29.890 align:start position:0% the dopin we're going to be marriage off 02:54:29.890 --> 02:54:31.170 align:start position:0% the dopin we're going to be marriage off street<02:54:30.129> but<02:54:30.249> we're<02:54:30.369> already<02:54:30.520> using<02:54:30.879> it<02:54:30.970> in<02:54:31.089> our 02:54:31.170 --> 02:54:31.180 align:start position:0% street but we're already using it in our 02:54:31.180 --> 02:54:34.889 align:start position:0% street but we're already using it in our own<02:54:31.209> applications<02:54:33.359> we're<02:54:34.359> also<02:54:34.449> working<02:54:34.689> on 02:54:34.889 --> 02:54:34.899 align:start position:0% own applications we're also working on 02:54:34.899 --> 02:54:37.409 align:start position:0% own applications we're also working on adding<02:54:35.169> support<02:54:35.470> for<02:54:35.709> web<02:54:36.039> RTC<02:54:36.339> transport<02:54:37.149> so 02:54:37.409 --> 02:54:37.419 align:start position:0% adding support for web RTC transport so 02:54:37.419 --> 02:54:39.599 align:start position:0% adding support for web RTC transport so whoever<02:54:37.629> TC<02:54:38.049> can<02:54:38.289> enable<02:54:38.680> -<02:54:38.919> browser-based 02:54:39.599 --> 02:54:39.609 align:start position:0% whoever TC can enable - browser-based 02:54:39.609 --> 02:54:41.249 align:start position:0% whoever TC can enable - browser-based appears<02:54:40.089> to<02:54:40.390> redial<02:54:40.689> each<02:54:40.899> other<02:54:41.079> directly 02:54:41.249 --> 02:54:41.259 align:start position:0% appears to redial each other directly 02:54:41.259 --> 02:54:47.550 align:start position:0% appears to redial each other directly without<02:54:42.249> relying<02:54:42.850> on<02:54:43.089> everything<02:54:43.989> out<02:54:46.560> the 02:54:47.550 --> 02:54:47.560 align:start position:0% without relying on everything out the 02:54:47.560 --> 02:54:48.630 align:start position:0% without relying on everything out the other<02:54:47.680> major<02:54:47.949> component<02:54:48.039> that<02:54:48.369> we<02:54:48.459> had<02:54:48.579> to 02:54:48.630 --> 02:54:48.640 align:start position:0% other major component that we had to 02:54:48.640 --> 02:54:51.179 align:start position:0% other major component that we had to replace<02:54:48.850> is<02:54:49.270> the<02:54:49.779> storage<02:54:50.169> layer<02:54:50.350> so<02:54:51.069> what 02:54:51.179 --> 02:54:51.189 align:start position:0% replace is the storage layer so what 02:54:51.189 --> 02:54:52.949 align:start position:0% replace is the storage layer so what we're<02:54:51.310> doing<02:54:51.339> is<02:54:51.819> we're<02:54:52.060> using<02:54:52.209> level<02:54:52.689> Eenie 02:54:52.949 --> 02:54:52.959 align:start position:0% we're doing is we're using level Eenie 02:54:52.959 --> 02:54:56.189 align:start position:0% we're doing is we're using level Eenie we<02:54:53.829> added<02:54:54.249> webassembly<02:54:55.089> bindings<02:54:55.659> for<02:54:55.869> level 02:54:56.189 --> 02:54:56.199 align:start position:0% we added webassembly bindings for level 02:54:56.199 --> 02:54:58.499 align:start position:0% we added webassembly bindings for level gb<02:54:56.409> just<02:54:57.129> replacing<02:54:57.640> these<02:54:57.819> underlying 02:54:58.499 --> 02:54:58.509 align:start position:0% gb just replacing these underlying 02:54:58.509 --> 02:55:00.960 align:start position:0% gb just replacing these underlying storage<02:54:58.959> component<02:54:59.579> laughter<02:55:00.579> we<02:55:00.669> did<02:55:00.819> that 02:55:00.960 --> 02:55:00.970 align:start position:0% storage component laughter we did that 02:55:00.970 --> 02:55:02.519 align:start position:0% storage component laughter we did that everything<02:55:01.329> worked<02:55:01.479> pretty<02:55:01.629> well<02:55:01.869> the<02:55:02.229> pdb 02:55:02.519 --> 02:55:02.529 align:start position:0% everything worked pretty well the pdb 02:55:02.529 --> 02:55:04.619 align:start position:0% everything worked pretty well the pdb already<02:55:02.739> has<02:55:02.890> support<02:55:03.279> for<02:55:03.430> using<02:55:03.759> level<02:55:04.539> 2b 02:55:04.619 --> 02:55:04.629 align:start position:0% already has support for using level 2b 02:55:04.629 --> 02:55:07.170 align:start position:0% already has support for using level 2b as<02:55:04.989> in<02:55:05.319> the<02:55:05.409> datastore<02:55:05.789> so<02:55:06.789> we<02:55:06.879> just<02:55:06.999> had<02:55:07.119> to 02:55:07.170 --> 02:55:07.180 align:start position:0% as in the datastore so we just had to 02:55:07.180 --> 02:55:08.789 align:start position:0% as in the datastore so we just had to put<02:55:07.299> the<02:55:07.359> pieces<02:55:07.509> together<02:55:07.689> we<02:55:08.529> were<02:55:08.619> on<02:55:08.709> the 02:55:08.789 --> 02:55:08.799 align:start position:0% put the pieces together we were on the 02:55:08.799 --> 02:55:09.960 align:start position:0% put the pieces together we were on the browser<02:55:09.009> we<02:55:09.220> use<02:55:09.339> something<02:55:09.489> called<02:55:09.579> browser 02:55:09.960 --> 02:55:09.970 align:start position:0% browser we use something called browser 02:55:09.970 --> 02:55:12.989 align:start position:0% browser we use something called browser FS<02:55:10.419> on<02:55:11.109> top<02:55:11.289> of<02:55:11.439> local<02:55:11.649> storage<02:55:11.890> to<02:55:12.009> shim<02:55:12.459> have 02:55:12.989 --> 02:55:12.999 align:start position:0% FS on top of local storage to shim have 02:55:12.999 --> 02:55:18.179 align:start position:0% FS on top of local storage to shim have a<02:55:13.029> file<02:55:13.329> system<02:55:16.109> so<02:55:17.109> all<02:55:17.259> the<02:55:17.379> Spoils<02:55:17.709> down<02:55:17.890> to 02:55:18.179 --> 02:55:18.189 align:start position:0% a file system so all the Spoils down to 02:55:18.189 --> 02:55:21.329 align:start position:0% a file system so all the Spoils down to single<02:55:19.089> time<02:55:19.779> script<02:55:20.049> or<02:55:20.140> JavaScript<02:55:20.619> library 02:55:21.329 --> 02:55:21.339 align:start position:0% single time script or JavaScript library 02:55:21.339 --> 02:55:24.239 align:start position:0% single time script or JavaScript library on<02:55:21.640> NPM<02:55:21.970> that<02:55:22.749> users<02:55:23.229> can<02:55:23.379> download<02:55:23.499> to<02:55:24.009> build 02:55:24.239 --> 02:55:24.249 align:start position:0% on NPM that users can download to build 02:55:24.249 --> 02:55:27.090 align:start position:0% on NPM that users can download to build applications<02:55:24.999> on<02:55:25.419> top<02:55:25.629> of<02:55:25.749> mesh<02:55:25.959> it's<02:55:26.829> super 02:55:27.090 --> 02:55:27.100 align:start position:0% applications on top of mesh it's super 02:55:27.100 --> 02:55:28.529 align:start position:0% applications on top of mesh it's super easy<02:55:27.279> it<02:55:27.549> feels<02:55:27.789> like<02:55:27.970> you're<02:55:28.119> using<02:55:28.149> any 02:55:28.529 --> 02:55:28.539 align:start position:0% easy it feels like you're using any 02:55:28.539 --> 02:55:32.249 align:start position:0% easy it feels like you're using any other<02:55:28.629> JavaScript<02:55:29.439> or<02:55:29.560> typescript<02:55:29.919> lender<02:55:31.259> ok 02:55:32.249 --> 02:55:32.259 align:start position:0% other JavaScript or typescript lender ok 02:55:32.259 --> 02:55:33.569 align:start position:0% other JavaScript or typescript lender ok hopefully<02:55:32.560> if<02:55:32.799> we<02:55:32.890> have<02:55:32.979> time<02:55:33.189> I'm<02:55:33.399> going<02:55:33.520> to 02:55:33.569 --> 02:55:33.579 align:start position:0% hopefully if we have time I'm going to 02:55:33.579 --> 02:55:34.051 align:start position:0% hopefully if we have time I'm going to do<02:55:33.699> it 02:55:34.051 --> 02:55:34.061 align:start position:0% do it 02:55:34.061 --> 02:55:37.140 align:start position:0% do it quick<02:55:34.210> demo<02:55:35.250> my<02:55:36.250> minutes<02:55:36.641> left 02:55:37.140 --> 02:55:37.150 align:start position:0% quick demo my minutes left 02:55:37.150 --> 02:55:40.140 align:start position:0% quick demo my minutes left cool<02:55:37.540> so<02:55:38.320> I<02:55:38.650> have<02:55:39.070> to<02:55:39.280> give<02:55:39.790> a<02:55:39.820> disclaimer 02:55:40.140 --> 02:55:40.150 align:start position:0% cool so I have to give a disclaimer 02:55:40.150 --> 02:55:42.870 align:start position:0% cool so I have to give a disclaimer which<02:55:40.570> is<02:55:40.690> that<02:55:41.521> United<02:55:42.521> here<02:55:42.641> is<02:55:42.700> really 02:55:42.870 --> 02:55:42.880 align:start position:0% which is that United here is really 02:55:42.880 --> 02:55:44.341 align:start position:0% which is that United here is really wonky<02:55:43.120> I'm<02:55:43.480> currently<02:55:43.721> going<02:55:43.900> through<02:55:44.230> my 02:55:44.341 --> 02:55:44.351 align:start position:0% wonky I'm currently going through my 02:55:44.351 --> 02:55:46.200 align:start position:0% wonky I'm currently going through my phone<02:55:44.561> a<02:55:44.590> hotspot<02:55:45.400> connection<02:55:45.820> but<02:55:45.940> hopefully 02:55:46.200 --> 02:55:46.210 align:start position:0% phone a hotspot connection but hopefully 02:55:46.210 --> 02:55:48.690 align:start position:0% phone a hotspot connection but hopefully it'll<02:55:46.330> work<02:55:46.710> right<02:55:47.710> now<02:55:47.830> my<02:55:48.011> browser<02:55:48.340> is 02:55:48.690 --> 02:55:48.700 align:start position:0% it'll work right now my browser is 02:55:48.700 --> 02:55:52.830 align:start position:0% it'll work right now my browser is running<02:55:48.730> -<02:55:49.530> it's<02:55:50.530> running<02:55:51.340> webassembly<02:55:51.910> we're 02:55:52.830 --> 02:55:52.840 align:start position:0% running - it's running webassembly we're 02:55:52.840 --> 02:55:54.930 align:start position:0% running - it's running webassembly we're hopefully<02:55:53.290> connecting<02:55:53.800> to<02:55:53.920> the<02:55:54.011> DHT<02:55:54.250> and 02:55:54.930 --> 02:55:54.940 align:start position:0% hopefully connecting to the DHT and 02:55:54.940 --> 02:55:57.270 align:start position:0% hopefully connecting to the DHT and finding<02:55:55.391> peers<02:55:55.601> to<02:55:55.750> connect<02:55:56.021> to<02:55:56.170> and<02:55:56.561> that 02:55:57.270 --> 02:55:57.280 align:start position:0% finding peers to connect to and that 02:55:57.280 --> 02:55:59.120 align:start position:0% finding peers to connect to and that process<02:55:57.460> go<02:55:57.880> smoothly<02:55:58.210> we'll<02:55:58.540> start<02:55:58.780> to<02:55:58.931> see 02:55:59.120 --> 02:55:59.130 align:start position:0% process go smoothly we'll start to see 02:55:59.130 --> 02:56:02.011 align:start position:0% process go smoothly we'll start to see Xerox<02:56:00.130> orders<02:56:00.521> coming<02:56:00.820> in<02:56:01.000> there's<02:56:01.660> a<02:56:01.750> lot 02:56:02.011 --> 02:56:02.021 align:start position:0% Xerox orders coming in there's a lot 02:56:02.021 --> 02:56:09.450 align:start position:0% Xerox orders coming in there's a lot about<02:56:06.420> yeah<02:56:07.530> I'm<02:56:08.530> using<02:56:08.771> my<02:56:09.011> house<02:56:09.221> but 02:56:09.450 --> 02:56:09.460 align:start position:0% about yeah I'm using my house but 02:56:09.460 --> 02:56:11.910 align:start position:0% about yeah I'm using my house but hopefully<02:56:10.000> we're<02:56:10.870> really<02:56:11.141> really<02:56:11.440> out<02:56:11.710> with 02:56:11.910 --> 02:56:11.920 align:start position:0% hopefully we're really really out with 02:56:11.920 --> 02:56:15.570 align:start position:0% hopefully we're really really out with our<02:56:12.160> Butler<02:56:12.880> graduates<02:56:13.181> teaser<02:56:14.580> when 02:56:15.570 --> 02:56:15.580 align:start position:0% our Butler graduates teaser when 02:56:15.580 --> 02:56:17.910 align:start position:0% our Butler graduates teaser when everyone<02:56:16.090> else<02:56:16.240> in<02:56:16.420> have<02:56:16.570> a<02:56:16.601> backup<02:56:16.920> video 02:56:17.910 --> 02:56:17.920 align:start position:0% everyone else in have a backup video 02:56:17.920 --> 02:56:24.180 align:start position:0% everyone else in have a backup video method<02:56:18.431> so<02:56:18.610> I<02:56:18.670> just<02:56:18.880> can't<02:56:22.050> this<02:56:23.050> would<02:56:23.860> be 02:56:24.180 --> 02:56:24.190 align:start position:0% method so I just can't this would be 02:56:24.190 --> 02:56:31.200 align:start position:0% method so I just can't this would be running<02:56:24.460> in<02:56:24.550> the<02:56:24.580> browser<02:56:28.860> so<02:56:29.860> hi<02:56:30.250> I<02:56:30.580> am<02:56:30.820> here 02:56:31.200 --> 02:56:31.210 align:start position:0% running in the browser so hi I am here 02:56:31.210 --> 02:56:34.261 align:start position:0% running in the browser so hi I am here to<02:56:31.330> talk<02:56:31.511> briefly<02:56:31.811> about<02:56:32.021> IP<02:56:32.681> LD<02:56:33.070> yeah<02:56:33.730> this<02:56:34.120> is 02:56:34.261 --> 02:56:34.271 align:start position:0% to talk briefly about IP LD yeah this is 02:56:34.271 --> 02:56:36.240 align:start position:0% to talk briefly about IP LD yeah this is one<02:56:34.420> of<02:56:34.511> the<02:56:34.650> interplanetary<02:56:35.650> and<02:56:35.920> family 02:56:36.240 --> 02:56:36.250 align:start position:0% one of the interplanetary and family 02:56:36.250 --> 02:56:38.400 align:start position:0% one of the interplanetary and family projects<02:56:36.851> the<02:56:37.181> IP<02:56:37.391> is<02:56:37.601> for<02:56:38.080> interplanetary 02:56:38.400 --> 02:56:38.410 align:start position:0% projects the IP is for interplanetary 02:56:38.410 --> 02:56:41.970 align:start position:0% projects the IP is for interplanetary the<02:56:38.950> LD<02:56:39.370> is<02:56:39.490> for<02:56:39.761> linked<02:56:40.030> data<02:56:40.300> so<02:56:41.050> the<02:56:41.410> IP<02:56:41.590> part 02:56:41.970 --> 02:56:41.980 align:start position:0% the LD is for linked data so the IP part 02:56:41.980 --> 02:56:45.150 align:start position:0% the LD is for linked data so the IP part sort<02:56:42.670> of<02:56:42.761> just<02:56:42.971> like<02:56:43.271> shared<02:56:44.200> identity<02:56:44.771> with 02:56:45.150 --> 02:56:45.160 align:start position:0% sort of just like shared identity with 02:56:45.160 --> 02:56:46.620 align:start position:0% sort of just like shared identity with the<02:56:45.190> ipfs<02:56:45.730> project<02:56:46.120> which<02:56:46.210> is<02:56:46.360> where<02:56:46.511> this 02:56:46.620 --> 02:56:46.630 align:start position:0% the ipfs project which is where this 02:56:46.630 --> 02:56:48.690 align:start position:0% the ipfs project which is where this comes<02:56:46.811> out<02:56:47.141> of<02:56:47.290> but<02:56:47.530> also<02:56:47.681> of<02:56:47.920> course<02:56:48.160> part<02:56:48.641> of 02:56:48.690 --> 02:56:48.700 align:start position:0% comes out of but also of course part of 02:56:48.700 --> 02:56:49.701 align:start position:0% comes out of but also of course part of the<02:56:48.820> nation-state 02:56:49.701 --> 02:56:49.711 align:start position:0% the nation-state 02:56:49.711 --> 02:56:52.551 align:start position:0% the nation-state we<02:56:50.671> want<02:56:50.911> to<02:56:51.091> build<02:56:51.301> data<02:56:51.751> structures<02:56:52.200> and 02:56:52.551 --> 02:56:52.561 align:start position:0% we want to build data structures and 02:56:52.561 --> 02:56:54.261 align:start position:0% we want to build data structures and linking<02:56:53.011> conventions<02:56:53.610> which<02:56:53.730> are<02:56:53.881> good<02:56:54.150> for 02:56:54.261 --> 02:56:54.271 align:start position:0% linking conventions which are good for 02:56:54.271 --> 02:56:55.821 align:start position:0% linking conventions which are good for when<02:56:54.570> we're<02:56:54.721> building<02:56:54.841> applications<02:56:55.621> that 02:56:55.821 --> 02:56:55.831 align:start position:0% when we're building applications that 02:56:55.831 --> 02:56:58.281 align:start position:0% when we're building applications that work<02:56:56.101> at<02:56:56.371> extremely<02:56:57.030> high<02:56:57.181> latency<02:56:57.601> offline 02:56:58.281 --> 02:56:58.291 align:start position:0% work at extremely high latency offline 02:56:58.291 --> 02:57:01.850 align:start position:0% work at extremely high latency offline and<02:56:58.621> interplanetary<02:56:59.371> galactic<02:57:00.181> whatever<02:57:00.860> so 02:57:01.850 --> 02:57:01.860 align:start position:0% and interplanetary galactic whatever so 02:57:01.860 --> 02:57:04.310 align:start position:0% and interplanetary galactic whatever so to<02:57:02.730> build<02:57:02.911> data<02:57:03.211> structures<02:57:03.661> for<02:57:03.690> distributed 02:57:04.310 --> 02:57:04.320 align:start position:0% to build data structures for distributed 02:57:04.320 --> 02:57:06.861 align:start position:0% to build data structures for distributed applications<02:57:04.831> on<02:57:04.950> this<02:57:05.070> scale<02:57:05.631> we<02:57:06.631> need<02:57:06.690> to 02:57:06.861 --> 02:57:06.871 align:start position:0% applications on this scale we need to 02:57:06.871 --> 02:57:08.541 align:start position:0% applications on this scale we need to get<02:57:06.990> a<02:57:07.021> couple<02:57:07.291> of<02:57:07.381> things<02:57:07.711> that<02:57:08.161> are<02:57:08.311> like 02:57:08.541 --> 02:57:08.551 align:start position:0% get a couple of things that are like 02:57:08.551 --> 02:57:10.251 align:start position:0% get a couple of things that are like kind<02:57:08.851> of<02:57:08.881> a<02:57:08.971> great<02:57:09.211> opponent<02:57:09.450> foundational 02:57:10.251 --> 02:57:10.261 align:start position:0% kind of a great opponent foundational 02:57:10.261 --> 02:57:11.901 align:start position:0% kind of a great opponent foundational concepts<02:57:10.650> picked<02:57:10.891> out<02:57:11.070> so<02:57:11.280> one<02:57:11.431> of<02:57:11.521> those<02:57:11.730> is 02:57:11.901 --> 02:57:11.911 align:start position:0% concepts picked out so one of those is 02:57:11.911 --> 02:57:15.551 align:start position:0% concepts picked out so one of those is of<02:57:12.061> course<02:57:12.501> Merkel<02:57:13.501> ization<02:57:13.771> and<02:57:14.221> linking 02:57:15.551 --> 02:57:15.561 align:start position:0% of course Merkel ization and linking 02:57:15.561 --> 02:57:18.020 align:start position:0% of course Merkel ization and linking that's<02:57:16.561> such<02:57:16.711> a<02:57:16.740> gimme<02:57:17.131> in<02:57:17.400> this<02:57:17.551> audience<02:57:17.820> I'm 02:57:18.020 --> 02:57:18.030 align:start position:0% that's such a gimme in this audience I'm 02:57:18.030 --> 02:57:19.491 align:start position:0% that's such a gimme in this audience I'm not<02:57:18.150> gonna<02:57:18.360> talk<02:57:18.601> about<02:57:18.721> it<02:57:18.900> anymore<02:57:19.110> of 02:57:19.491 --> 02:57:19.501 align:start position:0% not gonna talk about it anymore of 02:57:19.501 --> 02:57:21.350 align:start position:0% not gonna talk about it anymore of course<02:57:19.621> we<02:57:19.891> need<02:57:20.011> actual<02:57:20.371> things<02:57:20.521> let's<02:57:21.150> just 02:57:21.350 --> 02:57:21.360 align:start position:0% course we need actual things let's just 02:57:21.360 --> 02:57:23.541 align:start position:0% course we need actual things let's just do<02:57:21.541> it<02:57:21.570> I<02:57:21.871> filled<02:57:22.681> the<02:57:22.801> air<02:57:22.891> some<02:57:23.070> specs<02:57:23.371> for 02:57:23.541 --> 02:57:23.551 align:start position:0% do it I filled the air some specs for 02:57:23.551 --> 02:57:26.331 align:start position:0% do it I filled the air some specs for how<02:57:23.730> to<02:57:23.791> do<02:57:24.030> anything<02:57:24.921> since<02:57:25.921> we<02:57:26.011> want<02:57:26.161> to<02:57:26.251> talk 02:57:26.331 --> 02:57:26.341 align:start position:0% how to do anything since we want to talk 02:57:26.341 --> 02:57:27.711 align:start position:0% how to do anything since we want to talk about<02:57:26.400> data<02:57:26.820> structures<02:57:27.121> the<02:57:27.360> other<02:57:27.480> thing<02:57:27.631> we 02:57:27.711 --> 02:57:27.721 align:start position:0% about data structures the other thing we 02:57:27.721 --> 02:57:29.571 align:start position:0% about data structures the other thing we have<02:57:27.811> to<02:57:27.931> figure<02:57:28.381> out<02:57:28.411> is<02:57:28.650> what<02:57:29.011> indeed<02:57:29.371> is<02:57:29.551> a 02:57:29.571 --> 02:57:29.581 align:start position:0% have to figure out is what indeed is a 02:57:29.581 --> 02:57:33.321 align:start position:0% have to figure out is what indeed is a data<02:57:29.911> structure<02:57:30.211> and<02:57:30.931> so<02:57:31.320> an<02:57:31.591> IPL<02:57:31.921> D<02:57:32.331> we're 02:57:33.321 --> 02:57:33.331 align:start position:0% data structure and so an IPL D we're 02:57:33.331 --> 02:57:35.001 align:start position:0% data structure and so an IPL D we're going<02:57:33.480> to<02:57:33.570> sort<02:57:33.751> of<02:57:33.811> aim<02:57:34.021> for<02:57:34.471> eventually 02:57:35.001 --> 02:57:35.011 align:start position:0% going to sort of aim for eventually 02:57:35.011 --> 02:57:37.190 align:start position:0% going to sort of aim for eventually getting<02:57:35.190> towards<02:57:35.551> some<02:57:35.730> data<02:57:36.631> definition 02:57:37.190 --> 02:57:37.200 align:start position:0% getting towards some data definition 02:57:37.200 --> 02:57:38.930 align:start position:0% getting towards some data definition languages<02:57:37.621> like<02:57:37.950> the<02:57:38.101> imagine<02:57:38.431> schemas<02:57:38.911> for 02:57:38.930 --> 02:57:38.940 align:start position:0% languages like the imagine schemas for 02:57:38.940 --> 02:57:40.751 align:start position:0% languages like the imagine schemas for databases<02:57:39.541> but<02:57:39.900> now<02:57:40.021> for<02:57:40.261> decentralized 02:57:40.751 --> 02:57:40.761 align:start position:0% databases but now for decentralized 02:57:40.761 --> 02:57:44.751 align:start position:0% databases but now for decentralized serialization<02:57:41.761> concepts<02:57:43.311> but<02:57:44.311> that's<02:57:44.641> going 02:57:44.751 --> 02:57:44.761 align:start position:0% serialization concepts but that's going 02:57:44.761 --> 02:57:46.131 align:start position:0% serialization concepts but that's going to<02:57:44.820> be<02:57:44.881> the<02:57:45.001> aim<02:57:45.181> and<02:57:45.661> we're<02:57:45.811> actually<02:57:45.931> going 02:57:46.131 --> 02:57:46.141 align:start position:0% to be the aim and we're actually going 02:57:46.141 --> 02:57:47.390 align:start position:0% to be the aim and we're actually going to<02:57:46.200> start<02:57:46.291> somewhere<02:57:46.591> a<02:57:46.711> little<02:57:46.801> simpler<02:57:47.251> and 02:57:47.390 --> 02:57:47.400 align:start position:0% to start somewhere a little simpler and 02:57:47.400 --> 02:57:49.310 align:start position:0% to start somewhere a little simpler and I<02:57:47.461> feel<02:57:47.671> deep<02:57:47.881> and<02:57:48.450> we<02:57:48.541> want<02:57:48.751> some<02:57:49.051> sort<02:57:49.230> of 02:57:49.310 --> 02:57:49.320 align:start position:0% I feel deep and we want some sort of 02:57:49.320 --> 02:57:52.371 align:start position:0% I feel deep and we want some sort of common<02:57:50.041> data<02:57:50.371> model<02:57:50.570> that<02:57:51.570> works<02:57:51.990> regardless 02:57:52.371 --> 02:57:52.381 align:start position:0% common data model that works regardless 02:57:52.381 --> 02:57:54.081 align:start position:0% common data model that works regardless of<02:57:52.771> how<02:57:52.980> you're<02:57:53.131> going<02:57:53.251> to<02:57:53.341> serialize<02:57:53.791> things 02:57:54.081 --> 02:57:54.091 align:start position:0% of how you're going to serialize things 02:57:54.091 --> 02:57:55.551 align:start position:0% of how you're going to serialize things and<02:57:54.421> regardless<02:57:54.811> of<02:57:54.871> the<02:57:54.961> application<02:57:55.471> logic 02:57:55.551 --> 02:57:55.561 align:start position:0% and regardless of the application logic 02:57:55.561 --> 02:57:57.341 align:start position:0% and regardless of the application logic you're<02:57:55.860> about<02:57:56.070> to<02:57:56.251> bring<02:57:56.371> on<02:57:56.551> top<02:57:56.761> of<02:57:56.881> it<02:57:57.001> so 02:57:57.341 --> 02:57:57.351 align:start position:0% you're about to bring on top of it so 02:57:57.351 --> 02:58:00.890 align:start position:0% you're about to bring on top of it so maybe<02:57:58.431> serialization<02:57:59.431> oriented<02:58:00.360> thinking 02:58:00.890 --> 02:58:00.900 align:start position:0% maybe serialization oriented thinking 02:58:00.900 --> 02:58:03.020 align:start position:0% maybe serialization oriented thinking about<02:58:01.291> the<02:58:01.381> data<02:58:01.561> model<02:58:01.860> but<02:58:02.490> not<02:58:02.671> like 02:58:03.020 --> 02:58:03.030 align:start position:0% about the data model but not like 02:58:03.030 --> 02:58:03.750 align:start position:0% about the data model but not like implement 02:58:03.750 --> 02:58:03.760 align:start position:0% implement 02:58:03.760 --> 02:58:06.059 align:start position:0% implement -<02:58:03.970> fine<02:58:04.210> so<02:58:04.510> we<02:58:04.660> want<02:58:04.870> to<02:58:04.960> have<02:58:05.080> a<02:58:05.350> model<02:58:05.859> which 02:58:06.059 --> 02:58:06.069 align:start position:0% - fine so we want to have a model which 02:58:06.069 --> 02:58:08.309 align:start position:0% - fine so we want to have a model which feels<02:58:06.670> like<02:58:07.000> JSON<02:58:07.510> so<02:58:07.689> we<02:58:07.779> can<02:58:07.899> reason<02:58:08.260> about 02:58:08.309 --> 02:58:08.319 align:start position:0% feels like JSON so we can reason about 02:58:08.319 --> 02:58:10.950 align:start position:0% feels like JSON so we can reason about malison<02:58:09.010> lists<02:58:09.340> and<02:58:09.490> strings<02:58:09.670> and<02:58:09.970> so<02:58:10.120> on<02:58:10.270> but 02:58:10.950 --> 02:58:10.960 align:start position:0% malison lists and strings and so on but 02:58:10.960 --> 02:58:12.599 align:start position:0% malison lists and strings and so on but doesn't<02:58:11.229> need<02:58:11.290> to<02:58:11.410> be<02:58:11.500> defined<02:58:11.920> by<02:58:12.189> the<02:58:12.250> white 02:58:12.599 --> 02:58:12.609 align:start position:0% doesn't need to be defined by the white 02:58:12.609 --> 02:58:14.790 align:start position:0% doesn't need to be defined by the white 4<02:58:12.819> byte<02:58:12.970> serialization<02:58:13.540> problems<02:58:14.140> up<02:58:14.290> to<02:58:14.470> JSON 02:58:14.790 --> 02:58:14.800 align:start position:0% 4 byte serialization problems up to JSON 02:58:14.800 --> 02:58:16.290 align:start position:0% 4 byte serialization problems up to JSON so<02:58:15.220> we<02:58:15.430> should<02:58:15.580> be<02:58:15.609> able<02:58:15.760> to<02:58:15.910> bring<02:58:16.060> something 02:58:16.290 --> 02:58:16.300 align:start position:0% so we should be able to bring something 02:58:16.300 --> 02:58:18.059 align:start position:0% so we should be able to bring something like<02:58:16.420> C<02:58:16.720> or<02:58:16.899> and<02:58:17.140> have<02:58:17.229> an<02:58:17.380> amount<02:58:17.680> the<02:58:17.890> same 02:58:18.059 --> 02:58:18.069 align:start position:0% like C or and have an amount the same 02:58:18.069 --> 02:58:20.309 align:start position:0% like C or and have an amount the same item<02:58:18.399> or<02:58:18.760> JSON<02:58:19.300> what<02:58:19.479> you<02:58:19.569> do<02:58:19.720> want<02:58:19.960> to<02:58:19.990> keep<02:58:20.170> up 02:58:20.309 --> 02:58:20.319 align:start position:0% item or JSON what you do want to keep up 02:58:20.319 --> 02:58:21.900 align:start position:0% item or JSON what you do want to keep up or<02:58:20.620> cut<02:58:21.069> above<02:58:21.279> when<02:58:21.460> you<02:58:21.550> all<02:58:21.700> make<02:58:21.880> this 02:58:21.900 --> 02:58:21.910 align:start position:0% or cut above when you all make this 02:58:21.910 --> 02:58:23.900 align:start position:0% or cut above when you all make this other<02:58:22.180> strategy<02:58:22.689> entirely<02:58:23.020> this<02:58:23.260> really<02:58:23.529> fast 02:58:23.900 --> 02:58:23.910 align:start position:0% other strategy entirely this really fast 02:58:23.910 --> 02:58:25.860 align:start position:0% other strategy entirely this really fast we<02:58:24.910> should<02:58:25.060> be<02:58:25.149> able<02:58:25.240> to<02:58:25.359> use<02:58:25.510> all<02:58:25.660> of<02:58:25.689> these 02:58:25.860 --> 02:58:25.870 align:start position:0% we should be able to use all of these 02:58:25.870 --> 02:58:27.900 align:start position:0% we should be able to use all of these things<02:58:26.109> interchangeably<02:58:26.740> this<02:58:27.609> is<02:58:27.729> what<02:58:27.880> I 02:58:27.900 --> 02:58:27.910 align:start position:0% things interchangeably this is what I 02:58:27.910 --> 02:58:29.820 align:start position:0% things interchangeably this is what I peel<02:58:28.149> D<02:58:28.270> is<02:58:28.359> about<02:58:28.479> standardizing<02:58:29.350> this<02:58:29.560> data 02:58:29.820 --> 02:58:29.830 align:start position:0% peel D is about standardizing this data 02:58:29.830 --> 02:58:31.200 align:start position:0% peel D is about standardizing this data model<02:58:30.160> and<02:58:30.279> making<02:58:30.670> it<02:58:30.760> connects<02:58:31.180> to 02:58:31.200 --> 02:58:31.210 align:start position:0% model and making it connects to 02:58:31.210 --> 02:58:33.120 align:start position:0% model and making it connects to everything<02:58:31.660> codec<02:58:32.410> should<02:58:32.620> be<02:58:32.740> able<02:58:32.890> to<02:58:32.979> come 02:58:33.120 --> 02:58:33.130 align:start position:0% everything codec should be able to come 02:58:33.130 --> 02:58:34.769 align:start position:0% everything codec should be able to come and<02:58:33.279> go<02:58:33.370> from<02:58:33.580> here<02:58:33.670> as<02:58:33.910> they<02:58:34.029> please 02:58:34.769 --> 02:58:34.779 align:start position:0% and go from here as they please 02:58:34.779 --> 02:58:38.400 align:start position:0% and go from here as they please now<02:58:35.590> once<02:58:35.920> we<02:58:36.130> have<02:58:36.490> a<02:58:36.939> state<02:58:37.450> model<02:58:37.630> we<02:58:38.260> can 02:58:38.400 --> 02:58:38.410 align:start position:0% now once we have a state model we can 02:58:38.410 --> 02:58:40.710 align:start position:0% now once we have a state model we can also<02:58:38.529> take<02:58:38.859> those<02:58:39.220> concepts<02:58:39.939> announcement 02:58:40.710 --> 02:58:40.720 align:start position:0% also take those concepts announcement 02:58:40.720 --> 02:58:43.260 align:start position:0% also take those concepts announcement lists<02:58:41.580> and<02:58:42.580> we<02:58:42.609> can<02:58:42.850> build<02:58:43.000> functional 02:58:43.260 --> 02:58:43.270 align:start position:0% lists and we can build functional 02:58:43.270 --> 02:58:45.840 align:start position:0% lists and we can build functional operations<02:58:43.930> on<02:58:44.050> top<02:58:44.319> of<02:58:44.470> these<02:58:44.620> like<02:58:45.250> any<02:58:45.640> kind 02:58:45.840 --> 02:58:45.850 align:start position:0% operations on top of these like any kind 02:58:45.850 --> 02:58:47.940 align:start position:0% operations on top of these like any kind of<02:58:45.910> traversal<02:58:46.479> and<02:58:46.660> fullness<02:58:47.020> or<02:58:47.410> selections 02:58:47.940 --> 02:58:47.950 align:start position:0% of traversal and fullness or selections 02:58:47.950 --> 02:58:48.990 align:start position:0% of traversal and fullness or selections that<02:58:48.100> you've<02:58:48.220> ever<02:58:48.370> heard<02:58:48.580> of<02:58:48.640> from<02:58:48.850> any 02:58:48.990 --> 02:58:49.000 align:start position:0% that you've ever heard of from any 02:58:49.000 --> 02:58:50.760 align:start position:0% that you've ever heard of from any functional<02:58:49.479> programming<02:58:49.779> language<02:58:50.080> we're 02:58:50.760 --> 02:58:50.770 align:start position:0% functional programming language we're 02:58:50.770 --> 02:58:52.200 align:start position:0% functional programming language we're trying<02:58:50.979> to<02:58:51.100> write<02:58:51.160> a<02:58:51.220> standardized<02:58:51.729> way<02:58:51.760> to<02:58:51.939> do 02:58:52.200 --> 02:58:52.210 align:start position:0% trying to write a standardized way to do 02:58:52.210 --> 02:58:56.370 align:start position:0% trying to write a standardized way to do this<02:58:52.390> on<02:58:52.630> top<02:58:52.960> of<02:58:53.170> this<02:58:53.740> table<02:58:54.270> so<02:58:55.270> if<02:58:55.750> you<02:58:56.109> have 02:58:56.370 --> 02:58:56.380 align:start position:0% this on top of this table so if you have 02:58:56.380 --> 02:58:58.769 align:start position:0% this on top of this table so if you have any<02:58:56.770> structure<02:58:57.399> that<02:58:57.430> you<02:58:57.939> can<02:58:57.970> map<02:58:58.359> into<02:58:58.750> the 02:58:58.769 --> 02:58:58.779 align:start position:0% any structure that you can map into the 02:58:58.779 --> 02:59:00.750 align:start position:0% any structure that you can map into the data<02:58:59.050> models<02:58:59.470> with<02:58:59.680> your<02:58:59.859> serialize<02:59:00.279> formats 02:59:00.750 --> 02:59:00.760 align:start position:0% data models with your serialize formats 02:59:00.760 --> 02:59:02.820 align:start position:0% data models with your serialize formats then<02:59:01.540> we<02:59:01.990> can<02:59:02.170> give<02:59:02.319> you<02:59:02.410> a<02:59:02.470> bunch<02:59:02.680> of 02:59:02.820 --> 02:59:02.830 align:start position:0% then we can give you a bunch of 02:59:02.830 --> 02:59:04.440 align:start position:0% then we can give you a bunch of libraries<02:59:03.399> where<02:59:03.729> these<02:59:03.850> charges<02:59:04.300> or 02:59:04.440 --> 02:59:04.450 align:start position:0% libraries where these charges or 02:59:04.450 --> 02:59:06.550 align:start position:0% libraries where these charges or thoughts<02:59:04.750> and<02:59:04.899> songs 02:59:06.550 --> 02:59:06.560 align:start position:0% thoughts and songs 02:59:06.560 --> 02:59:08.979 align:start position:0% thoughts and songs on<02:59:06.949> top<02:59:07.550> of<02:59:07.699> all<02:59:07.850> this<02:59:07.999> we<02:59:08.060> are<02:59:08.239> now<02:59:08.569> trying<02:59:08.810> to 02:59:08.979 --> 02:59:08.989 align:start position:0% on top of all this we are now trying to 02:59:08.989 --> 02:59:10.989 align:start position:0% on top of all this we are now trying to also<02:59:09.170> build<02:59:09.499> schemas<02:59:10.279> which<02:59:10.579> allow<02:59:10.819> you<02:59:10.880> to 02:59:10.989 --> 02:59:10.999 align:start position:0% also build schemas which allow you to 02:59:10.999 --> 02:59:12.639 align:start position:0% also build schemas which allow you to have<02:59:11.149> a<02:59:11.209> plan<02:59:11.420> the<02:59:11.899> way<02:59:12.020> you<02:59:12.079> interact<02:59:12.439> with 02:59:12.639 --> 02:59:12.649 align:start position:0% have a plan the way you interact with 02:59:12.649 --> 02:59:15.099 align:start position:0% have a plan the way you interact with your<02:59:12.770> data<02:59:13.119> name<02:59:14.119> sometimes<02:59:14.449> even<02:59:14.959> if<02:59:15.020> you 02:59:15.099 --> 02:59:15.109 align:start position:0% your data name sometimes even if you 02:59:15.109 --> 02:59:17.109 align:start position:0% your data name sometimes even if you don't<02:59:15.289> see<02:59:15.499> realized<02:59:15.800> schema<02:59:16.609> free<02:59:16.880> data 02:59:17.109 --> 02:59:17.119 align:start position:0% don't see realized schema free data 02:59:17.119 --> 02:59:31.809 align:start position:0% don't see realized schema free data analyst<02:59:17.600> Chema's<02:59:17.930> at<02:59:18.050> the<02:59:18.140> same<02:59:18.350> time<02:59:30.819> our 02:59:31.809 --> 02:59:31.819 align:start position:0% analyst Chema's at the same time our 02:59:31.819 --> 02:59:35.439 align:start position:0% analyst Chema's at the same time our research<02:59:32.779> I'm<02:59:33.560> a<02:59:33.619> researcher<02:59:34.220> from<02:59:34.760> total 02:59:35.439 --> 02:59:35.449 align:start position:0% research I'm a researcher from total 02:59:35.449 --> 02:59:37.929 align:start position:0% research I'm a researcher from total debt<02:59:35.630> top<02:59:36.079> Institute<02:59:36.529> of<02:59:36.649> Technology<02:59:37.310> so<02:59:37.550> I'm 02:59:37.929 --> 02:59:37.939 align:start position:0% debt top Institute of Technology so I'm 02:59:37.939 --> 02:59:39.699 align:start position:0% debt top Institute of Technology so I'm reading<02:59:38.149> in<02:59:38.359> Japan<02:59:38.659> that<02:59:38.689> they<02:59:38.989> welcome<02:59:39.529> you 02:59:39.699 --> 02:59:39.709 align:start position:0% reading in Japan that they welcome you 02:59:39.709 --> 02:59:43.149 align:start position:0% reading in Japan that they welcome you back<02:59:40.010> and<02:59:40.369> that<02:59:41.329> conduct<02:59:41.899> is<02:59:42.260> not<02:59:42.649> a<02:59:42.800> network 02:59:43.149 --> 02:59:43.159 align:start position:0% back and that conduct is not a network 02:59:43.159 --> 02:59:46.090 align:start position:0% back and that conduct is not a network research<02:59:43.760> and<02:59:44.119> I<02:59:44.569> give<02:59:45.319> you<02:59:45.350> an<02:59:45.619> information 02:59:46.090 --> 02:59:46.100 align:start position:0% research and I give you an information 02:59:46.100 --> 02:59:51.550 align:start position:0% research and I give you an information of<02:59:46.939> our<02:59:47.209> product<02:59:47.930> names<02:59:48.859> in<02:59:49.130> rock<02:59:49.369> in<02:59:49.670> a<02:59:50.560> public 02:59:51.550 --> 02:59:51.560 align:start position:0% of our product names in rock in a public 02:59:51.560 --> 02:59:55.330 align:start position:0% of our product names in rock in a public forest<02:59:52.489> blockchain<02:59:53.109> network<02:59:54.109> simulator<02:59:54.560> so 02:59:55.330 --> 02:59:55.340 align:start position:0% forest blockchain network simulator so 02:59:55.340 --> 03:00:02.080 align:start position:0% forest blockchain network simulator so you<02:59:55.699> see<02:59:55.970> now<02:59:56.300> that<02:59:58.180> when<02:59:59.180> you<02:59:59.359> adopt<03:00:00.579> 2015<03:00:01.579> and 03:00:02.080 --> 03:00:02.090 align:start position:0% you see now that when you adopt 2015 and 03:00:02.090 --> 03:00:06.670 align:start position:0% you see now that when you adopt 2015 and we<03:00:02.749> are<03:00:02.810> taking<03:00:03.670> Internet<03:00:04.899> emitter<03:00:05.899> and<03:00:06.289> wrote 03:00:06.670 --> 03:00:06.680 align:start position:0% we are taking Internet emitter and wrote 03:00:06.680 --> 03:00:09.639 align:start position:0% we are taking Internet emitter and wrote a<03:00:06.709> parameter<03:00:07.189> for<03:00:07.609> as<03:00:08.029> of<03:00:08.149> today<03:00:08.479> so<03:00:09.260> anyway 03:00:09.639 --> 03:00:09.649 align:start position:0% a parameter for as of today so anyway 03:00:09.649 --> 03:00:13.439 align:start position:0% a parameter for as of today so anyway you<03:00:10.430> see<03:00:10.670> make<03:00:11.329> dots<03:00:11.630> of<03:00:12.319> course<03:00:12.649> state 03:00:13.439 --> 03:00:13.449 align:start position:0% you see make dots of course state 03:00:13.449 --> 03:00:18.090 align:start position:0% you see make dots of course state represents<03:00:14.449> between<03:00:15.319> old<03:00:15.529> and<03:00:16.149> drive 03:00:18.090 --> 03:00:18.100 align:start position:0% represents between old and drive 03:00:18.100 --> 03:00:22.090 align:start position:0% represents between old and drive truncations<03:00:19.100> of<03:00:19.430> rocks<03:00:21.100> transmitting 03:00:22.090 --> 03:00:22.100 align:start position:0% truncations of rocks transmitting 03:00:22.100 --> 03:00:26.769 align:start position:0% truncations of rocks transmitting between<03:00:22.609> nodes<03:00:23.180> and<03:00:23.840> why<03:00:24.770> why<03:00:25.489> did<03:00:25.729> we<03:00:25.909> develop 03:00:26.769 --> 03:00:26.779 align:start position:0% between nodes and why why did we develop 03:00:26.779 --> 03:00:30.010 align:start position:0% between nodes and why why did we develop this<03:00:26.899> kind<03:00:27.140> of<03:00:27.350> software 03:00:30.010 --> 03:00:30.020 align:start position:0% 03:00:30.020 --> 03:00:33.949 align:start position:0% and<03:00:31.020> it's<03:00:31.859> very<03:00:32.039> kind<03:00:32.399> of<03:00:32.670> easy<03:00:33.149> to<03:00:33.300> find<03:00:33.630> this 03:00:33.949 --> 03:00:33.959 align:start position:0% and it's very kind of easy to find this 03:00:33.959 --> 03:00:37.160 align:start position:0% and it's very kind of easy to find this demonstration<03:00:34.920> test<03:00:35.489> by<03:00:35.729> searching<03:00:36.029> read<03:00:36.569> the 03:00:37.160 --> 03:00:37.170 align:start position:0% demonstration test by searching read the 03:00:37.170 --> 03:00:41.059 align:start position:0% demonstration test by searching read the QR<03:00:38.840> single<03:00:39.840> as<03:00:40.260> I<03:00:40.529> am 03:00:41.059 --> 03:00:41.069 align:start position:0% QR single as I am 03:00:41.069 --> 03:00:44.449 align:start position:0% QR single as I am Yosuke<03:00:42.029> and<03:00:42.479> visualizer<03:00:42.899> you<03:00:43.439> can<03:00:43.680> access<03:00:44.279> and 03:00:44.449 --> 03:00:44.459 align:start position:0% Yosuke and visualizer you can access and 03:00:44.459 --> 03:00:50.719 align:start position:0% Yosuke and visualizer you can access and see<03:00:44.699> on<03:00:44.970> your<03:00:45.149> browser<03:00:45.959> and<03:00:47.329> now<03:00:48.499> let<03:00:49.499> me<03:00:49.739> both 03:00:50.719 --> 03:00:50.729 align:start position:0% see on your browser and now let me both 03:00:50.729 --> 03:00:57.170 align:start position:0% see on your browser and now let me both to<03:00:50.970> you<03:00:51.060> might<03:00:54.079> go<03:00:55.340> talk<03:00:56.340> about<03:00:56.369> boys<03:00:56.909> of 03:00:57.170 --> 03:00:57.180 align:start position:0% to you might go talk about boys of 03:00:57.180 --> 03:00:59.330 align:start position:0% to you might go talk about boys of course<03:00:57.329> performance<03:00:57.959> and<03:00:58.170> we're<03:00:58.499> doing 03:00:59.330 --> 03:00:59.340 align:start position:0% course performance and we're doing 03:00:59.340 --> 03:01:03.279 align:start position:0% course performance and we're doing research<03:00:59.609> on<03:01:01.220> securities<03:01:02.220> and<03:01:02.520> we<03:01:02.880> give<03:01:03.180> a 03:01:03.279 --> 03:01:03.289 align:start position:0% research on securities and we give a 03:01:03.289 --> 03:01:06.649 align:start position:0% research on securities and we give a talk<03:01:04.289> about<03:01:04.770> our<03:01:05.039> security<03:01:05.310> search<03:01:05.789> about 03:01:06.649 --> 03:01:06.659 align:start position:0% talk about our security search about 03:01:06.659 --> 03:01:10.699 align:start position:0% talk about our security search about eternal<03:01:07.350> III<03:01:07.949> m<03:01:08.189> in<03:01:08.850> Thursday<03:01:09.630> writing<03:01:10.439> talk 03:01:10.699 --> 03:01:10.709 align:start position:0% eternal III m in Thursday writing talk 03:01:10.709 --> 03:01:20.390 align:start position:0% eternal III m in Thursday writing talk session<03:01:10.949> in<03:01:11.640> the<03:01:12.090> evening<03:01:12.439> so<03:01:17.300> your 03:01:20.390 --> 03:01:20.400 align:start position:0% 03:01:20.400 --> 03:01:24.150 align:start position:0% Sunanda<03:01:21.931> decided<03:01:22.931> about<03:01:23.051> the<03:01:23.381> sniper<03:01:23.771> and 03:01:24.150 --> 03:01:24.160 align:start position:0% Sunanda decided about the sniper and 03:01:24.160 --> 03:01:26.820 align:start position:0% Sunanda decided about the sniper and this<03:01:24.881> is<03:01:25.030> a<03:01:25.061> public<03:01:25.780> vote<03:01:26.080> senator<03:01:26.410> straight 03:01:26.820 --> 03:01:26.830 align:start position:0% this is a public vote senator straight 03:01:26.830 --> 03:01:30.390 align:start position:0% this is a public vote senator straight so<03:01:27.311> first<03:01:28.211> target<03:01:28.601> is<03:01:28.750> a<03:01:28.841> world<03:01:29.530> Bitcoin<03:01:30.221> right 03:01:30.390 --> 03:01:30.400 align:start position:0% so first target is a world Bitcoin right 03:01:30.400 --> 03:01:35.161 align:start position:0% so first target is a world Bitcoin right when<03:01:30.700> those<03:01:31.271> coin<03:01:31.601> and<03:01:32.641> naturally<03:01:33.641> of<03:01:33.931> 43m<03:01:34.931> and 03:01:35.161 --> 03:01:35.171 align:start position:0% when those coin and naturally of 43m and 03:01:35.171 --> 03:01:39.240 align:start position:0% when those coin and naturally of 43m and as<03:01:35.620> I<03:01:35.830> said<03:01:36.131> we<03:01:36.881> didn't<03:01:37.120> talk<03:01:37.240> about<03:01:38.250> consent 03:01:39.240 --> 03:01:39.250 align:start position:0% as I said we didn't talk about consent 03:01:39.250 --> 03:01:45.390 align:start position:0% as I said we didn't talk about consent and<03:01:39.900> we<03:01:41.431> provide<03:01:42.540> riser<03:01:43.540> and<03:01:43.961> we<03:01:44.681> provided 03:01:45.390 --> 03:01:45.400 align:start position:0% and we provide riser and we provided 03:01:45.400 --> 03:01:49.701 align:start position:0% and we provide riser and we provided demo<03:01:45.790> and<03:01:46.061> so<03:01:46.950> that's<03:01:47.950> right<03:01:48.160> as<03:01:48.370> you<03:01:48.580> do 03:01:49.701 --> 03:01:49.711 align:start position:0% demo and so that's right as you do 03:01:49.711 --> 03:01:52.890 align:start position:0% demo and so that's right as you do routine<03:01:50.711> network<03:01:51.070> research<03:01:51.431> by<03:01:52.120> Josefa<03:01:52.480> I 03:01:52.890 --> 03:01:52.900 align:start position:0% routine network research by Josefa I 03:01:52.900 --> 03:01:57.381 align:start position:0% routine network research by Josefa I seem<03:01:53.561> to<03:01:53.740> find<03:01:54.311> on<03:01:54.671> it<03:01:55.091> on<03:01:55.391> the<03:01:55.841> type 03:01:57.381 --> 03:01:57.391 align:start position:0% seem to find on it on the type 03:01:57.391 --> 03:02:05.720 align:start position:0% seem to find on it on the type interchanging<03:01:58.391> that<03:01:58.601> you<03:01:58.750> do<03:01:59.471> your<03:01:59.650> research 03:02:05.720 --> 03:02:05.730 align:start position:0% 03:02:05.730 --> 03:02:09.780 align:start position:0% say<03:02:06.730> like<03:02:06.910> we'll<03:02:07.120> do<03:02:07.211> you<03:02:07.271> like<03:02:08.040> around<03:02:09.040> 25 03:02:09.780 --> 03:02:09.790 align:start position:0% say like we'll do you like around 25 03:02:09.790 --> 03:02:12.680 align:start position:0% say like we'll do you like around 25 minutes<03:02:09.971> or<03:02:10.450> 20<03:02:10.721> minutes<03:02:10.750> and<03:02:11.051> small<03:02:11.290> groups 03:02:12.680 --> 03:02:12.690 align:start position:0% minutes or 20 minutes and small groups 03:02:12.690 --> 03:02:18.609 align:start position:0% minutes or 20 minutes and small groups what<03:02:13.690> if<03:02:13.780> okay<03:02:13.990> that's<03:02:14.141> it<03:02:14.440> smugglers 03:02:18.609 --> 03:02:18.619 align:start position:0% 03:02:18.619 --> 03:02:21.080 align:start position:0% and<03:02:19.619> then<03:02:19.859> we'll<03:02:20.100> come<03:02:20.369> back<03:02:20.399> here<03:02:20.550> report 03:02:21.080 --> 03:02:21.090 align:start position:0% and then we'll come back here report 03:02:21.090 --> 03:02:22.350 align:start position:0% and then we'll come back here report back 03:02:22.350 --> 03:02:22.360 align:start position:0% back 03:02:22.360 --> 03:02:31.630 align:start position:0% back [Music] 03:02:31.630 --> 03:02:31.640 align:start position:0% 03:02:31.640 --> 03:02:36.309 align:start position:0% okay<03:02:33.489> so<03:02:34.489> for<03:02:34.670> the<03:02:34.729> small<03:02:34.939> groups<03:02:35.210> but<03:02:36.170> it's 03:02:36.309 --> 03:02:36.319 align:start position:0% okay so for the small groups but it's 03:02:36.319 --> 03:02:38.559 align:start position:0% okay so for the small groups but it's like<03:02:36.470> basically<03:02:37.340> popcorn<03:02:38.029> office'<03:02:38.420> like 03:02:38.559 --> 03:02:38.569 align:start position:0% like basically popcorn office' like 03:02:38.569 --> 03:02:39.760 align:start position:0% like basically popcorn office' like raise<03:02:38.779> your<03:02:38.899> hand<03:02:39.080> and<03:02:39.229> say<03:02:39.380> something<03:02:39.680> about 03:02:39.760 --> 03:02:39.770 align:start position:0% raise your hand and say something about 03:02:39.770 --> 03:02:42.450 align:start position:0% raise your hand and say something about like<03:02:39.920> a<03:02:40.040> topic<03:02:40.489> they'd<03:02:40.670> like<03:02:40.939> to<03:02:40.970> discuss 03:02:42.450 --> 03:02:42.460 align:start position:0% like a topic they'd like to discuss 03:02:42.460 --> 03:02:45.070 align:start position:0% like a topic they'd like to discuss so<03:02:43.460> one<03:02:44.000> topic<03:02:44.330> I<03:02:44.449> would<03:02:44.569> just<03:02:44.750> like<03:02:45.050> to 03:02:45.070 --> 03:02:45.080 align:start position:0% so one topic I would just like to 03:02:45.080 --> 03:02:50.380 align:start position:0% so one topic I would just like to provide<03:02:45.380> for<03:02:45.560> myself<03:02:45.680> is<03:02:46.130> a<03:02:47.800> network<03:02:49.390> light 03:02:50.380 --> 03:02:50.390 align:start position:0% provide for myself is a network light 03:02:50.390 --> 03:03:11.801 align:start position:0% provide for myself is a network light what<03:02:51.430> is<03:02:52.430> there<03:02:52.609> like<03:02:52.960> networking<03:02:53.960> like<03:02:54.430> DHT 03:03:11.801 --> 03:03:11.811 align:start position:0% 03:03:11.811 --> 03:03:17.290 align:start position:0% funding<03:03:12.620> the<03:03:13.521> funding<03:03:13.730> boom<03:03:15.070> okay<03:03:16.240> any<03:03:17.240> other 03:03:17.290 --> 03:03:17.300 align:start position:0% funding the funding boom okay any other 03:03:17.300 --> 03:03:24.751 align:start position:0% funding the funding boom okay any other topics<03:03:17.721> this<03:03:19.511> browser<03:03:20.511> seemingly<03:03:23.050> that's 03:03:24.751 --> 03:03:24.761 align:start position:0% topics this browser seemingly that's 03:03:24.761 --> 03:03:48.301 align:start position:0% topics this browser seemingly that's building<03:03:25.761> browsers<03:03:26.210> or 03:03:48.301 --> 03:03:48.311 align:start position:0% 03:03:48.311 --> 03:04:08.160 align:start position:0% yeah 03:04:08.160 --> 03:04:08.170 align:start position:0% 03:04:08.170 --> 03:04:10.850 align:start position:0% yeah 03:04:10.850 --> 03:04:10.860 align:start position:0% 03:04:10.860 --> 03:04:20.511 align:start position:0% data<03:04:12.410> availability 03:04:20.511 --> 03:04:20.521 align:start position:0% 03:04:20.521 --> 03:04:27.020 align:start position:0% right 03:04:27.020 --> 03:04:27.030 align:start position:0% 03:04:27.030 --> 03:04:30.810 align:start position:0% don't<03:04:28.030> worry<03:04:28.240> about<03:04:28.450> much<03:04:29.490> we<03:04:30.490> get<03:04:30.640> more 03:04:30.810 --> 03:04:30.820 align:start position:0% don't worry about much we get more 03:04:30.820 --> 03:04:37.020 align:start position:0% don't worry about much we get more granular<03:04:35.490> there's<03:04:36.490> actually<03:04:36.790> a<03:04:36.820> lot<03:04:37.000> more 03:04:37.020 --> 03:04:37.030 align:start position:0% granular there's actually a lot more 03:04:37.030 --> 03:04:38.640 align:start position:0% granular there's actually a lot more people<03:04:37.390> here<03:04:37.660> than<03:04:37.690> I<03:04:37.900> expected<03:04:38.320> so<03:04:38.380> if<03:04:38.561> you 03:04:38.640 --> 03:04:38.650 align:start position:0% people here than I expected so if you 03:04:38.650 --> 03:04:42.270 align:start position:0% people here than I expected so if you probably<03:04:39.010> just<03:04:39.190> do<03:04:39.370> it<03:04:40.320> yeah<03:04:41.320> I<03:04:41.351> think<03:04:41.650> so 03:04:42.270 --> 03:04:42.280 align:start position:0% probably just do it yeah I think so 03:04:42.280 --> 03:04:43.680 align:start position:0% probably just do it yeah I think so yeah<03:04:42.490> that's<03:04:42.760> really<03:04:42.910> like<03:04:43.061> a<03:04:43.180> like<03:04:43.450> a<03:04:43.480> big 03:04:43.680 --> 03:04:43.690 align:start position:0% yeah that's really like a like a big 03:04:43.690 --> 03:04:48.500 align:start position:0% yeah that's really like a like a big group<03:04:43.840> yeah<03:04:44.230> yeah<03:04:45.450> yeah<03:04:46.450> come<03:04:46.690> over<03:04:46.900> here 03:04:48.500 --> 03:04:48.510 align:start position:0% group yeah yeah yeah come over here 03:04:48.510 --> 03:05:07.970 align:start position:0% group yeah yeah yeah come over here boom<03:04:49.660> s<03:04:51.540> cars<03:04:56.550> maybe<03:04:57.550> I<03:04:57.670> put<03:04:58.000> it<03:05:00.750> yeah 03:05:07.970 --> 03:05:07.980 align:start position:0% 03:05:07.980 --> 03:05:10.410 align:start position:0% sorry 03:05:10.410 --> 03:05:10.420 align:start position:0% sorry 03:05:10.420 --> 03:05:12.689 align:start position:0% sorry we<03:05:10.870> can<03:05:11.020> have<03:05:11.109> someone<03:05:11.380> take<03:05:11.680> back<03:05:12.130> the<03:05:12.550> life 03:05:12.689 --> 03:05:12.699 align:start position:0% we can have someone take back the life 03:05:12.699 --> 03:05:14.729 align:start position:0% we can have someone take back the life instantly<03:05:13.090> do<03:05:13.930> a<03:05:13.960> raise<03:05:14.170> our<03:05:14.319> hands<03:05:14.470> on<03:05:14.649> this 03:05:14.729 --> 03:05:14.739 align:start position:0% instantly do a raise our hands on this 03:05:14.739 --> 03:05:37.800 align:start position:0% instantly do a raise our hands on this hot<03:05:14.949> picture<03:05:15.340> there's<03:05:25.710> that<03:05:26.710> red<03:05:26.890> petals<03:05:27.520> red 03:05:37.800 --> 03:05:37.810 align:start position:0% 03:05:37.810 --> 03:05:40.240 align:start position:0% first<03:05:38.810> thing<03:05:38.960> you<03:05:39.020> little<03:05:39.229> next<03:05:39.710> you're 03:05:40.240 --> 03:05:40.250 align:start position:0% first thing you little next you're 03:05:40.250 --> 03:05:44.370 align:start position:0% first thing you little next you're single<03:05:40.700> if<03:05:41.600> you<03:05:41.720> own<03:05:41.810> the<03:05:41.960> interjects<03:05:42.710> purple 03:05:44.370 --> 03:05:44.380 align:start position:0% single if you own the interjects purple 03:05:44.380 --> 03:05:49.120 align:start position:0% single if you own the interjects purple said<03:05:45.380> again<03:05:46.510> 100<03:05:47.510> next<03:05:48.050> side<03:05:48.740> let<03:05:48.890> the<03:05:48.950> person 03:05:49.120 --> 03:05:49.130 align:start position:0% said again 100 next side let the person 03:05:49.130 --> 03:05:51.099 align:start position:0% said again 100 next side let the person finish<03:05:49.520> in<03:05:49.640> a<03:05:49.729> little<03:05:50.060> Kaltura<03:05:50.450> okay 03:05:51.099 --> 03:05:51.109 align:start position:0% finish in a little Kaltura okay 03:05:51.109 --> 03:05:52.420 align:start position:0% finish in a little Kaltura okay you'll<03:05:51.260> need<03:05:51.410> to<03:05:51.560> checked<03:05:51.800> on<03:05:51.950> something<03:05:52.250> with 03:05:52.420 --> 03:05:52.430 align:start position:0% you'll need to checked on something with 03:05:52.430 --> 03:05:53.860 align:start position:0% you'll need to checked on something with two<03:05:52.609> thumbs<03:05:52.819> up<03:05:52.939> everybody<03:05:53.420> the<03:05:53.479> person<03:05:53.750> will 03:05:53.860 --> 03:05:53.870 align:start position:0% two thumbs up everybody the person will 03:05:53.870 --> 03:05:58.120 align:start position:0% two thumbs up everybody the person will see<03:05:54.020> you<03:05:54.170> they<03:05:54.740> said<03:05:54.950> everyone<03:05:55.399> cool<03:05:57.130> yeah 03:05:58.120 --> 03:05:58.130 align:start position:0% see you they said everyone cool yeah 03:05:58.130 --> 03:06:09.400 align:start position:0% see you they said everyone cool yeah that's<03:05:58.910> nice<03:06:06.550> yes<03:06:07.550> so<03:06:07.790> I<03:06:08.149> really<03:06:08.390> liked<03:06:08.600> that<03:06:08.689> a 03:06:09.400 --> 03:06:09.410 align:start position:0% that's nice yes so I really liked that a 03:06:09.410 --> 03:06:11.950 align:start position:0% that's nice yes so I really liked that a lot<03:06:09.830> of<03:06:10.100> the<03:06:10.189> talks<03:06:10.430> had<03:06:10.780> social<03:06:11.780> and 03:06:11.950 --> 03:06:11.960 align:start position:0% lot of the talks had social and 03:06:11.960 --> 03:06:13.540 align:start position:0% lot of the talks had social and political<03:06:12.080> implications<03:06:13.010> and<03:06:13.189> likely<03:06:13.460> to 03:06:13.540 --> 03:06:13.550 align:start position:0% political implications and likely to 03:06:13.550 --> 03:06:16.179 align:start position:0% political implications and likely to talked<03:06:13.790> about<03:06:14.060> why<03:06:14.960> their<03:06:15.380> topic<03:06:15.740> why<03:06:15.950> their 03:06:16.179 --> 03:06:16.189 align:start position:0% talked about why their topic why their 03:06:16.189 --> 03:06:19.660 align:start position:0% talked about why their topic why their projects<03:06:16.670> were<03:06:16.819> important<03:06:17.479> to<03:06:18.670> system 03:06:19.660 --> 03:06:19.670 align:start position:0% projects were important to system 03:06:19.670 --> 03:06:22.540 align:start position:0% projects were important to system outside<03:06:20.450> of<03:06:20.600> just<03:06:20.780> like<03:06:21.220> here<03:06:22.220> at<03:06:22.340> a<03:06:22.370> whole 03:06:22.540 --> 03:06:22.550 align:start position:0% outside of just like here at a whole 03:06:22.550 --> 03:06:23.920 align:start position:0% outside of just like here at a whole stuff<03:06:22.790> which<03:06:23.000> is<03:06:23.120> important<03:06:23.479> also<03:06:23.600> but 03:06:23.920 --> 03:06:23.930 align:start position:0% stuff which is important also but 03:06:23.930 --> 03:06:34.040 align:start position:0% stuff which is important also but there's<03:06:24.290> no<03:06:24.590> limitations 03:06:34.040 --> 03:06:34.050 align:start position:0% 03:06:34.050 --> 03:06:36.319 align:start position:0% I<03:06:34.079> personally<03:06:34.800> and<03:06:35.369> I<03:06:35.699> would<03:06:35.880> say<03:06:36.029> that<03:06:36.210> in 03:06:36.319 --> 03:06:36.329 align:start position:0% I personally and I would say that in 03:06:36.329 --> 03:06:39.139 align:start position:0% I personally and I would say that in country<03:06:36.659> said<03:06:36.960> the<03:06:37.640> authoritarian<03:06:38.640> countries 03:06:39.139 --> 03:06:39.149 align:start position:0% country said the authoritarian countries 03:06:39.149 --> 03:06:42.529 align:start position:0% country said the authoritarian countries like<03:06:39.359> my<03:06:39.840> country<03:06:40.289> Venezuela<03:06:41.029> and<03:06:42.029> see<03:06:42.270> that 03:06:42.529 --> 03:06:42.539 align:start position:0% like my country Venezuela and see that 03:06:42.539 --> 03:06:43.760 align:start position:0% like my country Venezuela and see that there<03:06:42.720> are<03:06:42.750> some<03:06:42.930> lot<03:06:43.079> of<03:06:43.170> people<03:06:43.439> that<03:06:43.619> are 03:06:43.760 --> 03:06:43.770 align:start position:0% there are some lot of people that are 03:06:43.770 --> 03:06:45.710 align:start position:0% there are some lot of people that are actually<03:06:44.670> using<03:06:44.939> a<03:06:45.210> lot<03:06:45.359> of<03:06:45.420> peer-to-peer 03:06:45.710 --> 03:06:45.720 align:start position:0% actually using a lot of peer-to-peer 03:06:45.720 --> 03:06:48.260 align:start position:0% actually using a lot of peer-to-peer networks<03:06:46.520> there's<03:06:47.520> one<03:06:47.729> that<03:06:47.880> is<03:06:47.970> going<03:06:48.180> to 03:06:48.260 --> 03:06:48.270 align:start position:0% networks there's one that is going to 03:06:48.270 --> 03:06:50.840 align:start position:0% networks there's one that is going to our<03:06:48.420> chat<03:06:48.630> network<03:06:48.989> and<03:06:49.399> you<03:06:50.399> know<03:06:50.489> these<03:06:50.670> guys 03:06:50.840 --> 03:06:50.850 align:start position:0% our chat network and you know these guys 03:06:50.850 --> 03:06:53.719 align:start position:0% our chat network and you know these guys have<03:06:51.000> nothing<03:06:51.810> they<03:06:52.619> have<03:06:52.770> no<03:06:52.949> money<03:06:53.159> so 03:06:53.719 --> 03:06:53.729 align:start position:0% have nothing they have no money so 03:06:53.729 --> 03:06:54.950 align:start position:0% have nothing they have no money so they're<03:06:53.880> just<03:06:54.090> doing<03:06:54.270> all<03:06:54.569> this 03:06:54.950 --> 03:06:54.960 align:start position:0% they're just doing all this 03:06:54.960 --> 03:06:57.710 align:start position:0% they're just doing all this together<03:06:55.680> they<03:06:56.010> you<03:06:56.369> can<03:06:56.550> find<03:06:56.760> it<03:06:56.909> on<03:06:57.359> Twitter 03:06:57.710 --> 03:06:57.720 align:start position:0% together they you can find it on Twitter 03:06:57.720 --> 03:07:00.319 align:start position:0% together they you can find it on Twitter it's<03:06:57.930> called<03:06:58.170> logic<03:06:58.529> Network<03:06:58.920> and<03:06:59.220> this<03:07:00.180> is 03:07:00.319 --> 03:07:00.329 align:start position:0% it's called logic Network and this is 03:07:00.329 --> 03:07:02.200 align:start position:0% it's called logic Network and this is what<03:07:00.449> we<03:07:00.569> do<03:07:00.689> is<03:07:00.840> use<03:07:00.989> a<03:07:01.140> mesh<03:07:01.319> network<03:07:01.350> and 03:07:02.200 --> 03:07:02.210 align:start position:0% what we do is use a mesh network and 03:07:02.210 --> 03:07:04.429 align:start position:0% what we do is use a mesh network and they're<03:07:03.210> just<03:07:03.390> communicating<03:07:03.989> between<03:07:04.079> them 03:07:04.429 --> 03:07:04.439 align:start position:0% they're just communicating between them 03:07:04.439 --> 03:07:06.769 align:start position:0% they're just communicating between them and<03:07:04.949> also<03:07:05.159> they're<03:07:05.399> listening<03:07:05.729> for<03:07:05.789> Bitcoin 03:07:06.769 --> 03:07:06.779 align:start position:0% and also they're listening for Bitcoin 03:07:06.779 --> 03:07:09.469 align:start position:0% and also they're listening for Bitcoin transactions<03:07:07.350> and<03:07:07.770> I<03:07:07.979> find<03:07:08.220> this<03:07:08.310> super<03:07:08.489> super 03:07:09.469 --> 03:07:09.479 align:start position:0% transactions and I find this super super 03:07:09.479 --> 03:07:11.210 align:start position:0% transactions and I find this super super amazing<03:07:10.319> that<03:07:10.439> these<03:07:10.529> guys<03:07:10.710> are<03:07:10.920> doing<03:07:11.010> this 03:07:11.210 --> 03:07:11.220 align:start position:0% amazing that these guys are doing this 03:07:11.220 --> 03:07:13.219 align:start position:0% amazing that these guys are doing this news<03:07:11.789> because<03:07:12.210> you<03:07:12.479> know<03:07:13.050> they're<03:07:13.199> just 03:07:13.219 --> 03:07:13.229 align:start position:0% news because you know they're just 03:07:13.229 --> 03:07:16.010 align:start position:0% news because you know they're just trying<03:07:13.800> to<03:07:13.920> find<03:07:14.159> ways<03:07:14.729> of<03:07:14.939> communicating<03:07:15.479> and 03:07:16.010 --> 03:07:16.020 align:start position:0% trying to find ways of communicating and 03:07:16.020 --> 03:07:19.630 align:start position:0% trying to find ways of communicating and avoiding<03:07:16.829> the<03:07:17.520> government<03:07:18.060> because 03:07:19.630 --> 03:07:19.640 align:start position:0% avoiding the government because 03:07:19.640 --> 03:07:23.059 align:start position:0% avoiding the government because personally<03:07:20.640> I<03:07:20.789> was<03:07:21.890> targeted<03:07:22.890> by<03:07:23.010> the 03:07:23.059 --> 03:07:23.069 align:start position:0% personally I was targeted by the 03:07:23.069 --> 03:07:26.000 align:start position:0% personally I was targeted by the government<03:07:23.609> in<03:07:24.119> Venezuela<03:07:24.600> when<03:07:24.840> I<03:07:24.869> was<03:07:25.109> doing 03:07:26.000 --> 03:07:26.010 align:start position:0% government in Venezuela when I was doing 03:07:26.010 --> 03:07:29.990 align:start position:0% government in Venezuela when I was doing a<03:07:26.279> revolution<03:07:27.090> kind<03:07:27.390> of<03:07:27.510> and<03:07:28.609> like<03:07:29.609> they<03:07:29.789> look 03:07:29.990 --> 03:07:30.000 align:start position:0% a revolution kind of and like they look 03:07:30.000 --> 03:07:33.170 align:start position:0% a revolution kind of and like they look on<03:07:30.390> my<03:07:30.600> social<03:07:31.109> media<03:07:31.590> they<03:07:32.550> become<03:07:32.850> all<03:07:33.000> my 03:07:33.170 --> 03:07:33.180 align:start position:0% on my social media they become all my 03:07:33.180 --> 03:07:36.469 align:start position:0% on my social media they become all my stuff<03:07:33.449> so<03:07:33.619> it's<03:07:34.619> like<03:07:34.909> very<03:07:35.909> important<03:07:36.329> that 03:07:36.469 --> 03:07:36.479 align:start position:0% stuff so it's like very important that 03:07:36.479 --> 03:07:38.210 align:start position:0% stuff so it's like very important that we<03:07:36.630> use<03:07:36.869> these<03:07:37.199> kind<03:07:37.380> of<03:07:37.500> networks<03:07:37.920> in<03:07:38.069> order 03:07:38.210 --> 03:07:38.220 align:start position:0% we use these kind of networks in order 03:07:38.220 --> 03:07:40.670 align:start position:0% we use these kind of networks in order to<03:07:38.340> communicate<03:07:38.930> even<03:07:39.930> more<03:07:40.170> it's<03:07:40.289> important 03:07:40.670 --> 03:07:40.680 align:start position:0% to communicate even more it's important 03:07:40.680 --> 03:07:42.319 align:start position:0% to communicate even more it's important in<03:07:40.800> these<03:07:40.920> countries<03:07:41.250> where<03:07:41.640> we<03:07:41.909> don't<03:07:42.090> have 03:07:42.319 --> 03:07:42.329 align:start position:0% in these countries where we don't have 03:07:42.329 --> 03:07:47.480 align:start position:0% in these countries where we don't have freedom 03:07:47.480 --> 03:07:47.490 align:start position:0% 03:07:47.490 --> 03:07:49.940 align:start position:0% it's<03:07:48.060> more<03:07:48.270> like<03:07:48.420> a<03:07:48.450> question<03:07:48.770> is<03:07:49.770> it 03:07:49.940 --> 03:07:49.950 align:start position:0% it's more like a question is it 03:07:49.950 --> 03:07:51.920 align:start position:0% it's more like a question is it important<03:07:50.430> for<03:07:50.640> these<03:07:50.729> countries<03:07:50.970> that<03:07:51.540> these 03:07:51.920 --> 03:07:51.930 align:start position:0% important for these countries that these 03:07:51.930 --> 03:07:57.469 align:start position:0% important for these countries that these systems<03:07:52.320> work<03:07:52.800> on<03:07:53.130> mobile<03:07:54.560> 100%<03:07:55.560> because<03:07:56.479> they 03:07:57.469 --> 03:07:57.479 align:start position:0% systems work on mobile 100% because they 03:07:57.479 --> 03:07:59.000 align:start position:0% systems work on mobile 100% because they don't<03:07:57.660> have<03:07:57.750> computers<03:07:58.170> how<03:07:58.380> much<03:07:58.530> does<03:07:58.979> it 03:07:59.000 --> 03:07:59.010 align:start position:0% don't have computers how much does it 03:07:59.010 --> 03:08:02.840 align:start position:0% don't have computers how much does it cost<03:07:59.130> the<03:07:59.340> computer<03:07:59.700> 500<03:08:00.270> $700<03:08:01.160> $800<03:08:02.160> and<03:08:02.400> the 03:08:02.840 --> 03:08:02.850 align:start position:0% cost the computer 500 $700 $800 and the 03:08:02.850 --> 03:08:06.350 align:start position:0% cost the computer 500 $700 $800 and the mobile<03:08:03.150> phone<03:08:03.330> in<03:08:03.479> Casa<03:08:03.690> anyone<03:08:04.350> $80<03:08:04.950> $90<03:08:05.700> so 03:08:06.350 --> 03:08:06.360 align:start position:0% mobile phone in Casa anyone $80 $90 so 03:08:06.360 --> 03:08:09.260 align:start position:0% mobile phone in Casa anyone $80 $90 so yes<03:08:06.810> it<03:08:07.200> is<03:08:07.260> super<03:08:07.800> important<03:08:08.280> and<03:08:08.520> also<03:08:08.880> in 03:08:09.260 --> 03:08:09.270 align:start position:0% yes it is super important and also in 03:08:09.270 --> 03:08:11.630 align:start position:0% yes it is super important and also in Africa<03:08:09.600> in<03:08:10.170> Africa<03:08:10.530> the<03:08:10.710> African<03:08:11.070> Regency<03:08:11.490> is 03:08:11.630 --> 03:08:11.640 align:start position:0% Africa in Africa the African Regency is 03:08:11.640 --> 03:08:13.100 align:start position:0% Africa in Africa the African Regency is super<03:08:12.030> important<03:08:12.420> that<03:08:12.450> we<03:08:12.630> have<03:08:12.780> these<03:08:12.870> kind 03:08:13.100 --> 03:08:13.110 align:start position:0% super important that we have these kind 03:08:13.110 --> 03:08:20.690 align:start position:0% super important that we have these kind of<03:08:13.140> connections<03:08:13.850> Java<03:08:14.850> 6<03:08:16.250> sorry<03:08:17.250> Java<03:08:17.940> 6<03:08:19.670> yes 03:08:20.690 --> 03:08:20.700 align:start position:0% of connections Java 6 sorry Java 6 yes 03:08:20.700 --> 03:08:23.540 align:start position:0% of connections Java 6 sorry Java 6 yes hundred<03:08:21.300> I'm<03:08:21.840> also<03:08:22.200> we<03:08:22.320> have<03:08:22.500> this<03:08:23.190> kind<03:08:23.400> of 03:08:23.540 --> 03:08:23.550 align:start position:0% hundred I'm also we have this kind of 03:08:23.550 --> 03:08:29.210 align:start position:0% hundred I'm also we have this kind of phones<03:08:24.450> that<03:08:24.840> are<03:08:25.610> very<03:08:27.380> light<03:08:28.380> phones<03:08:28.920> they 03:08:29.210 --> 03:08:29.220 align:start position:0% phones that are very light phones they 03:08:29.220 --> 03:08:33.440 align:start position:0% phones that are very light phones they call<03:08:29.430> it<03:08:30.200> they're<03:08:31.200> reaching<03:08:31.470> like<03:08:31.950> $40<03:08:32.729> 50<03:08:33.270> RS 03:08:33.440 --> 03:08:33.450 align:start position:0% call it they're reaching like $40 50 RS 03:08:33.450 --> 03:08:34.219 align:start position:0% call it they're reaching like $40 50 RS phones 03:08:34.219 --> 03:08:34.229 align:start position:0% phones 03:08:34.229 --> 03:08:37.640 align:start position:0% phones Chinese<03:08:34.950> phones<03:08:35.900> yeah<03:08:36.900> that's<03:08:37.140> what<03:08:37.530> people 03:08:37.640 --> 03:08:37.650 align:start position:0% Chinese phones yeah that's what people 03:08:37.650 --> 03:08:41.780 align:start position:0% Chinese phones yeah that's what people are<03:08:37.830> using<03:08:38.070> currently<03:08:40.160> doing<03:08:41.160> a<03:08:41.580> lot<03:08:41.670> of 03:08:41.780 --> 03:08:41.790 align:start position:0% are using currently doing a lot of 03:08:41.790 --> 03:08:44.690 align:start position:0% are using currently doing a lot of mobile<03:08:41.940> stuff<03:08:42.270> Network<03:08:42.780> glue<03:08:43.080> worth<03:08:43.770> in 03:08:44.690 --> 03:08:44.700 align:start position:0% mobile stuff Network glue worth in 03:08:44.700 --> 03:08:48.400 align:start position:0% mobile stuff Network glue worth in Ecuador<03:08:45.060> Peru<03:08:45.390> big<03:08:46.170> mobile<03:08:46.770> stuff<03:08:46.950> there<03:08:47.400> and 03:08:48.400 --> 03:08:48.410 align:start position:0% Ecuador Peru big mobile stuff there and 03:08:48.410 --> 03:08:52.660 align:start position:0% Ecuador Peru big mobile stuff there and actually<03:08:49.410> the<03:08:49.650> issue<03:08:49.770> is<03:08:50.040> auto<03:08:50.580> updating 03:08:52.660 --> 03:08:52.670 align:start position:0% actually the issue is auto updating 03:08:52.670 --> 03:08:56.480 align:start position:0% actually the issue is auto updating whatsoever<03:08:53.670> yes<03:08:54.060> there's<03:08:54.750> some<03:08:55.490> sometimes 03:08:56.480 --> 03:08:56.490 align:start position:0% whatsoever yes there's some sometimes 03:08:56.490 --> 03:08:57.890 align:start position:0% whatsoever yes there's some sometimes like<03:08:56.700> different<03:08:57.479> there's<03:08:57.630> like<03:08:57.780> different 03:08:57.890 --> 03:08:57.900 align:start position:0% like different there's like different 03:08:57.900 --> 03:08:59.780 align:start position:0% like different there's like different firewall<03:08:58.530> like<03:08:58.770> this<03:08:59.010> actually<03:08:59.190> happened<03:08:59.640> in 03:08:59.780 --> 03:08:59.790 align:start position:0% firewall like this actually happened in 03:08:59.790 --> 03:09:01.370 align:start position:0% firewall like this actually happened in real<03:08:59.820> life<03:09:00.210> like<03:09:00.420> we<03:09:00.810> were<03:09:00.930> about<03:09:01.110> to<03:09:01.260> do<03:09:01.350> a 03:09:01.370 --> 03:09:01.380 align:start position:0% real life like we were about to do a 03:09:01.380 --> 03:09:02.751 align:start position:0% real life like we were about to do a deployment<03:09:01.740> and<03:09:02.160> it 03:09:02.751 --> 03:09:02.761 align:start position:0% deployment and it 03:09:02.761 --> 03:09:04.610 align:start position:0% deployment and it or<03:09:03.000> enjoy<03:09:03.120> training<03:09:03.450> and<03:09:04.051> then<03:09:04.261> like<03:09:04.410> you<03:09:04.591> know 03:09:04.610 --> 03:09:04.620 align:start position:0% or enjoy training and then like you know 03:09:04.620 --> 03:09:06.081 align:start position:0% or enjoy training and then like you know some<03:09:04.950> house<03:09:05.131> some<03:09:05.551> of<03:09:05.671> the<03:09:05.730> phones<03:09:05.940> had 03:09:06.081 --> 03:09:06.091 align:start position:0% some house some of the phones had 03:09:06.091 --> 03:09:08.150 align:start position:0% some house some of the phones had updated<03:09:06.511> select<03:09:06.841> Android<03:09:07.620> ten<03:09:07.860> or<03:09:08.040> whatever 03:09:08.150 --> 03:09:08.160 align:start position:0% updated select Android ten or whatever 03:09:08.160 --> 03:09:11.121 align:start position:0% updated select Android ten or whatever might<03:09:08.551> go<03:09:09.181> to<03:09:09.301> us<03:09:09.450> they're<03:09:09.931> like<03:09:10.080> didn't<03:09:10.410> they 03:09:11.121 --> 03:09:11.131 align:start position:0% might go to us they're like didn't they 03:09:11.131 --> 03:09:13.280 align:start position:0% might go to us they're like didn't they have<03:09:11.311> added<03:09:11.881> some<03:09:12.061> new<03:09:12.181> firewall<03:09:12.690> things<03:09:13.021> so 03:09:13.280 --> 03:09:13.290 align:start position:0% have added some new firewall things so 03:09:13.290 --> 03:09:14.720 align:start position:0% have added some new firewall things so then<03:09:13.440> you<03:09:13.591> might<03:09:13.740> then<03:09:14.131> like<03:09:14.370> to<03:09:14.521> stay<03:09:14.671> to 03:09:14.720 --> 03:09:14.730 align:start position:0% then you might then like to stay to 03:09:14.730 --> 03:09:18.530 align:start position:0% then you might then like to stay to connect<03:09:15.181> to<03:09:15.301> the<03:09:15.421> emptiness<03:09:15.950> that<03:09:17.421> was<03:09:18.421> an 03:09:18.530 --> 03:09:18.540 align:start position:0% connect to the emptiness that was an 03:09:18.540 --> 03:09:23.591 align:start position:0% connect to the emptiness that was an issue 03:09:23.591 --> 03:09:23.601 align:start position:0% 03:09:23.601 --> 03:09:26.600 align:start position:0% for<03:09:24.601> really<03:09:24.930> could<03:09:25.110> be<03:09:25.290> very<03:09:25.530> big<03:09:26.070> so<03:09:26.250> this<03:09:26.430> is 03:09:26.600 --> 03:09:26.610 align:start position:0% for really could be very big so this is 03:09:26.610 --> 03:09:29.030 align:start position:0% for really could be very big so this is holding<03:09:26.970> cosine<03:09:27.360> reduction<03:09:27.870> so<03:09:28.050> that's<03:09:28.290> that 03:09:29.030 --> 03:09:29.040 align:start position:0% holding cosine reduction so that's that 03:09:29.040 --> 03:09:32.450 align:start position:0% holding cosine reduction so that's that that's<03:09:29.340> the<03:09:29.610> point<03:09:29.820> right<03:09:30.061> for<03:09:30.930> me<03:09:31.050> for<03:09:31.380> out<03:09:31.530> of 03:09:32.450 --> 03:09:32.460 align:start position:0% that's the point right for me for out of 03:09:32.460 --> 03:09:33.890 align:start position:0% that's the point right for me for out of this<03:09:32.610> workshop<03:09:33.000> I<03:09:33.150> would<03:09:33.271> like<03:09:33.450> that's<03:09:33.750> like 03:09:33.890 --> 03:09:33.900 align:start position:0% this workshop I would like that's like 03:09:33.900 --> 03:09:35.870 align:start position:0% this workshop I would like that's like the<03:09:34.050> smallest<03:09:34.351> of<03:09:34.740> the<03:09:34.830> things<03:09:35.040> that<03:09:35.311> we<03:09:35.490> have 03:09:35.870 --> 03:09:35.880 align:start position:0% the smallest of the things that we have 03:09:35.880 --> 03:09:38.690 align:start position:0% the smallest of the things that we have to<03:09:36.660> do<03:09:36.840> projects<03:09:37.380> themselves<03:09:37.530> right<03:09:38.130> we're 03:09:38.690 --> 03:09:38.700 align:start position:0% to do projects themselves right we're 03:09:38.700 --> 03:09:40.850 align:start position:0% to do projects themselves right we're just<03:09:38.730> like<03:09:39.061> may<03:09:39.720> finally<03:09:40.230> be<03:09:40.351> censored 03:09:40.850 --> 03:09:40.860 align:start position:0% just like may finally be censored 03:09:40.860 --> 03:09:42.620 align:start position:0% just like may finally be censored Americans<03:09:41.430> but<03:09:41.610> probably<03:09:41.940> is<03:09:42.090> it<03:09:42.240> probably 03:09:42.620 --> 03:09:42.630 align:start position:0% Americans but probably is it probably 03:09:42.630 --> 03:09:43.970 align:start position:0% Americans but probably is it probably there<03:09:42.750> are<03:09:42.870> more<03:09:43.050> things<03:09:43.200> falling<03:09:43.500> in<03:09:43.740> fact 03:09:43.970 --> 03:09:43.980 align:start position:0% there are more things falling in fact 03:09:43.980 --> 03:09:46.970 align:start position:0% there are more things falling in fact like<03:09:44.190> I'm<03:09:44.610> thinking<03:09:44.790> for<03:09:45.120> example<03:09:45.170> okay<03:09:46.170> so<03:09:46.680> I 03:09:46.970 --> 03:09:46.980 align:start position:0% like I'm thinking for example okay so I 03:09:46.980 --> 03:09:49.460 align:start position:0% like I'm thinking for example okay so I am<03:09:47.220> a<03:09:47.311> developer<03:09:47.610> and<03:09:48.120> I<03:09:48.570> want<03:09:48.930> to<03:09:49.050> like<03:09:49.170> create 03:09:49.460 --> 03:09:49.470 align:start position:0% am a developer and I want to like create 03:09:49.470 --> 03:09:51.440 align:start position:0% am a developer and I want to like create for<03:09:49.830> example<03:09:49.890> you<03:09:50.250> know<03:09:50.370> about<03:09:50.521> a<03:09:50.580> lot<03:09:50.730> lately 03:09:51.440 --> 03:09:51.450 align:start position:0% for example you know about a lot lately 03:09:51.450 --> 03:09:53.990 align:start position:0% for example you know about a lot lately where<03:09:52.170> do<03:09:52.351> are<03:09:52.530> you<03:09:52.740> you<03:09:52.980> know<03:09:53.101> do<03:09:53.340> I<03:09:53.430> just<03:09:53.670> run 03:09:53.990 --> 03:09:54.000 align:start position:0% where do are you you know do I just run 03:09:54.000 --> 03:09:57.230 align:start position:0% where do are you you know do I just run at<03:09:54.210> least<03:09:54.740> jumping<03:09:55.740> like<03:09:55.980> whichever<03:09:56.640> project 03:09:57.230 --> 03:09:57.240 align:start position:0% at least jumping like whichever project 03:09:57.240 --> 03:09:59.091 align:start position:0% at least jumping like whichever project has<03:09:57.390> better<03:09:57.690> the<03:09:57.870> foundation<03:09:58.351> of<03:09:58.470> the<03:09:58.561> time<03:09:58.800> or 03:09:59.091 --> 03:09:59.101 align:start position:0% has better the foundation of the time or 03:09:59.101 --> 03:10:01.460 align:start position:0% has better the foundation of the time or is<03:09:59.220> there<03:09:59.370> like<03:09:59.570> sources<03:10:00.570> to<03:10:00.811> move<03:10:00.960> somewhere 03:10:01.460 --> 03:10:01.470 align:start position:0% is there like sources to move somewhere 03:10:01.470 --> 03:10:03.380 align:start position:0% is there like sources to move somewhere is<03:10:01.680> that<03:10:01.860> gonna<03:10:01.980> be<03:10:02.160> a<03:10:02.190> white<03:10:02.460> look<03:10:02.730> report<03:10:03.150> of 03:10:03.380 --> 03:10:03.390 align:start position:0% is that gonna be a white look report of 03:10:03.390 --> 03:10:05.210 align:start position:0% is that gonna be a white look report of like<03:10:03.570> which<03:10:03.840> stack<03:10:04.140> actually<03:10:04.650> works<03:10:04.950> and 03:10:05.210 --> 03:10:05.220 align:start position:0% like which stack actually works and 03:10:05.220 --> 03:10:07.100 align:start position:0% like which stack actually works and works<03:10:05.430> if<03:10:05.610> we<03:10:05.760> scale<03:10:06.150> and<03:10:06.570> like<03:10:06.811> you<03:10:06.960> know 03:10:07.100 --> 03:10:07.110 align:start position:0% works if we scale and like you know 03:10:07.110 --> 03:10:08.330 align:start position:0% works if we scale and like you know where<03:10:07.590> do<03:10:07.740> I<03:10:07.830> go 03:10:08.330 --> 03:10:08.340 align:start position:0% where do I go 03:10:08.340 --> 03:10:11.000 align:start position:0% where do I go orientate<03:10:08.880> myself<03:10:09.110> around<03:10:10.110> how<03:10:10.410> quite<03:10:10.740> great 03:10:11.000 --> 03:10:11.010 align:start position:0% orientate myself around how quite great 03:10:11.010 --> 03:10:13.011 align:start position:0% orientate myself around how quite great news<03:10:11.190> things<03:10:11.521> in<03:10:11.760> any<03:10:12.150> way<03:10:12.300> that<03:10:12.780> actually 03:10:13.011 --> 03:10:13.021 align:start position:0% news things in any way that actually 03:10:13.021 --> 03:10:15.591 align:start position:0% news things in any way that actually works<03:10:13.561> right<03:10:13.980> so<03:10:14.311> for<03:10:14.760> me<03:10:14.910> I<03:10:15.120> know<03:10:15.330> how<03:10:15.540> we 03:10:15.591 --> 03:10:15.601 align:start position:0% works right so for me I know how we 03:10:15.601 --> 03:10:17.360 align:start position:0% works right so for me I know how we would<03:10:15.780> even<03:10:15.930> call<03:10:16.140> that<03:10:16.200> right<03:10:16.680> and<03:10:16.920> maybe<03:10:17.190> you 03:10:17.360 --> 03:10:17.370 align:start position:0% would even call that right and maybe you 03:10:17.370 --> 03:10:18.860 align:start position:0% would even call that right and maybe you guys<03:10:17.610> disagree<03:10:17.970> maybe<03:10:18.180> there<03:10:18.480> is<03:10:18.570> a<03:10:18.601> place<03:10:18.750> in 03:10:18.860 --> 03:10:18.870 align:start position:0% guys disagree maybe there is a place in 03:10:18.870 --> 03:10:20.360 align:start position:0% guys disagree maybe there is a place in the<03:10:19.050> web<03:10:19.200> like<03:10:19.351> that<03:10:19.620> I<03:10:19.800> just<03:10:19.860> don't<03:10:20.220> know 03:10:20.360 --> 03:10:20.370 align:start position:0% the web like that I just don't know 03:10:20.370 --> 03:10:24.110 align:start position:0% the web like that I just don't know about<03:10:20.490> right<03:10:21.061> that<03:10:22.490> death<03:10:23.490> for<03:10:23.730> me<03:10:23.820> would<03:10:23.940> be 03:10:24.110 --> 03:10:24.120 align:start position:0% about right that death for me would be 03:10:24.120 --> 03:10:26.301 align:start position:0% about right that death for me would be interesting<03:10:24.630> but<03:10:24.720> Bunny<03:10:25.050> General<03:10:25.500> might<03:10:25.680> this 03:10:26.301 --> 03:10:26.311 align:start position:0% interesting but Bunny General might this 03:10:26.311 --> 03:10:27.920 align:start position:0% interesting but Bunny General might this is<03:10:26.460> one<03:10:26.670> of<03:10:26.700> my<03:10:26.910> points<03:10:27.090> like<03:10:27.360> this<03:10:27.540> source<03:10:27.780> it 03:10:27.920 --> 03:10:27.930 align:start position:0% is one of my points like this source it 03:10:27.930 --> 03:10:30.801 align:start position:0% is one of my points like this source it through<03:10:28.170> but<03:10:28.440> but<03:10:28.800> bigger<03:10:29.190> one<03:10:29.400> is<03:10:29.640> like<03:10:29.910> who 03:10:30.801 --> 03:10:30.811 align:start position:0% through but but bigger one is like who 03:10:30.811 --> 03:10:33.261 align:start position:0% through but but bigger one is like who has<03:10:30.960> ideas<03:10:31.170> for<03:10:31.530> what<03:10:31.950> is<03:10:32.101> actually<03:10:32.580> only<03:10:32.820> not 03:10:33.261 --> 03:10:33.271 align:start position:0% has ideas for what is actually only not 03:10:33.271 --> 03:10:35.180 align:start position:0% has ideas for what is actually only not only<03:10:33.390> the<03:10:33.811> beauty<03:10:34.021> probably<03:10:34.590> expect<03:10:34.920> right 03:10:35.180 --> 03:10:35.190 align:start position:0% only the beauty probably expect right 03:10:35.190 --> 03:10:37.850 align:start position:0% only the beauty probably expect right thus<03:10:35.370> we<03:10:35.490> be<03:10:35.640> headed<03:10:35.910> for<03:10:35.940> a<03:10:36.150> long<03:10:36.300> time<03:10:36.630> and<03:10:37.021> by 03:10:37.850 --> 03:10:37.860 align:start position:0% thus we be headed for a long time and by 03:10:37.860 --> 03:10:39.770 align:start position:0% thus we be headed for a long time and by the<03:10:37.890> way<03:10:38.070> like<03:10:38.280> I<03:10:38.460> I<03:10:38.790> really<03:10:39.510> like<03:10:39.630> the 03:10:39.770 --> 03:10:39.780 align:start position:0% the way like I I really like the 03:10:39.780 --> 03:10:41.870 align:start position:0% the way like I I really like the Harrises<03:10:40.170> talk<03:10:40.380> that<03:10:40.620> that<03:10:40.890> there<03:10:41.130> was<03:10:41.311> that 03:10:41.870 --> 03:10:41.880 align:start position:0% Harrises talk that that there was that 03:10:41.880 --> 03:10:44.270 align:start position:0% Harrises talk that that there was that there<03:10:42.090> was<03:10:42.300> there<03:10:42.601> was<03:10:42.860> listening<03:10:43.860> that<03:10:44.040> there 03:10:44.270 --> 03:10:44.280 align:start position:0% there was there was listening that there 03:10:44.280 --> 03:10:47.030 align:start position:0% there was there was listening that there was<03:10:44.430> one<03:10:45.000> point<03:10:45.180> six<03:10:45.450> million<03:10:45.690> since<03:10:46.230> 2013 03:10:47.030 --> 03:10:47.040 align:start position:0% was one point six million since 2013 03:10:47.040 --> 03:10:49.341 align:start position:0% was one point six million since 2013 right<03:10:47.370> but<03:10:47.880> that's<03:10:48.030> the<03:10:48.180> money<03:10:48.450> and<03:10:48.840> I'm<03:10:49.170> also 03:10:49.341 --> 03:10:49.351 align:start position:0% right but that's the money and I'm also 03:10:49.351 --> 03:10:51.500 align:start position:0% right but that's the money and I'm also wondering<03:10:49.650> like<03:10:50.160> if<03:10:50.610> you<03:10:50.760> tried<03:10:51.030> counting 03:10:51.500 --> 03:10:51.510 align:start position:0% wondering like if you tried counting 03:10:51.510 --> 03:10:53.500 align:start position:0% wondering like if you tried counting contributors<03:10:52.110> time 03:10:53.500 --> 03:10:53.510 align:start position:0% contributors time 03:10:53.510 --> 03:10:55.360 align:start position:0% contributors time light<03:10:53.750> starts<03:10:54.140> very<03:10:54.319> qualified<03:10:54.649> people<03:10:54.920> so 03:10:55.360 --> 03:10:55.370 align:start position:0% light starts very qualified people so 03:10:55.370 --> 03:10:56.920 align:start position:0% light starts very qualified people so their<03:10:55.550> time<03:10:55.729> is<03:10:55.880> where<03:10:56.090> it<03:10:56.149> belongs<03:10:56.270> so<03:10:56.750> like 03:10:56.920 --> 03:10:56.930 align:start position:0% their time is where it belongs so like 03:10:56.930 --> 03:11:01.000 align:start position:0% their time is where it belongs so like how<03:10:57.140> do<03:10:57.200> we<03:10:57.500> you<03:10:57.890> know<03:10:57.920> met<03:10:58.420> with<03:10:59.420> them<03:10:59.740> who<03:11:00.740> are 03:11:01.000 --> 03:11:01.010 align:start position:0% how do we you know met with them who are 03:11:01.010 --> 03:11:07.360 align:start position:0% how do we you know met with them who are swiping 03:11:07.360 --> 03:11:07.370 align:start position:0% 03:11:07.370 --> 03:11:09.490 align:start position:0% so<03:11:08.240> I<03:11:08.270> don't<03:11:08.540> think<03:11:08.750> what<03:11:08.899> book<03:11:09.050> or<03:11:09.170> Forsman 03:11:09.490 --> 03:11:09.500 align:start position:0% so I don't think what book or Forsman 03:11:09.500 --> 03:11:11.500 align:start position:0% so I don't think what book or Forsman out<03:11:09.620> that<03:11:09.890> much<03:11:10.100> but<03:11:10.670> I<03:11:10.880> think<03:11:11.210> this<03:11:11.359> is 03:11:11.500 --> 03:11:11.510 align:start position:0% out that much but I think this is 03:11:11.510 --> 03:11:12.969 align:start position:0% out that much but I think this is something<03:11:11.689> that<03:11:11.840> lifts<03:11:12.200> me<03:11:12.350> to<03:11:12.470> meet<03:11:12.620> some 03:11:12.969 --> 03:11:12.979 align:start position:0% something that lifts me to meet some 03:11:12.979 --> 03:11:14.200 align:start position:0% something that lifts me to meet some point<03:11:13.250> like<03:11:13.430> kind<03:11:13.670> of<03:11:13.700> like<03:11:13.819> an<03:11:13.970> ordinary 03:11:14.200 --> 03:11:14.210 align:start position:0% point like kind of like an ordinary 03:11:14.210 --> 03:11:16.809 align:start position:0% point like kind of like an ordinary level<03:11:14.779> things<03:11:15.050> because<03:11:15.859> it's<03:11:16.040> not<03:11:16.279> just<03:11:16.609> your 03:11:16.809 --> 03:11:16.819 align:start position:0% level things because it's not just your 03:11:16.819 --> 03:11:19.450 align:start position:0% level things because it's not just your app<03:11:17.180> it's<03:11:17.510> also<03:11:17.689> gonna<03:11:18.410> be<03:11:18.529> sent<03:11:18.890> to<03:11:19.010> G<03:11:19.130> to<03:11:19.250> do 03:11:19.450 --> 03:11:19.460 align:start position:0% app it's also gonna be sent to G to do 03:11:19.460 --> 03:11:23.050 align:start position:0% app it's also gonna be sent to G to do things<03:11:19.850> for<03:11:20.479> example<03:11:21.520> that's<03:11:22.520> a<03:11:22.640> very<03:11:22.939> good 03:11:23.050 --> 03:11:23.060 align:start position:0% things for example that's a very good 03:11:23.060 --> 03:11:24.760 align:start position:0% things for example that's a very good choice<03:11:23.120> if<03:11:23.720> you<03:11:23.899> need<03:11:24.050> to<03:11:24.170> have<03:11:24.319> Street 03:11:24.760 --> 03:11:24.770 align:start position:0% choice if you need to have Street 03:11:24.770 --> 03:11:35.200 align:start position:0% choice if you need to have Street central<03:11:25.399> pub<03:11:25.640> just<03:11:26.439> watching<03:11:33.790> you<03:11:34.790> just<03:11:34.939> want 03:11:35.200 --> 03:11:35.210 align:start position:0% central pub just watching you just want 03:11:35.210 --> 03:11:40.680 align:start position:0% central pub just watching you just want to<03:11:35.270> like<03:11:35.720> be<03:11:35.960> put<03:11:36.170> in<03:11:36.290> place<03:11:36.580> out<03:11:37.580> there 03:11:40.680 --> 03:11:40.690 align:start position:0% 03:11:40.690 --> 03:11:42.961 align:start position:0% investments<03:11:41.591> to<03:11:41.710> understand<03:11:42.070> that<03:11:42.521> you<03:11:42.851> were 03:11:42.961 --> 03:11:42.971 align:start position:0% investments to understand that you were 03:11:42.971 --> 03:11:47.820 align:start position:0% investments to understand that you were not<03:11:43.120> tied<03:11:43.391> to<03:11:44.070> instant<03:11:45.070> change<03:11:46.320> can<03:11:47.320> change<03:11:47.530> or 03:11:47.820 --> 03:11:47.830 align:start position:0% not tied to instant change can change or 03:11:47.830 --> 03:11:49.911 align:start position:0% not tied to instant change can change or nice<03:11:48.221> Main<03:11:48.431> St<03:11:48.521> crisper<03:11:49.210> integration<03:11:49.631> song 03:11:49.911 --> 03:11:49.921 align:start position:0% nice Main St crisper integration song 03:11:49.921 --> 03:11:54.541 align:start position:0% nice Main St crisper integration song things<03:11:50.921> so<03:11:51.221> I<03:11:51.490> think<03:11:52.150> it's<03:11:53.160> something<03:11:54.160> though 03:11:54.541 --> 03:11:54.551 align:start position:0% things so I think it's something though 03:11:54.551 --> 03:11:56.930 align:start position:0% things so I think it's something though and 03:11:56.930 --> 03:11:56.940 align:start position:0% and 03:11:56.940 --> 03:11:59.291 align:start position:0% and we've<03:11:57.931> seen<03:11:58.200> a<03:11:58.230> mobile<03:11:58.591> change<03:11:58.830> because 03:11:59.291 --> 03:11:59.301 align:start position:0% we've seen a mobile change because 03:11:59.301 --> 03:12:03.130 align:start position:0% we've seen a mobile change because absent<03:12:00.301> that<03:12:01.080> means<03:12:01.381> with<03:12:01.591> more 03:12:03.130 --> 03:12:03.140 align:start position:0% absent that means with more 03:12:03.140 --> 03:12:07.050 align:start position:0% absent that means with more sensitive<03:12:03.979> difference<03:12:04.310> rehearsals 03:12:07.050 --> 03:12:07.060 align:start position:0% 03:12:07.060 --> 03:12:09.239 align:start position:0% yeah<03:12:07.629> you<03:12:07.810> want<03:12:07.989> to<03:12:08.020> interpret<03:12:08.350> but<03:12:08.890> just 03:12:09.239 --> 03:12:09.249 align:start position:0% yeah you want to interpret but just 03:12:09.249 --> 03:12:10.739 align:start position:0% yeah you want to interpret but just wanted<03:12:09.520> to<03:12:09.609> say<03:12:09.789> that<03:12:10.029> I'm<03:12:10.270> not<03:12:10.419> even<03:12:10.629> talking 03:12:10.739 --> 03:12:10.749 align:start position:0% wanted to say that I'm not even talking 03:12:10.749 --> 03:12:12.659 align:start position:0% wanted to say that I'm not even talking about<03:12:10.930> dungeons<03:12:11.499> as<03:12:11.680> much<03:12:11.890> because<03:12:12.100> like<03:12:12.430> that 03:12:12.659 --> 03:12:12.669 align:start position:0% about dungeons as much because like that 03:12:12.669 --> 03:12:15.599 align:start position:0% about dungeons as much because like that there<03:12:12.879> are<03:12:13.379> verses<03:12:14.379> for<03:12:14.609> multi-protocol 03:12:15.599 --> 03:12:15.609 align:start position:0% there are verses for multi-protocol 03:12:15.609 --> 03:12:17.609 align:start position:0% there are verses for multi-protocol right<03:12:15.850> right<03:12:16.539> so<03:12:16.810> that<03:12:17.109> I<03:12:17.350> can't<03:12:17.560> imagine 03:12:17.609 --> 03:12:17.619 align:start position:0% right right so that I can't imagine 03:12:17.619 --> 03:12:19.319 align:start position:0% right right so that I can't imagine where<03:12:18.039> I'm<03:12:18.129> going<03:12:18.459> to<03:12:18.549> go<03:12:18.640> on<03:12:18.760> the<03:12:18.879> web<03:12:19.029> like 03:12:19.319 --> 03:12:19.329 align:start position:0% where I'm going to go on the web like 03:12:19.329 --> 03:12:21.329 align:start position:0% where I'm going to go on the web like but<03:12:19.989> I'm<03:12:20.169> talking<03:12:20.409> about<03:12:20.470> like<03:12:20.770> more<03:12:21.129> like 03:12:21.329 --> 03:12:21.339 align:start position:0% but I'm talking about like more like 03:12:21.339 --> 03:12:27.949 align:start position:0% but I'm talking about like more like like<03:12:21.939> new<03:12:22.810> projects<03:12:23.229> like<03:12:23.409> that<03:12:24.539> where<03:12:25.539> I<03:12:25.569> go 03:12:27.949 --> 03:12:27.959 align:start position:0% 03:12:27.959 --> 03:12:33.680 align:start position:0% telegram<03:12:29.100> like<03:12:30.100> get<03:12:30.819> started 03:12:33.680 --> 03:12:33.690 align:start position:0% 03:12:33.690 --> 03:12:36.540 align:start position:0% and<03:12:34.690> it's<03:12:35.021> a<03:12:35.110> discount<03:12:35.470> of<03:12:35.650> some<03:12:36.070> place<03:12:36.370> where 03:12:36.540 --> 03:12:36.550 align:start position:0% and it's a discount of some place where 03:12:36.550 --> 03:12:40.310 align:start position:0% and it's a discount of some place where people<03:12:36.641> go<03:12:36.970> through<03:12:37.120> for<03:12:37.630> new<03:12:37.780> developments<03:12:38.650> I 03:12:40.310 --> 03:12:40.320 align:start position:0% people go through for new developments I 03:12:40.320 --> 03:12:47.150 align:start position:0% people go through for new developments I [Music] 03:12:47.150 --> 03:12:47.160 align:start position:0% 03:12:47.160 --> 03:12:51.870 align:start position:0% just<03:12:48.811> so<03:12:49.811> did<03:12:50.351> I<03:12:50.470> get<03:12:50.710> your<03:12:50.860> question<03:12:51.280> right<03:12:51.460> so 03:12:51.870 --> 03:12:51.880 align:start position:0% just so did I get your question right so 03:12:51.880 --> 03:12:55.520 align:start position:0% just so did I get your question right so your<03:12:52.030> question<03:12:52.391> was<03:12:52.420> I<03:12:52.660> um<03:12:52.960> I<03:12:53.200> think<03:12:53.530> like<03:12:54.420> my 03:12:55.520 --> 03:12:55.530 align:start position:0% your question was I um I think like my 03:12:55.530 --> 03:12:58.290 align:start position:0% your question was I um I think like my application<03:12:56.530> that<03:12:56.800> this<03:12:57.010> tactic<03:12:57.490> works<03:12:57.760> is 03:12:58.290 --> 03:12:58.300 align:start position:0% application that this tactic works is 03:12:58.300 --> 03:12:59.910 align:start position:0% application that this tactic works is that<03:12:58.480> what<03:12:58.601> you<03:12:58.690> were<03:12:58.811> asking<03:12:58.990> or<03:12:59.380> is<03:12:59.590> that<03:12:59.680> I'm 03:12:59.910 --> 03:12:59.920 align:start position:0% that what you were asking or is that I'm 03:12:59.920 --> 03:13:01.650 align:start position:0% that what you were asking or is that I'm thinking<03:13:00.250> about<03:13:00.340> so<03:13:00.700> what<03:13:00.910> is<03:13:01.061> holding<03:13:01.391> me<03:13:01.540> to 03:13:01.650 --> 03:13:01.660 align:start position:0% thinking about so what is holding me to 03:13:01.660 --> 03:13:03.631 align:start position:0% thinking about so what is holding me to the<03:13:01.750> projects<03:13:02.170> back<03:13:02.380> so<03:13:02.710> like<03:13:02.950> if<03:13:03.370> there<03:13:03.550> are 03:13:03.631 --> 03:13:03.641 align:start position:0% the projects back so like if there are 03:13:03.641 --> 03:13:05.131 align:start position:0% the projects back so like if there are more<03:13:03.790> developers<03:13:04.300> building<03:13:04.601> on<03:13:04.750> a<03:13:04.840> smart 03:13:05.131 --> 03:13:05.141 align:start position:0% more developers building on a smart 03:13:05.141 --> 03:13:06.511 align:start position:0% more developers building on a smart developers<03:13:05.500> are<03:13:05.680> going<03:13:05.740> to<03:13:05.891> be<03:13:05.950> contributing 03:13:06.511 --> 03:13:06.521 align:start position:0% developers are going to be contributing 03:13:06.521 --> 03:13:08.341 align:start position:0% developers are going to be contributing and<03:13:06.790> like<03:13:07.000> thinking<03:13:07.360> about<03:13:07.450> barriers<03:13:08.080> for 03:13:08.341 --> 03:13:08.351 align:start position:0% and like thinking about barriers for 03:13:08.351 --> 03:13:10.080 align:start position:0% and like thinking about barriers for developers<03:13:08.891> to<03:13:09.040> use<03:13:09.101> a<03:13:09.340> blank<03:13:09.610> developer 03:13:10.080 --> 03:13:10.090 align:start position:0% developers to use a blank developer 03:13:10.090 --> 03:13:11.580 align:start position:0% developers to use a blank developer recording<03:13:10.540> and<03:13:10.690> knowing<03:13:10.960> what's<03:13:11.170> out<03:13:11.351> it's 03:13:11.580 --> 03:13:11.590 align:start position:0% recording and knowing what's out it's 03:13:11.590 --> 03:13:12.960 align:start position:0% recording and knowing what's out it's like<03:13:11.680> one<03:13:11.891> of<03:13:12.010> them<03:13:12.160> looks<03:13:12.370> like<03:13:12.400> you<03:13:12.880> know 03:13:12.960 --> 03:13:12.970 align:start position:0% like one of them looks like you know 03:13:12.970 --> 03:13:14.520 align:start position:0% like one of them looks like you know that<03:13:13.150> you<03:13:13.300> want<03:13:13.480> to<03:13:13.540> be<03:13:13.750> afternoo<03:13:14.170> like<03:13:14.351> the 03:13:14.520 --> 03:13:14.530 align:start position:0% that you want to be afternoo like the 03:13:14.530 --> 03:13:16.140 align:start position:0% that you want to be afternoo like the stopping<03:13:14.920> in<03:13:15.040> 60<03:13:15.340> to<03:13:15.370> 90<03:13:15.700> minutes<03:13:15.820> and<03:13:16.061> have 03:13:16.140 --> 03:13:16.150 align:start position:0% stopping in 60 to 90 minutes and have 03:13:16.150 --> 03:13:17.850 align:start position:0% stopping in 60 to 90 minutes and have something<03:13:16.391> working<03:13:16.900> but<03:13:17.320> that's<03:13:17.530> not<03:13:17.740> the 03:13:17.850 --> 03:13:17.860 align:start position:0% something working but that's not the 03:13:17.860 --> 03:13:19.320 align:start position:0% something working but that's not the experience<03:13:18.400> that<03:13:18.641> you're<03:13:18.851> going<03:13:18.880> to<03:13:19.030> have<03:13:19.120> to 03:13:19.320 --> 03:13:19.330 align:start position:0% experience that you're going to have to 03:13:19.330 --> 03:13:20.730 align:start position:0% experience that you're going to have to both<03:13:19.540> of<03:13:19.720> those<03:13:19.811> projects<03:13:20.230> at<03:13:20.351> least<03:13:20.530> not<03:13:20.710> in 03:13:20.730 --> 03:13:20.740 align:start position:0% both of those projects at least not in 03:13:20.740 --> 03:13:22.801 align:start position:0% both of those projects at least not in an<03:13:20.950> easy<03:13:21.130> way<03:13:21.370> right<03:13:21.641> so<03:13:21.880> I<03:13:22.180> think<03:13:22.210> where<03:13:22.601> do<03:13:22.750> I 03:13:22.801 --> 03:13:22.811 align:start position:0% an easy way right so I think where do I 03:13:22.811 --> 03:13:24.120 align:start position:0% an easy way right so I think where do I go<03:13:23.021> to<03:13:23.080> orient<03:13:23.500> it<03:13:23.620> myself 03:13:24.120 --> 03:13:24.130 align:start position:0% go to orient it myself 03:13:24.130 --> 03:13:31.040 align:start position:0% go to orient it myself enough<03:13:24.400> research<03:13:24.730> whether<03:13:25.030> it's<03:13:25.480> myself 03:13:31.040 --> 03:13:31.050 align:start position:0% 03:13:31.050 --> 03:13:33.630 align:start position:0% because<03:13:32.050> usually<03:13:32.439> you<03:13:32.830> are<03:13:32.890> trying<03:13:33.279> to<03:13:33.399> lock 03:13:33.630 --> 03:13:33.640 align:start position:0% because usually you are trying to lock 03:13:33.640 --> 03:13:37.180 align:start position:0% because usually you are trying to lock the<03:13:34.180> information<03:13:34.840> and<03:13:35.050> this<03:13:35.170> is 03:13:37.180 --> 03:13:37.190 align:start position:0% the information and this is 03:13:37.190 --> 03:13:38.490 align:start position:0% the information and this is [Music] 03:13:38.490 --> 03:13:38.500 align:start position:0% [Music] 03:13:38.500 --> 03:13:42.120 align:start position:0% [Music] my<03:13:39.760> problem<03:13:40.760> quite<03:13:40.940> developers 03:13:42.120 --> 03:13:42.130 align:start position:0% my problem quite developers 03:13:42.130 --> 03:13:47.710 align:start position:0% my problem quite developers which<03:13:42.790> have<03:13:43.029> been<03:13:43.060> pruned<03:13:43.479> away 03:13:47.710 --> 03:13:47.720 align:start position:0% 03:13:47.720 --> 03:13:54.469 align:start position:0% monetization<03:13:48.720> a<03:13:52.490> little<03:13:53.490> confused<03:13:54.240> by<03:13:54.450> the 03:13:54.469 --> 03:13:54.479 align:start position:0% monetization a little confused by the 03:13:54.479 --> 03:13:57.350 align:start position:0% monetization a little confused by the question<03:13:54.689> or<03:13:55.680> extra<03:13:56.400> the<03:13:56.520> whole<03:13:56.760> thing<03:13:57.180> or 03:13:57.350 --> 03:13:57.360 align:start position:0% question or extra the whole thing or 03:13:57.360 --> 03:13:59.480 align:start position:0% question or extra the whole thing or read<03:13:57.479> history<03:13:57.750> of<03:13:58.050> discussing<03:13:58.410> the<03:13:58.770> yeah 03:13:59.480 --> 03:13:59.490 align:start position:0% read history of discussing the yeah 03:13:59.490 --> 03:14:05.890 align:start position:0% read history of discussing the yeah because<03:13:59.760> I<03:14:00.060> hear<03:14:00.360> this<03:14:00.540> because<03:14:01.229> it<03:14:01.530> says 03:14:05.890 --> 03:14:05.900 align:start position:0% 03:14:05.900 --> 03:14:09.920 align:start position:0% sorry<03:14:06.900> for<03:14:07.170> we're<03:14:07.460> attitude<03:14:08.460> like<03:14:08.640> I<03:14:09.180> was<03:14:09.900> just 03:14:09.920 --> 03:14:09.930 align:start position:0% sorry for we're attitude like I was just 03:14:09.930 --> 03:14:12.410 align:start position:0% sorry for we're attitude like I was just curious<03:14:10.229> about<03:14:10.439> what<03:14:10.880> we<03:14:11.880> should<03:14:11.910> like<03:14:12.180> what 03:14:12.410 --> 03:14:12.420 align:start position:0% curious about what we should like what 03:14:12.420 --> 03:14:15.020 align:start position:0% curious about what we should like what the<03:14:12.600> poll<03:14:12.810> was<03:14:13.380> -<03:14:13.710> yeah<03:14:14.100> I<03:14:14.370> feel<03:14:14.580> like<03:14:14.640> right 03:14:15.020 --> 03:14:15.030 align:start position:0% the poll was - yeah I feel like right 03:14:15.030 --> 03:14:16.820 align:start position:0% the poll was - yeah I feel like right now<03:14:15.210> really 03:14:16.820 --> 03:14:16.830 align:start position:0% now really 03:14:16.830 --> 03:14:19.770 align:start position:0% now really Chavez<03:14:17.830> video<03:14:18.070> to<03:14:18.550> just<03:14:18.790> travel<03:14:19.000> to<03:14:19.240> just<03:14:19.540> like 03:14:19.770 --> 03:14:19.780 align:start position:0% Chavez video to just travel to just like 03:14:19.780 --> 03:14:21.720 align:start position:0% Chavez video to just travel to just like debrief<03:14:20.320> I'm<03:14:20.561> gonna<03:14:20.680> be<03:14:20.771> this<03:14:20.891> mess<03:14:21.130> but<03:14:21.490> if 03:14:21.720 --> 03:14:21.730 align:start position:0% debrief I'm gonna be this mess but if 03:14:21.730 --> 03:14:25.080 align:start position:0% debrief I'm gonna be this mess but if people<03:14:21.880> like<03:14:23.190> no<03:14:24.190> no<03:14:24.490> I'm<03:14:24.550> sorry 03:14:25.080 --> 03:14:25.090 align:start position:0% people like no no I'm sorry 03:14:25.090 --> 03:14:29.610 align:start position:0% people like no no I'm sorry yeah<03:14:25.720> I'm<03:14:25.870> just<03:14:25.990> trying<03:14:26.170> to<03:14:26.320> like<03:14:26.500> Congrats 03:14:29.610 --> 03:14:29.620 align:start position:0% 03:14:29.620 --> 03:14:31.470 align:start position:0% I<03:14:29.760> do<03:14:30.760> you<03:14:30.851> think<03:14:31.030> that<03:14:31.120> people<03:14:31.240> just<03:14:31.420> need 03:14:31.470 --> 03:14:31.480 align:start position:0% I do you think that people just need 03:14:31.480 --> 03:14:33.840 align:start position:0% I do you think that people just need better<03:14:31.660> documentation 03:14:33.840 --> 03:14:33.850 align:start position:0% better documentation 03:14:33.850 --> 03:14:37.099 align:start position:0% better documentation to<03:14:34.119> answer<03:14:34.479> your<03:14:34.630> question<03:14:35.170> about<03:14:35.909> 7:45 03:14:37.099 --> 03:14:37.109 align:start position:0% to answer your question about 7:45 03:14:37.109 --> 03:14:39.149 align:start position:0% to answer your question about 7:45 fact-finding<03:14:38.109> Commission<03:14:38.290> and<03:14:38.770> I<03:14:39.010> actually 03:14:39.149 --> 03:14:39.159 align:start position:0% fact-finding Commission and I actually 03:14:39.159 --> 03:14:41.010 align:start position:0% fact-finding Commission and I actually don't<03:14:39.640> know<03:14:39.880> this<03:14:40.119> is<03:14:40.270> why<03:14:40.449> I'm<03:14:40.600> asking 03:14:41.010 --> 03:14:41.020 align:start position:0% don't know this is why I'm asking 03:14:41.020 --> 03:14:42.840 align:start position:0% don't know this is why I'm asking like<03:14:41.290> you<03:14:41.500> know<03:14:41.649> season<03:14:41.979> to<03:14:42.069> me<03:14:42.189> to<03:14:42.310> people 03:14:42.840 --> 03:14:42.850 align:start position:0% like you know season to me to people 03:14:42.850 --> 03:14:48.599 align:start position:0% like you know season to me to people that's<03:14:43.000> like<03:14:43.380> this<03:14:44.380> really<03:14:44.680> is<03:14:47.430> is<03:14:48.430> it 03:14:48.599 --> 03:14:48.609 align:start position:0% that's like this really is is it 03:14:48.609 --> 03:14:50.429 align:start position:0% that's like this really is is it worrisome<03:14:49.119> that<03:14:49.359> like<03:14:49.510> the<03:14:49.720> barrier<03:14:50.140> to<03:14:50.380> entry 03:14:50.429 --> 03:14:50.439 align:start position:0% worrisome that like the barrier to entry 03:14:50.439 --> 03:14:52.080 align:start position:0% worrisome that like the barrier to entry and<03:14:50.739> I<03:14:50.800> like<03:14:50.920> work<03:14:51.130> on<03:14:51.310> these<03:14:51.520> things<03:14:51.790> is<03:14:52.060> very 03:14:52.080 --> 03:14:52.090 align:start position:0% and I like work on these things is very 03:14:52.090 --> 03:14:55.590 align:start position:0% and I like work on these things is very I<03:14:52.810> was<03:14:53.319> like<03:14:53.439> a<03:14:53.560> sort<03:14:54.399> of<03:14:54.489> like<03:14:54.670> a<03:14:55.060> privileged 03:14:55.590 --> 03:14:55.600 align:start position:0% I was like a sort of like a privileged 03:14:55.600 --> 03:14:58.680 align:start position:0% I was like a sort of like a privileged feeling 03:14:58.680 --> 03:14:58.690 align:start position:0% 03:14:58.690 --> 03:15:01.500 align:start position:0% why<03:14:59.320> why<03:14:59.620> provisioning<03:15:00.311> it's<03:15:00.700> the<03:15:00.851> closing 03:15:01.500 --> 03:15:01.510 align:start position:0% why why provisioning it's the closing 03:15:01.510 --> 03:15:02.820 align:start position:0% why why provisioning it's the closing minutes<03:15:01.660> and<03:15:02.021> they're<03:15:02.141> everything<03:15:02.470> is<03:15:02.680> like 03:15:02.820 --> 03:15:02.830 align:start position:0% minutes and they're everything is like 03:15:02.830 --> 03:15:04.980 align:start position:0% minutes and they're everything is like has<03:15:03.070> really<03:15:03.430> big<03:15:03.670> words<03:15:04.000> I<03:15:04.330> feel<03:15:04.540> like<03:15:04.690> there 03:15:04.980 --> 03:15:04.990 align:start position:0% has really big words I feel like there 03:15:04.990 --> 03:15:06.720 align:start position:0% has really big words I feel like there are<03:15:05.080> a<03:15:05.110> lot<03:15:05.290> a<03:15:05.320> lot<03:15:05.620> of<03:15:05.680> it<03:15:05.830> we've<03:15:06.400> had<03:15:06.430> this 03:15:06.720 --> 03:15:06.730 align:start position:0% are a lot a lot of it we've had this 03:15:06.730 --> 03:15:12.340 align:start position:0% are a lot a lot of it we've had this discussion<03:15:06.940> I<03:15:08.340> had<03:15:09.340> this<03:15:09.460> is<03:15:09.610> settled 03:15:12.340 --> 03:15:12.350 align:start position:0% 03:15:12.350 --> 03:15:14.380 align:start position:0% look<03:15:13.159> yeah<03:15:13.430> go<03:15:13.640> ahead<03:15:13.669> in<03:15:13.939> the<03:15:14.029> vacuum 03:15:14.380 --> 03:15:14.390 align:start position:0% look yeah go ahead in the vacuum 03:15:14.390 --> 03:15:18.969 align:start position:0% look yeah go ahead in the vacuum cocktail<03:15:14.810> hi<03:15:15.279> so<03:15:16.279> I<03:15:16.550> always<03:15:17.499> thought<03:15:18.499> it<03:15:18.770> gets 03:15:18.969 --> 03:15:18.979 align:start position:0% cocktail hi so I always thought it gets 03:15:18.979 --> 03:15:20.619 align:start position:0% cocktail hi so I always thought it gets to<03:15:19.069> have<03:15:19.189> a<03:15:19.220> lot<03:15:19.339> of<03:15:19.369> it<03:15:19.579> works<03:15:19.760> cause<03:15:20.300> really 03:15:20.619 --> 03:15:20.629 align:start position:0% to have a lot of it works cause really 03:15:20.629 --> 03:15:22.119 align:start position:0% to have a lot of it works cause really complicated<03:15:21.140> that<03:15:21.379> were<03:15:21.560> starting<03:15:21.859> out<03:15:21.979> with 03:15:22.119 --> 03:15:22.129 align:start position:0% complicated that were starting out with 03:15:22.129 --> 03:15:24.189 align:start position:0% complicated that were starting out with a<03:15:22.249> factor<03:15:22.609> so<03:15:23.239> if<03:15:23.390> you<03:15:23.479> can<03:15:23.600> dump<03:15:23.779> into<03:15:23.959> how<03:15:24.169> to 03:15:24.189 --> 03:15:24.199 align:start position:0% a factor so if you can dump into how to 03:15:24.199 --> 03:15:26.780 align:start position:0% a factor so if you can dump into how to use<03:15:24.729> significant<03:15:25.729> lessons 03:15:26.780 --> 03:15:26.790 align:start position:0% use significant lessons 03:15:26.790 --> 03:15:28.750 align:start position:0% use significant lessons but<03:15:26.970> it's<03:15:27.149> not<03:15:27.330> going<03:15:27.689> to 03:15:28.750 --> 03:15:28.760 align:start position:0% but it's not going to 03:15:28.760 --> 03:15:31.030 align:start position:0% but it's not going to so<03:15:29.660> that<03:15:29.930> then<03:15:30.110> it's<03:15:30.260> like<03:15:30.470> the<03:15:30.680> minutes<03:15:30.950> of 03:15:31.030 --> 03:15:31.040 align:start position:0% so that then it's like the minutes of 03:15:31.040 --> 03:15:33.820 align:start position:0% so that then it's like the minutes of documentation<03:15:31.780> it's<03:15:32.780> an<03:15:33.170> occupational 03:15:33.820 --> 03:15:33.830 align:start position:0% documentation it's an occupational 03:15:33.830 --> 03:15:36.670 align:start position:0% documentation it's an occupational training<03:15:33.950> so<03:15:34.880> it's<03:15:35.080> a<03:15:36.080> lot<03:15:36.380> of<03:15:36.470> it<03:15:36.560> like 03:15:36.670 --> 03:15:36.680 align:start position:0% training so it's a lot of it like 03:15:36.680 --> 03:15:38.710 align:start position:0% training so it's a lot of it like there's<03:15:37.010> a<03:15:37.070> lot<03:15:37.490> of<03:15:37.760> stuff<03:15:38.210> you<03:15:38.240> need<03:15:38.510> to<03:15:38.570> know 03:15:38.710 --> 03:15:38.720 align:start position:0% there's a lot of stuff you need to know 03:15:38.720 --> 03:15:42.700 align:start position:0% there's a lot of stuff you need to know who<03:15:39.200> is<03:15:39.350> he<03:15:39.470> a<03:15:39.500> secret<03:15:39.830> document<03:15:39.950> did<03:15:40.460> but<03:15:41.710> you 03:15:42.700 --> 03:15:42.710 align:start position:0% who is he a secret document did but you 03:15:42.710 --> 03:15:45.640 align:start position:0% who is he a secret document did but you have<03:15:42.950> to<03:15:43.100> train<03:15:43.310> your<03:15:43.460> transaction<03:15:44.650> first 03:15:45.640 --> 03:15:45.650 align:start position:0% have to train your transaction first 03:15:45.650 --> 03:15:47.260 align:start position:0% have to train your transaction first thing<03:15:45.890> I<03:15:46.100> think<03:15:46.400> one<03:15:46.550> thing<03:15:46.700> in<03:15:46.850> New<03:15:47.030> Year's 03:15:47.260 --> 03:15:47.270 align:start position:0% thing I think one thing in New Year's 03:15:47.270 --> 03:15:50.620 align:start position:0% thing I think one thing in New Year's and<03:15:47.870> highlight<03:15:48.229> areas<03:15:48.620> of<03:15:48.880> knowledge<03:15:49.880> in 03:15:50.620 --> 03:15:50.630 align:start position:0% and highlight areas of knowledge in 03:15:50.630 --> 03:16:20.000 align:start position:0% and highlight areas of knowledge in Interlaken 03:16:20.000 --> 03:16:20.010 align:start position:0% 03:16:20.010 --> 03:16:24.120 align:start position:0% one<03:16:21.010> problem<03:16:21.490> that<03:16:21.520> I<03:16:21.760> think<03:16:21.940> is<03:16:22.740> pretty<03:16:23.740> core 03:16:24.120 --> 03:16:24.130 align:start position:0% one problem that I think is pretty core 03:16:24.130 --> 03:16:27.890 align:start position:0% one problem that I think is pretty core to<03:16:24.430> the<03:16:24.610> whole<03:16:24.820> issue<03:16:24.970> is<03:16:25.270> that<03:16:25.710> p2p<03:16:26.850> just 03:16:27.890 --> 03:16:27.900 align:start position:0% to the whole issue is that p2p just 03:16:27.900 --> 03:16:31.620 align:start position:0% to the whole issue is that p2p just doesn't<03:16:28.900> seem<03:16:29.200> to<03:16:29.380> be<03:16:29.530> able<03:16:29.710> to<03:16:29.920> just<03:16:30.300> pick<03:16:31.300> a 03:16:31.620 --> 03:16:31.630 align:start position:0% doesn't seem to be able to just pick a 03:16:31.630 --> 03:16:34.680 align:start position:0% doesn't seem to be able to just pick a single<03:16:32.440> horse<03:16:32.800> and<03:16:33.040> like<03:16:33.190> go<03:16:33.430> with<03:16:33.640> it<03:16:33.820> so 03:16:34.680 --> 03:16:34.690 align:start position:0% single horse and like go with it so 03:16:34.690 --> 03:16:39.440 align:start position:0% single horse and like go with it so there's<03:16:34.930> like<03:16:35.320> people<03:16:35.740> are<03:16:38.070> specific 03:16:39.440 --> 03:16:39.450 align:start position:0% there's like people are specific 03:16:39.450 --> 03:16:47.360 align:start position:0% there's like people are specific networks<03:16:40.450> and<03:16:40.720> wind<03:16:40.960> are<03:16:42.210> incompatible<03:16:43.210> and 03:16:47.360 --> 03:16:47.370 align:start position:0% 03:16:47.370 --> 03:16:49.830 align:start position:0% communism<03:16:48.370> right<03:16:48.700> like<03:16:48.940> I<03:16:48.970> mean<03:16:49.210> everybody 03:16:49.830 --> 03:16:49.840 align:start position:0% communism right like I mean everybody 03:16:49.840 --> 03:16:51.600 align:start position:0% communism right like I mean everybody was<03:16:49.960> into<03:16:50.260> communism<03:16:50.800> Vegas<03:16:51.070> reading<03:16:51.430> to 03:16:51.600 --> 03:16:51.610 align:start position:0% was into communism Vegas reading to 03:16:51.610 --> 03:16:54.600 align:start position:0% was into communism Vegas reading to communism<03:16:52.030> but<03:16:52.680> you<03:16:53.680> can<03:16:54.130> still<03:16:54.370> totally 03:16:54.600 --> 03:16:54.610 align:start position:0% communism but you can still totally 03:16:54.610 --> 03:16:57.030 align:start position:0% communism but you can still totally disagree<03:16:55.330> about<03:16:55.510> you<03:16:55.900> know<03:16:56.050> like<03:16:56.260> trance<03:16:56.830> Q 03:16:57.030 --> 03:16:57.040 align:start position:0% disagree about you know like trance Q 03:16:57.040 --> 03:17:00.900 align:start position:0% disagree about you know like trance Q over<03:16:57.280> you<03:16:57.520> know<03:16:57.610> like<03:16:57.970> it's<03:16:59.520> they<03:17:00.520> just<03:17:00.760> don't 03:17:00.900 --> 03:17:00.910 align:start position:0% over you know like it's they just don't 03:17:00.910 --> 03:17:02.310 align:start position:0% over you know like it's they just don't get<03:17:01.030> along<03:17:01.180> right<03:17:01.510> and<03:17:01.720> turn<03:17:01.810> on<03:17:01.930> you<03:17:02.020> I<03:17:02.050> feel 03:17:02.310 --> 03:17:02.320 align:start position:0% get along right and turn on you I feel 03:17:02.320 --> 03:17:04.260 align:start position:0% get along right and turn on you I feel that<03:17:02.350> it's<03:17:02.650> the<03:17:02.740> same<03:17:02.950> with<03:17:03.190> like<03:17:03.340> a<03:17:03.670> lot<03:17:04.150> of 03:17:04.260 --> 03:17:04.270 align:start position:0% that it's the same with like a lot of 03:17:04.270 --> 03:17:06.360 align:start position:0% that it's the same with like a lot of p2p<03:17:04.570> discussion<03:17:05.200> for<03:17:05.380> their<03:17:05.560> site<03:17:05.800> so<03:17:06.160> many 03:17:06.360 --> 03:17:06.370 align:start position:0% p2p discussion for their site so many 03:17:06.370 --> 03:17:09.900 align:start position:0% p2p discussion for their site so many opinions<03:17:07.270> and<03:17:07.780> like<03:17:07.930> technologies<03:17:08.650> using<03:17:09.550> but 03:17:09.900 --> 03:17:09.910 align:start position:0% opinions and like technologies using but 03:17:09.910 --> 03:17:12.540 align:start position:0% opinions and like technologies using but they're<03:17:10.060> all<03:17:10.300> like<03:17:10.979> slightly<03:17:11.979> different<03:17:12.400> and 03:17:12.540 --> 03:17:12.550 align:start position:0% they're all like slightly different and 03:17:12.550 --> 03:17:13.620 align:start position:0% they're all like slightly different and it's<03:17:12.670> just<03:17:12.850> really<03:17:13.060> weird 03:17:13.620 --> 03:17:13.630 align:start position:0% it's just really weird 03:17:13.630 --> 03:17:33.740 align:start position:0% it's just really weird I<03:17:13.750> feel<03:17:14.410> working<03:17:14.770> much<03:17:14.920> easier<03:17:15.310> like<03:17:32.040> project 03:17:33.740 --> 03:17:33.750 align:start position:0% I feel working much easier like project 03:17:33.750 --> 03:17:36.240 align:start position:0% I feel working much easier like project design<03:17:34.750> decisions<03:17:35.380> and<03:17:35.470> trade-offs<03:17:35.800> that 03:17:36.240 --> 03:17:36.250 align:start position:0% design decisions and trade-offs that 03:17:36.250 --> 03:17:38.580 align:start position:0% design decisions and trade-offs that they<03:17:36.370> are<03:17:36.430> making<03:17:36.850> so<03:17:37.510> I'm<03:17:37.660> familiar<03:17:38.140> with 03:17:38.580 --> 03:17:38.590 align:start position:0% they are making so I'm familiar with 03:17:38.590 --> 03:17:41.160 align:start position:0% they are making so I'm familiar with some<03:17:38.830> of<03:17:38.860> them<03:17:39.160> but<03:17:39.820> some<03:17:40.060> others<03:17:40.390> I<03:17:40.660> am<03:17:40.780> not 03:17:41.160 --> 03:17:41.170 align:start position:0% some of them but some others I am not 03:17:41.170 --> 03:17:43.380 align:start position:0% some of them but some others I am not familiar<03:17:41.770> enough<03:17:42.100> for<03:17:42.550> example<03:17:42.880> I'm<03:17:43.120> going<03:17:43.180> to 03:17:43.380 --> 03:17:43.390 align:start position:0% familiar enough for example I'm going to 03:17:43.390 --> 03:17:45.660 align:start position:0% familiar enough for example I'm going to think<03:17:43.780> about<03:17:44.050> every<03:17:44.380> two<03:17:44.500> P<03:17:44.680> I<03:17:44.920> am<03:17:45.280> not<03:17:45.460> too 03:17:45.660 --> 03:17:45.670 align:start position:0% think about every two P I am not too 03:17:45.670 --> 03:17:47.490 align:start position:0% think about every two P I am not too familiar<03:17:45.850> with<03:17:46.150> all<03:17:46.450> the<03:17:46.630> designs<03:17:46.960> and<03:17:47.350> how 03:17:47.490 --> 03:17:47.500 align:start position:0% familiar with all the designs and how 03:17:47.500 --> 03:17:49.620 align:start position:0% familiar with all the designs and how they<03:17:47.650> compare<03:17:47.860> to<03:17:48.250> other<03:17:48.520> systems<03:17:48.970> and<03:17:49.450> what 03:17:49.620 --> 03:17:49.630 align:start position:0% they compare to other systems and what 03:17:49.630 --> 03:17:51.690 align:start position:0% they compare to other systems and what they<03:17:49.750> do<03:17:49.870> and<03:17:50.200> I<03:17:50.470> think<03:17:50.530> there's<03:17:50.890> my<03:17:51.400> knowledge 03:17:51.690 --> 03:17:51.700 align:start position:0% they do and I think there's my knowledge 03:17:51.700 --> 03:17:53.940 align:start position:0% they do and I think there's my knowledge is<03:17:51.940> not<03:17:52.300> like<03:17:52.510> a<03:17:52.540> peer<03:17:52.870> comparison<03:17:53.560> and<03:17:53.770> the 03:17:53.940 --> 03:17:53.950 align:start position:0% is not like a peer comparison and the 03:17:53.950 --> 03:17:56.100 align:start position:0% is not like a peer comparison and the talk<03:17:54.130> again<03:17:54.370> just<03:17:54.580> like<03:17:54.640> a<03:17:54.700> table<03:17:55.270> remark<03:17:55.900> some 03:17:56.100 --> 03:17:56.110 align:start position:0% talk again just like a table remark some 03:17:56.110 --> 03:17:58.860 align:start position:0% talk again just like a table remark some features<03:17:56.530> but<03:17:56.710> maybe<03:17:56.890> some<03:17:57.160> more<03:17:57.420> the<03:17:58.420> quality 03:17:58.860 --> 03:17:58.870 align:start position:0% features but maybe some more the quality 03:17:58.870 --> 03:18:04.500 align:start position:0% features but maybe some more the quality description<03:17:59.650> that<03:18:00.160> explains<03:18:00.550> the 03:18:04.500 --> 03:18:04.510 align:start position:0% 03:18:04.510 --> 03:18:21.990 align:start position:0% Ginetta<03:18:05.260> pretty<03:18:05.800> sacred<03:18:20.069> like<03:18:21.069> what<03:18:21.760> are<03:18:21.880> the 03:18:21.990 --> 03:18:22.000 align:start position:0% Ginetta pretty sacred like what are the 03:18:22.000 --> 03:18:23.820 align:start position:0% Ginetta pretty sacred like what are the trade-offs<03:18:22.300> and<03:18:22.750> different<03:18:23.260> features<03:18:23.439> for 03:18:23.820 --> 03:18:23.830 align:start position:0% trade-offs and different features for 03:18:23.830 --> 03:18:28.469 align:start position:0% trade-offs and different features for white<03:18:24.160> wines<03:18:24.490> people<03:18:25.120> decide<03:18:25.450> to<03:18:25.590> waste<03:18:27.479> time 03:18:28.469 --> 03:18:28.479 align:start position:0% white wines people decide to waste time 03:18:28.479 --> 03:18:45.090 align:start position:0% white wines people decide to waste time for<03:18:42.750> perspective<03:18:43.750> but<03:18:43.990> now<03:18:44.319> driving<03:18:44.740> into<03:18:45.010> the 03:18:45.090 --> 03:18:45.100 align:start position:0% for perspective but now driving into the 03:18:45.100 --> 03:18:46.700 align:start position:0% for perspective but now driving into the people<03:18:45.370> you<03:18:45.460> are<03:18:45.490> one<03:18:45.910> of<03:18:46.029> the 03:18:46.700 --> 03:18:46.710 align:start position:0% people you are one of the 03:18:46.710 --> 03:18:49.219 align:start position:0% people you are one of the we<03:18:46.920> keep<03:18:47.250> talking<03:18:47.490> about<03:18:47.610> adoption<03:18:47.940> I<03:18:48.360> think 03:18:49.219 --> 03:18:49.229 align:start position:0% we keep talking about adoption I think 03:18:49.229 --> 03:18:51.200 align:start position:0% we keep talking about adoption I think that<03:18:49.410> p2p<03:18:50.010> networks<03:18:50.610> have<03:18:50.760> a<03:18:50.790> different<03:18:51.090> value 03:18:51.200 --> 03:18:51.210 align:start position:0% that p2p networks have a different value 03:18:51.210 --> 03:18:53.840 align:start position:0% that p2p networks have a different value proposition 03:18:53.840 --> 03:18:53.850 align:start position:0% proposition 03:18:53.850 --> 03:18:56.330 align:start position:0% proposition but<03:18:54.330> that<03:18:54.480> doesn't<03:18:54.780> mean<03:18:54.930> that<03:18:55.680> they<03:18:56.040> aren't 03:18:56.330 --> 03:18:56.340 align:start position:0% but that doesn't mean that they aren't 03:18:56.340 --> 03:18:59.840 align:start position:0% but that doesn't mean that they aren't able<03:18:56.550> to<03:18:56.760> capture<03:18:57.600> value<03:18:58.170> right<03:18:58.710> so<03:18:59.010> like<03:18:59.430> when 03:18:59.840 --> 03:18:59.850 align:start position:0% able to capture value right so like when 03:18:59.850 --> 03:19:03.110 align:start position:0% able to capture value right so like when we<03:19:00.000> keep<03:19:00.240> talking<03:19:00.390> about<03:19:01.610> like<03:19:02.610> security 03:19:03.110 --> 03:19:03.120 align:start position:0% we keep talking about like security 03:19:03.120 --> 03:19:05.240 align:start position:0% we keep talking about like security convenience<03:19:03.870> /<03:19:04.260> security<03:19:04.710> and<03:19:04.830> how<03:19:04.950> people 03:19:05.240 --> 03:19:05.250 align:start position:0% convenience / security and how people 03:19:05.250 --> 03:19:07.070 align:start position:0% convenience / security and how people are<03:19:05.310> risking<03:19:05.790> an<03:19:05.940> inconvenience<03:19:06.690> they<03:19:06.810> don't 03:19:07.070 --> 03:19:07.080 align:start position:0% are risking an inconvenience they don't 03:19:07.080 --> 03:19:09.380 align:start position:0% are risking an inconvenience they don't think<03:19:07.320> that<03:19:07.530> that's<03:19:07.710> actually<03:19:08.070> true<03:19:08.880> I<03:19:09.150> think 03:19:09.380 --> 03:19:09.390 align:start position:0% think that that's actually true I think 03:19:09.390 --> 03:19:12.470 align:start position:0% think that that's actually true I think that<03:19:09.570> we<03:19:10.110> can<03:19:10.260> start<03:19:10.730> finding<03:19:11.730> design<03:19:12.150> spaces 03:19:12.470 --> 03:19:12.480 align:start position:0% that we can start finding design spaces 03:19:12.480 --> 03:19:16.490 align:start position:0% that we can start finding design spaces and<03:19:13.440> people<03:19:14.250> experiencing<03:19:15.030> problems<03:19:15.500> that 03:19:16.490 --> 03:19:16.500 align:start position:0% and people experiencing problems that 03:19:16.500 --> 03:19:18.770 align:start position:0% and people experiencing problems that resonate<03:19:17.010> with<03:19:17.040> the<03:19:17.550> PMP<03:19:17.940> value<03:19:18.210> proposition 03:19:18.770 --> 03:19:18.780 align:start position:0% resonate with the PMP value proposition 03:19:18.780 --> 03:19:22.850 align:start position:0% resonate with the PMP value proposition and<03:19:19.050> building<03:19:19.771> for<03:19:19.980> those<03:19:20.330> problems<03:19:21.410> and<03:19:22.410> I 03:19:22.850 --> 03:19:22.860 align:start position:0% and building for those problems and I 03:19:22.860 --> 03:19:23.930 align:start position:0% and building for those problems and I was<03:19:23.010> going<03:19:23.160> to<03:19:23.190> say<03:19:23.310> something<03:19:23.370> that<03:19:23.670> was 03:19:23.930 --> 03:19:23.940 align:start position:0% was going to say something that was 03:19:23.940 --> 03:19:27.100 align:start position:0% was going to say something that was relevant<03:19:24.420> to<03:19:24.860> this 03:19:27.100 --> 03:19:27.110 align:start position:0% relevant to this 03:19:27.110 --> 03:19:30.171 align:start position:0% relevant to this I<03:19:27.430> love<03:19:28.430> this<03:19:28.610> kind<03:19:28.820> of 03:19:30.171 --> 03:19:30.181 align:start position:0% I love this kind of 03:19:30.181 --> 03:19:35.461 align:start position:0% I love this kind of yeah<03:19:31.181> okay<03:19:31.780> yeah<03:19:32.280> they're<03:19:33.280> all<03:19:33.400> yeah 03:19:35.461 --> 03:19:35.471 align:start position:0% yeah okay yeah they're all yeah 03:19:35.471 --> 03:19:37.501 align:start position:0% yeah okay yeah they're all yeah like<03:19:35.980> the<03:19:36.190> education<03:19:36.820> I<03:19:37.091> want<03:19:37.150> to<03:19:37.240> make<03:19:37.391> this 03:19:37.501 --> 03:19:37.511 align:start position:0% like the education I want to make this 03:19:37.511 --> 03:19:39.511 align:start position:0% like the education I want to make this you<03:19:38.201> know<03:19:38.320> it's<03:19:38.711> me<03:19:38.831> actually<03:19:39.011> on<03:19:39.221> that<03:19:39.280> point 03:19:39.511 --> 03:19:39.521 align:start position:0% you know it's me actually on that point 03:19:39.521 --> 03:19:42.060 align:start position:0% you know it's me actually on that point but<03:19:40.121> their<03:19:40.570> particular<03:19:40.811> use<03:19:41.081> cases<03:19:41.291> that<03:19:41.440> uses 03:19:42.060 --> 03:19:42.070 align:start position:0% but their particular use cases that uses 03:19:42.070 --> 03:19:44.161 align:start position:0% but their particular use cases that uses as<03:19:42.280> Springs<03:19:42.851> for<03:19:43.150> this<03:19:43.301> like<03:19:43.541> it's<03:19:43.871> a<03:19:43.931> movie 03:19:44.161 --> 03:19:44.171 align:start position:0% as Springs for this like it's a movie 03:19:44.171 --> 03:19:46.411 align:start position:0% as Springs for this like it's a movie like<03:19:44.501> what<03:19:45.221> would<03:19:45.341> it<03:19:45.400> work<03:19:45.701> electability<03:19:46.091> be 03:19:46.411 --> 03:19:46.421 align:start position:0% like what would it work electability be 03:19:46.421 --> 03:19:48.511 align:start position:0% like what would it work electability be a<03:19:46.451> clear<03:19:46.690> economic<03:19:46.921> message<03:19:47.921> consistent<03:19:48.341> per 03:19:48.511 --> 03:19:48.521 align:start position:0% a clear economic message consistent per 03:19:48.521 --> 03:19:50.430 align:start position:0% a clear economic message consistent per se<03:19:48.701> like<03:19:48.730> a<03:19:49.091> conflict<03:19:49.480> something<03:19:49.871> that's<03:19:50.351> very 03:19:50.430 --> 03:19:50.440 align:start position:0% se like a conflict something that's very 03:19:50.440 --> 03:19:52.921 align:start position:0% se like a conflict something that's very precise<03:19:50.831> like<03:19:51.251> it<03:19:52.061> hasn't<03:19:52.211> it<03:19:52.511> needs<03:19:52.661> certain 03:19:52.921 --> 03:19:52.931 align:start position:0% precise like it hasn't it needs certain 03:19:52.931 --> 03:19:54.691 align:start position:0% precise like it hasn't it needs certain properties<03:19:53.351> together<03:19:53.681> to<03:19:54.101> find<03:19:54.311> this<03:19:54.461> case 03:19:54.691 --> 03:19:54.701 align:start position:0% properties together to find this case 03:19:54.701 --> 03:19:56.611 align:start position:0% properties together to find this case just<03:19:55.301> getting<03:19:55.511> a<03:19:55.570> sense<03:19:55.721> in<03:19:55.900> those<03:19:56.051> contexts 03:19:56.611 --> 03:19:56.621 align:start position:0% just getting a sense in those contexts 03:19:56.621 --> 03:19:58.411 align:start position:0% just getting a sense in those contexts like<03:19:57.131> what<03:19:57.730> the<03:19:57.851> difference<03:19:58.150> is<03:19:58.271> in 03:19:58.411 --> 03:19:58.421 align:start position:0% like what the difference is in 03:19:58.421 --> 03:20:00.270 align:start position:0% like what the difference is in trade-offs<03:19:58.751> are<03:19:58.931> usually<03:19:59.650> different<03:19:59.831> pension 03:20:00.270 --> 03:20:00.280 align:start position:0% trade-offs are usually different pension 03:20:00.280 --> 03:20:02.551 align:start position:0% trade-offs are usually different pension systems<03:20:00.641> I<03:20:01.091> think<03:20:01.451> like<03:20:01.690> priceless<03:20:02.320> or<03:20:02.411> some 03:20:02.551 --> 03:20:02.561 align:start position:0% systems I think like priceless or some 03:20:02.561 --> 03:20:06.691 align:start position:0% systems I think like priceless or some examples<03:20:02.980> were<03:20:03.101> useful<03:20:03.610> just<03:20:04.331> in<03:20:04.980> from<03:20:05.980> our 03:20:06.691 --> 03:20:06.701 align:start position:0% examples were useful just in from our 03:20:06.701 --> 03:20:14.210 align:start position:0% examples were useful just in from our survey<03:20:07.530> appearances<03:20:08.530> thanks 03:20:14.210 --> 03:20:14.220 align:start position:0% 03:20:14.220 --> 03:20:16.519 align:start position:0% yeah<03:20:14.729> even<03:20:15.090> wasn't<03:20:15.449> a<03:20:15.539> dad<03:20:15.720> ecosystem<03:20:16.350> like 03:20:16.519 --> 03:20:16.529 align:start position:0% yeah even wasn't a dad ecosystem like 03:20:16.529 --> 03:20:18.439 align:start position:0% yeah even wasn't a dad ecosystem like they're<03:20:17.069> not<03:20:17.279> necessarily<03:20:17.819> compatible<03:20:18.180> to 03:20:18.439 --> 03:20:18.449 align:start position:0% they're not necessarily compatible to 03:20:18.449 --> 03:20:18.889 align:start position:0% they're not necessarily compatible to each<03:20:18.539> other 03:20:18.889 --> 03:20:18.899 align:start position:0% each other 03:20:18.899 --> 03:20:20.689 align:start position:0% each other so<03:20:19.260> unless<03:20:19.649> they're<03:20:19.859> like<03:20:19.979> directly<03:20:20.399> like 03:20:20.689 --> 03:20:20.699 align:start position:0% so unless they're like directly like 03:20:20.699 --> 03:20:25.609 align:start position:0% so unless they're like directly like using<03:20:21.060> metric<03:20:21.329> or<03:20:21.479> inline<03:20:23.749> and<03:20:24.749> so<03:20:25.140> but<03:20:25.590> I 03:20:25.609 --> 03:20:25.619 align:start position:0% using metric or inline and so but I 03:20:25.619 --> 03:20:27.080 align:start position:0% using metric or inline and so but I think<03:20:25.859> that<03:20:25.979> in<03:20:26.069> some<03:20:26.100> ways<03:20:26.399> that's<03:20:26.520> a<03:20:26.670> benefit 03:20:27.080 --> 03:20:27.090 align:start position:0% think that in some ways that's a benefit 03:20:27.090 --> 03:20:29.210 align:start position:0% think that in some ways that's a benefit because<03:20:27.569> the<03:20:27.869> project<03:20:28.260> can<03:20:28.529> then<03:20:28.680> succeed 03:20:29.210 --> 03:20:29.220 align:start position:0% because the project can then succeed 03:20:29.220 --> 03:20:32.660 align:start position:0% because the project can then succeed with<03:20:29.459> Pentacles<03:20:30.029> so<03:20:30.659> like<03:20:31.130> not<03:20:32.130> use<03:20:32.430> it<03:20:32.550> it's 03:20:32.660 --> 03:20:32.670 align:start position:0% with Pentacles so like not use it it's 03:20:32.670 --> 03:20:34.580 align:start position:0% with Pentacles so like not use it it's like<03:20:32.760> kind<03:20:32.939> of<03:20:32.999> like<03:20:33.149> this<03:20:33.300> design<03:20:33.630> you<03:20:34.350> start 03:20:34.580 --> 03:20:34.590 align:start position:0% like kind of like this design you start 03:20:34.590 --> 03:20:35.719 align:start position:0% like kind of like this design you start with<03:20:34.680> the<03:20:34.770> design<03:20:35.039> of<03:20:35.069> like<03:20:35.369> what<03:20:35.579> are<03:20:35.670> the 03:20:35.719 --> 03:20:35.729 align:start position:0% with the design of like what are the 03:20:35.729 --> 03:20:37.910 align:start position:0% with the design of like what are the requirements<03:20:36.119> for<03:20:36.689> the<03:20:37.050> app<03:20:37.289> and<03:20:37.649> then<03:20:37.859> you 03:20:37.910 --> 03:20:37.920 align:start position:0% requirements for the app and then you 03:20:37.920 --> 03:20:40.760 align:start position:0% requirements for the app and then you pick<03:20:38.249> yes<03:20:39.239> I<03:20:39.630> shall<03:20:40.050> lot<03:20:40.229> of<03:20:40.289> people<03:20:40.499> who<03:20:40.560> come 03:20:40.760 --> 03:20:40.770 align:start position:0% pick yes I shall lot of people who come 03:20:40.770 --> 03:20:43.130 align:start position:0% pick yes I shall lot of people who come to<03:20:41.039> dad<03:20:41.340> try<03:20:41.999> it<03:20:42.060> out<03:20:42.239> at<03:20:42.510> the<03:20:42.630> best<03:20:42.869> first 03:20:43.130 --> 03:20:43.140 align:start position:0% to dad try it out at the best first 03:20:43.140 --> 03:20:45.139 align:start position:0% to dad try it out at the best first because<03:20:43.680> that's<03:20:43.859> like<03:20:44.010> there<03:20:44.159> are<03:20:44.369> many<03:20:44.579> and 03:20:45.139 --> 03:20:45.149 align:start position:0% because that's like there are many and 03:20:45.149 --> 03:20:46.849 align:start position:0% because that's like there are many and then<03:20:45.420> they<03:20:45.510> figured<03:20:46.199> out<03:20:46.289> they<03:20:46.439> like<03:20:46.649> being 03:20:46.849 --> 03:20:46.859 align:start position:0% then they figured out they like being 03:20:46.859 --> 03:20:48.469 align:start position:0% then they figured out they like being the<03:20:47.100> content<03:20:47.399> addressability<03:20:47.880> or<03:20:48.180> something 03:20:48.469 --> 03:20:48.479 align:start position:0% the content addressability or something 03:20:48.479 --> 03:20:50.599 align:start position:0% the content addressability or something and<03:20:48.930> then<03:20:49.319> that<03:20:49.499> doesn't<03:20:49.859> have<03:20:49.949> that<03:20:49.979> big<03:20:50.220> into 03:20:50.599 --> 03:20:50.609 align:start position:0% and then that doesn't have that big into 03:20:50.609 --> 03:20:52.309 align:start position:0% and then that doesn't have that big into them<03:20:50.760> they<03:20:50.880> come<03:20:51.029> on<03:20:51.149> my<03:20:51.270> but<03:20:51.659> like<03:20:51.810> I<03:20:52.020> think 03:20:52.309 --> 03:20:52.319 align:start position:0% them they come on my but like I think 03:20:52.319 --> 03:20:55.519 align:start position:0% them they come on my but like I think that<03:20:52.670> when<03:20:53.670> you're<03:20:53.819> doing<03:20:54.420> us<03:20:54.659> unfortunately 03:20:55.519 --> 03:20:55.529 align:start position:0% that when you're doing us unfortunately 03:20:55.529 --> 03:20:58.279 align:start position:0% that when you're doing us unfortunately it's<03:20:55.680> like<03:20:56.090> currently<03:20:57.090> you<03:20:57.209> have<03:20:57.270> to<03:20:57.569> have<03:20:58.020> an 03:20:58.279 --> 03:20:58.289 align:start position:0% it's like currently you have to have an 03:20:58.289 --> 03:20:59.479 align:start position:0% it's like currently you have to have an understanding<03:20:58.619> of<03:20:58.979> distributed<03:20:59.430> systems 03:20:59.479 --> 03:20:59.489 align:start position:0% understanding of distributed systems 03:20:59.489 --> 03:21:01.160 align:start position:0% understanding of distributed systems that<03:20:59.999> have<03:21:00.149> some<03:21:00.510> computer<03:21:00.899> science 03:21:01.160 --> 03:21:01.170 align:start position:0% that have some computer science 03:21:01.170 --> 03:21:03.889 align:start position:0% that have some computer science background<03:21:01.380> so<03:21:02.159> like<03:21:02.340> really<03:21:03.029> name<03:21:03.209> these 03:21:03.889 --> 03:21:03.899 align:start position:0% background so like really name these 03:21:03.899 --> 03:21:05.750 align:start position:0% background so like really name these like<03:21:04.079> properties<03:21:04.560> of<03:21:04.739> the<03:21:04.949> database 03:21:05.750 --> 03:21:05.760 align:start position:0% like properties of the database 03:21:05.760 --> 03:21:08.150 align:start position:0% like properties of the database what<03:21:06.000> you<03:21:06.120> want<03:21:06.330> and<03:21:06.600> then<03:21:06.770> find<03:21:07.770> that<03:21:07.890> which 03:21:08.150 --> 03:21:08.160 align:start position:0% what you want and then find that which 03:21:08.160 --> 03:21:13.620 align:start position:0% what you want and then find that which tools<03:21:08.430> you<03:21:08.580> need<03:21:11.180> yeah 03:21:13.620 --> 03:21:13.630 align:start position:0% tools you need yeah 03:21:13.630 --> 03:21:15.929 align:start position:0% tools you need yeah but<03:21:14.140> on<03:21:14.470> that<03:21:14.770> point<03:21:14.949> which<03:21:15.279> I<03:21:15.430> think<03:21:15.460> when 03:21:15.929 --> 03:21:15.939 align:start position:0% but on that point which I think when 03:21:15.939 --> 03:21:17.670 align:start position:0% but on that point which I think when we're<03:21:16.149> designing<03:21:16.420> to<03:21:16.779> be<03:21:16.899> a<03:21:17.020> radical<03:21:17.500> new 03:21:17.670 --> 03:21:17.680 align:start position:0% we're designing to be a radical new 03:21:17.680 --> 03:21:19.139 align:start position:0% we're designing to be a radical new building<03:21:17.979> within<03:21:18.130> a<03:21:18.279> certain<03:21:18.640> design<03:21:18.909> space 03:21:19.139 --> 03:21:19.149 align:start position:0% building within a certain design space 03:21:19.149 --> 03:21:21.240 align:start position:0% building within a certain design space right<03:21:19.449> which<03:21:19.689> is<03:21:19.869> creating<03:21:20.830> a<03:21:20.859> good<03:21:21.010> career 03:21:21.240 --> 03:21:21.250 align:start position:0% right which is creating a good career 03:21:21.250 --> 03:21:23.790 align:start position:0% right which is creating a good career Network<03:21:21.489> for<03:21:21.819> resource<03:21:22.750> projects<03:21:23.619> to 03:21:23.790 --> 03:21:23.800 align:start position:0% Network for resource projects to 03:21:23.800 --> 03:21:25.679 align:start position:0% Network for resource projects to collaborate<03:21:24.310> that<03:21:24.729> it's<03:21:24.909> like<03:21:25.060> you<03:21:25.479> can 03:21:25.679 --> 03:21:25.689 align:start position:0% collaborate that it's like you can 03:21:25.689 --> 03:21:27.450 align:start position:0% collaborate that it's like you can easily<03:21:25.989> create<03:21:26.409> a<03:21:26.500> list<03:21:26.800> of<03:21:27.100> design 03:21:27.450 --> 03:21:27.460 align:start position:0% easily create a list of design 03:21:27.460 --> 03:21:28.320 align:start position:0% easily create a list of design requirements<03:21:27.970> but<03:21:28.090> it's<03:21:28.210> so<03:21:28.300> interesting 03:21:28.320 --> 03:21:28.330 align:start position:0% requirements but it's so interesting 03:21:28.330 --> 03:21:30.330 align:start position:0% requirements but it's so interesting because<03:21:28.779> we're<03:21:29.500> looking<03:21:29.619> to<03:21:29.890> scuttle<03:21:30.100> blood 03:21:30.330 --> 03:21:30.340 align:start position:0% because we're looking to scuttle blood 03:21:30.340 --> 03:21:31.830 align:start position:0% because we're looking to scuttle blood right<03:21:30.699> because<03:21:30.939> we're<03:21:31.119> trying<03:21:31.300> to<03:21:31.390> understand 03:21:31.830 --> 03:21:31.840 align:start position:0% right because we're trying to understand 03:21:31.840 --> 03:21:33.750 align:start position:0% right because we're trying to understand how<03:21:31.989> people<03:21:32.050> have<03:21:32.409> designed<03:21:32.680> before<03:21:33.220> to 03:21:33.750 --> 03:21:33.760 align:start position:0% how people have designed before to 03:21:33.760 --> 03:21:35.760 align:start position:0% how people have designed before to inform<03:21:34.119> the<03:21:34.270> design<03:21:34.449> of<03:21:34.810> our<03:21:34.899> actual<03:21:35.290> network 03:21:35.760 --> 03:21:35.770 align:start position:0% inform the design of our actual network 03:21:35.770 --> 03:21:38.070 align:start position:0% inform the design of our actual network and<03:21:36.010> so<03:21:36.250> we're<03:21:36.790> learning<03:21:37.270> off<03:21:37.569> of<03:21:37.720> each<03:21:37.840> other 03:21:38.070 --> 03:21:38.080 align:start position:0% and so we're learning off of each other 03:21:38.080 --> 03:21:39.530 align:start position:0% and so we're learning off of each other but<03:21:38.380> also<03:21:38.560> trying<03:21:38.949> to<03:21:39.069> create<03:21:39.310> new 03:21:39.530 --> 03:21:39.540 align:start position:0% but also trying to create new 03:21:39.540 --> 03:21:42.030 align:start position:0% but also trying to create new requirements<03:21:40.540> and<03:21:40.750> so<03:21:40.989> we're<03:21:41.590> running<03:21:41.770> into 03:21:42.030 --> 03:21:42.040 align:start position:0% requirements and so we're running into 03:21:42.040 --> 03:21:43.849 align:start position:0% requirements and so we're running into questions<03:21:42.520> that<03:21:42.640> people<03:21:42.790> have<03:21:43.029> solved<03:21:43.449> before 03:21:43.849 --> 03:21:43.859 align:start position:0% questions that people have solved before 03:21:43.859 --> 03:21:47.130 align:start position:0% questions that people have solved before that<03:21:44.859> have<03:21:45.069> no<03:21:45.460> actual<03:21:46.060> guide<03:21:46.390> load<03:21:46.569> if<03:21:46.960> for 03:21:47.130 --> 03:21:47.140 align:start position:0% that have no actual guide load if for 03:21:47.140 --> 03:21:49.649 align:start position:0% that have no actual guide load if for example<03:21:47.500> like<03:21:47.649> how<03:21:48.279> many<03:21:48.430> hops<03:21:48.670> do<03:21:49.119> we<03:21:49.330> need<03:21:49.479> to 03:21:49.649 --> 03:21:49.659 align:start position:0% example like how many hops do we need to 03:21:49.659 --> 03:21:51.929 align:start position:0% example like how many hops do we need to go<03:21:49.750> grab<03:21:49.960> projects<03:21:50.760> scuttlebutt<03:21:51.760> is 03:21:51.929 --> 03:21:51.939 align:start position:0% go grab projects scuttlebutt is 03:21:51.939 --> 03:21:53.609 align:start position:0% go grab projects scuttlebutt is following<03:21:52.359> so<03:21:52.689> you<03:21:52.779> can<03:21:52.960> see<03:21:53.140> the<03:21:53.260> post 03:21:53.609 --> 03:21:53.619 align:start position:0% following so you can see the post 03:21:53.619 --> 03:21:55.590 align:start position:0% following so you can see the post we<03:21:53.800> just<03:21:54.010> need<03:21:54.189> to<03:21:54.369> access<03:21:54.520> the<03:21:55.000> repo<03:21:55.300> so<03:21:55.510> we 03:21:55.590 --> 03:21:55.600 align:start position:0% we just need to access the repo so we 03:21:55.600 --> 03:21:57.330 align:start position:0% we just need to access the repo so we can<03:21:55.720> pull<03:21:55.869> the<03:21:55.960> code<03:21:56.170> so<03:21:56.500> it's<03:21:56.649> like<03:21:56.800> really 03:21:57.330 --> 03:21:57.340 align:start position:0% can pull the code so it's like really 03:21:57.340 --> 03:21:58.710 align:start position:0% can pull the code so it's like really interesting<03:21:57.880> to<03:21:58.119> start<03:21:58.330> seeing<03:21:58.630> those 03:21:58.710 --> 03:21:58.720 align:start position:0% interesting to start seeing those 03:21:58.720 --> 03:22:01.019 align:start position:0% interesting to start seeing those overlapping<03:21:59.199> it<03:21:59.409> not<03:21:59.560> overlapping<03:22:00.130> and<03:22:00.939> I 03:22:01.019 --> 03:22:01.029 align:start position:0% overlapping it not overlapping and I 03:22:01.029 --> 03:22:02.250 align:start position:0% overlapping it not overlapping and I think<03:22:01.239> that<03:22:01.420> there<03:22:01.600> could<03:22:01.810> be<03:22:01.840> a<03:22:01.960> lot<03:22:02.229> more 03:22:02.250 --> 03:22:02.260 align:start position:0% think that there could be a lot more 03:22:02.260 --> 03:22:04.469 align:start position:0% think that there could be a lot more information<03:22:03.040> share<03:22:03.250> how<03:22:03.489> these<03:22:04.000> networks<03:22:04.180> are 03:22:04.469 --> 03:22:04.479 align:start position:0% information share how these networks are 03:22:04.479 --> 03:22:06.179 align:start position:0% information share how these networks are designed<03:22:04.840> before<03:22:05.080> the<03:22:05.710> size<03:22:05.920> just<03:22:06.130> like 03:22:06.179 --> 03:22:06.189 align:start position:0% designed before the size just like 03:22:06.189 --> 03:22:11.070 align:start position:0% designed before the size just like scraping<03:22:06.729> through<03:22:07.149> documentation<03:22:09.810> yeah<03:22:10.840> so 03:22:11.070 --> 03:22:11.080 align:start position:0% scraping through documentation yeah so 03:22:11.080 --> 03:22:13.769 align:start position:0% scraping through documentation yeah so they<03:22:11.380> can<03:22:11.529> tell<03:22:11.739> something<03:22:12.100> talk<03:22:13.000> about<03:22:13.210> war 03:22:13.769 --> 03:22:13.779 align:start position:0% they can tell something talk about war 03:22:13.779 --> 03:22:16.950 align:start position:0% they can tell something talk about war zone<03:22:14.050> kid<03:22:14.979> networks<03:22:15.369> there's<03:22:16.119> a<03:22:16.449> talk<03:22:16.689> by 03:22:16.950 --> 03:22:16.960 align:start position:0% zone kid networks there's a talk by 03:22:16.960 --> 03:22:18.420 align:start position:0% zone kid networks there's a talk by Enoch<03:22:17.470> and<03:22:17.619> then 03:22:18.420 --> 03:22:18.430 align:start position:0% Enoch and then 03:22:18.430 --> 03:22:21.340 align:start position:0% Enoch and then it's<03:22:19.430> called<03:22:19.970> go<03:22:20.210> strike<03:22:20.510> do<03:22:20.659> you<03:22:20.720> check<03:22:21.199> it 03:22:21.340 --> 03:22:21.350 align:start position:0% it's called go strike do you check it 03:22:21.350 --> 03:22:23.710 align:start position:0% it's called go strike do you check it out<03:22:21.470> to<03:22:22.399> make<03:22:22.850> sure<03:22:22.880> things<03:22:23.090> go<03:22:23.300> it<03:22:23.510> looks 03:22:23.710 --> 03:22:23.720 align:start position:0% out to make sure things go it looks 03:22:23.720 --> 03:22:26.740 align:start position:0% out to make sure things go it looks where<03:22:24.290> I<03:22:24.319> like<03:22:24.529> the<03:22:24.710> history<03:22:25.609> books<03:22:26.060> check<03:22:26.689> it 03:22:26.740 --> 03:22:26.750 align:start position:0% where I like the history books check it 03:22:26.750 --> 03:22:27.309 align:start position:0% where I like the history books check it out 03:22:27.309 --> 03:22:27.319 align:start position:0% out 03:22:27.319 --> 03:22:30.609 align:start position:0% out and<03:22:28.220> you<03:22:28.369> guys<03:22:28.609> are<03:22:28.790> game<03:22:29.020> by<03:22:30.020> both<03:22:30.199> cannot 03:22:30.609 --> 03:22:30.619 align:start position:0% and you guys are game by both cannot 03:22:30.619 --> 03:22:32.530 align:start position:0% and you guys are game by both cannot cease<03:22:30.770> neutral<03:22:31.130> zone<03:22:31.279> right<03:22:31.460> now<03:22:31.489> in<03:22:32.270> place 03:22:32.530 --> 03:22:32.540 align:start position:0% cease neutral zone right now in place 03:22:32.540 --> 03:22:34.000 align:start position:0% cease neutral zone right now in place for<03:22:32.750> some<03:22:32.840> time<03:22:32.899> too<03:22:33.080> long<03:22:33.199> this<03:22:33.260> time<03:22:33.319> if<03:22:33.770> you 03:22:34.000 --> 03:22:34.010 align:start position:0% for some time too long this time if you 03:22:34.010 --> 03:22:37.450 align:start position:0% for some time too long this time if you want<03:22:34.250> us<03:22:34.489> to<03:22:34.760> help<03:22:35.920> everybody<03:22:36.920> in<03:22:37.220> the<03:22:37.310> same 03:22:37.450 --> 03:22:37.460 align:start position:0% want us to help everybody in the same 03:22:37.460 --> 03:22:39.399 align:start position:0% want us to help everybody in the same room<03:22:37.640> and<03:22:37.760> socialize<03:22:38.300> with<03:22:38.330> salsa<03:22:38.810> feedback 03:22:39.399 --> 03:22:39.409 align:start position:0% room and socialize with salsa feedback 03:22:39.409 --> 03:22:41.740 align:start position:0% room and socialize with salsa feedback comments<03:22:40.000> discussions<03:22:41.000> one<03:22:41.119> get<03:22:41.330> to<03:22:41.420> connect 03:22:41.740 --> 03:22:41.750 align:start position:0% comments discussions one get to connect 03:22:41.750 --> 03:22:43.809 align:start position:0% comments discussions one get to connect works<03:22:41.930> we<03:22:42.380> have<03:22:42.409> a<03:22:42.560> discourse<03:22:42.920> in<03:22:43.430> sense<03:22:43.699> that 03:22:43.809 --> 03:22:43.819 align:start position:0% works we have a discourse in sense that 03:22:43.819 --> 03:22:46.269 align:start position:0% works we have a discourse in sense that means<03:22:44.119> they're<03:22:44.689> simply<03:22:45.020> can<03:22:45.680> also<03:22:45.859> have<03:22:46.069> to<03:22:46.159> do 03:22:46.269 --> 03:22:46.279 align:start position:0% means they're simply can also have to do 03:22:46.279 --> 03:22:49.280 align:start position:0% means they're simply can also have to do a<03:22:46.580> published<03:22:47.029> report<03:22:47.149> means<03:22:48.109> everybody 03:22:49.280 --> 03:22:49.290 align:start position:0% a published report means everybody 03:22:49.290 --> 03:22:52.220 align:start position:0% a published report means everybody collaborating<03:22:50.101> on<03:22:50.160> that<03:22:50.841> that's<03:22:51.841> talking 03:22:52.220 --> 03:22:52.230 align:start position:0% collaborating on that that's talking 03:22:52.230 --> 03:22:58.050 align:start position:0% collaborating on that that's talking chest<03:22:52.971> that's<03:22:53.971> also<03:22:54.301> thing 03:22:58.050 --> 03:22:58.060 align:start position:0% 03:22:58.060 --> 03:23:29.740 align:start position:0% [Music] 03:23:29.740 --> 03:23:29.750 align:start position:0% 03:23:29.750 --> 03:23:36.740 align:start position:0% let's<03:23:31.189> later<03:23:32.189> so<03:23:34.939> one<03:23:35.939> problem<03:23:36.180> that<03:23:36.330> I<03:23:36.510> see 03:23:36.740 --> 03:23:36.750 align:start position:0% let's later so one problem that I see 03:23:36.750 --> 03:23:42.170 align:start position:0% let's later so one problem that I see said<03:23:37.020> it's<03:23:37.290> not<03:23:37.590> easy<03:23:37.950> to<03:23:39.050> like<03:23:40.050> like<03:23:41.180> if 03:23:42.170 --> 03:23:42.180 align:start position:0% said it's not easy to like like if 03:23:42.180 --> 03:23:44.030 align:start position:0% said it's not easy to like like if you're<03:23:42.330> building<03:23:42.540> a<03:23:42.780> network<03:23:42.960> for<03:23:43.260> phones<03:23:43.620> and 03:23:44.030 --> 03:23:44.040 align:start position:0% you're building a network for phones and 03:23:44.040 --> 03:23:46.280 align:start position:0% you're building a network for phones and usually<03:23:44.640> the<03:23:44.850> place<03:23:45.240> you<03:23:45.510> go<03:23:45.660> to<03:23:45.689> is<03:23:46.050> like 03:23:46.280 --> 03:23:46.290 align:start position:0% usually the place you go to is like 03:23:46.290 --> 03:23:49.340 align:start position:0% usually the place you go to is like pharmacies<03:23:46.800> and<03:23:47.100> you<03:23:48.030> can<03:23:48.210> just<03:23:48.420> like<03:23:48.750> there 03:23:49.340 --> 03:23:49.350 align:start position:0% pharmacies and you can just like there 03:23:49.350 --> 03:23:50.690 align:start position:0% pharmacies and you can just like there are<03:23:49.410> so<03:23:49.560> many<03:23:49.650> other<03:23:49.890> seeds<03:23:50.160> you<03:23:50.400> can<03:23:50.520> read 03:23:50.690 --> 03:23:50.700 align:start position:0% are so many other seeds you can read 03:23:50.700 --> 03:23:52.610 align:start position:0% are so many other seeds you can read them<03:23:50.820> all<03:23:50.970> you<03:23:51.300> can<03:23:51.360> read<03:23:51.630> about<03:23:51.720> like<03:23:52.080> how<03:23:52.560> the 03:23:52.610 --> 03:23:52.620 align:start position:0% them all you can read about like how the 03:23:52.620 --> 03:23:55.370 align:start position:0% them all you can read about like how the Internet<03:23:53.070> is<03:23:53.130> made<03:23:53.400> and<03:23:53.670> how<03:23:53.729> some<03:23:54.660> things<03:23:54.689> are 03:23:55.370 --> 03:23:55.380 align:start position:0% Internet is made and how some things are 03:23:55.380 --> 03:23:56.341 align:start position:0% Internet is made and how some things are made 03:23:56.341 --> 03:23:56.351 align:start position:0% made 03:23:56.351 --> 03:23:59.651 align:start position:0% made maybe<03:23:57.351> won't<03:23:57.561> even<03:23:57.950> use<03:23:57.980> anymore<03:23:58.431> like<03:23:59.331> what 03:23:59.651 --> 03:23:59.661 align:start position:0% maybe won't even use anymore like what 03:23:59.661 --> 03:24:02.531 align:start position:0% maybe won't even use anymore like what the<03:23:59.780> thinking<03:24:00.021> was<03:24:00.200> like<03:24:00.860> but<03:24:01.671> way<03:24:01.881> back<03:24:02.150> with 03:24:02.531 --> 03:24:02.541 align:start position:0% the thinking was like but way back with 03:24:02.541 --> 03:24:04.180 align:start position:0% the thinking was like but way back with like<03:24:02.900> just<03:24:03.141> recently<03:24:03.320> for<03:24:03.711> some<03:24:03.891> like<03:24:04.041> things 03:24:04.180 --> 03:24:04.190 align:start position:0% like just recently for some like things 03:24:04.190 --> 03:24:05.951 align:start position:0% like just recently for some like things like<03:24:04.400> two<03:24:04.851> days<03:24:05.030> ago<03:24:05.181> it<03:24:05.661> was<03:24:05.721> really 03:24:05.951 --> 03:24:05.961 align:start position:0% like two days ago it was really 03:24:05.961 --> 03:24:10.571 align:start position:0% like two days ago it was really interesting<03:24:07.721> news<03:24:08.721> about<03:24:08.841> like<03:24:09.351> the<03:24:09.581> most 03:24:10.571 --> 03:24:10.581 align:start position:0% interesting news about like the most 03:24:10.581 --> 03:24:12.730 align:start position:0% interesting news about like the most protocol<03:24:11.061> and<03:24:11.631> actually<03:24:11.931> I<03:24:11.961> thought<03:24:12.530> that 03:24:12.730 --> 03:24:12.740 align:start position:0% protocol and actually I thought that 03:24:12.740 --> 03:24:14.591 align:start position:0% protocol and actually I thought that that<03:24:12.891> was<03:24:13.041> insane<03:24:13.490> because<03:24:13.700> the<03:24:14.240> thinking 03:24:14.591 --> 03:24:14.601 align:start position:0% that was insane because the thinking 03:24:14.601 --> 03:24:16.451 align:start position:0% that was insane because the thinking that<03:24:14.721> went<03:24:14.871> into<03:24:15.081> this<03:24:15.291> was<03:24:15.740> like<03:24:15.950> I<03:24:16.131> wasn't 03:24:16.451 --> 03:24:16.461 align:start position:0% that went into this was like I wasn't 03:24:16.461 --> 03:24:18.251 align:start position:0% that went into this was like I wasn't really<03:24:16.700> aware<03:24:17.061> of<03:24:17.181> it<03:24:17.360> but<03:24:17.751> the<03:24:17.841> cool<03:24:18.021> thing<03:24:18.051> is 03:24:18.251 --> 03:24:18.261 align:start position:0% really aware of it but the cool thing is 03:24:18.261 --> 03:24:19.901 align:start position:0% really aware of it but the cool thing is it<03:24:18.440> was<03:24:18.561> defined<03:24:18.950> in<03:24:19.070> it<03:24:19.221> in<03:24:19.400> the<03:24:19.461> door<03:24:19.641> see 03:24:19.901 --> 03:24:19.911 align:start position:0% it was defined in it in the door see 03:24:19.911 --> 03:24:22.571 align:start position:0% it was defined in it in the door see like<03:24:20.211> years<03:24:21.051> ago<03:24:21.320> and<03:24:21.860> I<03:24:21.950> think<03:24:22.011> I<03:24:22.280> can<03:24:22.431> still 03:24:22.571 --> 03:24:22.581 align:start position:0% like years ago and I think I can still 03:24:22.581 --> 03:24:24.011 align:start position:0% like years ago and I think I can still read<03:24:22.761> about<03:24:22.971> that<03:24:23.150> I<03:24:23.271> could<03:24:23.331> actually<03:24:23.631> I<03:24:23.811> was 03:24:24.011 --> 03:24:24.021 align:start position:0% read about that I could actually I was 03:24:24.021 --> 03:24:25.511 align:start position:0% read about that I could actually I was like<03:24:24.110> oh<03:24:24.261> yeah<03:24:24.501> they<03:24:24.711> have<03:24:24.921> some<03:24:25.311> interesting 03:24:25.511 --> 03:24:25.521 align:start position:0% like oh yeah they have some interesting 03:24:25.521 --> 03:24:27.281 align:start position:0% like oh yeah they have some interesting issues<03:24:25.820> and<03:24:26.240> like<03:24:26.690> these<03:24:26.841> issues<03:24:27.141> are 03:24:27.281 --> 03:24:27.291 align:start position:0% issues and like these issues are 03:24:27.291 --> 03:24:29.770 align:start position:0% issues and like these issues are relevant<03:24:27.711> and<03:24:28.221> like<03:24:28.791> some<03:24:29.240> of<03:24:29.331> the<03:24:29.450> system 03:24:29.770 --> 03:24:29.780 align:start position:0% relevant and like some of the system 03:24:29.780 --> 03:24:31.060 align:start position:0% relevant and like some of the system that<03:24:29.871> they<03:24:29.990> built<03:24:30.171> there<03:24:30.351> for<03:24:30.381> example<03:24:30.860> really 03:24:31.060 --> 03:24:31.070 align:start position:0% that they built there for example really 03:24:31.070 --> 03:24:32.321 align:start position:0% that they built there for example really similar<03:24:31.341> to<03:24:31.461> what<03:24:31.641> people<03:24:31.761> are<03:24:32.030> building 03:24:32.321 --> 03:24:32.331 align:start position:0% similar to what people are building 03:24:32.331 --> 03:24:34.591 align:start position:0% similar to what people are building today<03:24:32.450> was<03:24:32.871> basically<03:24:33.291> about<03:24:33.530> that<03:24:33.740> indexing 03:24:34.591 --> 03:24:34.601 align:start position:0% today was basically about that indexing 03:24:34.601 --> 03:24:37.871 align:start position:0% today was basically about that indexing identity<03:24:35.601> information<03:24:35.871> you<03:24:36.381> know<03:24:36.530> like<03:24:36.881> it 03:24:37.871 --> 03:24:37.881 align:start position:0% identity information you know like it 03:24:37.881 --> 03:24:40.151 align:start position:0% identity information you know like it was<03:24:38.061> was<03:24:38.631> just<03:24:38.661> had<03:24:39.650> like<03:24:39.771> a<03:24:39.831> bit<03:24:40.011> of<03:24:40.101> a 03:24:40.151 --> 03:24:40.161 align:start position:0% was was just had like a bit of a 03:24:40.161 --> 03:24:41.711 align:start position:0% was was just had like a bit of a flashback<03:24:40.610> I<03:24:40.641> was<03:24:40.971> like<03:24:41.121> you<03:24:41.240> know<03:24:41.360> what<03:24:41.601> why 03:24:41.711 --> 03:24:41.721 align:start position:0% flashback I was like you know what why 03:24:41.721 --> 03:24:43.270 align:start position:0% flashback I was like you know what why do<03:24:41.780> we<03:24:41.931> have<03:24:42.081> something<03:24:42.291> like<03:24:42.561> that<03:24:42.740> like 03:24:43.270 --> 03:24:43.280 align:start position:0% do we have something like that like 03:24:43.280 --> 03:24:48.161 align:start position:0% do we have something like that like there<03:24:43.551> is<03:24:43.641> no<03:24:43.881> sort<03:24:44.721> of<03:24:44.780> like<03:24:47.171> repository 03:24:48.161 --> 03:24:48.171 align:start position:0% there is no sort of like repository 03:24:48.171 --> 03:24:50.081 align:start position:0% there is no sort of like repository before<03:24:48.561> like<03:24:48.771> all<03:24:49.400> the<03:24:49.641> people<03:24:49.911> you<03:24:50.001> know 03:24:50.081 --> 03:24:50.091 align:start position:0% before like all the people you know 03:24:50.091 --> 03:24:51.701 align:start position:0% before like all the people you know condition<03:24:50.601> for<03:24:50.780> example<03:24:50.990> and<03:24:51.261> this<03:24:51.381> is<03:24:51.530> just 03:24:51.701 --> 03:24:51.711 align:start position:0% condition for example and this is just 03:24:51.711 --> 03:24:53.531 align:start position:0% condition for example and this is just about<03:24:51.860> basic<03:24:52.551> techniques<03:24:52.971> you<03:24:53.240> know<03:24:53.331> like 03:24:53.531 --> 03:24:53.541 align:start position:0% about basic techniques you know like 03:24:53.541 --> 03:24:54.821 align:start position:0% about basic techniques you know like thinks<03:24:53.841> that<03:24:53.871> you<03:24:54.051> have<03:24:54.230> to<03:24:54.381> like<03:24:54.501> everyone 03:24:54.821 --> 03:24:54.831 align:start position:0% thinks that you have to like everyone 03:24:54.831 --> 03:24:56.651 align:start position:0% thinks that you have to like everyone who<03:24:55.161> goes<03:24:55.371> in<03:24:55.581> the<03:24:55.671> PDP<03:24:56.091> has<03:24:56.240> to<03:24:56.391> learn<03:24:56.541> about 03:24:56.651 --> 03:24:56.661 align:start position:0% who goes in the PDP has to learn about 03:24:56.661 --> 03:24:58.631 align:start position:0% who goes in the PDP has to learn about all<03:24:57.021> that<03:24:57.230> stuff<03:24:57.530> over<03:24:57.740> and<03:24:57.950> over<03:24:58.041> again<03:24:58.311> and 03:24:58.631 --> 03:24:58.641 align:start position:0% all that stuff over and over again and 03:24:58.641 --> 03:25:00.520 align:start position:0% all that stuff over and over again and then<03:24:59.091> they<03:24:59.240> like<03:24:59.511> eventually<03:24:59.900> it<03:25:00.320> was 03:25:00.520 --> 03:25:00.530 align:start position:0% then they like eventually it was 03:25:00.530 --> 03:25:02.321 align:start position:0% then they like eventually it was covering<03:25:00.980> there<03:25:01.341> was<03:25:01.490> this<03:25:01.641> this<03:25:01.820> is<03:25:02.030> super 03:25:02.321 --> 03:25:02.331 align:start position:0% covering there was this this is super 03:25:02.331 --> 03:25:03.881 align:start position:0% covering there was this this is super cool<03:25:02.480> software<03:25:02.900> project<03:25:03.230> that<03:25:03.411> you<03:25:03.591> know<03:25:03.711> I 03:25:03.881 --> 03:25:03.891 align:start position:0% cool software project that you know I 03:25:03.891 --> 03:25:05.081 align:start position:0% cool software project that you know I didn't<03:25:04.190> even<03:25:04.221> know<03:25:04.400> about<03:25:04.581> and<03:25:04.761> they<03:25:05.061> have 03:25:05.081 --> 03:25:05.091 align:start position:0% didn't even know about and they have 03:25:05.091 --> 03:25:07.560 align:start position:0% didn't even know about and they have they<03:25:05.751> have<03:25:05.780> this<03:25:06.081> awesome<03:25:06.351> way<03:25:06.650> of<03:25:06.950> like 03:25:07.560 --> 03:25:07.570 align:start position:0% they have this awesome way of like 03:25:07.570 --> 03:25:10.390 align:start position:0% they have this awesome way of like handing<03:25:08.570> that<03:25:08.811> or<03:25:09.230> you<03:25:09.381> know<03:25:09.501> I<03:25:09.711> think<03:25:09.891> these 03:25:10.390 --> 03:25:10.400 align:start position:0% handing that or you know I think these 03:25:10.400 --> 03:25:12.071 align:start position:0% handing that or you know I think these kinds<03:25:10.700> of<03:25:10.761> things<03:25:10.911> are<03:25:11.121> just<03:25:11.271> like<03:25:11.601> I<03:25:11.811> feel 03:25:12.071 --> 03:25:12.081 align:start position:0% kinds of things are just like I feel 03:25:12.081 --> 03:25:14.560 align:start position:0% kinds of things are just like I feel like<03:25:12.141> the<03:25:12.411> space<03:25:12.980> right<03:25:13.221> now<03:25:13.431> is<03:25:13.971> because 03:25:14.560 --> 03:25:14.570 align:start position:0% like the space right now is because 03:25:14.570 --> 03:25:16.211 align:start position:0% like the space right now is because we're<03:25:14.751> not<03:25:14.900> being<03:25:15.171> in<03:25:15.291> academia<03:25:15.740> we're<03:25:16.041> just 03:25:16.211 --> 03:25:16.221 align:start position:0% we're not being in academia we're just 03:25:16.221 --> 03:25:19.740 align:start position:0% we're not being in academia we're just you<03:25:16.461> know<03:25:16.551> like<03:25:16.791> just<03:25:17.291> people<03:25:18.291> was<03:25:18.711> different 03:25:19.740 --> 03:25:19.750 align:start position:0% you know like just people was different 03:25:19.750 --> 03:25:22.860 align:start position:0% you know like just people was different development<03:25:20.650> I<03:25:20.710> guess<03:25:21.030> is<03:25:22.030> is<03:25:22.390> that<03:25:22.570> this<03:25:22.690> very 03:25:22.860 --> 03:25:22.870 align:start position:0% development I guess is is that this very 03:25:22.870 --> 03:25:25.050 align:start position:0% development I guess is is that this very product<03:25:23.380> eyes<03:25:23.590> the<03:25:24.280> whole<03:25:24.400> thing<03:25:24.640> like<03:25:24.910> you're 03:25:25.050 --> 03:25:25.060 align:start position:0% product eyes the whole thing like you're 03:25:25.060 --> 03:25:26.310 align:start position:0% product eyes the whole thing like you're always<03:25:25.180> talking<03:25:25.600> about<03:25:25.660> that<03:25:25.810> what's<03:25:26.200> my 03:25:26.310 --> 03:25:26.320 align:start position:0% always talking about that what's my 03:25:26.320 --> 03:25:26.850 align:start position:0% always talking about that what's my product 03:25:26.850 --> 03:25:26.860 align:start position:0% product 03:25:26.860 --> 03:25:28.830 align:start position:0% product what<03:25:27.010> is<03:25:27.100> my<03:25:27.220> product<03:25:27.460> -<03:25:27.700> how's<03:25:28.240> my<03:25:28.480> product 03:25:28.830 --> 03:25:28.840 align:start position:0% what is my product - how's my product 03:25:28.840 --> 03:25:30.210 align:start position:0% what is my product - how's my product constructed<03:25:29.260> even<03:25:29.470> the<03:25:29.590> product<03:25:29.830> of<03:25:30.100> the 03:25:30.210 --> 03:25:30.220 align:start position:0% constructed even the product of the 03:25:30.220 --> 03:26:21.180 align:start position:0% constructed even the product of the source<03:26:15.270> this<03:26:16.270> is<03:26:17.160> so<03:26:18.160> I<03:26:18.460> mean<03:26:20.070> who's<03:26:21.070> gonna 03:26:21.180 --> 03:26:21.190 align:start position:0% source this is so I mean who's gonna 03:26:21.190 --> 03:26:26.280 align:start position:0% source this is so I mean who's gonna fund<03:26:21.490> that<03:26:22.890> I<03:26:24.180> mean<03:26:25.180> I<03:26:25.240> people<03:26:25.540> to<03:26:25.660> figure<03:26:26.110> that 03:26:26.280 --> 03:26:26.290 align:start position:0% fund that I mean I people to figure that 03:26:26.290 --> 03:26:38.840 align:start position:0% fund that I mean I people to figure that out 03:26:38.840 --> 03:26:38.850 align:start position:0% 03:26:38.850 --> 03:26:44.830 align:start position:0% [Music] 03:26:44.830 --> 03:26:44.840 align:start position:0% 03:26:44.840 --> 03:26:50.780 align:start position:0% and<03:26:46.100> we<03:26:47.100> look<03:26:47.310> to<03:26:47.340> kid<03:26:49.190> since<03:26:50.190> the<03:26:50.310> beginning 03:26:50.780 --> 03:26:50.790 align:start position:0% and we look to kid since the beginning 03:26:50.790 --> 03:26:54.200 align:start position:0% and we look to kid since the beginning two<03:26:51.540> years<03:26:51.720> ago<03:26:52.520> and<03:26:53.520> we<03:26:53.550> realized<03:26:53.940> they<03:26:54.090> were 03:26:54.200 --> 03:26:54.210 align:start position:0% two years ago and we realized they were 03:26:54.210 --> 03:26:59.300 align:start position:0% two years ago and we realized they were like<03:26:54.240> a<03:26:54.600> lot<03:26:54.810> of<03:26:54.990> design<03:26:55.710> yes<03:26:58.280> assumption<03:26:59.280> that 03:26:59.300 --> 03:26:59.310 align:start position:0% like a lot of design yes assumption that 03:26:59.310 --> 03:27:00.770 align:start position:0% like a lot of design yes assumption that they<03:26:59.640> didn't<03:27:00.000> work<03:27:00.150> for<03:27:00.180> us 03:27:00.770 --> 03:27:00.780 align:start position:0% they didn't work for us 03:27:00.780 --> 03:27:05.600 align:start position:0% they didn't work for us so<03:27:01.610> in<03:27:02.610> our<03:27:02.760> I<03:27:03.180> guess<03:27:03.560> problem<03:27:04.560> we<03:27:04.890> had<03:27:05.250> to<03:27:05.280> do 03:27:05.600 --> 03:27:05.610 align:start position:0% so in our I guess problem we had to do 03:27:05.610 --> 03:27:09.969 align:start position:0% so in our I guess problem we had to do like<03:27:05.820> a<03:27:05.880> lot<03:27:06.240> of<03:27:07.280> designs<03:27:08.280> bags<03:27:08.729> trade<03:27:09.210> our 03:27:09.969 --> 03:27:09.979 align:start position:0% like a lot of designs bags trade our 03:27:09.979 --> 03:27:13.580 align:start position:0% like a lot of designs bags trade our research<03:27:10.979> back<03:27:11.340> as<03:27:11.550> you<03:27:12.300> know<03:27:12.420> you<03:27:12.590> mentioned 03:27:13.580 --> 03:27:13.590 align:start position:0% research back as you know you mentioned 03:27:13.590 --> 03:27:25.040 align:start position:0% research back as you know you mentioned and<03:27:16.580> there's<03:27:17.580> a<03:27:17.700> lot<03:27:18.060> of<03:27:22.700> I<03:27:23.700> think<03:27:24.030> like<03:27:24.420> maybe 03:27:25.040 --> 03:27:25.050 align:start position:0% and there's a lot of I think like maybe 03:27:25.050 --> 03:27:27.620 align:start position:0% and there's a lot of I think like maybe like<03:27:25.410> content<03:27:25.860> to<03:27:26.010> be<03:27:26.130> that<03:27:26.280> you<03:27:26.460> like<03:27:26.640> we<03:27:27.360> like 03:27:27.620 --> 03:27:27.630 align:start position:0% like content to be that you like we like 03:27:27.630 --> 03:27:28.751 align:start position:0% like content to be that you like we like comment<03:27:28.080> both 03:27:28.751 --> 03:27:28.761 align:start position:0% comment both 03:27:28.761 --> 03:27:33.430 align:start position:0% comment both and<03:27:30.160> community<03:27:31.160> knowledge<03:27:32.150> sharing<03:27:32.570> and<03:27:32.900> big 03:27:33.430 --> 03:27:33.440 align:start position:0% and community knowledge sharing and big 03:27:33.440 --> 03:27:34.780 align:start position:0% and community knowledge sharing and big healthy<03:27:33.771> product<03:27:34.101> because<03:27:34.431> that<03:27:34.671> will 03:27:34.780 --> 03:27:34.790 align:start position:0% healthy product because that will 03:27:34.790 --> 03:27:38.440 align:start position:0% healthy product because that will provide<03:27:35.471> monetary<03:27:36.471> view<03:27:36.971> by<03:27:37.971> the<03:27:38.030> same<03:27:38.271> time 03:27:38.440 --> 03:27:38.450 align:start position:0% provide monetary view by the same time 03:27:38.450 --> 03:27:40.780 align:start position:0% provide monetary view by the same time like<03:27:38.690> if<03:27:38.900> you<03:27:39.021> think<03:27:39.261> how<03:27:39.500> many<03:27:39.790> graphical 03:27:40.780 --> 03:27:40.790 align:start position:0% like if you think how many graphical 03:27:40.790 --> 03:27:46.291 align:start position:0% like if you think how many graphical each<03:27:41.240> key<03:27:41.601> goes<03:27:41.870> into<03:27:42.171> a<03:27:42.200> other<03:27:43.190> or<03:27:45.040> Society<03:27:46.040> or 03:27:46.291 --> 03:27:46.301 align:start position:0% each key goes into a other or Society or 03:27:46.301 --> 03:27:48.820 align:start position:0% each key goes into a other or Society or ecosystem<03:27:47.301> measure<03:27:47.811> wasting<03:27:48.290> more<03:27:48.440> money<03:27:48.500> on 03:27:48.820 --> 03:27:48.830 align:start position:0% ecosystem measure wasting more money on 03:27:48.830 --> 03:27:51.610 align:start position:0% ecosystem measure wasting more money on that<03:27:49.070> side<03:27:49.400> of<03:27:49.761> like<03:27:50.601> you<03:27:50.690> know<03:27:50.721> with<03:27:51.471> the 03:27:51.610 --> 03:27:51.620 align:start position:0% that side of like you know with the 03:27:51.620 --> 03:27:55.930 align:start position:0% that side of like you know with the whole<03:27:51.860> life 03:27:55.930 --> 03:27:55.940 align:start position:0% 03:27:55.940 --> 03:27:58.540 align:start position:0% which 03:27:58.540 --> 03:27:58.550 align:start position:0% which 03:27:58.550 --> 03:28:01.400 align:start position:0% which [Music] 03:28:01.400 --> 03:28:01.410 align:start position:0% [Music] 03:28:01.410 --> 03:28:03.830 align:start position:0% [Music] depending<03:28:02.100> on<03:28:02.130> how<03:28:02.340> much<03:28:02.520> public<03:28:02.850> energy<03:28:03.420> mass 03:28:03.830 --> 03:28:03.840 align:start position:0% depending on how much public energy mass 03:28:03.840 --> 03:28:05.990 align:start position:0% depending on how much public energy mass pretty<03:28:04.500> medical<03:28:04.950> protocol<03:28:05.430> communications 03:28:05.990 --> 03:28:06.000 align:start position:0% pretty medical protocol communications 03:28:06.000 --> 03:28:08.840 align:start position:0% pretty medical protocol communications anyway<03:28:06.899> attention<03:28:07.410> to<03:28:07.500> the<03:28:07.590> project<03:28:07.979> but<03:28:08.610> not 03:28:08.840 --> 03:28:08.850 align:start position:0% anyway attention to the project but not 03:28:08.850 --> 03:28:11.630 align:start position:0% anyway attention to the project but not to<03:28:09.090> actually<03:28:09.300> lead<03:28:09.750> into<03:28:10.080> other<03:28:10.640> projects 03:28:11.630 --> 03:28:11.640 align:start position:0% to actually lead into other projects 03:28:11.640 --> 03:28:13.820 align:start position:0% to actually lead into other projects that<03:28:11.729> may<03:28:12.090> give<03:28:12.270> us<03:28:12.390> a<03:28:12.540> different<03:28:13.410> approach 03:28:13.820 --> 03:28:13.830 align:start position:0% that may give us a different approach 03:28:13.830 --> 03:28:16.220 align:start position:0% that may give us a different approach and<03:28:14.610> worked<03:28:14.970> through<03:28:15.090> that<03:28:15.420> and<03:28:15.660> it<03:28:15.750> also 03:28:16.220 --> 03:28:16.230 align:start position:0% and worked through that and it also 03:28:16.230 --> 03:28:18.650 align:start position:0% and worked through that and it also today<03:28:16.980> to<03:28:17.040> compare<03:28:17.610> them<03:28:17.790> I<03:28:17.940> think<03:28:18.061> you<03:28:18.450> just 03:28:18.650 --> 03:28:18.660 align:start position:0% today to compare them I think you just 03:28:18.660 --> 03:28:21.551 align:start position:0% today to compare them I think you just like<03:28:19.110> know<03:28:19.351> that<03:28:19.801> he<03:28:19.891> came<03:28:20.040> in<03:28:20.190> funding<03:28:20.671> to 03:28:21.551 --> 03:28:21.561 align:start position:0% like know that he came in funding to 03:28:21.561 --> 03:28:23.900 align:start position:0% like know that he came in funding to make<03:28:22.561> the<03:28:22.591> kind<03:28:22.950> of<03:28:22.980> comparison<03:28:23.400> were 03:28:23.900 --> 03:28:23.910 align:start position:0% make the kind of comparison were 03:28:23.910 --> 03:28:28.820 align:start position:0% make the kind of comparison were possible<03:28:24.690> then<03:28:25.290> I<03:28:25.671> person 03:28:28.820 --> 03:28:28.830 align:start position:0% 03:28:28.830 --> 03:28:31.461 align:start position:0% because<03:28:29.280> I<03:28:29.370> think<03:28:29.431> it's<03:28:29.700> worth<03:28:30.271> -<03:28:30.510> I<03:28:30.870> wasn't 03:28:31.461 --> 03:28:31.471 align:start position:0% because I think it's worth - I wasn't 03:28:31.471 --> 03:28:33.650 align:start position:0% because I think it's worth - I wasn't keeping<03:28:31.620> up<03:28:31.830> to<03:28:31.860> date<03:28:32.010> any<03:28:32.490> way<03:28:32.610> to<03:28:32.670> do<03:28:32.910> it<03:28:33.510> all 03:28:33.650 --> 03:28:33.660 align:start position:0% keeping up to date any way to do it all 03:28:33.660 --> 03:28:35.330 align:start position:0% keeping up to date any way to do it all so<03:28:33.690> basically<03:28:34.290> that<03:28:34.530> will<03:28:34.681> help<03:28:34.891> between 03:28:35.330 --> 03:28:35.340 align:start position:0% so basically that will help between 03:28:35.340 --> 03:28:37.551 align:start position:0% so basically that will help between probably<03:28:36.271> informants<03:28:36.900> all<03:28:37.050> these<03:28:37.200> different 03:28:37.551 --> 03:28:37.561 align:start position:0% probably informants all these different 03:28:37.561 --> 03:28:38.990 align:start position:0% probably informants all these different cues<03:28:37.771> about<03:28:37.891> a<03:28:38.010> different<03:28:38.340> decision<03:28:38.550> that<03:28:38.820> be 03:28:38.990 --> 03:28:39.000 align:start position:0% cues about a different decision that be 03:28:39.000 --> 03:28:44.900 align:start position:0% cues about a different decision that be more<03:28:39.271> aware<03:28:39.570> of<03:28:39.870> why<03:28:43.101> he<03:28:44.101> said<03:28:44.340> or<03:28:44.641> he<03:28:44.700> said 03:28:44.900 --> 03:28:44.910 align:start position:0% more aware of why he said or he said 03:28:44.910 --> 03:28:46.870 align:start position:0% more aware of why he said or he said because<03:28:45.061> there's<03:28:45.420> no<03:28:45.630> organization<03:28:46.050> that<03:28:46.530> is 03:28:46.870 --> 03:28:46.880 align:start position:0% because there's no organization that is 03:28:46.880 --> 03:28:54.051 align:start position:0% because there's no organization that is coordinating<03:28:47.880> everything<03:28:48.150> or<03:28:52.550> that<03:28:53.550> goes 03:28:54.051 --> 03:28:54.061 align:start position:0% coordinating everything or that goes 03:28:54.061 --> 03:28:56.480 align:start position:0% coordinating everything or that goes around<03:28:54.210> interviewing<03:28:54.840> and<03:28:55.410> collects<03:28:56.040> data<03:28:56.250> it 03:28:56.480 --> 03:28:56.490 align:start position:0% around interviewing and collects data it 03:28:56.490 --> 03:29:04.461 align:start position:0% around interviewing and collects data it keeps<03:28:56.790> like<03:28:57.000> a<03:28:57.050> comparison<03:29:03.141> there<03:29:04.141> with<03:29:04.320> no 03:29:04.461 --> 03:29:04.471 align:start position:0% keeps like a comparison there with no 03:29:04.471 --> 03:29:06.350 align:start position:0% keeps like a comparison there with no software<03:29:04.860> 25<03:29:05.280> minutes<03:29:05.521> on<03:29:05.641> like<03:29:05.790> challenges 03:29:06.350 --> 03:29:06.360 align:start position:0% software 25 minutes on like challenges 03:29:06.360 --> 03:29:08.600 align:start position:0% software 25 minutes on like challenges and<03:29:06.601> it<03:29:06.660> seems<03:29:06.870> like<03:29:06.990> we're<03:29:07.440> proud<03:29:08.340> of<03:29:08.370> all<03:29:08.580> we 03:29:08.600 --> 03:29:08.610 align:start position:0% and it seems like we're proud of all we 03:29:08.610 --> 03:29:10.131 align:start position:0% and it seems like we're proud of all we know<03:29:08.820> this<03:29:08.940> one<03:29:09.120> particular<03:29:09.391> travel<03:29:09.900> engine 03:29:10.131 --> 03:29:10.141 align:start position:0% know this one particular travel engine 03:29:10.141 --> 03:29:10.580 align:start position:0% know this one particular travel engine plane 03:29:10.580 --> 03:29:10.590 align:start position:0% plane 03:29:10.590 --> 03:29:12.921 align:start position:0% plane who's<03:29:11.070> experienced<03:29:11.580> in<03:29:11.760> like<03:29:11.971> the<03:29:12.570> latest 03:29:12.921 --> 03:29:12.931 align:start position:0% who's experienced in like the latest 03:29:12.931 --> 03:29:14.631 align:start position:0% who's experienced in like the latest poll 03:29:14.631 --> 03:29:14.641 align:start position:0% poll 03:29:14.641 --> 03:29:16.881 align:start position:0% poll this<03:29:14.971> alert<03:29:15.570> also<03:29:15.751> if<03:29:15.961> you<03:29:16.081> want<03:29:16.261> to<03:29:16.320> like<03:29:16.471> you 03:29:16.881 --> 03:29:16.891 align:start position:0% this alert also if you want to like you 03:29:16.891 --> 03:29:18.411 align:start position:0% this alert also if you want to like you know<03:29:17.341> change<03:29:17.791> topics 03:29:18.411 --> 03:29:18.421 align:start position:0% know change topics 03:29:18.421 --> 03:29:21.440 align:start position:0% know change topics or<03:29:19.851> proposals<03:29:20.851> we<03:29:20.940> can<03:29:21.091> still<03:29:21.301> go<03:29:21.421> through 03:29:21.440 --> 03:29:21.450 align:start position:0% or proposals we can still go through 03:29:21.450 --> 03:29:25.491 align:start position:0% or proposals we can still go through relaxed<03:29:21.990> last<03:29:22.230> few<03:29:22.410> people<03:29:23.570> yeah<03:29:24.570> but<03:29:24.841> be<03:29:25.200> you 03:29:25.491 --> 03:29:25.501 align:start position:0% relaxed last few people yeah but be you 03:29:25.501 --> 03:29:27.411 align:start position:0% relaxed last few people yeah but be you know<03:29:25.591> 20<03:29:26.011> minutes<03:29:26.431> left<03:29:26.581> we<03:29:26.820> call<03:29:27.001> so<03:29:27.150> the<03:29:27.211> top 03:29:27.411 --> 03:29:27.421 align:start position:0% know 20 minutes left we call so the top 03:29:27.421 --> 03:29:32.801 align:start position:0% know 20 minutes left we call so the top pivot<03:29:28.141> in<03:29:28.291> the<03:29:28.410> solution<03:29:29.131> solutions<03:29:30.141> problem 03:29:32.801 --> 03:29:32.811 align:start position:0% pivot in the solution solutions problem 03:29:32.811 --> 03:29:36.890 align:start position:0% pivot in the solution solutions problem yeah<03:29:33.811> that's<03:29:34.171> a<03:29:34.291> major<03:29:34.820> yeah<03:29:35.820> we<03:29:36.450> just<03:29:36.601> want<03:29:36.841> to 03:29:36.890 --> 03:29:36.900 align:start position:0% yeah that's a major yeah we just want to 03:29:36.900 --> 03:29:37.610 align:start position:0% yeah that's a major yeah we just want to look 03:29:37.610 --> 03:29:37.620 align:start position:0% look 03:29:37.620 --> 03:29:39.701 align:start position:0% look conversation 03:29:39.701 --> 03:29:39.711 align:start position:0% conversation 03:29:39.711 --> 03:29:43.060 align:start position:0% conversation not<03:29:40.311> only<03:29:40.551> did<03:29:41.211> you<03:29:41.320> get<03:29:42.320> us<03:29:42.471> continue<03:29:42.860> this 03:29:43.060 --> 03:29:43.070 align:start position:0% not only did you get us continue this 03:29:43.070 --> 03:29:45.371 align:start position:0% not only did you get us continue this ain't<03:29:43.341> like<03:29:43.490> we<03:29:43.641> could<03:29:43.881> like<03:29:44.780> five<03:29:45.200> minutes 03:29:45.371 --> 03:29:45.381 align:start position:0% ain't like we could like five minutes 03:29:45.381 --> 03:29:48.661 align:start position:0% ain't like we could like five minutes say<03:29:45.740> yeah<03:29:46.271> you<03:29:47.271> know<03:29:47.331> I<03:29:47.450> gotta<03:29:48.110> say<03:29:48.141> the 03:29:48.661 --> 03:29:48.671 align:start position:0% say yeah you know I gotta say the 03:29:48.671 --> 03:29:53.081 align:start position:0% say yeah you know I gotta say the there's<03:29:49.671> too<03:29:50.421> many<03:29:50.601> unsold<03:29:52.091> problems 03:29:53.081 --> 03:29:53.091 align:start position:0% there's too many unsold problems 03:29:53.091 --> 03:29:56.230 align:start position:0% there's too many unsold problems throughout<03:29:53.381> be<03:29:54.381> gentle 03:29:56.230 --> 03:29:56.240 align:start position:0% throughout be gentle 03:29:56.240 --> 03:29:59.410 align:start position:0% throughout be gentle I<03:29:56.270> think<03:29:56.540> that's<03:29:56.720> that's<03:29:57.290> part<03:29:57.590> of<03:29:57.710> what<03:29:58.420> back 03:29:59.410 --> 03:29:59.420 align:start position:0% I think that's that's part of what back 03:29:59.420 --> 03:30:01.599 align:start position:0% I think that's that's part of what back and<03:30:00.200> I<03:30:00.350> think 03:30:01.599 --> 03:30:01.609 align:start position:0% and I think 03:30:01.609 --> 03:30:04.661 align:start position:0% and I think respect 03:30:04.661 --> 03:30:04.671 align:start position:0% 03:30:04.671 --> 03:30:07.531 align:start position:0% as<03:30:05.450> it<03:30:05.660> was<03:30:05.751> mentioned<03:30:05.931> the<03:30:06.591> specs<03:30:06.921> are 03:30:07.531 --> 03:30:07.541 align:start position:0% as it was mentioned the specs are 03:30:07.541 --> 03:30:11.111 align:start position:0% as it was mentioned the specs are definitely<03:30:08.541> important<03:30:08.900> link<03:30:09.311> right<03:30:10.311> now<03:30:10.431> an 03:30:11.111 --> 03:30:11.121 align:start position:0% definitely important link right now an 03:30:11.121 --> 03:30:13.720 align:start position:0% definitely important link right now an art<03:30:11.331> scene<03:30:11.631> you<03:30:11.751> can<03:30:11.900> see<03:30:12.081> now 03:30:13.720 --> 03:30:13.730 align:start position:0% art scene you can see now 03:30:13.730 --> 03:30:16.421 align:start position:0% art scene you can see now what<03:30:14.730> was<03:30:14.940> proposed<03:30:15.480> to<03:30:15.511> like<03:30:15.931> disappear 03:30:16.421 --> 03:30:16.431 align:start position:0% what was proposed to like disappear 03:30:16.431 --> 03:30:21.440 align:start position:0% what was proposed to like disappear whatever<03:30:17.431> but<03:30:18.351> the<03:30:19.790> web<03:30:20.790> brief<03:30:21.000> updates<03:30:21.330> on 03:30:21.440 --> 03:30:21.450 align:start position:0% whatever but the web brief updates on 03:30:21.450 --> 03:30:28.090 align:start position:0% whatever but the web brief updates on the<03:30:21.511> team<03:30:21.771> after<03:30:22.771> there<03:30:23.190> was<03:30:23.370> a<03:30:24.360> browser 03:30:28.090 --> 03:30:28.100 align:start position:0% 03:30:28.100 --> 03:30:31.969 align:start position:0% I<03:30:29.100> think<03:30:29.609> we're<03:30:30.079> still<03:30:31.079> good<03:30:31.289> for<03:30:31.500> downstate 03:30:31.969 --> 03:30:31.979 align:start position:0% I think we're still good for downstate 03:30:31.979 --> 03:30:33.830 align:start position:0% I think we're still good for downstate we're<03:30:32.819> still<03:30:33.060> trying<03:30:33.300> to<03:30:33.359> figure<03:30:33.539> out<03:30:33.750> the 03:30:33.830 --> 03:30:33.840 align:start position:0% we're still trying to figure out the 03:30:33.840 --> 03:30:35.421 align:start position:0% we're still trying to figure out the waters 03:30:35.421 --> 03:30:35.431 align:start position:0% waters 03:30:35.431 --> 03:30:38.900 align:start position:0% waters I<03:30:35.460> don't<03:30:36.091> think<03:30:36.150> we're<03:30:36.420> ever<03:30:36.511> got<03:30:36.750> a<03:30:36.780> point 03:30:38.900 --> 03:30:38.910 align:start position:0% I don't think we're ever got a point 03:30:38.910 --> 03:30:41.000 align:start position:0% I don't think we're ever got a point you<03:30:39.330> know<03:30:39.420> just<03:30:39.689> like<03:30:39.810> hey<03:30:40.080> let's<03:30:40.350> just<03:30:40.560> you 03:30:41.000 --> 03:30:41.010 align:start position:0% you know just like hey let's just you 03:30:41.010 --> 03:30:43.219 align:start position:0% you know just like hey let's just you know<03:30:41.040> put<03:30:41.580> it<03:30:41.670> all<03:30:41.820> in<03:30:41.970> a<03:30:42.000> nice<03:30:42.330> document<03:30:43.140> that 03:30:43.219 --> 03:30:43.229 align:start position:0% know put it all in a nice document that 03:30:43.229 --> 03:30:45.170 align:start position:0% know put it all in a nice document that way<03:30:43.439> and<03:30:43.920> because<03:30:44.460> we<03:30:44.580> don't<03:30:44.760> have<03:30:44.790> to<03:30:45.000> say 03:30:45.170 --> 03:30:45.180 align:start position:0% way and because we don't have to say 03:30:45.180 --> 03:30:46.429 align:start position:0% way and because we don't have to say were<03:30:45.390> concerned<03:30:45.689> there's<03:30:45.899> just<03:30:46.080> too<03:30:46.320> many 03:30:46.429 --> 03:30:46.439 align:start position:0% were concerned there's just too many 03:30:46.439 --> 03:30:47.780 align:start position:0% were concerned there's just too many things<03:30:46.740> we<03:30:46.890> haven't<03:30:47.070> yet<03:30:47.370> figured<03:30:47.580> out 03:30:47.780 --> 03:30:47.790 align:start position:0% things we haven't yet figured out 03:30:47.790 --> 03:30:50.370 align:start position:0% things we haven't yet figured out properly 03:30:50.370 --> 03:30:50.380 align:start position:0% properly 03:30:50.380 --> 03:30:54.899 align:start position:0% properly I'm<03:30:51.189> swishing<03:30:51.699> from<03:30:51.939> facilitator<03:30:53.640> yeah<03:30:54.640> like 03:30:54.899 --> 03:30:54.909 align:start position:0% I'm swishing from facilitator yeah like 03:30:54.909 --> 03:30:58.969 align:start position:0% I'm swishing from facilitator yeah like on<03:30:55.149> that<03:30:55.300> like<03:30:55.569> there's<03:30:56.020> a<03:30:56.290> teepee 03:30:58.969 --> 03:30:58.979 align:start position:0% 03:30:58.979 --> 03:31:01.540 align:start position:0% sssh<03:30:59.979> recipe<03:31:00.850> with 03:31:01.540 --> 03:31:01.550 align:start position:0% sssh recipe with 03:31:01.550 --> 03:31:05.660 align:start position:0% sssh recipe with my<03:31:02.550> tools<03:31:02.790> and<03:31:02.910> I<03:31:03.000> imagine<03:31:03.870> you<03:31:03.960> what 03:31:05.660 --> 03:31:05.670 align:start position:0% my tools and I imagine you what 03:31:05.670 --> 03:31:07.849 align:start position:0% my tools and I imagine you what right<03:31:06.239> animators<03:31:06.750> and<03:31:07.620> there's<03:31:07.770> probably 03:31:07.849 --> 03:31:07.859 align:start position:0% right animators and there's probably 03:31:07.859 --> 03:31:10.639 align:start position:0% right animators and there's probably gonna<03:31:08.130> be<03:31:08.220> peace<03:31:09.199> there's<03:31:10.199> probably<03:31:10.439> gonna<03:31:10.560> be 03:31:10.639 --> 03:31:10.649 align:start position:0% gonna be peace there's probably gonna be 03:31:10.649 --> 03:31:12.019 align:start position:0% gonna be peace there's probably gonna be a<03:31:10.739> bunch<03:31:10.949> of<03:31:11.069> stuff<03:31:11.310> that<03:31:11.340> are<03:31:11.609> gonna<03:31:11.790> be 03:31:12.019 --> 03:31:12.029 align:start position:0% a bunch of stuff that are gonna be 03:31:12.029 --> 03:31:15.830 align:start position:0% a bunch of stuff that are gonna be abandoned<03:31:12.960> and<03:31:13.109> forgotten<03:31:13.909> we<03:31:14.909> are<03:31:15.239> now<03:31:15.420> super 03:31:15.830 --> 03:31:15.840 align:start position:0% abandoned and forgotten we are now super 03:31:15.840 --> 03:31:22.780 align:start position:0% abandoned and forgotten we are now super excited<03:31:16.290> about<03:31:16.350> but<03:31:17.040> there 03:31:22.780 --> 03:31:22.790 align:start position:0% 03:31:22.790 --> 03:31:26.130 align:start position:0% [Music] 03:31:26.130 --> 03:31:26.140 align:start position:0% 03:31:26.140 --> 03:31:29.600 align:start position:0% yeah<03:31:26.530> so<03:31:26.860> like<03:31:27.130> okay<03:31:27.340> so<03:31:27.880> we<03:31:28.150> find<03:31:28.390> like<03:31:28.900> a 03:31:29.600 --> 03:31:29.610 align:start position:0% yeah so like okay so we find like a 03:31:29.610 --> 03:31:32.130 align:start position:0% yeah so like okay so we find like a funding<03:31:30.610> entity<03:31:31.060> that<03:31:31.180> wants<03:31:31.390> to<03:31:31.540> help<03:31:31.780> me<03:31:32.021> to 03:31:32.130 --> 03:31:32.140 align:start position:0% funding entity that wants to help me to 03:31:32.140 --> 03:31:35.160 align:start position:0% funding entity that wants to help me to be<03:31:32.320> the<03:31:32.350> right<03:31:32.650> role<03:31:33.521> or<03:31:34.030> if<03:31:34.180> I'm<03:31:34.360> an<03:31:34.690> engineer 03:31:35.160 --> 03:31:35.170 align:start position:0% be the right role or if I'm an engineer 03:31:35.170 --> 03:31:37.470 align:start position:0% be the right role or if I'm an engineer coming<03:31:35.620> out<03:31:35.771> right<03:31:36.400> down<03:31:36.670> while<03:31:36.970> people<03:31:37.150> join 03:31:37.470 --> 03:31:37.480 align:start position:0% coming out right down while people join 03:31:37.480 --> 03:31:39.690 align:start position:0% coming out right down while people join the<03:31:37.510> space<03:31:37.810> portal<03:31:38.290> and<03:31:38.590> maybe<03:31:38.950> don't<03:31:39.280> ever 03:31:39.690 --> 03:31:39.700 align:start position:0% the space portal and maybe don't ever 03:31:39.700 --> 03:31:42.030 align:start position:0% the space portal and maybe don't ever answer<03:31:39.850> whatever<03:31:40.360> like<03:31:40.660> where<03:31:41.260> do<03:31:41.470> I<03:31:41.560> go<03:31:41.800> for 03:31:42.030 --> 03:31:42.040 align:start position:0% answer whatever like where do I go for 03:31:42.040 --> 03:31:44.400 align:start position:0% answer whatever like where do I go for this<03:31:42.190> list<03:31:42.430> of<03:31:42.610> the<03:31:42.700> problems<03:31:43.180> he's<03:31:43.570> the<03:31:43.840> for 03:31:44.400 --> 03:31:44.410 align:start position:0% this list of the problems he's the for 03:31:44.410 --> 03:31:54.290 align:start position:0% this list of the problems he's the for me<03:31:44.530> to<03:31:44.680> head 03:31:54.290 --> 03:31:54.300 align:start position:0% 03:31:54.300 --> 03:31:59.760 align:start position:0% problems<03:31:57.930> because<03:31:58.930> I<03:31:59.050> think<03:31:59.109> you're<03:31:59.350> right<03:31:59.529> I 03:31:59.760 --> 03:31:59.770 align:start position:0% problems because I think you're right I 03:31:59.770 --> 03:32:01.229 align:start position:0% problems because I think you're right I just<03:31:59.829> need<03:32:00.039> like<03:32:00.189> you<03:32:00.430> to<03:32:00.609> be<03:32:00.729> took<03:32:00.880> you<03:32:01.060> time 03:32:01.229 --> 03:32:01.239 align:start position:0% just need like you to be took you time 03:32:01.239 --> 03:32:02.969 align:start position:0% just need like you to be took you time to<03:32:01.479> arrive<03:32:01.659> at<03:32:01.810> this<03:32:01.930> conclusion<03:32:01.989> so<03:32:02.739> how<03:32:02.919> do 03:32:02.969 --> 03:32:02.979 align:start position:0% to arrive at this conclusion so how do 03:32:02.979 --> 03:32:05.699 align:start position:0% to arrive at this conclusion so how do we<03:32:03.159> speed<03:32:03.399> this<03:32:03.430> out<03:32:03.760> for<03:32:04.090> that<03:32:04.779> one<03:32:05.020> space 03:32:05.699 --> 03:32:05.709 align:start position:0% we speed this out for that one space 03:32:05.709 --> 03:32:07.980 align:start position:0% we speed this out for that one space monoxide<03:32:06.310> desert<03:32:06.699> island 03:32:07.980 --> 03:32:07.990 align:start position:0% monoxide desert island 03:32:07.990 --> 03:32:13.551 align:start position:0% monoxide desert island so<03:32:08.530> like<03:32:09.280> before<03:32:09.760> judge<03:32:10.270> my<03:32:10.420> love 03:32:13.551 --> 03:32:13.561 align:start position:0% 03:32:13.561 --> 03:32:15.140 align:start position:0% I<03:32:13.590> should<03:32:14.040> build<03:32:14.221> lose<03:32:14.400> a<03:32:14.431> bunch<03:32:14.761> of<03:32:14.851> friends 03:32:15.140 --> 03:32:15.150 align:start position:0% I should build lose a bunch of friends 03:32:15.150 --> 03:32:16.690 align:start position:0% I should build lose a bunch of friends or<03:32:15.721> pergola<03:32:16.110> Delta 03:32:16.690 --> 03:32:16.700 align:start position:0% or pergola Delta 03:32:16.700 --> 03:32:23.679 align:start position:0% or pergola Delta we<03:32:17.600> want<03:32:17.810> to<03:32:17.930> make<03:32:18.080> every<03:32:18.590> c1 03:32:23.679 --> 03:32:23.689 align:start position:0% 03:32:23.689 --> 03:32:29.979 align:start position:0% and<03:32:23.779> the<03:32:24.439> idea<03:32:24.709> was<03:32:24.799> like<03:32:27.999> neutral<03:32:28.999> zone<03:32:29.209> it's 03:32:29.979 --> 03:32:29.989 align:start position:0% and the idea was like neutral zone it's 03:32:29.989 --> 03:32:40.869 align:start position:0% and the idea was like neutral zone it's not<03:32:31.029> because<03:32:32.029> it's<03:32:39.459> there's<03:32:40.459> a<03:32:40.520> lot<03:32:40.579> of 03:32:40.869 --> 03:32:40.879 align:start position:0% not because it's there's a lot of 03:32:40.879 --> 03:32:42.819 align:start position:0% not because it's there's a lot of innovation<03:32:41.569> that<03:32:41.779> we<03:32:41.959> just<03:32:42.259> need<03:32:42.439> to<03:32:42.619> just 03:32:42.819 --> 03:32:42.829 align:start position:0% innovation that we just need to just 03:32:42.829 --> 03:32:46.090 align:start position:0% innovation that we just need to just make<03:32:43.069> love<03:32:43.429> equally<03:32:44.649> you're<03:32:45.649> like<03:32:45.770> really 03:32:46.090 --> 03:32:46.100 align:start position:0% make love equally you're like really 03:32:46.100 --> 03:32:48.599 align:start position:0% make love equally you're like really deserve<03:32:46.759> thinking<03:32:47.270> them<03:32:47.449> to<03:32:47.689> a<03:32:47.719> bit<03:32:47.929> unlucky 03:32:48.599 --> 03:32:48.609 align:start position:0% deserve thinking them to a bit unlucky 03:32:48.609 --> 03:32:50.699 align:start position:0% deserve thinking them to a bit unlucky a<03:32:48.749> dating<03:32:49.749> to<03:32:49.899> see<03:32:50.049> other<03:32:50.289> growth<03:32:50.529> data 03:32:50.699 --> 03:32:50.709 align:start position:0% a dating to see other growth data 03:32:50.709 --> 03:32:54.059 align:start position:0% a dating to see other growth data problem<03:32:51.810> directly<03:32:52.810> to<03:32:53.349> that<03:32:53.499> diluted<03:32:53.889> in<03:32:54.009> the 03:32:54.059 --> 03:32:54.069 align:start position:0% problem directly to that diluted in the 03:32:54.069 --> 03:32:55.619 align:start position:0% problem directly to that diluted in the back<03:32:54.249> burner<03:32:54.429> because<03:32:54.939> we<03:32:55.329> have<03:32:55.419> a<03:32:55.449> business 03:32:55.619 --> 03:32:55.629 align:start position:0% back burner because we have a business 03:32:55.629 --> 03:32:56.609 align:start position:0% back burner because we have a business to<03:32:55.869> run 03:32:56.609 --> 03:32:56.619 align:start position:0% to run 03:32:56.619 --> 03:32:59.039 align:start position:0% to run but<03:32:57.219> we're<03:32:57.520> thinkin<03:32:57.849> T<03:32:57.999> to<03:32:58.149> that<03:32:58.270> would<03:32:59.020> you 03:32:59.039 --> 03:32:59.049 align:start position:0% but we're thinkin T to that would you 03:32:59.049 --> 03:33:01.050 align:start position:0% but we're thinkin T to that would you take<03:32:59.409> a<03:32:59.679> synergist<03:33:00.279> yep<03:33:00.459> and<03:33:00.609> she's<03:33:00.759> a<03:33:00.849> feral 03:33:01.050 --> 03:33:01.060 align:start position:0% take a synergist yep and she's a feral 03:33:01.060 --> 03:33:03.449 align:start position:0% take a synergist yep and she's a feral nation<03:33:01.479> where<03:33:01.719> we<03:33:01.959> would<03:33:02.349> elect 03:33:03.449 --> 03:33:03.459 align:start position:0% nation where we would elect 03:33:03.459 --> 03:33:06.969 align:start position:0% nation where we would elect or<03:33:04.459> is<03:33:04.640> it<03:33:04.670> like<03:33:05.449> to<03:33:05.600> work<03:33:05.630> so<03:33:06.499> that<03:33:06.649> it's<03:33:06.829> going 03:33:06.969 --> 03:33:06.979 align:start position:0% or is it like to work so that it's going 03:33:06.979 --> 03:33:09.250 align:start position:0% or is it like to work so that it's going to<03:33:07.039> teach<03:33:07.249> you<03:33:07.340> crazy<03:33:07.670> from<03:33:07.939> us<03:33:08.090> I<03:33:08.359> started<03:33:09.140> to 03:33:09.250 --> 03:33:09.260 align:start position:0% to teach you crazy from us I started to 03:33:09.260 --> 03:33:14.450 align:start position:0% to teach you crazy from us I started to them 03:33:14.450 --> 03:33:14.460 align:start position:0% 03:33:14.460 --> 03:33:44.121 align:start position:0% [Music] 03:33:44.121 --> 03:33:44.131 align:start position:0% 03:33:44.131 --> 03:33:47.281 align:start position:0% we<03:33:45.131> should<03:33:45.551> have<03:33:45.911> probably<03:33:46.301> an<03:33:46.601> aggravator 03:33:47.281 --> 03:33:47.291 align:start position:0% we should have probably an aggravator 03:33:47.291 --> 03:33:50.100 align:start position:0% we should have probably an aggravator and<03:33:48.131> then<03:33:48.521> at<03:33:48.791> the<03:33:48.881> same<03:33:48.911> time<03:33:49.331> a<03:33:49.360> forum<03:33:49.900> with 03:33:50.100 --> 03:33:50.110 align:start position:0% and then at the same time a forum with 03:33:50.110 --> 03:33:55.951 align:start position:0% and then at the same time a forum with all<03:33:50.291> of<03:33:50.411> this<03:33:54.001> miners<03:33:55.001> like<03:33:55.450> you're<03:33:55.690> not 03:33:55.951 --> 03:33:55.961 align:start position:0% all of this miners like you're not 03:33:55.961 --> 03:33:58.350 align:start position:0% all of this miners like you're not seeing<03:33:56.291> like<03:33:56.831> fast<03:33:57.371> venture<03:33:57.761> toolbox<03:33:58.150> that 03:33:58.350 --> 03:33:58.360 align:start position:0% seeing like fast venture toolbox that 03:33:58.360 --> 03:34:00.060 align:start position:0% seeing like fast venture toolbox that Eric<03:33:58.690> we've<03:33:58.900> been<03:33:59.051> talking<03:33:59.381> to<03:33:59.501> love<03:33:59.681> teams 03:34:00.060 --> 03:34:00.070 align:start position:0% Eric we've been talking to love teams 03:34:00.070 --> 03:34:01.770 align:start position:0% Eric we've been talking to love teams and<03:34:00.461> only<03:34:00.641> been<03:34:00.761> in<03:34:00.851> touch<03:34:00.971> opinions<03:34:01.450> don't 03:34:01.770 --> 03:34:01.780 align:start position:0% and only been in touch opinions don't 03:34:01.780 --> 03:34:05.980 align:start position:0% and only been in touch opinions don't need<03:34:02.051> feel<03:34:02.261> about<03:34:02.440> it<03:34:02.820> there's<03:34:03.820> innovation 03:34:05.980 --> 03:34:05.990 align:start position:0% need feel about it there's innovation 03:34:05.990 --> 03:34:09.560 align:start position:0% need feel about it there's innovation lucky<03:34:06.990> about<03:34:07.790> particular<03:34:08.790> says<03:34:09.390> they're 03:34:09.560 --> 03:34:09.570 align:start position:0% lucky about particular says they're 03:34:09.570 --> 03:34:11.240 align:start position:0% lucky about particular says they're still<03:34:09.689> in<03:34:10.050> today's<03:34:10.350> where<03:34:10.590> it's<03:34:10.920> been<03:34:11.100> a 03:34:11.240 --> 03:34:11.250 align:start position:0% still in today's where it's been a 03:34:11.250 --> 03:34:14.940 align:start position:0% still in today's where it's been a product<03:34:11.520> built<03:34:12.510> their<03:34:12.660> custom 03:34:14.940 --> 03:34:14.950 align:start position:0% product built their custom 03:34:14.950 --> 03:34:18.850 align:start position:0% product built their custom that<03:34:15.950> I<03:34:15.980> only<03:34:16.280> have<03:34:16.490> 20<03:34:16.730> minutes<03:34:17.180> I<03:34:17.350> know<03:34:18.350> I 03:34:18.850 --> 03:34:18.860 align:start position:0% that I only have 20 minutes I know I 03:34:18.860 --> 03:34:20.350 align:start position:0% that I only have 20 minutes I know I wanted<03:34:19.100> to<03:34:19.190> say<03:34:19.400> is<03:34:19.460> that<03:34:19.580> means<03:34:20.000> before<03:34:20.150> you 03:34:20.350 --> 03:34:20.360 align:start position:0% wanted to say is that means before you 03:34:20.360 --> 03:34:22.990 align:start position:0% wanted to say is that means before you leave<03:34:20.630> the<03:34:20.780> room<03:34:20.810> please<03:34:21.460> take<03:34:22.460> that 03:34:22.990 --> 03:34:23.000 align:start position:0% leave the room please take that 03:34:23.000 --> 03:34:32.700 align:start position:0% leave the room please take that that<03:34:23.030> you<03:34:23.240> believe<03:34:23.990> in<03:34:24.110> got<03:34:24.290> behind<03:34:24.590> with<03:34:25.340> you 03:34:32.700 --> 03:34:32.710 align:start position:0% 03:34:32.710 --> 03:34:35.560 align:start position:0% so<03:34:33.710> I<03:34:34.010> wanted<03:34:34.430> to<03:34:34.610> transition<03:34:35.090> to<03:34:35.450> this 03:34:35.560 --> 03:34:35.570 align:start position:0% so I wanted to transition to this 03:34:35.570 --> 03:34:37.030 align:start position:0% so I wanted to transition to this discussion 03:34:37.030 --> 03:34:37.040 align:start position:0% discussion 03:34:37.040 --> 03:34:41.050 align:start position:0% discussion that<03:34:37.630> receipt<03:34:38.630> may<03:34:39.410> be<03:34:39.880> continuing<03:34:40.880> on<03:34:41.000> the 03:34:41.050 --> 03:34:41.060 align:start position:0% that receipt may be continuing on the 03:34:41.060 --> 03:34:43.470 align:start position:0% that receipt may be continuing on the discussion<03:34:41.540> and<03:34:41.630> thinking<03:34:41.960> about<03:34:42.050> burdens 03:34:43.470 --> 03:34:43.480 align:start position:0% discussion and thinking about burdens 03:34:43.480 --> 03:34:47.230 align:start position:0% discussion and thinking about burdens both<03:34:44.480> what<03:34:44.780> sort<03:34:45.200> of<03:34:45.290> like<03:34:45.880> this<03:34:46.880> is<03:34:47.060> kind<03:34:47.210> of 03:34:47.230 --> 03:34:47.240 align:start position:0% both what sort of like this is kind of 03:34:47.240 --> 03:34:49.570 align:start position:0% both what sort of like this is kind of like<03:34:47.330> peer-to-peer<03:34:48.280> organization<03:34:49.280> to 03:34:49.570 --> 03:34:49.580 align:start position:0% like peer-to-peer organization to 03:34:49.580 --> 03:35:08.519 align:start position:0% like peer-to-peer organization to centralized<03:34:49.970> organization<03:34:50.180> space 03:35:08.519 --> 03:35:08.529 align:start position:0% 03:35:08.529 --> 03:35:10.780 align:start position:0% so<03:35:09.529> world<03:35:09.770> people<03:35:09.979> enjoy<03:35:10.370> freedom<03:35:10.609> is 03:35:10.780 --> 03:35:10.790 align:start position:0% so world people enjoy freedom is 03:35:10.790 --> 03:35:15.170 align:start position:0% so world people enjoy freedom is disgusting 03:35:15.170 --> 03:35:15.180 align:start position:0% 03:35:15.180 --> 03:35:16.699 align:start position:0% though<03:35:15.689> people<03:35:15.840> enter<03:35:16.289> they're<03:35:16.499> just 03:35:16.699 --> 03:35:16.709 align:start position:0% though people enter they're just 03:35:16.709 --> 03:35:21.170 align:start position:0% though people enter they're just discussing<03:35:16.949> like<03:35:18.199> the<03:35:19.520> challenges<03:35:20.520> of<03:35:20.939> the 03:35:21.170 --> 03:35:21.180 align:start position:0% discussing like the challenges of the 03:35:21.180 --> 03:35:23.359 align:start position:0% discussing like the challenges of the peer-to-peer<03:35:21.390> spaces<03:35:22.229> and<03:35:22.859> one<03:35:23.100> of<03:35:23.220> the 03:35:23.359 --> 03:35:23.369 align:start position:0% peer-to-peer spaces and one of the 03:35:23.369 --> 03:35:25.519 align:start position:0% peer-to-peer spaces and one of the challenges<03:35:23.819> we<03:35:23.939> kind<03:35:24.119> of<03:35:24.180> founded<03:35:24.569> on<03:35:24.720> was<03:35:24.989> how 03:35:25.519 --> 03:35:25.529 align:start position:0% challenges we kind of founded on was how 03:35:25.529 --> 03:35:28.219 align:start position:0% challenges we kind of founded on was how you<03:35:25.590> choose<03:35:26.340> a<03:35:26.369> toolset<03:35:26.850> to<03:35:27.119> build<03:35:27.510> your<03:35:27.720> your 03:35:28.219 --> 03:35:28.229 align:start position:0% you choose a toolset to build your your 03:35:28.229 --> 03:35:30.739 align:start position:0% you choose a toolset to build your your house<03:35:28.439> and<03:35:28.890> then<03:35:29.249> kind<03:35:29.909> of<03:35:29.970> linens<03:35:30.359> to<03:35:30.539> like 03:35:30.739 --> 03:35:30.749 align:start position:0% house and then kind of linens to like 03:35:30.749 --> 03:35:33.559 align:start position:0% house and then kind of linens to like well<03:35:31.399> everyone's<03:35:32.399> kind<03:35:32.699> of<03:35:32.760> this<03:35:32.939> trying<03:35:33.419> to 03:35:33.559 --> 03:35:33.569 align:start position:0% well everyone's kind of this trying to 03:35:33.569 --> 03:35:35.840 align:start position:0% well everyone's kind of this trying to build<03:35:33.779> apps<03:35:34.020> and<03:35:34.470> building<03:35:35.279> on<03:35:35.399> the<03:35:35.489> product 03:35:35.840 --> 03:35:35.850 align:start position:0% build apps and building on the product 03:35:35.850 --> 03:35:37.099 align:start position:0% build apps and building on the product because<03:35:36.060> they're<03:35:36.209> after<03:35:36.359> other<03:35:36.659> things<03:35:36.779> an 03:35:37.099 --> 03:35:37.109 align:start position:0% because they're after other things an 03:35:37.109 --> 03:35:39.050 align:start position:0% because they're after other things an open-source<03:35:37.560> reading<03:35:38.189> documentation<03:35:38.760> is 03:35:39.050 --> 03:35:39.060 align:start position:0% open-source reading documentation is 03:35:39.060 --> 03:35:41.420 align:start position:0% open-source reading documentation is already<03:35:39.419> a<03:35:39.449> huge<03:35:39.720> challenge<03:35:40.050> alone<03:35:41.010> for<03:35:41.340> your 03:35:41.420 --> 03:35:41.430 align:start position:0% already a huge challenge alone for your 03:35:41.430 --> 03:35:44.239 align:start position:0% already a huge challenge alone for your own<03:35:41.520> product<03:35:42.560> compared<03:35:43.560> to<03:35:43.680> other<03:35:43.859> products 03:35:44.239 --> 03:35:44.249 align:start position:0% own product compared to other products 03:35:44.249 --> 03:35:46.340 align:start position:0% own product compared to other products that<03:35:44.459> make<03:35:44.999> it<03:35:45.720> easy<03:35:45.930> for<03:35:46.079> developers 03:35:46.340 --> 03:35:46.350 align:start position:0% that make it easy for developers 03:35:46.350 --> 03:35:49.670 align:start position:0% that make it easy for developers sketball<03:35:47.060> so<03:35:48.060> it's<03:35:48.600> become<03:35:49.020> all<03:35:49.140> sort<03:35:49.380> of<03:35:49.529> a 03:35:49.670 --> 03:35:49.680 align:start position:0% sketball so it's become all sort of a 03:35:49.680 --> 03:35:51.710 align:start position:0% sketball so it's become all sort of a difficult<03:35:50.550> space<03:35:50.729> adventure<03:35:51.270> for<03:35:51.539> a<03:35:51.569> lot<03:35:51.689> of 03:35:51.710 --> 03:35:51.720 align:start position:0% difficult space adventure for a lot of 03:35:51.720 --> 03:35:53.330 align:start position:0% difficult space adventure for a lot of folks<03:35:51.869> and<03:35:52.739> so<03:35:52.859> you're<03:35:52.979> trying<03:35:53.159> to<03:35:53.220> think 03:35:53.330 --> 03:35:53.340 align:start position:0% folks and so you're trying to think 03:35:53.340 --> 03:35:54.649 align:start position:0% folks and so you're trying to think about<03:35:53.489> those<03:35:53.880> kind<03:35:54.149> of<03:35:54.209> problem<03:35:54.569> you're 03:35:54.649 --> 03:35:54.659 align:start position:0% about those kind of problem you're 03:35:54.659 --> 03:35:56.269 align:start position:0% about those kind of problem you're assessing<03:35:54.899> and<03:35:55.409> we're<03:35:55.590> going<03:35:55.709> to<03:35:55.739> go<03:35:55.979> over<03:35:56.189> the 03:35:56.269 --> 03:35:56.279 align:start position:0% assessing and we're going to go over the 03:35:56.279 --> 03:36:01.580 align:start position:0% assessing and we're going to go over the next<03:35:56.430> 20<03:35:56.699> minutes<03:35:56.729> into<03:35:58.069> solutions<03:35:59.930> just<03:36:00.930> kind 03:36:01.580 --> 03:36:01.590 align:start position:0% next 20 minutes into solutions just kind 03:36:01.590 --> 03:36:05.059 align:start position:0% next 20 minutes into solutions just kind of<03:36:01.619> like<03:36:01.800> popping<03:36:02.609> out<03:36:02.819> solutions<03:36:03.890> making<03:36:04.890> it 03:36:05.059 --> 03:36:05.069 align:start position:0% of like popping out solutions making it 03:36:05.069 --> 03:36:07.720 align:start position:0% of like popping out solutions making it cool<03:36:05.220> to<03:36:05.399> like<03:36:05.579> maybe<03:36:06.300> go<03:36:06.600> around<03:36:06.720> and<03:36:07.229> see 03:36:07.720 --> 03:36:07.730 align:start position:0% cool to like maybe go around and see 03:36:07.730 --> 03:36:10.810 align:start position:0% cool to like maybe go around and see think<03:36:08.120> about<03:36:08.330> this<03:36:08.540> and<03:36:08.900> then<03:36:09.200> we<03:36:10.190> can<03:36:10.341> have<03:36:10.521> a 03:36:10.810 --> 03:36:10.820 align:start position:0% think about this and then we can have a 03:36:10.820 --> 03:36:13.020 align:start position:0% think about this and then we can have a discussion<03:36:11.450> later<03:36:11.811> or<03:36:11.990> maybe<03:36:12.200> we<03:36:12.381> can<03:36:12.500> have<03:36:12.681> a 03:36:13.020 --> 03:36:13.030 align:start position:0% discussion later or maybe we can have a 03:36:13.030 --> 03:36:15.730 align:start position:0% discussion later or maybe we can have a happy<03:36:14.030> hour<03:36:14.120> I<03:36:14.690> think<03:36:15.080> that<03:36:15.200> the<03:36:15.410> main<03:36:15.561> problem 03:36:15.730 --> 03:36:15.740 align:start position:0% happy hour I think that the main problem 03:36:15.740 --> 03:36:19.270 align:start position:0% happy hour I think that the main problem is<03:36:16.040> that<03:36:16.221> we<03:36:16.370> all<03:36:16.461> will<03:36:16.700> be<03:36:18.011> separate<03:36:19.011> and 03:36:19.270 --> 03:36:19.280 align:start position:0% is that we all will be separate and 03:36:19.280 --> 03:36:20.980 align:start position:0% is that we all will be separate and we're<03:36:19.610> not<03:36:19.761> collaborating<03:36:20.540> that<03:36:20.690> we're<03:36:20.841> not 03:36:20.980 --> 03:36:20.990 align:start position:0% we're not collaborating that we're not 03:36:20.990 --> 03:36:23.801 align:start position:0% we're not collaborating that we're not like<03:36:21.711> integrating<03:36:22.700> what<03:36:22.881> other<03:36:23.330> people<03:36:23.721> are 03:36:23.801 --> 03:36:23.811 align:start position:0% like integrating what other people are 03:36:23.811 --> 03:36:25.121 align:start position:0% like integrating what other people are doing<03:36:23.870> with<03:36:24.230> our<03:36:24.381> the<03:36:24.711> thing<03:36:24.891> that<03:36:25.040> I'm 03:36:25.121 --> 03:36:25.131 align:start position:0% doing with our the thing that I'm 03:36:25.131 --> 03:36:28.480 align:start position:0% doing with our the thing that I'm currently<03:36:25.521> doing<03:36:26.530> so<03:36:27.530> I<03:36:27.561> think<03:36:27.681> that's<03:36:28.070> one<03:36:28.461> of 03:36:28.480 --> 03:36:28.490 align:start position:0% currently doing so I think that's one of 03:36:28.490 --> 03:36:31.060 align:start position:0% currently doing so I think that's one of the<03:36:28.610> main<03:36:28.910> thing<03:36:29.421> and<03:36:29.780> that's<03:36:30.440> why<03:36:30.650> I<03:36:30.681> said 03:36:31.060 --> 03:36:31.070 align:start position:0% the main thing and that's why I said 03:36:31.070 --> 03:36:32.560 align:start position:0% the main thing and that's why I said that<03:36:31.101> we<03:36:31.341> should<03:36:31.370> probably<03:36:31.851> have<03:36:32.150> a<03:36:32.181> diamond 03:36:32.560 --> 03:36:32.570 align:start position:0% that we should probably have a diamond 03:36:32.570 --> 03:36:35.291 align:start position:0% that we should probably have a diamond grader<03:36:32.660> or<03:36:33.141> the<03:36:33.320> need<03:36:34.250> to<03:36:34.370> be<03:36:34.521> networks<03:36:35.000> and<03:36:35.181> at 03:36:35.291 --> 03:36:35.301 align:start position:0% grader or the need to be networks and at 03:36:35.301 --> 03:36:39.761 align:start position:0% grader or the need to be networks and at the<03:36:35.391> same<03:36:35.570> time<03:36:35.891> rate<03:36:36.891> them<03:36:37.131> and<03:36:37.461> that<03:36:38.450> we<03:36:38.771> put 03:36:39.761 --> 03:36:39.771 align:start position:0% the same time rate them and that we put 03:36:39.771 --> 03:36:43.301 align:start position:0% the same time rate them and that we put some<03:36:40.011> kind<03:36:40.250> of<03:36:40.341> rating<03:36:41.181> system<03:36:41.601> there<03:36:41.950> I<03:36:42.950> don't 03:36:43.301 --> 03:36:43.311 align:start position:0% some kind of rating system there I don't 03:36:43.311 --> 03:36:44.921 align:start position:0% some kind of rating system there I don't know<03:36:43.490> bro<03:36:43.851> or<03:36:44.000> something<03:36:44.421> like<03:36:44.480> this<03:36:44.601> could<03:36:44.841> be 03:36:44.921 --> 03:36:44.931 align:start position:0% know bro or something like this could be 03:36:44.931 --> 03:36:52.140 align:start position:0% know bro or something like this could be useful 03:36:52.140 --> 03:36:52.150 align:start position:0% 03:36:52.150 --> 03:36:55.990 align:start position:0% our<03:36:53.150> systems<03:36:53.780> and<03:36:54.220> often<03:36:55.220> times<03:36:55.490> there<03:36:55.790> might 03:36:55.990 --> 03:36:56.000 align:start position:0% our systems and often times there might 03:36:56.000 --> 03:36:59.280 align:start position:0% our systems and often times there might be<03:36:56.080> reasons<03:36:57.080> why<03:36:57.320> certain<03:36:57.860> project<03:36:58.340> us 03:36:59.280 --> 03:36:59.290 align:start position:0% be reasons why certain project us 03:36:59.290 --> 03:37:02.760 align:start position:0% be reasons why certain project us delivered<03:36:59.800> differently<03:37:00.540> it's<03:37:01.540> not<03:37:01.720> easy<03:37:02.290> for 03:37:02.760 --> 03:37:02.770 align:start position:0% delivered differently it's not easy for 03:37:02.770 --> 03:37:10.280 align:start position:0% delivered differently it's not easy for somebody<03:37:03.010> who's<03:37:03.430> moved<03:37:03.700> to<03:37:04.450> a<03:37:04.479> figure<03:37:04.810> out<03:37:04.930> why 03:37:10.280 --> 03:37:10.290 align:start position:0% 03:37:10.290 --> 03:37:11.960 align:start position:0% but<03:37:10.470> it's<03:37:10.590> very<03:37:10.680> hard<03:37:11.010> to<03:37:11.279> figure<03:37:11.579> out<03:37:11.699> all 03:37:11.960 --> 03:37:11.970 align:start position:0% but it's very hard to figure out all 03:37:11.970 --> 03:37:14.179 align:start position:0% but it's very hard to figure out all these<03:37:12.060> aspects<03:37:12.510> my<03:37:12.989> heart<03:37:13.229> you<03:37:13.529> differently 03:37:14.179 --> 03:37:14.189 align:start position:0% these aspects my heart you differently 03:37:14.189 --> 03:37:18.080 align:start position:0% these aspects my heart you differently and<03:37:14.550> then<03:37:14.760> being<03:37:15.449> able<03:37:15.569> to<03:37:15.869> think<03:37:16.470> about<03:37:16.560> this 03:37:18.080 --> 03:37:18.090 align:start position:0% and then being able to think about this 03:37:18.090 --> 03:37:23.809 align:start position:0% and then being able to think about this but<03:37:18.779> maybe<03:37:18.960> resolution<03:37:22.189> well<03:37:23.189> I<03:37:23.520> don't<03:37:23.729> know<03:37:23.790> I 03:37:23.809 --> 03:37:23.819 align:start position:0% but maybe resolution well I don't know I 03:37:23.819 --> 03:37:25.280 align:start position:0% but maybe resolution well I don't know I have<03:37:24.119> a<03:37:24.149> feeling<03:37:24.479> that<03:37:24.600> it's<03:37:24.840> a<03:37:24.930> funding 03:37:25.280 --> 03:37:25.290 align:start position:0% have a feeling that it's a funding 03:37:25.290 --> 03:37:27.469 align:start position:0% have a feeling that it's a funding project<03:37:25.710> problem<03:37:26.460> because<03:37:26.790> if<03:37:27.000> there<03:37:27.180> is<03:37:27.270> more 03:37:27.469 --> 03:37:27.479 align:start position:0% project problem because if there is more 03:37:27.479 --> 03:37:31.099 align:start position:0% project problem because if there is more money<03:37:27.689> that<03:37:28.050> means<03:37:28.319> you<03:37:28.560> can<03:37:29.840> explain<03:37:30.840> things 03:37:31.099 --> 03:37:31.109 align:start position:0% money that means you can explain things 03:37:31.109 --> 03:37:32.990 align:start position:0% money that means you can explain things more<03:37:31.290> you<03:37:31.619> can<03:37:31.770> communicate<03:37:32.279> better<03:37:32.550> if<03:37:32.819> it 03:37:32.990 --> 03:37:33.000 align:start position:0% more you can communicate better if it 03:37:33.000 --> 03:37:34.280 align:start position:0% more you can communicate better if it will<03:37:33.149> better<03:37:33.329> documentation<03:37:33.899> with<03:37:34.199> an 03:37:34.280 --> 03:37:34.290 align:start position:0% will better documentation with an 03:37:34.290 --> 03:37:37.370 align:start position:0% will better documentation with an experiment<03:37:34.770> better<03:37:35.100> and<03:37:35.520> also<03:37:36.390> like<03:37:36.689> when<03:37:37.170> you 03:37:37.370 --> 03:37:37.380 align:start position:0% experiment better and also like when you 03:37:37.380 --> 03:37:38.899 align:start position:0% experiment better and also like when you are<03:37:37.500> trying<03:37:37.800> to<03:37:38.100> use<03:37:38.399> peer-to-peer 03:37:38.899 --> 03:37:38.909 align:start position:0% are trying to use peer-to-peer 03:37:38.909 --> 03:37:43.280 align:start position:0% are trying to use peer-to-peer technology<03:37:39.739> a<03:37:40.739> lot<03:37:41.159> of<03:37:41.310> times<03:37:41.779> if<03:37:42.779> you<03:37:42.930> want<03:37:43.199> to 03:37:43.280 --> 03:37:43.290 align:start position:0% technology a lot of times if you want to 03:37:43.290 --> 03:37:46.280 align:start position:0% technology a lot of times if you want to get<03:37:43.439> funding<03:37:44.010> like<03:37:44.640> we<03:37:44.939> are<03:37:45.029> not<03:37:45.180> creating<03:37:45.840> we 03:37:46.280 --> 03:37:46.290 align:start position:0% get funding like we are not creating we 03:37:46.290 --> 03:37:49.250 align:start position:0% get funding like we are not creating we are<03:37:46.380> using<03:37:46.680> that<03:37:47.069> for<03:37:47.340> example<03:37:47.579> yeah<03:37:48.000> but<03:37:48.449> then 03:37:49.250 --> 03:37:49.260 align:start position:0% are using that for example yeah but then 03:37:49.260 --> 03:37:51.530 align:start position:0% are using that for example yeah but then you<03:37:49.680> have<03:37:49.920> to<03:37:49.949> like<03:37:50.520> people<03:37:50.670> want<03:37:51.060> you<03:37:51.210> to<03:37:51.239> use 03:37:51.530 --> 03:37:51.540 align:start position:0% you have to like people want you to use 03:37:51.540 --> 03:37:53.080 align:start position:0% you have to like people want you to use the<03:37:51.659> technology<03:37:52.109> that<03:37:52.199> is<03:37:52.380> more<03:37:52.680> popular 03:37:53.080 --> 03:37:53.090 align:start position:0% the technology that is more popular 03:37:53.090 --> 03:37:55.760 align:start position:0% the technology that is more popular because<03:37:54.090> then<03:37:54.540> it's<03:37:54.659> easier<03:37:55.079> to<03:37:55.229> get<03:37:55.319> funding 03:37:55.760 --> 03:37:55.770 align:start position:0% because then it's easier to get funding 03:37:55.770 --> 03:37:59.960 align:start position:0% because then it's easier to get funding so<03:37:55.949> this<03:37:56.310> is<03:37:56.430> also<03:37:58.189> but<03:37:59.189> yeah<03:37:59.340> what<03:37:59.579> we<03:37:59.670> want<03:37:59.850> to 03:37:59.960 --> 03:37:59.970 align:start position:0% so this is also but yeah what we want to 03:37:59.970 --> 03:38:00.590 align:start position:0% so this is also but yeah what we want to do<03:38:00.210> wrong 03:38:00.590 --> 03:38:00.600 align:start position:0% do wrong 03:38:00.600 --> 03:38:02.210 align:start position:0% do wrong yeah<03:38:00.720> we'll<03:38:00.869> just<03:38:00.899> focus<03:38:01.350> on<03:38:01.500> solutions<03:38:01.710> here 03:38:02.210 --> 03:38:02.220 align:start position:0% yeah we'll just focus on solutions here 03:38:02.220 --> 03:38:04.040 align:start position:0% yeah we'll just focus on solutions here and<03:38:02.340> I'll<03:38:02.430> start<03:38:02.520> with<03:38:02.790> signal<03:38:03.149> on<03:38:03.270> and 03:38:04.040 --> 03:38:04.050 align:start position:0% and I'll start with signal on and 03:38:04.050 --> 03:38:05.330 align:start position:0% and I'll start with signal on and they'll<03:38:04.170> just<03:38:04.380> start<03:38:04.529> reading<03:38:04.680> that's<03:38:04.949> we<03:38:05.159> can 03:38:05.330 --> 03:38:05.340 align:start position:0% they'll just start reading that's we can 03:38:05.340 --> 03:38:08.149 align:start position:0% they'll just start reading that's we can see<03:38:05.550> yeah<03:38:06.270> let's<03:38:06.750> go<03:38:06.899> around<03:38:07.140> what<03:38:07.529> maybe<03:38:07.949> it's 03:38:08.149 --> 03:38:08.159 align:start position:0% see yeah let's go around what maybe it's 03:38:08.159 --> 03:38:10.609 align:start position:0% see yeah let's go around what maybe it's because<03:38:08.279> we<03:38:08.579> don't<03:38:08.760> have<03:38:08.819> we<03:38:09.630> don't<03:38:09.810> have<03:38:09.869> a 03:38:10.609 --> 03:38:10.619 align:start position:0% because we don't have we don't have a 03:38:10.619 --> 03:38:13.969 align:start position:0% because we don't have we don't have a group<03:38:11.430> or<03:38:11.699> something<03:38:12.479> that<03:38:12.689> who<03:38:13.409> received 03:38:13.969 --> 03:38:13.979 align:start position:0% group or something that who received 03:38:13.979 --> 03:38:16.250 align:start position:0% group or something that who received that<03:38:14.100> money<03:38:14.369> we<03:38:14.760> don't<03:38:14.880> have<03:38:15.090> data<03:38:15.630> organism 03:38:16.250 --> 03:38:16.260 align:start position:0% that money we don't have data organism 03:38:16.260 --> 03:38:20.269 align:start position:0% that money we don't have data organism you<03:38:16.439> know<03:38:16.590> maybe<03:38:17.489> we<03:38:17.760> have<03:38:18.600> a<03:38:19.050> foundation<03:38:19.859> for 03:38:20.269 --> 03:38:20.279 align:start position:0% you know maybe we have a foundation for 03:38:20.279 --> 03:38:22.639 align:start position:0% you know maybe we have a foundation for this<03:38:20.510> or<03:38:21.510> I<03:38:21.840> don't<03:38:21.960> know<03:38:22.050> I<03:38:22.229> don't<03:38:22.409> know<03:38:22.470> what's 03:38:22.639 --> 03:38:22.649 align:start position:0% this or I don't know I don't know what's 03:38:22.649 --> 03:38:25.399 align:start position:0% this or I don't know I don't know what's the<03:38:22.710> best<03:38:22.920> book<03:38:23.130> but<03:38:23.640> every<03:38:24.079> location<03:38:25.079> or 03:38:25.399 --> 03:38:25.409 align:start position:0% the best book but every location or 03:38:25.409 --> 03:38:32.540 align:start position:0% the best book but every location or something<03:38:29.210> here<03:38:30.829> kind<03:38:31.829> of<03:38:31.890> knows<03:38:32.010> me<03:38:32.399> out 03:38:32.540 --> 03:38:32.550 align:start position:0% something here kind of knows me out 03:38:32.550 --> 03:38:37.280 align:start position:0% something here kind of knows me out standards<03:38:32.880> also<03:38:34.279> very<03:38:35.279> helpful<03:38:35.779> results<03:38:36.779> like 03:38:37.280 --> 03:38:37.290 align:start position:0% standards also very helpful results like 03:38:37.290 --> 03:38:40.729 align:start position:0% standards also very helpful results like some<03:38:38.069> of<03:38:38.189> these<03:38:38.279> issues<03:38:38.550> would<03:38:39.479> be<03:38:39.510> if<03:38:40.380> there 03:38:40.729 --> 03:38:40.739 align:start position:0% some of these issues would be if there 03:38:40.739 --> 03:38:41.969 align:start position:0% some of these issues would be if there be 03:38:41.969 --> 03:38:41.979 align:start position:0% be 03:38:41.979 --> 03:38:45.359 align:start position:0% be some<03:38:42.669> place<03:38:43.089> to<03:38:43.449> letting<03:38:44.219> publish<03:38:45.219> these 03:38:45.359 --> 03:38:45.369 align:start position:0% some place to letting publish these 03:38:45.369 --> 03:38:48.569 align:start position:0% some place to letting publish these things<03:38:45.669> and<03:38:45.939> I<03:38:46.810> know<03:38:47.529> that<03:38:47.739> like<03:38:48.039> these<03:38:48.369> places 03:38:48.569 --> 03:38:48.579 align:start position:0% things and I know that like these places 03:38:48.579 --> 03:38:50.189 align:start position:0% things and I know that like these places exist<03:38:48.759> you<03:38:49.270> know<03:38:49.299> you<03:38:49.509> could<03:38:49.749> just<03:38:49.930> you<03:38:50.140> could 03:38:50.189 --> 03:38:50.199 align:start position:0% exist you know you could just you could 03:38:50.199 --> 03:38:56.010 align:start position:0% exist you know you could just you could just<03:38:50.529> go<03:38:50.680> through<03:38:50.949> my<03:38:51.009> testing<03:38:54.539> for<03:38:55.539> example 03:38:56.010 --> 03:38:56.020 align:start position:0% just go through my testing for example 03:38:56.020 --> 03:38:59.099 align:start position:0% just go through my testing for example it's<03:38:56.619> just<03:38:56.739> that<03:38:57.159> for<03:38:57.909> a<03:38:58.299> lot<03:38:58.629> of<03:38:58.659> people<03:38:58.989> in 03:38:59.099 --> 03:38:59.109 align:start position:0% it's just that for a lot of people in 03:38:59.109 --> 03:39:04.769 align:start position:0% it's just that for a lot of people in this<03:39:00.359> community<03:39:01.359> also<03:39:01.899> very<03:39:02.259> like<03:39:03.779> mutilating 03:39:04.769 --> 03:39:04.779 align:start position:0% this community also very like mutilating 03:39:04.779 --> 03:39:07.109 align:start position:0% this community also very like mutilating internet<03:39:05.649> in<03:39:06.249> general<03:39:06.399> and<03:39:06.819> might<03:39:06.969> not 03:39:07.109 --> 03:39:07.119 align:start position:0% internet in general and might not 03:39:07.119 --> 03:39:08.639 align:start position:0% internet in general and might not actually<03:39:07.329> you<03:39:07.689> know<03:39:07.810> like<03:39:07.839> you<03:39:08.109> know<03:39:08.199> I'll<03:39:08.439> get 03:39:08.639 --> 03:39:08.649 align:start position:0% actually you know like you know I'll get 03:39:08.649 --> 03:39:10.920 align:start position:0% actually you know like you know I'll get into<03:39:09.009> these<03:39:09.129> kinds<03:39:09.459> of<03:39:09.520> things<03:39:09.699> so<03:39:09.999> it<03:39:10.689> is<03:39:10.779> the 03:39:10.920 --> 03:39:10.930 align:start position:0% into these kinds of things so it is the 03:39:10.930 --> 03:39:13.050 align:start position:0% into these kinds of things so it is the forever<03:39:11.229> like<03:39:11.739> it<03:39:11.890> has<03:39:12.039> a<03:39:12.069> bit<03:39:12.249> of<03:39:12.279> a<03:39:12.459> traffic 03:39:13.050 --> 03:39:13.060 align:start position:0% forever like it has a bit of a traffic 03:39:13.060 --> 03:39:16.349 align:start position:0% forever like it has a bit of a traffic problem<03:39:14.399> so<03:39:15.399> you<03:39:15.430> could<03:39:15.789> either<03:39:15.969> just<03:39:16.239> for 03:39:16.349 --> 03:39:16.359 align:start position:0% problem so you could either just for 03:39:16.359 --> 03:39:18.840 align:start position:0% problem so you could either just for your<03:39:16.689> own<03:39:16.810> standards<03:39:17.379> organization<03:39:18.009> which<03:39:18.699> is 03:39:18.840 --> 03:39:18.850 align:start position:0% your own standards organization which is 03:39:18.850 --> 03:39:20.579 align:start position:0% your own standards organization which is chrome<03:39:19.119> at<03:39:19.239> an<03:39:19.359> existing<03:39:19.659> one<03:39:20.109> but<03:39:20.319> then 03:39:20.579 --> 03:39:20.589 align:start position:0% chrome at an existing one but then 03:39:20.589 --> 03:39:24.739 align:start position:0% chrome at an existing one but then somehow<03:39:20.890> make<03:39:21.310> it<03:39:21.339> so<03:39:21.640> that<03:39:21.669> I<03:39:21.909> can 03:39:24.739 --> 03:39:24.749 align:start position:0% 03:39:24.749 --> 03:39:31.019 align:start position:0% what<03:39:25.749> about<03:39:25.869> doing<03:39:26.199> at<03:39:26.350> our<03:39:30.029> implement 03:39:31.019 --> 03:39:31.029 align:start position:0% what about doing at our implement 03:39:31.029 --> 03:39:34.170 align:start position:0% what about doing at our implement sensitive<03:39:31.829> document<03:39:32.829> to<03:39:33.100> get<03:39:33.219> some<03:39:33.459> key<03:39:33.999> with 03:39:34.170 --> 03:39:34.180 align:start position:0% sensitive document to get some key with 03:39:34.180 --> 03:39:35.679 align:start position:0% sensitive document to get some key with the 03:39:35.679 --> 03:39:35.689 align:start position:0% the 03:39:35.689 --> 03:39:38.389 align:start position:0% the except<03:39:36.689> you're<03:39:36.870> starting<03:39:37.739> with<03:39:37.770> JavaScript 03:39:38.389 --> 03:39:38.399 align:start position:0% except you're starting with JavaScript 03:39:38.399 --> 03:39:40.399 align:start position:0% except you're starting with JavaScript or<03:39:38.550> something<03:39:38.760> like<03:39:38.850> that<03:39:38.939> you're<03:39:39.779> avoiding 03:39:40.399 --> 03:39:40.409 align:start position:0% or something like that you're avoiding 03:39:40.409 --> 03:39:42.349 align:start position:0% or something like that you're avoiding my<03:39:40.710> sister<03:39:41.040> didn't<03:39:41.250> take<03:39:41.609> it<03:39:41.729> difficulty 03:39:42.349 --> 03:39:42.359 align:start position:0% my sister didn't take it difficulty 03:39:42.359 --> 03:39:45.320 align:start position:0% my sister didn't take it difficulty music<03:39:42.659> go<03:39:44.120> okay 03:39:45.320 --> 03:39:45.330 align:start position:0% music go okay 03:39:45.330 --> 03:39:47.599 align:start position:0% music go okay geillis<03:39:45.659> listen<03:39:46.170> I<03:39:46.680> know<03:39:47.189> we've<03:39:47.340> done<03:39:47.370> a<03:39:47.520> lot 03:39:47.599 --> 03:39:47.609 align:start position:0% geillis listen I know we've done a lot 03:39:47.609 --> 03:39:49.760 align:start position:0% geillis listen I know we've done a lot of<03:39:47.819> problems<03:39:48.180> but<03:39:48.359> I<03:39:48.600> think<03:39:48.720> in<03:39:49.319> this<03:39:49.470> section 03:39:49.760 --> 03:39:49.770 align:start position:0% of problems but I think in this section 03:39:49.770 --> 03:39:51.290 align:start position:0% of problems but I think in this section we're<03:39:49.979> gonna<03:39:50.130> train<03:39:50.489> for<03:39:50.850> every<03:39:50.909> one<03:39:51.120> into 03:39:51.290 --> 03:39:51.300 align:start position:0% we're gonna train for every one into 03:39:51.300 --> 03:39:54.320 align:start position:0% we're gonna train for every one into Center<03:39:51.529> we're<03:39:52.529> talking<03:39:53.279> about<03:39:53.430> solutions<03:39:54.149> to 03:39:54.320 --> 03:39:54.330 align:start position:0% Center we're talking about solutions to 03:39:54.330 --> 03:39:55.969 align:start position:0% Center we're talking about solutions to the<03:39:54.420> issue<03:39:54.569> of<03:39:54.689> like<03:39:54.899> the<03:39:55.020> fragmentation<03:39:55.859> and 03:39:55.969 --> 03:39:55.979 align:start position:0% the issue of like the fragmentation and 03:39:55.979 --> 03:39:57.769 align:start position:0% the issue of like the fragmentation and the<03:39:56.069> preference<03:39:56.460> base<03:39:56.640> and<03:39:57.330> how<03:39:57.449> to<03:39:57.510> make<03:39:57.689> it 03:39:57.769 --> 03:39:57.779 align:start position:0% the preference base and how to make it 03:39:57.779 --> 03:40:00.500 align:start position:0% the preference base and how to make it easy<03:39:57.960> for<03:39:58.109> new<03:39:58.380> people<03:39:58.529> to<03:39:58.710> get<03:39:58.920> involved<03:39:59.510> as 03:40:00.500 --> 03:40:00.510 align:start position:0% easy for new people to get involved as 03:40:00.510 --> 03:40:02.330 align:start position:0% easy for new people to get involved as well<03:40:00.689> as<03:40:00.840> like<03:40:01.050> solves<03:40:01.770> for<03:40:01.859> the<03:40:02.010> questions 03:40:02.330 --> 03:40:02.340 align:start position:0% well as like solves for the questions 03:40:02.340 --> 03:40:05.149 align:start position:0% well as like solves for the questions around<03:40:02.689> funding<03:40:03.689> and<03:40:03.870> standards<03:40:04.260> like<03:40:04.979> that 03:40:05.149 --> 03:40:05.159 align:start position:0% around funding and standards like that 03:40:05.159 --> 03:40:07.960 align:start position:0% around funding and standards like that sensible<03:40:05.819> the<03:40:06.120> solution<03:40:06.510> is<03:40:06.600> not<03:40:06.750> very<03:40:07.109> simple 03:40:07.960 --> 03:40:07.970 align:start position:0% sensible the solution is not very simple 03:40:07.970 --> 03:40:09.889 align:start position:0% sensible the solution is not very simple example<03:40:08.970> for<03:40:09.090> tech<03:40:09.270> that<03:40:09.420> you<03:40:09.449> get<03:40:09.630> kind<03:40:09.870> of 03:40:09.889 --> 03:40:09.899 align:start position:0% example for tech that you get kind of 03:40:09.899 --> 03:40:11.630 align:start position:0% example for tech that you get kind of made<03:40:10.080> that<03:40:10.590> will<03:40:10.739> be<03:40:10.859> coming<03:40:11.040> across<03:40:11.279> every 03:40:11.630 --> 03:40:11.640 align:start position:0% made that will be coming across every 03:40:11.640 --> 03:40:15.800 align:start position:0% made that will be coming across every action<03:40:12.149> cool<03:40:13.640> we're<03:40:14.640> gonna<03:40:14.760> have<03:40:14.939> 20<03:40:15.210> 20<03:40:15.689> more 03:40:15.800 --> 03:40:15.810 align:start position:0% action cool we're gonna have 20 20 more 03:40:15.810 --> 03:40:20.600 align:start position:0% action cool we're gonna have 20 20 more minutes 03:40:20.600 --> 03:40:20.610 align:start position:0% 03:40:20.610 --> 03:40:23.240 align:start position:0% I<03:40:20.640> think<03:40:21.330> first<03:40:21.900> of<03:40:22.050> all<03:40:22.170> I<03:40:22.260> think<03:40:22.320> it's<03:40:22.920> fine 03:40:23.240 --> 03:40:23.250 align:start position:0% I think first of all I think it's fine 03:40:23.250 --> 03:40:27.290 align:start position:0% I think first of all I think it's fine if<03:40:23.280> we<03:40:23.430> have<03:40:23.700> some<03:40:24.600> level<03:40:24.900> of<03:40:26.300> fragmentation 03:40:27.290 --> 03:40:27.300 align:start position:0% if we have some level of fragmentation 03:40:27.300 --> 03:40:28.479 align:start position:0% if we have some level of fragmentation and<03:40:27.690> expiry 03:40:28.479 --> 03:40:28.489 align:start position:0% and expiry 03:40:28.489 --> 03:40:30.100 align:start position:0% and expiry it's<03:40:28.850> true 03:40:30.100 --> 03:40:30.110 align:start position:0% it's true 03:40:30.110 --> 03:40:33.050 align:start position:0% it's true we're<03:40:30.470> trying<03:40:30.710> out<03:40:30.920> different<03:40:30.950> things<03:40:31.370> in 03:40:33.050 --> 03:40:33.060 align:start position:0% we're trying out different things in 03:40:33.060 --> 03:40:36.030 align:start position:0% we're trying out different things in but<03:40:34.060> it's<03:40:34.450> also<03:40:34.630> useful<03:40:34.900> to<03:40:35.350> have<03:40:35.650> any 03:40:36.030 --> 03:40:36.040 align:start position:0% but it's also useful to have any 03:40:36.040 --> 03:40:41.930 align:start position:0% but it's also useful to have any companies 03:40:41.930 --> 03:40:41.940 align:start position:0% 03:40:41.940 --> 03:40:47.830 align:start position:0% eventually<03:40:43.351> the<03:40:44.351> most<03:40:45.190> successful 03:40:47.830 --> 03:40:47.840 align:start position:0% eventually the most successful 03:40:47.840 --> 03:40:50.120 align:start position:0% eventually the most successful the<03:40:48.840> solution<03:40:49.290> is<03:40:49.410> going<03:40:49.529> to<03:40:49.620> be<03:40:49.680> about<03:40:49.920> that 03:40:50.120 --> 03:40:50.130 align:start position:0% the solution is going to be about that 03:40:50.130 --> 03:40:57.881 align:start position:0% the solution is going to be about that but<03:40:50.430> I<03:40:50.670> think<03:40:50.910> we're<03:40:51.239> at<03:40:51.330> the<03:40:51.450> stage<03:40:51.479> where 03:40:57.881 --> 03:40:57.891 align:start position:0% 03:40:57.891 --> 03:41:03.440 align:start position:0% okay<03:40:59.361> so<03:41:00.381> we 03:41:03.440 --> 03:41:03.450 align:start position:0% 03:41:03.450 --> 03:41:06.830 align:start position:0% and<03:41:03.570> the<03:41:03.810> solution<03:41:04.200> is<03:41:04.320> is<03:41:04.650> to<03:41:05.280> have<03:41:06.240> an 03:41:06.830 --> 03:41:06.840 align:start position:0% and the solution is is to have an 03:41:06.840 --> 03:41:09.410 align:start position:0% and the solution is is to have an activator<03:41:07.500> please<03:41:07.950> look<03:41:08.340> at<03:41:08.520> organization 03:41:09.410 --> 03:41:09.420 align:start position:0% activator please look at organization 03:41:09.420 --> 03:41:29.320 align:start position:0% activator please look at organization yeah<03:41:09.660> where<03:41:09.840> we<03:41:09.990> can<03:41:12.560> stand<03:41:13.560> there's<03:41:13.860> funding 03:41:29.320 --> 03:41:29.330 align:start position:0% 03:41:29.330 --> 03:41:36.480 align:start position:0% for<03:41:30.260> what 03:41:36.480 --> 03:41:36.490 align:start position:0% 03:41:36.490 --> 03:41:39.000 align:start position:0% come<03:41:37.000> here 03:41:39.000 --> 03:41:39.010 align:start position:0% come here 03:41:39.010 --> 03:41:42.389 align:start position:0% come here I<03:41:39.039> mean<03:41:39.909> I'm<03:41:40.060> imagining<03:41:40.479> maybe<03:41:40.869> for<03:41:41.859> me<03:41:42.010> the 03:41:42.389 --> 03:41:42.399 align:start position:0% I mean I'm imagining maybe for me the 03:41:42.399 --> 03:41:44.910 align:start position:0% I mean I'm imagining maybe for me the quickest<03:41:43.210> way<03:41:43.300> that<03:41:44.140> I<03:41:44.229> think<03:41:44.289> matches<03:41:44.800> the 03:41:44.910 --> 03:41:44.920 align:start position:0% quickest way that I think matches the 03:41:44.920 --> 03:41:47.819 align:start position:0% quickest way that I think matches the depleting<03:41:45.640> projects<03:41:46.180> they<03:41:46.659> may<03:41:46.840> be<03:41:46.899> taken<03:41:47.319> all 03:41:47.819 --> 03:41:47.829 align:start position:0% depleting projects they may be taken all 03:41:47.829 --> 03:41:50.140 align:start position:0% depleting projects they may be taken all the<03:41:48.220> they<03:41:48.579> talk<03:41:48.760> to<03:41:48.850> each<03:41:48.909> other 03:41:50.140 --> 03:41:50.150 align:start position:0% the they talk to each other 03:41:50.150 --> 03:41:52.330 align:start position:0% the they talk to each other thank<03:41:50.780> you<03:41:51.021> their<03:41:51.380> funding<03:41:51.860> to<03:41:51.890> put<03:41:52.220> it 03:41:52.330 --> 03:41:52.340 align:start position:0% thank you their funding to put it 03:41:52.340 --> 03:41:55.600 align:start position:0% thank you their funding to put it together<03:41:52.460> and<03:41:52.940> say<03:41:53.450> that<03:41:53.750> some<03:41:54.070> rusty<03:41:55.070> vigil 03:41:55.600 --> 03:41:55.610 align:start position:0% together and say that some rusty vigil 03:41:55.610 --> 03:41:58.810 align:start position:0% together and say that some rusty vigil or<03:41:55.940> maybe<03:41:56.210> small<03:41:56.630> teeth<03:41:56.930> posed<03:41:57.650> interviews<03:41:58.610> or 03:41:58.810 --> 03:41:58.820 align:start position:0% or maybe small teeth posed interviews or 03:41:58.820 --> 03:42:02.350 align:start position:0% or maybe small teeth posed interviews or research<03:41:59.150> is<03:41:59.330> reduced<03:41:59.690> in<03:42:00.320> comparison<03:42:00.760> if<03:42:01.760> the 03:42:02.350 --> 03:42:02.360 align:start position:0% research is reduced in comparison if the 03:42:02.360 --> 03:42:04.270 align:start position:0% research is reduced in comparison if the team's<03:42:02.601> agreed<03:42:02.900> in<03:42:03.140> just<03:42:03.320> yet<03:42:03.710> for<03:42:03.830> all<03:42:04.130> their 03:42:04.270 --> 03:42:04.280 align:start position:0% team's agreed in just yet for all their 03:42:04.280 --> 03:42:06.640 align:start position:0% team's agreed in just yet for all their documentation<03:42:04.790> that<03:42:05.120> particular<03:42:05.720> github 03:42:06.640 --> 03:42:06.650 align:start position:0% documentation that particular github 03:42:06.650 --> 03:42:09.310 align:start position:0% documentation that particular github repo<03:42:07.010> or<03:42:07.160> whatever<03:42:07.400> it<03:42:07.580> is<03:42:07.840> just<03:42:08.840> a<03:42:08.930> quick<03:42:09.140> way 03:42:09.310 --> 03:42:09.320 align:start position:0% repo or whatever it is just a quick way 03:42:09.320 --> 03:42:11.380 align:start position:0% repo or whatever it is just a quick way to<03:42:09.561> start<03:42:09.830> so<03:42:10.130> this<03:42:10.250> is<03:42:10.400> comparison<03:42:10.940> I<03:42:11.030> have<03:42:11.061> no 03:42:11.380 --> 03:42:11.390 align:start position:0% to start so this is comparison I have no 03:42:11.390 --> 03:42:13.511 align:start position:0% to start so this is comparison I have no idea<03:42:11.811> maybe<03:42:12.140> they<03:42:12.380> could<03:42:12.561> pull<03:42:12.771> in<03:42:12.890> funds<03:42:13.250> and 03:42:13.511 --> 03:42:13.521 align:start position:0% idea maybe they could pull in funds and 03:42:13.521 --> 03:42:15.490 align:start position:0% idea maybe they could pull in funds and figure<03:42:13.760> out<03:42:13.880> what<03:42:14.150> will<03:42:14.300> be<03:42:14.420> all<03:42:14.630> need<03:42:15.230> and 03:42:15.490 --> 03:42:15.500 align:start position:0% figure out what will be all need and 03:42:15.500 --> 03:42:52.770 align:start position:0% figure out what will be all need and then<03:42:31.030> one<03:42:32.030> thing<03:42:32.210> that<03:42:32.950> is 03:42:52.770 --> 03:42:52.780 align:start position:0% 03:42:52.780 --> 03:43:01.171 align:start position:0% offering<03:42:53.780> that<03:42:53.961> across<03:42:54.261> all<03:42:54.320> just<03:42:54.891> universe 03:43:01.171 --> 03:43:01.181 align:start position:0% 03:43:01.181 --> 03:43:11.210 align:start position:0% thanks<03:43:02.181> for<03:43:02.330> ditching<03:43:02.570> way<03:43:02.950> protectively 03:43:11.210 --> 03:43:11.220 align:start position:0% 03:43:11.220 --> 03:43:16.920 align:start position:0% who's<03:43:12.220> here<03:43:12.490> for<03:43:12.670> the<03:43:12.730> next<03:43:13.060> floor<03:43:15.930> treatments 03:43:16.920 --> 03:43:16.930 align:start position:0% who's here for the next floor treatments 03:43:16.930 --> 03:43:22.620 align:start position:0% who's here for the next floor treatments like<03:43:17.021> on<03:43:17.230> my<03:43:17.950> part 03:43:22.620 --> 03:43:22.630 align:start position:0% 03:43:22.630 --> 03:43:25.710 align:start position:0% I<03:43:22.660> don't<03:43:23.560> think<03:43:23.620> a<03:43:23.771> lot<03:43:24.070> of<03:43:24.310> Fundy<03:43:24.820> was<03:43:25.450> that 03:43:25.710 --> 03:43:25.720 align:start position:0% I don't think a lot of Fundy was that 03:43:25.720 --> 03:43:28.590 align:start position:0% I don't think a lot of Fundy was that may<03:43:25.870> issue<03:43:26.110> wipe<03:43:26.470> these<03:43:27.600> ecosystem 03:43:28.590 --> 03:43:28.600 align:start position:0% may issue wipe these ecosystem 03:43:28.600 --> 03:43:31.241 align:start position:0% may issue wipe these ecosystem oversharing 03:43:31.241 --> 03:43:31.251 align:start position:0% 03:43:31.251 --> 03:43:40.541 align:start position:0% we<03:43:31.551> have<03:43:31.791> been<03:43:32.001> like<03:43:38.171> and<03:43:39.171> also<03:43:39.411> I<03:43:39.561> think<03:43:40.251> like 03:43:40.541 --> 03:43:40.551 align:start position:0% we have been like and also I think like 03:43:40.551 --> 03:43:43.411 align:start position:0% we have been like and also I think like you<03:43:40.911> very<03:43:41.541> surprised<03:43:41.871> at<03:43:42.110> how<03:43:42.261> little<03:43:42.621> cost 03:43:43.411 --> 03:43:43.421 align:start position:0% you very surprised at how little cost 03:43:43.421 --> 03:43:46.270 align:start position:0% you very surprised at how little cost for<03:43:44.421> each<03:43:44.631> project<03:43:44.990> to<03:43:45.771> have<03:43:45.980> just<03:43:46.221> like 03:43:46.270 --> 03:43:46.280 align:start position:0% for each project to have just like 03:43:46.280 --> 03:43:48.701 align:start position:0% for each project to have just like community<03:43:46.940> people<03:43:47.271> even<03:43:47.961> wanted<03:43:48.320> to<03:43:48.501> like 03:43:48.701 --> 03:43:48.711 align:start position:0% community people even wanted to like 03:43:48.711 --> 03:43:55.751 align:start position:0% community people even wanted to like study<03:43:50.320> issues<03:43:51.820> and<03:43:53.320> I<03:43:54.320> mean<03:43:55.011> there's<03:43:55.551> another 03:43:55.751 --> 03:43:55.761 align:start position:0% study issues and I mean there's another 03:43:55.761 --> 03:43:59.020 align:start position:0% study issues and I mean there's another problem<03:43:56.240> for<03:43:56.650> which<03:43:57.650> like<03:43:57.860> the<03:43:58.131> each<03:43:58.730> project 03:43:59.020 --> 03:43:59.030 align:start position:0% problem for which like the each project 03:43:59.030 --> 03:44:01.871 align:start position:0% problem for which like the each project I<03:43:59.541> went<03:44:00.501> through<03:44:00.650> that<03:44:00.801> my<03:44:01.251> voice<03:44:01.490> being<03:44:01.701> like 03:44:01.871 --> 03:44:01.881 align:start position:0% I went through that my voice being like 03:44:01.881 --> 03:44:03.730 align:start position:0% I went through that my voice being like we<03:44:02.091> were<03:44:02.240> implementing<03:44:02.661> the<03:44:02.931> best<03:44:03.201> process 03:44:03.730 --> 03:44:03.740 align:start position:0% we were implementing the best process 03:44:03.740 --> 03:44:06.850 align:start position:0% we were implementing the best process for<03:44:03.771> our<03:44:04.161> project<03:44:05.021> we'll<03:44:06.021> get<03:44:06.171> a<03:44:06.201> doctor 03:44:06.850 --> 03:44:06.860 align:start position:0% for our project we'll get a doctor 03:44:06.860 --> 03:44:09.191 align:start position:0% for our project we'll get a doctor so<03:44:07.521> you<03:44:07.730> know<03:44:07.851> like<03:44:08.001> this<03:44:08.211> like<03:44:08.451> no<03:44:08.721> I'm<03:44:08.990> not 03:44:09.191 --> 03:44:09.201 align:start position:0% so you know like this like no I'm not 03:44:09.201 --> 03:44:13.270 align:start position:0% so you know like this like no I'm not incentive<03:44:09.801> to<03:44:10.131> share<03:44:10.871> right<03:44:11.871> away<03:44:12.141> we<03:44:12.951> do<03:44:13.131> want 03:44:13.270 --> 03:44:13.280 align:start position:0% incentive to share right away we do want 03:44:13.280 --> 03:44:15.100 align:start position:0% incentive to share right away we do want to<03:44:13.311> share<03:44:13.490> later<03:44:13.791> after<03:44:14.421> the<03:44:14.541> fact<03:44:14.780> because 03:44:15.100 --> 03:44:15.110 align:start position:0% to share later after the fact because 03:44:15.110 --> 03:44:18.371 align:start position:0% to share later after the fact because then<03:44:15.530> you<03:44:15.740> get<03:44:15.860> a<03:44:15.921> selfie<03:44:16.581> on<03:44:16.610> the<03:44:17.331> credit<03:44:17.631> but 03:44:18.371 --> 03:44:18.381 align:start position:0% then you get a selfie on the credit but 03:44:18.381 --> 03:44:22.211 align:start position:0% then you get a selfie on the credit but before<03:44:18.711> the<03:44:18.801> fact<03:44:19.011> is<03:44:20.530> but<03:44:21.530> a<03:44:21.561> similar<03:44:21.891> thing 03:44:22.211 --> 03:44:22.221 align:start position:0% before the fact is but a similar thing 03:44:22.221 --> 03:44:27.161 align:start position:0% before the fact is but a similar thing like<03:44:22.461> it<03:44:23.391> does<03:44:24.881> and<03:44:25.881> the<03:44:26.121> Sun<03:44:26.570> biggest<03:44:26.900> issue<03:44:27.021> I 03:44:27.161 --> 03:44:27.171 align:start position:0% like it does and the Sun biggest issue I 03:44:27.171 --> 03:44:32.111 align:start position:0% like it does and the Sun biggest issue I saw<03:44:27.561> is<03:44:27.801> not<03:44:27.980> what<03:44:29.740> the<03:44:30.740> design<03:44:31.041> aspect<03:44:31.581> they 03:44:32.111 --> 03:44:32.121 align:start position:0% saw is not what the design aspect they 03:44:32.121 --> 03:44:34.961 align:start position:0% saw is not what the design aspect they were<03:44:32.271> sort<03:44:32.480> of<03:44:32.570> eight<03:44:32.721> or<03:44:33.141> more<03:44:33.201> like<03:44:33.711> what<03:44:34.671> are 03:44:34.961 --> 03:44:34.971 align:start position:0% were sort of eight or more like what are 03:44:34.971 --> 03:44:38.470 align:start position:0% were sort of eight or more like what are the<03:44:35.240> options<03:44:35.391> they<03:44:35.751> saw<03:44:36.201> that<03:44:37.011> you<03:44:37.161> refused<03:44:37.730> no 03:44:38.470 --> 03:44:38.480 align:start position:0% the options they saw that you refused no 03:44:38.480 --> 03:44:40.451 align:start position:0% the options they saw that you refused no you<03:44:38.961> need<03:44:39.171> it<03:44:39.201> and<03:44:39.591> then<03:44:39.650> why<03:44:40.131> I<03:44:40.371> think 03:44:40.451 --> 03:44:40.461 align:start position:0% you need it and then why I think 03:44:40.461 --> 03:44:42.161 align:start position:0% you need it and then why I think actually<03:44:40.730> that's<03:44:41.001> them<03:44:41.301> learning<03:44:41.601> like<03:44:41.841> them 03:44:42.161 --> 03:44:42.171 align:start position:0% actually that's them learning like them 03:44:42.171 --> 03:44:46.060 align:start position:0% actually that's them learning like them it's<03:44:42.711> like<03:44:42.860> this<03:44:43.131> Beach<03:44:43.690> like<03:44:44.690> that's<03:44:45.621> so<03:44:45.891> we 03:44:46.060 --> 03:44:46.070 align:start position:0% it's like this Beach like that's so we 03:44:46.070 --> 03:44:48.011 align:start position:0% it's like this Beach like that's so we don't<03:44:46.311> want<03:44:46.521> them<03:44:46.761> to<03:44:46.911> say<03:44:47.211> bye<03:44:47.451> before<03:44:47.511> like 03:44:48.011 --> 03:44:48.021 align:start position:0% don't want them to say bye before like 03:44:48.021 --> 03:44:48.801 align:start position:0% don't want them to say bye before like everybody 03:44:48.801 --> 03:44:48.811 align:start position:0% everybody 03:44:48.811 --> 03:44:51.140 align:start position:0% everybody because<03:44:49.500> no<03:44:49.740> one<03:44:49.920> explained<03:44:50.340> why<03:44:50.670> they<03:44:50.820> didn't 03:44:51.140 --> 03:44:51.150 align:start position:0% because no one explained why they didn't 03:44:51.150 --> 03:44:55.820 align:start position:0% because no one explained why they didn't choose<03:44:51.391> I<03:44:52.761> so<03:44:53.761> yes<03:44:54.511> I<03:44:54.690> if<03:44:55.050> we<03:44:55.110> just<03:44:55.471> come<03:44:55.710> up 03:44:55.820 --> 03:44:55.830 align:start position:0% choose I so yes I if we just come up 03:44:55.830 --> 03:44:58.580 align:start position:0% choose I so yes I if we just come up with<03:44:55.891> like<03:44:56.240> initial<03:44:57.240> for<03:44:57.391> all<03:44:57.540> those<03:44:57.811> cars<03:44:58.200> and 03:44:58.580 --> 03:44:58.590 align:start position:0% with like initial for all those cars and 03:44:58.590 --> 03:45:01.011 align:start position:0% with like initial for all those cars and how<03:44:59.280> do<03:44:59.641> we<03:44:59.761> spread<03:45:00.000> among<03:45:00.330> or<03:45:00.540> the<03:45:00.601> project 03:45:01.011 --> 03:45:01.021 align:start position:0% how do we spread among or the project 03:45:01.021 --> 03:45:02.631 align:start position:0% how do we spread among or the project thing<03:45:01.141> like<03:45:01.290> everybody<03:45:01.650> we<03:45:01.860> they<03:45:02.130> surprised 03:45:02.631 --> 03:45:02.641 align:start position:0% thing like everybody we they surprised 03:45:02.641 --> 03:45:05.830 align:start position:0% thing like everybody we they surprised us<03:45:02.910> more<03:45:03.210> is<03:45:03.511> there<03:45:03.690> to<03:45:03.931> share<03:45:04.410> learnings<03:45:04.950> yeah 03:45:05.830 --> 03:45:05.840 align:start position:0% us more is there to share learnings yeah 03:45:05.840 --> 03:45:10.850 align:start position:0% us more is there to share learnings yeah that's<03:45:06.840> that's<03:45:07.050> the<03:45:07.230> biggest<03:45:07.440> part<03:45:07.800> that<03:45:08.730> is<03:45:09.860> a 03:45:10.850 --> 03:45:10.860 align:start position:0% that's that's the biggest part that is a 03:45:10.860 --> 03:45:13.239 align:start position:0% that's that's the biggest part that is a lot<03:45:11.190> of<03:45:11.280> projects<03:45:11.700> point 03:45:13.239 --> 03:45:13.249 align:start position:0% lot of projects point 03:45:13.249 --> 03:45:17.809 align:start position:0% lot of projects point yeah<03:45:14.249> but<03:45:14.999> I'm<03:45:15.359> gonna<03:45:15.539> say<03:45:15.689> I<03:45:15.859> sort<03:45:16.859> of<03:45:16.919> did<03:45:17.789> it 03:45:17.809 --> 03:45:17.819 align:start position:0% yeah but I'm gonna say I sort of did it 03:45:17.819 --> 03:45:19.429 align:start position:0% yeah but I'm gonna say I sort of did it the<03:45:18.149> title<03:45:18.479> Asians<03:45:18.720> in<03:45:18.840> my<03:45:18.930> head<03:45:19.109> you<03:45:19.260> make 03:45:19.429 --> 03:45:19.439 align:start position:0% the title Asians in my head you make 03:45:19.439 --> 03:45:22.790 align:start position:0% the title Asians in my head you make something<03:45:20.399> out<03:45:20.729> likely<03:45:21.180> to<03:45:21.359> people<03:45:21.749> for<03:45:22.590> six 03:45:22.790 --> 03:45:22.800 align:start position:0% something out likely to people for six 03:45:22.800 --> 03:45:27.380 align:start position:0% something out likely to people for six months<03:45:23.659> pretty<03:45:24.659> good 03:45:27.380 --> 03:45:27.390 align:start position:0% 03:45:27.390 --> 03:45:38.600 align:start position:0% fifteen<03:45:28.390> more<03:45:28.540> minutes<03:45:34.439> our<03:45:35.439> ambush 03:45:38.600 --> 03:45:38.610 align:start position:0% 03:45:38.610 --> 03:45:41.310 align:start position:0% I<03:45:38.690> would<03:45:39.690> just<03:45:39.811> go<03:45:40.021> in<03:45:40.170> London 03:45:41.310 --> 03:45:41.320 align:start position:0% I would just go in London 03:45:41.320 --> 03:45:52.091 align:start position:0% I would just go in London [Music] 03:45:52.091 --> 03:45:52.101 align:start position:0% 03:45:52.101 --> 03:46:39.860 align:start position:0% it's<03:46:36.351> just<03:46:37.461> that<03:46:38.461> I<03:46:38.490> think<03:46:38.971> the<03:46:39.211> Dow<03:46:39.391> is<03:46:39.601> late 03:46:39.860 --> 03:46:39.870 align:start position:0% it's just that I think the Dow is late 03:46:39.870 --> 03:46:41.661 align:start position:0% it's just that I think the Dow is late potentially<03:46:40.320> actually<03:46:40.561> very<03:46:40.801> or<03:46:41.221> say<03:46:41.400> we 03:46:41.661 --> 03:46:41.671 align:start position:0% potentially actually very or say we 03:46:41.671 --> 03:46:42.951 align:start position:0% potentially actually very or say we should<03:46:41.820> probably<03:46:41.971> sort<03:46:42.271> more<03:46:42.391> generally<03:46:42.780> just 03:46:42.951 --> 03:46:42.961 align:start position:0% should probably sort more generally just 03:46:42.961 --> 03:46:45.130 align:start position:0% should probably sort more generally just defining<03:46:43.351> what 03:46:45.130 --> 03:46:45.140 align:start position:0% defining what 03:46:45.140 --> 03:46:54.740 align:start position:0% defining what maybe<03:46:45.499> find<03:46:45.919> a<03:46:46.039> lotta<03:46:46.249> pieces<03:46:46.760> here 03:46:54.740 --> 03:46:54.750 align:start position:0% 03:46:54.750 --> 03:46:56.729 align:start position:0% what<03:46:55.750> is<03:46:55.869> up<03:46:55.989> here<03:46:56.170> those<03:46:56.350> are<03:46:56.380> things<03:46:56.680> that 03:46:56.729 --> 03:46:56.739 align:start position:0% what is up here those are things that 03:46:56.739 --> 03:46:59.849 align:start position:0% what is up here those are things that are<03:46:56.890> my<03:46:57.930> priorities<03:46:58.930> if<03:46:59.199> I<03:46:59.319> had<03:46:59.500> been 03:46:59.849 --> 03:46:59.859 align:start position:0% are my priorities if I had been 03:46:59.859 --> 03:47:01.620 align:start position:0% are my priorities if I had been declining 03:47:01.620 --> 03:47:01.630 align:start position:0% declining 03:47:01.630 --> 03:47:05.710 align:start position:0% declining yeah<03:47:02.630> I<03:47:03.200> was<03:47:03.440> gonna<03:47:03.620> say<03:47:03.771> well<03:47:04.670> had<03:47:05.330> something 03:47:05.710 --> 03:47:05.720 align:start position:0% yeah I was gonna say well had something 03:47:05.720 --> 03:47:09.100 align:start position:0% yeah I was gonna say well had something to<03:47:05.840> listen<03:47:06.260> said<03:47:06.440> it<03:47:06.530> was<03:47:06.620> something<03:47:06.950> but<03:47:08.110> yeah 03:47:09.100 --> 03:47:09.110 align:start position:0% to listen said it was something but yeah 03:47:09.110 --> 03:47:12.820 align:start position:0% to listen said it was something but yeah I<03:47:09.200> really<03:47:09.620> think<03:47:09.860> having<03:47:10.101> an<03:47:11.090> initial<03:47:11.480> scan<03:47:12.260> of 03:47:12.820 --> 03:47:12.830 align:start position:0% I really think having an initial scan of 03:47:12.830 --> 03:47:15.220 align:start position:0% I really think having an initial scan of the<03:47:13.101> committee<03:47:13.490> and<03:47:14.330> funding<03:47:14.750> that<03:47:14.900> through 03:47:15.220 --> 03:47:15.230 align:start position:0% the committee and funding that through 03:47:15.230 --> 03:47:17.230 align:start position:0% the committee and funding that through the<03:47:15.620> communities<03:47:16.101> like<03:47:16.311> the<03:47:16.700> projects<03:47:17.181> that 03:47:17.230 --> 03:47:17.240 align:start position:0% the communities like the projects that 03:47:17.240 --> 03:47:19.690 align:start position:0% the communities like the projects that have<03:47:17.840> a<03:47:18.200> lot<03:47:18.410> more<03:47:18.440> money<03:47:18.740> to<03:47:19.220> spend<03:47:19.340> like 03:47:19.690 --> 03:47:19.700 align:start position:0% have a lot more money to spend like 03:47:19.700 --> 03:47:23.770 align:start position:0% have a lot more money to spend like maybe<03:47:19.910> they<03:47:20.090> convention<03:47:20.570> like<03:47:21.730> 30k<03:47:22.730> to<03:47:23.630> pay 03:47:23.770 --> 03:47:23.780 align:start position:0% maybe they convention like 30k to pay 03:47:23.780 --> 03:47:27.911 align:start position:0% maybe they convention like 30k to pay for<03:47:23.990> some<03:47:24.110> of<03:47:24.230> the<03:47:24.290> work<03:47:24.440> of<03:47:24.561> the<03:47:24.650> specialist 03:47:27.911 --> 03:47:27.921 align:start position:0% 03:47:27.921 --> 03:47:32.060 align:start position:0% so<03:47:28.921> I<03:47:29.221> would<03:47:30.061> say<03:47:30.240> like<03:47:30.480> an<03:47:31.261> initial<03:47:31.710> report 03:47:32.060 --> 03:47:32.070 align:start position:0% so I would say like an initial report 03:47:32.070 --> 03:47:35.450 align:start position:0% so I would say like an initial report and<03:47:32.400> maybe<03:47:32.761> also<03:47:33.000> like<03:47:34.221> something's<03:47:35.221> like<03:47:35.341> an 03:47:35.450 --> 03:47:35.460 align:start position:0% and maybe also like something's like an 03:47:35.460 --> 03:47:37.190 align:start position:0% and maybe also like something's like an investigative<03:47:36.120> report<03:47:36.450> that<03:47:36.690> like<03:47:36.811> comes<03:47:37.051> out 03:47:37.190 --> 03:47:37.200 align:start position:0% investigative report that like comes out 03:47:37.200 --> 03:47:42.140 align:start position:0% investigative report that like comes out with<03:47:37.351> like<03:47:37.471> some<03:47:37.650> Doc's<03:47:37.971> maybe<03:47:39.830> and<03:47:40.940> then<03:47:41.940> like 03:47:42.140 --> 03:47:42.150 align:start position:0% with like some Doc's maybe and then like 03:47:42.150 --> 03:47:54.110 align:start position:0% with like some Doc's maybe and then like an<03:47:42.601> event<03:47:43.730> you<03:47:44.730> like<03:47:44.940> get<03:47:45.721> everybody<03:47:53.120> sharing 03:47:54.110 --> 03:47:54.120 align:start position:0% an event you like get everybody sharing 03:47:54.120 --> 03:47:58.700 align:start position:0% an event you like get everybody sharing roadmaps<03:47:55.610> around<03:47:56.780> sharing<03:47:57.780> the<03:47:58.021> road<03:47:58.261> map<03:47:58.500> I 03:47:58.700 --> 03:47:58.710 align:start position:0% roadmaps around sharing the road map I 03:47:58.710 --> 03:47:59.270 align:start position:0% roadmaps around sharing the road map I mean 03:47:59.270 --> 03:47:59.280 align:start position:0% mean 03:47:59.280 --> 03:48:01.820 align:start position:0% mean road<03:47:59.490> maps<03:47:59.881> is<03:48:00.030> this<03:48:00.240> something<03:48:00.710> opening<03:48:01.710> up 03:48:01.820 --> 03:48:01.830 align:start position:0% road maps is this something opening up 03:48:01.830 --> 03:48:05.281 align:start position:0% road maps is this something opening up hiring<03:48:02.400> a<03:48:02.551> debate 03:48:05.281 --> 03:48:05.291 align:start position:0% 03:48:05.291 --> 03:48:07.661 align:start position:0% the<03:48:06.291> commitment<03:48:06.681> just<03:48:06.711> means<03:48:06.980> like<03:48:07.071> I'm<03:48:07.491> gonna 03:48:07.661 --> 03:48:07.671 align:start position:0% the commitment just means like I'm gonna 03:48:07.671 --> 03:48:12.241 align:start position:0% the commitment just means like I'm gonna start<03:48:07.911> streaming<03:48:08.561> r5b<03:48:09.561> please<03:48:09.951> and<03:48:10.311> those<03:48:10.491> are 03:48:12.241 --> 03:48:12.251 align:start position:0% start streaming r5b please and those are 03:48:12.251 --> 03:48:21.519 align:start position:0% start streaming r5b please and those are you<03:48:12.371> know<03:48:12.490> it's<03:48:12.701> pretty<03:48:12.940> I<03:48:16.980> think<03:48:18.990> advertising 03:48:21.519 --> 03:48:21.529 align:start position:0% you know it's pretty I think advertising 03:48:21.529 --> 03:48:26.149 align:start position:0% you know it's pretty I think advertising Curren<03:48:22.859> don't<03:48:23.369> worry<03:48:24.499> the<03:48:25.499> technologists 03:48:26.149 --> 03:48:26.159 align:start position:0% Curren don't worry the technologists 03:48:26.159 --> 03:48:28.489 align:start position:0% Curren don't worry the technologists already<03:48:26.579> have<03:48:26.789> in<03:48:26.970> this<03:48:27.090> field<03:48:27.359> will<03:48:28.079> help<03:48:28.289> you 03:48:28.489 --> 03:48:28.499 align:start position:0% already have in this field will help you 03:48:28.499 --> 03:48:30.529 align:start position:0% already have in this field will help you find<03:48:28.829> the<03:48:29.100> real<03:48:29.249> problems<03:48:29.760> under<03:48:30.090> this<03:48:30.239> list 03:48:30.529 --> 03:48:30.539 align:start position:0% find the real problems under this list 03:48:30.539 --> 03:48:34.460 align:start position:0% find the real problems under this list first<03:48:30.810> and<03:48:31.680> then<03:48:32.129> the<03:48:32.279> funding<03:48:32.899> so<03:48:33.899> everyone 03:48:34.460 --> 03:48:34.470 align:start position:0% first and then the funding so everyone 03:48:34.470 --> 03:48:36.710 align:start position:0% first and then the funding so everyone is<03:48:34.619> the<03:48:34.739> first<03:48:34.979> time<03:48:35.159> you<03:48:35.760> should<03:48:35.789> just<03:48:36.329> over 03:48:36.710 --> 03:48:36.720 align:start position:0% is the first time you should just over 03:48:36.720 --> 03:48:39.080 align:start position:0% is the first time you should just over finish<03:48:37.020> what<03:48:37.199> you<03:48:37.289> have<03:48:37.879> advertisement<03:48:38.879> unit 03:48:39.080 --> 03:48:39.090 align:start position:0% finish what you have advertisement unit 03:48:39.090 --> 03:48:45.889 align:start position:0% finish what you have advertisement unit yeah<03:48:39.479> more<03:48:40.109> like<03:48:43.039> yes<03:48:44.419> just<03:48:45.419> to<03:48:45.539> go<03:48:45.629> back<03:48:45.779> to 03:48:45.889 --> 03:48:45.899 align:start position:0% yeah more like yes just to go back to 03:48:45.899 --> 03:48:47.779 align:start position:0% yeah more like yes just to go back to them<03:48:46.050> just<03:48:46.619> say<03:48:46.770> no<03:48:46.859> myself<03:48:47.220> problem<03:48:47.520> section 03:48:47.779 --> 03:48:47.789 align:start position:0% them just say no myself problem section 03:48:47.789 --> 03:48:49.909 align:start position:0% them just say no myself problem section under<03:48:47.939> protect<03:48:48.300> pens<03:48:48.510> like<03:48:48.629> I<03:48:48.989> think<03:48:49.499> what<03:48:49.649> a 03:48:49.909 --> 03:48:49.919 align:start position:0% under protect pens like I think what a 03:48:49.919 --> 03:48:52.130 align:start position:0% under protect pens like I think what a lot<03:48:50.039> of<03:48:50.159> people<03:48:50.249> of<03:48:50.459> Reyes<03:48:50.669> was<03:48:50.970> that<03:48:51.810> a 03:48:52.130 --> 03:48:52.140 align:start position:0% lot of people of Reyes was that a 03:48:52.140 --> 03:48:54.679 align:start position:0% lot of people of Reyes was that a project<03:48:52.949> can't<03:48:53.550> necessarily<03:48:53.819> or<03:48:54.359> doesn't 03:48:54.679 --> 03:48:54.689 align:start position:0% project can't necessarily or doesn't 03:48:54.689 --> 03:48:56.630 align:start position:0% project can't necessarily or doesn't necessarily<03:48:55.140> a<03:48:55.169> time<03:48:55.470> or<03:48:55.739> one<03:48:55.919> prioritize 03:48:56.630 --> 03:48:56.640 align:start position:0% necessarily a time or one prioritize 03:48:56.640 --> 03:48:59.300 align:start position:0% necessarily a time or one prioritize often<03:48:57.029> that<03:48:57.779> sort<03:48:57.989> of<03:48:58.020> work<03:48:58.229> because<03:48:58.619> they're 03:48:59.300 --> 03:48:59.310 align:start position:0% often that sort of work because they're 03:48:59.310 --> 03:49:00.939 align:start position:0% often that sort of work because they're already<03:48:59.430> getting<03:48:59.609> clients<03:48:59.909> or<03:49:00.270> something<03:49:00.569> so 03:49:00.939 --> 03:49:00.949 align:start position:0% already getting clients or something so 03:49:00.949 --> 03:49:03.500 align:start position:0% already getting clients or something so 30<03:49:01.949> getting<03:49:02.249> to<03:49:02.760> do<03:49:02.879> other<03:49:03.119> things<03:49:03.390> that 03:49:03.500 --> 03:49:03.510 align:start position:0% 30 getting to do other things that 03:49:03.510 --> 03:49:04.639 align:start position:0% 30 getting to do other things that aren't<03:49:03.689> that<03:49:03.810> so<03:49:04.140> it's<03:49:04.260> kind<03:49:04.470> of<03:49:04.499> like 03:49:04.639 --> 03:49:04.649 align:start position:0% aren't that so it's kind of like 03:49:04.649 --> 03:49:07.790 align:start position:0% aren't that so it's kind of like sometimes<03:49:05.100> it's<03:49:05.939> hard<03:49:06.119> to<03:49:06.149> do<03:49:06.329> some<03:49:06.539> doctor<03:49:07.289> or 03:49:07.790 --> 03:49:07.800 align:start position:0% sometimes it's hard to do some doctor or 03:49:07.800 --> 03:49:11.309 align:start position:0% sometimes it's hard to do some doctor or you<03:49:07.919> always<03:49:08.100> be<03:49:08.430> prioritized 03:49:11.309 --> 03:49:11.319 align:start position:0% 03:49:11.319 --> 03:49:40.841 align:start position:0% so 03:49:40.841 --> 03:49:40.851 align:start position:0% 03:49:40.851 --> 03:49:50.080 align:start position:0% the<03:49:41.120> 70s 03:49:50.080 --> 03:49:50.090 align:start position:0% 03:49:50.090 --> 03:49:55.210 align:start position:0% they 03:49:55.210 --> 03:49:55.220 align:start position:0% 03:49:55.220 --> 03:49:59.110 align:start position:0% these<03:49:56.220> generate<03:49:57.210> foxes 03:49:59.110 --> 03:49:59.120 align:start position:0% these generate foxes 03:49:59.120 --> 03:50:05.030 align:start position:0% these generate foxes and<03:50:01.240> assertions<03:50:02.240> about<03:50:02.570> you<03:50:02.900> have<03:50:03.140> programs 03:50:05.030 --> 03:50:05.040 align:start position:0% and assertions about you have programs 03:50:05.040 --> 03:50:13.950 align:start position:0% and assertions about you have programs so<03:50:05.640> he<03:50:06.170> respiration<03:50:07.170> like<03:50:07.380> monthly<03:50:07.710> dues<03:50:07.979> that 03:50:13.950 --> 03:50:13.960 align:start position:0% 03:50:13.960 --> 03:50:18.210 align:start position:0% tourists<03:50:15.120> I<03:50:16.120> think<03:50:16.750> that 03:50:18.210 --> 03:50:18.220 align:start position:0% tourists I think that 03:50:18.220 --> 03:50:21.899 align:start position:0% tourists I think that vehicles<03:50:19.220> that<03:50:20.020> particular<03:50:21.020> solution 03:50:21.899 --> 03:50:21.909 align:start position:0% vehicles that particular solution 03:50:21.909 --> 03:50:26.131 align:start position:0% vehicles that particular solution assaults<03:50:22.909> actual<03:50:23.979> horizontal<03:50:24.979> fish 03:50:26.131 --> 03:50:26.141 align:start position:0% assaults actual horizontal fish 03:50:26.141 --> 03:50:30.720 align:start position:0% assaults actual horizontal fish I<03:50:27.070> think<03:50:27.790> air 03:50:30.720 --> 03:50:30.730 align:start position:0% 03:50:30.730 --> 03:50:34.190 align:start position:0% yes 03:50:34.190 --> 03:50:34.200 align:start position:0% 03:50:34.200 --> 03:50:52.230 align:start position:0% like<03:50:34.860> questionnaire<03:50:43.729> definition<03:50:44.729> ice 03:50:52.230 --> 03:50:52.240 align:start position:0% 03:50:52.240 --> 03:51:04.701 align:start position:0% or<03:50:52.570> this<03:50:52.810> resolution<03:50:53.260> actually<03:50:53.979> sorta<03:50:54.430> start 03:51:04.701 --> 03:51:04.711 align:start position:0% 03:51:04.711 --> 03:51:07.090 align:start position:0% something 03:51:07.090 --> 03:51:07.100 align:start position:0% something 03:51:07.100 --> 03:51:24.600 align:start position:0% something [Music] 03:51:24.600 --> 03:51:24.610 align:start position:0% 03:51:24.610 --> 03:51:27.551 align:start position:0% story<03:51:25.610> what<03:51:26.210> everyone<03:51:27.080> likes<03:51:27.290> to<03:51:27.410> write 03:51:27.551 --> 03:51:27.561 align:start position:0% story what everyone likes to write 03:51:27.561 --> 03:51:30.070 align:start position:0% story what everyone likes to write though<03:51:27.801> right<03:51:28.400> -<03:51:28.450> hackathon<03:51:29.450> so<03:51:29.721> you<03:51:29.840> don't 03:51:30.070 --> 03:51:30.080 align:start position:0% though right - hackathon so you don't 03:51:30.080 --> 03:51:37.450 align:start position:0% though right - hackathon so you don't plug<03:51:32.230> the<03:51:33.230> Ducks<03:51:33.920> oh<03:51:34.240> I<03:51:35.240> have<03:51:35.990> a<03:51:36.221> prospect<03:51:37.221> I 03:51:37.450 --> 03:51:37.460 align:start position:0% plug the Ducks oh I have a prospect I 03:51:37.460 --> 03:51:39.190 align:start position:0% plug the Ducks oh I have a prospect I think<03:51:37.700> after<03:51:38.181> listening<03:51:38.330> to<03:51:38.511> this<03:51:38.721> provision 03:51:39.190 --> 03:51:39.200 align:start position:0% think after listening to this provision 03:51:39.200 --> 03:52:27.040 align:start position:0% think after listening to this provision you<03:51:39.740> might<03:51:39.920> be<03:51:40.070> wonderful<03:51:40.400> it<03:51:41.150> is 03:52:27.040 --> 03:52:27.050 align:start position:0% 03:52:27.050 --> 03:52:47.650 align:start position:0% I<03:52:33.100> mean<03:52:34.100> what's<03:52:34.399> time<03:52:34.640> today 03:52:47.650 --> 03:52:47.660 align:start position:0% 03:52:47.660 --> 03:52:54.069 align:start position:0% [Applause] 03:52:54.069 --> 03:52:54.079 align:start position:0% 03:52:54.079 --> 03:52:56.139 align:start position:0% you