WEBVTT Kind: captions Language: en 00:00:01.070 --> 00:00:10.350 align:start position:0% [Applause] 00:00:10.350 --> 00:00:10.360 align:start position:0% 00:00:10.360 --> 00:00:15.190 align:start position:0% my<00:00:11.360> name<00:00:11.480> is<00:00:11.570> Greg<00:00:12.880> from<00:00:13.880> chain<00:00:14.090> Save<00:00:14.360> Eric 00:00:15.190 --> 00:00:15.200 align:start position:0% my name is Greg from chain Save Eric 00:00:15.200 --> 00:00:17.920 align:start position:0% my name is Greg from chain Save Eric we've<00:00:15.620> got<00:00:15.740> Eric<00:00:15.920> over<00:00:16.190> here<00:00:16.369> and<00:00:16.640> Dean<00:00:17.090> need 00:00:17.920 --> 00:00:17.930 align:start position:0% we've got Eric over here and Dean need 00:00:17.930 --> 00:00:20.740 align:start position:0% we've got Eric over here and Dean need some<00:00:18.110> status<00:00:18.460> with<00:00:19.460> chain<00:00:19.670> safe<00:00:19.849> we're<00:00:20.630> going 00:00:20.740 --> 00:00:20.750 align:start position:0% some status with chain safe we're going 00:00:20.750 --> 00:00:23.920 align:start position:0% some status with chain safe we're going to<00:00:20.810> present<00:00:20.930> to<00:00:21.140> you<00:00:21.170> guys<00:00:21.349> something<00:00:22.040> that<00:00:22.930> we 00:00:23.920 --> 00:00:23.930 align:start position:0% to present to you guys something that we 00:00:23.930 --> 00:00:26.200 align:start position:0% to present to you guys something that we worked<00:00:24.140> on<00:00:24.230> as<00:00:24.380> a<00:00:24.410> hack<00:00:24.710> and<00:00:25.400> realizing<00:00:26.180> that 00:00:26.200 --> 00:00:26.210 align:start position:0% worked on as a hack and realizing that 00:00:26.210 --> 00:00:27.790 align:start position:0% worked on as a hack and realizing that there's<00:00:26.510> a<00:00:26.570> lot<00:00:26.600> of<00:00:26.810> actual<00:00:27.140> like<00:00:27.289> application 00:00:27.790 --> 00:00:27.800 align:start position:0% there's a lot of actual like application 00:00:27.800 --> 00:00:31.140 align:start position:0% there's a lot of actual like application to<00:00:28.220> it<00:00:28.340> and<00:00:29.300> it's<00:00:29.510> a<00:00:29.539> little<00:00:29.750> tree<00:00:29.930> lightning 00:00:31.140 --> 00:00:31.150 align:start position:0% to it and it's a little tree lightning 00:00:31.150 --> 00:00:35.410 align:start position:0% to it and it's a little tree lightning so<00:00:33.280> quick<00:00:34.280> outline<00:00:34.580> we're<00:00:34.940> just<00:00:35.090> gonna<00:00:35.180> kind 00:00:35.410 --> 00:00:35.420 align:start position:0% so quick outline we're just gonna kind 00:00:35.420 --> 00:00:37.210 align:start position:0% so quick outline we're just gonna kind of<00:00:35.480> like<00:00:35.600> over<00:00:36.019> everything<00:00:36.470> and<00:00:36.830> give<00:00:37.100> you 00:00:37.210 --> 00:00:37.220 align:start position:0% of like over everything and give you 00:00:37.220 --> 00:00:39.970 align:start position:0% of like over everything and give you guys<00:00:37.370> a<00:00:37.699> basically<00:00:38.239> the<00:00:38.480> code<00:00:38.900> walkthrough<00:00:39.440> we 00:00:39.970 --> 00:00:39.980 align:start position:0% guys a basically the code walkthrough we 00:00:39.980 --> 00:00:42.820 align:start position:0% guys a basically the code walkthrough we have<00:00:40.129> a<00:00:40.160> full<00:00:40.430> we<00:00:40.610> have<00:00:40.699> a<00:00:40.870> sorry<00:00:41.870> we<00:00:42.470> do<00:00:42.620> have 00:00:42.820 --> 00:00:42.830 align:start position:0% have a full we have a sorry we do have 00:00:42.830 --> 00:00:44.950 align:start position:0% have a full we have a sorry we do have like<00:00:43.010> a<00:00:43.040> running<00:00:43.339> surface<00:00:43.640> TK<00:00:43.970> that<00:00:44.510> works<00:00:44.750> but 00:00:44.950 --> 00:00:44.960 align:start position:0% like a running surface TK that works but 00:00:44.960 --> 00:00:47.380 align:start position:0% like a running surface TK that works but it's<00:00:45.409> it<00:00:46.250> only<00:00:46.430> supports<00:00:46.670> bluetooth 00:00:47.380 --> 00:00:47.390 align:start position:0% it's it only supports bluetooth 00:00:47.390 --> 00:00:48.520 align:start position:0% it's it only supports bluetooth currently<00:00:47.780> in<00:00:47.870> minutes<00:00:48.080> a<00:00:48.110> working<00:00:48.379> progress 00:00:48.520 --> 00:00:48.530 align:start position:0% currently in minutes a working progress 00:00:48.530 --> 00:00:51.729 align:start position:0% currently in minutes a working progress on<00:00:48.799> the<00:00:49.000> Wi-Fi<00:00:50.000> direct<00:00:50.110> if<00:00:51.110> we<00:00:51.290> want<00:00:51.500> me<00:00:51.620> to 00:00:51.729 --> 00:00:51.739 align:start position:0% on the Wi-Fi direct if we want me to 00:00:51.739 --> 00:00:52.660 align:start position:0% on the Wi-Fi direct if we want me to show<00:00:51.860> you<00:00:51.920> guys<00:00:52.040> how<00:00:52.100> to<00:00:52.190> integrate<00:00:52.430> it 00:00:52.660 --> 00:00:52.670 align:start position:0% show you guys how to integrate it 00:00:52.670 --> 00:00:55.590 align:start position:0% show you guys how to integrate it directly<00:00:52.790> into<00:00:53.299> like<00:00:53.570> a<00:00:53.600> sub<00:00:54.199> tab<00:00:54.379> right<00:00:54.589> now 00:00:55.590 --> 00:00:55.600 align:start position:0% directly into like a sub tab right now 00:00:55.600 --> 00:00:57.549 align:start position:0% directly into like a sub tab right now we<00:00:56.600> can<00:00:56.720> be<00:00:56.750> like<00:00:56.930> outdoors 00:00:57.549 --> 00:00:57.559 align:start position:0% we can be like outdoors 00:00:57.559 --> 00:01:03.130 align:start position:0% we can be like outdoors we're<00:00:57.920> gonna<00:00:58.010> turn<00:00:58.250> the<00:00:58.430> TV<00:00:58.640> music<00:00:59.440> so<00:01:02.140> you 00:01:03.130 --> 00:01:03.140 align:start position:0% we're gonna turn the TV music so you 00:01:03.140 --> 00:01:04.390 align:start position:0% we're gonna turn the TV music so you know<00:01:03.260> they<00:01:03.470> have<00:01:03.589> this<00:01:03.739> slide<00:01:04.010> is<00:01:04.129> kind<00:01:04.309> of 00:01:04.390 --> 00:01:04.400 align:start position:0% know they have this slide is kind of 00:01:04.400 --> 00:01:06.760 align:start position:0% know they have this slide is kind of cheeky<00:01:04.580> like<00:01:05.299> this<00:01:05.659> Wi-Fi<00:01:06.049> a<00:01:06.080> good<00:01:06.560> luck 00:01:06.760 --> 00:01:06.770 align:start position:0% cheeky like this Wi-Fi a good luck 00:01:06.770 --> 00:01:11.170 align:start position:0% cheeky like this Wi-Fi a good luck downloading<00:01:07.190> Xcode<00:01:07.580> so<00:01:09.790> over<00:01:10.790> doing<00:01:10.940> the<00:01:11.000> Code 00:01:11.170 --> 00:01:11.180 align:start position:0% downloading Xcode so over doing the Code 00:01:11.180 --> 00:01:12.280 align:start position:0% downloading Xcode so over doing the Code walkthrough<00:01:11.330> not<00:01:11.690> an<00:01:11.750> actual<00:01:11.869> integration 00:01:12.280 --> 00:01:12.290 align:start position:0% walkthrough not an actual integration 00:01:12.290 --> 00:01:15.310 align:start position:0% walkthrough not an actual integration but<00:01:12.830> if<00:01:12.890> you<00:01:12.950> have<00:01:13.070> Xcode<00:01:13.400> we<00:01:13.520> can<00:01:13.640> do<00:01:14.320> that's 00:01:15.310 --> 00:01:15.320 align:start position:0% but if you have Xcode we can do that's 00:01:15.320 --> 00:01:18.429 align:start position:0% but if you have Xcode we can do that's like<00:01:15.469> four<00:01:15.649> games<00:01:16.719> kind<00:01:17.719> of<00:01:17.780> like<00:01:17.899> results<00:01:18.320> are 00:01:18.429 --> 00:01:18.439 align:start position:0% like four games kind of like results are 00:01:18.439 --> 00:01:20.349 align:start position:0% like four games kind of like results are like<00:01:18.560> me<00:01:18.710> where<00:01:19.009> did<00:01:19.070> it<00:01:19.130> happen<00:01:19.219> so<00:01:19.700> we<00:01:20.270> were 00:01:20.349 --> 00:01:20.359 align:start position:0% like me where did it happen so we were 00:01:20.359 --> 00:01:23.349 align:start position:0% like me where did it happen so we were in<00:01:20.420> New<00:01:20.719> York<00:01:20.780> and<00:01:21.520> basically<00:01:22.520> we<00:01:23.060> have<00:01:23.240> this 00:01:23.349 --> 00:01:23.359 align:start position:0% in New York and basically we have this 00:01:23.359 --> 00:01:25.590 align:start position:0% in New York and basically we have this crazy<00:01:23.719> idea<00:01:23.899> that<00:01:24.289> we<00:01:24.590> were<00:01:24.649> gonna<00:01:24.770> transmit 00:01:25.590 --> 00:01:25.600 align:start position:0% crazy idea that we were gonna transmit 00:01:25.600 --> 00:01:28.120 align:start position:0% crazy idea that we were gonna transmit offline<00:01:26.600> theorem<00:01:27.350> transactions<00:01:27.950> over 00:01:28.120 --> 00:01:28.130 align:start position:0% offline theorem transactions over 00:01:28.130 --> 00:01:31.240 align:start position:0% offline theorem transactions over bluetooth<00:01:28.729> and<00:01:29.000> Wi-Fi<00:01:29.179> direct<00:01:29.509> and<00:01:30.289> we<00:01:30.979> did<00:01:31.130> it 00:01:31.240 --> 00:01:31.250 align:start position:0% bluetooth and Wi-Fi direct and we did it 00:01:31.250 --> 00:01:35.529 align:start position:0% bluetooth and Wi-Fi direct and we did it but<00:01:32.149> you<00:01:32.420> know<00:01:32.509> very<00:01:32.810> naively<00:01:33.079> put<00:01:34.270> we<00:01:35.270> started 00:01:35.529 --> 00:01:35.539 align:start position:0% but you know very naively put we started 00:01:35.539 --> 00:01:36.609 align:start position:0% but you know very naively put we started working<00:01:35.689> on<00:01:35.780> from<00:01:35.899> that<00:01:36.049> and<00:01:36.109> then<00:01:36.469> a 00:01:36.609 --> 00:01:36.619 align:start position:0% working on from that and then a 00:01:36.619 --> 00:01:38.610 align:start position:0% working on from that and then a dimension<00:01:37.070> proceeded<00:01:37.490> into 00:01:38.610 --> 00:01:38.620 align:start position:0% dimension proceeded into 00:01:38.620 --> 00:01:41.670 align:start position:0% dimension proceeded into you<00:01:38.860> know<00:01:39.600> dude<00:01:40.600> go 00:01:41.670 --> 00:01:41.680 align:start position:0% you know dude go 00:01:41.680 --> 00:01:43.620 align:start position:0% you know dude go they<00:01:42.100> were<00:01:42.160> like<00:01:42.370> whoa<00:01:42.550> these<00:01:42.850> by<00:01:43.030> pnina 00:01:43.620 --> 00:01:43.630 align:start position:0% they were like whoa these by pnina 00:01:43.630 --> 00:01:45.870 align:start position:0% they were like whoa these by pnina there's<00:01:44.470> no<00:01:44.590> support<00:01:44.920> for<00:01:45.220> Bluetooth<00:01:45.340> and 00:01:45.870 --> 00:01:45.880 align:start position:0% there's no support for Bluetooth and 00:01:45.880 --> 00:01:48.240 align:start position:0% there's no support for Bluetooth and these<00:01:46.120> languages<00:01:46.570> you<00:01:46.870> know<00:01:46.960> on<00:01:47.530> like<00:01:47.770> public 00:01:48.240 --> 00:01:48.250 align:start position:0% these languages you know on like public 00:01:48.250 --> 00:01:50.640 align:start position:0% these languages you know on like public and<00:01:48.490> we're<00:01:48.760> like<00:01:48.880> less<00:01:49.090> problems<00:01:49.540> and<00:01:50.350> then<00:01:50.530> we 00:01:50.640 --> 00:01:50.650 align:start position:0% and we're like less problems and then we 00:01:50.650 --> 00:01:52.830 align:start position:0% and we're like less problems and then we realized<00:01:50.980> there's<00:01:51.250> no<00:01:51.370> support<00:01:51.670> for<00:01:52.090> certain 00:01:52.830 --> 00:01:52.840 align:start position:0% realized there's no support for certain 00:01:52.840 --> 00:01:54.900 align:start position:0% realized there's no support for certain function<00:01:53.200> either<00:01:53.320> bluetooth<00:01:53.860> on<00:01:54.100> you<00:01:54.820> know 00:01:54.900 --> 00:01:54.910 align:start position:0% function either bluetooth on you know 00:01:54.910 --> 00:01:56.790 align:start position:0% function either bluetooth on you know only<00:01:55.150> on<00:01:55.330> iPhones<00:01:55.750> or<00:01:55.960> Android<00:01:56.380> devices<00:01:56.590> so 00:01:56.790 --> 00:01:56.800 align:start position:0% only on iPhones or Android devices so 00:01:56.800 --> 00:01:57.990 align:start position:0% only on iPhones or Android devices so everything<00:01:57.100> we<00:01:57.400> realized<00:01:57.730> really<00:01:57.850> quickly 00:01:57.990 --> 00:01:58.000 align:start position:0% everything we realized really quickly 00:01:58.000 --> 00:01:59.790 align:start position:0% everything we realized really quickly that<00:01:58.510> like<00:01:58.660> the<00:01:58.780> ecosystem<00:01:59.320> itself<00:01:59.440> within 00:01:59.790 --> 00:01:59.800 align:start position:0% that like the ecosystem itself within 00:01:59.800 --> 00:02:02.640 align:start position:0% that like the ecosystem itself within Bluetooth<00:02:00.570> even<00:02:01.570> white<00:02:01.690> button<00:02:01.990> wasn't 00:02:02.640 --> 00:02:02.650 align:start position:0% Bluetooth even white button wasn't 00:02:02.650 --> 00:02:04.830 align:start position:0% Bluetooth even white button wasn't submitted<00:02:02.980> so<00:02:03.700> we<00:02:04.030> ended<00:02:04.180> up<00:02:04.270> moving<00:02:04.480> more 00:02:04.830 --> 00:02:04.840 align:start position:0% submitted so we ended up moving more 00:02:04.840 --> 00:02:15.170 align:start position:0% submitted so we ended up moving more towards<00:02:05.200> a<00:02:05.490> swift<00:02:06.490> and<00:02:06.810> because<00:02:07.810> you<00:02:08.080> know 00:02:15.170 --> 00:02:15.180 align:start position:0% 00:02:15.180 --> 00:02:18.110 align:start position:0% basically<00:02:16.180> what<00:02:16.330> is<00:02:16.420> ultimately<00:02:16.810> we're<00:02:17.290> a 00:02:18.110 --> 00:02:18.120 align:start position:0% basically what is ultimately we're a 00:02:18.120 --> 00:02:21.150 align:start position:0% basically what is ultimately we're a transport<00:02:19.120> agnostic<00:02:19.600> Manning<00:02:19.990> so<00:02:20.560> mobile<00:02:20.980> ad 00:02:21.150 --> 00:02:21.160 align:start position:0% transport agnostic Manning so mobile ad 00:02:21.160 --> 00:02:24.810 align:start position:0% transport agnostic Manning so mobile ad hoc<00:02:21.370> network<00:02:22.890> for<00:02:23.890> sending<00:02:24.310> arbitrary<00:02:24.700> data 00:02:24.810 --> 00:02:24.820 align:start position:0% hoc network for sending arbitrary data 00:02:24.820 --> 00:02:27.290 align:start position:0% hoc network for sending arbitrary data over<00:02:25.240> the<00:02:25.330> wire<00:02:25.560> basically<00:02:26.560> what<00:02:26.950> that<00:02:26.980> means 00:02:27.290 --> 00:02:27.300 align:start position:0% over the wire basically what that means 00:02:27.300 --> 00:02:32.430 align:start position:0% over the wire basically what that means is<00:02:29.490> we<00:02:30.490> don't<00:02:30.760> really<00:02:31.060> care<00:02:31.420> whether<00:02:31.900> you<00:02:32.140> use 00:02:32.430 --> 00:02:32.440 align:start position:0% is we don't really care whether you use 00:02:32.440 --> 00:02:35.070 align:start position:0% is we don't really care whether you use bluetooth<00:02:32.950> whether<00:02:33.340> you<00:02:33.610> use<00:02:33.970> Wi-Fi<00:02:34.690> direct 00:02:35.070 --> 00:02:35.080 align:start position:0% bluetooth whether you use Wi-Fi direct 00:02:35.080 --> 00:02:37.170 align:start position:0% bluetooth whether you use Wi-Fi direct whether<00:02:35.380> you're<00:02:35.620> using<00:02:35.800> like<00:02:36.130> you<00:02:36.520> know<00:02:36.640> hard 00:02:37.170 --> 00:02:37.180 align:start position:0% whether you're using like you know hard 00:02:37.180 --> 00:02:40.470 align:start position:0% whether you're using like you know hard code<00:02:38.130> it<00:02:39.130> really<00:02:39.790> doesn't<00:02:40.030> matter<00:02:40.090> what<00:02:40.330> we're 00:02:40.470 --> 00:02:40.480 align:start position:0% code it really doesn't matter what we're 00:02:40.480 --> 00:02:41.580 align:start position:0% code it really doesn't matter what we're trying<00:02:40.600> to<00:02:40.690> is<00:02:40.810> we're<00:02:40.900> trying<00:02:41.020> to<00:02:41.140> find<00:02:41.320> a<00:02:41.410> way 00:02:41.580 --> 00:02:41.590 align:start position:0% trying to is we're trying to find a way 00:02:41.590 --> 00:02:43.410 align:start position:0% trying to is we're trying to find a way to<00:02:41.620> actually<00:02:42.130> communicate<00:02:42.520> over<00:02:43.150> your 00:02:43.410 --> 00:02:43.420 align:start position:0% to actually communicate over your 00:02:43.420 --> 00:02:45.570 align:start position:0% to actually communicate over your networks<00:02:43.930> that<00:02:44.110> are<00:02:44.310> we<00:02:45.310> don't<00:02:45.370> care<00:02:45.489> about 00:02:45.570 --> 00:02:45.580 align:start position:0% networks that are we don't care about 00:02:45.580 --> 00:02:47.220 align:start position:0% networks that are we don't care about really<00:02:45.940> the<00:02:46.060> topology<00:02:46.330> we<00:02:46.600> like<00:02:46.720> we<00:02:46.870> only<00:02:46.989> care 00:02:47.220 --> 00:02:47.230 align:start position:0% really the topology we like we only care 00:02:47.230 --> 00:02:52.410 align:start position:0% really the topology we like we only care about<00:02:49.320> how<00:02:50.320> you're<00:02:50.709> transmitting<00:02:51.070> data<00:02:51.790> from 00:02:52.410 --> 00:02:52.420 align:start position:0% about how you're transmitting data from 00:02:52.420 --> 00:02:54.750 align:start position:0% about how you're transmitting data from one<00:02:52.600> period<00:02:52.840> to<00:02:52.959> another<00:02:53.050> peer<00:02:53.650> and<00:02:53.980> when<00:02:54.640> you 00:02:54.750 --> 00:02:54.760 align:start position:0% one period to another peer and when you 00:02:54.760 --> 00:02:56.610 align:start position:0% one period to another peer and when you don't<00:02:55.000> have<00:02:55.300> a<00:02:55.360> stable<00:02:55.630> connection<00:02:56.080> that's 00:02:56.610 --> 00:02:56.620 align:start position:0% don't have a stable connection that's 00:02:56.620 --> 00:02:58.680 align:start position:0% don't have a stable connection that's like<00:02:56.830> basically<00:02:57.220> the<00:02:57.310> idea<00:02:57.640> -<00:02:57.790> it's<00:02:58.450> like<00:02:58.570> how 00:02:58.680 --> 00:02:58.690 align:start position:0% like basically the idea - it's like how 00:02:58.690 --> 00:03:00.150 align:start position:0% like basically the idea - it's like how can<00:02:58.840> we<00:02:58.959> actually<00:02:59.080> make<00:02:59.230> that<00:02:59.440> work<00:02:59.500> and<00:03:00.100> how 00:03:00.150 --> 00:03:00.160 align:start position:0% can we actually make that work and how 00:03:00.160 --> 00:03:02.400 align:start position:0% can we actually make that work and how can<00:03:00.250> we<00:03:00.489> do<00:03:00.640> it<00:03:00.670> in<00:03:01.390> the<00:03:01.570> future<00:03:01.780> and<00:03:01.989> to<00:03:02.050> do<00:03:02.200> so 00:03:02.400 --> 00:03:02.410 align:start position:0% can we do it in the future and to do so 00:03:02.410 --> 00:03:04.320 align:start position:0% can we do it in the future and to do so we<00:03:02.530> can<00:03:02.650> actually<00:03:02.890> like<00:03:03.040> do<00:03:03.940> kind<00:03:04.150> of<00:03:04.180> like 00:03:04.320 --> 00:03:04.330 align:start position:0% we can actually like do kind of like 00:03:04.330 --> 00:03:06.960 align:start position:0% we can actually like do kind of like relay<00:03:04.690> with<00:03:04.959> your<00:03:05.140> transactions<00:03:05.709> and<00:03:06.100> or<00:03:06.820> just 00:03:06.960 --> 00:03:06.970 align:start position:0% relay with your transactions and or just 00:03:06.970 --> 00:03:09.420 align:start position:0% relay with your transactions and or just any<00:03:07.120> transaction<00:03:07.720> really<00:03:08.100> in<00:03:09.100> a<00:03:09.250> very 00:03:09.420 --> 00:03:09.430 align:start position:0% any transaction really in a very 00:03:09.430 --> 00:03:10.920 align:start position:0% any transaction really in a very unstable<00:03:09.730> environment<00:03:10.360> we'll<00:03:10.510> get<00:03:10.630> into<00:03:10.750> the 00:03:10.920 --> 00:03:10.930 align:start position:0% unstable environment we'll get into the 00:03:10.930 --> 00:03:16.340 align:start position:0% unstable environment we'll get into the get<00:03:11.350> inside<00:03:11.620> show<00:03:14.040> so<00:03:15.040> quickly<00:03:15.459> about<00:03:15.640> minutes 00:03:16.340 --> 00:03:16.350 align:start position:0% get inside show so quickly about minutes 00:03:16.350 --> 00:03:19.050 align:start position:0% get inside show so quickly about minutes so<00:03:17.350> man<00:03:17.920> refers<00:03:18.220> to<00:03:18.250> continues 00:03:19.050 --> 00:03:19.060 align:start position:0% so man refers to continues 00:03:19.060 --> 00:03:20.640 align:start position:0% so man refers to continues self-configuring 00:03:20.640 --> 00:03:20.650 align:start position:0% self-configuring 00:03:20.650 --> 00:03:22.140 align:start position:0% self-configuring infrastructure<00:03:21.550> list 00:03:22.140 --> 00:03:22.150 align:start position:0% infrastructure list 00:03:22.150 --> 00:03:24.270 align:start position:0% infrastructure list of<00:03:22.480> mobile<00:03:22.870> devices<00:03:23.140> on<00:03:23.440> that<00:03:23.620> date<00:03:23.799> let's<00:03:24.159> see 00:03:24.270 --> 00:03:24.280 align:start position:0% of mobile devices on that date let's see 00:03:24.280 --> 00:03:26.640 align:start position:0% of mobile devices on that date let's see that's<00:03:24.640> a<00:03:24.730> lot<00:03:24.819> of<00:03:24.879> buzzwords<00:03:25.090> I<00:03:25.450> have<00:03:25.959> very 00:03:26.640 --> 00:03:26.650 align:start position:0% that's a lot of buzzwords I have very 00:03:26.650 --> 00:03:29.520 align:start position:0% that's a lot of buzzwords I have very little<00:03:27.360> interactive<00:03:28.360> thing<00:03:29.230> I'm<00:03:29.349> going<00:03:29.470> to 00:03:29.520 --> 00:03:29.530 align:start position:0% little interactive thing I'm going to 00:03:29.530 --> 00:03:30.509 align:start position:0% little interactive thing I'm going to show<00:03:29.590> you<00:03:29.680> guys<00:03:29.860> are<00:03:29.980> not<00:03:30.099> to<00:03:30.220> make<00:03:30.400> the 00:03:30.509 --> 00:03:30.519 align:start position:0% show you guys are not to make the 00:03:30.519 --> 00:03:32.610 align:start position:0% show you guys are not to make the difference<00:03:31.019> so<00:03:32.019> it<00:03:32.080> kind<00:03:32.230> of<00:03:32.260> sounds<00:03:32.470> like<00:03:32.500> a 00:03:32.610 --> 00:03:32.620 align:start position:0% difference so it kind of sounds like a 00:03:32.620 --> 00:03:33.720 align:start position:0% difference so it kind of sounds like a mesh<00:03:32.799> network<00:03:32.830> and<00:03:33.340> I<00:03:33.370> want<00:03:33.549> a<00:03:33.580> different 00:03:33.720 --> 00:03:33.730 align:start position:0% mesh network and I want a different 00:03:33.730 --> 00:03:38.100 align:start position:0% mesh network and I want a different different<00:03:34.709> you<00:03:35.709> know<00:03:35.799> make<00:03:36.159> the<00:03:36.989> explain<00:03:37.989> the 00:03:38.100 --> 00:03:38.110 align:start position:0% different you know make the explain the 00:03:38.110 --> 00:03:40.350 align:start position:0% different you know make the explain the difference<00:03:38.349> quite<00:03:38.920> clearly<00:03:39.159> so<00:03:40.120> a<00:03:40.150> mesh 00:03:40.350 --> 00:03:40.360 align:start position:0% difference quite clearly so a mesh 00:03:40.360 --> 00:03:41.789 align:start position:0% difference quite clearly so a mesh network<00:03:40.390> you<00:03:40.930> can<00:03:41.049> think<00:03:41.230> of<00:03:41.319> like<00:03:41.530> a<00:03:41.560> bunch<00:03:41.709> of 00:03:41.789 --> 00:03:41.799 align:start position:0% network you can think of like a bunch of 00:03:41.799 --> 00:03:43.770 align:start position:0% network you can think of like a bunch of IOT<00:03:41.980> devices<00:03:42.400> that<00:03:42.670> don't<00:03:42.849> move<00:03:42.940> is<00:03:43.599> your 00:03:43.770 --> 00:03:43.780 align:start position:0% IOT devices that don't move is your 00:03:43.780 --> 00:03:47.069 align:start position:0% IOT devices that don't move is your camera<00:03:44.110> movement<00:03:45.090> all<00:03:46.090> right<00:03:46.239> probably<00:03:46.930> not 00:03:47.069 --> 00:03:47.079 align:start position:0% camera movement all right probably not 00:03:47.079 --> 00:03:48.899 align:start position:0% camera movement all right probably not your<00:03:47.590> cameras<00:03:47.950> like<00:03:48.129> staying<00:03:48.400> still<00:03:48.670> and 00:03:48.899 --> 00:03:48.909 align:start position:0% your cameras like staying still and 00:03:48.909 --> 00:03:52.940 align:start position:0% your cameras like staying still and there<00:03:49.450> it's<00:03:49.750> gonna<00:03:49.840> be<00:03:50.019> our<00:03:50.110> camera<00:03:51.480> you<00:03:52.480> know 00:03:52.940 --> 00:03:52.950 align:start position:0% there it's gonna be our camera you know 00:03:52.950 --> 00:03:55.259 align:start position:0% there it's gonna be our camera you know same<00:03:53.950> apply<00:03:54.280> your<00:03:54.579> your<00:03:54.790> toaster<00:03:55.150> your 00:03:55.259 --> 00:03:55.269 align:start position:0% same apply your your toaster your 00:03:55.269 --> 00:03:56.580 align:start position:0% same apply your your toaster your toaster<00:03:55.569> probably<00:03:55.930> doesn't<00:03:56.200> move<00:03:56.290> for<00:03:56.470> that 00:03:56.580 --> 00:03:56.590 align:start position:0% toaster probably doesn't move for that 00:03:56.590 --> 00:03:58.410 align:start position:0% toaster probably doesn't move for that stove<00:03:56.859> that's<00:03:57.129> like<00:03:57.280> all<00:03:57.519> connected<00:03:57.940> that's<00:03:58.299> a 00:03:58.410 --> 00:03:58.420 align:start position:0% stove that's like all connected that's a 00:03:58.420 --> 00:03:59.610 align:start position:0% stove that's like all connected that's a machine<00:03:58.599> or<00:03:58.750> even<00:03:58.959> your<00:03:59.200> brother<00:03:59.379> you<00:03:59.560> know 00:03:59.610 --> 00:03:59.620 align:start position:0% machine or even your brother you know 00:03:59.620 --> 00:04:01.470 align:start position:0% machine or even your brother you know those<00:03:59.859> Google<00:04:00.220> like<00:04:00.430> little<00:04:00.700> rubber<00:04:00.819> modulus 00:04:01.470 --> 00:04:01.480 align:start position:0% those Google like little rubber modulus 00:04:01.480 --> 00:04:03.119 align:start position:0% those Google like little rubber modulus like<00:04:01.660> they're<00:04:02.200> staying<00:04:02.440> in<00:04:02.620> one<00:04:02.769> place<00:04:02.799> and 00:04:03.119 --> 00:04:03.129 align:start position:0% like they're staying in one place and 00:04:03.129 --> 00:04:04.050 align:start position:0% like they're staying in one place and typically<00:04:03.430> not<00:04:03.549> moving<00:04:03.849> and<00:04:03.940> they're 00:04:04.050 --> 00:04:04.060 align:start position:0% typically not moving and they're 00:04:04.060 --> 00:04:05.699 align:start position:0% typically not moving and they're relaying<00:04:04.359> this<00:04:04.629> whatever<00:04:04.959> the<00:04:05.109> data<00:04:05.260> is<00:04:05.470> like 00:04:05.699 --> 00:04:05.709 align:start position:0% relaying this whatever the data is like 00:04:05.709 --> 00:04:08.640 align:start position:0% relaying this whatever the data is like in<00:04:05.859> a<00:04:05.920> very<00:04:06.069> static<00:04:06.970> way<00:04:07.349> do<00:04:08.349> you<00:04:08.409> know<00:04:08.530> what 00:04:08.640 --> 00:04:08.650 align:start position:0% in a very static way do you know what 00:04:08.650 --> 00:04:11.550 align:start position:0% in a very static way do you know what here's<00:04:08.799> me<00:04:08.920> a<00:04:09.010> thumb<00:04:09.250> and<00:04:09.840> I'm<00:04:10.840> gonna<00:04:11.019> be<00:04:11.349> there 00:04:11.550 --> 00:04:11.560 align:start position:0% here's me a thumb and I'm gonna be there 00:04:11.560 --> 00:04:13.740 align:start position:0% here's me a thumb and I'm gonna be there yeah<00:04:11.890> it's<00:04:12.609> nice<00:04:12.760> you<00:04:13.209> know<00:04:13.239> this<00:04:13.599> is 00:04:13.740 --> 00:04:13.750 align:start position:0% yeah it's nice you know this is 00:04:13.750 --> 00:04:15.630 align:start position:0% yeah it's nice you know this is technology<00:04:14.109> that's<00:04:14.769> sending<00:04:15.010> that<00:04:15.310> it's<00:04:15.430> very 00:04:15.630 --> 00:04:15.640 align:start position:0% technology that's sending that it's very 00:04:15.640 --> 00:04:16.229 align:start position:0% technology that's sending that it's very low-power 00:04:16.229 --> 00:04:16.239 align:start position:0% low-power 00:04:16.239 --> 00:04:18.120 align:start position:0% low-power doesn't<00:04:16.900> need<00:04:17.019> a<00:04:17.049> lot<00:04:17.199> of<00:04:17.350> work<00:04:17.470> and<00:04:17.709> can 00:04:18.120 --> 00:04:18.130 align:start position:0% doesn't need a lot of work and can 00:04:18.130 --> 00:04:21.840 align:start position:0% doesn't need a lot of work and can actually<00:04:18.280> like<00:04:18.910> will<00:04:19.690> work<00:04:19.930> on<00:04:20.139> this<00:04:20.289> up<00:04:20.639> so<00:04:21.639> in 00:04:21.840 --> 00:04:21.850 align:start position:0% actually like will work on this up so in 00:04:21.850 --> 00:04:24.779 align:start position:0% actually like will work on this up so in our<00:04:21.940> example<00:04:22.860> we<00:04:23.860> are<00:04:23.889> static<00:04:24.370> we're<00:04:24.699> not 00:04:24.779 --> 00:04:24.789 align:start position:0% our example we are static we're not 00:04:24.789 --> 00:04:27.600 align:start position:0% our example we are static we're not moving<00:04:25.150> we're<00:04:25.479> a<00:04:25.510> match<00:04:25.720> but<00:04:26.169> as<00:04:26.950> steam<00:04:27.250> starts 00:04:27.600 --> 00:04:27.610 align:start position:0% moving we're a match but as steam starts 00:04:27.610 --> 00:04:28.680 align:start position:0% moving we're a match but as steam starts to<00:04:27.789> move<00:04:28.090> around 00:04:28.680 --> 00:04:28.690 align:start position:0% to move around 00:04:28.690 --> 00:04:30.960 align:start position:0% to move around crystal<00:04:29.440> transmitting<00:04:29.979> data<00:04:30.190> to<00:04:30.490> oh<00:04:30.520> and 00:04:30.960 --> 00:04:30.970 align:start position:0% crystal transmitting data to oh and 00:04:30.970 --> 00:04:33.180 align:start position:0% crystal transmitting data to oh and somehow<00:04:31.630> this<00:04:31.900> camera<00:04:32.260> is<00:04:32.380> actually<00:04:32.919> moving 00:04:33.180 --> 00:04:33.190 align:start position:0% somehow this camera is actually moving 00:04:33.190 --> 00:04:35.400 align:start position:0% somehow this camera is actually moving or<00:04:33.610> not<00:04:33.639> moving<00:04:33.970> so<00:04:34.389> as<00:04:34.510> a<00:04:34.539> picture<00:04:34.900> right<00:04:35.169> this 00:04:35.400 --> 00:04:35.410 align:start position:0% or not moving so as a picture right this 00:04:35.410 --> 00:04:38.760 align:start position:0% or not moving so as a picture right this can<00:04:35.830> move<00:04:35.950> to<00:04:36.130> this 00:04:38.760 --> 00:04:38.770 align:start position:0% 00:04:38.770 --> 00:04:41.710 align:start position:0% this<00:04:39.770> is<00:04:40.190> a<00:04:40.340> mesh<00:04:40.700> network<00:04:40.730> and<00:04:41.360> we're<00:04:41.480> chance 00:04:41.710 --> 00:04:41.720 align:start position:0% this is a mesh network and we're chance 00:04:41.720 --> 00:04:44.250 align:start position:0% this is a mesh network and we're chance winning<00:04:41.990> today<00:04:42.110> like<00:04:42.320> Jane<00:04:42.530> hi<00:04:42.800> Jean<00:04:43.070> hi<00:04:43.550> hi 00:04:44.250 --> 00:04:44.260 align:start position:0% winning today like Jane hi Jean hi hi 00:04:44.260 --> 00:04:47.020 align:start position:0% winning today like Jane hi Jean hi hi ping<00:04:45.260> and<00:04:45.650> then<00:04:45.830> wait<00:04:46.130> team<00:04:46.550> is<00:04:46.670> gonna<00:04:46.790> go 00:04:47.020 --> 00:04:47.030 align:start position:0% ping and then wait team is gonna go 00:04:47.030 --> 00:04:48.520 align:start position:0% ping and then wait team is gonna go through<00:04:47.060> this<00:04:47.480> wall<00:04:47.840> where<00:04:48.140> there's<00:04:48.350> no 00:04:48.520 --> 00:04:48.530 align:start position:0% through this wall where there's no 00:04:48.530 --> 00:04:51.340 align:start position:0% through this wall where there's no connectivity<00:04:49.630> where<00:04:50.630> it's<00:04:50.750> still<00:04:50.960> a<00:04:50.990> minute 00:04:51.340 --> 00:04:51.350 align:start position:0% connectivity where it's still a minute 00:04:51.350 --> 00:04:52.960 align:start position:0% connectivity where it's still a minute no<00:04:51.440> I'm<00:04:51.890> saying<00:04:52.130> hi<00:04:52.430> team 00:04:52.960 --> 00:04:52.970 align:start position:0% no I'm saying hi team 00:04:52.970 --> 00:04:55.690 align:start position:0% no I'm saying hi team hi<00:04:53.270> Dean<00:04:53.900> he's<00:04:54.440> the<00:04:54.830> messages<00:04:55.250> are<00:04:55.400> in<00:04:55.430> queue 00:04:55.690 --> 00:04:55.700 align:start position:0% hi Dean he's the messages are in queue 00:04:55.700 --> 00:04:58.240 align:start position:0% hi Dean he's the messages are in queue Erik<00:04:56.090> did<00:04:56.210> you<00:04:56.330> see<00:04:56.480> my<00:04:56.600> hi<00:04:56.810> team<00:04:57.050> you<00:04:58.040> saw<00:04:58.220> I 00:04:58.240 --> 00:04:58.250 align:start position:0% Erik did you see my hi team you saw I 00:04:58.250 --> 00:04:58.570 align:start position:0% Erik did you see my hi team you saw I mean 00:04:58.570 --> 00:04:58.580 align:start position:0% mean 00:04:58.580 --> 00:05:02.650 align:start position:0% mean oh<00:04:58.720> hi<00:04:59.720> team<00:05:00.020> hi<00:05:00.410> hi<00:05:00.890> so<00:05:01.640> right<00:05:01.880> there<00:05:02.150> you<00:05:02.570> know 00:05:02.650 --> 00:05:02.660 align:start position:0% oh hi team hi hi so right there you know 00:05:02.660 --> 00:05:08.140 align:start position:0% oh hi team hi hi so right there you know these<00:05:02.870> messages<00:05:06.610> when<00:05:07.610> he<00:05:07.670> comes<00:05:07.880> back 00:05:08.140 --> 00:05:08.150 align:start position:0% these messages when he comes back 00:05:08.150 --> 00:05:38.860 align:start position:0% these messages when he comes back because<00:05:27.070> yes<00:05:37.060> we<00:05:38.060> have<00:05:38.210> some<00:05:38.390> like<00:05:38.570> kind<00:05:38.810> of 00:05:38.860 --> 00:05:38.870 align:start position:0% because yes we have some like kind of 00:05:38.870 --> 00:05:43.090 align:start position:0% because yes we have some like kind of we've<00:05:39.260> got<00:05:39.410> some<00:05:39.590> issues<00:05:40.460> I<00:05:40.760> get<00:05:41.150> up<00:05:41.270> two<00:05:42.170> ways 00:05:43.090 --> 00:05:43.100 align:start position:0% we've got some issues I get up two ways 00:05:43.100 --> 00:05:46.930 align:start position:0% we've got some issues I get up two ways that<00:05:43.400> we<00:05:43.460> can<00:05:43.870> filter<00:05:44.870> no<00:05:45.170> traffic<00:05:45.430> to<00:05:46.430> hop 00:05:46.930 --> 00:05:46.940 align:start position:0% that we can filter no traffic to hop 00:05:46.940 --> 00:05:49.690 align:start position:0% that we can filter no traffic to hop path<00:05:47.270> of<00:05:47.420> least<00:05:47.510> amount<00:05:47.720> of<00:05:47.810> hops<00:05:48.020> and<00:05:48.770> then<00:05:49.490> we 00:05:49.690 --> 00:05:49.700 align:start position:0% path of least amount of hops and then we 00:05:49.700 --> 00:05:51.400 align:start position:0% path of least amount of hops and then we do<00:05:49.880> that<00:05:50.000> using<00:05:50.210> like<00:05:50.510> more<00:05:50.750> centralized<00:05:51.200> will 00:05:51.400 --> 00:05:51.410 align:start position:0% do that using like more centralized will 00:05:51.410 --> 00:05:53.500 align:start position:0% do that using like more centralized will be<00:05:51.500> layers<00:05:51.710> so<00:05:52.070> some<00:05:52.340> needed<00:05:52.640> connect<00:05:53.090> talk 00:05:53.500 --> 00:05:53.510 align:start position:0% be layers so some needed connect talk 00:05:53.510 --> 00:05:57.400 align:start position:0% be layers so some needed connect talk about<00:05:53.690> that<00:05:53.810> we'll<00:05:54.140> get<00:05:54.230> to<00:05:54.380> the<00:05:56.410> any 00:05:57.400 --> 00:05:57.410 align:start position:0% about that we'll get to the any 00:05:57.410 --> 00:05:59.500 align:start position:0% about that we'll get to the any mandatory<00:05:57.740> special<00:05:58.280> questions<00:05:58.880> just<00:05:59.360> wanna 00:05:59.500 --> 00:05:59.510 align:start position:0% mandatory special questions just wanna 00:05:59.510 --> 00:06:19.780 align:start position:0% mandatory special questions just wanna make<00:05:59.630> sure<00:05:59.750> we<00:05:59.870> have<00:06:00.020> the<00:06:18.160> yeah<00:06:19.160> why<00:06:19.610> is<00:06:19.670> this 00:06:19.780 --> 00:06:19.790 align:start position:0% make sure we have the yeah why is this 00:06:19.790 --> 00:06:21.610 align:start position:0% make sure we have the yeah why is this super<00:06:20.060> useful<00:06:20.180> let's<00:06:21.080> think<00:06:21.200> about<00:06:21.320> this<00:06:21.500> for 00:06:21.610 --> 00:06:21.620 align:start position:0% super useful let's think about this for 00:06:21.620 --> 00:06:22.180 align:start position:0% super useful let's think about this for a<00:06:21.710> second 00:06:22.180 --> 00:06:22.190 align:start position:0% a second 00:06:22.190 --> 00:06:25.150 align:start position:0% a second so<00:06:23.090> this<00:06:23.510> is<00:06:23.600> kind<00:06:23.810> of<00:06:23.840> this<00:06:23.930> photo<00:06:24.260> drink<00:06:24.770> it's 00:06:25.150 --> 00:06:25.160 align:start position:0% so this is kind of this photo drink it's 00:06:25.160 --> 00:06:27.420 align:start position:0% so this is kind of this photo drink it's kind<00:06:25.550> of<00:06:25.580> when<00:06:25.700> you're<00:06:25.790> in<00:06:25.850> yeah<00:06:26.600> we're<00:06:27.110> like 00:06:27.420 --> 00:06:27.430 align:start position:0% kind of when you're in yeah we're like 00:06:27.430 --> 00:06:30.400 align:start position:0% kind of when you're in yeah we're like totally<00:06:28.430> cut<00:06:29.060> off<00:06:29.090> we're<00:06:29.510> talking<00:06:29.870> like<00:06:30.020> zero 00:06:30.400 --> 00:06:30.410 align:start position:0% totally cut off we're talking like zero 00:06:30.410 --> 00:06:32.080 align:start position:0% totally cut off we're talking like zero internet<00:06:30.830> how<00:06:31.310> do<00:06:31.370> you<00:06:31.460> communicate<00:06:31.640> with<00:06:31.970> my 00:06:32.080 --> 00:06:32.090 align:start position:0% internet how do you communicate with my 00:06:32.090 --> 00:06:40.270 align:start position:0% internet how do you communicate with my number<00:06:32.450> you<00:06:33.400> can<00:06:34.400> do<00:06:34.520> it 00:06:40.270 --> 00:06:40.280 align:start position:0% 00:06:40.280 --> 00:06:42.580 align:start position:0% these<00:06:40.430> are<00:06:40.550> like<00:06:40.670> non<00:06:40.820> sensible<00:06:41.510> tools<00:06:42.350> that 00:06:42.580 --> 00:06:42.590 align:start position:0% these are like non sensible tools that 00:06:42.590 --> 00:06:44.410 align:start position:0% these are like non sensible tools that our<00:06:42.650> disposal<00:06:43.100> you<00:06:43.490> know<00:06:43.610> going<00:06:43.820> over<00:06:44.030> data 00:06:44.410 --> 00:06:44.420 align:start position:0% our disposal you know going over data 00:06:44.420 --> 00:06:46.480 align:start position:0% our disposal you know going over data and<00:06:44.840> connecting<00:06:45.500> to<00:06:45.530> the<00:06:45.710> carrier<00:06:46.100> that<00:06:46.220> sense 00:06:46.480 --> 00:06:46.490 align:start position:0% and connecting to the carrier that sense 00:06:46.490 --> 00:06:49.360 align:start position:0% and connecting to the carrier that sense right<00:06:46.910> because<00:06:47.060> they<00:06:47.150> can<00:06:47.330> completion<00:06:48.280> in<00:06:49.280> a 00:06:49.360 --> 00:06:49.370 align:start position:0% right because they can completion in a 00:06:49.370 --> 00:06:51.400 align:start position:0% right because they can completion in a large<00:06:49.580> crowd<00:06:49.880> all<00:06:50.660> you<00:06:50.810> need<00:06:51.050> are<00:06:51.320> a<00:06:51.380> few 00:06:51.400 --> 00:06:51.410 align:start position:0% large crowd all you need are a few 00:06:51.410 --> 00:06:54.310 align:start position:0% large crowd all you need are a few people<00:06:51.979> with<00:06:52.479> devices<00:06:53.479> going<00:06:53.660> and<00:06:53.960> you<00:06:54.140> have<00:06:54.290> a 00:06:54.310 --> 00:06:54.320 align:start position:0% people with devices going and you have a 00:06:54.320 --> 00:06:55.240 align:start position:0% people with devices going and you have a full-blown 00:06:55.240 --> 00:06:55.250 align:start position:0% full-blown 00:06:55.250 --> 00:06:58.330 align:start position:0% full-blown network<00:06:56.320> and<00:06:57.320> where<00:06:57.830> you<00:06:58.010> can<00:06:58.160> communicate 00:06:58.330 --> 00:06:58.340 align:start position:0% network and where you can communicate 00:06:58.340 --> 00:07:00.040 align:start position:0% network and where you can communicate with<00:06:58.610> somebody<00:06:58.910> potential<00:06:59.870> on<00:06:59.930> the<00:06:59.990> other 00:07:00.040 --> 00:07:00.050 align:start position:0% with somebody potential on the other 00:07:00.050 --> 00:07:01.690 align:start position:0% with somebody potential on the other side<00:07:00.290> of<00:07:00.410> the<00:07:00.470> world<00:07:00.560> as<00:07:00.650> long<00:07:00.680> one<00:07:01.190> person<00:07:01.580> is 00:07:01.690 --> 00:07:01.700 align:start position:0% side of the world as long one person is 00:07:01.700 --> 00:07:04.450 align:start position:0% side of the world as long one person is internet<00:07:02.030> then<00:07:02.960> we<00:07:03.410> can<00:07:03.590> be<00:07:03.740> funneling<00:07:04.130> all 00:07:04.450 --> 00:07:04.460 align:start position:0% internet then we can be funneling all 00:07:04.460 --> 00:07:06.670 align:start position:0% internet then we can be funneling all our<00:07:04.880> requests<00:07:05.630> through<00:07:05.780> that<00:07:05.990> one<00:07:06.169> person<00:07:06.560> to 00:07:06.670 --> 00:07:06.680 align:start position:0% our requests through that one person to 00:07:06.680 --> 00:07:09.219 align:start position:0% our requests through that one person to a<00:07:06.710> bounce<00:07:07.070> back<00:07:07.340> outwards<00:07:07.729> and<00:07:08.690> you<00:07:08.840> you<00:07:09.110> know 00:07:09.219 --> 00:07:09.229 align:start position:0% a bounce back outwards and you you know 00:07:09.229 --> 00:07:11.980 align:start position:0% a bounce back outwards and you you know you<00:07:09.290> can<00:07:09.500> be<00:07:09.590> like<00:07:09.770> two<00:07:10.729> kilometres<00:07:11.150> away<00:07:11.240> as 00:07:11.980 --> 00:07:11.990 align:start position:0% you can be like two kilometres away as 00:07:11.990 --> 00:07:13.480 align:start position:0% you can be like two kilometres away as long<00:07:12.169> as<00:07:12.380> there's<00:07:12.680> people<00:07:12.979> moving<00:07:13.340> and 00:07:13.480 --> 00:07:13.490 align:start position:0% long as there's people moving and 00:07:13.490 --> 00:07:15.490 align:start position:0% long as there's people moving and carrying<00:07:13.790> these<00:07:13.880> messages<00:07:14.300> around<00:07:14.570> kind<00:07:15.470> of 00:07:15.490 --> 00:07:15.500 align:start position:0% carrying these messages around kind of 00:07:15.500 --> 00:07:17.320 align:start position:0% carrying these messages around kind of like<00:07:15.590> carrier<00:07:15.950> pigeons<00:07:16.280> you<00:07:16.490> know<00:07:16.580> like<00:07:16.850> hey 00:07:17.320 --> 00:07:17.330 align:start position:0% like carrier pigeons you know like hey 00:07:17.330 --> 00:07:18.520 align:start position:0% like carrier pigeons you know like hey this<00:07:17.510> like<00:07:17.690> flying<00:07:17.990> flying<00:07:18.380> flying 00:07:18.520 --> 00:07:18.530 align:start position:0% this like flying flying flying 00:07:18.530 --> 00:07:20.140 align:start position:0% this like flying flying flying eventually<00:07:19.160> get<00:07:19.340> to<00:07:19.460> their<00:07:19.580> location<00:07:19.729> where 00:07:20.140 --> 00:07:20.150 align:start position:0% eventually get to their location where 00:07:20.150 --> 00:07:21.550 align:start position:0% eventually get to their location where they<00:07:20.240> get<00:07:20.390> deep<00:07:20.570> it's<00:07:21.020> kind<00:07:21.169> of<00:07:21.200> a<00:07:21.260> similar 00:07:21.550 --> 00:07:21.560 align:start position:0% they get deep it's kind of a similar 00:07:21.560 --> 00:07:25.730 align:start position:0% they get deep it's kind of a similar idea 00:07:25.730 --> 00:07:25.740 align:start position:0% 00:07:25.740 --> 00:07:29.489 align:start position:0% oh<00:07:26.999> yeah<00:07:27.999> in<00:07:28.240> buildings<00:07:28.659> another<00:07:29.110> really<00:07:29.379> good 00:07:29.489 --> 00:07:29.499 align:start position:0% oh yeah in buildings another really good 00:07:29.499 --> 00:07:32.010 align:start position:0% oh yeah in buildings another really good you<00:07:29.620> say<00:07:29.800> Smith's<00:07:30.069> oh<00:07:30.189> no<00:07:30.339> no<00:07:30.639> no<00:07:31.300> like<00:07:31.539> you 00:07:32.010 --> 00:07:32.020 align:start position:0% you say Smith's oh no no no like you 00:07:32.020 --> 00:07:33.749 align:start position:0% you say Smith's oh no no no like you ever<00:07:32.199> been<00:07:32.349> in<00:07:32.469> a<00:07:32.529> building<00:07:32.860> it's<00:07:33.339> there's<00:07:33.699> so 00:07:33.749 --> 00:07:33.759 align:start position:0% ever been in a building it's there's so 00:07:33.759 --> 00:07:35.489 align:start position:0% ever been in a building it's there's so much<00:07:33.969> concrete<00:07:34.240> you<00:07:34.659> just<00:07:34.870> can't<00:07:35.080> actually 00:07:35.489 --> 00:07:35.499 align:start position:0% much concrete you just can't actually 00:07:35.499 --> 00:07:37.019 align:start position:0% much concrete you just can't actually communicate<00:07:35.949> with<00:07:35.979> anybody<00:07:36.460> like<00:07:36.789> your 00:07:37.019 --> 00:07:37.029 align:start position:0% communicate with anybody like your 00:07:37.029 --> 00:07:40.110 align:start position:0% communicate with anybody like your phone's<00:07:37.240> down<00:07:37.569> like<00:07:38.469> same<00:07:39.219> concept<00:07:39.669> you<00:07:39.849> could 00:07:40.110 --> 00:07:40.120 align:start position:0% phone's down like same concept you could 00:07:40.120 --> 00:07:41.730 align:start position:0% phone's down like same concept you could just<00:07:40.300> keep<00:07:40.449> relaying<00:07:40.960> it<00:07:41.139> until<00:07:41.439> there's<00:07:41.589> one 00:07:41.730 --> 00:07:41.740 align:start position:0% just keep relaying it until there's one 00:07:41.740 --> 00:07:43.439 align:start position:0% just keep relaying it until there's one person<00:07:41.919> with<00:07:42.159> the<00:07:42.219> internet<00:07:42.520> and<00:07:43.059> you<00:07:43.150> can<00:07:43.330> get 00:07:43.439 --> 00:07:43.449 align:start position:0% person with the internet and you can get 00:07:43.449 --> 00:07:44.730 align:start position:0% person with the internet and you can get out<00:07:43.569> and<00:07:43.809> one<00:07:44.050> of<00:07:44.139> the<00:07:44.199> things<00:07:44.349> I<00:07:44.439> wanted<00:07:44.620> like 00:07:44.730 --> 00:07:44.740 align:start position:0% out and one of the things I wanted like 00:07:44.740 --> 00:07:46.980 align:start position:0% out and one of the things I wanted like clear<00:07:45.430> the<00:07:45.550> differentiate<00:07:45.999> hears<00:07:46.210> like<00:07:46.360> yes 00:07:46.980 --> 00:07:46.990 align:start position:0% clear the differentiate hears like yes 00:07:46.990 --> 00:07:49.049 align:start position:0% clear the differentiate hears like yes this<00:07:47.139> is<00:07:47.289> to<00:07:47.409> like<00:07:47.559> do<00:07:47.710> an<00:07:47.800> offline<00:07:48.249> set<00:07:48.490> up<00:07:48.610> but 00:07:49.049 --> 00:07:49.059 align:start position:0% this is to like do an offline set up but 00:07:49.059 --> 00:07:50.700 align:start position:0% this is to like do an offline set up but it's<00:07:49.180> also<00:07:49.330> a<00:07:49.449> way<00:07:49.599> to<00:07:49.629> actually<00:07:49.870> get<00:07:50.319> offline 00:07:50.700 --> 00:07:50.710 align:start position:0% it's also a way to actually get offline 00:07:50.710 --> 00:07:52.200 align:start position:0% it's also a way to actually get offline devices<00:07:51.219> to<00:07:51.460> actually<00:07:51.729> connect<00:07:52.029> to<00:07:52.059> the 00:07:52.200 --> 00:07:52.210 align:start position:0% devices to actually connect to the 00:07:52.210 --> 00:07:54.510 align:start position:0% devices to actually connect to the internet<00:07:52.360> and<00:07:53.229> send<00:07:53.800> them<00:07:53.889> receive<00:07:54.159> messages 00:07:54.510 --> 00:07:54.520 align:start position:0% internet and send them receive messages 00:07:54.520 --> 00:07:55.709 align:start position:0% internet and send them receive messages so<00:07:54.699> that's<00:07:54.849> where<00:07:55.029> the<00:07:55.120> like<00:07:55.300> power<00:07:55.539> behind 00:07:55.709 --> 00:07:55.719 align:start position:0% so that's where the like power behind 00:07:55.719 --> 00:07:58.469 align:start position:0% so that's where the like power behind this<00:07:55.930> slick<00:07:56.199> really<00:07:57.180> becomes<00:07:58.180> like<00:07:58.360> a 00:07:58.469 --> 00:07:58.479 align:start position:0% this slick really becomes like a 00:07:58.479 --> 00:08:00.239 align:start position:0% this slick really becomes like a powering<00:07:58.899> for<00:07:59.050> people<00:07:59.319> is<00:07:59.469> because<00:07:59.649> you<00:08:00.069> can 00:08:00.239 --> 00:08:00.249 align:start position:0% powering for people is because you can 00:08:00.249 --> 00:08:02.879 align:start position:0% powering for people is because you can now<00:08:00.430> like<00:08:00.789> we<00:08:00.969> can<00:08:01.120> give<00:08:01.419> Internet<00:08:01.930> access 00:08:02.879 --> 00:08:02.889 align:start position:0% now like we can give Internet access 00:08:02.889 --> 00:08:05.909 align:start position:0% now like we can give Internet access well<00:08:03.460> messaging<00:08:04.120> access<00:08:04.569> to<00:08:04.809> the<00:08:04.899> Internet<00:08:05.169> to 00:08:05.909 --> 00:08:05.919 align:start position:0% well messaging access to the Internet to 00:08:05.919 --> 00:08:08.399 align:start position:0% well messaging access to the Internet to devices<00:08:06.759> that<00:08:06.999> could<00:08:07.300> be<00:08:07.479> a<00:08:07.509> 50-story<00:08:08.139> deep 00:08:08.399 --> 00:08:08.409 align:start position:0% devices that could be a 50-story deep 00:08:08.409 --> 00:08:10.739 align:start position:0% devices that could be a 50-story deep with<00:08:08.680> no<00:08:09.099> actual<00:08:09.309> active<00:08:09.819> engine<00:08:10.059> as<00:08:10.419> long<00:08:10.629> as 00:08:10.739 --> 00:08:10.749 align:start position:0% with no actual active engine as long as 00:08:10.749 --> 00:08:14.429 align:start position:0% with no actual active engine as long as there's<00:08:10.899> somebody<00:08:11.169> who<00:08:13.169> similarly<00:08:14.169> you<00:08:14.349> know 00:08:14.429 --> 00:08:14.439 align:start position:0% there's somebody who similarly you know 00:08:14.439 --> 00:08:17.549 align:start position:0% there's somebody who similarly you know like<00:08:14.680> in<00:08:14.889> places<00:08:15.249> that<00:08:15.279> don't<00:08:15.460> have<00:08:15.990> access<00:08:16.990> to 00:08:17.549 --> 00:08:17.559 align:start position:0% like in places that don't have access to 00:08:17.559 --> 00:08:20.429 align:start position:0% like in places that don't have access to like<00:08:18.099> get<00:08:18.520> infrastructure<00:08:19.240> whatsoever<00:08:19.449> you 00:08:20.429 --> 00:08:20.439 align:start position:0% like get infrastructure whatsoever you 00:08:20.439 --> 00:08:22.860 align:start position:0% like get infrastructure whatsoever you know<00:08:20.559> we<00:08:20.770> can<00:08:21.039> this<00:08:21.639> could<00:08:21.909> set<00:08:22.149> up<00:08:22.240> like<00:08:22.419> like 00:08:22.860 --> 00:08:22.870 align:start position:0% know we can this could set up like like 00:08:22.870 --> 00:08:26.760 align:start position:0% know we can this could set up like like in<00:08:23.080> like<00:08:24.009> small<00:08:24.339> communities<00:08:24.999> of<00:08:25.240> like<00:08:25.770> to 00:08:26.760 --> 00:08:26.770 align:start position:0% in like small communities of like to 00:08:26.770 --> 00:08:32.730 align:start position:0% in like small communities of like to talk<00:08:26.949> to<00:08:27.099> people<00:08:27.249> so<00:08:30.360> that's<00:08:31.360> kind<00:08:32.289> of<00:08:32.319> like<00:08:32.500> my 00:08:32.730 --> 00:08:32.740 align:start position:0% talk to people so that's kind of like my 00:08:32.740 --> 00:08:36.809 align:start position:0% talk to people so that's kind of like my intro<00:08:33.159> to<00:08:33.300> kind<00:08:34.300> of<00:08:34.389> mesh<00:08:34.769> and<00:08:35.769> the<00:08:36.519> useful 00:08:36.809 --> 00:08:36.819 align:start position:0% intro to kind of mesh and the useful 00:08:36.819 --> 00:08:39.659 align:start position:0% intro to kind of mesh and the useful applications<00:08:37.329> to<00:08:38.039> them<00:08:39.039> we<00:08:39.430> have<00:08:39.519> any 00:08:39.659 --> 00:08:39.669 align:start position:0% applications to them we have any 00:08:39.669 --> 00:08:41.329 align:start position:0% applications to them we have any questions<00:08:40.060> on<00:08:40.180> that 00:08:41.329 --> 00:08:41.339 align:start position:0% questions on that 00:08:41.339 --> 00:08:43.350 align:start position:0% questions on that because<00:08:42.339> then<00:08:42.550> we're<00:08:42.669> gonna<00:08:42.760> talk<00:08:43.000> about<00:08:43.029> like 00:08:43.350 --> 00:08:43.360 align:start position:0% because then we're gonna talk about like 00:08:43.360 --> 00:08:45.830 align:start position:0% because then we're gonna talk about like the<00:08:43.389> like<00:08:44.110> cash<00:08:44.350> flow<00:08:44.589> like<00:08:44.740> stack<00:08:45.010> here 00:08:45.830 --> 00:08:45.840 align:start position:0% the like cash flow like stack here 00:08:45.840 --> 00:08:47.900 align:start position:0% the like cash flow like stack here the<00:08:46.380> merciless<00:08:46.800> is<00:08:47.040> like<00:08:47.190> the<00:08:47.310> best<00:08:47.490> time<00:08:47.730> to 00:08:47.900 --> 00:08:47.910 align:start position:0% the merciless is like the best time to 00:08:47.910 --> 00:09:01.610 align:start position:0% the merciless is like the best time to ask<00:08:48.090> about<00:08:48.300> Li<00:08:52.220> yes<00:08:53.220> so<00:08:59.720> you<00:09:00.720> could<00:09:01.050> yeah<00:09:01.320> you 00:09:01.610 --> 00:09:01.620 align:start position:0% ask about Li yes so you could yeah you 00:09:01.620 --> 00:09:05.269 align:start position:0% ask about Li yes so you could yeah you probably<00:09:02.130> could<00:09:02.370> run<00:09:02.610> it<00:09:03.230> again<00:09:04.230> this<00:09:05.010> just 00:09:05.269 --> 00:09:05.279 align:start position:0% probably could run it again this just 00:09:05.279 --> 00:09:08.110 align:start position:0% probably could run it again this just managed<00:09:06.210> some<00:09:06.450> like<00:09:06.810> we're<00:09:07.350> using<00:09:07.500> a<00:09:07.710> mana 00:09:08.110 --> 00:09:08.120 align:start position:0% managed some like we're using a mana 00:09:08.120 --> 00:09:12.350 align:start position:0% managed some like we're using a mana simply<00:09:09.120> to<00:09:09.360> help<00:09:10.670> yeah<00:09:11.670> yeah<00:09:12.120> he's<00:09:12.240> probably 00:09:12.350 --> 00:09:12.360 align:start position:0% simply to help yeah yeah he's probably 00:09:12.360 --> 00:09:20.120 align:start position:0% simply to help yeah yeah he's probably key<00:09:12.630> to<00:09:12.779> run<00:09:12.960> Cisco<00:09:13.560> but<00:09:13.740> yeah<00:09:19.010> Eric's<00:09:20.010> gonna 00:09:20.120 --> 00:09:20.130 align:start position:0% key to run Cisco but yeah Eric's gonna 00:09:20.130 --> 00:09:22.280 align:start position:0% key to run Cisco but yeah Eric's gonna die<00:09:20.820> if<00:09:20.880> you<00:09:21.210> guys<00:09:21.390> deep<00:09:21.690> into<00:09:21.960> kind<00:09:22.200> of<00:09:22.230> like 00:09:22.280 --> 00:09:22.290 align:start position:0% die if you guys deep into kind of like 00:09:22.290 --> 00:09:25.960 align:start position:0% die if you guys deep into kind of like what<00:09:22.710> all<00:09:22.830> this<00:09:22.980> means<00:09:23.480> and<00:09:24.480> what<00:09:24.510> we've<00:09:24.750> done 00:09:25.960 --> 00:09:25.970 align:start position:0% what all this means and what we've done 00:09:25.970 --> 00:09:32.840 align:start position:0% what all this means and what we've done thank<00:09:26.970> you<00:09:27.089> Greg<00:09:30.650> yeah<00:09:31.650> so<00:09:32.040> this<00:09:32.310> is<00:09:32.520> kind<00:09:32.820> of 00:09:32.840 --> 00:09:32.850 align:start position:0% thank you Greg yeah so this is kind of 00:09:32.850 --> 00:09:35.420 align:start position:0% thank you Greg yeah so this is kind of our<00:09:32.970> architectural<00:09:33.690> diagram<00:09:34.170> for<00:09:34.529> ultralight 00:09:35.420 --> 00:09:35.430 align:start position:0% our architectural diagram for ultralight 00:09:35.430 --> 00:09:38.960 align:start position:0% our architectural diagram for ultralight beam<00:09:35.779> we<00:09:36.779> have<00:09:36.810> I'll<00:09:37.380> go<00:09:37.890> into<00:09:38.310> each<00:09:38.640> part 00:09:38.960 --> 00:09:38.970 align:start position:0% beam we have I'll go into each part 00:09:38.970 --> 00:09:42.170 align:start position:0% beam we have I'll go into each part separately<00:09:39.300> but<00:09:39.779> kinda<00:09:40.680> the<00:09:40.800> flow<00:09:41.070> is<00:09:41.339> like<00:09:41.670> if 00:09:42.170 --> 00:09:42.180 align:start position:0% separately but kinda the flow is like if 00:09:42.180 --> 00:09:43.630 align:start position:0% separately but kinda the flow is like if you're<00:09:42.450> sending<00:09:42.690> and<00:09:42.960> receiving<00:09:42.990> information 00:09:43.630 --> 00:09:43.640 align:start position:0% you're sending and receiving information 00:09:43.640 --> 00:09:46.730 align:start position:0% you're sending and receiving information like<00:09:44.640> data<00:09:44.910> comes<00:09:45.180> into<00:09:45.420> the<00:09:45.660> transport<00:09:46.260> it 00:09:46.730 --> 00:09:46.740 align:start position:0% like data comes into the transport it 00:09:46.740 --> 00:09:49.370 align:start position:0% like data comes into the transport it goes<00:09:46.950> to<00:09:47.070> the<00:09:47.130> node<00:09:47.370> and<00:09:47.990> if<00:09:48.990> the<00:09:49.200> node 00:09:49.370 --> 00:09:49.380 align:start position:0% goes to the node and if the node 00:09:49.380 --> 00:09:51.410 align:start position:0% goes to the node and if the node supports<00:09:49.830> like<00:09:50.010> certain<00:09:50.310> services<00:09:50.820> of<00:09:51.030> Emma 00:09:51.410 --> 00:09:51.420 align:start position:0% supports like certain services of Emma 00:09:51.420 --> 00:09:53.540 align:start position:0% supports like certain services of Emma button<00:09:51.810> this<00:09:51.900> and<00:09:52.650> if<00:09:52.770> a<00:09:52.830> node<00:09:52.980> supports<00:09:53.400> like 00:09:53.540 --> 00:09:53.550 align:start position:0% button this and if a node supports like 00:09:53.550 --> 00:09:55.490 align:start position:0% button this and if a node supports like certain<00:09:53.880> services<00:09:54.330> that<00:09:54.390> you<00:09:54.690> know<00:09:54.780> it<00:09:54.930> you 00:09:55.490 --> 00:09:55.500 align:start position:0% certain services that you know it you 00:09:55.500 --> 00:09:56.810 align:start position:0% certain services that you know it you know<00:09:55.530> and<00:09:55.890> it<00:09:56.280> will<00:09:56.370> process<00:09:56.610> that 00:09:56.810 --> 00:09:56.820 align:start position:0% know and it will process that 00:09:56.820 --> 00:09:58.370 align:start position:0% know and it will process that information<00:09:57.060> if<00:09:57.630> it<00:09:57.750> doesn't<00:09:58.080> it<00:09:58.230> like 00:09:58.370 --> 00:09:58.380 align:start position:0% information if it doesn't it like 00:09:58.380 --> 00:10:00.079 align:start position:0% information if it doesn't it like propagates<00:09:58.890> back<00:09:59.130> out<00:09:59.339> to<00:09:59.520> somebody<00:09:59.730> else<00:10:00.000> who 00:10:00.079 --> 00:10:00.089 align:start position:0% propagates back out to somebody else who 00:10:00.089 --> 00:10:05.590 align:start position:0% propagates back out to somebody else who can<00:10:00.120> potentially<00:10:01.400> then<00:10:02.400> you<00:10:02.730> know<00:10:02.850> in<00:10:03.390> Reverse 00:10:05.590 --> 00:10:05.600 align:start position:0% 00:10:05.600 --> 00:10:10.850 align:start position:0% so<00:10:06.600> transports<00:10:07.670> its<00:10:08.670> we<00:10:09.270> I'm<00:10:10.200> not<00:10:10.500> sure<00:10:10.740> if 00:10:10.850 --> 00:10:10.860 align:start position:0% so transports its we I'm not sure if 00:10:10.860 --> 00:10:12.320 align:start position:0% so transports its we I'm not sure if we're<00:10:10.980> gonna<00:10:11.100> stick<00:10:11.370> with<00:10:11.400> this<00:10:11.670> name<00:10:11.910> but<00:10:12.210> it 00:10:12.320 --> 00:10:12.330 align:start position:0% we're gonna stick with this name but it 00:10:12.330 --> 00:10:15.680 align:start position:0% we're gonna stick with this name but it transports<00:10:12.960> in<00:10:13.800> ultralight<00:10:14.520> beam<00:10:14.700> are<00:10:15.060> it's 00:10:15.680 --> 00:10:15.690 align:start position:0% transports in ultralight beam are it's 00:10:15.690 --> 00:10:19.040 align:start position:0% transports in ultralight beam are it's the<00:10:15.810> communication<00:10:17.060> protocol<00:10:18.060> I<00:10:18.120> guess<00:10:18.450> so 00:10:19.040 --> 00:10:19.050 align:start position:0% the communication protocol I guess so 00:10:19.050 --> 00:10:20.270 align:start position:0% the communication protocol I guess so that<00:10:19.110> includes<00:10:19.500> things<00:10:19.620> like<00:10:19.770> Bluetooth 00:10:20.270 --> 00:10:20.280 align:start position:0% that includes things like Bluetooth 00:10:20.280 --> 00:10:23.150 align:start position:0% that includes things like Bluetooth Wi-Fi<00:10:20.550> direct<00:10:21.000> and<00:10:21.180> radio<00:10:21.740> but<00:10:22.740> it<00:10:22.830> could<00:10:23.010> be 00:10:23.150 --> 00:10:23.160 align:start position:0% Wi-Fi direct and radio but it could be 00:10:23.160 --> 00:10:25.250 align:start position:0% Wi-Fi direct and radio but it could be like<00:10:23.400> literally<00:10:23.790> anything<00:10:24.089> as<00:10:24.720> long<00:10:24.870> as<00:10:25.110> you 00:10:25.250 --> 00:10:25.260 align:start position:0% like literally anything as long as you 00:10:25.260 --> 00:10:27.079 align:start position:0% like literally anything as long as you conform<00:10:25.620> to<00:10:25.920> like<00:10:26.100> an<00:10:26.310> interface<00:10:26.640> that<00:10:26.970> we 00:10:27.079 --> 00:10:27.089 align:start position:0% conform to like an interface that we 00:10:27.089 --> 00:10:29.449 align:start position:0% conform to like an interface that we need<00:10:27.210> to<00:10:27.270> provide<00:10:27.540> and<00:10:27.860> the<00:10:28.860> interface<00:10:29.310> is 00:10:29.449 --> 00:10:29.459 align:start position:0% need to provide and the interface is 00:10:29.459 --> 00:10:32.240 align:start position:0% need to provide and the interface is very<00:10:29.520> simple<00:10:30.200> this<00:10:31.200> is<00:10:31.380> what<00:10:31.530> our<00:10:31.680> interface 00:10:32.240 --> 00:10:32.250 align:start position:0% very simple this is what our interface 00:10:32.250 --> 00:10:34.610 align:start position:0% very simple this is what our interface looks<00:10:32.520> like<00:10:32.700> you've<00:10:32.970> implemented<00:10:33.620> the 00:10:34.610 --> 00:10:34.620 align:start position:0% looks like you've implemented the 00:10:34.620 --> 00:10:38.030 align:start position:0% looks like you've implemented the Englishman 00:10:38.030 --> 00:10:38.040 align:start position:0% 00:10:38.040 --> 00:10:39.320 align:start position:0% sorry 00:10:39.320 --> 00:10:39.330 align:start position:0% sorry 00:10:39.330 --> 00:10:41.360 align:start position:0% sorry that's<00:10:39.720> our<00:10:40.050> interface<00:10:40.470> you<00:10:40.800> basically<00:10:41.070> have 00:10:41.360 --> 00:10:41.370 align:start position:0% that's our interface you basically have 00:10:41.370 --> 00:10:42.740 align:start position:0% that's our interface you basically have to<00:10:41.490> implement<00:10:41.730> two<00:10:42.060> functions 00:10:42.740 --> 00:10:42.750 align:start position:0% to implement two functions 00:10:42.750 --> 00:10:45.290 align:start position:0% to implement two functions it's<00:10:42.930> descent<00:10:43.380> and<00:10:43.650> listen<00:10:43.980> function<00:10:44.400> so<00:10:44.970> I 00:10:45.290 --> 00:10:45.300 align:start position:0% it's descent and listen function so I 00:10:45.300 --> 00:10:47.480 align:start position:0% it's descent and listen function so I mean<00:10:45.900> theoretically<00:10:46.050> like<00:10:46.620> you<00:10:47.220> can<00:10:47.370> do<00:10:47.460> that 00:10:47.480 --> 00:10:47.490 align:start position:0% mean theoretically like you can do that 00:10:47.490 --> 00:10:50.800 align:start position:0% mean theoretically like you can do that for<00:10:47.760> like<00:10:47.880> any<00:10:48.740> form<00:10:49.740> of<00:10:49.770> communication<00:10:50.010> so 00:10:50.800 --> 00:10:50.810 align:start position:0% for like any form of communication so 00:10:50.810 --> 00:10:54.050 align:start position:0% for like any form of communication so you<00:10:51.810> can<00:10:51.960> even<00:10:52.140> do<00:10:52.230> over<00:10:52.850> ultra<00:10:53.850> high 00:10:54.050 --> 00:10:54.060 align:start position:0% you can even do over ultra high 00:10:54.060 --> 00:10:56.920 align:start position:0% you can even do over ultra high frequency<00:10:54.090> low<00:10:55.050> frequency<00:10:55.620> radios<00:10:56.280> if<00:10:56.580> you 00:10:56.920 --> 00:10:56.930 align:start position:0% frequency low frequency radios if you 00:10:56.930 --> 00:11:02.980 align:start position:0% frequency low frequency radios if you want<00:10:57.930> to<00:10:58.020> implement<00:10:58.230> that<00:11:00.680> so<00:11:01.680> transports 00:11:02.980 --> 00:11:02.990 align:start position:0% want to implement that so transports 00:11:02.990 --> 00:11:06.650 align:start position:0% want to implement that so transports they're<00:11:03.990> interesting<00:11:04.500> because<00:11:05.330> in<00:11:06.330> ultra 00:11:06.650 --> 00:11:06.660 align:start position:0% they're interesting because in ultra 00:11:06.660 --> 00:11:08.180 align:start position:0% they're interesting because in ultra light<00:11:06.780> beam<00:11:06.960> we<00:11:07.410> can<00:11:07.440> support<00:11:07.890> multiple 00:11:08.180 --> 00:11:08.190 align:start position:0% light beam we can support multiple 00:11:08.190 --> 00:11:10.850 align:start position:0% light beam we can support multiple transports<00:11:08.910> at<00:11:09.030> the<00:11:09.120> same<00:11:09.300> time<00:11:09.540> so<00:11:10.380> if<00:11:10.710> you 00:11:10.850 --> 00:11:10.860 align:start position:0% transports at the same time so if you 00:11:10.860 --> 00:11:13.130 align:start position:0% transports at the same time so if you have<00:11:11.040> a<00:11:11.070> device<00:11:11.400> that's<00:11:11.730> Wi-Fi<00:11:12.150> only<00:11:12.420> you<00:11:13.050> have 00:11:13.130 --> 00:11:13.140 align:start position:0% have a device that's Wi-Fi only you have 00:11:13.140 --> 00:11:14.840 align:start position:0% have a device that's Wi-Fi only you have another<00:11:13.380> device<00:11:13.650> that's<00:11:13.890> Bluetooth<00:11:14.280> only<00:11:14.640> you 00:11:14.840 --> 00:11:14.850 align:start position:0% another device that's Bluetooth only you 00:11:14.850 --> 00:11:16.430 align:start position:0% another device that's Bluetooth only you have<00:11:14.970> another<00:11:15.180> device<00:11:15.390> that's<00:11:15.750> Wi-Fi<00:11:16.170> and 00:11:16.430 --> 00:11:16.440 align:start position:0% have another device that's Wi-Fi and 00:11:16.440 --> 00:11:19.700 align:start position:0% have another device that's Wi-Fi and Bluetooth<00:11:17.360> the<00:11:18.360> the<00:11:18.900> devices<00:11:19.320> that<00:11:19.350> are<00:11:19.530> like 00:11:19.700 --> 00:11:19.710 align:start position:0% Bluetooth the the devices that are like 00:11:19.710 --> 00:11:22.100 align:start position:0% Bluetooth the the devices that are like only<00:11:19.980> supporting<00:11:20.970> one<00:11:21.090> transport<00:11:21.600> can<00:11:21.960> also 00:11:22.100 --> 00:11:22.110 align:start position:0% only supporting one transport can also 00:11:22.110 --> 00:11:23.630 align:start position:0% only supporting one transport can also talk<00:11:22.500> to<00:11:22.650> each<00:11:22.710> other<00:11:22.920> by<00:11:23.160> going<00:11:23.400> through<00:11:23.520> the 00:11:23.630 --> 00:11:23.640 align:start position:0% talk to each other by going through the 00:11:23.640 --> 00:11:25.010 align:start position:0% talk to each other by going through the second<00:11:23.940> one<00:11:23.970> and<00:11:24.300> that<00:11:24.390> makes<00:11:24.570> it<00:11:24.660> super 00:11:25.010 --> 00:11:25.020 align:start position:0% second one and that makes it super 00:11:25.020 --> 00:11:26.570 align:start position:0% second one and that makes it super powerful<00:11:25.290> so<00:11:25.950> you<00:11:26.040> can<00:11:26.130> create<00:11:26.250> like<00:11:26.460> these 00:11:26.570 --> 00:11:26.580 align:start position:0% powerful so you can create like these 00:11:26.580 --> 00:11:29.720 align:start position:0% powerful so you can create like these massive<00:11:27.270> networks<00:11:27.960> that<00:11:28.560> are<00:11:28.590> you<00:11:28.980> know<00:11:29.100> in 00:11:29.720 --> 00:11:29.730 align:start position:0% massive networks that are you know in 00:11:29.730 --> 00:11:31.640 align:start position:0% massive networks that are you know in the<00:11:29.940> macroscale<00:11:30.480> or<00:11:30.630> very<00:11:30.810> short-range<00:11:31.140> but 00:11:31.640 --> 00:11:31.650 align:start position:0% the macroscale or very short-range but 00:11:31.650 --> 00:11:34.400 align:start position:0% the macroscale or very short-range but then<00:11:31.860> it<00:11:32.250> connects<00:11:32.580> like<00:11:32.790> larger<00:11:33.540> other 00:11:34.400 --> 00:11:34.410 align:start position:0% then it connects like larger other 00:11:34.410 --> 00:11:36.290 align:start position:0% then it connects like larger other methods<00:11:34.860> perform<00:11:35.280> like<00:11:35.550> a<00:11:35.580> huge<00:11:35.940> magnetic 00:11:36.290 --> 00:11:36.300 align:start position:0% methods perform like a huge magnetic 00:11:36.300 --> 00:11:38.860 align:start position:0% methods perform like a huge magnetic over<00:11:36.660> like<00:11:36.810> radio<00:11:37.170> or<00:11:37.440> something<00:11:37.740> like<00:11:37.830> that 00:11:38.860 --> 00:11:38.870 align:start position:0% over like radio or something like that 00:11:38.870 --> 00:11:41.330 align:start position:0% over like radio or something like that currently<00:11:39.870> for<00:11:40.290> ultra<00:11:40.590> light<00:11:40.770> beam<00:11:41.040> we 00:11:41.330 --> 00:11:41.340 align:start position:0% currently for ultra light beam we 00:11:41.340 --> 00:11:43.700 align:start position:0% currently for ultra light beam we support<00:11:41.820> bluetooth<00:11:42.390> low<00:11:42.600> esteem<00:11:43.050> for<00:11:43.470> short 00:11:43.700 --> 00:11:43.710 align:start position:0% support bluetooth low esteem for short 00:11:43.710 --> 00:11:46.010 align:start position:0% support bluetooth low esteem for short distance<00:11:44.070> communication<00:11:44.280> which<00:11:45.180> we<00:11:45.210> will 00:11:46.010 --> 00:11:46.020 align:start position:0% distance communication which we will 00:11:46.020 --> 00:11:49.370 align:start position:0% distance communication which we will definitely<00:11:46.400> learn<00:11:47.400> it<00:11:47.640> but<00:11:47.910> um<00:11:48.210> soon<00:11:49.170> we're 00:11:49.370 --> 00:11:49.380 align:start position:0% definitely learn it but um soon we're 00:11:49.380 --> 00:11:51.980 align:start position:0% definitely learn it but um soon we're gonna<00:11:49.500> focus<00:11:50.160> on<00:11:50.460> Wi-Fi<00:11:50.850> direct<00:11:51.150> and<00:11:51.630> get<00:11:51.870> that 00:11:51.980 --> 00:11:51.990 align:start position:0% gonna focus on Wi-Fi direct and get that 00:11:51.990 --> 00:11:53.870 align:start position:0% gonna focus on Wi-Fi direct and get that working<00:11:52.200> for<00:11:52.440> Android<00:11:52.920> and<00:11:53.250> so<00:11:53.490> like<00:11:53.640> we<00:11:53.760> can 00:11:53.870 --> 00:11:53.880 align:start position:0% working for Android and so like we can 00:11:53.880 --> 00:12:00.790 align:start position:0% working for Android and so like we can do<00:11:54.690> like<00:11:54.870> a<00:11:55.080> bunch<00:11:55.410> of<00:11:55.500> cool<00:11:55.680> stuff<00:11:58.700> yeah<00:11:59.700> again 00:12:00.790 --> 00:12:00.800 align:start position:0% do like a bunch of cool stuff yeah again 00:12:00.800 --> 00:12:06.230 align:start position:0% do like a bunch of cool stuff yeah again now<00:12:01.800> we<00:12:01.860> talk<00:12:02.100> about<00:12:02.220> services<00:12:03.770> so<00:12:05.240> currently 00:12:06.230 --> 00:12:06.240 align:start position:0% now we talk about services so currently 00:12:06.240 --> 00:12:09.110 align:start position:0% now we talk about services so currently like<00:12:07.050> ultra<00:12:07.410> with<00:12:07.860> gold<00:12:08.130> with<00:12:08.340> ultra<00:12:08.670> beam<00:12:08.940> is 00:12:09.110 --> 00:12:09.120 align:start position:0% like ultra with gold with ultra beam is 00:12:09.120 --> 00:12:11.450 align:start position:0% like ultra with gold with ultra beam is to<00:12:09.240> be<00:12:09.360> able<00:12:09.480> to<00:12:09.630> like<00:12:09.900> relay<00:12:10.260> these<00:12:10.460> generic 00:12:11.450 --> 00:12:11.460 align:start position:0% to be able to like relay these generic 00:12:11.460 --> 00:12:14.140 align:start position:0% to be able to like relay these generic messages<00:12:11.970> like<00:12:12.270> these<00:12:12.420> UV<00:12:13.050> message<00:12:13.380> payloads 00:12:14.140 --> 00:12:14.150 align:start position:0% messages like these UV message payloads 00:12:14.150 --> 00:12:19.190 align:start position:0% messages like these UV message payloads but<00:12:15.150> so<00:12:15.510> services<00:12:15.960> are<00:12:16.140> things<00:12:16.470> like<00:12:17.840> we<00:12:18.840> want 00:12:19.190 --> 00:12:19.200 align:start position:0% but so services are things like we want 00:12:19.200 --> 00:12:20.720 align:start position:0% but so services are things like we want to<00:12:19.260> make<00:12:19.350> it<00:12:19.500> so<00:12:19.770> that<00:12:19.800> ultra<00:12:20.430> light<00:12:20.520> being 00:12:20.720 --> 00:12:20.730 align:start position:0% to make it so that ultra light being 00:12:20.730 --> 00:12:23.030 align:start position:0% to make it so that ultra light being conserved<00:12:21.150> like<00:12:21.420> specific<00:12:21.930> application<00:12:22.560> type 00:12:23.030 --> 00:12:23.040 align:start position:0% conserved like specific application type 00:12:23.040 --> 00:12:25.160 align:start position:0% conserved like specific application type things<00:12:23.280> as<00:12:23.430> well<00:12:23.610> so<00:12:24.450> you<00:12:24.540> want<00:12:24.630> to<00:12:24.750> be<00:12:24.870> able<00:12:25.020> to 00:12:25.160 --> 00:12:25.170 align:start position:0% things as well so you want to be able to 00:12:25.170 --> 00:12:27.440 align:start position:0% things as well so you want to be able to like<00:12:25.440> as<00:12:25.650> grave<00:12:26.400> said<00:12:26.640> before<00:12:26.970> the<00:12:27.090> relay 00:12:27.440 --> 00:12:27.450 align:start position:0% like as grave said before the relay 00:12:27.450 --> 00:12:31.610 align:start position:0% like as grave said before the relay transactions<00:12:29.780> offline<00:12:30.780> like<00:12:31.020> on<00:12:31.170> a<00:12:31.200> plane<00:12:31.470> or 00:12:31.610 --> 00:12:31.620 align:start position:0% transactions offline like on a plane or 00:12:31.620 --> 00:12:32.540 align:start position:0% transactions offline like on a plane or something<00:12:31.920> like<00:12:32.010> that 00:12:32.540 --> 00:12:32.550 align:start position:0% something like that 00:12:32.550 --> 00:12:35.060 align:start position:0% something like that maybe<00:12:32.790> one<00:12:32.970> guy's<00:12:33.180> Wi-Fi<00:12:33.750> because<00:12:34.140> a<00:12:34.290> rich<00:12:34.740> in 00:12:35.060 --> 00:12:35.070 align:start position:0% maybe one guy's Wi-Fi because a rich in 00:12:35.070 --> 00:12:43.790 align:start position:0% maybe one guy's Wi-Fi because a rich in the<00:12:35.310> bodies<00:12:39.740> are<00:12:40.740> change<00:12:42.320> state<00:12:43.320> channel 00:12:43.790 --> 00:12:43.800 align:start position:0% the bodies are change state channel 00:12:43.800 --> 00:12:52.130 align:start position:0% the bodies are change state channel you're<00:12:43.920> gonna<00:12:44.040> clean<00:12:50.690> you<00:12:51.690> can<00:12:51.810> start<00:12:52.050> the 00:12:52.130 --> 00:12:52.140 align:start position:0% you're gonna clean you can start the 00:12:52.140 --> 00:12:54.230 align:start position:0% you're gonna clean you can start the offline<00:12:52.530> state<00:12:52.860> channels<00:12:53.250> within<00:12:53.430> like<00:12:54.210> a 00:12:54.230 --> 00:12:54.240 align:start position:0% offline state channels within like a 00:12:54.240 --> 00:12:59.660 align:start position:0% offline state channels within like a plane<00:12:54.510> and<00:12:54.780> send<00:12:55.020> people<00:12:55.860> money<00:12:57.140> or<00:12:58.520> you<00:12:59.520> can 00:12:59.660 --> 00:12:59.670 align:start position:0% plane and send people money or you can 00:12:59.670 --> 00:13:01.940 align:start position:0% plane and send people money or you can just<00:12:59.850> doing<00:13:00.210> chat<00:13:00.450> messaging<00:13:00.960> so<00:13:01.530> these<00:13:01.770> are 00:13:01.940 --> 00:13:01.950 align:start position:0% just doing chat messaging so these are 00:13:01.950 --> 00:13:04.250 align:start position:0% just doing chat messaging so these are what<00:13:02.070> like<00:13:02.250> services<00:13:02.730> are<00:13:02.880> they<00:13:03.060> defined<00:13:03.510> like 00:13:04.250 --> 00:13:04.260 align:start position:0% what like services are they defined like 00:13:04.260 --> 00:13:06.380 align:start position:0% what like services are they defined like how<00:13:04.770> when<00:13:05.100> these<00:13:05.220> like<00:13:05.730> how<00:13:05.880> to<00:13:05.940> handle<00:13:06.000> these 00:13:06.380 --> 00:13:06.390 align:start position:0% how when these like how to handle these 00:13:06.390 --> 00:13:09.560 align:start position:0% how when these like how to handle these messages<00:13:06.930> if<00:13:07.710> you're<00:13:07.890> a<00:13:07.920> node<00:13:08.160> and<00:13:08.570> nodes 00:13:09.560 --> 00:13:09.570 align:start position:0% messages if you're a node and nodes 00:13:09.570 --> 00:13:11.570 align:start position:0% messages if you're a node and nodes don't<00:13:09.690> have<00:13:09.900> to<00:13:09.990> support<00:13:10.170> all<00:13:10.560> services<00:13:11.190> equal 00:13:11.570 --> 00:13:11.580 align:start position:0% don't have to support all services equal 00:13:11.580 --> 00:13:13.550 align:start position:0% don't have to support all services equal support<00:13:11.880> some<00:13:12.240> services<00:13:12.750> and<00:13:12.960> they<00:13:13.350> can't 00:13:13.550 --> 00:13:13.560 align:start position:0% support some services and they can't 00:13:13.560 --> 00:13:14.840 align:start position:0% support some services and they can't support<00:13:13.710> it<00:13:13.950> they<00:13:14.040> just<00:13:14.220> like<00:13:14.340> sent<00:13:14.580> somebody 00:13:14.840 --> 00:13:14.850 align:start position:0% support it they just like sent somebody 00:13:14.850 --> 00:13:17.270 align:start position:0% support it they just like sent somebody else<00:13:14.970> who's<00:13:15.720> on<00:13:15.870> their<00:13:16.020> peer<00:13:16.170> list<00:13:16.350> and<00:13:16.680> maybe 00:13:17.270 --> 00:13:17.280 align:start position:0% else who's on their peer list and maybe 00:13:17.280 --> 00:13:19.010 align:start position:0% else who's on their peer list and maybe they<00:13:17.490> can<00:13:17.550> support<00:13:17.910> it<00:13:18.090> just<00:13:18.390> keeps<00:13:18.660> going<00:13:18.840> and 00:13:19.010 --> 00:13:19.020 align:start position:0% they can support it just keeps going and 00:13:19.020 --> 00:13:25.130 align:start position:0% they can support it just keeps going and going<00:13:21.050> yeah<00:13:23.090> so<00:13:24.090> relayer<00:13:24.750> we<00:13:24.990> have<00:13:25.080> the 00:13:25.130 --> 00:13:25.140 align:start position:0% going yeah so relayer we have the 00:13:25.140 --> 00:13:27.470 align:start position:0% going yeah so relayer we have the concept<00:13:25.500> of<00:13:25.560> relayer<00:13:25.980> that's<00:13:26.310> a<00:13:26.670> node<00:13:27.210> that 00:13:27.470 --> 00:13:27.480 align:start position:0% concept of relayer that's a node that 00:13:27.480 --> 00:13:30.020 align:start position:0% concept of relayer that's a node that generally<00:13:28.320> lives<00:13:28.740> like<00:13:29.100> on<00:13:29.250> the<00:13:29.370> edge<00:13:29.520> of<00:13:29.850> the 00:13:30.020 --> 00:13:30.030 align:start position:0% generally lives like on the edge of the 00:13:30.030 --> 00:13:33.530 align:start position:0% generally lives like on the edge of the mesh<00:13:30.240> network<00:13:30.920> like<00:13:31.920> for<00:13:32.760> example<00:13:32.850> like<00:13:33.360> in 00:13:33.530 --> 00:13:33.540 align:start position:0% mesh network like for example like in 00:13:33.540 --> 00:13:36.230 align:start position:0% mesh network like for example like in the<00:13:33.680> like<00:13:34.680> in<00:13:34.950> a<00:13:34.980> yeah<00:13:35.250> like<00:13:35.550> a<00:13:35.610> festival<00:13:35.850> or 00:13:36.230 --> 00:13:36.240 align:start position:0% the like in a yeah like a festival or 00:13:36.240 --> 00:13:38.360 align:start position:0% the like in a yeah like a festival or something<00:13:36.390> like<00:13:36.660> that<00:13:36.870> there<00:13:37.590> is<00:13:37.890> technically 00:13:38.360 --> 00:13:38.370 align:start position:0% something like that there is technically 00:13:38.370 --> 00:13:41.030 align:start position:0% something like that there is technically like<00:13:38.670> you<00:13:39.060> know<00:13:39.180> there<00:13:40.170> is<00:13:40.260> like<00:13:40.470> cell<00:13:40.710> signal 00:13:41.030 --> 00:13:41.040 align:start position:0% like you know there is like cell signal 00:13:41.040 --> 00:13:42.950 align:start position:0% like you know there is like cell signal but<00:13:41.190> it's<00:13:41.310> like<00:13:41.460> super<00:13:41.880> bad<00:13:42.060> but<00:13:42.630> it<00:13:42.720> might<00:13:42.840> be 00:13:42.950 --> 00:13:42.960 align:start position:0% but it's like super bad but it might be 00:13:42.960 --> 00:13:44.780 align:start position:0% but it's like super bad but it might be good<00:13:43.170> for<00:13:43.200> the<00:13:43.410> guy<00:13:43.560> who's<00:13:43.830> like<00:13:44.040> maybe<00:13:44.670> a 00:13:44.780 --> 00:13:44.790 align:start position:0% good for the guy who's like maybe a 00:13:44.790 --> 00:13:46.250 align:start position:0% good for the guy who's like maybe a little<00:13:44.940> bit<00:13:45.090> further<00:13:45.360> out<00:13:45.480> from<00:13:45.870> like<00:13:46.140> some 00:13:46.250 --> 00:13:46.260 align:start position:0% little bit further out from like some 00:13:46.260 --> 00:13:50.120 align:start position:0% little bit further out from like some background<00:13:46.740> and<00:13:46.980> that<00:13:47.640> guy's<00:13:47.850> internet<00:13:49.130> so 00:13:50.120 --> 00:13:50.130 align:start position:0% background and that guy's internet so 00:13:50.130 --> 00:13:51.410 align:start position:0% background and that guy's internet so you<00:13:50.310> know<00:13:50.400> you<00:13:50.550> might<00:13:50.790> try<00:13:51.030> something<00:13:51.300> a 00:13:51.410 --> 00:13:51.420 align:start position:0% you know you might try something a 00:13:51.420 --> 00:13:53.000 align:start position:0% you know you might try something a facebook<00:13:51.810> message<00:13:51.990> to<00:13:52.350> your<00:13:52.440> mom<00:13:52.590> showing 00:13:53.000 --> 00:13:53.010 align:start position:0% facebook message to your mom showing 00:13:53.010 --> 00:13:57.910 align:start position:0% facebook message to your mom showing like<00:13:53.220> your<00:13:53.610> party 00:13:57.910 --> 00:13:57.920 align:start position:0% 00:13:57.920 --> 00:13:59.560 align:start position:0% but<00:13:58.340> you<00:13:58.430> can't<00:13:58.670> kiss<00:13:58.940> your<00:13:59.120> like<00:13:59.210> in<00:13:59.420> the 00:13:59.560 --> 00:13:59.570 align:start position:0% but you can't kiss your like in the 00:13:59.570 --> 00:14:02.200 align:start position:0% but you can't kiss your like in the middle<00:13:59.870> of<00:14:00.080> the<00:14:00.410> festival<00:14:00.920> so<00:14:01.790> you<00:14:01.880> send<00:14:02.090> it 00:14:02.200 --> 00:14:02.210 align:start position:0% middle of the festival so you send it 00:14:02.210 --> 00:14:04.210 align:start position:0% middle of the festival so you send it out<00:14:02.300> through<00:14:02.570> ultralight<00:14:03.170> beam<00:14:03.350> it<00:14:03.800> goes<00:14:04.010> like 00:14:04.210 --> 00:14:04.220 align:start position:0% out through ultralight beam it goes like 00:14:04.220 --> 00:14:05.800 align:start position:0% out through ultralight beam it goes like through<00:14:04.640> a<00:14:04.670> bunch<00:14:04.850> of<00:14:04.910> people<00:14:05.240> and<00:14:05.480> then<00:14:05.630> it 00:14:05.800 --> 00:14:05.810 align:start position:0% through a bunch of people and then it 00:14:05.810 --> 00:14:07.360 align:start position:0% through a bunch of people and then it finally<00:14:06.170> hits<00:14:06.320> a<00:14:06.410> guy<00:14:06.560> who<00:14:06.620> has<00:14:06.800> internet<00:14:07.220> and 00:14:07.360 --> 00:14:07.370 align:start position:0% finally hits a guy who has internet and 00:14:07.370 --> 00:14:10.420 align:start position:0% finally hits a guy who has internet and he<00:14:07.580> relays<00:14:08.540> it<00:14:08.720> to<00:14:08.750> the<00:14:09.500> internet<00:14:09.890> gets<00:14:10.160> Nessa 00:14:10.420 --> 00:14:10.430 align:start position:0% he relays it to the internet gets Nessa 00:14:10.430 --> 00:14:12.430 align:start position:0% he relays it to the internet gets Nessa tracking<00:14:10.850> this<00:14:11.000> you<00:14:11.330> know<00:14:11.420> like<00:14:11.540> tracing<00:14:12.020> back 00:14:12.430 --> 00:14:12.440 align:start position:0% tracking this you know like tracing back 00:14:12.440 --> 00:14:17.410 align:start position:0% tracking this you know like tracing back to<00:14:12.770> you<00:14:14.140> so<00:14:15.140> yeah<00:14:16.090> generally<00:14:17.090> these<00:14:17.360> things 00:14:17.410 --> 00:14:17.420 align:start position:0% to you so yeah generally these things 00:14:17.420 --> 00:14:19.870 align:start position:0% to you so yeah generally these things like<00:14:17.780> living<00:14:18.020> on<00:14:18.080> the<00:14:18.170> edge<00:14:18.200> of<00:14:18.650> the<00:14:18.860> network<00:14:19.010> I 00:14:19.870 --> 00:14:19.880 align:start position:0% like living on the edge of the network I 00:14:19.880 --> 00:14:25.780 align:start position:0% like living on the edge of the network I just<00:14:20.540> said<00:14:20.660> that<00:14:23.140> yeah<00:14:24.140> so<00:14:24.770> we<00:14:25.280> have<00:14:25.400> Bluetooth 00:14:25.780 --> 00:14:25.790 align:start position:0% just said that yeah so we have Bluetooth 00:14:25.790 --> 00:14:28.240 align:start position:0% just said that yeah so we have Bluetooth Low<00:14:26.210> Energy<00:14:26.240> right<00:14:26.810> now<00:14:26.930> you<00:14:27.830> got<00:14:27.980> it<00:14:28.070> working 00:14:28.240 --> 00:14:28.250 align:start position:0% Low Energy right now you got it working 00:14:28.250 --> 00:14:31.150 align:start position:0% Low Energy right now you got it working on<00:14:28.520> Mac<00:14:28.700> OS<00:14:29.060> it<00:14:29.840> should<00:14:30.020> be<00:14:30.140> fairly<00:14:30.620> simple<00:14:30.860> to 00:14:31.150 --> 00:14:31.160 align:start position:0% on Mac OS it should be fairly simple to 00:14:31.160 --> 00:14:33.900 align:start position:0% on Mac OS it should be fairly simple to get<00:14:31.250> it<00:14:31.430> on<00:14:31.610> iOS<00:14:31.820> because<00:14:32.360> we're<00:14:32.690> using<00:14:32.840> only 00:14:33.900 --> 00:14:33.910 align:start position:0% get it on iOS because we're using only 00:14:33.910 --> 00:14:37.420 align:start position:0% get it on iOS because we're using only libraries<00:14:34.910> that<00:14:35.120> are<00:14:35.180> core<00:14:35.750> apple<00:14:36.430> and 00:14:37.420 --> 00:14:37.430 align:start position:0% libraries that are core apple and 00:14:37.430 --> 00:14:40.090 align:start position:0% libraries that are core apple and they're<00:14:37.670> cross-platform<00:14:38.530> we're<00:14:39.530> going<00:14:39.800> to<00:14:39.950> do 00:14:40.090 --> 00:14:40.100 align:start position:0% they're cross-platform we're going to do 00:14:40.100 --> 00:14:42.370 align:start position:0% they're cross-platform we're going to do Wi-Fi<00:14:40.520> direct<00:14:40.790> soon<00:14:41.360> it's<00:14:42.170> going<00:14:42.260> to<00:14:42.320> be 00:14:42.370 --> 00:14:42.380 align:start position:0% Wi-Fi direct soon it's going to be 00:14:42.380 --> 00:14:44.740 align:start position:0% Wi-Fi direct soon it's going to be supported<00:14:42.800> on<00:14:42.890> Android<00:14:43.070> and<00:14:43.550> all<00:14:43.640> that<00:14:43.880> so 00:14:44.740 --> 00:14:44.750 align:start position:0% supported on Android and all that so 00:14:44.750 --> 00:14:49.300 align:start position:0% supported on Android and all that so that's<00:14:44.900> gonna<00:14:45.050> be<00:14:45.170> dope<00:14:47.620> don't<00:14:48.620> go<00:14:48.740> don't<00:14:49.190> go 00:14:49.300 --> 00:14:49.310 align:start position:0% that's gonna be dope don't go don't go 00:14:49.310 --> 00:14:52.150 align:start position:0% that's gonna be dope don't go don't go to<00:14:49.400> bed<00:14:49.580> yeah<00:14:49.960> yeah<00:14:50.960> yeah<00:14:51.470> so<00:14:51.770> we<00:14:51.920> were<00:14:52.010> gonna 00:14:52.150 --> 00:14:52.160 align:start position:0% to bed yeah yeah yeah so we were gonna 00:14:52.160 --> 00:14:54.310 align:start position:0% to bed yeah yeah yeah so we were gonna prepare<00:14:52.580> a<00:14:52.610> full<00:14:52.850> workshop<00:14:53.150> and<00:14:53.600> then<00:14:53.990> we<00:14:54.140> got 00:14:54.310 --> 00:14:54.320 align:start position:0% prepare a full workshop and then we got 00:14:54.320 --> 00:14:55.720 align:start position:0% prepare a full workshop and then we got here<00:14:54.560> on<00:14:54.590> the<00:14:54.680> first<00:14:55.010> day<00:14:55.100> and<00:14:55.250> we<00:14:55.310> realized 00:14:55.720 --> 00:14:55.730 align:start position:0% here on the first day and we realized 00:14:55.730 --> 00:14:57.400 align:start position:0% here on the first day and we realized that<00:14:55.790> the<00:14:55.940> Internet<00:14:56.330> of<00:14:56.690> and<00:14:56.960> so<00:14:57.200> getting 00:14:57.400 --> 00:14:57.410 align:start position:0% that the Internet of and so getting 00:14:57.410 --> 00:14:59.410 align:start position:0% that the Internet of and so getting you<00:14:57.620> guys<00:14:57.740> to<00:14:57.800> download<00:14:58.250> packages<00:14:59.030> and<00:14:59.210> stuff 00:14:59.410 --> 00:14:59.420 align:start position:0% you guys to download packages and stuff 00:14:59.420 --> 00:15:01.230 align:start position:0% you guys to download packages and stuff like<00:14:59.540> that<00:14:59.750> isn't<00:15:00.140> going<00:15:00.260> to<00:15:00.320> work<00:15:00.410> for<00:15:00.650> us<00:15:00.740> so 00:15:01.230 --> 00:15:01.240 align:start position:0% like that isn't going to work for us so 00:15:01.240 --> 00:15:04.240 align:start position:0% like that isn't going to work for us so what<00:15:02.240> we've<00:15:02.450> decided<00:15:02.900> to<00:15:03.080> do<00:15:03.290> is<00:15:03.650> that<00:15:03.710> we'll 00:15:04.240 --> 00:15:04.250 align:start position:0% what we've decided to do is that we'll 00:15:04.250 --> 00:15:07.270 align:start position:0% what we've decided to do is that we'll do<00:15:04.850> we'll<00:15:05.480> try<00:15:05.750> to<00:15:05.810> do<00:15:05.990> a<00:15:06.020> quick<00:15:06.380> demo<00:15:06.650> live<00:15:06.980> of 00:15:07.270 --> 00:15:07.280 align:start position:0% do we'll try to do a quick demo live of 00:15:07.280 --> 00:15:09.880 align:start position:0% do we'll try to do a quick demo live of how<00:15:07.910> one<00:15:08.750> of<00:15:08.900> the<00:15:09.050> real<00:15:09.230> ER<00:15:09.320> works<00:15:09.560> just<00:15:09.830> to 00:15:09.880 --> 00:15:09.890 align:start position:0% how one of the real ER works just to 00:15:09.890 --> 00:15:11.680 align:start position:0% how one of the real ER works just to show<00:15:10.730> that<00:15:10.760> this<00:15:11.210> isn't<00:15:11.570> completely 00:15:11.680 --> 00:15:11.690 align:start position:0% show that this isn't completely 00:15:11.690 --> 00:15:14.230 align:start position:0% show that this isn't completely vaporware<00:15:12.620> that<00:15:13.160> we<00:15:13.280> can<00:15:13.430> actually<00:15:13.580> send<00:15:14.060> and 00:15:14.230 --> 00:15:14.240 align:start position:0% vaporware that we can actually send and 00:15:14.240 --> 00:15:15.180 align:start position:0% vaporware that we can actually send and receive<00:15:14.540> messages 00:15:15.180 --> 00:15:15.190 align:start position:0% receive messages 00:15:15.190 --> 00:15:24.520 align:start position:0% receive messages did<00:15:16.190> you<00:15:16.310> guys<00:15:16.460> download<00:15:16.820> I<00:15:23.380> figured<00:15:24.380> you 00:15:24.520 --> 00:15:24.530 align:start position:0% did you guys download I figured you 00:15:24.530 --> 00:15:28.080 align:start position:0% did you guys download I figured you would 00:15:28.080 --> 00:15:28.090 align:start position:0% 00:15:28.090 --> 00:15:31.060 align:start position:0% if<00:15:29.090> you<00:15:29.300> guys<00:15:29.390> actually<00:15:29.840> have<00:15:30.140> Xcode<00:15:30.740> you<00:15:30.920> guys 00:15:31.060 --> 00:15:31.070 align:start position:0% if you guys actually have Xcode you guys 00:15:31.070 --> 00:15:33.930 align:start position:0% if you guys actually have Xcode you guys can<00:15:31.280> pull<00:15:31.490> a<00:15:31.520> repo<00:15:31.940> and<00:15:32.240> join<00:15:32.510> our<00:15:32.690> network<00:15:32.810> too 00:15:33.930 --> 00:15:33.940 align:start position:0% can pull a repo and join our network too 00:15:33.940 --> 00:15:36.850 align:start position:0% can pull a repo and join our network too but<00:15:34.940> yeah<00:15:35.270> if<00:15:35.360> anyone<00:15:35.630> has<00:15:35.840> a<00:15:35.870> Mac<00:15:36.170> with<00:15:36.380> Xcode 00:15:36.850 --> 00:15:36.860 align:start position:0% but yeah if anyone has a Mac with Xcode 00:15:36.860 --> 00:15:38.830 align:start position:0% but yeah if anyone has a Mac with Xcode an<00:15:37.130> internet<00:15:37.760> they<00:15:38.030> could<00:15:38.210> pretty<00:15:38.390> much<00:15:38.480> pull 00:15:38.830 --> 00:15:38.840 align:start position:0% an internet they could pretty much pull 00:15:38.840 --> 00:16:07.510 align:start position:0% an internet they could pretty much pull and<00:15:39.140> join<00:16:03.760> you<00:16:04.760> have<00:16:04.910> any<00:16:05.060> questions<00:16:05.800> yes<00:16:06.800> yes 00:16:07.510 --> 00:16:07.520 align:start position:0% and join you have any questions yes yes 00:16:07.520 --> 00:16:08.830 align:start position:0% and join you have any questions yes yes I<00:16:07.550> was<00:16:07.790> learning<00:16:08.030> about<00:16:08.090> the<00:16:08.390> Facebook 00:16:08.830 --> 00:16:08.840 align:start position:0% I was learning about the Facebook 00:16:08.840 --> 00:16:11.650 align:start position:0% I was learning about the Facebook example<00:16:09.350> so<00:16:10.340> they<00:16:10.940> start<00:16:11.210> asking<00:16:11.360> for 00:16:11.650 --> 00:16:11.660 align:start position:0% example so they start asking for 00:16:11.660 --> 00:16:16.860 align:start position:0% example so they start asking for messages<00:16:11.900> but<00:16:12.440> can<00:16:12.560> they<00:16:12.680> actually<00:16:12.830> initiate 00:16:16.860 --> 00:16:16.870 align:start position:0% 00:16:16.870 --> 00:16:21.670 align:start position:0% communication<00:16:18.670> in<00:16:19.670> theory<00:16:20.030> yeah<00:16:20.330> but<00:16:21.170> that's 00:16:21.670 --> 00:16:21.680 align:start position:0% communication in theory yeah but that's 00:16:21.680 --> 00:16:27.370 align:start position:0% communication in theory yeah but that's like<00:16:21.890> a<00:16:21.920> lot<00:16:22.130> of<00:16:22.160> work<00:16:25.660> dean<00:16:26.660> of<00:16:26.810> inland<00:16:27.080> coding 00:16:27.370 --> 00:16:27.380 align:start position:0% like a lot of work dean of inland coding 00:16:27.380 --> 00:16:29.950 align:start position:0% like a lot of work dean of inland coding this<00:16:27.710> for<00:16:28.130> like<00:16:28.280> the<00:16:29.150> last<00:16:29.270> four<00:16:29.540> months<00:16:29.690> we've 00:16:29.950 --> 00:16:29.960 align:start position:0% this for like the last four months we've 00:16:29.960 --> 00:16:32.890 align:start position:0% this for like the last four months we've been<00:16:29.990> spending<00:16:30.440> like<00:16:30.680> 10%<00:16:31.100> of<00:16:31.310> our<00:16:31.430> time<00:16:31.900> 20% 00:16:32.890 --> 00:16:32.900 align:start position:0% been spending like 10% of our time 20% 00:16:32.900 --> 00:16:37.810 align:start position:0% been spending like 10% of our time 20% because<00:16:33.020> we<00:16:33.260> have<00:16:33.350> like<00:16:33.440> eight<00:16:33.710> jobs<00:16:36.760> yeah<00:16:37.760> you 00:16:37.810 --> 00:16:37.820 align:start position:0% because we have like eight jobs yeah you 00:16:37.820 --> 00:16:42.220 align:start position:0% because we have like eight jobs yeah you could<00:16:38.180> we<00:16:38.840> made<00:16:39.080> like<00:16:39.770> design<00:16:40.460> is<00:16:41.120> that<00:16:41.510> like 00:16:42.220 --> 00:16:42.230 align:start position:0% could we made like design is that like 00:16:42.230 --> 00:16:43.960 align:start position:0% could we made like design is that like our<00:16:42.380> rationale<00:16:43.010> behind<00:16:43.130> like<00:16:43.460> our<00:16:43.580> design<00:16:43.820> is 00:16:43.960 --> 00:16:43.970 align:start position:0% our rationale behind like our design is 00:16:43.970 --> 00:16:45.850 align:start position:0% our rationale behind like our design is like<00:16:44.060> we<00:16:44.210> made<00:16:44.390> it<00:16:44.420> generic<00:16:44.930> enough<00:16:45.050> such<00:16:45.830> that 00:16:45.850 --> 00:16:45.860 align:start position:0% like we made it generic enough such that 00:16:45.860 --> 00:16:47.920 align:start position:0% like we made it generic enough such that you<00:16:46.220> can<00:16:46.370> do<00:16:46.760> whatever<00:16:46.970> you<00:16:47.240> want<00:16:47.480> on<00:16:47.600> it<00:16:47.660> this 00:16:47.920 --> 00:16:47.930 align:start position:0% you can do whatever you want on it this 00:16:47.930 --> 00:16:51.070 align:start position:0% you can do whatever you want on it this is<00:16:48.080> like<00:16:48.230> we<00:16:48.890> just<00:16:49.040> provide<00:16:49.370> you<00:16:49.960> you<00:16:50.960> know 00:16:51.070 --> 00:16:51.080 align:start position:0% is like we just provide you you know 00:16:51.080 --> 00:16:53.650 align:start position:0% is like we just provide you you know like<00:16:51.230> a<00:16:51.530> way<00:16:52.220> to<00:16:52.280> like<00:16:52.580> just<00:16:52.820> send<00:16:53.270> messages 00:16:53.650 --> 00:16:53.660 align:start position:0% like a way to like just send messages 00:16:53.660 --> 00:16:55.720 align:start position:0% like a way to like just send messages but<00:16:53.840> you<00:16:54.020> can<00:16:54.140> definitely<00:16:54.260> encrypt<00:16:54.830> messages 00:16:55.720 --> 00:16:55.730 align:start position:0% but you can definitely encrypt messages 00:16:55.730 --> 00:16:58.930 align:start position:0% but you can definitely encrypt messages you<00:16:56.150> can<00:16:56.330> probably<00:16:57.020> build<00:16:57.320> tcp<00:16:57.890> on<00:16:58.070> this<00:16:58.310> you 00:16:58.930 --> 00:16:58.940 align:start position:0% you can probably build tcp on this you 00:16:58.940 --> 00:17:01.780 align:start position:0% you can probably build tcp on this you probably<00:16:59.240> build<00:16:59.450> like<00:16:59.930> into<00:17:00.680> HTTP<00:17:01.400> on<00:17:01.610> that's 00:17:01.780 --> 00:17:01.790 align:start position:0% probably build like into HTTP on that's 00:17:01.790 --> 00:17:04.720 align:start position:0% probably build like into HTTP on that's too<00:17:01.850> probably<00:17:03.430> there 00:17:04.720 --> 00:17:04.730 align:start position:0% too probably there 00:17:04.730 --> 00:17:13.819 align:start position:0% too probably there yes<00:17:10.640> yeah<00:17:11.640> so<00:17:12.600> it's<00:17:13.230> like<00:17:13.439> super<00:17:13.589> generic 00:17:13.819 --> 00:17:13.829 align:start position:0% yes yeah so it's like super generic 00:17:13.829 --> 00:17:21.319 align:start position:0% yes yeah so it's like super generic should<00:17:14.429> wear<00:17:14.579> girls<00:17:14.789> it<00:17:14.909> over<00:17:15.149> yeah<00:17:19.880> so<00:17:20.880> going 00:17:21.319 --> 00:17:21.329 align:start position:0% should wear girls it over yeah so going 00:17:21.329 --> 00:17:23.090 align:start position:0% should wear girls it over yeah so going back<00:17:21.539> to<00:17:21.600> your<00:17:21.809> music<00:17:22.289> festival<00:17:22.649> example 00:17:23.090 --> 00:17:23.100 align:start position:0% back to your music festival example 00:17:23.100 --> 00:17:24.889 align:start position:0% back to your music festival example thing<00:17:23.250> so<00:17:23.520> the<00:17:23.640> guy<00:17:23.970> on<00:17:24.179> the<00:17:24.299> periphery<00:17:24.779> who 00:17:24.889 --> 00:17:24.899 align:start position:0% thing so the guy on the periphery who 00:17:24.899 --> 00:17:27.529 align:start position:0% thing so the guy on the periphery who actually<00:17:25.049> has<00:17:25.380> serviced<00:17:26.370> this<00:17:26.850> we<00:17:27.089> need<00:17:27.360> to<00:17:27.449> be 00:17:27.529 --> 00:17:27.539 align:start position:0% actually has serviced this we need to be 00:17:27.539 --> 00:17:30.560 align:start position:0% actually has serviced this we need to be like<00:17:27.870> running<00:17:28.110> this<00:17:28.380> I<00:17:29.000> yeah<00:17:30.000> so<00:17:30.419> like 00:17:30.560 --> 00:17:30.570 align:start position:0% like running this I yeah so like 00:17:30.570 --> 00:17:34.519 align:start position:0% like running this I yeah so like everyone<00:17:31.250> involved<00:17:32.250> in<00:17:32.580> that<00:17:32.730> chain<00:17:33.390> of<00:17:33.529> yeah 00:17:34.519 --> 00:17:34.529 align:start position:0% everyone involved in that chain of yeah 00:17:34.529 --> 00:17:36.710 align:start position:0% everyone involved in that chain of yeah yes<00:17:35.010> so<00:17:35.190> we<00:17:35.340> still<00:17:35.520> have<00:17:35.789> this<00:17:35.940> yes<00:17:36.299> of<00:17:36.539> like 00:17:36.710 --> 00:17:36.720 align:start position:0% yes so we still have this yes of like 00:17:36.720 --> 00:17:39.230 align:start position:0% yes so we still have this yes of like the<00:17:37.140> the<00:17:37.529> idea<00:17:37.919> behind<00:17:38.190> what<00:17:38.730> we've<00:17:38.909> done<00:17:39.090> is 00:17:39.230 --> 00:17:39.240 align:start position:0% the the idea behind what we've done is 00:17:39.240 --> 00:17:40.340 align:start position:0% the the idea behind what we've done is we're<00:17:39.419> trying<00:17:39.539> to<00:17:39.659> make<00:17:39.779> it<00:17:39.899> as<00:17:39.990> minimal<00:17:40.260> as 00:17:40.340 --> 00:17:40.350 align:start position:0% we're trying to make it as minimal as 00:17:40.350 --> 00:17:47.090 align:start position:0% we're trying to make it as minimal as possible<00:17:40.440> because<00:17:41.130> that<00:17:41.880> way<00:17:42.090> he<00:17:44.539> any<00:17:45.799> any<00:17:46.799> app 00:17:47.090 --> 00:17:47.100 align:start position:0% possible because that way he any any app 00:17:47.100 --> 00:17:50.230 align:start position:0% possible because that way he any any app could<00:17:47.429> integrate<00:17:47.730> this<00:17:48.360> the<00:17:49.080> protocol<00:17:49.590> itself 00:17:50.230 --> 00:17:50.240 align:start position:0% could integrate this the protocol itself 00:17:50.240 --> 00:17:54.049 align:start position:0% could integrate this the protocol itself as<00:17:51.240> like<00:17:51.630> a<00:17:51.659> secondary<00:17:52.200> pop<00:17:52.470> as<00:17:52.710> like<00:17:52.830> a<00:17:53.000> like<00:17:54.000> a 00:17:54.049 --> 00:17:54.059 align:start position:0% as like a secondary pop as like a like a 00:17:54.059 --> 00:17:55.460 align:start position:0% as like a secondary pop as like a like a layer<00:17:54.270> on<00:17:54.299> top<00:17:54.510> of<00:17:54.690> like<00:17:54.960> an<00:17:55.080> existing 00:17:55.460 --> 00:17:55.470 align:start position:0% layer on top of like an existing 00:17:55.470 --> 00:17:57.620 align:start position:0% layer on top of like an existing messaging<00:17:55.950> service<00:17:56.429> right<00:17:56.789> so<00:17:57.390> this<00:17:57.480> isn't 00:17:57.620 --> 00:17:57.630 align:start position:0% messaging service right so this isn't 00:17:57.630 --> 00:18:00.560 align:start position:0% messaging service right so this isn't like<00:17:57.899> we're<00:17:58.830> making<00:17:58.980> another<00:17:59.340> chata<00:17:59.669> this<00:18:00.390> is 00:18:00.560 --> 00:18:00.570 align:start position:0% like we're making another chata this is 00:18:00.570 --> 00:18:03.139 align:start position:0% like we're making another chata this is like<00:18:00.750> hey<00:18:01.020> please<00:18:01.799> use<00:18:02.070> this<00:18:02.309> as<00:18:02.610> a<00:18:02.669> forum<00:18:03.090> to 00:18:03.139 --> 00:18:03.149 align:start position:0% like hey please use this as a forum to 00:18:03.149 --> 00:18:05.600 align:start position:0% like hey please use this as a forum to do<00:18:03.419> your<00:18:03.630> if<00:18:03.899> to<00:18:04.559> this<00:18:04.980> is<00:18:05.159> like<00:18:05.279> this<00:18:05.399> way<00:18:05.549> to 00:18:05.600 --> 00:18:05.610 align:start position:0% do your if to this is like this way to 00:18:05.610 --> 00:18:07.970 align:start position:0% do your if to this is like this way to like<00:18:05.850> toggle<00:18:06.360> like<00:18:06.570> hey<00:18:06.840> I<00:18:07.140> want<00:18:07.470> to<00:18:07.529> like<00:18:07.770> use 00:18:07.970 --> 00:18:07.980 align:start position:0% like toggle like hey I want to like use 00:18:07.980 --> 00:18:10.880 align:start position:0% like toggle like hey I want to like use the<00:18:08.159> offline<00:18:08.610> mode<00:18:09.140> so<00:18:10.140> your<00:18:10.260> existing<00:18:10.679> like 00:18:10.880 --> 00:18:10.890 align:start position:0% the offline mode so your existing like 00:18:10.890 --> 00:18:13.850 align:start position:0% the offline mode so your existing like Java<00:18:11.190> that's<00:18:11.909> kind<00:18:12.120> of<00:18:12.149> like<00:18:12.330> the<00:18:12.779> design<00:18:13.440> idea 00:18:13.850 --> 00:18:13.860 align:start position:0% Java that's kind of like the design idea 00:18:13.860 --> 00:18:16.370 align:start position:0% Java that's kind of like the design idea so<00:18:14.250> in<00:18:14.490> theory<00:18:14.970> if<00:18:15.330> you<00:18:15.360> went<00:18:15.720> into<00:18:15.960> that<00:18:16.080> mode 00:18:16.370 --> 00:18:16.380 align:start position:0% so in theory if you went into that mode 00:18:16.380 --> 00:18:18.230 align:start position:0% so in theory if you went into that mode you<00:18:16.710> could<00:18:16.860> essentially<00:18:17.250> receive<00:18:17.760> messages 00:18:18.230 --> 00:18:18.240 align:start position:0% you could essentially receive messages 00:18:18.240 --> 00:18:22.519 align:start position:0% you could essentially receive messages from<00:18:18.809> other<00:18:19.140> apps<00:18:19.620> that<00:18:20.130> support<00:18:20.450> you<00:18:21.529> friend 00:18:22.519 --> 00:18:22.529 align:start position:0% from other apps that support you friend 00:18:22.529 --> 00:18:23.840 align:start position:0% from other apps that support you friend so<00:18:22.919> you<00:18:23.010> can<00:18:23.130> have<00:18:23.250> your<00:18:23.370> own<00:18:23.490> the<00:18:23.669> same 00:18:23.840 --> 00:18:23.850 align:start position:0% so you can have your own the same 00:18:23.850 --> 00:18:26.299 align:start position:0% so you can have your own the same interface<00:18:24.270> like<00:18:24.659> what<00:18:24.899> in<00:18:25.289> theory<00:18:25.890> if<00:18:26.070> you 00:18:26.299 --> 00:18:26.309 align:start position:0% interface like what in theory if you 00:18:26.309 --> 00:18:28.130 align:start position:0% interface like what in theory if you know<00:18:26.490> Facebook<00:18:26.970> would<00:18:27.120> ever<00:18:27.270> adopt<00:18:27.720> it<00:18:27.899> you 00:18:28.130 --> 00:18:28.140 align:start position:0% know Facebook would ever adopt it you 00:18:28.140 --> 00:18:30.110 align:start position:0% know Facebook would ever adopt it you know<00:18:28.260> theory<00:18:28.799> like<00:18:29.340> whatsapp<00:18:29.820> can 00:18:30.110 --> 00:18:30.120 align:start position:0% know theory like whatsapp can 00:18:30.120 --> 00:18:32.060 align:start position:0% know theory like whatsapp can communicate<00:18:30.659> with<00:18:30.870> like<00:18:31.080> messenger<00:18:31.590> on<00:18:31.890> an 00:18:32.060 --> 00:18:32.070 align:start position:0% communicate with like messenger on an 00:18:32.070 --> 00:18:40.230 align:start position:0% communicate with like messenger on an offline<00:18:34.190> yes 00:18:40.230 --> 00:18:40.240 align:start position:0% 00:18:40.240 --> 00:18:45.120 align:start position:0% you<00:18:42.870> know<00:18:43.870> so<00:18:44.080> you<00:18:44.200> can<00:18:44.440> do<00:18:44.590> whatever<00:18:44.770> you<00:18:44.950> want 00:18:45.120 --> 00:18:45.130 align:start position:0% you know so you can do whatever you want 00:18:45.130 --> 00:18:46.950 align:start position:0% you know so you can do whatever you want to<00:18:45.250> the<00:18:45.340> payload<00:18:45.670> right<00:18:46.150> so<00:18:46.570> the<00:18:46.690> message 00:18:46.950 --> 00:18:46.960 align:start position:0% to the payload right so the message 00:18:46.960 --> 00:18:50.040 align:start position:0% to the payload right so the message itself<00:18:47.320> we<00:18:47.890> don't<00:18:48.100> define<00:18:48.610> how<00:18:48.970> do<00:18:49.510> we<00:18:49.630> don't 00:18:50.040 --> 00:18:50.050 align:start position:0% itself we don't define how do we don't 00:18:50.050 --> 00:18:51.660 align:start position:0% itself we don't define how do we don't we<00:18:50.290> don't<00:18:50.440> define<00:18:50.620> no<00:18:50.860> you<00:18:51.040> do<00:18:51.160> to<00:18:51.220> the<00:18:51.370> message 00:18:51.660 --> 00:18:51.670 align:start position:0% we don't define no you do to the message 00:18:51.670 --> 00:18:53.940 align:start position:0% we don't define no you do to the message but<00:18:51.940> you<00:18:52.150> can<00:18:52.450> encrypt<00:18:52.990> it<00:18:53.200> however<00:18:53.530> you<00:18:53.770> would 00:18:53.940 --> 00:18:53.950 align:start position:0% but you can encrypt it however you would 00:18:53.950 --> 00:18:57.210 align:start position:0% but you can encrypt it however you would choose<00:18:54.160> to<00:18:54.429> to<00:18:54.670> ensure<00:18:54.820> that<00:18:55.260> like<00:18:56.260> we<00:18:56.650> want<00:18:57.130> to 00:18:57.210 --> 00:18:57.220 align:start position:0% choose to to ensure that like we want to 00:18:57.220 --> 00:19:00.240 align:start position:0% choose to to ensure that like we want to be<00:18:57.340> as<00:18:57.490> less<00:18:58.450> intrusive<00:18:59.260> as<00:18:59.530> least<00:19:00.010> intrusive 00:19:00.240 --> 00:19:00.250 align:start position:0% be as less intrusive as least intrusive 00:19:00.250 --> 00:19:02.190 align:start position:0% be as less intrusive as least intrusive as<00:19:00.550> possible<00:19:01.000> so<00:19:01.450> you<00:19:01.510> can<00:19:01.690> do<00:19:01.780> whatever<00:19:01.929> one 00:19:02.190 --> 00:19:02.200 align:start position:0% as possible so you can do whatever one 00:19:02.200 --> 00:19:04.250 align:start position:0% as possible so you can do whatever one that<00:19:02.380> you<00:19:02.470> couldn't<00:19:02.770> repetition<00:19:03.340> easiest<00:19:03.700> is 00:19:04.250 --> 00:19:04.260 align:start position:0% that you couldn't repetition easiest is 00:19:04.260 --> 00:19:13.140 align:start position:0% that you couldn't repetition easiest is yes<00:19:05.260> just<00:19:05.790> how<00:19:06.790> do<00:19:06.850> you<00:19:11.580> so<00:19:12.580> now<00:19:12.970> you<00:19:13.030> believe 00:19:13.140 --> 00:19:13.150 align:start position:0% yes just how do you so now you believe 00:19:13.150 --> 00:19:14.910 align:start position:0% yes just how do you so now you believe we<00:19:13.540> have<00:19:13.720> this<00:19:13.870> thing<00:19:14.050> called<00:19:14.110> the<00:19:14.410> gossip 00:19:14.910 --> 00:19:14.920 align:start position:0% we have this thing called the gossip 00:19:14.920 --> 00:19:17.549 align:start position:0% we have this thing called the gossip right<00:19:15.070> now<00:19:15.250> which<00:19:15.640> is<00:19:15.880> doing<00:19:16.179> that<00:19:16.559> we're 00:19:17.549 --> 00:19:17.559 align:start position:0% right now which is doing that we're 00:19:17.559 --> 00:19:20.549 align:start position:0% right now which is doing that we're working<00:19:18.870> Dean's<00:19:19.870> been<00:19:20.110> doing<00:19:20.320> a<00:19:20.380> lot<00:19:20.530> of 00:19:20.549 --> 00:19:20.559 align:start position:0% working Dean's been doing a lot of 00:19:20.559 --> 00:19:25.860 align:start position:0% working Dean's been doing a lot of research<00:19:20.950> with<00:19:20.980> Oscar<00:19:22.230> Oscar<00:19:23.940> on<00:19:24.940> better 00:19:25.860 --> 00:19:25.870 align:start position:0% research with Oscar Oscar on better 00:19:25.870 --> 00:19:28.650 align:start position:0% research with Oscar Oscar on better routing<00:19:26.559> paths<00:19:26.770> so<00:19:27.429> that<00:19:27.580> we<00:19:27.730> can<00:19:27.910> do<00:19:28.090> more 00:19:28.650 --> 00:19:28.660 align:start position:0% routing paths so that we can do more 00:19:28.660 --> 00:19:30.480 align:start position:0% routing paths so that we can do more efficient<00:19:29.050> hops<00:19:29.260> and<00:19:29.530> I<00:19:29.679> actually<00:19:29.950> like<00:19:30.309> have 00:19:30.480 --> 00:19:30.490 align:start position:0% efficient hops and I actually like have 00:19:30.490 --> 00:19:32.190 align:start position:0% efficient hops and I actually like have less<00:19:30.730> hops<00:19:31.030> throughout<00:19:31.510> the<00:19:31.660> network<00:19:31.900> itself 00:19:32.190 --> 00:19:32.200 align:start position:0% less hops throughout the network itself 00:19:32.200 --> 00:19:37.640 align:start position:0% less hops throughout the network itself the<00:19:32.860> problem<00:19:33.100> though<00:19:33.400> is<00:19:34.030> that<00:19:36.270> typically 00:19:37.640 --> 00:19:37.650 align:start position:0% the problem though is that typically 00:19:37.650 --> 00:19:40.590 align:start position:0% the problem though is that typically what<00:19:38.650> you<00:19:38.890> would<00:19:39.220> in<00:19:39.820> a<00:19:39.880> festival<00:19:40.300> is<00:19:40.390> a<00:19:40.420> little 00:19:40.590 --> 00:19:40.600 align:start position:0% what you would in a festival is a little 00:19:40.600 --> 00:19:41.790 align:start position:0% what you would in a festival is a little bit<00:19:40.690> different<00:19:41.020> festivals<00:19:41.200> there's<00:19:41.679> not 00:19:41.790 --> 00:19:41.800 align:start position:0% bit different festivals there's not 00:19:41.800 --> 00:19:43.710 align:start position:0% bit different festivals there's not people<00:19:42.010> are<00:19:42.250> typically<00:19:42.610> standing<00:19:43.210> still<00:19:43.480> so 00:19:43.710 --> 00:19:43.720 align:start position:0% people are typically standing still so 00:19:43.720 --> 00:19:45.480 align:start position:0% people are typically standing still so we<00:19:44.230> can<00:19:44.350> actually<00:19:44.500> benefit<00:19:45.010> from<00:19:45.130> the<00:19:45.280> fact 00:19:45.480 --> 00:19:45.490 align:start position:0% we can actually benefit from the fact 00:19:45.490 --> 00:19:46.770 align:start position:0% we can actually benefit from the fact that<00:19:45.580> you<00:19:45.880> know<00:19:45.970> I<00:19:46.000> can<00:19:46.240> assume<00:19:46.510> that<00:19:46.540> the 00:19:46.770 --> 00:19:46.780 align:start position:0% that you know I can assume that the 00:19:46.780 --> 00:19:48.299 align:start position:0% that you know I can assume that the device<00:19:47.050> would<00:19:47.410> probably<00:19:47.710> last<00:19:47.920> more<00:19:48.130> than<00:19:48.160> a 00:19:48.299 --> 00:19:48.309 align:start position:0% device would probably last more than a 00:19:48.309 --> 00:19:50.640 align:start position:0% device would probably last more than a minute<00:19:48.400> and<00:19:48.850> roughly<00:19:49.630> you<00:19:50.110> know<00:19:50.200> like<00:19:50.350> a<00:19:50.380> 5 00:19:50.640 --> 00:19:50.650 align:start position:0% minute and roughly you know like a 5 00:19:50.650 --> 00:19:53.190 align:start position:0% minute and roughly you know like a 5 meter<00:19:50.890> radius<00:19:51.280> but<00:19:52.120> in<00:19:52.240> a<00:19:52.330> busier<00:19:52.690> crowd 00:19:53.190 --> 00:19:53.200 align:start position:0% meter radius but in a busier crowd 00:19:53.200 --> 00:19:54.930 align:start position:0% meter radius but in a busier crowd things<00:19:53.860> get<00:19:54.010> a<00:19:54.040> little<00:19:54.190> complicated<00:19:54.370> because 00:19:54.930 --> 00:19:54.940 align:start position:0% things get a little complicated because 00:19:54.940 --> 00:19:56.490 align:start position:0% things get a little complicated because what<00:19:55.540> ends<00:19:55.750> up<00:19:55.809> happening<00:19:55.870> is<00:19:56.320> you<00:19:56.380> have 00:19:56.490 --> 00:19:56.500 align:start position:0% what ends up happening is you have 00:19:56.500 --> 00:20:02.669 align:start position:0% what ends up happening is you have people<00:19:58.290> moving<00:19:59.290> from<00:20:00.809> like<00:20:01.809> you<00:20:02.200> can<00:20:02.380> assume 00:20:02.669 --> 00:20:02.679 align:start position:0% people moving from like you can assume 00:20:02.679 --> 00:20:04.230 align:start position:0% people moving from like you can assume like<00:20:02.890> we<00:20:03.010> only<00:20:03.220> have<00:20:03.429> connectivity<00:20:03.970> for<00:20:04.090> like 00:20:04.230 --> 00:20:04.240 align:start position:0% like we only have connectivity for like 00:20:04.240 --> 00:20:07.230 align:start position:0% like we only have connectivity for like maybe<00:20:04.480> 10<00:20:04.780> seconds<00:20:05.140> before<00:20:05.770> now<00:20:06.760> the<00:20:06.820> peer 00:20:07.230 --> 00:20:07.240 align:start position:0% maybe 10 seconds before now the peer 00:20:07.240 --> 00:20:09.180 align:start position:0% maybe 10 seconds before now the peer list<00:20:07.390> might<00:20:07.600> be<00:20:07.720> changing<00:20:08.050> and<00:20:08.200> drastically 00:20:09.180 --> 00:20:09.190 align:start position:0% list might be changing and drastically 00:20:09.190 --> 00:20:10.650 align:start position:0% list might be changing and drastically changing<00:20:09.580> so<00:20:09.730> we<00:20:09.850> have<00:20:09.970> to<00:20:10.059> find<00:20:10.240> as<00:20:10.390> a<00:20:10.420> way<00:20:10.600> to 00:20:10.650 --> 00:20:10.660 align:start position:0% changing so we have to find as a way to 00:20:10.660 --> 00:20:13.890 align:start position:0% changing so we have to find as a way to do<00:20:10.929> an<00:20:11.140> efficient<00:20:11.590> like<00:20:11.950> one<00:20:12.540> like<00:20:13.540> a<00:20:13.570> DHT 00:20:13.890 --> 00:20:13.900 align:start position:0% do an efficient like one like a DHT 00:20:13.900 --> 00:20:16.200 align:start position:0% do an efficient like one like a DHT wouldn't<00:20:14.290> work<00:20:14.380> here<00:20:14.559> because<00:20:14.740> like<00:20:15.100> it<00:20:16.090> would 00:20:16.200 --> 00:20:16.210 align:start position:0% wouldn't work here because like it would 00:20:16.210 --> 00:20:17.790 align:start position:0% wouldn't work here because like it would be<00:20:16.330> so<00:20:16.540> aggressively<00:20:17.020> updating<00:20:17.440> all<00:20:17.530> the<00:20:17.559> time 00:20:17.790 --> 00:20:17.800 align:start position:0% be so aggressively updating all the time 00:20:17.800 --> 00:20:19.200 align:start position:0% be so aggressively updating all the time that<00:20:18.370> doesn't<00:20:18.490> work<00:20:18.730> so<00:20:18.940> you<00:20:18.970> have<00:20:19.120> to 00:20:19.200 --> 00:20:19.210 align:start position:0% that doesn't work so you have to 00:20:19.210 --> 00:20:20.549 align:start position:0% that doesn't work so you have to maintain<00:20:19.330> like<00:20:19.660> a<00:20:19.720> really<00:20:19.929> close<00:20:20.110> peerless 00:20:20.549 --> 00:20:20.559 align:start position:0% maintain like a really close peerless 00:20:20.559 --> 00:20:23.940 align:start position:0% maintain like a really close peerless and<00:20:20.770> finally<00:20:21.309> better<00:20:21.520> running<00:20:21.760> hats<00:20:22.950> that's 00:20:23.940 --> 00:20:23.950 align:start position:0% and finally better running hats that's 00:20:23.950 --> 00:20:25.740 align:start position:0% and finally better running hats that's what<00:20:24.100> I'm<00:20:24.190> working<00:20:24.340> on<00:20:24.550> but<00:20:24.910> if<00:20:25.000> you<00:20:25.120> have<00:20:25.630> to 00:20:25.740 --> 00:20:25.750 align:start position:0% what I'm working on but if you have to 00:20:25.750 --> 00:20:28.500 align:start position:0% what I'm working on but if you have to stop<00:20:25.960> see<00:20:26.140> yeah<00:20:26.650> that's<00:20:26.950> right<00:20:27.370> like<00:20:27.640> there's 00:20:28.500 --> 00:20:28.510 align:start position:0% stop see yeah that's right like there's 00:20:28.510 --> 00:20:30.890 align:start position:0% stop see yeah that's right like there's only<00:20:28.600> one<00:20:29.020> guy 00:20:30.890 --> 00:20:30.900 align:start position:0% only one guy 00:20:30.900 --> 00:20:35.100 align:start position:0% only one guy access<00:20:31.900> to<00:20:32.430> yep<00:20:33.460> otherwise<00:20:34.210> how<00:20:34.630> do<00:20:34.690> I<00:20:34.840> know 00:20:35.100 --> 00:20:35.110 align:start position:0% access to yep otherwise how do I know 00:20:35.110 --> 00:20:38.250 align:start position:0% access to yep otherwise how do I know the<00:20:35.320> roots<00:20:35.559> gets<00:20:35.950> him<00:20:36.370> like<00:20:37.240> I<00:20:37.510> look<00:20:38.110> for 00:20:38.250 --> 00:20:38.260 align:start position:0% the roots gets him like I look for 00:20:38.260 --> 00:20:40.350 align:start position:0% the roots gets him like I look for customized<00:20:38.770> in<00:20:39.070> magnets<00:20:39.670> you<00:20:39.820> don't<00:20:40.030> know 00:20:40.350 --> 00:20:40.360 align:start position:0% customized in magnets you don't know 00:20:40.360 --> 00:20:42.510 align:start position:0% customized in magnets you don't know roots<00:20:40.930> yeah<00:20:41.380> that's<00:20:41.920> a<00:20:42.010> penalty 00:20:42.510 --> 00:20:42.520 align:start position:0% roots yeah that's a penalty 00:20:42.520 --> 00:20:44.549 align:start position:0% roots yeah that's a penalty so<00:20:42.670> measurements<00:20:43.330> have<00:20:43.600> the<00:20:43.809> efficiency<00:20:44.410> that 00:20:44.549 --> 00:20:44.559 align:start position:0% so measurements have the efficiency that 00:20:44.559 --> 00:20:47.040 align:start position:0% so measurements have the efficiency that you<00:20:44.680> can<00:20:44.890> pre<00:20:45.160> calculate<00:20:45.640> roofs<00:20:45.880> and<00:20:46.510> magnets 00:20:47.040 --> 00:20:47.050 align:start position:0% you can pre calculate roofs and magnets 00:20:47.050 --> 00:20:49.410 align:start position:0% you can pre calculate roofs and magnets because<00:20:47.350> we<00:20:47.470> assume<00:20:47.830> very<00:20:48.790> short 00:20:49.410 --> 00:20:49.420 align:start position:0% because we assume very short 00:20:49.420 --> 00:20:53.250 align:start position:0% because we assume very short liveness<00:20:49.720> of<00:20:50.880> things<00:20:51.880> or<00:20:52.240> very<00:20:52.990> short 00:20:53.250 --> 00:20:53.260 align:start position:0% liveness of things or very short 00:20:53.260 --> 00:20:54.890 align:start position:0% liveness of things or very short lightness<00:20:53.710> of<00:20:53.830> the<00:20:53.980> peers<00:20:54.280> we<00:20:54.550> can 00:20:54.890 --> 00:20:54.900 align:start position:0% lightness of the peers we can 00:20:54.900 --> 00:20:57.540 align:start position:0% lightness of the peers we can predetermine<00:20:55.900> roofs<00:20:56.440> so<00:20:56.980> there<00:20:57.130> are<00:20:57.190> certain 00:20:57.540 --> 00:20:57.550 align:start position:0% predetermine roofs so there are certain 00:20:57.550 --> 00:21:00.780 align:start position:0% predetermine roofs so there are certain ways<00:20:57.730> to<00:20:58.260> for<00:20:59.260> every<00:20:59.590> health<00:20:59.860> pick<00:21:00.370> the<00:21:00.580> next 00:21:00.780 --> 00:21:00.790 align:start position:0% ways to for every health pick the next 00:21:00.790 --> 00:21:02.790 align:start position:0% ways to for every health pick the next best<00:21:01.150> by<00:21:01.570> acquiring<00:21:01.990> their<00:21:02.290> peers<00:21:02.590> right 00:21:02.790 --> 00:21:02.800 align:start position:0% best by acquiring their peers right 00:21:02.800 --> 00:21:06.360 align:start position:0% best by acquiring their peers right before<00:21:03.160> the<00:21:03.250> hall<00:21:03.400> but<00:21:03.910> like<00:21:04.120> if<00:21:05.220> there<00:21:06.220> is 00:21:06.360 --> 00:21:06.370 align:start position:0% before the hall but like if there is 00:21:06.370 --> 00:21:09.750 align:start position:0% before the hall but like if there is like<00:21:06.610> 50<00:21:07.179> people<00:21:07.390> between<00:21:07.929> you<00:21:08.530> and<00:21:09.010> the 00:21:09.750 --> 00:21:09.760 align:start position:0% like 50 people between you and the 00:21:09.760 --> 00:21:13.950 align:start position:0% like 50 people between you and the internet<00:21:10.210> you<00:21:10.420> can<00:21:10.679> do<00:21:11.679> that<00:21:12.030> right<00:21:13.030> so<00:21:13.270> I<00:21:13.300> cast 00:21:13.950 --> 00:21:13.960 align:start position:0% internet you can do that right so I cast 00:21:13.960 --> 00:21:21.780 align:start position:0% internet you can do that right so I cast like<00:21:14.230> potentially<00:21:14.770> to<00:21:15.809> like<00:21:16.809> a<00:21:17.610> list<00:21:20.790> that's 00:21:21.780 --> 00:21:21.790 align:start position:0% like potentially to like a list that's 00:21:21.790 --> 00:21:24.180 align:start position:0% like potentially to like a list that's that's<00:21:22.210> how<00:21:22.390> it<00:21:22.600> works<00:21:22.929> in<00:21:23.140> the<00:21:23.260> worst<00:21:23.530> case<00:21:23.830> in 00:21:24.180 --> 00:21:24.190 align:start position:0% that's how it works in the worst case in 00:21:24.190 --> 00:21:27.270 align:start position:0% that's how it works in the worst case in the<00:21:24.880> best<00:21:25.120> case<00:21:25.480> what<00:21:26.260> we<00:21:26.440> have<00:21:26.470> right<00:21:26.830> now<00:21:26.890> is 00:21:27.270 --> 00:21:27.280 align:start position:0% the best case what we have right now is 00:21:27.280 --> 00:21:30.180 align:start position:0% the best case what we have right now is that<00:21:27.809> you<00:21:28.809> try<00:21:29.050> to<00:21:29.080> first<00:21:29.440> linked<00:21:29.890> to<00:21:30.070> the 00:21:30.180 --> 00:21:30.190 align:start position:0% that you try to first linked to the 00:21:30.190 --> 00:21:33.330 align:start position:0% that you try to first linked to the peers<00:21:30.490> who<00:21:30.670> have<00:21:31.000> a<00:21:31.590> specific<00:21:32.590> service<00:21:32.890> that 00:21:33.330 --> 00:21:33.340 align:start position:0% peers who have a specific service that 00:21:33.340 --> 00:21:36.360 align:start position:0% peers who have a specific service that you<00:21:33.490> need<00:21:33.520> and<00:21:34.090> then<00:21:34.630> hop<00:21:34.960> further<00:21:35.260> on<00:21:35.410> like 00:21:36.360 --> 00:21:36.370 align:start position:0% you need and then hop further on like 00:21:36.370 --> 00:21:44.150 align:start position:0% you need and then hop further on like the<00:21:36.550> worst<00:21:36.760> cases<00:21:37.030> is<00:21:37.800> having<00:21:38.800> thing<00:21:40.530> yeah 00:21:44.150 --> 00:21:44.160 align:start position:0% 00:21:44.160 --> 00:21:48.050 align:start position:0% yeah<00:21:45.860> validation<00:21:46.860> every<00:21:47.100> message<00:21:47.370> is<00:21:47.460> like<00:21:47.730> is 00:21:48.050 --> 00:21:48.060 align:start position:0% yeah validation every message is like is 00:21:48.060 --> 00:21:50.480 align:start position:0% yeah validation every message is like is there<00:21:48.240> a<00:21:48.270> pattern<00:21:48.840> no<00:21:49.200> they<00:21:49.440> go<00:21:49.560> sale<00:21:49.890> let's 00:21:50.480 --> 00:21:50.490 align:start position:0% there a pattern no they go sale let's 00:21:50.490 --> 00:21:53.950 align:start position:0% there a pattern no they go sale let's say<00:21:50.610> I<00:21:50.640> realized<00:21:51.540> somebody<00:21:51.780> else's<00:21:52.080> message 00:21:53.950 --> 00:21:53.960 align:start position:0% say I realized somebody else's message 00:21:53.960 --> 00:21:58.430 align:start position:0% say I realized somebody else's message especially<00:21:54.960> on<00:21:55.470> a<00:21:55.500> stove<00:21:55.770> yeah<00:21:56.580> so<00:21:57.440> we've 00:21:58.430 --> 00:21:58.440 align:start position:0% especially on a stove yeah so we've 00:21:58.440 --> 00:22:01.730 align:start position:0% especially on a stove yeah so we've talked<00:21:58.710> about<00:21:58.740> the<00:21:59.070> idea<00:21:59.400> of<00:22:00.290> kind<00:22:01.290> of<00:22:01.410> like<00:22:01.590> an 00:22:01.730 --> 00:22:01.740 align:start position:0% talked about the idea of kind of like an 00:22:01.740 --> 00:22:04.370 align:start position:0% talked about the idea of kind of like an act<00:22:02.010> where<00:22:02.460> you<00:22:02.490> know<00:22:02.970> once<00:22:03.210> we've<00:22:03.450> seen<00:22:03.930> it<00:22:04.080> we 00:22:04.370 --> 00:22:04.380 align:start position:0% act where you know once we've seen it we 00:22:04.380 --> 00:22:06.800 align:start position:0% act where you know once we've seen it we acknowledge<00:22:05.070> we<00:22:05.340> like<00:22:05.700> to<00:22:05.820> catch<00:22:06.270> of<00:22:06.510> it<00:22:06.600> so 00:22:06.800 --> 00:22:06.810 align:start position:0% acknowledge we like to catch of it so 00:22:06.810 --> 00:22:09.080 align:start position:0% acknowledge we like to catch of it so like<00:22:06.960> we're<00:22:07.080> not<00:22:07.200> gonna<00:22:07.350> like<00:22:07.560> push<00:22:07.770> this<00:22:08.090> if 00:22:09.080 --> 00:22:09.090 align:start position:0% like we're not gonna like push this if 00:22:09.090 --> 00:22:10.220 align:start position:0% like we're not gonna like push this if we<00:22:09.240> receive<00:22:09.540> it<00:22:09.660> one<00:22:09.750> more<00:22:09.870> time<00:22:10.020> we're<00:22:10.170> gonna 00:22:10.220 --> 00:22:10.230 align:start position:0% we receive it one more time we're gonna 00:22:10.230 --> 00:22:12.980 align:start position:0% we receive it one more time we're gonna like<00:22:10.470> ignore<00:22:10.920> it<00:22:11.010> filter<00:22:11.510> problem<00:22:12.510> being<00:22:12.690> is 00:22:12.980 --> 00:22:12.990 align:start position:0% like ignore it filter problem being is 00:22:12.990 --> 00:22:15.650 align:start position:0% like ignore it filter problem being is some<00:22:13.320> what<00:22:14.040> that<00:22:14.220> does<00:22:14.490> is<00:22:14.700> if<00:22:14.970> the<00:22:15.300> context 00:22:15.650 --> 00:22:15.660 align:start position:0% some what that does is if the context 00:22:15.660 --> 00:22:18.110 align:start position:0% some what that does is if the context that<00:22:15.870> if<00:22:16.140> you're<00:22:16.350> local<00:22:16.710> if<00:22:17.640> the<00:22:17.790> one<00:22:17.970> if 00:22:18.110 --> 00:22:18.120 align:start position:0% that if you're local if the one if 00:22:18.120 --> 00:22:19.790 align:start position:0% that if you're local if the one if you're<00:22:18.360> man<00:22:18.540> that<00:22:18.720> disconnects<00:22:19.470> from<00:22:19.530> like<00:22:19.770> a 00:22:19.790 --> 00:22:19.800 align:start position:0% you're man that disconnects from like a 00:22:19.800 --> 00:22:21.950 align:start position:0% you're man that disconnects from like a larger<00:22:20.250> group<00:22:20.490> you<00:22:21.120> end<00:22:21.300> up<00:22:21.450> pushing<00:22:21.720> that 00:22:21.950 --> 00:22:21.960 align:start position:0% larger group you end up pushing that 00:22:21.960 --> 00:22:23.930 align:start position:0% larger group you end up pushing that really<00:22:22.200> quickly<00:22:22.440> and<00:22:22.800> then<00:22:23.160> the<00:22:23.490> message<00:22:23.610> gets 00:22:23.930 --> 00:22:23.940 align:start position:0% really quickly and then the message gets 00:22:23.940 --> 00:22:24.410 align:start position:0% really quickly and then the message gets dropped 00:22:24.410 --> 00:22:24.420 align:start position:0% dropped 00:22:24.420 --> 00:22:27.260 align:start position:0% dropped so<00:22:25.280> we've<00:22:26.280> played<00:22:26.490> with<00:22:26.580> the<00:22:26.700> idea<00:22:26.940> of<00:22:27.000> kind<00:22:27.180> of 00:22:27.260 --> 00:22:27.270 align:start position:0% so we've played with the idea of kind of 00:22:27.270 --> 00:22:28.760 align:start position:0% so we've played with the idea of kind of like<00:22:27.390> expiry<00:22:27.780> times<00:22:28.080> and<00:22:28.320> stuff<00:22:28.440> like<00:22:28.560> that 00:22:28.760 --> 00:22:28.770 align:start position:0% like expiry times and stuff like that 00:22:28.770 --> 00:22:30.770 align:start position:0% like expiry times and stuff like that but<00:22:29.040> it's<00:22:29.190> still<00:22:29.430> kind<00:22:29.940> of<00:22:29.970> a<00:22:30.060> big<00:22:30.240> open 00:22:30.770 --> 00:22:30.780 align:start position:0% but it's still kind of a big open 00:22:30.780 --> 00:22:32.810 align:start position:0% but it's still kind of a big open question<00:22:30.990> until<00:22:31.740> we<00:22:31.920> can<00:22:32.100> actually<00:22:32.250> deploy 00:22:32.810 --> 00:22:32.820 align:start position:0% question until we can actually deploy 00:22:32.820 --> 00:22:35.630 align:start position:0% question until we can actually deploy this<00:22:33.470> in<00:22:34.470> a<00:22:34.650> bit<00:22:34.800> of<00:22:34.830> a<00:22:34.950> blur<00:22:35.100> and<00:22:35.310> a<00:22:35.370> larger 00:22:35.630 --> 00:22:35.640 align:start position:0% this in a bit of a blur and a larger 00:22:35.640 --> 00:22:37.220 align:start position:0% this in a bit of a blur and a larger scale<00:22:35.880> to<00:22:35.910> actually<00:22:36.270> like<00:22:36.390> kind<00:22:36.600> of<00:22:36.720> see<00:22:36.960> like 00:22:37.220 --> 00:22:37.230 align:start position:0% scale to actually like kind of see like 00:22:37.230 --> 00:22:39.620 align:start position:0% scale to actually like kind of see like how<00:22:37.770> long<00:22:38.010> does<00:22:38.190> the<00:22:38.310> message<00:22:38.460> survive<00:22:38.940> you 00:22:39.620 --> 00:22:39.630 align:start position:0% how long does the message survive you 00:22:39.630 --> 00:22:41.000 align:start position:0% how long does the message survive you know<00:22:39.720> until<00:22:40.140> it<00:22:40.260> can<00:22:40.350> actually<00:22:40.530> get<00:22:40.740> to<00:22:40.890> its 00:22:41.000 --> 00:22:41.010 align:start position:0% know until it can actually get to its 00:22:41.010 --> 00:22:43.940 align:start position:0% know until it can actually get to its end<00:22:41.160> user<00:22:42.260> one<00:22:43.260> of<00:22:43.350> the<00:22:43.440> problems<00:22:43.770> we've<00:22:43.920> had 00:22:43.940 --> 00:22:43.950 align:start position:0% end user one of the problems we've had 00:22:43.950 --> 00:22:46.310 align:start position:0% end user one of the problems we've had right<00:22:44.220> now<00:22:44.430> as<00:22:44.580> well<00:22:44.760> as<00:22:44.910> testing<00:22:45.600> anything 00:22:46.310 --> 00:22:46.320 align:start position:0% right now as well as testing anything 00:22:46.320 --> 00:22:50.210 align:start position:0% right now as well as testing anything Bluetooth<00:22:46.770> is<00:22:47.040> Pichet<00:22:48.380> they<00:22:49.380> will<00:22:49.530> be<00:22:49.680> optimal 00:22:50.210 --> 00:22:50.220 align:start position:0% Bluetooth is Pichet they will be optimal 00:22:50.220 --> 00:22:51.440 align:start position:0% Bluetooth is Pichet they will be optimal if<00:22:50.370> we<00:22:50.490> could<00:22:50.670> like<00:22:50.820> use<00:22:51.000> something<00:22:51.330> like 00:22:51.440 --> 00:22:51.450 align:start position:0% if we could like use something like 00:22:51.450 --> 00:22:53.920 align:start position:0% if we could like use something like white<00:22:51.630> blockers<00:22:52.140> spin<00:22:52.410> up<00:22:52.560> all<00:22:52.800> our<00:22:53.010> notes<00:22:53.220> and 00:22:53.920 --> 00:22:53.930 align:start position:0% white blockers spin up all our notes and 00:22:53.930 --> 00:22:56.120 align:start position:0% white blockers spin up all our notes and run<00:22:54.930> it<00:22:55.080> but<00:22:55.320> that's<00:22:55.530> close<00:22:55.860> to<00:22:55.890> impossible 00:22:56.120 --> 00:22:56.130 align:start position:0% run it but that's close to impossible 00:22:56.130 --> 00:22:59.530 align:start position:0% run it but that's close to impossible because<00:22:56.730> of<00:22:56.760> how<00:22:56.970> Bluetooth<00:22:57.360> works<00:22:57.650> Bluetooth 00:22:59.530 --> 00:22:59.540 align:start position:0% because of how Bluetooth works Bluetooth 00:22:59.540 --> 00:23:02.390 align:start position:0% because of how Bluetooth works Bluetooth the<00:23:00.540> way<00:23:00.720> it<00:23:00.960> works<00:23:01.200> is<00:23:01.470> like<00:23:01.500> it's<00:23:02.040> driver 00:23:02.390 --> 00:23:02.400 align:start position:0% the way it works is like it's driver 00:23:02.400 --> 00:23:04.190 align:start position:0% the way it works is like it's driver dependent<00:23:03.060> it's<00:23:03.270> operating<00:23:03.840> system 00:23:04.190 --> 00:23:04.200 align:start position:0% dependent it's operating system 00:23:04.200 --> 00:23:05.600 align:start position:0% dependent it's operating system dependent<00:23:04.680> and<00:23:04.890> then<00:23:04.980> those<00:23:05.130> operating 00:23:05.600 --> 00:23:05.610 align:start position:0% dependent and then those operating 00:23:05.610 --> 00:23:08.090 align:start position:0% dependent and then those operating systems<00:23:05.640> implement<00:23:06.450> different<00:23:06.630> api's<00:23:07.170> and<00:23:07.500> so 00:23:08.090 --> 00:23:08.100 align:start position:0% systems implement different api's and so 00:23:08.100 --> 00:23:12.020 align:start position:0% systems implement different api's and so like<00:23:08.280> our<00:23:08.820> Mac<00:23:10.610> implementation<00:23:11.610> would<00:23:11.850> be 00:23:12.020 --> 00:23:12.030 align:start position:0% like our Mac implementation would be 00:23:12.030 --> 00:23:13.370 align:start position:0% like our Mac implementation would be really<00:23:12.300> nice<00:23:12.420> if<00:23:12.660> we<00:23:12.780> could<00:23:12.900> just<00:23:12.960> spin<00:23:13.350> up 00:23:13.370 --> 00:23:13.380 align:start position:0% really nice if we could just spin up 00:23:13.380 --> 00:23:15.530 align:start position:0% really nice if we could just spin up fake<00:23:13.770> Macs<00:23:14.100> and<00:23:14.430> test<00:23:14.700> it<00:23:14.880> but<00:23:15.060> we<00:23:15.150> can't<00:23:15.390> do 00:23:15.530 --> 00:23:15.540 align:start position:0% fake Macs and test it but we can't do 00:23:15.540 --> 00:23:17.270 align:start position:0% fake Macs and test it but we can't do that<00:23:15.720> because<00:23:15.960> us<00:23:16.440> so<00:23:16.590> you<00:23:16.650> can't<00:23:16.980> spit<00:23:17.250> out 00:23:17.270 --> 00:23:17.280 align:start position:0% that because us so you can't spit out 00:23:17.280 --> 00:23:19.160 align:start position:0% that because us so you can't spit out magnet<00:23:17.790> VMs<00:23:18.210> because<00:23:18.750> it<00:23:18.870> doesn't<00:23:19.110> exist 00:23:19.160 --> 00:23:19.170 align:start position:0% magnet VMs because it doesn't exist 00:23:19.170 --> 00:23:21.380 align:start position:0% magnet VMs because it doesn't exist unless<00:23:19.530> you<00:23:19.680> spend<00:23:20.010> on<00:23:20.100> packing<00:23:20.490> Tosh's<00:23:20.880> which 00:23:21.380 --> 00:23:21.390 align:start position:0% unless you spend on packing Tosh's which 00:23:21.390 --> 00:23:22.700 align:start position:0% unless you spend on packing Tosh's which then<00:23:21.600> usually<00:23:21.960> don't<00:23:22.140> have<00:23:22.350> the<00:23:22.500> proper 00:23:22.700 --> 00:23:22.710 align:start position:0% then usually don't have the proper 00:23:22.710 --> 00:23:25.880 align:start position:0% then usually don't have the proper Bluetooth<00:23:23.160> drivers<00:23:23.670> so<00:23:24.510> the<00:23:24.990> entire<00:23:25.320> testing 00:23:25.880 --> 00:23:25.890 align:start position:0% Bluetooth drivers so the entire testing 00:23:25.890 --> 00:23:27.590 align:start position:0% Bluetooth drivers so the entire testing of<00:23:26.010> this<00:23:26.160> requires<00:23:26.730> us<00:23:26.820> to<00:23:26.970> actually<00:23:27.420> get 00:23:27.590 --> 00:23:27.600 align:start position:0% of this requires us to actually get 00:23:27.600 --> 00:23:29.150 align:start position:0% of this requires us to actually get together<00:23:27.780> physically<00:23:28.500> and<00:23:28.620> test<00:23:28.830> it<00:23:29.010> which 00:23:29.150 --> 00:23:29.160 align:start position:0% together physically and test it which 00:23:29.160 --> 00:23:31.130 align:start position:0% together physically and test it which has<00:23:29.280> been<00:23:29.520> kind<00:23:30.150> of<00:23:30.210> hard<00:23:30.360> considering<00:23:30.810> daily 00:23:31.130 --> 00:23:31.140 align:start position:0% has been kind of hard considering daily 00:23:31.140 --> 00:23:35.350 align:start position:0% has been kind of hard considering daily living 00:23:35.350 --> 00:23:35.360 align:start position:0% 00:23:35.360 --> 00:23:38.570 align:start position:0% yeah<00:23:36.360> we're<00:23:37.289> gonna<00:23:37.650> work<00:23:38.100> on<00:23:38.309> something 00:23:38.570 --> 00:23:38.580 align:start position:0% yeah we're gonna work on something 00:23:38.580 --> 00:23:40.279 align:start position:0% yeah we're gonna work on something better<00:23:38.850> yeah<00:23:39.390> if<00:23:39.480> you<00:23:39.570> have<00:23:39.690> any<00:23:39.720> mac<00:23:40.020> books 00:23:40.279 --> 00:23:40.289 align:start position:0% better yeah if you have any mac books 00:23:40.289 --> 00:23:44.049 align:start position:0% better yeah if you have any mac books you<00:23:40.470> will<00:23:40.590> donate<00:23:41.190> we'll<00:23:41.429> take<00:23:41.610> them 00:23:44.049 --> 00:23:44.059 align:start position:0% 00:23:44.059 --> 00:23:46.520 align:start position:0% so<00:23:45.059> here<00:23:45.360> what<00:23:45.510> happened<00:23:46.080> is<00:23:46.200> we're<00:23:46.380> both 00:23:46.520 --> 00:23:46.530 align:start position:0% so here what happened is we're both 00:23:46.530 --> 00:23:48.159 align:start position:0% so here what happened is we're both running<00:23:46.770> a<00:23:47.010> real<00:23:47.220> heir<00:23:47.370> with<00:23:47.580> just<00:23:47.820> a<00:23:47.910> basic 00:23:48.159 --> 00:23:48.169 align:start position:0% running a real heir with just a basic 00:23:48.169 --> 00:23:51.919 align:start position:0% running a real heir with just a basic service<00:23:49.169> that<00:23:49.830> implements<00:23:50.549> just<00:23:51.510> normal 00:23:51.919 --> 00:23:51.929 align:start position:0% service that implements just normal 00:23:51.929 --> 00:23:54.710 align:start position:0% service that implements just normal messaging<00:23:52.440> between<00:23:52.559> Eric<00:23:53.190> and<00:23:53.280> I<00:23:53.600> it's<00:23:54.600> a 00:23:54.710 --> 00:23:54.720 align:start position:0% messaging between Eric and I it's a 00:23:54.720 --> 00:23:56.810 align:start position:0% messaging between Eric and I it's a essentially<00:23:55.410> it's<00:23:55.530> a<00:23:55.559> terminal<00:23:56.010> chat<00:23:56.429> up<00:23:56.580> that 00:23:56.810 --> 00:23:56.820 align:start position:0% essentially it's a terminal chat up that 00:23:56.820 --> 00:24:00.409 align:start position:0% essentially it's a terminal chat up that just<00:23:56.940> spends<00:23:57.720> a<00:23:57.900> main<00:23:58.169> channel<00:23:58.669> its<00:23:59.669> cents<00:24:00.240> to 00:24:00.409 --> 00:24:00.419 align:start position:0% just spends a main channel its cents to 00:24:00.419 --> 00:24:03.560 align:start position:0% just spends a main channel its cents to a<00:24:00.450> service<00:24:00.840> directly<00:24:01.289> so<00:24:01.679> that<00:24:02.390> anyone<00:24:03.390> who 00:24:03.560 --> 00:24:03.570 align:start position:0% a service directly so that anyone who 00:24:03.570 --> 00:24:05.570 align:start position:0% a service directly so that anyone who would<00:24:03.690> be<00:24:03.720> connected<00:24:04.260> to<00:24:04.590> this<00:24:04.710> channel<00:24:05.190> would 00:24:05.570 --> 00:24:05.580 align:start position:0% would be connected to this channel would 00:24:05.580 --> 00:24:07.880 align:start position:0% would be connected to this channel would now<00:24:05.820> just<00:24:06.090> be<00:24:06.240> receiving<00:24:06.720> these<00:24:06.840> messages<00:24:06.900> and 00:24:07.880 --> 00:24:07.890 align:start position:0% now just be receiving these messages and 00:24:07.890 --> 00:24:11.409 align:start position:0% now just be receiving these messages and our<00:24:08.010> Pro<00:24:08.159> Cemetery<00:24:08.700> which<00:24:09.120> is<00:24:09.240> pretty<00:24:09.750> cool 00:24:11.409 --> 00:24:11.419 align:start position:0% our Pro Cemetery which is pretty cool 00:24:11.419 --> 00:24:13.549 align:start position:0% our Pro Cemetery which is pretty cool next<00:24:12.419> thing<00:24:12.690> I'm<00:24:12.780> going<00:24:12.870> to<00:24:12.960> do<00:24:13.110> is<00:24:13.380> I'm<00:24:13.530> going 00:24:13.549 --> 00:24:13.559 align:start position:0% next thing I'm going to do is I'm going 00:24:13.559 --> 00:24:15.919 align:start position:0% next thing I'm going to do is I'm going to<00:24:13.710> show<00:24:13.950> you<00:24:14.010> the<00:24:14.250> code<00:24:14.490> does<00:24:15.030> some<00:24:15.690> of<00:24:15.720> this 00:24:15.919 --> 00:24:15.929 align:start position:0% to show you the code does some of this 00:24:15.929 --> 00:24:28.490 align:start position:0% to show you the code does some of this stuff<00:24:16.230> this<00:24:16.950> pump<00:24:17.250> is<00:24:17.370> also<00:24:17.640> too<00:24:17.700> small 00:24:28.490 --> 00:24:28.500 align:start position:0% 00:24:28.500 --> 00:24:47.370 align:start position:0% you<00:24:29.500> guys<00:24:29.650> know<00:24:29.830> how<00:24:30.010> to<00:24:30.040> use<00:24:30.250> your<00:24:46.380> any 00:24:47.370 --> 00:24:47.380 align:start position:0% you guys know how to use your any 00:24:47.380 --> 00:24:51.570 align:start position:0% you guys know how to use your any questions<00:24:47.860> while<00:24:48.990> dc2<00:24:49.990> message<00:24:50.320> replay<00:24:50.680> they 00:24:51.570 --> 00:24:51.580 align:start position:0% questions while dc2 message replay they 00:24:51.580 --> 00:24:53.390 align:start position:0% questions while dc2 message replay they give<00:24:51.730> the<00:24:51.910> prettiest<00:24:52.450> partitions<00:24:52.990> and<00:24:53.140> then 00:24:53.390 --> 00:24:53.400 align:start position:0% give the prettiest partitions and then 00:24:53.400 --> 00:24:55.770 align:start position:0% give the prettiest partitions and then reconstructed<00:24:54.400> you<00:24:54.520> replay<00:24:54.880> messages<00:24:55.450> yes 00:24:55.770 --> 00:24:55.780 align:start position:0% reconstructed you replay messages yes 00:24:55.780 --> 00:24:58.650 align:start position:0% reconstructed you replay messages yes message<00:24:56.500> to<00:24:56.680> retransmission<00:24:57.400> by<00:24:57.550> yes<00:24:58.060> if<00:24:58.240> you 00:24:58.650 --> 00:24:58.660 align:start position:0% message to retransmission by yes if you 00:24:58.660 --> 00:25:03.120 align:start position:0% message to retransmission by yes if you like<00:24:59.910> exactly<00:25:00.910> yeah<00:25:01.180> so<00:25:01.810> right<00:25:02.380> now<00:25:02.560> what 00:25:03.120 --> 00:25:03.130 align:start position:0% like exactly yeah so right now what 00:25:03.130 --> 00:25:05.520 align:start position:0% like exactly yeah so right now what happens<00:25:03.520> is<00:25:03.700> a<00:25:03.880> message<00:25:04.240> will<00:25:04.390> walk<00:25:04.600> around<00:25:04.990> in 00:25:05.520 --> 00:25:05.530 align:start position:0% happens is a message will walk around in 00:25:05.530 --> 00:25:09.210 align:start position:0% happens is a message will walk around in a<00:25:06.370> network<00:25:06.760> for<00:25:07.360> quite<00:25:07.570> a<00:25:07.690> time<00:25:08.020> until<00:25:08.530> you 00:25:09.210 --> 00:25:09.220 align:start position:0% a network for quite a time until you 00:25:09.220 --> 00:25:11.220 align:start position:0% a network for quite a time until you know<00:25:09.370> it's<00:25:09.520> no<00:25:09.670> longer<00:25:09.940> choose<00:25:10.120> to<00:25:10.450> retransmit 00:25:11.220 --> 00:25:11.230 align:start position:0% know it's no longer choose to retransmit 00:25:11.230 --> 00:25:13.970 align:start position:0% know it's no longer choose to retransmit it<00:25:11.530> it's<00:25:12.220> a<00:25:12.370> passive<00:25:12.940> it's<00:25:13.060> a<00:25:13.120> very<00:25:13.390> naive 00:25:13.970 --> 00:25:13.980 align:start position:0% it it's a passive it's a very naive 00:25:13.980 --> 00:25:17.040 align:start position:0% it it's a passive it's a very naive sending<00:25:14.980> algorithm<00:25:15.490> which<00:25:16.270> I<00:25:16.480> will<00:25:16.660> show<00:25:16.870> you 00:25:17.040 --> 00:25:17.050 align:start position:0% sending algorithm which I will show you 00:25:17.050 --> 00:25:22.770 align:start position:0% sending algorithm which I will show you here<00:25:17.580> here<00:25:18.580> we<00:25:18.760> go<00:25:19.000> that's<00:25:19.780> some<00:25:21.360> so<00:25:22.360> this<00:25:22.630> is 00:25:22.770 --> 00:25:22.780 align:start position:0% here here we go that's some so this is 00:25:22.780 --> 00:25:25.380 align:start position:0% here here we go that's some so this is essentially<00:25:23.170> the<00:25:23.410> same<00:25:23.620> function<00:25:24.150> and<00:25:25.150> what 00:25:25.380 --> 00:25:25.390 align:start position:0% essentially the same function and what 00:25:25.390 --> 00:25:28.560 align:start position:0% essentially the same function and what happens<00:25:25.840> in<00:25:26.110> the<00:25:26.380> first<00:25:26.650> check<00:25:27.550> is<00:25:27.820> we<00:25:28.180> ensure 00:25:28.560 --> 00:25:28.570 align:start position:0% happens in the first check is we ensure 00:25:28.570 --> 00:25:30.360 align:start position:0% happens in the first check is we ensure that<00:25:28.750> the<00:25:28.900> message<00:25:29.080> I<00:25:29.380> there<00:25:29.710> has<00:25:29.860> a<00:25:29.890> recipient 00:25:30.360 --> 00:25:30.370 align:start position:0% that the message I there has a recipient 00:25:30.370 --> 00:25:35.040 align:start position:0% that the message I there has a recipient which<00:25:30.820> is<00:25:31.030> a<00:25:31.360> device<00:25:31.930> or<00:25:33.120> a<00:25:34.120> service<00:25:34.630> which<00:25:34.870> is 00:25:35.040 --> 00:25:35.050 align:start position:0% which is a device or a service which is 00:25:35.050 --> 00:25:37.860 align:start position:0% which is a device or a service which is like<00:25:35.260> a<00:25:35.560> characteristic<00:25:36.550> like<00:25:36.700> if<00:25:37.570> you're<00:25:37.780> in 00:25:37.860 --> 00:25:37.870 align:start position:0% like a characteristic like if you're in 00:25:37.870 --> 00:25:40.800 align:start position:0% like a characteristic like if you're in transactions<00:25:38.440> or<00:25:38.560> whatever<00:25:39.210> the<00:25:40.210> recipient 00:25:40.800 --> 00:25:40.810 align:start position:0% transactions or whatever the recipient 00:25:40.810 --> 00:25:44.310 align:start position:0% transactions or whatever the recipient is<00:25:41.080> a<00:25:42.240> identifier<00:25:43.240> is<00:25:43.630> identified<00:25:44.140> by<00:25:44.170> a 00:25:44.310 --> 00:25:44.320 align:start position:0% is a identifier is identified by a 00:25:44.320 --> 00:25:47.010 align:start position:0% is a identifier is identified by a public<00:25:44.710> key<00:25:44.920> so<00:25:45.220> that<00:25:45.250> one<00:25:46.210> recipient<00:25:46.570> can 00:25:47.010 --> 00:25:47.020 align:start position:0% public key so that one recipient can 00:25:47.020 --> 00:25:48.990 align:start position:0% public key so that one recipient can have<00:25:47.260> multiple<00:25:47.710> transports<00:25:48.430> attached<00:25:48.730> to<00:25:48.910> it 00:25:48.990 --> 00:25:49.000 align:start position:0% have multiple transports attached to it 00:25:49.000 --> 00:25:51.840 align:start position:0% have multiple transports attached to it kind<00:25:49.210> of<00:25:49.330> how<00:25:49.660> multi<00:25:50.620> addresses<00:25:50.980> work<00:25:51.190> in<00:25:51.460> the 00:25:51.840 --> 00:25:51.850 align:start position:0% kind of how multi addresses work in the 00:25:51.850 --> 00:25:55.290 align:start position:0% kind of how multi addresses work in the p2p<00:25:52.120> and<00:25:53.010> then<00:25:54.010> what<00:25:54.220> we<00:25:54.340> do<00:25:54.490> is<00:25:54.670> we<00:25:54.850> try<00:25:55.270> to 00:25:55.290 --> 00:25:55.300 align:start position:0% p2p and then what we do is we try to 00:25:55.300 --> 00:25:56.820 align:start position:0% p2p and then what we do is we try to serialize<00:25:55.930> a<00:25:55.990> message<00:25:56.440> because<00:25:56.620> it's<00:25:56.770> a 00:25:56.820 --> 00:25:56.830 align:start position:0% serialize a message because it's a 00:25:56.830 --> 00:25:58.320 align:start position:0% serialize a message because it's a protocol<00:25:57.220> buffer<00:25:57.580> that's<00:25:57.790> not<00:25:57.970> really<00:25:58.180> that 00:25:58.320 --> 00:25:58.330 align:start position:0% protocol buffer that's not really that 00:25:58.330 --> 00:26:03.060 align:start position:0% protocol buffer that's not really that important<00:25:58.810> and<00:25:59.080> then<00:25:59.740> we<00:25:59.920> get<00:26:00.100> to<00:26:01.680> we<00:26:02.680> iterate 00:26:03.060 --> 00:26:03.070 align:start position:0% important and then we get to we iterate 00:26:03.070 --> 00:26:05.100 align:start position:0% important and then we get to we iterate over<00:26:03.220> our<00:26:03.490> transports<00:26:04.180> and<00:26:04.390> our<00:26:04.540> transports 00:26:05.100 --> 00:26:05.110 align:start position:0% over our transports and our transports 00:26:05.110 --> 00:26:08.310 align:start position:0% over our transports and our transports have<00:26:05.320> specific<00:26:06.160> peers<00:26:06.670> and<00:26:07.420> what<00:26:07.630> we<00:26:07.750> first<00:26:08.020> do 00:26:08.310 --> 00:26:08.320 align:start position:0% have specific peers and what we first do 00:26:08.320 --> 00:26:12.690 align:start position:0% have specific peers and what we first do is<00:26:08.740> we<00:26:09.070> check<00:26:09.370> if<00:26:09.790> that<00:26:10.800> if<00:26:11.800> our<00:26:12.070> recipient 00:26:12.690 --> 00:26:12.700 align:start position:0% is we check if that if our recipient 00:26:12.700 --> 00:26:15.780 align:start position:0% is we check if that if our recipient isn't<00:26:12.940> empty<00:26:13.090> we<00:26:13.960> try<00:26:14.320> to<00:26:14.380> find<00:26:14.620> a<00:26:14.740> peer<00:26:15.070> to 00:26:15.780 --> 00:26:15.790 align:start position:0% isn't empty we try to find a peer to 00:26:15.790 --> 00:26:17.420 align:start position:0% isn't empty we try to find a peer to send<00:26:16.090> to<00:26:16.210> that<00:26:16.390> that<00:26:16.780> has<00:26:16.990> that 00:26:17.420 --> 00:26:17.430 align:start position:0% send to that that has that 00:26:17.430 --> 00:26:20.060 align:start position:0% send to that that has that specific<00:26:17.850> PR<00:26:18.090> ID<00:26:18.240> and<00:26:18.720> if<00:26:19.440> we<00:26:19.560> do<00:26:19.710> that<00:26:19.740> we 00:26:20.060 --> 00:26:20.070 align:start position:0% specific PR ID and if we do that we 00:26:20.070 --> 00:26:22.640 align:start position:0% specific PR ID and if we do that we return<00:26:20.400> we've<00:26:20.910> done<00:26:21.330> a<00:26:21.360> successful<00:26:21.900> set<00:26:22.080> we 00:26:22.640 --> 00:26:22.650 align:start position:0% return we've done a successful set we 00:26:22.650 --> 00:26:24.290 align:start position:0% return we've done a successful set we don't<00:26:22.830> need<00:26:22.950> to<00:26:23.010> send<00:26:23.250> it<00:26:23.370> to<00:26:23.400> anyone<00:26:23.640> anymore 00:26:24.290 --> 00:26:24.300 align:start position:0% don't need to send it to anyone anymore 00:26:24.300 --> 00:26:27.470 align:start position:0% don't need to send it to anyone anymore what<00:26:25.110> we<00:26:25.260> do<00:26:25.380> otherwise<00:26:25.710> is<00:26:26.190> we<00:26:26.580> look<00:26:26.850> for<00:26:27.180> all 00:26:27.470 --> 00:26:27.480 align:start position:0% what we do otherwise is we look for all 00:26:27.480 --> 00:26:30.380 align:start position:0% what we do otherwise is we look for all the<00:26:27.690> peers<00:26:28.050> which<00:26:28.800> implement<00:26:29.760> that<00:26:29.910> specific 00:26:30.380 --> 00:26:30.390 align:start position:0% the peers which implement that specific 00:26:30.390 --> 00:26:34.340 align:start position:0% the peers which implement that specific service<00:26:30.810> and<00:26:31.020> we<00:26:31.920> then<00:26:32.640> flood<00:26:33.450> that<00:26:33.870> message 00:26:34.340 --> 00:26:34.350 align:start position:0% service and we then flood that message 00:26:34.350 --> 00:26:37.250 align:start position:0% service and we then flood that message to<00:26:34.740> every<00:26:35.070> single<00:26:35.340> member<00:26:36.060> who<00:26:36.750> implements 00:26:37.250 --> 00:26:37.260 align:start position:0% to every single member who implements 00:26:37.260 --> 00:26:42.800 align:start position:0% to every single member who implements that<00:26:37.290> service<00:26:37.830> and<00:26:39.320> when<00:26:40.320> we<00:26:40.470> do<00:26:40.710> a<00:26:41.640> flood<00:26:42.480> send 00:26:42.800 --> 00:26:42.810 align:start position:0% that service and when we do a flood send 00:26:42.810 --> 00:26:44.570 align:start position:0% that service and when we do a flood send we<00:26:43.230> ensure<00:26:43.620> that<00:26:43.650> we're<00:26:44.010> not<00:26:44.160> sending<00:26:44.430> a 00:26:44.570 --> 00:26:44.580 align:start position:0% we ensure that we're not sending a 00:26:44.580 --> 00:26:46.790 align:start position:0% we ensure that we're not sending a message<00:26:45.030> to<00:26:45.450> the<00:26:45.660> person<00:26:46.050> we<00:26:46.200> received<00:26:46.620> it 00:26:46.790 --> 00:26:46.800 align:start position:0% message to the person we received it 00:26:46.800 --> 00:26:48.680 align:start position:0% message to the person we received it from<00:26:46.980> where<00:26:47.700> the<00:26:47.730> person<00:26:48.180> who<00:26:48.300> originally 00:26:48.680 --> 00:26:48.690 align:start position:0% from where the person who originally 00:26:48.690 --> 00:26:53.240 align:start position:0% from where the person who originally sent<00:26:49.050> it<00:26:49.230> so<00:26:50.010> if<00:26:51.200> for<00:26:52.200> example<00:26:52.260> Eric<00:26:52.950> sends 00:26:53.240 --> 00:26:53.250 align:start position:0% sent it so if for example Eric sends 00:26:53.250 --> 00:26:57.200 align:start position:0% sent it so if for example Eric sends Greg<00:26:53.520> a<00:26:53.550> message<00:26:54.090> and<00:26:54.860> then<00:26:55.860> great<00:26:56.310> passes 00:26:57.200 --> 00:26:57.210 align:start position:0% Greg a message and then great passes 00:26:57.210 --> 00:26:59.270 align:start position:0% Greg a message and then great passes that<00:26:57.330> home<00:26:57.480> to<00:26:57.660> me<00:26:57.810> I<00:26:58.080> won't<00:26:58.380> send<00:26:58.650> it<00:26:58.770> to<00:26:59.070> any 00:26:59.270 --> 00:26:59.280 align:start position:0% that home to me I won't send it to any 00:26:59.280 --> 00:27:02.240 align:start position:0% that home to me I won't send it to any one<00:26:59.400> of<00:26:59.610> those<00:26:59.910> anymore<00:27:00.900> but<00:27:01.560> for<00:27:01.590> example<00:27:01.920> if 00:27:02.240 --> 00:27:02.250 align:start position:0% one of those anymore but for example if 00:27:02.250 --> 00:27:04.460 align:start position:0% one of those anymore but for example if America<00:27:02.670> sends<00:27:02.910> Greg<00:27:03.510> a<00:27:03.540> message<00:27:04.020> and<00:27:04.200> there's 00:27:04.460 --> 00:27:04.470 align:start position:0% America sends Greg a message and there's 00:27:04.470 --> 00:27:08.300 align:start position:0% America sends Greg a message and there's someone<00:27:04.740> between<00:27:05.930> right<00:27:06.930> and<00:27:07.140> I<00:27:07.350> Greg<00:27:08.040> may 00:27:08.300 --> 00:27:08.310 align:start position:0% someone between right and I Greg may 00:27:08.310 --> 00:27:09.770 align:start position:0% someone between right and I Greg may receive<00:27:08.700> that<00:27:08.880> message<00:27:09.060> again<00:27:09.480> because<00:27:09.660> we 00:27:09.770 --> 00:27:09.780 align:start position:0% receive that message again because we 00:27:09.780 --> 00:27:12.740 align:start position:0% receive that message again because we don't<00:27:09.810> have<00:27:10.260> the<00:27:10.500> entire<00:27:11.210> sentence<00:27:12.210> to<00:27:12.360> really 00:27:12.740 --> 00:27:12.750 align:start position:0% don't have the entire sentence to really 00:27:12.750 --> 00:27:15.110 align:start position:0% don't have the entire sentence to really have<00:27:12.900> the<00:27:13.140> first<00:27:13.920> because<00:27:14.850> that's<00:27:15.000> the 00:27:15.110 --> 00:27:15.120 align:start position:0% have the first because that's the 00:27:15.120 --> 00:27:17.900 align:start position:0% have the first because that's the original<00:27:15.510> sender<00:27:15.750> and<00:27:16.070> the<00:27:17.070> latest<00:27:17.550> because 00:27:17.900 --> 00:27:17.910 align:start position:0% original sender and the latest because 00:27:17.910 --> 00:27:19.750 align:start position:0% original sender and the latest because that's<00:27:18.120> the<00:27:18.270> person<00:27:18.450> we<00:27:19.050> thought<00:27:19.080> of<00:27:19.320> from 00:27:19.750 --> 00:27:19.760 align:start position:0% that's the person we thought of from 00:27:19.760 --> 00:27:22.700 align:start position:0% that's the person we thought of from their<00:27:20.760> optimizations<00:27:21.540> we<00:27:21.660> computed<00:27:22.080> this<00:27:22.260> and 00:27:22.700 --> 00:27:22.710 align:start position:0% their optimizations we computed this and 00:27:22.710 --> 00:27:24.920 align:start position:0% their optimizations we computed this and then<00:27:23.130> we<00:27:23.220> count<00:27:23.520> how<00:27:23.640> many<00:27:23.790> peers<00:27:24.330> we<00:27:24.510> sent<00:27:24.780> it 00:27:24.920 --> 00:27:24.930 align:start position:0% then we count how many peers we sent it 00:27:24.930 --> 00:27:26.570 align:start position:0% then we count how many peers we sent it to<00:27:24.960> because<00:27:25.230> with<00:27:25.440> if<00:27:25.650> we<00:27:25.860> sent<00:27:26.160> it<00:27:26.310> to<00:27:26.430> none 00:27:26.570 --> 00:27:26.580 align:start position:0% to because with if we sent it to none 00:27:26.580 --> 00:27:28.250 align:start position:0% to because with if we sent it to none now<00:27:26.880> this<00:27:27.240> is<00:27:27.390> part<00:27:27.630> of<00:27:27.660> our<00:27:27.750> naive<00:27:27.990> approach 00:27:28.250 --> 00:27:28.260 align:start position:0% now this is part of our naive approach 00:27:28.260 --> 00:27:30.980 align:start position:0% now this is part of our naive approach we<00:27:29.130> end<00:27:29.340> up<00:27:29.520> just<00:27:29.700> letting<00:27:30.060> it<00:27:30.270> to<00:27:30.510> every<00:27:30.810> one 00:27:30.980 --> 00:27:30.990 align:start position:0% we end up just letting it to every one 00:27:30.990 --> 00:27:34.610 align:start position:0% we end up just letting it to every one of<00:27:31.350> our<00:27:32.310> peers<00:27:32.610> which<00:27:33.570> is<00:27:33.780> kind<00:27:34.200> of<00:27:34.260> ugly<00:27:34.440> but 00:27:34.610 --> 00:27:34.620 align:start position:0% of our peers which is kind of ugly but 00:27:34.620 --> 00:27:37.340 align:start position:0% of our peers which is kind of ugly but it<00:27:34.890> works<00:27:35.160> for<00:27:35.640> our<00:27:35.940> current<00:27:36.630> implementation 00:27:37.340 --> 00:27:37.350 align:start position:0% it works for our current implementation 00:27:37.350 --> 00:27:40.450 align:start position:0% it works for our current implementation news<00:27:37.920> case<00:27:38.510> so<00:27:39.510> that's<00:27:39.720> pretty<00:27:40.260> much 00:27:40.450 --> 00:27:40.460 align:start position:0% news case so that's pretty much 00:27:40.460 --> 00:27:45.230 align:start position:0% news case so that's pretty much architectural<00:27:41.460> E<00:27:43.640> versus<00:27:44.640> what<00:27:44.820> like<00:27:45.000> Iraq 00:27:45.230 --> 00:27:45.240 align:start position:0% architectural E versus what like Iraq 00:27:45.240 --> 00:27:47.900 align:start position:0% architectural E versus what like Iraq with<00:27:45.420> the<00:27:45.710> geographical<00:27:46.710> range<00:27:46.890> talk<00:27:47.700> about 00:27:47.900 --> 00:27:47.910 align:start position:0% with the geographical range talk about 00:27:47.910 --> 00:27:48.850 align:start position:0% with the geographical range talk about you<00:27:48.090> have<00:27:48.180> different 00:27:48.850 --> 00:27:48.860 align:start position:0% you have different 00:27:48.860 --> 00:27:52.419 align:start position:0% you have different listen<00:27:49.580> there's<00:27:49.820> other<00:27:50.090> mechanisms<00:27:51.429> yeah 00:27:52.419 --> 00:27:52.429 align:start position:0% listen there's other mechanisms yeah 00:27:52.429 --> 00:27:54.789 align:start position:0% listen there's other mechanisms yeah there<00:27:53.179> will<00:27:53.330> be<00:27:53.390> different<00:27:53.899> like<00:27:54.019> ways<00:27:54.559> up 00:27:54.789 --> 00:27:54.799 align:start position:0% there will be different like ways up 00:27:54.799 --> 00:27:57.210 align:start position:0% there will be different like ways up because<00:27:55.370> for<00:27:55.549> Bluetooth<00:27:55.940> as<00:27:56.090> well<00:27:56.240> you<00:27:56.960> do<00:27:57.140> the 00:27:57.210 --> 00:27:57.220 align:start position:0% because for Bluetooth as well you do the 00:27:57.220 --> 00:28:01.240 align:start position:0% because for Bluetooth as well you do the limits<00:27:58.220> itself<00:27:58.580> on<00:27:58.820> to<00:27:59.000> eight<00:27:59.149> peers<00:27:59.679> so<00:28:00.679> we 00:28:01.240 --> 00:28:01.250 align:start position:0% limits itself on to eight peers so we 00:28:01.250 --> 00:28:04.389 align:start position:0% limits itself on to eight peers so we need<00:28:01.370> to<00:28:01.429> optimize<00:28:02.000> that<00:28:02.210> we're<00:28:02.830> hearing<00:28:03.830> with 00:28:04.389 --> 00:28:04.399 align:start position:0% need to optimize that we're hearing with 00:28:04.399 --> 00:28:07.060 align:start position:0% need to optimize that we're hearing with best<00:28:05.149> possible<00:28:05.779> peers<00:28:06.110> of<00:28:06.289> a<00:28:06.350> specific<00:28:06.830> time 00:28:07.060 --> 00:28:07.070 align:start position:0% best possible peers of a specific time 00:28:07.070 --> 00:28:09.490 align:start position:0% best possible peers of a specific time with<00:28:07.820> Wi-Fi<00:28:08.269> direct<00:28:08.510> you<00:28:08.809> don't<00:28:09.019> really<00:28:09.230> have 00:28:09.490 --> 00:28:09.500 align:start position:0% with Wi-Fi direct you don't really have 00:28:09.500 --> 00:28:11.080 align:start position:0% with Wi-Fi direct you don't really have that<00:28:09.679> you<00:28:09.799> can<00:28:09.950> start<00:28:10.220> direct<00:28:10.580> connections 00:28:11.080 --> 00:28:11.090 align:start position:0% that you can start direct connections 00:28:11.090 --> 00:28:16.000 align:start position:0% that you can start direct connections with<00:28:11.419> I<00:28:11.809> think<00:28:12.649> almost<00:28:12.860> like<00:28:13.600> 16<00:28:14.600> or<00:28:15.010> 17 00:28:16.000 --> 00:28:16.010 align:start position:0% with I think almost like 16 or 17 00:28:16.010 --> 00:28:18.220 align:start position:0% with I think almost like 16 or 17 devices<00:28:16.640> at<00:28:16.880> the<00:28:17.000> same<00:28:17.029> time<00:28:17.450> bluetooth 00:28:18.220 --> 00:28:18.230 align:start position:0% devices at the same time bluetooth 00:28:18.230 --> 00:28:20.320 align:start position:0% devices at the same time bluetooth you're<00:28:18.500> limited<00:28:18.890> to<00:28:18.980> eight<00:28:19.130> so<00:28:19.460> the<00:28:20.000> way<00:28:20.149> we 00:28:20.320 --> 00:28:20.330 align:start position:0% you're limited to eight so the way we 00:28:20.330 --> 00:28:23.110 align:start position:0% you're limited to eight so the way we appear<00:28:20.960> right<00:28:21.529> now<00:28:21.740> very<00:28:22.340> naive<00:28:22.700> but<00:28:22.909> there's 00:28:23.110 --> 00:28:23.120 align:start position:0% appear right now very naive but there's 00:28:23.120 --> 00:28:25.659 align:start position:0% appear right now very naive but there's open<00:28:23.960> research<00:28:24.350> issues<00:28:24.740> on<00:28:24.919> how<00:28:25.100> to<00:28:25.159> best 00:28:25.659 --> 00:28:25.669 align:start position:0% open research issues on how to best 00:28:25.669 --> 00:28:29.860 align:start position:0% open research issues on how to best appear<00:28:26.179> with<00:28:26.960> other<00:28:27.200> members<00:28:28.510> so<00:28:29.510> because<00:28:29.779> of 00:28:29.860 --> 00:28:29.870 align:start position:0% appear with other members so because of 00:28:29.870 --> 00:28:31.299 align:start position:0% appear with other members so because of the<00:28:29.990> limitations<00:28:30.529> of<00:28:30.590> all<00:28:30.710> these<00:28:30.830> things<00:28:31.070> like 00:28:31.299 --> 00:28:31.309 align:start position:0% the limitations of all these things like 00:28:31.309 --> 00:28:33.129 align:start position:0% the limitations of all these things like we<00:28:31.519> have<00:28:31.639> naive<00:28:32.090> implementations<00:28:32.840> but<00:28:32.990> we 00:28:33.129 --> 00:28:33.139 align:start position:0% we have naive implementations but we 00:28:33.139 --> 00:28:34.450 align:start position:0% we have naive implementations but we know<00:28:33.289> of<00:28:33.529> course<00:28:33.679> that<00:28:33.830> we<00:28:34.070> need<00:28:34.190> to<00:28:34.309> have 00:28:34.450 --> 00:28:34.460 align:start position:0% know of course that we need to have 00:28:34.460 --> 00:28:37.419 align:start position:0% know of course that we need to have better<00:28:35.240> implementations<00:28:36.200> and<00:28:36.320> discovery<00:28:37.279> and 00:28:37.419 --> 00:28:37.429 align:start position:0% better implementations and discovery and 00:28:37.429 --> 00:28:39.070 align:start position:0% better implementations and discovery and routing<00:28:37.850> will<00:28:38.059> be<00:28:38.210> different<00:28:38.659> based<00:28:38.929> on 00:28:39.070 --> 00:28:39.080 align:start position:0% routing will be different based on 00:28:39.080 --> 00:28:43.389 align:start position:0% routing will be different based on device<00:28:39.669> of<00:28:40.669> course<00:28:40.970> like<00:28:41.350> if<00:28:42.350> I<00:28:42.470> have<00:28:42.919> finding 00:28:43.389 --> 00:28:43.399 align:start position:0% device of course like if I have finding 00:28:43.399 --> 00:28:47.019 align:start position:0% device of course like if I have finding etc<00:28:44.649> but<00:28:45.649> yeah<00:28:45.799> that's<00:28:46.399> pretty<00:28:46.639> much<00:28:46.760> the 00:28:47.019 --> 00:28:47.029 align:start position:0% etc but yeah that's pretty much the 00:28:47.029 --> 00:28:48.909 align:start position:0% etc but yeah that's pretty much the entire<00:28:47.120> scent<00:28:47.750> function<00:28:48.169> and<00:28:48.440> this<00:28:48.590> is<00:28:48.649> pretty 00:28:48.909 --> 00:28:48.919 align:start position:0% entire scent function and this is pretty 00:28:48.919 --> 00:28:51.310 align:start position:0% entire scent function and this is pretty much<00:28:49.039> the<00:28:49.639> hardest<00:28:50.090> part<00:28:50.480> of<00:28:50.750> ultralight 00:28:51.310 --> 00:28:51.320 align:start position:0% much the hardest part of ultralight 00:28:51.320 --> 00:28:53.440 align:start position:0% much the hardest part of ultralight being<00:28:51.620> like<00:28:52.309> when<00:28:52.519> you<00:28:52.700> implement<00:28:53.419> a 00:28:53.440 --> 00:28:53.450 align:start position:0% being like when you implement a 00:28:53.450 --> 00:28:54.669 align:start position:0% being like when you implement a transport<00:28:53.990> you<00:28:54.110> don't<00:28:54.260> need<00:28:54.350> to<00:28:54.440> care<00:28:54.649> about 00:28:54.669 --> 00:28:54.679 align:start position:0% transport you don't need to care about 00:28:54.679 --> 00:28:57.430 align:start position:0% transport you don't need to care about this<00:28:55.269> when<00:28:56.269> you<00:28:56.389> met<00:28:56.750> a<00:28:56.779> service<00:28:57.200> you<00:28:57.289> don't 00:28:57.430 --> 00:28:57.440 align:start position:0% this when you met a service you don't 00:28:57.440 --> 00:28:59.139 align:start position:0% this when you met a service you don't need<00:28:57.529> to<00:28:57.620> care<00:28:57.799> about<00:28:57.830> this<00:28:58.190> we<00:28:58.669> take<00:28:58.880> care<00:28:59.090> of 00:28:59.139 --> 00:28:59.149 align:start position:0% need to care about this we take care of 00:28:59.149 --> 00:29:03.220 align:start position:0% need to care about this we take care of that<00:29:00.279> then<00:29:01.279> I'll<00:29:01.429> quickly<00:29:01.610> show<00:29:02.029> how 00:29:03.220 --> 00:29:03.230 align:start position:0% that then I'll quickly show how 00:29:03.230 --> 00:29:04.649 align:start position:0% that then I'll quickly show how [Music] 00:29:04.649 --> 00:29:04.659 align:start position:0% [Music] 00:29:04.659 --> 00:29:11.139 align:start position:0% [Music] transports<00:29:05.659> work<00:29:09.549> should<00:29:10.549> in<00:29:10.669> a<00:29:10.760> very<00:29:10.970> rough 00:29:11.139 --> 00:29:11.149 align:start position:0% transports work should in a very rough 00:29:11.149 --> 00:29:12.879 align:start position:0% transports work should in a very rough way<00:29:11.269> because<00:29:11.570> there's<00:29:11.779> a<00:29:11.840> lot<00:29:12.019> of<00:29:12.049> ugly<00:29:12.649> code 00:29:12.879 --> 00:29:12.889 align:start position:0% way because there's a lot of ugly code 00:29:12.889 --> 00:29:15.820 align:start position:0% way because there's a lot of ugly code on<00:29:13.190> top<00:29:13.220> of<00:29:13.639> it<00:29:13.789> what<00:29:14.600> happens<00:29:14.960> is<00:29:15.110> a<00:29:15.139> transport 00:29:15.820 --> 00:29:15.830 align:start position:0% on top of it what happens is a transport 00:29:15.830 --> 00:29:17.500 align:start position:0% on top of it what happens is a transport asset<00:29:16.340> implements<00:29:16.850> this<00:29:16.970> sending<00:29:17.360> this 00:29:17.500 --> 00:29:17.510 align:start position:0% asset implements this sending this 00:29:17.510 --> 00:29:19.810 align:start position:0% asset implements this sending this listing<00:29:17.840> function<00:29:18.230> and<00:29:18.559> they<00:29:19.429> then<00:29:19.610> have 00:29:19.810 --> 00:29:19.820 align:start position:0% listing function and they then have 00:29:19.820 --> 00:29:21.340 align:start position:0% listing function and they then have callback<00:29:20.269> functions<00:29:20.720> which<00:29:20.899> is<00:29:20.990> like<00:29:21.139> the 00:29:21.340 --> 00:29:21.350 align:start position:0% callback functions which is like the 00:29:21.350 --> 00:29:24.120 align:start position:0% callback functions which is like the transport<00:29:21.919> received<00:29:22.639> certain<00:29:23.059> data<00:29:23.240> which<00:29:23.750> is 00:29:24.120 --> 00:29:24.130 align:start position:0% transport received certain data which is 00:29:24.130 --> 00:29:26.710 align:start position:0% transport received certain data which is which<00:29:25.130> the<00:29:25.159> node<00:29:25.549> implements<00:29:26.179> so<00:29:26.360> that<00:29:26.510> when 00:29:26.710 --> 00:29:26.720 align:start position:0% which the node implements so that when 00:29:26.720 --> 00:29:29.860 align:start position:0% which the node implements so that when data<00:29:27.679> is<00:29:27.769> received<00:29:28.190> the<00:29:28.909> node<00:29:29.120> tries<00:29:29.630> to 00:29:29.860 --> 00:29:29.870 align:start position:0% data is received the node tries to 00:29:29.870 --> 00:29:32.580 align:start position:0% data is received the node tries to unpack<00:29:30.440> it<00:29:30.470> checks<00:29:31.039> if<00:29:31.340> it<00:29:31.700> is<00:29:31.820> supposed<00:29:32.210> to 00:29:32.580 --> 00:29:32.590 align:start position:0% unpack it checks if it is supposed to 00:29:32.590 --> 00:29:35.200 align:start position:0% unpack it checks if it is supposed to handle<00:29:33.590> that<00:29:33.710> data<00:29:33.980> and<00:29:34.250> then<00:29:34.399> passes<00:29:34.850> it<00:29:35.000> one 00:29:35.200 --> 00:29:35.210 align:start position:0% handle that data and then passes it one 00:29:35.210 --> 00:29:36.639 align:start position:0% handle that data and then passes it one layer<00:29:35.419> up<00:29:35.630> which<00:29:35.779> would<00:29:35.929> be<00:29:36.049> for<00:29:36.200> example<00:29:36.529> your 00:29:36.639 --> 00:29:36.649 align:start position:0% layer up which would be for example your 00:29:36.649 --> 00:29:39.700 align:start position:0% layer up which would be for example your application<00:29:37.960> so<00:29:38.960> the<00:29:39.049> node<00:29:39.230> does<00:29:39.440> all<00:29:39.559> that 00:29:39.700 --> 00:29:39.710 align:start position:0% application so the node does all that 00:29:39.710 --> 00:29:41.259 align:start position:0% application so the node does all that checking<00:29:39.950> for<00:29:40.190> you<00:29:40.309> so<00:29:40.490> if<00:29:40.789> you<00:29:40.940> implement 00:29:41.259 --> 00:29:41.269 align:start position:0% checking for you so if you implement 00:29:41.269 --> 00:29:44.049 align:start position:0% checking for you so if you implement electrolyte<00:29:41.840> beam<00:29:42.049> you<00:29:42.710> can<00:29:43.130> be<00:29:43.610> certain<00:29:44.029> that 00:29:44.049 --> 00:29:44.059 align:start position:0% electrolyte beam you can be certain that 00:29:44.059 --> 00:29:45.940 align:start position:0% electrolyte beam you can be certain that you're<00:29:44.330> only<00:29:44.510> receiving<00:29:45.230> packets<00:29:45.649> that<00:29:45.860> you 00:29:45.940 --> 00:29:45.950 align:start position:0% you're only receiving packets that you 00:29:45.950 --> 00:29:47.769 align:start position:0% you're only receiving packets that you know<00:29:46.100> how<00:29:46.279> to<00:29:46.340> handle<00:29:46.580> or<00:29:47.149> that<00:29:47.360> were<00:29:47.480> sent<00:29:47.720> to 00:29:47.769 --> 00:29:47.779 align:start position:0% know how to handle or that were sent to 00:29:47.779 --> 00:29:51.260 align:start position:0% know how to handle or that were sent to you<00:29:47.899> directly<00:29:48.380> and<00:29:48.940> are<00:29:49.940> not<00:29:50.149> just<00:29:50.179> packet 00:29:51.260 --> 00:29:51.270 align:start position:0% you directly and are not just packet 00:29:51.270 --> 00:29:54.310 align:start position:0% you directly and are not just packet -<00:29:51.360> forward<00:29:51.780> because<00:29:52.560> right<00:29:53.130> now<00:29:53.340> what<00:29:53.580> we<00:29:53.670> have 00:29:54.310 --> 00:29:54.320 align:start position:0% - forward because right now what we have 00:29:54.320 --> 00:29:58.730 align:start position:0% - forward because right now what we have ultralight<00:29:55.320> beam<00:29:55.500> notes<00:29:55.740> are<00:29:56.570> all<00:29:57.710> have<00:29:58.710> a 00:29:58.730 --> 00:29:58.740 align:start position:0% ultralight beam notes are all have a 00:29:58.740 --> 00:30:01.340 align:start position:0% ultralight beam notes are all have a forward<00:29:59.280> capability<00:29:59.910> so<00:30:00.150> that<00:30:00.180> we<00:30:00.960> can<00:30:01.110> have 00:30:01.340 --> 00:30:01.350 align:start position:0% forward capability so that we can have 00:30:01.350 --> 00:30:04.340 align:start position:0% forward capability so that we can have this<00:30:01.530> strong<00:30:02.130> network<00:30:02.490> so<00:30:03.060> even<00:30:03.360> like<00:30:03.510> if<00:30:03.780> you 00:30:04.340 --> 00:30:04.350 align:start position:0% this strong network so even like if you 00:30:04.350 --> 00:30:06.050 align:start position:0% this strong network so even like if you were<00:30:04.500> building<00:30:04.800> a<00:30:05.040> chat<00:30:05.310> app<00:30:05.550> and<00:30:05.760> someone 00:30:06.050 --> 00:30:06.060 align:start position:0% were building a chat app and someone 00:30:06.060 --> 00:30:08.960 align:start position:0% were building a chat app and someone else<00:30:06.210> is<00:30:06.390> building<00:30:06.840> a<00:30:07.140> game<00:30:07.980> for<00:30:08.280> example<00:30:08.730> and 00:30:08.960 --> 00:30:08.970 align:start position:0% else is building a game for example and 00:30:08.970 --> 00:30:10.850 align:start position:0% else is building a game for example and those<00:30:09.210> both<00:30:09.690> implement<00:30:10.260> butcher<00:30:10.500> light<00:30:10.650> beam 00:30:10.850 --> 00:30:10.860 align:start position:0% those both implement butcher light beam 00:30:10.860 --> 00:30:14.240 align:start position:0% those both implement butcher light beam what<00:30:11.490> will<00:30:11.640> happen<00:30:12.030> is<00:30:12.440> your<00:30:13.440> chat<00:30:13.770> app<00:30:13.980> might 00:30:14.240 --> 00:30:14.250 align:start position:0% what will happen is your chat app might 00:30:14.250 --> 00:30:16.940 align:start position:0% what will happen is your chat app might actually<00:30:14.460> really<00:30:15.200> someone<00:30:16.200> else's<00:30:16.530> game<00:30:16.770> at 00:30:16.940 --> 00:30:16.950 align:start position:0% actually really someone else's game at 00:30:16.950 --> 00:30:18.710 align:start position:0% actually really someone else's game at packets<00:30:17.400> and<00:30:17.700> that<00:30:18.000> way<00:30:18.120> you<00:30:18.180> can<00:30:18.360> build<00:30:18.480> like 00:30:18.710 --> 00:30:18.720 align:start position:0% packets and that way you can build like 00:30:18.720 --> 00:30:21.050 align:start position:0% packets and that way you can build like a<00:30:18.750> really<00:30:19.200> strong<00:30:19.500> network<00:30:19.950> like<00:30:20.670> just 00:30:21.050 --> 00:30:21.060 align:start position:0% a really strong network like just 00:30:21.060 --> 00:30:22.910 align:start position:0% a really strong network like just imagine<00:30:21.240> in<00:30:21.450> New<00:30:21.570> York<00:30:21.810> City<00:30:22.020> or<00:30:22.140> blog<00:30:22.410> set<00:30:22.710> and 00:30:22.910 --> 00:30:22.920 align:start position:0% imagine in New York City or blog set and 00:30:22.920 --> 00:30:24.800 align:start position:0% imagine in New York City or blog set and both<00:30:23.190> telegram<00:30:23.670> had<00:30:23.880> all<00:30:24.030> fine<00:30:24.240> messaging<00:30:24.690> you 00:30:24.800 --> 00:30:24.810 align:start position:0% both telegram had all fine messaging you 00:30:24.810 --> 00:30:27.260 align:start position:0% both telegram had all fine messaging you never<00:30:25.220> waste<00:30:26.220> data<00:30:26.550> again<00:30:26.850> minutes<00:30:27.180> you<00:30:27.240> just 00:30:27.260 --> 00:30:27.270 align:start position:0% never waste data again minutes you just 00:30:27.270 --> 00:30:32.050 align:start position:0% never waste data again minutes you just walk<00:30:27.660> through<00:30:27.690> it<00:30:27.900> at<00:30:28.260> this<00:30:28.380> point<00:30:30.140> so<00:30:31.140> yeah 00:30:32.050 --> 00:30:32.060 align:start position:0% walk through it at this point so yeah 00:30:32.060 --> 00:30:37.010 align:start position:0% walk through it at this point so yeah that's<00:30:33.060> pretty<00:30:33.240> much<00:30:33.830> what<00:30:34.830> we<00:30:34.980> have<00:30:36.020> I'm 00:30:37.010 --> 00:30:37.020 align:start position:0% that's pretty much what we have I'm 00:30:37.020 --> 00:30:38.660 align:start position:0% that's pretty much what we have I'm gonna<00:30:37.200> show<00:30:37.410> the<00:30:37.530> real<00:30:37.710> layer<00:30:37.860> code<00:30:38.100> as<00:30:38.220> well<00:30:38.400> a 00:30:38.660 --> 00:30:38.670 align:start position:0% gonna show the real layer code as well a 00:30:38.670 --> 00:30:41.420 align:start position:0% gonna show the real layer code as well a lot<00:30:39.570> of<00:30:39.660> this<00:30:39.810> code<00:30:40.050> which<00:30:40.380> we<00:30:40.590> have<00:30:40.800> external 00:30:41.420 --> 00:30:41.430 align:start position:0% lot of this code which we have external 00:30:41.430 --> 00:30:43.820 align:start position:0% lot of this code which we have external and<00:30:41.610> the<00:30:41.670> layer<00:30:41.970> is<00:30:42.120> going<00:30:42.300> to<00:30:42.360> become<00:30:42.830> no 00:30:43.820 --> 00:30:43.830 align:start position:0% and the layer is going to become no 00:30:43.830 --> 00:30:47.690 align:start position:0% and the layer is going to become no native<00:30:44.340> code<00:30:44.610> later<00:30:45.270> on<00:30:45.480> that's<00:30:46.260> an<00:30:46.590> open<00:30:47.400> pool 00:30:47.690 --> 00:30:47.700 align:start position:0% native code later on that's an open pool 00:30:47.700 --> 00:30:49.700 align:start position:0% native code later on that's an open pool request<00:30:48.000> right<00:30:48.150> now<00:30:48.330> but<00:30:48.990> real<00:30:49.320> layers<00:30:49.500> are 00:30:49.700 --> 00:30:49.710 align:start position:0% request right now but real layers are 00:30:49.710 --> 00:30:52.550 align:start position:0% request right now but real layers are really<00:30:50.010> simple<00:30:50.640> as<00:30:50.700> well<00:30:50.850> what<00:30:51.060> happens<00:30:51.450> is<00:30:51.660> it 00:30:52.550 --> 00:30:52.560 align:start position:0% really simple as well what happens is it 00:30:52.560 --> 00:30:54.410 align:start position:0% really simple as well what happens is it checks<00:30:52.950> if<00:30:53.100> we<00:30:53.220> have<00:30:53.400> that<00:30:53.580> specific<00:30:53.760> service 00:30:54.410 --> 00:30:54.420 align:start position:0% checks if we have that specific service 00:30:54.420 --> 00:30:56.690 align:start position:0% checks if we have that specific service and<00:30:54.660> then<00:30:55.080> that<00:30:55.230> message<00:30:55.650> is<00:30:55.980> processed<00:30:56.610> by 00:30:56.690 --> 00:30:56.700 align:start position:0% and then that message is processed by 00:30:56.700 --> 00:30:58.760 align:start position:0% and then that message is processed by specific<00:30:57.270> service<00:30:57.630> so<00:30:58.050> in<00:30:58.140> the<00:30:58.230> case<00:30:58.440> of<00:30:58.470> our 00:30:58.760 --> 00:30:58.770 align:start position:0% specific service so in the case of our 00:30:58.770 --> 00:31:01.460 align:start position:0% specific service so in the case of our chat<00:30:59.070> app<00:30:59.310> it<00:30:59.910> was<00:31:00.030> really<00:31:00.330> just<00:31:00.510> decoding<00:31:01.320> the 00:31:01.460 --> 00:31:01.470 align:start position:0% chat app it was really just decoding the 00:31:01.470 --> 00:31:09.800 align:start position:0% chat app it was really just decoding the data<00:31:01.680> that<00:31:02.280> we<00:31:02.430> had<00:31:02.640> in<00:31:03.060> our<00:31:03.540> packet<00:31:04.110> I<00:31:08.810> don't 00:31:09.800 --> 00:31:09.810 align:start position:0% data that we had in our packet I don't 00:31:09.810 --> 00:31:11.580 align:start position:0% data that we had in our packet I don't know<00:31:09.960> if<00:31:10.080> I<00:31:10.140> have<00:31:10.230> that<00:31:10.260> person<00:31:10.650> joined<00:31:10.830> it 00:31:11.580 --> 00:31:11.590 align:start position:0% know if I have that person joined it 00:31:11.590 --> 00:31:15.120 align:start position:0% know if I have that person joined it I<00:31:11.620> don't<00:31:12.340> have<00:31:12.460> internet<00:31:12.730> oh<00:31:13.120> yeah<00:31:13.810> see<00:31:14.710> if<00:31:14.950> we 00:31:15.120 --> 00:31:15.130 align:start position:0% I don't have internet oh yeah see if we 00:31:15.130 --> 00:31:20.880 align:start position:0% I don't have internet oh yeah see if we had<00:31:15.220> a<00:31:15.280> multi<00:31:16.060> being<00:31:16.300> you<00:31:16.840> see<00:31:17.170> it<00:31:17.320> though<00:31:19.890> it 00:31:20.880 --> 00:31:20.890 align:start position:0% had a multi being you see it though it 00:31:20.890 --> 00:31:22.980 align:start position:0% had a multi being you see it though it certainly<00:31:21.310> the<00:31:21.520> real<00:31:21.880> Ayres<00:31:22.060> will<00:31:22.510> just<00:31:22.840> be 00:31:22.980 --> 00:31:22.990 align:start position:0% certainly the real Ayres will just be 00:31:22.990 --> 00:31:24.630 align:start position:0% certainly the real Ayres will just be having<00:31:23.500> a<00:31:23.530> much<00:31:23.740> three<00:31:24.010> that<00:31:24.160> they<00:31:24.250> find<00:31:24.520> in 00:31:24.630 --> 00:31:24.640 align:start position:0% having a much three that they find in 00:31:24.640 --> 00:31:26.520 align:start position:0% having a much three that they find in frustrating<00:31:25.180> they<00:31:25.330> were<00:31:25.450> like<00:31:25.660> opt-out<00:31:26.140> so 00:31:26.520 --> 00:31:26.530 align:start position:0% frustrating they were like opt-out so 00:31:26.530 --> 00:31:28.590 align:start position:0% frustrating they were like opt-out so this<00:31:26.680> is<00:31:26.830> kind<00:31:27.070> of<00:31:27.160> there's<00:31:27.520> this<00:31:27.790> so<00:31:28.420> what 00:31:28.590 --> 00:31:28.600 align:start position:0% this is kind of there's this so what 00:31:28.600 --> 00:31:29.940 align:start position:0% this is kind of there's this so what we're<00:31:28.750> thinking<00:31:28.930> of<00:31:29.260> right<00:31:29.440> now<00:31:29.590> is<00:31:29.710> like<00:31:29.830> an 00:31:29.940 --> 00:31:29.950 align:start position:0% we're thinking of right now is like an 00:31:29.950 --> 00:31:32.580 align:start position:0% we're thinking of right now is like an accounting<00:31:30.400> model<00:31:30.990> and<00:31:31.990> then<00:31:32.140> we<00:31:32.230> do<00:31:32.380> some 00:31:32.580 --> 00:31:32.590 align:start position:0% accounting model and then we do some 00:31:32.590 --> 00:31:34.260 align:start position:0% accounting model and then we do some form<00:31:32.830> of<00:31:32.890> tit-for-tat<00:31:33.160> that<00:31:33.790> you<00:31:33.910> wouldn't 00:31:34.260 --> 00:31:34.270 align:start position:0% form of tit-for-tat that you wouldn't 00:31:34.270 --> 00:31:36.810 align:start position:0% form of tit-for-tat that you wouldn't continue<00:31:34.660> relaying<00:31:35.290> messages<00:31:35.520> through<00:31:36.520> for 00:31:36.810 --> 00:31:36.820 align:start position:0% continue relaying messages through for 00:31:36.820 --> 00:31:40.500 align:start position:0% continue relaying messages through for someone<00:31:37.440> given<00:31:38.440> that<00:31:38.590> they<00:31:38.710> have<00:31:39.120> used<00:31:40.120> up<00:31:40.360> all 00:31:40.500 --> 00:31:40.510 align:start position:0% someone given that they have used up all 00:31:40.510 --> 00:31:42.390 align:start position:0% someone given that they have used up all their<00:31:40.660> bandwidth<00:31:41.140> unless<00:31:41.740> they<00:31:41.890> for<00:31:42.340> example 00:31:42.390 --> 00:31:42.400 align:start position:0% their bandwidth unless they for example 00:31:42.400 --> 00:31:44.880 align:start position:0% their bandwidth unless they for example start<00:31:42.820> paying<00:31:43.060> but<00:31:43.990> the<00:31:44.110> second<00:31:44.440> we<00:31:44.530> have<00:31:44.620> some 00:31:44.880 --> 00:31:44.890 align:start position:0% start paying but the second we have some 00:31:44.890 --> 00:31:46.770 align:start position:0% start paying but the second we have some naive<00:31:45.100> accounting<00:31:45.850> model<00:31:46.000> we<00:31:46.270> can<00:31:46.420> figure<00:31:46.690> out 00:31:46.770 --> 00:31:46.780 align:start position:0% naive accounting model we can figure out 00:31:46.780 --> 00:31:48.540 align:start position:0% naive accounting model we can figure out the<00:31:47.020> incentive<00:31:47.410> models<00:31:47.710> on<00:31:47.830> top<00:31:48.010> of<00:31:48.130> that<00:31:48.250> so 00:31:48.540 --> 00:31:48.550 align:start position:0% the incentive models on top of that so 00:31:48.550 --> 00:31:50.820 align:start position:0% the incentive models on top of that so that's<00:31:48.730> why<00:31:48.910> we<00:31:49.630> started<00:31:49.990> it<00:31:50.110> as<00:31:50.380> New<00:31:50.560> York 00:31:50.820 --> 00:31:50.830 align:start position:0% that's why we started it as New York 00:31:50.830 --> 00:31:52.140 align:start position:0% that's why we started it as New York because<00:31:51.100> we<00:31:51.220> thought<00:31:51.400> about<00:31:51.550> this<00:31:51.910> would<00:31:52.060> be 00:31:52.140 --> 00:31:52.150 align:start position:0% because we thought about this would be 00:31:52.150 --> 00:31:53.550 align:start position:0% because we thought about this would be cool<00:31:52.360> for<00:31:52.390> you<00:31:52.720> that<00:31:52.840> also<00:31:52.990> have<00:31:53.140> payment 00:31:53.550 --> 00:31:53.560 align:start position:0% cool for you that also have payment 00:31:53.560 --> 00:31:55.500 align:start position:0% cool for you that also have payment channels<00:31:53.830> on<00:31:53.950> top<00:31:54.160> of<00:31:54.310> it<00:31:54.430> so<00:31:54.970> that's<00:31:55.150> someone 00:31:55.500 --> 00:31:55.510 align:start position:0% channels on top of it so that's someone 00:31:55.510 --> 00:31:59.760 align:start position:0% channels on top of it so that's someone like<00:31:55.690> you<00:31:56.260> pay<00:31:56.470> for<00:31:56.530> relays<00:31:57.270> which<00:31:58.320> we<00:31:59.320> can<00:31:59.530> do 00:31:59.760 --> 00:31:59.770 align:start position:0% like you pay for relays which we can do 00:31:59.770 --> 00:32:01.440 align:start position:0% like you pay for relays which we can do and<00:31:59.950> it<00:32:00.040> might<00:32:00.250> be<00:32:00.280> it<00:32:00.730> would<00:32:00.910> probably<00:32:01.240> end<00:32:01.330> up 00:32:01.440 --> 00:32:01.450 align:start position:0% and it might be it would probably end up 00:32:01.450 --> 00:32:03.900 align:start position:0% and it might be it would probably end up being<00:32:01.630> she<00:32:01.870> preferred<00:32:02.290> than<00:32:02.860> having<00:32:03.640> to<00:32:03.790> get 00:32:03.900 --> 00:32:03.910 align:start position:0% being she preferred than having to get 00:32:03.910 --> 00:32:12.700 align:start position:0% being she preferred than having to get data<00:32:04.270> into<00:32:04.630> certain<00:32:04.990> places<00:32:09.450> yeah<00:32:11.250> exactly 00:32:12.700 --> 00:32:12.710 align:start position:0% data into certain places yeah exactly 00:32:12.710 --> 00:32:17.750 align:start position:0% data into certain places yeah exactly [Music] 00:32:17.750 --> 00:32:17.760 align:start position:0% 00:32:17.760 --> 00:32:24.890 align:start position:0% are<00:32:18.760> there<00:32:18.940> any<00:32:19.060> questions 00:32:24.890 --> 00:32:24.900 align:start position:0% 00:32:24.900 --> 00:32:28.050 align:start position:0% not<00:32:25.900> yet<00:32:26.350> like<00:32:26.590> we're<00:32:26.860> very<00:32:27.370> early<00:32:27.790> stage<00:32:28.030> in 00:32:28.050 --> 00:32:28.060 align:start position:0% not yet like we're very early stage in 00:32:28.060 --> 00:32:30.120 align:start position:0% not yet like we're very early stage in spam<00:32:28.540> attacks<00:32:28.870> amendments<00:32:29.470> are<00:32:29.590> relatively 00:32:30.120 --> 00:32:30.130 align:start position:0% spam attacks amendments are relatively 00:32:30.130 --> 00:32:43.650 align:start position:0% spam attacks amendments are relatively hard<00:32:30.490> to<00:32:30.820> solve 00:32:43.650 --> 00:32:43.660 align:start position:0% 00:32:43.660 --> 00:32:47.230 align:start position:0% it's<00:32:44.660> called<00:32:44.900> laser<00:32:45.850> so<00:32:46.850> we<00:32:46.970> were<00:32:47.090> looking 00:32:47.230 --> 00:32:47.240 align:start position:0% it's called laser so we were looking 00:32:47.240 --> 00:32:50.230 align:start position:0% it's called laser so we were looking into<00:32:47.510> more<00:32:47.990> traditional<00:32:48.250> amendment<00:32:49.250> routing 00:32:50.230 --> 00:32:50.240 align:start position:0% into more traditional amendment routing 00:32:50.240 --> 00:32:51.870 align:start position:0% into more traditional amendment routing protocols<00:32:50.720> and<00:32:51.020> there's<00:32:51.230> three<00:32:51.590> of<00:32:51.620> those 00:32:51.870 --> 00:32:51.880 align:start position:0% protocols and there's three of those 00:32:51.880 --> 00:32:54.430 align:start position:0% protocols and there's three of those essentially<00:32:52.880> that<00:32:53.480> are<00:32:53.600> used<00:32:53.780> for<00:32:53.960> amendments 00:32:54.430 --> 00:32:54.440 align:start position:0% essentially that are used for amendments 00:32:54.440 --> 00:32:56.650 align:start position:0% essentially that are used for amendments because<00:32:55.070> the<00:32:55.340> problem<00:32:55.700> the<00:32:56.150> problem<00:32:56.420> with<00:32:56.630> a 00:32:56.650 --> 00:32:56.660 align:start position:0% because the problem the problem with a 00:32:56.660 --> 00:32:59.290 align:start position:0% because the problem the problem with a lot<00:32:56.930> of<00:32:57.080> these<00:32:57.890> routing<00:32:58.340> protocols<00:32:59.000> is<00:32:59.150> that 00:32:59.290 --> 00:32:59.300 align:start position:0% lot of these routing protocols is that 00:32:59.300 --> 00:33:01.390 align:start position:0% lot of these routing protocols is that they<00:32:59.420> don't<00:32:59.660> work<00:32:59.930> the<00:33:00.320> second<00:33:00.770> you<00:33:00.860> have<00:33:01.070> any 00:33:01.390 --> 00:33:01.400 align:start position:0% they don't work the second you have any 00:33:01.400 --> 00:33:03.610 align:start position:0% they don't work the second you have any aspect<00:33:01.880> of<00:33:02.200> connections<00:33:03.200> made<00:33:03.380> very 00:33:03.610 --> 00:33:03.620 align:start position:0% aspect of connections made very 00:33:03.620 --> 00:33:12.450 align:start position:0% aspect of connections made very short-lived<00:33:05.230> side<00:33:06.230> of<00:33:06.350> a<00:33:06.470> quasar<00:33:10.660> thank<00:33:11.660> you 00:33:12.450 --> 00:33:12.460 align:start position:0% short-lived side of a quasar thank you 00:33:12.460 --> 00:33:15.010 align:start position:0% short-lived side of a quasar thank you yeah<00:33:13.460> midnight<00:33:13.670> routing<00:33:14.090> is<00:33:14.210> hard<00:33:14.420> it's 00:33:15.010 --> 00:33:15.020 align:start position:0% yeah midnight routing is hard it's 00:33:15.020 --> 00:33:17.410 align:start position:0% yeah midnight routing is hard it's there's<00:33:15.650> like<00:33:15.800> as<00:33:16.610> Dean<00:33:16.910> said<00:33:17.120> there's<00:33:17.300> like 00:33:17.410 --> 00:33:17.420 align:start position:0% there's like as Dean said there's like 00:33:17.420 --> 00:33:20.020 align:start position:0% there's like as Dean said there's like three<00:33:17.630> different<00:33:17.660> kinds<00:33:18.550> there's<00:33:19.550> obviously 00:33:20.020 --> 00:33:20.030 align:start position:0% three different kinds there's obviously 00:33:20.030 --> 00:33:22.750 align:start position:0% three different kinds there's obviously trade-offs<00:33:20.510> in<00:33:20.870> like<00:33:21.650> processing<00:33:22.400> speed 00:33:22.750 --> 00:33:22.760 align:start position:0% trade-offs in like processing speed 00:33:22.760 --> 00:33:24.610 align:start position:0% trade-offs in like processing speed early<00:33:23.150> yeah<00:33:23.510> you<00:33:23.900> can<00:33:24.020> either<00:33:24.200> have<00:33:24.410> like<00:33:24.590> very 00:33:24.610 --> 00:33:24.620 align:start position:0% early yeah you can either have like very 00:33:24.620 --> 00:33:28.390 align:start position:0% early yeah you can either have like very accurate<00:33:25.340> routing<00:33:25.700> or<00:33:25.970> you<00:33:26.240> can<00:33:26.390> have<00:33:27.400> where 00:33:28.390 --> 00:33:28.400 align:start position:0% accurate routing or you can have where 00:33:28.400 --> 00:33:30.400 align:start position:0% accurate routing or you can have where you<00:33:28.520> would<00:33:28.640> have<00:33:28.760> to<00:33:28.910> do<00:33:29.060> a<00:33:29.300> lot<00:33:29.690> a<00:33:29.990> lot<00:33:30.230> of 00:33:30.400 --> 00:33:30.410 align:start position:0% you would have to do a lot a lot of 00:33:30.410 --> 00:33:34.210 align:start position:0% you would have to do a lot a lot of computations<00:33:31.040> so<00:33:32.380> yeah<00:33:33.380> one<00:33:33.830> of<00:33:33.860> our<00:33:34.070> next 00:33:34.210 --> 00:33:34.220 align:start position:0% computations so yeah one of our next 00:33:34.220 --> 00:33:36.190 align:start position:0% computations so yeah one of our next steps<00:33:34.490> is<00:33:34.730> going<00:33:34.880> to<00:33:34.970> be<00:33:35.150> investigating<00:33:35.870> like 00:33:36.190 --> 00:33:36.200 align:start position:0% steps is going to be investigating like 00:33:36.200 --> 00:33:37.690 align:start position:0% steps is going to be investigating like building<00:33:36.650> out<00:33:36.740> all<00:33:36.950> of<00:33:36.980> these<00:33:37.160> different<00:33:37.220> ones 00:33:37.690 --> 00:33:37.700 align:start position:0% building out all of these different ones 00:33:37.700 --> 00:33:39.670 align:start position:0% building out all of these different ones and<00:33:38.060> do<00:33:38.450> the<00:33:38.570> actual<00:33:38.810> artist<00:33:39.140> testing<00:33:39.590> them 00:33:39.670 --> 00:33:39.680 align:start position:0% and do the actual artist testing them 00:33:39.680 --> 00:33:42.880 align:start position:0% and do the actual artist testing them out<00:33:40.210> and<00:33:41.210> obviously<00:33:41.840> doing<00:33:42.260> original 00:33:42.880 --> 00:33:42.890 align:start position:0% out and obviously doing original 00:33:42.890 --> 00:33:45.310 align:start position:0% out and obviously doing original research<00:33:43.130> on<00:33:43.730> that<00:33:44.480> I<00:33:44.510> can<00:33:44.780> see<00:33:44.990> if<00:33:45.050> we<00:33:45.170> could 00:33:45.310 --> 00:33:45.320 align:start position:0% research on that I can see if we could 00:33:45.320 --> 00:33:48.640 align:start position:0% research on that I can see if we could talk<00:33:45.500> about<00:33:45.590> something<00:33:45.860> better<00:33:46.160> as<00:33:46.370> well<00:33:47.650> and 00:33:48.640 --> 00:33:48.650 align:start position:0% talk about something better as well and 00:33:48.650 --> 00:33:50.920 align:start position:0% talk about something better as well and also<00:33:49.550> with<00:33:49.850> when<00:33:50.270> it<00:33:50.390> comes<00:33:50.540> to<00:33:50.660> the<00:33:50.750> real 00:33:50.920 --> 00:33:50.930 align:start position:0% also with when it comes to the real 00:33:50.930 --> 00:33:54.280 align:start position:0% also with when it comes to the real layers<00:33:51.790> to<00:33:52.790> kind<00:33:53.060> of<00:33:53.090> address<00:33:53.360> like<00:33:53.690> your 00:33:54.280 --> 00:33:54.290 align:start position:0% layers to kind of address like your 00:33:54.290 --> 00:34:01.000 align:start position:0% layers to kind of address like your question<00:33:54.800> I<00:33:54.830> like<00:33:57.760> that<00:33:58.790> ideally<00:33:59.780> in<00:34:00.110> a<00:34:00.590> sales 00:34:01.000 --> 00:34:01.010 align:start position:0% question I like that ideally in a sales 00:34:01.010 --> 00:34:02.540 align:start position:0% question I like that ideally in a sales falling<00:34:01.340> like<00:34:01.520> an<00:34:01.640> ER 00:34:02.540 --> 00:34:02.550 align:start position:0% falling like an ER 00:34:02.550 --> 00:34:04.280 align:start position:0% falling like an ER here<00:34:02.670> is<00:34:02.880> an<00:34:02.970> example<00:34:03.240> of<00:34:03.450> an<00:34:03.660> official<00:34:04.110> it's<00:34:04.230> a 00:34:04.280 --> 00:34:04.290 align:start position:0% here is an example of an official it's a 00:34:04.290 --> 00:34:05.570 align:start position:0% here is an example of an official it's a little<00:34:04.440> bit<00:34:04.530> easier<00:34:04.560> you<00:34:04.860> can<00:34:05.070> probably<00:34:05.310> get 00:34:05.570 --> 00:34:05.580 align:start position:0% little bit easier you can probably get 00:34:05.580 --> 00:34:08.750 align:start position:0% little bit easier you can probably get away<00:34:05.610> with<00:34:05.970> like<00:34:07.100> with<00:34:08.100> just<00:34:08.310> like<00:34:08.429> a<00:34:08.460> mobile 00:34:08.750 --> 00:34:08.760 align:start position:0% away with like with just like a mobile 00:34:08.760 --> 00:34:11.450 align:start position:0% away with like with just like a mobile phone<00:34:09.110> or<00:34:10.110> a<00:34:10.140> tablet<00:34:10.200> you<00:34:10.830> know<00:34:10.950> kind<00:34:11.159> of<00:34:11.190> doing 00:34:11.450 --> 00:34:11.460 align:start position:0% phone or a tablet you know kind of doing 00:34:11.460 --> 00:34:14.300 align:start position:0% phone or a tablet you know kind of doing that<00:34:11.669> and<00:34:12.630> in<00:34:12.960> against<00:34:13.320> city<00:34:13.710> or<00:34:13.980> in<00:34:14.100> a<00:34:14.159> much 00:34:14.300 --> 00:34:14.310 align:start position:0% that and in against city or in a much 00:34:14.310 --> 00:34:17.270 align:start position:0% that and in against city or in a much more<00:34:14.460> dense<00:34:14.669> area<00:34:15.000> let's<00:34:15.330> say<00:34:16.010> let's<00:34:17.010> use<00:34:17.070> the 00:34:17.270 --> 00:34:17.280 align:start position:0% more dense area let's say let's use the 00:34:17.280 --> 00:34:18.740 align:start position:0% more dense area let's say let's use the protest<00:34:17.700> fine<00:34:17.880> then<00:34:18.030> right<00:34:18.179> like<00:34:18.360> a<00:34:18.390> protest 00:34:18.740 --> 00:34:18.750 align:start position:0% protest fine then right like a protest 00:34:18.750 --> 00:34:20.450 align:start position:0% protest fine then right like a protest that<00:34:18.990> goes<00:34:19.140> on<00:34:19.380> we<00:34:19.919> have<00:34:20.040> like<00:34:20.190> a<00:34:20.220> lot<00:34:20.399> of 00:34:20.450 --> 00:34:20.460 align:start position:0% that goes on we have like a lot of 00:34:20.460 --> 00:34:22.760 align:start position:0% that goes on we have like a lot of people<00:34:20.790> are<00:34:20.850> running<00:34:20.909> around<00:34:21.149> ideally<00:34:21.960> what 00:34:22.760 --> 00:34:22.770 align:start position:0% people are running around ideally what 00:34:22.770 --> 00:34:25.940 align:start position:0% people are running around ideally what you<00:34:22.890> could<00:34:23.130> do<00:34:23.340> in<00:34:23.640> those<00:34:23.730> situations<00:34:24.000> is<00:34:24.950> kind 00:34:25.940 --> 00:34:25.950 align:start position:0% you could do in those situations is kind 00:34:25.950 --> 00:34:28.370 align:start position:0% you could do in those situations is kind of<00:34:25.980> set<00:34:26.190> up<00:34:26.280> like<00:34:26.460> actual<00:34:27.240> devices<00:34:27.540> that<00:34:28.260> are 00:34:28.370 --> 00:34:28.380 align:start position:0% of set up like actual devices that are 00:34:28.380 --> 00:34:31.190 align:start position:0% of set up like actual devices that are meant<00:34:28.649> to<00:34:28.770> be<00:34:28.950> real<00:34:29.280> layers<00:34:29.870> it<00:34:30.870> could<00:34:31.020> be<00:34:31.110> as 00:34:31.190 --> 00:34:31.200 align:start position:0% meant to be real layers it could be as 00:34:31.200 --> 00:34:32.690 align:start position:0% meant to be real layers it could be as simple<00:34:31.320> as<00:34:31.530> like<00:34:31.560> you<00:34:31.950> know<00:34:31.980> battery<00:34:32.370> packs<00:34:32.550> in 00:34:32.690 --> 00:34:32.700 align:start position:0% simple as like you know battery packs in 00:34:32.700 --> 00:34:35.000 align:start position:0% simple as like you know battery packs in a<00:34:32.730> backpack<00:34:32.909> and<00:34:33.149> like<00:34:33.480> very<00:34:34.110> powerful 00:34:35.000 --> 00:34:35.010 align:start position:0% a backpack and like very powerful 00:34:35.010 --> 00:34:38.240 align:start position:0% a backpack and like very powerful computer<00:34:35.760> running<00:34:36.179> in<00:34:36.300> their<00:34:36.950> real<00:34:37.950> areas 00:34:38.240 --> 00:34:38.250 align:start position:0% computer running in their real areas 00:34:38.250 --> 00:34:40.550 align:start position:0% computer running in their real areas that<00:34:38.610> are<00:34:39.179> intended<00:34:39.600> for<00:34:39.720> dense<00:34:40.020> areas<00:34:40.260> should 00:34:40.550 --> 00:34:40.560 align:start position:0% that are intended for dense areas should 00:34:40.560 --> 00:34:43.130 align:start position:0% that are intended for dense areas should not<00:34:40.620> be<00:34:40.980> a<00:34:41.520> phone<00:34:41.730> they<00:34:42.360> should<00:34:42.600> be<00:34:42.750> something 00:34:43.130 --> 00:34:43.140 align:start position:0% not be a phone they should be something 00:34:43.140 --> 00:34:45.800 align:start position:0% not be a phone they should be something that<00:34:43.169> you<00:34:43.649> know<00:34:44.070> can<00:34:44.310> actively<00:34:44.730> take<00:34:45.480> a 00:34:45.800 --> 00:34:45.810 align:start position:0% that you know can actively take a 00:34:45.810 --> 00:34:47.810 align:start position:0% that you know can actively take a beating<00:34:46.590> and<00:34:46.800> are<00:34:47.040> expected<00:34:47.490> to<00:34:47.610> take<00:34:47.760> a 00:34:47.810 --> 00:34:47.820 align:start position:0% beating and are expected to take a 00:34:47.820 --> 00:34:49.490 align:start position:0% beating and are expected to take a meeting<00:34:48.000> so<00:34:48.330> you<00:34:48.360> can<00:34:48.659> get<00:34:48.929> the<00:34:49.020> throughput<00:34:49.380> we 00:34:49.490 --> 00:34:49.500 align:start position:0% meeting so you can get the throughput we 00:34:49.500 --> 00:34:53.149 align:start position:0% meeting so you can get the throughput we need<00:34:50.000> and<00:34:51.000> again<00:34:51.300> it's<00:34:51.570> like<00:34:51.830> specific<00:34:52.830> it's 00:34:53.149 --> 00:34:53.159 align:start position:0% need and again it's like specific it's 00:34:53.159 --> 00:34:59.150 align:start position:0% need and again it's like specific it's for<00:34:53.340> the<00:34:53.399> specifics<00:34:57.140> to<00:34:58.140> say<00:34:58.350> I<00:34:58.710> want<00:34:59.100> to 00:34:59.150 --> 00:34:59.160 align:start position:0% for the specifics to say I want to 00:34:59.160 --> 00:35:01.040 align:start position:0% for the specifics to say I want to contribute<00:34:59.370> to<00:34:59.550> this<00:34:59.730> like<00:34:59.970> you<00:35:00.540> do<00:35:00.690> have<00:35:00.900> the 00:35:01.040 --> 00:35:01.050 align:start position:0% contribute to this like you do have the 00:35:01.050 --> 00:35:02.450 align:start position:0% contribute to this like you do have the kind<00:35:01.290> of<00:35:01.320> capacity<00:35:01.470> attached<00:35:02.070> to<00:35:02.250> it<00:35:02.370> which 00:35:02.450 --> 00:35:02.460 align:start position:0% kind of capacity attached to it which 00:35:02.460 --> 00:35:04.990 align:start position:0% kind of capacity attached to it which allows<00:35:02.550> for<00:35:02.790> the<00:35:03.000> data<00:35:03.210> any<00:35:03.510> sort<00:35:03.750> of<00:35:03.780> yeah 00:35:04.990 --> 00:35:05.000 align:start position:0% allows for the data any sort of yeah 00:35:05.000 --> 00:35:08.870 align:start position:0% allows for the data any sort of yeah yeah<00:35:06.290> yeah<00:35:07.290> exactly<00:35:07.560> so<00:35:07.950> the<00:35:08.160> beauty<00:35:08.460> the 00:35:08.870 --> 00:35:08.880 align:start position:0% yeah yeah exactly so the beauty the 00:35:08.880 --> 00:35:11.120 align:start position:0% yeah yeah exactly so the beauty the beauty<00:35:08.910> of<00:35:09.180> all<00:35:09.360> this<00:35:09.480> is<00:35:09.660> that<00:35:09.690> you<00:35:10.320> can 00:35:11.120 --> 00:35:11.130 align:start position:0% beauty of all this is that you can 00:35:11.130 --> 00:35:13.130 align:start position:0% beauty of all this is that you can choose<00:35:11.370> which<00:35:11.430> services<00:35:12.180> transports<00:35:12.900> want<00:35:13.080> to 00:35:13.130 --> 00:35:13.140 align:start position:0% choose which services transports want to 00:35:13.140 --> 00:35:15.080 align:start position:0% choose which services transports want to use<00:35:13.230> you<00:35:13.440> can<00:35:13.590> choose<00:35:13.770> Bluetooth<00:35:14.130> Wi-Fi<00:35:14.280> you 00:35:15.080 --> 00:35:15.090 align:start position:0% use you can choose Bluetooth Wi-Fi you 00:35:15.090 --> 00:35:17.120 align:start position:0% use you can choose Bluetooth Wi-Fi you can<00:35:15.210> also<00:35:15.360> choose<00:35:15.660> what<00:35:16.170> type<00:35:16.440> of<00:35:16.500> a<00:35:16.950> node 00:35:17.120 --> 00:35:17.130 align:start position:0% can also choose what type of a node 00:35:17.130 --> 00:35:19.340 align:start position:0% can also choose what type of a node you're<00:35:17.280> running<00:35:17.990> obviously<00:35:18.990> in 00:35:19.340 --> 00:35:19.350 align:start position:0% you're running obviously in 00:35:19.350 --> 00:35:20.660 align:start position:0% you're running obviously in centralization<00:35:19.920> laws<00:35:20.070> would<00:35:20.190> be<00:35:20.220> cool<00:35:20.490> to 00:35:20.660 --> 00:35:20.670 align:start position:0% centralization laws would be cool to 00:35:20.670 --> 00:35:22.780 align:start position:0% centralization laws would be cool to like<00:35:20.850> you<00:35:21.120> know 00:35:22.780 --> 00:35:22.790 align:start position:0% like you know 00:35:22.790 --> 00:35:25.060 align:start position:0% like you know Constance<00:35:23.630> is<00:35:23.720> like<00:35:23.900> more<00:35:24.170> of<00:35:24.200> like<00:35:24.290> a<00:35:24.410> as<00:35:25.040> a 00:35:25.060 --> 00:35:25.070 align:start position:0% Constance is like more of like a as a 00:35:25.070 --> 00:35:27.610 align:start position:0% Constance is like more of like a as a goodwill<00:35:25.340> it's<00:35:26.120> like<00:35:26.240> a<00:35:26.320> public<00:35:27.320> good<00:35:27.470> like 00:35:27.610 --> 00:35:27.620 align:start position:0% goodwill it's like a public good like 00:35:27.620 --> 00:35:30.040 align:start position:0% goodwill it's like a public good like you<00:35:28.070> know<00:35:28.190> when<00:35:28.520> you<00:35:28.610> need<00:35:28.790> this<00:35:29.060> it<00:35:29.780> should<00:35:29.960> be 00:35:30.040 --> 00:35:30.050 align:start position:0% you know when you need this it should be 00:35:30.050 --> 00:35:31.960 align:start position:0% you know when you need this it should be used<00:35:30.290> i<00:35:30.500> don'ts<00:35:30.740> for<00:35:30.770> we<00:35:31.190> don't<00:35:31.370> it<00:35:31.880> be 00:35:31.960 --> 00:35:31.970 align:start position:0% used i don'ts for we don't it be 00:35:31.970 --> 00:35:33.460 align:start position:0% used i don'ts for we don't it be beautiful<00:35:32.420> if<00:35:32.480> this<00:35:32.630> is<00:35:32.750> like<00:35:32.960> running<00:35:33.290> all 00:35:33.460 --> 00:35:33.470 align:start position:0% beautiful if this is like running all 00:35:33.470 --> 00:35:35.800 align:start position:0% beautiful if this is like running all the<00:35:33.560> time<00:35:33.740> like<00:35:33.920> a<00:35:34.010> subway<00:35:34.190> you<00:35:34.580> know<00:35:34.700> but<00:35:35.660> in 00:35:35.800 --> 00:35:35.810 align:start position:0% the time like a subway you know but in 00:35:35.810 --> 00:35:38.410 align:start position:0% the time like a subway you know but in ideal<00:35:36.470> ideally<00:35:37.130> and<00:35:37.490> realistically<00:35:38.210> speaking 00:35:38.410 --> 00:35:38.420 align:start position:0% ideal ideally and realistically speaking 00:35:38.420 --> 00:35:39.910 align:start position:0% ideal ideally and realistically speaking this<00:35:38.900> is<00:35:39.020> something<00:35:39.320> that<00:35:39.350> should<00:35:39.590> be<00:35:39.650> using 00:35:39.910 --> 00:35:39.920 align:start position:0% this is something that should be using 00:35:39.920 --> 00:35:44.620 align:start position:0% this is something that should be using like<00:35:40.610> very<00:35:41.890> for<00:35:42.890> the<00:35:43.250> use<00:35:43.430> cases<00:35:43.640> and<00:35:44.450> like 00:35:44.620 --> 00:35:44.630 align:start position:0% like very for the use cases and like 00:35:44.630 --> 00:35:47.230 align:start position:0% like very for the use cases and like concerts<00:35:45.080> and<00:35:45.260> whatnot<00:35:45.820> to<00:35:46.820> which<00:35:47.000> like 00:35:47.230 --> 00:35:47.240 align:start position:0% concerts and whatnot to which like 00:35:47.240 --> 00:35:49.270 align:start position:0% concerts and whatnot to which like people<00:35:47.600> are<00:35:47.930> going<00:35:48.110> in<00:35:48.410> understanding<00:35:49.160> the 00:35:49.270 --> 00:35:49.280 align:start position:0% people are going in understanding the 00:35:49.280 --> 00:35:50.830 align:start position:0% people are going in understanding the conditions<00:35:49.730> and<00:35:50.030> like<00:35:50.180> knowing<00:35:50.420> what<00:35:50.630> like 00:35:50.830 --> 00:35:50.840 align:start position:0% conditions and like knowing what like 00:35:50.840 --> 00:35:53.880 align:start position:0% conditions and like knowing what like this<00:35:51.380> is<00:35:51.590> just<00:35:51.770> like<00:35:51.980> a<00:35:52.160> very<00:35:52.490> viable<00:35:52.820> way<00:35:53.150> to 00:35:53.880 --> 00:35:53.890 align:start position:0% this is just like a very viable way to 00:35:53.890 --> 00:36:11.170 align:start position:0% this is just like a very viable way to communicate<00:36:08.680> yeah<00:36:09.680> so<00:36:10.130> ideally<00:36:10.610> I<00:36:10.640> didn't 00:36:11.170 --> 00:36:11.180 align:start position:0% communicate yeah so ideally I didn't 00:36:11.180 --> 00:36:12.880 align:start position:0% communicate yeah so ideally I didn't you've<00:36:11.300> never<00:36:11.540> actually<00:36:11.750> had<00:36:12.080> a<00:36:12.110> real<00:36:12.170> ER<00:36:12.440> yeah 00:36:12.880 --> 00:36:12.890 align:start position:0% you've never actually had a real ER yeah 00:36:12.890 --> 00:36:14.470 align:start position:0% you've never actually had a real ER yeah like<00:36:13.130> given<00:36:13.490> there<00:36:13.640> would<00:36:13.790> be<00:36:13.820> enough<00:36:14.150> device 00:36:14.470 --> 00:36:14.480 align:start position:0% like given there would be enough device 00:36:14.480 --> 00:36:16.390 align:start position:0% like given there would be enough device coverage<00:36:14.900> in<00:36:15.020> a<00:36:15.110> place<00:36:15.290> like<00:36:15.320> New<00:36:15.860> York<00:36:16.190> City 00:36:16.390 --> 00:36:16.400 align:start position:0% coverage in a place like New York City 00:36:16.400 --> 00:36:17.830 align:start position:0% coverage in a place like New York City you've<00:36:16.670> never<00:36:16.940> actually<00:36:17.150> had<00:36:17.450> a<00:36:17.480> real<00:36:17.690> layer 00:36:17.830 --> 00:36:17.840 align:start position:0% you've never actually had a real layer 00:36:17.840 --> 00:36:20.860 align:start position:0% you've never actually had a real layer because<00:36:18.080> you<00:36:18.200> would<00:36:18.350> just<00:36:18.380> halt<00:36:18.830> until<00:36:19.870> the 00:36:20.860 --> 00:36:20.870 align:start position:0% because you would just halt until the 00:36:20.870 --> 00:36:22.720 align:start position:0% because you would just halt until the destination<00:36:21.440> was<00:36:21.590> found<00:36:21.860> that's<00:36:22.310> also 00:36:22.720 --> 00:36:22.730 align:start position:0% destination was found that's also 00:36:22.730 --> 00:36:24.850 align:start position:0% destination was found that's also something<00:36:22.940> that<00:36:23.090> like<00:36:23.480> guess<00:36:24.020> I<00:36:24.200> glossed<00:36:24.650> over 00:36:24.850 --> 00:36:24.860 align:start position:0% something that like guess I glossed over 00:36:24.860 --> 00:36:26.980 align:start position:0% something that like guess I glossed over and<00:36:25.160> plank<00:36:25.400> you<00:36:26.000> don't<00:36:26.180> actually<00:36:26.330> need<00:36:26.720> ever 00:36:26.980 --> 00:36:26.990 align:start position:0% and plank you don't actually need ever 00:36:26.990 --> 00:36:29.320 align:start position:0% and plank you don't actually need ever eat<00:36:27.230> the<00:36:27.380> internet<00:36:27.650> in<00:36:27.800> these<00:36:27.920> use<00:36:28.100> cases<00:36:28.330> we 00:36:29.320 --> 00:36:29.330 align:start position:0% eat the internet in these use cases we 00:36:29.330 --> 00:36:30.820 align:start position:0% eat the internet in these use cases we always<00:36:29.660> say<00:36:29.810> the<00:36:29.960> internet<00:36:30.260> so<00:36:30.440> that<00:36:30.470> it's 00:36:30.820 --> 00:36:30.830 align:start position:0% always say the internet so that it's 00:36:30.830 --> 00:36:33.880 align:start position:0% always say the internet so that it's like<00:36:30.950> way<00:36:31.580> like<00:36:31.940> your<00:36:32.390> phone<00:36:32.630> connected<00:36:33.500> can 00:36:33.880 --> 00:36:33.890 align:start position:0% like way like your phone connected can 00:36:33.890 --> 00:36:36.220 align:start position:0% like way like your phone connected can talk<00:36:34.100> to<00:36:34.280> people<00:36:34.400> but<00:36:34.790> in<00:36:34.970> reality<00:36:35.210> as<00:36:35.990> Dean 00:36:36.220 --> 00:36:36.230 align:start position:0% talk to people but in reality as Dean 00:36:36.230 --> 00:36:38.890 align:start position:0% talk to people but in reality as Dean says<00:36:36.470> if<00:36:37.120> like<00:36:38.120> at<00:36:38.270> a<00:36:38.300> concert<00:36:38.630> you<00:36:38.720> just 00:36:38.890 --> 00:36:38.900 align:start position:0% says if like at a concert you just 00:36:38.900 --> 00:36:40.120 align:start position:0% says if like at a concert you just trying<00:36:39.020> to<00:36:39.110> coordinate<00:36:39.230> like<00:36:39.590> where<00:36:39.740> you<00:36:39.860> sit 00:36:40.120 --> 00:36:40.130 align:start position:0% trying to coordinate like where you sit 00:36:40.130 --> 00:36:42.160 align:start position:0% trying to coordinate like where you sit where<00:36:40.340> you're<00:36:40.430> standing<00:36:40.910> right<00:36:41.660> and<00:36:42.050> like 00:36:42.160 --> 00:36:42.170 align:start position:0% where you're standing right and like 00:36:42.170 --> 00:36:43.540 align:start position:0% where you're standing right and like that's<00:36:42.350> what's<00:36:42.770> really<00:36:42.980> powerful<00:36:43.220> is<00:36:43.520> that 00:36:43.540 --> 00:36:43.550 align:start position:0% that's what's really powerful is that 00:36:43.550 --> 00:36:46.090 align:start position:0% that's what's really powerful is that you<00:36:43.760> can<00:36:43.940> say<00:36:44.210> like<00:36:44.480> where<00:36:44.780> you<00:36:44.930> are<00:36:45.110> kind<00:36:45.980> of 00:36:46.090 --> 00:36:46.100 align:start position:0% you can say like where you are kind of 00:36:46.100 --> 00:36:47.740 align:start position:0% you can say like where you are kind of like<00:36:46.250> the<00:36:46.370> same<00:36:46.520> thing<00:36:46.580> with<00:36:46.910> like<00:36:47.090> you<00:36:47.630> know 00:36:47.740 --> 00:36:47.750 align:start position:0% like the same thing with like you know 00:36:47.750 --> 00:36:49.810 align:start position:0% like the same thing with like you know live<00:36:48.500> protests<00:36:49.070> or<00:36:49.160> whatever<00:36:49.370> you<00:36:49.490> can<00:36:49.670> like 00:36:49.810 --> 00:36:49.820 align:start position:0% live protests or whatever you can like 00:36:49.820 --> 00:36:51.640 align:start position:0% live protests or whatever you can like it's<00:36:50.120> a<00:36:50.240> lot<00:36:50.420> easier<00:36:50.660> to<00:36:51.080> coordinate<00:36:51.260> where 00:36:51.640 --> 00:36:51.650 align:start position:0% it's a lot easier to coordinate where 00:36:51.650 --> 00:36:52.540 align:start position:0% it's a lot easier to coordinate where you<00:36:51.740> are<00:36:51.890> when<00:36:52.070> there's<00:36:52.220> like<00:36:52.340> a<00:36:52.400> million 00:36:52.540 --> 00:36:52.550 align:start position:0% you are when there's like a million 00:36:52.550 --> 00:36:55.060 align:start position:0% you are when there's like a million people<00:36:53.110> you<00:36:54.110> know<00:36:54.200> on<00:36:54.260> the<00:36:54.350> Raptors<00:36:54.530> won<00:36:54.920> the 00:36:55.060 --> 00:36:55.070 align:start position:0% people you know on the Raptors won the 00:36:55.070 --> 00:36:58.330 align:start position:0% people you know on the Raptors won the NBA<00:36:55.670> title<00:36:55.760> I<00:36:56.630> was<00:36:57.140> trapped<00:36:57.590> in<00:36:57.770> the<00:36:58.100> streets 00:36:58.330 --> 00:36:58.340 align:start position:0% NBA title I was trapped in the streets 00:36:58.340 --> 00:37:00.610 align:start position:0% NBA title I was trapped in the streets of<00:36:58.400> Toronto<00:36:58.520> and<00:36:59.000> literally<00:36:59.960> did<00:37:00.410> not<00:37:00.440> know 00:37:00.610 --> 00:37:00.620 align:start position:0% of Toronto and literally did not know 00:37:00.620 --> 00:37:03.910 align:start position:0% of Toronto and literally did not know where<00:37:00.740> my<00:37:00.920> friends<00:37:01.220> were<00:37:02.140> it<00:37:03.140> was<00:37:03.380> awful<00:37:03.710> and 00:37:03.910 --> 00:37:03.920 align:start position:0% where my friends were it was awful and 00:37:03.920 --> 00:37:05.890 align:start position:0% where my friends were it was awful and like<00:37:04.730> that's<00:37:04.880> kind<00:37:05.180> of<00:37:05.210> like<00:37:05.300> where<00:37:05.630> the<00:37:05.750> use 00:37:05.890 --> 00:37:05.900 align:start position:0% like that's kind of like where the use 00:37:05.900 --> 00:37:07.510 align:start position:0% like that's kind of like where the use of<00:37:06.050> days<00:37:06.170> like<00:37:06.410> this<00:37:06.560> becomes<00:37:07.010> very<00:37:07.250> powerful 00:37:07.510 --> 00:37:07.520 align:start position:0% of days like this becomes very powerful 00:37:07.520 --> 00:37:09.010 align:start position:0% of days like this becomes very powerful and<00:37:07.820> that's<00:37:07.880> why<00:37:08.060> I<00:37:08.090> say<00:37:08.270> it's<00:37:08.390> very<00:37:08.540> like<00:37:08.870> you 00:37:09.010 --> 00:37:09.020 align:start position:0% and that's why I say it's very like you 00:37:09.020 --> 00:37:10.650 align:start position:0% and that's why I say it's very like you stay<00:37:09.200> specific<00:37:09.770> I<00:37:09.890> don't<00:37:10.160> think 00:37:10.650 --> 00:37:10.660 align:start position:0% stay specific I don't think 00:37:10.660 --> 00:37:13.289 align:start position:0% stay specific I don't think should<00:37:10.869> be<00:37:10.930> like<00:37:11.079> widely<00:37:11.680> deployed<00:37:12.299> 24/7 00:37:13.289 --> 00:37:13.299 align:start position:0% should be like widely deployed 24/7 00:37:13.299 --> 00:37:16.079 align:start position:0% should be like widely deployed 24/7 rather<00:37:13.599> like<00:37:13.960> deployed<00:37:14.410> agree<00:37:14.740> on<00:37:15.700> a<00:37:15.759> location 00:37:16.079 --> 00:37:16.089 align:start position:0% rather like deployed agree on a location 00:37:16.089 --> 00:37:19.589 align:start position:0% rather like deployed agree on a location missus<00:37:17.700> you<00:37:18.700> guys<00:37:18.849> have<00:37:19.000> any<00:37:19.150> sort<00:37:19.420> of<00:37:19.450> like 00:37:19.589 --> 00:37:19.599 align:start position:0% missus you guys have any sort of like 00:37:19.599 --> 00:37:21.809 align:start position:0% missus you guys have any sort of like countless<00:37:20.440> mechanism<00:37:20.920> besides<00:37:21.339> like<00:37:21.579> I<00:37:21.609> guess 00:37:21.809 --> 00:37:21.819 align:start position:0% countless mechanism besides like I guess 00:37:21.819 --> 00:37:23.549 align:start position:0% countless mechanism besides like I guess what<00:37:22.000> really<00:37:22.299> Bluetooth<00:37:22.839> Low<00:37:23.049> Energy<00:37:23.079> hack 00:37:23.549 --> 00:37:23.559 align:start position:0% what really Bluetooth Low Energy hack 00:37:23.559 --> 00:37:26.279 align:start position:0% what really Bluetooth Low Energy hack the<00:37:24.369> device<00:37:24.670> right<00:37:25.210> it's<00:37:25.390> like<00:37:25.569> basically<00:37:26.170> the 00:37:26.279 --> 00:37:26.289 align:start position:0% the device right it's like basically the 00:37:26.289 --> 00:37:27.749 align:start position:0% the device right it's like basically the biggest<00:37:26.500> I<00:37:26.650> think<00:37:26.680> not<00:37:26.980> troll<00:37:27.279> box<00:37:27.490> right 00:37:27.749 --> 00:37:27.759 align:start position:0% biggest I think not troll box right 00:37:27.759 --> 00:37:28.950 align:start position:0% biggest I think not troll box right because<00:37:28.000> like<00:37:28.119> if<00:37:28.240> I'm<00:37:28.329> at<00:37:28.420> a<00:37:28.450> concert<00:37:28.900> a 00:37:28.950 --> 00:37:28.960 align:start position:0% because like if I'm at a concert a 00:37:28.960 --> 00:37:31.019 align:start position:0% because like if I'm at a concert a million<00:37:29.710> message<00:37:29.980> going<00:37:30.160> from<00:37:30.430> filter<00:37:30.730> flying 00:37:31.019 --> 00:37:31.029 align:start position:0% million message going from filter flying 00:37:31.029 --> 00:37:43.460 align:start position:0% million message going from filter flying than<00:37:31.269> my<00:37:31.359> friends<00:37:38.400> just<00:37:40.230> know<00:37:41.230> because<00:37:42.180> so 00:37:43.460 --> 00:37:43.470 align:start position:0% than my friends just know because so 00:37:43.470 --> 00:37:46.470 align:start position:0% than my friends just know because so Bluetooth<00:37:44.470> Mac's<00:37:44.710> often<00:37:45.670> aren't<00:37:45.880> exposed<00:37:46.180> by 00:37:46.470 --> 00:37:46.480 align:start position:0% Bluetooth Mac's often aren't exposed by 00:37:46.480 --> 00:37:49.140 align:start position:0% Bluetooth Mac's often aren't exposed by high<00:37:46.720> level<00:37:47.200> in<00:37:47.470> the<00:37:47.589> eyes<00:37:47.970> because<00:37:48.970> of 00:37:49.140 --> 00:37:49.150 align:start position:0% high level in the eyes because of 00:37:49.150 --> 00:37:51.539 align:start position:0% high level in the eyes because of security<00:37:49.509> reasons<00:37:49.690> so<00:37:50.230> what<00:37:51.099> ends<00:37:51.430> up<00:37:51.490> being 00:37:51.539 --> 00:37:51.549 align:start position:0% security reasons so what ends up being 00:37:51.549 --> 00:37:54.359 align:start position:0% security reasons so what ends up being exposed<00:37:52.150> as<00:37:52.450> a<00:37:52.539> UUID<00:37:52.869> that<00:37:53.380> has<00:37:53.559> changed<00:37:54.099> for 00:37:54.359 --> 00:37:54.369 align:start position:0% exposed as a UUID that has changed for 00:37:54.369 --> 00:37:55.109 align:start position:0% exposed as a UUID that has changed for every<00:37:54.670> device 00:37:55.109 --> 00:37:55.119 align:start position:0% every device 00:37:55.119 --> 00:37:57.120 align:start position:0% every device so<00:37:55.210> there's<00:37:55.420> devices<00:37:56.380> have<00:37:56.529> a<00:37:56.559> public<00:37:56.950> key 00:37:57.120 --> 00:37:57.130 align:start position:0% so there's devices have a public key 00:37:57.130 --> 00:38:00.180 align:start position:0% so there's devices have a public key probably<00:37:57.490> kind<00:37:57.910> of<00:37:57.970> played<00:37:58.240> live<00:37:58.539> p2p<00:37:58.990> so<00:37:59.619> you 00:38:00.180 --> 00:38:00.190 align:start position:0% probably kind of played live p2p so you 00:38:00.190 --> 00:38:02.730 align:start position:0% probably kind of played live p2p so you have<00:38:00.339> an<00:38:00.430> identity<00:38:00.849> that<00:38:01.059> can<00:38:01.119> be<00:38:01.329> found<00:38:01.569> on<00:38:01.869> X 00:38:02.730 --> 00:38:02.740 align:start position:0% have an identity that can be found on X 00:38:02.740 --> 00:38:08.940 align:start position:0% have an identity that can be found on X transpose<00:38:04.799> okay<00:38:05.829> the<00:38:06.369> UID<00:38:07.359> can<00:38:07.720> be<00:38:07.869> set<00:38:08.259> so 00:38:08.940 --> 00:38:08.950 align:start position:0% transpose okay the UID can be set so 00:38:08.950 --> 00:38:10.980 align:start position:0% transpose okay the UID can be set so it's<00:38:09.220> you<00:38:09.970> know<00:38:10.059> the<00:38:10.089> public/private<00:38:10.869> key 00:38:10.980 --> 00:38:10.990 align:start position:0% it's you know the public/private key 00:38:10.990 --> 00:38:15.569 align:start position:0% it's you know the public/private key cops<00:38:11.230> yeah<00:38:13.619> is<00:38:14.619> there<00:38:14.740> any<00:38:14.920> information<00:38:15.039> like 00:38:15.569 --> 00:38:15.579 align:start position:0% cops yeah is there any information like 00:38:15.579 --> 00:38:17.940 align:start position:0% cops yeah is there any information like your<00:38:15.789> the<00:38:15.970> tendinous<00:38:16.420> Indian<00:38:16.809> your<00:38:17.650> example 00:38:17.940 --> 00:38:17.950 align:start position:0% your the tendinous Indian your example 00:38:17.950 --> 00:38:20.130 align:start position:0% your the tendinous Indian your example about<00:38:17.980> the<00:38:18.220> Raptors<00:38:18.789> downtown<00:38:19.630> trying<00:38:20.079> to 00:38:20.130 --> 00:38:20.140 align:start position:0% about the Raptors downtown trying to 00:38:20.140 --> 00:38:21.029 align:start position:0% about the Raptors downtown trying to find<00:38:20.289> somebody<00:38:20.470> else<00:38:20.619> is<00:38:20.829> there<00:38:20.950> any 00:38:21.029 --> 00:38:21.039 align:start position:0% find somebody else is there any 00:38:21.039 --> 00:38:22.200 align:start position:0% find somebody else is there any information<00:38:21.160> about<00:38:21.640> when<00:38:21.880> you<00:38:21.940> receive<00:38:22.180> a 00:38:22.200 --> 00:38:22.210 align:start position:0% information about when you receive a 00:38:22.210 --> 00:38:24.120 align:start position:0% information about when you receive a message<00:38:22.390> which<00:38:23.109> direction<00:38:23.529> that<00:38:23.769> that<00:38:23.920> came 00:38:24.120 --> 00:38:24.130 align:start position:0% message which direction that that came 00:38:24.130 --> 00:38:25.529 align:start position:0% message which direction that that came from<00:38:24.279> you<00:38:24.670> could<00:38:24.789> potentially<00:38:24.970> use<00:38:25.210> this<00:38:25.359> for 00:38:25.529 --> 00:38:25.539 align:start position:0% from you could potentially use this for 00:38:25.539 --> 00:38:27.540 align:start position:0% from you could potentially use this for about<00:38:25.630> our<00:38:25.900> quarter<00:38:26.380> naive 00:38:27.540 --> 00:38:27.550 align:start position:0% about our quarter naive 00:38:27.550 --> 00:38:29.340 align:start position:0% about our quarter naive friends<00:38:28.210> aren't<00:38:28.300> saying<00:38:28.540> here's<00:38:29.110> what<00:38:29.260> we 00:38:29.340 --> 00:38:29.350 align:start position:0% friends aren't saying here's what we 00:38:29.350 --> 00:38:30.900 align:start position:0% friends aren't saying here's what we oughta<00:38:29.530> size<00:38:29.830> you're<00:38:30.100> trying<00:38:30.490> to<00:38:30.550> get<00:38:30.700> to 00:38:30.900 --> 00:38:30.910 align:start position:0% oughta size you're trying to get to 00:38:30.910 --> 00:38:32.460 align:start position:0% oughta size you're trying to get to where<00:38:31.030> that<00:38:31.210> message<00:38:31.480> initiated<00:38:32.020> physically 00:38:32.460 --> 00:38:32.470 align:start position:0% where that message initiated physically 00:38:32.470 --> 00:38:34.560 align:start position:0% where that message initiated physically because<00:38:32.800> of<00:38:32.890> all<00:38:33.010> these<00:38:33.220> like<00:38:33.400> yes<00:38:34.300> uh<00:38:34.510> the 00:38:34.560 --> 00:38:34.570 align:start position:0% because of all these like yes uh the 00:38:34.570 --> 00:38:37.080 align:start position:0% because of all these like yes uh the inferior<00:38:35.140> yeah<00:38:35.710> if<00:38:35.950> you<00:38:36.160> can<00:38:36.520> do<00:38:36.640> that<00:38:36.820> because 00:38:37.080 --> 00:38:37.090 align:start position:0% inferior yeah if you can do that because 00:38:37.090 --> 00:38:40.140 align:start position:0% inferior yeah if you can do that because a<00:38:37.810> group<00:38:38.770> of<00:38:38.980> people<00:38:39.130> I<00:38:39.610> think<00:38:39.790> there's<00:38:40.000> two 00:38:40.140 --> 00:38:40.150 align:start position:0% a group of people I think there's two 00:38:40.150 --> 00:38:41.280 align:start position:0% a group of people I think there's two separate<00:38:40.420> groups<00:38:40.600> of<00:38:40.720> people<00:38:40.840> one<00:38:41.110> at 00:38:41.280 --> 00:38:41.290 align:start position:0% separate groups of people one at 00:38:41.290 --> 00:38:42.330 align:start position:0% separate groups of people one at university<00:38:41.860> one<00:38:41.950> of<00:38:42.040> the<00:38:42.100> one<00:38:42.220> of<00:38:42.250> the 00:38:42.330 --> 00:38:42.340 align:start position:0% university one of the one of the 00:38:42.340 --> 00:38:44.730 align:start position:0% university one of the one of the University<00:38:42.730> of<00:38:42.760> Toronto<00:38:43.200> where<00:38:44.200> they<00:38:44.680> were 00:38:44.730 --> 00:38:44.740 align:start position:0% University of Toronto where they were 00:38:44.740 --> 00:38:47.250 align:start position:0% University of Toronto where they were actually<00:38:45.250> they're<00:38:45.370> able<00:38:45.490> to<00:38:45.930> steer<00:38:46.930> ethically 00:38:47.250 --> 00:38:47.260 align:start position:0% actually they're able to steer ethically 00:38:47.260 --> 00:38:51.510 align:start position:0% actually they're able to steer ethically possible<00:38:49.740> where<00:38:50.740> they<00:38:51.010> were<00:38:51.070> able<00:38:51.490> to 00:38:51.510 --> 00:38:51.520 align:start position:0% possible where they were able to 00:38:51.520 --> 00:38:57.240 align:start position:0% possible where they were able to actually<00:38:52.860> do<00:38:53.860> in<00:38:54.160> or<00:38:54.550> offline<00:38:55.150> GPS<00:38:56.250> by 00:38:57.240 --> 00:38:57.250 align:start position:0% actually do in or offline GPS by 00:38:57.250 --> 00:38:59.010 align:start position:0% actually do in or offline GPS by bouncing<00:38:57.790> off<00:38:57.910> of<00:38:57.940> Wi-Fi<00:38:58.450> and<00:38:58.660> Bluetooth 00:38:59.010 --> 00:38:59.020 align:start position:0% bouncing off of Wi-Fi and Bluetooth 00:38:59.020 --> 00:39:01.830 align:start position:0% bouncing off of Wi-Fi and Bluetooth signals<00:38:59.430> to<00:39:00.430> understand<00:39:00.880> where<00:39:01.240> they<00:39:01.480> are<00:39:01.510> in 00:39:01.830 --> 00:39:01.840 align:start position:0% signals to understand where they are in 00:39:01.840 --> 00:39:04.350 align:start position:0% signals to understand where they are in proximity<00:39:02.050> to<00:39:02.440> the<00:39:02.740> building<00:39:03.210> so<00:39:04.210> it's 00:39:04.350 --> 00:39:04.360 align:start position:0% proximity to the building so it's 00:39:04.360 --> 00:39:06.720 align:start position:0% proximity to the building so it's definitely<00:39:04.690> possible<00:39:05.130> and<00:39:06.130> I<00:39:06.250> do<00:39:06.310> know<00:39:06.700> that 00:39:06.720 --> 00:39:06.730 align:start position:0% definitely possible and I do know that 00:39:06.730 --> 00:39:09.690 align:start position:0% definitely possible and I do know that you<00:39:07.180> do<00:39:07.390> have<00:39:07.570> access<00:39:07.750> to<00:39:08.050> the<00:39:08.320> range<00:39:08.620> and<00:39:08.920> vo<00:39:09.400> - 00:39:09.690 --> 00:39:09.700 align:start position:0% you do have access to the range and vo - 00:39:09.700 --> 00:39:13.110 align:start position:0% you do have access to the range and vo - yeah<00:39:10.270> I<00:39:10.690> don't<00:39:10.840> know<00:39:11.160> yeah<00:39:12.160> yeah<00:39:12.640> you<00:39:12.970> know<00:39:13.060> if 00:39:13.110 --> 00:39:13.120 align:start position:0% yeah I don't know yeah yeah you know if 00:39:13.120 --> 00:39:14.580 align:start position:0% yeah I don't know yeah yeah you know if you<00:39:13.240> give<00:39:13.360> some<00:39:13.600> sort<00:39:13.840> of<00:39:13.930> bounces<00:39:14.260> something 00:39:14.580 --> 00:39:14.590 align:start position:0% you give some sort of bounces something 00:39:14.590 --> 00:39:17.600 align:start position:0% you give some sort of bounces something so<00:39:14.740> you<00:39:14.860> can<00:39:15.060> it<00:39:16.060> would<00:39:16.180> have<00:39:16.270> a<00:39:16.360> size<00:39:16.540> range 00:39:17.600 --> 00:39:17.610 align:start position:0% so you can it would have a size range 00:39:17.610 --> 00:39:19.860 align:start position:0% so you can it would have a size range yes<00:39:18.610> si<00:39:18.880> equal<00:39:19.000> zero<00:39:19.360> strength 00:39:19.860 --> 00:39:19.870 align:start position:0% yes si equal zero strength 00:39:19.870 --> 00:39:21.660 align:start position:0% yes si equal zero strength yeah<00:39:20.110> but<00:39:20.440> you<00:39:20.500> have<00:39:20.710> to<00:39:20.740> do<00:39:20.980> some<00:39:21.190> like<00:39:21.370> pretty 00:39:21.660 --> 00:39:21.670 align:start position:0% yeah but you have to do some like pretty 00:39:21.670 --> 00:39:23.880 align:start position:0% yeah but you have to do some like pretty nifty<00:39:22.120> accounting<00:39:23.020> to<00:39:23.260> kind<00:39:23.500> of<00:39:23.560> like 00:39:23.880 --> 00:39:23.890 align:start position:0% nifty accounting to kind of like 00:39:23.890 --> 00:39:27.300 align:start position:0% nifty accounting to kind of like basically<00:39:25.410> you'd<00:39:26.410> have<00:39:26.530> to<00:39:26.620> like<00:39:26.770> essentially 00:39:27.300 --> 00:39:27.310 align:start position:0% basically you'd have to like essentially 00:39:27.310 --> 00:39:29.460 align:start position:0% basically you'd have to like essentially like<00:39:27.460> retranslate<00:39:28.150> the<00:39:28.300> entire<00:39:28.600> shape<00:39:29.140> right 00:39:29.460 --> 00:39:29.470 align:start position:0% like retranslate the entire shape right 00:39:29.470 --> 00:39:30.810 align:start position:0% like retranslate the entire shape right because<00:39:29.650> you'd<00:39:29.800> get<00:39:29.980> some<00:39:30.160> like<00:39:30.310> really<00:39:30.640> ugly 00:39:30.810 --> 00:39:30.820 align:start position:0% because you'd get some like really ugly 00:39:30.820 --> 00:39:33.480 align:start position:0% because you'd get some like really ugly shape<00:39:31.270> and<00:39:31.720> get<00:39:31.900> some<00:39:32.080> zigzag<00:39:32.530> and<00:39:33.190> you<00:39:33.310> have 00:39:33.480 --> 00:39:33.490 align:start position:0% shape and get some zigzag and you have 00:39:33.490 --> 00:39:35.910 align:start position:0% shape and get some zigzag and you have to<00:39:33.640> basically<00:39:33.910> find<00:39:34.540> click<00:39:34.810> there's<00:39:35.800> a 00:39:35.910 --> 00:39:35.920 align:start position:0% to basically find click there's a 00:39:35.920 --> 00:39:38.970 align:start position:0% to basically find click there's a straight<00:39:36.280> line<00:39:36.580> somewhere<00:39:37.590> along<00:39:38.590> with<00:39:38.830> those 00:39:38.970 --> 00:39:38.980 align:start position:0% straight line somewhere along with those 00:39:38.980 --> 00:39:43.080 align:start position:0% straight line somewhere along with those joggers<00:39:40.740> so<00:39:41.740> bluetooth<00:39:42.460> you're<00:39:42.760> looking<00:39:43.000> at 00:39:43.080 --> 00:39:43.090 align:start position:0% joggers so bluetooth you're looking at 00:39:43.090 --> 00:39:45.900 align:start position:0% joggers so bluetooth you're looking at with<00:39:43.210> 35<00:39:43.690> the<00:39:44.140> tops<00:39:44.620> yeah<00:39:45.160> yeah<00:39:45.520> you<00:39:45.580> only<00:39:45.730> have 00:39:45.900 --> 00:39:45.910 align:start position:0% with 35 the tops yeah yeah you only have 00:39:45.910 --> 00:39:48.090 align:start position:0% with 35 the tops yeah yeah you only have like<00:39:45.940> 35<00:39:46.330> feet<00:39:46.630> tops<00:39:46.870> you<00:39:47.110> like<00:39:47.440> realistically 00:39:48.090 --> 00:39:48.100 align:start position:0% like 35 feet tops you like realistically 00:39:48.100 --> 00:39:50.100 align:start position:0% like 35 feet tops you like realistically speaking<00:39:48.340> you<00:39:49.120> can<00:39:49.270> probably<00:39:49.480> expect<00:39:49.870> to<00:39:49.960> get 00:39:50.100 --> 00:39:50.110 align:start position:0% speaking you can probably expect to get 00:39:50.110 --> 00:39:52.770 align:start position:0% speaking you can probably expect to get like<00:39:50.320> upwards<00:39:51.220> of<00:39:51.310> like<00:39:51.340> 8<00:39:51.700> hops<00:39:51.940> like<00:39:52.300> if 00:39:52.770 --> 00:39:52.780 align:start position:0% like upwards of like 8 hops like if 00:39:52.780 --> 00:39:54.510 align:start position:0% like upwards of like 8 hops like if you're<00:39:52.930> in<00:39:53.020> like<00:39:53.170> close<00:39:53.500> together<00:39:54.160> like<00:39:54.250> this 00:39:54.510 --> 00:39:54.520 align:start position:0% you're in like close together like this 00:39:54.520 --> 00:39:55.770 align:start position:0% you're in like close together like this enough<00:39:54.790> that's<00:39:55.030> out<00:39:55.240> immunes<00:39:55.600> you<00:39:55.690> can 00:39:55.770 --> 00:39:55.780 align:start position:0% enough that's out immunes you can 00:39:55.780 --> 00:39:57.130 align:start position:0% enough that's out immunes you can probably<00:39:56.020> at<00:39:56.110> least<00:39:56.290> get<00:39:56.440> it<00:39:56.470> off 00:39:57.130 --> 00:39:57.140 align:start position:0% probably at least get it off 00:39:57.140 --> 00:40:00.400 align:start position:0% probably at least get it off see<00:39:58.010> you<00:39:58.070> like<00:39:58.600> there's<00:39:59.600> a<00:39:59.690> it's<00:40:00.110> a<00:40:00.200> lot<00:40:00.380> of 00:40:00.400 --> 00:40:00.410 align:start position:0% see you like there's a it's a lot of 00:40:00.410 --> 00:40:02.560 align:start position:0% see you like there's a it's a lot of data<00:40:00.740> to<00:40:00.890> be<00:40:01.220> also<00:40:01.490> transmitting<00:40:02.210> across<00:40:02.450> the 00:40:02.560 --> 00:40:02.570 align:start position:0% data to be also transmitting across the 00:40:02.570 --> 00:40:04.030 align:start position:0% data to be also transmitting across the wire<00:40:02.750> because<00:40:02.960> we<00:40:03.080> don't<00:40:03.230> we<00:40:03.470> don't<00:40:03.590> keep<00:40:03.800> that 00:40:04.030 --> 00:40:04.040 align:start position:0% wire because we don't we don't keep that 00:40:04.040 --> 00:40:05.710 align:start position:0% wire because we don't we don't keep that the<00:40:04.730> you<00:40:04.820> know<00:40:04.850> say<00:40:05.030> we<00:40:05.090> only<00:40:05.270> took<00:40:05.420> the<00:40:05.570> last 00:40:05.710 --> 00:40:05.720 align:start position:0% the you know say we only took the last 00:40:05.720 --> 00:40:08.200 align:start position:0% the you know say we only took the last recipient<00:40:06.260> in<00:40:06.320> the<00:40:06.410> first<00:40:06.620> one<00:40:06.820> we<00:40:07.820> could<00:40:08.000> pay 00:40:08.200 --> 00:40:08.210 align:start position:0% recipient in the first one we could pay 00:40:08.210 --> 00:40:10.930 align:start position:0% recipient in the first one we could pay you<00:40:08.240> mean<00:40:08.570> at<00:40:08.930> a<00:40:08.960> counter<00:40:09.380> to<00:40:10.220> some<00:40:10.400> degree<00:40:10.730> but 00:40:10.930 --> 00:40:10.940 align:start position:0% you mean at a counter to some degree but 00:40:10.940 --> 00:40:27.190 align:start position:0% you mean at a counter to some degree but you<00:40:11.210> know<00:40:11.390> it's<00:40:11.660> also<00:40:13.390> difficult<00:40:25.270> yeah<00:40:26.270> yeah 00:40:27.190 --> 00:40:27.200 align:start position:0% you know it's also difficult yeah yeah 00:40:27.200 --> 00:40:29.260 align:start position:0% you know it's also difficult yeah yeah for<00:40:27.470> sure<00:40:27.620> you<00:40:27.920> can<00:40:28.070> like<00:40:28.220> attach<00:40:28.850> like<00:40:29.150> a 00:40:29.260 --> 00:40:29.270 align:start position:0% for sure you can like attach like a 00:40:29.270 --> 00:40:31.330 align:start position:0% for sure you can like attach like a bunch<00:40:29.450> of<00:40:29.570> metadata<00:40:29.990> to<00:40:30.440> like<00:40:30.590> your<00:40:30.830> your 00:40:31.330 --> 00:40:31.340 align:start position:0% bunch of metadata to like your your 00:40:31.340 --> 00:40:34.030 align:start position:0% bunch of metadata to like your your packet<00:40:32.030> based<00:40:32.510> on<00:40:32.750> link<00:40:32.960> replay<00:40:33.320> the<00:40:33.650> previous 00:40:34.030 --> 00:40:34.040 align:start position:0% packet based on link replay the previous 00:40:34.040 --> 00:40:36.610 align:start position:0% packet based on link replay the previous sender<00:40:34.370> and<00:40:34.760> then<00:40:35.210> based<00:40:35.930> on<00:40:36.080> that<00:40:36.140> you<00:40:36.320> can 00:40:36.610 --> 00:40:36.620 align:start position:0% sender and then based on that you can 00:40:36.620 --> 00:40:38.500 align:start position:0% sender and then based on that you can decide<00:40:36.980> like<00:40:37.160> kind<00:40:37.640> of<00:40:37.730> which<00:40:38.090> appeared<00:40:38.420> to 00:40:38.500 --> 00:40:38.510 align:start position:0% decide like kind of which appeared to 00:40:38.510 --> 00:40:40.750 align:start position:0% decide like kind of which appeared to send<00:40:38.780> it<00:40:38.870> to<00:40:38.900> next<00:40:39.260> best<00:40:39.530> right<00:40:39.830> like<00:40:40.370> using 00:40:40.750 --> 00:40:40.760 align:start position:0% send it to next best right like using 00:40:40.760 --> 00:40:44.110 align:start position:0% send it to next best right like using like<00:40:40.880> the<00:40:40.910> our<00:40:41.210> our<00:40:41.540> SSI<00:40:41.960> example<00:40:42.530> I<00:40:43.190> guess 00:40:44.110 --> 00:40:44.120 align:start position:0% like the our our SSI example I guess 00:40:44.120 --> 00:40:46.060 align:start position:0% like the our our SSI example I guess generally<00:40:44.780> signal<00:40:45.470> strength<00:40:45.710> doesn't 00:40:46.060 --> 00:40:46.070 align:start position:0% generally signal strength doesn't 00:40:46.070 --> 00:40:48.070 align:start position:0% generally signal strength doesn't necessarily<00:40:46.790> mean<00:40:47.000> like<00:40:47.240> somebody's<00:40:47.750> brother 00:40:48.070 --> 00:40:48.080 align:start position:0% necessarily mean like somebody's brother 00:40:48.080 --> 00:40:51.280 align:start position:0% necessarily mean like somebody's brother or<00:40:48.200> not<00:40:48.320> but<00:40:49.040> I<00:40:49.310> mean<00:40:49.640> sometimes<00:40:50.030> it<00:40:50.180> does<00:40:50.360> but 00:40:51.280 --> 00:40:51.290 align:start position:0% or not but I mean sometimes it does but 00:40:51.290 --> 00:40:52.660 align:start position:0% or not but I mean sometimes it does but like<00:40:51.440> you<00:40:51.590> can<00:40:51.770> if<00:40:52.100> you<00:40:52.310> were<00:40:52.400> trying<00:40:52.640> to 00:40:52.660 --> 00:40:52.670 align:start position:0% like you can if you were trying to 00:40:52.670 --> 00:40:54.040 align:start position:0% like you can if you were trying to disseminate<00:40:53.000> information<00:40:53.240> really<00:40:53.930> quickly 00:40:54.040 --> 00:40:54.050 align:start position:0% disseminate information really quickly 00:40:54.050 --> 00:40:57.750 align:start position:0% disseminate information really quickly right<00:40:54.650> you<00:40:55.130> can<00:40:55.280> attach<00:40:55.640> like<00:40:56.120> our<00:40:56.360> SSI 00:40:57.750 --> 00:40:57.760 align:start position:0% right you can attach like our SSI 00:40:57.760 --> 00:40:59.890 align:start position:0% right you can attach like our SSI information<00:40:58.760> to<00:40:58.910> like<00:40:59.030> you're<00:40:59.180> getting<00:40:59.480> at<00:40:59.660> it 00:40:59.890 --> 00:40:59.900 align:start position:0% information to like you're getting at it 00:40:59.900 --> 00:41:02.470 align:start position:0% information to like you're getting at it and<00:41:00.110> then<00:41:00.650> you<00:41:00.920> try<00:41:01.130> you<00:41:01.550> prioritize<00:41:02.090> sending 00:41:02.470 --> 00:41:02.480 align:start position:0% and then you try you prioritize sending 00:41:02.480 --> 00:41:03.640 align:start position:0% and then you try you prioritize sending it<00:41:02.570> to<00:41:02.720> like<00:41:02.840> the<00:41:02.960> person<00:41:03.110> who's<00:41:03.380> furthest 00:41:03.640 --> 00:41:03.650 align:start position:0% it to like the person who's furthest 00:41:03.650 --> 00:41:06.130 align:start position:0% it to like the person who's furthest away<00:41:03.890> and<00:41:04.460> look<00:41:05.150> down<00:41:05.330> on<00:41:05.390> that<00:41:05.570> and<00:41:05.900> within 00:41:06.130 --> 00:41:06.140 align:start position:0% away and look down on that and within 00:41:06.140 --> 00:41:07.930 align:start position:0% away and look down on that and within that<00:41:06.500> way<00:41:06.830> you<00:41:06.890> can<00:41:07.160> like<00:41:07.340> so<00:41:07.820> much 00:41:07.930 --> 00:41:07.940 align:start position:0% that way you can like so much 00:41:07.940 --> 00:41:09.490 align:start position:0% that way you can like so much information<00:41:08.450> like<00:41:08.570> super<00:41:08.930> quickly<00:41:09.140> right 00:41:09.490 --> 00:41:09.500 align:start position:0% information like super quickly right 00:41:09.500 --> 00:41:11.530 align:start position:0% information like super quickly right because<00:41:10.190> you<00:41:10.610> know<00:41:10.640> that<00:41:10.850> guy's<00:41:11.060> far<00:41:11.330> away<00:41:11.480> so 00:41:11.530 --> 00:41:11.540 align:start position:0% because you know that guy's far away so 00:41:11.540 --> 00:41:14.800 align:start position:0% because you know that guy's far away so that<00:41:11.750> he<00:41:11.870> tries<00:41:12.230> sends<00:41:12.650> his<00:41:12.830> peers<00:41:13.810> pops 00:41:14.800 --> 00:41:14.810 align:start position:0% that he tries sends his peers pops 00:41:14.810 --> 00:41:16.069 align:start position:0% that he tries sends his peers pops Brandon 00:41:16.069 --> 00:41:16.079 align:start position:0% Brandon 00:41:16.079 --> 00:41:19.130 align:start position:0% Brandon and<00:41:16.849> you<00:41:17.849> guys<00:41:17.999> think<00:41:18.269> about<00:41:18.299> using<00:41:18.630> radio<00:41:18.989> in 00:41:19.130 --> 00:41:19.140 align:start position:0% and you guys think about using radio in 00:41:19.140 --> 00:41:21.229 align:start position:0% and you guys think about using radio in one<00:41:19.829> slide<00:41:20.069> talk<00:41:20.459> about<00:41:20.640> rabies<00:41:20.939> how<00:41:21.089> we're 00:41:21.229 --> 00:41:21.239 align:start position:0% one slide talk about rabies how we're 00:41:21.239 --> 00:41:23.150 align:start position:0% one slide talk about rabies how we're gonna<00:41:21.299> do<00:41:21.539> it<00:41:21.569> as<00:41:21.719> a<00:41:21.749> troll<00:41:22.049> transport<00:41:22.589> you 00:41:23.150 --> 00:41:23.160 align:start position:0% gonna do it as a troll transport you 00:41:23.160 --> 00:41:25.039 align:start position:0% gonna do it as a troll transport you know<00:41:23.359> someone's<00:41:24.359> working<00:41:24.660> on<00:41:24.749> it<00:41:24.869> right<00:41:25.019> now 00:41:25.039 --> 00:41:25.049 align:start position:0% know someone's working on it right now 00:41:25.049 --> 00:41:27.499 align:start position:0% know someone's working on it right now actually<00:41:25.589> control<00:41:26.219> yeah<00:41:26.969> because<00:41:27.179> it's<00:41:27.420> like 00:41:27.499 --> 00:41:27.509 align:start position:0% actually control yeah because it's like 00:41:27.509 --> 00:41:29.089 align:start position:0% actually control yeah because it's like you<00:41:27.630> know<00:41:27.779> those<00:41:27.929> obvious<00:41:28.469> the<00:41:28.619> radio<00:41:28.949> of 00:41:29.089 --> 00:41:29.099 align:start position:0% you know those obvious the radio of 00:41:29.099 --> 00:41:30.410 align:start position:0% you know those obvious the radio of dudes<00:41:29.339> and<00:41:29.519> like<00:41:29.670> sent<00:41:29.910> messages<00:41:30.239> across 00:41:30.410 --> 00:41:30.420 align:start position:0% dudes and like sent messages across 00:41:30.420 --> 00:41:33.079 align:start position:0% dudes and like sent messages across Europe<00:41:30.869> embassies<00:41:31.709> yeah<00:41:32.249> someone<00:41:32.759> is<00:41:32.880> working 00:41:33.079 --> 00:41:33.089 align:start position:0% Europe embassies yeah someone is working 00:41:33.089 --> 00:41:34.669 align:start position:0% Europe embassies yeah someone is working on<00:41:33.359> a<00:41:33.420> transport<00:41:34.019> for<00:41:34.170> that<00:41:34.319> put<00:41:34.559> a<00:41:34.589> little 00:41:34.669 --> 00:41:34.679 align:start position:0% on a transport for that put a little 00:41:34.679 --> 00:41:37.160 align:start position:0% on a transport for that put a little cream<00:41:34.979> here<00:41:35.939> you<00:41:36.089> can<00:41:36.239> read<00:41:36.689> your<00:41:36.779> goes<00:41:36.989> a<00:41:37.019> lot 00:41:37.160 --> 00:41:37.170 align:start position:0% cream here you can read your goes a lot 00:41:37.170 --> 00:41:38.479 align:start position:0% cream here you can read your goes a lot further<00:41:37.349> right<00:41:37.679> yeah<00:41:37.829> and<00:41:38.009> you've<00:41:38.339> already 00:41:38.479 --> 00:41:38.489 align:start position:0% further right yeah and you've already 00:41:38.489 --> 00:41:40.009 align:start position:0% further right yeah and you've already established<00:41:38.699> that<00:41:39.150> it's<00:41:39.390> like<00:41:39.539> you<00:41:39.630> use<00:41:39.869> the 00:41:40.009 --> 00:41:40.019 align:start position:0% established that it's like you use the 00:41:40.019 --> 00:41:41.449 align:start position:0% established that it's like you use the acknowledged<00:41:40.499> thing<00:41:40.979> you're<00:41:41.160> talked<00:41:41.309> about 00:41:41.449 --> 00:41:41.459 align:start position:0% acknowledged thing you're talked about 00:41:41.459 --> 00:41:43.870 align:start position:0% acknowledged thing you're talked about earlier<00:41:41.729> and<00:41:42.150> they<00:41:42.749> found<00:41:43.049> each<00:41:43.259> other 00:41:43.870 --> 00:41:43.880 align:start position:0% earlier and they found each other 00:41:43.880 --> 00:41:45.589 align:start position:0% earlier and they found each other potentially<00:41:44.880> have<00:41:44.969> something<00:41:45.239> within<00:41:45.420> the 00:41:45.589 --> 00:41:45.599 align:start position:0% potentially have something within the 00:41:45.599 --> 00:41:48.019 align:start position:0% potentially have something within the radio<00:41:45.900> signals<00:41:46.289> trigger<00:41:46.559> sort<00:41:47.160> of<00:41:47.249> on<00:41:47.670> some 00:41:48.019 --> 00:41:48.029 align:start position:0% radio signals trigger sort of on some 00:41:48.029 --> 00:41:49.789 align:start position:0% radio signals trigger sort of on some sort<00:41:48.179> of<00:41:48.269> frequency<00:41:48.689> that's<00:41:49.079> all<00:41:49.199> so<00:41:49.349> whatever 00:41:49.789 --> 00:41:49.799 align:start position:0% sort of frequency that's all so whatever 00:41:49.799 --> 00:41:52.459 align:start position:0% sort of frequency that's all so whatever it's<00:41:49.979> very<00:41:50.189> light<00:41:50.539> payload<00:41:51.539> and<00:41:51.689> then<00:41:52.229> boom 00:41:52.459 --> 00:41:52.469 align:start position:0% it's very light payload and then boom 00:41:52.469 --> 00:41:54.620 align:start position:0% it's very light payload and then boom you've<00:41:52.709> got<00:41:52.739> a<00:41:52.859> natural<00:41:53.039> direct<00:41:53.519> path<00:41:53.699> to<00:41:53.729> know 00:41:54.620 --> 00:41:54.630 align:start position:0% you've got a natural direct path to know 00:41:54.630 --> 00:41:59.469 align:start position:0% you've got a natural direct path to know you<00:41:54.689> should<00:41:54.929> do<00:41:55.339> going<00:41:56.339> on<00:41:56.429> github<00:41:56.849> there's 00:41:59.469 --> 00:41:59.479 align:start position:0% 00:41:59.479 --> 00:42:02.749 align:start position:0% there's<00:42:00.479> research<00:42:00.900> repository<00:42:01.259> and<00:42:01.920> if<00:42:02.670> you 00:42:02.749 --> 00:42:02.759 align:start position:0% there's research repository and if you 00:42:02.759 --> 00:42:05.299 align:start position:0% there's research repository and if you have<00:42:02.910> any<00:42:03.150> ideas<00:42:03.359> like<00:42:03.779> that<00:42:04.309> relationship 00:42:05.299 --> 00:42:05.309 align:start position:0% have any ideas like that relationship 00:42:05.309 --> 00:42:07.519 align:start position:0% have any ideas like that relationship with<00:42:05.579> like<00:42:05.759> any<00:42:06.390> research<00:42:06.869> interesting 00:42:07.519 --> 00:42:07.529 align:start position:0% with like any research interesting 00:42:07.529 --> 00:42:09.469 align:start position:0% with like any research interesting research<00:42:07.799> ideas<00:42:08.219> like<00:42:08.910> we're<00:42:09.089> trying<00:42:09.299> to<00:42:09.359> get 00:42:09.469 --> 00:42:09.479 align:start position:0% research ideas like we're trying to get 00:42:09.479 --> 00:42:11.870 align:start position:0% research ideas like we're trying to get as<00:42:09.599> many<00:42:09.719> people<00:42:10.140> as<00:42:10.229> well<00:42:10.380> as<00:42:10.529> possible<00:42:10.890> to<00:42:11.009> do 00:42:11.870 --> 00:42:11.880 align:start position:0% as many people as well as possible to do 00:42:11.880 --> 00:42:13.939 align:start position:0% as many people as well as possible to do comas<00:42:12.269> what's<00:42:12.749> that<00:42:12.869> company<00:42:13.229> that<00:42:13.410> does<00:42:13.679> I 00:42:13.939 --> 00:42:13.949 align:start position:0% comas what's that company that does I 00:42:13.949 --> 00:42:15.439 align:start position:0% comas what's that company that does I think<00:42:14.189> they've<00:42:14.309> done<00:42:14.339> Bitcoin<00:42:14.819> transactions 00:42:15.439 --> 00:42:15.449 align:start position:0% think they've done Bitcoin transactions 00:42:15.449 --> 00:42:18.019 align:start position:0% think they've done Bitcoin transactions over<00:42:15.630> radio<00:42:15.900> yeah<00:42:16.349> yeah<00:42:17.279> but<00:42:17.519> the<00:42:17.819> difference 00:42:18.019 --> 00:42:18.029 align:start position:0% over radio yeah yeah but the difference 00:42:18.029 --> 00:42:20.239 align:start position:0% over radio yeah yeah but the difference about<00:42:18.630> their<00:42:18.929> thing<00:42:19.170> is<00:42:19.319> you<00:42:19.499> need<00:42:19.679> external 00:42:20.239 --> 00:42:20.249 align:start position:0% about their thing is you need external 00:42:20.249 --> 00:42:23.239 align:start position:0% about their thing is you need external devices<00:42:20.849> for<00:42:21.329> their<00:42:21.449> mission<00:42:21.869> what's<00:42:22.859> do<00:42:23.189> you 00:42:23.239 --> 00:42:23.249 align:start position:0% devices for their mission what's do you 00:42:23.249 --> 00:42:29.029 align:start position:0% devices for their mission what's do you know<00:42:23.369> the<00:42:23.489> name<00:42:23.609> of<00:42:23.640> the<00:42:23.729> company<00:42:28.039> someone 00:42:29.029 --> 00:42:29.039 align:start position:0% know the name of the company someone 00:42:29.039 --> 00:42:29.989 align:start position:0% know the name of the company someone keeps<00:42:29.279> sending<00:42:29.489> it<00:42:29.699> to<00:42:29.819> us 00:42:29.989 --> 00:42:29.999 align:start position:0% keeps sending it to us 00:42:29.999 --> 00:42:31.459 align:start position:0% keeps sending it to us yeah<00:42:30.209> we've<00:42:30.390> kept<00:42:30.660> team<00:42:30.869> like<00:42:31.049> we<00:42:31.079> don't<00:42:31.349> wanna 00:42:31.459 --> 00:42:31.469 align:start position:0% yeah we've kept team like we don't wanna 00:42:31.469 --> 00:42:32.630 align:start position:0% yeah we've kept team like we don't wanna do<00:42:31.619> this<00:42:31.769> this<00:42:31.979> is<00:42:32.099> you<00:42:32.160> need<00:42:32.279> separate 00:42:32.630 --> 00:42:32.640 align:start position:0% do this this is you need separate 00:42:32.640 --> 00:42:34.609 align:start position:0% do this this is you need separate devices<00:42:32.939> okay<00:42:33.449> so<00:42:33.509> and<00:42:33.749> it<00:42:33.809> also<00:42:33.869> says<00:42:34.229> Bitcoin 00:42:34.609 --> 00:42:34.619 align:start position:0% devices okay so and it also says Bitcoin 00:42:34.619 --> 00:42:37.069 align:start position:0% devices okay so and it also says Bitcoin transit<00:42:34.979> okay<00:42:35.219> so<00:42:35.279> it's<00:42:35.900> specific<00:42:36.900> to<00:42:36.929> their 00:42:37.069 --> 00:42:37.079 align:start position:0% transit okay so it's specific to their 00:42:37.079 --> 00:42:40.189 align:start position:0% transit okay so it's specific to their device<00:42:37.410> can<00:42:37.859> you<00:42:37.949> generalize<00:42:38.249> no<00:42:38.729> it's<00:42:39.209> it's<00:42:39.689> a 00:42:40.189 --> 00:42:40.199 align:start position:0% device can you generalize no it's it's a 00:42:40.199 --> 00:42:43.130 align:start position:0% device can you generalize no it's it's a generalized<00:42:41.099> thing<00:42:41.880> that<00:42:42.390> then<00:42:42.630> someone 00:42:43.130 --> 00:42:43.140 align:start position:0% generalized thing that then someone 00:42:43.140 --> 00:42:44.959 align:start position:0% generalized thing that then someone built<00:42:43.380> Bitcoin<00:42:43.890> stuff<00:42:44.099> long<00:42:44.309> but<00:42:44.519> it<00:42:44.609> requires 00:42:44.959 --> 00:42:44.969 align:start position:0% built Bitcoin stuff long but it requires 00:42:44.969 --> 00:42:47.150 align:start position:0% built Bitcoin stuff long but it requires specific<00:42:45.299> hardware<00:42:45.929> it<00:42:46.499> requires<00:42:46.769> your<00:42:46.920> phone 00:42:47.150 --> 00:42:47.160 align:start position:0% specific hardware it requires your phone 00:42:47.160 --> 00:42:48.540 align:start position:0% specific hardware it requires your phone to<00:42:47.339> be<00:42:47.459> plugged<00:42:47.699> in<00:42:47.849> one<00:42:48.029> at 00:42:48.540 --> 00:42:48.550 align:start position:0% to be plugged in one at 00:42:48.550 --> 00:42:52.380 align:start position:0% to be plugged in one at and<00:42:48.640> the<00:42:48.850> list<00:42:49.030> goes<00:42:49.270> on<00:42:51.250> yeah<00:42:51.370> ten<00:42:51.850> exactly<00:42:52.330> oh 00:42:52.380 --> 00:42:52.390 align:start position:0% and the list goes on yeah ten exactly oh 00:42:52.390 --> 00:42:55.230 align:start position:0% and the list goes on yeah ten exactly oh yeah<00:42:52.930> it's<00:42:53.470> patented<00:42:54.130> it's<00:42:54.580> closed<00:42:54.970> source 00:42:55.230 --> 00:42:55.240 align:start position:0% yeah it's patented it's closed source 00:42:55.240 --> 00:42:58.110 align:start position:0% yeah it's patented it's closed source that's<00:42:56.110> yeah<00:42:56.680> well<00:42:56.950> it's<00:42:57.280> the<00:42:57.340> bugger<00:42:57.670> spike 00:42:58.110 --> 00:42:58.120 align:start position:0% that's yeah well it's the bugger spike 00:42:58.120 --> 00:42:59.640 align:start position:0% that's yeah well it's the bugger spike the<00:42:58.240> main<00:42:58.420> reason<00:42:58.810> we're<00:42:58.960> doing<00:42:59.080> this<00:42:59.290> yeah 00:42:59.640 --> 00:42:59.650 align:start position:0% the main reason we're doing this yeah 00:42:59.650 --> 00:43:02.100 align:start position:0% the main reason we're doing this yeah there's<00:42:59.950> like<00:43:00.100> obviously<00:43:00.760> I<00:43:00.910> think<00:43:01.480> the 00:43:02.100 --> 00:43:02.110 align:start position:0% there's like obviously I think the 00:43:02.110 --> 00:43:05.070 align:start position:0% there's like obviously I think the umbrella<00:43:03.210> well<00:43:04.210> no<00:43:04.330> now<00:43:04.480> in<00:43:04.660> Hong<00:43:04.780> Kong 00:43:05.070 --> 00:43:05.080 align:start position:0% umbrella well no now in Hong Kong 00:43:05.080 --> 00:43:06.750 align:start position:0% umbrella well no now in Hong Kong there's<00:43:05.350> like<00:43:05.470> because<00:43:05.920> firechat<00:43:06.430> used<00:43:06.670> to 00:43:06.750 --> 00:43:06.760 align:start position:0% there's like because firechat used to 00:43:06.760 --> 00:43:08.640 align:start position:0% there's like because firechat used to exist<00:43:06.970> yeah<00:43:07.270> when<00:43:07.780> what<00:43:07.900> happened<00:43:07.930> there<00:43:08.470> is 00:43:08.640 --> 00:43:08.650 align:start position:0% exist yeah when what happened there is 00:43:08.650 --> 00:43:10.290 align:start position:0% exist yeah when what happened there is the<00:43:08.860> developer<00:43:09.370> was<00:43:09.490> told<00:43:09.700> by<00:43:09.790> the<00:43:09.850> Chinese 00:43:10.290 --> 00:43:10.300 align:start position:0% the developer was told by the Chinese 00:43:10.300 --> 00:43:11.760 align:start position:0% the developer was told by the Chinese government<00:43:10.690> to<00:43:10.720> stop<00:43:10.990> building<00:43:11.230> on<00:43:11.650> it 00:43:11.760 --> 00:43:11.770 align:start position:0% government to stop building on it 00:43:11.770 --> 00:43:13.440 align:start position:0% government to stop building on it because<00:43:12.010> he's<00:43:12.100> a<00:43:12.130> Chinese<00:43:12.460> citizen<00:43:13.000> right<00:43:13.180> and 00:43:13.440 --> 00:43:13.450 align:start position:0% because he's a Chinese citizen right and 00:43:13.450 --> 00:43:15.090 align:start position:0% because he's a Chinese citizen right and now<00:43:13.840> there's<00:43:14.050> like<00:43:14.140> another<00:43:14.440> one<00:43:14.680> and<00:43:14.980> they 00:43:15.090 --> 00:43:15.100 align:start position:0% now there's like another one and they 00:43:15.100 --> 00:43:17.070 align:start position:0% now there's like another one and they have<00:43:15.280> an<00:43:15.370> SDK<00:43:15.700> but<00:43:16.060> it's<00:43:16.180> a<00:43:16.270> closed<00:43:16.540> source<00:43:16.780> sdk 00:43:17.070 --> 00:43:17.080 align:start position:0% have an SDK but it's a closed source sdk 00:43:17.080 --> 00:43:20.160 align:start position:0% have an SDK but it's a closed source sdk and<00:43:17.410> you<00:43:17.740> need<00:43:17.950> an<00:43:18.040> API<00:43:18.490> key<00:43:18.840> weird<00:43:19.840> that<00:43:20.050> you 00:43:20.160 --> 00:43:20.170 align:start position:0% and you need an API key weird that you 00:43:20.170 --> 00:43:26.850 align:start position:0% and you need an API key weird that you can<00:43:20.320> have<00:43:20.440> them<00:43:20.530> in<00:43:24.690> our<00:43:25.690> chat<00:43:26.440> and<00:43:26.650> there's 00:43:26.850 --> 00:43:26.860 align:start position:0% can have them in our chat and there's 00:43:26.860 --> 00:43:28.320 align:start position:0% can have them in our chat and there's like<00:43:27.010> the<00:43:27.190> other<00:43:27.310> thing<00:43:27.580> because<00:43:27.970> they're 00:43:28.320 --> 00:43:28.330 align:start position:0% like the other thing because they're 00:43:28.330 --> 00:43:29.850 align:start position:0% like the other thing because they're both<00:43:28.540> proprietary<00:43:29.290> they're<00:43:29.500> closed<00:43:29.830> so 00:43:29.850 --> 00:43:29.860 align:start position:0% both proprietary they're closed so 00:43:29.860 --> 00:43:31.860 align:start position:0% both proprietary they're closed so that's<00:43:30.280> written<00:43:30.490> by<00:43:30.760> us<00:43:30.970> oh<00:43:31.270> yeah<00:43:31.540> average<00:43:31.750> of 00:43:31.860 --> 00:43:31.870 align:start position:0% that's written by us oh yeah average of 00:43:31.870 --> 00:43:33.750 align:start position:0% that's written by us oh yeah average of Pi<00:43:31.990> yet<00:43:32.200> they're<00:43:32.680> closed<00:43:32.890> source<00:43:33.130> they<00:43:33.490> cost 00:43:33.750 --> 00:43:33.760 align:start position:0% Pi yet they're closed source they cost 00:43:33.760 --> 00:43:35.940 align:start position:0% Pi yet they're closed source they cost money<00:43:34.060> to<00:43:34.150> use<00:43:34.390> it's<00:43:34.630> like<00:43:34.690> we<00:43:35.620> don't<00:43:35.710> want<00:43:35.890> to 00:43:35.940 --> 00:43:35.950 align:start position:0% money to use it's like we don't want to 00:43:35.950 --> 00:43:38.010 align:start position:0% money to use it's like we don't want to pay<00:43:36.070> for<00:43:36.130> this<00:43:36.370> we<00:43:36.610> want<00:43:37.570> to<00:43:37.600> be<00:43:37.660> able<00:43:37.780> to<00:43:37.900> like 00:43:38.010 --> 00:43:38.020 align:start position:0% pay for this we want to be able to like 00:43:38.020 --> 00:43:40.110 align:start position:0% pay for this we want to be able to like just<00:43:38.200> download<00:43:38.560> it<00:43:38.650> and<00:43:38.710> use<00:43:38.890> it<00:43:38.920> you<00:43:39.790> just<00:43:39.970> did 00:43:40.110 --> 00:43:40.120 align:start position:0% just download it and use it you just did 00:43:40.120 --> 00:43:48.300 align:start position:0% just download it and use it you just did yeah<00:43:40.540> I<00:43:42.690> think<00:43:43.690> it's<00:43:43.810> what<00:43:46.260> I<00:43:47.260> think<00:43:47.860> it's<00:43:48.040> MIT 00:43:48.300 --> 00:43:48.310 align:start position:0% yeah I think it's what I think it's MIT 00:43:48.310 --> 00:43:50.610 align:start position:0% yeah I think it's what I think it's MIT yeah<00:43:49.030> it's<00:43:49.180> all<00:43:49.270> MIT<00:43:49.570> like<00:43:49.840> yes<00:43:50.020> and<00:43:50.320> that's 00:43:50.610 --> 00:43:50.620 align:start position:0% yeah it's all MIT like yes and that's 00:43:50.620 --> 00:43:51.870 align:start position:0% yeah it's all MIT like yes and that's the<00:43:50.770> point<00:43:50.950> right 00:43:51.870 --> 00:43:51.880 align:start position:0% the point right 00:43:51.880 --> 00:43:55.560 align:start position:0% the point right steal<00:43:52.150> steal<00:43:52.750> it<00:43:52.930> if<00:43:53.050> you<00:43:53.200> run<00:43:53.770> it<00:43:53.890> use<00:43:54.610> it<00:43:54.790> like 00:43:55.560 --> 00:43:55.570 align:start position:0% steal steal it if you run it use it like 00:43:55.570 --> 00:43:58.470 align:start position:0% steal steal it if you run it use it like this<00:43:56.260> is<00:43:56.500> a<00:43:56.530> free<00:43:56.890> public<00:43:57.160> good<00:43:57.580> for<00:43:57.820> people 00:43:58.470 --> 00:43:58.480 align:start position:0% this is a free public good for people 00:43:58.480 --> 00:44:00.120 align:start position:0% this is a free public good for people right<00:43:58.780> this<00:43:59.110> is<00:43:59.260> and<00:43:59.440> as<00:43:59.530> you<00:43:59.620> said<00:43:59.800> you<00:43:59.980> hate 00:44:00.120 --> 00:44:00.130 align:start position:0% right this is and as you said you hate 00:44:00.130 --> 00:44:02.400 align:start position:0% right this is and as you said you hate radios<00:44:00.550> that<00:44:00.640> just<00:44:01.030> means<00:44:01.270> we<00:44:01.480> can<00:44:01.660> as<00:44:02.080> soon<00:44:02.320> as 00:44:02.400 --> 00:44:02.410 align:start position:0% radios that just means we can as soon as 00:44:02.410 --> 00:44:05.510 align:start position:0% radios that just means we can as soon as we<00:44:02.500> get<00:44:02.590> any<00:44:02.650> better<00:44:02.890> bands<00:44:03.190> and<00:44:03.580> -<00:44:03.940> play 00:44:05.510 --> 00:44:05.520 align:start position:0% we get any better bands and - play 00:44:05.520 --> 00:44:06.810 align:start position:0% we get any better bands and - play further 00:44:06.810 --> 00:44:06.820 align:start position:0% further 00:44:06.820 --> 00:44:08.160 align:start position:0% further yeah<00:44:07.090> and<00:44:07.240> once<00:44:07.390> we<00:44:07.480> get<00:44:07.570> more<00:44:07.750> like<00:44:07.960> low 00:44:08.160 --> 00:44:08.170 align:start position:0% yeah and once we get more like low 00:44:08.170 --> 00:44:10.320 align:start position:0% yeah and once we get more like low frequency<00:44:08.650> bands<00:44:08.860> just<00:44:09.610> like<00:44:09.760> think<00:44:10.000> of<00:44:10.120> the 00:44:10.320 --> 00:44:10.330 align:start position:0% frequency bands just like think of the 00:44:10.330 --> 00:44:14.050 align:start position:0% frequency bands just like think of the possibilities<00:44:11.080> here<00:44:11.260> we<00:44:11.440> can<00:44:11.560> literally<00:44:11.830> do 00:44:14.050 --> 00:44:14.060 align:start position:0% 00:44:14.060 --> 00:44:16.940 align:start position:0% like<00:44:15.060> because<00:44:15.780> why<00:44:16.320> would<00:44:16.470> I<00:44:16.560> want<00:44:16.740> to<00:44:16.800> use<00:44:16.890> the 00:44:16.940 --> 00:44:16.950 align:start position:0% like because why would I want to use the 00:44:16.950 --> 00:44:18.020 align:start position:0% like because why would I want to use the internet<00:44:17.040> when<00:44:17.400> it's<00:44:17.520> attached<00:44:17.730> to<00:44:17.850> me<00:44:17.910> I 00:44:18.020 --> 00:44:18.030 align:start position:0% internet when it's attached to me I 00:44:18.030 --> 00:44:20.390 align:start position:0% internet when it's attached to me I speak<00:44:18.270> French<00:44:19.220> there's<00:44:20.220> a<00:44:20.250> lot<00:44:20.340> of 00:44:20.390 --> 00:44:20.400 align:start position:0% speak French there's a lot of 00:44:20.400 --> 00:44:23.240 align:start position:0% speak French there's a lot of possibilities<00:44:20.880> here<00:44:21.590> design<00:44:22.590> space<00:44:22.860> is<00:44:22.890> huge 00:44:23.240 --> 00:44:23.250 align:start position:0% possibilities here design space is huge 00:44:23.250 --> 00:44:27.710 align:start position:0% possibilities here design space is huge it's<00:44:23.790> awesome<00:44:25.550> yeah<00:44:26.580> wouldn't<00:44:27.420> you<00:44:27.480> meet 00:44:27.710 --> 00:44:27.720 align:start position:0% it's awesome yeah wouldn't you meet 00:44:27.720 --> 00:44:29.750 align:start position:0% it's awesome yeah wouldn't you meet Akash<00:44:28.020> the<00:44:28.380> unique<00:44:28.770> idea<00:44:29.130> the<00:44:29.280> messages<00:44:29.730> that 00:44:29.750 --> 00:44:29.760 align:start position:0% Akash the unique idea the messages that 00:44:29.760 --> 00:44:31.520 align:start position:0% Akash the unique idea the messages that you're<00:44:29.970> providing<00:44:30.660> around<00:44:30.930> if<00:44:31.080> you<00:44:31.170> can<00:44:31.230> run 00:44:31.520 --> 00:44:31.530 align:start position:0% you're providing around if you can run 00:44:31.530 --> 00:44:34.760 align:start position:0% you're providing around if you can run into<00:44:31.680> an<00:44:31.830> infinite<00:44:32.220> loop<00:44:32.370> with<00:44:32.750> yeah<00:44:33.780> yeah<00:44:34.470> so 00:44:34.760 --> 00:44:34.770 align:start position:0% into an infinite loop with yeah yeah so 00:44:34.770 --> 00:44:36.830 align:start position:0% into an infinite loop with yeah yeah so you<00:44:34.860> guys<00:44:34.950> are<00:44:35.160> caching<00:44:35.670> with<00:44:35.820> you<00:44:36.030> we<00:44:36.630> are 00:44:36.830 --> 00:44:36.840 align:start position:0% you guys are caching with you we are 00:44:36.840 --> 00:44:38.270 align:start position:0% you guys are caching with you we are caching<00:44:37.260> right<00:44:37.410> now<00:44:37.530> in<00:44:37.740> the<00:44:37.920> naive 00:44:38.270 --> 00:44:38.280 align:start position:0% caching right now in the naive 00:44:38.280 --> 00:44:40.070 align:start position:0% caching right now in the naive implementation<00:44:38.430> but<00:44:39.150> there's<00:44:39.390> a<00:44:39.450> discussion 00:44:40.070 --> 00:44:40.080 align:start position:0% implementation but there's a discussion 00:44:40.080 --> 00:44:41.660 align:start position:0% implementation but there's a discussion by<00:44:40.170> one<00:44:40.320> on<00:44:40.440> how<00:44:40.560> we<00:44:40.620> must<00:44:40.860> do<00:44:41.010> that<00:44:41.190> oh<00:44:41.340> right 00:44:41.660 --> 00:44:41.670 align:start position:0% by one on how we must do that oh right 00:44:41.670 --> 00:44:44.930 align:start position:0% by one on how we must do that oh right there<00:44:42.800> there's<00:44:43.800> also<00:44:43.980> a<00:44:44.100> question<00:44:44.250> on<00:44:44.520> if<00:44:44.790> we 00:44:44.930 --> 00:44:44.940 align:start position:0% there there's also a question on if we 00:44:44.940 --> 00:44:46.790 align:start position:0% there there's also a question on if we need<00:44:45.120> a<00:44:45.150> build<00:44:45.420> that<00:44:45.570> data<00:44:45.780> sync<00:44:46.110> protocol<00:44:46.650> on 00:44:46.790 --> 00:44:46.800 align:start position:0% need a build that data sync protocol on 00:44:46.800 --> 00:44:49.040 align:start position:0% need a build that data sync protocol on top<00:44:46.980> of<00:44:47.100> it<00:44:47.220> something<00:44:47.490> like<00:44:47.520> TCP<00:44:48.000> so<00:44:48.810> that<00:44:48.930> we 00:44:49.040 --> 00:44:49.050 align:start position:0% top of it something like TCP so that we 00:44:49.050 --> 00:44:50.630 align:start position:0% top of it something like TCP so that we can<00:44:49.170> assert<00:44:49.440> that<00:44:49.470> messages<00:44:50.100> are<00:44:50.370> somehow 00:44:50.630 --> 00:44:50.640 align:start position:0% can assert that messages are somehow 00:44:50.640 --> 00:44:52.310 align:start position:0% can assert that messages are somehow received<00:44:51.120> but<00:44:51.330> the<00:44:51.450> question<00:44:51.750> then<00:44:51.900> there<00:44:52.140> is 00:44:52.310 --> 00:44:52.320 align:start position:0% received but the question then there is 00:44:52.320 --> 00:44:53.810 align:start position:0% received but the question then there is how<00:44:52.500> do<00:44:52.560> we<00:44:52.650> do<00:44:52.920> that<00:44:53.100> with<00:44:53.340> all<00:44:53.460> the<00:44:53.580> holes 00:44:53.810 --> 00:44:53.820 align:start position:0% how do we do that with all the holes 00:44:53.820 --> 00:44:56.420 align:start position:0% how do we do that with all the holes that<00:44:54.120> are<00:44:54.510> in<00:44:54.690> between<00:44:54.960> two<00:44:55.320> points<00:44:55.740> there's<00:44:56.370> a 00:44:56.420 --> 00:44:56.430 align:start position:0% that are in between two points there's a 00:44:56.430 --> 00:44:59.120 align:start position:0% that are in between two points there's a lot<00:44:56.670> of<00:44:56.900> there's<00:44:57.900> a<00:44:57.960> lot<00:44:58.080> of<00:44:58.200> ideas<00:44:58.560> that<00:44:58.770> we 00:44:59.120 --> 00:44:59.130 align:start position:0% lot of there's a lot of ideas that we 00:44:59.130 --> 00:45:01.310 align:start position:0% lot of there's a lot of ideas that we are<00:44:59.430> floating<00:45:00.000> around<00:45:00.120> but<00:45:00.540> a<00:45:00.780> lot<00:45:01.200> of 00:45:01.310 --> 00:45:01.320 align:start position:0% are floating around but a lot of 00:45:01.320 --> 00:45:03.920 align:start position:0% are floating around but a lot of research<00:45:02.250> that<00:45:02.280> needs<00:45:02.640> to<00:45:02.760> be<00:45:02.790> done<00:45:03.030> to<00:45:03.240> figure 00:45:03.920 --> 00:45:03.930 align:start position:0% research that needs to be done to figure 00:45:03.930 --> 00:45:05.930 align:start position:0% research that needs to be done to figure out<00:45:04.020> a<00:45:04.050> solution<00:45:04.740> unlike<00:45:05.520> this<00:45:05.700> clever 00:45:05.930 --> 00:45:05.940 align:start position:0% out a solution unlike this clever 00:45:05.940 --> 00:45:10.310 align:start position:0% out a solution unlike this clever chassis<00:45:06.510> to<00:45:06.630> do<00:45:06.840> that<00:45:07.940> so<00:45:08.940> if<00:45:09.420> for<00:45:10.230> instance 00:45:10.310 --> 00:45:10.320 align:start position:0% chassis to do that so if for instance 00:45:10.320 --> 00:45:13.160 align:start position:0% chassis to do that so if for instance you<00:45:10.890> had<00:45:11.070> the<00:45:11.220> ability<00:45:11.640> you<00:45:12.030> also<00:45:12.900> have<00:45:13.140> a 00:45:13.160 --> 00:45:13.170 align:start position:0% you had the ability you also have a 00:45:13.170 --> 00:45:15.020 align:start position:0% you had the ability you also have a little<00:45:13.410> frequency<00:45:13.770> band<00:45:13.980> we<00:45:14.460> could<00:45:14.760> and<00:45:15.000> you 00:45:15.020 --> 00:45:15.030 align:start position:0% little frequency band we could and you 00:45:15.030 --> 00:45:16.430 align:start position:0% little frequency band we could and you could<00:45:15.360> in<00:45:15.450> theory<00:45:15.630> set<00:45:15.900> something<00:45:16.170> up<00:45:16.260> where 00:45:16.430 --> 00:45:16.440 align:start position:0% could in theory set something up where 00:45:16.440 --> 00:45:18.080 align:start position:0% could in theory set something up where the<00:45:16.620> acknowledgments<00:45:17.370> go<00:45:17.550> over<00:45:17.850> the<00:45:17.940> low 00:45:18.080 --> 00:45:18.090 align:start position:0% the acknowledgments go over the low 00:45:18.090 --> 00:45:19.610 align:start position:0% the acknowledgments go over the low frequency<00:45:18.570> bands<00:45:18.780> that<00:45:19.050> everybody<00:45:19.470> can 00:45:19.610 --> 00:45:19.620 align:start position:0% frequency bands that everybody can 00:45:19.620 --> 00:45:22.070 align:start position:0% frequency bands that everybody can receive<00:45:19.920> it<00:45:20.070> and<00:45:20.100> we<00:45:21.090> don't<00:45:21.360> actually<00:45:21.570> use<00:45:21.750> it 00:45:22.070 --> 00:45:22.080 align:start position:0% receive it and we don't actually use it 00:45:22.080 --> 00:45:23.480 align:start position:0% receive it and we don't actually use it to<00:45:22.260> actually<00:45:22.380> just<00:45:22.710> drop<00:45:22.890> the<00:45:23.010> network<00:45:23.250> and 00:45:23.480 --> 00:45:23.490 align:start position:0% to actually just drop the network and 00:45:23.490 --> 00:45:24.890 align:start position:0% to actually just drop the network and you<00:45:23.580> go<00:45:23.730> and<00:45:23.850> use<00:45:23.940> Wi-Fi<00:45:24.330> and<00:45:24.450> Bluetooth<00:45:24.720> we 00:45:24.890 --> 00:45:24.900 align:start position:0% you go and use Wi-Fi and Bluetooth we 00:45:24.900 --> 00:45:27.260 align:start position:0% you go and use Wi-Fi and Bluetooth we can<00:45:25.080> send<00:45:25.320> way<00:45:25.470> more<00:45:25.680> you<00:45:26.130> know<00:45:26.220> or<00:45:26.730> bigger 00:45:27.260 --> 00:45:27.270 align:start position:0% can send way more you know or bigger 00:45:27.270 --> 00:45:30.440 align:start position:0% can send way more you know or bigger payloads<00:45:28.430> across<00:45:29.430> and<00:45:29.760> that<00:45:29.910> that<00:45:30.150> could<00:45:30.300> be<00:45:30.420> a 00:45:30.440 --> 00:45:30.450 align:start position:0% payloads across and that that could be a 00:45:30.450 --> 00:45:33.650 align:start position:0% payloads across and that that could be a way<00:45:30.630> to<00:45:30.690> like<00:45:31.020> cheaply<00:45:31.350> do<00:45:31.680> it<00:45:32.450> you<00:45:33.450> know<00:45:33.540> when 00:45:33.650 --> 00:45:33.660 align:start position:0% way to like cheaply do it you know when 00:45:33.660 --> 00:45:35.870 align:start position:0% way to like cheaply do it you know when the<00:45:33.750> device<00:45:33.960> receives<00:45:34.230> message<00:45:34.590> it<00:45:34.770> goes<00:45:34.980> hey 00:45:35.870 --> 00:45:35.880 align:start position:0% the device receives message it goes hey 00:45:35.880 --> 00:45:38.170 align:start position:0% the device receives message it goes hey I<00:45:35.910> received<00:45:36.330> it<00:45:36.480> like<00:45:36.810> fine 00:45:38.170 --> 00:45:38.180 align:start position:0% I received it like fine 00:45:38.180 --> 00:45:41.680 align:start position:0% I received it like fine thank<00:45:38.480> you<00:45:38.660> right<00:45:39.820> but<00:45:40.820> again<00:45:41.120> these<00:45:41.480> are<00:45:41.660> all 00:45:41.680 --> 00:45:41.690 align:start position:0% thank you right but again these are all 00:45:41.690 --> 00:45:43.270 align:start position:0% thank you right but again these are all like<00:45:41.930> open<00:45:42.260> questions<00:45:42.620> and<00:45:42.770> obviously 00:45:43.270 --> 00:45:43.280 align:start position:0% like open questions and obviously 00:45:43.280 --> 00:45:45.580 align:start position:0% like open questions and obviously becomes<00:45:43.610> harbor<00:45:44.210> challenges<00:45:44.960> and<00:45:45.230> we're 00:45:45.580 --> 00:45:45.590 align:start position:0% becomes harbor challenges and we're 00:45:45.590 --> 00:45:47.560 align:start position:0% becomes harbor challenges and we're trying<00:45:45.800> to<00:45:45.860> make<00:45:45.920> it<00:45:46.070> so<00:45:46.220> that<00:45:46.570> ideally 00:45:47.560 --> 00:45:47.570 align:start position:0% trying to make it so that ideally 00:45:47.570 --> 00:45:49.000 align:start position:0% trying to make it so that ideally doesn't<00:45:47.930> matter<00:45:48.050> like<00:45:48.440> you<00:45:48.740> shouldn't<00:45:48.950> have 00:45:49.000 --> 00:45:49.010 align:start position:0% doesn't matter like you shouldn't have 00:45:49.010 --> 00:45:50.470 align:start position:0% doesn't matter like you shouldn't have to<00:45:49.130> have<00:45:49.370> hardware<00:45:49.760> I'm<00:45:49.970> gonna<00:45:50.180> have<00:45:50.390> the 00:45:50.470 --> 00:45:50.480 align:start position:0% to have hardware I'm gonna have the 00:45:50.480 --> 00:45:53.200 align:start position:0% to have hardware I'm gonna have the challenge<00:45:50.930> of<00:45:51.140> like<00:45:51.460> battery<00:45:52.460> on<00:45:52.970> a<00:45:53.000> mobile 00:45:53.200 --> 00:45:53.210 align:start position:0% challenge of like battery on a mobile 00:45:53.210 --> 00:45:57.130 align:start position:0% challenge of like battery on a mobile phone<00:45:54.970> Bluetooth<00:45:55.970> and<00:45:56.210> Wi-Fi<00:45:56.330> direct<00:45:56.720> you 00:45:57.130 --> 00:45:57.140 align:start position:0% phone Bluetooth and Wi-Fi direct you 00:45:57.140 --> 00:45:58.960 align:start position:0% phone Bluetooth and Wi-Fi direct you don't<00:45:57.470> want<00:45:57.650> that<00:45:57.770> to<00:45:57.830> be<00:45:57.950> volume<00:45:58.520> all<00:45:58.850> the 00:45:58.960 --> 00:45:58.970 align:start position:0% don't want that to be volume all the 00:45:58.970 --> 00:46:00.850 align:start position:0% don't want that to be volume all the time<00:45:59.180> because<00:45:59.630> at<00:46:00.050> one<00:46:00.170> point<00:46:00.230> you're<00:46:00.770> gonna 00:46:00.850 --> 00:46:00.860 align:start position:0% time because at one point you're gonna 00:46:00.860 --> 00:46:04.030 align:start position:0% time because at one point you're gonna run<00:46:01.160> out<00:46:01.280> of<00:46:01.310> battery<00:46:01.760> yeah<00:46:02.800> there's<00:46:03.800> a<00:46:03.890> bunch 00:46:04.030 --> 00:46:04.040 align:start position:0% run out of battery yeah there's a bunch 00:46:04.040 --> 00:46:06.100 align:start position:0% run out of battery yeah there's a bunch of<00:46:04.190> those<00:46:04.640> technical<00:46:05.000> jobs<00:46:05.330> should<00:46:05.750> allow 00:46:06.100 --> 00:46:06.110 align:start position:0% of those technical jobs should allow 00:46:06.110 --> 00:46:07.450 align:start position:0% of those technical jobs should allow people<00:46:06.320> to<00:46:06.440> harvest<00:46:06.740> the<00:46:07.040> battery<00:46:07.310> level 00:46:07.450 --> 00:46:07.460 align:start position:0% people to harvest the battery level 00:46:07.460 --> 00:46:15.370 align:start position:0% people to harvest the battery level three<00:46:07.850> layers<00:46:13.450> you<00:46:14.450> see<00:46:14.630> that<00:46:14.900> that's 00:46:15.370 --> 00:46:15.380 align:start position:0% three layers you see that that's 00:46:15.380 --> 00:46:20.350 align:start position:0% three layers you see that that's actually<00:46:15.740> a<00:46:15.980> nice<00:46:16.660> yeah 00:46:20.350 --> 00:46:20.360 align:start position:0% 00:46:20.360 --> 00:46:29.480 align:start position:0% that's<00:46:20.930> right<00:46:23.500> all<00:46:24.500> right 00:46:29.480 --> 00:46:29.490 align:start position:0% 00:46:29.490 --> 00:46:33.940 align:start position:0% [Applause]