WEBVTT Kind: captions Language: en 00:00:00.000 --> 00:00:04.350 align:start position:0% foreign 00:00:04.350 --> 00:00:04.360 align:start position:0% 00:00:04.360 --> 00:00:17.870 align:start position:0% [Music] 00:00:17.870 --> 00:00:17.880 align:start position:0% 00:00:17.880 --> 00:00:19.070 align:start position:0% and<00:00:18.300> today<00:00:18.420> I'm<00:00:18.600> going<00:00:18.720> to<00:00:18.779> speak<00:00:18.900> about 00:00:19.070 --> 00:00:19.080 align:start position:0% and today I'm going to speak about 00:00:19.080 --> 00:00:21.410 align:start position:0% and today I'm going to speak about streamies 00:00:21.410 --> 00:00:21.420 align:start position:0% streamies 00:00:21.420 --> 00:00:24.230 align:start position:0% streamies um<00:00:21.539> a<00:00:21.900> project<00:00:22.160> I've<00:00:23.160> been<00:00:23.340> working<00:00:23.460> on<00:00:23.699> with 00:00:24.230 --> 00:00:24.240 align:start position:0% um a project I've been working on with 00:00:24.240 --> 00:00:25.790 align:start position:0% um a project I've been working on with the<00:00:24.359> ethereum<00:00:24.840> foundation 00:00:25.790 --> 00:00:25.800 align:start position:0% the ethereum foundation 00:00:25.800 --> 00:00:29.689 align:start position:0% the ethereum foundation and<00:00:26.100> the<00:00:26.279> guys<00:00:26.400> from<00:00:26.640> life<00:00:27.119> here 00:00:29.689 --> 00:00:29.699 align:start position:0% 00:00:29.699 --> 00:00:31.669 align:start position:0% um<00:00:29.820> it's<00:00:30.539> a<00:00:30.660> project<00:00:30.779> that<00:00:31.019> we're<00:00:31.140> using<00:00:31.380> right 00:00:31.669 --> 00:00:31.679 align:start position:0% um it's a project that we're using right 00:00:31.679 --> 00:00:34.370 align:start position:0% um it's a project that we're using right now<00:00:31.859> to<00:00:32.220> stream<00:00:32.520> Defcon<00:00:33.360> so<00:00:33.840> if<00:00:33.960> you<00:00:34.079> go<00:00:34.260> to 00:00:34.370 --> 00:00:34.380 align:start position:0% now to stream Defcon so if you go to 00:00:34.380 --> 00:00:36.350 align:start position:0% now to stream Defcon so if you go to live.defcon.org 00:00:36.350 --> 00:00:36.360 align:start position:0% live.defcon.org 00:00:36.360 --> 00:00:38.750 align:start position:0% live.defcon.org you<00:00:36.780> can<00:00:36.899> actually<00:00:37.079> follow<00:00:37.440> all<00:00:38.399> the<00:00:38.520> sessions 00:00:38.750 --> 00:00:38.760 align:start position:0% you can actually follow all the sessions 00:00:38.760 --> 00:00:40.850 align:start position:0% you can actually follow all the sessions there 00:00:40.850 --> 00:00:40.860 align:start position:0% there 00:00:40.860 --> 00:00:42.709 align:start position:0% there um<00:00:40.980> so<00:00:41.399> yeah<00:00:41.520> I'll<00:00:41.640> be<00:00:41.820> speaking<00:00:42.059> about 00:00:42.709 --> 00:00:42.719 align:start position:0% um so yeah I'll be speaking about 00:00:42.719 --> 00:00:46.670 align:start position:0% um so yeah I'll be speaking about what<00:00:43.140> treatment<00:00:43.440> is<00:00:43.860> how<00:00:44.340> it<00:00:44.520> works<00:00:45.300> and<00:00:46.260> why 00:00:46.670 --> 00:00:46.680 align:start position:0% what treatment is how it works and why 00:00:46.680 --> 00:00:48.410 align:start position:0% what treatment is how it works and why we<00:00:46.860> need<00:00:46.980> stream<00:00:47.160> it<00:00:47.460> actually<00:00:47.640> which<00:00:48.120> I<00:00:48.300> think 00:00:48.410 --> 00:00:48.420 align:start position:0% we need stream it actually which I think 00:00:48.420 --> 00:00:50.510 align:start position:0% we need stream it actually which I think is<00:00:48.539> the<00:00:48.660> most<00:00:48.840> important<00:00:49.680> thing 00:00:50.510 --> 00:00:50.520 align:start position:0% is the most important thing 00:00:50.520 --> 00:00:53.150 align:start position:0% is the most important thing and<00:00:51.000> then<00:00:51.180> I'll<00:00:51.780> go<00:00:51.960> over<00:00:52.079> a<00:00:52.260> bit<00:00:52.440> of<00:00:52.680> history 00:00:53.150 --> 00:00:53.160 align:start position:0% and then I'll go over a bit of history 00:00:53.160 --> 00:00:57.290 align:start position:0% and then I'll go over a bit of history on<00:00:53.640> how<00:00:54.420> the<00:00:54.539> application<00:00:54.899> came<00:00:55.199> to<00:00:55.379> to<00:00:55.620> be 00:00:57.290 --> 00:00:57.300 align:start position:0% on how the application came to to be 00:00:57.300 --> 00:00:58.069 align:start position:0% on how the application came to to be um 00:00:58.069 --> 00:00:58.079 align:start position:0% um 00:00:58.079 --> 00:01:00.889 align:start position:0% um where<00:00:58.440> we<00:00:58.559> used<00:00:58.739> it<00:00:58.980> and<00:00:59.879> also<00:01:00.180> how<00:01:00.660> the<00:01:00.780> future 00:01:00.889 --> 00:01:00.899 align:start position:0% where we used it and also how the future 00:01:00.899 --> 00:01:03.709 align:start position:0% where we used it and also how the future is<00:01:01.079> going<00:01:01.260> to<00:01:01.320> look<00:01:01.440> like<00:01:01.559> for<00:01:01.800> streamies<00:01:02.940> so 00:01:03.709 --> 00:01:03.719 align:start position:0% is going to look like for streamies so 00:01:03.719 --> 00:01:05.990 align:start position:0% is going to look like for streamies so what<00:01:04.320> is<00:01:04.559> three<00:01:04.799> myth 00:01:05.990 --> 00:01:06.000 align:start position:0% what is three myth 00:01:06.000 --> 00:01:08.570 align:start position:0% what is three myth there<00:01:06.420> is<00:01:06.540> a<00:01:06.659> very<00:01:06.780> official<00:01:07.320> definition<00:01:08.159> that 00:01:08.570 --> 00:01:08.580 align:start position:0% there is a very official definition that 00:01:08.580 --> 00:01:10.789 align:start position:0% there is a very official definition that I<00:01:08.760> made<00:01:08.939> up<00:01:09.540> yesterday 00:01:10.789 --> 00:01:10.799 align:start position:0% I made up yesterday 00:01:10.799 --> 00:01:12.950 align:start position:0% I made up yesterday so 00:01:12.950 --> 00:01:12.960 align:start position:0% so 00:01:12.960 --> 00:01:14.810 align:start position:0% so um<00:01:13.080> streaming<00:01:13.920> is<00:01:14.220> a<00:01:14.340> self-hosted 00:01:14.810 --> 00:01:14.820 align:start position:0% um streaming is a self-hosted 00:01:14.820 --> 00:01:17.030 align:start position:0% um streaming is a self-hosted application<00:01:15.240> that<00:01:16.080> event<00:01:16.260> organizers<00:01:16.860> can 00:01:17.030 --> 00:01:17.040 align:start position:0% application that event organizers can 00:01:17.040 --> 00:01:19.670 align:start position:0% application that event organizers can use<00:01:17.220> to<00:01:17.460> host<00:01:17.640> their<00:01:18.000> virtual<00:01:18.360> events<00:01:18.840> like<00:01:19.560> I 00:01:19.670 --> 00:01:19.680 align:start position:0% use to host their virtual events like I 00:01:19.680 --> 00:01:22.130 align:start position:0% use to host their virtual events like I said<00:01:19.799> streaming<00:01:20.280> was<00:01:20.520> born<00:01:20.700> out<00:01:21.180> of<00:01:21.420> a 00:01:22.130 --> 00:01:22.140 align:start position:0% said streaming was born out of a 00:01:22.140 --> 00:01:23.510 align:start position:0% said streaming was born out of a collaboration<00:01:22.619> between<00:01:22.799> ethereum 00:01:23.510 --> 00:01:23.520 align:start position:0% collaboration between ethereum 00:01:23.520 --> 00:01:25.270 align:start position:0% collaboration between ethereum Foundation<00:01:23.820> life<00:01:24.060> here<00:01:24.240> and<00:01:24.479> myself 00:01:25.270 --> 00:01:25.280 align:start position:0% Foundation life here and myself 00:01:25.280 --> 00:01:28.190 align:start position:0% Foundation life here and myself and<00:01:26.299> it<00:01:27.299> all<00:01:27.420> started<00:01:27.659> with<00:01:27.780> ethereum 00:01:28.190 --> 00:01:28.200 align:start position:0% and it all started with ethereum 00:01:28.200 --> 00:01:30.649 align:start position:0% and it all started with ethereum Foundation<00:01:28.500> wanting<00:01:28.979> to<00:01:29.299> decouple<00:01:30.299> this<00:01:30.479> term 00:01:30.649 --> 00:01:30.659 align:start position:0% Foundation wanting to decouple this term 00:01:30.659 --> 00:01:31.670 align:start position:0% Foundation wanting to decouple this term from<00:01:30.840> YouTube 00:01:31.670 --> 00:01:31.680 align:start position:0% from YouTube 00:01:31.680 --> 00:01:34.730 align:start position:0% from YouTube and<00:01:32.460> they<00:01:32.939> wanted<00:01:33.119> to<00:01:33.299> do<00:01:33.479> three<00:01:34.380> simple 00:01:34.730 --> 00:01:34.740 align:start position:0% and they wanted to do three simple 00:01:34.740 --> 00:01:35.569 align:start position:0% and they wanted to do three simple things 00:01:35.569 --> 00:01:35.579 align:start position:0% things 00:01:35.579 --> 00:01:36.830 align:start position:0% things at<00:01:36.119> first 00:01:36.830 --> 00:01:36.840 align:start position:0% at first 00:01:36.840 --> 00:01:39.770 align:start position:0% at first so<00:01:37.500> our<00:01:37.680> current<00:01:37.920> version<00:01:38.159> of<00:01:38.340> Streamys<00:01:38.820> those 00:01:39.770 --> 00:01:39.780 align:start position:0% so our current version of Streamys those 00:01:39.780 --> 00:01:42.050 align:start position:0% so our current version of Streamys those these<00:01:40.500> three<00:01:40.680> simple<00:01:40.979> things 00:01:42.050 --> 00:01:42.060 align:start position:0% these three simple things 00:01:42.060 --> 00:01:46.969 align:start position:0% these three simple things fairly<00:01:43.020> good<00:01:43.740> I<00:01:43.979> think<00:01:44.600> so<00:01:45.600> stream<00:01:45.960> we<00:01:46.860> wanted 00:01:46.969 --> 00:01:46.979 align:start position:0% fairly good I think so stream we wanted 00:01:46.979 --> 00:01:48.530 align:start position:0% fairly good I think so stream we wanted to<00:01:47.220> live<00:01:47.460> stream<00:01:47.640> the<00:01:47.880> events<00:01:48.240> of<00:01:48.360> course 00:01:48.530 --> 00:01:48.540 align:start position:0% to live stream the events of course 00:01:48.540 --> 00:01:50.810 align:start position:0% to live stream the events of course without<00:01:49.079> relying<00:01:49.619> on<00:01:49.680> YouTube 00:01:50.810 --> 00:01:50.820 align:start position:0% without relying on YouTube 00:01:50.820 --> 00:01:54.350 align:start position:0% without relying on YouTube and<00:01:51.540> we<00:01:51.899> wanted<00:01:52.020> to<00:01:52.320> also<00:01:52.799> show<00:01:53.399> a<00:01:53.579> schedule<00:01:53.820> of 00:01:54.350 --> 00:01:54.360 align:start position:0% and we wanted to also show a schedule of 00:01:54.360 --> 00:01:57.289 align:start position:0% and we wanted to also show a schedule of these<00:01:54.600> sessions<00:01:54.899> and<00:01:55.860> for<00:01:56.040> each<00:01:56.220> talk<00:01:56.460> and 00:01:57.289 --> 00:01:57.299 align:start position:0% these sessions and for each talk and 00:01:57.299 --> 00:01:59.630 align:start position:0% these sessions and for each talk and after<00:01:57.600> the<00:01:57.780> event<00:01:57.899> was<00:01:58.200> done<00:01:58.380> we<00:01:59.159> wanted<00:01:59.340> to 00:01:59.630 --> 00:01:59.640 align:start position:0% after the event was done we wanted to 00:01:59.640 --> 00:02:00.889 align:start position:0% after the event was done we wanted to record 00:02:00.889 --> 00:02:00.899 align:start position:0% record 00:02:00.899 --> 00:02:03.710 align:start position:0% record and<00:02:01.799> show<00:02:02.460> the<00:02:02.579> recording<00:02:03.000> of<00:02:03.299> all<00:02:03.659> the 00:02:03.710 --> 00:02:03.720 align:start position:0% and show the recording of all the 00:02:03.720 --> 00:02:05.929 align:start position:0% and show the recording of all the sessions<00:02:03.960> that<00:02:04.140> we've<00:02:04.320> streamed<00:02:04.560> right 00:02:05.929 --> 00:02:05.939 align:start position:0% sessions that we've streamed right 00:02:05.939 --> 00:02:07.550 align:start position:0% sessions that we've streamed right so<00:02:06.360> when<00:02:06.540> we<00:02:06.659> started<00:02:06.899> designing<00:02:07.259> the<00:02:07.380> the 00:02:07.550 --> 00:02:07.560 align:start position:0% so when we started designing the the 00:02:07.560 --> 00:02:09.889 align:start position:0% so when we started designing the the application<00:02:07.979> we<00:02:08.280> decided<00:02:08.700> that<00:02:08.880> we<00:02:09.539> wanted<00:02:09.660> to 00:02:09.889 --> 00:02:09.899 align:start position:0% application we decided that we wanted to 00:02:09.899 --> 00:02:11.869 align:start position:0% application we decided that we wanted to mimic 00:02:11.869 --> 00:02:11.879 align:start position:0% mimic 00:02:11.879 --> 00:02:12.650 align:start position:0% mimic um 00:02:12.650 --> 00:02:12.660 align:start position:0% um 00:02:12.660 --> 00:02:14.930 align:start position:0% um kind<00:02:13.319> of<00:02:13.500> how<00:02:14.099> the<00:02:14.220> application<00:02:14.580> looked<00:02:14.879> like 00:02:14.930 --> 00:02:14.940 align:start position:0% kind of how the application looked like 00:02:14.940 --> 00:02:17.150 align:start position:0% kind of how the application looked like we<00:02:15.060> wanted<00:02:15.180> to<00:02:15.360> mimic<00:02:15.900> it<00:02:16.080> to<00:02:16.379> what<00:02:16.920> a<00:02:17.040> real 00:02:17.150 --> 00:02:17.160 align:start position:0% we wanted to mimic it to what a real 00:02:17.160 --> 00:02:19.490 align:start position:0% we wanted to mimic it to what a real event<00:02:17.400> is<00:02:17.700> so<00:02:18.660> we<00:02:18.840> designed<00:02:19.319> everything 00:02:19.490 --> 00:02:19.500 align:start position:0% event is so we designed everything 00:02:19.500 --> 00:02:22.430 align:start position:0% event is so we designed everything around<00:02:19.739> rooms<00:02:20.280> and<00:02:21.060> sessions<00:02:21.420> right<00:02:21.780> so<00:02:22.200> one 00:02:22.430 --> 00:02:22.440 align:start position:0% around rooms and sessions right so one 00:02:22.440 --> 00:02:25.369 align:start position:0% around rooms and sessions right so one event<00:02:22.680> has<00:02:22.980> multiple<00:02:23.819> rooms<00:02:24.180> and<00:02:24.959> one<00:02:25.140> room 00:02:25.369 --> 00:02:25.379 align:start position:0% event has multiple rooms and one room 00:02:25.379 --> 00:02:28.190 align:start position:0% event has multiple rooms and one room has<00:02:25.680> multiple<00:02:26.340> sessions 00:02:28.190 --> 00:02:28.200 align:start position:0% has multiple sessions 00:02:28.200 --> 00:02:31.130 align:start position:0% has multiple sessions and<00:02:28.980> so<00:02:29.760> then<00:02:29.879> from<00:02:30.060> then<00:02:30.239> on<00:02:30.420> we<00:02:30.840> started 00:02:31.130 --> 00:02:31.140 align:start position:0% and so then from then on we started 00:02:31.140 --> 00:02:32.990 align:start position:0% and so then from then on we started building<00:02:31.319> streamies 00:02:32.990 --> 00:02:33.000 align:start position:0% building streamies 00:02:33.000 --> 00:02:35.030 align:start position:0% building streamies the<00:02:33.360> first<00:02:33.480> thing<00:02:33.599> we<00:02:33.720> focused<00:02:33.959> on<00:02:34.080> was<00:02:34.319> was<00:02:34.680> on 00:02:35.030 --> 00:02:35.040 align:start position:0% the first thing we focused on was was on 00:02:35.040 --> 00:02:36.530 align:start position:0% the first thing we focused on was was on live<00:02:35.400> streaming 00:02:36.530 --> 00:02:36.540 align:start position:0% live streaming 00:02:36.540 --> 00:02:41.150 align:start position:0% live streaming so<00:02:36.959> each<00:02:37.200> room<00:02:37.440> can<00:02:38.160> have<00:02:38.400> one<00:02:38.819> live<00:02:39.060> stream 00:02:41.150 --> 00:02:41.160 align:start position:0% so each room can have one live stream 00:02:41.160 --> 00:02:42.949 align:start position:0% so each room can have one live stream um<00:02:41.220> through<00:02:42.000> through<00:02:42.300> the<00:02:42.480> whole<00:02:42.599> application 00:02:42.949 --> 00:02:42.959 align:start position:0% um through through the whole application 00:02:42.959 --> 00:02:45.350 align:start position:0% um through through the whole application you<00:02:43.319> can<00:02:43.459> concurrently<00:02:44.459> stream<00:02:44.700> on<00:02:45.000> multiple 00:02:45.350 --> 00:02:45.360 align:start position:0% you can concurrently stream on multiple 00:02:45.360 --> 00:02:49.250 align:start position:0% you can concurrently stream on multiple rooms<00:02:45.660> so<00:02:45.959> today<00:02:46.620> at<00:02:47.040> inline<00:02:47.459> in<00:02:47.879> Defcon<00:02:48.420> we're 00:02:49.250 --> 00:02:49.260 align:start position:0% rooms so today at inline in Defcon we're 00:02:49.260 --> 00:02:50.990 align:start position:0% rooms so today at inline in Defcon we're concurrently<00:02:49.739> live<00:02:49.920> streaming<00:02:50.220> nine 00:02:50.990 --> 00:02:51.000 align:start position:0% concurrently live streaming nine 00:02:51.000 --> 00:02:53.630 align:start position:0% concurrently live streaming nine multiple<00:02:51.720> rooms<00:02:52.560> which<00:02:53.160> I<00:02:53.280> think<00:02:53.400> is<00:02:53.519> pretty 00:02:53.630 --> 00:02:53.640 align:start position:0% multiple rooms which I think is pretty 00:02:53.640 --> 00:02:57.410 align:start position:0% multiple rooms which I think is pretty cool<00:02:54.239> we<00:02:54.900> also<00:02:55.260> focus<00:02:55.680> on<00:02:56.040> uptime 00:02:57.410 --> 00:02:57.420 align:start position:0% cool we also focus on uptime 00:02:57.420 --> 00:03:00.350 align:start position:0% cool we also focus on uptime and<00:02:58.200> we're<00:02:58.980> building<00:02:59.160> a<00:02:59.459> failover<00:02:59.819> mechanism 00:03:00.350 --> 00:03:00.360 align:start position:0% and we're building a failover mechanism 00:03:00.360 --> 00:03:04.070 align:start position:0% and we're building a failover mechanism into<00:03:00.599> our<00:03:00.959> playback<00:03:01.920> systems<00:03:02.459> that<00:03:03.000> allows<00:03:03.420> a 00:03:04.070 --> 00:03:04.080 align:start position:0% into our playback systems that allows a 00:03:04.080 --> 00:03:06.130 align:start position:0% into our playback systems that allows a single<00:03:04.319> room<00:03:04.500> to<00:03:04.860> ingest 00:03:06.130 --> 00:03:06.140 align:start position:0% single room to ingest 00:03:06.140 --> 00:03:09.170 align:start position:0% single room to ingest two<00:03:07.140> sources<00:03:07.500> that<00:03:07.739> have<00:03:07.980> the<00:03:08.160> same<00:03:08.280> content 00:03:09.170 --> 00:03:09.180 align:start position:0% two sources that have the same content 00:03:09.180 --> 00:03:10.670 align:start position:0% two sources that have the same content to<00:03:09.599> fail<00:03:09.780> over 00:03:10.670 --> 00:03:10.680 align:start position:0% to fail over 00:03:10.680 --> 00:03:13.009 align:start position:0% to fail over to<00:03:10.860> one<00:03:11.159> or<00:03:11.340> the<00:03:11.459> other<00:03:11.580> in<00:03:11.940> case<00:03:12.120> there<00:03:12.840> were 00:03:13.009 --> 00:03:13.019 align:start position:0% to one or the other in case there were 00:03:13.019 --> 00:03:15.410 align:start position:0% to one or the other in case there were errors<00:03:13.319> in<00:03:13.620> the<00:03:13.819> broadcasting<00:03:14.819> on<00:03:15.000> one<00:03:15.239> of<00:03:15.360> the 00:03:15.410 --> 00:03:15.420 align:start position:0% errors in the broadcasting on one of the 00:03:15.420 --> 00:03:17.330 align:start position:0% errors in the broadcasting on one of the sources 00:03:17.330 --> 00:03:17.340 align:start position:0% sources 00:03:17.340 --> 00:03:19.190 align:start position:0% sources um<00:03:17.400> you<00:03:17.580> might<00:03:17.760> be<00:03:17.879> wondering<00:03:18.180> what<00:03:18.900> we<00:03:19.080> use 00:03:19.190 --> 00:03:19.200 align:start position:0% um you might be wondering what we use 00:03:19.200 --> 00:03:21.050 align:start position:0% um you might be wondering what we use instead<00:03:19.560> of<00:03:19.620> YouTube<00:03:19.800> and<00:03:20.519> that<00:03:20.640> is<00:03:20.819> of<00:03:21.000> course 00:03:21.050 --> 00:03:21.060 align:start position:0% instead of YouTube and that is of course 00:03:21.060 --> 00:03:23.690 align:start position:0% instead of YouTube and that is of course very<00:03:21.360> interesting<00:03:22.200> and<00:03:22.920> that's<00:03:23.280> where<00:03:23.459> life 00:03:23.690 --> 00:03:23.700 align:start position:0% very interesting and that's where life 00:03:23.700 --> 00:03:27.530 align:start position:0% very interesting and that's where life here<00:03:23.940> life<00:03:24.599> here<00:03:24.780> comes<00:03:25.019> in<00:03:26.120> stream<00:03:27.120> it<00:03:27.360> is 00:03:27.530 --> 00:03:27.540 align:start position:0% here life here comes in stream it is 00:03:27.540 --> 00:03:29.509 align:start position:0% here life here comes in stream it is actually<00:03:27.720> provider<00:03:28.379> agnostic 00:03:29.509 --> 00:03:29.519 align:start position:0% actually provider agnostic 00:03:29.519 --> 00:03:31.009 align:start position:0% actually provider agnostic which<00:03:29.940> means<00:03:30.239> that 00:03:31.009 --> 00:03:31.019 align:start position:0% which means that 00:03:31.019 --> 00:03:34.130 align:start position:0% which means that we<00:03:31.620> don't<00:03:31.800> do<00:03:32.640> any<00:03:32.940> of<00:03:33.239> the<00:03:33.540> broadcasting 00:03:34.130 --> 00:03:34.140 align:start position:0% we don't do any of the broadcasting 00:03:34.140 --> 00:03:36.229 align:start position:0% we don't do any of the broadcasting ourselves<00:03:34.500> right<00:03:34.739> we<00:03:35.040> just<00:03:35.280> we<00:03:35.700> are<00:03:35.819> just<00:03:36.060> a 00:03:36.229 --> 00:03:36.239 align:start position:0% ourselves right we just we are just a 00:03:36.239 --> 00:03:38.750 align:start position:0% ourselves right we just we are just a front-end<00:03:36.659> that<00:03:37.260> hooks<00:03:37.680> into 00:03:38.750 --> 00:03:38.760 align:start position:0% front-end that hooks into 00:03:38.760 --> 00:03:41.570 align:start position:0% front-end that hooks into Whatever<00:03:39.180> video<00:03:39.480> provider<00:03:40.019> we<00:03:40.680> want<00:03:40.860> in<00:03:41.459> our 00:03:41.570 --> 00:03:41.580 align:start position:0% Whatever video provider we want in our 00:03:41.580 --> 00:03:42.470 align:start position:0% Whatever video provider we want in our case 00:03:42.470 --> 00:03:42.480 align:start position:0% case 00:03:42.480 --> 00:03:46.369 align:start position:0% case we<00:03:43.379> build<00:03:44.099> a<00:03:44.340> solution<00:03:44.640> by<00:03:45.480> default<00:03:45.840> on<00:03:46.080> top<00:03:46.260> of 00:03:46.369 --> 00:03:46.379 align:start position:0% we build a solution by default on top of 00:03:46.379 --> 00:03:47.390 align:start position:0% we build a solution by default on top of life<00:03:46.560> here 00:03:47.390 --> 00:03:47.400 align:start position:0% life here 00:03:47.400 --> 00:03:49.490 align:start position:0% life here which<00:03:47.760> is<00:03:47.879> an<00:03:48.000> awesome<00:03:48.180> protocol<00:03:48.540> that 00:03:49.490 --> 00:03:49.500 align:start position:0% which is an awesome protocol that 00:03:49.500 --> 00:03:51.289 align:start position:0% which is an awesome protocol that some<00:03:49.860> of<00:03:50.040> you<00:03:50.099> may<00:03:50.220> know<00:03:50.400> I<00:03:50.760> know<00:03:51.000> these<00:03:51.239> guys 00:03:51.289 --> 00:03:51.299 align:start position:0% some of you may know I know these guys 00:03:51.299 --> 00:03:52.610 align:start position:0% some of you may know I know these guys know<00:03:51.540> them<00:03:51.720> because<00:03:51.900> they're<00:03:52.319> the<00:03:52.500> core 00:03:52.610 --> 00:03:52.620 align:start position:0% know them because they're the core 00:03:52.620 --> 00:03:54.949 align:start position:0% know them because they're the core developers<00:03:53.099> so<00:03:53.340> yeah 00:03:54.949 --> 00:03:54.959 align:start position:0% developers so yeah 00:03:54.959 --> 00:03:55.490 align:start position:0% developers so yeah um 00:03:55.490 --> 00:03:55.500 align:start position:0% um 00:03:55.500 --> 00:03:57.229 align:start position:0% um life<00:03:56.099> areas<00:03:56.459> are<00:03:56.580> the<00:03:56.700> centralized<00:03:57.060> video 00:03:57.229 --> 00:03:57.239 align:start position:0% life areas are the centralized video 00:03:57.239 --> 00:03:59.149 align:start position:0% life areas are the centralized video streaming<00:03:57.720> Network<00:03:57.900> built<00:03:58.799> on<00:03:58.860> ethereum 00:03:59.149 --> 00:03:59.159 align:start position:0% streaming Network built on ethereum 00:03:59.159 --> 00:04:00.050 align:start position:0% streaming Network built on ethereum blockchain 00:04:00.050 --> 00:04:00.060 align:start position:0% blockchain 00:04:00.060 --> 00:04:03.170 align:start position:0% blockchain a<00:04:00.480> library<00:04:00.780> can<00:04:01.260> currently<00:04:01.799> distribute<00:04:02.340> live 00:04:03.170 --> 00:04:03.180 align:start position:0% a library can currently distribute live 00:04:03.180 --> 00:04:05.500 align:start position:0% a library can currently distribute live and<00:04:03.480> on-demand<00:04:03.959> content 00:04:05.500 --> 00:04:05.510 align:start position:0% and on-demand content 00:04:05.510 --> 00:04:05.809 align:start position:0% and on-demand content [Music] 00:04:05.809 --> 00:04:05.819 align:start position:0% [Music] 00:04:05.819 --> 00:04:06.949 align:start position:0% [Music] um 00:04:06.949 --> 00:04:06.959 align:start position:0% um 00:04:06.959 --> 00:04:09.470 align:start position:0% um so<00:04:07.260> yeah<00:04:07.379> it's<00:04:07.500> pretty<00:04:07.680> cool<00:04:07.920> I'll<00:04:08.700> go<00:04:08.879> more<00:04:09.299> in 00:04:09.470 --> 00:04:09.480 align:start position:0% so yeah it's pretty cool I'll go more in 00:04:09.480 --> 00:04:12.350 align:start position:0% so yeah it's pretty cool I'll go more in depth<00:04:09.780> on<00:04:09.959> why<00:04:10.200> we<00:04:10.379> chose<00:04:10.560> live<00:04:11.280> here<00:04:11.519> later 00:04:12.350 --> 00:04:12.360 align:start position:0% depth on why we chose live here later 00:04:12.360 --> 00:04:14.270 align:start position:0% depth on why we chose live here later but<00:04:12.659> you<00:04:12.780> can<00:04:12.900> imagine<00:04:13.080> it's<00:04:13.860> a<00:04:14.040> protocol 00:04:14.270 --> 00:04:14.280 align:start position:0% but you can imagine it's a protocol 00:04:14.280 --> 00:04:16.689 align:start position:0% but you can imagine it's a protocol built<00:04:14.700> on<00:04:14.760> ethereum<00:04:15.239> so<00:04:16.019> decentralization 00:04:16.689 --> 00:04:16.699 align:start position:0% built on ethereum so decentralization 00:04:16.699 --> 00:04:18.710 align:start position:0% built on ethereum so decentralization censorship<00:04:17.699> assistant 00:04:18.710 --> 00:04:18.720 align:start position:0% censorship assistant 00:04:18.720 --> 00:04:21.170 align:start position:0% censorship assistant and<00:04:19.500> all<00:04:19.979> the<00:04:20.100> nice<00:04:20.220> things<00:04:20.400> about 00:04:21.170 --> 00:04:21.180 align:start position:0% and all the nice things about 00:04:21.180 --> 00:04:24.950 align:start position:0% and all the nice things about decentralization<00:04:22.079> right<00:04:22.940> and<00:04:23.940> so<00:04:24.660> like<00:04:24.780> I 00:04:24.950 --> 00:04:24.960 align:start position:0% decentralization right and so like I 00:04:24.960 --> 00:04:26.510 align:start position:0% decentralization right and so like I said<00:04:25.080> the<00:04:25.680> application<00:04:26.040> is<00:04:26.220> provided 00:04:26.510 --> 00:04:26.520 align:start position:0% said the application is provided 00:04:26.520 --> 00:04:29.270 align:start position:0% said the application is provided agnostic<00:04:27.000> but<00:04:27.360> there's<00:04:27.600> already<00:04:27.900> a<00:04:28.680> out<00:04:29.100> of 00:04:29.270 --> 00:04:29.280 align:start position:0% agnostic but there's already a out of 00:04:29.280 --> 00:04:31.370 align:start position:0% agnostic but there's already a out of the<00:04:29.340> box<00:04:29.460> solution<00:04:29.880> that<00:04:30.720> integrates<00:04:31.139> with 00:04:31.370 --> 00:04:31.380 align:start position:0% the box solution that integrates with 00:04:31.380 --> 00:04:33.110 align:start position:0% the box solution that integrates with life<00:04:31.680> here<00:04:31.919> so<00:04:32.220> you<00:04:32.400> can 00:04:33.110 --> 00:04:33.120 align:start position:0% life here so you can 00:04:33.120 --> 00:04:36.170 align:start position:0% life here so you can start<00:04:33.840> up<00:04:33.960> Streamys<00:04:34.440> a 00:04:36.170 --> 00:04:36.180 align:start position:0% start up Streamys a 00:04:36.180 --> 00:04:38.270 align:start position:0% start up Streamys a set<00:04:36.600> up<00:04:36.720> your<00:04:36.840> lifer<00:04:37.199> account<00:04:37.440> and<00:04:38.100> start 00:04:38.270 --> 00:04:38.280 align:start position:0% set up your lifer account and start 00:04:38.280 --> 00:04:40.610 align:start position:0% set up your lifer account and start streaming 00:04:40.610 --> 00:04:40.620 align:start position:0% streaming 00:04:40.620 --> 00:04:42.650 align:start position:0% streaming decentralized<00:04:41.520> then<00:04:41.940> we<00:04:42.060> also<00:04:42.300> put<00:04:42.419> a<00:04:42.540> lot<00:04:42.600> of 00:04:42.650 --> 00:04:42.660 align:start position:0% decentralized then we also put a lot of 00:04:42.660 --> 00:04:44.330 align:start position:0% decentralized then we also put a lot of focus<00:04:42.900> into<00:04:43.139> the<00:04:43.380> schedule 00:04:44.330 --> 00:04:44.340 align:start position:0% focus into the schedule 00:04:44.340 --> 00:04:46.629 align:start position:0% focus into the schedule this<00:04:44.699> is<00:04:44.820> because<00:04:45.000> stream<00:04:45.780> it<00:04:46.020> is<00:04:46.199> not<00:04:46.380> only 00:04:46.629 --> 00:04:46.639 align:start position:0% this is because stream it is not only 00:04:46.639 --> 00:04:49.129 align:start position:0% this is because stream it is not only something<00:04:47.639> you<00:04:47.880> can<00:04:48.000> use<00:04:48.060> to<00:04:48.240> live<00:04:48.419> stream<00:04:48.600> but 00:04:49.129 --> 00:04:49.139 align:start position:0% something you can use to live stream but 00:04:49.139 --> 00:04:51.290 align:start position:0% something you can use to live stream but it's<00:04:49.320> actually<00:04:49.440> something<00:04:49.740> that<00:04:50.040> we<00:04:50.160> wanna 00:04:51.290 --> 00:04:51.300 align:start position:0% it's actually something that we wanna 00:04:51.300 --> 00:04:53.150 align:start position:0% it's actually something that we wanna that<00:04:51.540> event<00:04:51.780> organizers<00:04:52.259> want<00:04:52.440> to<00:04:52.560> use<00:04:52.740> to 00:04:53.150 --> 00:04:53.160 align:start position:0% that event organizers want to use to 00:04:53.160 --> 00:04:55.689 align:start position:0% that event organizers want to use to like<00:04:53.880> I<00:04:54.000> said<00:04:54.060> replicate<00:04:54.600> the 00:04:55.689 --> 00:04:55.699 align:start position:0% like I said replicate the 00:04:55.699 --> 00:04:58.370 align:start position:0% like I said replicate the uh<00:04:56.699> the<00:04:56.940> event<00:04:57.000> experience<00:04:57.600> experience<00:04:58.199> but 00:04:58.370 --> 00:04:58.380 align:start position:0% uh the event experience experience but 00:04:58.380 --> 00:05:00.590 align:start position:0% uh the event experience experience but virtually<00:04:58.740> right<00:04:59.040> so<00:04:59.580> the<00:04:59.699> schedule<00:04:59.940> as 00:05:00.590 --> 00:05:00.600 align:start position:0% virtually right so the schedule as 00:05:00.600 --> 00:05:02.870 align:start position:0% virtually right so the schedule as always<00:05:00.780> is<00:05:01.139> a<00:05:01.500> very 00:05:02.870 --> 00:05:02.880 align:start position:0% always is a very 00:05:02.880 --> 00:05:05.330 align:start position:0% always is a very important<00:05:03.660> part<00:05:03.840> of<00:05:04.080> any<00:05:04.320> event 00:05:05.330 --> 00:05:05.340 align:start position:0% important part of any event 00:05:05.340 --> 00:05:07.370 align:start position:0% important part of any event especially<00:05:06.180> events<00:05:06.540> like<00:05:06.600> Defcon<00:05:07.020> where<00:05:07.199> you 00:05:07.370 --> 00:05:07.380 align:start position:0% especially events like Defcon where you 00:05:07.380 --> 00:05:09.890 align:start position:0% especially events like Defcon where you have<00:05:07.500> a<00:05:07.680> lot<00:05:07.800> of<00:05:07.860> sessions<00:05:08.220> in<00:05:09.180> another<00:05:09.419> rooms 00:05:09.890 --> 00:05:09.900 align:start position:0% have a lot of sessions in another rooms 00:05:09.900 --> 00:05:11.689 align:start position:0% have a lot of sessions in another rooms you<00:05:10.440> kind<00:05:10.560> of<00:05:10.680> want<00:05:10.800> to<00:05:10.919> automate<00:05:11.280> the<00:05:11.400> process 00:05:11.689 --> 00:05:11.699 align:start position:0% you kind of want to automate the process 00:05:11.699 --> 00:05:14.150 align:start position:0% you kind of want to automate the process of<00:05:12.240> scheduling<00:05:13.080> everything<00:05:13.320> and<00:05:13.740> showing<00:05:14.040> the 00:05:14.150 --> 00:05:14.160 align:start position:0% of scheduling everything and showing the 00:05:14.160 --> 00:05:15.710 align:start position:0% of scheduling everything and showing the information<00:05:14.340> in<00:05:14.759> nice 00:05:15.710 --> 00:05:15.720 align:start position:0% information in nice 00:05:15.720 --> 00:05:18.670 align:start position:0% information in nice in<00:05:16.080> a<00:05:16.259> nice<00:05:16.580> accessible<00:05:17.580> way 00:05:18.670 --> 00:05:18.680 align:start position:0% in a nice accessible way 00:05:18.680 --> 00:05:21.170 align:start position:0% in a nice accessible way so<00:05:19.680> we<00:05:19.800> built<00:05:20.100> a<00:05:20.280> schedule 00:05:21.170 --> 00:05:21.180 align:start position:0% so we built a schedule 00:05:21.180 --> 00:05:22.490 align:start position:0% so we built a schedule by<00:05:21.540> the<00:05:21.660> way<00:05:21.660> I'm<00:05:21.840> talking<00:05:22.199> about<00:05:22.320> the 00:05:22.490 --> 00:05:22.500 align:start position:0% by the way I'm talking about the 00:05:22.500 --> 00:05:23.990 align:start position:0% by the way I'm talking about the features<00:05:22.740> then<00:05:22.919> I<00:05:23.100> will<00:05:23.160> do<00:05:23.340> a<00:05:23.460> live<00:05:23.580> demo<00:05:23.880> and 00:05:23.990 --> 00:05:24.000 align:start position:0% features then I will do a live demo and 00:05:24.000 --> 00:05:25.490 align:start position:0% features then I will do a live demo and showcase<00:05:24.300> the<00:05:24.539> application<00:05:24.960> because<00:05:25.139> I<00:05:25.380> know 00:05:25.490 --> 00:05:25.500 align:start position:0% showcase the application because I know 00:05:25.500 --> 00:05:27.950 align:start position:0% showcase the application because I know it<00:05:25.800> might<00:05:26.039> be<00:05:26.160> a<00:05:26.220> bit<00:05:26.340> difficult<00:05:26.639> to<00:05:26.820> imagine 00:05:27.950 --> 00:05:27.960 align:start position:0% it might be a bit difficult to imagine 00:05:27.960 --> 00:05:30.409 align:start position:0% it might be a bit difficult to imagine what<00:05:28.380> I'm<00:05:28.560> saying<00:05:28.800> right<00:05:28.919> now 00:05:30.409 --> 00:05:30.419 align:start position:0% what I'm saying right now 00:05:30.419 --> 00:05:32.629 align:start position:0% what I'm saying right now um<00:05:30.539> so<00:05:30.720> yeah<00:05:30.840> this<00:05:30.960> guyo<00:05:31.380> is<00:05:31.500> a<00:05:31.680> very<00:05:31.800> central 00:05:32.629 --> 00:05:32.639 align:start position:0% um so yeah this guyo is a very central 00:05:32.639 --> 00:05:36.290 align:start position:0% um so yeah this guyo is a very central part<00:05:33.000> of<00:05:33.539> of<00:05:34.020> streamies<00:05:34.800> we<00:05:35.639> build<00:05:35.820> multiple 00:05:36.290 --> 00:05:36.300 align:start position:0% part of of streamies we build multiple 00:05:36.300 --> 00:05:37.870 align:start position:0% part of of streamies we build multiple Integrations 00:05:37.870 --> 00:05:37.880 align:start position:0% Integrations 00:05:37.880 --> 00:05:41.510 align:start position:0% Integrations with<00:05:38.880> different<00:05:39.180> schedule<00:05:39.479> providers<00:05:40.520> Defcon 00:05:41.510 --> 00:05:41.520 align:start position:0% with different schedule providers Defcon 00:05:41.520 --> 00:05:45.469 align:start position:0% with different schedule providers Defcon is<00:05:41.699> using<00:05:42.440> pre-talks<00:05:43.440> as<00:05:43.740> a<00:05:43.860> schedule<00:05:43.979> manager 00:05:45.469 --> 00:05:45.479 align:start position:0% is using pre-talks as a schedule manager 00:05:45.479 --> 00:05:47.330 align:start position:0% is using pre-talks as a schedule manager which<00:05:46.020> is 00:05:47.330 --> 00:05:47.340 align:start position:0% which is 00:05:47.340 --> 00:05:49.850 align:start position:0% which is and<00:05:48.240> a<00:05:48.419> pre-talk<00:05:48.840> is<00:05:48.960> an<00:05:49.080> open<00:05:49.199> source<00:05:49.620> tool 00:05:49.850 --> 00:05:49.860 align:start position:0% and a pre-talk is an open source tool 00:05:49.860 --> 00:05:51.770 align:start position:0% and a pre-talk is an open source tool for<00:05:50.039> for<00:05:50.280> management<00:05:50.580> that<00:05:51.060> the<00:05:51.300> Devcon<00:05:51.660> team 00:05:51.770 --> 00:05:51.780 align:start position:0% for for management that the Devcon team 00:05:51.780 --> 00:05:53.629 align:start position:0% for for management that the Devcon team is<00:05:51.960> using<00:05:52.199> to<00:05:52.440> organize<00:05:53.100> all<00:05:53.220> the<00:05:53.400> sessions 00:05:53.629 --> 00:05:53.639 align:start position:0% is using to organize all the sessions 00:05:53.639 --> 00:05:56.029 align:start position:0% is using to organize all the sessions and<00:05:53.880> and<00:05:54.120> all<00:05:54.360> the<00:05:54.479> rooms<00:05:54.780> so<00:05:55.620> we<00:05:55.740> built<00:05:55.979> an 00:05:56.029 --> 00:05:56.039 align:start position:0% and and all the rooms so we built an 00:05:56.039 --> 00:05:57.529 align:start position:0% and and all the rooms so we built an integration<00:05:56.340> with<00:05:56.460> their<00:05:56.580> API<00:05:56.940> and<00:05:57.419> that's 00:05:57.529 --> 00:05:57.539 align:start position:0% integration with their API and that's 00:05:57.539 --> 00:05:59.930 align:start position:0% integration with their API and that's also<00:05:57.900> available<00:05:58.080> in<00:05:59.039> three<00:05:59.280> meets<00:05:59.639> so<00:05:59.759> if 00:05:59.930 --> 00:05:59.940 align:start position:0% also available in three meets so if 00:05:59.940 --> 00:06:01.969 align:start position:0% also available in three meets so if you're<00:06:00.060> an<00:06:00.180> event<00:06:00.300> organizer<00:06:00.900> you<00:06:01.440> can<00:06:01.500> spin 00:06:01.969 --> 00:06:01.979 align:start position:0% you're an event organizer you can spin 00:06:01.979 --> 00:06:03.230 align:start position:0% you're an event organizer you can spin up 00:06:03.230 --> 00:06:03.240 align:start position:0% up 00:06:03.240 --> 00:06:06.409 align:start position:0% up a<00:06:03.539> pretalks<00:06:04.139> incense<00:06:04.440> and 00:06:06.409 --> 00:06:06.419 align:start position:0% a pretalks incense and 00:06:06.419 --> 00:06:08.210 align:start position:0% a pretalks incense and you<00:06:06.840> know<00:06:06.900> get<00:06:07.080> going<00:06:07.320> with<00:06:07.500> that<00:06:07.620> and<00:06:07.800> have<00:06:07.979> a 00:06:08.210 --> 00:06:08.220 align:start position:0% you know get going with that and have a 00:06:08.220 --> 00:06:09.469 align:start position:0% you know get going with that and have a pretty 00:06:09.469 --> 00:06:09.479 align:start position:0% pretty 00:06:09.479 --> 00:06:14.210 align:start position:0% pretty nice<00:06:10.139> schedule<00:06:10.639> functionality<00:06:11.639> there 00:06:14.210 --> 00:06:14.220 align:start position:0% 00:06:14.220 --> 00:06:17.810 align:start position:0% um<00:06:14.720> also<00:06:15.720> the<00:06:16.259> application<00:06:16.620> has<00:06:17.100> a<00:06:17.340> internal 00:06:17.810 --> 00:06:17.820 align:start position:0% um also the application has a internal 00:06:17.820 --> 00:06:18.590 align:start position:0% um also the application has a internal clock 00:06:18.590 --> 00:06:18.600 align:start position:0% clock 00:06:18.600 --> 00:06:20.230 align:start position:0% clock which<00:06:19.080> will<00:06:19.259> basically 00:06:20.230 --> 00:06:20.240 align:start position:0% which will basically 00:06:20.240 --> 00:06:23.809 align:start position:0% which will basically sync<00:06:21.240> you<00:06:21.300> up<00:06:21.479> with<00:06:22.319> the<00:06:22.500> latest<00:06:22.620> sessions<00:06:23.340> and 00:06:23.809 --> 00:06:23.819 align:start position:0% sync you up with the latest sessions and 00:06:23.819 --> 00:06:25.189 align:start position:0% sync you up with the latest sessions and always<00:06:24.000> display<00:06:24.240> kind<00:06:24.660> of<00:06:24.840> the<00:06:25.080> current 00:06:25.189 --> 00:06:25.199 align:start position:0% always display kind of the current 00:06:25.199 --> 00:06:26.689 align:start position:0% always display kind of the current information<00:06:25.500> on 00:06:26.689 --> 00:06:26.699 align:start position:0% information on 00:06:26.699 --> 00:06:28.670 align:start position:0% information on which<00:06:27.000> stock<00:06:27.240> is<00:06:27.419> happening 00:06:28.670 --> 00:06:28.680 align:start position:0% which stock is happening 00:06:28.680 --> 00:06:30.290 align:start position:0% which stock is happening and<00:06:29.100> all<00:06:29.220> of<00:06:29.400> that<00:06:29.520> but<00:06:29.759> I<00:06:30.060> think<00:06:30.180> that's 00:06:30.290 --> 00:06:30.300 align:start position:0% and all of that but I think that's 00:06:30.300 --> 00:06:31.430 align:start position:0% and all of that but I think that's better<00:06:30.479> too 00:06:31.430 --> 00:06:31.440 align:start position:0% better too 00:06:31.440 --> 00:06:33.409 align:start position:0% better too that<00:06:31.740> you<00:06:31.979> guys<00:06:32.100> see<00:06:32.460> it<00:06:32.580> in<00:06:32.699> a<00:06:32.819> live<00:06:32.940> demo<00:06:33.240> that 00:06:33.409 --> 00:06:33.419 align:start position:0% that you guys see it in a live demo that 00:06:33.419 --> 00:06:35.749 align:start position:0% that you guys see it in a live demo that I'm<00:06:33.600> going<00:06:33.720> to<00:06:33.780> show<00:06:34.560> later 00:06:35.749 --> 00:06:35.759 align:start position:0% I'm going to show later 00:06:35.759 --> 00:06:37.490 align:start position:0% I'm going to show later then<00:06:36.120> of<00:06:36.240> course<00:06:36.360> like<00:06:36.539> we<00:06:36.660> said<00:06:36.780> On<00:06:37.199> Demand 00:06:37.490 --> 00:06:37.500 align:start position:0% then of course like we said On Demand 00:06:37.500 --> 00:06:39.230 align:start position:0% then of course like we said On Demand with<00:06:37.620> the<00:06:37.800> playback<00:06:38.039> that<00:06:38.580> is<00:06:38.759> also<00:06:38.940> crucial 00:06:39.230 --> 00:06:39.240 align:start position:0% with the playback that is also crucial 00:06:39.240 --> 00:06:40.550 align:start position:0% with the playback that is also crucial for<00:06:39.660> the 00:06:40.550 --> 00:06:40.560 align:start position:0% for the 00:06:40.560 --> 00:06:44.450 align:start position:0% for the for<00:06:41.220> the<00:06:41.400> event<00:06:41.580> organizers<00:06:42.560> actually<00:06:43.560> most 00:06:44.450 --> 00:06:44.460 align:start position:0% for the event organizers actually most 00:06:44.460 --> 00:06:47.029 align:start position:0% for the event organizers actually most of<00:06:44.639> the<00:06:44.759> views<00:06:45.120> for<00:06:45.300> events<00:06:45.660> happen<00:06:45.840> during 00:06:47.029 --> 00:06:47.039 align:start position:0% of the views for events happen during 00:06:47.039 --> 00:06:50.150 align:start position:0% of the views for events happen during on<00:06:47.580> demand<00:06:47.880> playback<00:06:48.240> so<00:06:48.780> a<00:06:49.139> live<00:06:49.319> video 00:06:50.150 --> 00:06:50.160 align:start position:0% on demand playback so a live video 00:06:50.160 --> 00:06:52.189 align:start position:0% on demand playback so a live video don't<00:06:50.639> usually<00:06:50.940> get<00:06:51.120> too<00:06:51.300> many<00:06:51.479> views<00:06:51.840> but 00:06:52.189 --> 00:06:52.199 align:start position:0% don't usually get too many views but 00:06:52.199 --> 00:06:53.629 align:start position:0% don't usually get too many views but then<00:06:52.319> when<00:06:52.680> you 00:06:53.629 --> 00:06:53.639 align:start position:0% then when you 00:06:53.639 --> 00:06:55.570 align:start position:0% then when you when<00:06:53.940> you<00:06:54.120> saw<00:06:54.240> the<00:06:54.479> video<00:06:54.660> and<00:06:54.960> you<00:06:55.080> show<00:06:55.259> it 00:06:55.570 --> 00:06:55.580 align:start position:0% when you saw the video and you show it 00:06:55.580 --> 00:06:57.529 align:start position:0% when you saw the video and you show it on<00:06:56.580> demand 00:06:57.529 --> 00:06:57.539 align:start position:0% on demand 00:06:57.539 --> 00:06:59.090 align:start position:0% on demand because<00:06:58.259> of<00:06:58.440> the<00:06:58.500> content<00:06:58.740> we're<00:06:58.860> showing 00:06:59.090 --> 00:06:59.100 align:start position:0% because of the content we're showing 00:06:59.100 --> 00:07:00.730 align:start position:0% because of the content we're showing here<00:06:59.220> in<00:06:59.400> the<00:06:59.580> stocks<00:06:59.880> is<00:07:00.000> very<00:07:00.180> interesting 00:07:00.730 --> 00:07:00.740 align:start position:0% here in the stocks is very interesting 00:07:00.740 --> 00:07:04.550 align:start position:0% here in the stocks is very interesting you<00:07:01.740> know<00:07:01.860> people<00:07:01.979> go<00:07:02.280> and<00:07:02.699> watch<00:07:03.180> it 00:07:04.550 --> 00:07:04.560 align:start position:0% you know people go and watch it 00:07:04.560 --> 00:07:08.510 align:start position:0% you know people go and watch it so<00:07:05.460> yeah<00:07:05.520> this<00:07:05.819> is<00:07:05.940> also<00:07:06.680> currently<00:07:07.680> all<00:07:08.340> the 00:07:08.510 --> 00:07:08.520 align:start position:0% so yeah this is also currently all the 00:07:08.520 --> 00:07:11.390 align:start position:0% so yeah this is also currently all the on-demand<00:07:09.000> video<00:07:09.380> that<00:07:10.380> we<00:07:10.620> are<00:07:10.740> hosting<00:07:11.100> on 00:07:11.390 --> 00:07:11.400 align:start position:0% on-demand video that we are hosting on 00:07:11.400 --> 00:07:13.309 align:start position:0% on-demand video that we are hosting on different<00:07:11.580> stream<00:07:11.819> with<00:07:12.060> instances<00:07:12.479> it's 00:07:13.309 --> 00:07:13.319 align:start position:0% different stream with instances it's 00:07:13.319 --> 00:07:15.409 align:start position:0% different stream with instances it's also<00:07:13.620> living<00:07:13.740> on<00:07:13.979> their<00:07:14.100> life<00:07:14.280> your<00:07:14.460> network 00:07:15.409 --> 00:07:15.419 align:start position:0% also living on their life your network 00:07:15.419 --> 00:07:19.070 align:start position:0% also living on their life your network they<00:07:16.139> recently<00:07:16.560> developed<00:07:17.699> their<00:07:18.479> video<00:07:18.900> on 00:07:19.070 --> 00:07:19.080 align:start position:0% they recently developed their video on 00:07:19.080 --> 00:07:20.990 align:start position:0% they recently developed their video on demand<00:07:19.440> features<00:07:20.160> so<00:07:20.400> it's<00:07:20.520> working<00:07:20.699> very 00:07:20.990 --> 00:07:21.000 align:start position:0% demand features so it's working very 00:07:21.000 --> 00:07:22.610 align:start position:0% demand features so it's working very nicely 00:07:22.610 --> 00:07:22.620 align:start position:0% nicely 00:07:22.620 --> 00:07:24.469 align:start position:0% nicely um 00:07:24.469 --> 00:07:24.479 align:start position:0% um 00:07:24.479 --> 00:07:26.809 align:start position:0% um and<00:07:25.020> I'll<00:07:25.080> also<00:07:25.319> Show<00:07:25.560> an<00:07:26.039> example<00:07:26.340> of<00:07:26.699> a 00:07:26.809 --> 00:07:26.819 align:start position:0% and I'll also Show an example of a 00:07:26.819 --> 00:07:28.370 align:start position:0% and I'll also Show an example of a streaming<00:07:27.240> instance<00:07:27.539> where<00:07:27.780> we<00:07:27.900> used<00:07:28.080> video 00:07:28.370 --> 00:07:28.380 align:start position:0% streaming instance where we used video 00:07:28.380 --> 00:07:29.390 align:start position:0% streaming instance where we used video on<00:07:28.620> demand 00:07:29.390 --> 00:07:29.400 align:start position:0% on demand 00:07:29.400 --> 00:07:31.909 align:start position:0% on demand it<00:07:30.000> was<00:07:30.300> at<00:07:30.419> East<00:07:30.539> Berlin<00:07:30.900> last<00:07:31.139> month 00:07:31.909 --> 00:07:31.919 align:start position:0% it was at East Berlin last month 00:07:31.919 --> 00:07:35.029 align:start position:0% it was at East Berlin last month it<00:07:32.340> worked<00:07:32.580> very<00:07:32.639> very<00:07:32.699> nicely<00:07:33.180> so<00:07:33.479> I'll<00:07:33.720> show 00:07:35.029 --> 00:07:35.039 align:start position:0% it worked very very nicely so I'll show 00:07:35.039 --> 00:07:37.969 align:start position:0% it worked very very nicely so I'll show a<00:07:35.639> demo<00:07:36.360> of<00:07:36.419> that<00:07:36.599> as<00:07:36.720> well<00:07:37.319> and<00:07:37.740> finally 00:07:37.969 --> 00:07:37.979 align:start position:0% a demo of that as well and finally 00:07:37.979 --> 00:07:39.730 align:start position:0% a demo of that as well and finally plugins 00:07:39.730 --> 00:07:39.740 align:start position:0% plugins 00:07:39.740 --> 00:07:42.890 align:start position:0% plugins and<00:07:40.740> I<00:07:41.400> think<00:07:41.460> this<00:07:41.639> is<00:07:41.819> the<00:07:42.000> most<00:07:42.240> interesting 00:07:42.890 --> 00:07:42.900 align:start position:0% and I think this is the most interesting 00:07:42.900 --> 00:07:47.570 align:start position:0% and I think this is the most interesting feature<00:07:44.340> and<00:07:45.180> so<00:07:46.020> the<00:07:46.560> software<00:07:46.979> architecture 00:07:47.570 --> 00:07:47.580 align:start position:0% feature and so the software architecture 00:07:47.580 --> 00:07:51.710 align:start position:0% feature and so the software architecture that<00:07:47.880> we<00:07:48.120> built<00:07:49.139> was<00:07:49.740> taught<00:07:50.099> to<00:07:51.000> contain<00:07:51.360> this 00:07:51.710 --> 00:07:51.720 align:start position:0% that we built was taught to contain this 00:07:51.720 --> 00:07:54.529 align:start position:0% that we built was taught to contain this plug-in<00:07:52.139> feature<00:07:52.560> right<00:07:52.740> so<00:07:53.639> essentially<00:07:54.060> we 00:07:54.529 --> 00:07:54.539 align:start position:0% plug-in feature right so essentially we 00:07:54.539 --> 00:07:56.809 align:start position:0% plug-in feature right so essentially we in<00:07:55.020> the<00:07:55.080> long<00:07:55.199> term<00:07:55.319> of<00:07:55.560> course<00:07:55.680> we<00:07:56.639> want 00:07:56.809 --> 00:07:56.819 align:start position:0% in the long term of course we want 00:07:56.819 --> 00:07:59.570 align:start position:0% in the long term of course we want different<00:07:57.060> protocols<00:07:57.840> to<00:07:58.259> build<00:07:59.160> plugins 00:07:59.570 --> 00:07:59.580 align:start position:0% different protocols to build plugins 00:07:59.580 --> 00:08:01.670 align:start position:0% different protocols to build plugins into<00:08:00.300> streaming<00:08:00.840> so<00:08:01.199> that<00:08:01.319> they<00:08:01.500> can 00:08:01.670 --> 00:08:01.680 align:start position:0% into streaming so that they can 00:08:01.680 --> 00:08:03.850 align:start position:0% into streaming so that they can integrate<00:08:02.340> their<00:08:02.580> features 00:08:03.850 --> 00:08:03.860 align:start position:0% integrate their features 00:08:03.860 --> 00:08:06.469 align:start position:0% integrate their features into<00:08:04.860> the<00:08:05.099> application<00:08:05.400> right<00:08:05.699> so<00:08:06.300> for 00:08:06.469 --> 00:08:06.479 align:start position:0% into the application right so for 00:08:06.479 --> 00:08:08.990 align:start position:0% into the application right so for instance<00:08:06.660> we<00:08:07.020> are<00:08:07.139> working<00:08:07.380> with<00:08:07.680> radical<00:08:08.460> to 00:08:08.990 --> 00:08:09.000 align:start position:0% instance we are working with radical to 00:08:09.000 --> 00:08:11.330 align:start position:0% instance we are working with radical to integrate<00:08:09.300> radical<00:08:09.660> drips<00:08:10.440> and<00:08:10.979> that<00:08:11.160> will 00:08:11.330 --> 00:08:11.340 align:start position:0% integrate radical drips and that will 00:08:11.340 --> 00:08:13.309 align:start position:0% integrate radical drips and that will allow<00:08:11.580> to<00:08:11.940> I<00:08:12.720> don't<00:08:12.840> know<00:08:12.900> if<00:08:12.960> you<00:08:13.080> guys<00:08:13.199> know 00:08:13.309 --> 00:08:13.319 align:start position:0% allow to I don't know if you guys know 00:08:13.319 --> 00:08:15.830 align:start position:0% allow to I don't know if you guys know radical<00:08:13.620> drips<00:08:13.979> but<00:08:14.220> it's<00:08:14.340> basically<00:08:14.699> a 00:08:15.830 --> 00:08:15.840 align:start position:0% radical drips but it's basically a 00:08:15.840 --> 00:08:17.990 align:start position:0% radical drips but it's basically a a<00:08:16.259> product<00:08:16.500> that<00:08:16.740> allows<00:08:17.099> to 00:08:17.990 --> 00:08:18.000 align:start position:0% a product that allows to 00:08:18.000 --> 00:08:22.550 align:start position:0% a product that allows to have<00:08:18.720> tipping<00:08:19.500> on<00:08:20.099> web<00:08:20.900> interfaces<00:08:21.900> so<00:08:22.440> you 00:08:22.550 --> 00:08:22.560 align:start position:0% have tipping on web interfaces so you 00:08:22.560 --> 00:08:24.230 align:start position:0% have tipping on web interfaces so you could<00:08:22.620> have<00:08:22.740> a<00:08:22.860> streaming<00:08:23.280> stream<00:08:23.699> instance 00:08:24.230 --> 00:08:24.240 align:start position:0% could have a streaming stream instance 00:08:24.240 --> 00:08:26.089 align:start position:0% could have a streaming stream instance where<00:08:24.539> you're<00:08:24.780> live<00:08:25.139> streaming<00:08:25.500> an<00:08:25.620> event<00:08:25.800> and 00:08:26.089 --> 00:08:26.099 align:start position:0% where you're live streaming an event and 00:08:26.099 --> 00:08:28.070 align:start position:0% where you're live streaming an event and then<00:08:26.220> you<00:08:26.340> have<00:08:26.520> the<00:08:27.060> radical<00:08:27.360> drips<00:08:27.660> plugin 00:08:28.070 --> 00:08:28.080 align:start position:0% then you have the radical drips plugin 00:08:28.080 --> 00:08:30.890 align:start position:0% then you have the radical drips plugin and<00:08:28.560> so<00:08:28.740> users<00:08:29.699> of<00:08:30.000> that 00:08:30.890 --> 00:08:30.900 align:start position:0% and so users of that 00:08:30.900 --> 00:08:33.529 align:start position:0% and so users of that viewers<00:08:31.620> of<00:08:31.800> that<00:08:32.039> event<00:08:32.820> could<00:08:33.120> donate 00:08:33.529 --> 00:08:33.539 align:start position:0% viewers of that event could donate 00:08:33.539 --> 00:08:35.089 align:start position:0% viewers of that event could donate directly<00:08:33.839> to<00:08:33.959> the<00:08:34.080> speakers<00:08:34.260> which<00:08:34.860> I<00:08:34.979> think 00:08:35.089 --> 00:08:35.099 align:start position:0% directly to the speakers which I think 00:08:35.099 --> 00:08:38.630 align:start position:0% directly to the speakers which I think is<00:08:35.279> pretty<00:08:35.520> cool<00:08:35.700> right<00:08:35.940> so<00:08:36.479> the<00:08:36.659> plugin 00:08:38.630 --> 00:08:38.640 align:start position:0% is pretty cool right so the plugin 00:08:38.640 --> 00:08:40.730 align:start position:0% is pretty cool right so the plugin um<00:08:38.760> architecture<00:08:39.599> is<00:08:39.719> there<00:08:39.959> now<00:08:40.320> we<00:08:40.500> need<00:08:40.680> to 00:08:40.730 --> 00:08:40.740 align:start position:0% um architecture is there now we need to 00:08:40.740 --> 00:08:43.130 align:start position:0% um architecture is there now we need to develop<00:08:40.979> the<00:08:41.159> ecosystem<00:08:41.520> and<00:08:42.240> you<00:08:42.839> know<00:08:42.899> bring 00:08:43.130 --> 00:08:43.140 align:start position:0% develop the ecosystem and you know bring 00:08:43.140 --> 00:08:45.590 align:start position:0% develop the ecosystem and you know bring people<00:08:43.320> in<00:08:43.560> to<00:08:43.860> develop<00:08:44.099> this<00:08:44.459> plugins<00:08:44.760> for<00:08:44.940> us 00:08:45.590 --> 00:08:45.600 align:start position:0% people in to develop this plugins for us 00:08:45.600 --> 00:08:47.150 align:start position:0% people in to develop this plugins for us oh<00:08:46.080> and<00:08:46.260> this<00:08:46.380> is<00:08:46.500> the<00:08:46.620> slide<00:08:46.740> where<00:08:46.920> I<00:08:47.040> show 00:08:47.150 --> 00:08:47.160 align:start position:0% oh and this is the slide where I show 00:08:47.160 --> 00:08:49.670 align:start position:0% oh and this is the slide where I show the<00:08:47.279> live<00:08:47.399> demo<00:08:47.760> so<00:08:48.360> I'm<00:08:48.480> gonna 00:08:49.670 --> 00:08:49.680 align:start position:0% the live demo so I'm gonna 00:08:49.680 --> 00:08:51.590 align:start position:0% the live demo so I'm gonna uh<00:08:50.580> yeah 00:08:51.590 --> 00:08:51.600 align:start position:0% uh yeah 00:08:51.600 --> 00:08:53.030 align:start position:0% uh yeah yes 00:08:53.030 --> 00:08:53.040 align:start position:0% yes 00:08:53.040 --> 00:08:55.490 align:start position:0% yes so<00:08:53.880> this<00:08:54.240> is<00:08:54.360> the<00:08:54.480> stream<00:08:54.600> instance<00:08:55.200> that<00:08:55.380> we 00:08:55.490 --> 00:08:55.500 align:start position:0% so this is the stream instance that we 00:08:55.500 --> 00:08:57.350 align:start position:0% so this is the stream instance that we use<00:08:55.680> for<00:08:56.220> a 00:08:57.350 --> 00:08:57.360 align:start position:0% use for a 00:08:57.360 --> 00:08:59.570 align:start position:0% use for a Defcon 00:08:59.570 --> 00:08:59.580 align:start position:0% Defcon 00:08:59.580 --> 00:09:02.030 align:start position:0% Defcon and<00:09:00.000> we<00:09:00.180> can<00:09:00.240> see<00:09:00.420> there<00:09:00.600> that 00:09:02.030 --> 00:09:02.040 align:start position:0% and we can see there that 00:09:02.040 --> 00:09:03.470 align:start position:0% and we can see there that the<00:09:02.399> biggest<00:09:02.459> buffering<00:09:02.940> because<00:09:03.120> the<00:09:03.300> Wi-Fi 00:09:03.470 --> 00:09:03.480 align:start position:0% the biggest buffering because the Wi-Fi 00:09:03.480 --> 00:09:05.889 align:start position:0% the biggest buffering because the Wi-Fi isn't<00:09:04.080> the<00:09:04.380> best<00:09:04.500> in<00:09:04.680> the<00:09:04.860> world 00:09:05.889 --> 00:09:05.899 align:start position:0% isn't the best in the world 00:09:05.899 --> 00:09:09.710 align:start position:0% isn't the best in the world but<00:09:06.899> yeah<00:09:07.019> so<00:09:07.560> like<00:09:08.339> I<00:09:08.459> said 00:09:09.710 --> 00:09:09.720 align:start position:0% but yeah so like I said 00:09:09.720 --> 00:09:11.750 align:start position:0% but yeah so like I said we<00:09:10.080> are<00:09:10.200> live<00:09:10.380> streaming 00:09:11.750 --> 00:09:11.760 align:start position:0% we are live streaming 00:09:11.760 --> 00:09:13.490 align:start position:0% we are live streaming through<00:09:12.180> life<00:09:12.360> here<00:09:12.600> this<00:09:12.899> is<00:09:13.019> the<00:09:13.080> main<00:09:13.260> stage 00:09:13.490 --> 00:09:13.500 align:start position:0% through life here this is the main stage 00:09:13.500 --> 00:09:16.250 align:start position:0% through life here this is the main stage as<00:09:13.980> you<00:09:14.100> guys<00:09:14.220> can<00:09:14.339> see<00:09:14.940> so<00:09:15.839> even<00:09:16.019> though 00:09:16.250 --> 00:09:16.260 align:start position:0% as you guys can see so even though 00:09:16.260 --> 00:09:18.230 align:start position:0% as you guys can see so even though network<00:09:16.500> connections<00:09:16.980> are<00:09:17.100> pretty<00:09:17.580> it's 00:09:18.230 --> 00:09:18.240 align:start position:0% network connections are pretty it's 00:09:18.240 --> 00:09:20.509 align:start position:0% network connections are pretty it's working<00:09:18.420> fine<00:09:18.779> right<00:09:19.080> so<00:09:19.800> Props<00:09:20.220> to<00:09:20.279> the<00:09:20.399> live 00:09:20.509 --> 00:09:20.519 align:start position:0% working fine right so Props to the live 00:09:20.519 --> 00:09:22.310 align:start position:0% working fine right so Props to the live routine 00:09:22.310 --> 00:09:22.320 align:start position:0% routine 00:09:22.320 --> 00:09:25.310 align:start position:0% routine um<00:09:22.440> in<00:09:23.100> this<00:09:23.220> case<00:09:23.339> we<00:09:23.640> also<00:09:23.820> added<00:09:24.180> a<00:09:24.959> YouTube 00:09:25.310 --> 00:09:25.320 align:start position:0% um in this case we also added a YouTube 00:09:25.320 --> 00:09:26.150 align:start position:0% um in this case we also added a YouTube link 00:09:26.150 --> 00:09:26.160 align:start position:0% link 00:09:26.160 --> 00:09:28.310 align:start position:0% link so<00:09:26.700> the<00:09:26.880> good<00:09:27.000> thing<00:09:27.120> was<00:09:27.300> about<00:09:27.600> streaming<00:09:28.140> is 00:09:28.310 --> 00:09:28.320 align:start position:0% so the good thing was about streaming is 00:09:28.320 --> 00:09:29.889 align:start position:0% so the good thing was about streaming is that<00:09:28.560> because<00:09:28.740> it's<00:09:28.980> an<00:09:29.160> open<00:09:29.339> source 00:09:29.889 --> 00:09:29.899 align:start position:0% that because it's an open source 00:09:29.899 --> 00:09:33.290 align:start position:0% that because it's an open source application<00:09:30.899> each<00:09:31.800> instance<00:09:32.220> can<00:09:33.120> be 00:09:33.290 --> 00:09:33.300 align:start position:0% application each instance can be 00:09:33.300 --> 00:09:35.269 align:start position:0% application each instance can be adjusted<00:09:33.779> to<00:09:34.200> the<00:09:34.380> needs<00:09:34.620> of<00:09:34.740> the<00:09:34.860> event<00:09:34.980> right 00:09:35.269 --> 00:09:35.279 align:start position:0% adjusted to the needs of the event right 00:09:35.279 --> 00:09:38.389 align:start position:0% adjusted to the needs of the event right so<00:09:35.580> for<00:09:35.760> this<00:09:35.940> in<00:09:36.180> this<00:09:36.300> case<00:09:36.420> for<00:09:36.660> Defcon<00:09:37.100> a<00:09:38.100> we 00:09:38.389 --> 00:09:38.399 align:start position:0% so for this in this case for Defcon a we 00:09:38.399 --> 00:09:40.550 align:start position:0% so for this in this case for Defcon a we also<00:09:38.640> wanted<00:09:38.760> to<00:09:38.940> include<00:09:39.360> a<00:09:40.140> YouTube<00:09:40.320> stream 00:09:40.550 --> 00:09:40.560 align:start position:0% also wanted to include a YouTube stream 00:09:40.560 --> 00:09:42.650 align:start position:0% also wanted to include a YouTube stream for<00:09:41.100> a 00:09:42.650 --> 00:09:42.660 align:start position:0% for a 00:09:42.660 --> 00:09:45.110 align:start position:0% for a you<00:09:43.019> know<00:09:43.080> to<00:09:43.320> to<00:09:43.620> have<00:09:43.860> the<00:09:43.980> maximum<00:09:44.339> reach 00:09:45.110 --> 00:09:45.120 align:start position:0% you know to to have the maximum reach 00:09:45.120 --> 00:09:46.970 align:start position:0% you know to to have the maximum reach and<00:09:45.660> so<00:09:45.839> we<00:09:46.019> have<00:09:46.080> we're<00:09:46.260> streaming<00:09:46.620> both<00:09:46.800> on 00:09:46.970 --> 00:09:46.980 align:start position:0% and so we have we're streaming both on 00:09:46.980 --> 00:09:48.710 align:start position:0% and so we have we're streaming both on library<00:09:47.220> and<00:09:47.519> YouTube<00:09:47.700> and<00:09:48.000> with<00:09:48.120> other<00:09:48.360> with 00:09:48.710 --> 00:09:48.720 align:start position:0% library and YouTube and with other with 00:09:48.720 --> 00:09:51.110 align:start position:0% library and YouTube and with other with other<00:09:48.839> added<00:09:49.380> this<00:09:49.500> nice<00:09:49.740> switcher<00:09:50.580> in<00:09:51.000> the 00:09:51.110 --> 00:09:51.120 align:start position:0% other added this nice switcher in the 00:09:51.120 --> 00:09:52.730 align:start position:0% other added this nice switcher in the bottom<00:09:51.360> so<00:09:51.480> you<00:09:51.600> can<00:09:51.720> switch<00:09:51.839> between 00:09:52.730 --> 00:09:52.740 align:start position:0% bottom so you can switch between 00:09:52.740 --> 00:09:55.329 align:start position:0% bottom so you can switch between like<00:09:53.160> I<00:09:53.279> said<00:09:53.399> then<00:09:53.580> the<00:09:53.760> schedule 00:09:55.329 --> 00:09:55.339 align:start position:0% like I said then the schedule 00:09:55.339 --> 00:09:57.230 align:start position:0% like I said then the schedule for<00:09:56.339> this 00:09:57.230 --> 00:09:57.240 align:start position:0% for this 00:09:57.240 --> 00:09:59.389 align:start position:0% for this instance<00:09:58.019> we<00:09:58.200> build<00:09:58.380> the<00:09:58.500> schedule<00:09:58.680> into<00:09:58.980> a 00:09:59.389 --> 00:09:59.399 align:start position:0% instance we build the schedule into a 00:09:59.399 --> 00:10:01.490 align:start position:0% instance we build the schedule into a nice<00:09:59.580> navigation<00:10:00.000> bar<00:10:00.240> on<00:10:00.540> the<00:10:00.660> right<00:10:00.839> panel 00:10:01.490 --> 00:10:01.500 align:start position:0% nice navigation bar on the right panel 00:10:01.500 --> 00:10:04.250 align:start position:0% nice navigation bar on the right panel of<00:10:01.860> the<00:10:02.580> page<00:10:02.760> you<00:10:03.540> can 00:10:04.250 --> 00:10:04.260 align:start position:0% of the page you can 00:10:04.260 --> 00:10:07.550 align:start position:0% of the page you can kind<00:10:04.620> of<00:10:04.740> look<00:10:04.860> through<00:10:05.100> all<00:10:05.339> the<00:10:05.519> talks 00:10:07.550 --> 00:10:07.560 align:start position:0% kind of look through all the talks 00:10:07.560 --> 00:10:09.290 align:start position:0% kind of look through all the talks so<00:10:07.920> yeah<00:10:07.980> when<00:10:08.220> I<00:10:08.339> refresh<00:10:08.640> you<00:10:08.820> guys<00:10:09.000> can<00:10:09.180> see 00:10:09.290 --> 00:10:09.300 align:start position:0% so yeah when I refresh you guys can see 00:10:09.300 --> 00:10:11.090 align:start position:0% so yeah when I refresh you guys can see that<00:10:09.420> the<00:10:09.600> schedule<00:10:09.779> kind<00:10:10.440> of<00:10:10.560> synced<00:10:10.860> to<00:10:10.980> the 00:10:11.090 --> 00:10:11.100 align:start position:0% that the schedule kind of synced to the 00:10:11.100 --> 00:10:13.490 align:start position:0% that the schedule kind of synced to the latest<00:10:11.220> hour<00:10:11.820> and 00:10:13.490 --> 00:10:13.500 align:start position:0% latest hour and 00:10:13.500 --> 00:10:16.610 align:start position:0% latest hour and so<00:10:13.860> this<00:10:13.980> should<00:10:14.220> be<00:10:14.399> me<00:10:15.060> oh<00:10:15.839> no<00:10:16.019> I'm<00:10:16.260> this<00:10:16.500> is 00:10:16.610 --> 00:10:16.620 align:start position:0% so this should be me oh no I'm this is 00:10:16.620 --> 00:10:18.470 align:start position:0% so this should be me oh no I'm this is talk<00:10:16.740> five<00:10:16.980> this<00:10:17.339> is<00:10:17.459> not<00:10:17.519> my<00:10:17.700> stage<00:10:17.940> so<00:10:18.300> yeah 00:10:18.470 --> 00:10:18.480 align:start position:0% talk five this is not my stage so yeah 00:10:18.480 --> 00:10:22.070 align:start position:0% talk five this is not my stage so yeah right<00:10:19.140> now<00:10:19.320> in<00:10:19.500> stage<00:10:19.860> five 00:10:22.070 --> 00:10:22.080 align:start position:0% 00:10:22.080 --> 00:10:24.889 align:start position:0% how<00:10:22.440> to<00:10:22.560> scale<00:10:22.860> the<00:10:23.220> blockchain<00:10:23.580> is<00:10:23.940> happening 00:10:24.889 --> 00:10:24.899 align:start position:0% how to scale the blockchain is happening 00:10:24.899 --> 00:10:27.170 align:start position:0% how to scale the blockchain is happening and<00:10:25.500> so<00:10:25.740> that's<00:10:25.920> what<00:10:26.100> that's<00:10:26.459> the<00:10:26.700> internal 00:10:27.170 --> 00:10:27.180 align:start position:0% and so that's what that's the internal 00:10:27.180 --> 00:10:31.070 align:start position:0% and so that's what that's the internal clock<00:10:27.360> feature<00:10:27.779> that<00:10:27.839> I<00:10:27.959> was<00:10:28.080> talking<00:10:28.200> about 00:10:31.070 --> 00:10:31.080 align:start position:0% 00:10:31.080 --> 00:10:33.350 align:start position:0% um and<00:10:31.740> yeah<00:10:31.860> it's<00:10:32.100> pretty<00:10:32.279> simple<00:10:32.580> but<00:10:33.180> it 00:10:33.350 --> 00:10:33.360 align:start position:0% um and yeah it's pretty simple but it 00:10:33.360 --> 00:10:35.389 align:start position:0% um and yeah it's pretty simple but it works<00:10:33.959> and<00:10:34.560> like<00:10:34.740> we<00:10:34.860> said<00:10:34.980> I'm<00:10:35.100> going<00:10:35.220> to<00:10:35.339> show 00:10:35.389 --> 00:10:35.399 align:start position:0% works and like we said I'm going to show 00:10:35.399 --> 00:10:37.610 align:start position:0% works and like we said I'm going to show also<00:10:35.820> and<00:10:36.480> this<00:10:36.720> is<00:10:36.839> The<00:10:36.959> Ether<00:10:37.260> Lane 00:10:37.610 --> 00:10:37.620 align:start position:0% also and this is The Ether Lane 00:10:37.620 --> 00:10:41.150 align:start position:0% also and this is The Ether Lane streaming<00:10:38.519> that<00:10:38.700> we<00:10:38.820> deployed<00:10:39.240> and 00:10:41.150 --> 00:10:41.160 align:start position:0% streaming that we deployed and 00:10:41.160 --> 00:10:43.310 align:start position:0% streaming that we deployed and this<00:10:41.640> is<00:10:41.760> a<00:10:41.940> custom<00:10:42.120> schedule<00:10:42.420> schedule<00:10:42.959> page 00:10:43.310 --> 00:10:43.320 align:start position:0% this is a custom schedule schedule page 00:10:43.320 --> 00:10:44.750 align:start position:0% this is a custom schedule schedule page that<00:10:43.800> we<00:10:43.920> built 00:10:44.750 --> 00:10:44.760 align:start position:0% that we built 00:10:44.760 --> 00:10:47.329 align:start position:0% that we built and<00:10:45.180> so<00:10:45.480> this<00:10:45.660> is<00:10:45.779> containing<00:10:46.320> all<00:10:47.160> of<00:10:47.279> the 00:10:47.329 --> 00:10:47.339 align:start position:0% and so this is containing all of the 00:10:47.339 --> 00:10:49.910 align:start position:0% and so this is containing all of the sessions<00:10:48.060> for<00:10:48.300> Ether<00:10:48.660> Lane<00:10:49.019> you<00:10:49.680> can<00:10:49.740> filter 00:10:49.910 --> 00:10:49.920 align:start position:0% sessions for Ether Lane you can filter 00:10:49.920 --> 00:10:52.610 align:start position:0% sessions for Ether Lane you can filter by<00:10:50.279> state<00:10:50.700> stages<00:10:51.240> and<00:10:51.540> days 00:10:52.610 --> 00:10:52.620 align:start position:0% by state stages and days 00:10:52.620 --> 00:10:54.949 align:start position:0% by state stages and days and<00:10:53.100> so<00:10:53.220> when<00:10:53.399> you<00:10:53.519> click<00:10:53.700> on<00:10:53.820> a<00:10:53.940> session<00:10:54.060> it 00:10:54.949 --> 00:10:54.959 align:start position:0% and so when you click on a session it 00:10:54.959 --> 00:10:56.930 align:start position:0% and so when you click on a session it goes<00:10:55.140> to<00:10:55.200> the<00:10:55.320> session<00:10:55.500> page<00:10:55.800> and<00:10:56.399> it<00:10:56.519> loads<00:10:56.820> up 00:10:56.930 --> 00:10:56.940 align:start position:0% goes to the session page and it loads up 00:10:56.940 --> 00:11:00.110 align:start position:0% goes to the session page and it loads up the<00:10:57.480> VOD<00:10:58.140> content<00:10:58.680> and<00:10:59.519> also<00:10:59.700> some<00:10:59.820> speaker 00:11:00.110 --> 00:11:00.120 align:start position:0% the VOD content and also some speaker 00:11:00.120 --> 00:11:01.610 align:start position:0% the VOD content and also some speaker information<00:11:00.420> and<00:11:01.079> kind<00:11:01.260> of<00:11:01.320> like<00:11:01.440> the 00:11:01.610 --> 00:11:01.620 align:start position:0% information and kind of like the 00:11:01.620 --> 00:11:03.310 align:start position:0% information and kind of like the description<00:11:01.920> of<00:11:02.160> the<00:11:02.220> event 00:11:03.310 --> 00:11:03.320 align:start position:0% description of the event 00:11:03.320 --> 00:11:07.069 align:start position:0% description of the event and<00:11:04.320> let's<00:11:04.500> see<00:11:04.740> if<00:11:04.800> the<00:11:04.920> VOD<00:11:05.220> video<00:11:06.000> like<00:11:06.839> go 00:11:07.069 --> 00:11:07.079 align:start position:0% and let's see if the VOD video like go 00:11:07.079 --> 00:11:10.190 align:start position:0% and let's see if the VOD video like go check<00:11:07.260> it<00:11:07.380> out<00:11:07.500> watch<00:11:07.740> the<00:11:08.300> etherlin.org<00:11:09.300> and 00:11:10.190 --> 00:11:10.200 align:start position:0% check it out watch the etherlin.org and 00:11:10.200 --> 00:11:12.889 align:start position:0% check it out watch the etherlin.org and it's<00:11:10.620> very<00:11:10.800> good<00:11:11.040> content<00:11:12.000> so<00:11:12.540> yeah<00:11:12.600> like<00:11:12.779> I 00:11:12.889 --> 00:11:12.899 align:start position:0% it's very good content so yeah like I 00:11:12.899 --> 00:11:14.509 align:start position:0% it's very good content so yeah like I said<00:11:13.019> at<00:11:13.200> the<00:11:13.320> beginning<00:11:13.440> three<00:11:14.160> basic 00:11:14.509 --> 00:11:14.519 align:start position:0% said at the beginning three basic 00:11:14.519 --> 00:11:19.190 align:start position:0% said at the beginning three basic features<00:11:14.880> but<00:11:15.300> very<00:11:16.079> powerful<00:11:16.740> uh 00:11:19.190 --> 00:11:19.200 align:start position:0% features but very powerful uh 00:11:19.200 --> 00:11:21.470 align:start position:0% features but very powerful uh and<00:11:19.920> you<00:11:20.160> know<00:11:20.279> very<00:11:20.640> effective<00:11:21.060> as<00:11:21.300> well 00:11:21.470 --> 00:11:21.480 align:start position:0% and you know very effective as well 00:11:21.480 --> 00:11:23.990 align:start position:0% and you know very effective as well because<00:11:21.660> the<00:11:21.899> main<00:11:22.079> goal<00:11:22.380> was<00:11:22.620> to<00:11:22.860> decouple 00:11:23.990 --> 00:11:24.000 align:start position:0% because the main goal was to decouple 00:11:24.000 --> 00:11:27.290 align:start position:0% because the main goal was to decouple uh<00:11:24.720> Eve<00:11:25.079> events<00:11:25.500> and<00:11:25.920> community<00:11:26.100> events<00:11:26.700> of 00:11:27.290 --> 00:11:27.300 align:start position:0% uh Eve events and community events of 00:11:27.300 --> 00:11:30.110 align:start position:0% uh Eve events and community events of centralized<00:11:28.260> platforms<00:11:28.920> like<00:11:29.040> YouTube<00:11:29.760> right 00:11:30.110 --> 00:11:30.120 align:start position:0% centralized platforms like YouTube right 00:11:30.120 --> 00:11:32.389 align:start position:0% centralized platforms like YouTube right so<00:11:30.839> I<00:11:31.019> think<00:11:31.140> even<00:11:31.740> though<00:11:31.980> it's<00:11:32.220> nothing 00:11:32.389 --> 00:11:32.399 align:start position:0% so I think even though it's nothing 00:11:32.399 --> 00:11:35.389 align:start position:0% so I think even though it's nothing fancy<00:11:32.940> we're<00:11:33.300> not<00:11:33.480> tweets<00:11:33.899> we<00:11:34.500> don't<00:11:34.620> do<00:11:34.800> VR<00:11:35.220> we 00:11:35.389 --> 00:11:35.399 align:start position:0% fancy we're not tweets we don't do VR we 00:11:35.399 --> 00:11:38.750 align:start position:0% fancy we're not tweets we don't do VR we don't<00:11:35.579> do<00:11:35.760> 3d<00:11:36.300> nothing<00:11:36.740> it<00:11:37.740> really<00:11:37.980> serves<00:11:38.459> a 00:11:38.750 --> 00:11:38.760 align:start position:0% don't do 3d nothing it really serves a 00:11:38.760 --> 00:11:40.150 align:start position:0% don't do 3d nothing it really serves a purpose<00:11:39.060> right 00:11:40.150 --> 00:11:40.160 align:start position:0% purpose right 00:11:40.160 --> 00:11:42.410 align:start position:0% purpose right and<00:11:41.160> and<00:11:41.459> now<00:11:41.700> because<00:11:42.000> I'm<00:11:42.180> talking<00:11:42.360> about 00:11:42.410 --> 00:11:42.420 align:start position:0% and and now because I'm talking about 00:11:42.420 --> 00:11:44.030 align:start position:0% and and now because I'm talking about purpose<00:11:42.839> I<00:11:43.019> want<00:11:43.140> to<00:11:43.260> go<00:11:43.320> into<00:11:43.440> a<00:11:43.680> bit<00:11:43.740> of<00:11:43.860> the 00:11:44.030 --> 00:11:44.040 align:start position:0% purpose I want to go into a bit of the 00:11:44.040 --> 00:11:46.490 align:start position:0% purpose I want to go into a bit of the ethics<00:11:44.399> on<00:11:44.700> why<00:11:44.940> we<00:11:45.060> built<00:11:45.420> we<00:11:45.660> built<00:11:45.959> this<00:11:46.079> why 00:11:46.490 --> 00:11:46.500 align:start position:0% ethics on why we built we built this why 00:11:46.500 --> 00:11:51.470 align:start position:0% ethics on why we built we built this why we<00:11:46.740> think<00:11:46.860> it's<00:11:46.980> important<00:11:47.880> and<00:11:48.600> why<00:11:48.959> a 00:11:51.470 --> 00:11:51.480 align:start position:0% we think it's important and why a 00:11:51.480 --> 00:11:53.150 align:start position:0% we think it's important and why a yeah<00:11:51.899> no<00:11:52.079> why<00:11:52.320> we<00:11:52.440> built<00:11:52.680> this<00:11:52.740> and<00:11:52.860> why<00:11:53.040> we 00:11:53.150 --> 00:11:53.160 align:start position:0% yeah no why we built this and why we 00:11:53.160 --> 00:11:54.470 align:start position:0% yeah no why we built this and why we think<00:11:53.279> it's<00:11:53.399> important<00:11:53.700> I<00:11:54.000> think<00:11:54.180> that's<00:11:54.300> it 00:11:54.470 --> 00:11:54.480 align:start position:0% think it's important I think that's it 00:11:54.480 --> 00:11:55.310 align:start position:0% think it's important I think that's it yeah 00:11:55.310 --> 00:11:55.320 align:start position:0% yeah 00:11:55.320 --> 00:11:57.889 align:start position:0% yeah yeah<00:11:55.339> most<00:11:56.339> of<00:11:56.519> the<00:11:56.640> web<00:11:56.820> 3<00:11:57.060> events<00:11:57.480> are<00:11:57.720> being 00:11:57.889 --> 00:11:57.899 align:start position:0% yeah most of the web 3 events are being 00:11:57.899 --> 00:12:01.250 align:start position:0% yeah most of the web 3 events are being broadcasted<00:11:58.680> using<00:11:59.339> centralized<00:12:00.000> providers 00:12:01.250 --> 00:12:01.260 align:start position:0% broadcasted using centralized providers 00:12:01.260 --> 00:12:03.470 align:start position:0% broadcasted using centralized providers and<00:12:02.040> this<00:12:02.339> sucks 00:12:03.470 --> 00:12:03.480 align:start position:0% and this sucks 00:12:03.480 --> 00:12:05.930 align:start position:0% and this sucks a<00:12:03.899> lot<00:12:04.500> and<00:12:04.980> it's<00:12:05.100> not<00:12:05.339> just<00:12:05.519> because<00:12:05.640> I<00:12:05.820> say 00:12:05.930 --> 00:12:05.940 align:start position:0% a lot and it's not just because I say 00:12:05.940 --> 00:12:08.210 align:start position:0% a lot and it's not just because I say that<00:12:06.060> it<00:12:06.300> actually<00:12:06.480> sucks 00:12:08.210 --> 00:12:08.220 align:start position:0% that it actually sucks 00:12:08.220 --> 00:12:09.769 align:start position:0% that it actually sucks um like<00:12:08.700> we<00:12:08.880> all<00:12:09.000> know<00:12:09.120> YouTube<00:12:09.360> and<00:12:09.600> twitch 00:12:09.769 --> 00:12:09.779 align:start position:0% um like we all know YouTube and twitch 00:12:09.779 --> 00:12:11.690 align:start position:0% um like we all know YouTube and twitch don't<00:12:10.019> realign<00:12:10.620> with<00:12:10.860> a<00:12:10.980> core<00:12:11.160> values<00:12:11.519> of 00:12:11.690 --> 00:12:11.700 align:start position:0% don't realign with a core values of 00:12:11.700 --> 00:12:14.690 align:start position:0% don't realign with a core values of decentralization<00:12:12.420> that<00:12:12.779> we<00:12:13.019> you<00:12:13.740> know<00:12:13.920> that 00:12:14.690 --> 00:12:14.700 align:start position:0% decentralization that we you know that 00:12:14.700 --> 00:12:15.949 align:start position:0% decentralization that we you know that we're<00:12:14.880> all<00:12:15.000> here<00:12:15.180> for<00:12:15.300> and<00:12:15.540> that<00:12:15.660> we<00:12:15.779> believe 00:12:15.949 --> 00:12:15.959 align:start position:0% we're all here for and that we believe 00:12:15.959 --> 00:12:16.990 align:start position:0% we're all here for and that we believe in 00:12:16.990 --> 00:12:17.000 align:start position:0% in 00:12:17.000 --> 00:12:21.290 align:start position:0% in uh<00:12:18.000> so<00:12:18.300> stream<00:12:18.540> it<00:12:18.839> is<00:12:19.140> you<00:12:19.800> know<00:12:19.920> should<00:12:20.399> be 00:12:21.290 --> 00:12:21.300 align:start position:0% uh so stream it is you know should be 00:12:21.300 --> 00:12:23.030 align:start position:0% uh so stream it is you know should be a<00:12:21.779> good<00:12:21.959> first<00:12:22.140> step<00:12:22.320> to<00:12:22.620> help<00:12:22.740> these 00:12:23.030 --> 00:12:23.040 align:start position:0% a good first step to help these 00:12:23.040 --> 00:12:25.730 align:start position:0% a good first step to help these communities<00:12:23.459> decouple<00:12:24.120> from<00:12:24.420> from<00:12:25.019> these 00:12:25.730 --> 00:12:25.740 align:start position:0% communities decouple from from these 00:12:25.740 --> 00:12:27.290 align:start position:0% communities decouple from from these Services<00:12:25.860> right 00:12:27.290 --> 00:12:27.300 align:start position:0% Services right 00:12:27.300 --> 00:12:29.509 align:start position:0% Services right so<00:12:28.140> now<00:12:28.260> we're<00:12:28.380> going<00:12:28.500> to<00:12:28.560> look<00:12:28.680> a<00:12:28.800> bit<00:12:28.920> of<00:12:29.040> what 00:12:29.509 --> 00:12:29.519 align:start position:0% so now we're going to look a bit of what 00:12:29.519 --> 00:12:31.730 align:start position:0% so now we're going to look a bit of what are<00:12:29.760> the<00:12:29.820> problem<00:12:30.000> problems<00:12:30.420> about<00:12:30.620> that<00:12:31.620> you 00:12:31.730 --> 00:12:31.740 align:start position:0% are the problem problems about that you 00:12:31.740 --> 00:12:35.810 align:start position:0% are the problem problems about that you get<00:12:31.860> with<00:12:32.279> using<00:12:32.760> a<00:12:33.540> YouTube<00:12:33.779> right<00:12:34.140> so<00:12:35.100> the 00:12:35.810 --> 00:12:35.820 align:start position:0% get with using a YouTube right so the 00:12:35.820 --> 00:12:37.670 align:start position:0% get with using a YouTube right so the first<00:12:35.940> one<00:12:36.180> is<00:12:36.480> pretty<00:12:36.660> clear 00:12:37.670 --> 00:12:37.680 align:start position:0% first one is pretty clear 00:12:37.680 --> 00:12:41.150 align:start position:0% first one is pretty clear a<00:12:38.279> YouTube<00:12:38.519> and<00:12:39.000> twitch<00:12:39.360> and<00:12:40.019> others<00:12:40.380> are 00:12:41.150 --> 00:12:41.160 align:start position:0% a YouTube and twitch and others are 00:12:41.160 --> 00:12:44.629 align:start position:0% a YouTube and twitch and others are censorship<00:12:41.700> prone 00:12:44.629 --> 00:12:44.639 align:start position:0% 00:12:44.639 --> 00:12:45.769 align:start position:0% um 00:12:45.769 --> 00:12:45.779 align:start position:0% um 00:12:45.779 --> 00:12:49.850 align:start position:0% um so<00:12:46.260> yeah<00:12:46.440> here<00:12:47.279> I<00:12:47.579> I<00:12:47.700> put<00:12:48.060> two<00:12:48.240> tweets<00:12:49.019> and<00:12:49.560> the 00:12:49.850 --> 00:12:49.860 align:start position:0% so yeah here I I put two tweets and the 00:12:49.860 --> 00:12:53.269 align:start position:0% so yeah here I I put two tweets and the first<00:12:49.980> one<00:12:50.160> was<00:12:50.700> at<00:12:50.940> East<00:12:51.180> Barcelona<00:12:51.920> and<00:12:52.920> the 00:12:53.269 --> 00:12:53.279 align:start position:0% first one was at East Barcelona and the 00:12:53.279 --> 00:12:55.430 align:start position:0% first one was at East Barcelona and the live<00:12:53.399> stream<00:12:53.579> was<00:12:53.760> taken<00:12:54.060> down<00:12:54.240> because<00:12:54.600> they 00:12:55.430 --> 00:12:55.440 align:start position:0% live stream was taken down because they 00:12:55.440 --> 00:12:57.530 align:start position:0% live stream was taken down because they had<00:12:55.620> some<00:12:55.800> copyright<00:12:56.160> issues<00:12:56.700> which<00:12:57.420> is 00:12:57.530 --> 00:12:57.540 align:start position:0% had some copyright issues which is 00:12:57.540 --> 00:12:58.970 align:start position:0% had some copyright issues which is usually 00:12:58.970 --> 00:12:58.980 align:start position:0% usually 00:12:58.980 --> 00:13:00.710 align:start position:0% usually I<00:12:59.459> mean<00:12:59.519> if<00:12:59.700> event<00:12:59.940> production<00:13:00.360> is<00:13:00.540> pretty 00:13:00.710 --> 00:13:00.720 align:start position:0% I mean if event production is pretty 00:13:00.720 --> 00:13:03.230 align:start position:0% I mean if event production is pretty hard<00:13:00.980> and<00:13:01.980> you<00:13:02.279> have<00:13:02.339> all<00:13:02.519> kinds<00:13:02.760> of<00:13:02.760> audio<00:13:02.940> you 00:13:03.230 --> 00:13:03.240 align:start position:0% hard and you have all kinds of audio you 00:13:03.240 --> 00:13:05.290 align:start position:0% hard and you have all kinds of audio you have<00:13:03.360> all<00:13:03.540> kinds<00:13:03.779> of<00:13:03.839> music<00:13:04.019> and<00:13:04.440> sometimes<00:13:04.740> uh 00:13:05.290 --> 00:13:05.300 align:start position:0% have all kinds of music and sometimes uh 00:13:05.300 --> 00:13:08.090 align:start position:0% have all kinds of music and sometimes uh some<00:13:06.300> music<00:13:06.480> segments<00:13:07.380> with<00:13:07.500> copyright<00:13:07.800> can 00:13:08.090 --> 00:13:08.100 align:start position:0% some music segments with copyright can 00:13:08.100 --> 00:13:09.829 align:start position:0% some music segments with copyright can slip<00:13:08.579> into<00:13:08.760> the<00:13:08.940> production 00:13:09.829 --> 00:13:09.839 align:start position:0% slip into the production 00:13:09.839 --> 00:13:11.870 align:start position:0% slip into the production and<00:13:10.320> then<00:13:10.680> your<00:13:10.860> whole<00:13:10.980> stream<00:13:11.220> gets<00:13:11.579> taken 00:13:11.870 --> 00:13:11.880 align:start position:0% and then your whole stream gets taken 00:13:11.880 --> 00:13:12.650 align:start position:0% and then your whole stream gets taken down 00:13:12.650 --> 00:13:12.660 align:start position:0% down 00:13:12.660 --> 00:13:15.470 align:start position:0% down so<00:13:13.320> that's<00:13:13.440> not<00:13:13.680> good<00:13:13.980> so<00:13:14.639> if<00:13:14.760> Barcelona<00:13:15.300> had 00:13:15.470 --> 00:13:15.480 align:start position:0% so that's not good so if Barcelona had 00:13:15.480 --> 00:13:18.110 align:start position:0% so that's not good so if Barcelona had one<00:13:15.660> day<00:13:15.839> without<00:13:16.079> streaming 00:13:18.110 --> 00:13:18.120 align:start position:0% one day without streaming 00:13:18.120 --> 00:13:22.069 align:start position:0% one day without streaming and<00:13:18.660> then<00:13:19.279> a<00:13:20.279> there's<00:13:20.519> another<00:13:20.700> tweet<00:13:21.060> about<00:13:21.240> a 00:13:22.069 --> 00:13:22.079 align:start position:0% and then a there's another tweet about a 00:13:22.079 --> 00:13:24.110 align:start position:0% and then a there's another tweet about a YouTube<00:13:22.440> account<00:13:22.800> that<00:13:23.100> went<00:13:23.399> got<00:13:23.639> taken<00:13:24.000> down 00:13:24.110 --> 00:13:24.120 align:start position:0% YouTube account that went got taken down 00:13:24.120 --> 00:13:26.269 align:start position:0% YouTube account that went got taken down because<00:13:24.959> they<00:13:25.260> were 00:13:26.269 --> 00:13:26.279 align:start position:0% because they were 00:13:26.279 --> 00:13:28.430 align:start position:0% because they were talking<00:13:27.240> about<00:13:27.420> web<00:13:27.839> free<00:13:28.079> content<00:13:28.320> on 00:13:28.430 --> 00:13:28.440 align:start position:0% talking about web free content on 00:13:28.440 --> 00:13:30.949 align:start position:0% talking about web free content on YouTube<00:13:28.620> so<00:13:29.160> yeah<00:13:30.120> there<00:13:30.300> were<00:13:30.420> some<00:13:30.480> disputes 00:13:30.949 --> 00:13:30.959 align:start position:0% YouTube so yeah there were some disputes 00:13:30.959 --> 00:13:33.110 align:start position:0% YouTube so yeah there were some disputes and<00:13:31.200> YouTube<00:13:31.440> kind<00:13:31.920> of<00:13:32.040> banned<00:13:32.459> their<00:13:32.639> their 00:13:33.110 --> 00:13:33.120 align:start position:0% and YouTube kind of banned their their 00:13:33.120 --> 00:13:37.509 align:start position:0% and YouTube kind of banned their their account<00:13:33.360> right<00:13:33.860> so<00:13:34.860> what<00:13:35.519> is<00:13:35.700> the<00:13:35.760> solution 00:13:37.509 --> 00:13:37.519 align:start position:0% account right so what is the solution 00:13:37.519 --> 00:13:39.769 align:start position:0% account right so what is the solution yeah<00:13:38.519> so<00:13:39.060> that's<00:13:39.180> why<00:13:39.300> I'm<00:13:39.420> here<00:13:39.540> talking 00:13:39.769 --> 00:13:39.779 align:start position:0% yeah so that's why I'm here talking 00:13:39.779 --> 00:13:42.650 align:start position:0% yeah so that's why I'm here talking about<00:13:39.899> Streamys<00:13:40.440> no<00:13:40.920> the<00:13:41.339> solution<00:13:41.639> is 00:13:42.650 --> 00:13:42.660 align:start position:0% about Streamys no the solution is 00:13:42.660 --> 00:13:44.990 align:start position:0% about Streamys no the solution is you<00:13:43.019> know<00:13:43.079> having<00:13:43.200> a<00:13:43.440> front<00:13:43.620> end<00:13:43.800> so<00:13:44.700> the<00:13:44.820> first 00:13:44.990 --> 00:13:45.000 align:start position:0% you know having a front end so the first 00:13:45.000 --> 00:13:46.730 align:start position:0% you know having a front end so the first one<00:13:45.180> is<00:13:45.480> the<00:13:45.720> front<00:13:45.839> end<00:13:46.019> right<00:13:46.260> you<00:13:46.500> want<00:13:46.620> to 00:13:46.730 --> 00:13:46.740 align:start position:0% one is the front end right you want to 00:13:46.740 --> 00:13:49.250 align:start position:0% one is the front end right you want to deploy<00:13:46.980> the<00:13:47.160> front<00:13:47.279> end<00:13:47.459> on<00:13:48.060> a<00:13:48.540> decentralized 00:13:49.250 --> 00:13:49.260 align:start position:0% deploy the front end on a decentralized 00:13:49.260 --> 00:13:53.210 align:start position:0% deploy the front end on a decentralized storage<00:13:49.620> layer<00:13:50.040> like<00:13:50.300> ipfs<00:13:51.300> or<00:13:51.959> swarm<00:13:52.500> and 00:13:53.210 --> 00:13:53.220 align:start position:0% storage layer like ipfs or swarm and 00:13:53.220 --> 00:13:54.410 align:start position:0% storage layer like ipfs or swarm and that<00:13:53.339> is<00:13:53.519> actually<00:13:53.579> one<00:13:53.940> of<00:13:54.000> the<00:13:54.060> next<00:13:54.180> steps 00:13:54.410 --> 00:13:54.420 align:start position:0% that is actually one of the next steps 00:13:54.420 --> 00:13:56.870 align:start position:0% that is actually one of the next steps we're<00:13:54.540> going<00:13:54.720> to<00:13:54.779> take<00:13:54.959> after<00:13:55.260> Defcon<00:13:56.040> is<00:13:56.700> to 00:13:56.870 --> 00:13:56.880 align:start position:0% we're going to take after Defcon is to 00:13:56.880 --> 00:13:58.370 align:start position:0% we're going to take after Defcon is to make<00:13:57.000> sure<00:13:57.120> the<00:13:57.360> application<00:13:57.660> is<00:13:57.899> lightweight 00:13:58.370 --> 00:13:58.380 align:start position:0% make sure the application is lightweight 00:13:58.380 --> 00:14:01.190 align:start position:0% make sure the application is lightweight and<00:13:58.860> we<00:13:58.980> can<00:13:59.100> use<00:13:59.279> it<00:13:59.519> and<00:13:59.940> and<00:14:00.180> deploy<00:14:00.540> it<00:14:00.720> in 00:14:01.190 --> 00:14:01.200 align:start position:0% and we can use it and and deploy it in 00:14:01.200 --> 00:14:04.009 align:start position:0% and we can use it and and deploy it in in<00:14:01.680> one<00:14:01.920> of<00:14:02.040> these<00:14:02.279> two<00:14:02.700> layers 00:14:04.009 --> 00:14:04.019 align:start position:0% in one of these two layers 00:14:04.019 --> 00:14:05.750 align:start position:0% in one of these two layers and<00:14:04.500> the<00:14:04.680> second<00:14:04.800> solution<00:14:05.160> to<00:14:05.459> the<00:14:05.579> problem 00:14:05.750 --> 00:14:05.760 align:start position:0% and the second solution to the problem 00:14:05.760 --> 00:14:09.410 align:start position:0% and the second solution to the problem is<00:14:06.240> using<00:14:06.660> decentralized<00:14:07.700> and<00:14:08.700> with<00:14:09.180> the 00:14:09.410 --> 00:14:09.420 align:start position:0% is using decentralized and with the 00:14:09.420 --> 00:14:12.829 align:start position:0% is using decentralized and with the providers<00:14:09.779> like<00:14:10.440> life<00:14:10.740> here<00:14:11.300> since<00:14:12.300> life<00:14:12.540> here 00:14:12.829 --> 00:14:12.839 align:start position:0% providers like life here since life here 00:14:12.839 --> 00:14:16.670 align:start position:0% providers like life here since life here is<00:14:13.079> a<00:14:13.800> decentralized<00:14:14.399> layer<00:14:14.940> of<00:14:15.060> note<00:14:15.300> and<00:14:16.079> the 00:14:16.670 --> 00:14:16.680 align:start position:0% is a decentralized layer of note and the 00:14:16.680 --> 00:14:18.710 align:start position:0% is a decentralized layer of note and the content<00:14:16.920> cannot<00:14:17.220> be<00:14:17.339> really<00:14:17.519> stopped<00:14:18.360> even<00:14:18.540> if 00:14:18.710 --> 00:14:18.720 align:start position:0% content cannot be really stopped even if 00:14:18.720 --> 00:14:20.629 align:start position:0% content cannot be really stopped even if the<00:14:18.839> government<00:14:19.019> or<00:14:19.500> the<00:14:19.620> platform<00:14:20.040> any 00:14:20.629 --> 00:14:20.639 align:start position:0% the government or the platform any 00:14:20.639 --> 00:14:23.870 align:start position:0% the government or the platform any platform<00:14:21.120> says<00:14:21.720> so<00:14:21.959> right<00:14:22.320> the<00:14:23.040> next<00:14:23.279> problem 00:14:23.870 --> 00:14:23.880 align:start position:0% platform says so right the next problem 00:14:23.880 --> 00:14:27.530 align:start position:0% platform says so right the next problem that<00:14:24.360> arises<00:14:25.139> from<00:14:25.500> using 00:14:27.530 --> 00:14:27.540 align:start position:0% that arises from using 00:14:27.540 --> 00:14:29.269 align:start position:0% that arises from using um centralized<00:14:28.260> providers<00:14:28.620> is<00:14:29.040> the 00:14:29.269 --> 00:14:29.279 align:start position:0% um centralized providers is the 00:14:29.279 --> 00:14:31.069 align:start position:0% um centralized providers is the intellectual<00:14:29.760> property<00:14:30.120> this<00:14:30.720> is<00:14:30.899> kind<00:14:31.019> of 00:14:31.069 --> 00:14:31.079 align:start position:0% intellectual property this is kind of 00:14:31.079 --> 00:14:33.310 align:start position:0% intellectual property this is kind of tied<00:14:31.260> to<00:14:31.380> the<00:14:31.500> censorship<00:14:31.860> prone<00:14:32.160> issue 00:14:33.310 --> 00:14:33.320 align:start position:0% tied to the censorship prone issue 00:14:33.320 --> 00:14:36.230 align:start position:0% tied to the censorship prone issue and<00:14:34.320> so<00:14:34.680> like<00:14:34.860> we<00:14:34.980> said<00:14:35.100> copyright<00:14:35.459> Claims<00:14:35.880> can 00:14:36.230 --> 00:14:36.240 align:start position:0% and so like we said copyright Claims can 00:14:36.240 --> 00:14:38.150 align:start position:0% and so like we said copyright Claims can result<00:14:36.420> in<00:14:36.720> streams<00:14:37.079> being<00:14:37.200> taken<00:14:37.560> down 00:14:38.150 --> 00:14:38.160 align:start position:0% result in streams being taken down 00:14:38.160 --> 00:14:40.550 align:start position:0% result in streams being taken down tennis<00:14:38.700> being<00:14:39.000> banned<00:14:39.720> and<00:14:40.199> users<00:14:40.440> being 00:14:40.550 --> 00:14:40.560 align:start position:0% tennis being banned and users being 00:14:40.560 --> 00:14:43.250 align:start position:0% tennis being banned and users being demonetized<00:14:41.300> within<00:14:42.300> Wonder 00:14:43.250 --> 00:14:43.260 align:start position:0% demonetized within Wonder 00:14:43.260 --> 00:14:45.590 align:start position:0% demonetized within Wonder and<00:14:44.100> also 00:14:45.590 --> 00:14:45.600 align:start position:0% and also 00:14:45.600 --> 00:14:47.030 align:start position:0% and also it's<00:14:46.019> not<00:14:46.139> only<00:14:46.260> that<00:14:46.500> they're<00:14:46.620> taking<00:14:46.740> down 00:14:47.030 --> 00:14:47.040 align:start position:0% it's not only that they're taking down 00:14:47.040 --> 00:14:49.730 align:start position:0% it's not only that they're taking down the<00:14:47.160> streams<00:14:47.519> but<00:14:48.260> is<00:14:49.260> the<00:14:49.500> lack<00:14:49.680> of 00:14:49.730 --> 00:14:49.740 align:start position:0% the streams but is the lack of 00:14:49.740 --> 00:14:52.730 align:start position:0% the streams but is the lack of transparency<00:14:50.279> in<00:14:50.880> their<00:14:51.420> process<00:14:51.779> to<00:14:52.139> decide 00:14:52.730 --> 00:14:52.740 align:start position:0% transparency in their process to decide 00:14:52.740 --> 00:14:54.769 align:start position:0% transparency in their process to decide which<00:14:53.100> streams<00:14:53.519> get<00:14:53.760> taken<00:14:54.060> down<00:14:54.300> and<00:14:54.600> which 00:14:54.769 --> 00:14:54.779 align:start position:0% which streams get taken down and which 00:14:54.779 --> 00:14:57.050 align:start position:0% which streams get taken down and which content<00:14:55.139> is<00:14:55.320> being<00:14:55.500> shown<00:14:55.740> or<00:14:56.040> not<00:14:56.160> right<00:14:56.339> so 00:14:57.050 --> 00:14:57.060 align:start position:0% content is being shown or not right so 00:14:57.060 --> 00:14:58.430 align:start position:0% content is being shown or not right so there's<00:14:57.240> really<00:14:57.420> an<00:14:57.660> ethical<00:14:57.959> discussion 00:14:58.430 --> 00:14:58.440 align:start position:0% there's really an ethical discussion 00:14:58.440 --> 00:14:59.329 align:start position:0% there's really an ethical discussion around 00:14:59.329 --> 00:14:59.339 align:start position:0% around 00:14:59.339 --> 00:15:03.050 align:start position:0% around what<00:14:59.880> content<00:15:00.779> are<00:15:01.380> we<00:15:01.500> being 00:15:03.050 --> 00:15:03.060 align:start position:0% what content are we being 00:15:03.060 --> 00:15:07.069 align:start position:0% what content are we being allowed<00:15:03.660> to<00:15:03.779> see<00:15:04.079> right<00:15:04.980> so 00:15:07.069 --> 00:15:07.079 align:start position:0% allowed to see right so 00:15:07.079 --> 00:15:10.009 align:start position:0% allowed to see right so using<00:15:07.920> decentralized<00:15:08.639> Services<00:15:08.940> we<00:15:09.899> then 00:15:10.009 --> 00:15:10.019 align:start position:0% using decentralized Services we then 00:15:10.019 --> 00:15:10.910 align:start position:0% using decentralized Services we then really<00:15:10.199> solve<00:15:10.500> this<00:15:10.560> content<00:15:10.800> because 00:15:10.910 --> 00:15:10.920 align:start position:0% really solve this content because 00:15:10.920 --> 00:15:12.769 align:start position:0% really solve this content because there's<00:15:11.160> no<00:15:11.339> moderation<00:15:11.760> right<00:15:12.060> but<00:15:12.540> I<00:15:12.660> think 00:15:12.769 --> 00:15:12.779 align:start position:0% there's no moderation right but I think 00:15:12.779 --> 00:15:14.389 align:start position:0% there's no moderation right but I think we're<00:15:12.839> heading<00:15:13.139> in<00:15:13.260> the<00:15:13.380> right<00:15:13.500> direction 00:15:14.389 --> 00:15:14.399 align:start position:0% we're heading in the right direction 00:15:14.399 --> 00:15:17.389 align:start position:0% we're heading in the right direction in<00:15:15.120> regards<00:15:15.720> to<00:15:15.839> not<00:15:16.380> allowing<00:15:16.740> this<00:15:17.040> one 00:15:17.389 --> 00:15:17.399 align:start position:0% in regards to not allowing this one 00:15:17.399 --> 00:15:20.449 align:start position:0% in regards to not allowing this one Central<00:15:18.180> entity<00:15:19.079> to<00:15:19.440> decide<00:15:19.740> what<00:15:20.040> we<00:15:20.220> can<00:15:20.339> see 00:15:20.449 --> 00:15:20.459 align:start position:0% Central entity to decide what we can see 00:15:20.459 --> 00:15:23.269 align:start position:0% Central entity to decide what we can see or<00:15:20.760> what<00:15:21.060> we<00:15:21.240> can't<00:15:21.360> see<00:15:21.660> right<00:15:21.959> next<00:15:22.860> will<00:15:23.100> be 00:15:23.269 --> 00:15:23.279 align:start position:0% or what we can't see right next will be 00:15:23.279 --> 00:15:25.310 align:start position:0% or what we can't see right next will be the<00:15:23.459> high<00:15:23.579> fee<00:15:23.940> to<00:15:24.060> connect<00:15:24.180> creators<00:15:24.720> and 00:15:25.310 --> 00:15:25.320 align:start position:0% the high fee to connect creators and 00:15:25.320 --> 00:15:27.590 align:start position:0% the high fee to connect creators and this<00:15:25.440> is<00:15:25.560> also<00:15:25.740> very<00:15:25.980> interesting<00:15:26.600> especially 00:15:27.590 --> 00:15:27.600 align:start position:0% this is also very interesting especially 00:15:27.600 --> 00:15:29.810 align:start position:0% this is also very interesting especially recently<00:15:28.079> a<00:15:28.620> twitch 00:15:29.810 --> 00:15:29.820 align:start position:0% recently a twitch 00:15:29.820 --> 00:15:32.509 align:start position:0% recently a twitch I<00:15:30.120> think<00:15:30.240> increased<00:15:30.720> their<00:15:31.019> uh<00:15:31.560> this<00:15:32.339> year 00:15:32.509 --> 00:15:32.519 align:start position:0% I think increased their uh this year 00:15:32.519 --> 00:15:34.490 align:start position:0% I think increased their uh this year they're<00:15:33.000> taking<00:15:33.180> from<00:15:33.540> from<00:15:33.959> content 00:15:34.490 --> 00:15:34.500 align:start position:0% they're taking from from content 00:15:34.500 --> 00:15:36.829 align:start position:0% they're taking from from content creators<00:15:34.800> from<00:15:35.100> I<00:15:35.760> think<00:15:35.880> it<00:15:36.000> was<00:15:36.060> 15<00:15:36.300> to<00:15:36.600> 30 00:15:36.829 --> 00:15:36.839 align:start position:0% creators from I think it was 15 to 30 00:15:36.839 --> 00:15:39.170 align:start position:0% creators from I think it was 15 to 30 percent<00:15:37.139> or<00:15:37.860> something<00:15:38.040> like<00:15:38.279> this<00:15:38.459> because 00:15:39.170 --> 00:15:39.180 align:start position:0% percent or something like this because 00:15:39.180 --> 00:15:41.329 align:start position:0% percent or something like this because these<00:15:39.600> centralized<00:15:40.079> providers 00:15:41.329 --> 00:15:41.339 align:start position:0% these centralized providers 00:15:41.339 --> 00:15:43.910 align:start position:0% these centralized providers actually<00:15:41.880> super<00:15:42.360> expensive<00:15:42.899> to<00:15:43.380> run<00:15:43.560> right<00:15:43.800> so 00:15:43.910 --> 00:15:43.920 align:start position:0% actually super expensive to run right so 00:15:43.920 --> 00:15:45.949 align:start position:0% actually super expensive to run right so tweet<00:15:44.399> is<00:15:44.579> even<00:15:44.880> though<00:15:45.060> the<00:15:45.300> free<00:15:45.420> is<00:15:45.660> the 00:15:45.949 --> 00:15:45.959 align:start position:0% tweet is even though the free is the 00:15:45.959 --> 00:15:48.769 align:start position:0% tweet is even though the free is the content<00:15:46.260> is<00:15:46.380> free<00:15:46.699> it's<00:15:47.699> Mega<00:15:48.000> expensive<00:15:48.480> to 00:15:48.769 --> 00:15:48.779 align:start position:0% content is free it's Mega expensive to 00:15:48.779 --> 00:15:51.650 align:start position:0% content is free it's Mega expensive to run<00:15:48.959> an<00:15:49.199> operation<00:15:49.560> like<00:15:49.800> twitch<00:15:50.360> so<00:15:51.360> in<00:15:51.540> the 00:15:51.650 --> 00:15:51.660 align:start position:0% run an operation like twitch so in the 00:15:51.660 --> 00:15:53.569 align:start position:0% run an operation like twitch so in the long<00:15:51.779> term<00:15:51.899> they<00:15:52.800> are<00:15:52.980> they<00:15:53.339> have<00:15:53.459> two 00:15:53.569 --> 00:15:53.579 align:start position:0% long term they are they have two 00:15:53.579 --> 00:15:55.250 align:start position:0% long term they are they have two solutions<00:15:53.880> and<00:15:54.480> one<00:15:54.660> solution<00:15:54.899> is<00:15:55.139> to 00:15:55.250 --> 00:15:55.260 align:start position:0% solutions and one solution is to 00:15:55.260 --> 00:15:58.030 align:start position:0% solutions and one solution is to increase<00:15:55.440> the<00:15:56.339> share<00:15:56.699> they<00:15:56.880> take<00:15:57.060> him<00:15:57.240> from 00:15:58.030 --> 00:15:58.040 align:start position:0% increase the share they take him from 00:15:58.040 --> 00:16:00.949 align:start position:0% increase the share they take him from the<00:15:59.040> creators<00:15:59.399> the<00:15:59.579> other<00:15:59.760> solution<00:16:00.120> is 00:16:00.949 --> 00:16:00.959 align:start position:0% the creators the other solution is 00:16:00.959 --> 00:16:04.370 align:start position:0% the creators the other solution is uh<00:16:01.740> to<00:16:02.040> display<00:16:02.160> ads<00:16:02.760> right<00:16:03.060> so<00:16:03.720> yeah<00:16:03.899> moving 00:16:04.370 --> 00:16:04.380 align:start position:0% uh to display ads right so yeah moving 00:16:04.380 --> 00:16:05.810 align:start position:0% uh to display ads right so yeah moving on<00:16:04.560> to<00:16:04.800> a<00:16:04.920> decentralized<00:16:05.399> solution<00:16:05.639> like 00:16:05.810 --> 00:16:05.820 align:start position:0% on to a decentralized solution like 00:16:05.820 --> 00:16:09.290 align:start position:0% on to a decentralized solution like streamies<00:16:06.240> and<00:16:07.560> also<00:16:08.100> live<00:16:08.279> here<00:16:08.880> will 00:16:09.290 --> 00:16:09.300 align:start position:0% streamies and also live here will 00:16:09.300 --> 00:16:11.629 align:start position:0% streamies and also live here will basically<00:16:09.660> allow<00:16:10.079> us<00:16:10.199> to 00:16:11.629 --> 00:16:11.639 align:start position:0% basically allow us to 00:16:11.639 --> 00:16:13.129 align:start position:0% basically allow us to give<00:16:12.120> back 00:16:13.129 --> 00:16:13.139 align:start position:0% give back 00:16:13.139 --> 00:16:16.370 align:start position:0% give back the<00:16:14.100> monetization<00:16:14.820> is<00:16:15.420> a<00:16:15.720> power<00:16:16.019> to<00:16:16.260> the 00:16:16.370 --> 00:16:16.380 align:start position:0% the monetization is a power to the 00:16:16.380 --> 00:16:19.129 align:start position:0% the monetization is a power to the content<00:16:16.740> creator<00:16:17.519> and<00:16:18.060> because<00:16:18.360> then<00:16:18.839> if 00:16:19.129 --> 00:16:19.139 align:start position:0% content creator and because then if 00:16:19.139 --> 00:16:20.389 align:start position:0% content creator and because then if according<00:16:19.560> to<00:16:19.620> create<00:16:19.740> is<00:16:19.860> using<00:16:20.100> live<00:16:20.220> here 00:16:20.389 --> 00:16:20.399 align:start position:0% according to create is using live here 00:16:20.399 --> 00:16:22.430 align:start position:0% according to create is using live here to<00:16:20.579> distribute<00:16:20.940> the<00:16:21.060> content<00:16:21.360> the<00:16:21.959> content<00:16:22.320> is 00:16:22.430 --> 00:16:22.440 align:start position:0% to distribute the content the content is 00:16:22.440 --> 00:16:25.670 align:start position:0% to distribute the content the content is actually<00:16:22.620> theirs<00:16:23.220> right<00:16:23.519> so<00:16:24.420> he<00:16:24.600> is<00:16:24.839> then 00:16:25.670 --> 00:16:25.680 align:start position:0% actually theirs right so he is then 00:16:25.680 --> 00:16:28.250 align:start position:0% actually theirs right so he is then able<00:16:26.579> to<00:16:26.699> decide<00:16:27.060> how<00:16:27.420> he<00:16:27.540> monetizes<00:16:28.079> the 00:16:28.250 --> 00:16:28.260 align:start position:0% able to decide how he monetizes the 00:16:28.260 --> 00:16:31.610 align:start position:0% able to decide how he monetizes the content<00:16:29.459> also<00:16:30.300> building<00:16:30.899> on<00:16:31.260> top<00:16:31.380> of<00:16:31.500> the 00:16:31.610 --> 00:16:31.620 align:start position:0% content also building on top of the 00:16:31.620 --> 00:16:33.590 align:start position:0% content also building on top of the plugin<00:16:32.040> system<00:16:32.220> that<00:16:32.519> we<00:16:32.699> that<00:16:33.000> I<00:16:33.360> was<00:16:33.480> talking 00:16:33.590 --> 00:16:33.600 align:start position:0% plugin system that we that I was talking 00:16:33.600 --> 00:16:35.689 align:start position:0% plugin system that we that I was talking about<00:16:33.779> earlier 00:16:35.689 --> 00:16:35.699 align:start position:0% about earlier 00:16:35.699 --> 00:16:37.490 align:start position:0% about earlier uh<00:16:36.240> we're<00:16:36.480> releasing<00:16:36.779> setting<00:16:37.259> up<00:16:37.380> this 00:16:37.490 --> 00:16:37.500 align:start position:0% uh we're releasing setting up this 00:16:37.500 --> 00:16:39.530 align:start position:0% uh we're releasing setting up this ecosystem<00:16:37.920> for<00:16:38.339> developers<00:16:38.759> to<00:16:38.880> come<00:16:39.060> in<00:16:39.240> and 00:16:39.530 --> 00:16:39.540 align:start position:0% ecosystem for developers to come in and 00:16:39.540 --> 00:16:41.269 align:start position:0% ecosystem for developers to come in and build<00:16:39.720> custom<00:16:40.139> Solutions<00:16:40.620> on<00:16:41.040> top<00:16:41.160> of 00:16:41.269 --> 00:16:41.279 align:start position:0% build custom Solutions on top of 00:16:41.279 --> 00:16:43.850 align:start position:0% build custom Solutions on top of Streamys<00:16:41.759> that<00:16:42.300> they<00:16:42.480> can<00:16:42.600> use<00:16:42.779> to 00:16:43.850 --> 00:16:43.860 align:start position:0% Streamys that they can use to 00:16:43.860 --> 00:16:45.829 align:start position:0% Streamys that they can use to to<00:16:44.160> you<00:16:44.399> know 00:16:45.829 --> 00:16:45.839 align:start position:0% to you know 00:16:45.839 --> 00:16:48.530 align:start position:0% to you know monetize<00:16:46.620> their<00:16:46.980> content<00:16:47.279> so<00:16:47.639> radical<00:16:48.120> drips 00:16:48.530 --> 00:16:48.540 align:start position:0% monetize their content so radical drips 00:16:48.540 --> 00:16:50.329 align:start position:0% monetize their content so radical drips will<00:16:49.079> be<00:16:49.199> a<00:16:49.320> good<00:16:49.440> example 00:16:50.329 --> 00:16:50.339 align:start position:0% will be a good example 00:16:50.339 --> 00:16:51.530 align:start position:0% will be a good example but 00:16:51.530 --> 00:16:51.540 align:start position:0% but 00:16:51.540 --> 00:16:52.970 align:start position:0% but you<00:16:51.779> know<00:16:51.839> this<00:16:51.959> is<00:16:52.079> web<00:16:52.199> free<00:16:52.440> the<00:16:52.680> best<00:16:52.860> thing 00:16:52.970 --> 00:16:52.980 align:start position:0% you know this is web free the best thing 00:16:52.980 --> 00:16:56.870 align:start position:0% you know this is web free the best thing we<00:16:53.160> do<00:16:53.279> is<00:16:53.699> create<00:16:54.920> monitoration<00:16:55.920> a<00:16:56.639> route 00:16:56.870 --> 00:16:56.880 align:start position:0% we do is create monitoration a route 00:16:56.880 --> 00:17:00.110 align:start position:0% we do is create monitoration a route that<00:16:57.420> this<00:16:58.019> is<00:16:58.199> web3<00:16:58.560> crypto<00:16:59.160> we're<00:16:59.759> good<00:16:59.940> at 00:17:00.110 --> 00:17:00.120 align:start position:0% that this is web3 crypto we're good at 00:17:00.120 --> 00:17:02.329 align:start position:0% that this is web3 crypto we're good at monetizing<00:17:00.779> without<00:17:01.440> having<00:17:01.800> someone<00:17:02.040> in<00:17:02.279> the 00:17:02.329 --> 00:17:02.339 align:start position:0% monetizing without having someone in the 00:17:02.339 --> 00:17:06.470 align:start position:0% monetizing without having someone in the middle<00:17:02.459> taking<00:17:02.699> a<00:17:03.000> share<00:17:03.300> of<00:17:03.480> a<00:17:04.500> our<00:17:05.339> money<00:17:06.000> so 00:17:06.470 --> 00:17:06.480 align:start position:0% middle taking a share of a our money so 00:17:06.480 --> 00:17:09.010 align:start position:0% middle taking a share of a our money so you<00:17:07.079> guys<00:17:07.199> can<00:17:07.500> figure<00:17:07.740> out<00:17:07.860> the<00:17:08.040> rest 00:17:09.010 --> 00:17:09.020 align:start position:0% you guys can figure out the rest 00:17:09.020 --> 00:17:12.530 align:start position:0% you guys can figure out the rest uh<00:17:10.020> just<00:17:10.559> build<00:17:10.799> a<00:17:11.100> custom<00:17:11.280> plugin<00:17:11.819> that<00:17:12.299> sends 00:17:12.530 --> 00:17:12.540 align:start position:0% uh just build a custom plugin that sends 00:17:12.540 --> 00:17:14.809 align:start position:0% uh just build a custom plugin that sends money<00:17:12.720> to<00:17:12.900> one<00:17:13.020> address<00:17:13.140> or<00:17:13.500> the<00:17:13.620> other<00:17:14.040> and<00:17:14.640> we 00:17:14.809 --> 00:17:14.819 align:start position:0% money to one address or the other and we 00:17:14.819 --> 00:17:17.990 align:start position:0% money to one address or the other and we should<00:17:14.939> be<00:17:15.059> solving<00:17:15.480> this<00:17:15.600> issue 00:17:17.990 --> 00:17:18.000 align:start position:0% 00:17:18.000 --> 00:17:20.030 align:start position:0% and<00:17:18.480> finally<00:17:18.780> and<00:17:19.140> that's<00:17:19.319> for<00:17:19.559> me<00:17:19.679> this<00:17:19.919> is 00:17:20.030 --> 00:17:20.040 align:start position:0% and finally and that's for me this is 00:17:20.040 --> 00:17:22.309 align:start position:0% and finally and that's for me this is the<00:17:20.160> most<00:17:20.280> important<00:17:20.699> one<00:17:20.880> the<00:17:21.720> web<00:17:22.079> free 00:17:22.309 --> 00:17:22.319 align:start position:0% the most important one the web free 00:17:22.319 --> 00:17:25.909 align:start position:0% the most important one the web free ecosystem<00:17:23.280> and<00:17:24.120> how<00:17:24.360> to<00:17:24.720> Twitch<00:17:25.260> YouTube<00:17:25.559> and 00:17:25.909 --> 00:17:25.919 align:start position:0% ecosystem and how to Twitch YouTube and 00:17:25.919 --> 00:17:29.289 align:start position:0% ecosystem and how to Twitch YouTube and others<00:17:26.339> under<00:17:26.579> really<00:17:27.000> respecting 00:17:29.289 --> 00:17:29.299 align:start position:0% others under really respecting 00:17:29.299 --> 00:17:32.030 align:start position:0% others under really respecting the<00:17:30.299> values<00:17:30.900> that<00:17:31.140> we<00:17:31.260> stand<00:17:31.559> for<00:17:31.799> right 00:17:32.030 --> 00:17:32.040 align:start position:0% the values that we stand for right 00:17:32.040 --> 00:17:34.310 align:start position:0% the values that we stand for right especially<00:17:32.700> the<00:17:33.059> open<00:17:33.179> source 00:17:34.310 --> 00:17:34.320 align:start position:0% especially the open source 00:17:34.320 --> 00:17:36.490 align:start position:0% especially the open source and<00:17:35.039> their<00:17:35.400> communities<00:17:35.760> they<00:17:36.179> build 00:17:36.490 --> 00:17:36.500 align:start position:0% and their communities they build 00:17:36.500 --> 00:17:38.570 align:start position:0% and their communities they build Solutions<00:17:37.500> sometimes<00:17:38.039> and<00:17:38.220> they're<00:17:38.400> trying 00:17:38.570 --> 00:17:38.580 align:start position:0% Solutions sometimes and they're trying 00:17:38.580 --> 00:17:41.630 align:start position:0% Solutions sometimes and they're trying to<00:17:38.640> get<00:17:38.760> into<00:17:38.940> into<00:17:39.240> web<00:17:39.539> 3<00:17:39.780> but 00:17:41.630 --> 00:17:41.640 align:start position:0% to get into into web 3 but 00:17:41.640 --> 00:17:43.730 align:start position:0% to get into into web 3 but they're<00:17:42.179> not<00:17:42.360> actually<00:17:42.600> thinking<00:17:43.380> about<00:17:43.500> the 00:17:43.730 --> 00:17:43.740 align:start position:0% they're not actually thinking about the 00:17:43.740 --> 00:17:45.409 align:start position:0% they're not actually thinking about the community<00:17:43.919> they're<00:17:44.520> not<00:17:44.700> making<00:17:44.940> this<00:17:45.240> code 00:17:45.409 --> 00:17:45.419 align:start position:0% community they're not making this code 00:17:45.419 --> 00:17:48.110 align:start position:0% community they're not making this code public<00:17:45.780> they're<00:17:46.260> not<00:17:46.440> contributing<00:17:46.980> back<00:17:47.160> to 00:17:48.110 --> 00:17:48.120 align:start position:0% public they're not contributing back to 00:17:48.120 --> 00:17:50.390 align:start position:0% public they're not contributing back to the<00:17:48.539> protocols<00:17:49.080> they<00:17:49.140> use<00:17:49.320> right 00:17:50.390 --> 00:17:50.400 align:start position:0% the protocols they use right 00:17:50.400 --> 00:17:52.730 align:start position:0% the protocols they use right they're<00:17:51.179> not<00:17:51.299> part<00:17:51.480> of<00:17:51.600> our<00:17:51.720> community 00:17:52.730 --> 00:17:52.740 align:start position:0% they're not part of our community 00:17:52.740 --> 00:17:54.950 align:start position:0% they're not part of our community and 00:17:54.950 --> 00:17:54.960 align:start position:0% and 00:17:54.960 --> 00:17:59.090 align:start position:0% and yeah<00:17:55.320> I<00:17:55.500> think<00:17:55.880> we<00:17:56.880> stream<00:17:57.299> it<00:17:57.539> is<00:17:57.720> actually 00:17:59.090 --> 00:17:59.100 align:start position:0% yeah I think we stream it is actually 00:17:59.100 --> 00:18:01.370 align:start position:0% yeah I think we stream it is actually existing<00:17:59.820> because<00:18:00.059> we<00:18:00.539> believe<00:18:00.720> in<00:18:01.140> these 00:18:01.370 --> 00:18:01.380 align:start position:0% existing because we believe in these 00:18:01.380 --> 00:18:04.310 align:start position:0% existing because we believe in these ideas<00:18:01.580> and<00:18:02.580> it's<00:18:03.240> coming<00:18:03.480> out<00:18:03.720> of<00:18:03.900> a<00:18:04.080> community 00:18:04.310 --> 00:18:04.320 align:start position:0% ideas and it's coming out of a community 00:18:04.320 --> 00:18:07.970 align:start position:0% ideas and it's coming out of a community effort<00:18:04.919> between<00:18:05.520> the<00:18:05.880> EF<00:18:06.240> life<00:18:06.960> here 00:18:07.970 --> 00:18:07.980 align:start position:0% effort between the EF life here 00:18:07.980 --> 00:18:10.630 align:start position:0% effort between the EF life here and<00:18:08.460> me<00:18:08.640> and<00:18:08.820> others<00:18:09.120> the<00:18:09.179> other<00:18:09.480> developers 00:18:10.630 --> 00:18:10.640 align:start position:0% and me and others the other developers 00:18:10.640 --> 00:18:14.230 align:start position:0% and me and others the other developers to<00:18:11.640> embrace<00:18:12.059> these<00:18:12.960> ideas<00:18:13.080> right 00:18:14.230 --> 00:18:14.240 align:start position:0% to embrace these ideas right 00:18:14.240 --> 00:18:16.250 align:start position:0% to embrace these ideas right and<00:18:15.240> and 00:18:16.250 --> 00:18:16.260 align:start position:0% and and 00:18:16.260 --> 00:18:18.049 align:start position:0% and and trying<00:18:16.679> to<00:18:16.919> help<00:18:17.039> like<00:18:17.400> I<00:18:17.460> said<00:18:17.700> communities 00:18:18.049 --> 00:18:18.059 align:start position:0% trying to help like I said communities 00:18:18.059 --> 00:18:20.750 align:start position:0% trying to help like I said communities decouple<00:18:18.840> from<00:18:19.020> these<00:18:19.500> providers<00:18:20.280> and 00:18:20.750 --> 00:18:20.760 align:start position:0% decouple from these providers and 00:18:20.760 --> 00:18:22.730 align:start position:0% decouple from these providers and finally<00:18:21.059> oh<00:18:21.780> no<00:18:22.020> no<00:18:22.080> the<00:18:22.440> most<00:18:22.559> important 00:18:22.730 --> 00:18:22.740 align:start position:0% finally oh no no the most important 00:18:22.740 --> 00:18:23.830 align:start position:0% finally oh no no the most important Slide 00:18:23.830 --> 00:18:23.840 align:start position:0% Slide 00:18:23.840 --> 00:18:26.810 align:start position:0% Slide the<00:18:24.840> members<00:18:25.020> of<00:18:25.140> the<00:18:25.260> team<00:18:25.440> and<00:18:26.400> I<00:18:26.520> want<00:18:26.640> to 00:18:26.810 --> 00:18:26.820 align:start position:0% the members of the team and I want to 00:18:26.820 --> 00:18:29.510 align:start position:0% the members of the team and I want to run<00:18:26.940> off<00:18:27.179> Applause<00:18:27.539> after<00:18:28.140> I<00:18:28.440> say<00:18:28.620> all<00:18:29.160> of<00:18:29.340> the 00:18:29.510 --> 00:18:29.520 align:start position:0% run off Applause after I say all of the 00:18:29.520 --> 00:18:30.289 align:start position:0% run off Applause after I say all of the names 00:18:30.289 --> 00:18:30.299 align:start position:0% names 00:18:30.299 --> 00:18:32.810 align:start position:0% names so<00:18:31.380> um<00:18:31.380> first<00:18:31.799> we<00:18:32.100> have 00:18:32.810 --> 00:18:32.820 align:start position:0% so um first we have 00:18:32.820 --> 00:18:36.049 align:start position:0% so um first we have hands<00:18:33.539> which<00:18:34.080> is<00:18:34.260> the<00:18:34.679> guy<00:18:34.980> that<00:18:35.100> developed 00:18:36.049 --> 00:18:36.059 align:start position:0% hands which is the guy that developed 00:18:36.059 --> 00:18:37.669 align:start position:0% hands which is the guy that developed quite<00:18:36.480> a<00:18:36.600> big<00:18:36.720> chunk<00:18:36.840> of<00:18:37.080> the<00:18:37.200> code<00:18:37.320> he's 00:18:37.669 --> 00:18:37.679 align:start position:0% quite a big chunk of the code he's 00:18:37.679 --> 00:18:39.350 align:start position:0% quite a big chunk of the code he's sitting<00:18:38.039> there<00:18:38.100> in<00:18:38.280> the<00:18:38.400> audience 00:18:39.350 --> 00:18:39.360 align:start position:0% sitting there in the audience 00:18:39.360 --> 00:18:42.529 align:start position:0% sitting there in the audience Applause 00:18:42.529 --> 00:18:42.539 align:start position:0% 00:18:42.539 --> 00:18:45.289 align:start position:0% yes 00:18:45.289 --> 00:18:45.299 align:start position:0% 00:18:45.299 --> 00:18:47.930 align:start position:0% then<00:18:45.720> we<00:18:45.900> have<00:18:45.960> Wesley<00:18:46.440> efer<00:18:47.340> he's<00:18:47.520> in<00:18:47.760> there 00:18:47.930 --> 00:18:47.940 align:start position:0% then we have Wesley efer he's in there 00:18:47.940 --> 00:18:49.730 align:start position:0% then we have Wesley efer he's in there oh 00:18:49.730 --> 00:18:49.740 align:start position:0% oh 00:18:49.740 --> 00:18:51.830 align:start position:0% oh I<00:18:50.160> don't<00:18:50.280> know<00:18:50.400> if<00:18:50.520> Akio<00:18:50.880> is<00:18:51.120> here<00:18:51.299> I<00:18:51.720> don't 00:18:51.830 --> 00:18:51.840 align:start position:0% I don't know if Akio is here I don't 00:18:51.840 --> 00:18:53.150 align:start position:0% I don't know if Akio is here I don't think<00:18:51.960> so<00:18:52.080> he's<00:18:52.440> watching<00:18:52.740> me<00:18:52.860> on<00:18:52.980> the<00:18:53.100> stream 00:18:53.150 --> 00:18:53.160 align:start position:0% think so he's watching me on the stream 00:18:53.160 --> 00:18:57.110 align:start position:0% think so he's watching me on the stream Akio<00:18:53.880> what's<00:18:54.360> up<00:18:54.480> he's<00:18:55.020> the<00:18:55.260> designer 00:18:57.110 --> 00:18:57.120 align:start position:0% Akio what's up he's the designer 00:18:57.120 --> 00:18:58.850 align:start position:0% Akio what's up he's the designer and<00:18:57.539> then<00:18:57.660> I'm<00:18:57.840> there<00:18:58.020> with<00:18:58.140> the<00:18:58.260> pen<00:18:58.440> that<00:18:58.679> I 00:18:58.850 --> 00:18:58.860 align:start position:0% and then I'm there with the pen that I 00:18:58.860 --> 00:19:01.370 align:start position:0% and then I'm there with the pen that I set<00:18:59.039> for<00:18:59.160> the<00:18:59.340> merch<00:18:59.640> it's<00:19:00.480> my<00:19:00.780> pfp<00:19:01.140> for<00:19:01.260> the 00:19:01.370 --> 00:19:01.380 align:start position:0% set for the merch it's my pfp for the 00:19:01.380 --> 00:19:03.770 align:start position:0% set for the merch it's my pfp for the Emergency<00:19:01.500> I<00:19:02.160> didn't<00:19:02.280> change<00:19:02.520> it<00:19:02.640> so<00:19:02.820> yeah<00:19:03.480> the 00:19:03.770 --> 00:19:03.780 align:start position:0% Emergency I didn't change it so yeah the 00:19:03.780 --> 00:19:05.330 align:start position:0% Emergency I didn't change it so yeah the panda<00:19:04.080> and<00:19:04.440> that's<00:19:04.559> me 00:19:05.330 --> 00:19:05.340 align:start position:0% panda and that's me 00:19:05.340 --> 00:19:09.250 align:start position:0% panda and that's me and<00:19:05.520> you<00:19:05.700> don't<00:19:05.820> have<00:19:05.940> to<00:19:06.059> clap<00:19:06.299> yeah 00:19:09.250 --> 00:19:09.260 align:start position:0% 00:19:09.260 --> 00:19:11.150 align:start position:0% so<00:19:10.260> yeah<00:19:10.380> it<00:19:10.500> was<00:19:10.620> awesome<00:19:10.740> working<00:19:11.039> with 00:19:11.150 --> 00:19:11.160 align:start position:0% so yeah it was awesome working with 00:19:11.160 --> 00:19:12.770 align:start position:0% so yeah it was awesome working with these<00:19:11.400> guys 00:19:12.770 --> 00:19:12.780 align:start position:0% these guys 00:19:12.780 --> 00:19:14.210 align:start position:0% these guys really<00:19:13.260> great 00:19:14.210 --> 00:19:14.220 align:start position:0% really great 00:19:14.220 --> 00:19:16.610 align:start position:0% really great things<00:19:14.880> we<00:19:15.419> used<00:19:15.600> it<00:19:15.720> at<00:19:15.840> devconnect<00:19:16.200> that<00:19:16.500> was 00:19:16.610 --> 00:19:16.620 align:start position:0% things we used it at devconnect that was 00:19:16.620 --> 00:19:18.110 align:start position:0% things we used it at devconnect that was the<00:19:16.740> first<00:19:16.860> demo<00:19:17.160> that<00:19:17.280> we<00:19:17.400> used<00:19:17.580> it<00:19:18.000> was 00:19:18.110 --> 00:19:18.120 align:start position:0% the first demo that we used it was 00:19:18.120 --> 00:19:21.289 align:start position:0% the first demo that we used it was awesome<00:19:18.380> lots<00:19:19.380> of<00:19:19.440> traction<00:19:19.820> we<00:19:20.820> hacked<00:19:21.120> a 00:19:21.289 --> 00:19:21.299 align:start position:0% awesome lots of traction we hacked a 00:19:21.299 --> 00:19:22.730 align:start position:0% awesome lots of traction we hacked a demo<00:19:21.600> in<00:19:21.720> like<00:19:21.900> a<00:19:22.080> week 00:19:22.730 --> 00:19:22.740 align:start position:0% demo in like a week 00:19:22.740 --> 00:19:24.289 align:start position:0% demo in like a week and<00:19:23.280> so<00:19:23.520> that's<00:19:23.580> why<00:19:23.700> I'm<00:19:23.820> saying<00:19:23.940> it's<00:19:24.120> a 00:19:24.289 --> 00:19:24.299 align:start position:0% and so that's why I'm saying it's a 00:19:24.299 --> 00:19:26.630 align:start position:0% and so that's why I'm saying it's a great<00:19:24.419> team<00:19:24.600> because<00:19:24.780> we<00:19:25.260> didn't<00:19:25.500> really<00:19:25.919> plan 00:19:26.630 --> 00:19:26.640 align:start position:0% great team because we didn't really plan 00:19:26.640 --> 00:19:28.549 align:start position:0% great team because we didn't really plan the<00:19:26.880> development<00:19:27.179> it<00:19:27.419> was<00:19:27.539> just<00:19:27.720> it<00:19:28.380> was 00:19:28.549 --> 00:19:28.559 align:start position:0% the development it was just it was 00:19:28.559 --> 00:19:30.049 align:start position:0% the development it was just it was really<00:19:28.679> a<00:19:28.860> decentralized<00:19:29.460> development 00:19:30.049 --> 00:19:30.059 align:start position:0% really a decentralized development 00:19:30.059 --> 00:19:31.789 align:start position:0% really a decentralized development effort<00:19:30.480> because<00:19:30.840> everyone<00:19:31.140> was<00:19:31.380> doing<00:19:31.559> its 00:19:31.789 --> 00:19:31.799 align:start position:0% effort because everyone was doing its 00:19:31.799 --> 00:19:33.950 align:start position:0% effort because everyone was doing its own<00:19:31.860> thing<00:19:32.039> right<00:19:32.299> so<00:19:33.299> but<00:19:33.539> we<00:19:33.720> go<00:19:33.840> to 00:19:33.950 --> 00:19:33.960 align:start position:0% own thing right so but we go to 00:19:33.960 --> 00:19:36.230 align:start position:0% own thing right so but we go to devconnect<00:19:34.440> it<00:19:35.280> was<00:19:35.400> awesome<00:19:35.520> we<00:19:35.880> got<00:19:36.000> great 00:19:36.230 --> 00:19:36.240 align:start position:0% devconnect it was awesome we got great 00:19:36.240 --> 00:19:40.390 align:start position:0% devconnect it was awesome we got great numbers<00:19:36.480> on<00:19:36.660> viewership<00:19:37.340> and<00:19:38.340> no<00:19:38.880> box<00:19:39.240> I<00:19:40.020> think 00:19:40.390 --> 00:19:40.400 align:start position:0% numbers on viewership and no box I think 00:19:40.400 --> 00:19:42.470 align:start position:0% numbers on viewership and no box I think uh<00:19:41.400> so<00:19:41.640> great 00:19:42.470 --> 00:19:42.480 align:start position:0% uh so great 00:19:42.480 --> 00:19:45.529 align:start position:0% uh so great then<00:19:42.840> we<00:19:43.020> went<00:19:43.140> to<00:19:43.260> Ether<00:19:43.559> Lane<00:19:43.940> and<00:19:44.940> you<00:19:45.480> know 00:19:45.529 --> 00:19:45.539 align:start position:0% then we went to Ether Lane and you know 00:19:45.539 --> 00:19:47.930 align:start position:0% then we went to Ether Lane and you know we<00:19:45.780> redid<00:19:46.200> the<00:19:46.380> design<00:19:46.559> and<00:19:47.460> we<00:19:47.700> call<00:19:47.820> this 00:19:47.930 --> 00:19:47.940 align:start position:0% we redid the design and we call this 00:19:47.940 --> 00:19:50.690 align:start position:0% we redid the design and we call this stream<00:19:48.120> stream<00:19:48.660> is<00:19:48.900> 2.0<00:19:49.380> we<00:19:50.039> added<00:19:50.340> dark<00:19:50.460> mode 00:19:50.690 --> 00:19:50.700 align:start position:0% stream stream is 2.0 we added dark mode 00:19:50.700 --> 00:19:53.390 align:start position:0% stream stream is 2.0 we added dark mode which<00:19:51.419> is<00:19:52.080> actually<00:19:52.440> the<00:19:52.679> best<00:19:52.799> feature<00:19:53.160> in 00:19:53.390 --> 00:19:53.400 align:start position:0% which is actually the best feature in 00:19:53.400 --> 00:19:56.830 align:start position:0% which is actually the best feature in the<00:19:53.460> whole<00:19:53.580> application<00:19:54.380> uh<00:19:55.380> the<00:19:55.799> schedule 00:19:56.830 --> 00:19:56.840 align:start position:0% the whole application uh the schedule 00:19:56.840 --> 00:20:00.470 align:start position:0% the whole application uh the schedule and<00:19:57.840> super<00:19:58.559> good<00:19:59.280> there<00:19:59.820> really<00:20:00.059> we<00:20:00.240> had<00:20:00.360> no 00:20:00.470 --> 00:20:00.480 align:start position:0% and super good there really we had no 00:20:00.480 --> 00:20:02.690 align:start position:0% and super good there really we had no bugs<00:20:00.900> and<00:20:01.200> I<00:20:01.440> I<00:20:01.559> know<00:20:01.679> this<00:20:01.860> for<00:20:01.980> sure 00:20:02.690 --> 00:20:02.700 align:start position:0% bugs and I I know this for sure 00:20:02.700 --> 00:20:05.390 align:start position:0% bugs and I I know this for sure and<00:20:03.539> and<00:20:03.960> overall<00:20:04.320> we're<00:20:04.620> super<00:20:04.860> happy<00:20:05.100> with 00:20:05.390 --> 00:20:05.400 align:start position:0% and and overall we're super happy with 00:20:05.400 --> 00:20:09.350 align:start position:0% and and overall we're super happy with it<00:20:06.059> and<00:20:06.780> then<00:20:07.140> yeah<00:20:07.559> Defcon<00:20:08.100> which<00:20:08.580> is<00:20:08.760> a<00:20:09.120> great 00:20:09.350 --> 00:20:09.360 align:start position:0% it and then yeah Defcon which is a great 00:20:09.360 --> 00:20:11.150 align:start position:0% it and then yeah Defcon which is a great so<00:20:10.140> yeah 00:20:11.150 --> 00:20:11.160 align:start position:0% so yeah 00:20:11.160 --> 00:20:12.590 align:start position:0% so yeah and<00:20:11.400> how<00:20:11.520> this<00:20:11.640> feature<00:20:11.940> look<00:20:12.120> like<00:20:12.299> we're 00:20:12.590 --> 00:20:12.600 align:start position:0% and how this feature look like we're 00:20:12.600 --> 00:20:14.090 align:start position:0% and how this feature look like we're gonna<00:20:12.720> focus<00:20:12.960> on<00:20:13.080> usability<00:20:13.500> we're<00:20:13.919> going<00:20:14.039> to 00:20:14.090 --> 00:20:14.100 align:start position:0% gonna focus on usability we're going to 00:20:14.100 --> 00:20:15.710 align:start position:0% gonna focus on usability we're going to focus<00:20:14.280> on<00:20:14.460> plugins<00:20:14.760> and<00:20:15.360> we're<00:20:15.539> going<00:20:15.660> to 00:20:15.710 --> 00:20:15.720 align:start position:0% focus on plugins and we're going to 00:20:15.720 --> 00:20:17.150 align:start position:0% focus on plugins and we're going to focus<00:20:15.900> on<00:20:16.080> embracing<00:20:16.440> the<00:20:16.559> web<00:20:16.620> 3<00:20:16.799> ecosystem 00:20:17.150 --> 00:20:17.160 align:start position:0% focus on embracing the web 3 ecosystem 00:20:17.160 --> 00:20:18.730 align:start position:0% focus on embracing the web 3 ecosystem like<00:20:17.460> we<00:20:17.580> said 00:20:18.730 --> 00:20:18.740 align:start position:0% like we said 00:20:18.740 --> 00:20:21.590 align:start position:0% like we said and<00:20:19.740> yeah 00:20:21.590 --> 00:20:21.600 align:start position:0% and yeah 00:20:21.600 --> 00:20:24.169 align:start position:0% and yeah and<00:20:22.020> this<00:20:22.200> is<00:20:22.320> kind<00:20:22.740> of<00:20:22.860> like<00:20:23.039> our<00:20:23.640> vision<00:20:23.940> I 00:20:24.169 --> 00:20:24.179 align:start position:0% and this is kind of like our vision I 00:20:24.179 --> 00:20:25.190 align:start position:0% and this is kind of like our vision I don't<00:20:24.299> know<00:20:24.360> if<00:20:24.419> you<00:20:24.480> guys<00:20:24.600> know<00:20:24.720> WordPress 00:20:25.190 --> 00:20:25.200 align:start position:0% don't know if you guys know WordPress 00:20:25.200 --> 00:20:26.049 align:start position:0% don't know if you guys know WordPress but 00:20:26.049 --> 00:20:26.059 align:start position:0% but 00:20:26.059 --> 00:20:28.190 align:start position:0% but the<00:20:27.059> vision<00:20:27.240> that<00:20:27.480> we<00:20:27.600> had<00:20:27.720> since<00:20:28.080> the 00:20:28.190 --> 00:20:28.200 align:start position:0% the vision that we had since the 00:20:28.200 --> 00:20:30.470 align:start position:0% the vision that we had since the beginning<00:20:28.380> is<00:20:28.679> to<00:20:29.039> have<00:20:29.700> stream<00:20:30.000> with<00:20:30.299> be 00:20:30.470 --> 00:20:30.480 align:start position:0% beginning is to have stream with be 00:20:30.480 --> 00:20:32.750 align:start position:0% beginning is to have stream with be WordPress<00:20:30.960> so<00:20:31.200> something<00:20:31.500> so<00:20:32.100> WordPress<00:20:32.580> 4 00:20:32.750 --> 00:20:32.760 align:start position:0% WordPress so something so WordPress 4 00:20:32.760 --> 00:20:35.570 align:start position:0% WordPress so something so WordPress 4 video<00:20:33.000> right<00:20:33.780> so<00:20:34.020> something<00:20:34.260> that<00:20:34.740> a<00:20:35.280> event 00:20:35.570 --> 00:20:35.580 align:start position:0% video right so something that a event 00:20:35.580 --> 00:20:38.390 align:start position:0% video right so something that a event organizers<00:20:36.120> can<00:20:36.240> clone<00:20:36.480> and<00:20:36.780> use<00:20:36.960> quickly<00:20:37.440> to 00:20:38.390 --> 00:20:38.400 align:start position:0% organizers can clone and use quickly to 00:20:38.400 --> 00:20:40.430 align:start position:0% organizers can clone and use quickly to to<00:20:38.700> stream<00:20:39.000> their<00:20:39.240> events 00:20:40.430 --> 00:20:40.440 align:start position:0% to stream their events 00:20:40.440 --> 00:20:44.270 align:start position:0% to stream their events hello<00:20:40.980> hi<00:20:41.340> Paula<00:20:41.880> thank<00:20:42.360> you<00:20:42.480> for<00:20:42.660> your<00:20:42.780> talk 00:20:44.270 --> 00:20:44.280 align:start position:0% hello hi Paula thank you for your talk 00:20:44.280 --> 00:20:46.730 align:start position:0% hello hi Paula thank you for your talk um I<00:20:44.640> am<00:20:44.760> a<00:20:44.940> Bernard<00:20:45.240> organizer<00:20:45.780> and<00:20:46.320> I<00:20:46.620> have 00:20:46.730 --> 00:20:46.740 align:start position:0% um I am a Bernard organizer and I have 00:20:46.740 --> 00:20:50.210 align:start position:0% um I am a Bernard organizer and I have used<00:20:46.980> several<00:20:47.460> streaming<00:20:48.419> providers<00:20:48.919> and<00:20:49.919> I 00:20:50.210 --> 00:20:50.220 align:start position:0% used several streaming providers and I 00:20:50.220 --> 00:20:52.190 align:start position:0% used several streaming providers and I like<00:20:50.400> live<00:20:50.880> peer<00:20:51.299> but<00:20:51.480> one<00:20:51.720> thing<00:20:51.900> that 00:20:52.190 --> 00:20:52.200 align:start position:0% like live peer but one thing that 00:20:52.200 --> 00:20:56.169 align:start position:0% like live peer but one thing that worries<00:20:52.559> me<00:20:52.760> is<00:20:53.760> how<00:20:54.600> is<00:20:54.780> the<00:20:54.960> performance 00:20:56.169 --> 00:20:56.179 align:start position:0% worries me is how is the performance 00:20:56.179 --> 00:20:59.090 align:start position:0% worries me is how is the performance compared<00:20:57.179> to<00:20:57.299> other<00:20:58.140> Alternatives<00:20:58.679> like 00:20:59.090 --> 00:20:59.100 align:start position:0% compared to other Alternatives like 00:20:59.100 --> 00:21:01.010 align:start position:0% compared to other Alternatives like Vimeo<00:20:59.940> YouTube 00:21:01.010 --> 00:21:01.020 align:start position:0% Vimeo YouTube 00:21:01.020 --> 00:21:03.529 align:start position:0% Vimeo YouTube because<00:21:01.559> this<00:21:02.039> is<00:21:02.160> the<00:21:02.280> centralized<00:21:02.700> so<00:21:03.000> this 00:21:03.529 --> 00:21:03.539 align:start position:0% because this is the centralized so this 00:21:03.539 --> 00:21:07.070 align:start position:0% because this is the centralized so this is<00:21:03.660> kind<00:21:03.840> of<00:21:03.960> worry<00:21:04.080> for<00:21:04.380> for<00:21:04.620> events<00:21:04.980> yes 00:21:07.070 --> 00:21:07.080 align:start position:0% is kind of worry for for events yes 00:21:07.080 --> 00:21:11.210 align:start position:0% is kind of worry for for events yes so<00:21:07.740> this<00:21:08.240> library<00:21:09.240> is<00:21:09.539> pretty<00:21:09.720> good<00:21:09.900> so<00:21:10.500> I<00:21:10.799> was 00:21:11.210 --> 00:21:11.220 align:start position:0% so this library is pretty good so I was 00:21:11.220 --> 00:21:13.310 align:start position:0% so this library is pretty good so I was a<00:21:11.400> pretty<00:21:11.760> early<00:21:11.940> Community<00:21:12.240> member<00:21:12.720> and<00:21:13.200> I've 00:21:13.310 --> 00:21:13.320 align:start position:0% a pretty early Community member and I've 00:21:13.320 --> 00:21:15.230 align:start position:0% a pretty early Community member and I've been<00:21:13.440> using<00:21:13.679> it<00:21:13.860> in<00:21:14.160> the<00:21:14.520> early<00:21:14.580> days<00:21:14.820> it<00:21:15.059> had 00:21:15.230 --> 00:21:15.240 align:start position:0% been using it in the early days it had 00:21:15.240 --> 00:21:17.150 align:start position:0% been using it in the early days it had some<00:21:15.360> issues<00:21:15.780> so<00:21:16.380> since<00:21:16.559> the<00:21:16.740> beginning<00:21:16.860> I 00:21:17.150 --> 00:21:17.160 align:start position:0% some issues so since the beginning I 00:21:17.160 --> 00:21:18.710 align:start position:0% some issues so since the beginning I come<00:21:17.400> from<00:21:17.520> the<00:21:17.700> web<00:21:17.880> to<00:21:18.120> world<00:21:18.480> like 00:21:18.710 --> 00:21:18.720 align:start position:0% come from the web to world like 00:21:18.720 --> 00:21:20.690 align:start position:0% come from the web to world like production<00:21:19.080> world<00:21:19.380> and<00:21:20.220> you<00:21:20.400> always<00:21:20.520> have 00:21:20.690 --> 00:21:20.700 align:start position:0% production world and you always have 00:21:20.700 --> 00:21:22.850 align:start position:0% production world and you always have failovers<00:21:21.780> and<00:21:22.140> when<00:21:22.320> I<00:21:22.440> started<00:21:22.559> using<00:21:22.740> knife 00:21:22.850 --> 00:21:22.860 align:start position:0% failovers and when I started using knife 00:21:22.860 --> 00:21:24.049 align:start position:0% failovers and when I started using knife period<00:21:23.160> I<00:21:23.220> was<00:21:23.280> like<00:21:23.400> hey<00:21:23.520> we<00:21:23.640> need<00:21:23.760> to<00:21:23.820> build<00:21:23.940> a 00:21:24.049 --> 00:21:24.059 align:start position:0% period I was like hey we need to build a 00:21:24.059 --> 00:21:25.669 align:start position:0% period I was like hey we need to build a failover<00:21:24.419> here<00:21:24.660> so<00:21:25.080> that's<00:21:25.200> why<00:21:25.380> we<00:21:25.500> have 00:21:25.669 --> 00:21:25.679 align:start position:0% failover here so that's why we have 00:21:25.679 --> 00:21:27.529 align:start position:0% failover here so that's why we have built<00:21:26.100> in<00:21:26.160> a<00:21:26.280> failover<00:21:26.580> mechanism<00:21:26.940> into<00:21:27.240> all 00:21:27.529 --> 00:21:27.539 align:start position:0% built in a failover mechanism into all 00:21:27.539 --> 00:21:29.930 align:start position:0% built in a failover mechanism into all of<00:21:27.660> our<00:21:27.780> players<00:21:28.260> right<00:21:28.559> so 00:21:29.930 --> 00:21:29.940 align:start position:0% of our players right so 00:21:29.940 --> 00:21:31.730 align:start position:0% of our players right so on<00:21:30.360> the<00:21:30.480> one<00:21:30.539> hand<00:21:30.659> life<00:21:31.020> here<00:21:31.260> got<00:21:31.440> really 00:21:31.730 --> 00:21:31.740 align:start position:0% on the one hand life here got really 00:21:31.740 --> 00:21:34.669 align:start position:0% on the one hand life here got really good<00:21:32.159> already<00:21:32.760> on<00:21:33.659> the<00:21:33.720> other<00:21:33.840> hand<00:21:34.020> we<00:21:34.320> have<00:21:34.500> a 00:21:34.669 --> 00:21:34.679 align:start position:0% good already on the other hand we have a 00:21:34.679 --> 00:21:37.149 align:start position:0% good already on the other hand we have a failover<00:21:35.039> mechanism<00:21:35.580> that<00:21:35.940> allows 00:21:37.149 --> 00:21:37.159 align:start position:0% failover mechanism that allows 00:21:37.159 --> 00:21:40.430 align:start position:0% failover mechanism that allows to<00:21:38.159> basically<00:21:38.580> set<00:21:38.940> two<00:21:39.539> live<00:21:39.720> peer<00:21:40.080> channels 00:21:40.430 --> 00:21:40.440 align:start position:0% to basically set two live peer channels 00:21:40.440 --> 00:21:42.890 align:start position:0% to basically set two live peer channels for<00:21:40.559> the<00:21:40.740> same<00:21:40.860> room<00:21:41.220> so<00:21:41.940> you<00:21:42.059> have<00:21:42.179> double<00:21:42.480> the 00:21:42.890 --> 00:21:42.900 align:start position:0% for the same room so you have double the 00:21:42.900 --> 00:21:44.450 align:start position:0% for the same room so you have double the reliability 00:21:44.450 --> 00:21:44.460 align:start position:0% reliability 00:21:44.460 --> 00:21:46.070 align:start position:0% reliability so<00:21:45.000> yeah 00:21:46.070 --> 00:21:46.080 align:start position:0% so yeah 00:21:46.080 --> 00:21:49.610 align:start position:0% so yeah but<00:21:46.440> what<00:21:46.620> about<00:21:47.120> the<00:21:48.120> streaming<00:21:48.539> related<00:21:48.840> to 00:21:49.610 --> 00:21:49.620 align:start position:0% but what about the streaming related to 00:21:49.620 --> 00:21:53.029 align:start position:0% but what about the streaming related to attendees<00:21:50.159> because<00:21:51.059> you<00:21:51.659> have<00:21:51.840> attendees<00:21:52.500> all 00:21:53.029 --> 00:21:53.039 align:start position:0% attendees because you have attendees all 00:21:53.039 --> 00:21:56.090 align:start position:0% attendees because you have attendees all around<00:21:53.220> the<00:21:53.520> world<00:21:53.960> and<00:21:54.960> streaming<00:21:55.620> providers 00:21:56.090 --> 00:21:56.100 align:start position:0% around the world and streaming providers 00:21:56.100 --> 00:21:59.210 align:start position:0% around the world and streaming providers have<00:21:56.520> like<00:21:57.000> a<00:21:57.179> CDN<00:21:57.659> contact<00:21:57.900> yeah<00:21:58.260> no<00:21:58.919> so<00:21:59.039> how 00:21:59.210 --> 00:21:59.220 align:start position:0% have like a CDN contact yeah no so how 00:21:59.220 --> 00:22:02.750 align:start position:0% have like a CDN contact yeah no so how light<00:21:59.520> peers<00:21:59.880> solves<00:22:00.419> that<00:22:00.539> yeah<00:22:00.960> lifer 00:22:02.750 --> 00:22:02.760 align:start position:0% light peers solves that yeah lifer 00:22:02.760 --> 00:22:04.490 align:start position:0% light peers solves that yeah lifer oh<00:22:03.240> there's<00:22:03.480> a<00:22:03.659> bit<00:22:03.720> of<00:22:03.840> a<00:22:03.960> more<00:22:04.140> complex 00:22:04.490 --> 00:22:04.500 align:start position:0% oh there's a bit of a more complex 00:22:04.500 --> 00:22:05.630 align:start position:0% oh there's a bit of a more complex question<00:22:04.679> because<00:22:04.919> you<00:22:05.159> have<00:22:05.280> the<00:22:05.340> life<00:22:05.460> of 00:22:05.630 --> 00:22:05.640 align:start position:0% question because you have the life of 00:22:05.640 --> 00:22:06.830 align:start position:0% question because you have the life of the<00:22:05.760> protocol<00:22:05.940> and<00:22:06.179> then<00:22:06.240> you<00:22:06.360> have<00:22:06.419> live<00:22:06.600> for 00:22:06.830 --> 00:22:06.840 align:start position:0% the protocol and then you have live for 00:22:06.840 --> 00:22:09.230 align:start position:0% the protocol and then you have live for your<00:22:06.960> studio<00:22:07.460> but<00:22:08.460> basically<00:22:08.760> live<00:22:09.000> here 00:22:09.230 --> 00:22:09.240 align:start position:0% your studio but basically live here 00:22:09.240 --> 00:22:11.149 align:start position:0% your studio but basically live here studio<00:22:09.480> and<00:22:09.720> that's<00:22:09.840> what<00:22:10.080> we<00:22:10.260> are<00:22:10.380> using<00:22:10.620> has 00:22:11.149 --> 00:22:11.159 align:start position:0% studio and that's what we are using has 00:22:11.159 --> 00:22:15.110 align:start position:0% studio and that's what we are using has its<00:22:11.460> own<00:22:11.520> CDN<00:22:12.500> and<00:22:13.500> agency<00:22:13.980> is<00:22:14.280> pretty<00:22:14.460> good<00:22:14.640> so 00:22:15.110 --> 00:22:15.120 align:start position:0% its own CDN and agency is pretty good so 00:22:15.120 --> 00:22:16.490 align:start position:0% its own CDN and agency is pretty good so you<00:22:15.240> shouldn't<00:22:15.539> be<00:22:15.659> have<00:22:15.840> an<00:22:15.960> issue<00:22:16.200> if<00:22:16.380> you 00:22:16.490 --> 00:22:16.500 align:start position:0% you shouldn't be have an issue if you 00:22:16.500 --> 00:22:18.830 align:start position:0% you shouldn't be have an issue if you have<00:22:16.679> people<00:22:17.100> from<00:22:17.460> around<00:22:18.299> the<00:22:18.539> world<00:22:18.659> trying 00:22:18.830 --> 00:22:18.840 align:start position:0% have people from around the world trying 00:22:18.840 --> 00:22:20.029 align:start position:0% have people from around the world trying to<00:22:19.020> watch<00:22:19.140> your<00:22:19.260> stream<00:22:19.500> like<00:22:19.860> I<00:22:19.919> said 00:22:20.029 --> 00:22:20.039 align:start position:0% to watch your stream like I said 00:22:20.039 --> 00:22:21.770 align:start position:0% to watch your stream like I said performance<00:22:20.520> is<00:22:20.640> really<00:22:20.820> good<00:22:21.000> East<00:22:21.419> Berlin 00:22:21.770 --> 00:22:21.780 align:start position:0% performance is really good East Berlin 00:22:21.780 --> 00:22:24.169 align:start position:0% performance is really good East Berlin we<00:22:22.140> had<00:22:22.260> a<00:22:22.740> bunch<00:22:22.860> of<00:22:22.980> people<00:22:23.159> watching<00:22:23.700> that's 00:22:24.169 --> 00:22:24.179 align:start position:0% we had a bunch of people watching that's 00:22:24.179 --> 00:22:25.490 align:start position:0% we had a bunch of people watching that's kind<00:22:24.480> of<00:22:24.600> bunch<00:22:24.720> of<00:22:24.840> people<00:22:24.900> watching<00:22:25.200> here 00:22:25.490 --> 00:22:25.500 align:start position:0% kind of bunch of people watching here 00:22:25.500 --> 00:22:28.549 align:start position:0% kind of bunch of people watching here you<00:22:26.159> know<00:22:26.220> it's<00:22:26.460> Defcon<00:22:26.940> yesterday<00:22:27.720> we<00:22:28.020> had<00:22:28.140> 3K 00:22:28.549 --> 00:22:28.559 align:start position:0% you know it's Defcon yesterday we had 3K 00:22:28.559 --> 00:22:32.870 align:start position:0% you know it's Defcon yesterday we had 3K views<00:22:28.919> online<00:22:30.080> and<00:22:31.080> almost<00:22:31.740> no<00:22:31.980> downtime<00:22:32.340> so 00:22:32.870 --> 00:22:32.880 align:start position:0% views online and almost no downtime so 00:22:32.880 --> 00:22:35.810 align:start position:0% views online and almost no downtime so yeah<00:22:33.600> if<00:22:34.020> you<00:22:34.200> want<00:22:34.320> we<00:22:34.440> can<00:22:34.620> speak<00:22:34.860> later<00:22:35.100> and 00:22:35.810 --> 00:22:35.820 align:start position:0% yeah if you want we can speak later and 00:22:35.820 --> 00:22:38.750 align:start position:0% yeah if you want we can speak later and I<00:22:36.059> can<00:22:36.179> explain<00:22:36.480> a<00:22:36.780> bit<00:22:36.900> more 00:22:38.750 --> 00:22:38.760 align:start position:0% I can explain a bit more 00:22:38.760 --> 00:22:40.010 align:start position:0% I can explain a bit more yep 00:22:40.010 --> 00:22:40.020 align:start position:0% yep 00:22:40.020 --> 00:22:42.679 align:start position:0% yep thank<00:22:40.559> you