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:13.150 align:start position:0% [Music] 00:00:13.150 --> 00:00:13.160 align:start position:0% 00:00:13.160 --> 00:00:16.849 align:start position:0% our<00:00:14.160> team<00:00:14.280> is<00:00:14.519> about<00:00:14.759> as<00:00:15.360> a<00:00:15.540> growing<00:00:15.839> team<00:00:16.139> a 00:00:16.849 --> 00:00:16.859 align:start position:0% our team is about as a growing team a 00:00:16.859 --> 00:00:20.450 align:start position:0% our team is about as a growing team a bit<00:00:16.980> over<00:00:17.279> 60<00:00:17.760> people<00:00:18.119> now<00:00:18.539> and<00:00:19.199> they're 00:00:20.450 --> 00:00:20.460 align:start position:0% bit over 60 people now and they're 00:00:20.460 --> 00:00:23.390 align:start position:0% bit over 60 people now and they're six<00:00:20.939> of<00:00:21.119> us<00:00:21.300> who<00:00:21.720> make<00:00:21.900> up<00:00:22.140> the<00:00:22.740> design<00:00:23.039> and 00:00:23.390 --> 00:00:23.400 align:start position:0% six of us who make up the design and 00:00:23.400 --> 00:00:25.189 align:start position:0% six of us who make up the design and Communications<00:00:24.000> team 00:00:25.189 --> 00:00:25.199 align:start position:0% Communications team 00:00:25.199 --> 00:00:27.950 align:start position:0% Communications team we<00:00:25.619> all<00:00:25.740> work<00:00:25.980> really<00:00:26.279> closely<00:00:26.820> with<00:00:27.240> our<00:00:27.480> devs 00:00:27.950 --> 00:00:27.960 align:start position:0% we all work really closely with our devs 00:00:27.960 --> 00:00:30.890 align:start position:0% we all work really closely with our devs and<00:00:28.560> have<00:00:28.800> weekly<00:00:29.279> meetings<00:00:29.760> to<00:00:30.300> facilitate 00:00:30.890 --> 00:00:30.900 align:start position:0% and have weekly meetings to facilitate 00:00:30.900 --> 00:00:32.690 align:start position:0% and have weekly meetings to facilitate remote<00:00:31.260> collaboration 00:00:32.690 --> 00:00:32.700 align:start position:0% remote collaboration 00:00:32.700 --> 00:00:35.510 align:start position:0% remote collaboration on<00:00:33.300> CK<00:00:33.660> apps<00:00:34.079> and<00:00:34.200> protocols 00:00:35.510 --> 00:00:35.520 align:start position:0% on CK apps and protocols 00:00:35.520 --> 00:00:38.150 align:start position:0% on CK apps and protocols and<00:00:36.180> we<00:00:36.360> used<00:00:36.540> design<00:00:36.840> to<00:00:37.200> align<00:00:37.620> teammates 00:00:38.150 --> 00:00:38.160 align:start position:0% and we used design to align teammates 00:00:38.160 --> 00:00:41.389 align:start position:0% and we used design to align teammates from<00:00:38.760> various<00:00:39.300> technical<00:00:39.780> backgrounds 00:00:41.389 --> 00:00:41.399 align:start position:0% from various technical backgrounds 00:00:41.399 --> 00:00:43.549 align:start position:0% from various technical backgrounds creating<00:00:41.940> this<00:00:42.180> common<00:00:42.559> understanding 00:00:43.549 --> 00:00:43.559 align:start position:0% creating this common understanding 00:00:43.559 --> 00:00:45.830 align:start position:0% creating this common understanding internally<00:00:44.280> allows<00:00:44.640> us<00:00:44.820> to<00:00:45.120> communicate<00:00:45.540> the 00:00:45.830 --> 00:00:45.840 align:start position:0% internally allows us to communicate the 00:00:45.840 --> 00:00:48.290 align:start position:0% internally allows us to communicate the value<00:00:46.020> of<00:00:46.440> our<00:00:46.680> open<00:00:47.160> source<00:00:47.640> protocols<00:00:48.180> and 00:00:48.290 --> 00:00:48.300 align:start position:0% value of our open source protocols and 00:00:48.300 --> 00:00:52.010 align:start position:0% value of our open source protocols and apps<00:00:49.200> to<00:00:49.559> the<00:00:49.680> ecosystem<00:00:50.160> so<00:00:51.059> that<00:00:51.300> you<00:00:51.660> our 00:00:52.010 --> 00:00:52.020 align:start position:0% apps to the ecosystem so that you our 00:00:52.020 --> 00:00:54.590 align:start position:0% apps to the ecosystem so that you our community<00:00:52.399> Can<00:00:53.399> Dream<00:00:53.640> up<00:00:53.879> and<00:00:54.120> build<00:00:54.300> your 00:00:54.590 --> 00:00:54.600 align:start position:0% community Can Dream up and build your 00:00:54.600 --> 00:00:57.170 align:start position:0% community Can Dream up and build your own<00:00:54.780> ZK<00:00:55.260> products<00:00:55.860> when<00:00:56.399> I<00:00:56.520> started<00:00:56.879> working 00:00:57.170 --> 00:00:57.180 align:start position:0% own ZK products when I started working 00:00:57.180 --> 00:01:00.529 align:start position:0% own ZK products when I started working with<00:00:57.539> PSE<00:00:58.100> designing<00:00:59.100> public<00:00:59.399> goods<00:00:59.940> it<00:01:00.360> took 00:01:00.529 --> 00:01:00.539 align:start position:0% with PSE designing public goods it took 00:01:00.539 --> 00:01:03.229 align:start position:0% with PSE designing public goods it took me<00:01:00.660> some<00:01:00.960> time<00:01:01.199> to<00:01:01.500> wrap<00:01:01.620> my<00:01:01.920> head<00:01:02.100> around<00:01:02.399> the 00:01:03.229 --> 00:01:03.239 align:start position:0% me some time to wrap my head around the 00:01:03.239 --> 00:01:06.050 align:start position:0% me some time to wrap my head around the idea<00:01:03.539> of<00:01:03.780> not<00:01:04.019> designing<00:01:04.500> for<00:01:04.799> profit 00:01:06.050 --> 00:01:06.060 align:start position:0% idea of not designing for profit 00:01:06.060 --> 00:01:08.390 align:start position:0% idea of not designing for profit because<00:01:06.540> almost<00:01:06.960> all<00:01:07.260> of<00:01:07.439> my<00:01:07.619> previous<00:01:07.799> design 00:01:08.390 --> 00:01:08.400 align:start position:0% because almost all of my previous design 00:01:08.400 --> 00:01:11.929 align:start position:0% because almost all of my previous design experience<00:01:09.380> involved<00:01:10.380> aligning<00:01:10.979> ux<00:01:11.400> strategy 00:01:11.929 --> 00:01:11.939 align:start position:0% experience involved aligning ux strategy 00:01:11.939 --> 00:01:13.850 align:start position:0% experience involved aligning ux strategy with<00:01:12.299> business<00:01:12.540> goals 00:01:13.850 --> 00:01:13.860 align:start position:0% with business goals 00:01:13.860 --> 00:01:16.490 align:start position:0% with business goals it<00:01:14.280> was<00:01:14.400> a<00:01:14.580> big<00:01:14.700> mental<00:01:15.180> shift<00:01:15.479> to<00:01:15.900> move<00:01:16.080> from 00:01:16.490 --> 00:01:16.500 align:start position:0% it was a big mental shift to move from 00:01:16.500 --> 00:01:19.850 align:start position:0% it was a big mental shift to move from designing<00:01:17.280> to<00:01:17.520> increase<00:01:17.760> sales<00:01:18.360> or<00:01:19.200> signups 00:01:19.850 --> 00:01:19.860 align:start position:0% designing to increase sales or signups 00:01:19.860 --> 00:01:23.030 align:start position:0% designing to increase sales or signups to<00:01:20.340> designing<00:01:20.820> to<00:01:21.000> attract<00:01:21.360> participants 00:01:23.030 --> 00:01:23.040 align:start position:0% to designing to attract participants 00:01:23.040 --> 00:01:25.789 align:start position:0% to designing to attract participants who<00:01:23.880> can<00:01:24.479> use<00:01:24.659> what<00:01:24.900> we<00:01:25.020> have<00:01:25.140> built<00:01:25.439> to<00:01:25.560> build 00:01:25.789 --> 00:01:25.799 align:start position:0% who can use what we have built to build 00:01:25.799 --> 00:01:29.030 align:start position:0% who can use what we have built to build their<00:01:26.040> own<00:01:26.159> thing<00:01:26.460> on<00:01:27.299> my<00:01:27.479> team<00:01:28.040> designers 00:01:29.030 --> 00:01:29.040 align:start position:0% their own thing on my team designers 00:01:29.040 --> 00:01:32.570 align:start position:0% their own thing on my team designers developers<00:01:30.020> writers<00:01:31.020> product<00:01:31.380> owners<00:01:31.920> we're 00:01:32.570 --> 00:01:32.580 align:start position:0% developers writers product owners we're 00:01:32.580 --> 00:01:34.910 align:start position:0% developers writers product owners we're all<00:01:32.820> using<00:01:33.119> design<00:01:33.420> as<00:01:33.780> a<00:01:34.020> tool<00:01:34.320> to<00:01:34.560> make<00:01:34.680> the 00:01:34.910 --> 00:01:34.920 align:start position:0% all using design as a tool to make the 00:01:34.920 --> 00:01:37.429 align:start position:0% all using design as a tool to make the unfamiliar<00:01:35.700> familiar 00:01:37.429 --> 00:01:37.439 align:start position:0% unfamiliar familiar 00:01:37.439 --> 00:01:40.490 align:start position:0% unfamiliar familiar in<00:01:38.040> this<00:01:38.220> presentation<00:01:39.140> I'll<00:01:40.140> start<00:01:40.320> by 00:01:40.490 --> 00:01:40.500 align:start position:0% in this presentation I'll start by 00:01:40.500 --> 00:01:42.770 align:start position:0% in this presentation I'll start by addressing<00:01:41.040> the<00:01:41.700> value<00:01:41.880> of<00:01:42.180> Designing<00:01:42.540> for 00:01:42.770 --> 00:01:42.780 align:start position:0% addressing the value of Designing for 00:01:42.780 --> 00:01:44.030 align:start position:0% addressing the value of Designing for privacy 00:01:44.030 --> 00:01:44.040 align:start position:0% privacy 00:01:44.040 --> 00:01:46.670 align:start position:0% privacy share<00:01:44.520> some<00:01:44.700> design<00:01:44.939> challenges<00:01:45.720> highlight<00:01:46.500> a 00:01:46.670 --> 00:01:46.680 align:start position:0% share some design challenges highlight a 00:01:46.680 --> 00:01:48.289 align:start position:0% share some design challenges highlight a few<00:01:46.799> ZK<00:01:47.220> apps 00:01:48.289 --> 00:01:48.299 align:start position:0% few ZK apps 00:01:48.299 --> 00:01:51.230 align:start position:0% few ZK apps discuss<00:01:49.020> the<00:01:49.619> ways<00:01:50.100> design<00:01:50.280> can<00:01:50.820> be<00:01:50.939> used<00:01:51.060> to 00:01:51.230 --> 00:01:51.240 align:start position:0% discuss the ways design can be used to 00:01:51.240 --> 00:01:53.870 align:start position:0% discuss the ways design can be used to facilitate<00:01:51.840> conversation<00:01:52.500> and<00:01:53.460> touch<00:01:53.700> on 00:01:53.870 --> 00:01:53.880 align:start position:0% facilitate conversation and touch on 00:01:53.880 --> 00:01:57.469 align:start position:0% facilitate conversation and touch on mental<00:01:54.299> models<00:01:54.780> the<00:01:55.619> PSE<00:01:56.240> we're<00:01:57.240> building 00:01:57.469 --> 00:01:57.479 align:start position:0% mental models the PSE we're building 00:01:57.479 --> 00:02:00.289 align:start position:0% mental models the PSE we're building privacy<00:01:58.259> and<00:01:58.740> anonymity<00:01:59.299> infrastructure 00:02:00.289 --> 00:02:00.299 align:start position:0% privacy and anonymity infrastructure 00:02:00.299 --> 00:02:03.170 align:start position:0% privacy and anonymity infrastructure using<00:02:00.960> zero<00:02:01.380> knowledge<00:02:01.680> proofs<00:02:02.220> so<00:02:02.880> that<00:02:03.000> you 00:02:03.170 --> 00:02:03.180 align:start position:0% using zero knowledge proofs so that you 00:02:03.180 --> 00:02:05.630 align:start position:0% using zero knowledge proofs so that you can<00:02:03.299> choose<00:02:03.600> how<00:02:04.200> much<00:02:04.320> of<00:02:04.560> your<00:02:04.799> identity<00:02:05.219> you 00:02:05.630 --> 00:02:05.640 align:start position:0% can choose how much of your identity you 00:02:05.640 --> 00:02:07.969 align:start position:0% can choose how much of your identity you want<00:02:05.820> to<00:02:06.000> expose<00:02:06.540> when<00:02:07.439> going<00:02:07.680> about 00:02:07.969 --> 00:02:07.979 align:start position:0% want to expose when going about 00:02:07.979 --> 00:02:10.309 align:start position:0% want to expose when going about interacting<00:02:08.880> with<00:02:09.179> others<00:02:09.539> on<00:02:09.780> the<00:02:09.899> ethereum 00:02:10.309 --> 00:02:10.319 align:start position:0% interacting with others on the ethereum 00:02:10.319 --> 00:02:12.170 align:start position:0% interacting with others on the ethereum blockchain 00:02:12.170 --> 00:02:12.180 align:start position:0% blockchain 00:02:12.180 --> 00:02:16.490 align:start position:0% blockchain put<00:02:12.780> simply<00:02:13.319> a<00:02:13.980> zero<00:02:14.340> knowledge<00:02:14.640> or<00:02:15.300> ZK<00:02:15.720> proof 00:02:16.490 --> 00:02:16.500 align:start position:0% put simply a zero knowledge or ZK proof 00:02:16.500 --> 00:02:19.910 align:start position:0% put simply a zero knowledge or ZK proof is<00:02:17.040> a<00:02:17.160> method<00:02:17.459> by<00:02:17.700> which<00:02:17.940> one<00:02:18.420> party<00:02:18.660> can<00:02:19.560> prove 00:02:19.910 --> 00:02:19.920 align:start position:0% is a method by which one party can prove 00:02:19.920 --> 00:02:22.729 align:start position:0% is a method by which one party can prove to<00:02:20.040> another<00:02:20.280> party<00:02:20.900> that<00:02:21.900> something<00:02:22.140> is<00:02:22.440> true 00:02:22.729 --> 00:02:22.739 align:start position:0% to another party that something is true 00:02:22.739 --> 00:02:24.949 align:start position:0% to another party that something is true without<00:02:23.160> revealing<00:02:23.819> anything<00:02:24.180> besides<00:02:24.840> the 00:02:24.949 --> 00:02:24.959 align:start position:0% without revealing anything besides the 00:02:24.959 --> 00:02:27.350 align:start position:0% without revealing anything besides the fact<00:02:25.140> that<00:02:25.379> it<00:02:25.560> is<00:02:25.680> true 00:02:27.350 --> 00:02:27.360 align:start position:0% fact that it is true 00:02:27.360 --> 00:02:29.570 align:start position:0% fact that it is true we<00:02:27.720> call<00:02:27.840> our<00:02:28.140> zero<00:02:28.680> knowledge<00:02:28.920> protocols<00:02:29.459> and 00:02:29.570 --> 00:02:29.580 align:start position:0% we call our zero knowledge protocols and 00:02:29.580 --> 00:02:31.490 align:start position:0% we call our zero knowledge protocols and apps<00:02:29.940> public<00:02:30.180> goods<00:02:30.660> because<00:02:30.959> they're<00:02:31.319> open 00:02:31.490 --> 00:02:31.500 align:start position:0% apps public goods because they're open 00:02:31.500 --> 00:02:34.790 align:start position:0% apps public goods because they're open source<00:02:32.099> and<00:02:32.340> free<00:02:32.520> for<00:02:32.819> anyone<00:02:33.300> to<00:02:34.260> build<00:02:34.500> with 00:02:34.790 --> 00:02:34.800 align:start position:0% source and free for anyone to build with 00:02:34.800 --> 00:02:36.170 align:start position:0% source and free for anyone to build with or<00:02:35.160> use 00:02:36.170 --> 00:02:36.180 align:start position:0% or use 00:02:36.180 --> 00:02:38.150 align:start position:0% or use I<00:02:36.660> believe<00:02:36.840> that<00:02:37.140> we<00:02:37.319> need<00:02:37.440> to<00:02:37.620> design<00:02:37.800> for 00:02:38.150 --> 00:02:38.160 align:start position:0% I believe that we need to design for 00:02:38.160 --> 00:02:41.030 align:start position:0% I believe that we need to design for privacy<00:02:38.760> so<00:02:39.360> that<00:02:39.480> we<00:02:39.660> can<00:02:39.780> evolve<00:02:40.319> beyond<00:02:40.800> our 00:02:41.030 --> 00:02:41.040 align:start position:0% privacy so that we can evolve beyond our 00:02:41.040 --> 00:02:42.830 align:start position:0% privacy so that we can evolve beyond our current<00:02:41.280> challenges 00:02:42.830 --> 00:02:42.840 align:start position:0% current challenges 00:02:42.840 --> 00:02:45.309 align:start position:0% current challenges understand<00:02:43.440> our<00:02:43.920> material<00:02:44.340> more<00:02:44.700> deeply 00:02:45.309 --> 00:02:45.319 align:start position:0% understand our material more deeply 00:02:45.319 --> 00:02:49.330 align:start position:0% understand our material more deeply involve<00:02:46.319> more<00:02:46.680> people<00:02:47.120> as<00:02:48.120> collaborative 00:02:49.330 --> 00:02:49.340 align:start position:0% involve more people as collaborative 00:02:49.340 --> 00:02:52.309 align:start position:0% involve more people as collaborative co-creative<00:02:50.340> participants<00:02:51.060> and<00:02:51.959> in<00:02:52.140> turn 00:02:52.309 --> 00:02:52.319 align:start position:0% co-creative participants and in turn 00:02:52.319 --> 00:02:54.770 align:start position:0% co-creative participants and in turn fortify<00:02:53.040> privacy<00:02:53.580> Solutions<00:02:54.000> with<00:02:54.420> greater 00:02:54.770 --> 00:02:54.780 align:start position:0% fortify privacy Solutions with greater 00:02:54.780 --> 00:02:57.830 align:start position:0% fortify privacy Solutions with greater anonymity<00:02:55.319> sets 00:02:57.830 --> 00:02:57.840 align:start position:0% anonymity sets 00:02:57.840 --> 00:03:01.130 align:start position:0% anonymity sets so<00:02:58.500> yes<00:02:59.099> privacy<00:02:59.940> resources<00:03:00.480> are<00:03:00.780> difficult 00:03:01.130 --> 00:03:01.140 align:start position:0% so yes privacy resources are difficult 00:03:01.140 --> 00:03:03.290 align:start position:0% so yes privacy resources are difficult to<00:03:01.500> opt<00:03:01.680> into 00:03:03.290 --> 00:03:03.300 align:start position:0% to opt into 00:03:03.300 --> 00:03:06.410 align:start position:0% to opt into true<00:03:03.840> user<00:03:04.560> experience<00:03:05.040> for<00:03:05.400> these<00:03:05.700> apps<00:03:06.060> has 00:03:06.410 --> 00:03:06.420 align:start position:0% true user experience for these apps has 00:03:06.420 --> 00:03:08.690 align:start position:0% true user experience for these apps has a<00:03:06.780> lot<00:03:06.900> of<00:03:07.019> room<00:03:07.200> for<00:03:07.500> improvement 00:03:08.690 --> 00:03:08.700 align:start position:0% a lot of room for improvement 00:03:08.700 --> 00:03:10.910 align:start position:0% a lot of room for improvement sure<00:03:09.120> the<00:03:09.420> material<00:03:09.780> is<00:03:10.140> abstract<00:03:10.560> and 00:03:10.910 --> 00:03:10.920 align:start position:0% sure the material is abstract and 00:03:10.920 --> 00:03:12.229 align:start position:0% sure the material is abstract and complex 00:03:12.229 --> 00:03:12.239 align:start position:0% complex 00:03:12.239 --> 00:03:14.390 align:start position:0% complex and<00:03:13.019> to<00:03:13.319> some<00:03:13.500> of<00:03:13.680> us 00:03:14.390 --> 00:03:14.400 align:start position:0% and to some of us 00:03:14.400 --> 00:03:16.449 align:start position:0% and to some of us zero<00:03:15.180> knowledge<00:03:15.480> feels<00:03:15.959> like 00:03:16.449 --> 00:03:16.459 align:start position:0% zero knowledge feels like 00:03:16.459 --> 00:03:19.970 align:start position:0% zero knowledge feels like incomprehensible<00:03:17.459> witchcraft 00:03:19.970 --> 00:03:19.980 align:start position:0% incomprehensible witchcraft 00:03:19.980 --> 00:03:22.070 align:start position:0% incomprehensible witchcraft but<00:03:20.400> design<00:03:20.580> can<00:03:20.940> help<00:03:21.060> people<00:03:21.300> from<00:03:21.720> any 00:03:22.070 --> 00:03:22.080 align:start position:0% but design can help people from any 00:03:22.080 --> 00:03:24.050 align:start position:0% but design can help people from any technical<00:03:22.500> background<00:03:22.980> make<00:03:23.400> sense<00:03:23.580> of<00:03:23.819> the 00:03:24.050 --> 00:03:24.060 align:start position:0% technical background make sense of the 00:03:24.060 --> 00:03:27.350 align:start position:0% technical background make sense of the things<00:03:24.180> that<00:03:24.480> they<00:03:24.659> don't<00:03:24.780> understand 00:03:27.350 --> 00:03:27.360 align:start position:0% 00:03:27.360 --> 00:03:29.990 align:start position:0% the<00:03:27.900> only<00:03:28.019> way<00:03:28.440> to<00:03:28.860> create<00:03:29.040> better<00:03:29.400> more 00:03:29.990 --> 00:03:30.000 align:start position:0% the only way to create better more 00:03:30.000 --> 00:03:32.630 align:start position:0% the only way to create better more usable<00:03:30.360> interfaces<00:03:31.200> is<00:03:31.620> by<00:03:31.920> exploring<00:03:32.400> and 00:03:32.630 --> 00:03:32.640 align:start position:0% usable interfaces is by exploring and 00:03:32.640 --> 00:03:34.309 align:start position:0% usable interfaces is by exploring and iterating<00:03:33.060> our<00:03:33.420> work 00:03:34.309 --> 00:03:34.319 align:start position:0% iterating our work 00:03:34.319 --> 00:03:36.470 align:start position:0% iterating our work we're<00:03:34.680> only<00:03:34.860> at<00:03:35.159> the<00:03:35.280> very<00:03:35.459> beginning<00:03:35.700> there 00:03:36.470 --> 00:03:36.480 align:start position:0% we're only at the very beginning there 00:03:36.480 --> 00:03:38.809 align:start position:0% we're only at the very beginning there are<00:03:36.780> many<00:03:37.200> design<00:03:37.500> Cycles<00:03:38.159> in<00:03:38.459> our<00:03:38.580> future 00:03:38.809 --> 00:03:38.819 align:start position:0% are many design Cycles in our future 00:03:38.819 --> 00:03:42.589 align:start position:0% are many design Cycles in our future which<00:03:39.659> to<00:03:39.840> me<00:03:39.959> is<00:03:40.140> super<00:03:40.379> exciting 00:03:42.589 --> 00:03:42.599 align:start position:0% which to me is super exciting 00:03:42.599 --> 00:03:46.430 align:start position:0% which to me is super exciting the<00:03:43.200> design<00:03:43.319> process<00:03:43.920> is<00:03:44.459> a<00:03:44.700> Hands-On<00:03:45.180> way<00:03:45.480> for 00:03:46.430 --> 00:03:46.440 align:start position:0% the design process is a Hands-On way for 00:03:46.440 --> 00:03:48.229 align:start position:0% the design process is a Hands-On way for anyone<00:03:47.099> to<00:03:47.400> learn 00:03:48.229 --> 00:03:48.239 align:start position:0% anyone to learn 00:03:48.239 --> 00:03:50.930 align:start position:0% anyone to learn on<00:03:48.840> my<00:03:49.019> team<00:03:49.200> contributors<00:03:49.980> from<00:03:50.400> all<00:03:50.700> kinds 00:03:50.930 --> 00:03:50.940 align:start position:0% on my team contributors from all kinds 00:03:50.940 --> 00:03:54.649 align:start position:0% on my team contributors from all kinds of<00:03:51.060> backgrounds<00:03:51.720> are<00:03:52.500> finding<00:03:52.920> alignment<00:03:53.659> by 00:03:54.649 --> 00:03:54.659 align:start position:0% of backgrounds are finding alignment by 00:03:54.659 --> 00:03:56.809 align:start position:0% of backgrounds are finding alignment by cycling<00:03:54.900> through<00:03:55.379> phases<00:03:55.920> of<00:03:56.220> Discovery 00:03:56.809 --> 00:03:56.819 align:start position:0% cycling through phases of Discovery 00:03:56.819 --> 00:03:58.449 align:start position:0% cycling through phases of Discovery problem<00:03:57.239> definition 00:03:58.449 --> 00:03:58.459 align:start position:0% problem definition 00:03:58.459 --> 00:04:01.250 align:start position:0% problem definition prototyping<00:03:59.459> and<00:03:59.700> testing 00:04:01.250 --> 00:04:01.260 align:start position:0% prototyping and testing 00:04:01.260 --> 00:04:03.110 align:start position:0% prototyping and testing together 00:04:03.110 --> 00:04:03.120 align:start position:0% together 00:04:03.120 --> 00:04:06.170 align:start position:0% together when<00:04:03.780> the<00:04:04.140> abstract<00:04:04.680> can<00:04:05.400> become<00:04:05.819> something 00:04:06.170 --> 00:04:06.180 align:start position:0% when the abstract can become something 00:04:06.180 --> 00:04:08.809 align:start position:0% when the abstract can become something physical<00:04:06.920> Concepts<00:04:07.920> can<00:04:08.159> sink<00:04:08.400> in<00:04:08.519> and 00:04:08.809 --> 00:04:08.819 align:start position:0% physical Concepts can sink in and 00:04:08.819 --> 00:04:10.670 align:start position:0% physical Concepts can sink in and Inspire<00:04:09.180> the<00:04:09.420> next<00:04:09.599> cycle 00:04:10.670 --> 00:04:10.680 align:start position:0% Inspire the next cycle 00:04:10.680 --> 00:04:12.050 align:start position:0% Inspire the next cycle the<00:04:11.040> more<00:04:11.159> that<00:04:11.280> we<00:04:11.459> understand<00:04:11.640> the 00:04:12.050 --> 00:04:12.060 align:start position:0% the more that we understand the 00:04:12.060 --> 00:04:14.149 align:start position:0% the more that we understand the protocols<00:04:12.599> that<00:04:12.840> we're<00:04:12.959> working<00:04:13.260> with<00:04:13.680> the 00:04:14.149 --> 00:04:14.159 align:start position:0% protocols that we're working with the 00:04:14.159 --> 00:04:16.189 align:start position:0% protocols that we're working with the easier<00:04:14.459> time<00:04:14.700> we<00:04:15.000> will<00:04:15.239> have<00:04:15.420> communicating 00:04:16.189 --> 00:04:16.199 align:start position:0% easier time we will have communicating 00:04:16.199 --> 00:04:17.750 align:start position:0% easier time we will have communicating their<00:04:16.560> value 00:04:17.750 --> 00:04:17.760 align:start position:0% their value 00:04:17.760 --> 00:04:20.030 align:start position:0% their value more<00:04:18.419> and<00:04:18.540> more<00:04:18.720> people<00:04:19.019> are<00:04:19.440> understanding 00:04:20.030 --> 00:04:20.040 align:start position:0% more and more people are understanding 00:04:20.040 --> 00:04:22.610 align:start position:0% more and more people are understanding how<00:04:20.280> our<00:04:20.400> information<00:04:20.639> is<00:04:21.239> collected<00:04:21.780> and<00:04:22.260> how 00:04:22.610 --> 00:04:22.620 align:start position:0% how our information is collected and how 00:04:22.620 --> 00:04:24.409 align:start position:0% how our information is collected and how our<00:04:22.740> data<00:04:23.100> is<00:04:23.160> used<00:04:23.340> to<00:04:23.639> influence<00:04:24.060> our 00:04:24.409 --> 00:04:24.419 align:start position:0% our data is used to influence our 00:04:24.419 --> 00:04:26.570 align:start position:0% our data is used to influence our thoughts<00:04:24.900> and<00:04:25.320> actions<00:04:25.860> but<00:04:26.400> they're 00:04:26.570 --> 00:04:26.580 align:start position:0% thoughts and actions but they're 00:04:26.580 --> 00:04:28.430 align:start position:0% thoughts and actions but they're apathetic 00:04:28.430 --> 00:04:28.440 align:start position:0% apathetic 00:04:28.440 --> 00:04:33.409 align:start position:0% apathetic imagine<00:04:29.280> if<00:04:30.120> by<00:04:30.479> default<00:04:31.100> we<00:04:32.100> had<00:04:32.340> privacy<00:04:33.060> and 00:04:33.409 --> 00:04:33.419 align:start position:0% imagine if by default we had privacy and 00:04:33.419 --> 00:04:35.390 align:start position:0% imagine if by default we had privacy and anonymity<00:04:33.960> online 00:04:35.390 --> 00:04:35.400 align:start position:0% anonymity online 00:04:35.400 --> 00:04:37.550 align:start position:0% anonymity online If<00:04:35.940> people<00:04:36.120> could<00:04:36.419> make<00:04:36.720> an<00:04:36.960> informed 00:04:37.550 --> 00:04:37.560 align:start position:0% If people could make an informed 00:04:37.560 --> 00:04:40.430 align:start position:0% If people could make an informed decision<00:04:38.040> to<00:04:38.940> opt<00:04:39.180> out 00:04:40.430 --> 00:04:40.440 align:start position:0% decision to opt out 00:04:40.440 --> 00:04:42.469 align:start position:0% decision to opt out they<00:04:40.919> wouldn't<00:04:41.040> be<00:04:41.340> saying 00:04:42.469 --> 00:04:42.479 align:start position:0% they wouldn't be saying 00:04:42.479 --> 00:04:44.629 align:start position:0% they wouldn't be saying well<00:04:42.900> they<00:04:43.080> have<00:04:43.259> all<00:04:43.380> my<00:04:43.560> data<00:04:43.860> anyway<00:04:44.040> what 00:04:44.629 --> 00:04:44.639 align:start position:0% well they have all my data anyway what 00:04:44.639 --> 00:04:46.670 align:start position:0% well they have all my data anyway what can<00:04:44.820> I<00:04:45.000> do 00:04:46.670 --> 00:04:46.680 align:start position:0% can I do 00:04:46.680 --> 00:04:49.070 align:start position:0% can I do instead<00:04:47.340> of<00:04:47.460> creating<00:04:48.080> extractive 00:04:49.070 --> 00:04:49.080 align:start position:0% instead of creating extractive 00:04:49.080 --> 00:04:52.670 align:start position:0% instead of creating extractive applications<00:04:49.800> that<00:04:50.460> use<00:04:51.000> users<00:04:51.720> we<00:04:52.560> can 00:04:52.670 --> 00:04:52.680 align:start position:0% applications that use users we can 00:04:52.680 --> 00:04:54.830 align:start position:0% applications that use users we can choose<00:04:52.979> to<00:04:53.340> design<00:04:53.840> participatory 00:04:54.830 --> 00:04:54.840 align:start position:0% choose to design participatory 00:04:54.840 --> 00:04:58.129 align:start position:0% choose to design participatory environments<00:04:56.100> where<00:04:56.639> people<00:04:56.880> consent<00:04:57.600> to<00:04:57.780> how 00:04:58.129 --> 00:04:58.139 align:start position:0% environments where people consent to how 00:04:58.139 --> 00:05:00.290 align:start position:0% environments where people consent to how much<00:04:58.259> personal<00:04:58.620> information<00:04:59.100> they<00:04:59.940> reveal 00:05:00.290 --> 00:05:00.300 align:start position:0% much personal information they reveal 00:05:00.300 --> 00:05:03.370 align:start position:0% much personal information they reveal about<00:05:00.540> themselves 00:05:03.370 --> 00:05:03.380 align:start position:0% 00:05:03.380 --> 00:05:06.170 align:start position:0% and<00:05:04.380> although<00:05:04.919> there<00:05:05.220> may<00:05:05.340> not<00:05:05.520> be<00:05:05.759> a<00:05:06.000> high 00:05:06.170 --> 00:05:06.180 align:start position:0% and although there may not be a high 00:05:06.180 --> 00:05:08.510 align:start position:0% and although there may not be a high demand<00:05:06.600> for<00:05:07.080> zero<00:05:07.560> knowledge<00:05:07.800> public<00:05:08.040> goods 00:05:08.510 --> 00:05:08.520 align:start position:0% demand for zero knowledge public goods 00:05:08.520 --> 00:05:11.030 align:start position:0% demand for zero knowledge public goods or<00:05:08.639> products<00:05:09.120> yet<00:05:09.360> I<00:05:10.259> believe<00:05:10.440> the<00:05:10.740> more<00:05:10.860> that 00:05:11.030 --> 00:05:11.040 align:start position:0% or products yet I believe the more that 00:05:11.040 --> 00:05:13.430 align:start position:0% or products yet I believe the more that we<00:05:11.220> design<00:05:11.580> the<00:05:12.419> more<00:05:12.540> people<00:05:12.780> will<00:05:13.020> come<00:05:13.199> to 00:05:13.430 --> 00:05:13.440 align:start position:0% we design the more people will come to 00:05:13.440 --> 00:05:15.650 align:start position:0% we design the more people will come to understand<00:05:13.680> the<00:05:14.220> magic<00:05:14.340> of<00:05:14.639> ZK<00:05:15.000> and<00:05:15.300> want<00:05:15.479> to 00:05:15.650 --> 00:05:15.660 align:start position:0% understand the magic of ZK and want to 00:05:15.660 --> 00:05:16.790 align:start position:0% understand the magic of ZK and want to use<00:05:15.840> it 00:05:16.790 --> 00:05:16.800 align:start position:0% use it 00:05:16.800 --> 00:05:19.310 align:start position:0% use it we're<00:05:17.280> still<00:05:17.400> in<00:05:17.580> really<00:05:17.820> early<00:05:18.000> stages<00:05:18.479> of 00:05:19.310 --> 00:05:19.320 align:start position:0% we're still in really early stages of 00:05:19.320 --> 00:05:20.990 align:start position:0% we're still in really early stages of research<00:05:19.680> and<00:05:19.800> Design 00:05:20.990 --> 00:05:21.000 align:start position:0% research and Design 00:05:21.000 --> 00:05:22.969 align:start position:0% research and Design the<00:05:21.419> experiences<00:05:21.900> we<00:05:22.199> create<00:05:22.380> will<00:05:22.680> become 00:05:22.969 --> 00:05:22.979 align:start position:0% the experiences we create will become 00:05:22.979 --> 00:05:25.610 align:start position:0% the experiences we create will become more<00:05:23.280> usable<00:05:23.699> more<00:05:24.419> accessible<00:05:24.900> the<00:05:25.440> more 00:05:25.610 --> 00:05:25.620 align:start position:0% more usable more accessible the more 00:05:25.620 --> 00:05:28.310 align:start position:0% more usable more accessible the more cycles<00:05:26.100> that<00:05:26.280> we<00:05:26.460> go<00:05:26.639> through<00:05:26.820> and<00:05:27.780> the<00:05:28.080> more 00:05:28.310 --> 00:05:28.320 align:start position:0% cycles that we go through and the more 00:05:28.320 --> 00:05:30.770 align:start position:0% cycles that we go through and the more people<00:05:28.620> that<00:05:29.100> we<00:05:29.340> can<00:05:29.520> talk<00:05:30.000> to<00:05:30.240> about<00:05:30.479> their 00:05:30.770 --> 00:05:30.780 align:start position:0% people that we can talk to about their 00:05:30.780 --> 00:05:32.510 align:start position:0% people that we can talk to about their experiences 00:05:32.510 --> 00:05:32.520 align:start position:0% experiences 00:05:32.520 --> 00:05:35.570 align:start position:0% experiences and<00:05:33.300> this<00:05:33.539> part's<00:05:33.840> really<00:05:34.020> cool<00:05:34.199> to<00:05:34.440> me<00:05:35.039> the 00:05:35.570 --> 00:05:35.580 align:start position:0% and this part's really cool to me the 00:05:35.580 --> 00:05:37.850 align:start position:0% and this part's really cool to me the better<00:05:35.699> the<00:05:36.060> experiences<00:05:36.600> are<00:05:36.960> the<00:05:37.740> more 00:05:37.850 --> 00:05:37.860 align:start position:0% better the experiences are the more 00:05:37.860 --> 00:05:40.490 align:start position:0% better the experiences are the more participants<00:05:38.580> there<00:05:39.000> will<00:05:39.240> be<00:05:39.479> which<00:05:40.259> will 00:05:40.490 --> 00:05:40.500 align:start position:0% participants there will be which will 00:05:40.500 --> 00:05:43.070 align:start position:0% participants there will be which will result<00:05:40.680> in<00:05:41.220> larger<00:05:41.759> sets<00:05:42.300> of<00:05:42.600> anonymous 00:05:43.070 --> 00:05:43.080 align:start position:0% result in larger sets of anonymous 00:05:43.080 --> 00:05:45.950 align:start position:0% result in larger sets of anonymous participants<00:05:43.919> and<00:05:44.759> increase<00:05:45.000> privacy<00:05:45.660> for 00:05:45.950 --> 00:05:45.960 align:start position:0% participants and increase privacy for 00:05:45.960 --> 00:05:47.510 align:start position:0% participants and increase privacy for everyone 00:05:47.510 --> 00:05:47.520 align:start position:0% everyone 00:05:47.520 --> 00:05:49.969 align:start position:0% everyone if<00:05:48.000> this<00:05:48.300> material<00:05:48.660> still<00:05:49.020> feels<00:05:49.320> conceptual 00:05:49.969 --> 00:05:49.979 align:start position:0% if this material still feels conceptual 00:05:49.979 --> 00:05:51.830 align:start position:0% if this material still feels conceptual and<00:05:50.220> you're<00:05:50.460> wondering<00:05:50.880> what<00:05:51.240> an<00:05:51.419> experience 00:05:51.830 --> 00:05:51.840 align:start position:0% and you're wondering what an experience 00:05:51.840 --> 00:05:53.810 align:start position:0% and you're wondering what an experience with<00:05:52.139> zero<00:05:52.500> knowledge<00:05:52.800> would<00:05:53.039> be<00:05:53.160> like<00:05:53.400> here's 00:05:53.810 --> 00:05:53.820 align:start position:0% with zero knowledge would be like here's 00:05:53.820 --> 00:05:55.730 align:start position:0% with zero knowledge would be like here's a<00:05:54.000> relevant<00:05:54.360> example 00:05:55.730 --> 00:05:55.740 align:start position:0% a relevant example 00:05:55.740 --> 00:05:57.650 align:start position:0% a relevant example say<00:05:56.100> you<00:05:56.400> want<00:05:56.460> to<00:05:56.639> anonymously<00:05:57.240> share 00:05:57.650 --> 00:05:57.660 align:start position:0% say you want to anonymously share 00:05:57.660 --> 00:06:00.350 align:start position:0% say you want to anonymously share feedback<00:05:58.139> about<00:05:58.620> this<00:05:59.039> event<00:05:59.220> with<00:06:00.000> the<00:06:00.180> event 00:06:00.350 --> 00:06:00.360 align:start position:0% feedback about this event with the event 00:06:00.360 --> 00:06:01.850 align:start position:0% feedback about this event with the event organizers 00:06:01.850 --> 00:06:01.860 align:start position:0% organizers 00:06:01.860 --> 00:06:05.150 align:start position:0% organizers but<00:06:02.460> in<00:06:02.639> order<00:06:02.820> to<00:06:03.120> do<00:06:03.300> so<00:06:03.479> you<00:06:04.199> have<00:06:04.380> to<00:06:04.740> prove 00:06:05.150 --> 00:06:05.160 align:start position:0% but in order to do so you have to prove 00:06:05.160 --> 00:06:07.730 align:start position:0% but in order to do so you have to prove that<00:06:05.580> you<00:06:05.759> attended<00:06:06.180> the<00:06:06.419> event 00:06:07.730 --> 00:06:07.740 align:start position:0% that you attended the event 00:06:07.740 --> 00:06:11.810 align:start position:0% that you attended the event an<00:06:08.400> app<00:06:08.580> built<00:06:08.940> with<00:06:09.060> ZK<00:06:09.720> could<00:06:10.680> allow<00:06:11.160> you<00:06:11.340> to 00:06:11.810 --> 00:06:11.820 align:start position:0% an app built with ZK could allow you to 00:06:11.820 --> 00:06:13.790 align:start position:0% an app built with ZK could allow you to prove<00:06:12.060> that<00:06:12.180> you<00:06:12.479> did<00:06:12.660> in<00:06:12.900> fact<00:06:13.080> attend<00:06:13.560> the 00:06:13.790 --> 00:06:13.800 align:start position:0% prove that you did in fact attend the 00:06:13.800 --> 00:06:15.129 align:start position:0% prove that you did in fact attend the event 00:06:15.129 --> 00:06:15.139 align:start position:0% event 00:06:15.139 --> 00:06:18.710 align:start position:0% event without<00:06:16.139> revealing<00:06:16.860> Who<00:06:17.280> You<00:06:17.639> Are 00:06:18.710 --> 00:06:18.720 align:start position:0% without revealing Who You Are 00:06:18.720 --> 00:06:20.749 align:start position:0% without revealing Who You Are giving<00:06:19.080> you<00:06:19.320> the<00:06:19.500> opportunity<00:06:19.919> to<00:06:20.220> truly 00:06:20.749 --> 00:06:20.759 align:start position:0% giving you the opportunity to truly 00:06:20.759 --> 00:06:24.409 align:start position:0% giving you the opportunity to truly share<00:06:21.060> feedback<00:06:21.539> anonymously 00:06:24.409 --> 00:06:24.419 align:start position:0% 00:06:24.419 --> 00:06:26.749 align:start position:0% can<00:06:24.960> you<00:06:25.080> think<00:06:25.319> of<00:06:25.620> other<00:06:25.979> instances<00:06:26.460> where 00:06:26.749 --> 00:06:26.759 align:start position:0% can you think of other instances where 00:06:26.759 --> 00:06:28.189 align:start position:0% can you think of other instances where you<00:06:26.940> might<00:06:27.120> want<00:06:27.300> to<00:06:27.419> prove<00:06:27.780> that<00:06:27.960> something 00:06:28.189 --> 00:06:28.199 align:start position:0% you might want to prove that something 00:06:28.199 --> 00:06:30.590 align:start position:0% you might want to prove that something is<00:06:28.500> true<00:06:28.800> without<00:06:29.160> revealing<00:06:29.940> additional 00:06:30.590 --> 00:06:30.600 align:start position:0% is true without revealing additional 00:06:30.600 --> 00:06:32.930 align:start position:0% is true without revealing additional personal<00:06:30.960> information 00:06:32.930 --> 00:06:32.940 align:start position:0% personal information 00:06:32.940 --> 00:06:35.689 align:start position:0% personal information a<00:06:33.479> few<00:06:33.600> other<00:06:33.840> ones<00:06:34.259> I've<00:06:34.919> also<00:06:35.220> heard<00:06:35.400> are 00:06:35.689 --> 00:06:35.699 align:start position:0% a few other ones I've also heard are 00:06:35.699 --> 00:06:37.809 align:start position:0% a few other ones I've also heard are speaking<00:06:36.180> out<00:06:36.360> against<00:06:36.539> systems<00:06:37.199> of<00:06:37.380> power 00:06:37.809 --> 00:06:37.819 align:start position:0% speaking out against systems of power 00:06:37.819 --> 00:06:40.490 align:start position:0% speaking out against systems of power and<00:06:38.819> engaging<00:06:39.300> in<00:06:39.720> conversation<00:06:40.199> and 00:06:40.490 --> 00:06:40.500 align:start position:0% and engaging in conversation and 00:06:40.500 --> 00:06:41.629 align:start position:0% and engaging in conversation and discourse 00:06:41.629 --> 00:06:41.639 align:start position:0% discourse 00:06:41.639 --> 00:06:43.730 align:start position:0% discourse so<00:06:42.180> a<00:06:42.300> lot<00:06:42.419> of<00:06:42.539> our<00:06:42.660> protocols<00:06:43.199> have<00:06:43.440> the 00:06:43.730 --> 00:06:43.740 align:start position:0% so a lot of our protocols have the 00:06:43.740 --> 00:06:45.409 align:start position:0% so a lot of our protocols have the potential<00:06:44.100> to<00:06:44.280> structure<00:06:44.759> or<00:06:44.940> manage 00:06:45.409 --> 00:06:45.419 align:start position:0% potential to structure or manage 00:06:45.419 --> 00:06:47.870 align:start position:0% potential to structure or manage Anonymous<00:06:46.319> or<00:06:46.560> private<00:06:46.979> environments<00:06:47.580> for 00:06:47.870 --> 00:06:47.880 align:start position:0% Anonymous or private environments for 00:06:47.880 --> 00:06:51.170 align:start position:0% Anonymous or private environments for these<00:06:48.180> purposes 00:06:51.170 --> 00:06:51.180 align:start position:0% 00:06:51.180 --> 00:06:53.809 align:start position:0% there<00:06:52.020> are<00:06:52.139> plenty<00:06:52.560> of<00:06:52.860> challenges<00:06:53.460> that 00:06:53.809 --> 00:06:53.819 align:start position:0% there are plenty of challenges that 00:06:53.819 --> 00:06:56.390 align:start position:0% there are plenty of challenges that arise<00:06:54.120> when<00:06:54.419> designing<00:06:54.840> ZK<00:06:55.259> apps 00:06:56.390 --> 00:06:56.400 align:start position:0% arise when designing ZK apps 00:06:56.400 --> 00:06:59.809 align:start position:0% arise when designing ZK apps we<00:06:57.000> like<00:06:57.180> to<00:06:57.360> use<00:06:57.600> how<00:06:57.900> might<00:06:58.139> we<00:06:58.380> questions<00:06:58.819> to 00:06:59.809 --> 00:06:59.819 align:start position:0% we like to use how might we questions to 00:06:59.819 --> 00:07:02.150 align:start position:0% we like to use how might we questions to help<00:07:00.060> us<00:07:00.240> explore<00:07:00.660> problem<00:07:01.080> spaces<00:07:01.800> without 00:07:02.150 --> 00:07:02.160 align:start position:0% help us explore problem spaces without 00:07:02.160 --> 00:07:05.150 align:start position:0% help us explore problem spaces without immediately<00:07:03.120> jumping<00:07:03.660> to<00:07:03.900> Solutions 00:07:05.150 --> 00:07:05.160 align:start position:0% immediately jumping to Solutions 00:07:05.160 --> 00:07:07.189 align:start position:0% immediately jumping to Solutions so<00:07:05.520> I'd<00:07:05.699> like<00:07:05.819> to<00:07:06.000> share<00:07:06.300> some<00:07:06.479> of<00:07:06.660> those<00:07:06.780> with 00:07:07.189 --> 00:07:07.199 align:start position:0% so I'd like to share some of those with 00:07:07.199 --> 00:07:09.590 align:start position:0% so I'd like to share some of those with you 00:07:09.590 --> 00:07:09.600 align:start position:0% 00:07:09.600 --> 00:07:11.570 align:start position:0% some<00:07:10.020> of<00:07:10.139> our<00:07:10.259> challenges<00:07:10.680> reframe<00:07:11.340> does<00:07:11.460> help 00:07:11.570 --> 00:07:11.580 align:start position:0% some of our challenges reframe does help 00:07:11.580 --> 00:07:14.090 align:start position:0% some of our challenges reframe does help mightweight<00:07:12.120> statements 00:07:14.090 --> 00:07:14.100 align:start position:0% mightweight statements 00:07:14.100 --> 00:07:16.670 align:start position:0% mightweight statements how<00:07:14.580> might<00:07:14.759> we<00:07:14.940> balance<00:07:15.240> approachability<00:07:15.960> and 00:07:16.670 --> 00:07:16.680 align:start position:0% how might we balance approachability and 00:07:16.680 --> 00:07:18.290 align:start position:0% how might we balance approachability and transparency 00:07:18.290 --> 00:07:18.300 align:start position:0% transparency 00:07:18.300 --> 00:07:20.809 align:start position:0% transparency an<00:07:18.960> ever-present<00:07:19.680> challenge<00:07:20.099> that<00:07:20.699> we're 00:07:20.809 --> 00:07:20.819 align:start position:0% an ever-present challenge that we're 00:07:20.819 --> 00:07:22.670 align:start position:0% an ever-present challenge that we're facing<00:07:21.240> is<00:07:21.479> deciding<00:07:21.960> how<00:07:22.259> much<00:07:22.440> information 00:07:22.670 --> 00:07:22.680 align:start position:0% facing is deciding how much information 00:07:22.680 --> 00:07:26.150 align:start position:0% facing is deciding how much information to<00:07:23.220> share<00:07:23.520> in<00:07:23.880> our<00:07:24.060> apps<00:07:24.360> and<00:07:24.599> other<00:07:24.780> resources 00:07:26.150 --> 00:07:26.160 align:start position:0% to share in our apps and other resources 00:07:26.160 --> 00:07:29.270 align:start position:0% to share in our apps and other resources we<00:07:26.699> want<00:07:26.880> to<00:07:27.000> be<00:07:27.240> true<00:07:27.500> transparent<00:07:28.500> and<00:07:29.099> help 00:07:29.270 --> 00:07:29.280 align:start position:0% we want to be true transparent and help 00:07:29.280 --> 00:07:32.629 align:start position:0% we want to be true transparent and help curious<00:07:29.759> individuals<00:07:30.479> learn<00:07:31.020> more<00:07:31.979> about<00:07:32.160> CK 00:07:32.629 --> 00:07:32.639 align:start position:0% curious individuals learn more about CK 00:07:32.639 --> 00:07:35.270 align:start position:0% curious individuals learn more about CK products<00:07:33.120> while<00:07:33.479> they're<00:07:33.720> using<00:07:34.020> them<00:07:34.199> but<00:07:34.979> we 00:07:35.270 --> 00:07:35.280 align:start position:0% products while they're using them but we 00:07:35.280 --> 00:07:37.850 align:start position:0% products while they're using them but we also<00:07:35.639> want<00:07:35.880> to<00:07:36.120> avoid<00:07:36.599> overwhelm<00:07:37.500> and 00:07:37.850 --> 00:07:37.860 align:start position:0% also want to avoid overwhelm and 00:07:37.860 --> 00:07:41.330 align:start position:0% also want to avoid overwhelm and cognitive<00:07:38.639> overload 00:07:41.330 --> 00:07:41.340 align:start position:0% 00:07:41.340 --> 00:07:44.390 align:start position:0% here's<00:07:42.060> some<00:07:42.240> screenshots<00:07:42.780> from<00:07:43.440> our<00:07:43.740> zko 00:07:44.390 --> 00:07:44.400 align:start position:0% here's some screenshots from our zko 00:07:44.400 --> 00:07:48.650 align:start position:0% here's some screenshots from our zko Prue<00:07:44.960> a<00:07:45.960> private<00:07:46.860> wallet<00:07:47.639> this<00:07:47.940> is<00:07:48.060> a<00:07:48.240> browser 00:07:48.650 --> 00:07:48.660 align:start position:0% Prue a private wallet this is a browser 00:07:48.660 --> 00:07:52.189 align:start position:0% Prue a private wallet this is a browser extension<00:07:49.340> my<00:07:50.340> teammate<00:07:50.639> bionder<00:07:51.360> came<00:07:52.020> up 00:07:52.189 --> 00:07:52.199 align:start position:0% extension my teammate bionder came up 00:07:52.199 --> 00:07:54.650 align:start position:0% extension my teammate bionder came up with<00:07:52.440> these<00:07:52.740> designs<00:07:53.340> and<00:07:54.000> I<00:07:54.120> included<00:07:54.479> them 00:07:54.650 --> 00:07:54.660 align:start position:0% with these designs and I included them 00:07:54.660 --> 00:07:56.029 align:start position:0% with these designs and I included them because<00:07:54.840> I<00:07:55.080> think<00:07:55.199> they're<00:07:55.440> a<00:07:55.620> really<00:07:55.740> nice 00:07:56.029 --> 00:07:56.039 align:start position:0% because I think they're a really nice 00:07:56.039 --> 00:07:58.610 align:start position:0% because I think they're a really nice example<00:07:56.580> of<00:07:56.699> progressive<00:07:57.360> disclosure 00:07:58.610 --> 00:07:58.620 align:start position:0% example of progressive disclosure 00:07:58.620 --> 00:08:01.610 align:start position:0% example of progressive disclosure where<00:07:59.520> users<00:08:00.060> land<00:08:00.479> on<00:08:00.720> the<00:08:00.960> primary<00:08:01.319> screen 00:08:01.610 --> 00:08:01.620 align:start position:0% where users land on the primary screen 00:08:01.620 --> 00:08:04.249 align:start position:0% where users land on the primary screen that's<00:08:02.099> on<00:08:02.400> the<00:08:02.699> left 00:08:04.249 --> 00:08:04.259 align:start position:0% that's on the left 00:08:04.259 --> 00:08:05.570 align:start position:0% that's on the left and 00:08:05.570 --> 00:08:05.580 align:start position:0% and 00:08:05.580 --> 00:08:08.409 align:start position:0% and they<00:08:06.180> just<00:08:06.479> see<00:08:06.780> the<00:08:07.199> tokens<00:08:07.560> in<00:08:07.800> their<00:08:07.979> wallet 00:08:08.409 --> 00:08:08.419 align:start position:0% they just see the tokens in their wallet 00:08:08.419 --> 00:08:11.570 align:start position:0% they just see the tokens in their wallet when<00:08:09.419> they<00:08:09.720> want<00:08:10.020> to 00:08:11.570 --> 00:08:11.580 align:start position:0% when they want to 00:08:11.580 --> 00:08:13.610 align:start position:0% when they want to get<00:08:12.060> more<00:08:12.300> information<00:08:12.539> about<00:08:13.020> a<00:08:13.319> specific 00:08:13.610 --> 00:08:13.620 align:start position:0% get more information about a specific 00:08:13.620 --> 00:08:15.469 align:start position:0% get more information about a specific token<00:08:14.099> they<00:08:14.639> can 00:08:15.469 --> 00:08:15.479 align:start position:0% token they can 00:08:15.479 --> 00:08:17.809 align:start position:0% token they can click<00:08:15.960> the<00:08:16.139> Chevron<00:08:16.680> to<00:08:17.220> open<00:08:17.400> up<00:08:17.580> this 00:08:17.809 --> 00:08:17.819 align:start position:0% click the Chevron to open up this 00:08:17.819 --> 00:08:19.850 align:start position:0% click the Chevron to open up this secondary<00:08:18.240> window<00:08:18.539> where<00:08:19.319> you<00:08:19.440> see<00:08:19.620> more 00:08:19.850 --> 00:08:19.860 align:start position:0% secondary window where you see more 00:08:19.860 --> 00:08:22.850 align:start position:0% secondary window where you see more information<00:08:20.099> about<00:08:20.460> the<00:08:20.639> track<00:08:20.879> transactions 00:08:22.850 --> 00:08:22.860 align:start position:0% information about the track transactions 00:08:22.860 --> 00:08:25.610 align:start position:0% information about the track transactions and<00:08:23.460> also<00:08:23.699> like<00:08:24.000> the<00:08:24.240> full<00:08:24.419> functions<00:08:25.020> of<00:08:25.440> that 00:08:25.610 --> 00:08:25.620 align:start position:0% and also like the full functions of that 00:08:25.620 --> 00:08:27.830 align:start position:0% and also like the full functions of that app<00:08:25.800> how<00:08:26.520> might<00:08:26.699> we<00:08:26.879> give<00:08:27.000> users<00:08:27.360> the<00:08:27.539> freedom 00:08:27.830 --> 00:08:27.840 align:start position:0% app how might we give users the freedom 00:08:27.840 --> 00:08:29.930 align:start position:0% app how might we give users the freedom to<00:08:28.020> choose<00:08:28.319> how<00:08:28.800> much<00:08:28.979> they<00:08:29.340> reveal<00:08:29.699> about 00:08:29.930 --> 00:08:29.940 align:start position:0% to choose how much they reveal about 00:08:29.940 --> 00:08:31.550 align:start position:0% to choose how much they reveal about themselves 00:08:31.550 --> 00:08:31.560 align:start position:0% themselves 00:08:31.560 --> 00:08:34.130 align:start position:0% themselves because<00:08:32.039> ZK<00:08:32.580> apps<00:08:33.060> give<00:08:33.300> us<00:08:33.479> Anonymous 00:08:34.130 --> 00:08:34.140 align:start position:0% because ZK apps give us Anonymous 00:08:34.140 --> 00:08:37.310 align:start position:0% because ZK apps give us Anonymous identities<00:08:34.740> it's<00:08:35.219> up<00:08:35.459> to<00:08:35.640> us<00:08:35.820> to<00:08:36.240> preserve<00:08:36.779> or 00:08:37.310 --> 00:08:37.320 align:start position:0% identities it's up to us to preserve or 00:08:37.320 --> 00:08:39.409 align:start position:0% identities it's up to us to preserve or break<00:08:37.560> the<00:08:37.919> level<00:08:38.099> of<00:08:38.339> anonymity<00:08:38.880> that<00:08:39.300> we 00:08:39.409 --> 00:08:39.419 align:start position:0% break the level of anonymity that we 00:08:39.419 --> 00:08:40.730 align:start position:0% break the level of anonymity that we start<00:08:39.659> with 00:08:40.730 --> 00:08:40.740 align:start position:0% start with 00:08:40.740 --> 00:08:43.190 align:start position:0% start with when<00:08:41.219> we're<00:08:41.399> Anonymous<00:08:41.880> our<00:08:42.479> identity<00:08:42.959> is 00:08:43.190 --> 00:08:43.200 align:start position:0% when we're Anonymous our identity is 00:08:43.200 --> 00:08:46.790 align:start position:0% when we're Anonymous our identity is unknown<00:08:43.620> but<00:08:44.039> our<00:08:44.279> actions<00:08:44.760> are<00:08:45.120> public 00:08:46.790 --> 00:08:46.800 align:start position:0% unknown but our actions are public 00:08:46.800 --> 00:08:50.090 align:start position:0% unknown but our actions are public Trails<00:08:47.279> of<00:08:47.399> actions<00:08:48.000> we<00:08:48.779> have<00:08:48.959> taken<00:08:49.380> can<00:08:49.920> be 00:08:50.090 --> 00:08:50.100 align:start position:0% Trails of actions we have taken can be 00:08:50.100 --> 00:08:52.790 align:start position:0% Trails of actions we have taken can be Clues<00:08:50.519> to<00:08:50.820> our<00:08:51.060> real<00:08:51.240> identities 00:08:52.790 --> 00:08:52.800 align:start position:0% Clues to our real identities 00:08:52.800 --> 00:08:55.790 align:start position:0% Clues to our real identities ZK<00:08:53.339> apps<00:08:53.760> can<00:08:53.940> expose<00:08:54.480> you<00:08:54.720> to<00:08:54.959> the<00:08:55.140> idea<00:08:55.440> of 00:08:55.790 --> 00:08:55.800 align:start position:0% ZK apps can expose you to the idea of 00:08:55.800 --> 00:08:58.190 align:start position:0% ZK apps can expose you to the idea of controlling<00:08:56.279> how<00:08:56.640> much<00:08:56.820> you<00:08:57.180> reveal 00:08:58.190 --> 00:08:58.200 align:start position:0% controlling how much you reveal 00:08:58.200 --> 00:09:01.550 align:start position:0% controlling how much you reveal or<00:08:58.860> when<00:08:59.100> you<00:08:59.279> reveal<00:08:59.700> it 00:09:01.550 --> 00:09:01.560 align:start position:0% or when you reveal it 00:09:01.560 --> 00:09:04.310 align:start position:0% or when you reveal it in<00:09:02.519> one<00:09:02.880> of<00:09:03.000> our<00:09:03.180> applications<00:09:03.720> in<00:09:04.080> Europe 00:09:04.310 --> 00:09:04.320 align:start position:0% in one of our applications in Europe 00:09:04.320 --> 00:09:06.290 align:start position:0% in one of our applications in Europe social 00:09:06.290 --> 00:09:06.300 align:start position:0% social 00:09:06.300 --> 00:09:09.769 align:start position:0% social um<00:09:06.620> this<00:09:07.620> user<00:09:08.100> in<00:09:08.700> this<00:09:08.820> screenshot<00:09:09.180> the<00:09:09.420> user 00:09:09.769 --> 00:09:09.779 align:start position:0% um this user in this screenshot the user 00:09:09.779 --> 00:09:12.230 align:start position:0% um this user in this screenshot the user is<00:09:09.899> about<00:09:10.140> to<00:09:10.500> post 00:09:12.230 --> 00:09:12.240 align:start position:0% is about to post 00:09:12.240 --> 00:09:14.389 align:start position:0% is about to post um<00:09:12.360> to<00:09:12.779> the<00:09:13.019> feed<00:09:13.200> of<00:09:13.500> an<00:09:13.680> anonymous<00:09:14.100> social 00:09:14.389 --> 00:09:14.399 align:start position:0% um to the feed of an anonymous social 00:09:14.399 --> 00:09:18.530 align:start position:0% um to the feed of an anonymous social app<00:09:14.760> you<00:09:15.720> can<00:09:15.839> see<00:09:15.959> that<00:09:16.260> they<00:09:16.500> have<00:09:16.800> 30<00:09:17.399> rep 00:09:18.530 --> 00:09:18.540 align:start position:0% app you can see that they have 30 rep 00:09:18.540 --> 00:09:22.009 align:start position:0% app you can see that they have 30 rep and<00:09:19.019> you<00:09:19.200> can<00:09:19.320> see<00:09:19.500> that<00:09:19.680> before<00:09:19.980> they<00:09:20.459> post 00:09:22.009 --> 00:09:22.019 align:start position:0% and you can see that before they post 00:09:22.019 --> 00:09:23.570 align:start position:0% and you can see that before they post um 00:09:23.570 --> 00:09:23.580 align:start position:0% um 00:09:23.580 --> 00:09:27.170 align:start position:0% um five<00:09:24.120> points<00:09:24.540> are<00:09:24.720> required<00:09:25.260> to<00:09:25.560> post 00:09:27.170 --> 00:09:27.180 align:start position:0% five points are required to post 00:09:27.180 --> 00:09:30.170 align:start position:0% five points are required to post and<00:09:27.600> they<00:09:27.779> can<00:09:27.959> choose<00:09:28.700> from<00:09:29.700> three<00:09:29.940> different 00:09:30.170 --> 00:09:30.180 align:start position:0% and they can choose from three different 00:09:30.180 --> 00:09:32.530 align:start position:0% and they can choose from three different personas 00:09:32.530 --> 00:09:32.540 align:start position:0% personas 00:09:32.540 --> 00:09:34.970 align:start position:0% personas and<00:09:33.540> they<00:09:33.779> can<00:09:33.959> also 00:09:34.970 --> 00:09:34.980 align:start position:0% and they can also 00:09:34.980 --> 00:09:37.670 align:start position:0% and they can also choose<00:09:35.580> on<00:09:35.880> a<00:09:36.060> sliding<00:09:36.420> scale<00:09:36.600> how<00:09:37.260> much<00:09:37.440> of 00:09:37.670 --> 00:09:37.680 align:start position:0% choose on a sliding scale how much of 00:09:37.680 --> 00:09:40.610 align:start position:0% choose on a sliding scale how much of their<00:09:37.800> rep<00:09:38.040> they<00:09:38.399> want<00:09:38.640> to<00:09:38.880> display<00:09:39.320> so<00:09:40.320> my 00:09:40.610 --> 00:09:40.620 align:start position:0% their rep they want to display so my 00:09:40.620 --> 00:09:43.790 align:start position:0% their rep they want to display so my teammate<00:09:40.920> chiali<00:09:41.779> created<00:09:42.779> this<00:09:43.260> sliding 00:09:43.790 --> 00:09:43.800 align:start position:0% teammate chiali created this sliding 00:09:43.800 --> 00:09:46.070 align:start position:0% teammate chiali created this sliding scale<00:09:44.100> model<00:09:44.399> for 00:09:46.070 --> 00:09:46.080 align:start position:0% scale model for 00:09:46.080 --> 00:09:48.590 align:start position:0% scale model for giving<00:09:46.620> people<00:09:46.920> that<00:09:47.279> opportunity 00:09:48.590 --> 00:09:48.600 align:start position:0% giving people that opportunity 00:09:48.600 --> 00:09:50.990 align:start position:0% giving people that opportunity to<00:09:49.140> decide<00:09:49.380> how<00:09:49.860> much 00:09:50.990 --> 00:09:51.000 align:start position:0% to decide how much 00:09:51.000 --> 00:09:53.090 align:start position:0% to decide how much to<00:09:51.420> reveal<00:09:51.720> about<00:09:51.899> the<00:09:52.140> reputation<00:09:52.560> they<00:09:52.920> have 00:09:53.090 --> 00:09:53.100 align:start position:0% to reveal about the reputation they have 00:09:53.100 --> 00:09:56.690 align:start position:0% to reveal about the reputation they have and<00:09:54.000> that's<00:09:54.660> like<00:09:55.019> a<00:09:55.800> cool<00:09:55.920> way<00:09:56.220> to<00:09:56.519> show 00:09:56.690 --> 00:09:56.700 align:start position:0% and that's like a cool way to show 00:09:56.700 --> 00:09:58.090 align:start position:0% and that's like a cool way to show people 00:09:58.090 --> 00:09:58.100 align:start position:0% people 00:09:58.100 --> 00:10:01.430 align:start position:0% people making<00:09:59.100> a<00:09:59.459> decision<00:09:59.820> about<00:10:00.300> how<00:10:01.019> they<00:10:01.140> want<00:10:01.320> to 00:10:01.430 --> 00:10:01.440 align:start position:0% making a decision about how they want to 00:10:01.440 --> 00:10:03.829 align:start position:0% making a decision about how they want to appear<00:10:01.800> in<00:10:01.980> this<00:10:02.220> group<00:10:02.519> how<00:10:03.360> might<00:10:03.480> we<00:10:03.660> craft 00:10:03.829 --> 00:10:03.839 align:start position:0% appear in this group how might we craft 00:10:03.839 --> 00:10:05.990 align:start position:0% appear in this group how might we craft environments<00:10:04.560> for<00:10:04.740> anonymous<00:10:05.160> users<00:10:05.640> to 00:10:05.990 --> 00:10:06.000 align:start position:0% environments for anonymous users to 00:10:06.000 --> 00:10:08.750 align:start position:0% environments for anonymous users to build<00:10:06.240> trust<00:10:07.019> with<00:10:07.200> one<00:10:07.380> another 00:10:08.750 --> 00:10:08.760 align:start position:0% build trust with one another 00:10:08.760 --> 00:10:10.970 align:start position:0% build trust with one another a<00:10:09.180> lot<00:10:09.300> of<00:10:09.420> people<00:10:09.540> ask<00:10:09.899> me<00:10:10.080> why<00:10:10.380> I<00:10:10.620> would<00:10:10.800> ever 00:10:10.970 --> 00:10:10.980 align:start position:0% a lot of people ask me why I would ever 00:10:10.980 --> 00:10:12.769 align:start position:0% a lot of people ask me why I would ever design<00:10:11.339> apps<00:10:11.940> where<00:10:12.120> people<00:10:12.300> can<00:10:12.600> be 00:10:12.769 --> 00:10:12.779 align:start position:0% design apps where people can be 00:10:12.779 --> 00:10:15.530 align:start position:0% design apps where people can be anonymous<00:10:13.260> online<00:10:13.560> because<00:10:14.399> they<00:10:15.000> feel<00:10:15.180> that 00:10:15.530 --> 00:10:15.540 align:start position:0% anonymous online because they feel that 00:10:15.540 --> 00:10:20.570 align:start position:0% anonymous online because they feel that a<00:10:15.860> non-environments<00:10:16.860> are<00:10:16.980> often<00:10:17.399> hostile 00:10:20.570 --> 00:10:20.580 align:start position:0% 00:10:20.580 --> 00:10:21.170 align:start position:0% um 00:10:21.170 --> 00:10:21.180 align:start position:0% um 00:10:21.180 --> 00:10:24.949 align:start position:0% um and<00:10:21.839> I<00:10:22.140> would<00:10:22.260> argue<00:10:22.740> that<00:10:23.600> anonymity<00:10:24.600> can 00:10:24.949 --> 00:10:24.959 align:start position:0% and I would argue that anonymity can 00:10:24.959 --> 00:10:28.070 align:start position:0% and I would argue that anonymity can also<00:10:25.200> create<00:10:25.440> places<00:10:26.040> where<00:10:26.580> everyone<00:10:26.940> has<00:10:27.720> an 00:10:28.070 --> 00:10:28.080 align:start position:0% also create places where everyone has an 00:10:28.080 --> 00:10:29.210 align:start position:0% also create places where everyone has an equal<00:10:28.200> voice 00:10:29.210 --> 00:10:29.220 align:start position:0% equal voice 00:10:29.220 --> 00:10:33.350 align:start position:0% equal voice and<00:10:29.760> they're<00:10:30.000> not<00:10:30.180> limited<00:10:30.720> by<00:10:31.220> potential<00:10:32.360> uh 00:10:33.350 --> 00:10:33.360 align:start position:0% and they're not limited by potential uh 00:10:33.360 --> 00:10:35.810 align:start position:0% and they're not limited by potential uh judgments<00:10:33.959> that<00:10:34.140> they<00:10:34.320> might<00:10:34.500> experience<00:10:35.040> if 00:10:35.810 --> 00:10:35.820 align:start position:0% judgments that they might experience if 00:10:35.820 --> 00:10:38.930 align:start position:0% judgments that they might experience if their<00:10:36.000> identity<00:10:36.480> was<00:10:36.720> revealed 00:10:38.930 --> 00:10:38.940 align:start position:0% their identity was revealed 00:10:38.940 --> 00:10:40.850 align:start position:0% their identity was revealed however<00:10:39.480> an<00:10:39.899> interesting<00:10:40.260> way<00:10:40.440> to<00:10:40.680> create 00:10:40.850 --> 00:10:40.860 align:start position:0% however an interesting way to create 00:10:40.860 --> 00:10:43.190 align:start position:0% however an interesting way to create trust<00:10:41.339> is<00:10:41.640> by<00:10:41.880> creating<00:10:42.180> groups<00:10:42.779> where 00:10:43.190 --> 00:10:43.200 align:start position:0% trust is by creating groups where 00:10:43.200 --> 00:10:45.949 align:start position:0% trust is by creating groups where everyone<00:10:43.440> has<00:10:43.800> to<00:10:43.980> prove<00:10:44.399> that<00:10:44.640> they<00:10:44.880> belong 00:10:45.949 --> 00:10:45.959 align:start position:0% everyone has to prove that they belong 00:10:45.959 --> 00:10:50.509 align:start position:0% everyone has to prove that they belong and<00:10:47.060> if<00:10:48.060> they<00:10:48.480> qualify<00:10:48.959> to<00:10:49.260> join<00:10:49.560> a<00:10:49.740> group<00:10:49.980> they 00:10:50.509 --> 00:10:50.519 align:start position:0% and if they qualify to join a group they 00:10:50.519 --> 00:10:52.069 align:start position:0% and if they qualify to join a group they can<00:10:50.640> trust<00:10:50.880> that<00:10:51.120> everyone<00:10:51.420> else<00:10:51.779> who 00:10:52.069 --> 00:10:52.079 align:start position:0% can trust that everyone else who 00:10:52.079 --> 00:10:54.170 align:start position:0% can trust that everyone else who qualified 00:10:54.170 --> 00:10:54.180 align:start position:0% qualified 00:10:54.180 --> 00:10:55.550 align:start position:0% qualified um<00:10:54.240> also<00:10:54.600> had<00:10:54.779> to<00:10:54.899> go<00:10:55.019> through<00:10:55.200> the<00:10:55.380> same 00:10:55.550 --> 00:10:55.560 align:start position:0% um also had to go through the same 00:10:55.560 --> 00:10:58.850 align:start position:0% um also had to go through the same qualification<00:10:56.160> process<00:10:56.959> this<00:10:57.959> per 00:10:58.850 --> 00:10:58.860 align:start position:0% qualification process this per 00:10:58.860 --> 00:10:59.569 align:start position:0% qualification process this per um 00:10:59.569 --> 00:10:59.579 align:start position:0% um 00:10:59.579 --> 00:11:02.509 align:start position:0% um project<00:11:00.120> that<00:11:00.480> we've<00:11:00.720> worked<00:11:00.959> on<00:11:01.079> interop<00:11:01.740> is 00:11:02.509 --> 00:11:02.519 align:start position:0% project that we've worked on interop is 00:11:02.519 --> 00:11:05.750 align:start position:0% project that we've worked on interop is a<00:11:03.060> good<00:11:03.120> example<00:11:03.660> of<00:11:04.260> bridging<00:11:04.920> reputation 00:11:05.750 --> 00:11:05.760 align:start position:0% a good example of bridging reputation 00:11:05.760 --> 00:11:09.470 align:start position:0% a good example of bridging reputation from<00:11:06.500> centralized<00:11:07.500> applications 00:11:09.470 --> 00:11:09.480 align:start position:0% from centralized applications 00:11:09.480 --> 00:11:10.190 align:start position:0% from centralized applications um 00:11:10.190 --> 00:11:10.200 align:start position:0% um 00:11:10.200 --> 00:11:13.730 align:start position:0% um to<00:11:10.740> your<00:11:11.420> on-chain<00:11:12.420> identity 00:11:13.730 --> 00:11:13.740 align:start position:0% to your on-chain identity 00:11:13.740 --> 00:11:16.250 align:start position:0% to your on-chain identity to<00:11:14.220> be<00:11:14.339> able<00:11:14.519> to 00:11:16.250 --> 00:11:16.260 align:start position:0% to be able to 00:11:16.260 --> 00:11:20.090 align:start position:0% to be able to prove<00:11:17.100> that<00:11:18.060> you<00:11:18.420> qualify<00:11:19.380> for<00:11:19.800> a<00:11:19.980> certain 00:11:20.090 --> 00:11:20.100 align:start position:0% prove that you qualify for a certain 00:11:20.100 --> 00:11:22.370 align:start position:0% prove that you qualify for a certain group<00:11:20.339> with<00:11:20.700> other<00:11:20.940> people<00:11:21.180> so<00:11:22.019> in<00:11:22.200> this 00:11:22.370 --> 00:11:22.380 align:start position:0% group with other people so in this 00:11:22.380 --> 00:11:25.069 align:start position:0% group with other people so in this example<00:11:22.860> the<00:11:23.579> person<00:11:23.820> qualifies<00:11:24.480> to<00:11:24.779> be<00:11:24.899> a 00:11:25.069 --> 00:11:25.079 align:start position:0% example the person qualifies to be a 00:11:25.079 --> 00:11:27.889 align:start position:0% example the person qualifies to be a Twitter<00:11:25.200> Gold<00:11:25.620> Member<00:11:26.100> because<00:11:26.579> they<00:11:27.360> have<00:11:27.540> a 00:11:27.889 --> 00:11:27.899 align:start position:0% Twitter Gold Member because they have a 00:11:27.899 --> 00:11:31.730 align:start position:0% Twitter Gold Member because they have a certain<00:11:28.100> number<00:11:29.100> of<00:11:29.519> followers 00:11:31.730 --> 00:11:31.740 align:start position:0% certain number of followers 00:11:31.740 --> 00:11:33.290 align:start position:0% certain number of followers um<00:11:31.800> and<00:11:32.100> they<00:11:32.279> can<00:11:32.459> join 00:11:33.290 --> 00:11:33.300 align:start position:0% um and they can join 00:11:33.300 --> 00:11:35.690 align:start position:0% um and they can join how<00:11:33.779> might<00:11:33.899> we<00:11:34.079> represent<00:11:34.500> identity<00:11:35.160> in 00:11:35.690 --> 00:11:35.700 align:start position:0% how might we represent identity in 00:11:35.700 --> 00:11:38.630 align:start position:0% how might we represent identity in communities<00:11:36.240> of<00:11:36.660> anonymous<00:11:37.140> individuals 00:11:38.630 --> 00:11:38.640 align:start position:0% communities of anonymous individuals 00:11:38.640 --> 00:11:42.230 align:start position:0% communities of anonymous individuals if<00:11:39.060> a<00:11:39.240> non-environments<00:11:40.160> are<00:11:41.160> not<00:11:41.700> all<00:11:42.000> going 00:11:42.230 --> 00:11:42.240 align:start position:0% if a non-environments are not all going 00:11:42.240 --> 00:11:44.509 align:start position:0% if a non-environments are not all going to<00:11:42.600> necessarily<00:11:43.079> have<00:11:43.380> like<00:11:43.620> profile<00:11:44.160> pics 00:11:44.509 --> 00:11:44.519 align:start position:0% to necessarily have like profile pics 00:11:44.519 --> 00:11:48.110 align:start position:0% to necessarily have like profile pics and<00:11:44.880> user<00:11:45.360> bios<00:11:46.160> uh<00:11:47.160> what<00:11:47.579> will<00:11:47.820> the 00:11:48.110 --> 00:11:48.120 align:start position:0% and user bios uh what will the 00:11:48.120 --> 00:11:49.970 align:start position:0% and user bios uh what will the identities<00:11:48.600> look<00:11:48.959> like 00:11:49.970 --> 00:11:49.980 align:start position:0% identities look like 00:11:49.980 --> 00:11:52.190 align:start position:0% identities look like it's<00:11:50.579> fun<00:11:50.880> to<00:11:51.120> think<00:11:51.240> of<00:11:51.480> the<00:11:51.720> different<00:11:51.839> ways 00:11:52.190 --> 00:11:52.200 align:start position:0% it's fun to think of the different ways 00:11:52.200 --> 00:11:54.110 align:start position:0% it's fun to think of the different ways things<00:11:52.380> could<00:11:52.560> be<00:11:52.740> represented 00:11:54.110 --> 00:11:54.120 align:start position:0% things could be represented 00:11:54.120 --> 00:11:56.509 align:start position:0% things could be represented like<00:11:54.660> will<00:11:55.019> handles<00:11:55.560> always<00:11:55.860> be<00:11:56.100> the<00:11:56.339> same 00:11:56.509 --> 00:11:56.519 align:start position:0% like will handles always be the same 00:11:56.519 --> 00:11:59.210 align:start position:0% like will handles always be the same will<00:11:56.940> they<00:11:57.180> change<00:11:57.540> if<00:11:58.380> they<00:11:58.560> change<00:11:58.740> how 00:11:59.210 --> 00:11:59.220 align:start position:0% will they change if they change how 00:11:59.220 --> 00:12:00.250 align:start position:0% will they change if they change how often 00:12:00.250 --> 00:12:00.260 align:start position:0% often 00:12:00.260 --> 00:12:03.530 align:start position:0% often could<00:12:01.260> handles<00:12:01.740> instead<00:12:02.519> be<00:12:02.940> tied<00:12:03.300> to 00:12:03.530 --> 00:12:03.540 align:start position:0% could handles instead be tied to 00:12:03.540 --> 00:12:05.210 align:start position:0% could handles instead be tied to reputation 00:12:05.210 --> 00:12:05.220 align:start position:0% reputation 00:12:05.220 --> 00:12:09.650 align:start position:0% reputation my<00:12:06.000> teammate<00:12:06.360> sukino<00:12:07.339> created<00:12:08.339> skitter<00:12:09.180> this 00:12:09.650 --> 00:12:09.660 align:start position:0% my teammate sukino created skitter this 00:12:09.660 --> 00:12:12.530 align:start position:0% my teammate sukino created skitter this is<00:12:09.779> a<00:12:09.959> social<00:12:10.140> app<00:12:10.560> where 00:12:12.530 --> 00:12:12.540 align:start position:0% is a social app where 00:12:12.540 --> 00:12:15.769 align:start position:0% is a social app where um people<00:12:12.959> have<00:12:13.260> the<00:12:13.440> option<00:12:13.800> to<00:12:14.220> decide<00:12:14.779> how 00:12:15.769 --> 00:12:15.779 align:start position:0% um people have the option to decide how 00:12:15.779 --> 00:12:18.829 align:start position:0% um people have the option to decide how they<00:12:15.959> want<00:12:16.140> to<00:12:16.320> be<00:12:16.560> displayed<00:12:17.100> by<00:12:17.760> username<00:12:18.360> by 00:12:18.829 --> 00:12:18.839 align:start position:0% they want to be displayed by username by 00:12:18.839 --> 00:12:20.650 align:start position:0% they want to be displayed by username by their<00:12:19.019> ens<00:12:19.500> address 00:12:20.650 --> 00:12:20.660 align:start position:0% their ens address 00:12:20.660 --> 00:12:23.449 align:start position:0% their ens address or<00:12:21.660> saying<00:12:22.440> that<00:12:22.560> they're<00:12:22.740> a<00:12:22.920> member<00:12:23.160> of<00:12:23.279> a 00:12:23.449 --> 00:12:23.459 align:start position:0% or saying that they're a member of a 00:12:23.459 --> 00:12:25.610 align:start position:0% or saying that they're a member of a group<00:12:23.640> so<00:12:24.300> you<00:12:24.540> can<00:12:24.600> see<00:12:24.720> at<00:12:24.899> the<00:12:25.019> top<00:12:25.200> of<00:12:25.440> the 00:12:25.610 --> 00:12:25.620 align:start position:0% group so you can see at the top of the 00:12:25.620 --> 00:12:28.250 align:start position:0% group so you can see at the top of the screenshot<00:12:26.040> like<00:12:26.459> a<00:12:27.000> Tas<00:12:27.300> member<00:12:27.660> posted 00:12:28.250 --> 00:12:28.260 align:start position:0% screenshot like a Tas member posted 00:12:28.260 --> 00:12:31.310 align:start position:0% screenshot like a Tas member posted that's<00:12:29.160> someone<00:12:29.940> who<00:12:30.360> signed<00:12:30.720> up<00:12:30.779> for<00:12:31.079> our 00:12:31.310 --> 00:12:31.320 align:start position:0% that's someone who signed up for our 00:12:31.320 --> 00:12:34.310 align:start position:0% that's someone who signed up for our temporary<00:12:31.740> Anonymous<00:12:32.279> Zone<00:12:32.839> downstairs<00:12:33.839> so 00:12:34.310 --> 00:12:34.320 align:start position:0% temporary Anonymous Zone downstairs so 00:12:34.320 --> 00:12:37.130 align:start position:0% temporary Anonymous Zone downstairs so you<00:12:34.500> guys<00:12:34.560> should<00:12:34.740> all<00:12:34.860> check<00:12:35.040> it<00:12:35.220> out 00:12:37.130 --> 00:12:37.140 align:start position:0% you guys should all check it out 00:12:37.140 --> 00:12:37.730 align:start position:0% you guys should all check it out um 00:12:37.730 --> 00:12:37.740 align:start position:0% um 00:12:37.740 --> 00:12:40.250 align:start position:0% um and<00:12:38.339> then<00:12:38.459> they<00:12:38.700> were<00:12:38.820> able<00:12:39.060> to<00:12:39.360> take<00:12:40.019> their 00:12:40.250 --> 00:12:40.260 align:start position:0% and then they were able to take their 00:12:40.260 --> 00:12:42.110 align:start position:0% and then they were able to take their identity<00:12:40.620> from<00:12:40.920> that<00:12:41.100> app<00:12:41.279> and<00:12:41.640> use<00:12:41.760> it<00:12:41.940> in 00:12:42.110 --> 00:12:42.120 align:start position:0% identity from that app and use it in 00:12:42.120 --> 00:12:44.030 align:start position:0% identity from that app and use it in skitter 00:12:44.030 --> 00:12:44.040 align:start position:0% skitter 00:12:44.040 --> 00:12:47.150 align:start position:0% skitter and<00:12:44.820> say<00:12:45.180> like<00:12:45.480> yeah<00:12:45.779> I'm<00:12:46.019> a<00:12:46.200> non<00:12:46.380> but<00:12:46.680> I'm<00:12:46.860> also 00:12:47.150 --> 00:12:47.160 align:start position:0% and say like yeah I'm a non but I'm also 00:12:47.160 --> 00:12:48.949 align:start position:0% and say like yeah I'm a non but I'm also associated<00:12:47.639> with<00:12:47.940> this<00:12:48.120> group 00:12:48.949 --> 00:12:48.959 align:start position:0% associated with this group 00:12:48.959 --> 00:12:51.290 align:start position:0% associated with this group and<00:12:49.560> another<00:12:49.860> clever<00:12:50.279> thing<00:12:50.519> I<00:12:50.700> think<00:12:50.820> tsukino 00:12:51.290 --> 00:12:51.300 align:start position:0% and another clever thing I think tsukino 00:12:51.300 --> 00:12:53.449 align:start position:0% and another clever thing I think tsukino came<00:12:51.600> up<00:12:51.720> with<00:12:51.839> was 00:12:53.449 --> 00:12:53.459 align:start position:0% came up with was 00:12:53.459 --> 00:12:56.030 align:start position:0% came up with was um<00:12:53.519> saying<00:12:54.180> a<00:12:54.600> Twitter<00:12:54.720> user<00:12:55.139> with<00:12:55.260> 500<00:12:55.740> plus 00:12:56.030 --> 00:12:56.040 align:start position:0% um saying a Twitter user with 500 plus 00:12:56.040 --> 00:12:59.389 align:start position:0% um saying a Twitter user with 500 plus followers<00:12:56.760> said<00:12:57.720> XYZ 00:12:59.389 --> 00:12:59.399 align:start position:0% followers said XYZ 00:12:59.399 --> 00:13:00.949 align:start position:0% followers said XYZ but<00:12:59.820> what<00:13:00.000> gets<00:13:00.300> us<00:13:00.360> to<00:13:00.540> the<00:13:00.600> point<00:13:00.720> of 00:13:00.949 --> 00:13:00.959 align:start position:0% but what gets us to the point of 00:13:00.959 --> 00:13:02.750 align:start position:0% but what gets us to the point of creating<00:13:01.260> designs<00:13:01.800> that<00:13:01.980> address<00:13:02.160> these<00:13:02.579> hell 00:13:02.750 --> 00:13:02.760 align:start position:0% creating designs that address these hell 00:13:02.760 --> 00:13:04.490 align:start position:0% creating designs that address these hell might<00:13:03.000> way<00:13:03.180> statements 00:13:04.490 --> 00:13:04.500 align:start position:0% might way statements 00:13:04.500 --> 00:13:08.389 align:start position:0% might way statements I<00:13:05.220> believe<00:13:05.399> it's<00:13:06.360> environments<00:13:07.320> that<00:13:08.040> Foster 00:13:08.389 --> 00:13:08.399 align:start position:0% I believe it's environments that Foster 00:13:08.399 --> 00:13:10.790 align:start position:0% I believe it's environments that Foster collaboration<00:13:09.120> and<00:13:09.660> discovery 00:13:10.790 --> 00:13:10.800 align:start position:0% collaboration and discovery 00:13:10.800 --> 00:13:13.550 align:start position:0% collaboration and discovery and<00:13:11.519> processes<00:13:12.300> that<00:13:12.959> facilitate 00:13:13.550 --> 00:13:13.560 align:start position:0% and processes that facilitate 00:13:13.560 --> 00:13:16.430 align:start position:0% and processes that facilitate conversation 00:13:16.430 --> 00:13:16.440 align:start position:0% 00:13:16.440 --> 00:13:18.829 align:start position:0% as<00:13:17.100> much<00:13:17.220> as<00:13:17.399> design<00:13:17.639> is<00:13:18.000> about<00:13:18.180> creating 00:13:18.829 --> 00:13:18.839 align:start position:0% as much as design is about creating 00:13:18.839 --> 00:13:22.670 align:start position:0% as much as design is about creating objects<00:13:19.800> or<00:13:20.040> interfaces<00:13:21.019> that<00:13:22.019> people<00:13:22.380> can 00:13:22.670 --> 00:13:22.680 align:start position:0% objects or interfaces that people can 00:13:22.680 --> 00:13:24.710 align:start position:0% objects or interfaces that people can interact<00:13:23.100> with<00:13:23.279> it's<00:13:23.760> also<00:13:24.060> about<00:13:24.180> creating 00:13:24.710 --> 00:13:24.720 align:start position:0% interact with it's also about creating 00:13:24.720 --> 00:13:26.090 align:start position:0% interact with it's also about creating containers 00:13:26.090 --> 00:13:26.100 align:start position:0% containers 00:13:26.100 --> 00:13:27.889 align:start position:0% containers where<00:13:26.579> people<00:13:26.820> from<00:13:27.180> different<00:13:27.420> technical 00:13:27.889 --> 00:13:27.899 align:start position:0% where people from different technical 00:13:27.899 --> 00:13:30.949 align:start position:0% where people from different technical backgrounds<00:13:28.620> can<00:13:29.100> explore<00:13:29.519> ideas<00:13:29.940> and<00:13:30.660> find 00:13:30.949 --> 00:13:30.959 align:start position:0% backgrounds can explore ideas and find 00:13:30.959 --> 00:13:33.230 align:start position:0% backgrounds can explore ideas and find alignment 00:13:33.230 --> 00:13:33.240 align:start position:0% alignment 00:13:33.240 --> 00:13:36.290 align:start position:0% alignment we<00:13:33.660> create<00:13:33.839> containers<00:13:34.380> for<00:13:34.680> conversation<00:13:35.339> by 00:13:36.290 --> 00:13:36.300 align:start position:0% we create containers for conversation by 00:13:36.300 --> 00:13:38.690 align:start position:0% we create containers for conversation by frequently<00:13:36.779> hosting<00:13:37.320> workshops<00:13:38.100> in<00:13:38.399> digital 00:13:38.690 --> 00:13:38.700 align:start position:0% frequently hosting workshops in digital 00:13:38.700 --> 00:13:40.430 align:start position:0% frequently hosting workshops in digital whiteboards 00:13:40.430 --> 00:13:40.440 align:start position:0% whiteboards 00:13:40.440 --> 00:13:42.710 align:start position:0% whiteboards it's<00:13:41.040> in<00:13:41.220> these<00:13:41.399> workshops<00:13:41.940> that<00:13:42.180> people<00:13:42.420> from 00:13:42.710 --> 00:13:42.720 align:start position:0% it's in these workshops that people from 00:13:42.720 --> 00:13:44.690 align:start position:0% it's in these workshops that people from different<00:13:43.019> technical<00:13:43.500> backgrounds<00:13:44.160> can 00:13:44.690 --> 00:13:44.700 align:start position:0% different technical backgrounds can 00:13:44.700 --> 00:13:47.690 align:start position:0% different technical backgrounds can develop<00:13:45.600> common<00:13:46.139> language<00:13:46.560> and<00:13:47.459> create 00:13:47.690 --> 00:13:47.700 align:start position:0% develop common language and create 00:13:47.700 --> 00:13:50.269 align:start position:0% develop common language and create Bridges<00:13:48.660> between<00:13:49.139> their<00:13:49.620> domains<00:13:50.100> of 00:13:50.269 --> 00:13:50.279 align:start position:0% Bridges between their domains of 00:13:50.279 --> 00:13:52.910 align:start position:0% Bridges between their domains of understanding 00:13:52.910 --> 00:13:52.920 align:start position:0% understanding 00:13:52.920 --> 00:13:53.810 align:start position:0% understanding foreign 00:13:53.810 --> 00:13:53.820 align:start position:0% foreign 00:13:53.820 --> 00:13:56.090 align:start position:0% foreign here's<00:13:54.480> an<00:13:54.600> example<00:13:54.899> from<00:13:55.320> like<00:13:55.560> one<00:13:55.860> of<00:13:55.980> our 00:13:56.090 --> 00:13:56.100 align:start position:0% here's an example from like one of our 00:13:56.100 --> 00:13:58.850 align:start position:0% here's an example from like one of our fig<00:13:56.279> Jam<00:13:56.519> files 00:13:58.850 --> 00:13:58.860 align:start position:0% fig Jam files 00:13:58.860 --> 00:14:01.970 align:start position:0% fig Jam files um<00:13:58.980> I<00:13:59.880> am<00:14:00.540> obsessed<00:14:01.139> with<00:14:01.560> the<00:14:01.740> digital 00:14:01.970 --> 00:14:01.980 align:start position:0% um I am obsessed with the digital 00:14:01.980 --> 00:14:03.710 align:start position:0% um I am obsessed with the digital whiteboards 00:14:03.710 --> 00:14:03.720 align:start position:0% whiteboards 00:14:03.720 --> 00:14:05.870 align:start position:0% whiteboards um<00:14:03.779> I<00:14:04.260> feel<00:14:04.560> like<00:14:04.680> it's<00:14:04.860> so<00:14:05.100> cool<00:14:05.279> to<00:14:05.579> allow 00:14:05.870 --> 00:14:05.880 align:start position:0% um I feel like it's so cool to allow 00:14:05.880 --> 00:14:09.710 align:start position:0% um I feel like it's so cool to allow people<00:14:06.060> to<00:14:06.420> support<00:14:06.720> their<00:14:07.320> words<00:14:07.560> with 00:14:09.710 --> 00:14:09.720 align:start position:0% people to support their words with 00:14:09.720 --> 00:14:13.009 align:start position:0% people to support their words with um you<00:14:10.500> know<00:14:10.620> markers<00:14:11.459> sticky<00:14:12.000> notes 00:14:13.009 --> 00:14:13.019 align:start position:0% um you know markers sticky notes 00:14:13.019 --> 00:14:17.269 align:start position:0% um you know markers sticky notes shapes<00:14:13.820> cursor<00:14:14.820> gestures<00:14:15.300> or<00:14:15.720> chat<00:14:16.019> bubbles 00:14:17.269 --> 00:14:17.279 align:start position:0% shapes cursor gestures or chat bubbles 00:14:17.279 --> 00:14:20.030 align:start position:0% shapes cursor gestures or chat bubbles it's<00:14:17.940> way<00:14:18.300> more<00:14:18.480> comfy<00:14:18.899> spending<00:14:19.380> time<00:14:19.620> with 00:14:20.030 --> 00:14:20.040 align:start position:0% it's way more comfy spending time with 00:14:20.040 --> 00:14:21.829 align:start position:0% it's way more comfy spending time with unknowns 00:14:21.829 --> 00:14:21.839 align:start position:0% unknowns 00:14:21.839 --> 00:14:23.990 align:start position:0% unknowns when<00:14:22.440> everyone<00:14:22.680> can<00:14:23.100> visualize<00:14:23.700> the 00:14:23.990 --> 00:14:24.000 align:start position:0% when everyone can visualize the 00:14:24.000 --> 00:14:25.490 align:start position:0% when everyone can visualize the discussion 00:14:25.490 --> 00:14:25.500 align:start position:0% discussion 00:14:25.500 --> 00:14:27.949 align:start position:0% discussion and<00:14:26.100> I've<00:14:26.339> noticed<00:14:26.760> that<00:14:27.120> when<00:14:27.540> a<00:14:27.720> group<00:14:27.839> of 00:14:27.949 --> 00:14:27.959 align:start position:0% and I've noticed that when a group of 00:14:27.959 --> 00:14:30.370 align:start position:0% and I've noticed that when a group of people<00:14:28.260> are<00:14:28.680> all<00:14:28.860> looking<00:14:29.160> at<00:14:29.639> the<00:14:29.880> same<00:14:30.060> thing 00:14:30.370 --> 00:14:30.380 align:start position:0% people are all looking at the same thing 00:14:30.380 --> 00:14:33.650 align:start position:0% people are all looking at the same thing on<00:14:31.380> you<00:14:31.740> know<00:14:31.860> their<00:14:32.519> different<00:14:32.700> screens<00:14:33.180> and 00:14:33.650 --> 00:14:33.660 align:start position:0% on you know their different screens and 00:14:33.660 --> 00:14:36.350 align:start position:0% on you know their different screens and wherever<00:14:34.440> they<00:14:34.620> are<00:14:34.740> in<00:14:34.860> the<00:14:35.040> world<00:14:35.360> it's 00:14:36.350 --> 00:14:36.360 align:start position:0% wherever they are in the world it's 00:14:36.360 --> 00:14:40.129 align:start position:0% wherever they are in the world it's easier<00:14:36.720> to<00:14:37.079> identify<00:14:37.620> misunderstandings 00:14:40.129 --> 00:14:40.139 align:start position:0% easier to identify misunderstandings 00:14:40.139 --> 00:14:43.250 align:start position:0% easier to identify misunderstandings uh<00:14:40.740> with<00:14:40.980> the<00:14:41.160> visual<00:14:41.459> aids<00:14:42.000> in<00:14:42.360> this<00:14:42.660> created 00:14:43.250 --> 00:14:43.260 align:start position:0% uh with the visual aids in this created 00:14:43.260 --> 00:14:45.710 align:start position:0% uh with the visual aids in this created environment<00:14:43.920> there's<00:14:44.459> less<00:14:44.760> room<00:14:45.060> to<00:14:45.480> miss 00:14:45.710 --> 00:14:45.720 align:start position:0% environment there's less room to miss 00:14:45.720 --> 00:14:48.170 align:start position:0% environment there's less room to miss what<00:14:46.079> someone<00:14:46.320> said<00:14:46.740> or<00:14:47.519> to<00:14:47.760> not<00:14:47.940> understand 00:14:48.170 --> 00:14:48.180 align:start position:0% what someone said or to not understand 00:14:48.180 --> 00:14:49.970 align:start position:0% what someone said or to not understand what<00:14:48.779> they<00:14:48.959> mean 00:14:49.970 --> 00:14:49.980 align:start position:0% what they mean 00:14:49.980 --> 00:14:52.730 align:start position:0% what they mean we've<00:14:50.940> been<00:14:51.120> hosting<00:14:51.540> a<00:14:51.779> bunch<00:14:51.899> of<00:14:52.079> workshops 00:14:52.730 --> 00:14:52.740 align:start position:0% we've been hosting a bunch of workshops 00:14:52.740 --> 00:14:54.530 align:start position:0% we've been hosting a bunch of workshops and<00:14:53.160> so<00:14:53.279> I<00:14:53.399> wanted<00:14:53.579> to<00:14:53.760> share<00:14:53.940> with<00:14:54.120> you<00:14:54.240> some 00:14:54.530 --> 00:14:54.540 align:start position:0% and so I wanted to share with you some 00:14:54.540 --> 00:14:56.569 align:start position:0% and so I wanted to share with you some principles<00:14:54.959> that<00:14:55.440> have<00:14:55.740> helped<00:14:56.279> us<00:14:56.339> lead 00:14:56.569 --> 00:14:56.579 align:start position:0% principles that have helped us lead 00:14:56.579 --> 00:14:58.250 align:start position:0% principles that have helped us lead successful<00:14:57.180> ones 00:14:58.250 --> 00:14:58.260 align:start position:0% successful ones 00:14:58.260 --> 00:15:00.949 align:start position:0% successful ones uh<00:14:59.040> we're<00:14:59.399> opening<00:14:59.940> our<00:15:00.300> workshops<00:15:00.839> to 00:15:00.949 --> 00:15:00.959 align:start position:0% uh we're opening our workshops to 00:15:00.959 --> 00:15:04.670 align:start position:0% uh we're opening our workshops to teammates<00:15:01.320> from<00:15:01.680> various<00:15:02.160> uh<00:15:02.940> backgrounds<00:15:03.839> uh 00:15:04.670 --> 00:15:04.680 align:start position:0% teammates from various uh backgrounds uh 00:15:04.680 --> 00:15:06.829 align:start position:0% teammates from various uh backgrounds uh different<00:15:04.980> technical<00:15:05.459> backgrounds 00:15:06.829 --> 00:15:06.839 align:start position:0% different technical backgrounds 00:15:06.839 --> 00:15:08.870 align:start position:0% different technical backgrounds and<00:15:07.320> experience<00:15:07.740> levels 00:15:08.870 --> 00:15:08.880 align:start position:0% and experience levels 00:15:08.880 --> 00:15:11.629 align:start position:0% and experience levels we<00:15:09.300> offer<00:15:09.600> people<00:15:09.980> multiple<00:15:10.980> ways<00:15:11.399> to 00:15:11.629 --> 00:15:11.639 align:start position:0% we offer people multiple ways to 00:15:11.639 --> 00:15:13.250 align:start position:0% we offer people multiple ways to contribute<00:15:12.240> because<00:15:12.540> you<00:15:12.839> need<00:15:12.959> to<00:15:13.079> think 00:15:13.250 --> 00:15:13.260 align:start position:0% contribute because you need to think 00:15:13.260 --> 00:15:15.350 align:start position:0% contribute because you need to think about<00:15:13.440> different<00:15:14.100> personality<00:15:14.880> types 00:15:15.350 --> 00:15:15.360 align:start position:0% about different personality types 00:15:15.360 --> 00:15:18.290 align:start position:0% about different personality types different<00:15:15.779> technical<00:15:16.260> circumstances<00:15:17.300> not 00:15:18.290 --> 00:15:18.300 align:start position:0% different technical circumstances not 00:15:18.300 --> 00:15:20.509 align:start position:0% different technical circumstances not every<00:15:18.720> Workshop<00:15:19.440> should<00:15:19.800> just<00:15:19.980> be<00:15:20.220> people 00:15:20.509 --> 00:15:20.519 align:start position:0% every Workshop should just be people 00:15:20.519 --> 00:15:22.389 align:start position:0% every Workshop should just be people verbally 00:15:22.389 --> 00:15:22.399 align:start position:0% verbally 00:15:22.399 --> 00:15:25.129 align:start position:0% verbally exchanging<00:15:23.399> ideas<00:15:23.639> with<00:15:24.120> each<00:15:24.300> other<00:15:24.420> there 00:15:25.129 --> 00:15:25.139 align:start position:0% exchanging ideas with each other there 00:15:25.139 --> 00:15:27.710 align:start position:0% exchanging ideas with each other there needs<00:15:25.380> to<00:15:25.440> be<00:15:25.560> time<00:15:25.800> set<00:15:26.100> aside<00:15:26.399> for<00:15:26.880> writing 00:15:27.710 --> 00:15:27.720 align:start position:0% needs to be time set aside for writing 00:15:27.720 --> 00:15:32.090 align:start position:0% needs to be time set aside for writing or<00:15:28.560> drawing<00:15:28.980> as<00:15:29.220> well 00:15:32.090 --> 00:15:32.100 align:start position:0% 00:15:32.100 --> 00:15:34.189 align:start position:0% um<00:15:32.160> we<00:15:32.699> also<00:15:33.000> make<00:15:33.360> sure<00:15:33.480> we<00:15:33.720> always<00:15:33.839> have<00:15:34.079> a 00:15:34.189 --> 00:15:34.199 align:start position:0% um we also make sure we always have a 00:15:34.199 --> 00:15:36.769 align:start position:0% um we also make sure we always have a dedicated<00:15:34.560> notes<00:15:34.980> Taker<00:15:35.399> and<00:15:36.120> before<00:15:36.420> we 00:15:36.769 --> 00:15:36.779 align:start position:0% dedicated notes Taker and before we 00:15:36.779 --> 00:15:38.569 align:start position:0% dedicated notes Taker and before we synthesize<00:15:37.380> results<00:15:37.680> at<00:15:38.040> the<00:15:38.160> end<00:15:38.279> of<00:15:38.459> the 00:15:38.569 --> 00:15:38.579 align:start position:0% synthesize results at the end of the 00:15:38.579 --> 00:15:41.629 align:start position:0% synthesize results at the end of the workshop<00:15:39.019> we<00:15:40.019> preserve<00:15:40.620> what<00:15:40.980> we<00:15:41.160> had<00:15:41.339> like 00:15:41.629 --> 00:15:41.639 align:start position:0% workshop we preserve what we had like 00:15:41.639 --> 00:15:44.030 align:start position:0% workshop we preserve what we had like the<00:15:41.880> workshop<00:15:42.240> results<00:15:42.600> because<00:15:43.260> you<00:15:43.920> don't 00:15:44.030 --> 00:15:44.040 align:start position:0% the workshop results because you don't 00:15:44.040 --> 00:15:45.290 align:start position:0% the workshop results because you don't want<00:15:44.220> to<00:15:44.339> have<00:15:44.519> one<00:15:44.820> or<00:15:45.000> two<00:15:45.120> people 00:15:45.290 --> 00:15:45.300 align:start position:0% want to have one or two people 00:15:45.300 --> 00:15:48.650 align:start position:0% want to have one or two people synthesize<00:15:46.079> and<00:15:46.680> be<00:15:46.860> left<00:15:47.100> with<00:15:47.459> the<00:15:48.000> bias<00:15:48.360> of 00:15:48.650 --> 00:15:48.660 align:start position:0% synthesize and be left with the bias of 00:15:48.660 --> 00:15:50.990 align:start position:0% synthesize and be left with the bias of their<00:15:48.839> synthesis 00:15:50.990 --> 00:15:51.000 align:start position:0% their synthesis 00:15:51.000 --> 00:15:52.910 align:start position:0% their synthesis for<00:15:51.360> workshops<00:15:51.839> that<00:15:51.899> involve<00:15:52.440> a<00:15:52.680> lot<00:15:52.800> of 00:15:52.910 --> 00:15:52.920 align:start position:0% for workshops that involve a lot of 00:15:52.920 --> 00:15:55.490 align:start position:0% for workshops that involve a lot of people<00:15:53.040> and<00:15:53.459> have<00:15:53.639> a<00:15:53.820> tight<00:15:54.000> time<00:15:54.300> limit<00:15:54.600> I 00:15:55.490 --> 00:15:55.500 align:start position:0% people and have a tight time limit I 00:15:55.500 --> 00:15:57.829 align:start position:0% people and have a tight time limit I highly<00:15:56.100> suggest<00:15:56.579> collaborating<00:15:57.540> with 00:15:57.829 --> 00:15:57.839 align:start position:0% highly suggest collaborating with 00:15:57.839 --> 00:16:00.889 align:start position:0% highly suggest collaborating with someone<00:15:58.019> else<00:15:58.320> as<00:15:58.620> like<00:15:58.860> a<00:15:58.980> co-host 00:16:00.889 --> 00:16:00.899 align:start position:0% someone else as like a co-host 00:16:00.899 --> 00:16:01.490 align:start position:0% someone else as like a co-host um 00:16:01.490 --> 00:16:01.500 align:start position:0% um 00:16:01.500 --> 00:16:05.090 align:start position:0% um and<00:16:02.279> like<00:16:02.579> time<00:16:02.880> box<00:16:03.120> yourselves<00:16:03.720> and<00:16:04.680> have<00:16:04.920> a 00:16:05.090 --> 00:16:05.100 align:start position:0% and like time box yourselves and have a 00:16:05.100 --> 00:16:07.069 align:start position:0% and like time box yourselves and have a dress<00:16:05.279> rehearsal 00:16:07.069 --> 00:16:07.079 align:start position:0% dress rehearsal 00:16:07.079 --> 00:16:09.110 align:start position:0% dress rehearsal um<00:16:07.139> I<00:16:07.500> encourage<00:16:07.740> anyone<00:16:08.100> to<00:16:08.339> explore<00:16:08.579> using 00:16:09.110 --> 00:16:09.120 align:start position:0% um I encourage anyone to explore using 00:16:09.120 --> 00:16:11.750 align:start position:0% um I encourage anyone to explore using digital<00:16:09.420> whiteboards<00:16:10.260> in<00:16:11.040> this<00:16:11.220> way<00:16:11.339> and 00:16:11.750 --> 00:16:11.760 align:start position:0% digital whiteboards in this way and 00:16:11.760 --> 00:16:14.030 align:start position:0% digital whiteboards in this way and watch<00:16:11.880> how<00:16:12.120> it<00:16:12.240> gets<00:16:12.540> people<00:16:12.740> thinking<00:16:13.740> and 00:16:14.030 --> 00:16:14.040 align:start position:0% watch how it gets people thinking and 00:16:14.040 --> 00:16:15.710 align:start position:0% watch how it gets people thinking and talking<00:16:14.160> through<00:16:14.579> challenges 00:16:15.710 --> 00:16:15.720 align:start position:0% talking through challenges 00:16:15.720 --> 00:16:18.050 align:start position:0% talking through challenges for<00:16:16.440> us<00:16:16.560> we've<00:16:16.920> learned<00:16:17.100> a<00:16:17.220> lot<00:16:17.339> about<00:16:17.579> some<00:16:17.880> of 00:16:18.050 --> 00:16:18.060 align:start position:0% for us we've learned a lot about some of 00:16:18.060 --> 00:16:20.990 align:start position:0% for us we've learned a lot about some of our<00:16:18.180> protocols<00:16:18.839> like<00:16:19.079> zkl<00:16:19.740> Peru<00:16:20.100> semaphore 00:16:20.990 --> 00:16:21.000 align:start position:0% our protocols like zkl Peru semaphore 00:16:21.000 --> 00:16:23.150 align:start position:0% our protocols like zkl Peru semaphore and<00:16:21.300> unirub<00:16:21.959> through<00:16:22.500> these<00:16:22.860> digital 00:16:23.150 --> 00:16:23.160 align:start position:0% and unirub through these digital 00:16:23.160 --> 00:16:24.949 align:start position:0% and unirub through these digital whiteboard<00:16:23.639> sessions 00:16:24.949 --> 00:16:24.959 align:start position:0% whiteboard sessions 00:16:24.959 --> 00:16:28.730 align:start position:0% whiteboard sessions no<00:16:25.380> matter<00:16:25.500> how<00:16:25.920> Lo-Fi<00:16:26.779> visuals<00:16:27.779> help<00:16:28.320> us<00:16:28.440> move 00:16:28.730 --> 00:16:28.740 align:start position:0% no matter how Lo-Fi visuals help us move 00:16:28.740 --> 00:16:33.410 align:start position:0% no matter how Lo-Fi visuals help us move from<00:16:29.100> abstraction<00:16:29.699> to<00:16:30.180> something<00:16:30.420> concrete 00:16:33.410 --> 00:16:33.420 align:start position:0% 00:16:33.420 --> 00:16:35.389 align:start position:0% translating<00:16:34.320> a<00:16:34.620> protocol<00:16:34.860> into<00:16:35.160> an 00:16:35.389 --> 00:16:35.399 align:start position:0% translating a protocol into an 00:16:35.399 --> 00:16:37.430 align:start position:0% translating a protocol into an approachable<00:16:35.820> user<00:16:36.300> interface<00:16:36.720> takes<00:16:37.199> time 00:16:37.430 --> 00:16:37.440 align:start position:0% approachable user interface takes time 00:16:37.440 --> 00:16:40.009 align:start position:0% approachable user interface takes time it<00:16:38.279> takes<00:16:38.459> time<00:16:38.699> because<00:16:38.940> our<00:16:39.240> initial<00:16:39.600> means 00:16:40.009 --> 00:16:40.019 align:start position:0% it takes time because our initial means 00:16:40.019 --> 00:16:42.170 align:start position:0% it takes time because our initial means to<00:16:40.320> understanding<00:16:40.920> what<00:16:41.220> a<00:16:41.339> protocol<00:16:41.639> can<00:16:42.000> do 00:16:42.170 --> 00:16:42.180 align:start position:0% to understanding what a protocol can do 00:16:42.180 --> 00:16:45.710 align:start position:0% to understanding what a protocol can do usually<00:16:43.079> starts<00:16:43.560> with<00:16:43.980> documentation 00:16:45.710 --> 00:16:45.720 align:start position:0% usually starts with documentation 00:16:45.720 --> 00:16:47.930 align:start position:0% usually starts with documentation this<00:16:46.199> kind<00:16:46.320> of<00:16:46.500> writing<00:16:46.920> reflects<00:16:47.639> an 00:16:47.930 --> 00:16:47.940 align:start position:0% this kind of writing reflects an 00:16:47.940 --> 00:16:50.629 align:start position:0% this kind of writing reflects an implementation<00:16:48.660> model<00:16:49.279> necessary<00:16:50.279> for 00:16:50.629 --> 00:16:50.639 align:start position:0% implementation model necessary for 00:16:50.639 --> 00:16:52.730 align:start position:0% implementation model necessary for development<00:16:51.180> because<00:16:51.899> it<00:16:52.139> reflects<00:16:52.560> the 00:16:52.730 --> 00:16:52.740 align:start position:0% development because it reflects the 00:16:52.740 --> 00:16:56.569 align:start position:0% development because it reflects the technology<00:16:53.220> back<00:16:53.699> to<00:16:53.940> the<00:16:54.120> use<00:16:54.300> the<00:16:54.959> reader 00:16:56.569 --> 00:16:56.579 align:start position:0% technology back to the use the reader 00:16:56.579 --> 00:16:59.449 align:start position:0% technology back to the use the reader when<00:16:57.060> we<00:16:57.240> begin<00:16:57.360> designing<00:16:58.160> we<00:16:59.160> can<00:16:59.279> create 00:16:59.449 --> 00:16:59.459 align:start position:0% when we begin designing we can create 00:16:59.459 --> 00:17:01.310 align:start position:0% when we begin designing we can create other<00:16:59.820> kinds<00:17:00.240> of<00:17:00.300> models<00:17:00.779> to<00:17:01.139> better 00:17:01.310 --> 00:17:01.320 align:start position:0% other kinds of models to better 00:17:01.320 --> 00:17:03.650 align:start position:0% other kinds of models to better understand<00:17:01.699> protocols<00:17:02.699> that<00:17:03.240> instead 00:17:03.650 --> 00:17:03.660 align:start position:0% understand protocols that instead 00:17:03.660 --> 00:17:07.069 align:start position:0% understand protocols that instead reflect<00:17:04.199> familiarity<00:17:05.160> back<00:17:05.579> to<00:17:05.819> us 00:17:07.069 --> 00:17:07.079 align:start position:0% reflect familiarity back to us 00:17:07.079 --> 00:17:09.770 align:start position:0% reflect familiarity back to us uh<00:17:07.740> represented<00:17:08.400> models<00:17:08.880> reflect<00:17:09.480> the 00:17:09.770 --> 00:17:09.780 align:start position:0% uh represented models reflect the 00:17:09.780 --> 00:17:11.569 align:start position:0% uh represented models reflect the designer's<00:17:10.439> vision 00:17:11.569 --> 00:17:11.579 align:start position:0% designer's vision 00:17:11.579 --> 00:17:14.210 align:start position:0% designer's vision because<00:17:12.480> they<00:17:12.959> know<00:17:13.140> some<00:17:13.500> stuff<00:17:13.740> about<00:17:13.980> the 00:17:14.210 --> 00:17:14.220 align:start position:0% because they know some stuff about the 00:17:14.220 --> 00:17:17.090 align:start position:0% because they know some stuff about the protocol<00:17:14.520> and<00:17:15.240> mental<00:17:15.660> models<00:17:16.020> reflect<00:17:16.500> the 00:17:17.090 --> 00:17:17.100 align:start position:0% protocol and mental models reflect the 00:17:17.100 --> 00:17:18.710 align:start position:0% protocol and mental models reflect the user's<00:17:17.520> understanding 00:17:18.710 --> 00:17:18.720 align:start position:0% user's understanding 00:17:18.720 --> 00:17:20.750 align:start position:0% user's understanding they<00:17:19.319> know<00:17:19.439> nothing<00:17:19.740> about<00:17:20.280> the<00:17:20.520> protocol 00:17:20.750 --> 00:17:20.760 align:start position:0% they know nothing about the protocol 00:17:20.760 --> 00:17:22.850 align:start position:0% they know nothing about the protocol most<00:17:21.120> likely 00:17:22.850 --> 00:17:22.860 align:start position:0% most likely 00:17:22.860 --> 00:17:25.130 align:start position:0% most likely um<00:17:22.980> I<00:17:23.280> really<00:17:23.339> like<00:17:23.640> this<00:17:24.000> chart<00:17:24.360> for 00:17:25.130 --> 00:17:25.140 align:start position:0% um I really like this chart for 00:17:25.140 --> 00:17:27.590 align:start position:0% um I really like this chart for visualizing<00:17:25.799> the<00:17:26.160> difference<00:17:26.640> it's<00:17:27.059> adapted 00:17:27.590 --> 00:17:27.600 align:start position:0% visualizing the difference it's adapted 00:17:27.600 --> 00:17:30.370 align:start position:0% visualizing the difference it's adapted from<00:17:27.839> the<00:17:28.079> book<00:17:28.199> about<00:17:28.439> face 00:17:30.370 --> 00:17:30.380 align:start position:0% from the book about face 00:17:30.380 --> 00:17:33.710 align:start position:0% from the book about face there's<00:17:31.380> five<00:17:31.559> shapes<00:17:31.980> on<00:17:32.160> this<00:17:32.340> scale<00:17:32.720> can 00:17:33.710 --> 00:17:33.720 align:start position:0% there's five shapes on this scale can 00:17:33.720 --> 00:17:37.730 align:start position:0% there's five shapes on this scale can you<00:17:33.960> identify<00:17:34.679> any<00:17:35.039> of<00:17:35.220> the<00:17:35.400> shapes 00:17:37.730 --> 00:17:37.740 align:start position:0% you identify any of the shapes 00:17:37.740 --> 00:17:39.830 align:start position:0% you identify any of the shapes I<00:17:38.280> heard<00:17:38.400> Circle 00:17:39.830 --> 00:17:39.840 align:start position:0% I heard Circle 00:17:39.840 --> 00:17:43.250 align:start position:0% I heard Circle so<00:17:40.740> while<00:17:41.640> we<00:17:41.940> might 00:17:43.250 --> 00:17:43.260 align:start position:0% so while we might 00:17:43.260 --> 00:17:45.590 align:start position:0% so while we might um<00:17:43.320> some<00:17:43.799> of<00:17:43.919> us<00:17:43.980> might<00:17:44.280> be<00:17:44.400> able<00:17:44.940> to<00:17:45.120> identify 00:17:45.590 --> 00:17:45.600 align:start position:0% um some of us might be able to identify 00:17:45.600 --> 00:17:47.570 align:start position:0% um some of us might be able to identify the<00:17:45.840> potato 00:17:47.570 --> 00:17:47.580 align:start position:0% the potato 00:17:47.580 --> 00:17:50.510 align:start position:0% the potato um most<00:17:48.000> of<00:17:48.120> us<00:17:48.240> are<00:17:48.539> going<00:17:48.780> to<00:17:48.960> identify<00:17:49.559> the 00:17:50.510 --> 00:17:50.520 align:start position:0% um most of us are going to identify the 00:17:50.520 --> 00:17:51.350 align:start position:0% um most of us are going to identify the circle 00:17:51.350 --> 00:17:51.360 align:start position:0% circle 00:17:51.360 --> 00:17:56.210 align:start position:0% circle and<00:17:52.080> it's<00:17:52.500> a<00:17:52.679> representation<00:17:53.840> of<00:17:54.840> how<00:17:55.620> users 00:17:56.210 --> 00:17:56.220 align:start position:0% and it's a representation of how users 00:17:56.220 --> 00:18:00.950 align:start position:0% and it's a representation of how users mental<00:17:56.760> models<00:17:57.240> take<00:17:57.679> recognizable<00:17:58.679> shapes 00:18:00.950 --> 00:18:00.960 align:start position:0% mental models take recognizable shapes 00:18:00.960 --> 00:18:03.470 align:start position:0% mental models take recognizable shapes however<00:18:01.440> the<00:18:01.799> closer<00:18:02.220> we<00:18:02.940> get<00:18:03.059> to<00:18:03.179> the<00:18:03.360> other 00:18:03.470 --> 00:18:03.480 align:start position:0% however the closer we get to the other 00:18:03.480 --> 00:18:05.870 align:start position:0% however the closer we get to the other side<00:18:03.720> of<00:18:04.020> that<00:18:04.200> scale<00:18:04.500> the<00:18:05.100> the<00:18:05.400> model<00:18:05.640> that 00:18:05.870 --> 00:18:05.880 align:start position:0% side of that scale the the model that 00:18:05.880 --> 00:18:08.150 align:start position:0% side of that scale the the model that reflects<00:18:06.360> technology<00:18:06.840> it's<00:18:07.679> a<00:18:07.919> less 00:18:08.150 --> 00:18:08.160 align:start position:0% reflects technology it's a less 00:18:08.160 --> 00:18:10.610 align:start position:0% reflects technology it's a less recognizable<00:18:09.000> form<00:18:09.299> or<00:18:09.780> at<00:18:09.900> least<00:18:10.020> one<00:18:10.380> that 00:18:10.610 --> 00:18:10.620 align:start position:0% recognizable form or at least one that 00:18:10.620 --> 00:18:13.010 align:start position:0% recognizable form or at least one that we<00:18:10.919> are<00:18:11.640> probably<00:18:11.880> not<00:18:12.120> going<00:18:12.360> to<00:18:12.480> agree<00:18:12.720> on 00:18:13.010 --> 00:18:13.020 align:start position:0% we are probably not going to agree on 00:18:13.020 --> 00:18:15.830 align:start position:0% we are probably not going to agree on what<00:18:13.440> it's<00:18:13.559> called 00:18:15.830 --> 00:18:15.840 align:start position:0% 00:18:15.840 --> 00:18:18.650 align:start position:0% and<00:18:16.559> a<00:18:16.799> really<00:18:16.980> interesting<00:18:17.520> aspect<00:18:18.059> of<00:18:18.360> this 00:18:18.650 --> 00:18:18.660 align:start position:0% and a really interesting aspect of this 00:18:18.660 --> 00:18:21.529 align:start position:0% and a really interesting aspect of this is<00:18:19.140> that<00:18:19.440> developers<00:18:20.160> on<00:18:20.520> my<00:18:20.640> team<00:18:20.820> encounter 00:18:21.529 --> 00:18:21.539 align:start position:0% is that developers on my team encounter 00:18:21.539 --> 00:18:23.930 align:start position:0% is that developers on my team encounter a<00:18:22.200> similar<00:18:22.559> Journey<00:18:22.919> when<00:18:23.580> they<00:18:23.760> create 00:18:23.930 --> 00:18:23.940 align:start position:0% a similar Journey when they create 00:18:23.940 --> 00:18:26.390 align:start position:0% a similar Journey when they create programmable<00:18:24.660> cryptography 00:18:26.390 --> 00:18:26.400 align:start position:0% programmable cryptography 00:18:26.400 --> 00:18:28.490 align:start position:0% programmable cryptography they<00:18:26.880> start<00:18:27.000> with<00:18:27.299> mathematical<00:18:27.900> proofs 00:18:28.490 --> 00:18:28.500 align:start position:0% they start with mathematical proofs 00:18:28.500 --> 00:18:31.610 align:start position:0% they start with mathematical proofs which<00:18:29.160> they<00:18:29.460> abstract<00:18:30.000> into<00:18:30.600> simple<00:18:31.080> and 00:18:31.610 --> 00:18:31.620 align:start position:0% which they abstract into simple and 00:18:31.620 --> 00:18:35.630 align:start position:0% which they abstract into simple and familiar<00:18:32.100> code 00:18:35.630 --> 00:18:35.640 align:start position:0% 00:18:35.640 --> 00:18:38.570 align:start position:0% so<00:18:36.120> both<00:18:36.419> developers<00:18:37.080> and<00:18:37.559> designers<00:18:38.039> on<00:18:38.400> our 00:18:38.570 --> 00:18:38.580 align:start position:0% so both developers and designers on our 00:18:38.580 --> 00:18:40.690 align:start position:0% so both developers and designers on our team<00:18:38.760> are<00:18:39.059> on<00:18:39.299> this<00:18:39.539> similar<00:18:40.020> Journey 00:18:40.690 --> 00:18:40.700 align:start position:0% team are on this similar Journey 00:18:40.700 --> 00:18:43.010 align:start position:0% team are on this similar Journey transforming<00:18:41.700> abstraction<00:18:42.299> into<00:18:42.720> something 00:18:43.010 --> 00:18:43.020 align:start position:0% transforming abstraction into something 00:18:43.020 --> 00:18:45.230 align:start position:0% transforming abstraction into something familiar<00:18:43.620> and<00:18:43.799> usable 00:18:45.230 --> 00:18:45.240 align:start position:0% familiar and usable 00:18:45.240 --> 00:18:47.510 align:start position:0% familiar and usable let<00:18:45.780> me<00:18:45.900> give<00:18:46.080> you<00:18:46.260> an<00:18:46.440> example<00:18:46.799> of<00:18:47.100> how<00:18:47.340> this 00:18:47.510 --> 00:18:47.520 align:start position:0% let me give you an example of how this 00:18:47.520 --> 00:18:49.490 align:start position:0% let me give you an example of how this plays<00:18:47.820> out 00:18:49.490 --> 00:18:49.500 align:start position:0% plays out 00:18:49.500 --> 00:18:52.870 align:start position:0% plays out back<00:18:50.100> to<00:18:50.280> some<00:18:50.520> screenshots<00:18:50.880> of<00:18:51.120> unirf<00:18:51.660> social 00:18:52.870 --> 00:18:52.880 align:start position:0% back to some screenshots of unirf social 00:18:52.880 --> 00:18:55.010 align:start position:0% back to some screenshots of unirf social I<00:18:53.880> could<00:18:54.000> describe<00:18:54.480> this<00:18:54.660> with<00:18:54.900> an 00:18:55.010 --> 00:18:55.020 align:start position:0% I could describe this with an 00:18:55.020 --> 00:18:57.289 align:start position:0% I could describe this with an implementation<00:18:55.679> model<00:18:56.039> and<00:18:56.460> say<00:18:56.700> that<00:18:56.940> uni 00:18:57.289 --> 00:18:57.299 align:start position:0% implementation model and say that uni 00:18:57.299 --> 00:18:59.090 align:start position:0% implementation model and say that uni rep<00:18:57.480> social<00:18:57.840> was<00:18:58.140> built<00:18:58.440> with<00:18:58.559> two<00:18:58.679> ZK 00:18:59.090 --> 00:18:59.100 align:start position:0% rep social was built with two ZK 00:18:59.100 --> 00:19:02.210 align:start position:0% rep social was built with two ZK protocols<00:18:59.640> uni<00:19:00.059> rep<00:19:00.179> and<00:19:00.419> sentma<00:19:00.780> 4.<00:19:01.620> and<00:19:01.980> when 00:19:02.210 --> 00:19:02.220 align:start position:0% protocols uni rep and sentma 4. and when 00:19:02.220 --> 00:19:04.130 align:start position:0% protocols uni rep and sentma 4. and when you<00:19:02.340> register<00:19:02.760> and<00:19:03.179> a<00:19:03.299> tester<00:19:03.660> will<00:19:03.840> give<00:19:04.020> you 00:19:04.130 --> 00:19:04.140 align:start position:0% you register and a tester will give you 00:19:04.140 --> 00:19:06.409 align:start position:0% you register and a tester will give you three<00:19:04.559> Epoch<00:19:05.160> keys<00:19:05.400> and<00:19:05.640> a<00:19:05.820> set<00:19:05.940> number<00:19:06.179> of 00:19:06.409 --> 00:19:06.419 align:start position:0% three Epoch keys and a set number of 00:19:06.419 --> 00:19:09.250 align:start position:0% three Epoch keys and a set number of reputation<00:19:07.020> points 00:19:09.250 --> 00:19:09.260 align:start position:0% reputation points 00:19:09.260 --> 00:19:12.430 align:start position:0% reputation points every<00:19:10.260> Epoch<00:19:10.919> to<00:19:11.039> interact<00:19:11.400> with<00:19:11.640> other<00:19:11.820> users 00:19:12.430 --> 00:19:12.440 align:start position:0% every Epoch to interact with other users 00:19:12.440 --> 00:19:15.470 align:start position:0% every Epoch to interact with other users positive<00:19:13.440> reputation<00:19:14.100> points<00:19:14.820> are<00:19:15.000> used<00:19:15.179> to 00:19:15.470 --> 00:19:15.480 align:start position:0% positive reputation points are used to 00:19:15.480 --> 00:19:18.110 align:start position:0% positive reputation points are used to post<00:19:15.720> and<00:19:16.020> comment<00:19:16.440> you<00:19:17.160> can<00:19:17.280> give<00:19:17.580> positive 00:19:18.110 --> 00:19:18.120 align:start position:0% post and comment you can give positive 00:19:18.120 --> 00:19:20.810 align:start position:0% post and comment you can give positive reputation<00:19:18.720> points<00:19:19.440> to<00:19:19.980> content<00:19:20.400> that<00:19:20.640> you 00:19:20.810 --> 00:19:20.820 align:start position:0% reputation points to content that you 00:19:20.820 --> 00:19:23.930 align:start position:0% reputation points to content that you like<00:19:21.059> and<00:19:21.900> give<00:19:22.200> negative<00:19:22.799> reputation<00:19:23.400> points 00:19:23.930 --> 00:19:23.940 align:start position:0% like and give negative reputation points 00:19:23.940 --> 00:19:26.390 align:start position:0% like and give negative reputation points to<00:19:24.120> content<00:19:24.539> that<00:19:24.840> you<00:19:25.020> don't<00:19:25.200> like 00:19:26.390 --> 00:19:26.400 align:start position:0% to content that you don't like 00:19:26.400 --> 00:19:29.090 align:start position:0% to content that you don't like at<00:19:27.059> the<00:19:27.179> end<00:19:27.299> of<00:19:27.539> every<00:19:27.720> Epoch<00:19:28.440> a<00:19:28.620> user<00:19:28.919> State 00:19:29.090 --> 00:19:29.100 align:start position:0% at the end of every Epoch a user State 00:19:29.100 --> 00:19:31.549 align:start position:0% at the end of every Epoch a user State transition<00:19:29.580> occurs<00:19:30.179> where<00:19:30.660> the<00:19:31.020> positive<00:19:31.320> and 00:19:31.549 --> 00:19:31.559 align:start position:0% transition occurs where the positive and 00:19:31.559 --> 00:19:33.049 align:start position:0% transition occurs where the positive and negative<00:19:31.919> reputation<00:19:32.460> points<00:19:32.940> are 00:19:33.049 --> 00:19:33.059 align:start position:0% negative reputation points are 00:19:33.059 --> 00:19:35.630 align:start position:0% negative reputation points are recalculated<00:19:33.720> and<00:19:34.440> your<00:19:34.620> epoc<00:19:35.039> keys<00:19:35.460> are 00:19:35.630 --> 00:19:35.640 align:start position:0% recalculated and your epoc keys are 00:19:35.640 --> 00:19:39.169 align:start position:0% recalculated and your epoc keys are swapped<00:19:36.059> for<00:19:36.299> three<00:19:36.480> new<00:19:36.780> ones 00:19:39.169 --> 00:19:39.179 align:start position:0% 00:19:39.179 --> 00:19:41.150 align:start position:0% that<00:19:39.720> might<00:19:39.840> have<00:19:39.960> made<00:19:40.140> sense<00:19:40.440> to<00:19:40.740> some<00:19:40.919> of 00:19:41.150 --> 00:19:41.160 align:start position:0% that might have made sense to some of 00:19:41.160 --> 00:19:43.610 align:start position:0% that might have made sense to some of you<00:19:41.280> but<00:19:42.059> for<00:19:42.360> me<00:19:42.480> when<00:19:42.840> I<00:19:43.020> first<00:19:43.200> heard<00:19:43.440> this 00:19:43.610 --> 00:19:43.620 align:start position:0% you but for me when I first heard this 00:19:43.620 --> 00:19:46.730 align:start position:0% you but for me when I first heard this it<00:19:43.860> made<00:19:44.160> literally<00:19:44.760> no<00:19:45.000> sense<00:19:45.179> at<00:19:45.419> all 00:19:46.730 --> 00:19:46.740 align:start position:0% it made literally no sense at all 00:19:46.740 --> 00:19:50.150 align:start position:0% it made literally no sense at all the<00:19:47.280> language<00:19:47.520> is<00:19:47.820> Niche<00:19:48.360> and<00:19:48.720> uncommon 00:19:50.150 --> 00:19:50.160 align:start position:0% the language is Niche and uncommon 00:19:50.160 --> 00:19:53.330 align:start position:0% the language is Niche and uncommon but<00:19:51.059> I<00:19:51.419> I<00:19:51.720> do<00:19:51.960> understand<00:19:52.200> it<00:19:52.679> now<00:19:52.919> but<00:19:53.160> it's 00:19:53.330 --> 00:19:53.340 align:start position:0% but I I do understand it now but it's 00:19:53.340 --> 00:19:57.169 align:start position:0% but I I do understand it now but it's only<00:19:53.520> because<00:19:53.760> we<00:19:54.120> created<00:19:54.480> mental<00:19:55.260> models 00:19:57.169 --> 00:19:57.179 align:start position:0% only because we created mental models 00:19:57.179 --> 00:19:59.750 align:start position:0% only because we created mental models to<00:19:57.720> understand<00:19:57.960> it<00:19:58.380> we<00:19:59.100> could<00:19:59.220> have<00:19:59.400> trained 00:19:59.750 --> 00:19:59.760 align:start position:0% to understand it we could have trained 00:19:59.760 --> 00:20:01.789 align:start position:0% to understand it we could have trained ourselves<00:20:00.059> to<00:20:00.419> learn<00:20:00.539> the<00:20:00.840> system<00:20:01.020> vocabulary 00:20:01.789 --> 00:20:01.799 align:start position:0% ourselves to learn the system vocabulary 00:20:01.799 --> 00:20:04.430 align:start position:0% ourselves to learn the system vocabulary but<00:20:02.520> instead<00:20:02.880> we<00:20:03.059> came<00:20:03.240> up<00:20:03.419> with<00:20:03.720> a<00:20:03.900> new<00:20:04.080> way<00:20:04.260> to 00:20:04.430 --> 00:20:04.440 align:start position:0% but instead we came up with a new way to 00:20:04.440 --> 00:20:06.650 align:start position:0% but instead we came up with a new way to describe<00:20:04.860> the<00:20:05.039> app<00:20:05.580> by<00:20:06.000> asking<00:20:06.360> ourselves 00:20:06.650 --> 00:20:06.660 align:start position:0% describe the app by asking ourselves 00:20:06.660 --> 00:20:09.710 align:start position:0% describe the app by asking ourselves questions<00:20:07.020> like<00:20:07.559> what<00:20:08.340> does<00:20:08.520> this<00:20:08.820> remind<00:20:09.360> me 00:20:09.710 --> 00:20:09.720 align:start position:0% questions like what does this remind me 00:20:09.720 --> 00:20:10.909 align:start position:0% questions like what does this remind me of 00:20:10.909 --> 00:20:10.919 align:start position:0% of 00:20:10.919 --> 00:20:15.110 align:start position:0% of what<00:20:11.400> do<00:20:11.580> I<00:20:11.760> know<00:20:12.120> that<00:20:12.480> is<00:20:12.660> similar<00:20:13.200> to<00:20:13.500> this 00:20:15.110 --> 00:20:15.120 align:start position:0% what do I know that is similar to this 00:20:15.120 --> 00:20:18.169 align:start position:0% what do I know that is similar to this if<00:20:15.600> we<00:20:15.720> want<00:20:15.840> to<00:20:16.020> create<00:20:16.320> usable<00:20:16.980> ZK<00:20:17.520> products 00:20:18.169 --> 00:20:18.179 align:start position:0% if we want to create usable ZK products 00:20:18.179 --> 00:20:21.169 align:start position:0% if we want to create usable ZK products we<00:20:18.600> cannot<00:20:18.840> ask<00:20:19.140> people<00:20:19.380> to<00:20:19.799> just<00:20:20.039> get<00:20:20.700> used<00:20:20.940> to 00:20:21.169 --> 00:20:21.179 align:start position:0% we cannot ask people to just get used to 00:20:21.179 --> 00:20:24.169 align:start position:0% we cannot ask people to just get used to a<00:20:21.419> machine's<00:20:21.960> language<00:20:22.520> we<00:20:23.520> have<00:20:23.640> to<00:20:23.760> put<00:20:24.000> time 00:20:24.169 --> 00:20:24.179 align:start position:0% a machine's language we have to put time 00:20:24.179 --> 00:20:26.450 align:start position:0% a machine's language we have to put time into<00:20:24.480> deepening<00:20:25.080> our<00:20:25.320> understanding<00:20:25.919> so<00:20:26.280> that 00:20:26.450 --> 00:20:26.460 align:start position:0% into deepening our understanding so that 00:20:26.460 --> 00:20:28.310 align:start position:0% into deepening our understanding so that we<00:20:26.640> can<00:20:26.760> create<00:20:27.000> approachable<00:20:27.660> applications 00:20:28.310 --> 00:20:28.320 align:start position:0% we can create approachable applications 00:20:28.320 --> 00:20:31.430 align:start position:0% we can create approachable applications that<00:20:28.860> mirror<00:20:29.280> the<00:20:29.460> familiar 00:20:31.430 --> 00:20:31.440 align:start position:0% that mirror the familiar 00:20:31.440 --> 00:20:34.210 align:start position:0% that mirror the familiar so<00:20:31.860> let's<00:20:32.039> try<00:20:32.280> this<00:20:32.520> again<00:20:32.760> what<00:20:33.539> if<00:20:33.720> I<00:20:33.900> said 00:20:34.210 --> 00:20:34.220 align:start position:0% so let's try this again what if I said 00:20:34.220 --> 00:20:36.830 align:start position:0% so let's try this again what if I said unirup<00:20:35.220> social<00:20:35.460> is<00:20:35.940> a<00:20:36.179> place<00:20:36.360> to<00:20:36.720> build 00:20:36.830 --> 00:20:36.840 align:start position:0% unirup social is a place to build 00:20:36.840 --> 00:20:40.130 align:start position:0% unirup social is a place to build communities<00:20:37.559> based<00:20:38.520> on<00:20:38.640> ideas<00:20:39.000> rather<00:20:39.900> than 00:20:40.130 --> 00:20:40.140 align:start position:0% communities based on ideas rather than 00:20:40.140 --> 00:20:42.110 align:start position:0% communities based on ideas rather than identities 00:20:42.110 --> 00:20:42.120 align:start position:0% identities 00:20:42.120 --> 00:20:44.330 align:start position:0% identities if<00:20:42.600> you<00:20:42.720> sign<00:20:42.900> up<00:20:43.080> for<00:20:43.260> the<00:20:43.440> app<00:20:43.559> you<00:20:43.919> get<00:20:44.039> three 00:20:44.330 --> 00:20:44.340 align:start position:0% if you sign up for the app you get three 00:20:44.340 --> 00:20:47.330 align:start position:0% if you sign up for the app you get three personas<00:20:45.000> and<00:20:45.480> 30<00:20:45.720> rep<00:20:46.020> to<00:20:46.740> interact<00:20:47.039> with 00:20:47.330 --> 00:20:47.340 align:start position:0% personas and 30 rep to interact with 00:20:47.340 --> 00:20:50.270 align:start position:0% personas and 30 rep to interact with other<00:20:47.520> users<00:20:48.059> rep<00:20:48.960> is<00:20:49.200> like<00:20:49.440> points<00:20:50.039> or 00:20:50.270 --> 00:20:50.280 align:start position:0% other users rep is like points or 00:20:50.280 --> 00:20:51.590 align:start position:0% other users rep is like points or currency 00:20:51.590 --> 00:20:51.600 align:start position:0% currency 00:20:51.600 --> 00:20:54.590 align:start position:0% currency it's<00:20:52.140> needed<00:20:52.500> to<00:20:52.740> post<00:20:52.919> in<00:20:53.220> comment 00:20:54.590 --> 00:20:54.600 align:start position:0% it's needed to post in comment 00:20:54.600 --> 00:20:57.650 align:start position:0% it's needed to post in comment it's<00:20:55.320> also<00:20:55.740> used<00:20:55.980> to<00:20:56.460> boost<00:20:56.700> the<00:20:57.059> content<00:20:57.419> that 00:20:57.650 --> 00:20:57.660 align:start position:0% it's also used to boost the content that 00:20:57.660 --> 00:20:59.930 align:start position:0% it's also used to boost the content that you<00:20:57.840> like<00:20:58.020> and<00:20:58.500> squash<00:20:58.860> the<00:20:59.100> content<00:20:59.460> that<00:20:59.760> you 00:20:59.930 --> 00:20:59.940 align:start position:0% you like and squash the content that you 00:20:59.940 --> 00:21:01.250 align:start position:0% you like and squash the content that you don't<00:21:00.059> like 00:21:01.250 --> 00:21:01.260 align:start position:0% don't like 00:21:01.260 --> 00:21:05.029 align:start position:0% don't like every<00:21:02.100> cycle<00:21:02.460> about<00:21:03.360> one<00:21:03.720> week<00:21:03.960> you<00:21:04.559> receive 00:21:05.029 --> 00:21:05.039 align:start position:0% every cycle about one week you receive 00:21:05.039 --> 00:21:08.630 align:start position:0% every cycle about one week you receive three<00:21:05.820> new<00:21:06.059> personas<00:21:06.660> and<00:21:07.140> your<00:21:07.320> rep<00:21:07.440> total<00:21:07.919> is 00:21:08.630 --> 00:21:08.640 align:start position:0% three new personas and your rep total is 00:21:08.640 --> 00:21:10.669 align:start position:0% three new personas and your rep total is calculated<00:21:09.120> based<00:21:09.720> on<00:21:09.780> what<00:21:10.080> you<00:21:10.260> have<00:21:10.440> used 00:21:10.669 --> 00:21:10.679 align:start position:0% calculated based on what you have used 00:21:10.679 --> 00:21:13.130 align:start position:0% calculated based on what you have used and<00:21:11.160> what<00:21:11.400> you<00:21:11.580> received<00:21:12.000> from<00:21:12.419> other<00:21:12.660> members 00:21:13.130 --> 00:21:13.140 align:start position:0% and what you received from other members 00:21:13.140 --> 00:21:16.130 align:start position:0% and what you received from other members you<00:21:14.100> must<00:21:14.280> have<00:21:14.460> a<00:21:14.700> positive<00:21:15.179> amount<00:21:15.720> of<00:21:15.900> rep 00:21:16.130 --> 00:21:16.140 align:start position:0% you must have a positive amount of rep 00:21:16.140 --> 00:21:20.330 align:start position:0% you must have a positive amount of rep to<00:21:16.740> interact<00:21:17.039> with<00:21:17.340> the<00:21:17.520> system 00:21:20.330 --> 00:21:20.340 align:start position:0% 00:21:20.340 --> 00:21:23.029 align:start position:0% I<00:21:20.760> think<00:21:20.940> that<00:21:21.240> that<00:21:21.600> was<00:21:21.900> probably<00:21:22.140> more 00:21:23.029 --> 00:21:23.039 align:start position:0% I think that that was probably more 00:21:23.039 --> 00:21:26.210 align:start position:0% I think that that was probably more except<00:21:23.660> accessible<00:21:24.660> but<00:21:25.320> the<00:21:25.500> thing<00:21:25.679> to<00:21:26.100> point 00:21:26.210 --> 00:21:26.220 align:start position:0% except accessible but the thing to point 00:21:26.220 --> 00:21:28.850 align:start position:0% except accessible but the thing to point out<00:21:26.460> is<00:21:26.880> that<00:21:27.179> it's<00:21:27.660> not<00:21:27.840> a<00:21:28.080> user's<00:21:28.500> mental 00:21:28.850 --> 00:21:28.860 align:start position:0% out is that it's not a user's mental 00:21:28.860 --> 00:21:31.549 align:start position:0% out is that it's not a user's mental model<00:21:29.039> we're<00:21:29.760> still<00:21:30.000> not<00:21:30.179> at<00:21:30.419> that<00:21:30.600> stage<00:21:30.960> it's 00:21:31.549 --> 00:21:31.559 align:start position:0% model we're still not at that stage it's 00:21:31.559 --> 00:21:33.370 align:start position:0% model we're still not at that stage it's a<00:21:31.860> design<00:21:32.039> team's 00:21:33.370 --> 00:21:33.380 align:start position:0% a design team's 00:21:33.380 --> 00:21:35.450 align:start position:0% a design team's represented<00:21:34.380> model 00:21:35.450 --> 00:21:35.460 align:start position:0% represented model 00:21:35.460 --> 00:21:38.630 align:start position:0% represented model and<00:21:36.299> this<00:21:36.659> just<00:21:36.840> goes<00:21:37.200> back<00:21:37.380> to<00:21:37.860> iterating<00:21:38.340> the 00:21:38.630 --> 00:21:38.640 align:start position:0% and this just goes back to iterating the 00:21:38.640 --> 00:21:40.789 align:start position:0% and this just goes back to iterating the point<00:21:38.760> of<00:21:39.059> like<00:21:39.240> we<00:21:40.020> need<00:21:40.140> to<00:21:40.260> keep<00:21:40.440> cycling 00:21:40.789 --> 00:21:40.799 align:start position:0% point of like we need to keep cycling 00:21:40.799 --> 00:21:43.909 align:start position:0% point of like we need to keep cycling through<00:21:41.600> uh<00:21:42.600> and<00:21:42.960> iterating<00:21:43.380> on<00:21:43.559> the<00:21:43.740> work 00:21:43.909 --> 00:21:43.919 align:start position:0% through uh and iterating on the work 00:21:43.919 --> 00:21:45.950 align:start position:0% through uh and iterating on the work putting<00:21:44.700> the<00:21:44.880> work<00:21:45.000> in<00:21:45.179> front<00:21:45.360> of<00:21:45.480> people<00:21:45.659> and 00:21:45.950 --> 00:21:45.960 align:start position:0% putting the work in front of people and 00:21:45.960 --> 00:21:48.289 align:start position:0% putting the work in front of people and getting<00:21:46.200> feedback 00:21:48.289 --> 00:21:48.299 align:start position:0% getting feedback 00:21:48.299 --> 00:21:50.390 align:start position:0% getting feedback this<00:21:48.720> is<00:21:48.840> true<00:21:49.020> for<00:21:49.200> any<00:21:49.440> of<00:21:49.620> the<00:21:49.799> designs<00:21:50.220> in 00:21:50.390 --> 00:21:50.400 align:start position:0% this is true for any of the designs in 00:21:50.400 --> 00:21:52.549 align:start position:0% this is true for any of the designs in the<00:21:50.580> space 00:21:52.549 --> 00:21:52.559 align:start position:0% the space 00:21:52.559 --> 00:21:55.490 align:start position:0% the space so<00:21:53.039> although<00:21:53.400> I<00:21:53.520> could<00:21:53.700> only<00:21:53.880> share<00:21:54.299> a<00:21:54.780> few<00:21:54.960> of 00:21:55.490 --> 00:21:55.500 align:start position:0% so although I could only share a few of 00:21:55.500 --> 00:21:58.310 align:start position:0% so although I could only share a few of our<00:21:55.679> challenges<00:21:56.159> there<00:21:56.580> are<00:21:56.700> many 00:21:58.310 --> 00:21:58.320 align:start position:0% our challenges there are many 00:21:58.320 --> 00:21:59.990 align:start position:0% our challenges there are many um<00:21:58.440> but<00:21:59.100> that<00:21:59.220> means<00:21:59.460> there's<00:21:59.640> lots<00:21:59.940> of 00:21:59.990 --> 00:22:00.000 align:start position:0% um but that means there's lots of 00:22:00.000 --> 00:22:02.149 align:start position:0% um but that means there's lots of opportunity<00:22:00.539> for<00:22:00.900> design 00:22:02.149 --> 00:22:02.159 align:start position:0% opportunity for design 00:22:02.159 --> 00:22:04.789 align:start position:0% opportunity for design with<00:22:02.940> more<00:22:03.120> people<00:22:03.299> designing<00:22:03.960> CK<00:22:04.500> public 00:22:04.789 --> 00:22:04.799 align:start position:0% with more people designing CK public 00:22:04.799 --> 00:22:06.890 align:start position:0% with more people designing CK public goods<00:22:05.280> I<00:22:05.520> believe<00:22:05.640> that<00:22:05.820> we<00:22:06.000> can<00:22:06.179> Empower<00:22:06.539> more 00:22:06.890 --> 00:22:06.900 align:start position:0% goods I believe that we can Empower more 00:22:06.900 --> 00:22:09.590 align:start position:0% goods I believe that we can Empower more Builders<00:22:07.440> and<00:22:07.860> product<00:22:08.100> teams 00:22:09.590 --> 00:22:09.600 align:start position:0% Builders and product teams 00:22:09.600 --> 00:22:12.169 align:start position:0% Builders and product teams reduce<00:22:10.200> friction<00:22:10.679> when<00:22:11.280> onboarding<00:22:12.000> to 00:22:12.169 --> 00:22:12.179 align:start position:0% reduce friction when onboarding to 00:22:12.179 --> 00:22:13.909 align:start position:0% reduce friction when onboarding to privacy<00:22:12.600> apps 00:22:13.909 --> 00:22:13.919 align:start position:0% privacy apps 00:22:13.919 --> 00:22:15.890 align:start position:0% privacy apps help<00:22:14.400> developers<00:22:15.059> create<00:22:15.360> protocol 00:22:15.890 --> 00:22:15.900 align:start position:0% help developers create protocol 00:22:15.900 --> 00:22:18.409 align:start position:0% help developers create protocol resources<00:22:16.799> that<00:22:17.159> are<00:22:17.340> informed<00:22:17.700> by<00:22:18.000> user 00:22:18.409 --> 00:22:18.419 align:start position:0% resources that are informed by user 00:22:18.419 --> 00:22:19.970 align:start position:0% resources that are informed by user research 00:22:19.970 --> 00:22:19.980 align:start position:0% research 00:22:19.980 --> 00:22:22.850 align:start position:0% research educate<00:22:20.760> users<00:22:21.179> by<00:22:21.600> providing<00:22:22.080> transparent 00:22:22.850 --> 00:22:22.860 align:start position:0% educate users by providing transparent 00:22:22.860 --> 00:22:25.310 align:start position:0% educate users by providing transparent information<00:22:23.179> that<00:22:24.179> evolves<00:22:24.539> with<00:22:24.780> them<00:22:24.900> as 00:22:25.310 --> 00:22:25.320 align:start position:0% information that evolves with them as 00:22:25.320 --> 00:22:27.110 align:start position:0% information that evolves with them as they<00:22:25.620> learn 00:22:27.110 --> 00:22:27.120 align:start position:0% they learn 00:22:27.120 --> 00:22:30.890 align:start position:0% they learn and<00:22:27.840> reduce<00:22:28.260> the<00:22:28.740> stigma<00:22:29.360> and<00:22:30.360> normalize 00:22:30.890 --> 00:22:30.900 align:start position:0% and reduce the stigma and normalize 00:22:30.900 --> 00:22:35.930 align:start position:0% and reduce the stigma and normalize online<00:22:31.380> privacy<00:22:32.100> and<00:22:32.400> anonymity 00:22:35.930 --> 00:22:35.940 align:start position:0% 00:22:35.940 --> 00:22:38.570 align:start position:0% if<00:22:36.419> we<00:22:36.539> want<00:22:36.659> to<00:22:36.840> see<00:22:37.020> privacy<00:22:37.559> normalized<00:22:38.340> and 00:22:38.570 --> 00:22:38.580 align:start position:0% if we want to see privacy normalized and 00:22:38.580 --> 00:22:41.810 align:start position:0% if we want to see privacy normalized and made<00:22:38.820> accessible<00:22:39.360> to<00:22:40.260> everyone<00:22:40.679> we<00:22:41.640> must 00:22:41.810 --> 00:22:41.820 align:start position:0% made accessible to everyone we must 00:22:41.820 --> 00:22:44.450 align:start position:0% made accessible to everyone we must continue<00:22:42.120> to<00:22:42.659> collaboratively<00:22:43.380> design 00:22:44.450 --> 00:22:44.460 align:start position:0% continue to collaboratively design 00:22:44.460 --> 00:22:46.549 align:start position:0% continue to collaboratively design people<00:22:45.059> from<00:22:45.419> all<00:22:45.720> kinds<00:22:46.020> of<00:22:46.080> technical 00:22:46.549 --> 00:22:46.559 align:start position:0% people from all kinds of technical 00:22:46.559 --> 00:22:49.310 align:start position:0% people from all kinds of technical backgrounds<00:22:47.340> design<00:22:47.840> by<00:22:48.840> approaching 00:22:49.310 --> 00:22:49.320 align:start position:0% backgrounds design by approaching 00:22:49.320 --> 00:22:51.950 align:start position:0% backgrounds design by approaching challenges<00:22:49.860> with<00:22:50.220> curiosity<00:22:50.960> getting 00:22:51.950 --> 00:22:51.960 align:start position:0% challenges with curiosity getting 00:22:51.960 --> 00:22:53.630 align:start position:0% challenges with curiosity getting comfortable<00:22:52.380> spending<00:22:52.980> time<00:22:53.159> with<00:22:53.460> the 00:22:53.630 --> 00:22:53.640 align:start position:0% comfortable spending time with the 00:22:53.640 --> 00:22:54.770 align:start position:0% comfortable spending time with the unknown 00:22:54.770 --> 00:22:54.780 align:start position:0% unknown 00:22:54.780 --> 00:22:58.850 align:start position:0% unknown aligning<00:22:55.620> strategy<00:22:56.400> to<00:22:57.000> audience<00:22:57.419> objectives 00:22:58.850 --> 00:22:58.860 align:start position:0% aligning strategy to audience objectives 00:22:58.860 --> 00:23:01.789 align:start position:0% aligning strategy to audience objectives testing<00:22:59.580> potential<00:23:00.480> Solutions<00:23:01.020> and 00:23:01.789 --> 00:23:01.799 align:start position:0% testing potential Solutions and 00:23:01.799 --> 00:23:07.149 align:start position:0% testing potential Solutions and iterating<00:23:02.280> their<00:23:02.640> work 00:23:07.149 --> 00:23:07.159 align:start position:0% 00:23:07.159 --> 00:23:09.350 align:start position:0% I<00:23:08.159> want<00:23:08.340> to 00:23:09.350 --> 00:23:09.360 align:start position:0% I want to 00:23:09.360 --> 00:23:11.930 align:start position:0% I want to thank<00:23:09.720> my<00:23:10.080> team<00:23:10.200> members<00:23:10.620> who<00:23:10.980> helped<00:23:11.400> me 00:23:11.930 --> 00:23:11.940 align:start position:0% thank my team members who helped me 00:23:11.940 --> 00:23:13.750 align:start position:0% thank my team members who helped me collaboratively 00:23:13.750 --> 00:23:13.760 align:start position:0% collaboratively 00:23:13.760 --> 00:23:16.870 align:start position:0% collaboratively uh<00:23:14.760> with<00:23:15.179> this<00:23:15.360> presentation 00:23:16.870 --> 00:23:16.880 align:start position:0% uh with this presentation 00:23:16.880 --> 00:23:19.549 align:start position:0% uh with this presentation we<00:23:17.880> worked<00:23:18.120> really<00:23:18.299> similarly<00:23:18.780> to<00:23:19.140> the<00:23:19.320> way<00:23:19.440> we 00:23:19.549 --> 00:23:19.559 align:start position:0% we worked really similarly to the way we 00:23:19.559 --> 00:23:21.710 align:start position:0% we worked really similarly to the way we work<00:23:19.799> on<00:23:19.980> other<00:23:20.159> things 00:23:21.710 --> 00:23:21.720 align:start position:0% work on other things 00:23:21.720 --> 00:23:22.310 align:start position:0% work on other things um 00:23:22.310 --> 00:23:22.320 align:start position:0% um 00:23:22.320 --> 00:23:25.549 align:start position:0% um our<00:23:23.159> the<00:23:23.400> QR<00:23:23.700> code<00:23:23.880> goes<00:23:24.179> to<00:23:24.299> our<00:23:24.480> PSE<00:23:24.900> Discord 00:23:25.549 --> 00:23:25.559 align:start position:0% our the QR code goes to our PSE Discord 00:23:25.559 --> 00:23:28.370 align:start position:0% our the QR code goes to our PSE Discord where<00:23:26.159> you<00:23:26.280> can<00:23:26.400> find<00:23:26.580> all<00:23:26.940> of<00:23:27.059> us 00:23:28.370 --> 00:23:28.380 align:start position:0% where you can find all of us 00:23:28.380 --> 00:23:29.270 align:start position:0% where you can find all of us um 00:23:29.270 --> 00:23:29.280 align:start position:0% um 00:23:29.280 --> 00:23:32.450 align:start position:0% um my<00:23:29.820> handle's<00:23:30.299> in<00:23:30.419> the<00:23:30.600> top<00:23:30.720> left<00:23:31.100> and<00:23:32.100> we 00:23:32.450 --> 00:23:32.460 align:start position:0% my handle's in the top left and we 00:23:32.460 --> 00:23:34.909 align:start position:0% my handle's in the top left and we started<00:23:32.880> a<00:23:33.240> designing<00:23:34.020> for<00:23:34.260> public<00:23:34.440> goods 00:23:34.909 --> 00:23:34.919 align:start position:0% started a designing for public goods 00:23:34.919 --> 00:23:37.190 align:start position:0% started a designing for public goods channel<00:23:35.159> so<00:23:35.760> if<00:23:36.179> this<00:23:36.360> content<00:23:36.720> resonates 00:23:37.190 --> 00:23:37.200 align:start position:0% channel so if this content resonates 00:23:37.200 --> 00:23:38.690 align:start position:0% channel so if this content resonates with<00:23:37.380> you<00:23:37.559> please 00:23:38.690 --> 00:23:38.700 align:start position:0% with you please 00:23:38.700 --> 00:23:40.730 align:start position:0% with you please um join<00:23:39.059> our<00:23:39.240> Channel<00:23:39.419> and<00:23:40.260> start<00:23:40.559> a 00:23:40.730 --> 00:23:40.740 align:start position:0% um join our Channel and start a 00:23:40.740 --> 00:23:41.990 align:start position:0% um join our Channel and start a conversation 00:23:41.990 --> 00:23:42.000 align:start position:0% conversation 00:23:42.000 --> 00:23:45.310 align:start position:0% conversation if<00:23:42.480> you<00:23:42.600> want<00:23:42.840> to<00:23:42.960> get<00:23:43.320> involved<00:23:43.919> this<00:23:44.400> week 00:23:45.310 --> 00:23:45.320 align:start position:0% if you want to get involved this week 00:23:45.320 --> 00:23:48.169 align:start position:0% if you want to get involved this week like<00:23:46.320> I<00:23:46.500> mentioned<00:23:46.799> earlier<00:23:47.159> the<00:23:47.760> temporary 00:23:48.169 --> 00:23:48.179 align:start position:0% like I mentioned earlier the temporary 00:23:48.179 --> 00:23:50.630 align:start position:0% like I mentioned earlier the temporary Anonymous<00:23:48.659> Zone<00:23:49.020> Community<00:23:49.320> Hub<00:23:49.740> is 00:23:50.630 --> 00:23:50.640 align:start position:0% Anonymous Zone Community Hub is 00:23:50.640 --> 00:23:53.690 align:start position:0% Anonymous Zone Community Hub is downstairs<00:23:51.000> on<00:23:51.780> the<00:23:51.900> first<00:23:52.020> floor<00:23:52.400> and<00:23:53.400> then 00:23:53.690 --> 00:23:53.700 align:start position:0% downstairs on the first floor and then 00:23:53.700 --> 00:23:56.390 align:start position:0% downstairs on the first floor and then on<00:23:54.480> Thursday<00:23:54.659> from<00:23:55.080> 10<00:23:55.380> to<00:23:55.620> 6 00:23:56.390 --> 00:23:56.400 align:start position:0% on Thursday from 10 to 6 00:23:56.400 --> 00:23:59.330 align:start position:0% on Thursday from 10 to 6 uh<00:23:57.059> there's<00:23:57.360> the<00:23:57.720> adoption<00:23:58.320> day<00:23:58.620> ux 00:23:59.330 --> 00:23:59.340 align:start position:0% uh there's the adoption day ux 00:23:59.340 --> 00:24:02.450 align:start position:0% uh there's the adoption day ux unconference<00:24:00.179> where<00:24:00.600> we'll<00:24:00.780> do<00:24:00.960> some<00:24:01.200> ZK 00:24:02.450 --> 00:24:02.460 align:start position:0% unconference where we'll do some ZK 00:24:02.460 --> 00:24:04.970 align:start position:0% unconference where we'll do some ZK design<00:24:03.059> lightning<00:24:03.780> talks<00:24:04.260> and<00:24:04.559> then<00:24:04.679> have 00:24:04.970 --> 00:24:04.980 align:start position:0% design lightning talks and then have 00:24:04.980 --> 00:24:07.190 align:start position:0% design lightning talks and then have discussion<00:24:05.520> groups<00:24:05.880> later<00:24:06.059> in<00:24:06.360> the<00:24:06.480> day 00:24:07.190 --> 00:24:07.200 align:start position:0% discussion groups later in the day 00:24:07.200 --> 00:24:09.230 align:start position:0% discussion groups later in the day we<00:24:07.679> also<00:24:07.919> want<00:24:08.220> to 00:24:09.230 --> 00:24:09.240 align:start position:0% we also want to 00:24:09.240 --> 00:24:12.649 align:start position:0% we also want to um start<00:24:09.840> some<00:24:10.460> uh<00:24:11.460> learning<00:24:12.059> groups<00:24:12.419> for 00:24:12.649 --> 00:24:12.659 align:start position:0% um start some uh learning groups for 00:24:12.659 --> 00:24:14.630 align:start position:0% um start some uh learning groups for people<00:24:12.840> who<00:24:13.200> are<00:24:13.320> designing<00:24:13.860> in<00:24:14.159> this<00:24:14.340> space 00:24:14.630 --> 00:24:14.640 align:start position:0% people who are designing in this space 00:24:14.640 --> 00:24:19.010 align:start position:0% people who are designing in this space and<00:24:15.480> we'll<00:24:16.140> keep<00:24:16.320> you<00:24:16.440> updated<00:24:16.860> in<00:24:17.640> our 00:24:19.010 --> 00:24:19.020 align:start position:0% and we'll keep you updated in our 00:24:19.020 --> 00:24:20.690 align:start position:0% and we'll keep you updated in our designing<00:24:19.679> public<00:24:19.799> goods<00:24:20.220> channel<00:24:20.400> on<00:24:20.640> the 00:24:20.690 --> 00:24:20.700 align:start position:0% designing public goods channel on the 00:24:20.700 --> 00:24:22.190 align:start position:0% designing public goods channel on the PSC<00:24:21.120> Discord 00:24:22.190 --> 00:24:22.200 align:start position:0% PSC Discord 00:24:22.200 --> 00:24:25.220 align:start position:0% PSC Discord thank<00:24:22.740> you<00:24:22.860> so<00:24:23.039> much