WEBVTT Kind: captions Language: en 00:00:00.540 --> 00:00:17.710 align:start position:0% [Music] 00:00:17.710 --> 00:00:17.720 align:start position:0% [Music] 00:00:17.720 --> 00:00:20.810 align:start position:0% [Music] thank<00:00:18.720> you<00:00:19.070> thank<00:00:20.070> you<00:00:20.130> for<00:00:20.280> having<00:00:20.550> me<00:00:20.790> here 00:00:20.810 --> 00:00:20.820 align:start position:0% thank you thank you for having me here 00:00:20.820 --> 00:00:23.840 align:start position:0% thank you thank you for having me here today<00:00:21.000> uh<00:00:21.480> my<00:00:22.350> name<00:00:22.500> is<00:00:22.619> Sally<00:00:22.860> I'm<00:00:23.220> a<00:00:23.550> software 00:00:23.840 --> 00:00:23.850 align:start position:0% today uh my name is Sally I'm a software 00:00:23.850 --> 00:00:27.080 align:start position:0% today uh my name is Sally I'm a software engineer<00:00:24.390> at<00:00:24.570> protocol<00:00:25.470> labs<00:00:25.680> I<00:00:25.980> work<00:00:26.189> on<00:00:26.430> IFS 00:00:27.080 --> 00:00:27.090 align:start position:0% engineer at protocol labs I work on IFS 00:00:27.090 --> 00:00:30.260 align:start position:0% engineer at protocol labs I work on IFS and<00:00:27.360> more<00:00:27.570> specifically<00:00:28.439> on<00:00:28.849> dynamic<00:00:29.849> content 00:00:30.260 --> 00:00:30.270 align:start position:0% and more specifically on dynamic content 00:00:30.270 --> 00:00:34.150 align:start position:0% and more specifically on dynamic content so<00:00:30.420> distributed<00:00:31.410> peer-to-peer<00:00:32.400> applications 00:00:34.150 --> 00:00:34.160 align:start position:0% so distributed peer-to-peer applications 00:00:34.160 --> 00:00:36.500 align:start position:0% so distributed peer-to-peer applications one<00:00:35.160> of<00:00:35.250> the<00:00:35.400> applications<00:00:35.970> I've<00:00:36.330> been 00:00:36.500 --> 00:00:36.510 align:start position:0% one of the applications I've been 00:00:36.510 --> 00:00:38.229 align:start position:0% one of the applications I've been working<00:00:36.840> on<00:00:36.960> is<00:00:37.230> called 00:00:38.229 --> 00:00:38.239 align:start position:0% working on is called 00:00:38.239 --> 00:00:42.020 align:start position:0% working on is called Orban<00:00:39.440> appeared<00:00:40.440> to<00:00:40.590> hear<00:00:40.980> chat<00:00:41.370> application 00:00:42.020 --> 00:00:42.030 align:start position:0% Orban appeared to hear chat application 00:00:42.030 --> 00:00:44.750 align:start position:0% Orban appeared to hear chat application on<00:00:42.210> IP<00:00:42.420> FS<00:00:42.780> which<00:00:43.470> we<00:00:43.620> just<00:00:43.890> integrate<00:00:44.489> it<00:00:44.640> with 00:00:44.750 --> 00:00:44.760 align:start position:0% on IP FS which we just integrate it with 00:00:44.760 --> 00:00:48.410 align:start position:0% on IP FS which we just integrate it with you<00:00:44.970> port<00:00:45.739> you<00:00:46.739> already<00:00:47.159> seen<00:00:47.370> it<00:00:47.519> earlier 00:00:48.410 --> 00:00:48.420 align:start position:0% you port you already seen it earlier 00:00:48.420 --> 00:00:50.119 align:start position:0% you port you already seen it earlier here<00:00:48.629> today<00:00:48.870> and<00:00:49.110> the<00:00:49.440> marriage<00:00:49.650> of<00:00:49.949> these<00:00:50.070> two 00:00:50.119 --> 00:00:50.129 align:start position:0% here today and the marriage of these two 00:00:50.129 --> 00:00:53.390 align:start position:0% here today and the marriage of these two technologies<00:00:51.000> is<00:00:51.479> beautiful<00:00:52.080> so<00:00:52.860> today<00:00:53.250> I'm 00:00:53.390 --> 00:00:53.400 align:start position:0% technologies is beautiful so today I'm 00:00:53.400 --> 00:00:55.280 align:start position:0% technologies is beautiful so today I'm going<00:00:53.519> to<00:00:53.580> show<00:00:53.790> you<00:00:53.820> Orban<00:00:54.360> with<00:00:54.780> you<00:00:54.989> port 00:00:55.280 --> 00:00:55.290 align:start position:0% going to show you Orban with you port 00:00:55.290 --> 00:00:57.320 align:start position:0% going to show you Orban with you port and<00:00:55.500> talk<00:00:55.860> about<00:00:56.010> how<00:00:56.309> we<00:00:56.370> build<00:00:56.729> completely 00:00:57.320 --> 00:00:57.330 align:start position:0% and talk about how we build completely 00:00:57.330 --> 00:01:00.500 align:start position:0% and talk about how we build completely distributed<00:00:57.690> applications<00:00:58.650> today<00:00:59.280> and<00:00:59.610> also 00:01:00.500 --> 00:01:00.510 align:start position:0% distributed applications today and also 00:01:00.510 --> 00:01:02.840 align:start position:0% distributed applications today and also what<00:01:00.989> we<00:01:01.170> should<00:01:01.440> consider<00:01:01.920> when<00:01:02.460> we<00:01:02.580> build 00:01:02.840 --> 00:01:02.850 align:start position:0% what we should consider when we build 00:01:02.850 --> 00:01:07.160 align:start position:0% what we should consider when we build our<00:01:03.150> applications<00:01:04.019> for<00:01:04.409> web<00:01:05.129> 3.0<00:01:05.760> so<00:01:06.630> if<00:01:06.960> you 00:01:07.160 --> 00:01:07.170 align:start position:0% our applications for web 3.0 so if you 00:01:07.170 --> 00:01:10.039 align:start position:0% our applications for web 3.0 so if you heard<00:01:07.409> me<00:01:07.620> talking<00:01:07.950> about<00:01:08.190> orbit<00:01:08.820> before<00:01:09.049> you 00:01:10.039 --> 00:01:10.049 align:start position:0% heard me talking about orbit before you 00:01:10.049 --> 00:01:11.960 align:start position:0% heard me talking about orbit before you may<00:01:10.320> have<00:01:10.590> had<00:01:10.770> some<00:01:11.070> doubts<00:01:11.280> about<00:01:11.490> the 00:01:11.960 --> 00:01:11.970 align:start position:0% may have had some doubts about the 00:01:11.970 --> 00:01:14.750 align:start position:0% may have had some doubts about the distributed<00:01:12.570> nature<00:01:12.780> of<00:01:12.960> it<00:01:13.229> but<00:01:13.619> today<00:01:14.580> I'm 00:01:14.750 --> 00:01:14.760 align:start position:0% distributed nature of it but today I'm 00:01:14.760 --> 00:01:17.440 align:start position:0% distributed nature of it but today I'm happy<00:01:15.180> to<00:01:15.360> announce<00:01:15.540> that<00:01:16.049> orbit<00:01:16.650> is<00:01:16.830> finally 00:01:17.440 --> 00:01:17.450 align:start position:0% happy to announce that orbit is finally 00:01:17.450 --> 00:01:20.390 align:start position:0% happy to announce that orbit is finally completely<00:01:18.450> distributed<00:01:18.810> and<00:01:19.260> peer<00:01:20.040> to<00:01:20.220> peer 00:01:20.390 --> 00:01:20.400 align:start position:0% completely distributed and peer to peer 00:01:20.400 --> 00:01:28.120 align:start position:0% completely distributed and peer to peer there<00:01:20.730> are<00:01:20.880> no<00:01:21.150> servers<00:01:22.020> involved<00:01:23.210> so 00:01:28.120 --> 00:01:28.130 align:start position:0% 00:01:28.130 --> 00:01:32.500 align:start position:0% I'm<00:01:29.130> gonna<00:01:29.430> jump<00:01:30.150> right<00:01:30.360> into<00:01:30.570> the<00:01:31.160> demo<00:01:32.160> and 00:01:32.500 --> 00:01:32.510 align:start position:0% I'm gonna jump right into the demo and 00:01:32.510 --> 00:01:35.540 align:start position:0% I'm gonna jump right into the demo and show<00:01:33.510> you<00:01:33.840> the<00:01:34.050> cool<00:01:34.260> stuff<00:01:34.590> can<00:01:35.130> you<00:01:35.160> play<00:01:35.400> the 00:01:35.540 --> 00:01:35.550 align:start position:0% show you the cool stuff can you play the 00:01:35.550 --> 00:01:40.150 align:start position:0% show you the cool stuff can you play the video<00:01:35.820> please 00:01:40.150 --> 00:01:40.160 align:start position:0% 00:01:40.160 --> 00:01:42.010 align:start position:0% so 00:01:42.010 --> 00:01:42.020 align:start position:0% so 00:01:42.020 --> 00:01:45.200 align:start position:0% so when<00:01:43.020> I<00:01:43.050> open<00:01:43.440> orbit<00:01:43.800> I<00:01:43.980> can<00:01:44.430> log<00:01:44.610> in<00:01:44.790> with<00:01:44.820> is 00:01:45.200 --> 00:01:45.210 align:start position:0% when I open orbit I can log in with is 00:01:45.210 --> 00:01:47.540 align:start position:0% when I open orbit I can log in with is simply<00:01:45.690> with<00:01:45.780> a<00:01:45.840> nickname<00:01:46.140> or<00:01:46.560> I<00:01:46.620> can<00:01:47.040> use<00:01:47.340> you 00:01:47.540 --> 00:01:47.550 align:start position:0% simply with a nickname or I can use you 00:01:47.550 --> 00:01:50.120 align:start position:0% simply with a nickname or I can use you for<00:01:47.790> it<00:01:47.910> um<00:01:48.230> when<00:01:49.230> I<00:01:49.260> choose<00:01:49.500> you<00:01:49.710> for<00:01:49.920> it<00:01:50.040> it 00:01:50.120 --> 00:01:50.130 align:start position:0% for it um when I choose you for it it 00:01:50.130 --> 00:01:52.160 align:start position:0% for it um when I choose you for it it will<00:01:50.220> prompt<00:01:50.610> me<00:01:50.700> to<00:01:50.990> authenticate<00:01:51.990> the 00:01:52.160 --> 00:01:52.170 align:start position:0% will prompt me to authenticate the 00:01:52.170 --> 00:01:54.620 align:start position:0% will prompt me to authenticate the application<00:01:52.770> I<00:01:52.980> scan<00:01:53.550> the<00:01:53.700> QR<00:01:54.060> code<00:01:54.270> with<00:01:54.480> my 00:01:54.620 --> 00:01:54.630 align:start position:0% application I scan the QR code with my 00:01:54.630 --> 00:01:57.140 align:start position:0% application I scan the QR code with my mobile<00:01:55.020> app<00:01:55.260> and<00:01:55.470> orbit<00:01:56.340> will<00:01:56.520> pull<00:01:56.970> the 00:01:57.140 --> 00:01:57.150 align:start position:0% mobile app and orbit will pull the 00:01:57.150 --> 00:01:59.530 align:start position:0% mobile app and orbit will pull the profile<00:01:57.600> from<00:01:58.200> the<00:01:58.590> blockchain 00:01:59.530 --> 00:01:59.540 align:start position:0% profile from the blockchain 00:01:59.540 --> 00:02:02.960 align:start position:0% profile from the blockchain now<00:02:00.540> when<00:02:00.870> I<00:02:00.900> log<00:02:01.170> in<00:02:01.290> the<00:02:01.409> first<00:02:01.440> time<00:02:01.970> you 00:02:02.960 --> 00:02:02.970 align:start position:0% now when I log in the first time you 00:02:02.970 --> 00:02:05.060 align:start position:0% now when I log in the first time you port<00:02:03.240> will<00:02:03.390> ask<00:02:03.570> me<00:02:03.810> to<00:02:03.960> sign<00:02:04.170> my<00:02:04.409> orbit<00:02:04.800> key 00:02:05.060 --> 00:02:05.070 align:start position:0% port will ask me to sign my orbit key 00:02:05.070 --> 00:02:08.210 align:start position:0% port will ask me to sign my orbit key which<00:02:05.610> get<00:02:05.909> then<00:02:06.180> gets<00:02:06.450> added<00:02:06.659> to<00:02:06.930> my<00:02:07.220> Newports 00:02:08.210 --> 00:02:08.220 align:start position:0% which get then gets added to my Newports 00:02:08.220 --> 00:02:10.940 align:start position:0% which get then gets added to my Newports profile<00:02:08.610> and<00:02:08.849> will<00:02:09.810> work<00:02:10.019> as<00:02:10.229> the<00:02:10.560> public 00:02:10.940 --> 00:02:10.950 align:start position:0% profile and will work as the public 00:02:10.950 --> 00:02:13.490 align:start position:0% profile and will work as the public signing<00:02:11.310> key<00:02:11.790> for<00:02:12.180> the<00:02:12.300> messages<00:02:12.780> that<00:02:13.019> I'm 00:02:13.490 --> 00:02:13.500 align:start position:0% signing key for the messages that I'm 00:02:13.500 --> 00:02:16.280 align:start position:0% signing key for the messages that I'm sending<00:02:13.860> in<00:02:13.980> in<00:02:14.159> orbit<00:02:14.849> so<00:02:15.690> once<00:02:15.989> I'm<00:02:16.110> logged 00:02:16.280 --> 00:02:16.290 align:start position:0% sending in in orbit so once I'm logged 00:02:16.290 --> 00:02:18.290 align:start position:0% sending in in orbit so once I'm logged in<00:02:16.530> I<00:02:16.709> can<00:02:16.860> join<00:02:17.010> double<00:02:17.459> conte<00:02:17.730> channel<00:02:18.120> and 00:02:18.290 --> 00:02:18.300 align:start position:0% in I can join double conte channel and 00:02:18.300 --> 00:02:21.680 align:start position:0% in I can join double conte channel and start<00:02:18.480> chatting<00:02:19.379> um<00:02:20.000> one<00:02:21.000> of<00:02:21.030> the<00:02:21.180> really<00:02:21.540> cool 00:02:21.680 --> 00:02:21.690 align:start position:0% start chatting um one of the really cool 00:02:21.690 --> 00:02:24.649 align:start position:0% start chatting um one of the really cool features<00:02:21.750> of<00:02:22.849> orbit<00:02:23.849> is<00:02:24.060> the<00:02:24.120> file 00:02:24.649 --> 00:02:24.659 align:start position:0% features of orbit is the file 00:02:24.659 --> 00:02:27.649 align:start position:0% features of orbit is the file integration<00:02:25.260> with<00:02:25.499> ipfs<00:02:26.159> so<00:02:26.400> I<00:02:26.430> can<00:02:26.670> drag<00:02:27.389> and 00:02:27.649 --> 00:02:27.659 align:start position:0% integration with ipfs so I can drag and 00:02:27.659 --> 00:02:30.020 align:start position:0% integration with ipfs so I can drag and drop<00:02:27.840> file<00:02:28.350> and<00:02:28.590> folders<00:02:29.010> directly<00:02:29.640> into<00:02:29.910> the 00:02:30.020 --> 00:02:30.030 align:start position:0% drop file and folders directly into the 00:02:30.030 --> 00:02:32.170 align:start position:0% drop file and folders directly into the chat<00:02:30.330> and<00:02:30.510> share<00:02:30.990> it<00:02:31.140> with<00:02:31.320> the<00:02:31.410> channel<00:02:31.800> on 00:02:32.170 --> 00:02:32.180 align:start position:0% chat and share it with the channel on 00:02:32.180 --> 00:02:36.740 align:start position:0% chat and share it with the channel on code<00:02:33.180> pictures<00:02:33.960> video<00:02:34.710> audio<00:02:35.370> they<00:02:36.090> all<00:02:36.270> kind 00:02:36.740 --> 00:02:36.750 align:start position:0% code pictures video audio they all kind 00:02:36.750 --> 00:02:38.480 align:start position:0% code pictures video audio they all kind of<00:02:36.840> pop<00:02:37.200> right<00:02:37.500> in<00:02:37.710> and<00:02:38.040> you<00:02:38.220> can<00:02:38.250> start 00:02:38.480 --> 00:02:38.490 align:start position:0% of pop right in and you can start 00:02:38.490 --> 00:02:41.060 align:start position:0% of pop right in and you can start directly<00:02:39.390> streaming<00:02:39.990> the<00:02:40.110> videos<00:02:40.380> from<00:02:40.980> the 00:02:41.060 --> 00:02:41.070 align:start position:0% directly streaming the videos from the 00:02:41.070 --> 00:02:43.180 align:start position:0% directly streaming the videos from the other<00:02:41.460> users<00:02:41.910> um 00:02:43.180 --> 00:02:43.190 align:start position:0% other users um 00:02:43.190 --> 00:02:45.160 align:start position:0% other users um now 00:02:45.160 --> 00:02:45.170 align:start position:0% now 00:02:45.170 --> 00:02:49.030 align:start position:0% now what<00:02:46.170> you<00:02:46.710> four<00:02:46.950> gives<00:02:47.250> us<00:02:47.460> is 00:02:49.030 --> 00:02:49.040 align:start position:0% what you four gives us is 00:02:49.040 --> 00:02:52.610 align:start position:0% what you four gives us is the<00:02:50.040> verification<00:02:50.430> that<00:02:51.360> the<00:02:51.510> messages<00:02:52.020> from 00:02:52.610 --> 00:02:52.620 align:start position:0% the verification that the messages from 00:02:52.620 --> 00:02:56.390 align:start position:0% the verification that the messages from HUD<00:02:52.920> are<00:02:53.250> really<00:02:54.030> from<00:02:54.480> me<00:02:54.690> if<00:02:55.410> I<00:02:55.560> click<00:02:55.890> on<00:02:55.920> my 00:02:56.390 --> 00:02:56.400 align:start position:0% HUD are really from me if I click on my 00:02:56.400 --> 00:02:58.000 align:start position:0% HUD are really from me if I click on my username 00:02:58.000 --> 00:02:58.010 align:start position:0% username 00:02:58.010 --> 00:03:02.890 align:start position:0% username once<00:02:59.010> I'm<00:02:59.280> done<00:02:59.790> making<00:03:00.360> bad<00:03:00.750> jokes 00:03:02.890 --> 00:03:02.900 align:start position:0% 00:03:02.900 --> 00:03:05.830 align:start position:0% you<00:03:03.900> can<00:03:04.110> see<00:03:04.320> the 00:03:05.830 --> 00:03:05.840 align:start position:0% you can see the 00:03:05.840 --> 00:03:09.170 align:start position:0% you can see the you<00:03:06.840> poured<00:03:07.230> profile<00:03:07.920> data<00:03:08.190> right<00:03:08.610> there<00:03:09.000> so 00:03:09.170 --> 00:03:09.180 align:start position:0% you poured profile data right there so 00:03:09.180 --> 00:03:12.560 align:start position:0% you poured profile data right there so my<00:03:09.330> name<00:03:09.570> my<00:03:10.230> location<00:03:11.180> provider<00:03:12.180> is<00:03:12.390> you 00:03:12.560 --> 00:03:12.570 align:start position:0% my name my location provider is you 00:03:12.570 --> 00:03:14.480 align:start position:0% my name my location provider is you board<00:03:12.840> and<00:03:13.080> the<00:03:13.230> public<00:03:13.350> signing<00:03:13.920> key<00:03:14.130> that<00:03:14.460> I 00:03:14.480 --> 00:03:14.490 align:start position:0% board and the public signing key that I 00:03:14.490 --> 00:03:16.790 align:start position:0% board and the public signing key that I just<00:03:14.760> added<00:03:14.970> to<00:03:15.420> the<00:03:15.540> blockchain<00:03:15.780> and<00:03:16.230> which 00:03:16.790 --> 00:03:16.800 align:start position:0% just added to the blockchain and which 00:03:16.800 --> 00:03:19.130 align:start position:0% just added to the blockchain and which is<00:03:16.950> used<00:03:17.130> to<00:03:17.250> sign<00:03:17.490> the<00:03:17.640> messages<00:03:18.150> this<00:03:18.930> is 00:03:19.130 --> 00:03:19.140 align:start position:0% is used to sign the messages this is 00:03:19.140 --> 00:03:21.230 align:start position:0% is used to sign the messages this is extremely<00:03:19.680> exciting<00:03:20.190> I<00:03:20.550> know<00:03:20.610> who<00:03:21.180> I'm 00:03:21.230 --> 00:03:21.240 align:start position:0% extremely exciting I know who I'm 00:03:21.240 --> 00:03:23.560 align:start position:0% extremely exciting I know who I'm talking<00:03:21.750> with<00:03:21.900> and<00:03:22.140> I<00:03:22.530> can<00:03:22.770> verify<00:03:22.950> the<00:03:23.250> source 00:03:23.560 --> 00:03:23.570 align:start position:0% talking with and I can verify the source 00:03:23.570 --> 00:03:26.870 align:start position:0% talking with and I can verify the source this<00:03:24.570> you<00:03:25.320> fort<00:03:25.590> is<00:03:25.740> really<00:03:26.040> cool<00:03:26.220> I<00:03:26.370> love<00:03:26.670> it 00:03:26.870 --> 00:03:26.880 align:start position:0% this you fort is really cool I love it 00:03:26.880 --> 00:03:31.000 align:start position:0% this you fort is really cool I love it thank<00:03:27.420> you<00:03:27.540> Christian<00:03:27.900> and<00:03:28.140> consensus<00:03:29.180> so<00:03:30.180> I 00:03:31.000 --> 00:03:31.010 align:start position:0% thank you Christian and consensus so I 00:03:31.010 --> 00:03:35.710 align:start position:0% thank you Christian and consensus so I [Applause] 00:03:35.710 --> 00:03:35.720 align:start position:0% [Applause] 00:03:35.720 --> 00:03:38.210 align:start position:0% [Applause] wanted<00:03:36.720> to<00:03:36.900> show<00:03:37.080> you<00:03:37.140> another<00:03:37.320> cool<00:03:37.740> demo 00:03:38.210 --> 00:03:38.220 align:start position:0% wanted to show you another cool demo 00:03:38.220 --> 00:03:41.330 align:start position:0% wanted to show you another cool demo which<00:03:38.880> I<00:03:39.000> didn't<00:03:39.240> have<00:03:39.390> time<00:03:39.750> to<00:03:39.810> finish<00:03:40.340> but 00:03:41.330 --> 00:03:41.340 align:start position:0% which I didn't have time to finish but 00:03:41.340 --> 00:03:43.550 align:start position:0% which I didn't have time to finish but this<00:03:41.760> is<00:03:41.940> called<00:03:42.210> planet<00:03:42.630> Express<00:03:43.170> and<00:03:43.410> it's 00:03:43.550 --> 00:03:43.560 align:start position:0% this is called planet Express and it's 00:03:43.560 --> 00:03:45.560 align:start position:0% this is called planet Express and it's kind<00:03:43.920> of<00:03:43.980> like<00:03:44.160> Twitter<00:03:44.580> you<00:03:44.820> have<00:03:45.000> a<00:03:45.030> feed 00:03:45.560 --> 00:03:45.570 align:start position:0% kind of like Twitter you have a feed 00:03:45.570 --> 00:03:47.480 align:start position:0% kind of like Twitter you have a feed where<00:03:46.230> you<00:03:46.320> can<00:03:46.440> post<00:03:46.620> stuff<00:03:46.950> you<00:03:47.160> can<00:03:47.310> pose 00:03:47.480 --> 00:03:47.490 align:start position:0% where you can post stuff you can pose 00:03:47.490 --> 00:03:51.440 align:start position:0% where you can post stuff you can pose from<00:03:47.930> repost<00:03:49.170> from<00:03:50.130> other<00:03:50.340> users<00:03:50.550> you<00:03:51.000> can<00:03:51.120> pin 00:03:51.440 --> 00:03:51.450 align:start position:0% from repost from other users you can pin 00:03:51.450 --> 00:03:55.340 align:start position:0% from repost from other users you can pin them<00:03:51.690> you<00:03:52.230> can<00:03:52.440> um<00:03:53.060> comment<00:03:54.060> on<00:03:54.420> them<00:03:54.690> and<00:03:54.990> and 00:03:55.340 --> 00:03:55.350 align:start position:0% them you can um comment on them and and 00:03:55.350 --> 00:03:57.710 align:start position:0% them you can um comment on them and and so<00:03:55.650> on<00:03:55.830> and<00:03:56.040> it<00:03:56.130> uses<00:03:56.520> the<00:03:56.670> same<00:03:56.850> technology<00:03:57.120> as 00:03:57.710 --> 00:03:57.720 align:start position:0% so on and it uses the same technology as 00:03:57.720 --> 00:03:59.600 align:start position:0% so on and it uses the same technology as orbit<00:03:58.080> does<00:03:58.230> including<00:03:58.770> you<00:03:58.890> port<00:03:59.220> this<00:03:59.460> is 00:03:59.600 --> 00:03:59.610 align:start position:0% orbit does including you port this is 00:03:59.610 --> 00:04:03.140 align:start position:0% orbit does including you port this is really<00:04:00.000> sweet<00:04:00.180> and<00:04:01.010> what<00:04:02.010> you<00:04:02.130> just<00:04:02.160> saw<00:04:02.580> were 00:04:03.140 --> 00:04:03.150 align:start position:0% really sweet and what you just saw were 00:04:03.150 --> 00:04:04.610 align:start position:0% really sweet and what you just saw were completely<00:04:03.840> distributed<00:04:04.170> real-time 00:04:04.610 --> 00:04:04.620 align:start position:0% completely distributed real-time 00:04:04.620 --> 00:04:07.490 align:start position:0% completely distributed real-time applications<00:04:05.550> with<00:04:05.930> verifiable<00:04:06.930> walk<00:04:07.230> chain 00:04:07.490 --> 00:04:07.500 align:start position:0% applications with verifiable walk chain 00:04:07.500 --> 00:04:10.280 align:start position:0% applications with verifiable walk chain base<00:04:07.710> identities<00:04:08.640> running<00:04:09.330> on<00:04:09.450> desktops<00:04:10.080> and 00:04:10.280 --> 00:04:10.290 align:start position:0% base identities running on desktops and 00:04:10.290 --> 00:04:13.790 align:start position:0% base identities running on desktops and browsers<00:04:11.250> today<00:04:11.870> this<00:04:12.870> is<00:04:13.080> what<00:04:13.260> serverless 00:04:13.790 --> 00:04:13.800 align:start position:0% browsers today this is what serverless 00:04:13.800 --> 00:04:17.240 align:start position:0% browsers today this is what serverless architecture<00:04:14.760> really<00:04:14.970> means<00:04:15.300> and<00:04:15.570> let<00:04:16.410> that 00:04:17.240 --> 00:04:17.250 align:start position:0% architecture really means and let that 00:04:17.250 --> 00:04:19.070 align:start position:0% architecture really means and let that sink<00:04:17.520> in<00:04:17.640> for<00:04:17.790> a<00:04:18.090> while<00:04:18.270> because<00:04:18.480> this<00:04:18.930> is 00:04:19.070 --> 00:04:19.080 align:start position:0% sink in for a while because this is 00:04:19.080 --> 00:04:20.990 align:start position:0% sink in for a while because this is absolutely<00:04:19.770> huge<00:04:20.190> where<00:04:20.549> you've<00:04:20.670> come 00:04:20.990 --> 00:04:21.000 align:start position:0% absolutely huge where you've come 00:04:21.000 --> 00:04:24.670 align:start position:0% absolutely huge where you've come incredibly<00:04:21.989> far<00:04:22.320> in<00:04:22.560> just<00:04:22.620> a<00:04:23.280> few<00:04:23.460> years 00:04:24.670 --> 00:04:24.680 align:start position:0% incredibly far in just a few years 00:04:24.680 --> 00:04:28.280 align:start position:0% incredibly far in just a few years on<00:04:25.970> underneath<00:04:26.970> orbit<00:04:27.570> there's<00:04:27.780> a<00:04:27.840> peer<00:04:28.170> to 00:04:28.280 --> 00:04:28.290 align:start position:0% on underneath orbit there's a peer to 00:04:28.290 --> 00:04:31.160 align:start position:0% on underneath orbit there's a peer to peer<00:04:28.440> database<00:04:28.950> called<00:04:29.220> orbit<00:04:29.580> DB<00:04:29.940> um<00:04:30.180> it 00:04:31.160 --> 00:04:31.170 align:start position:0% peer database called orbit DB um it 00:04:31.170 --> 00:04:32.290 align:start position:0% peer database called orbit DB um it gives<00:04:31.440> you 00:04:32.290 --> 00:04:32.300 align:start position:0% gives you 00:04:32.300 --> 00:04:36.260 align:start position:0% gives you various<00:04:33.300> types<00:04:33.600> of<00:04:33.780> the<00:04:34.130> databases<00:04:35.130> event<00:04:36.060> log 00:04:36.260 --> 00:04:36.270 align:start position:0% various types of the databases event log 00:04:36.270 --> 00:04:37.909 align:start position:0% various types of the databases event log where<00:04:36.510> you<00:04:36.570> can<00:04:36.720> only<00:04:36.870> add<00:04:37.080> messages<00:04:37.320> but<00:04:37.830> you 00:04:37.909 --> 00:04:37.919 align:start position:0% where you can only add messages but you 00:04:37.919 --> 00:04:40.070 align:start position:0% where you can only add messages but you can<00:04:38.100> delete<00:04:38.490> them<00:04:38.640> if<00:04:39.000> he<00:04:39.270> is<00:04:39.479> the<00:04:39.600> same<00:04:39.780> as<00:04:39.930> the 00:04:40.070 --> 00:04:40.080 align:start position:0% can delete them if he is the same as the 00:04:40.080 --> 00:04:41.480 align:start position:0% can delete them if he is the same as the event<00:04:40.229> log<00:04:40.410> but<00:04:40.680> you<00:04:40.800> can<00:04:40.919> you<00:04:41.280> and<00:04:41.370> also 00:04:41.480 --> 00:04:41.490 align:start position:0% event log but you can you and also 00:04:41.490 --> 00:04:44.360 align:start position:0% event log but you can you and also delete<00:04:42.000> messages<00:04:42.510> a<00:04:42.720> key-value<00:04:43.620> store<00:04:43.889> just 00:04:44.360 --> 00:04:44.370 align:start position:0% delete messages a key-value store just 00:04:44.370 --> 00:04:46.310 align:start position:0% delete messages a key-value store just like<00:04:44.490> any<00:04:44.760> other<00:04:44.970> key<00:04:45.240> value<00:04:45.540> store<00:04:45.780> you<00:04:46.139> know 00:04:46.310 --> 00:04:46.320 align:start position:0% like any other key value store you know 00:04:46.320 --> 00:04:49.790 align:start position:0% like any other key value store you know but<00:04:46.920> peer-to-peer<00:04:47.460> and<00:04:48.440> counters<00:04:49.440> which<00:04:49.650> are 00:04:49.790 --> 00:04:49.800 align:start position:0% but peer-to-peer and counters which are 00:04:49.800 --> 00:04:52.400 align:start position:0% but peer-to-peer and counters which are really<00:04:50.010> useful<00:04:50.130> for<00:04:50.669> stuff<00:04:51.120> like<00:04:51.210> votes<00:04:52.050> and 00:04:52.400 --> 00:04:52.410 align:start position:0% really useful for stuff like votes and 00:04:52.410 --> 00:04:55.159 align:start position:0% really useful for stuff like votes and lights<00:04:52.680> and<00:04:53.040> and<00:04:53.250> so<00:04:53.639> on<00:04:53.790> you<00:04:54.570> can<00:04:54.690> also<00:04:54.870> easily 00:04:55.159 --> 00:04:55.169 align:start position:0% lights and and so on you can also easily 00:04:55.169 --> 00:04:57.980 align:start position:0% lights and and so on you can also easily implement<00:04:55.830> other<00:04:55.950> types<00:04:56.310> of<00:04:56.600> databases<00:04:57.600> like 00:04:57.980 --> 00:04:57.990 align:start position:0% implement other types of databases like 00:04:57.990 --> 00:05:01.220 align:start position:0% implement other types of databases like index<00:04:58.740> documents<00:04:59.430> or<00:04:59.639> kind<00:05:00.570> of<00:05:00.630> like<00:05:00.690> MongoDB 00:05:01.220 --> 00:05:01.230 align:start position:0% index documents or kind of like MongoDB 00:05:01.230 --> 00:05:03.310 align:start position:0% index documents or kind of like MongoDB or<00:05:01.740> so<00:05:01.919> on 00:05:03.310 --> 00:05:03.320 align:start position:0% or so on 00:05:03.320 --> 00:05:07.610 align:start position:0% or so on Orbitz<00:05:04.320> DVDs<00:05:04.889> um<00:05:05.360> ipfs<00:05:06.360> lock<00:05:06.660> for<00:05:07.050> database 00:05:07.610 --> 00:05:07.620 align:start position:0% Orbitz DVDs um ipfs lock for database 00:05:07.620 --> 00:05:10.540 align:start position:0% Orbitz DVDs um ipfs lock for database operations<00:05:08.310> log<00:05:08.700> it's<00:05:08.820> an<00:05:09.060> append-only 00:05:10.540 --> 00:05:10.550 align:start position:0% operations log it's an append-only 00:05:10.550 --> 00:05:13.490 align:start position:0% operations log it's an append-only partially<00:05:11.550> ordered<00:05:11.870> eventually<00:05:12.870> consistent 00:05:13.490 --> 00:05:13.500 align:start position:0% partially ordered eventually consistent 00:05:13.500 --> 00:05:16.960 align:start position:0% partially ordered eventually consistent Merkle<00:05:14.280> tree<00:05:14.640> of<00:05:14.910> database<00:05:15.450> operations 00:05:16.960 --> 00:05:16.970 align:start position:0% Merkle tree of database operations 00:05:16.970 --> 00:05:22.210 align:start position:0% Merkle tree of database operations basically<00:05:17.970> a<00:05:18.000> linked<00:05:18.390> list<00:05:18.419> of<00:05:18.960> IVA<00:05:19.380> hashes<00:05:20.250> um 00:05:22.210 --> 00:05:22.220 align:start position:0% basically a linked list of IVA hashes um 00:05:22.220 --> 00:05:25.550 align:start position:0% basically a linked list of IVA hashes um so<00:05:23.220> having<00:05:23.820> an<00:05:24.000> operation<00:05:24.450> log<00:05:24.780> allows<00:05:25.140> us<00:05:25.380> to 00:05:25.550 --> 00:05:25.560 align:start position:0% so having an operation log allows us to 00:05:25.560 --> 00:05:27.650 align:start position:0% so having an operation log allows us to use<00:05:25.680> CR<00:05:26.070> DTS 00:05:27.650 --> 00:05:27.660 align:start position:0% use CR DTS 00:05:27.660 --> 00:05:31.040 align:start position:0% use CR DTS they<00:05:27.990> basically<00:05:28.290> allow<00:05:28.680> us<00:05:29.040> to<00:05:29.310> merge<00:05:29.640> data<00:05:30.050> in 00:05:31.040 --> 00:05:31.050 align:start position:0% they basically allow us to merge data in 00:05:31.050 --> 00:05:34.790 align:start position:0% they basically allow us to merge data in a<00:05:31.410> way<00:05:31.590> that<00:05:31.620> there<00:05:32.010> are<00:05:32.130> never<00:05:32.460> conflicts<00:05:33.800> I 00:05:34.790 --> 00:05:34.800 align:start position:0% a way that there are never conflicts I 00:05:34.800 --> 00:05:36.860 align:start position:0% a way that there are never conflicts I would<00:05:35.520> highly<00:05:35.820> recommend<00:05:35.850> you<00:05:36.330> to<00:05:36.570> look<00:05:36.600> into 00:05:36.860 --> 00:05:36.870 align:start position:0% would highly recommend you to look into 00:05:36.870 --> 00:05:40.159 align:start position:0% would highly recommend you to look into CR<00:05:37.410> DD<00:05:37.710> sir<00:05:38.040> they're<00:05:38.490> extremely<00:05:39.000> cool<00:05:39.389> data 00:05:40.159 --> 00:05:40.169 align:start position:0% CR DD sir they're extremely cool data 00:05:40.169 --> 00:05:43.070 align:start position:0% CR DD sir they're extremely cool data structures<00:05:40.880> so<00:05:41.880> once<00:05:42.360> we<00:05:42.540> have<00:05:42.720> distributed 00:05:43.070 --> 00:05:43.080 align:start position:0% structures so once we have distributed 00:05:43.080 --> 00:05:45.380 align:start position:0% structures so once we have distributed data<00:05:43.530> structures<00:05:44.010> in<00:05:44.190> place<00:05:44.370> we<00:05:45.030> need<00:05:45.210> to 00:05:45.380 --> 00:05:45.390 align:start position:0% data structures in place we need to 00:05:45.390 --> 00:05:47.900 align:start position:0% data structures in place we need to replicate<00:05:45.570> the<00:05:45.960> data<00:05:46.169> between<00:05:46.830> the<00:05:47.400> peers<00:05:47.700> and 00:05:47.900 --> 00:05:47.910 align:start position:0% replicate the data between the peers and 00:05:47.910 --> 00:05:51.310 align:start position:0% replicate the data between the peers and orbit<00:05:48.720> DV<00:05:48.990> uses<00:05:49.350> IVFs<00:05:49.860> pops<00:05:50.310> up<00:05:50.610> on 00:05:51.310 --> 00:05:51.320 align:start position:0% orbit DV uses IVFs pops up on 00:05:51.320 --> 00:05:55.010 align:start position:0% orbit DV uses IVFs pops up on for<00:05:52.320> propagating<00:05:53.070> the<00:05:53.370> database<00:05:54.020> operations 00:05:55.010 --> 00:05:55.020 align:start position:0% for propagating the database operations 00:05:55.020 --> 00:05:59.060 align:start position:0% for propagating the database operations from<00:05:55.380> the<00:05:55.710> operation<00:05:56.460> log<00:05:56.700> to<00:05:57.479> the<00:05:57.840> network<00:05:58.440> so 00:05:59.060 --> 00:05:59.070 align:start position:0% from the operation log to the network so 00:05:59.070 --> 00:06:03.590 align:start position:0% from the operation log to the network so in<00:05:59.570> Orbitz<00:06:00.570> case<00:06:01.310> when<00:06:02.310> I<00:06:02.340> send<00:06:02.640> a<00:06:02.700> message<00:06:02.729> the 00:06:03.590 --> 00:06:03.600 align:start position:0% in Orbitz case when I send a message the 00:06:03.600 --> 00:06:05.300 align:start position:0% in Orbitz case when I send a message the message<00:06:03.720> gets<00:06:04.140> created<00:06:04.590> and<00:06:04.740> signed<00:06:04.919> with<00:06:05.160> my 00:06:05.300 --> 00:06:05.310 align:start position:0% message gets created and signed with my 00:06:05.310 --> 00:06:06.950 align:start position:0% message gets created and signed with my public<00:06:05.729> signing<00:06:06.060> key<00:06:06.210> the<00:06:06.479> one<00:06:06.600> that<00:06:06.810> was 00:06:06.950 --> 00:06:06.960 align:start position:0% public signing key the one that was 00:06:06.960 --> 00:06:10.310 align:start position:0% public signing key the one that was added<00:06:07.260> to<00:06:07.440> my<00:06:07.560> on<00:06:07.830> you<00:06:08.729> Ford<00:06:09.000> profile<00:06:09.419> we<00:06:10.110> then 00:06:10.310 --> 00:06:10.320 align:start position:0% added to my on you Ford profile we then 00:06:10.320 --> 00:06:13.250 align:start position:0% added to my on you Ford profile we then add<00:06:10.590> the<00:06:11.330> operation<00:06:12.330> to<00:06:12.479> the<00:06:12.570> database<00:06:13.020> and 00:06:13.250 --> 00:06:13.260 align:start position:0% add the operation to the database and 00:06:13.260 --> 00:06:16.250 align:start position:0% add the operation to the database and the<00:06:13.650> head<00:06:13.860> hash<00:06:14.220> of<00:06:14.580> the<00:06:14.970> operation<00:06:15.570> log<00:06:15.810> gets 00:06:16.250 --> 00:06:16.260 align:start position:0% the head hash of the operation log gets 00:06:16.260 --> 00:06:19.070 align:start position:0% the head hash of the operation log gets sent<00:06:16.620> to<00:06:16.710> pops<00:06:17.370> a<00:06:17.610> topic<00:06:18.120> which<00:06:18.570> in<00:06:18.750> this<00:06:18.870> case 00:06:19.070 --> 00:06:19.080 align:start position:0% sent to pops a topic which in this case 00:06:19.080 --> 00:06:21.620 align:start position:0% sent to pops a topic which in this case is<00:06:19.350> the<00:06:19.620> name<00:06:20.100> of<00:06:20.310> the<00:06:20.430> channel<00:06:20.669> and<00:06:20.970> that's 00:06:21.620 --> 00:06:21.630 align:start position:0% is the name of the channel and that's 00:06:21.630 --> 00:06:24.050 align:start position:0% is the name of the channel and that's how<00:06:21.840> the<00:06:22.470> data<00:06:22.650> gets<00:06:22.740> eventually<00:06:23.430> consistent 00:06:24.050 --> 00:06:24.060 align:start position:0% how the data gets eventually consistent 00:06:24.060 --> 00:06:26.240 align:start position:0% how the data gets eventually consistent across<00:06:24.539> the<00:06:24.810> peers<00:06:25.080> and<00:06:25.289> everyone<00:06:25.770> sees<00:06:26.010> the 00:06:26.240 --> 00:06:26.250 align:start position:0% across the peers and everyone sees the 00:06:26.250 --> 00:06:28.300 align:start position:0% across the peers and everyone sees the the<00:06:26.490> same<00:06:27.150> data 00:06:28.300 --> 00:06:28.310 align:start position:0% the same data 00:06:28.310 --> 00:06:31.400 align:start position:0% the same data so<00:06:29.310> orbit<00:06:30.180> DV<00:06:30.450> works<00:06:30.720> really<00:06:30.990> nicely<00:06:31.229> for 00:06:31.400 --> 00:06:31.410 align:start position:0% so orbit DV works really nicely for 00:06:31.410 --> 00:06:33.560 align:start position:0% so orbit DV works really nicely for application<00:06:32.340> databases<00:06:32.940> and<00:06:33.180> is<00:06:33.300> quite 00:06:33.560 --> 00:06:33.570 align:start position:0% application databases and is quite 00:06:33.570 --> 00:06:36.950 align:start position:0% application databases and is quite performant<00:06:34.200> but<00:06:34.320> there's<00:06:34.530> no<00:06:35.160> saving<00:06:36.120> of<00:06:36.600> the 00:06:36.950 --> 00:06:36.960 align:start position:0% performant but there's no saving of the 00:06:36.960 --> 00:06:39.620 align:start position:0% performant but there's no saving of the database<00:06:37.410> so<00:06:37.710> what<00:06:38.490> would<00:06:38.610> be<00:06:38.669> really<00:06:39.150> cool<00:06:39.390> is 00:06:39.620 --> 00:06:39.630 align:start position:0% database so what would be really cool is 00:06:39.630 --> 00:06:42.710 align:start position:0% database so what would be really cool is to<00:06:39.990> timestamp<00:06:40.680> the<00:06:40.919> hit<00:06:41.460> hash<00:06:41.700> of<00:06:42.090> the<00:06:42.240> log<00:06:42.450> or 00:06:42.710 --> 00:06:42.720 align:start position:0% to timestamp the hit hash of the log or 00:06:42.720 --> 00:06:45.170 align:start position:0% to timestamp the hit hash of the log or snapshot<00:06:43.680> it<00:06:43.830> periodically<00:06:44.280> into<00:06:45.030> the 00:06:45.170 --> 00:06:45.180 align:start position:0% snapshot it periodically into the 00:06:45.180 --> 00:06:46.540 align:start position:0% snapshot it periodically into the blockchain 00:06:46.540 --> 00:06:46.550 align:start position:0% blockchain 00:06:46.550 --> 00:06:49.880 align:start position:0% blockchain you<00:06:47.550> may<00:06:47.700> think<00:06:48.000> why<00:06:48.750> so<00:06:49.050> complicated<00:06:49.770> why 00:06:49.880 --> 00:06:49.890 align:start position:0% you may think why so complicated why 00:06:49.890 --> 00:06:51.980 align:start position:0% you may think why so complicated why can't<00:06:50.159> we<00:06:50.280> just<00:06:50.460> replicate<00:06:51.120> my<00:06:51.539> sequel 00:06:51.980 --> 00:06:51.990 align:start position:0% can't we just replicate my sequel 00:06:51.990 --> 00:06:55.119 align:start position:0% can't we just replicate my sequel databases<00:06:52.470> between<00:06:52.979> the<00:06:53.130> peers<00:06:53.599> in 00:06:55.119 --> 00:06:55.129 align:start position:0% databases between the peers in 00:06:55.129 --> 00:06:57.369 align:start position:0% databases between the peers in tribute<00:06:55.550> systems<00:06:56.089> time<00:06:56.779> is<00:06:57.050> a<00:06:57.080> very 00:06:57.369 --> 00:06:57.379 align:start position:0% tribute systems time is a very 00:06:57.379 --> 00:06:59.679 align:start position:0% tribute systems time is a very subjective<00:06:57.649> matter<00:06:58.249> and<00:06:58.550> without<00:06:59.119> a<00:06:59.149> central 00:06:59.679 --> 00:06:59.689 align:start position:0% subjective matter and without a central 00:06:59.689 --> 00:07:01.299 align:start position:0% subjective matter and without a central authority<00:06:59.869> we<00:07:00.499> don't<00:07:00.649> know<00:07:00.830> what<00:07:01.039> the<00:07:01.159> order 00:07:01.299 --> 00:07:01.309 align:start position:0% authority we don't know what the order 00:07:01.309 --> 00:07:04.600 align:start position:0% authority we don't know what the order of<00:07:01.610> the<00:07:01.729> messages<00:07:02.209> are<00:07:02.449> and<00:07:02.689> this<00:07:03.379> is<00:07:03.739> what<00:07:04.129> the 00:07:04.600 --> 00:07:04.610 align:start position:0% of the messages are and this is what the 00:07:04.610 --> 00:07:06.999 align:start position:0% of the messages are and this is what the CR<00:07:04.909> DT<00:07:05.269> sold<00:07:05.629> and<00:07:05.809> this<00:07:06.169> is<00:07:06.319> why<00:07:06.469> they<00:07:06.619> work<00:07:06.800> so 00:07:06.999 --> 00:07:07.009 align:start position:0% CR DT sold and this is why they work so 00:07:07.009 --> 00:07:09.570 align:start position:0% CR DT sold and this is why they work so well<00:07:07.039> in<00:07:07.459> distributed<00:07:08.449> systems 00:07:09.570 --> 00:07:09.580 align:start position:0% well in distributed systems 00:07:09.580 --> 00:07:13.119 align:start position:0% well in distributed systems so<00:07:10.580> we<00:07:10.969> have<00:07:11.149> ipfs<00:07:11.929> for<00:07:12.199> storage<00:07:12.769> an 00:07:13.119 --> 00:07:13.129 align:start position:0% so we have ipfs for storage an 00:07:13.129 --> 00:07:15.909 align:start position:0% so we have ipfs for storage an append-only<00:07:13.639> lock<00:07:14.059> for<00:07:14.599> data<00:07:14.929> transport<00:07:15.529> C<00:07:15.889> R 00:07:15.909 --> 00:07:15.919 align:start position:0% append-only lock for data transport C R 00:07:15.919 --> 00:07:18.929 align:start position:0% append-only lock for data transport C R DT<00:07:16.189> s<00:07:16.399> to<00:07:16.580> create<00:07:16.819> databases<00:07:17.569> on<00:07:17.959> top<00:07:18.199> of<00:07:18.379> on 00:07:18.929 --> 00:07:18.939 align:start position:0% DT s to create databases on top of on 00:07:18.939 --> 00:07:21.969 align:start position:0% DT s to create databases on top of on the<00:07:19.939> storage<00:07:20.300> and<00:07:20.599> we<00:07:20.749> have<00:07:20.929> pops<00:07:21.439> up<00:07:21.679> for 00:07:21.969 --> 00:07:21.979 align:start position:0% the storage and we have pops up for 00:07:21.979 --> 00:07:25.119 align:start position:0% the storage and we have pops up for superfast<00:07:22.809> Messick's<00:07:23.869> message<00:07:24.409> propagation 00:07:25.119 --> 00:07:25.129 align:start position:0% superfast Messick's message propagation 00:07:25.129 --> 00:07:28.059 align:start position:0% superfast Messick's message propagation that<00:07:25.309> enables<00:07:26.300> a<00:07:26.569> peer-to-peer<00:07:27.080> application 00:07:28.059 --> 00:07:28.069 align:start position:0% that enables a peer-to-peer application 00:07:28.069 --> 00:07:32.019 align:start position:0% that enables a peer-to-peer application and<00:07:28.279> we<00:07:29.059> have<00:07:29.269> a<00:07:29.479> theorem<00:07:30.019> for<00:07:31.029> authenticating 00:07:32.019 --> 00:07:32.029 align:start position:0% and we have a theorem for authenticating 00:07:32.029 --> 00:07:35.559 align:start position:0% and we have a theorem for authenticating and<00:07:32.149> verifying<00:07:32.809> data<00:07:33.189> people<00:07:34.569> transactions 00:07:35.559 --> 00:07:35.569 align:start position:0% and verifying data people transactions 00:07:35.569 --> 00:07:38.409 align:start position:0% and verifying data people transactions payments<00:07:36.349> and<00:07:36.499> so<00:07:36.649> on<00:07:36.830> combining<00:07:37.789> all<00:07:38.149> these 00:07:38.409 --> 00:07:38.419 align:start position:0% payments and so on combining all these 00:07:38.419 --> 00:07:40.749 align:start position:0% payments and so on combining all these we<00:07:38.929> finally<00:07:39.499> have<00:07:39.740> all<00:07:39.769> the<00:07:40.009> primitives<00:07:40.639> that 00:07:40.749 --> 00:07:40.759 align:start position:0% we finally have all the primitives that 00:07:40.759 --> 00:07:42.820 align:start position:0% we finally have all the primitives that we<00:07:40.909> need<00:07:41.269> to<00:07:41.569> build<00:07:41.719> truly<00:07:42.469> powerful 00:07:42.820 --> 00:07:42.830 align:start position:0% we need to build truly powerful 00:07:42.830 --> 00:07:44.290 align:start position:0% we need to build truly powerful distributed<00:07:43.610> peer-to-peer<00:07:43.819> applications 00:07:44.290 --> 00:07:44.300 align:start position:0% distributed peer-to-peer applications 00:07:44.300 --> 00:07:46.889 align:start position:0% distributed peer-to-peer applications that<00:07:45.229> also<00:07:45.619> work<00:07:45.769> in<00:07:45.949> the<00:07:45.979> browser<00:07:46.219> on 00:07:46.889 --> 00:07:46.899 align:start position:0% that also work in the browser on 00:07:46.899 --> 00:07:49.419 align:start position:0% that also work in the browser on different<00:07:47.899> types<00:07:48.110> of<00:07:48.319> databases<00:07:48.769> dynamic 00:07:49.419 --> 00:07:49.429 align:start position:0% different types of databases dynamic 00:07:49.429 --> 00:07:51.279 align:start position:0% different types of databases dynamic content<00:07:49.879> even<00:07:50.119> live<00:07:50.360> video<00:07:50.689> streaming<00:07:51.079> is 00:07:51.279 --> 00:07:51.289 align:start position:0% content even live video streaming is 00:07:51.289 --> 00:07:54.519 align:start position:0% content even live video streaming is possible<00:07:51.860> I<00:07:52.479> can't<00:07:53.479> emphasize<00:07:53.689> enough<00:07:54.110> how 00:07:54.519 --> 00:07:54.529 align:start position:0% possible I can't emphasize enough how 00:07:54.529 --> 00:07:57.419 align:start position:0% possible I can't emphasize enough how profound<00:07:55.519> the<00:07:56.059> sack<00:07:56.419> is 00:07:57.419 --> 00:07:57.429 align:start position:0% profound the sack is 00:07:57.429 --> 00:08:01.269 align:start position:0% profound the sack is so<00:07:58.779> with<00:07:59.779> these<00:07:59.899> new<00:08:00.139> superpowers<00:08:00.919> we<00:08:01.099> should 00:08:01.269 --> 00:08:01.279 align:start position:0% so with these new superpowers we should 00:08:01.279 --> 00:08:04.029 align:start position:0% so with these new superpowers we should also<00:08:01.429> consider<00:08:01.729> what<00:08:02.419> and<00:08:02.719> how<00:08:03.019> we<00:08:03.619> build<00:08:03.800> our 00:08:04.029 --> 00:08:04.039 align:start position:0% also consider what and how we build our 00:08:04.039 --> 00:08:06.759 align:start position:0% also consider what and how we build our applications<00:08:04.990> we<00:08:05.990> don't<00:08:06.169> want<00:08:06.409> to<00:08:06.589> just 00:08:06.759 --> 00:08:06.769 align:start position:0% applications we don't want to just 00:08:06.769 --> 00:08:09.959 align:start position:0% applications we don't want to just blindly<00:08:07.490> follow<00:08:07.819> the<00:08:08.029> web<00:08:08.179> 2.0<00:08:08.839> paradigms<00:08:09.529> and 00:08:09.959 --> 00:08:09.969 align:start position:0% blindly follow the web 2.0 paradigms and 00:08:09.969 --> 00:08:12.279 align:start position:0% blindly follow the web 2.0 paradigms and we<00:08:10.969> need<00:08:11.119> to<00:08:11.240> consider<00:08:11.659> what<00:08:12.079> are<00:08:12.229> the 00:08:12.279 --> 00:08:12.289 align:start position:0% we need to consider what are the 00:08:12.289 --> 00:08:15.689 align:start position:0% we need to consider what are the properties<00:08:12.889> of<00:08:13.269> distributed<00:08:14.269> applications 00:08:15.689 --> 00:08:15.699 align:start position:0% properties of distributed applications 00:08:15.699 --> 00:08:18.639 align:start position:0% properties of distributed applications today<00:08:16.699> pretty<00:08:17.329> much<00:08:17.569> nothing<00:08:17.839> works<00:08:18.319> if 00:08:18.639 --> 00:08:18.649 align:start position:0% today pretty much nothing works if 00:08:18.649 --> 00:08:20.259 align:start position:0% today pretty much nothing works if you're<00:08:18.919> not<00:08:19.129> connected<00:08:19.550> to<00:08:19.939> the<00:08:20.059> backbone 00:08:20.259 --> 00:08:20.269 align:start position:0% you're not connected to the backbone 00:08:20.269 --> 00:08:23.529 align:start position:0% you're not connected to the backbone this<00:08:21.079> is<00:08:21.229> a<00:08:21.259> huge<00:08:21.740> huge<00:08:22.099> problem<00:08:22.339> we<00:08:23.329> need<00:08:23.509> to 00:08:23.529 --> 00:08:23.539 align:start position:0% this is a huge huge problem we need to 00:08:23.539 --> 00:08:25.779 align:start position:0% this is a huge huge problem we need to make<00:08:23.749> sure<00:08:23.929> that<00:08:24.139> our<00:08:24.199> applications<00:08:25.129> work 00:08:25.779 --> 00:08:25.789 align:start position:0% make sure that our applications work 00:08:25.789 --> 00:08:28.540 align:start position:0% make sure that our applications work offline<00:08:26.269> first<00:08:26.719> and<00:08:26.929> foremost<00:08:27.409> there's<00:08:28.249> a<00:08:28.339> new 00:08:28.540 --> 00:08:28.550 align:start position:0% offline first and foremost there's a new 00:08:28.550 --> 00:08:30.189 align:start position:0% offline first and foremost there's a new trend<00:08:28.999> in<00:08:29.149> web<00:08:29.300> development<00:08:29.629> called 00:08:30.189 --> 00:08:30.199 align:start position:0% trend in web development called 00:08:30.199 --> 00:08:32.379 align:start position:0% trend in web development called progressive<00:08:30.679> web<00:08:31.129> applications<00:08:31.879> which<00:08:32.180> is<00:08:32.209> a 00:08:32.379 --> 00:08:32.389 align:start position:0% progressive web applications which is a 00:08:32.389 --> 00:08:34.149 align:start position:0% progressive web applications which is a great<00:08:32.689> direction<00:08:33.199> but<00:08:33.380> with<00:08:33.949> these 00:08:34.149 --> 00:08:34.159 align:start position:0% great direction but with these 00:08:34.159 --> 00:08:36.519 align:start position:0% great direction but with these technologies<00:08:34.810> offline<00:08:35.810> becomes<00:08:36.199> an<00:08:36.349> inherent 00:08:36.519 --> 00:08:36.529 align:start position:0% technologies offline becomes an inherent 00:08:36.529 --> 00:08:40.059 align:start position:0% technologies offline becomes an inherent implicit<00:08:37.519> property<00:08:38.389> and<00:08:38.569> we<00:08:39.199> can<00:08:39.380> make<00:08:39.560> it<00:08:39.740> so 00:08:40.059 --> 00:08:40.069 align:start position:0% implicit property and we can make it so 00:08:40.069 --> 00:08:42.730 align:start position:0% implicit property and we can make it so much<00:08:40.219> easier<00:08:40.550> and<00:08:40.969> better<00:08:41.180> for<00:08:41.779> all<00:08:42.229> the 00:08:42.730 --> 00:08:42.740 align:start position:0% much easier and better for all the 00:08:42.740 --> 00:08:44.860 align:start position:0% much easier and better for all the developers<00:08:43.189> around<00:08:43.430> the<00:08:43.699> world<00:08:43.880> than<00:08:44.209> it<00:08:44.630> is 00:08:44.860 --> 00:08:44.870 align:start position:0% developers around the world than it is 00:08:44.870 --> 00:08:46.769 align:start position:0% developers around the world than it is today<00:08:45.160> um 00:08:46.769 --> 00:08:46.779 align:start position:0% today um 00:08:46.779 --> 00:08:49.120 align:start position:0% today um this<00:08:47.779> should<00:08:47.810> be<00:08:48.050> pretty<00:08:48.350> obvious<00:08:48.470> to<00:08:49.009> the 00:08:49.120 --> 00:08:49.130 align:start position:0% this should be pretty obvious to the 00:08:49.130 --> 00:08:50.769 align:start position:0% this should be pretty obvious to the crowd<00:08:49.339> here<00:08:49.610> but<00:08:49.880> let's<00:08:50.149> make<00:08:50.329> sure<00:08:50.389> that<00:08:50.540> our 00:08:50.769 --> 00:08:50.779 align:start position:0% crowd here but let's make sure that our 00:08:50.779 --> 00:08:52.809 align:start position:0% crowd here but let's make sure that our applications<00:08:51.620> don't<00:08:51.800> depend<00:08:52.130> on<00:08:52.279> services 00:08:52.809 --> 00:08:52.819 align:start position:0% applications don't depend on services 00:08:52.819 --> 00:08:55.210 align:start position:0% applications don't depend on services that<00:08:52.850> can<00:08:53.269> just<00:08:53.509> disappear<00:08:53.720> can<00:08:54.529> be<00:08:54.680> shut<00:08:54.920> down 00:08:55.210 --> 00:08:55.220 align:start position:0% that can just disappear can be shut down 00:08:55.220 --> 00:08:58.860 align:start position:0% that can just disappear can be shut down or<00:08:55.579> otherwise<00:08:56.509> to<00:08:57.170> cease<00:08:57.410> to<00:08:57.620> exist 00:08:58.860 --> 00:08:58.870 align:start position:0% or otherwise to cease to exist 00:08:58.870 --> 00:09:01.179 align:start position:0% or otherwise to cease to exist we're<00:08:59.870> pretty<00:09:00.110> much<00:09:00.290> locked<00:09:00.620> in<00:09:00.769> with<00:09:01.009> our 00:09:01.179 --> 00:09:01.189 align:start position:0% we're pretty much locked in with our 00:09:01.189 --> 00:09:04.059 align:start position:0% we're pretty much locked in with our data<00:09:01.459> do<00:09:02.300> the<00:09:02.420> services<00:09:02.930> we<00:09:03.079> use<00:09:03.110> today<00:09:03.589> we 00:09:04.059 --> 00:09:04.069 align:start position:0% data do the services we use today we 00:09:04.069 --> 00:09:06.009 align:start position:0% data do the services we use today we can't<00:09:04.339> share<00:09:04.639> data<00:09:04.910> between<00:09:05.029> applications 00:09:06.009 --> 00:09:06.019 align:start position:0% can't share data between applications 00:09:06.019 --> 00:09:07.420 align:start position:0% can't share data between applications let<00:09:06.290> it<00:09:06.380> alone<00:09:06.529> and<00:09:06.709> have<00:09:06.829> any<00:09:06.980> control<00:09:07.399> over 00:09:07.420 --> 00:09:07.430 align:start position:0% let it alone and have any control over 00:09:07.430 --> 00:09:10.840 align:start position:0% let it alone and have any control over our<00:09:08.209> personal<00:09:08.540> data<00:09:08.779> this<00:09:09.740> is<00:09:09.920> not<00:09:10.100> cool<00:09:10.459> this 00:09:10.840 --> 00:09:10.850 align:start position:0% our personal data this is not cool this 00:09:10.850 --> 00:09:13.299 align:start position:0% our personal data this is not cool this is<00:09:11.029> not<00:09:11.059> the<00:09:11.389> internet<00:09:11.809> we<00:09:11.959> wanted<00:09:12.290> we<00:09:13.040> need<00:09:13.189> to 00:09:13.299 --> 00:09:13.309 align:start position:0% is not the internet we wanted we need to 00:09:13.309 --> 00:09:15.280 align:start position:0% is not the internet we wanted we need to make<00:09:13.459> sure<00:09:13.490> that<00:09:13.850> the<00:09:14.240> applications<00:09:14.869> we<00:09:15.019> build 00:09:15.280 --> 00:09:15.290 align:start position:0% make sure that the applications we build 00:09:15.290 --> 00:09:17.139 align:start position:0% make sure that the applications we build can<00:09:15.769> share<00:09:16.040> the<00:09:16.220> data<00:09:16.249> between<00:09:16.699> other 00:09:17.139 --> 00:09:17.149 align:start position:0% can share the data between other 00:09:17.149 --> 00:09:20.919 align:start position:0% can share the data between other programs<00:09:17.749> you<00:09:18.649> know<00:09:18.769> you<00:09:19.069> use<00:09:19.670> um<00:09:19.910> linked<00:09:20.629> data 00:09:20.919 --> 00:09:20.929 align:start position:0% programs you know you use um linked data 00:09:20.929 --> 00:09:23.470 align:start position:0% programs you know you use um linked data to<00:09:21.679> create<00:09:22.189> relationships<00:09:22.730> between<00:09:23.209> the 00:09:23.470 --> 00:09:23.480 align:start position:0% to create relationships between the 00:09:23.480 --> 00:09:26.410 align:start position:0% to create relationships between the nuggets<00:09:23.839> of<00:09:23.929> data<00:09:24.199> and<00:09:24.499> use<00:09:25.490> standard<00:09:26.149> data 00:09:26.410 --> 00:09:26.420 align:start position:0% nuggets of data and use standard data 00:09:26.420 --> 00:09:28.299 align:start position:0% nuggets of data and use standard data structures<00:09:27.019> as<00:09:27.230> much<00:09:27.410> as<00:09:27.619> possible<00:09:27.829> so<00:09:28.129> you 00:09:28.299 --> 00:09:28.309 align:start position:0% structures as much as possible so you 00:09:28.309 --> 00:09:30.489 align:start position:0% structures as much as possible so you know<00:09:28.670> like<00:09:28.790> a<00:09:28.850> chat<00:09:29.179> message<00:09:29.420> in<00:09:29.959> one<00:09:30.199> chat 00:09:30.489 --> 00:09:30.499 align:start position:0% know like a chat message in one chat 00:09:30.499 --> 00:09:32.769 align:start position:0% know like a chat message in one chat application<00:09:31.160> is<00:09:31.339> probably<00:09:32.149> the<00:09:32.269> same<00:09:32.449> as<00:09:32.480> it 00:09:32.769 --> 00:09:32.779 align:start position:0% application is probably the same as it 00:09:32.779 --> 00:09:35.590 align:start position:0% application is probably the same as it in<00:09:32.899> is<00:09:33.139> in<00:09:33.740> other<00:09:34.129> data<00:09:34.790> application<00:09:35.389> then<00:09:35.569> a 00:09:35.590 --> 00:09:35.600 align:start position:0% in is in other data application then a 00:09:35.600 --> 00:09:39.730 align:start position:0% in is in other data application then a feed<00:09:36.199> is<00:09:36.439> just<00:09:36.949> a<00:09:37.040> feed<00:09:37.490> viewed<00:09:38.329> and<00:09:38.740> packaged 00:09:39.730 --> 00:09:39.740 align:start position:0% feed is just a feed viewed and packaged 00:09:39.740 --> 00:09:41.489 align:start position:0% feed is just a feed viewed and packaged differently 00:09:41.489 --> 00:09:41.499 align:start position:0% differently 00:09:41.499 --> 00:09:45.220 align:start position:0% differently as<00:09:42.499> we<00:09:42.740> develop<00:09:43.279> our<00:09:43.429> attack<00:09:43.699> we<00:09:44.360> also<00:09:44.749> need<00:09:45.110> to 00:09:45.220 --> 00:09:45.230 align:start position:0% as we develop our attack we also need to 00:09:45.230 --> 00:09:46.540 align:start position:0% as we develop our attack we also need to make<00:09:45.350> sure<00:09:45.379> to<00:09:45.559> provide<00:09:46.100> a<00:09:46.129> smooth 00:09:46.540 --> 00:09:46.550 align:start position:0% make sure to provide a smooth 00:09:46.550 --> 00:09:49.809 align:start position:0% make sure to provide a smooth integration<00:09:47.029> path<00:09:47.660> on<00:09:48.339> otherwise<00:09:49.339> the 00:09:49.809 --> 00:09:49.819 align:start position:0% integration path on otherwise the 00:09:49.819 --> 00:09:51.489 align:start position:0% integration path on otherwise the revolution<00:09:50.389> will<00:09:50.569> not<00:09:50.600> happen<00:09:50.990> this<00:09:51.350> is 00:09:51.489 --> 00:09:51.499 align:start position:0% revolution will not happen this is 00:09:51.499 --> 00:09:54.280 align:start position:0% revolution will not happen this is crucial<00:09:52.369> to<00:09:52.699> gain<00:09:52.970> mass<00:09:53.300> adaptation 00:09:54.280 --> 00:09:54.290 align:start position:0% crucial to gain mass adaptation 00:09:54.290 --> 00:09:56.319 align:start position:0% crucial to gain mass adaptation application<00:09:55.160> developers<00:09:55.639> don't<00:09:55.879> care<00:09:56.209> about 00:09:56.319 --> 00:09:56.329 align:start position:0% application developers don't care about 00:09:56.329 --> 00:09:58.809 align:start position:0% application developers don't care about deeper<00:09:57.259> layers<00:09:57.529> of<00:09:57.709> the<00:09:58.069> stack<00:09:58.339> they<00:09:58.639> just 00:09:58.809 --> 00:09:58.819 align:start position:0% deeper layers of the stack they just 00:09:58.819 --> 00:10:00.850 align:start position:0% deeper layers of the stack they just want<00:09:59.059> something<00:09:59.329> that<00:09:59.540> works<00:09:59.990> that<00:10:00.679> they're 00:10:00.850 --> 00:10:00.860 align:start position:0% want something that works that they're 00:10:00.860 --> 00:10:02.919 align:start position:0% want something that works that they're familiar<00:10:01.040> with<00:10:01.429> and<00:10:01.879> something<00:10:02.600> that<00:10:02.689> works 00:10:02.919 --> 00:10:02.929 align:start position:0% familiar with and something that works 00:10:02.929 --> 00:10:05.049 align:start position:0% familiar with and something that works with<00:10:03.170> the<00:10:03.519> technologies<00:10:04.519> that<00:10:04.550> they<00:10:04.759> use 00:10:05.049 --> 00:10:05.059 align:start position:0% with the technologies that they use 00:10:05.059 --> 00:10:07.780 align:start position:0% with the technologies that they use today<00:10:05.269> so<00:10:05.749> as<00:10:05.990> an<00:10:06.139> example<00:10:06.259> or<00:10:06.829> DV<00:10:07.279> provides<00:10:07.670> a 00:10:07.780 --> 00:10:07.790 align:start position:0% today so as an example or DV provides a 00:10:07.790 --> 00:10:10.689 align:start position:0% today so as an example or DV provides a key<00:10:08.059> value<00:10:08.300> store<00:10:08.540> which<00:10:09.110> on<00:10:09.350> the<00:10:09.679> API<00:10:10.279> lever 00:10:10.689 --> 00:10:10.699 align:start position:0% key value store which on the API lever 00:10:10.699 --> 00:10:13.509 align:start position:0% key value store which on the API lever level<00:10:11.540> is<00:10:11.749> exactly<00:10:12.439> the<00:10:12.559> same<00:10:12.740> as<00:10:12.980> key<00:10:13.189> value 00:10:13.509 --> 00:10:13.519 align:start position:0% level is exactly the same as key value 00:10:13.519 --> 00:10:15.850 align:start position:0% level is exactly the same as key value stores<00:10:13.759> we<00:10:13.970> have<00:10:13.999> today<00:10:14.509> except<00:10:15.110> it's<00:10:15.379> fear<00:10:15.709> - 00:10:15.850 --> 00:10:15.860 align:start position:0% stores we have today except it's fear - 00:10:15.860 --> 00:10:16.799 align:start position:0% stores we have today except it's fear - fear 00:10:16.799 --> 00:10:16.809 align:start position:0% fear 00:10:16.809 --> 00:10:20.980 align:start position:0% fear so<00:10:18.160> like<00:10:19.160> say<00:10:19.369> we<00:10:19.639> come<00:10:20.149> really<00:10:20.689> far 00:10:20.980 --> 00:10:20.990 align:start position:0% so like say we come really far 00:10:20.990 --> 00:10:23.019 align:start position:0% so like say we come really far incredibly<00:10:21.649> far<00:10:21.889> just<00:10:22.100> in<00:10:22.249> a<00:10:22.309> few<00:10:22.519> years<00:10:22.790> and 00:10:23.019 --> 00:10:23.029 align:start position:0% incredibly far just in a few years and 00:10:23.029 --> 00:10:25.900 align:start position:0% incredibly far just in a few years and you<00:10:23.839> should<00:10:24.019> all<00:10:24.230> be<00:10:24.290> very<00:10:24.589> proud<00:10:25.279> of<00:10:25.339> what<00:10:25.519> you 00:10:25.900 --> 00:10:25.910 align:start position:0% you should all be very proud of what you 00:10:25.910 --> 00:10:28.960 align:start position:0% you should all be very proud of what you build<00:10:26.179> so<00:10:26.480> far<00:10:26.769> but<00:10:27.769> there's<00:10:28.339> still<00:10:28.549> a<00:10:28.579> lot<00:10:28.850> of 00:10:28.960 --> 00:10:28.970 align:start position:0% build so far but there's still a lot of 00:10:28.970 --> 00:10:32.139 align:start position:0% build so far but there's still a lot of work<00:10:29.149> ahead<00:10:29.329> and<00:10:29.769> I<00:10:30.769> want<00:10:31.459> to<00:10:31.549> leave<00:10:31.730> you<00:10:31.759> with 00:10:32.139 --> 00:10:32.149 align:start position:0% work ahead and I want to leave you with 00:10:32.149 --> 00:10:33.789 align:start position:0% work ahead and I want to leave you with something<00:10:32.509> to<00:10:32.839> think<00:10:32.990> about<00:10:33.139> how<00:10:33.529> can<00:10:33.589> we 00:10:33.789 --> 00:10:33.799 align:start position:0% something to think about how can we 00:10:33.799 --> 00:10:37.869 align:start position:0% something to think about how can we achieve<00:10:34.579> or<00:10:35.619> solve<00:10:36.619> some<00:10:37.160> of<00:10:37.189> the<00:10:37.429> remaining 00:10:37.869 --> 00:10:37.879 align:start position:0% achieve or solve some of the remaining 00:10:37.879 --> 00:10:40.980 align:start position:0% achieve or solve some of the remaining problems<00:10:38.779> that<00:10:38.959> we<00:10:39.079> still<00:10:39.319> have 00:10:40.980 --> 00:10:40.990 align:start position:0% problems that we still have 00:10:40.990 --> 00:10:45.419 align:start position:0% problems that we still have you<00:10:41.990> can<00:10:42.170> have<00:10:42.199> this<00:10:42.470> one 00:10:45.419 --> 00:10:45.429 align:start position:0% 00:10:45.429 --> 00:10:48.359 align:start position:0% thank<00:10:46.429> you 00:10:48.359 --> 00:10:48.369 align:start position:0% thank you 00:10:48.369 --> 00:10:52.090 align:start position:0% thank you so<00:10:49.369> the<00:10:50.240> way<00:10:50.389> you've<00:10:50.660> or<00:10:50.929> does<00:10:51.170> authentication 00:10:52.090 --> 00:10:52.100 align:start position:0% so the way you've or does authentication 00:10:52.100 --> 00:10:55.059 align:start position:0% so the way you've or does authentication is<00:10:52.249> fantastic<00:10:52.939> like<00:10:53.329> I<00:10:53.389> said<00:10:53.689> I<00:10:53.720> love<00:10:54.049> it<00:10:54.199> um<00:10:54.319> I 00:10:55.059 --> 00:10:55.069 align:start position:0% is fantastic like I said I love it um I 00:10:55.069 --> 00:10:57.879 align:start position:0% is fantastic like I said I love it um I wonder<00:10:55.670> how<00:10:55.850> we<00:10:56.329> could<00:10:56.509> use<00:10:56.540> the<00:10:56.869> same<00:10:57.079> or<00:10:57.410> a 00:10:57.879 --> 00:10:57.889 align:start position:0% wonder how we could use the same or a 00:10:57.889 --> 00:11:01.030 align:start position:0% wonder how we could use the same or a similar<00:10:57.920> mechanism<00:10:58.549> for<00:10:59.540> doing<00:11:00.040> permissions 00:11:01.030 --> 00:11:01.040 align:start position:0% similar mechanism for doing permissions 00:11:01.040 --> 00:11:04.109 align:start position:0% similar mechanism for doing permissions in<00:11:01.309> a<00:11:01.459> more<00:11:01.759> general<00:11:02.480> way<00:11:02.809> um 00:11:04.109 --> 00:11:04.119 align:start position:0% in a more general way um 00:11:04.119 --> 00:11:07.329 align:start position:0% in a more general way um the<00:11:05.119> mobile<00:11:05.569> use<00:11:05.809> case<00:11:06.049> is<00:11:06.470> a<00:11:06.529> very<00:11:06.889> different 00:11:07.329 --> 00:11:07.339 align:start position:0% the mobile use case is a very different 00:11:07.339 --> 00:11:10.569 align:start position:0% the mobile use case is a very different from<00:11:07.490> desktops<00:11:08.269> and<00:11:08.600> servers<00:11:08.660> so<00:11:09.499> how<00:11:10.040> can<00:11:10.100> we 00:11:10.569 --> 00:11:10.579 align:start position:0% from desktops and servers so how can we 00:11:10.579 --> 00:11:12.759 align:start position:0% from desktops and servers so how can we make<00:11:10.790> all<00:11:11.029> this<00:11:11.240> happen<00:11:11.299> smoothly<00:11:12.170> on<00:11:12.589> the 00:11:12.759 --> 00:11:12.769 align:start position:0% make all this happen smoothly on the 00:11:12.769 --> 00:11:14.400 align:start position:0% make all this happen smoothly on the mobile<00:11:12.980> web<00:11:13.189> and 00:11:14.400 --> 00:11:14.410 align:start position:0% mobile web and 00:11:14.410 --> 00:11:16.780 align:start position:0% mobile web and you<00:11:15.410> may<00:11:15.559> think<00:11:15.920> this<00:11:16.129> is<00:11:16.309> pretty<00:11:16.519> out<00:11:16.759> there 00:11:16.780 --> 00:11:16.790 align:start position:0% you may think this is pretty out there 00:11:16.790 --> 00:11:18.489 align:start position:0% you may think this is pretty out there but<00:11:17.329> think<00:11:17.600> about<00:11:17.779> the<00:11:17.899> future<00:11:18.079> of<00:11:18.350> the 00:11:18.489 --> 00:11:18.499 align:start position:0% but think about the future of the 00:11:18.499 --> 00:11:21.309 align:start position:0% but think about the future of the humankind<00:11:18.829> will<00:11:19.339> soon<00:11:19.639> reach<00:11:20.029> Mars<00:11:20.480> and<00:11:20.839> maybe 00:11:21.309 --> 00:11:21.319 align:start position:0% humankind will soon reach Mars and maybe 00:11:21.319 --> 00:11:24.670 align:start position:0% humankind will soon reach Mars and maybe beyond<00:11:22.040> in<00:11:22.130> our<00:11:22.399> lifetime<00:11:23.000> so<00:11:23.630> how<00:11:24.110> do<00:11:24.170> we<00:11:24.350> make 00:11:24.670 --> 00:11:24.680 align:start position:0% beyond in our lifetime so how do we make 00:11:24.680 --> 00:11:28.060 align:start position:0% beyond in our lifetime so how do we make truly<00:11:25.600> interplanetary<00:11:26.600> applications<00:11:27.560> that 00:11:28.060 --> 00:11:28.070 align:start position:0% truly interplanetary applications that 00:11:28.070 --> 00:11:30.639 align:start position:0% truly interplanetary applications that can<00:11:28.279> work<00:11:28.459> across<00:11:28.670> vast<00:11:29.300> distances<00:11:29.649> times 00:11:30.639 --> 00:11:30.649 align:start position:0% can work across vast distances times 00:11:30.649 --> 00:11:33.509 align:start position:0% can work across vast distances times fans<00:11:30.980> and<00:11:31.310> disconnected<00:11:32.269> networks<00:11:32.690> um 00:11:33.509 --> 00:11:33.519 align:start position:0% fans and disconnected networks um 00:11:33.519 --> 00:11:36.460 align:start position:0% fans and disconnected networks um my<00:11:34.519> personal<00:11:35.029> goal<00:11:35.240> is<00:11:35.570> to<00:11:35.750> put<00:11:35.930> orbit<00:11:36.350> on 00:11:36.460 --> 00:11:36.470 align:start position:0% my personal goal is to put orbit on 00:11:36.470 --> 00:11:38.249 align:start position:0% my personal goal is to put orbit on orbit 00:11:38.249 --> 00:11:38.259 align:start position:0% orbit 00:11:38.259 --> 00:11:40.740 align:start position:0% orbit thank<00:11:39.259> you 00:11:40.740 --> 00:11:40.750 align:start position:0% thank you 00:11:40.750 --> 00:11:43.160 align:start position:0% thank you [Applause] 00:11:43.160 --> 00:11:43.170 align:start position:0% [Applause] 00:11:43.170 --> 00:11:51.580 align:start position:0% [Applause] [Music]