[00:01.980 --> 00:02.420]  Okay.
[00:02.720 --> 00:02.980]  All right.
[00:03.120 --> 00:03.760]  Everyone, thank you.
[00:03.900 --> 00:05.960]  Welcome to day two of HOPE.
[00:06.560 --> 00:08.240]  My name is Andrew.
[00:08.400 --> 00:09.200]  I'm your MC.
[00:09.840 --> 00:13.860]  And I would like to present Jaguar and Dana from RIM.
[01:40.430 --> 01:40.950]  All right.
[01:41.070 --> 01:42.850]  So that was demo one of three demos.
[01:43.290 --> 01:53.670]  And the demo there was trying to show off how we can use tactile haptic technologies to increase collaboration.
[01:54.030 --> 01:59.010]  So what we were doing there was Dana and I were co-working in different locations.
[02:00.270 --> 02:06.370]  And when Dana was ready to close the laptop, was ready to take a break, he started to close the laptop.
[02:06.650 --> 02:09.630]  But I was not ready to end our co-working session yet.
[02:10.230 --> 02:12.890]  So I stopped the closing of the laptop.
[02:13.190 --> 02:17.010]  And Dana could feel that because they're haptically forced feedback connected.
[02:18.030 --> 02:22.370]  And through that we were able to communicate without words.
[02:24.730 --> 02:27.710]  Now we're going to show you a second demo to...
[02:41.850 --> 02:51.090]  So the reason why this is cool, why the first demo is cool, is because we think there's a lot of possibilities for wearable devices and haptic wearable devices.
[02:51.870 --> 02:54.630]  But we don't want to develop these technologies.
[02:54.630 --> 03:01.910]  And we don't want them to exist in a world where companies develop products so that they can get more data from you and sell it.
[03:04.290 --> 03:19.830]  So in order to support this kind of awesome technology in the future, we've designed these jewelry pieces with SD cards on them.
[03:19.830 --> 03:23.830]  So that we can store our data locally on our body and not in the cloud.
[03:26.570 --> 03:35.850]  And the idea here is that we have multiple jewelry pieces, like a ring, a watch, a necklace, an earring, that all has SD cards on them.
[03:36.310 --> 03:49.470]  And the data is dissolved across all of these different devices so that if you lose one, or if someone tries to take it from you, then they won't get access to all your data.
[03:49.630 --> 03:53.130]  And you won't lose all your data because it's kind of like a RAID structure.
[03:53.530 --> 03:55.430]  Dana will elaborate more on this later in the presentation.
[03:57.030 --> 03:58.070]  And it's also encrypted.
[03:58.070 --> 04:12.110]  So this demo is going to be an example of plugging in multiple SD cards until we get enough of them to unlock the data that's spread across all the SD cards.
[04:12.350 --> 04:13.390]  We call it dissolution.
[04:14.810 --> 04:20.830]  And if you wanted to pull it back from all the SD cards, it would be called crystallization.
[04:33.290 --> 04:38.650]  So these pieces of jewelry have a little SD card embedded in them.
[04:39.270 --> 04:45.490]  And you can pop them out and use them as you would a normal SD card.
[04:46.750 --> 04:47.490]  It's hard to see.
[04:47.570 --> 04:47.870]  I'm sorry.
[04:47.990 --> 04:49.230]  I'll show you on the camera in a second.
[04:49.910 --> 04:54.310]  But it also has a little strip of magnetic... of ferrous steel on it.
[04:54.650 --> 05:02.190]  So we can attach it to our computer with an adapter that has a magnet inside of it.
[05:34.070 --> 05:35.050]  You guys look great.
[05:39.670 --> 05:40.270]  Let's see.
[05:40.550 --> 05:41.870]  Video... Logitech.
[05:41.870 --> 05:42.270]  Alright.
[05:43.270 --> 05:43.710]  So...
[05:47.720 --> 05:48.360]  See okay?
[05:48.540 --> 05:48.700]  Cool.
[05:48.920 --> 05:49.640]  So this is the jewelry.
[05:57.270 --> 06:00.690]  We're selling these rims, by the way, if you want to come by our booth later.
[06:02.810 --> 06:04.130]  Um... SD card on jewelry.
[06:05.690 --> 06:06.570]  Magneted adapter.
[06:10.010 --> 06:10.450]  Ooh.
[06:19.060 --> 06:21.360]  Then the next cool trick is it actually mounts.
[06:21.880 --> 06:22.800]  It's not just a magnet.
[06:25.740 --> 06:26.180]  That's fine.
[06:27.280 --> 06:27.600]  Ooh.
[06:28.360 --> 06:28.640]  Cool.
[06:28.860 --> 06:28.880]  Yeah.
[06:31.540 --> 06:31.860]  So...
[06:32.200 --> 06:34.000]  We should do the presentation and we'll call back to these.
[06:34.140 --> 06:34.340]  Okay.
[06:34.480 --> 06:34.620]  Great.
[06:53.050 --> 06:53.370]  Alright.
[06:53.550 --> 06:54.370]  So live demos are hard.
[06:56.810 --> 06:59.990]  Thank you for bearing with us, everybody, while we attempt to do some live demos.
[07:06.170 --> 07:10.110]  And now we'll proceed to the rest of the presentation.
[07:10.310 --> 07:10.450]  Thanks.
[07:12.670 --> 07:17.230]  So we wanted to start by saying, we didn't think of these ideas ourselves.
[07:17.610 --> 07:19.210]  These ideas are not new.
[07:19.510 --> 07:27.950]  And we're grateful for all of the people who have came before us who've imagined and inspired us to try playing with these things.
[07:33.470 --> 07:34.090]  Okay.
[07:35.090 --> 07:35.590]  Yeah.
[07:35.710 --> 07:53.930]  So in particular, our project explores a lot of connection between people as a means of achieving better decision-making power or unity or other novel characteristics, which is something that shows up in like the fusion characteristics, mechanics in Steven Universe or Octavia Butler's hyper empathy.
[07:55.110 --> 08:02.990]  The Three-Body Problem explores collectivism in virtual worlds, actually in a bad way, but it does cover that idea.
[08:04.210 --> 08:12.410]  Ancillary Justice starts off with a main character who is entirely immersed in a hive mind and that's treated as a keystone part of the universe.
[08:12.570 --> 08:16.750]  And so these are very well embedded ideas into sci-fi culture.
[08:16.890 --> 08:20.830]  So our objective is to take a lot of them all at the same time and advance them simultaneously.
[08:23.960 --> 08:32.140]  And we're inspired by projects that have come before us, particularly GovZero in Taiwan.
[08:32.640 --> 08:39.820]  Audrey Tang was the Digital Minister of Taiwan and implemented a lot of really unique solutions to digital democracy.
[08:42.140 --> 08:54.460]  And Nora Bateson has a program exploring warm data, which is contextualized data, data that takes into account all the data that was around it, but not just pulling out and analyzing that on itself.
[08:54.780 --> 08:57.500]  And there's also this cool tool called Pollis.
[08:57.780 --> 09:04.940]  You can look it up, pol.is, which is a platform that helps pull perspectives together.
[09:06.300 --> 09:13.260]  Like Audrey Tang and Taiwan used Pollis to be able to draft legislation whether or not Uber should go to Taiwan.
[09:13.260 --> 09:19.780]  And they had the taxi drivers and all the different relevant stakeholders together to draft that policy using Pollis.
[09:20.580 --> 09:25.300]  And so it's an example of an algorithm that pulls for cohesion rather than diversion.
[09:26.380 --> 09:28.260]  And we're really excited about some of these projects.
[09:28.680 --> 09:37.180]  This Call Me ring up here, this ring, Hackadain, is a demo that we're going to show today that is possible because of this person doing all this work.
[09:40.020 --> 09:41.560]  You can find more information here.
[09:47.480 --> 09:53.720]  And then also the wiggling laptop demo is made possible by Aya Musa.
[09:55.140 --> 10:00.460]  Special thanks to him for making the design files available for these capstan drives, which are extremely difficult to design.
[10:00.580 --> 10:01.480]  So huge shout out.
[10:01.580 --> 10:04.680]  And if you want to support him, please search him up if you do mechanical design like this.
[10:07.460 --> 10:19.080]  So another thing, we made up a lot of names for this project to try to explain how you can, to try to explain connection, new types of human connection.
[10:19.080 --> 10:36.340]  And so being able to transmit haptic data, haptic feeling, force feedback across distance, we're calling tacking because the telegram and phones allowed for sharing of audio sensing across distance.
[10:36.340 --> 10:41.120]  And then the Internet allowed for sharing of visual senses across distance.
[10:41.380 --> 10:49.480]  And we think that we're on the beginning of a new era of wearables that are going to allow for tactile communication across distance.
[10:50.420 --> 10:51.740]  And so tactile, tacking.
[10:53.600 --> 11:01.300]  We also think that SD cards are... they've come to a point where they're cheap and they're 1.5 terabytes.
[11:01.480 --> 11:02.760]  They're insane new capacities.
[11:03.240 --> 11:06.140]  And so there's a sweet spot that they're unique.
[11:06.300 --> 11:06.660]  They're everywhere.
[11:06.900 --> 11:07.100]  Sorry.
[11:07.400 --> 11:08.140]  They're standard.
[11:08.360 --> 11:08.740]  They're everywhere.
[11:08.920 --> 11:10.700]  All of our devices, you can use them.
[11:10.980 --> 11:17.040]  And so building this data sharing storage method around SD cards is one of the core ideas.
[11:17.040 --> 11:25.480]  And so SD, self data, soul data, the name of the data protocol is Sorodyne.
[11:25.760 --> 11:27.700]  Yeah, the project is also called Sorodyne.
[11:27.800 --> 11:31.200]  So this is just the word dinosaur reversed so that it spells SD.
[11:31.900 --> 11:39.520]  The point is not just to do everything SD, but also to point out that what we're building here is kind of a proof of concept intentionally.
[11:40.380 --> 11:45.760]  It is not supposed to be used as security software, even though it is envisioned as a future private interface.
[11:46.660 --> 11:50.540]  So we're hoping that it goes out of date very quickly, but I'd love to show you how it works.
[11:52.500 --> 11:55.160]  We also made some icons that we're going to reference throughout the presentation.
[11:57.520 --> 12:01.180]  You came to this talk because you like the abstract.
[12:01.480 --> 12:02.420]  So what does zoom mean?
[12:03.860 --> 12:05.960]  Well, it's actually getting at a bigger vision.
[12:07.080 --> 12:14.660]  We assume that collective decision making will be the best solution for navigating us through these hard times, through these complex crises.
[12:15.160 --> 12:24.960]  And it's become apparent that as long as there's a group of organizations that are surveilling the people, that collective governance is not possible.
[12:26.660 --> 12:31.320]  And so first we need to take our data, reclaim our data back from these platforms.
[12:31.320 --> 12:49.060]  And then that will enable us to build these kind of cool technologies, which we believe through sharing haptic feedback, through sharing our touch sensations, we can develop the connections to collaborate across nations, across borders, to get to digital governance around the world.
[12:53.310 --> 12:55.790]  So the goal, digital governance, without borders.
[13:00.470 --> 13:04.650]  We're at a time when we need new tools to be able to tackle these problems.
[13:07.250 --> 13:11.090]  In order to get there, we believe that we need to have these...
[13:12.410 --> 13:24.050]  We believe that through these technologies we can do projects together, like RIM, like Pacific RIM, where you have two humans to operate this massive robot.
[13:24.310 --> 13:25.150]  You can't do it alone.
[13:26.090 --> 13:34.870]  And so through these connection technologies we can learn more about ourselves if we have our data, if we have the right to bear data.
[13:36.550 --> 13:38.370]  We can learn about our health and our choices.
[13:38.710 --> 13:41.310]  We can share that data with our friends and our community.
[13:41.310 --> 13:56.390]  And ultimately, learn more, get more personally tailored insights into how we live our lives with connections with our health coaches.
[13:56.710 --> 13:56.930]  Right.
[13:57.030 --> 14:05.630]  But we're not going to be able to reach for those heights without some ability to have really reliable, accessible bedrock authentication that's based on peer-to-peer architectures.
[14:06.250 --> 14:10.310]  This is not, of course, new to anybody here, but we're hoping to offer kind of a fresh take.
[14:11.030 --> 14:16.930]  But, you know, once we have those in place, then we can hope to build these technologies that will let us coordinate and cross borders like this.
[14:17.030 --> 14:20.130]  So there's another step before that, though.
[14:21.350 --> 14:24.230]  Go ahead.
[14:26.030 --> 14:27.250]  So in order to...
[14:27.250 --> 14:29.130]  So I want to use all these cool tools.
[14:29.350 --> 14:30.510]  I'm super excited about it.
[14:30.830 --> 14:37.790]  But I don't want to live in a world where we're using these tools that are captioning all of our 3D pose data of my body movements.
[14:37.790 --> 14:40.530]  And being monetized by companies.
[14:41.190 --> 14:43.910]  So first, we need to make an ecosystem of trusted tools.
[14:44.290 --> 14:45.550]  Both hardware and software.
[14:46.490 --> 14:50.150]  And so the idea of SD cards in a business card.
[14:50.250 --> 14:53.950]  We can have 10 terabytes in our business card, in our mallets, around our necks.
[14:57.270 --> 15:01.110]  And because it's stored on my person, no one else can manipulate it.
[15:02.290 --> 15:17.630]  Another key insight into how this will lead to collaboration platforms and digital governance and not just get taken over by the Apples and Googles of the world is innovation at the edge of taboo.
[15:18.770 --> 15:29.410]  The hope is that by introducing some technologies that are not possible to be touched by the big corporations because they just fall just outside of what's considered acceptable.
[15:29.870 --> 15:40.210]  Like, for example, I read a really wonderful research paper very recently about putting haptic ears on people for virtual reality.
[15:40.210 --> 15:43.030]  Something like 40% of all virtual reality avatars have ears.
[15:43.810 --> 15:50.590]  And to embody them, you could absolutely run a physics simulation that puts the correct forces on your scalp as if you had ears.
[15:50.590 --> 15:55.070]  I think that is just incredibly fascinating and also probably Google will not be coming out with that product.
[15:55.910 --> 16:11.550]  So that's just one example of ways that it's possible to maybe seek adoption or enter a market or get people involved where it won't immediately be subsumed and taken over.
[16:16.160 --> 16:20.020]  So all of that leads us to what we're actually going to talk about in our talk.
[16:20.020 --> 16:23.460]  But everything up to this point, this is like why we're doing this.
[16:23.460 --> 16:27.660]  We're hoping to communicate what is motivating us to go down this sort of convoluted path.
[16:28.180 --> 16:32.580]  But at the end of the day, what we're really talking about is this RIM self-data protocol that we've been developing.
[16:34.460 --> 16:42.400]  It's built on free and open-source software values with what we're calling Brass Roots.
[16:42.720 --> 16:44.260]  It's like a grassroots movement.
[16:45.040 --> 16:45.100]  Yeah.
[16:46.200 --> 16:46.560]  So...
[16:47.720 --> 16:48.300]  Yeah, go ahead.
[16:48.300 --> 16:50.740]  One quick reason why now is important.
[16:50.900 --> 16:56.720]  We believe that we're at the brink of a Cambrian explosion of wearables because storage is so cheap.
[16:56.960 --> 17:08.720]  And it's a new opportunity for FOSS to really get embedded in this new era of technology and devices like Linux was for servers.
[17:09.380 --> 17:12.460]  FOSS didn't quite get into the phones, but I think we can get into the wearables.
[17:15.500 --> 17:27.180]  Also, sorry, it's important that we do this before BCIs are predominant because if we have those in the world that exists as it is now, I don't believe that the data extraction business models will change.
[17:27.400 --> 17:31.180]  That's a brain-computer interface, by the way, just for people.
[17:32.140 --> 17:33.380]  So we're going to talk about this.
[17:37.660 --> 17:38.320]  SD-Core.
[17:38.440 --> 17:39.320]  What is SD-Core?
[17:40.240 --> 17:42.080]  SD-Core is an aesthetic.
[17:42.760 --> 17:44.940]  Basically, we're trying to communicate...
[17:44.940 --> 17:48.840]  So we've just talked about SD cards and how incredibly high capacity they are.
[17:48.920 --> 17:50.240]  They're almost magically high capacity.
[17:50.400 --> 17:54.480]  Like the one in my ear, we have some that are 1.5 terabytes in scale.
[17:54.480 --> 17:57.780]  So that's three times the capacity of my entire laptop in one ear.
[17:58.320 --> 17:59.540]  It's actually...
[18:00.000 --> 18:05.180]  It kind of flies in the face of this idea that you have to have big data corporations to host your own personal data.
[18:06.340 --> 18:11.500]  So you could just take advantage of that fact and have all your data on your body and do it quietly.
[18:12.160 --> 18:16.460]  But we actually think that it's even better to be loud about it.
[18:16.460 --> 18:22.360]  So to put your SD cards on your ear or on your person, there's more of them here.
[18:22.540 --> 18:25.480]  And it basically just says to the world, like, you have no idea what's on this.
[18:25.540 --> 18:26.740]  And Google doesn't know what's on this.
[18:26.780 --> 18:34.140]  I have chosen to intentionally opt out of the data vampiricism norms of our age.
[18:35.640 --> 18:38.220]  And just have all of my data just for me.
[18:45.880 --> 18:47.040]  Yeah, that's the next section.
[18:47.180 --> 18:47.340]  Sure.
[18:48.540 --> 18:49.780]  We'll be skipping the demo this time.
[18:49.860 --> 18:51.620]  But I'm going to talk about the Sordine live data model.
[18:51.760 --> 18:51.840]  Yeah.
[18:58.390 --> 19:01.350]  So just to get into the technical details, at least briefly.
[19:01.690 --> 19:08.230]  So the self-data object is like the basic unit of the Realm self-data protocol.
[19:08.770 --> 19:11.710]  They actually are asynchronous data flows between peers.
[19:11.910 --> 19:16.350]  They are not like an object that you would have in an object-oriented programming language.
[19:16.510 --> 19:20.590]  They exist entirely as a synchronization procedure between peers.
[19:21.590 --> 19:25.070]  The original data is stored locally via what we're calling dissolution.
[19:26.390 --> 19:29.550]  And when it needs to be sent elsewhere, it's compressed over networks.
[19:29.690 --> 19:41.150]  So dissolution, I'll tell you about that in a moment, but it basically just means that the data has been taken apart into component pieces and spread across multiple places to store it, such that no single one of them has any of the data on it.
[19:41.150 --> 19:50.030]  So if someone finds, if I have like important data or financial data or whatever on my ear, someone finds my earring, they don't get any important information about me until they get more of my things.
[19:51.210 --> 19:51.870]  Ideally never.
[19:53.670 --> 20:02.050]  Right, so you receive your data flows, you store them to local storage, and then if you want to view them later, you decompress them or crystallize them.
[20:02.110 --> 20:03.650]  That is like the opposite of dissolution.
[20:04.550 --> 20:13.630]  And then peers will use lightweight replicated data types, CRDTs, to track the location of the data within the constellation of trusted devices.
[20:13.630 --> 20:16.050]  So that's kind of like the overall, the overview.
[20:16.450 --> 20:19.590]  So your body can be your storage and also your identity.
[20:19.970 --> 20:25.590]  So your physical devices become your storage and your cryptographic identity through this dissolution protocol.
[20:25.910 --> 20:29.450]  The data is dissolved redundantly across all of your personal devices.
[20:29.630 --> 20:35.730]  And along the bottom, you can see some examples of places you might put an SD card that you may have thought of or maybe not have thought of.
[20:36.530 --> 20:40.550]  And attackers would need physical access to multiple items at the same time that you own.
[20:40.550 --> 20:45.530]  And each key and data piece is encrypted on different sets of devices.
[20:47.990 --> 20:56.890]  So Soradyne is the software package that is a proof of concept for this dissolution, crystallization, networking, CRDTs, all of that.
[20:57.810 --> 20:59.370]  And you can find it on GitHub.
[20:59.690 --> 21:01.550]  It's available if you want to check it out.
[21:01.850 --> 21:06.190]  Of course, not for production use at the moment, but it's hopefully interesting to you.
[21:08.770 --> 21:19.410]  Yeah, so overall, you're having multiple storage capable devices.
[21:19.430 --> 21:21.110]  You might say, like, okay, how do you get it off of the ear?
[21:21.230 --> 21:25.830]  Even with the mag adapter that Jaguar showed earlier, it might not be super straightforward to get data on and off of your ears.
[21:26.210 --> 21:28.150]  But that's not quite the vision we're trying to articulate.
[21:28.150 --> 21:33.290]  What we're showing is that it's possible, it's actually easy, it's trivial to put this much storage just on your person.
[21:33.410 --> 21:36.550]  And you become the server, the data center, you become the host of everything.
[21:37.010 --> 21:40.550]  So all we have to do is add one small layer of connectivity to your body.
[21:41.050 --> 21:50.030]  For example, Bluetooth low energy, if you are okay with radiating encrypted data from your body, or other ideas about how you might be able to contain that communication locally.
[21:50.030 --> 21:51.510]  There's many options.
[21:52.050 --> 21:58.190]  But we're within a hair's breadth of being able to actually use this type of body networking.
[22:00.790 --> 22:05.140]  I just wanted to talk briefly about the way that the dissolution is actually implemented.
[22:05.970 --> 22:08.130]  So it uses a cascaded encryption model.
[22:08.370 --> 22:10.250]  The top layer is Shamir secret sharing.
[22:11.590 --> 22:15.130]  And the bottom layer is read Solomon erasure-coded blocks.
[22:15.390 --> 22:17.710]  This is actually just for the people who know what this stuff means.
[22:17.750 --> 22:19.130]  I wanted to at least put it in there.
[22:20.010 --> 22:29.170]  So the reason that both are at play is I want it to be the case that you have to collect a certain amount, say three of five different pieces of data, before you can read it.
[22:29.250 --> 22:33.190]  And I also want you to be able to lose any two of them and still reconstruct it.
[22:33.310 --> 22:38.190]  So that's those two closely related ideas that are not accomplished by any one cryptographic entity.
[22:38.190 --> 22:44.130]  So that's why we do Shamir secret sharing to share a small cryptographic key, which is reconstructed locally.
[22:44.390 --> 22:49.870]  And then we use read Solomon erasure-coding to reconstruct data and then decrypt it locally.
[22:49.990 --> 22:57.530]  And you can actually store the shares and the read Solomon erasure-coded blocks at the same place, at the same locations around your data storage.
[22:57.610 --> 23:07.930]  Or you can store them with different values for how many different values instead of five and three, you can do seven and four for more or less redundancy and security.
[23:10.190 --> 23:12.330]  So yeah, ideas for where you could put it.
[23:12.530 --> 23:18.890]  Earrings, watch, belly chain, phone, ring, your tailbone, an anklet, not to mention cat ears from earlier.
[23:19.210 --> 23:21.090]  You could stuff them full of a petabyte of data.
[23:21.870 --> 23:22.690]  Can I get that high?
[23:22.830 --> 23:23.190]  Probably not.
[23:23.350 --> 23:24.130]  Hundreds of terabytes.
[23:25.910 --> 23:29.530]  And you could put it in your heels of your shoes or you could wear wings.
[23:29.910 --> 23:32.450]  Whatever your height might drive you to do.
[23:35.510 --> 23:38.290]  So what are the types of data that we are actually talking about here?
[23:38.390 --> 23:41.110]  Well, you've seen the tactile demo that we made.
[23:41.510 --> 23:43.750]  That's what's pictured on the top left-hand corner here.
[23:43.970 --> 23:51.450]  But we also think of other types of data as self-data, live self-data, like videos, video calls, or just telephone data.
[23:51.590 --> 23:52.730]  This is also your message history.
[23:52.850 --> 23:53.430]  It could be your email.
[23:53.670 --> 24:09.610]  Any amount of things that are very personal to you that you want to be even more secure and even more personal to you than they are in the current ecosystems, especially if you use cloud providers, which I think is many of us in the room, then you could consider these to be elements of self-data
[24:09.610 --> 24:15.690]  that you'd want to control and distribute and make available off of your own body using Sorodyne and the RIM protocol.
[24:17.430 --> 24:19.070]  However, what is received is not what's sent.
[24:19.190 --> 24:26.910]  You get back this pixelated stuff where you get a noisy output or you get the kind of reconstructed audio from a minimal data stream.
[24:27.490 --> 24:30.350]  This is an echo of that idea of like all data is derived.
[24:30.870 --> 24:44.690]  There's no such thing as the actual... even if you open your phone and look at phone images that are literally stored on your hard drive, you're not looking at the actual pixel data, you're looking at a resampling of that data for your screen at multiple resolution levels if it's stored remotely.
[24:44.690 --> 24:47.510]  So this is a general concept, we think.
[24:47.730 --> 24:53.090]  And you don't want to do file sharing where you copy literal data around and then display it.
[24:53.210 --> 24:59.750]  You want to be sending just the actual derived pieces that are relevant for the use case that you're trying to serve in that moment.
[25:01.870 --> 25:03.610]  So this is the overall architecture.
[25:04.370 --> 25:09.350]  LiveSelf data gets teed into dissolved local storage and compressed, sent over network.
[25:09.670 --> 25:12.850]  It's also dissolved to local storage wherever it arrives.
[25:13.150 --> 25:14.830]  It's decompressed and shown.
[25:15.030 --> 25:20.350]  So at both steps, it's possible to save to all of your connected devices.
[25:21.750 --> 25:24.730]  And just putting it all together, this is all of the things on one slide.
[25:24.850 --> 25:26.130]  It's just kind of overwhelming by itself.
[25:26.270 --> 25:27.910]  So you can see the structure and the elements.
[25:28.930 --> 25:32.190]  But that's the overall live self-data model.
[25:34.910 --> 25:35.690]  That's so cool.
[25:35.870 --> 25:36.370]  Oh, my God.
[25:44.200 --> 25:44.520]  So...
[25:47.390 --> 25:48.170]  Oh, oh, right.
[25:48.290 --> 25:48.430]  Sorry.
[25:49.830 --> 25:50.210]  Yeah, okay.
[25:50.290 --> 25:50.410]  Sorry.
[25:50.510 --> 25:50.610]  Right.
[25:50.910 --> 25:51.190]  Continuing.
[25:51.630 --> 25:58.710]  So moving beyond cloud dependency for things that we usually think of as cloud-provided things, such as, you know, if you lose your password, you have a password reset.
[25:58.990 --> 26:02.430]  This is... you may or may not think of that as a cloud service, but it's still a remote service.
[26:02.430 --> 26:04.110]  We're hoping to do that entirely locally.
[26:04.330 --> 26:07.350]  So the traditional approach would be identify...
[26:07.350 --> 26:11.470]  do identity and storage from data giants and cloud providers.
[26:11.690 --> 26:19.430]  And you recover or you have your data loss provisions covered by remote things.
[26:19.550 --> 26:28.970]  But the REM approach would be to actively rebalance all of the degrees of freedom of redundancy for your ecosystem of data so that you're unlikely to lose it.
[26:28.970 --> 26:37.510]  And we have a background process, not developed yet, but it will be next, that moves data around to rebalance it to minimize the probability that you lose anything.
[26:38.770 --> 26:39.950]  Yeah, so I'll skip that.
[26:40.090 --> 26:40.290]  That's okay.
[26:40.990 --> 26:42.910]  The point is that we can be our own servers.
[26:43.010 --> 26:47.070]  And because we have phones in our pockets, we're basically multiple nines up time servers.
[26:48.350 --> 26:54.810]  So whatever you may have thought you needed a cloud provider for, you can probably serve that need yourself.
[26:54.810 --> 26:56.270]  We're also connected now.
[26:58.110 --> 27:07.850]  So serving a remote request from direct dissolved storage involves querying the CRDT, finding the shards, reconstructing the blocks, and sending them back.
[27:12.890 --> 27:14.350]  So this enables...
[27:16.130 --> 27:19.630]  This enables building tools and...
[27:20.870 --> 27:24.590]  This enables basically having all your data on your person so that you can...
[27:24.590 --> 27:26.570]  When you have a wearable...
[27:26.570 --> 27:33.010]  Ideally, the wearable buys into this way of sharing data so that it's not hidden from you.
[27:33.190 --> 27:36.810]  And you can then download it, extract it, view it, play with it.
[27:36.810 --> 27:43.370]  And so we've actually got a workshop later today where we're going to build our own jewelry with these SD cards.
[27:43.530 --> 27:47.050]  And then extract Signal message history from Signal desktop if you have it.
[27:47.610 --> 27:54.750]  And then Chong Bai has awesomely made this visualization script to be able to play around with all your data.
[27:55.030 --> 28:00.330]  So this is like one example of something that we can do much more of.
[28:00.330 --> 28:08.870]  Imagine like a goodness index where you craft your own algorithm based on what brings you happiness and joy in your life.
[28:09.090 --> 28:14.990]  And you compare that, get kind of a sum aggregate metric of the data that you feed into it.
[28:26.070 --> 28:31.270]  So this sets us up for a future where we can trust our digital tools and...
[28:34.550 --> 28:37.670]  And this may have implications for a lot of different aspects of society.
[28:37.670 --> 28:41.590]  I just wanted to call back to a talk that we gave in 2020.
[28:42.910 --> 28:53.310]  So it's possible that you could be collecting information that is relevant for proving your own learning all the time, which sounds kind of creepy and you wouldn't want to be like storing that up and backing it up.
[28:53.770 --> 28:56.890]  Say the data about your child and what they learned in school today.
[28:57.050 --> 29:02.910]  You don't necessarily want that like in Google servers and then used later in life to manipulate them and advertise to them and things like that.
[29:03.290 --> 29:04.170]  I don't want that either.
[29:04.290 --> 29:12.910]  However, it would be extremely nice if you could actually trust that and you could accumulate that because then you could just derive your credentials from the actual data of what you experienced.
[29:12.910 --> 29:24.290]  And you could also go to your teacher and say, this is not here's a test and my results, but here's the data that just shows my actual understanding of that thing and extracts of it, summaries of it, like the signal message history.
[29:24.470 --> 29:26.550]  Instead of a message history, it's a transcript.
[29:26.790 --> 29:27.710]  That kind of idea.
[29:28.550 --> 29:38.450]  And building off of the signal message history, you can imagine having so many sensors on your body that you're collecting that you can get an accurate picture of your entire 3D pose throughout all time.
[29:39.090 --> 29:50.710]  And so if you go to a massage therapist and they're feeling where there's tension in your body, they can actually relieve that tension completely around your body, but then that would hurt you.
[29:50.850 --> 29:56.530]  You would get injured because you've built up certain habits because of how you live your life.
[29:56.670 --> 29:59.230]  And those habits are your livelihood.
[29:59.230 --> 30:16.990]  So if the therapist had access to seeing at what points in your daily routine you're building up this tension, they can then differentiate based on your speaking with them and your sharing the data that you have access to and your consenting to share.
[30:17.250 --> 30:31.250]  They can piece out which parts are because you're like a construction worker or you're sitting at a desk and you need those kinds of muscles to be activated versus a tweak in a soccer game or other forms that you'd like to change.
[30:31.490 --> 30:41.090]  So there's this kind of like slow and fast changing habits through having access to your real-time data and being able to share that with health professionals that can help you heal.
[30:41.750 --> 30:54.470]  And so ultimately the goal is to be able to outpace the rate of trauma by accelerating and strengthening and sharpening healers' abilities to heal the people they are healing.
[30:55.790 --> 31:00.890]  Like when you show up in a doctor's office and you would like to provide your medical data, like what's your immunizations?
[31:00.890 --> 31:04.230]  Even before, like the basics that we're familiar with everyday life.
[31:04.730 --> 31:08.990]  Many may have been to massage therapy, I'm not sure, but many of us will certainly have had vaccinations.
[31:10.030 --> 31:22.490]  To have your allergies, your vaccinations just available to you, not because there was a medical sharing server that you somehow made its way to your doctor, but because it's literally stored on your body exactly where it's relevant.
[31:23.350 --> 31:25.050]  That would be part of the vision.
[31:26.310 --> 31:37.350]  And so all of this leading up to being able to have more mutual connection across people around the world, like imagine holding someone's hand in a different country.
[31:38.150 --> 31:44.590]  As we grow more and more connected with physical sensation, more becomes unthinkable.
[31:47.190 --> 31:49.530]  And that's one of the goals of RIM.
[31:49.530 --> 31:55.590]  And another thing is that like brain-computer interfaces, 20 years from now, maybe everyone has one.
[31:56.090 --> 32:02.270]  And so being able to draft relevant, humane policy for that future, starting now is really important.
[32:02.630 --> 32:18.410]  And being able to build these tools that give us a sense for what telepathy is going to feel like, can give enough context and build up enough experience for policymakers that make those decisions to make the relevant policy before it happens.
[32:21.670 --> 32:22.930]  Thanks for coming to our talk.
[32:29.870 --> 32:38.110]  We'd like to give some special thanks to the people that helped support us in making this, and also invite Chong Bai and Nora up onto stage.
[32:38.390 --> 32:44.670]  They will be helping us with our workshop at 1pm in Tobin.
[32:48.630 --> 32:50.730]  So that's just approximately one short hour from now.
[32:50.890 --> 32:55.330]  You can come and join us and work with these fine folks to make your own jewelry, if you like.
[32:55.570 --> 32:58.190]  We will have SD cards that you can just have.
[32:58.310 --> 33:00.570]  They're very small capacity and very cheap, so feel free to...
[33:00.570 --> 33:02.130]  While supplies last, you can just have one.
[33:02.650 --> 33:07.170]  If you do want a bigger capacity card or nicer materials, we have that too, at cost.
[33:08.210 --> 33:18.510]  So please come on by, and even if you just hang out with us and tell us how this resonated with you and how we can potentially change our trajectory to match your ideals, that would be amazing.
[33:20.510 --> 33:21.150]  Thank you.
[33:21.470 --> 33:23.270]  Right, we have some time for questions.
[33:23.270 --> 33:24.630]  Any questions in the room?
[33:25.250 --> 33:27.150]  If you have any questions, please come up to the mic.
[33:27.770 --> 33:30.450]  While they're coming up, I do have one question from the chat.
[33:30.910 --> 33:37.030]  Question, if widely adopted, don't these become a target for law enforcement, particularly at border crossings?
[33:37.030 --> 33:38.690]  Or for other ne'er-de-wells?
[33:38.890 --> 33:40.510]  I think that is a phenomenal point.
[33:40.690 --> 34:01.410]  I also think that you need to weigh the positives of having all of that data stored elsewhere, and then potentially accessible to law enforcement when you might not want that to happen, via means that you cannot control, versus having any kinds of physical ownership or containment over it.
[34:01.490 --> 34:04.710]  Like, you can just destroy what's on your body if you absolutely need to.
[34:04.710 --> 34:09.930]  You can just take your earrings off and crush them, or eat them, or whatever.
[34:10.650 --> 34:18.230]  And I think giving people that level of autonomy is a really amazing gift that just can't be matched by trying to do this other ways.
[34:18.950 --> 34:23.590]  One example, sorry, might be that we make these forms of data storage swallowable.
[34:28.810 --> 34:31.270]  Hi, I just wanted to thank you for your talk.
[34:31.430 --> 34:42.190]  I think it's really inspiring, the sort of moving beyond sort of a corporate capitalist kind of like metaphor for a lot of these things.
[34:42.190 --> 34:49.630]  And the, I think it's really great, like looking to science fiction and other things for inspiration.
[34:49.890 --> 35:00.570]  I did just want to ask, like, I realize it's super early days and things like connectivity and things like that aren't, you know, by any means solidified or anything like that.
[35:00.570 --> 35:07.430]  But if you did have any early thoughts, I was wondering if you could expand on your thoughts on things like authentication and authorization.
[35:07.930 --> 35:25.810]  Like how am I, if I am exchanging information with somebody, how do I basically either verify or even like permit that I'm sharing that information with this person I intend to and not someone who's brushing past me in a crowd or something like that.
[35:25.810 --> 35:28.890]  If, if, if you have any early ideas about that, I'd be interested to hear.
[35:29.370 --> 35:29.810]  Sure.
[35:30.010 --> 35:30.130]  Yeah.
[35:30.290 --> 35:38.110]  So, um, I think the first thing I would say there is that you'd want your thresholds to be set differently for your authentication versus your data reconstruction.
[35:38.210 --> 35:46.390]  So you might want to have like four things of yours nearby or one thing with particular importance plus two other things, that kind of, uh, distribution.
[35:46.710 --> 35:51.170]  Um, so basically prepare yourself to have, uh, the security guarantees that you want.
[35:51.430 --> 35:54.190]  What you're actually unlocking when you go and pull that data.
[35:54.190 --> 36:00.730]  Uh, sorry, hopefully that are just the, like the first concern, which is just, you don't want someone making off with it and being able to impersonate you.
[36:00.990 --> 36:01.950]  That was part of it.
[36:02.150 --> 36:03.470]  Uh, yeah, I think so.
[36:03.730 --> 36:04.210]  That's part of it.
[36:04.310 --> 36:04.750]  That's part of it.
[36:04.830 --> 36:04.890]  Right.
[36:05.010 --> 36:11.570]  So, um, at that point you reconstruct from the, the things that are relevant or that the, the blocks that store that data.
[36:11.750 --> 36:16.470]  Um, ideally only you can do, and you just pull out very normal encryption information.
[36:16.470 --> 36:25.650]  Like you just get a normal private key that you would use to, uh, decrypt a key that could be used to secure a, uh, a third-party channel.
[36:25.930 --> 36:28.270]  Um, or like fully off device channel.
[36:28.370 --> 36:34.250]  So I think we, we really just do a, an authentication layer, like a challenge sign type of thing.
[36:34.410 --> 36:36.350]  And we use, uh, established tools.
[36:36.350 --> 36:39.750]  Like the only difference is just where you choose to store your secret.
[36:40.130 --> 36:46.870]  And I think the, um, the model that many of us prefer, which is that you have to keep a secret perfectly secret forever and you can never lose it.
[36:46.970 --> 36:51.610]  And if you do, your life is over is probably part of why it's very, very difficult to penetrate this community.
[36:51.770 --> 36:53.490]  We have of people who are very security minded.
[36:53.810 --> 36:55.810]  That is basically our defense, right?
[36:55.950 --> 36:57.510]  Like you have to keep your private key safe.
[36:57.690 --> 37:02.450]  So imagine if you basically had to keep your private key safe, but you could mess up twice.
[37:02.450 --> 37:07.930]  Um, I think that would be a much more flexible framework, but still basically use all the tools we use today.
[37:09.030 --> 37:09.610]  Thank you.
[37:13.660 --> 37:14.100]  Yeah.
[37:14.260 --> 37:17.240]  Thank, thank you so much for this, uh, presentation.
[37:17.340 --> 37:18.640]  It was really interesting.
[37:19.080 --> 37:27.560]  Um, I, while you are, while y'all were talking, I was thinking about how, um, on this.
[37:28.380 --> 37:55.940]  And when considering how this, uh, project functions as a form of, um, bodily and digital autonomy, and how we can build, um, a life outside of, uh, the strangleholds of oppressive regimes and capitalism, um, Um, I was thinking about how this could be applied to,
[37:55.960 --> 38:04.380]  um, bodily and autonomous, uh, infrastructures and collective organizing mechanisms, um, like of itself.
[38:04.640 --> 38:13.680]  And so one of the things I was thinking of is how, um, something that's been happening increasingly, especially in red states, is, um, DIY HRT networks.
[38:13.680 --> 38:19.320]  Um, and, uh, I'm, have friends and comrades that are doing that right now.
[38:19.720 --> 38:22.620]  Um, obviously it's pretty high stakes for a lot of reasons.
[38:22.620 --> 38:36.080]  But one of the, um, one of the things that they have been coming up with, um, is that doing our, uh, for hormone replacement therapy for, uh, trans people, for people who don't know, sorry.
[38:36.340 --> 38:58.560]  Um, and, uh, and the idea is that there's states that are increasingly, um, uh, not allowing, um, uh, HRT and there is a war on trans peoples we're all very familiar with, um, in figuring out how we can provide healthcare services and gender-affirming care for people who are trans,
[38:58.820 --> 39:00.040]  um, and on the trans spectrum.
[39:00.520 --> 39:11.060]  But, uh, one of the, one of the things that is tricky about that is that, um, there's HRT and other types of more medical-related affirming care.
[39:11.060 --> 39:12.600]  There's a lot at stake.
[39:12.900 --> 39:20.680]  Um, I, for instance, have a friend who passed away from getting, um, HRT off the, the black market, um, unfortunately.
[39:21.160 --> 39:29.200]  And out of not keeping up with her, um, blood pressure levels and, and, like, other, other, you know, other levels.
[39:29.200 --> 39:46.460]  And so, in, in that, people have been thinking of, like, well, how, if we want to try and build these, like, DIY HRT, like, networks to provide this, like, life-saving care, the care doesn't come just from providing the HR, to providing the hormones.
[39:46.460 --> 39:48.220]  There has to be something that is prolonged.
[39:48.220 --> 39:52.580]  And yet, if we're not doctors, how do we save that healthcare data?
[39:53.020 --> 40:09.880]  Um, and, so I was like, oh, this would be so interesting to see how that could, this, this functions as a form of trans bodily autonomy, collective organizing, that could be, like, coalesced with that type of work, uh, if, if that, if you guys are following me at all.
[40:09.980 --> 40:12.180]  And so, one, I think I just was like, what are your thoughts?
[40:12.480 --> 40:16.340]  But, um, like, do you see that as something that could be mobilized?
[40:16.500 --> 40:30.100]  And, like, obviously, I think that there, one dilemma is that, like, we're clearly have to, it's something that all of us need to do is get, be more aware of, like, tech literacy, that, like, the knowledge that we all have on technology and digital media,
[40:30.360 --> 40:32.100]  we need to translate that.
[40:32.100 --> 40:37.780]  Yeah, yeah, okay, yes, yes, yes, I'm sorry, I just, I should have just asked, talked to you guys afterwards, but just talk, yeah.
[40:38.120 --> 40:40.140]  I am so glad that you've joined us as a co-presenter.
[40:40.380 --> 40:41.800]  No, I'm really sorry, I'm really sorry.
[40:41.900 --> 40:46.740]  No, no, I, that was meant extremely sweetly, like, thank you so much for providing all of that amazing context.
[40:47.080 --> 40:52.820]  Um, and I wanted to say, uh, yeah, thank you for being so direct and open, and for sharing your friend's story.
[40:52.900 --> 40:55.840]  And that's very, uh, very close to your heart, I'm sure.
[40:56.420 --> 40:57.360]  Um, it's also close to mine.
[40:57.640 --> 41:02.080]  I have, uh, partners who require therapy of exactly that kind.
[41:03.220 --> 41:05.840]  Um, it's a deeply personal question, of course.
[41:06.140 --> 41:10.320]  Um, and I also don't think one answer will work for everybody, normal caveats, right?
[41:10.940 --> 41:18.260]  Um, that said, I do think that showing up into a medical system that is designed to serve you based on the data that just shows up with your body.
[41:18.720 --> 41:26.420]  It's already a big step in the right direction, and almost, like, completely antithetical to the, like, the current things that could deny you, uh, standards of care.
[41:26.640 --> 41:29.500]  Which are basically at emergency levels of necessity, right?
[41:29.580 --> 41:30.780]  Like, you cannot skip that stuff.
[41:30.900 --> 41:36.520]  You must have monitoring along with your HRT, or you may face the horrible consequences that your friend faced, right?
[41:36.640 --> 41:43.500]  So, um, I hope that what technology we've developed will be able to assist that, and I'd love to talk with you more about it.
[41:44.280 --> 41:44.860]  Thank you all.
[41:44.920 --> 41:45.340]  Thank you, Art.
[41:45.480 --> 41:46.780]  Let's give a nice round of applause.
[41:46.780 --> 41:47.800]  Thank you, Art.
[41:48.580 --> 41:50.740]  Thank you, Art.